Re: [sipcore] draft-sparks-sipcore-multiple-reasons
Chris Wendt <chris-ietf@chriswendt.net> Thu, 12 May 2022 15:00 UTC
Return-Path: <chris-ietf@chriswendt.net>
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 3915DC15948A for <sipcore@ietfa.amsl.com>; Thu, 12 May 2022 08:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=chriswendt-net.20210112.gappssmtp.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 e_C3s07cT71e for <sipcore@ietfa.amsl.com>; Thu, 12 May 2022 08:00:12 -0700 (PDT)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 76AA2C157B55 for <sipcore@ietf.org>; Thu, 12 May 2022 08:00:12 -0700 (PDT)
Received: by mail-pg1-x52d.google.com with SMTP id l11so4815326pgt.13 for <sipcore@ietf.org>; Thu, 12 May 2022 08:00:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chriswendt-net.20210112.gappssmtp.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3ubeMO7g6WUY9CLK5GqcMrV9KL/Fa3C2aeO/SBgTgMk=; b=lSqCFRHE+osC2NAB6Ay9r1k+HJrr/0FTy1V2dKCCyZLvv8soXs4O952KRfFfe01wSI qEeIMnbIvuBYHnn3m3/1tzmLKRxbkVvdxF89CV+XPYrOrOFxF/rI2pHWm02zQdY+uT/3 qc8mYstSBup7RTF9QmFHV9tUXQ4OKpY/uvHqPPUD873H5a2KQfsmLHhgMHnP3Evzk5xC R4vf276qzh4eFHCUnS2snFwMlJd/s8ZdaVO7UDlIGENyw2LdJWB4K45vtuxpmpoFedRV DSQkkSClpM/WWncdu/olujLloEXUYqS855bgzd37KTjmbaetGuJb3MQmqyKb4DQjODbf xOyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3ubeMO7g6WUY9CLK5GqcMrV9KL/Fa3C2aeO/SBgTgMk=; b=qLYbR3ufGKo2fIoOUl4Lh8cW/PlUItTtFQpTPUs+Ua4Y3o/zA9mFPd9FwQIPEYNThC Egc8S1c6LD2uvROBClzIj1IrUX7f4gWWp7ZPF1VWxAr7Eh/7vAm2zvGQmF4WMqh3ZJtd 5n4Zx0K1PRTVnB+1Sy/aKAxZK7/ac6OuiUZ76TQW731J1UvmHLZm7PewY0EbvW9DjfHm vDZUKeKGVbx5y67/6ArTSlKDIizGWjrbdeZWgh+ewV24Jl8sKYofd4nVW54rIZREsoe8 ++xzfneeeNzD0qsVE07CVisMPj5VJVtBiVUCeYhD0SVKqpGh76usr8idZE+lbN0y7gpi yMVA==
X-Gm-Message-State: AOAM530OcqjJVJ6x6KBWKDeraEUjh8YjNEs2C3j+8CiHm2OWoAHrjg8J nmrc+CSgMI0koiRh9TQz/+gNQQ==
X-Google-Smtp-Source: ABdhPJyDPoU5ePoUklgqO5M9ZpYccrvkOBRXwTPWRQknpmx4UC+LQEqXPsENCwkAYLglQ0IjN5HMdw==
X-Received: by 2002:a63:e549:0:b0:3c6:d87:d3ef with SMTP id z9-20020a63e549000000b003c60d87d3efmr84809pgj.111.1652367611598; Thu, 12 May 2022 08:00:11 -0700 (PDT)
Received: from smtpclient.apple ([206.13.63.98]) by smtp.gmail.com with ESMTPSA id p15-20020a170902e74f00b0015e8d4eb2c2sm4114251plf.268.2022.05.12.08.00.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 May 2022 08:00:11 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
From: Chris Wendt <chris-ietf@chriswendt.net>
In-Reply-To: <984BD4A9-CDC8-458E-A569-B2E2EBAC7918@brianrosen.net>
Date: Thu, 12 May 2022 11:00:10 -0400
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "Dale R. Worley" <worley@ariadne.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <69C84167-308C-4E71-A172-5E0FBAD031BE@chriswendt.net>
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> <984BD4A9-CDC8-458E-A569-B2E2EBAC7918@brianrosen.net>
To: Brian Rosen <br@brianrosen.net>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/SPZlkYP6uMQ8yj9gjzzSQBWTZNE>
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: Thu, 12 May 2022 15:00:13 -0000
Yes agree, explicitly state why a new protocol was justified and SIP had potential issues for future reference. -Chris > On May 11, 2022, at 10:35 AM, Brian Rosen <br@brianrosen.net> wrote: > > <as individual> > Aha! I was confused. This makes clear what you intended. No harm in noting the issue in the doc. I would expressly forbid multiple values in current protocols with a note as to why. But just a mention is probably okay with me. > > Brian > > >> On May 11, 2022, at 9:51 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> 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. >> >> 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 >> >> _______________________________________________ >> sipcore mailing list >> sipcore@ietf.org >> https://www.ietf.org/mailman/listinfo/sipcore > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Paul Kyzivat
- [sipcore] draft-sparks-sipcore-multiple-reasons Brian Rosen
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… worley
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Christer Holmberg
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Christer Holmberg
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Paul Kyzivat
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Brian Rosen
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Chris Wendt
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Robert Sparks
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Robert Sparks
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Robert Sparks
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Chris Wendt
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Paul Kyzivat
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Christer Holmberg
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Brian Rosen
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Brian Rosen
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Brian Rosen
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Christer Holmberg
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Mary Barnes
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Paul Kyzivat
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… worley
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Chris Wendt
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Olle E. Johansson
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Ranjit Avasarala
- Re: [sipcore] draft-sparks-sipcore-multiple-reaso… Brian Rosen