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

"Vijay K. Gurbani" <vkg@bell-labs.com> Wed, 15 September 2010 13:38 UTC

Return-Path: <vkg@bell-labs.com>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C53993A6A3D for <sip@core3.amsl.com>; Wed, 15 Sep 2010 06:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.457
X-Spam-Level:
X-Spam-Status: No, score=-102.457 tagged_above=-999 required=5 tests=[AWL=0.142, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iBAnSO541ptd for <sip@core3.amsl.com>; Wed, 15 Sep 2010 06:38:04 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id D367E3A6BE0 for <sip@ietf.org>; Wed, 15 Sep 2010 06:38:02 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id o8FDbrnm029109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Sep 2010 08:37:54 -0500 (CDT)
Received: from shoonya.ih.lucent.com (Knoppix-135185238233.ih.lucent.com [135.185.238.233]) by umail.lucent.com (8.13.8/TPES) with ESMTP id o8FDbnTd010442; Wed, 15 Sep 2010 08:37:49 -0500 (CDT)
Message-ID: <4C90CC91.3020607@bell-labs.com>
Date: Wed, 15 Sep 2010 08:39:29 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.11) Gecko/20100720 Fedora/3.0.6-1.fc12 Thunderbird/3.0.6
MIME-Version: 1.0
To: rfc-editor@rfc-editor.org
References: <20100914191047.ACECAE06DE@rfc-editor.org>
In-Reply-To: <20100914191047.ACECAE06DE@rfc-editor.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: Rohan Mahy <rohan@ekabal.com>, =?ISO-8859-1?Q?Alfred_H=C3nes?= <ah@TR-Sys.de>, brett@broadsoft.com, sip@ietf.org, drage@alcatel-lucent.com, gonzalo.camarillo@ericsson.com, dean.willis@softarmor.com
Subject: Re: [Sip] Corrected: [Technical Errata Reported] RFC5923 (2310)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 13:38:15 -0000

Dear RFC Editor: Please change errata state to "Verified".
The correct use is "SubjectAltName" and not "SubjectAlternativeName".

Thank you,

On 09/14/2010 02:10 PM, rfc-editor@rfc-editor.org wrote:
>
> [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 mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is essentially closed and only used for finishing old business.
> Use sip-implementors@cs.columbia.edu for questions on how to develop a SIP implementation.
> Use dispatch@ietf.org for new developments on the application of sip.
> Use sipcore@ietf.org for issues related to maintenance of the core SIP specifications.


- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/