Re: [p2pi] discussing P2PI-related standardization in Dublin
"Livingood, Jason" <Jason_Livingood@cable.comcast.com> Mon, 09 June 2008 21:01 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 233993A696A; Mon, 9 Jun 2008 14:01:43 -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 EA29D3A697B; Mon, 9 Jun 2008 14:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.282
X-Spam-Level:
X-Spam-Status: No, score=0.282 tagged_above=-999 required=5 tests=[AWL=0.746, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 6ddiflQXGoyr; Mon, 9 Jun 2008 14:01:41 -0700 (PDT)
Received: from paoakoavas09.cable.comcast.com (paoakoavas09.cable.comcast.com [208.17.35.58]) by core3.amsl.com (Postfix) with ESMTP id 9E7A33A689A; Mon, 9 Jun 2008 14:01:40 -0700 (PDT)
Received: from ([10.52.116.30]) by paoakoavas09.cable.comcast.com with ESMTP id KP-NTF18.56283810; Mon, 09 Jun 2008 17:01:41 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Jun 2008 17:01:41 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 09 Jun 2008 17:01:41 -0400
Message-ID: <45AEC6EF95942140888406588E1A6602050F8A1D@PACDCEXCMB04.cable.comcast.com>
In-Reply-To: <22F6A875-B548-4C65-AB68-B88E526CCA33@nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [p2pi] discussing P2PI-related standardization in Dublin
Thread-Index: AcjH3ZarWE/N3E6+S32PcBHCWewT6QClYsMw
References: <22F6A875-B548-4C65-AB68-B88E526CCA33@nokia.com>
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: TSV Area <tsv-area@ietf.org>
X-OriginalArrivalTime: 09 Jun 2008 21:01:41.0790 (UTC) FILETIME=[045733E0:01C8CA74]
Cc: p2prg@irtf.org, iab@iab.org, p2pi@ietf.org, "IESG ((E-mail))" <iesg@ietf.org>, P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [p2pi] discussing P2PI-related standardization in Dublin
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
Exceptionally minor comments inline. > We'd be interested to hear from the community if we should > schedule a BOF in Dublin to discuss whether the IETF should > take on some or all of these, and if so, whether TSV would be > the right place for this work. A BoF or two would be good, IMHO. Some of this probably fits into TSV too, so confiming that this seems on the right track to me at least. > The working title for the BOF is "Techniques for Advanced > Networking Applications" or TANA. So far we have TANA and ALTO, plus referring some items into TSV, which again, seems appropriate and useful. I do not have anything else to add to this list for now; perhaps discussion @ IETF-72 will reveal further needs. Jason _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- [p2pi] discussing P2PI-related standardization in… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Vijay K. Gurbani
- Re: [p2pi] discussing P2PI-related standardizatio… Peterson, Jon
- Re: [p2pi] discussing P2PI-related standardizatio… Livingood, Jason
- [p2pi] Refining the ALTO problem statement [Was: … Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi
- Re: [p2pi] Refining the ALTO problem statement [W… John Leslie
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] discussing P2PI-related standardizatio… Richard Bennett
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement [W… Henning Schulzrinne
- Re: [p2pi] Refining the ALTO problem statement [W… Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement Robert Snively
- Re: [p2pi] Refining the ALTO problem statement Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement stefano previdi
- Re: [p2pi] Refining the ALTO problem statement Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert