Re: [netmod] [netmod-wg/acl-model] TCP flags values not defined and only single flag allowed (#5)

2017-07-10 Thread Mahesh Jethanandani
> On Jul 10, 2017, at 4:21 AM, Ladislav Lhotka wrote: > >> >> On 10 Jul 2017, at 10:53, Eliot Lear > > wrote: >> >> What would you prefer? That way they can be knocked down one by one, >> without the bunch getting intertwined. > >

Re: [netmod] Wg use of github (was Re: [netmod-wg/acl-model] TCP flags values not defined and only single flag allowed (#5))

2017-07-10 Thread Kent Watsen
I have done it both ways, and it seems that folks prefer it more when the discussion appears to be less formalized. My current/personal thoughts are, use github internally, only as an author's aid. That is, don't mention the GitHub issue to the WG list at all. I have no issue with there being

[netmod] Wg use of github (was Re: [netmod-wg/acl-model] TCP flags values not defined and only single flag allowed (#5))

2017-07-10 Thread Lou Berger
Hi, From the wg chair perspective: The working group has not decided how Github should be used, and at this point we defer to the authors / editors on their preferred method. But in all cases, issue resolution must be reviewed with the working group. Editors / authors have a lot of

Re: [netmod] [netmod-wg/acl-model] TCP flags values not defined and only single flag allowed (#5)

2017-07-10 Thread Ladislav Lhotka
> On 10 Jul 2017, at 10:53, Eliot Lear wrote: > > What would you prefer? That way they can be knocked down one by one, > without the bunch getting intertwined. Sure, but the WG should deal with issues of published revisions of Internet Drafts whereas GitHub issues should (in

Re: [netmod] [netmod-wg/acl-model] TCP flags values not defined and only single flag allowed (#5)

2017-07-10 Thread Ladislav Lhotka
Hi, is it necessary to post these GitHub issues one by one to the WG mailing list? Thanks, Lada > On 8 Jul 2017, at 00:28, sonal1204 wrote: > > The TCP flags container is a leaf. This allows only 1 TCP value to be > specified per ACE. > > leaf flags { > type