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

"Stephen Sprunk" <stephen@sprunk.org> Sat, 14 July 2007 15:28 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 1I9jXm-0000ed-DG; Sat, 14 Jul 2007 11:28:26 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9jXl-0000eN-2k for ipv6@ietf.org; Sat, 14 Jul 2007 11:28:25 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.ygnition.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9jXV-0003kB-MT for ipv6@ietf.org; Sat, 14 Jul 2007 11:28:25 -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 l6EFRYmj010833; Sat, 14 Jul 2007 08:27:36 -0700
Message-ID: <00a501c7c62b$76a61e00$6401a8c0@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> <016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com> <Pine.LNX.4.64.0707132020150.9923@chandra.student.uit.no>
Date: Sat, 14 Jul 2007 10:18:35 -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.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: ipv6@ietf.org
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 Fri, 13 Jul 2007, Stephen Sprunk wrote:
>> 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.
>
> I can not see how SLAs are any of this wg's business, or ietfs
> businness.  thought SLA was something for the laywers that
> write the contracts governing any SLAs to fight out between
> them?

Site-Local Addresses, the predecessor to Unique Local Addresses.

>> 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.
>
> that downstream connection is ONE site for the upstream
> provider, will probably never be anything else. Why should it
> be anything else really? If the same "site" bought two
> connection to an ISP on different location they would still be
> one huge site, with several internal parts, two that the ISP need to know 
> about.

No, that's one interpretation of the word.  Others (notably the person I was 
responding to) consider every physical location to be a "site" even if a 
large set of locations all share a single internal network and single 
uplink.

> What I'm not sure you realize is that the moment anyone define
> a site to be something very specific... there will come alot of
> exceptions to that list, not to forget discussion on how to
> interprent whats written there.

We already have extensive disagreement on interpretation due to lack of any 
agreed-upon definition.

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
--------------------------------------------------------------------