- From: Jim Whitehead <ejw@ics.uci.edu>
- Date: Wed, 26 Mar 1997 18:09:59 -0800
- To: w3c-dist-auth@w3.org
FYI, this document provides definitions of common requirements terms, such as MUST, SHOULD, MAY, etc. which are often used in specifications. I expect we'll adopt these definitions when writing the WEBDAV specification. - Jim >To: IETF-Announce: ; >Subject: BCP 14, RFC 2119 on RFC Key Words >Cc: rfc-ed@isi.edu >Mime-Version: 1.0 >Date: Wed, 26 Mar 97 15:39:20 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. > > > BCP 14: > RFC 2119: > > Title: Key words for use in RFCs to Indicate > Requirement Level > Author: S. Bradner > Date: March 1997 > Mailbox: sob@harvard.edu > Pages: 3 > Characters: 4723 > Updates/Obsoletes: None > > URL: ftp://ds.internic.net/rfc/rfc2119.txt > > >In many standards track documents several words are used to signify >the requirements in the specification. These words are often >capitalized. This document defines these words as they should be >interpreted in IETF documents. > >This document specifies an Internet Best Current Practices for the >Internet Community, and requests discussion and suggestions for >improvements. 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: <970326140847.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 BCP 14, RFC 2119 on RFC Key (EuSn/CSOm) >(00011F5E) >Content-Type: Message/External-body; > name="rfc2119.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 rfc2119.txt (AURL/Arch) (00011F5F) >Content-Type: text/plain >Content-ID: <970326140847.RFC@ISI.EDU> >
Received on Wednesday, 26 March 1997 21:08:33 UTC