Re: [p2pi] [tsv-area] TANA proposed charter
"Das, Saumitra" <saumitra@qualcomm.com> Tue, 21 October 2008 21:32 UTC
Return-Path: <p2pi-bounces@ietf.org>
X-Original-To: p2pi-archive@ietf.org
Delivered-To: ietfarch-p2pi-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7442F3A6BB1; Tue, 21 Oct 2008 14:32:22 -0700 (PDT)
X-Original-To: p2pi@core3.amsl.com
Delivered-To: p2pi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C46293A6804; Tue, 21 Oct 2008 14:32:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.444
X-Spam-Level:
X-Spam-Status: No, score=-102.444 tagged_above=-999 required=5 tests=[AWL=-1.045, BAYES_00=-2.599, J_CHICKENPOX_41=0.6, J_CHICKENPOX_53=0.6, 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 pEuQE7hbSvrF; Tue, 21 Oct 2008 14:32:19 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 01F723A657C; Tue, 21 Oct 2008 14:32:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=saumitra@qualcomm.com; q=dns/txt; s=qcdkim; t=1224624814; x=1256160814; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Das,=20Saumitra"=20<saumitra@qualcomm.com>|To: =20"p2pi@ietf.org"=20<p2pi@ietf.org>|CC:=20"tana@ietf.org "=20<tana@ietf.org>,=20"tsv-area@ietf.org"=20<tsv-area@ie tf.org>|Date:=20Tue,=2021=20Oct=202008=2014:33:02=20-0700 |Subject:=20Re:=20[p2pi]=20[tsv-area]=20TANA=20proposed =20charter|Thread-Topic:=20[p2pi]=20[tsv-area]=20TANA=20p roposed=20charter|Thread-Index:=20AckzwOk1PC7juYL5Tt+kh3H ucqkfGwAAp4lA|Message-ID:=20<4A27D05E36DE7E47B96BCF7DD8F3 FD7101D352FD26@NASANEXMB04.na.qualcomm.com>|References: =20<mailman.3860.1224623104.4981.p2pi@ietf.org> |In-Reply-To:=20<mailman.3860.1224623104.4981.p2pi@ietf.o rg>|Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"us-as cii"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5411"=3B=20a=3D"11144656"; bh=0VBiy7y2rOjJKXx0DDiMXgRTrfbHLCnFlvxhBoRcnWM=; b=vK/5tep4yEsHqNTWmvu8aVRmxs11gQd60oR6e9mtUvVNJ3hcNitqxvgL ++55iBkR8y/oxeMeByrM9FoQQsavV7NLnPGG7QRt101UAYai3vAq1asmN Fib3geao5A+TN77wy2//bLq4gW7hjF+FX32+e9+I9JV5J3KwF476g2AkV o=;
X-IronPort-AV: E=McAfee;i="5300,2777,5411"; a="11144656"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Oct 2008 14:33:17 -0700
Received: from msgtransport05.qualcomm.com (msgtransport05.qualcomm.com [129.46.61.150]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m9LLXH9g018743 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 21 Oct 2008 14:33:17 -0700
Received: from nasanexhc01.na.qualcomm.com (nasanexhc01.na.qualcomm.com [172.30.37.21]) by msgtransport05.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m9LLVFf4020451 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 21 Oct 2008 14:33:16 -0700
Received: from NASANEXMB04.na.qualcomm.com ([129.46.52.85]) by nasanexhc01.na.qualcomm.com ([172.30.37.21]) with mapi; Tue, 21 Oct 2008 14:33:09 -0700
From: "Das, Saumitra" <saumitra@qualcomm.com>
To: "p2pi@ietf.org" <p2pi@ietf.org>
Date: Tue, 21 Oct 2008 14:33:02 -0700
Thread-Topic: [p2pi] [tsv-area] TANA proposed charter
Thread-Index: AckzwOk1PC7juYL5Tt+kh3HucqkfGwAAp4lA
Message-ID: <4A27D05E36DE7E47B96BCF7DD8F3FD7101D352FD26@NASANEXMB04.na.qualcomm.com>
References: <mailman.3860.1224623104.4981.p2pi@ietf.org>
In-Reply-To: <mailman.3860.1224623104.4981.p2pi@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "tana@ietf.org" <tana@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Subject: Re: [p2pi] [tsv-area] TANA proposed charter
X-BeenThere: p2pi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: P2P Infrastructure Discussion <p2pi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2pi>
List-Post: <mailto:p2pi@ietf.org>
List-Help: <mailto:p2pi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
Overall the problem is scoped well. Just a few clarifications about "(2) A document that clarifies the current practices of application design and reasons behind them and discusses the tradeoffs surrounding the use of many concurrent transport connections to one peer and/or to different peers." This seems a bit too broad. Multiple transport connections to a single peer/server is often used in applications like FDM and other download accelerators. Are we talking about how multiple TANA flows will share a bottleneck in this context or in general about how current TCP flows do this and best practices for that such as how many connections to open depending on network characteristics? When we talk about connections to different peers in multi-source downloads what exactly are the tradeoffs we are talking about: is it the impact on ISPs, or that the application could try to choose peers whose AS path or routing path is maximally disjoint. And again is this about how TANA flows would work connecting to multiple peers while sharing a common bottleneck at the client or really about multiple TCP flows to different peers and how to choose the peers such that you reduce common bottlenecks in the network. Maybe the multiple connections work item needs to be elaborated upon to give the correct context. Also, I think the name change is useful since there is not inkling that this really is about congestion control. Scavenger Network Congestion Protocols sounds good. Thanks Saumitra www.saumitra.info -----Original Message----- From: p2pi-bounces@ietf.org [mailto:p2pi-bounces@ietf.org] On Behalf Of p2pi-request@ietf.org Sent: Tuesday, October 21, 2008 2:05 PM To: p2pi@ietf.org Subject: p2pi Digest, Vol 7, Issue 27 Send p2pi mailing list submissions to p2pi@ietf.org To subscribe or unsubscribe via the World Wide Web, visit https://www.ietf.org/mailman/listinfo/p2pi or, via email, send a message with subject or body 'help' to p2pi-request@ietf.org You can reach the person managing the list at p2pi-owner@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of p2pi digest..." Today's Topics: 1. Re: [tsv-area] TANA proposed charter (Ted Faber) 2. Re: [tsv-area] TANA proposed charter (Ted Faber) 3. Re: [tsv-area] TANA proposed charter (Caitlin Bestler) 4. Re: [tana] [tsv-area] TANA proposed charter (Ted Faber) 5. Re: ASN utility (Marshall Eubanks) 6. Re: WG Review: Application-Layer Traffic Optimization (alto) (Nicholas Weaver) 7. Re: ASN utility (David Ward) 8. Re: WG Review: Application-Layer Traffic Optimization (alto) (Vijay K. Gurbani) ---------------------------------------------------------------------- Message: 1 Date: Tue, 21 Oct 2008 09:50:51 -0700 From: Ted Faber <faber@ISI.EDU> Subject: Re: [p2pi] [tsv-area] TANA proposed charter To: "Eddy, Wesley M. (GRC-RCN0)[VZ]" <Wesley.M.Eddy@nasa.gov> Cc: TSV Area <tsv-area@ietf.org>, tana@ietf.org, p2pi@ietf.org Message-ID: <20081021165051.GA64367@zod.isi.edu> Content-Type: text/plain; charset="us-ascii" On Tue, Oct 21, 2008 at 09:12:10AM -0500, Eddy, Wesley M. (GRC-RCN0)[VZ] wrote: > But if nobody else has a problem with the TANA name, I'll keep my mouth > shut so we don't waste time and energy. There are bigger fish to fry! It should change. I care about congestion control and nothing in the expansion of TANA indicated it was about congestion (to me). -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : <http://www.ietf.org/pipermail/p2pi/attachments/20081021/d0fa605b/attachment-0001.sig> ------------------------------ Message: 2 Date: Tue, 21 Oct 2008 13:23:27 -0700 From: Ted Faber <faber@ISI.EDU> Subject: Re: [p2pi] [tsv-area] TANA proposed charter To: Stanislav Shalunov <shalunov@shlang.com> Cc: TSV Area <tsv-area@ietf.org>, tana@ietf.org, p2pi@ietf.org, "Eddy, Wesley M. \(GRC-RCN0\)\[VZ\]" <Wesley.M.Eddy@nasa.gov> Message-ID: <20081021202327.GE64367@zod.isi.edu> Content-Type: text/plain; charset="us-ascii" On Tue, Oct 21, 2008 at 10:11:37AM -0700, Stanislav Shalunov wrote: > On Oct 21, 2008, at 9:50 AM, Ted Faber wrote: > >[The TANA name] should change. > > > Would it be sufficient to change the name on the documents and not in > the mailing list and the WG name? > > The WG name will go after we're done. The documents will remain. > This would also allow us to choose the names when the document bodies > are already written -- always a plus for relevance... If you want people who are interested in congestion control to take part in your group, "Techniques for Advanced Networking Applications" will do nothing to attract their attention. It is completely generic phrase. It could refer to UTF encoding strategies or peer-to-peer load balancing. It may not be important to you to attract congestion control expertise. If it is, I recommend changing the name to something that will get busy congestion control people to read past the name. YMMV. -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : <http://www.ietf.org/pipermail/p2pi/attachments/20081021/38f38679/attachment-0001.sig> ------------------------------ Message: 3 Date: Tue, 21 Oct 2008 09:23:01 -0700 From: Caitlin Bestler <cait@asomi.com> Subject: Re: [p2pi] [tsv-area] TANA proposed charter To: Murari Sridharan <muraris@microsoft.com> Cc: TSV Area <tsv-area@ietf.org>, "tana@ietf.org" <tana@ietf.org>, "p2pi@ietf.org" <p2pi@ietf.org>, "ext Eddy, Wesley M. \(GRC-RCN0\)\[VZ\]" <Wesley.M.Eddy@nasa.gov> Message-ID: <48FE01E5.5000302@asomi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Murari Sridharan wrote: > Isn't the goal here to achieve lower than best-effort, so essentially "Low Priority TCP", > assuming non-TCP traffic flows E2E we can make it more general and call it "Congestion control > for low priority flows" > > Murari > A successful algorithm here would not necessarily "lower than" best-effort, because the "low priority' flow could actually achieve higher throughput than a conventional TCP flow. I believe that the key phrase in the proposed charter is very much on target -- that the "TANA flows" rapidly yield to conventional TCP. It is possible to both rapidly yield *and* to rapidly claim bandwidth that conventional TCP algorithms would have left unused. The extent to which a given algorithm can rapidly claim bandwidth without imperiling existing TCP traffic is of course something that the WG would have to review. But given the charter objective of "saturation" it is important to understand that this is not necessarily "low priority" traffic. It is undoubtedly very jitter-tolerant traffic that can be quite elastic in its bandwidth utilization for any short period of time. ----- Caitlin Bestler cait@asomi.com - http://www.asomi.com/CaitlinBestlerResume.pdf ------------------------------ Message: 4 Date: Tue, 21 Oct 2008 13:31:40 -0700 From: Ted Faber <faber@ISI.EDU> Subject: Re: [p2pi] [tana] [tsv-area] TANA proposed charter To: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Cc: p2pi@ietf.org, tana@ietf.org, TSV Area <tsv-area@ietf.org>, "Eddy, Wesley M. \(GRC-RCN0\)\[VZ\]" <Wesley.M.Eddy@nasa.gov> Message-ID: <20081021203140.GH64367@zod.isi.edu> Content-Type: text/plain; charset="us-ascii" On Tue, Oct 21, 2008 at 01:26:46PM -0700, Nicholas Weaver wrote: > Why not: > > Scavenger Network Congestion Protocols? My ears would prick up for that. -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : <http://www.ietf.org/pipermail/p2pi/attachments/20081021/9d0b1224/attachment-0001.sig> ------------------------------ Message: 5 Date: Tue, 21 Oct 2008 16:38:30 -0400 From: Marshall Eubanks <tme@multicasttech.com> Subject: Re: [p2pi] ASN utility To: Lisa Dusseault <ldusseault@commerce.net> Cc: p2pi@ietf.org Message-ID: <62F04BA8-07BD-4DA4-BB13-09E3498ACA87@multicasttech.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes On Sep 29, 2008, at 1:54 PM, Lisa Dusseault wrote: > > > When the IESG looked at the proposed ALTO charter last week, Dave > had some comments about ASNs which I'd like to follow up on by > dragging Dave into the conversation. > > What I understand the ASN related suggestions so far to be, is to > have the ALTO server return a list of ASN numbers to prefer or > avoid. This sort of information could only be provided by an ISP- > operated ALTO server. Are you sure about that ? A peer can (for example) query route views, or I (or a host of others) can send it BGP / address block tables. It would not be hard to collate address information with ASN and ASN paths and draw conclusions. I don't see why an ISP is necessarily involved. Regards Marshall > A peer, armed with this information, can do whatever they do today > to figure > out which IP address falls in which ASN. The P4P and Yale folks > claim that returning a preference of ASNs helped their application > tremendously. > > Dave, was your concern about discovering ASN being unnecessary, or > about ranking of ASNs being unhelpful? Can you restate? > > Thanks, > Lisa > _______________________________________________ > p2pi mailing list > p2pi@ietf.org > https://www.ietf.org/mailman/listinfo/p2pi ------------------------------ Message: 6 Date: Tue, 21 Oct 2008 13:43:30 -0700 From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Subject: Re: [p2pi] WG Review: Application-Layer Traffic Optimization (alto) To: Karl Auerbach <karl@cavebear.com> Cc: "p2pi@ietf.org" <p2pi@ietf.org>, Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>, IESG IESG <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org> Message-ID: <EE0DFEE3-0646-45F7-B194-199B83B2E9D4@icsi.berkeley.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Hey, stupid thought... Could you do proximity based on "who's your DNS resolver"? Do a few name lookups: one to register YOU as using YOUR DNS resolver to the remote coordinator, and one to get "who are other peers using the same resolver"? An ugly, UGLY hack, but it might be interesting to think about. Has anyone done this already? ------------------------------ Message: 7 Date: Tue, 21 Oct 2008 15:50:40 -0500 From: David Ward <dward@cisco.com> Subject: Re: [p2pi] ASN utility To: Marshall Eubanks <tme@multicasttech.com> Cc: p2pi@ietf.org, Lisa Dusseault <ldusseault@commerce.net> Message-ID: <10062CD4-88B8-47EC-8809-D02486A3D05D@cisco.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Marshall - I mentioned that this is one deployment model and is as it works today but, the charter is unclear if they want to support any other model. I do think it is considerably harder to deduce a current AS_path from simple prefix -> ASN information. -DWard On Oct 21, 2008, at 3:38 PM, Marshall Eubanks wrote: > > On Sep 29, 2008, at 1:54 PM, Lisa Dusseault wrote: > >> >> >> When the IESG looked at the proposed ALTO charter last week, Dave >> had some comments about ASNs which I'd like to follow up on by >> dragging Dave into the conversation. >> >> What I understand the ASN related suggestions so far to be, is to >> have the ALTO server return a list of ASN numbers to prefer or >> avoid. This sort of information could only be provided by an ISP- >> operated ALTO server. > > Are you sure about that ? > > A peer can (for example) query route views, or I (or a host of > others) can send it BGP / address block tables. It would not be > hard to collate address information with ASN and ASN paths and draw > conclusions. I don't see why an ISP is necessarily involved. > > Regards > Marshall > > > >> A peer, armed with this information, can do whatever they do today >> to figure >> out which IP address falls in which ASN. The P4P and Yale folks >> claim that returning a preference of ASNs helped their application >> tremendously. >> >> Dave, was your concern about discovering ASN being unnecessary, or >> about ranking of ASNs being unhelpful? Can you restate? >> >> Thanks, >> Lisa >> _______________________________________________ >> p2pi mailing list >> p2pi@ietf.org >> https://www.ietf.org/mailman/listinfo/p2pi > ------------------------------ Message: 8 Date: Tue, 21 Oct 2008 16:05:40 -0500 From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com> Subject: Re: [p2pi] WG Review: Application-Layer Traffic Optimization (alto) To: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Cc: "p2pi@ietf.org" <p2pi@ietf.org> Message-ID: <48FE4424.2000309@alcatel-lucent.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Nicholas Weaver wrote: > Hey, stupid thought... > > Could you do proximity based on "who's your DNS resolver"? Do a few > name lookups: one to register YOU as using YOUR DNS resolver to the > remote coordinator, and one to get "who are other peers using the same > resolver"? > > An ugly, UGLY hack, but it might be interesting to think about. > > Has anyone done this already? Doesn't Ono [1] do that? Or am I missing something? CDNs also use DNS redirects to redirect clients to nearest servers. [1] David R. Choffnes and Fabi?n E. Bustamante. Taming the Torrent: A practical approach to reducing cross-ISP traffic in P2P systems, Proc. of ACM SIGCOMM 2008, August 2008. Thanks, - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA) Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org} WWW: http://www.alcatel-lucent.com/bell-labs ------------------------------ _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi End of p2pi Digest, Vol 7, Issue 27 *********************************** _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Reinaldo Penno
- Re: [p2pi] [tsv-area] TANA proposed charter Nicholas Weaver
- Re: [p2pi] [tsv-area] TANA proposed charter Stanislav Shalunov
- [p2pi] TANA proposed charter Stanislav Shalunov
- Re: [p2pi] [tsv-area] TANA proposed charter Lars Eggert
- Re: [p2pi] [tsv-area] TANA proposed charter Bruce Davie
- Re: [p2pi] [tsv-area] TANA proposed charter Joe Touch
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Marshall Eubanks
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Joe Touch
- Re: [p2pi] [tsv-area] TANA proposed charter Stanislav Shalunov
- Re: [p2pi] [tsv-area] TANA proposed charter Salman Abdul Baset
- Re: [p2pi] [tsv-area] TANA proposed charter Stanislav Shalunov
- Re: [p2pi] [tsv-area] TANA proposed charter Nicholas Weaver
- Re: [p2pi] [tsv-area] TANA proposed charter Stanislav Shalunov
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Narayanan, Vidya
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Nicholas Weaver
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Lars Eggert
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Narayanan, Vidya
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Narayanan, Vidya
- Re: [p2pi] TANA proposed charter Reinaldo Penno
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Narayanan, Vidya
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Narayanan, Vidya
- Re: [p2pi] TANA proposed charter Marshall Eubanks
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Nicholas Weaver
- Re: [p2pi] [tsv-area] TANA proposed charter Eddy, Wesley M. (GRC-RCN0)[VZ]
- Re: [p2pi] [tsv-area] TANA proposed charter Murari Sridharan
- Re: [p2pi] [tsv-area] TANA proposed charter Ted Faber
- Re: [p2pi] [tsv-area] TANA proposed charter Ted Faber
- Re: [p2pi] [tsv-area] TANA proposed charter Caitlin Bestler
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Ted Faber
- Re: [p2pi] [tsv-area] TANA proposed charter Das, Saumitra
- Re: [p2pi] [tsv-area] [tana] TANA proposed charter Das, Saumitra
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Stanislav Shalunov
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Rolf Winter
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Laird Popkin
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Salvatore Loreto
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Reinaldo Penno
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Rolf Winter
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Reinaldo Penno
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Rolf Winter
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Kurt Tutschku
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter toby.moncaster
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Nicholas Weaver
- Re: [p2pi] [tsv-area] TANA proposed charter Ingemar Johansson S
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Michael Menth
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Michael Welzl
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Roland Bless
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Roland Bless
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Nicholas Weaver
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Marshall Eubanks
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Marshall Eubanks
- Re: [p2pi] [tana] TANA proposed charter Stanislav Shalunov
- Re: [p2pi] [tana] TANA proposed charter Laird Popkin
- Re: [p2pi] [tana] TANA proposed charter Enrico Marocco
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Rolf Winter
- Re: [p2pi] [tana] TANA proposed charter toby.moncaster
- Re: [p2pi] [tsv-area] TANA proposed charter toby.moncaster
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter toby.moncaster
- Re: [p2pi] [tsv-area] TANA proposed charter Mark Allman
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Bryan Ford
- Re: [p2pi] [tana] TANA proposed charter Gorry Fairhurst
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Narayanan, Vidya
- [p2pi] TANA proposed charter -- packet marking qu… John Leslie
- Re: [p2pi] TANA proposed charter -- packet markin… Nicholas Weaver
- Re: [p2pi] TANA proposed charter -- packet markin… John Leslie
- Re: [p2pi] TANA proposed charter -- packet markin… Nicholas Weaver
- Re: [p2pi] TANA proposed charter Livingood, Jason
- Re: [p2pi] TANA proposed charter -- packet markin… Laird Popkin
- Re: [p2pi] [tana] TANA proposed charter -- packet… Woundy, Richard
- Re: [p2pi] TANA proposed charter -- packet markin… Stanislav Shalunov
- Re: [p2pi] TANA proposed charter -- packet markin… Robb Topolski
- Re: [p2pi] TANA proposed charter -- packet markin… Nicholas Weaver
- Re: [p2pi] TANA proposed charter -- packet markin… Bruce Davie
- Re: [p2pi] [tana] [tsv-area] TANA proposed charter Robb Topolski