Re: [netmod] AD review of draft-ietf-netmod-syslog-model-20

he element. Kent // shepherd = original message = Kent, Tom, Yaron, and Ron, A new version of the draft-ietf-netmod-syslog-model has been published that addresses your concerns. Thanks, Clyde On 2/20/18, 9:06 AM, "netmod on behalf of Kent Watsen" wrote:

Re: [netmod] ACL draft issues found during shepherd writeup

Hi Mahesh, Please search for below (6 instances) Thanks, Kent // shepherd On 2/17/18, 8:26 PM, "Mahesh Jethanandani" mailto:mjethanand...@gmail.com>> wrote: Kent, Thanks for a detailed review. See inline. On Feb 13, 2018, at 2:30 PM, Kent Watsen mailto:kwat...@jun

Re: [netmod] reference statement examples in draft-ietf-netmod-rfc6087bis-18

Juergen writes: > I think it was common practice to write > > reference "RFC 6991: Common YANG Data Types"; > > instead of just > > reference "RFC 6991"; Agreed, I always do. > that is to include the RFC title (this can be especially useful with > longer lists of references and less commonl

Re: [netmod] Proposal for minimalist full NMDA support in schema mount

So it this a possible way out of the current situation? We publish a trimmed down document that just defines the mount point extension and we do an update of this document that adds all the details needed to obtain the schema information? /js +1 This was something I suggested a while back. Th

Re: [netmod] AD review of draft-ietf-netmod-syslog-model-20

in the title of Section 1.4. Clyde, can you please post a v23 that fixes these last two points? Thanks, Kent // shepherd On 2/23/18, 1:05 PM, "Mahesh Jethanandani" mailto:mjethanand...@gmail.com>> wrote: Kent, On Feb 23, 2018, at 8:02 AM, Kent Watsen mailto:kwat...@juniper.net&

Re: [netmod] AD review of draft-ietf-netmod-syslog-model-20

Thanks Clyde. Benoit, it's ready now. Kent // shepherd On 3/1/18, 10:29 AM, "Clyde Wildes (cwildes)" mailto:cwil...@cisco.com>> wrote: Kent, I published a new draft that fixes the last two points. Thanks, Clyde From: Kent Watsen Date: Wednesday, February 28, 2018 a

Re: [netmod] [Technical Errata Reported] RFC6020 (5272)

>From RFC 7950, Section 7.20.2, first sentence: The "if-feature" statement makes its parent statement conditional. Thus: feature aaa { if-feature bbb; ... } means that feature "aaa" depends on feature "bbb". The current text is correct. Kent The following errata report h

Re: [netmod] I-D Action: draft-ietf-netmod-acl-model-17.txt

[To all those that said this draft was ready, really?] Hi Mahesh, Thanks for the update. I found some more issues. Some must be fixed, others are nits, and might be caught by the RFC Editor. But I think that it's embarrassing to receive comments for such things from the IESG, as is recently

Re: [netmod] Adam Roach's No Objection on draft-ietf-netmod-rfc6087bis-18: (with COMMENT)

> I came up with 2 sentences to add to 6087bis: > > #1) > > If the patterns used in a type definition have known limitations > such as false positive matches, then these limitations > SHOULD be documented within the typedef or data definition. I like this, but it would be better to also mention

Re: [netmod] I-D Action: draft-ietf-netmod-acl-model-17.txt

Hi Mahesh, Please look for below. Thanks, Kent On 3/8/18, 7:40 PM, "Mahesh Jethanandani" mailto:mjethanand...@gmail.com>> wrote: Kent, On Mar 7, 2018, at 1:55 PM, Kent Watsen mailto:kwat...@juniper.net>> wrote: [To all those that said this draft was ready, really?

Re: [netmod] I-D Action: draft-ietf-netmod-acl-model-17.txt

Hi Mahesh, please look for <> below. All, please take a look at the question around renaming the "access-lists" container. Thanks, Kent On 3/13/18, 9:46 PM, "Mahesh Jethanandani" mailto:mjethanand...@gmail.com>> wrote: On Mar 13, 2018, at 3

Re: [netmod] I-D Action: draft-ietf-netmod-acl-model-17.txt

Hi Mahesh, Two instances of <<>> below. Kent // shepherd On 3/14/18, 3:27 PM, "Mahesh Jethanandani" mailto:mjethanand...@gmail.com>> wrote: On Mar 14, 2018, at 10:42 AM, Kent Watsen mailto:kwat...@juniper.net>> wrote: Hi Mahesh, please look for <>

[netmod] kw review of draft-ietf-netmod-schema-mount-09

1: paragraph starting w/ "In some cases", 1st sentence, s/often/sometimes/ 2: add ref to RFC 8174 2.1: s/defines a label for/defines the label for/ 3.1: a) 2nd paragraph, s/defines a label for/defines the label for/ b) 4th paragraph, add ref to RFC 6020 3.2, 1st paragraph: a) 1st sentence

