Re: draft-ietf-mboned-64-multicast-address-format
Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 14 August 2012 16:40 UTC
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B667D21F8771 for <ipv6@ietfa.amsl.com>; Tue, 14 Aug 2012 09:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.56
X-Spam-Level:
X-Spam-Status: No, score=-3.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 zfh5N-sbJVvD for <ipv6@ietfa.amsl.com>; Tue, 14 Aug 2012 09:40:35 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9606821F871E for <ipv6@ietf.org>; Tue, 14 Aug 2012 09:40:23 -0700 (PDT)
Received: by ggnh4 with SMTP id h4so749871ggn.31 for <ipv6@ietf.org>; Tue, 14 Aug 2012 09:40:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=BnCp7JlUhzvnZaW2HBbUISq/NT4FI2eQjxfpPoiLJ/k=; b=YDK7bbo+ZGEI1xDTmfhRiXHTWFfQbYRCNraXVkD4TBP64h5cPGYpxMnCUI2ZDAbMAY Qwwn+iQYBUNZddtMh7pXm8Y1yasE/qw4hd4lGn3H3mgPCcQQPoGVTdVgKbAgkATLzowe 7a0h7dsLV6NxKP2a9JroiuRhRU8GPkGux1gF+oKmcJ5sb+5tCuhUEncMYQ8qKop7TAWK Es9qzSFYQQRB3Ci4CfRDLTxo2ivb7nAOFKw5JEckX24mwNC7tGUIv54fhplcqOqo6ks8 k0IP4m2b8Kdo/l1orKyyYdJW/ddgSHjgB4n8KpHBQMIcNoPs7KpUPqVAak42XMqV1Akl ETEw==
MIME-Version: 1.0
Received: by 10.43.45.200 with SMTP id ul8mr13444932icb.36.1344962421036; Tue, 14 Aug 2012 09:40:21 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Tue, 14 Aug 2012 09:40:20 -0700 (PDT)
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E4FC2D8C2@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36E4FC2D8C2@PUEXCB1B.nanterre.francetelecom.fr>
Date: Tue, 14 Aug 2012 11:40:20 -0500
Message-ID: <CAC8QAccH-72K7P3fj-uJB7x5L9xYsLF3W6xXATdtXrT6HB8Krw@mail.gmail.com>
Subject: Re: draft-ietf-mboned-64-multicast-address-format
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: mohamed.boucadair@orange.com
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "draft-ietf-mboned-64-multicast-address-format@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format@tools.ietf.org>, Jacni Qin <jacni@jacni.com>, Stig Venaas <stig@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 16:40:35 -0000
On Tue, Aug 14, 2012 at 4:09 AM, <mohamed.boucadair@orange.com> wrote: > Dear all, > > I'm initiating this thread in the hope of understanding the > objections from the 6man WG and hopefully to make some progress for > this document. To initiate the discussion, below are provided some > preliminary Q/A: > > What is the scope of this document? > The document specifies an algorithmic translation of an IPv6 > multicast address to a corresponding IPv4 multicast address, and > vice versa. The document reserves two IPv6 multicast prefixes to > be used for that purpose. > > What are these reserved prefixes? > * ff3x:0:8000::/96 for SSM > * ffxx:8000::/20 for ASM > > Does this document update IPv6 addressing architecture? > No. > > Is there a unicast counterpart of this proposal? > Yes, RFC6052. > > What is the problem to be solved? > There are several use cases as detailed in [I-D.ietf-mboned-v4v6- > mcast-ps]. In particular, the following use cases are of > interest: > 1. An IPv6-only receiver wants to receive multicast content from > an IPv4-only source (6-4). > 2. An IPv4 receiver wants to join a multicast group in IPv4 > domain via an IPv6-only network (4-6-4). > > Are there solutions for the unicast counterpart of these use cases? > Yes; various solutions including: > 1. 6-4: RFC6146 > 2. 4-6-4: RFC6333, RFC6346, ... I don't understand why RFC 6333 is included here. If you take a look at http://tools.ietf.org/html/draft-sarikaya-softwire-dslitemulticast-01 there is no need for this draft. Related to this is this statement in the abstract: This algorithmic translation can be used in both IPv4-IPv6 translation or encapsulation schemes. I suggest removing encapsulation from the above sentence. I have concerns on the way this draft justifies these new prefixes. I think the justification should be completely based on translation. If this basis is taken, the rest of the text will flow naturally. Regards, Behcet
- draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- RE: draft-ietf-mboned-64-multicast-address-format Manfredi, Albert E
- Re: draft-ietf-mboned-64-multicast-address-format Marshall Eubanks
- Re: draft-ietf-mboned-64-multicast-address-format Bob Hinden
- Re: draft-ietf-mboned-64-multicast-address-format Tom Taylor
- Re: draft-ietf-mboned-64-multicast-address-format Marshall Eubanks
- RE: draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- Re: draft-ietf-mboned-64-multicast-address-format Bob Hinden
- RE: draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- Re: draft-ietf-mboned-64-multicast-address-format Bob Hinden
- Re: draft-ietf-mboned-64-multicast-address-format Jon Steen
- Re: draft-ietf-mboned-64-multicast-address-format Tom Taylor
- draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- Re: draft-ietf-mboned-64-multicast-address-format Bob Hinden
- Re: draft-ietf-mboned-64-multicast-address-format Behcet Sarikaya
- Re: draft-ietf-mboned-64-multicast-address-format Stig Venaas
- RE: draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- RE: draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- RE: draft-ietf-mboned-64-multicast-address-format mohamed.boucadair