
	Where results make sense

Topic: RFC 1009

Related Topics

Shorten

Operator

Trisomy 13

Monopoly (game)

So Solid Crew

Chief of state

The Station nightclub fire

HCC

Ruritania

Telugu language

Selena Quintanilla Perez

UXO

Pisgah Astronomical Research Institute

Banco Popular

Max Carey

In the News (Mon 16 Nov 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	RFC 1009 (rfc1009) - Requirements for Internet gateways
		RFC 1009 - Requirements for Internet Gateways June 1987 A number of different dynamic routing protocols have been developed (see Section 4.1); the particular choice of routing protocol within a single AS is generically called an interior gateway protocol or IGP.
		RFC 1009 - Requirements for Internet Gateways June 1987 The assigned values for the Ether-Type field are the same for either this IEEE 802 encapsulation or the basic Ethernet encapsulation [10].
		RFC 1009 - Requirements for Internet Gateways June 1987 There must also be a mechanism to limit the frequency of such trap reports, and the parameters controlling this frequency must be settable in the gateway configuration.
	www.faqs.org /rfcs/rfc1009.html (15498 words)

	RFC1009 (Site not responding. Last check: 2007-11-07)
		RFC 1009 - Requirements for Internet Gateways June 1987 a gateway must be highly robust and able to operate, possibly in a degraded state, under conditions of extreme congestion or failure of network resources.
		RFC 1009 - Requirements for Internet Gateways June 1987 may also be sent by a gateway if the fragments of a datagram addressed to the gateway itself cannot be reassembled before the time limit.
		RFC 1009 - Requirements for Internet Gateways June 1987 case, it is required that a means be available to operate the control agent from a remote site using Internet protocols and paths and with equivalent functionality with respect to a local agent terminal.
	rfc.net /rfc1009.html (15606 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/Request_for_Comments (2380 words)

	Pantek - Expert Linux and Open Source Services: : RFC #1009: Requirements for Internet gateways. R.T. Braden, J. Postel.
		In their Braden & Postel [Page 10] RFC 1009 - Requirements for Internet Gateways June 1987 interconnect role, they will need to provide sophisticated means for monitoring and measuring traffic and other events and for diagnosing faults.
		If this is the Braden & Postel [Page 39] RFC 1009 - Requirements for Internet Gateways June 1987 case, it is required that a means be available to operate the control agent from a remote site using Internet protocols and paths and with equivalent functionality with respect to a local agent terminal.
		Braden & Postel [Page 41] RFC 1009 - Requirements for Internet Gateways June 1987 There must also be a mechanism to limit the frequency of such trap reports, and the parameters controlling this frequency must be settable in the gateway configuration.
	www.pantek.com /library/general/rfc/rfc1009.html (15614 words)

	RFC1009
		It is described in RFC 791 [19] and also in MIL-STD-1777 [5] as clarified by RFC 963 [36] ([1] and [5] are intended to describe the same standard, but in quite different words).
		RFC 975 [27] suggested one way to generalize EGP to lessen these topology restrictions; it has not been adopted as an official specification, although its ideas are finding their way into the new EGP developments.
		The original IP address mapping (RFC 796 [38]) is in the process of being replaced by a new interface specification called AHIP-E; see RFC 1005 [61] for the proposal.
	www.scit.wlv.ac.uk /rfc/rfc10xx/RFC1009.html (15165 words)

	RFC 1175 (rfc1175)
		RFCs are distributed on-line by being stored as public access files, and a short message is sent to the RFC distribution list (RFC- REQUEST@NIC.DDN.MIL) indicating the availability of the memo.
		RFC-1012 Bibliography of Request for Comments 1 through 999 This RFC is a reference guide for the Internet community which provides a bibliographic summary of the Request for Comments numbers 1 through 999 issued between the years 1969-1987.
		This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo.
	www.cse.ohio-state.edu /cgi-bin/rfc/rfc1175.html (10278 words)

	RFC1175 (Site not responding. Last check: 2007-11-07)
		RFC 1175 FYI - Bibliography August 1990 and routing as well as protocol layering; explores the core gateway system and protocol gateways used to exchange routing information; and discusses application level services available in the Internet.
		RFC 1175 FYI - Bibliography August 1990 summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987.
		RFC 1175 FYI - Bibliography August 1990 numbers that are assigned specific values for actual use, and lists the currently assigned values.
	www.rfc.net /rfc1175.html (10361 words)

	Variable Length Subnet Mask
		There aren't many ways to really use a network efficiently.
		The RFC 1009, implemented in 1987; which states that it is possible to use more than one subnet due to the different sizes of the extended network prefixes.
		As I said earlier having a flat network is a great disadvantage, because once the subnet mask is defined; it locks the network into a fixed number of subnets.
	www.comptechdoc.org /os/linux/manual4/variablesubnet.html (326 words)

Try your search on: Qwika (all wikis)