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

Stig Venaas <stig.venaas@uninett.no> Wed, 15 October 2008 15:59 UTC

Return-Path: <mboned-bounces@ietf.org>
X-Original-To: mboned-archive@lists.ietf.org
Delivered-To: ietfarch-mboned-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BD2828C221; Wed, 15 Oct 2008 08:59:13 -0700 (PDT)
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E232C28C265 for <mboned@core3.amsl.com>; Wed, 15 Oct 2008 08:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.04
X-Spam-Level:
X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[AWL=-0.560, BAYES_00=-2.599, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BArqX1xUvqpA for <mboned@core3.amsl.com>; Wed, 15 Oct 2008 08:59:00 -0700 (PDT)
Received: from tyholt.uninett.no (tyholt.uninett.no [IPv6:2001:700:1::eecb]) by core3.amsl.com (Postfix) with ESMTP id 3B85B28C221 for <mboned@ietf.org>; Wed, 15 Oct 2008 08:58:59 -0700 (PDT)
Received: from [158.38.160.252] (dhcp252.venaas.no [158.38.160.252]) by tyholt.uninett.no (Postfix) with ESMTP id EF4202BAABD; Wed, 15 Oct 2008 17:59:55 +0200 (CEST)
Message-ID: <48F613C3.8010501@uninett.no>
Date: Wed, 15 Oct 2008 18:01:07 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Marshall Eubanks <tme@multicasttech.com>
References: <20081015154759.GH923@cisco.com> <E4F4E302-6E9F-461B-8BF3-765BF2C96EAF@multicasttech.com>
In-Reply-To: <E4F4E302-6E9F-461B-8BF3-765BF2C96EAF@multicasttech.com>
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Question about multicast address to be used in documentation and example
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mboned-bounces@ietf.org
Errors-To: mboned-bounces@ietf.org

Marshall Eubanks wrote:
> 
> On Oct 15, 2008, at 11:47 AM, Toerless Eckert wrote:
> 
>>
>> So, what happens in that documentation tool when you use
>> some address from IPv4 multicast admin-scope or link-local scope ?
>> After all, you will need to be able to use addresses from all different
>> scopes in examples, because of the example you are trying to make.
>> eGLOB is just one of these scopes.
> 
> This would be like example.com - something you should never use.
> 
> There is no way to create a space like this in 239.0.0.0 AFAICT - too 
> many people use too many
> random pieces of it. (Or, to be more precise, we could do it, but we 
> would never be able to enforce it.)
> 
> 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.

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:tme@multicasttech.com]
>>> Sent: Wednesday, October 15, 2008 5:05 PM
>>> To: Leo Vegoda
>>> Cc: Stig Venaas; Maglione Roberta; mboned@ietf.org
>>> 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" <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).
>>>>
>>>> [...]
>>>>
>>>
>>>
>>>> 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
>>>
>>>
>>>
>>> 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 webmaster@telecomitalia.it.
>>>
>>>        Thank you
>>>
>>>                                        www.telecomitalia.it
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>>
>> -- 
>> ---
>> Toerless Eckert, eckert@cisco.com
>> 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
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

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