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
Bit
Click on the red underlined text to get to the source
... function. Given a character string, the caller wants one or more
32 bit IP addresses. Under the DNS, it translates into a request
...
...
This function will often follow the form of previous functions.
Given a 32 bit IP address, the caller wants a character string.
...
... bit map. The bit map
must be a multiple of 8 bits long.
The WKS record is used to describe the well known services ...
... IP protocol number, and the bit map has
one bit per port of the specified protocol. The first bit
...
... one bit per port of the specified protocol. The first bit
corresponds to port 0, the second to port ...
... corresponds to port 0, the second to port 1, etc. If the bit map
does not include a bit for a protocol of interest, that bit ...
... port 1, etc. If the bit map
does not include a bit for a protocol of interest, that bit is
assumed zero. The appropriate values and mnemonics ...
... bit map
does not include a bit for a protocol of interest, that bit is
assumed zero. The appropriate values and mnemonics for ports ...
...
For example, if PROTOCOL=TCP (6), the 26th bit corresponds to TCP
port 25 (SMTP). If this bit ...
... bit corresponds to TCP
port 25 (SMTP). If this bit is set, a SMTP server should be
listening on TCP port ...
... There are a variety of methods used in this standard to map IPv4
addresses to 32 bits fields in the HYPERchannel headers. This
...
... BOOTP packet is never fragmented.
Any numeric fields shown are packed in 'standard network byte
order', i.e., high order bits are sent first.
In the IP header ...
... The entire process of PMTU discovery is predicated on the use of the
DF bit in the IPv4 header, an ICMP message ...
... IPv4 networks. There are many
references to a specified IP version number of 4 and 32-bit
addresses. This is incompatible with IPv6 ...
... IPv4 networks. There are many
references to a specified IP version number of 4 and 32-bit
addresses. This is incompatible with IPv6 ...
... 16 bits Hardware type
ar$pro 16 bits Protocol type of the protocol fields below
ar$op 16 bits ...
... 16 bits Protocol type of the protocol fields below
ar$op 16 bits Operation code (request, reply, or NAK)
ar$pln 8 bits ...
... 16 bits Operation code (request, reply, or NAK)
ar$pln 8 bits byte length of each protocol address
ar$rhl 8 bits ...
... 8 bits byte length of each protocol address
ar$rhl 8 bits requester's HIPPI hardware address length (q)
...
... HIPPI hardware address length (x)
ar$rpa 32 bits requester's protocol address
ar$tpa 32 bits ...
... +---------------+---------------+---------------+---------------+
12 | thl = (x) | Requester IP Address upper (24 bits) |
+---------------------------------------------------------------+
13 | Req. IP ...
... 13 | Req. IP lower | Target IP Address upper (24 bits) |
+---------------+-----------------------------------------------+
14 | Tgt. IP ...
... architecture, where a
modification is needed to use both addresses of a 31-bit prefix.
This is possible by IPv6 address ...
... Endpoint addresses: 32 bits each ...
... version of IP (IP v6) will certainly have a
sufficient number of bits in its addressing space to provide an
address ...