Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

<stephane.litkowski@orange.com> Mon, 12 February 2018 08:47 UTC

Return-Path: <stephane.litkowski@orange.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 C05E3127011; Mon, 12 Feb 2018 00:47:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.629
X-Spam-Level:
X-Spam-Status: No, score=-2.629 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 eiey6z7eYHhw; Mon, 12 Feb 2018 00:47:18 -0800 (PST)
Received: from orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13701120725; Mon, 12 Feb 2018 00:47:18 -0800 (PST)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 579251C1348; Mon, 12 Feb 2018 09:47:16 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.59]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 37949180065; Mon, 12 Feb 2018 09:47:16 +0100 (CET)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c%19]) with mapi id 14.03.0382.000; Mon, 12 Feb 2018 09:47:12 +0100
From: <stephane.litkowski@orange.com>
To: LITKOWSKI Stephane OBS/OINIS <stephane.litkowski@orange.com>, "bess@ietf.org" <bess@ietf.org>, "draft-ietf-bess-evpn-ac-df.authors@ietf.org" <draft-ietf-bess-evpn-ac-df.authors@ietf.org>
Thread-Topic: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df
Thread-Index: AdOY2sLz2JVrLLhYRMyg7cHiqlyLHQLASsig
Date: Mon, 12 Feb 2018 08:47:12 +0000
Message-ID: <11934_1518425236_5A815494_11934_63_1_a03162ba-b433-4c1b-a592-8f260a16d4b2@OPEXCLILM43.corporate.adroot.infra.ftgroup>
References: <26309_1517214443_5A6EDAEB_26309_28_1_9E32478DFA9976438E7A22F69B08FF921EB33D25@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <26309_1517214443_5A6EDAEB_26309_28_1_9E32478DFA9976438E7A22F69B08FF921EB33D25@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: multipart/alternative; boundary="_000_a03162bab4334c1ba5928f260a16d4b2OPEXCLILM43corporateadr_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/NBn41tqNQnb2-fC1sL3GJkVfKHk>
Subject: Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
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, 12 Feb 2018 08:47:21 -0000

Hi Folks,

Some discussions came in about this draft during the shepherd's review and the WG last call.
As Jorge's pointed on the list, the extended community from the HRW draft (draft-ietf-bess-evpn-df-election) will be reused with some modifications:
https://mailarchive.ietf.org/arch/msg/bess/NkuEr7OPLNE01HbuLUa1x2s5k-Y

After some discussions with the authors of both drafts, I have encouraged a merge of the two proposals in a single NEW document describing the new extended community and the two first use cases (HRW for the DF type, AC-DF for the bitmap).
Authors will start working on a merged document and will issue it asap. The new draft should be published immediately as a WG document (as it comes from a merge of two existing WG documents).
The solutions will not change compared to what has already been discussed on the two drafts. As a consequence we expect to last call the new document in the coming weeks (possibly after London).

I encourage all of you to have a look on this merged document as soon as it has been published so we can close this work.

Thanks,

Stephane


From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of stephane.litkowski@orange.com
Sent: Monday, January 29, 2018 09:27
To: bess@ietf.org; draft-ietf-bess-evpn-ac-df.authors@ietf.org
Subject: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df


    Hello Working Group,



    This email starts a Working Group Last Call on

    draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and

    ready for a final working group review.



    Please read this document if you haven't read the most recent version

    yet, and send your comments to the list, no later than *12th of February*.

    Note that this is *not only* a call for comments on the document; it is

    also a call for support (or not) to publish this document as an Informational

    RFC.



    In addition, we are also polling for knowledge of any IPR that

    applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft

    please respond to this email and indicate whether or not you are aware

    of any relevant IPR.



    Note that, as of today, no IPR has been disclosed against this document

    or its earlier versions.



    We are **also polling for knowledge of implementations** of part or all

    of what this document specifies. This information is expected as per [2].

    Please inform the mailing list, or the chairs, or only one of the chairs.



    Thank you,

    Stephane & Martin



    [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-ac-df/

    [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.

_________________________________________________________________________________________________________________________

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.