Re: [Int-dir] Int-Dir Review of draft-ietf-softwire-dslite-multicast-12

<mohamed.boucadair@orange.com> Wed, 14 December 2016 12:32 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6ECE129A6C; Wed, 14 Dec 2016 04:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.815
X-Spam-Level:
X-Spam-Status: No, score=-4.815 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.896, 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 f845chjriO_E; Wed, 14 Dec 2016 04:32:46 -0800 (PST)
Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1551129A69; Wed, 14 Dec 2016 04:32:43 -0800 (PST)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 3259E6019F; Wed, 14 Dec 2016 13:32:42 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.43]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id 05C39600D7; Wed, 14 Dec 2016 13:32:42 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM5F.corporate.adroot.infra.ftgroup ([fe80::e172:f13e:8be6:71cc%18]) with mapi id 14.03.0319.002; Wed, 14 Dec 2016 13:32:41 +0100
From: mohamed.boucadair@orange.com
To: "Lee, Yiu" <Yiu_Lee@comcast.com>, Zhen Cao <zhencao.ietf@gmail.com>, "draft-ietf-softwire-dslite-multicast@tools.ietf.org" <draft-ietf-softwire-dslite-multicast@tools.ietf.org>
Thread-Topic: Int-Dir Review of draft-ietf-softwire-dslite-multicast-12
Thread-Index: AQHSVb3ZJIX3QLFgBkyggyBl7cSKwqEHYHZA
Date: Wed, 14 Dec 2016 12:32:40 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009DCCF0A@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <CAFxP68zBZ5+X8nLhtTOEcrA6c_kYhObd-8M_qQjA+Qw0gzuLQQ@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009DCBF87@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <4D6A4BB7-05A8-4C31-AF8D-7D71045323B5@comcast.com>
In-Reply-To: <4D6A4BB7-05A8-4C31-AF8D-7D71045323B5@comcast.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.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/30qxyJ793N0R5wh_pemdRliGECI>
Cc: "int-ads@ietf.org" <int-ads@ietf.org>, "int-dir@ietf.org" <int-dir@ietf.org>
Subject: Re: [Int-dir] Int-Dir Review of draft-ietf-softwire-dslite-multicast-12
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2016 12:32:47 -0000

Hi Yiu, 

I think that we are saying the same thing. 

As agreed with Zhen, no change is required to the current text. 

Cheers,
Med

> -----Message d'origine-----
> De : Lee, Yiu [mailto:Yiu_Lee@comcast.com]
> Envoyé : mercredi 14 décembre 2016 04:55
> À : BOUCADAIR Mohamed IMT/OLN; Zhen Cao; draft-ietf-softwire-dslite-
> multicast@tools.ietf.org
> Cc : int-ads@ietf.org; int-dir@ietf.org
> Objet : Re: Int-Dir Review of draft-ietf-softwire-dslite-multicast-12
> 
> Hi Med and Zhen,
> 
> Actually mB4 doesn’t need to do any check. Once decap is done, it will use
> the standard IPv4 mcast forwarding rule. If the v4 group address is in the
> mroute table, it will be forwarded, if not, it will be dropped. I propose
> the following:
> 
> When the mB4 receives an IP multicast packet, it MUST check the group
> address and the source address. If the IPv6 multicast group prefix is
> mPrefix64 and IPv6 source prefix is uPrefix64, the mB4 MUST decapsulate
> the IPv6 header. The decapsulated IPv4 multicast packet will be forwarded
> based on standard IPv4 multicast forwarding rule.
> 
> Thanks,
> Yiu
> 
> On 12/12/16, 1:45 AM, "mohamed.boucadair@orange.com"
> <mohamed.boucadair@orange.com> wrote:
> 
>     >
>     >b)
>     >6.2.  Multicast Data Forwarding
>     >   When the mB4 receives an IPv6 multicast packet, it MUST check the
>     >    group address and the source address.  If the IPv6 multicast
> group
>     >    prefix is mPrefix64 and the IPv6 source prefix is uPrefix64, the
> mB4
>     >    MUST decapsulate the IPv6 header and forward the IPv4 multicast
>     >    packet through each relevant interface.  Otherwise, the mB4 MUST
>     >    silently drop the packet.
>     >comments: the mB4 not only needs to check the validity of mPrefix and
>     >uPrefix, but also needs to check if there exists an associated
>     >MLD/IGMP requests from that prefixes.  Only if there was an IGMP
>     >report associted with this transaction, it will forward such
> multicast
>     >packets.
>     [Med] This is actually the intent of the last part of the text you
> quoted:
> 
>        prefix is mPrefix64 and the IPv6 source prefix is uPrefix64, the
> mB4
>        MUST decapsulate the IPv6 header and forward the IPv4 multicast
>        packet through each relevant interface.
>        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
>     If no state is found, there won't be any "relevant interface". So the
> traffic won't be forwarded.
>