
From xiaohong.deng@orange-ftgroup.com  Thu May  5 04:03:50 2011
Return-Path: <xiaohong.deng@orange-ftgroup.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B45C7E085F for <pcp@ietfa.amsl.com>; Thu,  5 May 2011 04:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7ppt+iRwi1A for <pcp@ietfa.amsl.com>; Thu,  5 May 2011 04:03:50 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id 06B18E0869 for <pcp@ietf.org>; Thu,  5 May 2011 04:03:49 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 7AF876C0005; Thu,  5 May 2011 12:55:09 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id 6F8F96C0002; Thu,  5 May 2011 12:55:09 +0200 (CEST)
Received: from ch-mailsrv.rd.francetelecom.fr ([10.193.250.27]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 5 May 2011 12:54:33 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 5 May 2011 18:54:29 +0800
Message-ID: <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: <05c101cc05bc$9d5d9c10$d818d430$@com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
Thread-Index: AcvpgbZjqATPUsFnRFan3ixj2Y8FqQAlk4zAAAdKXvAAJLt/0AAPaQzwAI5RLNAAAOWpIAAs7yOgAARenKAAt94SIAIfj1bAAtYosmAAC6vpAAAci1MgAAPZPWAAAeTygAARimagAVNyAQA=
References: <0cb801cbe29e$ee401b80$cac05280$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01621A9D@ch-mailsrv.rd.francetelecom.fr> <B116E08B-C28F-4FDE-855A-88DAA0B34E0D@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621DA1@ch-mailsrv.rd.francetelecom.fr> <65E8E82B-3C4A-479A-B158-76E56E96DC47@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621FE6@ch-mailsrv.rd.francetelecom.fr> <1e6601cbea35$abd8f5c0$038ae140$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016221BC@ch-mailsrv.rd.francetelecom.fr> <22fd01cbeb06$c4793500$4d6b9f00$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr> <03e101cbed42$d80d0ef0$88272cd0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr> <095601cbee08$9ef0c780$dcd25680$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr> <0f7901cbf965$ea64aa70$bf2dff50$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr> <013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 BE41A 8D	D2FC016ED 208	@ch-mailsrv.rd.francetelecom.fr> <044a01cc056e$977c9f10$c675dd30$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr> <05c101cc05bc$9d5d9c10$d818d430$@com>
From: <xiaohong.deng@orange-ftgroup.com>
To: <dwing@cisco.com>
X-OriginalArrivalTime: 05 May 2011 10:54:33.0776 (UTC) FILETIME=[D16C6300:01CC0B12]
Cc: cheshire@apple.com, pcp@ietf.org
Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 05 May 2011 11:03:50 -0000

|I wasn't planning on it.  What is your suggested text? =20
|
|I slightly changed the wording of " Implementing MAP with=20
|non-EIM NATs",=20
|http://tools.ietf.org/html/draft-ietf-pcp-base-09#section-11.1,
|to cover both connections from separate hosts (using the same=20
|source port) and connections from the same host (using the=20
|same source port) -- a change which I think causes the text to=20
|include an issue Francis raised in private email.
|
|But I don't know if you're describing a similar, related=20
|problem with PREFER_FAILURE or what.  Because, frankly, I=20
|don't understand the issue and need some hand-holding to=20
|understand the problem.
|With that understanding, I could have a chance to write text. =20
|But as I do not understand the problem, I cannot successfully=20
|write any text..
|
|So:  can you suggest text, please?

The concern of PREFER_FAILURE option is with EIM NAT:
Assume there is first an implicit dynamic mappings translating X1:x1 to
X1':x1',
and then recieved a MAP4 request with  PREFER_FAILURE option asking for
port y1 which is not equal to x1', how does the EIM NAT behave? return
an error
code?

BR,
Xiaohong

|
|-d

From dwing@cisco.com  Thu May  5 07:27:54 2011
Return-Path: <dwing@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 819AAE08B8 for <pcp@ietfa.amsl.com>; Thu,  5 May 2011 07:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.352
X-Spam-Level: 
X-Spam-Status: No, score=-110.352 tagged_above=-999 required=5 tests=[AWL=0.247, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uyOJIkLM7Q2t for <pcp@ietfa.amsl.com>; Thu,  5 May 2011 07:27:53 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id A9117E08B6 for <pcp@ietf.org>; Thu,  5 May 2011 07:27:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1928; q=dns/txt; s=iport; t=1304605673; x=1305815273; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=fJ24EuhXP1v7seUnHGqg/fJ/cd6bQwEul5mt/tQuQV4=; b=XSTZyExd4nG1Gl4KQ062estaDaFBOXAw8r4szyA15tz0OVJ+/qXVA7pa GZBD2TcSPaVBWPp/L88bDocOq4d/AtX582X/BwBrme8H36sMLc5aCrXtH xb/RCX3nf0tslSAxWon4Rr9TD40vBflbr/4ya+rFIwyf6ODYN6EdJqdBG M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ar8BAFezwk2rRDoH/2dsb2JhbACYEUCBJIxBd6cmnjKGBwSGOJAsh1U
X-IronPort-AV: E=Sophos;i="4.64,319,1301875200"; d="scan'208";a="442324241"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-1.cisco.com with ESMTP; 05 May 2011 14:27:53 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p45ERr42003430; Thu, 5 May 2011 14:27:53 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <xiaohong.deng@orange-ftgroup.com>
References: <0cb801cbe29e$ee401b80$cac05280$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01621A9D@ch-mailsrv.rd.francetelecom.fr> <B116E08B-C28F-4FDE-855A-88DAA0B34E0D@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621DA1@ch-mailsrv.rd.francetelecom.fr> <65E8E82B-3C4A-479A-B158-76E56E96DC47@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621FE6@ch-mailsrv.rd.francetelecom.fr> <1e6601cbea35$abd8f5c0$038ae140$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016221BC@ch-mailsrv.rd.francetelecom.fr> <22fd01cbeb06$c4793500$4d6b9f00$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr> <03e101cbed42$d80d0ef0$88272cd0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr> <095601cbee08$9ef0c780$dcd25680$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr> <0f7901cbf965$ea64aa70$bf2dff50$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr> <013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 BE41A	8D	D2FC016ED 208	@ch-mailsrv.rd.francetelecom.fr> <044a01cc056e$977c9f10$c675dd30$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr> <05c101cc05bc$9d5d9c10$d818d430$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr>
Date: Thu, 5 May 2011 07:27:52 -0700
Message-ID: <0b9c01cc0b30$9ea57100$dbf05300$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvpgbZjqATPUsFnRFan3ixj2Y8FqQAlk4zAAAdKXvAAJLt/0AAPaQzwAI5RLNAAAOWpIAAs7yOgAARenKAAt94SIAIfj1bAAtYosmAAC6vpAAAci1MgAAPZPWAAAeTygAARimagAVNyAQAACVTukA==
Content-Language: en-us
Cc: cheshire@apple.com, pcp@ietf.org
Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 05 May 2011 14:27:54 -0000

> -----Original Message-----
> From: xiaohong.deng@orange-ftgroup.com [mailto:xiaohong.deng@orange-
> ftgroup.com]
> Sent: Thursday, May 05, 2011 3:54 AM
> To: dwing@cisco.com
> Cc: pcp@ietf.org; cheshire@apple.com
> Subject: RE: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
> 
> 
> |I wasn't planning on it.  What is your suggested text?
> |
> |I slightly changed the wording of " Implementing MAP with
> |non-EIM NATs",
> |http://tools.ietf.org/html/draft-ietf-pcp-base-09#section-11.1,
> |to cover both connections from separate hosts (using the same
> |source port) and connections from the same host (using the
> |same source port) -- a change which I think causes the text to
> |include an issue Francis raised in private email.
> |
> |But I don't know if you're describing a similar, related
> |problem with PREFER_FAILURE or what.  Because, frankly, I
> |don't understand the issue and need some hand-holding to
> |understand the problem.
> |With that understanding, I could have a chance to write text.
> |But as I do not understand the problem, I cannot successfully
> |write any text..
> |
> |So:  can you suggest text, please?
> 
> The concern of PREFER_FAILURE option is with EIM NAT:
> Assume there is first an implicit dynamic mappings translating X1:x1 to
> X1':x1',
> and then recieved a MAP4 request with  PREFER_FAILURE option asking for
> port y1 which is not equal to x1', how does the EIM NAT behave? return
> an error code?

Thanks for the explanation.  Turning it into an example:

dynamic mapping:
  inside address:              192.168.1.1:12345  (X1:x1)
  external address:            192.0.2.1:5555     (X1':x1')

MAP4 request, with PREFER_FAILURE:
  inside address:              ?192.168.1.1:12345?, I assume?
  requested external address:  192.0.2.1:9999 (9999 is different from 5555)

It can return the error CANNOT_PROVIDE_EXTERNAL_PORT.

-d



From Internet-Drafts@ietf.org  Thu May  5 11:15:03 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76BE9E08DC; Thu,  5 May 2011 11:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7MSJb9o0n1Mz; Thu,  5 May 2011 11:15:02 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30090E0901; Thu,  5 May 2011 11:15:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.53
Message-ID: <20110505181502.4115.20308.idtracker@ietfa.amsl.com>
Date: Thu, 05 May 2011 11:15:02 -0700
Cc: pcp@ietf.org
Subject: [pcp] I-D ACTION:draft-ietf-pcp-base-10.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 05 May 2011 18:15:03 -0000

--NextPart

A new Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Port Control Protocol Working Group of the IETF.

    Title         : Port Control Protocol (PCP)
    Author(s)     : D. Wing, et al
    Filename      : draft-ietf-pcp-base-10.txt
    Pages         : 66
    Date          : 2011-04-29
    
   Port Control Protocol allows a host to control how incoming IPv6 or
   IPv4 packets are translated and forwarded by a network address
   translator (NAT) or simple firewall to an IPv6 or IPv4 host, and also
   allows a host to optimize its NAT keepalive messages.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pcp-base-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-pcp-base-10.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-05-05110802.I-D@ietf.org>


--NextPart--

From xiaohong.deng@orange-ftgroup.com  Fri May  6 05:47:48 2011
Return-Path: <xiaohong.deng@orange-ftgroup.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C42BDE06F2 for <pcp@ietfa.amsl.com>; Fri,  6 May 2011 05:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rwfs7hyldkpr for <pcp@ietfa.amsl.com>; Fri,  6 May 2011 05:47:48 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id 1B994E06C5 for <pcp@ietf.org>; Fri,  6 May 2011 05:47:47 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id B5E57738015; Fri,  6 May 2011 14:47:12 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id AADA0738016; Fri,  6 May 2011 14:47:12 +0200 (CEST)
Received: from ch-mailsrv.rd.francetelecom.fr ([10.193.250.27]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 6 May 2011 14:46:13 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 6 May 2011 20:46:09 +0800
Message-ID: <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: <0b9c01cc0b30$9ea57100$dbf05300$@com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE:[pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
Thread-Index: AcvpgbZjqATPUsFnRFan3ixj2Y8FqQAlk4zAAAdKXvAAJLt/0AAPaQzwAI5RLNAAAOWpIAAs7yOgAARenKAAt94SIAIfj1bAAtYosmAAC6vpAAAci1MgAAPZPWAAAeTygAARimagAVNyAQAACVTukAAtJnWw
References: <0cb801cbe29e$ee401b80$cac05280$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01621A9D@ch-mailsrv.rd.francetelecom.fr> <B116E08B-C28F-4FDE-855A-88DAA0B34E0D@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621DA1@ch-mailsrv.rd.francetelecom.fr> <65E8E82B-3C4A-479A-B158-76E56E96DC47@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621FE6@ch-mailsrv.rd.francetelecom.fr> <1e6601cbea35$abd8f5c0$038ae140$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016221BC@ch-mailsrv.rd.francetelecom.fr> <22fd01cbeb06$c4793500$4d6b9f00$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr> <03e101cbed42$d80d0ef0$88272cd0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr> <095601cbee08$9ef0c780$dcd25680$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr> <0f7901cbf965$ea64aa70$bf2dff50$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr> <013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 BE4 1A	8D	D2FC01 6ED	208	@ch-mailsrv.rd.francetelecom.fr> <044a01cc056e$977c9f10$c675dd30$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr> <05c101cc05bc$9d5d9c10$d818d430$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr> <0b9c01cc0b30$9ea57100$dbf05300$@com>
From: <xiaohong.deng@orange-ftgroup.com>
To: <dwing@cisco.com>
X-OriginalArrivalTime: 06 May 2011 12:46:13.0736 (UTC) FILETIME=[9552E680:01CC0BEB]
Cc: cheshire@apple.com, pcp@ietf.org
Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 06 May 2011 12:47:48 -0000

Hello Dan,

Please see inline.
|
|Thanks for the explanation.  Turning it into an example:
|
|dynamic mapping:
|  inside address:              192.168.1.1:12345  (X1:x1)
|  external address:            192.0.2.1:5555     (X1':x1')
|
|MAP4 request, with PREFER_FAILURE:
|  inside address:              ?192.168.1.1:12345?, I assume?
|  requested external address:  192.0.2.1:9999 (9999 is=20
|different from 5555)

Exactly!

|
|It can return the error CANNOT_PROVIDE_EXTERNAL_PORT.

But the reason why the PREFER_FAILURE option fails is due to internal
port
conflict with an implicit dynamic mapping (it happens during our UpnP
IWF=20
prototype test) rather than external port available, which means
PREFER_FAILURE=20
MAP still has a chance to succeed if it waits the implicit dynamic
mapping, which
is usually configured with short expire time  (e.g., 60s) comparing to
explicit dynamic=20
mappings, to be expired.

So, I propose another error code instead of CANNOT_PROVIDE_EXTERNAL_PORT
to inform the IWF wait for a short time and sent the request again, so
that the IWF will
succeed in a second try instead of returning an error to UPnP client in
the first place.

How do you think?

Beside, are there some text in base -10 describing how EIM NAT acts when
a MAP4 request
(without PREFER_FAILURE option) hits an implicit dynamic mapping, in
particular, whether or
not change the type and the lifetime of the exist implicit dynamic
mapping?

Thanks,
Xiaohong

|
|-d
|
|
|

From simon.perreault@viagenie.ca  Fri May  6 06:25:22 2011
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE574E0694 for <pcp@ietfa.amsl.com>; Fri,  6 May 2011 06:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.764
X-Spam-Level: 
X-Spam-Status: No, score=-1.764 tagged_above=-999 required=5 tests=[AWL=-0.653, BAYES_05=-1.11, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F8JbUi7sRiFF for <pcp@ietfa.amsl.com>; Fri,  6 May 2011 06:25:22 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 9D277E0691 for <pcp@ietf.org>; Fri,  6 May 2011 06:25:21 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:21d:60ff:fed7:e732]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 43E5420CC2 for <pcp@ietf.org>; Fri,  6 May 2011 09:25:20 -0400 (EDT)
Message-ID: <4DC3F6BF.3020500@viagenie.ca>
Date: Fri, 06 May 2011 09:25:19 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110320 Fedora/3.1.9-4.fc16 Lightning/1.0b3pre Thunderbird/3.1.9
MIME-Version: 1.0
To: pcp@ietf.org
References: <0cb801cbe29e$ee401b80$cac05280$@com>	<22fd01cbeb06$c4793500$4d6b9f00$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr>	<03e101cbed42$d80d0ef0$88272cd0$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr>	<095601cbee08$9ef0c780$dcd25680$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr>	<0f7901cbf965$ea64aa70$bf2dff50$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr>	<013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 BE4	1A	8D	D2FC01 6ED	208	@ch-mailsrv.rd.francetelecom.fr>	<044a01cc056e$977c9f10$c675dd30$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr>	<05c101cc05bc$9d5d9c10$d818d430$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr>	<0b9c01cc0b30$9ea57100$dbf05300$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 06 May 2011 13:25:22 -0000

On 2011-05-06 08:46, xiaohong.deng@orange-ftgroup.com wrote:
> So, I propose another error code instead of CANNOT_PROVIDE_EXTERNAL_PORT
> to inform the IWF wait for a short time and sent the request again, so
> that the IWF will
> succeed in a second try instead of returning an error to UPnP client in
> the first place.

Why not just set the lifetime in the error response to a low value
instead of creating a new error code?

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From dwing@cisco.com  Mon May  9 15:21:39 2011
Return-Path: <dwing@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91F3EE076B for <pcp@ietfa.amsl.com>; Mon,  9 May 2011 15:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.393
X-Spam-Level: 
X-Spam-Status: No, score=-110.393 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 47YF9ULXr8FT for <pcp@ietfa.amsl.com>; Mon,  9 May 2011 15:21:38 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA7FE0760 for <pcp@ietf.org>; Mon,  9 May 2011 15:21:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2505; q=dns/txt; s=iport; t=1304979698; x=1306189298; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=v3oPgxf5Ed+kEHZ9ANjoPBABVj8Tzg4XWvvG0baImCI=; b=VE/jI8OpNdtZkFeQBVe4JmLEAsI4X2vgIx+cspjcYDGMbMm4ofyrdDQL 5fxi3tBsyDeujKNB81kXx9+LJvnGBW6l8RgN2vjGGBioT3oZM6GYYm2Hz AA4qG84VyU/AKUn8B/8AtP3/v3ESZHnkElYzSyO0QRUOXaXxO1LTQi4pF 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApEBAIdnyE2rRDoJ/2dsb2JhbACXUkCBJIxLd4hxnwueLoYMBIZAkEWHXQ
X-IronPort-AV: E=Sophos;i="4.64,342,1301875200"; d="scan'208";a="444539180"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-1.cisco.com with ESMTP; 09 May 2011 22:21:37 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p49MLb0L031491; Mon, 9 May 2011 22:21:37 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <xiaohong.deng@orange-ftgroup.com>
References: <0cb801cbe29e$ee401b80$cac05280$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01621A9D@ch-mailsrv.rd.francetelecom.fr> <B116E08B-C28F-4FDE-855A-88DAA0B34E0D@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621DA1@ch-mailsrv.rd.francetelecom.fr> <65E8E82B-3C4A-479A-B158-76E56E96DC47@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621FE6@ch-mailsrv.rd.francetelecom.fr> <1e6601cbea35$abd8f5c0$038ae140$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016221BC@ch-mailsrv.rd.francetelecom.fr> <22fd01cbeb06$c4793500$4d6b9f00$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr> <03e101cbed42$d80d0ef0$88272cd0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr> <095601cbee08$9ef0c780$dcd25680$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr> <0f7901cbf965$ea64aa70$bf2dff50$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr> <013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 BE4	1A	8D	D2FC01 6ED	208	@ch-mailsrv.rd.francetelecom.fr> <044a01cc056e$977c9f10$c675dd30$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr> <05c101cc05bc$9d5d9c10$d818d430$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr> <0b9c01cc0b30$9ea57100$dbf05300$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr>
Date: Mon, 9 May 2011 15:21:37 -0700
Message-ID: <069001cc0e97$764f2290$62ed67b0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvpgbZjqATPUsFnRFan3ixj2Y8FqQAlk4zAAAdKXvAAJLt/0AAPaQzwAI5RLNAAAOWpIAAs7yOgAARenKAAt94SIAIfj1bAAtYosmAAC6vpAAAci1MgAAPZPWAAAeTygAARimagAVNyAQAACVTukAAtJnWwAKzBQvA=
Content-Language: en-us
Cc: cheshire@apple.com, pcp@ietf.org
Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 09 May 2011 22:21:39 -0000

> -----Original Message-----
> From: xiaohong.deng@orange-ftgroup.com [mailto:xiaohong.deng@orange-
> ftgroup.com]
> Sent: Friday, May 06, 2011 5:46 AM
> To: dwing@cisco.com
> Cc: pcp@ietf.org; cheshire@apple.com
> Subject: RE:[pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
> 
> Hello Dan,
> 
> Please see inline.
> |
> |Thanks for the explanation.  Turning it into an example:
> |
> |dynamic mapping:
> |  inside address:              192.168.1.1:12345  (X1:x1)
> |  external address:            192.0.2.1:5555     (X1':x1')
> |
> |MAP4 request, with PREFER_FAILURE:
> |  inside address:              ?192.168.1.1:12345?, I assume?
> |  requested external address:  192.0.2.1:9999 (9999 is
> |different from 5555)
> 
> Exactly!
> 
> |
> |It can return the error CANNOT_PROVIDE_EXTERNAL_PORT.
> 
> But the reason why the PREFER_FAILURE option fails is due to
> internal port conflict with an implicit dynamic mapping (it happens
> during our UpnP IWF prototype test) rather than external port
> available, which means PREFER_FAILURE MAP still has a chance to
> succeed if it waits the implicit dynamic mapping, which is usually
> configured with short expire time  (e.g., 60s) comparing to explicit
> dynamic mappings, to be expired.
>
> So, I propose another error code instead of
> CANNOT_PROVIDE_EXTERNAL_PORT to inform the IWF wait for a short time
> and sent the request again, so that the IWF will succeed in a second
> try instead of returning an error to UPnP client in the first place.> 

What makes us believe the port would be freed after a short time?  I
mean, the port could be the client's XMPP, SIP, IMAP, or HTTP persistent
connection -- all of which are pretty long-lived.  It could also be a 
short-lived connection (DNS, HTTP non-persistent connection).

Is there a typical amount of time a UPnP control point will wait for
a negative response?

> How do you think?
> 
> Beside, are there some text in base -10 describing how EIM NAT acts
> when
> a MAP4 request
> (without PREFER_FAILURE option) hits an implicit dynamic mapping, in
> particular, whether or
> not change the type and the lifetime of the exist implicit dynamic
> mapping?

You mean, a suggestion that it shorten the lifetime?  That seems
ill-advised, as it would make the NAT's operation less deterministic
(from the perspective of the application that made the implicit
dynamic mapping).

-d


> Thanks,
> Xiaohong
> 
> |
> |-d
> |
> |
> |


From dwing@cisco.com  Mon May  9 15:23:14 2011
Return-Path: <dwing@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1614BE076B for <pcp@ietfa.amsl.com>; Mon,  9 May 2011 15:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.352
X-Spam-Level: 
X-Spam-Status: No, score=-109.352 tagged_above=-999 required=5 tests=[AWL=-0.857, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i55qxBRFMWrE for <pcp@ietfa.amsl.com>; Mon,  9 May 2011 15:23:13 -0700 (PDT)
Received: from sj-iport-3.cisco.com (unknown [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 22C24E0760 for <pcp@ietf.org>; Mon,  9 May 2011 15:23:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1350; q=dns/txt; s=iport; t=1304979793; x=1306189393; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=uGernbxJefwi+BQNHNTFHikgecibUkhiKEIOAYKO+iA=; b=kSl1qUwDo/Mbzca+kKSu83zRAjKf3W8/0Um6DPX0u8q8iNTkn2eyYw59 DEmE0lTKL2PS+ItB8QRdljDflx3knUr6P50ryK5cXiyKfksaTb38dWlp3 eIOEAhgJgoOlxJ5UvVDhE2y3CNPimRKd2CzXXK1cIDhdoudbgZafe2OW3 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQBAKloyE2rRDoJ/2dsb2JhbACXUoFkhgyBTIRzd4hxnyKeLoYMBIZAkEWHXQ
X-IronPort-AV: E=Sophos;i="4.64,342,1301875200"; d="scan'208";a="311878026"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-3.cisco.com with ESMTP; 09 May 2011 22:23:12 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p49MNCQe000688; Mon, 9 May 2011 22:23:12 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Simon Perreault'" <simon.perreault@viagenie.ca>, <pcp@ietf.org>
References: <0cb801cbe29e$ee401b80$cac05280$@com>	<22fd01cbeb06$c4793500$4d6b9f00$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr>	<03e101cbed42$d80d0ef0$88272cd0$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr>	<095601cbee08$9ef0c780$dcd25680$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr>	<0f7901cbf965$ea64aa70$bf2dff50$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr>	<013001cc04ed$14550c20$3cff2460$@com>	<0962B0BEF842A24191AD9 BE4	1A	8D	D2FC01	6ED	208	@ch-mailsrv.rd.francetelecom.fr>	<044a01cc056e$977c9f10$c675dd30$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr>	<05c101cc05bc$9d5d9c10$d818d430$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr>	<0b9c01cc0b30$9ea57100$dbf05300$@com>	<0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr> <4DC3F6BF.3020500@viagenie.ca>
In-Reply-To: <4DC3F6BF.3020500@viagenie.ca>
Date: Mon, 9 May 2011 15:23:11 -0700
Message-ID: <069101cc0e97$ae982980$0bc87c80$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwL8VnjJPquF5WyRmSGxuG+6TMV3ACph0Wg
Content-Language: en-us
Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 09 May 2011 22:23:14 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Simon Perreault
> Sent: Friday, May 06, 2011 6:25 AM
> To: pcp@ietf.org
> Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
> 
> On 2011-05-06 08:46, xiaohong.deng@orange-ftgroup.com wrote:
> > So, I propose another error code instead of
> CANNOT_PROVIDE_EXTERNAL_PORT
> > to inform the IWF wait for a short time and sent the request again,
> so
> > that the IWF will
> > succeed in a second try instead of returning an error to UPnP client
> in
> > the first place.
> 
> Why not just set the lifetime in the error response to a low value
> instead of creating a new error code?

That seems reasonable.  We could provide guidance that the lifetime
for that error be a short value if it's a non-EIM NAT and an implicit 
dynamic mapping prevents allocating that port, in order to allow the
IWF to retry pretty quickly in the hope the port is no longer used.

-d


> Simon
> --
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> STUN/TURN server               --> http://numb.viagenie.ca
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From xiaohong.deng@orange-ftgroup.com  Tue May 10 03:05:52 2011
Return-Path: <xiaohong.deng@orange-ftgroup.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42C54E0688 for <pcp@ietfa.amsl.com>; Tue, 10 May 2011 03:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TYa6CJOrFYIq for <pcp@ietfa.amsl.com>; Tue, 10 May 2011 03:05:51 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by ietfa.amsl.com (Postfix) with ESMTP id 5E49CE0846 for <pcp@ietf.org>; Tue, 10 May 2011 03:05:51 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 531698B800D; Tue, 10 May 2011 12:06:27 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 601838B800B; Tue, 10 May 2011 12:06:22 +0200 (CEST)
Received: from ch-mailsrv.rd.francetelecom.fr ([10.193.250.27]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 10 May 2011 12:05:44 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 May 2011 18:05:39 +0800
Message-ID: <0962B0BEF842A24191AD9BE41A8DD2FC017269C3@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: <069001cc0e97$764f2290$62ed67b0$@com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE:[pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
Thread-Index: AcvpgbZjqATPUsFnRFan3ixj2Y8FqQAlk4zAAAdKXvAAJLt/0AAPaQzwAI5RLNAAAOWpIAAs7yOgAARenKAAt94SIAIfj1bAAtYosmAAC6vpAAAci1MgAAPZPWAAAeTygAARimagAVNyAQAACVTukAAtJnWwAKzBQvAAF43JUA==
References: <0cb801cbe29e$ee401b80$cac05280$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01621A9D@ch-mailsrv.rd.francetelecom.fr> <B116E08B-C28F-4FDE-855A-88DAA0B34E0D@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621DA1@ch-mailsrv.rd.francetelecom.fr> <65E8E82B-3C4A-479A-B158-76E56E96DC47@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621FE6@ch-mailsrv.rd.francetelecom.fr> <1e6601cbea35$abd8f5c0$038ae140$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016221BC@ch-mailsrv.rd.francetelecom.fr> <22fd01cbeb06$c4793500$4d6b9f00$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr> <03e101cbed42$d80d0ef0$88272cd0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr> <095601cbee08$9ef0c780$dcd25680$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr> <0f7901cbf965$ea64aa70$bf2dff50$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr> <013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 B E4	1A	8D	D2F C01	6ED	208	@ch-mailsrv.rd.francetelecom.fr> <044a01cc056e$977c9f10$c675dd30$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr> <05c101cc05bc$9d5d9c10$d818d430$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr> <0b9c01cc0b30$9ea57100$dbf05300$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr> <069001cc0e97$764f2290$62ed67b0$@com>
From: <xiaohong.deng@orange-ftgroup.com>
To: <dwing@cisco.com>
X-OriginalArrivalTime: 10 May 2011 10:05:44.0454 (UTC) FILETIME=[D37A1260:01CC0EF9]
Cc: cheshire@apple.com, pcp@ietf.org
Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 10 May 2011 10:05:52 -0000

|> So, I propose another error code instead of=20
|> CANNOT_PROVIDE_EXTERNAL_PORT to inform the IWF wait for a short time=20
|> and sent the request again, so that the IWF will succeed in a second=20
|> try instead of returning an error to UPnP client in the first place.>
|
|What makes us believe the port would be freed after a short=20
|time?  I mean, the port could be the client's XMPP, SIP, IMAP,=20
|or HTTP persistent connection -- all of which are pretty=20
|long-lived.  It could also be a short-lived connection (DNS,=20
|HTTP non-persistent connection).

The confilict dynamic implicit mappings that we ran into are often HTTP
non-persistent connection. But, yes you're right, it may run into long
life time=20
implicit mapping also.

|
|Is there a typical amount of time a UPnP control point will=20
|wait for a negative response?

As far as p2p application concerned, utorrent, vuzz and emule will=20
wait approximately 150s, 90s, 90s time respectively for a response.

When we made IWF delay 300s to send back a positive response,
All of them recovered from the error.

|
|> How do you think?
|>=20
|> Beside, are there some text in base -10 describing how EIM NAT acts=20
|> when a MAP4 request (without PREFER_FAILURE option) hits an implicit=20
|> dynamic mapping, in particular, whether or not change the=20
|type and the=20
|> lifetime of the exist implicit dynamic mapping?
|
|You mean, a suggestion that it shorten the lifetime?  That=20

No. And if it is a suggestion, should be suggested other wise--extend
the lifetime.
Not that here EIM was referred instead of Non-EIM.

|seems ill-advised, as it would make the NAT's operation less=20
|deterministic (from the perspective of the application that=20
|made the implicit dynamic mapping).

Would you please elaborate how EIM NAT,which assumed as free of  the=20
problem described in section 11.1, acts when a MAP4 request finds
an implicit dynamic already mapping exsit?  And why it doesn't have a
problem
in this case?

Thanks,
Xiaohong
opensource A+P: http://opensourceaplusp.weebly.com/



|
|-d
|

From dwing@cisco.com  Tue May 10 16:13:16 2011
Return-Path: <dwing@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 483E9E0691 for <pcp@ietfa.amsl.com>; Tue, 10 May 2011 16:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.925
X-Spam-Level: 
X-Spam-Status: No, score=-109.925 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qNEtrPTr2Uv6 for <pcp@ietfa.amsl.com>; Tue, 10 May 2011 16:13:15 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id 4DACDE06C3 for <pcp@ietf.org>; Tue, 10 May 2011 16:13:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3528; q=dns/txt; s=iport; t=1305069195; x=1306278795; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=z45ROhuBl60oKMx5fOTsFu/8laT6t/Lwjpf5Nn+EjRA=; b=ZsF89w3BPHW8BVTI+CCM+OW0Tt86B5w3PI7hLHvlOV4xVPbSsPKZFweu 2D9uI/KyiEADvMwNkKeTOmVA/ZRE2r11ynikbHvnUxJSu2KSHVM3uQPuS jLWX4+U0QqreZkI5l7UymOmHufLABSUlNz2zUM0piEa/1tjQ8eKpdDBvx Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAAObFyU2rRDoG/2dsb2JhbACXXIFkjEx3iHCgRJ4ihg8EhkKQTodf
X-IronPort-AV: E=Sophos;i="4.64,348,1301875200"; d="scan'208";a="695215260"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-6.cisco.com with ESMTP; 10 May 2011 23:13:15 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p4ANDExg012336; Tue, 10 May 2011 23:13:14 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <xiaohong.deng@orange-ftgroup.com>
References: <0cb801cbe29e$ee401b80$cac05280$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01621A9D@ch-mailsrv.rd.francetelecom.fr> <B116E08B-C28F-4FDE-855A-88DAA0B34E0D@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621DA1@ch-mailsrv.rd.francetelecom.fr> <65E8E82B-3C4A-479A-B158-76E56E96DC47@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621FE6@ch-mailsrv.rd.francetelecom.fr> <1e6601cbea35$abd8f5c0$038ae140$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016221BC@ch-mailsrv.rd.francetelecom.fr> <22fd01cbeb06$c4793500$4d6b9f00$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr> <03e101cbed42$d80d0ef0$88272cd0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr> <095601cbee08$9ef0c780$dcd25680$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr> <0f7901cbf965$ea64aa70$bf2dff50$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr> <013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 B	E4	1A	8D	D2F C01	6ED	208	@ch-mailsrv.rd.francetelecom.fr> <044a01cc056e$977c9f10$c675dd30$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr> <05c101cc05bc$9d5d9c10$d818d430$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr> <0b9c01cc0b30$9ea57100$dbf05300$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr> <069001cc0e97$764f2290$62ed67b0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC017269C3@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: <0962B0BEF842A24191AD9BE41A8DD2FC017269C3@ch-mailsrv.rd.francetelecom.fr>
Date: Tue, 10 May 2011 16:13:14 -0700
Message-ID: <0b2701cc0f67$d6c73790$8455a6b0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvpgbZjqATPUsFnRFan3ixj2Y8FqQAlk4zAAAdKXvAAJLt/0AAPaQzwAI5RLNAAAOWpIAAs7yOgAARenKAAt94SIAIfj1bAAtYosmAAC6vpAAAci1MgAAPZPWAAAeTygAARimagAVNyAQAACVTukAAtJnWwAKzBQvAAF43JUAALz+xA
Content-Language: en-us
Cc: cheshire@apple.com, pcp@ietf.org
Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 10 May 2011 23:13:16 -0000

> -----Original Message-----
> From: xiaohong.deng@orange-ftgroup.com [mailto:xiaohong.deng@orange-
> ftgroup.com]
> Sent: Tuesday, May 10, 2011 3:06 AM
> To: dwing@cisco.com
> Cc: pcp@ietf.org; cheshire@apple.com
> Subject: RE:[pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
> 
> 
> |> So, I propose another error code instead of
> |> CANNOT_PROVIDE_EXTERNAL_PORT to inform the IWF wait for a short time
> |> and sent the request again, so that the IWF will succeed in a second
> |> try instead of returning an error to UPnP client in the first
> place.>
> |
> |What makes us believe the port would be freed after a short
> |time?  I mean, the port could be the client's XMPP, SIP, IMAP,
> |or HTTP persistent connection -- all of which are pretty
> |long-lived.  It could also be a short-lived connection (DNS,
> |HTTP non-persistent connection).
> 
> The confilict dynamic implicit mappings that we ran into are often HTTP
> non-persistent connection. But, yes you're right, it may run into long
> life time
> implicit mapping also.
> 
> |
> |Is there a typical amount of time a UPnP control point will
> |wait for a negative response?
> 
> As far as p2p application concerned, utorrent, vuzz and emule will
> wait approximately 150s, 90s, 90s time respectively for a response.
> 
> When we made IWF delay 300s to send back a positive response,
> All of them recovered from the error.
> 
> |
> |> How do you think?
> |>
> |> Beside, are there some text in base -10 describing how EIM NAT acts
> |> when a MAP4 request (without PREFER_FAILURE option) hits an implicit
> |> dynamic mapping, in particular, whether or not change the
> |type and the
> |> lifetime of the exist implicit dynamic mapping?
> |
> |You mean, a suggestion that it shorten the lifetime?  That
> 
> No. And if it is a suggestion, should be suggested other wise--extend
> the lifetime.
> Not that here EIM was referred instead of Non-EIM.
> 
> |seems ill-advised, as it would make the NAT's operation less
> |deterministic (from the perspective of the application that
> |made the implicit dynamic mapping).
> 
> Would you please elaborate how EIM NAT,which assumed as free of  the
> problem described in section 11.1, acts when a MAP4 request finds
> an implicit dynamic already mapping exsit?  And why it doesn't have a
> problem in this case?

You're right, that if an EIM (or non-EIM) NAT receives a MAP request
that includes PREFER_FAILURE, it will need to return an error if
there is already an implicit (or explicit) dynamic mapping on the 
requested port.


I believe we have two proposals on the table right now, for when
a MAPx request contains the PREFER_FAILURE option if an implicit
dynamic mapping exists on that requested public port:

  * return the error CANNOT_PROVIDE_EXTERNAL_PORT with a
    short error lifetime to signal that the PCP client
    (IWF) should retry soon.

  * return a new error message, IMPLICIT_MAPPING_EXISTS, 
    with a short error lifetime to signal that the PCP
    client (IWF) should retry soon.

In both cases, the PCP client (IWF) behavior is the same --
after receiving the error, it waits "error lifetime" before
trying again to get the same port.

In both cases, the NAT needs to know if the existing
mapping was created implicitly or created explicitly, in order
to return the short error lifetime.

-d


> Thanks,
> Xiaohong
> opensource A+P: http://opensourceaplusp.weebly.com/
> 
> 
> 
> |
> |-d
> |


From xiaohong.deng@orange-ftgroup.com  Wed May 11 03:23:10 2011
Return-Path: <xiaohong.deng@orange-ftgroup.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22E0E069D for <pcp@ietfa.amsl.com>; Wed, 11 May 2011 03:23:10 -0700 (PDT)
X-Quarantine-ID: <CNDDlpDhqSw5>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace: References: ...> <0962B0BEF842A24191AD9\n  \n\t B\tE4\t1A\t8D\t\n[...]
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CNDDlpDhqSw5 for <pcp@ietfa.amsl.com>; Wed, 11 May 2011 03:23:10 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by ietfa.amsl.com (Postfix) with ESMTP id A434AE068C for <pcp@ietf.org>; Wed, 11 May 2011 03:23:09 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id A474D8B8004; Wed, 11 May 2011 12:23:46 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 9BAD08B8001; Wed, 11 May 2011 12:23:46 +0200 (CEST)
Received: from ch-mailsrv.rd.francetelecom.fr ([10.193.250.27]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 11 May 2011 12:23:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 11 May 2011 18:23:04 +0800
Message-ID: <0962B0BEF842A24191AD9BE41A8DD2FC0175717C@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: <0b2701cc0f67$d6c73790$8455a6b0$@com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE:[pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
Thread-Index: AcvpgbZjqATPUsFnRFan3ixj2Y8FqQAlk4zAAAdKXvAAJLt/0AAPaQzwAI5RLNAAAOWpIAAs7yOgAARenKAAt94SIAIfj1bAAtYosmAAC6vpAAAci1MgAAPZPWAAAeTygAARimagAVNyAQAACVTukAAtJnWwAKzBQvAAF43JUAALz+xAACcx+uA=
References: <0cb801cbe29e$ee401b80$cac05280$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01621A9D@ch-mailsrv.rd.francetelecom.fr> <B116E08B-C28F-4FDE-855A-88DAA0B34E0D@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621DA1@ch-mailsrv.rd.francetelecom.fr> <65E8E82B-3C4A-479A-B158-76E56E96DC47@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621FE6@ch-mailsrv.rd.francetelecom.fr> <1e6601cbea35$abd8f5c0$038ae140$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016221BC@ch-mailsrv.rd.francetelecom.fr> <22fd01cbeb06$c4793500$4d6b9f00$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr> <03e101cbed42$d80d0ef0$88272cd0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr> <095601cbee08$9ef0c780$dcd25680$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr> <0f7901cbf965$ea64aa70$bf2dff50$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr> <013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 ... B	E4	1A	8D	 D2F	C01	6ED	208	@ch-mailsrv.rd.francetelecom.fr> <044a01cc056e$977c9f10$c675dd30$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr> <05c101cc05bc$9d5d9c10$d818d430$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr> <0b9c01cc0b30$9ea57100$dbf05300$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr> <069001cc0e97$764f2290$62ed67b0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC017269C3@ch-mailsrv.rd.francetelecom.fr> <0b2701cc0f67$d6c73790$8455a6b0$@com>
From: <xiaohong.deng@orange-ftgroup.com>
To: <dwing@cisco.com>
X-OriginalArrivalTime: 11 May 2011 10:23:08.0626 (UTC) FILETIME=[6C43D320:01CC0FC5]
Cc: cheshire@apple.com, pcp@ietf.org
Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 11 May 2011 10:23:10 -0000

|You're right, that if an EIM (or non-EIM) NAT receives a MAP=20
|request that includes PREFER_FAILURE, it will need to return=20
|an error if there is already an implicit (or explicit) dynamic=20
|mapping on the requested port.
|
|
|I believe we have two proposals on the table right now, for when
|a MAPx request contains the PREFER_FAILURE option if an implicit
|dynamic mapping exists on that requested public port:

I guess you meant "dynamic mapping exists on that requested *internal*
port"?

|
|  * return the error CANNOT_PROVIDE_EXTERNAL_PORT with a
|    short error lifetime to signal that the PCP client
|    (IWF) should retry soon.
|
|  * return a new error message, IMPLICIT_MAPPING_EXISTS,=20
|    with a short error lifetime to signal that the PCP
|    client (IWF) should retry soon.
|
|In both cases, the PCP client (IWF) behavior is the same --
|after receiving the error, it waits "error lifetime" before
|trying again to get the same port.
|
|In both cases, the NAT needs to know if the existing
|mapping was created implicitly or created explicitly, in order
|to return the short error lifetime.

Yes, that could do. And how about the NAT  return the aging time=20
of existing mapping as the short error lifetime?

Don't see a strong need to define a new error code.
But  will it be more appropriate for IWF provide a more acurate
reason of error IMPLICIT_MAPPING_EXISTS,  to a user (e.g, log file)?


Another question:

Still, when a MAPx request does *not* contain the PREFER_FAILURE
option if an implicit dynamic mapping exists on that requested
*internal*
port, how does *EIM* NAT handle that?


|
|-d
|
|
|> Thanks,
|> Xiaohong
|> opensource A+P: http://opensourceaplusp.weebly.com/

From dwing@cisco.com  Wed May 11 08:21:04 2011
Return-Path: <dwing@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB096E072B for <pcp@ietfa.amsl.com>; Wed, 11 May 2011 08:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.166
X-Spam-Level: 
X-Spam-Status: No, score=-110.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qR+LAJuxtRbH for <pcp@ietfa.amsl.com>; Wed, 11 May 2011 08:21:03 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 4A692E0704 for <pcp@ietf.org>; Wed, 11 May 2011 08:21:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2745; q=dns/txt; s=iport; t=1305127263; x=1306336863; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=wnI3H2pXR6AyjdAJhylNAIcE1Z9Xb+6AWqUcXvG3F3Y=; b=l93DxVAZG56rKRBzk4K6Q5+h683mLEq0euMmF7HbPXidvD9enTl1qbjh SfSyu+CAiMozPpo/8XykPB1H2uDGFhf+rViOlRVfkAnbjh0dhJ+Lc0Hxh c6AiQLLgrul7OZ0DF1xjOVK0YhWDHJz6Rss+hXr3ZWx7CaUmtU0TKmirS 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIBAA+oyk2rRDoH/2dsb2JhbACXWUCBJIxOd4hwoXaeJYYQBIZDkE+HXw
X-IronPort-AV: E=Sophos;i="4.64,353,1301875200"; d="scan'208";a="313329663"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-3.cisco.com with ESMTP; 11 May 2011 15:21:02 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p4BFL2jT031585; Wed, 11 May 2011 15:21:02 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <xiaohong.deng@orange-ftgroup.com>
References: <0cb801cbe29e$ee401b80$cac05280$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01621A9D@ch-mailsrv.rd.francetelecom.fr> <B116E08B-C28F-4FDE-855A-88DAA0B34E0D@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621DA1@ch-mailsrv.rd.francetelecom.fr> <65E8E82B-3C4A-479A-B158-76E56E96DC47@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621FE6@ch-mailsrv.rd.francetelecom.fr> <1e6601cbea35$abd8f5c0$038ae140$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016221BC@ch-mailsrv.rd.francetelecom.fr> <22fd01cbeb06$c4793500$4d6b9f00$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr> <03e101cbed42$d80d0ef0$88272cd0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr> <095601cbee08$9ef0c780$dcd25680$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr> <0f7901cbf965$ea64aa70$bf2dff50$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr> <013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 B	E4	1A	8D	 D2F	C01	6ED	208	@ch-mailsrv.rd.francetelecom.fr> <044a01cc056e$977c9f10$c675dd30$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr> <05c101cc05bc$9d5d9c10$d818d430$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr> <0b9c01cc0b30$9ea57100$dbf05300$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr> <069001cc0e97$764f2290$62ed67b0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC017269C3@ch-mailsrv.rd.francetelecom.fr> <0b2701cc0f67$d6c73790$8455a6b0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0175717C@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: <0962B0BEF842A24191AD9BE41A8DD2FC0175717C@ch-mailsrv.rd.francetelecom.fr>
Date: Wed, 11 May 2011 08:21:04 -0700
Message-ID: <023b01cc0fef$0b47ff90$21d7feb0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvpgbZjqATPUsFnRFan3ixj2Y8FqQAlk4zAAAdKXvAAJLt/0AAPaQzwAI5RLNAAAOWpIAAs7yOgAARenKAAt94SIAIfj1bAAtYosmAAC6vpAAAci1MgAAPZPWAAAeTygAARimagAVNyAQAACVTukAAtJnWwAKzBQvAAF43JUAALz+xAACcx+uAAC0KF0A==
Content-Language: en-us
Cc: cheshire@apple.com, pcp@ietf.org
Subject: Re: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 11 May 2011 15:21:05 -0000

> -----Original Message-----
> From: xiaohong.deng@orange-ftgroup.com [mailto:xiaohong.deng@orange-
> ftgroup.com]
> Sent: Wednesday, May 11, 2011 3:23 AM
> To: dwing@cisco.com
> Cc: pcp@ietf.org; cheshire@apple.com
> Subject: RE:[pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS
> 
> |You're right, that if an EIM (or non-EIM) NAT receives a MAP
> |request that includes PREFER_FAILURE, it will need to return
> |an error if there is already an implicit (or explicit) dynamic
> |mapping on the requested port.
> |
> |
> |I believe we have two proposals on the table right now, for when
> |a MAPx request contains the PREFER_FAILURE option if an implicit
> |dynamic mapping exists on that requested public port:
> 
> I guess you meant "dynamic mapping exists on that requested *internal*
> port"?

Yes, that's what I intended to write.  

> |
> |  * return the error CANNOT_PROVIDE_EXTERNAL_PORT with a
> |    short error lifetime to signal that the PCP client
> |    (IWF) should retry soon.
> |
> |  * return a new error message, IMPLICIT_MAPPING_EXISTS,
> |    with a short error lifetime to signal that the PCP
> |    client (IWF) should retry soon.
> |
> |In both cases, the PCP client (IWF) behavior is the same --
> |after receiving the error, it waits "error lifetime" before
> |trying again to get the same port.
> |
> |In both cases, the NAT needs to know if the existing
> |mapping was created implicitly or created explicitly, in order
> |to return the short error lifetime.
> 
> Yes, that could do. And how about the NAT  return the aging time
> of existing mapping as the short error lifetime?

If I understand what you mean by 'aging time' correctly, it
is the lifetime of the existing mapping.  Our NATs (both
low end and high end) will allow a TCP mapping to persist
for a loooong time (an hour or so), idly.  Which means we
would return a lifetime of ~60 minutes.  That doesn't seem
useful for your purposes.

> Don't see a strong need to define a new error code.
> But  will it be more appropriate for IWF provide a more acurate
> reason of error IMPLICIT_MAPPING_EXISTS,  to a user (e.g, log file)?

Probably, yes.

I'll see what wording I can craft up later today.

> Another question:
> 
> Still, when a MAPx request does *not* contain the PREFER_FAILURE
> option if an implicit dynamic mapping exists on that requested
> *internal* port, how does *EIM* NAT handle that?

Seems it would have to return an error or do #2 of
http://tools.ietf.org/html/draft-ietf-pcp-base-10#section-11.1 (which needs
its text changed to accommodate).

-d


> 
> |
> |-d
> |
> |
> |> Thanks,
> |> Xiaohong
> |> opensource A+P: http://opensourceaplusp.weebly.com/


From dwing@cisco.com  Wed May 11 11:20:24 2011
Return-Path: <dwing@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FD31E07EB for <pcp@ietfa.amsl.com>; Wed, 11 May 2011 11:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.274
X-Spam-Level: 
X-Spam-Status: No, score=-110.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OL5OEsLYP90y for <pcp@ietfa.amsl.com>; Wed, 11 May 2011 11:20:23 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 45D99E06F5 for <pcp@ietf.org>; Wed, 11 May 2011 11:20:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=983; q=dns/txt; s=iport; t=1305138023; x=1306347623; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=lf1ogW2O7bcQUOZEQZXBOAmu6gw/oPsMmS9O9NWdANs=; b=TTAhfhzIJQ0wzXxu/BNSbF30Zr20jIcT4hKHynNvajI1OAMlUGmE1ipP +/biBzXVksxQDsAABMpzAVhIlOAm2sZLRL0txhB2CSWnlI/g1ZA34zwa8 meM6mgwCPQ2fuL+Eko46WH6tXAhY/lbY8pgJGnkOrM2odYxaw9A29tw88 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An4HAD/Syk2rRDoG/2dsb2JhbACYEYEkjE53iHChLJ4rhhAEhkOQT4df
X-IronPort-AV: E=Sophos;i="4.64,354,1301875200"; d="scan'208";a="313474626"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-3.cisco.com with ESMTP; 11 May 2011 18:20:22 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p4BIKMAW017232; Wed, 11 May 2011 18:20:22 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <xiaohong.deng@orange-ftgroup.com>
References: <0cb801cbe29e$ee401b80$cac05280$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01621A9D@ch-mailsrv.rd.francetelecom.fr> <B116E08B-C28F-4FDE-855A-88DAA0B34E0D@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621DA1@ch-mailsrv.rd.francetelecom.fr> <65E8E82B-3C4A-479A-B158-76E56E96DC47@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621FE6@ch-mailsrv.rd.francetelecom.fr> <1e6601cbea35$abd8f5c0$038ae140$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016221BC@ch-mailsrv.rd.francetelecom.fr> <22fd01cbeb06$c4793500$4d6b9f00$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr> <03e101cbed42$d80d0ef0$88272cd0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr> <095601cbee08$9ef0c780$dcd25680$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr> <0f7901cbf965$ea64aa70$bf2dff50$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr> <013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 B	E4	1A	8D	 D2F	C01	6ED	208	@ch-mailsrv.rd.francetelecom.fr> <044a01cc056e$977c9f10$c675dd30$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr> <05c101cc05bc$9d5d9c10$d818d430$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr> <0b9c01cc0b30$9ea57100$dbf05300$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr> <069001cc0e97$764f2290$62ed67b0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC017269C3@ch-mailsrv.rd.francetelecom.fr> <0b2701cc0f67$d6c73790$8455a6b0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0175717C@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: 
Date: Wed, 11 May 2011 11:20:22 -0700
Message-ID: <038701cc1008$1768aae0$463a00a0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvpgbZjqATPUsFnRFan3ixj2Y8FqQAlk4zAAAdKXvAAJLt/0AAPaQzwAI5RLNAAAOWpIAAs7yOgAARenKAAt94SIAIfj1bAAtYosmAAC6vpAAAci1MgAAPZPWAAAeTygAARimagAVNyAQAACVTukAAtJnWwAKzBQvAAF43JUAALz+xAACcx+uAAC0KF0AAGXC9Q
Content-Language: en-us
Cc: pcp@ietf.org
Subject: [pcp] EIM and dynamic mappings [was RE: hoping to eliminate IMPLICIT_MAPPING_EXISTS]
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 11 May 2011 18:20:24 -0000

Dan Wing wrote:

> Xiaohong Deng wrote:
> > Another question:
> >
> > Still, when a MAPx request does *not* contain the PREFER_FAILURE
> > option if an implicit dynamic mapping exists on that requested
> > *internal* port, how does *EIM* NAT handle that?
> 
> Seems it would have to return an error or do #2 of
> http://tools.ietf.org/html/draft-ietf-pcp-base-10#section-11.1 (which
> needs its text changed to accommodate).



I thought about this some more, and I believe EIM have no problem
here.

Let's say a host sends a packet from source port 12345 to the
Internet, which creates a mapping in their EIM NAT.  This will
be mapped to public port "X".  

The host then sends a PCP MAP4 request for internal-port=12345.
This is also mapped to public port "X".


Any traffic from the internal port 12345 is mapped to public
port "X".  And any traffic that arrives from the Internet to
public port "X" is mapped to the internal host's port 12345.

-d




From Francis.Dupont@fdupont.fr  Wed May 11 13:45:19 2011
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29A19E0870 for <pcp@ietfa.amsl.com>; Wed, 11 May 2011 13:45:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6oqJMPharnzd for <pcp@ietfa.amsl.com>; Wed, 11 May 2011 13:45:18 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id E5896E079B for <pcp@ietf.org>; Wed, 11 May 2011 13:45:17 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p4BKjAuX011753; Wed, 11 May 2011 22:45:10 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201105112045.p4BKjAuX011753@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Wed, 11 May 2011 11:20:22 PDT. <038701cc1008$1768aae0$463a00a0$@com> 
Date: Wed, 11 May 2011 22:45:10 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: xiaohong.deng@orange-ftgroup.com, pcp@ietf.org
Subject: Re: [pcp] EIM and dynamic mappings [was RE: hoping to eliminate IMPLICIT_MAPPING_EXISTS]
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 11 May 2011 20:45:19 -0000

 In your previous mail you wrote:

   I thought about this some more, and I believe EIM have no problem
   here.
   
=> I have to disagree: there is no critical issue but
you can't say there is no issue at all. I know
at least 3 contexts where EIM doesn't really help
with a implicit/explicit collision on the internal port:
 - PREFER_FAILURE
 - explicit dynamic mappings using a dedicated external port pool
 - all the cases where it is important to keep the same
  external port pool (*)

   Let's say a host sends a packet from source port 12345 to the
   Internet, which creates a mapping in their EIM NAT.  This will
   be mapped to public port "X".  
   
   The host then sends a PCP MAP4 request for internal-port=12345.
   This is also mapped to public port "X".
   
   Any traffic from the internal port 12345 is mapped to public
   port "X".  And any traffic that arrives from the Internet to
   public port "X" is mapped to the internal host's port 12345.
   
=> this means the choice of the external port is done by a race
between a packet to the Internet (**) and the MAP request.

Regards

Francis.Dupont@fdupont.fr

PS (*): this means if the explicit dynamic mappings have to be
persistent they must be restored first after a reboot. Not something
hard to implement but it can lead to longer unavailability on reboots.

PPS (**): it is less an issue for TCP if only SYN packets are allowed
to create mappings.

From xiaohong.deng@orange-ftgroup.com  Thu May 12 00:13:14 2011
Return-Path: <xiaohong.deng@orange-ftgroup.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2924CE06FB for <pcp@ietfa.amsl.com>; Thu, 12 May 2011 00:13:14 -0700 (PDT)
X-Quarantine-ID: <8-5IZfAEi+rv>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace: References: ...> <0962B0BEF842A24191AD9\n  \n\t  \t B\tE4\t1A\t\n[...]
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8-5IZfAEi+rv for <pcp@ietfa.amsl.com>; Thu, 12 May 2011 00:13:11 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by ietfa.amsl.com (Postfix) with ESMTP id DFAB5E06B3 for <pcp@ietf.org>; Thu, 12 May 2011 00:13:10 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id D0991858031; Thu, 12 May 2011 09:19:59 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id C9E34858030; Thu, 12 May 2011 09:19:59 +0200 (CEST)
Received: from ch-mailsrv.rd.francetelecom.fr ([10.193.250.27]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 12 May 2011 09:13:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 May 2011 15:13:01 +0800
Message-ID: <0962B0BEF842A24191AD9BE41A8DD2FC0175735E@ch-mailsrv.rd.francetelecom.fr>
In-Reply-To: <038701cc1008$1768aae0$463a00a0$@com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: EIM and dynamic mappings [was RE: [pcp] hoping to eliminate IMPLICIT_MAPPING_EXISTS]
Thread-Index: AcvpgbZjqATPUsFnRFan3ixj2Y8FqQAlk4zAAAdKXvAAJLt/0AAPaQzwAI5RLNAAAOWpIAAs7yOgAARenKAAt94SIAIfj1bAAtYosmAAC6vpAAAci1MgAAPZPWAAAeTygAARimagAVNyAQAACVTukAAtJnWwAKzBQvAAF43JUAALz+xAACcx+uAAC0KF0AAGXC9QABQOgSA=
References: <0cb801cbe29e$ee401b80$cac05280$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01621A9D@ch-mailsrv.rd.francetelecom.fr> <B116E08B-C28F-4FDE-855A-88DAA0B34E0D@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621DA1@ch-mailsrv.rd.francetelecom.fr> <65E8E82B-3C4A-479A-B158-76E56E96DC47@apple.com> <0962B0BEF842A24191AD9BE41A8DD2FC01621FE6@ch-mailsrv.rd.francetelecom.fr> <1e6601cbea35$abd8f5c0$038ae140$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016221BC@ch-mailsrv.rd.francetelecom.fr> <22fd01cbeb06$c4793500$4d6b9f00$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E41B@ch-mailsrv.rd.francetelecom.fr> <03e101cbed42$d80d0ef0$88272cd0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164E634@ch-mailsrv.rd.francetelecom.fr> <095601cbee08$9ef0c780$dcd25680$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0164EE47@ch-mailsrv.rd.francetelecom.fr> <0f7901cbf965$ea64aa70$bf2dff50$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED0E5@ch-mailsrv.rd.francetelecom.fr> <013001cc04ed$14550c20$3cff2460$@com> <0962B0BEF842A24191AD9 ... B	E4	1A	 8D		D2F	C01	6ED	208	@ch-mailsrv.rd.francetelecom.fr> <044a01cc056e$977c9f10$c675dd30$@com> <0962B0BEF842A24191AD9BE41A8DD2FC016ED2AE@ch-mailsrv.rd.francetelecom.fr> <05c101cc05bc$9d5d9c10$d818d430$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0172618B@ch-mailsrv.rd.francetelecom.fr> <0b9c01cc0b30$9ea57100$dbf05300$@com> <0962B0BEF842A24191AD9BE41A8DD2FC01726412@ch-mailsrv.rd.francetelecom.fr> <069001cc0e97$764f2290$62ed67b0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC017269C3@ch-mailsrv.rd.francetelecom.fr> <0b2701cc0f67$d6c73790$8455a6b0$@com> <0962B0BEF842A24191AD9BE41A8DD2FC0175717C@ch-mailsrv.rd.francetelecom.fr> <038701cc1008$1768aae0$463a00a0$@com>
From: <xiaohong.deng@orange-ftgroup.com>
To: <dwing@cisco.com>
X-OriginalArrivalTime: 12 May 2011 07:13:07.0381 (UTC) FILETIME=[0B01A650:01CC1074]
Cc: pcp@ietf.org
Subject: Re: [pcp] EIM and dynamic mappings [was RE: hoping to eliminate IMPLICIT_MAPPING_EXISTS]
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 12 May 2011 07:13:14 -0000

|
|Dan Wing wrote:
|
|> Xiaohong Deng wrote:
|> > Another question:
|> >
|> > Still, when a MAPx request does *not* contain the PREFER_FAILURE=20
|> > option if an implicit dynamic mapping exists on that requested
|> > *internal* port, how does *EIM* NAT handle that?
|>=20
|> Seems it would have to return an error or do #2 of
|>=20
|http://tools.ietf.org/html/draft-ietf-pcp-base-10#section-11.1 (which=20
|> needs its text changed to accommodate).
|
|
|
|I thought about this some more, and I believe EIM have no problem here.
|
|Let's say a host sends a packet from source port 12345 to the=20
|Internet, which creates a mapping in their EIM NAT.  This will=20
|be mapped to public port "X". =20
|
|The host then sends a PCP MAP4 request for internal-port=3D12345.
|This is also mapped to public port "X".
|
|
|Any traffic from the internal port 12345 is mapped to public=20
|port "X".  And any traffic that arrives from the Internet to=20
|public port "X" is mapped to the internal host's port 12345.

Doubt if this would always work, consider that the exist mapping=20
lifetime is short, in the case that we ran into, less than 60 seconds,=20
and it expired quickly as it's a http non-persistent.

Assume a positive response is retured to the PCP client ( is this what=20
you implied ?), but if the first incomming connection is issued
more than 60s later after a PCP client assumes the mapping created,
the mapping that the PCP client assumes as successfully created=20
would have already been deleted in this case, as there is no traffic
keep alive this mapping during that time.



|
|-d
|
|
|
|

From internet-drafts@ietf.org  Fri May 13 17:36:06 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 924ABE069E; Fri, 13 May 2011 17:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vyeR59Bpq0Vk; Fri, 13 May 2011 17:36:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1138DE067A; Fri, 13 May 2011 17:36:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.54
Message-ID: <20110514003606.32108.58740.idtracker@ietfa.amsl.com>
Date: Fri, 13 May 2011 17:36:06 -0700
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-base-11.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 May 2011 00:36:06 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Port Control Protocol Working Group o=
f the IETF.

	Title           : Port Control Protocol (PCP)
	Author(s)       : Dan Wing
                          Stuart Cheshire
                          Mohamed Boucadair
                          Reinaldo Penno
	Filename        : draft-ietf-pcp-base-11.txt
	Pages           : 66
	Date            : 2011-05-13

   Port Control Protocol allows a host to control how incoming IPv6 or
   IPv4 packets are translated and forwarded by a network address
   translator (NAT) or simple firewall to an IPv6 or IPv4 host, and also
   allows a host to optimize its NAT keepalive messages.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pcp-base-11.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-pcp-base-11.txt

From dwing@cisco.com  Fri May 13 17:38:35 2011
Return-Path: <dwing@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E0B6E06D9 for <pcp@ietfa.amsl.com>; Fri, 13 May 2011 17:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.382
X-Spam-Level: 
X-Spam-Status: No, score=-110.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JYFL4DJGkOjg for <pcp@ietfa.amsl.com>; Fri, 13 May 2011 17:38:34 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id E75FAE067A for <pcp@ietf.org>; Fri, 13 May 2011 17:38:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=270; q=dns/txt; s=iport; t=1305333514; x=1306543114; h=from:to:subject:date:message-id:mime-version: content-transfer-encoding; bh=9CmU6upmnWBnO3+yTFLuGftewmqlDjdO2CUXLK5PsdY=; b=E7pCS6+iRt8A0poYbWNnBNXmRWAtnp8THK4GFatzFXnQLe3jtBNl7x8y pD79Oec7CRRX80msJzsWvUWPwWJ5bvDNj4Mw5uL5z2GJSJLqAFNAMXAK1 8BPEeQqdF+YXDRYDxV4OHAQLp4SbP99O7WH8femR2E8ZfOD+57pYqDhSB Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUIAM7NzU2rRDoJ/2dsb2JhbACEWJM5gSSMX3elfoEdjQOQcoErg2aBBwSGUJhW
X-IronPort-AV: E=Sophos;i="4.64,367,1301875200"; d="scan'208";a="697291499"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-6.cisco.com with ESMTP; 14 May 2011 00:38:34 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p4E0cYdA013892 for <pcp@ietf.org>; Sat, 14 May 2011 00:38:34 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <pcp@ietf.org>
Date: Fri, 13 May 2011 17:38:34 -0700
Message-ID: <011701cc11cf$41b894e0$c529bea0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwRzuuRtFxbBEf6QYubMYAYvEl4NgAAAWqg
Content-Language: en-us
Subject: [pcp] draft-ietf-pcp-base-11
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 May 2011 00:38:35 -0000

After the recent thread with Xiaohong Deng, the pcp-base was updated.  

Changes:

   o  clarified what can cause CANNOT_PROVIDE_EXTERNAL_PORT error to be
      generated.

side-by-side diffs:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-pcp-base-11.txt

-d



From mohamed.boucadair@orange-ftgroup.com  Thu May 19 07:43:06 2011
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4ACE075E for <pcp@ietfa.amsl.com>; Thu, 19 May 2011 07:43:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gVfS1pGbPivT for <pcp@ietfa.amsl.com>; Thu, 19 May 2011 07:43:05 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by ietfa.amsl.com (Postfix) with ESMTP id 806F7E07C4 for <pcp@ietf.org>; Thu, 19 May 2011 07:43:05 -0700 (PDT)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id E644B1B84EF for <pcp@ietf.org>; Thu, 19 May 2011 16:43:03 +0200 (CEST)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id D065518007C for <pcp@ietf.org>; Thu, 19 May 2011 16:43:03 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Thu, 19 May 2011 16:43:03 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Date: Thu, 19 May 2011 16:43:02 +0200
Thread-Topic: PCP Extensions (draft-boucadair-pcp-extensions)
Thread-Index: AcwWHTZTCP6C0PqRQu+o2wef1GN6fQAFZRxg
Message-ID: <94C682931C08B048B7A8645303FDC9F33E4DF87913@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.5.19.141518
Subject: [pcp] PCP Extensions (draft-boucadair-pcp-extensions)
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 19 May 2011 14:43:06 -0000

Dear all,

A new I-D listing some extensions to PCP has been submitted.=20

Comments and suggestions are welcome.

Cheers,
Med

-----Message d'origine-----
De : i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] D=
e la part de internet-drafts@ietf.org
Envoy=E9 : jeudi 19 mai 2011 14:06
=C0 : i-d-announce@ietf.org
Objet : I-D Action: draft-boucadair-pcp-extensions-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.

	Title           : Some Extensions to Port Control Protocol (PCP)
	Author(s)       : Mohamed Boucadair
                          Reinaldo Penno
                          Dan Wing
	Filename        : draft-boucadair-pcp-extensions-00.txt
	Pages           : 15
	Date            : 2011-05-19

   This document extends Port Control Protocol (PCP) with some useful
   features.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-boucadair-pcp-extensions-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-boucadair-pcp-extensions-00.txt
_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

From internet-drafts@ietf.org  Fri May 20 13:10:10 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74205E07E4; Fri, 20 May 2011 13:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgzh5p5Uueyk; Fri, 20 May 2011 13:10:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 738A8E07D7; Fri, 20 May 2011 13:10:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.54
Message-ID: <20110520201004.2305.97127.idtracker@ietfa.amsl.com>
Date: Fri, 20 May 2011 13:10:04 -0700
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-base-12.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 20 May 2011 20:10:10 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Port Control Protocol Working Group o=
f the IETF.

	Title           : Port Control Protocol (PCP)
	Author(s)       : Dan Wing
                          Stuart Cheshire
                          Mohamed Boucadair
                          Reinaldo Penno
                          Paul Selkirk
	Filename        : draft-ietf-pcp-base-12.txt
	Pages           : 67
	Date            : 2011-05-20

   Port Control Protocol allows a host to control how incoming IPv6 or
   IPv4 packets are translated and forwarded by a network address
   translator (NAT) or simple firewall to an IPv6 or IPv4 host, and also
   allows a host to optimize its NAT keepalive messages.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pcp-base-12.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-pcp-base-12.txt

From dthaler@microsoft.com  Fri May 20 13:18:22 2011
Return-Path: <dthaler@microsoft.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4155E07EF for <pcp@ietfa.amsl.com>; Fri, 20 May 2011 13:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iH1KXnoXUrvj for <pcp@ietfa.amsl.com>; Fri, 20 May 2011 13:18:21 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id 43D0DE0742 for <pcp@ietf.org>; Fri, 20 May 2011 13:18:21 -0700 (PDT)
Received: from TK5EX14HUBC105.redmond.corp.microsoft.com (157.54.80.48) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 20 May 2011 13:18:14 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC105.redmond.corp.microsoft.com (157.54.80.48) with Microsoft SMTP Server (TLS) id 14.1.289.8; Fri, 20 May 2011 13:18:14 -0700
Received: from TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com ([169.254.4.118]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi id 14.01.0289.008; Fri, 20 May 2011 13:18:14 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: WGLC: draft-ietf-pcp-base-12.txt
Thread-Index: AcwXKk61FuyajK7hRbulosJtjQ9K5w==
Date: Fri, 20 May 2011 20:18:13 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B0BA0FD@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.90]
Content-Type: multipart/alternative; boundary="_000_9B57C850BB53634CACEC56EF4853FF653B0BA0FDTK5EX14MBXW604w_"
MIME-Version: 1.0
Subject: [pcp] WGLC: draft-ietf-pcp-base-12.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 20 May 2011 20:18:22 -0000

--_000_9B57C850BB53634CACEC56EF4853FF653B0BA0FDTK5EX14MBXW604w_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

This message starts a two-week WGLC on
http://www.ietf.org/internet-drafts/draft-ietf-pcp-base-12.txt

This last call will conclude on June 3rd at 5pm EST.

Please send your comments to the list.

We are scheduling a WebEx call shortly after the WGLC concludes,
and will send out details in separate email.

Thanks,
-Dave and Alain



--_000_9B57C850BB53634CACEC56EF4853FF653B0BA0FDTK5EX14MBXW604w_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">This message starts a two-week WGLC on<o:p></o:p></p=
>
<p class=3D"MsoNormal"><a href=3D"http://www.ietf.org/internet-drafts/draft=
-ietf-pcp-base-12.txt">http://www.ietf.org/internet-drafts/draft-ietf-pcp-b=
ase-12.txt</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This last call will conclude on June 3<sup>rd</sup> =
at 5pm EST.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please send your comments to the list.<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We are scheduling a WebEx call shortly after the WGL=
C concludes,<o:p></o:p></p>
<p class=3D"MsoNormal">and will send out details in separate email.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">-Dave and Alain<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9B57C850BB53634CACEC56EF4853FF653B0BA0FDTK5EX14MBXW604w_--

From tena@huawei.com  Fri May 20 17:41:18 2011
Return-Path: <tena@huawei.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43499E0740 for <pcp@ietfa.amsl.com>; Fri, 20 May 2011 17:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t+iGVEh5aovl for <pcp@ietfa.amsl.com>; Fri, 20 May 2011 17:41:17 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by ietfa.amsl.com (Postfix) with ESMTP id AB274E0728 for <pcp@ietf.org>; Fri, 20 May 2011 17:41:17 -0700 (PDT)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LLI00CYISKSNW@usaga04-in.huawei.com> for pcp@ietf.org; Fri, 20 May 2011 19:41:17 -0500 (CDT)
Received: from TingZousc1 ([10.193.34.188]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LLI00H8TSKQ3Y@usaga04-in.huawei.com> for pcp@ietf.org; Fri, 20 May 2011 19:41:16 -0500 (CDT)
Date: Fri, 20 May 2011 17:41:19 -0700
From: Tina Tsou <tena@huawei.com>
To: pcp@ietf.org
Message-id: <01a601cc174f$cdb79ec0$6926dc40$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcwXT8r6UjlRWv81Qyuvsm0TFYaujA==
X-CR-Puzzleid: {5120D9B5-41FD-43F2-8F81-1D19FACF0581}
X-CR-Hashedpuzzle: AXBj CiNC ELp6 FvFs F7YB GWGm GlOl G70B HuCb HvK+ Jmp7 KI13 K8Fb Lbqb Lv0e L/0T; 1; cABjAHAAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {5120D9B5-41FD-43F2-8F81-1D19FACF0581}; dABlAG4AYQBAAGgAdQBhAHcAZQBpAC4AYwBvAG0A; Sat, 21 May 2011 00:41:16 GMT; UABlAHIAZgBvAHIAbQBhAG4AYwBlACAAaQBzAHMAdQBlAHMAIABmAG8AcgAgAEcARQBUAC8ARwBFAFQAIABOAEUAWABUACAAaQBuACAAZAByAGEAZgB0AC0AYgBvAHUAYwBhAGQAYQBpAHIALQBwAGMAcAAtAGYAYQBpAGwAdQByAGUALQAwADEA
Subject: [pcp] Performance issues for GET/GET NEXT in draft-boucadair-pcp-failure-01
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 21 May 2011 00:41:18 -0000

Hi Med et al,
There may be some performance issues for GET/GET NEXT in
draft-boucadair-pcp-failure-01.
The client can get NAT entries from server based on some of all of the
parameters of internal IP/external IP/internal port/external port/protocol.
This kind of parameter combination may cause going through the whole NAT
entries at server side, to match one by one. If there are tens of millions
entries in CGN, that will bring a lot of computing effort.


We keep our promises with one another - no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html




From mohamed.boucadair@orange-ftgroup.com  Mon May 23 22:55:33 2011
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 587D0E06CD for <pcp@ietfa.amsl.com>; Mon, 23 May 2011 22:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2D3x0XAPDxLw for <pcp@ietfa.amsl.com>; Mon, 23 May 2011 22:55:32 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 456D5E06BC for <pcp@ietf.org>; Mon, 23 May 2011 22:55:31 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 4ED223B422F; Tue, 24 May 2011 07:55:30 +0200 (CEST)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 3721427C075; Tue, 24 May 2011 07:55:30 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Tue, 24 May 2011 07:55:30 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: Tina Tsou <tena@huawei.com>, "pcp@ietf.org" <pcp@ietf.org>
Date: Tue, 24 May 2011 07:55:28 +0200
Thread-Topic: [pcp] Performance issues for GET/GET NEXT in draft-boucadair-pcp-failure-01
Thread-Index: AcwXT8r6UjlRWv81Qyuvsm0TFYaujAChU3aQ
Message-ID: <94C682931C08B048B7A8645303FDC9F33E4E326337@PUEXCB1B.nanterre.francetelecom.fr>
References: <01a601cc174f$cdb79ec0$6926dc40$@com>
In-Reply-To: <01a601cc174f$cdb79ec0$6926dc40$@com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.5.24.11524
Subject: Re: [pcp] Performance issues for GET/GET NEXT in	draft-boucadair-pcp-failure-01
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 24 May 2011 05:55:33 -0000

Hi Tina,

GET/NEXT procedure aims to retrieve the PCP-instructed mappings from a PCP =
Server and not all the NAT entries. The amount of explicit mappings is like=
ly to be less than implicit ones.=20

We have tested a previous version of the GET procedure with a vendor and no=
 performance issues have been reported. Note, the "tens of millions" entrie=
s case has not been tested in our side because this is not our targeted con=
figuration.=20

Cheers,
Med=20

-----Message d'origine-----
De : pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] De la part de Tina =
Tsou
Envoy=E9 : samedi 21 mai 2011 02:41
=C0 : pcp@ietf.org
Objet : [pcp] Performance issues for GET/GET NEXT in draft-boucadair-pcp-fa=
ilure-01

Hi Med et al,
There may be some performance issues for GET/GET NEXT in
draft-boucadair-pcp-failure-01.
The client can get NAT entries from server based on some of all of the
parameters of internal IP/external IP/internal port/external port/protocol.
This kind of parameter combination may cause going through the whole NAT
entries at server side, to match one by one. If there are tens of millions
entries in CGN, that will bring a lot of computing effort.


We keep our promises with one another - no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html



_______________________________________________
pcp mailing list
pcp@ietf.org
https://www.ietf.org/mailman/listinfo/pcp

From mohamed.boucadair@orange-ftgroup.com  Mon May 23 23:17:50 2011
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABC01E0692 for <pcp@ietfa.amsl.com>; Mon, 23 May 2011 23:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qPY4Gw2u9Zyq for <pcp@ietfa.amsl.com>; Mon, 23 May 2011 23:17:49 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 8F6D2E0688 for <pcp@ietf.org>; Mon, 23 May 2011 23:17:49 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 5B93822C5AB; Tue, 24 May 2011 08:17:48 +0200 (CEST)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 41A80238086; Tue, 24 May 2011 08:17:48 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Tue, 24 May 2011 08:17:48 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: Simon Perreault <simon.perreault@viagenie.ca>, "draft-boucadair-pcp-rtp-rtcp@tools.ietf.org" <draft-boucadair-pcp-rtp-rtcp@tools.ietf.org>
Date: Tue, 24 May 2011 08:17:46 +0200
Thread-Topic: [pcp] MAP with PORT_RESERVATION_OPTION on existing mapping
Thread-Index: AcwE39pG1tc8yVIdR5emsDvbo0YSvgU+RBFQ
Message-ID: <94C682931C08B048B7A8645303FDC9F33E4E32633A@PUEXCB1B.nanterre.francetelecom.fr>
References: <4DB81B61.8040001@viagenie.ca>
In-Reply-To: <4DB81B61.8040001@viagenie.ca>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.5.23.184217
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] MAP with PORT_RESERVATION_OPTION on existing mapping
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 24 May 2011 06:17:50 -0000

Hi Simon,

Please see inline.

Cheers,
Med

-----Message d'origine-----
De : pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] De la part de Simon=
 Perreault
Envoy=E9 : mercredi 27 avril 2011 15:34
=C0 : draft-boucadair-pcp-rtp-rtcp@tools.ietf.org
Cc : pcp@ietf.org
Objet : [pcp] MAP with PORT_RESERVATION_OPTION on existing mapping

Hi,

How should a PCP server react when it receives a MAP request with a
PORT_RESERVATION_OPTION and it turns out that the mapping already
exists? This can happen with retransmissions, for example.

Med: You mean two mappings having N/N+1 internal port exit?

Trying to refresh both mappings seems to go against text in section 5.
("Two mappings are therefore instantiated by the PCP Server with the
same lifetime value. These mappings are treated as any individual
mapping.") It's possible that the server would have no way to find the
second mapping given the first since they're not linked.

Med: The PCP Server can rely on the internal port to detect whether a compa=
nion mapping (i.e., for N+1) exists also. The PCP Server has then to refres=
h these two mappings. No?

On the other hand, returning an error would go against the PCP design
principle of indempotence.

So I suggest that a MAP request with PORT_RESERVATION_OPTION on an
existing mapping would refresh the first mapping and return success,
just as a normal MAP request would. The second mapping would be
unmodified. It would be refreshed separately, as shown in the examples.

Simon

From simon.perreault@viagenie.ca  Wed May 25 06:25:50 2011
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 647B9E07F2 for <pcp@ietfa.amsl.com>; Wed, 25 May 2011 06:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fvfS478tnCCA for <pcp@ietfa.amsl.com>; Wed, 25 May 2011 06:25:50 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id CC6D4E06A8 for <pcp@ietf.org>; Wed, 25 May 2011 06:25:49 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:21d:60ff:fed7:e732]) by jazz.viagenie.ca (Postfix) with ESMTPSA id C263721C52; Wed, 25 May 2011 09:25:48 -0400 (EDT)
Message-ID: <4DDD035C.40307@viagenie.ca>
Date: Wed, 25 May 2011 09:25:48 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110320 Fedora/3.1.9-4.fc16 Lightning/1.0b3pre Thunderbird/3.1.9
MIME-Version: 1.0
To: mohamed.boucadair@orange-ftgroup.com
References: <4DB81B61.8040001@viagenie.ca> <94C682931C08B048B7A8645303FDC9F33E4E32633A@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F33E4E32633A@PUEXCB1B.nanterre.francetelecom.fr>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "pcp@ietf.org" <pcp@ietf.org>, "draft-boucadair-pcp-rtp-rtcp@tools.ietf.org" <draft-boucadair-pcp-rtp-rtcp@tools.ietf.org>
Subject: Re: [pcp] MAP with PORT_RESERVATION_OPTION on existing mapping
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 25 May 2011 13:25:50 -0000

On 2011-05-24 02:17, mohamed.boucadair@orange-ftgroup.com wrote:
> Med: The PCP Server can rely on the internal port to detect whether a companion mapping (i.e., for N+1) exists also. The PCP Server has then to refresh these two mappings. No?

Hmmm... Reading my original email I can't remember what the issue was.
Your explanation makes sense to me now. So feel free to consider this
issue as invalid.

Sorry for the noise.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From dthaler@microsoft.com  Fri May 27 11:59:17 2011
Return-Path: <dthaler@microsoft.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35C9AE073C for <pcp@ietfa.amsl.com>; Fri, 27 May 2011 11:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.541
X-Spam-Level: 
X-Spam-Status: No, score=-110.541 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V9WJxDnwK6pv for <pcp@ietfa.amsl.com>; Fri, 27 May 2011 11:59:16 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id E7940E073B for <pcp@ietf.org>; Fri, 27 May 2011 11:59:15 -0700 (PDT)
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (157.54.80.61) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 27 May 2011 11:59:15 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC106.redmond.corp.microsoft.com (157.54.80.61) with Microsoft SMTP Server (TLS) id 14.1.289.8; Fri, 27 May 2011 11:59:14 -0700
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.165]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.01.0289.008; Fri, 27 May 2011 11:59:14 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: Next PCP WebEx meeting
Thread-Index: Acwcn4ZYgk8e8C1xSumXczIv7qxdfQ==
Date: Fri, 27 May 2011 18:59:14 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B0DE663@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.90]
Content-Type: multipart/alternative; boundary="_000_9B57C850BB53634CACEC56EF4853FF653B0DE663TK5EX14MBXW601w_"
MIME-Version: 1.0
Subject: [pcp] Next PCP WebEx meeting
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 27 May 2011 18:59:17 -0000

--_000_9B57C850BB53634CACEC56EF4853FF653B0DE663TK5EX14MBXW601w_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhlIG5leHQgV2ViRXggbWVldGluZyBvZiB0aGUgUENQIFdHIHdpbGwgdGFrZSBwbGFjZSBvbiBU
dWVzZGF5IEp1bmUgN3RoDQphdCA3QU0tOUFNIFBhY2lmaWMgdGltZSAodGhpcyBpcyB0aGUgc2Ft
ZSB0aW1lIG9mIGRheSBhbmQgZHVyYXRpb24gYXMgcHJldmlvdXMNCldlYkV4IG1lZXRpbmdzKS4g
IENhbGwgZGV0YWlscyBhcmUgaW5jbHVkZWQgYXQgdGhlIGJvdHRvbSBvZiB0aGlzIG1lc3NhZ2Uu
DQoNClByaW9yaXR5IGdvZXMgdG8gZGlzY3Vzc2luZyBpc3N1ZXMgb24gdGhlIGJhc2Ugc3BlYyBy
YWlzZWQgZHVyaW5nIFdHTEMuDQoNCklmIHRoZXJlIGlzIGFkZGl0aW9uYWwgdGltZSwgdGhlIG5l
eHQgcHJpb3JpdHkgZ29lcyB0byB0aGUgb3RoZXIgcHJlc2VudGF0aW9ucw0KZGVmZXJyZWQgZnJv
bSB0aGUgbGFzdCBJRVRGIG1lZXRpbmcuDQoNCi1EYXZlDQoNCi0tLS0tLS0tLS0tLS0NClRvcGlj
OiBNZWV0aW5nIENlbnRlciBNUFYNCkRhdGU6IFR1ZXNkYXksIEp1bmUgNywgMjAxMQ0KVGltZTog
NzowMCBhbSwgUGFjaWZpYyBEYXlsaWdodCBUaW1lIChTYW4gRnJhbmNpc2NvLCBHTVQtMDc6MDAp
DQpNZWV0aW5nIE51bWJlcjogMjA3IDc1OCAxMDgNCk1lZXRpbmcgUGFzc3dvcmQ6IGlldGYNCg0K
DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQpUbyBqb2luIHRoZSBvbmxpbmUgbWVldGluZyAoTm93IGZyb20gbW9iaWxlIGRldmljZXMhKQ0K
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K
MS4gR28gdG8gaHR0cHM6Ly9jaXNjby53ZWJleC5jb20vY2lzY29zYWxlcy9qLnBocD9FRD0xNjU3
NTc4MTImVUlEPTAmUFc9Tk1EZGhPVE0xT0RSbSZSVD1NaU0wDQoyLiBFbnRlciB5b3VyIG5hbWUg
YW5kIGVtYWlsIGFkZHJlc3MuDQozLiBFbnRlciB0aGUgbWVldGluZyBwYXNzd29yZDogaWV0Zg0K
NC4gQ2xpY2sgIkpvaW4gTm93Ii4NCg0KVG8gdmlldyBpbiBvdGhlciB0aW1lIHpvbmVzIG9yIGxh
bmd1YWdlcywgcGxlYXNlIGNsaWNrIHRoZSBsaW5rOg0KaHR0cHM6Ly9jaXNjby53ZWJleC5jb20v
Y2lzY29zYWxlcy9qLnBocD9FRD0xNjU3NTc4MTImVUlEPTAmUFc9Tk1EZGhPVE0xT0RSbSZPUlQ9
TWlNMA0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tDQpBTEVSVDpUb2xsLUZyZWUgRGlhbCBSZXN0cmljdGlvbnMgZm9yICg0
MDgpIGFuZCAoOTE5KSBBcmVhIENvZGVzDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNClRoZSBhZmZlY3RlZCB0b2xsIGZy
ZWUgbnVtYmVycyBhcmU6ICg4NjYpIDQzMi05OTAzIGZvciB0aGUgU2FuIEpvc2UvTWlscGl0YXMg
YXJlYSBhbmQgKDg2NikgMzQ5LTM1MjAgZm9yIHRoZSBSVFAgYXJlYS4NCg0KUGxlYXNlIGRpYWwg
dGhlIGxvY2FsIGFjY2VzcyBudW1iZXIgZm9yIHlvdXIgYXJlYSBmcm9tIHRoZSBsaXN0IGJlbG93
Og0KLSBTYW4gSm9zZS9NaWxwaXRhcyAoNDA4KSBhcmVhOiA1MjUtNjgwMA0KLSBSVFAgKDkxOSkg
YXJlYTogMzkyLTMzMzANCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KVG8gam9pbiB0aGUgdGVsZWNvbmZlcmVuY2Ugb25seQ0KLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KMS4gRGlh
bCBpbnRvIENpc2NvIFdlYkV4ICh2aWV3IGFsbCBHbG9iYWwgQWNjZXNzIE51bWJlcnMgYXQNCmh0
dHA6Ly9jaXNjby5jb20vZW4vVVMvYWJvdXQvZG9pbmdfYnVzaW5lc3MvY29uZmVyZW5jaW5nL2lu
ZGV4Lmh0bWwNCjIuIEZvbGxvdyB0aGUgcHJvbXB0cyB0byBlbnRlciB0aGUgTWVldGluZyBOdW1i
ZXIgKGxpc3RlZCBhYm92ZSkgb3IgQWNjZXNzIENvZGUgZm9sbG93ZWQgYnkgdGhlICMgc2lnbi4N
Cg0KU2FuIEpvc2UsIENBOiArMS40MDguNTI1LjY4MDAgUlRQOiArMS45MTkuMzkyLjMzMzANCg0K
VVMvQ2FuYWRhOiArMS44NjYuNDMyLjk5MDMgVW5pdGVkIEtpbmdkb206ICs0NC4yMC44ODI0LjAx
MTcNCg0KSW5kaWE6ICs5MS44MC40MzUwLjExMTEgR2VybWFueTogKzQ5LjYxOS42NzczLjkwMDIN
Cg0KSmFwYW46ICs4MS4zLjU3NjMuOTM5NCBDaGluYTogKzg2LjEwLjg1MTUuNTY2Ng0KDQotLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpGb3Ig
YXNzaXN0YW5jZQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KMS4gR28gdG8gaHR0cHM6Ly9jaXNjby53ZWJleC5jb20vY2lzY29zYWxlcy9t
Yw0KMi4gT24gdGhlIGxlZnQgbmF2aWdhdGlvbiBiYXIsIGNsaWNrICJTdXBwb3J0Ii4NCg0KWW91
IGNhbiBjb250YWN0IG1lIGF0Og0KZHdpbmdAY2lzY28uY29tPG1haWx0bzpkd2luZ0BjaXNjby5j
b20+DQoxLTQwOC04NTMgNDE5Nw0KDQpUbyBhZGQgdGhpcyBtZWV0aW5nIHRvIHlvdXIgY2FsZW5k
YXIgcHJvZ3JhbSAoZm9yIGV4YW1wbGUgTWljcm9zb2Z0IE91dGxvb2spLCBjbGljayB0aGlzIGxp
bms6DQpodHRwczovL2Npc2NvLndlYmV4LmNvbS9jaXNjb3NhbGVzL2oucGhwP0VEPTE2NTc1Nzgx
MiZVSUQ9MCZJQ1M9TUkmTEQ9MSZSRD0yJlNUPTEmU0hBMj1NUkQ4UmIwS2xIa2tOZWF2QTFrL0Q5
UGgxcjBPSTg1QVNDS2thalZKR0hrPSZSVD1NaU0wDQoNClRoZSBwbGF5YmFjayBvZiBVQ0YgKFVu
aXZlcnNhbCBDb21tdW5pY2F0aW9ucyBGb3JtYXQpIHJpY2ggbWVkaWEgZmlsZXMgcmVxdWlyZXMg
YXBwcm9wcmlhdGUgcGxheWVycy4gVG8gdmlldyB0aGlzIHR5cGUgb2YgcmljaCBtZWRpYSBmaWxl
cyBpbiB0aGUgbWVldGluZywgcGxlYXNlIGNoZWNrIHdoZXRoZXIgeW91IGhhdmUgdGhlIHBsYXll
cnMgaW5zdGFsbGVkIG9uIHlvdXIgY29tcHV0ZXIgYnkgZ29pbmcgdG8gaHR0cHM6Ly9jaXNjby53
ZWJleC5jb20vY2lzY29zYWxlcy9zeXN0ZW1kaWFnbm9zaXMucGhwDQoNClNpZ24gdXAgZm9yIGEg
ZnJlZSB0cmlhbCBvZiBXZWJFeA0KaHR0cDovL3d3dy53ZWJleC5jb20vZ28vbWNlbWZyZWV0cmlh
bA0KDQpodHRwOi8vd3d3LndlYmV4LmNvbQ0KDQpDQ1A6KzE0MDg1MjU2ODAweDIwNzc1ODEwOCMN
Cg0KSU1QT1JUQU5UIE5PVElDRTogVGhpcyBXZWJFeCBzZXJ2aWNlIGluY2x1ZGVzIGEgZmVhdHVy
ZSB0aGF0IGFsbG93cyBhdWRpbyBhbmQgYW55IGRvY3VtZW50cyBhbmQgb3RoZXIgbWF0ZXJpYWxz
IGV4Y2hhbmdlZCBvciB2aWV3ZWQgZHVyaW5nIHRoZSBzZXNzaW9uIHRvIGJlIHJlY29yZGVkLiBC
eSBqb2luaW5nIHRoaXMgc2Vzc2lvbiwgeW91IGF1dG9tYXRpY2FsbHkgY29uc2VudCB0byBzdWNo
IHJlY29yZGluZ3MuIElmIHlvdSBkbyBub3QgY29uc2VudCB0byB0aGUgcmVjb3JkaW5nLCBkaXNj
dXNzIHlvdXIgY29uY2VybnMgd2l0aCB0aGUgbWVldGluZyBob3N0IHByaW9yIHRvIHRoZSBzdGFy
dCBvZiB0aGUgcmVjb3JkaW5nIG9yIGRvIG5vdCBqb2luIHRoZSBzZXNzaW9uLiBQbGVhc2Ugbm90
ZSB0aGF0IGFueSBzdWNoIHJlY29yZGluZ3MgbWF5IGJlIHN1YmplY3QgdG8gZGlzY292ZXJ5IGlu
IHRoZSBldmVudCBvZiBsaXRpZ2F0aW9uLg0K

--_000_9B57C850BB53634CACEC56EF4853FF653B0DE663TK5EX14MBXW601w_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAx
LjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24x
O30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRz
IHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtp
ZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1h
cCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRp
Zl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVy
cGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5UaGUgbmV4dCBXZWJFeCBt
ZWV0aW5nIG9mIHRoZSBQQ1AgV0cgd2lsbCB0YWtlIHBsYWNlIG9uIFR1ZXNkYXkgSnVuZSA3PHN1
cD50aDwvc3VwPg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+YXQgN0FNLTlBTSBQYWNp
ZmljIHRpbWUgKHRoaXMgaXMgdGhlIHNhbWUgdGltZSBvZiBkYXkgYW5kIGR1cmF0aW9uIGFzIHBy
ZXZpb3VzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+V2ViRXggbWVldGluZ3MpLiZuYnNw
OyBDYWxsIGRldGFpbHMgYXJlIGluY2x1ZGVkIGF0IHRoZSBib3R0b20gb2YgdGhpcyBtZXNzYWdl
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPlByaW9yaXR5IGdvZXMgdG8gZGlzY3Vzc2luZyBpc3N1ZXMgb24gdGhlIGJhc2Ug
c3BlYyByYWlzZWQgZHVyaW5nIFdHTEMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SWYgdGhlcmUgaXMgYWRkaXRpb25hbCB0
aW1lLCB0aGUgbmV4dCBwcmlvcml0eSBnb2VzIHRvIHRoZSBvdGhlciBwcmVzZW50YXRpb25zPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+ZGVmZXJyZWQgZnJvbSB0aGUgbGFzdCBJRVRGIG1l
ZXRpbmcuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+LURhdmU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJyPg0KPHNwYW4gc3R5bGU9ImNv
bG9yOiMxRjQ5N0QiPi0tLS0tLS0tLS0tLS08L3NwYW4+PGJyPg0KVG9waWM6IE1lZXRpbmcgQ2Vu
dGVyIE1QViA8YnI+DQpEYXRlOiBUdWVzZGF5LCBKdW5lIDcsIDIwMTEgPGJyPg0KVGltZTogNzow
MCBhbSwgUGFjaWZpYyBEYXlsaWdodCBUaW1lIChTYW4gRnJhbmNpc2NvLCBHTVQtMDc6MDApIDxi
cj4NCk1lZXRpbmcgTnVtYmVyOiAyMDcgNzU4IDEwOCA8YnI+DQpNZWV0aW5nIFBhc3N3b3JkOiBp
ZXRmIDxicj4NCjxicj4NCjxicj4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0gPGJyPg0KVG8gam9pbiB0aGUgb25saW5lIG1lZXRpbmcgKE5v
dyBmcm9tIG1vYmlsZSBkZXZpY2VzISkgPGJyPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSA8YnI+DQoxLiBHbyB0byA8YSBocmVmPSJodHRw
czovL2Npc2NvLndlYmV4LmNvbS9jaXNjb3NhbGVzL2oucGhwP0VEPTE2NTc1NzgxMiZhbXA7VUlE
PTAmYW1wO1BXPU5NRGRoT1RNMU9EUm0mYW1wO1JUPU1pTTAiIHRhcmdldD0iX2JsYW5rIj4NCmh0
dHBzOi8vY2lzY28ud2ViZXguY29tL2Npc2Nvc2FsZXMvai5waHA/RUQ9MTY1NzU3ODEyJmFtcDtV
SUQ9MCZhbXA7UFc9Tk1EZGhPVE0xT0RSbSZhbXA7UlQ9TWlNMDwvYT4NCjxicj4NCjIuIEVudGVy
IHlvdXIgbmFtZSBhbmQgZW1haWwgYWRkcmVzcy4gPGJyPg0KMy4gRW50ZXIgdGhlIG1lZXRpbmcg
cGFzc3dvcmQ6IGlldGYgPGJyPg0KNC4gQ2xpY2sgJnF1b3Q7Sm9pbiBOb3cmcXVvdDsuIDxicj4N
Cjxicj4NClRvIHZpZXcgaW4gb3RoZXIgdGltZSB6b25lcyBvciBsYW5ndWFnZXMsIHBsZWFzZSBj
bGljayB0aGUgbGluazogPGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly9jaXNjby53ZWJleC5jb20vY2lz
Y29zYWxlcy9qLnBocD9FRD0xNjU3NTc4MTImYW1wO1VJRD0wJmFtcDtQVz1OTURkaE9UTTFPRFJt
JmFtcDtPUlQ9TWlNMCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vY2lzY28ud2ViZXguY29tL2Np
c2Nvc2FsZXMvai5waHA/RUQ9MTY1NzU3ODEyJmFtcDtVSUQ9MCZhbXA7UFc9Tk1EZGhPVE0xT0RS
bSZhbXA7T1JUPU1pTTA8L2E+DQo8YnI+DQo8YnI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIDxicj4NCkFMRVJUOlRvbGwt
RnJlZSBEaWFsIFJlc3RyaWN0aW9ucyBmb3IgKDQwOCkgYW5kICg5MTkpIEFyZWEgQ29kZXMgPGJy
Pg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLSA8YnI+DQo8YnI+DQpUaGUgYWZmZWN0ZWQgdG9sbCBmcmVlIG51bWJlcnMgYXJl
OiAoODY2KSA0MzItOTkwMyBmb3IgdGhlIFNhbiBKb3NlL01pbHBpdGFzIGFyZWEgYW5kICg4NjYp
IDM0OS0zNTIwIGZvciB0aGUgUlRQIGFyZWEuDQo8YnI+DQo8YnI+DQpQbGVhc2UgZGlhbCB0aGUg
bG9jYWwgYWNjZXNzIG51bWJlciBmb3IgeW91ciBhcmVhIGZyb20gdGhlIGxpc3QgYmVsb3c6IDxi
cj4NCi0gU2FuIEpvc2UvTWlscGl0YXMgKDQwOCkgYXJlYTogNTI1LTY4MDAgPGJyPg0KLSBSVFAg
KDkxOSkgYXJlYTogMzkyLTMzMzAgPGJyPg0KPGJyPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSA8YnI+DQpUbyBqb2luIHRoZSB0ZWxlY29u
ZmVyZW5jZSBvbmx5IDxicj4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0gPGJyPg0KMS4gRGlhbCBpbnRvIENpc2NvIFdlYkV4ICh2aWV3IGFs
bCBHbG9iYWwgQWNjZXNzIE51bWJlcnMgYXQgPGJyPg0KPGEgaHJlZj0iaHR0cDovL2Npc2NvLmNv
bS9lbi9VUy9hYm91dC9kb2luZ19idXNpbmVzcy9jb25mZXJlbmNpbmcvaW5kZXguaHRtbCIgdGFy
Z2V0PSJfYmxhbmsiPmh0dHA6Ly9jaXNjby5jb20vZW4vVVMvYWJvdXQvZG9pbmdfYnVzaW5lc3Mv
Y29uZmVyZW5jaW5nL2luZGV4Lmh0bWw8L2E+DQo8YnI+DQoyLiBGb2xsb3cgdGhlIHByb21wdHMg
dG8gZW50ZXIgdGhlIE1lZXRpbmcgTnVtYmVyIChsaXN0ZWQgYWJvdmUpIG9yIEFjY2VzcyBDb2Rl
IGZvbGxvd2VkIGJ5IHRoZSAjIHNpZ24uDQo8YnI+DQo8YnI+DQpTYW4gSm9zZSwgQ0E6ICYjNDM7
MS40MDguNTI1LjY4MDAgUlRQOiAmIzQzOzEuOTE5LjM5Mi4zMzMwIDxicj4NCjxicj4NClVTL0Nh
bmFkYTogJiM0MzsxLjg2Ni40MzIuOTkwMyBVbml0ZWQgS2luZ2RvbTogJiM0Mzs0NC4yMC44ODI0
LjAxMTcgPGJyPg0KPGJyPg0KSW5kaWE6ICYjNDM7OTEuODAuNDM1MC4xMTExIEdlcm1hbnk6ICYj
NDM7NDkuNjE5LjY3NzMuOTAwMiA8YnI+DQo8YnI+DQpKYXBhbjogJiM0Mzs4MS4zLjU3NjMuOTM5
NCBDaGluYTogJiM0Mzs4Ni4xMC44NTE1LjU2NjYgPGJyPg0KPGJyPg0KLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSA8YnI+DQpGb3IgYXNzaXN0
YW5jZSA8YnI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tIDxicj4NCjEuIEdvIHRvIDxhIGhyZWY9Imh0dHBzOi8vY2lzY28ud2ViZXguY29t
L2Npc2Nvc2FsZXMvbWMiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL2Npc2NvLndlYmV4LmNvbS9j
aXNjb3NhbGVzL21jPC9hPg0KPGJyPg0KMi4gT24gdGhlIGxlZnQgbmF2aWdhdGlvbiBiYXIsIGNs
aWNrICZxdW90O1N1cHBvcnQmcXVvdDsuIDxicj4NCjxicj4NCllvdSBjYW4gY29udGFjdCBtZSBh
dDogPGJyPg0KPGEgaHJlZj0ibWFpbHRvOmR3aW5nQGNpc2NvLmNvbSI+ZHdpbmdAY2lzY28uY29t
PC9hPiA8YnI+DQoxLTQwOC04NTMgNDE5NyA8YnI+DQo8YnI+DQpUbyBhZGQgdGhpcyBtZWV0aW5n
IHRvIHlvdXIgY2FsZW5kYXIgcHJvZ3JhbSAoZm9yIGV4YW1wbGUgTWljcm9zb2Z0IE91dGxvb2sp
LCBjbGljayB0aGlzIGxpbms6DQo8YnI+DQo8YSBocmVmPSJodHRwczovL2Npc2NvLndlYmV4LmNv
bS9jaXNjb3NhbGVzL2oucGhwP0VEPTE2NTc1NzgxMiZhbXA7VUlEPTAmYW1wO0lDUz1NSSZhbXA7
TEQ9MSZhbXA7UkQ9MiZhbXA7U1Q9MSZhbXA7U0hBMj1NUkQ4UmIwS2xIa2tOZWF2QTFrL0Q5UGgx
cjBPSTg1QVNDS2thalZKR0hrPSZhbXA7UlQ9TWlNMCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8v
Y2lzY28ud2ViZXguY29tL2Npc2Nvc2FsZXMvai5waHA/RUQ9MTY1NzU3ODEyJmFtcDtVSUQ9MCZh
bXA7SUNTPU1JJmFtcDtMRD0xJmFtcDtSRD0yJmFtcDtTVD0xJmFtcDtTSEEyPU1SRDhSYjBLbEhr
a05lYXZBMWsvRDlQaDFyME9JODVBU0NLa2FqVkpHSGs9JmFtcDtSVD1NaU0wPC9hPg0KPGJyPg0K
PGJyPg0KVGhlIHBsYXliYWNrIG9mIFVDRiAoVW5pdmVyc2FsIENvbW11bmljYXRpb25zIEZvcm1h
dCkgcmljaCBtZWRpYSBmaWxlcyByZXF1aXJlcyBhcHByb3ByaWF0ZSBwbGF5ZXJzLiBUbyB2aWV3
IHRoaXMgdHlwZSBvZiByaWNoIG1lZGlhIGZpbGVzIGluIHRoZSBtZWV0aW5nLCBwbGVhc2UgY2hl
Y2sgd2hldGhlciB5b3UgaGF2ZSB0aGUgcGxheWVycyBpbnN0YWxsZWQgb24geW91ciBjb21wdXRl
ciBieSBnb2luZyB0bw0KPGEgaHJlZj0iaHR0cHM6Ly9jaXNjby53ZWJleC5jb20vY2lzY29zYWxl
cy9zeXN0ZW1kaWFnbm9zaXMucGhwIiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwczovL2Npc2NvLndl
YmV4LmNvbS9jaXNjb3NhbGVzL3N5c3RlbWRpYWdub3Npcy5waHA8L2E+IDxicj4NCjxicj4NClNp
Z24gdXAgZm9yIGEgZnJlZSB0cmlhbCBvZiBXZWJFeCA8YnI+DQo8YSBocmVmPSJodHRwOi8vd3d3
LndlYmV4LmNvbS9nby9tY2VtZnJlZXRyaWFsIiB0YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3dy53
ZWJleC5jb20vZ28vbWNlbWZyZWV0cmlhbDwvYT4NCjxicj4NCjxicj4NCjxhIGhyZWY9Imh0dHA6
Ly93d3cud2ViZXguY29tIiB0YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3dy53ZWJleC5jb208L2E+
IDxicj4NCjxicj4NCkNDUDomIzQzOzE0MDg1MjU2ODAweDIwNzc1ODEwOCMgPGJyPg0KPGJyPg0K
SU1QT1JUQU5UIE5PVElDRTogVGhpcyBXZWJFeCBzZXJ2aWNlIGluY2x1ZGVzIGEgZmVhdHVyZSB0
aGF0IGFsbG93cyBhdWRpbyBhbmQgYW55IGRvY3VtZW50cyBhbmQgb3RoZXIgbWF0ZXJpYWxzIGV4
Y2hhbmdlZCBvciB2aWV3ZWQgZHVyaW5nIHRoZSBzZXNzaW9uIHRvIGJlIHJlY29yZGVkLiBCeSBq
b2luaW5nIHRoaXMgc2Vzc2lvbiwgeW91IGF1dG9tYXRpY2FsbHkgY29uc2VudCB0byBzdWNoIHJl
Y29yZGluZ3MuIElmIHlvdSBkbyBub3QgY29uc2VudA0KIHRvIHRoZSByZWNvcmRpbmcsIGRpc2N1
c3MgeW91ciBjb25jZXJucyB3aXRoIHRoZSBtZWV0aW5nIGhvc3QgcHJpb3IgdG8gdGhlIHN0YXJ0
IG9mIHRoZSByZWNvcmRpbmcgb3IgZG8gbm90IGpvaW4gdGhlIHNlc3Npb24uIFBsZWFzZSBub3Rl
IHRoYXQgYW55IHN1Y2ggcmVjb3JkaW5ncyBtYXkgYmUgc3ViamVjdCB0byBkaXNjb3ZlcnkgaW4g
dGhlIGV2ZW50IG9mIGxpdGlnYXRpb24uDQo8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_9B57C850BB53634CACEC56EF4853FF653B0DE663TK5EX14MBXW601w_--

From pselkirk@isc.org  Mon May 30 21:26:21 2011
Return-Path: <pselkirk@isc.org>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 039E3E0769 for <pcp@ietfa.amsl.com>; Mon, 30 May 2011 21:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.36
X-Spam-Level: 
X-Spam-Status: No, score=-3.36 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, NO_RELAYS=-0.001, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L3oJigOsmB-P for <pcp@ietfa.amsl.com>; Mon, 30 May 2011 21:26:18 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 72EF2E076D for <pcp@ietf.org>; Mon, 30 May 2011 21:26:14 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 688E2C94B5 for <pcp@ietf.org>; Tue, 31 May 2011 04:26:06 +0000 (UTC) (envelope-from pselkirk@isc.org)
Received: by bikeshed.isc.org (Postfix, from userid 10300) id 54EA9216C7B; Tue, 31 May 2011 04:26:06 +0000 (UTC)
From: Paul Selkirk <pselkirk@isc.org>
To: pcp@ietf.org
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF653B0BA0FD@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> (message from Dave Thaler on Fri, 20 May 2011 20:18:13 +0000)
References: <9B57C850BB53634CACEC56EF4853FF653B0BA0FD@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 31 May 2011 04:26:06 +0000
Message-ID: <s1vmxi35wdd.fsf@bikeshed.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 31 May 2011 04:26:21 -0000

I'm sorry this review is so long; I didn't have time to write a shorter one.

I also apologize if this touches on issues that are being or have been
hashed out on the mailing list; I'm way behind on WG mail.

There are a few places where I have issues with how the protocol
actually works, a few clear (but easily cleared) errors in the
current draft (marked with "!!"), and a lot of editorial nits.

For the errors and nits, I'd be willing to make the necessary changes
myself, if Dan can give me the document source (since I seem to be
listed as a co-author now).

----------------
Policy issues:

- I'm not happy with the way PEER has evolved, to where it can create
mappings.  It's heading in the direction of making MAP a special case
of PEER (with remote port=0, remote peer=0 as wildcards).  I also don't
think the 7.3 use case is compelling enough to justify the added
complexity in the protocol (or even the suggested added complexity in
the client).

- I don't like the PCP Client's IP Address field.  I don't think it adds
sufficient value to be worth spending 16 bytes in every packet, plus
additional processing time.  I would support moving it to an Option, or
at least making it an optional field - e.g. if it's sent as all-zeroes
in the request, the server MUST process the request, and MAY either fill
it in, or leave it zeroed.  The change log says "This addition was
consensus at IETF80", but that doesn't match my notes of the meeting -
it was discussed as a possible approach to a possible problem, but no
sense of the meeting was ever asked.

- UNAUTH_THIRD_PARTY_INTERNAL_ADDRESS could be removed, and replaced
with NOT_AUTHORIZED (more on that inline).

- There is no discussion about levels of conformance.  There's some
discussion about particular options being optional (e.g. THIRD_PARTY
not supported in certain deployment scenarios), but no overall
statement of what features must be supported by all conformant
implementations.  e.g. If I had a small embedded server that supported
MAP opcodes but not PEER, would it be conformant?

----------------
General nits:

Normalize capitalization in all instances of "OpCode" and "Option".
(8 instances of "opcode", 5 instance of "Opcode", 76 instances of
"option").

Normalize capitalization of things like Internal Port and Remote Peer
Port (didn't count them).

Change "error code" to "result code" (5 instances).

Possibly use "NAT" as accepted vernacular throughout, even when
referring to NAPT, unless there's some clear distinction to be made by
referring to NAPT.

There are many places where the text has unnecessary embedded
definitions of implicit and/or explicit mappings:
7.4, 8.6 (twice), 11.1, 12.2, 13, 13.1, 13.2.

----------------
Line-by-line review:

1.  Introduction

   PCP is primarily designed to be implemented in
   the context of both Carrier-Grade NATs (CGN) and small NATs (e.g.,
   residential NATs).

Remove "primarily" - what other kind of NATs are there?

   PCP allows hosts to operate server for a long
   time (e.g., a webcam) or a short time (e.g., while playing a game or
   on a phone call)

A webcam could be long or short term, ditto a game or phone call.
Even the client may not be able to predict how long a mapping may be
needed.  It's immaterial to the protocol.

2.1.  Deployment Scenarios

   PCP can be used in various deployment scenarios, including:
   ...

Make this a real bulleted list, rather than a long bulleted sentence.
Also reorder to group them as current and emerging scenarios, e.g.

   PCP can be used in various deployment scenarios, including:

   o  Basic NAT [RFC3022]

   o  Network Address and Port Translation (NAPT) [RFC3022], such as
      commonly deployed in residential NAT devices

   o  Carrier-Grade NAT [I-D.ietf-behave-lsn-requirements]

   o  Dual-Stack Lite (DS-Lite) [I-D.ietf-softwire-dual-stack-lite]

   o  Layer-2 aware NAT [I-D.miles-behave-l2nat] and Dual-Stack Extra
      Lite [I-D.arkko-dual-stack-extra-lite]

   o  NAT64, both Stateful [RFC6146] and Stateless [RFC6145]

   o  IPv4 and IPv6 simple firewall control [RFC6092]

2.3.  Single-homed Customer Premises Network

   The PCP machinery assumes a single-homed host model.

"machinery" is an odd word
s/The PCP machinery/PCP/

   This
   restriction exists because otherwise there would need to be one PCP
   server for each egress, because the host could not reliably determine
   which egress path packets would take, so the client would need to be
   able to reliably make the same internal/external mapping in every NAT
   gateway, which in general is not possible (because the other NATs
   would likely have the necessary port mapped to another host).

run-on sentence

3.  Terminology

Add "PCP-controlled device" = NAT or firewall

   PCP Client:
      A PCP Client can issue PCP request on behalf of a third

s/request/requests/

      An interworking
      function from Universal Plug and Play Internet Gateway Device
      (UPnP IGD, [IGD]) to PCP is another example of a PCP Client.

Capitalize "interworking function"

   Interworking Function:
      a functional element responsible for interworking another protocol
      with PCP.  For example interworking between UPnP IGD [IGD] with
      PCP.

Capitalize "a"

Also, define "interworking"; maybe something like
      A functional element responsible for translating another protocol
      to PCP.

   subscriber:
      an entity provided access to the network.  In the case of a
      commercial ISP, this is typically a single home.

Capitalize "subscriber", "an"

   5-tuple  The 5 pieces of information that fully identify a flow, from
      the perspective of a subscriber: source IP address, destination IP

Line break before "The"

Also, change "subscriber" to "internal host" or "PCP client" for
consistency.

4.  Relationship between PCP Server and its NAT/firewall

   The PCP server receives PCP requests.  The PCP server might be
   integrated within the NAT or firewall device (as shown in Figure 1)
   which is expected to be a common deployment.

   It is also possible to operate the PCP server in a separate device
   from the NAT, so long as such operation is indistinguishable from the
   PCP client's perspective.

This is completely redundant to the Terminology entry.
In this case, I'd radically trim the terminology section, e.g.

   PCP Server:
      A network element which receives and processes PCP requests from a
      PCP client.  Generally this is a PCP-capable NAT gateway or
      firewall.

5.1.  Request Header

   OpCode:  Opcodes are defined in Section 8 and Section 9.

This seems like it needs something more.

   Requested Lifetime:  The Requested Lifetime field is an unsigned 32-
      bit integer, in seconds, ranging from 0 to 4,294,967,295 seconds.

s/The Requested Lifetime field is //

   PCP Client's IP Address:  The IP address of the PCP client, from the
      PCP client's perspective.  If IPv4, only the first 32 bits are
      used, the other bits MUST be set to 0.

This needs a little explanation, e.g. "If the enclosing IP packet is
IPv4, only the first 32 bits are used; the other bits MUST be sent as
0 and MUST be ignore when received."

This is discussed/explained/rationalized in 6.2, but as "PCP Client IP
Address" (no apostrophe s).

It must be optional - if it's all zeroes, the server will not reject
the packet, and will either send back its idea of the client's IP
address, or leave it zero'd.

Also normalize capitalization: "address" is lowercase in both of the
packet diagrams.

5.2.  Response Header

   Lifetime:  The Lifetime field is an unsigned 32-bit integer, in
      seconds, ranging from 0 to 4,294,967,295 seconds.

s/The Lifetime field is //

   Epoch:  The server's Epoch value.  See Section 6.5 for discussion.
      This value is set in both success and error responses.

This needs a concise description here, e.g. "seconds since start of
epoch".

5.3.  Options

   A PCP OpCode can be extended with an Option.

PCP packets can be extended with Options. (i.e. one or more)

   A given Option MAY be included in a request containing a specific
   OpCode.  The handling of an Option by the PCP client and PCP server
   MUST be specified in an appropriate document and MUST include whether
   the PCP Option can appear (one or more times) in a request and/or
   response, and indicate the contents of the Option in the request and
   in the response.  If several Options are included in a PCP request or
   response, they MAY be encoded in any order by the PCP client and are
   processed in the order received.

rewrite as
   The handling of an Option by the PCP client and PCP server MUST be
   specified in an appropriate document, which MUST include whether
   the PCP Option can appear in a request and/or response, whether it
   can appear more than once, and indicate what sort of Option data it
   conveys.  If several Options are included in a PCP request, they
   MAY be encoded in any order by the PCP client, but MUST be
   processed by the PCP server in the order in which they appear.

(The original wording of the last sentence was contradicted by the
next paragraph: "The response MUST encode the Options in the same
order".)

Actually, the whole paragraph is redundant to later text describing
what an Option definition must include.

   The response MUST encode the Options in the same order,
   but may omit some PCP Options in the response, as is necessary to
   indicate the PCP server does not understand that Option or that

s/may/MAY/
s/as is necessary //

   If the "O" bit (high bit) in the OpCode is clear,

   o  the PCP server MUST only generate a positive PCP response if it
      can successfully process the PCP request and this Option.

   o  if the PCP server does not implement this Option, or cannot
      perform the function indicated by this Option (e.g., due to a
      parsing error with the option), it MUST generate a failure
      response with code UNSUPP_OPTION or MALFORMED_OPTION (as
      appropriate) and include the UNPROCESSED option in the response
      (Section 6.7.1).

Remove the first bullet, make one sentence, change "failure response"
to "error response":

If the "O" bit (high bit) in the OpCode is clear, the PCP server MUST
process this Option.  If the PCP server does not implement this
Option, or cannot perform the function indicated by this Option (e.g.,
due to a parsing error with the option), it MUST generate an error
response with result code UNSUPP_OPTION or MALFORMED_OPTION (as
appropriate), and include the UNPROCESSED option in the response
(Section 6.7.1).

PREFER_FAILURE and FILTER do not include "purpose", but include
non-boilerplate "is included in responses".

Option boilerplate fields should start with a capital letter, e.g.
         Name: <mnemonic>
         Number: <value>
         Purpose: <textual description>
         Valid for OpCodes: <list of OpCodes>
         Length: <rules for length>
         May appear in: <requests/responses/both>
         Maximum occurrences: <count>

5.4.  Result Codes

   The following result codes may be returned as a result of any OpCode
   received by the PCP server.  The only success result code is 0, other
   values indicate an error.  If a PCP server has encountered multiple
   errors during processing of a request, it SHOULD use the most
   specific error message.

s/0,/0;/
s/has encountered/encounters/

   4  UNSUPP_OPTION, unsupported Option.  This error only occurs if the
      Option is in the mandatory-to-process range.

i.e. the "O" bit is clear

6.  General PCP Operation

   The order of operation is that a PCP client generates
   and sends a request to the PCP server, which processes the request
   and generates a response back to the PCP client.

Is it really necessary to say this?  Or is it saying something
normative, like this is a lock-step protocol with no request batching
or pipelining?  In any case, it doesn't belong in the same paragraph
as the discussion of idempotency.

6.1.  General PCP Client: Generating a Request

I'd still like to see this broken out into separate sections on server
discovery, retransmission timers, and server failover.

   The PCP client sends a PCP message the first
   server in its list of PCP servers.

s/message/request to/

It should be stated that there should be only one NAT on each
interface, and the purpose of having multiple server addresses is to
have multiple ways to contact *one* server.  e.g. A PCP server
controlling a DS-Lite AFTR may be reachable by one or more IPv6
addresses, and may also be reachable by IPv4 encapsulated in IPv6.

6.2.  General PCP Server: Processing a Request

   If the source IP address of the received packet does not match the
   contents of the PCP Client IP Address field, a response is generated
   with the ADDRESS_MISMATCH result code.  This is done to detect and
   prevent accidental use of PCP where a non-PCP-aware NAT or NAPT
   exists between the PCP client and PCP server.

s/PCP Client IP Address/PCP Client's IP Address/

!! ADDRESS_MISMATCH is not defined anywhere (should be in 5.4).

   Error responses have the same packet layout as success responses,
   with fields from the request copied into the response, and fields
   assigned by the PCP server are set as indicated in Figure 3

period.

6.3.  General PCP Client: Processing a Response

   If the result code is SERVER_OVERLOADED, clients SHOULD NOT send
   *any* further requests to that PCP server for the indicated error
   lifetime.

s/clients/the PCP client/

   For other error result codes, The PCP client SHOULD NOT
   resend the same request for the indicated error lifetime.

s/The/the/

   If a PCP
   server indicates an error lifetime in excess of 30 minutes, A PCP
   client MAY choose to set its retry timer to 30 minutes.

s/A/a/

   If the PCP client has discovered a new PCP server (e.g., connected to
   a new network), the PCP client MAY immediately begin communicating
   with this PCP server, without regard to hold times from communicating
   with a previous PCP server.

(See section 6.1.)

6.5.  Epoch

   When a client notices that the PCP server reduced its Epoch value,
   the PCP clients will send PCP requests to refresh their mappings.

This is redundant to the immediately preceding sentence.

6.6.  Version Negotiation

   When sending a response containing the UNSUPP_VERSION result code,
   the PCP message MUST be 12 octets long.

i.e. no PCP Client's IP Address or Opcode section - Is this really
what you meant, or was this not updated when PCP Client's IP Address
was added?

I think this restriction is a mistake, and the response should follow
normal guidelines, e.g. copy the whole request into the response.
This restriction was added in -08 with no explanation in the change log.

6.7.1.  UNPROCESSED Option

   If
   a certain Option appeared more than once in the PCP request, that
   Option value can appear once or as many times as it occurred in the
   request.

This was also changed in -08, was "If a certain Option appeared more
than once in the PCP request, that Option value only appears once in
the option-code fields."  I'm not sure this change really adds anything,
but it seems harmless.

         may appear in: responses, and only if the result code is non-
         zero.

I would only expect to see it on UNSUPP_OPTION or MALFORMED_OPTION.

7.  Introduction to MAP and PEER OpCodes

   There are four uses for the MAP and PEER OpCodes defined in this
   document: a host operating a server and wanting an incoming
   connection; a host operating a client and wanting to optimize the
   application keepalive traffic or restore lost state in its NAT; and a
   host operating a client and server on the same port.

That's three (missing 7.3 For Restoring Lost Implicit TCP Dynamic
Mapping State).

The pseudocode is complicated, and has unnecessary stuff, but I'm not
going to fight it.

The pseudocode for PEER (figure 7) doesn't process the PCP response.

7.3.  For Restoring Lost Implicit TCP Dynamic Mapping State

This use case is problematical and contentious, because it requires
the PCP server to create an implicit dynamic mapping, which may not be
possible on that NAT (e.g. it may use different port ranges for
implicit and PCP-controlled mappings).  It's also at odds with the
description of PEER in 9.1, which still says "The PEER OpCodes provide
a single function: the ability for the PCP client to query and
(possibly) extend the lifetime of an existing mapping."  OTOH, it's in
line with later text in 9.3, but that needs to be tightened up and
made normative.

7.4.  For Operating a Symmetric Client/Server

Organizationally, I'd like to see this as 7.2 (after Operating a
Server).  a) It's a closely related topic, and b) this would put the
two MAP scenarios together.

      PCP does not attempt to change or
      dictate how a NAT creates its mappings (endpoint independent
      mapping, or otherwise)

s/mappings/implicit mappings/
After all, explicit dynamic mappings are EIM by definition.

8.  MAP OpCodes

    MAP6=2:   create a mapping between an internal target address and
              external IPv6 address (e.g., NAT46, or firewall)

s/target //

   Note also that all NAT mappings (created by PCP or otherwise) are by
   necessity bidirectional and symmetrical.  For any packet going in one
   direction (in or out) that is translated by the NAT, a reply going in
   the opposite direction needs to have the corresponding opposite
   translation done so that the reply arrives at the right endpoint.
   This means that if a client creates a MAP mapping, and then later
   sends an outgoing packet using the mapping's internal source port,
   the NAT should translate that packet's Internal Address and Port to
   the mapping's External Address and Port, so that replies addressed to
   the External Address and Port are correctly translated to the
   mapping's Internal Address and Port.

Interesting but irrelevant.

8.1.  OpCode Packet Formats

   For both of the MAP OpCodes, if the assigned
   external IP address and assigned external port match the request's
   Internal IP address and port, the functionality is purely a firewall;
   otherwise it pertains to a network address translator which might
   also perform firewall-like functions.

Again, interesting but irrelevant.

8.2.  OpCode-Specific Result Codes

PEER should mention that it uses the same result codes as MAP.

   In addition to the general PCP result codes (Section 5.4), the
   following additional result codes may be returned as a result of the
   four MAP OpCodes received by the PCP server.

!! s/four/two/

   26 EXCESSIVE_REMOTE_PEERS, indicates the PCP server was not able to
      create the filters in this request.  This result code MUST only be
      returned if the MAP request contained the REMOTE_FILTER Option.
      See Section 10.3 for processing information.  This is a long
      lifetime error.

!! s/REMOTE_FILTER/FILTER/

8.3.  OpCode-Specific Client: Generating a Request

   The request MAY contain values in the suggested-external-ip-address
   and suggested-external-port fields.

rewrite as
   The request MAY contain values in the Suggested External Port and
   Suggested External IP Address fields.

8.4.  OpCode-Specific Server: Processing a Request

   If the server is overloaded by requests (from a particular client or
   from all clients), it MAY simply discard requests, as the requests
   will be retried by PCP clients, or MAY generate the SERVER_OVERLOADED
   error response, or both.

Remove "or both" - "discard" implies "without responding".

Also, this is generic, and should be moved to section 6.2.

   If the request contains internal-port=0 and the lifetime is non-zero,
   the server MUST generate a MALFORMED_REQUEST error.
rewrite as
   If the lifetime is non-zero, and the request contains internal-port=0
   or protocol=0, the server MUST generate a MALFORMED_REQUEST error.

   If the requested lifetime is not zero, it indicates a request to
   create a mapping or extend the lifetime of an existing mapping.
add
   If the requested lifetime is zero, it indicates a request to delete
   an existing mapping or set of mappings.

   If the PCP server can allocate the suggested external port, and the
   request did not contain the PREFER_FAILURE Option, it SHOULD do so.
rewrite as
   If the PCP server can allocate the suggested external port, it SHOULD
   do so.

Again, don't pretend a bulleted list is really a long sentence.  And
even if it's structured as an overly long sentence, the proper
connector is not ", or;" but "; or"

   By default, a PCP-controlled device MUST NOT create mappings for a
   protocol not indicated in the request.  For example, if the request
   was for a TCP mapping, a UDP mapping MUST NOT be created.

As opposed to NAT-PMP. Say it.

   If all of the proceeding operations were successful (did not generate
   an error response), then the requested mappings are created or
   refreshed

s/mappings/mapping/
only one per request

8.5.  OpCode-Specific Client: Processing a Response

   After performing common PCP response processing,
add "(see section 6.3)"

    the response is
   further matched with an outstanding request by comparing the
   protocol, internal IP address, internal port.
add "and" before "internal port".

   On error responses,
change to "an error response"

   the assigned external address and assigned external port can also be
   used to match the responses (which is useful if several requests with
   the PREFER_FAILURE option are outstanding).

That makes no sense.  On an error response, the "assigned" external
addr/port are copied from the request.  The client should not have
multiple requests in flight to map the same internal addr/port to
different external addr/port.

   If a successful response,

This clause no verb.  "On a successful response" or "If the response
indicates success".

   the PCP client can use the external IP
   address and port(s) as desired.  Typically the PCP client will
   communicate the external IP address and port(s) to another host on
   the Internet using an application-specific rendezvous mechanism such
   as DNS SRV records.

It's only "port(s)" if there are multiple requests.  Each request
creates a mapping for exactly one port - unless the NAT happens to be
NAT-only, and the request is just to learn to external addr.  Still, I
think it would be clearer to treat each request as creating a single
addr/port mapping.

   On an error response, clients SHOULD NOT repeat the same request to
   the same PCP server within the lifetime returned in the response.

Except the client is supposed to initiate renewal at 1/2 the lifetime.

8.6.  Mapping Lifetime and Deletion

   It is RECOMMENDED that the
   server be configured to restrict lifetimes to less than 24 hours,
   because they will consume ports

s/configured/configurable/
s/they/mappings/

   Mappings created by PCP MAP requests are not
   special or different to mappings created other ways.

This is British usage.  Since the spelling and grammar are mostly
American in this document, you want to say "different from".

   it is implementation-dependent if outgoing traffic extends the
   lifetime of such mappings

add "beyond the PCP-assigned lifetime"

   o  If the internal port is non-zero (port!=0) and protocol is non-
      zero (protocol!=0), it indicates a request to delete the indicated
      mapping immediately.

maybe "the single indicated mapping"

   o  If the internal port is zero (port==0) and the protocol is non-
      zero (protocol!=0), it indicates a request to delete all mappings
      for this Internal Address for the given internal port for all
      transport protocols.

No, that's backwards.  It indicates a request to delete all mappings
for this Internal Address on this protocol.

The effect you describe would be for port!=0 && protocol==0, which is
not specified in this document, because it's not actually useful.

   The suggested external address and port fields are ignored in
   requests where the requested lifetime is 0.

The Suggested External Port and Suggested External IP Address fields...

   If the PCP client attempts to delete an implicit dynamic
   mapping (e.g., created by a TCP SYN), the PCP server deletes the
   mapping and responds with the SUCCESS result code.

Not all NATs may support this.  And shouldn't it be a PEER opcode with
lifetime==0?

   If
   the PCP MAP request was for port=0 (indicating 'all ports'), the PCP
   server deletes all of the explicit dynamic mappings it can (but not
   any implicit mappings)

Compare and contrast with deleting a single implicit mapping.

   An explicit dynamic mapping MUST NOT have its lifetime
   reduced by transport protocol messages (e.g., TCP RST, TCP FIN).

This should be a separate paragraph, perhaps with some justification.

   To reduce unwanted traffic and data corruption, UDP and TCP ports
   should not be immediately re-used for an interval (TIME_WAIT interval
   as discussed in [RFC0793]).  However, the PCP server MUST allow the
   same subscriber and same internal address to re-acquire the same port
   during that interval.

As I mentioned in a previous review, these two requirements are
incompatible.  The MUST in the second sentence changes the "should not"
in the first sentence to a MUST NOT; or the "should not" in the first
sentence changes the MUST in the second sentence to a SHOULD.  It's more
realistic in the SHOULD form, so I'd go with that.

Also remove the word "immediately".  Possibly refer to this explicitly
as a hold-down timer.

   *  all ports, all protocols, all Internal Addresses for which the
   client is authorized:  internal address=0, via the THIRD_PARTY option

I would still recommend setting protocol==0, port==0.

8.7.  Subscriber Renumbering and Address Change Events

   PCP defined in this document
   does not provide machinery to reduce the subscriber renumbering
   problem.

Well, duh.

9.1.  OpCode Packet Formats

   The PEER OpCodes provide a single function: the ability for the PCP
   client to query and (possibly) extend the lifetime of an existing
   mapping.

No longer true.

   Requested Lifetime (in common header):  Requested lifetime of this
      mapping, in seconds.  Note that, depending on the implementation
      of the PCP-controlled device, it may not be possible to reduce the
      lifetime of a mapping (or delete it, with requested lifetime=0)
      using PEER.

There is no discussion about deleting mappings with PEER.

External_AF is the only packet field with an underscore.  I would
expect it to be "External AF".

   External_AF:  For success responses, this contains the address family
      of the external IP address associated with this peer connection,
      to properly decode the External IP Address.  This field is
      necessary because the Remote Peer's IP Address is from the PCP
      client's perspective, whereas the External_AF and External IP
      Address are from the PCP-controlled device's perspective.  As an
      example, if the PCP-controlled device is a NAT64, the PCP client
      only knows the remote peer's IPv6 address, whereas the NAT64 knows
      the remote peer's IPv4 address.  Values are from IANA's address
      family numbers (IPv4 is 1, IPv6 is 2).  For error responses, the
      value is copied from the request.

So this actually creates a difference between MAP and PEER in NAT64:
with MAP, the client would have to know that it's behind a NAT64, and
send a MAP4 request over v6.  Or possibly it would send MAP6, and the
NAT64 would return a v4-mapped v6 address, which the client would then
figure out is mapped, and advertise the corresponding v4 address to
its peers?  Whereas on a PEER6, it has this peer address that's really
v4-mapped v6, and the NAT64 returns an external addr that's explicitly
v4.  It all sounds complicated, and I'd like Simon to explain just how
he sees this all working in NAT64.

   External Port:  For success responses, this is the external port
      number, assigned by the NAT (or firewall) to this mapping.  If
      firewall or 1:1 NAT, this will match the internal port.  For error
      responses, this MUST be 0.

The last restriction doesn't make sense, and doesn't match the usage
in the MAP opcodes ("On error responses, the value from Suggested
External Port is used.").  On an error response, the external addr and
port should be ignored - they could be copied from the request, they
could be zeroed, but they don't contain any meaningful data in either
case.

   External IP Address:  For success responses, this contains the
      external IP address, assigned by the NAT (or firewall) to this
      mapping.  This field allows the PCP client and its remote peer to
      determine if there is another NAT between the PCP-controlled NAT
      and remote peer.

And what will they do with that information?

9.2.  OpCode-Specific Client: Generating a Request

   The PEER4 or PEER6 OpCodes MAY be sent before or after establishing
   bi-directional communication with the remote peer.  If sent before,
   PEER4 or PEER6 OpCodes will create a mapping in the PCP-controlled
   device (for the purpose described in Section 7.3), and the client
   SHOULD set the External_AF and Suggested External IP Address to the
   values of the previous mapping.

and Suggested External Port

   If sent after, the PEER4 or PEER6
   OpCodes query (and control) the implicit dynamic mapping (for the
   purpose described in Section 7.2).

and the Suggested External Port and Suggested External IP Address
fields SHOULD be set to zero.

   If the described mapping does not yet exist yet, it
   is created, honoring and the Suggested External Port and Suggested
   External IP Address are honored 

s/and //
s/are honored //

   (if possible; if not possible, a
   mapping on a different IP address or different port is created).

This implies that the PREFER_FAILURE Option is also valid for PEER
opcodes.

   By
   having PEER create such a mapping, we avoid a race condition between
   the PEER request or the initial outgoing packet arriving at the NAT
   gateway first

If the race condition is really a concern, we just mandate a delay
before sending the PEER request.  The PEER response would also tell
whether the implicit mapping had been successfully created.

It should be possible to delete mappings with PEER, just as for MAP.

Mention THIRD_PARTY with PEER.  Also USER_EX_QUOTA.

MAP and PEER processing should follow pretty much the same path on the
server; the spec should explicitly say what's the same and what's
different.

9.4.  OpCode-Specific Client: Processing a Response

   If a successful response, the application can use the assigned

This clause no verb.  "On a successful response" or "If the response
indicates success".

   If the PCP client wishes to keep this mapping alive beyond the
   indicated lifetime, it SHOULD issue a new PCP request prior to the
   expiration.  That is, inside->outside traffic is not sufficient to
   ensure the mapping will continue to exist.  It is RECOMMENDED to send
   a single renewal request packet when a mapping is halfway to
   expiration time, then, if no SUCCESS response is received, another
   single renewal request 3/4 of the way to expiration time, and then
   another at 7/8 of the way to expiration time, and so on, subject to
   the constraint that renewal requests MUST NOT be sent less than four
   seconds apart (a PCP client MUST NOT ever-closer-together requests in
   the last few seconds before a mapping expires).

For MAP, the language about renewing mappings is in the Generating a
Request section, not the Processing a Response section.

10.1.  THIRD_PARTY Option for MAP and PEER OpCodes

   A THIRD_PARTY Option MUST NOT contain the same address as the source
   address of the packet.  A PCP server receiving a THIRD_PARTY Option
   specifying the same address as the source address of the packet MUST
   return a MALFORMED_REQUEST result code.  This is because many PCP
   servers may not implement the THIRD_PARTY Option at all, and a client
   using the THIRD_PARTY Option to specify the same address as the
   source address of the packet will cause mapping requests to fail
   where they would otherwise have succeeded.

I would expect the operation to succeed if the server supports
THIRD_PARTY, because the client is making a valid request, albeit a
bit oddly.  And if the server doesn't support THIRD_PARTY, it will
return UNSUPP_OPTION, regardless of the contents of the option.

I would prefer to have to option header appear in all option layout
diagrams, for clarity, e.g.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Option Code=4 |  Reserved     |   Option-Length=4 or 16       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   :                                                               :
   :    Internal IP Address (32 bits of 128 bits, depending        :
   :                                       on Option length)       :
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   The following additional result codes may be returned as a result of
   using this Option.

s/codes/code/

   51 UNAUTH_THIRD_PARTY_INTERNAL_ADDRESS

How about using the existing NOT_AUTHORIZED code?  In fact, 8.4 says
the server MUST return NOT_AUTHORIZED in this specific case, and 9.3
doesn't mention THIRD_PARTY, so UNAUTH_THIRD_PARTY_INTERNAL_ADDRESS is
only mentioned in this section.  Seriously, this scenario would seem
to be covered under the following clause from NOT_AUTHORIZED: "the PCP
client requested a mapping that cannot be fulfilled by the PCP
server's security policy."

Paragraph break before "Determining which PCP clients are authorized
to use the THIRD_PARTY option depends on the deployment scenario."

   For home deployments (where the PCP server is
   embedded in the NAT device), this option MUST NOT be processed.

I would say "where the PCP server and the NAT are embedded in a home
gateway device".  Also, THIRD_PARTY would typically not be implemented
on a home gateway, so would generate UNSUPP_OPTION.

   It is RECOMMENDED that PCP servers embedded into customer premise
   equipment be configured to refuse third party mappings by default.
   With this default, if a user wants to create a third party mapping,
   the user needs to interact out-of-band with their customer premise
   router (e.g., using its HTTP administrative interface).

This is largely redundant to the previous paragraph.

   It is RECOMMENDED that PCP servers embedded into service provider NAT
   and firewall devices be configured to permit the THIRD_PARTY option,...

This whole paragraph is confusing, and it's hard to tell what's
actually being recommended or dis-recommended here.  The simple fact
of the matter is that THIRD_PARTY is most useful in DS-Lite, where the
NAT can send packets "directly" to internal hosts that don't embed a
PCP client; i.e. the B4 embeds a UPnP IWF and/or a NAT-PMP IWF and/or
a PCP-PCP proxy.

In a NAT444 scenario, the CGN can't "see" the internal hosts, so
THIRD_PARTY is pointless.  In NAT64 and NAT46, there isn't an obvious
place for an IWF or proxy, so it probably isn't useful there, although
I haven't spent a lot of time thinking about it.

   If the packet arrived from a
   different address, the PCP server MUST generate an
   UNAUTH_THIRD_PARTY_INTERNAL_ADDRESS error.

s/arrived/arrives/

10.2.  PREFER_FAILURE Option for MAP OpCodes

   This option is only used with the MAP4 and MAP6 OpCodes.

Since we redefined PEER to create or re-create mappings, we should
also support PREFER_FAILURE, and should mention it here and in 11.3.1.

If UNAUTH_THIRD_PARTY_INTERNAL_ADDRESS is defined under the
THIRD_PARTY Option (and I've argued that it shouldn't be defined at
all), then CANNOT_PROVIDE_EXTERNAL_PORT should be defined under the
PREFER_FAILURE Option.  Likewise EXCESSIVE_REMOTE_PEERS should be
defined under the FILTER Option.  But really, I'd prefer to keep all
the result codes in 8.2.

10.3.  FILTER Option for MAP OpCodes

   This Option indicates filtering incoming packets is desired.  The
   remote peer port and remote peer IP Address indicate the permitted
   remote peer's source IP address and port for packets from the
   Internet.

s/remote peer port/Remote Peer Port/
s/remote peer IP Address/Remote Peer IP Address/

Change the "prefix-length" field name to "Prefix Length".

I've never been able to figure out why "Reserved" is the first field,
not the second.

Note that FILTER is unidirectional - it doen't prevent an internal
host from sending packets to any remote host, it just prevents remote
hosts from replying.  I'm not saying this needs to be changed.

      is included in responses: MUST, if it appeared in the request

As previously noted, this field is not in the 5.3 boilerplate.
In 5.3, we should say that, if a request includes an Option that is
marked mandatory-to-process, the response (whether success or error)
MUST include that Option.

      length: 2 if used with MAP4, 5 if used with MAP6

!! Wrong; this is the old length (measured in 4-byte words).
Should be "8 if used with MAP4, 20 if used with MAP6".

   If a MAP request has a lifetime of 0 and contains the
   FILTER option, the error MALFORMED_OPTION is returned.

This is an example of the nonsensical-option clause of 8.4.

11.1.  Implementing MAP with non-EIM port-mapping NAPT

   For implicit dynamic mappings, some existing NAT devices have
   endpoint-independent mapping (EIM) behavior while other NAPT devices
   have non-endpoint-independent mapping (non-EIM) behavior.

Here you use NAT and NAPT in the same sentence.  As I said before, I
would refer to all such devices by the vernacular "NAT", unless
there's some clear distinction to be made by referring to NAPT.

   1.  have implicit dynamic mappings (e.g., TCP SYN) use a different
   2.  on arrival of a packet (from the Internet or from an internal

Capitalize

BTW, I prefer the second approach, which uses the most specific match
(somewhat analogously to kernel packet routing).  OTOH, I know Francis
prefers the first approach.

As I see it, the conflict would only arise if there was an existing
implicit mapping, and then an explicit mapping was created.  If the
explicit mapping exists, the NAT will use it for all new connections
from that internal addr/port/proto, rather than creating a new
implicit mapping.

11.2.  Interaction of MAP with Implicit Dynamic Mappings

I'm a bit confused by this one.  If the NAT creates an implicit
mapping that conflicts with an explicit mapping, it's a different
(more specific) mapping in the NAT's mapping table.  Even if the NAT
deletes that mapping on termination of the connection, that won't
affect the (more general) explicit mapping - it would still allow
incoming connections.

13.  Security Considerations

   This document defines Port Control Protocol and two types of OpCodes,
   PEER and MAP.  The PEER OpCode allows querying and extending (if
   permitted) the lifetime of an existing implicit dynamic mapping, so a
   host can reduce its keepalive messages.  The MAP OpCode allows
   creating a mapping so a host can receive incoming unsolicited
   connections from the Internet in order to run a server.

This whole paragraph can be deleted, because it doesn't say anything
new, and it doesn't say anything about security.

14.1.  Port Number

   PCP will use port 5351 (currently assigned by IANA to NAT-PMP).  We
   request that IANA re-assign that same port number to PCP, and
   relinquish UDP port 44323.

The bit about relinquishing port 44323 should be marked for removal by
the RFC Editor.

14.2.  OpCodes

   Additional OpCodes in the range 4-95 can be created via Standards
   Action [RFC5226], and the range 96-126 is for Private Use [RFC5226].

!! s/4/5/ (4 is PEER6)
How/why was the number 95 chosen?

14.3.  Result Codes

   IANA shall create a new registry for PCP result codes, numbered
   0-255, initially populated with the result codes from Section 5.4,
   Section 8.2, Section 10.3, and Section 10.1.  The values 0 and 255
   are reserved.

10.3 doesn't define a result code.

   Additional Result Codes can be defined via Specification Required
   [RFC5226].

There needs to be a Private range for result codes, to support Private
OpCodes and Options.

14.4.  Options

   IANA shall create a new registry for PCP Options, numbered 0-255 with
   an associated mnemonic.  The values 0-127 are mandatory-to-process,
   and 128-255 are optional-to-process.  The initial registry contains
   the options described in Section 10 and Section 10.1.  The option
   values 127 and 255 are reserved.

and sections 10.2 and 10.3 - why don't we just say section 10 (as a
whole), and drop the reference to 10.1?

From dwing@cisco.com  Tue May 31 11:40:48 2011
Return-Path: <dwing@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02A7CE071B for <pcp@ietfa.amsl.com>; Tue, 31 May 2011 11:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.958
X-Spam-Level: 
X-Spam-Status: No, score=-110.958 tagged_above=-999 required=5 tests=[AWL=0.401, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_HI=-8, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J+ztCBis8VCJ for <pcp@ietfa.amsl.com>; Tue, 31 May 2011 11:40:44 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfa.amsl.com (Postfix) with ESMTP id CF00BE06B9 for <pcp@ietf.org>; Tue, 31 May 2011 11:40:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=46125; q=dns/txt; s=iport; t=1306867244; x=1308076844; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=mtYxWNJ6dmeaJuUw6CSXRYhH4ijv2gD5sHoX22jHlUw=; b=f+5zXKiiD6WaBzy9OySuYMzkaGKi4+wTgEQ4DE390bLlUWtSIAlemLqd iwmozkKWDXhuF5FEaYAPAWUrN8xcgF3mbkic31LBCSow8w1tmC3y67hBY hrYs7s2IZnpKRwGNz2qqpq9NbA7zvb040+1GfKqp3teOUVlft/2LmvUJe A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBAGI15U2rRDoJ/2dsb2JhbABFDpMBhE2BZIxvd4hxn1mdVoMXgwcEhmSZJQ
X-IronPort-AV: E=Sophos;i="4.65,298,1304294400"; d="scan'208";a="367511461"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-2.cisco.com with ESMTP; 31 May 2011 18:40:44 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p4VIehrM023491; Tue, 31 May 2011 18:40:43 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Paul Selkirk'" <pselkirk@isc.org>, <pcp@ietf.org>
References: <9B57C850BB53634CACEC56EF4853FF653B0BA0FD@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <s1vmxi35wdd.fsf@bikeshed.isc.org>
In-Reply-To: <s1vmxi35wdd.fsf@bikeshed.isc.org>
Date: Tue, 31 May 2011 11:40:43 -0700
Message-ID: <04ce01cc1fc2$3fa360d0$beea2270$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwfSulbNvnKpeCTTsqeDQrCvC6F3gAdZA+w
Content-Language: en-us
Subject: Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 31 May 2011 18:40:48 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Paul Selkirk
> Sent: Monday, May 30, 2011 9:26 PM
> To: pcp@ietf.org
> Subject: Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt
> 
> I'm sorry this review is so long; I didn't have time to write a shorter
> one.
> 
> I also apologize if this touches on issues that are being or have been
> hashed out on the mailing list; I'm way behind on WG mail.
> 
> There are a few places where I have issues with how the protocol
> actually works, a few clear (but easily cleared) errors in the
> current draft (marked with "!!"), and a lot of editorial nits.
> 
> For the errors and nits, I'd be willing to make the necessary changes
> myself, if Dan can give me the document source (since I seem to be
> listed as a co-author now).

Will send you a pointer.

> ----------------
> Policy issues:
> 
> - I'm not happy with the way PEER has evolved, to where it can create
> mappings.  It's heading in the direction of making MAP a special case
> of PEER (with remote port=0, remote peer=0 as wildcards).  I also don't
> think the 7.3 use case is compelling enough to justify the added
> complexity in the protocol (or even the suggested added complexity in
> the client).

The motivation for that change was to eliminate the error condition
if the PCP server received a PEER message for a mapping that didn't
already exist.  The fear was that client code would not be implemented
robustly to deal with that error, because the error would occur
rarely.

I would certainly like to hear from others on this change.  Only a 
few people have provided Yeah/Nay comments on this change.  From
memory, I recall:

   Dan:     yeah
   Simon:   yeah
   Stuart:  yeah
   Paul:    nay
   Francis: nay

> - I don't like the PCP Client's IP Address field.  I don't think it
> adds
> sufficient value to be worth spending 16 bytes in every packet, plus
> additional processing time.  I would support moving it to an Option, or
> at least making it an optional field - e.g. if it's sent as all-zeroes
> in the request, the server MUST process the request, and MAY either
> fill
> it in, or leave it zeroed.  The change log says "This addition was
> consensus at IETF80", but that doesn't match my notes of the meeting -
> it was discussed as a possible approach to a possible problem, but no
> sense of the meeting was ever asked.

The consensus of the meeting is there was a problem that the protocol
could solve.  I admit this solution was not agreed at the meeting --
discussing bits-on-the-wire seemed a poor use of meeting time.

Moving it to an option implies there are cases where the PCP client 
does not want to test for an on-path NAT.  What are those cases?  (I
need to know, in order to write text explaining when the option should
be used and when it shouldn't be used).

> - UNAUTH_THIRD_PARTY_INTERNAL_ADDRESS could be removed, and replaced
> with NOT_AUTHORIZED (more on that inline).
> 
> - There is no discussion about levels of conformance.  There's some
> discussion about particular options being optional (e.g. THIRD_PARTY
> not supported in certain deployment scenarios), but no overall
> statement of what features must be supported by all conformant
> implementations.  e.g. If I had a small embedded server that supported
> MAP opcodes but not PEER, would it be conformant?

Nobody has initiated discussion or provided a straw-man on conformance 
levels.  What do we want?  Myself, if there is any chance of a wireless
devices (which is approximately 100% chance), PEER needs to be supported
because it allows the wireless device to optimize its NAT keepalive
traffic.  But, to me, MAP doesn't need to necessarily be supported.


-d



> ----------------
> General nits:
> 
> Normalize capitalization in all instances of "OpCode" and "Option".
> (8 instances of "opcode", 5 instance of "Opcode", 76 instances of
> "option").
> 
> Normalize capitalization of things like Internal Port and Remote Peer
> Port (didn't count them).
> 
> Change "error code" to "result code" (5 instances).
> 
> Possibly use "NAT" as accepted vernacular throughout, even when
> referring to NAPT, unless there's some clear distinction to be made by
> referring to NAPT.
> 
> There are many places where the text has unnecessary embedded
> definitions of implicit and/or explicit mappings:
> 7.4, 8.6 (twice), 11.1, 12.2, 13, 13.1, 13.2.
> 
> ----------------
> Line-by-line review:
> 
> 1.  Introduction
> 
>    PCP is primarily designed to be implemented in
>    the context of both Carrier-Grade NATs (CGN) and small NATs (e.g.,
>    residential NATs).
> 
> Remove "primarily" - what other kind of NATs are there?
> 
>    PCP allows hosts to operate server for a long
>    time (e.g., a webcam) or a short time (e.g., while playing a game or
>    on a phone call)
> 
> A webcam could be long or short term, ditto a game or phone call.
> Even the client may not be able to predict how long a mapping may be
> needed.  It's immaterial to the protocol.
> 
> 2.1.  Deployment Scenarios
> 
>    PCP can be used in various deployment scenarios, including:
>    ...
> 
> Make this a real bulleted list, rather than a long bulleted sentence.
> Also reorder to group them as current and emerging scenarios, e.g.
> 
>    PCP can be used in various deployment scenarios, including:
> 
>    o  Basic NAT [RFC3022]
> 
>    o  Network Address and Port Translation (NAPT) [RFC3022], such as
>       commonly deployed in residential NAT devices
> 
>    o  Carrier-Grade NAT [I-D.ietf-behave-lsn-requirements]
> 
>    o  Dual-Stack Lite (DS-Lite) [I-D.ietf-softwire-dual-stack-lite]
> 
>    o  Layer-2 aware NAT [I-D.miles-behave-l2nat] and Dual-Stack Extra
>       Lite [I-D.arkko-dual-stack-extra-lite]
> 
>    o  NAT64, both Stateful [RFC6146] and Stateless [RFC6145]
> 
>    o  IPv4 and IPv6 simple firewall control [RFC6092]
> 
> 2.3.  Single-homed Customer Premises Network
> 
>    The PCP machinery assumes a single-homed host model.
> 
> "machinery" is an odd word
> s/The PCP machinery/PCP/
> 
>    This
>    restriction exists because otherwise there would need to be one PCP
>    server for each egress, because the host could not reliably
> determine
>    which egress path packets would take, so the client would need to be
>    able to reliably make the same internal/external mapping in every
> NAT
>    gateway, which in general is not possible (because the other NATs
>    would likely have the necessary port mapped to another host).
> 
> run-on sentence
> 
> 3.  Terminology
> 
> Add "PCP-controlled device" = NAT or firewall
> 
>    PCP Client:
>       A PCP Client can issue PCP request on behalf of a third
> 
> s/request/requests/
> 
>       An interworking
>       function from Universal Plug and Play Internet Gateway Device
>       (UPnP IGD, [IGD]) to PCP is another example of a PCP Client.
> 
> Capitalize "interworking function"
> 
>    Interworking Function:
>       a functional element responsible for interworking another
> protocol
>       with PCP.  For example interworking between UPnP IGD [IGD] with
>       PCP.
> 
> Capitalize "a"
> 
> Also, define "interworking"; maybe something like
>       A functional element responsible for translating another protocol
>       to PCP.
> 
>    subscriber:
>       an entity provided access to the network.  In the case of a
>       commercial ISP, this is typically a single home.
> 
> Capitalize "subscriber", "an"
> 
>    5-tuple  The 5 pieces of information that fully identify a flow,
> from
>       the perspective of a subscriber: source IP address, destination
> IP
> 
> Line break before "The"
> 
> Also, change "subscriber" to "internal host" or "PCP client" for
> consistency.
> 
> 4.  Relationship between PCP Server and its NAT/firewall
> 
>    The PCP server receives PCP requests.  The PCP server might be
>    integrated within the NAT or firewall device (as shown in Figure 1)
>    which is expected to be a common deployment.
> 
>    It is also possible to operate the PCP server in a separate device
>    from the NAT, so long as such operation is indistinguishable from
> the
>    PCP client's perspective.
> 
> This is completely redundant to the Terminology entry.
> In this case, I'd radically trim the terminology section, e.g.
> 
>    PCP Server:
>       A network element which receives and processes PCP requests from
> a
>       PCP client.  Generally this is a PCP-capable NAT gateway or
>       firewall.
> 
> 5.1.  Request Header
> 
>    OpCode:  Opcodes are defined in Section 8 and Section 9.
> 
> This seems like it needs something more.
> 
>    Requested Lifetime:  The Requested Lifetime field is an unsigned 32-
>       bit integer, in seconds, ranging from 0 to 4,294,967,295 seconds.
> 
> s/The Requested Lifetime field is //
> 
>    PCP Client's IP Address:  The IP address of the PCP client, from the
>       PCP client's perspective.  If IPv4, only the first 32 bits are
>       used, the other bits MUST be set to 0.
> 
> This needs a little explanation, e.g. "If the enclosing IP packet is
> IPv4, only the first 32 bits are used; the other bits MUST be sent as
> 0 and MUST be ignore when received."
> 
> This is discussed/explained/rationalized in 6.2, but as "PCP Client IP
> Address" (no apostrophe s).
> 
> It must be optional - if it's all zeroes, the server will not reject
> the packet, and will either send back its idea of the client's IP
> address, or leave it zero'd.
> 
> Also normalize capitalization: "address" is lowercase in both of the
> packet diagrams.
> 
> 5.2.  Response Header
> 
>    Lifetime:  The Lifetime field is an unsigned 32-bit integer, in
>       seconds, ranging from 0 to 4,294,967,295 seconds.
> 
> s/The Lifetime field is //
> 
>    Epoch:  The server's Epoch value.  See Section 6.5 for discussion.
>       This value is set in both success and error responses.
> 
> This needs a concise description here, e.g. "seconds since start of
> epoch".
> 
> 5.3.  Options
> 
>    A PCP OpCode can be extended with an Option.
> 
> PCP packets can be extended with Options. (i.e. one or more)
> 
>    A given Option MAY be included in a request containing a specific
>    OpCode.  The handling of an Option by the PCP client and PCP server
>    MUST be specified in an appropriate document and MUST include
> whether
>    the PCP Option can appear (one or more times) in a request and/or
>    response, and indicate the contents of the Option in the request and
>    in the response.  If several Options are included in a PCP request
> or
>    response, they MAY be encoded in any order by the PCP client and are
>    processed in the order received.
> 
> rewrite as
>    The handling of an Option by the PCP client and PCP server MUST be
>    specified in an appropriate document, which MUST include whether
>    the PCP Option can appear in a request and/or response, whether it
>    can appear more than once, and indicate what sort of Option data it
>    conveys.  If several Options are included in a PCP request, they
>    MAY be encoded in any order by the PCP client, but MUST be
>    processed by the PCP server in the order in which they appear.
> 
> (The original wording of the last sentence was contradicted by the
> next paragraph: "The response MUST encode the Options in the same
> order".)
> 
> Actually, the whole paragraph is redundant to later text describing
> what an Option definition must include.
> 
>    The response MUST encode the Options in the same order,
>    but may omit some PCP Options in the response, as is necessary to
>    indicate the PCP server does not understand that Option or that
> 
> s/may/MAY/
> s/as is necessary //
> 
>    If the "O" bit (high bit) in the OpCode is clear,
> 
>    o  the PCP server MUST only generate a positive PCP response if it
>       can successfully process the PCP request and this Option.
> 
>    o  if the PCP server does not implement this Option, or cannot
>       perform the function indicated by this Option (e.g., due to a
>       parsing error with the option), it MUST generate a failure
>       response with code UNSUPP_OPTION or MALFORMED_OPTION (as
>       appropriate) and include the UNPROCESSED option in the response
>       (Section 6.7.1).
> 
> Remove the first bullet, make one sentence, change "failure response"
> to "error response":
> 
> If the "O" bit (high bit) in the OpCode is clear, the PCP server MUST
> process this Option.  If the PCP server does not implement this
> Option, or cannot perform the function indicated by this Option (e.g.,
> due to a parsing error with the option), it MUST generate an error
> response with result code UNSUPP_OPTION or MALFORMED_OPTION (as
> appropriate), and include the UNPROCESSED option in the response
> (Section 6.7.1).
> 
> PREFER_FAILURE and FILTER do not include "purpose", but include
> non-boilerplate "is included in responses".
> 
> Option boilerplate fields should start with a capital letter, e.g.
>          Name: <mnemonic>
>          Number: <value>
>          Purpose: <textual description>
>          Valid for OpCodes: <list of OpCodes>
>          Length: <rules for length>
>          May appear in: <requests/responses/both>
>          Maximum occurrences: <count>
> 
> 5.4.  Result Codes
> 
>    The following result codes may be returned as a result of any OpCode
>    received by the PCP server.  The only success result code is 0,
> other
>    values indicate an error.  If a PCP server has encountered multiple
>    errors during processing of a request, it SHOULD use the most
>    specific error message.
> 
> s/0,/0;/
> s/has encountered/encounters/
> 
>    4  UNSUPP_OPTION, unsupported Option.  This error only occurs if the
>       Option is in the mandatory-to-process range.
> 
> i.e. the "O" bit is clear
> 
> 6.  General PCP Operation
> 
>    The order of operation is that a PCP client generates
>    and sends a request to the PCP server, which processes the request
>    and generates a response back to the PCP client.
> 
> Is it really necessary to say this?  Or is it saying something
> normative, like this is a lock-step protocol with no request batching
> or pipelining?  In any case, it doesn't belong in the same paragraph
> as the discussion of idempotency.
> 
> 6.1.  General PCP Client: Generating a Request
> 
> I'd still like to see this broken out into separate sections on server
> discovery, retransmission timers, and server failover.
> 
>    The PCP client sends a PCP message the first
>    server in its list of PCP servers.
> 
> s/message/request to/
> 
> It should be stated that there should be only one NAT on each
> interface, and the purpose of having multiple server addresses is to
> have multiple ways to contact *one* server.  e.g. A PCP server
> controlling a DS-Lite AFTR may be reachable by one or more IPv6
> addresses, and may also be reachable by IPv4 encapsulated in IPv6.
> 
> 6.2.  General PCP Server: Processing a Request
> 
>    If the source IP address of the received packet does not match the
>    contents of the PCP Client IP Address field, a response is generated
>    with the ADDRESS_MISMATCH result code.  This is done to detect and
>    prevent accidental use of PCP where a non-PCP-aware NAT or NAPT
>    exists between the PCP client and PCP server.
> 
> s/PCP Client IP Address/PCP Client's IP Address/
> 
> !! ADDRESS_MISMATCH is not defined anywhere (should be in 5.4).
> 
>    Error responses have the same packet layout as success responses,
>    with fields from the request copied into the response, and fields
>    assigned by the PCP server are set as indicated in Figure 3
> 
> period.
> 
> 6.3.  General PCP Client: Processing a Response
> 
>    If the result code is SERVER_OVERLOADED, clients SHOULD NOT send
>    *any* further requests to that PCP server for the indicated error
>    lifetime.
> 
> s/clients/the PCP client/
> 
>    For other error result codes, The PCP client SHOULD NOT
>    resend the same request for the indicated error lifetime.
> 
> s/The/the/
> 
>    If a PCP
>    server indicates an error lifetime in excess of 30 minutes, A PCP
>    client MAY choose to set its retry timer to 30 minutes.
> 
> s/A/a/
> 
>    If the PCP client has discovered a new PCP server (e.g., connected
> to
>    a new network), the PCP client MAY immediately begin communicating
>    with this PCP server, without regard to hold times from
> communicating
>    with a previous PCP server.
> 
> (See section 6.1.)
> 
> 6.5.  Epoch
> 
>    When a client notices that the PCP server reduced its Epoch value,
>    the PCP clients will send PCP requests to refresh their mappings.
> 
> This is redundant to the immediately preceding sentence.
> 
> 6.6.  Version Negotiation
> 
>    When sending a response containing the UNSUPP_VERSION result code,
>    the PCP message MUST be 12 octets long.
> 
> i.e. no PCP Client's IP Address or Opcode section - Is this really
> what you meant, or was this not updated when PCP Client's IP Address
> was added?
> 
> I think this restriction is a mistake, and the response should follow
> normal guidelines, e.g. copy the whole request into the response.
> This restriction was added in -08 with no explanation in the change
> log.
> 
> 6.7.1.  UNPROCESSED Option
> 
>    If
>    a certain Option appeared more than once in the PCP request, that
>    Option value can appear once or as many times as it occurred in the
>    request.
> 
> This was also changed in -08, was "If a certain Option appeared more
> than once in the PCP request, that Option value only appears once in
> the option-code fields."  I'm not sure this change really adds
> anything,
> but it seems harmless.
> 
>          may appear in: responses, and only if the result code is non-
>          zero.
> 
> I would only expect to see it on UNSUPP_OPTION or MALFORMED_OPTION.
> 
> 7.  Introduction to MAP and PEER OpCodes
> 
>    There are four uses for the MAP and PEER OpCodes defined in this
>    document: a host operating a server and wanting an incoming
>    connection; a host operating a client and wanting to optimize the
>    application keepalive traffic or restore lost state in its NAT; and
> a
>    host operating a client and server on the same port.
> 
> That's three (missing 7.3 For Restoring Lost Implicit TCP Dynamic
> Mapping State).
> 
> The pseudocode is complicated, and has unnecessary stuff, but I'm not
> going to fight it.
> 
> The pseudocode for PEER (figure 7) doesn't process the PCP response.
> 
> 7.3.  For Restoring Lost Implicit TCP Dynamic Mapping State
> 
> This use case is problematical and contentious, because it requires
> the PCP server to create an implicit dynamic mapping, which may not be
> possible on that NAT (e.g. it may use different port ranges for
> implicit and PCP-controlled mappings).  It's also at odds with the
> description of PEER in 9.1, which still says "The PEER OpCodes provide
> a single function: the ability for the PCP client to query and
> (possibly) extend the lifetime of an existing mapping."  OTOH, it's in
> line with later text in 9.3, but that needs to be tightened up and
> made normative.
> 
> 7.4.  For Operating a Symmetric Client/Server
> 
> Organizationally, I'd like to see this as 7.2 (after Operating a
> Server).  a) It's a closely related topic, and b) this would put the
> two MAP scenarios together.
> 
>       PCP does not attempt to change or
>       dictate how a NAT creates its mappings (endpoint independent
>       mapping, or otherwise)
> 
> s/mappings/implicit mappings/
> After all, explicit dynamic mappings are EIM by definition.
> 
> 8.  MAP OpCodes
> 
>     MAP6=2:   create a mapping between an internal target address and
>               external IPv6 address (e.g., NAT46, or firewall)
> 
> s/target //
> 
>    Note also that all NAT mappings (created by PCP or otherwise) are by
>    necessity bidirectional and symmetrical.  For any packet going in
> one
>    direction (in or out) that is translated by the NAT, a reply going
> in
>    the opposite direction needs to have the corresponding opposite
>    translation done so that the reply arrives at the right endpoint.
>    This means that if a client creates a MAP mapping, and then later
>    sends an outgoing packet using the mapping's internal source port,
>    the NAT should translate that packet's Internal Address and Port to
>    the mapping's External Address and Port, so that replies addressed
> to
>    the External Address and Port are correctly translated to the
>    mapping's Internal Address and Port.
> 
> Interesting but irrelevant.
> 
> 8.1.  OpCode Packet Formats
> 
>    For both of the MAP OpCodes, if the assigned
>    external IP address and assigned external port match the request's
>    Internal IP address and port, the functionality is purely a
> firewall;
>    otherwise it pertains to a network address translator which might
>    also perform firewall-like functions.
> 
> Again, interesting but irrelevant.
> 
> 8.2.  OpCode-Specific Result Codes
> 
> PEER should mention that it uses the same result codes as MAP.
> 
>    In addition to the general PCP result codes (Section 5.4), the
>    following additional result codes may be returned as a result of the
>    four MAP OpCodes received by the PCP server.
> 
> !! s/four/two/
> 
>    26 EXCESSIVE_REMOTE_PEERS, indicates the PCP server was not able to
>       create the filters in this request.  This result code MUST only
> be
>       returned if the MAP request contained the REMOTE_FILTER Option.
>       See Section 10.3 for processing information.  This is a long
>       lifetime error.
> 
> !! s/REMOTE_FILTER/FILTER/
> 
> 8.3.  OpCode-Specific Client: Generating a Request
> 
>    The request MAY contain values in the suggested-external-ip-address
>    and suggested-external-port fields.
> 
> rewrite as
>    The request MAY contain values in the Suggested External Port and
>    Suggested External IP Address fields.
> 
> 8.4.  OpCode-Specific Server: Processing a Request
> 
>    If the server is overloaded by requests (from a particular client or
>    from all clients), it MAY simply discard requests, as the requests
>    will be retried by PCP clients, or MAY generate the
> SERVER_OVERLOADED
>    error response, or both.
> 
> Remove "or both" - "discard" implies "without responding".
> 
> Also, this is generic, and should be moved to section 6.2.
> 
>    If the request contains internal-port=0 and the lifetime is non-
> zero,
>    the server MUST generate a MALFORMED_REQUEST error.
> rewrite as
>    If the lifetime is non-zero, and the request contains internal-
> port=0
>    or protocol=0, the server MUST generate a MALFORMED_REQUEST error.
> 
>    If the requested lifetime is not zero, it indicates a request to
>    create a mapping or extend the lifetime of an existing mapping.
> add
>    If the requested lifetime is zero, it indicates a request to delete
>    an existing mapping or set of mappings.
> 
>    If the PCP server can allocate the suggested external port, and the
>    request did not contain the PREFER_FAILURE Option, it SHOULD do so.
> rewrite as
>    If the PCP server can allocate the suggested external port, it
> SHOULD
>    do so.
> 
> Again, don't pretend a bulleted list is really a long sentence.  And
> even if it's structured as an overly long sentence, the proper
> connector is not ", or;" but "; or"
> 
>    By default, a PCP-controlled device MUST NOT create mappings for a
>    protocol not indicated in the request.  For example, if the request
>    was for a TCP mapping, a UDP mapping MUST NOT be created.
> 
> As opposed to NAT-PMP. Say it.
> 
>    If all of the proceeding operations were successful (did not
> generate
>    an error response), then the requested mappings are created or
>    refreshed
> 
> s/mappings/mapping/
> only one per request
> 
> 8.5.  OpCode-Specific Client: Processing a Response
> 
>    After performing common PCP response processing,
> add "(see section 6.3)"
> 
>     the response is
>    further matched with an outstanding request by comparing the
>    protocol, internal IP address, internal port.
> add "and" before "internal port".
> 
>    On error responses,
> change to "an error response"
> 
>    the assigned external address and assigned external port can also be
>    used to match the responses (which is useful if several requests
> with
>    the PREFER_FAILURE option are outstanding).
> 
> That makes no sense.  On an error response, the "assigned" external
> addr/port are copied from the request.  The client should not have
> multiple requests in flight to map the same internal addr/port to
> different external addr/port.
> 
>    If a successful response,
> 
> This clause no verb.  "On a successful response" or "If the response
> indicates success".
> 
>    the PCP client can use the external IP
>    address and port(s) as desired.  Typically the PCP client will
>    communicate the external IP address and port(s) to another host on
>    the Internet using an application-specific rendezvous mechanism such
>    as DNS SRV records.
> 
> It's only "port(s)" if there are multiple requests.  Each request
> creates a mapping for exactly one port - unless the NAT happens to be
> NAT-only, and the request is just to learn to external addr.  Still, I
> think it would be clearer to treat each request as creating a single
> addr/port mapping.
> 
>    On an error response, clients SHOULD NOT repeat the same request to
>    the same PCP server within the lifetime returned in the response.
> 
> Except the client is supposed to initiate renewal at 1/2 the lifetime.
> 
> 8.6.  Mapping Lifetime and Deletion
> 
>    It is RECOMMENDED that the
>    server be configured to restrict lifetimes to less than 24 hours,
>    because they will consume ports
> 
> s/configured/configurable/
> s/they/mappings/
> 
>    Mappings created by PCP MAP requests are not
>    special or different to mappings created other ways.
> 
> This is British usage.  Since the spelling and grammar are mostly
> American in this document, you want to say "different from".
> 
>    it is implementation-dependent if outgoing traffic extends the
>    lifetime of such mappings
> 
> add "beyond the PCP-assigned lifetime"
> 
>    o  If the internal port is non-zero (port!=0) and protocol is non-
>       zero (protocol!=0), it indicates a request to delete the
> indicated
>       mapping immediately.
> 
> maybe "the single indicated mapping"
> 
>    o  If the internal port is zero (port==0) and the protocol is non-
>       zero (protocol!=0), it indicates a request to delete all mappings
>       for this Internal Address for the given internal port for all
>       transport protocols.
> 
> No, that's backwards.  It indicates a request to delete all mappings
> for this Internal Address on this protocol.
> 
> The effect you describe would be for port!=0 && protocol==0, which is
> not specified in this document, because it's not actually useful.
> 
>    The suggested external address and port fields are ignored in
>    requests where the requested lifetime is 0.
> 
> The Suggested External Port and Suggested External IP Address fields...
> 
>    If the PCP client attempts to delete an implicit dynamic
>    mapping (e.g., created by a TCP SYN), the PCP server deletes the
>    mapping and responds with the SUCCESS result code.
> 
> Not all NATs may support this.  And shouldn't it be a PEER opcode with
> lifetime==0?
> 
>    If
>    the PCP MAP request was for port=0 (indicating 'all ports'), the PCP
>    server deletes all of the explicit dynamic mappings it can (but not
>    any implicit mappings)
> 
> Compare and contrast with deleting a single implicit mapping.
> 
>    An explicit dynamic mapping MUST NOT have its lifetime
>    reduced by transport protocol messages (e.g., TCP RST, TCP FIN).
> 
> This should be a separate paragraph, perhaps with some justification.
> 
>    To reduce unwanted traffic and data corruption, UDP and TCP ports
>    should not be immediately re-used for an interval (TIME_WAIT
> interval
>    as discussed in [RFC0793]).  However, the PCP server MUST allow the
>    same subscriber and same internal address to re-acquire the same
> port
>    during that interval.
> 
> As I mentioned in a previous review, these two requirements are
> incompatible.  The MUST in the second sentence changes the "should not"
> in the first sentence to a MUST NOT; or the "should not" in the first
> sentence changes the MUST in the second sentence to a SHOULD.  It's
> more
> realistic in the SHOULD form, so I'd go with that.
> 
> Also remove the word "immediately".  Possibly refer to this explicitly
> as a hold-down timer.
> 
>    *  all ports, all protocols, all Internal Addresses for which the
>    client is authorized:  internal address=0, via the THIRD_PARTY
> option
> 
> I would still recommend setting protocol==0, port==0.
> 
> 8.7.  Subscriber Renumbering and Address Change Events
> 
>    PCP defined in this document
>    does not provide machinery to reduce the subscriber renumbering
>    problem.
> 
> Well, duh.
> 
> 9.1.  OpCode Packet Formats
> 
>    The PEER OpCodes provide a single function: the ability for the PCP
>    client to query and (possibly) extend the lifetime of an existing
>    mapping.
> 
> No longer true.
> 
>    Requested Lifetime (in common header):  Requested lifetime of this
>       mapping, in seconds.  Note that, depending on the implementation
>       of the PCP-controlled device, it may not be possible to reduce
> the
>       lifetime of a mapping (or delete it, with requested lifetime=0)
>       using PEER.
> 
> There is no discussion about deleting mappings with PEER.
> 
> External_AF is the only packet field with an underscore.  I would
> expect it to be "External AF".
> 
>    External_AF:  For success responses, this contains the address
> family
>       of the external IP address associated with this peer connection,
>       to properly decode the External IP Address.  This field is
>       necessary because the Remote Peer's IP Address is from the PCP
>       client's perspective, whereas the External_AF and External IP
>       Address are from the PCP-controlled device's perspective.  As an
>       example, if the PCP-controlled device is a NAT64, the PCP client
>       only knows the remote peer's IPv6 address, whereas the NAT64
> knows
>       the remote peer's IPv4 address.  Values are from IANA's address
>       family numbers (IPv4 is 1, IPv6 is 2).  For error responses, the
>       value is copied from the request.
> 
> So this actually creates a difference between MAP and PEER in NAT64:
> with MAP, the client would have to know that it's behind a NAT64, and
> send a MAP4 request over v6.  Or possibly it would send MAP6, and the
> NAT64 would return a v4-mapped v6 address, which the client would then
> figure out is mapped, and advertise the corresponding v4 address to
> its peers?  Whereas on a PEER6, it has this peer address that's really
> v4-mapped v6, and the NAT64 returns an external addr that's explicitly
> v4.  It all sounds complicated, and I'd like Simon to explain just how
> he sees this all working in NAT64.
> 
>    External Port:  For success responses, this is the external port
>       number, assigned by the NAT (or firewall) to this mapping.  If
>       firewall or 1:1 NAT, this will match the internal port.  For
> error
>       responses, this MUST be 0.
> 
> The last restriction doesn't make sense, and doesn't match the usage
> in the MAP opcodes ("On error responses, the value from Suggested
> External Port is used.").  On an error response, the external addr and
> port should be ignored - they could be copied from the request, they
> could be zeroed, but they don't contain any meaningful data in either
> case.
> 
>    External IP Address:  For success responses, this contains the
>       external IP address, assigned by the NAT (or firewall) to this
>       mapping.  This field allows the PCP client and its remote peer to
>       determine if there is another NAT between the PCP-controlled NAT
>       and remote peer.
> 
> And what will they do with that information?
> 
> 9.2.  OpCode-Specific Client: Generating a Request
> 
>    The PEER4 or PEER6 OpCodes MAY be sent before or after establishing
>    bi-directional communication with the remote peer.  If sent before,
>    PEER4 or PEER6 OpCodes will create a mapping in the PCP-controlled
>    device (for the purpose described in Section 7.3), and the client
>    SHOULD set the External_AF and Suggested External IP Address to the
>    values of the previous mapping.
> 
> and Suggested External Port
> 
>    If sent after, the PEER4 or PEER6
>    OpCodes query (and control) the implicit dynamic mapping (for the
>    purpose described in Section 7.2).
> 
> and the Suggested External Port and Suggested External IP Address
> fields SHOULD be set to zero.
> 
>    If the described mapping does not yet exist yet, it
>    is created, honoring and the Suggested External Port and Suggested
>    External IP Address are honored
> 
> s/and //
> s/are honored //
> 
>    (if possible; if not possible, a
>    mapping on a different IP address or different port is created).
> 
> This implies that the PREFER_FAILURE Option is also valid for PEER
> opcodes.
> 
>    By
>    having PEER create such a mapping, we avoid a race condition between
>    the PEER request or the initial outgoing packet arriving at the NAT
>    gateway first
> 
> If the race condition is really a concern, we just mandate a delay
> before sending the PEER request.  The PEER response would also tell
> whether the implicit mapping had been successfully created.
> 
> It should be possible to delete mappings with PEER, just as for MAP.
> 
> Mention THIRD_PARTY with PEER.  Also USER_EX_QUOTA.
> 
> MAP and PEER processing should follow pretty much the same path on the
> server; the spec should explicitly say what's the same and what's
> different.
> 
> 9.4.  OpCode-Specific Client: Processing a Response
> 
>    If a successful response, the application can use the assigned
> 
> This clause no verb.  "On a successful response" or "If the response
> indicates success".
> 
>    If the PCP client wishes to keep this mapping alive beyond the
>    indicated lifetime, it SHOULD issue a new PCP request prior to the
>    expiration.  That is, inside->outside traffic is not sufficient to
>    ensure the mapping will continue to exist.  It is RECOMMENDED to
> send
>    a single renewal request packet when a mapping is halfway to
>    expiration time, then, if no SUCCESS response is received, another
>    single renewal request 3/4 of the way to expiration time, and then
>    another at 7/8 of the way to expiration time, and so on, subject to
>    the constraint that renewal requests MUST NOT be sent less than four
>    seconds apart (a PCP client MUST NOT ever-closer-together requests
> in
>    the last few seconds before a mapping expires).
> 
> For MAP, the language about renewing mappings is in the Generating a
> Request section, not the Processing a Response section.
> 
> 10.1.  THIRD_PARTY Option for MAP and PEER OpCodes
> 
>    A THIRD_PARTY Option MUST NOT contain the same address as the source
>    address of the packet.  A PCP server receiving a THIRD_PARTY Option
>    specifying the same address as the source address of the packet MUST
>    return a MALFORMED_REQUEST result code.  This is because many PCP
>    servers may not implement the THIRD_PARTY Option at all, and a
> client
>    using the THIRD_PARTY Option to specify the same address as the
>    source address of the packet will cause mapping requests to fail
>    where they would otherwise have succeeded.
> 
> I would expect the operation to succeed if the server supports
> THIRD_PARTY, because the client is making a valid request, albeit a
> bit oddly.  And if the server doesn't support THIRD_PARTY, it will
> return UNSUPP_OPTION, regardless of the contents of the option.
> 
> I would prefer to have to option header appear in all option layout
> diagrams, for clarity, e.g.
> 
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    | Option Code=4 |  Reserved     |   Option-Length=4 or 16       |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                                                               :
>    :    Internal IP Address (32 bits of 128 bits, depending        :
>    :                                       on Option length)       :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>    The following additional result codes may be returned as a result of
>    using this Option.
> 
> s/codes/code/
> 
>    51 UNAUTH_THIRD_PARTY_INTERNAL_ADDRESS
> 
> How about using the existing NOT_AUTHORIZED code?  In fact, 8.4 says
> the server MUST return NOT_AUTHORIZED in this specific case, and 9.3
> doesn't mention THIRD_PARTY, so UNAUTH_THIRD_PARTY_INTERNAL_ADDRESS is
> only mentioned in this section.  Seriously, this scenario would seem
> to be covered under the following clause from NOT_AUTHORIZED: "the PCP
> client requested a mapping that cannot be fulfilled by the PCP
> server's security policy."
> 
> Paragraph break before "Determining which PCP clients are authorized
> to use the THIRD_PARTY option depends on the deployment scenario."
> 
>    For home deployments (where the PCP server is
>    embedded in the NAT device), this option MUST NOT be processed.
> 
> I would say "where the PCP server and the NAT are embedded in a home
> gateway device".  Also, THIRD_PARTY would typically not be implemented
> on a home gateway, so would generate UNSUPP_OPTION.
> 
>    It is RECOMMENDED that PCP servers embedded into customer premise
>    equipment be configured to refuse third party mappings by default.
>    With this default, if a user wants to create a third party mapping,
>    the user needs to interact out-of-band with their customer premise
>    router (e.g., using its HTTP administrative interface).
> 
> This is largely redundant to the previous paragraph.
> 
>    It is RECOMMENDED that PCP servers embedded into service provider
> NAT
>    and firewall devices be configured to permit the THIRD_PARTY
> option,...
> 
> This whole paragraph is confusing, and it's hard to tell what's
> actually being recommended or dis-recommended here.  The simple fact
> of the matter is that THIRD_PARTY is most useful in DS-Lite, where the
> NAT can send packets "directly" to internal hosts that don't embed a
> PCP client; i.e. the B4 embeds a UPnP IWF and/or a NAT-PMP IWF and/or
> a PCP-PCP proxy.
> 
> In a NAT444 scenario, the CGN can't "see" the internal hosts, so
> THIRD_PARTY is pointless.  In NAT64 and NAT46, there isn't an obvious
> place for an IWF or proxy, so it probably isn't useful there, although
> I haven't spent a lot of time thinking about it.
> 
>    If the packet arrived from a
>    different address, the PCP server MUST generate an
>    UNAUTH_THIRD_PARTY_INTERNAL_ADDRESS error.
> 
> s/arrived/arrives/
> 
> 10.2.  PREFER_FAILURE Option for MAP OpCodes
> 
>    This option is only used with the MAP4 and MAP6 OpCodes.
> 
> Since we redefined PEER to create or re-create mappings, we should
> also support PREFER_FAILURE, and should mention it here and in 11.3.1.
> 
> If UNAUTH_THIRD_PARTY_INTERNAL_ADDRESS is defined under the
> THIRD_PARTY Option (and I've argued that it shouldn't be defined at
> all), then CANNOT_PROVIDE_EXTERNAL_PORT should be defined under the
> PREFER_FAILURE Option.  Likewise EXCESSIVE_REMOTE_PEERS should be
> defined under the FILTER Option.  But really, I'd prefer to keep all
> the result codes in 8.2.
> 
> 10.3.  FILTER Option for MAP OpCodes
> 
>    This Option indicates filtering incoming packets is desired.  The
>    remote peer port and remote peer IP Address indicate the permitted
>    remote peer's source IP address and port for packets from the
>    Internet.
> 
> s/remote peer port/Remote Peer Port/
> s/remote peer IP Address/Remote Peer IP Address/
> 
> Change the "prefix-length" field name to "Prefix Length".
> 
> I've never been able to figure out why "Reserved" is the first field,
> not the second.
> 
> Note that FILTER is unidirectional - it doen't prevent an internal
> host from sending packets to any remote host, it just prevents remote
> hosts from replying.  I'm not saying this needs to be changed.
> 
>       is included in responses: MUST, if it appeared in the request
> 
> As previously noted, this field is not in the 5.3 boilerplate.
> In 5.3, we should say that, if a request includes an Option that is
> marked mandatory-to-process, the response (whether success or error)
> MUST include that Option.
> 
>       length: 2 if used with MAP4, 5 if used with MAP6
> 
> !! Wrong; this is the old length (measured in 4-byte words).
> Should be "8 if used with MAP4, 20 if used with MAP6".
> 
>    If a MAP request has a lifetime of 0 and contains the
>    FILTER option, the error MALFORMED_OPTION is returned.
> 
> This is an example of the nonsensical-option clause of 8.4.
> 
> 11.1.  Implementing MAP with non-EIM port-mapping NAPT
> 
>    For implicit dynamic mappings, some existing NAT devices have
>    endpoint-independent mapping (EIM) behavior while other NAPT devices
>    have non-endpoint-independent mapping (non-EIM) behavior.
> 
> Here you use NAT and NAPT in the same sentence.  As I said before, I
> would refer to all such devices by the vernacular "NAT", unless
> there's some clear distinction to be made by referring to NAPT.
> 
>    1.  have implicit dynamic mappings (e.g., TCP SYN) use a different
>    2.  on arrival of a packet (from the Internet or from an internal
> 
> Capitalize
> 
> BTW, I prefer the second approach, which uses the most specific match
> (somewhat analogously to kernel packet routing).  OTOH, I know Francis
> prefers the first approach.
> 
> As I see it, the conflict would only arise if there was an existing
> implicit mapping, and then an explicit mapping was created.  If the
> explicit mapping exists, the NAT will use it for all new connections
> from that internal addr/port/proto, rather than creating a new
> implicit mapping.
> 
> 11.2.  Interaction of MAP with Implicit Dynamic Mappings
> 
> I'm a bit confused by this one.  If the NAT creates an implicit
> mapping that conflicts with an explicit mapping, it's a different
> (more specific) mapping in the NAT's mapping table.  Even if the NAT
> deletes that mapping on termination of the connection, that won't
> affect the (more general) explicit mapping - it would still allow
> incoming connections.
> 
> 13.  Security Considerations
> 
>    This document defines Port Control Protocol and two types of
> OpCodes,
>    PEER and MAP.  The PEER OpCode allows querying and extending (if
>    permitted) the lifetime of an existing implicit dynamic mapping, so
> a
>    host can reduce its keepalive messages.  The MAP OpCode allows
>    creating a mapping so a host can receive incoming unsolicited
>    connections from the Internet in order to run a server.
> 
> This whole paragraph can be deleted, because it doesn't say anything
> new, and it doesn't say anything about security.
> 
> 14.1.  Port Number
> 
>    PCP will use port 5351 (currently assigned by IANA to NAT-PMP).  We
>    request that IANA re-assign that same port number to PCP, and
>    relinquish UDP port 44323.
> 
> The bit about relinquishing port 44323 should be marked for removal by
> the RFC Editor.
> 
> 14.2.  OpCodes
> 
>    Additional OpCodes in the range 4-95 can be created via Standards
>    Action [RFC5226], and the range 96-126 is for Private Use [RFC5226].
> 
> !! s/4/5/ (4 is PEER6)
> How/why was the number 95 chosen?
> 
> 14.3.  Result Codes
> 
>    IANA shall create a new registry for PCP result codes, numbered
>    0-255, initially populated with the result codes from Section 5.4,
>    Section 8.2, Section 10.3, and Section 10.1.  The values 0 and 255
>    are reserved.
> 
> 10.3 doesn't define a result code.
> 
>    Additional Result Codes can be defined via Specification Required
>    [RFC5226].
> 
> There needs to be a Private range for result codes, to support Private
> OpCodes and Options.
> 
> 14.4.  Options
> 
>    IANA shall create a new registry for PCP Options, numbered 0-255
> with
>    an associated mnemonic.  The values 0-127 are mandatory-to-process,
>    and 128-255 are optional-to-process.  The initial registry contains
>    the options described in Section 10 and Section 10.1.  The option
>    values 127 and 255 are reserved.
> 
> and sections 10.2 and 10.3 - why don't we just say section 10 (as a
> whole), and drop the reference to 10.1?
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp

