[sipcore] Protocol Action: 'Multiple SIP Reason Header Field Values' to Proposed Standard (draft-ietf-sipcore-multiple-reasons-01.txt)

The IESG <iesg-secretary@ietf.org> Wed, 02 November 2022 16:42 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: The IESG <iesg@ietf.org>, br@brianrosen.net, draft-ietf-sipcore-multiple-reasons@ietf.org, rfc-editor@rfc-editor.org, sipcore-chairs@ietf.org, sipcore@ietf.org, superuser@gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <166740734132.47455.7806873376649844420@ietfa.amsl.com>
Date: Wed, 02 Nov 2022 09:42:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/33RzHRZFq3KI2f_XHsl7PrbQ_Ow>
Subject: [sipcore] Protocol Action: 'Multiple SIP Reason Header Field Values' to Proposed Standard (draft-ietf-sipcore-multiple-reasons-01.txt)

The IESG has approved the following document:
- 'Multiple SIP Reason Header Field Values'
  (draft-ietf-sipcore-multiple-reasons-01.txt) as Proposed Standard

This document is the product of the Session Initiation Protocol Core Working
Group.

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-multiple-reasons/





Technical Summary

   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.

Working Group Summary

The consensus for this document within the workgroup was very strong.  A relatively large cross section of the work group read the doc and believed it was ready to publish,  

Document Quality

There are entities who are planning implementations but the shepherd is unaware of existing implementations.  However, this document is required for recent developments in STIR, which has wide deployment, and we expect quite a few implementations shortly.  

Personnel

Brian Rosen is the Document Shepherd.
Murray Kucherawy is the responsible Area Director.

[sipcore] Protocol Action: 'Multiple SIP Reason H… The IESG