[MMUSIC] IANA section review of draft-ietf-mmusic-sdp-mux-attributes-10

[Bo Burman <[e-mail]>]

I have reviewed the IANA section (15) of this draft and have the following comments:

In section 5.47; "alt-group" is inconsistent with IANA table, where it is defined as session level.

In section 5.54; "T38FaxMaxIFP", "T38FaxUdpECDepth", "T38UdpFECMaxSpan", and "T38ModemType" are all inconsistent with IANA, where they are defined as media level.

In section 9.1; Editorial: missing ":" in "ssrc-groupFEC-FR"

In section 15.1; suggest clarifying what it means to "indicate the applicability" of a newly defined multiplexing category value to various sub-registries is detailed a bit more, e.g. that such new multiplexing category can replace the assigned category defined in this document, if that is the intent, and in that case what it means (e.g. for interoperability) to change the category for an attribute.

In section 15.2.2; "rtsp-ice-d-m" is not discussed anywhere else in the document; should it be?

In section 15.2.3; "qos-mech-send" and "qos-mech-recv" are here both listed as NORMAL, which is inconsistent with the categorization TRANSPORT in section 5.6. The current table ends with "calgextmap", but the IANA table continues with "phone-context", "clir", "Q763-nature", "Q763-plan", "Q763-INN", "require", "record", and "recordpref", some of which refer quite old RFCs. Why are those not included in the table?

In section 15.2.4; "codecConfig" is inconsistent with IANA value that does not use a capital C in the middle: "codecconfig". The IANA table now also has "predefined_ROI", which should then be added.

In section 15.2.7; "DDP" is listed here, but is not mentioned or motivated in section 8.5, which would be reasonable considering that "DUP" is discussed in section 8.6.

In section 15.2.8; What does it really mean when "rtcp-fb" attribute as such is defined as IDENTICAL-PER-PT, but a certain parameter (here "app") is assigned another category (here "SPECIAL")? Does the parameter override the attribute-wide default? Is this principle described somewhere? The IANA table now also contains "3gpp-roi-arbitrary" and "3gpp-roi-predefined", which should then be added.

In section 15.2.9; Same comment regarding override as for 15.2.8, for both "app" and "ecn" values.

In section 15.2.14; IANA table now also contains "pause", which should then be added.

In section 15.2.16; Editorial: Table heading "QoS Mechanism" seems to be copy-pasted from 15.2.15, but should probably instead be "Value Name" or something similar.

In section 15.2.17; The names listed in the table are not mentioned or motivated in section 5.16 - should they be?

In section 15.2.18; Same comment as for section 15.2.17.

Cheers,
Bo