RE: Liaison from BBF
"Wes Beebee (wbeebee)" <wbeebee@cisco.com> Mon, 09 November 2009 21:50 UTC
Return-Path: <wbeebee@cisco.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 1E2733A63EB for <ipv6@core3.amsl.com>; Mon, 9 Nov 2009 13:50:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level:
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=0.301, 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 E5zeYLL5a6VQ for <ipv6@core3.amsl.com>; Mon, 9 Nov 2009 13:50:23 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 54CE528C271 for <ipv6@ietf.org>; Mon, 9 Nov 2009 13:49:50 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEABwd+EqrR7Hu/2dsb2JhbADHJ5cuhD4EgWg
X-IronPort-AV: E=Sophos;i="4.44,711,1249257600"; d="scan'208";a="428503962"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-6.cisco.com with ESMTP; 09 Nov 2009 21:50:17 +0000
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id nA9LoFBn029320; Mon, 9 Nov 2009 21:50:16 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 16:50:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Liaison from BBF
Date: Mon, 09 Nov 2009 16:50:15 -0500
Message-ID: <BB56240F3A190F469C52A57138047A03037B0B9C@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <alpine.DEB.1.10.0911091833170.22728@uplift.swm.pp.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Liaison from BBF
Thread-Index: AcphY8coU7aPyIcHSiOYCtrn5ondFQAIY5ag
References: <60C093A41B5E45409A19D42CF7786DFD4DEDE9BC10@EUSAACMS0703.eamcs.ericsson.se><200911091500.nA9F0PSm002116@cichlid.raleigh.ibm.com><alpine.DEB.1.10.0911091623150.22728@uplift.swm.pp.se><B0147C3DD45E42478038FC347CCB65FE16EDA143@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> <alpine.DEB.1.10.0911091833170.22728@uplift.swm.pp.se>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, ipv6@ietf.org
X-OriginalArrivalTime: 09 Nov 2009 21:50:16.0478 (UTC) FILETIME=[9F9BCBE0:01CA6186]
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:50:24 -0000
One common way of setting up a residential gateway is to first set up a PC connected to the ISP, let it get an IPv4 address through DHCPv4, tell the ISP about it and get the MAC address and DHCPv4 lease recorded (and reserved) in the ISP servers (to get it online). Then, the customer hangs up the phone from the ISP and transfers the connection to the PC from behind the modem to behind the residential gateway (on the LAN side). The WAN side of the residential gateway is then connected to the modem of the ISP. However, since the residential gateway no longer has a MAC address that matches the lease recorded in the ISP DHCPv4 server, the user simply clones the MAC address of the PC onto the WAN side of the CPE Router. The residential gateway completes DHCPv4, and everything works fine. The MAC address of the PC and the MAC address of the WAN side interface of the residential gateway are the same. However, this is not a problem as long as the residential gateway either routes traffic or is a NAT box. If the residential gateway is a bridge, this causes all sorts of problems (including the problems listed in the BBF liason). However, if it were a bridge, then you wouldn't have to clone the MAC address in the first place! - Wes -----Original Message----- From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Mikael Abrahamsson Sent: Monday, November 09, 2009 12:40 PM To: ipv6@ietf.org Subject: RE: Liaison from BBF On Mon, 9 Nov 2009, Manfredi, Albert E wrote: > Does not the ISP control, own, and distribute the "residential gateway"? Not in my market anyway (some have this service of course, but it's definitely not mandatory). > Why would ISP not own and control the residential gateway? Because it's cheaper to have the customer walk into their electronics store and buy any CPE they fancy, than to have the ISP handle it. It also gives customers more choice. In some markets, people like to have the choice between ISP provided CPE and one they run themselves. > 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? As far as I can discern, it's standard in the US but not in the rest of the world. Generally, the more competition in the market, the less likely it is that the ISP provides the end user CPE. If customers switch ISPs every year or so, they want to be able to re-use their CPE. -- Mikael Abrahamsson email: swmike@swm.pp.se -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- RE: Liaison from BBF Mikael Abrahamsson
- Liaison from BBF David Allan I
- Re: Liaison from BBF Thomas Narten
- Re: Liaison from BBF Mikael Abrahamsson
- RE: Liaison from BBF Manfredi, Albert E
- RE: Liaison from BBF Mikael Abrahamsson
- RE: Liaison from BBF Manfredi, Albert E
- RE: Liaison from BBF Wes Beebee (wbeebee)
- Re: Liaison from BBF Phil Bedard
- RE: Liaison from BBF Manfredi, Albert E
- RE: Liaison from BBF David Allan I
- RE: Liaison from BBF David Allan I
- RE: Liaison from BBF Hemant Singh (shemant)
- RE: Liaison from BBF David Allan I
- RE: Liaison from BBF Hemant Singh (shemant)
- RE: Liaison from BBF Wojciech Dec (wdec)