Hi tcpinc wg,
as already announced, I am stepping down as tcpinc co-chair. I’m very happy to
see that tcpinc is progressing smoothly at this point! Of course, I will
further follow the working group, as the responsible AD. Therefore I’m still
open to help with any questions or concerns. Please
On 4/12/2016 8:17 AM, Kyle Rose wrote:
>> The IESG statement is worded poorly at best. It appears to me to imply
>> "when picking between MIB and Netconf/YANG models, pick the latter".
>
> This is how I read it, as well.
>
>> An abstract API should never need to get into such a level of detail
> > An abstract API should never need to get into such a level of detail
> > to require a particular implementation. If you're aiming for something
> > beyond that, IMO the IETF is the wrong place (e.g., a better place
> > would be POSIX).
> To this point, does it make sense to use a common
> The IESG statement is worded poorly at best. It appears to me to imply
> "when picking between MIB and Netconf/YANG models, pick the latter".
This is how I read it, as well.
> An abstract API should never need to get into such a level of detail to
> require a particular implementation. If
On 4/12/2016 3:05 AM, Scharf, Michael (Nokia - DE) wrote:
> The link is in my first e-mail:
> https://www.ietf.org/iesg/statement/writable-mib-module.html
>
> The relevant sentence is: "IETF working groups are therefore encouraged to
> use the NETCONF/YANG standards for configuration,
The link is in my first e-mail:
https://www.ietf.org/iesg/statement/writable-mib-module.html
The relevant sentence is: "IETF working groups are therefore encouraged to use
the NETCONF/YANG standards for configuration, especially in new charters."
Section 2.2 of draft-bittau-tcpinc-api-01
On 12/04/16 10:54, Stephen Farrell wrote:
>
> Michael,
>
> Which of the IESG statements listed at [1] do you mean?
> That's not clear to me, sorry,
Ah sorry now I see the URL:-)
I doubt that there'll be a problem for this draft from the
IESG, other than the usual nitpicking. That is, unless
Inline
-Original Message-
From: EXT David Mazieres [mailto:dm-list-tcpcr...@scs.stanford.edu]
Sent: Monday, April 11, 2016 6:52 PM
To: Scharf, Michael (Nokia - DE); EXT Kyle Rose; tcpinc
Subject: Re: [tcpinc] Confirmation of consensus to adopt API document
"Scharf, Michael (Nokia -
