[AVTCORE] draft-ietf-avtcore-rtp-over-quic: Normative references to Internet Drafts

[Bernard Aboba <[e-mail]>]

With the QUIC specifications still evolving, this specification is put in a
difficult position.  Beyond the basic QUIC specifications, there are
extensions which could be of potential benefit.  However, some of the
extensions are not yet WG work items, or are not widely deployed, or may
take some time to be published as RFCs, or may never be published as RFCs.

Currently, the document has an Appendix A: List of Optional QUIC
extensions, which states "The following is a list of QUIC protocol
extensions that might be beneficial for RoQ, but are not required by RoQ."
Putting discussion of non-RFC QUIC extensions into a (non-normative)
Appendix seems like a good idea, if it could allow the main specification
to focus on the core QUIC functionality and avoid normative references to
documents which may or may not ever be published as RFCs.

However, the problem is that discussion of the extensions is not limited to
the (non-normative) Appendix, but is contained in other sections, including
Sections 7, 7.3.4 and 8.1.

This results in normative references to [I-D.draft-huitema-quic-ts],
[I-D.draft-ietf-quic-ack-frequency] and [I-D.draft-smith-quic-receive-ts]. ¶
<https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtp-over-quic-05#appendix-A-1>



I would like to suggest that the RTP over QUIC specification be
restructured so as to only normatively reference documents which have been
published as RFCs.

For this to work, material in Sections 7 and 8 may need to be moved to
Appendix A, which would presumably avoid normative references.