by manufacturers or users ("operators")
Can operators remove vendor tags? How does adding/removing tags interact
with nodes/leaves that are read-only?
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP
ut once it's up, it can not be
changed?
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
is that an example might be the presence of an "lo" device
in a list of interfaces would be immutable. While other interfaces can be
added/deleted, that interface itself can't be deleted.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and
he initial
> registry contents.
I don't object to that, but it was not in what I saw as the plans for the
document.
If you think that this is what we should do, then yeah, lets do it.
I'd like to hear from our AD to confirm this view so that nobody is surprised.
--
Michael Richardson.
gt; The assignment range is insufficient for interoperability.
I hadn't imagined that we'd have to do all that work before publishing, but
rather that we couldn't do any of that work until we published.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works
Andy Bierman wrote:
>> Fengchong (frank) wrote:
>> > Hi Michael,
>> > You can use augment-structure to extend a yang structure.
>>
>> You can't use augment-structure to extend in-place an existing yang
>> structure
>> Augment-structure produces a new structure with a
ng YANG modules with new attributes. We have to revise
> 8366 each time we want extend things. This email details the work to
> make that occur.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Descr
thought is that we change our mind about making this a Obsoletes, and
go back to making this document an Updates:, but I am still stting on the
fence for this.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signa
quot;,
refined the rules for some leaves. It's not clear to me that we can do this
using sx:structure, and I think that augment-structure has the same failings
as "augment" had.
I would very much like to have a wider discussion of this.
--
Michael Richardson. o O ( IPv6 IøT consulting
nd easily accessible form, i.e. as
> compilable YANG modules on github.
Glad it helped, if I could have presented it better, let me know.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP
wrote:
> You should run it with "--tree-print-structures".
Thanks. That makes sense.
I admit that much of my pyang use is cargo culted from one draft to another.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa
tool.
However: https://github.com/mbj4668/pyang/issues/716 there was some
confusion, but it seems that SIDs were generated for groupings.
I don't know if I need to re-introduce deeper groupings, I don't think so.
I have opened:
https://github.com/mbj4668/pyang/issues/835
--
Michael
Probably converting to RFC8791 is also a good thing.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
netmod mailing list
netmod@ietf.or
don't see
any clear difference. So how do I get the tree structure printed from the
examples in RFC8791?
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP
uping for module D1";
container module-D1-things {
uses vA:module-A-grouping;
uses vB:module-B-grouping;
uses vC1:module-C1-grouping;
leaf attribute-D-Delta {
type binary;
description "Delta";
}
}
}
The file practice2.sh uses
could just add the the groupings that they need.
I'm trying this now.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
by me making
> editorial comments. AFAICT the I-D has not had a YANG Doctor
> review.
Seems that this should have happened.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
crowd?
b) I watched the CBOR WG meeting and Carsten spoke about solving this
somehow.
c) I'm wondering where we do this work, and also when.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP
Thank you for very much for the reply.
Jan Lindblad wrote:
> I had a look at your test example. The example is invalid, but pyang
> fails to detect the error and overwrites some internal structures, with
> the result below. The root cause of the problem is this:
...
> Each one
Jan Lindblad wrote:
> I'll make a sketch here, let me know if you have questions.
Thank you.
So I think we have our augments slightly wrong, and maybe we have it wrong in
RFC8995 too, and I'll have to get fully caffeinated and check it all out.
--
Michael Richardson. o O ( IPv6
r-cert? binary
+--rw prior-signed-voucher-request? binary
So I got the entries and the augment from ietf-voucher-request-constrained,
but not those from ietf-voucher-request-prm!
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc,
-ietf-netmod-rfc6991-bis-13 is in progress, although I
don't seem to follow the list to know what's up with.
(I thought I subscribed, but maybe it was all via IMAP)
Is there some interest in doing this?
I guess the better question is, what are the objections?
--
Michael Richardson , Sandelman Sof
Fries, Steffen wrote:
> Thank you for the clarification. This means we don't have to change
> anything in either BRSKI-PRM and constraint voucher, resp. in the
> general approach we use the voucher.
Yes!
I was worred that there were dragons in the future, but seems not.
-
tion. {It might need an RFC for
trade agreement reasons though}
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
ike
a bit more assurance that moving from RESTCONF->RFC8791 would be considered an
acceptable bug fix when going from Proposed Standard to Internet Standard.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Carsten Bormann wrote:
> On 2021-12-12, at 22:17, Michael Richardson wrote:
>> I'm working on draft-richardson-anima-rfc8366bis, trying to make it
RFC8791.
> […]
>> What I don't know how to deal with:
> RFC 8792?
If I put \ into the original .yan
(397): Warning: Too long line found
(L382), 1 characters longer than 72 characters:
namespace "urn:ietf:params:xml:ns:yang:iana-voucher-assertion-type";
okay, I could contract the name, but that seems wrong.
(I also could use a FAQ/Tutorial/screencast on adapting to RFC8791)
YANG module for the voucher
> itself, only for the voucher-request. To my understanding we do not
> need an augmentation for the voucher, as agent-proximity is already
> included in draft RFC 8366bis.
I think that is correct.
--
Michael Richardson. o O
.
Toerless: I think that this is the major change.
Qiufang Ma did the bulk of the YANG work here, and with the blessing of the
WG chairs, I'd like to add her as a co-author.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
an IANA managed YANG module.
Can someone point me at some specific text/explanation?
Maybe there is a PHB version? Maybe just an email from the dawn of YANG-time.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
ditor to delete the
> IANA-maintained module.
I think you mean, the RFC-maintained module :-)
How do we keep the YANG catalog from latching onto it.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signatu
art of the specification of an enumeration - not in
> YANG).
yes, it's a text string for XML and JSON,
this isn't the case for YANG-CBOR if a value is set.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
e (usually a guess and usually wrong but it helps to have the
tp> assumptions about the requirements spelt out) and such like.
tp> As an engineer, I do like to know the requirements before working on
the design!
We need to be able to write RFCs that extend the voucher types.
Not that ofte
Michael Richardson wrote:
> I propose that the WG adopt this as the -00, and then we change the
document
> to change this into an RFC7224-style IANA-maintained YANG module.
> (In DHC WG, when we did RFC3315bis to make RFC8415 we did a -00 which was
> whitespac
s updated when IANA revises the module. I think, it mostly
doesn't matter because none of are generating code from YANG... AT THIS TIME.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwid
//datatracker.ietf.org/doc/draft-richardson-anima-rfc8366bis/
Html:
https://www.ietf.org/archive/id/draft-richardson-anima-rfc8366bis-00.html
Htmlized:
https://datatracker.ietf.org/doc/html/draft-richardson-anima-rfc8366bis
--
Michael Richardson. o O ( IPv6 IøT consulting )
out that, but others might not.
I was basically trying to distill it down into a few words.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works|IoT architect [
] m...@sandelman.ca http://www.sandelm
t)
-> jose-voucher (voucher, voucher-request)
and my question was a bit about how we manage all their things inherited.
It's really the classic CS multiple inheritance problem.
{A Cat is an Mammal
A Cat is an Four-legged creature
A Cat is Nocturnal.}
--
Michael Richardson. o O
<#secure method=pgpmime mode=sign>
> On Mon, Jun 28, 2021 at 12:39:38PM -0400, Michael Richardson wrote:
>>
>> Juergen Schoenwaelder wrote:
>> >> Juergen Schoenwaelder wrote:
>
>> > You revise RFC 8366 and do the fo
t make any modifications to the existing enumerations.
> - You republish the revised version of RFC 8366.
> A couple of month later (and after surviving all the reviews), you
> declare success. I fear there is nothing "cheaper".
--
Michael Richardson. o O
Juergen Schoenwaelder wrote:
> Note that there is also a middle ground, namely an enumeration type
> factored out into an IANA maintained module that is process wise easier
> to extend - should extensions be needed more regularly.
That would suit me. How do we do that?
-
to see what happens to SID values,
etc.
But, not before the hackathon, maybe during.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
__
but how much whisky does it cost to bribe an AD?
2) write a formal "Updates" RFC8366 that just does the NEW/OLD version of
updates, and that's it.
3) do an entire RFC8366bis.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works
d flip "leaf assertion” to “type
> identityref”.
Yes, okay, so if we have to revise 8366, then this sounds like something we
should do.
> FWIW, "leaf assertion” is not used by SZTP (RFC 8572).
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelma
ble extend it?
Can we do this via IANA registry in some way instead?
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
netmod mailing l
the grouping help us at all?
We need to do this for both voucher and voucher-request.
> enum agent-proximity { description "Indicates that the voucher has
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.
ink this is close.)
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
___
ute YANG modules (as pull-requests) to drafts
for which I'm not an author, and I don't really want to have to convince them
to upgrade.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network archite
Carsten Bormann wrote:
> On 14. Jun 2021, at 03:09, Michael Richardson
> wrote:
>>
>> 1) how to process yang files with -DD-MM into XML. 2) how to
>> generate yang tree files. 3) how do I get my YANG includes
>> downloaded, and do I
Carsten Bormann wrote:
> On 14. Jun 2021, at 03:09, Michael Richardson
wrote:
>>
>> 1) how to process yang files with -DD-MM into XML.
>> 2) how to generate yang tree files.
>> 3) how do I get my YANG includes downloaded, and do I put them i
Michael Richardson wrote:
> 3) how do I get my YANG includes downloaded, and do I put them into my
repo?
The other part of the question is how to manage the various extensions that
are occuring. What I know about so far: (ascii art warning. fixed font needed)
https://www.yangcatalog.
Michael Richardson wrote:
> 3) how do I get my YANG includes downloaded, and do I put them into my
repo?
RFC8995 has been published.
It has a YANG module, ietf-voucher-request, which is derived from the RFC8366
ietf-voucher.
RFC8366 has: ietf-voucher@2018-05-09
The DT still poi
with some co-authors which want to stick to XMLv3
rather than kramdown, and whose understanding of Makefiles is poor. I want
to stick with the normal stuff so that all the github/etc. tooling works for
everyone involved.
I'm looking for advice on how do this this?
--
Michael Richardson. o O
an example for usage outside yang?
if such a situation should present itself in the next 10 weeks, sure.
> * *Issue*: Should we maybe point out any specific seccons of 8520?
The only issue I can see is that claiming a copyright might reveal that such
an entity has dealt with such a device.
--
Carsten Bormann wrote:
> On 2020-11-06, at 22:24, Michael Richardson wrote:
>>
>> In one of my drafts, I guess some minor wording tweaks in one draft
leads to
>> some lines exceeding 72 characters (by one). Argh. Change from C-mode to
>> text
about what to do here.
I was introduced to the SED method of fixing yang MMDD version
references.
While I like YANG as executable "code", it sure feels like it is not smart to
be authoring in it.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works I
a generic decoder for YANG encoded content, then it might need
a hint from the application, or it could have a compile-time arbitrary limit.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_
57 matches
Mail list logo