Re: [netmod] kw review of draft-ietf-netmod-schema-mount-09

[Reducing to just the open threads] >> 3.1: >> a) 2nd paragraph, s/defines a label for/defines the label for/ > > Is this really correct? If we say "the label", it seems that we > first have to say that such a label exists; otherwise, which label > does "the label" refer to? I think so, in t

Re: [netmod] draft-ietf-netmod-acl-model

[just back from PTO] I'll be doing the shepherd write-up shortly. Kent // shepherd = original message = status on this draft? ___ netmod mailing list netmod@ietf.org https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_

Re: [netmod] yang-data-ext issues

I like Andy's proposal below, for the argument of the 'yang-data' statement to encode some meta-information regarding the context/namespace in which it's used, but I wonder how it really works. For instance, would "top" and "error-info" be the only allowed base-path values for the argument? and

Re: [netmod] yang-data-ext issues

Another and somewhat radical idea is to think of 'yang-data' as defining a data node, like a 'container', but not a config or opstate node. Yes, this is different from rc:yang-data, which defines a transparent node, like 'choice', but maybe it's okay if we can get the substitution groups part

Re: [netmod] yang-data-ext issues

> People want to use YANG to define the schema for an XML or JSON > representation of a stand-alone document. Agreed > The only data needed must be module + local-name. Or maybe: module + local-name + context, where context is one of: - data nodes - RPC/actions - notifications - stand

[netmod] IPR call on draft-ietf-netmod-acl-model-18

Authors, Contributors, WG, As part of Shepherd write-up for the acl-model draft, we need to ensure that all IPR has been declared. There was an IPR-call before, when there was a different set of authors involved, but not since, so it seems prudent to do another call now. Are you aware of any

[netmod] ACL (-18) issues found during shepherd write-up

Authors, Just a few minor things found while going through the shepherd checklist. These won't block the write-up, but should be fixed before we submit for publication. For now, the write-up will explain that these will be fixed, and I'll clear these comments as soon as an update is posted: 1

[netmod] Publication has been requested for draft-ietf-netmod-acl-model-18

Kent Watsen has requested publication of draft-ietf-netmod-acl-model-18 as Proposed Standard on behalf of the NETMOD working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-netmod-acl-model/ ___ netmod ma

Re: [netmod] yang-data-ext issues

>Martin wrote before: > No I was thinking along the lines of: > > ydx:yang-data my-first-rpc-error-info { >... > } > > rpc my-first-rpc { >... >opx:error-info-structure my-first-rpc-error-info; > } > > I.e., use yang-data to define a structure, and use another statement > to tie t

Re: [netmod] yang-data-ext issues

Lada writes: > Andy writes: >>IMO, the yang-data defined in RFC 8040 has a clear purpose, and it >>is sufficient for that purpose, which is a YANG representation of >>an instance document (such as a protocol message or file). > > The same is basically true even without the extension. For example,

Re: [netmod] IPR call on draft-ietf-netmod-acl-model-18

Thank you, Mahesh and Sonal. I'm still waiting to hear from Lisa and Dana. Neither have been heard from since the pen moved a couple years ago. Is anyone aware of Lisa or Dana's current email? Let's give it a few days but, if we don't hear back from them shortly, I recommend moving their n

Re: [netmod] yang-data-ext issues

Juergen writes: > Kent writes: >> I don't understand talk about abandoning this draft. There is no question >> that it is needed (e.g., anima vouch, zerotouch, tail-f's "structure"), >> and RFC 8040 is unsatisfactory because 1) it doesn't allow a top-level >> 'choice' between two containers and 2

