Re: [PEPPERMINT] Data model for "reachability data" and naming/terminology for group of addresses

Ray.Bellis@nominet.org.uk Thu, 26 June 2008 14:49 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 3440D3A69C1; Thu, 26 Jun 2008 07:49:00 -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 ABDE13A69C1 for <peppermint@core3.amsl.com>; Thu, 26 Jun 2008 07:48:59 -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 YdLjML9JBV6p for <peppermint@core3.amsl.com>; Thu, 26 Jun 2008 07:48:58 -0700 (PDT)
Received: from mx3.nominet.org.uk (mx3.nominet.org.uk [213.248.199.23]) by core3.amsl.com (Postfix) with ESMTP id 6077128C126 for <peppermint@ietf.org>; Thu, 26 Jun 2008 07:48:54 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:In-Reply-To:References:To:Cc: Subject:MIME-Version:X-Mailer:Message-ID:From:Date: X-MIMETrack:Content-Type; b=A1753dfrTqroZJ/WqptXjYFotiR2i167Z2iiVNeGEVjdaBSpueny1Clq bIImVKwbMRHMYMpwJ71QT6fPSssUILx1LOHztK5Oz1DXzm3NSDXaDSigR zqA07gDKH11LjYN;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1214491739; x=1246027739; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray.Bellis@nominet.org.uk|Subject:=20Re:=20[PEPP ERMINT]=20Data=20model=20for=20"reachability=20data"=20an d=09naming/terminology=0D=0A=20for=20group=20of=20address es|Date:=20Thu,=2026=20Jun=202008=2015:48:55=20+0100 |Message-ID:=20<OF70AE4588.D4FC8E58-ON80257474.00506742-8 0257474.00516285@nominet.org.uk>|To:=20"Jean-Francois=20M ule"=20<jf.mule@cablelabs.com>|Cc:=20peppermint@ietf.org |MIME-Version:=201.0|In-Reply-To:=20<9AAEDF491EF7CA48AB58 7781B8F5D7C601216A72@srvxchg3.cablelabs.com>|References: =20<9AAEDF491EF7CA48AB587781B8F5D7C601216A72@srvxchg3.cab lelabs.com>; bh=fKYOGVCCmng2NlxGh76aDeQi2eBHWqKoSVhJOGvKOgA=; b=Zp8x0sKOH0gUVWcwBjXZnd3ie/HxYMEtr8UvWo1tx/qwkvBKigwt/7JB sIWG4KrkdUC47dNxhkVHeMgWCZMBeq1wTvMGfH84q8MtaMSZpWorJuQMS 4FSExvlVYMxzaxm;
X-IronPort-AV: E=Sophos;i="4.27,708,1204502400"; d="scan'208";a="3853642"
Received: from notes1.nominet.org.uk ([213.248.197.128]) by mx3.nominet.org.uk with ESMTP; 26 Jun 2008 15:48:57 +0100
In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C601216A72@srvxchg3.cablelabs.com>
References: <9AAEDF491EF7CA48AB587781B8F5D7C601216A72@srvxchg3.cablelabs.com>
To: Jean-Francois Mule <jf.mule@cablelabs.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Build VMac_Beta85_20080115_MM2 January 15, 2008
Message-ID: <OF70AE4588.D4FC8E58-ON80257474.00506742-80257474.00516285@nominet.org.uk>
From: Ray.Bellis@nominet.org.uk
Date: Thu, 26 Jun 2008 15:48:55 +0100
X-MIMETrack: Serialize by Router on notes1/Nominet(Release 7.0.1FP1 | May 25, 2006) at 26/06/2008 03:48:56 PM, Serialize complete at 26/06/2008 03:48:56 PM
Cc: peppermint@ietf.org
Subject: Re: [PEPPERMINT] Data model for "reachability data" and naming/terminology for group of addresses
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

> We're updating the draft to integrate comments received from the list
> and fix a few issues we found.
> 1) We're changing LRNs (US, PSTN centric to Penn and Otmar's point) to
> use prefix.
> David et al. have chosen prefix in their problem statement draft and
> this describes something that's close to LRNs, yet more generally
> applicable.
> 2) We're also renaming "Service Areas" to "AddressGroup" for a lack of a
> better term

Jean-Francois,

Can you elaborate on what a "Service Area" / "Address Group" actually is?

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?

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