[MMUSIC] draft-ejzak-mmusic-data-channel-sdpneg: make "subprotocol" optional in dcmap

"Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com> Tue, 02 December 2014 16:31 UTC

From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-ejzak-mmusic-data-channel-sdpneg: make "subprotocol" optional in dcmap
Thread-Index: AdAOOh4XGrrUYNLGRo+3IKnmkB+//Q==
Date: Tue, 02 Dec 2014 16:30:45 +0000
Deferred-Delivery: Tue, 2 Dec 2014 16:30:00 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17828E648763@US70UWXCHMBA02.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/SCiW34pXVtY7-sYJJZBOBDIxQRM
Subject: [MMUSIC] draft-ejzak-mmusic-data-channel-sdpneg: make "subprotocol" optional in dcmap
Precedence: list

Section 5.1.1.3 says "subprotocol" is a mandatory parameter.
However, "5.1.  DATA_CHANNEL_OPEN Message" of draft-ietf-rtcweb-data-protocol (DCEP) says the subprotocol can be empty (i.e. unspecified).

We also foresee draft-ejzak-mmusic-data-channel-sdpneg to be used for cases where stream id is negotiated while subprotocol is unspecified.

To align it with DCEP and to allow the above use case, we want to make the subprotocol optional in dcmap.
Existing text in 5.1.1.3 
"Subprotocol is a mandatory parameter."
will be changed to
"Subprotocol is a an optional parameter. If the subprotocol parameter is not present, then its value defaults to empty string"

Please let us know if you have any objections to this.

Thanks
Raju

Re: [MMUSIC] draft-ejzak-mmusic-data-channel-sdpn… Christer Holmberg
[MMUSIC] draft-ejzak-mmusic-data-channel-sdpneg: … Makaraju, Maridi Raju (Raju)