Hi Paolo, I reviewed
https://datatracker.ietf.org/doc/html/draft-lucente-grow-bmp-tlv-ebit-02 and have some minor nits and simplifications in wording to be considered. Best wishes Thomas Change from Vendors need the ability to define proprietary Information Elements, because, for example, they are delivering a pre-standard product. To Vendors need the ability to define proprietary Information Elements for various reasons such as delivering a pre-standard product. Change from This This would align with Also for code point assignment to be eligible, an IETF document needs to be adopted at a Working Group and in a stable condition. To This aligns also with code point assignments where a document needs to be at stable condition in IETF Working Group first. Change from shipped to network operators to be tested there as well. To shipped to network operators for testing. Change from This would align with This document re-defines the format of IANA- registered TLVs in a backward compatible manner with respect to previous documents and existing IANA allocations; To This document re-defines the format of IANA- registered TLVs in a backward compatible manner with respect to previous documents and existing IANA allocations; Change from The encoding specified in this document applies to all existing BMP Message Types and their namespaces defined in Future BMP Message Types MUST make use of the TLV encoding defined in this document. To The TLV encoding specified in this document applies to all existing and future BMP Message Types and their namespaces. .
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
