Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29th May)

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Thu, 30 May 2013 17:38 UTC

Return-Path: <fluffy@cisco.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 BDCBA21F9354 for <mmusic@ietfa.amsl.com>; Thu, 30 May 2013 10:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.179
X-Spam-Level:
X-Spam-Status: No, score=-110.179 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_56=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 rwF9GykwCvwl for <mmusic@ietfa.amsl.com>; Thu, 30 May 2013 10:38:50 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 7376421F941D for <mmusic@ietf.org>; Thu, 30 May 2013 10:38:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5255; q=dns/txt; s=iport; t=1369935526; x=1371145126; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=G4Dzb7n2JCs+MOYKDboAfIQx3ZI6VcxX8opoxfxMfME=; b=QxBAVHWOaMNrxNYLsUbbAOadYVzDAtdggKdyBdNlTtCsxXuQOpOCCeDB K8pe8jtnTp4XlCIjDsC+eNAEwpHK4g3EuZvhpS0ztAJ4A5f7X8FrcP+H3 fZW5R+L5kK1jQ0mWKcgo/b56PwfYZJAOPGG9amGF4W5jdcM+s8cGZ6J57 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAKSNp1GtJXG//2dsb2JhbABZgwkwwhZ+FnSCIwEBAQMBAQEBawsFCwIBCCIkJwslAgQOBQiHfwYMu2gEjWp/AjEHgnZhA4wykhyKMIMPgXE2
X-IronPort-AV: E=Sophos;i="4.87,772,1363132800"; d="scan'208";a="213874795"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-9.cisco.com with ESMTP; 30 May 2013 17:38:45 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r4UHcjxS021276 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 May 2013 17:38:45 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.36]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.004; Thu, 30 May 2013 12:38:45 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29th May)
Thread-Index: AQHOXVyIByzNcym6vEWUaYu7/MrJxA==
Date: Thu, 30 May 2013 17:37:48 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB11352446E@xmb-aln-x02.cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B1C37B973@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C37B973@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <ACA97AFC444ABB419698CD567219E2B6@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29th May)
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: Thu, 30 May 2013 17:38:55 -0000

Looks good to me

On May 29, 2013, at 5:39 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:

> Hi,
>  
> Based on the e-mail and interim discussions, I’ve tried together some ”Answerer Procedures” text for BUNDLE.
>  
> For now, I would request that people mainly focus on the technical stuff, and if some text is unclear. I WILL align the usage of “m=” line and “media description” :)
>  
> Also note that examples will be added later.
>  
> Regards,
>  
> Christer
>  
> -----------------------------------------------------
>  
>  
> 6.4.  Answerer Procedures
>  
> 6.4.1.  General
>  
>    This section describes how an Answerer, when it receives an SDP Offer
>    including a BUNDLE group, generates the associated SDP Answer.
>  
>    When an Answerer receives an SDP Offer which includes a BUNDLE group,
>    and the Answerer accepts the offered BUNDLE group, the Answerer MUST
>    generate an SDP Answer according to the procedures in Section 6.1 and
>    this section.
>  
> 6.4.2.  RFC 5888 restrictions
>  
>    Based on the rules and procedures in RFC 5888, the following
>    restrictions also apply to BUNDLE groups in SDP Answers:
>  
>    o  1) A BUNDLE group must not be added to an SDP Answer, unless the
>       same BUNDLE group was included in the associated SDP Offer; and
>  
>    o  2) An SDP "m=" line must not be added to a BUNDLE group in the SDP
>       Answer, unless it in the associated SDP Offer was included in the
>       same BUNDLE group.
>  
> 6.4.3.  Offerer Bundle Address Selection
>  
>    In the SDP Answer, the Answerer selects the bundle address for the
>    Offerer, based on the address information received in the associated
>    SDP Offer, using the mid value.  The mid value associated with the
>    "m=" line in the SDP Offer that represents the bundle address MUST in
>    the SDP Answer be located first in the mid value list added to SDP
>    group:BUNDLE attribute associated with the BUNDLE group.
>  
>    From the associated SDP Offer, the Answerer SHOULD choose the bundle
>    address associated with the mid value located first in the mid value
>    list included in the SDP group:BUNDLE attribute associated with the
>    BUNDLE group, unless:
>  
>    o  1) The mid value represents an "m=" line with a port zero value in
>       the SDP Offer; or
>  
>    o  2) The mid value represents an "m=" line with a port zero value in
>       the SDP Answer.
>  
>    OPEN: The decision for allowing a media description with port zero
>    values inside a BUNDLE group is pending on update for RFC 5888.
>  
> 6.4.4.  Answerer Bundle Address Selection
>  
>    In the SDP Answer, the Answerer selects its local bundle address.
>    Each "m=" line included in a BUNDLE group MUST contain identical
>    address information.  The only exception is the usage of a zero port
>    value for an "m=" line, which is allowed eventhough another port
>    value number is used for other "m=" lines in the BUNDLE group.
>  
>    OPEN: The decision for allowing a media description with port zero
>    values inside a BUNDLE group is pending on update for RFC 5888.
>  
>    In a subsequent SDP Answer, the Answerer MAY change its local bundle
>    address, as long as each "m=" line included the BUNDLE group contain
>    identical address information.
>  
>    For a given BUNDLE group, the Answerer MUST NOT assign the bundle
>    address to "m=" lines that are not included the BUNDLE group, or to
>    "m=" lines that are included in another BUNDLE group.
>  
> 6.4.5.  Rejecting A BUNDLE Media Description
>  
>    When generating the SDP Answer, if the Answerer wants to reject media
>    associated with an "m=" line in the BUNDLE group, it will add a zero
>    port number value to the "m=" line, according to the procedures
>    defined in RFC 3264.
>  
>    OPEN ISSUE: It is FFS whether it is allowed to include a port zero
>    media descriptions in a BUNDLE group.
>  
> 6.4.6.  Removing a media description from a BUNDLE group
>  
>    When generating the SDP Answer, if the Answerer wants to remove an
>    "m=" line from a BUNDLE group (without rejecting the "m=" line),it
>    MUST NOT include the "m=" line in a BUNDLE group.  In addition, the
>    SDP Answer MUST not add its local bundle address to the "m=" line.
>  
>    An Answerer MUST NOT, in the SDP Answer, remove an "m=" line from a
>    BUNDLE group, unless the "m=" line had unique address information in
>    the associated SDP Offer.
>  
>    NOTE: The reason for the restriction above is that, if the "m=" line
>    would be removed from the BUNDLE group, the address information would
>    be identical to the "m=" lines remaining in the BUNDLE group.
>  
>    OPEN: The decision for allowing a media description with port zero
>    values inside a BUNDLE group is pending on update for RFC 5888.
>  
>  
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic