Re: [multrans] Draft Multrans 2nd BoF request

"Dan Wing" <dwing@cisco.com> Thu, 25 August 2011 16:11 UTC

Return-Path: <dwing@cisco.com>
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 C9D7921F855F for <multrans@ietfa.amsl.com>; Thu, 25 Aug 2011 09:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.098
X-Spam-Level:
X-Spam-Status: No, score=-103.098 tagged_above=-999 required=5 tests=[AWL=-1.099, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 ZpeH3X9V-3Qw for <multrans@ietfa.amsl.com>; Thu, 25 Aug 2011 09:11:53 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3D421F84E4 for <multrans@ietf.org>; Thu, 25 Aug 2011 09:11:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2787; q=dns/txt; s=iport; t=1314288787; x=1315498387; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=McIpP9AWfFx7RLR6ooA9aqVIHlCUUjy9vt+9ouXuvUs=; b=j0KVTLBaaFt+pYWBiX7iVye3RPznjEmfP50oDSOVY0m3k8gtlWrarRdi ln3blCd1qE1Mbr6/nn3iJzfZgbjixbhLiYkpgflexM6Bp+WAoUJotHJtm qxk6pC3oV7JqGy8n5afYUZ2ACdbte8JBT1jIjSpcMYwX3GlQopcIRe9YV c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ar8AALVzVk6rRDoI/2dsb2JhbABCmCqBbI1sd4FAAQEBAQIBAQEBBQoBFxA0EAcBAwIJDwIEAQEOGgcZDhUKCQgBAQQBEgsXh1AEnAABnw+GTASHYZxT
X-IronPort-AV: E=Sophos;i="4.68,281,1312156800"; d="scan'208";a="16473652"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-6.cisco.com with ESMTP; 25 Aug 2011 16:13:06 +0000
Received: from dwingWS (sjc-vpn6-1523.cisco.com [10.21.125.243]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7PGD5ow031574; Thu, 25 Aug 2011 16:13:06 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Tina TSOU' <Tina.Tsou.Zouting@huawei.com>, multrans@ietf.org
References: <C0E0A32284495243BDE0AC8A066631A88A7A9A@szxeml526-mbs.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A88A7A9A@szxeml526-mbs.china.huawei.com>
Date: Thu, 25 Aug 2011 09:13:05 -0700
Message-ID: <016401cc6341$df854920$9e8fdb60$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acxi1KTRF0FMQ8rrQGS+7rlSCBaqgAAbRTAQ
Content-Language: en-us
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: Thu, 25 Aug 2011 16:11:53 -0000

> -----Original Message-----
> From: multrans-bounces@ietf.org [mailto:multrans-bounces@ietf.org] On
> Behalf Of Tina TSOU
> Sent: Wednesday, August 24, 2011 8:11 PM
> To: multrans@ietf.org
> Subject: [multrans] Draft Multrans 2nd BoF request
> 
> 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

Please include BEHAVE in the conflict list.

-d

>   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