Hi Dhruv,

From: rtgwg <[email protected]> on behalf of Dhruv Dhody 
<[email protected]>
Date: Thursday, July 14, 2022 at 9:07 AM
To: Yingzhen Qu <[email protected]>
Cc: Routing WG <[email protected]>
Subject: Re: Working Group Adoption Call for 
draft-addogra-rtgwg-vrrp-rfc5798bis-11

Hi,

I support adoption.

Now that we are doing bis, could we improve the IANA section a bit -- it would 
help to identify the registry and explicit instructions to update the 
references, for instance.   Also for ethernet, isn't IPv4 allocation missing -> 
"00-01-00 to 00-01-FF"?

I agree. I’ve updated as Donald suggested with a bit more information.


Section "11.2.6. 0 - Reserved" and the VRP packet with the field being called 
"0" but the description as "This reserved field MUST be set to zero..." reads 
wrong. I suggest either using "reserved" in the figure and section title or 
just using MBZ - must be zero and not call it reserved.

I renamed the field to “Reserve”, it can’t be “Reserved” since it is only 7 
characters for the 4-bit field.

Thanks,
Acee

Thanks!
Dhruv



On Fri, Jul 1, 2022 at 8:23 AM Yingzhen Qu 
<[email protected]<mailto:[email protected]>> wrote:

Dear RTGWG,

This email begins a working group adoption call for the following draft:

https://datatracker.ietf.org/doc/draft-addogra-rtgwg-vrrp-rfc5798bis/

Please indicate your support or objections by July 17th, 2022.

Authors, please respond to the list indicating whether you are aware of any IPR 
that applies to the draft..

Thanks,
Yingzhen
_______________________________________________
rtgwg mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/rtgwg
_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg

Reply via email to