
From anandnilkal@gmail.com  Mon Jan  3 23:50:18 2011
Return-Path: <anandnilkal@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 137BD3A6B53 for <sigtran@core3.amsl.com>; Mon,  3 Jan 2011 23:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.353
X-Spam-Level: 
X-Spam-Status: No, score=-2.353 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_05=-1.11, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6J5L8kDheTH for <sigtran@core3.amsl.com>; Mon,  3 Jan 2011 23:50:17 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id C44583A6B4E for <sigtran@ietf.org>; Mon,  3 Jan 2011 23:50:16 -0800 (PST)
Received: by gwj17 with SMTP id 17so7879215gwj.31 for <sigtran@ietf.org>; Mon, 03 Jan 2011 23:52:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=EmQ6XZw6C8CTqhz9rqw6dmNelcnioHRpM0F+NRevQ9Y=; b=WOBkDMukl0++/9BjPnk93DHnlgtbJuw8Ifw5k5KVp0g9Zjocymp7ZOUZx82LwU0TZQ eaZqQjIxDj/9OsTuhMoW6k4qsIGwJT05KRouxcs8S9DaV/C/ioy5gRVgTimNc7gWl7LN XQ5e8kybwKltOfTse937GKLII4oBrdM5kKGuM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=r/wY5/DnoXIlELOd19esva9luEGWwHXWjcs6fkEwQQt9iCvDvzz14MwwoB0NnuI1/v 9bxYhTbMEfAH8nA8W0gsE5jXvc/YF4+utsBSUYyPfDtH2yAfcY2slhAEOLR2CX4LM2c6 RUXMv2ZfV8N8PIRNjLACAzxwJnXwRgMW2zx/M=
MIME-Version: 1.0
Received: by 10.236.111.39 with SMTP id v27mr4071821yhg.43.1294127543607; Mon, 03 Jan 2011 23:52:23 -0800 (PST)
Received: by 10.236.108.145 with HTTP; Mon, 3 Jan 2011 23:52:23 -0800 (PST)
Date: Tue, 4 Jan 2011 13:22:23 +0530
Message-ID: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com>
From: Anand N Ilkal <anandnilkal@gmail.com>
To: sigtran@ietf.org
Content-Type: multipart/alternative; boundary=0023547c96c987e1670499008c62
Subject: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 07:50:18 -0000

--0023547c96c987e1670499008c62
Content-Type: text/plain; charset=ISO-8859-1

Hello,

i have doubt regarding the following section is RFC 4666  -
4.3.4.3.  ASP Active Procedures

   Anytime after the ASP has received an ASP Up Ack message from the SGP
   or IPSP, the ASP MAY send an ASP Active message to the SGP,
   indicating that the ASP is ready to start processing traffic....

1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
2. is receipt of ASP Up Ack message is treated as sufficient condition,
whereas there is a necessary condition which should be satisfied so as ASP
active message is sent? if so, what is that condition?

-- 
with regards,
Anand kumar Ilkal

--0023547c96c987e1670499008c62
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div><div>Hello,</div><div><br></div><div>i have doubt regarding the follow=
ing section is RFC 4666 =A0-=A0</div><div>4.3.4.3. =A0ASP Active Procedures=
</div><div><br></div><div>=A0=A0 Anytime after the ASP has received an ASP =
Up Ack message from the SGP</div>
<div>=A0=A0 or IPSP, the ASP MAY send an ASP Active message to the SGP,</di=
v><div>=A0=A0 indicating that the ASP is ready to start processing traffic.=
...</div><div>=A0=A0=A0</div><div>1. why ASP MAY chose not to send ASP acti=
ve on receipt of ASP Up Ack?</div>
<div>2. is receipt of ASP Up Ack message is treated as sufficient condition=
, whereas there is a necessary condition which should be satisfied so as AS=
P active message is sent? if so, what is that condition?</div><div><br>
</div>-- <br>with regards,<br>Anand kumar Ilkal<br>
</div>

--0023547c96c987e1670499008c62--

From deepak.gunjal@aricent.com  Tue Jan  4 00:05:40 2011
Return-Path: <deepak.gunjal@aricent.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B989A3A6B54 for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 00:05:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6fZGT-QK-Cnu for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 00:05:39 -0800 (PST)
Received: from jaguar.aricent.com (jaguar.aricent.com [180.151.2.24]) by core3.amsl.com (Postfix) with ESMTP id BEA253A6B53 for <sigtran@ietf.org>; Tue,  4 Jan 2011 00:05:38 -0800 (PST)
Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 72F9E36B9A; Tue,  4 Jan 2011 13:35:14 +0530 (IST)
Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (Postfix) with ESMTP id 5D06336B99; Tue,  4 Jan 2011 13:35:14 +0530 (IST)
Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Tue, 4 Jan 2011 13:37:43 +0530
From: Deepak Gunjal <deepak.gunjal@aricent.com>
To: Anand N Ilkal <anandnilkal@gmail.com>, "sigtran@ietf.org" <sigtran@ietf.org>
Date: Tue, 4 Jan 2011 13:37:41 +0530
Thread-Topic: [Sigtran] ASP active procedure
Thread-Index: Acur5Fa27huTCHnfTuKtdmExGt7ikwAAW27Q
Message-ID: <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com>
In-Reply-To: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_DF735188ED91BD458FA0E0C17929339F013665CCD9GUREXMB01ASIA_"
MIME-Version: 1.0
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 08:05:40 -0000

--_000_DF735188ED91BD458FA0E0C17929339F013665CCD9GUREXMB01ASIA_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As per my opinion the ASP ACTIVE is triggered after the reception of ASP UP=
 ACK only but the trigger point may not be immediate. The trigger point can=
 be an indication from high availability framework; it could be some applic=
ation logic which once determines via local procedures that it is ready to =
process the application traffic from network can initiate ASP ACTIVE to SGP=
.

Regards
Deepak

________________________________
From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On Behalf =
Of Anand N Ilkal
Sent: Tuesday, January 04, 2011 1:22 PM
To: sigtran@ietf.org
Subject: [Sigtran] ASP active procedure

Hello,

i have doubt regarding the following section is RFC 4666  -
4.3.4.3.  ASP Active Procedures

   Anytime after the ASP has received an ASP Up Ack message from the SGP
   or IPSP, the ASP MAY send an ASP Active message to the SGP,
   indicating that the ASP is ready to start processing traffic....

1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
2. is receipt of ASP Up Ack message is treated as sufficient condition, whe=
reas there is a necessary condition which should be satisfied so as ASP act=
ive message is sent? if so, what is that condition?

--
with regards,
Anand kumar Ilkal

________________________________
"DISCLAIMER: This message is proprietary to Aricent and is intended solely =
for the use of the individual to whom it is addressed. It may contain privi=
leged 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 m=
essage in error, please notify the originator immediately. If you are not t=
he intended recipient, you are notified that you are strictly prohibited fr=
om using, copying, altering, or disclosing the contents of this message. Ar=
icent accepts no responsibility for loss or damage arising from the use of =
the information transmitted by this email including damage from virus."

--_000_DF735188ED91BD458FA0E0C17929339F013665CCD9GUREXMB01ASIA_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h4
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.6in;
	text-indent:-.6in;
	page-break-after:avoid;
	mso-list:l0 level4 lfo1;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:69;
	mso-list-template-ids:439751080;}
@list l0:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l0:level3
	{mso-level-suffix:space;
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	mso-ansi-font-size:12.0pt;
	mso-ascii-font-family:Arial;
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:Arial;
	font-variant:normal !important;
	color:windowtext;
	mso-text-animation:none;
	text-transform:none;
	position:relative;
	top:0pt;
	mso-text-raise:0pt;
	letter-spacing:0pt;
	border:none;
	mso-font-width:100%;
	mso-font-kerning:0pt;
	text-shadow:none;
	text-effect:none;
	text-effect:none;
	mso-bidi-font-weight:bold;
	mso-bidi-font-style:normal;
	text-decoration:none;
	text-underline:none;
	text-decoration:none;
	text-line-through:none;}
@list l0:level4
	{mso-level-style-link:"Heading 4";
	mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.6in;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l0:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.7in;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l0:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:.8in;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l0:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:.9in;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">As per my opinion the ASP ACTIVE is tr=
iggered after the reception of ASP UP ACK only but the trigger point may no=
t be immediate. The
 trigger point can be an indication from high availability framework; it co=
uld be some application logic which once determines via local procedures th=
at it is ready to process the application traffic from network can initiate=
 ASP ACTIVE to SGP.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Regards<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Deepak<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0pt">
<hr size=3D"2" width=3D"100%" align=3D"center" tabindex=3D"-1">
</span></font></div>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span style=3D"f=
ont-size:10.0pt;
font-family:Tahoma;font-weight:bold">From:</span></font></b><font size=3D"2=
" face=3D"Tahoma"><span style=3D"font-size:10.0pt;font-family:Tahoma"> sigt=
ran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org]
<b><span style=3D"font-weight:bold">On Behalf Of </span></b>Anand N Ilkal<b=
r>
<b><span style=3D"font-weight:bold">Sent:</span></b> Tuesday, January 04, 2=
011 1:22 PM<br>
<b><span style=3D"font-weight:bold">To:</span></b> sigtran@ietf.org<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> [Sigtran] ASP activ=
e procedure</span></font><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">Hello,<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">i have doubt regarding the following section is RFC 4666 &nbsp;-&nb=
sp;<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">4.3.4.3. &nbsp;ASP Active Procedures<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">&nbsp;&nbsp; Anytime after the ASP has received an ASP Up Ack messa=
ge from the SGP<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">&nbsp;&nbsp; or IPSP, the ASP MAY send an ASP Active message to the=
 SGP,<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">&nbsp;&nbsp; indicating that the ASP is ready to start processing t=
raffic....<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">&nbsp;&nbsp;&nbsp;<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ac=
k?<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">2. is receipt of ASP Up Ack message is treated as sufficient condit=
ion, whereas there is a necessary condition which should be satisfied so as=
 ASP active message is
 sent? if so, what is that condition?<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">--
<br>
with regards,<br>
Anand kumar Ilkal<o:p></o:p></span></font></p>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"3">&quot;DISCLAIMER: This messa=
ge is proprietary to Aricent and is intended solely for the use of the indi=
vidual to whom it is addressed. It may contain privileged or confidential i=
nformation and should not be circulated or
 used for any purpose other than for what it is intended. If you have recei=
ved this message in error, please notify the originator immediately. If you=
 are not the intended recipient, you are notified that you are strictly pro=
hibited from using, copying, altering,
 or disclosing the contents of this message. Aricent accepts no responsibil=
ity for loss or damage arising from the use of the information transmitted =
by this email including damage from virus.&quot;<br>
</font>
</body>
</html>

--_000_DF735188ED91BD458FA0E0C17929339F013665CCD9GUREXMB01ASIA_--

From arif15jan@gmail.com  Tue Jan  4 00:29:26 2011
Return-Path: <arif15jan@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 07FDB3A6B54 for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 00:29:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eh1+pOmpBNo1 for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 00:29:25 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id ED0E03A6982 for <sigtran@ietf.org>; Tue,  4 Jan 2011 00:29:24 -0800 (PST)
Received: by qwg5 with SMTP id 5so14970948qwg.31 for <sigtran@ietf.org>; Tue, 04 Jan 2011 00:31:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ImCU/NlEdfDvdXXQsSu+ROj7rQXDNaK5a/58cJ9Ow7s=; b=hyDIVADkf1ymI7lRg8KVeHLF+8CeA2gHAZlaQiNUZhfcwgSL5AUIiqjkxhGBBd9G8i ACYBO/BpUfP5+Oi38uTS4bCr34FAi2vC7R+clFROaYZ1VUFYQRnOj+mE5wXjsJgO1FOQ 3Juc13V8uMnHm4lvFXjOg28k1Wn0pW5yON7W0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QcqsVT6ru27OuEw8l5k7fY+PUn4j4dguFMXYG4RKmOa+D2uUvIrL/h4DuwCSis9iqh M4JLUWSPsL2KVCdAos3VjDezrjExhocQ4c3Ge9Ye3izMWXAuZ78/ycFQW+maxlf7+Gde zBQB/h5usppp58e89HHtOVvkdMaqVoHjnVlU4=
MIME-Version: 1.0
Received: by 10.224.181.141 with SMTP id by13mr20490408qab.98.1294129891475; Tue, 04 Jan 2011 00:31:31 -0800 (PST)
Received: by 10.220.75.3 with HTTP; Tue, 4 Jan 2011 00:31:31 -0800 (PST)
In-Reply-To: <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM>
Date: Tue, 4 Jan 2011 14:01:31 +0530
Message-ID: <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com>
From: arif khan <arif15jan@gmail.com>
To: Deepak Gunjal <deepak.gunjal@aricent.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Anand N Ilkal <anandnilkal@gmail.com>, "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 08:29:26 -0000

Implementation logic is ok in their own context ...........
But ASP can process the TRAFFIC message only after the ASP ACT ACK
received from the NW and local side ASP with the remote ASP change
their state and becomes ready to process the TRAFFIC.









On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
> As per my opinion the ASP ACTIVE is triggered after the reception of ASP UP
> ACK only but the trigger point may not be immediate. The trigger point can
> be an indication from high availability framework; it could be some
> application logic which once determines via local procedures that it is
> ready to process the application traffic from network can initiate ASP
> ACTIVE to SGP.
>
> Regards
> Deepak
>
> ________________________________
> From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On Behalf
> Of Anand N Ilkal
> Sent: Tuesday, January 04, 2011 1:22 PM
> To: sigtran@ietf.org
> Subject: [Sigtran] ASP active procedure
>
> Hello,
>
> i have doubt regarding the following section is RFC 4666  -
> 4.3.4.3.  ASP Active Procedures
>
>    Anytime after the ASP has received an ASP Up Ack message from the SGP
>    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>    indicating that the ASP is ready to start processing traffic....
>
> 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
> 2. is receipt of ASP Up Ack message is treated as sufficient condition,
> whereas there is a necessary condition which should be satisfied so as ASP
> active message is sent? if so, what is that condition?
>
> --
> with regards,
> Anand kumar Ilkal
>
> ________________________________
> "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising from
> the use of the information transmitted by this email including damage from
> virus."
>

From anandnilkal@gmail.com  Tue Jan  4 02:16:55 2011
Return-Path: <anandnilkal@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 88FB13A6B5A for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 02:16:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ED2ZfGsxwY2i for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 02:16:54 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 433EF3A6B59 for <sigtran@ietf.org>; Tue,  4 Jan 2011 02:16:54 -0800 (PST)
Received: by gyd12 with SMTP id 12so6176616gyd.31 for <sigtran@ietf.org>; Tue, 04 Jan 2011 02:19:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=kLruwnK1pvUwVU5419aXgVXoAo7ldP7jr65ZFu8NpsY=; b=KurnQFLE264VccBdd2b4onMXXTRyfqjIJMpylp3kH7ZK0+7R4ARPbkczK2Q41oCmq4 c4Ww/mGZtloJncVg9CWMb48y6qvjyApO5/ttmgYSobV5FzIDvEMyT3EycQYcDT9I9TNj F0HcN5joO3B+nE/iIDrAsigQutCJesh9sh21k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TvFlUlPTijLqmyxLsTyW5mu68mCS4NNe+C/lNAPFcxVHr9If8FyHmnb8ojNkT26kdy dc9V4MUIw7oRZYBdCJoDQq+uhlhvA5ZZHOGVa0HloVEJOCFIpe6ah9Gitwj9BO2swa6o vCLreyIw7Gkb5IrMLfNcGsvE7cyB+HO2xBves=
MIME-Version: 1.0
Received: by 10.236.108.43 with SMTP id p31mr16077031yhg.69.1294136340992; Tue, 04 Jan 2011 02:19:00 -0800 (PST)
Received: by 10.236.108.145 with HTTP; Tue, 4 Jan 2011 02:19:00 -0800 (PST)
In-Reply-To: <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com>
Date: Tue, 4 Jan 2011 15:49:00 +0530
Message-ID: <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com>
From: Anand N Ilkal <anandnilkal@gmail.com>
To: arif khan <arif15jan@gmail.com>, Deepak Gunjal <deepak.gunjal@aricent.com>
Content-Type: multipart/alternative; boundary=90e6ba4fbe2ee5591104990298e4
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 10:16:55 -0000

--90e6ba4fbe2ee5591104990298e4
Content-Type: text/plain; charset=ISO-8859-1

Hello Deepak,

I understand that there needs to be local check whether stack is ready to
receive traffic for that routing key.

lets assume all those scenarios are satisfied. and i am pretty sure that
when RFC says MAY, it has taken all these cases into account (for example
you can read from NOTIFY procedures - for NOTIFY to be sent, lot of
conditions needs to be satisfied - like n number of ASP's being active. Yet
RFC uses the words like MUST or SHOULD) .

If traffic modes are to be taken into account, what should act as trigger
for sending ASP Active message from a perticular ASP?

Hence my opinion is ASP Up Ack is only a sufficient condition, where-as
NOTIFY from peer acts as necessary condition.
can any comment on that?

On 4 January 2011 14:01, arif khan <arif15jan@gmail.com> wrote:

> Implementation logic is ok in their own context ...........
> But ASP can process the TRAFFIC message only after the ASP ACT ACK
> received from the NW and local side ASP with the remote ASP change
> their state and becomes ready to process the TRAFFIC.
>
>
>
>
>
>
>
>
>
> On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
> > As per my opinion the ASP ACTIVE is triggered after the reception of ASP
> UP
> > ACK only but the trigger point may not be immediate. The trigger point
> can
> > be an indication from high availability framework; it could be some
> > application logic which once determines via local procedures that it is
> > ready to process the application traffic from network can initiate ASP
> > ACTIVE to SGP.
> >
> > Regards
> > Deepak
> >
> > ________________________________
> > From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On
> Behalf
> > Of Anand N Ilkal
> > Sent: Tuesday, January 04, 2011 1:22 PM
> > To: sigtran@ietf.org
> > Subject: [Sigtran] ASP active procedure
> >
> > Hello,
> >
> > i have doubt regarding the following section is RFC 4666  -
> > 4.3.4.3.  ASP Active Procedures
> >
> >    Anytime after the ASP has received an ASP Up Ack message from the SGP
> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
> >    indicating that the ASP is ready to start processing traffic....
> >
> > 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
> > 2. is receipt of ASP Up Ack message is treated as sufficient condition,
> > whereas there is a necessary condition which should be satisfied so as
> ASP
> > active message is sent? if so, what is that condition?
> >
> > --
> > with regards,
> > Anand kumar Ilkal
> >
> > ________________________________
> > "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising
> from
> > the use of the information transmitted by this email including damage
> from
> > virus."
> >
>



-- 
with regards,
Anand kumar Ilkal

--90e6ba4fbe2ee5591104990298e4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Deepak,<div><br></div><div>I understand that there needs to be local =
check whether stack is ready to receive traffic for that routing key.=A0</d=
iv><div><br></div><div>lets assume all those scenarios are satisfied. and i=
=A0am pretty sure that when RFC says MAY, it has taken all these cases into=
 account (for example you can read from NOTIFY procedures - for NOTIFY to b=
e sent, lot of conditions needs to be satisfied - like n number of ASP&#39;=
s being active. Yet RFC uses the words like MUST or SHOULD) .</div>
<div><br></div><div>If traffic modes are to be taken into account, what sho=
uld act as trigger for sending ASP Active message from a perticular ASP?</d=
iv><div><br></div><div>Hence my opinion is ASP Up Ack is only a sufficient =
condition, where-as NOTIFY from peer acts as necessary condition.</div>
<div>can any comment on that?</div><div><br><div class=3D"gmail_quote">On 4=
 January 2011 14:01, arif khan <span dir=3D"ltr">&lt;<a href=3D"mailto:arif=
15jan@gmail.com">arif15jan@gmail.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex;">
Implementation logic is ok in their own context ...........<br>
But ASP can process the TRAFFIC message only after the ASP ACT ACK<br>
received from the NW and local side ASP with the remote ASP change<br>
their state and becomes ready to process the TRAFFIC.<br>
<div><div></div><div class=3D"h5"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 1/4/11, Deepak Gunjal &lt;<a href=3D"mailto:deepak.gunjal@aricent.com">d=
eepak.gunjal@aricent.com</a>&gt; wrote:<br>
&gt; As per my opinion the ASP ACTIVE is triggered after the reception of A=
SP UP<br>
&gt; ACK only but the trigger point may not be immediate. The trigger point=
 can<br>
&gt; be an indication from high availability framework; it could be some<br=
>
&gt; application logic which once determines via local procedures that it i=
s<br>
&gt; ready to process the application traffic from network can initiate ASP=
<br>
&gt; ACTIVE to SGP.<br>
&gt;<br>
&gt; Regards<br>
&gt; Deepak<br>
&gt;<br>
&gt; ________________________________<br>
&gt; From: <a href=3D"mailto:sigtran-bounces@ietf.org">sigtran-bounces@ietf=
.org</a> [mailto:<a href=3D"mailto:sigtran-bounces@ietf.org">sigtran-bounce=
s@ietf.org</a>] On Behalf<br>
&gt; Of Anand N Ilkal<br>
&gt; Sent: Tuesday, January 04, 2011 1:22 PM<br>
&gt; To: <a href=3D"mailto:sigtran@ietf.org">sigtran@ietf.org</a><br>
&gt; Subject: [Sigtran] ASP active procedure<br>
&gt;<br>
&gt; Hello,<br>
&gt;<br>
&gt; i have doubt regarding the following section is RFC 4666 =A0-<br>
&gt; 4.3.4.3. =A0ASP Active Procedures<br>
&gt;<br>
&gt; =A0 =A0Anytime after the ASP has received an ASP Up Ack message from t=
he SGP<br>
&gt; =A0 =A0or IPSP, the ASP MAY send an ASP Active message to the SGP,<br>
&gt; =A0 =A0indicating that the ASP is ready to start processing traffic...=
.<br>
&gt;<br>
&gt; 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?<=
br>
&gt; 2. is receipt of ASP Up Ack message is treated as sufficient condition=
,<br>
&gt; whereas there is a necessary condition which should be satisfied so as=
 ASP<br>
&gt; active message is sent? if so, what is that condition?<br>
&gt;<br>
&gt; --<br>
&gt; with regards,<br>
&gt; Anand kumar Ilkal<br>
&gt;<br>
&gt; ________________________________<br>
&gt; &quot;DISCLAIMER: This message is proprietary to Aricent and is intend=
ed solely<br>
&gt; for the use of the individual to whom it is addressed. It may contain<=
br>
&gt; privileged or confidential information and should not be circulated or=
 used<br>
&gt; for any purpose other than for what it is intended. If you have receiv=
ed<br>
&gt; this message in error, please notify the originator immediately. If yo=
u are<br>
&gt; not the intended recipient, you are notified that you are strictly<br>
&gt; prohibited from using, copying, altering, or disclosing the contents o=
f this<br>
&gt; message. Aricent accepts no responsibility for loss or damage arising =
from<br>
&gt; the use of the information transmitted by this email including damage =
from<br>
&gt; virus.&quot;<br>
&gt;<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>with regard=
s,<br>Anand kumar Ilkal<br>
</div>

--90e6ba4fbe2ee5591104990298e4--

From deepak.gunjal@aricent.com  Tue Jan  4 02:59:04 2011
Return-Path: <deepak.gunjal@aricent.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABCFC3A698E for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 02:59:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G3615gzOB8Q7 for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 02:59:03 -0800 (PST)
Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by core3.amsl.com (Postfix) with ESMTP id E00113A6B3F for <sigtran@ietf.org>; Tue,  4 Jan 2011 02:59:01 -0800 (PST)
Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 555D436BB3; Tue,  4 Jan 2011 16:28:37 +0530 (IST)
Received: from GUREXHT01.ASIAN.AD.ARICENT.COM (gurexht01.asian.ad.aricent.com [10.203.171.136]) by jaguar.aricent.com (Postfix) with ESMTP id 3E03936B98; Tue,  4 Jan 2011 16:28:37 +0530 (IST)
Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by GUREXHT01.ASIAN.AD.ARICENT.COM ([10.203.171.137]) with mapi; Tue, 4 Jan 2011 16:31:06 +0530
From: Deepak Gunjal <deepak.gunjal@aricent.com>
To: Anand N Ilkal <anandnilkal@gmail.com>, arif khan <arif15jan@gmail.com>
Date: Tue, 4 Jan 2011 16:31:05 +0530
Thread-Topic: [Sigtran] ASP active procedure
Thread-Index: Acur+M+wuQ0dPd05TJCiXvIMBUWvvAAASiEg
Message-ID: <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com>
In-Reply-To: <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_DF735188ED91BD458FA0E0C17929339F013665CEA2GUREXMB01ASIA_"
MIME-Version: 1.0
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 10:59:04 -0000

--_000_DF735188ED91BD458FA0E0C17929339F013665CEA2GUREXMB01ASIA_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Anand,

Generally the application logic is treated separately from the transport la=
yer which is here M3UA layer. So it is not necessary that if the transport =
layer is ready at a node then its application layer will also be in a ready=
 state.

The M3UA ASP UP message signifies the availability of transport function at=
 ASP but not about the application layer processing function on the same AS=
P. Also in similar fashion SGP sends ASP UP Ack to indicate its availabilit=
y to accept the protocol messages only.

By sending ASP ACTIVE an ASP indicates that now it can generate and process=
 the user layer traffic and by sending ASP ACTIVE Ack SGP also indicates th=
e same.

So there is a distinction as I interpret the RFC for having TWO different m=
essages viz. ASP UP and ASP ACTIVE which I think have been designed for suc=
h aspects. Also note that the application subsequently can initiate ASP ACT=
IVE from another ASP. The interpretation is now in the context of the traff=
ic mode. So in Override mode the ASP which has generated the ASP AC will ta=
ke on the active role, in case of loadshare it will be kind of parallel pro=
cessing and in broadcast all the ASPs will process the same traffic simulta=
neously.

That means there is some control function which will decide when the applic=
ation is ready and traffic can be started. Now I may design my system which=
 will first complete all the application level readiness functions and then=
 will start with ASP UP. In that case it is possible that as soon as I rece=
ive and ASP UP ack I will send ASP ACT immediately.

To answer your question if ASP AC can be triggered from a particular ASP I =
would say yes when ASPs are running in high availability framework it is th=
e framework which directs a particular ASP to assume ACTIVE role and then o=
nly that specific ASP will initiate the ASP ACK message to SGP. The framewo=
rk may determine the active ASP based on multiple factors like nodes priori=
ty in that framework, its previous restart history, the state of applicatio=
n functions etc.

Regards
Deepak
________________________________
From: Anand N Ilkal [mailto:anandnilkal@gmail.com]
Sent: Tuesday, January 04, 2011 3:49 PM
To: arif khan; Deepak Gunjal
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] ASP active procedure

Hello Deepak,

I understand that there needs to be local check whether stack is ready to r=
eceive traffic for that routing key.

lets assume all those scenarios are satisfied. and i am pretty sure that wh=
en RFC says MAY, it has taken all these cases into account (for example you=
 can read from NOTIFY procedures - for NOTIFY to be sent, lot of conditions=
 needs to be satisfied - like n number of ASP's being active. Yet RFC uses =
the words like MUST or SHOULD) .

If traffic modes are to be taken into account, what should act as trigger f=
or sending ASP Active message from a perticular ASP?

Hence my opinion is ASP Up Ack is only a sufficient condition, where-as NOT=
IFY from peer acts as necessary condition.
can any comment on that?

On 4 January 2011 14:01, arif khan <arif15jan@gmail.com<mailto:arif15jan@gm=
ail.com>> wrote:
Implementation logic is ok in their own context ...........
But ASP can process the TRAFFIC message only after the ASP ACT ACK
received from the NW and local side ASP with the remote ASP change
their state and becomes ready to process the TRAFFIC.









On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com<mailto:deepak.gunjal@ar=
icent.com>> wrote:
> As per my opinion the ASP ACTIVE is triggered after the reception of ASP =
UP
> ACK only but the trigger point may not be immediate. The trigger point ca=
n
> be an indication from high availability framework; it could be some
> application logic which once determines via local procedures that it is
> ready to process the application traffic from network can initiate ASP
> ACTIVE to SGP.
>
> Regards
> Deepak
>
> ________________________________
> From: sigtran-bounces@ietf.org<mailto:sigtran-bounces@ietf.org> [mailto:s=
igtran-bounces@ietf.org<mailto:sigtran-bounces@ietf.org>] On Behalf
> Of Anand N Ilkal
> Sent: Tuesday, January 04, 2011 1:22 PM
> To: sigtran@ietf.org<mailto:sigtran@ietf.org>
> Subject: [Sigtran] ASP active procedure
>
> Hello,
>
> i have doubt regarding the following section is RFC 4666  -
> 4.3.4.3.  ASP Active Procedures
>
>    Anytime after the ASP has received an ASP Up Ack message from the SGP
>    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>    indicating that the ASP is ready to start processing traffic....
>
> 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
> 2. is receipt of ASP Up Ack message is treated as sufficient condition,
> whereas there is a necessary condition which should be satisfied so as AS=
P
> active message is sent? if so, what is that condition?
>
> --
> with regards,
> Anand kumar Ilkal
>
> ________________________________
> "DISCLAIMER: This message is proprietary to Aricent and is intended solel=
y
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or us=
ed
> 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 a=
re
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of t=
his
> message. Aricent accepts no responsibility for loss or damage arising fro=
m
> the use of the information transmitted by this email including damage fro=
m
> virus."
>



--
with regards,
Anand kumar Ilkal

________________________________
"DISCLAIMER: This message is proprietary to Aricent and is intended solely =
for the use of the individual to whom it is addressed. It may contain privi=
leged 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 m=
essage in error, please notify the originator immediately. If you are not t=
he intended recipient, you are notified that you are strictly prohibited fr=
om using, copying, altering, or disclosing the contents of this message. Ar=
icent accepts no responsibility for loss or damage arising from the use of =
the information transmitted by this email including damage from virus."

--_000_DF735188ED91BD458FA0E0C17929339F013665CEA2GUREXMB01ASIA_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:offic=
e:smarttags" name=3D"PersonName" /><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h4
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.6in;
	text-indent:-.6in;
	page-break-after:avoid;
	mso-list:l0 level4 lfo1;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:69;
	mso-list-template-ids:439751080;}
@list l0:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l0:level3
	{mso-level-suffix:space;
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	mso-ansi-font-size:12.0pt;
	mso-ascii-font-family:Arial;
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:Arial;
	font-variant:normal !important;
	color:windowtext;
	mso-text-animation:none;
	text-transform:none;
	position:relative;
	top:0pt;
	mso-text-raise:0pt;
	letter-spacing:0pt;
	border:none;
	mso-font-width:100%;
	mso-font-kerning:0pt;
	text-shadow:none;
	text-effect:none;
	text-effect:none;
	mso-bidi-font-weight:bold;
	mso-bidi-font-style:normal;
	text-decoration:none;
	text-underline:none;
	text-decoration:none;
	text-line-through:none;}
