[P2PSIP] FW: New Version Notification for draft-jiang-p2psip-relay-03
Ning Zong <zongning@huawei.com> Mon, 05 October 2009 04:19 UTC
Return-Path: <zongning@huawei.com>
X-Original-To: p2psip@core3.amsl.com
Delivered-To: p2psip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 07A613A681D for <p2psip@core3.amsl.com>; Sun, 4 Oct 2009 21:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.069
X-Spam-Level:
X-Spam-Status: No, score=-96.069 tagged_above=-999 required=5 tests=[AWL=0.626, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_14=0.6, J_CHICKENPOX_44=0.6, RDNS_NONE=0.1, 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 evkIjWEuZ7kn for <p2psip@core3.amsl.com>; Sun, 4 Oct 2009 21:19:08 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id C15D43A6817 for <p2psip@ietf.org>; Sun, 4 Oct 2009 21:19:07 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KR000IIKXE78M@szxga03-in.huawei.com> for p2psip@ietf.org; Mon, 05 Oct 2009 12:20:31 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KR0004JGXE7C8@szxga03-in.huawei.com> for p2psip@ietf.org; Mon, 05 Oct 2009 12:20:31 +0800 (CST)
Received: from z63316 ([10.164.12.81]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KR000EORXE6G7@szxml06-in.huawei.com> for p2psip@ietf.org; Mon, 05 Oct 2009 12:20:31 +0800 (CST)
Date: Mon, 05 Oct 2009 12:20:30 +0800
From: Ning Zong <zongning@huawei.com>
To: p2psip@ietf.org
Message-id: <004d01ca4573$2cc53e00$510ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/mixed; boundary="Boundary_(ID_C7cfUWD+Jxhy0SAqOUkfQA)"
Thread-index: AcpFcjwTvdgOqCVGQueMVFzBQiroigAACoGg
Subject: [P2PSIP] FW: New Version Notification for draft-jiang-p2psip-relay-03
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2009 04:19:12 -0000
Hi, all, A new version of I-D "An extension to RELOAD to support Direct Response and Relay Peer routing" - draft-jiang-p2psip-relay-03 has been uploaded to IETF and attached in this message. The main modification is the new section 5 where the authors compare the cost of SRR, DRR and RPR. Comments and suggestions are welcome! Thanks. BR, Ning Zong -----Original Message----- From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] Sent: Monday, October 05, 2009 12:12 PM To: zongning@huawei.com Cc: jiang.x.f@huawei.com; ron.even.tlv@gmail.com; zhangyunfei@chinamobile.com Subject: New Version Notification for draft-jiang-p2psip-relay-03 A new version of I-D, draft-jiang-p2psip-relay-03.txt has been successfuly submitted by Ning Zong and posted to the IETF repository. Filename: draft-jiang-p2psip-relay Revision: 03 Title: An extension to RELOAD to support Direct Response and Relay Peer routing Creation_date: 2009-10-03 WG ID: Independent Submission Number_of_pages: 23 Abstract: This document proposes an optional extension to RELOAD to support direct response and relay peer routing modes. RELOAD recommends symmetric recursive routing for routing messages. The new optional extensions provide a shorter route for responses reducing the overhead on intermediary peers and describe the potential cases where these extensions can be used. The IETF Secretariat.