Re: [Last-Call] Last Call: <draft-koster-rep-06.txt> (Robots Exclusion Protocol) to Informational RFC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm uncomfortable leaving change control for a key interoperability
mechanism in the search market in the hands of one competitor, yet blessing
it as part of the IETF stream. I think the IETF as a whole should be
uncomfortable with that too, given current competition enforcement trends.

Putting on my trustee hat, I don't think this can be an IETF document without IETF change control. RFC 5378 says

      The right to produce
   derivative works, in addition to translations, is required for all
   IETF Standards Track documents and for most IETF non-Standards Track
   documents.  There are two exceptions to this requirement: documents
   describing proprietary technologies and documents that are
   republications of the work of other standards organizations.

If it's a proprietary technology, Mark is right.  If it's not, we need
change control.

Another possibility would be to move it to the Independent stream if Eliot agrees.

Regards,
John Levine, johnl@xxxxxxxxx, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux