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

Paul Hoffman paul.hoffman at vpnc.org
Mon Feb 10 08:15:11 PST 2014

On Feb 10, 2014, at 7:36 AM, Michael Richardson <mcr+ietf at sandelman.ca> wrote:

>> The <reference> element can take another optional attribute: "rfc",
>> "fyi", "id" "bcp", or "std". Each takes a string that is a number. If
>> "bcp" or "std" are given, an additional optional "expanded" attribute
>> can be given: it is a comma-separated list of numbers. At the same
>> time, the contents of <reference> goes from requiring <front> to making
>> <front> optional.
> okay.... so does the References section get a fully expanded output
> (the reference.XXXX.xml file gets sucked in at some point), or is it
> truncated if the user is offline?

Fully expanded. That is, if you have an offline version of the processor tool, it should have the entire database in it.

> A *concern* that I have is that referencing RFCs is really easy, but
> getting a reference constructed to other documents is sometimes quite
> arcane...

Right. See my followup to Julian yesterday: it makes sense for the tool to handle references to a bunch of other SDOs as well.

--Paul Hoffman

More information about the rfc-interest mailing list