Re: Comments on Optimizing BFD Authentication

Mahesh Jethanandani <mjethanandani@gmail.com> Mon, 02 April 2018 12:47 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 F2C691275AB; Mon, 2 Apr 2018 05:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, MIME_QP_LONG_LINE=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 jhgPuln6NFBP; Mon, 2 Apr 2018 05:47:21 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 17C72124D37; Mon, 2 Apr 2018 05:47:21 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id l27so9443435pfk.12; Mon, 02 Apr 2018 05:47:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:mime-version:in-reply-to:content-transfer-encoding :message-id:cc:from:subject:date:to; bh=q6Z7+sFAck15vF57meNR4+ou9rwIbGoDbSQtOl62PmE=; b=ZRcRotBonZ9d8O8zLQXmWXEEfanvcQ6CzPWu2IX+q6n21azlSfNp7jTxw3TmRA35vc aS26e7Hjwa2MMkjA8p3YmLv3VkHU2VcYY+WKRDQBexj6goQr0AkCxD0Rw9D1XTvkQWeD kCwJiYuLAwWkI9MVk0oKnTfQ39xOaJ8Cd7TCOKHKro+5dcpzo7sY53S0z8j4P4DpiR0R 2nCCsR1mCH1MHYu4dEb8RjPP6WDkW0Qe7y7A9UTCOkG2amD1LTuSl7r0frt6H11LEBYw /EsrrmDoiDCx81BVMJgxteAy04wDCxZZrHV6PiLSJS3TfCYT7D/Ewg9i/hA8gfdXd/ta vwKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:mime-version:in-reply-to :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=q6Z7+sFAck15vF57meNR4+ou9rwIbGoDbSQtOl62PmE=; b=bA5t5SS2UMg6YnJh2JkwFufVdZSBPa059qhuPikbDlGqtsFLK7kQrW+YbmdYKh6FPE 1IU+6NBJ0A0+mKo2A31jYQeiIxF1l5xEeZE+ZSfarhE6YE8JYQv2v+l6GUP8fzaTD82e KccdO9uo5Ssn2Xc84TJYKUG2D+rJ0LR4nKvozJixbZGgZHILHhPST+2juGtSuoGcNzZz MVRaVQaDMtXxiWxJfa7CwxwrljxOA2MNDwsJ+VyXf/cId+zdDpxf/yjGrKEUIiEn5eIc fxMipWWtQTt2KHPRB474UinjEB+CyXX/Fu2y0nBUuEs0quLvkAlfyVCkcondgox6U+TP fJcg==
X-Gm-Message-State: AElRT7FPouPCE7aY5Z9hrNi6+F1QCCrbcUcdmWDpsdLRU6cITRlI2S+t GzMO8vkyOPboRMXH8QVBciPT+SYJ
X-Google-Smtp-Source: AIpwx49XLiKcuisspamFDZpiOryBCv+m9jpcucn1Q1dnnM+SEI0ZQMI5DQ/Z10vzP8T/a+nybuRUBA==
X-Received: by 10.98.137.218 with SMTP id n87mr7376934pfk.48.1522673240564; Mon, 02 Apr 2018 05:47:20 -0700 (PDT)
Received: from [192.168.1.108] (c-24-6-191-201.hsd1.ca.comcast.net. [24.6.191.201]) by smtp.gmail.com with ESMTPSA id h15sm742548pfi.56.2018.04.02.05.47.19 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 02 Apr 2018 05:47:19 -0700 (PDT)
References: <20180328165736.GD3126@pfrc.org> <CAHDNOD+F0YjUaFfqR20g1DZyqUBnf1ZOhF2BuA3Nb-vue8_oKA@mail.gmail.com> <C64CA0DF-2358-4291-B393-92E1BB89DA4F@gmail.com> <D08326D2-2515-4348-982A-159971BBE5E7@cisco.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <D08326D2-2515-4348-982A-159971BBE5E7@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-43E22E4D-F6EA-4E55-AA78-8B20C963947E"
Content-Transfer-Encoding: 7bit
Message-Id: <AD2C3687-0C44-4E40-98F2-EBC7294F80CA@gmail.com>
Cc: Ashesh Mishra <mishra.ashesh@gmail.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "draft-ietf-bfd-optimizing-authentication@ietf.org" <draft-ietf-bfd-optimizing-authentication@ietf.org>
X-Mailer: iPad Mail (13G36)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Subject: Re: Comments on Optimizing BFD Authentication
Date: Mon, 02 Apr 2018 05:47:18 -0700
To: "Acee Lindem (acee)" <acee@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/fFRtbTgIJgP4p0rJhUrdSouUZuA>
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 12:47:23 -0000

Acee,

Or by doing a "bis" version of the draft. There is no way to augment a typedef.

Mahesh Jethanandani
mjethanandani@gmail.com

> On Apr 2, 2018, at 5:08 AM, Acee Lindem (acee) <acee@cisco.com> wrote:
> 
> Mahesh – I believe these should be done as augmentations since draft-ietf-bfd-yang-13 has already been submitted to the IESG for publication.
> Thanks,
> Acee
>  
> From: Rtg-bfd <rtg-bfd-bounces@ietf.org> on behalf of Mahesh Jethanandani <mjethanandani@gmail.com>
> Date: Monday, April 2, 2018 at 12:06 AM
> To: Ashesh Mishra <mishra.ashesh@gmail.com>
> Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "draft-ietf-bfd-optimizing-authentication@ietf.org" <draft-ietf-bfd-optimizing-authentication@ietf.org>
> Subject: Re: Comments on Optimizing BFD Authentication
>  
>  
> 
> 
> 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
> 
>