IETF Logo Mail Archive

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

Robert Sparks <rjsparks@nostrum.com> Sun, 15 May 2022 16:58 UTC

Return-Path: <rjsparks@nostrum.com>
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 DE260C20D67F for <sipcore@ietfa.amsl.com>; Sun, 15 May 2022 09:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.936
X-Spam-Level:
X-Spam-Status: No, score=-8.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_HI=-5, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 s1ebp9txyxkW for <sipcore@ietfa.amsl.com>; Sun, 15 May 2022 09:58:16 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C2B3C20D67C for <sipcore@ietf.org>; Sun, 15 May 2022 09:58:16 -0700 (PDT)
Received: from [192.168.1.114] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 24FGwDtQ066968 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <sipcore@ietf.org>; Sun, 15 May 2022 11:58:14 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1652633894; bh=UcLgie7IK9Ci0I64Ysb1vvKZXx6de83LgV6SGQEMhrg=; h=Date:Subject:From:To:References:In-Reply-To; b=jKekvxjqDSvnSYXs+a8YwMRSpLphXaKFCc8BAGSZYOFeF/WS//QepSKJ/vMWiFcQd QPppaYzgxkRAa0oIROf4y01Pn1hI6e7R9EUXi4L9oDICLDGsRYxNao/jj1I5VAb6NY 8fVbbPgLTGNcDOfN5e1F/sM1R8oiwYNhan9gs/8c=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Content-Type: multipart/alternative; boundary="------------P4ZjIvLR3b7bUVJ0OCq5Mk22"
Message-ID: <a18eb058-0eed-6d49-be1c-989d08172f94@nostrum.com>
Date: Sun, 15 May 2022 11:58:08 -0500
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
From: Robert Sparks <rjsparks@nostrum.com>
To: sipcore@ietf.org
References: <2da137fe-2747-fb16-addf-139c705a8767@alum.mit.edu> <878rr84yh1.fsf@hobgoblin.ariadne.com> <HE1PR07MB44415BDDF6BD204D7ED331C793C89@HE1PR07MB4441.eurprd07.prod.outlook.com> <c7656cb9-598f-b5dc-5790-07b73d3335fa@alum.mit.edu> <0bd00014-5647-330a-095c-9514d6fc8b6b@nostrum.com>
In-Reply-To: <0bd00014-5647-330a-095c-9514d6fc8b6b@nostrum.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/VssOZIIFDRtaY3h761awilCh6zU>
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: Sun, 15 May 2022 16:58:19 -0000

On 5/11/22 8:51 AM, Paul Kyzivat wrote:
> 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.
In my initial formulation, I felt that this would be that future draft's 
problem. (There are a lot of _other_ things a future update to SIP might 
do as well, and I'm reticent to start discussing ramifications of 
something this draft doesn't do).
>
> 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