IETF Logo Mail Archive

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

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Mon, 24 April 2017 13:47 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 03D26131539 for <rtg-bfd@ietfa.amsl.com>; Mon, 24 Apr 2017 06:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 DWwS4flxk5vE for <rtg-bfd@ietfa.amsl.com>; Mon, 24 Apr 2017 06:47:28 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 369AD131531 for <rtg-bfd@ietf.org>; Mon, 24 Apr 2017 06:47:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8825; q=dns/txt; s=iport; t=1493041647; x=1494251247; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=DciyYOyMB24l88Flo4PrTj7qQlArLOVM+X9cfyognRk=; b=BZNvZVT65Fj7Kzmwpkcxx66VtvajDA9MBNq4mMB+BhKt7U/++TbYAo5a NZPLXeJkWxgIpw9a27hs7sy+M5idGYfO4h21wHffNl4ETzzkbds0f6idb lSmyKx6RimSHBMUB51UxBJRIchWZkda9wqDPyjHlSF8cgyTSo8Hbk0dfv Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BsAQCVAf5Y/4YNJK1bGQEBAQEBAQEBAQEBBwEBAQEBgm47K4FtB4NgihWRaII8hWSIEIU1gg+GJAIag3E/GAECAQEBAQEBAWsohRUBAQEBAx1RCxACAQYCEQMBAigFAgIwEwEGAwgCBAENBRuJaQMVjU2dWAiCJIsbAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZThHaBPIEVgh0JgmKCYwWHXQyBUYQ0iFuGPTsBjkKEQ4IAhTOFKIR8ixKJBgEfOIEGYxVEhGgNEBkZgTF1iCmBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.37,244,1488844800"; d="scan'208,217";a="240436435"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Apr 2017 13:47:27 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v3ODlRFD009576 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 24 Apr 2017 13:47:27 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 24 Apr 2017 08:47:26 -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; Mon, 24 Apr 2017 08:47:26 -0500
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: LuHuang <hlisname@yahoo.com>, Jeffrey Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, Mahesh Jethanandani <mjethanandani@gmail.com>
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+/I6HKqBaAgAn7twA=
Date: Mon, 24 Apr 2017 13:47:26 +0000
Message-ID: <D5237347.2840C9%rrahman@cisco.com>
References: <20170417213533.GB18219@pfrc.org> <638481980.2346797.1492478397080@mail.yahoo.com>
In-Reply-To: <638481980.2346797.1492478397080@mail.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.8.160830
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.248.73]
Content-Type: multipart/alternative; boundary="_000_D52373472840C9rrahmanciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/8pSwGdTxCBhfFdLqPJrVsH6RWU0>
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, 24 Apr 2017 13:47:30 -0000

Mahesh, should that be added to draft-ietf-bfd-optimizing-authentication?

From: Rtg-bfd <rtg-bfd-bounces@ietf.org<mailto:rtg-bfd-bounces@ietf.org>> on behalf of LuHuang <hlisname@yahoo.com<mailto:hlisname@yahoo.com>>
Reply-To: LuHuang <hlisname@yahoo.com<mailto:hlisname@yahoo.com>>
Date: Monday, April 17, 2017 at 9:19 PM
To: Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>, "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>
Cc: Reshad <rrahman@cisco.com<mailto:rrahman@cisco.com>>, "Sonal Agarwal (agarwaso)" <agarwaso@cisco.com<mailto:agarwaso@cisco.com>>
Subject: 回复： Adoption call for draft-sonal-bfd-secure-sequence-numbers (ending April 30, 2017)

Yes./ support

But I think one problem should be considered. If packet loss happens, the sequence number of received packet won't be the expected number or hash value, which should be distinguished from malicious packet.

Thanks.

--------------------
LuHuang
China Mobile Research Institute
Mobile: +86 13810820540


Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>> 于 2017年4月18日, 星期二, 上午 5:28 写道：


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