IETF Logo Mail Archive

Re: [Lsr] WG adoption call for draft-acee-lsr-ospf-admin-tags-07

Aijun Wang <wangaijun@tsinghua.org.cn> Thu, 07 January 2021 02:15 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 C46DC3A0FF5; Wed, 6 Jan 2021 18:15:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 c5eoZRGov8WG; Wed, 6 Jan 2021 18:15:20 -0800 (PST)
Received: from mail-m17638.qiye.163.com (mail-m17638.qiye.163.com [59.111.176.38]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBAA23A02BB; Wed, 6 Jan 2021 18:15:19 -0800 (PST)
Received: from DESKTOP2IOH5QC (unknown [219.142.69.75]) by mail-m17638.qiye.163.com (Hmail) with ESMTPA id B62981C0210; Thu, 7 Jan 2021 10:15:16 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: "'Acee Lindem (acee)'" <acee=40cisco.com@dmarc.ietf.org>, "'Peter Psenak (ppsenak)'" <ppsenak@cisco.com>, lsr@ietf.org
Cc: lsr-chairs@ietf.org
References: <FD4C69FA-CBDF-4D04-86ED-897A53C4EA0A@chopps.org>
In-Reply-To: <FD4C69FA-CBDF-4D04-86ED-897A53C4EA0A@chopps.org>
Date: Thu, 07 Jan 2021 10:15:15 +0800
Message-ID: <009201d6e49a$f0372290$d0a567b0$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHMkrqcHU9d2GGanXscKI1iDtM6r6owC4fw
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgYFAkeWUFZS1VLWVdZKFlBSkxLS0o3V1ktWUFJV1 kPCRoVCBIfWUFZSktMTUlLHx4aGEJMVkpNS0JCQ05MSk1CTE5VEwETFhoSFyQUDg9ZV1kWGg8SFR 0UWUFZT0tIVUpKS09ISFVLWQY+
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6MBg6TAw5Sj8NCAgjTT4VHi0q NChPCTdVSlVKTUtCQkNOTEpMSEhMVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxOWVdZCAFZQUlIQk43Bg++
X-HM-Tid: 0a76daa0729ad993kuwsb62981c0210
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/DyEe7Hq8tWqlBct_OLPR1ibYcQw>
Subject: Re: [Lsr] WG adoption call for draft-acee-lsr-ospf-admin-tags-07
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: Thu, 07 Jan 2021 02:15:23 -0000

Hi, Acee and Peter:

https://tools.ietf.org/html/rfc8362#section-3.12 has defined the Route-Tag
Sub-TLV for External-Prefix, is it more straightforward to extend this
sub-TLV to be included in other Prefix TLVs(Inter-Area-Prefix TLV,
Intra-Area-Prefix TLV) to accomplish the aimed application scenario?
And, do we need to cover multiple tag scenario? Even for external prefix,
only one Route-Tag will be processed.

Anyway, I support its adoption.


Best Regards

Aijun Wang
China Telecom

-----Original Message-----
From: lsr-bounces@ietf.org <lsr-bounces@ietf.org> On Behalf Of Christian
Hopps
Sent: Tuesday, January 5, 2021 5:17 PM
To: lsr@ietf.org
Cc: lsr-chairs@ietf.org; Christian Hopps <chopps@chopps.org>
Subject: [Lsr] WG adoption call for draft-acee-lsr-ospf-admin-tags-07

This begins a 2 week WG adoption call for the following draft:

  https://datatracker.ietf.org/doc/draft-acee-lsr-ospf-admin-tags/

Please indicate your support or objection by January 19th, 2021.

Authors, please respond to the list indicating whether you are aware of any
IPR that applies to this draft.

Thanks,
Chris.

v2.23.0 | Report a Bug | By Email