@list l0:level4
	{mso-level-style-link:"Heading 4";
	mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.6in;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l0:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.7in;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l0:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:.8in;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l0:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:.9in;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"blue">
<div class=3D"Section1">
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Hi Anand,<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Generally the application logic is tre=
ated separately from the transport layer which is here M3UA layer. So it is=
 not necessary that
 if the transport layer is ready at a node then its application layer will =
also be in a ready state.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">The M3UA ASP UP message signifies the =
availability of transport function at ASP but not about the application lay=
er processing function
 on the same ASP. Also in similar fashion SGP sends ASP UP Ack to indicate =
its availability to accept the protocol messages only.<o:p></o:p></span></f=
ont></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">By sending ASP ACTIVE an ASP indicates=
 that now it can generate and process the user layer traffic and by sending=
 ASP ACTIVE Ack SGP
 also indicates the same.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">So there is a distinction as I interpr=
et the RFC for having TWO different messages viz. ASP UP and ASP ACTIVE whi=
ch I think have been
 designed for such aspects. Also note that the application subsequently can=
 initiate ASP ACTIVE from another ASP. The interpretation is now in the con=
text of the traffic mode. So in Override mode the ASP which has generated t=
he ASP AC will take on the active
 role, in case of loadshare it will be kind of parallel processing and in b=
roadcast all the ASPs will process the same traffic simultaneously.<o:p></o=
:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">That means there is some control funct=
ion which will decide when the application is ready and traffic can be star=
ted. Now I may design
 my system which will first complete all the application level readiness fu=
nctions and then will start with ASP UP. In that case it is possible that a=
s soon as I receive and ASP UP ack I will send ASP ACT immediately.<o:p></o=
:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">To answer your question if ASP AC can =
be triggered from a particular ASP I would say yes when ASPs are running in=
 high availability framework
 it is the framework which directs a particular ASP to assume ACTIVE role a=
nd then only that specific ASP will initiate the ASP ACK message to SGP. Th=
e framework may determine the active ASP based on multiple factors like nod=
es priority in that framework, its
 previous restart history, the state of application functions etc.<o:p></o:=
p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Regards<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Deepak<o:p></o:p></span></font></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0pt">
<hr size=3D"2" width=3D"100%" align=3D"center" tabindex=3D"-1">
</span></font></div>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span style=3D"f=
ont-size:10.0pt;
font-family:Tahoma;font-weight:bold">From:</span></font></b><font size=3D"2=
" face=3D"Tahoma"><span style=3D"font-size:10.0pt;font-family:Tahoma"> Anan=
d N Ilkal [mailto:anandnilkal@gmail.com]
<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Tuesday, January 04, 2=
011 3:49 PM<br>
<b><span style=3D"font-weight:bold">To:</span></b> arif khan; <st1:PersonNa=
me w:st=3D"on">
Deepak Gunjal</st1:PersonName><br>
<b><span style=3D"font-weight:bold">Cc:</span></b> sigtran@ietf.org<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: [Sigtran] ASP a=
ctive procedure</span></font><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">Hello Deepak,<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">I understand that there needs to be local check whether stack is re=
ady to receive traffic for that routing key.&nbsp;<o:p></o:p></span></font>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">lets assume all those scenarios are satisfied. and i&nbsp;am pretty=
 sure that when RFC says MAY, it has taken all these cases into account (fo=
r example you can read from
 NOTIFY procedures - for NOTIFY to be sent, lot of conditions needs to be s=
atisfied - like n number of ASP's being active. Yet RFC uses the words like=
 MUST or SHOULD) .<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">If traffic modes are to be taken into account, what should act as t=
rigger for sending ASP Active message from a perticular ASP?<o:p></o:p></sp=
an></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">Hence my opinion is ASP Up Ack is only a sufficient condition, wher=
e-as NOTIFY from peer acts as necessary condition.<o:p></o:p></span></font>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">can any comment on that?<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">On 4 January 2011 14:01, arif khan &lt;<a href=3D"mailto:arif15jan@=
gmail.com">arif15jan@gmail.com</a>&gt; wrote:<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">Implementation logic is ok in their own context ...........<br>
But ASP can process the TRAFFIC message only after the ASP ACT ACK<br>
received from the NW and local side ASP with the remote ASP change<br>
their state and becomes ready to process the TRAFFIC.<o:p></o:p></span></fo=
nt></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 1/4/11, <st1:PersonName w:st=3D"on">Deepak Gunjal</st1:PersonName> &lt;<=
a href=3D"mailto:deepak.gunjal@aricent.com">deepak.gunjal@aricent.com</a>&g=
t; wrote:<br>
&gt; As per my opinion the ASP ACTIVE is triggered after the reception of A=
SP UP<br>
&gt; ACK only but the trigger point may not be immediate. The trigger point=
 can<br>
&gt; be an indication from high availability framework; it could be some<br=
>
&gt; application logic which once determines via local procedures that it i=
s<br>
&gt; ready to process the application traffic from network can initiate ASP=
<br>
&gt; ACTIVE to SGP.<br>
&gt;<br>
&gt; Regards<br>
&gt; Deepak<br>
&gt;<br>
&gt; ________________________________<br>
&gt; From: <a href=3D"mailto:sigtran-bounces@ietf.org">sigtran-bounces@ietf=
.org</a> [mailto:<a href=3D"mailto:sigtran-bounces@ietf.org">sigtran-bounce=
s@ietf.org</a>] On Behalf<br>
&gt; Of Anand N Ilkal<br>
&gt; Sent: Tuesday, January 04, 2011 1:22 PM<br>
&gt; To: <a href=3D"mailto:sigtran@ietf.org">sigtran@ietf.org</a><br>
&gt; Subject: [Sigtran] ASP active procedure<br>
&gt;<br>
&gt; Hello,<br>
&gt;<br>
&gt; i have doubt regarding the following section is RFC 4666 &nbsp;-<br>
&gt; 4.3.4.3. &nbsp;ASP Active Procedures<br>
&gt;<br>
&gt; &nbsp; &nbsp;Anytime after the ASP has received an ASP Up Ack message =
from the SGP<br>
&gt; &nbsp; &nbsp;or IPSP, the ASP MAY send an ASP Active message to the SG=
P,<br>
&gt; &nbsp; &nbsp;indicating that the ASP is ready to start processing traf=
fic....<br>
&gt;<br>
&gt; 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?<=
br>
&gt; 2. is receipt of ASP Up Ack message is treated as sufficient condition=
,<br>
&gt; whereas there is a necessary condition which should be satisfied so as=
 ASP<br>
&gt; active message is sent? if so, what is that condition?<br>
&gt;<br>
&gt; --<br>
&gt; with regards,<br>
&gt; Anand kumar Ilkal<br>
&gt;<br>
&gt; ________________________________<br>
&gt; &quot;DISCLAIMER: This message is proprietary to Aricent and is intend=
ed solely<br>
&gt; for the use of the individual to whom it is addressed. It may contain<=
br>
&gt; privileged or confidential information and should not be circulated or=
 used<br>
&gt; for any purpose other than for what it is intended. If you have receiv=
ed<br>
&gt; this message in error, please notify the originator immediately. If yo=
u are<br>
&gt; not the intended recipient, you are notified that you are strictly<br>
&gt; prohibited from using, copying, altering, or disclosing the contents o=
f this<br>
&gt; message. Aricent accepts no responsibility for loss or damage arising =
from<br>
&gt; the use of the information transmitted by this email including damage =
from<br>
&gt; virus.&quot;<br>
&gt;<o:p></o:p></span></font></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><br>
<br clear=3D"all">
<br>
-- <br>
with regards,<br>
Anand kumar Ilkal<o:p></o:p></span></font></p>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"3">&quot;DISCLAIMER: This messa=
ge is proprietary to Aricent and is intended solely for the use of the indi=
vidual to whom it is addressed. It may contain privileged or confidential i=
nformation and should not be circulated or
 used for any purpose other than for what it is intended. If you have recei=
ved this message in error, please notify the originator immediately. If you=
 are not the intended recipient, you are notified that you are strictly pro=
hibited from using, copying, altering,
 or disclosing the contents of this message. Aricent accepts no responsibil=
ity for loss or damage arising from the use of the information transmitted =
by this email including damage from virus.&quot;<br>
</font>
</body>
</html>

--_000_DF735188ED91BD458FA0E0C17929339F013665CEA2GUREXMB01ASIA_--

From arif15jan@gmail.com  Tue Jan  4 04:58:11 2011
Return-Path: <arif15jan@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BACE53A6BD7 for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 04:58:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6E9gGUrOE1B for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 04:58:10 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id E67F03A6A44 for <sigtran@ietf.org>; Tue,  4 Jan 2011 04:58:09 -0800 (PST)
Received: by qyk34 with SMTP id 34so16219012qyk.10 for <sigtran@ietf.org>; Tue, 04 Jan 2011 05:00:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=/fnvmhN9UdHTg0Qo5qGTG3De/rdV4QbXpx4CjKO0m9M=; b=sh1pBXNGg+u7Vj0sLaa2FtDd78agA/dy8plsOcSQm7zpPoh0kyT1wjAibXZfeW9YnB iAHQo5c6qoG3Xo3euk2+2GRSdOJoZFwR/DDMwr0C0CeKkwWO1+PNf8EbxJ4r2p0dHIBo owCpjTBSuuu0JxjKVrUPPADHk3u+jUuHrgzNQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=spggcVQAtCCPfuFUplCCP7e0cy9PpkignYZ9my9Lsxu7vLnHN3bVnBpV9eU+RO9THD Zr0YVlsFodVpz5vCV1UJYi739Sq/VjHp8q08Va9RAKVCcr+/19XF4Al4BXfymfSkBv4i BH4KfOjnIk8vNq+Izh39CVD93oMcmsRp/OS6k=
MIME-Version: 1.0
Received: by 10.229.181.74 with SMTP id bx10mr19070265qcb.215.1294146016480; Tue, 04 Jan 2011 05:00:16 -0800 (PST)
Received: by 10.220.75.3 with HTTP; Tue, 4 Jan 2011 05:00:16 -0800 (PST)
In-Reply-To: <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com>
Date: Tue, 4 Jan 2011 18:30:16 +0530
Message-ID: <AANLkTikjws2QNj-h8+TxBaPCDEaXWBSW2LmYWLuKxZNu@mail.gmail.com>
From: arif khan <arif15jan@gmail.com>
To: Anand N Ilkal <anandnilkal@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 12:58:11 -0000

For ASP UP ACK only, this scenario is possible only in the single
exchange mode with traffic share mode .

If we use double exchange then further messages like ASP ACT from both
side is expected including ACK also apart from ASPUP.

if still not clear please re introduce the problem again and RFC line
where you have any doubt.

Cheers
-arif






On 1/4/11, Anand N Ilkal <anandnilkal@gmail.com> wrote:
> Hello Deepak,
>
> I understand that there needs to be local check whether stack is ready to
> receive traffic for that routing key.
>
> lets assume all those scenarios are satisfied. and i am pretty sure that
> when RFC says MAY, it has taken all these cases into account (for example
> you can read from NOTIFY procedures - for NOTIFY to be sent, lot of
> conditions needs to be satisfied - like n number of ASP's being active. Yet
> RFC uses the words like MUST or SHOULD) .
>
> If traffic modes are to be taken into account, what should act as trigger
> for sending ASP Active message from a perticular ASP?
>
> Hence my opinion is ASP Up Ack is only a sufficient condition, where-as
> NOTIFY from peer acts as necessary condition.
> can any comment on that?
>
> On 4 January 2011 14:01, arif khan <arif15jan@gmail.com> wrote:
>
>> Implementation logic is ok in their own context ...........
>> But ASP can process the TRAFFIC message only after the ASP ACT ACK
>> received from the NW and local side ASP with the remote ASP change
>> their state and becomes ready to process the TRAFFIC.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
>> > As per my opinion the ASP ACTIVE is triggered after the reception of ASP
>> UP
>> > ACK only but the trigger point may not be immediate. The trigger point
>> can
>> > be an indication from high availability framework; it could be some
>> > application logic which once determines via local procedures that it is
>> > ready to process the application traffic from network can initiate ASP
>> > ACTIVE to SGP.
>> >
>> > Regards
>> > Deepak
>> >
>> > ________________________________
>> > From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On
>> Behalf
>> > Of Anand N Ilkal
>> > Sent: Tuesday, January 04, 2011 1:22 PM
>> > To: sigtran@ietf.org
>> > Subject: [Sigtran] ASP active procedure
>> >
>> > Hello,
>> >
>> > i have doubt regarding the following section is RFC 4666  -
>> > 4.3.4.3.  ASP Active Procedures
>> >
>> >    Anytime after the ASP has received an ASP Up Ack message from the SGP
>> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>> >    indicating that the ASP is ready to start processing traffic....
>> >
>> > 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
>> > 2. is receipt of ASP Up Ack message is treated as sufficient condition,
>> > whereas there is a necessary condition which should be satisfied so as
>> ASP
>> > active message is sent? if so, what is that condition?
>> >
>> > --
>> > with regards,
>> > Anand kumar Ilkal
>> >
>> > ________________________________
>> > "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising
>> from
>> > the use of the information transmitted by this email including damage
>> from
>> > virus."
>> >
>>
>
>
>
> --
> with regards,
> Anand kumar Ilkal
>

From anandnilkal@gmail.com  Tue Jan  4 07:59:47 2011
Return-Path: <anandnilkal@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF0AA3A6CC6 for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 07:59:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z5-lGM2Ar10I for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 07:59:45 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id B1AE53A6CBF for <sigtran@ietf.org>; Tue,  4 Jan 2011 07:59:44 -0800 (PST)
Received: by ywk9 with SMTP id 9so6407368ywk.31 for <sigtran@ietf.org>; Tue, 04 Jan 2011 08:01:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=AQPovnYNvbfcb6o3GRM+knrRyQH/NIdRb1ig3ZaWLO0=; b=KJ8UJpbhTvwDAd3SbKuGc0Z41+D1QYfyre/IwTFEpxJ3AJYLp6vSjeFQFOBze1uaM6 7ZY6HoXFo+UzMQeo44q3FrnZigIWjJx9jSr7jzGIhH7E4G/veBIq8+rjdhuucYL181+i nQir57v4EtuXTzD6PS0psiD8chBItPNtX5vIc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=SfNXTaZbYoZVjh8203mr/MLqEI7YwQ11G60Stq/8P1uD7aNDGt2kn1iaQIqEWiXwMI Y2mbpsFKSeKIrMFQryKb4zCuUa/pJ6jWA3KZ94Nl18CMh7111EjZ/SI/uCOxJWBuXCKV GtseDIgfBAgJHyOVXkMx37XdlzOFFFJbEvTqM=
MIME-Version: 1.0
Received: by 10.236.111.17 with SMTP id v17mr19511402yhg.4.1294156911484; Tue, 04 Jan 2011 08:01:51 -0800 (PST)
Received: by 10.236.108.145 with HTTP; Tue, 4 Jan 2011 08:01:51 -0800 (PST)
In-Reply-To: <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM>
Date: Tue, 4 Jan 2011 21:31:51 +0530
Message-ID: <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com>
From: Anand N Ilkal <anandnilkal@gmail.com>
To: Deepak Gunjal <deepak.gunjal@aricent.com>
Content-Type: multipart/alternative; boundary=90e6ba476b55fe23c504990762e7
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 15:59:48 -0000

--90e6ba476b55fe23c504990762e7
Content-Type: text/plain; charset=ISO-8859-1

Hello Deepak, arif,

Please find my comments below -

According to RFC 4666, section -
4.3.4.3.  ASP Active Procedures

   Anytime after the ASP has received an ASP Up Ack message from the SGP
   or IPSP, the ASP MAY send an ASP Active message to the SGP,
   indicating that the ASP is ready to start processing traffic....

what if i decide not to send ASP Active after receiving ASP Up Ack , when
can i decide again to send ASP Active?

On 4 January 2011 16:31, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:

>  Hi Anand,
>
>
>
> Generally the application logic is treated separately from the transport
> layer which is here M3UA layer. So it is not necessary that if the transport
> layer is ready at a node then its application layer will also be in a ready
> state.
>
Agreed : in the entirety of the M3UA layer, it should never depend on the
status of the upper layer. always upper layers use the services of the lower
layers. otherway is seldom used.

>
>
> The M3UA ASP UP message signifies the availability of transport function at
> ASP but not about the application layer processing function on the same ASP.
> Also in similar fashion SGP sends ASP UP Ack to indicate its availability to
> accept the protocol messages only.
>
Consider the hypothetical stack configuration, where only till M3UA layer is
configured, does it mean, it can not send ASP Active Message? I do not think
so.

>
>
> By sending ASP ACTIVE an ASP indicates that now it can generate and process
> the user layer traffic and by sending ASP ACTIVE Ack SGP also indicates the
> same.
>
if application layer is not available local M3UA layer simply drops
message.

>
>
> So there is a distinction as I interpret the RFC for having TWO different
> messages viz. ASP UP and ASP ACTIVE which I think have been designed for
> such aspects. Also note that the application subsequently can initiate ASP
> ACTIVE from another ASP. The interpretation is now in the context of the
> traffic mode. So in Override mode the ASP which has generated the ASP AC
> will take on the active role, in case of loadshare it will be kind of
> parallel processing and in broadcast all the ASPs will process the same
> traffic simultaneously.
>
>
>
> That means there is some control function which will decide when the
> application is ready and traffic can be started. Now I may design my system
> which will first complete all the application level readiness functions and
> then will start with ASP UP. In that case it is possible that as soon as I
> receive and ASP UP ack I will send ASP ACT immediately.
>
that will be a good design. But i am not convinced that the readiness of the
application layer is the reason why sending of ASP Active is marked as MAY
in RFC4666. what if LM is the one who is triggering ASPSM and ASPTM
messages. in that case your design requires LM to communicate to both M3UA
layer and upper layer. there are only following boundaries defined between
M3UA and MTP3 User layers -

      MTP-TRANSFER request
      MTP-TRANSFER indication
      MTP-PAUSE indication
      MTP-RESUME indication
      MTP-STATUS indication


>
> To answer your question if ASP AC can be triggered from a particular ASP I
> would say yes when ASPs are running in high availability framework it is the
> framework which directs a particular ASP to assume ACTIVE role and then only
> that specific ASP will initiate the ASP ACK message to SGP. The framework
> may determine the active ASP based on multiple factors like nodes priority
> in that framework, its previous restart history, the state of application
> functions etc.
>
>
>
> Regards
>
> Deepak
>  ------------------------------
>
> *From:* Anand N Ilkal [mailto:anandnilkal@gmail.com]
> *Sent:* Tuesday, January 04, 2011 3:49 PM
> *To:* arif khan; Deepak Gunjal
> *Cc:* sigtran@ietf.org
> *Subject:* Re: [Sigtran] ASP active procedure
>
>
>
> Hello Deepak,
>
>
>
> I understand that there needs to be local check whether stack is ready to
> receive traffic for that routing key.
>
>
>
> lets assume all those scenarios are satisfied. and i am pretty sure that
> when RFC says MAY, it has taken all these cases into account (for example
> you can read from NOTIFY procedures - for NOTIFY to be sent, lot of
> conditions needs to be satisfied - like n number of ASP's being active. Yet
> RFC uses the words like MUST or SHOULD) .
>
>
>
> If traffic modes are to be taken into account, what should act as trigger
> for sending ASP Active message from a perticular ASP?
>
>
>
> Hence my opinion is ASP Up Ack is only a sufficient condition, where-as
> NOTIFY from peer acts as necessary condition.
>
> can any comment on that?
>
>
>
> On 4 January 2011 14:01, arif khan <arif15jan@gmail.com> wrote:
>
> Implementation logic is ok in their own context ...........
> But ASP can process the TRAFFIC message only after the ASP ACT ACK
> received from the NW and local side ASP with the remote ASP change
> their state and becomes ready to process the TRAFFIC.
>
>
>
>
>
>
>
>
>
>
> On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
> > As per my opinion the ASP ACTIVE is triggered after the reception of ASP
> UP
> > ACK only but the trigger point may not be immediate. The trigger point
> can
> > be an indication from high availability framework; it could be some
> > application logic which once determines via local procedures that it is
> > ready to process the application traffic from network can initiate ASP
> > ACTIVE to SGP.
> >
> > Regards
> > Deepak
> >
> > ________________________________
> > From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On
> Behalf
> > Of Anand N Ilkal
> > Sent: Tuesday, January 04, 2011 1:22 PM
> > To: sigtran@ietf.org
> > Subject: [Sigtran] ASP active procedure
> >
> > Hello,
> >
> > i have doubt regarding the following section is RFC 4666  -
> > 4.3.4.3.  ASP Active Procedures
> >
> >    Anytime after the ASP has received an ASP Up Ack message from the SGP
> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
> >    indicating that the ASP is ready to start processing traffic....
> >
> > 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
> > 2. is receipt of ASP Up Ack message is treated as sufficient condition,
> > whereas there is a necessary condition which should be satisfied so as
> ASP
> > active message is sent? if so, what is that condition?
> >
> > --
> > with regards,
> > Anand kumar Ilkal
> >
> > ________________________________
> > "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising
> from
> > the use of the information transmitted by this email including damage
> from
> > virus."
> >
>
>
>
>
> --
> with regards,
> Anand kumar Ilkal
>
> ------------------------------
> "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising from
> the use of the information transmitted by this email including damage from
> virus."
>



-- 
with regards,
Anand kumar Ilkal

--90e6ba476b55fe23c504990762e7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Deepak, arif,<div><br></div><div>Please find my comments below -</div=
><div><br></div><div>According to RFC 4666, section -</div><div><span class=
=3D"Apple-style-span" style=3D"font-family: arial, sans-serif; font-size: 1=
3px; border-collapse: collapse; "><div>
4.3.4.3. =A0ASP Active Procedures</div><div><br></div><div>=A0=A0 Anytime a=
fter the ASP has received an ASP Up Ack message from the SGP</div><div>=A0=
=A0 or IPSP, the ASP MAY send an ASP Active message to the SGP,</div><div>=
=A0=A0 indicating that the ASP is ready to start processing traffic....</di=
v>
<div><br></div></span></div><div>what if i decide not to send ASP Active af=
ter receiving ASP Up Ack , when can i decide again to send ASP Active?<br><=
br><div class=3D"gmail_quote">On 4 January 2011 16:31, Deepak Gunjal <span =
dir=3D"ltr">&lt;<a href=3D"mailto:deepak.gunjal@aricent.com">deepak.gunjal@=
aricent.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">Hi Anand,</span></=
font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">Generally the appl=
ication logic is treated separately from the transport layer which is here =
M3UA layer. So it is not necessary that
 if the transport layer is ready at a node then its application layer will =
also be in a ready state.</span></font></p></div></div></blockquote><div>Ag=
reed : in the=A0entirety=A0of the M3UA layer, it should never depend on the=
 status of the upper layer. always upper layers use the services of the low=
er layers. otherway is seldom used.=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div lang=3D"EN-US" link=3D"blue" vlink=3D"=
blue"><div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">The M3UA ASP UP me=
ssage signifies the availability of transport function at ASP but not about=
 the application layer processing function
 on the same ASP. Also in similar fashion SGP sends ASP UP Ack to indicate =
its availability to accept the protocol messages only.</span></font></p></d=
iv></div></blockquote><div>Consider the hypothetical stack configuration, w=
here only till M3UA layer is configured, does it mean, it can not send ASP =
Active Message? I do not think so.=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div lang=3D"EN-US" link=3D"blue" vlink=3D"=
blue"><div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">By sending ASP ACT=
IVE an ASP indicates that now it can generate and process the user layer tr=
affic and by sending ASP ACTIVE Ack SGP
 also indicates the same.</span></font></p></div></div></blockquote><div>if=
 application layer is not available local M3UA layer simply drops message.=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex;">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"blue"><div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">So there is a dist=
inction as I interpret the RFC for having TWO different messages viz. ASP U=
P and ASP ACTIVE which I think have been
 designed for such aspects. Also note that the application subsequently can=
 initiate ASP ACTIVE from another ASP. The interpretation is now in the con=
text of the traffic mode. So in Override mode the ASP which has generated t=
he ASP AC will take on the active
 role, in case of loadshare it will be kind of parallel processing and in b=
roadcast all the ASPs will process the same traffic simultaneously.</span><=
/font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">That means there i=
s some control function which will decide when the application is ready and=
 traffic can be started. Now I may design
 my system which will first complete all the application level readiness fu=
nctions and then will start with ASP UP. In that case it is possible that a=
s soon as I receive and ASP UP ack I will send ASP ACT immediately.</span><=
/font></p>
</div></div></blockquote><div>that will be a good design. But i am not conv=
inced that the readiness of the application layer is the reason why sending=
 of ASP Active is marked as MAY in RFC4666.=A0what if LM is the one who is =
triggering ASPSM and ASPTM messages. in that case your design requires LM t=
o communicate to both M3UA layer and upper layer. there are only following =
boundaries defined=A0between M3UA and MTP3 User layers -</div>
<div><span class=3D"Apple-style-span" style=3D"font-family: &#39;Times New =
Roman&#39;; font-size: 16px; "><pre class=3D"newpage" style=3D"font-size: 1=
em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; ">     =
 MTP-TRANSFER request
      MTP-TRANSFER indication
      MTP-PAUSE indication
      MTP-RESUME indication
      MTP-STATUS indication</pre></span></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
;"><div lang=3D"EN-US" link=3D"blue" vlink=3D"blue"><div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">To answer your que=
stion if ASP AC can be triggered from a particular ASP I would say yes when=
 ASPs are running in high availability framework
 it is the framework which directs a particular ASP to assume ACTIVE role a=
nd then only that specific ASP will initiate the ASP ACK message to SGP. Th=
e framework may determine the active ASP based on multiple factors like nod=
es priority in that framework, its
 previous restart history, the state of application functions etc.</span></=
font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">Regards</span></fo=
nt></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:10.0pt;font-family:Arial;color:navy">Deepak</span></fon=
t></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0pt">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></font></div>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span style=3D"f=
ont-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</span></font></b=
><font size=3D"2" face=3D"Tahoma"><span style=3D"font-size:10.0pt;font-fami=
ly:Tahoma"> Anand N Ilkal [mailto:<a href=3D"mailto:anandnilkal@gmail.com" =
target=3D"_blank">anandnilkal@gmail.com</a>]
<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Tuesday, January 04, 2=
011 3:49 PM<br>
<b><span style=3D"font-weight:bold">To:</span></b> arif khan;=20
Deepak Gunjal<br>
<b><span style=3D"font-weight:bold">Cc:</span></b> <a href=3D"mailto:sigtra=
n@ietf.org" target=3D"_blank">sigtran@ietf.org</a><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: [Sigtran] ASP a=
ctive procedure</span></font></p>
</div><div><div></div><div class=3D"h5">
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0</span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">Hello Deepak,</span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0</span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">I understand that there needs to be local check whet=
her stack is ready to receive traffic for that routing key.=A0</span></font=
></p>

</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0</span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">lets assume all those scenarios are satisfied. and i=
=A0am pretty sure that when RFC says MAY, it has taken all these cases into=
 account (for example you can read from
 NOTIFY procedures - for NOTIFY to be sent, lot of conditions needs to be s=
atisfied - like n number of ASP&#39;s being active. Yet RFC uses the words =
like MUST or SHOULD) .</span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0</span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">If traffic modes are to be taken into account, what =
should act as trigger for sending ASP Active message from a perticular ASP?=
</span></font></p>

</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0</span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">Hence my opinion is ASP Up Ack is only a sufficient =
condition, where-as NOTIFY from peer acts as necessary condition.</span></f=
ont></p>

</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">can any comment on that?</span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0</span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">On 4 January 2011 14:01, arif khan &lt;<a href=3D"ma=
ilto:arif15jan@gmail.com" target=3D"_blank">arif15jan@gmail.com</a>&gt; wro=
te:</span></font></p>

<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">Implementation logic is ok in their own context ....=
.......<br>
But ASP can process the TRAFFIC message only after the ASP ACT ACK<br>
received from the NW and local side ASP with the remote ASP change<br>
their state and becomes ready to process the TRAFFIC.</span></font></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 1/4/11, Deepak Gunjal &lt;<a href=3D"mailto:deepak.gunjal@aricent.com" t=
arget=3D"_blank">deepak.gunjal@aricent.com</a>&gt; wrote:<br>
&gt; As per my opinion the ASP ACTIVE is triggered after the reception of A=
SP UP<br>
&gt; ACK only but the trigger point may not be immediate. The trigger point=
 can<br>
