Re: FW: New Version Notification for draft-rvelucha-bfd-offload-yang-05.txt

t petch <ietfa@btconnect.com> Thu, 13 April 2023 11:07 UTC

Return-Path: <ietfa@btconnect.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 20085C15C2BE for <rtg-bfd@ietfa.amsl.com>; Thu, 13 Apr 2023 04:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5mJk72aPFJdU for <rtg-bfd@ietfa.amsl.com>; Thu, 13 Apr 2023 04:07:33 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2072c.outbound.protection.outlook.com [IPv6:2a01:111:f400:7e1b::72c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DA19C15C2A0 for <rtg-bfd@ietf.org>; Thu, 13 Apr 2023 04:07:32 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZTcjencunk1BuXzD7PhdC1hca6nW8YS5RFre5xTZSMpOopPFm8MAh3io5HklAXNBdFtEhcezEeg+9RcSi/vOJVw1/MiSKgPO5KWiJFn7q3QYHir0ERJ7nm8DTVbTYhYRaAicOeJZEGnTkhDmIgp6iRYAfn0VeM1zwcWk9UAbnB9fQt3bRILsBNH0lAfsAK17cFV8aQF02/Pq9u/MNPBltiIlxv32D6avqndldo0r6lYtkSmc1jRkqWScYah7aXTCG1F/9ucOC+A7ZMX7yNXlyUtMUnO+RLQ5xNI9jxADLPC8tO0wZbJfV0Oa6SA3+nb42Fc29RvLTGJMNiCE5id6tA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=OrsfrniiauKmwQIUSfRmnrj2lohIp5G7UvuSTnqPSYg=; b=Ptcy2GDHgSuKMMPUrz1Gx1h2ISzRm/7vwKUp1cy/5kdPfju9e+81Hneirz7fqxbvxjsF+qaVhTZluYU90ZpsevoPXw6S3/YuaanHCS3Jktig/Y4rz3cUhP+iaAdrcBxWwVkr7On/xZz4IkmfxEMXD56KdnKBY0YeB0NNkbjtBC1Q0+ET6ha9Iyy9JMsorNfxWGnc7lBCcjV7N1x9Rh6aHTHcaDM8KTiMyxEgDHuCae+Qpkwa6xVQIC+nyOQU1HTQlJbh3J+dGEQidHxT9CoeCMcaVwOmtkrCrI++pgBFIP/D+CBcq1CYMQNDAdgXdj3VZlMs1FUUvB4v/m+EguN2gg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OrsfrniiauKmwQIUSfRmnrj2lohIp5G7UvuSTnqPSYg=; b=ivHLM1fK61GfBKeDdhGHdzfILh4nMJiOf3uSXCqozKfTcN46WsDVOCVkLWPausWqeLr7CinkTMrx0Zr++kWQMWlNet5nDc/YEEl/cBKfhtOAXVZBxwH1Ml1O2OsgxqzP0TqIcQRqIZiXA0ZZa0Tz1j7KpYeOMMg+mjMBdZDeHGc=
Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=btconnect.com;
Received: from DB7PR07MB5546.eurprd07.prod.outlook.com (2603:10a6:10:73::23) by AM7PR07MB6995.eurprd07.prod.outlook.com (2603:10a6:20b:1b6::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6298.30; Thu, 13 Apr 2023 11:07:28 +0000
Received: from DB7PR07MB5546.eurprd07.prod.outlook.com ([fe80::4265:3d58:4dba:2db4]) by DB7PR07MB5546.eurprd07.prod.outlook.com ([fe80::4265:3d58:4dba:2db4%3]) with mapi id 15.20.6277.034; Thu, 13 Apr 2023 11:07:28 +0000
Subject: Re: FW: New Version Notification for draft-rvelucha-bfd-offload-yang-05.txt
To: "Rajaguru Veluchamy (rvelucha)" <rvelucha@cisco.com>, "Rajaguru Veluchamy (rvelucha)" <rvelucha=40cisco.com@dmarc.ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
References: <168018517638.26385.151594919232783582@ietfa.amsl.com> <DM4PR11MB5294B5CEBD7D55AF6091CE87D28E9@DM4PR11MB5294.namprd11.prod.outlook.com> <6425B988.3040206@btconnect.com> <DM4PR11MB52940BD4B8305ABC32A85774D2939@DM4PR11MB5294.namprd11.prod.outlook.com> <642D3D71.4060708@btconnect.com>
Cc: "reshad@yahoo.com" <reshad@yahoo.com>
From: t petch <ietfa@btconnect.com>
Message-ID: <6437E1FB.30704@btconnect.com>
Date: Thu, 13 Apr 2023 12:05:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <642D3D71.4060708@btconnect.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: LO4P123CA0054.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:152::23) To DB7PR07MB5546.eurprd07.prod.outlook.com (2603:10a6:10:73::23)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DB7PR07MB5546:EE_|AM7PR07MB6995:EE_
X-MS-Office365-Filtering-Correlation-Id: 27793b10-5600-482f-efce-08db3c0f44df
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: w2ZL+3cjjTn/DOcb0AadK8JeLmuFl21md4MTtaE/TuUDGdRV14oh/iW4JcwInHSwDmk7iaTdM0rpTS7CRBBTT8qgbKL4+OLLFdASWKgLNGSmX7iTfOCO9U8lHK14T3hO3b8hHa0XUM7Mp6PA2stob2qwxMCzSJiSmk+o2c172DXNrwAFVAVZZ+g4MbRrLTvXQE8Ek4AxHaKn/CrP06XUtdFhjaPmn9G5L1GHYrdA8hPi/3Bej+MK+qEGw0FqDJ2IXPR+BZ8WlEYlhtx8XHl2SHY/uefdAjZ8DD7IL3kLSkjCp6r1HSXFlsSWbhEsisA0LhkSTzR9ars+KQvWyj8llvcq4TkCJnp1xDu+sAowTibjHB98uzBVgIANAJzlaBhunz/bNj2lTxzu69DAoGGRr3UdwfuplfApATsiOVmNeL8d7y1PV9kp0FVtgeIt/n3JT1pOK4iT2YmQKlBDic10e7HFEnNKzltYMCm+9n/AhA/pGJ2p+3/VAOpGV013XRaEEYaxKFQjca2llinjsdbTUjSXKBjXH3EaMV9HqPwp5nQHwhwqSynRwz1Wz2yX155i8g4KCvUaZSAYRvNFjPc8AViCRY0lIa3Nxp9Cf9efp4kKyBI8FpfHKWdyN0eBEYtjFVSqy0LnS4gJt2iTvpImqWroorcWvSmUWZ1ggQbdNEYHLWAvNryBKLB6Nznq+A3Sea/xbba9o/dVU6mmBc8mvYvio7hGFh3dJIp5urRMg/E=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB7PR07MB5546.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230028)(366004)(396003)(346002)(136003)(39860400002)(376002)(451199021)(2906002)(8676002)(33656002)(8936002)(5660300002)(66899021)(15650500001)(478600001)(6666004)(41300700001)(316002)(66946007)(82960400001)(36756003)(66476007)(83380400001)(66556008)(110136005)(4326008)(186003)(52116002)(6486002)(38350700002)(38100700002)(966005)(86362001)(26005)(6506007)(53546011)(6512007)(2616005)(66574015)(43740500002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: Mz0F8by0xY2yxmF6M6nKi+49nW3DdLFD4g+3kRiO3IOtq0hfh2yUpmhAagCKtty9QeenuYmrpmLtUZJZEl1gRIuwH2Igg6RpyIacbBjULy9N8YSqltlymWBZFmA1NXoq/38Es7yK42Ch1WEu7Ob2HTR5vZq3/rcDmmrTByfdco9EFS4kw5EnDeDFvQ0PQys9azUmdjU/1MGhtuey7SevmN/Y40WSiS+HqwQ0NzHZO/UXP3hS8abFbsBe41o+CUtcroOi5FTARNQRBops7J9g/aG+iFlzt0UNJ/8S+8LVhf2cIcxCQSBQ1tvKokUp+73bufWMCoEsJx6sfCl7qD1QJdMP8oA9whd9P5UNp9pe2tN9kdCIExOaf9xY7YHR93MgfcsDQCvjhD3xg5R7JZIspOXolgyz4KQB1H0k3UBX7G1bBdvTwE2dzb8MvrQ9xV+0af29sgfUgTYgay6Xk+j6MgOoOgNsYkw9FzkmoHRrwg04+sRwMxRviDwSlZDMrQcvrxVpyj0Gt3XQ1QC/H3XLuAg3akF64sm3HLPD84mSdsmnzCY2KOFvEqCB8XBiM7OojVFhtjxxgNhJ7cjgw25b9BEEGn40UtJtpOY54w0tdzgz5XTdGRTT3jWvBDQPfleYs0HxjgHt/GvteDcwFJ485Hz3L4ziZXITTceZtsYTocEys9OuX5WVtG0Sni/jynkf0XH18NycSG0V23S3kwak95mPKe5BTqNr2DRPfyLvRxaKLpoCiSEAvfWooenagPSaUJ6YMRT/KpqHDS2YZOO0fN/fx4FsZ7HB/84CV2uWUsCLer3oDVcXldKxDQdpYD/8UjrQ9OPbnZHbSHR6/9UJUT1J6EHJvxOwT3Y7oSof0V0jydGt9m4wXSsQECC0bx9GgytV/HjY3xeY/nRYe0Q/XS93EJ3I/3RZ9ReouH0tC/bWkpn7jJHaN0YyfbLQPx0pJT67V20Q2roGgbmiAkfeRXZfClbImozcnYFbF3wKh3KEoLrMkAppVlE9lOJcc/inpjeY7fjhGDNb/Kd3kl40avtJ41E48mSzz6IiAp3M4BQaN0Fn368hO8ks8OzTxuvMnxd39DLmAKMT71SkOux9Qmz7EFGMJVNDumJGnLasPis7xVGYOxXaB3QIPstcvH6AV+vL8VzCoftZaXX9bVR2Gf1fATd/l6QrvWRSqoOyYFL4v1xJxosduVgCJDvmMqeqIYJE3lg6/zcYuEannSaGOIrJyz3kMBDbuFGsENuDbfhGvpTrDzS7COcMQj5zCh9lplV3DTJEdvlYuZzGnFXHhNFu3BRlwXJEVpYjt7WvN34Uan6c6HrLVh0pt5SptmE2OemmN/pOFF07XQRIhiDgAuStyrQcb5iHSBEbj/INIu7naMQD0W9cYHQeuVJj4NAwC8jkxjcKokfXD5r307HSgYpygcKOAHq0+fuL4Hz0WnWe1a0WLyOU+JZJxLQA6CZANc17imWCc9NVrWEKMQSIhOzSTLNOMwVF4ivblxnN6JN9HaAp9VY4eYAWBgxcO4Vw73R+n8VSbO+HdU5W6750SI6qNnPB2dSa9N3dR/k2JBSGkGlf+fgFK44mrrgfwMN5
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 27793b10-5600-482f-efce-08db3c0f44df
X-MS-Exchange-CrossTenant-AuthSource: DB7PR07MB5546.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Apr 2023 11:07:28.3495 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 4oslZiWFx4gHxQ5fep02FX1uNRzwOx5QRGG0Dc8U4yORmssJUG4fXwTZDImq43eybqXJhBZZZzXBR1FUUAi/jg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR07MB6995
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/ASXrBoHtfJyqfCzgrZnBJTdoSGU>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 13 Apr 2023 11:07:35 -0000

Taking a step back

On 05/04/2023 10:20, t petch wrote:
> On 04/04/2023 06:20, Rajaguru Veluchamy (rvelucha) wrote:
>> Thanks, Tom for review/comments.
>>
>> Version been updated for comments. Can u please check.

How widely is bfd offload implemented by manufacturers?  I had a look at 
the Juniper website and find it refers to Distributed BFD running on the 
Packet Forwarding Engine and Centralized BFD running on the Routing 
Engine.  Is this what you mean by BFD offload?  (Searching the Juniper 
website for BFD offload generates thousands of hits none of which seem 
to be about the offloading of BFD).

Who else supports it (such as I could see in publicly available 
documentation, I am not asking for anything proprietary)?  What other 
terms are used to reference it?

I always look at the affiilations of the authors of I-D and when I see 
several different manufacturere names I am reassured (but not here:-)

Tom Petch

>> https://www.ietf.org/archive/id/draft-rvelucha-bfd-offload-yang-06.txt
>
> Mmmm, no not really.
>
> For a YANG module to exist it must be registered.  You register the name
> spaces, which looks ok, except that I think that the choice of names
> needs thinking about.
>
> You do not register the YANG modules.  This requires a reference to the
> document in which the YANG module appears with name and prefix.  Where
> this is yet to be published, the usual convention is to reference
> RFC XXXX <title of I-D>
>
> The prefix in IANA Considerations you specify do not match those in the
> YANG modules.
>
> I think the choice of names unfortunate.  Yes, these are extensions to
> the existing modules but what happens when the next extensions to these
> modules comes along?  .extext, .ext2, .next?  Better to use some
> abbreviation of what these modules are about IMHO as a suffix in the
> name and in the prefix; hardware offload, reduced to three characters
> ideally but 'hw' seems ok - I avoid the letter 'o' because of the
> numerous times it gets confused with zero but you might have a better idea.
>
> Security considerations must use the template from YANG Guidelines even
> it says there appear to be no exposures.
>
> 'contact; ' must be HTTPS: and to the datatracker not tools
>
> BSD licence is 'Revised' not 'Simplified;
>
> Fundamentally, while these are largely editorial I would oppose adoption
> until there is some reason why this should exist.  Who cares if there is
> hardware offload?  And what is the boolean for?  Can it be set and reset
> to turn hardware offload on and off or is it read only to reflect what
> the hardware is currenly up to?  I expect to learn this from the
> Introduction and perhaps from the Abstract.
>
> These thoughts were triggered by my recent experience with an up-market
> PC which refused to shutdown when I told it to and led to me pulling the
> plug from the wall.  I eventually found a customisation option which
> specified what should happen when I pressed the off button.  To me it is
> obvious what should happen when I press the off button, but seemingly
> not to leading PC manufacturers and suppliers of leading operating
> systems; they need to be told that pressing the off button is an
> instruction to power off the PC.
>
> Thus you know exactly what is meant here.  I do not:-(
>
> Tom Petch
>
>
>>
>> Regards
>> V.Rajaguru
>> XR/BFD/PI
>>
>>
>> -----Original Message-----
>> From: t petch <ietfa@btconnect.com>
>> Sent: Thursday, March 30, 2023 10:02 PM
>> To: Rajaguru Veluchamy (rvelucha)
>> <rvelucha=40cisco.com@dmarc.ietf.org>; rtg-bfd@ietf.org
>> Cc: reshad@yahoo.com; Rajaguru Veluchamy (rvelucha) <rvelucha@cisco.com>
>> Subject: Re: FW: New Version Notification for
>> draft-rvelucha-bfd-offload-yang-05.txt
>>
>> On 30/03/2023 15:09, Rajaguru Veluchamy (rvelucha) wrote:
>>> HI Team,
>>>
>>> Can we have WG adoption for this draft please.
>>>
>>> https://datatracker.ietf.org/doc/draft-rvelucha-bfd-offload-yang/
>>
>> Since it imports RFC8349, that must be a Normative Reference in
>> the7950 I-D.
>>
>> There is a template for Security Considerations in the YANG Guidelines
>> RFC which there needs to be a good reason not to follow. Those
>> guidelines drag in some more references.
>>
>> A YANG module does not exist until it is registered via IANA so the
>> IANA Considerations need supplying, registering the three modules,
>> registered the three name spaces.
>>
>> YANG would benefit from a reference, RFC7950, in the Introduction.
>>
>> The WG Web URL are out of date as are the trust URL.
>>
>> The BSD License reference is out of date.  (In fact, that reference
>> was never valid in the first place:-(
>>
>> RFC9127 gives some ideas of what is wanted.
>>
>> Tom Petch
>>
>>
>>
>>>
>>> Regards
>>> V.Rajaguru
>>> XR/BFD/PI
>>>
>>> -----Original Message-----
>>> From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
>>> <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
>>> Sent: Thursday, March 30, 2023 7:36 PM
>>> To: Rajaguru Veluchamy (rvelucha)
>>> <rvelucha@cisco.com<mailto:rvelucha@cisco.com>>; Rajaguru
>>> Veluchamy (rvelucha) <rvelucha@cisco.com<mailto:rvelucha@cisco.com>>
>>> Subject: New Version Notification for
>>> draft-rvelucha-bfd-offload-yang-05.txt
>>>
>>>
>>> A new version of I-D, draft-rvelucha-bfd-offload-yang-05.txt
>>> has been successfully submitted by RAJAGURU VELUCHAMY and posted to
>>> the IETF repository.
>>>
>>> Name:           draft-rvelucha-bfd-offload-yang
>>> Revision:       05
>>> Title:          YANG Data Model for Bidirectional Forwarding
>>> Detection (BFD) Hardware Offloaded Session
>>> Document date:  2023-03-30
>>> Group:          Individual Submission
>>> Pages:          10
>>> URL:
>>> https://www.ietf.org/archive/id/draft-rvelucha-bfd-offload-yang-05.txt
>>> Status:
>>> https://datatracker.ietf.org/doc/draft-rvelucha-bfd-offload-yang/
>>> Htmlized:
>>> https://datatracker.ietf.org/doc/html/draft-rvelucha-bfd-offload-yang
>>> Diff:
>>> https://author-tools.ietf.org/iddiff?url2=draft-rvelucha-bfd-offload-yang-05
>>>
>>>
>>> Abstract:
>>>      This document defines a extension YANG data model that can be
>>> used to
>>>      manage Hardware Offloaded Bidirectional Forwarding Detection (BFD).
>>>
>>>      This document specially talks about BFD sessions that are offloaded
>>>      to hardware.
>>>
>>>      The YANG modules in this document conform to the Network Management
>>>      Datastore Architecture (NMDA).
>>>
>>>
>>>
>>>
>>> The IETF Secretariat
>>>
>>>
>>>
>>