RFC 3252:Binary Lexical Octet Ad-hoc Transport
RFC-Ref

address


Click on the red underlined text to get to the source

... encoding, the behavioral aspects of each of the existing protocols remain unchanged. Routing, address spaces, TCP congestion control ...


... validation of the document/datagram and then processing the destination address, TTL, and checksum before sending it on to its ...
... Bit-masks, where present have been converted into human-readable values. IP addresses are listed in their dotted- decimal notation [RFC1123]. Length and checksum ...
... <checksum value="8707"/> <source address="10.0.0.22"/> <destination address="10.0.0.1"/> ...
... <source address="10.0.0.22"/> <destination address="10.0.0.1"/> <options> <end copied="0" class ...


... physical layer transport. Future RFCs will address additional transports as routing vendors ...


... <!ELEMENT source EMPTY> <!ATTLIST source address %IP4Addr; #REQUIRED> <!ELEMENT ...
... ELEMENT destination EMPTY> <!ATTLIST destination address %IP4Addr; #REQUIRED> <!ELEMENT ...
... <!ELEMENT hop EMPTY> <!ATTLIST hop address %IP4Addr; #REQUIRED> <!ELEMENT ...
... <!ATTLIST tstamp time %Digits; #REQUIRED address %IP4Addr; #IMPLIED> <!-- padding to bring header ...


... Author's Address ...



Google
Web
RFC-Ref