Re: [MMUSIC] BUNDLE TEXT: nettype/addrtype restriction [was: Draft new version: draft-ietf-mmusic-sdp-bundle-negotiation-05]

Hello Christer,

It looks OK to me.

Regards, Christian
On 13/11/2013 10:08 AM, Christer Holmberg wrote:
> Hi,
>
> Based on the comments from Christian, I suggest the following new text for BUNDLE:
>
> -----------------------------
>
> 6.2.2.  Connection Data (c=)
>
>     The "c=" line nettype value [RFC4566] associated with each "m=" line
>     within a BUNDLE group MUST be 'IN'.
>
>     The "c=" line addrtype value [RFC4566] associated with each "m=" line
>     within a BUNDLE group MUST be 'IP4' or 'IP6'.  The same value MUST be
>     associated with each "m=" line within a BUNDLE group.
>
>     NOTE: Extensions to this specification can specify usage of the
>     BUNDLE mechanism for other nettype and addrtype values than the ones
>     listed above.
>
> -----------------------------
>
> Regards,
>
> Christer
>
>
>
>
> -----Alkuperäinen viesti-----
> Lähettäjä: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] Puolesta Christian Groves
> Lähetetty: 15. lokakuuta 2013 3:05
> Vastaanottaja: mmusic@ietf.org
> Aihe: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sdp-bundle-negotiation-05
>
> Hello Christer,
>
> The SDP grouping mechanism can be applied to different nettype/addrtypes. The BUNDLE draft appears to define behaviour related only to the nettype=IN and addrtypes=IPv4/IPv6. i.e. section 2 defines BUNDLE terminology based on IP.
>
> Is there an intention that the BUNDLE mechanism is only used for the above net and addrtypes? If so should it be mentioned somewhere in the applicability statement?
>
> Regards, Christian
>
> On 14/10/2013 10:37 PM, Christer Holmberg wrote:
>> Hi,
>>
>> I've submitted a new version of the BUNDLE draft.
>>
>> I have implemented the modified text for the Offerer and Answerer
>> procedures, as presented on the list in September.
>>
>> The procedures now also mention the usage of the SDP 'bundle-only'
>> attribute. However, the attribute definition itself has yet not been
>> added to the draft, as we still haven't solved the issue regarding
>> usage of port zero.
>>
>> In addition, there are some reference corrections, and the FQDN values
>> in the examples are now according to RFC 2606.
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>