- From: Yaron Goland (Exchange) <yarong@Exchange.Microsoft.com>
- Date: Wed, 1 Dec 1999 15:11:41 -0800
- To: "'mpresler@us.ibm.com'" <mpresler@us.ibm.com>, discuss@apps.ietf.org
- Message-ID: <A10314B4D590E647A18A19A817ACEAB209A0EC@dobie.platinum.corp.microsoft.com>
SSDP (http://search.ietf.org/internet-drafts/draft-cai-ssdp-v1-03.txt) and SOAP (http://search.ietf.org/internet-drafts/draft-box-http-soap-00.txt) both use it. Making MAN experimental is just silly. Man has been implemented, deployed and tested. We know it works. For example, Microsoft will be shipping Man as part of SSDP in our next Win 9x release (code name: Millennium). Man is a done deal. Not only is the spec fully baked, many other specs already depend on it. Running code and rough consensus at its best... Yaron > -----Original Message----- > From: mpresler@us.ibm.com [mailto:mpresler@us.ibm.com] > Sent: Wed, December 01, 1999 5:56 AM > To: discuss@apps.ietf.org > Subject: RE: HTTP Extensions Framework status? > > > > > My first motivation for asking was because P3P > (http://www.w3.org/P3P/) is making use of the HTTP extensions > framework - > P3P messages may be added to responses as optional extensions > (using Opt:), > and I wanted to see if the extensions framework was going > forward to be > standardized any time soon. > > My other question is what other protocols/applications have been > interested in using the HTTP extensions framework? I have > been considering > what it'd take to add P3P support to Apache, and this led me > down to the > idea of implementing the HTTP extensions framework as an > Apache module, but > there's little point if there aren't any users expected any time soon. > > Thanks, > > Martin > > Martin Presler-Marshall - P3P Champion > E-mail: mpresler@us.ibm.com > Phone: (919) 254-7819 (tie-line 444-7819) Fax: (919) 543-4118 > (tie-line > 441-4118) >
Received on Wednesday, 1 December 1999 18:13:28 UTC