Re: IETF Y2K Compliance...

"Jim Fleming" <jfleming@anet.com> Fri, 09 July 1999 15:00 UTC

Message-ID: <04d301beca19$52c88a20$0101010a@naperville.unir.com>
From: Jim Fleming <jfleming@anet.com>
To: Ned Freed <Ned.Freed@innosoft.com>, Jim Fleming <jfleming@anet.com>
Cc: fred@cisco.com, Erik.Huizer@sec.nl, ietf@ietf.org, poised@lists.tislabs.com
Subject: Re: IETF Y2K Compliance...
Date: Fri, 09 Jul 1999 09:42:50 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

YYMM ????

Archive: ftp://ftp.tis.com/pub/lists/poised/poised.yymm

-----Original Message-----
From: Ned Freed <Ned.Freed@innosoft.com>
To: Jim Fleming <jfleming@anet.com>
Cc: fred@cisco.com <fred@cisco.com>; Erik.Huizer@sec.nl
<Erik.Huizer@sec.nl>; ietf@ietf.org <ietf@ietf.org>;
poised@lists.tislabs.com <poised@lists.tislabs.com>
Date: Friday, July 09, 1999 9:40 AM
Subject: Re: IETF Y2K Compliance...


>> The IETF may not have noticed that this is 1999 and
>> some organizations are trying to make sure that they
>> are Y2K compliant. Using 2 digit year codes will not
>> get you there. I suggest that you review all of the IETF
>> "Processes" for compliance.
>
>Jim, apparently you have not noticed that work on this issue has been
>underway for quite some time. See:
>
>  http://www.ietf.org/html.charters/2000-charter.html
>
>for details. In particular, you'll want to look at the output of this
group,
>RFC 2626.
>
> Ned
>