[Sip] Corrected: [Technical Errata Reported] RFC5923 (2310)

rfc-editor@rfc-editor.org Tue, 14 September 2010 19:10 UTC

To: Vijay K. Gurbani <vkg@alcatel-lucent.com>, Rohan Mahy <rohan@ekabal.com>, brett@broadsoft.com, gonzalo.camarillo@ericsson.com, rjsparks@nostrum.com, dean.willis@softarmor.com, drage@alcatel-lucent.com
From: rfc-editor@rfc-editor.org
Message-Id: <20100914191047.ACECAE06DE@rfc-editor.org>
Date: Tue, 14 Sep 2010 12:10:47 -0700 (PDT)
Cc: sip@ietf.org, Alfred H��nes <ah@TR-Sys.de>, rfc-editor@rfc-editor.org
Subject: [Sip] Corrected: [Technical Errata Reported] RFC5923 (2310)
Precedence: list

[Resending with corrected Source of RFC: sip (rai).
Thanks to Magnus Westerlund for bringing this to our attention.]


The following errata report has been submitted for RFC5923,
"Connection Reuse in the Session Initiation Protocol (SIP)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5923&eid=2310

--------------------------------------
Type: Technical
Reported by: Alfred Hoenes <ah@TR-Sys.de>

Section: 8.2

Original Text
-------------
[[ in the last paragraph at the bottom of page 13: ]]

  The server, if it decides to reuse the connection, MUST cache in the
  alias table the identity (or identities) of the client as they appear
|  in the X.509 certificate subjectAlternativeName extension field.  [...]
                                  ^^^^^^^^^^^

Corrected Text
--------------
  The server, if it decides to reuse the connection, MUST cache in the
  alias table the identity (or identities) of the client as they appear
|  in the X.509 certificate subjectAltName extension field.  [...]
                                  ^^^

Notes
-----
Rationale:
 Mis-spelling of the defined certificate extension name --
 see (for example) RFC 5280.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5923 (draft-ietf-sip-connect-reuse-14)
--------------------------------------
Title               : Connection Reuse in the Session Initiation Protocol (SIP)
Publication Date    : June 2010
Author(s)           : V. Gurbani, Ed., R. Mahy, B. Tate
Category            : PROPOSED STANDARD
Source              : Session Initiation Protocol
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG

[Sip] Corrected: [Technical Errata Reported] RFC5… rfc-editor
Re: [Sip] Corrected: [Technical Errata Reported] … Vijay K. Gurbani