From: "Gaurav Dawra (gdawra)" <gdawra@cisco.com>
To: Martin Vigoureux <martin.vigoureux@nokia.com>, BESS <bess@ietf.org>
Thread-Topic: [bess] WG Last Call for
 draft-ietf-bess-evpn-prefix-advertisement-04
Thread-Index: AQHShkWi/+hwBIs4GEWNzmrFD4Oj16FnX1CA
Date: Mon, 13 Feb 2017 23:15:41 +0000
Message-ID: <D4C77E11.1CF269%gdawra@cisco.com>
References: <3035f4d6-163e-2f90-8462-74fa8801540b@nokia.com>
In-Reply-To: <3035f4d6-163e-2f90-8462-74fa8801540b@nokia.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.7.0.161029
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.152.11]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8DB57C6D40A6F84982B4034BE0329DFF@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/TC1gyS8o3OJVoFYugAtMO3vQB1A>
Subject: Re: [bess] WG Last Call for
 draft-ietf-bess-evpn-prefix-advertisement-04
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Feb 2017 23:15:44 -0000

Support.

Regards,

-Gaurav




On 2/13/17, 2:07 PM, "BESS on behalf of Martin Vigoureux"
<bess-bounces@ietf.org on behalf of martin.vigoureux@nokia.com> wrote:

>Hello Working Group,
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-prefix-advertisement-04 [1] which is considered
>mature and ready for a final working group review.
>Note that this call is longer than usual because we are pushing two
>correlated documents together.
>
>Please read this document if you haven't read the most recent
>version yet, and send your comments to the list, no later than
>*5th of March*.
>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 a Proposed
>Standard RFC.
>
>*Coincidentally*, we are also polling for knowledge of any IPR that
>applies to draft-ietf-bess-evpn-prefix-advertisement, 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
>draft-ietf-bess-evpn-prefix-advertisement-04 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,
>M&T
>
>[1]=20
>https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-prefix-advertisement
>/
>[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
>_______________________________________________
>BESS mailing list
>BESS@ietf.org
>https://www.ietf.org/mailman/listinfo/bess