"status" : "up"
}
]
}
With Regards,
Rohit R
From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of Robert Wilton
Sent: 14 February 2019 16:57
To: Amar Jadagoud ; netmod@ietf.org
Subject: Re: [netmod] Regarding origin annotation encoding in
ietf-netcon
-with-defaults:default" : true,
"ietf-origin:origin" : "intended"
},
"status" : "up"
}
]
}
From: netmod on behalf of Amar Jadagoud
Sent: Thursday, 14 February 2019 7
Hi Robert, Ladislav,
Thanks for the clarification. I think it would be helpful if an example of
encoding multiple annotations in JSON metadata encoding is mentioned in any
of the related drafts.
Thanks,
Amar
On Thu 14 Feb, 2019, 5:10 PM Ladislav Lhotka On Thu, 2019-02-14 at 11:26 +, Robert
On Thu, 2019-02-14 at 11:26 +, Robert Wilton wrote:
> Hi Amar,
> Based on RFC 7952 section 5.2.1, I think that it would look like this:
> {
> "example:interface" : [
>{
>"name" : "eth1",
>"mtu" : 1500,
>"@mtu" : {
> "ietf-netcon
Hi Amar,
Based on RFC 7952 section 5.2.1, I think that it would look like this:
{
"example:interface" : [
{
"name" : "eth1",
"mtu" : 1500,
"@mtu" : {
"ietf-netconf-with-defaults:default" : true,
"ietf-origin:origin" : intended
Hi All,
I have a question regarding encoding of origin annotation along with other
annotation (with-defaults) in JSON metadata encoding format.
Suppose if below is the GET method :
GET
/restconf/ds/ietf-datastores:operational/ietf-interface:interfaces/interface=eth1?with-defaults=report-all-tagg
