IETF Logo Mail Archive

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

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Tue, 25 April 2017 20:43 UTC

Return-Path: <ginsberg@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 BA2CD1292CE for <rtg-bfd@ietfa.amsl.com>; Tue, 25 Apr 2017 13:43:17 -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 shQ7n5c8i2B5 for <rtg-bfd@ietfa.amsl.com>; Tue, 25 Apr 2017 13:43:16 -0700 (PDT)
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 4F66C12709D for <rtg-bfd@ietf.org>; Tue, 25 Apr 2017 13:43:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1516; q=dns/txt; s=iport; t=1493152996; x=1494362596; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=h8/480kuil2ampJc7HAynaqCmUyA6WEd7uy8TLtnLHc=; b=WcGwedxXL3gD2GTGhoQ9TdWwnzZmtZdYmJATtnQdAw7oX07df6Y1Ld+3 dzOuYwaGbA+RQ5pdFi2uly3wsiaBqlpxXAgqgAp1m0B1rHbmOgUrr2fPo Md0cQY2R9Dl9b8sbqEZ+NoEMbkNKn1T1rPhRcnk64wB1mw8aW3C0aHJgp Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DPAAC+tP9Y/4kNJK1bGQEBAQEBAQEBAQEBBwEBAQEBg1SBbQeNdZFulWWCD4YkAoQVPxgBAgEBAQEBAQFrKIUVAQEBAQMdHTQLDAQCAQgOAwQBAR8JBzIUCQgCBAENBQgTigGsdoskAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZThHaBPIkAAQSdQQGSfIIJhTOKJJQYAR84gQZjFUSFHoFKdYgpgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.37,251,1488844800"; d="scan'208";a="416957635"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 25 Apr 2017 20:43:04 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v3PKh4qE020495 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 25 Apr 2017 20:43:04 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 25 Apr 2017 15:43:03 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Tue, 25 Apr 2017 15:43:03 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
CC: "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: AQHSt8GUD/TxZOMKzUiIHi1mn82Z1aHWmUcw
Date: Tue, 25 Apr 2017 20:43:03 +0000
Message-ID: <fe5bfbea56e64a08840a41f82c482ec2@XCH-ALN-001.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-transport-fromentityheader: Hosted
x-originating-ip: [10.32.152.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/VOqzip06_AuVqKzF7lNrJ6nkXjY>
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 20:43:18 -0000

Support - this seems a useful tool to help address security scalability in BFD.

   Les

> -----Original Message-----
> From: Rtg-bfd [mailto:rtg-bfd-bounces@ietf.org] On Behalf Of Jeffrey Haas
> Sent: Monday, April 17, 2017 2:36 PM
> To: rtg-bfd@ietf.org
> Cc: Reshad Rahman (rrahman); Sonal Agarwal (agarwaso)
> Subject: Adoption call for draft-sonal-bfd-secure-sequence-numbers (ending
> April 30, 2017)
> 
> 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

v2.23.0 | Report a Bug | By Email