[prev in list] [next in list] [prev in thread] [next in thread]
List: mpls
Subject: [mpls] =?gb2312?b?tPC4tDogIE1haWwgcmVnYXJkaW5nIGRyYWZ0LWNoZW4t?= =?gb2312?b?bXBscy1zb3VyY2UtbGFiZWw=
From: Xuxiaohu <xuxiaohu () huawei ! com>
Date: 2014-03-26 3:15:15
Message-ID: 1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08264D01 () NKGEML512-MBS ! china ! huawei ! com
[Download RAW message or body]
[Attachment #2 (text/plain)]
What about if a route reflector is deployed?
·¢¼þÈË: mpls [mailto:mpls-bounces@ietf.org] ´ú±í Shahram Davari
·¢ËÍʱ¼ä: 2014Äê3Ô 26ÈÕ 11:12
ÊÕ¼þÈË: Mach Chen
³ËÍ: draft-chen-mpls-source-label@tools.ietf.org; mpls@ietf.org
Ö÷Ìâ: Re: [mpls] Mail regarding draft-chen-mpls-source-label
Hi Mach
In L3VPN you could modify the VPN label distribution and distribute A unique VPN \
label to each remote VRF.
This would solve your problem by just software upgrade without need for new hardware.
Regards,
Shahram
On Mar 25, 2014, at 7:33 PM, "Mach Chen" \
<mach.chen@huawei.com<mailto:mach.chen@huawei.com>> wrote: Hi Shahram
The problem is that not all the networks deploy PW to transport the service, there \
are quite number of networks use L3VPN and other techniques.
Best regards,
Mach
From: S. Davari [mailto:davarish@yahoo.com]
Sent: Tuesday, March 25, 2014 6:08 PM
To: Mach Chen
Cc: Shahram Davari; Yimin Shen; \
draft-chen-mpls-source-label@tools.ietf.org<mailto:draft-chen-mpls-source-label@tools.ietf.org>; \
mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [mpls] Mail regarding draft-chen-mpls-source-label
Hi Mach
Since the service is P2P, each bas station has its own PW. Therefore there is no need \
to identify each BS using yet another label.
Regards,
Shahram
On Mar 25, 2014, at 1:32 AM, Mach Chen \
<mach.chen@huawei.com<mailto:mach.chen@huawei.com>> wrote: Hi Shahram,
IP/MPLS is commonly used in the mobile backhaul, and many of the networks use pure \
LDP based tunnel. The service is point-to-point (e.g., from CSG to RSG), but the LDP \
based tunnel is actually MP2P model. And several customers require to support passive \
performance in their mobile backhaul network.
Regarding the number of labels, I agree if only the Extended special purpose label \
can be assigned, but if the normal special purpose label is assigned, then only two \
extra labels.
Best regards,
Mach
From: S. Davari [mailto:davarish@yahoo.com]
Sent: Tuesday, March 25, 2014 2:51 PM
To: Mach Chen; Shahram Davari; Yimin Shen
Cc: draft-chen-mpls-source-label@tools.ietf.org<mailto:draft-chen-mpls-source-label@tools.ietf.org>; \
mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [mpls] Mail regarding draft-chen-mpls-source-label
Hi Mach,
The draft you refer to, refers to wireless backhaul, which as far as I know, does \
not use multi-point service, and you could use normal P2P LM/DM. Regarding the number \
of labels, note that there are not many reserved labels left and as per following \
IETF draft pretty much no more reserved label can be assigned without the use of \
Extended Label Indiactor, which means you need 3 labels: XL-SLI-SL
http://tools.ietf.org/html/draft-ietf-mpls-special-purpose-labels-06
Thx
Shahram
________________________________
From: Mach Chen <mach.chen@huawei.com<mailto:mach.chen@huawei.com>>
To: Shahram Davari <davari@broadcom.com<mailto:davari@broadcom.com>>; Yimin Shen \
<yshen@juniper.net<mailto:yshen@juniper.net>>
Cc: "draft-chen-mpls-source-label@tools.ietf.org<mailto:draft-chen-mpls-source-label@tools.ietf.org>" \
<draft-chen-mpls-source-label@tools.ietf.org<mailto:draft-chen-mpls-source-label@tools.ietf.org>>; \
"mpls@ietf.org<mailto:mpls@ietf.org>" \
<mpls@ietf.org<mailto:mpls@ietf.org>>
Sent: Monday, March 24, 2014 11:12:28 PM
Subject: Re: [mpls] Mail regarding draft-chen-mpls-source-label
Hi Shahram,
Everybody knows there is SLM, but SPs need passive LM and DM in some scenarios(please \
refer to : http://tools.ietf.org/html/draft-deng-ippm-wireless-01 and RFC6374). Both \
active and passive PM have their application scenarios.
Again, to correct a mistake here, same as EL, there are only two labels needed.
Best regards,
Mach
> -----Original Message-----
> From: Shahram Davari [mailto:davari@broadcom.com<mailto:davari@broadcom.com>]
> Sent: Tuesday, March 25, 2014 11:24 AM
> To: Yimin Shen
> Cc: Mach Chen; draft-chen-mpls-source-label@tools.ietf.org<mailto:draft-chen-mpls-source-label@tools.ietf.org>; \
> mpls@ietf.org<mailto:mpls@ietf.org>
> Subject: Re: [mpls] Mail regarding draft-chen-mpls-source-label
>
> Hi
>
> So far I haven't seen any valid use car that would only be possible by adding this \
> 3 labels. For VPLS LM you could always use Synthetic loss measurement. Just
> saying Synthetic LM is not as accurate as direct LM is not a good justification for
> adding 3 labels.
>
> Regards,
> Shahram
>
>
> > On Mar 21, 2014, at 11:39 AM, "Yimin Shen" \
> > <yshen@juniper.net<mailto:yshen@juniper.net>> wrote:
> > Hi Mach,
> >
> > For an intermediate node, SL would definitely NOT be at the top of _incoming_
> label stack. You would have to install complex forwarding state in data plane to
> look for SL and process the packet differently based on the
> existence/non-existence of SL. It would get even more complicated if you need
> to put the SL back to the packets, in case other nodes downstream may also be
> expecting it. So I'd like to see a valid use case for this increased complexity and
> overhead.
> >
> > Regarding the egress node use case, note that it is different than Entropy \
> > labels,
> where an EL is actually used by intermediate nodes and only popped by egress
> node. So, if your goal is simply to inform an egress node about the identity of a
> source node, the source node could just push one label to identify itself. This
> label could be configured or communicated between the egress node and the
> source node in any fashion. However in this draft, the source node would have to
> push 3 extra labels (for SL).
> >
> > Thanks,
> >
> > /Yimin
> >
> >
> > -----Original Message-----
> > From: Mach Chen [mailto:mach.chen@huawei.com<mailto:mach.chen@huawei.com>]
> > Sent: Thursday, March 20, 2014 11:00 AM
> > To: Yimin Shen; draft-chen-mpls-source-label@tools.ietf.org<mailto:draft-chen-mpls-source-label@tools.ietf.org>;
> > mpls@ietf.org<mailto:mpls@ietf.org>
> > Subject: RE: Mail regarding draft-chen-mpls-source-label
> >
> > Hi Yimin,
> >
> > Thanks for your questions and comments!
> >
> > Please see my reply inline...
> >
> > > -----Original Message-----
> > > From: Mach Chen
> > > Sent: Thursday, March 20, 2014 10:45 PM
> > > To: Mach Chen
> > > Subject: FW: Mail regarding draft-chen-mpls-source-label
> > >
> > >
> > >
> > > From: mpls [mailto:mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org>] On \
> > > Behalf Of Yimin Shen
> > > Sent: Thursday, March 20, 2014 12:03 AM
> > > To: draft-chen-mpls-source-label@tools.ietf.org<mailto:draft-chen-mpls-source-label@tools.ietf.org>; \
> > > mpls@ietf.org<mailto:mpls@ietf.org>
> > > Subject: [mpls] Mail regarding draft-chen-mpls-source-label
> > >
> > > Hi authors,
> > >
> > > Can you please clarify if SL is expected to be used only by egress
> > > node, or by intermediate node as well ?
> >
> > The SL can be used by the egress and intermediate node, but for intermediate
> node, since the SL may not be on the top of the label stack, if it wants to use it, \
> it needs to search the label stack to find the SL, just as to find an EL.
> >
> > >
> > > Section 3.2 "Traffic Matrix Measurement and Steering" describes a use
> > > case for intermediate node, but I think congestion should in general
> > > be resolved by control plane to reroute traffic based on a global
> > > view of network resources, rather than by data plane based on a SL.
> > > In your case, would the intermediate node move the traffic to an LSP
> > > that is different than the LSP intended by the ingress node ? I don't think it \
> > > is
> the right thing to do.
> > >
> > > Regarding the use case of section 3.3 "Source Filtering". If somebody
> > > is doing DoS attack, why would he put an SL in the packets ?
> >
> > Regarding to these two use cases, as discussed with Curtis, there need more
> considerations, we will remove these two section in the next revision.
> >
> > Thanks,
> > Mach
> >
> > >
> > > Thanks,
> > >
> > > /Yimin
> >
> >
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org<mailto:mpls@ietf.org>
> > https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls
[Attachment #3 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<meta name="Generator" content="Microsoft Word 12 (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:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:??;}
@font-face
{font-family:"\@??";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"\6279\6CE8\6846\6587\672C Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Times New Roman","serif";}
span.Char
{mso-style-name:"\6279\6CE8\6846\6587\672C Char";
mso-style-priority:99;
mso-style-link:\6279\6CE8\6846\6587\672C;
font-family:??;}
p.a, li.a, div.a
{mso-style-name:?????;
mso-style-link:"????? Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.Char0
{mso-style-name:"????? Char";
mso-style-priority:99;
mso-style-link:?????;
font-family:??;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</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="ZH-CN" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D">What \
about if a route reflector is deployed?<o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:SimSun">·¢¼þÈË<span \
lang="EN-US">:</span></span></b><span lang="EN-US" \
style="font-size:10.0pt;font-family:SimSun"> mpls [mailto:mpls-bounces@ietf.org] \
</span><b><span style="font-size:10.0pt;font-family:SimSun">´ú±í </span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun">Shahram Davari<br> \
</span><b><span style="font-size:10.0pt;font-family:SimSun">·¢ËÍʱ¼ä<span \
lang="EN-US">:</span></span></b><span lang="EN-US" \
style="font-size:10.0pt;font-family:SimSun"> 2014</span><span \
style="font-size:10.0pt;font-family:SimSun">Äê<span lang="EN-US">3</span>Ô <span \
lang="EN-US">26</span>ÈÕ<span lang="EN-US"> 11:12<br>
</span><b>ÊÕ¼þÈË<span lang="EN-US">:</span></b><span lang="EN-US"> Mach Chen<br>
</span><b>³ËÍ<span lang="EN-US">:</span></b><span lang="EN-US"> \
draft-chen-mpls-source-label@tools.ietf.org; mpls@ietf.org<br> </span><b>Ö÷Ìâ<span \
lang="EN-US">:</span></b><span lang="EN-US"> Re: [mpls] Mail regarding \
draft-chen-mpls-source-label<o:p></o:p></span></span></p> </div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi Mach<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">In L3VPN you could modify the VPN label \
distribution and distribute A unique VPN label to each remote \
VRF.<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">This would solve your problem by just \
software upgrade without need for new hardware. <br> <br>
Regards, <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Shahram<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><br>
On Mar 25, 2014, at 7:33 PM, "Mach Chen" <<a \
href="mailto:mach.chen@huawei.com">mach.chen@huawei.com</a>> \
wrote:<o:p></o:p></span></p> </div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi \
Shahram</span><span lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">The \
problem is that not all the networks deploy PW to transport the service, there are \
quite number of networks use L3VPN and other techniques. </span><span \
lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Best \
regards,</span><span lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Mach</span><span \
lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US"><o:p></o:p></span></p> <div style="border:none;border-left:solid blue \
1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> \
S. Davari [<a href="mailto:davarish@yahoo.com">mailto:davarish@yahoo.com</a>] <br>
<b>Sent:</b> Tuesday, March 25, 2014 6:08 PM<br>
<b>To:</b> Mach Chen<br>
<b>Cc:</b> Shahram Davari; Yimin Shen; <a \
href="mailto:draft-chen-mpls-source-label@tools.ietf.org"> \
draft-chen-mpls-source-label@tools.ietf.org</a>; <a \
href="mailto:mpls@ietf.org">mpls@ietf.org</a><br> <b>Subject:</b> Re: [mpls] Mail \
regarding draft-chen-mpls-source-label</span><span \
lang="EN-US"><o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi Mach<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Since the service is P2P, each bas station \
has its own PW. Therefore there is no need to identify each BS using yet another \
label. <o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US"><br>
Regards,<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Shahram<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><br>
On Mar 25, 2014, at 1:32 AM, Mach Chen <<a \
href="mailto:mach.chen@huawei.com">mach.chen@huawei.com</a>> \
wrote:<o:p></o:p></span></p> </div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi \
Shahram,</span><span lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">IP/MPLS \
is commonly used in the mobile backhaul, and many of the networks use pure LDP based \
tunnel. The service is point-to-point (e.g., from CSG to RSG), but the LDP \
based tunnel is actually MP2P model. And several customers require to support passive \
performance in their mobile backhaul network.</span><span \
lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Regarding \
the number of labels, I agree if only the Extended special purpose label can be \
assigned, but if the normal special purpose label is assigned, then only two extra \
labels.</span><span lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Best \
regards,</span><span lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Mach</span><span \
lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US"><o:p></o:p></span></p> <div style="border:none;border-left:solid blue \
1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> \
S. Davari [<a href="mailto:davarish@yahoo.com">mailto:davarish@yahoo.com</a>] <br>
<b>Sent:</b> Tuesday, March 25, 2014 2:51 PM<br>
<b>To:</b> Mach Chen; Shahram Davari; Yimin Shen<br>
<b>Cc:</b> <a href="mailto:draft-chen-mpls-source-label@tools.ietf.org">draft-chen-mpls-source-label@tools.ietf.org</a>;
<a href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<b>Subject:</b> Re: [mpls] Mail regarding draft-chen-mpls-source-label</span><span \
lang="EN-US"><o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-US" \
style="color:black">Hi Mach,<br> <br>
The draft you refer to, refers to wireless backhaul, which as far as I know, \
does not use multi-point service, and you could use normal P2P LM/DM. Regarding the \
number of labels, note that there are not many reserved labels left and as per \
following IETF draft pretty much no more reserved label can be assigned without the \
use of Extended Label Indiactor, which means you need 3 labels: XL-SLI-SL<br> <br>
<a href="http://tools.ietf.org/html/draft-ietf-mpls-special-purpose-labels-06">http://tools.ietf.org/html/draft-ietf-mpls-special-purpose-labels-06</a><br>
<br>
Thx<br>
Shahram</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-US" \
style="color:black"> </span><span lang="EN-US"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-US" \
style="color:black"> </span><span lang="EN-US"><o:p></o:p></span></p> </div>
<div>
<div>
<div>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span lang="EN-US" style="color:black">
<hr size="1" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="background:white"><b><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">From:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> \
Mach Chen <<a href="mailto:mach.chen@huawei.com">mach.chen@huawei.com</a>><br> \
<b>To:</b> Shahram Davari <<a \
href="mailto:davari@broadcom.com">davari@broadcom.com</a>>; Yimin Shen <<a \
href="mailto:yshen@juniper.net">yshen@juniper.net</a>> <br>
<b>Cc:</b> "<a href="mailto:draft-chen-mpls-source-label@tools.ietf.org">draft-chen-mpls-source-label@tools.ietf.org</a>" \
<<a href="mailto:draft-chen-mpls-source-label@tools.ietf.org">draft-chen-mpls-source-label@tools.ietf.org</a>>; \
"<a href="mailto:mpls@ietf.org">mpls@ietf.org</a>" <<a \
href="mailto:mpls@ietf.org">mpls@ietf.org</a>> <br> <b>Sent:</b> Monday, March 24, \
2014 11:12:28 PM<br> <b>Subject:</b> Re: [mpls] Mail regarding \
draft-chen-mpls-source-label</span><span lang="EN-US"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-US" \
style="color:black"><br> Hi Shahram,<br>
<br>
Everybody knows there is SLM, but SPs need passive LM and DM in some scenarios(please \
refer to : <a href="http://tools.ietf.org/html/draft-deng-ippm-wireless-01" \
target="_blank"> http://tools.ietf.org/html/draft-deng-ippm-wireless-01 </a>and \
RFC6374). Both active and passive PM have their application scenarios. <br>
<br>
Again, to correct a mistake here, same as EL, there are only two labels needed. <br>
<br>
<br>
Best regards,<br>
Mach</span><span lang="EN-US"><o:p></o:p></span></p>
<div id="yqtfd46112">
<p class="MsoNormal" style="background:white"><span lang="EN-US" \
style="color:black"><br> > -----Original Message-----<br>
> From: Shahram Davari [mailto:<a \
href="mailto:davari@broadcom.com">davari@broadcom.com</a>]<br> > Sent: Tuesday, \
March 25, 2014 11:24 AM<br> > To: Yimin Shen<br>
> Cc: Mach Chen; <a \
href="mailto:draft-chen-mpls-source-label@tools.ietf.org">draft-chen-mpls-source-label@tools.ietf.org</a>;
<a href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
> Subject: Re: [mpls] Mail regarding draft-chen-mpls-source-label<br>
> <br>
> Hi<br>
> <br>
> So far I haven't seen any valid use car that would only be possible by adding \
this 3<br> > labels. For VPLS LM you could always use Synthetic loss measurement. \
Just<br> > saying Synthetic LM is not as accurate as direct LM is not a good \
justification for<br> > adding 3 labels.<br>
> <br>
> Regards,<br>
> Shahram<br>
> <br>
> <br>
> > On Mar 21, 2014, at 11:39 AM, "Yimin Shen" <<a \
href="mailto:yshen@juniper.net">yshen@juniper.net</a>> wrote:<br> > ><br>
> > Hi Mach,<br>
> ><br>
> > For an intermediate node, SL would definitely NOT be at the top of \
_incoming_<br> > label stack. You would have to install complex forwarding state \
in data plane to<br> > look for SL and process the packet differently based on \
the<br> > existence/non-existence of SL. It would get even more complicated if you \
need<br> > to put the SL back to the packets, in case other nodes downstream may \
also be<br> > expecting it. So I'd like to see a valid use case for this increased \
complexity and<br> > overhead.<br>
> ><br>
> > Regarding the egress node use case, note that it is different than Entropy \
labels,<br> > where an EL is actually used by intermediate nodes and only popped \
by egress<br> > node. So, if your goal is simply to inform an egress node about \
the identity of a<br> > source node, the source node could just push one label to \
identify itself. This<br> > label could be configured or communicated between the \
egress node and the<br> > source node in any fashion. However in this draft, the \
source node would have to<br> > push 3 extra labels (for SL).<br>
> ><br>
> > Thanks,<br>
> ><br>
> > /Yimin<br>
> ><br>
> ><br>
> > -----Original Message-----<br>
> > From: Mach Chen [mailto:<a \
href="mailto:mach.chen@huawei.com">mach.chen@huawei.com</a>]<br> > > Sent: \
Thursday, March 20, 2014 11:00 AM<br> > > To: Yimin Shen; <a \
href="mailto:draft-chen-mpls-source-label@tools.ietf.org"> \
draft-chen-mpls-source-label@tools.ietf.org</a>;<br> > > <a \
href="mailto:mpls@ietf.org">mpls@ietf.org</a><br> > > Subject: RE: Mail \
regarding draft-chen-mpls-source-label<br> > ><br>
> > Hi Yimin,<br>
> ><br>
> > Thanks for your questions and comments!<br>
> ><br>
> > Please see my reply inline...<br>
> ><br>
> >> -----Original Message-----<br>
> >> From: Mach Chen<br>
> >> Sent: Thursday, March 20, 2014 10:45 PM<br>
> >> To: Mach Chen<br>
> >> Subject: FW: Mail regarding draft-chen-mpls-source-label<br>
> >><br>
> >><br>
> >><br>
> >> From: mpls [mailto:<a \
href="mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a>] On Behalf Of Yimin \
Shen<br> > >> Sent: Thursday, March 20, 2014 12:03 AM<br>
> >> To: <a \
href="mailto:draft-chen-mpls-source-label@tools.ietf.org">draft-chen-mpls-source-label@tools.ietf.org</a>;
<a href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
> >> Subject: [mpls] Mail regarding draft-chen-mpls-source-label<br>
> >><br>
> >> Hi authors,<br>
> >><br>
> >> Can you please clarify if SL is expected to be used only by egress<br>
> >> node, or by intermediate node as well ?<br>
> ><br>
> > The SL can be used by the egress and intermediate node, but for \
intermediate<br> > node, since the SL may not be on the top of the label stack, if \
it wants to use it, it<br> > needs to search the label stack to find the SL, just \
as to find an EL.<br> > ><br>
> >><br>
> >> Section 3.2 "Traffic Matrix Measurement and Steering" \
describes a use<br> > >> case for intermediate node, but I think congestion \
should in general<br> > >> be resolved by control plane to reroute traffic \
based on a global<br> > >> view of network resources, rather than by data \
plane based on a SL.<br> > >> In your case, would the intermediate node move \
the traffic to an LSP<br> > >> that is different than the LSP intended by \
the ingress node ? I don't think it is<br> > the right thing to do.<br>
> >><br>
> >> Regarding the use case of section 3.3 "Source Filtering". If \
somebody<br> > >> is doing DoS attack, why would he put an SL in the packets \
?<br> > ><br>
> > Regarding to these two use cases, as discussed with Curtis, there need \
more<br> > considerations, we will remove these two section in the next \
revision.<br> > ><br>
> > Thanks,<br>
> > Mach<br>
> ><br>
> >><br>
> >> Thanks,<br>
> >><br>
> >> /Yimin<br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > mpls mailing list<br>
> > <a href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
> > <a href="https://www.ietf.org/mailman/listinfo/mpls" \
target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br> <br>
_______________________________________________<br>
mpls mailing list<br>
<a href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/mpls" \
target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a></span><span \
lang="EN-US"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span lang="EN-US" \
style="color:black"> </span><span lang="EN-US"><o:p></o:p></span></p> </div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
--===============2039762595306037401==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic