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 10A2C3A6803; Thu,  5 Aug 2010 00:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.665
X-Spam-Level: 
X-Spam-Status: No, score=-1.665 tagged_above=-999 required=5 tests=[AWL=-0.556,
 BAYES_05=-1.11, 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 6FkMfjT0vCeP;
 Thu,  5 Aug 2010 00:35:06 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com
 [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 22F1B3A67F1;
 Thu,  5 Aug 2010 00:35:05 -0700 (PDT)
Received: by pxi20 with SMTP id 20so2670344pxi.31 for <multiple recipients>;
 Thu, 05 Aug 2010 00:35:35 -0700 (PDT)
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=/E8/ywLzUA2sh1UIC0+lviYW9QuvuyEeZbI4Y115H+I=;
 b=RiYCNutY5JrsIhmERgaP8H7OQ5QhgXeOCdEMTu0alGpID7OPOhd2OgcLbdbaAUFZHP
 dDyCdkeDQ/LFaQn3UVVb4CDllHF0oa1pvnbBq3QLs280e5tA0QUXKI6ho+tMHWTvne3q
 UYElLSHxMiV1O1tNE+ju6XvPXguhVbhKo+xV4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
 h=mime-version:date:message-id:subject:from:to:content-type;
 b=WeotJp+CuPjiYa3FjwJuPI0ZvYS63XiqFZtv8OQ0v6PRVL/xR1gK5CKuYOv93eWSxD
 5paivpHFizDQRn99q+cp1co26kYURjWDq3uS74r3tMq+iDfeUeJhI1qJzil4WNHm1wV/
 xkw82K6y2OXTECVhQQ8jwv6TkGp5DGN8cPETU=
MIME-Version: 1.0
Received: by 10.142.200.5 with SMTP id x5mr8709853wff.227.1280993735319;
 Thu,  05 Aug 2010 00:35:35 -0700 (PDT)
Received: by 10.142.78.12 with HTTP; Thu, 5 Aug 2010 00:35:35 -0700 (PDT)
Date: Thu, 5 Aug 2010 13:05:35 +0530
Message-ID: <AANLkTimuwMWWykHHnjBbLE2V-usLqV3Gbm8tBrcRfwA9@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: mpls-tp@ietf.org, mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary=000e0cd32cf88da230048d0e9882
Subject: [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: Thu, 05 Aug 2010 07:35:09 -0000

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

Hi,

Please clarify the below query regarding *how to associate the PSC message
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 an=
d
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 LS=
Rs
(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 wit=
h
the MEG/MEP corresponding to the protection LSP - *based on the label stack=
?
*



If the answer is *=91yes=92*, then how this association be done in case if
Penultimate Hop Popping *(PHP) is enabled* where the label in the PSC packe=
t
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 sent =
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 and
so with a protection path.



(OR)



B) *=91Source MEP TLV=94* should be sent in *the =91optional TLV=92 in the =
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 =91n=
=92
working transport paths.

In this case, *should the PSC message hold any additional information in th=
e
optional TLVs so as to associate the status conveyed in the PSC message
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) LSP2
(or) LSP3 ?

Should it be discriminated by exchanging relevant information in the
=91optional TLV=92  ?


--=20
Best Regards,
Venkatesan Mahalingam.

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

<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 class=3D"773=
572705-05082010"></span></span></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 class=3D"773572705-05082010">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 class=3D"773572705-05082010"></span></s=
pan>=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 style=3D"mso-bidi-f=
ont-weight: normal"><u><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">=
The questions are:</span></u></b></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.=
25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><b style=3D"mso-bidi-=
font-weight: normal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; ms=
o-fareast-font-family: Arial"><span style=3D"mso-list: Ignore">1)<span styl=
e=3D"FONT: 7pt &#39;Times New Roman&#39;">=A0=A0=A0=A0=A0=A0 </span></span>=
</span></b><u><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Associati=
ng PSC with protection path based on the label stack:<b style=3D"mso-bidi-f=
ont-weight: normal"></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 style=3D"mso-bidi-font-weight: normal">based on the label s=
tack?</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 style=3D"mso-bidi-f=
ont-weight: normal">=91yes=92</b>, then how this association be done in cas=
e if Penultimate Hop Popping <b style=3D"mso-bidi-font-weight: normal">(PHP=
) is enabled</b> where the label in the PSC packet will be stripped off whe=
n the 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 style=3D"mso-=
bidi-font-weight: normal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Aria=
l">(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 style=3D"mso-spacerun: yes">=A0=
=A0=A0=A0=A0 </span></span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.=
25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><b style=3D"mso-bidi-=
font-weight: normal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; ms=
o-fareast-font-family: Arial"><span style=3D"mso-list: Ignore"><span style=
=3D"FONT: 7pt &#39;Times New Roman&#39;"><span class=3D"046212707-05082010"=
><font face=3D"Verdana" color=3D"#0000ff" size=3D"2">=A0=A0=A0 =A0</font></=
span>=A0</span></span></span></b><u><span style=3D"FONT-SIZE: 10pt; FONT-FA=
MILY: Arial">Associating PSC with protection path based on the MEG/MEP in o=
ptional TLV :<b style=3D"mso-bidi-font-weight: normal"></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 style=3D"mso-bidi-font-we=
ight: normal">=91Remote MEG/MEP=92</b> information of the protection LSP be=
 sent in <b style=3D"mso-bidi-font-weight: normal">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 style=3D"mso-bidi-font-weight: n=
ormal">=91Source MEP TLV=94</b> should be sent in <b style=3D"mso-bidi-font=
-weight: normal">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; TEXT-INDENT: -0.=
25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><b style=3D"mso-bidi-=
font-weight: normal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; ms=
o-fareast-font-family: Arial"><span style=3D"mso-list: Ignore"><font color=
=3D"#333333"><span class=3D"046212707-05082010"><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 style=3D"mso-bidi-font-weigh=
t: normal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In case of s=
hared<span style=3D"mso-spacerun: yes">=A0 </span>protection path in 1:n ar=
chitecture 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 style=3D"mso-bidi-font=
-weight: normal">should the PSC message hold any additional information in =
the optional TLVs so as to associate the 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 style=3D"mso-spacerun: yes=
">=A0 </span>LSP1, LSP2, LSP3 are being protected by the LSP100, then PSC m=
essages 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 style=3D"mso-spacerun=
: yes">=A0 </span>?</span></p>
</font></span><br clear=3D"all"><br>-- <br>Best Regards,<br>Venkatesan Maha=
lingam.<br>

--000e0cd32cf88da230048d0e9882--