Re: [IPsec] [draft-ietf-ipsecme-roadmap-00] Comments about references
Paul Hoffman <paul.hoffman@vpnc.org> Tue, 03 February 2009 18:54 UTC
Return-Path: <ipsec-bounces@ietf.org>
X-Original-To: ipsec-archive@megatron.ietf.org
Delivered-To: ietfarch-ipsec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4823B3A6C51; Tue, 3 Feb 2009 10:54:36 -0800 (PST)
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 106A53A6C51 for <ipsec@core3.amsl.com>; Tue, 3 Feb 2009 10:54:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Level:
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599]
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 WhXjj36N0Lgt for <ipsec@core3.amsl.com>; Tue, 3 Feb 2009 10:54:34 -0800 (PST)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 9A27C3A67FD for <ipsec@ietf.org>; Tue, 3 Feb 2009 10:54:33 -0800 (PST)
Received: from [10.20.30.158] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n13Is8En030596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Feb 2009 11:54:09 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240812c5ae42f8290c@[10.20.30.158]>
In-Reply-To: <729b68be0902030935g39daeb27i6ab2e2d00221808b@mail.gmail.com>
References: <729b68be0902030935g39daeb27i6ab2e2d00221808b@mail.gmail.com>
Date: Tue, 03 Feb 2009 10:54:07 -0800
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>, IPsec WG <ipsec@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [IPsec] [draft-ietf-ipsecme-roadmap-00] Comments about references
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipsec-bounces@ietf.org
Errors-To: ipsec-bounces@ietf.org
At 6:35 PM +0100 2/3/09, Jean-Michel Combes wrote: >Hi, > >as promised during the interim meeting, here are comments about references: > >o IPSECKEY implementation > >IPSECKEY RR has been implemented here: >http://www.idsa.prd.fr/index.php?page=code&lang=en > >and included in BIND after (cf. https://www.isc.org/about/pr/2007032700). This seems good enough for listing RFC 4025 in the roadmap. >o PANA and IPsec > >AFAIK, it was decided in Dublin meeting that PANA WG has to work again >on PANA based IPsec bootstrapping >(http://tools.ietf.org/html/draft-ietf-pana-ipsec-07) but, as I didn't >attend Minneapolis meeting, I don't know whether this is still the >case ... We should wait for this to stabilize. >o Pfr+ use > >Pfr+ is used in RFC 5295 (cf. section 3.1.2). As I said on the call, it seems like overkill to list docs that have picked up our PRFs. That's not reall IPsec. --Paul Hoffman, Director --VPN Consortium _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
- [IPsec] [draft-ietf-ipsecme-roadmap-00] Comments … Jean-Michel Combes
- Re: [IPsec] [draft-ietf-ipsecme-roadmap-00] Comme… Paul Hoffman