Hi Acee, I verified the errata in the errata back-end system.
@Kris, Long time no speak and many thanks for pointing this out. Take care, G/ -----Original Message----- From: Acee Lindem <acee.i...@gmail.com> Sent: Monday, September 16, 2024 3:14 PM To: RFC Errata System <rfc-edi...@rfc-editor.org> Cc: Peter Psenak <ppse...@cisco.com>; han...@gredler.at; r...@rob.sh; Wim Henderickx (Nokia) <wim.henderi...@nokia.com>; jeff.tants...@ericsson.com; a...@cisco.com; James Guichard <james.n.guich...@futurewei.com>; John Scudder <j...@juniper.net>; Gunter van de Velde (Nokia) <gunter.van_de_ve...@nokia.com>; a...@cisco.com; kmich...@cisco.com; lsr <lsr@ietf.org> Subject: Re: [Lsr] [Technical Errata Reported] RFC7684 (8104) CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. The errata is correct and should be verified. Thanks, Acee > On Sep 16, 2024, at 07:38, RFC Errata System <rfc-edi...@rfc-editor.org> > wrote: > > The following errata report has been submitted for RFC7684, > "OSPFv2 Prefix/Link Attribute Advertisement". > > -------------------------------------- > You may review the report below and at: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > rfc-editor.org%2Ferrata%2Feid8104&data=05%7C02%7Cgunter.van_de_velde%4 > 0nokia.com%7Cbbd7e71619e74cbbfb5108dcd6517fb4%7C5d4717519675428d917b70 > f44f9630b0%7C0%7C0%7C638620892719072837%7CUnknown%7CTWFpbGZsb3d8eyJWIj > oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C > %7C&sdata=a5ZM0eznwvZpJkSt6FmmLIJmuchibSFR89DAxTVzPWI%3D&reserved=0 > > -------------------------------------- > Type: Technical > Reported by: Kris Michielsen <kmich...@cisco.com> > > 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 -- lsr@ietf.org > To unsubscribe send an email to lsr-le...@ietf.org _______________________________________________ Lsr mailing list -- lsr@ietf.org To unsubscribe send an email to lsr-le...@ietf.org
