Ideas for stuff that could go into a Part 0

[julian.reschke@…]

• terminology
• ABNF extensions (list rule)
• combined ABNF (note that we have less dependencies between the parts than we used to have; maybe it's not useful to do this)
• all IANA registrations
• common index
• HTTP version history (p1 appendix A)
• Architecture (p1 section 2)
• possibly parts of p1 section 7
• acknowledgements?
• general approach to conformance and error handling

Related to this, if we create a P0, we should also discuss which documents in the set need the "Obsoletes: 2616" disclaimer. All? P1..7? P0?

[mnot@…]

Another strong argument for a p0 came up in review of James' Prefer draft with the ADs; I-Ds (and other docs) referencing HTTP may now have to use up to seven separate references, which is quite unwieldy. A properly structured p0 would make a single reference possible.

[julian.reschke@…]

From [1687]:

add skeleton for P0 (see #326)

[julian.reschke@…]

From [1688]:

add skeleton for P0 (see #326)

[mnot@…]

From [1717]:

Initial go at p0; see #326

[julian.reschke@…]

From [1718]:

regenerate HTML for [1717] (see #326)

[julian.reschke@…]

From [1719]:

fix SVN metadata and link metadata (see #326)

[julian.reschke@…]

From [1723]:

regenerate HTML (see #326)

[mnot@…]

Closing, as it doesn't appear we'll be doing a p0.