Subject: [Tsvwg] M2UA-15 minor comments

From: Jacob Heitz <[email-masked]>
Date: Wed, 06 Mar 2002 20:57:09 -0800

s/proces /process /
s/Tek/Tel/
s/to the unique Application Server/to an Application Server/
s/The M-ERROR message/The M-ERROR primitive/
s/inside M2UA/inside the M2UA/
s/The format for the BEAT message/The format of the Heartbeat Data parameter/
s/The format for the BEAT ACK message/The format of the Heartbeat Data parameter/
s/0verride/Override/
s/de-registration requires/de-registration/
s/MUST response/MUST respond/

In section 1.6.4, the "Purpose:" parts refer to ASP and SGP,
where the primitive is used in the same way on either the
SGP or the ASP. I think the references to "ASP" and "SGP" in some
of these cases should be changed to "M2UA" and "M2UA peer".

In section 5.3.1, there is an "Emer Cfm" primitive from MTP2
to MTP3. No such primitive exists in Q.703.

In section 5.3.3, there is an "LPO Cfm" primitive from MTP2
to MTP3. No such primitive exists in Q.703.
The example for STATUS_LPO_CLEAR should show something like
"LPO Rcvr Req" instead of "LPO Req".

In section 5.3.6, there is an "Clr RTB Req" primitive from MTP2
to MTP3. No such primitive exists in Q.703 for this direction.

In section 5.3.7, there is an "Flush Cfm" primitive from MTP2
to MTP3. No such primitive exists in Q.703.

In section 5.3.7, there is an "Cont Cfm" primitive from MTP2
to MTP3. No such primitive exists in Q.703.

-- 
// Jacob Heitz. Tel:510-747-2917

_______________________________________________
tsvwg mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/tsvwg