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

Thanks for your feedback, John. Would a modified charter with these changes 
work for you:

Jari

charter-as-modified.txt
Description: Text document

	charter-as-proposed.txt		charter-as-modified.txt
	Locator/ID Separation Protocol (lisp)		Locator/ID Separation Protocol (lisp)
	-------------------------------------		-------------------------------------
	Current Status: Active		Current Status: Active
	Last updated: 2012-02-14		Last updated: 2012-03-08
	Chairs:		Chairs:
	Joel Halpern <jmh(_at_)joelhalpern(_dot_)com>		Joel Halpern <jmh(_at_)joelhalpern(_dot_)com>
	Terry Manderson <terry(_dot_)manderson(_at_)icann(_dot_)org>		Terry Manderson <terry(_dot_)manderson(_at_)icann(_dot_)org>
	Internet Area Directors:		Internet Area Directors:
	Ralph Droms <rdroms(_dot_)ietf(_at_)gmail(_dot_)com>		Ralph Droms <rdroms(_dot_)ietf(_at_)gmail(_dot_)com>
	Jari Arkko <jari(_dot_)arkko(_at_)piuha(_dot_)net>		Jari Arkko <jari(_dot_)arkko(_at_)piuha(_dot_)net>
	Internet Area Advisor:		Internet Area Advisor:
	skipping to change at line 90		skipping to change at line 90
	- LISP security threats and solutions: This document will describe the		- LISP security threats and solutions: This document will describe the
	security analysis of the LISP system, what issues it needs to		security analysis of the LISP system, what issues it needs to
	protect against, and a solution that helps defend against those		protect against, and a solution that helps defend against those
	issues. The replay attack problem discussed on the mailing list		issues. The replay attack problem discussed on the mailing list
	should be included in this work.		should be included in this work.
	- Allocation of Endpoint IDentifier (EID) space: This document		- Allocation of Endpoint IDentifier (EID) space: This document
	requests address space to be used for the LISP experiment as		requests address space to be used for the LISP experiment as
	identifier space		identifier space
			- Provide example specifications for performing cache management
			and ETR synchronization.
	- Alternate mapping system designs: Develop alternative mapping		- Alternate mapping system designs: Develop alternative mapping
	designs to be tested.		designs to be tested.
	- Data models for management of LISP.		- Data models for management of LISP.
	The first three items need to be completed first before other items		The first three items (architecture, deployment models, impacts) need
	can be submitted as RFCs. The three first documents also need to		to be completed first before other items can be submitted as RFCs. The
	complement each other, by describing how the architecture supports a		three first documents also need to complement each other, by
	solution for a particular problem area and how the solution can be		describing how the architecture supports a solution for a particular
	deployed to help with that problem.		problem area and how the solution can be deployed to help with that
			problem.
	In addition, if work chartered in some other IETF WG requires changes		In addition, if work chartered in some other IETF WG requires changes
	in the LISP base protocol or any items which directly impact LISP		in the LISP base protocol or any items which directly impact LISP
	protocol structures, then the LISP WG is chartered to work on such		protocol structures, then the LISP WG is chartered to work on such
	changes.		changes.
	It is expected that the results of specifying, implementing, and testing		It is expected that the results of specifying, implementing, and testing
	LISP will be fed to the general efforts at the IETF and IRTF to		LISP will be fed to the general efforts at the IETF and IRTF to
	understand which type of a solution is optimal. The LISP WG is not		understand which type of a solution is optimal. The LISP WG is not
	chartered to develop a standard solution for solving the routing		chartered to develop a standard solution for solving the routing
	skipping to change at line 137		skipping to change at line 141
	October 2012: Submit a LISP threats analysis document to the IESG for		October 2012: Submit a LISP threats analysis document to the IESG for
	publication as an Experimental RFC		publication as an Experimental RFC
	October 2012: Submit an EID allocation document to the IESG for		October 2012: Submit an EID allocation document to the IESG for
	publication as an Experimental RFC		publication as an Experimental RFC
	January 2013: Submit an lternate mapping system designs to the IESG		January 2013: Submit an lternate mapping system designs to the IESG
	for publication as an Experimental RFC		for publication as an Experimental RFC
			January 2013: Publish an example cache management specification.
			January 2013: Publish an example ETR synchronization specification.
	March 2013: Submit a data model (e.g., a MIB) document to the IESG for		March 2013: Submit a data model (e.g., a MIB) document to the IESG for
	publication as an Experimental RFC		publication as an Experimental RFC
			March 2013: Summarize results of specifying, implementing, and testing
			LISP and forward to IESG and/or IRTF.
End of changes. 5 change blocks.
	6 lines changed or deleted		14 lines changed or added
This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/

_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf