[renum] summary of the gap analysis draft--//FW: New draft: draft-liu-6renum-gap-analysis-00.txt

["Leo Liu(bing)" <[e-mail]>]

If you don’t' have enough time to read the whole draft, following is a summary of the draft:

Abstract: This document briefly introduces the existing mechanisms could be utilized by IPv6 site renumbering and envisions the effort could be done under the 6renum working group. This document tries to cover the most explicit issues and requirements of IPv6 renumbering. Through the gap analysis, the document provides a basis for future work to identify and develop solutions or to stimulate such development as appropriate. The gap analysis is presented following a renumbering event procedure clue.

Overall requirements for renumbering (envisions the effort potentially be achieved in the future)
o	Prefix delegation and delivery should be automatic and accurate in aggregation and coordination.
o	Address reconfiguration should be automatically achieved through standard protocols with minimum human intervene. [open question] "with no human intervene" possible?
o	Address relevant entries (DNS records, ACLs, etc.) update should be processed integrally and error-prevented. [open question]Is it necessary to develop automatic entries update mechanisms? If necessary, do we need standard protocols/interface for it?
o	[open question]Is it necessary/possible to develop a “One-Click” fully automatic renumbering technology? What scenarios have the potential possibility?
o	[open question]Is session survivability within our scope?

Existing components for IPv6 renumbering ("components" in current protocols/tools could be utilized for renumbering)
- Protocols: ND, DHCP, DHCP-PD, rfc2894(router renumbering), etc.
- Management Tools: Some operations of renumbering could be automatically processed by management tools to make the renumbering process more efficient and accurate.
- Procedures/Policies: something like RFC4192, which proposed a procedure for renumbering a IPv6 network without a flag day.

Gap analysis
The gap analysis is organized by the main steps of renumbering process:

1) Managing prefix (a short prefix may be divided into longer prefixes for subnets)
  - Prefix delegation
  - Prefix assignment
2) Address Configuration
  - Host Address Configuration
  - Router Address Configuration
  - Static Address Configuration
3) Address Relevant Entries Update
  - DNS Records Update
  - Filters
4) Renumbering Event Management
renumbering is a kind of event which may need additional process to make the process more easy and manageable.
5) Miscellaneous
  - Multicast
  - Mobility

-----Original Message-----
From: Leo Liu(bing) 
Sent: Tuesday, July 05, 2011 4:03 PM
To: [e-mail]
Subject: New draft: draft-liu-6renum-gap-analysis-00.txt

Hi, all

The renumbering gap analysis draft has been posted:
http://tools.ietf.org/html/draft-liu-6renum-gap-analysis-00

The 00 version intends to provide a clue for analysis and some open questions to provoke discussions rather than a decided gap list. 
So please don't stint your comments and ideas, :)
We'll continue work on it to produce a 01 version, your comments would be very useful for it.


-----Original Message-----
From: [e-mail] [mailto:[e-mail]] 
Sent: Monday, July 04, 2011 6:30 PM
To: Jiangsheng
Cc: Leo Liu(bing); Jiangsheng
Subject: New Version Notification for draft-liu-6renum-gap-analysis-00.txt

A new version of I-D, draft-liu-6renum-gap-analysis-00.txt has been successfully submitted by Sheng Jiang and posted to the IETF repository.

Filename:	 draft-liu-6renum-gap-analysis
Revision:	 00
Title:		 IPv6 Site Renumbering Gap Analysis
Creation date:	 2011-07-04
WG ID:		 Individual Submission
Number of pages: 14

Abstract:
   This document briefly introduces the existing mechanisms could be
   utilized by IPv6 site renumbering and envisions the effort could be
   done under the 6renum working group. This document tries to cover the
   most explicit issues and requirements of IPv6 renumbering. Through
   the gap analysis, the document provides a basis for future work to
   identify and develop solutions or to stimulate such development as
   appropriate. The gap analysis is presented following a renumbering
   event procedure clue.



                                                                                  


The IETF Secretariat