Re: [MBONED] Draft agenda for multicast transition interim
Ronald Bonica <rbonica@juniper.net> Mon, 26 December 2011 22:16 UTC
Return-Path: <rbonica@juniper.net>
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 18B4021F8C5A for <mboned@ietfa.amsl.com>; Mon, 26 Dec 2011 14:16:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.419
X-Spam-Level:
X-Spam-Status: No, score=-106.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 p7og0aDr-vfo for <mboned@ietfa.amsl.com>; Mon, 26 Dec 2011 14:16:43 -0800 (PST)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 1555421F8C58 for <mboned@ietf.org>; Mon, 26 Dec 2011 14:16:43 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKTvjyPbv/MxPD2nBhfjx4gOI665zYOyWp@postini.com; Mon, 26 Dec 2011 14:16:43 PST
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 26 Dec 2011 14:16:27 -0800
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 26 Dec 2011 14:16:27 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Mon, 26 Dec 2011 17:16:26 -0500
From: Ronald Bonica <rbonica@juniper.net>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, MBONED WG <mboned@ietf.org>
Date: Mon, 26 Dec 2011 17:16:24 -0500
Thread-Topic: Draft agenda for multicast transition interim
Thread-Index: AQHMs6Ffjh6RlJwL9UOCkcshob2Wj5XN/LJggAEdUwCABnzlEIAZOMPg
Message-ID: <13205C286662DE4387D9AF3AC30EF456D74E91E1ED@EMBX01-WF.jnpr.net>
References: <C0E0A32284495243BDE0AC8A066631A80C216ECF@szxeml526-mbx.china.huawei.com> <13205C286662DE4387D9AF3AC30EF456D74DE5BC2F@EMBX01-WF.jnpr.net> <C0E0A32284495243BDE0AC8A066631A80C22062B@szxeml526-mbx.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80C22062B@szxeml526-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [MBONED] Draft agenda for multicast transition interim
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: Mon, 26 Dec 2011 22:16:44 -0000
Tina, Would it be possible to condense everything that needs to be discussed in the Overview into the draft that you are working on with Marshall and Stig? Ron > -----Original Message----- > From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com] > Sent: Saturday, December 10, 2011 4:13 PM > To: Ronald Bonica; multrans@ietf.org; MBONED WG > Subject: RE: Draft agenda for multicast transition interim > > Hi Ron, > Input Drafts for the first agenda item "Overview" are below. > 1. > http://datatracker.ietf.org/doc/draft-tsou-multicast-transition- > taxonomy/ > A Classification and Evaluation of Approaches to Transitional Multicast > 2. > http://datatracker.ietf.org/doc/draft-tsou-behave-translated-multicast/ > A Generic Approach to Multicast Translation In Support of IPv6 > Transition > > Tina > > -----Original Message----- > From: Ronald Bonica [mailto:rbonica@juniper.net] > Sent: Tuesday, December 06, 2011 10:44 AM > To: Tina TSOU; multrans@ietf.org; MBONED WG > Subject: RE: Draft agenda for multicast transition interim > > Hi Tina, > > Thanks for the proposed agenda. A few comments are inline. > > Ron > > > -----Original Message----- > > From: multrans-bounces@ietf.org [mailto:multrans-bounces@ietf.org] On > > Behalf Of Tina TSOU > > Sent: Monday, December 05, 2011 8:04 PM > > To: multrans@ietf.org; MBONED WG > > Subject: [multrans] Draft agenda for multicast transition interim > > > > Dear all, > > It is proposed to hold the multicast transition interim meeting as a > > series of short meetings. Timing of individual meetings may be set to > > spread inconvenient hours around the globe. The objective of these > > meetings is to achieve technical progress in the indicated topics. > Here > > is the proposed agenda: > > > > 1. Use Cases (1 hour) > > > > Ensure we are all clear on what use cases will be in scope. > > We might want to call the first agenda item "Overview" instead of "Use > Cases". IMHO, the Overview contains the following parts: > > - an introduction to the problem space > - an introduction to the solution space > > The crux of the problem is that multicast connectivity is required > among the following host types: > > - dual-stack > - IPv4-only > - IPv6-only > > Therefore, multicast data and signaling will need to traverse IPv4/IPv6 > boundaries. The IPv4/IPv6 boundary may be adjacent to the source, at > any point between the source and destination, or adjacent to the > destination. For some network topologies (e.g., IPv4 edge, IPv6 core), > multiple IPv4/IPv6 boundary crossings may be required. For the purpose > of this exercise, all network segments are assumed to be multicast > enabled. > > (You can talk about use cases here, but you probably don't want to > enumerate every possible use-case. Talk about a use case only if it > introduces new requirements for the adaptation function that will be > deployed at the IPv4/IPv6 boundary). > > The solution space contains: > > - a source discovery solution > - a multicast address mapping solution > - an adaptation function solution > > More on each of those, below. It would be great if we had a short > draft to review before the first Interim meeting. > > > > > > 2. Multicast address discovery by the receiver (2 hours) > > > > How does the receiver learn the multicast addresses corresponding to > > specific programs, in the IP version that the receiver understands? > > We might want to call this Multicast Source Discovery. The following > are a few interesting questions: > > - How are multicast sources identified? > - How dynamic is the Source Discovery Mechanism? Does it simple > discover and announce every multicast stream in the network or is > registration required? > - How do we ensure that the scope of the Source discovery mechanism is > the same as the scope of the multicast network? > - Can the Source Discovery mechanism be crafted from existing > protocols? > > Again, it would be great if we had a draft to work from. > > > > > > > 3. Multicast address translation (2 hours) > > > > Stateless translation between IPv4 and IPv6 addresses should get > > priority in this discussion, but we may go on to the broader topic if > > there appears to be a need. > > What broader topic? Stateful translation? Why go there? > > > > > > > 4. What and how an adaptation function between the receiver and the > > network works (2 hours) > > > > In cases where the receiver and the multicast-enabled network to > which > > it is attached support different IP versions, an adaptation function > > (AF) is required between them. What are the requirements on that AF > for > > the handling of multicast signalling and the handling of multicast > > content? > > > > 5. What and how an adaptation function between two networks works (2 > > hours) > > > > In cases where two adjacent multicast-enabled networks support > > different > > IP versions, another type of adaptation function is needed. What are > > the > > requirements on that AF for the handling of multicast signalling and > > the > > handling of multicast content? > > > > Comments on this draft agenda are invited. > > > > Tina > > _______________________________________________ > > multrans mailing list > > multrans@ietf.org > > https://www.ietf.org/mailman/listinfo/multrans
- Re: [MBONED] Draft agenda for multicast transitio… Ronald Bonica
- Re: [MBONED] Draft agenda for multicast transitio… Ronald Bonica
- Re: [MBONED] [multrans] Draft agenda for multicas… Ronald Bonica
- Re: [MBONED] Draft agenda for multicast transitio… Tina TSOU
- Re: [MBONED] [multrans] Draft agenda for multicas… Tom Taylor
- Re: [MBONED] Draft agenda for multicast transitio… Ronald Bonica
- Re: [MBONED] Draft agenda for multicast transitio… Ronald Bonica
- Re: [MBONED] Draft agenda for multicast transitio… Tina TSOU