Scott O. Bradner wrote:
1st way:
The IETF community provides the IETF Trust with a specific request and
the Trust provides possible changes or new text to meet the specific
request. The IETF request can come form a WG, in which case it should
be in the form of a BCP (an IETF consensus document) or, with a public
justification, from the IETF Chair (or maybe the IAB Chair). The Trust
publishes the proposed changes with a 4-week last call and the changes
are adopted if the IETF Chair determines that there is IETF consensus
support for the specific changes.
Isn't this what has essentially happened in this case? RFC 5377 and
5378 were published and other issues were raised later on. The Trust
responded by reviewing the TLP and suggest modifications based on the
RFC and discussions afterwards. The modifications are now out for a
30 day community review.
Henk
------------------------------------------------------------------------------
Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre http://www.xs4all.nl/~henku
P.O.Box 10096 Singel 258 Phone: +31.20.5354414
1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445
The Netherlands The Netherlands Mobile: +31.6.55861746
------------------------------------------------------------------------------
Belgium: an unsolvable problem, discussed in endless meetings, with no
hope for a solution, where everybody still lives happily.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf