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

TCP


Click on the red underlined text to get to the source

... IP [RFC791]), and two associated transport layer protocols (TCP [RFC793] and UDP ...
... transport protocols are maintained in this RFC despite the optimizations that could be made if the line were somewhat blurred (i.e. merging TCP and IP into a single, larger element ...
... existing protocols remain unchanged. Routing, address spaces, TCP congestion control, etc. behave as specified in the extant standards. ...


... TCP Description ...
... A number of items have changed from the original TCP specification. Bit-masks, where present have been converted into human-readable ...
... To calculate the length and checksum fields of the TCP element, a canonicalized form of the element ...
... element MUST be encoded as in section 2.1. The TCP offset element was expanded to a maximum of 255 from 16 to allow for the increased size of the header ...
... <!DOCTYPE tcp PUBLIC "-//IETF//DTD BLOAT 1.0 TCP//EN" "bloat.dtd"> <tcp> ...


... <!-- DTD for TCP over XML. Refer to this DTD ...
... <!DOCTYPE tcp PUBLIC "-//IETF//DTD BLOAT 1.0 TCP//EN" "bloat.dtd"> --> ...


... Security considerations that apply to IP, TCP and UDP also likely apply to BLOAT as it does not attempt to correct for issues not related to message format ...



Google
Web
RFC-Ref