Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



John,

The IESG had no specific objection to these parts, but we made the charter in general shorter and reformulated some of the results. In particular, the idea was to put much of the material that you pointed to into the "LISP impacts" document. In general, the IESG felt that we had to go back a bit, and describe more of the big picture - the architecture, what problem we are addressing, what the results and downsides are - than the technical details. But it was not intended that topics like scalability and amount of state could be left out.

I do agree that the description of the impacts document is short at the moment, is there something that you'd like to lift to put in the new charter?

Jari

On 16.02.2012 19:00, 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@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]