Fwd: [Sip] New version of draft-ietf-sip-ipv6-abnf-fix

Robert Sparks <rjsparks@nostrum.com> Wed, 05 May 2010 20:45 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 416A43A6CC9 for <ietf@core3.amsl.com>; Wed, 5 May 2010 13:45:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.453
X-Spam-Level:
X-Spam-Status: No, score=-2.453 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001]
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 32U3R336jkoj for <ietf@core3.amsl.com>; Wed, 5 May 2010 13:44:58 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 6BE763A6CCE for <ietf@ietf.org>; Wed, 5 May 2010 13:44:48 -0700 (PDT)
Received: from [172.16.3.177] (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o45KiNUY080495 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 May 2010 15:44:24 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
From: Robert Sparks <rjsparks@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: multipart/alternative; boundary="Apple-Mail-80-579803910"
Subject: Fwd: [Sip] New version of draft-ietf-sip-ipv6-abnf-fix
Date: Wed, 05 May 2010 15:44:23 -0500
References: <4BDEE1A1.90605@bell-labs.com>
To: IETF Discussion <ietf@ietf.org>
Message-Id: <47F96304-E999-4CBF-8091-17581E595CE1@nostrum.com>
X-Mailer: Apple Mail (2.1078)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "Vijay K. K. Gurbani" <vkg@bell-labs.com>, Brett Tate <brett@broadsoft.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 May 2010 20:45:04 -0000

fyi

Begin forwarded message:

> From: "Vijay K. Gurbani" <vkg@bell-labs.com>
> Date: May 3, 2010 9:45:53 AM CDT
> To: IETF SIP List <sip@ietf.org>
> Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Brett Tate <brett@broadsoft.com>
> Subject: [Sip] New version of draft-ietf-sip-ipv6-abnf-fix
> 
> Folks: A new version (-05) of draft-ietf-sip-ipv6-abnf-fix
> is ready to be sent to the IESG.
> 
> The summary of changes is as follows:
> 
> 1) Minor typo and grammatical fixes.
> 2) Added a new S4 in -05 to serve as a reference point to
>   draft-ietf-6man-text-addr-representation-07, a draft on
>   how to generate a canonical IPv6 textual representation.
> 
>   draft-...-addr-representation is now referenced using a
>   normative SHOULD and has been made a normative reference.
>   This should not delay the release of draft-...-ipv6-abnf-fix
>   since draft-...-addr-representation is now in RFC Ed Queue.
> 
> The relevant links are:
> New version (-05):
> http://www.ietf.org/internet-drafts/draft-ietf-sip-ipv6-abnf-fix-05.txt
> 
> Diff from previous version:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-sip-ipv6-abnf-fix-05
> 
> Thanks,
> 
> - 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/
> _______________________________________________
> 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.