Re: I-D Action: draft-ietf-l2vpn-evpn-05.txt
Zhuangshunwan <zhuangshunwan@huawei.com> Fri, 28 February 2014 08:26 UTC
Return-Path: <zhuangshunwan@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 A68771A00CB; Fri, 28 Feb 2014 00:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level:
X-Spam-Status: No,
score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 gvY8VT9h3Jux;
Fri, 28 Feb 2014 00:26:45 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by
ietfa.amsl.com (Postfix) with ESMTP id 08EA11A0017;
Fri, 28 Feb 2014 00:26:44 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com)
([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
with ESMTP id BBP37159; Fri, 28 Feb 2014 08:26:41 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by
lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server
(TLS) id 14.3.158.1; Fri, 28 Feb 2014 08:26:17 +0000
Received: from SZXEML415-HUB.china.huawei.com (10.82.67.154) by
lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server
(TLS) id 14.3.158.1; Fri, 28 Feb 2014 08:26:23 +0000
Received: from peky1z001750051 (10.111.80.111) by smtpscn.huawei.com
(10.82.67.154) with Microsoft SMTP Server (TLS) id 14.3.158.1;
Fri, 28 Feb 2014 16:26:16 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: <internet-drafts@ietf.org>, <i-d-announce@ietf.org>
References: <20140214001110.27377.41608.idtracker@ietfa.amsl.com>
In-Reply-To: <20140214001110.27377.41608.idtracker@ietfa.amsl.com>
Subject: Re: I-D Action: draft-ietf-l2vpn-evpn-05.txt
Date: Fri, 28 Feb 2014 16:26:15 +0800
Message-ID: <000401cf345e$bfc34790$3f49d6b0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac8pGVmHAvvRvDBZSmSXzfrFpcJJLALRARFw
Content-Language: zh-cn
X-Originating-IP: [10.111.80.111]
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/9dy8uiOFoDM32GRXFsc3AMM3sZY
Cc: l2vpn@ietf.org
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: Fri, 28 Feb 2014 08:26:47 -0000
Dear Authors,
I have a minor question, see inline.
8.4.1.1.1 Auto-Derivation from the Ethernet Tag ID
The following is the procedure for deriving the RT attribute
automatically from the Ethernet Tag ID associated with the
advertisement:
+ The Global Administrator field of the RT MUST
be set to the Autonomous System (AS) number that the PE
belongs to.
Vincent: Here Global Administrator field contains a 2 octets long number, but the Autonomous System (AS) number could be 4 octets, how to handle such case?
+ The Local Administrator field of the RT contains a 4
octets long number that encodes the Ethernet Tag-ID. If the
Ethernet Tag-ID is a two octet VLAN ID then it MUST be
encoded in the lower two octets of the Local Administrator
field and the higher two octets MUST be set to zero.
Regards,
Vincent
-----邮件原件-----
发件人: L2vpn [mailto:l2vpn-bounces@ietf.org] 代表 internet-drafts@ietf.org
发送时间: 2014年2月14日 8:11
收件人: i-d-announce@ietf.org
抄送: l2vpn@ietf.org
主题: I-D Action: draft-ietf-l2vpn-evpn-05.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 2 Virtual Private Networks Working Group of the IETF.
Title : BGP MPLS Based Ethernet VPN
Authors : Ali Sajassi
Rahul Aggarwal
Wim Henderickx
Aldrin Isaac
James Uttaro
Filename : draft-ietf-l2vpn-evpn-05.txt
Pages : 49
Date : 2014-02-13
Abstract:
This document describes procedures for BGP MPLS based Ethernet VPNs
(EVPN).
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-l2vpn-evpn/
There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-l2vpn-evpn-05
A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-l2vpn-evpn-05
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
- I-D Action: draft-ietf-l2vpn-evpn-05.txt internet-drafts
- RE: I-D Action: draft-ietf-l2vpn-evpn-05.txt Jakob Heitz
- Re: I-D Action: draft-ietf-l2vpn-evpn-05.txt Ali Sajassi (sajassi)
- Re: I-D Action: draft-ietf-l2vpn-evpn-05.txt Zhuangshunwan
- Re: I-D Action: draft-ietf-l2vpn-evpn-05.txt Zhuangshunwan
- Re: I-D Action: draft-ietf-l2vpn-evpn-05.txt Ali Sajassi (sajassi)
- RE: I-D Action: draft-ietf-l2vpn-evpn-05.txt Duwenhua
- FW: I-D Action: draft-ietf-l2vpn-evpn-05.txt Duwenhua
- Re: I-D Action: draft-ietf-l2vpn-evpn-05.txt Rabadan, Jorge (Jorge)
- Re: I-D Action: draft-ietf-l2vpn-evpn-05.txt Ali Sajassi (sajassi)
- RE: I-D Action: draft-ietf-l2vpn-evpn-05.txt Duwenhua