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

Marshall Eubanks <tme@multicasttech.com> Wed, 15 October 2008 14:47 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 0D3153A6C4C; Wed, 15 Oct 2008 07:47:47 -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 E759A3A6B81 for <mboned@core3.amsl.com>; Wed, 15 Oct 2008 07:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.279
X-Spam-Level:
X-Spam-Status: No, score=-103.279 tagged_above=-999 required=5 tests=[AWL=0.320, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 YWv3poY7MJpG for <mboned@core3.amsl.com>; Wed, 15 Oct 2008 07:47:40 -0700 (PDT)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 4141A3A68CC for <mboned@ietf.org>; Wed, 15 Oct 2008 07:47:40 -0700 (PDT)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 13393266; Wed, 15 Oct 2008 10:48:39 -0400
Message-Id: <F8DF1DF1-C7A6-4BB0-A3CF-09924BD9CD5E@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: Stig Venaas <stig.venaas@uninett.no>
In-Reply-To: <48F5FAD6.20401@uninett.no>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 15 Oct 2008 10:48:38 -0400
References: <A1F769BC58A8B146B2EEA818EAE052A20129492004@GRFMBX702RM001.griffon.local> <48F5FAD6.20401@uninett.no>
X-Mailer: Apple Mail (2.929.2)
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"; DelSp="yes"
Sender: mboned-bounces@ietf.org
Errors-To: mboned-bounces@ietf.org

On Oct 15, 2008, at 10:14 AM, Stig Venaas wrote:

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

Do you mean a specific prefix just for examples, like "example.com" ?  
Obviously, that couldn't
come from 239/8, but I like the idea of setting aside an example range  
in eGLOP, which could be added to

draft-ietf-mboned-rfc3171bis-04

Do others on list agree with this idea ?

Regards
Marshall

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

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