Re: Adoption call for draft-sonal-bfd-secure-sequence-numbers (ending April 30, 2017)

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Tue, 25 April 2017 19:55 UTC

Return-Path: <rrahman@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 8A3BC12946C for <rtg-bfd@ietfa.amsl.com>; Tue, 25 Apr 2017 12:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 4OZ0JYzYUcCO for <rtg-bfd@ietfa.amsl.com>; Tue, 25 Apr 2017 12:55:07 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C30C12943E for <rtg-bfd@ietf.org>; Tue, 25 Apr 2017 12:55:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1149; q=dns/txt; s=iport; t=1493150107; x=1494359707; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=uTlBU4tMUK4sU0jKXwR931OuPQX7N8I24czrELxqJEY=; b=lUVNGFliBXXvtBnmOBgrpiI2WTzIydOuu/To1UVQ0X7K1lkSiKNNMlnw NczNFktgxZBILiSwA4HYapgSE4Z09Uic8Y4XTawxdagIlHZirFE6GiMbR EAqW/PWiZHncgQqicDCV25QsYY+5X8ZWMu3+wdWuPdllTrhTzPc19fh8P w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DPAAAqqf9Y/4oNJK1bGQEBAQEBAQEBAQEBBwEBAQEBg1SBbQeNdadTgg+GJAKEFT8YAQIBAQEBAQEBayiFFgYdHTQLEAIBCA4oEDIlAgQBDQUbigGseYskAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZThHaBPIkAAQSdQQGTBYIAhTOKJJQYAR84gQZjFUSEdSmBSnWIKQGBDAEBAQ
X-IronPort-AV: E=Sophos;i="5.37,250,1488844800"; d="scan'208";a="414627633"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 25 Apr 2017 19:55:06 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v3PJt6uZ032377 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 25 Apr 2017 19:55:06 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 25 Apr 2017 14:55:05 -0500
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1210.000; Tue, 25 Apr 2017 14:55:05 -0500
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
CC: "Sonal Agarwal (agarwaso)" <agarwaso@cisco.com>
Subject: Re: Adoption call for draft-sonal-bfd-secure-sequence-numbers (ending April 30, 2017)
Thread-Topic: Adoption call for draft-sonal-bfd-secure-sequence-numbers (ending April 30, 2017)
Thread-Index: AQHSt8GOym0WvtZ2iE2jKJQ4DD+/I6HWnOaA
Date: Tue, 25 Apr 2017 19:55:05 +0000
Message-ID: <D5252191.284BFF%rrahman@cisco.com>
References: <20170417213533.GB18219@pfrc.org>
In-Reply-To: <20170417213533.GB18219@pfrc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [161.44.213.119]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8D265B0B91EDD9429B831F10E55CA832@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/mNv9fAHqfaGbkAX0J29NyFjfUoE>
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: Tue, 25 Apr 2017 19:55:08 -0000

Support (as individual contributor).




On 2017-04-17, 5:35 PM, "Jeffrey Haas" <jhaas@pfrc.org> wrote:

>Working Group,
>
>As part of our discussion at the Working Group session at IETF 98 in
>Chicago, Sonal Agarwal presented "Secure BFD Sequence Numbers"
>(draft-sonal-bfd-secure-sequence-numbers-00).  This work complements a
>problem space the Security area had asked us to address as part of the
>work
>on optimizing BFD authentication, our adopted
>draft-ietf-bfd-optimizing-authentication.
>
>The discussion on the implementation implictions of the optimizing
>authentication draft was energetic this last IETF.  To drive that solution
>further along, we will need a technology similar to the one in the
>proposal.
>
>This starts a 2 week adoption call for
>draft-sonal-bfd-secure-sequence-numbers.
>Please indicate your support or lack of support for the proposal to the
>mailing list.
>
>Note that part of the discussion was that optimizing BFD is not ready to
>proceed to Last CAll until we've adopted such a proposal and have
>properly integrated it into the optimization procedures.
>
>-- Jeff and Reshad