- From: Jim Whitehead <ejw@ics.uci.edu>
- Date: Wed, 22 Jan 1997 13:16:56 -0800
- To: w3c-dist-auth@www10.w3.org
Members of this list may find the following RFC to be of interest. - Jim >To: IETF-Announce: ; >Subject: RFC 2084 on Considerations for Web Transaction Security >Cc: rfc-ed@isi.edu >Mime-Version: 1.0 >Date: Wed, 22 Jan 97 12:13:27 PST >Sender:ietf-announce-request@ietf.org >From: RFC Editor <rfc-ed@isi.edu> > > >A new Request for Comments is now available in online RFC libraries. > > > RFC 2084: > > Title: Considerations for Web Transaction Security > Author: G. Bossert, S. Cooper, W. Drummond > Date: January 1997 > Mailbox: bossert@corp.sgi.com, sc@corp.sgi.com, > drummond@ieee.org > Pages: 6 > Characters: 9022 > Updates/Obsoletes: None > > URL: ftp://ds.internic.net/rfc/rfc2084.txt > > >This document specifies the requirements for the provision of security >services to the HyperText Transport Protocol. These services include >confidentiality, integrity, user authentication, and authentication of >servers/services, including proxied or gatewayed services. Such >services may be provided as extensions to HTTP, or as an encapsulating >security protocol. This document is a product of the Web Transaction >Security Working Group of the IETF. > >This memo provides information for the Internet community. This memo >does not specify an Internet standard of any kind. Distribution of >this memo is unlimited. > >This announcement is sent to the IETF list and the RFC-DIST list. >Requests to be added to or deleted from the IETF distribution list >should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to RFC-DIST-REQUEST@ISI.EDU. > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to rfc-info@ISI.EDU with the message body >help: ways_to_get_rfcs. For example: > > To: rfc-info@ISI.EDU > Subject: getting rfcs > > help: ways_to_get_rfcs > >Requests for special distribution should be addressed to either the >author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution. > >Submissions for Requests for Comments should be sent to >RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC >Authors, for further information. > > >Joyce K. Reynolds and Mary Kennedy >USC/Information Sciences Institute > >... > >Below is the data which will enable a MIME compliant Mail Reader >implementation to automatically retrieve the ASCII version >of the RFCs. > >Content-Type: text/plain >Content-ID: <970122120849.RFC@ISI.EDU> > >[This attachment must be fetched by mail. >Open the stationery below and send the resulting >message to get the attachment.] >Attachment converted: Galileo:Get RFC 2084 on Considerations (EuSn/CSOm) >(0000FB9A) >Content-Type: Message/External-body; > name="rfc2084.txt"; > site="ds.internic.net"; > access-type="anon-ftp"; > directory="rfc" > >[This attachment must be fetched by ftp. > Open the document below to ask your ftp client to fetch it.] >Attachment converted: Galileo:Get rfc2084.txt (AURL/Arch) (0000FB9B) >Content-Type: text/plain >Content-ID: <970122120849.RFC@ISI.EDU> >
Received on Wednesday, 22 January 1997 17:03:10 UTC