Hi Edward, Lamberto and all,
Sorry for the later reply. And no, when apply HSMP LSP to VPLS, the path 
from leaf PE to root PE is exactly the shortest path. mLDP leaf will send 
mapping message to root node, choosing the path with routing table, and 
this path is the shortest path from leaf to root.

We have updated the draft with more clarification of the use cases, and 
added new use case of VPLS application.
You can get the new draft from link: 
http://tools.ietf.org/html/draft-jin-jounay-mpls-mldp-hsmp-03

Thank you.
Lizhong


> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sun, 9 Jan 2011 02:50:16 +0100
> From: Lamberto Sterling <[email protected]>
> Subject: Re: [mpls] Request comments for HSMP LSP
> To: [email protected], [email protected]
> Cc: [email protected], [email protected], Ice <[email protected]>,
>    [email protected],   [email protected]
> Message-ID:
>    <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi guys,
> Sorry for the email subject. Change it now.
> 
> Lamberto
> 
> On Sat, Jan 8, 2011 at 5:19 PM, Lamberto Sterling <
> [email protected]> wrote:
> 
> > Hi Lizhong, Edward,
> > It seems that it is a good idea to apply HSMP LSP to VPLS, and the
> > broadcast/unicast/unknow packet would be optimized. However, the path 
from
> > leaf to root may not be the best path compared with current VPLS using 
P2P
> > LSP, which is not a critical issue.
> >
> > Thanks
> > Lamberto
> >
> >
> >
> >>
> >> ------------------------------
> >>
> >>
> >> Date: Wed, 5 Jan 2011 15:50:45 +0800
> >> From: [email protected]
> >> Subject: Re: [mpls] Request comments for HSMP LSP
> >> To: Ed <[email protected]>
> >> Cc: [email protected], [email protected], Ice <[email protected]>,
> >>        [email protected],   [email protected]
> >> Message-ID:
> >>        <
> >> of4ba0bf75.a883e04c-on4825780f.002802e4-4825780f.002b2...@zte.com.cn>
> >> Content-Type: text/plain; charset="us-ascii"
> >>
> >> Hi Edward,
> >> Thank you for the comments. I add l2vpn maillist in cc list. I agree 
with
> >> the application you proposed, and in order to improve the scalability 
of
> >> VPLS, P2MP PW multiplexed to HSMP LSP could be used for VPLS. 
Actually
> >> this is a good application case for P2MP PW with reverse path 
(section
> >> 4.4, draft-ietf-pwe3-p2mp-pw-00). We can add some description about 
this
> >> use case.
> >>
> >> Regards
> >> Lizhong
> >>
> >>
> >> Ed <[email protected]> wrote on 2011-01-05 15:05:30:
> >>
> >> > Hi Lizhong,
> >> >
> >> > I think one possible application for HSMP LSPs is to reduce the
> >> > overall broadcast/multicast utilization on a VPLS. In current VPLS
> >> > implementations with a full mesh of P2P LSPs between PEs, 
broadcast,
> >> > multicast and unknown traffic are not efficiently propagated on the
> >> > physical links between PEs and Ps.
> >> >
> >> > In the VPLS implementation scenario with HSMP LSPs, each PE signals
> >> > a HSMP LSP with itself as a root to all other PEs in the VPLS.
> >> > Thereafter, all broadcast/multicast/unknown traffic from this PE
> >> > will use this HSMP LSP. Unicast traffic from a particular PE (e.g.
> >> > PE1) to another PE (e.g. PE2) will be sent from leaf to root using
> >> > the HSMP LSP where PE2 is the root.
> >> >
> >> > This simplifies the VPLS implementation by:
> >> > -          Reducing traffic utilization from broadcast, multicast
> >> > and unknown traffic
> >> > -          Reducing the total number of LSPs maintained by each PE
> >> > (i.e. instead of requiring a full mesh of LSPs, now only require 
one
> >> > HSMP LSP per PE).
> >> >
> >> > This is similar to the idea expressed in  draft-key-l2vpn-etree-
> >> > frwk-03.txt (in a more general sense).
> >> >
> >> > What do you think? Would HSMP LSP be suitable for this?
> >> >
> >> > Regards,
> >> > Edward
> >> >
> >> >
> >> >
> >> > On Wed, Jan 5, 2011 at 5:24 PM, <[email protected]> wrote:
> >> >
> >> > Hi all,
> >> > During IETF 79 Beijing, we made a presentation for HSMP LSP at MPLS
> >> session.
> >> > HSMP LSP has several use cases described in the draft, e.g, time
> >> > synchronization in MPLS network, IPTV scenario, or P2MP PW. It 
would
> >> > be appreciated if you could give more scenarios for HSMP LSP. 
Please
> >> > review the draft, and any comments are welcome.
> >> >
> >> > The draft link is: 
http://tools.ietf.org/html/draft-jin-jounay-mpls-
> >> > mldp-hsmp-01
> >> >
> >> > Thank you.
> >> > Authors of draft-hsmp.
> >> > --------------------------------------------------------
> >> >
> >>
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.ietf.org/mail-
> archive/web/mpls/attachments/20110109/e5b476e5/attachment.html>
> 
> ------------------------------
> 
> _______________________________________________
> mpls mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/mpls
> 
> 
> End of mpls Digest, Vol 81, Issue 12
> ************************************
> 


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is 
solely property of the sender's organization. This mail communication is 
confidential. Recipients named above are obligated to maintain secrecy and are 
not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the originator of the 
message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________
TICTOC mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tictoc

Reply via email to