The P1 protocol handles the layout of a message sent from one
Message Transfer Agent (MTA) to another
Message Transfer Agent. This
Protocol is the equivalent of a letter and an envelope.
The 'envelope' is known as the P1 header and the 'letter' is
the
P2 Message.
Addresses of the recipient must be globally unique for the
P1 Protocol
So the address of the recipient is fully qualified (ie. looked up
using X.500 Directory Service).
(MGMT: check this link)
The P2 protocol is the way in which the
sender and the recipient know
in what format the message is being transmitted. This means that both
sides should be able to understand the meaning of the messages being sent.
The P3 protocol is how the Message Transfer Agent (MTA)
communicates
with the User Agent (UA).
The User Agent (UA)
prepares a message and transmits
it to the Message Transfer Agent (MTA)
. This protocol also is used to deliver
a message directly to the User Agent (UA)
from the Message Transfer Agent (MTA)
Because the User Agent
is not always available there is a Message Store.
The P7 Protocol is for communication between the User Agent (UA)
and the
Message Store (MS).
P7 provides facilities to select messages selectively
from the Message Store (MS)
Application Service Elements (ASEs) are abstractions of
a group of functions used by
Application Entities (AEs eg. Message Transfer Agents, User Agents)
to interact with each other. Their purpose is to help describe how
they provide services using the lower levels of the OSI model.
In X.400 the following ASEs are used
P1 Protocol
P2 Protocol
P3 Protocol
P7 Protocol
Application Service Elements (ASE)
This Page created by: Kevin Bushe, kbushe@alf2.tcd.ie.