Re: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03

"Henderickx, Wim (Nokia - BE)" <> Tue, 14 February 2017 03:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CB038129463 for <>; Mon, 13 Feb 2017 19:22:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.788
X-Spam-Status: No, score=-8.788 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-1.887, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SGG3BFRkzh2Y for <>; Mon, 13 Feb 2017 19:22:25 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7A4E1129409 for <>; Mon, 13 Feb 2017 19:22:25 -0800 (PST)
Received: from (unknown []) by Websense Email Security Gateway with ESMTPS id 37D821A8EB63D for <>; Tue, 14 Feb 2017 03:22:22 +0000 (GMT)
Received: from ( []) by (GMO-o) with ESMTP id v1E3ML1L023986 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <>; Tue, 14 Feb 2017 04:22:23 +0100
Received: from ( []) by (GMO) with ESMTP id v1E3MG1Q013590 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <>; Tue, 14 Feb 2017 03:22:20 GMT
Received: from ([]) by ([]) with mapi id 14.03.0301.000; Tue, 14 Feb 2017 04:22:16 +0100
From: "Henderickx, Wim (Nokia - BE)" <>
To: "Rabadan, Jorge (Nokia - US)" <>, "Vigoureux, Martin (Nokia - FR)" <>, BESS <>
Thread-Topic: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03
Thread-Index: AQHShkbKUh6leyM+20uuv220cHnmVKFn50gA
Date: Tue, 14 Feb 2017 03:22:15 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: nl-BE, en-US
Content-Language: en-GB
user-agent: Microsoft-MacOutlook/f.1f.0.170208
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03
X-Mailman-Version: 2.1.17
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: Tue, 14 Feb 2017 03:22:28 -0000

Support doc as co-author for publication as standard RFC

On 14/02/2017, 00:15, "BESS on behalf of Rabadan, Jorge (Nokia - US)" < on behalf of> wrote:

    I support this document, as a co-author, for publication as Standard RFC.
    Not aware of any IPR.
    On 2/13/17, 11:07 PM, "BESS on behalf of Martin Vigoureux" < on behalf of> wrote:
        Hello Working Group,
        This email starts a Working Group Last Call on 
        draft-ietf-bess-evpn-inter-subnet-forwarding-03 [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-inter-subnet-forwarding, 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-inter-subnet-forwarding-03 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,
        BESS mailing list
    BESS mailing list