IETF Logo Mail Archive

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

Leo Vegoda <leo.vegoda@icann.org> Fri, 17 October 2008 13:18 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 C10F23A67EE; Fri, 17 Oct 2008 06:18:45 -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 EF7823A67EE for <mboned@core3.amsl.com>; Fri, 17 Oct 2008 06:18:44 -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 4LwrXEa-chSj for <mboned@core3.amsl.com>; Fri, 17 Oct 2008 06:18:44 -0700 (PDT)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id 2519F3A6405 for <mboned@ietf.org>; Fri, 17 Oct 2008 06:18:44 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.233]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Fri, 17 Oct 2008 06:19:48 -0700
From: Leo Vegoda <leo.vegoda@icann.org>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>, Marshall Eubanks <tme@multicasttech.com>
Date: Fri, 17 Oct 2008 06:19:45 -0700
Thread-Topic: [MBONED] Question about multicast address to be used in documentation and example
Thread-Index: Acku12c5ZvSV3wR/TkejviuCWXmTBwAAPn3AAGCpF8Q=
Message-ID: <C51E5D91.20526%leo.vegoda@icann.org>
In-Reply-To: <A1F769BC58A8B146B2EEA818EAE052A2012949200B@GRFMBX702RM001.griffon.local>
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>, 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

On 15/10/2008 5:21, "Maglione Roberta" <roberta.maglione@telecomitalia.it>
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.

OK. If this language is OK we'll include it in
draft-ietf-mboned-rfc3171bis-03, which we'd like to publish as soon as
possible.

   233.252.0.0/24 - This block of multicast addresses is assigned as
   "MCAST-TEST-NET" for use in documentation and example code.
   It is often used in conjunction with domain names example.com
   or example.net in vendor and protocol documentation.  Addresses
   within this block should not appear on the public Internet.

Regards,

Leo Vegoda

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

v2.23.0 | Report a Bug | By Email