Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: RFC 2223


Related Topics

In the News (Tue 23 Jul 19)

  
  RFC OVERVIEW
The function of the RFC Editor is primarily to publish and archive RFCs.
The RFC Editor is responsible for the final editorial review of the documents and attempts to maintain the standards of the series.
RFC documents are governed by very liberal copyright rules, which are essentially meant only to prevent the blatant misuse of RFC text.
www.rfc-editor.org /overview.html   (404 words)

  
  DocMirror.Net - RFC 2223
RFC 2223 Instructions to RFC Authors October 1997 Most of the RFCs are processed by the RFC Editor with the unix "nroff" program using a very simple set of the formatting commands (or "requests") from the "ms" macro package (see the Appendix).
RFC 2223 Instructions to RFC Authors October 1997 For example: On the Assigned Numbers RFCs the term Obsoletes should be used since the new document actually incorporate new information (however brief) into the text of existing information and is more up-to-date than the older document, and hence, replaces it and makes it Obsoletes.
RFC 2223 Instructions to RFC Authors October 1997.ti 0 Frame Format The IP datagram is printed, on a small scroll of paper, in hexadecimal, with each octet separated by whitestuff and flstuff.
www.docmirror.net /en/rfc/rfc2223.html   (4455 words)

  
 RFC 2223 (rfc2223) - Instructions to RFC Authors
RFCs have been traditionally published and continue to be published in ASCII text.
Most of the RFCs are processed by the RFC Editor with the unix "nroff" program using a very simple set of the formatting commands (or "requests") from the "ms" macro package (see the Appendix).
RFCs in ASCII Format may be submitted to the RFC Editor in e-mail messages (or as online files) in either the finished publication format or in nroff.
www.faqs.org /rfcs/rfc2223.html   (4396 words)

  
 Independent Submissions
The RFC Editor may make general and/or specific suggestions to the author(s) about improvements in the editorial quality of the document or violations of the format and content rules.
Reviewers may be members of the RFC Editorial Board or some person known to the RFC Editor or the Editorial Board to be competent in the subject of the document.
The RFC Editor generally applies a liberal standard if a document is at all relevant and interesting to some potential readers.
www.rfc-editor.org /indsubs.html   (629 words)

  
 HOW TO PUBLISH
All RFCs in a standards-track or Best Current Practice (BCP) category, as well as some Informational and Experimental RFCs, originate within the IETF process and reach the RFC Editor through the IESG.
Once an RFC has been edited and is ready for publication, the author(s) are given "48 hours" (in practice, this often stretches over weeks) to look over their document for errors, editorial and otherwise.
Indefinite delays are not allowed, but when there is a choice, the RFC Editor would in general prefer to publish it right than to publish it early.
www.rfc-editor.org /howtopub.html   (882 words)

  
 RFC 2223 - (rfc2223) - Instructions to RFC Authors
Postel and Reynolds Informational [Page 4] RFC 2223 Instructions to RFC Authors October 1997 Most of the RFCs are processed by the RFC Editor with the unix "nroff" program using a very simple set of the formatting commands (or "requests") from the "ms" macro package (see the Appendix).
If the RFC is not based on an I-D, other possibilities are: Postel and Reynolds Informational [Page 9] RFC 2223 Instructions to RFC Authors October 1997 Protocol This protocol is intended to provide the bla-bla service, and be used between clients and servers on host computers.
Postel and Reynolds Informational [Page 18] RFC 2223 Instructions to RFC Authors October 1997.ti 0 Frame Format The IP datagram is printed, on a small scroll of paper, in hexadecimal, with each octet separated by whitestuff and flstuff.
www.rfcsearch.org /rfcview/2223?tips=1   (4496 words)

  
 Request for comment - Questionz.net , answers to all your questions   (Site not responding. Last check: 2007-11-04)
The RFCs issued by the Internet Engineering Task Force (IETF) and its predecessors are the most well-known series known as 'RFC', and is almost always what is meant by RFC without further qualification; however, other organizations have in the past also issued series called 'RFCs'.
The RFCs are unusual in that they are floated by technical experts acting on their own initiative and reviewed by the Internet at large, rather than formally promulgated through an institution such as ANSI.
The RFCs are most remarkable for how well they work - they manage to have neither the ambiguities that are usually rife in informal specifications, nor the committee-perpetrated misfeatures that often haunt formal standards, and they define a network that has grown to truly worldwide proportions.
www.questionz.net /History_of_the_Internet/RFC.html   (2076 words)

  
 RFC Series Overview
