
	Where results make sense

Topic: RFC 1918

Related Topics

CIDR

Network address translation

VAS

Irish general election, 1918

Old Nubian

RBMK

Caliber

Naboo

Orania

Superficial anatomy

Raga

BIF

Carlsten

Epode

Ezekiel

In the News (Wed 11 Nov 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	RFC 1918 (rfc1918) - Address Allocation for Private Internets
		RFC 1918: Is IP addresses starting with 169.254.0.0 considered in IP address space for...
		RFC 1918: If a public IP(64.27.12.150 for http://odissei.atspace com) is hit from a...
		RFC 1918: There should be a reference to the other non globally routable IP addresses used...
	www.faqs.org /rfcs/rfc1918.html (3106 words)

	BCP5
		RFC 1918 Address Allocation for Private Internets February 1996 Moving a host from private to public or vice versa involves a change of IP address, changes to the appropriate DNS entries, and changes to configuration files on other hosts that reference the host by IP address.
		RFC 1918 Address Allocation for Private Internets February 1996 A major drawback to the use of private address space is that it may actually reduce an enterprise's flexibility to access the Internet.
		RFC 1918 Address Allocation for Private Internets February 1996 If a suitable subnetting scheme can be designed and is supported by the equipment concerned, it is advisable to use the 24-bit block (class A network) of private address space and make an addressing plan with a good growth path.
	www.unix.org.ua /rfc/bcp0005.html (2679 words)

	RFC2101
		To summarize, since RFC 1918, we have not really changed the spatial uniqueness of an address, so much as recognized that there are multiple spaces.
		RFC 2101 IPv4 Address Behavior Today February 1997 ANNEX: Current Practices for IPv4 Address Allocation and Routing Initially IP address structure and IP routing were designed around the notion of network number classes (Class A/B/C networks) [RFC 790].
		RFC 2101 IPv4 Address Behavior Today February 1997 protocols are required to handle reachability (addressing) information expressed in terms of variable length address prefixes, and forwarding is required to implement the "longest match" algorithm.
	www.unix.org.ua /rfc/rfc2101.html (3939 words)

	RFC 1918 - Address Allocation for Private Internets. Y. Rekhter, B. Moskowitz, D. Karrenberg, G. J. de Groot, E. Lear. (Site not responding. Last check: 2007-10-10)
		RFC 1918 Address Allocation for Private Internets February 1996 Moving a host from private to public or vice versa involves a change of IP address, changes to the appropriate DNS entries, and changes to configuration files on other hosts that reference the host by IP address.
		RFC 1918 Address Allocation for Private Internets February 1996 A major drawback to the use of private address space is that it may actually reduce an enterprise's flexibility to access the Internet.
		RFC 1918 Address Allocation for Private Internets February 1996 If a suitable subnetting scheme can be designed and is supported by the equipment concerned, it is advisable to use the 24-bit block (class A network) of private address space and make an addressing plan with a good growth path.
	sunsite.auc.dk /RFC/rfc/rfc1918.html (2644 words)

	RFC 1918 (rfc1918)
		A separate and far more pressing concern is that the amount of routing overhead will grow beyond the Rekhter, et al Best Current Practice [Page 1] RFC 1918 Address Allocation for Private Internets February 1996 capabilities of Internet Service Providers.
		Rekhter, et al Best Current Practice [Page 4] RFC 1918 Address Allocation for Private Internets February 1996 Moving a host from private to public or vice versa involves a change of IP address, changes to the appropriate DNS entries, and changes to configuration files on other hosts that reference the host by IP address.
		Rekhter, et al Best Current Practice [Page 5] RFC 1918 Address Allocation for Private Internets February 1996 A major drawback to the use of private address space is that it may actually reduce an enterprise's flexibility to access the Internet.
	www.cse.ohio-state.edu /cgi-bin/rfc/rfc1918.html (2569 words)

	RFC 1918 - (rfc1918) - Address Allocation for Private Internets (Site not responding. Last check: 2007-10-10)
		Rekhter, et al Best Current Practice [Page 4] RFC 1918 Address Allocation for Private Internets February 1996 Moving a host from private to public or vice versa involves a change of IP address, changes to the appropriate DNS entries, and changes to configuration files on other hosts that reference the host by IP address.
		Rekhter, et al Best Current Practice [Page 5] RFC 1918 Address Allocation for Private Internets February 1996 A major drawback to the use of private address space is that it may actually reduce an enterprise's flexibility to access the Internet.
		Once one commits to using a private address, one is committing to renumber part or all of an enterprise, should one decide to provide IP connectivity between that part (or all of the enterprise) and the Internet.
	www.rfcsearch.org /rfcview/RFC/1918.html (2579 words)

	Roxen Community: RFC 3882 Configuring BGP to Block Denial-of-Service Attacks (Informational)
		Assuming the router is properly configured to direct RFC 1918 destined traffic to a null interface, traffic destined to the attacked network gets dropped, making the attacked network unreachable to the attacker and everyone else.
		Even if a static route pointing an RFC 1918 address to a null interface is not configured on all routers within the destination AS, the modified next hop makes the traffic un-routable to its legitimate destination.
		To be able to alter the next hop on the border router, a subnet of an RFC 1918 network is statically routed to the tunnel interface.
	community.roxen.com /developers/idocs/rfc/rfc3882.html (2352 words)

	RFC 2647 - Benchmarking Terminology for Firewall Performance
		Connections to public networks are made by use of a device that translates one or more RFC 1918 addresses to one or more public addresses--a network address translator (NAT).
		Newman Informational [Page 16] RFC 2647 Firewall Performance Terminology August 1999 The use of private addressing also introduces a security benefit in that RFC 1918 addresses are not visible to hosts on the public Internet.
		Newman Informational [Page 17] RFC 2647 Firewall Performance Terminology August 1999 Discussion: Security policies generally do not spell out specific configurations for firewalls; rather, they set general guidelines for what is and is not acceptable network access.
	www.packetizer.com /rfc/rfc2647 (4891 words)

	Private IP address
		This means the addresses are available for any use by anyone and therefore the same RFC 1918 IP addreses can be reused.
		Private IP addresses also provide a basic form of security as in a typical network configuation of this type it is not possible for the outside world (Internet) to establish a connection directly to a host using these addresses.
		256 contiguous class Cs RFC 1597 was the original specification but is now for historical purposes only.
	www.ebroadcast.com.au /lookup/encyclopedia/rf/RFC_1918.html (127 words)

	rfc2101
		Informational [Page 4] RFC 2101 IPv4 Address Behavior Today February 1997 At the other end of the spectrum is a Network Address Translator (NAT) [RFC 1631].
		Informational [Page 8] RFC 2101 IPv4 Address Behavior Today February 1997 ANNEX: Current Practices for IPv4 Address Allocation & Routing Initially IP address structure and IP routing were designed around the notion of network number classes (Class A/B/C networks) [RFC 790].
		Informational [Page 9] RFC 2101 IPv4 Address Behavior Today February 1997 protocols are required to handle reachability (addressing) information expressed in terms of variable length address prefixes, and forwarding is required to implement the "longest match" algorithm.
	www.nalanda.nitc.ac.in /misc/rfc/html/rfc2101.html (4007 words)

	RFC 4600 - 4699 (Site not responding. Last check: 2007-10-10)
		RFC 1918, RFC 2119, RFC 2858, RFC 3446, RFC 3618, RFC 4271, RFC 4601.
		RFC 2119, RFC 2277, RFC 4234, RFC 4646.
		RFC 1766, RFC 2616, RFC 3066, RFC 3282.
	www.networksorcery.com /enp/rfc4600.htm (1052 words)

	RFC3879 (Site not responding. Last check: 2007-10-10)
		In theory, the private addresses defined in RFC 1918 should only be used locally, and should never appear in the Internet.
		RFC 3879 Deprecating Site Local Addresses September 2004 The experience with RFC 1918 addresses also shows some non trivial leaks, besides placing these addresses in IP headers.
		RFC 3879 Deprecating Site Local Addresses September 2004 Network management complexity is also increased by the fact that though sites could be supported using existing routing constructs-- such as domains and areas--the factors driving creation and setting the boundaries of sites are different from the factors driving those of areas and domains.
	rfc.net /rfc3879.html (2949 words)

	RFC 2101 (Site not responding. Last check: 2007-10-10)
		Scaling capabilities of CIDR are based on the assumption that address allocation reflects network topology as much as possible, and boundaries for aggregation of addressing information are not required to be fully contained within a single organization - they may span multiple organizations (e.g., provider with its subscribers).
		Since we deployed multicast [RFC 1112], we must separate the debate over meaning of IP addresses into meaning of source and destination addresses.
		[RFC 1772] Rekhter, Y., and P. Gross, "Application of the Border Gateway Protocol in the Internet", RFC 1772, March 1995.
	library.n0i.net /rfc/html/rfc2101.html (3852 words)

	BSCN Study Guide Outline
		RFC 1519 is concerned with efficiently assigning the existing address space.
		RFC 1918 gives guidelines on assigning private address space to your network.
		RFC 1918 specifies address ranges for each class of network for private use.
	www.geocities.com /mehrankohan/chapter_two.htm (5415 words)

	[No title]
		Hain Informational [Page 12] RFC 2993 Architectural Implications of NAT November 2000 One of the greatest concerns from the explosion of NATs is the impact on the fledgling efforts at deploying network layer end-to-end IP security.
		Hain Informational [Page 21] RFC 2993 Architectural Implications of NAT November 2000 An alternative methodology would be to translate the packets between IPv6 and IPv4 at the boarders between IPv4 supporting networks and IPv6 supporting networks.
		The need for this functionality was recognized in [RFC 1752], the document that recommended to the IETF that IPv6 be developed and recommended that a set of working groups be established to work on a number of specific problems.
	www.isi.edu /in-notes/rfc2993.txt (8767 words)

	RFC 3056
		IPv6 packets are transmitted in IPv4 packets [RFC 791] with an IPv4 protocol type of 41, the same as has been assigned [MECH] for IPv6 packets that are tunneled inside of IPv4 frames.
		Specifically, this means that IPv4 addresses defined in [RFC 1918], broadcast, subnet broadcast, multicast and loopback addresses are unacceptable.
		[RFC 1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., de Groot, G. and E. Lear, "Address Allocation for Private Internets", BCP 5, RFC 1918, February 1996.
	www.apps.ietf.org /rfc/rfc3056.html (5846 words)

	RFC1918 (Site not responding. Last check: 2007-10-10)
		Network Working Group Y. Rekhter Request for Comments: 1918 Cisco Systems Obsoletes: 1627, 1597 B. Moskowitz BCP: 5 Chrysler Corp. Category: Best Current Practice D. Karrenberg RIPE NCC G.
		RFC 1918 Address Allocation for Private Internets February 1996 via IP connectivity) may be unnecessary and even undesirable for privacy/security reasons.
		RFC 1918 Address Allocation for Private Internets February 1996
	rfc.net /rfc1918.html (2679 words)

	RFC 1918 - Address Allocation for Private Internets. Y. Rekhter, B. Moskowitz, D. Karrenberg, G. J. de Groot, E. Lear. (Site not responding. Last check: 2007-10-10)
		RFC 1918 - Address Allocation for Private Internets.
		RFC 1918 Address Allocation for Private Internets February 1996 3.
		RFC 1918 Address Allocation for Private Internets February 1996 10.
	rfc.dotsrc.org /rfc/rfc1918.html (2644 words)

	Royal Air Force
		At the beginning of the war the RFC mainly used the BE-2, Avro 504, Vickers FB5 and the Bristol Scout.
		In July 1916 the RFC had a total strength of twenty-seven squadrons (421 aircraft), with four kite-balloon squadrons and fourteen balloons.
		By the beginning of 1918 the RFC had grown rapidly and it now operated 4,000 combat aircraft and employed 114,000 personnel.
	www.spartacus.schoolnet.co.uk /FWWraf.htm (207 words)

	1918 - Webled.com (Site not responding. Last check: 2007-10-10)
		[ RFC 1918: The RFC 1918 should include all the reserve addresses for ]...
		[ RFC 1918: what is ip 172.16.0.0/12 by mamad (7/2/2005).
		In November 11 of 1918 the end of the war ]...
	www.webled.com /1918.htm (339 words)

	IP Addresses
		Various international wireless groups have already setup their own networks and have begun to use private (RFC 1918) IP addresses mainly to avoid having to consult third parties and also to avoid the costs associated with requesting public IP addresses.
		Although the use of public IP addresses is not considered necessary, this may change in the future, when there is a large enough user base to justify this or if for example there is an interest of people on the Internet to connect IN to a wireless group.
		There is no agreed standard as to the number of addresses that should be assigned to a group, but it is recommended that the requested allocations be conservative, as it is always possible to request another block at a later stage.
	www.wl0.org /~sjmudd/wireless/network-structure/english/html/x78.html (1364 words)

	[No title]
		Note that (in pre-CIDR notation) the first block is nothing but a single class A network number, while the second block is a set of 16 contiguous class B network numbers, and third block is a set of 256 contiguous class C network numbers.
		Once one commits to using a private address, one is committing to renumber part or all of an enterprise, should one decide to provide IP connectivity between that part (or all of the enterprise) and the Internet.
		The other server would be reachable only from the private network and would contain the full set of data, including the private addresses and whatever public addresses are reachable the private network.
	www.ietf.org /rfc/rfc1918.txt (2569 words)

	[No title]
		However, the formal deprecation allows existing usage of site-local addresses to continue until the replacement is standardized and implemented.
		Manager Pain, Leaks The management of IPv6 site local addresses is in many ways similar to the management of RFC 1918 [RFC1918] addresses in some IPv4 networks.
		Private addresses end up being used as source or destination of TCP requests or UDP messages, for example in DNS or trace-route requests, causing the request to fail, or the response to arrive at unsuspecting hosts.
	www.isi.edu /in-notes/rfc3879.txt (2928 words)

	IANA \| Abuse Issues and IP Addresses
		Since the RFC 1918 addresses should never be used on the public Internet, there should be no names in the public DNS that refer to them.
		It is believed that the large majority of those queries occur because of "leakage" from intranets that are using the RFC 1918 private addresses.
		It is possible to construct network packets with forged source addresses that are in the RFC 1918 ranges.
	www.iana.org /faqs/abuse-faq.htm (2779 words)

	RFC 3000 - 3099 (Site not responding. Last check: 2007-10-10)
		References: RFC 1918, RFC 2002, RFC 2003, RFC 2119, RFC 2267, RFC 2402, RFC 2406, RFC 2486, RFC 2784, RFC 2890.
		RFC 1327, RFC 1521, RFC 2026, RFC 2028, RFC 2119, RFC 2234, RFC 2616, RFC 2860.
		[RFC 3068] An Anycast Prefix for 6to4 Relay Routers.
	www.networksorcery.com /enp/rfc3000.htm (2054 words)

	[No title]
		OVERVIEW This RFC is a snapshot of the ongoing process of the assignment of protocol parameters for the Internet protocol suite.
		This RFC has been assembled by catinating these files together with a minimum of formatting "glue".
		Reynolds & Postel [Page 64] RFC 1700 Assigned Numbers October 1994 TOS Value Description Reference --------- -------------------------- --------- 0000 Default [RFC1349] 0001 Minimize Monetary Cost [RFC1349] 0010 Maximize Reliability [RFC1349] 0100 Maximize Throughput [RFC1349] 1000 Minimize Delay [RFC1349] 1111 Maximize Security [RFC1455] The TOS value is used to indicate "better".
	www.ietf.org /rfc/rfc1700.txt?number=1918 (9722 words)

	RFC; The Royal Flying Corps
		The Royal Flying Corps was formed on 13th May 1912 and served through the majority of the First World War.
		On 1st April 1918, the RFC and the RNAS (Royal Navy Air Service) were separated from the army and the navy and merged to form a new service, the Royal Air Force.
		No attempt is made here to tell the whole RFC story.
	www.diggerhistory.info /pages-conflicts-periods/ww1/afc/rfc.htm (167 words)

	Cisco - Addressing an Unregistered Network Inside the PIX Firewall Using RFC 1918
		When it is possible, users of unregistered (or "dirty") networks should use the reserved addresses in RFC 1918
		As discussed in RFC 1918, the addresses that you should use are shown here.
		There are two advantages of using these numbers on the inside of the PIX.
	www.cisco.com /warp/public/110/8.html (241 words)

	Private (RFC1918) IP addresses
		This document defines a partitioning of the RFC1918 address space within the University of Cambridge to accommodate both CUDN-wide private internet and institutional private internets.
		It is pointless for this document to replicate those parts of the text of RFC1918 which are relevant for this purpose; reference should be made to the RFC for general details and rationale.
		This document does not discuss the further partitioning of RFC1918 private addresses to provide both an institution-wide private internet and private internets for the subunits within the institution.
	www.cam.ac.uk /cs/netdiv/rfc1918use.html (1432 words)

Try your search on: Qwika (all wikis)