&gt; be an indication from high availability framework; it could be some<br=
>
&gt; application logic which once determines via local procedures that it i=
s<br>
&gt; ready to process the application traffic from network can initiate ASP=
<br>
&gt; ACTIVE to SGP.<br>
&gt;<br>
&gt; Regards<br>
&gt; Deepak<br>
&gt;<br>
&gt; ________________________________<br>
&gt; From: <a href=3D"mailto:sigtran-bounces@ietf.org" target=3D"_blank">si=
gtran-bounces@ietf.org</a> [mailto:<a href=3D"mailto:sigtran-bounces@ietf.o=
rg" target=3D"_blank">sigtran-bounces@ietf.org</a>] On Behalf<br>
&gt; Of Anand N Ilkal<br>
&gt; Sent: Tuesday, January 04, 2011 1:22 PM<br>
&gt; To: <a href=3D"mailto:sigtran@ietf.org" target=3D"_blank">sigtran@ietf=
.org</a><br>
&gt; Subject: [Sigtran] ASP active procedure<br>
&gt;<br>
&gt; Hello,<br>
&gt;<br>
&gt; i have doubt regarding the following section is RFC 4666 =A0-<br>
&gt; 4.3.4.3. =A0ASP Active Procedures<br>
&gt;<br>
&gt; =A0 =A0Anytime after the ASP has received an ASP Up Ack message from t=
he SGP<br>
&gt; =A0 =A0or IPSP, the ASP MAY send an ASP Active message to the SGP,<br>
&gt; =A0 =A0indicating that the ASP is ready to start processing traffic...=
.<br>
&gt;<br>
&gt; 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?<=
br>
&gt; 2. is receipt of ASP Up Ack message is treated as sufficient condition=
,<br>
&gt; whereas there is a necessary condition which should be satisfied so as=
 ASP<br>
&gt; active message is sent? if so, what is that condition?<br>
&gt;<br>
&gt; --<br>
&gt; with regards,<br>
&gt; Anand kumar Ilkal<br>
&gt;<br>
&gt; ________________________________<br>
&gt; &quot;DISCLAIMER: This message is proprietary to Aricent and is intend=
ed solely<br>
&gt; for the use of the individual to whom it is addressed. It may contain<=
br>
&gt; privileged or confidential information and should not be circulated or=
 used<br>
&gt; for any purpose other than for what it is intended. If you have receiv=
ed<br>
&gt; this message in error, please notify the originator immediately. If yo=
u are<br>
&gt; not the intended recipient, you are notified that you are strictly<br>
&gt; prohibited from using, copying, altering, or disclosing the contents o=
f this<br>
&gt; message. Aricent accepts no responsibility for loss or damage arising =
from<br>
&gt; the use of the information transmitted by this email including damage =
from<br>
&gt; virus.&quot;<br>
&gt;</span></font></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><br>
<br clear=3D"all">
<br>
-- <br>
with regards,<br>
Anand kumar Ilkal</span></font></p>
</div>
</div></div></div><div><div></div><div class=3D"h5">
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"3">&quot;DISCLAIMER: This messa=
ge is proprietary to Aricent and is intended solely for the use of the indi=
vidual to whom it is addressed. It may contain privileged or confidential i=
nformation and should not be circulated or
 used for any purpose other than for what it is intended. If you have recei=
ved this message in error, please notify the originator immediately. If you=
 are not the intended recipient, you are notified that you are strictly pro=
hibited from using, copying, altering,
 or disclosing the contents of this message. Aricent accepts no responsibil=
ity for loss or damage arising from the use of the information transmitted =
by this email including damage from virus.&quot;<br>
</font>
</div></div></div>

</blockquote></div><br><br clear=3D"all"><br>-- <br>with regards,<br>Anand =
kumar Ilkal<br>
</div>

--90e6ba476b55fe23c504990762e7--

From arif15jan@gmail.com  Tue Jan  4 09:35:31 2011
Return-Path: <arif15jan@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 734B33A6CFE for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 09:35:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nf3jHXpWvlaj for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 09:35:30 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 055933A6CFD for <sigtran@ietf.org>; Tue,  4 Jan 2011 09:35:29 -0800 (PST)
Received: by qwg5 with SMTP id 5so15493509qwg.31 for <sigtran@ietf.org>; Tue, 04 Jan 2011 09:37:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Sc8ygYhFxbNdqzMZo27aco5NwXIi6GdKA4bC35zz280=; b=q+Cbt7UUkjR1i+iqQsqlNv8JGR1QTQcKyc3b0mVYuX6aF4cbu7/RZNc5GUm/FvR12Z UWBWITqwvPFfmihGGnIIjvVjvWjJ2H70LuJ2Xrs62IVZ7x5q1yBli13lxlNuvZ58KAuP frWJnZElhDm5SZSjmvukvIdQJo8dTxQlcuacU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=KBLa+N2bYt5XqWbxEOEvBLd+xMpB4eEtCH5LBTHhEyar7yk184I63pf7ITYvXf48vm HP2ptXMTalWdh4iOxBnSEEqiC4nkGGkHzLp4Ul/VWdeihjynuF19XoUxEVQuHL6PosLq 78vCJM+JBDdmMCnS2yBe56iCDsP9Y3xLwPrQQ=
MIME-Version: 1.0
Received: by 10.229.43.195 with SMTP id x3mr18962613qce.291.1294162656668; Tue, 04 Jan 2011 09:37:36 -0800 (PST)
Received: by 10.220.75.3 with HTTP; Tue, 4 Jan 2011 09:37:36 -0800 (PST)
In-Reply-To: <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com>
Date: Tue, 4 Jan 2011 23:07:36 +0530
Message-ID: <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com>
From: arif khan <arif15jan@gmail.com>
To: Anand N Ilkal <anandnilkal@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 17:35:31 -0000

Yes this is the implementation need to handle this kind of situation.
Suppose if Peer is already in ASP ACT state or any other
state(excluding, waiting for the ASP UP ACK) and receives such
messages then state machine of the ASP should perform the state change
and should come to the original state.

This could be done by the system management entity to handle this kind
of situation.




On 1/4/11, Anand N Ilkal <anandnilkal@gmail.com> wrote:
> Hello Deepak, arif,
>
> Please find my comments below -
>
> According to RFC 4666, section -
> 4.3.4.3.  ASP Active Procedures
>
>    Anytime after the ASP has received an ASP Up Ack message from the SGP
>    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>    indicating that the ASP is ready to start processing traffic....
>
> what if i decide not to send ASP Active after receiving ASP Up Ack , when
> can i decide again to send ASP Active?
>
> On 4 January 2011 16:31, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
>
>>  Hi Anand,
>>
>>
>>
>> Generally the application logic is treated separately from the transport
>> layer which is here M3UA layer. So it is not necessary that if the
>> transport
>> layer is ready at a node then its application layer will also be in a
>> ready
>> state.
>>
> Agreed : in the entirety of the M3UA layer, it should never depend on the
> status of the upper layer. always upper layers use the services of the lower
> layers. otherway is seldom used.
>
>>
>>
>> The M3UA ASP UP message signifies the availability of transport function
>> at
>> ASP but not about the application layer processing function on the same
>> ASP.
>> Also in similar fashion SGP sends ASP UP Ack to indicate its availability
>> to
>> accept the protocol messages only.
>>
> Consider the hypothetical stack configuration, where only till M3UA layer is
> configured, does it mean, it can not send ASP Active Message? I do not think
> so.
>
>>
>>
>> By sending ASP ACTIVE an ASP indicates that now it can generate and
>> process
>> the user layer traffic and by sending ASP ACTIVE Ack SGP also indicates
>> the
>> same.
>>
> if application layer is not available local M3UA layer simply drops
> message.
>
>>
>>
>> So there is a distinction as I interpret the RFC for having TWO different
>> messages viz. ASP UP and ASP ACTIVE which I think have been designed for
>> such aspects. Also note that the application subsequently can initiate ASP
>> ACTIVE from another ASP. The interpretation is now in the context of the
>> traffic mode. So in Override mode the ASP which has generated the ASP AC
>> will take on the active role, in case of loadshare it will be kind of
>> parallel processing and in broadcast all the ASPs will process the same
>> traffic simultaneously.
>>
>>
>>
>> That means there is some control function which will decide when the
>> application is ready and traffic can be started. Now I may design my
>> system
>> which will first complete all the application level readiness functions
>> and
>> then will start with ASP UP. In that case it is possible that as soon as I
>> receive and ASP UP ack I will send ASP ACT immediately.
>>
> that will be a good design. But i am not convinced that the readiness of the
> application layer is the reason why sending of ASP Active is marked as MAY
> in RFC4666. what if LM is the one who is triggering ASPSM and ASPTM
> messages. in that case your design requires LM to communicate to both M3UA
> layer and upper layer. there are only following boundaries defined between
> M3UA and MTP3 User layers -
>
>       MTP-TRANSFER request
>       MTP-TRANSFER indication
>       MTP-PAUSE indication
>       MTP-RESUME indication
>       MTP-STATUS indication
>
>
>>
>> To answer your question if ASP AC can be triggered from a particular ASP I
>> would say yes when ASPs are running in high availability framework it is
>> the
>> framework which directs a particular ASP to assume ACTIVE role and then
>> only
>> that specific ASP will initiate the ASP ACK message to SGP. The framework
>> may determine the active ASP based on multiple factors like nodes priority
>> in that framework, its previous restart history, the state of application
>> functions etc.
>>
>>
>>
>> Regards
>>
>> Deepak
>>  ------------------------------
>>
>> *From:* Anand N Ilkal [mailto:anandnilkal@gmail.com]
>> *Sent:* Tuesday, January 04, 2011 3:49 PM
>> *To:* arif khan; Deepak Gunjal
>> *Cc:* sigtran@ietf.org
>> *Subject:* Re: [Sigtran] ASP active procedure
>>
>>
>>
>> Hello Deepak,
>>
>>
>>
>> I understand that there needs to be local check whether stack is ready to
>> receive traffic for that routing key.
>>
>>
>>
>> lets assume all those scenarios are satisfied. and i am pretty sure that
>> when RFC says MAY, it has taken all these cases into account (for example
>> you can read from NOTIFY procedures - for NOTIFY to be sent, lot of
>> conditions needs to be satisfied - like n number of ASP's being active.
>> Yet
>> RFC uses the words like MUST or SHOULD) .
>>
>>
>>
>> If traffic modes are to be taken into account, what should act as trigger
>> for sending ASP Active message from a perticular ASP?
>>
>>
>>
>> Hence my opinion is ASP Up Ack is only a sufficient condition, where-as
>> NOTIFY from peer acts as necessary condition.
>>
>> can any comment on that?
>>
>>
>>
>> On 4 January 2011 14:01, arif khan <arif15jan@gmail.com> wrote:
>>
>> Implementation logic is ok in their own context ...........
>> But ASP can process the TRAFFIC message only after the ASP ACT ACK
>> received from the NW and local side ASP with the remote ASP change
>> their state and becomes ready to process the TRAFFIC.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
>> > As per my opinion the ASP ACTIVE is triggered after the reception of ASP
>> UP
>> > ACK only but the trigger point may not be immediate. The trigger point
>> can
>> > be an indication from high availability framework; it could be some
>> > application logic which once determines via local procedures that it is
>> > ready to process the application traffic from network can initiate ASP
>> > ACTIVE to SGP.
>> >
>> > Regards
>> > Deepak
>> >
>> > ________________________________
>> > From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On
>> Behalf
>> > Of Anand N Ilkal
>> > Sent: Tuesday, January 04, 2011 1:22 PM
>> > To: sigtran@ietf.org
>> > Subject: [Sigtran] ASP active procedure
>> >
>> > Hello,
>> >
>> > i have doubt regarding the following section is RFC 4666  -
>> > 4.3.4.3.  ASP Active Procedures
>> >
>> >    Anytime after the ASP has received an ASP Up Ack message from the SGP
>> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>> >    indicating that the ASP is ready to start processing traffic....
>> >
>> > 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
>> > 2. is receipt of ASP Up Ack message is treated as sufficient condition,
>> > whereas there is a necessary condition which should be satisfied so as
>> ASP
>> > active message is sent? if so, what is that condition?
>> >
>> > --
>> > with regards,
>> > Anand kumar Ilkal
>> >
>> > ________________________________
>> > "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising
>> from
>> > the use of the information transmitted by this email including damage
>> from
>> > virus."
>> >
>>
>>
>>
>>
>> --
>> with regards,
>> Anand kumar Ilkal
>>
>> ------------------------------
>> "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising from
>> the use of the information transmitted by this email including damage from
>> virus."
>>
>
>
>
> --
> with regards,
> Anand kumar Ilkal
>

From imranrazakhan@gmail.com  Mon Jan  3 01:29:21 2011
Return-Path: <imranrazakhan@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FBAD28C103 for <sigtran@core3.amsl.com>; Mon,  3 Jan 2011 01:29:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5+X-DBnPBmSV for <sigtran@core3.amsl.com>; Mon,  3 Jan 2011 01:29:20 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 5913928C102 for <sigtran@ietf.org>; Mon,  3 Jan 2011 01:29:19 -0800 (PST)
Received: by wyf23 with SMTP id 23so13687035wyf.31 for <sigtran@ietf.org>; Mon, 03 Jan 2011 01:31:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=wgKhs++Q4bY2yqAfMxcwZwtX9BR86ueOCqs2oCdkl8U=; b=n5iXbsqq/e0SijasM7+THqvzKrW686EmRlVSRAlt6U89h/7ueJGdn13uRdc9LIgy+k qHl0SnM6T1YYskpBzQ+8RfFfcjX6UhuBzZ4a8GgZNnJ/yZSzNjB9oNQIU6L9ayXXcIRU 3ohKe21QSpJ6CGTc99QPUQbgQBOdCWDV3DnMI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=JlbgYbkMELqmSiAppRGAy4rtt85+qhO+W5knwqTl39vhsWOYbBw4gz4CS7N4LVCuY3 lkPCvX9pirAHeTFnnH3QFIo+UPNNUyG4I/4tq5P2KUHepamfdNzKrp7r9Ebr3NOMzwkT RAFGmdW12OAaaf2ojHRRPhy1vNmNE3AfKW0jw=
MIME-Version: 1.0
Received: by 10.216.156.149 with SMTP id m21mr12627257wek.22.1294047086646; Mon, 03 Jan 2011 01:31:26 -0800 (PST)
Received: by 10.216.61.18 with HTTP; Mon, 3 Jan 2011 01:31:26 -0800 (PST)
Date: Mon, 3 Jan 2011 14:31:26 +0500
Message-ID: <AANLkTi=c73mO-x6Tx5Yfrut7pzE5_o3HUcqemx2C8Koo@mail.gmail.com>
From: Imran Raza Khan <imranrazakhan@gmail.com>
To: sigtran@ietf.org
Content-Type: multipart/alternative; boundary=001485f45418ec161c0498edd02b
X-Mailman-Approved-At: Tue, 04 Jan 2011 16:01:12 -0800
Subject: [Sigtran] TCAP User Adaptation Layer
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2011 09:56:22 -0000

--001485f45418ec161c0498edd02b
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I want to inquire about the TCAP user Adaptation Layer draft. Available on
link http://tools.ietf.org/html/draft-bidulock-sigtran-tua-05<http://www.google.com/url?sa=D&q=http://tools.ietf.org/html/draft-bidulock-sigtran-tua-05&usg=AFQjCNFfxGAS2BRAazFKQdXLdWlHMg8-fw>
 .

I have couple of question regarding that

   - Why its status is expired?
   - Is it still implementable?
   - Any further roadmap of TUA?
   - Will it be part of SIGTRAN or not?

Regards,
imran Raza Khan

--001485f45418ec161c0498edd02b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<span class=3D"Apple-style-span" style=3D"font-family: arial, sans-serif; f=
ont-size: 13px; border-collapse: collapse; ">Hi,<div><br></div><div>I want =
to inquire about the TCAP user Adaptation Layer draft.=A0Available=A0on lin=
k=A0<span style=3D"font-family: arial, sans-serif; font-size: 12px; "><a re=
l=3D"nofollow" href=3D"http://www.google.com/url?sa=3DD&amp;q=3Dhttp://tool=
s.ietf.org/html/draft-bidulock-sigtran-tua-05&amp;usg=3DAFQjCNFfxGAS2BRAazF=
KQdXLdWlHMg8-fw" target=3D"_blank" style=3D"color: rgb(0, 0, 204); ">http:/=
/tools.ietf.org/html/draft-bidulock-sigtran-tua-05</a></span><span style=3D=
"font-family: arial, sans-serif; font-size: 12px; ">=A0.</span></div>
<div><span style=3D"font-family: arial, sans-serif; font-size: 12px; "><br>=
</span></div><div><span style=3D"font-family: arial, sans-serif; font-size:=
 12px; ">I have couple of question regarding that</span></div><div><ul><li =
style=3D"margin-left: 15px; ">
<font face=3D"arial, sans-serif"><span style=3D"font-size: 12px; ">Why its =
status is expired?</span></font></li><li style=3D"margin-left: 15px; "><fon=
t face=3D"arial, sans-serif"><span style=3D"font-size: 12px; ">Is it still =
implementable?</span></font></li>
<li style=3D"margin-left: 15px; "><font face=3D"arial, sans-serif"><span st=
yle=3D"font-size: 12px; ">Any further roadmap of TUA?</span></font></li><li=
 style=3D"margin-left: 15px; "><font face=3D"arial, sans-serif"><span style=
=3D"font-size: 12px; ">Will it be part of SIGTRAN or not?</span></font></li=
>
</ul><div><font face=3D"arial, sans-serif"><span style=3D"font-size: 12px; =
">Regards,</span></font></div></div><div><font face=3D"arial, sans-serif"><=
span style=3D"font-size: 12px; ">imran Raza Khan</span></font></div></span>

--001485f45418ec161c0498edd02b--

From anandnilkal@gmail.com  Tue Jan  4 18:13:37 2011
Return-Path: <anandnilkal@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7D7F3A6806 for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 18:13:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level: 
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[AWL=-0.950, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_62=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LUZqNyQ1AW9F for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 18:13:36 -0800 (PST)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id A5AC83A680B for <sigtran@ietf.org>; Tue,  4 Jan 2011 18:13:35 -0800 (PST)
Received: by yie19 with SMTP id 19so4344092yie.31 for <sigtran@ietf.org>; Tue, 04 Jan 2011 18:15:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Pe5un4ZtVtVgGAHMcTyeJLo7EefEi3Ivqdtt0Lf4NKA=; b=g+OxsTJm0mTxOMigXzZd+B0U0mvWUYwWUnYAIqROcKqN7kvf03JiQB6MYuoPQFKq6A zMAvzyriih2tTb0fplOAsfeE1jZMt9Qy46Cz2SeTf65TkiNDIATeqNXGBHiKPwmVuk84 Np3xsw8vFoc6/uOxaCm2ZFYI4qlaeybeBdN1E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=UcZoY1gGQXDQWguLDqqvBUZltUDXQp1ThfUTCnw51zAHHNZpgi9SQtAGcw93/TCCoU BV5kkYhkEYKw8u74exJHc4w58OrviuLgpL7uIMwm6w3rIjzLe5gDZZlNpNahMHSawMZm /WbizS3OGTEsuhbc28XEaAokrZ9Rp9Fqffisk=
MIME-Version: 1.0
Received: by 10.236.110.6 with SMTP id t6mr138995yhg.17.1294193742462; Tue, 04 Jan 2011 18:15:42 -0800 (PST)
Received: by 10.236.108.145 with HTTP; Tue, 4 Jan 2011 18:15:42 -0800 (PST)
In-Reply-To: <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com> <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com>
Date: Wed, 5 Jan 2011 07:45:42 +0530
Message-ID: <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com>
From: Anand N Ilkal <anandnilkal@gmail.com>
To: arif khan <arif15jan@gmail.com>
Content-Type: multipart/alternative; boundary=0023547c90154a3e7504990ff668
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 02:13:37 -0000

--0023547c90154a3e7504990ff668
Content-Type: text/plain; charset=ISO-8859-1

Hello Arif, Deepak,

This is not a special scenario, which would require special handling by
either M3UA layer or LM.
My argument is, this section could have very well been written as follows -

4.3.4.3.  ASP Active Procedures

   Anytime after the ASP has received an ASP Up Ack message from the SGP
   or IPSP, the ASP SHOULD(or MUST) send an ASP Active message to the SGP,
   indicating that the ASP is ready to start processing traffic....

This would have covered all the scenarios related to readiness of the
traffic handling (and management blocking). *But text is not as shown here*,
hence receipt of ASP Up Ack is just a sufficient condition where-as NOTIFY
serves the necessary condition to send ASP Active message.

I would like you to comment on this sufficient and necessary conditions.

On 4 January 2011 23:07, arif khan <arif15jan@gmail.com> wrote:

> Yes this is the implementation need to handle this kind of situation.
> Suppose if Peer is already in ASP ACT state or any other
> state(excluding, waiting for the ASP UP ACK) and receives such
> messages then state machine of the ASP should perform the state change
> and should come to the original state.
>
> This could be done by the system management entity to handle this kind
> of situation.
>
>
>
>
> On 1/4/11, Anand N Ilkal <anandnilkal@gmail.com> wrote:
> > Hello Deepak, arif,
> >
> > Please find my comments below -
> >
> > According to RFC 4666, section -
> > 4.3.4.3.  ASP Active Procedures
> >
> >    Anytime after the ASP has received an ASP Up Ack message from the SGP
> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
> >    indicating that the ASP is ready to start processing traffic....
> >
> > what if i decide not to send ASP Active after receiving ASP Up Ack , when
> > can i decide again to send ASP Active?
> >
> > On 4 January 2011 16:31, Deepak Gunjal <deepak.gunjal@aricent.com>
> wrote:
> >
> >>  Hi Anand,
> >>
> >>
> >>
> >> Generally the application logic is treated separately from the transport
> >> layer which is here M3UA layer. So it is not necessary that if the
> >> transport
> >> layer is ready at a node then its application layer will also be in a
> >> ready
> >> state.
> >>
> > Agreed : in the entirety of the M3UA layer, it should never depend on the
> > status of the upper layer. always upper layers use the services of the
> lower
> > layers. otherway is seldom used.
> >
> >>
> >>
> >> The M3UA ASP UP message signifies the availability of transport function
> >> at
> >> ASP but not about the application layer processing function on the same
> >> ASP.
> >> Also in similar fashion SGP sends ASP UP Ack to indicate its
> availability
> >> to
> >> accept the protocol messages only.
> >>
> > Consider the hypothetical stack configuration, where only till M3UA layer
> is
> > configured, does it mean, it can not send ASP Active Message? I do not
> think
> > so.
> >
> >>
> >>
> >> By sending ASP ACTIVE an ASP indicates that now it can generate and
> >> process
> >> the user layer traffic and by sending ASP ACTIVE Ack SGP also indicates
> >> the
> >> same.
> >>
> > if application layer is not available local M3UA layer simply drops
> > message.
> >
> >>
> >>
> >> So there is a distinction as I interpret the RFC for having TWO
> different
> >> messages viz. ASP UP and ASP ACTIVE which I think have been designed for
> >> such aspects. Also note that the application subsequently can initiate
> ASP
> >> ACTIVE from another ASP. The interpretation is now in the context of the
> >> traffic mode. So in Override mode the ASP which has generated the ASP AC
> >> will take on the active role, in case of loadshare it will be kind of
> >> parallel processing and in broadcast all the ASPs will process the same
> >> traffic simultaneously.
> >>
> >>
> >>
> >> That means there is some control function which will decide when the
> >> application is ready and traffic can be started. Now I may design my
> >> system
> >> which will first complete all the application level readiness functions
> >> and
> >> then will start with ASP UP. In that case it is possible that as soon as
> I
> >> receive and ASP UP ack I will send ASP ACT immediately.
> >>
> > that will be a good design. But i am not convinced that the readiness of
> the
> > application layer is the reason why sending of ASP Active is marked as
> MAY
> > in RFC4666. what if LM is the one who is triggering ASPSM and ASPTM
> > messages. in that case your design requires LM to communicate to both
> M3UA
> > layer and upper layer. there are only following boundaries defined
> between
> > M3UA and MTP3 User layers -
> >
> >       MTP-TRANSFER request
> >       MTP-TRANSFER indication
> >       MTP-PAUSE indication
> >       MTP-RESUME indication
> >       MTP-STATUS indication
> >
> >
> >>
> >> To answer your question if ASP AC can be triggered from a particular ASP
> I
> >> would say yes when ASPs are running in high availability framework it is
> >> the
> >> framework which directs a particular ASP to assume ACTIVE role and then
> >> only
> >> that specific ASP will initiate the ASP ACK message to SGP. The
> framework
> >> may determine the active ASP based on multiple factors like nodes
> priority
> >> in that framework, its previous restart history, the state of
> application
> >> functions etc.
> >>
> >>
> >>
> >> Regards
> >>
> >> Deepak
> >>  ------------------------------
> >>
> >> *From:* Anand N Ilkal [mailto:anandnilkal@gmail.com]
> >> *Sent:* Tuesday, January 04, 2011 3:49 PM
> >> *To:* arif khan; Deepak Gunjal
> >> *Cc:* sigtran@ietf.org
> >> *Subject:* Re: [Sigtran] ASP active procedure
> >>
> >>
> >>
> >> Hello Deepak,
> >>
> >>
> >>
> >> I understand that there needs to be local check whether stack is ready
> to
> >> receive traffic for that routing key.
> >>
> >>
> >>
> >> lets assume all those scenarios are satisfied. and i am pretty sure that
> >> when RFC says MAY, it has taken all these cases into account (for
> example
> >> you can read from NOTIFY procedures - for NOTIFY to be sent, lot of
> >> conditions needs to be satisfied - like n number of ASP's being active.
> >> Yet
> >> RFC uses the words like MUST or SHOULD) .
> >>
> >>
> >>
> >> If traffic modes are to be taken into account, what should act as
> trigger
> >> for sending ASP Active message from a perticular ASP?
> >>
> >>
> >>
> >> Hence my opinion is ASP Up Ack is only a sufficient condition, where-as
> >> NOTIFY from peer acts as necessary condition.
> >>
> >> can any comment on that?
> >>
> >>
> >>
> >> On 4 January 2011 14:01, arif khan <arif15jan@gmail.com> wrote:
> >>
> >> Implementation logic is ok in their own context ...........
> >> But ASP can process the TRAFFIC message only after the ASP ACT ACK
> >> received from the NW and local side ASP with the remote ASP change
> >> their state and becomes ready to process the TRAFFIC.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
> >> > As per my opinion the ASP ACTIVE is triggered after the reception of
> ASP
> >> UP
> >> > ACK only but the trigger point may not be immediate. The trigger point
> >> can
> >> > be an indication from high availability framework; it could be some
> >> > application logic which once determines via local procedures that it
> is
> >> > ready to process the application traffic from network can initiate ASP
> >> > ACTIVE to SGP.
> >> >
> >> > Regards
> >> > Deepak
> >> >
> >> > ________________________________
> >> > From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On
> >> Behalf
> >> > Of Anand N Ilkal
> >> > Sent: Tuesday, January 04, 2011 1:22 PM
> >> > To: sigtran@ietf.org
> >> > Subject: [Sigtran] ASP active procedure
> >> >
> >> > Hello,
> >> >
> >> > i have doubt regarding the following section is RFC 4666  -
> >> > 4.3.4.3.  ASP Active Procedures
> >> >
> >> >    Anytime after the ASP has received an ASP Up Ack message from the
> SGP
> >> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
> >> >    indicating that the ASP is ready to start processing traffic....
> >> >
> >> > 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
> >> > 2. is receipt of ASP Up Ack message is treated as sufficient
> condition,
> >> > whereas there is a necessary condition which should be satisfied so as
> >> ASP
> >> > active message is sent? if so, what is that condition?
> >> >
> >> > --
> >> > with regards,
> >> > Anand kumar Ilkal
> >> >
> >> > ________________________________
> >> > "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising
> >> from
> >> > the use of the information transmitted by this email including damage
> >> from
> >> > virus."
> >> >
> >>
> >>
> >>
> >>
> >> --
> >> with regards,
> >> Anand kumar Ilkal
> >>
> >> ------------------------------
> >> "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising
> from
> >> the use of the information transmitted by this email including damage
> from
> >> virus."
> >>
> >
> >
> >
> > --
> > with regards,
> > Anand kumar Ilkal
> >
>



-- 
with regards,
Anand kumar Ilkal

--0023547c90154a3e7504990ff668
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Arif, Deepak,<div><br></div><div>This is not a special scenario, whic=
h would require special handling by either M3UA layer or LM.</div><div>My a=
rgument is, this section could have very well been written as follows -</di=
v>
<div><br></div><div><span class=3D"Apple-style-span" style=3D"font-family: =
arial, sans-serif; font-size: 13px; border-collapse: collapse; "><div style=
=3D"color: rgb(80, 0, 80); ">4.3.4.3. =A0ASP Active Procedures</div><div st=
yle=3D"color: rgb(80, 0, 80); ">
<br></div><div style=3D"color: rgb(80, 0, 80); ">=A0=A0 Anytime after the A=
SP has received an ASP Up Ack message from the SGP</div><div><font class=3D=
"Apple-style-span" color=3D"#500050">=A0=A0 or IPSP, the ASP </font><font c=
lass=3D"Apple-style-span" color=3D"#FF0000">SHOULD</font><font class=3D"App=
le-style-span" color=3D"#500050">(or </font><font class=3D"Apple-style-span=
" color=3D"#FF0000">MUST</font><font class=3D"Apple-style-span" color=3D"#5=
00050">) send an ASP Active message to the SGP,</font></div>
<div style=3D"color: rgb(80, 0, 80); ">=A0=A0 indicating that the ASP is re=
ady to start processing traffic....</div><div style=3D"color: rgb(80, 0, 80=
); "><br></div><div>This would have covered all the scenarios related to re=
adiness of the traffic handling (and management blocking). <b>But text is n=
ot as shown here</b>, hence receipt of ASP Up Ack is just a sufficient cond=
ition where-as NOTIFY serves the necessary condition to send ASP Active mes=
sage.</div>
<div><br></div><div>I would like you to comment on this sufficient and nece=
ssary conditions.</div></span><br><div class=3D"gmail_quote">On 4 January 2=
011 23:07, arif khan <span dir=3D"ltr">&lt;<a href=3D"mailto:arif15jan@gmai=
l.com">arif15jan@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Yes this is the implementation need to hand=
le this kind of situation.<br>
Suppose if Peer is already in ASP ACT state or any other<br>
state(excluding, waiting for the ASP UP ACK) and receives such<br>
messages then state machine of the ASP should perform the state change<br>
and should come to the original state.<br>
<br>
This could be done by the system management entity to handle this kind<br>
of situation.<br>
<div class=3D"im"><br>
<br>
<br>
<br>
On 1/4/11, Anand N Ilkal &lt;<a href=3D"mailto:anandnilkal@gmail.com">anand=
nilkal@gmail.com</a>&gt; wrote:<br>
</div><div><div></div><div class=3D"h5">&gt; Hello Deepak, arif,<br>
&gt;<br>
&gt; Please find my comments below -<br>
&gt;<br>
&gt; According to RFC 4666, section -<br>
&gt; 4.3.4.3. =A0ASP Active Procedures<br>
&gt;<br>
&gt; =A0 =A0Anytime after the ASP has received an ASP Up Ack message from t=
he SGP<br>
&gt; =A0 =A0or IPSP, the ASP MAY send an ASP Active message to the SGP,<br>
&gt; =A0 =A0indicating that the ASP is ready to start processing traffic...=
.<br>
&gt;<br>
&gt; what if i decide not to send ASP Active after receiving ASP Up Ack , w=
hen<br>
&gt; can i decide again to send ASP Active?<br>
&gt;<br>
&gt; On 4 January 2011 16:31, Deepak Gunjal &lt;<a href=3D"mailto:deepak.gu=
njal@aricent.com">deepak.gunjal@aricent.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; =A0Hi Anand,<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Generally the application logic is treated separately from the tra=
nsport<br>
&gt;&gt; layer which is here M3UA layer. So it is not necessary that if the=
<br>
&gt;&gt; transport<br>
&gt;&gt; layer is ready at a node then its application layer will also be i=
n a<br>
&gt;&gt; ready<br>
&gt;&gt; state.<br>
&gt;&gt;<br>
&gt; Agreed : in the entirety of the M3UA layer, it should never depend on =
the<br>
&gt; status of the upper layer. always upper layers use the services of the=
 lower<br>
&gt; layers. otherway is seldom used.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The M3UA ASP UP message signifies the availability of transport fu=
nction<br>
&gt;&gt; at<br>
&gt;&gt; ASP but not about the application layer processing function on the=
 same<br>
&gt;&gt; ASP.<br>
&gt;&gt; Also in similar fashion SGP sends ASP UP Ack to indicate its avail=
ability<br>
&gt;&gt; to<br>
&gt;&gt; accept the protocol messages only.<br>
&gt;&gt;<br>
&gt; Consider the hypothetical stack configuration, where only till M3UA la=
yer is<br>
&gt; configured, does it mean, it can not send ASP Active Message? I do not=
 think<br>
&gt; so.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; By sending ASP ACTIVE an ASP indicates that now it can generate an=
d<br>
&gt;&gt; process<br>
&gt;&gt; the user layer traffic and by sending ASP ACTIVE Ack SGP also indi=
cates<br>
&gt;&gt; the<br>
&gt;&gt; same.<br>
&gt;&gt;<br>
&gt; if application layer is not available local M3UA layer simply drops<br=
>
&gt; message.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; So there is a distinction as I interpret the RFC for having TWO di=
fferent<br>
&gt;&gt; messages viz. ASP UP and ASP ACTIVE which I think have been design=
ed for<br>
&gt;&gt; such aspects. Also note that the application subsequently can init=
iate ASP<br>
&gt;&gt; ACTIVE from another ASP. The interpretation is now in the context =
of the<br>
&gt;&gt; traffic mode. So in Override mode the ASP which has generated the =
ASP AC<br>
&gt;&gt; will take on the active role, in case of loadshare it will be kind=
 of<br>
&gt;&gt; parallel processing and in broadcast all the ASPs will process the=
 same<br>
&gt;&gt; traffic simultaneously.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; That means there is some control function which will decide when t=
he<br>
&gt;&gt; application is ready and traffic can be started. Now I may design =
my<br>
&gt;&gt; system<br>
&gt;&gt; which will first complete all the application level readiness func=
tions<br>
&gt;&gt; and<br>
&gt;&gt; then will start with ASP UP. In that case it is possible that as s=
oon as I<br>
&gt;&gt; receive and ASP UP ack I will send ASP ACT immediately.<br>
&gt;&gt;<br>
&gt; that will be a good design. But i am not convinced that the readiness =
of the<br>
&gt; application layer is the reason why sending of ASP Active is marked as=
 MAY<br>
&gt; in RFC4666. what if LM is the one who is triggering ASPSM and ASPTM<br=
>
&gt; messages. in that case your design requires LM to communicate to both =
M3UA<br>
&gt; layer and upper layer. there are only following boundaries defined bet=
ween<br>
&gt; M3UA and MTP3 User layers -<br>
&gt;<br>
&gt; =A0 =A0 =A0 MTP-TRANSFER request<br>
&gt; =A0 =A0 =A0 MTP-TRANSFER indication<br>
&gt; =A0 =A0 =A0 MTP-PAUSE indication<br>
&gt; =A0 =A0 =A0 MTP-RESUME indication<br>
&gt; =A0 =A0 =A0 MTP-STATUS indication<br>
&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; To answer your question if ASP AC can be triggered from a particul=
ar ASP I<br>
&gt;&gt; would say yes when ASPs are running in high availability framework=
 it is<br>
&gt;&gt; the<br>
&gt;&gt; framework which directs a particular ASP to assume ACTIVE role and=
 then<br>
&gt;&gt; only<br>
&gt;&gt; that specific ASP will initiate the ASP ACK message to SGP. The fr=
amework<br>
&gt;&gt; may determine the active ASP based on multiple factors like nodes =
priority<br>
&gt;&gt; in that framework, its previous restart history, the state of appl=
ication<br>
&gt;&gt; functions etc.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Regards<br>
&gt;&gt;<br>
&gt;&gt; Deepak<br>
&gt;&gt; =A0------------------------------<br>
&gt;&gt;<br>
&gt;&gt; *From:* Anand N Ilkal [mailto:<a href=3D"mailto:anandnilkal@gmail.=
com">anandnilkal@gmail.com</a>]<br>
&gt;&gt; *Sent:* Tuesday, January 04, 2011 3:49 PM<br>
&gt;&gt; *To:* arif khan; Deepak Gunjal<br>
&gt;&gt; *Cc:* <a href=3D"mailto:sigtran@ietf.org">sigtran@ietf.org</a><br>
&gt;&gt; *Subject:* Re: [Sigtran] ASP active procedure<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Hello Deepak,<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; I understand that there needs to be local check whether stack is r=
eady to<br>
&gt;&gt; receive traffic for that routing key.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; lets assume all those scenarios are satisfied. and i am pretty sur=
e that<br>
&gt;&gt; when RFC says MAY, it has taken all these cases into account (for =
example<br>
&gt;&gt; you can read from NOTIFY procedures - for NOTIFY to be sent, lot o=
f<br>
&gt;&gt; conditions needs to be satisfied - like n number of ASP&#39;s bein=
g active.<br>
&gt;&gt; Yet<br>
&gt;&gt; RFC uses the words like MUST or SHOULD) .<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; If traffic modes are to be taken into account, what should act as =
trigger<br>
&gt;&gt; for sending ASP Active message from a perticular ASP?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Hence my opinion is ASP Up Ack is only a sufficient condition, whe=
re-as<br>
&gt;&gt; NOTIFY from peer acts as necessary condition.<br>
&gt;&gt;<br>
&gt;&gt; can any comment on that?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On 4 January 2011 14:01, arif khan &lt;<a href=3D"mailto:arif15jan=
@gmail.com">arif15jan@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Implementation logic is ok in their own context ...........<br>
&gt;&gt; But ASP can process the TRAFFIC message only after the ASP ACT ACK=
<br>
&gt;&gt; received from the NW and local side ASP with the remote ASP change=
<br>
&gt;&gt; their state and becomes ready to process the TRAFFIC.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On 1/4/11, Deepak Gunjal &lt;<a href=3D"mailto:deepak.gunjal@arice=
nt.com">deepak.gunjal@aricent.com</a>&gt; wrote:<br>
&gt;&gt; &gt; As per my opinion the ASP ACTIVE is triggered after the recep=
tion of ASP<br>
&gt;&gt; UP<br>
&gt;&gt; &gt; ACK only but the trigger point may not be immediate. The trig=
ger point<br>
&gt;&gt; can<br>
&gt;&gt; &gt; be an indication from high availability framework; it could b=
e some<br>
&gt;&gt; &gt; application logic which once determines via local procedures =
that it is<br>
&gt;&gt; &gt; ready to process the application traffic from network can ini=
tiate ASP<br>
&gt;&gt; &gt; ACTIVE to SGP.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Regards<br>
&gt;&gt; &gt; Deepak<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; ________________________________<br>
&gt;&gt; &gt; From: <a href=3D"mailto:sigtran-bounces@ietf.org">sigtran-bou=
nces@ietf.org</a> [mailto:<a href=3D"mailto:sigtran-bounces@ietf.org">sigtr=
an-bounces@ietf.org</a>] On<br>
&gt;&gt; Behalf<br>
&gt;&gt; &gt; Of Anand N Ilkal<br>
&gt;&gt; &gt; Sent: Tuesday, January 04, 2011 1:22 PM<br>
&gt;&gt; &gt; To: <a href=3D"mailto:sigtran@ietf.org">sigtran@ietf.org</a><=
br>
&gt;&gt; &gt; Subject: [Sigtran] ASP active procedure<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Hello,<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; i have doubt regarding the following section is RFC 4666 =A0-=
<br>
&gt;&gt; &gt; 4.3.4.3. =A0ASP Active Procedures<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; =A0 =A0Anytime after the ASP has received an ASP Up Ack messa=
ge from the SGP<br>
&gt;&gt; &gt; =A0 =A0or IPSP, the ASP MAY send an ASP Active message to the=
 SGP,<br>
&gt;&gt; &gt; =A0 =A0indicating that the ASP is ready to start processing t=
raffic....<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; 1. why ASP MAY chose not to send ASP active on receipt of ASP=
 Up Ack?<br>
&gt;&gt; &gt; 2. is receipt of ASP Up Ack message is treated as sufficient =
condition,<br>
&gt;&gt; &gt; whereas there is a necessary condition which should be satisf=
ied so as<br>
&gt;&gt; ASP<br>
&gt;&gt; &gt; active message is sent? if so, what is that condition?<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; --<br>
&gt;&gt; &gt; with regards,<br>
&gt;&gt; &gt; Anand kumar Ilkal<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; ________________________________<br>
&gt;&gt; &gt; &quot;DISCLAIMER: This message is proprietary to Aricent and =
is intended<br>
&gt;&gt; solely<br>
&gt;&gt; &gt; for the use of the individual to whom it is addressed. It may=
 contain<br>
&gt;&gt; &gt; privileged or confidential information and should not be circ=
ulated or<br>
&gt;&gt; used<br>
&gt;&gt; &gt; for any purpose other than for what it is intended. If you ha=
ve received<br>
&gt;&gt; &gt; this message in error, please notify the originator immediate=
ly. If you<br>
&gt;&gt; are<br>
&gt;&gt; &gt; not the intended recipient, you are notified that you are str=
ictly<br>
&gt;&gt; &gt; prohibited from using, copying, altering, or disclosing the c=
ontents of<br>
&gt;&gt; this<br>
&gt;&gt; &gt; message. Aricent accepts no responsibility for loss or damage=
 arising<br>
&gt;&gt; from<br>
&gt;&gt; &gt; the use of the information transmitted by this email includin=
g damage<br>
&gt;&gt; from<br>
&gt;&gt; &gt; virus.&quot;<br>
&gt;&gt; &gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; with regards,<br>
&gt;&gt; Anand kumar Ilkal<br>
&gt;&gt;<br>
&gt;&gt; ------------------------------<br>
&gt;&gt; &quot;DISCLAIMER: This message is proprietary to Aricent and is in=
tended solely<br>
&gt;&gt; for the use of the individual to whom it is addressed. It may cont=
ain<br>
&gt;&gt; privileged or confidential information and should not be circulate=
d or<br>
&gt;&gt; used<br>
&gt;&gt; for any purpose other than for what it is intended. If you have re=
ceived<br>
&gt;&gt; this message in error, please notify the originator immediately. I=
f you<br>
&gt;&gt; are<br>
&gt;&gt; not the intended recipient, you are notified that you are strictly=
<br>
&gt;&gt; prohibited from using, copying, altering, or disclosing the conten=
ts of<br>
&gt;&gt; this<br>
&gt;&gt; message. Aricent accepts no responsibility for loss or damage aris=
ing from<br>
&gt;&gt; the use of the information transmitted by this email including dam=
age from<br>
&gt;&gt; virus.&quot;<br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; with regards,<br>
&gt; Anand kumar Ilkal<br>
&gt;<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>with regard=
s,<br>Anand kumar Ilkal<br>
</div>

--0023547c90154a3e7504990ff668--

From cbenson@adax.com  Tue Jan  4 19:03:33 2011
Return-Path: <cbenson@adax.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 161FB3A68DA for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 19:03:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.429
X-Spam-Level: 
X-Spam-Status: No, score=-1.429 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_62=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VXGA9n3RUshT for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 19:03:31 -0800 (PST)
Received: from mail1.adax.com (mail1.adax.com [208.201.231.104]) by core3.amsl.com (Postfix) with ESMTP id E465F3A67E9 for <sigtran@ietf.org>; Tue,  4 Jan 2011 19:03:29 -0800 (PST)
Received: from adax (adax [12.0.0.88]) by mail1.adax.com (Postfix) with ESMTP id 0C87A120A0E; Tue,  4 Jan 2011 19:05:37 -0800 (PST)
Received: by adax (Postfix, from userid 243) id 69DE08EDD0; Tue,  4 Jan 2011 19:07:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by adax (Postfix) with ESMTP id 60D638EDCF; Tue,  4 Jan 2011 19:07:24 -0800 (PST)
Date: Tue, 4 Jan 2011 19:07:24 -0800 (PST)
From: Chris Benson <cbenson@adax.com>
X-X-Sender: cbenson@adax.adax
To: Anand N Ilkal <anandnilkal@gmail.com>
In-Reply-To: <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1101041848300.15433@adax.adax>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com> <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com> <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 03:03:33 -0000

Anand,

I believe that the aspect of RFC 4666 that provides the
answer to your question is found in Section 1.6.3. ...

M-ASP_ACTIVE request
Direction:  LM -> M3UA
Purpose: LM requests that ASP send an ASP Active message to its peer.

An ASP Active message is sent both when the local M3UA is
in the appropriate state *AND* when "Layer Management"
makes this request.  Therefore, Section 4.3.4.3 only
suggests that an ASP Active message MAY be sent.  There's
no intention that this messgae always be sent immediately
and automatically/unilaterally by M3UA itself.

You could choose to implement a "Layer Management" entity
that does automatically issue a M-ASP_ACTIVE request
just as soon as it receives an M-ASP UP confirm from
the local M3UA ASP, but the RFC does not require that,
in part because this "Layer Management" is not part of
M3UA itself.  The "Layer Management" entity could even
be a bureaucrat or trained monkey.  An extreme analogy,
but the point is that LM decides to move an ASP to
Active state, although the M3UA's ASP state enforces
required conditions as described in Section 4.3.1. etc.

This is the model of RFC 4666 rather than one in which
states always progress automatically towards data transfer.

I hope this helps, from Chris Benson.


On Wed, 5 Jan 2011, Anand N Ilkal wrote:

>>  Date: Wed, 5 Jan 2011 07:45:42 +0530
>>  From: Anand N Ilkal <anandnilkal@gmail.com>
>>  To: arif khan <arif15jan@gmail.com>
>>  Cc: "sigtran@ietf.org" <sigtran@ietf.org>
>>  Subject: Re: [Sigtran] ASP active procedure
>>  
>>  Hello Arif, Deepak,
>>  
>>  This is not a special scenario, which would require special handling by
>>  either M3UA layer or LM.
>>  My argument is, this section could have very well been written as follows -
>>  
>>  4.3.4.3.  ASP Active Procedures
>>  
>>     Anytime after the ASP has received an ASP Up Ack message from the SGP
>>     or IPSP, the ASP SHOULD(or MUST) send an ASP Active message to the SGP,
>>     indicating that the ASP is ready to start processing traffic....
>>  
>>  This would have covered all the scenarios related to readiness of the
>>  traffic handling (and management blocking). *But text is not as shown here*,
>>  hence receipt of ASP Up Ack is just a sufficient condition where-as NOTIFY
>>  serves the necessary condition to send ASP Active message.
>>  
>>  I would like you to comment on this sufficient and necessary conditions.
>>  
>>  On 4 January 2011 23:07, arif khan <arif15jan@gmail.com> wrote:
>>  
>>  > Yes this is the implementation need to handle this kind of situation.
>>  > Suppose if Peer is already in ASP ACT state or any other
>>  > state(excluding, waiting for the ASP UP ACK) and receives such
>>  > messages then state machine of the ASP should perform the state change
>>  > and should come to the original state.
>>  >
>>  > This could be done by the system management entity to handle this kind
>>  > of situation.
>>  >
>>  >
>>  >
>>  >
>>  > On 1/4/11, Anand N Ilkal <anandnilkal@gmail.com> wrote:
>>  > > Hello Deepak, arif,
>>  > >
>>  > > Please find my comments below -
>>  > >
>>  > > According to RFC 4666, section -
>>  > > 4.3.4.3.  ASP Active Procedures
>>  > >
>>  > >    Anytime after the ASP has received an ASP Up Ack message from the SGP
>>  > >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>>  > >    indicating that the ASP is ready to start processing traffic....
>>  > >
>>  > > what if i decide not to send ASP Active after receiving ASP Up Ack , when
>>  > > can i decide again to send ASP Active?
>>  > >
>>  > > On 4 January 2011 16:31, Deepak Gunjal <deepak.gunjal@aricent.com>
>>  > wrote:
>>  > >
>>  > >>  Hi Anand,
>>  > >>
>>  > >>
>>  > >>
>>  > >> Generally the application logic is treated separately from the transport
>>  > >> layer which is here M3UA layer. So it is not necessary that if the
>>  > >> transport
>>  > >> layer is ready at a node then its application layer will also be in a
>>  > >> ready
>>  > >> state.
>>  > >>
>>  > > Agreed : in the entirety of the M3UA layer, it should never depend on the
>>  > > status of the upper layer. always upper layers use the services of the
>>  > lower
>>  > > layers. otherway is seldom used.
>>  > >
>>  > >>
>>  > >>
>>  > >> The M3UA ASP UP message signifies the availability of transport function
>>  > >> at
>>  > >> ASP but not about the application layer processing function on the same
>>  > >> ASP.
>>  > >> Also in similar fashion SGP sends ASP UP Ack to indicate its
>>  > availability
>>  > >> to
>>  > >> accept the protocol messages only.
>>  > >>
>>  > > Consider the hypothetical stack configuration, where only till M3UA layer
>>  > is
>>  > > configured, does it mean, it can not send ASP Active Message? I do not
>>  > think
>>  > > so.
>>  > >
>>  > >>
>>  > >>
>>  > >> By sending ASP ACTIVE an ASP indicates that now it can generate and
>>  > >> process
>>  > >> the user layer traffic and by sending ASP ACTIVE Ack SGP also indicates
>>  > >> the
>>  > >> same.
>>  > >>
>>  > > if application layer is not available local M3UA layer simply drops
>>  > > message.
>>  > >
>>  > >>
>>  > >>
>>  > >> So there is a distinction as I interpret the RFC for having TWO
>>  > different
>>  > >> messages viz. ASP UP and ASP ACTIVE which I think have been designed for
>>  > >> such aspects. Also note that the application subsequently can initiate
>>  > ASP
>>  > >> ACTIVE from another ASP. The interpretation is now in the context of the
>>  > >> traffic mode. So in Override mode the ASP which has generated the ASP AC
>>  > >> will take on the active role, in case of loadshare it will be kind of
>>  > >> parallel processing and in broadcast all the ASPs will process the same
>>  > >> traffic simultaneously.
>>  > >>
>>  > >>
>>  > >>
>>  > >> That means there is some control function which will decide when the
>>  > >> application is ready and traffic can be started. Now I may design my
>>  > >> system
>>  > >> which will first complete all the application level readiness functions
>>  > >> and
>>  > >> then will start with ASP UP. In that case it is possible that as soon as
>>  > I
>>  > >> receive and ASP UP ack I will send ASP ACT immediately.
>>  > >>
>>  > > that will be a good design. But i am not convinced that the readiness of
>>  > the
>>  > > application layer is the reason why sending of ASP Active is marked as
>>  > MAY
>>  > > in RFC4666. what if LM is the one who is triggering ASPSM and ASPTM
>>  > > messages. in that case your design requires LM to communicate to both
>>  > M3UA
>>  > > layer and upper layer. there are only following boundaries defined
>>  > between
>>  > > M3UA and MTP3 User layers -
>>  > >
>>  > >       MTP-TRANSFER request
>>  > >       MTP-TRANSFER indication
>>  > >       MTP-PAUSE indication
>>  > >       MTP-RESUME indication
>>  > >       MTP-STATUS indication
>>  > >
>>  > >
>>  > >>
>>  > >> To answer your question if ASP AC can be triggered from a particular ASP
>>  > I
>>  > >> would say yes when ASPs are running in high availability framework it is
>>  > >> the
>>  > >> framework which directs a particular ASP to assume ACTIVE role and then
>>  > >> only
>>  > >> that specific ASP will initiate the ASP ACK message to SGP. The
>>  > framework
>>  > >> may determine the active ASP based on multiple factors like nodes
>>  > priority
>>  > >> in that framework, its previous restart history, the state of
>>  > application
>>  > >> functions etc.
>>  > >>
>>  > >>
>>  > >>
>>  > >> Regards
>>  > >>
>>  > >> Deepak
>>  > >>  ------------------------------
>>  > >>
>>  > >> *From:* Anand N Ilkal [mailto:anandnilkal@gmail.com]
>>  > >> *Sent:* Tuesday, January 04, 2011 3:49 PM
>>  > >> *To:* arif khan; Deepak Gunjal
>>  > >> *Cc:* sigtran@ietf.org
>>  > >> *Subject:* Re: [Sigtran] ASP active procedure
>>  > >>
>>  > >>
>>  > >>
>>  > >> Hello Deepak,
>>  > >>
>>  > >>
>>  > >>
>>  > >> I understand that there needs to be local check whether stack is ready
>>  > to
>>  > >> receive traffic for that routing key.
>>  > >>
>>  > >>
>>  > >>
>>  > >> lets assume all those scenarios are satisfied. and i am pretty sure that
>>  > >> when RFC says MAY, it has taken all these cases into account (for
>>  > example
>>  > >> you can read from NOTIFY procedures - for NOTIFY to be sent, lot of
>>  > >> conditions needs to be satisfied - like n number of ASP's being active.
>>  > >> Yet
>>  > >> RFC uses the words like MUST or SHOULD) .
>>  > >>
>>  > >>
>>  > >>
>>  > >> If traffic modes are to be taken into account, what should act as
>>  > trigger
>>  > >> for sending ASP Active message from a perticular ASP?
>>  > >>
>>  > >>
>>  > >>
>>  > >> Hence my opinion is ASP Up Ack is only a sufficient condition, where-as
>>  > >> NOTIFY from peer acts as necessary condition.
>>  > >>
>>  > >> can any comment on that?
>>  > >>
>>  > >>
>>  > >>
>>  > >> On 4 January 2011 14:01, arif khan <arif15jan@gmail.com> wrote:
>>  > >>
>>  > >> Implementation logic is ok in their own context ...........
>>  > >> But ASP can process the TRAFFIC message only after the ASP ACT ACK
>>  > >> received from the NW and local side ASP with the remote ASP change
>>  > >> their state and becomes ready to process the TRAFFIC.
>>  > >>
>>  > >>
>>  > >>
>>  > >>
>>  > >>
>>  > >>
>>  > >>
>>  > >>
>>  > >>
>>  > >>
>>  > >> On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
>>  > >> > As per my opinion the ASP ACTIVE is triggered after the reception of
>>  > ASP
>>  > >> UP
>>  > >> > ACK only but the trigger point may not be immediate. The trigger point
>>  > >> can
>>  > >> > be an indication from high availability framework; it could be some
>>  > >> > application logic which once determines via local procedures that it
>>  > is
>>  > >> > ready to process the application traffic from network can initiate ASP
>>  > >> > ACTIVE to SGP.
>>  > >> >
>>  > >> > Regards
>>  > >> > Deepak
>>  > >> >
>>  > >> > ________________________________
>>  > >> > From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On
>>  > >> Behalf
>>  > >> > Of Anand N Ilkal
>>  > >> > Sent: Tuesday, January 04, 2011 1:22 PM
>>  > >> > To: sigtran@ietf.org
>>  > >> > Subject: [Sigtran] ASP active procedure
>>  > >> >
>>  > >> > Hello,
>>  > >> >
>>  > >> > i have doubt regarding the following section is RFC 4666  -
>>  > >> > 4.3.4.3.  ASP Active Procedures
>>  > >> >
>>  > >> >    Anytime after the ASP has received an ASP Up Ack message from the
>>  > SGP
>>  > >> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>>  > >> >    indicating that the ASP is ready to start processing traffic....
>>  > >> >
>>  > >> > 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
>>  > >> > 2. is receipt of ASP Up Ack message is treated as sufficient
>>  > condition,
>>  > >> > whereas there is a necessary condition which should be satisfied so as
>>  > >> ASP
>>  > >> > active message is sent? if so, what is that condition?
>>  > >> >
>>  > >> > --
>>  > >> > with regards,
>>  > >> > Anand kumar Ilkal
>>  > >> >
>>  > >> > ________________________________
>>  > >> > "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising
>>  > >> from
>>  > >> > the use of the information transmitted by this email including damage
>>  > >> from
>>  > >> > virus."
>>  > >> >
>>  > >>
>>  > >>
>>  > >>
>>  > >>
>>  > >> --
>>  > >> with regards,
>>  > >> Anand kumar Ilkal
>>  > >>
>>  > >> ------------------------------
>>  > >> "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising
>>  > from
>>  > >> the use of the information transmitted by this email including damage
>>  > from
>>  > >> virus."
>>  > >>
>>  > >
>>  > >
>>  > >
>>  > > --
>>  > > with regards,
>>  > > Anand kumar Ilkal
>>  > >
>>  >
>>  
>>  
>>  
>>  -- 
>>  with regards,
>>  Anand kumar Ilkal
>>  

From anandnilkal@gmail.com  Tue Jan  4 21:17:45 2011
Return-Path: <anandnilkal@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 525B03A6805 for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 21:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level: 
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[AWL=-0.133, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_62=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GsBeNCMjeWXU for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 21:17:42 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 794CB3A67A2 for <sigtran@ietf.org>; Tue,  4 Jan 2011 21:17:42 -0800 (PST)
Received: by ywk9 with SMTP id 9so6649405ywk.31 for <sigtran@ietf.org>; Tue, 04 Jan 2011 21:19:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=6r6kZcr6nxj5TeCjuO85K3eTnUElOlXo6aUVnVXokE4=; b=W9yySnvlAfYmKY4UmPpfzrG+6iOKBvLssE1cWZ7ucBhVfPPQhr3DwJhadCZ9tXoKPW btQIOge/MnDyrMMk5xc32Zdq/bAWtat/G06TpaPC1/sE7xCR3fcOahCctEGDoRu/PiaD TGNjqiLzahBmFL1c3Qo36ivNSBAIAJuq8i6kc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=oGQgplkpTu8QX6CVVSB+hWObSZKTyi7bbyGAjwFGxWR5l4Jpe84Xi9eTAB20Jj208V Pt957eLafQxJwLLmtT3XPU+DhTGDu5rHnpSmeH7LwpZD755WRGnCSfHvmDYybaN7HMsM fykwGND1O+lbNYzRPhFCqlRKO/cqVi17akLjA=
MIME-Version: 1.0
Received: by 10.236.110.6 with SMTP id t6mr357738yhg.17.1294204789296; Tue, 04 Jan 2011 21:19:49 -0800 (PST)
Received: by 10.236.108.145 with HTTP; Tue, 4 Jan 2011 21:19:49 -0800 (PST)
In-Reply-To: <Pine.LNX.4.64.1101041848300.15433@adax.adax>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com> <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com> <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com> <Pine.LNX.4.64.1101041848300.15433@adax.adax>
Date: Wed, 5 Jan 2011 10:49:49 +0530
Message-ID: <AANLkTikk6_rOtZwbeTcENxHsx++fS=m7UvAS5LsFm6C8@mail.gmail.com>
From: Anand N Ilkal <anandnilkal@gmail.com>
To: Chris Benson <cbenson@adax.com>
Content-Type: multipart/alternative; boundary=0023547c9015bbad770499128870
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 05:17:45 -0000

--0023547c9015bbad770499128870
Content-Type: text/plain; charset=ISO-8859-1

Hello Chris,

That certainly help -
Please find my comments inline.

On 5 January 2011 08:37, Chris Benson <cbenson@adax.com> wrote:

> Anand,
>
> I believe that the aspect of RFC 4666 that provides the
> answer to your question is found in Section 1.6.3. ...
>
> M-ASP_ACTIVE request
> Direction:  LM -> M3UA
> Purpose: LM requests that ASP send an ASP Active message to its peer.
>
> An ASP Active message is sent both when the local M3UA is
> in the appropriate state *AND* when "Layer Management"
> makes this request.  Therefore, Section 4.3.4.3 only
> suggests that an ASP Active message MAY be sent.  There's
> no intention that this messgae always be sent immediately
> and automatically/unilaterally by M3UA itself.
>
Agreed, then is it safe for me to decide to send ASP Active if M3UA layer is
ready to receive traffic and  it has received ASP Up Ack?
then how about the scenario where n+k ASP's are configured in an AS, there
are already n ASP's active. n+1th ASP has received ASP Up Ack. Since M3UA
layer is ready to receive traffic, can this ASP also send ASP Active ?
(although it can send since there is no problem if there are n+1 ASP's
active in that perticular AS, just it could happen that n+1th ASP may be
part of other AS's too, hence i do not want to load it further unless it is
required)

>
> You could choose to implement a "Layer Management" entity
> that does automatically issue a M-ASP_ACTIVE request
> just as soon as it receives an M-ASP UP confirm from
> the local M3UA ASP, but the RFC does not require that,
> in part because this "Layer Management" is not part of
> M3UA itself.  The "Layer Management" entity could even
> be a bureaucrat or trained monkey.  An extreme analogy,
> but the point is that LM decides to move an ASP to
> Active state, although the M3UA's ASP state enforces
> required conditions as described in Section 4.3.1. etc.
>

Yes, RFC does not cover Layer Manager. But to cover n+k model, traffic mode
support, RFC recommends either internal logic in M3UA layer or use of NOTIFY
message to arrive at conclusive decision whether to send ASP Active or not.
Hence this internal logic or NOTIFY procedure are the necessary condition to
ultimately decide whether to send ASP Active from a particular ASP or not.

Although NOTIFY messages carry only advisory importance, but their
procedures are non-optional. it is at implementor discretion whether to make
use of those or not.

>
> This is the model of RFC 4666 rather than one in which
> states always progress automatically towards data transfer.
>
> I hope this helps, from Chris Benson.
>
>
> On Wed, 5 Jan 2011, Anand N Ilkal wrote:
>
> >>  Date: Wed, 5 Jan 2011 07:45:42 +0530
> >>  From: Anand N Ilkal <anandnilkal@gmail.com>
> >>  To: arif khan <arif15jan@gmail.com>
> >>  Cc: "sigtran@ietf.org" <sigtran@ietf.org>
> >>  Subject: Re: [Sigtran] ASP active procedure
> >>
> >>  Hello Arif, Deepak,
> >>
> >>  This is not a special scenario, which would require special handling by
> >>  either M3UA layer or LM.
> >>  My argument is, this section could have very well been written as
> follows -
> >>
> >>  4.3.4.3.  ASP Active Procedures
> >>
> >>     Anytime after the ASP has received an ASP Up Ack message from the
> SGP
> >>     or IPSP, the ASP SHOULD(or MUST) send an ASP Active message to the
> SGP,
> >>     indicating that the ASP is ready to start processing traffic....
> >>
> >>  This would have covered all the scenarios related to readiness of the
> >>  traffic handling (and management blocking). *But text is not as shown
> here*,
> >>  hence receipt of ASP Up Ack is just a sufficient condition where-as
> NOTIFY
> >>  serves the necessary condition to send ASP Active message.
> >>
> >>  I would like you to comment on this sufficient and necessary
> conditions.
> >>
> >>  On 4 January 2011 23:07, arif khan <arif15jan@gmail.com> wrote:
> >>
> >>  > Yes this is the implementation need to handle this kind of situation.
> >>  > Suppose if Peer is already in ASP ACT state or any other
> >>  > state(excluding, waiting for the ASP UP ACK) and receives such
> >>  > messages then state machine of the ASP should perform the state
> change
> >>  > and should come to the original state.
> >>  >
> >>  > This could be done by the system management entity to handle this
> kind
> >>  > of situation.
> >>  >
> >>  >
> >>  >
> >>  >
> >>  > On 1/4/11, Anand N Ilkal <anandnilkal@gmail.com> wrote:
> >>  > > Hello Deepak, arif,
> >>  > >
> >>  > > Please find my comments below -
> >>  > >
> >>  > > According to RFC 4666, section -
> >>  > > 4.3.4.3.  ASP Active Procedures
> >>  > >
> >>  > >    Anytime after the ASP has received an ASP Up Ack message from
> the SGP
> >>  > >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
> >>  > >    indicating that the ASP is ready to start processing traffic....
> >>  > >
> >>  > > what if i decide not to send ASP Active after receiving ASP Up Ack
> , when
> >>  > > can i decide again to send ASP Active?
> >>  > >
> >>  > > On 4 January 2011 16:31, Deepak Gunjal <deepak.gunjal@aricent.com>
> >>  > wrote:
> >>  > >
> >>  > >>  Hi Anand,
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> Generally the application logic is treated separately from the
> transport
> >>  > >> layer which is here M3UA layer. So it is not necessary that if the
> >>  > >> transport
> >>  > >> layer is ready at a node then its application layer will also be
> in a
> >>  > >> ready
> >>  > >> state.
> >>  > >>
> >>  > > Agreed : in the entirety of the M3UA layer, it should never depend
> on the
> >>  > > status of the upper layer. always upper layers use the services of
> the
> >>  > lower
> >>  > > layers. otherway is seldom used.
> >>  > >
> >>  > >>
> >>  > >>
> >>  > >> The M3UA ASP UP message signifies the availability of transport
> function
> >>  > >> at
> >>  > >> ASP but not about the application layer processing function on the
> same
> >>  > >> ASP.
> >>  > >> Also in similar fashion SGP sends ASP UP Ack to indicate its
> >>  > availability
> >>  > >> to
> >>  > >> accept the protocol messages only.
> >>  > >>
> >>  > > Consider the hypothetical stack configuration, where only till M3UA
> layer
> >>  > is
> >>  > > configured, does it mean, it can not send ASP Active Message? I do
> not
> >>  > think
> >>  > > so.
> >>  > >
> >>  > >>
> >>  > >>
> >>  > >> By sending ASP ACTIVE an ASP indicates that now it can generate
> and
> >>  > >> process
> >>  > >> the user layer traffic and by sending ASP ACTIVE Ack SGP also
> indicates
> >>  > >> the
> >>  > >> same.
> >>  > >>
> >>  > > if application layer is not available local M3UA layer simply drops
> >>  > > message.
> >>  > >
> >>  > >>
> >>  > >>
> >>  > >> So there is a distinction as I interpret the RFC for having TWO
> >>  > different
> >>  > >> messages viz. ASP UP and ASP ACTIVE which I think have been
> designed for
> >>  > >> such aspects. Also note that the application subsequently can
> initiate
> >>  > ASP
> >>  > >> ACTIVE from another ASP. The interpretation is now in the context
> of the
> >>  > >> traffic mode. So in Override mode the ASP which has generated the
> ASP AC
> >>  > >> will take on the active role, in case of loadshare it will be kind
> of
> >>  > >> parallel processing and in broadcast all the ASPs will process the
> same
> >>  > >> traffic simultaneously.
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> That means there is some control function which will decide when
> the
> >>  > >> application is ready and traffic can be started. Now I may design
> my
> >>  > >> system
> >>  > >> which will first complete all the application level readiness
> functions
> >>  > >> and
> >>  > >> then will start with ASP UP. In that case it is possible that as
> soon as
> >>  > I
> >>  > >> receive and ASP UP ack I will send ASP ACT immediately.
> >>  > >>
> >>  > > that will be a good design. But i am not convinced that the
> readiness of
> >>  > the
> >>  > > application layer is the reason why sending of ASP Active is marked
> as
> >>  > MAY
> >>  > > in RFC4666. what if LM is the one who is triggering ASPSM and ASPTM
> >>  > > messages. in that case your design requires LM to communicate to
> both
> >>  > M3UA
> >>  > > layer and upper layer. there are only following boundaries defined
> >>  > between
> >>  > > M3UA and MTP3 User layers -
> >>  > >
> >>  > >       MTP-TRANSFER request
> >>  > >       MTP-TRANSFER indication
> >>  > >       MTP-PAUSE indication
> >>  > >       MTP-RESUME indication
> >>  > >       MTP-STATUS indication
> >>  > >
> >>  > >
> >>  > >>
> >>  > >> To answer your question if ASP AC can be triggered from a
> particular ASP
> >>  > I
> >>  > >> would say yes when ASPs are running in high availability framework
> it is
> >>  > >> the
> >>  > >> framework which directs a particular ASP to assume ACTIVE role and
> then
> >>  > >> only
> >>  > >> that specific ASP will initiate the ASP ACK message to SGP. The
> >>  > framework
> >>  > >> may determine the active ASP based on multiple factors like nodes
> >>  > priority
> >>  > >> in that framework, its previous restart history, the state of
> >>  > application
> >>  > >> functions etc.
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> Regards
> >>  > >>
> >>  > >> Deepak
> >>  > >>  ------------------------------
> >>  > >>
> >>  > >> *From:* Anand N Ilkal [mailto:anandnilkal@gmail.com]
> >>  > >> *Sent:* Tuesday, January 04, 2011 3:49 PM
> >>  > >> *To:* arif khan; Deepak Gunjal
> >>  > >> *Cc:* sigtran@ietf.org
> >>  > >> *Subject:* Re: [Sigtran] ASP active procedure
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> Hello Deepak,
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> I understand that there needs to be local check whether stack is
> ready
> >>  > to
> >>  > >> receive traffic for that routing key.
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> lets assume all those scenarios are satisfied. and i am pretty
> sure that
> >>  > >> when RFC says MAY, it has taken all these cases into account (for
> >>  > example
> >>  > >> you can read from NOTIFY procedures - for NOTIFY to be sent, lot
> of
> >>  > >> conditions needs to be satisfied - like n number of ASP's being
> active.
> >>  > >> Yet
> >>  > >> RFC uses the words like MUST or SHOULD) .
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> If traffic modes are to be taken into account, what should act as
> >>  > trigger
> >>  > >> for sending ASP Active message from a perticular ASP?
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> Hence my opinion is ASP Up Ack is only a sufficient condition,
> where-as
> >>  > >> NOTIFY from peer acts as necessary condition.
> >>  > >>
> >>  > >> can any comment on that?
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> On 4 January 2011 14:01, arif khan <arif15jan@gmail.com> wrote:
> >>  > >>
> >>  > >> Implementation logic is ok in their own context ...........
> >>  > >> But ASP can process the TRAFFIC message only after the ASP ACT ACK
> >>  > >> received from the NW and local side ASP with the remote ASP change
> >>  > >> their state and becomes ready to process the TRAFFIC.
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
> >>  > >> > As per my opinion the ASP ACTIVE is triggered after the
> reception of
> >>  > ASP
> >>  > >> UP
> >>  > >> > ACK only but the trigger point may not be immediate. The trigger
> point
> >>  > >> can
> >>  > >> > be an indication from high availability framework; it could be
> some
> >>  > >> > application logic which once determines via local procedures
> that it
> >>  > is
> >>  > >> > ready to process the application traffic from network can
> initiate ASP
> >>  > >> > ACTIVE to SGP.
> >>  > >> >
> >>  > >> > Regards
> >>  > >> > Deepak
> >>  > >> >
> >>  > >> > ________________________________
> >>  > >> > From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org]
> On
> >>  > >> Behalf
> >>  > >> > Of Anand N Ilkal
> >>  > >> > Sent: Tuesday, January 04, 2011 1:22 PM
> >>  > >> > To: sigtran@ietf.org
> >>  > >> > Subject: [Sigtran] ASP active procedure
> >>  > >> >
> >>  > >> > Hello,
> >>  > >> >
> >>  > >> > i have doubt regarding the following section is RFC 4666  -
> >>  > >> > 4.3.4.3.  ASP Active Procedures
> >>  > >> >
> >>  > >> >    Anytime after the ASP has received an ASP Up Ack message from
> the
> >>  > SGP
> >>  > >> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
> >>  > >> >    indicating that the ASP is ready to start processing
> traffic....
> >>  > >> >
> >>  > >> > 1. why ASP MAY chose not to send ASP active on receipt of ASP Up
> Ack?
> >>  > >> > 2. is receipt of ASP Up Ack message is treated as sufficient
> >>  > condition,
> >>  > >> > whereas there is a necessary condition which should be satisfied
> so as
> >>  > >> ASP
> >>  > >> > active message is sent? if so, what is that condition?
> >>  > >> >
> >>  > >> > --
> >>  > >> > with regards,
> >>  > >> > Anand kumar Ilkal
> >>  > >> >
> >>  > >> > ________________________________
> >>  > >> > "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage
> arising
> >>  > >> from
> >>  > >> > the use of the information transmitted by this email including
> damage
> >>  > >> from
> >>  > >> > virus."
> >>  > >> >
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >>
> >>  > >> --
> >>  > >> with regards,
> >>  > >> Anand kumar Ilkal
> >>  > >>
> >>  > >> ------------------------------
> >>  > >> "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage
> arising
> >>  > from
> >>  > >> the use of the information transmitted by this email including
> damage
> >>  > from
> >>  > >> virus."
> >>  > >>
> >>  > >
> >>  > >
> >>  > >
> >>  > > --
> >>  > > with regards,
> >>  > > Anand kumar Ilkal
> >>  > >
> >>  >
> >>
> >>
> >>
> >>  --
> >>  with regards,
> >>  Anand kumar Ilkal
> >>
>



-- 
with regards,
Anand kumar Ilkal

--0023547c9015bbad770499128870
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Chris,<div><br></div><div>That certainly help -</div><div>Please find=
 my comments inline.<br><br><div class=3D"gmail_quote">On 5 January 2011 08=
:37, Chris Benson <span dir=3D"ltr">&lt;<a href=3D"mailto:cbenson@adax.com"=
>cbenson@adax.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Anand,<br>
<br>
I believe that the aspect of RFC 4666 that provides the<br>
answer to your question is found in Section 1.6.3. ...<br>
<br>
M-ASP_ACTIVE request<br>
Direction: =A0LM -&gt; M3UA<br>
Purpose: LM requests that ASP send an ASP Active message to its peer.<br>
<br>
An ASP Active message is sent both when the local M3UA is<br>
in the appropriate state *AND* when &quot;Layer Management&quot;<br>
makes this request. =A0Therefore, Section 4.3.4.3 only<br>
suggests that an ASP Active message MAY be sent. =A0There&#39;s<br>
no intention that this messgae always be sent immediately<br>
and automatically/unilaterally by M3UA itself.<br></blockquote><div>Agreed,=
 then is it safe for me to decide to send ASP Active if M3UA layer is ready=
 to receive traffic and =A0it has received ASP Up Ack?</div><div>then how a=
bout the scenario where n+k ASP&#39;s are configured in an AS, there are al=
ready n ASP&#39;s active. n+1th ASP has received ASP Up Ack. Since M3UA lay=
er is ready to receive traffic, can this ASP also send ASP Active ? (althou=
gh it can send since there is no problem if there are n+1 ASP&#39;s active =
in that perticular AS, just it could happen that n+1th ASP may be part of o=
ther AS&#39;s too, hence i do not want to load it further unless it is requ=
ired)</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<br>
You could choose to implement a &quot;Layer Management&quot; entity<br>
that does automatically issue a M-ASP_ACTIVE request<br>
just as soon as it receives an M-ASP UP confirm from<br>
the local M3UA ASP, but the RFC does not require that,<br>
in part because this &quot;Layer Management&quot; is not part of<br>
M3UA itself. =A0The &quot;Layer Management&quot; entity could even<br>
be a bureaucrat or trained monkey. =A0An extreme analogy,<br>
but the point is that LM decides to move an ASP to<br>
Active state, although the M3UA&#39;s ASP state enforces<br>
required conditions as described in Section 4.3.1. etc.<br></blockquote><di=
v>=A0</div><div>Yes, RFC does not cover Layer Manager. But to cover n+k mod=
el, traffic mode support, RFC recommends either internal logic in M3UA laye=
r or use of NOTIFY message to arrive at conclusive decision whether to send=
 ASP Active or not. Hence this internal logic or NOTIFY procedure are the n=
ecessary condition to ultimately decide whether to send ASP Active from a=
=A0particular=A0ASP or not.</div>
<div><br></div><div>Although NOTIFY messages carry only advisory importance=
, but their procedures are non-optional. it is at implementor=A0discretion=
=A0whether to make use of those or not.</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;=
">

<br>
This is the model of RFC 4666 rather than one in which<br>
states always progress automatically towards data transfer.<br>
<br>
I hope this helps, from Chris Benson.<br>
<br>
<br>
On Wed, 5 Jan 2011, Anand N Ilkal wrote:<br>
<br>
&gt;&gt; =A0Date: Wed, 5 Jan 2011 07:45:42 +0530<br>
&gt;&gt; =A0From: Anand N Ilkal &lt;<a href=3D"mailto:anandnilkal@gmail.com=
">anandnilkal@gmail.com</a>&gt;<br>
&gt;&gt; =A0To: arif khan &lt;<a href=3D"mailto:arif15jan@gmail.com">arif15=
jan@gmail.com</a>&gt;<br>
&gt;&gt; =A0Cc: &quot;<a href=3D"mailto:sigtran@ietf.org">sigtran@ietf.org<=
/a>&quot; &lt;<a href=3D"mailto:sigtran@ietf.org">sigtran@ietf.org</a>&gt;<=
br>
<div><div></div><div class=3D"h5">&gt;&gt; =A0Subject: Re: [Sigtran] ASP ac=
tive procedure<br>
&gt;&gt;<br>
&gt;&gt; =A0Hello Arif, Deepak,<br>
&gt;&gt;<br>
&gt;&gt; =A0This is not a special scenario, which would require special han=
dling by<br>
&gt;&gt; =A0either M3UA layer or LM.<br>
&gt;&gt; =A0My argument is, this section could have very well been written =
as follows -<br>
&gt;&gt;<br>
&gt;&gt; =A04.3.4.3. =A0ASP Active Procedures<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 Anytime after the ASP has received an ASP Up Ack message f=
rom the SGP<br>
&gt;&gt; =A0 =A0 or IPSP, the ASP SHOULD(or MUST) send an ASP Active messag=
e to the SGP,<br>
&gt;&gt; =A0 =A0 indicating that the ASP is ready to start processing traff=
ic....<br>
&gt;&gt;<br>
&gt;&gt; =A0This would have covered all the scenarios related to readiness =
of the<br>
&gt;&gt; =A0traffic handling (and management blocking). *But text is not as=
 shown here*,<br>
&gt;&gt; =A0hence receipt of ASP Up Ack is just a sufficient condition wher=
e-as NOTIFY<br>
&gt;&gt; =A0serves the necessary condition to send ASP Active message.<br>
&gt;&gt;<br>
&gt;&gt; =A0I would like you to comment on this sufficient and necessary co=
nditions.<br>
&gt;&gt;<br>
&gt;&gt; =A0On 4 January 2011 23:07, arif khan &lt;<a href=3D"mailto:arif15=
jan@gmail.com">arif15jan@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; =A0&gt; Yes this is the implementation need to handle this kind of=
 situation.<br>
&gt;&gt; =A0&gt; Suppose if Peer is already in ASP ACT state or any other<b=
r>
&gt;&gt; =A0&gt; state(excluding, waiting for the ASP UP ACK) and receives =
such<br>
&gt;&gt; =A0&gt; messages then state machine of the ASP should perform the =
state change<br>
&gt;&gt; =A0&gt; and should come to the original state.<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; This could be done by the system management entity to hand=
le this kind<br>
&gt;&gt; =A0&gt; of situation.<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; On 1/4/11, Anand N Ilkal &lt;<a href=3D"mailto:anandnilkal=
@gmail.com">anandnilkal@gmail.com</a>&gt; wrote:<br>
&gt;&gt; =A0&gt; &gt; Hello Deepak, arif,<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt; Please find my comments below -<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt; According to RFC 4666, section -<br>
&gt;&gt; =A0&gt; &gt; 4.3.4.3. =A0ASP Active Procedures<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt; =A0 =A0Anytime after the ASP has received an ASP Up A=
ck message from the SGP<br>
&gt;&gt; =A0&gt; &gt; =A0 =A0or IPSP, the ASP MAY send an ASP Active messag=
e to the SGP,<br>
&gt;&gt; =A0&gt; &gt; =A0 =A0indicating that the ASP is ready to start proc=
essing traffic....<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt; what if i decide not to send ASP Active after receivi=
ng ASP Up Ack , when<br>
&gt;&gt; =A0&gt; &gt; can i decide again to send ASP Active?<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt; On 4 January 2011 16:31, Deepak Gunjal &lt;<a href=3D=
"mailto:deepak.gunjal@aricent.com">deepak.gunjal@aricent.com</a>&gt;<br>
&gt;&gt; =A0&gt; wrote:<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0Hi Anand,<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; Generally the application logic is treated separa=
tely from the transport<br>
&gt;&gt; =A0&gt; &gt;&gt; layer which is here M3UA layer. So it is not nece=
ssary that if the<br>
&gt;&gt; =A0&gt; &gt;&gt; transport<br>
&gt;&gt; =A0&gt; &gt;&gt; layer is ready at a node then its application lay=
er will also be in a<br>
&gt;&gt; =A0&gt; &gt;&gt; ready<br>
&gt;&gt; =A0&gt; &gt;&gt; state.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt; Agreed : in the entirety of the M3UA layer, it should=
 never depend on the<br>
&gt;&gt; =A0&gt; &gt; status of the upper layer. always upper layers use th=
e services of the<br>
&gt;&gt; =A0&gt; lower<br>
&gt;&gt; =A0&gt; &gt; layers. otherway is seldom used.<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; The M3UA ASP UP message signifies the availabilit=
y of transport function<br>
&gt;&gt; =A0&gt; &gt;&gt; at<br>
&gt;&gt; =A0&gt; &gt;&gt; ASP but not about the application layer processin=
g function on the same<br>
&gt;&gt; =A0&gt; &gt;&gt; ASP.<br>
&gt;&gt; =A0&gt; &gt;&gt; Also in similar fashion SGP sends ASP UP Ack to i=
ndicate its<br>
&gt;&gt; =A0&gt; availability<br>
&gt;&gt; =A0&gt; &gt;&gt; to<br>
&gt;&gt; =A0&gt; &gt;&gt; accept the protocol messages only.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt; Consider the hypothetical stack configuration, where =
only till M3UA layer<br>
&gt;&gt; =A0&gt; is<br>
&gt;&gt; =A0&gt; &gt; configured, does it mean, it can not send ASP Active =
Message? I do not<br>
&gt;&gt; =A0&gt; think<br>
&gt;&gt; =A0&gt; &gt; so.<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; By sending ASP ACTIVE an ASP indicates that now i=
t can generate and<br>
&gt;&gt; =A0&gt; &gt;&gt; process<br>
&gt;&gt; =A0&gt; &gt;&gt; the user layer traffic and by sending ASP ACTIVE =
Ack SGP also indicates<br>
&gt;&gt; =A0&gt; &gt;&gt; the<br>
&gt;&gt; =A0&gt; &gt;&gt; same.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt; if application layer is not available local M3UA laye=
r simply drops<br>
&gt;&gt; =A0&gt; &gt; message.<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; So there is a distinction as I interpret the RFC =
for having TWO<br>
&gt;&gt; =A0&gt; different<br>
&gt;&gt; =A0&gt; &gt;&gt; messages viz. ASP UP and ASP ACTIVE which I think=
 have been designed for<br>
&gt;&gt; =A0&gt; &gt;&gt; such aspects. Also note that the application subs=
equently can initiate<br>
&gt;&gt; =A0&gt; ASP<br>
&gt;&gt; =A0&gt; &gt;&gt; ACTIVE from another ASP. The interpretation is no=
w in the context of the<br>
&gt;&gt; =A0&gt; &gt;&gt; traffic mode. So in Override mode the ASP which h=
as generated the ASP AC<br>
&gt;&gt; =A0&gt; &gt;&gt; will take on the active role, in case of loadshar=
e it will be kind of<br>
&gt;&gt; =A0&gt; &gt;&gt; parallel processing and in broadcast all the ASPs=
 will process the same<br>
&gt;&gt; =A0&gt; &gt;&gt; traffic simultaneously.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; That means there is some control function which w=
ill decide when the<br>
&gt;&gt; =A0&gt; &gt;&gt; application is ready and traffic can be started. =
Now I may design my<br>
&gt;&gt; =A0&gt; &gt;&gt; system<br>
&gt;&gt; =A0&gt; &gt;&gt; which will first complete all the application lev=
el readiness functions<br>
&gt;&gt; =A0&gt; &gt;&gt; and<br>
&gt;&gt; =A0&gt; &gt;&gt; then will start with ASP UP. In that case it is p=
ossible that as soon as<br>
&gt;&gt; =A0&gt; I<br>
&gt;&gt; =A0&gt; &gt;&gt; receive and ASP UP ack I will send ASP ACT immedi=
ately.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt; that will be a good design. But i am not convinced th=
at the readiness of<br>
&gt;&gt; =A0&gt; the<br>
&gt;&gt; =A0&gt; &gt; application layer is the reason why sending of ASP Ac=
tive is marked as<br>
&gt;&gt; =A0&gt; MAY<br>
&gt;&gt; =A0&gt; &gt; in RFC4666. what if LM is the one who is triggering A=
SPSM and ASPTM<br>
&gt;&gt; =A0&gt; &gt; messages. in that case your design requires LM to com=
municate to both<br>
&gt;&gt; =A0&gt; M3UA<br>
&gt;&gt; =A0&gt; &gt; layer and upper layer. there are only following bound=
aries defined<br>
&gt;&gt; =A0&gt; between<br>
&gt;&gt; =A0&gt; &gt; M3UA and MTP3 User layers -<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt; =A0 =A0 =A0 MTP-TRANSFER request<br>
&gt;&gt; =A0&gt; &gt; =A0 =A0 =A0 MTP-TRANSFER indication<br>
&gt;&gt; =A0&gt; &gt; =A0 =A0 =A0 MTP-PAUSE indication<br>
&gt;&gt; =A0&gt; &gt; =A0 =A0 =A0 MTP-RESUME indication<br>
&gt;&gt; =A0&gt; &gt; =A0 =A0 =A0 MTP-STATUS indication<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; To answer your question if ASP AC can be triggere=
d from a particular ASP<br>
&gt;&gt; =A0&gt; I<br>
&gt;&gt; =A0&gt; &gt;&gt; would say yes when ASPs are running in high avail=
ability framework it is<br>
&gt;&gt; =A0&gt; &gt;&gt; the<br>
&gt;&gt; =A0&gt; &gt;&gt; framework which directs a particular ASP to assum=
e ACTIVE role and then<br>
&gt;&gt; =A0&gt; &gt;&gt; only<br>
&gt;&gt; =A0&gt; &gt;&gt; that specific ASP will initiate the ASP ACK messa=
ge to SGP. The<br>
&gt;&gt; =A0&gt; framework<br>
&gt;&gt; =A0&gt; &gt;&gt; may determine the active ASP based on multiple fa=
ctors like nodes<br>
&gt;&gt; =A0&gt; priority<br>
&gt;&gt; =A0&gt; &gt;&gt; in that framework, its previous restart history, =
the state of<br>
&gt;&gt; =A0&gt; application<br>
&gt;&gt; =A0&gt; &gt;&gt; functions etc.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; Regards<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; Deepak<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0------------------------------<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; *From:* Anand N Ilkal [mailto:<a href=3D"mailto:a=
nandnilkal@gmail.com">anandnilkal@gmail.com</a>]<br>
&gt;&gt; =A0&gt; &gt;&gt; *Sent:* Tuesday, January 04, 2011 3:49 PM<br>
&gt;&gt; =A0&gt; &gt;&gt; *To:* arif khan; Deepak Gunjal<br>
&gt;&gt; =A0&gt; &gt;&gt; *Cc:* <a href=3D"mailto:sigtran@ietf.org">sigtran=
@ietf.org</a><br>
&gt;&gt; =A0&gt; &gt;&gt; *Subject:* Re: [Sigtran] ASP active procedure<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; Hello Deepak,<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; I understand that there needs to be local check w=
hether stack is ready<br>
&gt;&gt; =A0&gt; to<br>
&gt;&gt; =A0&gt; &gt;&gt; receive traffic for that routing key.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; lets assume all those scenarios are satisfied. an=
d i am pretty sure that<br>
&gt;&gt; =A0&gt; &gt;&gt; when RFC says MAY, it has taken all these cases i=
nto account (for<br>
&gt;&gt; =A0&gt; example<br>
&gt;&gt; =A0&gt; &gt;&gt; you can read from NOTIFY procedures - for NOTIFY =
to be sent, lot of<br>
&gt;&gt; =A0&gt; &gt;&gt; conditions needs to be satisfied - like n number =
of ASP&#39;s being active.<br>
&gt;&gt; =A0&gt; &gt;&gt; Yet<br>
&gt;&gt; =A0&gt; &gt;&gt; RFC uses the words like MUST or SHOULD) .<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; If traffic modes are to be taken into account, wh=
at should act as<br>
&gt;&gt; =A0&gt; trigger<br>
&gt;&gt; =A0&gt; &gt;&gt; for sending ASP Active message from a perticular =
ASP?<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; Hence my opinion is ASP Up Ack is only a sufficie=
nt condition, where-as<br>
&gt;&gt; =A0&gt; &gt;&gt; NOTIFY from peer acts as necessary condition.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; can any comment on that?<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; On 4 January 2011 14:01, arif khan &lt;<a href=3D=
"mailto:arif15jan@gmail.com">arif15jan@gmail.com</a>&gt; wrote:<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; Implementation logic is ok in their own context .=
..........<br>
&gt;&gt; =A0&gt; &gt;&gt; But ASP can process the TRAFFIC message only afte=
r the ASP ACT ACK<br>
&gt;&gt; =A0&gt; &gt;&gt; received from the NW and local side ASP with the =
remote ASP change<br>
&gt;&gt; =A0&gt; &gt;&gt; their state and becomes ready to process the TRAF=
FIC.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; On 1/4/11, Deepak Gunjal &lt;<a href=3D"mailto:de=
epak.gunjal@aricent.com">deepak.gunjal@aricent.com</a>&gt; wrote:<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; As per my opinion the ASP ACTIVE is triggere=
d after the reception of<br>
&gt;&gt; =A0&gt; ASP<br>
&gt;&gt; =A0&gt; &gt;&gt; UP<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; ACK only but the trigger point may not be im=
mediate. The trigger point<br>
&gt;&gt; =A0&gt; &gt;&gt; can<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; be an indication from high availability fram=
ework; it could be some<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; application logic which once determines via =
local procedures that it<br>
&gt;&gt; =A0&gt; is<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; ready to process the application traffic fro=
m network can initiate ASP<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; ACTIVE to SGP.<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; Regards<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; Deepak<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; ________________________________<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; From: <a href=3D"mailto:sigtran-bounces@ietf=
.org">sigtran-bounces@ietf.org</a> [mailto:<a href=3D"mailto:sigtran-bounce=
s@ietf.org">sigtran-bounces@ietf.org</a>] On<br>
&gt;&gt; =A0&gt; &gt;&gt; Behalf<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; Of Anand N Ilkal<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; Sent: Tuesday, January 04, 2011 1:22 PM<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; To: <a href=3D"mailto:sigtran@ietf.org">sigt=
ran@ietf.org</a><br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; Subject: [Sigtran] ASP active procedure<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; Hello,<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; i have doubt regarding the following section=
 is RFC 4666 =A0-<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; 4.3.4.3. =A0ASP Active Procedures<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; =A0 =A0Anytime after the ASP has received an=
 ASP Up Ack message from the<br>
&gt;&gt; =A0&gt; SGP<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; =A0 =A0or IPSP, the ASP MAY send an ASP Acti=
ve message to the SGP,<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; =A0 =A0indicating that the ASP is ready to s=
tart processing traffic....<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; 1. why ASP MAY chose not to send ASP active =
on receipt of ASP Up Ack?<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; 2. is receipt of ASP Up Ack message is treat=
ed as sufficient<br>
&gt;&gt; =A0&gt; condition,<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; whereas there is a necessary condition which=
 should be satisfied so as<br>
&gt;&gt; =A0&gt; &gt;&gt; ASP<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; active message is sent? if so, what is that =
condition?<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; --<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; with regards,<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; Anand kumar Ilkal<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; ________________________________<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; &quot;DISCLAIMER: This message is proprietar=
y to Aricent and is intended<br>
&gt;&gt; =A0&gt; &gt;&gt; solely<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; for the use of the individual to whom it is =
addressed. It may contain<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; privileged or confidential information and s=
hould not be circulated or<br>
&gt;&gt; =A0&gt; &gt;&gt; used<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; for any purpose other than for what it is in=
tended. If you have<br>
&gt;&gt; =A0&gt; received<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; this message in error, please notify the ori=
ginator immediately. If<br>
&gt;&gt; =A0&gt; you<br>
&gt;&gt; =A0&gt; &gt;&gt; are<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; not the intended recipient, you are notified=
 that you are strictly<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; prohibited from using, copying, altering, or=
 disclosing the contents<br>
&gt;&gt; =A0&gt; of<br>
&gt;&gt; =A0&gt; &gt;&gt; this<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; message. Aricent accepts no responsibility f=
or loss or damage arising<br>
&gt;&gt; =A0&gt; &gt;&gt; from<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; the use of the information transmitted by th=
is email including damage<br>
&gt;&gt; =A0&gt; &gt;&gt; from<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt; virus.&quot;<br>
&gt;&gt; =A0&gt; &gt;&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; --<br>
&gt;&gt; =A0&gt; &gt;&gt; with regards,<br>
&gt;&gt; =A0&gt; &gt;&gt; Anand kumar Ilkal<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; ------------------------------<br>
&gt;&gt; =A0&gt; &gt;&gt; &quot;DISCLAIMER: This message is proprietary to =
Aricent and is intended<br>
&gt;&gt; =A0&gt; solely<br>
&gt;&gt; =A0&gt; &gt;&gt; for the use of the individual to whom it is addre=
ssed. It may contain<br>
&gt;&gt; =A0&gt; &gt;&gt; privileged or confidential information and should=
 not be circulated or<br>
&gt;&gt; =A0&gt; &gt;&gt; used<br>
&gt;&gt; =A0&gt; &gt;&gt; for any purpose other than for what it is intende=
d. If you have received<br>
&gt;&gt; =A0&gt; &gt;&gt; this message in error, please notify the originat=
or immediately. If you<br>
&gt;&gt; =A0&gt; &gt;&gt; are<br>
&gt;&gt; =A0&gt; &gt;&gt; not the intended recipient, you are notified that=
 you are strictly<br>
&gt;&gt; =A0&gt; &gt;&gt; prohibited from using, copying, altering, or disc=
losing the contents of<br>
&gt;&gt; =A0&gt; &gt;&gt; this<br>
&gt;&gt; =A0&gt; &gt;&gt; message. Aricent accepts no responsibility for lo=
ss or damage arising<br>
&gt;&gt; =A0&gt; from<br>
&gt;&gt; =A0&gt; &gt;&gt; the use of the information transmitted by this em=
ail including damage<br>
&gt;&gt; =A0&gt; from<br>
&gt;&gt; =A0&gt; &gt;&gt; virus.&quot;<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt; --<br>
&gt;&gt; =A0&gt; &gt; with regards,<br>
&gt;&gt; =A0&gt; &gt; Anand kumar Ilkal<br>
&gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; =A0--<br>
&gt;&gt; =A0with regards,<br>
&gt;&gt; =A0Anand kumar Ilkal<br>
&gt;&gt;<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>with regard=
s,<br>Anand kumar Ilkal<br>
</div>

--0023547c9015bbad770499128870--

From cbenson@adax.com  Tue Jan  4 21:47:42 2011
Return-Path: <cbenson@adax.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0603B3A6B17 for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 21:47:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.424
X-Spam-Level: 
X-Spam-Status: No, score=-1.424 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_62=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id udyGtS-MLBkN for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 21:47:40 -0800 (PST)
Received: from mail1.adax.com (mail1.adax.com [208.201.231.104]) by core3.amsl.com (Postfix) with ESMTP id B9C353A6A2C for <sigtran@ietf.org>; Tue,  4 Jan 2011 21:47:39 -0800 (PST)
Received: from adax (adax [12.0.0.88]) by mail1.adax.com (Postfix) with ESMTP id EFA65120B8C; Tue,  4 Jan 2011 21:49:46 -0800 (PST)
Received: by adax (Postfix, from userid 243) id 9C49B8EDD0; Tue,  4 Jan 2011 21:51:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by adax (Postfix) with ESMTP id 95FEF8EDCF; Tue,  4 Jan 2011 21:51:34 -0800 (PST)
Date: Tue, 4 Jan 2011 21:51:34 -0800 (PST)
From: Chris Benson <cbenson@adax.com>
X-X-Sender: cbenson@adax.adax
To: Anand N Ilkal <anandnilkal@gmail.com>
In-Reply-To: <AANLkTikk6_rOtZwbeTcENxHsx++fS=m7UvAS5LsFm6C8@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1101042128060.17141@adax.adax>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com> <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com> <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com> <Pine.LNX.4.64.1101041848300.15433@adax.adax> <AANLkTikk6_rOtZwbeTcENxHsx++fS=m7UvAS5LsFm6C8@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 05:47:42 -0000

Anand,

My comments to your questions are inline.
With thanks, from, Chris Benson.

On Wed, 5 Jan 2011, Anand N Ilkal wrote:

>>  Date: Wed, 5 Jan 2011 10:49:49 +0530
>>  From: Anand N Ilkal <anandnilkal@gmail.com>
>>  To: Chris Benson <cbenson@adax.com>
>>  Cc: arif khan <arif15jan@gmail.com>, "sigtran@ietf.org" <sigtran@ietf.org>
>>  Subject: Re: [Sigtran] ASP active procedure
>>  
>>  Hello Chris,
>>  
>>  That certainly help -
>>  Please find my comments inline.
>>  
>>  On 5 January 2011 08:37, Chris Benson <cbenson@adax.com> wrote:
>>  
>>  > Anand,
>>  >
>>  > I believe that the aspect of RFC 4666 that provides the
>>  > answer to your question is found in Section 1.6.3. ...
>>  >
>>  > M-ASP_ACTIVE request
>>  > Direction:  LM -> M3UA
>>  > Purpose: LM requests that ASP send an ASP Active message to its peer.
>>  >
>>  > An ASP Active message is sent both when the local M3UA is
>>  > in the appropriate state *AND* when "Layer Management"
>>  > makes this request.  Therefore, Section 4.3.4.3 only
>>  > suggests that an ASP Active message MAY be sent.  There's
>>  > no intention that this messgae always be sent immediately
>>  > and automatically/unilaterally by M3UA itself.
>>  >
>>  Agreed, then is it safe for me to decide to send ASP Active if M3UA layer is
>>  ready to receive traffic and  it has received ASP Up Ack?

Yes it is safe and usually (but not always) desirable.

>>  then how about the scenario where n+k ASP's are configured in an AS, there
>>  are already n ASP's active. n+1th ASP has received ASP Up Ack. Since M3UA
>>  layer is ready to receive traffic, can this ASP also send ASP Active ?
>>  (although it can send since there is no problem if there are n+1 ASP's
>>  active in that perticular AS, just it could happen that n+1th ASP may be
>>  part of other AS's too, hence i do not want to load it further unless it is
>>  required)

1.  Yes the n+1th ASP to receive ASP Up Ack is allowed to issue 
an ASP Active message.  It is not always desirable though, for 
example as you suggest, it may not have resources to do that 
yet.  There may be a locally-decided strategy to support at
most n ASPs in the active state.  If n = 1 and k > 0, it is
not usually a good idea to issue ASP Active from the 2nd ASP
if in Override Traffic Mode for example.  This decision is
left to a "Layer Manager" and the best M3UA implementation
would defer to a modifyable LM strategy.

2.  I am not sure what exactly you meant by another AS.
An ASP Up message is about the ASP and every AS in which
it resides.  An ASP Active message is only about one or
more AS contexts as specified in the message, and an ASP
can specify different traffic modes for receipt of traffic
within each AS (using different ASP Active messages from
the same ASP).  This complexity is governed by the local
prefernces and LM implementation and not by RFC 4666.
The LM implementor can offer a simple automatic LM or a
more complex set of tools to use at run-time (traffic
time).  The implementations of the LM and of its strategies
are not part of the M3UA internal implementation.

I consider M3UA as an automated implementation of RFC 4666,
and the two separate entities of LM and M3UA user interface
as a library of tools that make the concepts of RFC 4666
Section 1.6.3 available as needed.

>>  
>>  >
>>  > You could choose to implement a "Layer Management" entity
>>  > that does automatically issue a M-ASP_ACTIVE request
>>  > just as soon as it receives an M-ASP UP confirm from
>>  > the local M3UA ASP, but the RFC does not require that,
>>  > in part because this "Layer Management" is not part of
>>  > M3UA itself.  The "Layer Management" entity could even
>>  > be a bureaucrat or trained monkey.  An extreme analogy,
>>  > but the point is that LM decides to move an ASP to
>>  > Active state, although the M3UA's ASP state enforces
>>  > required conditions as described in Section 4.3.1. etc.
>>  >
>>  
>>  Yes, RFC does not cover Layer Manager. But to cover n+k model, traffic mode
>>  support, RFC recommends either internal logic in M3UA layer or use of NOTIFY
>>  message to arrive at conclusive decision whether to send ASP Active or not.
>>  Hence this internal logic or NOTIFY procedure are the necessary condition to
>>  ultimately decide whether to send ASP Active from a particular ASP or not.
>>  
>>  Although NOTIFY messages carry only advisory importance, but their
>>  procedures are non-optional. it is at implementor discretion whether to make
>>  use of those or not.
>>  
>>  >
>>  > This is the model of RFC 4666 rather than one in which
>>  > states always progress automatically towards data transfer.
>>  >
>>  > I hope this helps, from Chris Benson.
>>  >
>>  >
>>  > On Wed, 5 Jan 2011, Anand N Ilkal wrote:
>>  >
>>  > >>  Date: Wed, 5 Jan 2011 07:45:42 +0530
>>  > >>  From: Anand N Ilkal <anandnilkal@gmail.com>
>>  > >>  To: arif khan <arif15jan@gmail.com>
>>  > >>  Cc: "sigtran@ietf.org" <sigtran@ietf.org>
>>  > >>  Subject: Re: [Sigtran] ASP active procedure
>>  > >>
>>  > >>  Hello Arif, Deepak,
>>  > >>
>>  > >>  This is not a special scenario, which would require special handling by
>>  > >>  either M3UA layer or LM.
>>  > >>  My argument is, this section could have very well been written as
>>  > follows -
>>  > >>
>>  > >>  4.3.4.3.  ASP Active Procedures
>>  > >>
>>  > >>     Anytime after the ASP has received an ASP Up Ack message from the
>>  > SGP
>>  > >>     or IPSP, the ASP SHOULD(or MUST) send an ASP Active message to the
>>  > SGP,
>>  > >>     indicating that the ASP is ready to start processing traffic....
>>  > >>
>>  > >>  This would have covered all the scenarios related to readiness of the
>>  > >>  traffic handling (and management blocking). *But text is not as shown
>>  > here*,
>>  > >>  hence receipt of ASP Up Ack is just a sufficient condition where-as
>>  > NOTIFY
>>  > >>  serves the necessary condition to send ASP Active message.
>>  > >>
>>  > >>  I would like you to comment on this sufficient and necessary
>>  > conditions.
>>  > >>
>>  > >>  On 4 January 2011 23:07, arif khan <arif15jan@gmail.com> wrote:
>>  > >>
>>  > >>  > Yes this is the implementation need to handle this kind of situation.
>>  > >>  > Suppose if Peer is already in ASP ACT state or any other
>>  > >>  > state(excluding, waiting for the ASP UP ACK) and receives such
>>  > >>  > messages then state machine of the ASP should perform the state
>>  > change
>>  > >>  > and should come to the original state.
>>  > >>  >
>>  > >>  > This could be done by the system management entity to handle this
>>  > kind
>>  > >>  > of situation.
>>  > >>  >
>>  > >>  >
>>  > >>  >
>>  > >>  >
>>  > >>  > On 1/4/11, Anand N Ilkal <anandnilkal@gmail.com> wrote:
>>  > >>  > > Hello Deepak, arif,
>>  > >>  > >
>>  > >>  > > Please find my comments below -
>>  > >>  > >
>>  > >>  > > According to RFC 4666, section -
>>  > >>  > > 4.3.4.3.  ASP Active Procedures
>>  > >>  > >
>>  > >>  > >    Anytime after the ASP has received an ASP Up Ack message from
>>  > the SGP
>>  > >>  > >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>>  > >>  > >    indicating that the ASP is ready to start processing traffic....
>>  > >>  > >
>>  > >>  > > what if i decide not to send ASP Active after receiving ASP Up Ack
>>  > , when
>>  > >>  > > can i decide again to send ASP Active?
>>  > >>  > >
>>  > >>  > > On 4 January 2011 16:31, Deepak Gunjal <deepak.gunjal@aricent.com>
>>  > >>  > wrote:
>>  > >>  > >
>>  > >>  > >>  Hi Anand,
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> Generally the application logic is treated separately from the
>>  > transport
>>  > >>  > >> layer which is here M3UA layer. So it is not necessary that if the
>>  > >>  > >> transport
>>  > >>  > >> layer is ready at a node then its application layer will also be
>>  > in a
>>  > >>  > >> ready
>>  > >>  > >> state.
>>  > >>  > >>
>>  > >>  > > Agreed : in the entirety of the M3UA layer, it should never depend
>>  > on the
>>  > >>  > > status of the upper layer. always upper layers use the services of
>>  > the
>>  > >>  > lower
>>  > >>  > > layers. otherway is seldom used.
>>  > >>  > >
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> The M3UA ASP UP message signifies the availability of transport
>>  > function
>>  > >>  > >> at
>>  > >>  > >> ASP but not about the application layer processing function on the
>>  > same
>>  > >>  > >> ASP.
>>  > >>  > >> Also in similar fashion SGP sends ASP UP Ack to indicate its
>>  > >>  > availability
>>  > >>  > >> to
>>  > >>  > >> accept the protocol messages only.
>>  > >>  > >>
>>  > >>  > > Consider the hypothetical stack configuration, where only till M3UA
>>  > layer
>>  > >>  > is
>>  > >>  > > configured, does it mean, it can not send ASP Active Message? I do
>>  > not
>>  > >>  > think
>>  > >>  > > so.
>>  > >>  > >
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> By sending ASP ACTIVE an ASP indicates that now it can generate
>>  > and
>>  > >>  > >> process
>>  > >>  > >> the user layer traffic and by sending ASP ACTIVE Ack SGP also
>>  > indicates
>>  > >>  > >> the
>>  > >>  > >> same.
>>  > >>  > >>
>>  > >>  > > if application layer is not available local M3UA layer simply drops
>>  > >>  > > message.
>>  > >>  > >
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> So there is a distinction as I interpret the RFC for having TWO
>>  > >>  > different
>>  > >>  > >> messages viz. ASP UP and ASP ACTIVE which I think have been
>>  > designed for
>>  > >>  > >> such aspects. Also note that the application subsequently can
>>  > initiate
>>  > >>  > ASP
>>  > >>  > >> ACTIVE from another ASP. The interpretation is now in the context
>>  > of the
>>  > >>  > >> traffic mode. So in Override mode the ASP which has generated the
>>  > ASP AC
>>  > >>  > >> will take on the active role, in case of loadshare it will be kind
>>  > of
>>  > >>  > >> parallel processing and in broadcast all the ASPs will process the
>>  > same
>>  > >>  > >> traffic simultaneously.
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> That means there is some control function which will decide when
>>  > the
>>  > >>  > >> application is ready and traffic can be started. Now I may design
>>  > my
>>  > >>  > >> system
>>  > >>  > >> which will first complete all the application level readiness
>>  > functions
>>  > >>  > >> and
>>  > >>  > >> then will start with ASP UP. In that case it is possible that as
>>  > soon as
>>  > >>  > I
>>  > >>  > >> receive and ASP UP ack I will send ASP ACT immediately.
>>  > >>  > >>
>>  > >>  > > that will be a good design. But i am not convinced that the
>>  > readiness of
>>  > >>  > the
>>  > >>  > > application layer is the reason why sending of ASP Active is marked
>>  > as
>>  > >>  > MAY
>>  > >>  > > in RFC4666. what if LM is the one who is triggering ASPSM and ASPTM
>>  > >>  > > messages. in that case your design requires LM to communicate to
>>  > both
>>  > >>  > M3UA
>>  > >>  > > layer and upper layer. there are only following boundaries defined
>>  > >>  > between
>>  > >>  > > M3UA and MTP3 User layers -
>>  > >>  > >
>>  > >>  > >       MTP-TRANSFER request
>>  > >>  > >       MTP-TRANSFER indication
>>  > >>  > >       MTP-PAUSE indication
>>  > >>  > >       MTP-RESUME indication
>>  > >>  > >       MTP-STATUS indication
>>  > >>  > >
>>  > >>  > >
>>  > >>  > >>
>>  > >>  > >> To answer your question if ASP AC can be triggered from a
>>  > particular ASP
>>  > >>  > I
>>  > >>  > >> would say yes when ASPs are running in high availability framework
>>  > it is
>>  > >>  > >> the
>>  > >>  > >> framework which directs a particular ASP to assume ACTIVE role and
>>  > then
>>  > >>  > >> only
>>  > >>  > >> that specific ASP will initiate the ASP ACK message to SGP. The
>>  > >>  > framework
>>  > >>  > >> may determine the active ASP based on multiple factors like nodes
>>  > >>  > priority
>>  > >>  > >> in that framework, its previous restart history, the state of
>>  > >>  > application
>>  > >>  > >> functions etc.
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> Regards
>>  > >>  > >>
>>  > >>  > >> Deepak
>>  > >>  > >>  ------------------------------
>>  > >>  > >>
>>  > >>  > >> *From:* Anand N Ilkal [mailto:anandnilkal@gmail.com]
>>  > >>  > >> *Sent:* Tuesday, January 04, 2011 3:49 PM
>>  > >>  > >> *To:* arif khan; Deepak Gunjal
>>  > >>  > >> *Cc:* sigtran@ietf.org
>>  > >>  > >> *Subject:* Re: [Sigtran] ASP active procedure
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> Hello Deepak,
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> I understand that there needs to be local check whether stack is
>>  > ready
>>  > >>  > to
>>  > >>  > >> receive traffic for that routing key.
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> lets assume all those scenarios are satisfied. and i am pretty
>>  > sure that
>>  > >>  > >> when RFC says MAY, it has taken all these cases into account (for
>>  > >>  > example
>>  > >>  > >> you can read from NOTIFY procedures - for NOTIFY to be sent, lot
>>  > of
>>  > >>  > >> conditions needs to be satisfied - like n number of ASP's being
>>  > active.
>>  > >>  > >> Yet
>>  > >>  > >> RFC uses the words like MUST or SHOULD) .
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> If traffic modes are to be taken into account, what should act as
>>  > >>  > trigger
>>  > >>  > >> for sending ASP Active message from a perticular ASP?
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> Hence my opinion is ASP Up Ack is only a sufficient condition,
>>  > where-as
>>  > >>  > >> NOTIFY from peer acts as necessary condition.
>>  > >>  > >>
>>  > >>  > >> can any comment on that?
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> On 4 January 2011 14:01, arif khan <arif15jan@gmail.com> wrote:
>>  > >>  > >>
>>  > >>  > >> Implementation logic is ok in their own context ...........
>>  > >>  > >> But ASP can process the TRAFFIC message only after the ASP ACT ACK
>>  > >>  > >> received from the NW and local side ASP with the remote ASP change
>>  > >>  > >> their state and becomes ready to process the TRAFFIC.
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
>>  > >>  > >> > As per my opinion the ASP ACTIVE is triggered after the
>>  > reception of
>>  > >>  > ASP
>>  > >>  > >> UP
>>  > >>  > >> > ACK only but the trigger point may not be immediate. The trigger
>>  > point
>>  > >>  > >> can
>>  > >>  > >> > be an indication from high availability framework; it could be
>>  > some
>>  > >>  > >> > application logic which once determines via local procedures
>>  > that it
>>  > >>  > is
>>  > >>  > >> > ready to process the application traffic from network can
>>  > initiate ASP
>>  > >>  > >> > ACTIVE to SGP.
>>  > >>  > >> >
>>  > >>  > >> > Regards
>>  > >>  > >> > Deepak
>>  > >>  > >> >
>>  > >>  > >> > ________________________________
>>  > >>  > >> > From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org]
>>  > On
>>  > >>  > >> Behalf
>>  > >>  > >> > Of Anand N Ilkal
>>  > >>  > >> > Sent: Tuesday, January 04, 2011 1:22 PM
>>  > >>  > >> > To: sigtran@ietf.org
>>  > >>  > >> > Subject: [Sigtran] ASP active procedure
>>  > >>  > >> >
>>  > >>  > >> > Hello,
>>  > >>  > >> >
>>  > >>  > >> > i have doubt regarding the following section is RFC 4666  -
>>  > >>  > >> > 4.3.4.3.  ASP Active Procedures
>>  > >>  > >> >
>>  > >>  > >> >    Anytime after the ASP has received an ASP Up Ack message from
>>  > the
>>  > >>  > SGP
>>  > >>  > >> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>>  > >>  > >> >    indicating that the ASP is ready to start processing
>>  > traffic....
>>  > >>  > >> >
>>  > >>  > >> > 1. why ASP MAY chose not to send ASP active on receipt of ASP Up
>>  > Ack?
>>  > >>  > >> > 2. is receipt of ASP Up Ack message is treated as sufficient
>>  > >>  > condition,
>>  > >>  > >> > whereas there is a necessary condition which should be satisfied
>>  > so as
>>  > >>  > >> ASP
>>  > >>  > >> > active message is sent? if so, what is that condition?
>>  > >>  > >> >
>>  > >>  > >> > --
>>  > >>  > >> > with regards,
>>  > >>  > >> > Anand kumar Ilkal
>>  > >>  > >> >
>>  > >>  > >> > ________________________________
>>  > >>  > >> > "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage
>>  > arising
>>  > >>  > >> from
>>  > >>  > >> > the use of the information transmitted by this email including
>>  > damage
>>  > >>  > >> from
>>  > >>  > >> > virus."
>>  > >>  > >> >
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >>
>>  > >>  > >> --
>>  > >>  > >> with regards,
>>  > >>  > >> Anand kumar Ilkal
>>  > >>  > >>
>>  > >>  > >> ------------------------------
>>  > >>  > >> "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage
>>  > arising
>>  > >>  > from
>>  > >>  > >> the use of the information transmitted by this email including
>>  > damage
>>  > >>  > from
>>  > >>  > >> virus."
>>  > >>  > >>
>>  > >>  > >
>>  > >>  > >
>>  > >>  > >
>>  > >>  > > --
>>  > >>  > > with regards,
>>  > >>  > > Anand kumar Ilkal
>>  > >>  > >
>>  > >>  >
>>  > >>
>>  > >>
>>  > >>
>>  > >>  --
>>  > >>  with regards,
>>  > >>  Anand kumar Ilkal
>>  > >>
>>  >
>>  
>>  
>>  
>>  -- 
>>  with regards,
>>  Anand kumar Ilkal
>>  

From bidulock@openss7.org  Tue Jan  4 23:04:04 2011
Return-Path: <bidulock@openss7.org>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AC563A6B45 for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 23:04:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HkuKzn1XkD9Y for <sigtran@core3.amsl.com>; Tue,  4 Jan 2011 23:04:00 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id 844083A6C5A for <sigtran@ietf.org>; Tue,  4 Jan 2011 23:03:57 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0575xqI022366; Wed, 5 Jan 2011 00:05:59 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0575wDC022529; Wed, 5 Jan 2011 00:05:58 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id p0575vso022528; Wed, 5 Jan 2011 00:05:57 -0700
Date: Wed, 5 Jan 2011 00:05:57 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Imran Raza Khan <imranrazakhan@gmail.com>
Message-ID: <20110105070557.GA21216@openss7.org>
Mail-Followup-To: Imran Raza Khan <imranrazakhan@gmail.com>, sigtran@ietf.org
References: <AANLkTi=c73mO-x6Tx5Yfrut7pzE5_o3HUcqemx2C8Koo@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AANLkTi=c73mO-x6Tx5Yfrut7pzE5_o3HUcqemx2C8Koo@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] TCAP User Adaptation Layer
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 07:04:05 -0000

Imran,

Imran Raza Khan wrote:                 (Mon, 03 Jan 2011 14:31:26)
>    Hi,
> 
>    I want to inquire about the TCAP user Adaptation Layer
>    draft. Available on
>    link [1]http://tools.ietf.org/html/draft-bidulock-sigtran-tua-05 .
> 
>    I have couple of question regarding that
> 
>      * Why its status is expired?

All internet-drafts expire in six months from their initial publication.

>      * Is it still implementable?

Knock yourself out: I implemented it.

>      * Any further roadmap of TUA?

No, ...

>      * Will it be part of SIGTRAN or not?

SIGTRAN is a defunct working group with no further charter.

--brian

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

From anandnilkal@gmail.com  Wed Jan  5 00:38:34 2011
Return-Path: <anandnilkal@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DFD03A6B83 for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 00:38:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_62=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03rN1yJIi4Nd for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 00:38:32 -0800 (PST)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id 65DB13A6B5F for <sigtran@ietf.org>; Wed,  5 Jan 2011 00:38:32 -0800 (PST)
Received: by yie19 with SMTP id 19so4434991yie.31 for <sigtran@ietf.org>; Wed, 05 Jan 2011 00:40:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=eS8LTO0Ov96JWSLDGnjz4waxUgE+BrfMolVsZ8DqiXE=; b=ws9CIIXPKScNy2L2FmTN5mQXQAOxGpKmAaPMRztgQyy0wDJaQXWgIiCWn3l3Vp/Ky6 nZfbVSQvmhZ0+vUtLLtPqq9TwnAL6DnQLgi6wjRw8Jcbf9ya3+q7M4iwjGl/O8D6DjQf EWt3OCuf5a6bgHwmH9ejhJBjkm+8J8fg0ys5Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=n8hdiJKbO0R325JnjsaaiCdgWiVR32jIx2k19OzmbFFsAYmpAXAcv6vM/7bfEi75Ml Ho57K8u8s7jzvt03sEG1usIe9RuPs9G6dxVlQ7kxVBaTDtdWvhgdejh6hQ8rb7B2Mvbr FnR6kWVeLsLM+GkoQaqO64vhUO1Tq+LZhWd2A=
MIME-Version: 1.0
Received: by 10.236.95.17 with SMTP id o17mr14019155yhf.56.1294216839202; Wed, 05 Jan 2011 00:40:39 -0800 (PST)
Received: by 10.236.108.145 with HTTP; Wed, 5 Jan 2011 00:40:39 -0800 (PST)
In-Reply-To: <AANLkTikdWN4Xv+ZXH3razSSjA0ZGD-_tZ_k8p5TDGzO+@mail.gmail.com>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com> <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com> <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com> <Pine.LNX.4.64.1101041848300.15433@adax.adax> <AANLkTikk6_rOtZwbeTcENxHsx++fS=m7UvAS5LsFm6C8@mail.gmail.com> <Pine.LNX.4.64.1101042128060.17141@adax.adax> <AANLkTikdWN4Xv+ZXH3razSSjA0ZGD-_tZ_k8p5TDGzO+@mail.gmail.com>
Date: Wed, 5 Jan 2011 14:10:39 +0530
Message-ID: <AANLkTi=ovH4SzJ1O1piiksQbT6Zgr+5x6gkXNRX6K_GZ@mail.gmail.com>
From: Anand N Ilkal <anandnilkal@gmail.com>
To: Chris Benson <cbenson@adax.com>, Deepak Gunjal <deepak.gunjal@aricent.com>
Content-Type: multipart/alternative; boundary=0023544fb8dcf6873e04991556c4
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 08:38:34 -0000

--0023544fb8dcf6873e04991556c4
Content-Type: text/plain; charset=ISO-8859-1

Hello Chris, deepak, arif,

here's the summary what i understood -

1. receive ASP Up Ack.
2. check if the ASP is part of n+k model, and already n ASP's are active for
a particular RK. if so dont send the ASP Active.
3. check if the ASP is following a particular traffic mode.
Then take a decision to send ASP Active.
 I am just curious, all the examples in this RFC include NOTIFY message.
will NOTIFY message do not play any role in this decision making?

PS: i have cut short the mail due to message size restriction.

On 5 January 2011 12:23, Anand N Ilkal <anandnilkal@gmail.com> wrote:

> chris , deepak,
>
> please find my comments inline -
>
> will the following statement fairly sums up the behaviour?
> RFC recommends either internal logic in M3UA layer or use of NOTIFY message
> to arrive at conclusive decision whether to send ASP Active or not. Hence
> this internal logic or NOTIFY procedure are the necessary condition to
> ultimately decide whether to send ASP Active from a particular ASP or not.
>
> On 5 January 2011 11:21, Chris Benson <cbenson@adax.com> wrote:
>
>> Anand,
>>
>> My comments to your questions are inline.
>> With thanks, from, Chris Benson.
>>
>> On Wed, 5 Jan 2011, Anand N Ilkal wrote:
>>
>> >>  Date: Wed, 5 Jan 2011 10:49:49 +0530
>> >>  From: Anand N Ilkal <anandnilkal@gmail.com>
>> >>  To: Chris Benson <cbenson@adax.com>
>> >>  Cc: arif khan <arif15jan@gmail.com>, "sigtran@ietf.org" <
>> sigtran@ietf.org>
>> >>  Subject: Re: [Sigtran] ASP active procedure
>> >>
>> >>  Hello Chris,
>> >>
>> >>  That certainly help -
>> >>  Please find my comments inline.
>> >>
>> >>  On 5 January 2011 08:37, Chris Benson <cbenson@adax.com> wrote:
>> >>
>> >>  > Anand,
>> >>  >
>> >>  > I believe that the aspect of RFC 4666 that provides the
>> >>  > answer to your question is found in Section 1.6.3. ...
>> >>  >
>> >>  > M-ASP_ACTIVE request
>> >>  > Direction:  LM -> M3UA
>> >>  > Purpose: LM requests that ASP send an ASP Active message to its
>> peer.
>> >>  >
>> >>  > An ASP Active message is sent both when the local M3UA is
>> >>  > in the appropriate state *AND* when "Layer Management"
>> >>  > makes this request.  Therefore, Section 4.3.4.3 only
>> >>  > suggests that an ASP Active message MAY be sent.  There's
>> >>  > no intention that this messgae always be sent immediately
>> >>  > and automatically/unilaterally by M3UA itself.
>> >>  >
>> >>  Agreed, then is it safe for me to decide to send ASP Active if M3UA
>> layer is
>> >>  ready to receive traffic and  it has received ASP Up Ack?
>>
>> Yes it is safe and usually (but not always) desirable.
>>
> Yes. This is not the sole reason on which i can decide to send ASP Active.
>
>
>>
>> >>  then how about the scenario where n+k ASP's are configured in an AS,
>> there
>> >>  are already n ASP's active. n+1th ASP has received ASP Up Ack. Since
>> M3UA
>> >>  layer is ready to receive traffic, can this ASP also send ASP Active ?
>> >>  (although it can send since there is no problem if there are n+1 ASP's
>> >>  active in that perticular AS, just it could happen that n+1th ASP may
>> be
>> >>  part of other AS's too, hence i do not want to load it further unless
>> it is
>> >>  required)
>>
>> 1.  Yes the n+1th ASP to receive ASP Up Ack is allowed to issue
>> an ASP Active message.  It is not always desirable though, for
>> example as you suggest, it may not have resources to do that
>> yet.  There may be a locally-decided strategy to support at
>> most n ASPs in the active state.  If n = 1 and k > 0, it is
>> not usually a good idea to issue ASP Active from the 2nd ASP
>> if in Override Traffic Mode for example.  This decision is
>> left to a "Layer Manager" and the best M3UA implementation
>> would defer to a modifyable LM strategy.
>>
> How about using NOTIFY procedure to come to this conclusion?
>
>>
>> 2.  I am not sure what exactly you meant by another AS.
>> An ASP Up message is about the ASP and every AS in which
>> it resides.  An ASP Active message is only about one or
>> more AS contexts as specified in the message, and an ASP
>> can specify different traffic modes for receipt of traffic
>> within each AS (using different ASP Active messages from
>> the same ASP).  This complexity is governed by the local
>> prefernces and LM implementation and not by RFC 4666.
>> The LM implementor can offer a simple automatic LM or a
>> more complex set of tools to use at run-time (traffic
>> time).  The implementations of the LM and of its strategies
>> are not part of the M3UA internal implementation.
>>
>> I consider M3UA as an automated implementation of RFC 4666,
>> and the two separate entities of LM and M3UA user interface
>> as a library of tools that make the concepts of RFC 4666
>> Section 1.6.3 available as needed.
>>
>> >>
>> >>  >
>> >>  > You could choose to implement a "Layer Management" entity
>> >>  > that does automatically issue a M-ASP_ACTIVE request
>> >>  > just as soon as it receives an M-ASP UP confirm from
>> >>  > the local M3UA ASP, but the RFC does not require that,
>> >>  > in part because this "Layer Management" is not part of
>> >>  > M3UA itself.  The "Layer Management" entity could even
>> >>  > be a bureaucrat or trained monkey.  An extreme analogy,
>> >>  > but the point is that LM decides to move an ASP to
>> >>  > Active state, although the M3UA's ASP state enforces
>> >>  > required conditions as described in Section 4.3.1. etc.
>> >>  >
>> >>
>> >>  Yes, RFC does not cover Layer Manager. But to cover n+k model, traffic
>> mode
>> >>  support, RFC recommends either internal logic in M3UA layer or use of
>> NOTIFY
>> >>  message to arrive at conclusive decision whether to send ASP Active or
>> not.
>> >>  Hence this internal logic or NOTIFY procedure are the necessary
>> condition to
>> >>  ultimately decide whether to send ASP Active from a particular ASP or
>> not.
>> >>
>> >>  Although NOTIFY messages carry only advisory importance, but their
>> >>  procedures are non-optional. it is at implementor discretion whether
>> to make
>> >>  use of those or not.
>> >>
>> >>  >
>> >>  > This is the model of RFC 4666 rather than one in which
>> >>  > states always progress automatically towards data transfer.
>> >>  >
>> >>  > I hope this helps, from Chris Benson.
>> >>  >
>> >>  >
>> >>  > On Wed, 5 Jan 2011, Anand N Ilkal wrote:
>> >>  >
>> >>  > >>  Date: Wed, 5 Jan 2011 07:45:42 +0530
>> >>  > >>  From: Anand N Ilkal <anandnilkal@gmail.com>
>> >>  > >>  To: arif khan <arif15jan@gmail.com>
>> >>  > >>  Cc: "sigtran@ietf.org" <sigtran@ietf.org>
>> >>  > >>  Subject: Re: [Sigtran] ASP active procedure
>> >>  > >>
>> >>  > >>  Hello Arif, Deepak,
>> >>  > >>
>> >>  > >>  This is not a special scenario, which would require special
>> handling by
>> >>  > >>  either M3UA layer or LM.
>> >>  > >>  My argument is, this section could have very well been written
>> as
>> >>  > follows -
>> >>  > >>
>> >>  > >>  4.3.4.3.  ASP Active Procedures
>> >>  > >>
>> >>  > >>     Anytime after the ASP has received an ASP Up Ack message from
>> the
>> >>  > SGP
>> >>  > >>     or IPSP, the ASP SHOULD(or MUST) send an ASP Active message
>> to the
>> >>  > SGP,
>> >>  > >>     indicating that the ASP is ready to start processing
>> traffic....
>> >>  > >>
>> >>  > >>  This would have covered all the scenarios related to readiness
>> of the
>> >>  > >>  traffic handling (and management blocking). *But text is not as
>> shown
>> >>  > here*,
>> >>  > >>  hence receipt of ASP Up Ack is just a sufficient condition
>> where-as
>> >>  > NOTIFY
>> >>  > >>  serves the necessary condition to send ASP Active message.
>> >>  > >>
>> >>  > >>  I would like you to comment on this sufficient and necessary
>> >>  > conditions.
>> >>  > >>
>> >>  > >>  On 4 January 2011 23:07, arif khan <arif15jan@gmail.com> wrote:
>> >>  > >>
>> >>  > >>  > Yes this is the implementation need to handle this kind of
>> situation.
>> >>  > >>  > Suppose if Peer is already in ASP ACT state or any other
>> >>  > >>  > state(excluding, waiting for the ASP UP ACK) and receives such
>> >>  > >>  > messages then state machine of the ASP should perform the
>> state
>> >>  > change
>> >>  > >>  > and should come to the original state.
>> >>  > >>  >
>> >>  > >>  > This could be done by the system management entity to handle
>> this
>> >>  > kind
>> >>  > >>  > of situation.
>> >>  > >>  >
>> >>  > >>  >
>> >>  > >>  >
>> >>  > >>  >
>> >>  > >>  > On 1/4/11, Anand N Ilkal <anandnilkal@gmail.com> wrote:
>> >>  > >>  > > Hello Deepak, arif,
>> >>  > >>  > >
>> >>  > >>  > > Please find my comments below -
>> >>  > >>  > >
>> >>  > >>  > > According to RFC 4666, section -
>> >>  > >>  > > 4.3.4.3.  ASP Active Procedures
>> >>  > >>  > >
>> >>  > >>  > >    Anytime after the ASP has received an ASP Up Ack message
>> from
>> >>  > the SGP
>> >>  > >>  > >    or IPSP, the ASP MAY send an ASP Active message to the
>> SGP,
>> >>  > >>  > >    indicating that the ASP is ready to start processing
>> traffic....
>> >>  > >>  > >
>> >>  > >>  > > what if i decide not to send ASP Active after receiving ASP
>> Up Ack
>> >>  > , when
>> >>  > >>  > > can i decide again to send ASP Active?
>> >>  > >>  > >
>>
>

-- 
with regards,
Anand kumar Ilkal

--0023544fb8dcf6873e04991556c4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Chris, deepak, arif,<div><br></div><div>here&#39;s the summary what i=
 understood -</div><div><div><br></div><div>1.<span class=3D"Apple-tab-span=
" style=3D"white-space:pre">	</span>receive ASP Up Ack.</div><div>2.<span c=
lass=3D"Apple-tab-span" style=3D"white-space:pre">	</span>check if the ASP =
is part of n+k model, and already n ASP&#39;s are active for a particular R=
K. if so dont send the ASP Active.</div>
<div>3.<span class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>che=
ck if the ASP is following a particular traffic mode.</div><div><span class=
=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Then take a decision =
to send ASP Active.</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	</span></div=
><div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>I am=
 just curious, all the examples in this RFC include NOTIFY message. will NO=
TIFY message do not play any role in this decision making?</div>
<div><br></div>PS: i have cut short the mail due to message size restrictio=
n.</div><div><br><div class=3D"gmail_quote">On 5 January 2011 12:23, Anand =
N Ilkal <span dir=3D"ltr">&lt;<a href=3D"mailto:anandnilkal@gmail.com">anan=
dnilkal@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">chris , deepak,<div><br></div><div>please f=
ind my comments inline -</div><div><br></div><div>will the following statem=
ent fairly sums up the behaviour?</div>
<div><div class=3D"im"><span style=3D"border-collapse:collapse;font-family:=
arial, sans-serif;font-size:13px">RFC recommends either internal logic in M=
3UA layer or use of NOTIFY message to arrive at conclusive decision whether=
 to send ASP Active or not. Hence this internal logic or NOTIFY procedure a=
re the necessary condition to ultimately decide whether to send ASP Active =
from a=A0particular=A0ASP or not.</span><br>

<br></div><div class=3D"gmail_quote"><div><div></div><div class=3D"h5">On 5=
 January 2011 11:21, Chris Benson <span dir=3D"ltr">&lt;<a href=3D"mailto:c=
benson@adax.com" target=3D"_blank">cbenson@adax.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">

Anand,<br>
<br>
My comments to your questions are inline.<br>
With thanks, from, Chris Benson.<br>
<div><br>
On Wed, 5 Jan 2011, Anand N Ilkal wrote:<br>
<br>
</div>&gt;&gt; =A0Date: Wed, 5 Jan 2011 10:49:49 +0530<br>
<div>&gt;&gt; =A0From: Anand N Ilkal &lt;<a href=3D"mailto:anandnilkal@gmai=
l.com" target=3D"_blank">anandnilkal@gmail.com</a>&gt;<br>
</div>&gt;&gt; =A0To: Chris Benson &lt;<a href=3D"mailto:cbenson@adax.com" =
target=3D"_blank">cbenson@adax.com</a>&gt;<br>
&gt;&gt; =A0Cc: arif khan &lt;<a href=3D"mailto:arif15jan@gmail.com" target=
=3D"_blank">arif15jan@gmail.com</a>&gt;, &quot;<a href=3D"mailto:sigtran@ie=
tf.org" target=3D"_blank">sigtran@ietf.org</a>&quot; &lt;<a href=3D"mailto:=
sigtran@ietf.org" target=3D"_blank">sigtran@ietf.org</a>&gt;<br>


<div>&gt;&gt; =A0Subject: Re: [Sigtran] ASP active procedure<br>
&gt;&gt;<br>
</div><div>&gt;&gt; =A0Hello Chris,<br>
&gt;&gt;<br>
&gt;&gt; =A0That certainly help -<br>
&gt;&gt; =A0Please find my comments inline.<br>
&gt;&gt;<br>
&gt;&gt; =A0On 5 January 2011 08:37, Chris Benson &lt;<a href=3D"mailto:cbe=
nson@adax.com" target=3D"_blank">cbenson@adax.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; =A0&gt; Anand,<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; I believe that the aspect of RFC 4666 that provides the<br=
>
&gt;&gt; =A0&gt; answer to your question is found in Section 1.6.3. ...<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; M-ASP_ACTIVE request<br>
&gt;&gt; =A0&gt; Direction: =A0LM -&gt; M3UA<br>
&gt;&gt; =A0&gt; Purpose: LM requests that ASP send an ASP Active message t=
o its peer.<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; An ASP Active message is sent both when the local M3UA is<=
br>
&gt;&gt; =A0&gt; in the appropriate state *AND* when &quot;Layer Management=
&quot;<br>
&gt;&gt; =A0&gt; makes this request. =A0Therefore, Section 4.3.4.3 only<br>
&gt;&gt; =A0&gt; suggests that an ASP Active message MAY be sent. =A0There&=
#39;s<br>
&gt;&gt; =A0&gt; no intention that this messgae always be sent immediately<=
br>
&gt;&gt; =A0&gt; and automatically/unilaterally by M3UA itself.<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0Agreed, then is it safe for me to decide to send ASP Active if =
M3UA layer is<br>
&gt;&gt; =A0ready to receive traffic and =A0it has received ASP Up Ack?<br>
<br>
</div>Yes it is safe and usually (but not always) desirable.<br></blockquot=
e></div></div><div>Yes. This is not the sole reason on which i can decide t=
o send ASP Active. =A0</div><div class=3D"im"><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">


<div><br>
&gt;&gt; =A0then how about the scenario where n+k ASP&#39;s are configured =
in an AS, there<br>
&gt;&gt; =A0are already n ASP&#39;s active. n+1th ASP has received ASP Up A=
ck. Since M3UA<br>
&gt;&gt; =A0layer is ready to receive traffic, can this ASP also send ASP A=
ctive ?<br>
&gt;&gt; =A0(although it can send since there is no problem if there are n+=
1 ASP&#39;s<br>
&gt;&gt; =A0active in that perticular AS, just it could happen that n+1th A=
SP may be<br>
&gt;&gt; =A0part of other AS&#39;s too, hence i do not want to load it furt=
her unless it is<br>
&gt;&gt; =A0required)<br>
<br>
</div>1. =A0Yes the n+1th ASP to receive ASP Up Ack is allowed to issue<br>
an ASP Active message. =A0It is not always desirable though, for<br>
example as you suggest, it may not have resources to do that<br>
yet. =A0There may be a locally-decided strategy to support at<br>
most n ASPs in the active state. =A0If n =3D 1 and k &gt; 0, it is<br>
not usually a good idea to issue ASP Active from the 2nd ASP<br>
if in Override Traffic Mode for example. =A0This decision is<br>
left to a &quot;Layer Manager&quot; and the best M3UA implementation<br>
would defer to a modifyable LM strategy.<br></blockquote></div><div>How abo=
ut using NOTIFY procedure to come to this conclusion?=A0</div><div><div></d=
iv><div class=3D"h5"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<br>
2. =A0I am not sure what exactly you meant by another AS.<br>
An ASP Up message is about the ASP and every AS in which<br>
it resides. =A0An ASP Active message is only about one or<br>
more AS contexts as specified in the message, and an ASP<br>
can specify different traffic modes for receipt of traffic<br>
within each AS (using different ASP Active messages from<br>
the same ASP). =A0This complexity is governed by the local<br>
prefernces and LM implementation and not by RFC 4666.<br>
The LM implementor can offer a simple automatic LM or a<br>
more complex set of tools to use at run-time (traffic<br>
time). =A0The implementations of the LM and of its strategies<br>
are not part of the M3UA internal implementation.<br>
<br>
I consider M3UA as an automated implementation of RFC 4666,<br>
and the two separate entities of LM and M3UA user interface<br>
as a library of tools that make the concepts of RFC 4666<br>
Section 1.6.3 available as needed.<br>
<div><div></div><div><br>
&gt;&gt;<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; You could choose to implement a &quot;Layer Management&quo=
t; entity<br>
&gt;&gt; =A0&gt; that does automatically issue a M-ASP_ACTIVE request<br>
&gt;&gt; =A0&gt; just as soon as it receives an M-ASP UP confirm from<br>
&gt;&gt; =A0&gt; the local M3UA ASP, but the RFC does not require that,<br>
&gt;&gt; =A0&gt; in part because this &quot;Layer Management&quot; is not p=
art of<br>
&gt;&gt; =A0&gt; M3UA itself. =A0The &quot;Layer Management&quot; entity co=
uld even<br>
&gt;&gt; =A0&gt; be a bureaucrat or trained monkey. =A0An extreme analogy,<=
br>
&gt;&gt; =A0&gt; but the point is that LM decides to move an ASP to<br>
&gt;&gt; =A0&gt; Active state, although the M3UA&#39;s ASP state enforces<b=
r>
&gt;&gt; =A0&gt; required conditions as described in Section 4.3.1. etc.<br=
>
&gt;&gt; =A0&gt;<br>
&gt;&gt;<br>
&gt;&gt; =A0Yes, RFC does not cover Layer Manager. But to cover n+k model, =
traffic mode<br>
&gt;&gt; =A0support, RFC recommends either internal logic in M3UA layer or =
use of NOTIFY<br>
&gt;&gt; =A0message to arrive at conclusive decision whether to send ASP Ac=
tive or not.<br>
&gt;&gt; =A0Hence this internal logic or NOTIFY procedure are the necessary=
 condition to<br>
&gt;&gt; =A0ultimately decide whether to send ASP Active from a particular =
ASP or not.<br>
&gt;&gt;<br>
&gt;&gt; =A0Although NOTIFY messages carry only advisory importance, but th=
eir<br>
&gt;&gt; =A0procedures are non-optional. it is at implementor discretion wh=
ether to make<br>
&gt;&gt; =A0use of those or not.<br>
&gt;&gt;<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; This is the model of RFC 4666 rather than one in which<br>
&gt;&gt; =A0&gt; states always progress automatically towards data transfer=
.<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; I hope this helps, from Chris Benson.<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; On Wed, 5 Jan 2011, Anand N Ilkal wrote:<br>
&gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0Date: Wed, 5 Jan 2011 07:45:42 +0530<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0From: Anand N Ilkal &lt;<a href=3D"mailto:anan=
dnilkal@gmail.com" target=3D"_blank">anandnilkal@gmail.com</a>&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0To: arif khan &lt;<a href=3D"mailto:arif15jan@=
gmail.com" target=3D"_blank">arif15jan@gmail.com</a>&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0Cc: &quot;<a href=3D"mailto:sigtran@ietf.org" =
target=3D"_blank">sigtran@ietf.org</a>&quot; &lt;<a href=3D"mailto:sigtran@=
ietf.org" target=3D"_blank">sigtran@ietf.org</a>&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0Subject: Re: [Sigtran] ASP active procedure<br=
>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0Hello Arif, Deepak,<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0This is not a special scenario, which would re=
quire special handling by<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0either M3UA layer or LM.<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0My argument is, this section could have very w=
ell been written as<br>
&gt;&gt; =A0&gt; follows -<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A04.3.4.3. =A0ASP Active Procedures<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0 =A0 Anytime after the ASP has received an ASP=
 Up Ack message from the<br>
&gt;&gt; =A0&gt; SGP<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0 =A0 or IPSP, the ASP SHOULD(or MUST) send an =
ASP Active message to the<br>
&gt;&gt; =A0&gt; SGP,<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0 =A0 indicating that the ASP is ready to start=
 processing traffic....<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0This would have covered all the scenarios rela=
ted to readiness of the<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0traffic handling (and management blocking). *B=
ut text is not as shown<br>
&gt;&gt; =A0&gt; here*,<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0hence receipt of ASP Up Ack is just a sufficie=
nt condition where-as<br>
&gt;&gt; =A0&gt; NOTIFY<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0serves the necessary condition to send ASP Act=
ive message.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0I would like you to comment on this sufficient=
 and necessary<br>
&gt;&gt; =A0&gt; conditions.<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0On 4 January 2011 23:07, arif khan &lt;<a href=
=3D"mailto:arif15jan@gmail.com" target=3D"_blank">arif15jan@gmail.com</a>&g=
t; wrote:<br>
&gt;&gt; =A0&gt; &gt;&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; Yes this is the implementation need to ha=
ndle this kind of situation.<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; Suppose if Peer is already in ASP ACT sta=
te or any other<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; state(excluding, waiting for the ASP UP A=
CK) and receives such<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; messages then state machine of the ASP sh=
ould perform the state<br>
&gt;&gt; =A0&gt; change<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; and should come to the original state.<br=
>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; This could be done by the system manageme=
nt entity to handle this<br>
&gt;&gt; =A0&gt; kind<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; of situation.<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; On 1/4/11, Anand N Ilkal &lt;<a href=3D"m=
ailto:anandnilkal@gmail.com" target=3D"_blank">anandnilkal@gmail.com</a>&gt=
; wrote:<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt; Hello Deepak, arif,<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt; Please find my comments below -<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt; According to RFC 4666, section -<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt; 4.3.4.3. =A0ASP Active Procedures<br=
>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt; =A0 =A0Anytime after the ASP has rec=
eived an ASP Up Ack message from<br>
&gt;&gt; =A0&gt; the SGP<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt; =A0 =A0or IPSP, the ASP MAY send an =
ASP Active message to the SGP,<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt; =A0 =A0indicating that the ASP is re=
ady to start processing traffic....<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt;<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt; what if i decide not to send ASP Act=
ive after receiving ASP Up Ack<br>
&gt;&gt; =A0&gt; , when<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt; can i decide again to send ASP Activ=
e?<br>
&gt;&gt; =A0&gt; &gt;&gt; =A0&gt; &gt;<br></div></div></blockquote></div></=
div></div></div></blockquote></div><br clear=3D"all"><br>-- <br>with regard=
s,<br>Anand kumar Ilkal<br>
</div>

--0023544fb8dcf6873e04991556c4--

From arif15jan@gmail.com  Wed Jan  5 01:21:10 2011
Return-Path: <arif15jan@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7FCE3A6D17 for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 01:21:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level: 
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_62=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gTEch34IK7SH for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 01:21:09 -0800 (PST)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 2A9CD3A6CEC for <sigtran@ietf.org>; Wed,  5 Jan 2011 01:21:09 -0800 (PST)
Received: by qyj19 with SMTP id 19so16393333qyj.10 for <sigtran@ietf.org>; Wed, 05 Jan 2011 01:23:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=JfRqT/1v0FfjEFewf7puucNXdIdQ10KGyhg4PzxkaaU=; b=DC8dOiUQg0IErBo+15YypjT6/d+QbN9uR7dYZ9b2R8lLzMW9xm5UN/pddRa3QCEoko b3okTl4f2JamJCVYc0NcocOstlFtAMnaRxXRVkwT265AB+PfS42BAx+pFU0XHVghwBCX IRss+DY8Ez1ukwDSPNEa8G+siTPiZqvlWewKw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=q9/i8+02hQ5f0YT0TkYwuacURWC4Au9AqnY1tkq5rsbt3MLsODgQ1O3b2ef3St2LGe o32BENnv1XkJxIQ4efW0x96r7DSU7qTfKc2i94ha4okP/QdfmGTX4OB+4PEYtXwMGsuT hC1qpDpVbmvxX40yJ5HONltP7Rw0BOjjDfG6U=
MIME-Version: 1.0
Received: by 10.224.54.6 with SMTP id o6mr6611744qag.198.1294219395883; Wed, 05 Jan 2011 01:23:15 -0800 (PST)
Received: by 10.220.75.3 with HTTP; Wed, 5 Jan 2011 01:23:15 -0800 (PST)
In-Reply-To: <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com> <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com> <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com>
Date: Wed, 5 Jan 2011 14:53:15 +0530
Message-ID: <AANLkTin-FSm_hjmdpEQ=Sxf_NzTV7x0ikC17F1SJ+Hdd@mail.gmail.com>
From: arif khan <arif15jan@gmail.com>
To: Anand N Ilkal <anandnilkal@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 09:21:11 -0000

No It is wrong to keep it must...........

You may send one or multiple ASP ACT message depending on the
configuration of ASPs

Suppose if you have 2 asp and you want to send aspac for both after
receiving the ASP UP Ack msg from SGP.In this situation either wait
for the second asp ack to send the aspac for both the asp or one by
one.

So for this reason the MAY tag is given.




On 1/5/11, Anand N Ilkal <anandnilkal@gmail.com> wrote:
> Hello Arif, Deepak,
>
> This is not a special scenario, which would require special handling by
> either M3UA layer or LM.
> My argument is, this section could have very well been written as follows -
>
> 4.3.4.3.  ASP Active Procedures
>
>    Anytime after the ASP has received an ASP Up Ack message from the SGP
>    or IPSP, the ASP SHOULD(or MUST) send an ASP Active message to the SGP,
>    indicating that the ASP is ready to start processing traffic....
>
> This would have covered all the scenarios related to readiness of the
> traffic handling (and management blocking). *But text is not as shown here*,
> hence receipt of ASP Up Ack is just a sufficient condition where-as NOTIFY
> serves the necessary condition to send ASP Active message.
>
> I would like you to comment on this sufficient and necessary conditions.
>
> On 4 January 2011 23:07, arif khan <arif15jan@gmail.com> wrote:
>
>> Yes this is the implementation need to handle this kind of situation.
>> Suppose if Peer is already in ASP ACT state or any other
>> state(excluding, waiting for the ASP UP ACK) and receives such
>> messages then state machine of the ASP should perform the state change
>> and should come to the original state.
>>
>> This could be done by the system management entity to handle this kind
>> of situation.
>>
>>
>>
>>
>> On 1/4/11, Anand N Ilkal <anandnilkal@gmail.com> wrote:
>> > Hello Deepak, arif,
>> >
>> > Please find my comments below -
>> >
>> > According to RFC 4666, section -
>> > 4.3.4.3.  ASP Active Procedures
>> >
>> >    Anytime after the ASP has received an ASP Up Ack message from the SGP
>> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>> >    indicating that the ASP is ready to start processing traffic....
>> >
>> > what if i decide not to send ASP Active after receiving ASP Up Ack ,
>> > when
>> > can i decide again to send ASP Active?
>> >
>> > On 4 January 2011 16:31, Deepak Gunjal <deepak.gunjal@aricent.com>
>> wrote:
>> >
>> >>  Hi Anand,
>> >>
>> >>
>> >>
>> >> Generally the application logic is treated separately from the
>> >> transport
>> >> layer which is here M3UA layer. So it is not necessary that if the
>> >> transport
>> >> layer is ready at a node then its application layer will also be in a
>> >> ready
>> >> state.
>> >>
>> > Agreed : in the entirety of the M3UA layer, it should never depend on
>> > the
>> > status of the upper layer. always upper layers use the services of the
>> lower
>> > layers. otherway is seldom used.
>> >
>> >>
>> >>
>> >> The M3UA ASP UP message signifies the availability of transport
>> >> function
>> >> at
>> >> ASP but not about the application layer processing function on the same
>> >> ASP.
>> >> Also in similar fashion SGP sends ASP UP Ack to indicate its
>> availability
>> >> to
>> >> accept the protocol messages only.
>> >>
>> > Consider the hypothetical stack configuration, where only till M3UA
>> > layer
>> is
>> > configured, does it mean, it can not send ASP Active Message? I do not
>> think
>> > so.
>> >
>> >>
>> >>
>> >> By sending ASP ACTIVE an ASP indicates that now it can generate and
>> >> process
>> >> the user layer traffic and by sending ASP ACTIVE Ack SGP also indicates
>> >> the
>> >> same.
>> >>
>> > if application layer is not available local M3UA layer simply drops
>> > message.
>> >
>> >>
>> >>
>> >> So there is a distinction as I interpret the RFC for having TWO
>> different
>> >> messages viz. ASP UP and ASP ACTIVE which I think have been designed
>> >> for
>> >> such aspects. Also note that the application subsequently can initiate
>> ASP
>> >> ACTIVE from another ASP. The interpretation is now in the context of
>> >> the
>> >> traffic mode. So in Override mode the ASP which has generated the ASP
>> >> AC
>> >> will take on the active role, in case of loadshare it will be kind of
>> >> parallel processing and in broadcast all the ASPs will process the same
>> >> traffic simultaneously.
>> >>
>> >>
>> >>
>> >> That means there is some control function which will decide when the
>> >> application is ready and traffic can be started. Now I may design my
>> >> system
>> >> which will first complete all the application level readiness functions
>> >> and
>> >> then will start with ASP UP. In that case it is possible that as soon
>> >> as
>> I
>> >> receive and ASP UP ack I will send ASP ACT immediately.
>> >>
>> > that will be a good design. But i am not convinced that the readiness of
>> the
>> > application layer is the reason why sending of ASP Active is marked as
>> MAY
>> > in RFC4666. what if LM is the one who is triggering ASPSM and ASPTM
>> > messages. in that case your design requires LM to communicate to both
>> M3UA
>> > layer and upper layer. there are only following boundaries defined
>> between
>> > M3UA and MTP3 User layers -
>> >
>> >       MTP-TRANSFER request
>> >       MTP-TRANSFER indication
>> >       MTP-PAUSE indication
>> >       MTP-RESUME indication
>> >       MTP-STATUS indication
>> >
>> >
>> >>
>> >> To answer your question if ASP AC can be triggered from a particular
>> >> ASP
>> I
>> >> would say yes when ASPs are running in high availability framework it
>> >> is
>> >> the
>> >> framework which directs a particular ASP to assume ACTIVE role and then
>> >> only
>> >> that specific ASP will initiate the ASP ACK message to SGP. The
>> framework
>> >> may determine the active ASP based on multiple factors like nodes
>> priority
>> >> in that framework, its previous restart history, the state of
>> application
>> >> functions etc.
>> >>
>> >>
>> >>
>> >> Regards
>> >>
>> >> Deepak
>> >>  ------------------------------
>> >>
>> >> *From:* Anand N Ilkal [mailto:anandnilkal@gmail.com]
>> >> *Sent:* Tuesday, January 04, 2011 3:49 PM
>> >> *To:* arif khan; Deepak Gunjal
>> >> *Cc:* sigtran@ietf.org
>> >> *Subject:* Re: [Sigtran] ASP active procedure
>> >>
>> >>
>> >>
>> >> Hello Deepak,
>> >>
>> >>
>> >>
>> >> I understand that there needs to be local check whether stack is ready
>> to
>> >> receive traffic for that routing key.
>> >>
>> >>
>> >>
>> >> lets assume all those scenarios are satisfied. and i am pretty sure
>> >> that
>> >> when RFC says MAY, it has taken all these cases into account (for
>> example
>> >> you can read from NOTIFY procedures - for NOTIFY to be sent, lot of
>> >> conditions needs to be satisfied - like n number of ASP's being active.
>> >> Yet
>> >> RFC uses the words like MUST or SHOULD) .
>> >>
>> >>
>> >>
>> >> If traffic modes are to be taken into account, what should act as
>> trigger
>> >> for sending ASP Active message from a perticular ASP?
>> >>
>> >>
>> >>
>> >> Hence my opinion is ASP Up Ack is only a sufficient condition, where-as
>> >> NOTIFY from peer acts as necessary condition.
>> >>
>> >> can any comment on that?
>> >>
>> >>
>> >>
>> >> On 4 January 2011 14:01, arif khan <arif15jan@gmail.com> wrote:
>> >>
>> >> Implementation logic is ok in their own context ...........
>> >> But ASP can process the TRAFFIC message only after the ASP ACT ACK
>> >> received from the NW and local side ASP with the remote ASP change
>> >> their state and becomes ready to process the TRAFFIC.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On 1/4/11, Deepak Gunjal <deepak.gunjal@aricent.com> wrote:
>> >> > As per my opinion the ASP ACTIVE is triggered after the reception of
>> ASP
>> >> UP
>> >> > ACK only but the trigger point may not be immediate. The trigger
>> >> > point
>> >> can
>> >> > be an indication from high availability framework; it could be some
>> >> > application logic which once determines via local procedures that it
>> is
>> >> > ready to process the application traffic from network can initiate
>> >> > ASP
>> >> > ACTIVE to SGP.
>> >> >
>> >> > Regards
>> >> > Deepak
>> >> >
>> >> > ________________________________
>> >> > From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On
>> >> Behalf
>> >> > Of Anand N Ilkal
>> >> > Sent: Tuesday, January 04, 2011 1:22 PM
>> >> > To: sigtran@ietf.org
>> >> > Subject: [Sigtran] ASP active procedure
>> >> >
>> >> > Hello,
>> >> >
>> >> > i have doubt regarding the following section is RFC 4666  -
>> >> > 4.3.4.3.  ASP Active Procedures
>> >> >
>> >> >    Anytime after the ASP has received an ASP Up Ack message from the
>> SGP
>> >> >    or IPSP, the ASP MAY send an ASP Active message to the SGP,
>> >> >    indicating that the ASP is ready to start processing traffic....
>> >> >
>> >> > 1. why ASP MAY chose not to send ASP active on receipt of ASP Up Ack?
>> >> > 2. is receipt of ASP Up Ack message is treated as sufficient
>> condition,
>> >> > whereas there is a necessary condition which should be satisfied so
>> >> > as
>> >> ASP
>> >> > active message is sent? if so, what is that condition?
>> >> >
>> >> > --
>> >> > with regards,
>> >> > Anand kumar Ilkal
>> >> >
>> >> > ________________________________
>> >> > "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising
>> >> from
>> >> > the use of the information transmitted by this email including damage
>> >> from
>> >> > virus."
>> >> >
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> with regards,
>> >> Anand kumar Ilkal
>> >>
>> >> ------------------------------
>> >> "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising
>> from
>> >> the use of the information transmitted by this email including damage
>> from
>> >> virus."
>> >>
>> >
>> >
>> >
>> > --
>> > with regards,
>> > Anand kumar Ilkal
>> >
>>
>
>
>
> --
> with regards,
> Anand kumar Ilkal
>

From arif15jan@gmail.com  Wed Jan  5 01:35:33 2011
Return-Path: <arif15jan@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E606C3A6CD5 for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 01:35:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.374
X-Spam-Level: 
X-Spam-Status: No, score=-3.374 tagged_above=-999 required=5 tests=[AWL=0.225,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fedsBKLqstgQ for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 01:35:32 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 718A73A6992 for <sigtran@ietf.org>; Wed,  5 Jan 2011 01:35:32 -0800 (PST)
Received: by qwg5 with SMTP id 5so16223210qwg.31 for <sigtran@ietf.org>; Wed, 05 Jan 2011 01:37:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=W9SsnbMf6mF5v9HXdWVp7M+dxz2V+FGRSh03K5AH+J8=; b=Fj9vsoPYMz807YfnZ/CMpxq2ob8e3iWnJoWXxeabwX54qf0jpCkeDMl2kMPf8tNPy6 H7zRdiGx+lIGl7lyEVhmMXBpDoJ/TOIEsX3egK6qDEZVLBtuCESa29ucn1MaB7dKOFB5 iALzhvgjSfuW2PZS7BMQK+5x1T4e6QQGZSyY0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Kv2XvC20F6rXxGtHPY5tWr3hWBlfbeA5HbRzktfxZBWp4UBdzFbYg6iFfR+7SOgvc3 nMTSjxa/awJpawhUgz2YgL+7W3qdji9wuijWEH9kDHM/aCG0SQycteloABh7j1+Jcr0k JVbxM1pUQ5VL21eXf1IkO/HbZ4qOPYE7iTneA=
MIME-Version: 1.0
Received: by 10.224.181.141 with SMTP id by13mr21720786qab.98.1294220257787; Wed, 05 Jan 2011 01:37:37 -0800 (PST)
Received: by 10.220.75.3 with HTTP; Wed, 5 Jan 2011 01:37:37 -0800 (PST)
In-Reply-To: <AANLkTi=c73mO-x6Tx5Yfrut7pzE5_o3HUcqemx2C8Koo@mail.gmail.com>
References: <AANLkTi=c73mO-x6Tx5Yfrut7pzE5_o3HUcqemx2C8Koo@mail.gmail.com>
Date: Wed, 5 Jan 2011 15:07:37 +0530
Message-ID: <AANLkTinAiS0+mmrs8ZEpX9aUEnxu_wdnZnZ+-D8cvAwC@mail.gmail.com>
From: arif khan <arif15jan@gmail.com>
To: Imran Raza Khan <imranrazakhan@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] TCAP User Adaptation Layer
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 09:35:34 -0000

May be it has been deprecated and has been moved into other packages.


On 1/3/11, Imran Raza Khan <imranrazakhan@gmail.com> wrote:
> Hi,
>
> I want to inquire about the TCAP user Adaptation Layer draft. Available on
> link
> http://tools.ietf.org/html/draft-bidulock-sigtran-tua-05<http://www.google.com/url?sa=D&q=http://tools.ietf.org/html/draft-bidulock-sigtran-tua-05&usg=AFQjCNFfxGAS2BRAazFKQdXLdWlHMg8-fw>
>  .
>
> I have couple of question regarding that
>
>    - Why its status is expired?
>    - Is it still implementable?
>    - Any further roadmap of TUA?
>    - Will it be part of SIGTRAN or not?
>
> Regards,
> imran Raza Khan
>

From bidulock@openss7.org  Wed Jan  5 02:22:34 2011
Return-Path: <bidulock@openss7.org>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA6A03A6B6F for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 02:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nf3lpeyD7G2J for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 02:22:33 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id 603CE3A6A1A for <sigtran@ietf.org>; Wed,  5 Jan 2011 02:22:33 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p05AOYfA025720; Wed, 5 Jan 2011 03:24:34 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p05AOYRp025595; Wed, 5 Jan 2011 03:24:34 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id p05AOYvp025594; Wed, 5 Jan 2011 03:24:34 -0700
Date: Wed, 5 Jan 2011 03:24:34 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: arif khan <arif15jan@gmail.com>
Message-ID: <20110105102434.GA25360@openss7.org>
Mail-Followup-To: arif khan <arif15jan@gmail.com>, Anand N Ilkal <anandnilkal@gmail.com>, "sigtran@ietf.org" <sigtran@ietf.org>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com> <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com> <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com> <AANLkTin-FSm_hjmdpEQ=Sxf_NzTV7x0ikC17F1SJ+Hdd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AANLkTin-FSm_hjmdpEQ=Sxf_NzTV7x0ikC17F1SJ+Hdd@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Anand N Ilkal <anandnilkal@gmail.com>, "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 10:22:34 -0000

arif,

arif khan wrote:                                                      (Wed, 05 Jan 2011 14:53:15)
> No It is wrong to keep it must...........
> 
> You may send one or multiple ASP ACT message depending on the
> configuration of ASPs
> 
> Suppose if you have 2 asp and you want to send aspac for both after
> receiving the ASP UP Ack msg from SGP.In this situation either wait
> for the second asp ack to send the aspac for both the asp or one by
> one.
> 
> So for this reason the MAY tag is given.
> 

No.  The reason is that it is not necessary for an ASP to ever
send an ASP Active message.

Consider and ASP that goes ASP-UP with an SGP just to receive
NOTIFY messages for its AS, and nothing else.  This is
permitted.

Also, a backup ASP may never ever need to go active.  This too
is permitted.

MUST or SHOULD is terribly wrong.  Please try to understand the
standard before trying to change it.

--brian

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

From anandnilkal@gmail.com  Wed Jan  5 02:39:53 2011
Return-Path: <anandnilkal@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9AC673A6B76 for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 02:39:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.978
X-Spam-Level: 
X-Spam-Status: No, score=-2.978 tagged_above=-999 required=5 tests=[AWL=0.620,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8cmpOT0Cuvee for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 02:39:52 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 1E75E3A6949 for <sigtran@ietf.org>; Wed,  5 Jan 2011 02:39:52 -0800 (PST)
Received: by ywk9 with SMTP id 9so6726863ywk.31 for <sigtran@ietf.org>; Wed, 05 Jan 2011 02:41:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=88WzjWpGMnFGSMKu4s4X/26QCcgph98M123Usv/czMI=; b=hg/RM6i92kfgwHyiUYBIA1pv/frK9Fq/njDBr6LZ9iDGJRJlSY9DCBettOmL/3tus/ ZlXbwzKAxlO08RImxs9L6NHA8ynmjuxQOmm4jlpIg/XES6+49Z4x6IfB04M9lgbHrlWa RxjeWl0rX1jPtDQVtD8Q0ERh2IleIyapVlCx8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=NZaLF0rZc+PMoY48toOwpbtPwfEBdqpCKiZicIqTiutjKsifsgvGsVc8W9GJuUxJcN v3B3XIFIgSnwCay4ZhlCnLcx90hLb4825QdCk105UDEJzb0He/2vSHmWUptMLN9gaeHb CoftmF2tF5IJhe09+ZW4sm8LqujMvGZFNAKY0=
MIME-Version: 1.0
Received: by 10.236.95.17 with SMTP id o17mr14206456yhf.56.1294224118835; Wed, 05 Jan 2011 02:41:58 -0800 (PST)
Received: by 10.236.108.145 with HTTP; Wed, 5 Jan 2011 02:41:58 -0800 (PST)
In-Reply-To: <20110105102434.GA25360@openss7.org>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com> <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com> <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com> <AANLkTin-FSm_hjmdpEQ=Sxf_NzTV7x0ikC17F1SJ+Hdd@mail.gmail.com> <20110105102434.GA25360@openss7.org>
Date: Wed, 5 Jan 2011 16:11:58 +0530
Message-ID: <AANLkTi=aHKioWYXbkQ2SaROVzHrwpWk_hjSkbGJBgCZk@mail.gmail.com>
From: Anand N Ilkal <anandnilkal@gmail.com>
To: bidulock@openss7.org, arif khan <arif15jan@gmail.com>,  Anand N Ilkal <anandnilkal@gmail.com>, "sigtran@ietf.org" <sigtran@ietf.org>
Content-Type: multipart/alternative; boundary=0023544fb8dcdce99904991708aa
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 10:39:53 -0000

--0023544fb8dcdce99904991708aa
Content-Type: text/plain; charset=ISO-8859-1

Hello Brian,

"Consider and ASP that goes ASP-UP with an SGP just to receive
NOTIFY messages for its AS, and nothing else.  This is
permitted."

the above comment pretty much solves my doubt.

On 5 January 2011 15:54, Brian F. G. Bidulock <bidulock@openss7.org> wrote:

> arif,
>
> arif khan wrote:                                                      (Wed,
> 05 Jan 2011 14:53:15)
> > No It is wrong to keep it must...........
> >
> > You may send one or multiple ASP ACT message depending on the
> > configuration of ASPs
> >
> > Suppose if you have 2 asp and you want to send aspac for both after
> > receiving the ASP UP Ack msg from SGP.In this situation either wait
> > for the second asp ack to send the aspac for both the asp or one by
> > one.
> >
> > So for this reason the MAY tag is given.
> >
>
> No.  The reason is that it is not necessary for an ASP to ever
> send an ASP Active message.
>
> Consider and ASP that goes ASP-UP with an SGP just to receive
> NOTIFY messages for its AS, and nothing else.  This is
> permitted.
>
> Also, a backup ASP may never ever need to go active.  This too
> is permitted.
>
> MUST or SHOULD is terribly wrong.  Please try to understand the
> standard before trying to change it.
>
> --brian
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>



-- 
with regards,
Anand kumar Ilkal

--0023544fb8dcdce99904991708aa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Brian,<br><br><div>&quot;Consider and ASP that goes ASP-UP with an SG=
P just to receive<br>NOTIFY messages for its AS, and nothing else. =A0This =
is<br>permitted.&quot;</div><div><br></div><div>the above comment pretty mu=
ch solves my doubt.<br>
<div><br><div class=3D"gmail_quote">On 5 January 2011 15:54, Brian F. G. Bi=
dulock <span dir=3D"ltr">&lt;<a href=3D"mailto:bidulock@openss7.org">bidulo=
ck@openss7.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
arif,<br>
<br>
arif khan wrote: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(Wed, 05 Jan 2011 14:53:=
15)<br>
<div class=3D"im">&gt; No It is wrong to keep it must...........<br>
&gt;<br>
&gt; You may send one or multiple ASP ACT message depending on the<br>
&gt; configuration of ASPs<br>
&gt;<br>
&gt; Suppose if you have 2 asp and you want to send aspac for both after<br=
>
&gt; receiving the ASP UP Ack msg from SGP.In this situation either wait<br=
>
&gt; for the second asp ack to send the aspac for both the asp or one by<br=
>
&gt; one.<br>
&gt;<br>
&gt; So for this reason the MAY tag is given.<br>
&gt;<br>
<br>
</div>No. =A0The reason is that it is not necessary for an ASP to ever<br>
send an ASP Active message.<br>
<br>
Consider and ASP that goes ASP-UP with an SGP just to receive<br>
NOTIFY messages for its AS, and nothing else. =A0This is<br>
permitted.<br>
<br>
Also, a backup ASP may never ever need to go active. =A0This too<br>
is permitted.<br>
<br>
MUST or SHOULD is terribly wrong. =A0Please try to understand the<br>
standard before trying to change it.<br>
<br>
--brian<br>
<font color=3D"#888888"><br>
--<br>
Brian F. G. Bidulock<br>
<a href=3D"mailto:bidulock@openss7.org">bidulock@openss7.org</a><br>
<a href=3D"http://www.openss7.org/" target=3D"_blank">http://www.openss7.or=
g/</a><br>
</font></blockquote></div><br><br clear=3D"all"><br>-- <br>with regards,<br=
>Anand kumar Ilkal<br>
</div></div>

--0023544fb8dcdce99904991708aa--

From arif15jan@gmail.com  Wed Jan  5 09:17:54 2011
Return-Path: <arif15jan@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 189303A6C16 for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 09:17:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.419
X-Spam-Level: 
X-Spam-Status: No, score=-3.419 tagged_above=-999 required=5 tests=[AWL=0.180,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RXFrSwxaD7kt for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 09:17:53 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id DF8213A6C07 for <sigtran@ietf.org>; Wed,  5 Jan 2011 09:17:52 -0800 (PST)
Received: by qyk34 with SMTP id 34so17654589qyk.10 for <sigtran@ietf.org>; Wed, 05 Jan 2011 09:19:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=PYbJeP0YT4JBGxQoinc9E3AlyfepRwTH/3k0ZLRvemE=; b=SVWPKnVd/g+FTcRDBwS1NFaG5zhapRBUWK8+B04eRofdin1toZXnufinhnz77GwClw zion7pmWQsmlgAmUyLF+pKxG8uGiCDw0XkpsgTzgTX08mWLyodcYxd1JEOQCtJPors1J D2ej2sgVRQ5D6yIquH6bO0t899mGRUKH5kSbg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=BjHfVPPqa4wHXc+NaULqHgO9KMdqDLEdKZOz8837bX8Y58wg0uM0N0hw7AUX6dxw1S Zzs6rMbWxj8RkkwW1k6ZpNjv7ep0wwVEg/MhAEFzhibyq/R25Mnan9xe7Eccd1BSk8Z1 c9ILkT5jZblFaQCTVfjW/GvWAYO/zw4kvFQuA=
MIME-Version: 1.0
Received: by 10.224.181.141 with SMTP id by13mr22112195qab.98.1294247999623; Wed, 05 Jan 2011 09:19:59 -0800 (PST)
Received: by 10.220.75.3 with HTTP; Wed, 5 Jan 2011 09:19:59 -0800 (PST)
In-Reply-To: <20110105102434.GA25360@openss7.org>
References: <AANLkTi=pQFzf14y_0vG0UCnqNpjs3=Tr0Jr51M40LOyy@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CCD9@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTi=AMJ1cY0n66kS5RJwHuO5b1+fNmQ3UpfC7AXx4@mail.gmail.com> <AANLkTinVmwUS=gCSFdGfES3f3sf1C1DqYG9vMZz9BUQf@mail.gmail.com> <DF735188ED91BD458FA0E0C17929339F013665CEA2@GUREXMB01.ASIAN.AD.ARICENT.COM> <AANLkTimGzK6VYQJikg16ngGZjBUPOMwGs=_PJVvR5Ug7@mail.gmail.com> <AANLkTi=ybtw3tjbsLG798Q3zV79i659VP-oKtb-cbCrt@mail.gmail.com> <AANLkTikENz8NbWZ8c9nTuP7-Diz1J2hRMwZ3B8CYfWZR@mail.gmail.com> <AANLkTin-FSm_hjmdpEQ=Sxf_NzTV7x0ikC17F1SJ+Hdd@mail.gmail.com> <20110105102434.GA25360@openss7.org>
Date: Wed, 5 Jan 2011 22:49:59 +0530
Message-ID: <AANLkTiniW17e16ej78-BfkSNAJhG4dLhsxfTPsOA=RGc@mail.gmail.com>
From: arif khan <arif15jan@gmail.com>
To: bidulock@openss7.org, arif khan <arif15jan@gmail.com>,  Anand N Ilkal <anandnilkal@gmail.com>, "sigtran@ietf.org" <sigtran@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Sigtran] ASP active procedure
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 17:17:54 -0000

Thanks Brian!!!!!!!!
Yes of course any side can send ASPAC.....


On 1/5/11, Brian F. G. Bidulock <bidulock@openss7.org> wrote:
> arif,
>
> arif khan wrote:                                                      (Wed,
> 05 Jan 2011 14:53:15)
>> No It is wrong to keep it must...........
>>
>> You may send one or multiple ASP ACT message depending on the
>> configuration of ASPs
>>
>> Suppose if you have 2 asp and you want to send aspac for both after
>> receiving the ASP UP Ack msg from SGP.In this situation either wait
>> for the second asp ack to send the aspac for both the asp or one by
>> one.
>>
>> So for this reason the MAY tag is given.
>>
>
> No.  The reason is that it is not necessary for an ASP to ever
> send an ASP Active message.
>
> Consider and ASP that goes ASP-UP with an SGP just to receive
> NOTIFY messages for its AS, and nothing else.  This is
> permitted.
>
> Also, a backup ASP may never ever need to go active.  This too
> is permitted.
>
> MUST or SHOULD is terribly wrong.  Please try to understand the
> standard before trying to change it.
>
> --brian
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>

From santhana@huawei.com  Wed Jan  5 21:10:06 2011
Return-Path: <santhana@huawei.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 243D23A6ED0 for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 21:10:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.744
X-Spam-Level: 
X-Spam-Status: No, score=-3.744 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-4,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JEtH+TSjnc3m for <sigtran@core3.amsl.com>; Wed,  5 Jan 2011 21:10:05 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 2EAA83A6ECA for <sigtran@ietf.org>; Wed,  5 Jan 2011 21:10:05 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEL00GL3541YI@szxga04-in.huawei.com> for sigtran@ietf.org; Thu, 06 Jan 2011 13:12:01 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEL00IZS541GT@szxga04-in.huawei.com> for sigtran@ietf.org; Thu, 06 Jan 2011 13:12:01 +0800 (CST)
Received: from BLRNSHTIPL2NC ([10.18.1.32]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LEL00BPY54091@szxml04-in.huawei.com> for sigtran@ietf.org; Thu, 06 Jan 2011 13:12:01 +0800 (CST)
Date: Thu, 06 Jan 2011 10:26:34 +0530
From: Santhana <santhana@huawei.com>
To: sigtran@ietf.org
Message-id: <C23941ED19204949AADB4D957AE5367F@china.huawei.com>
Organization: Htipl
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.4657
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_hFbvFbGMX3wtHJkyekikBg)"
Thread-index: AcutXhc8sVQnZgQ9SCSxPnI2MeRTMg==
Subject: [Sigtran] [M3UA] ASP UP in IPSP DE mode
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: santhana@huawei.com
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2011 05:10:06 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_hFbvFbGMX3wtHJkyekikBg)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Dear Brian

            In IPSP DE mode, is the double exchange of ASP UP messages
mandatory? As per the M3UA RFC 4666, in section 4.3.4.1.2 para2 says double
exchange of ASPSM is MUST.

Whereas in section 5.6.2 in the sequence diagrams it says second exchange is
optional.

 

If it is mandated, then what purpose it solves?

 

Regards

Santhanakrishnan


--Boundary_(ID_hFbvFbGMX3wtHJkyekikBg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Dear Brian<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In
<st1:place w:st="on"><st1:City w:st="on">IPSP</st1:City> <st1:State w:st="on">DE</st1:State></st1:place>
mode, is the double exchange of ASP UP messages mandatory? As per the M3UA RFC
4666, in section 4.3.4.1.2 para2 says double exchange of ASPSM is MUST.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Whereas in section 5.6.2 in the sequence diagrams it says second
exchange is optional.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>If it is mandated, then what purpose it solves?<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Regards<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Santhanakrishnan<o:p></o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_hFbvFbGMX3wtHJkyekikBg)--

From bidulock@openss7.org  Thu Jan  6 01:44:04 2011
Return-Path: <bidulock@openss7.org>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CD2B3A6C50 for <sigtran@core3.amsl.com>; Thu,  6 Jan 2011 01:44:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t+G9X-3OQXm6 for <sigtran@core3.amsl.com>; Thu,  6 Jan 2011 01:44:03 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id C36BE3A6BA7 for <sigtran@ietf.org>; Thu,  6 Jan 2011 01:44:02 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p069joeI017560; Thu, 6 Jan 2011 02:45:50 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p069joBS014990; Thu, 6 Jan 2011 02:45:50 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id p069joqT014989; Thu, 6 Jan 2011 02:45:50 -0700
Date: Thu, 6 Jan 2011 02:45:50 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Santhana <santhana@huawei.com>
Message-ID: <20110106094549.GC14204@openss7.org>
Mail-Followup-To: Santhana <santhana@huawei.com>, sigtran@ietf.org
References: <C23941ED19204949AADB4D957AE5367F@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C23941ED19204949AADB4D957AE5367F@china.huawei.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] [M3UA] ASP UP in IPSP DE mode
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2011 09:44:04 -0000

