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

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Mon, 17 April 2017 23:37 UTC

Return-Path: <cpignata@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 8B982129416 for <rtg-bfd@ietfa.amsl.com>; Mon, 17 Apr 2017 16:37:27 -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 Uh16x6f0Uf2Y for <rtg-bfd@ietfa.amsl.com>; Mon, 17 Apr 2017 16:37:26 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45C24124D68 for <rtg-bfd@ietf.org>; Mon, 17 Apr 2017 16:37:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1730; q=dns/txt; s=iport; t=1492472246; x=1493681846; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=3KDC/ZhItppzaPv7thSCcvklJdHv3lJrjCEElMLU2oc=; b=GoUPNOluHPa3rnf0YAbVUjbiP4Fx5raUAlY33cHnv+GXJozvh4o0kSXp k74i+6Pr1m5nBeRfFsysfVfaIqpDf+F93pENn0bktLkwHyBD1L+x6OB/m AmB/381gvaROm9XupP2uI3g7RB0+6nVlqxYGo/44kVj3oIO4DlNVZ449n 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CbAgBWUfVY/4cNJK1cGQEBAQEBAQEBAQEBBwEBAQEBg1OBbAeDX4oVkT4hlV+CD4YkAhqDaj8YAQIBAQEBAQEBayiFFQEBAQECAR0GEToLBQsCAQgOCgICJgICAjAVEAIEDgUbiXQIqxGCJoshAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYELhUeCCAqCY4E8gxuDBi6CMQWWMoZpAZJkgX+FMIoXlAkBHziBBWMVRBEBhGApgUp1iA6BDQEBAQ
X-IronPort-AV: E=Sophos;i="5.37,217,1488844800"; d="scan'208";a="231924095"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Apr 2017 23:37:25 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v3HNbObo014526 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 17 Apr 2017 23:37:25 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 17 Apr 2017 19:37:24 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Mon, 17 Apr 2017 19:37:24 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Jeff Haas <jhaas@pfrc.org>
CC: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "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: AQHSt8GTnRQLvxEyAUuhxNZeNM1CJaHKequA
Date: Mon, 17 Apr 2017 23:37:24 +0000
Message-ID: <96131342-6E92-49B7-A14F-179F1D696E55@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:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.233.250]
Content-Type: text/plain; charset="utf-8"
Content-ID: <782601522579A947806A91F1A0E0C3D6@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/boQPnDcL7YUBm2FTaoGYKNVXOes>
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: Mon, 17 Apr 2017 23:37:27 -0000

Jeff and Reshad,

Yes, I support BFD WG adoption of draft-sonal-bfd-secure-sequence-numbers-00.

Thanks!

— Carlos.


> On Apr 17, 2017, at 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
>