All, I believe this Errata should be accepted as a IPvX Addr Count of zero is an error.
Thanks, Acee > On Feb 17, 2025, at 10:36, RFC Errata System <rfc-edi...@rfc-editor.org> > wrote: > > The following errata report has been submitted for RFC9568, > "Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid8299 > > -------------------------------------- > Type: Technical > Reported by: Quentin Armitage <quen...@armitage.org.uk> > > Section: 7.1 > > Original Text > ------------- > * It MUST verify that the VRID is configured on the receiving > interface and the local router is not the IPvX address owner > (Priority = 255 (decimal)). > > If any one of the above checks fails, the receiver MUST discard the > packet, SHOULD log the event (subject to rate-limiting), and MAY > indicate via network management that an error occurred. > > Corrected Text > -------------- > * It MUST verify that the VRID is configured on the receiving > interface and the local router is not the IPvX address owner > (Priority = 255 (decimal)). > > * It MUST verify that IPvX Addr Count is non zero. > > If any one of the above checks fails, the receiver MUST discard the > packet, SHOULD log the event (subject to rate-limiting), and MAY > indicate via network management that an error occurred. > > Notes > ----- > The only change above is adding: > * It MUST verify that IPvX Addr Count is non zero. > > This is due to section 5.2.5 requiring it: > > 5.2.5. IPvX Addr Count > > The IPvX Addr Count field is the number of either IPv4 addresses or IPv6 > addresses contained in this VRRP advertisement. The minimum value is 1. If > the received count is 0, the VRRP advertisement MUST be ignored. > > 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. > > -------------------------------------- > RFC9568 (draft-ietf-rtgwg-vrrp-rfc5798bis-18) > -------------------------------------- > Title : Virtual Router Redundancy Protocol (VRRP) Version 3 for > IPv4 and IPv6 > Publication Date : April 2024 > Author(s) : A. Lindem, A. Dogra > Category : PROPOSED STANDARD > Source : Routing Area Working Group > Stream : IETF > Verifying Party : IESG _______________________________________________ rtgwg mailing list -- rtgwg@ietf.org To unsubscribe send an email to rtgwg-le...@ietf.org
