What you seem to be asking for is something like the v4
        delegation 192.0.2.0/24.  It was set aside for documentation.

        My thought is/was that we might reuse the 5f:: prefix that
        predates the 6bone.




% 
% there was suggestion to not use 3ffe::/16 space so that it can be later 
% (humm, do not know how many years...) reclaimed and reused as part of the 
% 001b/3 current addressing architecture.  So may be something out of 
% 2000::/3 is the right thing, I don't know, and actually, I don't care. My 
% point was to reserve a space, any space, for documentation/examples/... 
% purposes.
% 
% Marc.
% 
% At/� 12:08 2001-06-06 -0700, Alain Durand you wrote/vous �criviez:
% >At 11:50 AM 6/6/2001 -0700, Bill Manning wrote:
% >
% >>         Strong Objections to this tactic.  If you want a 6bone prefix,
% >>         you should follow the process. Hijacking is bad form. I'm
% >>         sure Bob would be amenable to making the delegation, but
% >>         asking is appropriate.
% >
% >This is the reason why I had Cced Bob to this thread.
% >
% >Bob:
% >- do you think it would be appropriate to use a 6bone ptla for that purpose?
% >- what should be the formal process to follow?
% >- would you have any preferences? 3ffe:ff00::/24, 3ffe:5550::/28, anything 
% >else?
% >
% >         - Alain.
% >
% >--------------------------------------------------------------------
% >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 [EMAIL PROTECTED]
% >--------------------------------------------------------------------
% 
% 


-- 
--bill
--------------------------------------------------------------------
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 [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to