Santhana,

Please see comments below...

Santhana wrote:                               (Thu, 06 Jan 2011 10:26:34)
>    Dear Brian
> 
>                In IPSP DE mode, is the double exchange of ASP UP messages
>    mandatory? As per the M3UA RFC 4666, in section 4.3.4.1.2 para2 says
>    double exchange of ASPSM is MUST.
> 
>    Whereas in section 5.6.2 in the sequence diagrams it says second
>    exchange is optional.
> 
> 
>    If it is mandated, then what purpose it solves?
> 
> 
>    Regards
> 
>    Santhanakrishnan

I don't know what purpose it solves.  There was a change from RFC3332 to
RFC4666 in 4.3.4.1.2 para2, but the example in 5.6.2 did not change.  But
then the editor of RFC4666 did a poor job of keeping examples up to date
with the text.

 RFC 4666

   Alternatively, when using the IPSP DE model, an interchange of ASP Up
   messages from each end MUST be performed.  Four messages are needed
   for completion.

 RFC 3332

   Alternatively, an interchange of ASP Up messages from each end can be
   performed. This option follows the ASP state transition diagram. It
   would need four messages for completion.

The only reason I can remember for requiring double exchange of ASP-UP
for DE was so that a misconfiguration between SE and DE would be detected.
The original intent from RFC 3332 is described at the end of example
RFC4666/5.6.2 or RFC3332/5.5.2 (which are identical).

   In this approach, only one single exchange of ASP Up message can be
   considered as enough since the response by the other peer can be
   considered as a notice that it is in ASP_UP state.

