Re: DRN and TID Label Issues - Issue #7

Lincoln,

Why should it need to be a new ASP?  We don't have that requirement
currently.  Why not an existing ASP?  How does one of the existing
ASPs pick up the traffic of a failed ASP or one that is taken out
of service?

How are you going to upgrade a loadshare AS that has 2 ASPs?

--brian

Haresign Lincoln wrote:                                           (Wed, 11 Oct 2006 16:26:08)
> Brian,
> 
> All new dialogs will be loadshared, obviously existing dialogs can not
> be routed unless another ASP becomes Active and takes over that range of
> TIDs.
> 
> Lincoln
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:[email protected]] 
> Sent: Wednesday, October 11, 2006 3:59 PM
> To: Haresign Lincoln; Barry Nagelberg; [email protected]
> Subject: DRN and TID Label Issues - Issue #7
> 
> Lincoln,
> 
> RFC 3868 says:
> 
> 4.3.4.4.  ASP Inactive Procedures
> 
>    ...
> 
>    In the case of a Loadshare mode AS, the SGP moves the ASP to the
>    ASP-INACTIVE state and the AS traffic is reallocated across the
>    remaining ASPs in the state ASP-ACTIVE, as per the loadsharing
>    algorithm currently used within the AS.  A Notify message
>    ("Insufficient ASP resources active in AS") MAY be sent to all
>    inactive ASPs, if required.  An ASP Inactive Ack message is sent to
>    the ASP after all traffic is halted and Layer Management is informed
>    with an M-ASP_INACTIVE indication primitive.
> 
> Application of DRN/TID label is inconsistent with this procedure for
> loadshare AS.
> 
> --brian
> 
> --
> Brian F. G. Bidulock
> [email protected]
> http://www.openss7.org/

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