Re: [multrans] Draft Multrans 2nd BoF request

"Spencer Dawkins" <spencer@wonderhamster.org> Wed, 14 September 2011 15:10 UTC

Return-Path: <spencer@wonderhamster.org>
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 7904821F8CB3 for <multrans@ietfa.amsl.com>; Wed, 14 Sep 2011 08:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.988
X-Spam-Level:
X-Spam-Status: No, score=-101.988 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, STOX_REPLY_TYPE=0.001, 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 DyKf4ERFHNBR for <multrans@ietfa.amsl.com>; Wed, 14 Sep 2011 08:10:44 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 209DE21F8B61 for <multrans@ietf.org>; Wed, 14 Sep 2011 08:10:44 -0700 (PDT)
Received: from S73602b ([50.58.7.243]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MHGpv-1QrXKE35DH-00DkfK; Wed, 14 Sep 2011 11:12:51 -0400
Message-ID: <84062BDB236B4F2EB392E782A1AC4DD8@china.huawei.com>
From: Spencer Dawkins <spencer@wonderhamster.org>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, multrans@ietf.org
References: <C0E0A32284495243BDE0AC8A066631A88A7A9A@szxeml526-mbs.china.huawei.com>
Date: Wed, 14 Sep 2011 10:12:49 -0500
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Provags-ID: V02:K0:UAk1Xlk/nlIma6H7LMkMM1FzOKhQ1349iNtAdRXodXW t3s99hRsfi9otS/Zo405KSeVvdk3+XnKjae3wH/4NSP84oklAl llD36oLKNynki2p9YqGBiqpqBDiCAOu+gMqwmY1LsZGTrOc9Bv +vd9pVb1UqtaJ35NXM1nIUwIqnkho90VwKb0LVc2pAuWdz5RIZ KKabOIGSVB9yaxQW38wQrX3uYYWf0tl9wpQ7R2GYOwHlPJcx3V 0rJpy1PLl4dkMbWVtBj2ac6AkBDV9ISuikGsL5bXnxmZ5RTD2v EaMjAKmi6M44/pHT4loZbz1FLJRLeJ8AGj1Gy/wXjuzOZL9T4o H/1cclse0DydkS4FDd3ECc4wqGmsBPoTRk4PO08fp
Subject: Re: [multrans] Draft Multrans 2nd 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: Wed, 14 Sep 2011 15:10:57 -0000

(Speaking as individual)

Just as a schedule check, the cutoff date for IETF 82 BOF requests is 10/03 
(according to http://www.ietf.org/meeting/cutoff-dates-2011.html#IETF82). 
The only response I've seen to this proposal was from Dan Wing, asking that 
BEHAVE be added to the first-priority conflict list.

Are there any other suggestions that people would like to make? If so, it 
might be great to say something before the BOF request goes in.

Thanks,

Spencer (as individual)

> Hi all,
> This is draft Multrans 2nd BoF request. Comments are welcome.
>
> ---------------------------------------------------------
> Working Group Name: Multrans BOF
> Area Name: Transport Area
> Session Requester: Tina Tsou
>
> Number of Sessions: 1
> Length of Session(s):  2 hours
>
>
> Number of Attendees: 100
> Conflicts to Avoid:
>  First Priority: PIM, MBONED, RMT, V6OPS, SOFTWIRE
>  Second Priority: tsvarea intarea
>
> Special Requests:
>  N/A
>
> 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 use cases and prioritizing 
> list of issues, forming a new WG.
> The proposed agenda for the BoF session goes like this:
> . Welcome introduction and agenda bashing (chairs, 10 min)
> . Use cases (TBD, 30 min)
> . Prioritizing list of issues (TBD, 30 min)
> . Discussion (all, 30 min)
> . Conclusion and next steps (chairs, ADs, 20 min)
> Reading material:
> http://tools.ietf.org/html/draft-jaclee-behave-v4v6-mcast-ps-02
> http://tools.ietf.org/html/draft-tsou-multrans-use-cases-00
> ---------------------------------------------------------
>
>
>
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
>
>
>
> _______________________________________________
> multrans mailing list
> multrans@ietf.org
> https://www.ietf.org/mailman/listinfo/multrans