Re: Request for WG adoption of draft-mahesh-bfd-authentication

"Dacheng Zhang" <dacheng.zdc@alibaba-inc.com> Tue, 24 November 2015 06:26 UTC

Return-Path: <dacheng.zdc@alibaba-inc.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 450241B2E5E; Mon, 23 Nov 2015 22:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.249
X-Spam-Level:
X-Spam-Status: No, score=-0.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_CHARSET_FARAWAY=2.45, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 baASwFsnIoQO; Mon, 23 Nov 2015 22:26:19 -0800 (PST)
Received: from out4133-146.mail.aliyun.com (out4133-146.mail.aliyun.com [42.120.133.146]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3701B2E5C; Mon, 23 Nov 2015 22:26:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1448346378; h=Date:Subject:From:To:Message-ID:Mime-version:Content-type; bh=6ICLufS1ZELzvtgPjKeUhnQ8WBIZVRgwI9mOdwbnqlU=; b=uJ84vGCUV9P7udB4vIpIXS3NJLatu/hYSEECvWlMV2ThbujucZKIu8pumWM0wwATufAwWGSXJ7UJ3dxZpVGh6x44wcKDGzdMsKhqugWLTxsVgFpFLjknqnM93uptFCQrYtFZWa2ebjE+mdxioVvslsXsQSbbdlF6Euf3Cp5nREw=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R141e4; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03308; MF=dacheng.zdc@alibaba-inc.com; NM=1; PH=DS; RN=4; SR=0; TI=SMTPD_----4FIQSlc;
Received: from 10.62.54.19(mailfrom:dacheng.zdc@alibaba-inc.com ip:182.92.253.23) by smtp.aliyun-inc.com(127.0.0.1); Tue, 24 Nov 2015 14:26:15 +0800
User-Agent: Microsoft-MacOutlook/14.5.7.151005
Date: Tue, 24 Nov 2015 14:26:11 +0800
Subject: Re: Request for WG adoption of draft-mahesh-bfd-authentication
From: Dacheng Zhang <dacheng.zdc@alibaba-inc.com>
To: Marc Binderberger <marc@sniff.de>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "draft-mahesh-bfd-authentication@ietf.org" <draft-mahesh-bfd-authentication@ietf.org>
Message-ID: <D27A1EEE.300E7%dacheng.zdc@alibaba-inc.com>
Thread-Topic: Request for WG adoption of draft-mahesh-bfd-authentication
References: <D2747638.109021%rrahman@cisco.com> <20151121022956672568.a3e4948f@sniff.de>
In-Reply-To: <20151121022956672568.a3e4948f@sniff.de>
Mime-version: 1.0
Content-type: text/plain; charset="GB2312"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/XzVA-2nQeD0QeJ3HyqC2sXQxn9Y>
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: Tue, 24 Nov 2015 06:26:21 -0000

Hi,I think this is an interesting draft. It is quite common that we have
make a trade off between performance and security. Support for the
adoption. ^_^

Some comments and questions:
1) discuss which types of frames MUST be authenticated and which ones
SHOULD be authentication.
2) There is a discussion about how the sequence number should be increased
in RFC5880, maybe you could follow that one and so avoid any unnecessary
confusion.
3) Q: since in this solution, only a small number of frames need to be
authenticated, maybe we could consider again to use SHA-2 since the
influence in the performance brought by the strong algorithms will no
longer be that serious.
4) Q: do you plan to propose a negotiation mechanism for the peers to
decide the frames which should be authenticated? If not, please clarify
this part of work is out of scope.

Cheers

Dacheng

在 15-11-21 下午6:29, "Rtg-bfd on behalf of Marc Binderberger"
<rtg-bfd-bounces@ietf.org on behalf of marc@sniff.de> 写入:

>Hello Reshad and authors (and BFD experts on the list),
>
>it's a smart idea so I support the WG support ;-)
>
>But reading the document: it's at this point mainly outlining an idea and
>I 
>would expect more details to allow for interoperable implementations.
>
>
>Regards, Marc
>
>
>
>
>
>On Fri, 20 Nov 2015 12:03:25 +0000, Reshad Rahman (rrahman) wrote:
>> 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.