Re: [e2md] Problem statement, Requirements and Use Cases
"PFAUTZ, PENN L (ATTCORP)" <pp3129@att.com> Wed, 19 May 2010 16:45 UTC
Return-Path: <pp3129@att.com>
X-Original-To: e2md@core3.amsl.com
Delivered-To: e2md@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8944B3A6847 for <e2md@core3.amsl.com>; Wed, 19 May 2010 09:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.336
X-Spam-Level:
X-Spam-Status: No, score=-104.336 tagged_above=-999 required=5 tests=[AWL=-0.337, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 LVsmwCsDCcrG for <e2md@core3.amsl.com>; Wed, 19 May 2010 09:45:23 -0700 (PDT)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id A556B3A6818 for <e2md@ietf.org>; Wed, 19 May 2010 09:45:23 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: pp3129@att.com
X-Msg-Ref: server-11.tower-129.messagelabs.com!1274287515!14712346!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 15119 invoked from network); 19 May 2010 16:45:16 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-11.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 May 2010 16:45:16 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o4JGivGi017195 for <e2md@ietf.org>; Wed, 19 May 2010 12:44:57 -0400
Received: from gaalpa1msgusr7a.ugd.att.com (gaalpa1msgusr7a.ugd.att.com [135.53.26.15]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o4JGipPe017096 for <e2md@ietf.org>; Wed, 19 May 2010 12:44:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 May 2010 12:45:10 -0400
Message-ID: <35FE871E2B085542A35726420E29DA6B0401450B@gaalpa1msgusr7a.ugd.att.com>
In-Reply-To: <4BF40919.9000907@netmagic.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [e2md] Problem statement, Requirements and Use Cases
Thread-Index: Acr3a0BZG8yLIclLRaCzOX53GUtXzwABkaUA
References: <alpine.DEB.2.00.1005161433580.31324@softronics.hoeneisen.ch><32FCCBEC-E8B1-45D9-A068-0B120AAADC55@rfc1035.com> <alpine.DEB.2.00.1005171404110.16091@softronics.hoeneisen.ch> <35FE871E2B085542A35726420E29DA6B040143F4@gaalpa1msgusr7a.ugd.att.com> <4BF40919.9000907@netmagic.com>
From: "PFAUTZ, PENN L (ATTCORP)" <pp3129@att.com>
To: trutkowski@netmagic.com
Cc: "E.164 To MetaData BOF discussion list" <e2md@ietf.org>
Subject: Re: [e2md] Problem statement, Requirements and Use Cases
X-BeenThere: e2md@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "E.164 To MetaData \(E2MD\) BOF discussion list" <e2md.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/e2md>, <mailto:e2md-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/e2md>
List-Post: <mailto:e2md@ietf.org>
List-Help: <mailto:e2md-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/e2md>, <mailto:e2md-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2010 16:45:24 -0000
Tony: This is an area that will need more discussion which I hope will ensue, if not necessarily under e2md then in the IETF, ITU, i3 and national SDOs. At least some bodies are looking for a single integer (SPN), e.g. the value under the OID 1.3.6.1.4 arc, for AT&T 74. There have also been some requests to support hierarchy subtending an SPN. Penn Pfautz AT&T Access Management +1-732-420-4962 -----Original Message----- From: Tony Rutkowski [mailto:trutkowski@netmagic.com] Sent: Wednesday, May 19, 2010 11:52 AM To: PFAUTZ, PENN L (ATTCORP) Cc: E.164 To MetaData BOF discussion list Subject: Re: [e2md] Problem statement, Requirements and Use Cases On 5/19/2010 11:03 AM, PFAUTZ, PENN L (ATTCORP) wrote: > Use RFC 3761 technology provide for the Carrier of Record for an E.164 > number (as defined in RFC 5067) to publish the mapping of > that E.164 to a globally defined identifier, specifically an IANA > Enterprise Number as defined in RFC 2578. > Hi Penn, Good choice. However, the text needs tweaking to read: Use RFC 3761 technology to provide for the Carrier of Record for an E.164 number (as defined in RFC 5067) to publish the mapping of that E.164 number using an assigned Carrier of Record Object Identifier (OID)) such as an IANA Enterprise Number as defined in RFC 2578. Ref. Rec. ITU-T Recs. X.660 and X.680. The changes clarify what identifier is being specified and includes reference to the authoritative OID standard. It also allows for the possibility of using other assigned OIDs for a Carrier of Record. Although more than 35,000 Enterprise Numbers have been registered with IANA, there are many carriers who have OIDs that were registered with national authorities for Carrier of Record purposes. As long as there is a valid, globally unique OID, some flexibility should exist. For example, ATT has the OID 1.3.6.1.4.74 from IANA's OID block, but it also has 0.7.7223 that it uses for some services in Argentina. best, tony
- [e2md] RFC 5507 & RFC 5395 Bernie Hoeneisen
- Re: [e2md] RFC 5507 & RFC 5395 Jim Reid
- [e2md] Problem statement, Requirements and Use Ca… Bernie Hoeneisen
- Re: [e2md] Problem statement, Requirements and Us… PFAUTZ, PENN L (ATTCORP)
- Re: [e2md] Problem statement, Requirements and Us… Ray Bellis
- Re: [e2md] Problem statement, Requirements and Us… Dean Willis
- Re: [e2md] Problem statement, Requirements and Us… PFAUTZ, PENN L (ATTCORP)
- [e2md] the RFC5935 process Jim Reid
- Re: [e2md] Problem statement, Requirements and Us… Dean Willis
- Re: [e2md] the RFC5935 process Ray Bellis
- Re: [e2md] Problem statement, Requirements and Us… Cartwright, Kenneth
- Re: [e2md] Problem statement, Requirements and Us… Richard Shockey
- [e2md] Problem statement, Requirements and Use Ca… PFAUTZ, PENN L (ATTCORP)
- Re: [e2md] Problem statement, Requirements and Us… Tony Rutkowski
- Re: [e2md] Problem statement, Requirements and Us… PFAUTZ, PENN L (ATTCORP)
- Re: [e2md] Problem statement, Requirements and Us… Tony Rutkowski
- Re: [e2md] Problem statement, Requirements and Us… Cartwright, Kenneth
- Re: [e2md] Problem statement, Requirements and Us… Cartwright, Kenneth
- Re: [e2md] Problem statement, Requirements and Us… Tony Rutkowski
- Re: [e2md] Problem statement, Requirements and Us… PFAUTZ, PENN L (ATTCORP)
- Re: [e2md] Problem statement, Requirements and Us… Tony Rutkowski
- Re: [e2md] Problem statement, Requirements and Us… Sumanth Channabasappa
- Re: [e2md] Problem statement, Requirements and Us… Richard Shockey
- Re: [e2md] Problem statement, Requirements and Us… Cartwright, Kenneth
- [e2md] Shall we go this way? (was Re: Problem sta… Bernie Hoeneisen
- Re: [e2md] Shall we go this way? (was Re: Problem… Dave CROCKER