The errata is correct and should be verified. 

Thanks,
Acee

> On Sep 16, 2024, at 07:38, RFC Errata System <[email protected]> 
> wrote:
> 
> The following errata report has been submitted for RFC7684,
> "OSPFv2 Prefix/Link Attribute Advertisement".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid8104
> 
> --------------------------------------
> Type: Technical
> Reported by: Kris Michielsen <[email protected]>
> 
> Section: 2.1
> 
> Original Text
> -------------
>   Route Type
>      The type of the OSPFv2 route.  If the route type is 0
>      (Unspecified), the information inside the OSPFv2 External Prefix
>      TLV applies to the prefix regardless of prefix's route type.  This
>      is useful when prefix-specific attributes are advertised by an
>      external entity that is not aware of the route type associated
>      with the prefix.  Supported types are:
> 
> Corrected Text
> --------------
>   Route Type
>      The type of the OSPFv2 route.  If the route type is 0
>      (Unspecified), the information inside the OSPFv2 Extended Prefix
>      TLV applies to the prefix regardless of prefix's route type.  This
>      is useful when prefix-specific attributes are advertised by an
>      external entity that is not aware of the route type associated
>      with the prefix.  Supported types are:
> 
> Notes
> -----
> s/External Prefix/Extended Prefix/
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it 
> will be removed shortly by the RFC Production Center.) Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> will log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC7684 (draft-ietf-ospf-prefix-link-attr-13)
> --------------------------------------
> Title               : OSPFv2 Prefix/Link Attribute Advertisement
> Publication Date    : November 2015
> Author(s)           : P. Psenak, H. Gredler, R. Shakir, W. Henderickx, J. 
> Tantsura, A. Lindem
> Category            : PROPOSED STANDARD
> Source              : Open Shortest Path First IGP
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> Lsr mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to