[AVTCORE] draft-ietf-avtcore-rfc5285-bis-11.txt - new text for bundle case

Roni Even <roni.even@huawei.com> Thu, 18 May 2017 11:15 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695E812E3AE for <avt@ietfa.amsl.com>; Thu, 18 May 2017 04:15:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level:
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id la1728aEIigG for <avt@ietfa.amsl.com>; Thu, 18 May 2017 04:15:54 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66A6512949F for <avt@ietf.org>; Thu, 18 May 2017 04:11:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNH31437; Thu, 18 May 2017 11:11:00 +0000 (GMT)
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 18 May 2017 12:10:58 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.49]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0301.000; Thu, 18 May 2017 19:10:42 +0800
From: Roni Even <roni.even@huawei.com>
To: Roni Even <roni.even@huawei.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: draft-ietf-avtcore-rfc5285-bis-11.txt - new text for bundle case
Thread-Index: AdLPxyMuz+YWFcXDRVedJ3p+i/n0dA==
Date: Thu, 18 May 2017 11:10:42 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7CC7D1@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.201.202]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0201.591D8145.0163, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.49, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: d81068b2d0e6f13833efb4be93ecaa02
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/54mLAb-I1cQCMHttG3IYQDAYbXU>
Subject: [AVTCORE] draft-ietf-avtcore-rfc5285-bis-11.txt - new text for bundle case
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 May 2017 11:15:55 -0000

Hi,

 I suggest adding the following text to section 6

When used in [bundle] this attribute is specified as normal category for the [mux attribute]. This allows for only a subset of the m-lines in the bundle group to offer extmap-allow-mixed. When an answerer supporting the extmap-allow-mix attribute receives an offer where only some of the m-lines in the bundle group include the extmap-allow-mixed attribute, the answerer must receive this offer and support mixed one-byte and two-bytes only for those m-lines.  



And the following text to section 7

When using [bundle] to bundle multiple m-lines the extmap attribute falls under the special category of [mux attribute]. 
All the m-lines in a bundle group are considered to be part of the same local identifier (ID) space.  If an extension URI is offered in multiple m-lines the same attributes as part of the same bundle group it MUST use the same ID in all this m-lines. Each m-line in a bundle group can include different extension URIs allowing for example audio and video sources to use different sets of RTP header extensions. The directionality of the RTP header extensions in each m-line of the bundle group are handled as the non-bundled case. This allows for specifying different directionality for each of the repteated extension URI in bundled group.


Roni Even