IETF Logo Mail Archive

Re: [v6ops] transition-ipv4aas: IPv4 Multicast

<mohamed.boucadair@orange.com> Thu, 26 April 2018 05:32 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD3B120725 for <v6ops@ietfa.amsl.com>; Wed, 25 Apr 2018 22:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 fd8LOa8-5iTo for <v6ops@ietfa.amsl.com>; Wed, 25 Apr 2018 22:32:24 -0700 (PDT)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCBFB1205F0 for <v6ops@ietf.org>; Wed, 25 Apr 2018 22:32:23 -0700 (PDT)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 4B85360B49; Thu, 26 Apr 2018 07:32:22 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.62]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 331F418007E; Thu, 26 Apr 2018 07:32:22 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM5E.corporate.adroot.infra.ftgroup ([fe80::2912:bfa5:91d3:bf63%18]) with mapi id 14.03.0389.001; Thu, 26 Apr 2018 07:32:22 +0200
From: mohamed.boucadair@orange.com
To: "STARK, BARBARA H" <bs7652@att.com>, V6 Ops List <v6ops@ietf.org>
Thread-Topic: [v6ops] transition-ipv4aas: IPv4 Multicast
Thread-Index: AdPcxdfgRGiwtZ8bRoKsQ9J1PFTp6gAWfqNg
Date: Thu, 26 Apr 2018 05:32:21 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DF11C99@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <2D09D61DDFA73D4C884805CC7865E6114DD80E6E@GAALPA1MSGUSRBF.ITServices.sbc.com>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DD80E6E@GAALPA1MSGUSRBF.ITServices.sbc.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.2]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/kPjwDmEhAFzuvzwd3MnDJQujpEo>
Subject: Re: [v6ops] transition-ipv4aas: IPv4 Multicast
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Apr 2018 05:32:25 -0000

Hi Barbara, 

Your alternate wording works for me. 

Cheers,
Med

> -----Message d'origine-----
> De : v6ops [mailto:v6ops-bounces@ietf.org] De la part de STARK, BARBARA H
> Envoyé : mercredi 25 avril 2018 21:01
> À : V6 Ops List
> Objet : [v6ops] transition-ipv4aas: IPv4 Multicast
> 
> The transition-ipv4aas draft has the following section:
> 
> 6.  IPv4 Multicast Support
>    Actual deployments support IPv4 multicast for services such as IPTV.
>    In the transition phase it is expected that multicast services will
>    still be provided using IPv4 to the customer LANs.
>    In order to support the delivery of IPv4 multicast services to IPv4
>    clients over an IPv6 multicast network, the IPv6 Transition CE router
>    SHOULD support [RFC8114] and [RFC8115].
> 
> WAN to LAN IPv4 Multicast (such as used for delivery of IPTV) is not
> supported by many IPv4 CE routers today. Those that do "support" IPv4
> multicast often do it poorly. Since I do not believe IPv4 CE routers, in
> general, should or can be expected to support delivery of IPv4 multicast
> services, I disagree that an IPv6 Transition CE Routers SHOULD support
> delivery of IPv4 multicast services. I suggest removing this entire section.
> 
> Alternately, rephrase to say "If the IPv6 Transition CE Router supports
> delivery of IPv4 multicast services, then it SHOULD (MUST?) support [RFC8114]
> and [RFC8115]."
> 
> Barbara
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email