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

reqs for local addressing OR requirements for SL replacement? [Re:Accept hain/templin draft as wg item?]



Hi,

As some others have also commented, I have serious concerns about the 
hain/templin draft.

An observation:

This document seems to take for granted that local-use addressing is 
needed.  Moreover, it lists requirements for every possible case where 
local-use address could be applied to (and, not for example, those cases 
where the local-use addressing is really necessary).

Process questions:

 1. Shouldn't we first see the requirements for site-local replacement
(and other issues) and not jump straight to the requirements for local
addressing?

 2. Then if we see that local addressing is required to do X, see that 
this document covers X adequately?

 3. Not consider those not listed in the sum-of-all-X at all? (or at 
least, make the separation what scenarios require specific features 
clearer)?

I don't send in more detailed comments on the draft, because I pretty much 
disagree with everything it says.  If we explicitly make the decision that 
local-use addressing is needed in some scenarios, I might accept that and 
review it again with that in mind.

 Just two notes:

 3.1 -- "Network managers have stated, and historical experience has 
shown, that there is a need for addresses that do not require public 
registration."  
 ==> there is no supporting evidence of this expect vague statements.  
Please be more explicit as I don't see how we can take this for given.

 3.2 "Applications require addresses that remain stable during 
intermittent connectivity, site mergers, ..."
 ==> it is not clear what you mean with stability, i.e. what the _real_ 
requirement is.  Connection survibability, or something else?


On Fri, 22 Aug 2003, Fred Templin wrote:
> Folks - do we have consensus to accept this document as an
> IPv6 wg item (see below)?
> 
> Fred
> ftemplin@iprg.nokia.com
> 
> 
> Subject:
> I-D ACTION:draft-hain-templin-ipv6-limitedrange-01.txt
> From:
> Internet-Drafts@ietf.org
> Date:
> Thu, 14 Aug 2003 10:27:13 -0400
> 
> To:
> IETF-Announce: ;
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
> 	Title		: Addressing Requirements for Local Communications 
>                           within Sites
> 	Author(s)	: T. Hain, F. Templin
> 	Filename	: draft-hain-templin-ipv6-limitedrange-01.txt
> 	Pages		: 19
> 	Date		: 2003-8-14
> 	
> The IPv6 addressing architecture specifies global and local-use
> unicast addressing schemes, but provides no operational guidelines or
> requirements for their use. There is a strong requirement for
> addressing to support local communications within sites. Of special
> interest are 'active sites', e.g., sites that are
> intermittently-connected or disconnected from the global Internet,
> sites that frequently change provider points of attachment, sites
> that temporarily or permanently merge with other sites, multi-homed
> sites, etc. This memo will discuss addressing requirements for local
> communications within sites.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-hain-templin-ipv6-limitedrange-01.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-hain-templin-ipv6-limitedrange-01.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:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-hain-templin-ipv6-limitedrange-01.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.
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
> 

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to majordomo@sunroof.eng.sun.com
--------------------------------------------------------------------