
	Where results make sense

Topic: RFC 2026

Related Topics

IETF

ANSI

ISO

	Pantek - Expert Linux and Open Source Services: : RFC #2026: The Internet Standards Process -- Revision 3. S. Bradner. ...
		Bradner Best Current Practice [Page 10] RFC 2026 Internet Standards Process October 1996 As noted in section 4.1, there are TSs that are not in the standards track or that have been retired from the standards track, and are therefore not required, recommended, or elective.
		Bradner Best Current Practice [Page 22] RFC 2026 Internet Standards Process October 1996 The IAB decision is final with respect to the question of whether or not the Internet standards procedures have been followed and with respect to all questions of technical merit.
		Internet-Drafts that Bradner Best Current Practice [Page 26] RFC 2026 Internet Standards Process October 1996 have been removed (for any reason) from the Internet-Drafts directories shall be archived by the IETF Secretariat for the sole purpose of preserving an historical record of Internet standards activity and thus are not retrievable except in special circumstances.
	www.pantek.com /library/general/rfc/rfc2026.html (9753 words)

	RFC 2026 (rfc2026) - The Internet Standards Process -- Revision 3 (Site not responding. Last check: 2007-11-07)
		RFC publication is the direct responsibility of the RFC Editor, under the general direction of the IAB.
		The other versions of an RFC may contain material (such as diagrams and figures) that is not present in the ASCII version, and it may be formatted differently.
		The process was first described in RFC 1310 then revised in RFC 1602 before the current effort (which relies heavily on its predecessors).
	www.faqs.org /rfcs/rfc2026.html (9617 words)

	Request for Comments - Wikipedia, the free encyclopedia
		RFCs can be obtained on the Internet from the RFC Editor [1], the IETF [2], or many other sites, principally using the Web, but also through anonymous FTP, gopher, and other Internet document-retrieval systems.
		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.
	en.wikipedia.org /wiki/RFC_2026 (2386 words)

	RFC 2026
		RFCs cover a wide range of topics in addition to Internet Standards, from early discussion of new research concepts to status memos about the Internet.
		An Internet-Draft that is published as an RFC, or that has remained unchanged in the Internet-Drafts directory for more than six months without being recommended by the IESG for publication as an RFC, is simply removed from the Internet-Drafts directory.
		These intervals shall be measured from the date of publication of the corresponding RFC(s), or, if the action does not result in RFC publication, the date of the announcement of the IESG approval of the action.
	www.kefk.net /CIE/RFC/bynumc92a.html?2026 (9736 words)

	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)

	RFC 2629 (rfc2629) - Writing I-Ds and RFCs using XML
		(Note that in all examples, indentation is used only for expository purposes.) The "front" element consists of a "title" element, one or more "author" elements, a "date" element, one or more optional "area" elements, one or more optional "workgroup" elements, one or more optional "keyword" elements, an optional "abstract" element.
		2.2.7.1 Conformance with RFC 2026 If an Internet-Draft is being produced, then the "ipr" attribute should be present in the "" tag at the beginning of the file.
		Because RFC 2223 [2] allows no more than 69 characters by 49 lines of content on each page, XML applications should be prepared to prematurely introduce page breaks to allow for better visual grouping.
	www.faqs.org /rfcs/rfc2629.html (3081 words)

	RFC 2026 (Site not responding. Last check: 2007-11-07)
		Some RFCs standardize the results of community deliberations about statements of principle or conclusions about what is the best way to perform some operations or IETF process function.
		The BCP subseries of the RFC series is designed to be a way to standardize practices and the results of community deliberations.
		Other proprietary specifications may be incorporated by reference to a version of the specification as long as the proprietor meets the requirements of section 10.
	asg.web.cmu.edu /rfc/rfc2026.html (9498 words)

	[No title]
		In the years since RFC 2026 was published there have been a number of times when the exact intent of Section 10, the section which deals with IPR disclosures has been the subject of vigorous debate within the IETF community.
		The aim of this document is to clarify various ambiguities in Section 10 of [RFC 2026] that led to these debates and to amplify the policy in order to clarify what the IETF is, or should be, doing.
		RFC, with respect to any technology or specification, described in a Contribution in the manner set forth in Section 6 of this document, the RFC Editor shall ensure that the document include a note indicating the existence of such claimed Intellectual Property Rights in any RFC published from the Contribution.
	www.mit.edu /afs/athena/reference/rfc/authors/rfc3668-diff.html (4551 words)

	Writing I-Ds and RFCs using XML (Site not responding. Last check: 2007-11-07)
		Note that text relating to the memo's status, copyright notice, or table of contents is not included in the document's markup -- this is automatically inserted by an XML application when it produces either a text or HTML version of the document.
		The "" tag at the beginning of the file, with only an "ipr" attributeConformance with RFC 2026, produces an Internet-Draft.
		Authors preparing an RFC should use this entity whenever they want to reference the number of the RFC within the document itself.
	xml.resource.org /public/rfc/html/rfc2629.html (3554 words)

	RFC.net repository of RFC STD BCP and FYI documents (Site not responding. Last check: 2007-11-07)
		The process by which an RFC is produced is described in detail in RFC 2026.
		Further information on the RFC documents and the IETF, the body that produces them, can be had at http://www.rfc-editor.org, the home of the RFC Editor.
		While the RFC Editor was once a single individual, the legendary Jon Postel, it is now a group funded by the Internet Society.
	www.rfc.net (175 words)

	RFC 2410 (rfc2410)
		Glenn & Kent Standards Track [Page 1] RFC 2410 NULL and IPsec November 1998 [ESP] specifies the use of an optional encryption algorithm to provide confidentiality and the use of an optional authentication algorithm to provide authentication and integrity.
		Algorithm Definition NULL is defined mathematically by the use of the Identity function I applied to a block of data b such that: NULL(b) = I(b) = b 2.1 Keying Material Like other modern ciphers, e.g., RC5 [RFC-2040], the NULL encryption algorithm can make use of keys of varying lengths.
		Glenn & Kent Standards Track [Page 2] RFC 2410 NULL and IPsec November 1998 2.3 Padding NULL has a block size of 1 byte, thus padding is not necessary.
	www.cse.ohio-state.edu /cgi-bin/rfc/rfc2410.html (1294 words)

	Writing I-Ds and RFCs using XML
		Rose Informational [Page 9] RFC 2629 Writing I-Ds and RFCs using XML June 1999 In the latter case, a copyright notice will not be automatically inserted during processing by an XML application.
		Rose Informational [Page 15] RFC 2629 Writing I-Ds and RFCs using XML June 1999 2.3.1.6 The iref Element The "iref" element is used to add information to an index.
		Rose Informational [Page 19] RFC 2629 Writing I-Ds and RFCs using XML June 1999 3.2 Converting to Text Format The author has written the xml2rfc tool [10], which reads the source file and produces both a text and HTML version of the document.
	www.ietf.org /rfc/rfc2629.txt (3903 words)

	IETF Request For Comments (RFCs)
		The level of standardization that an RFC reaches is determined not only by "how good" the RFC is, but by how widely it is implemented and tested.
		Some RFCs are not solid standards, but they nonetheless document technologies that are of great value to the Internet and thus should be used as guidelines for implementing Internet mail programs.
		The official rules for how RFCs are made and how things become standards are stated in RFC 2026.
	www.imc.org /rfcs.html (1166 words)

	[No title]
		Response to RFC 28 R.E. Kahn [ Jan-19-1970 ] (TXT = 790 bytes)(Also RFC0028)
		Response to RFC 111: Pressure from the chairman J.F. Heafner [ Apr-22-1971 ] (TXT = 2580 bytes)(Updates RFC0111)
		Modifications to RFC 177 J. McConnell [ Jul-21-1971 ] (TXT = 4892 bytes)(Updates RFC0177)
	www.rfc-editor.org /rfc-index.html (8324 words)

	RFC Index (Site not responding. Last check: 2007-11-07)
		Draft (Obsoletes RFC 2298) (Updates RFC 3461 RFC 2046), txt=62K
		Informational (Obsoletes RFC 1484 RFC 1485 RFC 1487 RFC 1777 RFC 1778 RFC 1779 RFC 1781 RFC 2559), txt=9K
		Draft (Obsoletes RFC 1891) (Updated by RFC 3798 RFC 3885), txt=74K
	asg.web.cmu.edu /rfc/rfc-index.html (5327 words)

Try your search on: Qwika (all wikis)