Re: [MMUSIC] BUNDLE DECISSION: SDP Answer Restrictions

Suhas Nandakumar <suhasietf@gmail.com> Fri, 24 May 2013 21:47 UTC

Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B7C621F9649 for <mmusic@ietfa.amsl.com>; Fri, 24 May 2013 14:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level:
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxfMzg-yD4qu for <mmusic@ietfa.amsl.com>; Fri, 24 May 2013 14:47:22 -0700 (PDT)
Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 296B911E80E2 for <mmusic@ietf.org>; Fri, 24 May 2013 14:47:22 -0700 (PDT)
Received: by mail-qa0-f46.google.com with SMTP id bv4so160862qab.19 for <mmusic@ietf.org>; Fri, 24 May 2013 14:47:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Kbl/50jmr1lS+LTlABG2NFLjq3Ty8MEEjF0UJRg3Ces=; b=ya74uGghJM/8IEBzGVTVhZFKZRNlMdM2cItrqmKyg2AIl1BR1NG8W2/sXAbqFlHXRy AriKm6luJZWKOrfSDh4QRTn8Jm5acHZ+LYE3kP2QAhWBoHSoRH+aFwqCP21ITjlujwrm b733xx51/tyBl92n49+HT+oyKKlZEXcbXx51oF2zPYPlRK2XFV250Lz9RbvC66Lv+Uh3 +EDP3mnnApM3Ne0nrA2aG28+x+xEk6tDpnyYfHC4JODU8Hq4ZreS+DKaoIKZBpcCyXVR TUpMktPETe+DzWC8B6ERU9n/J/C1HQqIPWmy5DXJMv1fFhvTWAe/+WwqM1fIwmPo3oM0 BxDQ==
MIME-Version: 1.0
X-Received: by 10.49.60.98 with SMTP id g2mr21014373qer.51.1369432041625; Fri, 24 May 2013 14:47:21 -0700 (PDT)
Received: by 10.49.6.97 with HTTP; Fri, 24 May 2013 14:47:21 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C377967@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C377967@ESESSMB209.ericsson.se>
Date: Fri, 24 May 2013 14:47:21 -0700
Message-ID: <CAMRcRGSNoDNadgHApfak5xj1pXjXvErUUu+hFqKH=JBuH_+oKA@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=047d7b62450c62b7bb04dd7dbe85
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE DECISSION: SDP Answer Restrictions
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 21:47:23 -0000

Hi Christer

  Please find my comments in line.

On Fri, May 24, 2013 at 5:32 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>  Hi,****
>
> ** **
>
> At the interim meeting yesterday, we agreed on some restrictions regarding
> creating SDP answers containing bundle group(s).****
>
> ** **
>
> Note that the restrictions 1-3 are simply alignments with RFC 5888, and
> are listed simply for clarification purpose. Restrictions 4 is BUNDLE
> specific. Restriction 5 is also alignment with RFC 5888, as m- lines with
> port zero are not allowed within groups, but we will need some
> clarification text saying that a new offer will have to be sent in order to
> remove a stream (either from a bundle group, or completely from the
> session).****
>
> ** **
>
> (Note that the text below is not necessarily the wording that will go into
> the draft)****
>
> ** **
>
> In an SDP answer:****
>
> **1)      **a BUNDLE group MUST NOT be created, unless it was included in
> the associated offer****
>
> **2)      **an m- line MUST NOT be added to a BUNDLE group, unless it was
> included in a BUNDLE group in the associated offer****
>
> **3)      **an m- line MUST NOT be added to another BUNDLE group than the
> group in which was included in the associated offer****
>
> **4)      **an m- line MUST NOT be removed from a BUNDLE group if, in the
> associated offer, an identical port number was indicated for all m- lines
> in a BUNDLE group****
>
> **
>
  [Suhas]  .. RFC5888 doesn't clarify what does removing means. Hence, I
would be happy to see 4)
                  If a m-line is removed ( not rejected) in the Answer,
then the m-line should include a unique port that doesn't collide with port
associated with any BUNDLE groups.

5)      **an m- line MUST NOT be rejected if, in the associated offer, an
> identical port number was indicated for all m- lines in a BUNDLE group****
>
> **
>
 [Suhas]. I agree with Paul here. Rejecting a m-line MUST be allowed by the
answerer by setting port to zero and removing mid from the BUNDLE group
attribute line. This is special case where BUNDLE should be satisfied if
            a) Either all the port are identical
            b) Ports in the BUNDLE group can be zero (if rejected).

>  **
>
> ** **
>
> Note that there is also a discussion regarding bundle offers, e.g. when
> restrictions when adding new m- lines to a bundle. Based on the outcome of
> that, there may be some additional answer restrictions, e.g. regarding the
> change of bundle transport parameters. But, let’s deal with that in the
> offer thread.
>

 [Suhas] Agreed.


> So, if anyone OBJECTS to the restrictions above, please indicate so.****
>
> ** **
>
> Regards,****
>
> ** **
>
> Christer****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>