But, in general, DE mode is always a situation of performing two message
exchanges where one will do.  Use SE mode wherever possible.

--brian

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

From cbenson@adax.com  Thu Jan  6 10:58:19 2011
Return-Path: <cbenson@adax.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A33753A6CD8 for <sigtran@core3.amsl.com>; Thu,  6 Jan 2011 10:58:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.72
X-Spam-Level: 
X-Spam-Status: No, score=-1.72 tagged_above=-999 required=5 tests=[AWL=0.279,  BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MfSaWLMdA0xG for <sigtran@core3.amsl.com>; Thu,  6 Jan 2011 10:58:18 -0800 (PST)
Received: from mail1.adax.com (mail1.adax.com [208.201.231.104]) by core3.amsl.com (Postfix) with ESMTP id 7A5253A6CC6 for <sigtran@ietf.org>; Thu,  6 Jan 2011 10:58:18 -0800 (PST)
Received: from adax (adax [12.0.0.88]) by mail1.adax.com (Postfix) with ESMTP id 40270211FA; Thu,  6 Jan 2011 11:00:25 -0800 (PST)
Received: by adax (Postfix, from userid 243) id 9E7E98EDD9; Thu,  6 Jan 2011 11:02:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by adax (Postfix) with ESMTP id 97B2C8EDD7; Thu,  6 Jan 2011 11:02:16 -0800 (PST)
Date: Thu, 6 Jan 2011 11:02:16 -0800 (PST)
From: Chris Benson <cbenson@adax.com>
X-X-Sender: cbenson@adax.adax
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
In-Reply-To: <20110106094549.GC14204@openss7.org>
Message-ID: <Pine.LNX.4.64.1101061055311.21714@adax.adax>
References: <C23941ED19204949AADB4D957AE5367F@china.huawei.com> <20110106094549.GC14204@openss7.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] [M3UA] ASP UP in IPSP DE mode
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2011 18:58:19 -0000

Brian and Santhana,

Noting first that "Brian was there", and "I was not",
I had considered that the DE mode was to cater to
different ASP states at each end of the IPSP pairing.

I think this means that in DE mode, sending an ASP-UP-Ack
meant that you were permitting the other side to enter
ASP UP state, but weren't implying that you were requesting
the same for your own state.

The usefulness of one side being UP and the other side
not UP in a single peer-to-peer relationship is beyond
my imaginings, though.  I think Brian's implication
is that if you are allowing the other side to move to
ASP-UP then you are admitting that you are happy to go
ASP-UP too, and I agree that SE is always the preferred
IPSP mode.

With thanks, from Chris Benson.

On Thu, 6 Jan 2011, Brian F. G. Bidulock wrote:

>>  Date: Thu, 6 Jan 2011 02:45:50 -0700
>>  From: Brian F. G. Bidulock <bidulock@openss7.org>
>>  To: Santhana <santhana@huawei.com>
>>  Cc:  <sigtran@ietf.org>
>>  Subject: Re: [Sigtran] [M3UA] ASP UP in IPSP DE mode
>>  
>>  Santhana,
>>  
>>  Please see comments below...
>>  
>>  Santhana wrote:                               (Thu, 06 Jan 2011 10:26:34)
>>  >    Dear Brian
>>  > 
>>  >                In IPSP DE mode, is the double exchange of ASP UP messages
>>  >    mandatory? As per the M3UA RFC 4666, in section 4.3.4.1.2 para2 says
>>  >    double exchange of ASPSM is MUST.
>>  > 
>>  >    Whereas in section 5.6.2 in the sequence diagrams it says second
>>  >    exchange is optional.
>>  > 
>>  > 
>>  >    If it is mandated, then what purpose it solves?
>>  > 
>>  > 
>>  >    Regards
>>  > 
>>  >    Santhanakrishnan
>>  
>>  I don't know what purpose it solves.  There was a change from RFC3332 to
>>  RFC4666 in 4.3.4.1.2 para2, but the example in 5.6.2 did not change.  But
>>  then the editor of RFC4666 did a poor job of keeping examples up to date
>>  with the text.
>>  
>>   RFC 4666
>>  
>>     Alternatively, when using the IPSP DE model, an interchange of ASP Up
>>     messages from each end MUST be performed.  Four messages are needed
>>     for completion.
>>  
>>   RFC 3332
>>  
>>     Alternatively, an interchange of ASP Up messages from each end can be
>>     performed. This option follows the ASP state transition diagram. It
>>     would need four messages for completion.
>>  
>>  The only reason I can remember for requiring double exchange of ASP-UP
>>  for DE was so that a misconfiguration between SE and DE would be detected.
>>  The original intent from RFC 3332 is described at the end of example
>>  RFC4666/5.6.2 or RFC3332/5.5.2 (which are identical).
>>  
>>     In this approach, only one single exchange of ASP Up message can be
>>     considered as enough since the response by the other peer can be
>>     considered as a notice that it is in ASP_UP state.
>>  
>>  But, in general, DE mode is always a situation of performing two message
>>  exchanges where one will do.  Use SE mode wherever possible.
>>  
>>  --brian
>>  
>>  -- 
>>  Brian F. G. Bidulock
>>  bidulock@openss7.org
>>  http://www.openss7.org/
>>  _______________________________________________
>>  Sigtran mailing list
>>  Sigtran@ietf.org
>>  https://www.ietf.org/mailman/listinfo/sigtran
>>  

From suresh.jaddu@nsn.com  Thu Jan  6 21:33:04 2011
Return-Path: <suresh.jaddu@nsn.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDFC93A63EB for <sigtran@core3.amsl.com>; Thu,  6 Jan 2011 21:33:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C+6MLx1PwA1P for <sigtran@core3.amsl.com>; Thu,  6 Jan 2011 21:33:02 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id CB7B93A63D2 for <sigtran@ietf.org>; Thu,  6 Jan 2011 21:33:01 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p075Z0WZ027392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 7 Jan 2011 06:35:00 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p075YtkF002317; Fri, 7 Jan 2011 06:34:59 +0100
Received: from SGSIEXC017.nsn-intra.net ([10.159.224.99]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 7 Jan 2011 06:34:53 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 7 Jan 2011 13:29:10 +0800
Message-ID: <53078B21B5DDA14BA1E89B400224A33502576DCD@SGSIEXC017.nsn-intra.net>
In-Reply-To: <Pine.LNX.4.64.1101061055311.21714@adax.adax>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sigtran] [M3UA] ASP UP in IPSP DE mode
Thread-Index: Acut0/5kzUD03CO2TE2+7Th9OoT2QwATw+pQ
References: <C23941ED19204949AADB4D957AE5367F@china.huawei.com><20110106094549.GC14204@openss7.org> <Pine.LNX.4.64.1101061055311.21714@adax.adax>
From: "Jaddu, Suresh (NSN - IN/Bangalore)" <suresh.jaddu@nsn.com>
To: "ext Chris Benson" <cbenson@adax.com>, "Brian F. G. Bidulock" <bidulock@openss7.org>
X-OriginalArrivalTime: 07 Jan 2011 05:34:53.0234 (UTC) FILETIME=[9C2F7120:01CBAE2C]
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] [M3UA] ASP UP in IPSP DE mode
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 05:33:05 -0000

Hi,

Since SE/DE is under discussion I have one relevant question. RFC talks
about the two modes one is SGASP and another one IPSP (point to point)
but it is possible to have point to multi point network as well as shown
below (model-2).

model 1)
--------

Node 1  |  ------->   Node 2  [IPSP-SE]


model 2)
--------

	 |    ------>   Node2
Node 1 |    		      [IPSP-DE]
	 |    ------->  Node3


RFC talks about the IPSP is for point to point (which I understood as
model 1) but it does not talk much (atleast I could not find mentioning
of this) about the model-2 and possible configuration options. I know
the model-2) is also can be achieved using the IPSP but this is not
exactly the point to point some additional considerations are required,
I am not sure any one has encountered this before?? Question is what is
the recommended configuration for model-2? I do not think SE model will
straight way work for model-2?? From what I understand DE is more
suitable here?? Any one has similar views??

Suresh.

-----Original Message-----
From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On
Behalf Of ext Chris Benson
Sent: Friday, January 07, 2011 12:32 AM
To: Brian F. G. Bidulock
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] [M3UA] ASP UP in IPSP DE mode

Brian and Santhana,

Noting first that "Brian was there", and "I was not",
I had considered that the DE mode was to cater to
different ASP states at each end of the IPSP pairing.

I think this means that in DE mode, sending an ASP-UP-Ack
meant that you were permitting the other side to enter
ASP UP state, but weren't implying that you were requesting
the same for your own state.

The usefulness of one side being UP and the other side
not UP in a single peer-to-peer relationship is beyond
my imaginings, though.  I think Brian's implication
is that if you are allowing the other side to move to
ASP-UP then you are admitting that you are happy to go
ASP-UP too, and I agree that SE is always the preferred
IPSP mode.

With thanks, from Chris Benson.

On Thu, 6 Jan 2011, Brian F. G. Bidulock wrote:

>>  Date: Thu, 6 Jan 2011 02:45:50 -0700
>>  From: Brian F. G. Bidulock <bidulock@openss7.org>
>>  To: Santhana <santhana@huawei.com>
>>  Cc:  <sigtran@ietf.org>
>>  Subject: Re: [Sigtran] [M3UA] ASP UP in IPSP DE mode
>> =20
>>  Santhana,
>> =20
>>  Please see comments below...
>> =20
>>  Santhana wrote:                               (Thu, 06 Jan 2011
10:26:34)
>>  >    Dear Brian
>>  >=20
>>  >                In IPSP DE mode, is the double exchange of ASP UP
messages
>>  >    mandatory? As per the M3UA RFC 4666, in section 4.3.4.1.2 para2
says
>>  >    double exchange of ASPSM is MUST.
>>  >=20
>>  >    Whereas in section 5.6.2 in the sequence diagrams it says
second
>>  >    exchange is optional.
>>  >=20
>>  >=20
>>  >    If it is mandated, then what purpose it solves?
>>  >=20
>>  >=20
>>  >    Regards
>>  >=20
>>  >    Santhanakrishnan
>> =20
>>  I don't know what purpose it solves.  There was a change from
RFC3332 to
>>  RFC4666 in 4.3.4.1.2 para2, but the example in 5.6.2 did not change.
But
>>  then the editor of RFC4666 did a poor job of keeping examples up to
date
>>  with the text.
>> =20
>>   RFC 4666
>> =20
>>     Alternatively, when using the IPSP DE model, an interchange of
ASP Up
>>     messages from each end MUST be performed.  Four messages are
needed
>>     for completion.
>> =20
>>   RFC 3332
>> =20
>>     Alternatively, an interchange of ASP Up messages from each end
can be
>>     performed. This option follows the ASP state transition diagram.
It
>>     would need four messages for completion.
>> =20
>>  The only reason I can remember for requiring double exchange of
ASP-UP
>>  for DE was so that a misconfiguration between SE and DE would be
detected.
>>  The original intent from RFC 3332 is described at the end of example
>>  RFC4666/5.6.2 or RFC3332/5.5.2 (which are identical).
>> =20
>>     In this approach, only one single exchange of ASP Up message can
be
>>     considered as enough since the response by the other peer can be
>>     considered as a notice that it is in ASP_UP state.
>> =20
>>  But, in general, DE mode is always a situation of performing two
message
>>  exchanges where one will do.  Use SE mode wherever possible.
>> =20
>>  --brian
>> =20
>>  --=20
>>  Brian F. G. Bidulock
>>  bidulock@openss7.org
>>  http://www.openss7.org/
>>  _______________________________________________
>>  Sigtran mailing list
>>  Sigtran@ietf.org
>>  https://www.ietf.org/mailman/listinfo/sigtran
>> =20
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www.ietf.org/mailman/listinfo/sigtran

From bidulock@openss7.org  Fri Jan  7 02:42:45 2011
Return-Path: <bidulock@openss7.org>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5EF6C3A67F8 for <sigtran@core3.amsl.com>; Fri,  7 Jan 2011 02:42:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rp3KNNiCLhn7 for <sigtran@core3.amsl.com>; Fri,  7 Jan 2011 02:42:44 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id 345EC3A67F2 for <sigtran@ietf.org>; Fri,  7 Jan 2011 02:42:44 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p07Aim1e010823; Fri, 7 Jan 2011 03:44:48 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p07AimUR005670; Fri, 7 Jan 2011 03:44:48 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id p07AilhO005669; Fri, 7 Jan 2011 03:44:47 -0700
Date: Fri, 7 Jan 2011 03:44:47 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Jaddu, Suresh (NSN - IN/Bangalore)" <suresh.jaddu@nsn.com>
Message-ID: <20110107104447.GA5232@openss7.org>
Mail-Followup-To: "Jaddu, Suresh (NSN - IN/Bangalore)" <suresh.jaddu@nsn.com>,  ext Chris Benson <cbenson@adax.com>, sigtran@ietf.org
References: <Pine.LNX.4.64.1101061055311.21714@adax.adax> <53078B21B5DDA14BA1E89B400224A33502576DCD@SGSIEXC017.nsn-intra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53078B21B5DDA14BA1E89B400224A33502576DCD@SGSIEXC017.nsn-intra.net>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] [M3UA] ASP UP in IPSP DE mode
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 10:42:45 -0000

Suresh,

If by Model 2 you mean that Node2 can communicate with Node3 via Node1
then it is explicitly not supported by IPSP in M3UA.  Only point-to-point.
If you want Node2 to communication with Node3 via Node1, then Node1 must
be an SG and Node2 and Node3 must be ASPs.  That is, the recommended mode
is an ASP-SG mode.

--brian

Jaddu, Suresh (NSN - IN/Bangalore) wrote:     (Fri, 07 Jan 2011 13:29:10)
> Hi,
> 
> Since SE/DE is under discussion I have one relevant question. RFC talks
> about the two modes one is SGASP and another one IPSP (point to point)
> but it is possible to have point to multi point network as well as shown
> below (model-2).
> 
> model 1)
> --------
> 
> Node 1  |  ------->   Node 2  [IPSP-SE]
> 
> 
> model 2)
> --------
> 
> 	 |    ------>   Node2
> Node 1 |    		      [IPSP-DE]
> 	 |    ------->  Node3
> 
> 
> RFC talks about the IPSP is for point to point (which I understood as
> model 1) but it does not talk much (atleast I could not find mentioning
> of this) about the model-2 and possible configuration options. I know
> the model-2) is also can be achieved using the IPSP but this is not
> exactly the point to point some additional considerations are required,
> I am not sure any one has encountered this before?? Question is what is
> the recommended configuration for model-2? I do not think SE model will
> straight way work for model-2?? From what I understand DE is more
> suitable here?? Any one has similar views??
> 
> Suresh.

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

From sachin86mits@gmail.com  Fri Jan 21 05:29:07 2011
Return-Path: <sachin86mits@gmail.com>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FE723A696E for <sigtran@core3.amsl.com>; Fri, 21 Jan 2011 05:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LSV6FBjQdt2i for <sigtran@core3.amsl.com>; Fri, 21 Jan 2011 05:29:06 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id F35D03A691F for <Sigtran@ietf.org>; Fri, 21 Jan 2011 05:29:02 -0800 (PST)
Received: by eyd10 with SMTP id 10so891702eyd.31 for <Sigtran@ietf.org>; Fri, 21 Jan 2011 05:31:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=XBkmi2P2gbbLQR29CcvFptsDzpIAu7FB/W3n53DsGgs=; b=j5YobHr6odskDUm1kn6aSO+83jv5mbaVbPjC2W2FL90zgYEw9/uLIU/6Z4vN31P4C0 oUWeY5G3SBINjXP3R39DS8g4pKFuExIzZoVOww709jf5wGHDsuljFun5Y25iTe129kCf /VLXQgOdY38LsduzxhEn8XzdYFKI7eJ1tQyOQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Y73mzVZVtiSAo/7pSjumKfuEfhkrr9dYNXioPlWFNiUNfEJYhzP6tRvEFp4F9tSJoC qfc14+YToEyMJNJMan/ZEIEyPonqUuALq23mug185rMkB7d69t0/RvrQ//giI9QUAtRm 8oQHx1kXqTQYLgHYOjrtHZQ1tSkAzccvvOe9I=
MIME-Version: 1.0
Received: by 10.103.219.14 with SMTP id w14mr281297muq.3.1295616708098; Fri, 21 Jan 2011 05:31:48 -0800 (PST)
Received: by 10.102.213.30 with HTTP; Fri, 21 Jan 2011 05:31:48 -0800 (PST)
Date: Fri, 21 Jan 2011 19:01:48 +0530
Message-ID: <AANLkTi=gJ+qrUsC8YBr21cRUsRhyqtDT72j0aOUMO6qG@mail.gmail.com>
From: sachin agrawal <sachin86mits@gmail.com>
To: Sigtran@ietf.org
Content-Type: multipart/alternative; boundary=0016364c7cefa6be6d049a5b451f
Subject: [Sigtran] Is As-Pending state required in IPSP SE mode?
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jan 2011 13:29:07 -0000

--0016364c7cefa6be6d049a5b451f
Content-Type: text/plain; charset=ISO-8859-1

Hi All,

As per the RFC 4666 AS Pending state is described from the ASP-SGP
perspective, so in case of IPSP SE mode since mostly it is used as a point
to point communication. So is there any requirement of AS pending state in
IPSP SE mode.

Regards,
Sachin

--0016364c7cefa6be6d049a5b451f
Content-Type: text/html; charset=ISO-8859-1

Hi All,<br><br>As per the RFC 4666 AS Pending state is described from the ASP-SGP perspective, so in case of IPSP SE mode since mostly it is used as a point to point communication. So is there any requirement of AS pending state in IPSP SE mode.<br>
<br>Regards,<br>Sachin<br>

--0016364c7cefa6be6d049a5b451f--

From bidulock@openss7.org  Fri Jan 21 05:52:38 2011
Return-Path: <bidulock@openss7.org>
X-Original-To: sigtran@core3.amsl.com
Delivered-To: sigtran@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DC713A6987 for <sigtran@core3.amsl.com>; Fri, 21 Jan 2011 05:52:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i4Dd4ptdWfpG for <sigtran@core3.amsl.com>; Fri, 21 Jan 2011 05:52:35 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id DDDBE3A6992 for <sigtran@ietf.org>; Fri, 21 Jan 2011 05:52:34 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0LDtIre003662; Fri, 21 Jan 2011 06:55:18 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0LDtH4c001874; Fri, 21 Jan 2011 06:55:17 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id p0LDtHSU001873; Fri, 21 Jan 2011 06:55:17 -0700
Date: Fri, 21 Jan 2011 06:55:17 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: sigtran@ietf.org
Message-ID: <20110121135517.GA1731@openss7.org>
Mail-Followup-To: sigtran@ietf.org, sachin agrawal <sachin86mits@gmail.com>
References: <AANLkTi=gJ+qrUsC8YBr21cRUsRhyqtDT72j0aOUMO6qG@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AANLkTi=gJ+qrUsC8YBr21cRUsRhyqtDT72j0aOUMO6qG@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [Sigtran] Is As-Pending state required in IPSP SE mode?
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jan 2011 13:52:38 -0000

Sachin,

On Fri, 21 Jan 2011, sachin agrawal wrote:
>    As per the RFC 4666 AS Pending state is described from the ASP-SGP
>    perspective, so in case of IPSP SE mode since mostly it is used as a
>    point to point communication. So is there any requirement of AS pending
>    state in IPSP SE mode.

No, there is no need.  Note, however, that AS Pending is optional
in any regard because the duration of AS Pending state can be set
to zero (0) by the implementaiton.

--brian

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