On Wednesday, October 23, 2002, at 08:31 AM, Michel Py wrote:
Thomas,There is a fundamental question here, which is whether or not toThomas Narten wrote: There has been some private discussion about the need for addresses for documentation, but it's probably worth discussing how much address space is needed for this purpose, and what the prefix should be (e.g., allocate out of 001/3?). the /32 length is a strawman.
consider documentation new or not-yet-implemented proposals. If the
answer is yes, I have an immediate need for a /15. Let's say you want to
document a new protocol comparable to 6to4; you need a /16 right off the
bat.
If it was my call, I would allocate 3FF8::/14 for documentation.
And if you wanted to document a complete different address scheme, you would need at least
half the entire address space....
I do not think this is a valid argument. One need to reserve a portion of the
address space to describe example scenarios in product documentation.
For that, the address space need to be large enough to accommodate
a decent size network. I think a /32 is plenty and I support Thomas proposal...
- 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]
--------------------------------------------------------------------
