Re: working group adoption poll for draft-mirsky-bfd-p2mp-vrrp-use-case

"Acee Lindem (acee)" <> Thu, 21 June 2018 15:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EAAF112F1A6; Thu, 21 Jun 2018 08:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Y5JUkTptoJmR; Thu, 21 Jun 2018 08:10:10 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6FD28130DE2; Thu, 21 Jun 2018 08:10:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=16634; q=dns/txt; s=iport; t=1529593809; x=1530803409; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=0p8uI5PFuHY8ld/rjFh81FT4cdxx9d7TMYkrYHi+8BU=; b=W7K7cWNtEodZ8ECoP7EYTfClmQPLVXBXn/8+YEbE4kQ/kKXDkUXOzMpZ GjIyCalcJVyWv8WbRNp4u4SKujb8NTNBMaN/ztoZSYmy8duErXD1/pOna ueTsglZ5y5jVO+AwM8GLwN06Thg4tK4/Fsr3snQlfOLoqR6r1ux3Z/oe2 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.51,252,1526342400"; d="scan'208,217";a="132244022"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Jun 2018 15:10:08 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id w5LFA8X9019170 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 21 Jun 2018 15:10:08 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 21 Jun 2018 11:10:07 -0400
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Thu, 21 Jun 2018 11:10:07 -0400
From: "Acee Lindem (acee)" <>
To: Chris Bowers <>, RTGWG <>, "" <>
Subject: Re: working group adoption poll for draft-mirsky-bfd-p2mp-vrrp-use-case
Thread-Topic: working group adoption poll for draft-mirsky-bfd-p2mp-vrrp-use-case
Date: Thu, 21 Jun 2018 15:10:07 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_8FF2E83786A3400F85C12156D1AD7290ciscocom_"
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Jun 2018 15:10:13 -0000

I support WG adoption.

From: Rtg-bfd <> on behalf of Chris Bowers <>
Date: Wednesday, June 20, 2018 at 12:46 PM
To: Routing WG <>, "" <>
Subject: working group adoption poll for draft-mirsky-bfd-p2mp-vrrp-use-case


The authors of draft-mirsky-bfd-p2mp-vrrp-use-case have requested
that RTGWG adopt this draft as a WG document.

Please indicate whether or not you support adoption of the draft
as a WG document.  An explanation of why or why not is also very helpful.

The two authors have already indicated that they know of no relevant IPR
other than what has already been disclosed. The draft has two IPR disclosures.

For some history related to this draft, please see:

For information about IPR in IETF technology, see RFC 8179.

Note that one of the basic principles regarding how the IETF deals with IPR claims (from RFC 8179)
is that: "The IETF will make no determination about the validity of any particular IPR claim."

Since Jeff Tantsura is a co-author, he will not be involved in judging consensus.

The closing date for this poll is Friday, July 6th.