[P2PSIP] FW: New Version Notification for draft-jiang-p2psip-relay-04
Ning Zong <zongning@huawei.com> Tue, 06 April 2010 02:39 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 6AD1D3A6819 for <p2psip@core3.amsl.com>; Mon, 5 Apr 2010 19:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.895
X-Spam-Level:
X-Spam-Status: No, score=-97.895 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 k80B24Wu0bf8 for <p2psip@core3.amsl.com>; Mon, 5 Apr 2010 19:39:08 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id B6EDE3A67EC for <p2psip@ietf.org>; Mon, 5 Apr 2010 19:39:08 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L0F006VKOOUEO@szxga02-in.huawei.com> for p2psip@ietf.org; Tue, 06 Apr 2010 10:38:54 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L0F004M5OOTTH@szxga02-in.huawei.com> for p2psip@ietf.org; Tue, 06 Apr 2010 10:38:54 +0800 (CST)
Received: from z63316 ([10.138.84.86]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L0F006ATOOTXN@szxml04-in.huawei.com> for p2psip@ietf.org; Tue, 06 Apr 2010 10:38:53 +0800 (CST)
Date: Tue, 06 Apr 2010 10:38:53 +0800
From: Ning Zong <zongning@huawei.com>
To: p2psip@ietf.org
Message-id: <007901cad532$4c4dab00$56548a0a@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: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: AcrVMMOV1JUiKQt6Q2WTbiWrwZNzOAAAFLrg
Subject: [P2PSIP] FW: New Version Notification for draft-jiang-p2psip-relay-04
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: Tue, 06 Apr 2010 02:39:10 -0000
Hi, Folks, A new -04 revision of Direct Response and Relay Routing draft has been uploaded to IETF repository. The main revision is to clarify the number of messages used by DRR/RPR with (D)TLS connections, and we keep the message header part open and to be aligned with base draft. BR, Ning Zong -----Original Message----- From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] Sent: Tuesday, April 06, 2010 10:28 AM 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-04 A new version of I-D, draft-jiang-p2psip-relay-04.txt has been successfully submitted by Ning Zong and posted to the IETF repository. Filename: draft-jiang-p2psip-relay Revision: 04 Title: An extension to RELOAD to support Direct Response and Relay Peer routing Creation_date: 2010-04-06 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.