Re: [tana] Why not SSM?
Marshall Eubanks <tme@multicasttech.com> Sat, 16 August 2008 00:45 UTC
Return-Path: <tana-bounces@ietf.org>
X-Original-To: tana-archive@ietf.org
Delivered-To: ietfarch-tana-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 264623A6A3F; Fri, 15 Aug 2008 17:45:31 -0700 (PDT)
X-Original-To: tana@core3.amsl.com
Delivered-To: tana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 680613A6A56 for <tana@core3.amsl.com>; Fri, 15 Aug 2008 17:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.697
X-Spam-Level:
X-Spam-Status: No, score=-102.697 tagged_above=-999 required=5 tests=[AWL=-0.902, BAYES_05=-1.11, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5YROVjcYvuv9 for <tana@core3.amsl.com>; Fri, 15 Aug 2008 17:45:27 -0700 (PDT)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 8DCE83A6A4F for <tana@ietf.org>; Fri, 15 Aug 2008 17:45:27 -0700 (PDT)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 12513405; Fri, 15 Aug 2008 20:45:28 -0400
Message-Id: <0CE84681-0679-410B-AB1F-C5C88306693B@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: The 8472 <the8472@infinite-source.de>
In-Reply-To: <48A61C24.1080407@infinite-source.de>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Fri, 15 Aug 2008 20:45:28 -0400
References: <48A61C24.1080407@infinite-source.de>
X-Mailer: Apple Mail (2.926)
Cc: tana@ietf.org
Subject: Re: [tana] Why not SSM?
X-BeenThere: tana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Techniques for Advanced Networking Applications \(TANA\)" <tana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tana>, <mailto:tana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tana>
List-Post: <mailto:tana@ietf.org>
List-Help: <mailto:tana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tana>, <mailto:tana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tana-bounces@ietf.org
Errors-To: tana-bounces@ietf.org
On Aug 15, 2008, at 8:15 PM, The 8472 wrote: > I can't browse the archive right now, so sry if this has been > discussed before. I have suggested the following repeatedly in > various places and it always ended w/o any insight due to the lack > of knowledge regarding the core internet infrastructure. > > Everything i have seen so far amounts to alchemy... > We're trying to preserve P2P-performance for the enduser while > easing the load on ISP infrastructure and maintaining fairness. The > problem is that P2P applications are a zero-sum-game. Things that > are downloaded must be uploaded somewhere else. > > All the voodo protocols can either shuffle the bandwidth around to > other ISPs or lower the overall performance of the P2P applications. > Considering that Comcast basically is highly allergic to any kind of > sustained upload due to... humhum... shortcomings in the cable > network infrastructure this would mean any effective solution would > more or less shift significant proportions of their upload to other > ISPs. Other ISPs in turn may not like transit rather than upload on > the last mile. Now... combine these two and you have conflicting > interests, which in turn might result in conflicting policies > between various ISPs. > > Anyway, i'm digressing. As i said all we can do with the current > approaches is shuffle around bandwidth. The real solution would be > breaking up the zero-sum-game. And multicast does exactly that. > Source-Specific Multicast (RFCs 3569, 4607) is ideally suited for ad- > hoc allocation of groups as nodes always join a (source, group) > tuple, i.e. there wouldn't be any collisions. > > Now let's imagine an ideal world. Globally scoped SSM works and is > available to every enduser (as source and as sink). 10 people with > 2Mbit upload each could serve an aggregate bandwidth of 20Mbit to an > unlimited amount (until we run out of v6 addresses) of group > subscribers. This would reduce the bandwidth consumed on the last > mile to downloads and almost no uploads, and transit bandwidth would > be 20Mbit tops (assuming non-redundant / sparse trees) - even less > assuming the 10 uploaders are spread throughout various ISPs. > There is a protocol called AMT intended to deal with this issue. See draft-ietf-mboned-auto-multicast-09.txt > Ok, back to the real world which is far from ideal. I know that many > home routers don't support IGMPv3, let alone IPv6/MLD. I also figure > that millions of mcast group subscriptions done at high churn rates > spread throughout the internet and at least ten-thousands of group/ > source tuples would put a significant strain on the routing tables. It isn't SSM, but if this is a problem, IPv6 embedded RP might be worth looking into. > > If anyone is aware of further problems (and i guess there are > plenty), please enlighten us. > If you want to do a proposal, we will listen in MBONED. Regards Marshall > > But even if there are lots of obstacles, the idealized scenario > should show that it's worthwhile as it would tackle the problem at > its root instead of mitigating the symptoms. So, my question is if/ > how/when can we deploy SSM? Or why can't we? > > And even if we could there'd still be various open issues for > protocols running ontop of SSM, e.g. that SSM is unidirectional and > we'd need some congestion control feedback over multiple unicast > links to allow the sender to adjust his send rates, we also might > have to work with SSM scoped to the ISP/AS level and interconnect > various SSM-islands via unicast. We'd need strategies to minimize > the number of active groups while still providing enough choice for > downloaders to pick various streams to saturate their download link > etc. etc. > > -- > The 8472 > independent developer for the Azureus Vuze Bittorrent client > _______________________________________________ > tana mailing list > tana@ietf.org > https://www.ietf.org/mailman/listinfo/tana _______________________________________________ tana mailing list tana@ietf.org https://www.ietf.org/mailman/listinfo/tana
- [tana] Why not SSM? The 8472
- Re: [tana] Why not SSM? Marshall Eubanks
- Re: [tana] Why not SSM? The 8472
- Re: [tana] Why not SSM? Marshall Eubanks
- Re: [tana] Why not SSM? Stanislav Shalunov