Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt

<mohamed.boucadair@orange.com> Thu, 16 August 2012 05:55 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E61AC21F844F for <mboned@ietfa.amsl.com>; Wed, 15 Aug 2012 22:55:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.035
X-Spam-Level:
X-Spam-Status: No, score=-2.035 tagged_above=-999 required=5 tests=[AWL=0.213, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N-3BlFUx03Xa for <mboned@ietfa.amsl.com>; Wed, 15 Aug 2012 22:55:26 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id CED2021F844E for <mboned@ietf.org>; Wed, 15 Aug 2012 22:55:25 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 251E4324276; Thu, 16 Aug 2012 07:55:25 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 0AFC34C015; Thu, 16 Aug 2012 07:55:25 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Thu, 16 Aug 2012 07:55:07 +0200
From: mohamed.boucadair@orange.com
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, Stig Venaas <stig@venaas.com>
Date: Thu, 16 Aug 2012 07:55:06 +0200
Thread-Topic: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
Thread-Index: Ac16PYN273/6hs4GReGltv8h/E17qQBNhO3Q
Message-ID: <94C682931C08B048B7A8645303FDC9F36E4FC2D9E2@PUEXCB1B.nanterre.francetelecom.fr>
References: <CAC8QAcdJ-u_XrWQ=soNL9rMykMD4W4oxsZrGDBdFcMU8t2ebqg@mail.gmail.com> <502975B9.30403@innovationslab.net> <50298B3E.2020207@venaas.com> <CAC8QAcc4V3x=AG+XC-bOupkKzyfOTJDR2b=RBiJBgojd7A9LaA@mail.gmail.com>
In-Reply-To: <CAC8QAcc4V3x=AG+XC-bOupkKzyfOTJDR2b=RBiJBgojd7A9LaA@mail.gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.8.16.22416
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Thu, 16 Aug 2012 05:55:27 -0000

Hi Behcet,

I updated my local copy to take into account your comment. Thanks.

Cheers,
Med 

>-----Message d'origine-----
>De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] 
>De la part de Behcet Sarikaya
>Envoyé : mardi 14 août 2012 18:55
>À : Stig Venaas
>Cc : mboned@ietf.org
>Objet : Re: [MBONED] 
>draft-ietf-mboned-64-multicast-address-format-03.txt
>
>On Mon, Aug 13, 2012 at 6:18 PM, Stig Venaas <stig@venaas.com> wrote:
>> On 13.08.2012 14:46, Brian Haberman wrote:
>>>
>>> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>>>>
>>>> Hi authors,
>>>>
>>>> Thanks for the revised draft, I find that the revision is 
>in the right
>>>> direction.
>>>>
>>>> I am confused on the prefix lengths:
>>>> on Figure 2,
>>>> ffxx:8000:0:abc::/96
>>>> while in Section 3.1
>>>> ffxx:8000::/20
>>>>
>>>
>>> The x's correspond to the flags and scope fields within the 
>multicast
>>> address.  Take a look at:
>>>
>>>
>>> 
>http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-m
>ulticast-addresses.xml#ipv6-multicast-addresses-4
>>
>>
>> We have one minor issue here though. They cannot simply be IANA
>> allocations, since they would not have the transient bit set. In
>> this case, the idea is that it should work for flag nibble values
>> like 1, 3 and 7. Actually I believe the transient bit should always
>> be set for these groups.
>
>I think it will be better to clarify in the draft saying that xx
>corresponds to flgs and scop fields defined in RFC 3306.
>
>Regards,
>
>Behcet
>
>>
>> Stig
>>
>>
>>>
>>>
>>>> How come these are reserved prefixes?
>>>> What are the values that are reserved?
>>>>
>>>> If you look at RFC 6052, the unicast translation specification,
>>>> 64:ff9b::/96 is defined as the Well-Known Prefix. There 
>are no x's in
>>>> the prefix definition.
>>>>
>>>> Regards,
>>>>
>>>> Behcet
>>>>
>>>> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>>>>
>>>>>
>>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>>> directories.
>>>>>   This draft is a work item of the MBONE Deployment 
>Working Group of
>>>>> the IETF.
>>>>>
>>>>>          Title           : IPv6 Multicast Address With 
>Embedded IPv4
>>>>> Multicast Address
>>>>>          Author(s)       : Mohamed Boucadair
>>>>>                            Jacni Qin
>>>>>                            Yiu L. Lee
>>>>>                            Stig Venaas
>>>>>                            Xing Li
>>>>>                            Mingwei Xu
>>>>>          Filename        :
>>>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>>>          Pages           : 13
>>>>>          Date            : 2012-08-09
>>>>>
>>>>> Abstract:
>>>>>     This document reserves two IPv6 multicast prefixes to 
>be used in the
>>>>>     context of IPv4-IPv6 interconnection.  The document 
>specifies an
>>>>>     algorithmic translation of an IPv6 multicast address to a
>>>>>     corresponding IPv4 multicast address, and vice versa.  This
>>>>>     algorithmic translation can be used in both IPv4-IPv6 
>translation or
>>>>>     encapsulation schemes.
>>>>>
>>>>>
>>>>>
>>>>> The IETF datatracker status page for this draft is:
>>>>>
>>>>> 
>https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast
>-address-format
>>>>>
>>>>>
>>>>> There's also a htmlized version available at:
>>>>>
>>>>> 
>http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-addre
>ss-format-03
>>>>>
>>>>>
>>>>> A diff from the previous version is available at:
>>>>>
>>>>> 
>http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast
>-address-format-03
>>>>>
>>>>>
>>>>>
>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>
>>
>> _______________________________________________
>> 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
>