![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Harald,
The trouble is - know it or not - this "language choice" is the result of a lot of wrangling. Your comment is a late comer to the "party" as we have been round and round on this as well as other issues relating to this document. What you see now is the current negotiated position, and it would be very nice if we did not have yet another round of negotiations because someone else is not exactly happy with what we have...
IETF Consensus - New values are assigned through the IETF
consensus process. Specifically, new assignments are made via
RFCs approved by the IESG. Typically, the IESG will seek
input on prospective assignments from appropriate persons
(e.g., a relevant Working Group if one exists).Wordsmithing is hard.
Harald
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.