IETF Logo Mail Archive

Comments on draft-rabadan-l2vpn-evpn-optimized-ir-00

Lizhenbin <lizhenbin@huawei.com> Wed, 23 July 2014 17:09 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 354FC1A012D for <l2vpn@ietfa.amsl.com>; Wed, 23 Jul 2014 10:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xu2Nui4164KD for <l2vpn@ietfa.amsl.com>; Wed, 23 Jul 2014 10:09:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE0CC1A014C for <l2vpn@ietf.org>; Wed, 23 Jul 2014 10:09:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BHN42599; Wed, 23 Jul 2014 17:09:46 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 23 Jul 2014 18:09:45 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.24]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Thu, 24 Jul 2014 01:09:42 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: Comments on draft-rabadan-l2vpn-evpn-optimized-ir-00
Thread-Topic: Comments on draft-rabadan-l2vpn-evpn-optimized-ir-00
Thread-Index: Ac+mmOTptQd6Jw02TRqHpyl41wju0Q==
Date: Wed, 23 Jul 2014 17:09:42 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D08232A5D@nkgeml506-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.216.44.158]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D08232A5Dnkgeml506mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/2OpvS-_9ivROpeJyL8za6RVKpfE
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jul 2014 17:09:50 -0000

Hi authors,

To follow up on my comments in the l2vpn meeting, following two drafts proposed in L2VPN WG and L3VPN WG are for your reference:

-- draft-li-l3vpn-mvpn-role-state-ad-02
-- draft-zhang-l2vpn-evpn-selective-mcast-01
The role information is truly a possible way to help optimize the BUM traffic in EVPN. Regarding the possible solutions, I have following more comments:

-- It is better to work out a generic role-info advertisement solutions based on all possible application scenarios.

-- Taking into account compatibility, it is better to define a new route type for NLRI or a new attribute to advertis the role information. The extension of PMSI Tunnel attribute may proposes compatibility issue for BGP-based MVPN defined in RFC 6514.





Regards,

Zhenbin(Robin)

v2.8.7 | Report a Bug | By Email