housley at vigilsec.com
Fri Jul 1 08:06:05 PDT 2016
The security considerations say:
Since RFCs are sometimes exchanged outside the normal Web sandboxing
mechanism (such as using the "rsync" program to a mirror site) then
loaded from a local file, more care must be taken with the HTML than
is ordinary on the web.
Is that care already factored into the specification? If so, please say that. If not, what additional care is needed?
On Jun 30, 2016, at 5:27 PM, Internet-Drafts at ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Internet Architecture Board of the IETF.
> Title : HyperText Markup Language Request For Comments Format
> Authors : Joe Hildebrand
> Paul Hoffman
> Filename : draft-iab-html-rfc-03.txt
> Pages : 41
> Date : 2016-06-30
> In order to meet the evolving needs of the Internet community, the
> format for RFCs is changing from a plain-text, ASCII-only format to a
> canonical XML format that will in turn be rendered into several
> publication formats. This document defines the HTML format that will
> be rendered for an RFC or Internet-Draft.
> The IETF datatracker status page for this draft is:
> There's also a htmlized version available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> Internet-Drafts are also available by anonymous FTP at:
More information about the rfc-interest