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

"Stephen Sprunk" <stephen@sprunk.org> Thu, 12 July 2007 18:02 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 1I92zT-0004Vs-Pe; Thu, 12 Jul 2007 14:02:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I92zS-0004Vm-83 for ipv6@ietf.org; Thu, 12 Jul 2007 14:02:10 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net ([65.67.187.82] helo=defiant.dfw.nostrum.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I92zJ-0007AH-P7 for ipv6@ietf.org; Thu, 12 Jul 2007 14:02:10 -0400
Received: from ssprunkxp (localhost [127.0.0.1]) by defiant.dfw.nostrum.com (8.13.8/8.13.8/Debian-3) with SMTP id l6CHwnXl031619; Thu, 12 Jul 2007 12:59:49 -0500
Message-ID: <00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com>
From: Stephen Sprunk <stephen@sprunk.org>
To: michael.dillon@bt.com, ipv6@ietf.org
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>
Date: Thu, 12 Jul 2007 12:41:32 -0500
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
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-Virus-Scanned: ClamAV 0.90.2/3648/Thu Jul 12 11:59:27 2007 on defiant.dfw.nostrum.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc:
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 <michael.dillon@bt.com>
>> A site is a network of computers with a single administration,
>> this can mean indeed a major corporation (who maybe even
>> require multiple /48's which is why rfc4193 is a bit off to cover
>> those cases)
>
> Where has the IETF redefined the meaning of the word "site"?
> In plain English, this word refers to a distinct physical location such
> as an office or building or campus.

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

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