Re: [Softwires] Call for reviewers draft-ietf-softwire-mesh-multicast

<mohamed.boucadair@orange.com> Mon, 25 April 2016 08:16 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E56B12D522 for <softwires@ietfa.amsl.com>; Mon, 25 Apr 2016 01:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.915
X-Spam-Level:
X-Spam-Status: No, score=-2.915 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RNT44ncPuNbi for <softwires@ietfa.amsl.com>; Mon, 25 Apr 2016 01:16:40 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D759412D4FB for <softwires@ietf.org>; Mon, 25 Apr 2016 01:16:39 -0700 (PDT)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 386BEC019E; Mon, 25 Apr 2016 10:16:38 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.75]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 09A0B1A006E; Mon, 25 Apr 2016 10:16:38 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe%19]) with mapi id 14.03.0279.002; Mon, 25 Apr 2016 10:16:37 +0200
From: <mohamed.boucadair@orange.com>
To: Ian Farrer <ianfarrer@gmx.com>, "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: [Softwires] Call for reviewers draft-ietf-softwire-mesh-multicast
Thread-Index: AQHRkOAGejSAQ+UaR0W3uNhoLmkdTJ+abUwQ
Date: Mon, 25 Apr 2016 08:16:37 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008D5F116@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <B5E05CB1-D4ED-457C-B383-824A52C99650@gmx.com>
In-Reply-To: <B5E05CB1-D4ED-457C-B383-824A52C99650@gmx.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/softwires/AYtpoMARJ5Rr0RZh4kUbbImGoyQ>
Subject: Re: [Softwires] Call for reviewers draft-ietf-softwire-mesh-multicast
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Apr 2016 08:16:41 -0000

Hi Ian, all,

I have the following comments about this draft:

* This draft covers two cases: IPv4-over-IPv6 and IPv6-over-IPv4. I see a potential overlap with draft-ietf-softwire-dslite-multicast (that passed the WGLC) for the IPv4-over-IPv6 case. Unless there are some differences between these two documents for this case, I suggest to scope draft-ietf-softwire-mesh-multicast to focus on the IPv6-over-IPv4 and add a pointer to draft-ietf-softwire-dslite-multicast. Otherwise, it would be helpful to identify the differences between the two documents. 

* The following section points to RFC7371. I think the authors meant https://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-06.   

==
4.2.  Group Address Mapping

   For IPv4-over-IPv6 scenario, a simple algorithmic mapping between
   IPv4 multicast group addresses and IPv6 group addresses is supported.
   [RFC7371] has already defined an applicable format.  Figure 4 is the
   reminder of the format:


     +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
     | 0-------------32--40--48--56--64--72--80--88--96-----------127|
     +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
     |                    MPREFIX64                  |group  address |
     +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+


           Figure 4: IPv4-Embedded IPv6 Multicast Address Format

   The MPREFIX64 for SSM mode is also defined in [RFC7371] :

   o  ff3x:0:8000::/96 ('x' is any valid scope)
==  

Thank you.

Cheers,
Med

> -----Message d'origine-----
> De : Softwires [mailto:softwires-bounces@ietf.org] De la part de Ian
> Farrer
> Envoyé : jeudi 7 avril 2016 16:59
> À : softwires@ietf.org
> Objet : [Softwires] Call for reviewers draft-ietf-softwire-mesh-multicast
> 
> Hi,
> 
> This document has been around for some time, but has not received any
> substantive reviews. Can I ask for volunteers who are willing to provide
> reviews?
> 
> Thanks,
> Ian
> 
> 
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires