IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 11 May 2022 13:52 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 47E6EC19D47E for <sipcore@ietfa.amsl.com>; Wed, 11 May 2022 06:52:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.857
X-Spam-Level:
X-Spam-Status: No, score=-3.857 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, 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 m_xbh6hS1wU9 for <sipcore@ietfa.amsl.com>; Wed, 11 May 2022 06:52:07 -0700 (PDT)
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (mail-bn7nam10on2061f.outbound.protection.outlook.com [IPv6:2a01:111:f400:7e8a::61f]) (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 432F6C19D46D for <sipcore@ietf.org>; Wed, 11 May 2022 06:52:07 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WjqMh2/XbfAXW3p5LXW7MCT5eZml69uBkUXWnr4/gA/tmDPO5BRB2BCzke4YUwtSxWzHPuu/86gg3J2s6rHXgDDENlWW0gbI6f5GBhmHoocTRkJl0JUsT6uS6YWTkSHrYXeA6fNzVeIO1PnImfiwOhRVob4PAQMJ8hAIbAGhzp6RzmO+aR9/MhEvhQM8019iz+pZL69JkC/td+LXspWKLqYL1gfWj7RNmJzdh0szR4fPu4L8SNMWJeRtmg/TZIPEwE4veMh8rV7Y4UD4yhviAjwQU5Al9sEH2TepP2xPq3gJYLhONXhRqB2b/xu1+qNbJr8Iq+eZ7wajCulQPnCR6w==
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=KSE7muRm6MUYtkUXg5nn6y0ooi+SkIQk4LbMbNVHJOc=; b=aEs+jjESHz3LLmxIM3m42ZcAongpoHca3n9Tt38ah/leGyP6bLa135MUjV5gmA0VDdGZS0FEdP/UTILntEn8b3/92WC68ftObY/++tfdEN3ocglzkk0EyCl54vCOfOKPq6E093YQie3L2WXGxyiyFy1ZAUShCK9OBHWFPOD1Q/6iEQmbqCowrB8kM50XPHelV5YJw+7l2prjpnfB4yvRzn8SyTogENWXO4TFcy9ME6XuJUnp2aEw7EinRDujUpcUXE0LO8GLHuq+7JP4OcMZiHh+MY4284j5VUwaRI5g21Z4gcz6I5wVaYBfP4x0suzoyXvBs296jBrGwMgNEBD3tA==
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=KSE7muRm6MUYtkUXg5nn6y0ooi+SkIQk4LbMbNVHJOc=; b=UxXM88XBP5ort0LeuaM8LN4GXBERDpzNhDJnOdTwHq6PV3MryJfGZLWt/Ll6AFpX589GzDcvVGZtDBH6keXORcfqd8PA3mJifseheFQp6NhUD+WLAqay4vUsgSYbUxE0S4tWLre+ZuCepGabc4fzRTWwJ0Y+qq3E0MVKSs+i6CM=
Received: from DS7PR06CA0040.namprd06.prod.outlook.com (2603:10b6:8:54::28) by PH7PR12MB6658.namprd12.prod.outlook.com (2603:10b6:510:211::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5227.22; Wed, 11 May 2022 13:52:03 +0000
Received: from DM3NAM02FT045.eop-nam02.prod.protection.outlook.com (2603:10b6:8:54:cafe::a5) by DS7PR06CA0040.outlook.office365.com (2603:10b6:8:54::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5227.22 via Frontend Transport; Wed, 11 May 2022 13:52:02 +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 DM3NAM02FT045.mail.protection.outlook.com (10.13.4.189) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5250.13 via Frontend Transport; Wed, 11 May 2022 13:52:01 +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 24BDpxtj007505 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 11 May 2022 09:52:00 -0400
Message-ID: <c7656cb9-598f-b5dc-5790-07b73d3335fa@alum.mit.edu>
Date: Wed, 11 May 2022 09:51:59 -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: Christer Holmberg <christer.holmberg@ericsson.com>, "Dale R. Worley" <worley@ariadne.com>
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
References: <2da137fe-2747-fb16-addf-139c705a8767@alum.mit.edu> <878rr84yh1.fsf@hobgoblin.ariadne.com> <HE1PR07MB44415BDDF6BD204D7ED331C793C89@HE1PR07MB4441.eurprd07.prod.outlook.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
In-Reply-To: <HE1PR07MB44415BDDF6BD204D7ED331C793C89@HE1PR07MB4441.eurprd07.prod.outlook.com>
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: 120eb3d7-601d-41da-8319-08da33556cc3
X-MS-TrafficTypeDiagnostic: PH7PR12MB6658:EE_
X-Microsoft-Antispam-PRVS: <PH7PR12MB665867D78B3647FE1E433416F9C89@PH7PR12MB6658.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: YSOlJnRkwbofyjGPW1qTvAG6904b/jj0Mze2FDkwCAm/GzbmsnXRjytsql6QJANz1SjdPsO2JeHHWQG3VrfmV/nEJAzCFyEfW7MfiUfnoo56HjzmPBh5HsG5ORktPkNXce50sqTjZddx7VgF+l1utVkaW6BbyeOEUMD/0N92/DLNoydBbuVuDF7oCNaIj9u4+ZpA0WwKG3kK0v4k5c7Jk+XKRhyr1zTFg6NEAAKPERolls5D81hOjS2mV1mzkvfKhLsi7bMyu6IFs32CSiYGY32mC47konmKcOGta1P8gK9WFGfG6lmxwwZdKPpQkH7WnBOUUgcXWDsyUwTXn8w45fodoEwH70l3C1wcWDToODtE7/5EnlBcaI3L35JfvTcLOJUnB27Y6HHAuuoDpL9eFIVlAFEsAHI8X2oUiydJ/1KF+M1v461Ru4wgaIP3pKoyMRr/NgMj0zGx8uYEa5yv71lmNVZGjj9t4MjKtgdSXwm90EN/PUQkGyCX0unzr6hLzeH4P6nfKPUE28UYjzgCNsCXbd3wxpt/qmds9vQmgFOta7tMxN9oi7njjAl8sOgMLOJtTV8LBn7V+l6YPKIGVP1wT1qZzEucXGdKwfFKiqa+jvKCHsttmNz7kt0FAuIVI/cyh0FAK9IXKLvuGeuv1MPPY8n0wihUtHkZdNjcMZktg+tT6qM5B8e/dZmObCSEf8M6j9xP/z/JxeWmkzryBRQoh0rZj5N1VncG1sMnrBsS158yYaxcoovxbzHypjOmYrZ1fUPDGyEb+xpH1ejTmw==
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)(83380400001)(336012)(36860700001)(508600001)(47076005)(5660300002)(77540400001)(786003)(316002)(70586007)(70206006)(86362001)(4326008)(31696002)(75432002)(8676002)(966005)(8936002)(356005)(7596003)(82310400005)(186003)(2616005)(956004)(2906002)(26005)(110136005)(53546011)(31686004)(43740500002); DIR:OUT; SFP:1101;
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 May 2022 13:52:01.4304 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 120eb3d7-601d-41da-8319-08da33556cc3
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: DM3NAM02FT045.eop-nam02.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH7PR12MB6658
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/qIMDkrhwF5HKPAk9jmVGYCAJsdE>
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: Wed, 11 May 2022 13:52:11 -0000

Its clear that this will be the case initially. My question is a 
hypothetical. At some time in the future someone may find a reason they 
want to use multiple reasons with SIP or another pre-existing protocol. 
At that point they might propose an update to allow that for SIP. At 
that point there would be a potential backward compatibility problem.

I'm only asking that this document discuss the issue and provide 
guidance for the future. For instance it might ban such changes for 
pre-existing protocols. Or it might just point out that an update to 
allow such for a protocol address the problem as part of the update.

	Thanks,
	Paul

On 5/11/22 2:30 AM, Christer Holmberg wrote:
> I thought the idea was to allow multiple protocols ONLY if the protocol value explicitly allows it (e.g., "STIR").
> 
> But, the change would NOT allow multiple instances of "SIP".
> 
> Regards,
> 
> Christer
> 
> -----Original Message-----
> From: sipcore <sipcore-bounces@ietf.org> On Behalf Of Dale R. Worley
> Sent: keskiviikko 11. toukokuuta 2022 5.04
> To: Paul Kyzivat <pkyzivat@alum.mit.edu>
> Cc: sipcore@ietf.org
> Subject: Re: [sipcore] draft-sparks-sipcore-multiple-reasons
> 
> Paul Kyzivat <pkyzivat@alum.mit.edu> writes:
>> If an update is made to an existing protocol definition that does
>> allow multiple reasons, it could break existing implementations.
> 
> A possible "upward compatibility" mechanism is to retain the requirement that existing protocol names still have only one value, and define a second protocol name to carry the other values that are semantically associated with the existing protocol name.  Thus one might have:
> 
>      Reason: SIP ;cause=200 ;text="Call completed elsewhere",
>              SIP-M ;cause=200.1 ;text="Call completed by voicemail",
>              SIP-M ;cause=200.1.17 ;text="Subscriber's voicemail"
> 
> Older implementations would likely discard both the SIP-M values and process the SIP value as expected.
> 
> Dale
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email