IETF Logo Mail Archive

Re: [netmod] draft netmod charter update proposal

Ladislav Lhotka <lhotka@nic.cz> Wed, 01 March 2017 08:32 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 9EDD9129460; Wed, 1 Mar 2017 00:32:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 PoG_Cfa8IHwO; Wed, 1 Mar 2017 00:32:40 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEDE91294C9; Wed, 1 Mar 2017 00:32:39 -0800 (PST)
Received: from [IPv6:2001:718:1a02:1:ddb5:e7d5:e3da:2a2d] (unknown [IPv6:2001:718:1a02:1:ddb5:e7d5:e3da:2a2d]) by mail.nic.cz (Postfix) with ESMTPSA id 8795C66A1F; Wed, 1 Mar 2017 09:32:38 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1488357158; bh=wWSO1uEtD7v6s4ctQaMjk+9xi23z8RfVeFdKw6hHv0I=; h=From:Date:To; b=OYmB9MoSUd8GjIjhdIIXTyLNpRSDc+sasqUKQ3zZulDo48ZYW/5Xo/AMVmQp8BSaO 0Lqihn9goQ3u+uIZHJRN45u1pAglOKhu5d9YzjU8FuJoq0jEv/NGqLYkPP1PECtz9W zp+7/4ndVE49ae0ZhihUOMbqREbuzZj1beqxCJiQ=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <20170301080626.GC74969@elstar.local>
Date: Wed, 01 Mar 2017 09:32:37 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F29941EC-F118-4CCE-B295-824EC0C417CB@nic.cz>
References: <B6359563-0649-453A-B29F-28375F2BD3A4@juniper.net> <0830e87c-ee4f-bf53-2c51-96c166d3955e@cisco.com> <9A9AD440-953D-46D4-9207-97619D054912@juniper.net> <9d7b60aa-1690-c598-7034-2e430c7a8e0a@cisco.com> <3C31A53A-6818-451E-9BEF-5E568C4DCB65@juniper.net> <20170301080626.GC74969@elstar.local>
To: Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.3259)
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/jGMECRqG7LYGP3Fjx5V4I2c3xbU>
Cc: "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] draft netmod charter update proposal
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 01 Mar 2017 08:32:41 -0000

> On 1 Mar 2017, at 09:06, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> 
> On Tue, Feb 28, 2017 at 11:41:35PM +0000, Kent Watsen wrote:
>> 
>> Hi NETMOD WG,
>> 
>> Please find below draft-2 having the following changes:
>> - clarified responsibility 'c'
>> - s/encoding/representation/g
>> - moved intf-ext-yang from Oct to Dec
>> 
> 
> So are we going through all NETMOD/NETCONF documents now to replace
> 'encoding' with 'representation', which also includes changing
> document titles? I am not necessarily against that change but I think
> it is good to understand the implications that go well beyond some
> charter text. (I did do my own analysis how frequently we have used
> encoding in our documents, I assume others have done this as well.)
> 

I don't think it is necessary to immediately update old RFCs with this new term. I do think though it is important to stop using "encoding". People have to realize that

- different representations of conceptual data/resources cannot be automatically translated to each other as the term "encoding" might suggest

- it is important to think about what representation to use for a given use case (this may influence the choice of protocols and/or tools).

This terminology will also help app folks understand what we are dealing with in NETCONF/NETMOD.

Lada

> /js
> 
> PS: RFC 7951 JSON Encoding of Data Modeled with YANG. L. Lhotka. August 2016.
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

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

v2.23.0 | Report a Bug | By Email