Re: [MMUSIC] draft-ietf-mmusic-rfc4566bis-10: can attributes have a null value

[Brett Tate <[e-mail]>]

> Given how established SDP is, I think we need to be careful about
> *how* we clarify it, to minimize compatibility issues.

I agree.  One option is potentially to keep it invalid.  A comment
potentially could be added indicating that RFC 3611 is a reason to
accommodate the unexpected ABNF expansion (i.e. sender not updated to
comply with the errata).

> The referenced erratum says that for one particular attribute the
> colon is required even if there is no value after it. And the proposed
> fix is to only permit the colon if there is a value.

Errata 3795's proposed fix to RFC 3611 would allow the ABNF to comply with
RFC 4566.

> I think we should at least *consider* changing it to:
>
>     attribute =           att-field [ ":" [att-value] ]
>
> It would be good to hear from anybody who thinks this change
> would be troublesome.

It would cause the rfc4566bis attribute ABNF to not be backward compatible
with RFC 4566 devices.

This could cause issues with some RFC 4566 devices; however some already
accommodate it for interoperability reasons.

Thanks,
Brett