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

[Toerless Eckert <[e-mail]>]

On Wed, Oct 15, 2008 at 06:01:07PM +0200, Stig Venaas wrote:
> >Is there a suitable range for examples in IPv6 ?
> 
> Only I know, is that you can use unicast prefix based multicast
> addresses based on 2001:db8::/32. Also embedded-RP. This can be done
> for all scopes. Question is whether one also need examples for other
> types of addresses...
> 
> In particular for both IPv4 and IPv6 one should probably have examples
> also in the SSM range.

IPv6 IMHO is simple, because all we need is one prefix owned by IETF
or whomever designated for documentation, and we can derive all unicast
and multicast addresses and unicast addresses of interest from it IMHO.

IPv4 multicast is the issue, because of all those historic scopes you
may want to use in examples.
> 
> Stig
> 
> >
> >Regards
> >Marshall
> >
> >
> >>
> >>
> >>On Wed, Oct 15, 2008 at 05:21:42PM +0200, Maglione Roberta wrote:
> >>>
> >>>>>>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 /24 would be fine for documentation.
> >>>
> >>>Thanks,
> >>>Roberta
> >>>
> >>>-----Original Message-----
> >>>From: Marshall Eubanks [mailto:[e-mail]]
> >>>Sent: Wednesday, October 15, 2008 5:05 PM
> >>>To: Leo Vegoda
> >>>Cc: Stig Venaas; Maglione Roberta; [e-mail]
> >>>Subject: 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" <[e-mail]> 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).
> >>>>
> >>>>[...]
> >>>>
> >>>
> >>>
> >>>>I think that a /32 would be too small, and inconvenient as well.
> >>>
> >>>Marshall
> >>>
> >>>>Regards,
> >>>>
> >>>>Leo
> >>>>
> >>>>_______________________________________________
> >>>>MBONED mailing list
> >>>>[e-mail]
> >>>>https://www.ietf.org/mailman/listinfo/mboned
> >>>
> >>>
> >>>
> >>>CONFIDENTIALITY NOTICE
> >>>
> >>>This message and its attachments are addressed solely to the persons 
> >>>above and may contain confidential information. If you have received 
> >>>the message in error, be informed that any use of the content hereof 
> >>>is prohibited. Please return it immediately to the sender and delete 
> >>>the message. Should you have any questions, please contact us by 
> >>>replying to [e-mail].
> >>>
> >>>       Thank you
> >>>
> >>>                                       www.telecomitalia.it
> >>>_______________________________________________
> >>>MBONED mailing list
> >>>[e-mail]
> >>>https://www.ietf.org/mailman/listinfo/mboned
> >>
> >>-- 
> >>---
> >>Toerless Eckert, [e-mail]
> >>Cisco NSSTG Systems & Technology Architecture
> >>"The strategy is what you do, not what you write" - Wesley Clark
> >>"Vision without ressources is hallucination" - James L. Jones
> >
> >_______________________________________________
> >MBONED mailing list
> >[e-mail]
> >https://www.ietf.org/mailman/listinfo/mboned
_______________________________________________
MBONED mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/mboned