Re: PEP over TCP, or TCPPEP

Joseph M. Reagle Jr. (reagle@rpcp.mit.edu)
Wed, 08 Apr 1998 12:48:41 -0400

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: David Crook: "Re: A potential candidate for Rohit's soul mate."
Previous message: Joseph M. Reagle Jr.: "Fork Demographics [Was Re: A potential candidate for Rohit's"
In reply to: Rohit Khare: "PEP over TCP, or TCPPEP"

At 03:47 PM 4/7/98 -0700, Rohit Khare wrote:
>Welcome to the crowd, folks -- here's another PEP draft that may actually
>make it to experimental RFC status soon:
>
>"PEP - an Extension Mechanism for HTTP"
>http://www.ietf.org/internet-drafts/draft-ietf-http-pep-05.txt

The W3C even claims it as a common law trade mark.
http://www.w3.org/Consortium/Legal/ipr-notice.html#Copyright

Though we aren't pursuing registration because its had so much play in the
IETF realm and because it is now being called "mandatory."

_______________________
Regards, http://web.mit.edu/reagle/www/home.html
Joseph Reagle E0 D5 B2 05 B6 12 DA 65 BE 4D E3 C1 6A 66 25 4E
reagle@mit.edu independent research account

Next message: David Crook: "Re: A potential candidate for Rohit's soul mate."
Previous message: Joseph M. Reagle Jr.: "Fork Demographics [Was Re: A potential candidate for Rohit's"
In reply to: Rohit Khare: "PEP over TCP, or TCPPEP"