FYI,

This adopts Acee’s comments and a few other editorial changes.

Tony


> Begin forwarded message:
> 
> From: [email protected]
> Subject: New Version Notification for draft-ietf-lsr-dynamic-flooding-12.txt
> Date: February 24, 2023 at 8:42:55 AM PST
> To: "Gyan S. Mishra" <[email protected]>, "Dave Cooper" 
> <[email protected]>, "David Cooper" <[email protected]>, 
> "Gyan Mishra" <[email protected]>, "Huaimo Chen" 
> <[email protected]>, "Les Ginsberg" <[email protected]>, "Luay Jalil" 
> <[email protected]>, "Peter Psenak" <[email protected]>, "Srinath 
> Dontula" <[email protected]>, "Tony Li" <[email protected]>, "Tony Przygienda" 
> <[email protected]>, <[email protected]>
> 
> 
> A new version of I-D, draft-ietf-lsr-dynamic-flooding-12.txt
> has been successfully submitted by Tony Li and posted to the
> IETF repository.
> 
> Name:         draft-ietf-lsr-dynamic-flooding
> Revision:     12
> Title:                Dynamic Flooding on Dense Graphs
> Document date:        2023-02-24
> Group:                lsr
> Pages:                47
> URL:            
> https://www.ietf.org/archive/id/draft-ietf-lsr-dynamic-flooding-12.txt
> Status:         
> https://datatracker.ietf.org/doc/draft-ietf-lsr-dynamic-flooding/
> Htmlized:       
> https://datatracker.ietf.org/doc/html/draft-ietf-lsr-dynamic-flooding
> Diff:           
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-dynamic-flooding-12
> 
> Abstract:
>   Routing with link state protocols in dense network topologies can
>   result in sub-optimal convergence times due to the overhead
>   associated with flooding.  This can be addressed by decreasing the
>   flooding topology so that it is less dense.
> 
>   This document discusses the problem in some depth and an
>   architectural solution.  Specific protocol changes for IS-IS, OSPFv2,
>   and OSPFv3 are described in this document.
> 
> 
> 
> 
> The IETF Secretariat
> 
> 

_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to