WG adoption of draft-mahesh-bfd-authentication

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Fri, 04 December 2015 21:24 UTC

Return-Path: <rrahman@cisco.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7327D1A90BF; Fri, 4 Dec 2015 13:24:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Ary0H0rGI_XL; Fri, 4 Dec 2015 13:24:22 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA76A1A90BE; Fri, 4 Dec 2015 13:24:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9823; q=dns/txt; s=iport; t=1449264262; x=1450473862; h=from:to:cc:subject:date:message-id:mime-version; bh=YV1RDToj6O2zGJ4CMy7u8/GfeT98YhN5z35oRJX4yMc=; b=FvvVUA9n44tkl4lYeQ203N9F6eiGeU6Ev2Xkl8K9pO01erChq1Domhiv 7PfQiS+STvoF5GK1mkUOrQl3K3DRafoiSwEr6ULy9/OA1eLq93be6xRYx fqm4BC8uef/f7NOBxXjiFlWzTZwanr5w1EEclD1++EF+/xfsymE3DE4Wn k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C9AgARA2JW/4QNJK1egm5MU24GvT8OgW4hhW2BLDgUAQEBAQEBAX8LhDQBAgRuCxIBDA0DAQIoORQJCgQOBQ6IIQ3AIwEBAQEBAQEBAQEBAQEBAQEBAQERBQSGVIl4DYQzBZZhAYJggkyID4FbhEOSXYNxAR8BQ4QEcoRogQcBAQE
X-IronPort-AV: E=Sophos;i="5.20,382,1444694400"; d="scan'208,217";a="214955154"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Dec 2015 21:24:21 +0000
Received: from XCH-RTP-001.cisco.com (xch-rtp-001.cisco.com [64.101.220.141]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id tB4LOLDg026231 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 4 Dec 2015 21:24:21 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-001.cisco.com (64.101.220.141) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 4 Dec 2015 16:24:20 -0500
Received: from xch-rtp-005.cisco.com ([64.101.220.145]) by XCH-RTP-005.cisco.com ([64.101.220.145]) with mapi id 15.00.1104.009; Fri, 4 Dec 2015 16:24:20 -0500
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: "draft-mahesh-bfd-authentication@ietf.org" <draft-mahesh-bfd-authentication@ietf.org>
Subject: WG adoption of draft-mahesh-bfd-authentication
Thread-Topic: WG adoption of draft-mahesh-bfd-authentication
Thread-Index: AQHRLtojIh/kkbA/IkuhM00ajaJoAg==
Date: Fri, 04 Dec 2015 21:24:20 +0000
Message-ID: <D2876BE6.10C1BC%rrahman@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.2.150604
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.249.251]
Content-Type: multipart/mixed; boundary="_004_D2876BE610C1BCrrahmanciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/R9pH6z2dmI7_OqvDDpeBJwNv3kg>
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 04 Dec 2015 21:24:24 -0000

Hi all,

This document has passed adoption as BFD WG document.

Usual practice would be to resubmit as draft-ietf-bfd-authentication, however that could be a bit confusing. How about draft-ietf-bfd-authentication-optimization or draft-ietf-bfd-optimizing-authentication?

Regards,
Jeff & Reshad.

From: Rtg-bfd <rtg-bfd-bounces@ietf.org<mailto:rtg-bfd-bounces@ietf.org>> on behalf of Reshad <rrahman@cisco.com<mailto:rrahman@cisco.com>>
Date: Friday, November 20, 2015 at 7:03 AM
To: "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>, "draft-mahesh-bfd-authentication@ietf.org<mailto:draft-mahesh-bfd-authentication@ietf.org>" <draft-mahesh-bfd-authentication@ietf.org<mailto:draft-mahesh-bfd-authentication@ietf.org>>
Subject: Request for WG adoption of draft-mahesh-bfd-authentication

BFD WG members,

Please indicate to the WG mailing list whether you would support or not support BFD WG adoption of the following document.

https://datatracker.ietf.org/doc/draft-mahesh-bfd-authentication/

Authors, as was mentioned at IETF94, you should get your proposal reviewed by the security group.

Regards,
Jeff & Reshad.
--- Begin Message ---
The IETF WG state of draft-mahesh-bfd-authentication has been changed to
"Adopted by a WG" from "Candidate for WG Adoption" by Reshad Rahman:

https://datatracker.ietf.org/doc/draft-mahesh-bfd-authentication/


Comment:
Adopted as BFD WG doc


--- End Message ---