IETF Logo Mail Archive

Re: [multrans] Draft Multrans BoF request

<mohamed.boucadair@orange-ftgroup.com> Fri, 10 June 2011 06:55 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: multrans@ietfa.amsl.com
Delivered-To: multrans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3490311E808A for <multrans@ietfa.amsl.com>; Thu, 9 Jun 2011 23:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level:
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, 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 hvhLEn3mKWnZ for <multrans@ietfa.amsl.com>; Thu, 9 Jun 2011 23:55:15 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD6A11E8084 for <multrans@ietf.org>; Thu, 9 Jun 2011 23:55:14 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 920ED18C502; Fri, 10 Jun 2011 08:53:56 +0200 (CEST)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 6AE1727C054; Fri, 10 Jun 2011 08:53:56 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Fri, 10 Jun 2011 08:53:56 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: Tina Tsou <tena@huawei.com>, "multrans@ietf.org" <multrans@ietf.org>
Date: Fri, 10 Jun 2011 08:53:55 +0200
Thread-Topic: [multrans] Draft Multrans BoF request
Thread-Index: AcwklYM01/VtPbTlQqqyEc7aBoR9LAAABE8gAKlFa8A=
Message-ID: <94C682931C08B048B7A8645303FDC9F33E50162487@PUEXCB1B.nanterre.francetelecom.fr>
References: <027f01cc2495$8596a070$90c3e150$@com> <028001cc2495$f1496d70$d3dc4850$@com>
In-Reply-To: <028001cc2495$f1496d70$d3dc4850$@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.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.6.10.53315
Cc: 'Jari Arkko' <jari.arkko@piuha.net>
Subject: Re: [multrans] Draft Multrans BoF request
X-BeenThere: multrans@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discuss the work of IPv4-IPv6 multicast." <multrans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multrans>, <mailto:multrans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multrans>
List-Post: <mailto:multrans@ietf.org>
List-Help: <mailto:multrans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multrans>, <mailto:multrans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 06:55:16 -0000

Hi Tina, all,

I would propose to keep one single slot to discuss the issues and requirements.

Furthermore, a slot to present the scope (http://tools.ietf.org/html/draft-jaclee-behave-v4v6-mcast-ps-02#section-2.1) and the list of work items should be added (see http://tools.ietf.org/html/draft-jaclee-behave-v4v6-mcast-ps-02#section-5)

Cheers,
Med
 

-----Message d'origine-----
De : multrans-bounces@ietf.org [mailto:multrans-bounces@ietf.org] De la part de Tina Tsou
Envoyé : mardi 7 juin 2011 00:06
À : multrans@ietf.org
Cc : 'Jari Arkko'
Objet : Re: [multrans] Draft Multrans BoF request

Hi all,
A small nit, 
.	Requirements and issues (TBD, 15 min)
should be
.	Requirements (TBD, 15 min)

It is updated below.

In current deployments, the IP multicast forwarding scheme is used by many
providers to deliver some services, such as live TV broadcasting.
Transition to IPv6 raises issues and corresponding requirements. In
particular, IPv4 service continuity is an essential requirement from a
business perspective. 
This specifically includes continued receiver access to IPv4-formatted
contents even when the assignment of a dedicated global IPv4 address to the
receiver is no longer possible and even after the receivers have migrated to
IPv6. 
Likewise, the delivery of IPv6-formatted contents to IPv4 receivers must
also be possible.
Multicast transition scenarios include the ability to access IPv4-formatted
multicast contents from an IPv4 receiver over an IPv6-only network and the
ability to access IPv4-formatted multicast contents from an IPv6-only
receiver.
The aforementioned issues can be classified into:
.	Multicast group and source discovery procedures
.	Multicast group subscription procedures
.	Multicast tree computation
.	Required IPv4-IPv6 multicast inter-working functions
The proposed BoF session aims at discussing and hopefully validating the
need for the IETF to work on these issues.
The proposed agenda for the BoF session goes like this:
.	Welcome introduction and agenda bashing (chairs, 10 min)
.	Multicast transition scenarios (TBD, 20 min)
.	Requirements (TBD, 15 min)
.	Issues (TBD, 15 min)
.	Discussion (all, 20 min)
.	Conclusion and next steps (chairs, ADs, 10 min)
Reading material:
http://tools.ietf.org/html/draft-jaclee-behave-v4v6-mcast-ps-02"
 
BoF chairs should include one rep from the service provider's community.


We keep our promises with one another - no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html




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

v2.8.7 | Report a Bug | By Email