1 - 2 - 3 - 4 - 6 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - Q - R - S - T - U - V - W - X
address
Click on the red underlined text to get to the source
...
This document is part of a document set aiming to document all usage
of IPv4 addresses in IETF standards. In an effort to have the
information in a manageable form, it has been broken into 7 documents
...
... Transport).
This specific document focuses on usage of IPv4 addresses within the
Internet area.
...
...
There are many implicit assumptions about the use of IPv4 addresses
in this document.
...
... RFC 903std38 Reverse Address Resolution Protocol ...
... 1. Host name to host address translation.
This function is often defined to mimic a previous HOSTS ...
... caller wants one or more
32 bit IP addresses. Under the DNS, it translates into a request
for type A RRs ...
... DNS does not preserve the order of RRs,
this function may choose to sort the returned addresses or select
the "best" address if the service ...
... this function may choose to sort the returned addresses or select
the "best" address if the service returns only one choice to the
client ...
... service returns only one choice to the
client. Note that a multiple address return is recommended, but a
single address may be the only way to emulate prior HOSTS ...
... client. Note that a multiple address return is recommended, but a
single address may be the only way to emulate prior HOSTS.TXT
services ...
... This function will often follow the form of previous functions.
Given a 32 bit IP address, the caller wants a character string.
The octets of the IP address ...
... IP address, the caller wants a character string.
The octets of the IP address are reversed, used as name
components, and suffixed with "IN-ADDR.ARPA". A type PTR query ...
... host. For
example, a request for the host name corresponding to IP address
1.2.3.4 looks for PTR RRs for domain name ...
... IN-ADDR.ARPA".
There are, of course, numerous examples of IPv4 addresses scattered
throughout the document.
...
...
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| ADDRESS |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
...
... A records cause no additional section processing. The RDATA section
of an A line in a master file is an Internet address expressed as
four decimal numbers separated by dots without any embedded spaces
(e.g.,"10.2.0.52" or "192.0.5.6").
...
...
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| ADDRESS |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| PROTOCOL | |
...
... services supported
by a particular protocol on a particular internet address. The
PROTOCOL field specifies an IP protocol number ...
... TCP port 25; if zero, SMTP service is not supported on
the specified address.
The purpose of WKS RRs ...
... IPv4 dependent.
There are, of course, numerous examples of IPv4 addresses scattered
throughout the document.
...
...
There are a variety of methods used in this standard to map IPv4
addresses to 32 bits fields in the HYPERchannel headers ...
... NetBIOS names of the form
IP.XX.XX.XX.XX will not work for IPv6 addresses since the length of
IPv6 addresses will not fit within the NetBIOS ...
... IP.XX.XX.XX.XX will not work for IPv6 addresses since the length of
IPv6 addresses will not fit within the NetBIOS 15 octet name
limitation.
...
...
The major concerns of this specification with respect to IPv4
addresses occur in the resolution of ARCnet 8bit addresses to IPv4
addresses ...
... The major concerns of this specification with respect to IPv4
addresses occur in the resolution of ARCnet 8bit addresses to IPv4
addresses in an "ARPlike" method. This is incompatible with IPv6 ...
... IPv4
addresses occur in the resolution of ARCnet 8bit addresses to IPv4
addresses in an "ARPlike" method. This is incompatible with IPv6.
...
...
This specification defines the use of IPv4 address on FDDI networks.
There are numerous IPv4 ...
... Type Code (2048 for IPv4) and
a corresponding Protocol Address length (4 bytes for IPv4) needs to
...
... In the IP header of a bootrequest, the client fills in its own IP
source address if known, otherwise zero. When the server address is
unknown, the IP ...
... IP header of a bootrequest, the client fills in its own IP
source address if known, otherwise zero. When the server address is
unknown, the IP destination address ...
... IP destination address will be the 'broadcast address'
255.255.255.255. This address means 'broadcast ...
... broadcast address'
255.255.255.255. This address means 'broadcast on the local cable,
(I don't know my net number)'.
...
... filled by server if client doesn't
know its own address (ciaddr was 0).
siaddr 4 server IP address ...
... address (ciaddr was 0).
siaddr 4 server IP address;
returned in bootreply by server.
...
... The Class field is one octet and indicates the identifier address
space. The most up-to-date values of the LCP Endpoint
...
... RFC 2390draft Inverse Address Resolution Protocol ...
... RFC 2462draft IPv6 Stateless Address Autoconfiguration ...
...
The section "Unicast Address Mappings" has the following text:
For implementations of this memo, the first two octets of the host ...
... number will always be zero and the last four octets will be the
node's four octet IP address. This makes address mapping trivial
for unicast ...
... node's four octet IP address. This makes address mapping trivial
for unicast transmissions: the first two octets of the host ...
... unicast transmissions: the first two octets of the host number
are discarded, leaving the normal four octet IP address. The
encapsulation code should use this IP address ...
... IP address. The
encapsulation code should use this IP address as the destination
address of the UDP/IP tunnel ...
... encapsulation code should use this IP address as the destination
address of the UDP/IP tunnel packet.
...
... IP tunnel packet.
This mapping will not be able to work with IPv6 addresses.
There are also numerous discussions ...
... to map between IP and IPX addresses. The specifics are not discussed
in the document and are left to the individual implementation.
...
... Network Specific Format" describes a
structure that reserves 12 digits for the textual representation of
an IP address.
This 12 octet ...
... This 12 octet field for decimal versions of IP addresses is
insufficient for a decimal version of IPv6 addresses ...
... addresses is
insufficient for a decimal version of IPv6 addresses. It is possible
to define a new encoding using the 20 digit long IP Address ...
... IPv6 addresses. It is possible
to define a new encoding using the 20 digit long IP Address + Port +
Transport ...
... Transport Set fields in order to accommodate a binary version of an
IPv6 address, port number and Transport Set. There are several
...
...
This specification defines a mechanism for devices to assign IPv4
addresses to PPP clients once PPP ...
... IPCP option types which
embed the IP address in 4-byte long fields. This is clearly not
enough for IPv6 ...
...
Although the examples used in this document use IPv4 addresses,
(i.e., A records) there is nothing in the specification to preclude
...
... There are no IPv4 dependencies in this specification. The only
reference to IP addresses discuss the use of an anycast address, so
but one can assume that these techniques are IPv6 ...
... IPv4 dependencies in this specification. The only
reference to IP addresses discuss the use of an anycast address, so
but one can assume that these techniques are IPv6 operable.
...
... that it is implicitly stated, as in:
ar$spln - length in octets of the source protocol address. Value
range is 0 or 4 (decimal). For IPv4 ar$spln is 4.
...
... IPv4 ar$spln is 4.
ar$tpln - length in octets of the target protocol address. Value
range is 0 or 4 (decimal). For IPv4 ar$tpln is 4.
...
... backward compatibility with previous implementations, a null
IPv4 protocol address may be received with length = 4 and an
allocated address in storage set to the value 0.0.0.0. Receiving ...
... IPv4 protocol address may be received with length = 4 and an
allocated address in storage set to the value 0.0.0.0. Receiving
stations must be liberal in accepting this format of a null IPv4
address ...
... address in storage set to the value 0.0.0.0. Receiving
stations must be liberal in accepting this format of a null IPv4
address. However, on transmitting an ATMARP or InATMARP packet, a
...
... transmitting an ATMARP or InATMARP packet, a
null IPv4 address must only be indicated by the length set to zero
and must have no storage allocated.
...
... DSS (code 6)
Length is (n * 4) and the value is an array of n IP addresses,
each four bytes in length. The maximum number of addresses is
...
... Length is (n * 4) and the value is an array of n IP addresses,
each four bytes in length. The maximum number of addresses is
5 and therefore the maximum length value is 20. The list
contains the addresses ...
... addresses is
5 and therefore the maximum length value is 20. The list
contains the addresses of n NetWare Domain SAP ...
... NEAREST_NWIP_SERVER (code 7)
Length is (n * 4) and the value is an array of n IP addresses,
each four bytes in length. The maximum number of addresses is
...
... Length is (n * 4) and the value is an array of n IP addresses,
each four bytes in length. The maximum number of addresses is
5 and therefore the maximum length value is 20. The list
contains the addresses ...
... addresses is
5 and therefore the maximum length value is 20. The list
contains the addresses of n Nearest NetWare/IP servers.
...
... DSS (code 11)
Length of 4, and the value is a single IP address. This field
identifies the Primary Domain SAP ...
...
TIP transaction manager addresses take the form:
<hostport><path>
...
... where <host> is either a <dns name> or an <ip address>; and <port>
is a decimal number specifying the port ...
... receiver of the command.
An <ip address> is an IP address, in the usual form: four decimal
numbers separated by period characters.
...
...
An <ip address> is an IP address, in the usual form: four decimal
numbers separated by period characters.
...
...
where <transaction manager address> identifies the TIP transaction
manager (as defined in Section 7 above); and <transaction ...
... identifier. In this non-standard case, it is the
combination of <transaction manager address> and <transaction
identifier ...
...
This document is only defined for IPv4 addresses. An IPv6
specification may be needed.
...
...
This document is only defined for IPv4 addresses. An IPv6
specification may be needed.
...
...
This document uses the generic term "IP Address" in the text but it
also contains the text:
...
... 8 bits target's HIPPI hardware address length (x)
ar$rpa 32 bits requester's protocol address ...
... hardware address length (x)
ar$rpa 32 bits requester's protocol address
ar$tpa 32 bits target ...
... 11 | op (ar$op) | pln (6) | rhl (q) |
+---------------+---------------+---------------+---------------+
12 | thl = (x) | Requester IP Address upper (24 bits) |
+---------------------------------------------------------------+
...
... +---------------------------------------------------------------+
13 | Req. IP lower | Target IP Address upper (24 bits) |
+---------------+-----------------------------------------------+
...
... 14 | Tgt. IP lower | Requester HIPPI Hardware Address bytes 0 - 2 |
+---------------+-----------------------------------------------+
15 | Requester HIPPI ...
... +---------------+-----------------------------------------------+
15 | Requester HIPPI Hardware Address bytes 3 - 6 |
+-----------------------------------------------+---------------+
16 | Requester HW Address ...
... Hardware Address bytes 3 - 6 |
+-----------------------------------------------+---------------+
16 | Requester HW Address bytes 7 - q | Tgt HW byte 0 |
+---------------+---------------+---------------+---------------+
...
... 17 | Target HIPPI Hardware Address bytes 1 - 4 |
+---------------------------------------------------------------+
18 | Target ...
... 18 | Target HIPPI Hardware Address bytes 5 - 8 |
+---------------+---------------+---------------+---------------+
19 |Tgt HW ...
...
This specification is specific to IPv4 address architecture, where a
modification is needed to use both addresses ...
... IPv4 address architecture, where a
modification is needed to use both addresses of a 31-bit prefix.
...
... Endpoint addresses: 32 bits each ...
...
The internet addresses of the two communicating parties for which the
link is being prepared.
...
... | Type | Code | Unused |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source IP address ...
... Destination IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NBMA ...
... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Source and Destination IP Addresses
Respectively, these are the IP addresses of the NARP ...
... Source and Destination IP Addresses
Respectively, these are the IP addresses of the NARP requester
and the target ...
... | Type | Code | Unused |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source IP address ...
... Destination IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NBMA ...
... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Source and Destination IP Address
Respectively, these are the IP addresses of the NARP ...
... Source and Destination IP Address
Respectively, these are the IP addresses of the NARP requester
and the target ...
... bits in its addressing space to provide an
address for even smaller GPS addressable units. In this
proposal, however, we assume the current version ...
... The problems have been fixed by defining new resource records for
IPv6 addresses.
...
... The problems have been fixed by defining new resource records for
IPv6 addresses.
...
...
This problem has been fixed by RFC 2462draft, IPv6 Stateless Address
Autoconfiguration, and RFC 3315prop, Dynamic Host Configuration Protocol
...
... Nesser II, P. and A. Bergstrom, Editor, "Introduction to the Survey of IPv4 Addresses in Currently Deployed IETF Standards", RFC 3789, June 2004. ...
... Authors' Addresses ...
... any copyrights, patents or patent applications, or other
proprietary rights that may cover technology that may be required
to implement this standard. Please address the information to the
IETF at ietf-ipr@ietf.org.
...