On the size of the prefix to allocate for documentation.

In IPv4, the following is reserved per RFC 3330.

>    192.0.2.0/24 - This block is assigned as "TEST-NET" for use in
>    documentation and example code.  It is often used in conjunction with
>    domain names example.com or example.net in vendor and protocol
>    documentation.  Addresses within this block should not appear on the
>    public Internet.

This is far less than is needed (strictly speaking) to document usages
that require shorter prefixes. But I'm not aware of this being a
problem in practice.

I think what we want here is a workable balance between no addresses
for documentation at all and allocating too much space in order to
document all possibilities.

"Michel Py" <[EMAIL PROTECTED]> writes:

> Then a /32 is not enough, IMHO. A /32 is the size currently allocated to
> LIRs; imagine a sample BGP config that involves three LIRs, you would
> need at least three /32s. A /30 would be what I consider the bare
> minimum in this case.

But can't the same then be said for a 192.0.2.0/24 not being long
enough in IPv4?

Thomas
--------------------------------------------------------------------
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