IETF Logo Mail Archive

[pcp] Ensuring Address Reuse In the Pinhole Control Protocol (PCP)

Tina TSOU <tena@huawei.com> Sat, 16 October 2010 06:25 UTC

Return-Path: <tena@huawei.com>
X-Original-To: pcp@core3.amsl.com
Delivered-To: pcp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38C303A6BBE for <pcp@core3.amsl.com>; Fri, 15 Oct 2010 23:25:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.586
X-Spam-Level:
X-Spam-Status: No, score=-97.586 tagged_above=-999 required=5 tests=[AWL=2.908, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 VtxaTVLuvALu for <pcp@core3.amsl.com>; Fri, 15 Oct 2010 23:25:03 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 01FBB3A6A91 for <pcp@ietf.org>; Fri, 15 Oct 2010 23:25:03 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAD006LIDVRV9@szxga05-in.huawei.com> for pcp@ietf.org; Sat, 16 Oct 2010 14:26:15 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAD00M8LDVRTG@szxga05-in.huawei.com> for pcp@ietf.org; Sat, 16 Oct 2010 14:26:15 +0800 (CST)
Received: from [192.168.1.7] (c-24-7-50-101.hsd1.ca.comcast.net [24.7.50.101]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LAD00HH2DVOQ3@szxml02-in.huawei.com> for pcp@ietf.org; Sat, 16 Oct 2010 14:26:15 +0800 (CST)
Date: Fri, 15 Oct 2010 23:26:11 -0700
From: Tina TSOU <tena@huawei.com>
To: pcp@ietf.org
Message-id: <07A90FBB-EB5F-4623-A455-E9DF251138BF@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: multipart/alternative; boundary="Boundary_(ID_0j2V68878n87eVkRzLdLOw)"
Subject: [pcp] Ensuring Address Reuse In the Pinhole Control Protocol (PCP)
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Oct 2010 06:25:04 -0000

Hi PCPers,
An I-D "Ensuring Address Reuse In the Pinhole Control Protocol (PCP)"  
was posted just now.

http://www.ietf.org/id/draft-tsou-pcp-address-modify-00.txt

Abstract

    This document proposes that a field be added to the PIN-REQUEST
    message in the Pinhole Control Protocol to ask that the new mapping
    being requested reuse the same external address already assigned to
    the requesting device.  The actual form of this new field is
    discussed within the document.

Good night.

B. R.
Tina
http://tinatsou.weebly.com

v2.23.0 | Report a Bug | By Email