RE: [Sigtran] M3UA: 1IPSP - multiple IPSPs traffic flow

"Tolga Asveren" <asveren@ulticom.com> Fri, 04 November 2005 15:38 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EY3eQ-0003kq-CR; Fri, 04 Nov 2005 10:38:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EY3eP-0003ke-BK for sigtran@megatron.ietf.org; Fri, 04 Nov 2005 10:38:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26306 for <sigtran@ietf.org>; Fri, 4 Nov 2005 10:38:21 -0500 (EST)
Received: from 192-73-206-10.ulticom.com ([192.73.206.10] helo=colby.ulticom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EY3tP-0001tS-6G for sigtran@ietf.org; Fri, 04 Nov 2005 10:54:16 -0500
Received: from pcasveren (pc-asveren.ulticom.com [172.25.33.55]) by colby.ulticom.com (8.13.4/8.12.10) with SMTP id jA4FcNmN018792 for <sigtran@ietf.org>; Fri, 4 Nov 2005 10:38:25 -0500 (EST)
From: Tolga Asveren <asveren@ulticom.com>
To: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA: 1IPSP - multiple IPSPs traffic flow
Date: Fri, 04 Nov 2005 10:20:45 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMKEANDIAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <6733C768256DEC42A72BAFEFA9CF06D210FB685B@ii0015exch002u.iprc.lucent.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Importance: Normal
X-Scanned-By: MIMEDefang 2.40
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Content-Transfer-Encoding: 7bit
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
Sender: sigtran-bounces@ietf.org
Errors-To: sigtran-bounces@ietf.org

This is implementation/traffic type dependent and is not something
standardized by M3UA.

> -----Original Message-----
> From: Prasad, Shashank S (Shashank) [mailto:ssprasad@lucent.com]
> Sent: Friday, November 04, 2005 10:28 AM
> To: 'Tolga Asveren'; sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA: 1IPSP - multiple IPSPs traffic flow
>
>
> Thanx Tolga. U are right in understanding my question.
>
> Followup Question:
> Since IPSP2 and IPSP3 are serving the same AS, what would determine at
> NodeB, if the traffic to IPSP1 is
> to be sent via IPSP2 or IPSP3 ?
>
>
> shashank
>
> -----Original Message-----
> From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org]On
> Behalf Of Tolga Asveren
> Sent: Friday, November 04, 2005 8:13 PM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA: 1IPSP - multiple IPSPs traffic flow
>
>
> Shashank,
>
> As far as I understand your question:
>
> You have IPSP1, IPSP2, IPSP3. You have one RK. IPSP sends ASPAC
> for this RK
> to IPSP2 and IPSP3. IPSP2 and IPSP3 are working in loadsharing
> mode. You are
> wondering whether IPSP1 will receive traffic from both IPSP2 and IPSP3.
>
> Yes, it can, but I wouldn't call it traffic being loadshared to
> IPSP1. IPSP2
> and IPSP3 are not the same entities. OTOH it makes sense to speak of
> loadharing traffic from IPSP1 to IPSP2 and IPSP3 because traffic from a
> single source is distrubuted to multiple peers.
>
>    Tolga
>
> > -----Original Message-----
> > From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org]On
> > Behalf Of Prasad, Shashank S (Shashank)
> > Sent: Friday, November 04, 2005 9:48 AM
> > To: 'sigtran@ietf.org'
> > Subject: [Sigtran] M3UA: 1IPSP - multiple IPSPs traffic flow
> >
> >
> > Hi,
> > I had a specific question related to a specific scenario explained below
> > (Single Exchange scenario)
> >
> > NodeA supports 1 PS with 1 IPSP
> > NodeB supports 1 PS with 2 IPSPs in Loadshared mode.
> >
> >
> > There are two associations between NodeA and NodeB.
> > The first association is between IPSP1 (NodeA) and IPSP2 (NodeB).
> > The second association is between IPSP1 (NodeA) and IPSP3 (NodeB).
> >
> > The IPSP2 and IPSP3, which are serving loadshared for the PS2 on NodeB,
> > send an ASP Up to IPSP1 serving for PS1 on NodeA. Which means
> > that IPSP2 and
> > IPSP3,
> > serving a loadshared PS2, are essentially telling NodeA to
> > loadshare all the
> > traffic
> > for PS2, between IPSP2 and IPSP3.
> >
> > The above concepts are also illustrated below....(I have purposefully
> > avoided AS-ACTIVE notification)
> >
> >
> >
> >          NodeA                   <------------NodeB------------>
> >
> >          PS1-IPSP1               PS2-IPSP2                 PS2-IPSP3
> >           |                        |                          |
> >           |<-----ASP Up------------|                          |
> >           |-------ASP Up Ack------>| (Assoc #1)               |
> >           |                        |                          |
> >           |                        |                          |
> >           |<--------------------ASP Up------------------------|
> (Assoc #2)
> >           |----------------------------ASP Up Ack------------>|
> >           |                        |                          |
> >           |                        |                          |
> >           |                        |                          |
> >           |<--ASP Active(Ldshr)----|                          |
> >           |------ASP Active Ack--->|                          |
> >           |                        |                          |
> >           |                        |                          |
> >           |                        |                          |
> >           |<--------------------ASP Active(Ldshr)-------------|
> >           |----------------------------ASP Up Ack------------>|
> >           |                        |                          |
> >           |                        |                          |
> >           |---NOTIFY(AS-ACTIVE)--->|                          |
> >           |--------------------------NOTIFY(AS-ACTIVE)------->|
> >           |                        |                          |
> >
> >
> >
> > Questions:
> > Assuming a single exchange scenario, would the traffic towards
> > PS1 on NodeA,
> >
> > be also loadshared across 2 associations ?
> >
> > I thought it would and hence another follow-up question:
> > It looks like a loadshared peer (NodeB in our case) with
> multiple IPSPs,
> > is putting a constraint on the NodeA, to ALSO be ready to
> receive data on
> > multiple associations and possibly loadshared. Is this a fair
> > understanding
> > ?
> >
> >
> > shashank
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >
>
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>



_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran