[multrans] Clarification question about Problem Statement and Use Cases draft
Maglione Roberta <roberta.maglione@telecomitalia.it> Tue, 23 August 2011 07:47 UTC
Return-Path: <roberta.maglione@telecomitalia.it>
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 4F82821F86DD for <multrans@ietfa.amsl.com>;
Tue, 23 Aug 2011 00:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.238
X-Spam-Level: *
X-Spam-Status: No, score=1.238 tagged_above=-999 required=5 tests=[AWL=-0.457,
BAYES_40=-0.185, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QSfaubCwLG4U for
<multrans@ietfa.amsl.com>; Tue, 23 Aug 2011 00:47:47 -0700 (PDT)
Received: from GRFEDG702BA020.telecomitalia.it
(grfedg702ba020.telecomitalia.it [156.54.233.201]) by ietfa.amsl.com
(Postfix) with ESMTP id 86FE721F8620 for <multrans@ietf.org>;
Tue, 23 Aug 2011 00:47:47 -0700 (PDT)
Received: from GRFHUB703BA020.griffon.local (10.188.101.113) by
GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server
(TLS) id 8.2.254.0; Tue, 23 Aug 2011 09:48:52 +0200
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by
GRFHUB703BA020.griffon.local ([10.188.101.113]) with mapi;
Tue, 23 Aug 2011 09:48:52 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: "'multrans@ietf.org'" <multrans@ietf.org>
Date: Tue, 23 Aug 2011 09:48:52 +0200
Thread-Topic: Clarification question about Problem Statement and Use Cases
draft
Thread-Index: AcxhaRlrFggMTacCSO21470vfvxz1w==
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3EB5E53D91@GRFMBX704BA020.griffon.local>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, it-IT
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Ullio Mario <mario.ullio@telecomitalia.it>
Subject: [multrans] Clarification question about Problem Statement and Use
Cases draft
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: Tue, 23 Aug 2011 07:47:48 -0000
Hello, I have a question about the prioritization of the scenarios described in draft draft-jaclee-behave-v4v6-mcast-ps: Section 3.2 "IPv6 Receiver and Source Connected to an IPv4-Only Network" says that 6-4-6 scenario according to the BEHAVE WG is of lower priority, I would like to better understand why. In my opinion "IPv6 Receiver and Source Connected to an IPv4-Only Network" use case could also cover the scenario where both receivers and source are IPv6 and they get IPv6 unicast connectivity from an IPv4 network by using 6PE solution (for unicast traffic). If I am not wrong this use case does not belong to behave discussion, but I believe that having a multicast equivalent solution for 6PE may be useful for a Service Provider that would like to start offering IPv6 multicast keeping his own backbone network in IPv4. I would appreciate your comments. Thanks, Best regards, Roberta Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
- [multrans] Clarification question about Problem S… Maglione Roberta
- Re: [multrans] Clarification question about Probl… Lee, Yiu
- Re: [multrans] Clarification question about Probl… Maglione Roberta
- Re: [multrans] Clarification question about Probl… Lee, Yiu
- Re: [multrans] Clarification question about Probl… Maglione Roberta
- Re: [multrans] Clarification question about Probl… Tina TSOU
- Re: [multrans] Clarification question about Probl… Lee, Yiu
- Re: [multrans] Clarification question about Probl… Greg Shepherd