Multicast Addresses for Documentation (original) (raw)
Related papers
2017
This document is subject to BCP 78 and the IETF Trust’s Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
2008
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. A single physical link can have multiple prefixes assigned to it. In that environment, end hosts might have multiple IP addresses and be required to use them selectively. RFC 3484 defines default source and destination address selection rules and is implemented in a variety of OSs. But, it has been too difficult to use operationally for several reasons. In some environments where multiple prefixes are assigned on a single physical link, the host using the default address selection rules will experience some trouble in communication. This document describes the possible problems that
Network Working Group A. Matsumoto
2008
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. There are some problematic cases when using the default address selection mechanism that RFC 3484 defines. This document describes additional requirements that operate with RFC 3484 to solve the
Network Working Group Internet-Draft
draft-duerst-iri-01 This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at
In today's connected age, almost everyone knows what the Internet is. However, very few people have an idea about the workings of this worldwide network. The Internet, as we know it today, has had a long history of evolution and like any other interesting and useful invention, is governed by a set of rules and protocols. This blog introduces the reader to the basics of the fundamental protocol behind the workings of the Internet – the Internet Protocol, and the current and upcoming versions of this protocol. The current Internet Protocol, IPv4, is the original standard Internet Protocol set up for handling IP addresses when the Internet was initial developed by DARPA (Defense Advanced Research Projects Agency) in the early 1970s. The IPv4 uses a 32 bit address field which provides for 4,294,967,296 unique Internet addresses. This number was deemed to be more than enough to last beyond any foreseeable requirements because in the early 1970's the population of the earth was less than 4 billion people and personal computers did not exist. Now, the rapid explosion of the Internet fueled by the vast number of personal computers attaching to it, made it clear that the IPv4 address space was already consumed to the point that a replacement had to be found. The next generation IP, IPv6, was developed in response to this situation. In this paper, I will try to give a complete overview of this new protocol. I start by giving a history of the internet and its current protocol. Then I will describe the main features of the new protocol, IPv6, and how they have solved the current limitation of the current protocol.