[AVTCORE] Need feedback on RFC5285bis (RTP header extensions) comments
Roni Even <roni.even@huawei.com> Wed, 01 February 2017 10:42 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 E10D3129D18 for <avt@ietfa.amsl.com>; Wed, 1 Feb 2017 02:42:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.419
X-Spam-Level:
X-Spam-Status: No, score=-7.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, 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 nuUdXkdvp78W for <avt@ietfa.amsl.com>; Wed, 1 Feb 2017 02:42:55 -0800 (PST)
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 66FE9129424 for <avt@ietf.org>; Wed, 1 Feb 2017 02:42:54 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DFP31179; Wed, 01 Feb 2017 10:42:52 +0000 (GMT)
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml701-cah.china.huawei.com (10.201.5.93) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 1 Feb 2017 10:42:50 +0000
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.117]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0301.000; Wed, 1 Feb 2017 18:42:44 +0800
From: Roni Even <roni.even@huawei.com>
To: IETF AVTCore WG <avt@ietf.org>
Thread-Topic: Need feedback on RFC5285bis (RTP header extensions) comments
Thread-Index: AdJ8cvwqQ20XYkJqScm51Efh6qfqvg==
Date: Wed, 01 Feb 2017 10:42:42 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD770167@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.150]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD770167DGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090204.5891BBAC.0131, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.117, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: ac2151dff37877f5ba5a64be817e2399
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/CPrW22XBf0U3qkX-rPFGyryDSwI>
Cc: David Singer <singer@apple.com>
Subject: [AVTCORE] Need feedback on RFC5285bis (RTP header extensions) comments
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 01 Feb 2017 10:42:59 -0000
Hi, Paul made a very thorough SDP review and had some comments on which I am looking for feedback. 1. In section 7 "If an extension is marked as "sendonly" and the answerer desires to receive it, the extension MUST be marked as "recvonly" in the SDP answer. An answerer that has no desire to receive the extension or does not understand the extension SHOULD remove it from the SDP answer." . Is there a reason for the "SHOULD" here or should we change it to "MUST" or maybe if not removed to respond with "inactive" or "sendonly" if want to send and and not receive? 2. In this case if the offer is refused by removing the extmap line, can the ID be re-used? 3. In section 7 "Local identifiers in the valid range inclusive in an offer or answer MUST NOT be used more than once per media section (including the session-level section). A session update MAY change the direction qualifiers of extensions under use. A session update MAY add or remove extension(s). Identifiers values in the valid range MUST NOT be altered (remapped)." Paul asked what is the scope over which identifiers must not be altered. His thought was only for the current RTP session so when a call is transferred (one party is still in the call) they may be altered. Any thoughts? 4. Is it valid to use IDs in the (unusable) range in answers? (I guess that would give the offerer info that it could use in a future offer.). I am not sure what was meant here. Is it an answer to an offer with an ID in the valid range? Or is it about keeping an alternative from the offer with the unusable space and not remove it? I assume that the answer cannot add extensions to the ones in the offer, will need a new offer for that. 5. May values from the (unused) range that are used in offers (or answers) be reused differently in subsequent offers? 6. Would the following be valid? (Only the directionality differs.) OFFER: a=extmap:4096/sendonly http://example.com/082005/ext.htm#opt1 a=extmap:4096/recvonly http://example.com/082005/ext.htm#opt1 7. Is it allowed to use the "alternatives" mechanism with only a single alternative? This would be a way to avoid "wasting" an ID value until you know if your peer supports the option. I see this usage in an example, but it is not mentioned in text. If this is an intended usage then it would be good to provide some further explanation. Thanks Roni Even As the document editor.
- [AVTCORE] Need feedback on RFC5285bis (RTP header… Roni Even
- Re: [AVTCORE] Need feedback on RFC5285bis (RTP he… Paul Kyzivat
- Re: [AVTCORE] Need feedback on RFC5285bis (RTP he… Dale R. Worley
- Re: [AVTCORE] Need feedback on RFC5285bis (RTP he… Roni Even
- Re: [AVTCORE] Need feedback on RFC5285bis (RTP he… Dale R. Worley
- Re: [AVTCORE] Need feedback on RFC5285bis (RTP he… Magnus Westerlund
- Re: [AVTCORE] Need feedback on RFC5285bis (RTP he… Iñaki Baz Castillo
- Re: [AVTCORE] Need feedback on RFC5285bis (RTP he… Iñaki Baz Castillo