[sipcore] Fwd: New Version Notification for draft-sparks-sipcore-multiple-reasons-00.txt
Robert Sparks <rjsparks@nostrum.com> Fri, 12 November 2021 18:46 UTC
Return-Path: <rjsparks@nostrum.com>
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 771123A1075; Fri, 12 Nov 2021 10:46:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.078
X-Spam-Level:
X-Spam-Status: No, score=-2.078 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, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t_v1BDLRKV_r; Fri, 12 Nov 2021 10:46:14 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAFEF3A1070; Fri, 12 Nov 2021 10:46:14 -0800 (PST)
Received: from [192.168.1.114] ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 1ACIkC2s057667 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 12 Nov 2021 12:46:12 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1636742773; bh=nQfOUiawS91vkHLkAPNAdU2/y1gxc4O2CasCsrXrE/E=; h=Date:References:To:Reply-To:From:Subject:In-Reply-To; b=C19LxBDmNmbw5TZ8D5zq+22u1QHK5ZWS4sMo8a8YOBJqmaMx6oTRoUjN1MNns00j0 NN3Phj/bUHc/q2O9tIPRQXZ624i3rYfQaJcNyzQKa5iCj2vyFmNUUfCg2KX0kIhgjm +BoJMWTAFvYR7zK1KytMJz4pXKzyrf9dYe86v1Fs=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be [192.168.1.114]
Content-Type: multipart/alternative; boundary="------------3gnlKtjx19PQnbH2ZWkqyQiN"
Message-ID: <ad9838c4-ba42-c433-7604-4fa68a2b9036@nostrum.com>
Date: Fri, 12 Nov 2021 12:46:07 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.0
References: <163674236973.518.9330414781217950009@ietfa.amsl.com>
Content-Language: en-US
To: sipcore@ietf.org, IETF STIR Mail List <stir@ietf.org>
Reply-To: sipcore@ietf.org
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <163674236973.518.9330414781217950009@ietfa.amsl.com>
X-Forwarded-Message-Id: <163674236973.518.9330414781217950009@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/elXUdl57xIHoLyXULV4nofSpbTU>
Subject: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-multiple-reasons-00.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 12 Nov 2021 18:46:20 -0000
(Crossposting, with reply-to set to SIPCORE) The STIR working group has identified a reason to provide multiple Reason header field values with the same protocol (STIR) in a SIP message. See https://datatracker.ietf.org/meeting/112/materials/slides-112-stir-wendt-stir-identity-header-error-handling-03-00 for a bit of background. This draft proposes to update 3326 to allow that to happen. Discussion should take place on the STIR list. PRs are welcome at https://github.com/rjsparks/draft-sparks-sipcore-multiple-reasons RjS -------- Forwarded Message -------- Subject: New Version Notification for draft-sparks-sipcore-multiple-reasons-00.txt Date: Fri, 12 Nov 2021 10:39:29 -0800 From: internet-drafts@ietf.org To: Robert Sparks <rjsparks@nostrum.com> A new version of I-D, draft-sparks-sipcore-multiple-reasons-00.txt has been successfully submitted by Robert Sparks and posted to the IETF repository. Name: draft-sparks-sipcore-multiple-reasons Revision: 00 Title: Multiple SIP Reason Header Field Values Document date: 2021-11-12 Group: Individual Submission Pages: 4 URL: https://www.ietf.org/archive/id/draft-sparks-sipcore-multiple-reasons-00.txt Status: https://datatracker.ietf.org/doc/draft-sparks-sipcore-multiple-reasons/ Html: https://www.ietf.org/archive/id/draft-sparks-sipcore-multiple-reasons-00.html Htmlized: https://datatracker.ietf.org/doc/html/draft-sparks-sipcore-multiple-reasons Abstract: The SIP Reason Header Field as defined in RFC 3326 allows only one Reason value per protocol value. Practice shows it is useful to allow multiple values with the same protocol value. This update to RFC 3326 allows multiple values for an indicated registered protocol when that protocol defines what the presence of multiple values means. The IETF Secretariat
- [sipcore] Fwd: New Version Notification for draft… Robert Sparks