Subject: [Sigtran] Allowing Double Exchange in M3UA

From: [email-masked]
Date: Thu, 28 Nov 2002 18:55:43 +0530

Hi,

HSS would agree with HP for the Double Exchange Model.
DE is a part of M3UA since version 10 and has been a part of HSS SIGTRAN for
long.
We already have customers who have applications using the DE Model. These
applications still require the flexibility offered by DE.
There was an agreement at the interop about the use of this model and we have
actually tested it with a few companies present there.
Since this model is already in use, and is actually more flexible than the SE,
DE should be a part of the M3UA Protocol.

With Regards
Anshoo.
www.hssworld.com

>  This is actually the point that we would like to
> discuss with you.
>
>  Unfortunately we didn't follow the discussion that
> occured, as far as I
> remember on a separate mailing list (by the way, is
> there a way to access
> the mail archive now). At the first plugtest,
> implementor's consensus was
> that the double ended model was more flexible than
> the SE mode.
>
>  Since then, things are getting much clearer for HP
> which got customers
> requests which does not fit into the simple AS-to-AS
> model which gets a
> consensus on the mailing list and we do feel this
> flexibility is now a MUST
> for the IPSP-IPSP case.
>
>  We have requests to support AS-to-several AS
> (namely hundred of AS): this
> make dynamic registration especially useful and from
> our perspective a MUST:
> It allows to define the AS RK as DPC(,SI) instead of
> having of hundred of
> symetric RK (OPC+DPC).
>
>  This is a real concrete business case. It has been
> successfully tested in
> interop sessions in DE mode.
>
>  Therefore, the DE mode must at least be kept in the
> standard.
> If we get too far in the standard to drop the SE
> mode, then both modes need
> to coexist to address different architecture.
>
> Best Regards,
> Herve

DISCLAIMER: This message is proprietary to Hughes Software Systems
Limited (HSS) and is intended solely for the use of the individual
to whom it is addressed. It may contain  privileged or confidential
information  and should not be circulated or used for any purpose other
than for what it is intended. If you have received this message in error,
please notify the originator immediately. If you are not the intended
recipient, you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. HSS accepts
no responsibility for loss or damage arising from the use of the information
transmitted by this email including damage from virus.

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