- Philip
afaict the way to do it is what Brian Carpenter suggested -- you still
need to insert a "note" in the xml immediately before <abstract>
<note title=""><t>Blah blah disclaimer blah blah</t></note>
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s)
controlling the copyright in such materials, this document may not
be modified outside the IETF Standards Process, and derivative
works of it may not be created outside the IETF Standards Process,
except to format it for publication as an RFC or to translate it
into languages other than English.
Source of the disclaimer: <http://trustee.ietf.org/license-info/>,
where one can download the PDF file in which see Section 6.c.iii
You don't, as far as I know. I'm hoping one of the volunteers will
reply with good news.
I'm going to release an update shortly with the new DTD, but if you
can find the xxe addon directory (~/.xxe4/addon in MacOS and Linux,
somewhere under your settings directory on Windows) you can replace
the dtd file found in the xml2rfc addon with the one shipped with the
newer xml2rfc version and use the new values in the pulldown.
There is not yet an xml2rfc release with the February 2009 IPR; it was
just ready for release but then the desired location of the IPR
statement changed late last night so we'll have to re-respin.
Bill
Please clarify ... we can snatch the DTD from the new xml2rfc release
with the February 2009 IPR, and stick it in your addon directory, _when_
the new xml2rfc release becomes available, but it's not available yet?
Right.
Bill