Re: [IETF-PKIX] Re patent 5699431 & PKIX
"David P. Kemp" <dpkemp@missi.ncsc.mil> Wed, 04 March 1998 17:04 UTC
Received: from talia.mis.tandem.com (talia-100.mis.tandem.com [130.252.226.155]) by mail.proper.com (8.8.8/8.7.3) with ESMTP id JAA22368; Wed, 4 Mar 1998 09:04:07 -0800 (PST)
Received: from suntan (suntan.tandem.com [192.216.221.8]) by talia.mis.tandem.com (8.8.7/8.8.7) with ESMTP id JAA26775; Wed, 4 Mar 1998 09:00:20 -0800 (PST)
Received: from LISTS.TANDEM.COM by LISTS.TANDEM.COM (LISTSERV-TCP/IP release 1.8c) with spool id 28268 for IETF-PKIX@LISTS.TANDEM.COM; Wed, 4 Mar 1998 08:58:59 -0800
Received: from stingray.missi.ncsc.mil (stingray.missi.ncsc.mil [144.51.52.1]) by Tandem.com (8.8.8/2.0.1) with ESMTP id IAA23848 for <IETF-PKIX@LISTS.TANDEM.COM>; Wed, 4 Mar 1998 08:58:56 -0800 (PST)
Received: from stingray.missi.ncsc.mil (root@localhost) by stingray.missi.ncsc.mil with ESMTP id LAA28896 for <IETF-PKIX@LISTS.TANDEM.COM>; Wed, 4 Mar 1998 11:58:55 -0500 (EST)
Received: from depot.missi.ncsc.mil (depot.missi.ncsc.mil [144.51.60.1]) by stingray.missi.ncsc.mil with ESMTP id LAA28891 for <IETF-PKIX@LISTS.TANDEM.COM>; Wed, 4 Mar 1998 11:58:54 -0500 (EST)
Received: from argon.ncsc.mil (argon.missi.ncsc.mil [144.51.56.1]) by depot.missi.ncsc.mil (8.6.12/8.6.9) with ESMTP id LAA14857 for <IETF-PKIX@LISTS.TANDEM.COM>; Wed, 4 Mar 1998 11:55:51 -0500
Received: by argon.ncsc.mil (SMI-8.6/SMI-SVR4) id LAA29605; Wed, 4 Mar 1998 11:56:32 -0500
X-Sun-Charset: US-ASCII
Approved-By: "David P. Kemp" <dpkemp@MISSI.NCSC.MIL>
Message-ID: <199803041656.LAA29605@argon.ncsc.mil>
Date: Wed, 04 Mar 1998 11:56:32 -0500
Reply-To: "IETF X.509-based public key infrastructure mailing list" <IETF-PKIX@LISTS.TANDEM.COM>
Sender: "IETF X.509-based public key infrastructure mailing list" <IETF-PKIX@LISTS.TANDEM.COM>
From: "David P. Kemp" <dpkemp@missi.ncsc.mil>
Subject: Re: [IETF-PKIX] Re patent 5699431 & PKIX
To: IETF-PKIX@LISTS.TANDEM.COM
> From: Paul Hoffman / IMC <paulh@IMC.ORG> > Date: Thu, 15 Jan 1998 17:55:15 -0800 > > Section 10.3.2 specifies what kind of patent information must be made > available before something can move onto standards track. If a company is > known to have an applicable patent but has not come up with a patent > statement, that company can hold up the process of getting the document on > standards track (nudge, nudge). > > --Paul Hoffman, Director > --Internet Mail Consortium draft-ietf-pkix-ipki3cmp-07.txt does not contain a patent statement, sigh. Will we need to wait for draft -08 before going to the IESG? (nudge, nudge, nudge).
- Re: [IETF-PKIX] Re patent 5699431 & PKIX Hal Lockhart
- Re: [IETF-PKIX] Re patent 5699431 & PKIX Paul Hoffman / IMC
- [IETF-PKIX] Re patent 5699431 & PKIX Sharon Boeyen
- Re: [IETF-PKIX] Re patent 5699431 & PKIX Todd Glassey
- Re: [IETF-PKIX] Re patent 5699431 & PKIX David P. Kemp