Hi,

We submitted a new version of this draft with detailed OSPFv2 and OSPFv3 
encodings. Please review and send your comments.

Thanks,
Yingzhen

> 
> From: [email protected] <mailto:[email protected]> 
> <[email protected] <mailto:[email protected]>>
> Sent: Sunday, February 21, 2021 11:21 AM
> To: Abhay Roy <[email protected] <mailto:[email protected]>>; Acee Lindem 
> <[email protected] <mailto:[email protected]>>; Sina Mirtorabi <[email protected] 
> <mailto:[email protected]>>; Yingzhen Qu <[email protected] 
> <mailto:[email protected]>>
> Subject: New Version Notification for 
> draft-acee-lsr-ospf-transport-instance-02.txt
>  
> 
> A new version of I-D, draft-acee-lsr-ospf-transport-instance-02.txt
> has been successfully submitted by Yingzhen Qu and posted to the
> IETF repository.
> 
> Name:           draft-acee-lsr-ospf-transport-instance
> Revision:       02
> Title:          OSPF Transport Instance Extensions
> Document date:  2021-02-19
> Group:          Individual Submission
> Pages:          14
> URL:           
> https://www.ietf.org/archive/id/draft-acee-lsr-ospf-transport-instance-02.txt 
> <https://www.ietf.org/archive/id/draft-acee-lsr-ospf-transport-instance-02.txt>
>  
> Status:         
> https://datatracker.ietf.org/doc/draft-acee-lsr-ospf-transport-instance/ 
> <https://datatracker.ietf.org/doc/draft-acee-lsr-ospf-transport-instance/> 
> Htmlized:      
> https://datatracker.ietf.org/doc/html/draft-acee-lsr-ospf-transport-instance 
> <https://datatracker.ietf.org/doc/html/draft-acee-lsr-ospf-transport-instance>
>  
> Diff:          
> https://www.ietf.org/rfcdiff?url2=draft-acee-lsr-ospf-transport-instance-02 
> <https://www.ietf.org/rfcdiff?url2=draft-acee-lsr-ospf-transport-instance-02> 
> 
> Abstract:
>    OSPFv2 and OSPFv3 include a reliable flooding mechanism to
>    disseminate routing topology and Traffic Engineering (TE) information
>    within a routing domain.  Given the effectiveness of these
>    mechanisms, it is convenient to envision using the same mechanism for
>    dissemination of other types of information within the domain.
>    However, burdening OSPF with this additional information will impact
>    intra-domain routing convergence and possibly jeopardize the
>    stability of the OSPF routing domain.  This document presents
>    mechanism to relegate this ancillary information to a separate OSPF
>    instance and minimize the impact.
> 
>                                                                               
>     
> 
> 
> 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 
> <http://tools.ietf.org/>.
> 
> The IETF Secretariat

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

Reply via email to