(re: draft-saucez-lisp-impact-00.txt)

> With the WG co-chair hat stapled on.
> 
> Unfortunately this draft is not yet a WG item and pursuant to the agreement
> between the LISP chairs and the responsible AD, we will only focus on WG
> items until the priority, gating documents, are submitted to the IESG.
> Sorry, but I will not provide an agenda slot at IETF 85 for this item.
> 
> I do (fully) expect that this document will become a WG item in the near
> future. In fact the LISP charter calls for it. However the line has been
> drawn in the sand - we MUST put the work into lisp-introduction and
> lisp-architecture first.
> 
> If we have time remaining for an AOB session in Atlanta, and productive
> discussion is seen on the list about this draft before we all touchdown in
> ATL, Joel and I will be willing to allow microphone time (sans slides!) in
> AOB for a face to face discussion.
> 
> Apologies for the tight hold on the reigns. I cannot stress this enough, we
> MUST get cracking on lisp-introduction and lisp-architecture!

Hi Terry-

I find this response a little confusing since I thought that the impact
statement was explicitly listed as a gating item for the WG, despite it
being a bit behind schedule for WG adoption; seems like something of a
"Catch-22" not to be able to talk about it during the meeting.

Is the LISP WG agenda really so tight that we can't afford a few minutes to
mention the salient points of the impact statement document? Can you provide
the current tentative agenda, or at least the set of items (and times
assigned) accepted so far?

Note that, at present, there is nothing new to present regarding either
draft-ietf-lisp-introduction or draft-ietf-lisp-architecture; that *may*
change prior to the -01 draft deadline next week (and I have volunteered
to present the set of changes and lead a discussion if applicable) but
there is no guarantee of that. I can't imagine how we will "get cracking"
on these documents during the WG meeting if there is nothing to say about
them.

        Thanks,
        --Vince
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to