Re: [Isis-wg] New Layer2 extensions to ISIS - thorough review will be required
John E Drake <jdrake@juniper.net> Sun, 25 April 2010 18:43 UTC
Return-Path: <jdrake@juniper.net>
X-Original-To: isis-wg@core3.amsl.com
Delivered-To: isis-wg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B1BB3A6A63 for <isis-wg@core3.amsl.com>; Sun, 25 Apr 2010 11:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.318
X-Spam-Level:
X-Spam-Status: No, score=-6.318 tagged_above=-999 required=5 tests=[AWL=0.281, 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 A5EaZk5iV6CS for <isis-wg@core3.amsl.com>; Sun, 25 Apr 2010 11:43:56 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by core3.amsl.com (Postfix) with ESMTP id 804393A6A64 for <isis-wg@ietf.org>; Sun, 25 Apr 2010 11:43:51 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKS9SNWVNrqC8ZtX+4V9RYBAkxz0a+0Nbp@postini.com; Sun, 25 Apr 2010 11:43:45 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Sun, 25 Apr 2010 11:43:37 -0700
From: John E Drake <jdrake@juniper.net>
To: John E Drake <jdrake@juniper.net>, David Allan I <david.i.allan@ericsson.com>, David Ward <dward@juniper.net>, isis-wg <isis-wg@ietf.org>
Date: Sun, 25 Apr 2010 11:43:34 -0700
Thread-Topic: [Isis-wg] New Layer2 extensions to ISIS - thorough review will be required
Thread-Index: AcrjCpFI/xK+V3+XRmKiuuE0umjLQgAv4CtwACe/tYAACbPwIA==
Message-ID: <5E893DB832F57341992548CDBB333163980F89BBF4@EMBX01-HQ.jnpr.net>
References: <E5AACC79-7A9A-4315-86DF-8E27268EA20D@juniper.net> <60C093A41B5E45409A19D42CF7786DFD4F9969AE14@EUSAACMS0703.eamcs.ericsson.se> <5E893DB832F57341992548CDBB333163980F89BBCE@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB333163980F89BBCE@EMBX01-HQ.jnpr.net>
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
Cc: Christian Hopps <chopps@rawdofmt.org>, Adrian Farrel <Adrian.Farrel@huawei.com>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Isis-wg] New Layer2 extensions to ISIS - thorough review will be required
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Apr 2010 18:43:57 -0000
Hi, In particular, it appears that OTV is out of scope wrt the current charter. Also, no one likes proprietary extensions more than I do, but they should have their own document and codepoints. Thanks, John > -----Original Message----- > From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On Behalf > Of John E Drake > Sent: Sunday, April 25, 2010 4:19 AM > To: David Allan I; David Ward; isis-wg > Cc: Christian Hopps; Adrian Farrel; Ralph Droms > Subject: Re: [Isis-wg] New Layer2 extensions to ISIS - thorough review > will be required > > +1 > > > -----Original Message----- > > From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On > Behalf > > Of David Allan I > > Sent: Saturday, April 24, 2010 9:31 AM > > To: David Ward; isis-wg > > Cc: Christian Hopps; Adrian Farrel; Ralph Droms > > Subject: Re: [Isis-wg] New Layer2 extensions to ISIS - thorough review > > will be required > > > > Hi Folks: > > > > While the decision of splitting the drafts is in discussion (and that is > a > > direction I favor as the scope of IS-IS changes is radically different > and > > disjoint between the "layer 2"s), the question needs to be asked "what > in > > the draft survives the split as WG items". > > > > 802.1aq - yes > > TRILL - yes > > OTV - does not belong here, it is proprietary... > > > > If OTV is standardized it COULD be considered by the WG at some point in > > the future. Right now it is simply an wholly inappropriate complication > in > > addressing the two technologies the WG has agreed to... > > > > It should be removed from the draft and a new version published ASAP. > > > > My 2 cents > > D > > > > -----Original Message----- > > From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On > Behalf > > Of David Ward > > Sent: Friday, April 23, 2010 1:30 PM > > To: isis-wg > > Cc: Christian Hopps; Ralph Droms; Jari Arkko; Adrian Farrel > > Subject: [Isis-wg] New Layer2 extensions to ISIS - thorough review will > be > > required > > > > All - > > > > The WG Chairs would like to be clear on the approach to review and > > progression of the draft: draft-ietf-isis-layer2. There will be a > request > > for the routing directorate, specific guest reviewers and a lengthy > > community review. There will also be a requirement of multiple, > > interoperable implementations. Whether we split the draft into TRILL, > .aq, > > OTV extensions into separate drafts or not, the foundational changes to > > ISIS for each of the technologies will need to be proven working and > > correct. > > > > The draft itself will need to be cleaned up and clear what PDUs, TLVs, > etc > > are necessary for any of this technology which will make reading and > > implementation awareness easier. If we decide to split them (we will > > decide later - please remain calm and not discuss this nit now- let's > get > > the information completed as we know it); it will be quite trivial. If > we > > decide not to; it will be clear to the reader/implementor. > > > > The purpose of such a process is because in several decades of the > > existence of ISIS and extremely wide deployment, no new PDU types were > > ever deemed necessary. The new TLVs being proposed and the data being > > carried has never been carried before and may cause new scaling, > > performance or other impacts that we don't currently understand. We need > > to fully understand the impact of these changes and learn what we don't > > know about the changes we are proposing. I've found in my experience > that > > new protocols, new technologies and fundamental changes to protocols > > require a deep understanding and implementation experience and not a > rush > > to RFC. Headsup > > > > Thanks. > > > > -DWard, CHopps > > > > _______________________________________________ > > Isis-wg mailing list > > Isis-wg@ietf.org > > https://www.ietf.org/mailman/listinfo/isis-wg > > _______________________________________________ > > Isis-wg mailing list > > Isis-wg@ietf.org > > https://www.ietf.org/mailman/listinfo/isis-wg > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg
- [Isis-wg] New Layer2 extensions to ISIS - thoroug… David Ward
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… David Allan I
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… John E Drake
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… Paul Unbehagen
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… John E Drake
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… Peter Ashwood-Smith
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… David Ward
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… Fedyk, Donald (Don)
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… Stewart Bryant
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… Paul Unbehagen
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… Peter Ashwood-Smith
- Re: [Isis-wg] New Layer2 extensions to ISIS - tho… David Michael Bond