RFCs are numbered (roughly) consecutively, and these numbers provide a single unique label space for all RFCs.
The RFC series is the publication vehicle for technical specifications and policy documents produced by the (IETF (Internet Engineering Task Force), the IAB (Internet Architecture Board), or the IRTF (Internet Research Task Force).
In addition to the master RFC index, there are secondary indexes for useful subsets or " sub-series " of the RFCs.
www.rfc-editor.org /RFCoverview.html   (521 words)

  
 [No title]
Myers Standards Track [Page 5] RFC 2222 SASL October 1997 In the case that a profile explicitly permits multiple successful SASL negotiations to occur, then in no case may multiple security layers be simultaneously in effect.
Myers Standards Track [Page 8] RFC 2222 SASL October 1997 The security layers and their corresponding bit-masks are as follows: 1 No security layer 2 Integrity (krb_mk_safe) protection 4 Privacy (krb_mk_priv) protection Other bit-masks may be defined in the future; bits which are not understood must be negotiated off.
If the client sends the empty string as the authorization identity (thus requesting the authorization identity be derived from the client's authentication credentials), the authorization identity is to be derived from authentication credentials which exist in the system which is providing the external authentication.
www.ietf.org /rfc/rfc2222.txt   (3625 words)

  
 RFC-Online Project
The earliest RFCs were produced and distributed on paper, but network distribution began after as the FTP protocol was defined and implemented on the ARPAnet.
At some point in the history of the RFCs, when operating systems were changed and links and/or conversions did not work, the files containing the first 600 RFCs were lost.
ISI is currently backlogged on editing and proofreading the text; there are approximately 100 RFCs for which we now have nroff sources that we have not yet edited.
www.rfc-editor.org /rfc-online.html   (879 words)

  
 [No title]
RFC 2396 [1] defines the general syntax and semantics of URIs, and, by inclusion, URLs.
Material may be published as an Informational RFC by sending it to the RFC Editor (please follow the instructions to RFC authors, RFC 2223 [3]).
The most common case of this will be to enable changes to be made to schemes where the scheme name is privately owned by the rules of its tree, and the owner of the scheme name has died, moved out of contact or is otherwise unable to make changes that are important to the community.
www.ietf.org /rfc/rfc2717.txt   (2262 words)

  
 [No title]
As such, the definition of this term was revised to emphasize both the conversion aspect of the process, and the term itself has been changed to "charset" to emphasize that it is not, after all, just a set of characters.
The intent of the public posting is to solicit comments and feedback on the definition of the charset and the name chosen for it over a two week period.
The description of the charset may also be published as an Informational RFC by sending it to "rfc-editor@isi.edu" (please follow the instructions to RFC authors [RFC-2223]).
www.ietf.org /rfc/rfc2278.txt   (2247 words)

  
 RFC 2223 - Instructions to RFC Authors
top Each RFC should have an Introduction section that (among other things) explains the motivation for the RFC and (if appropriate) describes the applicability of the protocol described.
top All RFCs must contain a section near the end of the document that discusses the security considerations of the protocol or procedures that are the main topic of the RFC.
top Each RFC must have at the very end a section giving the author's address, including the name and postal address, the telephone number, (optional: a FAX number) and the Internet email address.
ip-doc.com /rfc/rfc2223   (4235 words)

  
 RFC 2223 (rfc2223)   (Site not responding. Last check: 2007-11-04)
Postel & Reynolds Informational [Page 4] RFC 2223 Instructions to RFC Authors October 1997 Most of the RFCs are processed by the RFC Editor with the unix "nroff" program using a very simple set of the formatting commands (or "requests") from the "ms" macro package (see the Appendix).
If the RFC is not based on an I-D, other possibilities are: Postel & Reynolds Informational [Page 9] RFC 2223 Instructions to RFC Authors October 1997 Protocol This protocol is intended to provide the bla-bla service, and be used between clients and servers on host computers.
Postel & Reynolds Informational [Page 18] RFC 2223 Instructions to RFC Authors October 1997.ti 0 Frame Format The IP datagram is printed, on a small scroll of paper, in hexadecimal, with each octet separated by whitestuff and flstuff.
www.cse.ohio-state.edu /cgi-bin/rfc/rfc2223.html   (4395 words)

  
 RFC 2223
This RFC is being distributed to members of the Internet community in order to solicit their reactions to the proposals contained in it.
All RFCs must contain a section near the end of the document that discusses the security considerations of the protocol or procedures that are the main topic of the RFC.
Per BCP 9, RFC 2026 [2], "The following copyright notice and disclaimer shall be included in all ISOC standards-related documentation." The following statement should be placed on the last page of the RFC, as the "Full Copyright Statement".
asg.web.cmu.edu /rfc/rfc2223.html   (3886 words)

  
 The Internet Report
A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms.
This memo also defines an extension to the encoded words defined in RFC 2047 to allow the specification of the language to be used for display as well as the character set.
RFC 4510, RFC 4511, RFC 4513, RFC 4512
ietfreport.isoc.org /rfc2200-2299.html   (5566 words)

  
 IETF RFC Page
The first choice below connects to the RFC repository maintained by the IETF Secretariat.
RFCs associated with an active IETF Working Group can also be accessed from the Working Group's web page via IETF Working Groups.
where NNNN is the RFC number prefixed with zeroes as necessary to make a four digit number.
www.ietf.org /rfc   (158 words)

  
 IP-Doc
The RFCs are most remarkable for how well they work - they manage to have neither the ambiguities that are usually rife in informal specifications, nor the committee-perpetrated misfeatures that often haunt formal standards, and they define a network that has grown to truly worldwide proportions.
RFC 1, entitled "Host Software", was written by Steve Crocker from the University of California, Los Angeles, and published on April 7, 1969.
RFC 2047 specifies a standard way of encoding non US-ASCII characters into a string that identifies both the character set to use and the actual characters.
ip-doc.com   (2214 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.