Re: [netmod] 6021 ipv4-prefix

Ladislav Lhotka <lhotka@nic.cz> Thu, 02 May 2019 12:38 UTC

Return-Path: <lhotka@nic.cz>
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 982211203A0 for <netmod@ietfa.amsl.com>; Thu, 2 May 2019 05:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham 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 20x_MvS35r9m for <netmod@ietfa.amsl.com>; Thu, 2 May 2019 05:38:54 -0700 (PDT)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id B150212038A for <netmod@ietf.org>; Thu, 2 May 2019 05:38:46 -0700 (PDT)
Received: by trail.lhotka.name (Postfix, from userid 109) id BB8021820449; Thu, 2 May 2019 14:38:23 +0200 (CEST)
Received: from localhost (nat-1.nic.cz [217.31.205.1]) by trail.lhotka.name (Postfix) with ESMTPSA id 1E338182004F; Thu, 2 May 2019 14:38:20 +0200 (CEST)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Cc: netmod@ietf.org
In-Reply-To: <alpine.DEB.2.20.1905021330140.1824@uplift.swm.pp.se>
References: <0c4265d31adbf208a680f76216cc4bc42c766eae.camel@nic.cz> <959ed1a8092f4798ac0b923384962049@XCH-RCD-007.cisco.com> <20190429153643.oxfcq7ze6ttdihb4@anna.jacobs.jacobs-university.de> <alpine.DEB.2.20.1904300713100.3490@uplift.swm.pp.se> <20190430061737.vvxghxyacd57k73i@anna.jacobs.jacobs-university.de> <alpine.DEB.2.20.1904301038570.3490@uplift.swm.pp.se> <20190430090905.qsa3r4dwauilsxur@anna.jacobs.jacobs-university.de> <alpine.DEB.2.20.1905011051160.1824@uplift.swm.pp.se> <20190501111712.347bpz26br6ox3jp@anna.jacobs.jacobs-university.de> <alpine.DEB.2.20.1905011456580.1824@uplift.swm.pp.se> <20190501155321.v4qz6twsom45y62f@anna.jacobs.jacobs-university.de> <alpine.DEB.2.20.1905012137310.1824@uplift.swm.pp.se> <5CCA58DA.3030801@alumni.stanford.edu> <alpine.DEB.2.20.1905021330140.1824@uplift.swm.pp.se>
Mail-Followup-To: Mikael Abrahamsson <swmike@swm.pp.se>, Randy Presuhn <randy_presuhn@alumni.stanford.edu>, netmod@ietf.org
Date: Thu, 02 May 2019 14:38:41 +0200
Message-ID: <87v9yt58vi.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/S0h7CkwLJSGjbp7QtQog1l9Rga8>
Subject: Re: [netmod] 6021 ipv4-prefix
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 02 May 2019 12:39:05 -0000

Mikael Abrahamsson <swmike@swm.pp.se> writes:

> On Wed, 1 May 2019, Randy Presuhn wrote:
>
>> Hi -
>>
>> On 5/1/2019 12:46 PM, Mikael Abrahamsson wrote:
>> ....
>>> Where is the text that tells the server implementor whether to throw an
>>> error when client commits non-zero bits, or to just throw the bits away
>>> and store the value in the canonical format?
>>
>> Such text would be an inappropriate constraint the server's
>> internal representation.  We should only specify
>> the externally-visible behaviour: that the reported value
>> will be in the canonical format.  Whether an implementation
>> preserves extraneous cruft in its internal representation is
>> purely an implementation decision, and not subject to standardization.
>
> I am talking about what goes on the wire. If the client does an 
> edit-config with ipv6-prefix 2001:db8::1/64, should the server convert 
> this into 2001:db8::/64 or throw an error on the edit-config operation.
>
> Jurgen seems to say it should convert it and not throw an error, and I'd 
> like text to say that indeed, this is proper behaviour. Nobody has so far 
> been able to tell me where this text currently is, so that's why I'm

If we agree that a type defines the set of legal on-the-wire values
(possibly modulo representation - JSON/XML/...), then section 4.2.2.1 in
RFC 7950 says:

[A leaf instance] has exactly one value of a particular type ...

So why should a server throw an error if this is satisfied?

Lada

> asking for it to be added. Either this should go into an update to 
> https://tools.ietf.org/html/rfc7950#section-9.1 or it should go into each 
> and every definition of types (or both of them).
>
>>> It seems it should "fix it", so we should
>>> have text that reflects this.
>>
>> False dichotomy.  An implementation might actually preserve
>> those bits, though of course they'd never be seen again (at
>> least not on a netconf interface) since the netconf server
>> will always behave as though the value were in its canonical
>> form, regardless of the internal representation.
>
> Again, I am talking about what goes on the wire, what is seen when issuing 
> "get" or "edit-config" etc.
>
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67