Re: [netmod] Query about draft-ietf-netconf-rfc7895bis-06

[+netconf, since this discussion regards a netconf draft] > But possibly a useful discussion to have may be what the members of the > NETCONF WG perceives is the future for the IETF network management > protocols. I'm an advocate for RESTCONF being as capable as NETCONF, and perhaps more capabl

[netmod] FW: IPR call on draft-ietf-netmod-acl-model-18

Forwarding to the netmod list, for general awareness and posterity. On 5/15/18, 12:47 PM, "Dana Blair" mailto:d...@blairhome.com>> wrote: No, I’m not aware of any IPR that applies to this draft. thanks, Dana On May 14, 2018, at 9:40 AM, Benoit Claise wrote: Including Dana's email address.

Re: [netmod] draft-ietf-netconf-rfc7895bis-06 deviation query

> Co-authors, if you agree, how do we track this? As co-author, I agree and view it as an editorial update. As co-chair, I recommend the authors commit the fix to GitHub now and wait for AD and/or IESG reviews to trigger an update that it will get swept into. I don't think that it's worth fix

Re: [netmod] yang-data-ext issues

[resurrecting this thread] Currently the zerotouch draft has a normative reference to this draft. I will this week post an update to the zerotouch draft to resolve the netconf list thread "a couple zerotouch-21 issues". It would be easy for me to also switch back to using rc:yang-data, but I won

Re: [netmod] yang-data-ext issues

>>> >> The primary use case is not "generic RPC messages", but standalone >>> >> instance documents, error-info structures, etc. >>> > >>> > The proper solution for rpcs and actions is to define error >>> > information as part of the rpc/action. YANG 1.1 does not support >>> > this but this is wher

[netmod] handling long lines in artwork in drafts

As those in London recall, I suggested an alternative solution for handling long lines in artwork in drafts. FWIW, I have captured this idea in the following I-D: https://tools.ietf.org/html/draft-kwatsen-netmod-artwork-folding-00 Kent // contributor

[netmod] IETF 102 presentation requests

Dear WG, The chairs notice that the preliminary IETF 102 Agenda has been posted [1]. NETMOD is scheduled to meet Tuesday afternoon and Friday morning, both sessions are two hours. *** Yes, NETMOD is meeting on Friday, the last day of the conference! *** If you are interested in presenting to

Re: [netmod] yang-data-ext issues

The authors of yang-data-ext met today to discuss how to move this draft forward. After about an hour, we decided that the best course of action is to: * clarify RFC 8040 rc:yang-data for the zerotouch use case - and update the zerotouch draft to use rc:yang-data * request this WG f

Re: [netmod] yang-data-ext issues

>> The authors of yang-data-ext met today to discuss how to move this >> draft forward. After about an hour, we decided that the best course >> of action is to: >> >> * clarify RFC 8040 rc:yang-data for the zerotouch use case >> - and update the zerotouch draft to use rc:yang-data >>

Re: [netmod] IETF 102 presentation requests

Just a quick reminder for folks to send presentation requests. Please have requests in no later than this Sunday (July 1st). K. = original message = Dear WG, The chairs notice that the preliminary IETF 102 Agenda has been posted [1]. NETMOD is scheduled to meet Tuesday afternoon and F

Re: [netmod] Call for adoption request of draft-kwatsen-netmod-artwork-folding-04

Hi Martin, First, I just posted -05 to address the missing artwork: https://tools.ietf.org/html/draft-kwatsen-netmod-artwork-folding-05. See below for more comments. Kent // contributor = original message = > Hi, > > I support this work. See below for some comments. > > Qin Wu wr

Re: [netmod] Call for adoption request of draft-kwatsen-netmod-artwork-folding-04

