Re: Content-Transfer-Encoding "packet"

Larry Masinter (masinter@parc.xerox.com)
Wed, 26 Jul 1995 06:28:27 PDT

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Phillip M. Hallam-Baker: "Re: potential security holes in digest authorization"
Previous message: Harald.T.Alvestrand@uninett.no: "Re: Content-Transfer-Encoding "packet""
In reply to: Harald.T.Alvestrand@uninett.no: "Re: Content-Transfer-Encoding "packet""
Next in thread: Harald.T.Alvestrand@uninett.no: "Re: Content-Transfer-Encoding "packet""
Reply: Harald.T.Alvestrand@uninett.no: "Re: Content-Transfer-Encoding "packet""

In what way does what is being proposed here (the "packet" proposal
however you name it) have different semantics from MIME c-t-e?

Next message: Phillip M. Hallam-Baker: "Re: potential security holes in digest authorization"
Previous message: Harald.T.Alvestrand@uninett.no: "Re: Content-Transfer-Encoding "packet""
In reply to: Harald.T.Alvestrand@uninett.no: "Re: Content-Transfer-Encoding "packet""
Next in thread: Harald.T.Alvestrand@uninett.no: "Re: Content-Transfer-Encoding "packet""
Reply: Harald.T.Alvestrand@uninett.no: "Re: Content-Transfer-Encoding "packet""