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

"PFAUTZ, PENN L" <pp3129@att.com> Mon, 26 September 2011 17:51 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 072A811E80D8 for <rai@ietfa.amsl.com>; Mon, 26 Sep 2011 10:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.24
X-Spam-Level:
X-Spam-Status: No, score=-106.24 tagged_above=-999 required=5 tests=[AWL=0.360, BAYES_00=-2.599, 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 SiovEkKR0iKc for <rai@ietfa.amsl.com>; Mon, 26 Sep 2011 10:51:07 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id 3A92D11E80CD for <rai@ietf.org>; Mon, 26 Sep 2011 10:51:06 -0700 (PDT)
X-Env-Sender: pp3129@att.com
X-Msg-Ref: server-3.tower-119.messagelabs.com!1317059628!41256247!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.3.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21679 invoked from network); 26 Sep 2011 17:53:48 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-3.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Sep 2011 17:53:48 -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 p8QHsFiC018317; Mon, 26 Sep 2011 13:54:15 -0400
Received: from MISOUT7MSGHUB9C.ITServices.sbc.com (misout7msghub9c.itservices.sbc.com [144.151.223.82]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p8QHsCI6018261 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 26 Sep 2011 13:54:12 -0400
Received: from MISOUT7MSGUSR9N.ITServices.sbc.com ([169.254.5.157]) by MISOUT7MSGHUB9C.ITServices.sbc.com ([144.151.223.82]) with mapi id 14.01.0289.001; Mon, 26 Sep 2011 13:53:44 -0400
From: "PFAUTZ, PENN L" <pp3129@att.com>
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>, "Worley, Dale R (Dale)" <dworley@avaya.com>, Hadriel Kaplan <HKaplan@acmepacket.com>
Thread-Topic: [RAI] Global Service Provider ID - draft-pfautz-service-provider-identifier-urn-01
Thread-Index: Acx6AcDeNS0NeSsqR7m50XF38KY7vgAY41iAAIe6+gD//9vjgP///yyQ
Date: Mon, 26 Sep 2011 17:53:43 +0000
Message-ID: <38726EDA2109264987B45E29E758C4D6022C0F@MISOUT7MSGUSR9N.ITServices.sbc.com>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F590A@DC-US1MBEX4.global.avaya.com> <CAA62EE0.3B275%jason_livingood@cable.comcast.com>
In-Reply-To: <CAA62EE0.3B275%jason_livingood@cable.comcast.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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rai@ietf.org" <rai@ietf.org>
Subject: Re: [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: Mon, 26 Sep 2011 17:51:08 -0000

Jason:
Because of the issues alluded to, of finding you've locked someone out you'd like to be in, we were inclined *not* to set up specific qualifications.
So although the focus was service providers, it clearly went beyond ITU recognized operating authorities or even US OCN-eligible parties.
I understand the concern about being too short but not the basis for 10 digits (10 billion) not being enough as the thinking was entities, not end points or individuals in general. ITADs at 2**32-1 will top out below 10B. I'm not sure there's a direct limit on PENs in terms of OID syntax but I'm guessing SNMP implementations might constrain it to the same range as ITADs.

I remain concerned about being too big because of the desire of some parties to do prefixing with them or to incorporate into domain name frames.


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

-----Original Message-----
From: Livingood, Jason [mailto:Jason_Livingood@cable.comcast.com]
Sent: Monday, September 26, 2011 1:32 PM
To: Worley, Dale R (Dale); Hadriel Kaplan; PFAUTZ, PENN L
Cc: rai@ietf.org
Subject: Re: [RAI] Global Service Provider ID - draft-pfautz-service-provider-identifier-urn-01

Along these lines, who qualifies for a SPID? Could it be a small business
with their own SIP proxy / softswitch? If so, a 10-digit-length registry
will be wholly insufficient.


Jason

On 9/26/11 11:41 AM, "Worley, Dale R (Dale)" <dworley@avaya.com> wrote:

>> From: Hadriel Kaplan [HKaplan@acmepacket.com]
>>
>> So I asked some people about why ITAD wasn't what they wanted to use
>> for SPIDs, and they said exactly what you said above:
>>
>> > because the existing ones were intended for other purposes and
>> > already had many registrations
>>
>> It's the latter part (that they already have many registrations) that
>> I think is really why people don't want to use ITADs, and that's what
>> worries me in a weird way... because it implies they think some new
>> SPID registry won't be populated with junk.  It will be.
>
>I think there are two overlapping flavors of this distaste.  One is
>the symbolism of membership in a registry.  There is going to be a
>visceral desire that the registry is "for service providers, but not
>limited to traditional telephony".  However, if there are enough
>identifiers that we don't risk running out, it really doesn't matter
>who or what is allowed into the registry.
>
>The other flavor is what Hadriel says, "we don't want the registry
>filled with junk".  But the reality, the *meta-design principle*, is
>that if you have a system that can actually keep the junk out, you
>will also be keeping out something you want to let in.
>
>Dale
>_______________________________________________
>RAI mailing list
>RAI@ietf.org
>https://www.ietf.org/mailman/listinfo/rai