1 / 6

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

Global Service Provider ID draft-pfautz-service-provider-identifier-urn-01. Penn Pfautz ppfautz@att.com. IETF 81, July 2011, Quebec , Canada Dispatch WG. Background. Interest in a globally unique service provider identifier in several industry bodies i 3 Forum – Global SPID

garan
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Global Service Provider IDdraft-pfautz-service-provider-identifier-urn-01 Penn Pfautz ppfautz@att.com IETF 81, July 2011, Quebec , Canada Dispatch WG

  2. Background • Interest in a globally unique service provider identifier in several industry bodies • i3 Forum – Global SPID http://i3forum.org/sites/default/files/i3_Global_SPID_Specifications_Release_1_may_2011.pdf • Identify serving provider of an E.164 number for least cost routing • Direct URI routing not appropriate • Seek open registration – support for non-traditional carriers • GSMA - IR.67 proposed Service Provider Number, TBD by ITU-T, as substitute for E.212 assignments for non-mobile carriers • ITU-T correspondence group on SPN • Little progress • support for non-traditional registrants unclear • Needs from other bodies: • Drinks • SIP Forum?

  3. Need for Convergence –wouldn’t it be nice… • Desirable to have one globally unique identifier • i3 members initially looked to ITU, consistent with GMSA IR.67 • Prospects in ITU are dim

  4. Proposal for Specification in IETF • 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 URN:SPID:<8>DIGIT ; could be something other than “SPID” DIGIT=%30-39

  5. Alternatives • Private Enterprise Numbers (used in SNMP MIB, RFC 2578) • Part of OID hierarchy: iso.org.dod.internet.private.enterprise 1.3.6.1.4.1 • Not specifically fixed length (issue re use in prefixing) • Use sub-delegation rather than explicitly allowing multiple assignments to an entity or general reserved allocation for internal use • ITADs (RFC 3219 – TRIP protocol) • ITAD numbers in the range 1-255 are designated for Private Use • ITAD numbers in the range from 256 to (2**32)-1 are allocated by IANA on a First-Come-First-Serve basis. (not specifically fixed length) • Multiple allocation per entity?

  6. Discussion, please • Thanks!

More Related