Re: Liaison from BBF

Phil Bedard <bedard.phil@gmail.com> Mon, 09 November 2009 21:55 UTC

Return-Path: <bedard.phil@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F90B3A6BB6 for <ipv6@core3.amsl.com>; Mon, 9 Nov 2009 13:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H+q9BsrdpgT0 for <ipv6@core3.amsl.com>; Mon, 9 Nov 2009 13:55:53 -0800 (PST)
Received: from mail-yw0-f183.google.com (mail-yw0-f183.google.com [209.85.211.183]) by core3.amsl.com (Postfix) with ESMTP id 8E7943A6BB1 for <ipv6@ietf.org>; Mon, 9 Nov 2009 13:55:53 -0800 (PST)
Received: by ywh13 with SMTP id 13so3721025ywh.29 for <ipv6@ietf.org>; Mon, 09 Nov 2009 13:56:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:in-reply-to :mime-version:content-type:message-id:content-transfer-encoding:cc :from:subject:date:to:x-mailer; bh=MbCNYzABrRMScOAJv/BcZ07+wDNPR2gXhxJrOJZZ7u4=; b=W7ofv/pxrL5AfZGecuUQf5WQveU4z++z+AHN6Vwd236ttchs8BiMlZQ7o/QyH+06Zv pGS5NcZK4uIV5S2j7e7IKXfZc0Acg/6fMj/TZB3yAFClRgEY+inSApBSC0gAOSBuqsgL g7g9QHM294WnTWQyp9oBDRm0iiuM5IMz6ODXc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=v0kFjHB8cQrhonH7nuSTra73w6dqgRh/x2QnDyiAyYYmELh4m/GEi8yQmU3HBaTw+K bHIzn+Ja7owWQwlB6Jcbzp9Xqxpd1DpcXiMNQ8hXtSzoc7m122ul/p9QgFcQLAXM0ExF l/OgrQ0fZ6FSazU4hrSo/GUZgGX4qkOy4ZAwI=
Received: by 10.101.136.29 with SMTP id o29mr868009ann.1.1257803775291; Mon, 09 Nov 2009 13:56:15 -0800 (PST)
Received: from ?192.168.1.106? ([96.32.84.32]) by mx.google.com with ESMTPS id 8sm40047yxg.60.2009.11.09.13.56.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 09 Nov 2009 13:56:14 -0800 (PST)
References: <60C093A41B5E45409A19D42CF7786DFD4DEDE9BC10@EUSAACMS0703.eamcs.e ricsson.se><200911091500.nA9F0PSm002116@cichlid.raleigh.ibm.com> <alpine.DEB.1.10.0911091623150.22728@uplift.swm.pp.se><B0147C3DD45E42478038 FC347CCB65FE16EDA143@XCH-MW-08V.mw.nos.boeing.com> <alpine.DEB.1.10.0911091739460.22728@uplift.swm.pp.se> <B0147C3DD45E42478038FC347CCB65FE16EDA1DD@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE16EDA1DD@XCH-MW-08V.mw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
Message-Id: <F8BAB134-59FC-4CFD-BF2E-5121A355A3F0@gmail.com>
Content-Transfer-Encoding: 7bit
From: Phil Bedard <bedard.phil@gmail.com>
Subject: Re: Liaison from BBF
Date: Mon, 09 Nov 2009 16:56:11 -0500
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
X-Mailer: Apple Mail (2.1076)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2009 21:55:54 -0000

Answers inline

On Nov 9, 2009, at 12:09 PM, Manfredi, Albert E wrote:

>> -----Original Message-----
>> From: Mikael Abrahamsson [mailto:swmike@swm.pp.se]
>
> Here is the crux of my not understanding the problem:
>
>> And no, I haven't seen any residential rollout
>> plan where
>> IPv6 would be provisioned in the static way you describe,
>> DHCPv6-PD seems
>> to be the most popular method seen in discussion.
>
> Does not the ISP control, own, and distribute the "residential  
> gateway"? If yes, then the DHCP conducted within the broadcast  
> domain part of the network, i.e. the "last mile" part *outside*  
> customer premises, should be able to ensure uniqueness of the EUI  
> and consequently the IPv6 address of each residential gateway WAN  
> side, no? So that DHCP or whatever method of assigning IPv6 WAN side  
> addresses should be safe.
>

Traditionally, they don't.  Some providers can provide a gateway but  
it's far cheaper to go to your local electronics store and get a home  
router with wireless than to "rent" one from a service provider.   
You'll find a SP-provided gateway more often with business services  
than residential services.


> For that matter, one could use the client identifier option, and the  
> ISP could hard-code the client ID in each of their residential  
> gateways, before distributing these to customer premises.
>
> Why would ISP not own and control the residential gateway?
>

The just don't.


> We received our ADSL "modem" in the mail, from Verizon. It is a NAT,  
> and the WAN side is under their control entirely. Is this not  
> standard practice among ISPs?
>

Not for most ISPs in the US.  I would say the Verizon example is more  
the exception than the rule.  I've only ever used my own store-bought  
gateway.  For most cable providers in the US you don't even need to  
use their provided modem, you can bring your own and use it.


Phil