Re: New Version Notification for draft-mahesh-bfd-authentication-01.txt

Jeffrey Haas <jhaas@pfrc.org> Mon, 05 October 2015 14:22 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 821941A1AC1 for <rtg-bfd@ietfa.amsl.com>; Mon, 5 Oct 2015 07:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.578
X-Spam-Level:
X-Spam-Status: No, score=-1.578 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 TpAMECPnxaLe for <rtg-bfd@ietfa.amsl.com>; Mon, 5 Oct 2015 07:22:13 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id C18341A014C for <rtg-bfd@ietf.org>; Mon, 5 Oct 2015 07:22:13 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 885261E38D; Mon, 5 Oct 2015 10:26:07 -0400 (EDT)
Date: Mon, 05 Oct 2015 10:26:07 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Subject: Re: New Version Notification for draft-mahesh-bfd-authentication-01.txt
Message-ID: <20151005142607.GE18260@pfrc.org>
References: <20150930022701.5965.79739.idtracker@ietfa.amsl.com> <D02E27D3-E349-4BD2-8AB4-2CFB2ED168B0@gmail.com> <20151002173926.GP5754@pfrc.org> <01DA576E-C388-4829-B066-608EB1785851@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <01DA576E-C388-4829-B066-608EB1785851@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/QNOq6BLPhWOP35w3kBEjxhxjbRc>
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: Mon, 05 Oct 2015 14:22:14 -0000

Mahesh,

On Fri, Oct 02, 2015 at 01:54:19PM -0700, Mahesh Jethanandani wrote:
> > A place where I think the document needs to be more proscriptive is about
> > *when* you use the more aggressive crypto.  As I was working through the
> > possible modes, it almost seems as if anything that is intended to alter the
> > BFD Control packet prior to the Authentication section is a good idea.
> 
> That is also correct. Would it help to state exactly the state transitions that will be covered by authentication?

I think this is a requirement.

> There is a question of keys that are being used for authentication and how often they are rolled over. But that is out-of-band and was (supposed to be) covered by KARP WG, and therefore out of scope of this draft.

This required the use of the crypto extensions I-D anyway.

> > What's your intention for the document?  Time to ask for adoption?
> 
> Yes, we would like a call for WG adoption of the draft. I can post an updated draft.

My suggestion will be to update the Working Group during this upcoming
session in Yokohama.  We can poll for adoption after that?

-- Jeff