Differences between revisions 3 and 4
Revision 3 as of 2007-11-18 21:09:38
Size: 2988
Editor: GuyHarris
Comment: Add what I think was a missing word.
Revision 4 as of 2008-04-12 17:50:22
Size: 3006
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
The P7 protocol allows a mail user agent to send and receive messages through an X.400 message store and the X.400 MTS. It is the X.400 equivalent to the the Internet ["IMAP"] protocol, providing services to manage the messages within the message store, rather than having to download them locally. The P7 protocol allows a mail user agent to send and receive messages through an X.400 message store and the X.400 MTS. It is the X.400 equivalent to the the Internet [[IMAP]] protocol, providing services to manage the messages within the message store, rather than having to download them locally.
Line 8: Line 8:
The P7 message store access protocol was introduced in the X.400(88) version of the standards. It initially provided very limited management facilities, with no support for folders or even storage of submitted messages. These features were gradually introduced in subsequent versions of the standard. However, many P7 user agents still just retrieve the messages and manage them locally, which is more comparable with the ["POP3"] model. The P7 message store access protocol was introduced in the X.400(88) version of the standards. It initially provided very limited management facilities, with no support for folders or even storage of submitted messages. These features were gradually introduced in subsequent versions of the standard. However, many P7 user agents still just retrieve the messages and manage them locally, which is more comparable with the [[POP3]] model.
Line 12: Line 12:
 * ["ROS"]: Typically, P7 uses ["ROS"] during connection establishment (abstract syntaxes [http://oid.elibel.tm.fr/2.6.0.2.1 2.6.0.2.1], [http://oid.elibel.tm.fr/2.6.0.2.5 2.6.0.2.5], [http://oid.elibel.tm.fr/2.6.0.2.9 2.6.0.2.9]).
 * ["ACSE"]: Typically, P7 uses ["ACSE"] for association control (association context [http://oid.elibel.tm.fr/2.6.0.1.11 2.6.0.1.11])
 * ["COTP"]: Typically, P7 uses ["COTP"] as its transport protocol. The well known TCP port for P7 traffic is 102, though some Message Stores may listen on a dedicated port.
 * [[ROS]]: Typically, P7 uses [[ROS]] during connection establishment (abstract syntaxes [[http://oid.elibel.tm.fr/2.6.0.2.1|2.6.0.2.1]], [[http://oid.elibel.tm.fr/2.6.0.2.5|2.6.0.2.5]], [[http://oid.elibel.tm.fr/2.6.0.2.9|2.6.0.2.9]]).
 * [[ACSE]]: Typically, P7 uses [[ACSE]] for association control (association context [[http://oid.elibel.tm.fr/2.6.0.1.11|2.6.0.1.11]])
 * [[COTP]]: Typically, P7 uses [[COTP]] as its transport protocol. The well known TCP port for P7 traffic is 102, though some Message Stores may listen on a dedicated port.
Line 16: Line 16:
P7 may also optionally use ["RTSE"]. P7 may also optionally use [[RTSE]].
Line 24: Line 24:
The P7 dissector is partially functional have currently only implemented the message retrieval and message submission services. The administration services, and support for ["RTSE"] has not yet been included. The P7 dissector is partially functional have currently only implemented the message retrieval and message submission services. The administration services, and support for [[RTSE]] has not yet been included.
Line 34: Line 34:
 * attachment:SampleCaptures/P7.pcap  * [[attachment:SampleCaptures/P7.pcap]]
Line 37: Line 37:
A complete list of P7display filter fields can be found in the [http://www.wireshark.org/docs/dfref/protofirstletter/proto.html display filter reference] A complete list of P7display filter fields can be found in the [[http://www.wireshark.org/docs/dfref/protofirstletter/proto.html|display filter reference]]
Line 44: Line 44:
You cannot directly filter P7 protocols while capturing. However, if you know the ["TCP"] port used (see above), you can filter on that one. You cannot directly filter P7 protocols while capturing. However, if you know the [[TCP]] port used (see above), you can filter on that one.
Line 51: Line 51:
 * [http://www.itu.int/ITU-T/asn1/database/itu-t/x/x413/1999/MSAbstractService.html ASN.1 Module from ITU]
 * [http://www.itu.int/rec/T-REC-X.413-199906-I/en X.413 Recommendation]
 * [[http://www.itu.int/ITU-T/asn1/database/itu-t/x/x413/1999/MSAbstractService.html|ASN.1 Module from ITU]]
 * [[http://www.itu.int/rec/T-REC-X.413-199906-I/en|X.413 Recommendation]]

X.413 Message Store: Abstract Service (P7)

The P7 protocol allows a mail user agent to send and receive messages through an X.400 message store and the X.400 MTS. It is the X.400 equivalent to the the Internet IMAP protocol, providing services to manage the messages within the message store, rather than having to download them locally.

History

The P7 message store access protocol was introduced in the X.400(88) version of the standards. It initially provided very limited management facilities, with no support for folders or even storage of submitted messages. These features were gradually introduced in subsequent versions of the standard. However, many P7 user agents still just retrieve the messages and manage them locally, which is more comparable with the POP3 model.

Protocol dependencies

  • ROS: Typically, P7 uses ROS during connection establishment (abstract syntaxes 2.6.0.2.1, 2.6.0.2.5, 2.6.0.2.9).

  • ACSE: Typically, P7 uses ACSE for association control (association context 2.6.0.1.11)

  • COTP: Typically, P7 uses COTP as its transport protocol. The well known TCP port for P7 traffic is 102, though some Message Stores may listen on a dedicated port.

P7 may also optionally use RTSE.

Example traffic

XXX - Add example decoded traffic for this protocol here (as plain text or Wireshark screenshot).

Wireshark

The P7 dissector is partially functional have currently only implemented the message retrieval and message submission services. The administration services, and support for RTSE has not yet been included.

Preference Settings

There is a single preference field for the P7 dissector, the P7 TCP Port - the port to which P7 associations are made. The default value is 102.

Example capture file

XXX - Add a simple example capture file to the SampleCaptures page and link from here (see below). Keep this file short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.

Display Filter

A complete list of P7display filter fields can be found in the display filter reference

  • Show only the P7 based traffic:

     p7

Capture Filter

You cannot directly filter P7 protocols while capturing. However, if you know the TCP port used (see above), you can filter on that one.

  • Capture only the P7 traffic over the non-standard port (103):

     tcp port 103

Discussion

X413 (last edited 2008-04-12 17:50:22 by localhost)