[Bier] Re: [Shepherding AD review] Pre-IETF Last-Call review of draft-ietf-bier-php-11

["Gunter van de Velde (Nokia)" <[e-mail]>]

Thanks Jeffrey.

G/

Sent from Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Jeffrey (Zhaohui) Zhang <[e-mail]>
Sent: Wednesday, September 25, 2024 11:21:28 PM
To: Gunter van de Velde (Nokia) <[e-mail]>; [e-mail] <[e-mail]>
Cc: BIER WG <[e-mail]>
Subject: RE: [Shepherding AD review] Pre-IETF Last-Call review of draft-ietf-bier-php-11


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.



Hi Gunter,

Thank you so much for the editorial rewrites you suggested. I adopted all of them.
Thank you so much for the checklist/guidelines you provided for the security and operational considerations. They're always my headaches, but now I was able to check against the guidelines and added an operational considerations section.

I have uploaded the -12 revision.

Jeffrey


Juniper Business Use Only
-----Original Message-----
From: Gunter van de Velde (Nokia) <[e-mail]>
Sent: Friday, August 23, 2024 6:11 AM
To: [e-mail]
Cc: BIER WG <[e-mail]>
Subject: [Shepherding AD review] Pre-IETF Last-Call review of draft-ietf-bier-php-11

[External Email. Be cautious of content]


# Gunter Van de Velde, RTG AD, comments for draft-ietf-bier-php-11

Hi Jeffrey and BIER WG,

Please find here a shepherding AD review of draft-ietf-bier-php-11

Many thanks to Xiao Min for the excellent Shepherd write-up. It was great to see that the work has been validated with the MPLS Working Group. I also noted from the email archive that Loa provided some valuable feedback, which has been thoughtfully incorporated.

When running idnits, a few messages appeared, likely due to the references being slightly outdated over time. You can view the idnits report here: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fauthor-tools.ietf.org%2Fapi%2Fidnits%3Furl%3Dhttps%3A**Awww.ietf.org*archive*id*draft-ietf-bier-php-11.txt__%3BLy8vLy8!!NEt6yMaO-gk!GcVPJnAM2wXo7M3Fsll7EiAcVHTnE65UYgXsHyZg8f4X-tE4T7W-4YhFjWPmDDzu0xhwBOp5Z8OQ3EmxSjtbE9MNJcY%24&data=05%7C02%7Cgunter.van_de_velde%40nokia.com%7Ce3934f795da746fb584508dcdda80824%7C5d4717519675428d917b70f44f9630b0%7C0%7C0%7C638628960980763690%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=r0DrGpUNAXnNFMOxhOXuCTl7Feoe7%2FU5vSGAZpJT5f8%3D&reserved=0<https://urldefense.com/v3/__https://author-tools.ietf.org/api/idnits?url=https:**Awww.ietf.org*archive*id*draft-ietf-bier-php-11.txt__;Ly8vLy8!!NEt6yMaO-gk!GcVPJnAM2wXo7M3Fsll7EiAcVHTnE65UYgXsHyZg8f4X-tE4T7W-4YhFjWPmDDzu0xhwBOp5Z8OQ3EmxSjtbE9MNJcY$>

The document currently lacks an operational considerations/implication section. To assist with this, I've added some initial thoughts on the operational aspects associated with PHP operation at the very end of this AD review for inspiration and to discuss if they apply to the BIER use-case.

The security section is somewhat brief. I've included some ideas to help expand on the security considerations related to PHP and its application within BIER. Not all the suggested observations will apply strongly for this BIER use case.

While the document effectively outlines the operational procedures, it could benefit from some grammatical enhancements to improve clarity. Given that this draft is concise, I thought it would be more convenient to propose the revised text section by section rather than suggesting edits paragraph by paragraph. This approach should make it easier to incorporate the suggestions into the XML.


#DETAILED COMMENTS (snipped in this reply)