Re: [netmod] IETF91 NETMOD agenda ?

[Ladislav Lhotka <[e-mail]>]

Hi,

I agree with Andy. I think we already have a LOT to do with the existing
WG items, and YANG 1.1 in particular, and we should devote most of the
WG meeting time to them. Offloading this work to interim telcos is IMO
not good.

In my view, authors of new YANG modules face three challenges:

1. Organize a group of domain experts to work on the substance of the
module (scope, configuration logic, dealing with the legacy of existing
CLIs etc.).

2. Get advice about YANG-related aspects.

3. Find a home for the module so that it can eventually become an RFC.

For the most part, #1 and #3 should be done outside NETMOD in an
appropriate IETF area. It involves convincing domain experts that the
work is worth doing in the first place, and then find enough support and
capacity to carry it out. But this is I guess IETF business as
usual. NETMOD WG cannot act as a shortcut for this hard part. And
judging from the recently announced guidelines, I think the routing area
got it pretty much right.

There might be modules that need to be done in the NETMOD WG, e.g. if
they span multiple areas, but they should be an exception.

As for #2, I think it is a task for YANG doctors. In this case, I'd be
willing to accept stricter rules and more deterministic workflow so that
module autors receive feedback in a timely manner.

Lada

Andy Bierman <[e-mail]> writes:

>>
>
> It is not NIMBY. The YANG experts are not all SYSLOG experts.
> Getting the right people in the room is important (you said that ;-)
> Making a few SYSLOG experts sit through 140 minutes of
> unrelated material may not be the best option for them either.
>
> It is unfortunate that the SYSLOG WG has decided the protocol
> is complete and no further work is needed.  I don't agree IETF
> process should be a good reason to choose NETMOD WG.
> This draft is already chartered and I am not trying to stop
> the SYSLOG work.  I don't want it to start a trend though.
>

-- 
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C