Re: The BFD WG has placed draft-spallagatti-bfd-vxlan in state "Call For Adoption By WG Issued"

"Acee Lindem (acee)" <acee@cisco.com> Sat, 20 January 2018 00:00 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F43012D962 for <rtg-bfd@ietfa.amsl.com>; Fri, 19 Jan 2018 16:00:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 aVj8vU9Kp7wO for <rtg-bfd@ietfa.amsl.com>; Fri, 19 Jan 2018 16:00:34 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9699F12E057 for <rtg-bfd@ietf.org>; Fri, 19 Jan 2018 16:00:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2246; q=dns/txt; s=iport; t=1516406433; x=1517616033; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=PC8JvKGV0eRvi/JPAxnrOcrBCqBuiOzTEaT0cIuh05s=; b=iMRbRXBZFdapDiiZOb2bb0ycOh+sXzaTlREKEbUAo32M7jALZ1RResiZ +GxDIWe6AmSLB17raFx/x4jqyUgPQ8/psQykxBRZlTyjrfV7X/9NoVkrZ j88fukI6MA626U3NcG4S8aYWJ/YTUVxKySZ6vw+wZkENjI8Hc313mFWq4 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAQALhmJa/5JdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNCZnQnB4NWiiSOYIIClzKCFwojhAOBFQIahEg/GAEBAQEBAQE?= =?us-ascii?q?BAWsohSQBBR0GEVUCAQgOCgICJgICAjAVEAIEARKKMxCweIInii4BAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEYBYEPgzmCFYNogwWDLwICAQGFBDGCNAWjdQKID41Hghm?= =?us-ascii?q?KNIdLjUyJRQIRGQGBOwEfOYFPbxU9KgGBf4MJgU54i0uBFwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.46,383,1511827200"; d="scan'208";a="59205725"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jan 2018 00:00:32 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id w0K00WfZ006685 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 20 Jan 2018 00:00:32 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 19 Jan 2018 19:00:31 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Fri, 19 Jan 2018 19:00:31 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: The BFD WG has placed draft-spallagatti-bfd-vxlan in state "Call For Adoption By WG Issued"
Thread-Topic: The BFD WG has placed draft-spallagatti-bfd-vxlan in state "Call For Adoption By WG Issued"
Thread-Index: AQHThKpu7hwRQo9eEkKGdW65xjeDSqN74/sA
Date: Sat, 20 Jan 2018 00:00:31 +0000
Message-ID: <607B64F7-DD73-414C-BF1C-7CCC1C2DC750@cisco.com>
References: <151386931708.12826.10490556245680582987.idtracker@ietfa.amsl.com> <20180103154925.GB5950@pfrc.org>
In-Reply-To: <20180103154925.GB5950@pfrc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5C3A003437B19846B64BE46FFF60AD55@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/WDZP7lxcJGpkA65ZFX_ywYrA41s>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jan 2018 00:00:37 -0000

Hi Jeff, 
I finally read this draft and support WG adoption (even though I’m NOT a fan of VXLAN, I realize it is a popular deployment scenario). 
Thanks,
Acee 

On 1/3/18, 10:45 AM, "Rtg-bfd on behalf of Jeffrey Haas" <rtg-bfd-bounces@ietf.org on behalf of jhaas@pfrc.org>; wrote:

    Working Group,
    
    As a reminder, we have an active adoption call for the BFD for vxlan
    document.  We've seen support for it on the list, but a few more people
    offering commentary from outside of the author's list would be helpful. :-)
    
    -- Jeff
    
    On Thu, Dec 21, 2017 at 07:15:17AM -0800, IETF Secretariat wrote:
    > The BFD WG has placed draft-spallagatti-bfd-vxlan in state
    > Call For Adoption By WG Issued (entered by Jeffrey Haas)
    > 
    > The document is available at
    > https://datatracker.ietf.org/doc/draft-spallagatti-bfd-vxlan/
    > 
    > Comment:
    > The authors of draft-spallagatti-bfd-vxlan have asked for adoption of their
    > draft by the BFD working group.  The BFD working group is chosen because the
    > document has implications on base RFC 5880 procedures.
    > 
    > Given the nature of the document, co-review and coordinated working group
    > last call with the nvo3 Working Group is expected.
    > 
    > The last date for comments for this adoption is January 20.  This extended
    > period is intended to accommodate end of year holidays.
    > 
    > A final note is that adoption is contingent upon our AD confirming this is
    > within current WG charter, or permitting us otherwise to re-charter
    > appropriately.