|Deletions are marked like this.||Additions are marked like this.|
|Line 52:||Line 52:|
|* the ISO 8073 specification is available as [http://www.ietf.org/rfc/rfc0905.txt RFC905])||* the ISO 8073 specification is available as [http://www.ietf.org/rfc/rfc0905.txt RFC905]|
Connection Oriented Transport Protocol (COTP, ISO 7073)
This is the connection transport protocol of the IsoProtocolFamily.
As most readers nowadays will be more familiar with ["TCP"], COTP is explained comparing both protocols as they are both used to transport users's data reliably over a network.
Packet-based vs. stream-based: COTP transports packets of data from one user to the other, so the receiver will get exactly the same data boundaries as the sender transmitted. ["TCP"] transports a continuous stream of data to the receiver, so the protocol on top of TCP often has to add such boundaries itself (see the ["TPKT"] protocol for such a protocol).
TSAP's vs. ports: To multiplex several conversations between two hosts, COTP uses TSAP's which are variable length binary blobs (often a meaningful string is used). These TAP's are matched at connection establishing phase, and replaced by the 2 byte (destination/source) references at data transfer. TCP uses ports for this. One remarkable difference is that TSAP's are singletons - if a TSAP is used for a connection it cannot be used by another.
This protocol has been replaced by ["TCP"] in most applications. Applications that used COTP before, will often use the ["TPKT"] protocol on top of ["TCP"] now.
- ["CLNP"]: COTP uses ["CLNP"] as its underlying network protocol.
XXX - Add example traffic here (as plain text or Ethereal screenshot).
The COTP dissector is fully functional.
- Reassemble segmented COTP datagrams: XXX - add info here
- Display TSAPs as string or bytes: The TSAP's can be any binary data. Often applications chooses textual representation, so the default setting "As strings if printable" might be a good idea in many cases.
Example capture file
XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Ethereal can open gzipped files automatically.
A complete list of COTP display filter fields can be found in the [http://www.ethereal.com/docs/dfref/c/cotp.html display filter reference]
Show only the COTP based traffic:
Show only the COTP based traffic, except for the COTP Data (cotp.type == 0x06) and Acknowledge (cotp.type == 0x0f) TPDU's. This way you will only see special packets like connection establishing or expedited data:
cotp && !(cotp.type == 0x06 || cotp.type == 0x0f)
You cannot directly filter COTP protocols while capturing. XXX - add information about capturing of lengths smaller than 1450? bytes or even better ways to capture only COTP.
the ISO 8073 specification is available as [http://www.ietf.org/rfc/rfc0905.txt RFC905]