Re: I-D ACTION:draft-ietf-dnsop-v6-name-space-fragmentation-00.txt

[Johan Ihren <[e-mail]>]

This is exactly the draft I presented in SLC, it has only been renamed
to reflect its adoption as a working group document.

However, it was unclear (to me at least) what direction this document
really should take. I see at least two possibilities:

1. Make this document the base paper for the general discussion on the
   fragmentation problem (while leaving the particulars of various
   architectural alternatives to other documents).

2. Focus only on the particular subissue of possible validation of
   delegations (i.e. one position on the scale from "do nothing" to
   "provide full bridging of DNS lookups in both directions").

I think that (1) is needed, but it could well be that it is better to
keep that discussion in draft-ietf-ngtrans-dns-ops-req-03.txt where
Alain and I started with it. 

The key is that it would be good to find a structure that also in an
obvious way can fit at least one or two additional papers on possible
solutions that I see coming without everyone getting even more
confused over an unsorted but hairy tangle of interconnected documents.

All input appreciated,

Johan

-------
[e-mail] writes:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Domain Name Server Operations
> Working Group of the IETF.
> 
> 	Title		: IPv4-to-IPv6 migration and DNS name space 
>                           fragmentation
> 	Author(s)	: J. Ihren
> 	Filename	: draft-ietf-dnsop-v6-name-space-fragmentation-00.txt
> 	Pages		: 
> 	Date		: 23-Jan-02
> 	
> This memo documents some problems forseen in transitioning from a
> IPv4-only DNS hierarchy via a long period of mixture to an
> IPv6-mostly situation sometime in the future. The mixture period is
> expected to be very long, and hence design choices should very much
> take this into account, rather than just regard the transition as a
> relatively short period of pain.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-dnsop-v6-name-space-fragmentation-00.txt
> 
> To remove yourself from the IETF Announcement list, send a message to 
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-dnsop-v6-name-space-fragmentation-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	[e-mail].
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-dnsop-v6-name-space-fragmentation-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.