Re: [mpls] [MPLS] Next hop address in mLDP

lizhong.jin@zte.com.cn Mon, 26 July 2010 16:27 UTC

Return-Path: <lizhong.jin@zte.com.cn>
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 2A7023A6908 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 09:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.655
X-Spam-Level:
X-Spam-Status: No, score=-102.655 tagged_above=-999 required=5 tests=[AWL=-0.817, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
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 hNXGvIvrVktW for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 09:27:15 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 4082A3A67B6 for <mpls@ietf.org>; Mon, 26 Jul 2010 09:27:14 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 3510806486374; Tue, 27 Jul 2010 00:26:51 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 96784.5546608072; Tue, 27 Jul 2010 00:19:17 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o6QGRhL9049744; Tue, 27 Jul 2010 00:27:44 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <E756ED44-CBFE-417F-BDDA-37913EAC4F8B@cisco.com>
To: IJsbrand Wijnands <ice@cisco.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF75B2DFDC.371F732E-ON4825776C.005A33A2-4825776C.005A6432@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Tue, 27 Jul 2010 00:26:33 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2010-07-27 00:27:19, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2010-07-27 00:27:19, Serialize complete at 2010-07-27 00:27:19, S/MIME Sign failed at 2010-07-27 00:27:19: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-27 00:27:25, Serialize complete at 2010-07-27 00:27:25
Content-Type: multipart/alternative; boundary="=_alternative 005A642F4825776C_="
X-MAIL: mse2.zte.com.cn o6QGRhL9049744
Cc: mpls@ietf.org
Subject: Re: [mpls] [MPLS] Next hop address in mLDP
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: Mon, 26 Jul 2010 16:27:17 -0000

Dear Ice,
Thank you for your reply. Just because I think this issue is important. 
That's great we will address this issue in the new version.

BR
Lizhong

 


IJsbrand Wijnands <ice@cisco.com> 
2010-07-27 00:11

To
lizhong.jin@zte.com.cn
cc
kireeti@juniper.net, bobthomas@alum.mit.edu, ina@juniper.net, 
mpls@ietf.org
Subject
Re: [mpls] [MPLS] Next hop address in mLDP






Hi Lizhong,

About your comment at the mic.

I guess this is the question that did not get addressed in the latest 
revision, sorry about that.

I'll discuss with the c-authors and get back to you.

Thx,

Ice.


On 18 Jun 2010, at 17:06, lizhong.jin@zte.com.cn wrote:

> Hi Ice,
> For draft-ietf-mpls-ldp-p2mp-09, on a LAN, the procedures discussed 
> supports that the upstream LSR can send a copy of the packet to each 
> receiver individually. The question is how to get the next hop address 
for 
> each receiver? There maybe the following method:
> 1. upstream LSP gets an IP address A from the downstream receiver, 
either 
> the hello packet source address or transport address;
> 2. looking up the local IP forwarding table for the address A, and check 

> if the corresponding next hop address is in the LDP session address 
list. 
> If it is, then the next hop address is found, if not, then next hop 
> address found failure.
> 
> I think some description is necessary in the draft about this.
> 
> BR
> Lizhong
> 
> 
> 
> --------------------------------------------------------
> 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.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls





--------------------------------------------------------
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.