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

datagram


Click on the red underlined text to get to the source

... XML parser, as the regular structure lends itself handily to parsing and validation of the document/datagram and then processing the destination address, TTL ...
... of RFC 2279(-> 3629std63) [RFC2279]. All BLOAT document/datagrams MUST be well- formed and include the XMLDecl. ...
... character set restrictions of XML, the payload of IP datagrams (which MAY contain arbitrary data) MUST be encoded for transport. This RFC ...
... Example Datagram ...
... The following is an example IPoXML datagram with an empty payload: ...


... XML. TCPoXML datagrams encapsulated by IPoXML MAY omit the <?xml?> header ...
... Example Datagram ...
... The following is an example TCPoXML datagram with an empty payload: ...


... element MUST be encoded as in section 2.1. UDPoXML datagrams encapsulated by IPoXML MAY omit the <?xml?> header ...
... Example Datagram ...
... The following is an example UDPoXML datagram with an empty payload: ...


... This document provides for the transmission of BLOAT datagrams over two common families of physical layer transport ...
... BLOAT is encapsulated in Ethernet datagrams as in [RFC894] with the exception that the type field ...


... ELEMENT total.length EMPTY> <!-- total length of datagram (header and payload) in octets, MUST be ...


... Postel, J., "User Datagram Protocol", STD 6, RFC 768std6, August 1980. ...
... Hornig, C., "Standard for the Transmission of IP Datagrams over Ethernet Networks.", RFC 894std41, April 1984. ...
... Postel, J. and J. Reynolds, "Standard for the Transmission of IP Datagrams Over IEEE 802 Networks", STD 43, RFC 1042std43 ...



Google
Web
RFC-Ref