Draft: draft-ietf-quic-qpack

Commentary: Two things : Links are better as than as the latter puts the link in the text output twice ( HTML is fine ) . Boilerplate is more concise if we let kramdown - rfc2629 add it . 
 : heart : , gon na borrow that one
Paragraph (version A):
Working Group information can be found at https://github.com/quicwg
[2]; source code and issues list for this draft can be found at
https://github.com/quicwg/base-drafts/labels/-qpack [3].
Paragraph (version B):
Working Group information can be found at <https://github.com/
quicwg>; source code and issues list for this draft can be found at
<https://github.com/quicwg/base-drafts/labels/-qpack>.
Paragraph (version A):
Working Group information can be found at https://github.com/quicwg
[2]; source code and issues list for this draft can be found at
https://github.com/quicwg/base-drafts/labels/-http [3].
Paragraph (version B):
Working Group information can be found at <https://github.com/
quicwg>; source code and issues list for this draft can be found at
<https://github.com/quicwg/base-drafts/labels/-http>.
Paragraph (version A):
Non-compatible experiments that are based on these draft versions
MUST append the string "-" and an experiment name to the identifier.
For example, an experimental implementation based on draft-ietf-quic-
http-09 which reserves an extra stream for unsolicited transmission
of 1980s pop music might identify itself as "h3-09-rickroll".  Note
that any label MUST conform to the "token" syntax defined in
Section 4.4.1.1 of SEMANTICS.  Experimenters are encouraged to
coordinate their experiments on the quic@ietf.org mailing list.
Paragraph (version B):
Non-compatible experiments that are based on these draft versions
MUST append the string "-" and an experiment name to the identifier.
For example, an experimental implementation based on draft-ietf-quic-
http-09 which reserves an extra stream for unsolicited transmission
of 1980s pop music might identify itself as "h3-09-rickroll".  Note
that any label MUST conform to the "token" syntax defined in
Section 4.4.1.1 of SEMANTICS.  Experimenters are encouraged to
coordinate their experiments on the quic@ietf.org [2] mailing list.
Paragraph (version A):
HTTP messages carry metadata as a series of key-value pairs, called
HTTP fields.  For a listing of registered HTTP fields, see the
"Hypertext Transfer Protocol (HTTP) Field Name Registry" maintained
at https://www.iana.org/assignments/http-fields/ [4].
Paragraph (version B):
HTTP messages carry metadata as a series of key-value pairs, called
HTTP fields.  For a listing of registered HTTP fields, see the
"Hypertext Transfer Protocol (HTTP) Field Name Registry" maintained
at <https://www.iana.org/assignments/http-fields/>.
Paragraph (version A):
Working Group information can be found at https://github.com/quicwg
[2]; source code and issues list for this draft can be found at
https://github.com/quicwg/base-drafts/labels/-invariants [3].
Paragraph (version B):
Working Group information can be found at <https://github.com/
quicwg>; source code and issues list for this draft can be found at
<https://github.com/quicwg/base-drafts/labels/-invariants>.
Paragraph (version A):
Working Group information can be found at https://github.com/quicwg
[2]; source code and issues list for this draft can be found at
https://github.com/quicwg/base-drafts/labels/-recovery [3].
Paragraph (version B):
Working Group information can be found at <https://github.com/
quicwg>; source code and issues list for this draft can be found at
<https://github.com/quicwg/base-drafts/labels/-recovery>.
Paragraph (version A):
Working Group information can be found at https://github.com/quicwg
[2]; source code and issues list for this draft can be found at
https://github.com/quicwg/base-drafts/labels/-tls [3].
Paragraph (version B):
Working Group information can be found at <https://github.com/
quicwg>; source code and issues list for this draft can be found at
<https://github.com/quicwg/base-drafts/labels/-tls>.
Paragraph (version A):
Discussion of this draft takes place on the QUIC working group
mailing list (quic@ietf.org), which is archived at
<https://mailarchive.ietf.org/arch/search/?email_list=quic>.
Paragraph (version A):
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 RFC2119 RFC8174 when, and only when, they appear in all capitals,
as shown here.
Paragraph (version A):
All registrations in this document are assigned a permanent status
and list as contact both the IESG (ietf@ietf.org) and the QUIC
working group (quic@ietf.org).
Paragraph (version B):
All registrations in this document are assigned a permanent status
and list as contact both the IESG (ietf@ietf.org) and the QUIC
working group (quic@ietf.org [2]).
Paragraph (version B):
The initial contents of this registry are shown in iana-error-table.