Re: [Isis-wg] FW: New Version Notification for draft-ginsberg-isis-rfc4971bis-00.txt
Mach Chen <mach.chen@huawei.com> Fri, 09 October 2015 02:37 UTC
Return-Path: <mach.chen@huawei.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8C931B2AC2 for <isis-wg@ietfa.amsl.com>; Thu, 8 Oct 2015 19:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zOhjq7Mg7cFs for <isis-wg@ietfa.amsl.com>; Thu, 8 Oct 2015 19:37:44 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA0D81B2AC1 for <isis-wg@ietf.org>; Thu, 8 Oct 2015 19:37:43 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BYO00332; Fri, 09 Oct 2015 02:37:42 +0000 (GMT)
Received: from SZXEMA412-HUB.china.huawei.com (10.82.72.71) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 9 Oct 2015 03:37:41 +0100
Received: from SZXEMA510-MBX.china.huawei.com ([169.254.3.229]) by SZXEMA412-HUB.china.huawei.com ([10.82.72.71]) with mapi id 14.03.0235.001; Fri, 9 Oct 2015 10:37:38 +0800
From: Mach Chen <mach.chen@huawei.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Uma Chunduri <uma.chunduri@ericsson.com>, ISIS-WG <isis-wg@ietf.org>
Thread-Topic: [Isis-wg] FW: New Version Notification for draft-ginsberg-isis-rfc4971bis-00.txt
Thread-Index: AQHRAjhN4BlXeyqH6EK89kRhtfj9up5icgWw
Date: Fri, 09 Oct 2015 02:37:37 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28B60C437@SZXEMA510-MBX.china.huawei.com>
References: <20151008035854.31741.17926.idtracker@ietfa.amsl.com> <d0010681b7f64c74b2b8cdc07174bdfd@XCH-ALN-001.cisco.com> <1B502206DFA0C544B7A604691520086351367CB3@eusaamb105.ericsson.se> <054f9ef202e74cad820db9979aac669e@XCH-ALN-001.cisco.com> <1B502206DFA0C544B7A604691520086351368002@eusaamb105.ericsson.se> <ffbdd6d48305432c888ad6d1c17f35a9@XCH-ALN-001.cisco.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28B60C3BF@SZXEMA510-MBX.china.huawei.com> <38ac44f00f354ceeb71bcb6f30163270@XCH-ALN-001.cisco.com>
In-Reply-To: <38ac44f00f354ceeb71bcb6f30163270@XCH-ALN-001.cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.102.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/Wq09adLG_rOdgP009oWN46v8Pq8>
Cc: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
Subject: Re: [Isis-wg] FW: New Version Notification for draft-ginsberg-isis-rfc4971bis-00.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Fri, 09 Oct 2015 02:37:47 -0000
Les, > -----Original Message----- > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Les Ginsberg > (ginsberg) > Sent: Friday, October 09, 2015 10:15 AM > To: Mach Chen; Uma Chunduri; ISIS-WG > Cc: Stefano Previdi (sprevidi) > Subject: Re: [Isis-wg] FW: New Version Notification for > draft-ginsberg-isis-rfc4971bis-00.txt > > Mach - > > Good to know you are there. :-) > > > -----Original Message----- > > From: Mach Chen [mailto:mach.chen@huawei.com] > > Sent: Thursday, October 08, 2015 7:06 PM > > To: Les Ginsberg (ginsberg); Uma Chunduri; ISIS-WG > > Cc: Stefano Previdi (sprevidi) > > Subject: RE: [Isis-wg] FW: New Version Notification for > > draft-ginsberg-isis- rfc4971bis-00.txt > > > > Hi Les, > > > > Thanks for the clear explanation! > > > > > -----Original Message----- > > > From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com] > > > Sent: Friday, October 09, 2015 7:37 AM > > > To: Uma Chunduri; ISIS-WG > > > Cc: Stefano Previdi (sprevidi); Mach Chen > > > Subject: RE: [Isis-wg] FW: New Version Notification for > > > draft-ginsberg-isis-rfc4971bis-00.txt > > > > > > (Not sure why Mach's email address keeps disappearing from the TO > > > list > > > - hopefully he is receiving copies via the WG alias) > > > > Yes, I am watching :-) > > > > > > > > Uma - > > > > > > Mach and I have had some discussions about doing a BIS for RFC 5316 > > > because TLV 141 has a similar issue since its format stipulates a 32 > > > bit router ID. If that were to happen I think that is the best place > > > to clarify the content of sub-TLVs 11/12. > > > What do you think? > > > > > > Note that we don't really have a use case for sub-TLV 11(IPv4 > > > Router > > > ID) since that Router ID can be encoded in the fixed part of TLV 141/242. > > > > Regarding sub-TLV 11, when sent with the 32 bit router ID, it is > > indeed a bit redundant. > > Thinking more about it, there may be a use case that two IPv4 > > networks(ASes) connected by a IPv6 network (AS), for the IPv6 AS, the > > ASBRs support dual stack. To setup an end-to-end IPv4 TE LSP, the > > ASBRs to need to advertise their IPv4 TE Router ID within the domain. > > Is this case valid? > > [Les:] My point is that if you need to "advertise" the IPv4 Router ID you simply > put it in the fixed part of TLV 242 (and/or TLV 141). You don't need to use the > sub-TLV. > If you also want to advertise the IPv6 Router ID in the same TLV you then use > the IPv6 Router ID sub-TLV i.e., nothing in 4971bis prohibits you from sending > IPv6 Router ID sub-TLV when the router id in TLV 242 is a valid IPv4 Router ID > (NOT 0.0.0.0). Indeed. Best regards, Mach > > Les > > > > > Best regards, > > Mach > > > > > > > > Note also that to resolve the TLV 141 issue we need to define the > > > equivalent of TLV242/sub-TLV 12 for TLV 141. > > > > > > Les > > > > > > > > > > > > > -----Original Message----- > > > > From: Uma Chunduri [mailto:uma.chunduri@ericsson.com] > > > > Sent: Thursday, October 08, 2015 4:04 PM > > > > To: Les Ginsberg (ginsberg); ISIS-WG > > > > Cc: Stefano Previdi (sprevidi) > > > > Subject: RE: [Isis-wg] FW: New Version Notification for > > > > draft-ginsberg-isis- rfc4971bis-00.txt > > > > > > > > Les, > > > > > > > > In-line [Uma]: > > > > > > > > -- > > > > Uma C. > > > > > > > > -----Original Message----- > > > > From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com] > > > > Sent: Thursday, October 08, 2015 11:51 AM > > > > To: Uma Chunduri; ISIS-WG > > > > Cc: Stefano Previdi (sprevidi) > > > > Subject: RE: [Isis-wg] FW: New Version Notification for > > > > draft-ginsberg-isis- rfc4971bis-00.txt > > > > > > > > Uma - > > > > > > > > Thanx for the comments. > > > > > > > > If you read RFC 5316 Section 3.2 I think it is clear that the TLV > > > > 242 sub-TLVs defined there are meant to advertise what is in TLVs > > 134/140. > > > > [Uma]: Loosely yes, but it really gets murky if we see 3.3.4 and 3.3.5. > > > > > > > > If you think that RFC 5316 is not explicit enough we can discuss > > > > the best way to clarify that. I am not sure that rfc4971bis is the > > > > best place to do that - but we can certainly discuss. > > > > > > > > [Uma]: It's not that explicit, IMO. I am sure you are thinking of > > > > the implications from 5316 PoV if we make it explicit? > > > > Like v4, it's too good to clarify non-TE situation with IPv6 too. > > > > > > > > Les > > > > > > > > > > > > > -----Original Message----- > > > > > From: Uma Chunduri [mailto:uma.chunduri@ericsson.com] > > > > > Sent: Thursday, October 08, 2015 11:43 AM > > > > > To: Les Ginsberg (ginsberg); ISIS-WG > > > > > Cc: Stefano Previdi (sprevidi) > > > > > Subject: RE: [Isis-wg] FW: New Version Notification for > > > > > draft-ginsberg-isis- rfc4971bis-00.txt > > > > > > > > > > > > > > > In various contexts this hole has been discussed multiple times > > > > > and today we have to have an IPv4 router ID have to be > > > > > configured even for IPv6-only deployments. > > > > > I see the proposed text is a reasonable and perhaps less > > > > > disruptive way to address this . > > > > > > > > > > May be it's good disambiguate further this should be tied to TLV > > > > > 140 (RFC 6119); meaning the sub-TLV 12 (RFC 5316) should be > > > > > matching to TLV 140 if both are present. > > > > > Thoughts? > > > > > -- > > > > > Uma C. > > > > > > > > > > -----Original Message----- > > > > > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Les > > > > > Ginsberg > > > > > (ginsberg) > > > > > Sent: Wednesday, October 07, 2015 9:04 PM > > > > > To: ISIS-WG > > > > > Cc: Stefano Previdi (sprevidi) > > > > > Subject: [Isis-wg] FW: New Version Notification for > > > > > draft-ginsberg-isis- rfc4971bis-00.txt > > > > > > > > > > Folks - > > > > > > > > > > We have just submitted a bis draft for RFC 4971 to define how to > > > > > use TLV 242 on a router which supports only IPv6 (has no IPv4 > > addresses). > > > > > > > > > > The draft is identical to the original RFC except for: > > > > > > > > > > 1)New text at the beginning of Section 3 defining how to use the > > > > > TLV when no IPv4 Router ID is present > > > > > > > > > > 2)References have been updated > > > > > > > > > > Please let us know of any questions or comments. > > > > > > > > > > Les (on behalf of Stefano and Mach) > > > > > > > > > > -----Original Message----- > > > > > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > > > > > Sent: Wednesday, October 07, 2015 8:59 PM > > > > > To: Mach Chen; Stefano Previdi (sprevidi); Les Ginsberg > > > > > (ginsberg); Stefano Previdi (sprevidi); Les Ginsberg (ginsberg); > > > > > Mach Chen > > > > > (Guoyi) > > > > > Subject: New Version Notification for > > > > > draft-ginsberg-isis-rfc4971bis-00.txt > > > > > > > > > > > > > > > A new version of I-D, draft-ginsberg-isis-rfc4971bis-00.txt > > > > > has been successfully submitted by Les Ginsberg and posted to > > > > > the IETF repository. > > > > > > > > > > Name: draft-ginsberg-isis-rfc4971bis > > > > > Revision: 00 > > > > > Title: IS-IS Extensions for Advertising Router Info > > > > > Document date: 2015-10-07 > > > > > Group: Individual Submission > > > > > Pages: 9 > > > > > URL: > > > https://www.ietf.org/internet-drafts/draft-ginsberg-isis- > > > > > rfc4971bis-00.txt > > > > > Status: > > > https://datatracker.ietf.org/doc/draft-ginsberg-isis-rfc4971bis/ > > > > > Htmlized: > > > https://tools.ietf.org/html/draft-ginsberg-isis-rfc4971bis-00 > > > > > > > > > > > > > > > Abstract: > > > > > This document defines a new optional Intermediate System to > > > > > Intermediate System (IS-IS) TLV named CAPABILITY, formed of > > multiple > > > > > sub-TLVs, which allows a router to announce its capabilities within > > > > > an IS-IS level or the entire routing domain. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Please note that it may take a couple of minutes from the time > > > > > of submission until the htmlized version and diff are available > > > > > at > > tools.ietf.org. > > > > > > > > > > The IETF Secretariat > > > > > > > > > > _______________________________________________ > > > > > 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] FW: New Version Notification for draft-… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Tony Przygienda
- Re: [Isis-wg] FW: New Version Notification for dr… Tony Przygienda
- Re: [Isis-wg] FW: New Version Notification for dr… Tony Przygienda
- Re: [Isis-wg] FW: New Version Notification for dr… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Tony Przygienda
- Re: [Isis-wg] FW: New Version Notification for dr… Uma Chunduri
- Re: [Isis-wg] FW: New Version Notification for dr… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Uma Chunduri
- Re: [Isis-wg] FW: New Version Notification for dr… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Mach Chen
- Re: [Isis-wg] FW: New Version Notification for dr… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Mach Chen
- Re: [Isis-wg] FW: New Version Notification for dr… Uma Chunduri
- Re: [Isis-wg] FW: New Version Notification for dr… Xuxiaohu
- Re: [Isis-wg] FW: New Version Notification for dr… Xuxiaohu
- Re: [Isis-wg] FW: New Version Notification for dr… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Xuxiaohu
- Re: [Isis-wg] FW: New Version Notification for dr… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Xuxiaohu
- Re: [Isis-wg] FW: New Version Notification for dr… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Xuxiaohu
- Re: [Isis-wg] FW: New Version Notification for dr… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Xuxiaohu
- Re: [Isis-wg] FW: New Version Notification for dr… Les Ginsberg (ginsberg)
- Re: [Isis-wg] FW: New Version Notification for dr… Xuxiaohu