RE: [P2PSIP] Fw: I-D Action:draft-bryan-p2psip-app-scenarios-00.txt

JiangXingFeng <jiang.x.f@huawei.com> Mon, 26 November 2007 09:01 UTC

Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwZqV-0002lB-VE; Mon, 26 Nov 2007 04:01:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwZqU-0002ky-SY for p2psip@ietf.org; Mon, 26 Nov 2007 04:01:38 -0500
Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwZqL-0007ss-6s for p2psip@ietf.org; Mon, 26 Nov 2007 04:01:38 -0500
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JS3001SLVIY83@szxga01-in.huawei.com> for p2psip@ietf.org; Mon, 26 Nov 2007 16:56:58 +0800 (CST)
Received: from huawei.com ([172.24.1.18]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JS300LE9VIXF7@szxga01-in.huawei.com> for p2psip@ietf.org; Mon, 26 Nov 2007 16:56:58 +0800 (CST)
Received: from j36340 ([10.164.5.105]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0JS300HBFVIW0J@szxml03-in.huawei.com> for p2psip@ietf.org; Mon, 26 Nov 2007 16:56:57 +0800 (CST)
Date: Mon, 26 Nov 2007 16:56:56 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
Subject: RE: [P2PSIP] Fw: I-D Action:draft-bryan-p2psip-app-scenarios-00.txt
In-reply-to: <02a601c820e2$e2b416d0$6501a8c0@china.huawei.com>
To: 'Spencer Dawkins' <spencer@mcsr-labs.org>, 'P2PSIP Mailing List' <p2psip@ietf.org>
Message-id: <002d01c8300a$4c6edfc0$6905a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: Acgg4w25/suZ0J3iRqCa5+hxmwj3+gPJeAHw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc:
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, Spencer:

Thanks for the analysis work of application scenarios from you guys.

Application scenarios vary tremendously in its attributes you have
classified. Do you want our resulting protocol support all or most of the
application scenarios? 

IMHO, the more valuable work is to find the commonalities among them and try
to get some conclusions like that: whether all or most of peers are behind
NAT; whether centralized server could be available in every application
scenarios, what is the suitable churn rate for the various applications,
etc. 

If we could reach consensus on these issues, we could make it as a input to
the design of the peer and/or client protocol.

Regards!
--
Jiang XingFeng

> -----Original Message-----
> From: Spencer Dawkins [mailto:spencer@mcsr-labs.org]
> Sent: Wednesday, November 07, 2007 10:07 AM
> To: P2PSIP Mailing List
> Subject: [P2PSIP] Fw: I-D Action:draft-bryan-p2psip-app-scenarios-00.txt
> 
> Just as a heads-up - we've redone the Use Case draft (as "application
> scenarios") and submitted the document - should be available now.
> 
> Please feel free to express opinions (and outrage - flaming torches and
> pitchforks will work better in cyberspace than in damp Vancouver :-)
> 
> Thanks,
> 
> Spencer
> 
> 
> >A New Internet-Draft is available from the on-line Internet-Drafts
> >directories.
> >
> > Title           : Application Scenarios for Peer-to-Peer Session
> > Initiation Protocol (P2PSIP)
> > Author(s)       : D. Bryan, et al.
> > Filename        : draft-bryan-p2psip-app-scenarios-00.txt
> > Pages           : 19
> > Date            : 2007-11-06
> >
> > This document attempts to identify and classify application scenarios
> > of P2P based SIP.  It does not attempt to exhaustively enumerate
> > these scenarios, and is focused exclusively on scenarios related to
> > real-time IP communication.
> >
> > A URL for this Internet-Draft is:
> >
http://www.ietf.org/internet-drafts/draft-bryan-p2psip-app-scenarios-00.txt
> >
> > To remove yourself from the I-D Announcement list, send a message to
> > i-d-announce-request@ietf.org with the word unsubscribe in the body of
> > the message.
> > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> > to change your subscription settings.
> >
> > Internet-Drafts are also available by anonymous FTP. Login with the
> > username "anonymous" and a password of your e-mail address. After
> > logging in, type "cd internet-drafts" and then
> > "get draft-bryan-p2psip-app-scenarios-00.txt".
> >
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> > Internet-Drafts can also be obtained by e-mail.
> >
> > Send a message to:
> > mailserv@ietf.org.
> > In the body type:
> > "FILE /internet-drafts/draft-bryan-p2psip-app-scenarios-00.txt".
> >
> > NOTE:   The mail server at ietf.org can return the document in
> > MIME-encoded form by using the "mpack" utility.  To use this
> > feature, insert the command "ENCODING mime" before the "FILE"
> > command.  To decode the response(s), you will need "munpack" or
> > a MIME-compliant mail reader.  Different MIME-compliant mail readers
> > exhibit different behavior, especially when dealing with
> > "multipart" MIME messages (i.e. documents which have been split
> > up into multiple messages), so check your local documentation on
> > how to manipulate these messages.
> >
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >
> 
> 
>
----------------------------------------------------------------------------
----
> 
> 
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www1.ietf.org/mailman/listinfo/i-d-announce
> >
> 
> 
> 
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip


_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www1.ietf.org/mailman/listinfo/p2psip