[Lsr] FW: New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-06.txt

Aijun Wang <wangaj3@chinatelecom.cn> Fri, 26 March 2021 06:42 UTC

Return-Path: <wangaj3@chinatelecom.cn>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id BD0843A1296; Thu, 25 Mar 2021 23:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id PcDW2C69WgsR; Thu, 25 Mar 2021 23:42:38 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn []) by ietfa.amsl.com (Postfix) with ESMTP id 54C5C3A129A; Thu, 25 Mar 2021 23:42:37 -0700 (PDT)
Received: from clientip- (unknown []) by chinatelecom.cn (HERMES) with SMTP id 9295C2800AE; Fri, 26 Mar 2021 14:42:34 +0800 (CST)
X-189-SAVE-TO-SEND: 66040164@chinatelecom.cn
Received: from ([]) by App0024 with ESMTP id 674285bc072f44a88f561dbd22e9fb8c for acee@cisco.com; Fri Mar 26 14:42:37 2021
X-Transaction-ID: 674285bc072f44a88f561dbd22e9fb8c
X-filter-score: filter<0>
X-Real-From: wangaj3@chinatelecom.cn
X-MEDUSA-Status: 0
Sender: wangaj3@chinatelecom.cn
From: "Aijun Wang" <wangaj3@chinatelecom.cn>
To: <acee@cisco.com>
Cc: <lsr@ietf.org>, <lsr-chairs@ietf.org>, "'draft-wang-lsr-prefix-unreachable-annoucement'" <draft-wang-lsr-prefix-unreachable-annoucement@ietf.org>
References: <161673969916.24245.12406819614373253433@ietfa.amsl.com>
In-Reply-To: <161673969916.24245.12406819614373253433@ietfa.amsl.com>
Date: Fri, 26 Mar 2021 14:42:28 +0800
Message-ID: <00a501d7220b$33127030$99375090$@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQK3n0pr5iwDcUdhqUN/AESrGv/rfKjU0htg
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/z-KxYl73yKvlZXF5FCQrRbtd3-8>
Subject: [Lsr] FW: New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-06.txt
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, 26 Mar 2021 06:42:43 -0000

Hi, Acee :

We have uploaded the updated version of the PUA draft( https://datatracker.ietf.org/doc/html/draft-wang-lsr-prefix-unreachable-annoucement) and think it addressed the issues that discussed on the LSR mailing list.
After presenting this idea several times on the IETF meetings, and discussed also several rounds on the mailing list, we think it is time to begin the WG adoption call on this idea.
Alternate solutions to the scenarios described in this draft are also welcome.

The update for this draft is mainly in section 7 "Deployment Considerations", which describes the following information:
1. Which node should be upgraded to support the PUA to accomplish the task.(ABRs and related PEs need to support this features.)
2. How to limit the advertisement of unnecessary PUA message?(ABR can configure the protected prefixes)
3. How long the PUA message will be advertised?(Last for a configurable period to allow the service on the failed prefixes switchover)
4. Will PUA announce for the non-used inactive prefixes within the summary range?(No, ABR will only advertise the PUA message when the prefix status is changed from active to down) 

Are the above updates addresses your concerns for this draft? 
If so, we would like to ask for the WG adoption call. If not, would you like to raise it within the mailing list, and we will try to address them to forward this draft.

Thanks in advance.

Best Regards

Aijun Wang
China Telecom

> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> Sent: Friday, March 26, 2021 2:22 PM
> To: Aijun Wang <wangaj3@chinatelecom.cn>cn>; Gyan Mishra
> <gyan.s.mishra@verizon.com>om>; Yaqun Xiao <xiaoyaqun@huawei.com>om>; Zhibo
> Hu <huzhibo@huawei.com>
> Subject: New Version Notification for
> draft-wang-lsr-prefix-unreachable-annoucement-06.txt
> A new version of I-D, draft-wang-lsr-prefix-unreachable-annoucement-06.txt
> has been successfully submitted by Aijun Wang and posted to the IETF
> repository.
> Name:		draft-wang-lsr-prefix-unreachable-annoucement
> Revision:	06
> Title:		Prefix Unreachable Announcement
> Document date:	2021-03-26
> Group:		Individual Submission
> Pages:		9
> URL:
> https://www.ietf.org/archive/id/draft-wang-lsr-prefix-unreachable-annouceme
> nt-06.txt
> Status:
> https://datatracker.ietf.org/doc/draft-wang-lsr-prefix-unreachable-annouceme
> nt/
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-wang-lsr-prefix-unreachable-annou
> cement
> Htmlized:
> https://tools.ietf.org/html/draft-wang-lsr-prefix-unreachable-annoucement-06
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-wang-lsr-prefix-unreachable-annoucem
> ent-06
> Abstract:
>    This document describes a mechanism to solve an existing issue with
>    Longest Prefix Match (LPM), that exists where an operator domain is
>    divided into multiple areas or levels where summarization is
>    utilized.  This draft addresses a fail-over issue related to a multi
>    areas or levels domain, where a link or node down event occurs
>    resulting in an LPM component prefix being omitted from the FIB
>    resulting in black hole sink of routing and connectivity loss.  This
>    draft introduces a new control plane convergence signaling mechanism
>    using a negative prefix called Prefix Unreachable Announcement (PUA),
>    utilized to detect a link or node down event and signal the RIB that
>    the event has occurred to force immediate control plane convergence.
> 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