[stir] Fwd: RFC 9366 on Multiple SIP Reason Header Field Values
Robert Sparks <rjsparks@nostrum.com> Wed, 08 March 2023 15:49 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A8F1C151556 for <stir@ietfa.amsl.com>; Wed, 8 Mar 2023 07:49:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.076
X-Spam-Level:
X-Spam-Status: No, score=-7.076 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 kvn8oc2IBYZw for <stir@ietfa.amsl.com>; Wed, 8 Mar 2023 07:49:27 -0800 (PST)
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 20616C151546 for <stir@ietf.org>; Wed, 8 Mar 2023 07:49:27 -0800 (PST)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 328FnPR5019993 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <stir@ietf.org>; Wed, 8 Mar 2023 09:49:26 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1678290566; bh=6C9boKXkYO6vawAwwtuGhO4XrA6LIs6qUJjpW/0H97s=; h=Date:Subject:References:To:From:In-Reply-To; b=O4yejItg799h98dYOFCoMi7/IGKCB0yaK7W0M+33GERRK0LHc6Y86As0U/0I20UDm 6qvvdojhwFZti6o/DAxXYADWprGbjVerwQYb79e87vgtc8E1NoGm61J+5EeMYVZVS4 xow9P6t4itOeU3P7v96GBOL561rgz/iskqK/md4Y=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Content-Type: multipart/alternative; boundary="------------ns9t1qCtDx6j30jLsQ4d1r7R"
Message-ID: <1e83fe07-a363-3567-0714-b1388fc4f48f@nostrum.com>
Date: Wed, 08 Mar 2023 09:49:20 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.8.0
References: <20230308042045.E162A7FDDE@rfcpa.amsl.com>
Content-Language: en-US
To: IETF STIR Mail List <stir@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <20230308042045.E162A7FDDE@rfcpa.amsl.com>
X-Forwarded-Message-Id: <20230308042045.E162A7FDDE@rfcpa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/QMsoB800pfiX6fi5OWBBBw4lr_s>
Subject: [stir] Fwd: RFC 9366 on Multiple SIP Reason Header Field Values
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Mar 2023 15:49:31 -0000
Forwarding in case anyone here isn't watching the announce or sipcore list. RjS -------- Forwarded Message -------- Subject: RFC 9366 on Multiple SIP Reason Header Field Values Date: Tue, 7 Mar 2023 20:20:45 -0800 (PST) From: rfc-editor@rfc-editor.org To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sipcore@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 9366 Title: Multiple SIP Reason Header Field Values Author: R. Sparks Status: Standards Track Stream: IETF Date: March 2023 Mailbox: rjsparks@nostrum.com Pages: 4 Updates: RFC 3326 I-D Tag: draft-ietf-sipcore-multiple-reasons-01.txt URL: https://www.rfc-editor.org/info/rfc9366 DOI: 10.17487/RFC9366 The SIP Reason header field as defined in RFC 3326 allows only one Reason value per protocol value. Experience with more recently defined protocols shows it is useful to allow multiple values with the same protocol value. This document updates RFC 3326 to allow multiple values for an indicated registered protocol when that protocol defines what the presence of multiple values means. This document is a product of the Session Initiation Protocol Core Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
- [stir] Fwd: RFC 9366 on Multiple SIP Reason Heade… Robert Sparks