[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-ospf
Subject:    [Lsr] FW: New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-06.txt
From:       "Aijun Wang" <wangaj3 () chinatelecom ! cn>
Date:       2021-03-26 6:42:28
Message-ID: 00a501d7220b$33127030$99375090$ () chinatelecom ! cn
[Download RAW message or body]

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>; Gyan Mishra
> <gyan.s.mishra@verizon.com>; Yaqun Xiao <xiaoyaqun@huawei.com>; 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
> 


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


[prev in list] [next in list] [prev in thread] [next in thread]