Re: Comments on Optimizing BFD Authentication

Mahesh Jethanandani <mjethanandani@gmail.com> Mon, 02 April 2018 04:06 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 837E5126CB6; Sun, 1 Apr 2018 21:06:24 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 slmKOu70n4g8; Sun, 1 Apr 2018 21:06:22 -0700 (PDT)
Received: from mail-pl0-x22c.google.com (mail-pl0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) (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 C327B126579; Sun, 1 Apr 2018 21:06:22 -0700 (PDT)
Received: by mail-pl0-x22c.google.com with SMTP id u11-v6so3420618plq.1; Sun, 01 Apr 2018 21:06:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=GZVlra22Hmo943AVWUZYG80lI7tCF9R/POz4LfEwPLM=; b=dKV7ArqBjFpKrthAuT+c8sxScquLS+60HYjn79kfN+ypgi7hl8YVm468vn3HgAATM3 i5y+DbKsjUNc3cbTwk1ggTSsqBysQ7Nu7DERWDIp9lXyQnvghhgYotK61p5vexIyke7q VCFyelLtwqE0bgP1o+GoV3E4T6zzV8QVPSCTSHXH4cNXIHJ79Gf9CSrIZJtx+HWNDBQi VfyZuhlpZe/uCbGahqS9tzhl3VSumqmHI+iKqMzvbqNBSDYTHWSgjBJh5SXg3hJ3XdA7 5cAOCYnV5w6/bnB+/IIjzW3w6dHkKWrRgoufTNwGS3ZDWi9dqgbYPEjT/vAnyzSCeK4u 6NcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=GZVlra22Hmo943AVWUZYG80lI7tCF9R/POz4LfEwPLM=; b=r6ujxH7VaAI7RvsYC5zltHU/1MJtVq/ix8GOFGQBL6ySwndyReorcQi2UBwY52yyTj ZLDJ8Q6WvU1c6hgiLL+Q6Tqz5HNaPeFrHO2/7AjGWDYqF4MKtK5HQHmXAdTHtwnaKVoN cKRWQtYA+ddC9qA2d2bjA+OwIrwMAcKNQwXnhept2gdbT2F6SaR/pY3Pc6Ynl3tbwowZ 5HOQDu7RbwOGy/5PaORm+re8G4J1En0rS2SAYe1o4sHVjeKaMAo1vGcBYM7/95r8WnZu 0bkEygS2++7cCVp1jsjahYUOzoHgsPOkp7SjduWHVsl9IeXRzbrtZYfRTO6+n3ph/8hW 08XA==
X-Gm-Message-State: AElRT7Eefp/aTUEbw0Nhl9MJmkiaBCLUVNO9sJHPj3yVH+0AUUOMS6Ts TXqp+IpWbJ/X3F8k8gW7YDU=
X-Google-Smtp-Source: AIpwx4+KI7OKdUkOo4CpRb6x+IJQKSIPNkwsDytESjwORKB1h8g/BOOdOGwaVVw8KrynY9qYU0oEYQ==
X-Received: by 2002:a17:902:ab88:: with SMTP id f8-v6mr8326457plr.34.1522641982229; Sun, 01 Apr 2018 21:06:22 -0700 (PDT)
Received: from ?IPv6:2601:647:4700:1280:483a:1ec3:e512:4540? ([2601:647:4700:1280:483a:1ec3:e512:4540]) by smtp.gmail.com with ESMTPSA id z83sm21797514pfd.31.2018.04.01.21.06.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Apr 2018 21:06:21 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <C64CA0DF-2358-4291-B393-92E1BB89DA4F@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9B4A154D-2683-4E29-A3B6-406CE2ABEFE8"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: Comments on Optimizing BFD Authentication
Date: Sun, 01 Apr 2018 21:07:45 -0700
In-Reply-To: <CAHDNOD+F0YjUaFfqR20g1DZyqUBnf1ZOhF2BuA3Nb-vue8_oKA@mail.gmail.com>
Cc: Jeffrey Haas <jhaas@pfrc.org>, draft-ietf-bfd-optimizing-authentication@ietf.org, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
To: Ashesh Mishra <mishra.ashesh@gmail.com>
References: <20180328165736.GD3126@pfrc.org> <CAHDNOD+F0YjUaFfqR20g1DZyqUBnf1ZOhF2BuA3Nb-vue8_oKA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/zhVXa-VjslZ5-Uv8Pt7iNbwcszs>
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, 02 Apr 2018 04:06:24 -0000


> On Apr 1, 2018, at 8:40 AM, Ashesh Mishra <mishra.ashesh@gmail.com> wrote:
> 
>  
>  
> What are the yang model considerations?  (See prior point.)
> 
> [AM] I'll let Mahesh comment on this. 

To support the optimized BFD authentication, we will need to change the BFD YANG model to add a ‘optimized’ authentication capability.

Following are some of the changes I anticipate

- The current model has a typedef for auth-type, but since a bit has not been assigned (it is a TBD), it will require an update to the typedef to include the new bit, when it is assigned after IANA approves it. 

- The current YANG model only supports the meticulous mode of authentication in its grouping for auth-parms. Will need to make it a choice between meticulous and the ‘optimized’ mode.


Mahesh Jethanandani
mjethanandani@gmail.com