[RAI] Global Service Provider ID - draft-pfautz-service-provider-identifier-urn-01

"PFAUTZ, PENN L" <pp3129@att.com> Fri, 23 September 2011 14:59 UTC

Return-Path: <pp3129@att.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 447E121F8C90 for <rai@ietfa.amsl.com>; Fri, 23 Sep 2011 07:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.802
X-Spam-Level:
X-Spam-Status: No, score=-104.802 tagged_above=-999 required=5 tests=[AWL=1.795, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWNHwxQbRkyD for <rai@ietfa.amsl.com>; Fri, 23 Sep 2011 07:59:41 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id 1652321F8C8C for <rai@ietf.org>; Fri, 23 Sep 2011 07:59:40 -0700 (PDT)
X-Env-Sender: pp3129@att.com
X-Msg-Ref: server-11.tower-119.messagelabs.com!1316790133!40772207!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.3.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 4334 invoked from network); 23 Sep 2011 15:02:13 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-11.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Sep 2011 15:02:13 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p8NF2eb6026510 for <rai@ietf.org>; Fri, 23 Sep 2011 11:02:40 -0400
Received: from MISOUT7MSGHUB9B.ITServices.sbc.com (misout7msghub9b.itservices.sbc.com [144.151.223.72]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p8NF2WR3026275 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rai@ietf.org>; Fri, 23 Sep 2011 11:02:35 -0400
Received: from MISOUT7MSGUSR9N.ITServices.sbc.com ([169.254.5.157]) by MISOUT7MSGHUB9B.ITServices.sbc.com ([144.151.223.72]) with mapi id 14.01.0289.001; Fri, 23 Sep 2011 11:02:05 -0400
From: "PFAUTZ, PENN L" <pp3129@att.com>
To: "rai@ietf.org" <rai@ietf.org>
Thread-Topic: Global Service Provider ID - draft-pfautz-service-provider-identifier-urn-01
Thread-Index: Acx6AcDeNS0NeSsqR7m50XF38KY7vg==
Date: Fri, 23 Sep 2011 15:02:04 +0000
Message-ID: <38726EDA2109264987B45E29E758C4D6022778@MISOUT7MSGUSR9N.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.91.160.51]
Content-Type: multipart/alternative; boundary="_000_38726EDA2109264987B45E29E758C4D6022778MISOUT7MSGUSR9NIT_"
MIME-Version: 1.0
Subject: [RAI] Global Service Provider ID - draft-pfautz-service-provider-identifier-urn-01
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Sep 2011 14:59:43 -0000

Following up on the discussion in dispatch at IETF 81 (www.ietf.org/proceedings/81/minutes/dispatch.txt<http://www.ietf.org/proceedings/81/minutes/dispatch.txt>) I'd like to get some discussion of   draft-pfautz-service-provider-identifier-urn-01 going.
The draft proposed IANA registration of a service provider ID (SPID) which would have the following characteristics:
-      Numeric ID, at least 8 digits long
-      Fixed length
-      Available to any type of entity
-      Entities able to obtain multiple identifiers.
-       Some range of identifiers reserved for internal usage
-      Open registration by IANA

The minutes concluded:

-      WG is in support of creating a URN for this.
-      Document(s) likely to be AD sponsored.
-      Discussion should move to RAI area list (as opposed to DRINKS or DISPATCH).

The outstanding issues seemed to be
1. Is a new resource assignment necessary for the URN or could an existing one, Private Enterprise Numbers or ITADs be used with a URN defined to provide a fixed length parameter as requested in the I-D?

2. Assuming a fixed length parameter will be used, what's the right length?

The I-D proposed a new resource, partly because the existing ones were intended for other purposes and already had many registrations. I'd also note that PENs suggest a sub-delegation approach to assigning multiple SPIDs to an entity (an entity gets one PEN assignment and can assign values hierarchically below that (e.g. AT&T has PEN 74, and would assign 74.1, 74.2, etc). Because at least some of the service providers wanted to use SPID to prefix E.164 numbers and others want to incorporate SPID in a domain name, this would present issues.


Penn Pfautz
AT&T Access Management
+1-732-420-4962