Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

"UTTARO, JAMES" <> Mon, 12 June 2017 19:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8A11C127735 for <>; Mon, 12 Jun 2017 12:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.411
X-Spam-Status: No, score=-3.411 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XI6J4c351E9h for <>; Mon, 12 Jun 2017 12:39:47 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7F4E0127077 for <>; Mon, 12 Jun 2017 12:39:47 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id v5CJZXtj007071; Mon, 12 Jun 2017 15:39:44 -0400
Received: from ( []) by with ESMTP id 2b1xc2enux-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 12 Jun 2017 15:39:44 -0400
Received: from (localhost []) by (8.14.5/8.14.5) with ESMTP id v5CJdhKF026235; Mon, 12 Jun 2017 15:39:43 -0400
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v5CJdWoY026060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 12 Jun 2017 15:39:37 -0400
Received: from ( []) by (RSA Interceptor); Mon, 12 Jun 2017 19:39:27 GMT
Received: from ([]) by ([]) with mapi id 14.03.0319.002; Mon, 12 Jun 2017 15:39:27 -0400
From: "UTTARO, JAMES" <>
To: Senad IETF - Internet Engineering Task Force <>, Martin Vigoureux <>
Thread-Topic: [bess] WG Last Call for draft-ietf-bess-evpn-usage
Thread-Index: AQHS3s7UfY4lda8Df0Os6M6Ttg//EqIh6a6A//+/kBA=
Date: Mon, 12 Jun 2017 19:39:26 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B17A6910EEDD1F45980687268941550F2B3277E0MISOUT7MSGUSRCD_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-12_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706120343
Archived-At: <>
Subject: Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 12 Jun 2017 19:39:49 -0000

Fully support as co-author..I am not aware of any IPR related to this document..

                Jim Uttaro

From: BESS [] On Behalf Of Senad IETF - Internet Engineering Task Force
Sent: Monday, June 12, 2017 3:29 PM
To: Martin Vigoureux <>
Cc: BESS <>
Subject: Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

Full support of this document for RFC publication.  As a co-author, I am not aware of any IPR related to this document.

On Tue, Jun 6, 2017 at 10:11 AM, Martin Vigoureux <<>> wrote:
Hello Working Group,

This email starts a Working Group Last Call on draft-ietf-bess-evpn-usage-04 [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
*20th of June*.
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.

*Coincidentally*, we are also polling for knowledge of any IPR that applies to draft-ietf-bess-evpn-usage, 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-usage-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.

As opposed to the policy [2], we are not polling for knowledge of implementations as it does not seem to make sense in that case. If you feel otherwise, please let us know.

Thank you,


BESS mailing list<><>