[sipcore] Last Call: <draft-ietf-sipcore-multiple-reasons-01.txt> (Multiple SIP Reason Header Field Values) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Mon, 26 September 2022 15:14 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: br@brianrosen.net, draft-ietf-sipcore-multiple-reasons@ietf.org, sipcore-chairs@ietf.org, sipcore@ietf.org, superuser@gmail.com
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <166420526611.29665.18146931948450810936@ietfa.amsl.com>
Date: Mon, 26 Sep 2022 08:14:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/4fuVrWyRe0rgAzk6nDqnWIUBOC4>
Subject: [sipcore] Last Call: <draft-ietf-sipcore-multiple-reasons-01.txt> (Multiple SIP Reason Header Field Values) to Proposed Standard

The IESG has received a request from the Session Initiation Protocol Core WG
(sipcore) to consider the following document: - 'Multiple SIP Reason Header
Field Values'
  <draft-ietf-sipcore-multiple-reasons-01.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-10-10. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   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 update to RFC 3326 allows multiple
   values for an indicated registered protocol when that protocol
   defines what the presence of multiple values means.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-sipcore-multiple-reasons/



No IPR declarations have been submitted directly on this I-D.

[sipcore] Last Call: <draft-ietf-sipcore-multiple… The IESG