Re: [sipcore] [Technical Errata Reported] RFC3261 (4553)
Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 15 December 2015 04:26 UTC
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF5951B2A9D for <sipcore@ietfa.amsl.com>; Mon, 14 Dec 2015 20:26:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=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 2SCclim5YKyu for <sipcore@ietfa.amsl.com>; Mon, 14 Dec 2015 20:26:21 -0800 (PST)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 740011B2A9C for <sipcore@ietf.org>; Mon, 14 Dec 2015 20:26:20 -0800 (PST)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-05v.sys.comcast.net with comcast id tgSC1r0052XD5SV01gSKMB; Tue, 15 Dec 2015 04:26:19 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-20v.sys.comcast.net with comcast id tgSJ1r0083KdFy101gSJGS; Tue, 15 Dec 2015 04:26:19 +0000
To: Ben Campbell <ben@nostrum.com>
References: <20151204140645.77D7B180004@rfc-editor.org> <7594FB04B1934943A5C02806D1A2204B37C8372C@ESESSMB209.ericsson.se> <56635188.40009@nostrum.com> <6CF3A5B1-90E7-4F50-8424-0315287BB712@nostrum.com> <7594FB04B1934943A5C02806D1A2204B37C8B0E1@ESESSMB209.ericsson.se> <9FFEF072-6575-4FB8-8C80-E850F43F9BD6@nostrum.com> <5666EAC4.1040601@alum.mit.edu> <6263C891-71DE-41F8-91F8-6FFF7A71A091@nostrum.com> <566F4A18.8010503@alum.mit.edu> <F217E1CE-C9F9-4C0A-A768-32AC284DAFBD@nostrum.com> <566F6469.2000102@alum.mit.edu> <F7C55DA3-5193-4517-9A33-EFC37A9CB5EE@nostrum.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <566F9668.4000000@alum.mit.edu>
Date: Mon, 14 Dec 2015 23:26:16 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <F7C55DA3-5193-4517-9A33-EFC37A9CB5EE@nostrum.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1450153579; bh=KMA/HANFQQnFqiB0BcuUQi66G1TPxq/LsCGBEuiAm3Y=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=dWQc/FrDhvehUUaUPsO7gsF/LlGGvMp3dOQ4W336+qWhKsEFBXt3oyMWV2rvE72gF p4ICxSIRHLbHpLnO7y65ReCh6vEf+eV0hlxxeQKorA6va6/ryMCt+gPhkrpI0lLd0S n0/JFIpUoj9eGXIjjCdAk5DcM0FGxYZ9ZrEmts78qcidqVClyY4rmYSbF+qbDS9LOH jam4/X+bsdTqfm0K4YEdK16MiGZDRvK/HK1ET6ic9iVNhonV7WGqT4esLsRIH64M1m nWRWjhLCtmwAp8uKlQ9WskAHHbLnRzL9svUC+oFOm78H7RAL4rhJlQbv3hmGgamxSM 1F+hjpf9DCPXQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/XX3ZEpiLRYjkjhoNyRAPslM5Rog>
Cc: sipcore@ietf.org
Subject: Re: [sipcore] [Technical Errata Reported] RFC3261 (4553)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2015 04:26:23 -0000
On 12/14/15 8:31 PM, Ben Campbell wrote: > On 14 Dec 2015, at 18:52, Paul Kyzivat wrote: > >> On 12/14/15 6:21 PM, Ben Campbell wrote: >>> On 14 Dec 2015, at 17:00, Paul Kyzivat wrote: >>> >>>> On 12/14/15 5:29 PM, Ben Campbell wrote: >>>> >>>>> In any case, it seems to me from discussion so far that we do not >>>>> have a >>>>> settled consensus on what the default value of the handling parameter >>>>> should be when C-D is not present. That suggests this should be >>>>> done in >>>>> an I-D, not in an erratum. If people disagree with that, please >>>>> speak up. >>>> >>>> I don't know if we have consensus. But is there any plausible argument >>>> for why the default should be different when the C-D is missing from >>>> when it is present but doesn't have a handling parameter? >>>> >>> >>> I agree that this is already settled for the case where C-D is present >>> but with no handling parameter, and consistency is a strong argument. >>> But do we think it makes sense to say "If the content is critical, put >>> in C-D" rather than "If the content is _not_ critical, put in C-D"? Do >>> we really think "required" is or will be the most common case, or that >>> the risk of accidentally failing to render critical content is high >>> enough to default to failure? >>> >>> >>> I'm personally on the fence here, if everyone paying attention thinks >>> consistency with the default when C-D is present is the correct way to >>> handle this, and was the original intent in 3261, then an erratum makes >>> sense. But if we feel the need to discuss this further, this probably >>> should come in the form of an I-D, even if the final answer is the same. >> >> Well, in the case where there is no C-D, and the C-T is SDP, then the >> default is handling=required. Is that enough to convince you? > > SDP has a rather privileged place in SIP messages. Yes, it does. But some effort was made to arrange a consistent set of general rules for bodies that is backward compatible with that. > But let me turn that around. Are you convinced? Does anyone else thing > this needs further discussion? If you are, and no one else speaks out > really soon now[1], I would approve an erratum without the SHOULD to > MUST bit. > > [*] Meaning, "before such an erratum arrives in my email." Yes, I'm convinced. Thanks, Paul
- Re: [sipcore] FW: [Technical Errata Reported] RFC… A. Jean Mahoney
- Re: [sipcore] [Technical Errata Reported] RFC3261… Ben Campbell
- Re: [sipcore] [Technical Errata Reported] RFC3261… Christer Holmberg
- Re: [sipcore] [Technical Errata Reported] RFC3261… Paul Kyzivat
- Re: [sipcore] [Technical Errata Reported] RFC3261… Christer Holmberg
- Re: [sipcore] [Technical Errata Reported] RFC3261… Ben Campbell
- Re: [sipcore] [Technical Errata Reported] RFC3261… Ben Campbell
- Re: [sipcore] [Technical Errata Reported] RFC3261… Paul Kyzivat
- Re: [sipcore] [Technical Errata Reported] RFC3261… Ben Campbell
- Re: [sipcore] [Technical Errata Reported] RFC3261… Paul Kyzivat
- Re: [sipcore] [Technical Errata Reported] RFC3261… Ben Campbell
- Re: [sipcore] [Technical Errata Reported] RFC3261… Paul Kyzivat
- Re: [sipcore] [Technical Errata Reported] RFC3261… Christer Holmberg
- Re: [sipcore] [Technical Errata Reported] RFC3261… Christer Holmberg