Re: Consensus call on adopting:draft-krishnan-6man-rs-mark-06.txt

Suresh Krishnan <suresh.krishnan@ericsson.com> Fri, 13 August 2010 20:16 UTC

Return-Path: <suresh.krishnan@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 6B8E23A68F3 for <ipv6@core3.amsl.com>; Fri, 13 Aug 2010 13:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.617
X-Spam-Level:
X-Spam-Status: No, score=-102.617 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ABoB+1lvgrrD for <ipv6@core3.amsl.com>; Fri, 13 Aug 2010 13:15:58 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 7A76C3A6A18 for <ipv6@ietf.org>; Fri, 13 Aug 2010 13:15:57 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id o7DKJns8011358; Fri, 13 Aug 2010 15:19:51 -0500
Received: from [142.133.10.113] (147.117.20.213) by eusaamw0711.eamcs.ericsson.se (147.117.20.179) with Microsoft SMTP Server id 8.2.234.1; Fri, 13 Aug 2010 16:16:27 -0400
Message-ID: <4C65A823.9050704@ericsson.com>
Date: Fri, 13 Aug 2010 16:16:35 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: Re: Consensus call on adopting:draft-krishnan-6man-rs-mark-06.txt
References: <4C61959A.7040805@innovationslab.net> <C88AFA1B.C0E3B%wbeebee@cisco.com> <AF742F21C1FCEE4DAB7F4842ABDC511C025D6531@XMB-RCD-114.cisco.com> <AF742F21C1FCEE4DAB7F4842ABDC511C025D6566@XMB-RCD-114.cisco.com>
In-Reply-To: <AF742F21C1FCEE4DAB7F4842ABDC511C025D6566@XMB-RCD-114.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IPv6 WG Mailing List <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>
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: Fri, 13 Aug 2010 20:16:00 -0000

Hi Hemant,

On 10-08-13 02:19 PM, Hemant Singh (shemant) wrote:
> During the IETF 78, I met Ashok S. Joshi from Alcatel-Lucent who
> appraised me of one key property of the DSL broadband network.  He said,
> our cheap DSL devices in the home have about 3-5% of the devices with
> duplicate mac-addresses. So what the DSL AN does is create a new
> mac-addr per home and then this mac-addr is used to send data from the
> AN to the Internet.  If the DSL AN does such a new mac-addr creation,
> then our suggested tunnel for the RA back terminates at the AN.  The AN
> has enough information to de-multiplex the tunneled RA to the individual
> home. I have cced Ashok in this email to keep me honest. 
> 
> If existing tunneling mechanisms work, why do we need any of the
> draft-gundavelli-v6ops-l2-unicast or this document in the IETF?  If DSL
> folks really want such existing IPv6 mechanisms specified, one could do
> so in the DSL standards bodies.

The mechanism specified in this document requires allocation of a 
destination option and it can be allocated one only through standards 
action. So, while the mechanism has been specified in the BBF specs 
already, the option to be used has not been allocated.

Thanks
Suresh