[rfc-i] draft-iab-html-rfc-02: references
julian.reschke at gmx.de (Julian Reschke) Thu, 03 March 2016 12:55 UTC
From: julian.reschke at gmx.de (Julian Reschke)
Date: Thu, 3 Mar 2016 13:55:51 +0100
Subject: [rfc-i] draft-iab-html-rfc-02: references
In-Reply-To: <56D79826.30208@it.aoyama.ac.jp>
References: <56D16672.4000708@gmx.de>
<0EB37407-B7F1-4022-9822-6D5720D45B8C@vpnc.org> <56D1CFD8.2090909@gmx.de>
<017E4EA1-75C5-4891-AC5C-D5ABD845A1D3@vpnc.org> <56D1D4C4.1090007@gmx.de>
<64E8088C-4B3B-4445-B3DF-C673579EEE14@cisco.com>
<0E1902D3-A929-40D3-BEF7-2064D9F5A6A5@cisco.com>
<BF9113FB-DE8C-4EFC-8B74-571B8C22FACC@cisco.com> <56D52F2E.3000003@gmx.de>
<29116D5B-9576-4CD2-B2F3-F272F6F032FE@cisco.com> <56D5D0B0.9040105@gmx.de>
<6BF904F1-C6ED-44FE-839C-CF28BCF2BB51@vpnc.org> <56D5D64B.90608@gmx.de>
<99EA90EC-2423-4879-98EB-A6E959DC7800@cisco.com>
<CE678DE8-43E3-4A2D-BE82-1685A4F3E9FD@att.com>
<0F3DE961-1D6E-4499-BC9F-B6C4EC7C7DD9@cisco.com>
<56D79826.30208@it.aoyama.ac.jp>
Message-ID: <56D83457.9080608@gmx.de>
On 2016-03-03 02:49, Martin J. D?rst wrote: > On 2016/03/02 04:48, Joe Hildebrand (jhildebr) wrote: >> On 3/1/16, 11:59 AM, "HANSEN, TONY L" <tony at att.com> wrote: > >>> I see three choices: >>> >>> 1) Require the processors to all follow the multiple pass rules, or >>> act like it did by back-patching >> >> They still have to get the section number right. Remember that >> <references> are in <back>, but are numbered as if they are in >> <middle>, which is surprising as a output formatter author. >> >> Another approach I'd be fine with is number the references sections as >> R.1 ... R.n, which would conflict with an Appendix R, which I hope >> never happens. > > Another approach would be to not number (or otherwise label) the > reference section. This is what a lot (it may even be the majority) of > books and journal formats do, and what I personally find easier to use. > > This may not solve the structuring problem, but hopefully would make it > easier. It's another way to do things, but it would be inconsistent with the existing body of RFCs and the current style guide (see, for instance <https://tools.ietf.org/html/rfc7322#section-4>). Best regards, Julian
- [rfc-i] draft-iab-html-rfc-02: references Julian Reschke
- [rfc-i] draft-iab-html-rfc-02: references Paul Hoffman
- [rfc-i] draft-iab-html-rfc-02: references Julian Reschke
- [rfc-i] draft-iab-html-rfc-02: references Paul Hoffman
- [rfc-i] draft-iab-html-rfc-02: references Julian Reschke
- [rfc-i] draft-iab-html-rfc-02: references Joe Hildebrand jhildebr
- [rfc-i] draft-iab-html-rfc-02: references Joe Hildebrand jhildebr
- [rfc-i] draft-iab-html-rfc-02: references Joe Hildebrand jhildebr
- [rfc-i] draft-iab-html-rfc-02: references Paul Hoffman
- [rfc-i] draft-iab-html-rfc-02: references Julian Reschke
- [rfc-i] draft-iab-html-rfc-02: references HANSEN, TONY L
- [rfc-i] draft-iab-html-rfc-02: references Paul Hoffman
- [rfc-i] draft-iab-html-rfc-02: references Joe Hildebrand jhildebr
- [rfc-i] draft-iab-html-rfc-02: references Julian Reschke
- [rfc-i] draft-iab-html-rfc-02: references Julian Reschke
- [rfc-i] draft-iab-html-rfc-02: references Paul Hoffman
- [rfc-i] draft-iab-html-rfc-02: references Joe Hildebrand jhildebr
- [rfc-i] draft-iab-html-rfc-02: references Julian Reschke
- [rfc-i] draft-iab-html-rfc-02: references Paul Hoffman
- [rfc-i] draft-iab-html-rfc-02: references Joe Hildebrand jhildebr
- [rfc-i] draft-iab-html-rfc-02: references Joe Hildebrand jhildebr
- [rfc-i] draft-iab-html-rfc-02: references HANSEN, TONY L
- [rfc-i] draft-iab-html-rfc-02: references Julian Reschke
- [rfc-i] draft-iab-html-rfc-02: references Martin J. Dürst
- [rfc-i] draft-iab-html-rfc-02: references Julian Reschke