![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
On 21:25 25/08/2005, Stephane Bortzmeyer said:
If the IESG were to refuse to publish the Sender-ID document as it is, it would not "police" everything: anyone can still do what he wants on the Internet.
The only thing than the IETF can do is to "bless" or not the document,
Stephane,
just a remark here. In the RFC 3066bis Last Call case the IETF has the capacity not only to "police" but to "impose" and "force". This is the case when a memo documents a IANA registry. In the case of a standard track memo, there can be an appeal before it is imposed. It seems not in the case of a BCP.
Wrong. IESG approvals of a standards track draft or of a BCP are equally subject to appeal within two months.
Brian
_______________________________________________ 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.