Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

Yu Tianpeng <yutianpeng.ietf@gmail.com> Wed, 09 January 2019 12:03 UTC

Return-Path: <yutianpeng.ietf@gmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40A9D12F1A6 for <bess@ietfa.amsl.com>; Wed, 9 Jan 2019 04:03:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 3Rjvpb5kPJrO for <bess@ietfa.amsl.com>; Wed, 9 Jan 2019 04:03:28 -0800 (PST)
Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com [IPv6:2607:f8b0:4864:20::a2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1141127133 for <bess@ietf.org>; Wed, 9 Jan 2019 04:03:27 -0800 (PST)
Received: by mail-vk1-xa2a.google.com with SMTP id n126so1591803vke.12 for <bess@ietf.org>; Wed, 09 Jan 2019 04:03:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Z/ViWfd6gTjCc/sAy/u+fuaqu79ycVbmvsUvVetJUJA=; b=JCFae4byHJklgu8DueEKpG2UbqYjZid3RDB3myzueZ0Lvr4UcuowtacLl438Nh+OvM 7MtVNc49Sq8vsxPL/qiqxsRVGqc82Nqflld34IFJix0ZhndxDZRtnbvnybxz3bN4PAak VD/1kMrBMRzGC1HU5eYCeSrkTms4GDyT6twXXT/WePD9nAqcM9iW1ny4vJEK/xPxKVsz fwqlz3lIinO5U2yEP/WuIYDCDiSpgVjtQfLkUbfmlcqiKTViY5XqSszjMNobc7Zf4yIn xEwNoP13i7PZwIukioAt1mW94ArxoClhRyZG+GDk1ZIREbYldUZauCbNHdK1/eMff+iZ GSLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Z/ViWfd6gTjCc/sAy/u+fuaqu79ycVbmvsUvVetJUJA=; b=EaEJ9cAx81ZJ5GMzZHMuKOtug7wYjWRHrodcwM8DJZLA6FIlonbvGv4WjkAQHMC+eV l4jHFy3uhaLiwZNQ8Uum8iUbgdE4ada0ToASrIqsFraCIvpPU6JPYYYXkORrjsrx0znn omxMxBuyBCDRWBLz442CaVfzZRoONkf+KbUBv3u4OxUIOjwAkvH7VLAbsmKvhcCXH0Kf kUSg0qTmRulsDiftvJOHaQ+HPIjxls2F7gLdzojlqwlLkryXWBYGpo7Msq6J10RG7wBp D6o4imgHnprmMrqCliX3+GxNss+h4PaZDdnfv/iUcqaGYGB29e7ovZ5WktwAFhYPW2kf zZCA==
X-Gm-Message-State: AJcUukcO6VOYZ3GaPsJ9KzbLoX9WAkYXkUXhjE2Sul+A5A0Yoi5InJLe v6Lfxs4XWnTLW/2nnjO7ln3/w0eGnBlgXnfui6Y=
X-Google-Smtp-Source: ALg8bN5NJPz+09DRHWlH/NGIDmg4Ys4ob14i5vOKRoZwVA1wO/VHRP7bHV5lWbXvera4pyMiizEJuOUFvQIVA1+Fk2Q=
X-Received: by 2002:a1f:4982:: with SMTP id w124mr2069725vka.4.1547035405141; Wed, 09 Jan 2019 04:03:25 -0800 (PST)
MIME-Version: 1.0
References: <17128_1543833795_5C0508C3_17128_38_7_9E32478DFA9976438E7A22F69B08FF924B778825@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <b8a609d8-0e79-07d1-eb55-0a80076456ca@gmail.com> <C9AA0D7F-9519-41A8-8FED-5E8794492395@cisco.com> <8DE4E380-29E6-49B7-AFFD-5AA1BC460649@cisco.com>
In-Reply-To: <8DE4E380-29E6-49B7-AFFD-5AA1BC460649@cisco.com>
From: Yu Tianpeng <yutianpeng.ietf@gmail.com>
Date: Wed, 9 Jan 2019 12:03:14 +0000
Message-ID: <CAKFJ8epD=7G9GvfnziSqMx=NuUkTeeG0p1NkjvSB1_UQfaUK5A@mail.gmail.com>
To: sajassi@cisco.com
Cc: stephane.litkowski@orange.com, bess@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c74e98057f053fc7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/kpGfnrvcZB3AckGYJYC6PZ_gJ_Q>
Subject: Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2019 12:03:31 -0000

Thanks a lot Ali for the updating.
Looks fine for me apart from one point.
Correct me if I am wrong for what mentioned below.
This document aims to enable capability of evpn to be used on ENNI. But
ENNI also have EVPL, ELAN and ETREE services.  This document have a
brilliant solution, but overall current document only mentions usage in
ELAN, so the question is how about ETREE and VPWS? As the solution in this
document is vES based, I believe it should work for ETREE and VPWS without
much extra considerations.  So if authors agree, I prefer to cover this in
the current document. It is also fine for me if authors' choice is out of
scope and prefer to cover other scenarios in a separate document.

By the way another nits..
Sub type in figure 6 is not consistent with description above. I got lost
on this as previous version was still 0x04.. so if 0x07 is the correct one
please fix the value in the figure
Thanks a lot.

Regards,
Tim


On Wed, 9 Jan 2019, 00:31 Mankamana Mishra (mankamis) <mankamis@cisco.com
wrote:

> Thanks ali. I took look at the diff, it looks ok to me to move forward.
>
>
>
> Thanks
>
> Mankamana
>
>
>
>
>
> *From: *BESS <bess-bounces@ietf.org> on behalf of "Ali Sajassi (sajassi)"
> <sajassi@cisco.com>
> *Date: *Tuesday, January 8, 2019 at 3:17 PM
> *To: *Tim <yutianpeng.ietf@gmail.com>om>, "stephane.litkowski@orange.com" <
> stephane.litkowski@orange.com>gt;, "bess@ietf.org" <bess@ietf.org>
> *Subject: *Re: [bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-evpn-virtual-eth-segment
>
>
>
>
>
> Tim, Mankamana,
>
>
>
> The rev02 of the draft has the updates to address your latest comments.
>
>
>
> Cheers,
>
> Ali
>
>
>
> *From: *BESS <bess-bounces@ietf.org> on behalf of Tim <
> yutianpeng.ietf@gmail.com>
> *Date: *Monday, January 7, 2019 at 2:53 PM
> *To: *"stephane.litkowski@orange.com" <stephane.litkowski@orange.com>om>, "
> bess@ietf.org" <bess@ietf.org>
> *Subject: *Re: [bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-evpn-virtual-eth-segment
>
>
>
> Hi,
>
> Support this work as an individual. This document is a great and elegant
> step for EVPN towards SP network.
>
> Some small comments by the way:
>
> 1. Figure 2 shows the scope of EVPN network but the other figures in the
> document not. Please kindly update, then it is more readable.
>
> 2. There are 2 Figure 2
>
> 3. Document is lack of mention on E-Tree, it should work without any extra
> consideration right?
>
> 4. Please fix format issue in section 8 and update TBD in section 9.
>
> Thanks,
>
> Tim
>
>
>
> On 2018/12/3 18:43, stephane.litkowski@orange.com wrote:
>
> Hello Working Group,
>
>
>
> This email starts a two-week Working Group Last Call on
> draft-ietf-bess-evpn-virtual-eth-segment [1]
>
>
>
> This poll runs until *the 17th of December*.
>
>
>
> We are also polling for knowledge of any undisclosed IPR that applies to
> this Document, to ensure that IPR has been disclosed in compliance with
> IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
>
> If you are listed as an Author or a Contributor of this Document please
> respond to this email and indicate whether or not you are aware of any
> relevant undisclosed IPR. The Document won't progress without answers from
> all the Authors and Contributors.
>
>
>
> There is currently no IPR disclosed.
>
>
>
> If you are not listed as an Author or a Contributor, then please
> explicitly respond only if you are aware of any IPR that has not yet been
> disclosed in conformance with IETF rules.
>
>
>
> We are also polling for any existing implementation as per [2].
>
>
>
>     Thank you,
>
>     Stephane & Matthew
>
>
>
>     [1]
> https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-virtual-eth-segment/
>
>
>
>     [2]
> https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
>
>
>
>
> _________________________________________________________________________________________________________________________
>
>
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
>
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and delete this message and its attachments.
>
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>
> Thank you.
>
>
>
>
> _______________________________________________
>
> BESS mailing list
>
> BESS@ietf.org
>
> https://www.ietf.org/mailman/listinfo/bess
>
>