IETF Logo Mail Archive

Re: [sipcore] draft-sparks-sipcore-multiple-reasons

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 10 May 2022 19:06 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AFF6C14F73D for <sipcore@ietfa.amsl.com>; Tue, 10 May 2022 12:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.856
X-Spam-Level:
X-Spam-Status: No, score=-3.856 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2gIgW2vn2Wq for <sipcore@ietfa.amsl.com>; Tue, 10 May 2022 12:05:58 -0700 (PDT)
Received: from NAM02-DM3-obe.outbound.protection.outlook.com (mail-dm3nam07on20620.outbound.protection.outlook.com [IPv6:2a01:111:f400:7e83::620]) (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 83F68C14F723 for <sipcore@ietf.org>; Tue, 10 May 2022 12:05:58 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OTzmHyc3N9StaEdb8epdBUCRaZKZOocVwwpGMzfSygPzn9x+jmD5YFOypvQwNafrSh5fn2Hdh5gxrZt8mbpXylf3RrvzasRBB7MHsrlec1ZdGI9nhadqRScADOe9DVA6cgBLuc8bLdhgVXTK4o6XdApLlewBXxlEVmYf9lMl/UJPIPzu3rJjy2IcSD3DsAsWHwGpeTjlx1G4ll+z3enwYEZ5YgesuGkoR8+5zojDU8JyA7g4pugKFd687WBqIqooM6hgwAdztkspuhHK6n5+UKbCFHM20L2OpsLyXqlq6C8jMGxM/IR7kS6z8R7skJilWmPr8Xk7dzkbn6mh9IUnJw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=1KuYIDAd8uKEV4i/Hd4013t/Gn2gOjJlkGaT0n0tD9M=; b=M54E0+q3lIDl4ltxNpjO7J6Ik7tZh56Ctg6MIQPQ2F0Um2stv1SG4GXMq1yWWUaUKVyrj/agaQcvn+TAsfMXRo0xNSC5C5rXw8TGvOdYTI5BSotLAa5PP3uqiwHROETiNeSDMyu+jU4FjvKGcje14JKWvwKxDPop+jwoCJ48TvCmhkvA5BaYk7KEcge7sEECNE6+ZhM9967tyfINHJ3JPXAhb2eowDSCKo96tqHtM/z9hRbT3o3qsRtfJ5LXh1qKYbOueAlT2gHLJwMw0+sb2VGc7oYHgcWLZppNLzppAHsSqsFq3yV9yxTHKjfoWo4aHRayxMW3Tn4u7MxwxoWmoA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=ietf.org smtp.mailfrom=alum.mit.edu; dmarc=pass (p=none sp=none pct=100) action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1KuYIDAd8uKEV4i/Hd4013t/Gn2gOjJlkGaT0n0tD9M=; b=PJPJPvydBbEPEW00lodlIjfsgRj/qBFKnhyHiLZPLM49QSZvO9VgcuD8GAwnf4qb0pt0FLA5oUFb3XCdJWOOa6e8qj1tO2SK0lHsagbCzvFgHJhIjednMZ1YV5pwaAwDEMxsnk3hAAfIsIATgP2PK6nQB2NTUdwciC24fgf0i3A=
Received: from SN6PR08CA0002.namprd08.prod.outlook.com (2603:10b6:805:66::15) by DM4PR12MB6229.namprd12.prod.outlook.com (2603:10b6:8:a8::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5227.21; Tue, 10 May 2022 19:05:53 +0000
Received: from SN1NAM02FT0023.eop-nam02.prod.protection.outlook.com (2603:10b6:805:66:cafe::d8) by SN6PR08CA0002.outlook.office365.com (2603:10b6:805:66::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5227.23 via Frontend Transport; Tue, 10 May 2022 19:05:53 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; dkim=none (message not signed) header.d=none;dmarc=pass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com; client-ip=18.7.68.33; helo=outgoing-alum.mit.edu;
Received: from outgoing-alum.mit.edu (18.7.68.33) by SN1NAM02FT0023.mail.protection.outlook.com (10.97.4.236) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5227.15 via Frontend Transport; Tue, 10 May 2022 19:05:52 +0000
Received: from [192.168.1.52] (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 24AJ5osR032097 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <sipcore@ietf.org>; Tue, 10 May 2022 15:05:51 -0400
Message-ID: <2da137fe-2747-fb16-addf-139c705a8767@alum.mit.edu>
Date: Tue, 10 May 2022 15:05:50 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
Content-Language: en-US
To: sipcore@ietf.org
References: <9B843813-A446-4EAB-AAF4-0AC9EE37E73D@brianrosen.net>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
In-Reply-To: <9B843813-A446-4EAB-AAF4-0AC9EE37E73D@brianrosen.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-EOPAttributedMessage: 0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 97b44d88-72f0-4aff-9e69-08da32b81ab6
X-MS-TrafficTypeDiagnostic: DM4PR12MB6229:EE_
X-Microsoft-Antispam-PRVS: <DM4PR12MB622966FBD4A5D1884972303DF9C99@DM4PR12MB6229.namprd12.prod.outlook.com>
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: YetsUYXdzAISAVH4iwGwNKAAxTM04aqLYGpJ/HOV6hu1BBnxJALz3/Sdpp1/cYCjDVppK8IdpNGWaBr5F2R6xelb/LFtuIOE8KBcehsRAbb4NRj1rxROLNgj5wLRQd6TdUSdJjG0ni8ALRHn6xscE0us90nY4BzyQSR1MTBG31EOyE6jM76AtBZuMe13dasI0p2xuQIYgtvD0BcV+cmh3sdqhKytLdpBPeqb69Y0UCtlCZPzOiRx1zc3VQCUd3iscLxPQAluq/Qk2likILgxvmlzW7nZYULgnTlzLEz8xmdJXtckV7k+lUBKzaxTmKyRzvG99a6Rejl3XxdqTrF3RrKEE7xKgu5z7VNvlJ3uTlkbJf8t1XV8ItYYBweFa1EK8HAyg8MfuYenPyrfl9XnupVnv4HDFPkwQ7Nhs52JMt7ii1N6RuUBhhSVjn69Z19I4G+VedQDjYGYNg1pDVZUw1cYryisdE1fiFTJTWPOR4BkYNB33bqZjZzf/3PS4eV7WxtZRtTGxPqMTb+T+jPy17473/Zqy0LjtjwOygL9primrS+w5iwyDnMoaNWThK3IKwgIFYiiF1LR8adgboQij17FGI8PIedIgsuhdbDzaVcIhYPVY6PMB/T5VgsUC8lRsPKgIgn+U/BKGOB3m1rek5j5W+L5w+AhzoO5G/JjJRT+Ki92hHysdV2yDFsbT2lbFB1zEs1YyhQIzJcmBTInRu/nN/AhK/dr1VB0AqIxCBxBiHwal4kjTY1eM6uf8OjplUG7omZdzfbxXH8DvBeT8A==
X-Forefront-Antispam-Report: CIP:18.7.68.33; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:outgoing-alum.mit.edu; PTR:outgoing-alum.mit.edu; CAT:NONE; SFS:(13230001)(46966006)(36840700001)(31696002)(26005)(8676002)(86362001)(956004)(36860700001)(2616005)(53546011)(2906002)(75432002)(966005)(356005)(83380400001)(8936002)(508600001)(316002)(6916009)(5660300002)(786003)(31686004)(186003)(70586007)(82310400005)(70206006)(7596003)(47076005)(336012)(43740500002); DIR:OUT; SFP:1101;
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 May 2022 19:05:52.7706 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 97b44d88-72f0-4aff-9e69-08da32b81ab6
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33]; Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-AuthSource: SN1NAM02FT0023.eop-nam02.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM4PR12MB6229
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/tYbkoWuZpu3libS11MYEsQkMco0>
Subject: Re: [sipcore] draft-sparks-sipcore-multiple-reasons
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.34
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, 10 May 2022 19:06:00 -0000

I think this is ok, but it is worth discussing the implications for 
backward compatibility.

Existing protocol values presumably don't mention support for multiple 
reasons, so in the short term nothing should be impacted.

If a new protocol value is defined that does allow multiple reasons, 
then hopefully most implementations that don't support the new protocol 
value won't notice the issue. There is a faint possibility that a strict 
implementation will notice this even for a protocol it doesn't support. 
I'm inclined not to worry about this.

If an update is made to an existing protocol definition that does allow 
multiple reasons, it could break existing implementations. They might 
detect an error, or they might just act on one of the reasons. In the 
latter case they might not all act on the same one. (Some may use the 
first, while others use the last.)

I suggest that this draft should discuss this issue, and give guidance 
for the future.

	Thanks,
	Paul

On 5/10/22 12:14 PM, Brian Rosen wrote:
> The author has requested sipcore to adopt this draft.  Please review the draft and let us know your thoughts on adoption.
> 
> https://datatracker.ietf.org/doc/draft-sparks-sipcore-multiple-reasons
> 
> Brian
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email