Re: [MBONED] Question about multicast address to be used in documentation and example

On Oct 15, 2008, at 10:52 AM, Leo Vegoda wrote:

> Hi,
>
> On 15/10/2008 4:14, "Stig Venaas" <stig.venaas@uninett.no> wrote:
>
> [...]
>
>>> I checked RFC3330, it proposes an IPv4 range to be used in  
>>> documentation and
>>> example but only for unicast, I could not find an equivalent range  
>>> for
>>> multicast. Does this range exist for multicast? Or should I remove  
>>> the
>>> example from the draft?
>>
>> There is a draft draft-ietf-idr-as-documentation-reservation-00.txt
>> proposing ASNs 64496 - 64511 for documentation. This is only a draft.
>> But if this is approved, then I guess you could use GLOP addresses
>> based on those for documentation :)
>
> In draft-ietf-mboned-rfc3171bis-03.txt we have marked that portion  
> of the
> space for extending the AD-HOC range (section 9.2).
>
> [...]
>
>> But I guess assigning a specific multicast prefix would be good,
>
> I suppose it's always helpful if people know that a particular  
> address is
> reserved for documentation purposes and so cannot be part of a live
> configuration.
>

My thinking was that the FIRST such range in eGLOP could be so  
reserved. Is a /24 sufficient ?
I think that a /32 would be too small, and inconvenient as well.

Marshall

> Regards,
>
> Leo
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

_______________________________________________
MBONED mailing list
MBONED@ietf.org
https://www.ietf.org/mailman/listinfo/mboned