From exim@www1.ietf.org  Fri Aug  1 03:26:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01508
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 03:26:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iUIi-0004FQ-Na
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 03:26:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h717Q8K2016327
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 03:26:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iUIb-0004F3-5t; Fri, 01 Aug 2003 03:26:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iUII-0004EU-BZ
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 03:25:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01494
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 03:25:39 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19iUIG-00038U-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 03:25:40 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19iUIE-00038Q-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 03:25:38 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h717LDV03868
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 12:51:13 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h717P6R09952
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 12:55:06 +0530 (IST)
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OFB02DFC22.9C7FCC45-ON65256D75.0022CFF5@hss.hns.com>
Date: Fri, 1 Aug 2003 12:49:36 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 01/08/2003
 12:48:13 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>





Hi Some comments below

 When IPSP B receives ASPAC message from IPSP A for AS1 it marks remote
IPSP A active for remote AS1 and sends ASPAC ack back for AS1 to IPSP A.Now
with these message exchanges it means that IPSP A is ready to receive
traffic for AS1.At this point of time IPSP B has not expressed its
willingness to send data for any AS.IPSP B  cannot  send any application
data because its local applications are not active yet.So single direction
traffic flow will never occur.Now when IPSP B sends ASPAC message for AS2
to IPSP A and gets back ASPAC ack for AS2 it will give resume indication to
user now.AS1 and AS2 are basically same type of MTP3 users, and user to
user communication will only start if both users are ready and active.


    +-----------+              +-----------+
    |           |              |           |
    | IPSP A    |              | IPSP B    |
    |           +--------------+           |
    |           |              |           |
    +-----------+              +-----------+

        AS1                        AS2

Kamesh Kaul
www.hssworld.com
Hughes Software Systems





"VIvek Toky" <vivektoky@ccpu.com>@ietf.org on 07/31/2003 11:19:39 PM

Sent by:    sigtran-admin@ietf.org


To:    "Tolga Asveren" <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
cc:

Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour


Tolga,

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Tolga Asveren
Sent: Thursday, July 31, 2003 10:19 AM
To: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour


Vivek,
--- Vivek Toky <vivektoky@ccpu.com> wrote:
> Please see my comments inline
>
> > See my opigion online
> >
> > > -----Original Message-----
> > > From: Vivek Toky [mailto:vivektoky@ccpu.com]
> > > Sent: Thursday, July 31, 2003 2:42 PM
> > > To: Tolga Asveren; sigtran@ietf.org
> > > Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> > >
> > >
> > > Hi Tolga,
> > >   "Above case" means
> > > "when AS1 has activated itself by sending
> > >  ASP Active from both the IPSPs (A & B) but
> > >  AS2 has sent ASP Active just to IPSP_A."
> > >
> > > In my opinion IPSP_C should loadshare the
> traffic
> > > as it has received ASP active from both the
> IPSPs
> > > so AS1 is accessible through both of these.
> > > However, it is the responsibility of AS1 to
> route
> > > all the traffic towards AS2 through IPSP_A.
> >
> > If IPSP_B receive some traffic from IPSP_C BUT no
> AS is ACTIVE for
> it on
> > IPSP_C can it route this traffic???
> > CAN a SG send to a ss7 network a message receive
> from an INACTIVE
> ASP !
> > I don't think so!
> > IPSP DE must be considered as two ASP/SG head to
> tail.
> >
> [Vivek]
> AS is ACTIVE on IPSP_B (remember it sent ASP Active
> message)
[TOLGA]State of an AS is in the context of an ASP/SGP
pair. That ASP (IPSP_B) sends ACTIVE does not mean
that AS is ACTIVE for the SGP, unless SGP sends
ASPAC-ACK (IPSP_C in your example)

You are right, state of AS is in context of ASP, this was
what I wanted to say. I am assuming that SGP did send
ACTIVE ack back and ASP( for that AS) is active through
the SGP from which it got the ACK back. Is it fine now...


> As far as the SGP - ASP example see the following..
>
> 1. It is the AS which is Active or Inactive not ASP
> 2. ASPTM ptocedures are between SGPs and ASPs not SG
> and ASPs
>
> The local AS on the ASP may be active through some
> other
> SGP (say SGPy)to which an ACTIVE message has been
> sent.
> So SGP (say SGPx) should route the traffic to SS7
> coming from an
> ASP which is inactive for an AS, because that AS is
> Active through some other SGP and SS7 destination
> may still
> be able to send the traffic towards that AS through
> some
> other SGP
>
> In M3UA outgoing and Incoming Traffic flows are
> independent,
> so why restrict the traffic ?
>
> > >
> > > In either case I think it is worth mentioning in
>
> > > Implementor's guide whether Unidirectional
> traffic
> > > is possible between associations(in case of
> > > IPSP DE) or not.It will avoid any further
> > > confusion or possible interoperatibility issues.
> > >
> > > thanks,
> > >
> > > -Vivek.
> > >
> > > > Vivek,
> > > > --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > > > > Hi All,
> > > > >  What should be done in the following case:
> > > > >
> > > > >
> > > > >       |IPSP_A                             |
> > > > >   AS1 |      ---------------------- IPSP_C|
> AS2
> > > > >       |IPSP_B                             |
> > > > >
> > > > > IPSP_A and IPSP_B are in loadshare mode.
> > > > >
> > > > >   when AS1 has activated itself by sending
> > > > > ASP Active from both the IPSPs (A & B) but
> > > > > AS2 has sent ASP Active just to IPSP_A.
> > > > >
> > > > > What should IPSP_C do on receiving traffic
> for AS1?
> > > > >
> > > > > a) Loadshare the traffic towards IPSP_A and
> IPSP_B
> > > > >
> > > > > or
> > > > >
> > > > > b) It should send all the traffic to IPSP_A
> and
> > > > >    wait untill it sends ASP Active IPSP_B as
> well.
> > > > >    In the above case IPSP_B cannot send the
> traffic
> > > > >    towards IPSP_C but IPSP_C can.
> > > > [TOLGA]It should send all traffic to IPSPS_A.
> Which
> > > > case do you refer as "the above case", a) or
> b) ?
> > > > >
> > > > > thanks,
> > > > > Vivek.
> > > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! SiteBuilder - Free, easy-to-use web
> site design software
> > > > http://sitebuilder.yahoo.com
> > > >
> > > >
> _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > > >
> > >
> > > --
> > > Continuous Computing
> > > http://www.ccpu.com
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> >
> >
>
> --
> Continuous Computing
> http://www.ccpu.com


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

_______________________________________________
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



From exim@www1.ietf.org  Fri Aug  1 03:54:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02095
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 03:54:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iUjo-0005jN-5u
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 03:54:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h717s81s022029
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 03:54:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iUjh-0005ho-RM; Fri, 01 Aug 2003 03:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iUj0-0005h4-Pk
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 03:53:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02065
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 03:53:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19iUiy-0003IM-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 03:53:16 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19iUix-0003IJ-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 03:53:15 -0400
Received: from httpd by smtp.ccpu.com with local (Exim 4.20 #1 (Debian))
	id 19iUit-0001iE-O5; Fri, 01 Aug 2003 00:53:11 -0700
From: "Vivek Toky" <vivektoky@ccpu.com>
To: kakaul@hss.hns.com, sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
X-Mailer: NeoMail 1.25
X-IPAddress: 66.75.130.161
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Message-Id: <E19iUit-0001iE-O5@smtp.ccpu.com>
Date: Fri, 01 Aug 2003 00:53:11 -0700
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Kamesh,
 
  Single direction traffic will still be possible. If you look at my 
example carefully you will notice that in case of 3 IPSPs, it will be 
possible. It may be for a short duration of time. In my example local 
AS is already Active as it sent ASP Active message to one of the peer 
IPSPs ( also got the ACK back ) 

please go through the example again .. waiting for comments ?

Vivek
> 
> 
> 
> 
> Hi Some comments below
> 
>  When IPSP B receives ASPAC message from IPSP A for AS1 it marks 
remote
> IPSP A active for remote AS1 and sends ASPAC ack back for AS1 to 
IPSP A.Now
> with these message exchanges it means that IPSP A is ready to receive
> traffic for AS1.At this point of time IPSP B has not expressed its
> willingness to send data for any AS.IPSP B  cannot  send any 
application
> data because its local applications are not active yet.So single 
direction
> traffic flow will never occur.Now when IPSP B sends ASPAC message 
for AS2
> to IPSP A and gets back ASPAC ack for AS2 it will give resume 
indication to
> user now.AS1 and AS2 are basically same type of MTP3 users, and user 
to
> user communication will only start if both users are ready and 
active.
> 
> 
>     +-----------+              +-----------+
>     |           |              |           |
>     | IPSP A    |              | IPSP B    |
>     |           +--------------+           |
>     |           |              |           |
>     +-----------+              +-----------+
> 
>         AS1                        AS2
> 
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
> 
> 
> 
> 
> 
> "VIvek Toky" <vivektoky@ccpu.com>@ietf.org on 07/31/2003 11:19:39 PM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    "Tolga Asveren" <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
> cc:
> 
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> Tolga,
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On 
Behalf Of
> Tolga Asveren
> Sent: Thursday, July 31, 2003 10:19 AM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> Vivek,
> --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > Please see my comments inline
> >
> > > See my opigion online
> > >
> > > > -----Original Message-----
> > > > From: Vivek Toky [mailto:vivektoky@ccpu.com]
> > > > Sent: Thursday, July 31, 2003 2:42 PM
> > > > To: Tolga Asveren; sigtran@ietf.org
> > > > Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> > > >
> > > >
> > > > Hi Tolga,
> > > >   "Above case" means
> > > > "when AS1 has activated itself by sending
> > > >  ASP Active from both the IPSPs (A & B) but
> > > >  AS2 has sent ASP Active just to IPSP_A."
> > > >
> > > > In my opinion IPSP_C should loadshare the
> > traffic
> > > > as it has received ASP active from both the
> > IPSPs
> > > > so AS1 is accessible through both of these.
> > > > However, it is the responsibility of AS1 to
> > route
> > > > all the traffic towards AS2 through IPSP_A.
> > >
> > > If IPSP_B receive some traffic from IPSP_C BUT no
> > AS is ACTIVE for
> > it on
> > > IPSP_C can it route this traffic???
> > > CAN a SG send to a ss7 network a message receive
> > from an INACTIVE
> > ASP !
> > > I don't think so!
> > > IPSP DE must be considered as two ASP/SG head to
> > tail.
> > >
> > [Vivek]
> > AS is ACTIVE on IPSP_B (remember it sent ASP Active
> > message)
> [TOLGA]State of an AS is in the context of an ASP/SGP
> pair. That ASP (IPSP_B) sends ACTIVE does not mean
> that AS is ACTIVE for the SGP, unless SGP sends
> ASPAC-ACK (IPSP_C in your example)
> 
> You are right, state of AS is in context of ASP, this was
> what I wanted to say. I am assuming that SGP did send
> ACTIVE ack back and ASP( for that AS) is active through
> the SGP from which it got the ACK back. Is it fine now...
> 
> 
> > As far as the SGP - ASP example see the following..
> >
> > 1. It is the AS which is Active or Inactive not ASP
> > 2. ASPTM ptocedures are between SGPs and ASPs not SG
> > and ASPs
> >
> > The local AS on the ASP may be active through some
> > other
> > SGP (say SGPy)to which an ACTIVE message has been
> > sent.
> > So SGP (say SGPx) should route the traffic to SS7
> > coming from an
> > ASP which is inactive for an AS, because that AS is
> > Active through some other SGP and SS7 destination
> > may still
> > be able to send the traffic towards that AS through
> > some
> > other SGP
> >
> > In M3UA outgoing and Incoming Traffic flows are
> > independent,
> > so why restrict the traffic ?
> >
> > > >
> > > > In either case I think it is worth mentioning in
> >
> > > > Implementor's guide whether Unidirectional
> > traffic
> > > > is possible between associations(in case of
> > > > IPSP DE) or not.It will avoid any further
> > > > confusion or possible interoperatibility issues.
> > > >
> > > > thanks,
> > > >
> > > > -Vivek.
> > > >
> > > > > Vivek,
> > > > > --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > > > > > Hi All,
> > > > > >  What should be done in the following case:
> > > > > >
> > > > > >
> > > > > >       |IPSP_A                             |
> > > > > >   AS1 |      ---------------------- IPSP_C|
> > AS2
> > > > > >       |IPSP_B                             |
> > > > > >
> > > > > > IPSP_A and IPSP_B are in loadshare mode.
> > > > > >
> > > > > >   when AS1 has activated itself by sending
> > > > > > ASP Active from both the IPSPs (A & B) but
> > > > > > AS2 has sent ASP Active just to IPSP_A.
> > > > > >
> > > > > > What should IPSP_C do on receiving traffic
> > for AS1?
> > > > > >
> > > > > > a) Loadshare the traffic towards IPSP_A and
> > IPSP_B
> > > > > >
> > > > > > or
> > > > > >
> > > > > > b) It should send all the traffic to IPSP_A
> > and
> > > > > >    wait untill it sends ASP Active IPSP_B as
> > well.
> > > > > >    In the above case IPSP_B cannot send the
> > traffic
> > > > > >    towards IPSP_C but IPSP_C can.
> > > > > [TOLGA]It should send all traffic to IPSPS_A.
> > Which
> > > > > case do you refer as "the above case", a) or
> > b) ?
> > > > > >
> > > > > > thanks,
> > > > > > Vivek.
> > > > > >
> > > > >
> > > > >
> > > > > __________________________________
> > > > > Do you Yahoo!?
> > > > > Yahoo! SiteBuilder - Free, easy-to-use web
> > site design software
> > > > > http://sitebuilder.yahoo.com
> > > > >
> > > > >
> > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >
> > > > >
> > > >
> > > > --
> > > > Continuous Computing
> > > > http://www.ccpu.com
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > >
> > >
> >
> > --
> > Continuous Computing
> > http://www.ccpu.com
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> 
> _______________________________________________
> 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
> 
> 

-- 
Continuous Computing
http://www.ccpu.com

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



From exim@www1.ietf.org  Fri Aug  1 04:24:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02542
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 04:24:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iVCq-00078p-Be
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 04:24:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h718O860027452
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 04:24:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iVCj-000778-8D; Fri, 01 Aug 2003 04:24:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iVBy-00073h-36
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 04:23:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02499
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 04:23:10 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19iVBv-0003QC-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 04:23:11 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19iVBp-0003Px-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 04:23:05 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h718ILV09979;
	Fri, 1 Aug 2003 13:48:31 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h718LnC16208;
	Fri, 1 Aug 2003 13:52:09 +0530 (IST)
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
To: "Vivek Toky" <vivektoky@ccpu.com>
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF6E5CD569.BB0D027F-ON65256D75.002D07E5@hss.hns.com>
Date: Fri, 1 Aug 2003 13:46:20 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 01/08/2003
 01:45:21 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>





Vivek,

In your example also IPSP C will send data for AS1 to IPSP A only.I dont
see any reason for IPSP C to send data to IPSP B because ASPAC message is
not sent to IPSP B. I dont see any possibility of single direction traffic
flow in your example also.

Kamesh Kaul
www.hssworld.com
Hughes Software Systems




"Vivek Toky" <vivektoky@ccpu.com> on 08/01/2003 01:23:11 PM

To:    Kamesh Kaul/HSS@HSS, sigtran@ietf.org
cc:

Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour


Kamesh,

  Single direction traffic will still be possible. If you look at my
example carefully you will notice that in case of 3 IPSPs, it will be
possible. It may be for a short duration of time. In my example local
AS is already Active as it sent ASP Active message to one of the peer
IPSPs ( also got the ACK back )

please go through the example again .. waiting for comments ?

Vivek
>
>
>
>
> Hi Some comments below
>
>  When IPSP B receives ASPAC message from IPSP A for AS1 it marks
remote
> IPSP A active for remote AS1 and sends ASPAC ack back for AS1 to
IPSP A.Now
> with these message exchanges it means that IPSP A is ready to receive
> traffic for AS1.At this point of time IPSP B has not expressed its
> willingness to send data for any AS.IPSP B  cannot  send any
application
> data because its local applications are not active yet.So single
direction
> traffic flow will never occur.Now when IPSP B sends ASPAC message
for AS2
> to IPSP A and gets back ASPAC ack for AS2 it will give resume
indication to
> user now.AS1 and AS2 are basically same type of MTP3 users, and user
to
> user communication will only start if both users are ready and
active.
>
>
>     +-----------+              +-----------+
>     |           |              |           |
>     | IPSP A    |              | IPSP B    |
>     |           +--------------+           |
>     |           |              |           |
>     +-----------+              +-----------+
>
>         AS1                        AS2
>
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>
>
>
>
>
> "VIvek Toky" <vivektoky@ccpu.com>@ietf.org on 07/31/2003 11:19:39 PM
>
> Sent by:    sigtran-admin@ietf.org
>
>
> To:    "Tolga Asveren" <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
> cc:
>
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
> Tolga,
>
> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On
Behalf Of
> Tolga Asveren
> Sent: Thursday, July 31, 2003 10:19 AM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
> Vivek,
> --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > Please see my comments inline
> >
> > > See my opigion online
> > >
> > > > -----Original Message-----
> > > > From: Vivek Toky [mailto:vivektoky@ccpu.com]
> > > > Sent: Thursday, July 31, 2003 2:42 PM
> > > > To: Tolga Asveren; sigtran@ietf.org
> > > > Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> > > >
> > > >
> > > > Hi Tolga,
> > > >   "Above case" means
> > > > "when AS1 has activated itself by sending
> > > >  ASP Active from both the IPSPs (A & B) but
> > > >  AS2 has sent ASP Active just to IPSP_A."
> > > >
> > > > In my opinion IPSP_C should loadshare the
> > traffic
> > > > as it has received ASP active from both the
> > IPSPs
> > > > so AS1 is accessible through both of these.
> > > > However, it is the responsibility of AS1 to
> > route
> > > > all the traffic towards AS2 through IPSP_A.
> > >
> > > If IPSP_B receive some traffic from IPSP_C BUT no
> > AS is ACTIVE for
> > it on
> > > IPSP_C can it route this traffic???
> > > CAN a SG send to a ss7 network a message receive
> > from an INACTIVE
> > ASP !
> > > I don't think so!
> > > IPSP DE must be considered as two ASP/SG head to
> > tail.
> > >
> > [Vivek]
> > AS is ACTIVE on IPSP_B (remember it sent ASP Active
> > message)
> [TOLGA]State of an AS is in the context of an ASP/SGP
> pair. That ASP (IPSP_B) sends ACTIVE does not mean
> that AS is ACTIVE for the SGP, unless SGP sends
> ASPAC-ACK (IPSP_C in your example)
>
> You are right, state of AS is in context of ASP, this was
> what I wanted to say. I am assuming that SGP did send
> ACTIVE ack back and ASP( for that AS) is active through
> the SGP from which it got the ACK back. Is it fine now...
>
>
> > As far as the SGP - ASP example see the following..
> >
> > 1. It is the AS which is Active or Inactive not ASP
> > 2. ASPTM ptocedures are between SGPs and ASPs not SG
> > and ASPs
> >
> > The local AS on the ASP may be active through some
> > other
> > SGP (say SGPy)to which an ACTIVE message has been
> > sent.
> > So SGP (say SGPx) should route the traffic to SS7
> > coming from an
> > ASP which is inactive for an AS, because that AS is
> > Active through some other SGP and SS7 destination
> > may still
> > be able to send the traffic towards that AS through
> > some
> > other SGP
> >
> > In M3UA outgoing and Incoming Traffic flows are
> > independent,
> > so why restrict the traffic ?
> >
> > > >
> > > > In either case I think it is worth mentioning in
> >
> > > > Implementor's guide whether Unidirectional
> > traffic
> > > > is possible between associations(in case of
> > > > IPSP DE) or not.It will avoid any further
> > > > confusion or possible interoperatibility issues.
> > > >
> > > > thanks,
> > > >
> > > > -Vivek.
> > > >
> > > > > Vivek,
> > > > > --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > > > > > Hi All,
> > > > > >  What should be done in the following case:
> > > > > >
> > > > > >
> > > > > >       |IPSP_A                             |
> > > > > >   AS1 |      ---------------------- IPSP_C|
> > AS2
> > > > > >       |IPSP_B                             |
> > > > > >
> > > > > > IPSP_A and IPSP_B are in loadshare mode.
> > > > > >
> > > > > >   when AS1 has activated itself by sending
> > > > > > ASP Active from both the IPSPs (A & B) but
> > > > > > AS2 has sent ASP Active just to IPSP_A.
> > > > > >
> > > > > > What should IPSP_C do on receiving traffic
> > for AS1?
> > > > > >
> > > > > > a) Loadshare the traffic towards IPSP_A and
> > IPSP_B
> > > > > >
> > > > > > or
> > > > > >
> > > > > > b) It should send all the traffic to IPSP_A
> > and
> > > > > >    wait untill it sends ASP Active IPSP_B as
> > well.
> > > > > >    In the above case IPSP_B cannot send the
> > traffic
> > > > > >    towards IPSP_C but IPSP_C can.
> > > > > [TOLGA]It should send all traffic to IPSPS_A.
> > Which
> > > > > case do you refer as "the above case", a) or
> > b) ?
> > > > > >
> > > > > > thanks,
> > > > > > Vivek.
> > > > > >
> > > > >
> > > > >
> > > > > __________________________________
> > > > > Do you Yahoo!?
> > > > > Yahoo! SiteBuilder - Free, easy-to-use web
> > site design software
> > > > > http://sitebuilder.yahoo.com
> > > > >
> > > > >
> > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >
> > > > >
> > > >
> > > > --
> > > > Continuous Computing
> > > > http://www.ccpu.com
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > >
> > >
> >
> > --
> > Continuous Computing
> > http://www.ccpu.com
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
>
> _______________________________________________
> 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
>
>

--
Continuous Computing
 http://www.ccpu.com




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



From exim@www1.ietf.org  Fri Aug  1 08:54:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07834
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 08:54:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iZQ4-0007Ng-2e
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 08:54:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71Cs47B028351
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 08:54:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iZQ1-0007Mv-2w; Fri, 01 Aug 2003 08:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iZP5-0007MR-RR
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 08:53:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07827
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 08:52:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19iZP4-0004h2-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 08:53:02 -0400
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 19iZP3-0004gz-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 08:53:01 -0400
Received: from lurchi.franken.de (dialin-145-254-158-014.arcor-ip.net [145.254.158.14])
	by mail-n.franken.de (Postfix) with ESMTP id 28462245CA
	for <sigtran@ietf.org>; Fri,  1 Aug 2003 14:50:34 +0200 (CEST)
Date: Fri, 1 Aug 2003 14:52:22 +0200
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
To: sigtran@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <FE86BF34-C41E-11D7-9BBA-000A9591232C@lurchi.franken.de>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] Interop Test in September
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Dear all,

I would like to remind you that the deadline for registration
for the SIGTRAN Interop is August 11th. It will be held in
Nice at ETSI premises from September 1st to 5th.

You can register online and get more information at
http://www.etsi.org/plugtests/home.htm
(click at calendar of events).

I hope to see you there.

Best regards
Michael Tuexen


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



From exim@www1.ietf.org  Fri Aug  1 09:20:52 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14519
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 09:20:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iZeZ-0004R6-SJ
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 09:09:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71D93Ph017042
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 09:09:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iZeZ-0004Qk-OI
	for sigtran-web-archive@optimus.ietf.org; Fri, 01 Aug 2003 09:09:03 -0400
Date: Fri, 01 Aug 2003 09:09:03 -0400
Message-ID: <20030801130903.29120.84064.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: sigtran-web-archive@optimus.ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, sigtran-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for sigtran-web-archive@optimus.ietf.org:

List                                     Password // URL
----                                     --------  
sigtran@ietf.org                         emupuc    
https://www1.ietf.org/mailman/options/sigtran/sigtran-web-archive%40optimus.ietf.org



From exim@www1.ietf.org  Fri Aug  1 11:22:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26347
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 11:22:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ibjG-0007UQ-Vd
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 11:22:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71FM2v0028779
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 11:22:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ibjE-0007TX-N6; Fri, 01 Aug 2003 11:22:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ibj9-0007St-IB
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 11:21:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26321
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 11:21:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ibj8-0003KH-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 11:21:54 -0400
Received: from [66.180.118.20] (helo=sevis-main.SEVISNORTHDOM)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ibj8-0003Jw-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 11:21:54 -0400
Content-Class: urn:content-classes:message
Date: Fri, 1 Aug 2003 10:22:43 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <9B9A9DE704231348A20E8E2CA7696A9509B79D@sevis-main.SEVISNORTHDOM>
Thread-Topic: M2PA Last Call Comment
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Thread-Index: AcNXtRvdNx9kgyFGRnKvQHvUWzEwvAAi2hnQ
From: "Nitin Vairagare" <nitin.vairagare@sevis.com>
To: "Tom George" <Tom.George@alcatel.com>
Cc: "IETF sigtran" <sigtran@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: [Sigtran] RE: M2PA Last Call Comment
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Tom,

Do we have updated M2PA text available somewhere after the=20
Last call discussion?

Thanks,
Nitin

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



From exim@www1.ietf.org  Fri Aug  1 11:40:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26928
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 11:40:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ic0f-0008By-N9
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 11:40:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71Fe1kL031462
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 11:40:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ic0f-0008BL-7p; Fri, 01 Aug 2003 11:40:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ic0Q-0008An-Ch
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 11:39:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26921
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 11:39:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ic0P-0003Rn-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 11:39:45 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ic0O-0003Rf-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 11:39:44 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h71FdDwA003366;
	Fri, 1 Aug 2003 10:39:13 -0500 (CDT)
Message-ID: <3F2A89A1.4090004@alcatel.com>
Date: Fri, 01 Aug 2003 10:39:13 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] RE: M2PA Last Call Comment
References: <9B9A9DE704231348A20E8E2CA7696A9509B79D@sevis-main.SEVISNORTHDOM>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Nitin,

No, I do not have the text posted anywhere. I have been showing the 
corrected text with each comment. When I am done with the last comment, 
I will post it to the list.

tomG.

Nitin Vairagare wrote:
> Tom,
> 
> Do we have updated M2PA text available somewhere after the 
> Last call discussion?
> 
> Thanks,
> Nitin


-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
*   I actively disclaim speaking for Alcatel.  I do not purport to    *
*   advertise or represent its position, operations, or activities.   *


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



From exim@www1.ietf.org  Fri Aug  1 12:18:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28663
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 12:18:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19icbR-0001Rj-De
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 12:18:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71GI1M3005538
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 12:18:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19icbQ-0001R6-Pa; Fri, 01 Aug 2003 12:18:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19icb6-0001Pp-Ko
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 12:17:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28619
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 12:17:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19icb5-0003vX-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 12:17:39 -0400
Received: from web14508.mail.yahoo.com ([216.136.224.71])
	by ietf-mx with smtp (Exim 4.12)
	id 19icb4-0003vU-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 12:17:38 -0400
Message-ID: <20030801161732.74341.qmail@web14508.mail.yahoo.com>
Received: from [63.242.157.170] by web14508.mail.yahoo.com via HTTP; Fri, 01 Aug 2003 09:17:32 PDT
Date: Fri, 1 Aug 2003 09:17:32 -0700 (PDT)
From: Barry Nagelberg <bnagelberg@yahoo.com>
To: SIGTRAN mailing list <sigtran@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Sigtran] SUA v15: Address Mapping at the ASP
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Section 1.5.2 states that

"An ASP routes all responses to the SGP that it
received messages from; within the routing context
which it is currently active and receiving traffic. 
The ASP uses the routing context to select the SGP."

There is at least one syntax error here, making this
section difficult to understand. Could Kevin please
supply the correct text?

Barry Nagelberg

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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



From exim@www1.ietf.org  Fri Aug  1 14:37:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03624
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 14:37:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iem2-0006hD-3P
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 14:37:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71Ib6Oo025738
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 14:37:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iely-0006fn-4E; Fri, 01 Aug 2003 14:37:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ielt-0006fE-73
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 14:36:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03614
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 14:36:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ielq-00050m-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 14:36:54 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ielp-00050g-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 14:36:53 -0400
Received: from [172.16.1.203] (helo=CCPU00186)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19iell-00047g-6v; Fri, 01 Aug 2003 11:36:49 -0700
From: "Vivek Toky" <vivektoky@ccpu.com>
To: <kakaul@hss.hns.com>
Cc: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
Date: Fri, 1 Aug 2003 11:41:39 -0700
Message-ID: <HKEBKFBNPIDALDOKLGKDAELHCDAA.vivektoky@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <OF6E5CD569.BB0D027F-ON65256D75.002D07E5@hss.hns.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi Kamesh,
  Although ASPAC message has not been sent to IPSP B, but the local AS is
still active and is sending and receiving traffic through IPSP A. Now on the
other side IPSP A and IPSP B are part of the same AS ( AS1 ). So following
points should be noted.

1. Bi-directional traffic between AS1 and AS2 is possible
2. IPSP B has already sent ASPAC and received ASPAC Ack, so it is ready to
receive traffic.

 So why don't we loadshare the traffic among IPSP A and IPSP B as the
traffic is anyway going to get to the same destination i.e. AS1

In the reverse direction AS1 can choose IPSP A to send traffic towards AS2,
as only IPSP A has received ASPAC from IPSP C (for AS2)

comments?

-Vivek.

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
kakaul@hss.hns.com
Sent: Friday, August 01, 2003 1:16 AM
To: Vivek Toky
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour






Vivek,

In your example also IPSP C will send data for AS1 to IPSP A only.I dont
see any reason for IPSP C to send data to IPSP B because ASPAC message is
not sent to IPSP B. I dont see any possibility of single direction traffic
flow in your example also.

Kamesh Kaul
www.hssworld.com
Hughes Software Systems




"Vivek Toky" <vivektoky@ccpu.com> on 08/01/2003 01:23:11 PM

To:    Kamesh Kaul/HSS@HSS, sigtran@ietf.org
cc:

Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour


Kamesh,

  Single direction traffic will still be possible. If you look at my
example carefully you will notice that in case of 3 IPSPs, it will be
possible. It may be for a short duration of time. In my example local
AS is already Active as it sent ASP Active message to one of the peer
IPSPs ( also got the ACK back )

please go through the example again .. waiting for comments ?

Vivek
>
>
>
>
> Hi Some comments below
>
>  When IPSP B receives ASPAC message from IPSP A for AS1 it marks
remote
> IPSP A active for remote AS1 and sends ASPAC ack back for AS1 to
IPSP A.Now
> with these message exchanges it means that IPSP A is ready to receive
> traffic for AS1.At this point of time IPSP B has not expressed its
> willingness to send data for any AS.IPSP B  cannot  send any
application
> data because its local applications are not active yet.So single
direction
> traffic flow will never occur.Now when IPSP B sends ASPAC message
for AS2
> to IPSP A and gets back ASPAC ack for AS2 it will give resume
indication to
> user now.AS1 and AS2 are basically same type of MTP3 users, and user
to
> user communication will only start if both users are ready and
active.
>
>
>     +-----------+              +-----------+
>     |           |              |           |
>     | IPSP A    |              | IPSP B    |
>     |           +--------------+           |
>     |           |              |           |
>     +-----------+              +-----------+
>
>         AS1                        AS2
>
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>
>
>
>
>
> "VIvek Toky" <vivektoky@ccpu.com>@ietf.org on 07/31/2003 11:19:39 PM
>
> Sent by:    sigtran-admin@ietf.org
>
>
> To:    "Tolga Asveren" <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
> cc:
>
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
> Tolga,
>
> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On
Behalf Of
> Tolga Asveren
> Sent: Thursday, July 31, 2003 10:19 AM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
> Vivek,
> --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > Please see my comments inline
> >
> > > See my opigion online
> > >
> > > > -----Original Message-----
> > > > From: Vivek Toky [mailto:vivektoky@ccpu.com]
> > > > Sent: Thursday, July 31, 2003 2:42 PM
> > > > To: Tolga Asveren; sigtran@ietf.org
> > > > Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> > > >
> > > >
> > > > Hi Tolga,
> > > >   "Above case" means
> > > > "when AS1 has activated itself by sending
> > > >  ASP Active from both the IPSPs (A & B) but
> > > >  AS2 has sent ASP Active just to IPSP_A."
> > > >
> > > > In my opinion IPSP_C should loadshare the
> > traffic
> > > > as it has received ASP active from both the
> > IPSPs
> > > > so AS1 is accessible through both of these.
> > > > However, it is the responsibility of AS1 to
> > route
> > > > all the traffic towards AS2 through IPSP_A.
> > >
> > > If IPSP_B receive some traffic from IPSP_C BUT no
> > AS is ACTIVE for
> > it on
> > > IPSP_C can it route this traffic???
> > > CAN a SG send to a ss7 network a message receive
> > from an INACTIVE
> > ASP !
> > > I don't think so!
> > > IPSP DE must be considered as two ASP/SG head to
> > tail.
> > >
> > [Vivek]
> > AS is ACTIVE on IPSP_B (remember it sent ASP Active
> > message)
> [TOLGA]State of an AS is in the context of an ASP/SGP
> pair. That ASP (IPSP_B) sends ACTIVE does not mean
> that AS is ACTIVE for the SGP, unless SGP sends
> ASPAC-ACK (IPSP_C in your example)
>
> You are right, state of AS is in context of ASP, this was
> what I wanted to say. I am assuming that SGP did send
> ACTIVE ack back and ASP( for that AS) is active through
> the SGP from which it got the ACK back. Is it fine now...
>
>
> > As far as the SGP - ASP example see the following..
> >
> > 1. It is the AS which is Active or Inactive not ASP
> > 2. ASPTM ptocedures are between SGPs and ASPs not SG
> > and ASPs
> >
> > The local AS on the ASP may be active through some
> > other
> > SGP (say SGPy)to which an ACTIVE message has been
> > sent.
> > So SGP (say SGPx) should route the traffic to SS7
> > coming from an
> > ASP which is inactive for an AS, because that AS is
> > Active through some other SGP and SS7 destination
> > may still
> > be able to send the traffic towards that AS through
> > some
> > other SGP
> >
> > In M3UA outgoing and Incoming Traffic flows are
> > independent,
> > so why restrict the traffic ?
> >
> > > >
> > > > In either case I think it is worth mentioning in
> >
> > > > Implementor's guide whether Unidirectional
> > traffic
> > > > is possible between associations(in case of
> > > > IPSP DE) or not.It will avoid any further
> > > > confusion or possible interoperatibility issues.
> > > >
> > > > thanks,
> > > >
> > > > -Vivek.
> > > >
> > > > > Vivek,
> > > > > --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > > > > > Hi All,
> > > > > >  What should be done in the following case:
> > > > > >
> > > > > >
> > > > > >       |IPSP_A                             |
> > > > > >   AS1 |      ---------------------- IPSP_C|
> > AS2
> > > > > >       |IPSP_B                             |
> > > > > >
> > > > > > IPSP_A and IPSP_B are in loadshare mode.
> > > > > >
> > > > > >   when AS1 has activated itself by sending
> > > > > > ASP Active from both the IPSPs (A & B) but
> > > > > > AS2 has sent ASP Active just to IPSP_A.
> > > > > >
> > > > > > What should IPSP_C do on receiving traffic
> > for AS1?
> > > > > >
> > > > > > a) Loadshare the traffic towards IPSP_A and
> > IPSP_B
> > > > > >
> > > > > > or
> > > > > >
> > > > > > b) It should send all the traffic to IPSP_A
> > and
> > > > > >    wait untill it sends ASP Active IPSP_B as
> > well.
> > > > > >    In the above case IPSP_B cannot send the
> > traffic
> > > > > >    towards IPSP_C but IPSP_C can.
> > > > > [TOLGA]It should send all traffic to IPSPS_A.
> > Which
> > > > > case do you refer as "the above case", a) or
> > b) ?
> > > > > >
> > > > > > thanks,
> > > > > > Vivek.
> > > > > >
> > > > >
> > > > >
> > > > > __________________________________
> > > > > Do you Yahoo!?
> > > > > Yahoo! SiteBuilder - Free, easy-to-use web
> > site design software
> > > > > http://sitebuilder.yahoo.com
> > > > >
> > > > >
> > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >
> > > > >
> > > >
> > > > --
> > > > Continuous Computing
> > > > http://www.ccpu.com
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > >
> > >
> >
> > --
> > Continuous Computing
> > http://www.ccpu.com
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
>
> _______________________________________________
> 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
>
>

--
Continuous Computing
 http://www.ccpu.com




_______________________________________________
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



From exim@www1.ietf.org  Fri Aug  1 14:51:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04133
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 14:51:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iezW-0007XR-6k
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 14:51:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71Ip2f8028971
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 14:51:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iezV-0007X3-Gz; Fri, 01 Aug 2003 14:51:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iezI-0007WK-2s
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 14:50:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04043
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 14:50:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19iezF-00056U-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 14:50:45 -0400
Received: from web12810.mail.yahoo.com ([216.136.174.137])
	by ietf-mx with smtp (Exim 4.12)
	id 19iezD-00056R-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 14:50:44 -0400
Message-ID: <20030801185040.99801.qmail@web12810.mail.yahoo.com>
Received: from [208.255.120.2] by web12810.mail.yahoo.com via HTTP; Fri, 01 Aug 2003 11:50:40 PDT
Date: Fri, 1 Aug 2003 11:50:40 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
To: sigtran@ietf.org
In-Reply-To: <HKEBKFBNPIDALDOKLGKDAELHCDAA.vivektoky@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Vivek,

Last time I misunderstood your example, yes IMO you
are right, traffic should be loadshared between IPSP
A/B, because both of them have sent ASPAC and received
ASPAC-ACK from IPSP-C, showing that both of them are
ready to receive traffic for AS1 from IPSP-C.

   Tolga
--- Vivek Toky <vivektoky@ccpu.com> wrote:
> Hi Kamesh,
>   Although ASPAC message has not been sent to IPSP
> B, but the local AS is
> still active and is sending and receiving traffic
> through IPSP A. Now on the
> other side IPSP A and IPSP B are part of the same AS
> ( AS1 ). So following
> points should be noted.
> 
> 1. Bi-directional traffic between AS1 and AS2 is
> possible
> 2. IPSP B has already sent ASPAC and received ASPAC
> Ack, so it is ready to
> receive traffic.
> 
>  So why don't we loadshare the traffic among IPSP A
> and IPSP B as the
> traffic is anyway going to get to the same
> destination i.e. AS1
> 
> In the reverse direction AS1 can choose IPSP A to
> send traffic towards AS2,
> as only IPSP A has received ASPAC from IPSP C (for
> AS2)
> 
> comments?
> 
> -Vivek.
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> kakaul@hss.hns.com
> Sent: Friday, August 01, 2003 1:16 AM
> To: Vivek Toky
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> 
> 
> 
> 
> Vivek,
> 
> In your example also IPSP C will send data for AS1
> to IPSP A only.I dont
> see any reason for IPSP C to send data to IPSP B
> because ASPAC message is
> not sent to IPSP B. I dont see any possibility of
> single direction traffic
> flow in your example also.
> 
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
> 
> 
> 
> 
> "Vivek Toky" <vivektoky@ccpu.com> on 08/01/2003
> 01:23:11 PM
> 
> To:    Kamesh Kaul/HSS@HSS, sigtran@ietf.org
> cc:
> 
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> Kamesh,
> 
>   Single direction traffic will still be possible.
> If you look at my
> example carefully you will notice that in case of 3
> IPSPs, it will be
> possible. It may be for a short duration of time. In
> my example local
> AS is already Active as it sent ASP Active message
> to one of the peer
> IPSPs ( also got the ACK back )
> 
> please go through the example again .. waiting for
> comments ?
> 
> Vivek
> >
> >
> >
> >
> > Hi Some comments below
> >
> >  When IPSP B receives ASPAC message from IPSP A
> for AS1 it marks
> remote
> > IPSP A active for remote AS1 and sends ASPAC ack
> back for AS1 to
> IPSP A.Now
> > with these message exchanges it means that IPSP A
> is ready to receive
> > traffic for AS1.At this point of time IPSP B has
> not expressed its
> > willingness to send data for any AS.IPSP B  cannot
>  send any
> application
> > data because its local applications are not active
> yet.So single
> direction
> > traffic flow will never occur.Now when IPSP B
> sends ASPAC message
> for AS2
> > to IPSP A and gets back ASPAC ack for AS2 it will
> give resume
> indication to
> > user now.AS1 and AS2 are basically same type of
> MTP3 users, and user
> to
> > user communication will only start if both users
> are ready and
> active.
> >
> >
> >     +-----------+              +-----------+
> >     |           |              |           |
> >     | IPSP A    |              | IPSP B    |
> >     |           +--------------+           |
> >     |           |              |           |
> >     +-----------+              +-----------+
> >
> >         AS1                        AS2
> >
> > Kamesh Kaul
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> >


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

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



From exim@www1.ietf.org  Fri Aug  1 15:04:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04671
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:04:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifC6-00081g-CM
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:04:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71J42XU030842
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:04:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifC5-000815-KC; Fri, 01 Aug 2003 15:04:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifBX-00080N-DD
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:03:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04526
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 15:03:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ifBU-0005DD-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 15:03:24 -0400
Received: from web41804.mail.yahoo.com ([66.218.93.138])
	by ietf-mx with smtp (Exim 4.12)
	id 19ifBT-0005Cn-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 15:03:23 -0400
Message-ID: <20030801190251.21255.qmail@web41804.mail.yahoo.com>
Received: from [65.198.40.11] by web41804.mail.yahoo.com via HTTP; Fri, 01 Aug 2003 14:02:51 CDT
Date: Fri, 1 Aug 2003 14:02:51 -0500 (CDT)
From: =?iso-8859-1?q?Pablo=20Salinas?= <pablopesb@yahoo.com>
To: sigtran@ietf.org
Cc: kartik@comminventors.com, dreibh@exp-math.uni-essen.de,
        bidulock@openss7.org, rezhirpavai@hss.hns.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-552294386-1059764571=:19811"
Subject: [Sigtran] SDTI parameter in a link key registration request m2ua message
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--0-552294386-1059764571=:19811
Content-Type: text/plain; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA04527
Content-Transfer-Encoding: quoted-printable


Hi there,
         I've searched information about the SDTI parameter inside the re=
gistration request message. I've read the Clause 12 of the Q.704 Document=
. I also took a look at the Q.751-1 document. What I could understand fro=
m these documents is that the SDTI parameter in a Registration Request M2=
UA Message represents a piece of hardware able to manage various SS7 Link=
s.
So, my question for you people is the following:
Could the SDTI parameter represent a E1/T1 card inside a machine working =
as Signaling Gateway(figure 1)?

Or, it represents a machine that works in armony with other machines bein=
g each one of them a SDT(figure 2)?

-------------------------------------------------
|  Signaling Gateway                  |
|  (Phisical block)                       |
|                                               |
|      ----------------   ------------------    |
|     |                |   |                 |   |
|     |    SDT      |   | SDT         |   |
|     |                |   |                 |  |
|     | E1/T1 card|  |E1/T1 card  |  |
|     |---------------- |  |-----------------|  |
|             |                  |              |
|             |                  |              |
|             |                  |              |
|             |mux/demux |              |
|             |------------------|              |
|                      |                        |
|----------------------|-------------------------
    Link set       |
 ---------------------|

    figure 1

=20

-------------------------------------------------
|  Signaling Gateway                  |
|  (Logical block)                        |
|                                               |
|      ----------------   ------------------    |
|     | (Physical |   | (Physical   |   |
|     |  Block)    |   |  Block)      |   |

|     |    SDT      |   | SDT         |   |
|     |                |   |                 |  |
|     | E1/T1 card|  |E1/T1 card  |  |
|     |---------------- |  |-----------------|  |
|             |                  |              |
|             |                  |              |
|             |                  |              |
|             |mux/demux |              |
|             |------------------|              |
|                      |                        |
|----------------------|-------------------------
    Link set       |
 ---------------------|

    figure 2

If it is as figure 2 indicates, there should be another phisical block wo=
rking as managment device of the SDT's, rigth?

Another thing, I was thinking about, was the procedures the MTP3 Layer (t=
he M2UA Layer user within the MGC)  should do.
After it calls the M-LINK_KEY_REG Request, it should send a Signalling-da=
ta-link-connection-order message (MTP3 message) to the STP in the SS7 net=
work, rigth?

Please anyone help me out on this one. Thanks everybody,
                                                         Pablo S.


=20






---------------------------------
Do You Yahoo!?
Todo lo que quieres saber de Estados Unidos, Am=E9rica Latina y el resto =
del Mundo.
Vis=EDta Yahoo! Noticias.

--0-552294386-1059764571=:19811
Content-Type: text/html; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA04527
Content-Transfer-Encoding: quoted-printable

<P>Hi there,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I've sea=
rched information about the SDTI parameter inside the registration reques=
t message. I've read the Clause 12 of the Q.704 Document. I also took a l=
ook at the Q.751-1 document. What I could understand&nbsp;from these docu=
ments is that&nbsp;the SDTI parameter in a Registration Request M2UA Mess=
age represents a piece of hardware able to manage various SS7 Links.<BR>S=
o, my question for you people is the following:<BR>Could the SDTI paramet=
er represent a E1/T1 card inside a machine working as Signaling Gateway(f=
igure 1)?</P>
<P>Or, it represents a machine that works in armony with other machines b=
eing each one of them a SDT(figure 2)?</P>
<P>-------------------------------------------------<BR>|&nbsp;&nbsp;Sign=
aling Gateway&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; |<BR>|&nbsp;&nbsp;(Phisical block)=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; |<BR>|&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp; |<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
----------------&nbsp;&nbsp; ------------------&nbsp; &nbsp; |<BR>|&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|=
&nbsp;&nbsp; |<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|
 &nbsp;&nbsp; SDT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; | SDT&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<BR>|&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;=
|&nbsp;&nbsp;|<BR>|&nbsp;&nbsp;&nbsp;&nbsp; | E1/T1 card|&nbsp;&nbsp;|E1/=
T1 card&nbsp; |&nbsp; |<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|--------------=
-- |&nbsp; |-----------------|&nbsp; |<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nnbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
 &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;|<BR>|&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nb=
sp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &=
nbsp;&nbsp;|<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&=
nbsp;&nbsp; |mux/demux |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|------------------|&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|<BR>|=
&nbsp;&nbsp;&nbsp;&nbssp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;|<BR>=
|----------------------|-------------------------<BR>&nbsp;&nbsp;&nbsp; L=
ink set&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&nbspp;-----------------=
----|</P>
<P>&nbsp;&nbsp;&nbsp;&nbsp;figure 1</P>
<P>&nbsp;</P>
<P>-------------------------------------------------<BR>|&nbsp;&nbsp;Sign=
aling Gateway&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; |<BR>|&nbsp;&nbsp;(Logical block)&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; |<BR>|&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp; |<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
----------------&nbsp;&nbsp; ------------------&nbsp; &nbsp; |<BR>|&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;| (Physical&nbsp;|&nbsp;&nbsp; | (Physical&nbsp;&=
nbsp;&nbsp;|&nbsp;&nbsp; |<BR>|&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Block)&nb=
sp;&nbsp;&nbsp; |&nbsp;&nbsp; |&nbsp; Block)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; |&nbsp;&nbsp;&nbsp;|</P>
<P>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp; SDT&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |&nbsp;&nbsp; | SDT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; |&nbsp;&nbsp; |<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nb=
sp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|&nbsp;&nbsp;|<BR>|&nbsp;&nbsp;&nbsp;&=
nbsp; | E1/T1 card|&nbsp;&nbsp;|E1/T1 card&nbsp; |&nbsp; |<BR>|&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;|---------------- |&nbsp; |-----------------|&nbsp; |=
<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &=
nnbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<BR>|&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;|<BR>|&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nb=
sp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &=
nbsp;&nbsp;|<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&=
nbsp;&nbsp; |mux/demux |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|------------------|&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|<BR>|=
&nbsp;&nbsp;&nbsp;&nbssp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;|<BR>=
|----------------------|-------------------------<BR>&nbsp;&nbsp;&nbsp; L=
ink set&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&nbspp;-----------------=
----|</P>
<P>&nbsp;&nbsp;&nbsp;&nbsp;figure 2</P>
<P>If it is as figure 2 indicates, there should be another phisical block=
 working as managment device of the SDT's, rigth?</P>
<P>Another thing, I was thinking about, was&nbsp;the procedures the MTP3 =
Layer (the M2UA Layer user within the MGC)&nbsp; should do.<BR>After it c=
alls the M-LINK_KEY_REG Request, it should send a Signalling-data-link-co=
nnection-order message (MTP3 message) to the STP in the SS7 network, rigt=
h?</P>
<P>Please anyone help me out on this one. Thanks everybody,<BR>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pablo S.</P>
<P><BR>&nbsp;</P>
<DIV></DIV><BR><BR><p><br><hr size=3D1 noshade><b>Do You Yahoo!?</b><br>
<a href=3Dhttp://espanol.yahoo.com/mail_tagline/*http://espanol.news.yaho=
o.com><img src=3D"http://us.i1.yimg.com/us.yimg.com/i/not/dailynews.gif" =
width=3D30 height=3D26 border=3D0 align=3Dleft></a>
Todo lo que quieres saber de Estados Unidos, Am=E9rica Latina y el resto =
del Mundo.<br>
Vis=EDta <a href=3Dhttp://espanol.yahoo.com/mail_tagline/*http://espanol.=
news.yahoo.com>Yahoo! Noticias</a>.<br>
--0-552294386-1059764571=:19811--

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



From exim@www1.ietf.org  Fri Aug  1 15:28:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06743
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:28:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZK-0000dF-Dw
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:28:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JS24H002405
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:28:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZK-0000cd-5q; Fri, 01 Aug 2003 15:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZF-0000c0-7T
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:27:57 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06578;
	Fri, 1 Aug 2003 15:27:53 -0400 (EDT)
Message-Id: <200308011927.PAA06578@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 01 Aug 2003 15:27:53 -0400
Subject: [Sigtran] I-D ACTION:draft-bidulock-sigtran-corid-02.txt,.ps,.pdf
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Correlation Id and Hearbeat Procedures (CORID)
                          Supporting Lossless Fail-Over between SCTP 
                          Associations
                          for Signalling User Adaptation Layers
	Author(s)	: B. Bidulock
	Filename	: draft-bidulock-sigtran-corid-02.txt,.ps,.pdf
	Pages		: 50
	Date		: 2003-8-1
	
This Internet-Draft describes Correlation Id and Heartbeat
procedures to support lossless fail-over between SCTP [RFC 2960]
associations for SS7 [Q.700] Signalling User Adaptation Protocols
[M2UA..ISUA, TUA] supporting the concept of a Routing Context or
Interface Identifier.  These procedures permit lossless fail-over
between Application Server Processes (ASPs) at a Signalling Gateway
(SG) and fail-over between Signalling Gateway Processes (SGPs) and
Signalling Gateways (SGs) at an Application Server Process (ASP).
Lossless fail-over permits these fail-overs to occur without loss or
duplication of UA-User messages.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-corid-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bidulock-sigtran-corid-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-bidulock-sigtran-corid-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-1153545.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-bidulock-sigtran-corid-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-bidulock-sigtran-corid-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-1153545.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Aug  1 15:29:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06947
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:29:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaH-0000sk-1i
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:29:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JT15B003374
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:29:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaG-0000sK-SX; Fri, 01 Aug 2003 15:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZN-0000e8-Mv
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:28:05 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06613;
	Fri, 1 Aug 2003 15:28:01 -0400 (EDT)
Message-Id: <200308011928.PAA06613@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 01 Aug 2003 15:28:01 -0400
Subject: [Sigtran] I-D ACTION:draft-bidulock-sigtran-loadsel-02.txt,.ps,.pdf
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Load Selection for Signalling User Adaptation Layers
	Author(s)	: B. Bidulock
	Filename	: draft-bidulock-sigtran-loadsel-02.txt,.ps,.pdf
	Pages		: 44
	Date		: 2003-8-1
	
This Internet-Draft describes Load Selection (LOADSEL) for
Signalling User Adaptation Protocols [IUA..SUA, IUA-BIS..TUA], which
permits an Application Server Processes (ASP) to indicate its
placement within an Application Server and permits an Signalling
Gateway (SG) to distribute traffic over ASPs in Application Servers
under Application Server Process (ASP) control.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-loadsel-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bidulock-sigtran-loadsel-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-bidulock-sigtran-loadsel-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-1153605.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-bidulock-sigtran-loadsel-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-bidulock-sigtran-loadsel-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-1153605.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Aug  1 15:29:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06960
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:29:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaI-0000xn-AN
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:29:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JT2HE003699
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:29:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaI-0000xY-62; Fri, 01 Aug 2003 15:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZJ-0000cN-Ck
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:28:01 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06594;
	Fri, 1 Aug 2003 15:27:57 -0400 (EDT)
Message-Id: <200308011927.PAA06594@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 01 Aug 2003 15:27:57 -0400
Subject: [Sigtran] I-D ACTION:draft-bidulock-sigtran-loadgrp-02.txt,.ps,.pdf
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Load Grouping Extension for Signalling User Adaptation
                          Layers
	Author(s)	: B. Bidulock
	Filename	: draft-bidulock-sigtran-loadgrp-02.txt,.ps,.pdf
	Pages		: 12
	Date		: 2003-8-1
	
This Internet-Draft describes an extension parameter and procedure
to the Signalling User Adaptation Protocols [IUA..TUA, IUA-
BIS..GR303UA00], based on the Stream Transmission Control Protocol
(SCTP) [RFC 2960] which permits an Application Server Processes (ASP)
to indicate its placement within a Load Group and permits an
Signalling Gateway (SG) to distribute traffic over Load Groups under
Application Server Process (ASP) control.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-loadgrp-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bidulock-sigtran-loadgrp-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-bidulock-sigtran-loadgrp-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-1153555.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-bidulock-sigtran-loadgrp-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-bidulock-sigtran-loadgrp-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-1153555.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Aug  1 15:29:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06985
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:29:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaI-0000zo-Uo
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:29:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JT23Y003823
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:29:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaI-0000zY-QI; Fri, 01 Aug 2003 15:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZW-0000hY-Gf
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:28:14 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06668;
	Fri, 1 Aug 2003 15:28:11 -0400 (EDT)
Message-Id: <200308011928.PAA06668@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 01 Aug 2003 15:28:10 -0400
Subject: [Sigtran] I-D ACTION:draft-bidulock-sigtran-sginfo-03.txt,.ps,.pdf
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Signalling Gateway (SG) Information (SGINFO) Support
                          for Signalling User Adaptation Layers
	Author(s)	: B. Bidulock
	Filename	: draft-bidulock-sigtran-sginfo-03.txt,.ps,.pdf
	Pages		: 22
	Date		: 2003-8-1
	
This Internet-Draft describes Signalling Gateway (SG) Information
(SGINFO) for Signalling User Adaptation Protocols [M2UA...TUA], which
permits supporting Signalling Gateways (SG) to convey additional
Application Server (AS) support information to Application Server
Processes (ASPs) activating for AS on the SG.  This additional AS
support information consists of information pertaining to the
underlying SS7 Signalling Provider that otherwise would have to be
statically configured at the Application Server Process (ASP) or
exchanged between SG and ASP using a non-IETF defined protocol.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-sginfo-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bidulock-sigtran-sginfo-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-bidulock-sigtran-sginfo-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-1153627.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-bidulock-sigtran-sginfo-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-bidulock-sigtran-sginfo-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-1153627.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Aug  1 15:29:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06996
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:29:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaJ-00011q-K9
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:29:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JT3l0003945
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:29:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaJ-00011W-Ed; Fri, 01 Aug 2003 15:29:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZb-0000hd-4f
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:28:19 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06684;
	Fri, 1 Aug 2003 15:28:15 -0400 (EDT)
Message-Id: <200308011928.PAA06684@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 01 Aug 2003 15:28:15 -0400
Subject: [Sigtran] I-D ACTION:draft-bidulock-sigtran-isua-01.txt,.ps,.pdf
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: SS7 ISUP-User Adaptation Layer (ISUA)
	Author(s)	: B. Bidulock
	Filename	: draft-bidulock-sigtran-isua-01.txt,.ps,.pdf
	Pages		: 134
	Date		: 2003-8-1
	
This document defines a protocol for the transport of any SS7 ISUP-
User signalling (e.g, Call Control) over IP using the Stream Control
Transport Protocol [RFC 2960].  The protocol should be modular and
symmetric, to allow it to work in diverse architectures, such as a
Signalling Gateway and IP Signalling End-point architecture.  Protocol
elements are added to allow seamless operation between peers in the
SS7 and IP domains.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-isua-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bidulock-sigtran-isua-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-bidulock-sigtran-isua-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-1153636.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-bidulock-sigtran-isua-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-bidulock-sigtran-isua-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-1153636.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Aug  1 15:29:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07016
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:29:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaK-00013c-9I
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:29:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JT4ua004061
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:29:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaK-00013N-3i; Fri, 01 Aug 2003 15:29:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZf-0000iR-M7
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:28:23 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06701;
	Fri, 1 Aug 2003 15:28:20 -0400 (EDT)
Message-Id: <200308011928.PAA06701@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 01 Aug 2003 15:28:20 -0400
Subject: [Sigtran] I-D ACTION:draft-bidulock-sigtran-m2ua-ss7test-00.txt,.ps,.pdf
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: SS7 MTP2-User Adaptation Layer (M2UA)SS7 Test 
                          Specifications M2UA-SS7TEST
	Author(s)	: B. Bidulock
	Filename	: draft-bidulock-sigtran-m2ua-ss7test-00.txt,.ps,.pdf
	Pages		: 21
	Date		: 2003-8-1
	
This Internet-Draft provides information for the Internet community
on the implementation of test cases for testing the SS7 MTP2-User
Adaptation Layer [M2UA] Signalling Gateway (SG) based on the
conformance test specifications for SS7 MTP Level 2
[Q.780..M2PATEST04].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-m2ua-ss7test-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bidulock-sigtran-m2ua-ss7test-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-bidulock-sigtran-m2ua-ss7test-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-1153646.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-bidulock-sigtran-m2ua-ss7test-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-bidulock-sigtran-m2ua-ss7test-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-1153646.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Aug  1 15:29:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07038
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:29:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaL-00015j-3n
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:29:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JT5r8004193
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:29:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaK-00015X-Sh; Fri, 01 Aug 2003 15:29:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZk-0000nR-50
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:28:28 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06717;
	Fri, 1 Aug 2003 15:28:24 -0400 (EDT)
Message-Id: <200308011928.PAA06717@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 01 Aug 2003 15:28:24 -0400
Subject: [Sigtran] I-D ACTION:draft-bidulock-sigtran-m2pa-test-03.txt,.ps,.pdf
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: SS7 MTP2-User Peer-to-Peer Adaptation Layer Test 
                          Specifications M2PA-TEST
	Author(s)	: B. Bidulock
	Filename	: draft-bidulock-sigtran-m2pa-test-03.txt,.ps,.pdf
	Pages		: 136
	Date		: 2003-8-1
	
This Internet Draft provides information for the Internet community
on test cases for testing the SS7 M2P2-User Peer-to-Peer Adaptation
Layer [M2PA06] based on the conformance test specifications for SS7
MTP Level 2 [Q.781].
This memo describes the test environment and a detailed description
of test cases for validation, compatibility and interoperability
testing of the M2PA protocol implemented on the foundation of ITU SS7
MTP Signalling Links [Q.703].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-m2pa-test-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bidulock-sigtran-m2pa-test-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-bidulock-sigtran-m2pa-test-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-1153655.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-bidulock-sigtran-m2pa-test-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-bidulock-sigtran-m2pa-test-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-1153655.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Aug  1 15:29:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07052
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:29:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaL-00017f-ML
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:29:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JT5Eo004308
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:29:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaL-00017O-Hj; Fri, 01 Aug 2003 15:29:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZo-0000nX-5R
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:28:32 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06733;
	Fri, 1 Aug 2003 15:28:28 -0400 (EDT)
Message-Id: <200308011928.PAA06733@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 01 Aug 2003 15:28:28 -0400
Subject: [Sigtran] I-D ACTION:draft-bidulock-sigtran-tua-02.txt,.ps,.pdf
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: SS7 TCAP-User Adaptation Layer TUA
	Author(s)	: B. Bidulock
	Filename	: draft-bidulock-sigtran-tua-02.txt,.ps,.pdf
	Pages		: 152
	Date		: 2003-8-1
	
This document defines a protocol for the transport of any SS7 TCAP-
User signalling (e.g, INAP, MAP, etc.) over IP using the Stream
Control Transport Protocol [RFC 2960].  The protocol should be modular
and symmetric, to allow it to work in diverse architectures, such as a
Signalling Gateway and IP Signalling End-point architecture.  Protocol
elements are added to allow seamless operation between peers in the
SS7 and IP domains.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-tua-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bidulock-sigtran-tua-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-bidulock-sigtran-tua-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-1153706.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-bidulock-sigtran-tua-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-bidulock-sigtran-tua-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-1153706.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Aug  1 16:16:03 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06745
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:28:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZK-0000dG-ED
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:28:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JS24H002406
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:28:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZJ-0000cV-Nv; Fri, 01 Aug 2003 15:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZB-0000bu-8q
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:27:53 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06562;
	Fri, 1 Aug 2003 15:27:49 -0400 (EDT)
Message-Id: <200308011927.PAA06562@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 01 Aug 2003 15:27:49 -0400
Subject: [Sigtran] I-D ACTION:draft-bidulock-sigtran-aspext-02.txt,.ps,.pdf
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Application Server Process (ASP) Extension (ASPEXT) 
                          Framework for Signalling User Adaptation Layers
	Author(s)	: B. Bidulock
	Filename	: draft-bidulock-sigtran-aspext-02.txt,.ps,.pdf
	Pages		: 21
	Date		: 2003-8-1
	
This Internet-Draft describes ASP Extensions (ASPEXT) for
Signalling User Adaptation Protocols [IUA..SUA, IUA-BIS..TUA], which
permits cooperating Signalling Peer Processes (SPPs) to indicate to
each other the specific protocol extensions that each supports.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-aspext-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bidulock-sigtran-aspext-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-bidulock-sigtran-aspext-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-1153534.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-bidulock-sigtran-aspext-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-bidulock-sigtran-aspext-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-1153534.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Aug  1 16:16:03 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06948
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:29:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaH-0000vn-Q9
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 15:29:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JT1LV003577
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 15:29:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifaH-0000va-Kd; Fri, 01 Aug 2003 15:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ifZR-0000f0-SN
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 15:28:09 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06652;
	Fri, 1 Aug 2003 15:28:06 -0400 (EDT)
Message-Id: <200308011928.PAA06652@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 01 Aug 2003 15:28:06 -0400
Subject: [Sigtran] I-D ACTION:draft-bidulock-sigtran-regext-01.txt,.pdf
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Registration Extensions (REGEXT)for Signalling User 
                          Adaptation Layers
	Author(s)	: B. Bidulock
	Filename	: draft-bidulock-sigtran-regext-01.txt,.pdf
	Pages		: 28
	Date		: 2003-8-1
	
This memo describes Registration Extensions (REGEXT) that provides
the ability for an Application Server Process (ASP) to modify existing
Routing (Link) Keys with a Signalling Gateway (SG).
Current procedures in the SS7 Signalling User Adaptation Layers
(UAs) [M2UA..TUA] do not provide for the modification of Routing
(Link) Keys without deactivation of the Application Server (AS).  This
causes problems in making changes to live systems.
The extensions described in this memo permit modification of
Signalling Link membership in Application Servers for SS7 MTP2-User
Adaptation Layer [M2UA], modification of Circuit Identification Code
(CIC) ranges for the SS7 MTP3-User Adaptation Layer [M3UA],
modification of Circuit Identification Code (CIC) rnages for the SS7
ISUP-User Adaptation Layer [ISUA], modificiation of Destination Local
Reference (DLR) ranges for SS7 SCCP-User Adaptation Layer [SUA], and
modification of Transaction Identifier (TID) ranges for SS7 TCAP-User
Adaptation Layer [TUA].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-regext-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bidulock-sigtran-regext-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-bidulock-sigtran-regext-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-1153615.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-bidulock-sigtran-regext-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-bidulock-sigtran-regext-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-1153615.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Fri Aug  1 16:47:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11732
	for <sigtran-archive@odin.ietf.org>; Fri, 1 Aug 2003 16:47:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ignn-0005vH-Nm
	for sigtran-archive@odin.ietf.org; Fri, 01 Aug 2003 16:47:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71Kl39P022761
	for sigtran-archive@odin.ietf.org; Fri, 1 Aug 2003 16:47:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ignl-0005ut-Sc; Fri, 01 Aug 2003 16:47:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19igmv-0005uC-4B
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 16:46:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11716
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 16:46:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19igmt-0006kv-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 16:46:07 -0400
Received: from ottgw.pt.com ([206.191.2.130] helo=pt.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19igms-0006kZ-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 16:46:06 -0400
Received: from pt.com (IDENT:root@localhost [127.0.0.1])
	by  pt.com (8.9.3/8.9.3) with ESMTP id QAA11061;
	Fri, 1 Aug 2003 16:45:15 -0400
Message-ID: <3F2AD15F.90305@pt.com>
Date: Fri, 01 Aug 2003 16:45:19 -0400
From: Andrew Booth <abooth@pt.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Tom George <Tom.George@alcatel.com>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Use of BSN.  Was: Re: [Sigtran] M2PA Last Call Comment - T6
References: <829F074A10F98943A218DC363D09C92A25022F@w2ksjexg06.oni.com> <20030712002921.A21136@openss7.org> <3F26EEFA.7040203@alcatel.com> <20030729160553.A5718@openss7.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi Tom, Brian,

I agree that the BSN in LS messages could be used for various purposes, 
but I wonder if we need some more text should go with it. I also have a 
question about the description of BSN in 2.2.1.

2.2.1 Backward Sequence Number (BSN)
This is the FSN of the message last received from the peer.

For data messages this sounds inaccurate, should it not be the FSN that 
is being acknowledged? These numbers could be different in some cases, 
say if messages are queued in a receive buffer waiting for M2PA to 
process them.

For LS PR I think we agreed that the BSN should be set to the last FSN 
received from the peer, in which case it should not be considered to 
acknowledge data (some queued data might not have been passed to MTP3 yet).

If the BSN in LS Busy Ended is used to ack data then should this be 
clarified in 2.2.1?

If the BSN from LS messages may be used to ack data, should we include 
some text on how to recognize unreasonable BSNs?

Andrew

Brian F. G. Bidulock wrote:

>Tom,
>
>Right.  That was my thinking too.
>
>--brian
>
>Tom George wrote:                                                                      (Tue, 29 Jul 2003 17:02:34)
>  
>
>>Brian,
>>
>>The old text about ignoring the BSN in the LS messages has been taken 
>>out in version 9. We explicitly mention that the BSN in the LS PO 
>>message can be used, but there is no reason to restrict the use of the 
>>BSN in other LS messages.
>>
>>Right?
>>
>>tomG.
>>
>>Brian F. G. Bidulock wrote:
>>   [...]
>>    
>>
>>>Now, I know that we said that Link Status messages are not used to acknowledge
>>>DATA messages, but it makes sense to permit the Link Status Busy Ended message
>>>to acknowledge outstanding User Data messages, so that upon its receipt, T7
>>>might not need to be started if all messages in the retransmission buffer are
>>>acknolwedged by the Link Status Busy Ended message.
>>>
>>>The above also kind of changes the idea of T7 metering the oldest message in
>>>the retransmission buffer.  It would now measure the oldest message in the
>>>retransmission buffer since the receipt of the last Link Status Busy Ended.
>>>      
>>>
>>   [...]
>>
>>-- 
>>* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
>>* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
>>* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
>>*   I actively disclaim speaking for Alcatel.  I do not purport to    *
>>*   advertise or represent its position, operations, or activities.   *
>>
>>
>>_______________________________________________
>>Sigtran mailing list
>>Sigtran@ietf.org
>>https://www1.ietf.org/mailman/listinfo/sigtran
>>    
>>
>
>  
>

-- 
Andrew Booth, Software Developer
Signaling Systems Group, Performance Technologies
613-237-4344

Visit www.pt.com/mailing.html to subscribe to our Packets & Signals eLetter.



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



From exim@www1.ietf.org  Sat Aug  2 23:25:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27438
	for <sigtran-archive@odin.ietf.org>; Sat, 2 Aug 2003 23:25:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19j9UW-0000BR-2D
	for sigtran-archive@odin.ietf.org; Sat, 02 Aug 2003 23:25:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h733P4Sx000701
	for sigtran-archive@odin.ietf.org; Sat, 2 Aug 2003 23:25:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19j9UT-0000B4-OK; Sat, 02 Aug 2003 23:25:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19j9Tm-00006f-Lv
	for sigtran@optimus.ietf.org; Sat, 02 Aug 2003 23:24:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27429
	for <sigtran@ietf.org>; Sat, 2 Aug 2003 23:24:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19j9Tk-00066T-00
	for sigtran@ietf.org; Sat, 02 Aug 2003 23:24:16 -0400
Received: from web60004.mail.yahoo.com ([216.109.116.227])
	by ietf-mx with smtp (Exim 4.12)
	id 19j9Tk-00066N-00
	for sigtran@ietf.org; Sat, 02 Aug 2003 23:24:16 -0400
Message-ID: <20030803032346.56020.qmail@web60004.mail.yahoo.com>
Received: from [203.94.199.45] by web60004.mail.yahoo.com via HTTP; Sat, 02 Aug 2003 20:23:46 PDT
Date: Sat, 2 Aug 2003 20:23:46 -0700 (PDT)
From: kamesh kaul <kkk_kaul@yahoo.com>
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
To: Vivek Toky <vivektoky@ccpu.com>
Cc: sigtran@ietf.org
In-Reply-To: <HKEBKFBNPIDALDOKLGKDAELHCDAA.vivektoky@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Hi Vivek,
    I argee with you that if we intermix IPSP SE and
DE models we can start loadsharing traffic for AS2
among IPSP B and IPSP A even though IPSP B has not
received ASPAC message from IPSP c.It would result in
intermixing of two IPSP models.For some messages IPSP
C has to behave in DE manner and for other SE
behaviour is required.Lets take your example. On
receiving ASPAC messages from IPSP A and IPSP B for
AS1 IPSP C updates only remote IPSP'S states for AS1
behaving in DE manner.when IPSP c sends ASPAC for AS2
to IPSP A and receives ACK back then also IPSP C
changes its state to active for local AS2 behaving in
DE manner.Now as you said Bi-directional data is
flowing from IPSP C and IPSP A where as single
direction traffic is possible from IPSP C to IPSP B
(for AS2).Now assume IPSP A sends ASPIA message for
AS1 to IPSP C in this case IPSP c on receiving ASPIA
message has to update state of remote IPSP A in AS1
and also state of local IPSP C in local AS2 behaving
in SE manner.If IPSP C does not bother about local
state updation on receiving ASPIA from IPSP A, IPSP C
will continue to send data messages for AS2 to IPSP B
without receiving anything from other side. This will
result in single direction traffic from IPSP C to AS1
without the knowledge of IPSP C.If we associate AS
state with local and peer IPSP's (in your example
AS2's state with IPSP c and each peer IPSPA and IPSPB,
AS2's state with IPSP C and each peer IPSP's) single
direction traffic flow is not possible. Please comment

Regards
Kamesh        
--- Vivek Toky <vivektoky@ccpu.com> wrote:
> Hi Kamesh,
>   Although ASPAC message has not been sent to IPSP
> B, but the local AS is
> still active and is sending and receiving traffic
> through IPSP A. Now on the
> other side IPSP A and IPSP B are part of the same AS
> ( AS1 ). So following
> points should be noted.
> 
> 1. Bi-directional traffic between AS1 and AS2 is
> possible
> 2. IPSP B has already sent ASPAC and received ASPAC
> Ack, so it is ready to
> receive traffic.
> 
>  So why don't we loadshare the traffic among IPSP A
> and IPSP B as the
> traffic is anyway going to get to the same
> destination i.e. AS1
> 
> In the reverse direction AS1 can choose IPSP A to
> send traffic towards AS2,
> as only IPSP A has received ASPAC from IPSP C (for
> AS2)
> 
> comments?
> 
> -Vivek.
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> kakaul@hss.hns.com
> Sent: Friday, August 01, 2003 1:16 AM
> To: Vivek Toky
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> 
> 
> 
> 
> Vivek,
> 
> In your example also IPSP C will send data for AS1
> to IPSP A only.I dont
> see any reason for IPSP C to send data to IPSP B
> because ASPAC message is
> not sent to IPSP B. I dont see any possibility of
> single direction traffic
> flow in your example also.
> 
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
> 
> 
> 
> 
> "Vivek Toky" <vivektoky@ccpu.com> on 08/01/2003
> 01:23:11 PM
> 
> To:    Kamesh Kaul/HSS@HSS, sigtran@ietf.org
> cc:
> 
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> Kamesh,
> 
>   Single direction traffic will still be possible.
> If you look at my
> example carefully you will notice that in case of 3
> IPSPs, it will be
> possible. It may be for a short duration of time. In
> my example local
> AS is already Active as it sent ASP Active message
> to one of the peer
> IPSPs ( also got the ACK back )
> 
> please go through the example again .. waiting for
> comments ?
> 
> Vivek
> >
> >
> >
> >
> > Hi Some comments below
> >
> >  When IPSP B receives ASPAC message from IPSP A
> for AS1 it marks
> remote
> > IPSP A active for remote AS1 and sends ASPAC ack
> back for AS1 to
> IPSP A.Now
> > with these message exchanges it means that IPSP A
> is ready to receive
> > traffic for AS1.At this point of time IPSP B has
> not expressed its
> > willingness to send data for any AS.IPSP B  cannot
>  send any
> application
> > data because its local applications are not active
> yet.So single
> direction
> > traffic flow will never occur.Now when IPSP B
> sends ASPAC message
> for AS2
> > to IPSP A and gets back ASPAC ack for AS2 it will
> give resume
> indication to
> > user now.AS1 and AS2 are basically same type of
> MTP3 users, and user
> to
> > user communication will only start if both users
> are ready and
> active.
> >
> >
> >     +-----------+              +-----------+
> >     |           |              |           |
> >     | IPSP A    |              | IPSP B    |
> >     |           +--------------+           |
> >     |           |              |           |
> >     +-----------+              +-----------+
> >
> >         AS1                        AS2
> >
> > Kamesh Kaul
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> >
> >
> >
> > "VIvek Toky" <vivektoky@ccpu.com>@ietf.org on
> 07/31/2003 11:19:39 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    "Tolga Asveren" <tolga_asveren@yahoo.com>,
> <sigtran@ietf.org>
> > cc:
> >
> > Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> >
> >
> > Tolga,
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On
> Behalf Of
> > Tolga Asveren
> > Sent: Thursday, July 31, 2003 10:19 AM
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> >
> >
> > Vivek,
> > --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > > Please see my comments inline
> > >
> > > > See my opigion online
> > > >
> > > > > -----Original Message-----
> > > > > From: Vivek Toky [mailto:vivektoky@ccpu.com]
> > > > > Sent: Thursday, July 31, 2003 2:42 PM
> > > > > To: Tolga Asveren; sigtran@ietf.org
> > > > > Subject: RE: [Sigtran] M3UA : IPSP DE
> behaviour
> > > > >
> > > > >
> > > > > Hi Tolga,
> > > > >   "Above case" means
> > > > > "when AS1 has activated itself by sending
> > > > >  ASP Active from both the IPSPs (A & B) but
> > > > >  AS2 has sent ASP Active just to IPSP_A."
> > > > >
> > > > > In my opinion IPSP_C should loadshare the
> > > traffic
> > > > > as it has received ASP active from both the
> > > IPSPs
> > > > > so AS1 is accessible through both of these.
> > > > > However, it is the responsibility of AS1 to
> > > route
> > > > > all the traffic towards AS2 through IPSP_A.
> > > >
> > > > If IPSP_B receive some traffic from IPSP_C BUT
> no
> > > AS is ACTIVE for
> > > it on
> > > > IPSP_C can it route this traffic???
> > > > CAN a SG send to a ss7 network a message
> receive
> > > from an INACTIVE
> > > ASP !
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

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



From exim@www1.ietf.org  Mon Aug  4 02:03:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA08895
	for <sigtran-archive@odin.ietf.org>; Mon, 4 Aug 2003 02:03:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jYQz-0000fg-P6
	for sigtran-archive@odin.ietf.org; Mon, 04 Aug 2003 02:03:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h746359o002557
	for sigtran-archive@odin.ietf.org; Mon, 4 Aug 2003 02:03:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jYQu-0000es-T3; Mon, 04 Aug 2003 02:03:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jYQk-0000eJ-2y
	for sigtran@optimus.ietf.org; Mon, 04 Aug 2003 02:02:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA08072
	for <sigtran@ietf.org>; Mon, 4 Aug 2003 02:02:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19jYQg-0006LW-00
	for sigtran@ietf.org; Mon, 04 Aug 2003 02:02:46 -0400
Received: from relay5.tp1rc.edu.tw ([163.28.16.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19jYQf-0006LS-00
	for sigtran@ietf.org; Mon, 04 Aug 2003 02:02:45 -0400
Received: from KHL (61-219-40-1.HINET-IP.hinet.net [61.219.40.1])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by relay5.tp1rc.edu.tw (Postfix) with ESMTP id CBB09106DFE
	for <sigtran@ietf.org>; Mon,  4 Aug 2003 14:02:43 +0800 (CST)
Message-ID: <000c01c35a4f$17755eb0$6ec5900a@saoe.com>
From: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
To: "sigtran" <sigtran@ietf.org>
Date: Mon, 4 Aug 2003 14:10:01 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0009_01C35A92.18553BF0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Sigtran] question about m3UA
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C35A92.18553BF0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: quoted-printable


Should ASP3 in the Section 5.1.4 of =
<draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive =
NOTIFY(AS-INACTIVE)?

Thanls

Ling-Chih Kao
------=_NextPart_000_0009_01C35A92.18553BF0
Content-Type: text/html;
	charset="big5"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dbig5">
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Should&nbsp;ASP3 in the Section 5.1.4 of=20
&lt;draft-ietf-sigtran-m3ua-implementors-guide-04.txt&gt; receive=20
NOTIFY(AS-INACTIVE)?</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Thanls</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Ling-Chih Kao</FONT></DIV></BODY></HTML>

------=_NextPart_000_0009_01C35A92.18553BF0--


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



From exim@www1.ietf.org  Mon Aug  4 16:32:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11227
	for <sigtran-archive@odin.ietf.org>; Mon, 4 Aug 2003 16:32:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jlzv-0004H8-Ue
	for sigtran-archive@odin.ietf.org; Mon, 04 Aug 2003 16:32:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h74KW3WA016417
	for sigtran-archive@odin.ietf.org; Mon, 4 Aug 2003 16:32:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jlzt-0004GY-Hf; Mon, 04 Aug 2003 16:32:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jlzc-0004Fu-63
	for sigtran@optimus.ietf.org; Mon, 04 Aug 2003 16:31:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11222
	for <sigtran@ietf.org>; Mon, 4 Aug 2003 16:31:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19jlzZ-0005RE-00
	for sigtran@ietf.org; Mon, 04 Aug 2003 16:31:41 -0400
Received: from [66.180.118.20] (helo=sevis-main.SEVISNORTHDOM)
	by ietf-mx with esmtp (Exim 4.12)
	id 19jlzZ-0005RB-00
	for sigtran@ietf.org; Mon, 04 Aug 2003 16:31:41 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 4 Aug 2003 15:32:37 -0500
Message-ID: <9B9A9DE704231348A20E8E2CA7696A9509B7CC@sevis-main.SEVISNORTHDOM>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Thread-Topic: M2PA Timers
Thread-Index: AcNax4pSwxRf2T/aTTu/W8DbahP0aQ==
From: "Nitin Vairagare" <nitin.vairagare@sevis.com>
To: "IETF sigtran" <sigtran@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: [Sigtran] M2PA Timers
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Hi All,
=20
In M2PA draft, there are direct references to MTP2 timers. It might be
useful to=20
add section named "M2PA Timers" (similar to section 12.3 in T1.111.3)
summarizing all timers, their suggested values for IP networks and
relevant=20
considerations. For example, Timer MTP2 T7 is irrelevant to M2PA.
=20
Also, are their any specific considerations in M2PA for delay caused by
SCTP due to:
a)       delayed Ack procedures
b)       chunk bundling
=20
Thanks,
Nitin

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



From exim@www1.ietf.org  Tue Aug  5 00:24:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19710
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 00:24:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtMj-0007RK-4Y
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 00:24:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h754O5gL028560
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 00:24:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtMh-0007Q0-Jx; Tue, 05 Aug 2003 00:24:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtGq-0007IQ-KW
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 00:18:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19508
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 00:17:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19jtGo-0007Md-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 00:17:58 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19jtGm-0007Ma-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 00:17:56 -0400
Received: from [172.16.2.12] (helo=hewlettyf9yyzb)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19jtGo-00018V-9m; Mon, 04 Aug 2003 21:17:58 -0700
From: "Vivek Toky" <vivektoky@ccpu.com>
To: "kamesh kaul" <kkk_kaul@yahoo.com>
Cc: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
Date: Mon, 4 Aug 2003 21:17:43 -0700
Message-ID: <FHEPLGHNCJCJADFMFBGFAELPCBAA.vivektoky@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <20030803032346.56020.qmail@web60004.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Kamesh,
  Please see comments inline
-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
kamesh kaul
Sent: Saturday, August 02, 2003 8:24 PM
To: Vivek Toky
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour


Hi Vivek,
    I argee with you that if we intermix IPSP SE and
DE models we can start loadsharing traffic for AS2
among IPSP B and IPSP A even though IPSP B has not
received ASPAC message from IPSP c.It would result in
intermixing of two IPSP models.For some messages IPSP
C has to behave in DE manner and for other SE
behaviour is required.Lets take your example. On
receiving ASPAC messages from IPSP A and IPSP B for
AS1 IPSP C updates only remote IPSP'S states for AS1
behaving in DE manner.when IPSP c sends ASPAC for AS2
to IPSP A and receives ACK back then also IPSP C
changes its state to active for local AS2 behaving in
DE manner.Now as you said Bi-directional data is
flowing from IPSP C and IPSP A where as single
direction traffic is possible from IPSP C to IPSP B
(for AS2).Now assume IPSP A sends ASPIA message for
AS1 to IPSP C in this case IPSP c on receiving ASPIA
message has to update state of remote IPSP A in AS1
and also state of local IPSP C in local AS2 behaving
in SE manner.

[Vivek]
 You have a good point but I did not understand why would we need to change
the state of IPSP C in this case ( when IPSP A sends ASPIA to IPSP C). When
IPSP A sends ASPIA message for AS1 to IPSP C then only IPSP A's state will
change in local AS1 and the corresponding remote AS1 on the other side. You
are right that AS1 will not be able to receive traffic through IPSP A , but
that doesnot restrict AS1 to send traffic from IPSP A. Note: AS1 is still UP
and ready to process data and so is AS2. If AS1 wants to go down and not
process data at all then it should sent Inactive through both the IPSPs (
IPSP A and IPSP B). Now the question arises that what should IPSP A do if it
receives data from AS1 which has inactivated itself from both  the IPSPs and
is now totally unable to receive DATA ? ... following points should be noted
1. If AS1 doesn't want to receive data, why we care if the data sent by AS1
went through all the way to AS2.
2. Now we know that AS2 won't be able to send data to AS1 atall so it can
take recovery and De-activate itself through IPSP A (to which it sent ASP
Active and got Active Ack.)

does it make sense ? please comment..


If IPSP C does not bother about local
state updation on receiving ASPIA from IPSP A, IPSP C
will continue to send data messages for AS2 to IPSP B
without receiving anything from other side. This will
result in single direction traffic from IPSP C to AS1
without the knowledge of IPSP C.If we associate AS
state with local and peer IPSP's (in your example
AS2's state with IPSP c and each peer IPSPA and IPSPB,
AS2's state with IPSP C and each peer IPSP's) single
direction traffic flow is not possible. Please comment

Regards
Kamesh
--- Vivek Toky <vivektoky@ccpu.com> wrote:
> Hi Kamesh,
>   Although ASPAC message has not been sent to IPSP
> B, but the local AS is
> still active and is sending and receiving traffic
> through IPSP A. Now on the
> other side IPSP A and IPSP B are part of the same AS
> ( AS1 ). So following
> points should be noted.
>
> 1. Bi-directional traffic between AS1 and AS2 is
> possible
> 2. IPSP B has already sent ASPAC and received ASPAC
> Ack, so it is ready to
> receive traffic.
>
>  So why don't we loadshare the traffic among IPSP A
> and IPSP B as the
> traffic is anyway going to get to the same
> destination i.e. AS1
>
> In the reverse direction AS1 can choose IPSP A to
> send traffic towards AS2,
> as only IPSP A has received ASPAC from IPSP C (for
> AS2)
>
> comments?
>
> -Vivek.
>
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> kakaul@hss.hns.com
> Sent: Friday, August 01, 2003 1:16 AM
> To: Vivek Toky
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
>
>
>
>
> Vivek,
>
> In your example also IPSP C will send data for AS1
> to IPSP A only.I dont
> see any reason for IPSP C to send data to IPSP B
> because ASPAC message is
> not sent to IPSP B. I dont see any possibility of
> single direction traffic
> flow in your example also.
>
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>
>
>
>
> "Vivek Toky" <vivektoky@ccpu.com> on 08/01/2003
> 01:23:11 PM
>
> To:    Kamesh Kaul/HSS@HSS, sigtran@ietf.org
> cc:
>
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
> Kamesh,
>
>   Single direction traffic will still be possible.
> If you look at my
> example carefully you will notice that in case of 3
> IPSPs, it will be
> possible. It may be for a short duration of time. In
> my example local
> AS is already Active as it sent ASP Active message
> to one of the peer
> IPSPs ( also got the ACK back )
>
> please go through the example again .. waiting for
> comments ?
>
> Vivek
> >
> >
> >
> >
> > Hi Some comments below
> >
> >  When IPSP B receives ASPAC message from IPSP A
> for AS1 it marks
> remote
> > IPSP A active for remote AS1 and sends ASPAC ack
> back for AS1 to
> IPSP A.Now
> > with these message exchanges it means that IPSP A
> is ready to receive
> > traffic for AS1.At this point of time IPSP B has
> not expressed its
> > willingness to send data for any AS.IPSP B  cannot
>  send any
> application
> > data because its local applications are not active
> yet.So single
> direction
> > traffic flow will never occur.Now when IPSP B
> sends ASPAC message
> for AS2
> > to IPSP A and gets back ASPAC ack for AS2 it will
> give resume
> indication to
> > user now.AS1 and AS2 are basically same type of
> MTP3 users, and user
> to
> > user communication will only start if both users
> are ready and
> active.
> >
> >
> >     +-----------+              +-----------+
> >     |           |              |           |
> >     | IPSP A    |              | IPSP B    |
> >     |           +--------------+           |
> >     |           |              |           |
> >     +-----------+              +-----------+
> >
> >         AS1                        AS2
> >
> > Kamesh Kaul
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> >
> >
> >
> > "VIvek Toky" <vivektoky@ccpu.com>@ietf.org on
> 07/31/2003 11:19:39 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    "Tolga Asveren" <tolga_asveren@yahoo.com>,
> <sigtran@ietf.org>
> > cc:
> >
> > Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> >
> >
> > Tolga,
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On
> Behalf Of
> > Tolga Asveren
> > Sent: Thursday, July 31, 2003 10:19 AM
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> >
> >
> > Vivek,
> > --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > > Please see my comments inline
> > >
> > > > See my opigion online
> > > >
> > > > > -----Original Message-----
> > > > > From: Vivek Toky [mailto:vivektoky@ccpu.com]
> > > > > Sent: Thursday, July 31, 2003 2:42 PM
> > > > > To: Tolga Asveren; sigtran@ietf.org
> > > > > Subject: RE: [Sigtran] M3UA : IPSP DE
> behaviour
> > > > >
> > > > >
> > > > > Hi Tolga,
> > > > >   "Above case" means
> > > > > "when AS1 has activated itself by sending
> > > > >  ASP Active from both the IPSPs (A & B) but
> > > > >  AS2 has sent ASP Active just to IPSP_A."
> > > > >
> > > > > In my opinion IPSP_C should loadshare the
> > > traffic
> > > > > as it has received ASP active from both the
> > > IPSPs
> > > > > so AS1 is accessible through both of these.
> > > > > However, it is the responsibility of AS1 to
> > > route
> > > > > all the traffic towards AS2 through IPSP_A.
> > > >
> > > > If IPSP_B receive some traffic from IPSP_C BUT
> no
> > > AS is ACTIVE for
> > > it on
> > > > IPSP_C can it route this traffic???
> > > > CAN a SG send to a ss7 network a message
> receive
> > > from an INACTIVE
> > > ASP !
>
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

_______________________________________________
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



From exim@www1.ietf.org  Tue Aug  5 00:41:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19930
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 00:41:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtd7-000849-Om
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 00:41:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h754f1aa030984
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 00:41:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtd7-00083W-7I; Tue, 05 Aug 2003 00:41:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtcV-00082r-0e
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 00:40:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19910
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 00:40:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19jtcS-0007Uc-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 00:40:20 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[PNvoWAMa9HmxjAr0oDSG+ZblVk66hogJ])
	by ietf-mx with esmtp (Exim 4.12)
	id 19jtcR-0007UZ-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 00:40:19 -0400
Received: from ns.pigworks.openss7.net (IDENT:YmggeCIxkAmVjNekf4LcrmByghFCyk/e@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h754eJE12982;
	Mon, 4 Aug 2003 22:40:19 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h754eJi09600;
	Mon, 4 Aug 2003 22:40:19 -0600
Date: Mon, 4 Aug 2003 22:40:19 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Nitin Vairagare <nitin.vairagare@sevis.com>
Cc: IETF sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] M2PA Timers
Message-ID: <20030804224019.A9304@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Nitin Vairagare <nitin.vairagare@sevis.com>,
	IETF sigtran <sigtran@ietf.org>
References: <9B9A9DE704231348A20E8E2CA7696A9509B7CC@sevis-main.SEVISNORTHDOM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <9B9A9DE704231348A20E8E2CA7696A9509B7CC@sevis-main.SEVISNORTHDOM>; from nitin.vairagare@sevis.com on Mon, Aug 04, 2003 at 03:32:37PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Nitin,

1) T7 is relevant.

2) 12.3 is applicable and does not need to be copied into M2PA.

--brian

Nitin Vairagare wrote:                                                               (Mon, 04 Aug 2003 15:32:37)
> Hi All,
>  
> In M2PA draft, there are direct references to MTP2 timers. It might be
> useful to 
> add section named "M2PA Timers" (similar to section 12.3 in T1.111.3)
> summarizing all timers, their suggested values for IP networks and
> relevant 
> considerations. For example, Timer MTP2 T7 is irrelevant to M2PA.
>  
> Also, are their any specific considerations in M2PA for delay caused by
> SCTP due to:
> a)       delayed Ack procedures
> b)       chunk bundling
>  
> Thanks,
> Nitin
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Tue Aug  5 00:49:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19984
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 00:49:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtkr-0008C5-Ik
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 00:49:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h754n1R3031493
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 00:49:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtkq-0008Bj-ND; Tue, 05 Aug 2003 00:49:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtk8-0008BR-Ex
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 00:48:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19978
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 00:48:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19jtk5-0007WE-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 00:48:13 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[D1qSTMLKr2Q4w3suC4zAqp1j59ufZMVN])
	by ietf-mx with esmtp (Exim 4.12)
	id 19jtk4-0007WB-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 00:48:13 -0400
Received: from ns.pigworks.openss7.net (IDENT:014Kb/nEfwasL8XBQrDfKfap8WKiz/G5@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h754mDE13075;
	Mon, 4 Aug 2003 22:48:13 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h754mDm09640;
	Mon, 4 Aug 2003 22:48:13 -0600
Date: Mon, 4 Aug 2003 22:48:13 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: kakaul@hss.hns.com
Cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030804224812.B9304@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: kakaul@hss.hns.com, Ling-Chih Kao <d86942004@ntu.edu.tw>,
	sigtran <sigtran@ietf.org>
References: <OF7995203C.4931A9B8-ON65256D79.0015EA13@hss.hns.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF7995203C.4931A9B8-ON65256D79.0015EA13@hss.hns.com>; from kakaul@hss.hns.com on Tue, Aug 05, 2003 at 09:31:47AM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h754mDE13075
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

kakaul,

But I think that we agreed that it would be wise to tell newly inactive
ASPs that state of the AS.  Also, in the diagram, the state of the AS
does not change with the second ASP (ASP2) sending ASPUP.  The AS changes
state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram should
show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately after the
ASPUP Ack is sent to the ASP in question.

The diagram is quite wrong.  Also it is wrong considering the changes to
be made to the next issue of the IG.

--brian

kakaul@hss.hns.com wrote:                                                =
           (Tue, 05 Aug 2003 09:31:47)
>=20
>=20
>=20
>=20
> On receiving ASPUP message from ASP3 state of AS does not change, so
> NOTIFY(AS-INACTIVE) is not send to ASP3.
>=20
> Kamesh
>=20
>=20
>=20
>=20
> "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003 11:40:01 =
AM
>=20
> Sent by:    sigtran-admin@ietf.org
>=20
>=20
> To:    "sigtran" <sigtran@ietf.org>
> cc:
>=20
> Subject:    [Sigtran] question about m3UA
>=20
>=20
>=20
>=20
> Should=A0ASP3 in the Section 5.1.4 of
> <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> NOTIFY(AS-INACTIVE)?
>=20
> Thanls
>=20
> Ling-Chih Kao
>=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Tue Aug  5 01:11:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19712
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 00:24:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtMj-0007R0-3D
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 00:24:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h754O5px028561
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 00:24:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jtMg-0007P4-F9; Tue, 05 Aug 2003 00:24:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19jt73-0007Ab-GV
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 00:07:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19426
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 00:07:48 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19jt71-0007L0-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 00:07:51 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19jt70-0007Kt-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 00:07:50 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h7543OV24039;
	Tue, 5 Aug 2003 09:33:24 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h7547Ju03986;
	Tue, 5 Aug 2003 09:37:19 +0530 (IST)
Subject: Re: [Sigtran] question about m3UA
To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
Cc: "sigtran" <sigtran@ietf.org>
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF7995203C.4931A9B8-ON65256D79.0015EA13@hss.hns.com>
Date: Tue, 5 Aug 2003 09:31:47 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 05/08/2003
 09:30:23 AM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable





On receiving ASPUP message from ASP3 state of AS does not change, so
NOTIFY(AS-INACTIVE) is not send to ASP3.

Kamesh




"Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003 11:40:01 =
AM

Sent by:    sigtran-admin@ietf.org


To:    "sigtran" <sigtran@ietf.org>
cc:

Subject:    [Sigtran] question about m3UA




Should=A0ASP3 in the Section 5.1.4 of
<draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
NOTIFY(AS-INACTIVE)?

Thanls

Ling-Chih Kao
=



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



From exim@www1.ietf.org  Tue Aug  5 01:24:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20514
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 01:24:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19juIj-0000lQ-NG
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 01:24:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h755O1T9002935
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 01:24:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19juIi-0000l7-Rg; Tue, 05 Aug 2003 01:24:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19juIg-0000kt-A1
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 01:23:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20510
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 01:23:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19juId-0007fQ-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 01:23:55 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19juIc-0007fI-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 01:23:54 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h755N3wA004549;
	Tue, 5 Aug 2003 00:23:04 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h755MP1C024912;
	Tue, 5 Aug 2003 00:22:25 -0500 (CDT)
Date: Tue, 5 Aug 2003 00:22:25 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: kakaul@hss.hns.com, Ling-Chih Kao <d86942004@ntu.edu.tw>,
        sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <20030804224812.B9304@openss7.org>
Message-ID: <Pine.SOL.4.10.10308050007240.3982-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: QUOTED-PRINTABLE


Brian,

On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:

> kakaul,
>=20
> But I think that we agreed that it would be wise to tell newly inactive
                                                      ------------------
> ASPs that state of the AS.  Also, in the diagram, the state of the AS
  -------------------------

What does ASP3 do with NOTIFY(AS-INACTIVE)?
Whenever AS state-change happens at SGP, a NTFY will be sent to all ASPes
(other than DOWN-ASPes) pertaining to the same RC.
This is what i remember that everybody agreed.

--Samuel
> does not change with the second ASP (ASP2) sending ASPUP.  The AS changes
> state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram should
> show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately after the
> ASPUP Ack is sent to the ASP in question.
>=20
> The diagram is quite wrong.  Also it is wrong considering the changes to
> be made to the next issue of the IG.
>=20
> --brian
>=20
> kakaul@hss.hns.com wrote:                                                =
           (Tue, 05 Aug 2003 09:31:47)
> >=20
> >=20
> >=20
> >=20
> > On receiving ASPUP message from ASP3 state of AS does not change, so
> > NOTIFY(AS-INACTIVE) is not send to ASP3.
> >=20
> > Kamesh
> >=20
> >=20
> >=20
> >=20
> > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003 11:40:01 =
AM
> >=20
> > Sent by:    sigtran-admin@ietf.org
> >=20
> >=20
> > To:    "sigtran" <sigtran@ietf.org>
> > cc:
> >=20
> > Subject:    [Sigtran] question about m3UA
> >=20
> >=20
> >=20
> >=20
> > Should=A0ASP3 in the Section 5.1.4 of
> > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > NOTIFY(AS-INACTIVE)?
> >=20
> > Thanls
> >=20
> > Ling-Chih Kao
> >=20
> >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20


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



From exim@www1.ietf.org  Tue Aug  5 10:16:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12992
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 10:16:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2bc-0000hj-Tb
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 10:16:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75EG4aP002697
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 10:16:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2ba-0000gG-U3; Tue, 05 Aug 2003 10:16:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2bK-0000fK-N3
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 10:15:46 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12817;
	Tue, 5 Aug 2003 10:15:31 -0400 (EDT)
Message-Id: <200308051415.KAA12817@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 05 Aug 2003 10:15:31 -0400
Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-signalling-over-sctp-applic-09.txt
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Signaling Transport Working Group of the IETF.

	Title		: Telephony Signalling Transport over SCTP applicability statement
	Author(s)	: L. Coene, J. Pastor
	Filename	: draft-ietf-sigtran-signalling-over-sctp-applic-09.txt
	Pages		: 23
	Date		: 2003-8-5
	
This document describes the applicability of the new protocols
developed under the signaling transport framework[RFC2719]. A
description of the main issues regarding the use of the Stream
Control Transmission Protocol (SCTP)[RFC2960] and each adaptation
layer for transport of telephony signalling information over IP
infrastructure is explained.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-signalling-over-sctp-applic-09.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sigtran-signalling-over-sctp-applic-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sigtran-signalling-over-sctp-applic-09.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-5100440.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sigtran-signalling-over-sctp-applic-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sigtran-signalling-over-sctp-applic-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-5100440.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Tue Aug  5 10:55:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14365
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 10:55:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k3DM-0002RM-Rb
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 10:55:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75Et4KT009359
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 10:55:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k3DJ-0002Qf-3s; Tue, 05 Aug 2003 10:55:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k3D6-0002QB-CS
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 10:54:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14250
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 10:54:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k3D3-0002bf-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 10:54:45 -0400
Received: from [66.180.118.20] (helo=sevis-main.SEVISNORTHDOM)
	by ietf-mx with esmtp (Exim 4.12)
	id 19k3D3-0002aX-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 10:54:45 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Sigtran] M2PA Timers
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 5 Aug 2003 09:55:46 -0500
Message-ID: <9B9A9DE704231348A20E8E2CA7696A9509B7D8@sevis-main.SEVISNORTHDOM>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Thread-Topic: [Sigtran] M2PA Timers
Thread-Index: AcNbC+UEH7YHE+J5TQqsoJCn67mSOQAT3PUg
From: "Nitin Vairagare" <nitin.vairagare@sevis.com>
To: <bidulock@openss7.org>
Cc: "IETF sigtran" <sigtran@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Brain,

Sorry for the Typo, I mean=20
* The Timer T8 used for error rate monitoring.
* Also there is no mention of timer T5 (sending SIB/Status Busy).
  It just specifies: "M2PA MAY send additional Link Status Busy
  messages as long as that condition persists". It is not clear if
  Timer T5 should be used or implementation can decide its own interval.
* Similarly a parameter Proving_interval is introduced, if proving is=20
  performed.

I was not concerned about copying section 12.3, but summarizing=20
exceptions to this section.

Regards,
Nitin

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]=20
Sent: Monday, August 04, 2003 11:40 PM
To: Nitin Vairagare
Cc: IETF sigtran
Subject: Re: [Sigtran] M2PA Timers

Nitin,

1) T7 is relevant.

2) 12.3 is applicable and does not need to be copied into M2PA.

--brian

Nitin Vairagare wrote:
(Mon, 04 Aug 2003 15:32:37)
> Hi All,
> =20
> In M2PA draft, there are direct references to MTP2 timers. It might be
> useful to=20
> add section named "M2PA Timers" (similar to section 12.3 in T1.111.3)
> summarizing all timers, their suggested values for IP networks and
> relevant=20
> considerations. For example, Timer MTP2 T7 is irrelevant to M2PA.
> =20
> Also, are their any specific considerations in M2PA for delay caused
by
> SCTP due to:
> a)       delayed Ack procedures
> b)       chunk bundling
> =20
> Thanks,
> Nitin
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Tue Aug  5 11:28:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16064
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 11:28:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k3jG-0003fT-SW
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 11:28:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75FS2f5014093
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 11:28:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k3jF-0003f5-8F; Tue, 05 Aug 2003 11:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k3iH-0003ck-75
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 11:27:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16044
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 11:26:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k3iG-0003B5-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 11:27:00 -0400
Received: from mails.conexion.com.py ([65.198.40.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k3iD-0003At-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 11:26:58 -0400
Received: from miguelpc (mf.conexion.com.py [65.198.40.11])
	by mails.conexion.com.py (8.12.8/8.12.8) with SMTP id h75FXJkT019766
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 11:33:19 -0400
Message-ID: <009901c35b33$a49c6b00$6700a8c0@miguelpc>
From: "Miguel Willigs" <miguel.willigs@conexiongroup.com>
To: <sigtran@ietf.org>
Date: Tue, 5 Aug 2003 11:26:25 +0200
Organization: Conexion
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0096_01C35B44.680D4630"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
Subject: [Sigtran] doubt about sctp associations
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_0096_01C35B44.680D4630
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi there,
         I am having a doubt about sctp associations when used in the =
M2UA Layer.

It says in RFC 3331, page 9, "The M2UA layer MUST maintain a map of an =
Interface ID to a physical interface on the Signalling Gateway.  A =
physical interface would be a V.35 line, T1 line/time slot, E1 line/time =
slot, etc.  The M2UA layer MUST also maintain a map of the Interface =
Identifier to SCTP association and to the related stream within the =
association."

So, does it mean that (always) a sctp association consists in 2 sctp =
endpoints (IP:Port address) and also the stream they use to communicate?

          thanks,
                  Miguel

------=_NextPart_000_0096_01C35B44.680D4630
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Hi=20
there,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I am having a =
doubt=20
about sctp associations when used in the M2UA Layer.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>It says in RFC 3331, page 9, "The M2UA =
layer MUST=20
maintain a map of an Interface ID to a physical interface on the =
Signalling=20
Gateway.&nbsp; A physical interface would be a V.35 line, T1 line/time =
slot, E1=20
line/time slot, etc.&nbsp; The M2UA layer MUST also maintain a map of =
the=20
Interface Identifier to SCTP association and to the related stream =
within the=20
association."</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>So, does it mean that (always) a sctp =
association=20
consists in 2 sctp endpoints (IP:Port address) and also the stream they =
use to=20
communicate?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
thanks,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Miguel</FONT></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0096_01C35B44.680D4630--


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



From exim@www1.ietf.org  Tue Aug  5 11:34:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16280
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 11:34:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k3p4-0003te-IB
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 11:34:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75FY2jo014957
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 11:34:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k3p3-0003t0-OC; Tue, 05 Aug 2003 11:34:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k3oe-0003sc-0O
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 11:33:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16257
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 11:33:31 -0400 (EDT)
From: svakumar@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k3od-0003Du-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 11:33:35 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19k3ob-0003DT-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 11:33:33 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5] (may be forged))
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h75FUQw08197;
	Tue, 5 Aug 2003 21:00:26 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h75FWxT14660;
	Tue, 5 Aug 2003 21:02:59 +0530 (IST)
Subject: Re: [Sigtran] doubt about sctp associations
To: "Miguel Willigs" <miguel.willigs@conexiongroup.com>
Cc: <sigtran@ietf.org>
Date: Tue, 5 Aug 2003 20:57:28 +0530
Message-ID: <OF0648169A.4605068B-ON65256D79.0054BFB6@hss.hns.com>
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 05/08/2003
 08:56:04 PM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable






Hi Migual,
yes.

regds
Satyendra




"Miguel Willigs" <miguel.willigs@conexiongroup.com>@ietf.org on 08/05/2=
003
02:56:25 PM

Sent by:    sigtran-admin@ietf.org


To:    <sigtran@ietf.org>
cc:

Subject:    [Sigtran] doubt about sctp associations




Hi  there,
=A0=A0=A0=A0=A0=A0=A0=A0 I am having a doubt  about sctp associations w=
hen used in the M2UA
Layer.

It says in RFC 3331, page 9, "The M2UA layer MUST  maintain a map of an=

Interface ID to a physical interface on the Signalling  Gateway.=A0 A
physical interface would be a V.35 line, T1 line/time slot, E1  line/ti=
me
slot, etc.=A0 The M2UA layer MUST also maintain a map of the  Interface=

Identifier to SCTP association and to the related stream within the
association."

So, does it mean that (always) a sctp association  consists in 2 sctp
endpoints (IP:Port address) and also the stream they use to  communicat=
e?

=A0=A0=A0=A0=A0=A0=A0=A0=A0  thanks,
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0  Miguel
=



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



From exim@www1.ietf.org  Tue Aug  5 14:37:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22395
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 14:37:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k6gB-0002mR-Hl
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 14:37:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75Ib3h3010683
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 14:37:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k6g9-0002lY-BE; Tue, 05 Aug 2003 14:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k6fy-0002kd-2I
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 14:36:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22343
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 14:36:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k6fu-0004gZ-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 14:36:46 -0400
Received: from mails.conexion.com.py ([65.198.40.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k6fr-0004fh-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 14:36:43 -0400
Received: from miguelpc (mf.conexion.com.py [65.198.40.11])
	by mails.conexion.com.py (8.12.8/8.12.8) with SMTP id h75IhAkT007023
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 14:43:13 -0400
Message-ID: <001a01c35b4e$2b3339e0$6700a8c0@miguelpc>
From: "Miguel Willigs" <miguel.willigs@conexiongroup.com>
To: <sigtran@ietf.org>
Date: Tue, 5 Aug 2003 14:36:15 +0200
Organization: Conexion
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0017_01C35B5E.ECF4B760"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
Subject: [Sigtran] SG and MGC
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_0017_01C35B5E.ECF4B760
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi there,

         I have a question for you, people. Suppose, I have a SG and a =
MGC that have to communicate
with each other. ASP #1 is attached to AS #1 and ASP #2 is attached to =
AS #2. Suppose both ASP's are
in the active state. I know the sctp association is a half-duplex =
channel, rigth? So, is it rigth for=20
them to use the same IP:Port address to send and receive M2UA messages. =
Example, for ASP #1 in the=20
SG the 65.198.40.50:3005 (IP:Port) address is used, and in the MGC the =
65.198.40.52:3006 is used.

If that is the case, how is the communication synchronized?



|----------- SG -------------------||----------- MGC =
---------------------|

ASP #1 ---- 65.198.40.50:3005 <-----------> 65.198.40.52:3006 ----- ASP =
#1

ASP #2 ---- 65.198.40.51:3005 <-----------> 65.198.40.53:3006 ----- ASP =
#2


Another question, can a SG support both, dynamic and static =
registration, of ASP's. I mean, to have
initially pre-configured ASP's and to support dynamic registration at =
the same time.


                  thanks,
                          Miguel.

------=_NextPart_000_0017_01C35B5E.ECF4B760
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi there,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I=20
have a question for you, people. Suppose, I have a SG and a MGC that =
have to=20
communicate<BR>with each other. ASP #1 is attached to AS #1 and ASP #2 =
is=20
attached to AS #2. Suppose both ASP's are<BR>in the active state. I know =
the=20
sctp association is a half-duplex channel, rigth? So, is it rigth for =
<BR>them=20
to use the same IP:Port address to send and receive M2UA messages. =
Example, for=20
ASP #1 in the <BR>SG the 65.198.40.50:3005 (IP:Port) address is used, =
and in the=20
MGC the 65.198.40.52:3006 is used.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>If that is the case, how is the =
communication=20
synchronized?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>|----------- SG =
-------------------||-----------=20
MGC ---------------------|</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>ASP #1 ---- 65.198.40.50:3005 =
&lt;-----------&gt;=20
65.198.40.52:3006 ----- ASP #1</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>ASP #2 ---- 65.198.40.51:3005 =
&lt;-----------&gt;=20
65.198.40.53:3006 ----- ASP #2</FONT></DIV>
<DIV>&nbsp;</DIV><FONT face=3DArial size=3D2>
<DIV><BR>Another question, can a SG support both, dynamic and static=20
registration, of ASP's. I mean, to have<BR>initially pre-configured =
ASP's and to=20
support dynamic registration at the same time.</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
thanks,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
Miguel.</FONT></DIV></BODY></HTML>

------=_NextPart_000_0017_01C35B5E.ECF4B760--


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



From exim@www1.ietf.org  Tue Aug  5 16:03:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26672
	for <sigtran-archive@odin.ietf.org>; Tue, 5 Aug 2003 16:03:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k81P-00067Q-4B
	for sigtran-archive@odin.ietf.org; Tue, 05 Aug 2003 16:03:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75K33hN023516
	for sigtran-archive@odin.ietf.org; Tue, 5 Aug 2003 16:03:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k81N-00066d-Fs; Tue, 05 Aug 2003 16:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k80T-00064y-Tt
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 16:02:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26602
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 16:02:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k80R-0005PD-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 16:02:03 -0400
Received: from mails.conexion.com.py ([65.198.40.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k80K-0005Ox-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 16:02:01 -0400
Received: from miguelpc (mf.conexion.com.py [65.198.40.11])
	by mails.conexion.com.py (8.12.8/8.12.8) with SMTP id h75K8QkT032265
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 16:08:29 -0400
Message-ID: <00b001c35b5a$14e8c810$6700a8c0@miguelpc>
From: "Miguel Willigs" <miguel.willigs@conexiongroup.com>
To: <sigtran@ietf.org>
Subject: [Sigtran] doubt about sctp associations
Date: Tue, 5 Aug 2003 16:01:31 +0200
Organization: Conexion
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi,

  Sorry,the last message wasn't suppost to go to the mailing list. That's an
old message I've coppied from the mailing list. Here are my doubdts:

What about the case where an ASP is resident on a Host using dynamic
address/port number assignments? Should the SG know the stream that will be
used for communicating with an ASP, by looking at what stream the ASP Up
message arrived?

Another question: Dynamic address/port number assignments is different from
dynamic ASP's registrations, rigth?
So, dynamic address/port number assignments "must" be supported in opposed
to dynamic ASP's registrations, that are optional, right?

         thanks again,
                      Miguel


----- Original Message -----
From: <svakumar@hss.hns.com>
To: "Miguel Willigs" <miguel.willigs@conexiongroup.com>
Cc: <sigtran@ietf.org>
Sent: Tuesday, August 05, 2003 5:27 PM
Subject: Re: [Sigtran] doubt about sctp associations







Hi Migual,
yes.

regds
Satyendra




"Miguel Willigs" <miguel.willigs@conexiongroup.com>@ietf.org on 08/05/2003
02:56:25 PM

Sent by:    sigtran-admin@ietf.org


To:    <sigtran@ietf.org>
cc:

Subject:    [Sigtran] doubt about sctp associations




Hi  there,
I am having a doubt  about sctp associations when used in the M2UA
Layer.

It says in RFC 3331, page 9, "The M2UA layer MUST  maintain a map of an
Interface ID to a physical interface on the Signalling  Gateway. A
physical interface would be a V.35 line, T1 line/time slot, E1  line/time
slot, etc. The M2UA layer MUST also maintain a map of the  Interface
Identifier to SCTP association and to the related stream within the
association."

So, does it mean that (always) a sctp association  consists in 2 sctp
endpoints (IP:Port address) and also the stream they use to  communicate?

  thanks,
  Miguel



_______________________________________________
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



From exim@www1.ietf.org  Wed Aug  6 00:36:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08728
	for <sigtran-archive@odin.ietf.org>; Wed, 6 Aug 2003 00:36:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kG1w-0004N1-CP
	for sigtran-archive@odin.ietf.org; Wed, 06 Aug 2003 00:36:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h764a8lo016795
	for sigtran-archive@odin.ietf.org; Wed, 6 Aug 2003 00:36:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kG1q-0004Mf-1s; Wed, 06 Aug 2003 00:36:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kG19-0004LK-Bn
	for sigtran@optimus.ietf.org; Wed, 06 Aug 2003 00:35:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08693
	for <sigtran@ietf.org>; Wed, 6 Aug 2003 00:35:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kG16-0000Gq-00
	for sigtran@ietf.org; Wed, 06 Aug 2003 00:35:16 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[fJHgxtswglmDlI8MxiOBvJBBz1QGouHy])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kG16-0000Gn-00
	for sigtran@ietf.org; Wed, 06 Aug 2003 00:35:16 -0400
Received: from ns.pigworks.openss7.net (IDENT:KslFJkPm0e1GuYzMQYfxgbTIB+8ZW67G@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h764ZDE32736;
	Tue, 5 Aug 2003 22:35:13 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h764ZCo24452;
	Tue, 5 Aug 2003 22:35:12 -0600
Date: Tue, 5 Aug 2003 22:35:11 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Nitin Vairagare <nitin.vairagare@sevis.com>
Cc: IETF sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] M2PA Timers
Message-ID: <20030805223511.A24285@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Nitin Vairagare <nitin.vairagare@sevis.com>,
	IETF sigtran <sigtran@ietf.org>
References: <9B9A9DE704231348A20E8E2CA7696A9509B7D8@sevis-main.SEVISNORTHDOM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <9B9A9DE704231348A20E8E2CA7696A9509B7D8@sevis-main.SEVISNORTHDOM>; from nitin.vairagare@sevis.com on Tue, Aug 05, 2003 at 09:55:46AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Nitin,

Nitin Vairagare wrote:                                                               (Tue, 05 Aug 2003 09:55:46)
> Brain,
> 
> Sorry for the Typo, I mean 
> * The Timer T8 used for error rate monitoring.

T8 appears in Q.703 Annex A, which is no longer cited by the draft.


> * Also there is no mention of timer T5 (sending SIB/Status Busy).
>   It just specifies: "M2PA MAY send additional Link Status Busy
>   messages as long as that condition persists". It is not clear if
>   Timer T5 should be used or implementation can decide its own interval.

There is no interval mentioned.

> * Similarly a parameter Proving_interval is introduced, if proving is 
>   performed.

Recommendations for setting the Proving_interval appear in the draft.

> 
> I was not concerned about copying section 12.3, but summarizing 
> exceptions to this section.

--brian


> 
> Regards,
> Nitin
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org] 
> Sent: Monday, August 04, 2003 11:40 PM
> To: Nitin Vairagare
> Cc: IETF sigtran
> Subject: Re: [Sigtran] M2PA Timers
> 
> Nitin,
> 
> 1) T7 is relevant.
> 
> 2) 12.3 is applicable and does not need to be copied into M2PA.
> 
> --brian
> 
> Nitin Vairagare wrote:
> (Mon, 04 Aug 2003 15:32:37)
> > Hi All,
> >  
> > In M2PA draft, there are direct references to MTP2 timers. It might be
> > useful to 
> > add section named "M2PA Timers" (similar to section 12.3 in T1.111.3)
> > summarizing all timers, their suggested values for IP networks and
> > relevant 
> > considerations. For example, Timer MTP2 T7 is irrelevant to M2PA.
> >  
> > Also, are their any specific considerations in M2PA for delay caused
> by
> > SCTP due to:
> > a)       delayed Ack procedures
> > b)       chunk bundling
> >  
> > Thanks,
> > Nitin
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Wed Aug  6 08:31:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14093
	for <sigtran-archive@odin.ietf.org>; Wed, 6 Aug 2003 08:31:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kNRX-0002rI-HM
	for sigtran-archive@odin.ietf.org; Wed, 06 Aug 2003 08:31:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h76CV3HB010987
	for sigtran-archive@odin.ietf.org; Wed, 6 Aug 2003 08:31:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kNRV-0002qw-NQ; Wed, 06 Aug 2003 08:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kNRH-0002qN-Tk
	for sigtran@optimus.ietf.org; Wed, 06 Aug 2003 08:30:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14069
	for <sigtran@ietf.org>; Wed, 6 Aug 2003 08:30:44 -0400 (EDT)
From: ygahlaut@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kNRG-0002Pf-00
	for sigtran@ietf.org; Wed, 06 Aug 2003 08:30:46 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kNRF-0002PI-00
	for sigtran@ietf.org; Wed, 06 Aug 2003 08:30:45 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5] (may be forged))
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h76CRbw25793
	for <sigtran@ietf.org>; Wed, 6 Aug 2003 17:57:37 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h76CUC428854
	for <sigtran@ietf.org>; Wed, 6 Aug 2003 18:00:12 +0530 (IST)
To: sigtran@ietf.org
Date: Wed, 6 Aug 2003 17:54:39 +0530
Message-ID: <OFDAE64171.DFB3F976-ON65256D7A.0037A2D5@hss.hns.com>
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 06/08/2003
 05:53:15 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Subject: [Sigtran] SUA -- Source Address in the CORE message
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>





Hi,
        According to the SUA draft Source Address field in CORE message is
optional.
Consider the following sequence

SGP sends a CORE message to ASP without Source Address.
ASP sends back the COAK to same SGP without Destination Address.
Connection established
:
:
 Data transfer takes place
:
:
SGP sends a DUNA message
:
:  <----- Point 1
:
ASP Send Connection Oriented Data
:
:  <---- Point 2
:


Now  queries
1> on Point 1 should the connection be terminated with the destination from
which DUNA message is received and no CODT is allowed
If Yes.... How ?  considering the case where ASP did not receive the Source
Address in CORE message. how can the connection be identified?  because ASP
does not know the peer's address for this Connection.

Should the Connection be identified using RC  but then there may be a case
in which there is no RC in DUNA message (RC is optional in DUNA message) ?

2> on point 2 should this CODT message be allowed to reach SGP ?
   should this message be  routed to another SGP(if there) ?


Please correct me if I am missing something

Regards
Yogesh
www.hssworld.com
Hughes Software Systems


"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
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From exim@www1.ietf.org  Wed Aug  6 09:35:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15918
	for <sigtran-archive@odin.ietf.org>; Wed, 6 Aug 2003 09:35:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kORT-0005MU-4e
	for sigtran-archive@odin.ietf.org; Wed, 06 Aug 2003 09:35:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h76DZ37O020593
	for sigtran-archive@odin.ietf.org; Wed, 6 Aug 2003 09:35:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kORR-0005Lk-Kl; Wed, 06 Aug 2003 09:35:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kOQo-0005L7-0b
	for sigtran@optimus.ietf.org; Wed, 06 Aug 2003 09:34:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15875
	for <sigtran@ietf.org>; Wed, 6 Aug 2003 09:34:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kOQm-0002qT-00
	for sigtran@ietf.org; Wed, 06 Aug 2003 09:34:20 -0400
Received: from angelica.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kOQl-0002q2-00
	for sigtran@ietf.org; Wed, 06 Aug 2003 09:34:19 -0400
Received: from navy.fr.ulticom.com (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with ESMTP id JAA24730
	for <sigtran@ietf.org>; Wed, 6 Aug 2003 09:33:19 -0400 (EDT)
Received: from PCGASTAUDL (pc-gastaud-l.fr.ulticom.com [172.26.32.88])
	by navy.fr.ulticom.com (8.11.6+Sun/8.11.6) with SMTP id h76DTIJ08963
	for <sigtran@ietf.org>; Wed, 6 Aug 2003 15:29:19 +0200 (MEST)
From: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
To: "Sigtran" <sigtran@ietf.org>
Date: Wed, 6 Aug 2003 15:33:59 +0200
Message-ID: <NDBBIHAOCKGAMIKNLALOIENGDOAA.valerie.gastaud@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.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] SUA - RC in CLDT
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit


Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2 messages)?
This is not consistent with M3UA and this is not consistent with the SUA
ASPAC message in which the RC is optional.
In case of static provisioning of RK, if an SGP receives an ASPAC w/o RC, it
won't be able to insert the RC in the CLDT.

Valerie



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



From exim@www1.ietf.org  Wed Aug  6 17:03:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04794
	for <sigtran-archive@odin.ietf.org>; Wed, 6 Aug 2003 17:03:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kVR1-0001xT-PD
	for sigtran-archive@odin.ietf.org; Wed, 06 Aug 2003 17:03:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h76L33q4007506
	for sigtran-archive@odin.ietf.org; Wed, 6 Aug 2003 17:03:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kVQz-0001wn-LG; Wed, 06 Aug 2003 17:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kVQd-0001w7-3N
	for sigtran@optimus.ietf.org; Wed, 06 Aug 2003 17:02:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04777
	for <sigtran@ietf.org>; Wed, 6 Aug 2003 17:02:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kVQa-00079k-00
	for sigtran@ietf.org; Wed, 06 Aug 2003 17:02:36 -0400
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kVQa-00079g-00
	for sigtran@ietf.org; Wed, 06 Aug 2003 17:02:36 -0400
Received: from lurchi.franken.de (dialin-145-254-160-122.arcor-ip.net [145.254.160.122])
	by mail-n.franken.de (Postfix) with ESMTP id BE1A124652
	for <sigtran@ietf.org>; Wed,  6 Aug 2003 23:02:10 +0200 (CEST)
Date: Wed, 6 Aug 2003 23:00:56 +0200
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
To: sigtran@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <13201337-C851-11D7-8CB5-000A9591232C@lurchi.franken.de>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] Extended deadline for SIGTRAN Interop
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Dear all,

I would like to let you know that the original deadline for
registration August 11th is extended to August 17th.

You can register for the interoperability test using the URL
http://www.etsi.org/plugtests/02UpcomingEvents/SIGTRAN/SIGTRAN_home.htm

Best regards
Michael

tuexen@fh-muenster.de


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



From exim@www1.ietf.org  Wed Aug  6 23:54:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16497
	for <sigtran-archive@odin.ietf.org>; Wed, 6 Aug 2003 23:54:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kbqm-0007xt-24
	for sigtran-archive@odin.ietf.org; Wed, 06 Aug 2003 23:54:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h773s4hn030613
	for sigtran-archive@odin.ietf.org; Wed, 6 Aug 2003 23:54:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kbqj-0007xX-J7; Wed, 06 Aug 2003 23:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kbqK-0007xD-LR
	for sigtran@optimus.ietf.org; Wed, 06 Aug 2003 23:53:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16481
	for <sigtran@ietf.org>; Wed, 6 Aug 2003 23:53:32 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kbqI-000297-00
	for sigtran@ietf.org; Wed, 06 Aug 2003 23:53:34 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kbqG-00028y-00
	for sigtran@ietf.org; Wed, 06 Aug 2003 23:53:33 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5] (may be forged))
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h773oPw05986;
	Thu, 7 Aug 2003 09:20:25 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h773r0d02195;
	Thu, 7 Aug 2003 09:23:00 +0530 (IST)
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
To: vivektoky@ccpu.com
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF453B9C5C.69D37498-ON65256D7B.0014AE62@hss.hns.com>
Date: Thu, 7 Aug 2003 09:17:27 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 07/08/2003
 09:16:01 AM
MIME-Version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: base64
Content-Transfer-Encoding: base64
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: base64

DQoNCg0KDQoNClZpdmVrDQogICAgICBQbGVhc2Ugc2VlIGNvbW1lbnRzIGluIGxpbmUNCg0KDQoN
CiJWaXZlayBUb2t5IiA8dml2ZWt0b2t5QGNjcHUuY29tPkBpZXRmLm9yZyBvbiAwOC8wNS8yMDAz
IDA5OjQ3OjQzIEFNDQoNClNlbnQgYnk6ICAgIHNpZ3RyYW4tYWRtaW5AaWV0Zi5vcmcNCg0KDQpU
bzogICAgImthbWVzaCBrYXVsIiA8a2trX2thdWxAeWFob28uY29tPg0KY2M6ICAgIDxzaWd0cmFu
QGlldGYub3JnPg0KDQpTdWJqZWN0OiAgICBSRTogW1NpZ3RyYW5dIE0zVUEgOiBJUFNQIERFIGJl
aGF2aW91cg0KDQoNCkthbWVzaCwNCiAgUGxlYXNlIHNlZSBjb21tZW50cyBpbmxpbmUNCi0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBzaWd0cmFuLWFkbWluQGlldGYub3JnIFttYWls
dG86c2lndHJhbi1hZG1pbkBpZXRmLm9yZ11PbiBCZWhhbGYgT2YNCmthbWVzaCBrYXVsDQpTZW50
OiBTYXR1cmRheSwgQXVndXN0IDAyLCAyMDAzIDg6MjQgUE0NClRvOiBWaXZlayBUb2t5DQpDYzog
c2lndHJhbkBpZXRmLm9yZw0KU3ViamVjdDogUkU6IFtTaWd0cmFuXSBNM1VBIDogSVBTUCBERSBi
ZWhhdmlvdXINCg0KDQpIaSBWaXZlaywNCiAgICBJIGFyZ2VlIHdpdGggeW91IHRoYXQgaWYgd2Ug
aW50ZXJtaXggSVBTUCBTRSBhbmQNCkRFIG1vZGVscyB3ZSBjYW4gc3RhcnQgbG9hZHNoYXJpbmcg
dHJhZmZpYyBmb3IgQVMyDQphbW9uZyBJUFNQIEIgYW5kIElQU1AgQSBldmVuIHRob3VnaCBJUFNQ
IEIgaGFzIG5vdA0KcmVjZWl2ZWQgQVNQQUMgbWVzc2FnZSBmcm9tIElQU1AgYy5JdCB3b3VsZCBy
ZXN1bHQgaW4NCmludGVybWl4aW5nIG9mIHR3byBJUFNQIG1vZGVscy5Gb3Igc29tZSBtZXNzYWdl
cyBJUFNQDQpDIGhhcyB0byBiZWhhdmUgaW4gREUgbWFubmVyIGFuZCBmb3Igb3RoZXIgU0UNCmJl
aGF2aW91ciBpcyByZXF1aXJlZC5MZXRzIHRha2UgeW91ciBleGFtcGxlLiBPbg0KcmVjZWl2aW5n
IEFTUEFDIG1lc3NhZ2VzIGZyb20gSVBTUCBBIGFuZCBJUFNQIEIgZm9yDQpBUzEgSVBTUCBDIHVw
ZGF0ZXMgb25seSByZW1vdGUgSVBTUCdTIHN0YXRlcyBmb3IgQVMxDQpiZWhhdmluZyBpbiBERSBt
YW5uZXIud2hlbiBJUFNQIGMgc2VuZHMgQVNQQUMgZm9yIEFTMg0KdG8gSVBTUCBBIGFuZCByZWNl
aXZlcyBBQ0sgYmFjayB0aGVuIGFsc28gSVBTUCBDDQpjaGFuZ2VzIGl0cyBzdGF0ZSB0byBhY3Rp
dmUgZm9yIGxvY2FsIEFTMiBiZWhhdmluZyBpbg0KREUgbWFubmVyLk5vdyBhcyB5b3Ugc2FpZCBC
aS1kaXJlY3Rpb25hbCBkYXRhIGlzDQpmbG93aW5nIGZyb20gSVBTUCBDIGFuZCBJUFNQIEEgd2hl
cmUgYXMgc2luZ2xlDQpkaXJlY3Rpb24gdHJhZmZpYyBpcyBwb3NzaWJsZSBmcm9tIElQU1AgQyB0
byBJUFNQIEINCihmb3IgQVMyKS5Ob3cgYXNzdW1lIElQU1AgQSBzZW5kcyBBU1BJQSBtZXNzYWdl
IGZvcg0KQVMxIHRvIElQU1AgQyBpbiB0aGlzIGNhc2UgSVBTUCBjIG9uIHJlY2VpdmluZyBBU1BJ
QQ0KbWVzc2FnZSBoYXMgdG8gdXBkYXRlIHN0YXRlIG9mIHJlbW90ZSBJUFNQIEEgaW4gQVMxDQph
bmQgYWxzbyBzdGF0ZSBvZiBsb2NhbCBJUFNQIEMgaW4gbG9jYWwgQVMyIGJlaGF2aW5nDQppbiBT
RSBtYW5uZXIuDQoNCltWaXZla10NCiBZb3UgaGF2ZSBhIGdvb2QgcG9pbnQgYnV0IEkgZGlkIG5v
dCB1bmRlcnN0YW5kIHdoeSB3b3VsZCB3ZSBuZWVkIHRvIGNoYW5nZQ0KdGhlIHN0YXRlIG9mIElQ
U1AgQyBpbiB0aGlzIGNhc2UgKCB3aGVuIElQU1AgQSBzZW5kcyBBU1BJQSB0byBJUFNQIEMpLiBX
aGVuDQpJUFNQIEEgc2VuZHMgQVNQSUEgbWVzc2FnZSBmb3IgQVMxIHRvIElQU1AgQyB0aGVuIG9u
bHkgSVBTUCBBJ3Mgc3RhdGUgd2lsbA0KY2hhbmdlIGluIGxvY2FsIEFTMSBhbmQgdGhlIGNvcnJl
c3BvbmRpbmcgcmVtb3RlIEFTMSBvbiB0aGUgb3RoZXIgc2lkZS4gWW91DQphcmUgcmlnaHQgdGhh
dCBBUzEgd2lsbCBub3QgYmUgYWJsZSB0byByZWNlaXZlIHRyYWZmaWMgdGhyb3VnaCBJUFNQIEEg
LCBidXQNCnRoYXQgZG9lc25vdCByZXN0cmljdCBBUzEgdG8gc2VuZCB0cmFmZmljIGZyb20gSVBT
UCBBLg0KW0thbWVzaF0NCklQU1AgQSBpcyBpbmFjdGl2ZSAoaXQgaGFzIHNlbmQgQVNQSUEpIGZv
ciBBUzEgc28gaG93IGNhbiBpdCBzZW5kIGRhdGEgZm9yDQpBUzEuDQoNCk5vdGU6IEFTMSBpcyBz
dGlsbCBVUA0KYW5kIHJlYWR5IHRvIHByb2Nlc3MgZGF0YSBhbmQgc28gaXMgQVMyLiBJZiBBUzEg
d2FudHMgdG8gZ28gZG93biBhbmQgbm90DQpwcm9jZXNzIGRhdGEgYXQgYWxsIHRoZW4gaXQgc2hv
dWxkIHNlbnQgSW5hY3RpdmUgdGhyb3VnaCBib3RoIHRoZSBJUFNQcyAoDQpJUFNQIEEgYW5kIElQ
U1AgQikuDQpbS2FtZXNoXQ0KIElQU1AgQiBjYW504oCZdCBzZW5kIGRhdGEgZm9yIEFTMSB0byBJ
UFNQIEMgYmVjYXVzZSBJUFNQIEMgaGFzIG5vdCBzZW5kDQpBU1BBQyBtZXNzYWdlIHRvIGl0LlNv
IGl0IG1lYW5zIHRoYXQgQVMx4oCZcyBkYXRhIGNhbnQgcmVhY2ggSVBTUCBDIGJlY2F1c2UNCklQ
U1AgQSBpcyBpbmFjdGl2ZSBmb3IgQVMxIGFuZCBJUFNQIEIgaGFzIG5vdCByZWNlaXZlZCBBU1BB
QyBtZXNzYWdlIGZyb20NCklQU1AgQy4NCk5vdyB0aGUgcXVlc3Rpb24gYXJpc2VzIHRoYXQgd2hh
dCBzaG91bGQgSVBTUCBBIGRvIGlmIGl0DQpyZWNlaXZlcyBkYXRhIGZyb20gQVMxIHdoaWNoIGhh
cyBpbmFjdGl2YXRlZCBpdHNlbGYgZnJvbSBib3RoICB0aGUgSVBTUHMNCmFuZA0KaXMgbm93IHRv
dGFsbHkgdW5hYmxlIHRvIHJlY2VpdmUgREFUQSA/IC4uLiBmb2xsb3dpbmcgcG9pbnRzIHNob3Vs
ZCBiZQ0Kbm90ZWQNCjEuIElmIEFTMSBkb2Vzbid0IHdhbnQgdG8gcmVjZWl2ZSBkYXRhLCB3aHkg
d2UgY2FyZSBpZiB0aGUgZGF0YSBzZW50IGJ5IEFTMQ0Kd2VudCB0aHJvdWdoIGFsbCB0aGUgd2F5
IHRvIEFTMi4NCjIuIE5vdyB3ZSBrbm93IHRoYXQgQVMyIHdvbid0IGJlIGFibGUgdG8gc2VuZCBk
YXRhIHRvIEFTMSBhdGFsbCBzbyBpdCBjYW4NCnRha2UgcmVjb3ZlcnkgYW5kIERlLWFjdGl2YXRl
IGl0c2VsZiB0aHJvdWdoIElQU1AgQSAodG8gd2hpY2ggaXQgc2VudCBBU1ANCkFjdGl2ZSBhbmQg
Z290IEFjdGl2ZSBBY2suKQ0KDQpkb2VzIGl0IG1ha2Ugc2Vuc2UgPyBwbGVhc2UgY29tbWVudC4u
DQoNCltLYW1lc2hdDQogV2UgaGF2ZSB0byBjaGVjayB0aGUgc3RhdGUgb2YgbG9jYWwgSVBTUCBi
ZWZvcmUgc2VsZWN0aW5nIHJlbW90ZQ0KYXBwbGljYXRpb24gc2VydmVyIGZvciBkYXRhDQoNCg0K
SWYgSVBTUCBDIGRvZXMgbm90IGJvdGhlciBhYm91dCBsb2NhbA0Kc3RhdGUgdXBkYXRpb24gb24g
cmVjZWl2aW5nIEFTUElBIGZyb20gSVBTUCBBLCBJUFNQIEMNCndpbGwgY29udGludWUgdG8gc2Vu
ZCBkYXRhIG1lc3NhZ2VzIGZvciBBUzIgdG8gSVBTUCBCDQp3aXRob3V0IHJlY2VpdmluZyBhbnl0
aGluZyBmcm9tIG90aGVyIHNpZGUuIFRoaXMgd2lsbA0KcmVzdWx0IGluIHNpbmdsZSBkaXJlY3Rp
b24gdHJhZmZpYyBmcm9tIElQU1AgQyB0byBBUzENCndpdGhvdXQgdGhlIGtub3dsZWRnZSBvZiBJ
UFNQIEMuSWYgd2UgYXNzb2NpYXRlIEFTDQpzdGF0ZSB3aXRoIGxvY2FsIGFuZCBwZWVyIElQU1An
cyAoaW4geW91ciBleGFtcGxlDQpBUzIncyBzdGF0ZSB3aXRoIElQU1AgYyBhbmQgZWFjaCBwZWVy
IElQU1BBIGFuZCBJUFNQQiwNCkFTMidzIHN0YXRlIHdpdGggSVBTUCBDIGFuZCBlYWNoIHBlZXIg
SVBTUCdzKSBzaW5nbGUNCmRpcmVjdGlvbiB0cmFmZmljIGZsb3cgaXMgbm90IHBvc3NpYmxlLiBQ
bGVhc2UgY29tbWVudA0KDQpSZWdhcmRzDQpLYW1lc2gNCi0tLSBWaXZlayBUb2t5IDx2aXZla3Rv
a3lAY2NwdS5jb20+IHdyb3RlOg0KPiBIaSBLYW1lc2gsDQo+ICAgQWx0aG91Z2ggQVNQQUMgbWVz
c2FnZSBoYXMgbm90IGJlZW4gc2VudCB0byBJUFNQDQo+IEIsIGJ1dCB0aGUgbG9jYWwgQVMgaXMN
Cj4gc3RpbGwgYWN0aXZlIGFuZCBpcyBzZW5kaW5nIGFuZCByZWNlaXZpbmcgdHJhZmZpYw0KPiB0
aHJvdWdoIElQU1AgQS4gTm93IG9uIHRoZQ0KPiBvdGhlciBzaWRlIElQU1AgQSBhbmQgSVBTUCBC
IGFyZSBwYXJ0IG9mIHRoZSBzYW1lIEFTDQo+ICggQVMxICkuIFNvIGZvbGxvd2luZw0KPiBwb2lu
dHMgc2hvdWxkIGJlIG5vdGVkLg0KPg0KPiAxLiBCaS1kaXJlY3Rpb25hbCB0cmFmZmljIGJldHdl
ZW4gQVMxIGFuZCBBUzIgaXMNCj4gcG9zc2libGUNCj4gMi4gSVBTUCBCIGhhcyBhbHJlYWR5IHNl
bnQgQVNQQUMgYW5kIHJlY2VpdmVkIEFTUEFDDQo+IEFjaywgc28gaXQgaXMgcmVhZHkgdG8NCj4g
cmVjZWl2ZSB0cmFmZmljLg0KPg0KPiAgU28gd2h5IGRvbid0IHdlIGxvYWRzaGFyZSB0aGUgdHJh
ZmZpYyBhbW9uZyBJUFNQIEENCj4gYW5kIElQU1AgQiBhcyB0aGUNCj4gdHJhZmZpYyBpcyBhbnl3
YXkgZ29pbmcgdG8gZ2V0IHRvIHRoZSBzYW1lDQo+IGRlc3RpbmF0aW9uIGkuZS4gQVMxDQo+DQo+
IEluIHRoZSByZXZlcnNlIGRpcmVjdGlvbiBBUzEgY2FuIGNob29zZSBJUFNQIEEgdG8NCj4gc2Vu
ZCB0cmFmZmljIHRvd2FyZHMgQVMyLA0KPiBhcyBvbmx5IElQU1AgQSBoYXMgcmVjZWl2ZWQgQVNQ
QUMgZnJvbSBJUFNQIEMgKGZvcg0KPiBBUzIpDQo+DQo+IGNvbW1lbnRzPw0KPg0KPiAtVml2ZWsu
DQo+DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHNpZ3RyYW4tYWRtaW5A
aWV0Zi5vcmcNCj4gW21haWx0bzpzaWd0cmFuLWFkbWluQGlldGYub3JnXU9uIEJlaGFsZiBPZg0K
PiBrYWthdWxAaHNzLmhucy5jb20NCj4gU2VudDogRnJpZGF5LCBBdWd1c3QgMDEsIDIwMDMgMTox
NiBBTQ0KPiBUbzogVml2ZWsgVG9reQ0KPiBDYzogc2lndHJhbkBpZXRmLm9yZw0KPiBTdWJqZWN0
OiBSRTogW1NpZ3RyYW5dIE0zVUEgOiBJUFNQIERFIGJlaGF2aW91cg0KPg0KPg0KPg0KPg0KPg0K
Pg0KPiBWaXZlaywNCj4NCj4gSW4geW91ciBleGFtcGxlIGFsc28gSVBTUCBDIHdpbGwgc2VuZCBk
YXRhIGZvciBBUzENCj4gdG8gSVBTUCBBIG9ubHkuSSBkb250DQo+IHNlZSBhbnkgcmVhc29uIGZv
ciBJUFNQIEMgdG8gc2VuZCBkYXRhIHRvIElQU1AgQg0KPiBiZWNhdXNlIEFTUEFDIG1lc3NhZ2Ug
aXMNCj4gbm90IHNlbnQgdG8gSVBTUCBCLiBJIGRvbnQgc2VlIGFueSBwb3NzaWJpbGl0eSBvZg0K
PiBzaW5nbGUgZGlyZWN0aW9uIHRyYWZmaWMNCj4gZmxvdyBpbiB5b3VyIGV4YW1wbGUgYWxzby4N
Cj4NCj4gS2FtZXNoIEthdWwNCj4gd3d3Lmhzc3dvcmxkLmNvbQ0KPiBIdWdoZXMgU29mdHdhcmUg
U3lzdGVtcw0KPg0KPg0KPg0KPg0KPiAiVml2ZWsgVG9reSIgPHZpdmVrdG9reUBjY3B1LmNvbT4g
b24gMDgvMDEvMjAwMw0KPiAwMToyMzoxMSBQTQ0KPg0KPiBUbzogICAgS2FtZXNoIEthdWwvSFNT
QEhTUywgc2lndHJhbkBpZXRmLm9yZw0KPiBjYzoNCj4NCj4gU3ViamVjdDogICAgUkU6IFtTaWd0
cmFuXSBNM1VBIDogSVBTUCBERSBiZWhhdmlvdXINCj4NCj4NCj4gS2FtZXNoLA0KPg0KPiAgIFNp
bmdsZSBkaXJlY3Rpb24gdHJhZmZpYyB3aWxsIHN0aWxsIGJlIHBvc3NpYmxlLg0KPiBJZiB5b3Ug
bG9vayBhdCBteQ0KPiBleGFtcGxlIGNhcmVmdWxseSB5b3Ugd2lsbCBub3RpY2UgdGhhdCBpbiBj
YXNlIG9mIDMNCj4gSVBTUHMsIGl0IHdpbGwgYmUNCj4gcG9zc2libGUuIEl0IG1heSBiZSBmb3Ig
YSBzaG9ydCBkdXJhdGlvbiBvZiB0aW1lLiBJbg0KPiBteSBleGFtcGxlIGxvY2FsDQo+IEFTIGlz
IGFscmVhZHkgQWN0aXZlIGFzIGl0IHNlbnQgQVNQIEFjdGl2ZSBtZXNzYWdlDQo+IHRvIG9uZSBv
ZiB0aGUgcGVlcg0KPiBJUFNQcyAoIGFsc28gZ290IHRoZSBBQ0sgYmFjayApDQo+DQo+IHBsZWFz
ZSBnbyB0aHJvdWdoIHRoZSBleGFtcGxlIGFnYWluIC4uIHdhaXRpbmcgZm9yDQo+IGNvbW1lbnRz
ID8NCj4NCj4gVml2ZWsNCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+IEhpIFNvbWUgY29tbWVudHMg
YmVsb3cNCj4gPg0KPiA+ICBXaGVuIElQU1AgQiByZWNlaXZlcyBBU1BBQyBtZXNzYWdlIGZyb20g
SVBTUCBBDQo+IGZvciBBUzEgaXQgbWFya3MNCj4gcmVtb3RlDQo+ID4gSVBTUCBBIGFjdGl2ZSBm
b3IgcmVtb3RlIEFTMSBhbmQgc2VuZHMgQVNQQUMgYWNrDQo+IGJhY2sgZm9yIEFTMSB0bw0KPiBJ
UFNQIEEuTm93DQo+ID4gd2l0aCB0aGVzZSBtZXNzYWdlIGV4Y2hhbmdlcyBpdCBtZWFucyB0aGF0
IElQU1AgQQ0KPiBpcyByZWFkeSB0byByZWNlaXZlDQo+ID4gdHJhZmZpYyBmb3IgQVMxLkF0IHRo
aXMgcG9pbnQgb2YgdGltZSBJUFNQIEIgaGFzDQo+IG5vdCBleHByZXNzZWQgaXRzDQo+ID4gd2ls
bGluZ25lc3MgdG8gc2VuZCBkYXRhIGZvciBhbnkgQVMuSVBTUCBCICBjYW5ub3QNCj4gIHNlbmQg
YW55DQo+IGFwcGxpY2F0aW9uDQo+ID4gZGF0YSBiZWNhdXNlIGl0cyBsb2NhbCBhcHBsaWNhdGlv
bnMgYXJlIG5vdCBhY3RpdmUNCj4geWV0LlNvIHNpbmdsZQ0KPiBkaXJlY3Rpb24NCj4gPiB0cmFm
ZmljIGZsb3cgd2lsbCBuZXZlciBvY2N1ci5Ob3cgd2hlbiBJUFNQIEINCj4gc2VuZHMgQVNQQUMg
bWVzc2FnZQ0KPiBmb3IgQVMyDQo+ID4gdG8gSVBTUCBBIGFuZCBnZXRzIGJhY2sgQVNQQUMgYWNr
IGZvciBBUzIgaXQgd2lsbA0KPiBnaXZlIHJlc3VtZQ0KPiBpbmRpY2F0aW9uIHRvDQo+ID4gdXNl
ciBub3cuQVMxIGFuZCBBUzIgYXJlIGJhc2ljYWxseSBzYW1lIHR5cGUgb2YNCj4gTVRQMyB1c2Vy
cywgYW5kIHVzZXINCj4gdG8NCj4gPiB1c2VyIGNvbW11bmljYXRpb24gd2lsbCBvbmx5IHN0YXJ0
IGlmIGJvdGggdXNlcnMNCj4gYXJlIHJlYWR5IGFuZA0KPiBhY3RpdmUuDQo+ID4NCj4gPg0KPiA+
ICAgICArLS0tLS0tLS0tLS0rICAgICAgICAgICAgICArLS0tLS0tLS0tLS0rDQo+ID4gICAgIHwg
ICAgICAgICAgIHwgICAgICAgICAgICAgIHwgICAgICAgICAgIHwNCj4gPiAgICAgfCBJUFNQIEEg
ICAgfCAgICAgICAgICAgICAgfCBJUFNQIEIgICAgfA0KPiA+ICAgICB8ICAgICAgICAgICArLS0t
LS0tLS0tLS0tLS0rICAgICAgICAgICB8DQo+ID4gICAgIHwgICAgICAgICAgIHwgICAgICAgICAg
ICAgIHwgICAgICAgICAgIHwNCj4gPiAgICAgKy0tLS0tLS0tLS0tKyAgICAgICAgICAgICAgKy0t
LS0tLS0tLS0tKw0KPiA+DQo+ID4gICAgICAgICBBUzEgICAgICAgICAgICAgICAgICAgICAgICBB
UzINCj4gPg0KPiA+IEthbWVzaCBLYXVsDQo+ID4gd3d3Lmhzc3dvcmxkLmNvbQ0KPiA+IEh1Z2hl
cyBTb2Z0d2FyZSBTeXN0ZW1zDQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+ICJWSXZlayBU
b2t5IiA8dml2ZWt0b2t5QGNjcHUuY29tPkBpZXRmLm9yZyBvbg0KPiAwNy8zMS8yMDAzIDExOjE5
OjM5IFBNDQo+ID4NCj4gPiBTZW50IGJ5OiAgICBzaWd0cmFuLWFkbWluQGlldGYub3JnDQo+ID4N
Cj4gPg0KPiA+IFRvOiAgICAiVG9sZ2EgQXN2ZXJlbiIgPHRvbGdhX2FzdmVyZW5AeWFob28uY29t
PiwNCj4gPHNpZ3RyYW5AaWV0Zi5vcmc+DQo+ID4gY2M6DQo+ID4NCj4gPiBTdWJqZWN0OiAgICBS
RTogW1NpZ3RyYW5dIE0zVUEgOiBJUFNQIERFIGJlaGF2aW91cg0KPiA+DQo+ID4NCj4gPiBUb2xn
YSwNCj4gPg0KPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4gRnJvbTogc2lndHJh
bi1hZG1pbkBpZXRmLm9yZw0KPiBbbWFpbHRvOnNpZ3RyYW4tYWRtaW5AaWV0Zi5vcmddT24NCj4g
QmVoYWxmIE9mDQo+ID4gVG9sZ2EgQXN2ZXJlbg0KPiA+IFNlbnQ6IFRodXJzZGF5LCBKdWx5IDMx
LCAyMDAzIDEwOjE5IEFNDQo+ID4gVG86IHNpZ3RyYW5AaWV0Zi5vcmcNCj4gPiBTdWJqZWN0OiBS
RTogW1NpZ3RyYW5dIE0zVUEgOiBJUFNQIERFIGJlaGF2aW91cg0KPiA+DQo+ID4NCj4gPiBWaXZl
aywNCj4gPiAtLS0gVml2ZWsgVG9reSA8dml2ZWt0b2t5QGNjcHUuY29tPiB3cm90ZToNCj4gPiA+
IFBsZWFzZSBzZWUgbXkgY29tbWVudHMgaW5saW5lDQo+ID4gPg0KPiA+ID4gPiBTZWUgbXkgb3Bp
Z2lvbiBvbmxpbmUNCj4gPiA+ID4NCj4gPiA+ID4gPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t
LQ0KPiA+ID4gPiA+IEZyb206IFZpdmVrIFRva3kgW21haWx0bzp2aXZla3Rva3lAY2NwdS5jb21d
DQo+ID4gPiA+ID4gU2VudDogVGh1cnNkYXksIEp1bHkgMzEsIDIwMDMgMjo0MiBQTQ0KPiA+ID4g
PiA+IFRvOiBUb2xnYSBBc3ZlcmVuOyBzaWd0cmFuQGlldGYub3JnDQo+ID4gPiA+ID4gU3ViamVj
dDogUkU6IFtTaWd0cmFuXSBNM1VBIDogSVBTUCBERQ0KPiBiZWhhdmlvdXINCj4gPiA+ID4gPg0K
PiA+ID4gPiA+DQo+ID4gPiA+ID4gSGkgVG9sZ2EsDQo+ID4gPiA+ID4gICAiQWJvdmUgY2FzZSIg
bWVhbnMNCj4gPiA+ID4gPiAid2hlbiBBUzEgaGFzIGFjdGl2YXRlZCBpdHNlbGYgYnkgc2VuZGlu
Zw0KPiA+ID4gPiA+ICBBU1AgQWN0aXZlIGZyb20gYm90aCB0aGUgSVBTUHMgKEEgJiBCKSBidXQN
Cj4gPiA+ID4gPiAgQVMyIGhhcyBzZW50IEFTUCBBY3RpdmUganVzdCB0byBJUFNQX0EuIg0KPiA+
ID4gPiA+DQo+ID4gPiA+ID4gSW4gbXkgb3BpbmlvbiBJUFNQX0Mgc2hvdWxkIGxvYWRzaGFyZSB0
aGUNCj4gPiA+IHRyYWZmaWMNCj4gPiA+ID4gPiBhcyBpdCBoYXMgcmVjZWl2ZWQgQVNQIGFjdGl2
ZSBmcm9tIGJvdGggdGhlDQo+ID4gPiBJUFNQcw0KPiA+ID4gPiA+IHNvIEFTMSBpcyBhY2Nlc3Np
YmxlIHRocm91Z2ggYm90aCBvZiB0aGVzZS4NCj4gPiA+ID4gPiBIb3dldmVyLCBpdCBpcyB0aGUg
cmVzcG9uc2liaWxpdHkgb2YgQVMxIHRvDQo+ID4gPiByb3V0ZQ0KPiA+ID4gPiA+IGFsbCB0aGUg
dHJhZmZpYyB0b3dhcmRzIEFTMiB0aHJvdWdoIElQU1BfQS4NCj4gPiA+ID4NCj4gPiA+ID4gSWYg
SVBTUF9CIHJlY2VpdmUgc29tZSB0cmFmZmljIGZyb20gSVBTUF9DIEJVVA0KPiBubw0KPiA+ID4g
QVMgaXMgQUNUSVZFIGZvcg0KPiA+ID4gaXQgb24NCj4gPiA+ID4gSVBTUF9DIGNhbiBpdCByb3V0
ZSB0aGlzIHRyYWZmaWM/Pz8NCj4gPiA+ID4gQ0FOIGEgU0cgc2VuZCB0byBhIHNzNyBuZXR3b3Jr
IGEgbWVzc2FnZQ0KPiByZWNlaXZlDQo+ID4gPiBmcm9tIGFuIElOQUNUSVZFDQo+ID4gPiBBU1Ag
IQ0KPg0KPT09IG1lc3NhZ2UgdHJ1bmNhdGVkID09PQ0KDQoNCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCkRvIHlvdSBZYWhvbyE/DQpZYWhvbyEgQ2FsZW5kYXIgLSBGcmVlIG9u
bGluZSBjYWxlbmRhciB3aXRoIHN5bmMgdG8gT3V0bG9vayhUTSkuDQpodHRwOi8vY2FsZW5kYXIu
eWFob28uY29tDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQpTaWd0cmFuIG1haWxpbmcgbGlzdA0KU2lndHJhbkBpZXRmLm9yZw0KaHR0cHM6Ly93d3cx
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lndHJhbg0KDQoNCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpTaWd0cmFuIG1haWxpbmcgbGlzdA0KU2ln
dHJhbkBpZXRmLm9yZw0KIGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Np
Z3RyYW4NCg0KDQoNCg0KDQoiRElTQ0xBSU1FUjogVGhpcyBtZXNzYWdlIGlzIHByb3ByaWV0YXJ5
IHRvIEh1Z2hlcyBTb2Z0d2FyZSBTeXN0ZW1zIExpbWl0ZWQNCihIU1MpIGFuZCBpcyBpbnRlbmRl
ZCBzb2xlbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgdG8gd2hvbSBpdCBpcw0KYWRk
cmVzc2VkLiBJdCBtYXkgY29udGFpbiAgcHJpdmlsZWdlZCBvciBjb25maWRlbnRpYWwgaW5mb3Jt
YXRpb24gYW5kDQpzaG91bGQgbm90IGJlIGNpcmN1bGF0ZWQgb3IgdXNlZCBmb3IgYW55IHB1cnBv
c2Ugb3RoZXIgdGhhbiBmb3Igd2hhdCBpdCBpcw0KaW50ZW5kZWQuIElmIHlvdSBoYXZlIHJlY2Vp
dmVkIHRoaXMgbWVzc2FnZSBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUNCm9yaWdpbmF0b3Ig
aW1tZWRpYXRlbHkuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsIHlvdSBh
cmUNCm5vdGlmaWVkIHRoYXQgeW91IGFyZSBzdHJpY3RseSBwcm9oaWJpdGVkIGZyb20gdXNpbmcs
IGNvcHlpbmcsIGFsdGVyaW5nLCBvcg0KZGlzY2xvc2luZyB0aGUgY29udGVudHMgb2YgdGhpcyBt
ZXNzYWdlLiBIU1MgYWNjZXB0cyBubyByZXNwb25zaWJpbGl0eSBmb3INCmxvc3Mgb3IgZGFtYWdl
IGFyaXNpbmcgZnJvbSB0aGUgdXNlIG9mIHRoZSBpbmZvcm1hdGlvbiB0cmFuc21pdHRlZCBieSB0
aGlzDQplbWFpbCBpbmNsdWRpbmcgZGFtYWdlIGZyb20gdmlydXMuIg==



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



From exim@www1.ietf.org  Thu Aug  7 00:31:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17618
	for <sigtran-archive@odin.ietf.org>; Thu, 7 Aug 2003 00:31:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kcQY-0000se-Gz
	for sigtran-archive@odin.ietf.org; Thu, 07 Aug 2003 00:31:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h774V2JF003380
	for sigtran-archive@odin.ietf.org; Thu, 7 Aug 2003 00:31:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kcQY-0000rp-0p; Thu, 07 Aug 2003 00:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kcPh-0000qv-TG
	for sigtran@optimus.ietf.org; Thu, 07 Aug 2003 00:30:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17560
	for <sigtran@ietf.org>; Thu, 7 Aug 2003 00:30:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kcPf-0002SS-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 00:30:07 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kcPe-0002SP-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 00:30:06 -0400
Received: from [172.16.2.14] (helo=hewlettyf9yyzb)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19kcPb-000764-Gu; Wed, 06 Aug 2003 21:30:03 -0700
From: "Vivek Toky" <vivektoky@ccpu.com>
To: <kakaul@hss.hns.com>
Cc: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
Date: Wed, 6 Aug 2003 21:30:09 -0700
Message-ID: <FHEPLGHNCJCJADFMFBGFCEMFCBAA.vivektoky@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <OF453B9C5C.69D37498-ON65256D7B.0014AE62@hss.hns.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable


Kamesh,

  See my comments Inline..

-----Original Message-----
From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
Sent: Wednesday, August 06, 2003 8:47 PM
To: vivektoky@ccpu.com
Cc: sigtran@ietf.org
Subject: [Spam] RE: [Sigtran] M3UA : IPSP DE behaviour







Vivek
      Please see comments in line



"Vivek Toky" <vivektoky@ccpu.com>@ietf.org on 08/05/2003 09:47:43 AM

Sent by:    sigtran-admin@ietf.org


To:    "kamesh kaul" <kkk_kaul@yahoo.com>
cc:    <sigtran@ietf.org>

Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour


Kamesh,
  Please see comments inline
-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
kamesh kaul
Sent: Saturday, August 02, 2003 8:24 PM
To: Vivek Toky
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour


Hi Vivek,
    I argee with you that if we intermix IPSP SE and
DE models we can start loadsharing traffic for AS2
among IPSP B and IPSP A even though IPSP B has not
received ASPAC message from IPSP c.It would result in
intermixing of two IPSP models.For some messages IPSP
C has to behave in DE manner and for other SE
behaviour is required.Lets take your example. On
receiving ASPAC messages from IPSP A and IPSP B for
AS1 IPSP C updates only remote IPSP'S states for AS1
behaving in DE manner.when IPSP c sends ASPAC for AS2
to IPSP A and receives ACK back then also IPSP C
changes its state to active for local AS2 behaving in
DE manner.Now as you said Bi-directional data is
flowing from IPSP C and IPSP A where as single
direction traffic is possible from IPSP C to IPSP B
(for AS2).Now assume IPSP A sends ASPIA message for
AS1 to IPSP C in this case IPSP c on receiving ASPIA
message has to update state of remote IPSP A in AS1
and also state of local IPSP C in local AS2 behaving
in SE manner.

[Vivek]
 You have a good point but I did not understand why would we need to =
change
the state of IPSP C in this case ( when IPSP A sends ASPIA to IPSP C). =
When
IPSP A sends ASPIA message for AS1 to IPSP C then only IPSP A's state =
will
change in local AS1 and the corresponding remote AS1 on the other side. =
You
are right that AS1 will not be able to receive traffic through IPSP A , =
but
that doesnot restrict AS1 to send traffic from IPSP A.
[Kamesh]
IPSP A is inactive (it has send ASPIA) for AS1 so how can it send data =
for
AS1.
****Vivek*****
That is what I am trying to say, IPSP A is inactive to receive data. It =
can still send data because remote destination is still active to =
receive data through  IPSP A
If sending an Active message means it will be able to send and receive =
data then an Active Ack from other would have been suffcient to tell =
IPSP A that it can start sending data as well. But it did not happen.. =
IPSP C sent an explicit Active message to indicate that its ready to =
receive data so IPSP C is the one who will indicate that now it is not =
going to receive data. IPSP A does not need to stop sending data to IPSP =
C just because it send ASPIA message.
**************

Note: AS1 is still UP
and ready to process data and so is AS2. If AS1 wants to go down and not
process data at all then it should sent Inactive through both the IPSPs =
(
IPSP A and IPSP B).
[Kamesh]
 IPSP B cant=E2=80=99t send data for AS1 to IPSP C because IPSP C has =
not send
ASPAC message to it.So it means that AS1=E2=80=99s data cant reach IPSP =
C because
IPSP A is inactive for AS1 and IPSP B has not received ASPAC message =
from
IPSP C.
Now the question arises that what should IPSP A do if it
receives data from AS1 which has inactivated itself from both  the IPSPs
and
is now totally unable to receive DATA ? ... following points should be
noted
1. If AS1 doesn't want to receive data, why we care if the data sent by =
AS1
went through all the way to AS2.
2. Now we know that AS2 won't be able to send data to AS1 atall so it =
can
take recovery and De-activate itself through IPSP A (to which it sent =
ASP
Active and got Active Ack.)

does it make sense ? please comment..

[Kamesh]
 We have to check the state of local IPSP before selecting remote
application server for data


If IPSP C does not bother about local
state updation on receiving ASPIA from IPSP A, IPSP C
will continue to send data messages for AS2 to IPSP B
without receiving anything from other side. This will
result in single direction traffic from IPSP C to AS1
without the knowledge of IPSP C.If we associate AS
state with local and peer IPSP's (in your example
AS2's state with IPSP c and each peer IPSPA and IPSPB,
AS2's state with IPSP C and each peer IPSP's) single
direction traffic flow is not possible. Please comment

Regards
Kamesh
--- Vivek Toky <vivektoky@ccpu.com> wrote:
> Hi Kamesh,
>   Although ASPAC message has not been sent to IPSP
> B, but the local AS is
> still active and is sending and receiving traffic
> through IPSP A. Now on the
> other side IPSP A and IPSP B are part of the same AS
> ( AS1 ). So following
> points should be noted.
>
> 1. Bi-directional traffic between AS1 and AS2 is
> possible
> 2. IPSP B has already sent ASPAC and received ASPAC
> Ack, so it is ready to
> receive traffic.
>
>  So why don't we loadshare the traffic among IPSP A
> and IPSP B as the
> traffic is anyway going to get to the same
> destination i.e. AS1
>
> In the reverse direction AS1 can choose IPSP A to
> send traffic towards AS2,
> as only IPSP A has received ASPAC from IPSP C (for
> AS2)
>
> comments?
>
> -Vivek.
>
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> kakaul@hss.hns.com
> Sent: Friday, August 01, 2003 1:16 AM
> To: Vivek Toky
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
>
>
>
>
> Vivek,
>
> In your example also IPSP C will send data for AS1
> to IPSP A only.I dont
> see any reason for IPSP C to send data to IPSP B
> because ASPAC message is
> not sent to IPSP B. I dont see any possibility of
> single direction traffic
> flow in your example also.
>
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>
>
>
>
> "Vivek Toky" <vivektoky@ccpu.com> on 08/01/2003
> 01:23:11 PM
>
> To:    Kamesh Kaul/HSS@HSS, sigtran@ietf.org
> cc:
>
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
> Kamesh,
>
>   Single direction traffic will still be possible.
> If you look at my
> example carefully you will notice that in case of 3
> IPSPs, it will be
> possible. It may be for a short duration of time. In
> my example local
> AS is already Active as it sent ASP Active message
> to one of the peer
> IPSPs ( also got the ACK back )
>
> please go through the example again .. waiting for
> comments ?
>
> Vivek
> >
> >
> >
> >
> > Hi Some comments below
> >
> >  When IPSP B receives ASPAC message from IPSP A
> for AS1 it marks
> remote
> > IPSP A active for remote AS1 and sends ASPAC ack
> back for AS1 to
> IPSP A.Now
> > with these message exchanges it means that IPSP A
> is ready to receive
> > traffic for AS1.At this point of time IPSP B has
> not expressed its
> > willingness to send data for any AS.IPSP B  cannot
>  send any
> application
> > data because its local applications are not active
> yet.So single
> direction
> > traffic flow will never occur.Now when IPSP B
> sends ASPAC message
> for AS2
> > to IPSP A and gets back ASPAC ack for AS2 it will
> give resume
> indication to
> > user now.AS1 and AS2 are basically same type of
> MTP3 users, and user
> to
> > user communication will only start if both users
> are ready and
> active.
> >
> >
> >     +-----------+              +-----------+
> >     |           |              |           |
> >     | IPSP A    |              | IPSP B    |
> >     |           +--------------+           |
> >     |           |              |           |
> >     +-----------+              +-----------+
> >
> >         AS1                        AS2
> >
> > Kamesh Kaul
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> >
> >
> >
> > "VIvek Toky" <vivektoky@ccpu.com>@ietf.org on
> 07/31/2003 11:19:39 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    "Tolga Asveren" <tolga_asveren@yahoo.com>,
> <sigtran@ietf.org>
> > cc:
> >
> > Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> >
> >
> > Tolga,
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On
> Behalf Of
> > Tolga Asveren
> > Sent: Thursday, July 31, 2003 10:19 AM
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> >
> >
> > Vivek,
> > --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > > Please see my comments inline
> > >
> > > > See my opigion online
> > > >
> > > > > -----Original Message-----
> > > > > From: Vivek Toky [mailto:vivektoky@ccpu.com]
> > > > > Sent: Thursday, July 31, 2003 2:42 PM
> > > > > To: Tolga Asveren; sigtran@ietf.org
> > > > > Subject: RE: [Sigtran] M3UA : IPSP DE
> behaviour
> > > > >
> > > > >
> > > > > Hi Tolga,
> > > > >   "Above case" means
> > > > > "when AS1 has activated itself by sending
> > > > >  ASP Active from both the IPSPs (A & B) but
> > > > >  AS2 has sent ASP Active just to IPSP_A."
> > > > >
> > > > > In my opinion IPSP_C should loadshare the
> > > traffic
> > > > > as it has received ASP active from both the
> > > IPSPs
> > > > > so AS1 is accessible through both of these.
> > > > > However, it is the responsibility of AS1 to
> > > route
> > > > > all the traffic towards AS2 through IPSP_A.
> > > >
> > > > If IPSP_B receive some traffic from IPSP_C BUT
> no
> > > AS is ACTIVE for
> > > it on
> > > > IPSP_C can it route this traffic???
> > > > CAN a SG send to a ss7 network a message
> receive
> > > from an INACTIVE
> > > ASP !
>
=3D=3D=3D message truncated =3D=3D=3D


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

_______________________________________________
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





"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
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From exim@www1.ietf.org  Thu Aug  7 02:15:34 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01323
	for <sigtran-archive@odin.ietf.org>; Thu, 7 Aug 2003 02:15:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ke3J-0005VL-Bz
	for sigtran-archive@odin.ietf.org; Thu, 07 Aug 2003 02:15:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h776F9Bo021136
	for sigtran-archive@odin.ietf.org; Thu, 7 Aug 2003 02:15:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ke3C-0005U7-Ex; Thu, 07 Aug 2003 02:15:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ke2J-0005OH-9U
	for sigtran@optimus.ietf.org; Thu, 07 Aug 2003 02:14:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01184
	for <sigtran@ietf.org>; Thu, 7 Aug 2003 02:14:01 -0400 (EDT)
From: agurmukhani@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ke2F-000369-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 02:14:03 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ke2E-00035N-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 02:14:02 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5] (may be forged))
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h776Ajw18913;
	Thu, 7 Aug 2003 11:40:45 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h776DFr18638;
	Thu, 7 Aug 2003 11:43:20 +0530 (IST)
Subject: Re: [Sigtran] SUA - RC in CLDT
To: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
Cc: sigtran@ietf.org
Date: Thu, 7 Aug 2003 11:36:20 +0530
Message-ID: <OFBE8A24CF.0336D205-ON65256D7B.001F00F6@hss.hns.com>
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 07/08/2003
 11:36:24 AM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>





Hi Valerie

 In M3UA  ,RC  is  conditional so that if an association is serving
multiple Application servers the RC parameter can be used to identify which
AS the data coming on the association is meant for. This parameter was
specifically made semi-optional/conditional from optional.

Also though in ASPAC the parameter is optional but this is only when the
association is catering to only a single AS. And  the draft also mentions
in the Asp Active procedures that if the ASP is serving traffic for
multiple Application servers across common SCTP association, then it should
include list of Routing context.

So IMO you are right that RC can be made conditional from mandatory in SUA
data messages also.

But I am not able to understand your last point. If there is static
configuration and the association is serving single AS, it will insert  the
RC that was statically configured. Please comment.

Thanks and Regards
Anjali
www.hssworld.com
Hughes Software Systems





"Valerie Gastaud" <valerie.gastaud@ulticom.com>@ietf.org on 08/06/2003
07:03:59 PM

Sent by:    sigtran-admin@ietf.org


To:    "Sigtran" <sigtran@ietf.org>
cc:

Subject:    [Sigtran] SUA - RC in CLDT



Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2 messages)?
This is not consistent with M3UA and this is not consistent with the SUA
ASPAC message in which the RC is optional.
In case of static provisioning of RK, if an SGP receives an ASPAC w/o RC,
it
won't be able to insert the RC in the CLDT.

Valerie



_______________________________________________
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



From exim@www1.ietf.org  Thu Aug  7 04:24:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04063
	for <sigtran-archive@odin.ietf.org>; Thu, 7 Aug 2003 04:24:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kg46-0002IV-9I
	for sigtran-archive@odin.ietf.org; Thu, 07 Aug 2003 04:24:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h778O62J008784
	for sigtran-archive@odin.ietf.org; Thu, 7 Aug 2003 04:24:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kg44-0002Ge-4x; Thu, 07 Aug 2003 04:24:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kf23-0008T8-L4
	for sigtran@optimus.ietf.org; Thu, 07 Aug 2003 03:17:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03046
	for <sigtran@ietf.org>; Thu, 7 Aug 2003 03:17:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kf21-0003ft-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 03:17:53 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[Wpzh2Iey+eBe2wO+2ZNvbLQq7WDJbMQq])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kf20-0003fq-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 03:17:52 -0400
Received: from ns.pigworks.openss7.net (IDENT:v3ilTEbGoakgmtwsapl5RzTAL6bP6M3c@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h777HrE25085;
	Thu, 7 Aug 2003 01:17:53 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h777HqB08112;
	Thu, 7 Aug 2003 01:17:52 -0600
Date: Thu, 7 Aug 2003 01:17:52 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Valerie Gastaud <valerie.gastaud@ulticom.com>
Cc: Sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA - RC in CLDT
Message-ID: <20030807011752.G7039@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Valerie Gastaud <valerie.gastaud@ulticom.com>,
	Sigtran <sigtran@ietf.org>
References: <NDBBIHAOCKGAMIKNLALOIENGDOAA.valerie.gastaud@ulticom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <NDBBIHAOCKGAMIKNLALOIENGDOAA.valerie.gastaud@ulticom.com>; from valerie.gastaud@ulticom.com on Wed, Aug 06, 2003 at 03:33:59PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Valerie,

SUA had RC mandatory in all messages.  This was just a cut and paste error
from "common UA procedures".  The SUA draft should be corrected to make RC
mandatory in ASPAC.  Although it may make some sense to M2UA and even M3UA
to have RC optional in ASPAC, it makes little sense in SUA.  This is why
RC is mandatory in all messages in SUA.

--brian

Valerie Gastaud wrote:                                                             (Wed, 06 Aug 2003 15:33:59)
> 
> Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2 messages)?
> This is not consistent with M3UA and this is not consistent with the SUA
> ASPAC message in which the RC is optional.
> In case of static provisioning of RK, if an SGP receives an ASPAC w/o RC, it
> won't be able to insert the RC in the CLDT.
> 
> Valerie
> 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Thu Aug  7 04:24:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04107
	for <sigtran-archive@odin.ietf.org>; Thu, 7 Aug 2003 04:24:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kg4A-0002Ko-Vb
	for sigtran-archive@odin.ietf.org; Thu, 07 Aug 2003 04:24:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h778OAJH008958
	for sigtran-archive@odin.ietf.org; Thu, 7 Aug 2003 04:24:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kg4A-0002KO-P5; Thu, 07 Aug 2003 04:24:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kftb-00025i-BX
	for sigtran@optimus.ietf.org; Thu, 07 Aug 2003 04:13:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03841
	for <sigtran@ietf.org>; Thu, 7 Aug 2003 04:13:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kftY-0003t7-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 04:13:12 -0400
Received: from angelica.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kftX-0003sw-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 04:13:12 -0400
Received: from navy.fr.ulticom.com (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with ESMTP id EAA13943;
	Thu, 7 Aug 2003 04:12:37 -0400 (EDT)
Received: from PCGASTAUDL (pc-gastaud-l.fr.ulticom.com [172.26.32.88])
	by navy.fr.ulticom.com (8.11.6+Sun/8.11.6) with SMTP id h7788ZJ24141;
	Thu, 7 Aug 2003 10:08:36 +0200 (MEST)
From: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
To: <agurmukhani@hss.hns.com>
Cc: "Sigtran" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA - RC in CLDT
Date: Thu, 7 Aug 2003 10:13:18 +0200
Message-ID: <NDBBIHAOCKGAMIKNLALOGENLDOAA.valerie.gastaud@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <OFBE8A24CF.0336D205-ON65256D7B.001F00F6@hss.hns.com>
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi Anjali,

Since inserting the RC parameter in the messages is not necessary when the
association is serving single AS, why would it be mandatory to statically
configure a RC in this case?
Valerie

-----Original Message-----
From: agurmukhani@hss.hns.com [mailto:agurmukhani@hss.hns.com]
Sent: jeudi 7 aout 2003 08:06
To: Valerie Gastaud
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] SUA - RC in CLDT






Hi Valerie

 In M3UA  ,RC  is  conditional so that if an association is serving
multiple Application servers the RC parameter can be used to identify which
AS the data coming on the association is meant for. This parameter was
specifically made semi-optional/conditional from optional.

Also though in ASPAC the parameter is optional but this is only when the
association is catering to only a single AS. And  the draft also mentions
in the Asp Active procedures that if the ASP is serving traffic for
multiple Application servers across common SCTP association, then it should
include list of Routing context.

So IMO you are right that RC can be made conditional from mandatory in SUA
data messages also.

But I am not able to understand your last point. If there is static
configuration and the association is serving single AS, it will insert  the
RC that was statically configured. Please comment.

Thanks and Regards
Anjali
www.hssworld.com
Hughes Software Systems





"Valerie Gastaud" <valerie.gastaud@ulticom.com>@ietf.org on 08/06/2003
07:03:59 PM

Sent by:    sigtran-admin@ietf.org


To:    "Sigtran" <sigtran@ietf.org>
cc:

Subject:    [Sigtran] SUA - RC in CLDT



Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2 messages)?
This is not consistent with M3UA and this is not consistent with the SUA
ASPAC message in which the RC is optional.
In case of static provisioning of RK, if an SGP receives an ASPAC w/o RC,
it
won't be able to insert the RC in the CLDT.

Valerie



_______________________________________________
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



From exim@www1.ietf.org  Thu Aug  7 04:29:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04403
	for <sigtran-archive@odin.ietf.org>; Thu, 7 Aug 2003 04:29:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kg8s-0002l4-1k
	for sigtran-archive@odin.ietf.org; Thu, 07 Aug 2003 04:29:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h778T20x010579
	for sigtran-archive@odin.ietf.org; Thu, 7 Aug 2003 04:29:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kg8r-0002kC-5k; Thu, 07 Aug 2003 04:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kg81-0002j3-IO
	for sigtran@optimus.ietf.org; Thu, 07 Aug 2003 04:28:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04319
	for <sigtran@ietf.org>; Thu, 7 Aug 2003 04:28:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kg7y-00041S-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 04:28:06 -0400
Received: from angelica.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kg7y-000417-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 04:28:06 -0400
Received: from navy.fr.ulticom.com (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with ESMTP id EAA15610;
	Thu, 7 Aug 2003 04:27:36 -0400 (EDT)
Received: from PCGASTAUDL (pc-gastaud-l.fr.ulticom.com [172.26.32.88])
	by navy.fr.ulticom.com (8.11.6+Sun/8.11.6) with SMTP id h778NYJ25001;
	Thu, 7 Aug 2003 10:23:34 +0200 (MEST)
From: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
To: <bidulock@openss7.org>
Cc: "Sigtran" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA - RC in CLDT
Date: Thu, 7 Aug 2003 10:28:17 +0200
Message-ID: <NDBBIHAOCKGAMIKNLALOOENLDOAA.valerie.gastaud@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <20030807011752.G7039@openss7.org>
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Brian,

Why does it make less sense with SUA than M3UA?
And even if it makes little sense, assuming this is not no sense, it's
always better to have consistency between the UAs, this avoids people asking
the same question in the future.

Valerie

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: jeudi 7 aout 2003 09:18
To: Valerie Gastaud
Cc: Sigtran
Subject: Re: [Sigtran] SUA - RC in CLDT


Valerie,

SUA had RC mandatory in all messages.  This was just a cut and paste error
from "common UA procedures".  The SUA draft should be corrected to make RC
mandatory in ASPAC.  Although it may make some sense to M2UA and even M3UA
to have RC optional in ASPAC, it makes little sense in SUA.  This is why
RC is mandatory in all messages in SUA.

--brian

Valerie Gastaud wrote:
(Wed, 06 Aug 2003 15:33:59)
>
> Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2
messages)?
> This is not consistent with M3UA and this is not consistent with the SUA
> ASPAC message in which the RC is optional.
> In case of static provisioning of RK, if an SGP receives an ASPAC w/o RC,
it
> won't be able to insert the RC in the CLDT.
>
> Valerie
>
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


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



From exim@www1.ietf.org  Thu Aug  7 05:11:51 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04064
	for <sigtran-archive@odin.ietf.org>; Thu, 7 Aug 2003 04:24:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kg46-0002IK-8p
	for sigtran-archive@odin.ietf.org; Thu, 07 Aug 2003 04:24:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h778O6Ww008783
	for sigtran-archive@odin.ietf.org; Thu, 7 Aug 2003 04:24:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kg43-0002GJ-05; Thu, 07 Aug 2003 04:24:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kewR-0008N6-97
	for sigtran@optimus.ietf.org; Thu, 07 Aug 2003 03:12:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02993
	for <sigtran@ietf.org>; Thu, 7 Aug 2003 03:12:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kewP-0003dl-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 03:12:05 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[R2qRq67gqnAJTL4FNGIbSypUn99tHN/r])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kewO-0003di-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 03:12:04 -0400
Received: from ns.pigworks.openss7.net (IDENT:G9xBAuIEiN6/gp00aLttsSKjO/kl5oXQ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h777C4E25019;
	Thu, 7 Aug 2003 01:12:04 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h777C3g08088;
	Thu, 7 Aug 2003 01:12:03 -0600
Date: Thu, 7 Aug 2003 01:12:03 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ygahlaut@hss.hns.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] SUA -- Source Address in the CORE message
Message-ID: <20030807011203.F7039@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ygahlaut@hss.hns.com, sigtran@ietf.org
References: <OFDAE64171.DFB3F976-ON65256D7A.0037A2D5@hss.hns.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFDAE64171.DFB3F976-ON65256D7A.0037A2D5@hss.hns.com>; from ygahlaut@hss.hns.com on Wed, Aug 06, 2003 at 05:54:39PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

ygahlaut,

ygahlaut@hss.hns.com wrote:                                                       (Wed, 06 Aug 2003 17:54:39)
> 
> 
> 
> 
> Hi,
>         According to the SUA draft Source Address field in CORE message is
> optional.
> Consider the following sequence
> 
> SGP sends a CORE message to ASP without Source Address.
> ASP sends back the COAK to same SGP without Destination Address.
> Connection established
> :
> :
>  Data transfer takes place
> :
> :
> SGP sends a DUNA message
> :

It is not the role of the ASP to perform SCCP CO state machine functions.
These are performed at the SGP.  It is the SGP's resposibility to, as well as
sending the DUNA, send RELRE (N-DISCONNNECT-Indication) to the ASP with the
appropriate cause (in this case, Subsystem Failure, SCCP Failure, or MTP
Failure).

: SGP sends RELRE

> :  <----- Point 1
> :
> ASP Send Connection Oriented Data

It would be typical to discard CO data after sending RELRE (at least for
a short while), to give the AS time to respond to the N-DISCONNECT-Indication
and stop sending data.

--brian

Please remove your DISCLAIMER below from future mailings.

> :
> :  <---- Point 2
> :
> 
> 
> Now  queries
> 1> on Point 1 should the connection be terminated with the destination from
> which DUNA message is received and no CODT is allowed
> If Yes.... How ?  considering the case where ASP did not receive the Source
> Address in CORE message. how can the connection be identified?  because ASP
> does not know the peer's address for this Connection.
> 
> Should the Connection be identified using RC  but then there may be a case
> in which there is no RC in DUNA message (RC is optional in DUNA message) ?
> 
> 2> on point 2 should this CODT message be allowed to reach SGP ?
>    should this message be  routed to another SGP(if there) ?
> 
> 
> Please correct me if I am missing something
> 
> Regards
> Yogesh
> www.hssworld.com
> Hughes Software Systems
> 
> 
> "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
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Thu Aug  7 06:19:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06544
	for <sigtran-archive@odin.ietf.org>; Thu, 7 Aug 2003 06:19:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19khrL-0006KQ-6M
	for sigtran-archive@odin.ietf.org; Thu, 07 Aug 2003 06:19:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h77AJ3w7024320
	for sigtran-archive@odin.ietf.org; Thu, 7 Aug 2003 06:19:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19khrJ-0006K2-5C; Thu, 07 Aug 2003 06:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19khrA-0006Jr-Ib
	for sigtran@optimus.ietf.org; Thu, 07 Aug 2003 06:18:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06521
	for <sigtran@ietf.org>; Thu, 7 Aug 2003 06:18:45 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19khr6-0004fl-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 06:18:48 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19khr4-0004f3-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 06:18:47 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5] (may be forged))
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h77AFdw10406;
	Thu, 7 Aug 2003 15:45:39 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h77AI1822009;
	Thu, 7 Aug 2003 15:48:12 +0530 (IST)
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
To: "Vivek Toky" <vivektoky@ccpu.com>
Cc: <sigtran@ietf.org>
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF30F6A559.B44F57FF-ON65256D7B.0037743C@hss.hns.com>
Date: Thu, 7 Aug 2003 15:42:25 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 07/08/2003
 03:41:15 PM
MIME-Version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: base64
Content-Transfer-Encoding: base64
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: base64

DQoNCg0KDQpIaSBWaXZlaywNCiAgIFBsZWFzZSBnbyB0aHJvdWdoIHRoZSBzZWN0aW9uIGF0dGFj
aGVkIGZyb20gUkZDIDMzMzINCiAgIDQuMy40LjQuMSBJUFNQIENvbnNpZGVyYXRpb25zIChBU1Ag
SW5hY3RpdmUpDQoNCiAgIEFuIElQU1AgbWF5IGJlIGNvbnNpZGVyZWQgaW4gdGhlIEFTUC1JTkFD
VElWRSBzdGF0ZSBieSBhIHJlbW90ZSBJUFNQDQogICBhZnRlciBhbiBBU1AgSW5hY3RpdmUgb3Ig
QVNQIEluYWN0aXZlIEFjayBtZXNzYWdlIGhhcyBiZWVuIHJlY2VpdmVkDQogICBmcm9tIGl0Lg0K
DQogICBBbHRlcm5hdGl2ZWx5LCBhbiBpbnRlcmNoYW5nZSBvZiBBU1AgSW5hY3RpdmUgbWVzc2Fn
ZXMgZnJvbSBlYWNoIGVuZA0KICAgY2FuIGJlIHBlcmZvcm1lZC4gVGhpcyBvcHRpb24gZm9sbG93
cyB0aGUgQVNQIHN0YXRlIHRyYW5zaXRpb24NCiAgIGRpYWdyYW0gYW5kIGdpdmVzIHRoZSBhZGRp
dGlvbmFsIGFkdmFudGFnZSBvZiBzZWxlY3RpbmcgYSBwYXJ0aWN1bGFyDQogICBBUyB0byBiZSBk
ZWFjdGl2YXRlZCBmcm9tIGVhY2ggZW5kLiBJdCBpcyBlc3BlY2lhbGx5IHVzZWZ1bCB3aGVuIGFu
DQogICBJUFNQIGlzIHNlcnZpbmcgbW9yZSB0aGFuIG9uZSBBUy4gSXQgd291bGQgbmVlZCBmb3Vy
IG1lc3NhZ2VzIGZvcg0KICAgY29tcGxldGlvbi4NCg0KICAgSU1PIElQU1AgQSBpbiB5b3VyIGV4
YW1wbGUgYWZ0ZXIgc2VuZGluZyBBU1BJQSBtZXNzYWdlIGZvciBBUzEgd291bGQNCiAgIG5vdCBi
ZSBhYmxlIHRvIHNlbmQgb3IgcmVjZWl2ZSB0cmFmZmljIGZyb20gb3IgZm9yIEFTMS4NCg0KUmVn
YXJkcw0KS2FtZXNoIEthdWwNCnd3dy5oc3N3b3JsZC5jb20NCkh1Z2hlcyBTb2Z0d2FyZSBTeXN0
ZW1zDQoNCg0KDQoNCg0KDQoNCg0KIlZpdmVrIFRva3kiIDx2aXZla3Rva3lAY2NwdS5jb20+QGll
dGYub3JnIG9uIDA4LzA3LzIwMDMgMTA6MDA6MDkgQU0NCg0KU2VudCBieTogICAgc2lndHJhbi1h
ZG1pbkBpZXRmLm9yZw0KDQoNClRvOiAgICBLYW1lc2ggS2F1bC9IU1NASFNTDQpjYzogICAgPHNp
Z3RyYW5AaWV0Zi5vcmc+DQoNClN1YmplY3Q6ICAgIFJFOiBbU2lndHJhbl0gTTNVQSA6IElQU1Ag
REUgYmVoYXZpb3VyDQoNCg0KDQpLYW1lc2gsDQoNCiAgU2VlIG15IGNvbW1lbnRzIElubGluZS4u
DQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBrYWthdWxAaHNzLmhucy5jb20g
W21haWx0bzprYWthdWxAaHNzLmhucy5jb21dDQpTZW50OiBXZWRuZXNkYXksIEF1Z3VzdCAwNiwg
MjAwMyA4OjQ3IFBNDQpUbzogdml2ZWt0b2t5QGNjcHUuY29tDQpDYzogc2lndHJhbkBpZXRmLm9y
Zw0KU3ViamVjdDogW1NwYW1dIFJFOiBbU2lndHJhbl0gTTNVQSA6IElQU1AgREUgYmVoYXZpb3Vy
DQoNCg0KDQoNCg0KDQoNClZpdmVrDQogICAgICBQbGVhc2Ugc2VlIGNvbW1lbnRzIGluIGxpbmUN
Cg0KDQoNCiJWaXZlayBUb2t5IiA8dml2ZWt0b2t5QGNjcHUuY29tPkBpZXRmLm9yZyBvbiAwOC8w
NS8yMDAzIDA5OjQ3OjQzIEFNDQoNClNlbnQgYnk6ICAgIHNpZ3RyYW4tYWRtaW5AaWV0Zi5vcmcN
Cg0KDQpUbzogICAgImthbWVzaCBrYXVsIiA8a2trX2thdWxAeWFob28uY29tPg0KY2M6ICAgIDxz
aWd0cmFuQGlldGYub3JnPg0KDQpTdWJqZWN0OiAgICBSRTogW1NpZ3RyYW5dIE0zVUEgOiBJUFNQ
IERFIGJlaGF2aW91cg0KDQoNCkthbWVzaCwNCiAgUGxlYXNlIHNlZSBjb21tZW50cyBpbmxpbmUN
Ci0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBzaWd0cmFuLWFkbWluQGlldGYub3Jn
IFttYWlsdG86c2lndHJhbi1hZG1pbkBpZXRmLm9yZ11PbiBCZWhhbGYgT2YNCmthbWVzaCBrYXVs
DQpTZW50OiBTYXR1cmRheSwgQXVndXN0IDAyLCAyMDAzIDg6MjQgUE0NClRvOiBWaXZlayBUb2t5
DQpDYzogc2lndHJhbkBpZXRmLm9yZw0KU3ViamVjdDogUkU6IFtTaWd0cmFuXSBNM1VBIDogSVBT
UCBERSBiZWhhdmlvdXINCg0KDQpIaSBWaXZlaywNCiAgICBJIGFyZ2VlIHdpdGggeW91IHRoYXQg
aWYgd2UgaW50ZXJtaXggSVBTUCBTRSBhbmQNCkRFIG1vZGVscyB3ZSBjYW4gc3RhcnQgbG9hZHNo
YXJpbmcgdHJhZmZpYyBmb3IgQVMyDQphbW9uZyBJUFNQIEIgYW5kIElQU1AgQSBldmVuIHRob3Vn
aCBJUFNQIEIgaGFzIG5vdA0KcmVjZWl2ZWQgQVNQQUMgbWVzc2FnZSBmcm9tIElQU1AgYy5JdCB3
b3VsZCByZXN1bHQgaW4NCmludGVybWl4aW5nIG9mIHR3byBJUFNQIG1vZGVscy5Gb3Igc29tZSBt
ZXNzYWdlcyBJUFNQDQpDIGhhcyB0byBiZWhhdmUgaW4gREUgbWFubmVyIGFuZCBmb3Igb3RoZXIg
U0UNCmJlaGF2aW91ciBpcyByZXF1aXJlZC5MZXRzIHRha2UgeW91ciBleGFtcGxlLiBPbg0KcmVj
ZWl2aW5nIEFTUEFDIG1lc3NhZ2VzIGZyb20gSVBTUCBBIGFuZCBJUFNQIEIgZm9yDQpBUzEgSVBT
UCBDIHVwZGF0ZXMgb25seSByZW1vdGUgSVBTUCdTIHN0YXRlcyBmb3IgQVMxDQpiZWhhdmluZyBp
biBERSBtYW5uZXIud2hlbiBJUFNQIGMgc2VuZHMgQVNQQUMgZm9yIEFTMg0KdG8gSVBTUCBBIGFu
ZCByZWNlaXZlcyBBQ0sgYmFjayB0aGVuIGFsc28gSVBTUCBDDQpjaGFuZ2VzIGl0cyBzdGF0ZSB0
byBhY3RpdmUgZm9yIGxvY2FsIEFTMiBiZWhhdmluZyBpbg0KREUgbWFubmVyLk5vdyBhcyB5b3Ug
c2FpZCBCaS1kaXJlY3Rpb25hbCBkYXRhIGlzDQpmbG93aW5nIGZyb20gSVBTUCBDIGFuZCBJUFNQ
IEEgd2hlcmUgYXMgc2luZ2xlDQpkaXJlY3Rpb24gdHJhZmZpYyBpcyBwb3NzaWJsZSBmcm9tIElQ
U1AgQyB0byBJUFNQIEINCihmb3IgQVMyKS5Ob3cgYXNzdW1lIElQU1AgQSBzZW5kcyBBU1BJQSBt
ZXNzYWdlIGZvcg0KQVMxIHRvIElQU1AgQyBpbiB0aGlzIGNhc2UgSVBTUCBjIG9uIHJlY2Vpdmlu
ZyBBU1BJQQ0KbWVzc2FnZSBoYXMgdG8gdXBkYXRlIHN0YXRlIG9mIHJlbW90ZSBJUFNQIEEgaW4g
QVMxDQphbmQgYWxzbyBzdGF0ZSBvZiBsb2NhbCBJUFNQIEMgaW4gbG9jYWwgQVMyIGJlaGF2aW5n
DQppbiBTRSBtYW5uZXIuDQoNCltWaXZla10NCiBZb3UgaGF2ZSBhIGdvb2QgcG9pbnQgYnV0IEkg
ZGlkIG5vdCB1bmRlcnN0YW5kIHdoeSB3b3VsZCB3ZSBuZWVkIHRvIGNoYW5nZQ0KdGhlIHN0YXRl
IG9mIElQU1AgQyBpbiB0aGlzIGNhc2UgKCB3aGVuIElQU1AgQSBzZW5kcyBBU1BJQSB0byBJUFNQ
IEMpLiBXaGVuDQpJUFNQIEEgc2VuZHMgQVNQSUEgbWVzc2FnZSBmb3IgQVMxIHRvIElQU1AgQyB0
aGVuIG9ubHkgSVBTUCBBJ3Mgc3RhdGUgd2lsbA0KY2hhbmdlIGluIGxvY2FsIEFTMSBhbmQgdGhl
IGNvcnJlc3BvbmRpbmcgcmVtb3RlIEFTMSBvbiB0aGUgb3RoZXIgc2lkZS4gWW91DQphcmUgcmln
aHQgdGhhdCBBUzEgd2lsbCBub3QgYmUgYWJsZSB0byByZWNlaXZlIHRyYWZmaWMgdGhyb3VnaCBJ
UFNQIEEgLCBidXQNCnRoYXQgZG9lc25vdCByZXN0cmljdCBBUzEgdG8gc2VuZCB0cmFmZmljIGZy
b20gSVBTUCBBLg0KW0thbWVzaF0NCklQU1AgQSBpcyBpbmFjdGl2ZSAoaXQgaGFzIHNlbmQgQVNQ
SUEpIGZvciBBUzEgc28gaG93IGNhbiBpdCBzZW5kIGRhdGEgZm9yDQpBUzEuDQoqKioqVml2ZWsq
KioqKg0KVGhhdCBpcyB3aGF0IEkgYW0gdHJ5aW5nIHRvIHNheSwgSVBTUCBBIGlzIGluYWN0aXZl
IHRvIHJlY2VpdmUgZGF0YS4gSXQgY2FuDQpzdGlsbCBzZW5kIGRhdGEgYmVjYXVzZSByZW1vdGUg
ZGVzdGluYXRpb24gaXMgc3RpbGwgYWN0aXZlIHRvIHJlY2VpdmUgZGF0YQ0KdGhyb3VnaCAgSVBT
UCBBDQpJZiBzZW5kaW5nIGFuIEFjdGl2ZSBtZXNzYWdlIG1lYW5zIGl0IHdpbGwgYmUgYWJsZSB0
byBzZW5kIGFuZCByZWNlaXZlIGRhdGENCnRoZW4gYW4gQWN0aXZlIEFjayBmcm9tIG90aGVyIHdv
dWxkIGhhdmUgYmVlbiBzdWZmY2llbnQgdG8gdGVsbCBJUFNQIEEgdGhhdA0KaXQgY2FuIHN0YXJ0
IHNlbmRpbmcgZGF0YSBhcyB3ZWxsLiBCdXQgaXQgZGlkIG5vdCBoYXBwZW4uLiBJUFNQIEMgc2Vu
dCBhbg0KZXhwbGljaXQgQWN0aXZlIG1lc3NhZ2UgdG8gaW5kaWNhdGUgdGhhdCBpdHMgcmVhZHkg
dG8gcmVjZWl2ZSBkYXRhIHNvIElQU1ANCkMgaXMgdGhlIG9uZSB3aG8gd2lsbCBpbmRpY2F0ZSB0
aGF0IG5vdyBpdCBpcyBub3QgZ29pbmcgdG8gcmVjZWl2ZSBkYXRhLg0KSVBTUCBBIGRvZXMgbm90
IG5lZWQgdG8gc3RvcCBzZW5kaW5nIGRhdGEgdG8gSVBTUCBDIGp1c3QgYmVjYXVzZSBpdCBzZW5k
DQpBU1BJQSBtZXNzYWdlLg0KKioqKioqKioqKioqKioNCg0KTm90ZTogQVMxIGlzIHN0aWxsIFVQ
DQphbmQgcmVhZHkgdG8gcHJvY2VzcyBkYXRhIGFuZCBzbyBpcyBBUzIuIElmIEFTMSB3YW50cyB0
byBnbyBkb3duIGFuZCBub3QNCnByb2Nlc3MgZGF0YSBhdCBhbGwgdGhlbiBpdCBzaG91bGQgc2Vu
dCBJbmFjdGl2ZSB0aHJvdWdoIGJvdGggdGhlIElQU1BzICgNCklQU1AgQSBhbmQgSVBTUCBCKS4N
CltLYW1lc2hdDQogSVBTUCBCIGNhbnTigJl0IHNlbmQgZGF0YSBmb3IgQVMxIHRvIElQU1AgQyBi
ZWNhdXNlIElQU1AgQyBoYXMgbm90IHNlbmQNCkFTUEFDIG1lc3NhZ2UgdG8gaXQuU28gaXQgbWVh
bnMgdGhhdCBBUzHigJlzIGRhdGEgY2FudCByZWFjaCBJUFNQIEMgYmVjYXVzZQ0KSVBTUCBBIGlz
IGluYWN0aXZlIGZvciBBUzEgYW5kIElQU1AgQiBoYXMgbm90IHJlY2VpdmVkIEFTUEFDIG1lc3Nh
Z2UgZnJvbQ0KSVBTUCBDLg0KTm93IHRoZSBxdWVzdGlvbiBhcmlzZXMgdGhhdCB3aGF0IHNob3Vs
ZCBJUFNQIEEgZG8gaWYgaXQNCnJlY2VpdmVzIGRhdGEgZnJvbSBBUzEgd2hpY2ggaGFzIGluYWN0
aXZhdGVkIGl0c2VsZiBmcm9tIGJvdGggIHRoZSBJUFNQcw0KYW5kDQppcyBub3cgdG90YWxseSB1
bmFibGUgdG8gcmVjZWl2ZSBEQVRBID8gLi4uIGZvbGxvd2luZyBwb2ludHMgc2hvdWxkIGJlDQpu
b3RlZA0KMS4gSWYgQVMxIGRvZXNuJ3Qgd2FudCB0byByZWNlaXZlIGRhdGEsIHdoeSB3ZSBjYXJl
IGlmIHRoZSBkYXRhIHNlbnQgYnkgQVMxDQp3ZW50IHRocm91Z2ggYWxsIHRoZSB3YXkgdG8gQVMy
Lg0KMi4gTm93IHdlIGtub3cgdGhhdCBBUzIgd29uJ3QgYmUgYWJsZSB0byBzZW5kIGRhdGEgdG8g
QVMxIGF0YWxsIHNvIGl0IGNhbg0KdGFrZSByZWNvdmVyeSBhbmQgRGUtYWN0aXZhdGUgaXRzZWxm
IHRocm91Z2ggSVBTUCBBICh0byB3aGljaCBpdCBzZW50IEFTUA0KQWN0aXZlIGFuZCBnb3QgQWN0
aXZlIEFjay4pDQoNCmRvZXMgaXQgbWFrZSBzZW5zZSA/IHBsZWFzZSBjb21tZW50Li4NCg0KW0th
bWVzaF0NCiBXZSBoYXZlIHRvIGNoZWNrIHRoZSBzdGF0ZSBvZiBsb2NhbCBJUFNQIGJlZm9yZSBz
ZWxlY3RpbmcgcmVtb3RlDQphcHBsaWNhdGlvbiBzZXJ2ZXIgZm9yIGRhdGENCg0KDQpJZiBJUFNQ
IEMgZG9lcyBub3QgYm90aGVyIGFib3V0IGxvY2FsDQpzdGF0ZSB1cGRhdGlvbiBvbiByZWNlaXZp
bmcgQVNQSUEgZnJvbSBJUFNQIEEsIElQU1AgQw0Kd2lsbCBjb250aW51ZSB0byBzZW5kIGRhdGEg
bWVzc2FnZXMgZm9yIEFTMiB0byBJUFNQIEINCndpdGhvdXQgcmVjZWl2aW5nIGFueXRoaW5nIGZy
b20gb3RoZXIgc2lkZS4gVGhpcyB3aWxsDQpyZXN1bHQgaW4gc2luZ2xlIGRpcmVjdGlvbiB0cmFm
ZmljIGZyb20gSVBTUCBDIHRvIEFTMQ0Kd2l0aG91dCB0aGUga25vd2xlZGdlIG9mIElQU1AgQy5J
ZiB3ZSBhc3NvY2lhdGUgQVMNCnN0YXRlIHdpdGggbG9jYWwgYW5kIHBlZXIgSVBTUCdzIChpbiB5
b3VyIGV4YW1wbGUNCkFTMidzIHN0YXRlIHdpdGggSVBTUCBjIGFuZCBlYWNoIHBlZXIgSVBTUEEg
YW5kIElQU1BCLA0KQVMyJ3Mgc3RhdGUgd2l0aCBJUFNQIEMgYW5kIGVhY2ggcGVlciBJUFNQJ3Mp
IHNpbmdsZQ0KZGlyZWN0aW9uIHRyYWZmaWMgZmxvdyBpcyBub3QgcG9zc2libGUuIFBsZWFzZSBj
b21tZW50DQoNClJlZ2FyZHMNCkthbWVzaA0KLS0tIFZpdmVrIFRva3kgPHZpdmVrdG9reUBjY3B1
LmNvbT4gd3JvdGU6DQo+IEhpIEthbWVzaCwNCj4gICBBbHRob3VnaCBBU1BBQyBtZXNzYWdlIGhh
cyBub3QgYmVlbiBzZW50IHRvIElQU1ANCj4gQiwgYnV0IHRoZSBsb2NhbCBBUyBpcw0KPiBzdGls
bCBhY3RpdmUgYW5kIGlzIHNlbmRpbmcgYW5kIHJlY2VpdmluZyB0cmFmZmljDQo+IHRocm91Z2gg
SVBTUCBBLiBOb3cgb24gdGhlDQo+IG90aGVyIHNpZGUgSVBTUCBBIGFuZCBJUFNQIEIgYXJlIHBh
cnQgb2YgdGhlIHNhbWUgQVMNCj4gKCBBUzEgKS4gU28gZm9sbG93aW5nDQo+IHBvaW50cyBzaG91
bGQgYmUgbm90ZWQuDQo+DQo+IDEuIEJpLWRpcmVjdGlvbmFsIHRyYWZmaWMgYmV0d2VlbiBBUzEg
YW5kIEFTMiBpcw0KPiBwb3NzaWJsZQ0KPiAyLiBJUFNQIEIgaGFzIGFscmVhZHkgc2VudCBBU1BB
QyBhbmQgcmVjZWl2ZWQgQVNQQUMNCj4gQWNrLCBzbyBpdCBpcyByZWFkeSB0bw0KPiByZWNlaXZl
IHRyYWZmaWMuDQo+DQo+ICBTbyB3aHkgZG9uJ3Qgd2UgbG9hZHNoYXJlIHRoZSB0cmFmZmljIGFt
b25nIElQU1AgQQ0KPiBhbmQgSVBTUCBCIGFzIHRoZQ0KPiB0cmFmZmljIGlzIGFueXdheSBnb2lu
ZyB0byBnZXQgdG8gdGhlIHNhbWUNCj4gZGVzdGluYXRpb24gaS5lLiBBUzENCj4NCj4gSW4gdGhl
IHJldmVyc2UgZGlyZWN0aW9uIEFTMSBjYW4gY2hvb3NlIElQU1AgQSB0bw0KPiBzZW5kIHRyYWZm
aWMgdG93YXJkcyBBUzIsDQo+IGFzIG9ubHkgSVBTUCBBIGhhcyByZWNlaXZlZCBBU1BBQyBmcm9t
IElQU1AgQyAoZm9yDQo+IEFTMikNCj4NCj4gY29tbWVudHM/DQo+DQo+IC1WaXZlay4NCj4NCj4g
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogc2lndHJhbi1hZG1pbkBpZXRmLm9y
Zw0KPiBbbWFpbHRvOnNpZ3RyYW4tYWRtaW5AaWV0Zi5vcmddT24gQmVoYWxmIE9mDQo+IGtha2F1
bEBoc3MuaG5zLmNvbQ0KPiBTZW50OiBGcmlkYXksIEF1Z3VzdCAwMSwgMjAwMyAxOjE2IEFNDQo+
IFRvOiBWaXZlayBUb2t5DQo+IENjOiBzaWd0cmFuQGlldGYub3JnDQo+IFN1YmplY3Q6IFJFOiBb
U2lndHJhbl0gTTNVQSA6IElQU1AgREUgYmVoYXZpb3VyDQo+DQo+DQo+DQo+DQo+DQo+DQo+IFZp
dmVrLA0KPg0KPiBJbiB5b3VyIGV4YW1wbGUgYWxzbyBJUFNQIEMgd2lsbCBzZW5kIGRhdGEgZm9y
IEFTMQ0KPiB0byBJUFNQIEEgb25seS5JIGRvbnQNCj4gc2VlIGFueSByZWFzb24gZm9yIElQU1Ag
QyB0byBzZW5kIGRhdGEgdG8gSVBTUCBCDQo+IGJlY2F1c2UgQVNQQUMgbWVzc2FnZSBpcw0KPiBu
b3Qgc2VudCB0byBJUFNQIEIuIEkgZG9udCBzZWUgYW55IHBvc3NpYmlsaXR5IG9mDQo+IHNpbmds
ZSBkaXJlY3Rpb24gdHJhZmZpYw0KPiBmbG93IGluIHlvdXIgZXhhbXBsZSBhbHNvLg0KPg0KPiBL
YW1lc2ggS2F1bA0KPiB3d3cuaHNzd29ybGQuY29tDQo+IEh1Z2hlcyBTb2Z0d2FyZSBTeXN0ZW1z
DQo+DQo+DQo+DQo+DQo+ICJWaXZlayBUb2t5IiA8dml2ZWt0b2t5QGNjcHUuY29tPiBvbiAwOC8w
MS8yMDAzDQo+IDAxOjIzOjExIFBNDQo+DQo+IFRvOiAgICBLYW1lc2ggS2F1bC9IU1NASFNTLCBz
aWd0cmFuQGlldGYub3JnDQo+IGNjOg0KPg0KPiBTdWJqZWN0OiAgICBSRTogW1NpZ3RyYW5dIE0z
VUEgOiBJUFNQIERFIGJlaGF2aW91cg0KPg0KPg0KPiBLYW1lc2gsDQo+DQo+ICAgU2luZ2xlIGRp
cmVjdGlvbiB0cmFmZmljIHdpbGwgc3RpbGwgYmUgcG9zc2libGUuDQo+IElmIHlvdSBsb29rIGF0
IG15DQo+IGV4YW1wbGUgY2FyZWZ1bGx5IHlvdSB3aWxsIG5vdGljZSB0aGF0IGluIGNhc2Ugb2Yg
Mw0KPiBJUFNQcywgaXQgd2lsbCBiZQ0KPiBwb3NzaWJsZS4gSXQgbWF5IGJlIGZvciBhIHNob3J0
IGR1cmF0aW9uIG9mIHRpbWUuIEluDQo+IG15IGV4YW1wbGUgbG9jYWwNCj4gQVMgaXMgYWxyZWFk
eSBBY3RpdmUgYXMgaXQgc2VudCBBU1AgQWN0aXZlIG1lc3NhZ2UNCj4gdG8gb25lIG9mIHRoZSBw
ZWVyDQo+IElQU1BzICggYWxzbyBnb3QgdGhlIEFDSyBiYWNrICkNCj4NCj4gcGxlYXNlIGdvIHRo
cm91Z2ggdGhlIGV4YW1wbGUgYWdhaW4gLi4gd2FpdGluZyBmb3INCj4gY29tbWVudHMgPw0KPg0K
PiBWaXZlaw0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4gSGkgU29tZSBjb21tZW50cyBiZWxvdw0K
PiA+DQo+ID4gIFdoZW4gSVBTUCBCIHJlY2VpdmVzIEFTUEFDIG1lc3NhZ2UgZnJvbSBJUFNQIEEN
Cj4gZm9yIEFTMSBpdCBtYXJrcw0KPiByZW1vdGUNCj4gPiBJUFNQIEEgYWN0aXZlIGZvciByZW1v
dGUgQVMxIGFuZCBzZW5kcyBBU1BBQyBhY2sNCj4gYmFjayBmb3IgQVMxIHRvDQo+IElQU1AgQS5O
b3cNCj4gPiB3aXRoIHRoZXNlIG1lc3NhZ2UgZXhjaGFuZ2VzIGl0IG1lYW5zIHRoYXQgSVBTUCBB
DQo+IGlzIHJlYWR5IHRvIHJlY2VpdmUNCj4gPiB0cmFmZmljIGZvciBBUzEuQXQgdGhpcyBwb2lu
dCBvZiB0aW1lIElQU1AgQiBoYXMNCj4gbm90IGV4cHJlc3NlZCBpdHMNCj4gPiB3aWxsaW5nbmVz
cyB0byBzZW5kIGRhdGEgZm9yIGFueSBBUy5JUFNQIEIgIGNhbm5vdA0KPiAgc2VuZCBhbnkNCj4g
YXBwbGljYXRpb24NCj4gPiBkYXRhIGJlY2F1c2UgaXRzIGxvY2FsIGFwcGxpY2F0aW9ucyBhcmUg
bm90IGFjdGl2ZQ0KPiB5ZXQuU28gc2luZ2xlDQo+IGRpcmVjdGlvbg0KPiA+IHRyYWZmaWMgZmxv
dyB3aWxsIG5ldmVyIG9jY3VyLk5vdyB3aGVuIElQU1AgQg0KPiBzZW5kcyBBU1BBQyBtZXNzYWdl
DQo+IGZvciBBUzINCj4gPiB0byBJUFNQIEEgYW5kIGdldHMgYmFjayBBU1BBQyBhY2sgZm9yIEFT
MiBpdCB3aWxsDQo+IGdpdmUgcmVzdW1lDQo+IGluZGljYXRpb24gdG8NCj4gPiB1c2VyIG5vdy5B
UzEgYW5kIEFTMiBhcmUgYmFzaWNhbGx5IHNhbWUgdHlwZSBvZg0KPiBNVFAzIHVzZXJzLCBhbmQg
dXNlcg0KPiB0bw0KPiA+IHVzZXIgY29tbXVuaWNhdGlvbiB3aWxsIG9ubHkgc3RhcnQgaWYgYm90
aCB1c2Vycw0KPiBhcmUgcmVhZHkgYW5kDQo+IGFjdGl2ZS4NCj4gPg0KPiA+DQo+ID4gICAgICst
LS0tLS0tLS0tLSsgICAgICAgICAgICAgICstLS0tLS0tLS0tLSsNCj4gPiAgICAgfCAgICAgICAg
ICAgfCAgICAgICAgICAgICAgfCAgICAgICAgICAgfA0KPiA+ICAgICB8IElQU1AgQSAgICB8ICAg
ICAgICAgICAgICB8IElQU1AgQiAgICB8DQo+ID4gICAgIHwgICAgICAgICAgICstLS0tLS0tLS0t
LS0tLSsgICAgICAgICAgIHwNCj4gPiAgICAgfCAgICAgICAgICAgfCAgICAgICAgICAgICAgfCAg
ICAgICAgICAgfA0KPiA+ICAgICArLS0tLS0tLS0tLS0rICAgICAgICAgICAgICArLS0tLS0tLS0t
LS0rDQo+ID4NCj4gPiAgICAgICAgIEFTMSAgICAgICAgICAgICAgICAgICAgICAgIEFTMg0KPiA+
DQo+ID4gS2FtZXNoIEthdWwNCj4gPiB3d3cuaHNzd29ybGQuY29tDQo+ID4gSHVnaGVzIFNvZnR3
YXJlIFN5c3RlbXMNCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4gIlZJdmVrIFRva3kiIDx2
aXZla3Rva3lAY2NwdS5jb20+QGlldGYub3JnIG9uDQo+IDA3LzMxLzIwMDMgMTE6MTk6MzkgUE0N
Cj4gPg0KPiA+IFNlbnQgYnk6ICAgIHNpZ3RyYW4tYWRtaW5AaWV0Zi5vcmcNCj4gPg0KPiA+DQo+
ID4gVG86ICAgICJUb2xnYSBBc3ZlcmVuIiA8dG9sZ2FfYXN2ZXJlbkB5YWhvby5jb20+LA0KPiA8
c2lndHJhbkBpZXRmLm9yZz4NCj4gPiBjYzoNCj4gPg0KPiA+IFN1YmplY3Q6ICAgIFJFOiBbU2ln
dHJhbl0gTTNVQSA6IElQU1AgREUgYmVoYXZpb3VyDQo+ID4NCj4gPg0KPiA+IFRvbGdhLA0KPiA+
DQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBzaWd0cmFuLWFkbWlu
QGlldGYub3JnDQo+IFttYWlsdG86c2lndHJhbi1hZG1pbkBpZXRmLm9yZ11Pbg0KPiBCZWhhbGYg
T2YNCj4gPiBUb2xnYSBBc3ZlcmVuDQo+ID4gU2VudDogVGh1cnNkYXksIEp1bHkgMzEsIDIwMDMg
MTA6MTkgQU0NCj4gPiBUbzogc2lndHJhbkBpZXRmLm9yZw0KPiA+IFN1YmplY3Q6IFJFOiBbU2ln
dHJhbl0gTTNVQSA6IElQU1AgREUgYmVoYXZpb3VyDQo+ID4NCj4gPg0KPiA+IFZpdmVrLA0KPiA+
IC0tLSBWaXZlayBUb2t5IDx2aXZla3Rva3lAY2NwdS5jb20+IHdyb3RlOg0KPiA+ID4gUGxlYXNl
IHNlZSBteSBjb21tZW50cyBpbmxpbmUNCj4gPiA+DQo+ID4gPiA+IFNlZSBteSBvcGlnaW9uIG9u
bGluZQ0KPiA+ID4gPg0KPiA+ID4gPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4g
PiA+ID4gRnJvbTogVml2ZWsgVG9reSBbbWFpbHRvOnZpdmVrdG9reUBjY3B1LmNvbV0NCj4gPiA+
ID4gPiBTZW50OiBUaHVyc2RheSwgSnVseSAzMSwgMjAwMyAyOjQyIFBNDQo+ID4gPiA+ID4gVG86
IFRvbGdhIEFzdmVyZW47IHNpZ3RyYW5AaWV0Zi5vcmcNCj4gPiA+ID4gPiBTdWJqZWN0OiBSRTog
W1NpZ3RyYW5dIE0zVUEgOiBJUFNQIERFDQo+IGJlaGF2aW91cg0KPiA+ID4gPiA+DQo+ID4gPiA+
ID4NCj4gPiA+ID4gPiBIaSBUb2xnYSwNCj4gPiA+ID4gPiAgICJBYm92ZSBjYXNlIiBtZWFucw0K
PiA+ID4gPiA+ICJ3aGVuIEFTMSBoYXMgYWN0aXZhdGVkIGl0c2VsZiBieSBzZW5kaW5nDQo+ID4g
PiA+ID4gIEFTUCBBY3RpdmUgZnJvbSBib3RoIHRoZSBJUFNQcyAoQSAmIEIpIGJ1dA0KPiA+ID4g
PiA+ICBBUzIgaGFzIHNlbnQgQVNQIEFjdGl2ZSBqdXN0IHRvIElQU1BfQS4iDQo+ID4gPiA+ID4N
Cj4gPiA+ID4gPiBJbiBteSBvcGluaW9uIElQU1BfQyBzaG91bGQgbG9hZHNoYXJlIHRoZQ0KPiA+
ID4gdHJhZmZpYw0KPiA+ID4gPiA+IGFzIGl0IGhhcyByZWNlaXZlZCBBU1AgYWN0aXZlIGZyb20g
Ym90aCB0aGUNCj4gPiA+IElQU1BzDQo+ID4gPiA+ID4gc28gQVMxIGlzIGFjY2Vzc2libGUgdGhy
b3VnaCBib3RoIG9mIHRoZXNlLg0KPiA+ID4gPiA+IEhvd2V2ZXIsIGl0IGlzIHRoZSByZXNwb25z
aWJpbGl0eSBvZiBBUzEgdG8NCj4gPiA+IHJvdXRlDQo+ID4gPiA+ID4gYWxsIHRoZSB0cmFmZmlj
IHRvd2FyZHMgQVMyIHRocm91Z2ggSVBTUF9BLg0KPiA+ID4gPg0KPiA+ID4gPiBJZiBJUFNQX0Ig
cmVjZWl2ZSBzb21lIHRyYWZmaWMgZnJvbSBJUFNQX0MgQlVUDQo+IG5vDQo+ID4gPiBBUyBpcyBB
Q1RJVkUgZm9yDQo+ID4gPiBpdCBvbg0KPiA+ID4gPiBJUFNQX0MgY2FuIGl0IHJvdXRlIHRoaXMg
dHJhZmZpYz8/Pw0KPiA+ID4gPiBDQU4gYSBTRyBzZW5kIHRvIGEgc3M3IG5ldHdvcmsgYSBtZXNz
YWdlDQo+IHJlY2VpdmUNCj4gPiA+IGZyb20gYW4gSU5BQ1RJVkUNCj4gPiA+IEFTUCAhDQo+DQo9
PT0gbWVzc2FnZSB0cnVuY2F0ZWQgPT09DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KRG8geW91IFlhaG9vIT8NCllhaG9vISBDYWxlbmRhciAtIEZyZWUgb25saW5lIGNh
bGVuZGFyIHdpdGggc3luYyB0byBPdXRsb29rKFRNKS4NCmh0dHA6Ly9jYWxlbmRhci55YWhvby5j
b20NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClNp
Z3RyYW4gbWFpbGluZyBsaXN0DQpTaWd0cmFuQGlldGYub3JnDQpodHRwczovL3d3dzEuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9zaWd0cmFuDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NClNpZ3RyYW4gbWFpbGluZyBsaXN0DQpTaWd0cmFuQGll
dGYub3JnDQogaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lndHJhbg0K
DQoNCg0KDQoNCiJESVNDTEFJTUVSOiBUaGlzIG1lc3NhZ2UgaXMgcHJvcHJpZXRhcnkgdG8gSHVn
aGVzIFNvZnR3YXJlIFN5c3RlbXMgTGltaXRlZA0KKEhTUykgYW5kIGlzIGludGVuZGVkIHNvbGVs
eSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCB0byB3aG9tIGl0IGlzDQphZGRyZXNzZWQu
IEl0IG1heSBjb250YWluICBwcml2aWxlZ2VkIG9yIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiBh
bmQNCnNob3VsZCBub3QgYmUgY2lyY3VsYXRlZCBvciB1c2VkIGZvciBhbnkgcHVycG9zZSBvdGhl
ciB0aGFuIGZvciB3aGF0IGl0IGlzDQppbnRlbmRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhp
cyBtZXNzYWdlIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZQ0Kb3JpZ2luYXRvciBpbW1lZGlh
dGVseS4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgeW91IGFyZQ0Kbm90
aWZpZWQgdGhhdCB5b3UgYXJlIHN0cmljdGx5IHByb2hpYml0ZWQgZnJvbSB1c2luZywgY29weWlu
ZywgYWx0ZXJpbmcsIG9yDQpkaXNjbG9zaW5nIHRoZSBjb250ZW50cyBvZiB0aGlzIG1lc3NhZ2Uu
IEhTUyBhY2NlcHRzIG5vIHJlc3BvbnNpYmlsaXR5IGZvcg0KbG9zcyBvciBkYW1hZ2UgYXJpc2lu
ZyBmcm9tIHRoZSB1c2Ugb2YgdGhlIGluZm9ybWF0aW9uIHRyYW5zbWl0dGVkIGJ5IHRoaXMNCmVt
YWlsIGluY2x1ZGluZyBkYW1hZ2UgZnJvbSB2aXJ1cy4iDQoNCg0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClNpZ3RyYW4gbWFpbGluZyBsaXN0DQpTaWd0
cmFuQGlldGYub3JnDQogaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2ln
dHJhbg0K



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



From exim@www1.ietf.org  Thu Aug  7 07:12:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08013
	for <sigtran-archive@odin.ietf.org>; Thu, 7 Aug 2003 07:12:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kiga-00085l-TD
	for sigtran-archive@odin.ietf.org; Thu, 07 Aug 2003 07:12:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h77BC08w031099
	for sigtran-archive@odin.ietf.org; Thu, 7 Aug 2003 07:12:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kigZ-00085H-GA; Thu, 07 Aug 2003 07:11:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kigR-00084w-7T
	for sigtran@optimus.ietf.org; Thu, 07 Aug 2003 07:11:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08000
	for <sigtran@ietf.org>; Thu, 7 Aug 2003 07:11:43 -0400 (EDT)
From: ygahlaut@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kigM-00054W-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 07:11:46 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kigH-000545-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 07:11:45 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5] (may be forged))
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h77B8Yw14969;
	Thu, 7 Aug 2003 16:38:34 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h77BB7O27252;
	Thu, 7 Aug 2003 16:41:08 +0530 (IST)
Subject: Re: [Sigtran] SUA -- Source Address in the CORE message
To: bidulock@openss7.org
Cc: sigtran@ietf.org
Date: Thu, 7 Aug 2003 16:35:36 +0530
Message-ID: <OF33C89C32.6D027798-ON65256D7B.00392774@hss.hns.com>
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 07/08/2003
 04:34:11 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>





Hi Brian,
 Please see some comments inline
Regards
Yogesh
www.hssworld.com
Hughes Software Systems




"Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 08/07/2003
01:42:03 PM

Please respond to bidulock@openss7.org

Sent by:    sigtran-admin@ietf.org


To:    Yogesh Gahlaut/HSS@HSS
cc:    sigtran@ietf.org

Subject:    Re: [Sigtran] SUA -- Source Address in the CORE message


ygahlaut,

ygahlaut@hss.hns.com wrote:
(Wed, 06 Aug 2003 17:54:39)
>
>
>
>
> Hi,
>         According to the SUA draft Source Address field in CORE message
is
> optional.
> Consider the following sequence
>
> SGP sends a CORE message to ASP without Source Address.
> ASP sends back the COAK to same SGP without Destination Address.
> Connection established
> :
> :
>  Data transfer takes place
> :
> :
> SGP sends a DUNA message
> :

It is not the role of the ASP to perform SCCP CO state machine functions.
These are performed at the SGP.  It is the SGP's resposibility to, as well
as
sending the DUNA, send RELRE (N-DISCONNNECT-Indication) to the ASP with the
appropriate cause (in this case, Subsystem Failure, SCCP Failure, or MTP
Failure).

: SGP sends RELRE
###### Yogesh #######
I agree about performing the SCCP CO state machine functions at the SGP
side. But my query was that how to identify the connection for which i need
to send RELRE. I am saying that connection was initiated from SGP side and
N-CONNECT request has no calling address(because its optional). When DUNA
is to be sent to ASP with some point code (say X). Now look out for
connections which has calling address(or Originating Node) as the Point
Code X which is now getting Unavailable.
Please Correct me if i am missing something.

One more thing as you said RELRE should be sent to ASP. In case if i have
say 'n' connections, first i should send 'n' RELRE and then wait for 'n'
RELCO and then send DUNA.
###################

> :  <----- Point 1
> :
> ASP Send Connection Oriented Data

It would be typical to discard CO data after sending RELRE (at least for
a short while), to give the AS time to respond to the
N-DISCONNECT-Indication
and stop sending data.

--brian

Please remove your DISCLAIMER below from future mailings.

> :
> :  <---- Point 2
> :
>
>
> Now  queries
> 1> on Point 1 should the connection be terminated with the destination
from
> which DUNA message is received and no CODT is allowed
> If Yes.... How ?  considering the case where ASP did not receive the
Source
> Address in CORE message. how can the connection be identified?  because
ASP
> does not know the peer's address for this Connection.
>
> Should the Connection be identified using RC  but then there may be a
case
> in which there is no RC in DUNA message (RC is optional in DUNA message)
?
>
> 2> on point 2 should this CODT message be allowed to reach SGP ?
>    should this message be  routed to another SGP(if there) ?
>
>
> Please correct me if I am missing something
>
> Regards
> Yogesh
> www.hssworld.com
> Hughes Software Systems
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

_______________________________________________
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



From exim@www1.ietf.org  Fri Aug  8 02:23:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00550
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 02:23:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l0eZ-0001hR-5i
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 02:23:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h786N7vI006534
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 02:23:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l0eV-0001gt-H8; Fri, 08 Aug 2003 02:23:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l0dy-0001eR-8L
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 02:22:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00505
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 02:22:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l0du-0005xT-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 02:22:26 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19l0ds-0005xM-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 02:22:25 -0400
Received: from [172.16.2.15] (helo=hewlettyf9yyzb)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19l0dm-0005W9-MP; Thu, 07 Aug 2003 23:22:19 -0700
From: "Vivek Toky" <vivektoky@ccpu.com>
To: <kakaul@hss.hns.com>
Cc: <sigtran@ietf.org>
Subject: RE: [Spam] RE: [Sigtran] M3UA : IPSP DE behaviour
Date: Thu, 7 Aug 2003 23:22:14 -0700
Message-ID: <FHEPLGHNCJCJADFMFBGFGEMJCBAA.vivektoky@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <OF30F6A559.B44F57FF-ON65256D7B.0037743C@hss.hns.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Hi Kamesh,
   The text specified in the section can be interpreted in several ways. =
Please see inline response

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
kakaul@hss.hns.com
Sent: Thursday, August 07, 2003 3:12 AM
To: Vivek Toky
Cc: sigtran@ietf.org
Subject: [Spam] RE: [Sigtran] M3UA : IPSP DE behaviour






Hi Vivek,
   Please go through the section attached from RFC 3332
   4.3.4.4.1 IPSP Considerations (ASP Inactive)

   An IPSP may be considered in the ASP-INACTIVE state by a remote IPSP
   after an ASP Inactive or ASP Inactive Ack message has been received
   from it.

   Alternatively, an interchange of ASP Inactive messages from each end
   can be performed. This option follows the ASP state transition
   diagram and gives the additional advantage of selecting a particular
   AS to be deactivated from each end ([Vivek:] does it mean, if you =
inactivate AS in one direction that does not de-activate AS from other =
end).
   It is especially useful when an IPSP is serving more than one AS.=20
   It would need four messages for completion ([Vivek:] does it mean =
that single direction inactivation will not complete the inactivation =
procedure ).

   IMO IPSP A in your example after sending ASPIA message for AS1 would
   not be able to send or receive traffic from or for AS1.

[Vivek:] I would say that RFC as well as IG do not explain IPSP DE =
correctly.
There should be more explicit statements present to avoid any =
interoperability problems. The example which I gave clearly explains =
that there is no need to stop traffic in both directions if Inactivation =
occurred just from one direction. I would again suggest the authors of =
M3UA to clarify IPSP DE Activation and De-Activation procedure in next =
version of IG.

Regards
Kamesh Kaul
www.hssworld.com
Hughes Software Systems








"Vivek Toky" <vivektoky@ccpu.com>@ietf.org on 08/07/2003 10:00:09 AM

Sent by:    sigtran-admin@ietf.org


To:    Kamesh Kaul/HSS@HSS
cc:    <sigtran@ietf.org>

Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour



Kamesh,

  See my comments Inline..

-----Original Message-----
From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
Sent: Wednesday, August 06, 2003 8:47 PM
To: vivektoky@ccpu.com
Cc: sigtran@ietf.org
Subject: [Spam] RE: [Sigtran] M3UA : IPSP DE behaviour







Vivek
      Please see comments in line



"Vivek Toky" <vivektoky@ccpu.com>@ietf.org on 08/05/2003 09:47:43 AM

Sent by:    sigtran-admin@ietf.org


To:    "kamesh kaul" <kkk_kaul@yahoo.com>
cc:    <sigtran@ietf.org>

Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour


Kamesh,
  Please see comments inline
-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
kamesh kaul
Sent: Saturday, August 02, 2003 8:24 PM
To: Vivek Toky
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour


Hi Vivek,
    I argee with you that if we intermix IPSP SE and
DE models we can start loadsharing traffic for AS2
among IPSP B and IPSP A even though IPSP B has not
received ASPAC message from IPSP c.It would result in
intermixing of two IPSP models.For some messages IPSP
C has to behave in DE manner and for other SE
behaviour is required.Lets take your example. On
receiving ASPAC messages from IPSP A and IPSP B for
AS1 IPSP C updates only remote IPSP'S states for AS1
behaving in DE manner.when IPSP c sends ASPAC for AS2
to IPSP A and receives ACK back then also IPSP C
changes its state to active for local AS2 behaving in
DE manner.Now as you said Bi-directional data is
flowing from IPSP C and IPSP A where as single
direction traffic is possible from IPSP C to IPSP B
(for AS2).Now assume IPSP A sends ASPIA message for
AS1 to IPSP C in this case IPSP c on receiving ASPIA
message has to update state of remote IPSP A in AS1
and also state of local IPSP C in local AS2 behaving
in SE manner.

[Vivek]
 You have a good point but I did not understand why would we need to =
change
the state of IPSP C in this case ( when IPSP A sends ASPIA to IPSP C). =
When
IPSP A sends ASPIA message for AS1 to IPSP C then only IPSP A's state =
will
change in local AS1 and the corresponding remote AS1 on the other side. =
You
are right that AS1 will not be able to receive traffic through IPSP A , =
but
that doesnot restrict AS1 to send traffic from IPSP A.
[Kamesh]
IPSP A is inactive (it has send ASPIA) for AS1 so how can it send data =
for
AS1.
****Vivek*****
That is what I am trying to say, IPSP A is inactive to receive data. It =
can
still send data because remote destination is still active to receive =
data
through  IPSP A
If sending an Active message means it will be able to send and receive =
data
then an Active Ack from other would have been suffcient to tell IPSP A =
that
it can start sending data as well. But it did not happen.. IPSP C sent =
an
explicit Active message to indicate that its ready to receive data so =
IPSP
C is the one who will indicate that now it is not going to receive data.
IPSP A does not need to stop sending data to IPSP C just because it send
ASPIA message.
**************

Note: AS1 is still UP
and ready to process data and so is AS2. If AS1 wants to go down and not
process data at all then it should sent Inactive through both the IPSPs =
(
IPSP A and IPSP B).
[Kamesh]
 IPSP B cant=E2=80=99t send data for AS1 to IPSP C because IPSP C has =
not send
ASPAC message to it.So it means that AS1=E2=80=99s data cant reach IPSP =
C because
IPSP A is inactive for AS1 and IPSP B has not received ASPAC message =
from
IPSP C.
Now the question arises that what should IPSP A do if it
receives data from AS1 which has inactivated itself from both  the IPSPs
and
is now totally unable to receive DATA ? ... following points should be
noted
1. If AS1 doesn't want to receive data, why we care if the data sent by =
AS1
went through all the way to AS2.
2. Now we know that AS2 won't be able to send data to AS1 atall so it =
can
take recovery and De-activate itself through IPSP A (to which it sent =
ASP
Active and got Active Ack.)

does it make sense ? please comment..

[Kamesh]
 We have to check the state of local IPSP before selecting remote
application server for data


If IPSP C does not bother about local
state updation on receiving ASPIA from IPSP A, IPSP C
will continue to send data messages for AS2 to IPSP B
without receiving anything from other side. This will
result in single direction traffic from IPSP C to AS1
without the knowledge of IPSP C.If we associate AS
state with local and peer IPSP's (in your example
AS2's state with IPSP c and each peer IPSPA and IPSPB,
AS2's state with IPSP C and each peer IPSP's) single
direction traffic flow is not possible. Please comment

Regards
Kamesh
--- Vivek Toky <vivektoky@ccpu.com> wrote:
> Hi Kamesh,
>   Although ASPAC message has not been sent to IPSP
> B, but the local AS is
> still active and is sending and receiving traffic
> through IPSP A. Now on the
> other side IPSP A and IPSP B are part of the same AS
> ( AS1 ). So following
> points should be noted.
>
> 1. Bi-directional traffic between AS1 and AS2 is
> possible
> 2. IPSP B has already sent ASPAC and received ASPAC
> Ack, so it is ready to
> receive traffic.
>
>  So why don't we loadshare the traffic among IPSP A
> and IPSP B as the
> traffic is anyway going to get to the same
> destination i.e. AS1
>
> In the reverse direction AS1 can choose IPSP A to
> send traffic towards AS2,
> as only IPSP A has received ASPAC from IPSP C (for
> AS2)
>
> comments?
>
> -Vivek.
>
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> kakaul@hss.hns.com
> Sent: Friday, August 01, 2003 1:16 AM
> To: Vivek Toky
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
>
>
>
>
> Vivek,
>
> In your example also IPSP C will send data for AS1
> to IPSP A only.I dont
> see any reason for IPSP C to send data to IPSP B
> because ASPAC message is
> not sent to IPSP B. I dont see any possibility of
> single direction traffic
> flow in your example also.
>
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>
>
>
>
> "Vivek Toky" <vivektoky@ccpu.com> on 08/01/2003
> 01:23:11 PM
>
> To:    Kamesh Kaul/HSS@HSS, sigtran@ietf.org
> cc:
>
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
> Kamesh,
>
>   Single direction traffic will still be possible.
> If you look at my
> example carefully you will notice that in case of 3
> IPSPs, it will be
> possible. It may be for a short duration of time. In
> my example local
> AS is already Active as it sent ASP Active message
> to one of the peer
> IPSPs ( also got the ACK back )
>
> please go through the example again .. waiting for
> comments ?
>
> Vivek
> >
> >
> >
> >
> > Hi Some comments below
> >
> >  When IPSP B receives ASPAC message from IPSP A
> for AS1 it marks
> remote
> > IPSP A active for remote AS1 and sends ASPAC ack
> back for AS1 to
> IPSP A.Now
> > with these message exchanges it means that IPSP A
> is ready to receive
> > traffic for AS1.At this point of time IPSP B has
> not expressed its
> > willingness to send data for any AS.IPSP B  cannot
>  send any
> application
> > data because its local applications are not active
> yet.So single
> direction
> > traffic flow will never occur.Now when IPSP B
> sends ASPAC message
> for AS2
> > to IPSP A and gets back ASPAC ack for AS2 it will
> give resume
> indication to
> > user now.AS1 and AS2 are basically same type of
> MTP3 users, and user
> to
> > user communication will only start if both users
> are ready and
> active.
> >
> >
> >     +-----------+              +-----------+
> >     |           |              |           |
> >     | IPSP A    |              | IPSP B    |
> >     |           +--------------+           |
> >     |           |              |           |
> >     +-----------+              +-----------+
> >
> >         AS1                        AS2
> >
> > Kamesh Kaul
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> >
> >
> >
> > "VIvek Toky" <vivektoky@ccpu.com>@ietf.org on
> 07/31/2003 11:19:39 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    "Tolga Asveren" <tolga_asveren@yahoo.com>,
> <sigtran@ietf.org>
> > cc:
> >
> > Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> >
> >
> > Tolga,
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On
> Behalf Of
> > Tolga Asveren
> > Sent: Thursday, July 31, 2003 10:19 AM
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> >
> >
> > Vivek,
> > --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > > Please see my comments inline
> > >
> > > > See my opigion online
> > > >
> > > > > -----Original Message-----
> > > > > From: Vivek Toky [mailto:vivektoky@ccpu.com]
> > > > > Sent: Thursday, July 31, 2003 2:42 PM
> > > > > To: Tolga Asveren; sigtran@ietf.org
> > > > > Subject: RE: [Sigtran] M3UA : IPSP DE
> behaviour
> > > > >
> > > > >
> > > > > Hi Tolga,
> > > > >   "Above case" means
> > > > > "when AS1 has activated itself by sending
> > > > >  ASP Active from both the IPSPs (A & B) but
> > > > >  AS2 has sent ASP Active just to IPSP_A."
> > > > >
> > > > > In my opinion IPSP_C should loadshare the
> > > traffic
> > > > > as it has received ASP active from both the
> > > IPSPs
> > > > > so AS1 is accessible through both of these.
> > > > > However, it is the responsibility of AS1 to
> > > route
> > > > > all the traffic towards AS2 through IPSP_A.
> > > >
> > > > If IPSP_B receive some traffic from IPSP_C BUT
> no
> > > AS is ACTIVE for
> > > it on
> > > > IPSP_C can it route this traffic???
> > > > CAN a SG send to a ss7 network a message
> receive
> > > from an INACTIVE
> > > ASP !
>
=3D=3D=3D message truncated =3D=3D=3D


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

_______________________________________________
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





"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
Sigtran@ietf.org
 https://www1.ietf.org/mailman/listinfo/sigtran
J(-j)b	b=E6=9E=B2=D4=A2 '~ i=20
bz =0F j)fj=7F b?(-


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



From exim@www1.ietf.org  Fri Aug  8 02:29:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00678
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 02:29:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l0kJ-00027f-01
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 02:29:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h786T226008158
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 02:29:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l0kH-00027I-Ps; Fri, 08 Aug 2003 02:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l0jS-00024d-0V
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 02:28:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00644
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 02:28:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l0jO-0005zL-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 02:28:06 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[0bFlPlfSbWrqiWHvuXhX0vdCMqbDB4+w])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l0jN-0005zI-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 02:28:05 -0400
Received: from ns.pigworks.openss7.net (IDENT:Lhb1nQHG4GbTsg0bzWpZ1Jn0ZBvkTuBF@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h786S5E12459;
	Fri, 8 Aug 2003 00:28:05 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h786S5T23603;
	Fri, 8 Aug 2003 00:28:05 -0600
Date: Fri, 8 Aug 2003 00:28:04 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Valerie Gastaud <valerie.gastaud@ulticom.com>
Cc: Sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA - RC in CLDT
Message-ID: <20030808002804.B23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Valerie Gastaud <valerie.gastaud@ulticom.com>,
	Sigtran <sigtran@ietf.org>
References: <20030807011752.G7039@openss7.org> <NDBBIHAOCKGAMIKNLALOOENLDOAA.valerie.gastaud@ulticom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <NDBBIHAOCKGAMIKNLALOOENLDOAA.valerie.gastaud@ulticom.com>; from valerie.gastaud@ulticom.com on Thu, Aug 07, 2003 at 10:28:17AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Valerie,

Yes, I agree, RC should be made mandatory in M3UA ASPAC as well.

--brian

Valerie Gastaud wrote:                                                             (Thu, 07 Aug 2003 10:28:17)
> Brian,
> 
> Why does it make less sense with SUA than M3UA?
> And even if it makes little sense, assuming this is not no sense, it's
> always better to have consistency between the UAs, this avoids people asking
> the same question in the future.
> 
> Valerie
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: jeudi 7 aout 2003 09:18
> To: Valerie Gastaud
> Cc: Sigtran
> Subject: Re: [Sigtran] SUA - RC in CLDT
> 
> 
> Valerie,
> 
> SUA had RC mandatory in all messages.  This was just a cut and paste error
> from "common UA procedures".  The SUA draft should be corrected to make RC
> mandatory in ASPAC.  Although it may make some sense to M2UA and even M3UA
> to have RC optional in ASPAC, it makes little sense in SUA.  This is why
> RC is mandatory in all messages in SUA.
> 
> --brian
> 
> Valerie Gastaud wrote:
> (Wed, 06 Aug 2003 15:33:59)
> >
> > Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2
> messages)?
> > This is not consistent with M3UA and this is not consistent with the SUA
> > ASPAC message in which the RC is optional.
> > In case of static provisioning of RK, if an SGP receives an ASPAC w/o RC,
> it
> > won't be able to insert the RC in the CLDT.
> >
> > Valerie
> >
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 02:31:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00844
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 02:31:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l0mF-0002JM-R5
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 02:31:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h786V3Ao008879
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 02:31:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l0mF-0002J3-Jy; Fri, 08 Aug 2003 02:31:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l0lv-0002Gu-0i
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 02:30:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00778
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 02:30:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l0lr-00064j-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 02:30:39 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[b3r2MlBqJ1RFPeYhqB6IbgmFVM9bzY4h])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l0lq-00064g-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 02:30:38 -0400
Received: from ns.pigworks.openss7.net (IDENT:XMXmn7ETkiG2a3aAPAl4VdN1/bggi2lP@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h786UdE12494;
	Fri, 8 Aug 2003 00:30:39 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h786UcG23669;
	Fri, 8 Aug 2003 00:30:38 -0600
Date: Fri, 8 Aug 2003 00:30:38 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Anzile, Christophe" <christophe.anzile@hp.com>
Cc: Valerie Gastaud <valerie.gastaud@ulticom.com>, Sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA - RC in CLDT
Message-ID: <20030808003038.C23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Anzile, Christophe" <christophe.anzile@hp.com>,
	Valerie Gastaud <valerie.gastaud@ulticom.com>,
	Sigtran <sigtran@ietf.org>
References: <BE462396B4A022449E0EB2DD4753D054342ED7@vbeexc02.emea.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <BE462396B4A022449E0EB2DD4753D054342ED7@vbeexc02.emea.cpqcorp.net>; from christophe.anzile@hp.com on Thu, Aug 07, 2003 at 11:24:09AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Anzile,,

Anzile, Christophe wrote:                                                          (Thu, 07 Aug 2003 11:24:09)
> Brian (& Valerie),
> 
> Please do not make RC mandatory in ASPAC, or you'll have strong side effects on the draft..
> This is not consistent at all with what's written in the draft page 92, ie
>  [ it is not necessary for the ASP to 
>    include all Routing Contexts of interest in a single ASP Active 
>    message, thus requesting to become active in all Routing Contexts at 
>    the same time.  Multiple ASP Active messages MAY be used to activate 
>    within the Application Servers independently, or in sets.  In the 
>    case where an ASP Active message does not contain a Routing Context 
>    parameter, the receiver must know, via configuration data, which 
>    Application Server(s) the ASP is a member. ]
> 
> -> This is clear that if no RC is present in the ASPAC, it should be considered as a wildcard
> for all AS statically configured in the SG.. 

No, that is not what it means.  If RC is not included, only a single AS can
exist for the SCTP association.


> In return, SG should send back all RCs activated in the ASPAC-ACK msg.

No.  If there is no RC in ASPAC there may be no RC in ASPAC Ack.

> 
> -> This is why RC is therefore mandatory in CLDT/CLDR.

Don't think so...

--brian

> 
> 
> Christophe.
> 
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Thursday, August 07, 2003 9:18 AM
> To: Valerie Gastaud
> Cc: Sigtran
> Subject: Re: [Sigtran] SUA - RC in CLDT
> 
> 
> Valerie,
> 
> SUA had RC mandatory in all messages.  This was just a cut and paste error
> from "common UA procedures".  The SUA draft should be corrected to make RC
> mandatory in ASPAC.  Although it may make some sense to M2UA and even M3UA
> to have RC optional in ASPAC, it makes little sense in SUA.  This is why
> RC is mandatory in all messages in SUA.
> 
> --brian
> 
> Valerie Gastaud wrote:                                                             (Wed, 06 Aug 2003 15:33:59)
> > 
> > Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2 messages)?
> > This is not consistent with M3UA and this is not consistent with the SUA
> > ASPAC message in which the RC is optional.
> > In case of static provisioning of RK, if an SGP receives an ASPAC w/o RC, it
> > won't be able to insert the RC in the CLDT.
> > 
> > Valerie
> > 
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 03:00:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01690
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 03:00:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1EI-0003xI-Uy
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 03:00:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h78702VE015204
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 03:00:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1EH-0003ww-LR; Fri, 08 Aug 2003 03:00:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1EC-0003wS-06
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 02:59:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01668
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 02:59:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l1E8-0006KP-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 02:59:52 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l1E7-0006KL-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 02:59:51 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h786xGB5019874;
	Fri, 8 Aug 2003 01:59:17 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h786wh1C005789;
	Fri, 8 Aug 2003 01:58:43 -0500 (CDT)
Date: Fri, 8 Aug 2003 01:58:42 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: "Anzile, Christophe" <christophe.anzile@hp.com>,
        Valerie Gastaud <valerie.gastaud@ulticom.com>,
        Sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA - RC in CLDT
In-Reply-To: <20030808003038.C23030@openss7.org>
Message-ID: <Pine.SOL.4.10.10308080144320.6428-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>


Everybody,

RC is a mandatory field when an ASP serves more than one AS.
A single ASP ACTIVE message without RC can not be used to active 
multiple ASes across a common SCTP association.RFC does not explicitely
say that RC is mandatory when an ASP serves
multiple ASes across a common association.But it is implied.

RFC has given a flexibility that RC is an optional field when it serves
a single AS.

Say an example, an ASP1 serves multiple ASes and has been connected to 
SGP1.If RC is an optional parameter to activate all ASes, the potential
problem is, while sending DATA messages to ASP1, 

1) How does ASP1 relate the DATA message with an appropriate AS?

2) Suppose AS2 goes down, How does AS2 indicate this to SGP1?(remeber 
   RC has not been communicated between SGP1 and AS2)

3) Suppose SGP1 wants to put AS1 in DOWN state for some kind of
   configuration purpose, How does SGP1 communicate this with AS1 without 
   RC?

RFC implicitely says that RC is a mandatory field when an ASP serves
more than one ASes.

--Samuel

  Alcatel USA, Inc.                  Internet:
<userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:

> Anzile,,
> 
> Anzile, Christophe wrote:                                                          (Thu, 07 Aug 2003 11:24:09)
> > Brian (& Valerie),
> > 
> > Please do not make RC mandatory in ASPAC, or you'll have strong side effects on the draft..
> > This is not consistent at all with what's written in the draft page 92, ie
> >  [ it is not necessary for the ASP to 
> >    include all Routing Contexts of interest in a single ASP Active 
> >    message, thus requesting to become active in all Routing Contexts at 
> >    the same time.  Multiple ASP Active messages MAY be used to activate 
> >    within the Application Servers independently, or in sets.  In the 
> >    case where an ASP Active message does not contain a Routing Context 
> >    parameter, the receiver must know, via configuration data, which 
> >    Application Server(s) the ASP is a member. ]
> > 
> > -> This is clear that if no RC is present in the ASPAC, it should be considered as a wildcard
> > for all AS statically configured in the SG.. 
> 
> No, that is not what it means.  If RC is not included, only a single AS can
> exist for the SCTP association.
> 
> 
> > In return, SG should send back all RCs activated in the ASPAC-ACK msg.
> 
> No.  If there is no RC in ASPAC there may be no RC in ASPAC Ack.
> 
> > 
> > -> This is why RC is therefore mandatory in CLDT/CLDR.
> 
> Don't think so...
> 
> --brian
> 
> > 
> > 
> > Christophe.
> > 
> > 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Thursday, August 07, 2003 9:18 AM
> > To: Valerie Gastaud
> > Cc: Sigtran
> > Subject: Re: [Sigtran] SUA - RC in CLDT
> > 
> > 
> > Valerie,
> > 
> > SUA had RC mandatory in all messages.  This was just a cut and paste error
> > from "common UA procedures".  The SUA draft should be corrected to make RC
> > mandatory in ASPAC.  Although it may make some sense to M2UA and even M3UA
> > to have RC optional in ASPAC, it makes little sense in SUA.  This is why
> > RC is mandatory in all messages in SUA.
> > 
> > --brian
> > 
> > Valerie Gastaud wrote:                                                             (Wed, 06 Aug 2003 15:33:59)
> > > 
> > > Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2 messages)?
> > > This is not consistent with M3UA and this is not consistent with the SUA
> > > ASPAC message in which the RC is optional.
> > > In case of static provisioning of RK, if an SGP receives an ASPAC w/o RC, it
> > > won't be able to insert the RC in the CLDT.
> > > 
> > > Valerie
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> 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



From exim@www1.ietf.org  Fri Aug  8 03:04:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01747
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 03:04:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1IA-00045p-Sd
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 03:04:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7874240015732
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 03:04:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1IA-00045W-2B; Fri, 08 Aug 2003 03:04:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1HB-00044L-Bz
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 03:03:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01730
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 03:02:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l1H7-0006L1-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 03:02:57 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[OFvf5NqkzG5XjPXsQDyprcddm5YXLl8P])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l1H6-0006Ky-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 03:02:56 -0400
Received: from ns.pigworks.openss7.net (IDENT:cun61Uqunx39u7kreHpX9NbMl6V2lO2v@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h7872vE12940;
	Fri, 8 Aug 2003 01:02:57 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h7872vg23987;
	Fri, 8 Aug 2003 01:02:57 -0600
Date: Fri, 8 Aug 2003 01:02:56 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ygahlaut@hss.hns.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] SUA -- Source Address in the CORE message
Message-ID: <20030808010256.D23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: ygahlaut@hss.hns.com, sigtran@ietf.org
References: <OF33C89C32.6D027798-ON65256D7B.00392774@hss.hns.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF33C89C32.6D027798-ON65256D7B.00392774@hss.hns.com>; from ygahlaut@hss.hns.com on Thu, Aug 07, 2003 at 04:35:36PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

ygahlaut,

See Table 2/Q.711 note a1) (calling address in N-CONNECT request):

 "This parameter is associated with the SCCP service access point at
  which this primitive is issued if the calling address is absent."

Therefore, even though there is no calling address in the CORE, the
SGP can determine the SCCP-SAP of the sender of the CORE using the
RC associated with the CORE.

Also, note a3) (responding address in N-CONNECT response):

 "This parameter is associated with the SCCP service access point at
  which this primitive is issued if the calling address is absent."

Therefore, even though there is no calling address in the COAK, the
SCTP can determine the SCCP-SAP of the sender of the COAK using hte
RC associated with the COAK.

As an ASP, you do not send RELRE when DUNA occurs.  The SGP sends
RELRE to the ASP with the reasons already mentioned, but also sends
DUNA because it needs to be passed to the SCCP-User.

See Q.711/6.1.1.2.2 (duly cited in sua-15 section 1.6.1) for more
information.

--brian

ygahlaut@hss.hns.com wrote:                                                       (Thu, 07 Aug 2003 16:35:36)
> 
> 
> 
> 
> Hi Brian,
>  Please see some comments inline
> Regards
> Yogesh
> www.hssworld.com
> Hughes Software Systems
> 
> 
> 
> 
> "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 08/07/2003
> 01:42:03 PM
> 
> Please respond to bidulock@openss7.org
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    Yogesh Gahlaut/HSS@HSS
> cc:    sigtran@ietf.org
> 
> Subject:    Re: [Sigtran] SUA -- Source Address in the CORE message
> 
> 
> ygahlaut,
> 
> ygahlaut@hss.hns.com wrote:
> (Wed, 06 Aug 2003 17:54:39)
> >
> >
> >
> >
> > Hi,
> >         According to the SUA draft Source Address field in CORE message
> is
> > optional.
> > Consider the following sequence
> >
> > SGP sends a CORE message to ASP without Source Address.
> > ASP sends back the COAK to same SGP without Destination Address.
> > Connection established
> > :
> > :
> >  Data transfer takes place
> > :
> > :
> > SGP sends a DUNA message
> > :
> 
> It is not the role of the ASP to perform SCCP CO state machine functions.
> These are performed at the SGP.  It is the SGP's resposibility to, as well
> as
> sending the DUNA, send RELRE (N-DISCONNNECT-Indication) to the ASP with the
> appropriate cause (in this case, Subsystem Failure, SCCP Failure, or MTP
> Failure).
> 
> : SGP sends RELRE
> ###### Yogesh #######
> I agree about performing the SCCP CO state machine functions at the SGP
> side. But my query was that how to identify the connection for which i need
> to send RELRE. I am saying that connection was initiated from SGP side and
> N-CONNECT request has no calling address(because its optional). When DUNA
> is to be sent to ASP with some point code (say X). Now look out for
> connections which has calling address(or Originating Node) as the Point
> Code X which is now getting Unavailable.
> Please Correct me if i am missing something.
> 
> One more thing as you said RELRE should be sent to ASP. In case if i have
> say 'n' connections, first i should send 'n' RELRE and then wait for 'n'
> RELCO and then send DUNA.
> ###################
> 
> > :  <----- Point 1
> > :
> > ASP Send Connection Oriented Data
> 
> It would be typical to discard CO data after sending RELRE (at least for
> a short while), to give the AS time to respond to the
> N-DISCONNECT-Indication
> and stop sending data.
> 
> --brian
> 
> Please remove your DISCLAIMER below from future mailings.
> 
> > :
> > :  <---- Point 2
> > :
> >
> >
> > Now  queries
> > 1> on Point 1 should the connection be terminated with the destination
> from
> > which DUNA message is received and no CODT is allowed
> > If Yes.... How ?  considering the case where ASP did not receive the
> Source
> > Address in CORE message. how can the connection be identified?  because
> ASP
> > does not know the peer's address for this Connection.
> >
> > Should the Connection be identified using RC  but then there may be a
> case
> > in which there is no RC in DUNA message (RC is optional in DUNA message)
> ?
> >
> > 2> on point 2 should this CODT message be allowed to reach SGP ?
> >    should this message be  routed to another SGP(if there) ?
> >
> >
> > Please correct me if I am missing something
> >
> > Regards
> > Yogesh
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> 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

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 03:07:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01855
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 03:07:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1L5-0004L6-TR
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 03:07:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h78773X9016581
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 03:07:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1L4-0004J5-9M; Fri, 08 Aug 2003 03:07:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1Kx-0004IK-27
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 03:06:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01816
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 03:06:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l1Kt-0006MQ-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 03:06:51 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[p4c4EOUnp4vXoeKTIiJDVCvpc00cUYG5])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l1Ks-0006MN-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 03:06:50 -0400
Received: from ns.pigworks.openss7.net (IDENT:a17K0Z9mFXoMVAMOuvk1IPS5M4sQ2q6e@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h7876oE12994;
	Fri, 8 Aug 2003 01:06:50 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h7876oM24018;
	Fri, 8 Aug 2003 01:06:50 -0600
Date: Fri, 8 Aug 2003 01:06:50 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "Anzile, Christophe" <christophe.anzile@hp.com>,
        Valerie Gastaud <valerie.gastaud@ulticom.com>,
        Sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA - RC in CLDT
Message-ID: <20030808010650.E23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	"Anzile, Christophe" <christophe.anzile@hp.com>,
	Valerie Gastaud <valerie.gastaud@ulticom.com>,
	Sigtran <sigtran@ietf.org>
References: <20030808003038.C23030@openss7.org> <Pine.SOL.4.10.10308080144320.6428-100000@sun2685.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10308080144320.6428-100000@sun2685.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Aug 08, 2003 at 01:58:42AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Samuel,

The M3UA IG section 3.5 changes "optional" to "conditional" everywhere
for RC to indicate this explicitly.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 08 Aug 2003 01:58:42)
> 
> Everybody,
> 
> RC is a mandatory field when an ASP serves more than one AS.
> A single ASP ACTIVE message without RC can not be used to active 
> multiple ASes across a common SCTP association.RFC does not explicitely
> say that RC is mandatory when an ASP serves
> multiple ASes across a common association.But it is implied.
> 
> RFC has given a flexibility that RC is an optional field when it serves
> a single AS.
> 
> Say an example, an ASP1 serves multiple ASes and has been connected to 
> SGP1.If RC is an optional parameter to activate all ASes, the potential
> problem is, while sending DATA messages to ASP1, 
> 
> 1) How does ASP1 relate the DATA message with an appropriate AS?
> 
> 2) Suppose AS2 goes down, How does AS2 indicate this to SGP1?(remeber 
>    RC has not been communicated between SGP1 and AS2)
> 
> 3) Suppose SGP1 wants to put AS1 in DOWN state for some kind of
>    configuration purpose, How does SGP1 communicate this with AS1 without 
>    RC?
> 
> RFC implicitely says that RC is a mandatory field when an ASP serves
> more than one ASes.
> 
> --Samuel
> 
>   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> 
> On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> 
> > Anzile,,
> > 
> > Anzile, Christophe wrote:                                                          (Thu, 07 Aug 2003 11:24:09)
> > > Brian (& Valerie),
> > > 
> > > Please do not make RC mandatory in ASPAC, or you'll have strong side effects on the draft..
> > > This is not consistent at all with what's written in the draft page 92, ie
> > >  [ it is not necessary for the ASP to 
> > >    include all Routing Contexts of interest in a single ASP Active 
> > >    message, thus requesting to become active in all Routing Contexts at 
> > >    the same time.  Multiple ASP Active messages MAY be used to activate 
> > >    within the Application Servers independently, or in sets.  In the 
> > >    case where an ASP Active message does not contain a Routing Context 
> > >    parameter, the receiver must know, via configuration data, which 
> > >    Application Server(s) the ASP is a member. ]
> > > 
> > > -> This is clear that if no RC is present in the ASPAC, it should be considered as a wildcard
> > > for all AS statically configured in the SG.. 
> > 
> > No, that is not what it means.  If RC is not included, only a single AS can
> > exist for the SCTP association.
> > 
> > 
> > > In return, SG should send back all RCs activated in the ASPAC-ACK msg.
> > 
> > No.  If there is no RC in ASPAC there may be no RC in ASPAC Ack.
> > 
> > > 
> > > -> This is why RC is therefore mandatory in CLDT/CLDR.
> > 
> > Don't think so...
> > 
> > --brian
> > 
> > > 
> > > 
> > > Christophe.
> > > 
> > > 
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Thursday, August 07, 2003 9:18 AM
> > > To: Valerie Gastaud
> > > Cc: Sigtran
> > > Subject: Re: [Sigtran] SUA - RC in CLDT
> > > 
> > > 
> > > Valerie,
> > > 
> > > SUA had RC mandatory in all messages.  This was just a cut and paste error
> > > from "common UA procedures".  The SUA draft should be corrected to make RC
> > > mandatory in ASPAC.  Although it may make some sense to M2UA and even M3UA
> > > to have RC optional in ASPAC, it makes little sense in SUA.  This is why
> > > RC is mandatory in all messages in SUA.
> > > 
> > > --brian
> > > 
> > > Valerie Gastaud wrote:                                                             (Wed, 06 Aug 2003 15:33:59)
> > > > 
> > > > Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2 messages)?
> > > > This is not consistent with M3UA and this is not consistent with the SUA
> > > > ASPAC message in which the RC is optional.
> > > > In case of static provisioning of RK, if an SGP receives an ASPAC w/o RC, it
> > > > won't be able to insert the RC in the CLDT.
> > > > 
> > > > Valerie
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 03:09:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01885
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 03:09:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1Mz-0004i6-Nt
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 03:09:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h78791dV018084
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 03:09:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1My-0004hZ-VH; Fri, 08 Aug 2003 03:09:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1MV-0004h3-Ca
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 03:08:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01879
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 03:08:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l1MR-0006Mv-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 03:08:27 -0400
Received: from relay5.tp1rc.edu.tw ([163.28.16.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l1MQ-0006Ms-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 03:08:26 -0400
Received: from KHL (61-219-40-1.HINET-IP.hinet.net [61.219.40.1])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by relay5.tp1rc.edu.tw (Postfix) with ESMTP id 5DE33106D67
	for <sigtran@ietf.org>; Fri,  8 Aug 2003 15:08:25 +0800 (CST)
Message-ID: <00bd01c35d7c$f1006a50$6ec5900a@saoe.com>
From: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
To: "sigtran" <sigtran@ietf.org>
References: <Pine.SOL.4.10.10308050007240.3982-100000@sun2685.ssd.usa.alcatel.com>
Subject: Re: [Sigtran] question about m3UA
Date: Fri, 8 Aug 2003 15:16:06 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Hi all,

After SGP receives the ASP UP from ASP1, SGP should immediately send
NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?

Thanks

Ling-Chih Kao
----- Original Message -----
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtra=
n"
<sigtran@ietf.org>
Sent: Tuesday, August 05, 2003 1:22 PM
Subject: Re: [Sigtran] question about m3UA



Brian,

On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:

> kakaul,
>
> But I think that we agreed that it would be wise to tell newly inactive
                                                      ------------------
> ASPs that state of the AS.  Also, in the diagram, the state of the AS
  -------------------------

What does ASP3 do with NOTIFY(AS-INACTIVE)?
Whenever AS state-change happens at SGP, a NTFY will be sent to all ASPes
(other than DOWN-ASPes) pertaining to the same RC.
This is what i remember that everybody agreed.

--Samuel
> does not change with the second ASP (ASP2) sending ASPUP.  The AS chang=
es
> state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram shoul=
d
> show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately after the
> ASPUP Ack is sent to the ASP in question.
>
> The diagram is quite wrong.  Also it is wrong considering the changes t=
o
> be made to the next issue of the IG.
>
> --brian
>
> kakaul@hss.hns.com wrote:
(Tue, 05 Aug 2003 09:31:47)
> >
> >
> >
> >
> > On receiving ASPUP message from ASP3 state of AS does not change, so
> > NOTIFY(AS-INACTIVE) is not send to ASP3.
> >
> > Kamesh
> >
> >
> >
> >
> > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003 11:40:0=
1
AM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    "sigtran" <sigtran@ietf.org>
> > cc:
> >
> > Subject:    [Sigtran] question about m3UA
> >
> >
> >
> >
> > Should=A0ASP3 in the Section 5.1.4 of
> > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > NOTIFY(AS-INACTIVE)?
> >
> > Thanls
> >
> > Ling-Chih Kao
> >
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>
> _______________________________________________
> 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



From exim@www1.ietf.org  Fri Aug  8 03:42:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02392
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 03:42:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1sx-000617-8i
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 03:42:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h787g3BZ023123
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 03:42:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1sv-00060i-9e; Fri, 08 Aug 2003 03:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l1sj-0005y8-Ud
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 03:41:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02370
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 03:41:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l1sh-0006TG-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 03:41:47 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l1sg-0006T8-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 03:41:46 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h787fHB3022069;
	Fri, 8 Aug 2003 02:41:17 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h787fF1C013279;
	Fri, 8 Aug 2003 02:41:15 -0500 (CDT)
Date: Fri, 8 Aug 2003 02:41:15 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Ling-Chih Kao <d86942004@ntu.edu.tw>
cc: sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <00bd01c35d7c$f1006a50$6ec5900a@saoe.com>
Message-ID: <Pine.SOL.4.10.10308080229280.6428-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: QUOTED-PRINTABLE


Ling-Chih Kao,

NTFY(AS-INACT) is sent to all all available peer ASPes.
Note: Available peer means an ASP which received ASP-UP-ACK
in response to ASP-UP messages.(as per RFC section 4.3.4.1).

If you active the AS as soon as a single ASP goes to ASP-INACT
state then it is obvious that whoever sends ASP-UP message to=20
SGP, immediately SGP will send a NTFY(AS-INACT) to the concern
ASP followd by ASP-UP-ACK.


--Samuel
  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 8 Aug 2003, Ling-Chih Kao wrote:

> Hi all,
>=20
> After SGP receives the ASP UP from ASP1, SGP should immediately send
> NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?
>=20
> Thanks
>=20
> Ling-Chih Kao
> ----- Original Message -----
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtra=
n"
> <sigtran@ietf.org>
> Sent: Tuesday, August 05, 2003 1:22 PM
> Subject: Re: [Sigtran] question about m3UA
>=20
>=20
>=20
> Brian,
>=20
> On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
>=20
> > kakaul,
> >
> > But I think that we agreed that it would be wise to tell newly inactive
>                                                       ------------------
> > ASPs that state of the AS.  Also, in the diagram, the state of the AS
>   -------------------------
>=20
> What does ASP3 do with NOTIFY(AS-INACTIVE)?
> Whenever AS state-change happens at SGP, a NTFY will be sent to all ASPes
> (other than DOWN-ASPes) pertaining to the same RC.
> This is what i remember that everybody agreed.
>=20
> --Samuel
> > does not change with the second ASP (ASP2) sending ASPUP.  The AS chang=
es
> > state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram shoul=
d
> > show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately after the
> > ASPUP Ack is sent to the ASP in question.
> >
> > The diagram is quite wrong.  Also it is wrong considering the changes t=
o
> > be made to the next issue of the IG.
> >
> > --brian
> >
> > kakaul@hss.hns.com wrote:
> (Tue, 05 Aug 2003 09:31:47)
> > >
> > >
> > >
> > >
> > > On receiving ASPUP message from ASP3 state of AS does not change, so
> > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > >
> > > Kamesh
> > >
> > >
> > >
> > >
> > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003 11:40:0=
1
> AM
> > >
> > > Sent by:    sigtran-admin@ietf.org
> > >
> > >
> > > To:    "sigtran" <sigtran@ietf.org>
> > > cc:
> > >
> > > Subject:    [Sigtran] question about m3UA
> > >
> > >
> > >
> > >
> > > Should=A0ASP3 in the Section 5.1.4 of
> > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > > NOTIFY(AS-INACTIVE)?
> > >
> > > Thanls
> > >
> > > Ling-Chih Kao
> > >
> > >
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> >
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20


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



From exim@www1.ietf.org  Fri Aug  8 03:59:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02766
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 03:59:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l29P-0006mg-1Z
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 03:59:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h787x2bJ026077
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 03:59:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l29N-0006mN-Vp; Fri, 08 Aug 2003 03:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l28b-0006le-CX
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 03:58:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02732
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 03:58:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l28Y-0006YZ-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 03:58:10 -0400
Received: from relay5.tp1rc.edu.tw ([163.28.16.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l28X-0006YW-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 03:58:10 -0400
Received: from KHL (61-219-40-1.HINET-IP.hinet.net [61.219.40.1])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by relay5.tp1rc.edu.tw (Postfix) with ESMTP id BD2A1106D38
	for <sigtran@ietf.org>; Fri,  8 Aug 2003 15:58:09 +0800 (CST)
Message-ID: <010e01c35d83$e40ef3f0$6ec5900a@saoe.com>
From: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
To: "sigtran" <sigtran@ietf.org>
References: <Pine.SOL.4.10.10308080229280.6428-100000@sun2685.ssd.usa.alcatel.com>
Subject: Re: [Sigtran] question about m3UA
Date: Fri, 8 Aug 2003 16:05:53 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Dear Samuel Dur D. Jeyaseelan


From the new definition of AS-INACTIVE in sec 4.3.2 of
draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS becomes
AS-INACTIVE when there are at least n ASPs in either ASP-INACTIVE or
AS-ACTIVE.

Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP receives two AS=
P
UP (from ASP1 and ASP2).  However, when the SGP receives  ASP UP from ASP=
3,
SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to know whether i=
t
is optional or not?

Thanks.
Ling-Chih Kao

----- Original Message -----
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
Cc: "sigtran" <sigtran@ietf.org>
Sent: Friday, August 08, 2003 3:41 PM
Subject: Re: [Sigtran] question about m3UA



Ling-Chih Kao,

NTFY(AS-INACT) is sent to all all available peer ASPes.
Note: Available peer means an ASP which received ASP-UP-ACK
in response to ASP-UP messages.(as per RFC section 4.3.4.1).

If you active the AS as soon as a single ASP goes to ASP-INACT
state then it is obvious that whoever sends ASP-UP message to
SGP, immediately SGP will send a NTFY(AS-INACT) to the concern
ASP followd by ASP-UP-ACK.


--Samuel
  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.c=
om
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *****=
**

On Fri, 8 Aug 2003, Ling-Chih Kao wrote:

> Hi all,
>
> After SGP receives the ASP UP from ASP1, SGP should immediately send
> NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?
>
> Thanks
>
> Ling-Chih Kao
> ----- Original Message -----
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw>;
"sigtran"
> <sigtran@ietf.org>
> Sent: Tuesday, August 05, 2003 1:22 PM
> Subject: Re: [Sigtran] question about m3UA
>
>
>
> Brian,
>
> On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
>
> > kakaul,
> >
> > But I think that we agreed that it would be wise to tell newly inacti=
ve
>                                                       -----------------=
-
> > ASPs that state of the AS.  Also, in the diagram, the state of the AS
>   -------------------------
>
> What does ASP3 do with NOTIFY(AS-INACTIVE)?
> Whenever AS state-change happens at SGP, a NTFY will be sent to all ASP=
es
> (other than DOWN-ASPes) pertaining to the same RC.
> This is what i remember that everybody agreed.
>
> --Samuel
> > does not change with the second ASP (ASP2) sending ASPUP.  The AS
changes
> > state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram sho=
uld
> > show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately after t=
he
> > ASPUP Ack is sent to the ASP in question.
> >
> > The diagram is quite wrong.  Also it is wrong considering the changes=
 to
> > be made to the next issue of the IG.
> >
> > --brian
> >
> > kakaul@hss.hns.com wrote:
> (Tue, 05 Aug 2003 09:31:47)
> > >
> > >
> > >
> > >
> > > On receiving ASPUP message from ASP3 state of AS does not change, s=
o
> > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > >
> > > Kamesh
> > >
> > >
> > >
> > >
> > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003 11:40=
:01
> AM
> > >
> > > Sent by:    sigtran-admin@ietf.org
> > >
> > >
> > > To:    "sigtran" <sigtran@ietf.org>
> > > cc:
> > >
> > > Subject:    [Sigtran] question about m3UA
> > >
> > >
> > >
> > >
> > > Should=A0ASP3 in the Section 5.1.4 of
> > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > > NOTIFY(AS-INACTIVE)?
> > >
> > > Thanls
> > >
> > > Ling-Chih Kao
> > >
> > >
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >
> > _______________________________________________
> > 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
>
>


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



From exim@www1.ietf.org  Fri Aug  8 04:14:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03204
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 04:14:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2Nv-0007mP-Ne
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 04:14:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h788E33j029901
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 04:14:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2Nt-0007ly-HR; Fri, 08 Aug 2003 04:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2ND-0007lQ-HY
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 04:13:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03172
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 04:13:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2NA-0006fV-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:13:16 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[IXPzW1RAb2lTf3B7/tbXCh9ukTlrCMkH])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2N9-0006fS-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:13:16 -0400
Received: from ns.pigworks.openss7.net (IDENT:Ym3yC4rEntU32gtGT/lRqRWipsXxEv5o@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h788DGE13934;
	Fri, 8 Aug 2003 02:13:16 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h788DGZ24693;
	Fri, 8 Aug 2003 02:13:16 -0600
Date: Fri, 8 Aug 2003 02:13:16 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Ling-Chih Kao <d86942004@ntu.edu.tw>
Cc: sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030808021316.H23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Ling-Chih Kao <d86942004@ntu.edu.tw>,
	sigtran <sigtran@ietf.org>
References: <Pine.SOL.4.10.10308080229280.6428-100000@sun2685.ssd.usa.alcatel.com> <010e01c35d83$e40ef3f0$6ec5900a@saoe.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <010e01c35d83$e40ef3f0$6ec5900a@saoe.com>; from d86942004@ntu.edu.tw on Fri, Aug 08, 2003 at 04:05:53PM +0800
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h788DGE13934
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Ling-Chih,

We agreed it was a good idea to send it, even though there is no
text in the RFC that explicitly requires it.

It might be a good idea to add "SHOULD" text to the IG and correct
the diagram 5.1.4.

--brian

Ling-Chih Kao wrote:                                                     =
        (Fri, 08 Aug 2003 16:05:53)
> Dear Samuel Dur D. Jeyaseelan
>=20
>=20
> >From the new definition of AS-INACTIVE in sec 4.3.2 of
> draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS becomes
> AS-INACTIVE when there are at least n ASPs in either ASP-INACTIVE or
> AS-ACTIVE.
>=20
> Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP receives two =
ASP
> UP (from ASP1 and ASP2).  However, when the SGP receives  ASP UP from A=
SP3,
> SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to know whether=
 it
> is optional or not?
>=20
> Thanks.
> Ling-Chih Kao
>=20
> ----- Original Message -----
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> Cc: "sigtran" <sigtran@ietf.org>
> Sent: Friday, August 08, 2003 3:41 PM
> Subject: Re: [Sigtran] question about m3UA
>=20
>=20
>=20
> Ling-Chih Kao,
>=20
> NTFY(AS-INACT) is sent to all all available peer ASPes.
> Note: Available peer means an ASP which received ASP-UP-ACK
> in response to ASP-UP messages.(as per RFC section 4.3.4.1).
>=20
> If you active the AS as soon as a single ASP goes to ASP-INACT
> state then it is obvious that whoever sends ASP-UP message to
> SGP, immediately SGP will send a NTFY(AS-INACT) to the concern
> ASP followd by ASP-UP-ACK.
>=20
>=20
> --Samuel
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
>=20
> On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
>=20
> > Hi all,
> >
> > After SGP receives the ASP UP from ASP1, SGP should immediately send
> > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?
> >
> > Thanks
> >
> > Ling-Chih Kao
> > ----- Original Message -----
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw>;
> "sigtran"
> > <sigtran@ietf.org>
> > Sent: Tuesday, August 05, 2003 1:22 PM
> > Subject: Re: [Sigtran] question about m3UA
> >
> >
> >
> > Brian,
> >
> > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> >
> > > kakaul,
> > >
> > > But I think that we agreed that it would be wise to tell newly inac=
tive
> >                                                       ---------------=
---
> > > ASPs that state of the AS.  Also, in the diagram, the state of the =
AS
> >   -------------------------
> >
> > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > Whenever AS state-change happens at SGP, a NTFY will be sent to all A=
SPes
> > (other than DOWN-ASPes) pertaining to the same RC.
> > This is what i remember that everybody agreed.
> >
> > --Samuel
> > > does not change with the second ASP (ASP2) sending ASPUP.  The AS
> changes
> > > state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram s=
hould
> > > show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately after=
 the
> > > ASPUP Ack is sent to the ASP in question.
> > >
> > > The diagram is quite wrong.  Also it is wrong considering the chang=
es to
> > > be made to the next issue of the IG.
> > >
> > > --brian
> > >
> > > kakaul@hss.hns.com wrote:
> > (Tue, 05 Aug 2003 09:31:47)
> > > >
> > > >
> > > >
> > > >
> > > > On receiving ASPUP message from ASP3 state of AS does not change,=
 so
> > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > >
> > > > Kamesh
> > > >
> > > >
> > > >
> > > >
> > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003 11:=
40:01
> > AM
> > > >
> > > > Sent by:    sigtran-admin@ietf.org
> > > >
> > > >
> > > > To:    "sigtran" <sigtran@ietf.org>
> > > > cc:
> > > >
> > > > Subject:    [Sigtran] question about m3UA
> > > >
> > > >
> > > >
> > > >
> > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > > > NOTIFY(AS-INACTIVE)?
> > > >
> > > > Thanls
> > > >
> > > > Ling-Chih Kao
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > > _______________________________________________
> > > 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
> >
> >
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 04:20:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03355
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 04:20:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2Tl-0007xX-Cy
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 04:20:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h788K4Fi030575
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 04:20:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2Ti-0007wv-Fs; Fri, 08 Aug 2003 04:20:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2T0-0007vu-TA
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 04:19:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03348
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 04:19:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2Sy-0006i3-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:19:16 -0400
Received: from angelica.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2Sx-0006hm-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:19:15 -0400
Received: from navy.fr.ulticom.com (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with ESMTP id EAA01393;
	Fri, 8 Aug 2003 04:18:45 -0400 (EDT)
Received: from PCGASTAUDL (pc-gastaud-l.fr.ulticom.com [172.26.32.88])
	by navy.fr.ulticom.com (8.11.6+Sun/8.11.6) with SMTP id h788EeJ18671;
	Fri, 8 Aug 2003 10:14:41 +0200 (MEST)
From: "Valerie Gastaud" <valerie.gastaud@ulticom.com>
To: <bidulock@openss7.org>,
        "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "Anzile, Christophe" <christophe.anzile@hp.com>,
        "Sigtran" <sigtran@ietf.org>
Subject: RE: [Sigtran] SUA - RC in CLDT
Date: Fri, 8 Aug 2003 10:19:25 +0200
Message-ID: <NDBBIHAOCKGAMIKNLALOEEODDOAA.valerie.gastaud@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <20030808010650.E23030@openss7.org>
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit


All,

It is clear for M3UA: RC is conditional in the ASPAC/ack and data and the
rule is:
- an ASP serves only one AS across a common association => it is possible
not to configure/exchange RC, neither in ASPAC/ack nor in data.
- an ASP serves multiple ASes across one association => RCs must be used.

If we use the same rule for SUA, then the RC in the SUA data must be
modified from Mandatory to Conditional. If we keep RC mandatory in the SUA
data, then even if one ASP serves a single AS, we are forced to exchange a
RC.

Brian, if RC is mandatory in all SUA messages as you suggest, does this mean
that you consider that one SUA ASP will never serve a single AS?

Valerie

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: vendredi 8 aout 2003 09:07
To: Samuel Dur D. Jeyaseelan
Cc: Anzile, Christophe; Valerie Gastaud; Sigtran
Subject: Re: [Sigtran] SUA - RC in CLDT


Samuel,

The M3UA IG section 3.5 changes "optional" to "conditional" everywhere
for RC to indicate this explicitly.

--brian

Samuel Dur D. Jeyaseelan wrote:
(Fri, 08 Aug 2003 01:58:42)
>
> Everybody,
>
> RC is a mandatory field when an ASP serves more than one AS.
> A single ASP ACTIVE message without RC can not be used to active
> multiple ASes across a common SCTP association.RFC does not explicitely
> say that RC is mandatory when an ASP serves
> multiple ASes across a common association.But it is implied.
>
> RFC has given a flexibility that RC is an optional field when it serves
> a single AS.
>
> Say an example, an ASP1 serves multiple ASes and has been connected to
> SGP1.If RC is an optional parameter to activate all ASes, the potential
> problem is, while sending DATA messages to ASP1,
>
> 1) How does ASP1 relate the DATA message with an appropriate AS?
>
> 2) Suppose AS2 goes down, How does AS2 indicate this to SGP1?(remeber
>    RC has not been communicated between SGP1 and AS2)
>
> 3) Suppose SGP1 wants to put AS1 in DOWN state for some kind of
>    configuration purpose, How does SGP1 communicate this with AS1 without
>    RC?
>
> RFC implicitely says that RC is a mandatory field when an ASP serves
> more than one ASes.
>
> --Samuel
>
>   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc.
*******
>
> On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
>
> > Anzile,,
> >
> > Anzile, Christophe wrote:
(Thu, 07 Aug 2003 11:24:09)
> > > Brian (& Valerie),
> > >
> > > Please do not make RC mandatory in ASPAC, or you'll have strong side
effects on the draft..
> > > This is not consistent at all with what's written in the draft page
92, ie
> > >  [ it is not necessary for the ASP to
> > >    include all Routing Contexts of interest in a single ASP Active
> > >    message, thus requesting to become active in all Routing Contexts
at
> > >    the same time.  Multiple ASP Active messages MAY be used to
activate
> > >    within the Application Servers independently, or in sets.  In the
> > >    case where an ASP Active message does not contain a Routing Context
> > >    parameter, the receiver must know, via configuration data, which
> > >    Application Server(s) the ASP is a member. ]
> > >
> > > -> This is clear that if no RC is present in the ASPAC, it should be
considered as a wildcard
> > > for all AS statically configured in the SG..
> >
> > No, that is not what it means.  If RC is not included, only a single AS
can
> > exist for the SCTP association.
> >
> >
> > > In return, SG should send back all RCs activated in the ASPAC-ACK msg.
> >
> > No.  If there is no RC in ASPAC there may be no RC in ASPAC Ack.
> >
> > >
> > > -> This is why RC is therefore mandatory in CLDT/CLDR.
> >
> > Don't think so...
> >
> > --brian
> >
> > >
> > >
> > > Christophe.
> > >
> > >
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Thursday, August 07, 2003 9:18 AM
> > > To: Valerie Gastaud
> > > Cc: Sigtran
> > > Subject: Re: [Sigtran] SUA - RC in CLDT
> > >
> > >
> > > Valerie,
> > >
> > > SUA had RC mandatory in all messages.  This was just a cut and paste
error
> > > from "common UA procedures".  The SUA draft should be corrected to
make RC
> > > mandatory in ASPAC.  Although it may make some sense to M2UA and even
M3UA
> > > to have RC optional in ASPAC, it makes little sense in SUA.  This is
why
> > > RC is mandatory in all messages in SUA.
> > >
> > > --brian
> > >
> > > Valerie Gastaud wrote:
(Wed, 06 Aug 2003 15:33:59)
> > > >
> > > > Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2
messages)?
> > > > This is not consistent with M3UA and this is not consistent with the
SUA
> > > > ASPAC message in which the RC is optional.
> > > > In case of static provisioning of RK, if an SGP receives an ASPAC
w/o RC, it
> > > > won't be able to insert the RC in the CLDT.
> > > >
> > > > Valerie
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >

--
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


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



From exim@www1.ietf.org  Fri Aug  8 04:28:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03586
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 04:28:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2bT-0008Q2-15
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 04:28:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h788S2wj032356
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 04:28:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2bS-0008Pb-9h; Fri, 08 Aug 2003 04:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2ap-0008P9-2z
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 04:27:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03571
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 04:27:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2am-0006lc-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:27:20 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[YzHK6IXWY858SBl8qv9eu0uhfIKeUqzs])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2al-0006lZ-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:27:19 -0400
Received: from ns.pigworks.openss7.net (IDENT:004ok6ciAc3Xz+bjDco9QD4XKZETRK1y@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h788RIE14153;
	Fri, 8 Aug 2003 02:27:18 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h788RIR24827;
	Fri, 8 Aug 2003 02:27:18 -0600
Date: Fri, 8 Aug 2003 02:27:18 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Anzile, Christophe" <christophe.anzile@hp.com>
Cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        Valerie Gastaud <valerie.gastaud@ulticom.com>,
        Sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA - RC in CLDT
Message-ID: <20030808022718.I23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Anzile, Christophe" <christophe.anzile@hp.com>,
	"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Valerie Gastaud <valerie.gastaud@ulticom.com>,
	Sigtran <sigtran@ietf.org>
References: <BE462396B4A022449E0EB2DD4753D054342EDA@vbeexc02.emea.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <BE462396B4A022449E0EB2DD4753D054342EDA@vbeexc02.emea.cpqcorp.net>; from christophe.anzile@hp.com on Fri, Aug 08, 2003 at 10:12:27AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Anzile,,

SUA-15 was supposed to include some of the more stable changes from
the M3UA IG where applicable to SUA.  Changing optional to conditional
should have been one of them.

Nevertheless, SUA-15 section 4.3.4.3 does say:

  "...  In the case where an ASP wishes to process the traffic for
   more than one Application Server across a common SCTP association,
   the ASP Active message(s) SHOULD contain a list of one or more
   Routing Contexts to indicate for which Application Servers the ASP
   Active message applies. ..."

Which is no different than M3UA.

We can change optional to conditional against RC throughout.

--brian


Anzile, Christophe wrote:                                                          (Fri, 08 Aug 2003 10:12:27)
> Brian,
> 
> are we supposed to look at M3UA IG when implementing SUA ?
> if yes, it would be nice to rename it.
> if no, it would be nice if John could clarify the SUA draft especially the 4.3.4.3 section
> and use "conditional" instead of "optional" when it applies.
> 
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, August 08, 2003 9:07 AM
> To: Samuel Dur D. Jeyaseelan
> Cc: Anzile, Christophe; Valerie Gastaud; Sigtran
> Subject: Re: [Sigtran] SUA - RC in CLDT
> 
> 
> Samuel,
> 
> The M3UA IG section 3.5 changes "optional" to "conditional" everywhere
> for RC to indicate this explicitly.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 08 Aug 2003 01:58:42)
> > 
> > Everybody,
> > 
> > RC is a mandatory field when an ASP serves more than one AS.
> > A single ASP ACTIVE message without RC can not be used to active 
> > multiple ASes across a common SCTP association.RFC does not explicitely
> > say that RC is mandatory when an ASP serves
> > multiple ASes across a common association.But it is implied.
> > 
> > RFC has given a flexibility that RC is an optional field when it serves
> > a single AS.
> > 
> > Say an example, an ASP1 serves multiple ASes and has been connected to 
> > SGP1.If RC is an optional parameter to activate all ASes, the potential
> > problem is, while sending DATA messages to ASP1, 
> > 
> > 1) How does ASP1 relate the DATA message with an appropriate AS?
> > 
> > 2) Suppose AS2 goes down, How does AS2 indicate this to SGP1?(remeber 
> >    RC has not been communicated between SGP1 and AS2)
> > 
> > 3) Suppose SGP1 wants to put AS1 in DOWN state for some kind of
> >    configuration purpose, How does SGP1 communicate this with AS1 without 
> >    RC?
> > 
> > RFC implicitely says that RC is a mandatory field when an ASP serves
> > more than one ASes.
> > 
> > --Samuel
> > 
> >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > 
> > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > 
> > > Anzile,,
> > > 
> > > Anzile, Christophe wrote:                                                          (Thu, 07 Aug 2003 11:24:09)
> > > > Brian (& Valerie),
> > > > 
> > > > Please do not make RC mandatory in ASPAC, or you'll have strong side effects on the draft..
> > > > This is not consistent at all with what's written in the draft page 92, ie
> > > >  [ it is not necessary for the ASP to 
> > > >    include all Routing Contexts of interest in a single ASP Active 
> > > >    message, thus requesting to become active in all Routing Contexts at 
> > > >    the same time.  Multiple ASP Active messages MAY be used to activate 
> > > >    within the Application Servers independently, or in sets.  In the 
> > > >    case where an ASP Active message does not contain a Routing Context 
> > > >    parameter, the receiver must know, via configuration data, which 
> > > >    Application Server(s) the ASP is a member. ]
> > > > 
> > > > -> This is clear that if no RC is present in the ASPAC, it should be considered as a wildcard
> > > > for all AS statically configured in the SG.. 
> > > 
> > > No, that is not what it means.  If RC is not included, only a single AS can
> > > exist for the SCTP association.
> > > 
> > > 
> > > > In return, SG should send back all RCs activated in the ASPAC-ACK msg.
> > > 
> > > No.  If there is no RC in ASPAC there may be no RC in ASPAC Ack.
> > > 
> > > > 
> > > > -> This is why RC is therefore mandatory in CLDT/CLDR.
> > > 
> > > Don't think so...
> > > 
> > > --brian
> > > 
> > > > 
> > > > 
> > > > Christophe.
> > > > 
> > > > 
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: Thursday, August 07, 2003 9:18 AM
> > > > To: Valerie Gastaud
> > > > Cc: Sigtran
> > > > Subject: Re: [Sigtran] SUA - RC in CLDT
> > > > 
> > > > 
> > > > Valerie,
> > > > 
> > > > SUA had RC mandatory in all messages.  This was just a cut and paste error
> > > > from "common UA procedures".  The SUA draft should be corrected to make RC
> > > > mandatory in ASPAC.  Although it may make some sense to M2UA and even M3UA
> > > > to have RC optional in ASPAC, it makes little sense in SUA.  This is why
> > > > RC is mandatory in all messages in SUA.
> > > > 
> > > > --brian
> > > > 
> > > > Valerie Gastaud wrote:                                                             (Wed, 06 Aug 2003 15:33:59)
> > > > > 
> > > > > Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2 messages)?
> > > > > This is not consistent with M3UA and this is not consistent with the SUA
> > > > > ASPAC message in which the RC is optional.
> > > > > In case of static provisioning of RK, if an SGP receives an ASPAC w/o RC, it
> > > > > won't be able to insert the RC in the CLDT.
> > > > > 
> > > > > Valerie
> > > > > 
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 04:32:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03748
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 04:32:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2fK-0000MD-VZ
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 04:32:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h788W2gu001363
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 04:32:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2fK-0000Ll-2q; Fri, 08 Aug 2003 04:32:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2ea-0000LP-00
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 04:31:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03728
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 04:31:10 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2eX-0006nK-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:31:13 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2eS-0006mm-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:31:10 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5] (may be forged))
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h788Rpw28682;
	Fri, 8 Aug 2003 13:57:51 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h788URS10718;
	Fri, 8 Aug 2003 14:00:27 +0530 (IST)
Subject: Re: [Sigtran] question about m3UA
To: bidulock@openss7.org
Cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OFD74D207E.819856CA-ON65256D7C.002D5CF6@hss.hns.com>
Date: Fri, 8 Aug 2003 13:54:54 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 08/08/2003
 01:53:29 PM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable





Brian,
   Do you mean to say that whenever new ASP is sending ASPUP or ASPAC(f=
or
an AS) which does not result in AS state change at SGP.SGP  responds  w=
ith
ACK and NOTIFY(AS).
Right ?
What should ASP do with that NOTIFY.

Regards
Kamesh Kaul
www.hssworld.com
Hughes Software Systems




"Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 08/08/2003
01:43:16 PM

Please respond to bidulock@openss7.org

Sent by:    sigtran-admin@ietf.org


To:    Ling-Chih Kao <d86942004@ntu.edu.tw>
cc:    sigtran <sigtran@ietf.org>

Subject:    Re: [Sigtran] question about m3UA


Ling-Chih,

We agreed it was a good idea to send it, even though there is no
text in the RFC that explicitly requires it.

It might be a good idea to add "SHOULD" text to the IG and correct
the diagram 5.1.4.

--brian

Ling-Chih Kao wrote:
(Fri, 08 Aug 2003 16:05:53)
> Dear Samuel Dur D. Jeyaseelan
>
>
> >From the new definition of AS-INACTIVE in sec 4.3.2 of
> draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS becomes
> AS-INACTIVE when there are at least n ASPs in either ASP-INACTIVE or
> AS-ACTIVE.
>
> Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP receives tw=
o
ASP
> UP (from ASP1 and ASP2).  However, when the SGP receives  ASP UP from=

ASP3,
> SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to know wheth=
er
it
> is optional or not?
>
> Thanks.
> Ling-Chih Kao
>
> ----- Original Message -----
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> Cc: "sigtran" <sigtran@ietf.org>
> Sent: Friday, August 08, 2003 3:41 PM
> Subject: Re: [Sigtran] question about m3UA
>
>
>
> Ling-Chih Kao,
>
> NTFY(AS-INACT) is sent to all all available peer ASPes.
> Note: Available peer means an ASP which received ASP-UP-ACK
> in response to ASP-UP messages.(as per RFC section 4.3.4.1).
>
> If you active the AS as soon as a single ASP goes to ASP-INACT
> state then it is obvious that whoever sends ASP-UP message to
> SGP, immediately SGP will send a NTFY(AS-INACT) to the concern
> ASP followd by ASP-UP-ACK.
>
>
> --Samuel
>   Alcatel USA, Inc.                  Internet:
<userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc.
*******
>
> On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
>
> > Hi all,
> >
> > After SGP receives the ASP UP from ASP1, SGP should immediately sen=
d
> > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?
> >
> > Thanks
> >
> > Ling-Chih Kao
> > ----- Original Message -----
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw>;
> "sigtran"
> > <sigtran@ietf.org>
> > Sent: Tuesday, August 05, 2003 1:22 PM
> > Subject: Re: [Sigtran] question about m3UA
> >
> >
> >
> > Brian,
> >
> > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> >
> > > kakaul,
> > >
> > > But I think that we agreed that it would be wise to tell newly
inactive
> >
------------------
> > > ASPs that state of the AS.  Also, in the diagram, the state of th=
e AS
> >   -------------------------
> >
> > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > Whenever AS state-change happens at SGP, a NTFY will be sent to all=

ASPes
> > (other than DOWN-ASPes) pertaining to the same RC.
> > This is what i remember that everybody agreed.
> >
> > --Samuel
> > > does not change with the second ASP (ASP2) sending ASPUP.  The AS=

> changes
> > > state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram=

should
> > > show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately aft=
er
the
> > > ASPUP Ack is sent to the ASP in question.
> > >
> > > The diagram is quite wrong.  Also it is wrong considering the cha=
nges
to
> > > be made to the next issue of the IG.
> > >
> > > --brian
> > >
> > > kakaul@hss.hns.com wrote:
> > (Tue, 05 Aug 2003 09:31:47)
> > > >
> > > >
> > > >
> > > >
> > > > On receiving ASPUP message from ASP3 state of AS does not chang=
e,
so
> > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > >
> > > > Kamesh
> > > >
> > > >
> > > >
> > > >
> > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003
11:40:01
> > AM
> > > >
> > > > Sent by:    sigtran-admin@ietf.org
> > > >
> > > >
> > > > To:    "sigtran" <sigtran@ietf.org>
> > > > cc:
> > > >
> > > > Subject:    [Sigtran] question about m3UA
> > > >
> > > >
> > > >
> > > >
> > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > > > NOTIFY(AS-INACTIVE)?
> > > >
> > > > Thanls
> > > >
> > > > Ling-Chih Kao
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > > _______________________________________________
> > > 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
> >
> >
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

_______________________________________________
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



From exim@www1.ietf.org  Fri Aug  8 04:49:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04123
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 04:49:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2vo-0001Fw-NS
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 04:49:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h788n4va004827
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 04:49:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2vk-0001FD-UJ; Fri, 08 Aug 2003 04:49:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2vc-0001Ei-HQ
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 04:48:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04111
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 04:48:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2vZ-0006sb-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:48:49 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2vY-0006sU-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:48:48 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h788mHB5024858;
	Fri, 8 Aug 2003 03:48:19 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h788lU1C025149;
	Fri, 8 Aug 2003 03:47:30 -0500 (CDT)
Date: Fri, 8 Aug 2003 03:47:30 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Ling-Chih Kao <d86942004@ntu.edu.tw>
cc: sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <010e01c35d83$e40ef3f0$6ec5900a@saoe.com>
Message-ID: <Pine.SOL.4.10.10308080340480.6428-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: QUOTED-PRINTABLE


Ling-Chih Kao and Brian,

In n+k reduntancy case,when n=3D2 that means ASP1 and ASP2 are going to
handle the traffic.So sending NTFY to these ASPes is mandatory.
Sending NTFY to ASP3 is an optional because it is not going to handle=20
the traffic.When ASP1 or ASP2 goes down then ASP3 will come up to take
over the traffic this case SGP will send a NTFY message with AS state,
here it is mandatory to send NTFY to ASP3.

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 8 Aug 2003, Ling-Chih Kao wrote:

> Dear Samuel Dur D. Jeyaseelan
>=20
>=20
> From the new definition of AS-INACTIVE in sec 4.3.2 of
> draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS becomes
> AS-INACTIVE when there are at least n ASPs in either ASP-INACTIVE or
> AS-ACTIVE.
>=20
> Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP receives two AS=
P
> UP (from ASP1 and ASP2).  However, when the SGP receives  ASP UP from ASP=
3,
> SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to know whether i=
t
> is optional or not?
>=20
> Thanks.
> Ling-Chih Kao
>=20
> ----- Original Message -----
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> Cc: "sigtran" <sigtran@ietf.org>
> Sent: Friday, August 08, 2003 3:41 PM
> Subject: Re: [Sigtran] question about m3UA
>=20
>=20
>=20
> Ling-Chih Kao,
>=20
> NTFY(AS-INACT) is sent to all all available peer ASPes.
> Note: Available peer means an ASP which received ASP-UP-ACK
> in response to ASP-UP messages.(as per RFC section 4.3.4.1).
>=20
> If you active the AS as soon as a single ASP goes to ASP-INACT
> state then it is obvious that whoever sends ASP-UP message to
> SGP, immediately SGP will send a NTFY(AS-INACT) to the concern
> ASP followd by ASP-UP-ACK.
>=20
>=20
> --Samuel
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.c=
om
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *****=
**
>=20
> On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
>=20
> > Hi all,
> >
> > After SGP receives the ASP UP from ASP1, SGP should immediately send
> > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?
> >
> > Thanks
> >
> > Ling-Chih Kao
> > ----- Original Message -----
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw>;
> "sigtran"
> > <sigtran@ietf.org>
> > Sent: Tuesday, August 05, 2003 1:22 PM
> > Subject: Re: [Sigtran] question about m3UA
> >
> >
> >
> > Brian,
> >
> > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> >
> > > kakaul,
> > >
> > > But I think that we agreed that it would be wise to tell newly inacti=
ve
> >                                                       -----------------=
-
> > > ASPs that state of the AS.  Also, in the diagram, the state of the AS
> >   -------------------------
> >
> > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > Whenever AS state-change happens at SGP, a NTFY will be sent to all ASP=
es
> > (other than DOWN-ASPes) pertaining to the same RC.
> > This is what i remember that everybody agreed.
> >
> > --Samuel
> > > does not change with the second ASP (ASP2) sending ASPUP.  The AS
> changes
> > > state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram sho=
uld
> > > show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately after t=
he
> > > ASPUP Ack is sent to the ASP in question.
> > >
> > > The diagram is quite wrong.  Also it is wrong considering the changes=
 to
> > > be made to the next issue of the IG.
> > >
> > > --brian
> > >
> > > kakaul@hss.hns.com wrote:
> > (Tue, 05 Aug 2003 09:31:47)
> > > >
> > > >
> > > >
> > > >
> > > > On receiving ASPUP message from ASP3 state of AS does not change, s=
o
> > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > >
> > > > Kamesh
> > > >
> > > >
> > > >
> > > >
> > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003 11:40=
:01
> > AM
> > > >
> > > > Sent by:    sigtran-admin@ietf.org
> > > >
> > > >
> > > > To:    "sigtran" <sigtran@ietf.org>
> > > > cc:
> > > >
> > > > Subject:    [Sigtran] question about m3UA
> > > >
> > > >
> > > >
> > > >
> > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > > > NOTIFY(AS-INACTIVE)?
> > > >
> > > > Thanls
> > > >
> > > > Ling-Chih Kao
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > > _______________________________________________
> > > 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
> >
> >
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20


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



From exim@www1.ietf.org  Fri Aug  8 04:50:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04170
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 04:50:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2wj-0001PX-7Y
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 04:50:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h788o11Q005412
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 04:50:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2wj-0001PB-0m; Fri, 08 Aug 2003 04:50:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2wZ-0001OZ-G0
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 04:49:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04148
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 04:49:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2wW-0006t7-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:49:48 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[XiNaW4tiMy8wGlZZwY7rNnhHn2cCQKM3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2wV-0006t3-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:49:47 -0400
Received: from ns.pigworks.openss7.net (IDENT:N7oviyUSp34ZdXnUU8uxnwCh8dVpsSYd@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h788nlE14475;
	Fri, 8 Aug 2003 02:49:47 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h788nkP25031;
	Fri, 8 Aug 2003 02:49:46 -0600
Date: Fri, 8 Aug 2003 02:49:46 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Valerie Gastaud <valerie.gastaud@ulticom.com>
Cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        "Anzile, Christophe" <christophe.anzile@hp.com>,
        Sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] SUA - RC in CLDT
Message-ID: <20030808024946.J23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Valerie Gastaud <valerie.gastaud@ulticom.com>,
	"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	"Anzile, Christophe" <christophe.anzile@hp.com>,
	Sigtran <sigtran@ietf.org>
References: <20030808010650.E23030@openss7.org> <NDBBIHAOCKGAMIKNLALOEEODDOAA.valerie.gastaud@ulticom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <NDBBIHAOCKGAMIKNLALOEEODDOAA.valerie.gastaud@ulticom.com>; from valerie.gastaud@ulticom.com on Fri, Aug 08, 2003 at 10:19:25AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Valerie,

Valerie Gastaud wrote:                                                             (Fri, 08 Aug 2003 10:19:25)
> 
> All,
> 
> It is clear for M3UA: RC is conditional in the ASPAC/ack and data and the
> rule is:
> - an ASP serves only one AS across a common association => it is possible
> not to configure/exchange RC, neither in ASPAC/ack nor in data.
> - an ASP serves multiple ASes across one association => RCs must be used.
> 
> If we use the same rule for SUA, then the RC in the SUA data must be
> modified from Mandatory to Conditional. If we keep RC mandatory in the SUA
> data, then even if one ASP serves a single AS, we are forced to exchange a
> RC.
> 
> Brian, if RC is mandatory in all SUA messages as you suggest, does this mean
> that you consider that one SUA ASP will never serve a single AS?

No, just if an ASP serves a single AS then it would configure a
single RC value and include it where mandatory.

The ASP that can only serve a single AS has little use or value for SUA.
(And questionable use or value for M3UA.)

--brian


> 
> Valerie
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: vendredi 8 aout 2003 09:07
> To: Samuel Dur D. Jeyaseelan
> Cc: Anzile, Christophe; Valerie Gastaud; Sigtran
> Subject: Re: [Sigtran] SUA - RC in CLDT
> 
> 
> Samuel,
> 
> The M3UA IG section 3.5 changes "optional" to "conditional" everywhere
> for RC to indicate this explicitly.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:
> (Fri, 08 Aug 2003 01:58:42)
> >
> > Everybody,
> >
> > RC is a mandatory field when an ASP serves more than one AS.
> > A single ASP ACTIVE message without RC can not be used to active
> > multiple ASes across a common SCTP association.RFC does not explicitely
> > say that RC is mandatory when an ASP serves
> > multiple ASes across a common association.But it is implied.
> >
> > RFC has given a flexibility that RC is an optional field when it serves
> > a single AS.
> >
> > Say an example, an ASP1 serves multiple ASes and has been connected to
> > SGP1.If RC is an optional parameter to activate all ASes, the potential
> > problem is, while sending DATA messages to ASP1,
> >
> > 1) How does ASP1 relate the DATA message with an appropriate AS?
> >
> > 2) Suppose AS2 goes down, How does AS2 indicate this to SGP1?(remeber
> >    RC has not been communicated between SGP1 and AS2)
> >
> > 3) Suppose SGP1 wants to put AS1 in DOWN state for some kind of
> >    configuration purpose, How does SGP1 communicate this with AS1 without
> >    RC?
> >
> > RFC implicitely says that RC is a mandatory field when an ASP serves
> > more than one ASes.
> >
> > --Samuel
> >
> >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> *******
> >
> > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> >
> > > Anzile,,
> > >
> > > Anzile, Christophe wrote:
> (Thu, 07 Aug 2003 11:24:09)
> > > > Brian (& Valerie),
> > > >
> > > > Please do not make RC mandatory in ASPAC, or you'll have strong side
> effects on the draft..
> > > > This is not consistent at all with what's written in the draft page
> 92, ie
> > > >  [ it is not necessary for the ASP to
> > > >    include all Routing Contexts of interest in a single ASP Active
> > > >    message, thus requesting to become active in all Routing Contexts
> at
> > > >    the same time.  Multiple ASP Active messages MAY be used to
> activate
> > > >    within the Application Servers independently, or in sets.  In the
> > > >    case where an ASP Active message does not contain a Routing Context
> > > >    parameter, the receiver must know, via configuration data, which
> > > >    Application Server(s) the ASP is a member. ]
> > > >
> > > > -> This is clear that if no RC is present in the ASPAC, it should be
> considered as a wildcard
> > > > for all AS statically configured in the SG..
> > >
> > > No, that is not what it means.  If RC is not included, only a single AS
> can
> > > exist for the SCTP association.
> > >
> > >
> > > > In return, SG should send back all RCs activated in the ASPAC-ACK msg.
> > >
> > > No.  If there is no RC in ASPAC there may be no RC in ASPAC Ack.
> > >
> > > >
> > > > -> This is why RC is therefore mandatory in CLDT/CLDR.
> > >
> > > Don't think so...
> > >
> > > --brian
> > >
> > > >
> > > >
> > > > Christophe.
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: Thursday, August 07, 2003 9:18 AM
> > > > To: Valerie Gastaud
> > > > Cc: Sigtran
> > > > Subject: Re: [Sigtran] SUA - RC in CLDT
> > > >
> > > >
> > > > Valerie,
> > > >
> > > > SUA had RC mandatory in all messages.  This was just a cut and paste
> error
> > > > from "common UA procedures".  The SUA draft should be corrected to
> make RC
> > > > mandatory in ASPAC.  Although it may make some sense to M2UA and even
> M3UA
> > > > to have RC optional in ASPAC, it makes little sense in SUA.  This is
> why
> > > > RC is mandatory in all messages in SUA.
> > > >
> > > > --brian
> > > >
> > > > Valerie Gastaud wrote:
> (Wed, 06 Aug 2003 15:33:59)
> > > > >
> > > > > Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2
> messages)?
> > > > > This is not consistent with M3UA and this is not consistent with the
> SUA
> > > > > ASPAC message in which the RC is optional.
> > > > > In case of static provisioning of RK, if an SGP receives an ASPAC
> w/o RC, it
> > > > > won't be able to insert the RC in the CLDT.
> > > > >
> > > > > Valerie
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > > > --
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> 
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 04:54:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04301
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 04:54:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l30c-0001ba-Hk
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 04:54:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h788s2cH006162
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 04:54:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l30b-0001b3-Pl; Fri, 08 Aug 2003 04:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2zt-0001aP-VL
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 04:53:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04287
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 04:53:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2zq-0006vT-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:53:14 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[ekz+PdNWc/2iRHCB3K9+b4ka0/MmYIsO])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2zp-0006vO-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:53:13 -0400
Received: from ns.pigworks.openss7.net (IDENT:k2z/Rq34S0JxgN/FidolaUZxBeeZznaR@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h788rEE14523;
	Fri, 8 Aug 2003 02:53:14 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h788rEJ25071;
	Fri, 8 Aug 2003 02:53:14 -0600
Date: Fri, 8 Aug 2003 02:53:13 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030808025313.K23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
References: <010e01c35d83$e40ef3f0$6ec5900a@saoe.com> <Pine.SOL.4.10.10308080340480.6428-100000@sun2685.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10308080340480.6428-100000@sun2685.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Aug 08, 2003 at 03:47:30AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h788rEE14523
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Samuel,

None of the ASPs are handling traffic at that point.  Who is to say
that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perhaps ASP2
and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely doesn't know.
Sending NTFY(AS-INACTIVE) to all of them is the wisest choice.

--brian

Samuel Dur D. Jeyaseelan wrote:                                          =
           (Fri, 08 Aug 2003 03:47:30)
>=20
> Ling-Chih Kao and Brian,
>=20
> In n+k reduntancy case,when n=3D2 that means ASP1 and ASP2 are going to
> handle the traffic.So sending NTFY to these ASPes is mandatory.
> Sending NTFY to ASP3 is an optional because it is not going to handle=20
> the traffic.When ASP1 or ASP2 goes down then ASP3 will come up to take
> over the traffic this case SGP will send a NTFY message with AS state,
> here it is mandatory to send NTFY to ASP3.
>=20
> --Samuel
>=20
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
>=20
> On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
>=20
> > Dear Samuel Dur D. Jeyaseelan
> >=20
> >=20
> > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS becomes
> > AS-INACTIVE when there are at least n ASPs in either ASP-INACTIVE or
> > AS-ACTIVE.
> >=20
> > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP receives tw=
o ASP
> > UP (from ASP1 and ASP2).  However, when the SGP receives  ASP UP from=
 ASP3,
> > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to know wheth=
er it
> > is optional or not?
> >=20
> > Thanks.
> > Ling-Chih Kao
> >=20
> > ----- Original Message -----
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > Cc: "sigtran" <sigtran@ietf.org>
> > Sent: Friday, August 08, 2003 3:41 PM
> > Subject: Re: [Sigtran] question about m3UA
> >=20
> >=20
> >=20
> > Ling-Chih Kao,
> >=20
> > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > Note: Available peer means an ASP which received ASP-UP-ACK
> > in response to ASP-UP messages.(as per RFC section 4.3.4.1).
> >=20
> > If you active the AS as soon as a single ASP goes to ASP-INACT
> > state then it is obvious that whoever sends ASP-UP message to
> > SGP, immediately SGP will send a NTFY(AS-INACT) to the concern
> > ASP followd by ASP-UP-ACK.
> >=20
> >=20
> > --Samuel
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcat=
el.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. *=
******
> >=20
> > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> >=20
> > > Hi all,
> > >
> > > After SGP receives the ASP UP from ASP1, SGP should immediately sen=
d
> > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?
> > >
> > > Thanks
> > >
> > > Ling-Chih Kao
> > > ----- Original Message -----
> > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw>;
> > "sigtran"
> > > <sigtran@ietf.org>
> > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > Subject: Re: [Sigtran] question about m3UA
> > >
> > >
> > >
> > > Brian,
> > >
> > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > >
> > > > kakaul,
> > > >
> > > > But I think that we agreed that it would be wise to tell newly in=
active
> > >                                                       -------------=
-----
> > > > ASPs that state of the AS.  Also, in the diagram, the state of th=
e AS
> > >   -------------------------
> > >
> > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > Whenever AS state-change happens at SGP, a NTFY will be sent to all=
 ASPes
> > > (other than DOWN-ASPes) pertaining to the same RC.
> > > This is what i remember that everybody agreed.
> > >
> > > --Samuel
> > > > does not change with the second ASP (ASP2) sending ASPUP.  The AS
> > changes
> > > > state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram=
 should
> > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately aft=
er the
> > > > ASPUP Ack is sent to the ASP in question.
> > > >
> > > > The diagram is quite wrong.  Also it is wrong considering the cha=
nges to
> > > > be made to the next issue of the IG.
> > > >
> > > > --brian
> > > >
> > > > kakaul@hss.hns.com wrote:
> > > (Tue, 05 Aug 2003 09:31:47)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On receiving ASPUP message from ASP3 state of AS does not chang=
e, so
> > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > >
> > > > > Kamesh
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003 1=
1:40:01
> > > AM
> > > > >
> > > > > Sent by:    sigtran-admin@ietf.org
> > > > >
> > > > >
> > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > cc:
> > > > >
> > > > > Subject:    [Sigtran] question about m3UA
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > > > > NOTIFY(AS-INACTIVE)?
> > > > >
> > > > > Thanls
> > > > >
> > > > > Ling-Chih Kao
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > > > --
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >
> > > > _______________________________________________
> > > > 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
> > >
> > >
> >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> >=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 04:58:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04366
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 04:58:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l34T-0001ju-AJ
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 04:58:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h788w1NI006679
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 04:58:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l34S-0001jV-Np; Fri, 08 Aug 2003 04:58:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l33Z-0001j4-0C
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 04:57:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04358
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 04:56:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l33V-0006x1-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:57:01 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[HKz6SC1K/OmNZVSd+OWIERnT4TjAMu2H])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l33V-0006wy-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:57:01 -0400
Received: from ns.pigworks.openss7.net (IDENT:EBk+eTID9mPhzmQn5BRWRKhtpbYZ1/+P@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h788v1E14567;
	Fri, 8 Aug 2003 02:57:01 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h788v1T25104;
	Fri, 8 Aug 2003 02:57:01 -0600
Date: Fri, 8 Aug 2003 02:57:01 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: kakaul@hss.hns.com
Cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030808025701.L23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: kakaul@hss.hns.com, Ling-Chih Kao <d86942004@ntu.edu.tw>,
	sigtran <sigtran@ietf.org>
References: <OFD74D207E.819856CA-ON65256D7C.002D5CF6@hss.hns.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OFD74D207E.819856CA-ON65256D7C.002D5CF6@hss.hns.com>; from kakaul@hss.hns.com on Fri, Aug 08, 2003 at 01:54:54PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h788v1E14567
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

kakaul,

kakaul@hss.hns.com wrote:                                                =
           (Fri, 08 Aug 2003 13:54:54)
>=20
>=20
>=20
>=20
> Brian,
>    Do you mean to say that whenever new ASP is sending ASPUP or ASPAC(f=
or
> an AS) which does not result in AS state change at SGP.SGP  responds  w=
ith
> ACK and NOTIFY(AS).
> Right ?

Only when the new ASP sends ASPUP.  Becase before that point, the ASP has
not received any notifications.  Notifications are only sent to ASPs in
the ASP-INACTIVE state for the AS and not in the ASP-DOWN state.


> What should ASP do with that NOTIFY.

Take it under advisement in the same manner as the other ASPs receiving
NTFY(AS-INACTIVE).  As with the other ASPs, this ASP may choose based on
this and any other information that it has at its disposal about the
intentions of other ASPs, to send ASPAC (or not) for the AS.

--brian


>=20
> Regards
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>=20
>=20
>=20
>=20
> "Brian F. G. Bidulock" <bidulock@openss7.org>@ietf.org on 08/08/2003
> 01:43:16 PM
>=20
> Please respond to bidulock@openss7.org
>=20
> Sent by:    sigtran-admin@ietf.org
>=20
>=20
> To:    Ling-Chih Kao <d86942004@ntu.edu.tw>
> cc:    sigtran <sigtran@ietf.org>
>=20
> Subject:    Re: [Sigtran] question about m3UA
>=20
>=20
> Ling-Chih,
>=20
> We agreed it was a good idea to send it, even though there is no
> text in the RFC that explicitly requires it.
>=20
> It might be a good idea to add "SHOULD" text to the IG and correct
> the diagram 5.1.4.
>=20
> --brian
>=20
> Ling-Chih Kao wrote:
> (Fri, 08 Aug 2003 16:05:53)
> > Dear Samuel Dur D. Jeyaseelan
> >
> >
> > >From the new definition of AS-INACTIVE in sec 4.3.2 of
> > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS becomes
> > AS-INACTIVE when there are at least n ASPs in either ASP-INACTIVE or
> > AS-ACTIVE.
> >
> > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP receives tw=
o
> ASP
> > UP (from ASP1 and ASP2).  However, when the SGP receives  ASP UP from
> ASP3,
> > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to know wheth=
er
> it
> > is optional or not?
> >
> > Thanks.
> > Ling-Chih Kao
> >
> > ----- Original Message -----
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > Cc: "sigtran" <sigtran@ietf.org>
> > Sent: Friday, August 08, 2003 3:41 PM
> > Subject: Re: [Sigtran] question about m3UA
> >
> >
> >
> > Ling-Chih Kao,
> >
> > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > Note: Available peer means an ASP which received ASP-UP-ACK
> > in response to ASP-UP messages.(as per RFC section 4.3.4.1).
> >
> > If you active the AS as soon as a single ASP goes to ASP-INACT
> > state then it is obvious that whoever sends ASP-UP message to
> > SGP, immediately SGP will send a NTFY(AS-INACT) to the concern
> > ASP followd by ASP-UP-ACK.
> >
> >
> > --Samuel
> >   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> *******
> >
> > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> >
> > > Hi all,
> > >
> > > After SGP receives the ASP UP from ASP1, SGP should immediately sen=
d
> > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?
> > >
> > > Thanks
> > >
> > > Ling-Chih Kao
> > > ----- Original Message -----
> > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw>;
> > "sigtran"
> > > <sigtran@ietf.org>
> > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > Subject: Re: [Sigtran] question about m3UA
> > >
> > >
> > >
> > > Brian,
> > >
> > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > >
> > > > kakaul,
> > > >
> > > > But I think that we agreed that it would be wise to tell newly
> inactive
> > >
> ------------------
> > > > ASPs that state of the AS.  Also, in the diagram, the state of th=
e AS
> > >   -------------------------
> > >
> > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > Whenever AS state-change happens at SGP, a NTFY will be sent to all
> ASPes
> > > (other than DOWN-ASPes) pertaining to the same RC.
> > > This is what i remember that everybody agreed.
> > >
> > > --Samuel
> > > > does not change with the second ASP (ASP2) sending ASPUP.  The AS
> > changes
> > > > state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram
> should
> > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately aft=
er
> the
> > > > ASPUP Ack is sent to the ASP in question.
> > > >
> > > > The diagram is quite wrong.  Also it is wrong considering the cha=
nges
> to
> > > > be made to the next issue of the IG.
> > > >
> > > > --brian
> > > >
> > > > kakaul@hss.hns.com wrote:
> > > (Tue, 05 Aug 2003 09:31:47)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On receiving ASPUP message from ASP3 state of AS does not chang=
e,
> so
> > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > >
> > > > > Kamesh
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003
> 11:40:01
> > > AM
> > > > >
> > > > > Sent by:    sigtran-admin@ietf.org
> > > > >
> > > > >
> > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > cc:
> > > > >
> > > > > Subject:    [Sigtran] question about m3UA
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > > > > NOTIFY(AS-INACTIVE)?
> > > > >
> > > > > Thanls
> > > > >
> > > > > Ling-Chih Kao
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > > > --
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >
> > > > _______________________________________________
> > > > 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
> > >
> > >
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
>  https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 05:06:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04666
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 05:06:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3CE-00025M-KI
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 05:06:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h78962XY008009
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 05:06:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3CD-00024x-PW; Fri, 08 Aug 2003 05:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3C9-00024i-VD
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 05:05:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04659
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 05:05:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3C6-00072C-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:05:54 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3C0-00071k-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:05:48 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h7895IB5025500;
	Fri, 8 Aug 2003 04:05:19 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h7894o1C028246;
	Fri, 8 Aug 2003 04:04:50 -0500 (CDT)
Date: Fri, 8 Aug 2003 04:04:50 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <20030808025313.K23030@openss7.org>
Message-ID: <Pine.SOL.4.10.10308080356430.6428-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: QUOTED-PRINTABLE


Brian,

  I meant first 2 ASPes will receive NTFY messages.Sending NTFY to=20
  3rd ASP is an optional.Do you have any problem here?

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:

> Samuel,
>=20
> None of the ASPs are handling traffic at that point.  Who is to say
> that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perhaps ASP2
> and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely doesn't know.
> Sending NTFY(AS-INACTIVE) to all of them is the wisest choice.
>=20
> --brian
>=20
> Samuel Dur D. Jeyaseelan wrote:                                          =
           (Fri, 08 Aug 2003 03:47:30)
> >=20
> > Ling-Chih Kao and Brian,
> >=20
> > In n+k reduntancy case,when n=3D2 that means ASP1 and ASP2 are going to
> > handle the traffic.So sending NTFY to these ASPes is mandatory.
> > Sending NTFY to ASP3 is an optional because it is not going to handle=
=20
> > the traffic.When ASP1 or ASP2 goes down then ASP3 will come up to take
> > over the traffic this case SGP will send a NTFY message with AS state,
> > here it is mandatory to send NTFY to ASP3.
> >=20
> > --Samuel
> >=20
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
=2Ecom
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
> >=20
> > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> >=20
> > > Dear Samuel Dur D. Jeyaseelan
> > >=20
> > >=20
> > > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS becomes
> > > AS-INACTIVE when there are at least n ASPs in either ASP-INACTIVE or
> > > AS-ACTIVE.
> > >=20
> > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP receives tw=
o ASP
> > > UP (from ASP1 and ASP2).  However, when the SGP receives  ASP UP from=
 ASP3,
> > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to know wheth=
er it
> > > is optional or not?
> > >=20
> > > Thanks.
> > > Ling-Chih Kao
> > >=20
> > > ----- Original Message -----
> > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > Cc: "sigtran" <sigtran@ietf.org>
> > > Sent: Friday, August 08, 2003 3:41 PM
> > > Subject: Re: [Sigtran] question about m3UA
> > >=20
> > >=20
> > >=20
> > > Ling-Chih Kao,
> > >=20
> > > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > > Note: Available peer means an ASP which received ASP-UP-ACK
> > > in response to ASP-UP messages.(as per RFC section 4.3.4.1).
> > >=20
> > > If you active the AS as soon as a single ASP goes to ASP-INACT
> > > state then it is obvious that whoever sends ASP-UP message to
> > > SGP, immediately SGP will send a NTFY(AS-INACT) to the concern
> > > ASP followd by ASP-UP-ACK.
> > >=20
> > >=20
> > > --Samuel
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcat=
el.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc. *=
******
> > >=20
> > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > >=20
> > > > Hi all,
> > > >
> > > > After SGP receives the ASP UP from ASP1, SGP should immediately sen=
d
> > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?
> > > >
> > > > Thanks
> > > >
> > > > Ling-Chih Kao
> > > > ----- Original Message -----
> > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw>;
> > > "sigtran"
> > > > <sigtran@ietf.org>
> > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > Subject: Re: [Sigtran] question about m3UA
> > > >
> > > >
> > > >
> > > > Brian,
> > > >
> > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > >
> > > > > kakaul,
> > > > >
> > > > > But I think that we agreed that it would be wise to tell newly in=
active
> > > >                                                       -------------=
-----
> > > > > ASPs that state of the AS.  Also, in the diagram, the state of th=
e AS
> > > >   -------------------------
> > > >
> > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > Whenever AS state-change happens at SGP, a NTFY will be sent to all=
 ASPes
> > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > This is what i remember that everybody agreed.
> > > >
> > > > --Samuel
> > > > > does not change with the second ASP (ASP2) sending ASPUP.  The AS
> > > changes
> > > > > state to AS-INACTIVE with ASP1 coming up.  Therefore, the diagram=
 should
> > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately aft=
er the
> > > > > ASPUP Ack is sent to the ASP in question.
> > > > >
> > > > > The diagram is quite wrong.  Also it is wrong considering the cha=
nges to
> > > > > be made to the next issue of the IG.
> > > > >
> > > > > --brian
> > > > >
> > > > > kakaul@hss.hns.com wrote:
> > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On receiving ASPUP message from ASP3 state of AS does not chang=
e, so
> > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > >
> > > > > > Kamesh
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/2003 1=
1:40:01
> > > > AM
> > > > > >
> > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > >
> > > > > >
> > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > cc:
> > > > > >
> > > > > > Subject:    [Sigtran] question about m3UA
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > > > > > NOTIFY(AS-INACTIVE)?
> > > > > >
> > > > > > Thanls
> > > > > >
> > > > > > Ling-Chih Kao
> > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >
> > > > > --
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >
> > > > > _______________________________________________
> > > > > 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
> > > >
> > > >
> > >=20
> > >=20
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >=20
> > >=20
> >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
>=20


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



From exim@www1.ietf.org  Fri Aug  8 05:08:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04725
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 05:08:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3EA-0002UW-38
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 05:08:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h78982Vi009556
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 05:08:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3E9-0002Tz-Ui; Fri, 08 Aug 2003 05:08:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Dz-0002Rn-1l
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 05:07:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04711
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 05:07:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3Dv-000732-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:07:47 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[I+h9GCEAhRYw5vRItzS9GYFsr2OE/lTo])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3Du-00072z-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:07:47 -0400
Received: from ns.pigworks.openss7.net (IDENT:zeyh9IklobbMObL0N9toPDV8YLcw7zvG@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h7897lE14813;
	Fri, 8 Aug 2003 03:07:47 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h7897l925363;
	Fri, 8 Aug 2003 03:07:47 -0600
Date: Fri, 8 Aug 2003 03:07:47 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030808030747.N23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
References: <20030808025313.K23030@openss7.org> <Pine.SOL.4.10.10308080356430.6428-100000@sun2685.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10308080356430.6428-100000@sun2685.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Aug 08, 2003 at 04:04:50AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h7897lE14813
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Samuel,

Yes, I have a problem, because it is a race condition.

--brian

Samuel Dur D. Jeyaseelan wrote:                                          =
           (Fri, 08 Aug 2003 04:04:50)
>=20
> Brian,
>=20
>   I meant first 2 ASPes will receive NTFY messages.Sending NTFY to=20
>   3rd ASP is an optional.Do you have any problem here?
>=20
> --Samuel
>=20
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
>=20
> On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
>=20
> > Samuel,
> >=20
> > None of the ASPs are handling traffic at that point.  Who is to say
> > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perhaps ASP2
> > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely doesn't kno=
w.
> > Sending NTFY(AS-INACTIVE) to all of them is the wisest choice.
> >=20
> > --brian
> >=20
> > Samuel Dur D. Jeyaseelan wrote:                                      =
               (Fri, 08 Aug 2003 03:47:30)
> > >=20
> > > Ling-Chih Kao and Brian,
> > >=20
> > > In n+k reduntancy case,when n=3D2 that means ASP1 and ASP2 are goin=
g to
> > > handle the traffic.So sending NTFY to these ASPes is mandatory.
> > > Sending NTFY to ASP3 is an optional because it is not going to hand=
le=20
> > > the traffic.When ASP1 or ASP2 goes down then ASP3 will come up to t=
ake
> > > over the traffic this case SGP will send a NTFY message with AS sta=
te,
> > > here it is mandatory to send NTFY to ASP3.
> > >=20
> > > --Samuel
> > >=20
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alc=
atel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc.=
 *******
> > >=20
> > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > >=20
> > > > Dear Samuel Dur D. Jeyaseelan
> > > >=20
> > > >=20
> > > > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS become=
s
> > > > AS-INACTIVE when there are at least n ASPs in either ASP-INACTIVE=
 or
> > > > AS-ACTIVE.
> > > >=20
> > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP receive=
s two ASP
> > > > UP (from ASP1 and ASP2).  However, when the SGP receives  ASP UP =
from ASP3,
> > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to know w=
hether it
> > > > is optional or not?
> > > >=20
> > > > Thanks.
> > > > Ling-Chih Kao
> > > >=20
> > > > ----- Original Message -----
> > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > Subject: Re: [Sigtran] question about m3UA
> > > >=20
> > > >=20
> > > >=20
> > > > Ling-Chih Kao,
> > > >=20
> > > > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > > > Note: Available peer means an ASP which received ASP-UP-ACK
> > > > in response to ASP-UP messages.(as per RFC section 4.3.4.1).
> > > >=20
> > > > If you active the AS as soon as a single ASP goes to ASP-INACT
> > > > state then it is obvious that whoever sends ASP-UP message to
> > > > SGP, immediately SGP will send a NTFY(AS-INACT) to the concern
> > > > ASP followd by ASP-UP-ACK.
> > > >=20
> > > >=20
> > > > --Samuel
> > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.a=
lcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, In=
c. *******
> > > >=20
> > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > >=20
> > > > > Hi all,
> > > > >
> > > > > After SGP receives the ASP UP from ASP1, SGP should immediately=
 send
> > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Ling-Chih Kao
> > > > > ----- Original Message -----
> > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw=
>;
> > > > "sigtran"
> > > > > <sigtran@ietf.org>
> > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > Subject: Re: [Sigtran] question about m3UA
> > > > >
> > > > >
> > > > >
> > > > > Brian,
> > > > >
> > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > >
> > > > > > kakaul,
> > > > > >
> > > > > > But I think that we agreed that it would be wise to tell newl=
y inactive
> > > > >                                                       ---------=
---------
> > > > > > ASPs that state of the AS.  Also, in the diagram, the state o=
f the AS
> > > > >   -------------------------
> > > > >
> > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > Whenever AS state-change happens at SGP, a NTFY will be sent to=
 all ASPes
> > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > This is what i remember that everybody agreed.
> > > > >
> > > > > --Samuel
> > > > > > does not change with the second ASP (ASP2) sending ASPUP.  Th=
e AS
> > > > changes
> > > > > > state to AS-INACTIVE with ASP1 coming up.  Therefore, the dia=
gram should
> > > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately=
 after the
> > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > >
> > > > > > The diagram is quite wrong.  Also it is wrong considering the=
 changes to
> > > > > > be made to the next issue of the IG.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > kakaul@hss.hns.com wrote:
> > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On receiving ASPUP message from ASP3 state of AS does not c=
hange, so
> > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > >
> > > > > > > Kamesh
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/20=
03 11:40:01
> > > > > AM
> > > > > > >
> > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > >
> > > > > > >
> > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > cc:
> > > > > > >
> > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > >
> > > > > > > Thanls
> > > > > > >
> > > > > > > Ling-Chih Kao
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Sigtran mailing list
> > > > > > > Sigtran@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > >
> > > > > > --
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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
> > > > >
> > > > >
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >=20
> > > >=20
> > >=20
> > >=20
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >=20
> >=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 05:13:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04844
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 05:13:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Iz-0002f9-Q3
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 05:13:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h789D1dd010229
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 05:13:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Iy-0002ch-VO; Fri, 08 Aug 2003 05:13:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3IF-0002bO-CX
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 05:12:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04822
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 05:12:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3IC-00075w-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:12:12 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[t4VlRr/RCQceyajcUtfInUjNsrUvKHUJ])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3IB-00075s-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:12:11 -0400
Received: from ns.pigworks.openss7.net (IDENT:/VPJ7WhovdA9foJm0kRVqNVClKPeMFB4@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h789CCE14868;
	Fri, 8 Aug 2003 03:12:12 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h789CBH25404;
	Fri, 8 Aug 2003 03:12:11 -0600
Date: Fri, 8 Aug 2003 03:12:11 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Anzile, Christophe" <christophe.anzile@hp.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] SUA - RC in CLDT
Message-ID: <20030808031211.O23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Anzile, Christophe" <christophe.anzile@hp.com>,
	sigtran@ietf.org
References: <BE462396B4A022449E0EB2DD4753D05402F26B1F@vbeexc02.emea.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <BE462396B4A022449E0EB2DD4753D05402F26B1F@vbeexc02.emea.cpqcorp.net>; from christophe.anzile@hp.com on Fri, Aug 08, 2003 at 10:34:13AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h789CCE14868
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Anzile,,

We already discussed for M3UA that the '(s)' in the following passage
should be struck.  The same argument applies to SUA:

  "In the case where an ASP Active message does not contain a Routing
   Context parameter, the receive must know, via configuration data,
   [of] which Application Server(s) the ASP is a member."

Should read:

  "In the case where an ASP Active message does not contain a Routing
   Context parameter, the receive must know, via configuration data,
   [of] which Application Server the ASP is a member."

--brian

On Fri, 08 Aug 2003, Anzile, Christophe wrote:

> I agree about this section..=20
> what is confused to me is just the sentence following that one,
> the one talking about "all Routing Contexts" when it is supposed
> to have only one RC configured on the SG.
>=20
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: Friday, August 08, 2003 10:27 AM
> To: Anzile, Christophe
> Cc: Samuel Dur D. Jeyaseelan; Valerie Gastaud; Sigtran
> Subject: Re: [Sigtran] SUA - RC in CLDT
>=20
>=20
> Anzile,,
>=20
> SUA-15 was supposed to include some of the more stable changes from
> the M3UA IG where applicable to SUA.  Changing optional to conditional
> should have been one of them.
>=20
> Nevertheless, SUA-15 section 4.3.4.3 does say:
>=20
>   "...  In the case where an ASP wishes to process the traffic for
>    more than one Application Server across a common SCTP association,
>    the ASP Active message(s) SHOULD contain a list of one or more
>    Routing Contexts to indicate for which Application Servers the ASP
>    Active message applies. ..."
>=20
> Which is no different than M3UA.
>=20
> We can change optional to conditional against RC throughout.
>=20
> --brian
>=20
>=20
> Anzile, Christophe wrote:                                              =
            (Fri, 08 Aug 2003 10:12:27)
> > Brian,
> >=20
> > are we supposed to look at M3UA IG when implementing SUA ?
> > if yes, it would be nice to rename it.
> > if no, it would be nice if John could clarify the SUA draft especiall=
y the 4.3.4.3 section
> > and use "conditional" instead of "optional" when it applies.
> >=20
> >=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Friday, August 08, 2003 9:07 AM
> > To: Samuel Dur D. Jeyaseelan
> > Cc: Anzile, Christophe; Valerie Gastaud; Sigtran
> > Subject: Re: [Sigtran] SUA - RC in CLDT
> >=20
> >=20
> > Samuel,
> >=20
> > The M3UA IG section 3.5 changes "optional" to "conditional" everywher=
e
> > for RC to indicate this explicitly.
> >=20
> > --brian
> >=20
> > Samuel Dur D. Jeyaseelan wrote:                                      =
               (Fri, 08 Aug 2003 01:58:42)
> > >=20
> > > Everybody,
> > >=20
> > > RC is a mandatory field when an ASP serves more than one AS.
> > > A single ASP ACTIVE message without RC can not be used to active=20
> > > multiple ASes across a common SCTP association.RFC does not explici=
tely
> > > say that RC is mandatory when an ASP serves
> > > multiple ASes across a common association.But it is implied.
> > >=20
> > > RFC has given a flexibility that RC is an optional field when it se=
rves
> > > a single AS.
> > >=20
> > > Say an example, an ASP1 serves multiple ASes and has been connected=
 to=20
> > > SGP1.If RC is an optional parameter to activate all ASes, the poten=
tial
> > > problem is, while sending DATA messages to ASP1,=20
> > >=20
> > > 1) How does ASP1 relate the DATA message with an appropriate AS?
> > >=20
> > > 2) Suppose AS2 goes down, How does AS2 indicate this to SGP1?(remeb=
er=20
> > >    RC has not been communicated between SGP1 and AS2)
> > >=20
> > > 3) Suppose SGP1 wants to put AS1 in DOWN state for some kind of
> > >    configuration purpose, How does SGP1 communicate this with AS1 w=
ithout=20
> > >    RC?
> > >=20
> > > RFC implicitely says that RC is a mandatory field when an ASP serve=
s
> > > more than one ASes.
> > >=20
> > > --Samuel
> > >=20
> > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc.=
 *******
> > >=20
> > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > >=20
> > > > Anzile,,
> > > >=20
> > > > Anzile, Christophe wrote:                                        =
                  (Thu, 07 Aug 2003 11:24:09)
> > > > > Brian (& Valerie),
> > > > >=20
> > > > > Please do not make RC mandatory in ASPAC, or you'll have strong=
 side effects on the draft..
> > > > > This is not consistent at all with what's written in the draft =
page 92, ie
> > > > >  [ it is not necessary for the ASP to=20
> > > > >    include all Routing Contexts of interest in a single ASP Act=
ive=20
> > > > >    message, thus requesting to become active in all Routing Con=
texts at=20
> > > > >    the same time.  Multiple ASP Active messages MAY be used to =
activate=20
> > > > >    within the Application Servers independently, or in sets.  I=
n the=20
> > > > >    case where an ASP Active message does not contain a Routing =
Context=20
> > > > >    parameter, the receiver must know, via configuration data, w=
hich=20
> > > > >    Application Server(s) the ASP is a member. ]
> > > > >=20
> > > > > -> This is clear that if no RC is present in the ASPAC, it shou=
ld be considered as a wildcard
> > > > > for all AS statically configured in the SG..=20
> > > >=20
> > > > No, that is not what it means.  If RC is not included, only a sin=
gle AS can
> > > > exist for the SCTP association.
> > > >=20
> > > >=20
> > > > > In return, SG should send back all RCs activated in the ASPAC-A=
CK msg.
> > > >=20
> > > > No.  If there is no RC in ASPAC there may be no RC in ASPAC Ack.
> > > >=20
> > > > >=20
> > > > > -> This is why RC is therefore mandatory in CLDT/CLDR.
> > > >=20
> > > > Don't think so...
> > > >=20
> > > > --brian
> > > >=20
> > > > >=20
> > > > >=20
> > > > > Christophe.
> > > > >=20
> > > > >=20
> > > > > -----Original Message-----
> > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > Sent: Thursday, August 07, 2003 9:18 AM
> > > > > To: Valerie Gastaud
> > > > > Cc: Sigtran
> > > > > Subject: Re: [Sigtran] SUA - RC in CLDT
> > > > >=20
> > > > >=20
> > > > > Valerie,
> > > > >=20
> > > > > SUA had RC mandatory in all messages.  This was just a cut and =
paste error
> > > > > from "common UA procedures".  The SUA draft should be corrected=
 to make RC
> > > > > mandatory in ASPAC.  Although it may make some sense to M2UA an=
d even M3UA
> > > > > to have RC optional in ASPAC, it makes little sense in SUA.  Th=
is is why
> > > > > RC is mandatory in all messages in SUA.
> > > > >=20
> > > > > --brian
> > > > >=20
> > > > > Valerie Gastaud wrote:                                         =
                    (Wed, 06 Aug 2003 15:33:59)
> > > > > >=20
> > > > > > Why is RC mandatory in the SUA data messages (CLDT/CLDR + cla=
ss2 messages)?
> > > > > > This is not consistent with M3UA and this is not consistent w=
ith the SUA
> > > > > > ASPAC message in which the RC is optional.
> > > > > > In case of static provisioning of RK, if an SGP receives an A=
SPAC w/o RC, it
> > > > > > won't be able to insert the RC in the CLDT.
> > > > > >=20
> > > > > > Valerie
> > > > > >=20
> > > > > >=20
> > > > > >=20
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >=20
> > > > > --=20
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >=20
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >=20
> > > > --=20
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >=20
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >=20
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/

--=20
Brian F. G. Bidulock    =A6 The reasonable man adapts himself to the =A6
bidulock@openss7.org    =A6 world; the unreasonable one persists in  =A6
http://www.openss7.org/ =A6 trying  to adapt the  world  to himself. =A6
                        =A6 Therefore  all  progress  depends on the =A6
                        =A6 unreasonable man. -- George Bernard Shaw =A6

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



From exim@www1.ietf.org  Fri Aug  8 05:19:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04944
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 05:19:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Oo-0002sy-HK
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 05:19:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h789J2Oo011086
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 05:19:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3On-0002sa-UA; Fri, 08 Aug 2003 05:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Od-0002sF-Iz
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 05:18:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04932
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 05:18:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3Oa-00078I-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:18:48 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3OZ-00078E-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:18:47 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h789IIwA018427;
	Fri, 8 Aug 2003 04:18:18 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h789HV1C000491;
	Fri, 8 Aug 2003 04:17:31 -0500 (CDT)
Date: Fri, 8 Aug 2003 04:17:31 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <20030808030747.N23030@openss7.org>
Message-ID: <Pine.SOL.4.10.10308080409330.6428-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: QUOTED-PRINTABLE


Brian,
 Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, but ASP1 and
 ASP2 received NTFY(AS-INACT) but ASP3 did not.
 Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT message,
 here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1 and ASP3).

 This is the reason i said it is an optional of sending NTFY(AS-INACT)
 to 'n+1'th ASP.

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:

> Samuel,
>=20
> Yes, I have a problem, because it is a race condition.
>=20
> --brian
>=20
> Samuel Dur D. Jeyaseelan wrote:                                          =
           (Fri, 08 Aug 2003 04:04:50)
> >=20
> > Brian,
> >=20
> >   I meant first 2 ASPes will receive NTFY messages.Sending NTFY to=20
> >   3rd ASP is an optional.Do you have any problem here?
> >=20
> > --Samuel
> >=20
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
=2Ecom
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
> >=20
> > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> >=20
> > > Samuel,
> > >=20
> > > None of the ASPs are handling traffic at that point.  Who is to say
> > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perhaps ASP2
> > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely doesn't kno=
w.
> > > Sending NTFY(AS-INACTIVE) to all of them is the wisest choice.
> > >=20
> > > --brian
> > >=20
> > > Samuel Dur D. Jeyaseelan wrote:                                      =
               (Fri, 08 Aug 2003 03:47:30)
> > > >=20
> > > > Ling-Chih Kao and Brian,
> > > >=20
> > > > In n+k reduntancy case,when n=3D2 that means ASP1 and ASP2 are goin=
g to
> > > > handle the traffic.So sending NTFY to these ASPes is mandatory.
> > > > Sending NTFY to ASP3 is an optional because it is not going to hand=
le=20
> > > > the traffic.When ASP1 or ASP2 goes down then ASP3 will come up to t=
ake
> > > > over the traffic this case SGP will send a NTFY message with AS sta=
te,
> > > > here it is mandatory to send NTFY to ASP3.
> > > >=20
> > > > --Samuel
> > > >=20
> > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alc=
atel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.=
 *******
> > > >=20
> > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > >=20
> > > > > Dear Samuel Dur D. Jeyaseelan
> > > > >=20
> > > > >=20
> > > > > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS become=
s
> > > > > AS-INACTIVE when there are at least n ASPs in either ASP-INACTIVE=
 or
> > > > > AS-ACTIVE.
> > > > >=20
> > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP receive=
s two ASP
> > > > > UP (from ASP1 and ASP2).  However, when the SGP receives  ASP UP =
from ASP3,
> > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to know w=
hether it
> > > > > is optional or not?
> > > > >=20
> > > > > Thanks.
> > > > > Ling-Chih Kao
> > > > >=20
> > > > > ----- Original Message -----
> > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > Subject: Re: [Sigtran] question about m3UA
> > > > >=20
> > > > >=20
> > > > >=20
> > > > > Ling-Chih Kao,
> > > > >=20
> > > > > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > > > > Note: Available peer means an ASP which received ASP-UP-ACK
> > > > > in response to ASP-UP messages.(as per RFC section 4.3.4.1).
> > > > >=20
> > > > > If you active the AS as soon as a single ASP goes to ASP-INACT
> > > > > state then it is obvious that whoever sends ASP-UP message to
> > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to the concern
> > > > > ASP followd by ASP-UP-ACK.
> > > > >=20
> > > > >=20
> > > > > --Samuel
> > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.a=
lcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, In=
c. *******
> > > > >=20
> > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > >=20
> > > > > > Hi all,
> > > > > >
> > > > > > After SGP receives the ASP UP from ASP1, SGP should immediately=
 send
> > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this right?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Ling-Chih Kao
> > > > > > ----- Original Message -----
> > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.edu.tw=
>;
> > > > > "sigtran"
> > > > > > <sigtran@ietf.org>
> > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > >
> > > > > >
> > > > > >
> > > > > > Brian,
> > > > > >
> > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > >
> > > > > > > kakaul,
> > > > > > >
> > > > > > > But I think that we agreed that it would be wise to tell newl=
y inactive
> > > > > >                                                       ---------=
---------
> > > > > > > ASPs that state of the AS.  Also, in the diagram, the state o=
f the AS
> > > > > >   -------------------------
> > > > > >
> > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > Whenever AS state-change happens at SGP, a NTFY will be sent to=
 all ASPes
> > > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > > This is what i remember that everybody agreed.
> > > > > >
> > > > > > --Samuel
> > > > > > > does not change with the second ASP (ASP2) sending ASPUP.  Th=
e AS
> > > > > changes
> > > > > > > state to AS-INACTIVE with ASP1 coming up.  Therefore, the dia=
gram should
> > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP immediately=
 after the
> > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > >
> > > > > > > The diagram is quite wrong.  Also it is wrong considering the=
 changes to
> > > > > > > be made to the next issue of the IG.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > kakaul@hss.hns.com wrote:
> > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On receiving ASPUP message from ASP3 state of AS does not c=
hange, so
> > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > >
> > > > > > > > Kamesh
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/04/20=
03 11:40:01
> > > > > > AM
> > > > > > > >
> > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > >
> > > > > > > >
> > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > cc:
> > > > > > > >
> > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> receive
> > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > >
> > > > > > > > Thanls
> > > > > > > >
> > > > > > > > Ling-Chih Kao
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > Sigtran mailing list
> > > > > > > > Sigtran@ietf.org
> > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > >
> > > > > > > --
> > > > > > > Brian F. G. Bidulock
> > > > > > > bidulock@openss7.org
> > > > > > > http://www.openss7.org/
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > 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
> > > > > >
> > > > > >
> > > > >=20
> > > > >=20
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >=20
> > > > >=20
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >=20
> > > --=20
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >=20
> > >=20
> >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
>=20


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



From exim@www1.ietf.org  Fri Aug  8 05:21:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05042
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 05:21:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Qi-00036I-QR
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 05:21:00 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h789L00d011896
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 05:21:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Qi-00035m-L1; Fri, 08 Aug 2003 05:21:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Py-00035D-Lb
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 05:20:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04993
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 05:20:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3Pv-000795-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:20:11 -0400
Received: from gremg1.net.external.hp.com ([192.6.111.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3Pt-000791-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:20:09 -0400
Received: from garonne.grenoble.hp.com (garonne.grenoble.hp.com [15.128.14.138])
	by gremg1.net.external.hp.com (Postfix) with ESMTP
	id 183FD4CA; Fri,  8 Aug 2003 11:20:09 +0200 (METDST)
Received: by garonne.grenoble.hp.com with Internet Mail Service (5.5.2655.55)
	id <QMM0K9GD>; Fri, 8 Aug 2003 11:20:08 +0200
Message-ID: <D00C96E68738D511941F0090276D8F0B07FECF5C@prevert.grenoble.hp.com>
From: "BAND,RICHARD (HP-France,ex1)" <richard.band@hp.com>
To: "'kakaul@hss.hns.com'" <kakaul@hss.hns.com>,
        Vivek Toky <vivektoky@ccpu.com>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
Date: Fri, 8 Aug 2003 11:20:05 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA04995
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Hi Kamesh,

The text you refer to describes both SE and DE IPSP behavior.
Both behaviors have been clearly separated in the IG, and have been
described in more detail.

Specifically, in DE IPSP, the AS FSM shows that the AS state as seen by t=
he
SGP or by a remote IPSP only changes at the reception of an ASPIA.
So, if IPSP A sends an ASPIA for AS 1, it only means that IPSP A is no
longer able to receive traffic for AS1.
It does not mean that it cannot send traffic from AS 1 to the AS at IPSP =
C.
Although your implementation may opt not to send any traffic, the protoco=
l
does allow it until IPSP C sends an APIA of its own.

Regards,

Richard

-----Original Message-----
From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
Sent: Thursday, August 07, 2003 12:12
To: Vivek Toky
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour




Hi Vivek,
   Please go through the section attached from RFC 3332
   4.3.4.4.1 IPSP Considerations (ASP Inactive)

   An IPSP may be considered in the ASP-INACTIVE state by a remote IPSP
   after an ASP Inactive or ASP Inactive Ack message has been received
   from it.

   Alternatively, an interchange of ASP Inactive messages from each end
   can be performed. This option follows the ASP state transition
   diagram and gives the additional advantage of selecting a particular
   AS to be deactivated from each end. It is especially useful when an
   IPSP is serving more than one AS. It would need four messages for
   completion.

   IMO IPSP A in your example after sending ASPIA message for AS1 would
   not be able to send or receive traffic from or for AS1.

Regards
Kamesh Kaul
www.hssworld.com
Hughes Software Systems








"Vivek Toky" <vivektoky@ccpu.com>@ietf.org on 08/07/2003 10:00:09 AM

Sent by:    sigtran-admin@ietf.org


To:    Kamesh Kaul/HSS@HSS
cc:    <sigtran@ietf.org>

Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour



Kamesh,

  See my comments Inline..

-----Original Message-----
From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
Sent: Wednesday, August 06, 2003 8:47 PM
To: vivektoky@ccpu.com
Cc: sigtran@ietf.org
Subject: [Spam] RE: [Sigtran] M3UA : IPSP DE behaviour







Vivek
      Please see comments in line



"Vivek Toky" <vivektoky@ccpu.com>@ietf.org on 08/05/2003 09:47:43 AM

Sent by:    sigtran-admin@ietf.org


To:    "kamesh kaul" <kkk_kaul@yahoo.com>
cc:    <sigtran@ietf.org>

Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour


Kamesh,
  Please see comments inline
-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
kamesh kaul
Sent: Saturday, August 02, 2003 8:24 PM
To: Vivek Toky
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour


Hi Vivek,
    I argee with you that if we intermix IPSP SE and
DE models we can start loadsharing traffic for AS2
among IPSP B and IPSP A even though IPSP B has not
received ASPAC message from IPSP c.It would result in
intermixing of two IPSP models.For some messages IPSP
C has to behave in DE manner and for other SE
behaviour is required.Lets take your example. On
receiving ASPAC messages from IPSP A and IPSP B for
AS1 IPSP C updates only remote IPSP'S states for AS1
behaving in DE manner.when IPSP c sends ASPAC for AS2
to IPSP A and receives ACK back then also IPSP C
changes its state to active for local AS2 behaving in
DE manner.Now as you said Bi-directional data is
flowing from IPSP C and IPSP A where as single
direction traffic is possible from IPSP C to IPSP B
(for AS2).Now assume IPSP A sends ASPIA message for
AS1 to IPSP C in this case IPSP c on receiving ASPIA
message has to update state of remote IPSP A in AS1
and also state of local IPSP C in local AS2 behaving
in SE manner.

[Vivek]
 You have a good point but I did not understand why would we need to chan=
ge
the state of IPSP C in this case ( when IPSP A sends ASPIA to IPSP C). Wh=
en
IPSP A sends ASPIA message for AS1 to IPSP C then only IPSP A's state wil=
l
change in local AS1 and the corresponding remote AS1 on the other side. Y=
ou
are right that AS1 will not be able to receive traffic through IPSP A , b=
ut
that doesnot restrict AS1 to send traffic from IPSP A.
[Kamesh]
IPSP A is inactive (it has send ASPIA) for AS1 so how can it send data fo=
r
AS1.
****Vivek*****
That is what I am trying to say, IPSP A is inactive to receive data. It c=
an
still send data because remote destination is still active to receive dat=
a
through  IPSP A
If sending an Active message means it will be able to send and receive da=
ta
then an Active Ack from other would have been suffcient to tell IPSP A th=
at
it can start sending data as well. But it did not happen.. IPSP C sent an
explicit Active message to indicate that its ready to receive data so IPS=
P
C is the one who will indicate that now it is not going to receive data.
IPSP A does not need to stop sending data to IPSP C just because it send
ASPIA message.
**************

Note: AS1 is still UP
and ready to process data and so is AS2. If AS1 wants to go down and not
process data at all then it should sent Inactive through both the IPSPs (
IPSP A and IPSP B).
[Kamesh]
 IPSP B cant't send data for AS1 to IPSP C because IPSP C has not send
ASPAC message to it.So it means that AS1's data cant reach IPSP C because
IPSP A is inactive for AS1 and IPSP B has not received ASPAC message from
IPSP C.
Now the question arises that what should IPSP A do if it
receives data from AS1 which has inactivated itself from both  the IPSPs
and
is now totally unable to receive DATA ? ... following points should be
noted
1. If AS1 doesn't want to receive data, why we care if the data sent by A=
S1
went through all the way to AS2.
2. Now we know that AS2 won't be able to send data to AS1 atall so it can
take recovery and De-activate itself through IPSP A (to which it sent ASP
Active and got Active Ack.)

does it make sense ? please comment..

[Kamesh]
 We have to check the state of local IPSP before selecting remote
application server for data


If IPSP C does not bother about local
state updation on receiving ASPIA from IPSP A, IPSP C
will continue to send data messages for AS2 to IPSP B
without receiving anything from other side. This will
result in single direction traffic from IPSP C to AS1
without the knowledge of IPSP C.If we associate AS
state with local and peer IPSP's (in your example
AS2's state with IPSP c and each peer IPSPA and IPSPB,
AS2's state with IPSP C and each peer IPSP's) single
direction traffic flow is not possible. Please comment

Regards
Kamesh
--- Vivek Toky <vivektoky@ccpu.com> wrote:
> Hi Kamesh,
>   Although ASPAC message has not been sent to IPSP
> B, but the local AS is
> still active and is sending and receiving traffic
> through IPSP A. Now on the
> other side IPSP A and IPSP B are part of the same AS
> ( AS1 ). So following
> points should be noted.
>
> 1. Bi-directional traffic between AS1 and AS2 is
> possible
> 2. IPSP B has already sent ASPAC and received ASPAC
> Ack, so it is ready to
> receive traffic.
>
>  So why don't we loadshare the traffic among IPSP A
> and IPSP B as the
> traffic is anyway going to get to the same
> destination i.e. AS1
>
> In the reverse direction AS1 can choose IPSP A to
> send traffic towards AS2,
> as only IPSP A has received ASPAC from IPSP C (for
> AS2)
>
> comments?
>
> -Vivek.
>
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> kakaul@hss.hns.com
> Sent: Friday, August 01, 2003 1:16 AM
> To: Vivek Toky
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
>
>
>
>
> Vivek,
>
> In your example also IPSP C will send data for AS1
> to IPSP A only.I dont
> see any reason for IPSP C to send data to IPSP B
> because ASPAC message is
> not sent to IPSP B. I dont see any possibility of
> single direction traffic
> flow in your example also.
>
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
>
>
>
>
> "Vivek Toky" <vivektoky@ccpu.com> on 08/01/2003
> 01:23:11 PM
>
> To:    Kamesh Kaul/HSS@HSS, sigtran@ietf.org
> cc:
>
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
>
>
> Kamesh,
>
>   Single direction traffic will still be possible.
> If you look at my
> example carefully you will notice that in case of 3
> IPSPs, it will be
> possible. It may be for a short duration of time. In
> my example local
> AS is already Active as it sent ASP Active message
> to one of the peer
> IPSPs ( also got the ACK back )
>
> please go through the example again .. waiting for
> comments ?
>
> Vivek
> >
> >
> >
> >
> > Hi Some comments below
> >
> >  When IPSP B receives ASPAC message from IPSP A
> for AS1 it marks
> remote
> > IPSP A active for remote AS1 and sends ASPAC ack
> back for AS1 to
> IPSP A.Now
> > with these message exchanges it means that IPSP A
> is ready to receive
> > traffic for AS1.At this point of time IPSP B has
> not expressed its
> > willingness to send data for any AS.IPSP B  cannot
>  send any
> application
> > data because its local applications are not active
> yet.So single
> direction
> > traffic flow will never occur.Now when IPSP B
> sends ASPAC message
> for AS2
> > to IPSP A and gets back ASPAC ack for AS2 it will
> give resume
> indication to
> > user now.AS1 and AS2 are basically same type of
> MTP3 users, and user
> to
> > user communication will only start if both users
> are ready and
> active.
> >
> >
> >     +-----------+              +-----------+
> >     |           |              |           |
> >     | IPSP A    |              | IPSP B    |
> >     |           +--------------+           |
> >     |           |              |           |
> >     +-----------+              +-----------+
> >
> >         AS1                        AS2
> >
> > Kamesh Kaul
> > www.hssworld.com
> > Hughes Software Systems
> >
> >
> >
> >
> >
> > "VIvek Toky" <vivektoky@ccpu.com>@ietf.org on
> 07/31/2003 11:19:39 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    "Tolga Asveren" <tolga_asveren@yahoo.com>,
> <sigtran@ietf.org>
> > cc:
> >
> > Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> >
> >
> > Tolga,
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On
> Behalf Of
> > Tolga Asveren
> > Sent: Thursday, July 31, 2003 10:19 AM
> > To: sigtran@ietf.org
> > Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> >
> >
> > Vivek,
> > --- Vivek Toky <vivektoky@ccpu.com> wrote:
> > > Please see my comments inline
> > >
> > > > See my opigion online
> > > >
> > > > > -----Original Message-----
> > > > > From: Vivek Toky [mailto:vivektoky@ccpu.com]
> > > > > Sent: Thursday, July 31, 2003 2:42 PM
> > > > > To: Tolga Asveren; sigtran@ietf.org
> > > > > Subject: RE: [Sigtran] M3UA : IPSP DE
> behaviour
> > > > >
> > > > >
> > > > > Hi Tolga,
> > > > >   "Above case" means
> > > > > "when AS1 has activated itself by sending
> > > > >  ASP Active from both the IPSPs (A & B) but
> > > > >  AS2 has sent ASP Active just to IPSP_A."
> > > > >
> > > > > In my opinion IPSP_C should loadshare the
> > > traffic
> > > > > as it has received ASP active from both the
> > > IPSPs
> > > > > so AS1 is accessible through both of these.
> > > > > However, it is the responsibility of AS1 to
> > > route
> > > > > all the traffic towards AS2 through IPSP_A.
> > > >
> > > > If IPSP_B receive some traffic from IPSP_C BUT
> no
> > > AS is ACTIVE for
> > > it on
> > > > IPSP_C can it route this traffic???
> > > > CAN a SG send to a ss7 network a message
> receive
> > > from an INACTIVE
> > > ASP !
>
=3D=3D=3D message truncated =3D=3D=3D


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

_______________________________________________
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





"DISCLAIMER: This message is proprietary to Hughes Software Systems Limit=
ed
(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 i=
s
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 fo=
r
loss or damage arising from the use of the information transmitted by thi=
s
email including damage from virus."


_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
 https://www1.ietf.org/mailman/listinfo/sigtran
J(-j)b  b=E1=B4=B2=D4=A2=1A'~=06i
bz.=0F
j)fj=7F=C5=8Ab?(-

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



From exim@www1.ietf.org  Fri Aug  8 05:25:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05164
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 05:25:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Uc-0003EV-K3
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 05:25:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h789P2FI012420
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 05:25:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Ub-0003EB-AO; Fri, 08 Aug 2003 05:25:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3U4-0003De-3S
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 05:24:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05145
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 05:24:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3U0-0007Bf-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:24:24 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[oQ0rftNLhlJZF/RlWXsnoPH98wnEypJo])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3Tz-0007Bc-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:24:23 -0400
Received: from ns.pigworks.openss7.net (IDENT:DBGjeXjkdNfVDvy6yAs19msgUPn271FB@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h789ONE15067;
	Fri, 8 Aug 2003 03:24:23 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h789ONQ25524;
	Fri, 8 Aug 2003 03:24:23 -0600
Date: Fri, 8 Aug 2003 03:24:23 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030808032423.Q23030@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
References: <20030808030747.N23030@openss7.org> <Pine.SOL.4.10.10308080409330.6428-100000@sun2685.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10308080409330.6428-100000@sun2685.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Aug 08, 2003 at 04:17:31AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h789ONE15067
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Samuel,

What if ASP1 and ASP3 receive it but ASP2 did not, just because
ASP3's ASPUP arrived before ASP2's.  That is a race condition.
This is why it is wise (and "SHOULD" is appropriate) to avoid
the race condition by sending NTFY(AS-INACTIVVE) to all of the
ASPs when they come up.  It should not be optional.  It is necessary
to proper interworking that this race be broken.

--brian

Samuel Dur D. Jeyaseelan wrote:                                          =
           (Fri, 08 Aug 2003 04:17:31)
>=20
> Brian,
>  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, but ASP1 a=
nd
>  ASP2 received NTFY(AS-INACT) but ASP3 did not.
>  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT message,
>  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1 and ASP3).
>=20
>  This is the reason i said it is an optional of sending NTFY(AS-INACT)
>  to 'n+1'th ASP.
>=20
> --Samuel
>=20
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
>=20
> On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
>=20
> > Samuel,
> >=20
> > Yes, I have a problem, because it is a race condition.
> >=20
> > --brian
> >=20
> > Samuel Dur D. Jeyaseelan wrote:                                      =
               (Fri, 08 Aug 2003 04:04:50)
> > >=20
> > > Brian,
> > >=20
> > >   I meant first 2 ASPes will receive NTFY messages.Sending NTFY to=20
> > >   3rd ASP is an optional.Do you have any problem here?
> > >=20
> > > --Samuel
> > >=20
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alc=
atel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc.=
 *******
> > >=20
> > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > >=20
> > > > Samuel,
> > > >=20
> > > > None of the ASPs are handling traffic at that point.  Who is to s=
ay
> > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perhaps ASP2
> > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely doesn't=
 know.
> > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest choice.
> > > >=20
> > > > --brian
> > > >=20
> > > > Samuel Dur D. Jeyaseelan wrote:                                  =
                   (Fri, 08 Aug 2003 03:47:30)
> > > > >=20
> > > > > Ling-Chih Kao and Brian,
> > > > >=20
> > > > > In n+k reduntancy case,when n=3D2 that means ASP1 and ASP2 are =
going to
> > > > > handle the traffic.So sending NTFY to these ASPes is mandatory.
> > > > > Sending NTFY to ASP3 is an optional because it is not going to =
handle=20
> > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 will come up =
to take
> > > > > over the traffic this case SGP will send a NTFY message with AS=
 state,
> > > > > here it is mandatory to send NTFY to ASP3.
> > > > >=20
> > > > > --Samuel
> > > > >=20
> > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa=
.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, =
Inc. *******
> > > > >=20
> > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > >=20
> > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > >=20
> > > > > >=20
> > > > > > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS be=
comes
> > > > > > AS-INACTIVE when there are at least n ASPs in either ASP-INAC=
TIVE or
> > > > > > AS-ACTIVE.
> > > > > >=20
> > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP rec=
eives two ASP
> > > > > > UP (from ASP1 and ASP2).  However, when the SGP receives  ASP=
 UP from ASP3,
> > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to kn=
ow whether it
> > > > > > is optional or not?
> > > > > >=20
> > > > > > Thanks.
> > > > > > Ling-Chih Kao
> > > > > >=20
> > > > > > ----- Original Message -----
> > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.co=
m>
> > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > >=20
> > > > > >=20
> > > > > >=20
> > > > > > Ling-Chih Kao,
> > > > > >=20
> > > > > > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > > > > > Note: Available peer means an ASP which received ASP-UP-ACK
> > > > > > in response to ASP-UP messages.(as per RFC section 4.3.4.1).
> > > > > >=20
> > > > > > If you active the AS as soon as a single ASP goes to ASP-INAC=
T
> > > > > > state then it is obvious that whoever sends ASP-UP message to
> > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to the concer=
n
> > > > > > ASP followd by ASP-UP-ACK.
> > > > > >=20
> > > > > >=20
> > > > > > --Samuel
> > > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.u=
sa.alcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of Alcatel USA=
, Inc. *******
> > > > > >=20
> > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > >=20
> > > > > > > Hi all,
> > > > > > >
> > > > > > > After SGP receives the ASP UP from ASP1, SGP should immedia=
tely send
> > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this ri=
ght?
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Ling-Chih Kao
> > > > > > > ----- Original Message -----
> > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.=
com>
> > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.ed=
u.tw>;
> > > > > > "sigtran"
> > > > > > > <sigtran@ietf.org>
> > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Brian,
> > > > > > >
> > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > >
> > > > > > > > kakaul,
> > > > > > > >
> > > > > > > > But I think that we agreed that it would be wise to tell =
newly inactive
> > > > > > >                                                       -----=
-------------
> > > > > > > > ASPs that state of the AS.  Also, in the diagram, the sta=
te of the AS
> > > > > > >   -------------------------
> > > > > > >
> > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > Whenever AS state-change happens at SGP, a NTFY will be sen=
t to all ASPes
> > > > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > > > This is what i remember that everybody agreed.
> > > > > > >
> > > > > > > --Samuel
> > > > > > > > does not change with the second ASP (ASP2) sending ASPUP.=
  The AS
> > > > > > changes
> > > > > > > > state to AS-INACTIVE with ASP1 coming up.  Therefore, the=
 diagram should
> > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP immedia=
tely after the
> > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > >
> > > > > > > > The diagram is quite wrong.  Also it is wrong considering=
 the changes to
> > > > > > > > be made to the next issue of the IG.
> > > > > > > >
> > > > > > > > --brian
> > > > > > > >
> > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On receiving ASPUP message from ASP3 state of AS does n=
ot change, so
> > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > >
> > > > > > > > > Kamesh
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/0=
4/2003 11:40:01
> > > > > > > AM
> > > > > > > > >
> > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > cc:
> > > > > > > > >
> > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> rec=
eive
> > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > >
> > > > > > > > > Thanls
> > > > > > > > >
> > > > > > > > > Ling-Chih Kao
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > Sigtran mailing list
> > > > > > > > > Sigtran@ietf.org
> > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > >
> > > > > > > > --
> > > > > > > > Brian F. G. Bidulock
> > > > > > > > bidulock@openss7.org
> > > > > > > > http://www.openss7.org/
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > >=20
> > > > > >=20
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > >=20
> > > > > >=20
> > > > >=20
> > > > >=20
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >=20
> > > > --=20
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >=20
> > > >=20
> > >=20
> > >=20
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >=20
> >=20

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 05:38:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05506
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 05:38:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3hB-0004AL-Sg
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 05:38:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h789c1RF016008
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 05:38:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3hB-00049y-6o; Fri, 08 Aug 2003 05:38:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3h3-000478-4Z
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 05:37:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05479
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 05:37:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3gz-0007HQ-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:37:49 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3gy-0007HF-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:37:48 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h789bIwC020098;
	Fri, 8 Aug 2003 04:37:19 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h789ao1C008053;
	Fri, 8 Aug 2003 04:36:50 -0500 (CDT)
Date: Fri, 8 Aug 2003 04:36:50 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <20030808032423.Q23030@openss7.org>
Message-ID: <Pine.SOL.4.10.10308080432230.6428-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: QUOTED-PRINTABLE


Brian,
 We all know that in n+k redundancy case that ASPes will coordinate
 among themselves the number of active ASPs in the AS, here it is
 clear that who is going to go to ACTIVE state then where is the
 question of race condition?

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:

> Samuel,
>=20
> What if ASP1 and ASP3 receive it but ASP2 did not, just because
> ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> This is why it is wise (and "SHOULD" is appropriate) to avoid
> the race condition by sending NTFY(AS-INACTIVVE) to all of the
> ASPs when they come up.  It should not be optional.  It is necessary
> to proper interworking that this race be broken.
>=20
> --brian
>=20
> Samuel Dur D. Jeyaseelan wrote:                                          =
           (Fri, 08 Aug 2003 04:17:31)
> >=20
> > Brian,
> >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, but ASP1 a=
nd
> >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT message,
> >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1 and ASP3)=
=2E
> >=20
> >  This is the reason i said it is an optional of sending NTFY(AS-INACT)
> >  to 'n+1'th ASP.
> >=20
> > --Samuel
> >=20
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
=2Ecom
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
> >=20
> > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> >=20
> > > Samuel,
> > >=20
> > > Yes, I have a problem, because it is a race condition.
> > >=20
> > > --brian
> > >=20
> > > Samuel Dur D. Jeyaseelan wrote:                                      =
               (Fri, 08 Aug 2003 04:04:50)
> > > >=20
> > > > Brian,
> > > >=20
> > > >   I meant first 2 ASPes will receive NTFY messages.Sending NTFY to=
=20
> > > >   3rd ASP is an optional.Do you have any problem here?
> > > >=20
> > > > --Samuel
> > > >=20
> > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alc=
atel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.=
 *******
> > > >=20
> > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > >=20
> > > > > Samuel,
> > > > >=20
> > > > > None of the ASPs are handling traffic at that point.  Who is to s=
ay
> > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perhaps ASP2
> > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely doesn't=
 know.
> > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest choice.
> > > > >=20
> > > > > --brian
> > > > >=20
> > > > > Samuel Dur D. Jeyaseelan wrote:                                  =
                   (Fri, 08 Aug 2003 03:47:30)
> > > > > >=20
> > > > > > Ling-Chih Kao and Brian,
> > > > > >=20
> > > > > > In n+k reduntancy case,when n=3D2 that means ASP1 and ASP2 are =
going to
> > > > > > handle the traffic.So sending NTFY to these ASPes is mandatory.
> > > > > > Sending NTFY to ASP3 is an optional because it is not going to =
handle=20
> > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 will come up =
to take
> > > > > > over the traffic this case SGP will send a NTFY message with AS=
 state,
> > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > >=20
> > > > > > --Samuel
> > > > > >=20
> > > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa=
=2Ealcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of Alcatel USA, =
Inc. *******
> > > > > >=20
> > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > >=20
> > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > >=20
> > > > > > >=20
> > > > > > > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the AS be=
comes
> > > > > > > AS-INACTIVE when there are at least n ASPs in either ASP-INAC=
TIVE or
> > > > > > > AS-ACTIVE.
> > > > > > >=20
> > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP rec=
eives two ASP
> > > > > > > UP (from ASP1 and ASP2).  However, when the SGP receives  ASP=
 UP from ASP3,
> > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want to kn=
ow whether it
> > > > > > > is optional or not?
> > > > > > >=20
> > > > > > > Thanks.
> > > > > > > Ling-Chih Kao
> > > > > > >=20
> > > > > > > ----- Original Message -----
> > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.co=
m>
> > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > >=20
> > > > > > >=20
> > > > > > >=20
> > > > > > > Ling-Chih Kao,
> > > > > > >=20
> > > > > > > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > > > > > > Note: Available peer means an ASP which received ASP-UP-ACK
> > > > > > > in response to ASP-UP messages.(as per RFC section 4.3.4.1).
> > > > > > >=20
> > > > > > > If you active the AS as soon as a single ASP goes to ASP-INAC=
T
> > > > > > > state then it is obvious that whoever sends ASP-UP message to
> > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to the concer=
n
> > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > >=20
> > > > > > >=20
> > > > > > > --Samuel
> > > > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.u=
sa.alcatel.com
> > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > >   ******* The opinions expressed are not those of Alcatel USA=
, Inc. *******
> > > > > > >=20
> > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > >=20
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > After SGP receives the ASP UP from ASP1, SGP should immedia=
tely send
> > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is this ri=
ght?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > Ling-Chih Kao
> > > > > > > > ----- Original Message -----
> > > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.=
com>
> > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@ntu.ed=
u.tw>;
> > > > > > > "sigtran"
> > > > > > > > <sigtran@ietf.org>
> > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Brian,
> > > > > > > >
> > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > >
> > > > > > > > > kakaul,
> > > > > > > > >
> > > > > > > > > But I think that we agreed that it would be wise to tell =
newly inactive
> > > > > > > >                                                       -----=
-------------
> > > > > > > > > ASPs that state of the AS.  Also, in the diagram, the sta=
te of the AS
> > > > > > > >   -------------------------
> > > > > > > >
> > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > Whenever AS state-change happens at SGP, a NTFY will be sen=
t to all ASPes
> > > > > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > > > > This is what i remember that everybody agreed.
> > > > > > > >
> > > > > > > > --Samuel
> > > > > > > > > does not change with the second ASP (ASP2) sending ASPUP.=
  The AS
> > > > > > > changes
> > > > > > > > > state to AS-INACTIVE with ASP1 coming up.  Therefore, the=
 diagram should
> > > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP immedia=
tely after the
> > > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > > >
> > > > > > > > > The diagram is quite wrong.  Also it is wrong considering=
 the changes to
> > > > > > > > > be made to the next issue of the IG.
> > > > > > > > >
> > > > > > > > > --brian
> > > > > > > > >
> > > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On receiving ASPUP message from ASP3 state of AS does n=
ot change, so
> > > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > > >
> > > > > > > > > > Kamesh
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on 08/0=
4/2003 11:40:01
> > > > > > > > AM
> > > > > > > > > >
> > > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > > cc:
> > > > > > > > > >
> > > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt> rec=
eive
> > > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > > >
> > > > > > > > > > Thanls
> > > > > > > > > >
> > > > > > > > > > Ling-Chih Kao
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > _______________________________________________
> > > > > > > > > > Sigtran mailing list
> > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > bidulock@openss7.org
> > > > > > > > > http://www.openss7.org/
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > 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
> > > > > > > >
> > > > > > > >
> > > > > > >=20
> > > > > > >=20
> > > > > > > _______________________________________________
> > > > > > > Sigtran mailing list
> > > > > > > Sigtran@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > >=20
> > > > > > >=20
> > > > > >=20
> > > > > >=20
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >=20
> > > > > --=20
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >=20
> > > > >=20
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >=20
> > > --=20
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >=20
> > >=20
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
>=20


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



From exim@www1.ietf.org  Fri Aug  8 05:48:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05815
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 05:48:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3qr-0004c4-VF
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 05:48:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h789m1iA017725
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 05:48:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3qr-0004bf-95; Fri, 08 Aug 2003 05:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3qT-0004b6-Lc
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 05:47:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05789
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 05:47:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3qQ-0007MT-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:47:34 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[LNMrP6p1tAd5C+JH7xNFEvz6Zw+HHVUT])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3qP-0007MQ-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 05:47:33 -0400
Received: from ns.pigworks.openss7.net (IDENT:fct+e5k068xum4nEw8D9k80ImZNrUmzW@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h789lYE15432;
	Fri, 8 Aug 2003 03:47:34 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h789lXQ25750;
	Fri, 8 Aug 2003 03:47:33 -0600
Date: Fri, 8 Aug 2003 03:47:33 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030808034733.A25706@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
References: <20030808032423.Q23030@openss7.org> <Pine.SOL.4.10.10308080432230.6428-100000@sun2685.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10308080432230.6428-100000@sun2685.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Aug 08, 2003 at 04:36:50AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h789lYE15432
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Samuel,

Maybe clear to the ASPs depending on implementation, but not
clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
used by any of the ASPs, why send it in the first place?
If it serves a purpose, it should be sent to all of them to avoid
the race condition.

--brian

Samuel Dur D. Jeyaseelan wrote:                                          =
           (Fri, 08 Aug 2003 04:36:50)
>=20
> Brian,
>  We all know that in n+k redundancy case that ASPes will coordinate
>  among themselves the number of active ASPs in the AS, here it is
>  clear that who is going to go to ACTIVE state then where is the
>  question of race condition?
>=20
> --Samuel
>=20
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
>=20
> On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
>=20
> > Samuel,
> >=20
> > What if ASP1 and ASP3 receive it but ASP2 did not, just because
> > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > ASPs when they come up.  It should not be optional.  It is necessary
> > to proper interworking that this race be broken.
> >=20
> > --brian
> >=20
> > Samuel Dur D. Jeyaseelan wrote:                                      =
               (Fri, 08 Aug 2003 04:17:31)
> > >=20
> > > Brian,
> > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, but AS=
P1 and
> > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT message,
> > >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1 and A=
SP3).
> > >=20
> > >  This is the reason i said it is an optional of sending NTFY(AS-INA=
CT)
> > >  to 'n+1'th ASP.
> > >=20
> > > --Samuel
> > >=20
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alc=
atel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc.=
 *******
> > >=20
> > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > >=20
> > > > Samuel,
> > > >=20
> > > > Yes, I have a problem, because it is a race condition.
> > > >=20
> > > > --brian
> > > >=20
> > > > Samuel Dur D. Jeyaseelan wrote:                                  =
                   (Fri, 08 Aug 2003 04:04:50)
> > > > >=20
> > > > > Brian,
> > > > >=20
> > > > >   I meant first 2 ASPes will receive NTFY messages.Sending NTFY=
 to=20
> > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > >=20
> > > > > --Samuel
> > > > >=20
> > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa=
.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, =
Inc. *******
> > > > >=20
> > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > >=20
> > > > > > Samuel,
> > > > > >=20
> > > > > > None of the ASPs are handling traffic at that point.  Who is =
to say
> > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perhaps =
ASP2
> > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely doe=
sn't know.
> > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest choice.
> > > > > >=20
> > > > > > --brian
> > > > > >=20
> > > > > > Samuel Dur D. Jeyaseelan wrote:                              =
                       (Fri, 08 Aug 2003 03:47:30)
> > > > > > >=20
> > > > > > > Ling-Chih Kao and Brian,
> > > > > > >=20
> > > > > > > In n+k reduntancy case,when n=3D2 that means ASP1 and ASP2 =
are going to
> > > > > > > handle the traffic.So sending NTFY to these ASPes is mandat=
ory.
> > > > > > > Sending NTFY to ASP3 is an optional because it is not going=
 to handle=20
> > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 will come=
 up to take
> > > > > > > over the traffic this case SGP will send a NTFY message wit=
h AS state,
> > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > >=20
> > > > > > > --Samuel
> > > > > > >=20
> > > > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd=
.usa.alcatel.com
> > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > >   ******* The opinions expressed are not those of Alcatel U=
SA, Inc. *******
> > > > > > >=20
> > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > >=20
> > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > >=20
> > > > > > > >=20
> > > > > > > > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the A=
S becomes
> > > > > > > > AS-INACTIVE when there are at least n ASPs in either ASP-=
INACTIVE or
> > > > > > > > AS-ACTIVE.
> > > > > > > >=20
> > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP=
 receives two ASP
> > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP receives =
 ASP UP from ASP3,
> > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want t=
o know whether it
> > > > > > > > is optional or not?
> > > > > > > >=20
> > > > > > > > Thanks.
> > > > > > > > Ling-Chih Kao
> > > > > > > >=20
> > > > > > > > ----- Original Message -----
> > > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcate=
l.com>
> > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > >=20
> > > > > > > >=20
> > > > > > > >=20
> > > > > > > > Ling-Chih Kao,
> > > > > > > >=20
> > > > > > > > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > > > > > > > Note: Available peer means an ASP which received ASP-UP-A=
CK
> > > > > > > > in response to ASP-UP messages.(as per RFC section 4.3.4.=
1).
> > > > > > > >=20
> > > > > > > > If you active the AS as soon as a single ASP goes to ASP-=
INACT
> > > > > > > > state then it is obvious that whoever sends ASP-UP messag=
e to
> > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to the co=
ncern
> > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > >=20
> > > > > > > >=20
> > > > > > > > --Samuel
> > > > > > > >   Alcatel USA, Inc.                  Internet: <userid>@s=
sd.usa.alcatel.com
> > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > >   ******* The opinions expressed are not those of Alcatel=
 USA, Inc. *******
> > > > > > > >=20
> > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > >=20
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > After SGP receives the ASP UP from ASP1, SGP should imm=
ediately send
> > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is thi=
s right?
> > > > > > > > >
> > > > > > > > > Thanks
> > > > > > > > >
> > > > > > > > > Ling-Chih Kao
> > > > > > > > > ----- Original Message -----
> > > > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alca=
tel.com>
> > > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@nt=
u.edu.tw>;
> > > > > > > > "sigtran"
> > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Brian,
> > > > > > > > >
> > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > >
> > > > > > > > > > kakaul,
> > > > > > > > > >
> > > > > > > > > > But I think that we agreed that it would be wise to t=
ell newly inactive
> > > > > > > > >                                                       -=
-----------------
> > > > > > > > > > ASPs that state of the AS.  Also, in the diagram, the=
 state of the AS
> > > > > > > > >   -------------------------
> > > > > > > > >
> > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > Whenever AS state-change happens at SGP, a NTFY will be=
 sent to all ASPes
> > > > > > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > > > > > This is what i remember that everybody agreed.
> > > > > > > > >
> > > > > > > > > --Samuel
> > > > > > > > > > does not change with the second ASP (ASP2) sending AS=
PUP.  The AS
> > > > > > > > changes
> > > > > > > > > > state to AS-INACTIVE with ASP1 coming up.  Therefore,=
 the diagram should
> > > > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP imm=
ediately after the
> > > > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > > > >
> > > > > > > > > > The diagram is quite wrong.  Also it is wrong conside=
ring the changes to
> > > > > > > > > > be made to the next issue of the IG.
> > > > > > > > > >
> > > > > > > > > > --brian
> > > > > > > > > >
> > > > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On receiving ASPUP message from ASP3 state of AS do=
es not change, so
> > > > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > > > >
> > > > > > > > > > > Kamesh
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on =
08/04/2003 11:40:01
> > > > > > > > > AM
> > > > > > > > > > >
> > > > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > cc:
> > > > > > > > > > >
> > > > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt>=
 receive
> > > > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > > > >
> > > > > > > > > > > Thanls
> > > > > > > > > > >
> > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > > bidulock@openss7.org
> > > > > > > > > > http://www.openss7.org/
> > > > > > > > > >
> > > > > > > > > > _______________________________________________
> > > > > > > > > > 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
> > > > > > > > >
> > > > > > > > >
> > > > > > > >=20
> > > > > > > >=20
> > > > > > > > _______________________________________________
> > > > > > > > Sigtran mailing list
> > > > > > > > Sigtran@ietf.org
> > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > >=20
> > > > > > > >=20
> > > > > > >=20
> > > > > > >=20
> > > > > > > _______________________________________________
> > > > > > > Sigtran mailing list
> > > > > > > Sigtran@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > >=20
> > > > > > --=20
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > > > >=20
> > > > > >=20
> > > > >=20
> > > > >=20
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >=20
> > > > --=20
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >=20
> > > >=20
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >=20
> >=20

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug  8 06:10:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06414
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 06:10:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l4CB-0005l7-FG
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 06:10:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h78AA3Od022131
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 06:10:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l4C9-0005kj-QK; Fri, 08 Aug 2003 06:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l4C0-0005kD-H9
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 06:09:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06411
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 06:09:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l4Bw-0007Vn-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 06:09:48 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l4Bw-0007Ve-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 06:09:48 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h78A9IB3027746;
	Fri, 8 Aug 2003 05:09:19 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h78A8M1C013661;
	Fri, 8 Aug 2003 05:08:22 -0500 (CDT)
Date: Fri, 8 Aug 2003 05:08:22 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <20030808034733.A25706@openss7.org>
Message-ID: <Pine.SOL.4.10.10308080450510.6428-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: QUOTED-PRINTABLE


Brian,
 Huh, it is not an implementation dependent, rfc says=20
 ASPs which are in that AS should coordinate among themselves the number
 of active ASPs in the AS.So it is clear to SGP that first arrived
 'n' ASPs will receive NTFY(AS-INACT) message.

 If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN state)
 you are not restricted but it is not mandatory to send, thats what i
 am saying from the beginning.

 Keep IG as it is.
--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:

> Samuel,
>=20
> Maybe clear to the ASPs depending on implementation, but not
> clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> used by any of the ASPs, why send it in the first place?
> If it serves a purpose, it should be sent to all of them to avoid
> the race condition.
>=20
> --brian
>=20
> Samuel Dur D. Jeyaseelan wrote:                                          =
           (Fri, 08 Aug 2003 04:36:50)
> >=20
> > Brian,
> >  We all know that in n+k redundancy case that ASPes will coordinate
> >  among themselves the number of active ASPs in the AS, here it is
> >  clear that who is going to go to ACTIVE state then where is the
> >  question of race condition?
> >=20
> > --Samuel
> >=20
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
=2Ecom
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
> >=20
> > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> >=20
> > > Samuel,
> > >=20
> > > What if ASP1 and ASP3 receive it but ASP2 did not, just because
> > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > > ASPs when they come up.  It should not be optional.  It is necessary
> > > to proper interworking that this race be broken.
> > >=20
> > > --brian
> > >=20
> > > Samuel Dur D. Jeyaseelan wrote:                                      =
               (Fri, 08 Aug 2003 04:17:31)
> > > >=20
> > > > Brian,
> > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, but AS=
P1 and
> > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT message,
> > > >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1 and A=
SP3).
> > > >=20
> > > >  This is the reason i said it is an optional of sending NTFY(AS-INA=
CT)
> > > >  to 'n+1'th ASP.
> > > >=20
> > > > --Samuel
> > > >=20
> > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alc=
atel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.=
 *******
> > > >=20
> > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > >=20
> > > > > Samuel,
> > > > >=20
> > > > > Yes, I have a problem, because it is a race condition.
> > > > >=20
> > > > > --brian
> > > > >=20
> > > > > Samuel Dur D. Jeyaseelan wrote:                                  =
                   (Fri, 08 Aug 2003 04:04:50)
> > > > > >=20
> > > > > > Brian,
> > > > > >=20
> > > > > >   I meant first 2 ASPes will receive NTFY messages.Sending NTFY=
 to=20
> > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > >=20
> > > > > > --Samuel
> > > > > >=20
> > > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa=
=2Ealcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of Alcatel USA, =
Inc. *******
> > > > > >=20
> > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > >=20
> > > > > > > Samuel,
> > > > > > >=20
> > > > > > > None of the ASPs are handling traffic at that point.  Who is =
to say
> > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perhaps =
ASP2
> > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely doe=
sn't know.
> > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest choice=
=2E
> > > > > > >=20
> > > > > > > --brian
> > > > > > >=20
> > > > > > > Samuel Dur D. Jeyaseelan wrote:                              =
                       (Fri, 08 Aug 2003 03:47:30)
> > > > > > > >=20
> > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > >=20
> > > > > > > > In n+k reduntancy case,when n=3D2 that means ASP1 and ASP2 =
are going to
> > > > > > > > handle the traffic.So sending NTFY to these ASPes is mandat=
ory.
> > > > > > > > Sending NTFY to ASP3 is an optional because it is not going=
 to handle=20
> > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 will come=
 up to take
> > > > > > > > over the traffic this case SGP will send a NTFY message wit=
h AS state,
> > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > >=20
> > > > > > > > --Samuel
> > > > > > > >=20
> > > > > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd=
=2Eusa.alcatel.com
> > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > >   ******* The opinions expressed are not those of Alcatel U=
SA, Inc. *******
> > > > > > > >=20
> > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > >=20
> > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > >=20
> > > > > > > > >=20
> > > > > > > > > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > > > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the A=
S becomes
> > > > > > > > > AS-INACTIVE when there are at least n ASPs in either ASP-=
INACTIVE or
> > > > > > > > > AS-ACTIVE.
> > > > > > > > >=20
> > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when SGP=
 receives two ASP
> > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP receives =
 ASP UP from ASP3,
> > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want t=
o know whether it
> > > > > > > > > is optional or not?
> > > > > > > > >=20
> > > > > > > > > Thanks.
> > > > > > > > > Ling-Chih Kao
> > > > > > > > >=20
> > > > > > > > > ----- Original Message -----
> > > > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcate=
l.com>
> > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > >=20
> > > > > > > > >=20
> > > > > > > > >=20
> > > > > > > > > Ling-Chih Kao,
> > > > > > > > >=20
> > > > > > > > > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > > > > > > > > Note: Available peer means an ASP which received ASP-UP-A=
CK
> > > > > > > > > in response to ASP-UP messages.(as per RFC section 4.3.4.=
1).
> > > > > > > > >=20
> > > > > > > > > If you active the AS as soon as a single ASP goes to ASP-=
INACT
> > > > > > > > > state then it is obvious that whoever sends ASP-UP messag=
e to
> > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to the co=
ncern
> > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > >=20
> > > > > > > > >=20
> > > > > > > > > --Samuel
> > > > > > > > >   Alcatel USA, Inc.                  Internet: <userid>@s=
sd.usa.alcatel.com
> > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > >   ******* The opinions expressed are not those of Alcatel=
 USA, Inc. *******
> > > > > > > > >=20
> > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > >=20
> > > > > > > > > > Hi all,
> > > > > > > > > >
> > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP should imm=
ediately send
> > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is thi=
s right?
> > > > > > > > > >
> > > > > > > > > > Thanks
> > > > > > > > > >
> > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > ----- Original Message -----
> > > > > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alca=
tel.com>
> > > > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@nt=
u.edu.tw>;
> > > > > > > > > "sigtran"
> > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Brian,
> > > > > > > > > >
> > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > >
> > > > > > > > > > > kakaul,
> > > > > > > > > > >
> > > > > > > > > > > But I think that we agreed that it would be wise to t=
ell newly inactive
> > > > > > > > > >                                                       -=
-----------------
> > > > > > > > > > > ASPs that state of the AS.  Also, in the diagram, the=
 state of the AS
> > > > > > > > > >   -------------------------
> > > > > > > > > >
> > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY will be=
 sent to all ASPes
> > > > > > > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > > > > > > This is what i remember that everybody agreed.
> > > > > > > > > >
> > > > > > > > > > --Samuel
> > > > > > > > > > > does not change with the second ASP (ASP2) sending AS=
PUP.  The AS
> > > > > > > > > changes
> > > > > > > > > > > state to AS-INACTIVE with ASP1 coming up.  Therefore,=
 the diagram should
> > > > > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP imm=
ediately after the
> > > > > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > > > > >
> > > > > > > > > > > The diagram is quite wrong.  Also it is wrong conside=
ring the changes to
> > > > > > > > > > > be made to the next issue of the IG.
> > > > > > > > > > >
> > > > > > > > > > > --brian
> > > > > > > > > > >
> > > > > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On receiving ASPUP message from ASP3 state of AS do=
es not change, so
> > > > > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > > > > >
> > > > > > > > > > > > Kamesh
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org on =
08/04/2003 11:40:01
> > > > > > > > > > AM
> > > > > > > > > > > >
> > > > > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > cc:
> > > > > > > > > > > >
> > > > > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.txt>=
 receive
> > > > > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > >
> > > > > > > > > > > > Thanls
> > > > > > > > > > > >
> > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > > > bidulock@openss7.org
> > > > > > > > > > > http://www.openss7.org/
> > > > > > > > > > >
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > 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
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >=20
> > > > > > > > >=20
> > > > > > > > > _______________________________________________
> > > > > > > > > Sigtran mailing list
> > > > > > > > > Sigtran@ietf.org
> > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > >=20
> > > > > > > > >=20
> > > > > > > >=20
> > > > > > > >=20
> > > > > > > > _______________________________________________
> > > > > > > > Sigtran mailing list
> > > > > > > > Sigtran@ietf.org
> > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > >=20
> > > > > > > --=20
> > > > > > > Brian F. G. Bidulock
> > > > > > > bidulock@openss7.org
> > > > > > > http://www.openss7.org/
> > > > > > >=20
> > > > > > >=20
> > > > > >=20
> > > > > >=20
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >=20
> > > > > --=20
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >=20
> > > > >=20
> > >=20
> > > --=20
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >=20
> > >=20
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20


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



From exim@www1.ietf.org  Fri Aug  8 06:18:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06560
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 06:18:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l4Ju-0005zX-4H
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 06:18:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h78AI2Pb023022
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 06:18:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l4Jt-0005z6-Ir; Fri, 08 Aug 2003 06:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l4Iy-0005wW-BK
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 06:17:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06531
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 06:16:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l4Iu-0007Xr-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 06:17:00 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l4It-0007Xo-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 06:17:00 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h78AGIB5028065;
	Fri, 8 Aug 2003 05:16:19 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h78AFs1C015001;
	Fri, 8 Aug 2003 05:15:54 -0500 (CDT)
Date: Fri, 8 Aug 2003 05:15:54 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: "Anzile, Christophe" <christophe.anzile@hp.com>, sigtran@ietf.org
Subject: Re: [Sigtran] SUA and - RC in CLDT
In-Reply-To: <20030808031211.O23030@openss7.org>
Message-ID: <Pine.SOL.4.10.10308080513250.6428-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: QUOTED-PRINTABLE


Authors of M3UA and SUA,


Many a time we have discussed this point none of the documents reflect
this change, It is good if IG reflects this change.

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:

> Anzile,,
>=20
> We already discussed for M3UA that the '(s)' in the following passage
> should be struck.  The same argument applies to SUA:
>=20
>   "In the case where an ASP Active message does not contain a Routing
>    Context parameter, the receive must know, via configuration data,
>    [of] which Application Server(s) the ASP is a member."
>=20
> Should read:
>=20
>   "In the case where an ASP Active message does not contain a Routing
>    Context parameter, the receive must know, via configuration data,
>    [of] which Application Server the ASP is a member."
>=20
> --brian
>=20
> On Fri, 08 Aug 2003, Anzile, Christophe wrote:
>=20
> > I agree about this section..=20
> > what is confused to me is just the sentence following that one,
> > the one talking about "all Routing Contexts" when it is supposed
> > to have only one RC configured on the SG.
> >=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: Friday, August 08, 2003 10:27 AM
> > To: Anzile, Christophe
> > Cc: Samuel Dur D. Jeyaseelan; Valerie Gastaud; Sigtran
> > Subject: Re: [Sigtran] SUA - RC in CLDT
> >=20
> >=20
> > Anzile,,
> >=20
> > SUA-15 was supposed to include some of the more stable changes from
> > the M3UA IG where applicable to SUA.  Changing optional to conditional
> > should have been one of them.
> >=20
> > Nevertheless, SUA-15 section 4.3.4.3 does say:
> >=20
> >   "...  In the case where an ASP wishes to process the traffic for
> >    more than one Application Server across a common SCTP association,
> >    the ASP Active message(s) SHOULD contain a list of one or more
> >    Routing Contexts to indicate for which Application Servers the ASP
> >    Active message applies. ..."
> >=20
> > Which is no different than M3UA.
> >=20
> > We can change optional to conditional against RC throughout.
> >=20
> > --brian
> >=20
> >=20
> > Anzile, Christophe wrote:                                              =
            (Fri, 08 Aug 2003 10:12:27)
> > > Brian,
> > >=20
> > > are we supposed to look at M3UA IG when implementing SUA ?
> > > if yes, it would be nice to rename it.
> > > if no, it would be nice if John could clarify the SUA draft especiall=
y the 4.3.4.3 section
> > > and use "conditional" instead of "optional" when it applies.
> > >=20
> > >=20
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Friday, August 08, 2003 9:07 AM
> > > To: Samuel Dur D. Jeyaseelan
> > > Cc: Anzile, Christophe; Valerie Gastaud; Sigtran
> > > Subject: Re: [Sigtran] SUA - RC in CLDT
> > >=20
> > >=20
> > > Samuel,
> > >=20
> > > The M3UA IG section 3.5 changes "optional" to "conditional" everywher=
e
> > > for RC to indicate this explicitly.
> > >=20
> > > --brian
> > >=20
> > > Samuel Dur D. Jeyaseelan wrote:                                      =
               (Fri, 08 Aug 2003 01:58:42)
> > > >=20
> > > > Everybody,
> > > >=20
> > > > RC is a mandatory field when an ASP serves more than one AS.
> > > > A single ASP ACTIVE message without RC can not be used to active=20
> > > > multiple ASes across a common SCTP association.RFC does not explici=
tely
> > > > say that RC is mandatory when an ASP serves
> > > > multiple ASes across a common association.But it is implied.
> > > >=20
> > > > RFC has given a flexibility that RC is an optional field when it se=
rves
> > > > a single AS.
> > > >=20
> > > > Say an example, an ASP1 serves multiple ASes and has been connected=
 to=20
> > > > SGP1.If RC is an optional parameter to activate all ASes, the poten=
tial
> > > > problem is, while sending DATA messages to ASP1,=20
> > > >=20
> > > > 1) How does ASP1 relate the DATA message with an appropriate AS?
> > > >=20
> > > > 2) Suppose AS2 goes down, How does AS2 indicate this to SGP1?(remeb=
er=20
> > > >    RC has not been communicated between SGP1 and AS2)
> > > >=20
> > > > 3) Suppose SGP1 wants to put AS1 in DOWN state for some kind of
> > > >    configuration purpose, How does SGP1 communicate this with AS1 w=
ithout=20
> > > >    RC?
> > > >=20
> > > > RFC implicitely says that RC is a mandatory field when an ASP serve=
s
> > > > more than one ASes.
> > > >=20
> > > > --Samuel
> > > >=20
> > > >   Alcatel USA, Inc.                  Internet:
> > > > <userid>@ssd.usa.alcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.=
 *******
> > > >=20
> > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > >=20
> > > > > Anzile,,
> > > > >=20
> > > > > Anzile, Christophe wrote:                                        =
                  (Thu, 07 Aug 2003 11:24:09)
> > > > > > Brian (& Valerie),
> > > > > >=20
> > > > > > Please do not make RC mandatory in ASPAC, or you'll have strong=
 side effects on the draft..
> > > > > > This is not consistent at all with what's written in the draft =
page 92, ie
> > > > > >  [ it is not necessary for the ASP to=20
> > > > > >    include all Routing Contexts of interest in a single ASP Act=
ive=20
> > > > > >    message, thus requesting to become active in all Routing Con=
texts at=20
> > > > > >    the same time.  Multiple ASP Active messages MAY be used to =
activate=20
> > > > > >    within the Application Servers independently, or in sets.  I=
n the=20
> > > > > >    case where an ASP Active message does not contain a Routing =
Context=20
> > > > > >    parameter, the receiver must know, via configuration data, w=
hich=20
> > > > > >    Application Server(s) the ASP is a member. ]
> > > > > >=20
> > > > > > -> This is clear that if no RC is present in the ASPAC, it shou=
ld be considered as a wildcard
> > > > > > for all AS statically configured in the SG..=20
> > > > >=20
> > > > > No, that is not what it means.  If RC is not included, only a sin=
gle AS can
> > > > > exist for the SCTP association.
> > > > >=20
> > > > >=20
> > > > > > In return, SG should send back all RCs activated in the ASPAC-A=
CK msg.
> > > > >=20
> > > > > No.  If there is no RC in ASPAC there may be no RC in ASPAC Ack.
> > > > >=20
> > > > > >=20
> > > > > > -> This is why RC is therefore mandatory in CLDT/CLDR.
> > > > >=20
> > > > > Don't think so...
> > > > >=20
> > > > > --brian
> > > > >=20
> > > > > >=20
> > > > > >=20
> > > > > > Christophe.
> > > > > >=20
> > > > > >=20
> > > > > > -----Original Message-----
> > > > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > > > Sent: Thursday, August 07, 2003 9:18 AM
> > > > > > To: Valerie Gastaud
> > > > > > Cc: Sigtran
> > > > > > Subject: Re: [Sigtran] SUA - RC in CLDT
> > > > > >=20
> > > > > >=20
> > > > > > Valerie,
> > > > > >=20
> > > > > > SUA had RC mandatory in all messages.  This was just a cut and =
paste error
> > > > > > from "common UA procedures".  The SUA draft should be corrected=
 to make RC
> > > > > > mandatory in ASPAC.  Although it may make some sense to M2UA an=
d even M3UA
> > > > > > to have RC optional in ASPAC, it makes little sense in SUA.  Th=
is is why
> > > > > > RC is mandatory in all messages in SUA.
> > > > > >=20
> > > > > > --brian
> > > > > >=20
> > > > > > Valerie Gastaud wrote:                                         =
                    (Wed, 06 Aug 2003 15:33:59)
> > > > > > >=20
> > > > > > > Why is RC mandatory in the SUA data messages (CLDT/CLDR + cla=
ss2 messages)?
> > > > > > > This is not consistent with M3UA and this is not consistent w=
ith the SUA
> > > > > > > ASPAC message in which the RC is optional.
> > > > > > > In case of static provisioning of RK, if an SGP receives an A=
SPAC w/o RC, it
> > > > > > > won't be able to insert the RC in the CLDT.
> > > > > > >=20
> > > > > > > Valerie
> > > > > > >=20
> > > > > > >=20
> > > > > > >=20
> > > > > > > _______________________________________________
> > > > > > > Sigtran mailing list
> > > > > > > Sigtran@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > >=20
> > > > > > --=20
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > > > >=20
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >=20
> > > > > --=20
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >=20
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >=20
> > >=20
> > > --=20
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
>=20
> --=20
> Brian F. G. Bidulock    =A6 The reasonable man adapts himself to the =A6
> bidulock@openss7.org    =A6 world; the unreasonable one persists in  =A6
> http://www.openss7.org/ =A6 trying  to adapt the  world  to himself. =A6
>                         =A6 Therefore  all  progress  depends on the =A6
>                         =A6 unreasonable man. -- George Bernard Shaw =A6
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20


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



From exim@www1.ietf.org  Fri Aug  8 11:31:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15208
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 11:31:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l9Cs-0001te-TU
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 11:31:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h78FV66c007286
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 11:31:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l9Cn-0001tI-O8; Fri, 08 Aug 2003 11:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l9CB-0001sj-Cv
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 11:30:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15171
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 11:30:18 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l9CA-0001WE-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 11:30:22 -0400
Received: from [202.54.26.202] (helo=hindon.hss.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19l9C3-0001Vn-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 11:30:16 -0400
Received: from ultra.hss.co.in (ultra [192.168.100.5] (may be forged))
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h78FR1w29376;
	Fri, 8 Aug 2003 20:57:01 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h78FTW821255;
	Fri, 8 Aug 2003 20:59:33 +0530 (IST)
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
To: "BAND,RICHARD (HP-France,ex1)" <richard.band@hp.com>
Cc: Vivek Toky <vivektoky@ccpu.com>, sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF397F08A8.9C062FF8-ON65256D7C.00520F7C@hss.hns.com>
Date: Fri, 8 Aug 2003 20:53:59 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 08/08/2003
 08:52:41 PM
MIME-Version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: base64
Content-Transfer-Encoding: base64
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: base64

DQoNCg0KDQpIaSBSaWNoYXJkLA0KICAgWW91IGFyZSByaWdodCB0aGF0IGluIElHIDA0IElQU1Ag
REUgYmVoYXZpb3VyIGlzIHNpbWlsYXIgdG8NCiAgIFNHUCBiZWhhdmlvdXIgaW4gQVNQLVNHUCBz
Y2VuYXJpbyBhcyB0aGUgdGV4dCBhdHRhY2hlZA0KICAgZnJvbSBJRyAwNCBiZWxvdyBwcm9wb3Nl
cyA6DQoNCiAgIEluIHNlY3Rpb24gNC4zLjE6IEFTUC9JUFNQIFN0YXRlcywgb25seSB0aGUgU0dQ
LUFTUCBhbmQgdGhlIElQU1AgU0UNCiAgIHNjZW5hcmlvcyBhcmUgZGVzY3JpYmVkLiBGb3IgdGhl
IElQU1AgREUgbW9kZWwsIGJvdGggSVBTUHMgTVVTVA0KICAgZm9sbG93IHRoZSBTR1Agc2lkZSBv
ZiB0aGUgU0dQLUFTUCBwcm9jZWR1cmVzLg0KDQogICBBY2NvcmRpbmcgdG8gdGhpcyB5b3UgYXJl
IHJpZ2h0IHRoYXQgSVBTUCBBIHdpbGwgc3RpbGwgYmUgYWJsZSB0bw0KICAgc2VuZCBBUzIgbWVz
c2FnZXMgdG8gSVBTUCBDIGJlY2F1c2UgaXQgaGFzIG5vdCByZWNlaXZlZCBBU1BJQQ0KICAgbWVz
c2FnZSBmcm9tIElQU1AgQy4NCg0KICAgQnkgZG9pbmcgdGhpcyBsb2NhbCBJUFNQIHRvdGFsbHkg
ZGVwZW5kcyBvbiByZW1vdGUgSVBTUCdzDQogICAoQVNQQUMgb3IgQVNQSUEpIG1lc3NhZ2VzIHRv
IHNlbmQgbG9jYWwgSVBTUCdzIGFwcGxpY2F0aW9ucw0KICAgZGF0YSB0byByZW1vdGUgSVBTUC5T
aG91bGQgbm90IGxvY2FsIElQU1Aga25vdyB0aGUgc3RhdHVzIG9mDQogICBpdHMgbG9jYWwgYXBw
bGljYXRpb24gYmVmb3JlIHNlbmRpbmcgZGF0YSB0byB0aGUgcGVlciBJUFNQDQogICBmb3IgYSBn
aXZlbiBhcHBsaWNhdGlvbi5EbyB5b3UgbWVhbiB0byBzYXkgdGhhdCBpZiBsb2NhbA0KICAgYXBw
bGljYXRpb24gc2VuZHMgZGF0YSB0aHJvdWdoIGxvY2FsIElQU1AgaXQgaXMgYWN0aXZlIGZvcg0K
ICAgc2VuZGluZywgd2UgZG9udCBuZWVkIHRvIGNoZWNrIHRoZSBsb2NhbCBzdGF0dXMgb2YgYXBw
bGljYXRpb24NCiAgIGluIGxvY2FsIElQU1AuSVBTUCBiZWhhdmlvdXIgaXMgdXNlciB0byB1c2Vy
IGNvbW11bmljYXRpb24NCiAgIElNTyBpdCBpcyBkaWZmZXJlbnQgZnJvbSBTR1AgYmVoYXZpb3Vy
LlBsZWFzZSBjb21tZW50DQpSZWdhcmRzDQpLYW1lc2ggS2F1bA0Kd3d3Lmhzc3dvcmxkLmNvbQ0K
SHVnaGVzIFNvZnR3YXJlIFN5c3RlbXMNCg0KDQoNCg0KDQoNCiJCQU5ELFJJQ0hBUkQgKEhQLUZy
YW5jZSxleDEpIiA8cmljaGFyZC5iYW5kQGhwLmNvbT5AaWV0Zi5vcmcgb24gMDgvMDgvMjAwMw0K
MDI6NTA6MDUgUE0NCg0KU2VudCBieTogICAgc2lndHJhbi1hZG1pbkBpZXRmLm9yZw0KDQoNClRv
OiAgICBLYW1lc2ggS2F1bC9IU1NASFNTLCBWaXZlayBUb2t5IDx2aXZla3Rva3lAY2NwdS5jb20+
DQpjYzogICAgc2lndHJhbkBpZXRmLm9yZw0KDQpTdWJqZWN0OiAgICBSRTogW1NpZ3RyYW5dIE0z
VUEgOiBJUFNQIERFIGJlaGF2aW91cg0KDQoNCkhpIEthbWVzaCwNCg0KVGhlIHRleHQgeW91IHJl
ZmVyIHRvIGRlc2NyaWJlcyBib3RoIFNFIGFuZCBERSBJUFNQIGJlaGF2aW9yLg0KQm90aCBiZWhh
dmlvcnMgaGF2ZSBiZWVuIGNsZWFybHkgc2VwYXJhdGVkIGluIHRoZSBJRywgYW5kIGhhdmUgYmVl
bg0KZGVzY3JpYmVkIGluIG1vcmUgZGV0YWlsLg0KDQpTcGVjaWZpY2FsbHksIGluIERFIElQU1As
IHRoZSBBUyBGU00gc2hvd3MgdGhhdCB0aGUgQVMgc3RhdGUgYXMgc2VlbiBieSB0aGUNClNHUCBv
ciBieSBhIHJlbW90ZSBJUFNQIG9ubHkgY2hhbmdlcyBhdCB0aGUgcmVjZXB0aW9uIG9mIGFuIEFT
UElBLg0KU28sIGlmIElQU1AgQSBzZW5kcyBhbiBBU1BJQSBmb3IgQVMgMSwgaXQgb25seSBtZWFu
cyB0aGF0IElQU1AgQSBpcyBubw0KbG9uZ2VyIGFibGUgdG8gcmVjZWl2ZSB0cmFmZmljIGZvciBB
UzEuDQpJdCBkb2VzIG5vdCBtZWFuIHRoYXQgaXQgY2Fubm90IHNlbmQgdHJhZmZpYyBmcm9tIEFT
IDEgdG8gdGhlIEFTIGF0IElQU1AgQy4NCkFsdGhvdWdoIHlvdXIgaW1wbGVtZW50YXRpb24gbWF5
IG9wdCBub3QgdG8gc2VuZCBhbnkgdHJhZmZpYywgdGhlIHByb3RvY29sDQpkb2VzIGFsbG93IGl0
IHVudGlsIElQU1AgQyBzZW5kcyBhbiBBUElBIG9mIGl0cyBvd24uDQoNClJlZ2FyZHMsDQoNClJp
Y2hhcmQNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGtha2F1bEBoc3MuaG5z
LmNvbSBbbWFpbHRvOmtha2F1bEBoc3MuaG5zLmNvbV0NClNlbnQ6IFRodXJzZGF5LCBBdWd1c3Qg
MDcsIDIwMDMgMTI6MTINClRvOiBWaXZlayBUb2t5DQpDYzogc2lndHJhbkBpZXRmLm9yZw0KU3Vi
amVjdDogUkU6IFtTaWd0cmFuXSBNM1VBIDogSVBTUCBERSBiZWhhdmlvdXINCg0KDQoNCg0KSGkg
Vml2ZWssDQogICBQbGVhc2UgZ28gdGhyb3VnaCB0aGUgc2VjdGlvbiBhdHRhY2hlZCBmcm9tIFJG
QyAzMzMyDQogICA0LjMuNC40LjEgSVBTUCBDb25zaWRlcmF0aW9ucyAoQVNQIEluYWN0aXZlKQ0K
DQogICBBbiBJUFNQIG1heSBiZSBjb25zaWRlcmVkIGluIHRoZSBBU1AtSU5BQ1RJVkUgc3RhdGUg
YnkgYSByZW1vdGUgSVBTUA0KICAgYWZ0ZXIgYW4gQVNQIEluYWN0aXZlIG9yIEFTUCBJbmFjdGl2
ZSBBY2sgbWVzc2FnZSBoYXMgYmVlbiByZWNlaXZlZA0KICAgZnJvbSBpdC4NCg0KICAgQWx0ZXJu
YXRpdmVseSwgYW4gaW50ZXJjaGFuZ2Ugb2YgQVNQIEluYWN0aXZlIG1lc3NhZ2VzIGZyb20gZWFj
aCBlbmQNCiAgIGNhbiBiZSBwZXJmb3JtZWQuIFRoaXMgb3B0aW9uIGZvbGxvd3MgdGhlIEFTUCBz
dGF0ZSB0cmFuc2l0aW9uDQogICBkaWFncmFtIGFuZCBnaXZlcyB0aGUgYWRkaXRpb25hbCBhZHZh
bnRhZ2Ugb2Ygc2VsZWN0aW5nIGEgcGFydGljdWxhcg0KICAgQVMgdG8gYmUgZGVhY3RpdmF0ZWQg
ZnJvbSBlYWNoIGVuZC4gSXQgaXMgZXNwZWNpYWxseSB1c2VmdWwgd2hlbiBhbg0KICAgSVBTUCBp
cyBzZXJ2aW5nIG1vcmUgdGhhbiBvbmUgQVMuIEl0IHdvdWxkIG5lZWQgZm91ciBtZXNzYWdlcyBm
b3INCiAgIGNvbXBsZXRpb24uDQoNCiAgIElNTyBJUFNQIEEgaW4geW91ciBleGFtcGxlIGFmdGVy
IHNlbmRpbmcgQVNQSUEgbWVzc2FnZSBmb3IgQVMxIHdvdWxkDQogICBub3QgYmUgYWJsZSB0byBz
ZW5kIG9yIHJlY2VpdmUgdHJhZmZpYyBmcm9tIG9yIGZvciBBUzEuDQoNClJlZ2FyZHMNCkthbWVz
aCBLYXVsDQp3d3cuaHNzd29ybGQuY29tDQpIdWdoZXMgU29mdHdhcmUgU3lzdGVtcw0KDQoNCg0K
DQoNCg0KDQoNCiJWaXZlayBUb2t5IiA8dml2ZWt0b2t5QGNjcHUuY29tPkBpZXRmLm9yZyBvbiAw
OC8wNy8yMDAzIDEwOjAwOjA5IEFNDQoNClNlbnQgYnk6ICAgIHNpZ3RyYW4tYWRtaW5AaWV0Zi5v
cmcNCg0KDQpUbzogICAgS2FtZXNoIEthdWwvSFNTQEhTUw0KY2M6ICAgIDxzaWd0cmFuQGlldGYu
b3JnPg0KDQpTdWJqZWN0OiAgICBSRTogW1NpZ3RyYW5dIE0zVUEgOiBJUFNQIERFIGJlaGF2aW91
cg0KDQoNCg0KS2FtZXNoLA0KDQogIFNlZSBteSBjb21tZW50cyBJbmxpbmUuLg0KDQotLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbToga2FrYXVsQGhzcy5obnMuY29tIFttYWlsdG86a2Fr
YXVsQGhzcy5obnMuY29tXQ0KU2VudDogV2VkbmVzZGF5LCBBdWd1c3QgMDYsIDIwMDMgODo0NyBQ
TQ0KVG86IHZpdmVrdG9reUBjY3B1LmNvbQ0KQ2M6IHNpZ3RyYW5AaWV0Zi5vcmcNClN1YmplY3Q6
IFtTcGFtXSBSRTogW1NpZ3RyYW5dIE0zVUEgOiBJUFNQIERFIGJlaGF2aW91cg0KDQoNCg0KDQoN
Cg0KDQpWaXZlaw0KICAgICAgUGxlYXNlIHNlZSBjb21tZW50cyBpbiBsaW5lDQoNCg0KDQoiVml2
ZWsgVG9reSIgPHZpdmVrdG9reUBjY3B1LmNvbT5AaWV0Zi5vcmcgb24gMDgvMDUvMjAwMyAwOTo0
Nzo0MyBBTQ0KDQpTZW50IGJ5OiAgICBzaWd0cmFuLWFkbWluQGlldGYub3JnDQoNCg0KVG86ICAg
ICJrYW1lc2gga2F1bCIgPGtra19rYXVsQHlhaG9vLmNvbT4NCmNjOiAgICA8c2lndHJhbkBpZXRm
Lm9yZz4NCg0KU3ViamVjdDogICAgUkU6IFtTaWd0cmFuXSBNM1VBIDogSVBTUCBERSBiZWhhdmlv
dXINCg0KDQpLYW1lc2gsDQogIFBsZWFzZSBzZWUgY29tbWVudHMgaW5saW5lDQotLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogc2lndHJhbi1hZG1pbkBpZXRmLm9yZyBbbWFpbHRvOnNp
Z3RyYW4tYWRtaW5AaWV0Zi5vcmddT24gQmVoYWxmIE9mDQprYW1lc2gga2F1bA0KU2VudDogU2F0
dXJkYXksIEF1Z3VzdCAwMiwgMjAwMyA4OjI0IFBNDQpUbzogVml2ZWsgVG9reQ0KQ2M6IHNpZ3Ry
YW5AaWV0Zi5vcmcNClN1YmplY3Q6IFJFOiBbU2lndHJhbl0gTTNVQSA6IElQU1AgREUgYmVoYXZp
b3VyDQoNCg0KSGkgVml2ZWssDQogICAgSSBhcmdlZSB3aXRoIHlvdSB0aGF0IGlmIHdlIGludGVy
bWl4IElQU1AgU0UgYW5kDQpERSBtb2RlbHMgd2UgY2FuIHN0YXJ0IGxvYWRzaGFyaW5nIHRyYWZm
aWMgZm9yIEFTMg0KYW1vbmcgSVBTUCBCIGFuZCBJUFNQIEEgZXZlbiB0aG91Z2ggSVBTUCBCIGhh
cyBub3QNCnJlY2VpdmVkIEFTUEFDIG1lc3NhZ2UgZnJvbSBJUFNQIGMuSXQgd291bGQgcmVzdWx0
IGluDQppbnRlcm1peGluZyBvZiB0d28gSVBTUCBtb2RlbHMuRm9yIHNvbWUgbWVzc2FnZXMgSVBT
UA0KQyBoYXMgdG8gYmVoYXZlIGluIERFIG1hbm5lciBhbmQgZm9yIG90aGVyIFNFDQpiZWhhdmlv
dXIgaXMgcmVxdWlyZWQuTGV0cyB0YWtlIHlvdXIgZXhhbXBsZS4gT24NCnJlY2VpdmluZyBBU1BB
QyBtZXNzYWdlcyBmcm9tIElQU1AgQSBhbmQgSVBTUCBCIGZvcg0KQVMxIElQU1AgQyB1cGRhdGVz
IG9ubHkgcmVtb3RlIElQU1AnUyBzdGF0ZXMgZm9yIEFTMQ0KYmVoYXZpbmcgaW4gREUgbWFubmVy
LndoZW4gSVBTUCBjIHNlbmRzIEFTUEFDIGZvciBBUzINCnRvIElQU1AgQSBhbmQgcmVjZWl2ZXMg
QUNLIGJhY2sgdGhlbiBhbHNvIElQU1AgQw0KY2hhbmdlcyBpdHMgc3RhdGUgdG8gYWN0aXZlIGZv
ciBsb2NhbCBBUzIgYmVoYXZpbmcgaW4NCkRFIG1hbm5lci5Ob3cgYXMgeW91IHNhaWQgQmktZGly
ZWN0aW9uYWwgZGF0YSBpcw0KZmxvd2luZyBmcm9tIElQU1AgQyBhbmQgSVBTUCBBIHdoZXJlIGFz
IHNpbmdsZQ0KZGlyZWN0aW9uIHRyYWZmaWMgaXMgcG9zc2libGUgZnJvbSBJUFNQIEMgdG8gSVBT
UCBCDQooZm9yIEFTMikuTm93IGFzc3VtZSBJUFNQIEEgc2VuZHMgQVNQSUEgbWVzc2FnZSBmb3IN
CkFTMSB0byBJUFNQIEMgaW4gdGhpcyBjYXNlIElQU1AgYyBvbiByZWNlaXZpbmcgQVNQSUENCm1l
c3NhZ2UgaGFzIHRvIHVwZGF0ZSBzdGF0ZSBvZiByZW1vdGUgSVBTUCBBIGluIEFTMQ0KYW5kIGFs
c28gc3RhdGUgb2YgbG9jYWwgSVBTUCBDIGluIGxvY2FsIEFTMiBiZWhhdmluZw0KaW4gU0UgbWFu
bmVyLg0KDQpbVml2ZWtdDQogWW91IGhhdmUgYSBnb29kIHBvaW50IGJ1dCBJIGRpZCBub3QgdW5k
ZXJzdGFuZCB3aHkgd291bGQgd2UgbmVlZCB0byBjaGFuZ2UNCnRoZSBzdGF0ZSBvZiBJUFNQIEMg
aW4gdGhpcyBjYXNlICggd2hlbiBJUFNQIEEgc2VuZHMgQVNQSUEgdG8gSVBTUCBDKS4gV2hlbg0K
SVBTUCBBIHNlbmRzIEFTUElBIG1lc3NhZ2UgZm9yIEFTMSB0byBJUFNQIEMgdGhlbiBvbmx5IElQ
U1AgQSdzIHN0YXRlIHdpbGwNCmNoYW5nZSBpbiBsb2NhbCBBUzEgYW5kIHRoZSBjb3JyZXNwb25k
aW5nIHJlbW90ZSBBUzEgb24gdGhlIG90aGVyIHNpZGUuIFlvdQ0KYXJlIHJpZ2h0IHRoYXQgQVMx
IHdpbGwgbm90IGJlIGFibGUgdG8gcmVjZWl2ZSB0cmFmZmljIHRocm91Z2ggSVBTUCBBICwgYnV0
DQp0aGF0IGRvZXNub3QgcmVzdHJpY3QgQVMxIHRvIHNlbmQgdHJhZmZpYyBmcm9tIElQU1AgQS4N
CltLYW1lc2hdDQpJUFNQIEEgaXMgaW5hY3RpdmUgKGl0IGhhcyBzZW5kIEFTUElBKSBmb3IgQVMx
IHNvIGhvdyBjYW4gaXQgc2VuZCBkYXRhIGZvcg0KQVMxLg0KKioqKlZpdmVrKioqKioNClRoYXQg
aXMgd2hhdCBJIGFtIHRyeWluZyB0byBzYXksIElQU1AgQSBpcyBpbmFjdGl2ZSB0byByZWNlaXZl
IGRhdGEuIEl0IGNhbg0Kc3RpbGwgc2VuZCBkYXRhIGJlY2F1c2UgcmVtb3RlIGRlc3RpbmF0aW9u
IGlzIHN0aWxsIGFjdGl2ZSB0byByZWNlaXZlIGRhdGENCnRocm91Z2ggIElQU1AgQQ0KSWYgc2Vu
ZGluZyBhbiBBY3RpdmUgbWVzc2FnZSBtZWFucyBpdCB3aWxsIGJlIGFibGUgdG8gc2VuZCBhbmQg
cmVjZWl2ZSBkYXRhDQp0aGVuIGFuIEFjdGl2ZSBBY2sgZnJvbSBvdGhlciB3b3VsZCBoYXZlIGJl
ZW4gc3VmZmNpZW50IHRvIHRlbGwgSVBTUCBBIHRoYXQNCml0IGNhbiBzdGFydCBzZW5kaW5nIGRh
dGEgYXMgd2VsbC4gQnV0IGl0IGRpZCBub3QgaGFwcGVuLi4gSVBTUCBDIHNlbnQgYW4NCmV4cGxp
Y2l0IEFjdGl2ZSBtZXNzYWdlIHRvIGluZGljYXRlIHRoYXQgaXRzIHJlYWR5IHRvIHJlY2VpdmUg
ZGF0YSBzbyBJUFNQDQpDIGlzIHRoZSBvbmUgd2hvIHdpbGwgaW5kaWNhdGUgdGhhdCBub3cgaXQg
aXMgbm90IGdvaW5nIHRvIHJlY2VpdmUgZGF0YS4NCklQU1AgQSBkb2VzIG5vdCBuZWVkIHRvIHN0
b3Agc2VuZGluZyBkYXRhIHRvIElQU1AgQyBqdXN0IGJlY2F1c2UgaXQgc2VuZA0KQVNQSUEgbWVz
c2FnZS4NCioqKioqKioqKioqKioqDQoNCk5vdGU6IEFTMSBpcyBzdGlsbCBVUA0KYW5kIHJlYWR5
IHRvIHByb2Nlc3MgZGF0YSBhbmQgc28gaXMgQVMyLiBJZiBBUzEgd2FudHMgdG8gZ28gZG93biBh
bmQgbm90DQpwcm9jZXNzIGRhdGEgYXQgYWxsIHRoZW4gaXQgc2hvdWxkIHNlbnQgSW5hY3RpdmUg
dGhyb3VnaCBib3RoIHRoZSBJUFNQcyAoDQpJUFNQIEEgYW5kIElQU1AgQikuDQpbS2FtZXNoXQ0K
IElQU1AgQiBjYW50J3Qgc2VuZCBkYXRhIGZvciBBUzEgdG8gSVBTUCBDIGJlY2F1c2UgSVBTUCBD
IGhhcyBub3Qgc2VuZA0KQVNQQUMgbWVzc2FnZSB0byBpdC5TbyBpdCBtZWFucyB0aGF0IEFTMSdz
IGRhdGEgY2FudCByZWFjaCBJUFNQIEMgYmVjYXVzZQ0KSVBTUCBBIGlzIGluYWN0aXZlIGZvciBB
UzEgYW5kIElQU1AgQiBoYXMgbm90IHJlY2VpdmVkIEFTUEFDIG1lc3NhZ2UgZnJvbQ0KSVBTUCBD
Lg0KTm93IHRoZSBxdWVzdGlvbiBhcmlzZXMgdGhhdCB3aGF0IHNob3VsZCBJUFNQIEEgZG8gaWYg
aXQNCnJlY2VpdmVzIGRhdGEgZnJvbSBBUzEgd2hpY2ggaGFzIGluYWN0aXZhdGVkIGl0c2VsZiBm
cm9tIGJvdGggIHRoZSBJUFNQcw0KYW5kDQppcyBub3cgdG90YWxseSB1bmFibGUgdG8gcmVjZWl2
ZSBEQVRBID8gLi4uIGZvbGxvd2luZyBwb2ludHMgc2hvdWxkIGJlDQpub3RlZA0KMS4gSWYgQVMx
IGRvZXNuJ3Qgd2FudCB0byByZWNlaXZlIGRhdGEsIHdoeSB3ZSBjYXJlIGlmIHRoZSBkYXRhIHNl
bnQgYnkgQVMxDQp3ZW50IHRocm91Z2ggYWxsIHRoZSB3YXkgdG8gQVMyLg0KMi4gTm93IHdlIGtu
b3cgdGhhdCBBUzIgd29uJ3QgYmUgYWJsZSB0byBzZW5kIGRhdGEgdG8gQVMxIGF0YWxsIHNvIGl0
IGNhbg0KdGFrZSByZWNvdmVyeSBhbmQgRGUtYWN0aXZhdGUgaXRzZWxmIHRocm91Z2ggSVBTUCBB
ICh0byB3aGljaCBpdCBzZW50IEFTUA0KQWN0aXZlIGFuZCBnb3QgQWN0aXZlIEFjay4pDQoNCmRv
ZXMgaXQgbWFrZSBzZW5zZSA/IHBsZWFzZSBjb21tZW50Li4NCg0KW0thbWVzaF0NCiBXZSBoYXZl
IHRvIGNoZWNrIHRoZSBzdGF0ZSBvZiBsb2NhbCBJUFNQIGJlZm9yZSBzZWxlY3RpbmcgcmVtb3Rl
DQphcHBsaWNhdGlvbiBzZXJ2ZXIgZm9yIGRhdGENCg0KDQpJZiBJUFNQIEMgZG9lcyBub3QgYm90
aGVyIGFib3V0IGxvY2FsDQpzdGF0ZSB1cGRhdGlvbiBvbiByZWNlaXZpbmcgQVNQSUEgZnJvbSBJ
UFNQIEEsIElQU1AgQw0Kd2lsbCBjb250aW51ZSB0byBzZW5kIGRhdGEgbWVzc2FnZXMgZm9yIEFT
MiB0byBJUFNQIEINCndpdGhvdXQgcmVjZWl2aW5nIGFueXRoaW5nIGZyb20gb3RoZXIgc2lkZS4g
VGhpcyB3aWxsDQpyZXN1bHQgaW4gc2luZ2xlIGRpcmVjdGlvbiB0cmFmZmljIGZyb20gSVBTUCBD
IHRvIEFTMQ0Kd2l0aG91dCB0aGUga25vd2xlZGdlIG9mIElQU1AgQy5JZiB3ZSBhc3NvY2lhdGUg
QVMNCnN0YXRlIHdpdGggbG9jYWwgYW5kIHBlZXIgSVBTUCdzIChpbiB5b3VyIGV4YW1wbGUNCkFT
MidzIHN0YXRlIHdpdGggSVBTUCBjIGFuZCBlYWNoIHBlZXIgSVBTUEEgYW5kIElQU1BCLA0KQVMy
J3Mgc3RhdGUgd2l0aCBJUFNQIEMgYW5kIGVhY2ggcGVlciBJUFNQJ3MpIHNpbmdsZQ0KZGlyZWN0
aW9uIHRyYWZmaWMgZmxvdyBpcyBub3QgcG9zc2libGUuIFBsZWFzZSBjb21tZW50DQoNClJlZ2Fy
ZHMNCkthbWVzaA0KLS0tIFZpdmVrIFRva3kgPHZpdmVrdG9reUBjY3B1LmNvbT4gd3JvdGU6DQo+
IEhpIEthbWVzaCwNCj4gICBBbHRob3VnaCBBU1BBQyBtZXNzYWdlIGhhcyBub3QgYmVlbiBzZW50
IHRvIElQU1ANCj4gQiwgYnV0IHRoZSBsb2NhbCBBUyBpcw0KPiBzdGlsbCBhY3RpdmUgYW5kIGlz
IHNlbmRpbmcgYW5kIHJlY2VpdmluZyB0cmFmZmljDQo+IHRocm91Z2ggSVBTUCBBLiBOb3cgb24g
dGhlDQo+IG90aGVyIHNpZGUgSVBTUCBBIGFuZCBJUFNQIEIgYXJlIHBhcnQgb2YgdGhlIHNhbWUg
QVMNCj4gKCBBUzEgKS4gU28gZm9sbG93aW5nDQo+IHBvaW50cyBzaG91bGQgYmUgbm90ZWQuDQo+
DQo+IDEuIEJpLWRpcmVjdGlvbmFsIHRyYWZmaWMgYmV0d2VlbiBBUzEgYW5kIEFTMiBpcw0KPiBw
b3NzaWJsZQ0KPiAyLiBJUFNQIEIgaGFzIGFscmVhZHkgc2VudCBBU1BBQyBhbmQgcmVjZWl2ZWQg
QVNQQUMNCj4gQWNrLCBzbyBpdCBpcyByZWFkeSB0bw0KPiByZWNlaXZlIHRyYWZmaWMuDQo+DQo+
ICBTbyB3aHkgZG9uJ3Qgd2UgbG9hZHNoYXJlIHRoZSB0cmFmZmljIGFtb25nIElQU1AgQQ0KPiBh
bmQgSVBTUCBCIGFzIHRoZQ0KPiB0cmFmZmljIGlzIGFueXdheSBnb2luZyB0byBnZXQgdG8gdGhl
IHNhbWUNCj4gZGVzdGluYXRpb24gaS5lLiBBUzENCj4NCj4gSW4gdGhlIHJldmVyc2UgZGlyZWN0
aW9uIEFTMSBjYW4gY2hvb3NlIElQU1AgQSB0bw0KPiBzZW5kIHRyYWZmaWMgdG93YXJkcyBBUzIs
DQo+IGFzIG9ubHkgSVBTUCBBIGhhcyByZWNlaXZlZCBBU1BBQyBmcm9tIElQU1AgQyAoZm9yDQo+
IEFTMikNCj4NCj4gY29tbWVudHM/DQo+DQo+IC1WaXZlay4NCj4NCj4gLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCj4gRnJvbTogc2lndHJhbi1hZG1pbkBpZXRmLm9yZw0KPiBbbWFpbHRvOnNp
Z3RyYW4tYWRtaW5AaWV0Zi5vcmddT24gQmVoYWxmIE9mDQo+IGtha2F1bEBoc3MuaG5zLmNvbQ0K
PiBTZW50OiBGcmlkYXksIEF1Z3VzdCAwMSwgMjAwMyAxOjE2IEFNDQo+IFRvOiBWaXZlayBUb2t5
DQo+IENjOiBzaWd0cmFuQGlldGYub3JnDQo+IFN1YmplY3Q6IFJFOiBbU2lndHJhbl0gTTNVQSA6
IElQU1AgREUgYmVoYXZpb3VyDQo+DQo+DQo+DQo+DQo+DQo+DQo+IFZpdmVrLA0KPg0KPiBJbiB5
b3VyIGV4YW1wbGUgYWxzbyBJUFNQIEMgd2lsbCBzZW5kIGRhdGEgZm9yIEFTMQ0KPiB0byBJUFNQ
IEEgb25seS5JIGRvbnQNCj4gc2VlIGFueSByZWFzb24gZm9yIElQU1AgQyB0byBzZW5kIGRhdGEg
dG8gSVBTUCBCDQo+IGJlY2F1c2UgQVNQQUMgbWVzc2FnZSBpcw0KPiBub3Qgc2VudCB0byBJUFNQ
IEIuIEkgZG9udCBzZWUgYW55IHBvc3NpYmlsaXR5IG9mDQo+IHNpbmdsZSBkaXJlY3Rpb24gdHJh
ZmZpYw0KPiBmbG93IGluIHlvdXIgZXhhbXBsZSBhbHNvLg0KPg0KPiBLYW1lc2ggS2F1bA0KPiB3
d3cuaHNzd29ybGQuY29tDQo+IEh1Z2hlcyBTb2Z0d2FyZSBTeXN0ZW1zDQo+DQo+DQo+DQo+DQo+
ICJWaXZlayBUb2t5IiA8dml2ZWt0b2t5QGNjcHUuY29tPiBvbiAwOC8wMS8yMDAzDQo+IDAxOjIz
OjExIFBNDQo+DQo+IFRvOiAgICBLYW1lc2ggS2F1bC9IU1NASFNTLCBzaWd0cmFuQGlldGYub3Jn
DQo+IGNjOg0KPg0KPiBTdWJqZWN0OiAgICBSRTogW1NpZ3RyYW5dIE0zVUEgOiBJUFNQIERFIGJl
aGF2aW91cg0KPg0KPg0KPiBLYW1lc2gsDQo+DQo+ICAgU2luZ2xlIGRpcmVjdGlvbiB0cmFmZmlj
IHdpbGwgc3RpbGwgYmUgcG9zc2libGUuDQo+IElmIHlvdSBsb29rIGF0IG15DQo+IGV4YW1wbGUg
Y2FyZWZ1bGx5IHlvdSB3aWxsIG5vdGljZSB0aGF0IGluIGNhc2Ugb2YgMw0KPiBJUFNQcywgaXQg
d2lsbCBiZQ0KPiBwb3NzaWJsZS4gSXQgbWF5IGJlIGZvciBhIHNob3J0IGR1cmF0aW9uIG9mIHRp
bWUuIEluDQo+IG15IGV4YW1wbGUgbG9jYWwNCj4gQVMgaXMgYWxyZWFkeSBBY3RpdmUgYXMgaXQg
c2VudCBBU1AgQWN0aXZlIG1lc3NhZ2UNCj4gdG8gb25lIG9mIHRoZSBwZWVyDQo+IElQU1BzICgg
YWxzbyBnb3QgdGhlIEFDSyBiYWNrICkNCj4NCj4gcGxlYXNlIGdvIHRocm91Z2ggdGhlIGV4YW1w
bGUgYWdhaW4gLi4gd2FpdGluZyBmb3INCj4gY29tbWVudHMgPw0KPg0KPiBWaXZlaw0KPiA+DQo+
ID4NCj4gPg0KPiA+DQo+ID4gSGkgU29tZSBjb21tZW50cyBiZWxvdw0KPiA+DQo+ID4gIFdoZW4g
SVBTUCBCIHJlY2VpdmVzIEFTUEFDIG1lc3NhZ2UgZnJvbSBJUFNQIEENCj4gZm9yIEFTMSBpdCBt
YXJrcw0KPiByZW1vdGUNCj4gPiBJUFNQIEEgYWN0aXZlIGZvciByZW1vdGUgQVMxIGFuZCBzZW5k
cyBBU1BBQyBhY2sNCj4gYmFjayBmb3IgQVMxIHRvDQo+IElQU1AgQS5Ob3cNCj4gPiB3aXRoIHRo
ZXNlIG1lc3NhZ2UgZXhjaGFuZ2VzIGl0IG1lYW5zIHRoYXQgSVBTUCBBDQo+IGlzIHJlYWR5IHRv
IHJlY2VpdmUNCj4gPiB0cmFmZmljIGZvciBBUzEuQXQgdGhpcyBwb2ludCBvZiB0aW1lIElQU1Ag
QiBoYXMNCj4gbm90IGV4cHJlc3NlZCBpdHMNCj4gPiB3aWxsaW5nbmVzcyB0byBzZW5kIGRhdGEg
Zm9yIGFueSBBUy5JUFNQIEIgIGNhbm5vdA0KPiAgc2VuZCBhbnkNCj4gYXBwbGljYXRpb24NCj4g
PiBkYXRhIGJlY2F1c2UgaXRzIGxvY2FsIGFwcGxpY2F0aW9ucyBhcmUgbm90IGFjdGl2ZQ0KPiB5
ZXQuU28gc2luZ2xlDQo+IGRpcmVjdGlvbg0KPiA+IHRyYWZmaWMgZmxvdyB3aWxsIG5ldmVyIG9j
Y3VyLk5vdyB3aGVuIElQU1AgQg0KPiBzZW5kcyBBU1BBQyBtZXNzYWdlDQo+IGZvciBBUzINCj4g
PiB0byBJUFNQIEEgYW5kIGdldHMgYmFjayBBU1BBQyBhY2sgZm9yIEFTMiBpdCB3aWxsDQo+IGdp
dmUgcmVzdW1lDQo+IGluZGljYXRpb24gdG8NCj4gPiB1c2VyIG5vdy5BUzEgYW5kIEFTMiBhcmUg
YmFzaWNhbGx5IHNhbWUgdHlwZSBvZg0KPiBNVFAzIHVzZXJzLCBhbmQgdXNlcg0KPiB0bw0KPiA+
IHVzZXIgY29tbXVuaWNhdGlvbiB3aWxsIG9ubHkgc3RhcnQgaWYgYm90aCB1c2Vycw0KPiBhcmUg
cmVhZHkgYW5kDQo+IGFjdGl2ZS4NCj4gPg0KPiA+DQo+ID4gICAgICstLS0tLS0tLS0tLSsgICAg
ICAgICAgICAgICstLS0tLS0tLS0tLSsNCj4gPiAgICAgfCAgICAgICAgICAgfCAgICAgICAgICAg
ICAgfCAgICAgICAgICAgfA0KPiA+ICAgICB8IElQU1AgQSAgICB8ICAgICAgICAgICAgICB8IElQ
U1AgQiAgICB8DQo+ID4gICAgIHwgICAgICAgICAgICstLS0tLS0tLS0tLS0tLSsgICAgICAgICAg
IHwNCj4gPiAgICAgfCAgICAgICAgICAgfCAgICAgICAgICAgICAgfCAgICAgICAgICAgfA0KPiA+
ICAgICArLS0tLS0tLS0tLS0rICAgICAgICAgICAgICArLS0tLS0tLS0tLS0rDQo+ID4NCj4gPiAg
ICAgICAgIEFTMSAgICAgICAgICAgICAgICAgICAgICAgIEFTMg0KPiA+DQo+ID4gS2FtZXNoIEth
dWwNCj4gPiB3d3cuaHNzd29ybGQuY29tDQo+ID4gSHVnaGVzIFNvZnR3YXJlIFN5c3RlbXMNCj4g
Pg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4gIlZJdmVrIFRva3kiIDx2aXZla3Rva3lAY2NwdS5j
b20+QGlldGYub3JnIG9uDQo+IDA3LzMxLzIwMDMgMTE6MTk6MzkgUE0NCj4gPg0KPiA+IFNlbnQg
Ynk6ICAgIHNpZ3RyYW4tYWRtaW5AaWV0Zi5vcmcNCj4gPg0KPiA+DQo+ID4gVG86ICAgICJUb2xn
YSBBc3ZlcmVuIiA8dG9sZ2FfYXN2ZXJlbkB5YWhvby5jb20+LA0KPiA8c2lndHJhbkBpZXRmLm9y
Zz4NCj4gPiBjYzoNCj4gPg0KPiA+IFN1YmplY3Q6ICAgIFJFOiBbU2lndHJhbl0gTTNVQSA6IElQ
U1AgREUgYmVoYXZpb3VyDQo+ID4NCj4gPg0KPiA+IFRvbGdhLA0KPiA+DQo+ID4gLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBzaWd0cmFuLWFkbWluQGlldGYub3JnDQo+IFtt
YWlsdG86c2lndHJhbi1hZG1pbkBpZXRmLm9yZ11Pbg0KPiBCZWhhbGYgT2YNCj4gPiBUb2xnYSBB
c3ZlcmVuDQo+ID4gU2VudDogVGh1cnNkYXksIEp1bHkgMzEsIDIwMDMgMTA6MTkgQU0NCj4gPiBU
bzogc2lndHJhbkBpZXRmLm9yZw0KPiA+IFN1YmplY3Q6IFJFOiBbU2lndHJhbl0gTTNVQSA6IElQ
U1AgREUgYmVoYXZpb3VyDQo+ID4NCj4gPg0KPiA+IFZpdmVrLA0KPiA+IC0tLSBWaXZlayBUb2t5
IDx2aXZla3Rva3lAY2NwdS5jb20+IHdyb3RlOg0KPiA+ID4gUGxlYXNlIHNlZSBteSBjb21tZW50
cyBpbmxpbmUNCj4gPiA+DQo+ID4gPiA+IFNlZSBteSBvcGlnaW9uIG9ubGluZQ0KPiA+ID4gPg0K
PiA+ID4gPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4gPiA+ID4gRnJvbTogVml2
ZWsgVG9reSBbbWFpbHRvOnZpdmVrdG9reUBjY3B1LmNvbV0NCj4gPiA+ID4gPiBTZW50OiBUaHVy
c2RheSwgSnVseSAzMSwgMjAwMyAyOjQyIFBNDQo+ID4gPiA+ID4gVG86IFRvbGdhIEFzdmVyZW47
IHNpZ3RyYW5AaWV0Zi5vcmcNCj4gPiA+ID4gPiBTdWJqZWN0OiBSRTogW1NpZ3RyYW5dIE0zVUEg
OiBJUFNQIERFDQo+IGJlaGF2aW91cg0KPiA+ID4gPiA+DQo+ID4gPiA+ID4NCj4gPiA+ID4gPiBI
aSBUb2xnYSwNCj4gPiA+ID4gPiAgICJBYm92ZSBjYXNlIiBtZWFucw0KPiA+ID4gPiA+ICJ3aGVu
IEFTMSBoYXMgYWN0aXZhdGVkIGl0c2VsZiBieSBzZW5kaW5nDQo+ID4gPiA+ID4gIEFTUCBBY3Rp
dmUgZnJvbSBib3RoIHRoZSBJUFNQcyAoQSAmIEIpIGJ1dA0KPiA+ID4gPiA+ICBBUzIgaGFzIHNl
bnQgQVNQIEFjdGl2ZSBqdXN0IHRvIElQU1BfQS4iDQo+ID4gPiA+ID4NCj4gPiA+ID4gPiBJbiBt
eSBvcGluaW9uIElQU1BfQyBzaG91bGQgbG9hZHNoYXJlIHRoZQ0KPiA+ID4gdHJhZmZpYw0KPiA+
ID4gPiA+IGFzIGl0IGhhcyByZWNlaXZlZCBBU1AgYWN0aXZlIGZyb20gYm90aCB0aGUNCj4gPiA+
IElQU1BzDQo+ID4gPiA+ID4gc28gQVMxIGlzIGFjY2Vzc2libGUgdGhyb3VnaCBib3RoIG9mIHRo
ZXNlLg0KPiA+ID4gPiA+IEhvd2V2ZXIsIGl0IGlzIHRoZSByZXNwb25zaWJpbGl0eSBvZiBBUzEg
dG8NCj4gPiA+IHJvdXRlDQo+ID4gPiA+ID4gYWxsIHRoZSB0cmFmZmljIHRvd2FyZHMgQVMyIHRo
cm91Z2ggSVBTUF9BLg0KPiA+ID4gPg0KPiA+ID4gPiBJZiBJUFNQX0IgcmVjZWl2ZSBzb21lIHRy
YWZmaWMgZnJvbSBJUFNQX0MgQlVUDQo+IG5vDQo+ID4gPiBBUyBpcyBBQ1RJVkUgZm9yDQo+ID4g
PiBpdCBvbg0KPiA+ID4gPiBJUFNQX0MgY2FuIGl0IHJvdXRlIHRoaXMgdHJhZmZpYz8/Pw0KPiA+
ID4gPiBDQU4gYSBTRyBzZW5kIHRvIGEgc3M3IG5ldHdvcmsgYSBtZXNzYWdlDQo+IHJlY2VpdmUN
Cj4gPiA+IGZyb20gYW4gSU5BQ1RJVkUNCj4gPiA+IEFTUCAhDQo+DQo9PT0gbWVzc2FnZSB0cnVu
Y2F0ZWQgPT09DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRG8geW91
IFlhaG9vIT8NCllhaG9vISBDYWxlbmRhciAtIEZyZWUgb25saW5lIGNhbGVuZGFyIHdpdGggc3lu
YyB0byBPdXRsb29rKFRNKS4NCmh0dHA6Ly9jYWxlbmRhci55YWhvby5jb20NCg0KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClNpZ3RyYW4gbWFpbGluZyBs
aXN0DQpTaWd0cmFuQGlldGYub3JnDQpodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9zaWd0cmFuDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NClNpZ3RyYW4gbWFpbGluZyBsaXN0DQpTaWd0cmFuQGlldGYub3JnDQogaHR0cHM6
Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lndHJhbg0KDQoNCg0KDQoNCiJESVND
TEFJTUVSOiBUaGlzIG1lc3NhZ2UgaXMgcHJvcHJpZXRhcnkgdG8gSHVnaGVzIFNvZnR3YXJlIFN5
c3RlbXMgTGltaXRlZA0KKEhTUykgYW5kIGlzIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBv
ZiB0aGUgaW5kaXZpZHVhbCB0byB3aG9tIGl0IGlzDQphZGRyZXNzZWQuIEl0IG1heSBjb250YWlu
ICBwcml2aWxlZ2VkIG9yIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiBhbmQNCnNob3VsZCBub3Qg
YmUgY2lyY3VsYXRlZCBvciB1c2VkIGZvciBhbnkgcHVycG9zZSBvdGhlciB0aGFuIGZvciB3aGF0
IGl0IGlzDQppbnRlbmRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBtZXNzYWdlIGluIGVy
cm9yLCBwbGVhc2Ugbm90aWZ5IHRoZQ0Kb3JpZ2luYXRvciBpbW1lZGlhdGVseS4gSWYgeW91IGFy
ZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgeW91IGFyZQ0Kbm90aWZpZWQgdGhhdCB5b3Ug
YXJlIHN0cmljdGx5IHByb2hpYml0ZWQgZnJvbSB1c2luZywgY29weWluZywgYWx0ZXJpbmcsIG9y
DQpkaXNjbG9zaW5nIHRoZSBjb250ZW50cyBvZiB0aGlzIG1lc3NhZ2UuIEhTUyBhY2NlcHRzIG5v
IHJlc3BvbnNpYmlsaXR5IGZvcg0KbG9zcyBvciBkYW1hZ2UgYXJpc2luZyBmcm9tIHRoZSB1c2Ug
b2YgdGhlIGluZm9ybWF0aW9uIHRyYW5zbWl0dGVkIGJ5IHRoaXMNCmVtYWlsIGluY2x1ZGluZyBk
YW1hZ2UgZnJvbSB2aXJ1cy4iDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NClNpZ3RyYW4gbWFpbGluZyBsaXN0DQpTaWd0cmFuQGlldGYub3JnDQog
aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lndHJhbg0KSigtailiICBi
4bSy1KIaJ34GaQ0KYnouDw0Kailman/FimI/KC0NCg0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NClNpZ3RyYW4gbWFpbGluZyBsaXN0DQpTaWd0cmFuQGll
dGYub3JnDQogaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lndHJhbg0K




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



From exim@www1.ietf.org  Fri Aug  8 11:39:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15375
	for <sigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 11:39:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l9KX-0002Mq-IL
	for sigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 11:39:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h78Fd1kV009093
	for sigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 11:39:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l9KX-0002MO-1x; Fri, 08 Aug 2003 11:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l9Jl-0002KV-B3
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 11:38:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15333
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 11:38:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l9Jk-0001YZ-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 11:38:12 -0400
Received: from web12807.mail.yahoo.com ([216.136.174.42])
	by ietf-mx with smtp (Exim 4.12)
	id 19l9Jj-0001YW-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 11:38:11 -0400
Message-ID: <20030808153810.14013.qmail@web12807.mail.yahoo.com>
Received: from [208.255.120.2] by web12807.mail.yahoo.com via HTTP; Fri, 08 Aug 2003 08:38:10 PDT
Date: Fri, 8 Aug 2003 08:38:10 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
To: sigtran@ietf.org
In-Reply-To: <OF397F08A8.9C062FF8-ON65256D7C.00520F7C@hss.hns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Hi Kamesh,

If one chooses IPSP-DE, while sending DATA, only the
status of the remote AS is considered, exactly like in
SGP/ASP case. IMO, considering local AS state on M3UA
level for DE mode is not correct. If one wants to do
so, one needs to choose SE mode. But one can do such a
harmonization on an upper layer (for example on NIF)
for DE mode of operation, which is implementation
dependent.

     Tolga
--- kakaul@hss.hns.com wrote:
> 
> 
> 
> 
> Hi Richard,
>    You are right that in IG 04 IPSP DE behaviour is
> similar to
>    SGP behaviour in ASP-SGP scenario as the text
> attached
>    from IG 04 below proposes :
> 
>    In section 4.3.1: ASP/IPSP States, only the
> SGP-ASP and the IPSP SE
>    scenarios are described. For the IPSP DE model,
> both IPSPs MUST
>    follow the SGP side of the SGP-ASP procedures.
> 
>    According to this you are right that IPSP A will
> still be able to
>    send AS2 messages to IPSP C because it has not
> received ASPIA
>    message from IPSP C.
> 
>    By doing this local IPSP totally depends on
> remote IPSP's
>    (ASPAC or ASPIA) messages to send local IPSP's
> applications
>    data to remote IPSP.Should not local IPSP know
> the status of
>    its local application before sending data to the
> peer IPSP
>    for a given application.Do you mean to say that
> if local
>    application sends data through local IPSP it is
> active for
>    sending, we dont need to check the local status
> of application
>    in local IPSP.IPSP behaviour is user to user
> communication
>    IMO it is different from SGP behaviour.Please
> comment
> Regards
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
> 
> 
> 
> 
> 
> 
> "BAND,RICHARD (HP-France,ex1)"
> <richard.band@hp.com>@ietf.org on 08/08/2003
> 02:50:05 PM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    Kamesh Kaul/HSS@HSS, Vivek Toky
> <vivektoky@ccpu.com>
> cc:    sigtran@ietf.org
> 
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> Hi Kamesh,
> 
> The text you refer to describes both SE and DE IPSP
> behavior.
> Both behaviors have been clearly separated in the
> IG, and have been
> described in more detail.
> 
> Specifically, in DE IPSP, the AS FSM shows that the
> AS state as seen by the
> SGP or by a remote IPSP only changes at the
> reception of an ASPIA.
> So, if IPSP A sends an ASPIA for AS 1, it only means
> that IPSP A is no
> longer able to receive traffic for AS1.
> It does not mean that it cannot send traffic from AS
> 1 to the AS at IPSP C.
> Although your implementation may opt not to send any
> traffic, the protocol
> does allow it until IPSP C sends an APIA of its own.
> 
> Regards,
> 
> Richard
> 
> -----Original Message-----
> From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
> Sent: Thursday, August 07, 2003 12:12
> To: Vivek Toky
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> 
> 
> Hi Vivek,
>    Please go through the section attached from RFC
> 3332
>    4.3.4.4.1 IPSP Considerations (ASP Inactive)
> 
>    An IPSP may be considered in the ASP-INACTIVE
> state by a remote IPSP
>    after an ASP Inactive or ASP Inactive Ack message
> has been received
>    from it.
> 
>    Alternatively, an interchange of ASP Inactive
> messages from each end
>    can be performed. This option follows the ASP
> state transition
>    diagram and gives the additional advantage of
> selecting a particular
>    AS to be deactivated from each end. It is
> especially useful when an
>    IPSP is serving more than one AS. It would need
> four messages for
>    completion.
> 
>    IMO IPSP A in your example after sending ASPIA
> message for AS1 would
>    not be able to send or receive traffic from or
> for AS1.
> 
> Regards
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
> 
> 
> 
> 
> 
> 
> 
> 
> "Vivek Toky" <vivektoky@ccpu.com>@ietf.org on
> 08/07/2003 10:00:09 AM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    Kamesh Kaul/HSS@HSS
> cc:    <sigtran@ietf.org>
> 
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> 
> Kamesh,
> 
>   See my comments Inline..
> 
> -----Original Message-----
> From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
> Sent: Wednesday, August 06, 2003 8:47 PM
> To: vivektoky@ccpu.com
> Cc: sigtran@ietf.org
> Subject: [Spam] RE: [Sigtran] M3UA : IPSP DE
> behaviour
> 
> 
> 
> 
> 
> 
> 
> Vivek
>       Please see comments in line
> 
> 
> 
> "Vivek Toky" <vivektoky@ccpu.com>@ietf.org on
> 08/05/2003 09:47:43 AM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    "kamesh kaul" <kkk_kaul@yahoo.com>
> cc:    <sigtran@ietf.org>
> 
> Subject:    RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> Kamesh,
>   Please see comments inline
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> kamesh kaul
> Sent: Saturday, August 02, 2003 8:24 PM
> To: Vivek Toky
> Cc: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> Hi Vivek,
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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



From exim@www1.ietf.org  Mon Aug 11 17:01:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06232
	for <sigtran-archive@odin.ietf.org>; Mon, 11 Aug 2003 17:01:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmr-0004Pe-83
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BL15f9016945
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmp-0004OJ-Hf; Mon, 11 Aug 2003 17:01:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19hqDy-0007WN-Pq
	for sigtran@optimus.ietf.org; Wed, 30 Jul 2003 08:38:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28609
	for <sigtran@ietf.org>; Wed, 30 Jul 2003 08:38:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19hqDx-0007M6-00
	for sigtran@ietf.org; Wed, 30 Jul 2003 08:38:33 -0400
Received: from gremg1.net.external.hp.com ([192.6.111.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19hqDw-0007M3-00
	for sigtran@ietf.org; Wed, 30 Jul 2003 08:38:32 -0400
Received: from garonne.grenoble.hp.com (garonne.grenoble.hp.com [15.128.14.138])
	by gremg1.net.external.hp.com (Postfix) with ESMTP id DFB3F3D3
	for <sigtran@ietf.org>; Wed, 30 Jul 2003 14:38:30 +0200 (METDST)
Received: by garonne.grenoble.hp.com with Internet Mail Service (5.5.2655.55)
	id <P7RADF0F>; Wed, 30 Jul 2003 14:38:30 +0200
Message-ID: <D00C96E68738D511941F0090276D8F0B07FECF11@prevert.grenoble.hp.com>
From: "BAND,RICHARD (HP-France,ex1)" <richard.band@hp.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: FW: [Sigtran] M3UA : IPSP DE behaviour
Date: Wed, 30 Jul 2003 14:37:48 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Resending...
Hi Kamesh, Umesh,

I agree that the protocol allows traffic from IPSP B to A without having
traffic from IPSP A to B.

However, I do think that there is a problem with the notifications for the
AS on each side:
In this situation, how should the IPSPs A and B indicate the availability of
the remote AS to the local AS?
Should IPSP A indicate that AS 2 is available, even though it knows AS 2
cannot reply?
Should IPSP B indicate that AS 1 in unavailable, as AS 2 cannot send any
messages to AS 1? 
If so, what should IPSP B do when AS 1 sends traffic? Discard the messages,
or transfer the data to AS 2, which will then receive traffic from an
unavailable destination?

In my opinion, both IPSPs should indicate that the remote AS is unavailable.
I would say that the DE IPSP exchange mode allows each side to indicate its
readiness to receive traffic, but traffic should not be started unless both
sides are active.
It seems to me that this is the only to avoid the problems described above.

Please let me know your opinion on this point.

Regards,

Richard Band

-----Original Message-----
From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
Sent: Wednesday, July 30, 2003 06:17
To: umesh@ccpu.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : IPSP DE behaviour




Umesh

  IPSP B can send DATA messages for AS1 to IPSP A only if on receiving
ASPAC message from IPSP A , IPSP B sends ASPAC ack for AS1 to IPSP A.Not
activating AS2 means IPSP B will not be able to receive any message for
AS2.So in a way only data for AS1 will flow from IPSP B to IPSP A.

Regards
Kamesh Kaul
www.hssworld.com
Hughes Software Systems




"Umesh Vats" <umesh@ccpu.com>@ietf.org on 07/30/2003 07:44:36 AM

Please respond to <umesh@ccpu.com>

Sent by:    sigtran-admin@ietf.org


To:    <sigtran@ietf.org>
cc:

Subject:    [Sigtran] M3UA : IPSP DE behaviour


Suppose we have two Double Ended IPSPs A and B. AS1 is application server
on IPSP-A and AS2 is application server on IPSP-B

     AS1 A----------B AS2

Now, IPSP-A sends ASPAC for for AS1 to B. IPSP-B doesn't activate AS2.
After this, can IPSP-B send DATA messages for AS1 to IPSP-A in any scenario
?

Thanks
Umesh Vats
Sr Software Engg.
extn : 8986


_______________________________________________
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



From exim@www1.ietf.org  Mon Aug 11 17:01:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06234
	for <sigtran-archive@odin.ietf.org>; Mon, 11 Aug 2003 17:01:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmr-0004Pl-8o
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BL15F7016946
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmo-0004O7-Pr; Mon, 11 Aug 2003 17:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19hpgW-0006BK-7Q
	for sigtran@optimus.ietf.org; Wed, 30 Jul 2003 08:04:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27711
	for <sigtran@ietf.org>; Wed, 30 Jul 2003 08:03:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19hpgV-00075g-00
	for sigtran@ietf.org; Wed, 30 Jul 2003 08:03:59 -0400
Received: from bramg1.net.external.hp.com ([192.6.126.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19hpgU-00075d-00
	for sigtran@ietf.org; Wed, 30 Jul 2003 08:03:58 -0400
Received: from loire.grenoble.hp.com (loire.grenoble.hp.com [15.128.14.199])
	by bramg1.net.external.hp.com (Postfix) with ESMTP
	id 8A1E1AE7; Wed, 30 Jul 2003 14:03:56 +0200 (METDST)
Received: by loire.grenoble.hp.com with Internet Mail Service (5.5.2655.55)
	id <P7Q7QLBC>; Wed, 30 Jul 2003 14:03:55 +0200
Message-ID: <D00C96E68738D511941F0090276D8F0B07FECF0F@prevert.grenoble.hp.com>
From: "BAND,RICHARD (HP-France,ex1)" <richard.band@hp.com>
To: "'kakaul@hss.hns.com'" <kakaul@hss.hns.com>, umesh@ccpu.com
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : IPSP DE behaviour
Date: Wed, 30 Jul 2003 14:03:53 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Hi Kamesh, Umesh,

I agree that the protocol allows traffic from IPSP B to A without having
traffic from IPSP A to B.

However, I do think that there is a problem with the notifications for the
AS on each side:
In this situation, how should the IPSPs A and B indicate the availability of
the remote AS to the local AS?
Should IPSP A indicate that AS 2 is available, even though it knows AS 2
cannot reply?
Should IPSP B indicate that AS 1 in unavailable, as AS 2 cannot send any
messages to AS 1?  
If so, what should IPSP B do when AS 1 sends traffic? Discard the messages,
or transfer the data to AS 2, which will then receive traffic from an
unavailable destination?

In my opinion, both IPSPs should indicate that the remote AS is unavailable.
I would say that the DE IPSP exchange mode allows each side to indicate its
readiness to receive traffic, but traffic should not be started unless both
sides are active.
It seems to me that this is the only to avoid the problems described above.

Please let me know your opinion on this point.

Regards,

Richard Band

-----Original Message-----
From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
Sent: Wednesday, July 30, 2003 06:17
To: umesh@ccpu.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : IPSP DE behaviour




Umesh

  IPSP B can send DATA messages for AS1 to IPSP A only if on receiving
ASPAC message from IPSP A , IPSP B sends ASPAC ack for AS1 to IPSP A.Not
activating AS2 means IPSP B will not be able to receive any message for
AS2.So in a way only data for AS1 will flow from IPSP B to IPSP A.

Regards
Kamesh Kaul
www.hssworld.com
Hughes Software Systems




"Umesh Vats" <umesh@ccpu.com>@ietf.org on 07/30/2003 07:44:36 AM

Please respond to <umesh@ccpu.com>

Sent by:    sigtran-admin@ietf.org


To:    <sigtran@ietf.org>
cc:

Subject:    [Sigtran] M3UA : IPSP DE behaviour


Suppose we have two Double Ended IPSPs A and B. AS1 is application server
on IPSP-A and AS2 is application server on IPSP-B

     AS1 A----------B AS2

Now, IPSP-A sends ASPAC for for AS1 to B. IPSP-B doesn't activate AS2.
After this, can IPSP-B send DATA messages for AS1 to IPSP-A in any scenario
?

Thanks
Umesh Vats
Sr Software Engg.
extn : 8986


_______________________________________________
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



From exim@www1.ietf.org  Mon Aug 11 17:01:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06248
	for <sigtran-archive@odin.ietf.org>; Mon, 11 Aug 2003 17:01:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmr-0004Q0-DU
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BL15Uq016951
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmq-0004Oe-25; Mon, 11 Aug 2003 17:01:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19igOn-00040G-WD
	for sigtran@optimus.ietf.org; Fri, 01 Aug 2003 16:21:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10768
	for <sigtran@ietf.org>; Fri, 1 Aug 2003 16:21:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19igOm-0006Yc-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 16:21:12 -0400
Received: from ottgw.pt.com ([206.191.2.130] helo=pt.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19igOl-0006YY-00
	for sigtran@ietf.org; Fri, 01 Aug 2003 16:21:11 -0400
Received: from pt.com (IDENT:root@localhost [127.0.0.1])
	by  pt.com (8.9.3/8.9.3) with ESMTP id QAA17572;
	Fri, 1 Aug 2003 16:20:22 -0400
Message-ID: <3F2ACB8B.7090806@pt.com>
Date: Fri, 01 Aug 2003 16:20:27 -0400
From: Andrew Booth <andrew@pt.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bidulock@openss7.org
CC: Tom George <Tom.George@alcatel.com>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M2PA Last Call Comment - RPO
References: <3F15C7F2.6070704@pt.com> <20030716191143.F6725@openss7.org> <3F18328D.1080706@pt.com> <20030718120053.C14760@openss7.org> <3F184959.2040103@pt.com> <20030718133957.A16698@openss7.org> <3F1867CB.6060108@pt.com> <20030724134845.D11627@openss7.org> <3F26BAA2.1080908@pt.com> <3F29983B.2040505@alcatel.com> <20030731165031.A6734@openss7.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi Brian,

It looks like your proposal will only handle the case where the M2PA in 
LPO is able to pass all messages in its TB to the remote M2PA and that 
the remote M2PA is able to deliver these to MTP3.  If the remote M2PA 
implementation is not able to deliver Data to MTP3 while in RPO then 
your proposal as is does not work.  Am I correct so far?

There are several reasons why an M2PA in RPO might not be able to pass 
messages to its MTP3
- it might not be allowed by its interface to MTP3 to pass data after RPO
- it might need to stop delivering messages to MTP3 to make changeovers 
work correctly e.g. after receiving a BSNT request
In either of these cases the M2PA in RPO may need to queue messages 
until RPO is finished.  I don't think that your proposal addresses the 
case where the side in LPO is unable to empty its TB/RTB because the 
other end was forced to queue.

Consider the following difference between MTP2 and M2PA:  When MTP2 is 
in RPO it cannot receive more data until the RPO condition abates (since 
the remote MTP2 is sending only SIPO during this period).  This means in 
particular that the BSNT does not change while MTP2 is in Processor 
Outage.  I believe that several procedures/SDLs depend on this 
assumption (it mostly affects changeover).

In M2PA on the other hand LS PO/LS PR and Data are sent on different 
streams so there are a variety of cases in which Data can be received 
during RPO.  In past revisions of M2PA we handled this by queueing the 
messages in a receive buffer and not delivering them to MTP3, so again 
the BSNT does not change during RPO.

I have an alternative proposal that I think allows for the 
implementation you suggested, but does not require it.  I think the 
extra changes you propose (e.g. passing messages to MTP3 during RPO and 
acking them) can be left within the scope of an implementation.

-------------------------------
Proposal:
Overview:
The implementation of the interface between MTP3 and M2PA will have an 
impact on how an implementation can reasonably deal with changeover 
during RPO.  Leave the existing proposal largely as it is.  Make the 
minimal changes needed to allow an M2PA to continue to send to MTP3 
while in RPO, but leave it to implementations to handle the details of 
interacting with changeover.

Add to 4.1.4:
The side in LPO MAY send data in its TB to the remote M2PA and SHOULD 
continue to process Data Acknowledgment messages received from the peer.

Modify in 4.1.4 the description of the side in RPO:

Change
=====================================
While there is a remote processor outage condition:

   (a) Any User Data messages received from the peer after the Link
       Status Processor Outage MUST NOT be acknowledged and MUST be
       buffered.

   (b) M2PA SHOULD continue to acknowledge User Data messages received
       and accepted by MTP3 before the remote processor outage.
======================================
To
======================================

 Some implementations may continue to deliver messages to MTP3 during 
RPO.  This is considered an implementation dependent option.  Such an 
implementation must continue to handle MTP3 changeover procedures 
correctly during various processor outage states, the details of which 
is out of the scope of M2PA.  With these comments in mind,
while there is a remote processor outage condition:

   (a) Any User Data messages received from the peer after the Link
       Status Processor Outage SHOULD NOT be acknowledged, SHOULD be
       buffered and MUST NOT be discarded.

   (b) M2PA SHOULD continue to acknowledge User Data messages received
       and accepted by MTP3, regardless of the processor outage 
condition.  This
       applies in particular to messages received and processed before 
the remote
       processor outage.
=======================================

Also, I like Brian's comment about high speed links, although I'm 
personally not overly familiar with High speed links.

As Q.2140 handles processor outage by putting the link out of service, also add:

  When M2PA experiences a local processor outage, it MAY put the link out
  of service by sending a Link Status Out of Service message if allowed by
  the applicable MTP2 standard (e.g, [Q.2140]).

----------------------------------

Thoughts?
Andrew

Brian F. G. Bidulock wrote:

>Tom,
>
>See the original note on this thread for suggested changes.
>
>--brian
>
>Tom George wrote:                                                                      (Thu, 31 Jul 2003 17:29:15)
>  
>
>>Brian, Andrew, et. al.,
>>
>>So where do we stand on this issue? If it is true that some MTP3 
>>implementations would accept incoming messages during RPO and some would 
>>not, then we should probably cover both cases.
>>
>>tomG.
>>
>>    
>>
>  
>


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



From exim@www1.ietf.org  Mon Aug 11 17:01:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06251
	for <sigtran-archive@odin.ietf.org>; Mon, 11 Aug 2003 17:01:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJms-0004RY-1j
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BL16tf017073
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmr-0004RH-U0; Mon, 11 Aug 2003 17:01:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l2N6-0007lH-7k
	for sigtran@optimus.ietf.org; Fri, 08 Aug 2003 04:13:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03169
	for <sigtran@ietf.org>; Fri, 8 Aug 2003 04:13:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2N3-0006fP-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:13:09 -0400
Received: from zdemail04.zdem.compaq.com ([161.114.112.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l2N2-0006fA-00
	for sigtran@ietf.org; Fri, 08 Aug 2003 04:13:08 -0400
Received: from demexg11.emea.cpqcorp.net (demexg11.emea.cpqcorp.net [16.41.86.63])
	by zdemail04.zdem.compaq.com (Postfix) with ESMTP
	id 160A3CA7; Fri,  8 Aug 2003 10:12:29 +0200 (CEST)
Received: from vbeexc02.emea.cpqcorp.net ([16.188.146.229]) by demexg11.emea.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.6673);
	 Fri, 8 Aug 2003 10:12:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sigtran] SUA - RC in CLDT
Date: Fri, 8 Aug 2003 10:12:27 +0200
Message-ID: <BE462396B4A022449E0EB2DD4753D054342EDA@vbeexc02.emea.cpqcorp.net>
Thread-Topic: [Sigtran] SUA - RC in CLDT
Thread-Index: AcNde7Gtu7PDM3HpSHSQ5lIEe++xGAABx9Qg
From: "Anzile, Christophe" <christophe.anzile@hp.com>
To: <bidulock@openss7.org>,
        "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "Valerie Gastaud" <valerie.gastaud@ulticom.com>,
        "Sigtran" <sigtran@ietf.org>
X-OriginalArrivalTime: 08 Aug 2003 08:12:28.0979 (UTC) FILETIME=[CF32E030:01C35D84]
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Brian,

are we supposed to look at M3UA IG when implementing SUA ?
if yes, it would be nice to rename it.
if no, it would be nice if John could clarify the SUA draft especially =
the 4.3.4.3 section
and use "conditional" instead of "optional" when it applies.


-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Friday, August 08, 2003 9:07 AM
To: Samuel Dur D. Jeyaseelan
Cc: Anzile, Christophe; Valerie Gastaud; Sigtran
Subject: Re: [Sigtran] SUA - RC in CLDT


Samuel,

The M3UA IG section 3.5 changes "optional" to "conditional" everywhere
for RC to indicate this explicitly.

--brian

Samuel Dur D. Jeyaseelan wrote:                                          =
           (Fri, 08 Aug 2003 01:58:42)
>=20
> Everybody,
>=20
> RC is a mandatory field when an ASP serves more than one AS.
> A single ASP ACTIVE message without RC can not be used to active=20
> multiple ASes across a common SCTP association.RFC does not =
explicitely
> say that RC is mandatory when an ASP serves
> multiple ASes across a common association.But it is implied.
>=20
> RFC has given a flexibility that RC is an optional field when it =
serves
> a single AS.
>=20
> Say an example, an ASP1 serves multiple ASes and has been connected to =

> SGP1.If RC is an optional parameter to activate all ASes, the =
potential
> problem is, while sending DATA messages to ASP1,=20
>=20
> 1) How does ASP1 relate the DATA message with an appropriate AS?
>=20
> 2) Suppose AS2 goes down, How does AS2 indicate this to SGP1?(remeber=20
>    RC has not been communicated between SGP1 and AS2)
>=20
> 3) Suppose SGP1 wants to put AS1 in DOWN state for some kind of
>    configuration purpose, How does SGP1 communicate this with AS1 =
without=20
>    RC?
>=20
> RFC implicitely says that RC is a mandatory field when an ASP serves
> more than one ASes.
>=20
> --Samuel
>=20
>   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. =
*******
>=20
> On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
>=20
> > Anzile,,
> >=20
> > Anzile, Christophe wrote:                                            =
              (Thu, 07 Aug 2003 11:24:09)
> > > Brian (& Valerie),
> > >=20
> > > Please do not make RC mandatory in ASPAC, or you'll have strong =
side effects on the draft..
> > > This is not consistent at all with what's written in the draft =
page 92, ie
> > >  [ it is not necessary for the ASP to=20
> > >    include all Routing Contexts of interest in a single ASP Active =

> > >    message, thus requesting to become active in all Routing =
Contexts at=20
> > >    the same time.  Multiple ASP Active messages MAY be used to =
activate=20
> > >    within the Application Servers independently, or in sets.  In =
the=20
> > >    case where an ASP Active message does not contain a Routing =
Context=20
> > >    parameter, the receiver must know, via configuration data, =
which=20
> > >    Application Server(s) the ASP is a member. ]
> > >=20
> > > -> This is clear that if no RC is present in the ASPAC, it should =
be considered as a wildcard
> > > for all AS statically configured in the SG..=20
> >=20
> > No, that is not what it means.  If RC is not included, only a single =
AS can
> > exist for the SCTP association.
> >=20
> >=20
> > > In return, SG should send back all RCs activated in the ASPAC-ACK =
msg.
> >=20
> > No.  If there is no RC in ASPAC there may be no RC in ASPAC Ack.
> >=20
> > >=20
> > > -> This is why RC is therefore mandatory in CLDT/CLDR.
> >=20
> > Don't think so...
> >=20
> > --brian
> >=20
> > >=20
> > >=20
> > > Christophe.
> > >=20
> > >=20
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: Thursday, August 07, 2003 9:18 AM
> > > To: Valerie Gastaud
> > > Cc: Sigtran
> > > Subject: Re: [Sigtran] SUA - RC in CLDT
> > >=20
> > >=20
> > > Valerie,
> > >=20
> > > SUA had RC mandatory in all messages.  This was just a cut and =
paste error
> > > from "common UA procedures".  The SUA draft should be corrected to =
make RC
> > > mandatory in ASPAC.  Although it may make some sense to M2UA and =
even M3UA
> > > to have RC optional in ASPAC, it makes little sense in SUA.  This =
is why
> > > RC is mandatory in all messages in SUA.
> > >=20
> > > --brian
> > >=20
> > > Valerie Gastaud wrote:                                             =
                (Wed, 06 Aug 2003 15:33:59)
> > > >=20
> > > > Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2 =
messages)?
> > > > This is not consistent with M3UA and this is not consistent with =
the SUA
> > > > ASPAC message in which the RC is optional.
> > > > In case of static provisioning of RK, if an SGP receives an =
ASPAC w/o RC, it
> > > > won't be able to insert the RC in the CLDT.
> > > >=20
> > > > Valerie
> > > >=20
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >=20
> > > --=20
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >=20
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Mon Aug 11 17:01:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06311
	for <sigtran-archive@odin.ietf.org>; Mon, 11 Aug 2003 17:01:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmr-0004Pj-8W
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BL15oN016947
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmq-0004Os-HH; Mon, 11 Aug 2003 17:01:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k3Kx-0002wy-H0
	for sigtran@optimus.ietf.org; Tue, 05 Aug 2003 11:02:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15330
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 11:02:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k3Kt-0002x4-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 11:02:51 -0400
Received: from mails.conexion.com.py ([65.198.40.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k3Kr-0002v8-00
	for sigtran@ietf.org; Tue, 05 Aug 2003 11:02:49 -0400
Received: from miguelpc (mf.conexion.com.py [65.198.40.11])
	by mails.conexion.com.py (8.12.8/8.12.8) with SMTP id h75F8tkT012897
	for <sigtran@ietf.org>; Tue, 5 Aug 2003 11:09:01 -0400
Message-ID: <004f01c35b30$3f2cbc00$6700a8c0@miguelpc>
From: "Miguel Willigs" <miguel.willigs@conexiongroup.com>
To: <sigtran@ietf.org>
Date: Tue, 5 Aug 2003 11:02:01 +0200
Organization: Conexion
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_004C_01C35B40.FF436FB0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
Subject: [Sigtran] doubt about sctp associations
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_004C_01C35B40.FF436FB0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi there,
         I am having a doubt about sctp associations when used in the =
M2UA Layer.

It says in RFC 3331, page 9, "The M2UA layer MUST maintain a map of an =
Interface ID to a physical interface on the Signalling Gateway.  A =
physical interface would be a V.35 line, T1 line/time slot, E1 line/time =
slot, etc.  The M2UA layer MUST also maintain a map of the Interface =
Identifier to SCTP association and to the related stream within the =
association."

So, does it mean that (always) a sctp association consists in 2 sctp =
endpoints (IP:Port address) and also the stream they use to communicate?

          thanks,
                  Miguel

------=_NextPart_000_004C_01C35B40.FF436FB0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi=20
there,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I am having a =
doubt=20
about sctp associations when used in the M2UA Layer.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>It says in RFC 3331, page 9, "The M2UA =
layer MUST=20
maintain a map of an Interface ID to a physical interface on the =
Signalling=20
Gateway.&nbsp; A physical interface would be a V.35 line, T1 line/time =
slot, E1=20
line/time slot, etc.&nbsp; The M2UA layer MUST also maintain a map of =
the=20
Interface Identifier to SCTP association and to the related stream =
within the=20
association."</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>So, does it mean that (always) a sctp =
association=20
consists in 2 sctp endpoints (IP:Port address) and also the stream they =
use to=20
communicate?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
thanks,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Miguel</FONT></DIV></BODY></HTML>

------=_NextPart_000_004C_01C35B40.FF436FB0--


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



From exim@www1.ietf.org  Mon Aug 11 17:25:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07055
	for <sigtran-archive@odin.ietf.org>; Mon, 11 Aug 2003 17:25:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mKA2-0005gf-GO
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:25:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BLP2I7021855
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:25:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mKA1-0005gB-NS; Mon, 11 Aug 2003 17:25:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mK9x-0005ff-R9
	for sigtran@optimus.ietf.org; Mon, 11 Aug 2003 17:24:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07022
	for <sigtran@ietf.org>; Mon, 11 Aug 2003 17:24:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mK9v-0002YK-00
	for sigtran@ietf.org; Mon, 11 Aug 2003 17:24:55 -0400
Received: from web12803.mail.yahoo.com ([216.136.174.38])
	by ietf-mx with smtp (Exim 4.12)
	id 19mK9u-0002YH-00
	for sigtran@ietf.org; Mon, 11 Aug 2003 17:24:54 -0400
Message-ID: <20030811212451.44507.qmail@web12803.mail.yahoo.com>
Received: from [208.255.120.2] by web12803.mail.yahoo.com via HTTP; Mon, 11 Aug 2003 14:24:51 PDT
Date: Mon, 11 Aug 2003 14:24:51 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: FW: [Sigtran] M3UA : IPSP DE behaviour
To: sigtran@ietf.org
In-Reply-To: <D00C96E68738D511941F0090276D8F0B07FECF11@prevert.grenoble.hp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Richard,

M3UA does not dictate, which MTP3/MTP3 User part
primitive should be sent to an application when -this
is dependent on architecture and implementation-. So,
IMO from M3UA protocol point of view, there is no way
to introduce the intelligence you are describing below
with DE-IPSP mode, but this might be done in NIF. And
also, an application does not get indication about
remote AS availability but primitives like in plain
MTP3 about remote PC status.
In fact, it seems to me that such a harmonization of
remote/local AS states might make DE mode quite
similar to SE mode from application point of view,
where the intelligence is shifted from M3UA to NIF
-and this may beg the question why DE mode is
introduced-.

     Tolga
--- "BAND,RICHARD (HP-France,ex1)"
<richard.band@hp.com> wrote:
> Resending...
> Hi Kamesh, Umesh,
> 
> I agree that the protocol allows traffic from IPSP B
> to A without having
> traffic from IPSP A to B.
> 
> However, I do think that there is a problem with the
> notifications for the
> AS on each side:
> In this situation, how should the IPSPs A and B
> indicate the availability of
> the remote AS to the local AS?
> Should IPSP A indicate that AS 2 is available, even
> though it knows AS 2
> cannot reply?
> Should IPSP B indicate that AS 1 in unavailable, as
> AS 2 cannot send any
> messages to AS 1? 
> If so, what should IPSP B do when AS 1 sends
> traffic? Discard the messages,
> or transfer the data to AS 2, which will then
> receive traffic from an
> unavailable destination?
> 
> In my opinion, both IPSPs should indicate that the
> remote AS is unavailable.
> I would say that the DE IPSP exchange mode allows
> each side to indicate its
> readiness to receive traffic, but traffic should not
> be started unless both
> sides are active.
> It seems to me that this is the only to avoid the
> problems described above.
> 
> Please let me know your opinion on this point.
> 
> Regards,
> 
> Richard Band
> 
> -----Original Message-----
> From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
> Sent: Wednesday, July 30, 2003 06:17
> To: umesh@ccpu.com
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> 
> 
> Umesh
> 
>   IPSP B can send DATA messages for AS1 to IPSP A
> only if on receiving
> ASPAC message from IPSP A , IPSP B sends ASPAC ack
> for AS1 to IPSP A.Not
> activating AS2 means IPSP B will not be able to
> receive any message for
> AS2.So in a way only data for AS1 will flow from
> IPSP B to IPSP A.
> 
> Regards
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
> 
> 
> 
> 
> "Umesh Vats" <umesh@ccpu.com>@ietf.org on 07/30/2003
> 07:44:36 AM
> 
> Please respond to <umesh@ccpu.com>
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    <sigtran@ietf.org>
> cc:
> 
> Subject:    [Sigtran] M3UA : IPSP DE behaviour
> 
> 
> Suppose we have two Double Ended IPSPs A and B. AS1
> is application server
> on IPSP-A and AS2 is application server on IPSP-B
> 
>      AS1 A----------B AS2
> 
> Now, IPSP-A sends ASPAC for for AS1 to B. IPSP-B
> doesn't activate AS2.
> After this, can IPSP-B send DATA messages for AS1 to
> IPSP-A in any scenario
> ?
> 
> Thanks
> Umesh Vats
> Sr Software Engg.
> extn : 8986
> 
> 
> _______________________________________________
> 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


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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



From exim@www1.ietf.org  Mon Aug 11 17:47:37 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06252
	for <sigtran-archive@odin.ietf.org>; Mon, 11 Aug 2003 17:01:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmr-0004R0-FY
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BL15qA016984
	for sigtran-archive@odin.ietf.org; Mon, 11 Aug 2003 17:01:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mJmr-0004PI-6S; Mon, 11 Aug 2003 17:01:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kh0m-0004dF-Nu
	for sigtran@optimus.ietf.org; Thu, 07 Aug 2003 05:24:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05431
	for <sigtran@ietf.org>; Thu, 7 Aug 2003 05:24:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kh0j-0004GY-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 05:24:41 -0400
Received: from zdemail03.zdem.compaq.com ([161.114.112.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kh0i-0004GR-00
	for sigtran@ietf.org; Thu, 07 Aug 2003 05:24:40 -0400
Received: from demexg11.emea.cpqcorp.net (demexg11.emea.cpqcorp.net [16.41.86.63])
	by zdemail03.zdem.compaq.com (Postfix) with ESMTP
	id AAD9711F0; Thu,  7 Aug 2003 11:24:10 +0200 (CEST)
Received: from vbeexc02.emea.cpqcorp.net ([16.188.146.229]) by demexg11.emea.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.6673);
	 Thu, 7 Aug 2003 11:24:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sigtran] SUA - RC in CLDT
Date: Thu, 7 Aug 2003 11:24:09 +0200
Message-ID: <BE462396B4A022449E0EB2DD4753D054342ED7@vbeexc02.emea.cpqcorp.net>
Thread-Topic: [Sigtran] SUA - RC in CLDT
Thread-Index: AcNcvpIA92Anf+yeRWqsMiqTXaQv1QABVs3g
From: "Anzile, Christophe" <christophe.anzile@hp.com>
To: <bidulock@openss7.org>, "Valerie Gastaud" <valerie.gastaud@ulticom.com>
Cc: "Sigtran" <sigtran@ietf.org>
X-OriginalArrivalTime: 07 Aug 2003 09:24:10.0442 (UTC) FILETIME=[A8A84AA0:01C35CC5]
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Brian (& Valerie),

Please do not make RC mandatory in ASPAC, or you'll have strong side =
effects on the draft..
This is not consistent at all with what's written in the draft page 92, =
ie
 [ it is not necessary for the ASP to=20
   include all Routing Contexts of interest in a single ASP Active=20
   message, thus requesting to become active in all Routing Contexts at=20
   the same time.  Multiple ASP Active messages MAY be used to activate=20
   within the Application Servers independently, or in sets.  In the=20
   case where an ASP Active message does not contain a Routing Context=20
   parameter, the receiver must know, via configuration data, which=20
   Application Server(s) the ASP is a member. ]

-> This is clear that if no RC is present in the ASPAC, it should be =
considered as a wildcard
for all AS statically configured in the SG..=20
In return, SG should send back all RCs activated in the ASPAC-ACK msg.

-> This is why RC is therefore mandatory in CLDT/CLDR.


Christophe.


-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Thursday, August 07, 2003 9:18 AM
To: Valerie Gastaud
Cc: Sigtran
Subject: Re: [Sigtran] SUA - RC in CLDT


Valerie,

SUA had RC mandatory in all messages.  This was just a cut and paste =
error
from "common UA procedures".  The SUA draft should be corrected to make =
RC
mandatory in ASPAC.  Although it may make some sense to M2UA and even =
M3UA
to have RC optional in ASPAC, it makes little sense in SUA.  This is why
RC is mandatory in all messages in SUA.

--brian

Valerie Gastaud wrote:                                                   =
          (Wed, 06 Aug 2003 15:33:59)
>=20
> Why is RC mandatory in the SUA data messages (CLDT/CLDR + class2 =
messages)?
> This is not consistent with M3UA and this is not consistent with the =
SUA
> ASPAC message in which the RC is optional.
> In case of static provisioning of RK, if an SGP receives an ASPAC w/o =
RC, it
> won't be able to insert the RC in the CLDT.
>=20
> Valerie
>=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

_______________________________________________
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



From exim@www1.ietf.org  Tue Aug 12 22:40:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07394
	for <sigtran-archive@odin.ietf.org>; Tue, 12 Aug 2003 22:40:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mlYU-0007Ff-9t
	for sigtran-archive@odin.ietf.org; Tue, 12 Aug 2003 22:40:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7D2e6ur027872
	for sigtran-archive@odin.ietf.org; Tue, 12 Aug 2003 22:40:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mlYP-0007FD-Lu; Tue, 12 Aug 2003 22:40:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mlXk-0007EY-Qn
	for sigtran@optimus.ietf.org; Tue, 12 Aug 2003 22:39:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07373
	for <sigtran@ietf.org>; Tue, 12 Aug 2003 22:39:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mlXh-0005TZ-00
	for sigtran@ietf.org; Tue, 12 Aug 2003 22:39:17 -0400
Received: from relay5.tp1rc.edu.tw ([163.28.16.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mlXf-0005TS-00
	for sigtran@ietf.org; Tue, 12 Aug 2003 22:39:15 -0400
Received: from KHL (61-219-40-1.HINET-IP.hinet.net [61.219.40.1])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by relay5.tp1rc.edu.tw (Postfix) with ESMTP
	id 68077106E34; Wed, 13 Aug 2003 10:38:58 +0800 (CST)
Message-ID: <001901c36145$2b17bec0$6ec5900a@saoe.com>
From: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        <bidulock@openss7.org>
Cc: "sigtran" <sigtran@ietf.org>
References: <Pine.SOL.4.10.10308080450510.6428-100000@sun2685.ssd.usa.alcatel.com>
Subject: Re: [Sigtran] question about m3UA
Date: Wed, 13 Aug 2003 08:55:25 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Hi, Brian and Samuel

The answer for both of you is different.
See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not sent ASP Ac=
t.
to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional or
mandatory?

Thanks

Ling-Chih Kao



----- Original Message -----
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran" <sigtran@ietf.org>
Sent: Friday, August 08, 2003 6:08 PM
Subject: Re: [Sigtran] question about m3UA



Brian,
 Huh, it is not an implementation dependent, rfc says
 ASPs which are in that AS should coordinate among themselves the number
 of active ASPs in the AS.So it is clear to SGP that first arrived
 'n' ASPs will receive NTFY(AS-INACT) message.

 If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN state)
 you are not restricted but it is not mandatory to send, thats what i
 am saying from the beginning.

 Keep IG as it is.
--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.c=
om
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *****=
**

On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:

> Samuel,
>
> Maybe clear to the ASPs depending on implementation, but not
> clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> used by any of the ASPs, why send it in the first place?
> If it serves a purpose, it should be sent to all of them to avoid
> the race condition.
>
> --brian
>
> Samuel Dur D. Jeyaseelan wrote:
(Fri, 08 Aug 2003 04:36:50)
> >
> > Brian,
> >  We all know that in n+k redundancy case that ASPes will coordinate
> >  among themselves the number of active ASPs in the AS, here it is
> >  clear that who is going to go to ACTIVE state then where is the
> >  question of race condition?
> >
> > --Samuel
> >
> >   Alcatel USA, Inc.                  Internet:
<userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc.
*******
> >
> > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> >
> > > Samuel,
> > >
> > > What if ASP1 and ASP3 receive it but ASP2 did not, just because
> > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > > ASPs when they come up.  It should not be optional.  It is necessar=
y
> > > to proper interworking that this race be broken.
> > >
> > > --brian
> > >
> > > Samuel Dur D. Jeyaseelan wrote:
(Fri, 08 Aug 2003 04:17:31)
> > > >
> > > > Brian,
> > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, but
ASP1 and
> > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT message,
> > > >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1 and
ASP3).
> > > >
> > > >  This is the reason i said it is an optional of sending
NTFY(AS-INACT)
> > > >  to 'n+1'th ASP.
> > > >
> > > > --Samuel
> > > >
> > > >   Alcatel USA, Inc.                  Internet:
<userid>@ssd.usa.alcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, In=
c.
*******
> > > >
> > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > >
> > > > > Samuel,
> > > > >
> > > > > Yes, I have a problem, because it is a race condition.
> > > > >
> > > > > --brian
> > > > >
> > > > > Samuel Dur D. Jeyaseelan wrote:
(Fri, 08 Aug 2003 04:04:50)
> > > > > >
> > > > > > Brian,
> > > > > >
> > > > > >   I meant first 2 ASPes will receive NTFY messages.Sending NT=
FY
to
> > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > >
> > > > > > --Samuel
> > > > > >
> > > > > >   Alcatel USA, Inc.                  Internet:
<userid>@ssd.usa.alcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of Alcatel USA=
,
Inc. *******
> > > > > >
> > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > >
> > > > > > > Samuel,
> > > > > > >
> > > > > > > None of the ASPs are handling traffic at that point.  Who i=
s
to say
> > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perhap=
s
ASP2
> > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely
doesn't know.
> > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest choi=
ce.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > Samuel Dur D. Jeyaseelan wrote:
(Fri, 08 Aug 2003 03:47:30)
> > > > > > > >
> > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > >
> > > > > > > > In n+k reduntancy case,when n=3D2 that means ASP1 and ASP=
2 are
going to
> > > > > > > > handle the traffic.So sending NTFY to these ASPes is
mandatory.
> > > > > > > > Sending NTFY to ASP3 is an optional because it is not goi=
ng
to handle
> > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 will co=
me
up to take
> > > > > > > > over the traffic this case SGP will send a NTFY message w=
ith
AS state,
> > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > >
> > > > > > > > --Samuel
> > > > > > > >
> > > > > > > >   Alcatel USA, Inc.                  Internet:
<userid>@ssd.usa.alcatel.com
> > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > >   ******* The opinions expressed are not those of Alcatel
USA, Inc. *******
> > > > > > > >
> > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > >
> > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > > > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the=
 AS
becomes
> > > > > > > > > AS-INACTIVE when there are at least n ASPs in either
ASP-INACTIVE or
> > > > > > > > > AS-ACTIVE.
> > > > > > > > >
> > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when S=
GP
receives two ASP
> > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP receive=
s
ASP UP from ASP3,
> > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want=
 to
know whether it
> > > > > > > > > is optional or not?
> > > > > > > > >
> > > > > > > > > Thanks.
> > > > > > > > > Ling-Chih Kao
> > > > > > > > >
> > > > > > > > > ----- Original Message -----
> > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
<sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Ling-Chih Kao,
> > > > > > > > >
> > > > > > > > > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > > > > > > > > Note: Available peer means an ASP which received
ASP-UP-ACK
> > > > > > > > > in response to ASP-UP messages.(as per RFC section
4.3.4.1).
> > > > > > > > >
> > > > > > > > > If you active the AS as soon as a single ASP goes to
ASP-INACT
> > > > > > > > > state then it is obvious that whoever sends ASP-UP mess=
age
to
> > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to the
concern
> > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --Samuel
> > > > > > > > >   Alcatel USA, Inc.                  Internet:
<userid>@ssd.usa.alcatel.com
> > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > >   ******* The opinions expressed are not those of Alcat=
el
USA, Inc. *******
> > > > > > > > >
> > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > >
> > > > > > > > > > Hi all,
> > > > > > > > > >
> > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP should
immediately send
> > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is t=
his
right?
> > > > > > > > > >
> > > > > > > > > > Thanks
> > > > > > > > > >
> > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > ----- Original Message -----
> > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
<sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
<d86942004@ntu.edu.tw>;
> > > > > > > > > "sigtran"
> > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Brian,
> > > > > > > > > >
> > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > >
> > > > > > > > > > > kakaul,
> > > > > > > > > > >
> > > > > > > > > > > But I think that we agreed that it would be wise to
tell newly inactive
> > > > > > > > >
  ------------------
> > > > > > > > > > > ASPs that state of the AS.  Also, in the diagram, t=
he
state of the AS
> > > > > > > > > >   -------------------------
> > > > > > > > > >
> > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY will =
be
sent to all ASPes
> > > > > > > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > > > > > > This is what i remember that everybody agreed.
> > > > > > > > > >
> > > > > > > > > > --Samuel
> > > > > > > > > > > does not change with the second ASP (ASP2) sending
ASPUP.  The AS
> > > > > > > > > changes
> > > > > > > > > > > state to AS-INACTIVE with ASP1 coming up.  Therefor=
e,
the diagram should
> > > > > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP
immediately after the
> > > > > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > > > > >
> > > > > > > > > > > The diagram is quite wrong.  Also it is wrong
considering the changes to
> > > > > > > > > > > be made to the next issue of the IG.
> > > > > > > > > > >
> > > > > > > > > > > --brian
> > > > > > > > > > >
> > > > > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On receiving ASPUP message from ASP3 state of AS
does not change, so
> > > > > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > > > > >
> > > > > > > > > > > > Kamesh
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org o=
n
08/04/2003 11:40:01
> > > > > > > > > > AM
> > > > > > > > > > > >
> > > > > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > cc:
> > > > > > > > > > > >
> > > > > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.tx=
t>
receive
> > > > > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > >
> > > > > > > > > > > > Thanls
> > > > > > > > > > > >
> > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > > > bidulock@openss7.org
> > > > > > > > > > > http://www.openss7.org/
> > > > > > > > > > >
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > 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
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > 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
> > > > > > >
> > > > > > > --
> > > > > > > Brian F. G. Bidulock
> > > > > > > bidulock@openss7.org
> > > > > > > http://www.openss7.org/
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > >
> > > > > --
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >
> > > > >
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > >
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>
> _______________________________________________
> 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



From exim@www1.ietf.org  Tue Aug 12 23:04:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08213
	for <sigtran-archive@odin.ietf.org>; Tue, 12 Aug 2003 23:04:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mlve-00086a-Rl
	for sigtran-archive@odin.ietf.org; Tue, 12 Aug 2003 23:04:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7D342Ut031154
	for sigtran-archive@odin.ietf.org; Tue, 12 Aug 2003 23:04:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mlvd-00086H-Pu; Tue, 12 Aug 2003 23:04:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mlvV-00085w-2n
	for sigtran@optimus.ietf.org; Tue, 12 Aug 2003 23:03:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08171
	for <sigtran@ietf.org>; Tue, 12 Aug 2003 23:03:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mlvR-0005ee-00
	for sigtran@ietf.org; Tue, 12 Aug 2003 23:03:49 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[gXdpIzzoH1hhtgkYXczuGuqso+e1w7WC])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mlvQ-0005eQ-00
	for sigtran@ietf.org; Tue, 12 Aug 2003 23:03:48 -0400
Received: from ns.pigworks.openss7.net (IDENT:hgIzQCKX7tjFXohJYUGZbGHxcQ1vzyic@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h7D33eE25467;
	Tue, 12 Aug 2003 21:03:40 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h7D33eP07719;
	Tue, 12 Aug 2003 21:03:40 -0600
Date: Tue, 12 Aug 2003 21:03:40 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Ling-Chih Kao <d86942004@ntu.edu.tw>
Cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030812210340.A7399@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Ling-Chih Kao <d86942004@ntu.edu.tw>,
	"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran <sigtran@ietf.org>
References: <Pine.SOL.4.10.10308080450510.6428-100000@sun2685.ssd.usa.alcatel.com> <001901c36145$2b17bec0$6ec5900a@saoe.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <001901c36145$2b17bec0$6ec5900a@saoe.com>; from d86942004@ntu.edu.tw on Wed, Aug 13, 2003 at 08:55:25AM +0800
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h7D33eE25467
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Ling-Chih,

Mandatory.  All ASP-INACTIVE ASPs for an AS receive notifications
of state change.  ASP3 is ASP-INACTIVE in this case and must receive
the notification.

The contentious case is when an ASP (ASP3) becomes ASP-INACTIVE from
ASP-DOWN.  I believe that the SGP should notify the newly inactive
ASP of the current state of the AS (which it did not receive before).
Samuel thinks that they should somehow guess the state of the AS.

--brian

Ling-Chih Kao wrote:                                                     =
        (Wed, 13 Aug 2003 08:55:25)
> Hi, Brian and Samuel
>=20
> The answer for both of you is different.
> See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not sent ASP =
Act.
> to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional or
> mandatory?
>=20
> Thanks
>=20
> Ling-Chih Kao
>=20
>=20
>=20
> ----- Original Message -----
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran" <sigtran@ietf.org=
>
> Sent: Friday, August 08, 2003 6:08 PM
> Subject: Re: [Sigtran] question about m3UA
>=20
>=20
>=20
> Brian,
>  Huh, it is not an implementation dependent, rfc says
>  ASPs which are in that AS should coordinate among themselves the numbe=
r
>  of active ASPs in the AS.So it is clear to SGP that first arrived
>  'n' ASPs will receive NTFY(AS-INACT) message.
>=20
>  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN state)
>  you are not restricted but it is not mandatory to send, thats what i
>  am saying from the beginning.
>=20
>  Keep IG as it is.
> --Samuel
>=20
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
>=20
> On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
>=20
> > Samuel,
> >
> > Maybe clear to the ASPs depending on implementation, but not
> > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > used by any of the ASPs, why send it in the first place?
> > If it serves a purpose, it should be sent to all of them to avoid
> > the race condition.
> >
> > --brian
> >
> > Samuel Dur D. Jeyaseelan wrote:
> (Fri, 08 Aug 2003 04:36:50)
> > >
> > > Brian,
> > >  We all know that in n+k redundancy case that ASPes will coordinate
> > >  among themselves the number of active ASPs in the AS, here it is
> > >  clear that who is going to go to ACTIVE state then where is the
> > >  question of race condition?
> > >
> > > --Samuel
> > >
> > >   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> *******
> > >
> > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > >
> > > > Samuel,
> > > >
> > > > What if ASP1 and ASP3 receive it but ASP2 did not, just because
> > > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > > > ASPs when they come up.  It should not be optional.  It is necess=
ary
> > > > to proper interworking that this race be broken.
> > > >
> > > > --brian
> > > >
> > > > Samuel Dur D. Jeyaseelan wrote:
> (Fri, 08 Aug 2003 04:17:31)
> > > > >
> > > > > Brian,
> > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, bu=
t
> ASP1 and
> > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT message=
,
> > > > >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1 a=
nd
> ASP3).
> > > > >
> > > > >  This is the reason i said it is an optional of sending
> NTFY(AS-INACT)
> > > > >  to 'n+1'th ASP.
> > > > >
> > > > > --Samuel
> > > > >
> > > > >   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, =
Inc.
> *******
> > > > >
> > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > >
> > > > > > Samuel,
> > > > > >
> > > > > > Yes, I have a problem, because it is a race condition.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > Samuel Dur D. Jeyaseelan wrote:
> (Fri, 08 Aug 2003 04:04:50)
> > > > > > >
> > > > > > > Brian,
> > > > > > >
> > > > > > >   I meant first 2 ASPes will receive NTFY messages.Sending =
NTFY
> to
> > > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > > >
> > > > > > > --Samuel
> > > > > > >
> > > > > > >   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
> > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > >   ******* The opinions expressed are not those of Alcatel U=
SA,
> Inc. *******
> > > > > > >
> > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > >
> > > > > > > > Samuel,
> > > > > > > >
> > > > > > > > None of the ASPs are handling traffic at that point.  Who=
 is
> to say
> > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perh=
aps
> ASP2
> > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely
> doesn't know.
> > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest ch=
oice.
> > > > > > > >
> > > > > > > > --brian
> > > > > > > >
> > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > >
> > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > >
> > > > > > > > > In n+k reduntancy case,when n=3D2 that means ASP1 and A=
SP2 are
> going to
> > > > > > > > > handle the traffic.So sending NTFY to these ASPes is
> mandatory.
> > > > > > > > > Sending NTFY to ASP3 is an optional because it is not g=
oing
> to handle
> > > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 will =
come
> up to take
> > > > > > > > > over the traffic this case SGP will send a NTFY message=
 with
> AS state,
> > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > >
> > > > > > > > > --Samuel
> > > > > > > > >
> > > > > > > > >   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
> > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > >   ******* The opinions expressed are not those of Alcat=
el
> USA, Inc. *******
> > > > > > > > >
> > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > >
> > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > From the new definition of AS-INACTIVE in sec 4.3.2 o=
f
> > > > > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, t=
he AS
> becomes
> > > > > > > > > > AS-INACTIVE when there are at least n ASPs in either
> ASP-INACTIVE or
> > > > > > > > > > AS-ACTIVE.
> > > > > > > > > >
> > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when=
 SGP
> receives two ASP
> > > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP recei=
ves
> ASP UP from ASP3,
> > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I wa=
nt to
> know whether it
> > > > > > > > > > is optional or not?
> > > > > > > > > >
> > > > > > > > > > Thanks.
> > > > > > > > > > Ling-Chih Kao
> > > > > > > > > >
> > > > > > > > > > ----- Original Message -----
> > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > >
> > > > > > > > > > NTFY(AS-INACT) is sent to all all available peer ASPe=
s.
> > > > > > > > > > Note: Available peer means an ASP which received
> ASP-UP-ACK
> > > > > > > > > > in response to ASP-UP messages.(as per RFC section
> 4.3.4.1).
> > > > > > > > > >
> > > > > > > > > > If you active the AS as soon as a single ASP goes to
> ASP-INACT
> > > > > > > > > > state then it is obvious that whoever sends ASP-UP me=
ssage
> to
> > > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to th=
e
> concern
> > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --Samuel
> > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
> > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > >   ******* The opinions expressed are not those of Alc=
atel
> USA, Inc. *******
> > > > > > > > > >
> > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi all,
> > > > > > > > > > >
> > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP should
> immediately send
> > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is=
 this
> right?
> > > > > > > > > > >
> > > > > > > > > > > Thanks
> > > > > > > > > > >
> > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
> <d86942004@ntu.edu.tw>;
> > > > > > > > > > "sigtran"
> > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Brian,
> > > > > > > > > > >
> > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > >
> > > > > > > > > > > > kakaul,
> > > > > > > > > > > >
> > > > > > > > > > > > But I think that we agreed that it would be wise =
to
> tell newly inactive
> > > > > > > > > >
>   ------------------
> > > > > > > > > > > > ASPs that state of the AS.  Also, in the diagram,=
 the
> state of the AS
> > > > > > > > > > >   -------------------------
> > > > > > > > > > >
> > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY wil=
l be
> sent to all ASPes
> > > > > > > > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > > > > > > > This is what i remember that everybody agreed.
> > > > > > > > > > >
> > > > > > > > > > > --Samuel
> > > > > > > > > > > > does not change with the second ASP (ASP2) sendin=
g
> ASPUP.  The AS
> > > > > > > > > > changes
> > > > > > > > > > > > state to AS-INACTIVE with ASP1 coming up.  Theref=
ore,
> the diagram should
> > > > > > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP
> immediately after the
> > > > > > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > > > > > >
> > > > > > > > > > > > The diagram is quite wrong.  Also it is wrong
> considering the changes to
> > > > > > > > > > > > be made to the next issue of the IG.
> > > > > > > > > > > >
> > > > > > > > > > > > --brian
> > > > > > > > > > > >
> > > > > > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On receiving ASPUP message from ASP3 state of A=
S
> does not change, so
> > > > > > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Kamesh
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org=
 on
> 08/04/2003 11:40:01
> > > > > > > > > > > AM
> > > > > > > > > > > > >
> > > > > > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > cc:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.=
txt>
> receive
> > > > > > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanls
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > > > > bidulock@openss7.org
> > > > > > > > > > > > http://www.openss7.org/
> > > > > > > > > > > >
> > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > 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
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > _______________________________________________
> > > > > > > > > > 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
> > > > > > > >
> > > > > > > > --
> > > > > > > > Brian F. G. Bidulock
> > > > > > > > bidulock@openss7.org
> > > > > > > > http://www.openss7.org/
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Sigtran mailing list
> > > > > > > Sigtran@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > >
> > > > > > --
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > > > >
> > > > > >
> > > >
> > > > --
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >
> > > >
> >
> > --
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >
> >
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Wed Aug 13 00:29:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11385
	for <sigtran-archive@odin.ietf.org>; Wed, 13 Aug 2003 00:29:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnFy-0002tg-Bj
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 00:29:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7D4T646011136
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 00:29:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnFu-0002tJ-1q; Wed, 13 Aug 2003 00:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnFj-0002sz-3W
	for sigtran@optimus.ietf.org; Wed, 13 Aug 2003 00:28:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11361
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 00:28:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mnFg-0006LH-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 00:28:48 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mnFf-0006Ko-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 00:28:47 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h7D4RqwW029675;
	Tue, 12 Aug 2003 23:28:17 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h7D4R41C021102;
	Tue, 12 Aug 2003 23:27:04 -0500 (CDT)
Date: Tue, 12 Aug 2003 23:27:04 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <20030812210340.A7399@openss7.org>
Message-ID: <Pine.SOL.4.10.10308122304030.8235-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: QUOTED-PRINTABLE


Brian,
 If it is mandatory to send NTFY(AS-STATE) to all ASPes(other than down),
 Why dont we send SS7 node availability status(like DUNA,DAVA,DRST...)=20
 to all INACTIVE-ASPes?(because anyway when INACTIVE-ASP moves to ACTIVE
 ASP, it should know the status of SS7 nodes but finally it was decided
 that newly active ASP will send an DAUD and gets the SS7 node(s) status
 or SGP may send SS7 node(s) status to the newly active ASP.)
 This i suggested long back(i think you remeber) but you strongly opposed
 it. Now you are partially true with my old arguments.

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Tue, 12 Aug 2003, Brian F. G. Bidulock wrote:

> Ling-Chih,
>=20
> Mandatory.  All ASP-INACTIVE ASPs for an AS receive notifications
> of state change.  ASP3 is ASP-INACTIVE in this case and must receive
> the notification.
>=20
> The contentious case is when an ASP (ASP3) becomes ASP-INACTIVE from
> ASP-DOWN.  I believe that the SGP should notify the newly inactive
> ASP of the current state of the AS (which it did not receive before).
> Samuel thinks that they should somehow guess the state of the AS.
>=20
> --brian
>=20
> Ling-Chih Kao wrote:                                                     =
        (Wed, 13 Aug 2003 08:55:25)
> > Hi, Brian and Samuel
> >=20
> > The answer for both of you is different.
> > See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not sent ASP =
Act.
> > to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional or
> > mandatory?
> >=20
> > Thanks
> >=20
> > Ling-Chih Kao
> >=20
> >=20
> >=20
> > ----- Original Message -----
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran" <sigtran@ietf.org=
>
> > Sent: Friday, August 08, 2003 6:08 PM
> > Subject: Re: [Sigtran] question about m3UA
> >=20
> >=20
> >=20
> > Brian,
> >  Huh, it is not an implementation dependent, rfc says
> >  ASPs which are in that AS should coordinate among themselves the numbe=
r
> >  of active ASPs in the AS.So it is clear to SGP that first arrived
> >  'n' ASPs will receive NTFY(AS-INACT) message.
> >=20
> >  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN state)
> >  you are not restricted but it is not mandatory to send, thats what i
> >  am saying from the beginning.
> >=20
> >  Keep IG as it is.
> > --Samuel
> >=20
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
=2Ecom
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
> >=20
> > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> >=20
> > > Samuel,
> > >
> > > Maybe clear to the ASPs depending on implementation, but not
> > > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > > used by any of the ASPs, why send it in the first place?
> > > If it serves a purpose, it should be sent to all of them to avoid
> > > the race condition.
> > >
> > > --brian
> > >
> > > Samuel Dur D. Jeyaseelan wrote:
> > (Fri, 08 Aug 2003 04:36:50)
> > > >
> > > > Brian,
> > > >  We all know that in n+k redundancy case that ASPes will coordinate
> > > >  among themselves the number of active ASPs in the AS, here it is
> > > >  clear that who is going to go to ACTIVE state then where is the
> > > >  question of race condition?
> > > >
> > > > --Samuel
> > > >
> > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> > *******
> > > >
> > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > >
> > > > > Samuel,
> > > > >
> > > > > What if ASP1 and ASP3 receive it but ASP2 did not, just because
> > > > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > > > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > > > > ASPs when they come up.  It should not be optional.  It is necess=
ary
> > > > > to proper interworking that this race be broken.
> > > > >
> > > > > --brian
> > > > >
> > > > > Samuel Dur D. Jeyaseelan wrote:
> > (Fri, 08 Aug 2003 04:17:31)
> > > > > >
> > > > > > Brian,
> > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, bu=
t
> > ASP1 and
> > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT message=
,
> > > > > >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1 a=
nd
> > ASP3).
> > > > > >
> > > > > >  This is the reason i said it is an optional of sending
> > NTFY(AS-INACT)
> > > > > >  to 'n+1'th ASP.
> > > > > >
> > > > > > --Samuel
> > > > > >
> > > > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of Alcatel USA, =
Inc.
> > *******
> > > > > >
> > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > >
> > > > > > > Samuel,
> > > > > > >
> > > > > > > Yes, I have a problem, because it is a race condition.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > (Fri, 08 Aug 2003 04:04:50)
> > > > > > > >
> > > > > > > > Brian,
> > > > > > > >
> > > > > > > >   I meant first 2 ASPes will receive NTFY messages.Sending =
NTFY
> > to
> > > > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > > > >
> > > > > > > > --Samuel
> > > > > > > >
> > > > > > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > >   ******* The opinions expressed are not those of Alcatel U=
SA,
> > Inc. *******
> > > > > > > >
> > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > >
> > > > > > > > > Samuel,
> > > > > > > > >
> > > > > > > > > None of the ASPs are handling traffic at that point.  Who=
 is
> > to say
> > > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perh=
aps
> > ASP2
> > > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely
> > doesn't know.
> > > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest ch=
oice.
> > > > > > > > >
> > > > > > > > > --brian
> > > > > > > > >
> > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > >
> > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > >
> > > > > > > > > > In n+k reduntancy case,when n=3D2 that means ASP1 and A=
SP2 are
> > going to
> > > > > > > > > > handle the traffic.So sending NTFY to these ASPes is
> > mandatory.
> > > > > > > > > > Sending NTFY to ASP3 is an optional because it is not g=
oing
> > to handle
> > > > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 will =
come
> > up to take
> > > > > > > > > > over the traffic this case SGP will send a NTFY message=
 with
> > AS state,
> > > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > > >
> > > > > > > > > > --Samuel
> > > > > > > > > >
> > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > >   ******* The opinions expressed are not those of Alcat=
el
> > USA, Inc. *******
> > > > > > > > > >
> > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > >
> > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > From the new definition of AS-INACTIVE in sec 4.3.2 o=
f
> > > > > > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, t=
he AS
> > becomes
> > > > > > > > > > > AS-INACTIVE when there are at least n ASPs in either
> > ASP-INACTIVE or
> > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > >
> > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when=
 SGP
> > receives two ASP
> > > > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP recei=
ves
> > ASP UP from ASP3,
> > > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I wa=
nt to
> > know whether it
> > > > > > > > > > > is optional or not?
> > > > > > > > > > >
> > > > > > > > > > > Thanks.
> > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > >
> > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > >
> > > > > > > > > > > NTFY(AS-INACT) is sent to all all available peer ASPe=
s.
> > > > > > > > > > > Note: Available peer means an ASP which received
> > ASP-UP-ACK
> > > > > > > > > > > in response to ASP-UP messages.(as per RFC section
> > 4.3.4.1).
> > > > > > > > > > >
> > > > > > > > > > > If you active the AS as soon as a single ASP goes to
> > ASP-INACT
> > > > > > > > > > > state then it is obvious that whoever sends ASP-UP me=
ssage
> > to
> > > > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to th=
e
> > concern
> > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --Samuel
> > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > >   ******* The opinions expressed are not those of Alc=
atel
> > USA, Inc. *******
> > > > > > > > > > >
> > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Hi all,
> > > > > > > > > > > >
> > > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP should
> > immediately send
> > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is=
 this
> > right?
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks
> > > > > > > > > > > >
> > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
> > <d86942004@ntu.edu.tw>;
> > > > > > > > > > > "sigtran"
> > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Brian,
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > >
> > > > > > > > > > > > > But I think that we agreed that it would be wise =
to
> > tell newly inactive
> > > > > > > > > > >
> >   ------------------
> > > > > > > > > > > > > ASPs that state of the AS.  Also, in the diagram,=
 the
> > state of the AS
> > > > > > > > > > > >   -------------------------
> > > > > > > > > > > >
> > > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY wil=
l be
> > sent to all ASPes
> > > > > > > > > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > > > > > > > > This is what i remember that everybody agreed.
> > > > > > > > > > > >
> > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > does not change with the second ASP (ASP2) sendin=
g
> > ASPUP.  The AS
> > > > > > > > > > > changes
> > > > > > > > > > > > > state to AS-INACTIVE with ASP1 coming up.  Theref=
ore,
> > the diagram should
> > > > > > > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP
> > immediately after the
> > > > > > > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > > > > > > >
> > > > > > > > > > > > > The diagram is quite wrong.  Also it is wrong
> > considering the changes to
> > > > > > > > > > > > > be made to the next issue of the IG.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --brian
> > > > > > > > > > > > >
> > > > > > > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On receiving ASPUP message from ASP3 state of A=
S
> > does not change, so
> > > > > > > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Kamesh
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org=
 on
> > 08/04/2003 11:40:01
> > > > > > > > > > > > AM
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > > cc:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.=
txt>
> > receive
> > > > > > > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanls
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > > > > > bidulock@openss7.org
> > > > > > > > > > > > > http://www.openss7.org/
> > > > > > > > > > > > >
> > > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > > 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
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > 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
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > bidulock@openss7.org
> > > > > > > > > http://www.openss7.org/
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > Sigtran mailing list
> > > > > > > > Sigtran@ietf.org
> > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > >
> > > > > > > --
> > > > > > > Brian F. G. Bidulock
> > > > > > > bidulock@openss7.org
> > > > > > > http://www.openss7.org/
> > > > > > >
> > > > > > >
> > > > >
> > > > > --
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >
> > > > >
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >
> > >
> >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
>=20


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



From exim@www1.ietf.org  Wed Aug 13 00:38:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11630
	for <sigtran-archive@odin.ietf.org>; Wed, 13 Aug 2003 00:38:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnOc-0003QQ-C5
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 00:38:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7D4c2KR013161
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 00:38:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnOb-0003Q4-TW; Wed, 13 Aug 2003 00:38:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnOB-0003Lr-0q
	for sigtran@optimus.ietf.org; Wed, 13 Aug 2003 00:37:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11626
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 00:37:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mnO8-0006Pj-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 00:37:32 -0400
Received: from [142.179.199.224] (helo=gw.openss7.com ident=[+dBgQl1L6V32MSN8PJGPLZ/3WfRWsuDL])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mnO6-0006Pf-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 00:37:31 -0400
Received: from ns.pigworks.openss7.net (IDENT:i9hUKQnL5D9vxapYhdg7/S1OiGuYtJQ2@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h7D4aFE26769;
	Tue, 12 Aug 2003 22:36:15 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h7D4aFE08432;
	Tue, 12 Aug 2003 22:36:15 -0600
Date: Tue, 12 Aug 2003 22:36:14 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030812223614.A8409@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
References: <20030812210340.A7399@openss7.org> <Pine.SOL.4.10.10308122304030.8235-100000@sun2685.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10308122304030.8235-100000@sun2685.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Tue, Aug 12, 2003 at 11:27:04PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h7D4aFE26769
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Samuel,

You confuse SS7 node state with AS state.  Also, SS7 node state has
an audit procedure using DAUD, so if the ASP ever wants to know the
SS7 node state in can enquire as to such.  Therefore it is not necessary
for the SGP to send SS7 node state to newly active ASPs.

AS state OTOH has NO audit procedure.  There is no way for the newly
inactive ASP to request the AS state from the SGP.  The smart SGP
implemetnation will send it anyway.  The foolish one will require the ASP
to guess.

Either an audit procedure is required, or the SGP should always send NTFY
of the AS state to newly inactive ASPs.

--brian

Samuel Dur D. Jeyaseelan wrote:                                          =
           (Tue, 12 Aug 2003 23:27:04)
>=20
> Brian,
>  If it is mandatory to send NTFY(AS-STATE) to all ASPes(other than down=
),
>  Why dont we send SS7 node availability status(like DUNA,DAVA,DRST...)=20
>  to all INACTIVE-ASPes?(because anyway when INACTIVE-ASP moves to ACTIV=
E
>  ASP, it should know the status of SS7 nodes but finally it was decided
>  that newly active ASP will send an DAUD and gets the SS7 node(s) statu=
s
>  or SGP may send SS7 node(s) status to the newly active ASP.)
>  This i suggested long back(i think you remeber) but you strongly oppos=
ed
>  it. Now you are partially true with my old arguments.
>=20
> --Samuel
>=20
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
>=20
> On Tue, 12 Aug 2003, Brian F. G. Bidulock wrote:
>=20
> > Ling-Chih,
> >=20
> > Mandatory.  All ASP-INACTIVE ASPs for an AS receive notifications
> > of state change.  ASP3 is ASP-INACTIVE in this case and must receive
> > the notification.
> >=20
> > The contentious case is when an ASP (ASP3) becomes ASP-INACTIVE from
> > ASP-DOWN.  I believe that the SGP should notify the newly inactive
> > ASP of the current state of the AS (which it did not receive before).
> > Samuel thinks that they should somehow guess the state of the AS.
> >=20
> > --brian
> >=20
> > Ling-Chih Kao wrote:                                                 =
            (Wed, 13 Aug 2003 08:55:25)
> > > Hi, Brian and Samuel
> > >=20
> > > The answer for both of you is different.
> > > See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not sent =
ASP Act.
> > > to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional or
> > > mandatory?
> > >=20
> > > Thanks
> > >=20
> > > Ling-Chih Kao
> > >=20
> > >=20
> > >=20
> > > ----- Original Message -----
> > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran" <sigtran@ietf=
.org>
> > > Sent: Friday, August 08, 2003 6:08 PM
> > > Subject: Re: [Sigtran] question about m3UA
> > >=20
> > >=20
> > >=20
> > > Brian,
> > >  Huh, it is not an implementation dependent, rfc says
> > >  ASPs which are in that AS should coordinate among themselves the n=
umber
> > >  of active ASPs in the AS.So it is clear to SGP that first arrived
> > >  'n' ASPs will receive NTFY(AS-INACT) message.
> > >=20
> > >  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN st=
ate)
> > >  you are not restricted but it is not mandatory to send, thats what=
 i
> > >  am saying from the beginning.
> > >=20
> > >  Keep IG as it is.
> > > --Samuel
> > >=20
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alc=
atel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc.=
 *******
> > >=20
> > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > >=20
> > > > Samuel,
> > > >
> > > > Maybe clear to the ASPs depending on implementation, but not
> > > > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > > > used by any of the ASPs, why send it in the first place?
> > > > If it serves a purpose, it should be sent to all of them to avoid
> > > > the race condition.
> > > >
> > > > --brian
> > > >
> > > > Samuel Dur D. Jeyaseelan wrote:
> > > (Fri, 08 Aug 2003 04:36:50)
> > > > >
> > > > > Brian,
> > > > >  We all know that in n+k redundancy case that ASPes will coordi=
nate
> > > > >  among themselves the number of active ASPs in the AS, here it =
is
> > > > >  clear that who is going to go to ACTIVE state then where is th=
e
> > > > >  question of race condition?
> > > > >
> > > > > --Samuel
> > > > >
> > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, =
Inc.
> > > *******
> > > > >
> > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > >
> > > > > > Samuel,
> > > > > >
> > > > > > What if ASP1 and ASP3 receive it but ASP2 did not, just becau=
se
> > > > > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > > > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > > > > the race condition by sending NTFY(AS-INACTIVVE) to all of th=
e
> > > > > > ASPs when they come up.  It should not be optional.  It is ne=
cessary
> > > > > > to proper interworking that this race be broken.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > (Fri, 08 Aug 2003 04:17:31)
> > > > > > >
> > > > > > > Brian,
> > > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively=
, but
> > > ASP1 and
> > > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT mes=
sage,
> > > > > > >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(AS=
P1 and
> > > ASP3).
> > > > > > >
> > > > > > >  This is the reason i said it is an optional of sending
> > > NTFY(AS-INACT)
> > > > > > >  to 'n+1'th ASP.
> > > > > > >
> > > > > > > --Samuel
> > > > > > >
> > > > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > >   ******* The opinions expressed are not those of Alcatel U=
SA, Inc.
> > > *******
> > > > > > >
> > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > >
> > > > > > > > Samuel,
> > > > > > > >
> > > > > > > > Yes, I have a problem, because it is a race condition.
> > > > > > > >
> > > > > > > > --brian
> > > > > > > >
> > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > (Fri, 08 Aug 2003 04:04:50)
> > > > > > > > >
> > > > > > > > > Brian,
> > > > > > > > >
> > > > > > > > >   I meant first 2 ASPes will receive NTFY messages.Send=
ing NTFY
> > > to
> > > > > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > > > > >
> > > > > > > > > --Samuel
> > > > > > > > >
> > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > >   ******* The opinions expressed are not those of Alcat=
el USA,
> > > Inc. *******
> > > > > > > > >
> > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > >
> > > > > > > > > > Samuel,
> > > > > > > > > >
> > > > > > > > > > None of the ASPs are handling traffic at that point. =
 Who is
> > > to say
> > > > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  =
Perhaps
> > > ASP2
> > > > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP su=
rely
> > > doesn't know.
> > > > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wises=
t choice.
> > > > > > > > > >
> > > > > > > > > > --brian
> > > > > > > > > >
> > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > > >
> > > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > > >
> > > > > > > > > > > In n+k reduntancy case,when n=3D2 that means ASP1 a=
nd ASP2 are
> > > going to
> > > > > > > > > > > handle the traffic.So sending NTFY to these ASPes i=
s
> > > mandatory.
> > > > > > > > > > > Sending NTFY to ASP3 is an optional because it is n=
ot going
> > > to handle
> > > > > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 w=
ill come
> > > up to take
> > > > > > > > > > > over the traffic this case SGP will send a NTFY mes=
sage with
> > > AS state,
> > > > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > > > >
> > > > > > > > > > > --Samuel
> > > > > > > > > > >
> > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > >   ******* The opinions expressed are not those of A=
lcatel
> > > USA, Inc. *******
> > > > > > > > > > >
> > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > From the new definition of AS-INACTIVE in sec 4.3=
.2 of
> > > > > > > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt=
>, the AS
> > > becomes
> > > > > > > > > > > > AS-INACTIVE when there are at least n ASPs in eit=
her
> > > ASP-INACTIVE or
> > > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > > >
> > > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE =
when SGP
> > > receives two ASP
> > > > > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP r=
eceives
> > > ASP UP from ASP3,
> > > > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. =
I want to
> > > know whether it
> > > > > > > > > > > > is optional or not?
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks.
> > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > >
> > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > > >
> > > > > > > > > > > > NTFY(AS-INACT) is sent to all all available peer =
ASPes.
> > > > > > > > > > > > Note: Available peer means an ASP which received
> > > ASP-UP-ACK
> > > > > > > > > > > > in response to ASP-UP messages.(as per RFC sectio=
n
> > > 4.3.4.1).
> > > > > > > > > > > >
> > > > > > > > > > > > If you active the AS as soon as a single ASP goes=
 to
> > > ASP-INACT
> > > > > > > > > > > > state then it is obvious that whoever sends ASP-U=
P message
> > > to
> > > > > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) t=
o the
> > > concern
> > > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > --Samuel
> > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > >   ******* The opinions expressed are not those of=
 Alcatel
> > > USA, Inc. *******
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > >
> > > > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP sh=
ould
> > > immediately send
> > > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS=
. Is this
> > > right?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.or=
g>
> > > > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
> > > <d86942004@ntu.edu.tw>;
> > > > > > > > > > > > "sigtran"
> > > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Brian,
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > But I think that we agreed that it would be w=
ise to
> > > tell newly inactive
> > > > > > > > > > > >
> > >   ------------------
> > > > > > > > > > > > > > ASPs that state of the AS.  Also, in the diag=
ram, the
> > > state of the AS
> > > > > > > > > > > > >   -------------------------
> > > > > > > > > > > > >
> > > > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY=
 will be
> > > sent to all ASPes
> > > > > > > > > > > > > (other than DOWN-ASPes) pertaining to the same =
RC.
> > > > > > > > > > > > > This is what i remember that everybody agreed.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > > does not change with the second ASP (ASP2) se=
nding
> > > ASPUP.  The AS
> > > > > > > > > > > > changes
> > > > > > > > > > > > > > state to AS-INACTIVE with ASP1 coming up.  Th=
erefore,
> > > the diagram should
> > > > > > > > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each=
 ASP
> > > immediately after the
> > > > > > > > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > The diagram is quite wrong.  Also it is wrong
> > > considering the changes to
> > > > > > > > > > > > > > be made to the next issue of the IG.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --brian
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On receiving ASPUP message from ASP3 state =
of AS
> > > does not change, so
> > > > > > > > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Kamesh
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf=
.org on
> > > 08/04/2003 11:40:01
> > > > > > > > > > > > > AM
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > > > cc:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide=
-04.txt>
> > > receive
> > > > > > > > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thanls
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > ___________________________________________=
____
> > > > > > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigt=
ran
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > > > > > > bidulock@openss7.org
> > > > > > > > > > > > > > http://www.openss7.org/
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > _____________________________________________=
__
> > > > > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtra=
n
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > > 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
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > > bidulock@openss7.org
> > > > > > > > > > http://www.openss7.org/
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > Sigtran mailing list
> > > > > > > > > Sigtran@ietf.org
> > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > >
> > > > > > > > --
> > > > > > > > Brian F. G. Bidulock
> > > > > > > > bidulock@openss7.org
> > > > > > > > http://www.openss7.org/
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > > --
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > > > >
> > > > > >
> > > >
> > > > --
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > >
> > > >
> > >=20
> > >=20
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >=20
> >=20

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Wed Aug 13 00:58:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12005
	for <sigtran-archive@odin.ietf.org>; Wed, 13 Aug 2003 00:58:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnhy-00045G-6v
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 00:58:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7D4w2ke015698
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 00:58:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnhx-00044x-DM; Wed, 13 Aug 2003 00:58:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnhO-00044l-K5
	for sigtran@optimus.ietf.org; Wed, 13 Aug 2003 00:57:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12001
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 00:57:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mnhL-0006Uh-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 00:57:23 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mnhK-0006Ue-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 00:57:23 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h7D4uqB3026969;
	Tue, 12 Aug 2003 23:56:52 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h7D4uP1C005037;
	Tue, 12 Aug 2003 23:56:26 -0500 (CDT)
Date: Tue, 12 Aug 2003 23:56:25 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <Pine.SOL.4.10.10308080450510.6428-100000@sun2685.ssd.usa.alcatel.com>
Message-ID: <Pine.SOL.4.10.10308122352590.8235-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: QUOTED-PRINTABLE


Brian,
 Why dont you answer to this email?

 If you want to change IG then please answer the email.

 (i dont want to go back to old email, just i referred)

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 8 Aug 2003, Samuel Dur D. Jeyaseelan wrote:

>=20
> Brian,
>  Huh, it is not an implementation dependent, rfc says=20
>  ASPs which are in that AS should coordinate among themselves the number
>  of active ASPs in the AS.So it is clear to SGP that first arrived
>  'n' ASPs will receive NTFY(AS-INACT) message.
>=20
>  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN state)
>  you are not restricted but it is not mandatory to send, thats what i
>  am saying from the beginning.
>=20
>  Keep IG as it is.
> --Samuel
>=20
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.c=
om
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *****=
**
>=20
> On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
>=20
> > Samuel,
> >=20
> > Maybe clear to the ASPs depending on implementation, but not
> > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > used by any of the ASPs, why send it in the first place?
> > If it serves a purpose, it should be sent to all of them to avoid
> > the race condition.
> >=20
> > --brian
> >=20
> > Samuel Dur D. Jeyaseelan wrote:                                        =
             (Fri, 08 Aug 2003 04:36:50)
> > >=20
> > > Brian,
> > >  We all know that in n+k redundancy case that ASPes will coordinate
> > >  among themselves the number of active ASPs in the AS, here it is
> > >  clear that who is going to go to ACTIVE state then where is the
> > >  question of race condition?
> > >=20
> > > --Samuel
> > >=20
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcat=
el.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc. *=
******
> > >=20
> > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > >=20
> > > > Samuel,
> > > >=20
> > > > What if ASP1 and ASP3 receive it but ASP2 did not, just because
> > > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > > > ASPs when they come up.  It should not be optional.  It is necessar=
y
> > > > to proper interworking that this race be broken.
> > > >=20
> > > > --brian
> > > >=20
> > > > Samuel Dur D. Jeyaseelan wrote:                                    =
                 (Fri, 08 Aug 2003 04:17:31)
> > > > >=20
> > > > > Brian,
> > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, but =
ASP1 and
> > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT message,
> > > > >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1 and=
 ASP3).
> > > > >=20
> > > > >  This is the reason i said it is an optional of sending NTFY(AS-I=
NACT)
> > > > >  to 'n+1'th ASP.
> > > > >=20
> > > > > --Samuel
> > > > >=20
> > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.a=
lcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, In=
c. *******
> > > > >=20
> > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > >=20
> > > > > > Samuel,
> > > > > >=20
> > > > > > Yes, I have a problem, because it is a race condition.
> > > > > >=20
> > > > > > --brian
> > > > > >=20
> > > > > > Samuel Dur D. Jeyaseelan wrote:                                =
                     (Fri, 08 Aug 2003 04:04:50)
> > > > > > >=20
> > > > > > > Brian,
> > > > > > >=20
> > > > > > >   I meant first 2 ASPes will receive NTFY messages.Sending NT=
FY to=20
> > > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > > >=20
> > > > > > > --Samuel
> > > > > > >=20
> > > > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.u=
sa.alcatel.com
> > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > >   ******* The opinions expressed are not those of Alcatel USA=
, Inc. *******
> > > > > > >=20
> > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > >=20
> > > > > > > > Samuel,
> > > > > > > >=20
> > > > > > > > None of the ASPs are handling traffic at that point.  Who i=
s to say
> > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Perhap=
s ASP2
> > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely d=
oesn't know.
> > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest choi=
ce.
> > > > > > > >=20
> > > > > > > > --brian
> > > > > > > >=20
> > > > > > > > Samuel Dur D. Jeyaseelan wrote:                            =
                         (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > >=20
> > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > >=20
> > > > > > > > > In n+k reduntancy case,when n=3D2 that means ASP1 and ASP=
2 are going to
> > > > > > > > > handle the traffic.So sending NTFY to these ASPes is mand=
atory.
> > > > > > > > > Sending NTFY to ASP3 is an optional because it is not goi=
ng to handle=20
> > > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 will co=
me up to take
> > > > > > > > > over the traffic this case SGP will send a NTFY message w=
ith AS state,
> > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > >=20
> > > > > > > > > --Samuel
> > > > > > > > >=20
> > > > > > > > >   Alcatel USA, Inc.                  Internet: <userid>@s=
sd.usa.alcatel.com
> > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > >   ******* The opinions expressed are not those of Alcatel=
 USA, Inc. *******
> > > > > > > > >=20
> > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > >=20
> > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > >=20
> > > > > > > > > >=20
> > > > > > > > > > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > > > > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>, the=
 AS becomes
> > > > > > > > > > AS-INACTIVE when there are at least n ASPs in either AS=
P-INACTIVE or
> > > > > > > > > > AS-ACTIVE.
> > > > > > > > > >=20
> > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when S=
GP receives two ASP
> > > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP receive=
s  ASP UP from ASP3,
> > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I want=
 to know whether it
> > > > > > > > > > is optional or not?
> > > > > > > > > >=20
> > > > > > > > > > Thanks.
> > > > > > > > > > Ling-Chih Kao
> > > > > > > > > >=20
> > > > > > > > > > ----- Original Message -----
> > > > > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alca=
tel.com>
> > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > >=20
> > > > > > > > > >=20
> > > > > > > > > >=20
> > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > >=20
> > > > > > > > > > NTFY(AS-INACT) is sent to all all available peer ASPes.
> > > > > > > > > > Note: Available peer means an ASP which received ASP-UP=
-ACK
> > > > > > > > > > in response to ASP-UP messages.(as per RFC section 4.3.=
4.1).
> > > > > > > > > >=20
> > > > > > > > > > If you active the AS as soon as a single ASP goes to AS=
P-INACT
> > > > > > > > > > state then it is obvious that whoever sends ASP-UP mess=
age to
> > > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to the =
concern
> > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > >=20
> > > > > > > > > >=20
> > > > > > > > > > --Samuel
> > > > > > > > > >   Alcatel USA, Inc.                  Internet: <userid>=
@ssd.usa.alcatel.com
> > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > >   ******* The opinions expressed are not those of Alcat=
el USA, Inc. *******
> > > > > > > > > >=20
> > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > >=20
> > > > > > > > > > > Hi all,
> > > > > > > > > > >
> > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP should i=
mmediately send
> > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is t=
his right?
> > > > > > > > > > >
> > > > > > > > > > > Thanks
> > > > > > > > > > >
> > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.al=
catel.com>
> > > > > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942004@=
ntu.edu.tw>;
> > > > > > > > > > "sigtran"
> > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Brian,
> > > > > > > > > > >
> > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > >
> > > > > > > > > > > > kakaul,
> > > > > > > > > > > >
> > > > > > > > > > > > But I think that we agreed that it would be wise to=
 tell newly inactive
> > > > > > > > > > >                                                      =
 ------------------
> > > > > > > > > > > > ASPs that state of the AS.  Also, in the diagram, t=
he state of the AS
> > > > > > > > > > >   -------------------------
> > > > > > > > > > >
> > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY will =
be sent to all ASPes
> > > > > > > > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > > > > > > > This is what i remember that everybody agreed.
> > > > > > > > > > >
> > > > > > > > > > > --Samuel
> > > > > > > > > > > > does not change with the second ASP (ASP2) sending =
ASPUP.  The AS
> > > > > > > > > > changes
> > > > > > > > > > > > state to AS-INACTIVE with ASP1 coming up.  Therefor=
e, the diagram should
> > > > > > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each ASP i=
mmediately after the
> > > > > > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > > > > > >
> > > > > > > > > > > > The diagram is quite wrong.  Also it is wrong consi=
dering the changes to
> > > > > > > > > > > > be made to the next issue of the IG.
> > > > > > > > > > > >
> > > > > > > > > > > > --brian
> > > > > > > > > > > >
> > > > > > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On receiving ASPUP message from ASP3 state of AS =
does not change, so
> > > > > > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Kamesh
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.org o=
n 08/04/2003 11:40:01
> > > > > > > > > > > AM
> > > > > > > > > > > > >
> > > > > > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > cc:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-04.tx=
t> receive
> > > > > > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanls
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > > > > bidulock@openss7.org
> > > > > > > > > > > > http://www.openss7.org/
> > > > > > > > > > > >
> > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > 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
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >=20
> > > > > > > > > >=20
> > > > > > > > > > _______________________________________________
> > > > > > > > > > Sigtran mailing list
> > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > > >=20
> > > > > > > > > >=20
> > > > > > > > >=20
> > > > > > > > >=20
> > > > > > > > > _______________________________________________
> > > > > > > > > Sigtran mailing list
> > > > > > > > > Sigtran@ietf.org
> > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > >=20
> > > > > > > > --=20
> > > > > > > > Brian F. G. Bidulock
> > > > > > > > bidulock@openss7.org
> > > > > > > > http://www.openss7.org/
> > > > > > > >=20
> > > > > > > >=20
> > > > > > >=20
> > > > > > >=20
> > > > > > > _______________________________________________
> > > > > > > Sigtran mailing list
> > > > > > > Sigtran@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > >=20
> > > > > > --=20
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > > > >=20
> > > > > >=20
> > > >=20
> > > > --=20
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > >=20
> > > >=20
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> >=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
>=20


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



From exim@www1.ietf.org  Wed Aug 13 01:07:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12290
	for <sigtran-archive@odin.ietf.org>; Wed, 13 Aug 2003 01:07:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnqh-0004QS-3H
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 01:07:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7D573Nu017013
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 01:07:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnqg-0004Pw-Cj; Wed, 13 Aug 2003 01:07:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnqQ-0004PN-4F
	for sigtran@optimus.ietf.org; Wed, 13 Aug 2003 01:06:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12265
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 01:06:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mnqN-0006Z2-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 01:06:43 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[27ikq82jqxZAvzZtqKgh52oc2fCsmgBx])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mnqM-0006Yz-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 01:06:42 -0400
Received: from ns.pigworks.openss7.net (IDENT:qTqFTbACZTJ0yj+2d/A1Wv51B7JL0Jq5@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h7D56cE27246;
	Tue, 12 Aug 2003 23:06:38 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h7D56cQ08757;
	Tue, 12 Aug 2003 23:06:38 -0600
Date: Tue, 12 Aug 2003 23:06:38 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030812230638.A8740@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	Ling-Chih Kao <d86942004@ntu.edu.tw>, sigtran <sigtran@ietf.org>
References: <Pine.SOL.4.10.10308080450510.6428-100000@sun2685.ssd.usa.alcatel.com> <Pine.SOL.4.10.10308122352590.8235-100000@sun2685.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10308122352590.8235-100000@sun2685.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Tue, Aug 12, 2003 at 11:56:25PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h7D56cE27246
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Samuel,

What question did you need me to answer?

--brian

Samuel Dur D. Jeyaseelan wrote:                                          =
           (Tue, 12 Aug 2003 23:56:25)
>=20
> Brian,
>  Why dont you answer to this email?
>=20
>  If you want to change IG then please answer the email.
>=20
>  (i dont want to go back to old email, just i referred)
>=20
> --Samuel
>=20
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel=
.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. ***=
****
>=20
> On Fri, 8 Aug 2003, Samuel Dur D. Jeyaseelan wrote:
>=20
> >=20
> > Brian,
> >  Huh, it is not an implementation dependent, rfc says=20
> >  ASPs which are in that AS should coordinate among themselves the num=
ber
> >  of active ASPs in the AS.So it is clear to SGP that first arrived
> >  'n' ASPs will receive NTFY(AS-INACT) message.
> >=20
> >  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN stat=
e)
> >  you are not restricted but it is not mandatory to send, thats what i
> >  am saying from the beginning.
> >=20
> >  Keep IG as it is.
> > --Samuel
> >=20
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcat=
el.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. *=
******
> >=20
> > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> >=20
> > > Samuel,
> > >=20
> > > Maybe clear to the ASPs depending on implementation, but not
> > > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > > used by any of the ASPs, why send it in the first place?
> > > If it serves a purpose, it should be sent to all of them to avoid
> > > the race condition.
> > >=20
> > > --brian
> > >=20
> > > Samuel Dur D. Jeyaseelan wrote:                                    =
                 (Fri, 08 Aug 2003 04:36:50)
> > > >=20
> > > > Brian,
> > > >  We all know that in n+k redundancy case that ASPes will coordina=
te
> > > >  among themselves the number of active ASPs in the AS, here it is
> > > >  clear that who is going to go to ACTIVE state then where is the
> > > >  question of race condition?
> > > >=20
> > > > --Samuel
> > > >=20
> > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.a=
lcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, In=
c. *******
> > > >=20
> > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > >=20
> > > > > Samuel,
> > > > >=20
> > > > > What if ASP1 and ASP3 receive it but ASP2 did not, just because
> > > > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > > > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > > > > ASPs when they come up.  It should not be optional.  It is nece=
ssary
> > > > > to proper interworking that this race be broken.
> > > > >=20
> > > > > --brian
> > > > >=20
> > > > > Samuel Dur D. Jeyaseelan wrote:                                =
                     (Fri, 08 Aug 2003 04:17:31)
> > > > > >=20
> > > > > > Brian,
> > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, =
but ASP1 and
> > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT messa=
ge,
> > > > > >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1=
 and ASP3).
> > > > > >=20
> > > > > >  This is the reason i said it is an optional of sending NTFY(=
AS-INACT)
> > > > > >  to 'n+1'th ASP.
> > > > > >=20
> > > > > > --Samuel
> > > > > >=20
> > > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.u=
sa.alcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of Alcatel USA=
, Inc. *******
> > > > > >=20
> > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > >=20
> > > > > > > Samuel,
> > > > > > >=20
> > > > > > > Yes, I have a problem, because it is a race condition.
> > > > > > >=20
> > > > > > > --brian
> > > > > > >=20
> > > > > > > Samuel Dur D. Jeyaseelan wrote:                            =
                         (Fri, 08 Aug 2003 04:04:50)
> > > > > > > >=20
> > > > > > > > Brian,
> > > > > > > >=20
> > > > > > > >   I meant first 2 ASPes will receive NTFY messages.Sendin=
g NTFY to=20
> > > > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > > > >=20
> > > > > > > > --Samuel
> > > > > > > >=20
> > > > > > > >   Alcatel USA, Inc.                  Internet: <userid>@s=
sd.usa.alcatel.com
> > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > >   ******* The opinions expressed are not those of Alcatel=
 USA, Inc. *******
> > > > > > > >=20
> > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > >=20
> > > > > > > > > Samuel,
> > > > > > > > >=20
> > > > > > > > > None of the ASPs are handling traffic at that point.  W=
ho is to say
> > > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.  Pe=
rhaps ASP2
> > > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP sure=
ly doesn't know.
> > > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest =
choice.
> > > > > > > > >=20
> > > > > > > > > --brian
> > > > > > > > >=20
> > > > > > > > > Samuel Dur D. Jeyaseelan wrote:                        =
                             (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > >=20
> > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > >=20
> > > > > > > > > > In n+k reduntancy case,when n=3D2 that means ASP1 and=
 ASP2 are going to
> > > > > > > > > > handle the traffic.So sending NTFY to these ASPes is =
mandatory.
> > > > > > > > > > Sending NTFY to ASP3 is an optional because it is not=
 going to handle=20
> > > > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 wil=
l come up to take
> > > > > > > > > > over the traffic this case SGP will send a NTFY messa=
ge with AS state,
> > > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > > >=20
> > > > > > > > > > --Samuel
> > > > > > > > > >=20
> > > > > > > > > >   Alcatel USA, Inc.                  Internet: <useri=
d>@ssd.usa.alcatel.com
> > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > >   ******* The opinions expressed are not those of Alc=
atel USA, Inc. *******
> > > > > > > > > >=20
> > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > >=20
> > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > >=20
> > > > > > > > > > >=20
> > > > > > > > > > > From the new definition of AS-INACTIVE in sec 4.3.2=
 of
> > > > > > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>,=
 the AS becomes
> > > > > > > > > > > AS-INACTIVE when there are at least n ASPs in eithe=
r ASP-INACTIVE or
> > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > >=20
> > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE wh=
en SGP receives two ASP
> > > > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP rec=
eives  ASP UP from ASP3,
> > > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I =
want to know whether it
> > > > > > > > > > > is optional or not?
> > > > > > > > > > >=20
> > > > > > > > > > > Thanks.
> > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > >=20
> > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.=
alcatel.com>
> > > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > >=20
> > > > > > > > > > >=20
> > > > > > > > > > >=20
> > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > >=20
> > > > > > > > > > > NTFY(AS-INACT) is sent to all all available peer AS=
Pes.
> > > > > > > > > > > Note: Available peer means an ASP which received AS=
P-UP-ACK
> > > > > > > > > > > in response to ASP-UP messages.(as per RFC section =
4.3.4.1).
> > > > > > > > > > >=20
> > > > > > > > > > > If you active the AS as soon as a single ASP goes t=
o ASP-INACT
> > > > > > > > > > > state then it is obvious that whoever sends ASP-UP =
message to
> > > > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to =
the concern
> > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > >=20
> > > > > > > > > > >=20
> > > > > > > > > > > --Samuel
> > > > > > > > > > >   Alcatel USA, Inc.                  Internet: <use=
rid>@ssd.usa.alcatel.com
> > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > >   ******* The opinions expressed are not those of A=
lcatel USA, Inc. *******
> > > > > > > > > > >=20
> > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > >=20
> > > > > > > > > > > > Hi all,
> > > > > > > > > > > >
> > > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP shou=
ld immediately send
> > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. =
Is this right?
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks
> > > > > > > > > > > >
> > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.us=
a.alcatel.com>
> > > > > > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao" <d86942=
004@ntu.edu.tw>;
> > > > > > > > > > > "sigtran"
> > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Brian,
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > >
> > > > > > > > > > > > > But I think that we agreed that it would be wis=
e to tell newly inactive
> > > > > > > > > > > >                                                  =
     ------------------
> > > > > > > > > > > > > ASPs that state of the AS.  Also, in the diagra=
m, the state of the AS
> > > > > > > > > > > >   -------------------------
> > > > > > > > > > > >
> > > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY w=
ill be sent to all ASPes
> > > > > > > > > > > > (other than DOWN-ASPes) pertaining to the same RC.
> > > > > > > > > > > > This is what i remember that everybody agreed.
> > > > > > > > > > > >
> > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > does not change with the second ASP (ASP2) send=
ing ASPUP.  The AS
> > > > > > > > > > > changes
> > > > > > > > > > > > > state to AS-INACTIVE with ASP1 coming up.  Ther=
efore, the diagram should
> > > > > > > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each A=
SP immediately after the
> > > > > > > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > > > > > > >
> > > > > > > > > > > > > The diagram is quite wrong.  Also it is wrong c=
onsidering the changes to
> > > > > > > > > > > > > be made to the next issue of the IG.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --brian
> > > > > > > > > > > > >
> > > > > > > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On receiving ASPUP message from ASP3 state of=
 AS does not change, so
> > > > > > > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Kamesh
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.o=
rg on 08/04/2003 11:40:01
> > > > > > > > > > > > AM
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > > cc:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > > > > > > <draft-ietf-sigtran-m3ua-implementors-guide-0=
4.txt> receive
> > > > > > > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanls
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > _____________________________________________=
__
> > > > > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtra=
n
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > > > > > bidulock@openss7.org
> > > > > > > > > > > > > http://www.openss7.org/
> > > > > > > > > > > > >
> > > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > > 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
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >=20
> > > > > > > > > > >=20
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > > > >=20
> > > > > > > > > > >=20
> > > > > > > > > >=20
> > > > > > > > > >=20
> > > > > > > > > > _______________________________________________
> > > > > > > > > > Sigtran mailing list
> > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > > > >=20
> > > > > > > > > --=20
> > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > bidulock@openss7.org
> > > > > > > > > http://www.openss7.org/
> > > > > > > > >=20
> > > > > > > > >=20
> > > > > > > >=20
> > > > > > > >=20
> > > > > > > > _______________________________________________
> > > > > > > > Sigtran mailing list
> > > > > > > > Sigtran@ietf.org
> > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > >=20
> > > > > > > --=20
> > > > > > > Brian F. G. Bidulock
> > > > > > > bidulock@openss7.org
> > > > > > > http://www.openss7.org/
> > > > > > >=20
> > > > > > >=20
> > > > >=20
> > > > > --=20
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >=20
> > > > >=20
> > >=20
> > > --=20
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >=20
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > >=20
> > >=20
> >=20
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> >=20

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Wed Aug 13 01:17:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12516
	for <sigtran-archive@odin.ietf.org>; Wed, 13 Aug 2003 01:17:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mo0L-0004yX-Qm
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 01:17:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7D5H1FN019105
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 01:17:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mo0L-0004xw-9j; Wed, 13 Aug 2003 01:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mnzs-0004xg-W6
	for sigtran@optimus.ietf.org; Wed, 13 Aug 2003 01:16:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12509
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 01:16:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mnzq-0006ds-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 01:16:30 -0400
Received: from relay5.tp1rc.edu.tw ([163.28.16.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mnzo-0006dp-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 01:16:28 -0400
Received: from KHL (61-219-40-1.HINET-IP.hinet.net [61.219.40.1])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by relay5.tp1rc.edu.tw (Postfix) with ESMTP
	id 713B2106E88; Wed, 13 Aug 2003 13:16:26 +0800 (CST)
Message-ID: <006f01c3615b$228537e0$6ec5900a@saoe.com>
From: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: <bidulock@openss7.org>, "sigtran" <sigtran@ietf.org>
References: <Pine.SOL.4.10.10308122304030.8235-100000@sun2685.ssd.usa.alcatel.com>
Subject: Re: [Sigtran] question about m3UA
Date: Wed, 13 Aug 2003 13:24:07 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Hi, Samuel

1.
ASP3  in Sec. 5.1.4 did not send ASP Act. to SGP; however,  it  received
NOTIFY (AS-ACTIVE).

This NOTIFY is also optional whether ASP3 send ASP Act. to SGP or not.
That's right ?

Should ASP3 send  ASP Act. to SGP?

2.
Should ASP3 send  ASP UP to SGP?

If ASP3 did not sent ASP UP to SGP, reception of NOTIFY(AS-INACTIVE) is a=
lso
optional. Or, ASP3 will not receive  NOTIFY(AS-INACTIVE) because ASP3 doe=
s
not sent ASP UP to SGP.


Ling-Chih Kao

----- Original Message -----
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran" <sigtran@ietf.org>
Sent: Wednesday, August 13, 2003 12:27 PM
Subject: Re: [Sigtran] question about m3UA



Brian,
 If it is mandatory to send NTFY(AS-STATE) to all ASPes(other than down),
 Why dont we send SS7 node availability status(like DUNA,DAVA,DRST...)
 to all INACTIVE-ASPes?(because anyway when INACTIVE-ASP moves to ACTIVE
 ASP, it should know the status of SS7 nodes but finally it was decided
 that newly active ASP will send an DAUD and gets the SS7 node(s) status
 or SGP may send SS7 node(s) status to the newly active ASP.)
 This i suggested long back(i think you remeber) but you strongly opposed
 it. Now you are partially true with my old arguments.

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.c=
om
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *****=
**

On Tue, 12 Aug 2003, Brian F. G. Bidulock wrote:

> Ling-Chih,
>
> Mandatory.  All ASP-INACTIVE ASPs for an AS receive notifications
> of state change.  ASP3 is ASP-INACTIVE in this case and must receive
> the notification.
>
> The contentious case is when an ASP (ASP3) becomes ASP-INACTIVE from
> ASP-DOWN.  I believe that the SGP should notify the newly inactive
> ASP of the current state of the AS (which it did not receive before).
> Samuel thinks that they should somehow guess the state of the AS.
>
> --brian
>
> Ling-Chih Kao wrote:
(Wed, 13 Aug 2003 08:55:25)
> > Hi, Brian and Samuel
> >
> > The answer for both of you is different.
> > See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not sent AS=
P
Act.
> > to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional or
> > mandatory?
> >
> > Thanks
> >
> > Ling-Chih Kao
> >
> >
> >
> > ----- Original Message -----
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran" <sigtran@ietf.o=
rg>
> > Sent: Friday, August 08, 2003 6:08 PM
> > Subject: Re: [Sigtran] question about m3UA
> >
> >
> >
> > Brian,
> >  Huh, it is not an implementation dependent, rfc says
> >  ASPs which are in that AS should coordinate among themselves the num=
ber
> >  of active ASPs in the AS.So it is clear to SGP that first arrived
> >  'n' ASPs will receive NTFY(AS-INACT) message.
> >
> >  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN stat=
e)
> >  you are not restricted but it is not mandatory to send, thats what i
> >  am saying from the beginning.
> >
> >  Keep IG as it is.
> > --Samuel
> >
> >   Alcatel USA, Inc.                  Internet:
<userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc.
*******
> >
> > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> >
> > > Samuel,
> > >
> > > Maybe clear to the ASPs depending on implementation, but not
> > > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > > used by any of the ASPs, why send it in the first place?
> > > If it serves a purpose, it should be sent to all of them to avoid
> > > the race condition.
> > >
> > > --brian
> > >
> > > Samuel Dur D. Jeyaseelan wrote:
> > (Fri, 08 Aug 2003 04:36:50)
> > > >
> > > > Brian,
> > > >  We all know that in n+k redundancy case that ASPes will coordina=
te
> > > >  among themselves the number of active ASPs in the AS, here it is
> > > >  clear that who is going to go to ACTIVE state then where is the
> > > >  question of race condition?
> > > >
> > > > --Samuel
> > > >
> > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, In=
c.
> > *******
> > > >
> > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > >
> > > > > Samuel,
> > > > >
> > > > > What if ASP1 and ASP3 receive it but ASP2 did not, just because
> > > > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > > > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > > > > ASPs when they come up.  It should not be optional.  It is
necessary
> > > > > to proper interworking that this race be broken.
> > > > >
> > > > > --brian
> > > > >
> > > > > Samuel Dur D. Jeyaseelan wrote:
> > (Fri, 08 Aug 2003 04:17:31)
> > > > > >
> > > > > > Brian,
> > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, =
but
> > ASP1 and
> > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT messa=
ge,
> > > > > >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1
and
> > ASP3).
> > > > > >
> > > > > >  This is the reason i said it is an optional of sending
> > NTFY(AS-INACT)
> > > > > >  to 'n+1'th ASP.
> > > > > >
> > > > > > --Samuel
> > > > > >
> > > > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of Alcatel USA=
,
Inc.
> > *******
> > > > > >
> > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > >
> > > > > > > Samuel,
> > > > > > >
> > > > > > > Yes, I have a problem, because it is a race condition.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > (Fri, 08 Aug 2003 04:04:50)
> > > > > > > >
> > > > > > > > Brian,
> > > > > > > >
> > > > > > > >   I meant first 2 ASPes will receive NTFY messages.Sendin=
g
NTFY
> > to
> > > > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > > > >
> > > > > > > > --Samuel
> > > > > > > >
> > > > > > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > >   ******* The opinions expressed are not those of Alcatel
USA,
> > Inc. *******
> > > > > > > >
> > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > >
> > > > > > > > > Samuel,
> > > > > > > > >
> > > > > > > > > None of the ASPs are handling traffic at that point.  W=
ho
is
> > to say
> > > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.
Perhaps
> > ASP2
> > > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP sure=
ly
> > doesn't know.
> > > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest
choice.
> > > > > > > > >
> > > > > > > > > --brian
> > > > > > > > >
> > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > >
> > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > >
> > > > > > > > > > In n+k reduntancy case,when n=3D2 that means ASP1 and=
 ASP2
are
> > going to
> > > > > > > > > > handle the traffic.So sending NTFY to these ASPes is
> > mandatory.
> > > > > > > > > > Sending NTFY to ASP3 is an optional because it is not
going
> > to handle
> > > > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 wil=
l
come
> > up to take
> > > > > > > > > > over the traffic this case SGP will send a NTFY messa=
ge
with
> > AS state,
> > > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > > >
> > > > > > > > > > --Samuel
> > > > > > > > > >
> > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > >   ******* The opinions expressed are not those of
Alcatel
> > USA, Inc. *******
> > > > > > > > > >
> > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > >
> > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > From the new definition of AS-INACTIVE in sec 4.3.2=
 of
> > > > > > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>,
the AS
> > becomes
> > > > > > > > > > > AS-INACTIVE when there are at least n ASPs in eithe=
r
> > ASP-INACTIVE or
> > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > >
> > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE wh=
en
SGP
> > receives two ASP
> > > > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP
receives
> > ASP UP from ASP3,
> > > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I
want to
> > know whether it
> > > > > > > > > > > is optional or not?
> > > > > > > > > > >
> > > > > > > > > > > Thanks.
> > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > >
> > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > >
> > > > > > > > > > > NTFY(AS-INACT) is sent to all all available peer
ASPes.
> > > > > > > > > > > Note: Available peer means an ASP which received
> > ASP-UP-ACK
> > > > > > > > > > > in response to ASP-UP messages.(as per RFC section
> > 4.3.4.1).
> > > > > > > > > > >
> > > > > > > > > > > If you active the AS as soon as a single ASP goes t=
o
> > ASP-INACT
> > > > > > > > > > > state then it is obvious that whoever sends ASP-UP
message
> > to
> > > > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to =
the
> > concern
> > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --Samuel
> > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > >   ******* The opinions expressed are not those of
Alcatel
> > USA, Inc. *******
> > > > > > > > > > >
> > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Hi all,
> > > > > > > > > > > >
> > > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP shou=
ld
> > immediately send
> > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. =
Is
this
> > right?
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks
> > > > > > > > > > > >
> > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
> > <d86942004@ntu.edu.tw>;
> > > > > > > > > > > "sigtran"
> > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Brian,
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > >
> > > > > > > > > > > > > But I think that we agreed that it would be wis=
e
to
> > tell newly inactive
> > > > > > > > > > >
> >   ------------------
> > > > > > > > > > > > > ASPs that state of the AS.  Also, in the diagra=
m,
the
> > state of the AS
> > > > > > > > > > > >   -------------------------
> > > > > > > > > > > >
> > > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY w=
ill
be
> > sent to all ASPes
> > > > > > > > > > > > (other than DOWN-ASPes) pertaining to the same RC=
.
> > > > > > > > > > > > This is what i remember that everybody agreed.
> > > > > > > > > > > >
> > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > does not change with the second ASP (ASP2) send=
ing
> > ASPUP.  The AS
> > > > > > > > > > > changes
> > > > > > > > > > > > > state to AS-INACTIVE with ASP1 coming up.
Therefore,
> > the diagram should
> > > > > > > > > > > > > show a NOTIFY(AS-INACTIVE) being sent to each A=
SP
> > immediately after the
> > > > > > > > > > > > > ASPUP Ack is sent to the ASP in question.
> > > > > > > > > > > > >
> > > > > > > > > > > > > The diagram is quite wrong.  Also it is wrong
> > considering the changes to
> > > > > > > > > > > > > be made to the next issue of the IG.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --brian
> > > > > > > > > > > > >
> > > > > > > > > > > > > kakaul@hss.hns.com wrote:
> > > > > > > > > > > > (Tue, 05 Aug 2003 09:31:47)
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On receiving ASPUP message from ASP3 state of=
 AS
> > does not change, so
> > > > > > > > > > > > > > NOTIFY(AS-INACTIVE) is not send to ASP3.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Kamesh
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > "Ling-Chih Kao" <d86942004@ntu.edu.tw>@ietf.o=
rg
on
> > 08/04/2003 11:40:01
> > > > > > > > > > > > AM
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Sent by:    sigtran-admin@ietf.org
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > To:    "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > > cc:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Subject:    [Sigtran] question about m3UA
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Should=A0ASP3 in the Section 5.1.4 of
> > > > > > > > > > > > > >
<draft-ietf-sigtran-m3ua-implementors-guide-04.txt>
> > receive
> > > > > > > > > > > > > > NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanls
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > _____________________________________________=
__
> > > > > > > > > > > > > > Sigtran mailing list
> > > > > > > > > > > > > > Sigtran@ietf.org
> > > > > > > > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtra=
n
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > > > > > bidulock@openss7.org
> > > > > > > > > > > > > http://www.openss7.org/
> > > > > > > > > > > > >
> > > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > > 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
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > 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
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Brian F. G. Bidulock
> > > > > > > > > bidulock@openss7.org
> > > > > > > > > http://www.openss7.org/
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > Sigtran mailing list
> > > > > > > > Sigtran@ietf.org
> > > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > >
> > > > > > > --
> > > > > > > Brian F. G. Bidulock
> > > > > > > bidulock@openss7.org
> > > > > > > http://www.openss7.org/
> > > > > > >
> > > > > > >
> > > > >
> > > > > --
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >
> > > > >
> > >
> > > --
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > >
> > > _______________________________________________
> > > 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
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>
>


_______________________________________________
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



From exim@www1.ietf.org  Wed Aug 13 03:24:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11148
	for <sigtran-archive@odin.ietf.org>; Wed, 13 Aug 2003 03:24:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mpzK-0002ks-KT
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 03:24:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7D7O6wh010570
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 03:24:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mpzF-0002kH-M3; Wed, 13 Aug 2003 03:24:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mpyi-0002jj-9j
	for sigtran@optimus.ietf.org; Wed, 13 Aug 2003 03:23:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11137
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 03:23:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mpyg-0007Iq-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 03:23:26 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[eiZqL3lE/mgS21eAdd+y618BLjDm+tUM])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mpyf-0007In-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 03:23:25 -0400
Received: from ns.pigworks.openss7.net (IDENT:Rhq5PNbn11OAWTYOgsGaKJFkK1emUAwo@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h7D7NKE29287;
	Wed, 13 Aug 2003 01:23:20 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h7D7NJh09848;
	Wed, 13 Aug 2003 01:23:19 -0600
Date: Wed, 13 Aug 2003 01:23:19 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Ling-Chih Kao <d86942004@ntu.edu.tw>
Cc: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
Message-ID: <20030813012319.A8783@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Ling-Chih Kao <d86942004@ntu.edu.tw>,
	"Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran <sigtran@ietf.org>
References: <Pine.SOL.4.10.10308122304030.8235-100000@sun2685.ssd.usa.alcatel.com> <006f01c3615b$228537e0$6ec5900a@saoe.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <006f01c3615b$228537e0$6ec5900a@saoe.com>; from d86942004@ntu.edu.tw on Wed, Aug 13, 2003 at 01:24:07PM +0800
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Ling-Chih,

Ling-Chih Kao wrote:                                                             (Wed, 13 Aug 2003 13:24:07)
> Hi, Samuel
> 
> 1.
> ASP3  in Sec. 5.1.4 did not send ASP Act. to SGP; however,  it  received
> NOTIFY (AS-ACTIVE).
> 
> This NOTIFY is also optional whether ASP3 send ASP Act. to SGP or not.
> That's right ?

No.  That notify is mandatory.

> 
> Should ASP3 send  ASP Act. to SGP?
> 
> 2.
> Should ASP3 send  ASP UP to SGP?
> 
> If ASP3 did not sent ASP UP to SGP, reception of NOTIFY(AS-INACTIVE) is also
> optional. Or, ASP3 will not receive  NOTIFY(AS-INACTIVE) because ASP3 does
> not sent ASP UP to SGP.

Notify cannot be sent to ASPs in the ASP-DOWN state.

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Wed Aug 13 05:20:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13201
	for <sigtran-archive@odin.ietf.org>; Wed, 13 Aug 2003 05:20:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mrnY-00078k-EE
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 05:20:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7D9K46r027442
	for sigtran-archive@odin.ietf.org; Wed, 13 Aug 2003 05:20:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mrnV-00078P-QM; Wed, 13 Aug 2003 05:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19mrn0-00077o-PP
	for sigtran@optimus.ietf.org; Wed, 13 Aug 2003 05:19:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13179
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 05:19:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mrmx-0007nR-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 05:19:27 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mrmw-0007nC-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 05:19:26 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h7D9IuwC014466;
	Wed, 13 Aug 2003 04:18:57 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h7D9IH1C021155;
	Wed, 13 Aug 2003 04:18:17 -0500 (CDT)
Date: Wed, 13 Aug 2003 04:18:17 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Ling-Chih Kao <d86942004@ntu.edu.tw>
cc: bidulock@openss7.org, sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <006f01c3615b$228537e0$6ec5900a@saoe.com>
Message-ID: <Pine.SOL.4.10.10308130354190.8235-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>


Ling-Chih Kao,

On Wed, 13 Aug 2003, Ling-Chih Kao wrote:

> Hi, Samuel
> 
> 1.
> ASP3  in Sec. 5.1.4 did not send ASP Act. to SGP; however,  it  received
> NOTIFY (AS-ACTIVE).
> 
> This NOTIFY is also optional whether ASP3 send ASP Act. to SGP or not.
> That's right ?
> 
As per RFC it is mandatory.Basically NTFY has been used not only to 
reflect the AS state but also used like 'insufficent # of ASPs' to all
INACTIVE ASPs.
NTFY(AS-ACTIVE) - sending this to all INACTIVE-ASPs is mandatory as per
                  RFC, But i dont see any purpose here.

NTFY("Insuff # of ASPs) - sending this to all INACTIVE-ASPs is mandatory
                          because any of the INACTIVE-ASP will become ACT.

NTFY("AS-Pending") - sending this to all INACTIVE-ASPs is mandatory
                     because any of the INACTIVE-ASP will become ACT.
 
> Should ASP3 send  ASP Act. to SGP?
> 
In our example(n+k case), if n=2 then 2 ASPs(say ASP1 and ASP2) will send
ASP-ACT messages.But you can have a test case where you will be sending
ASP-ACT from ASP3, this case SGP will honour that ASP-ACT.But basically
'k' ASP is used for backup purpose so unless ASP1 or ASP2 goes down ASP3
will not be sending ASP3-ACT.

> 2.
> Should ASP3 send  ASP UP to SGP?
> 
Yes, because you make the backup ASP ready to a certain level so that
when any one of the ASCTIVE-ASP goes down, backup ASP will take minimum
time to take up the load.

> If ASP3 did not sent ASP UP to SGP, reception of NOTIFY(AS-INACTIVE) is also
> optional. Or, ASP3 will not receive  NOTIFY(AS-INACTIVE) because ASP3 does
> not sent ASP UP to SGP.
This already Brian has answered.NTFY will not be processed in DOWN state.

--Samuel
> 
> 
> Ling-Chih Kao
> 
> ----- Original Message -----
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran" <sigtran@ietf.org>
> Sent: Wednesday, August 13, 2003 12:27 PM
> Subject: Re: [Sigtran] question about m3UA
> 
> 
> 
> Brian,
>  If it is mandatory to send NTFY(AS-STATE) to all ASPes(other than down),
>  Why dont we send SS7 node availability status(like DUNA,DAVA,DRST...)
>  to all INACTIVE-ASPes?(because anyway when INACTIVE-ASP moves to ACTIVE
>  ASP, it should know the status of SS7 nodes but finally it was decided
>  that newly active ASP will send an DAUD and gets the SS7 node(s) status
>  or SGP may send SS7 node(s) status to the newly active ASP.)
>  This i suggested long back(i think you remeber) but you strongly opposed
>  it. Now you are partially true with my old arguments.
> 
> --Samuel
> 
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> 
> On Tue, 12 Aug 2003, Brian F. G. Bidulock wrote:
> 
> > Ling-Chih,
> >
> > Mandatory.  All ASP-INACTIVE ASPs for an AS receive notifications
> > of state change.  ASP3 is ASP-INACTIVE in this case and must receive
> > the notification.
> >
> > The contentious case is when an ASP (ASP3) becomes ASP-INACTIVE from
> > ASP-DOWN.  I believe that the SGP should notify the newly inactive
> > ASP of the current state of the AS (which it did not receive before).
> > Samuel thinks that they should somehow guess the state of the AS.
> >
> > --brian
> >
> > Ling-Chih Kao wrote:
> (Wed, 13 Aug 2003 08:55:25)
> > > Hi, Brian and Samuel
> > >
> > > The answer for both of you is different.
> > > See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not sent ASP
> Act.
> > > to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional or
> > > mandatory?
> > >
> > > Thanks
> > >
> > > Ling-Chih Kao
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran" <sigtran@ietf.org>
> > > Sent: Friday, August 08, 2003 6:08 PM
> > > Subject: Re: [Sigtran] question about m3UA
> > >
> > >
> > >
> > > Brian,
> > >  Huh, it is not an implementation dependent, rfc says
> > >  ASPs which are in that AS should coordinate among themselves the number
> > >  of active ASPs in the AS.So it is clear to SGP that first arrived
> > >  'n' ASPs will receive NTFY(AS-INACT) message.
> > >
> > >  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN state)
> > >  you are not restricted but it is not mandatory to send, thats what i
> > >  am saying from the beginning.
> > >
> > >  Keep IG as it is.
> > > --Samuel
> > >
> > >   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> *******
> > >
> > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > >
> > > > Samuel,
> > > >
> > > > Maybe clear to the ASPs depending on implementation, but not
> > > > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > > > used by any of the ASPs, why send it in the first place?
> > > > If it serves a purpose, it should be sent to all of them to avoid
> > > > the race condition.
> > > >
> > > > --brian
> > > >
> > > > Samuel Dur D. Jeyaseelan wrote:
> > > (Fri, 08 Aug 2003 04:36:50)
> > > > >
> > > > > Brian,
> > > > >  We all know that in n+k redundancy case that ASPes will coordinate
> > > > >  among themselves the number of active ASPs in the AS, here it is
> > > > >  clear that who is going to go to ACTIVE state then where is the
> > > > >  question of race condition?
> > > > >
> > > > > --Samuel
> > > > >
> > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> > > *******
> > > > >
> > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > >
> > > > > > Samuel,
> > > > > >
> > > > > > What if ASP1 and ASP3 receive it but ASP2 did not, just because
> > > > > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > > > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > > > > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > > > > > ASPs when they come up.  It should not be optional.  It is
> necessary
> > > > > > to proper interworking that this race be broken.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > (Fri, 08 Aug 2003 04:17:31)
> > > > > > >
> > > > > > > Brian,
> > > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively, but
> > > ASP1 and
> > > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT message,
> > > > > > >  here it is mandatory to send NTFY(AS-ACT) to both ASPes(ASP1
> and
> > > ASP3).
> > > > > > >
> > > > > > >  This is the reason i said it is an optional of sending
> > > NTFY(AS-INACT)
> > > > > > >  to 'n+1'th ASP.
> > > > > > >
> > > > > > > --Samuel
> > > > > > >
> > > > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > >   ******* The opinions expressed are not those of Alcatel USA,
> Inc.
> > > *******
> > > > > > >
> > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > >
> > > > > > > > Samuel,
> > > > > > > >
> > > > > > > > Yes, I have a problem, because it is a race condition.
> > > > > > > >
> > > > > > > > --brian
> > > > > > > >
> > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > (Fri, 08 Aug 2003 04:04:50)
> > > > > > > > >
> > > > > > > > > Brian,
> > > > > > > > >
> > > > > > > > >   I meant first 2 ASPes will receive NTFY messages.Sending
> NTFY
> > > to
> > > > > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > > > > >
> > > > > > > > > --Samuel
> > > > > > > > >
> > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > >   ******* The opinions expressed are not those of Alcatel
> USA,
> > > Inc. *******
> > > > > > > > >
> > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > >
> > > > > > > > > > Samuel,
> > > > > > > > > >
> > > > > > > > > > None of the ASPs are handling traffic at that point.  Who
> is
> > > to say
> > > > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.
> Perhaps
> > > ASP2
> > > > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP surely
> > > doesn't know.
> > > > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest
> choice.
> > > > > > > > > >
> > > > > > > > > > --brian
> > > > > > > > > >
> > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > > >
> > > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > > >
> > > > > > > > > > > In n+k reduntancy case,when n=2 that means ASP1 and ASP2
> are
> > > going to
> > > > > > > > > > > handle the traffic.So sending NTFY to these ASPes is
> > > mandatory.
> > > > > > > > > > > Sending NTFY to ASP3 is an optional because it is not
> going
> > > to handle
> > > > > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3 will
> come
> > > up to take
> > > > > > > > > > > over the traffic this case SGP will send a NTFY message
> with
> > > AS state,
> > > > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > > > >
> > > > > > > > > > > --Samuel
> > > > > > > > > > >
> > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > >   ******* The opinions expressed are not those of
> Alcatel
> > > USA, Inc. *******
> > > > > > > > > > >
> > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > From the new definition of AS-INACTIVE in sec 4.3.2 of
> > > > > > > > > > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>,
> the AS
> > > becomes
> > > > > > > > > > > > AS-INACTIVE when there are at least n ASPs in either
> > > ASP-INACTIVE or
> > > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > > >
> > > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE when
> SGP
> > > receives two ASP
> > > > > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP
> receives
> > > ASP UP from ASP3,
> > > > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I
> want to
> > > know whether it
> > > > > > > > > > > > is optional or not?
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks.
> > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > >
> > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > > >
> > > > > > > > > > > > NTFY(AS-INACT) is sent to all all available peer
> ASPes.
> > > > > > > > > > > > Note: Available peer means an ASP which received
> > > ASP-UP-ACK
> > > > > > > > > > > > in response to ASP-UP messages.(as per RFC section
> > > 4.3.4.1).
> > > > > > > > > > > >
> > > > > > > > > > > > If you active the AS as soon as a single ASP goes to
> > > ASP-INACT
> > > > > > > > > > > > state then it is obvious that whoever sends ASP-UP
> message
> > > to
> > > > > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to the
> > > concern
> > > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > --Samuel
> > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > >   ******* The opinions expressed are not those of
> Alcatel
> > > USA, Inc. *******
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > >
> > > > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP should
> > > immediately send
> > > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS. Is
> this
> > > right?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
> > > <d86942004@ntu.edu.tw>;
> > > > > > > > > > > > "sigtran"
> > > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Brian,
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > But I think that we agreed that it would be wise
> to
> > > tell newly inactive
> > > > > > > > > > > >
> > >   ------------------
> > > > > > > > > > > > > > ASPs that state of the AS.  Also, in the diagram,
> the
> > > state of the AS
> > > > > > > > > > > > >   -------------------------
> > > > > > > > > > > > >
> > > > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY will
> be
> > > sent to all ASPes
> > > > > > > > > > > > > (other than DOWN-ASPes) pertaining to the same RC
> 


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



From exim@www1.ietf.org  Thu Aug 14 17:05:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26927
	for <sigtran-archive@odin.ietf.org>; Thu, 14 Aug 2003 17:05:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19nPHO-0000FW-6I
	for sigtran-archive@odin.ietf.org; Thu, 14 Aug 2003 17:05:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7EL56xc000947
	for sigtran-archive@odin.ietf.org; Thu, 14 Aug 2003 17:05:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19nPHK-0000F0-Fh; Thu, 14 Aug 2003 17:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19msHm-0008OA-0R
	for sigtran@optimus.ietf.org; Wed, 13 Aug 2003 05:51:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14266
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 05:51:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19msHi-00009A-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 05:51:14 -0400
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19msHh-000097-00
	for sigtran@ietf.org; Wed, 13 Aug 2003 05:51:13 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h7D9pEu23197
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 11:51:14 +0200 (MEST)
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h7D9pEx20737
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 11:51:14 +0200 (MEST)
Received: from mchh253e.mchh.siemens.de (mchh253e.mchh.siemens.de [139.21.200.63])
	by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id LAA21457
	for <sigtran@ietf.org>; Wed, 13 Aug 2003 11:51:13 +0200 (MET DST)
Received: by mchh253e.mchh.siemens.de with Internet Mail Service (5.5.2653.19)
	id <QVGF9XRJ>; Wed, 13 Aug 2003 11:50:33 +0200
Message-ID: <79D5F4B2D775204D9C7852EE41C547739C0814@mchh2a1e.mchh.siemens.de>
From: Daghar Adel <adel.daghar@siemens.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Wed, 13 Aug 2003 11:50:32 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Subject: [Sigtran] Sigtran
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Hi Gentelmann,
please could you tell me where is the difference between Sigtran draft =
5 and Sigtran RFC3332.
does exist other draft numberapart from draft 5

Regards


gez. Adel Daghar
Adel Daghar                                 =20
Siemens AG
ICM N PG ES PLM A 2
St. Martin Stra=DFe
D-81541 M=FCnchen
fon:   +49 (0) 89 636 49083
fax:    +49 (0) 89 636 54319
mobil: +49 (0) 160 8860711
mailto:adel.daghar@siemens.com



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



From exim@www1.ietf.org  Thu Aug 14 21:01:09 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03278
	for <sigtran-archive@odin.ietf.org>; Thu, 14 Aug 2003 21:01:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19nSxP-0008Tf-93
	for sigtran-archive@odin.ietf.org; Thu, 14 Aug 2003 21:00:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7F10hmO032583
	for sigtran-archive@odin.ietf.org; Thu, 14 Aug 2003 21:00:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19nSwj-0008RP-KP; Thu, 14 Aug 2003 21:00:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19nSw8-0008QA-R8
	for sigtran@optimus.ietf.org; Thu, 14 Aug 2003 20:59:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03217
	for <sigtran@ietf.org>; Thu, 14 Aug 2003 20:59:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nSw6-0007HN-00
	for sigtran@ietf.org; Thu, 14 Aug 2003 20:59:22 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[LhqszzCL23TROPWGc44aF0Wrb2fCbIwM])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nSw5-0007HK-00
	for sigtran@ietf.org; Thu, 14 Aug 2003 20:59:21 -0400
Received: from ns.pigworks.openss7.net (IDENT:49sD4By+5L8xIdMmPQC6lgcK5rGnkdWO@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h7F0xK117012;
	Thu, 14 Aug 2003 18:59:20 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h7F0xKp11289;
	Thu, 14 Aug 2003 18:59:20 -0600
Date: Thu, 14 Aug 2003 18:59:19 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Daghar Adel <adel.daghar@siemens.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] Sigtran
Message-ID: <20030814185919.C11141@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Daghar Adel <adel.daghar@siemens.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <79D5F4B2D775204D9C7852EE41C547739C0814@mchh2a1e.mchh.siemens.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <79D5F4B2D775204D9C7852EE41C547739C0814@mchh2a1e.mchh.siemens.de>; from adel.daghar@siemens.com on Wed, Aug 13, 2003 at 11:50:32AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h7F0xK117012
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Daghar,

There are a lot of changes.  To numerous to count.  Whoever (and I
think we know who we are talking about) made permanent reference to
an IETF draft didn't consider the IETF warnings concerning making
reference to IETF drafts as other that "Work in Progress".

Perhaps you should ask that body that made the references to Draft
5 to explain to you why they did that, and why they have not yet
corrected their blunder.

--brian

Daghar Adel wrote:                                                       =
           (Wed, 13 Aug 2003 11:50:32)
> Hi Gentelmann,
> please could you tell me where is the difference between Sigtran draft =
5 and Sigtran RFC3332.
> does exist other draft numberapart from draft 5
>=20
> Regards
>=20
>=20
> gez. Adel Daghar
> Adel Daghar                                 =20
> Siemens AG
> ICM N PG ES PLM A 2
> St. Martin Stra=DFe
> D-81541 M=FCnchen
> fon:   +49 (0) 89 636 49083
> fax:    +49 (0) 89 636 54319
> mobil: +49 (0) 160 8860711
> mailto:adel.daghar@siemens.com
>=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



From exim@www1.ietf.org  Fri Aug 15 19:56:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18128
	for <sigtran-archive@odin.ietf.org>; Fri, 15 Aug 2003 19:56:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19noQO-0003TI-D9
	for sigtran-archive@odin.ietf.org; Fri, 15 Aug 2003 19:56:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7FNu4fe013340
	for sigtran-archive@odin.ietf.org; Fri, 15 Aug 2003 19:56:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19noQK-0003Sn-MP; Fri, 15 Aug 2003 19:56:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19noPQ-0003Oo-L6
	for sigtran@optimus.ietf.org; Fri, 15 Aug 2003 19:55:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18103
	for <sigtran@ietf.org>; Fri, 15 Aug 2003 19:55:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19noPO-0006wm-00
	for sigtran@ietf.org; Fri, 15 Aug 2003 19:55:02 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19noPJ-0006wh-00
	for sigtran@ietf.org; Fri, 15 Aug 2003 19:54:57 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h7FNsQB3024125;
	Fri, 15 Aug 2003 18:54:26 -0500 (CDT)
Message-ID: <3F3D72B2.8050007@alcatel.com>
Date: Fri, 15 Aug 2003 18:54:26 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M2PA Last Call Comment - RPO
References: <3F15C7F2.6070704@pt.com> <20030716191143.F6725@openss7.org> <3F18328D.1080706@pt.com> <20030718120053.C14760@openss7.org> <3F184959.2040103@pt.com> <20030718133957.A16698@openss7.org> <3F1867CB.6060108@pt.com> <20030724134845.D11627@openss7.org> <3F26BAA2.1080908@pt.com> <3F29983B.2040505@alcatel.com> <20030731165031.A6734@openss7.org> <3F2ACB8B.7090806@pt.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Brian, Andrew, et. al.,

Here is my attempt to incorporate all of the comments from this thread. 
I may have missed some comments, so please take a look and see if I 
missed everything. I tried to cover for both cases - where the M2PA in 
RPO could and could not pass messages to MTP3.

tomG.

Revised section 4.1.4:
=====
4.1.4 Processor Outage

The Link Status Processor Outage message replaces the SIPO message of
MTP2. Unlike MTP2, the message SHOULD NOT be transmitted
continuously. M2PA SHALL send a Link Status Processor Outage message
to its peer at the beginning of a processor outage condition where
MTP2 would send SIPO. M2PA MAY send additional Link Status Processor
Outage messages as long as that condition persists.

When the local processor outage condition ends, M2PA SHALL send a Link
Status Processor Recovered message to its peer. This message is used
to signal the end of the processor outage condition, instead of an MSU
or FISU as in MTP2. The BSN in the Link Status Processor Recovered
message is set to the FSN of the last User Data message received from
the peer M2PA. The BSN value in the Link Status Processor Recovered
message is used by the peer to resynchronize its sequence numbers, if
this is required by MTP2.

While in a local processor outage condition:

    (a) Any User Data messages received from the peer MUST NOT be
        acknowledged and MUST be buffered.

    (b) M2PA SHOULD continue to acknowledge User Data messages received
        and accepted by MTP3 before the local processor outage.

While there is a remote processor outage condition:

    (a) M2PA SHOULD continue to acknowledge User Data messages received
        and accepted by MTP3 regardless of the remote processor outage.

    (b) If any User Data messages received from the peer after the Link
        Status Processor Outage cannot be delivered to MTP3, then these
        messages MUST NOT be acknowledged and MUST be buffered.

If M2PA receives a Flush command from MTP3, M2PA SHALL discard any
incoming messages that were queued and unacknowledged during the
processor outage condition.

Furthermore, if the M2PA experiencing processor outage receives a
Flush command,

    (a) M2PA SHALL NOT discard messages from the transmit and
        retransmit queues.

    (b) M2PA SHALL NOT perform procedures to resynchronize sequence
        numbers.

    (c) M2PA SHALL continue normal transmission of User Data.

If the M2PA experiencing remote processor outage receives a Flush
command,

    (a) M2PA SHALL discard messages in the transmit and retransmit
        queues as required by MTP2.

    (b) M2PA MAY perform resynchronization of sequence numbers using
        the BSN from the received Link Status Processor Recovered
        message.  However, during resychronization, M2PA SHALL NOT
        discard any received User Data messages.

Note that because the Link Status and User Data messages are sent on
separate streams, it is possible for a User Data message sent after
the Link Status Processor Recovered message to arrive before
it. Therefore, when flushing buffers, M2PA must take care not to flush
messages sent after the remote processor recovered. M2PA SHOULD NOT
flush User Data messages with FSN greater than the FSN in the Link
Status Processor Recovered message.

If M2PA receives a Continue command from MTP3, M2PA SHALL begin
processing the incoming messages that were queued and unacknowledged
during the processor outage condition.

When M2PA experiences a local processor outage, it MAY put the link
out of service by sending a Link Status Out of Service message if
allowed by the applicable MTP2 standard (e.g., [Q.2140]).

In other respects, M2PA SHOULD follow the same procedures as MTP2 in
processor outage.

=====


Here is the previous section 4.1.4 for reference:
=====
4.1.4 Processor Outage

The Link Status Processor Outage message replaces the SIPO message of
MTP2. Unlike MTP2, the message SHOULD NOT be transmitted
continuously. M2PA SHALL send a Link Status Processor Outage message
to its peer at the beginning of a processor outage condition where
MTP2 would send SIPO. M2PA MAY send additional Link Status Processor
Outage messages as long as that condition persists.

When the local processor outage condition ends, M2PA SHALL send a Link
Status Processor Recovered message to its peer. This message is used
to signal the end of the processor outage condition, instead of an MSU
or FISU as in MTP2. The BSN in the Link Status Processor Recovered
message is set to the FSN of the last User Data message received from
the peer M2PA. The BSN value in the Link Status Processor Recovered
message is used by the peer to resynchronize its sequence numbers, if
this is required by MTP2.

While in a local processor outage condition:

    (a) Any User Data messages received from the peer MUST NOT be
        acknowledged and MUST be buffered.

    (b) M2PA SHOULD continue to acknowledge User Data messages received
        and accepted by MTP3 before the local processor outage.

While there is a remote processor outage condition:

    (a) Any User Data messages received from the peer after the Link
        Status Processor Outage MUST NOT be acknowledged and MUST be
        buffered.

    (b) M2PA SHOULD continue to acknowledge User Data messages received
        and accepted by MTP3 before the remote processor outage.

If M2PA receives a Flush command from MTP3, M2PA SHALL discard the
incoming messages that were queued and unacknowledged during the
processor outage condition. Furthermore, M2PA SHALL discard messages
in the transmit and retransmit queues as required by MTP2.

Note that because the Link Status and User Data messages are sent on
separate streams, it is possible for a User Data message sent after
the Link Status Processor Recovered message to arrive before
it. Therefore, when flushing buffers, M2PA must take care not to flush
messages sent after the remote processor recovered. M2PA SHOULD NOT
flush User Data messages with FSN greater than the FSN in the Link
Status Processor Recovered message.

If M2PA receives a Continue command from MTP3, M2PA SHALL begin
processing the incoming messages that were queued and unacknowledged
during the processor outage condition.

In other respects, M2PA SHOULD follow the same procedures as MTP2 in
processor outage.

=====

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
*   I actively disclaim speaking for Alcatel.  I do not purport to    *
*   advertise or represent its position, operations, or activities.   *


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



From exim@www1.ietf.org  Mon Aug 18 13:19:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26359
	for <sigtran-archive@odin.ietf.org>; Mon, 18 Aug 2003 13:19:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ones-0005NB-8L
	for sigtran-archive@odin.ietf.org; Mon, 18 Aug 2003 13:19:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7IHJ6wR020632
	for sigtran-archive@odin.ietf.org; Mon, 18 Aug 2003 13:19:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19onem-0005LV-Pn; Mon, 18 Aug 2003 13:19:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ondp-0005JU-9f
	for sigtran@optimus.ietf.org; Mon, 18 Aug 2003 13:18:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26324
	for <sigtran@ietf.org>; Mon, 18 Aug 2003 13:17:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ondn-00010H-00
	for sigtran@ietf.org; Mon, 18 Aug 2003 13:17:59 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ondm-000107-00
	for sigtran@ietf.org; Mon, 18 Aug 2003 13:17:58 -0400
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h7IHHQuG002008
	for <sigtran@ietf.org>; Mon, 18 Aug 2003 10:17:27 -0700 (PDT)
Received: from kmorneau-w2k01.cisco.com (rtp-vpn2-49.cisco.com [10.82.240.49])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AKM61244;
	Mon, 18 Aug 2003 10:17:25 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030818131437.02433788@cia.cisco.com>
X-Sender: kmorneau@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 18 Aug 2003 13:17:23 -0400
To: sigtran@ietf.org
From: Ken Morneault <kmorneau@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [Sigtran] Sigtran Plugtest Test Specifications
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>



All:

The M2UA, IUA and SUA test specifications have been updated and
are posted at the ETSI site.  These updates are corrections, clarifications
and additions to the previous specifications.  

Please take some time to review them.

Regards,

Ken


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



From exim@www1.ietf.org  Tue Aug 19 05:14:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02458
	for <sigtran-archive@odin.ietf.org>; Tue, 19 Aug 2003 05:14:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p2Z1-0005FY-LA
	for sigtran-archive@odin.ietf.org; Tue, 19 Aug 2003 05:14:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7J9E3GJ020174
	for sigtran-archive@odin.ietf.org; Tue, 19 Aug 2003 05:14:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p2Yz-0005F4-DI; Tue, 19 Aug 2003 05:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p2Yv-0005Eq-9x
	for sigtran@optimus.ietf.org; Tue, 19 Aug 2003 05:13:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02451
	for <sigtran@ietf.org>; Tue, 19 Aug 2003 05:13:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p2Ys-00064s-00
	for sigtran@ietf.org; Tue, 19 Aug 2003 05:13:54 -0400
Received: from relay5.tp1rc.edu.tw ([163.28.16.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p2Yl-00064l-00
	for sigtran@ietf.org; Tue, 19 Aug 2003 05:13:49 -0400
Received: from KHL (61-219-40-1.HINET-IP.hinet.net [61.219.40.1])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by relay5.tp1rc.edu.tw (Postfix) with ESMTP
	id E3827106DAA; Tue, 19 Aug 2003 17:13:35 +0800 (CST)
Message-ID: <003101c36633$46b79ef0$6ec5900a@saoe.com>
From: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "sigtran" <sigtran@ietf.org>
References: <Pine.SOL.4.10.10308130354190.8235-100000@sun2685.ssd.usa.alcatel.com>
Subject: Re: [Sigtran] question about m3UA
Date: Tue, 19 Aug 2003 17:21:30 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi, Samuel

You mentioned that NTFY("AS-Pending") - sending this to all INACTIVE-ASPs is
mandatory because any of the INACTIVE-ASP will become ACT.
However, from the definition of M3UA Implementor's Guide, it said that
"AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to
   ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started
   and all incoming signalling messages SHOULD be queued by the SGP. If
   an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the
   AS-ACTIVE state and all the queued messages will be sent to the ASP".

ASP3 overrides ASP1 when ASP1 want to withdraw (example in sec. 5.2.3 (2+1
redundancy model)).The AS still has an active ASP (ASP2). Why did SGP send
NTFY("AS-Pending") to all ASPs? Are this wrong?

As mentioned in sec. 5.2.1 of  RFC 3332, how did SGP instruct which ASP
should send ASP Active to SGP  when SGP M3UA layer detects the loss of  the
peer M3UA?

As mentioned in sec. 5.2.2 of RFC 3332, What is the reason for ASP2 to
override ASP1 ? How did ASP2 know to send ASP Active to SGP? When the model
is 2+2 redundancy model, there are two backup ASPs, which ASP will override
original ASP?

Ling-Chih Kao

----- Original Message -----
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
Cc: <bidulock@openss7.org>; "sigtran" <sigtran@ietf.org>
Sent: Wednesday, August 13, 2003 5:18 PM
Subject: Re: [Sigtran] question about m3UA


>
> Ling-Chih Kao,
>
> On Wed, 13 Aug 2003, Ling-Chih Kao wrote:
>
> > Hi, Samuel
> >
> > 1.
> > ASP3  in Sec. 5.1.4 did not send ASP Act. to SGP; however,  it  received
> > NOTIFY (AS-ACTIVE).
> >
> > This NOTIFY is also optional whether ASP3 send ASP Act. to SGP or not.
> > That's right ?
> >
> As per RFC it is mandatory.Basically NTFY has been used not only to
> reflect the AS state but also used like 'insufficent # of ASPs' to all
> INACTIVE ASPs.
> NTFY(AS-ACTIVE) - sending this to all INACTIVE-ASPs is mandatory as per
>                   RFC, But i dont see any purpose here.
>
> NTFY("Insuff # of ASPs) - sending this to all INACTIVE-ASPs is mandatory
>                           because any of the INACTIVE-ASP will become ACT.
>
> NTFY("AS-Pending") - sending this to all INACTIVE-ASPs is mandatory
>                      because any of the INACTIVE-ASP will become ACT.
>
> > Should ASP3 send  ASP Act. to SGP?
> >
> In our example(n+k case), if n=2 then 2 ASPs(say ASP1 and ASP2) will send
> ASP-ACT messages.But you can have a test case where you will be sending
> ASP-ACT from ASP3, this case SGP will honour that ASP-ACT.But basically
> 'k' ASP is used for backup purpose so unless ASP1 or ASP2 goes down ASP3
> will not be sending ASP3-ACT.
>
> > 2.
> > Should ASP3 send  ASP UP to SGP?
> >
> Yes, because you make the backup ASP ready to a certain level so that
> when any one of the ASCTIVE-ASP goes down, backup ASP will take minimum
> time to take up the load.
>
> > If ASP3 did not sent ASP UP to SGP, reception of NOTIFY(AS-INACTIVE) is
also
> > optional. Or, ASP3 will not receive  NOTIFY(AS-INACTIVE) because ASP3
does
> > not sent ASP UP to SGP.
> This already Brian has answered.NTFY will not be processed in DOWN state.
>
> --Samuel
> >
> >
> > Ling-Chih Kao
> >
> > ----- Original Message -----
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran" <sigtran@ietf.org>
> > Sent: Wednesday, August 13, 2003 12:27 PM
> > Subject: Re: [Sigtran] question about m3UA
> >
> >
> >
> > Brian,
> >  If it is mandatory to send NTFY(AS-STATE) to all ASPes(other than
down),
> >  Why dont we send SS7 node availability status(like DUNA,DAVA,DRST...)
> >  to all INACTIVE-ASPes?(because anyway when INACTIVE-ASP moves to ACTIVE
> >  ASP, it should know the status of SS7 nodes but finally it was decided
> >  that newly active ASP will send an DAUD and gets the SS7 node(s) status

> >  or SGP may send SS7 node(s) status to the newly active ASP.)
> >  This i suggested long back(i think you remeber) but you strongly
opposed
> >  it. Now you are partially true with my old arguments.
> >
> > --Samuel
> >
> >   Alcatel USA, Inc.                  Internet:
<userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc.
*******
> >
> > On Tue, 12 Aug 2003, Brian F. G. Bidulock wrote:
> >
> > > Ling-Chih,
> > >
> > > Mandatory.  All ASP-INACTIVE ASPs for an AS receive notifications
> > > of state change.  ASP3 is ASP-INACTIVE in this case and must receive
> > > the notification.
> > >
> > > The contentious case is when an ASP (ASP3) becomes ASP-INACTIVE from
> > > ASP-DOWN.  I believe that the SGP should notify the newly inactive
> > > ASP of the current state of the AS (which it did not receive before).
> > > Samuel thinks that they should somehow guess the state of the AS.
> > >
> > > --brian
> > >
> > > Ling-Chih Kao wrote:
> > (Wed, 13 Aug 2003 08:55:25)
> > > > Hi, Brian and Samuel
> > > >
> > > > The answer for both of you is different.
> > > > See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not sent
ASP
> > Act.
> > > > to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional or
> > > > mandatory?
> > > >
> > > > Thanks
> > > >
> > > > Ling-Chih Kao
> > > >
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran"
<sigtran@ietf.org>
> > > > Sent: Friday, August 08, 2003 6:08 PM
> > > > Subject: Re: [Sigtran] question about m3UA
> > > >
> > > >
> > > >
> > > > Brian,
> > > >  Huh, it is not an implementation dependent, rfc says
> > > >  ASPs which are in that AS should coordinate among themselves the
number
> > > >  of active ASPs in the AS.So it is clear to SGP that first arrived
> > > >  'n' ASPs will receive NTFY(AS-INACT) message.
> > > >
> > > >  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN
state)
> > > >  you are not restricted but it is not mandatory to send, thats what
i
> > > >  am saying from the beginning.
> > > >
> > > >  Keep IG as it is.
> > > > --Samuel
> > > >
> > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> > *******
> > > >
> > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > >
> > > > > Samuel,
> > > > >
> > > > > Maybe clear to the ASPs depending on implementation, but not
> > > > > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > > > > used by any of the ASPs, why send it in the first place?
> > > > > If it serves a purpose, it should be sent to all of them to avoid
> > > > > the race condition.
> > > > >
> > > > > --brian
> > > > >
> > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > (Fri, 08 Aug 2003 04:36:50)
> > > > > >
> > > > > > Brian,
> > > > > >  We all know that in n+k redundancy case that ASPes will
coordinate
> > > > > >  among themselves the number of active ASPs in the AS, here it
is
> > > > > >  clear that who is going to go to ACTIVE state then where is the
> > > > > >  question of race condition?
> > > > > >
> > > > > > --Samuel
> > > > > >
> > > > > >   Alcatel USA, Inc.                  Internet:
> > > > <userid>@ssd.usa.alcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of Alcatel USA,
Inc.
> > > > *******
> > > > > >
> > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > >
> > > > > > > Samuel,
> > > > > > >
> > > > > > > What if ASP1 and ASP3 receive it but ASP2 did not, just
because
> > > > > > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > > > > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > > > > > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > > > > > > ASPs when they come up.  It should not be optional.  It is
> > necessary
> > > > > > > to proper interworking that this race be broken.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > (Fri, 08 Aug 2003 04:17:31)
> > > > > > > >
> > > > > > > > Brian,
> > > > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively,
but
> > > > ASP1 and
> > > > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT
message,
> > > > > > > >  here it is mandatory to send NTFY(AS-ACT) to both
ASPes(ASP1
> > and
> > > > ASP3).
> > > > > > > >
> > > > > > > >  This is the reason i said it is an optional of sending
> > > > NTFY(AS-INACT)
> > > > > > > >  to 'n+1'th ASP.
> > > > > > > >
> > > > > > > > --Samuel
> > > > > > > >
> > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > <userid>@ssd.usa.alcatel.com
> > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > >   ******* The opinions expressed are not those of Alcatel
USA,
> > Inc.
> > > > *******
> > > > > > > >
> > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > >
> > > > > > > > > Samuel,
> > > > > > > > >
> > > > > > > > > Yes, I have a problem, because it is a race condition.
> > > > > > > > >
> > > > > > > > > --brian
> > > > > > > > >
> > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > (Fri, 08 Aug 2003 04:04:50)
> > > > > > > > > >
> > > > > > > > > > Brian,
> > > > > > > > > >
> > > > > > > > > >   I meant first 2 ASPes will receive NTFY
messages.Sending
> > NTFY
> > > > to
> > > > > > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > > > > > >
> > > > > > > > > > --Samuel
> > > > > > > > > >
> > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > >   ******* The opinions expressed are not those of
Alcatel
> > USA,
> > > > Inc. *******
> > > > > > > > > >
> > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > >
> > > > > > > > > > > Samuel,
> > > > > > > > > > >
> > > > > > > > > > > None of the ASPs are handling traffic at that point.
Who
> > is
> > > > to say
> > > > > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.
> > Perhaps
> > > > ASP2
> > > > > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP
surely
> > > > doesn't know.
> > > > > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest
> > choice.
> > > > > > > > > > >
> > > > > > > > > > > --brian
> > > > > > > > > > >
> > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > > > >
> > > > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > > > >
> > > > > > > > > > > > In n+k reduntancy case,when n=2 that means ASP1 and
ASP2
> > are
> > > > going to
> > > > > > > > > > > > handle the traffic.So sending NTFY to these ASPes is
> > > > mandatory.
> > > > > > > > > > > > Sending NTFY to ASP3 is an optional because it is
not
> > going
> > > > to handle
> > > > > > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3
will
> > come
> > > > up to take
> > > > > > > > > > > > over the traffic this case SGP will send a NTFY
message
> > with
> > > > AS state,
> > > > > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > > > > >
> > > > > > > > > > > > --Samuel
> > > > > > > > > > > >
> > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > >   ******* The opinions expressed are not those of
> > Alcatel
> > > > USA, Inc. *******
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > From the new definition of AS-INACTIVE in sec
4.3.2 of
> > > > > > > > > > > > >
draft-ietf-sigtran-m3ua-implementors-guide-04.txt>,
> > the AS
> > > > becomes
> > > > > > > > > > > > > AS-INACTIVE when there are at least n ASPs in
either
> > > > ASP-INACTIVE or
> > > > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE
when
> > SGP
> > > > receives two ASP
> > > > > > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP
> > receives
> > > > ASP UP from ASP3,
> > > > > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I
> > want to
> > > > know whether it
> > > > > > > > > > > > > is optional or not?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks.
> > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > >
> > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > > > >
> > > > > > > > > > > > > NTFY(AS-INACT) is sent to all all available peer
> > ASPes.
> > > > > > > > > > > > > Note: Available peer means an ASP which received
> > > > ASP-UP-ACK
> > > > > > > > > > > > > in response to ASP-UP messages.(as per RFC section
> > > > 4.3.4.1).
> > > > > > > > > > > > >
> > > > > > > > > > > > > If you active the AS as soon as a single ASP goes
to
> > > > ASP-INACT
> > > > > > > > > > > > > state then it is obvious that whoever sends ASP-UP
> > message
> > > > to
> > > > > > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to
the
> > > > concern
> > > > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > >   ******* The opinions expressed are not those of
> > Alcatel
> > > > USA, Inc. *******
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP
should
> > > > immediately send
> > > > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS.
Is
> > this
> > > > right?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanks
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > To: "Brian F. G. Bidulock"
<bidulock@openss7.org>
> > > > > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
> > > > <d86942004@ntu.edu.tw>;
> > > > > > > > > > > > > "sigtran"
> > > > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Brian,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > But I think that we agreed that it would be
wise
> > to
> > > > tell newly inactive
> > > > > > > > > > > > >
> > > >   ------------------
> > > > > > > > > > > > > > > ASPs that state of the AS.  Also, in the
diagram,
> > the
> > > > state of the AS
> > > > > > > > > > > > > >   -------------------------
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY
will
> > be
> > > > sent to all ASPes
> > > > > > > > > > > > > > (other than DOWN-ASPes) pertaining to the same
RC
> >
>


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



From exim@www1.ietf.org  Tue Aug 19 08:00:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06020
	for <sigtran-archive@odin.ietf.org>; Tue, 19 Aug 2003 08:00:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p59f-0001WA-VM
	for sigtran-archive@odin.ietf.org; Tue, 19 Aug 2003 08:00:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7JC03mK005828
	for sigtran-archive@odin.ietf.org; Tue, 19 Aug 2003 08:00:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p59d-0001Vl-Mt; Tue, 19 Aug 2003 08:00:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p58r-0001Uo-Bk
	for sigtran@optimus.ietf.org; Tue, 19 Aug 2003 07:59:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05987
	for <sigtran@ietf.org>; Tue, 19 Aug 2003 07:58:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p58e-0006wu-00
	for sigtran@ietf.org; Tue, 19 Aug 2003 07:59:00 -0400
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p58d-0006wl-00
	for sigtran@ietf.org; Tue, 19 Aug 2003 07:58:59 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h7JBwRLX000150;
	Tue, 19 Aug 2003 06:58:27 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h7JBwI1C017739;
	Tue, 19 Aug 2003 06:58:18 -0500 (CDT)
Date: Tue, 19 Aug 2003 06:58:17 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Ling-Chih Kao <d86942004@ntu.edu.tw>
cc: sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <003101c36633$46b79ef0$6ec5900a@saoe.com>
Message-ID: <Pine.SOL.4.10.10308190549300.3976-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>


Ling-Chih Kao,

comments in-line.

On Tue, 19 Aug 2003, Ling-Chih Kao wrote:

> Hi, Samuel
> 
> You mentioned that NTFY("AS-Pending") - sending this to all INACTIVE-ASPs is
> mandatory because any of the INACTIVE-ASP will become ACT.
> However, from the definition of M3UA Implementor's Guide, it said that
> "AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to
>    ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started
>    and all incoming signalling messages SHOULD be queued by the SGP. If
>    an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the
>    AS-ACTIVE state and all the queued messages will be sent to the ASP".
> 
> ASP3 overrides ASP1 when ASP1 want to withdraw (example in sec. 5.2.3 (2+1
> redundancy model)).The AS still has an active ASP (ASP2). Why did SGP send
> NTFY("AS-Pending") to all ASPs? Are this wrong?

NTFY(AS-Pending) is sent only when the final ACTIVE ASP goes down.
How do you say ASP2 is ACTIVE?

> 
> As mentioned in sec. 5.2.1 of  RFC 3332, how did SGP instruct which ASP
> should send ASP Active to SGP  when SGP M3UA layer detects the loss of  the
> peer M3UA?
My understanding is , it is not the SGP which instructs which ASP to
come-up, but it is the craft person's local database configuration at 
Application Server side.

If SGP detects loss of peer M3UA layer (may be ASP1 does not respond with
heartbeat-ack)SGP will send a NTFY message to ASP2 so that ASP2 will
become ACTIVE.

> 
> As mentioned in sec. 5.2.2 of RFC 3332, What is the reason for ASP2 to
> override ASP1 ? How did ASP2 know to send ASP Active to SGP? When the model
> is 2+2 redundancy model, there are two backup ASPs, which ASP will override
> original ASP?

What is the reason for ASP2 to override ASP1 ? 
See, everything is controlled by a craft means via configured database.
Say for example, traffic is smooth between SGP1 and ASP1 but after some
time craft wants to do some kind of databse modification at ASP1 so he
make ASP2 to send the ASP-ACTIVE, Is this ok?

All qtns are answered above with respect to local database configuration
at Application Server.

> Ling-Chih Kao
> 
> ----- Original Message -----
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> Cc: <bidulock@openss7.org>; "sigtran" <sigtran@ietf.org>
> Sent: Wednesday, August 13, 2003 5:18 PM
> Subject: Re: [Sigtran] question about m3UA
> 
> 
> >
> > Ling-Chih Kao,
> >
> > On Wed, 13 Aug 2003, Ling-Chih Kao wrote:
> >
> > > Hi, Samuel
> > >
> > > 1.
> > > ASP3  in Sec. 5.1.4 did not send ASP Act. to SGP; however,  it  received
> > > NOTIFY (AS-ACTIVE).
> > >
> > > This NOTIFY is also optional whether ASP3 send ASP Act. to SGP or not.
> > > That's right ?
> > >
> > As per RFC it is mandatory.Basically NTFY has been used not only to
> > reflect the AS state but also used like 'insufficent # of ASPs' to all
> > INACTIVE ASPs.
> > NTFY(AS-ACTIVE) - sending this to all INACTIVE-ASPs is mandatory as per
> >                   RFC, But i dont see any purpose here.
> >
> > NTFY("Insuff # of ASPs) - sending this to all INACTIVE-ASPs is mandatory
> >                           because any of the INACTIVE-ASP will become ACT.
> >
> > NTFY("AS-Pending") - sending this to all INACTIVE-ASPs is mandatory
> >                      because any of the INACTIVE-ASP will become ACT.
> >
> > > Should ASP3 send  ASP Act. to SGP?
> > >
> > In our example(n+k case), if n=2 then 2 ASPs(say ASP1 and ASP2) will send
> > ASP-ACT messages.But you can have a test case where you will be sending
> > ASP-ACT from ASP3, this case SGP will honour that ASP-ACT.But basically
> > 'k' ASP is used for backup purpose so unless ASP1 or ASP2 goes down ASP3
> > will not be sending ASP3-ACT.
> >
> > > 2.
> > > Should ASP3 send  ASP UP to SGP?
> > >
> > Yes, because you make the backup ASP ready to a certain level so that
> > when any one of the ASCTIVE-ASP goes down, backup ASP will take minimum
> > time to take up the load.
> >
> > > If ASP3 did not sent ASP UP to SGP, reception of NOTIFY(AS-INACTIVE) is
> also
> > > optional. Or, ASP3 will not receive  NOTIFY(AS-INACTIVE) because ASP3
> does
> > > not sent ASP UP to SGP.
> > This already Brian has answered.NTFY will not be processed in DOWN state.
> >
> > --Samuel
> > >
> > >
> > > Ling-Chih Kao
> > >
> > > ----- Original Message -----
> > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran" <sigtran@ietf.org>
> > > Sent: Wednesday, August 13, 2003 12:27 PM
> > > Subject: Re: [Sigtran] question about m3UA
> > >
> > >
> > >
> > > Brian,
> > >  If it is mandatory to send NTFY(AS-STATE) to all ASPes(other than
> down),
> > >  Why dont we send SS7 node availability status(like DUNA,DAVA,DRST...)
> > >  to all INACTIVE-ASPes?(because anyway when INACTIVE-ASP moves to ACTIVE
> > >  ASP, it should know the status of SS7 nodes but finally it was decided
> > >  that newly active ASP will send an DAUD and gets the SS7 node(s) status
> 
> > >  or SGP may send SS7 node(s) status to the newly active ASP.)
> > >  This i suggested long back(i think you remeber) but you strongly
> opposed
> > >  it. Now you are partially true with my old arguments.
> > >
> > > --Samuel
> > >
> > >   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> *******
> > >
> > > On Tue, 12 Aug 2003, Brian F. G. Bidulock wrote:
> > >
> > > > Ling-Chih,
> > > >
> > > > Mandatory.  All ASP-INACTIVE ASPs for an AS receive notifications
> > > > of state change.  ASP3 is ASP-INACTIVE in this case and must receive
> > > > the notification.
> > > >
> > > > The contentious case is when an ASP (ASP3) becomes ASP-INACTIVE from
> > > > ASP-DOWN.  I believe that the SGP should notify the newly inactive
> > > > ASP of the current state of the AS (which it did not receive before).
> > > > Samuel thinks that they should somehow guess the state of the AS.
> > > >
> > > > --brian
> > > >
> > > > Ling-Chih Kao wrote:
> > > (Wed, 13 Aug 2003 08:55:25)
> > > > > Hi, Brian and Samuel
> > > > >
> > > > > The answer for both of you is different.
> > > > > See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not sent
> ASP
> > > Act.
> > > > > to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional or
> > > > > mandatory?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Ling-Chih Kao
> > > > >
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran"
> <sigtran@ietf.org>
> > > > > Sent: Friday, August 08, 2003 6:08 PM
> > > > > Subject: Re: [Sigtran] question about m3UA
> > > > >
> > > > >
> > > > >
> > > > > Brian,
> > > > >  Huh, it is not an implementation dependent, rfc says
> > > > >  ASPs which are in that AS should coordinate among themselves the
> number
> > > > >  of active ASPs in the AS.So it is clear to SGP that first arrived
> > > > >  'n' ASPs will receive NTFY(AS-INACT) message.
> > > > >
> > > > >  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN
> state)
> > > > >  you are not restricted but it is not mandatory to send, thats what
> i
> > > > >  am saying from the beginning.
> > > > >
> > > > >  Keep IG as it is.
> > > > > --Samuel
> > > > >
> > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> > > *******
> > > > >
> > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > >
> > > > > > Samuel,
> > > > > >
> > > > > > Maybe clear to the ASPs depending on implementation, but not
> > > > > > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > > > > > used by any of the ASPs, why send it in the first place?
> > > > > > If it serves a purpose, it should be sent to all of them to avoid
> > > > > > the race condition.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > (Fri, 08 Aug 2003 04:36:50)
> > > > > > >
> > > > > > > Brian,
> > > > > > >  We all know that in n+k redundancy case that ASPes will
> coordinate
> > > > > > >  among themselves the number of active ASPs in the AS, here it
> is
> > > > > > >  clear that who is going to go to ACTIVE state then where is the
> > > > > > >  question of race condition?
> > > > > > >
> > > > > > > --Samuel
> > > > > > >
> > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > <userid>@ssd.usa.alcatel.com
> > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > >   ******* The opinions expressed are not those of Alcatel USA,
> Inc.
> > > > > *******
> > > > > > >
> > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > >
> > > > > > > > Samuel,
> > > > > > > >
> > > > > > > > What if ASP1 and ASP3 receive it but ASP2 did not, just
> because
> > > > > > > > ASP3's ASPUP arrived before ASP2's.  That is a race condition.
> > > > > > > > This is why it is wise (and "SHOULD" is appropriate) to avoid
> > > > > > > > the race condition by sending NTFY(AS-INACTIVVE) to all of the
> > > > > > > > ASPs when they come up.  It should not be optional.  It is
> > > necessary
> > > > > > > > to proper interworking that this race be broken.
> > > > > > > >
> > > > > > > > --brian
> > > > > > > >
> > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > (Fri, 08 Aug 2003 04:17:31)
> > > > > > > > >
> > > > > > > > > Brian,
> > > > > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message respectively,
> but
> > > > > ASP1 and
> > > > > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT
> message,
> > > > > > > > >  here it is mandatory to send NTFY(AS-ACT) to both
> ASPes(ASP1
> > > and
> > > > > ASP3).
> > > > > > > > >
> > > > > > > > >  This is the reason i said it is an optional of sending
> > > > > NTFY(AS-INACT)
> > > > > > > > >  to 'n+1'th ASP.
> > > > > > > > >
> > > > > > > > > --Samuel
> > > > > > > > >
> > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > >   ******* The opinions expressed are not those of Alcatel
> USA,
> > > Inc.
> > > > > *******
> > > > > > > > >
> > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > >
> > > > > > > > > > Samuel,
> > > > > > > > > >
> > > > > > > > > > Yes, I have a problem, because it is a race condition.
> > > > > > > > > >
> > > > > > > > > > --brian
> > > > > > > > > >
> > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > (Fri, 08 Aug 2003 04:04:50)
> > > > > > > > > > >
> > > > > > > > > > > Brian,
> > > > > > > > > > >
> > > > > > > > > > >   I meant first 2 ASPes will receive NTFY
> messages.Sending
> > > NTFY
> > > > > to
> > > > > > > > > > >   3rd ASP is an optional.Do you have any problem here?
> > > > > > > > > > >
> > > > > > > > > > > --Samuel
> > > > > > > > > > >
> > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > >   ******* The opinions expressed are not those of
> Alcatel
> > > USA,
> > > > > Inc. *******
> > > > > > > > > > >
> > > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Samuel,
> > > > > > > > > > > >
> > > > > > > > > > > > None of the ASPs are handling traffic at that point.
> Who
> > > is
> > > > > to say
> > > > > > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the 'k'.
> > > Perhaps
> > > > > ASP2
> > > > > > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP
> surely
> > > > > doesn't know.
> > > > > > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the wisest
> > > choice.
> > > > > > > > > > > >
> > > > > > > > > > > > --brian
> > > > > > > > > > > >
> > > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > > > > >
> > > > > > > > > > > > > In n+k reduntancy case,when n=2 that means ASP1 and
> ASP2
> > > are
> > > > > going to
> > > > > > > > > > > > > handle the traffic.So sending NTFY to these ASPes is
> > > > > mandatory.
> > > > > > > > > > > > > Sending NTFY to ASP3 is an optional because it is
> not
> > > going
> > > > > to handle
> > > > > > > > > > > > > the traffic.When ASP1 or ASP2 goes down then ASP3
> will
> > > come
> > > > > up to take
> > > > > > > > > > > > > over the traffic this case SGP will send a NTFY
> message
> > > with
> > > > > AS state,
> > > > > > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > >
> > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > >   ******* The opinions expressed are not those of
> > > Alcatel
> > > > > USA, Inc. *******
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > From the new definition of AS-INACTIVE in sec
> 4.3.2 of
> > > > > > > > > > > > > >
> draft-ietf-sigtran-m3ua-implementors-guide-04.txt>,
> > > the AS
> > > > > becomes
> > > > > > > > > > > > > > AS-INACTIVE when there are at least n ASPs in
> either
> > > > > ASP-INACTIVE or
> > > > > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes AS-INACTIVE
> when
> > > SGP
> > > > > receives two ASP
> > > > > > > > > > > > > > UP (from ASP1 and ASP2).  However, when the SGP
> > > receives
> > > > > ASP UP from ASP3,
> > > > > > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to ASP3. I
> > > want to
> > > > > know whether it
> > > > > > > > > > > > > > is optional or not?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanks.
> > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > NTFY(AS-INACT) is sent to all all available peer
> > > ASPes.
> > > > > > > > > > > > > > Note: Available peer means an ASP which received
> > > > > ASP-UP-ACK
> > > > > > > > > > > > > > in response to ASP-UP messages.(as per RFC section
> > > > > 4.3.4.1).
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > If you active the AS as soon as a single ASP goes
> to
> > > > > ASP-INACT
> > > > > > > > > > > > > > state then it is obvious that whoever sends ASP-UP
> > > message
> > > > > to
> > > > > > > > > > > > > > SGP, immediately SGP will send a NTFY(AS-INACT) to
> the
> > > > > concern
> > > > > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > > >   ******* The opinions expressed are not those of
> > > Alcatel
> > > > > USA, Inc. *******
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP
> should
> > > > > immediately send
> > > > > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same AS.
> Is
> > > this
> > > > > right?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thanks
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > > To: "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > > > > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
> > > > > <d86942004@ntu.edu.tw>;
> > > > > > > > > > > > > > "sigtran"
> > > > > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Brian,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > But I think that we agreed that it would be
> wise
> > > to
> > > > > tell newly inactive
> > > > > > > > > > > > > >
> > > > >   ------------------
> > > > > > > > > > > > > > > > ASPs that state of the AS.  Also, in the
> diagram,
> > > the
> > > > > state of the AS
> > > > > > > > > > > > > > >   -------------------------
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > > > Whenever AS state-change happens at SGP, a NTFY
> will
> > > be
> > > > > sent to all ASPes
> > > > > > > > > > > > > > > (other than DOWN-ASPes) pertaining to the same
> RC
> > >
> >
> 
> 


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



From exim@www1.ietf.org  Wed Aug 20 03:36:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27602
	for <sigtran-archive@odin.ietf.org>; Wed, 20 Aug 2003 03:36:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pNVp-0006sq-K4
	for sigtran-archive@odin.ietf.org; Wed, 20 Aug 2003 03:36:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7K7a9Qb026461
	for sigtran-archive@odin.ietf.org; Wed, 20 Aug 2003 03:36:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pNVh-0006sY-OB; Wed, 20 Aug 2003 03:36:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pNVM-0006rm-Ta
	for sigtran@optimus.ietf.org; Wed, 20 Aug 2003 03:35:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27566
	for <sigtran@ietf.org>; Wed, 20 Aug 2003 03:35:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pNVK-0005Yo-00
	for sigtran@ietf.org; Wed, 20 Aug 2003 03:35:38 -0400
Received: from relay5.tp1rc.edu.tw ([163.28.16.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pNVI-0005Yk-00
	for sigtran@ietf.org; Wed, 20 Aug 2003 03:35:36 -0400
Received: from KHL (61-219-40-1.HINET-IP.hinet.net [61.219.40.1])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by relay5.tp1rc.edu.tw (Postfix) with ESMTP
	id 2E4EE106B63; Wed, 20 Aug 2003 15:35:32 +0800 (CST)
Message-ID: <000701c366ee$c04da730$6ec5900a@saoe.com>
From: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "sigtran" <sigtran@ietf.org>
References: <Pine.SOL.4.10.10308190549300.3976-100000@sun2685.ssd.usa.alcatel.com>
Subject: Re: [Sigtran] question about m3UA
Date: Wed, 20 Aug 2003 15:43:14 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

 Samuel

The example in sec. 5.1.4 and 5.2.3 is for "2+1" sparing loadsharing case.
The original active ASP is ASP1 and ASP2. Later, ASP1 withdraws  and ASP3
overrides it. ASP2 is still active; therefore, not all ASPs go into ASP
inactive. Am I wrong?

In  the example of sec. 5.1.4  for "2+1" sparing loadsharing case, the
decision of  ASPs taking care traffic is still by a craft means via
configured database. (In this example, ASP1 and ASP2 take care traffic
first.)
Or, depend on which ASP send ASP active to SGP first?

Thanks

Ling-Chih Kao


----- Original Message -----
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
Cc: "sigtran" <sigtran@ietf.org>
Sent: Tuesday, August 19, 2003 7:58 PM
Subject: Re: [Sigtran] question about m3UA


>
> Ling-Chih Kao,
>
> comments in-line.
>
> On Tue, 19 Aug 2003, Ling-Chih Kao wrote:
>
> > Hi, Samuel
> >
> > You mentioned that NTFY("AS-Pending") - sending this to all
INACTIVE-ASPs is
> > mandatory because any of the INACTIVE-ASP will become ACT.
> > However, from the definition of M3UA Implementor's Guide, it said that
> > "AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to
> >    ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started
> >    and all incoming signalling messages SHOULD be queued by the SGP. If
> >    an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the
> >    AS-ACTIVE state and all the queued messages will be sent to the ASP".
> >
> > ASP3 overrides ASP1 when ASP1 want to withdraw (example in sec. 5.2.3
(2+1
> > redundancy model)).The AS still has an active ASP (ASP2). Why did SGP
send
> > NTFY("AS-Pending") to all ASPs? Are this wrong?
>
> NTFY(AS-Pending) is sent only when the final ACTIVE ASP goes down.
> How do you say ASP2 is ACTIVE?
>
> >
> > As mentioned in sec. 5.2.1 of  RFC 3332, how did SGP instruct which ASP
> > should send ASP Active to SGP  when SGP M3UA layer detects the loss of
the
> > peer M3UA?
> My understanding is , it is not the SGP which instructs which ASP to
> come-up, but it is the craft person's local database configuration at
> Application Server side.
>
> If SGP detects loss of peer M3UA layer (may be ASP1 does not respond with
> heartbeat-ack)SGP will send a NTFY message to ASP2 so that ASP2 will
> become ACTIVE.
>
> >
> > As mentioned in sec. 5.2.2 of RFC 3332, What is the reason for ASP2 to
> > override ASP1 ? How did ASP2 know to send ASP Active to SGP? When the
model
> > is 2+2 redundancy model, there are two backup ASPs, which ASP will
override
> > original ASP?
>
> What is the reason for ASP2 to override ASP1 ?
> See, everything is controlled by a craft means via configured database.
> Say for example, traffic is smooth between SGP1 and ASP1 but after some
> time craft wants to do some kind of databse modification at ASP1 so he
> make ASP2 to send the ASP-ACTIVE, Is this ok?
>
> All qtns are answered above with respect to local database configuration
> at Application Server.
>
> > Ling-Chih Kao
> >
> > ----- Original Message -----
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > Cc: <bidulock@openss7.org>; "sigtran" <sigtran@ietf.org>
> > Sent: Wednesday, August 13, 2003 5:18 PM
> > Subject: Re: [Sigtran] question about m3UA
> >
> >
> > >
> > > Ling-Chih Kao,
> > >
> > > On Wed, 13 Aug 2003, Ling-Chih Kao wrote:
> > >
> > > > Hi, Samuel
> > > >
> > > > 1.
> > > > ASP3  in Sec. 5.1.4 did not send ASP Act. to SGP; however,  it
received
> > > > NOTIFY (AS-ACTIVE).
> > > >
> > > > This NOTIFY is also optional whether ASP3 send ASP Act. to SGP or
not.
> > > > That's right ?
> > > >
> > > As per RFC it is mandatory.Basically NTFY has been used not only to
> > > reflect the AS state but also used like 'insufficent # of ASPs' to all
> > > INACTIVE ASPs.
> > > NTFY(AS-ACTIVE) - sending this to all INACTIVE-ASPs is mandatory as
per
> > >                   RFC, But i dont see any purpose here.
> > >
> > > NTFY("Insuff # of ASPs) - sending this to all INACTIVE-ASPs is
mandatory
> > >                           because any of the INACTIVE-ASP will become
ACT.
> > >
> > > NTFY("AS-Pending") - sending this to all INACTIVE-ASPs is mandatory
> > >                      because any of the INACTIVE-ASP will become ACT.
> > >
> > > > Should ASP3 send  ASP Act. to SGP?
> > > >
> > > In our example(n+k case), if n=2 then 2 ASPs(say ASP1 and ASP2) will
send
> > > ASP-ACT messages.But you can have a test case where you will be
sending
> > > ASP-ACT from ASP3, this case SGP will honour that ASP-ACT.But
basically
> > > 'k' ASP is used for backup purpose so unless ASP1 or ASP2 goes down
ASP3
> > > will not be sending ASP3-ACT.
> > >
> > > > 2.
> > > > Should ASP3 send  ASP UP to SGP?
> > > >
> > > Yes, because you make the backup ASP ready to a certain level so that
> > > when any one of the ASCTIVE-ASP goes down, backup ASP will take
minimum
> > > time to take up the load.
> > >
> > > > If ASP3 did not sent ASP UP to SGP, reception of NOTIFY(AS-INACTIVE)
is
> > also
> > > > optional. Or, ASP3 will not receive  NOTIFY(AS-INACTIVE) because
ASP3
> > does
> > > > not sent ASP UP to SGP.
> > > This already Brian has answered.NTFY will not be processed in DOWN
state.
> > >
> > > --Samuel
> > > >
> > > >
> > > > Ling-Chih Kao
> > > >
> > > > ----- Original Message -----
> > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran"
<sigtran@ietf.org>
> > > > Sent: Wednesday, August 13, 2003 12:27 PM
> > > > Subject: Re: [Sigtran] question about m3UA
> > > >
> > > >
> > > >
> > > > Brian,
> > > >  If it is mandatory to send NTFY(AS-STATE) to all ASPes(other than
> > down),
> > > >  Why dont we send SS7 node availability status(like
DUNA,DAVA,DRST...)
> > > >  to all INACTIVE-ASPes?(because anyway when INACTIVE-ASP moves to
ACTIVE
> > > >  ASP, it should know the status of SS7 nodes but finally it was
decided
> > > >  that newly active ASP will send an DAUD and gets the SS7 node(s)
status
> >
> > > >  or SGP may send SS7 node(s) status to the newly active ASP.)
> > > >  This i suggested long back(i think you remeber) but you strongly
> > opposed
> > > >  it. Now you are partially true with my old arguments.
> > > >
> > > > --Samuel
> > > >
> > > >   Alcatel USA, Inc.                  Internet:
> > <userid>@ssd.usa.alcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> > *******
> > > >
> > > > On Tue, 12 Aug 2003, Brian F. G. Bidulock wrote:
> > > >
> > > > > Ling-Chih,
> > > > >
> > > > > Mandatory.  All ASP-INACTIVE ASPs for an AS receive notifications
> > > > > of state change.  ASP3 is ASP-INACTIVE in this case and must
receive
> > > > > the notification.
> > > > >
> > > > > The contentious case is when an ASP (ASP3) becomes ASP-INACTIVE
from
> > > > > ASP-DOWN.  I believe that the SGP should notify the newly inactive
> > > > > ASP of the current state of the AS (which it did not receive
before).
> > > > > Samuel thinks that they should somehow guess the state of the AS.
> > > > >
> > > > > --brian
> > > > >
> > > > > Ling-Chih Kao wrote:
> > > > (Wed, 13 Aug 2003 08:55:25)
> > > > > > Hi, Brian and Samuel
> > > > > >
> > > > > > The answer for both of you is different.
> > > > > > See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not
sent
> > ASP
> > > > Act.
> > > > > > to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional
or
> > > > > > mandatory?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Ling-Chih Kao
> > > > > >
> > > > > >
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran"
> > <sigtran@ietf.org>
> > > > > > Sent: Friday, August 08, 2003 6:08 PM
> > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > >
> > > > > >
> > > > > >
> > > > > > Brian,
> > > > > >  Huh, it is not an implementation dependent, rfc says
> > > > > >  ASPs which are in that AS should coordinate among themselves
the
> > number
> > > > > >  of active ASPs in the AS.So it is clear to SGP that first
arrived
> > > > > >  'n' ASPs will receive NTFY(AS-INACT) message.
> > > > > >
> > > > > >  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN
> > state)
> > > > > >  you are not restricted but it is not mandatory to send, thats
what
> > i
> > > > > >  am saying from the beginning.
> > > > > >
> > > > > >  Keep IG as it is.
> > > > > > --Samuel
> > > > > >
> > > > > >   Alcatel USA, Inc.                  Internet:
> > > > <userid>@ssd.usa.alcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of Alcatel USA,
Inc.
> > > > *******
> > > > > >
> > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > >
> > > > > > > Samuel,
> > > > > > >
> > > > > > > Maybe clear to the ASPs depending on implementation, but not
> > > > > > > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > > > > > > used by any of the ASPs, why send it in the first place?
> > > > > > > If it serves a purpose, it should be sent to all of them to
avoid
> > > > > > > the race condition.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > (Fri, 08 Aug 2003 04:36:50)
> > > > > > > >
> > > > > > > > Brian,
> > > > > > > >  We all know that in n+k redundancy case that ASPes will
> > coordinate
> > > > > > > >  among themselves the number of active ASPs in the AS, here
it
> > is
> > > > > > > >  clear that who is going to go to ACTIVE state then where is
the
> > > > > > > >  question of race condition?
> > > > > > > >
> > > > > > > > --Samuel
> > > > > > > >
> > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > >   ******* The opinions expressed are not those of Alcatel
USA,
> > Inc.
> > > > > > *******
> > > > > > > >
> > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > >
> > > > > > > > > Samuel,
> > > > > > > > >
> > > > > > > > > What if ASP1 and ASP3 receive it but ASP2 did not, just
> > because
> > > > > > > > > ASP3's ASPUP arrived before ASP2's.  That is a race
condition.
> > > > > > > > > This is why it is wise (and "SHOULD" is appropriate) to
avoid
> > > > > > > > > the race condition by sending NTFY(AS-INACTIVVE) to all of
the
> > > > > > > > > ASPs when they come up.  It should not be optional.  It is
> > > > necessary
> > > > > > > > > to proper interworking that this race be broken.
> > > > > > > > >
> > > > > > > > > --brian
> > > > > > > > >
> > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > (Fri, 08 Aug 2003 04:17:31)
> > > > > > > > > >
> > > > > > > > > > Brian,
> > > > > > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message
respectively,
> > but
> > > > > > ASP1 and
> > > > > > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > > > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT
> > message,
> > > > > > > > > >  here it is mandatory to send NTFY(AS-ACT) to both
> > ASPes(ASP1
> > > > and
> > > > > > ASP3).
> > > > > > > > > >
> > > > > > > > > >  This is the reason i said it is an optional of sending
> > > > > > NTFY(AS-INACT)
> > > > > > > > > >  to 'n+1'th ASP.
> > > > > > > > > >
> > > > > > > > > > --Samuel
> > > > > > > > > >
> > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > >   ******* The opinions expressed are not those of
Alcatel
> > USA,
> > > > Inc.
> > > > > > *******
> > > > > > > > > >
> > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > >
> > > > > > > > > > > Samuel,
> > > > > > > > > > >
> > > > > > > > > > > Yes, I have a problem, because it is a race condition.
> > > > > > > > > > >
> > > > > > > > > > > --brian
> > > > > > > > > > >
> > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > (Fri, 08 Aug 2003 04:04:50)
> > > > > > > > > > > >
> > > > > > > > > > > > Brian,
> > > > > > > > > > > >
> > > > > > > > > > > >   I meant first 2 ASPes will receive NTFY
> > messages.Sending
> > > > NTFY
> > > > > > to
> > > > > > > > > > > >   3rd ASP is an optional.Do you have any problem
here?
> > > > > > > > > > > >
> > > > > > > > > > > > --Samuel
> > > > > > > > > > > >
> > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > >   ******* The opinions expressed are not those of
> > Alcatel
> > > > USA,
> > > > > > Inc. *******
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Samuel,
> > > > > > > > > > > > >
> > > > > > > > > > > > > None of the ASPs are handling traffic at that
point.
> > Who
> > > > is
> > > > > > to say
> > > > > > > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the
'k'.
> > > > Perhaps
> > > > > > ASP2
> > > > > > > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP
> > surely
> > > > > > doesn't know.
> > > > > > > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the
wisest
> > > > choice.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --brian
> > > > > > > > > > > > >
> > > > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > In n+k reduntancy case,when n=2 that means ASP1
and
> > ASP2
> > > > are
> > > > > > going to
> > > > > > > > > > > > > > handle the traffic.So sending NTFY to these
ASPes is
> > > > > > mandatory.
> > > > > > > > > > > > > > Sending NTFY to ASP3 is an optional because it
is
> > not
> > > > going
> > > > > > to handle
> > > > > > > > > > > > > > the traffic.When ASP1 or ASP2 goes down then
ASP3
> > will
> > > > come
> > > > > > up to take
> > > > > > > > > > > > > > over the traffic this case SGP will send a NTFY
> > message
> > > > with
> > > > > > AS state,
> > > > > > > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > > >   ******* The opinions expressed are not those
of
> > > > Alcatel
> > > > > > USA, Inc. *******
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > From the new definition of AS-INACTIVE in sec
> > 4.3.2 of
> > > > > > > > > > > > > > >
> > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>,
> > > > the AS
> > > > > > becomes
> > > > > > > > > > > > > > > AS-INACTIVE when there are at least n ASPs in
> > either
> > > > > > ASP-INACTIVE or
> > > > > > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes
AS-INACTIVE
> > when
> > > > SGP
> > > > > > receives two ASP
> > > > > > > > > > > > > > > UP (from ASP1 and ASP2).  However, when the
SGP
> > > > receives
> > > > > > ASP UP from ASP3,
> > > > > > > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to
ASP3. I
> > > > want to
> > > > > > know whether it
> > > > > > > > > > > > > > > is optional or not?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thanks.
> > > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > NTFY(AS-INACT) is sent to all all available
peer
> > > > ASPes.
> > > > > > > > > > > > > > > Note: Available peer means an ASP which
received
> > > > > > ASP-UP-ACK
> > > > > > > > > > > > > > > in response to ASP-UP messages.(as per RFC
section
> > > > > > 4.3.4.1).
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > If you active the AS as soon as a single ASP
goes
> > to
> > > > > > ASP-INACT
> > > > > > > > > > > > > > > state then it is obvious that whoever sends
ASP-UP
> > > > message
> > > > > > to
> > > > > > > > > > > > > > > SGP, immediately SGP will send a
NTFY(AS-INACT) to
> > the
> > > > > > concern
> > > > > > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > > > >   ******* The opinions expressed are not those
of
> > > > Alcatel
> > > > > > USA, Inc. *******
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP
> > should
> > > > > > immediately send
> > > > > > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same
AS.
> > Is
> > > > this
> > > > > > right?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Thanks
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > > > To: "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > > > > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
> > > > > > <d86942004@ntu.edu.tw>;
> > > > > > > > > > > > > > > "sigtran"
> > > > > > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Brian,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock
wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > But I think that we agreed that it would
be
> > wise
> > > > to
> > > > > > tell newly inactive
> > > > > > > > > > > > > > >
> > > > > >   ------------------
> > > > > > > > > > > > > > > > > ASPs that state of the AS.  Also, in the
> > diagram,
> > > > the
> > > > > > state of the AS
> > > > > > > > > > > > > > > >   -------------------------
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > > > > Whenever AS state-change happens at SGP, a
NTFY
> > will
> > > > be
> > > > > > sent to all ASPes
> > > > > > > > > > > > > > > > (other than DOWN-ASPes) pertaining to the
same
> > RC
> > > >
> > >
> >
> >
>
>
> _______________________________________________
> 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



From exim@www1.ietf.org  Wed Aug 20 11:56:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16670
	for <sigtran-archive@odin.ietf.org>; Wed, 20 Aug 2003 11:56:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pVJb-0003VQ-7y
	for sigtran-archive@odin.ietf.org; Wed, 20 Aug 2003 11:56:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7KFu3f5013470
	for sigtran-archive@odin.ietf.org; Wed, 20 Aug 2003 11:56:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pVJY-0003Um-Pe; Wed, 20 Aug 2003 11:56:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pVJ6-0003ND-EA
	for sigtran@optimus.ietf.org; Wed, 20 Aug 2003 11:55:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16612
	for <sigtran@ietf.org>; Wed, 20 Aug 2003 11:55:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pVJ5-0002kF-00
	for sigtran@ietf.org; Wed, 20 Aug 2003 11:55:31 -0400
Received: from ottgw.pt.com ([206.191.2.130] helo=pt.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pVJ4-0002k5-00
	for sigtran@ietf.org; Wed, 20 Aug 2003 11:55:30 -0400
Received: from pt.com (IDENT:root@localhost [127.0.0.1])
	by  pt.com (8.9.3/8.9.3) with ESMTP id LAA14876;
	Wed, 20 Aug 2003 11:51:11 -0400
Message-ID: <3F4399C2.6050104@pt.com>
Date: Wed, 20 Aug 2003 11:54:42 -0400
From: Andrew Booth <abooth@pt.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom George <Tom.George@alcatel.com>
CC: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M2PA Last Call Comment - RPO
References: <3F15C7F2.6070704@pt.com> <20030716191143.F6725@openss7.org> <3F18328D.1080706@pt.com> <20030718120053.C14760@openss7.org> <3F184959.2040103@pt.com> <20030718133957.A16698@openss7.org> <3F1867CB.6060108@pt.com> <20030724134845.D11627@openss7.org> <3F26BAA2.1080908@pt.com> <3F29983B.2040505@alcatel.com> <20030731165031.A6734@openss7.org> <3F2ACB8B.7090806@pt.com> <3F3D72B2.8050007@alcatel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi Tom,

Looks pretty good.  Some comments/questions below.

Tom George wrote:

> Brian, Andrew, et. al.,
>
> Here is my attempt to incorporate all of the comments from this 
> thread. I may have missed some comments, so please take a look and see 
> if I missed everything. I tried to cover for both cases - where the 
> M2PA in RPO could and could not pass messages to MTP3.

>
>
> tomG.
>
> Revised section 4.1.4:
> =====
> 4.1.4 Processor Outage
>
> The Link Status Processor Outage message replaces the SIPO message of
> MTP2. Unlike MTP2, the message SHOULD NOT be transmitted
> continuously. M2PA SHALL send a Link Status Processor Outage message
> to its peer at the beginning of a processor outage condition where
> MTP2 would send SIPO. M2PA MAY send additional Link Status Processor
> Outage messages as long as that condition persists.
>
> When the local processor outage condition ends, M2PA SHALL send a Link
> Status Processor Recovered message to its peer. This message is used
> to signal the end of the processor outage condition, instead of an MSU
> or FISU as in MTP2. The BSN in the Link Status Processor Recovered
> message is set to the FSN of the last User Data message received from
> the peer M2PA. The BSN value in the Link Status Processor Recovered
> message is used by the peer to resynchronize its sequence numbers, if
> this is required by MTP2.
>
> While in a local processor outage condition:
>
>    (a) Any User Data messages received from the peer MUST NOT be
>        acknowledged and MUST be buffered.
>
>    (b) M2PA SHOULD continue to acknowledge User Data messages received
>        and accepted by MTP3 before the local processor outage.
>
> While there is a remote processor outage condition:
>
>    (a) M2PA SHOULD continue to acknowledge User Data messages received
>        and accepted by MTP3 regardless of the remote processor outage.
>
>    (b) If any User Data messages received from the peer after the Link
>        Status Processor Outage cannot be delivered to MTP3, then these
>        messages MUST NOT be acknowledged and MUST be buffered.
>
> If M2PA receives a Flush command from MTP3, M2PA SHALL discard any
> incoming messages that were queued and unacknowledged during the
> processor outage condition.
>
> Furthermore, if the M2PA experiencing processor outage receives a
> Flush command,
>
>    (a) M2PA SHALL NOT discard messages from the transmit and
>        retransmit queues. 

Any messages still in the transmit/retransmit buffer when a flush is 
received are probably already stale and should be flushed.  This is 
particularly important if the remote end cannot ack the data for some 
reason, in which case data messages can get stuck in the TB/RTB for 
arbitrarily long times.
I think this proposal was based on the assumption that the remote end 
would ack the data in the TB/RTB so these queues would empty themselves 
anyway; however there are cases where the remote end might not be able 
to ack the data in the RTB so messages might get stuck in the TB/RTB.

>
>
>    (b) M2PA SHALL NOT perform procedures to resynchronize sequence
>        numbers.

I don't think resynchronization is necessary for either LPO or RPO, but 
I especially don't understand why it should be different between the two.

>
>
>    (c) M2PA SHALL continue normal transmission of User Data.
>
> If the M2PA experiencing remote processor outage receives a Flush
> command,
>
>    (a) M2PA SHALL discard messages in the transmit and retransmit
>        queues as required by MTP2.
>
>    (b) M2PA MAY perform resynchronization of sequence numbers using
>        the BSN from the received Link Status Processor Recovered
>        message.  However, during resychronization, M2PA SHALL NOT
>        discard any received User Data messages.

This confuses me a bit.  Is the idea is that we don't want to discard 
messages that were sent after processor outage, taking into account the 
multistreaming?  I assume we're still expected flush the receive buffer 
at some point?

Andrew

>
>
> Note that because the Link Status and User Data messages are sent on
> separate streams, it is possible for a User Data message sent after
> the Link Status Processor Recovered message to arrive before
> it. Therefore, when flushing buffers, M2PA must take care not to flush
> messages sent after the remote processor recovered. M2PA SHOULD NOT
> flush User Data messages with FSN greater than the FSN in the Link
> Status Processor Recovered message.
>
> If M2PA receives a Continue command from MTP3, M2PA SHALL begin
> processing the incoming messages that were queued and unacknowledged
> during the processor outage condition.
>
> When M2PA experiences a local processor outage, it MAY put the link
> out of service by sending a Link Status Out of Service message if
> allowed by the applicable MTP2 standard (e.g., [Q.2140]).
>
> In other respects, M2PA SHOULD follow the same procedures as MTP2 in
> processor outage.
>
> =====
>
>
> Here is the previous section 4.1.4 for reference:
> =====
> 4.1.4 Processor Outage
>
> The Link Status Processor Outage message replaces the SIPO message of
> MTP2. Unlike MTP2, the message SHOULD NOT be transmitted
> continuously. M2PA SHALL send a Link Status Processor Outage message
> to its peer at the beginning of a processor outage condition where
> MTP2 would send SIPO. M2PA MAY send additional Link Status Processor
> Outage messages as long as that condition persists.
>
> When the local processor outage condition ends, M2PA SHALL send a Link
> Status Processor Recovered message to its peer. This message is used
> to signal the end of the processor outage condition, instead of an MSU
> or FISU as in MTP2. The BSN in the Link Status Processor Recovered
> message is set to the FSN of the last User Data message received from
> the peer M2PA. The BSN value in the Link Status Processor Recovered
> message is used by the peer to resynchronize its sequence numbers, if
> this is required by MTP2.
>
> While in a local processor outage condition:
>
>    (a) Any User Data messages received from the peer MUST NOT be
>        acknowledged and MUST be buffered.
>
>    (b) M2PA SHOULD continue to acknowledge User Data messages received
>        and accepted by MTP3 before the local processor outage.
>
> While there is a remote processor outage condition:
>
>    (a) Any User Data messages received from the peer after the Link
>        Status Processor Outage MUST NOT be acknowledged and MUST be
>        buffered.
>
>    (b) M2PA SHOULD continue to acknowledge User Data messages received
>        and accepted by MTP3 before the remote processor outage.
>
> If M2PA receives a Flush command from MTP3, M2PA SHALL discard the
> incoming messages that were queued and unacknowledged during the
> processor outage condition. Furthermore, M2PA SHALL discard messages
> in the transmit and retransmit queues as required by MTP2.
>
> Note that because the Link Status and User Data messages are sent on
> separate streams, it is possible for a User Data message sent after
> the Link Status Processor Recovered message to arrive before
> it. Therefore, when flushing buffers, M2PA must take care not to flush
> messages sent after the remote processor recovered. M2PA SHOULD NOT
> flush User Data messages with FSN greater than the FSN in the Link
> Status Processor Recovered message.
>
> If M2PA receives a Continue command from MTP3, M2PA SHALL begin
> processing the incoming messages that were queued and unacknowledged
> during the processor outage condition.
>
> In other respects, M2PA SHOULD follow the same procedures as MTP2 in
> processor outage.
>
> =====
>

-- 
Andrew Booth, Software Developer
Signaling Systems Group, Performance Technologies
613-237-4344

Visit www.pt.com/mailing.html to subscribe to our Packets & Signals eLetter.



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



From exim@www1.ietf.org  Wed Aug 20 15:30:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03413
	for <sigtran-archive@odin.ietf.org>; Wed, 20 Aug 2003 15:30:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pYej-0007v1-Fk
	for sigtran-archive@odin.ietf.org; Wed, 20 Aug 2003 15:30:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7KJU5WS030439
	for sigtran-archive@odin.ietf.org; Wed, 20 Aug 2003 15:30:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pYeg-0007uK-3O; Wed, 20 Aug 2003 15:30:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pYeJ-0007t7-LV
	for sigtran@optimus.ietf.org; Wed, 20 Aug 2003 15:29:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03252
	for <sigtran@ietf.org>; Wed, 20 Aug 2003 15:29:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pYeI-00066H-00
	for sigtran@ietf.org; Wed, 20 Aug 2003 15:29:38 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pYeG-00065j-00
	for sigtran@ietf.org; Wed, 20 Aug 2003 15:29:37 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h7KJSpB3007639;
	Wed, 20 Aug 2003 14:28:52 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h7KJSO1C025147;
	Wed, 20 Aug 2003 14:28:28 -0500 (CDT)
Date: Wed, 20 Aug 2003 14:28:24 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Ling-Chih Kao <d86942004@ntu.edu.tw>
cc: sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <000701c366ee$c04da730$6ec5900a@saoe.com>
Message-ID: <Pine.SOL.4.10.10308201417530.17480-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>


Ling-Chih Kao,


On Wed, 20 Aug 2003, Ling-Chih Kao wrote:

>  Samuel
> 
> The example in sec. 5.1.4 and 5.2.3 is for "2+1" sparing loadsharing case.
> The original active ASP is ASP1 and ASP2. Later, ASP1 withdraws  and ASP3
> overrides it. ASP2 is still active; therefore, not all ASPs go into ASP
> inactive. Am I wrong?

You are correct. In section 5.2.3, SGP should not send NTFY(AS-PENDING) to
all ASP because ASP2 is alive(as you said).But SGP should send
NTFY(insuf-resources-at-AS) to INACTIVE-ASPes.

> 
> In  the example of sec. 5.1.4  for "2+1" sparing loadsharing case, the
> decision of  ASPs taking care traffic is still by a craft means via
> configured database. (In this example, ASP1 and ASP2 take care traffic
> first.)
> Or, depend on which ASP send ASP active to SGP first?

which ASP to send ASP-ACTIV to SGP first is also a part of database
configuration.

--Samuel
> 
> Thanks
> 
> Ling-Chih Kao
> 
> 
> ----- Original Message -----
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> Cc: "sigtran" <sigtran@ietf.org>
> Sent: Tuesday, August 19, 2003 7:58 PM
> Subject: Re: [Sigtran] question about m3UA
> 
> 
> >
> > Ling-Chih Kao,
> >
> > comments in-line.
> >
> > On Tue, 19 Aug 2003, Ling-Chih Kao wrote:
> >
> > > Hi, Samuel
> > >
> > > You mentioned that NTFY("AS-Pending") - sending this to all
> INACTIVE-ASPs is
> > > mandatory because any of the INACTIVE-ASP will become ACT.
> > > However, from the definition of M3UA Implementor's Guide, it said that
> > > "AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to
> > >    ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started
> > >    and all incoming signalling messages SHOULD be queued by the SGP. If
> > >    an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the
> > >    AS-ACTIVE state and all the queued messages will be sent to the ASP".
> > >
> > > ASP3 overrides ASP1 when ASP1 want to withdraw (example in sec. 5.2.3
> (2+1
> > > redundancy model)).The AS still has an active ASP (ASP2). Why did SGP
> send
> > > NTFY("AS-Pending") to all ASPs? Are this wrong?
> >
> > NTFY(AS-Pending) is sent only when the final ACTIVE ASP goes down.
> > How do you say ASP2 is ACTIVE?
> >
> > >
> > > As mentioned in sec. 5.2.1 of  RFC 3332, how did SGP instruct which ASP
> > > should send ASP Active to SGP  when SGP M3UA layer detects the loss of
> the
> > > peer M3UA?
> > My understanding is , it is not the SGP which instructs which ASP to
> > come-up, but it is the craft person's local database configuration at
> > Application Server side.
> >
> > If SGP detects loss of peer M3UA layer (may be ASP1 does not respond with
> > heartbeat-ack)SGP will send a NTFY message to ASP2 so that ASP2 will
> > become ACTIVE.
> >
> > >
> > > As mentioned in sec. 5.2.2 of RFC 3332, What is the reason for ASP2 to
> > > override ASP1 ? How did ASP2 know to send ASP Active to SGP? When the
> model
> > > is 2+2 redundancy model, there are two backup ASPs, which ASP will
> override
> > > original ASP?
> >
> > What is the reason for ASP2 to override ASP1 ?
> > See, everything is controlled by a craft means via configured database.
> > Say for example, traffic is smooth between SGP1 and ASP1 but after some
> > time craft wants to do some kind of databse modification at ASP1 so he
> > make ASP2 to send the ASP-ACTIVE, Is this ok?
> >
> > All qtns are answered above with respect to local database configuration
> > at Application Server.
> >
> > > Ling-Chih Kao
> > >
> > > ----- Original Message -----
> > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > Cc: <bidulock@openss7.org>; "sigtran" <sigtran@ietf.org>
> > > Sent: Wednesday, August 13, 2003 5:18 PM
> > > Subject: Re: [Sigtran] question about m3UA
> > >
> > >
> > > >
> > > > Ling-Chih Kao,
> > > >
> > > > On Wed, 13 Aug 2003, Ling-Chih Kao wrote:
> > > >
> > > > > Hi, Samuel
> > > > >
> > > > > 1.
> > > > > ASP3  in Sec. 5.1.4 did not send ASP Act. to SGP; however,  it
> received
> > > > > NOTIFY (AS-ACTIVE).
> > > > >
> > > > > This NOTIFY is also optional whether ASP3 send ASP Act. to SGP or
> not.
> > > > > That's right ?
> > > > >
> > > > As per RFC it is mandatory.Basically NTFY has been used not only to
> > > > reflect the AS state but also used like 'insufficent # of ASPs' to all
> > > > INACTIVE ASPs.
> > > > NTFY(AS-ACTIVE) - sending this to all INACTIVE-ASPs is mandatory as
> per
> > > >                   RFC, But i dont see any purpose here.
> > > >
> > > > NTFY("Insuff # of ASPs) - sending this to all INACTIVE-ASPs is
> mandatory
> > > >                           because any of the INACTIVE-ASP will become
> ACT.
> > > >
> > > > NTFY("AS-Pending") - sending this to all INACTIVE-ASPs is mandatory
> > > >                      because any of the INACTIVE-ASP will become ACT.
> > > >
> > > > > Should ASP3 send  ASP Act. to SGP?
> > > > >
> > > > In our example(n+k case), if n=2 then 2 ASPs(say ASP1 and ASP2) will
> send
> > > > ASP-ACT messages.But you can have a test case where you will be
> sending
> > > > ASP-ACT from ASP3, this case SGP will honour that ASP-ACT.But
> basically
> > > > 'k' ASP is used for backup purpose so unless ASP1 or ASP2 goes down
> ASP3
> > > > will not be sending ASP3-ACT.
> > > >
> > > > > 2.
> > > > > Should ASP3 send  ASP UP to SGP?
> > > > >
> > > > Yes, because you make the backup ASP ready to a certain level so that
> > > > when any one of the ASCTIVE-ASP goes down, backup ASP will take
> minimum
> > > > time to take up the load.
> > > >
> > > > > If ASP3 did not sent ASP UP to SGP, reception of NOTIFY(AS-INACTIVE)
> is
> > > also
> > > > > optional. Or, ASP3 will not receive  NOTIFY(AS-INACTIVE) because
> ASP3
> > > does
> > > > > not sent ASP UP to SGP.
> > > > This already Brian has answered.NTFY will not be processed in DOWN
> state.
> > > >
> > > > --Samuel
> > > > >
> > > > >
> > > > > Ling-Chih Kao
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran"
> <sigtran@ietf.org>
> > > > > Sent: Wednesday, August 13, 2003 12:27 PM
> > > > > Subject: Re: [Sigtran] question about m3UA
> > > > >
> > > > >
> > > > >
> > > > > Brian,
> > > > >  If it is mandatory to send NTFY(AS-STATE) to all ASPes(other than
> > > down),
> > > > >  Why dont we send SS7 node availability status(like
> DUNA,DAVA,DRST...)
> > > > >  to all INACTIVE-ASPes?(because anyway when INACTIVE-ASP moves to
> ACTIVE
> > > > >  ASP, it should know the status of SS7 nodes but finally it was
> decided
> > > > >  that newly active ASP will send an DAUD and gets the SS7 node(s)
> status
> > >
> > > > >  or SGP may send SS7 node(s) status to the newly active ASP.)
> > > > >  This i suggested long back(i think you remeber) but you strongly
> > > opposed
> > > > >  it. Now you are partially true with my old arguments.
> > > > >
> > > > > --Samuel
> > > > >
> > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> > > *******
> > > > >
> > > > > On Tue, 12 Aug 2003, Brian F. G. Bidulock wrote:
> > > > >
> > > > > > Ling-Chih,
> > > > > >
> > > > > > Mandatory.  All ASP-INACTIVE ASPs for an AS receive notifications
> > > > > > of state change.  ASP3 is ASP-INACTIVE in this case and must
> receive
> > > > > > the notification.
> > > > > >
> > > > > > The contentious case is when an ASP (ASP3) becomes ASP-INACTIVE
> from
> > > > > > ASP-DOWN.  I believe that the SGP should notify the newly inactive
> > > > > > ASP of the current state of the AS (which it did not receive
> before).
> > > > > > Samuel thinks that they should somehow guess the state of the AS.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > Ling-Chih Kao wrote:
> > > > > (Wed, 13 Aug 2003 08:55:25)
> > > > > > > Hi, Brian and Samuel
> > > > > > >
> > > > > > > The answer for both of you is different.
> > > > > > > See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not
> sent
> > > ASP
> > > > > Act.
> > > > > > > to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional
> or
> > > > > > > mandatory?
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Ling-Chih Kao
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ----- Original Message -----
> > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran"
> > > <sigtran@ietf.org>
> > > > > > > Sent: Friday, August 08, 2003 6:08 PM
> > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Brian,
> > > > > > >  Huh, it is not an implementation dependent, rfc says
> > > > > > >  ASPs which are in that AS should coordinate among themselves
> the
> > > number
> > > > > > >  of active ASPs in the AS.So it is clear to SGP that first
> arrived
> > > > > > >  'n' ASPs will receive NTFY(AS-INACT) message.
> > > > > > >
> > > > > > >  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN
> > > state)
> > > > > > >  you are not restricted but it is not mandatory to send, thats
> what
> > > i
> > > > > > >  am saying from the beginning.
> > > > > > >
> > > > > > >  Keep IG as it is.
> > > > > > > --Samuel
> > > > > > >
> > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > <userid>@ssd.usa.alcatel.com
> > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > >   ******* The opinions expressed are not those of Alcatel USA,
> Inc.
> > > > > *******
> > > > > > >
> > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > >
> > > > > > > > Samuel,
> > > > > > > >
> > > > > > > > Maybe clear to the ASPs depending on implementation, but not
> > > > > > > > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > > > > > > > used by any of the ASPs, why send it in the first place?
> > > > > > > > If it serves a purpose, it should be sent to all of them to
> avoid
> > > > > > > > the race condition.
> > > > > > > >
> > > > > > > > --brian
> > > > > > > >
> > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > (Fri, 08 Aug 2003 04:36:50)
> > > > > > > > >
> > > > > > > > > Brian,
> > > > > > > > >  We all know that in n+k redundancy case that ASPes will
> > > coordinate
> > > > > > > > >  among themselves the number of active ASPs in the AS, here
> it
> > > is
> > > > > > > > >  clear that who is going to go to ACTIVE state then where is
> the
> > > > > > > > >  question of race condition?
> > > > > > > > >
> > > > > > > > > --Samuel
> > > > > > > > >
> > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > >   ******* The opinions expressed are not those of Alcatel
> USA,
> > > Inc.
> > > > > > > *******
> > > > > > > > >
> > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > >
> > > > > > > > > > Samuel,
> > > > > > > > > >
> > > > > > > > > > What if ASP1 and ASP3 receive it but ASP2 did not, just
> > > because
> > > > > > > > > > ASP3's ASPUP arrived before ASP2's.  That is a race
> condition.
> > > > > > > > > > This is why it is wise (and "SHOULD" is appropriate) to
> avoid
> > > > > > > > > > the race condition by sending NTFY(AS-INACTIVVE) to all of
> the
> > > > > > > > > > ASPs when they come up.  It should not be optional.  It is
> > > > > necessary
> > > > > > > > > > to proper interworking that this race be broken.
> > > > > > > > > >
> > > > > > > > > > --brian
> > > > > > > > > >
> > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > (Fri, 08 Aug 2003 04:17:31)
> > > > > > > > > > >
> > > > > > > > > > > Brian,
> > > > > > > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message
> respectively,
> > > but
> > > > > > > ASP1 and
> > > > > > > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > > > > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT
> > > message,
> > > > > > > > > > >  here it is mandatory to send NTFY(AS-ACT) to both
> > > ASPes(ASP1
> > > > > and
> > > > > > > ASP3).
> > > > > > > > > > >
> > > > > > > > > > >  This is the reason i said it is an optional of sending
> > > > > > > NTFY(AS-INACT)
> > > > > > > > > > >  to 'n+1'th ASP.
> > > > > > > > > > >
> > > > > > > > > > > --Samuel
> > > > > > > > > > >
> > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > >   ******* The opinions expressed are not those of
> Alcatel
> > > USA,
> > > > > Inc.
> > > > > > > *******
> > > > > > > > > > >
> > > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Samuel,
> > > > > > > > > > > >
> > > > > > > > > > > > Yes, I have a problem, because it is a race condition.
> > > > > > > > > > > >
> > > > > > > > > > > > --brian
> > > > > > > > > > > >
> > > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > (Fri, 08 Aug 2003 04:04:50)
> > > > > > > > > > > > >
> > > > > > > > > > > > > Brian,
> > > > > > > > > > > > >
> > > > > > > > > > > > >   I meant first 2 ASPes will receive NTFY
> > > messages.Sending
> > > > > NTFY
> > > > > > > to
> > > > > > > > > > > > >   3rd ASP is an optional.Do you have any problem
> here?
> > > > > > > > > > > > >
> > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > >
> > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > >   ******* The opinions expressed are not those of
> > > Alcatel
> > > > > USA,
> > > > > > > Inc. *******
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Samuel,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > None of the ASPs are handling traffic at that
> point.
> > > Who
> > > > > is
> > > > > > > to say
> > > > > > > > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the
> 'k'.
> > > > > Perhaps
> > > > > > > ASP2
> > > > > > > > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP
> > > surely
> > > > > > > doesn't know.
> > > > > > > > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the
> wisest
> > > > > choice.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --brian
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > In n+k reduntancy case,when n=2 that means ASP1
> and
> > > ASP2
> > > > > are
> > > > > > > going to
> > > > > > > > > > > > > > > handle the traffic.So sending NTFY to these
> ASPes is
> > > > > > > mandatory.
> > > > > > > > > > > > > > > Sending NTFY to ASP3 is an optional because it
> is
> > > not
> > > > > going
> > > > > > > to handle
> > > > > > > > > > > > > > > the traffic.When ASP1 or ASP2 goes down then
> ASP3
> > > will
> > > > > come
> > > > > > > up to take
> > > > > > > > > > > > > > > over the traffic this case SGP will send a NTFY
> > > message
> > > > > with
> > > > > > > AS state,
> > > > > > > > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > > > >   ******* The opinions expressed are not those
> of
> > > > > Alcatel
> > > > > > > USA, Inc. *******
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > From the new definition of AS-INACTIVE in sec
> > > 4.3.2 of
> > > > > > > > > > > > > > > >
> > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>,
> > > > > the AS
> > > > > > > becomes
> > > > > > > > > > > > > > > > AS-INACTIVE when there are at least n ASPs in
> > > either
> > > > > > > ASP-INACTIVE or
> > > > > > > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes
> AS-INACTIVE
> > > when
> > > > > SGP
> > > > > > > receives two ASP
> > > > > > > > > > > > > > > > UP (from ASP1 and ASP2).  However, when the
> SGP
> > > > > receives
> > > > > > > ASP UP from ASP3,
> > > > > > > > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to
> ASP3. I
> > > > > want to
> > > > > > > know whether it
> > > > > > > > > > > > > > > > is optional or not?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Thanks.
> > > > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > NTFY(AS-INACT) is sent to all all available
> peer
> > > > > ASPes.
> > > > > > > > > > > > > > > > Note: Available peer means an ASP which
> received
> > > > > > > ASP-UP-ACK
> > > > > > > > > > > > > > > > in response to ASP-UP messages.(as per RFC
> section
> > > > > > > 4.3.4.1).
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > If you active the AS as soon as a single ASP
> goes
> > > to
> > > > > > > ASP-INACT
> > > > > > > > > > > > > > > > state then it is obvious that whoever sends
> ASP-UP
> > > > > message
> > > > > > > to
> > > > > > > > > > > > > > > > SGP, immediately SGP will send a
> NTFY(AS-INACT) to
> > > the
> > > > > > > concern
> > > > > > > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > > > > >   ******* The opinions expressed are not those
> of
> > > > > Alcatel
> > > > > > > USA, Inc. *******
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP
> > > should
> > > > > > > immediately send
> > > > > > > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same
> AS.
> > > Is
> > > > > this
> > > > > > > right?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Thanks
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > > > > To: "Brian F. G. Bidulock"
> > > <bidulock@openss7.org>
> > > > > > > > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
> > > > > > > <d86942004@ntu.edu.tw>;
> > > > > > > > > > > > > > > > "sigtran"
> > > > > > > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Brian,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock
> wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > But I think that we agreed that it would
> be
> > > wise
> > > > > to
> > > > > > > tell newly inactive
> > > > > > > > > > > > > > > >
> > > > > > >   ------------------
> > > > > > > > > > > > > > > > > > ASPs that state of the AS.  Also, in the
> > > diagram,
> > > > > the
> > > > > > > state of the AS
> > > > > > > > > > > > > > > > >   -------------------------
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > > > > > Whenever AS state-change happens at SGP, a
> NTFY
> > > will
> > > > > be
> > > > > > > sent to all ASPes
> > > > > > > > > > > > > > > > > (other than DOWN-ASPes) pertaining to the
> same
> > > RC
> > > > >
> > > >
> > >
> > >
> >
> >
> > _______________________________________________
> > 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



From exim@www1.ietf.org  Wed Aug 20 15:41:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05091
	for <sigtran-archive@odin.ietf.org>; Wed, 20 Aug 2003 15:41:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pYpJ-0000Zr-SD
	for sigtran-archive@odin.ietf.org; Wed, 20 Aug 2003 15:41:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7KJf1Su002218
	for sigtran-archive@odin.ietf.org; Wed, 20 Aug 2003 15:41:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pYpI-0000ZW-PD; Wed, 20 Aug 2003 15:41:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pYok-0000U0-BQ
	for sigtran@optimus.ietf.org; Wed, 20 Aug 2003 15:40:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04729
	for <sigtran@ietf.org>; Wed, 20 Aug 2003 15:40:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pYoi-0006U7-00
	for sigtran@ietf.org; Wed, 20 Aug 2003 15:40:24 -0400
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pYoh-0006S9-00
	for sigtran@ietf.org; Wed, 20 Aug 2003 15:40:23 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h7KJdpLX001842;
	Wed, 20 Aug 2003 14:39:52 -0500 (CDT)
Received: from sun2685.ssd.usa.alcatel.com (sun2685.ssd.usa.alcatel.com [143.209.151.167])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h7KJcv1C028329;
	Wed, 20 Aug 2003 14:38:57 -0500 (CDT)
Date: Wed, 20 Aug 2003 14:38:57 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Ling-Chih Kao <d86942004@ntu.edu.tw>
cc: sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] question about m3UA
In-Reply-To: <000701c366ee$c04da730$6ec5900a@saoe.com>
Message-ID: <Pine.SOL.4.10.10308201428420.17480-100000@sun2685.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>


Pastor,

IG section 5.1.4 and 5.2.3 are co-related, but section 5.2.3 diagram is
wrong because ASP2 is alive so SGP will send a NTFY(insuf-resources-at-AS)
to INACTIVE-ASPes.

Section 5.2.3 diagram should look like this

        SGP                 ASP1                ASP2                ASP3
          |                   |                   |                   |
          |<----ASP Inact.----|                   |                   |
          |---ASP Inact Ack-->|                   |                   |
          |                   |                   |                   |
          |NOTIFY(Ins. ASPs)->|                   |                   |
          |                   |                   |                   |
          |                   |                   |                   |
          |---------------------------------------NOTIFY(Ins. ASPs)-->|
          |                   |                   |                   |
          |                   |                   |                   |
          |<----------------------------------------ASP Act (Ldshr)---|
          |------------------------------------------ASP Act (Ack)--->|
          |                   |                   |                   |
          |-NTFY(AS-ACTIVE)-->|                   |                   |
          |-------------------NOTIFY(AS-ACTIVE)-->|                   |
          |---------------------------------------NOTIFY(AS-ACTIVE)-->|
          |                   |                   |                   |
          |                   |                   |                   |


Did you remeber this, we discussed few months back that in n+k reduntancy
case SGP should not stop the traffic until 'n' becomes zero.

--Samuel

On Wed, 20 Aug 2003, Ling-Chih Kao wrote:

>  Samuel
> 
> The example in sec. 5.1.4 and 5.2.3 is for "2+1" sparing loadsharing case.
> The original active ASP is ASP1 and ASP2. Later, ASP1 withdraws  and ASP3
> overrides it. ASP2 is still active; therefore, not all ASPs go into ASP
> inactive. Am I wrong?
> 
> In  the example of sec. 5.1.4  for "2+1" sparing loadsharing case, the
> decision of  ASPs taking care traffic is still by a craft means via
> configured database. (In this example, ASP1 and ASP2 take care traffic
> first.)
> Or, depend on which ASP send ASP active to SGP first?
> 
> Thanks
> 
> Ling-Chih Kao
> 
> 
> ----- Original Message -----
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> Cc: "sigtran" <sigtran@ietf.org>
> Sent: Tuesday, August 19, 2003 7:58 PM
> Subject: Re: [Sigtran] question about m3UA
> 
> 
> >
> > Ling-Chih Kao,
> >
> > comments in-line.
> >
> > On Tue, 19 Aug 2003, Ling-Chih Kao wrote:
> >
> > > Hi, Samuel
> > >
> > > You mentioned that NTFY("AS-Pending") - sending this to all
> INACTIVE-ASPs is
> > > mandatory because any of the INACTIVE-ASP will become ACT.
> > > However, from the definition of M3UA Implementor's Guide, it said that
> > > "AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to
> > >    ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started
> > >    and all incoming signalling messages SHOULD be queued by the SGP. If
> > >    an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the
> > >    AS-ACTIVE state and all the queued messages will be sent to the ASP".
> > >
> > > ASP3 overrides ASP1 when ASP1 want to withdraw (example in sec. 5.2.3
> (2+1
> > > redundancy model)).The AS still has an active ASP (ASP2). Why did SGP
> send
> > > NTFY("AS-Pending") to all ASPs? Are this wrong?
> >
> > NTFY(AS-Pending) is sent only when the final ACTIVE ASP goes down.
> > How do you say ASP2 is ACTIVE?
> >
> > >
> > > As mentioned in sec. 5.2.1 of  RFC 3332, how did SGP instruct which ASP
> > > should send ASP Active to SGP  when SGP M3UA layer detects the loss of
> the
> > > peer M3UA?
> > My understanding is , it is not the SGP which instructs which ASP to
> > come-up, but it is the craft person's local database configuration at
> > Application Server side.
> >
> > If SGP detects loss of peer M3UA layer (may be ASP1 does not respond with
> > heartbeat-ack)SGP will send a NTFY message to ASP2 so that ASP2 will
> > become ACTIVE.
> >
> > >
> > > As mentioned in sec. 5.2.2 of RFC 3332, What is the reason for ASP2 to
> > > override ASP1 ? How did ASP2 know to send ASP Active to SGP? When the
> model
> > > is 2+2 redundancy model, there are two backup ASPs, which ASP will
> override
> > > original ASP?
> >
> > What is the reason for ASP2 to override ASP1 ?
> > See, everything is controlled by a craft means via configured database.
> > Say for example, traffic is smooth between SGP1 and ASP1 but after some
> > time craft wants to do some kind of databse modification at ASP1 so he
> > make ASP2 to send the ASP-ACTIVE, Is this ok?
> >
> > All qtns are answered above with respect to local database configuration
> > at Application Server.
> >
> > > Ling-Chih Kao
> > >
> > > ----- Original Message -----
> > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > Cc: <bidulock@openss7.org>; "sigtran" <sigtran@ietf.org>
> > > Sent: Wednesday, August 13, 2003 5:18 PM
> > > Subject: Re: [Sigtran] question about m3UA
> > >
> > >
> > > >
> > > > Ling-Chih Kao,
> > > >
> > > > On Wed, 13 Aug 2003, Ling-Chih Kao wrote:
> > > >
> > > > > Hi, Samuel
> > > > >
> > > > > 1.
> > > > > ASP3  in Sec. 5.1.4 did not send ASP Act. to SGP; however,  it
> received
> > > > > NOTIFY (AS-ACTIVE).
> > > > >
> > > > > This NOTIFY is also optional whether ASP3 send ASP Act. to SGP or
> not.
> > > > > That's right ?
> > > > >
> > > > As per RFC it is mandatory.Basically NTFY has been used not only to
> > > > reflect the AS state but also used like 'insufficent # of ASPs' to all
> > > > INACTIVE ASPs.
> > > > NTFY(AS-ACTIVE) - sending this to all INACTIVE-ASPs is mandatory as
> per
> > > >                   RFC, But i dont see any purpose here.
> > > >
> > > > NTFY("Insuff # of ASPs) - sending this to all INACTIVE-ASPs is
> mandatory
> > > >                           because any of the INACTIVE-ASP will become
> ACT.
> > > >
> > > > NTFY("AS-Pending") - sending this to all INACTIVE-ASPs is mandatory
> > > >                      because any of the INACTIVE-ASP will become ACT.
> > > >
> > > > > Should ASP3 send  ASP Act. to SGP?
> > > > >
> > > > In our example(n+k case), if n=2 then 2 ASPs(say ASP1 and ASP2) will
> send
> > > > ASP-ACT messages.But you can have a test case where you will be
> sending
> > > > ASP-ACT from ASP3, this case SGP will honour that ASP-ACT.But
> basically
> > > > 'k' ASP is used for backup purpose so unless ASP1 or ASP2 goes down
> ASP3
> > > > will not be sending ASP3-ACT.
> > > >
> > > > > 2.
> > > > > Should ASP3 send  ASP UP to SGP?
> > > > >
> > > > Yes, because you make the backup ASP ready to a certain level so that
> > > > when any one of the ASCTIVE-ASP goes down, backup ASP will take
> minimum
> > > > time to take up the load.
> > > >
> > > > > If ASP3 did not sent ASP UP to SGP, reception of NOTIFY(AS-INACTIVE)
> is
> > > also
> > > > > optional. Or, ASP3 will not receive  NOTIFY(AS-INACTIVE) because
> ASP3
> > > does
> > > > > not sent ASP UP to SGP.
> > > > This already Brian has answered.NTFY will not be processed in DOWN
> state.
> > > >
> > > > --Samuel
> > > > >
> > > > >
> > > > > Ling-Chih Kao
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran"
> <sigtran@ietf.org>
> > > > > Sent: Wednesday, August 13, 2003 12:27 PM
> > > > > Subject: Re: [Sigtran] question about m3UA
> > > > >
> > > > >
> > > > >
> > > > > Brian,
> > > > >  If it is mandatory to send NTFY(AS-STATE) to all ASPes(other than
> > > down),
> > > > >  Why dont we send SS7 node availability status(like
> DUNA,DAVA,DRST...)
> > > > >  to all INACTIVE-ASPes?(because anyway when INACTIVE-ASP moves to
> ACTIVE
> > > > >  ASP, it should know the status of SS7 nodes but finally it was
> decided
> > > > >  that newly active ASP will send an DAUD and gets the SS7 node(s)
> status
> > >
> > > > >  or SGP may send SS7 node(s) status to the newly active ASP.)
> > > > >  This i suggested long back(i think you remeber) but you strongly
> > > opposed
> > > > >  it. Now you are partially true with my old arguments.
> > > > >
> > > > > --Samuel
> > > > >
> > > > >   Alcatel USA, Inc.                  Internet:
> > > <userid>@ssd.usa.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, Inc.
> > > *******
> > > > >
> > > > > On Tue, 12 Aug 2003, Brian F. G. Bidulock wrote:
> > > > >
> > > > > > Ling-Chih,
> > > > > >
> > > > > > Mandatory.  All ASP-INACTIVE ASPs for an AS receive notifications
> > > > > > of state change.  ASP3 is ASP-INACTIVE in this case and must
> receive
> > > > > > the notification.
> > > > > >
> > > > > > The contentious case is when an ASP (ASP3) becomes ASP-INACTIVE
> from
> > > > > > ASP-DOWN.  I believe that the SGP should notify the newly inactive
> > > > > > ASP of the current state of the AS (which it did not receive
> before).
> > > > > > Samuel thinks that they should somehow guess the state of the AS.
> > > > > >
> > > > > > --brian
> > > > > >
> > > > > > Ling-Chih Kao wrote:
> > > > > (Wed, 13 Aug 2003 08:55:25)
> > > > > > > Hi, Brian and Samuel
> > > > > > >
> > > > > > > The answer for both of you is different.
> > > > > > > See again in Sec. 5.1.4, the ASP3 is for backup. ASP3 did not
> sent
> > > ASP
> > > > > Act.
> > > > > > > to SGP. Why did it receive NOTIFY(AS-ACTIVE) ? This is optional
> or
> > > > > > > mandatory?
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Ling-Chih Kao
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ----- Original Message -----
> > > > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran"
> > > <sigtran@ietf.org>
> > > > > > > Sent: Friday, August 08, 2003 6:08 PM
> > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Brian,
> > > > > > >  Huh, it is not an implementation dependent, rfc says
> > > > > > >  ASPs which are in that AS should coordinate among themselves
> the
> > > number
> > > > > > >  of active ASPs in the AS.So it is clear to SGP that first
> arrived
> > > > > > >  'n' ASPs will receive NTFY(AS-INACT) message.
> > > > > > >
> > > > > > >  If you want to send NTFY(AS-INACT) to all ASPes(other than DOWN
> > > state)
> > > > > > >  you are not restricted but it is not mandatory to send, thats
> what
> > > i
> > > > > > >  am saying from the beginning.
> > > > > > >
> > > > > > >  Keep IG as it is.
> > > > > > > --Samuel
> > > > > > >
> > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > <userid>@ssd.usa.alcatel.com
> > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > >   ******* The opinions expressed are not those of Alcatel USA,
> Inc.
> > > > > *******
> > > > > > >
> > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > >
> > > > > > > > Samuel,
> > > > > > > >
> > > > > > > > Maybe clear to the ASPs depending on implementation, but not
> > > > > > > > clear to the SGP.  If the NTFY(AS-INACTIVE) is not going to be
> > > > > > > > used by any of the ASPs, why send it in the first place?
> > > > > > > > If it serves a purpose, it should be sent to all of them to
> avoid
> > > > > > > > the race condition.
> > > > > > > >
> > > > > > > > --brian
> > > > > > > >
> > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > (Fri, 08 Aug 2003 04:36:50)
> > > > > > > > >
> > > > > > > > > Brian,
> > > > > > > > >  We all know that in n+k redundancy case that ASPes will
> > > coordinate
> > > > > > > > >  among themselves the number of active ASPs in the AS, here
> it
> > > is
> > > > > > > > >  clear that who is going to go to ACTIVE state then where is
> the
> > > > > > > > >  question of race condition?
> > > > > > > > >
> > > > > > > > > --Samuel
> > > > > > > > >
> > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > >   ******* The opinions expressed are not those of Alcatel
> USA,
> > > Inc.
> > > > > > > *******
> > > > > > > > >
> > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > >
> > > > > > > > > > Samuel,
> > > > > > > > > >
> > > > > > > > > > What if ASP1 and ASP3 receive it but ASP2 did not, just
> > > because
> > > > > > > > > > ASP3's ASPUP arrived before ASP2's.  That is a race
> condition.
> > > > > > > > > > This is why it is wise (and "SHOULD" is appropriate) to
> avoid
> > > > > > > > > > the race condition by sending NTFY(AS-INACTIVVE) to all of
> the
> > > > > > > > > > ASPs when they come up.  It should not be optional.  It is
> > > > > necessary
> > > > > > > > > > to proper interworking that this race be broken.
> > > > > > > > > >
> > > > > > > > > > --brian
> > > > > > > > > >
> > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > (Fri, 08 Aug 2003 04:17:31)
> > > > > > > > > > >
> > > > > > > > > > > Brian,
> > > > > > > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message
> respectively,
> > > but
> > > > > > > ASP1 and
> > > > > > > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > > > > > > >  Now ASP1 sends ASP-ACT message then ASP3 sends ASP-ACT
> > > message,
> > > > > > > > > > >  here it is mandatory to send NTFY(AS-ACT) to both
> > > ASPes(ASP1
> > > > > and
> > > > > > > ASP3).
> > > > > > > > > > >
> > > > > > > > > > >  This is the reason i said it is an optional of sending
> > > > > > > NTFY(AS-INACT)
> > > > > > > > > > >  to 'n+1'th ASP.
> > > > > > > > > > >
> > > > > > > > > > > --Samuel
> > > > > > > > > > >
> > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > >   ******* The opinions expressed are not those of
> Alcatel
> > > USA,
> > > > > Inc.
> > > > > > > *******
> > > > > > > > > > >
> > > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Samuel,
> > > > > > > > > > > >
> > > > > > > > > > > > Yes, I have a problem, because it is a race condition.
> > > > > > > > > > > >
> > > > > > > > > > > > --brian
> > > > > > > > > > > >
> > > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > (Fri, 08 Aug 2003 04:04:50)
> > > > > > > > > > > > >
> > > > > > > > > > > > > Brian,
> > > > > > > > > > > > >
> > > > > > > > > > > > >   I meant first 2 ASPes will receive NTFY
> > > messages.Sending
> > > > > NTFY
> > > > > > > to
> > > > > > > > > > > > >   3rd ASP is an optional.Do you have any problem
> here?
> > > > > > > > > > > > >
> > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > >
> > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > >   ******* The opinions expressed are not those of
> > > Alcatel
> > > > > USA,
> > > > > > > Inc. *******
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Samuel,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > None of the ASPs are handling traffic at that
> point.
> > > Who
> > > > > is
> > > > > > > to say
> > > > > > > > > > > > > > that ASP1 and ASP2 are the 'n' and ASP3 is the
> 'k'.
> > > > > Perhaps
> > > > > > > ASP2
> > > > > > > > > > > > > > and ASP3 are the 'n' and ASP1 is the 'k'.  The SGP
> > > surely
> > > > > > > doesn't know.
> > > > > > > > > > > > > > Sending NTFY(AS-INACTIVE) to all of them is the
> wisest
> > > > > choice.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --brian
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > In n+k reduntancy case,when n=2 that means ASP1
> and
> > > ASP2
> > > > > are
> > > > > > > going to
> > > > > > > > > > > > > > > handle the traffic.So sending NTFY to these
> ASPes is
> > > > > > > mandatory.
> > > > > > > > > > > > > > > Sending NTFY to ASP3 is an optional because it
> is
> > > not
> > > > > going
> > > > > > > to handle
> > > > > > > > > > > > > > > the traffic.When ASP1 or ASP2 goes down then
> ASP3
> > > will
> > > > > come
> > > > > > > up to take
> > > > > > > > > > > > > > > over the traffic this case SGP will send a NTFY
> > > message
> > > > > with
> > > > > > > AS state,
> > > > > > > > > > > > > > > here it is mandatory to send NTFY to ASP3.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > > > >   ******* The opinions expressed are not those
> of
> > > > > Alcatel
> > > > > > > USA, Inc. *******
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > From the new definition of AS-INACTIVE in sec
> > > 4.3.2 of
> > > > > > > > > > > > > > > >
> > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>,
> > > > > the AS
> > > > > > > becomes
> > > > > > > > > > > > > > > > AS-INACTIVE when there are at least n ASPs in
> > > either
> > > > > > > ASP-INACTIVE or
> > > > > > > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes
> AS-INACTIVE
> > > when
> > > > > SGP
> > > > > > > receives two ASP
> > > > > > > > > > > > > > > > UP (from ASP1 and ASP2).  However, when the
> SGP
> > > > > receives
> > > > > > > ASP UP from ASP3,
> > > > > > > > > > > > > > > > SGP does not  send NOTIFY (AS-INACTIVE) to
> ASP3. I
> > > > > want to
> > > > > > > know whether it
> > > > > > > > > > > > > > > > is optional or not?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Thanks.
> > > > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > > > > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > NTFY(AS-INACT) is sent to all all available
> peer
> > > > > ASPes.
> > > > > > > > > > > > > > > > Note: Available peer means an ASP which
> received
> > > > > > > ASP-UP-ACK
> > > > > > > > > > > > > > > > in response to ASP-UP messages.(as per RFC
> section
> > > > > > > 4.3.4.1).
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > If you active the AS as soon as a single ASP
> goes
> > > to
> > > > > > > ASP-INACT
> > > > > > > > > > > > > > > > state then it is obvious that whoever sends
> ASP-UP
> > > > > message
> > > > > > > to
> > > > > > > > > > > > > > > > SGP, immediately SGP will send a
> NTFY(AS-INACT) to
> > > the
> > > > > > > concern
> > > > > > > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > > > > >   ******* The opinions expressed are not those
> of
> > > > > Alcatel
> > > > > > > USA, Inc. *******
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > After SGP receives the ASP UP from ASP1, SGP
> > > should
> > > > > > > immediately send
> > > > > > > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to all ASP in the same
> AS.
> > > Is
> > > > > this
> > > > > > > right?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Thanks
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > > > > To: "Brian F. G. Bidulock"
> > > <bidulock@openss7.org>
> > > > > > > > > > > > > > > > > Cc: <kakaul@hss.hns.com>; "Ling-Chih Kao"
> > > > > > > <d86942004@ntu.edu.tw>;
> > > > > > > > > > > > > > > > "sigtran"
> > > > > > > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > > > > > > Sent: Tuesday, August 05, 2003 1:22 PM
> > > > > > > > > > > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Brian,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Mon, 4 Aug 2003, Brian F. G. Bidulock
> wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > But I think that we agreed that it would
> be
> > > wise
> > > > > to
> > > > > > > tell newly inactive
> > > > > > > > > > > > > > > >
> > > > > > >   ------------------
> > > > > > > > > > > > > > > > > > ASPs that state of the AS.  Also, in the
> > > diagram,
> > > > > the
> > > > > > > state of the AS
> > > > > > > > > > > > > > > > >   -------------------------
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > What does ASP3 do with NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > > > > > Whenever AS state-change happens at SGP, a
> NTFY
> > > will
> > > > > be
> > > > > > > sent to all ASPes
> > > > > > > > > > > > > > > > > (other than DOWN-ASPes) pertaining to the
> same
> > > RC
> > > > >
> > > >
> > >
> > >
> >
> >
> > _______________________________________________
> > 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



From exim@www1.ietf.org  Thu Aug 21 03:27:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20824
	for <sigtran-archive@odin.ietf.org>; Thu, 21 Aug 2003 03:27:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pjqb-0008Pf-Cn
	for sigtran-archive@odin.ietf.org; Thu, 21 Aug 2003 03:27:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7L7R5GR032338
	for sigtran-archive@odin.ietf.org; Thu, 21 Aug 2003 03:27:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pjqY-0008PN-JM; Thu, 21 Aug 2003 03:27:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19pjq1-0008Ow-Jz
	for sigtran@optimus.ietf.org; Thu, 21 Aug 2003 03:26:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20784
	for <sigtran@ietf.org>; Thu, 21 Aug 2003 03:26:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pjpz-0007JD-00
	for sigtran@ietf.org; Thu, 21 Aug 2003 03:26:27 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pjpy-0007JA-00
	for sigtran@ietf.org; Thu, 21 Aug 2003 03:26:26 -0400
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125])
	by albatross-ext.wise.edt.ericsson.se (8.12.9/8.12.9/WIREfire-1.7) with ESMTP id h7L7QPAv009837;
	Thu, 21 Aug 2003 09:26:25 +0200 (MEST)
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id Q9LMH9M2; Thu, 21 Aug 2003 09:26:25 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <Q59KFR3F>; Thu, 21 Aug 2003 09:26:17 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C04331772@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (EE/EEM)" <j.javier.pastor@ericsson.com>
To: "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        Ling-Chih Kao <d86942004@ntu.edu.tw>
Cc: sigtran <sigtran@ietf.org>
Subject: RE: [Sigtran] question about m3UA
Date: Thu, 21 Aug 2003 09:26:22 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Hi Samuel,=20

Yes, this seems to be in line with the conclusions about n+k =
redundancy...

Thanks // Javier.

> -----Original Message-----
> From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> Sent: mi=E9rcoles, 20 de agosto de 2003 21:39
> To: Ling-Chih Kao
> Cc: sigtran
> Subject: Re: [Sigtran] question about m3UA
>=20
>=20
>=20
> Pastor,
>=20
> IG section 5.1.4 and 5.2.3 are co-related, but section 5.2.3=20
> diagram is
> wrong because ASP2 is alive so SGP will send a=20
> NTFY(insuf-resources-at-AS)
> to INACTIVE-ASPes.
>=20
> Section 5.2.3 diagram should look like this
>=20
>         SGP                 ASP1                ASP2         =20
>       ASP3
>           |                   |                   |          =20
>         |
>           |<----ASP Inact.----|                   |          =20
>         |
>           |---ASP Inact Ack-->|                   |          =20
>         |
>           |                   |                   |          =20
>         |
>           |NOTIFY(Ins. ASPs)->|                   |          =20
>         |
>           |                   |                   |          =20
>         |
>           |                   |                   |          =20
>         |
>           |---------------------------------------NOTIFY(Ins.=20
> ASPs)-->|
>           |                   |                   |          =20
>         |
>           |                   |                   |          =20
>         |
>           |<----------------------------------------ASP Act=20
> (Ldshr)---|
>           |------------------------------------------ASP Act=20
> (Ack)--->|
>           |                   |                   |          =20
>         |
>           |-NTFY(AS-ACTIVE)-->|                   |          =20
>         |
>           |-------------------NOTIFY(AS-ACTIVE)-->|          =20
>         |
>          =20
> |---------------------------------------NOTIFY(AS-ACTIVE)-->|
>           |                   |                   |          =20
>         |
>           |                   |                   |          =20
>         |
>=20
>=20
> Did you remeber this, we discussed few months back that in=20
> n+k reduntancy
> case SGP should not stop the traffic until 'n' becomes zero.
>=20
> --Samuel
>=20
> On Wed, 20 Aug 2003, Ling-Chih Kao wrote:
>=20
> >  Samuel
> >=20
> > The example in sec. 5.1.4 and 5.2.3 is for "2+1" sparing=20
> loadsharing case.
> > The original active ASP is ASP1 and ASP2. Later, ASP1=20
> withdraws  and ASP3
> > overrides it. ASP2 is still active; therefore, not all ASPs=20
> go into ASP
> > inactive. Am I wrong?
> >=20
> > In  the example of sec. 5.1.4  for "2+1" sparing=20
> loadsharing case, the
> > decision of  ASPs taking care traffic is still by a craft means via
> > configured database. (In this example, ASP1 and ASP2 take=20
> care traffic
> > first.)
> > Or, depend on which ASP send ASP active to SGP first?
> >=20
> > Thanks
> >=20
> > Ling-Chih Kao
> >=20
> >=20
> > ----- Original Message -----
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > Cc: "sigtran" <sigtran@ietf.org>
> > Sent: Tuesday, August 19, 2003 7:58 PM
> > Subject: Re: [Sigtran] question about m3UA
> >=20
> >=20
> > >
> > > Ling-Chih Kao,
> > >
> > > comments in-line.
> > >
> > > On Tue, 19 Aug 2003, Ling-Chih Kao wrote:
> > >
> > > > Hi, Samuel
> > > >
> > > > You mentioned that NTFY("AS-Pending") - sending this to all
> > INACTIVE-ASPs is
> > > > mandatory because any of the INACTIVE-ASP will become ACT.
> > > > However, from the definition of M3UA Implementor's=20
> Guide, it said that
> > > > "AS-PENDING: The last active ASP has transitioned from=20
> ASP-ACTIVE to
> > > >    ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r)=20
> SHOULD be started
> > > >    and all incoming signalling messages SHOULD be=20
> queued by the SGP. If
> > > >    an ASP becomes ASP-ACTIVE before T(r) expires, the=20
> AS is moved to the
> > > >    AS-ACTIVE state and all the queued messages will be=20
> sent to the ASP".
> > > >
> > > > ASP3 overrides ASP1 when ASP1 want to withdraw (example=20
> in sec. 5.2.3
> > (2+1
> > > > redundancy model)).The AS still has an active ASP=20
> (ASP2). Why did SGP
> > send
> > > > NTFY("AS-Pending") to all ASPs? Are this wrong?
> > >
> > > NTFY(AS-Pending) is sent only when the final ACTIVE ASP goes =
down.
> > > How do you say ASP2 is ACTIVE?
> > >
> > > >
> > > > As mentioned in sec. 5.2.1 of  RFC 3332, how did SGP=20
> instruct which ASP
> > > > should send ASP Active to SGP  when SGP M3UA layer=20
> detects the loss of
> > the
> > > > peer M3UA?
> > > My understanding is , it is not the SGP which instructs=20
> which ASP to
> > > come-up, but it is the craft person's local database=20
> configuration at
> > > Application Server side.
> > >
> > > If SGP detects loss of peer M3UA layer (may be ASP1 does=20
> not respond with
> > > heartbeat-ack)SGP will send a NTFY message to ASP2 so=20
> that ASP2 will
> > > become ACTIVE.
> > >
> > > >
> > > > As mentioned in sec. 5.2.2 of RFC 3332, What is the=20
> reason for ASP2 to
> > > > override ASP1 ? How did ASP2 know to send ASP Active to=20
> SGP? When the
> > model
> > > > is 2+2 redundancy model, there are two backup ASPs,=20
> which ASP will
> > override
> > > > original ASP?
> > >
> > > What is the reason for ASP2 to override ASP1 ?
> > > See, everything is controlled by a craft means via=20
> configured database.
> > > Say for example, traffic is smooth between SGP1 and ASP1=20
> but after some
> > > time craft wants to do some kind of databse modification=20
> at ASP1 so he
> > > make ASP2 to send the ASP-ACTIVE, Is this ok?
> > >
> > > All qtns are answered above with respect to local=20
> database configuration
> > > at Application Server.
> > >
> > > > Ling-Chih Kao
> > > >
> > > > ----- Original Message -----
> > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > To: "Ling-Chih Kao" <d86942004@ntu.edu.tw>
> > > > Cc: <bidulock@openss7.org>; "sigtran" <sigtran@ietf.org>
> > > > Sent: Wednesday, August 13, 2003 5:18 PM
> > > > Subject: Re: [Sigtran] question about m3UA
> > > >
> > > >
> > > > >
> > > > > Ling-Chih Kao,
> > > > >
> > > > > On Wed, 13 Aug 2003, Ling-Chih Kao wrote:
> > > > >
> > > > > > Hi, Samuel
> > > > > >
> > > > > > 1.
> > > > > > ASP3  in Sec. 5.1.4 did not send ASP Act. to SGP;=20
> however,  it
> > received
> > > > > > NOTIFY (AS-ACTIVE).
> > > > > >
> > > > > > This NOTIFY is also optional whether ASP3 send ASP=20
> Act. to SGP or
> > not.
> > > > > > That's right ?
> > > > > >
> > > > > As per RFC it is mandatory.Basically NTFY has been=20
> used not only to
> > > > > reflect the AS state but also used like 'insufficent=20
> # of ASPs' to all
> > > > > INACTIVE ASPs.
> > > > > NTFY(AS-ACTIVE) - sending this to all INACTIVE-ASPs=20
> is mandatory as
> > per
> > > > >                   RFC, But i dont see any purpose here.
> > > > >
> > > > > NTFY("Insuff # of ASPs) - sending this to all INACTIVE-ASPs =
is
> > mandatory
> > > > >                           because any of the=20
> INACTIVE-ASP will become
> > ACT.
> > > > >
> > > > > NTFY("AS-Pending") - sending this to all=20
> INACTIVE-ASPs is mandatory
> > > > >                      because any of the INACTIVE-ASP=20
> will become ACT.
> > > > >
> > > > > > Should ASP3 send  ASP Act. to SGP?
> > > > > >
> > > > > In our example(n+k case), if n=3D2 then 2 ASPs(say ASP1=20
> and ASP2) will
> > send
> > > > > ASP-ACT messages.But you can have a test case where=20
> you will be
> > sending
> > > > > ASP-ACT from ASP3, this case SGP will honour that ASP-ACT.But
> > basically
> > > > > 'k' ASP is used for backup purpose so unless ASP1 or=20
> ASP2 goes down
> > ASP3
> > > > > will not be sending ASP3-ACT.
> > > > >
> > > > > > 2.
> > > > > > Should ASP3 send  ASP UP to SGP?
> > > > > >
> > > > > Yes, because you make the backup ASP ready to a=20
> certain level so that
> > > > > when any one of the ASCTIVE-ASP goes down, backup ASP=20
> will take
> > minimum
> > > > > time to take up the load.
> > > > >
> > > > > > If ASP3 did not sent ASP UP to SGP, reception of=20
> NOTIFY(AS-INACTIVE)
> > is
> > > > also
> > > > > > optional. Or, ASP3 will not receive =20
> NOTIFY(AS-INACTIVE) because
> > ASP3
> > > > does
> > > > > > not sent ASP UP to SGP.
> > > > > This already Brian has answered.NTFY will not be=20
> processed in DOWN
> > state.
> > > > >
> > > > > --Samuel
> > > > > >
> > > > > >
> > > > > > Ling-Chih Kao
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "Samuel Dur D. Jeyaseelan"=20
> <sjeyasee@ssd.usa.alcatel.com>
> > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran"
> > <sigtran@ietf.org>
> > > > > > Sent: Wednesday, August 13, 2003 12:27 PM
> > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > >
> > > > > >
> > > > > >
> > > > > > Brian,
> > > > > >  If it is mandatory to send NTFY(AS-STATE) to all=20
> ASPes(other than
> > > > down),
> > > > > >  Why dont we send SS7 node availability status(like
> > DUNA,DAVA,DRST...)
> > > > > >  to all INACTIVE-ASPes?(because anyway when=20
> INACTIVE-ASP moves to
> > ACTIVE
> > > > > >  ASP, it should know the status of SS7 nodes but=20
> finally it was
> > decided
> > > > > >  that newly active ASP will send an DAUD and gets=20
> the SS7 node(s)
> > status
> > > >
> > > > > >  or SGP may send SS7 node(s) status to the newly=20
> active ASP.)
> > > > > >  This i suggested long back(i think you remeber)=20
> but you strongly
> > > > opposed
> > > > > >  it. Now you are partially true with my old arguments.
> > > > > >
> > > > > > --Samuel
> > > > > >
> > > > > >   Alcatel USA, Inc.                  Internet:
> > > > <userid>@ssd.usa.alcatel.com
> > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > >   ******* The opinions expressed are not those of=20
> Alcatel USA, Inc.
> > > > *******
> > > > > >
> > > > > > On Tue, 12 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > >
> > > > > > > Ling-Chih,
> > > > > > >
> > > > > > > Mandatory.  All ASP-INACTIVE ASPs for an AS=20
> receive notifications
> > > > > > > of state change.  ASP3 is ASP-INACTIVE in this=20
> case and must
> > receive
> > > > > > > the notification.
> > > > > > >
> > > > > > > The contentious case is when an ASP (ASP3)=20
> becomes ASP-INACTIVE
> > from
> > > > > > > ASP-DOWN.  I believe that the SGP should notify=20
> the newly inactive
> > > > > > > ASP of the current state of the AS (which it did=20
> not receive
> > before).
> > > > > > > Samuel thinks that they should somehow guess the=20
> state of the AS.
> > > > > > >
> > > > > > > --brian
> > > > > > >
> > > > > > > Ling-Chih Kao wrote:
> > > > > > (Wed, 13 Aug 2003 08:55:25)
> > > > > > > > Hi, Brian and Samuel
> > > > > > > >
> > > > > > > > The answer for both of you is different.
> > > > > > > > See again in Sec. 5.1.4, the ASP3 is for=20
> backup. ASP3 did not
> > sent
> > > > ASP
> > > > > > Act.
> > > > > > > > to SGP. Why did it receive NOTIFY(AS-ACTIVE) ?=20
> This is optional
> > or
> > > > > > > > mandatory?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > Ling-Chih Kao
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ----- Original Message -----
> > > > > > > > From: "Samuel Dur D. Jeyaseelan"=20
> <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > To: "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > > > > Cc: "Ling-Chih Kao" <d86942004@ntu.edu.tw>; "sigtran"
> > > > <sigtran@ietf.org>
> > > > > > > > Sent: Friday, August 08, 2003 6:08 PM
> > > > > > > > Subject: Re: [Sigtran] question about m3UA
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Brian,
> > > > > > > >  Huh, it is not an implementation dependent, rfc says
> > > > > > > >  ASPs which are in that AS should coordinate=20
> among themselves
> > the
> > > > number
> > > > > > > >  of active ASPs in the AS.So it is clear to SGP=20
> that first
> > arrived
> > > > > > > >  'n' ASPs will receive NTFY(AS-INACT) message.
> > > > > > > >
> > > > > > > >  If you want to send NTFY(AS-INACT) to all=20
> ASPes(other than DOWN
> > > > state)
> > > > > > > >  you are not restricted but it is not mandatory=20
> to send, thats
> > what
> > > > i
> > > > > > > >  am saying from the beginning.
> > > > > > > >
> > > > > > > >  Keep IG as it is.
> > > > > > > > --Samuel
> > > > > > > >
> > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > >   ******* The opinions expressed are not those=20
> of Alcatel USA,
> > Inc.
> > > > > > *******
> > > > > > > >
> > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > >
> > > > > > > > > Samuel,
> > > > > > > > >
> > > > > > > > > Maybe clear to the ASPs depending on=20
> implementation, but not
> > > > > > > > > clear to the SGP.  If the NTFY(AS-INACTIVE)=20
> is not going to be
> > > > > > > > > used by any of the ASPs, why send it in the=20
> first place?
> > > > > > > > > If it serves a purpose, it should be sent to=20
> all of them to
> > avoid
> > > > > > > > > the race condition.
> > > > > > > > >
> > > > > > > > > --brian
> > > > > > > > >
> > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > > (Fri, 08 Aug 2003 04:36:50)
> > > > > > > > > >
> > > > > > > > > > Brian,
> > > > > > > > > >  We all know that in n+k redundancy case=20
> that ASPes will
> > > > coordinate
> > > > > > > > > >  among themselves the number of active ASPs=20
> in the AS, here
> > it
> > > > is
> > > > > > > > > >  clear that who is going to go to ACTIVE=20
> state then where is
> > the
> > > > > > > > > >  question of race condition?
> > > > > > > > > >
> > > > > > > > > > --Samuel
> > > > > > > > > >
> > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > >   ******* The opinions expressed are not=20
> those of Alcatel
> > USA,
> > > > Inc.
> > > > > > > > *******
> > > > > > > > > >
> > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > >
> > > > > > > > > > > Samuel,
> > > > > > > > > > >
> > > > > > > > > > > What if ASP1 and ASP3 receive it but ASP2=20
> did not, just
> > > > because
> > > > > > > > > > > ASP3's ASPUP arrived before ASP2's.  That=20
> is a race
> > condition.
> > > > > > > > > > > This is why it is wise (and "SHOULD" is=20
> appropriate) to
> > avoid
> > > > > > > > > > > the race condition by sending=20
> NTFY(AS-INACTIVVE) to all of
> > the
> > > > > > > > > > > ASPs when they come up.  It should not be=20
> optional.  It is
> > > > > > necessary
> > > > > > > > > > > to proper interworking that this race be broken.
> > > > > > > > > > >
> > > > > > > > > > > --brian
> > > > > > > > > > >
> > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > > (Fri, 08 Aug 2003 04:17:31)
> > > > > > > > > > > >
> > > > > > > > > > > > Brian,
> > > > > > > > > > > >  Ok,say ASP1,ASP2 and ASP3 send ASP-UP message
> > respectively,
> > > > but
> > > > > > > > ASP1 and
> > > > > > > > > > > >  ASP2 received NTFY(AS-INACT) but ASP3 did not.
> > > > > > > > > > > >  Now ASP1 sends ASP-ACT message then=20
> ASP3 sends ASP-ACT
> > > > message,
> > > > > > > > > > > >  here it is mandatory to send=20
> NTFY(AS-ACT) to both
> > > > ASPes(ASP1
> > > > > > and
> > > > > > > > ASP3).
> > > > > > > > > > > >
> > > > > > > > > > > >  This is the reason i said it is an=20
> optional of sending
> > > > > > > > NTFY(AS-INACT)
> > > > > > > > > > > >  to 'n+1'th ASP.
> > > > > > > > > > > >
> > > > > > > > > > > > --Samuel
> > > > > > > > > > > >
> > > > > > > > > > > >   Alcatel USA, Inc.                  Internet:
> > > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > >   ******* The opinions expressed are=20
> not those of
> > Alcatel
> > > > USA,
> > > > > > Inc.
> > > > > > > > *******
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G. Bidulock wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Samuel,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Yes, I have a problem, because it is=20
> a race condition.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --brian
> > > > > > > > > > > > >
> > > > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > > (Fri, 08 Aug 2003 04:04:50)
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Brian,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >   I meant first 2 ASPes will receive NTFY
> > > > messages.Sending
> > > > > > NTFY
> > > > > > > > to
> > > > > > > > > > > > > >   3rd ASP is an optional.Do you=20
> have any problem
> > here?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >   Alcatel USA, Inc.                =20
>  Internet:
> > > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > > >   ******* The opinions expressed=20
> are not those of
> > > > Alcatel
> > > > > > USA,
> > > > > > > > Inc. *******
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Fri, 8 Aug 2003, Brian F. G.=20
> Bidulock wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Samuel,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > None of the ASPs are handling=20
> traffic at that
> > point.
> > > > Who
> > > > > > is
> > > > > > > > to say
> > > > > > > > > > > > > > > that ASP1 and ASP2 are the 'n'=20
> and ASP3 is the
> > 'k'.
> > > > > > Perhaps
> > > > > > > > ASP2
> > > > > > > > > > > > > > > and ASP3 are the 'n' and ASP1 is=20
> the 'k'.  The SGP
> > > > surely
> > > > > > > > doesn't know.
> > > > > > > > > > > > > > > Sending NTFY(AS-INACTIVE) to all=20
> of them is the
> > wisest
> > > > > > choice.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > --brian
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Samuel Dur D. Jeyaseelan wrote:
> > > > > > > > (Fri, 08 Aug 2003 03:47:30)
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Ling-Chih Kao and Brian,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > In n+k reduntancy case,when n=3D2=20
> that means ASP1
> > and
> > > > ASP2
> > > > > > are
> > > > > > > > going to
> > > > > > > > > > > > > > > > handle the traffic.So sending=20
> NTFY to these
> > ASPes is
> > > > > > > > mandatory.
> > > > > > > > > > > > > > > > Sending NTFY to ASP3 is an=20
> optional because it
> > is
> > > > not
> > > > > > going
> > > > > > > > to handle
> > > > > > > > > > > > > > > > the traffic.When ASP1 or ASP2=20
> goes down then
> > ASP3
> > > > will
> > > > > > come
> > > > > > > > up to take
> > > > > > > > > > > > > > > > over the traffic this case SGP=20
> will send a NTFY
> > > > message
> > > > > > with
> > > > > > > > AS state,
> > > > > > > > > > > > > > > > here it is mandatory to send=20
> NTFY to ASP3.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >   Alcatel USA, Inc.            =20
>      Internet:
> > > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > > > > >   ******* The opinions=20
> expressed are not those
> > of
> > > > > > Alcatel
> > > > > > > > USA, Inc. *******
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih Kao =
wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Dear Samuel Dur D. Jeyaseelan
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > From the new definition of=20
> AS-INACTIVE in sec
> > > > 4.3.2 of
> > > > > > > > > > > > > > > > >
> > > > draft-ietf-sigtran-m3ua-implementors-guide-04.txt>,
> > > > > > the AS
> > > > > > > > becomes
> > > > > > > > > > > > > > > > > AS-INACTIVE when there are at=20
> least n ASPs in
> > > > either
> > > > > > > > ASP-INACTIVE or
> > > > > > > > > > > > > > > > > AS-ACTIVE.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Therefore, in sec. 5.1.4, AS becomes
> > AS-INACTIVE
> > > > when
> > > > > > SGP
> > > > > > > > receives two ASP
> > > > > > > > > > > > > > > > > UP (from ASP1 and ASP2). =20
> However, when the
> > SGP
> > > > > > receives
> > > > > > > > ASP UP from ASP3,
> > > > > > > > > > > > > > > > > SGP does not  send NOTIFY=20
> (AS-INACTIVE) to
> > ASP3. I
> > > > > > want to
> > > > > > > > know whether it
> > > > > > > > > > > > > > > > > is optional or not?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Thanks.
> > > > > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > > > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > > > > To: "Ling-Chih Kao"=20
> <d86942004@ntu.edu.tw>
> > > > > > > > > > > > > > > > > Cc: "sigtran" <sigtran@ietf.org>
> > > > > > > > > > > > > > > > > Sent: Friday, August 08, 2003 3:41 PM
> > > > > > > > > > > > > > > > > Subject: Re: [Sigtran]=20
> question about m3UA
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Ling-Chih Kao,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > NTFY(AS-INACT) is sent to all=20
> all available
> > peer
> > > > > > ASPes.
> > > > > > > > > > > > > > > > > Note: Available peer means an=20
> ASP which
> > received
> > > > > > > > ASP-UP-ACK
> > > > > > > > > > > > > > > > > in response to ASP-UP=20
> messages.(as per RFC
> > section
> > > > > > > > 4.3.4.1).
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > If you active the AS as soon=20
> as a single ASP
> > goes
> > > > to
> > > > > > > > ASP-INACT
> > > > > > > > > > > > > > > > > state then it is obvious that=20
> whoever sends
> > ASP-UP
> > > > > > message
> > > > > > > > to
> > > > > > > > > > > > > > > > > SGP, immediately SGP will send a
> > NTFY(AS-INACT) to
> > > > the
> > > > > > > > concern
> > > > > > > > > > > > > > > > > ASP followd by ASP-UP-ACK.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > --Samuel
> > > > > > > > > > > > > > > > >   Alcatel USA, Inc.          =20
>        Internet:
> > > > > > > > <userid>@ssd.usa.alcatel.com
> > > > > > > > > > > > > > > > >   1000 Coit Road, Plano, Texas 75075
> > > > > > > > > > > > > > > > >   ******* The opinions=20
> expressed are not those
> > of
> > > > > > Alcatel
> > > > > > > > USA, Inc. *******
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Fri, 8 Aug 2003, Ling-Chih=20
> Kao wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > After SGP receives the ASP=20
> UP from ASP1, SGP
> > > > should
> > > > > > > > immediately send
> > > > > > > > > > > > > > > > > > NOTIFY(AS-INACTIVE)   to=20
> all ASP in the same
> > AS.
> > > > Is
> > > > > > this
> > > > > > > > right?
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Thanks
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Ling-Chih Kao
> > > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > > From: "Samuel Dur D. Jeyaseelan"
> > > > > > > > <sjeyasee@ssd.usa.alcatel.com>
> > > > > > > > > > > > > > > > > > To: "Brian F. G. Bidulock"
> > > > <bidulock@openss7.org>
> > > > > > > > > > > > > > > > > > Cc: <kakaul@hss.hns.com>;=20
> "Ling-Chih Kao"
> > > > > > > > <d86942004@ntu.edu.tw>;
> > > > > > > > > > > > > > > > > "sigtran"
> > > > > > > > > > > > > > > > > > <sigtran@ietf.org>
> > > > > > > > > > > > > > > > > > Sent: Tuesday, August 05,=20
> 2003 1:22 PM
> > > > > > > > > > > > > > > > > > Subject: Re: [Sigtran]=20
> question about m3UA
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Brian,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Mon, 4 Aug 2003, Brian=20
> F. G. Bidulock
> > wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > kakaul,
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > But I think that we=20
> agreed that it would
> > be
> > > > wise
> > > > > > to
> > > > > > > > tell newly inactive
> > > > > > > > > > > > > > > > >
> > > > > > > >   ------------------
> > > > > > > > > > > > > > > > > > > ASPs that state of the=20
> AS.  Also, in the
> > > > diagram,
> > > > > > the
> > > > > > > > state of the AS
> > > > > > > > > > > > > > > > > >   -------------------------
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > What does ASP3 do with=20
> NOTIFY(AS-INACTIVE)?
> > > > > > > > > > > > > > > > > > Whenever AS state-change=20
> happens at SGP, a
> > NTFY
> > > > will
> > > > > > be
> > > > > > > > sent to all ASPes
> > > > > > > > > > > > > > > > > > (other than DOWN-ASPes)=20
> pertaining to the
> > same
> > > > RC
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20
> >=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Tue Aug 26 17:25:02 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11074
	for <sigtran-archive@odin.ietf.org>; Tue, 26 Aug 2003 17:25:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19rkfH-0007Th-CS
	for sigtran-archive@odin.ietf.org; Tue, 26 Aug 2003 16:43:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7QKhgQo028719
	for sigtran-archive@odin.ietf.org; Tue, 26 Aug 2003 16:43:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19rkUr-0006z0-91; Tue, 26 Aug 2003 16:32:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19rjHY-0007qX-FM
	for sigtran@optimus.ietf.org; Tue, 26 Aug 2003 15:15:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26174
	for <sigtran@ietf.org>; Tue, 26 Aug 2003 15:15:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rjHX-0006le-00
	for sigtran@ietf.org; Tue, 26 Aug 2003 15:15:07 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rjHW-0006kp-00
	for sigtran@ietf.org; Tue, 26 Aug 2003 15:15:06 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h7QJEZwA026513;
	Tue, 26 Aug 2003 14:14:35 -0500 (CDT)
Message-ID: <3F4BB19B.2010803@alcatel.com>
Date: Tue, 26 Aug 2003 14:14:35 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M2PA Last Call Comment - RPO
References: <3F15C7F2.6070704@pt.com> <20030716191143.F6725@openss7.org> <3F18328D.1080706@pt.com> <20030718120053.C14760@openss7.org> <3F184959.2040103@pt.com> <20030718133957.A16698@openss7.org> <3F1867CB.6060108@pt.com> <20030724134845.D11627@openss7.org> <3F26BAA2.1080908@pt.com> <3F29983B.2040505@alcatel.com> <20030731165031.A6734@openss7.org> <3F2ACB8B.7090806@pt.com> <3F3D72B2.8050007@alcatel.com> <3F4399C2.6050104@pt.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Andrew, Brian, et. al.,

Comments below. Covering for the two cases is harder than it looks. 
Suggestions would be appreciated.

tomG.

Andrew Booth wrote:
> Hi Tom,
> 
> Looks pretty good.  Some comments/questions below.
> 
> Tom George wrote:
> 
>> Brian, Andrew, et. al.,
>>
>> Here is my attempt to incorporate all of the comments from this 
>> thread. I may have missed some comments, so please take a look and see 
>> if I missed everything. I tried to cover for both cases - where the 
>> M2PA in RPO could and could not pass messages to MTP3.
> 
> 
>>
>>
>> tomG.
>>
>> Revised section 4.1.4:
>> =====
>> 4.1.4 Processor Outage
>>
>> The Link Status Processor Outage message replaces the SIPO message of
>> MTP2. Unlike MTP2, the message SHOULD NOT be transmitted
>> continuously. M2PA SHALL send a Link Status Processor Outage message
>> to its peer at the beginning of a processor outage condition where
>> MTP2 would send SIPO. M2PA MAY send additional Link Status Processor
>> Outage messages as long as that condition persists.
>>
>> When the local processor outage condition ends, M2PA SHALL send a Link
>> Status Processor Recovered message to its peer. This message is used
>> to signal the end of the processor outage condition, instead of an MSU
>> or FISU as in MTP2. The BSN in the Link Status Processor Recovered
>> message is set to the FSN of the last User Data message received from
>> the peer M2PA. The BSN value in the Link Status Processor Recovered
>> message is used by the peer to resynchronize its sequence numbers, if
>> this is required by MTP2.
>>
>> While in a local processor outage condition:
>>
>>    (a) Any User Data messages received from the peer MUST NOT be
>>        acknowledged and MUST be buffered.
>>
>>    (b) M2PA SHOULD continue to acknowledge User Data messages received
>>        and accepted by MTP3 before the local processor outage.
>>
>> While there is a remote processor outage condition:
>>
>>    (a) M2PA SHOULD continue to acknowledge User Data messages received
>>        and accepted by MTP3 regardless of the remote processor outage.
>>
>>    (b) If any User Data messages received from the peer after the Link
>>        Status Processor Outage cannot be delivered to MTP3, then these
>>        messages MUST NOT be acknowledged and MUST be buffered.
>>
>> If M2PA receives a Flush command from MTP3, M2PA SHALL discard any
>> incoming messages that were queued and unacknowledged during the
>> processor outage condition.
>>
>> Furthermore, if the M2PA experiencing processor outage receives a
>> Flush command,
>>
>>    (a) M2PA SHALL NOT discard messages from the transmit and
>>        retransmit queues. 
> 
> 
> Any messages still in the transmit/retransmit buffer when a flush is 
> received are probably already stale and should be flushed.  This is 
> particularly important if the remote end cannot ack the data for some 
> reason, in which case data messages can get stuck in the TB/RTB for 
> arbitrarily long times.
> I think this proposal was based on the assumption that the remote end 
> would ack the data in the TB/RTB so these queues would empty themselves 
> anyway; however there are cases where the remote end might not be able 
> to ack the data in the RTB so messages might get stuck in the TB/RTB.

Yes, this was written with the assumption that the LPO end was going to 
keep transmitting messages. The thinking was that these messages should 
be drained out, so it would be misguided to attempt a flush.

But I think you are right in saying that any messages left over by the 
time that MTP3 commands a Flush are probably stale anyway, whether the 
other end is acking messages or not. So maybe it would be better to 
remove this (a) and follow MTP2, i.e., flush those messages.


>>
>>
>>    (b) M2PA SHALL NOT perform procedures to resynchronize sequence
>>        numbers.
> 
> 
> I don't think resynchronization is necessary for either LPO or RPO, but 
> I especially don't understand why it should be different between the two.

If the LPO end continues normal transmission, we would not need to 
resynch the sequence numbers.

The LPO end is going to have incoming queued-but-unacked messages. It 
will have to flush those after the PO ends. So it needs to resynch the 
sequence numbers (right?).


>>
>>
>>    (c) M2PA SHALL continue normal transmission of User Data.
>>
>> If the M2PA experiencing remote processor outage receives a Flush
>> command,
>>
>>    (a) M2PA SHALL discard messages in the transmit and retransmit
>>        queues as required by MTP2.
>>
>>    (b) M2PA MAY perform resynchronization of sequence numbers using
>>        the BSN from the received Link Status Processor Recovered
>>        message.  However, during resychronization, M2PA SHALL NOT
>>        discard any received User Data messages.
> 
> 
> This confuses me a bit.  Is the idea is that we don't want to discard 
> messages that were sent after processor outage, taking into account the 
> multistreaming?  I assume we're still expected flush the receive buffer 
> at some point?

Brian pointed out that in Q.703, the end recovering from RPO is allowed 
to discard a few MSUs. We do not want this to happen in M2PA, since 
there is no retransmission. But this is confusing (even to me), since 
earlier in the section I wrote that "M2PA SHALL discard any incoming 
messages that were queued and unacknowledged during the processor outage 
condition." I want it to flush the queued-and-unacked messages received 
during PO, but not discard any messages that are sent after PO ends.


> 
> Andrew
> 
>>
>>
>> Note that because the Link Status and User Data messages are sent on
>> separate streams, it is possible for a User Data message sent after
>> the Link Status Processor Recovered message to arrive before
>> it. Therefore, when flushing buffers, M2PA must take care not to flush
>> messages sent after the remote processor recovered. M2PA SHOULD NOT
>> flush User Data messages with FSN greater than the FSN in the Link
>> Status Processor Recovered message.
>>
>> If M2PA receives a Continue command from MTP3, M2PA SHALL begin
>> processing the incoming messages that were queued and unacknowledged
>> during the processor outage condition.
>>
>> When M2PA experiences a local processor outage, it MAY put the link
>> out of service by sending a Link Status Out of Service message if
>> allowed by the applicable MTP2 standard (e.g., [Q.2140]).
>>
>> In other respects, M2PA SHOULD follow the same procedures as MTP2 in
>> processor outage.
>>
>> =====
   [...]

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
*   I actively disclaim speaking for Alcatel.  I do not purport to    *
*   advertise or represent its position, operations, or activities.   *


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



From exim@www1.ietf.org  Wed Aug 27 00:49:45 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20639
	for <sigtran-archive@odin.ietf.org>; Wed, 27 Aug 2003 00:49:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19rmgr-0004q8-HU
	for sigtran-archive@odin.ietf.org; Tue, 26 Aug 2003 18:53:29 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7QMrT6w018584
	for sigtran-archive@odin.ietf.org; Tue, 26 Aug 2003 18:53:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19rlui-0002L3-Lh; Tue, 26 Aug 2003 18:03:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19rkvN-0007nK-5b
	for sigtran@optimus.ietf.org; Tue, 26 Aug 2003 17:00:21 -0400
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09105
	for <sigtran@odin.ietf.org>; Tue, 26 Aug 2003 17:00:15 -0400 (EDT)
Received: from apache by asgard.ietf.org with local (Exim 4.14)
	id 19rkut-0005a1-5H; Tue, 26 Aug 2003 16:59:51 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>, <sigtran@ietf.org>
Message-Id: <E19rkut-0005a1-5H@asgard.ietf.org>
Date: Tue, 26 Aug 2003 16:59:51 -0400
Subject: [Sigtran] Protocol Action: 'Stream Control Transmission Protocol
 Management Information Base' to Proposed Standard
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

The IESG has approved the Internet-Draft 'Stream Control Transmission 
Protocol Management Information Base' <draft-ietf-sigtran-sctp-mib-10.txt> 
as a Proposed Standard. This document is the product of the Signaling 
Transport Working Group. 

The IESG contact persons are Jon Peterson and Allison Mankin.

Technical Summary

The Stream Control Transmission Protocol (SCTP) is a reliable
transport protocol operating on top of a connectionless packet
network such as IP. It is designed to transport PSTN signaling
messages over the connectionless packet network, but is capable of
broader applications.

This memo defines the Management Information Base (MIB) module which
describes the minimum set of objects needed to manage the
implementation of the SCTP.

There is one existing nit that we need to fix in an RFC-editor note - 
namely that the SIZE restriction of 115 octets on the 
sctpAssocRemHostName needs to be removed (should be 255).
   
Working Group Summary
   
The SIGTRAN WG and the TSVWG WG supported this document.
   
Protocol Quality
   
This specification was reviewed for the IESG by Bert Wijnen and Jon
Peterson. Further MIB review was performed by the participants of 
the mreview mailing list.


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



From exim@www1.ietf.org  Wed Aug 27 00:58:20 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21469
	for <sigtran-archive@odin.ietf.org>; Wed, 27 Aug 2003 00:58:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19rnOp-0007Si-Gs
	for sigtran-archive@odin.ietf.org; Tue, 26 Aug 2003 19:38:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7QNctSw028659
	for sigtran-archive@odin.ietf.org; Tue, 26 Aug 2003 19:38:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19rmOm-0003Wl-1h; Tue, 26 Aug 2003 18:34:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19rlLh-0000jG-Oi
	for sigtran@optimus.ietf.org; Tue, 26 Aug 2003 17:27:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11332
	for <sigtran@ietf.org>; Tue, 26 Aug 2003 17:27:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rlLf-0002Qg-00
	for sigtran@ietf.org; Tue, 26 Aug 2003 17:27:31 -0400
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rlLe-0002QS-00
	for sigtran@ietf.org; Tue, 26 Aug 2003 17:27:30 -0400
Received: by w2ksjexg01.oni.com with Internet Mail Service (5.5.2653.19)
	id <RWHZ0D3L>; Tue, 26 Aug 2003 14:27:23 -0700
Message-ID: <829F074A10F98943A218DC363D09C92AAE5F88@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Tue, 26 Aug 2003 14:27:26 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Sigtran] FW: Protocol Action: 'Stream Control Transmission Protocol  Manag
 ement Information Base' to Proposed Standard
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Folks,

Thanks go to Maria-Carmen and Javier for all of their work
on the SCTP MIB, as indicated elow it has now been approved
as Proposed Standard.

Cheers,

L. Ong

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]
Sent: Tuesday, August 26, 2003 2:00 PM
To: IETF-Announce
Cc: Internet Architecture Board; RFC Editor; sigtran@ietf.org
Subject: Protocol Action: 'Stream Control Transmission Protocol
Management Information Base' to Proposed Standard 


The IESG has approved the Internet-Draft 'Stream Control Transmission 
Protocol Management Information Base' <draft-ietf-sigtran-sctp-mib-10.txt> 
as a Proposed Standard. This document is the product of the Signaling 
Transport Working Group. 

The IESG contact persons are Jon Peterson and Allison Mankin.

Technical Summary

The Stream Control Transmission Protocol (SCTP) is a reliable
transport protocol operating on top of a connectionless packet
network such as IP. It is designed to transport PSTN signaling
messages over the connectionless packet network, but is capable of
broader applications.

This memo defines the Management Information Base (MIB) module which
describes the minimum set of objects needed to manage the
implementation of the SCTP.

There is one existing nit that we need to fix in an RFC-editor note - 
namely that the SIZE restriction of 115 octets on the 
sctpAssocRemHostName needs to be removed (should be 255).
   
Working Group Summary
   
The SIGTRAN WG and the TSVWG WG supported this document.
   
Protocol Quality
   
This specification was reviewed for the IESG by Bert Wijnen and Jon
Peterson. Further MIB review was performed by the participants of 
the mreview mailing list.



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



From exim@www1.ietf.org  Wed Aug 27 22:32:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03559
	for <sigtran-archive@odin.ietf.org>; Wed, 27 Aug 2003 22:32:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sA8a-0008JV-DX
	for sigtran-archive@odin.ietf.org; Wed, 27 Aug 2003 19:55:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7RNteOw031946
	for sigtran-archive@odin.ietf.org; Wed, 27 Aug 2003 19:55:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19s52A-0001R4-9d; Wed, 27 Aug 2003 14:28:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19s2Gv-0007Us-H4
	for sigtran@optimus.ietf.org; Wed, 27 Aug 2003 11:31:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09434
	for <sigtran@ietf.org>; Wed, 27 Aug 2003 11:31:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s2Gt-000188-00
	for sigtran@ietf.org; Wed, 27 Aug 2003 11:31:43 -0400
Received: from [66.180.118.20] (helo=sevis-main.SEVISNORTHDOM)
	by ietf-mx with esmtp (Exim 4.12)
	id 19s2Gs-000161-00
	for sigtran@ietf.org; Wed, 27 Aug 2003 11:31:42 -0400
content-class: urn:content-classes:message
Subject: RE: [Sigtran] FW: Protocol Action: 'Stream Control Transmission Protocol  Management Information Base' to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 27 Aug 2003 10:33:51 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Message-ID: <9B9A9DE704231348A20E8E2CA7696A952140D9@sevis-main.SEVISNORTHDOM>
Thread-Topic: [Sigtran] FW: Protocol Action: 'Stream Control Transmission Protocol  Management Information Base' to Proposed Standard
Thread-Index: AcNsMGRaWVwJ8f2rSxmcA1NUCU5g6QAf/7KQ
From: "Nitin Vairagare" <nitin.vairagare@sevis.com>
To: <sigtran@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

What is the RFC number allocated to this?

Nitin

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]
Sent: Tuesday, August 26, 2003 2:00 PM
To: IETF-Announce
Cc: Internet Architecture Board; RFC Editor; sigtran@ietf.org
Subject: Protocol Action: 'Stream Control Transmission Protocol
Management Information Base' to Proposed Standard=20


The IESG has approved the Internet-Draft 'Stream Control Transmission=20
Protocol Management Information Base'
<draft-ietf-sigtran-sctp-mib-10.txt>=20
as a Proposed Standard. This document is the product of the Signaling=20
Transport Working Group.=20

The IESG contact persons are Jon Peterson and Allison Mankin.

Technical Summary

The Stream Control Transmission Protocol (SCTP) is a reliable
transport protocol operating on top of a connectionless packet
network such as IP. It is designed to transport PSTN signaling
messages over the connectionless packet network, but is capable of
broader applications.

This memo defines the Management Information Base (MIB) module which
describes the minimum set of objects needed to manage the
implementation of the SCTP.

There is one existing nit that we need to fix in an RFC-editor note -=20
namely that the SIZE restriction of 115 octets on the=20
sctpAssocRemHostName needs to be removed (should be 255).
  =20
Working Group Summary
  =20
The SIGTRAN WG and the TSVWG WG supported this document.
  =20
Protocol Quality
  =20
This specification was reviewed for the IESG by Bert Wijnen and Jon
Peterson. Further MIB review was performed by the participants of=20
the mreview mailing list.



_______________________________________________
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



From exim@www1.ietf.org  Thu Aug 28 14:05:50 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05589
	for <sigtran-archive@odin.ietf.org>; Thu, 28 Aug 2003 14:05:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sNCA-00028V-JG
	for sigtran-archive@odin.ietf.org; Thu, 28 Aug 2003 09:52:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7SDqERA008207
	for sigtran-archive@odin.ietf.org; Thu, 28 Aug 2003 09:52:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sKps-00026b-DN; Thu, 28 Aug 2003 07:21:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sIY6-0000VD-4j
	for sigtran@optimus.ietf.org; Thu, 28 Aug 2003 04:54:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18762
	for <sigtran@ietf.org>; Thu, 28 Aug 2003 04:54:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sIY3-0000AU-00
	for sigtran@ietf.org; Thu, 28 Aug 2003 04:54:31 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sIY1-0000AR-00
	for sigtran@ietf.org; Thu, 28 Aug 2003 04:54:29 -0400
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125])
	by albatross-ext.wise.edt.ericsson.se (8.12.9/8.12.9/WIREfire-1.7) with ESMTP id h7S8sQAv008786;
	Thu, 28 Aug 2003 10:54:29 +0200 (MEST)
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id Q9L3LH1T; Thu, 28 Aug 2003 10:54:25 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <Q59KHJKB>; Thu, 28 Aug 2003 10:54:12 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C043317A7@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (KI/EEM)" <j.javier.pastor@ericsson.com>
To: "'Nitin Vairagare'" <nitin.vairagare@sevis.com>, sigtran@ietf.org
Subject: RE: [Sigtran] FW: Protocol Action: 'Stream Control Transmission P
	rotocol  Management Information Base' to Proposed Standard
Date: Thu, 28 Aug 2003 10:54:20 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Hi Nitin,

The RFC number is not assigned yet...

Cheers // Javier.

> -----Original Message-----
> From: Nitin Vairagare [mailto:nitin.vairagare@sevis.com]
> Sent: mi=E9rcoles, 27 de agosto de 2003 17:34
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] FW: Protocol Action: 'Stream Control=20
> Transmission
> Protocol Management Information Base' to Proposed Standard
>=20
>=20
> What is the RFC number allocated to this?
>=20
> Nitin
>=20
> -----Original Message-----
> From: The IESG [mailto:iesg-secretary@ietf.org]
> Sent: Tuesday, August 26, 2003 2:00 PM
> To: IETF-Announce
> Cc: Internet Architecture Board; RFC Editor; sigtran@ietf.org
> Subject: Protocol Action: 'Stream Control Transmission Protocol
> Management Information Base' to Proposed Standard=20
>=20
>=20
> The IESG has approved the Internet-Draft 'Stream Control Transmission =

> Protocol Management Information Base'
> <draft-ietf-sigtran-sctp-mib-10.txt>=20
> as a Proposed Standard. This document is the product of the Signaling =

> Transport Working Group.=20
>=20
> The IESG contact persons are Jon Peterson and Allison Mankin.
>=20
> Technical Summary
>=20
> The Stream Control Transmission Protocol (SCTP) is a reliable
> transport protocol operating on top of a connectionless packet
> network such as IP. It is designed to transport PSTN signaling
> messages over the connectionless packet network, but is capable of
> broader applications.
>=20
> This memo defines the Management Information Base (MIB) module which
> describes the minimum set of objects needed to manage the
> implementation of the SCTP.
>=20
> There is one existing nit that we need to fix in an RFC-editor note - =

> namely that the SIZE restriction of 115 octets on the=20
> sctpAssocRemHostName needs to be removed (should be 255).
>   =20
> Working Group Summary
>   =20
> The SIGTRAN WG and the TSVWG WG supported this document.
>   =20
> Protocol Quality
>   =20
> This specification was reviewed for the IESG by Bert Wijnen and Jon
> Peterson. Further MIB review was performed by the participants of=20
> the mreview mailing list.
>=20
>=20
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Thu Aug 28 19:22:41 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29282
	for <sigtran-archive@odin.ietf.org>; Thu, 28 Aug 2003 19:22:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sVmg-0001Tx-Ny
	for sigtran-archive@odin.ietf.org; Thu, 28 Aug 2003 19:02:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7SN2UOH005680
	for sigtran-archive@odin.ietf.org; Thu, 28 Aug 2003 19:02:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sSha-00016t-PI; Thu, 28 Aug 2003 15:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sPuB-0000kN-DX
	for sigtran@optimus.ietf.org; Thu, 28 Aug 2003 12:45:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29299
	for <sigtran@ietf.org>; Thu, 28 Aug 2003 12:45:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sPu9-0002ZQ-00
	for sigtran@ietf.org; Thu, 28 Aug 2003 12:45:49 -0400
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sPu8-0002ZM-00
	for sigtran@ietf.org; Thu, 28 Aug 2003 12:45:48 -0400
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by penguin-ext.wise.edt.ericsson.se (8.12.9/8.12.9/WIREfire-1.7) with ESMTP id h7SGjl31023022
	for <sigtran@ietf.org>; Thu, 28 Aug 2003 18:45:48 +0200 (MEST)
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id QY1LK95Q; Thu, 28 Aug 2003 18:46:48 +0200
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <QX5HM38N>; Thu, 28 Aug 2003 18:45:50 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C043317AF@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "J.Javier Pastor (KI/EEM)" <j.javier.pastor@ericsson.com>
To: sigtran@ietf.org
Date: Thu, 28 Aug 2003 18:45:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] draft-ietf-sigtran-m3ua-implementors-guide-05.txt
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Hi guys, 

We have submitted a new version of the M3UA implementors' guide including the last conclusions from the mailing list.
You can get it at: http://standards.ericsson.net/javier/draft-ietf-sigtran-m3ua-implementors-guide-05.txt


Cheers // Javier.

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



From exim@www1.ietf.org  Fri Aug 29 02:13:15 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14231
	for <sigtran-archive@odin.ietf.org>; Fri, 29 Aug 2003 02:13:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sa9o-00071d-Lc
	for sigtran-archive@odin.ietf.org; Thu, 28 Aug 2003 23:42:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7T3gePE026999
	for sigtran-archive@odin.ietf.org; Thu, 28 Aug 2003 23:42:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sXp6-0008QO-JI; Thu, 28 Aug 2003 21:13:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sV2x-0008Gx-Da
	for sigtran@optimus.ietf.org; Thu, 28 Aug 2003 18:15:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24599
	for <sigtran@ietf.org>; Thu, 28 Aug 2003 18:15:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sV2u-0000L3-00
	for sigtran@ietf.org; Thu, 28 Aug 2003 18:15:12 -0400
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sV2p-0000Ks-00
	for sigtran@ietf.org; Thu, 28 Aug 2003 18:15:07 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h7SMEaLX029668;
	Thu, 28 Aug 2003 17:14:36 -0500 (CDT)
Message-ID: <3F4E7ECC.9070507@alcatel.com>
Date: Thu, 28 Aug 2003 17:14:36 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
CC: "Brian F. G. Bidulock" <bidulock@openss7.org>
Subject: Re: [Sigtran] M2PA Last Call Comment - RPO
References: <3F15C7F2.6070704@pt.com> <20030716191143.F6725@openss7.org> <3F18328D.1080706@pt.com> <20030718120053.C14760@openss7.org> <3F184959.2040103@pt.com> <20030718133957.A16698@openss7.org> <3F1867CB.6060108@pt.com> <20030724134845.D11627@openss7.org> <3F26BAA2.1080908@pt.com> <3F29983B.2040505@alcatel.com> <20030731165031.A6734@openss7.org> <3F2ACB8B.7090806@pt.com> <3F3D72B2.8050007@alcatel.com> <3F4399C2.6050104@pt.com> <3F4BB19B.2010803@alcatel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Andrew, Brian, et. al.,

It looks to me like either the LPO or RPO end could have messages queued 
in the incoming or outgoing buffers. Even if the LPO end continues 
transmitting after the PO, if the RPO end does not ack these messages, 
they will remain in the LPO end's retransmit buffer. If MTP3 sends a 
Flush command, these messages need to be flushed at both ends.

So I merged the statements about the Flush command into one list, since 
I think they are the same for both LPO and RPO.

I confess to some weasel language regarding resynchronization. But my 
defense is that Q.703 does not say much about it either. As long as the 
BSN in the LS PR message is set correctly, the receiving end has the 
information it needs.

Here is my latest attempt at the Proc Outage section. Everyone please 
criticize.

tomG.

=====
4.1.4 Processor Outage

The Link Status Processor Outage message replaces the SIPO message of
MTP2. Unlike MTP2, the message SHOULD NOT be transmitted
continuously. M2PA SHALL send a Link Status Processor Outage message
to its peer at the beginning of a processor outage condition where
MTP2 would send SIPO. M2PA MAY send additional Link Status Processor
Outage messages as long as that condition persists.

When the local processor outage condition ends, M2PA SHALL send a Link
Status Processor Recovered message to its peer. This message is used
to signal the end of the processor outage condition, instead of an MSU
or FISU as in MTP2. The BSN in the Link Status Processor Recovered
message is set to the FSN of the last User Data message received from
the peer M2PA. The BSN value in the Link Status Processor Recovered
message is used by the peer to resynchronize its sequence numbers, if
this is required by MTP2.

While in a local processor outage condition:

    (a) Any User Data messages received from the peer MUST NOT be
        acknowledged and MUST be buffered.

    (b) M2PA SHOULD continue to acknowledge User Data messages received
        and accepted by MTP3 before the local processor outage.

    (c) M2PA SHOULD continue to transmit messages that have been sent
        by its upper layer MTP3.

While there is a remote processor outage condition:

    (a) M2PA SHOULD continue to acknowledge User Data messages received
        and accepted by MTP3 regardless of the remote processor outage.

    (b) If any User Data messages received from the peer after the Link
        Status Processor Outage cannot be delivered to MTP3, then these
        messages MUST NOT be acknowledged and MUST be buffered.

If M2PA receives a Flush command from MTP3,

    (a) M2PA SHALL discard any incoming messages that were queued and
        unacknowledged during the processor outage condition.

    (b) M2PA SHALL discard messages in the transmit and retransmit
        queues as required by MTP2.

    (c) If resynchronization of sequence numbers is required, M2PA MAY
        perform resynchronization of sequence numbers using the BSN
        from the received Link Status Processor Recovered message.
        However, during resychronization, M2PA SHALL NOT discard any
        received User Data messages.

Note that because the Link Status and User Data messages are sent on
separate streams, it is possible for a User Data message sent after
the Link Status Processor Recovered message to arrive before
it. Therefore, when flushing buffers, M2PA must take care not to flush
messages sent after the remote processor recovered. M2PA SHOULD NOT
flush User Data messages with FSN greater than the FSN in the Link
Status Processor Recovered message.

If M2PA receives a Continue command from MTP3, M2PA SHALL begin
processing the incoming messages that were queued and unacknowledged
during the processor outage condition.

When M2PA experiences a local processor outage, it MAY put the link
out of service by sending a Link Status Out of Service message if
allowed by the applicable MTP2 standard (e.g., [Q.2140]).

In other respects, M2PA SHOULD follow the same procedures as MTP2 in
processor outage.

=====



-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
*   I actively disclaim speaking for Alcatel.  I do not purport to    *
*   advertise or represent its position, operations, or activities.   *


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



From exim@www1.ietf.org  Sat Aug 30 01:17:51 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10251
	for <sigtran-archive@odin.ietf.org>; Sat, 30 Aug 2003 01:17:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19svem-0002Ay-I2
	for sigtran-archive@odin.ietf.org; Fri, 29 Aug 2003 22:40:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7U2e4H9008337
	for sigtran-archive@odin.ietf.org; Fri, 29 Aug 2003 22:40:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19stl9-0004NV-Qn; Fri, 29 Aug 2003 20:38:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19spG1-0000pL-HY
	for sigtran@optimus.ietf.org; Fri, 29 Aug 2003 15:50:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29296
	for <sigtran@ietf.org>; Fri, 29 Aug 2003 15:49:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19spFz-0005HL-00
	for sigtran@ietf.org; Fri, 29 Aug 2003 15:50:03 -0400
Received: from angelica.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19spFy-0005GZ-00
	for sigtran@ietf.org; Fri, 29 Aug 2003 15:50:02 -0400
Received: from pckhusidp (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id PAA20666
	for <sigtran@ietf.org>; Fri, 29 Aug 2003 15:49:28 -0400 (EDT)
From: "Anatoly Khusid" <anatoly.khusid@ulticom.com>
To: <sigtran@ietf.org>
Date: Fri, 29 Aug 2003 15:47:56 -0400
Message-ID: <005901c36e66$72356f90$5a2119ac@pckhusidp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <3F4E7ECC.9070507@alcatel.com>
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] question on draft-bidulock-sigtran-m2pa-test-04
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hello,

I am looking at section 3.1.6.1 (Correct Procedure (Data) with Proving).
I don't understand why DATA-ACK is <-000000, FFFFFF--
I assume this means FSN=000000 and BSN=FFFFFF ?  If yes, then why BSN=FFFFF,
I thought it should be set to 0 (peer's FSN).

Thanks

Anatoly


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



From exim@www1.ietf.org  Sat Aug 30 05:03:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02796
	for <sigtran-archive@odin.ietf.org>; Sat, 30 Aug 2003 05:03:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19t19x-0002r0-2v
	for sigtran-archive@odin.ietf.org; Sat, 30 Aug 2003 04:32:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7U8WYx7010945
	for sigtran-archive@odin.ietf.org; Sat, 30 Aug 2003 04:32:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19szWk-0006Vt-Lq; Sat, 30 Aug 2003 02:48:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sxSD-0006jd-Tx
	for sigtran@optimus.ietf.org; Sat, 30 Aug 2003 00:35:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08472
	for <sigtran@ietf.org>; Sat, 30 Aug 2003 00:35:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sxSB-00068T-00
	for sigtran@ietf.org; Sat, 30 Aug 2003 00:35:11 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[QGLMUjRZlZs6bLa8ze3QWnGiDPugM1FP])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sxSA-00068P-00
	for sigtran@ietf.org; Sat, 30 Aug 2003 00:35:10 -0400
Received: from ns.pigworks.openss7.net (IDENT:JPLfONmfxQpDXs14NK2a6fJcT5PyL027@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h7U4ZAa07351;
	Fri, 29 Aug 2003 22:35:10 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h7U4Z9u21379;
	Fri, 29 Aug 2003 22:35:09 -0600
Date: Fri, 29 Aug 2003 22:35:09 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Anatoly Khusid <anatoly.khusid@ulticom.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] question on draft-bidulock-sigtran-m2pa-test-04
Message-ID: <20030829223509.A21281@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Anatoly Khusid <anatoly.khusid@ulticom.com>,
	sigtran@ietf.org
References: <3F4E7ECC.9070507@alcatel.com> <005901c36e66$72356f90$5a2119ac@pckhusidp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <005901c36e66$72356f90$5a2119ac@pckhusidp>; from anatoly.khusid@ulticom.com on Fri, Aug 29, 2003 at 03:47:56PM -0400
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
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>

Anatoly,

The IUT in the test has not sent any DATA messages and therefore, ala Q.703,
it's SN is -1 (FFFFFF) not 0.  The first data message sent is 0.

--brian

Anatoly Khusid wrote:                                                              (Fri, 29 Aug 2003 15:47:56)
> Hello,
> 
> I am looking at section 3.1.6.1 (Correct Procedure (Data) with Proving).
> I don't understand why DATA-ACK is <-000000, FFFFFF--
> I assume this means FSN=000000 and BSN=FFFFFF ?  If yes, then why BSN=FFFFF,
> I thought it should be set to 0 (peer's FSN).
> 
> Thanks
> 
> Anatoly
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

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



