- From: Jaye, Dan <DJaye@engagetech.com>
- Date: Thu, 3 Apr 1997 21:18:17 -0500
- To: "'http-wg@cuckoo.hpl.hp.com'" <http-wg@cuckoo.hpl.hp.com>
- Cc: "'ahyde@focalink.com'" <ahyde@focalink.com>, "'rodger@worldnet.atg.net'" <rodger@worldnet.atg.net>
As promised, here is a description of our proposal to amend RFC2109 to allow certification of unverifiable transactions. I have two questions in particular regarding this proposal: 1) Should "certified" cookies be a third! type of cookie header [this is what we have written in the proposal] or can we incorporate the certificate as an option in the SetCookie2 header? 2) Can we include this in the next version of RFC2109 or must it be a separate RFC? >)>)>)>)>)---------------------------------------->>>>>>> Daniel Jaye djaye@engagetech.com Engage Technologies, Inc. (508)684-3641 v 100 Brickstone Square, Andover MA 01810 (508)684-3636 f
Received on Thursday, 3 April 1997 18:21:04 UTC