1. <draft-bradner-rfc-extracts-00.txt>
Extracting RFCs
<draft-bradner-rfc-extracts-00.txt>
Scott Bradner

2. Problem people want to extract material from RFCs for:
use in documentation (e.g. on-line help pages)
use in MIB & code compilers
etc
RFC 3667/3668 does not ask ID authors for the right to permit that

3. Proposal add something like this to RFC 3667 sec 3.3
c. To the extent that a Contribution or any portion thereof is
protected by copyright and other rights of authorship, the
Contributor, and each named co-Contributor, and the organization
he or she represents or is sponsored by (if any) grant a
perpetual, irrevocable, non-exclusive, royalty-free, world-wide
right and license to anyone to extract, copy, publish, display, distribute,
and incorporate into other works, for any purpose (and not limited
to use within the IETF Standards Process) any portion of the
Contribution as long as the extract is not modified, proper
acknowledgement is given and as long as the ISOC copyright notice
is included. ...

4. Proposal, contd. might go someplace other than as sec 3.3 (c)
It also being understood that the licenses granted
under this paragraph (c) shall not be deemed to grant any right
under any patent, patent application or other similar intellectual
property right disclosed by the Contributor under [IETF IPR]).
might go someplace other than as sec 3.3 (c)

5. Reasons to Permit Extracts
the only reason that this is not in RFC 3667 already was a error on the part of the editor
seems to be a no brainer to permit extractions of MIBs and code fragments
seems to be useful to let people publish as-is extracts of any length in documentation
e.g., on-line help pages, text books, reference manuals etc

6. History
historically (pre RFC 2026) extracting RFCs was permitted but nothing in the RFCs specifically stated that this was OK
still the case for RFC Editor RFCs