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

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
>