Pekka Savola <pekkas@xxxxxxxxxx> writes: > On Mon, 12 Mar 2007, The IESG wrote: >> A URL of this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-legg-xed-asd-07.txt > ... >> Working Group Summary >> >> This document set was not produced by an IETF working group, but by an >> individual. IETF Last Call produced no comments, and solicited reviewers >> were basically positive. > > This writeup was not updated or comments were not duly processed. I > see 14 Last Call comments (retaining the subject line) on > ietf@xxxxxxxxx, as well as 12 comments under the 'Protest: Complexity > running rampant' thread. Thanks for pointing this out. I believe the protocol is not possible to implement due to the copyright issue, because the ASN.1 schema specifically says that the IETF copying conditions apply to it: -- Copyright (C) The IETF Trust (2006). This version of -- this ASN.1 module is part of RFC XXXX; see the RFC itself -- for full legal notices. I registered this as last call comment in http://article.gmane.org/gmane.ietf.general/23684 where I also suggested a way to solve this problem. I believe the IETF should not specify protocols that require that you violate a copyright notice to implement. Further, the copyright notice in the document appears to be both incorrect and to violate the IETF process. Typically copyrights on document text are not transferred to the IETF Trust, and I see no signs that this happened here. The notice violates the requirements set forth by RFC 3978 section 5.4 (as updated by RFC 4748) which says: 5.4. Copyright Notice (required for all IETF Documents) (Normally placed at the end of the IETF Document.) "Copyright (C) The IETF Trust (year). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights." Additional copyright notices are not permitted in IETF Documents ... The notice in the document doesn't match the required notice, and is thus not permitted under RFC 3978. Or am I missing something? I suppose an appeal is one way to bring this up formally, although if this can be resolved in a better way that would be preferable. /Simon _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf