Re: [MMUSIC] 4566bis-36: Ignoring/rejecting session description that contains unknown letter

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 26 July 2019 20:10 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 4E3951203A3 for <mmusic@ietfa.amsl.com>; Fri, 26 Jul 2019 13:10:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=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 EjCwE2U7pg-f for <mmusic@ietfa.amsl.com>; Fri, 26 Jul 2019 13:10:16 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5D81120368 for <mmusic@ietf.org>; Fri, 26 Jul 2019 13:10:16 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x6QKACRm029911 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 26 Jul 2019 16:10:12 -0400
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <FD3AE0AD-E9BA-48B1-8DF7-E35D67866F16@ericsson.com> <8f3027b7-7efe-dd6a-0afb-475c36042f20@alum.mit.edu> <HE1PR07MB31617B7C4E2BEED45A41ACBE93C00@HE1PR07MB3161.eurprd07.prod.outlook.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <9fc337ad-60e1-db46-133d-396e4af821d5@alum.mit.edu>
Date: Fri, 26 Jul 2019 16:10:11 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <HE1PR07MB31617B7C4E2BEED45A41ACBE93C00@HE1PR07MB3161.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ila7xFiwqOW_rKOQGY2JHgAtBiQ>
Subject: Re: [MMUSIC] 4566bis-36: Ignoring/rejecting session description that contains unknown letter
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Jul 2019 20:10:26 -0000

On 7/26/19 1:09 PM, Christer Holmberg wrote:
> Hi,
> 
>>> Due to my involvement in a large number of other drafts, I haven’t
>>> been able to follow the 4566bis work lately.
>>>
>>> I do have a question.
>>>
>>> The text says:
>>>
>>>      “The set of type letters is deliberately small and not intended to be
>>>      extensible -- an SDP parser MUST completely ignore or reject any
>>>      session description that contains a type letter that it does not
>>>      understand.”
>>>
>>> Since the syntax does not allow new letters to begin with, why can’t
>>> an SDP parser simply discard an unknown letter if received? Why does
>>> the parser have to ignore/reject the whole session description?
>>
>> This has always been part of the description of SDP. It would be odd to change it now. AFAIK there has never been another letter added to the syntax.
> 
> True.
> 
> So, what does "ignore the session description" actually mean? Discard it, and move on as it if hadn't been received? Perhaps it would then be better to always reject the session description, as there is a syntax error (as the syntax does not allow new letters).

Think of it in the concept of SAP, where the SDP was probably received 
by email and used at the discretion of the receiver. There was no 
mechanism to "reject". In that case "ignore" makes sense, while with O/A 
"reject" makes sense.

>> (Related to the point that the version has never been changed, and there is no mechanism for changing it in a backward compatible way.)
> 
> I don't think it would cause any backward compatible issues, as the receiver would only discard the letter and then process the session description.

True. My point was that while SDP includes a version number, there is no 
mechanism for changing the version in a backward compatible way. That 
would presumably be needed if anybody wanted to make a change such as 
adding another "letter". And perhaps that is why it has never been done.

	Thanks,
	Paul