Re: [AVTCORE] [rtcweb] Replacing a=extmap mapping in re-offer, is it legal?

Roni Even <roni.even@huawei.com> Wed, 09 August 2017 13:43 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 5F0111320B5; Wed, 9 Aug 2017 06:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 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, 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 8aLpRjti1599; Wed, 9 Aug 2017 06:43:56 -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 60F60131EB2; Wed, 9 Aug 2017 06:43:55 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DTA90744; Wed, 09 Aug 2017 13:43:53 +0000 (GMT)
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 9 Aug 2017 14:43:51 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.170]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0301.000; Wed, 9 Aug 2017 21:43:29 +0800
From: Roni Even <roni.even@huawei.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Iñaki Baz Castillo <ibc@aliax.net>, Taylor Brandstetter <deadbeef@google.com>
CC: "rtcweb@ietf.org" <rtcweb@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [rtcweb] Replacing a=extmap mapping in re-offer, is it legal?
Thread-Index: AQHTD4ZeWfNzICrgU0mNlPq2aeHenKJ47jTA///hPQCAADoWAIAAAq8AgAAizfCAAjDagIAAlitggAAUltA=
Date: Wed, 09 Aug 2017 13:43:29 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7F2006@DGGEMM506-MBX.china.huawei.com>
References: <CALiegf=_3XV9NnEzi4e6Tb=d5KiqpjtH09grrEzZvWrbaDOcxw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4CCB17B5@ESESSMB109.ericsson.se> <CALiegf=_W=ma9w0o6J9sa6fAfNLw0Zc7d9nMb+nOs6cS-9C5QQ@mail.gmail.com> <CAK35n0Zph3cWjkmP3Usep6QZLaCxSqe2wof0FsAjrkcx9s5QUg@mail.gmail.com> <CALiegf=4vV9wxXKE+GQCd_34ocVQvHXpYLCjXFkeCupBuWn8nA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4CCB2093@ESESSMB109.ericsson.se> <6E58094ECC8D8344914996DAD28F1CCD7F1F02@DGGEMM506-MBX.china.huawei.com> <7594FB04B1934943A5C02806D1A2204B4CCB5B07@ESESSMB109.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4CCB5B07@ESESSMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.51]
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.0A090204.598B1199.00FA, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.170, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: df59ab82d8b2f00f103ccea64c6b2d4e
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/SKNWtgLs1sbIp5A0gIY2eaDqFO8>
Subject: Re: [AVTCORE] [rtcweb] Replacing a=extmap mapping in re-offer, is it legal?
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: Wed, 09 Aug 2017 13:43:58 -0000

Hi Christer,
Inline, cc avtcore since it is avtcore document .
Look at https://tools.ietf.org/html/draft-ietf-avtcore-rfc5285-bis-14#section-7 
Roni

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: יום ד 09 אוגוסט 2017 15:27
> To: Roni Even; Iñaki Baz Castillo; Taylor Brandstetter
> Cc: rtcweb@ietf.org
> Subject: RE: [rtcweb] Replacing a=extmap mapping in re-offer, is it legal?
> 
> Hi,
> 
> >> Taylor's explanation makes sense. But, in this case:
> >>
> >> 1) Re-using the same value with a new mapping should be an explicit
> >> MUST NOT
> >[Roni Even] This is specified in RFC5285 section 6
> >
> >Identifiers values in the valid range MUST NOT  be altered (remapped).
> 
> Correct. Taylor indicated this earlier.
> 
> What if a previously negotiated mapping is not included at all in a subsequent
> offer?

[Roni Even] It is removed not supported "A session update MAY add or  remove extension(s)."

 Is it considered an error?

[Roni Even] no

 If not, does the previous mapping apply? 
[Roni Even] if you want to use it you can consider making it inactive

Or,
> is the previous mapping removed?
[Roni Even] removed but you cannot use the same ID for another extension

> 
> Regards,
> 
> Christer
> 
> 
> 
> > From: Iñaki Baz Castillo [mailto:ibc@aliax.net]
> > Sent: 07 August 2017 19:56
> > To: Taylor Brandstetter <deadbeef@google.com>
> > Cc: Christer Holmberg <christer.holmberg@ericsson.com>;
> > rtcweb@ietf.org
> > Subject: Re: [rtcweb] Replacing a=extmap mapping in re-offer, is it legal?
> >
> > On Mon, Aug 7, 2017 at 7:46 PM, Taylor Brandstetter
> > <deadbeef@google.com> wrote:
> > > I don't know if this is stated explicitly anywhere, but my
> > > assumption was that it works like payload types. You can introduce
> > > new IDs all you want, but you can't have one ID refer to multiple
> > > things during the
> > same session.
> > > Otherwise, if you receive a packet with that extension ID, you
> > > wouldn't be able to tell which extension it is.
> > >
> > > Meaning, if Bob's initial answer was:
> > >
> > > a=extmap:11 http://www.webrtc.org/experiments/rtp-hdrext/abs-
> send-
> > time
> > >
> > > It would be illegal to have a re-offer of:
> > >
> > > a=extmap:1 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-
> > time
> > > a=extmap:11 urn:ietf:params:rtp-hdrext:toffset
> > >
> > > Because if Bob then receives a packet with extension ID 11, Bob
> > > doesn't know if it's a packet sent before Alice received the answer
> > > (in which case it's "abs-send-time"), or after (in which case it's "toffset").
> >
> > Thanks, your rationale clearly makes sense. However:
> >
> > 1) I don't think Firefox cares about overriding a previous extmap ID
> > during a reoffer.
> >
> > 2) Should we really accept so complex and error prune things just
> > because SDP allows everything?
> >
> >
> > --
> > Iñaki Baz Castillo
> > <ibc@aliax.net>
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb