Re: [netmod] Alexey Melnikov's No Objection on draft-ietf-netmod-yang-data-ext-04: (with COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Tue, 22 October 2019 07:35 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 43E2212008C; Tue, 22 Oct 2019 00:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=X9lmmB01; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=L5pz8UAG
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 cQ6eQfcpNGgp; Tue, 22 Oct 2019 00:35:12 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57FBD12002F; Tue, 22 Oct 2019 00:35:12 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5F3AD21448; Tue, 22 Oct 2019 03:35:10 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Tue, 22 Oct 2019 03:35:10 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=K U6dGkkrnlRTfpVkEFN0vN5H8wlqVqacOFq5tRAft9c=; b=X9lmmB01qbjVxDvR+ EKfYtpThFfldo+4ZJvXeoQGUNP51Wxq/MXYzf+qz682nqCJ06Je7Or5eSVr17yVR Vkc0nksAtTZ411vfMVeDORmMDtk+MyZFybFT/b9kw0GaZjVj6NuTpPHHnsogoVxz rZGBIwzSBgHQkFrStmFKjptcF8y7oNQ2NXceytwtdIHWeSY9o5tQwnK2WU3a9fIV JPe4NpY+7auVX4vnPvMPyn+EeZDUzb5eDls6BT52zalY2jhQJ91sx9eYHpIHI6ad l2s4fncEX8HkRSRnbehFbA7gui7z3dLue+mDVEQPiwPTyIs5PXMmZ517b45CXcYs niO3g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=KU6dGkkrnlRTfpVkEFN0vN5H8wlqVqacOFq5tRAft 9c=; b=L5pz8UAGDJdUHicnLDpgfrsXw6LHGNoH06tXRfjI36TDWednMNUs/wpEs xtbs+VW4vyvbRTI98Dz6c/0LbjGew4puoysvqxbKSYs7fAiledwuakMr0s2LGidp Vxn97aiOH4trgS0UCaXkzuZJpYwlQkiLCDxyc9ocBK60f9nipllmXvLe63kzIsNG /Pl9bb11cVzWzt6gr7/g/UBK4HAdHwXcv5tiEcscd2Usp7e4vcxCA9QsiRsLWCBi Ca9MDzKAZnZoCiRyR1DNAZMXJ2lImapGjy+opARPWLsHnvziDZe1ii98dTxtbcM6 2dk7xYKgoJ80mBXsnzZRIYym5oWNg==
X-ME-Sender: <xms:LrGuXeLyIbJz_-KQeHpD0B_dIKJHn4cssfIJuFo623uMzYCYpJil2Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrkeeigdduvddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhofgjfffgkfhfvfesthejmhdthhdtvdenucfhrhhomheptehlvgig vgihucfovghlnhhikhhovhcuoegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmh eqnecukfhppeejjedrleejrddugeehrdehheenucfrrghrrghmpehmrghilhhfrhhomhep rggrmhgvlhhnihhkohhvsehfrghsthhmrghilhdrfhhmnecuvehluhhsthgvrhfuihiivg eptd
X-ME-Proxy: <xmx:LrGuXUr-bVw3kMCujTmwRI_y9rEVd4LiunX0t3nh9L1qwFv_uXriZg> <xmx:LrGuXaMAomPU8kG3ONcaeEVP8Ol5fbYoN6wbTjjke4ChUZPf8UpQ4A> <xmx:LrGuXdhKTMvPZEM4bpFe07tH0D9FKt0IgqYvRskGunBtogw3WLpjZw> <xmx:LrGuXbXtVXc2N87zoXMt9pMh2oNFFcWj0wwpzV_btNUsvJVGmsxwKw>
Received: from [192.168.0.5] (cpc121086-nmal24-2-0-cust54.19-2.cable.virginm.net [77.97.145.55]) by mail.messagingengine.com (Postfix) with ESMTPA id 2256680059; Tue, 22 Oct 2019 03:35:08 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (16F203)
In-Reply-To: <20191021.194232.2128729051695435599.mbj@tail-f.com>
Date: Tue, 22 Oct 2019 08:35:06 +0100
Cc: iesg@ietf.org, draft-ietf-netmod-yang-data-ext@ietf.org, joelja@gmail.com, netmod-chairs@ietf.org, netmod@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <DB995C5B-4591-4A58-93CE-882577D66FFB@fastmail.fm>
References: <157149705555.22382.7739043484092917840.idtracker@ietfa.amsl.com> <20191021.093315.1654394906403168701.mbj@tail-f.com> <255a8fa3-065c-43a7-8aaa-9d238082f1a2@www.fastmail.com> <20191021.194232.2128729051695435599.mbj@tail-f.com>
To: Martin Bjorklund <mbj@tail-f.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/PDQs69p2JSKSti7BwUM1AZXj8lQ>
Subject: Re: [netmod] Alexey Melnikov's No Objection on draft-ietf-netmod-yang-data-ext-04: (with COMMENT)
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: Tue, 22 Oct 2019 07:35:15 -0000

Hi Martin,

> On 21 Oct 2019, at 18:42, Martin Bjorklund <mbj@tail-f.com>; wrote:
> 
> "Alexey Melnikov" <aamelnikov@fastmail.fm>; wrote:
>> Hi Martin,
>> 
>> On Mon, Oct 21, 2019, at 8:33 AM, Martin Bjorklund wrote:
>> 
>>>> This is a fine document.
>>>> 
>>>> Can you show and example similar to what in A.3 with 2 addressbook
>>>> entries?
>>> 
>>> The example isn't really written to handle more than one address
>>> book.  The structure defines one single address book.  But perhaps I
>>> misunderstood your question?
>> 
>> The example in A.1 contains "list address". Can this list contain more
>> than one element in it?
> 
> Aha, I see.  Yes it can.
> 
>> If yes, can you provide an example with
>> multiple elements?
> 
> In XML it would be:
> 
>  <address-book xmlns="urn:example:example-module">
>     <address>
>       <last>Flintstone</last>
>       <first>Fred</first>
>       <street>301 Cobblestone Way</street>
>       <city>Bedrock</city>
>       <zipcode xmlns="urn:example:example-module-aug">70777</zipcode>
>     </address>
>     <address>
>       <last>Root</last>
>       <first>Charlie</first>
>       <street>4711 Cobblestone Way</street>
>       <city>Bedrock</city>
>       <zipcode xmlns="urn:example:example-module-aug">70777</zipcode>
>     </address>
>   </address-book>

Right, this is very sensible and I have no further questions.

Thank you,
Alexey

>> I am trying to figure out how multiple elements
>> would be represented in XML (In JSON it seems more obvious to me). My
>> YANG knowledge is limited, so I don't know whether or not there is an
>> issue. But I couldn't tell until I see an example.
> 
> Also see section 4.2.2.4 in RFC 7950 for another example of multiple
> list entries.
> 
> 
> 
> /martin
>