IETF Logo Mail Archive

RE: Liaison from BBF

David Allan I <david.i.allan@ericsson.com> Mon, 09 November 2009 23:01 UTC

Return-Path: <david.i.allan@ericsson.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 193763A6782 for <ipv6@core3.amsl.com>; Mon, 9 Nov 2009 15:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.44
X-Spam-Level:
X-Spam-Status: No, score=-6.44 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 qqDC5LW-KpSl for <ipv6@core3.amsl.com>; Mon, 9 Nov 2009 15:01:10 -0800 (PST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 3B13B3A6358 for <ipv6@ietf.org>; Mon, 9 Nov 2009 15:01:10 -0800 (PST)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id nA9N1XYL007353; Mon, 9 Nov 2009 17:01:35 -0600
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 17:00:24 -0600
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 17:00:24 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.4]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Mon, 9 Nov 2009 18:00:23 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Date: Mon, 09 Nov 2009 18:00:22 -0500
Subject: RE: Liaison from BBF
Thread-Topic: Liaison from BBF
Thread-Index: AcphW6XlYiZ9jMeZSzSiHHvX2u8UrgAAbw7wAAywrdA=
Message-ID: <60C093A41B5E45409A19D42CF7786DFD4DEDE9C240@EUSAACMS0703.eamcs.ericsson.se>
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>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 09 Nov 2009 23:00:24.0115 (UTC) FILETIME=[6B8E4030:01CA6190]
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 23:01:11 -0000

HI

There are a couple of scenarios to consider..

1) Simple bridging from the home, hence a number of NIC address will appear at the edge router...

2) Retail model for RGs, which is how I bought mine... My modem came from my DSL provider, but as it had no wireless, so I turned off all higher layer functions and front ended it with a Belkin box bought over the counter... 

Hope this helps
D

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Manfredi, Albert E
Sent: Tuesday, November 10, 2009 2:10 AM
To: Mikael Abrahamsson
Cc: ipv6@ietf.org
Subject: RE: Liaison from BBF

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

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?

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?

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

v2.23.0 | Report a Bug | By Email