[rfc-i] Proposal for v3 to simplify most references

Jim Schaad ietf at augustcellars.com
Wed Feb 12 16:11:50 PST 2014



> -----Original Message-----
> From: rfc-interest-bounces at rfc-editor.org
[mailto:rfc-interest-bounces at rfc-
> editor.org] On Behalf Of Paul Hoffman
> Sent: Monday, February 10, 2014 9:02 AM
> To: Nico Williams
> Cc: RFC Interest
> Subject: Re: [rfc-i] Proposal for v3 to simplify most references
> 
> On Feb 10, 2014, at 8:52 AM, Nico Williams <nico at cryptonector.com> wrote:
> 
> > On Mon, Feb 10, 2014 at 10:50 AM, Heather Flanagan (RFC Series Editor)
> > <rse at rfc-editor.org> wrote:
> >> One of the things I expect is that the final XML will be fairly
> >> self-contained.  In this case, that would mean that the final,
> >> canonical XML file would contain the references pulled from the
> >> citation library at the time of publication.
> >
> > That's a good idea.
> >
> > I wouldn't mind if stable references are left as references through an
> > external reference library, but it'd have to be a library maintained
> > by the RFC-Editor, as otherwise there's no way to guarantee stability.
> 
> This is a good point. As part of the proposal, I'll add "the library used
for
> expansion of the references is maintained by the RFC Editor". That doesn't
> prevent someone from turning in a document with their own fully-described
> <reference>s, but it makes it clear that if you use the easier version,
the RFC
> Editor will be the expander.

It would also, as with today, possible that a tool can do the expansion so
that the version submitted to the database uses only the standard library
and has things like BCPs expanded.

Jim

> 
> --Paul Hoffman
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest



More information about the rfc-interest mailing list