AW: Consensus call on adopting <draft-krishnan-6man-rs-mark-08.txt>

<Olaf.Bonness@telekom.de> Fri, 29 October 2010 10:48 UTC

Return-Path: <Olaf.Bonness@telekom.de>
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 A90BA3A6849 for <ipv6@core3.amsl.com>; Fri, 29 Oct 2010 03:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
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 KHK2ov5xK+Bf for <ipv6@core3.amsl.com>; Fri, 29 Oct 2010 03:48:32 -0700 (PDT)
Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by core3.amsl.com (Postfix) with ESMTP id 65F0A3A6810 for <ipv6@ietf.org>; Fri, 29 Oct 2010 03:48:31 -0700 (PDT)
Received: from s4de9jsaano.mgb.telekom.de (HELO S4DE9JSAANO.ost.t-com.de) ([10.125.177.105]) by tcmail81.telekom.de with ESMTP; 29 Oct 2010 12:50:10 +0200
Received: from S4DE9JSAACX.ost.t-com.de ([10.125.177.232]) by S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Oct 2010 12:50:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: Consensus call on adopting <draft-krishnan-6man-rs-mark-08.txt>
Date: Fri, 29 Oct 2010 12:50:06 +0200
Message-ID: <8A34913DF3402341B6E0AF5FD0E8BBA70801BB54@S4DE9JSAACX.ost.t-com.de>
In-Reply-To: <4C3E5140-689D-4B3C-88BE-24BFF8B5374C@employees.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Consensus call on adopting <draft-krishnan-6man-rs-mark-08.txt>
Thread-Index: Act3Q/suNTGhlBi8QvmlN405prWpiwAEiGrQ
References: <3F7E0126-76FB-43BA-B25F-1EE226FA73AA@gmail.com><CCEDE07D-AA1E-477F-A014-0CDDB46873F5@employees.org><4CC9C9EC.6020608@ericsson.com><60C093A41B5E45409A19D42CF7786DFD51CB328D0E@EUSAACMS0703.eamcs.ericsson.se> <4C3E5140-689D-4B3C-88BE-24BFF8B5374C@employees.org>
From: Olaf.Bonness@telekom.de
To: otroan@employees.org, david.i.allan@ericsson.com
X-OriginalArrivalTime: 29 Oct 2010 10:50:09.0634 (UTC) FILETIME=[0E528420:01CB7757]
Cc: ipv6@ietf.org, brian@innovationslab.net, bob.hinden@gmail.com, suresh.krishnan@ericsson.com
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, 29 Oct 2010 10:48:33 -0000

I appreciate the decision of the WG chairs to accept the I-D as v6ops working item since it reflects the majority of the raised opinions and acknowledges the need for a solution to make IPv6 happen in a very special, but nevertheless often implemented, network scenario. 

Kind regards
Olaf 
 

> -----Ursprüngliche Nachricht-----
> Von: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] Im 
> Auftrag von Ole Troan
> Gesendet: Freitag, 29. Oktober 2010 10:33
> An: David Allan I
> Cc: Bob Hinden; Brian Haberman; IPv6 WG Mailing List; Suresh Krishnan
> Betreff: Re: Consensus call on adopting 
> <draft-krishnan-6man-rs-mark-08.txt>
> 
> David,
> 
> good point indeed.
> 
> perhaps it is time for the IETF to acknowledge the fact that 
> these link types are common and to take a more architectural 
> and wide approach to solving and adapting its protocols to 
> this subnet model.
> 
> I'm concerned that we are standardising point solutions 
> without understanding the problem. and I disagree with the 
> chairs consensus call. (not that I necessarily think there 
> are alternatives, but I'd like to see a big warning banner 
> somewhere, not just a "we need to fix a few nits before last 
> calling it).
> 
> cheers,
> Ole
> 
> 
> On Oct 28, 2010, at 23:58 , David Allan I wrote:
> 
> > A quick comment on the soapbox statement...
> > 
> > <soapbox statement>: I'm biased against this subnet model 
> (N:1)... recreating PPP functionality over Ethernet, trying 
> to create user isolation on a shared IPv6 link, which after 
> all IPv6 protocols are not designed for.
> > 
> > I appreciate the IETF has been kind of blind to this but 
> this kind of asymmetric Ethernet subnet is actually much more 
> prevalent and been around longer than you might think. In 
> Metro Ethernet Forum terms it is known as an E-TREE, support 
> for which is being discussed by the IETF L2VPN WG. IEEE 
> 802.1ad(2005?) documents one possible means of implementing 
> this in the form of Asymmetric VID (which I think is also 
> known as private VLAN) and this has been carried forward into 
> 802.1ah PBB/.1aq SPB. 
> > 
> > There is also physical media that behaves like this in the 
> form of passive optical networks, which are p2p to the root 
> and broadcast to the leaves. GPON and EPON becoming a very 
> prevalent broadband deployment model.... 
> > 
> > BBF TR101(2006) is simply one instantiation of a useful 
> construct that has been around for years...and if anything 
> will become much more common over time...
> > 
> > Cheers
> > Dave
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>