Re: draft-ietf-mboned-64-multicast-address-format

Bob Hinden <bob.hinden@gmail.com> Tue, 14 August 2012 15:33 UTC

Return-Path: <bob.hinden@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 AC8AA21F8582 for <ipv6@ietfa.amsl.com>; Tue, 14 Aug 2012 08:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.677
X-Spam-Level:
X-Spam-Status: No, score=-103.677 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 iuh0H-Iqlsrm for <ipv6@ietfa.amsl.com>; Tue, 14 Aug 2012 08:33:51 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id E80A921F8514 for <ipv6@ietf.org>; Tue, 14 Aug 2012 08:33:50 -0700 (PDT)
Received: by eekb45 with SMTP id b45so207549eek.31 for <ipv6@ietf.org>; Tue, 14 Aug 2012 08:33:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=B1rtOm8b+K5Xx+ARzStlgd7XBQ2tnoI6VMvYVe7uIsQ=; b=AlFaKwb2tMbitTZzupiiyXZ4hX/0IYyH9/3XVF7JdX5FCt6eeuGcAn5bWmKl8ouXdh 2j9nDw/wYb/XKHRgqrJSEnJryA4ArEYrFtFqaai25Gt7lIq+7riVlOiSXhDO37iO6s0j EaXZzSDfkxY16kv4PwhjVQe6xJfDkNsJuDmvUsjJYQ8ocJHK5GMWi5D8IcwzGskKsgsg zV5leISb9VhHKksHPr/iEVbcnrepSIleIvsynYU7XSh3kSpSVvgHSL+AGi5KO3gkWdjE CJL4u2W9h1K/Om8xbmv7u/SixmBM/pe/7voPhHxQYcLnr0KFk+dWIVhjkGQTS7bTU6Z1 t5Mw==
Received: by 10.14.206.200 with SMTP id l48mr19965558eeo.41.1344958430155; Tue, 14 Aug 2012 08:33:50 -0700 (PDT)
Received: from ?IPv6:2601:9:4080:10:8047:2250:7163:4297? ([2601:9:4080:10:8047:2250:7163:4297]) by mx.google.com with ESMTPS id h2sm7798567eeo.3.2012.08.14.08.33.21 (version=SSLv3 cipher=OTHER); Tue, 14 Aug 2012 08:33:48 -0700 (PDT)
Subject: Re: draft-ietf-mboned-64-multicast-address-format
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: text/plain; charset="us-ascii"
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E4FC2D8C2@PUEXCB1B.nanterre.francetelecom.fr>
Date: Tue, 14 Aug 2012 08:33:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C0172054-000E-42AA-9968-5AC37CA57BA4@gmail.com>
References: <94C682931C08B048B7A8645303FDC9F36E4FC2D8C2@PUEXCB1B.nanterre.francetelecom.fr>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.1280)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "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
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 15:33:51 -0000

Med,

The new draft appears to have many changes from the previous version.  It would be helpful if you could describe the changes.  This is usually done in the draft itself, but I didn't see it in -03.

Thanks,
Bob

On Aug 14, 2012, at 2:09 AM, <mohamed.boucadair@orange.com> <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, ...
>  
> The latest version of the document is available at:
> https://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-03.
>  
> Comments and suggestions are more than welcome.
>  
> Cheers,
> Med 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------