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

Maglione Roberta <roberta.maglione@telecomitalia.it> Wed, 15 October 2008 15:31 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 934F53A68FC; Wed, 15 Oct 2008 08:31:59 -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 C13323A6948 for <mboned@core3.amsl.com>; Wed, 15 Oct 2008 08:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level:
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 0teZGeT1VcZh for <mboned@core3.amsl.com>; Wed, 15 Oct 2008 08:31:57 -0700 (PDT)
Received: from GRFEDG702RM001.telecomitalia.it (grfedg702rm001.telecomitalia.it [217.169.121.21]) by core3.amsl.com (Postfix) with ESMTP id 79A173A693C for <mboned@ietf.org>; Wed, 15 Oct 2008 08:31:57 -0700 (PDT)
Received: from grfhub703rm001.griffon.local (10.19.3.10) by GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP Server (TLS) id 8.1.291.1; Wed, 15 Oct 2008 17:20:31 +0200
Received: from GRFMBX702RM001.griffon.local ([10.19.3.19]) by grfhub703rm001.griffon.local ([10.19.3.10]) with mapi; Wed, 15 Oct 2008 17:21:43 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Marshall Eubanks' <tme@multicasttech.com>, Leo Vegoda <leo.vegoda@icann.org>
Date: Wed, 15 Oct 2008 17:21:42 +0200
Thread-Topic: [MBONED] Question about multicast address to be used in documentation and example
Thread-Index: Acku12c5ZvSV3wR/TkejviuCWXmTBwAAPn3A
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A2012949200B@GRFMBX702RM001.griffon.local>
References: <C51BD044.20386%leo.vegoda@icann.org> <6EDBBD24-7B7C-46DF-91C0-1213FDED4F7E@multicasttech.com>
In-Reply-To: <6EDBBD24-7B7C-46DF-91C0-1213FDED4F7E@multicasttech.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "mboned@ietf.org" <mboned@ietf.org>, Stig Venaas <stig.venaas@uninett.no>
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mboned-bounces@ietf.org
Errors-To: mboned-bounces@ietf.org

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