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

Peter Psenak <ppsenak@cisco.com> Tue, 09 August 2022 12:31 UTC

Return-Path: <ppsenak@cisco.com>
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 DA0C6C159488; Tue, 9 Aug 2022 05:31:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.189
X-Spam-Level:
X-Spam-Status: No, score=-10.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.582, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 1SmB4do-YjD9; Tue, 9 Aug 2022 05:31:56 -0700 (PDT)
Received: from aer-iport-7.cisco.com (aer-iport-7.cisco.com [173.38.203.69]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D94EC159486; Tue, 9 Aug 2022 05:31:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3014; q=dns/txt; s=iport; t=1660048316; x=1661257916; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=k7wMJ60XNVkb2Sh3Fny2+10wAk329z1H2uhgKWhozoE=; b=k+tZ3DsupvX4iTsD+JRxumaSCaxGRvVuJfC6cOl7pfNCA/rT941t0I+S Yc7FFpd+/9WVEML2+GwRqruo4TSqP0OXiB8dlaFeNfm4Xzw+RaVvawDHH bHVZoHW9Q+pDIJZ4G/Y5ElcBBKgmOQaHOnPh0JNCm8+3FPphLRYfV62oY c=;
X-IronPort-AV: E=Sophos;i="5.93,224,1654560000"; d="scan'208";a="781696"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Aug 2022 12:31:53 +0000
Received: from [10.209.203.121] ([10.209.203.121]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTP id 279CVqV3012236; Tue, 9 Aug 2022 12:31:53 GMT
Message-ID: <b8c52a5b-4118-7a78-0e52-9a11957e6a58@cisco.com>
Date: Tue, 09 Aug 2022 14:31:52 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: Aijun Wang <wangaijun@tsinghua.org.cn>, "Acee Lindem (acee)" <acee@cisco.com>
Cc: Christian Hopps <chopps@chopps.org>, lsr@ietf.org, lsr-chairs@ietf.org, lsr-ads@ietf.org
References: <F0BF7FCB-5CFE-40DF-B374-6EEA3D172F8E@cisco.com> <5138395B-A1AD-4EA2-BAE1-F5CD448C11D0@tsinghua.org.cn>
From: Peter Psenak <ppsenak@cisco.com>
In-Reply-To: <5138395B-A1AD-4EA2-BAE1-F5CD448C11D0@tsinghua.org.cn>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.209.203.121, [10.209.203.121]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/MMveR2SMYpKI7j0lLPqntOnj-ME>
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 12:31:59 -0000

Aijun,

RFC8919 and RFC8920 are both existing RFCs, we are just adding some 
clarification text to them.

If you want to come up with some new architecture, feel free, but don't 
try to neglect the existing ones.

thanks,
Peter



On 09/08/2022 08:26, Aijun Wang wrote:
> Hi, Acee, Peter:
> 
> If there is no significant updates for these two RFCs, I recommend we delay the obsolete of them, also the adoption call for these two bis drafts.
> What we should do is to find other more scalable, extensible and systematic approaches for the application specified advertisements.
> 
> For example, for the multiple application scenarios, is it enough just define the application specified attributes?
> 
>>From my understandings, different applications may build different LSDBs, run different SPF algorithm, update at different frequencies, forming different forwarding tables etc. It is necessary to divide/group all the above items based on application, not just the attributes.
> 
> 
> Aijun Wang
> China Telecom
> 
>> On Aug 9, 2022, at 18:31, Acee Lindem (acee) <acee@cisco.com> wrote:
>>
>> Hi Aijun,
>>
>> And the BIS changes are more clarifications than changes to the existing RFC 8919 and RFC 8920 RFCs.
>>
>> Thanks,
>> Acee
>>
>> On 8/9/22, 5:57 AM, "Peter Psenak" <ppsenak@cisco.com> wrote:
>>
>>     Aijun,
>>
>>>     On 09/08/2022 05:35, Aijun Wang wrote:
>>> 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?
>>
>>     sure there are deployments of it. Flex-algo is built around RFC8919, so
>>     any network where flex-algo is used with ISIS is using RFC8919.
>>
>>     Peter
>>
>>>
>>> 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.
>>>
>>> _______________________________________________
>>> Lsr mailing list
>>> Lsr@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lsr
>>>
>>
>>
> 
>