> (The exmaples with just a string of '\' are highy confusing. Unclear > what they try to tell me... probably that the alg is much more > difficult than I originally thought ;-) Those are torture tests, but they due illustrate the one case where having the '\\n' on the fold column would've be

Re: [netmod] Call for adoption request of draft-kwatsen-netmod-artwork-folding-04

>> Those are torture tests, but they due illustrate the one case where having >> the '\\n' on the fold column would've been illegal input (and hence the '\' >> was replaced with a 'x'). Great for internal algorithm validation, but >> perhaps unnecessary for the example in the text. Or maybe en

Re: [netmod] [Netconf] Editorial comments on draft-kwatsen-netmod-artwork-folding-05

Hi Jonathan, I have applied all your suggestions for -06 - thanks! Regarding this exchange: >> Section 5.3, 4th paragraph: Arguably this should be from bottom-to-top >> as, going from top-to-bottom, once you have concatenated two lines the >> '\' will not be on the folding-column From a draft

Re: [netmod] Call for adoption request of draft-kwatsen-netmod-artwork-folding-04

All, I just posted -06 that addresses some comments from Rob, Martin, and Jonathan. I realize that there are still open issues, but a rapid iteration for some of these things seems like it might be good: https://tools.ietf.org/html/draft-kwatsen-netmod-artwork-folding-06. Hi Robert, > A couple

Re: [netmod] Call for adoption request of draft-kwatsen-netmod-artwork-folding-04

>>But with variable placement of the '\' character you can do: >> >>        This very long line happens to have a space character \ >>        immediately after the fold column."; >> This would not work, since the line is one character too long >> or >> >>        This very long line happens to

Re: [netmod] IETF 102 presentation requests

Per the Important Dates [1], the draft submission cutoff deadline in this Monday, July 2nd. Please be sure sure to submit updates for your drafts before then! [1] https://datatracker.ietf.org/meeting/important-dates/ Thanks, Kent // co-chair Just a quick reminder for folks to send presentat

Re: [netmod] Call for adoption request of draft-kwatsen-netmod-artwork-folding-04

Hi Robert, >>> 2) The proposed solution always left indents the wrapped line. Often for >>> artwork (e.g. a YANG tree diagram), where whitespace is not significant, >>> and the wrapping is relatively minor, then right indenting the wrapped >>> line can make the results look more visually readab

[netmod] removing a node from a grouping

