IETF Logo Mail Archive

Re: [Lsr] WG adoption call for draft-ginsberg-lsr-rfc8919bis-02

Aijun Wang <wangaijun@tsinghua.org.cn> Tue, 09 August 2022 09:35 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 496DEC15A722; Tue, 9 Aug 2022 02:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RpBALSKLEJLg; Tue, 9 Aug 2022 02:35:13 -0700 (PDT)
Received: from mail-m121145.qiye.163.com (mail-m121145.qiye.163.com [115.236.121.145]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68E3AC1594A9; Tue, 9 Aug 2022 02:35:11 -0700 (PDT)
Received: from DESKTOP2IOH5QC (unknown [219.142.69.75]) by mail-m121145.qiye.163.com (Hmail) with ESMTPA id 8FB2480006E; Tue, 9 Aug 2022 17:35:09 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Christian Hopps' <chopps@chopps.org>, lsr@ietf.org
Cc: lsr-chairs@ietf.org, lsr-ads@ietf.org
References: <m2bksvvxx8.fsf@ja.int.chopps.org>
In-Reply-To: <m2bksvvxx8.fsf@ja.int.chopps.org>
Date: Tue, 09 Aug 2022 17:35:08 +0800
Message-ID: <001501d8abd3$50f03bc0$f2d0b340$@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: AQI3/hPRO9oR1pKKl84lgBqzTO86saznpwXg
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFKTEtLSjdXWS1ZQUlXWQ8JGhUIEh9ZQVlDGUMYVkNOT0kdSR5JSkpLTVUTARMWGhIXJB QOD1lXWRgSC1lBWUlKQlVKT0lVTUJVTE5ZV1kWGg8SFR0UWUFZT0tIVUpKS0hOT1VLWQY+
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6Ny46KBw5LT0xGS4WHjwhPjNN QxkaCjhVSlVKTU1LS0hMTEpLSkhMVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxOWVdZCAFZQUlJSkg3Bg++
X-HM-Tid: 0a8281f53fb6b03akuuu8fb2480006e
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/bVfiguo0SCzBf6QNufQ4vwWCnXk>
Subject: Re: [Lsr] WG adoption call for draft-ginsberg-lsr-rfc8919bis-02
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 09 Aug 2022 09:35:17 -0000

Hi, 

I am wondering why we are so hurry to obsolete RFC8919, given that only the
minor parts are  updated (mainly the zero length SABM/UABM, and other
interoperability issues).
There may be other methods to advertise the application specific attributes.
>From my POV, the rules, implementation of ASLA are still complex, the
deployment of them are challenging. 

Is there any real deployment for RFC8919 until now?

Best Regards

Aijun Wang
China Telecom

-----Original Message-----
From: lsr-bounces@ietf.org <lsr-bounces@ietf.org> On Behalf Of Christian
Hopps
Sent: Monday, August 8, 2022 6:17 PM
To: lsr@ietf.org
Cc: chopps@chopps.org; lsr-chairs@ietf.org; lsr-ads@ietf.org
Subject: [Lsr] WG adoption call for draft-ginsberg-lsr-rfc8919bis-02


Hi Folks,

This begins a 2 week WG Adoption Call for the following draft:

  https://datatracker.ietf.org/doc/draft-ginsberg-lsr-rfc8919bis/

Please indicate your support or objections by August 22nd, 2022.

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

Thanks,
Chris.

v2.23.0 | Report a Bug | By Email