[IPsec] Fwd: Informational RFC to be: <draft-zhang-ipsecme-anti-replay-07.txt>

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 01 November 2011 18:41 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F08011E8149 for <ipsec@ietfa.amsl.com>; Tue, 1 Nov 2011 11:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level:
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QR7EvcupsqP for <ipsec@ietfa.amsl.com>; Tue, 1 Nov 2011 11:41:00 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id EA81A11E8142 for <ipsec@ietf.org>; Tue, 1 Nov 2011 11:40:59 -0700 (PDT)
Received: from [10.20.30.103] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id pA1IewVA086329 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ipsec@ietf.org>; Tue, 1 Nov 2011 11:40:59 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 01 Nov 2011 11:40:58 -0700
References: <20111031234137.4675.64002.idtracker@ietfa.amsl.com>
To: IPsecme WG <ipsec@ietf.org>
Message-Id: <BA223AD9-B6C4-4418-97D2-DAC3A3CADDF2@vpnc.org>
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [IPsec] Fwd: Informational RFC to be: <draft-zhang-ipsecme-anti-replay-07.txt>
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 18:41:00 -0000

Of interest to the WG. Note that there is nothing to discuss, this is just a message from the IESG to the ISE.

Begin forwarded message:

> From: The IESG <iesg-secretary@ietf.org>
> Subject: Re: Informational RFC to be: <draft-zhang-ipsecme-anti-replay-07.txt>
> Date: October 31, 2011 4:41:37 PM PDT
> To: RFC ISE <rfc-ise@rfc-editor.org>
> Cc: iana@iana.org, The IESG <iesg@ietf.org>, ietf-announce@ietf.org, rfc-editor@rfc-editor.org
> 
> The IESG has no problem with the publication of 'IPsec anti-replay
> algorithm without bit-shifting' <draft-zhang-ipsecme-anti-replay-07.txt>
> as an Informational RFC.
> 
> The IESG would also like the RFC-Editor to review the comments in
> the datatracker
> (http://datatracker.ietf.org/doc/draft-zhang-ipsecme-anti-replay/)
> related to this document and determine whether or not they merit
> incorporation into the document. Comments may exist in both the ballot
> and the comment log.
> 
> A URL of this Internet Draft is:
> http://datatracker.ietf.org/doc/draft-zhang-ipsecme-anti-replay/
> 
> The process for such documents is described at
> http://www.rfc-editor.org/indsubs.html
> 
> Thank you,
> 
> The IESG Secretary
> 
> 
> 
> 
> Technical Summary
> 
>   This document presents an alternate method to do the anti-replay
>   checks and updates for IP Authentication Header (AH) and
>   Encapsulating Security Protocol (ESP).
> 
> Working Group Summary
> 
>   This is an independent submission via the RFC Editor.
> 
> Document Quality
> 
>   N/A
> 
> Personnel
> 
>   The responsible Area Director is Sean Turner
> 
> RFC Editor Note
> 
>  The IESG has concluded that this work is related to IETF work done
>  in the IPSECME WG, but this relationship does not prevent publishing.
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce