
	Where results make sense

Topic: RFC 0985

Related Topics

Audio Video Standard

Ext3

ASCII

Chinook Jargon

Photograph

Ramicristates

Chaos magic

Neobalaenidae

PPi

Diatessaron

Astral projection

Nadsat

Gravediggaz

G5

Michaelmas

In the News (Sun 6 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	RFC 985 (rfc985) - Requirements for Internet gateways - draft
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT The use of full-blown transport services such as TCP is in general ill-advised if required just to collect statistics from the gateway.
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT Appendix A. Ethernet Management Following is a summary of procedures specified for use by hosts and gateways on an Ethernet.
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT NSF systems vendors should understand that they also undertake a commitment to remain aware of current Internet technology and be prepared to upgrade their products from time to time as appropriate.
	www.faqs.org /rfcs/rfc985.html (7044 words)

	RFCs in HTML Format - RFC 0985
		RFC 975 [27] suggests certain modifications leading to a symmetric model; however, this is not an official specification.
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT ICMP Address Mask message, which a gateway can use to specify certain details of the subnetting scheme to hosts and is required in new host and gateway implementations.
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT packet switches in a network would normally be expected to have a routing algorithm with the capability of reacting to link and other gateway failures and changing the routing automatically.
	rfc.activedomain.org /0500-0999/rfc0985.html (7199 words)

	RFC Collection
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT The use of full-blown transport services such as TCP is in general ill-advised if required just to collect statistics from the gateway.
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT Appendix A. Ethernet Management Following is a summary of procedures specified for use by hosts and gateways on an Ethernet.
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT NSF systems vendors should understand that they also undertake a commitment to remain aware of current Internet technology and be prepared to upgrade their products from time to time as appropriate.
	www.richardlowe.com /rfc/rfc985.html (6996 words)

	RFCs 1000 - 1099 Index
		This RFC Reference Guide is intended to provide a historical account by categorizing and summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987.
		This RFC is designed as an aid to implementors and administrators by providing: 1) an overview of the transition process from host tables to domains, 2) a timetable for the transition, and 3) references to documentation and software relating to the domain system.
		This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville.
	cidr-report.org /ietf/html/rfc1000-1099.html (5506 words)

	RFC985 (Site not responding. Last check: 2007-10-09)
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT ICMP Address Mask message, which a gateway can use to specify certain details of the subnetting scheme to hosts and is required in new host and gateway implementations.
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT packet switches in a network would normally be expected to have a routing algorithm with the capability of reacting to link and other gateway failures and changing the routing automatically.
		RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT time no definitive common model for access control and accounting has emerged, it is possible to outline some general features such a model is likely to have, among them the following: 1.
	rfc.net /rfc0985.html (7088 words)

	RFC 0985 (rfc0985)
		NTAG [Page 14] RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT The use of full-blown transport services such as TCP is in general ill-advised if required just to collect statistics from the gateway.
		NTAG [Page 18] RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT Appendix A. Ethernet Management Following is a summary of procedures specified for use by hosts and gateways on an Ethernet.
		NTAG [Page 21] RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT NSF systems vendors should understand that they also undertake a commitment to remain aware of current Internet technology and be prepared to upgrade their products from time to time as appropriate.
	www.cse.ohio-state.edu /cgi-bin/rfc/rfc0985.html (7056 words)

	RFC 3485 - The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling ...
		Introduction SIP [3] and SDP [24] are text-based protocols that use the UTF-8 charset (RFC 2279 [5]).
		Standards Track [Page 4] RFC 3485 SIP and SDP Static Dictionary for SigComp February 2003 an entry whose value is CR, LF, the word From, a colon and a whitespace.
		Standards Track [Page 5] RFC 3485 SIP and SDP Static Dictionary for SigComp February 2003 stored as a one-byte value, and the offset is stored as a two-byte value that has had 1024 added to the offset (this allows direct referencing from the stored value if the dictionary state has been loaded at address 1024).
	www.packetizer.com /rfc/rfc3485 (3731 words)

	2-Nitropropane (CASRN 79-46-9), IRIS, Environmental Protection Agency
		The inhalation Reference Concentration (RfC) is analogous to the oral RfD and is likewise based on the assumption that thresholds exist for certain toxic effects such as cellular necrosis.
		Inhalation RfCs were derived according to the Interim Methods for Development of Inhalation Reference Doses (EPA/600/8-88/066F August 1989) and subsequently, according to Methods for Derivation of Inhalation Reference Concentrations and Application of Inhalation Dosimetry (EPA/600/8-90/066F October 1994).
		RfCs can also be derived for the noncarcinogenic health effects of substances that are carcinogens.
	www.epa.gov /iris/subst/0519.htm (2291 words)

	RFC 986 (rfc986) - Guidelines for the use of Internet-IP addresses in the
		This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
		This is necessary because the ISO protocol considers identification of the user protocol to be an addressing issue, and therefore does not allow for the user protocol to be specified in the protocol header independently from the address.
		RFC 986 June 1986 DOD IP Addresses in ISO CLNP Therefore a source or destination address within the ISO Connectionless Protocol, when used in the DOD Internet, looks as follows: Octet +------------------------+
	www.faqs.org /rfcs/rfc986.html (945 words)

	The Internet Report
		This memo is a report on the discussion of the representation of equations in a workshop at the ACM SIGGRAPH Conference held in Anaheim, California on 30 July 1987.
		RFC 1084, RFC 1395, RFC 1497, RFC 1533
		This memo is a revision of RFC 986.
	ietfreport.isoc.org /rfc1000-1099.html (5113 words)

	[No title]
		Following the RFC number are the title, the author(s), and the publication date of the RFC.
		Updates xxxx refers to other RFCs that this one merely updates but does not replace); Updated by xxxx refers to RFCs that have updated (but not replaced) this one.
		Generally, only immediately succeeding and/or preceding RFCs are indicated, not the entire history of each related earlier or later RFC in a related series.
	www.isi.edu /in-notes/rfc-index.txt (13951 words)

	RFCs @ Saint Roch Tree (tm)
		RFC 0955 - Towards a transport service for transaction processing applications.
		RFC 0985 - Requirements for Internet gateways - draft.
		RFC 0986 - Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol.
	www.saintrochtree.com /zones/it/links/comtel-stand-ietf-all-0950.htm (459 words)

	Computers - Internet - RFCs - 0901 - 1000 (Site not responding. Last check: 2007-10-09)
		RFC 0939 - Executive Summary of the NRC Report on Transport Protocols for Department of Defense Data Networks.
		RFC 0942 - Transport Protocols for Department of Defense Data Networks.
		RFC 0982 - Guidelines for the Specification of the Structure of the Domain Specific Part (DSP) of the ISO Standard NSAP Address.
	www.inter.co.yu /kategorije/Computers/Internet/RFCs/0901_-_1000 (886 words)

	Request for Comments - Wikipedia, the free encyclopedia
		RFC 1, entitled "Host Software", was written by Steve Crocker of the University of California, Los Angeles (UCLA), and published on April 7, 1969.
		Many of the subsequent RFCs of the 1970s also came from UCLA, not only because of the quality of the scholarship, but also because UCLA was one of the first Interface Message Processors (IMPs) on ARPANET.
		Every RFC is available as ASCII text, but may also be available in other file formats; however, as of 2006 the definitive version of any standards-track specification is the ASCII version.
	en.wikipedia.org /wiki/Request_for_Comments (1469 words)

	RFC 0985
		While the ARPANET 1822 protocols are widely NTAG [Page 9] RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT used at present, they are expected to be eventually overtaken by the DDN Standard X.25 protocol (see below) and the new PSN End-to-End Protocol described in RFC-979 [29].
		NTAG [Page 16] RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT [13] Kirton, P., "EGP Gateway under Berkeley UNIX 4.2", DARPA Network Working Group Report RFC-911, USC Information Sciences Institute, August 1984.
		NTAG [Page 17] RFC 985 May 1986 Requirements for Internet Gateways -- DRAFT [24] Nagle, J., "On Packet Switches with Infinite Storage", DARPA Network Working Group Report RFC-970, Ford Aerospace, December 1985.
	burks.bton.ac.uk /burks/internet/rfcs/rfcs/85/rfc0985.htm (7056 words)

	[No title]
		RFC citations appear in this format: #### Title of RFC.
		Each format is followed by an equals sign and the number of bytes for that version.
		Obsoletes xxxx refers to other RFCs that this one replaces; Obsoleted by xxxx refers to RFCs that have replaced this one.
	www.ietf.org /iesg/1rfc_index.txt (13951 words)

	U.S. EPA IRIS Substance file - 2-Nitropropane; CASRN 79-46-9
		Substance Name -- 2-Nitropropane CASRN -- 79-46-9 Last Revised -- 03/01/1991 The inhalation Reference Concentration (RfC) is analogous to the oral RfD and is likewise based on the assumption that thresholds exist for certain toxic effects such as cellular necrosis.
		In general, the RfC is an estimate (with uncertainty spanning perhaps an order of magnitude) of a daily inhalation exposure of the human population (including sensitive subgroups) that is likely to be without an appreciable risk of deleterious effects during a lifetime.
		If the U.S. has evaluated this substance for potential human carcinogenicity, a summary of that evaluation will be contained in Section II of this file.
	www.chem.uic.edu /web1/OCOL3/IRIS/SUBST/0519.HTM (2377 words)

	hjp: doc: RFC 0985: Requirements for Internet gateways - draft
		This RFC summarizes the requirements for gateways to be used on networks supporting the DARPA Internet protocols.
		Following is a summary of procedures specified for use by hosts and gateways on an Ethernet.
		NSF systems vendors should understand that they also undertake a commitment to remain aware of current Internet technology and be prepared to upgrade their products from time to time as appropriate.
	www.hjp.at /doc/rfc/rfc985.html (6973 words)

	[No title]
		Hoffman & Blanchet Standards Track [Page 5] RFC 3454 Preparation of Internationalized Strings December 2002 This document lists the unassigned code points in the range 0 to 10FFFF for Unicode 3.2 in appendix A. The list in appendix A MUST be used by implementations of this specification.
		Hoffman & Blanchet Standards Track [Page 9] RFC 3454 Preparation of Internationalized Strings December 2002 A profile that specifies Unicode normalization MUST use the normalization in [UAX15] that is associated with the version of the Unicode character set specified for the profile.
		Each entry in the registry has three fields: - Profile name - RFC in which the profile is defined - Indicator whether or not this is the newest version of the profile Each version of a profile will remain listed in the registry forever.
	www.ietf.org /rfc/rfc3454.txt (5796 words)

	RFC Index (Site not responding. Last check: 2007-10-09)
		Finally, the Status field gives the document's current status (see RFC 2026).
		(Format: TXT=659 bytes) (Updates RFC0107) (Status: UNKNOWN) 0125 Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream.
		(Format: TXT=11175 bytes) (Updated by RFC0147) (Status: UNKNOWN) 0130 Response to RFC 111: Pressure from the chairman.
	rfc.net /rfc-index.html (9033 words)

	RFCs 1000 - 1099 Index (Site not responding. Last check: 2007-10-09)
		Addendum to RFC 987: (Mapping between X.400 and RFC-822).
		RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 2065, RFC 2181, RFC 2308, RFC 2535
		RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 1995, RFC 1996, RFC 2065, RFC 2136, RFC 2181, RFC 2137, RFC 2308, RFC 2535, RFC 2845, RFC 3425, RFC 3658
	www.potaroo.net /ietf/rfc1000-1099.html (505 words)

	Zvon - RFC index
		ZVON > RFC Repository > RFC 900 - 999
		Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol (Obsoleted by RFC-1069)
		Mapping between X.400 and RFC 822 (Obsoleted by RFC-1327 -> RFC-2156
	www.zvon.org /tmRFC/RFC_share/Output/09xx.html (516 words)

	RFC Index
		This document provides definitions, formats, references, and citations for cryptographic algorithms, usage modes, and associated identifiers and parameters used in support of Privacy Enhanced Mail(PEM) in the Internet community.
		It is intended to become one member of the set of related PEM RFCs.
		This document is organized into four primary sections, dealing with message encryption algorithms, message integrity check algorithms, symmetric key management algorithms, and asymmetric key management algorithms (including both asymmetric encryption and asymmetric signature algorithms).
	www.potaroo.net /ietf/html/status_historic.html (4151 words)

	Requirements for Internet gateways [ R.T. Braden, J. Postel ]
		Requirements for Internet gateways, Internet historic RFC 1009, June 1987.
		National Science Foundation, Network Technical Advisory Group, Requirements for Internet gateways - draft, Internet RFC 0985, May 1986
		Baker, Requirements for IP Version 4 Routers, Internet proposed standard RFC 1812, June 1995
	dret.net /rfc-index/reference/RFC1009 (70 words)

	0901 - 1000 :: RFCs : Gourt
		Meta Description: [ RFC 939 - Executive summary of the NRC report on transport protocols for Department of Defense data networks ]
		Meta Description: [ RFC 942 - Transport protocols for Department of Defense data networks ]
		Meta Description: [ RFC 982 - Guidelines for the specification of the structure of the Domain Specific Part (DSP) of the ISO standard NSAP address ]
	computers.gourt.com /Internet/RFCs/0901-1000.html (1902 words)

	RFC Collection
		0985 - Requirements for Internet gateways - draft
		0628 - Status of RFC numbers and a note on pre-assigned journal numbers
		0568 - Response to RFC 567 - cross country network bandwidth
	www.richardlowe.com /rfc/index02.htm (1579 words)

Try your search on: Qwika (all wikis)