Re: [PEPPERMINT] PEPPERMINT Digest, Vol 13, Issue 8

"Cartwright, Kenneth" <kcartwright@verisign.com> Wed, 09 July 2008 15:27 UTC

Return-Path: <peppermint-bounces@ietf.org>
X-Original-To: peppermint-archive@optimus.ietf.org
Delivered-To: ietfarch-peppermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 22F423A683F; Wed, 9 Jul 2008 08:27:24 -0700 (PDT)
X-Original-To: peppermint@core3.amsl.com
Delivered-To: peppermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CEC153A69AA for <peppermint@core3.amsl.com>; Wed, 9 Jul 2008 08:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aAwElhNlXBsm for <peppermint@core3.amsl.com>; Wed, 9 Jul 2008 08:27:21 -0700 (PDT)
Received: from peregrine.verisign.com (peregrine.verisign.com [216.168.239.74]) by core3.amsl.com (Postfix) with ESMTP id BCBF23A683F for <peppermint@ietf.org>; Wed, 9 Jul 2008 08:27:21 -0700 (PDT)
Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com [10.170.12.139]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id m69FRdNs012396 for <peppermint@ietf.org>; Wed, 9 Jul 2008 11:27:39 -0400
Received: from DUL1WNEXMB05.vcorp.ad.vrsn.com ([10.170.12.240]) by dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 9 Jul 2008 11:27:33 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 09 Jul 2008 11:27:32 -0400
Message-ID: <DC577A902BAC134783E52BE37FCBCCA1023C9F5B@DUL1WNEXMB05.vcorp.ad.vrsn.com>
In-Reply-To: <mailman.3574.1215551639.4989.peppermint@ietf.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: PEPPERMINT Digest, Vol 13, Issue 8
Thread-Index: AcjhP5XCawX84g/eTLqOhrCpbN3GCQAmBPoA
From: "Cartwright, Kenneth" <kcartwright@verisign.com>
To: peppermint@ietf.org
X-OriginalArrivalTime: 09 Jul 2008 15:27:33.0280 (UTC) FILETIME=[4EE3DA00:01C8E1D8]
Subject: Re: [PEPPERMINT] PEPPERMINT Digest, Vol 13, Issue 8
X-BeenThere: peppermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection <peppermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/peppermint>
List-Post: <mailto:peppermint@ietf.org>
List-Help: <mailto:peppermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: peppermint-bounces@ietf.org
Errors-To: peppermint-bounces@ietf.org

Fwiw, I like the term "Destination Group" as one to supplant what ESPP
had labeled as a "Service Area".  And the way that "Destination Group"
is described by Ray tracks with the way that, I believe, ESPP defines
and uses "Service Areas".

Ken 

-----Original Message-----
From: peppermint-bounces@ietf.org [mailto:peppermint-bounces@ietf.org]
On Behalf Of peppermint-request@ietf.org
Sent: Tuesday, July 08, 2008 5:14 PM
To: peppermint@ietf.org
Subject: PEPPERMINT Digest, Vol 13, Issue 8

Send PEPPERMINT mailing list submissions to
	peppermint@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www.ietf.org/mailman/listinfo/peppermint
or, via email, send a message with subject or body 'help' to
	peppermint-request@ietf.org

You can reach the person managing the list at
	peppermint-owner@ietf.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of PEPPERMINT digest..."


Today's Topics:

   1. Re:  Data model for "reachability data"	and
      naming/terminology for group of addresses (Jean-Francois Mule)


----------------------------------------------------------------------

Message: 1
Date: Tue, 8 Jul 2008 15:13:53 -0600
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
Subject: Re: [PEPPERMINT] Data model for "reachability data"	and
	naming/terminology for group of addresses
To: <Ray.Bellis@nominet.org.uk>
Cc: peppermint@ietf.org
Message-ID:
	
<9AAEDF491EF7CA48AB587781B8F5D7C6012900C4@srvxchg3.cablelabs.com>
Content-Type: text/plain;	charset="us-ascii"

Ray,

   Thank you for the comments and sorry for the delay in responding.
More inline.

Jean-Francois.

Ray wrote:
> Can you elaborate on what a "Service Area" / "Address Group"
> actually is?
It is basically a way to logically group user addresses that can be
   - reached via a given Signaling path Border Element (SBE),
   - reached via a domain from which SIP servers can be located (a la
rfc3263)
Folks often picture this by saying it is a group of users reachable via
a common (SIP) 'route'.

> In the UK for our Central Numbering Database we've developed a concept

> of a "Destination Group" - that being all those numbers (or
> destinations)
> which are supposed to be routed identically.  Is that the same thing?
I believe so.  Would folks prefer Destination Group then?


> Note however that this does not mean that every originating carrier 
> has to route them to the same place as every other carrier.
> 
> For example if Carrier A (a terminating carrier) has:
> 
>   DG1 = (a, b)
>   DG2 = (c, d)
> 
> then originating Carrier B routes destinations in DG1 to a particular 
> interconnect, and routes DG2 to some other interconnect.  However 
> Carrier C might have completely different interconnects with Carrier 
> A.
> 
> In the UK model the actual interconnect addresses are private 
> information bilaterally agreed between carriers.
> 
> kind regards,
> 
> Ray



------------------------------

_______________________________________________
PEPPERMINT mailing list
PEPPERMINT@ietf.org
https://www.ietf.org/mailman/listinfo/peppermint


End of PEPPERMINT Digest, Vol 13, Issue 8
*****************************************
_______________________________________________
PEPPERMINT mailing list
PEPPERMINT@ietf.org
https://www.ietf.org/mailman/listinfo/peppermint