Hi Paul, Thanks for the feedback. Makes perfectly sense. All ack. Is queued for the next release.
Best Wishes Thomas From: Aitken, Paul <paul.ait...@intl.att.com> Sent: Thursday, March 26, 2020 11:31 PM To: Graf Thomas, INI-NET-DCF <thomas.g...@swisscom.com> Cc: spring@ietf.org Subject: Re: review of draft-tgraf-ipfix-mpls-sr-label-type-01 Thomas, Many thanks for the review and the feedback. Ack on all. I updated the draft according to your and other input from the mailing list. Looks good! Two nits: In the new text in the last paragraph of section 1, remove "to" : "to which label protocol it belongs to". In Figure 1, although the order is unimportant, could RFC 8665 come before RFC 8667 ? If the draft is to be accepted by IANA then it needs to be published or archived somewhere This was one of the unclarities I had. If I understand you correctly, this draft needs to be adopted by SPRING working group and published as RFC for documentation purposes before values can be assigned by IANA. Correct? Yes, publishing it as an RFC would be the most obvious solution. The language in RFC 7012 and RFC 5102 is flexible to allow for non-IETF documents. P.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
