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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 16 July 2007 07:53 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 1IALOl-0002FP-Qj; Mon, 16 Jul 2007 03:53:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IALOk-0002FE-9X for ipv6@ietf.org; Mon, 16 Jul 2007 03:53:38 -0400
Received: from ug-out-1314.google.com ([66.249.92.169]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IALOf-0001cu-V3 for ipv6@ietf.org; Mon, 16 Jul 2007 03:53:38 -0400
Received: by ug-out-1314.google.com with SMTP id u2so2578462uge for <ipv6@ietf.org>; Mon, 16 Jul 2007 00:53:33 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=CUoXUhV23zdCa/1rIZ3Wjrss8J9JeCtRi0DlVlurXWmhFPA65yAKdeLOUNeiOlJFeliLfMyc9CPZCkSwLSHPPf4ZypxwjEtiRE4oQ3fJ3LplNblUD0M/nhCJo8nFfUEFw6k2HGvc/NQ5v0ayTm28zdFK+GITe/UN661zZH24TI8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=lfg0TMzTZ+B3oYfSCrhuwLyZH15LMRlh9neRQcv/Wb2GazpZKupkeOJ3qTGMfU7zGskt50pNSd5IH/+Ff3Uhv1HWY7xZ8QoMDiULtHUqsYROwmcX46xRHlH/3n3ZBSw8W9S4DANtO4dFDj0BOC3U9vEcFPL9e3RV7lRYs5UHz5k=
Received: by 10.86.70.8 with SMTP id s8mr3353405fga.1184572413280; Mon, 16 Jul 2007 00:53:33 -0700 (PDT)
Received: from ?10.10.50.3? ( [213.3.13.1]) by mx.google.com with ESMTP id 31sm26235519nfu.2007.07.16.00.53.31 (version=SSLv3 cipher=RC4-MD5); Mon, 16 Jul 2007 00:53:32 -0700 (PDT)
Message-ID: <469B23FA.5010301@gmail.com>
Date: Mon, 16 Jul 2007 09:53:30 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: 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> <00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com> <Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no> <016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
In-Reply-To: <016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
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

On 2007-07-13 18:16, Stephen Sprunk wrote:
...
> 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.

I think another reason we've often expanded the meaning of 'site' is
because the IETF has never come to grips with the fact that most
multi-site companies (in the geographical sense) have intranets that
interconnect those sites and are multiply connected to the Internet.
Since we don't have an IETF term for such topologies, apart from AS,
we confuse ourselves.

On 2007-07-13 21:28, michael.dillon@bt.com wrote:
...
> I think it is important for the IETF to have clear documentation of the
> interconnectedness of "sites", /48 prefixes, mobility, and freedom of
> choice.

We should certainly provide technology that allows freedom of choice,
but the IETF can't do more than that.

> 
> At least one RIR now allows ISPs to assign shorter /56 prefixes to
> consumer sites, i.e. family homes and apartments. This is not
> necessarily a bad thing since it is rare for a family home to turn into
> an office without significant infrastructure change. But if there is to
> be a special size for the family home, it too should be the same
> worldwide. And it too should be documented by the IETF.

Actually the IAB tried (RFC 3177) and the RIRs chose another
approach, which is where /56 comes from.

     Brian

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