RFC 5954 on Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261

rfc-editor@rfc-editor.org Fri, 20 August 2010 18:14 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 245E53A6B3E; Fri, 20 Aug 2010 11:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.056
X-Spam-Level:
X-Spam-Status: No, score=-102.056 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, 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 RrxiTB5y-kRj; Fri, 20 Aug 2010 11:14:08 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 7A03D3A6B1A; Fri, 20 Aug 2010 11:14:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 84445E06E4; Fri, 20 Aug 2010 11:14:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5954 on Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261
From: rfc-editor@rfc-editor.org
Message-Id: <20100820181439.84445E06E4@rfc-editor.org>
Date: Fri, 20 Aug 2010 11:14:39 -0700 (PDT)
Cc: sip@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Aug 2010 18:14:10 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5954

        Title:      Essential Correction for IPv6 ABNF 
                    and URI Comparison in RFC 3261 
        Author:     V. Gurbani, Ed.,
                    B. Carpenter, Ed.,
                    B. Tate, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2010
        Mailbox:    vkg@bell-labs.com, 
                    brian.e.carpenter@gmail.com, 
                    brett@broadsoft.com
        Pages:      7
        Characters: 13764
        Updates:    RFC3261

        I-D Tag:    draft-ietf-sip-ipv6-abnf-fix-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5954.txt

This document corrects the Augmented Backus-Naur Form (ABNF)
production rule associated with generating IPv6 literals in RFC 3261.
It also clarifies the rule for Uniform Resource Identifier (URI)
comparison when the URIs contain textual representation of IP
addresses.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC