Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
 with ESMTP id 7F4DD3A65A5; Fri,  6 Aug 2010 01:59:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.39
X-Spam-Level: 
X-Spam-Status: No, score=-2.39 tagged_above=-999 required=5 tests=[AWL=0.208,
 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 K5ggE6A3b8-h;
 Fri,  6 Aug 2010 01:59:22 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com
 [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 2E5083A6A01;
 Fri,  6 Aug 2010 01:59:22 -0700 (PDT)
Received: by pwj2 with SMTP id 2so548161pwj.31 for <multiple recipients>;
 Fri, 06 Aug 2010 01:59:53 -0700 (PDT)
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=EqT0Z7IxNIe3vCde+oYd5CrqdUGZ2g/RV8ru4KyI4hQ=;
 b=fiRPfyOm758WmIBFW/UD3D+PPtikLrOrDabPAHwzpG+I9rSoJBSJJmlwFIwK+5WUe2
 ZEWS0vA+tD+YBw33vDyhVgzf6S34ITIGyUNx+avfssAeQrHXh0uaSy5aOMwgq/YPhVDr
 MwPlydpeEZdWcnkp7RqTqC4SnQ+97vIbGl6V0=
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=xJs8YWn2a/q0wwMlJmgn+7R+l9n05T9NSr0xlNVanWCRE04bX/A1t2K0cvRIfDBIgw
 lx9ehpPpOSk0Cjx8eB0+DEV51Xq0OwxHrw+c0nw+3O5rIj5eKqHMLQKcolqBpcids5LU
 9IPXgrBX0bzN4CfEY7UvR4Oug4bqnHk4z6bgA=
MIME-Version: 1.0
Received: by 10.142.147.7 with SMTP id u7mr10126620wfd.216.1281085193449;
 Fri,  06 Aug 2010 01:59:53 -0700 (PDT)
Received: by 10.142.221.2 with HTTP; Fri, 6 Aug 2010 01:59:53 -0700 (PDT)
In-Reply-To: <AANLkTimuwMWWykHHnjBbLE2V-usLqV3Gbm8tBrcRfwA9@mail.gmail.com>
References: <AANLkTimuwMWWykHHnjBbLE2V-usLqV3Gbm8tBrcRfwA9@mail.gmail.com>
Date: Fri, 6 Aug 2010 14:29:53 +0530
Message-ID: <AANLkTim5EBdOX+XJXbPWQZSXRq05QBTo-STT8s_3ko+a@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: mpls-tp@ietf.org, mpls <mpls@ietf.org>, yaacov.weingarten@nsn.com
Content-Type: multipart/alternative; boundary=000e0cd2281ee1f380048d23e32f
Subject: Re: [mpls] Association of PSC messages to a protection path
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
 <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
 <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Aug 2010 08:59:23 -0000

--000e0cd2281ee1f380048d23e32f
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,
Can protection switching guys please answer the below query?

Thanks,
Venkat.

On Thu, Aug 5, 2010 at 1:05 PM, venkatesan mahalingam
<venkatflex@gmail.com>wrote:

>  Hi,
>
> Please clarify the below query regarding *how to associate the PSC messag=
e
> with a protection path.*
>
>
>
> Below are the details.
>
>
>
> Format of the PSC control message is as follows:
>
>
>
> 0                   1                   2                   3
>         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |0 0 0 1|Version|  Reserved     |   Channel Type =3D MPLS-TP PSC  =
|
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                          ACH TLV Header                       |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        ~                         Optional TLVs                         ~
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |Ver|Request|PT |R|  Reserved   |     FPath     |     Path      |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Figure 2: Format of PSC packet with a G-ACh header
> (draft-ietf-mpls-tp-linear-protection-02)
>
>
>
> *Transmission of PSC control packets:*
>
> The PSC packet will be encapsulated with the MPLS label and next hop mac
> and will be sent over the out going interface related to the protection
> path.
>
>
>
> *Reception of PSC control packets:*
>
> The PSC control packets will be =91label switched=92 at the intermediate =
LSRs
> (based on the protection LSP=92s label) and thus will reach the LER.
>
>
>
> *The questions are:*
>
> *1)       **Associating PSC with protection path based on the label stack=
:
> *
>
>
>
> Should the LER which receives the PSC packet, associate the PSC message
> with the MEG/MEP corresponding to the protection LSP - *based on the labe=
l
> stack?*
>
>
>
> If the answer is *=91yes=92*, then how this association be done in case i=
f
> Penultimate Hop Popping *(PHP) is enabled* where the label in the PSC
> packet will be stripped off when the LER receives the PSC packet.
>
>
>
> *(OR)*
>
>
>
> *      **Associating PSC with protection path based on the MEG/MEP in
> optional TLV :*
>
>
>
> A) Should *=91Remote MEG/MEP=92* information of the protection LSP be sen=
t in
> *the =91Optional TLV=92* from the transmitting LER?
>
> If this information is available in the PSC packet, then even if PHP is
> enabled, the LER will be able to associate the PSC packet with MEG/MEP an=
d
> so with a protection path.
>
>
>
> (OR)
>
>
>
> B) *=91Source MEP TLV=94* should be sent in *the =91optional TLV=92 in th=
e PSC
> packet ?*
>
>
>
> * 2)       **In case of shared  protection path in 1:n architecture where
> n>1:*
>
> Here the understanding is that one protection path is being shared by =91=
n=92
> working transport paths.
>
> In this case, *should the PSC message hold any additional information in
> the optional TLVs so as to associate the status conveyed in the PSC messa=
ge
> against a particular working transport path ?*
>
>
>
> (eg) if  LSP1, LSP2, LSP3 are being protected by the LSP100, then PSC
> messages will be transmitted on LSP100.
>
> In this case, the information such as : PSC request, Fault Path (FPath),
> Data path (Path) exchanged in the PSC message should be for LSP1 (or) LSP=
2
> (or) LSP3 ?
>
> Should it be discriminated by exchanging relevant information in the
> =91optional TLV=92  ?
>
>
> --
> Best Regards,
> Venkatesan Mahalingam.
>



--=20
Best Regards,
Venkatesan Mahalingam.

--000e0cd2281ee1f380048d23e32f
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>Hi,</div>
<div>Can protection switching guys please answer the below query?<br><br>Th=
anks,</div>
<div>Venkat.</div>
<div>=A0</div>
<div class=3D"gmail_quote">On Thu, Aug 5, 2010 at 1:05 PM, venkatesan mahal=
ingam <span dir=3D"ltr">&lt;<a href=3D"mailto:venkatflex@gmail.com">venkatf=
lex@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><span lang=3D"en-us"><font face=
=3D"Arial" size=3D"2">
<p class=3D"MsoNormal" dir=3D"ltr" style=3D"MARGIN: 0in 0in 0pt" align=3D"l=
eft"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span></span></spa=
n></p>
<div dir=3D"ltr" align=3D"left"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY=
: Arial">Hi,</span></div>
<div dir=3D"ltr" align=3D"left"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY=
: Arial"></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY=
: Arial">Please clarify the below query=A0regarding <strong>how to associat=
e the PSC message with a protection path.</strong></span></div>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial"><span>Below are the details.</span></span></p=
>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial"><span></span></span>=A0</p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial">Format of the PSC control message is as follo=
ws:</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial">0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 2=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 3<br>=A0=A0=A0=A0=A0=A0=
=A0 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br>
=A0=A0=A0=A0=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+<br>=A0=A0=A0=A0=A0=A0 |0 0 0 1|Version|=A0 Reserved=A0=A0=A0=A0 |=
=A0=A0 Channel Type =3D MPLS-TP PSC=A0 |<br>=A0=A0=A0=A0=A0=A0 +-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
=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=A0=A0=A0=A0 ACH TLV Header=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>=A0=A0=A0=A0=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=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=A0=A0=A0 Optional TL=
Vs=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
~<br>
=A0=A0=A0=A0=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+<br>=A0=A0=A0=A0=A0=A0 |Ver|Request|PT |R|=A0 Reserved=A0=A0 |=A0=
=A0=A0=A0 FPath=A0=A0=A0=A0 |=A0=A0=A0=A0 Path=A0=A0=A0=A0=A0 |<br>=A0=A0=
=A0=A0=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+</span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial">Figure 2: Format of PSC packet with a G-ACh h=
eader (draft-ietf-mpls-tp-linear-protection-02)</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><u><span style=3D"FONT=
-SIZE: 10pt; FONT-FAMILY: Arial">Transmission of PSC control packets:</span=
></u></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial">The PSC packet will be encapsulated with the =
MPLS label and next hop mac and will be sent over the out going interface r=
elated to the protection path.</span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><u><span style=3D"FONT=
-SIZE: 10pt; FONT-FAMILY: Arial">Reception of PSC control packets:</span></=
u></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial">The PSC control packets will be =91label swit=
ched=92 at the intermediate LSRs (based on the protection LSP=92s label) an=
d thus will reach the LER.</span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><span style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt"><b><u><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">The questions are:</span></u></b></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><b><span style=
=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span>1)<span style=3D"FONT: 7pt &=
#39;Times New Roman&#39;">=A0=A0=A0=A0=A0=A0 </span></span></span></b><u><s=
pan style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Associating PSC with prot=
ection path based on the label stack:<b></b></span></u></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">Should the LER which receives the PSC p=
acket, associate the PSC message with the MEG/MEP corresponding to the prot=
ection LSP - <b>based on the label stack?</b></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">If the answer is <b>=91yes=92</b>, then=
 how this association be done in case if Penultimate Hop Popping <b>(PHP) i=
s enabled</b> where the label in the PSC packet will be stripped off when t=
he LER receives the PSC packet.</span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><b><span style=
=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">(OR)</span></b></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.25in"><span style=3D"=
FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span>=A0=A0=A0=A0=A0 </span></span></=
p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><b><span style=
=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span><span style=3D"FONT: 7pt &#3=
9;Times New Roman&#39;"><span><font face=3D"Verdana" color=3D"#0000ff" size=
=3D"2">=A0=A0=A0 =A0</font></span>=A0</span></span></span></b><u><span styl=
e=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Associating PSC with protection p=
ath based on the MEG/MEP in optional TLV :<b></b></span></u></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.25in"><span style=3D"=
FONT-SIZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.75in"><span style=3D"=
FONT-SIZE: 10pt; FONT-FAMILY: Arial">A) Should <b>=91Remote MEG/MEP=92</b> =
information of the protection LSP be sent in <b>the =91Optional TLV=92</b> =
from the transmitting LER? </span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.75in"><span style=3D"=
FONT-SIZE: 10pt; FONT-FAMILY: Arial">If this information is available in th=
e PSC packet, then even if PHP is enabled, the LER will be able to associat=
e the PSC packet with MEG/MEP and so with a protection path.</span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.75in"><span style=3D"=
FONT-SIZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.75in"><span style=3D"=
FONT-SIZE: 10pt; FONT-FAMILY: Arial">(OR)</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.75in"><span style=3D"=
FONT-SIZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.75in"><span style=3D"=
FONT-SIZE: 10pt; FONT-FAMILY: Arial">B) <b>=91Source MEP TLV=94</b> should =
be sent in <b>the =91optional TLV=92 in the PSC packet ?</b></span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.25in"><span style=3D"=
FONT-SIZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><b><span style=
=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span><font color=3D"#333333"><spa=
n><font face=3D"Verdana">=A02</font></span>)</font><span style=3D"FONT: 7pt=
 &#39;Times New Roman&#39;">=A0=A0=A0=A0=A0=A0 </span></span></span></b><b>=
<span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In case of shared<span>=
=A0 </span>protection path in 1:n architecture where n&gt;1:</span></b></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">Here the understanding is that one prot=
ection path is being shared by =91n=92 working transport paths.</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">In this case, <b>should the PSC message=
 hold any additional information in the optional TLVs so as to associate th=
e status conveyed in the PSC message against a particular working transport=
 path ?</b></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">=A0</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">(eg) if<span>=A0 </span>LSP1, LSP2, LSP=
3 are being protected by the LSP100, then PSC messages will be transmitted =
on LSP100. </span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">In this case, the information such as :=
 PSC request, Fault Path (FPath), Data path (Path) exchanged in the PSC mes=
sage should be for LSP1 (or) LSP2 (or) LSP3 ?</span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in"><span style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: Arial">Should it be discriminated by exchangin=
g relevant information in the =91optional TLV=92<span>=A0 </span>?</span></=
p></font></span><br clear=3D"all">
<br>-- <br>Best Regards,<br><font color=3D"#888888">Venkatesan Mahalingam.<=
br></font></blockquote></div><br><br clear=3D"all"><br>-- <br>Best Regards,=
<br>Venkatesan Mahalingam.<br>

--000e0cd2281ee1f380048d23e32f--