Hi John, 

Thanks for the review and “No Objection”. The comments below will be 
incorporated in the -18 version.

> On Jan 3, 2024, at 15:20, John Scudder via Datatracker <[email protected]> 
> wrote:
> 
> John Scudder has entered the following ballot position for
> draft-ietf-rtgwg-vrrp-rfc5798bis-17: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to 
> https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
> for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-rtgwg-vrrp-rfc5798bis/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks for doing this work!
> 
> I have a few small comments below, I hope they're helpful.
> 
> ### Section 4.1
> 
> “The IPvX example above shows a Virtual Router configured to cover the IPv4
> address owned by Router-1 (VRID=1, IPvX_Address=A)”
> 
> Shouldn’t that be “IPvX” not “IPv4”?

Yes - good catch. 


> 
> ### Section 6.4.3
> 
> Pretty nitty, the RFCEd would presumably catch this, and I’m puzzled how it
> would have happened, but “@ Discard ADVERTISEMENT” isn’t at the same indent
> level as all the other @ items (it should be one space further in).


Fixed - this discrepancy was introduced when I removed the pseudo-code line 
number of 12/18/2023.


> 
> ### Section 8.2.4
> 
> “Additional configuration MAY be required in order for Unsolicited Neighbor
> Advertisements to update the corresponding neighbor cache.”
> 
> Did you really intend the BCP 14-style MAY there? If so, OK, but it reads as
> though a lowercase “may” would do the job.

I agree, this isn’t really normative and should be “may”. 

Thanks,
Acee


> 
> 
> 

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

Reply via email to