Re: I-D Action: draft-ietf-bfd-optimizing-authentication-06.txt

Mahesh Jethanandani <mjethanandani@gmail.com> Mon, 29 October 2018 17:33 UTC

Return-Path: <mjethanandani@gmail.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 6064F131055 for <rtg-bfd@ietfa.amsl.com>; Mon, 29 Oct 2018 10:33:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5KrNopvg2mfl for <rtg-bfd@ietfa.amsl.com>; Mon, 29 Oct 2018 10:33:42 -0700 (PDT)
Received: from mail-wm1-x344.google.com (mail-wm1-x344.google.com [IPv6:2a00:1450:4864:20::344]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 024D0131023 for <rtg-bfd@ietf.org>; Mon, 29 Oct 2018 10:33:41 -0700 (PDT)
Received: by mail-wm1-x344.google.com with SMTP id p2-v6so8779086wmc.2 for <rtg-bfd@ietf.org>; Mon, 29 Oct 2018 10:33:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=r5f8BL2uvsMK3dJy61MZiGuY2c/Wc0n2PDKAi3TvcaQ=; b=jAucRVRS6650tMha1xhbaXSiyjwqukq8AOKauzy+5B0IEcrYYK8hdJG7lTfKPyhB9n eKKDAJETw3VJTB/vahHSVbq45eF4+S6dKaCJjri1rmwl6Xn3cId5SfMDmK2f3cDaCbfO k2PsPyTu+Ro1PpN6TxZICnFFKYgH/W91dB3kQjPd8Y+NdlbNj4D3Q4vtA27SY0rTJCor SwD/3KZWbuyxCZyjA3IbPvDJHQmKTMmX8K2zkHsCOif+u7tOIyaKovk19drpJ4u/j0sh s5z6z069xbxUhyFAdZvFzjtYNFHk474v7tkHhBVzM2TTWkXCFloNpaCxQbGlIPf0xOho zcoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=r5f8BL2uvsMK3dJy61MZiGuY2c/Wc0n2PDKAi3TvcaQ=; b=O53w5XPaM4VRUBOwF9WCHocVZYyciom7txfpxtd8tegjaGfR9qR26gfpMrE0/PYq6P g4uOlStaWVuz42s+xdqvf1FBDIFc6Dzhmbq/BsXpcDgDlBmToNSqfy+CM0JgLnhGKka1 OPu3hw5eUOuPW6sJQl/NUu+brELiL8gJIWupSVLrQJK2QRbIFlLB2GZix49hAFF/DJ7C q2HJrCmQmI/N0oXv2fu6O2hViRX41Y6yCRF0q7KoHwWkMOaX2mIHRfwgwy6SUxdczj+E UDljb5csTXyrGiaYmKYqe5MKZW3yBkVelPfLbVLWXzN0e4oSIXAHN1eCVtUJvRwF2b+h lfuQ==
X-Gm-Message-State: AGRZ1gJZrrDs7/sgw/GLY1vMjBMbGHmjGLRKtWvWYu02Sg66hYBIxpeO 02ol68b/N9E729af9/rmjj0=
X-Google-Smtp-Source: AJdET5d6i/59fyuy+S993M1vWYuXlqN7W2fvllIc5K6XzUPgHkrTYOQ6SEtx4A2AIp6Aft1Acyk5SA==
X-Received: by 2002:a1c:ce0e:: with SMTP id e14-v6mr14001277wmg.45.1540834420407; Mon, 29 Oct 2018 10:33:40 -0700 (PDT)
Received: from [10.33.122.212] ([66.170.99.1]) by smtp.gmail.com with ESMTPSA id l140-v6sm28242237wmb.24.2018.10.29.10.33.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Oct 2018 10:33:39 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: I-D Action: draft-ietf-bfd-optimizing-authentication-06.txt
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <20181029161026.GO12336@pfrc.org>
Date: Mon, 29 Oct 2018 10:33:37 -0700
Cc: Greg Mirsky <gregimirsky@gmail.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E580DDD-7504-4E58-B0FC-BA18DF9CE17C@gmail.com>
References: <153930035253.7105.12758186259660848661@ietfa.amsl.com> <D4B8FC5E-7FCE-4E53-A00C-BFE1530F56FC@gmail.com> <CA+RyBmXMOJOamDDk4bJu3tvgPCRet4=1GZEZJBobrxDPxkB6jA@mail.gmail.com> <8FC1854D-DA08-48FB-A291-B293AB1464EF@gmail.com> <CA+RyBmWQ1MkAh8eAm2mYEczPGL=y9HYFMvRjj-P50JFiiqOGGA@mail.gmail.com> <20181029161026.GO12336@pfrc.org>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/IsB611lmX86slJCKp_Cc_sO6pmI>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Oct 2018 17:33:44 -0000

Hi Jeff,

> On Oct 29, 2018, at 9:10 AM, Jeffrey Haas <jhaas@pfrc.org> wrote:
> 
> Mahesh,
> 
> On Mon, Oct 15, 2018 at 09:24:59PM -0700, Greg Mirsky wrote:
>> thank you for your quick response. The comment regarding the state change,
>> as I understand from the minutes, came from Jeff.
>> Yes, the question was about the periodic authentication in Up state. I
>> believe that at the meeting WG arrived at a very good solution and we've
>> agreed to make the appropriate changes in the document. I don't think that
>> the current version reflects the WG decision that in Up state authenticated
>> BFD control packets are transmitted periodically in sets of not less than
>> Detect Multiplier.
> 
> I think the text is very close to what we'd likely want.  Here's the text in
> the current draft:
> 
> :    Most frames transmitted on a BFD session are BFD CC UP frames.
> :    Authenticating a small subset of these frames, for example, a detect
> :    multiplier number of packets per configured period, significantly
> :    reduces the computational demand for the system while maintaining
> :    security of the session across the configured authentication periods.
> 
> Given BFD procedures, I believe we'd normally want to transmit at *least*
> Detect Multiplier number of packets to ensure that the remote site has seen it.
> 
> How about the following text?
> 
> Most frames transmitted on a BFD session are BFD CC UP frames.
> Authenticating a small subset of these frames, significantly
> reduces the computational demand for the system while maintaining
> security of the session across the configured authentication periods.
> A minimum of Detect Multiplier packets MUST be transmitted per configured
> periodic authentication interval.  This ensures that the BFD session should
> see at least one authenticated packet during that interval.

Ok. Will update and post once the submission window opens up.

> 
> -- Jeff

Mahesh Jethanandani
mjethanandani@gmail.com