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

Stig Venaas <stig.venaas@uninett.no> Wed, 15 October 2008 14:13 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 2D67E28C131; Wed, 15 Oct 2008 07:13:52 -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 9C45D28C131 for <mboned@core3.amsl.com>; Wed, 15 Oct 2008 07:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 Xm4+-kFP-rnr for <mboned@core3.amsl.com>; Wed, 15 Oct 2008 07:13:50 -0700 (PDT)
Received: from tyholt.uninett.no (tyholt.uninett.no [IPv6:2001:700:1::eecb]) by core3.amsl.com (Postfix) with ESMTP id 9F3C528C12D for <mboned@ietf.org>; Wed, 15 Oct 2008 07:13:49 -0700 (PDT)
Received: from [IPv6?2001?700?1?0?215?f2ff?fe35?307d] (sverresborg.uninett.no [IPv6:2001:700:1:0:215:f2ff:fe35:307d]) by tyholt.uninett.no (Postfix) with ESMTP id 493602BACD1; Wed, 15 Oct 2008 16:14:46 +0200 (CEST)
Message-ID: <48F5FAD6.20401@uninett.no>
Date: Wed, 15 Oct 2008 16:14:46 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.17 (X11/20081007)
MIME-Version: 1.0
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
References: <A1F769BC58A8B146B2EEA818EAE052A20129492004@GRFMBX702RM001.griffon.local>
In-Reply-To: <A1F769BC58A8B146B2EEA818EAE052A20129492004@GRFMBX702RM001.griffon.local>
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

Maglione Roberta wrote:
> Hello,
>         I'm currently cleaning up my multicast ietf draft but I have the problem:
> the ietf tool for draft error check is complaing, with the error below, because in the draft I'm using a multicast add (from the Administratively Scoped block) as an example.
> 
> "Found possible IPv4 address '239.23.2.2' in position 55; this doesn't match RFC3330's suggested 192.0.2.0/24 address range. "
> 
> 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 :)

Or if perhaps draft-ietf-mboned-ipv4-uni-based-mcast-05.txt ever gets
approved you could use unicast based addresses from 192.0.2.0/24 or
something...

But I guess assigning a specific multicast prefix would be good,

Stig

> Thank you in advance.
> Best Regards,
> Roberta
> 
> 
> 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

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