Say there is: grouping "foo-bar-etc" { container-or-leaf "foo" { ... } container-or-leaf "bar" { ... } ... // the "etc" ;) } And the goal is to use the grouping sans the "foo" node. Can a "when" statement that always evaluates to "false" do it? grouping "bar-etc" { uses

Re: [netmod] removing a node from a grouping

grouping "bar-etc" { container-or-leaf "bar" { ... } ... // the "etc" ;) } grouping "foo-bar-etc" { grouping "foo"; grouping "bar-etc"; } Thanks, Rob On 11/07/2018 18:30, Kent Watsen wrote: > Say there i

Re: [netmod] backward compatibility requirements in draft-verdt-netmod-yang-versioning-reqs-00

Before RESTCONF, I implemented a versioned REST API that maintained constant object URIs, while allowing the objects themselves to be versioned, by using the Content-Type and Accept headers (yes, we created a media type for every "object" in the system). The server always natively understood t

Re: [netmod] backward compatibility requirements in draft-verdt-netmod-yang-versioning-reqs-00

> So do we hit a requirement (which is independent of versioning) that a > mechanism is needed to select different module sets (or views), given > that the reality gives us overlapping and competing models? And then > as a side effect, such a mechanism may also be used to select between > differ

[netmod] FW: New Version Notification for draft-kwatsen-netmod-artwork-folding-07.txt

Message- A new version of I-D, draft-kwatsen-netmod-artwork-folding-07.txt has been successfully submitted by Kent Watsen and posted to the IETF repository. Name: draft-kwatsen-netmod-artwork-folding Revision: 07 Title: Handling Long Lines in Artwork in Internet-Drafts an

[netmod] perfect extraction, tabs, and long lines - oh my

[new subject line] It is one thing for an editor to use tabs during the creation of text, and another to publish text with an expectation that consumers will render the tabs the same way. Either the source editor converts tabs to spaces, which is interoperable today, or keep the tabs while publis

Re: [netmod] New Version Notification for draft-kwatsen-netmod-artwork-folding-07.txt

Hi Tom, > I would like a paragraph in this I-D to the effect that editors should > take care of this and that this phenomenon is nothing to do with the > technique described here, a sort of non-Applicability statement so that > we do not, in future, get too long lines as > > /* optical inte

Re: [netmod] perfect extraction, tabs, and long lines - oh my

I recommend that we select "option-2" (see bottom). - it easy to do. - there's no current support for having tabs in folded output. - doing so doesn't preclude an "option-3" someday in the future. The authors will assume that this is WG consensus if there are no objections within a week's time

Re: [netmod] perfect extraction, tabs, and long lines - oh my

> Given that 2) has a)-c), I do not understand what the recommendation > actually is. The recommendation is hopefully 2a) and we are done. For the script that we include in the Appendix, the authors wish to keep the current "2a" behavior and have no plans to change that. The only change we'

Re: [netmod] perfect extraction, tabs, and long lines - oh my

> This is not an improvement. Just more complexity and noise. Disagree. The RFC should not mandate the tool exits, that would be overreaching. How about this simpler language? NEW: Scan the artwork for horizontal tab characters. If any horizontal tab characters appear, either resolve

Re: [netmod] New Version Notification for draft-kwatsen-netmod-artwork-folding-07.txt

Hi Tom, >> Good enough? > > No:-) The authors of YANG modules seem not to understand that it > applies to them, or incorrectly use the tools that would apply > were they correctly used. This seems to be a problem outside the scope of this draft. I was thinking to strengthen Section 4.2 som

Re: [netmod] New Version Notification for draft-kwatsen-netmod-artwork-folding-07.txt

Hi Tom, As contributor, I agree with you. The only reason that it is here now is because draft-wu-netmod-yang-xml-doc-conventions did. As chair, let me discuss with my co-chairs. Meanwhile, would love to hear others opinions. Kent - Original Message - Kent Stepping back, I think

Re: [netmod] New Version Notification for draft-kwatsen-netmod-artwork-folding-07.txt

>> Now, to take it forward, I would like to constrain our efforts to >> solving the problem at hand. If our solution has wider applicability, >> that's great. But can we recognise that the overwhelming bulk of case >> we see today are in YANG documents and that's up to us to solve. > >That sounds

Re: [netmod] YANG module security considerations template - TLS reference

Benoit is the progenitor of the template. I took it to be an "AD thing" has since passed to Ignas. Kent -Original Message- From: "Acee Lindem (acee)" Date: Monday, October 1, 2018 at 10:25 AM To: Martin Bjorklund , "netmod-cha...@ietf.org" , "netmod-...@ietf.org" , "netmod@ietf.org

[netmod] IPR poll on draft-clemm-netmod-nmda-diff-00

This mail starts the IPR poll for draft-clemm-netmod-nmda-diff-00. Are you aware of any IPR that applies to this draft? If so, has this IPR been disclosed in compliance with IETF IPR rules? Note, you do not have to be an author or a contributor to make everyone aware of an IPR. See RFC 3669, 397

[netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00

The IETF 102 in-room poll should really good support to adopt this draft, and no objections. This email starts an adoption poll for: https://tools.ietf.org/html/draft-clemm-netmod-nmda-diff-00 Please indicate your support or objection to the adoption poll. If objecting, please state your reas

Re: [netmod] New Version Notification for draft-kwatsen-netmod-artwork-folding-07.txt

> At least remove YANG from the example, and I also think that > auto-folding of tree diagrams should be strongly discouraged, so find > a better example for (b). Removed "YANG" and s/(e.g., tree diagrams)/, using a tool that doesn't observe line lengths. FWIW, pyang's --tree-line-length sometime

Re: [netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00

to work on. I hope this is okay with everyone. With respect to the adoption poll. The important thing here is if anyone objects. Do you or anyone else object? Kent // chair -Original Message- From: "Reshad Rahman (rrahman)" Date: Tuesday, October 2, 2018 at 8:21 AM

Re: [netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00

Support. Kent // contributor -Original Message- From: Kent Watsen Date: Monday, October 1, 2018 at 2:48 PM To: "netmod@ietf.org" Subject: WG adoption poll for draft-clemm-netmod-nmda-diff-00 The IETF 102 in-room poll showed really good support to adopt this draft, and no

Re: [netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00

We agree that the diff-format should be client-selectable, modulo what the server supports. yang-patch and edit-config both are viable. Should we document them both? That said, since neither edit-config nor yang-patch are diffing formats, so much as formats for converting one data tree to ano

Re: [netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00

js Andy On Thu, Oct 04, 2018 at 05:41:22PM +, Kent Watsen wrote: > We agree that the diff-format should be client-selectable, modulo what the > server supports. yang-patch and edit-config both are viable. Should we > document them both? > > That said, since neither edit-conf

Re: [netmod] [Technical Errata Reported] RFC8342 (5514)

> After reading the RFC details, it seems that the example is intentional based > on > the text about NP-containers. > > I think an errata could be used because the sentence about a top-level origin > must be defined > could be interpreted to define "top-level" as the topmost level for which the

[netmod] IETF 103 presentation requests

Dear WG, The preliminary IETF 103 Agenda has been posted [1]. NETMOD is scheduled to meet in the first slot Tuesday (November 6th) morning for two hours and again in the last slot Thursday (November 8th) afternoon for another two hours. If you are interested in presenting to the WG, please sen

Re: [netmod] WG adoption poll - instance-data

As co-chair, I have two minds: 1) requests a fix and redo the adoption poll 2) realize that it's a living doc and regardless how it begins, the WG can sort it out in time. i.e., we're adopting to work on the problem, not necessarily the specific solution. While (1) seems more

Re: [netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00

-Original Message- From: Alexander Clemm Date: Monday, October 8, 2018 at 5:05 PM To: Ladislav Lhotka , Kent Watsen , Andy Bierman , Juergen Schoenwaelder , "netmod@ietf.org" Subject: RE: [netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00 I would second the request for

Re: [netmod] Whitespace in XML encoding - allowed ?

As Martin points out, this is how XML works. As a result, XML instance documents are poster-child examples for why long lines occur sometimes, and where the artwork-folding draft shines when placing said examples into drafts. Lada, good point, but would there be a layer violation? Kent // cont

Re: [netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00

a step in the right direction. Kent // contributor -Original Message- From: Alexander Clemm Date: Wednesday, October 10, 2018 at 6:06 PM To: Kent Watsen , Ladislav Lhotka , Andy Bierman , Juergen Schoenwaelder , "netmod@ietf.org" Subject: RE: [netmod] WG adoption poll for draft

Re: [netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00

IMO. Kent // contributor On 10/10/18, 10:20 PM, "Andy Bierman" mailto:a...@yumaworks.com>> wrote: On Wed, Oct 10, 2018 at 6:39 PM, Kent Watsen mailto:kwat...@juniper.net>> wrote: Hi Alex, no objection. My support withdraw appears to put me in the rough, which i

Re: [netmod] schematree-statement extension?

Hi Robert, Picking up on your YANG 1.2 comment. Please add a YANG-next issue, if this is not being tracked already. https://github.com/netmod-wg/yang-next/issues. Thanks, Kent -Original Message- From: netmod on behalf of Robert Varga Date: Monday, October 15, 2018 at 3:36 PM To: Ma

Re: [netmod] Regarding IPR on draft-kwatsen-netmod-artwork-folding-08

No, I'm not aware of any IPR that applies to this draft Kent // as an author -Original Message- From: Adrian Farrel Reply-To: "adr...@olddog.co.uk" Date: Tuesday, October 16, 2018 at 5:24 PM To: 'Lou Berger' , Kent Watsen , Benoit Claise , "bill...@hu

Re: [netmod] WG adoption poll draft-kwatsen-netmod-artwork-folding-08

[fixed the date in Lou's message below] No objection. Kent // contributor -Original Message- From: Lou Berger Date: Thursday, October 18, 2018 at 9:11 AM To: "netmod@ietf.org" Cc: "netmod-cha...@ietf.org" Subject: WG adoption poll draft-kwatsen-netmod-artwork-folding-08 Resent-From:

Re: [netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00

Message- From: netmod on behalf of Kent Watsen Date: Monday, October 1, 2018 at 2:48 PM To: "netmod@ietf.org" Subject: [netmod] WG adoption poll for draft-clemm-netmod-nmda-diff-00 The IETF 102 in-room poll should really good support to adopt this draft, and no objections.

Re: [netmod] New Version Notification for draft-wu-netmod-factory-default-01.txt

Hi Qin, AFIACT, the “replaces” button is only available for adopted (i.e., “-ietf”) documents. Kent On 10/19/18, 9:57 AM, "netmod on behalf of Qin Wu" mailto:netmod-boun...@ietf.org> on behalf of bill...@huawei.com> wrote: Thanks Balazs for the update, To netmod c

[netmod] FW: Cutoff date for requesting remote presentations at IETF103

Presenters, 1) in case you haven't done so already, please send your presentation requests to the chairs before Monday! 2) if needing to present remotely, please notify the chairs about this by Monday as well. Thanks, Kent PS: please excuse my company's URL-mangler below. -Original Me

Re: [netmod] yang-data issues

Folks, Can we get some quick replies to this email? Kent // all hats -Original Message- From: netmod on behalf of Martin Bjorklund Date: Tuesday, September 11, 2018 at 4:45 AM To: "netmod@ietf.org" Subject: [netmod] yang-data issues Hi, The authors of draft-ietf-netmod-yang-dat

Re: [netmod] WG adoption poll draft-kwatsen-netmod-artwork-folding-08

Correct, this document only defines a file format. A separate effort will be needed to extend `xml2rfc` and `xym` and the like. For those that wish to pre-fold their artwork prior to submitting the XML (hand-crafted folding --> max readability), the `xml2rfc` will not fold it again. For those

Re: [netmod] WG adoption poll draft-kwatsen-netmod-artwork-folding-08

Hi Martin, > one quick comment; the header used in the examples in > section 8 isn't equal to the header defined in section 5.1 This is intentional. Section 5.1 says: The first line is the following 46-character string that MAY be surrounded by any number of printable characters. The

Re: [netmod] xpath expressions in JSON

I submitted yang-next issue #55 to track the long-term solution. https://github.com/netmod-wg/yang-next/issues/55 K. -Original Message- From: netmod on behalf of Juergen Schoenwaelder Reply-To: Juergen Schoenwaelder Date: Tuesday, October 23, 2018 at 10:00 AM To: Martin Bjorklund

[netmod] for a future rfc6991bis

NETMOD WG, A conversation in NETCONF WG regarding the yang-push noted that it might be time to update RFC 6991, in particular to introduce a type for time-duration. https://mailarchive.ietf.org/arch/msg/netconf/KaUJloIShkLNIXTuHZNwB-SYBnQ In addition, it might be good to introduce [inet?] typ

Re: [netmod] for a future rfc6991bis

>> In addition, it might be good to introduce [inet?] types for RFC 5322 >> (Internet Message Format) including perhaps: >> >> - email-address(addr-spec, per Section 3.4.1) >> - named-email-address (name-addr, per Section 3.4) >> > > Where are these used? Or have these already bee

Re: [netmod] Confirming draft-ietf-netmod-module-tags-03 consensus call

> The servers implement the modules which can have predefined tags from > the module designer as well as the implementer (vendor) which literally > cannot come from anywhere *but* the server that implements the module. Predefined tags from the implementer only needs to come from the implementor

[netmod] Draft meeting minutes posted

The draft minutes, including key decisions, for the NETMOD WG meeting have been posted. Please review and provide corrections as needed. https://datatracker.ietf.org/doc/minutes-103-netmod Kent (and Joel and Lou) ___ netmod mailing list netmod@i

[netmod] FW: Comments on draft-ietf-netconf-keystore-07

YANG experts, Why are action/notification statements not allowed under a case statement? Yes, it’s simple to assert, but was it considered, in such cases, to instead allow them to attach/bind to the closest legal ancestor? Would it make sense? Nit: It would’ve been helpful if the “Since a” pa

Re: [netmod] yang-next meeting at IETF 104?

I'm interested as well. PS: I've been too busy to setup a virtual meeting for us to finish the review of the YANG-next items in the GitHub tracker. But things are just beginning to free up a little for me now. Would folks like to have a meeting before 104 to finish that review? Kent // contr

Re: [netmod] yang-next meeting at IETF 104?

>> PS: I've been too busy to setup a virtual meeting for us to finish the >> review of the YANG-next items in the GitHub tracker. But things are >> just beginning to free up a little for me now. Would folks like to >> have a meeting before 104 to finish that review? > > I think that's what the si

Re: [netmod] Network Modeling (netmod) WG Virtual Meeting: 2019-02-06

Reminder: the virtual interim to continue scoring the YANG Next items is tomorrow. Kent > On Jan 24, 2019, at 3:34 PM, IESG Secretary wrote: > > The Network Modeling (netmod) Working Group will hold > a virtual interim meeting on 2019-02-06 from 10:00 to 12:00 America/New_York. > > Agenda:

[netmod] Meeting Minutes

inutes === NETMOD Virtual Interim February 6th, 2019 Attendees: - Kent Watsen - Acee Linden - Andy Bierman - Juergen Schoenwaelder - Ladislav Lhotka - Mahesh Jethanandani - Martin Bjorklund - Reshad Rahman - Robert Wilton Agenda: The purpose of this meeting was to continue scori

Re: [netmod] Network Modeling (netmod) WG Virtual Meeting: 2019-02-20

Reminder: the virtual interim to continue scoring the YANG Next items is tomorrow. Kent > On Feb 6, 2019, at 6:52 PM, IESG Secretary wrote: > > The Network Modeling (netmod) Working Group will hold > a virtual interim meeting on 2019-02-20 from 10:00 to 12:00 America/New_York. > > Agenda: >

[netmod] Meeting minutes for virtual interim on Feb 20

place at IETF 104 in Prague. Attendees: - Kent Watsen - Acee Linden - Andy Bierman - Juergen Schoenwaelder - Ladislav Lhotka - Martin Bjorklund - Robert Wilton - Charles Eckel - Lou Berger - Mehmet Ersue Results: Overview of results follows. For details, please see the YANG

[netmod] artwork folding: dual support modes?

I had a chat with the tools team recently and, in the course of things, it was implied that the double backslash approach we have now was both surprising and non-intuitive. This got me thinking that we may have thrown the proverbial baby out with the bathwater. That is, currently we have a he

Re: [netmod] Obsolete feature - what does it mean?

> On Feb 27, 2019, at 6:16 AM, Balázs Lengyel > wrote: > > feature oldFeature { > status obsolete; > } > leaf myTimer { > if-feature oldFeature ; > mandatory true; > config true; > status current; > type string; > } > So should I configure myTimer or not? I assume yes, correct? Th

Re: [netmod] artwork folding: dual support modes?

mps over the lazy dog > > > So, my point is, if and only if we do not care about these “spaces on the > fold” cases, we can operate with a single slash. > > Cheers, > Adrian > > From: Joel Jaeggli mailto:joe...@bogus.com>> > Sent: 27 February 2019 06:31 > To

Re: [netmod] [Editorial Errata Reported] RFC7950 (5642)

Note: I just released this this email. Peter sent it on the 22nd, but it was trapped by Mailman: Post by non-member to a members-only list Kent // co-chair > On Feb 21, 2019, at 1:06 PM, Peter Loborg wrote: > > > Your example is fine – but the gammar is ch14 specifies somethin

Re: [netmod] Obsolete feature - what does it mean?

> On Feb 27, 2019, at 11:48 AM, Juergen Schoenwaelder > wrote: > > On Wed, Feb 27, 2019 at 04:09:17PM +, Kent Watsen wrote: >> >> >>> On Feb 27, 2019, at 6:16 AM, Balázs Lengyel >>> wrote: >>> >>> feature oldFeature { &g

Re: [netmod] Obsolete feature - what does it mean?

Hi Randy, > Are you saying that legacy boxes sitting in dark closets > would somehow be updated to provide this indication? Assuming YANG-next resolves the issue, and there is sufficient motivation then, yes, sys-admins would need to blow the dust off their servers (and clients) and update the

[netmod] IETF 104 Presentation Requests

Dear WG, The preliminary IETF 104 Agenda has been posted [1]. NETMOD is currently scheduled to meet twice, 2 hours Tuesday morning and again for two hours on Friday morning. If you are interested in presenting to the WG, please send your presentation requests to the "netmod-chairs" alias (CC-e

Re: [netmod] I-D Action: draft-chopps-netmod-geo-location-00.txt

This is a neat draft. Reminds me of when I worked on the Virtual Reality and real-time simulations.I once wrote a class to convert locations, vectors, and orientations to and from WGS84 geocentric coordinate space and topocentric coordinate space systems. I was fresh out of college with a

<    1   2   3   4   5   6   7   8   9   10   >