Re: [pim] pim wglc for 3228bis, 3376bis and 3810bis

[Brian Haberman <[e-mail]>]

Thanks for the comment, Jeffrey!

If I recall correctly, the tables were re-formatted due to the change in 
underlying xml2rfc schema. I will have to double-check that though.

Regards,
Brian

On 12/8/23 2:13 PM, Jeffrey (Zhaohui) Zhang wrote:
> Hi,
> 
> One editorial nit. It would be nice not to change to the following table format (as one example)
> 
>     An implementation of IGMPv3 MUST also support the following three
>     message types, for interoperation with previous versions of IGMP (see
>     Section 7):
> 
>        +===================+=============================+===========+
>        | Type Number (hex) |         Message Name        | Reference |
>        +===================+=============================+===========+
>        |        0x12       | Version 1 Membership Report | [RFC1112] |
>        +-------------------+-----------------------------+-----------+
>        |        0x16       | Version 2 Membership Report | [RFC2236] |
>        +-------------------+-----------------------------+-----------+
>        |        0x17       |    Version 2 Leave Group    | [RFC2236] |
>        +-------------------+-----------------------------+-----------+
> 
> It makes text-based editing slightly harder and gives noise when one uses the iddiff tool to compare against the original RFC.
> Just a personal preference 😊
> 
> Although I did not get to verify the technical details, I trust the author's work and support the advancement of these documents.
> 
> Thanks.
> Jeffrey
> 
> 
> Juniper Business Use Only
> -----Original Message-----
> From: pim <[e-mail]> On Behalf Of Stig Venaas
> Sent: Tuesday, November 28, 2023 5:59 PM
> To: [e-mail]
> Subject: [pim] pim wglc for 3228bis, 3376bis and 3810bis
> 
> [External Email. Be cautious of content]
> 
> 
> Dear working group
> 
> We have been working on progressing these core documents to Internet Standard.
> 
> The documents are
> 
> IANA Considerations for Internet Group Management Protocols https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-pim-3228bis/__;!!NEt6yMaO-gk!FD3Za78albR3t1oxIwbsTaKCPwsq4F3YEPNC4Xlu8JogXSjVIXnhrQZl1YKE-P9rE1xX4AHU_Fh4$
> 
> Internet Group Management Protocol, Version 3 https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-pim-3376bis/__;!!NEt6yMaO-gk!FD3Za78albR3t1oxIwbsTaKCPwsq4F3YEPNC4Xlu8JogXSjVIXnhrQZl1YKE-P9rE1xX4HT8Qtg6$
> 
> Multicast Listener Discovery Version 2 (MLDv2) for IPv6 https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-pim-3810bis/__;!!NEt6yMaO-gk!FD3Za78albR3t1oxIwbsTaKCPwsq4F3YEPNC4Xlu8JogXSjVIXnhrQZl1YKE-P9rE1xX4CNmGFB6$
> 
> As these are important documents, I am hoping we will get some people to review these drafts and give us feedback. We did not get any responses to the previous wglc for these documents.
> 
> Please respond by December 15th 2023 whether you believe these documents are ready for publication, and any comments or concerns you may have. Any input is helpful.
> 
> Regards,
> Stig
> 
> _______________________________________________
> pim mailing list
> [e-mail]
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/pim__;!!NEt6yMaO-gk!FD3Za78albR3t1oxIwbsTaKCPwsq4F3YEPNC4Xlu8JogXSjVIXnhrQZl1YKE-P9rE1xX4K6hUpD_$
> 
> _______________________________________________
> pim mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/pim