[sipcore] Warren Kumari's No Objection on draft-ietf-sipcore-multiple-reasons-01: (with COMMENT)
Warren Kumari via Datatracker <noreply@ietf.org> Thu, 27 October 2022 01:29 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 9E706C1526F7; Wed, 26 Oct 2022 18:29:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Warren Kumari 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.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Warren Kumari <warren@kumari.net>
Message-ID: <166683418263.47458.5592066856793099336@ietfa.amsl.com>
Date: Wed, 26 Oct 2022 18:29:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/4huJLiZt3s31lya1LucEhqsknSk>
Subject: [sipcore] Warren Kumari's No Objection on draft-ietf-sipcore-multiple-reasons-01: (with COMMENT)
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: Thu, 27 Oct 2022 01:29:42 -0000
Warren Kumari has entered the following ballot position for draft-ietf-sipcore-multiple-reasons-01: No Objection 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/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I was going to ballot DISCUSS on this, but I see that Paul W has beat me to the punch. If a "legacy" implementation gets multiple values for a protocol, it is likely to be OK with this, or is it likely to explode in a massive fireball? I have absolutely no idea how many implementations there are, how restrictive their parsers are, etc (AKA, "Nah, we thought about this, and it's all good" is enough to satisfy me). Also, thanks for keeping the document so short and sweet...
- [sipcore] Warren Kumari's No Objection on draft-i… Warren Kumari via Datatracker
- Re: [sipcore] Warren Kumari's No Objection on dra… Robert Sparks
- Re: [sipcore] Warren Kumari's No Objection on dra… Paul Wouters
- Re: [sipcore] Warren Kumari's No Objection on dra… Robert Sparks