as valid inputs.
Given that the colon format has been around for way more than 20 years
(see for example RFC 2579, STD 58), this exercise seems like a waste
of energy, it might take multiple decades to get changes widely
implemented and deployed.
/js
--
Juergen Schoenwaelder Jacobs University
>
> > > > > And this text in section 7.3.4 implies that derived types only do
> > > > > further restriction:
> > > > >
> > > > > If the type's default value is not valid according to the new
> > > > >restr
On Fri, Mar 27, 2020 at 04:35:44PM +0100, Martin Björklund wrote:
> [re-sent w/ correct address]
>
> Juergen Schoenwaelder wrote:
> > Hi,
> >
> > two comments:
> >
> > - It is unclear to me whether this really qualifies as an errata.
> >
> >
-system:system/authentication/user[name='jack']"
instead of
"/ietf-system:system/authentication/user[name='bob']"
to line up with the third example using SIDs?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Ca
ce...
- Incomplete sentence:
RFC7120] also says
Or is the following paragraph a quote? In that case, add a colon.
- There are likely more normative references, e.g., RFC 6991 and RFC
8040.
- Why does the example in appendix A not have / need
dependency-revisions?
- I have not run any tools to va
On Thu, Apr 02, 2020 at 06:51:41PM +0200, Martin Björklund wrote:
>
> I think it quite clear that such a label should not be used in I-Ds.
>
I agree.
Yesterday, com.example-1.2.3m+1 would have made sense to me. ;-)
/js
--
Juergen Schoenwaelder Jacobs University Bremen gG
___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 2875
uld probably be documented in
> section 3, with a sentence in section 6 to explain that is how it is
> protected.
>
Why would a factory-default datastore be more sensitive than ?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus
ue as two 3-octet values in YANG.
> I wonder whether it would make sense to provide something like:
>
> type uint24 {
>type uint32;
>range 0..16777215;
> }
>
> in ietf-inet-types as a common base type for such definitions.
If we add such a definition, it likely s
re. It specifies
> > >>> from where the node originated. If not specified for a given
> > >>> configuration data node, then the origin is the same as the
> > >>> origin of its parent node in the data tree. The origin for
> > >>&
On Tue, May 05, 2020 at 11:00:11AM +0200, Martin Björklund wrote:
> Hi,
>
> If we were to redo YANG, I would prefer to have a single statement
> "operation", either on the top-level, or tied to a node.
>
+1
/js
--
Juergen Schoenwaelder Jacobs University Br
e identifier? Or is
> > the difference between the two how namespaces are represented?
> >
>
> [IP]: I might have misunderstood something, but my understanding is that
> the prefix related to a module could be changed during an import, whereas
> here we really want to use th
tually the names bound to
the position). All other bits default to 0.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-univ
r in the definition of the -00:00 semantics. I would call this a
bug and fix it but then others may claim this is an non-backwards
compatible change...
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen
On Mon, Mar 09, 2020 at 04:17:40PM +, Balázs Lengyel wrote:
> See BALAZS4 below
>
> -Original Message-
> From: Juergen Schoenwaelder
> Sent: 2020. március 9., hétfő 10:44
> To: Balázs Lengyel
> Subject: Re: [netmod] WG Last Call:
> draft-ietf-netmod-yang
On Tue, May 05, 2020 at 12:06:34PM +0200, Per Hedeland wrote:
> On 2020-05-05 11:55, Juergen Schoenwaelder wrote:
> > On Tue, May 05, 2020 at 11:45:41AM +0200, Per Hedeland wrote:
> >> On 2020-05-05 11:00, Martin Björklund wrote:
> >>> Hi,
> >>>
>
e "rev:nbc-changes" substatement
> that indicates where NBC changes have occurred in the revision history. As
> long as the allocated YANG Semver revision labels are consistent with the use
> of the rev:nbc-changes" substatement in the revision history then it would
> still b
If module authors are too lazy
to use existing YANG mechanisms properly, does it make sense to add
more mechanism to the YANG eco system? I doubt it.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
ge churn is reasonably under control. During active
development phases, modules may undergo many little (nbc) changes
but dealing with them should be left to version management
systems.
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus
On Wed, Aug 26, 2020 at 05:43:27PM +, Joe Clarke (jclarke) wrote:
>
>
> > On Aug 13, 2020, at 06:23, Juergen Schoenwaelder
> > wrote:
> >
> > On Thu, Aug 13, 2020 at 11:37:18AM +0200, Ladislav Lhotka wrote:
> >>
> >>
> >
miss my point: The specification of a leaf needs to be clear what
it is. If it is not clear, then the specification is buggy.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103
standard version of ietf-yang-types in rfc 6991. So
> the import should be something like "revision 2013-07-15 or derived;".
>
> Rgds,
> Jason
>
>
> From: netmod On Behalf Of Andy Bierman
> Sent: Wednesday, September 2, 2020 10:52 AM
> To: Juergen Schoenwaelde
client needs
the complete module list every time a connection is (re-)established.
This is why the recommendation is to use the YANG library wherever
possible, it scales better than the orignal exchange design
and it is more flexible.
/js
--
Juergen Schoenwaelder Jacobs University Bremen
uot;we know about it, it is not ideal, but
> it will stay the way it is". I was hoping for something better.
>
> Regards,
> Michal
>
> On Thursday, July 16, 2020 17:55 CEST, Juergen Schoenwaelder
> wrote:
>
> > On Thu, Jul 16, 2020 at 04:24:43PM +0200, Michal Vaško wrote:
On Mon, Jul 20, 2020 at 11:04:55AM +0200, Ladislav Lhotka wrote:
> Juergen Schoenwaelder writes:
>
> > - Lada suggested to replace the inet:domain-name usage in
> > the union with a new host-name definition that follows
> > the NR-LDH definition in RFC 5890.
&
Tom,
my understanding is that Lada is now proposing something slightly
different but I am not sure what exactly, hence I asked again.
/js
On Wed, Jul 22, 2020 at 09:54:00AM +, tom petch wrote:
> From: netmod on behalf of Juergen Schoenwaelder
>
> Sent: 21 July 2020 20:44
>
&
raft-ietf-netmod-geo-location-05?
> > Type in my opinion is more reusable building block.
> >
> > -Qin
> > 发件人: Christian Hopps [mailto:cho...@chopps.org <mailto:cho...@chopps.org>]
> > 发送时间: 2020年7月31日 0:38
> > 收件人: Juergen Schoenwaelder >
YANG-Library.
Whether a change is BC or not always depends on which definitions have
changed, how they have changed, and how these definitions are used. So
the answer very likely must be option 1. Option 2 also seems to push
the problem elsewhere (packages, library) without providing the
details.
/
48, Juergen Schoenwaelder wrote:
> >
> >
> > I personally meanwhile believe that sub-modules add complexity with
> > little extra value but this view surely is not shared by others.
> >
> >+1. IMO removing sub-modules from YANG 2.0 should be on the list
day's YANG versioning rules handle them well.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
___
grouping instead of
> submodule.
>
> Tom Petch
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 358
ignificant.
Lets raise this to the next level. What about the following?
D1. description "A server.";
D2. description "A server."; // not very descriptive
E1. description "A server."; // not very descriptive
E2. // not very descriptive
description &q
> for them, and a JSON/XML encoding of them is seemingly trivial.
>
> Regards,
> Rob
>
>
> > -Original Message-
> > From: netmod On Behalf Of Juergen Schoenwaelder
> > Sent: 07 July 2020 12:25
> > To: Christian Hopps
> > Cc: NetMod WG
>
On Wed, Jul 08, 2020 at 04:53:52PM +, Rob Wilton (rwilton) wrote:
>
>
> > -Original Message-
> > From: Juergen Schoenwaelder
> > Sent: 08 July 2020 17:44
> > To: Rob Wilton (rwilton)
> > Cc: Christian Hopps ; NetMod WG
> > Subject: Re:
ows the following rules:
o The leftmost (top-level) data node name is always in the
namespace-qualified form.
o Any subsequent schema node name is in the namespace-qualified
form if the node is defined in a module other than its parent
node, and the simple form
But what matters is how the strings are interpreted
since computers internally often do not use strings when it comes to
numbers or addresses or ...
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +4
he/she likes? That would be a big
step backward since every implementation will then interpret the
numbers differently.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 4
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-uni
-Draft is available from the on-line Internet-Drafts
> > directories.
> > This draft is a work item of the Network Modeling WG of the IETF.
> >
> > Title : Common YANG Data Types
> > Author : Juergen Schoenwaelder
> > Filename : draft-ietf-netmod-rfc6991-bis-03.tx
uch newer) has numbers that start to become interesting
when you need more precision, a simple 64-bit counter starts falls
apart in JSON.
I can't tell how many of the "backward incompatible" changes are due
to picking too restrictive types.
/js
--
Juergen Schoenwaelder Jacobs
ing to plain JSON where you encode a number as a number
until you realize that some numbers must be encoded as strings to
avoid surprises. RFC 7951 does this for YANG defined data.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus
ncludes prefixes
> > instead of module names.
> >
>
> [IP]: I might be misunderstanding your statement or the text in RFC 7951,
> but if I read sec 6.11. from RFC 7951 correctly,
>
> The leftmost (top-level) data node name is always in the
> namespace-qualified form.
&
On Wed, Jun 24, 2020 at 09:56:11AM +0200, Ivaylo Petrov wrote:
> Hi Juergen,
>
> Thank you very much for your new comments! Please find my answers below.
>
> On Tue, Jun 23, 2020 at 6:59 PM Juergen Schoenwaelder <
> j.schoenwael...@jacobs-university.de> wrote:
>
>
1.1.0
> in this case.
>
> The main problems covered:
> - ensure all intermediate versions have a unique identifier (in case there
> are pre-release implementations, etc)
> - ensure the final version has the correct YANG Semver
>
/js
--
Juergen Schoenwaelder Jaco
eems to be needed, the most important thing is for
the profile SDO to talk to the other SDO. Modularity and reuse can
often be improved if SDOs talk to each other and work together.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 |
s are selected for modules
> in IETF RFCs that are being updated (e.g. a "bis" version is under
> development).
>
> (should we drop the "in IETF RFCs" ? )
>
> Jason
>
> ___
> netmod mailing list
> netmod@ietf.org
On Sat, Jul 18, 2020 at 09:00:42AM -0700, Andy Bierman wrote:
> On Sat, Jul 18, 2020 at 8:42 AM Vladimir Vassilev <
> vladi...@lightside-instruments.com> wrote:
>
> > On 17/07/2020 21.14, Juergen Schoenwaelder wrote:
> >
> > > - How do we deal with
On Fri, Jul 24, 2020 at 12:14:17PM +0200, Erik Auerswald wrote:
> Hi,
>
> On Fri, Jul 24, 2020 at 10:36:17AM +0200, Juergen Schoenwaelder wrote:
> > On Wed, Jul 22, 2020 at 01:46:38PM +0200, Ladislav Lhotka wrote:
> > > On 22. 07. 20 13:00, Juergen Schoenwaelder wr
esentation
> conforms to that precise type or otherwise it is an error. There is no
> ambiguity.
>
An annotation that is only understood by some tools and not by others
is creating a new problem since different tools now start to interpret
data in different ways, i.e., the annotation harms int
t;presentation time" probably is
not a good thing.)
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
___
user of the current session.")
- This interacts with the definition of xpath1.0 concerning the
context and the use of module names as prefixes.
- Proposal: ?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen
with the definition of node-instance-identifier.
- Options: (i) Leave this definition as it is. (ii) Detail how this
type work with encodings that use module names instead of prefixes
to qualify names.
- Proposal: ?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49
there is a
common need for types for loopback addresses.
- Proposal: do not add such types at this point in time
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <ht
the pattern right.
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
___
netmod mailing list
' in your private list archive
(I can't find it in the IETF archive)
- I can't tell for sure that Lada's proposal is (i) correct and (ii)
not breaking anything
- Proposal: ?
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring
gue seems to be down. :-(
- Proposal: do not add a percentage type since it is trivial to
define a context specific percentage type that matches range and
precision requirements (and there is already a definition in RFC
8294 for those who need exactly that definition).
--
Juergen Schoenwael
specific
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
___
netmod mailing list
netmod@ie
is, perhaps the Universal Postal Union.
- Options: (i) do nothing or (ii) add a country code definition
only or (iii) add both a country code definition and a postal
code definition (which might be to some extend vague)
- Proposal: do nothing
--
Juergen Schoenwaelder Jacobs
the timezone is implicit.
- Proposal: Make the timezone optional (adding text describing the
implications, i.e., comparisons may be surprising). Align as much
as possible with the XML schema definition concerning the
canonical format.
/js
--
Juergen Schoenwaelder Jacobs
nd I can see
> this having possibly quite nasty consequences.
>
This is known and has already be known when the JSON format was
standardized. Whether it is a feature or a bug (and if so where
the bug is) depends on whom you talk to.
/js
--
Juergen Schoenwaelder Jacobs Unive
On Mon, Jul 27, 2020 at 03:18:25PM +0200, Ladislav Lhotka wrote:
>
>
> On 27. 07. 20 12:44, Juergen Schoenwaelder wrote:
> > On Mon, Jul 27, 2020 at 10:51:31AM +0200, Ladislav Lhotka wrote:
> >> Juergen Schoenwaelder writes:
> >>
> >>&
nce tags. If anything, I would
be interested in a generic solution and not something taylored to one
specific use case (telemetry) and this is why I would prefer to have
the specific semantics in the tags and not in the set of leafs
carrying the tags.
/js
--
Juergen Schoenwaelder Jacobs Univ
On Mon, Jul 27, 2020 at 12:33:39PM +, Qin Wu wrote:
> -邮件原件-
> 发件人: Juergen Schoenwaelder [mailto:j.schoenwael...@jacobs-university.de]
> 发送时间: 2020年7月27日 18:42
> 收件人: Qin Wu
> 抄送: netmod@ietf.org
> 主题: Re: [netmod] The NETMOD WG has placed draft-tao-netmod-yang-nod
On Mon, Jul 27, 2020 at 10:51:31AM +0200, Ladislav Lhotka wrote:
> Juergen Schoenwaelder writes:
>
> > So would the following do the right thing?
>
> The invert-match pattern also needs to be added in order to avoid reserved
> labels:
Why are they illegal? If we make the
n, Jul 26, 2020 at 03:11:15PM +0200, Ladislav Lhotka wrote:
> Juergen Schoenwaelder writes:
>
> > On Wed, Jul 22, 2020 at 01:46:38PM +0200, Ladislav Lhotka wrote:
> >>
> >>
> >> On 22. 07. 20 13:00, Juergen Schoenwaelder wrote:
> >> >
gt; Benoit Claise:
> https://mailarchive.ietf.org/arch/msg/netmod/3C-K4JaAgLnpAoPqcQAn59DFHYw/
>
> _______
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49
On Wed, Jul 22, 2020 at 01:46:38PM +0200, Ladislav Lhotka wrote:
>
>
> On 22. 07. 20 13:00, Juergen Schoenwaelder wrote:
> > Tom,
> >
> > my understanding is that Lada is now proposing something slightly
> > different but I am not sure what exactly, hence I a
On Fri, Jul 24, 2020 at 10:36:17AM +0200, Juergen Schoenwaelder wrote:
>
> What is the '(.*\.)?' part doing in your pattern?
>
OK, I figured it out, the NR-LDH label and be in anywhere in the
sequence of labels.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
P
not most writers of examples for YANG modules seem
> unaware of so if we add anything, I would add those.
>
> Tom Petch
>
> From: netmod on behalf of Juergen Schoenwaelder
>
> Sent: 17 July 2020 20:25
>
> - There was a request to add types for loopback addr
used.
I think this is something where the input from Chris Hopps and the
NETMOD chairs is important to determine the path forward. Since we
have an ietf-geo-location module, I would prefer to have common types
for location information defined there and not in yang-types.
/js
On Thu, Jul 30, 2
ea", deprecation requires some internal communication and
collaboration (but not deprecating also won't hurt much for these
fairly simple types).
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax
On Wed, Jul 29, 2020 at 01:55:38PM +0200, Ladislav Lhotka wrote:
> Juergen Schoenwaelder writes:
>
> >> If we want to allow non-ASCII names, then it would IMO be safer to use a
> >> type that expects straight Unicode for lexical representation and leave
> >> it
-05 only define
> grouping, there is typedef for longitude and latitude, altitude.
>
> -Qin
> -邮件原件-
> 发件人: Juergen Schoenwaelder [mailto:j.schoenwael...@jacobs-university.de]
> 发送时间: 2020年7月30日 21:32
> 收件人: Qin Wu
> 抄送: netmod@ietf.org
> 主题: Re: [netm
On Thu, Jul 30, 2020 at 02:58:22PM +0200, Benoit Claise wrote:
> On 20/07/2020 11:19, Ladislav Lhotka wrote:
> > Juergen Schoenwaelder writes:
> >
> > >- Percentages are frequently used in YANG models but usages differ a
> > > lot in precision and range
I am not a fan of loopback seeing it as the implementation choice
> of one manufacturer. On the other hand, the IETF has defined documentation
> addresses which many if not most writers of examples for YANG modules seem
> unaware of so if we add anything, I would add those.
>
>
eneficial for future document to import these types from
> rfc6991bis instead of from te topo model.
>
> -Qin
> -邮件原件-
> 发件人: netmod [mailto:netmod-boun...@ietf.org] 代表 Juergen Schoenwaelder
> 发送时间: 2020年7月18日 3:16
> 收件人: netmod@ietf.org
> 主题: [netmod] rfc6991b
it would help to ground the discussions if those who can
> remember previous efforts would share their experiences or at least some
> pointers.
>
> Best,
> Adrian
>
> -Original Message-
> From: netmod On Behalf Of Juergen Schoenwaelder
> Sent: 23 December 2020 1
ve a good
> weekend!
>
> Rgds,
> Jason
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587
ECA work has a long 20+ year tradition in the IETF and several
specifications have been published over the years by various working
groups. As far as I can tell, none of them got traction in terms of
signifiant deployment of interoperable implementations.
I would have hoped that the next iterat
On Wed, Dec 23, 2020 at 07:08:52PM +0100, Juergen Schoenwaelder wrote:
>
> ECA work has a long 20+ year tradition in the IETF and several
> specifications have been published over the years by various working
> groups. As far as I can tell, none of them got traction in terms of
comes from the factory?" is that it is
empty. On first boot, on a system implementing RFC 8808, it would be
loaded with the content of the factory default datastore and on
systems not implementing RFC 8808 it would most likely remain empty.
/js
--
Juergen Schoenwaelder Jacobs Univers
in such a debate is often that modeling things as
a boolean is simplistic since there are often more than exactly two
states (in this case, enabled, disabled, failed, not-available, ...).
So you settle on blaming the model writer. ;-)
/js
--
Juergen Schoenwaelder Jacobs Universi
origin=default or
origin=system if the default derivation logic becomes more complex.
For me personally, if there is more complex logic involved in deriving
a value for a leaf (i.e., the existence of other leafs or values of
other leafs matter), then I would rather call it a system provided
value and not
by config false leafs.
An example is the zero-based-counter32 typedef in RFC 6991. However,
this style may be debated since it (mis)uses a default statement to
define an initial value. I am not sure whether the pattern of using
default statements for specifying intial values is a good one.
/js
--
Enclosed are the materials for the Virtual Interim on Monday. Have a good
> weekend!
>
> Rgds,
> Jason
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder
units (Kbps/Mbps/Gbps).
>
The description of bandwidth-ieee-float32 says:
The units are octets per second.
Note that draft-ietf-teas-yang-te-types has been published as RFC 8776
in June 2020, it should be safe to use these definitions.
/js
--
Juergen Schoenwaelder Jacobs
discussion of this open issue it was pointed
> out that it would be desirable to specify both the bandwidth and the units
> (Kbps/Mbps/Gbps)
>
> Italo
>
> > -Original Message-
> > From: Juergen Schoenwaelder [mailto:j.schoenwael...@jacobs-university.de]
> > S
mes (i.e., you want zoned addresses you use "-zoned" types e.g.,
> >> "ipv6-address-zoned").
> >>
> >> Thanks,
> >> Chris.
> >>
> >> ___
> >> netmod mailing list
> >> netmod@ietf.org
> >> https://
st
> Ericsson Hungary Ltd.
>
> Mobile: +36-70-330-7909 email: balazs.leng...@ericsson.com
>
>
>
> _______
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Ph
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> ___
> I-D-Announce mailing list
> i-d-annou...@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.i
, only the module-name+revision-label can be the unique
> identifier for a revision.
>
> Jason
>
> _______
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder Jacobs University Br
a
> module, if required.
>
I think it is not "allowed" but "mandatory to implement". We should
allow implementations to support an ftps:// scheme as long as there
is a common baseline.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49
representation? And does that
> saving justify to start engineering another schema specification format?
>
> I guess my choice would have been to just have
>
>+-- content-schema
> | +-- (content-schema-spec)?
>| +--: (yang-library)
>
augment in a new choice. So I am not
convinced by this argument.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
__
he way import-by-revision should have worked from the start.
>
> The draft contains some reasonable updates to YANG and YANG Guidelines
> wrt/ updating a module.. They would be appropriate for a new YANG language
> version.
>
+1
/js
--
Juergen Schoenwaelder Jacobs Un
ANA maintained module that is process wise
easier to extend - should extensions be needed more regularly.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103
On Mon, Jun 28, 2021 at 12:04:46PM -0400, Michael Richardson wrote:
>
> 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 ex
On Mon, Jun 28, 2021 at 12:39:38PM -0400, Michael Richardson wrote:
>
> Juergen Schoenwaelder wrote:
> >> Juergen Schoenwaelder wrote:
> >> > Note that there is also a middle ground, namely an enumeration type
> >> > factored out into an IANA
On Fri, Jul 09, 2021 at 08:57:34AM +, tom petch wrote:
> From: netmod on behalf of Juergen Schoenwaelder
>
> Sent: 08 July 2021 11:13
>
> On Thu, Jul 08, 2021 at 09:30:27AM +, Rob Wilton (rwilton) wrote:
> > It is perhaps worth noting that the NETCO
the import
dependency.
NEW:
If they are excluded then the consumer of the instance data file has
to apply the YANG language rules to resolve the imports.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Ger
901 - 1000 of 1039 matches
Mail list logo
