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

"Livingood, Jason" <Jason_Livingood@cable.comcast.com> Tue, 27 September 2011 17:35 UTC

Return-Path: <jason_livingood@cable.comcast.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 F289E21F8E97 for <rai@ietfa.amsl.com>; Tue, 27 Sep 2011 10:35:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.968
X-Spam-Level:
X-Spam-Status: No, score=-101.968 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, 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 ow5yJvi9CDVd for <rai@ietfa.amsl.com>; Tue, 27 Sep 2011 10:35:25 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfa.amsl.com (Postfix) with ESMTP id 6B6DF21F8E74 for <rai@ietf.org>; Tue, 27 Sep 2011 10:35:25 -0700 (PDT)
Received: from ([24.40.55.40]) by copdcimo01.cable.comcast.com with ESMTP id 5503630.54681770; Tue, 27 Sep 2011 11:44:47 -0600
Received: from PACDCEXMB06.cable.comcast.com ([fe80::6134:ea50:286a:c0]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%11]) with mapi id 14.01.0289.001; Tue, 27 Sep 2011 13:38:07 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: Dean Willis <dean.willis@softarmor.com>, "rai@ietf.org" <rai@ietf.org>
Thread-Topic: [RAI] Global Service Provider ID - draft-pfautz-service-provider-identifier-urn-01
Thread-Index: AQHMfTw3nJHAdSIvOkmjtjzxEJNMNQ==
Date: Tue, 27 Sep 2011 17:38:06 +0000
Message-ID: <CAA78216.3B564%jason_livingood@cable.comcast.com>
In-Reply-To: <4E820778.1070807@softarmor.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [147.191.227.152]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2AF82A9B2CD8694EB2DD236C31348743@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 27 Sep 2011 17:35:26 -0000

>On the other hand, perhaps we're being wildly optimistic about the
>importance of the SPID and the future demand for them.
>
>One might also note that 32 bits is a nice fixed-length number in binary
>(32 digits), quaternary (16 digits), or hexadecimal (8 digits). Why are
>we restricting ourselves to 10 decimal digits, which doesn't map to
>anything binary in a very nice way?

+1
Machines are going to process this stuff in practice anyway, so we needn't
worry that these #s are too long to remember or whatever. Also, now that I
am in the midst of IPv6 deployment I tend to be of the opinion that a
bigger initial address space is better. This is especially the case as
we're not exactly storage or processing constrained in key systems that
would be used.

Feel free to override this one opinion. I just don't want to be on a panel
discussion in 10+ years talking about why we choose such a small SPID
length. ;-)

Jason