Re: Comments on Optimizing BFD Authentication

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Fri, 06 April 2018 12:55 UTC

Return-Path: <rrahman@cisco.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 A842512E8EC; Fri, 6 Apr 2018 05:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 y46I93yr6J93; Fri, 6 Apr 2018 05:55:34 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0648212D7ED; Fri, 6 Apr 2018 05:55:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18204; q=dns/txt; s=iport; t=1523019334; x=1524228934; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=r5E8fGWhXY0fo9e/EjIPqQ+XRG+BInB9iql0q7qe4Uo=; b=jY6Gye5zigkCCeBX3S2krYK4dm2O4LC2aSiAM57cts8LdZ/QjdQYwPkG MvFBQwBESKHobRzByra3oryuPbi6/I77Jv3cA9cbeiCCcpUh6cj0GGpFw zT8XGEFcwfc/05vzYCvwZcsYyHFEqoI225Xw6uKZzVNDH2oY9UZSCaZJT E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DtAADqbcda/5ldJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYJNdWFvKAqDVYgAjQqBdIEPhmKHEoRkgXoLhQMCGoIeITQYAQIBAQEBAQECbCiFIgEBAQEDI1YQAgEIDgMDAQIoAwICAh8RFAkIAgQBDQWEKUwDFakBghyHDg2BK4Ilh2uBVD+BDCKCYoJPgkAWgkowgiQCiAyIQIZLLAgCizSCfYEyiw6HKYIvhgcCERMBgSQBHDiBUnAVZAGCGAmQRW+MTYEXAQE
X-IronPort-AV: E=Sophos; i="5.48,415,1517875200"; d="scan'208,217"; a="95071243"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Apr 2018 12:55:33 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w36CtX5H011299 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 6 Apr 2018 12:55:33 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 6 Apr 2018 07:55:32 -0500
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1320.000; Fri, 6 Apr 2018 07:55:32 -0500
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, "Acee Lindem (acee)" <acee@cisco.com>
CC: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "draft-ietf-bfd-optimizing-authentication@ietf.org" <draft-ietf-bfd-optimizing-authentication@ietf.org>, Ashesh Mishra <mishra.ashesh@gmail.com>
Subject: Re: Comments on Optimizing BFD Authentication
Thread-Topic: Comments on Optimizing BFD Authentication
Thread-Index: AQHTxrXg7R1nLPZpF0K7q9k2GbGfCKPsZcqAgADQ6oCAAIZsAIAACr0AgAYIkYA=
Date: Fri, 06 Apr 2018 12:55:32 +0000
Message-ID: <1DB6199F-61F6-47C7-A5C7-D631ACCC53CD@cisco.com>
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> <AD2C3687-0C44-4E40-98F2-EBC7294F80CA@gmail.com>
In-Reply-To: <AD2C3687-0C44-4E40-98F2-EBC7294F80CA@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.b.0.180311
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.255.69]
Content-Type: multipart/alternative; boundary="_000_1DB6199F61F647C7A5C7D631ACCC53CDciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/-017iSjF9H0T_dM5WGIIlmB2N0Q>
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: Fri, 06 Apr 2018 12:55:38 -0000

Yes looks like we’ll have to do a bis.

Regards,
Reshad.

From: Rtg-bfd <rtg-bfd-bounces@ietf.org> on behalf of Mahesh Jethanandani <mjethanandani@gmail.com>
Date: Monday, April 2, 2018 at 8:47 AM
To: "Acee Lindem (acee)" <acee@cisco.com>
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "draft-ietf-bfd-optimizing-authentication@ietf.org" <draft-ietf-bfd-optimizing-authentication@ietf.org>, Ashesh Mishra <mishra.ashesh@gmail.com>
Subject: Re: Comments on Optimizing BFD Authentication

Acee,

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

Mahesh Jethanandani
mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>

On Apr 2, 2018, at 5:08 AM, Acee Lindem (acee) <acee@cisco.com<mailto: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<mailto:rtg-bfd-bounces@ietf.org>> on behalf of Mahesh Jethanandani <mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>>
Date: Monday, April 2, 2018 at 12:06 AM
To: Ashesh Mishra <mishra.ashesh@gmail.com<mailto:mishra.ashesh@gmail.com>>
Cc: "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>, "draft-ietf-bfd-optimizing-authentication@ietf.org<mailto:draft-ietf-bfd-optimizing-authentication@ietf.org>" <draft-ietf-bfd-optimizing-authentication@ietf.org<mailto: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<mailto: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<mailto:mjethanandani@gmail.com>