[sipcore] Martin Duke's Discuss on draft-ietf-sipcore-multiple-reasons-01: (with DISCUSS)

Martin Duke via Datatracker <noreply@ietf.org> Mon, 24 October 2022 23:24 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7747AC152565; Mon, 24 Oct 2022 16:24:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-sipcore-multiple-reasons@ietf.org, sipcore-chairs@ietf.org, sipcore@ietf.org, br@brianrosen.net, br@brianrosen.net
X-Test-IDTracker: no
X-IETF-IDTracker: 8.18.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <166665387847.4155.18071629484758354380@ietfa.amsl.com>
Date: Mon, 24 Oct 2022 16:24:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/noRXZfpWQaJ6S5mWFF_WWGCcy9s>
Subject: [sipcore] Martin Duke's Discuss on draft-ietf-sipcore-multiple-reasons-01: (with DISCUSS)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 24 Oct 2022 23:24:38 -0000

Martin Duke has entered the following ballot position for
draft-ietf-sipcore-multiple-reasons-01: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-multiple-reasons/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

RFC 3326 doesn't specify what the receiver will do if two reason values have
the same protocol value. Are we reasonably sure that existing implementations
of SIP won't throw an error if they get this, or does there need to be some
sort of negotiation mechanism?