Re: [Isis-wg] I-D Action:draft-ietf-isis-layer2-05.txt

Hasmit Grover <hasmit@cisco.com> Wed, 05 May 2010 04:01 UTC

Return-Path: <hasmit@cisco.com>
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 3D41D3A67D6 for <isis-wg@core3.amsl.com>; Tue, 4 May 2010 21:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 ZDHvS708zLcf for <isis-wg@core3.amsl.com>; Tue, 4 May 2010 21:01:44 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id ECEAF3A63EB for <isis-wg@ietf.org>; Tue, 4 May 2010 21:01:43 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.52,330,1270425600"; d="scan'208";a="192633406"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 05 May 2010 04:01:30 +0000
Received: from sjc-vpn5-1232.cisco.com (sjc-vpn5-1232.cisco.com [10.21.92.208]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o4541TIk010903; Wed, 5 May 2010 04:01:30 GMT
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: Hasmit Grover <hasmit@cisco.com>
In-Reply-To: <000f01caec07$451523e0$108a2f0a@china.huawei.com>
Date: Tue, 04 May 2010 21:01:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B9960C2-5078-41A4-8F1F-634D2B42D769@cisco.com>
References: <000f01caec07$451523e0$108a2f0a@china.huawei.com>
To: Peter Ashwood-Smith <Peter.AshwoodSmith@huawei.com>
X-Mailer: Apple Mail (2.1078)
Cc: isis-wg@ietf.org
Subject: Re: [Isis-wg] I-D Action:draft-ietf-isis-layer2-05.txt
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: Wed, 05 May 2010 04:01:45 -0000

I am not proposing that we should not debate OTV TLVs and question their existence. We are open to any questions and concerns regarding the OTV TLV.

-Hasmit

On May 4, 2010, at 8:58 PM, Peter Ashwood-Smith wrote:

> The reason we all go to standards bodies is to contribute/debate/participate
> in the evolution of the Internet.
> 
> I've been able to debate/participate openly with the Trill folks over the
> last few years, they publish minutes, have an email list, regular meetings
> etc. etc.
> 
> I've been able to debate openly with the IEEE 802.1aq folks over the last
> few years, minutes, email lists, regular meetings etc.
> 
> Please explain to me where and when I've had the opportunity to debate OTV
> and why that is not a problem?
> 
> Peter
> 
> -----Original Message-----
> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On Behalf
> Of Hasmit Grover
> Sent: Tuesday, May 04, 2010 11:17 PM
> To: Fedyk, Donald (Don)
> Cc: isis-wg@ietf.org
> Subject: Re: [Isis-wg] I-D Action:draft-ietf-isis-layer2-05.txt
> 
> 
> Donald,
> 
> As per draft-ietf-isis-layer it's intent is to capture the IS-IS extensions
> used by protocols running over L2. Like other protocols mentioned in the
> draft, OTV is also an L2 protocol which is using some of the TLVs mentioned
> in the draft. It is really important that all the IS-IS TLV codepoints are
> captured in a single document so that different implementations can inter-op
> with each other. 
> 
> -Hasmit
> 
> On May 4, 2010, at 7:11 PM, Fedyk, Donald (Don) wrote:
> 
>> Hi Dhananjaya
>> 
>> It is rather unprecedented to have material published in a WG document
> before it is in an individual draft and there is a consensus to add it. 
>> 
>> So for the changes for OTV they really should go in an individual draft
> and be discussed on their own merits.  
>> 
>> Do you and your authors agree? 
>> 
>> Don 
>> 
>> 
>> -----Original Message-----
>> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On Behalf
> Of Dhananjaya Rao (dhrao)
>> Sent: Tuesday, May 04, 2010 6:45 PM
>> To: isis-wg@ietf.org
>> Subject: Re: [Isis-wg] I-D Action:draft-ietf-isis-layer2-05.txt
>> 
>> 
>> 
>> Hi folks,
>> 
>> We're just catching up on the discussions on the mailing list regarding
> the L2 IS-IS draft-ietf-isis-layer2-04.txt. As the authors of OTV, we'd like
> to clarify any doubts or concerns regarding the extensions used by OTV.
>> 
>> Briefly, OTV uses the L2 IS-IS extensions being defined to provide a
> solution for interconnecting datacenter networks. An I-D describing the
> solution has been recently published at
> http://tools.ietf.org/html/draft-hasmit-otv-00.
>> 
>> OTV shares along with TRILL/802.1aq several of the PDU/TLVs that have been
> defined in this draft. There are of course a few additional sub-TLVs defined
> specifically for OTV:
>> 
>> - A couple of hello extensions to advertise L2 site membership and
>> capabilities.
>> - A group membership sub-TLV to advertise multicast source information.
>> 
>> The solution is already being deployed in several enterprise networks and
> a final product with this solution is shipping soon. Given the multiple
> technologies using L2 IS-IS, we'd like to ensure the extensions and
> codepoints are published in a common document to aid interoperable
> implementations.
>> 
>> Please let us know if you have any questions.
>> 
>> Thanks,
>> -Dhananjaya (for the authors)
>> 
>> 
>>> 
>>> A New Internet-Draft is available from the on-line Internet-Drafts 
>>> directories.
>>> This draft is a work item of the IS-IS for IP Internets Working Group 
>>> of the IETF.
>>> 
>>> 
>>> 	Title           : Extensions to IS-IS for Layer-2 Systems
>>> 	Author(s)       : A. Banerjee, et al.
>>> 	Filename        : draft-ietf-isis-layer2-05.txt
>>> 	Pages           : 60
>>> 	Date            : 2010-04-30
>>> 
>>> This document specifies the IS-IS extensions necessary to support 
>>> multi-link IPv4 and IPv6 networks, as well as to provide true link 
>>> state routing to any protocols running directly over layer 2.  While 
>>> supporting this concept involves several pieces, this document only 
>>> describes extensions to IS-IS.  We leave it to the systems using these 
>>> IS-IS extensions to explain how the information carried in IS-IS is 
>>> used.
>>> 
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ietf-isis-layer2-05.txt
>>> 
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>> 
>>> Below is the data which will enable a MIME compliant mail reader 
>>> implementation to automatically retrieve the ASCII version of the 
>>> Internet-Draft.
>>> 
>>> <ftp://ftp.ietf.org/internet-drafts/draft-ietf-isis-layer2-05.txt>
>> _______________________________________________
>> 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
>