Re: M3UA: ASP Route Availability to SG/STP

Howard,

In general, there is nothing stopping an MTP User from sending a
message for a destination, event if it has received an MTP-PAUSE.
Therefore, an ASP can send a message to 'Alpha' regardless of
whether it has received DUNA or DAVA.  MTP at the SG should treat
the ASP like any ohter MTP user or MTP peer and reissue a DUNA
(once for every 8 or 10 MTP-TRANSFER primitives for the unavailable
destination, or once every T8 for a peer arrangement).

--brian


Howard May wrote:                            (Mon, 01 Sep 2008 10:56:53)
> 
>    Hi, I would value some clarification on the following:
> 
> 
>    Does the M3UA protocol provision for any situation whereby an ASP can
>    route messages for point code `Alpha' to an SG without first receiving
>    a DAVA for point code `Alpha' from the SG. Specifically if the SG
>    terminates messages for PC `Alpha' does M3UA presume the route to
>    `Alpha' from the ASP is available as soon as the ASP becomes active on
>    that SG (without the reception of DAVA)?
> 
> 
>    Or put slightly differently:
> 
>    When connecting to an SG/STP such as shown in Figure 1 of RFC 4666
>    should the ASP presume to receive DAVA and DUNA indications for the
>    Point Code of STP1 in the same manner as it would for any other Route
>    or is the Point Code of STP1 different? Should the ASP presume the
>    Point Code of STP1 is available as soon as the ASP is active on SG1?
> 
> 
>    Best Regards
> 
> 
>    Howard

> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/sigtran


-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/