If I may separate issues for a moment,
the absence of milestones is because Terry and I have to come up with a
proposal for them which matche sthe revised goals.
If you read the rest of the differences, you will see that the general
question of what LISP is aimed at providing is indeed still there.
The largest single difference is the addition of the architecture draft,
which the IESG considers a gating item for any of the longer term work
(such as the security solutions or the additional mapping system.
Some of the apparent removal is because, as Jari stated, the IESG has
requested that the working group focus on fewer deliverables.
Yours,
Joel
On 2/16/2012 12:00 PM, John Scudder wrote:
Hi Thomas,
On Feb 15, 2012, at 4:31 PM, Thomas Narten wrote:
A WG Review message for this WG already went out a month ago.
What has changed to necessitate another Last Call?
Could the-powers-that-be please make it easier for those who might
care to understand if there is something here that we should know and
possibly comment about?
A simple explanation, or a pointer to diffs, etc. would do the job
nicely.
Good question! I did go back and diff the last couple of versions and though
this isn't the exhaustive diff, these are the key changes that caught my eye:
This text was lost from the previous draft charter:
This analysis will explain what
role LISP can play in scalable routing. The analysis should also look at
scalability and levels of state required for encapsulation,
decapsulation, liveness, and so on as well as the manageability and
operability of LISP. Specifically, the group will work on:
- documenting areas that need experimentation
- summarizing the results of implementation, experiments, and deployment
experience
- describing the implications of employing LISP
- operational guidance for using LISP
And so were these Goals and Milestones:
Jun 2012 Forward to the IESG an operational document which should
include cache management and ETR synchronization
techniques (draft-ietf-lisp-deployment).
Dec 2013 Publish an example cache management specification.
Jun 2014 Summarize results of specifying, implementing, and testing
LISP and forward to IESG and/or IRTF.
Jun 2014 Analyze and document the implications of LISP deployments in
Internet topologies and forward to IESG for publication.
I'm not sure why these were removed, and I would like to see them reinstated or
at least have a discussion about their removal.
Thanks,
--John
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf