IETF Logo Mail Archive

[Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv

"Aijun Wang" <wangaijun@tsinghua.org.cn> Fri, 03 January 2020 02:31 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 978F112006B; Thu, 2 Jan 2020 18:31:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 wCekfy5TdzPf; Thu, 2 Jan 2020 18:31:00 -0800 (PST)
Received: from m176115.mail.qiye.163.com (m176115.mail.qiye.163.com [59.111.176.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40ACF12004D; Thu, 2 Jan 2020 18:30:59 -0800 (PST)
Received: from WangajPC (unknown [219.142.69.77]) by m176115.mail.qiye.163.com (Hmail) with ESMTPA id 55ECD661E4E; Fri, 3 Jan 2020 10:30:52 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Christian Hopps' <chopps@chopps.org>, lsr@ietf.org
Cc: lsr-ads@ietf.org, 'Antoni Przygienda' <prz@juniper.net>
References: <4CBA5DF1-E8E2-4370-9602-871FADAB1F9A@chopps.org>
In-Reply-To: <4CBA5DF1-E8E2-4370-9602-871FADAB1F9A@chopps.org>
Date: Fri, 03 Jan 2020 10:30:51 +0800
Message-ID: <004901d5c1dd$d2fda8b0$78f8fa10$@org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdXBn9hKpzguXNp1QUO/6BU7poderQANpp+g
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgYFAkeWUFZS1VOQ09LS0tKSktNSU1JSUpZV1koWU FKTEtLSjdXWS1ZQUlXWQkOFx4IWUFZNTQpNjo3JCkuNz5ZBg++
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6MiI6Gjo4Tjg5ISMWGlZIHFY0 IhIKCTdVSlVKTkxDS0pDTU5MTkxCVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxMWVdZCAFZQUlNSkM3Bg++
X-HM-Tid: 0a6f693dc13b9373kuws55ecd661e4e
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/-B9bcUO29Mb4GQeXxtlcbQQS8UY>
Subject: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2020 02:31:03 -0000

Is there any method to indicate or negotiate the support of
ISO10589/RFC5304/RFC6233 because they are not back compatible?
What will be the consequence when not all of the routers within the IGP
domain support the same RFC?
Will it valuable to add more clarification for the above incompatible
scenario, instead of saying "... ... therefore can only be safely enabled
when all nodes support the extensions"?


Best Regards.

Aijun Wang
China Telecom

-----邮件原件-----
发件人: lsr-bounces@ietf.org [mailto:lsr-bounces@ietf.org] 代表 Christian
Hopps
发送时间: 2020年1月3日 3:07
收件人: lsr@ietf.org
抄送: lsr-ads@ietf.org; Christian Hopps; Antoni Przygienda
主题: [Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

This begins a 2 week WG Last Call, ending after Jan 16th, 2020, for
draft-ietf-lsr-isis-invalid-tlv.

  https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-invalid-tlv/

Tony P (other authors already responded during the adoption poll), please
indicate your knowledge of any IPR related to this work to the list as well.

Thanks,
Chris & Acee.

_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

v2.23.0 | Report a Bug | By Email