IETF Logo Mail Archive

Re: [sipcore] Warren Kumari's No Objection on draft-ietf-sipcore-multiple-reasons-01: (with COMMENT)

Paul Wouters <paul.wouters@aiven.io> Thu, 27 October 2022 16:56 UTC

Return-Path: <paul.wouters@aiven.io>
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 60A03C14F72C for <sipcore@ietfa.amsl.com>; Thu, 27 Oct 2022 09:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=aiven.io
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 OYGTcSrhSxUK for <sipcore@ietfa.amsl.com>; Thu, 27 Oct 2022 09:55:58 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (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 E4344C14F74B for <sipcore@ietf.org>; Thu, 27 Oct 2022 09:55:58 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id d26so6364120eje.10 for <sipcore@ietf.org>; Thu, 27 Oct 2022 09:55:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aiven.io; s=google; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=ju8CbOIfpCW9WWniMd0mgtqVlT91VbAjhVZKxnA3jHM=; b=jTXVUb/Xql6+BmBJvsKdOJHs9Ehv6YscXrPq6rJUtXyHOdOUzKVwknuXYOoVvX120e +rdFDy8FPOc5XsgjmtmOSuTYy5YxnLVPUODJdX1GbPYREBDEiaxtm+fIosAInHPumtTh JqGaffSr70ncyPG45iBs0g9ptZs8WN4RQBdxI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ju8CbOIfpCW9WWniMd0mgtqVlT91VbAjhVZKxnA3jHM=; b=5FdFCgj6Xm4CeWq1pkS8CsBRHAyR39LFbjJGcOrLLtR6zO142qvm1xMsSgAc7H92X6 SdtGZI70SXHmqUOcGyim8dTSwvw0gfKOr525jVHpGQcflbaf7BcRIQIc0GUJ9g2T3Oc6 Sk+jgAAPbgt9rOZyJejpp9bfqPmJ4bIT0BLxmwDMiXZkeDc/EL15KWCok8zx2KGq3xh5 JUvN4cm7dP1LZerxbxuL0cyStTsJIOPBu/wrUUqhu0GBYbWd/JcXhNydD313TtgW9Y+h bJ/Qab0USFtt72wsZ9ncF1m/UJNthfVFFMhrfQkD0dremsNRtqKrzFkBXCefMoR5VZba oQgQ==
X-Gm-Message-State: ACrzQf3RXrH3cqwgS8GUQoUGSggs4kkoETs9A2Ixih4A5UXkRg3y/rDG ddVpltsMx9A7s5ow+Y7tT9RxOQ51/kQfDA==
X-Google-Smtp-Source: AMsMyM4Jz1HRo4lTxD14dm4iu1Ld8PSmLY21bmXVTyTc41YHrcDdHzD67IZlaREyi3kp9+zcRSwyNQ==
X-Received: by 2002:a17:907:97c7:b0:79b:f7c7:35ec with SMTP id js7-20020a17090797c700b0079bf7c735ecmr28446681ejc.362.1666889757259; Thu, 27 Oct 2022 09:55:57 -0700 (PDT)
Received: from smtpclient.apple ([74.122.52.94]) by smtp.gmail.com with ESMTPSA id o13-20020aa7d3cd000000b00458898fe90asm1257494edr.5.2022.10.27.09.55.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Oct 2022 09:55:56 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Paul Wouters <paul.wouters@aiven.io>
Mime-Version: 1.0 (1.0)
Date: Thu, 27 Oct 2022 12:55:54 -0400
Message-Id: <AC44E4F4-3695-44A3-85C7-C19A19945D9F@aiven.io>
References: <53f4a763-e2dd-be2c-9617-8c0aa28b847d@nostrum.com>
Cc: Warren Kumari <warren@kumari.net>, The IESG <iesg@ietf.org>, draft-ietf-sipcore-multiple-reasons@ietf.org, sipcore-chairs@ietf.org, sipcore@ietf.org, br@brianrosen.net
In-Reply-To: <53f4a763-e2dd-be2c-9617-8c0aa28b847d@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: iPhone Mail (19G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/q4oGsBOdSSJZF6-WNSmrXF_cVNw>
Subject: Re: [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
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, 27 Oct 2022 16:56:03 -0000

On Oct 27, 2022, at 10:34, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> Inline.
> 
>> 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).
> 
> Yes, we thought about this.
> 
> We tested this at SIPits back in the day, and implementations ignore any Reason header field values with protocols they don't know about, even if there are multiple values for the same unknown-to-them protocol.

But that statement doesn’t cover multiple values for protocols they do understand. Do they pick the first ? Just overwrite so it ends up picking the last one ? 

Hence my question on whether ordering could matter.

Paul

v2.23.0 | Report a Bug | By Email