Re: draft-ietf-ipv6-ula-central-02.txt

"Stephen Sprunk" <stephen@sprunk.org> Fri, 13 July 2007 16:32 UTC

Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9O4I-00024q-2V; Fri, 13 Jul 2007 12:32:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9O4G-00024k-PE for ipv6@ietf.org; Fri, 13 Jul 2007 12:32:32 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.ygnition.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9O4C-0005v1-Cs for ipv6@ietf.org; Fri, 13 Jul 2007 12:32:32 -0400
Received: from ssprunkxp (ip55.post-vineyard.dfw.ygnition.net [24.219.179.55]) by ns2.ygnition.com (8.13.6/8.13.5) with SMTP id l6DGWPVB008035; Fri, 13 Jul 2007 09:32:27 -0700
Message-ID: <016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
From: Stephen Sprunk <stephen@sprunk.org>
To: Roger Jorgensen <rogerj@jorgensen.no>
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org><467D0806.7030100@spaghetti.zurich.ibm.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com><467FDEAA.1020503@spaghetti.zurich.ibm.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com><467FE693.5060103@spaghetti.zurich.ibm.com> <D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net> <00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com> <Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no>
Date: Fri, 13 Jul 2007 11:16:58 -0500
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: ipv6@ietf.org, roger@jorgensen.no
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
> On Thu, 12 Jul 2007, Stephen Sprunk wrote:
>> This has been a longstanding problem in the IETF; in fact,
>> the inability to agree on what "site" means was one of the
>> reasons SLAs were deprecated.  The word "site" is often
>> abused to mean "administrative domain" rather than "physical location" 
>> due to the ISP-centric nature of the IETF
>> and RIRs. It's virtually impossible to tell, in any particular
>> context, which meaning an author meant.  We need to stop
>> using the word entirely...
>
> why does it mather if it is physical site, administrative domain
> (eh how can anyone interprent that as a site?!) or a room,
> company etc... why not leave that upto those that try to use it?

It matters because there are a lot of protocol and policy documents that 
refer to "sites".  For instance, one of the current qualifications for 
getting an IPv6 LIR allocation require that one have a plan to make 
assignments to 200 "sites".  Obviously the meaning of that is significantly 
changed depending on whether you consider a single company with 200+ 
locations sharing a single uplink to be one "site" or 200+ "sites".

Also, in the case of SLAs, the utility of the addresses is impacted greatly 
by whether you consider a "site" to be a single administrative domain, where 
there would not be internal collisions, vs. considering each distinct 
location to be a "site", which could lead to hundreds or thousands of 
internal collisions.

As far as why "site" has been abused to mean "administrative domain", that 
comes from the IETF and RIRs being very ISP-centric, as I said; a single 
downstream connection denotes a single "site" regardless of how complex the 
internal network behind it is or how many other locations it serves.  Or 
maybe it doesn't, depending on who's talking; that's the problem.

S

Stephen Sprunk      "Those people who think they know everything
CCIE #3723         are a great annoyance to those of us who do."
K5SSS                                             --Isaac Asimov 



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------