[anonsec] Fwd: [openikev2-announce] New versions released !!!

kent at bbn.com (Stephen Kent) Mon, 30 July 2007 17:06 UTC

From: kent at bbn.com (Stephen Kent)
Date: Mon, 30 Jul 2007 13:06:41 -0400
Subject: [anonsec] Fwd: [openikev2-announce] New versions released !!!
In-Reply-To: <20070730170041.GG1199@Sun.COM>
References: <1185527796.7989.10.camel@localhost.localdomain> <2A4BFA8D-DCDD-4DE9-B898-F2503130FFC2@checkpoint.com> <p06240503c2cfa98767f5@[172.28.170.89]> <C0F82729-0F0F-4F12-AAB2-A982919343E6@checkpoint.com> <p06240513c2d3ac271c8d@[128.89.89.71]> <20070730160010.GD1199@Sun.COM> <p06240519c2d3c2194128@[128.89.89.71]> <20070730170041.GG1199@Sun.COM>
Message-ID: <p0624051dc2d3caf8556c@[128.89.89.71]>

At 12:00 PM -0500 7/30/07, Nicolas Williams wrote:
>On Mon, Jul 30, 2007 at 12:30:02PM -0400, Stephen Kent wrote:
>>  At 11:00 AM -0500 7/30/07, Nicolas Williams wrote:
>>  >It happens a lot in the IETF.  For at least some Internet protocols
>>  >vendors have shipped long before the RFCs issued.
>>
>>  note my distinction between RFC issuance vs. IESG approval. Once the
>>  IESG approves a document is may take many months (it used to be as
>>  long as a year) for the RFC to be issued, but the substance of the
>>  standard is fixed.
>
>Yeah, but with SSHv2 the implementations existed and shipped long before
>the I-Ds even passed WGLC.

Then the vendors jumped the gun.

Steve