IETF Logo Mail Archive

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

Leo Vegoda <leo.vegoda@icann.org> Wed, 15 October 2008 14:51 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 5293528C223; Wed, 15 Oct 2008 07:51:26 -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 1A13B3A692D for <mboned@core3.amsl.com>; Wed, 15 Oct 2008 07:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 auHFb2l9o0Ys for <mboned@core3.amsl.com>; Wed, 15 Oct 2008 07:51:24 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 291DE28C21F for <mboned@ietf.org>; Wed, 15 Oct 2008 07:51:24 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.233]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Wed, 15 Oct 2008 07:52:24 -0700
From: Leo Vegoda <leo.vegoda@icann.org>
To: Stig Venaas <stig.venaas@uninett.no>, Maglione Roberta <roberta.maglione@telecomitalia.it>
Date: Wed, 15 Oct 2008 07:52:20 -0700
Thread-Topic: [MBONED] Question about multicast address to be used in documentation and example
Thread-Index: Acku0HDTqbvuI2WDQrCqyN5tGWr+kgABS7vP
Message-ID: <C51BD044.20386%leo.vegoda@icann.org>
In-Reply-To: <48F5FAD6.20401@uninett.no>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mboned-bounces@ietf.org
Errors-To: mboned-bounces@ietf.org

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.

Regards,

Leo

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

v2.23.0 | Report a Bug | By Email