Re: [MBONED] MLTRANS work and draft-ietf-mboned-v4v6-mcast-ps

Tom Taylor <tom.taylor.stds@gmail.com> Thu, 09 August 2012 23:32 UTC

Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B24421F8672 for <mboned@ietfa.amsl.com>; Thu, 9 Aug 2012 16:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 UDhv3x-U1fJZ for <mboned@ietfa.amsl.com>; Thu, 9 Aug 2012 16:32:37 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id E1AB121F8667 for <mboned@ietf.org>; Thu, 9 Aug 2012 16:32:30 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so1665427pbb.31 for <mboned@ietf.org>; Thu, 09 Aug 2012 16:32:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding:x-antivirus :x-antivirus-status; bh=2j39qPgQwU1eZsFniNuC3k1XrDNB9/29bhkeAIk/Y6k=; b=QfwaE2Nn4DMsDeRC3SAO7Ix0JNnKXQ+0s/Wdk1pK3T5ie3uSJRIr0mAVeZluhd4Bzn fhN0bBwMNtKRV1lxN4vqSAUZ3ktIwmmPVKVKn50wkN9i/CvPHcCFTD45Xa+cAtTwwOTn DA04NkluwrKOnwF5GgZh00W86d1nLO/xs7C+5O91Wfq99HYuuuFNoQPWQyDfAzwQ4i7U RYkFeGxb6KwX5B8lR+RjAPyD0M06dSFli8MalAu4eF5shw2nuMvsqzmhATqVlWNxXPj/ smWSQueQuMWYGwHWSEP+GW4C98WF9h/zjW8a4gv3u5So3d/s7Aqdox9Qg41E2O/A4A1G WFxg==
Received: by 10.68.231.163 with SMTP id th3mr7718553pbc.55.1344555150624; Thu, 09 Aug 2012 16:32:30 -0700 (PDT)
Received: from [127.0.0.1] ([199.246.39.165]) by mx.google.com with ESMTPS id rx7sm2015144pbc.64.2012.08.09.16.32.28 (version=SSLv3 cipher=OTHER); Thu, 09 Aug 2012 16:32:29 -0700 (PDT)
Message-ID: <50244888.6070402@gmail.com>
Date: Thu, 09 Aug 2012 19:32:24 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: mboned@ietf.org
References: <13205C286662DE4387D9AF3AC30EF456D77189AFEB@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D77189AFEB@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120809-0, 09/08/2012), Outbound message
X-Antivirus-Status: Clean
Subject: Re: [MBONED] MLTRANS work and draft-ietf-mboned-v4v6-mcast-ps
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 23:32:38 -0000

For the record, I sent the following E-mail to the NANOG list, and will
send it to others as I track them down:

Subject: IPTV, Multicast, and IPv6 Transition

This may be way off in the future for some of you, or others may be past 
it. In support of possible work on IPv6 transition in the IETF MBONED 
Working Group, I'm looking for an indication of what use cases are 
realistic for operators who:

-- deliver IPTV to their customers
-- use multicast for the purpose, either now or in the near future
-- are making the transition from IPv4 to IPv6.

First question: does anyone anticipate a situation where you will have 
to translate multicast content from an IPv4-only source so it can be 
delivered to an IPv6-only receiver, or vice versa?

Second question: the current official view is that dual stack is the 
sensible way to transition your network, and failing that, you can use 
Automatic Multicast Tunneling, an almost-ready Internet Draft available at

     http://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/

to tunnel multicast packets through a single-stack network when 
necessary. Do you consider your requirements adequately addressed by 
this view?

People who really want to be helpful can comment on the problem 
statement and use cases documented in

     http://datatracker.ietf.org/doc/draft-ietf-mboned-v4v6-mcast-ps/

Thanks for your attention. Privacy will be respected if people want to 
reply privately.

Tom Taylor
Consultant


On 08/08/2012 12:07 PM, Ronald Bonica wrote:
> Folks,
>
> All of the MLTRANS work, and in particular, the MLTRANS addressing
> work, seems to be in a holding pattern waiting for consensus around
> draft-ietf-mboned-v4v6-mcast-ps. In order to reach consensus, we need
> to determine which use cases are likely to see deployment.
>
> Could someone associated with the MLTRANS work be willing to bring
> draft-ietf-mboned-v4v6-mcast-ps to the attention of the NANOG and
> RIPE mailing lists so that we can get feedback from the larger
> operational community? This feedback will inform our next step.
>
> In Vancouver, somebody offered to do this, but I can't remember who.
>
> -------------------------- Ron Bonica vcard:
> www.bonica.org/ron/ronbonica.vcf
>
>
> _______________________________________________ MBONED mailing list
> MBONED@ietf.org https://www.ietf.org/mailman/listinfo/mboned
>