[Ipsec] ikev2 status
Kausty <kkumbhalkar@gmail.com> Wed, 16 February 2005 05:46 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22358 for <ipsec-archive@lists.ietf.org>; Wed, 16 Feb 2005 00:46:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Hsk-0003Y0-EY; Wed, 16 Feb 2005 00:37:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Hoc-0001jo-Oq for ipsec@megatron.ietf.org; Wed, 16 Feb 2005 00:33:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21050 for <ipsec@ietf.org>; Wed, 16 Feb 2005 00:33:31 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.195]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1I9n-0007qn-Cs for ipsec@ietf.org; Wed, 16 Feb 2005 00:55:28 -0500
Received: by wproxy.gmail.com with SMTP id 71so39373wri for <ipsec@ietf.org>; Tue, 15 Feb 2005 21:33:02 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=VtuElwOhM9es58d9s4A4U+GcOvbtB9g9bwzl6url8oNG1bEfRLIiVr8Mi1RPBGbt7GBfBlDzp0x9UzEGR4zbMFuhR4ZIjV2ClHGrAKNK7apE5tUEOZZAAw0Ui8DDN7GtGXvPmLNlZgsH0EW71WPNkrXYh4lCLAJmng7RSIYkWSU=
Received: by 10.54.31.8 with SMTP id e8mr158740wre; Tue, 15 Feb 2005 21:33:02 -0800 (PST)
Received: by 10.54.40.21 with HTTP; Tue, 15 Feb 2005 21:33:02 -0800 (PST)
Message-ID: <41ae44840502152133485f5de6@mail.gmail.com>
Date: Wed, 16 Feb 2005 11:03:02 +0530
From: Kausty <kkumbhalkar@gmail.com>
To: mleech@nortel.com, ipsec@ietf.org
In-Reply-To: <F5F4EC6358916448A81370AF56F211A505442520@RED-MSG-51.redmond.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
References: <F5F4EC6358916448A81370AF56F211A505442520@RED-MSG-51.redmond.corp.microsoft.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Subject: [Ipsec] ikev2 status
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Kausty <kkumbhalkar@gmail.com>
List-Id: IP Security <ipsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
Sender: ipsec-bounces@ietf.org
Errors-To: ipsec-bounces@ietf.org
Content-Transfer-Encoding: 7bit
IKEv2 is stuck in the RFC editor's queue behind RFC2401bis (because it
references it). That document has been imminent for some time; the WG
chairs or ADs might have a better idea when it will be completed. No
further changes to IKEv2 are contemplated.
Frustratingly, I've been asked not to comment on the Microsoft IPR
statement beyond what they have posted.
--Charlie
-----Original Message-----
From: Kausty [mailto:kkumbhalkar@gmail.com]
Sent: Monday, February 14, 2005 9:35 PM
To: Charlie Kaufman
Subject: Microsoft's statement about IPR claimed in
draft-ietf-ipsec-ikev2-08.txt
Hi,
Regarding the Patent Disclosure and Licensing Declaration relating to
IKEv2 draft,
I wanted to know which particular sections of IKEv2 are part of
microsoft's IPR and for which license would be required from
microsoft.
and yes by what time will ikev2 draft will get the RFC status.
Thanks
Kausty
_______________________________________________
Ipsec mailing list
Ipsec@ietf.org
https://www1.ietf.org/mailman/listinfo/ipsec
- [Ipsec] ikev2 status Kausty