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

Yu Tianpeng <yutianpeng.ietf@gmail.com> Mon, 07 January 2019 23:04 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 16C7912E036 for <bess@ietfa.amsl.com>; Mon, 7 Jan 2019 15:04:11 -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 upvrv17C6ODS for <bess@ietfa.amsl.com>; Mon, 7 Jan 2019 15:04:08 -0800 (PST)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (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 DC1FC12D4ED for <bess@ietf.org>; Mon, 7 Jan 2019 15:04:07 -0800 (PST)
Received: by mail-vs1-xe36.google.com with SMTP id h78so1325715vsi.6 for <bess@ietf.org>; Mon, 07 Jan 2019 15:04:07 -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=8R3UoPCHpOIufh+8WuzZV9HJDd7MFmdQSu6fIAUou8s=; b=aLPdV4FEW2uUGFlHtw5mu9xQW4xIfzW4SWMjpbUvsBJZwBJS2PDqYwYHRxuBVuSGMB 4xuAXOMYJvBOEG+OoNfYKm3a8+uedwoONi6rl+YCegvrIb+SzkT7Gs1WDRohvKSgI2SK EE5EvshPirIfcrIwMKfRTxsgR8vvfJ6uTH3wzFvjuW6uNO5I9PVbpBTgfZbOSnkcmWr0 GfoHTNjMO7BNDV/mxOanNJxn376wuVvV1qCY9IllBaWg/GGlBlV6Heuz2fyRjBfttYy6 rjILh2mDIWIcTfHyyUn7py0HXDOGekYczx/KhYu8d5OGxgjnpO3mkBeRVPZ3BPCS3/pc Btsg==
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=8R3UoPCHpOIufh+8WuzZV9HJDd7MFmdQSu6fIAUou8s=; b=exzgv2whSdb0R54/QS9/+nGLeoSJ64oRjy2IjzKohGsfsmivaiZ7qUeSyZcQBgsYFc MxSsXQc1HYPnRqubHJaWLQ423+6Cjmua6MyJ/uvc3usQhDVxyEPOtTJaJsmQEGBsoEM3 c3TmGFkhlTN4LgfLPQC4rxYQc/NSuFZYsDabFgC3kw9LbbYdsVAHR6P/kUAyhe9M+pje 4WGgtRtKkDS5Kr705npJZHheJ5IfaKsn3VMzy6U1sZQ0iHAHCWslMdisUEEzrPnaN8jz GOuX9PvJjWeYpC1xVq0nMudmMhEUztO6Q2lJrNp12FanxEg/iiq5cJVf5HMTOQbWSL8o 1png==
X-Gm-Message-State: AA+aEWZ8A0hrUkWE0WdBH8A/T1WgQRKVpCatvCYfLsYBjc7VS5wxt2Tp J2IxBtJ56WdOMl1CKksNrXT4I60GASlC5eZUTYI=
X-Google-Smtp-Source: ALg8bN5PuLBNi1pZ4E6fx3DS6iBoTfkFgn+dsa+EaNgnXqwqXB1anKseJnTQW1OWPgGwsKpqIdbQDgptFhWQPE4sJ5k=
X-Received: by 2002:a67:3b1b:: with SMTP id i27mr25805709vsa.14.1546902246767; Mon, 07 Jan 2019 15:04:06 -0800 (PST)
MIME-Version: 1.0
References: <17128_1543833795_5C0508C3_17128_38_7_9E32478DFA9976438E7A22F69B08FF924B778825@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <14B89D6C-697A-4FED-BDAE-0FA4146FB63E@cisco.com>
In-Reply-To: <14B89D6C-697A-4FED-BDAE-0FA4146FB63E@cisco.com>
From: Yu Tianpeng <yutianpeng.ietf@gmail.com>
Date: Mon, 7 Jan 2019 23:03:55 +0000
Message-ID: <CAKFJ8eqmKpW6KmoWzRoBQagxY0F2B6D-vC1im3k0Rbb2Q=3Q8w@mail.gmail.com>
To: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>
Cc: stephane.litkowski@orange.com, bess@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ebc3d0057ee63e25"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Z9V_5RR0sWxHUXmHWu2Isw_W5SY>
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: Mon, 07 Jan 2019 23:04:11 -0000

Indeed, confused me when first read as hundreds and thousands are really
just example and no particular identification on real number an implement
should support.

On Fri, 7 Dec 2018, 16:57 Mankamana Mishra (mankamis) <mankamis@cisco.com
wrote:

> Support.
>
>
>
>
>
> But I would be happy to see some changes if WG / Author agree to it.
>
>
>
> *Nits: *
>
>    1. Please move abstract to the top. It would be easy for readers.
>    2. It might be good to add a line to describe I-SID in terminology
>    section
>
>
>
>
> 3.2
> <https://tools.ietf.org/html/draft-ietf-bess-evpn-virtual-eth-segment-00#section-3.2>.
> Scalability
>
>
>
>
>
>
>
>    (R2a) A PE MUST handle thousands or tens of thousands of Single-homed
>
>    vES's on a single physical port (e.g., single ENNI)
>
>
>
> *Comment*: These section provides number “thousands or ten thousands”. As
> a standard document, I think we can avoid using some hard code numbers.
>
> Would it be more appropriate to say “A PE MUST handle multiple
> Single-homed vES’s
>
> on a single physical port (e.g., single ENNI)
>
>
>
>
>
>    (R2b) A PE MUST handle hundreds of Single-Active vES's on a single
>
>    physical port (e.g., single ENNI)
>
> *Comment: Same as above *
>
>
>
>    (R2c) A PE MAY handle tens or hundreds of All-Active Multi-Homed
>
>    vES's on a single physical port (e.g., single ENNI)
>
> *Comment: Same as above *
>
>
>
>
>
>
>
> Thanks
>
> Mankamana
>
>
>
>
>
> *From: *BESS <bess-bounces@ietf.org> on behalf of "
> stephane.litkowski@orange.com" <stephane.litkowski@orange.com>
> *Date: *Monday, December 3, 2018 at 2:43 AM
> *To: *"bess@ietf.org" <bess@ietf.org>
> *Subject: *[bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-evpn-virtual-eth-segment
>
>
>
> 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
>