Re: [netmod] Use feature to advertise pre-nmda-support {was: WG Last Call: draft-ietf-netmod-rfc7223bis-00 ]

Randy Presuhn <randy_presuhn@alumni.stanford.edu> Fri, 01 December 2017 22:41 UTC

Return-Path: <randy_presuhn@alumni.stanford.edu>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB4A12942F for <netmod@ietfa.amsl.com>; Fri, 1 Dec 2017 14:41:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.421
X-Spam-Level:
X-Spam-Status: No, score=-1.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no autolearn_force=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 c3jYIx4mhaQx for <netmod@ietfa.amsl.com>; Fri, 1 Dec 2017 14:41:13 -0800 (PST)
Received: from mail-pl0-f67.google.com (mail-pl0-f67.google.com [209.85.160.67]) (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 A6303129434 for <netmod@ietf.org>; Fri, 1 Dec 2017 14:41:11 -0800 (PST)
Received: by mail-pl0-f67.google.com with SMTP id d21so7043133pll.1 for <netmod@ietf.org>; Fri, 01 Dec 2017 14:41:11 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=5jXnyIwrrSMgCWjGvXbPNyxv74HSlt1uLZmkUkXhDu4=; b=YqdGqicenWJUr+IzE4YJc56fIX4/CpmpbUMuWuVGgiae+vseQjjr5xI57yHB4tbtam COzJdpbHjQqUvO/mN2m45fH6EtLBzz/uCMak4/mqQiil/qZcQ001SfsEibIP8CcBAbat IFkuNgXoV0VCWoBfOTOTZC2LYB4Sr/BbOD/rg0GQ9nSa8mbOr/SvlqiUPmqtx8sVrh3e ciowWI+ogRkBkBdFfozDoLXwBfEQpMXVnoV2TLE7SJh5YwkO57eAX8+H6DkUe5lvuwAD MJWAY0kQgw0scjKbghyB1L9o6fV83ay5AjKU3IJYM7vzcXC+dZ2188sGLQLaRGFN1Rl9 MVDQ==
X-Gm-Message-State: AJaThX7+Qsl+tMI5B2L90TpUXU4RX9s7BCGs8AaBN+z+WWOc4s+RqboP GaAqtTYwaHs0q95Cyo/ur/Qd3UxiB4U=
X-Google-Smtp-Source: AGs4zMYFRtytgYDV6niGmKLbHY7f0eb6UzxsgHg9euqWhdRfGNGe5xSUgdVEpTJLMoIcgZCrGdiQDg==
X-Received: by 10.84.238.140 with SMTP id v12mr7490254plk.356.1512168070742; Fri, 01 Dec 2017 14:41:10 -0800 (PST)
Received: from [192.168.1.101] (c-24-130-218-233.hsd1.ca.comcast.net. [24.130.218.233]) by smtp.gmail.com with ESMTPSA id f9sm11766548pgv.8.2017.12.01.14.41.09 for <netmod@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Dec 2017 14:41:10 -0800 (PST)
To: netmod@ietf.org
References: <10B5698A-BC7B-432E-A931-9069FA7BB03C@juniper.net> <926aa462-7e5a-350f-bc56-46b9ea2ac6b3@ericsson.com>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <3abeb1c3-68e8-a781-ed66-dace8084fa0a@alumni.stanford.edu>
Date: Fri, 01 Dec 2017 14:41:07 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <926aa462-7e5a-350f-bc56-46b9ea2ac6b3@ericsson.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/H6WYE4JRrKfffcqstYKhLQyvzzk>
Subject: Re: [netmod] Use feature to advertise pre-nmda-support {was: WG Last Call: draft-ietf-netmod-rfc7223bis-00 ]
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Dec 2017 22:41:14 -0000

Hi -

On 12/1/2017 3:37 AM, Balazs Lengyel wrote:
> Hello,
> 
> https://tools.ietf.org/html/rfc7950#section-7.21.2
> 
>     o  "deprecated" indicates an obsolete definition, but it permits
>        new/continued implementation in order to foster interoperability
>        with older/existing implementations.
> 
> This means that a node that is deprecated MAY or MAY NOT be implemented.
> YANG is considered an interface contract,  however "maybe implemented" 
> is unusable in a contract.

 From a client perspective, access control can have similar consequences.
A contract only outlines some of the kinds of things that
might possibly exist.  It doesn't tell you what's actually there or
whether you're allowed to do anything with them.

Randy