
From dwing@cisco.com  Mon Oct  3 12:33: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 6735D21F8E04 for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 12:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.956
X-Spam-Level: 
X-Spam-Status: No, score=-102.956 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aewye6H661sJ for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 12:33:47 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 0345921F8A56 for <pcp@ietf.org>; Mon,  3 Oct 2011 12:33:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=879; q=dns/txt; s=iport; t=1317670597; x=1318880197; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=Tnv4g4T8c9L5/FEIG0Rs//irlg4MkCOTa/duXjTDNWQ=; b=UyCHEj+2tC/O5NxFjTZ/9ztiyZu5x4br1Us4rLuW+mOFbKFYoZ6RWZe3 jGRYh/MMRJ5kHnWK3Oe+ZY21dPcQa+5s8oPDXFgVzEFT/R1tSn2dW/Sbl /hBORXph2kBeUy3ecaNw4vrnozs+o+z2QPMkQYaQGZrJ9TBb1RKyfzb82 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgAAIMOik6rRDoJ/2dsb2JhbABDmHCBa40ogQWBUwEBAQQICgEXED8MAQMCCQ8BAQQBAQEnBxkjCgkIAQEEARILF6JSAZ10hyEEh3edRw
X-IronPort-AV: E=Sophos;i="4.68,481,1312156800";  d="scan'208";a="5699583"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 03 Oct 2011 19:36:28 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p93JaRca003476; Mon, 3 Oct 2011 19:36:28 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <ext-felipe.m.costa@nokia.com>
References: Your message of Wed, 21 Sep 2011 16:27:11 -0000.	<0412136DF48FC94A9795E62ECFC014650DC4190A@008-AM1MPN1-026.mgdnok.nokia.com> <201109211737.p8LHbdJc046367@givry.fdupont.fr>
In-Reply-To: <201109211737.p8LHbdJc046367@givry.fdupont.fr>
Date: Mon, 3 Oct 2011 12:36:27 -0700
Message-ID: <01c301cc8203$be9dd7f0$3bd987d0$@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: Acx4hTFMozfQNHMPQPaRyZcIO5fLoAJfmbMQ
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] Mandatory OPTIONS
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, 03 Oct 2011 19:33:48 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Wednesday, September 21, 2011 10:38 AM
> To: ext-felipe.m.costa@nokia.com
> Cc: pcp@ietf.org
> Subject: Re: [pcp] Mandatory OPTIONS
> 
> 
>  In your previous mail you wrote:
> 
>    2.  Any Option which "Number" is higher than 128 is, by definition,
>    optional, while those which "Number" is smaller than 128 is, by
>    definition, mandatory?
> 
> => this one with "Code" in place of "Number" even it makes "opcode"
> a bit ambiguous...

I cleaned that up in the upcoming version by removing discussion
of the "O" bit, and instead just discussing the most significant
bit of the Option Code which indicates optional/mandatory.  Hopefully
that makes it clearer.  If not, suggestions to fix the text would
be appreciated.

-d



From dwing@cisco.com  Mon Oct  3 14:12:37 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 7553A21F8B5F for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 14:12:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.952
X-Spam-Level: 
X-Spam-Status: No, score=-102.952 tagged_above=-999 required=5 tests=[AWL=-0.353, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q35eslysO5zs for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 14:12:36 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 68B3921F8E0C for <pcp@ietf.org>; Mon,  3 Oct 2011 14:12:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1255; q=dns/txt; s=iport; t=1317676540; x=1318886140; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=zv7V9kdKwVU9dcK4LkvKtRUW8DRXVhDtJL0N8xOgcf4=; b=PZ/wFSZDh1gXgkLGsaK33xpcfScL0iodhHj+I5agYhQ5O83fKj93a5LH 7rDWORzfpgypelYXpfoQZ9yQGwSdp7kTEY9GhbEbYw6Cpf85Op0/gopQA cO+NKLo0p4505xrBel0fyx5eqphP+i6B1m0ncKsYgZCnhWB99K0kqpUVD M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgAANQkik6rRDoJ/2dsb2JhbABDmHCBa40ogQWBUwEBAQMBAQEBBQoBFxA0CwUHAQMCCQ8BAQQBAQEnBxkOFQoJCAEBBAESCxeHWQaaVgGdcQOHIQSHd51H
X-IronPort-AV: E=Sophos;i="4.68,481,1312156800";  d="scan'208";a="5702612"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 03 Oct 2011 21:15:39 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p93LFdNL027205; Mon, 3 Oct 2011 21:15:39 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <ext-felipe.m.costa@nokia.com>
References: Your message of Tue, 06 Sep 2011 21:27:46 -0000.	<0412136DF48FC94A9795E62ECFC0146503B89432@008-AM1MPN1-023.mgdnok.nokia.com> <201109070625.p876PW6d062850@givry.fdupont.fr>
In-Reply-To: <201109070625.p876PW6d062850@givry.fdupont.fr>
Date: Mon, 3 Oct 2011 14:15:39 -0700
Message-ID: <02d501cc8211$99f4e480$cddead80$@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: AcxtJvfFlmy6NdKtQ/2aLij6N8OxbQU6ow2A
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] Deleting mappings
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, 03 Oct 2011 21:12:37 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Tuesday, September 06, 2011 11:26 PM
> To: ext-felipe.m.costa@nokia.com
> Cc: pcp@ietf.org
> Subject: Re: [pcp] Deleting mappings
> 
> 
>  In your previous mail you wrote:
> 
> 
>    "- there was a discuss about implicit deletes, so current proposal
> is:
> 
>       * if we decide to provide implicit dynamic mapping deletion, it
> will be
>        by a PEER with lifetime zero
>    "
> 
> => and at the last IETF we decided to not provide a way to delete
> dynamic mapping as no use of this was found.
> 
>    So, my question is: does a MAP with lifetime = 0 delete any kind of
>    dynamic mappings (implicit and explicit) or just explicit dynamic
>    mappings?
> 
> => just explicit dynamic mappings and in particular *not* static
> mappings.

This should be clearer in the soon-to-be-published -14.

-d


> Thanks
> 
> Francis.Dupont@fdupont.fr
> 
> PS: as far as I know there is no text about the detailed
> behavior of a lifetime 0 PEER request...
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Mon Oct  3 14:18:09 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 6894E21F8CBF for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 14:18:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.948
X-Spam-Level: 
X-Spam-Status: No, score=-102.948 tagged_above=-999 required=5 tests=[AWL=-0.349, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohVnIN7FgdpD for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 14:18:08 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id E17B521F8CBE for <pcp@ietf.org>; Mon,  3 Oct 2011 14:18:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1742; q=dns/txt; s=iport; t=1317676872; x=1318886472; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=Lk0oIdE9s5Ab77IVv69GeZT9hMzY5RQK6HmUrqOe1wM=; b=DBIDR7e+vqM//vx1JgYHcGaOj7p+NqeFb54dwX9q3FcNo3Aiy8lBFWpK SNd6UeuVvSowCawOfC/KD/rsirRXUVj33l+iQMLO1KZnCVy2b0CEot7x7 LMsaPTm0tt46EqmP3A/sYpJ1BBOV4ngU71qhyXnBWqQcsl8n9j/ndmrPE E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgAAD8mik6rRDoG/2dsb2JhbABDmHCBa40ogQWBUwEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsXh1kGml4BnXEDhyEEh3edRw
X-IronPort-AV: E=Sophos;i="4.68,481,1312156800";  d="scan'208";a="5700639"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 03 Oct 2011 21:21:12 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p93LLC0d027803; Mon, 3 Oct 2011 21:21:12 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201109041532.p84FWdkW029805@givry.fdupont.fr>
In-Reply-To: <201109041532.p84FWdkW029805@givry.fdupont.fr>
Date: Mon, 3 Oct 2011 14:21:11 -0700
Message-ID: <02d601cc8212$6037beb0$20a73c10$@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: AcxrF/EUMa3dUcpGT86xMlqm1Ez+sQW+dj4Q
Content-Language: en-us
Subject: Re: [pcp] option overflow/truncated option
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, 03 Oct 2011 21:18:09 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Sunday, September 04, 2011 8:33 AM
> To: pcp@ietf.org
> Subject: [pcp] option overflow/truncated option
> 
> Another formal question about a case I could name truncated option
> or option overflow (BTW this alternative is a part of the question :-):
>  - a request includes an option with length N (so on 4*(N+1) octets)
>  - the request truncates the option to less than 4*(N+1) octets or
>   with other words the request parsing goes after the end of the
>   request when it deals with the option
>  - BTW it is not part of the option processing but before, i.e.,
>   the response should not depend on the particular truncated /
>   overflowing option
>  - there is a similar issue about option headers but the 4 octet
>   alignment constraint should make impossible to exercise the
>   corresponding check code (BTW this doesn't mean the check is
>   optional :-)
>  - we have the choice between MALFORMED_OPTION and MALFORMED_REQUEST,
>   in fact it is a matter of taste between the error is in the option
>   or the error is in the request, IMHO both are valid...

How is this:

        If an invalid option
        length is encountered (e.g., option length extends beyond the 
        length of the PCP OpCode itself), the error MALFORMED_OPTION SHOULD
        be returned (rather than MALFORMED_REQUEST), as that helps the
        client better understand how the packet was malformed.</t>

-d



> Thanks
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Mon Oct  3 14:22:03 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 436EE21F8B1F for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 14:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.944
X-Spam-Level: 
X-Spam-Status: No, score=-102.944 tagged_above=-999 required=5 tests=[AWL=-0.345, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dDjvLQtSd70Z for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 14:22:02 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 87BB321F8AB8 for <pcp@ietf.org>; Mon,  3 Oct 2011 14:22:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1281; q=dns/txt; s=iport; t=1317677106; x=1318886706; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=9Ba3W6hdUgC/yRbiD75G0BQHICQQquxh9FuU99Hq2pM=; b=SF4L1q+44c0zR6h+kwAuKAsVdfIPAQDAnDIIzenE7V0CZykz8tmjA4qV 05wLeQhXFPxGGwWl7TgJbZrq/7PRmpx02t+fQ3fyiHfPIBUotvUjkjxj7 qb5qZPwxbiSoXqi3b2yoYJjIBavOUS5obdwXMU6KUBq79DhIpEj6Qz+bx A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgAADgnik6rRDoH/2dsb2JhbABCmHCBa40ogQWBUwEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsXh1kGmlkBnXEDhyEEh3edRw
X-IronPort-AV: E=Sophos;i="4.68,481,1312156800";  d="scan'208";a="5719334"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 03 Oct 2011 21:25:05 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p93LP5JR024816; Mon, 3 Oct 2011 21:25:05 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201109041514.p84FEGf3028777@givry.fdupont.fr>
In-Reply-To: <201109041514.p84FEGf3028777@givry.fdupont.fr>
Date: Mon, 3 Oct 2011 14:25:05 -0700
Message-ID: <02d701cc8212$eb692320$c23b6960$@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: AcxrFVMgDSfv3gvISD65e84I0yx+hgW/Y9XQ
Content-Language: en-us
Subject: Re: [pcp] a question about the UNPROCESSED option
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, 03 Oct 2011 21:22:03 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Sunday, September 04, 2011 8:14 AM
> To: pcp@ietf.org
> Subject: [pcp] a question about the UNPROCESSED option
> 
> Still about conformance testing, I have no good idea about what to do
> with an UNPROCESSED option included in a PCP request:
>  - the only clear thing is this MUST raise an error
>  - there are 3 candidates:
>   * UNSUPP_OPTION but according to my previous message the next one
>    is better
>   * MALFORMED_OPTION seems to be the best candidate but perhaps the
>    next one is even better
>   * MALFORMED_REQUEST which means the request is plain wrong
>  - should we add an UNPROCESSED option? IMHO it should not add
>   an UNPROCESSED option for this reason, i.e., if there can be one
>   because and only because of another bad option

I added:

        The
        UNPROCESSED option MUST NOT appear in a request; if it does, it
        causes a MALFORMED_REQUEST error.

-d


> Thanks
> 
> Francis.Dupont@fdupont.fr
> 
> PS: of course this is at lowest priority...
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Mon Oct  3 14:37:00 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 DEA9521F8CF7 for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 14:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.941
X-Spam-Level: 
X-Spam-Status: No, score=-102.941 tagged_above=-999 required=5 tests=[AWL=-0.342, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k69iL-SMxd2m for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 14:37:00 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 4EB6521F8AAC for <pcp@ietf.org>; Mon,  3 Oct 2011 14:37:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3671; q=dns/txt; s=iport; t=1317678003; x=1318887603; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=l3lngSqkeKPsl/qsF1vSml59zjuZEOXiM0V1Ccme+Lc=; b=jImEVTSGohybxzzoe4uf+XZFR5X/XnNeSPMG2OdxmGPwqh3VdKayDZMj pMViJo0uSLvedo3vpnEIoJdPUhqxpEb5e0HJ/xUm1CuL7mMkuZKROQBSp QyR+xIcW6NUwWfFF6Wz/O9Zv5HnfXaFIoFFk1Ew4McinhTHEFi7bNNlNr I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgAAKYqik6rRDoG/2dsb2JhbABCmHCBa40ogQWBUwEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsXh1kGmlgBnXQDhyEEh3edRw
X-IronPort-AV: E=Sophos;i="4.68,481,1312156800";  d="scan'208";a="5703921"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 03 Oct 2011 21:40:03 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p93Le3Wu006363; Mon, 3 Oct 2011 21:40:03 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201108111309.p7BD9rsV020908@givry.fdupont.fr>
In-Reply-To: <201108111309.p7BD9rsV020908@givry.fdupont.fr>
Date: Mon, 3 Oct 2011 14:40:03 -0700
Message-ID: <02e401cc8215$0284e650$078eb2f0$@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: AcxYJ/hSTb2DbjfPR3qn105Qui8Qvwp6wEFQ
Content-Language: en-us
Subject: Re: [pcp] MAP4 vs MAP6 clarification
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, 03 Oct 2011 21:37:01 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, August 11, 2011 6:10 AM
> To: pcp@ietf.org
> Subject: [pcp] MAP4 vs MAP6 clarification
> 
> The base 13 spec is not very clear about the use of
> MAP4 vs MAP6 (and says nothing for PEER4 vs PEER6,
> one can just suppose the same logic applies).
> 
> There are only two places where one can find an
> indication:
>  - section 7 (not normative?) where the choice is
>   done according to client's listeners
>  - section 10.3 (FILTER option) as nearly a side effect.
> 
> IMHO the addresses involved in PCP can be classified into:
>  - source addresses (mainly the client's address in the
>   common header)
> 
>  - internal addresses
> 
>  - external addresses
> 
>  - remote peer addresses
> 
> It seems the current spec uses the last class (remote peer
> addresses) for opcode4 vs opcode6 but:
>  - this is far to be very clear
>  - this information is redundant with the base 13 address
>   encoding (i.e., IPv4 mapped IPv6 addresses)
> So IMHO we have two choices:
>  - merge MAP4 and MAP6 (and PEER4 with PEER6)

Version -14 will combine MAP4 and MAP6 into MAP, and will
combine PEER4 and PEER6 into PEER.  To indicate which sort
of external address is desired, the requested-external-address
field will be all-zeros (indicating IPv6 is desired) or 
::FFFF:0:0 (indicating IPv4 is desired).


>  - attach the opcode version to the remote peer one
>   and make inconsistent requests malformed
> 
> BTW it should be fine to have a table with the IP version
> to use for the 4 classes in function of the kind of device
> controlled by the PCP server, i.e.:
> 
> IPv4 firewall:
>  source, internal, external, remote: v4
> 
> IPv6 firewall:
>  source, internal, external, remote: v6
> 
> DS-Lite plain mode:
>  source: v6
>  internal, external, remote: v4
> 
> DS-Lite encapsulation mode:
>  source, internal, external, remote: v4
> 
> ?NAT64:
>  source, internal: v6
>  external, remote: v4
> 
> ?NAT46:
>  source, internal: v4
>  external, remote: v6
> 
> NAT444 (both home gateway and CGN):
>  source, internal, external, remote: v4

Yes, seems we need to have such a table.  How is this:

   The following table summarizes how various common PCP deployments use
   IPv6 and IPv4 addresses:

                               source  internal  external  remote peer
          IPv4 firewall:        IPv4     IPv4      IPv4       IPv4
          IPv6 firewall:        IPv6     IPv6      IPv6       IPv6
          NAT44:                IPv4     IPv4      IPv4       IPv4
          DS-Lite plain mode:   IPv6     IPv4      IPv4       IPv4
          DS-Lite encap. mode:  IPv4     IPv4      IPv4       IPv4
          NAT64:                IPv6     IPv6      IPv4       IPv6
          NAT46:                IPv4     IPv4      IPv6       IPv4
          NPTv6:                IPv6     IPv6      IPv6       IPv6

               Figure 6: Address Families with MAP and PEER

   The last two seem counter-intuitive, but the PCP client is not
   necessarily aware of the actual IP address of the remote peer -- so
   it expresses the IP address from its perspective (a PCP client using
   NAT64 only knows of IPv6 peers, so it uses IPv6 to represent its
   peer; similarly, a PCP client using NAT46 only knows of IPv4 peers,
   so it uses IPv4 to represent its peer).

-d


> Regards
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From Tina.Tsou.Zouting@huawei.com  Mon Oct  3 17:55:40 2011
Return-Path: <Tina.Tsou.Zouting@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 5690A21F8EAC for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 17:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.29
X-Spam-Level: 
X-Spam-Status: No, score=-6.29 tagged_above=-999 required=5 tests=[AWL=0.309,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnJ71zSzVvF1 for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 17:55:39 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id EDA6321F8EA9 for <pcp@ietf.org>; Mon,  3 Oct 2011 17:55:36 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSI00CVOO1QIB@szxga03-in.huawei.com> for pcp@ietf.org; Tue, 04 Oct 2011 08:58:38 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSI00CUXO1QPG@szxga03-in.huawei.com> for pcp@ietf.org; Tue, 04 Oct 2011 08:58:38 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEA82422; Tue, 04 Oct 2011 08:58:37 +0800
Received: from SZXEML407-HUB.china.huawei.com (10.82.67.94) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 04 Oct 2011 08:58:35 +0800
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.147]) by szxeml407-hub.china.huawei.com ([10.82.67.94]) with mapi id 14.01.0270.001; Tue, 04 Oct 2011 08:58:27 +0800
Date: Tue, 04 Oct 2011 00:58:27 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <02e401cc8215$0284e650$078eb2f0$@com>
X-Originating-IP: [10.193.34.158]
To: Dan Wing <dwing@cisco.com>, 'Francis Dupont' <Francis.Dupont@fdupont.fr>,  "pcp@ietf.org" <pcp@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A88DC806@szxeml526-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: [pcp] MAP4 vs MAP6 clarification
Thread-index: AcxYJ/hSTb2DbjfPR3qn105Qui8Qvwp6wEFQAAdjpxA=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <201108111309.p7BD9rsV020908@givry.fdupont.fr> <02e401cc8215$0284e650$078eb2f0$@com>
Subject: Re: [pcp] MAP4 vs MAP6 clarification
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, 04 Oct 2011 00:55:40 -0000

Dan,
In line...



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


-----Original Message-----
From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Dan Wing
Sent: Monday, October 03, 2011 2:40 PM
To: 'Francis Dupont'; pcp@ietf.org
Subject: Re: [pcp] MAP4 vs MAP6 clarification

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, August 11, 2011 6:10 AM
> To: pcp@ietf.org
> Subject: [pcp] MAP4 vs MAP6 clarification
> 
> The base 13 spec is not very clear about the use of
> MAP4 vs MAP6 (and says nothing for PEER4 vs PEER6,
> one can just suppose the same logic applies).
> 
> There are only two places where one can find an
> indication:
>  - section 7 (not normative?) where the choice is
>   done according to client's listeners
>  - section 10.3 (FILTER option) as nearly a side effect.
> 
> IMHO the addresses involved in PCP can be classified into:
>  - source addresses (mainly the client's address in the
>   common header)
> 
>  - internal addresses
> 
>  - external addresses
> 
>  - remote peer addresses
> 
> It seems the current spec uses the last class (remote peer
> addresses) for opcode4 vs opcode6 but:
>  - this is far to be very clear
>  - this information is redundant with the base 13 address
>   encoding (i.e., IPv4 mapped IPv6 addresses)
> So IMHO we have two choices:
>  - merge MAP4 and MAP6 (and PEER4 with PEER6)

Version -14 will combine MAP4 and MAP6 into MAP, and will
combine PEER4 and PEER6 into PEER.  To indicate which sort
of external address is desired, the requested-external-address
field will be all-zeros (indicating IPv6 is desired) or 
::FFFF:0:0 (indicating IPv4 is desired).


>  - attach the opcode version to the remote peer one
>   and make inconsistent requests malformed
> 
> BTW it should be fine to have a table with the IP version
> to use for the 4 classes in function of the kind of device
> controlled by the PCP server, i.e.:
> 
> IPv4 firewall:
>  source, internal, external, remote: v4
> 
> IPv6 firewall:
>  source, internal, external, remote: v6
> 
> DS-Lite plain mode:
>  source: v6
>  internal, external, remote: v4
> 
> DS-Lite encapsulation mode:
>  source, internal, external, remote: v4
> 
> ?NAT64:
>  source, internal: v6
>  external, remote: v4
> 
> ?NAT46:
>  source, internal: v4
>  external, remote: v6
> 
> NAT444 (both home gateway and CGN):
>  source, internal, external, remote: v4

Yes, seems we need to have such a table.  How is this:

   The following table summarizes how various common PCP deployments use
   IPv6 and IPv4 addresses:

                               source  internal  external  remote peer
          IPv4 firewall:        IPv4     IPv4      IPv4       IPv4
          IPv6 firewall:        IPv6     IPv6      IPv6       IPv6
          NAT44:                IPv4     IPv4      IPv4       IPv4
          DS-Lite plain mode:   IPv6     IPv4      IPv4       IPv4
          DS-Lite encap. mode:  IPv4     IPv4      IPv4       IPv4
          NAT64:                IPv6     IPv6      IPv4       IPv6
          NAT46:                IPv4     IPv4      IPv6       IPv4
          NPTv6:                IPv6     IPv6      IPv6       IPv6

               Figure 6: Address Families with MAP and PEER

   The last two seem counter-intuitive, but the PCP client is not
   necessarily aware of the actual IP address of the remote peer -- so
   it expresses the IP address from its perspective (a PCP client using
   NAT64 only knows of IPv6 peers, so it uses IPv6 to represent its
   peer; similarly, a PCP client using NAT46 only knows of IPv4 peers,
   so it uses IPv4 to represent its peer).


[TT] We need some texts to explain the last two rows, with * notes, maybe.

-d


> Regards
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp

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

From dwing@cisco.com  Mon Oct  3 18:09:26 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 627C121F8EB6 for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 18:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSGtSBwtVNAA for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 18:09:25 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 09F3121F8C87 for <pcp@ietf.org>; Mon,  3 Oct 2011 18:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1641; q=dns/txt; s=iport; t=1317690749; x=1318900349; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=dVC93A3z5xWkUbqZ1+Y9H7FtvxzRG2JSFvAtjYiGMGI=; b=RYmWgThss1yUoPnQostAvyXY9bEmItx6pnHMlWHZ8oi+hIezTaGeqnmK pExMjv/EmcK8gLbb1tcJBHXgBGtHhFwzpFNyqHjU6iqvr75wpOVEjcp7P i4qgIlGvoQ10UBcBXoB8FkvCO9OU0C35cLPm/O+VpPkLL3uer7uiAOxcP g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFABpdik6tJV2a/2dsb2JhbABCmlyNJoEFgVMBAQEBAgEICgEXEEQIAwIJDzcZIxsBAQQBHReHWZozAZ17hyEEh3edSg
X-IronPort-AV: E=Sophos;i="4.68,482,1312156800"; d="scan'208";a="25797755"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP; 04 Oct 2011 01:12:27 +0000
Received: from dwingWS ([10.32.240.196]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p941CRs2032251;  Tue, 4 Oct 2011 01:12:27 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Tina TSOU'" <Tina.Tsou.Zouting@huawei.com>, "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201108111309.p7BD9rsV020908@givry.fdupont.fr> <02e401cc8215$0284e650$078eb2f0$@com> <C0E0A32284495243BDE0AC8A066631A88DC806@szxeml526-mbs.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A88DC806@szxeml526-mbs.china.huawei.com>
Date: Mon, 3 Oct 2011 18:12:26 -0700
Message-ID: <03fe01cc8232$ae94e130$0bbea390$@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: AcxYJ/hSTb2DbjfPR3qn105Qui8Qvwp6wEFQAAdjpxAAAHAeYA==
Content-Language: en-us
Subject: Re: [pcp] MAP4 vs MAP6 clarification
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, 04 Oct 2011 01:09:26 -0000

> Yes, seems we need to have such a table.  How is this:
> 
>    The following table summarizes how various common PCP deployments
> use
>    IPv6 and IPv4 addresses:
> 
>                                source  internal  external  remote peer
>           IPv4 firewall:        IPv4     IPv4      IPv4       IPv4
>           IPv6 firewall:        IPv6     IPv6      IPv6       IPv6
>           NAT44:                IPv4     IPv4      IPv4       IPv4
>           DS-Lite plain mode:   IPv6     IPv4      IPv4       IPv4
>           DS-Lite encap. mode:  IPv4     IPv4      IPv4       IPv4
>           NAT64:                IPv6     IPv6      IPv4       IPv6
>           NAT46:                IPv4     IPv4      IPv6       IPv4
>           NPTv6:                IPv6     IPv6      IPv6       IPv6
> 
>                Figure 6: Address Families with MAP and PEER
> 
>    The last two seem counter-intuitive, but the PCP client is not
>    necessarily aware of the actual IP address of the remote peer -- so
>    it expresses the IP address from its perspective (a PCP client using
>    NAT64 only knows of IPv6 peers, so it uses IPv6 to represent its
>    peer; similarly, a PCP client using NAT46 only knows of IPv4 peers,
>    so it uses IPv4 to represent its peer).
> 
> 
> [TT] We need some texts to explain the last two rows, with * notes,
> maybe.

NPTv6 is cited earlier in the document as RFC6296.

I will remove NAT46; a table isn't where to discuss it, and I see
we don't have it in the Scope section, either.  NAT46 is also not
common (which was the justification to discuss it in the table).

-d



From Tina.Tsou.Zouting@huawei.com  Mon Oct  3 18:12:51 2011
Return-Path: <Tina.Tsou.Zouting@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 71D8D21F8D17 for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 18:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.293
X-Spam-Level: 
X-Spam-Status: No, score=-6.293 tagged_above=-999 required=5 tests=[AWL=0.306,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j++KKFMtsvv7 for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 18:12:50 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 57E8221F8CD6 for <pcp@ietf.org>; Mon,  3 Oct 2011 18:12:44 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSI0073HOUAZP@szxga05-in.huawei.com> for pcp@ietf.org; Tue, 04 Oct 2011 09:15:47 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSI00B33OUA47@szxga05-in.huawei.com> for pcp@ietf.org; Tue, 04 Oct 2011 09:15:46 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEA82669; Tue, 04 Oct 2011 09:15:44 +0800
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 04 Oct 2011 09:15:42 +0800
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.147]) by szxeml409-hub.china.huawei.com ([10.82.67.136]) with mapi id 14.01.0270.001; Tue, 04 Oct 2011 09:15:39 +0800
Date: Tue, 04 Oct 2011 01:15:37 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <03fe01cc8232$ae94e130$0bbea390$@com>
X-Originating-IP: [10.193.34.158]
To: Dan Wing <dwing@cisco.com>, 'Francis Dupont' <Francis.Dupont@fdupont.fr>,  "pcp@ietf.org" <pcp@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A88DC85C@szxeml526-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: [pcp] MAP4 vs MAP6 clarification
Thread-index: AcxYJ/hSTb2DbjfPR3qn105Qui8Qvwp6wEFQAAdjpxAAAHAeYAAAKlzQ
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <201108111309.p7BD9rsV020908@givry.fdupont.fr> <02e401cc8215$0284e650$078eb2f0$@com> <C0E0A32284495243BDE0AC8A066631A88DC806@szxeml526-mbs.china.huawei.com> <03fe01cc8232$ae94e130$0bbea390$@com>
Subject: Re: [pcp] MAP4 vs MAP6 clarification
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, 04 Oct 2011 01:12:51 -0000

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


-----Original Message-----
From: Dan Wing [mailto:dwing@cisco.com] 
Sent: Monday, October 03, 2011 6:12 PM
To: Tina TSOU; 'Francis Dupont'; pcp@ietf.org
Subject: RE: [pcp] MAP4 vs MAP6 clarification

> Yes, seems we need to have such a table.  How is this:
> 
>    The following table summarizes how various common PCP deployments
> use
>    IPv6 and IPv4 addresses:
> 
>                                source  internal  external  remote peer
>           IPv4 firewall:        IPv4     IPv4      IPv4       IPv4
>           IPv6 firewall:        IPv6     IPv6      IPv6       IPv6
>           NAT44:                IPv4     IPv4      IPv4       IPv4
>           DS-Lite plain mode:   IPv6     IPv4      IPv4       IPv4
>           DS-Lite encap. mode:  IPv4     IPv4      IPv4       IPv4
>           NAT64:                IPv6     IPv6      IPv4       IPv6
>           NAT46:                IPv4     IPv4      IPv6       IPv4
>           NPTv6:                IPv6     IPv6      IPv6       IPv6
> 
>                Figure 6: Address Families with MAP and PEER
> 
>    The last two seem counter-intuitive, but the PCP client is not
>    necessarily aware of the actual IP address of the remote peer -- so
>    it expresses the IP address from its perspective (a PCP client using
>    NAT64 only knows of IPv6 peers, so it uses IPv6 to represent its
>    peer; similarly, a PCP client using NAT46 only knows of IPv4 peers,
>    so it uses IPv4 to represent its peer).
> 
> 
> [TT] We need some texts to explain the last two rows, with * notes,
> maybe.

NPTv6 is cited earlier in the document as RFC6296.

I will remove NAT46; a table isn't where to discuss it, and I see
we don't have it in the Scope section, either.  NAT46 is also not
common (which was the justification to discuss it in the table).
[TT] NAT46 is not common, but necessary, think about the story of PNAT. 

-d



From dwing@cisco.com  Mon Oct  3 18:30:55 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 6E2B421F8DC0 for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 18:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.937
X-Spam-Level: 
X-Spam-Status: No, score=-102.937 tagged_above=-999 required=5 tests=[AWL=-0.338, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jR+pYwjkH9zp for <pcp@ietfa.amsl.com>; Mon,  3 Oct 2011 18:30:54 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id EF32821F8DB4 for <pcp@ietf.org>; Mon,  3 Oct 2011 18:30:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2744; q=dns/txt; s=iport; t=1317692035; x=1318901635; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=i4LgfuvfcFl/5zZLemh+oZ/FT0LBIvrFc4zvsznGYyk=; b=JEAKFeVvbgqg7hxdWEQAV44pQU10TS+Way6ptMzb7Tug8de6bVSJQTA7 GBi6Ugvzem3Vy4hMMtF9f+azuWnAKjDIkRkY/Z6ajyebnzrZcdFgEobeQ TQDq4TQb1GItpp2woZOw63nCMcFZwe07DPpRbqCEy8uj7mFxsOeuQ73/8 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ar4AAN9hik6rRDoH/2dsb2JhbABCmHGBa40ngQWBUwEBAQEDCAoBFxBLAQMCCQ8BAQQBASgHGSMKCQgBAQQBEgsXh1+aPwGdfIchBId3nUo
X-IronPort-AV: E=Sophos;i="4.68,482,1312156800";  d="scan'208";a="5735501"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 04 Oct 2011 01:33:54 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p941XsGo004408; Tue, 4 Oct 2011 01:33:54 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Tina TSOU'" <Tina.Tsou.Zouting@huawei.com>, "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201108111309.p7BD9rsV020908@givry.fdupont.fr> <02e401cc8215$0284e650$078eb2f0$@com> <C0E0A32284495243BDE0AC8A066631A88DC806@szxeml526-mbs.china.huawei.com> <03fe01cc8232$ae94e130$0bbea390$@com> <C0E0A32284495243BDE0AC8A066631A88DC85C@szxeml526-mbs.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A88DC85C@szxeml526-mbs.china.huawei.com>
Date: Mon, 3 Oct 2011 18:33:54 -0700
Message-ID: <041201cc8235$adb9bc10$092d3430$@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: AcxYJ/hSTb2DbjfPR3qn105Qui8Qvwp6wEFQAAdjpxAAAHAeYAAAKlzQAACd17A=
Content-Language: en-us
Subject: Re: [pcp] MAP4 vs MAP6 clarification
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, 04 Oct 2011 01:30:55 -0000

> -----Original Message-----
> From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
> Sent: Monday, October 03, 2011 6:16 PM
> To: Dan Wing; 'Francis Dupont'; pcp@ietf.org
> Subject: RE: [pcp] MAP4 vs MAP6 clarification
> 
> 
> 
> 
> 
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
> 
> 
> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Monday, October 03, 2011 6:12 PM
> To: Tina TSOU; 'Francis Dupont'; pcp@ietf.org
> Subject: RE: [pcp] MAP4 vs MAP6 clarification
> 
> > Yes, seems we need to have such a table.  How is this:
> >
> >    The following table summarizes how various common PCP deployments
> > use
> >    IPv6 and IPv4 addresses:
> >
> >                                source  internal  external  remote
> peer
> >           IPv4 firewall:        IPv4     IPv4      IPv4       IPv4
> >           IPv6 firewall:        IPv6     IPv6      IPv6       IPv6
> >           NAT44:                IPv4     IPv4      IPv4       IPv4
> >           DS-Lite plain mode:   IPv6     IPv4      IPv4       IPv4
> >           DS-Lite encap. mode:  IPv4     IPv4      IPv4       IPv4
> >           NAT64:                IPv6     IPv6      IPv4       IPv6
> >           NAT46:                IPv4     IPv4      IPv6       IPv4
> >           NPTv6:                IPv6     IPv6      IPv6       IPv6
> >
> >                Figure 6: Address Families with MAP and PEER
> >
> >    The last two seem counter-intuitive, but the PCP client is not
> >    necessarily aware of the actual IP address of the remote peer --
> so
> >    it expresses the IP address from its perspective (a PCP client
> using
> >    NAT64 only knows of IPv6 peers, so it uses IPv6 to represent its
> >    peer; similarly, a PCP client using NAT46 only knows of IPv4
> peers,
> >    so it uses IPv4 to represent its peer).
> >
> >
> > [TT] We need some texts to explain the last two rows, with * notes,
> > maybe.
> 
> NPTv6 is cited earlier in the document as RFC6296.
> 
> I will remove NAT46; a table isn't where to discuss it, and I see
> we don't have it in the Scope section, either.  NAT46 is also not
> common (which was the justification to discuss it in the table).
> [TT] NAT46 is not common, but necessary, think about the story of PNAT.

I am trying to constrain the scope of PCP so we can finish the
base specification.

How would PCP work in a PNAT environment?  Is the application 
(which "can't" be upgraded to IPv6) going to start speaking PCP
over IPv4, or over IPv6?  The answers are not obvious to me,
and unless there are clear answers I don't see how to close on
this quickly and keep the base PCP specification moving forward.

-d



From Francis.Dupont@fdupont.fr  Tue Oct  4 00:40:30 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 583FB21F8CC8 for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 00:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nyrxrFIT1xHg for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 00:40:29 -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 6A99B21F8C14 for <pcp@ietf.org>; Tue,  4 Oct 2011 00:40:29 -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 p947hUOK047731; Tue, 4 Oct 2011 09:43:30 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110040743.p947hUOK047731@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Mon, 03 Oct 2011 14:21:11 PDT. <02d601cc8212$6037beb0$20a73c10$@com> 
Date: Tue, 04 Oct 2011 09:43:30 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] option overflow/truncated option
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, 04 Oct 2011 07:40:30 -0000

 In your previous mail you wrote:

   How is this:
   
           If an invalid option
           length is encountered (e.g., option length extends beyond the 
           length of the PCP OpCode itself), the error MALFORMED_OPTION SHOULD
           be returned (rather than MALFORMED_REQUEST), as that helps the
           client better understand how the packet was malformed.</t>
   
=> fine with this, thanks!

Francis.Dupont@fdupont.fr

From jhw@apple.com  Tue Oct  4 13:58:55 2011
Return-Path: <jhw@apple.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 63DD221F8E24 for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 13:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.319
X-Spam-Level: 
X-Spam-Status: No, score=-106.319 tagged_above=-999 required=5 tests=[AWL=-0.320, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDlKHc-6X0HE for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 13:58:55 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id ED9CB21F8E22 for <pcp@ietf.org>; Tue,  4 Oct 2011 13:58:54 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LSK0079E79B87H2@mail-out.apple.com> for pcp@ietf.org; Tue, 04 Oct 2011 14:01:55 -0700 (PDT)
X-AuditID: 1180711d-b7b16ae000004efb-6d-4e8b737929ef
Received: from ba0301b-dhcp202.apple.com (ba0301b-dhcp202.apple.com [17.193.15.202]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 43.12.20219.9737B8E4; Tue, 04 Oct 2011 13:58:33 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com>
Date: Tue, 04 Oct 2011 14:01:55 -0700
Message-id: <56369024-31BD-4973-9799-012C490BBB02@apple.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com>
To: PCP <pcp@ietf.org>
X-Mailer: Apple Mail (2.1400)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjluLIzCtJLcpLzFFi42IRPMh/SreyuNvPYHO7hsXkY79ZHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMffzS6aCF2wVU6+cZW1g3MLaxcjJISFgInH6bQ8ThC0mceHe erYuRi4OIYFVTBJvlqwDK2IW0JK48e8lWBGvgKHEvZ8TGEFsYQFViTNHm1hAbDYBFYlvl++C 1XAK2Ep0nOgE62UBij9qfMwMMUdbYtnC18wQc2wkDl1fAVYjBGRvO9gN1isCdMTqxw+hDpKV 2PDsNvsERr5ZSM6YheSMWUjGLmBkXsUoWJSak1hpaKyXWFCQk6qXnJ+7iREUSg2FsjsY9//k P8QowMGoxMP7w7vbT4g1say4MvcQowQHs5II7+YPXX5CvCmJlVWpRfnxRaU5qcWHGKU5WJTE eX9/bPETEkhPLEnNTk0tSC2CyTJxcEo1MM6VslzdIuq/Y1Ops6yhaHPN+7v8IneqVKrvWa62 vj6LK3GPfGD8hjUvIt+qHPfgXxC78l7OxA0hYcd0v/8/3C6UvOLNjbO2OTuTJr9WFF3eVnNh O0udi75jec5K88cbuM4vm8G9pyuvnpPHPuNx4TlmISG3I1+5lypfqM3gu1r8NHr5iefW1kos xRmJhlrMRcWJABDAaMghAgAA
Subject: Re: [pcp] PCP and simple firewalls
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, 04 Oct 2011 20:58:55 -0000

everyone--

I've recently been reminded of a message I sent back in July to this working group, and so far as I can tell, it received no response from the working group.

  <http://www.ietf.org/mail-archive/web/pcp/current/msg01436.html>

I still believe these concerns are serious and merit more attention than they have so far received from the working group, especially since V6OPS is now in the process of revising RFC 6204 and there is a move to make an explicit recommendation to use PCP in IPv6 residential gateway devices.

As the -13 revision of the draft remains the most recent published edition, my previous message to the list on the topic, cited above, should still be relevant.  Could the working group PLEASE engage on this?



--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From dwing@cisco.com  Tue Oct  4 16:42:52 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 DE00D21F8BDC for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 16:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.634
X-Spam-Level: 
X-Spam-Status: No, score=-102.634 tagged_above=-999 required=5 tests=[AWL=-0.635, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NAxSmJX6tLx5 for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 16:42:52 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 08ABE21F8BB6 for <pcp@ietf.org>; Tue,  4 Oct 2011 16:42:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3404; q=dns/txt; s=iport; t=1317771958; x=1318981558; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=6WtrViNpf6xt+amjQai1OfyJiZyZ59bG6765XXMSL2g=; b=RVnc3SDuGa35ce09JyCBACN1MbPh3bUm4hCZQRS4Pt0a6Gdfl6L+aq+q oNR+Fx2yjQpqvI2IxZoAxoS06nbINQup2jIxe50Lws8mYHHj6q+PvQoA4 8IUMr9Eg6gwath0lxIQmM9okBVIXN/lC4d/bm3PC2un2v8H2YQgHdIM9J o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArwAAIOZi06rRDoI/2dsb2JhbABCmHeBa40pgQWBUwEBAQEDAQEBBQoBFxA0FwEDAgkPAgQBASgHGQ4VCgkIAQEEARIJAheHYZlbAZ1shyMEh3idUA
X-IronPort-AV: E=Sophos;i="4.68,488,1312156800";  d="scan'208";a="5972855"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 04 Oct 2011 23:45:58 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p94NjwKp031147; Tue, 4 Oct 2011 23:45:58 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'james woodyatt'" <jhw@apple.com>, "'PCP'" <pcp@ietf.org>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com>
In-Reply-To: <56369024-31BD-4973-9799-012C490BBB02@apple.com>
Date: Tue, 4 Oct 2011 16:45:58 -0700
Message-ID: <084c01cc82ef$c43edaf0$4cbc90d0$@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: AcyC2N7VKSmQcbuwQMaI0Zmj9jEWBgAEvrqw
Content-Language: en-us
Subject: Re: [pcp] PCP and simple firewalls
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, 04 Oct 2011 23:42:53 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> james woodyatt
> Sent: Tuesday, October 04, 2011 2:02 PM
> To: PCP
> Subject: Re: [pcp] PCP and simple firewalls
> 
> everyone--
> 
> I've recently been reminded of a message I sent back in July to this
> working group, and so far as I can tell, it received no response from
> the working group.
> 
>   <http://www.ietf.org/mail-archive/web/pcp/current/msg01436.html>
> 
> I still believe these concerns are serious and merit more attention
> than they have so far received from the working group, especially since
> V6OPS is now in the process of revising RFC 6204 and there is a move to
> make an explicit recommendation to use PCP in IPv6 residential gateway
> devices.
> 
> As the -13 revision of the draft remains the most recent published
> edition, my previous message to the list on the topic, cited above,
> should still be relevant.  Could the working group PLEASE engage on
> this?

Thanks for the reminder -- that one had slipped off my list.  I agree
it is important, and is something in PCP's scope.


Here is the new text in that same section you quoted above:

2.2.  Supported Protocols

   The PCP Opcodes defined in this document are designed to support
   transport-layer protocols that use a 16-bit port number (e.g., TCP,
   UDP, SCTP, DCCP).  Protocols that do not use a port number (e.g.,
   RSVP, IPsec ESP, ICMP, ICMPv6) are supported for IPv4 firewall, IPv6 
   firewall, and NPTv6 functions, but are out of scope for any NAT 
   functions.  A future document may describe how PCP can create NAT 
   mappings for such protocols.  Also out of scope is using PCP to 
   request forwarding of all traffic to a single default host (often 
   nicknamed a "DMZ").

Let me know if that is acceptable.


In the 'generating MAP request' section, I added:

   If the Protocol does not use 16-bit port numbers (e.g., RSVP), the
   port number MUST be 0.


In the 'processing MAP request' section, I adjusted the relevant
paragraph to allow port=0 if the Protocol 

        If the requested lifetime is non-zero, it indicates a
        request to create a mapping or extend the lifetime of an
        existing mapping.  If the PCP server or PCP-controlled device
        does not support the Protocol or cannot create a mapping for
        the Protocol (e.g., because the request is for a NAT mapping
        instead of a firewall mapping and the PCP-controlled device is
        not a NAT or does not support NATting that specific Protocol),
        it MUST generate an UNSUPP_PROTOCOL error.  If the Protocol is
        supported and the Internal Port is zero but the protocol uses
        a 16 bit port number (e.g., TCP, SCTP), it generates a
        MALFORMED_REQUEST error.  If the Protocol is supported and
        does not use 16 bit port number (e.g., RSVP), the Internal
        Port and the Requested External Port are ignored, but are
        copied into the response.


I don't believe we need similar support for PEER.  Let me know if
I'm wrong.

-d

> 
> 
> 
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, core os networking
> 
> 
> 
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From jhw@apple.com  Tue Oct  4 17:27:47 2011
Return-Path: <jhw@apple.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 4949721F8CCD for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 17:27:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.61
X-Spam-Level: 
X-Spam-Status: No, score=-106.61 tagged_above=-999 required=5 tests=[AWL=-0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GPj6HDmUs8qb for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 17:27:46 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1A15321F8CC9 for <pcp@ietf.org>; Tue,  4 Oct 2011 17:27:31 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LSK0050MHD3J0C0@mail-out.apple.com> for pcp@ietf.org; Tue, 04 Oct 2011 17:30:37 -0700 (PDT)
X-AuditID: 1180711d-b7b16ae000004efb-1e-4e8ba4625624
Received: from ba0301b-dhcp202.apple.com (ba0301b-dhcp202.apple.com [17.193.15.202]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 8B.CB.20219.364AB8E4; Tue, 04 Oct 2011 17:27:15 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <084c01cc82ef$c43edaf0$4cbc90d0$@com>
Date: Tue, 04 Oct 2011 17:30:36 -0700
Message-id: <004427B5-438A-4CB4-AD2E-0758BF2ECBA2@apple.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <084c01cc82ef$c43edaf0$4cbc90d0$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1400)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUieJD/lG7ykm4/g987mS0uXnvIZDH52G9W ByaPKb83snosWfKTKYApissmJTUnsyy1SN8ugSvj5NrjzAW7uCpWX9nK1sC4kaOLkZNDQsBE 4t35LlYIW0ziwr31bCC2kMAqJon7Z3lBbGEBbYmJzRuZQGxeAUOJez8nMILYzAJaEjf+vQSL swmoSHy7fBfM5hQwkphz6xQziM0CFF/y4jA7RL2ExMKGf1C2tsSyha+ZIWbaSGxqms3SxcgF tHcyo0Tnsg6wg0QE5CTuzp/ADHGcrMSGZ7fZJzDyz0Jyxywkd8xCMncBI/MqRsGi1JzESkNj vcSCgpxUveT83E2MoLBrKJTdwbj/J/8hRgEORiUe3h/e3X5CrIllxZW5hxglOJiVRHg3f+jy E+JNSaysSi3Kjy8qzUktPsQozcGiJM77+2OLn5BAemJJanZqakFqEUyWiYNTqoFx9mtzrsU6 bhJe800dX07ZUN/fzmDzXmX3qb89kYLbvH/mHWeb2lZlV/hJ4scTweLPaa+vvmI/2uq3W/DX XrHZsqu7Nt3xWeansPfKknc7koT5pTac0715xibeUfyL83GhvBnOWxTZZliUaV0XiGX6Z8ax r+vvjSvN7/boJXPcuBb5XOBBxr1kJZbijERDLeai4kQAf3BySTcCAAA=
Cc: 'PCP' <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 05 Oct 2011 00:27:47 -0000

On Oct 4, 2011, at 4:45 PM, Dan Wing wrote:
> 
> Let me know if that is acceptable.

I still have two major objections.

p1. I still don't see anything that permits an IPv6 host to request a MAP for the entire upper layer protocol number space from a simple non-translating or 1:1 NPTv6 firewall.  I suggest permitting protocol zero, HOPOPT, to stand as a wildcard for all upper layer protocols when creating a mapping as well as when deleting mappings.

p2. I still don't see any informative references to RFC 6092 or text that offers guidance to implementors of RFC 6092-conformant residential gateways regarding its exceptions to the default denial policy for IKE and IPsec AH/ESP in simple firewalls.  I suggest adding some text to the "Mapping Types" entry in the Terminology section that cites RFC 6092 and describes an additional mapping type: the 'conventional' mapping, which are always applied as a matter of convention or even future standards action.  If the term 'conventional mapping' is used, then section 8 [and everywhere else that mentions static mappings] will need to be revised to discuss how conventional mappings are handled differently or the same as static mappings.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From dthaler@microsoft.com  Tue Oct  4 17:30:58 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 1E08121F8E02 for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 17:30:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.235
X-Spam-Level: 
X-Spam-Status: No, score=-110.235 tagged_above=-999 required=5 tests=[AWL=-0.236, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exdgPIsuSoh1 for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 17:30:57 -0700 (PDT)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id 67BDE21F8DDD for <pcp@ietf.org>; Tue,  4 Oct 2011 17:30:57 -0700 (PDT)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 4 Oct 2011 17:34:03 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) with Microsoft SMTP Server (TLS) id 14.1.339.2; Tue, 4 Oct 2011 17:34:03 -0700
Received: from TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com ([169.254.4.161]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi id 14.01.0339.002; Tue, 4 Oct 2011 17:34:03 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Dan Wing <dwing@cisco.com>, 'james woodyatt' <jhw@apple.com>, 'PCP' <pcp@ietf.org>
Thread-Topic: [pcp] PCP and simple firewalls
Thread-Index: AQHMS9DpCskvFfigUEqAnKL7TVvgYpVtj2iAgAAt1gD//5cSMA==
Date: Wed, 5 Oct 2011 00:34:02 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B26D3A6@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <084c01cc82ef$c43edaf0$4cbc90d0$@com>
In-Reply-To: <084c01cc82ef$c43edaf0$4cbc90d0$@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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] PCP and simple firewalls
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, 05 Oct 2011 00:30:58 -0000

Also, PCP doesn't have any requirement on what the default policy is prior =
to
receiving any PCP messages.   There might be static mappings, or whatever e=
lse.
So if a simple firewall chooses to permit the IKE port or the ESP/UDP port =
or=20
whatever else, introducing PCP should have no effect on that.

-Dave

-----Original Message-----
From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Dan W=
ing
Sent: Tuesday, October 04, 2011 4:46 PM
To: 'james woodyatt'; 'PCP'
Subject: Re: [pcp] PCP and simple firewalls

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of=20
> james woodyatt
> Sent: Tuesday, October 04, 2011 2:02 PM
> To: PCP
> Subject: Re: [pcp] PCP and simple firewalls
>=20
> everyone--
>=20
> I've recently been reminded of a message I sent back in July to this=20
> working group, and so far as I can tell, it received no response from=20
> the working group.
>=20
>   <http://www.ietf.org/mail-archive/web/pcp/current/msg01436.html>
>=20
> I still believe these concerns are serious and merit more attention=20
> than they have so far received from the working group, especially=20
> since V6OPS is now in the process of revising RFC 6204 and there is a=20
> move to make an explicit recommendation to use PCP in IPv6 residential=20
> gateway devices.
>=20
> As the -13 revision of the draft remains the most recent published=20
> edition, my previous message to the list on the topic, cited above,=20
> should still be relevant.  Could the working group PLEASE engage on=20
> this?

Thanks for the reminder -- that one had slipped off my list.  I agree it is=
 important, and is something in PCP's scope.


Here is the new text in that same section you quoted above:

2.2.  Supported Protocols

   The PCP Opcodes defined in this document are designed to support
   transport-layer protocols that use a 16-bit port number (e.g., TCP,
   UDP, SCTP, DCCP).  Protocols that do not use a port number (e.g.,
   RSVP, IPsec ESP, ICMP, ICMPv6) are supported for IPv4 firewall, IPv6=20
   firewall, and NPTv6 functions, but are out of scope for any NAT=20
   functions.  A future document may describe how PCP can create NAT=20
   mappings for such protocols.  Also out of scope is using PCP to=20
   request forwarding of all traffic to a single default host (often=20
   nicknamed a "DMZ").

Let me know if that is acceptable.


In the 'generating MAP request' section, I added:

   If the Protocol does not use 16-bit port numbers (e.g., RSVP), the
   port number MUST be 0.


In the 'processing MAP request' section, I adjusted the relevant paragraph =
to allow port=3D0 if the Protocol=20

        If the requested lifetime is non-zero, it indicates a
        request to create a mapping or extend the lifetime of an
        existing mapping.  If the PCP server or PCP-controlled device
        does not support the Protocol or cannot create a mapping for
        the Protocol (e.g., because the request is for a NAT mapping
        instead of a firewall mapping and the PCP-controlled device is
        not a NAT or does not support NATting that specific Protocol),
        it MUST generate an UNSUPP_PROTOCOL error.  If the Protocol is
        supported and the Internal Port is zero but the protocol uses
        a 16 bit port number (e.g., TCP, SCTP), it generates a
        MALFORMED_REQUEST error.  If the Protocol is supported and
        does not use 16 bit port number (e.g., RSVP), the Internal
        Port and the Requested External Port are ignored, but are
        copied into the response.


I don't believe we need similar support for PEER.  Let me know if I'm wrong=
.

-d

>=20
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, core os networking
>=20
>=20
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp

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


From dwing@cisco.com  Tue Oct  4 17:54:18 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 6196C21F8C0A for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 17:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.627
X-Spam-Level: 
X-Spam-Status: No, score=-102.627 tagged_above=-999 required=5 tests=[AWL=-0.628, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lKnye-lC0Cbt for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 17:54:17 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id B2FA121F8BF9 for <pcp@ietf.org>; Tue,  4 Oct 2011 17:54:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=4581; q=dns/txt; s=iport; t=1317776244; x=1318985844; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=wGErZYiPrNe2MewDMuvz/wZS3QDG32GyOC6uVILJcng=; b=HaDnhLwb/+a4+xJ6ow5cTpc9fdsIuPlunUpkCkzVLmOYyiINRmOOmI7P ir+weUPY8kuuUIz6HvJIW1OpAYG6GflYMBfHzDL+6VfCtTUfSenF4inon Pwal+OAc1SL9x1la+Jp5MlC9D6jU+s+UXQto2PBDINjAGMsBR+XwgFZrr k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqsAAASri06rRDoJ/2dsb2JhbABCmHyBa40pgQWBUwEBAQEDAQEBBQoBFxA0FwEDAgkOAQIEAQEoBxkOFQoJCAIEARIJAheHYZk9AZ12hyMEh3idUw
X-IronPort-AV: E=Sophos;i="4.68,488,1312156800";  d="scan'208";a="5981311"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 05 Oct 2011 00:57:23 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p950vNZa028343; Wed, 5 Oct 2011 00:57:23 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Dave Thaler'" <dthaler@microsoft.com>, "'james woodyatt'" <jhw@apple.com>, "'PCP'" <pcp@ietf.org>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com>	<56369024-31BD-4973-9799-012C490BBB02@apple.com> <084c01cc82ef$c43edaf0$4cbc90d0$@com> <9B57C850BB53634CACEC56EF4853FF653B26D3A6@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF653B26D3A6@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 4 Oct 2011 17:57:23 -0700
Message-ID: <086101cc82f9$be807920$3b816b60$@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: AQHMS9DpCskvFfigUEqAnKL7TVvgYpVtj2iAgAAt1gD//5cSMIAABjFQ
Content-Language: en-us
Subject: Re: [pcp] PCP and simple firewalls
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, 05 Oct 2011 00:54:18 -0000

> -----Original Message-----
> From: Dave Thaler [mailto:dthaler@microsoft.com]
> Sent: Tuesday, October 04, 2011 5:34 PM
> To: Dan Wing; 'james woodyatt'; 'PCP'
> Subject: RE: [pcp] PCP and simple firewalls
> 
> Also, PCP doesn't have any requirement on what the default policy is
> prior to
> receiving any PCP messages.   There might be static mappings, or
> whatever else.
> So if a simple firewall chooses to permit the IKE port or the ESP/UDP
> port or
> whatever else, introducing PCP should have no effect on that.

That default falls to RFC6092 (or RFC6092bis that James was mentioning).

-d


> -Dave
> 
> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Dan Wing
> Sent: Tuesday, October 04, 2011 4:46 PM
> To: 'james woodyatt'; 'PCP'
> Subject: Re: [pcp] PCP and simple firewalls
> 
> > -----Original Message-----
> > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> > james woodyatt
> > Sent: Tuesday, October 04, 2011 2:02 PM
> > To: PCP
> > Subject: Re: [pcp] PCP and simple firewalls
> >
> > everyone--
> >
> > I've recently been reminded of a message I sent back in July to this
> > working group, and so far as I can tell, it received no response from
> > the working group.
> >
> >   <http://www.ietf.org/mail-archive/web/pcp/current/msg01436.html>
> >
> > I still believe these concerns are serious and merit more attention
> > than they have so far received from the working group, especially
> > since V6OPS is now in the process of revising RFC 6204 and there is a
> > move to make an explicit recommendation to use PCP in IPv6
> residential
> > gateway devices.
> >
> > As the -13 revision of the draft remains the most recent published
> > edition, my previous message to the list on the topic, cited above,
> > should still be relevant.  Could the working group PLEASE engage on
> > this?
> 
> Thanks for the reminder -- that one had slipped off my list.  I agree
> it is important, and is something in PCP's scope.
> 
> 
> Here is the new text in that same section you quoted above:
> 
> 2.2.  Supported Protocols
> 
>    The PCP Opcodes defined in this document are designed to support
>    transport-layer protocols that use a 16-bit port number (e.g., TCP,
>    UDP, SCTP, DCCP).  Protocols that do not use a port number (e.g.,
>    RSVP, IPsec ESP, ICMP, ICMPv6) are supported for IPv4 firewall, IPv6
>    firewall, and NPTv6 functions, but are out of scope for any NAT
>    functions.  A future document may describe how PCP can create NAT
>    mappings for such protocols.  Also out of scope is using PCP to
>    request forwarding of all traffic to a single default host (often
>    nicknamed a "DMZ").
> 
> Let me know if that is acceptable.
> 
> 
> In the 'generating MAP request' section, I added:
> 
>    If the Protocol does not use 16-bit port numbers (e.g., RSVP), the
>    port number MUST be 0.
> 
> 
> In the 'processing MAP request' section, I adjusted the relevant
> paragraph to allow port=0 if the Protocol
> 
>         If the requested lifetime is non-zero, it indicates a
>         request to create a mapping or extend the lifetime of an
>         existing mapping.  If the PCP server or PCP-controlled device
>         does not support the Protocol or cannot create a mapping for
>         the Protocol (e.g., because the request is for a NAT mapping
>         instead of a firewall mapping and the PCP-controlled device is
>         not a NAT or does not support NATting that specific Protocol),
>         it MUST generate an UNSUPP_PROTOCOL error.  If the Protocol is
>         supported and the Internal Port is zero but the protocol uses
>         a 16 bit port number (e.g., TCP, SCTP), it generates a
>         MALFORMED_REQUEST error.  If the Protocol is supported and
>         does not use 16 bit port number (e.g., RSVP), the Internal
>         Port and the Requested External Port are ignored, but are
>         copied into the response.
> 
> 
> I don't believe we need similar support for PEER.  Let me know if I'm
> wrong.
> 
> -d
> 
> >
> >
> >
> > --
> > james woodyatt <jhw@apple.com>
> > member of technical staff, core os networking
> >
> >
> >
> > _______________________________________________
> > pcp mailing list
> > pcp@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcp
> 
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Tue Oct  4 18:06:50 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 4A20D21F8CB9 for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 18:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.921
X-Spam-Level: 
X-Spam-Status: No, score=-102.921 tagged_above=-999 required=5 tests=[AWL=-0.322, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fCwFXJiEHIBp for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 18:06:49 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6F3C121F8C67 for <pcp@ietf.org>; Tue,  4 Oct 2011 18:06:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=4378; q=dns/txt; s=iport; t=1317776996; x=1318986596; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=sB9FLl5ZFpfzVIwdBA3jAwoyDiUK5APuiiiF0u3BgCc=; b=Qf1adJkhiEa7oGYtWMmif8a0OuzNwtB3DLfbqHOU7ub3vXSZjbShLpBY he2BCGAHgpEcGOHyBTsdMY20voaIQIox/o9Hyfn64KW0j47vILd8gRxX8 /zo6F2E16Reo1kauMfMV1fPO1THu/RPeLDNfDagZ3dfAQPxOXG1RXxvt5 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqsAAMWti06rRDoH/2dsb2JhbABCmHyBa40pgQWBUwEBAQECAQgKARcQOAcFBwEDAgkPAgQBAQEnBxkjCgkIAQEEEwsXh1uZOwGdd4cjBId4nVM
X-IronPort-AV: E=Sophos;i="4.68,488,1312156800";  d="scan'208";a="5969556"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 05 Oct 2011 01:09:56 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9519t7W019016; Wed, 5 Oct 2011 01:09:55 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'james woodyatt'" <jhw@apple.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <084c01cc82ef$c43edaf0$4cbc90d0$@com> <004427B5-438A-4CB4-AD2E-0758BF2ECBA2@apple.com>
In-Reply-To: <004427B5-438A-4CB4-AD2E-0758BF2ECBA2@apple.com>
Date: Tue, 4 Oct 2011 18:09:55 -0700
Message-ID: <086201cc82fb$7eb69980$7c23cc80$@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: AcyC9gEqyYqtpImYQgejRwRZlqm/YwAAzVlA
Content-Language: en-us
Cc: 'PCP' <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 05 Oct 2011 01:06:50 -0000

> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]
> Sent: Tuesday, October 04, 2011 5:31 PM
> To: Dan Wing
> Cc: 'PCP'
> Subject: Re: [pcp] PCP and simple firewalls
> 
> On Oct 4, 2011, at 4:45 PM, Dan Wing wrote:
> >
> > Let me know if that is acceptable.
> 
> I still have two major objections.
> 
> p1. I still don't see anything that permits an IPv6 host to request a
> MAP for the entire upper layer protocol number space from a simple non-
> translating or 1:1 NPTv6 firewall.  I suggest permitting protocol zero,
> HOPOPT, to stand as a wildcard for all upper layer protocols when
> creating a mapping as well as when deleting mappings.

Is this text sufficient?  Highlighting the new sentence which I 
believe captures what you want:

        If the Protocol is supported and
        does not use 16 bit port number (e.g., RSVP), the Internal
        Port and the Requested External Port are ignored, all packets
..........................................................^^^^^^^^^^^
        with that Protocol number are mapped to the internal host, and
........^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        these ignored field values are copied into the response.</t>


> p2. I still don't see any informative references to RFC 6092 or text
> that offers guidance to implementors of RFC 6092-conformant residential
> gateways regarding its exceptions to the default denial policy for IKE
> and IPsec AH/ESP in simple firewalls.  I suggest adding some text to
> the "Mapping Types" entry in the Terminology section that cites RFC
> 6092 and describes an additional mapping type: the 'conventional'
> mapping, which are always applied as a matter of convention or even
> future standards action.  If the term 'conventional mapping' is used,
> then section 8 [and everywhere else that mentions static mappings] will
> need to be revised to discuss how conventional mappings are handled
> differently or the same as static mappings.

I added a new paragraph to Section 4.  For context, here is all of
Section 4, the new paragraph is marked with "+".  I believe this is a
good place to add the paragraph (rather than in a terminology section,
which are often skipped over).


4.  Relationship between PCP Server and its NAT/firewall

   The PCP server receives and responds to PCP requests.  The PCP server
   functionality is typically a capability of a NAT or firewall device,
   as shown in Figure 1.  It is also possible for the PCP functionality
   to be provided by some other device, which communicates with the
   actual NAT or firewall via some other proprietary mechanism, as long
   as from the PCP client's perspective such split operation is
   indistinguishable from the integrated case.

                                  +-----------------+
         +------------+           | NAT or firewall |
         | PCP client |-<network>-+      with       +---<Internet>
         +------------+           |    PCP server   |
                                  +-----------------+

                   Figure 1: PCP-Enabled NAT or Firewall

+  A NAT or firewall device, between the PCP client and the Internet,
+  might implement simple or advanced firewall functionality.  This may
+  be a side-effect of the technology implemented by the device (e.g., a
+  network address and port translator, by virtue of its port rewriting,
+  normally requires connections to be initiated from an inside host
+  towards the Internet), or this might be an explicit firewall policy
+  to deny unsolicited traffic from the Internet.  Some firewall devices
+  deny certain unsolicited traffic from the Internet (e.g., TCP, UDP
+  to most ports) but allow certain other unsolicited traffic from the
+  Internet (e.g., UDP port 500 and IPsec ESP) [RFC6092]).  Such default
+  filtering (or lack thereof) is out of scope of PCP itself.  If a
+  device supports PCP and wants to receive traffic, and does not
+  possess knowledge of such filtering, SHOULD use PCP to create the
+  necessary mappings to receive the desired traffic.


I believe this allows RFC6092 CPE which filter, RFC6092 CPE which don't
filter, and also covers RFC6092bis.  I believe this text also walks
the line between mandating RFC6092 filtering and ignoring RFC6092
filtering.

-d



From jhw@apple.com  Tue Oct  4 20:16:36 2011
Return-Path: <jhw@apple.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 940FF21F8BB8 for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 20:16:36 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5GC-9jU7dVX for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 20:16:35 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id B6E0621F8BAB for <pcp@ietf.org>; Tue,  4 Oct 2011 20:16:35 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LSK005XPP8NJ0M0@mail-out.apple.com> for pcp@ietf.org; Tue, 04 Oct 2011 20:19:42 -0700 (PDT)
X-AuditID: 11807134-b7cedae000007447-99-4e8bca2b3aa5
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay14.apple.com (Apple SCV relay) with SMTP id 6A.AE.29767.C2ACB8E4; Tue, 04 Oct 2011 20:08:28 -0700 (PDT)
Received: from [172.16.1.12] ([75.101.54.88]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LSK004RMP8SWD00@koseret.apple.com> for pcp@ietf.org; Tue, 04 Oct 2011 20:19:41 -0700 (PDT)
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <084c01cc82ef$c43edaf0$4cbc90d0$@com> <004427B5-438A-4CB4-AD2E-0758BF2ECBA2@apple.com> <086201cc82fb$7eb69980$7c23cc80$@com>
In-reply-to: <086201cc82fb$7eb69980$7c23cc80$@com>
Message-id: <12936CA7-3131-40AF-B5D6-571B711E5CB2@apple.com>
X-Mailer: iPad Mail (9A334)
From: james woodyatt <jhw@apple.com>
Date: Tue, 04 Oct 2011 20:19:40 -0700
To: Dan Wing <dwing@cisco.com>
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUiON1OXVfnVLefwZe1HBaTj/1mdWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxrcPPAV/VCq2frjP1MC4SqaLkYNDQsBE4ss61i5GTiBTTOLC vfVsXYxcHEICnUwSnbs+sYEkeAUEJX5MvscCUs8sIC9x8LwsSJhZQEvi+6NWFoj6XiaJ9709 rBDOJ0aJvvf3GEGqOAWMJK4tOs8OMchGYvbJJhaIbjGJv/MuM0Fslpa41fsdrIZNQEXi2+W7 YHFhAW2Jic0bwWwWAVWJdX1HwWwRATmJu/MnME9gFJiF5L5ZCPfNQnLfAkbmVYyCRak5iZWG JnqJBQU5qXrJ+bmbGEFh11BosoPx4E/+Q4wCHIxKPLwLPLv9hFgTy4orcw8xSnAwK4nwbv7Q 5SfEm5JYWZValB9fVJqTWnyIUZqDRUmc1+ZDi5+QQHpiSWp2ampBahFMlomDU6qBUWlXzULj rUkmhklRrTOr5u811u9zD2fraBa77fh0gc2l0Lwte1V71xXGrbq8oqLfcvrNh693ZN4+1dCT /DnLoaOyd2n3120XlvjmZklPypz7tH9tat4RBa6fPhWcT7b+WpRwQNNWyCDYXU7L+q/Dz3/n w7U8k15vK/lydX37MtkV3OIdq9j9lViKMxINtZiLihMBzvyXKjcCAAA=
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 05 Oct 2011 03:16:36 -0000

So far as I know there is no effort underway to revise RFC 6092. It's RFC 6204bis that seems to be underway now.

Sent from my secret agent device.

On Oct 4, 2011, at 18:09, Dan Wing <dwing@cisco.com> wrote:

>> -----Original Message-----
>> From: james woodyatt [mailto:jhw@apple.com]
>> Sent: Tuesday, October 04, 2011 5:31 PM
>> To: Dan Wing
>> Cc: 'PCP'
>> Subject: Re: [pcp] PCP and simple firewalls
>> 
>> On Oct 4, 2011, at 4:45 PM, Dan Wing wrote:
>>> 
>>> Let me know if that is acceptable.
>> 
>> I still have two major objections.
>> 
>> p1. I still don't see anything that permits an IPv6 host to request a
>> MAP for the entire upper layer protocol number space from a simple non-
>> translating or 1:1 NPTv6 firewall.  I suggest permitting protocol zero,
>> HOPOPT, to stand as a wildcard for all upper layer protocols when
>> creating a mapping as well as when deleting mappings.
> 
> Is this text sufficient?  Highlighting the new sentence which I 
> believe captures what you want:
> 
>        If the Protocol is supported and
>        does not use 16 bit port number (e.g., RSVP), the Internal
>        Port and the Requested External Port are ignored, all packets
> ..........................................................^^^^^^^^^^^
>        with that Protocol number are mapped to the internal host, and
> ........^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>        these ignored field values are copied into the response.</t>
> 
> 
>> p2. I still don't see any informative references to RFC 6092 or text
>> that offers guidance to implementors of RFC 6092-conformant residential
>> gateways regarding its exceptions to the default denial policy for IKE
>> and IPsec AH/ESP in simple firewalls.  I suggest adding some text to
>> the "Mapping Types" entry in the Terminology section that cites RFC
>> 6092 and describes an additional mapping type: the 'conventional'
>> mapping, which are always applied as a matter of convention or even
>> future standards action.  If the term 'conventional mapping' is used,
>> then section 8 [and everywhere else that mentions static mappings] will
>> need to be revised to discuss how conventional mappings are handled
>> differently or the same as static mappings.
> 
> I added a new paragraph to Section 4.  For context, here is all of
> Section 4, the new paragraph is marked with "+".  I believe this is a
> good place to add the paragraph (rather than in a terminology section,
> which are often skipped over).
> 
> 
> 4.  Relationship between PCP Server and its NAT/firewall
> 
>   The PCP server receives and responds to PCP requests.  The PCP server
>   functionality is typically a capability of a NAT or firewall device,
>   as shown in Figure 1.  It is also possible for the PCP functionality
>   to be provided by some other device, which communicates with the
>   actual NAT or firewall via some other proprietary mechanism, as long
>   as from the PCP client's perspective such split operation is
>   indistinguishable from the integrated case.
> 
>                                  +-----------------+
>         +------------+           | NAT or firewall |
>         | PCP client |-<network>-+      with       +---<Internet>
>         +------------+           |    PCP server   |
>                                  +-----------------+
> 
>                   Figure 1: PCP-Enabled NAT or Firewall
> 
> +  A NAT or firewall device, between the PCP client and the Internet,
> +  might implement simple or advanced firewall functionality.  This may
> +  be a side-effect of the technology implemented by the device (e.g., a
> +  network address and port translator, by virtue of its port rewriting,
> +  normally requires connections to be initiated from an inside host
> +  towards the Internet), or this might be an explicit firewall policy
> +  to deny unsolicited traffic from the Internet.  Some firewall devices
> +  deny certain unsolicited traffic from the Internet (e.g., TCP, UDP
> +  to most ports) but allow certain other unsolicited traffic from the
> +  Internet (e.g., UDP port 500 and IPsec ESP) [RFC6092]).  Such default
> +  filtering (or lack thereof) is out of scope of PCP itself.  If a
> +  device supports PCP and wants to receive traffic, and does not
> +  possess knowledge of such filtering, SHOULD use PCP to create the
> +  necessary mappings to receive the desired traffic.
> 
> 
> I believe this allows RFC6092 CPE which filter, RFC6092 CPE which don't
> filter, and also covers RFC6092bis.  I believe this text also walks
> the line between mandating RFC6092 filtering and ignoring RFC6092
> filtering.
> 
> -d
> 
> 

From internet-drafts@ietf.org  Sun Oct  9 11:48:15 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 D416A21F8AFF; Sun,  9 Oct 2011 11:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.42
X-Spam-Level: 
X-Spam-Status: No, score=-102.42 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ynEGGZbIjYpC; Sun,  9 Oct 2011 11:48:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7300B21F8A64; Sun,  9 Oct 2011 11:48:15 -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.60
Message-ID: <20111009184815.21173.53079.idtracker@ietfa.amsl.com>
Date: Sun, 09 Oct 2011 11:48:15 -0700
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-base-14.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: Sun, 09 Oct 2011 18:48:16 -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-14.txt
	Pages           : 77
	Date            : 2011-10-09

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


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pcp-base-14.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-14.txt

From dwing@cisco.com  Sun Oct  9 11:50:46 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 2620E21F8AAF for <pcp@ietfa.amsl.com>; Sun,  9 Oct 2011 11:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ugnGMBQIW7ws for <pcp@ietfa.amsl.com>; Sun,  9 Oct 2011 11:50:45 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id B96C021F8B10 for <pcp@ietf.org>; Sun,  9 Oct 2011 11:50:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1655; q=dns/txt; s=iport; t=1318186245; x=1319395845; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=0WibV2WQcX1qYYzYMhPC6G/YkRfaI3SwD2AJgCke1EY=; b=Fs0g+/YPeLNaRyAmPfLKyKNZrKsEgnFYGr7FW5ReCZw64XITaK1DXlyP oEWrSgQoDSj8Ayo4NXVyN5qk7AlCINOHJTj/kP4A57Yu8sq/v0LwVThw1 GczhnVdrIEh7rwk5XJ10qcTGDKEaOw2r6Tu13M8+xd0tGoXgwzNwWBCoM A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqYGABPskU6rRDoG/2dsb2JhbABDmTOBKY08gQWBWggKARUCED8NBRhQIxwBBB4Xh2OYPAGdFodDBId9hloBlxA
X-IronPort-AV: E=Sophos;i="4.68,512,1312156800";  d="scan'208";a="6850928"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 09 Oct 2011 18:50:44 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p99Ioilb030902; Sun, 9 Oct 2011 18:50:44 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <pcp@ietf.org>
Date: Sun, 9 Oct 2011 11:50:43 -0700
Message-ID: <00f301cc86b4$59365530$0ba2ff90$@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: AcyGtFj6GLzMjtrjRoSkgOSKxmpSdQ==
Content-Language: en-us
Cc: draft-ietf-pcp-base@tools.ietf.org
Subject: [pcp] draft-ietf-pcp-base-14 posted
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: Sun, 09 Oct 2011 18:50:46 -0000

draft-ietf-pcp-base-14 has been posted,
http://tools.ietf.org/html/draft-ietf-pcp-base-14

Side-by-side diffs from -13 to -14 are at:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-pcp-base-14.txt

The authors believe this is ready for a second WGLC.

-d

-----


B.1.  Changes from draft-ietf-pcp-base-13 to -14

   o  Moved discussion of socket operations for PCP source address into
      Implementation Considerations section.

   o  Integrated numerous WGLC comments.

   o  NPTv6 in scope.

   o  Re-written security considerations section.  Thanks, Margaret!

   o  Reduced PEER4 and PEER6 Opcodes to just a single Opcode, PEER.

   o  Reduced MAP4 and MAP6 Opcodes to just a single Opcode, MAP.

   o  Rearranged the PEER packet formats to align with MAP.

   o  Removed discussion of the "O" bit for Options, which was
      confusing.  Now the text just discusses the most significant bit
      of the Option code which indicates mandatory/optional, so it is
      clearer the field is 8 bits.

   o  The THIRD_PARTY Option from an unauthorized host generates
      UNSUPP_OPTION, so the PCP server doesn't disclose it knows how to
      process THIRD_PARTY Option.

   o  Added table to show which fields of MAP or PEER need IPv6/IPv4
      addresses for IPv4 firewall, DS-Lite, NAT64, NAT44, etc.

   o  Accommodate the server's Epoch going up or down, to better detect
      switching to a different PCP server.

   o  Removed ADDRESS_MISMATCH; the server always includes its idea of
      the Client's IP Address and Port, and it's up to the client to
      detect a mismatch (and rectify it).



From Francis.Dupont@fdupont.fr  Mon Oct 10 00:51:44 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 059E121F8B20 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 00:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.259
X-Spam-Level: *
X-Spam-Status: No, score=1.259 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_PROFIT1=3.858]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7gzGmykMMemX for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 00:51:43 -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 3F90E21F8B18 for <pcp@ietf.org>; Mon, 10 Oct 2011 00:51:43 -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 p9A7pe0M077571 for <pcp@ietf.org>; Mon, 10 Oct 2011 09:51:42 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110100751.p9A7pe0M077571@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Mon, 10 Oct 2011 09:51:40 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] edition problem with NAT detection?
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, 10 Oct 2011 07:51:44 -0000

The change summary says:

   o  Removed ADDRESS_MISMATCH; the server always includes its idea of
      the Client's IP Address and Port, and it's up to the client to
      detect a mismatch (and rectify it).

I was happy with this as IMHO it is a bit better than
the previous solution but unfortunately it seems the common
response header is the same than for base 13 so how/where this is done?
(I believe it missed the edition but the ADDRESS_MISMATCH is gone so
the current spec is less usable than the previous one... argh!)

Regards

Francis.Dupont@fdupont.fr

PS: the PROCESSING_ERROR is not back when I shew a proof it is
required. I'd like to get a value and stop to use 128...

From moore@network-heretics.com  Tue Oct  4 14:02:35 2011
Return-Path: <moore@network-heretics.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 733DF21F8E17 for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 14:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.192
X-Spam-Level: 
X-Spam-Status: No, score=-3.192 tagged_above=-999 required=5 tests=[AWL=-0.193, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W5mTQOT7K45U for <pcp@ietfa.amsl.com>; Tue,  4 Oct 2011 14:02:33 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC2E21F8E0E for <pcp@ietf.org>; Tue,  4 Oct 2011 14:02:33 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id D7A8C2AD99; Tue,  4 Oct 2011 17:05:38 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 04 Oct 2011 17:05:38 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=XJX512zucfXaLMnqg/bFz1Oz7Yg=; b=nK CgEPwCZodEt4bJIloidNXHvkyOv0tMcua0HENHvZTw5VBkRtXQBQVXU/80YPNJCh mxlu86XRmdlyi/sAOlou6cmI9UjZnHijJY3WMLi5ksS1M0HkMhixlPEzb+Nvn2Pu UHR0I/kC2GtRwm0gRMEFfIVyA/2iQZfcCsXCjjnhk=
X-Sasl-enc: lClo7ewqBGgqCdKI235alB9Hvkww202uXPbPq8SdhK3X 1317762338
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 04C49CA046C; Tue,  4 Oct 2011 17:05:37 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <56369024-31BD-4973-9799-012C490BBB02@apple.com>
Date: Tue, 4 Oct 2011 17:05:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Mon, 10 Oct 2011 11:29:22 -0700
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 04 Oct 2011 21:02:35 -0000

I share your concern.   There is definitely a need for PCP to support =
firewall traversal for IP protocols that don't have ports.  There's no =
reason that this should be out of scope.  If PCP is going to be a =
firewall control protocol, it needs to address this case.

Keith

On Oct 4, 2011, at 5:01 PM, james woodyatt wrote:

> everyone--
>=20
> I've recently been reminded of a message I sent back in July to this =
working group, and so far as I can tell, it received no response from =
the working group.
>=20
>  <http://www.ietf.org/mail-archive/web/pcp/current/msg01436.html>
>=20
> I still believe these concerns are serious and merit more attention =
than they have so far received from the working group, especially since =
V6OPS is now in the process of revising RFC 6204 and there is a move to =
make an explicit recommendation to use PCP in IPv6 residential gateway =
devices.
>=20
> As the -13 revision of the draft remains the most recent published =
edition, my previous message to the list on the topic, cited above, =
should still be relevant.  Could the working group PLEASE engage on =
this?
>=20
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, core os networking
>=20
>=20
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From Tina.Tsou.Zouting@huawei.com  Mon Oct 10 11:44:08 2011
Return-Path: <Tina.Tsou.Zouting@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 47A6721F8C48 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 11:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aY19Bd+rEvHz for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 11:44:07 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 77A1221F8C19 for <pcp@ietf.org>; Mon, 10 Oct 2011 11:44:07 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSV0020P5DHZR@szxga04-in.huawei.com> for pcp@ietf.org; Tue, 11 Oct 2011 02:44:06 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSV00J3M5DH16@szxga04-in.huawei.com> for pcp@ietf.org; Tue, 11 Oct 2011 02:44:05 +0800 (CST)
Received: from szxeml206-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEI77515; Tue, 11 Oct 2011 02:44:03 +0800
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml206-edg.china.huawei.com (172.24.2.58) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 11 Oct 2011 02:44:01 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.58]) by szxeml401-hub.china.huawei.com ([10.82.67.31]) with mapi id 14.01.0270.001; Tue, 11 Oct 2011 02:43:56 +0800
Date: Mon, 10 Oct 2011 18:43:56 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com>
X-Originating-IP: [10.193.34.158]
To: Keith Moore <moore@network-heretics.com>, james woodyatt <jhw@apple.com>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: [pcp] PCP and simple firewalls
Thread-index: AQHMgtjjP507NEnvRk2ga0ajwF/phZVsJumAgAnMLnA=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com>
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 10 Oct 2011 18:44:08 -0000

I said it on the mic.
However, it seems that the WG priority now is to publish the base protocol ASAP. After that, we can add more functions.


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



-----Original Message-----
From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Keith Moore
Sent: Tuesday, October 04, 2011 2:06 PM
To: james woodyatt
Cc: PCP
Subject: Re: [pcp] PCP and simple firewalls

I share your concern.   There is definitely a need for PCP to support firewall traversal for IP protocols that don't have ports.  There's no reason that this should be out of scope.  If PCP is going to be a firewall control protocol, it needs to address this case.

Keith

On Oct 4, 2011, at 5:01 PM, james woodyatt wrote:

> everyone--
> 
> I've recently been reminded of a message I sent back in July to this working group, and so far as I can tell, it received no response from the working group.
> 
>  <http://www.ietf.org/mail-archive/web/pcp/current/msg01436.html>
> 
> I still believe these concerns are serious and merit more attention than they have so far received from the working group, especially since V6OPS is now in the process of revising RFC 6204 and there is a move to make an explicit recommendation to use PCP in IPv6 residential gateway devices.
> 
> As the -13 revision of the draft remains the most recent published edition, my previous message to the list on the topic, cited above, should still be relevant.  Could the working group PLEASE engage on this?
> 
> 
> 
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, core os networking
> 
> 
> 
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp

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

From jhw@apple.com  Mon Oct 10 12:13:50 2011
Return-Path: <jhw@apple.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 C0F5E21F8C99 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 12:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level: 
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HG0Bv5R2AFzf for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 12:13:50 -0700 (PDT)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9EF21F8443 for <pcp@ietf.org>; Mon, 10 Oct 2011 12:13:50 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LSV008276PZAVJ0@mail-out.apple.com> for pcp@ietf.org; Mon, 10 Oct 2011 12:13:46 -0700 (PDT)
X-AuditID: 1180711d-b7b16ae000004efb-11-4e934315e3a7
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 1E.E5.20219.513439E4; Mon, 10 Oct 2011 12:10:13 -0700 (PDT)
Received: from [10.72.51.25] ([63.194.72.222]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LSV005NB6QXEH50@cardamom.apple.com> for pcp@ietf.org; Mon, 10 Oct 2011 12:13:45 -0700 (PDT)
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com> <C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com>
In-reply-to: <C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com>
Message-id: <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com>
X-Mailer: iPad Mail (9A334)
From: james woodyatt <jhw@apple.com>
Date: Mon, 10 Oct 2011 12:13:45 -0700
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGLMWRmVeSWpSXmKPExsUiON1OVVfUebKfQX+bjMXkY79ZHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV8fPHJMaCL4IVJ07MYmtg3MrXxcjJISFgIvF/6xY2CFtM4sK9 9UA2F4eQQCuTxKr5/5lBErwCghI/Jt9j6WLk4GAWkJc4eF4WJMwsoCXx/VErC0T9BCaJY9uf sUI4PxklFk38xQRSxSkQIbF62gwmiEE2Eje+X2CD6HaQuD7pPhPEZmmJW73f2UFsNgEViW+X 74LFhQW0JSY2bwSzWQRUJS7vmMsIYosI6EjsatvFNoFRYBaS+2Yh3DcLyX0LGJlXMQoWpeYk Vhoa6yUWFOSk6iXn525iBIVeQ6HsDsb9P/kPMQpwMCrx8BpZTfITYk0sK67MPcQowcGsJMLb rTPZT4g3JbGyKrUoP76oNCe1+BCjNAeLkjjvHDuglEB6YklqdmpqQWoRTJaJg1OqgdHmzBlB 88df2HTUVHiibpUrrLxS5/OCOVL2Eb9+3beqeMUArlvJ01sdjrUt1FQ4E/Y3LnqTQVUxm2eF hd1180XbslmfF5m5rzj7efn3lt/O5w5Ef5C6+lLk7h1pg01Tjs9x/Ho4pj39+LIrDLZTrAUY d28sFFhu7/TwaXO0maTKbsP+6FdJ5kosxRmJhlrMRcWJAPWUKLo5AgAA
Cc: PCP <pcp@ietf.org>, Keith Moore <moore@network-heretics.com>
Subject: Re: [pcp] PCP and simple firewalls
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, 10 Oct 2011 19:13:50 -0000

I very much hope the working group will not make such a terrible mistake as to publish a base protocol specification with such a serious flaw in it, the current -13 revision does.

Sent from my secret agent device.

On Oct 10, 2011, at 11:43, Tina TSOU <Tina.Tsou.Zouting@huawei.com> wrote:

> I said it on the mic.
> However, it seems that the WG priority now is to publish the base protocol ASAP. After that, we can add more functions.
> 
> 
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
> 
> 
> 
> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Keith Moore
> Sent: Tuesday, October 04, 2011 2:06 PM
> To: james woodyatt
> Cc: PCP
> Subject: Re: [pcp] PCP and simple firewalls
> 
> I share your concern.   There is definitely a need for PCP to support firewall traversal for IP protocols that don't have ports.  There's no reason that this should be out of scope.  If PCP is going to be a firewall control protocol, it needs to address this case.
> 
> Keith
> 
> On Oct 4, 2011, at 5:01 PM, james woodyatt wrote:
> 
>> everyone--
>> 
>> I've recently been reminded of a message I sent back in July to this working group, and so far as I can tell, it received no response from the working group.
>> 
>> <http://www.ietf.org/mail-archive/web/pcp/current/msg01436.html>
>> 
>> I still believe these concerns are serious and merit more attention than they have so far received from the working group, especially since V6OPS is now in the process of revising RFC 6204 and there is a move to make an explicit recommendation to use PCP in IPv6 residential gateway devices.
>> 
>> As the -13 revision of the draft remains the most recent published edition, my previous message to the list on the topic, cited above, should still be relevant.  Could the working group PLEASE engage on this?
>> 
>> 
>> 
>> --
>> james woodyatt <jhw@apple.com>
>> member of technical staff, core os networking
>> 
>> 
>> 
>> _______________________________________________
>> pcp mailing list
>> pcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/pcp
> 
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp

From mrw@lilacglade.org  Mon Oct 10 12:21:49 2011
Return-Path: <mrw@lilacglade.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 2FE0521F8C72 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 12:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EaNOqAWKRPLt for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 12:21:48 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id C5A8221F8C4A for <pcp@ietf.org>; Mon, 10 Oct 2011 12:21:48 -0700 (PDT)
Received: from [10.36.0.36] (pool-108-7-232-64.bstnma.fios.verizon.net [108.7.232.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id AD1F320274; Mon, 10 Oct 2011 15:23:02 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com>
Date: Mon, 10 Oct 2011 15:21:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5ADB97ED-FC63-4732-81D5-FA2A6372ACC9@lilacglade.org>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com> <C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com> <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1084)
Cc: PCP <pcp@ietf.org>, Keith Moore <moore@network-heretics.com>
Subject: Re: [pcp] PCP and simple firewalls
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, 10 Oct 2011 19:21:49 -0000

Hi James,

On Oct 10, 2011, at 3:13 PM, james woodyatt wrote:
> I very much hope the working group will not make such a terrible =
mistake as to publish a base protocol specification with such a serious =
flaw in it, the current -13 revision does.

Dan suggested several changes on-list to address the concerns you have =
raised, and I haven't seen you respond to them...  Do you think that the =
changes he has suggested will fix this "serious flaw", or is there =
something further that you think ought to be done?

I agree that you pointed out some valid omissions in version -13 of the =
spec, but it appears to me that Dan's proposed changes would address =
them.  Am I missing something?

Margaret


From jhw@apple.com  Mon Oct 10 14:10:27 2011
Return-Path: <jhw@apple.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 9BC8721F8551 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 14:10:27 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NPIOAkFnP9Z8 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 14:10:27 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 388B621F853A for <pcp@ietf.org>; Mon, 10 Oct 2011 14:10:27 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LSV000V5C0XUMP1@mail-out.apple.com> for pcp@ietf.org; Mon, 10 Oct 2011 14:10:09 -0700 (PDT)
X-AuditID: 11807137-b7c6bae00000222c-5e-4e9361152a46
Received: from [17.153.16.202] (Unknown_Domain [17.153.16.202]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay16.apple.com (Apple SCV relay) with SMTP id 13.2F.08748.511639E4; Mon, 10 Oct 2011 14:18:13 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <5ADB97ED-FC63-4732-81D5-FA2A6372ACC9@lilacglade.org>
Date: Mon, 10 Oct 2011 14:10:09 -0700
Message-id: <14A48443-B8F0-4D34-AFFA-D99CC3E53D05@apple.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com> <C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com> <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com> <5ADB97ED-FC63-4732-81D5-FA2A6372ACC9@lilacglade.org>
To: Margaret Wasserman <mrw@lilacglade.org>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrELMWRmVeSWpSXmKPExsUiOFPglK5o4mQ/g6sTNCwWLF/KYjH52G9W ByaPJUt+Mnls3L6OJYApissmJTUnsyy1SN8ugSvj58MPbAWPOCra581iaWA8xdbFyMkhIWAi cbV7MyOELSZx4d56sLiQwFQmibn3DUFsYQFtiYnNG5m6GDk4eAWMJV7/YwIJMwtoSdz49xLM ZhNQkfh2+S6YzSngJHGzeRPYSBYBVYk1r9azQ9SLSfyddxmqV1ti2cLXzCA2r4CNxPLPh4DW cgGtvcUk8WDDIbAiEaCiQ8tXM0PcJi+xuOUz4wRG/lkIZ8xCcsYsJGMXMDKvYhQsSs1JrDQ0 00ssKMhJ1UvOz93ECAq5hkLzHYzb/8odYhTgYFTi4X1oN8lPiDWxrLgy9xCjBAezkghvVshk PyHelMTKqtSi/Pii0pzU4kOM0hwsSuK84Y5AKYH0xJLU7NTUgtQimCwTB6dUA6Ps3mTld4+0 euu/JPm/1ootDD4Vc/Pym95Var+suqZtYHP3+eNilu+6tnj2pSWcYsbvX7y9Pq1FyIr/3rvr FqpbeK3Fd85nb5t/Y55/hYuip2B9hE7rL/OQ2Zpnj/pvEw0zm83I+Up71aQeu9nsnj/i36Ql aXy/+IG1VPLR5gnaTkppSuqbO5VYijMSDbWYi4oTAVeSI7A1AgAA
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 10 Oct 2011 21:10:27 -0000

On Oct 10, 2011, at 12:21 , Margaret Wasserman wrote:
> 
> I agree that you pointed out some valid omissions in version -13 of the spec, but it appears to me that Dan's proposed changes would address them.  Am I missing something?

I've looked at the new -14 revision, and yes, it is still seriously flawed.

In section 2.2, the last sentence reads:

               Also out of scope is using PCP to request forwarding of
   all traffic to a single default host (often nicknamed a "DMZ").

In section 9.1, under the entry for Protocol in the format of the MAP packet, I see this text:

                             The value 0 has a special meaning for 'all
      protocols', and is used only for delete requests.

I proposed allowing a firewall (both non-translating and NPTv6 variants) to process MAP requests for the HOPOPT protocol as a request for all upper-layer protocols to be mapped to the requesting private network address.  Are there any technical objections to this proposal?


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From dwing@cisco.com  Mon Oct 10 20:38:00 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 7E26F21F8CD3 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 20:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.67
X-Spam-Level: 
X-Spam-Status: No, score=-100.67 tagged_above=-999 required=5 tests=[AWL=-1.929, BAYES_00=-2.599, FRT_PROFIT1=3.858, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZERYjiotqSLV for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 20:38:00 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 03BE521F8CCD for <pcp@ietf.org>; Mon, 10 Oct 2011 20:38:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1353; q=dns/txt; s=iport; t=1318304280; x=1319513880; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=+KWEaQ1Wg5BODhyJNRnZI6oeBwzz6404F+CGDiCMbKk=; b=Y0wfl4zSx7qUf20qyJekyXbUJ4NEFDN9GyLFfqKpT2ct3IaeYGWUcNan 8S7+67ZA2kkyNrJPHuiEd2Y4pAZFyyDt8iatp6duwFlcRCAmMkGmT/4uA OXZtPwUgmkluj8iu3RjODZtUvKHWyWYQJEFRH3zBH84/BFUXvaUKQV0xs s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An0AAAO5k06rRDoI/2dsb2JhbABDmHeBbI04gQWBUwEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsQB4dcB5sZAZ5DA4dMBKVi
X-IronPort-AV: E=Sophos;i="4.68,521,1312156800";  d="scan'208";a="7089569"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 11 Oct 2011 03:37:59 +0000
Received: from dwingWS (sjc-vpn2-1001.cisco.com [10.21.115.233]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p9B3bxLC027840; Tue, 11 Oct 2011 03:37:59 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110100751.p9A7pe0M077571@givry.fdupont.fr>
In-Reply-To: <201110100751.p9A7pe0M077571@givry.fdupont.fr>
Date: Mon, 10 Oct 2011 23:37:59 -0400
Message-ID: <05da01cc87c7$2c5a2a50$850e7ef0$@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: AcyHIXcsNO+glGucTSGLjJ2bTJWl4AApZCDg
Content-Language: en-us
Subject: Re: [pcp] edition problem with NAT detection?
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, 11 Oct 2011 03:38:00 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Monday, October 10, 2011 3:52 AM
> To: pcp@ietf.org
> Subject: [pcp] edition problem with NAT detection?
> 
> The change summary says:
> 
>    o  Removed ADDRESS_MISMATCH; the server always includes its idea of
>       the Client's IP Address and Port, and it's up to the client to
>       detect a mismatch (and rectify it).
> 
> I was happy with this as IMHO it is a bit better than
> the previous solution but unfortunately it seems the common
> response header is the same than for base 13 so how/where this is done?
> (I believe it missed the edition but the ADDRESS_MISMATCH is gone so
> the current spec is less usable than the previous one... argh!)

Yes, a mistake. 

Will fix.  I am currently travelling, though -- probably Wednesday.

My apologies.

> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: the PROCESSING_ERROR is not back when I shew a proof it is
> required. I'd like to get a value and stop to use 128...

Sorry, I didn't have that in my notes, and I do not have the
context of that proof.  Can you provide a pointer?  Thanks.

-d


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


From dwing@cisco.com  Mon Oct 10 20:39:00 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 5A9C321F8CD6 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 20:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.335
X-Spam-Level: 
X-Spam-Status: No, score=-101.335 tagged_above=-999 required=5 tests=[AWL=0.665, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jMldjLBiAITN for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 20:38:59 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id BCE1721F8CCD for <pcp@ietf.org>; Mon, 10 Oct 2011 20:38:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3048; q=dns/txt; s=iport; t=1318304339; x=1319513939; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=Qc7LESCZ/uUjDj3G0IHd6Ct4WblFvpwmJPTSnu30T5A=; b=YXJqy+oQIvRsmIwOZU1c+D5jgpxmBO0XlWrL1Cab1xbMRzF/XiT6ep59 B3jegTIZmr03T7StqEavMMpdQfJgdv2tQW61P6482EYmqrRTGud2BNlGQ nceFIyklLufLCLIulwzqyVM414xFtW3Yfmj3+Z39JtMOW2R35vLA1R9ye o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An0AAD26k06rRDoI/2dsb2JhbABDmHeBbI04gQWBUwEBAQMBAQEBBQoBFxA0CwUHAQMCCQ8CBAEBAScHGQ4VCgkIAQEEARIJAheHXAebGgGeRodMBKVi
X-IronPort-AV: E=Sophos;i="4.68,521,1312156800";  d="scan'208";a="7089649"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 11 Oct 2011 03:38:55 +0000
Received: from dwingWS (sjc-vpn2-1001.cisco.com [10.21.115.233]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p9B3csL5028040; Tue, 11 Oct 2011 03:38:55 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'james woodyatt'" <jhw@apple.com>, "'Tina TSOU'" <Tina.Tsou.Zouting@huawei.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com>	<56369024-31BD-4973-9799-012C490BBB02@apple.com>	<676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com>	<C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com> <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com>
In-Reply-To: <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com>
Date: Mon, 10 Oct 2011 23:38:54 -0400
Message-ID: <05db01cc87c7$4d81b6d0$e8852470$@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: AcyHgMD47vupylKnT7Ob4yWxMESBYgARncGA
Content-Language: en-us
Cc: 'PCP' <pcp@ietf.org>, 'Keith Moore' <moore@network-heretics.com>
Subject: Re: [pcp] PCP and simple firewalls
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, 11 Oct 2011 03:39:00 -0000

-14 should work with any protocol, including protocols that don't have
ports (e.g., IPSec ESP, RSVP).  That was my attempt when editing -14.

If there was an error where this _doesn't_ work, please point it out.

-d


> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> james woodyatt
> Sent: Monday, October 10, 2011 3:14 PM
> To: Tina TSOU
> Cc: PCP; Keith Moore
> Subject: Re: [pcp] PCP and simple firewalls
> 
> I very much hope the working group will not make such a terrible
> mistake as to publish a base protocol specification with such a serious
> flaw in it, the current -13 revision does.
> 
> Sent from my secret agent device.
> 
> On Oct 10, 2011, at 11:43, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
> wrote:
> 
> > I said it on the mic.
> > However, it seems that the WG priority now is to publish the base
> protocol ASAP. After that, we can add more functions.
> >
> >
> > Best Regards,
> > Tina TSOU
> > http://tinatsou.weebly.com/contact.html
> >
> >
> >
> > -----Original Message-----
> > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Keith Moore
> > Sent: Tuesday, October 04, 2011 2:06 PM
> > To: james woodyatt
> > Cc: PCP
> > Subject: Re: [pcp] PCP and simple firewalls
> >
> > I share your concern.   There is definitely a need for PCP to support
> firewall traversal for IP protocols that don't have ports.  There's no
> reason that this should be out of scope.  If PCP is going to be a
> firewall control protocol, it needs to address this case.
> >
> > Keith
> >
> > On Oct 4, 2011, at 5:01 PM, james woodyatt wrote:
> >
> >> everyone--
> >>
> >> I've recently been reminded of a message I sent back in July to this
> working group, and so far as I can tell, it received no response from
> the working group.
> >>
> >> <http://www.ietf.org/mail-archive/web/pcp/current/msg01436.html>
> >>
> >> I still believe these concerns are serious and merit more attention
> than they have so far received from the working group, especially since
> V6OPS is now in the process of revising RFC 6204 and there is a move to
> make an explicit recommendation to use PCP in IPv6 residential gateway
> devices.
> >>
> >> As the -13 revision of the draft remains the most recent published
> edition, my previous message to the list on the topic, cited above,
> should still be relevant.  Could the working group PLEASE engage on
> this?
> >>
> >>
> >>
> >> --
> >> james woodyatt <jhw@apple.com>
> >> member of technical staff, core os networking
> >>
> >>
> >>
> >> _______________________________________________
> >> pcp mailing list
> >> pcp@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pcp
> >
> > _______________________________________________
> > pcp mailing list
> > pcp@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcp
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Mon Oct 10 20:42:20 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 B073C21F8CA0 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 20:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.856
X-Spam-Level: 
X-Spam-Status: No, score=-101.856 tagged_above=-999 required=5 tests=[AWL=0.743, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vidRfZ1jQOaK for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 20:42:20 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2EB21F8C8A for <pcp@ietf.org>; Mon, 10 Oct 2011 20:42:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2161; q=dns/txt; s=iport; t=1318304540; x=1319514140; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=Rf+24Tu3NOACC7t+x+63ejzrbTVbjoo4M3yLY/CCLw4=; b=WEvsXOyEdqGBU1dd/IkdSrE41JuNjlIEzz75ONAtt3xPHM83ARM5lLUO HOHyGA6OwW8QLzEggMp88GksAaL84Rr7n6ltcVOBJFYRdVyyOw7mcXWfz czVbuWCgVtovi+FiEKLeeIlv2Ti/r7oI0cH9xqMi58mxbK/hqNSjcaMv0 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An0AAPm6k06rRDoH/2dsb2JhbABDmHeBbI04gQWBUwEBAQMBAQEBBQoBFxA0CwUHAQMCCQ8CBAEBAScHGQ4VCgkIAQEEARILF4dcB5sPAZ5DA4dMBKVi
X-IronPort-AV: E=Sophos;i="4.68,521,1312156800";  d="scan'208";a="7073522"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 11 Oct 2011 03:42:19 +0000
Received: from dwingWS (sjc-vpn2-1001.cisco.com [10.21.115.233]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9B3gJOK015850; Tue, 11 Oct 2011 03:42:19 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'james woodyatt'" <jhw@apple.com>, "'Margaret Wasserman'" <mrw@lilacglade.org>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com>	<56369024-31BD-4973-9799-012C490BBB02@apple.com>	<676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com>	<C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com>	<176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com>	<5ADB97ED-FC63-4732-81D5-FA2A6372ACC9@lilacglade.org> <14A48443-B8F0-4D34-AFFA-D99CC3E53D05@apple.com>
In-Reply-To: <14A48443-B8F0-4D34-AFFA-D99CC3E53D05@apple.com>
Date: Mon, 10 Oct 2011 23:42:18 -0400
Message-ID: <05dc01cc87c7$c741ed50$55c5c7f0$@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: AcyHkQrp6KivPQFDQPqIyG27AaEnSwANksNQ
Content-Language: en-us
Cc: 'PCP' <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 11 Oct 2011 03:42:20 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> james woodyatt
> Sent: Monday, October 10, 2011 5:10 PM
> To: Margaret Wasserman
> Cc: PCP
> Subject: Re: [pcp] PCP and simple firewalls
> 
> On Oct 10, 2011, at 12:21 , Margaret Wasserman wrote:
> >
> > I agree that you pointed out some valid omissions in version -13 of
> the spec, but it appears to me that Dan's proposed changes would
> address them.  Am I missing something?
> 
> I've looked at the new -14 revision, and yes, it is still seriously
> flawed.
> 
> In section 2.2, the last sentence reads:
> 
>                Also out of scope is using PCP to request forwarding of
>    all traffic to a single default host (often nicknamed a "DMZ").

That is "all traffic for all protocols."

That is different from "a protocol that does not use ports," which
is what you indicated you wanted, and I believe we have consensus
to add, and which I believe -14 allows.

> In section 9.1, under the entry for Protocol in the format of the MAP
> packet, I see this text:
> 
>                              The value 0 has a special meaning for 'all
>       protocols', and is used only for delete requests.
> 
> I proposed allowing a firewall (both non-translating and NPTv6
> variants) to process MAP requests for the HOPOPT protocol as a request
> for all upper-layer protocols to be mapped to the requesting private
> network address.  Are there any technical objections to this proposal?

Yes.  If this is a NAPT, does the DMZ request supersede all other
mappings, supersede just PCP-created explicit mappings (PEER/MAP)?
And if a new outgoing packet is sent by another host, how does it
get mapped?

If this isn't a NAPT, and just a firewall, the answers are easier.  I
don't know if we could scope DMZ to non-NAPT, but perhaps we could
do that.  Thoughts?

-d


> 
> 
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, core os networking
> 
> 
> 
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From jhw@apple.com  Mon Oct 10 21:20:14 2011
Return-Path: <jhw@apple.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 D689021F8D16 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 21:20:12 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QBH+E9IXcMhS for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 21:20:11 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id F41E321F8D14 for <pcp@ietf.org>; Mon, 10 Oct 2011 21:20:10 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LSV008GAW1KAVQ1@mail-out.apple.com> for pcp@ietf.org; Mon, 10 Oct 2011 21:20:08 -0700 (PDT)
X-AuditID: 11807137-b7c6bae00000222c-63-4e93c5ddb80e
Received: from [17.153.16.118] (Unknown_Domain [17.153.16.118]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay16.apple.com (Apple SCV relay) with SMTP id F7.11.08748.DD5C39E4; Mon, 10 Oct 2011 21:28:13 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <05db01cc87c7$4d81b6d0$e8852470$@com>
Date: Mon, 10 Oct 2011 21:20:07 -0700
Message-id: <6F582F15-C1BA-49AA-A5F7-AE4D9A542B0A@apple.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com> <C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com> <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com> <05db01cc87c7$4d81b6d0$e8852470$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrELMWRmVeSWpSXmKPExsUiOFOgTPfu0cl+BrvOiFlcvPaQyWLysd+s DkweU35vZPVYsuQnUwBTFJdNSmpOZllqkb5dAlfGtl8LWAr2MFc0N89ma2C8yNTFyMkhIWAi sbe/lR3CFpO4cG89WxcjF4eQwFQmiWNn+9hAEsIC2hITmzcCNXBw8AoYS7z+B9bLLKAlcePf SzCbTUBF4tvlu2A2p4CRxL6pjYwgNouAqsT2OduZIerFJP7OuwzVqy2xbOFrsDivgI3E4X9z WEBsIYFTTBINc/RAbBEBOYm78ycwQ9wmL7G45TPjBEb+WQhXzEJyxSwkUxcwMq9iFCxKzUms NDTTSywoyEnVS87P3cQICrmGQvMdjNv/yh1iFOBgVOLh3dg92U+INbGsuDL3EKMEB7OSCG9W CFCINyWxsiq1KD++qDQntfgQozQHi5I4b7gjUEogPbEkNTs1tSC1CCbLxMEp1cB4tepQh4KC 0NzXD10PMLvu7dK8mRPyK2hq1q/rfrlOi89l39/StPmjvpOib05giHxHyLaSmLebTnAEv15Q suLo65hkU7XMrzdu7A69MsEveq+W6MMrOeVaS9hZX/C08BZ52gS+sL8d3qgi9/Nzlqf08wtH fhtOqNSyO3tdN8TnbJHXFcewYyeUWIozEg21mIuKEwHGQ2erNQIAAA==
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 11 Oct 2011 04:20:14 -0000

On Oct 10, 2011, at 20:38 , Dan Wing wrote:
> 
> If there was an error where this _doesn't_ work, please point it out.

How do I ask the PCP server to MAP *all* protocols?  Send a request for each protocol number in turn?  I mean there's only 254 of them, so I suppose that's doable.  It would be stupid if that's what I've got to do.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From dwing@cisco.com  Mon Oct 10 21:42:13 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 E713C21F8D0E for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 21:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.042
X-Spam-Level: 
X-Spam-Status: No, score=-102.042 tagged_above=-999 required=5 tests=[AWL=0.557, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QSu++ylAXhT1 for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 21:42:13 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 66F8A21F8D0D for <pcp@ietf.org>; Mon, 10 Oct 2011 21:42:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=938; q=dns/txt; s=iport; t=1318308133; x=1319517733; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=DyigOXc3vgqbyubg9Gmm7DEbqZezyynfCGkNRm0/SDY=; b=i7nWpS+rr8pRQc2vZ5YdHH46rTZnSY2TGqoRrihDAqmcjuklt/WG3qs5 wXJf8AgMrnN9xcr7BnoqLFNGEO8ZPeUIoMYJOejBLLNB/8GNrPpAxLHlr Rep2RoYafECsvQdAYCsu72OtQHh00JTPakryZs3wA5199okKxQlQEQYf1 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An0AAETIk06rRDoJ/2dsb2JhbABDmHeBbI04gQWBUwEBAQQICgEXED8MAQMCCQ8CBAEBAScHGSMKCQgBAQQTCxeiTQGeRYdMBKVi
X-IronPort-AV: E=Sophos;i="4.68,521,1312156800";  d="scan'208";a="7096920"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 11 Oct 2011 04:42:11 +0000
Received: from dwingWS (sjc-vpn2-1001.cisco.com [10.21.115.233]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9B4gBaX005455; Tue, 11 Oct 2011 04:42:11 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'james woodyatt'" <jhw@apple.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com> <C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com> <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com> <05db01cc87c7$4d81b6d0$e8852470$@com> <6F582F15-C1BA-49AA-A5F7-AE4D9A542B0A@apple.com>
In-Reply-To: <6F582F15-C1BA-49AA-A5F7-AE4D9A542B0A@apple.com>
Date: Tue, 11 Oct 2011 00:42:10 -0400
Message-ID: <05f401cc87d0$23fe7dd0$6bfb7970$@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: AcyHzRBkl/Txnt4ZQ8mXwQHI9Ku6qgAAk+Ig
Content-Language: en-us
Cc: 'PCP' <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 11 Oct 2011 04:42:14 -0000

> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]
> Sent: Tuesday, October 11, 2011 12:20 AM
> To: Dan Wing
> Cc: PCP
> Subject: Re: [pcp] PCP and simple firewalls
> 
> On Oct 10, 2011, at 20:38 , Dan Wing wrote:
> >
> > If there was an error where this _doesn't_ work, please point it out.
> 
> How do I ask the PCP server to MAP *all* protocols?  Send a request for
> each protocol number in turn?  I mean there's only 254 of them, so I
> suppose that's doable.  It would be stupid if that's what I've got to
> do.

You are asking for something different today than you have asked 
for previously.  So please cut me some slack.

I believe we can do this for a firewall.  I believe we cannot do this
for a NAPT.

I will attempt to make the modifications to the document accordingly,
and get that published on Wednesday, along with the correction to
the ADDRESS_MISMATCH oversight.

-d



From jhw@apple.com  Mon Oct 10 22:14:04 2011
Return-Path: <jhw@apple.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 4AF3521F8D5A for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 22:14:04 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m8111j5wcx9u for <pcp@ietfa.amsl.com>; Mon, 10 Oct 2011 22:14:03 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 99EE621F8D58 for <pcp@ietf.org>; Mon, 10 Oct 2011 22:14:03 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LSV00ITAYIUKU00@mail-out.apple.com> for pcp@ietf.org; Mon, 10 Oct 2011 22:14:03 -0700 (PDT)
X-AuditID: 11807130-b7cb3ae000006822-ca-4e93cfc51f7f
Received: from [17.153.51.134] (Unknown_Domain [17.153.51.134]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay11.apple.com (Apple SCV relay) with SMTP id F5.90.26658.5CFC39E4; Mon, 10 Oct 2011 22:10:29 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <05f401cc87d0$23fe7dd0$6bfb7970$@com>
Date: Mon, 10 Oct 2011 22:10:35 -0700
Message-id: <A27FCE51-E876-4A7C-85A6-C57BF1F8F8E6@apple.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com> <C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com> <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com> <05db01cc87c7$4d81b6d0$e8852470$@com> <6F582F15-C1BA-49AA-A5F7-AE4D9A542B0A@apple.com> <05f401cc87d0$23fe7dd0$6bfb7970$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrILMWRmVeSWpSXmKPExsUiONO4TffY+cl+Bo3bGC0uXnvIZDH52G9W ByaPKb83snosWfKTKYApissmJTUnsyy1SN8ugSuj9WFZwVuhilMftzA2MD7n62Lk5JAQMJHY 27OFDcIWk7hwbz2QzcUhJDCVSWJn61JWkISwgLbExOaNTF2MHBy8AsYSr/8xgYSZBbQkbvx7 CWazCahIfLt8F8zmFDCSOLrwHzNIOYuAqkTfljqIcgmJhQ3/2CFsbYllC18zg9i8AjYSC94v gVq7kFni5toWsISIgJzE3fkTmCFuk5dY3PKZcQIj/yyEK2YhuWIWkrELGJlXMQoWpeYkVhoa 6iUWFOSk6iXn525iBAVcQ6HBDsa1P/kPMQpwMCrx8EZ2TvYTYk0sK67MPcQowcGsJMKbFQIU 4k1JrKxKLcqPLyrNSS0+xCjNwaIkzjvXDiglkJ5YkpqdmlqQWgSTZeLglGpgPLA5qyLkyKYZ k9bJ8Ed3igX69X714H/NZdPnW/ujj30nx+H5Tb028keu7NjNvUFliYyfjtfa7v74iVfPOoe8 FdWz9T60csWNFsbIxBibyyut5K+9Ljra43xjl0OS+r9JYR2t1/ZFrv6397yZ0XfHy8/umzF8 snBsK0u9u+HKdz8FzX+PJC58VmIpzkg01GIuKk4EAKjDdEI0AgAA
Cc: 'PCP' <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 11 Oct 2011 05:14:04 -0000

On Oct 10, 2011, at 21:42 , Dan Wing wrote:
> 
> You are asking for something different today than you have asked for previously.

The way I see it, I'm asking for something I started asking for-- and have not stopped asking for since-- back in July, when I wrote this:

On Jul 26, 2011, at 13:16 , james woodyatt wrote:

> If I want my host to have complete responsibility for securing itself, and I want the stupid simple cheap commodity firewall to get out of the way for me, and policy permits this, then the PCP server ought to be able to grant my request for opening a pinhole for the whole of IP upper layer protocol space to my host.

I'm sorry if I've come off sounding brusque earlier.  Hazard of writing IETF email on a device with only a touchscreen keyboard and an annoying autocomplete feature: I tend to write only what's necessary to convey the technical point I want to make, and it makes me come off sounding impatient or worse.  I'm merely trying to be constructively assertive, not cranky and angry.

I do wonder, however, if the mental model of NAPT and IPv4 address amplification is a bit overly dominant in the PCP working group.  I'm surprised that we've gotten all the way up to a -14 revision without anybody noticing this problem with 1:1 NAT and IPv6 firewall host mappings prior to my pointing it out.

On Oct 10, 2011, at 20:42 , Dan Wing wrote:
> 
> Yes.  If this is a NAPT, does the DMZ request supersede all other
> mappings, supersede just PCP-created explicit mappings (PEER/MAP)?
> And if a new outgoing packet is sent by another host, how does it
> get mapped?

One imagines that a NAPT might have a pool of public IP addresses that it reserves for granting 1:1 NAT mappings to hosts that request them.  I would agree that you could save until the successor document the opportunity to extend PCP to permit mapping requests for NAPT rules that apply in a more general case only when more specific mapping have not been inserted into the NAPT engine.  What's important is that the protocol have a way for A) a host to request a 1:1 pinhole mapping for the whole of IP protocol space, and B) a server to respond that it has either mapped the pinhole to the host or it is refusing to do so.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From moore@network-heretics.com  Tue Oct 11 03:25:03 2011
Return-Path: <moore@network-heretics.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 CBD4721F8C08 for <pcp@ietfa.amsl.com>; Tue, 11 Oct 2011 03:25:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S+-l4ttcKHjE for <pcp@ietfa.amsl.com>; Tue, 11 Oct 2011 03:25:03 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id EA30621F8D3F for <pcp@ietf.org>; Tue, 11 Oct 2011 03:25:02 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id EBBF620CBD; Tue, 11 Oct 2011 06:25:01 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Tue, 11 Oct 2011 06:25:01 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=LOW y8fBNv017xofyKF8vnW11AMI=; b=GXEyXI8fb0iv7QDzz2VfsKLp3HK0/I8/2r9 J5FbMDxB76Y/hR0Dy1NyEOUkag47uPGVMRvdgB0sJWHsRzLYT2dINti4uJbhQL8o JCxJoZEcbtFjb5C88a5POzBPKCk+8AONATb8YZj2XQkk000ITIjFoqOsUoOkX7Cf x5dl8a+4=
X-Sasl-enc: 8XSF0AghQZlah2AybdQXpM8r59FGpdbR2vhr+6NlGyXb 1318328701
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id CC8B9402F3E; Tue, 11 Oct 2011 06:25:00 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-5-719068728
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <A27FCE51-E876-4A7C-85A6-C57BF1F8F8E6@apple.com>
Date: Tue, 11 Oct 2011 06:24:44 -0400
Message-Id: <A8202ABE-4115-4738-9592-B285080C950A@network-heretics.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com> <C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com> <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com> <05db01cc87c7$4d81b6d0$e8852470$@com> <6F582F15-C1BA-49AA-A5F7-AE4D9A542B0A@apple.com> <05f401cc87d0$23fe7dd0$6bfb7970$@com> <A27FCE51-E876-4A7C-85A6-C57BF1F8F8E6@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1084)
Cc: 'PCP' <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 11 Oct 2011 10:25:03 -0000

--Apple-Mail-5-719068728
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Oct 11, 2011, at 1:10 AM, james woodyatt wrote:

> I do wonder, however, if the mental model of NAPT and IPv4 address =
amplification is a bit overly dominant in the PCP working group.  I'm =
surprised that we've gotten all the way up to a -14 revision without =
anybody noticing this problem with 1:1 NAT and IPv6 firewall host =
mappings prior to my pointing it out.


I've wondered the same thing.

>  What's important is that the protocol have a way for A) a host to =
request a 1:1 pinhole mapping for the whole of IP protocol space, and B) =
a server to respond that it has either mapped the pinhole to the host or =
it is refusing to do so.

Right.  The protocol needs to define a way that the host can ask for =
this, but the server should be able to respond "I can't do this".

Keith


--Apple-Mail-5-719068728
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Oct 11, 2011, at 1:10 AM, james woodyatt =
wrote:</div><div><br></div><div><blockquote type=3D"cite">I do wonder, =
however, if the mental model of NAPT and IPv4 address amplification is a =
bit overly dominant in the PCP working group. &nbsp;I'm surprised that =
we've gotten all the way up to a -14 revision without anybody noticing =
this problem with 1:1 NAT and IPv6 firewall host mappings prior to my =
pointing it out.</blockquote></div><div><br></div><div>I've wondered the =
same thing.</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">&nbsp;What's =
important is that the protocol have a way for A) a host to request a 1:1 =
pinhole mapping for the whole of IP protocol space, and B) a server to =
respond that it has either mapped the pinhole to the host or it is =
refusing to do so.<br></span></blockquote></div><br><div>Right. =
&nbsp;The protocol needs to define a way that the host can ask for this, =
but the server should be able to respond "I can't do =
this".</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-5-719068728--

From Francis.Dupont@fdupont.fr  Tue Oct 11 03:52:06 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 D618121F8D21 for <pcp@ietfa.amsl.com>; Tue, 11 Oct 2011 03:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.259
X-Spam-Level: *
X-Spam-Status: No, score=1.259 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_PROFIT1=3.858]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u+MzWzEVC2xI for <pcp@ietfa.amsl.com>; Tue, 11 Oct 2011 03:52:06 -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 2C70F21F8D13 for <pcp@ietf.org>; Tue, 11 Oct 2011 03:52:05 -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 p9BAogP2077726; Tue, 11 Oct 2011 12:50:42 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110111050.p9BAogP2077726@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Mon, 10 Oct 2011 23:37:59 EDT. <05da01cc87c7$2c5a2a50$850e7ef0$@com> 
Date: Tue, 11 Oct 2011 12:50:42 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] edition problem with NAT detection?
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, 11 Oct 2011 10:52:06 -0000

 In your previous mail you wrote:

   Yes, a mistake. 
   
   Will fix.  I am currently travelling, though -- probably Wednesday.
   
=> thank, so I should wait for a version 15 (:-).
   
   > PS: the PROCESSING_ERROR is not back when I shew a proof it is
   > required. I'd like to get a value and stop to use 128...
   
   Sorry, I didn't have that in my notes, and I do not have the
   context of that proof.  Can you provide a pointer?  Thanks.
   
=> my standard example is collision on the internal address and
port (exactly: a MAP request is sent, an implicit mapping already
exists with the same internal address and port, the CGN implementation
doesn't know how to upgrade the implicit mapping into an explicit one)
but I really believe there are many cases of "after parsing" errors
and as far as I know only the allocation failure is caught by
an existing PCP error code.
Note I don't buy the "don't add an error code if the client doesn't
know what to do with it" because:
 - not adding an error code has no effect on the error cause
 - error codes are extensible so this problem will exist
in conclusion I really prefer to have the error code in the spec
and keep 128 (and other) values for things they are to.

Thanks

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Tue Oct 11 13:16:50 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 3477C21F8B19 for <pcp@ietfa.amsl.com>; Tue, 11 Oct 2011 13:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.67
X-Spam-Level: 
X-Spam-Status: No, score=-0.67 tagged_above=-999 required=5 tests=[AWL=1.929,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2iV7xTQ+MkM for <pcp@ietfa.amsl.com>; Tue, 11 Oct 2011 13:16:49 -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 7039221F8B16 for <pcp@ietf.org>; Tue, 11 Oct 2011 13:16:49 -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 p9BKGmju012639 for <pcp@ietf.org>; Tue, 11 Oct 2011 22:16:48 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110112016.p9BKGmju012639@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Tue, 11 Oct 2011 22:16:48 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] clarification request about option processing
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, 11 Oct 2011 20:16:50 -0000

In the draft 14 it seems options are copied from the request to
the response without the possible omission from draft 13?
Is my interpretation correct?

If it is the case I have two comments:
 - it makes the processing of options far simpler as there is
  no longer a need for optional copy or squeeze of options in response
 - unfortunately it makes also easier to build a request which
  leads to an oversized response (i.e., more than 1024 byte long)

Regards

Francis.Dupont@fdupont.fr

PS: i do *not* request a change for version 15 here, I am only trying
to understand the 13 vs 14 changes...

From Francis.Dupont@fdupont.fr  Wed Oct 12 02:40:23 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 1147C21F8C36 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 02:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.313
X-Spam-Level: 
X-Spam-Status: No, score=-1.313 tagged_above=-999 required=5 tests=[AWL=1.286,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l0FF7ks+wWH4 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 02:40:22 -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 3EEF521F8C34 for <pcp@ietf.org>; Wed, 12 Oct 2011 02:40:22 -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 p9C9eH8H061124 for <pcp@ietf.org>; Wed, 12 Oct 2011 11:40:20 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110120940.p9C9eH8H061124@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Wed, 12 Oct 2011 11:40:17 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] out of scope text in base 14
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, 12 Oct 2011 09:40:23 -0000

In 7.2 I can read:

   When inspecting packets for translation and forwarding,
   the NAT engine should first consult its list of implicit mappings,
   and if a matching implicit mapping is found, that implicit mapping
   should be used for translating and forwarding the packet.  If no
   matching implicit mapping is found, the NAT engine should then
   consult its list of explicit mappings, and if a matching explicit
   mapping is found, that explicit mapping should be used for
   translating and forwarding the packet.

This is both out of scope of the document (as it is about
the internal behavior of NATs) and IMHO very far from the real
behavior of NATs. Worse, my personal opinion is to *not* recommend
to code NATs this way.
So I strongly suggest to remove this text and to not take
consequences from it.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Wed Oct 12 03:29:45 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 E958021F8C41 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 03:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.635
X-Spam-Level: 
X-Spam-Status: No, score=-1.635 tagged_above=-999 required=5 tests=[AWL=0.965,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bf0-yhWioFKl for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 03:29:45 -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 37A6821F8C20 for <pcp@ietf.org>; Wed, 12 Oct 2011 03:29:45 -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 p9CAThGw064123 for <pcp@ietf.org>; Wed, 12 Oct 2011 12:29:44 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110121029.p9CAThGw064123@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Wed, 12 Oct 2011 12:29:43 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] PEER vs. explicit mappings
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, 12 Oct 2011 10:29:46 -0000

It seems the PEER opcode was changed to create explicit dynamic
mappings, i.e., no longer implicit dynamic mappings.
If it is the case why this was not announced and/or discussed
in the list before?

Regards

Francis.Dupont@fdupont.fr

PS: BTW this major change is *not* listed in the B.1
"Changes from draft-ietf-pcp-base-13 to -14"???

From dwing@cisco.com  Wed Oct 12 12:45:38 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 77E5A21F84DF for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 12:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.969
X-Spam-Level: 
X-Spam-Status: No, score=-101.969 tagged_above=-999 required=5 tests=[AWL=0.630, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8+2NlMUiIPb9 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 12:45:37 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id E6FA721F84A3 for <pcp@ietf.org>; Wed, 12 Oct 2011 12:45:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1022; q=dns/txt; s=iport; t=1318448737; x=1319658337; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=2FO+diEl67fTNpDhg6QQ0Y5YnAbBKk51S654QMLuua8=; b=OhEqJGcZdD7g22N5K51V6WO60+6jKXaIoILdCAiV8Du9PdOqkkJERifz ZPDLe6XaGJ4qmRPtnFkIWRJTqcSl0rjF1dMULNYTmWWWlINd0pjsiRrnU cZLtqInoSHffDQC1rZQbnXekTv/fYwoFKmBH39gOFgNbpSo7QcEKmWWIo w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnIAAKXtlU6rRDoJ/2dsb2JhbABDmRiBbI01gQWBUwEBAQECAQEBAQUKARcQNBAHAQMCCQ8BAQQBASgHGQ4VCgkIAQEEARILF4dcCJswAZ5Sh1gEh3+dag
X-IronPort-AV: E=Sophos;i="4.69,336,1315180800";  d="scan'208";a="7479986"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 12 Oct 2011 19:45:37 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9CJjbPI019057; Wed, 12 Oct 2011 19:45:37 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110121029.p9CAThGw064123@givry.fdupont.fr>
In-Reply-To: <201110121029.p9CAThGw064123@givry.fdupont.fr>
Date: Wed, 12 Oct 2011 12:45:37 -0700
Message-ID: <025c01cc8917$83e77920$8bb66b60$@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: AcyIyd6FZnr+GsjOTIe8ArFewQVEqAATTebg
Content-Language: en-us
Subject: Re: [pcp] PEER vs. explicit mappings
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, 12 Oct 2011 19:45:38 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Wednesday, October 12, 2011 3:30 AM
> To: pcp@ietf.org
> Subject: [pcp] PEER vs. explicit mappings
> 
> It seems the PEER opcode was changed to create explicit dynamic
> mappings, i.e., no longer implicit dynamic mappings.

The ability to create a mapping was done in -09,
http://tools.ietf.org/html/draft-ietf-pcp-base-09#section-7.3
" For Restoring Lost Implicit TCP Dynamic Mapping State",
but at that time we neglected to describe PEER as creating
a mapping as being an "explicit" mapping.

-d

> If it is the case why this was not announced and/or discussed
> in the list before?
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: BTW this major change is *not* listed in the B.1
> "Changes from draft-ietf-pcp-base-13 to -14"???
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Wed Oct 12 12:50: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 5A2F221F8B72 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 12:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.059
X-Spam-Level: 
X-Spam-Status: No, score=-102.059 tagged_above=-999 required=5 tests=[AWL=0.540, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VpE2PI-4bkUv for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 12:50:15 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id C29CE21F8B15 for <pcp@ietf.org>; Wed, 12 Oct 2011 12:50:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1447; q=dns/txt; s=iport; t=1318449015; x=1319658615; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=kIFmzdlwWdCgkWQhebCeeWCYNlornKBFx2hKdygTuxI=; b=a1V775VtTcLUQTe4D26OzjC2dQ4tWaE9A3/3d6nMutdVmQxKUnXytMHj 5t1/PDpbIQ21/01rkHgGsjOw/alor1bQFkGB7clJYYhBiPcf/V2uK9pQ0 nhqBiRXuTr+6h6wms1eg/SAW6gaJonmG1hbkLK1llg9Xak6gH2gvC3Yfn A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnIAAOnulU6rRDoJ/2dsb2JhbABDmRiBbI01gQWBUwEBAQECAQEBAQUKARcQNBAHAQMCCQ8BAQQBASgHGQ4VCgkIAQEEARILF4dcCJs5AZ5Sh1gEh3+dag
X-IronPort-AV: E=Sophos;i="4.69,336,1315180800";  d="scan'208";a="7480794"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 12 Oct 2011 19:50:15 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9CJoFJ7021019; Wed, 12 Oct 2011 19:50:15 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110112016.p9BKGmju012639@givry.fdupont.fr>
In-Reply-To: <201110112016.p9BKGmju012639@givry.fdupont.fr>
Date: Wed, 12 Oct 2011 12:50:15 -0700
Message-ID: <025d01cc8918$2990d600$7cb28200$@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: AcyIUrc/5Wao4RFSSDickK9uLyRsuAAxOv+A
Content-Language: en-us
Subject: Re: [pcp] clarification request about option processing
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, 12 Oct 2011 19:50:16 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Tuesday, October 11, 2011 1:17 PM
> To: pcp@ietf.org
> Subject: [pcp] clarification request about option processing
> 
> In the draft 14 it seems options are copied from the request to
> the response without the possible omission from draft 13?

I don't see significant changes between the section titled
"General PCP Option" in -13 (which was Section 6.7) and
in -14 (which is Section 7.7), 
http://tools.ietf.org/rfcdiff?url2=draft-ietf-pcp-base-14.txt

Sorry, I do not understand that sentence in general, and especially 
do not understand the phrase "without the possible omission from 
draft 13".

So, please provide a specific pointer.

-d

> Is my interpretation correct?
> 
> If it is the case I have two comments:
>  - it makes the processing of options far simpler as there is
>   no longer a need for optional copy or squeeze of options in response
>  - unfortunately it makes also easier to build a request which
>   leads to an oversized response (i.e., more than 1024 byte long)
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: i do *not* request a change for version 15 here, I am only trying
> to understand the 13 vs 14 changes...
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From Francis.Dupont@fdupont.fr  Wed Oct 12 13:35:58 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 D58BC21F8507 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 13:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.827
X-Spam-Level: 
X-Spam-Status: No, score=-1.827 tagged_above=-999 required=5 tests=[AWL=0.772,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uWvKuI1YvHaS for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 13:35:58 -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 2640B21F853B for <pcp@ietf.org>; Wed, 12 Oct 2011 13:35:57 -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 p9CKYYVR001078; Wed, 12 Oct 2011 22:34:34 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110122034.p9CKYYVR001078@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Wed, 12 Oct 2011 12:45:37 PDT. <025c01cc8917$83e77920$8bb66b60$@com> 
Date: Wed, 12 Oct 2011 22:34:34 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] PEER vs. explicit mappings
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, 12 Oct 2011 20:35:58 -0000

 In your previous mail you wrote:

   > -----Original Message-----
   > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
   > Francis Dupont
   > Sent: Wednesday, October 12, 2011 3:30 AM
   > To: pcp@ietf.org
   > Subject: [pcp] PEER vs. explicit mappings
   > 
   > It seems the PEER opcode was changed to create explicit dynamic
   > mappings, i.e., no longer implicit dynamic mappings.
   
   The ability to create a mapping was done in -09,
   http://tools.ietf.org/html/draft-ietf-pcp-base-09#section-7.3
   " For Restoring Lost Implicit TCP Dynamic Mapping State",
   but at that time we neglected to describe PEER as creating
   a mapping as being an "explicit" mapping.
   
=> I strongly disagree and IMHO it is far to be a matter of misunderstanding:
until the version 14 the PEER opcodes were about implicit dynamic mappings
when the MAP opcodes were about explicit dynamic mappings.
As there are some NAT implementations where implicit dynamic mappings
and explicit dynamic mappings are essentially different this is *not* a detail.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Wed Oct 12 13:42:32 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 9AE6221F8B3A for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 13:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.956
X-Spam-Level: 
X-Spam-Status: No, score=-1.956 tagged_above=-999 required=5 tests=[AWL=0.643,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktfRK+-9YmH2 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 13:42:32 -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 DB6B921F8B2F for <pcp@ietf.org>; Wed, 12 Oct 2011 13:42:31 -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 p9CKgS9k001539; Wed, 12 Oct 2011 22:42:28 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110122042.p9CKgS9k001539@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Wed, 12 Oct 2011 12:50:15 PDT. <025d01cc8918$2990d600$7cb28200$@com> 
Date: Wed, 12 Oct 2011 22:42:28 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] clarification request about option processing
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, 12 Oct 2011 20:42:32 -0000

 In your previous mail you wrote:

   Sorry, I do not understand that sentence in general, and especially 
   do not understand the phrase "without the possible omission from 
   draft 13".
   
=> in 13 but not in 14:

   The response MUST encode the Options in the same order,
   but MAY omit some PCP Options in the response, to indicate the PCP
       ^^^^^^^^
   server does not understand that Option or that Option is not
   permitted to be included in responses by the definition of the Option
   itself.

so I interpret the 14 into the options are copied from the request
to the response, in fact the only difference after the opcode is
the response can get an UNPROCESSED option at the end of options.

Regards

Francis.Dupont@fdupont.fr

From dwing@cisco.com  Wed Oct 12 14:03:37 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 0D01121F8B84 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 14:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.127
X-Spam-Level: 
X-Spam-Status: No, score=-102.127 tagged_above=-999 required=5 tests=[AWL=0.472, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TuIS38hTZgn2 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 14:03:36 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 878FF21F8C14 for <pcp@ietf.org>; Wed, 12 Oct 2011 14:03:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1627; q=dns/txt; s=iport; t=1318453416; x=1319663016; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=qCYVoHk8IZ+CAqtcQjvTTdQmP45a4jSsfqf2yY/ZDP8=; b=Otk3vfkgHLj8PcMpIo23DHd/a+7xC3uYVW6SUTxxW2uX02L35z0SB+lb vL2DSq2i44oTJdrlcXtF0B86Te0WnfU6HgdHTj+hH1xl30ue/Ly0n0e99 JPIvG4+LgBzt4PeC79idF0VwM9PFbBmTZcJnJmBYdYD802vmdsPdI24HN 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0AAG//lU6rRDoG/2dsb2JhbABDmRhDgSmNNYEFgVMBAQEBAgEICgEXED8FBwEDAgkPAQEEAQEBJwcZIwoJCAEBBBMLF4dcCJplAZ5Lh1gEh3+dag
X-IronPort-AV: E=Sophos;i="4.69,336,1315180800";  d="scan'208";a="7499447"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 12 Oct 2011 21:03:35 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9CL3YXX027996; Wed, 12 Oct 2011 21:03:34 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Wed, 12 Oct 2011 12:45:37 PDT. <025c01cc8917$83e77920$8bb66b60$@com> <201110122034.p9CKYYVR001078@givry.fdupont.fr>
In-Reply-To: <201110122034.p9CKYYVR001078@givry.fdupont.fr>
Date: Wed, 12 Oct 2011 14:03:34 -0700
Message-ID: <02e201cc8922$67dde330$3799a990$@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: AcyJHo1TpDK+xdcPT+CbhmeSeVCrOAAA8WOQ
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] PEER vs. explicit mappings
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, 12 Oct 2011 21:03:37 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Wednesday, October 12, 2011 1:35 PM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] PEER vs. explicit mappings
> 
> 
>  In your previous mail you wrote:
> 
>    > -----Original Message-----
>    > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf
> Of
>    > Francis Dupont
>    > Sent: Wednesday, October 12, 2011 3:30 AM
>    > To: pcp@ietf.org
>    > Subject: [pcp] PEER vs. explicit mappings
>    >
>    > It seems the PEER opcode was changed to create explicit dynamic
>    > mappings, i.e., no longer implicit dynamic mappings.
> 
>    The ability to create a mapping was done in -09,
>    http://tools.ietf.org/html/draft-ietf-pcp-base-09#section-7.3
>    " For Restoring Lost Implicit TCP Dynamic Mapping State",
>    but at that time we neglected to describe PEER as creating
>    a mapping as being an "explicit" mapping.
> 
> => I strongly disagree and IMHO it is far to be a matter of
> misunderstanding:
> until the version 14 the PEER opcodes were about implicit dynamic
> mappings
> when the MAP opcodes were about explicit dynamic mappings.
> As there are some NAT implementations where implicit dynamic mappings
> and explicit dynamic mappings are essentially different this is *not* a
> detail.

Can those NATs, when they get a PEER request for mapping that does
not already exist (that is, an explicit mapping), return an error?

If so, I'll add text to the document explaining such.

-d


> Regards
> 
> Francis.Dupont@fdupont.fr


From rpenno@juniper.net  Wed Oct 12 14:49:35 2011
Return-Path: <rpenno@juniper.net>
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 4C6F421F8CA2 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 14:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qUbygxuqNejL for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 14:49:34 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id D1AA721F8B70 for <pcp@ietf.org>; Wed, 12 Oct 2011 14:49:20 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP;  Wed, 12 Oct 2011 14:49:34 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.83.0; Wed, 12 Oct 2011 14:46:17 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 12 Oct 2011 17:46:16 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Dan Wing <dwing@cisco.com>, "Francis.Dupont@fdupont.fr" <Francis.Dupont@fdupont.fr>
Date: Wed, 12 Oct 2011 17:46:14 -0400
Thread-Topic: [pcp] PEER vs. explicit mappings
Thread-Index: AcyJHo1TpDK+xdcPT+CbhmeSeVCrOAAA8WOQAAGCjDI=
Message-ID: <CABB58B6.54D26%rpenno@juniper.net>
In-Reply-To: <02e201cc8922$67dde330$3799a990$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] PEER vs. explicit mappings
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, 12 Oct 2011 21:49:35 -0000

If the NAT gets a PEER message before any connection it can install a
session/flow. This is a useful property and I would like it to remain as is=
.
It is implementation dependent is those mappings are kept in a separate
table or whatnot.

Optionally the PCP Server can disallow that, sure.


On 10/12/11 2:03 PM, "Dan Wing" <dwing@cisco.com> wrote:

>> -----Original Message-----
>> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
>> Sent: Wednesday, October 12, 2011 1:35 PM
>> To: Dan Wing
>> Cc: pcp@ietf.org
>> Subject: Re: [pcp] PEER vs. explicit mappings
>>=20
>>=20
>>  In your previous mail you wrote:
>>=20
>>> -----Original Message-----
>>> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf
>> Of
>>> Francis Dupont
>>> Sent: Wednesday, October 12, 2011 3:30 AM
>>> To: pcp@ietf.org
>>> Subject: [pcp] PEER vs. explicit mappings
>>>=20
>>> It seems the PEER opcode was changed to create explicit dynamic
>>> mappings, i.e., no longer implicit dynamic mappings.
>>=20
>>    The ability to create a mapping was done in -09,
>>    http://tools.ietf.org/html/draft-ietf-pcp-base-09#section-7.3
>>    " For Restoring Lost Implicit TCP Dynamic Mapping State",
>>    but at that time we neglected to describe PEER as creating
>>    a mapping as being an "explicit" mapping.
>>=20
>> =3D> I strongly disagree and IMHO it is far to be a matter of
>> misunderstanding:
>> until the version 14 the PEER opcodes were about implicit dynamic
>> mappings
>> when the MAP opcodes were about explicit dynamic mappings.
>> As there are some NAT implementations where implicit dynamic mappings
>> and explicit dynamic mappings are essentially different this is *not* a
>> detail.
>=20
> Can those NATs, when they get a PEER request for mapping that does
> not already exist (that is, an explicit mapping), return an error?
>=20
> If so, I'll add text to the document explaining such.
>=20
> -d
>=20
>=20
>> Regards
>>=20
>> Francis.Dupont@fdupont.fr
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Wed Oct 12 14:50:18 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 434C021F8CA9 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 14:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2kL86yTWLII for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 14:50:17 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id AFD9421F8B70 for <pcp@ietf.org>; Wed, 12 Oct 2011 14:50:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1286; q=dns/txt; s=iport; t=1318456217; x=1319665817; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=eXbZW6qz/GIC/0XjT6I9sNkeya8RSgTmAwoQZ6N4YWo=; b=SEcdtJS1VVLd0c/G1d5EVR3oNOku4zrsvU65P8GIHLycEoxxFGUErkRA dPyLDYOf2V8q4eI75AbxlY1AX8M5SZvwTX848jkpoP9IPDpvqeVG6X4mX BZQEv36yb/5iBQgpVZTGeaMrDqB1xJcfxpkBIOuhuCcQfcupJ3x2CXZ3n U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0AAJQKlk6rRDoJ/2dsb2JhbABDmRlDgSmNNYEFgVMBAQEBAgEICgEXED8FBwEDAgkPAQEEAQEBJwcZIwoJCAEBBBMLF4dcmlgBnkuHWASHf51q
X-IronPort-AV: E=Sophos;i="4.69,336,1315180800";  d="scan'208";a="7524765"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 12 Oct 2011 21:50:16 +0000
Received: from dwingWS ([128.107.106.161]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9CLoGBW022897; Wed, 12 Oct 2011 21:50:16 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Wed, 12 Oct 2011 12:50:15 PDT. <025d01cc8918$2990d600$7cb28200$@com> <201110122042.p9CKgS9k001539@givry.fdupont.fr>
In-Reply-To: <201110122042.p9CKgS9k001539@givry.fdupont.fr>
Date: Wed, 12 Oct 2011 14:50:16 -0700
Message-ID: <032801cc8928$eda7dc40$c8f794c0$@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: AcyJH3b6ug4s+cTuS9+ZstUHeiW2hQACQEIQ
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] clarification request about option processing
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, 12 Oct 2011 21:50:18 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Wednesday, October 12, 2011 1:42 PM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] clarification request about option processing
> 
> 
>  In your previous mail you wrote:
> 
>    Sorry, I do not understand that sentence in general, and especially
>    do not understand the phrase "without the possible omission from
>    draft 13".
> 
> => in 13 but not in 14:
> 
>    The response MUST encode the Options in the same order,
>    but MAY omit some PCP Options in the response, to indicate the PCP
>        ^^^^^^^^
>    server does not understand that Option or that Option is not
>    permitted to be included in responses by the definition of the
> Option
>    itself.
> 
> so I interpret the 14 into the options are copied from the request
> to the response, in fact the only difference after the opcode is
> the response can get an UNPROCESSED option at the end of options.

Right.  

If this causes heartburn related to the PCP maximum message size
for a response, suggestions for how to better deal with this 
are appreciated.

The "MAY omit" was giving too much wiggle room.

-d


> Regards
> 
> Francis.Dupont@fdupont.fr


From dwing@cisco.com  Wed Oct 12 15:00:59 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 1AD9621F87C2 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 15:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bniapmqPDN3r for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 15:00:58 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 85CD721F86AA for <pcp@ietf.org>; Wed, 12 Oct 2011 15:00:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1534; q=dns/txt; s=iport; t=1318456858; x=1319666458; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=bcEvu6Hl1Z8vYK2idhy2Me9qxCRmC2qNppf4t22KY4E=; b=PJC2e5BK7LX5RXRUeHiciRJ6G84zPeyNokUzjyISR/na4QpaMLf28UWW fmcOleqsTC1vePfJIU1jwnD7B5n2+ZCKMf2aWVRIPjpKE15/0G0JayZSa 8y/Tqf+yf0by+c8ueAWDcOA9LrOw45LpT9AI2wycK8M8/D0jCtVgBH3Mz Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnIAAIoNlk6rRDoJ/2dsb2JhbABDmRmBbI01gQWBUwEBAQECAQEBAQUKARcQNBAHAQMCCQ8BAQQBASgHGQ4VCgkIAQEEARILF4dcCJo3AZ5IA4dYBId/nWo
X-IronPort-AV: E=Sophos;i="4.69,336,1315180800";  d="scan'208";a="7510205"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 12 Oct 2011 22:00:58 +0000
Received: from dwingWS ([128.107.106.161]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9CM0w5k029806; Wed, 12 Oct 2011 22:00:58 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110120940.p9C9eH8H061124@givry.fdupont.fr>
In-Reply-To: <201110120940.p9C9eH8H061124@givry.fdupont.fr>
Date: Wed, 12 Oct 2011 15:00:58 -0700
Message-ID: <033201cc892a$6c250920$446f1b60$@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: AcyIwvhvXWBigzF3RL6T1qIQT6M8aQAZz7Hg
Content-Language: en-us
Subject: Re: [pcp] out of scope text in base 14
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, 12 Oct 2011 22:00:59 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Wednesday, October 12, 2011 2:40 AM
> To: pcp@ietf.org
> Subject: [pcp] out of scope text in base 14
> 
> In 7.2 I can read:
> 
>    When inspecting packets for translation and forwarding,
>    the NAT engine should first consult its list of implicit mappings,
>    and if a matching implicit mapping is found, that implicit mapping
>    should be used for translating and forwarding the packet.  If no
>    matching implicit mapping is found, the NAT engine should then
>    consult its list of explicit mappings, and if a matching explicit
>    mapping is found, that explicit mapping should be used for
>    translating and forwarding the packet.
> 
> This is both out of scope of the document (as it is about
> the internal behavior of NATs) and IMHO very far from the real
> behavior of NATs. Worse, my personal opinion is to *not* recommend
> to code NATs this way.
> So I strongly suggest to remove this text and to not take
> consequences from it.

Consensus from you, Reinaldo, and Paul is to remove the text above.  It will
be removed from -15.

There was some text in the introduction of PEER in -14 that similarly 
implied a specific implementation; I softened that text as well.

-d


> Regards
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From Tina.Tsou.Zouting@huawei.com  Wed Oct 12 15:18:59 2011
Return-Path: <Tina.Tsou.Zouting@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 D848621F8CBD for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 15:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.64
X-Spam-Level: 
X-Spam-Status: No, score=-2.64 tagged_above=-999 required=5 tests=[AWL=-3.336,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3,  MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YT-XaEY3fp7V for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 15:18:59 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 139F421F8C76 for <pcp@ietf.org>; Wed, 12 Oct 2011 15:18:59 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSZ00JN84NK7R@szxga03-in.huawei.com> for pcp@ietf.org; Thu, 13 Oct 2011 06:18:56 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSZ00EQ14NKJW@szxga03-in.huawei.com> for pcp@ietf.org; Thu, 13 Oct 2011 06:18:56 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEE89440; Thu, 13 Oct 2011 06:18:56 +0800
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 13 Oct 2011 06:18:51 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.58]) by szxeml402-hub.china.huawei.com ([10.82.67.32]) with mapi id 14.01.0270.001; Thu, 13 Oct 2011 06:18:48 +0800
Date: Wed, 12 Oct 2011 22:18:48 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <201110122042.p9CKgS9k001539@givry.fdupont.fr>
X-Originating-IP: [10.193.34.158]
To: Francis Dupont <Francis.Dupont@fdupont.fr>, Dan Wing <dwing@cisco.com>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C192E19@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: =?gb2312?B?v7S/tNTbw8e1xMq1z9bKx7K7ysdGcmFuY2lzy7W1xMTH0fkvL1JFOiBbcGNw?= =?gb2312?Q?]_clarification_request_about_option_processing?=
Thread-index: AQHMiR9006x0jSLiF0GWx1wpkIV7SpV5R2fw
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: "12 Oct 2011 12:50:15 PDT." <025d01cc8918$2990d600$7cb28200$@com> <201110122042.p9CKgS9k001539@givry.fdupont.fr>
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: [pcp] =?gb2312?b?v7S/tNTbw8e1xMq1z9bKx7K7ysdGcmFuY2lzy7W1xMTH0fkv?= =?gb2312?b?L1JFOiAgY2xhcmlmaWNhdGlvbiByZXF1ZXN0IGFib3V0IG9wdGlvbiBwcm9j?= =?gb2312?b?ZXNzaW5n?=
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, 12 Oct 2011 22:19:00 -0000

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html
http://www.huawei.com/en/solutions/expand-broadband/hw-092950-ipv6.htm



-----Original Message-----
From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Francis Dupont
Sent: Wednesday, October 12, 2011 1:42 PM
To: Dan Wing
Cc: pcp@ietf.org
Subject: Re: [pcp] clarification request about option processing

 In your previous mail you wrote:

   Sorry, I do not understand that sentence in general, and especially 
   do not understand the phrase "without the possible omission from 
   draft 13".
   
=> in 13 but not in 14:

   The response MUST encode the Options in the same order,
   but MAY omit some PCP Options in the response, to indicate the PCP
       ^^^^^^^^
   server does not understand that Option or that Option is not
   permitted to be included in responses by the definition of the Option
   itself.

so I interpret the 14 into the options are copied from the request
to the response, in fact the only difference after the opcode is
the response can get an UNPROCESSED option at the end of options.

Regards

Francis.Dupont@fdupont.fr
_______________________________________________
pcp mailing list
pcp@ietf.org
https://www.ietf.org/mailman/listinfo/pcp

From Tina.Tsou.Zouting@huawei.com  Wed Oct 12 15:24:27 2011
Return-Path: <Tina.Tsou.Zouting@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 37E8C21F8CC0 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 15:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level: 
X-Spam-Status: No, score=-1.096 tagged_above=-999 required=5 tests=[AWL=-3.545, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qQK03jPnOlpu for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 15:24:25 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 79C1221F8CC7 for <pcp@ietf.org>; Wed, 12 Oct 2011 15:24:25 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSZ00BI84WNKZ@szxga05-in.huawei.com> for pcp@ietf.org; Thu, 13 Oct 2011 06:24:23 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSZ0070W4WM28@szxga05-in.huawei.com> for pcp@ietf.org; Thu, 13 Oct 2011 06:24:23 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEJ92806; Thu, 13 Oct 2011 06:24:22 +0800
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 13 Oct 2011 06:24:17 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.58]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0270.001; Thu, 13 Oct 2011 06:24:14 +0800
Date: Wed, 12 Oct 2011 22:24:12 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
X-Originating-IP: [10.193.34.158]
To: Francis Dupont <Francis.Dupont@fdupont.fr>, Dan Wing <dwing@cisco.com>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C192E3E@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, zh-CN
Thread-topic: =?gb2312?B?U29ycnkgbWlzdHlwaW5nLy9SRTogv7S/tNTbw8e1xMq1z9bKx7K7ysdGcmFu?= =?gb2312?B?Y2lzy7W1xMTH0fkvL1JFOiBbcGNwXSBjbGFyaWZpY2F0aW9uIHJlcXVlc3Qg?= =?gb2312?Q?about_option_processing?=
Thread-index: AQHMiR9006x0jSLiF0GWx1wpkIV7SpV5R2fwgAAAWiA=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: "12 Oct 2011 12:50:15 PDT." <025d01cc8918$2990d600$7cb28200$@com> <201110122042.p9CKgS9k001539@givry.fdupont.fr>
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: [pcp] =?gb2312?b?U29ycnkgbWlzdHlwaW5nLy9SRTogv7S/tNTbw8e1xMq1z9Y=?= =?gb2312?b?yseyu8rHRnJhbmNpc8u1tcTEx9H5Ly9SRTogIGNsYXJpZmljYXRpb24gcmVx?= =?gb2312?b?dWVzdCBhYm91dCBvcHRpb24gcHJvY2Vzc2luZw==?=
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, 12 Oct 2011 22:24:27 -0000

U29ycnkgYnkgbWlzdHlwaW5nIGluIENoaW5lc2UuDQpGcmFuY2lzIGFuZCBJIGludGVyb3BlZCBp
biBRdWViZWMgbWVldGluZyBiYXNlZCBvbiAtMTIuDQotMTMgY2hhbmdlZCBhIGxvdCBmcm9tIC0x
Miwgc28gSSdtIG5vdCBhYmxlIHRvIGludGVyb3Agd2l0aCBHYWJvciBlYXNpbHksIGV2ZW4gd2l0
aCBvbmUgdmVyc2lvbiBkaWZmZXJlbmNlLg0KDQpGcmFuY2lzJyBoZXJlIGludGVycHJldGF0aW9u
IG1ha2VzIHNlbnNlLg0KDQpCZXN0IFJlZ2FyZHMsDQpUaW5hIFRTT1UNCmh0dHA6Ly90aW5hdHNv
dS53ZWVibHkuY29tL2NvbnRhY3QuaHRtbA0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQpGcm9tOiBUaW5hIFRTT1UgDQpTZW50OiBXZWRuZXNkYXksIE9jdG9iZXIgMTIsIDIwMTEgMzox
OSBQTQ0KVG86ICdGcmFuY2lzIER1cG9udCc7IERhbiBXaW5nDQpDYzogcGNwQGlldGYub3JnDQpT
dWJqZWN0OiC/tL+01NvDx7XEyrXP1srHsrvKx0ZyYW5jaXPLtbXExMfR+S8vUkU6IFtwY3BdIGNs
YXJpZmljYXRpb24gcmVxdWVzdCBhYm91dCBvcHRpb24gcHJvY2Vzc2luZw0KDQoNCg0KDQoNCkJl
c3QgUmVnYXJkcywNClRpbmEgVFNPVQ0KaHR0cDovL3RpbmF0c291LndlZWJseS5jb20vY29udGFj
dC5odG1sDQpodHRwOi8vd3d3Lmh1YXdlaS5jb20vZW4vc29sdXRpb25zL2V4cGFuZC1icm9hZGJh
bmQvaHctMDkyOTUwLWlwdjYuaHRtDQoNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
RnJvbTogcGNwLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpwY3AtYm91bmNlc0BpZXRmLm9yZ10g
T24gQmVoYWxmIE9mIEZyYW5jaXMgRHVwb250DQpTZW50OiBXZWRuZXNkYXksIE9jdG9iZXIgMTIs
IDIwMTEgMTo0MiBQTQ0KVG86IERhbiBXaW5nDQpDYzogcGNwQGlldGYub3JnDQpTdWJqZWN0OiBS
ZTogW3BjcF0gY2xhcmlmaWNhdGlvbiByZXF1ZXN0IGFib3V0IG9wdGlvbiBwcm9jZXNzaW5nDQoN
CiBJbiB5b3VyIHByZXZpb3VzIG1haWwgeW91IHdyb3RlOg0KDQogICBTb3JyeSwgSSBkbyBub3Qg
dW5kZXJzdGFuZCB0aGF0IHNlbnRlbmNlIGluIGdlbmVyYWwsIGFuZCBlc3BlY2lhbGx5IA0KICAg
ZG8gbm90IHVuZGVyc3RhbmQgdGhlIHBocmFzZSAid2l0aG91dCB0aGUgcG9zc2libGUgb21pc3Np
b24gZnJvbSANCiAgIGRyYWZ0IDEzIi4NCiAgIA0KPT4gaW4gMTMgYnV0IG5vdCBpbiAxNDoNCg0K
ICAgVGhlIHJlc3BvbnNlIE1VU1QgZW5jb2RlIHRoZSBPcHRpb25zIGluIHRoZSBzYW1lIG9yZGVy
LA0KICAgYnV0IE1BWSBvbWl0IHNvbWUgUENQIE9wdGlvbnMgaW4gdGhlIHJlc3BvbnNlLCB0byBp
bmRpY2F0ZSB0aGUgUENQDQogICAgICAgXl5eXl5eXl4NCiAgIHNlcnZlciBkb2VzIG5vdCB1bmRl
cnN0YW5kIHRoYXQgT3B0aW9uIG9yIHRoYXQgT3B0aW9uIGlzIG5vdA0KICAgcGVybWl0dGVkIHRv
IGJlIGluY2x1ZGVkIGluIHJlc3BvbnNlcyBieSB0aGUgZGVmaW5pdGlvbiBvZiB0aGUgT3B0aW9u
DQogICBpdHNlbGYuDQoNCnNvIEkgaW50ZXJwcmV0IHRoZSAxNCBpbnRvIHRoZSBvcHRpb25zIGFy
ZSBjb3BpZWQgZnJvbSB0aGUgcmVxdWVzdA0KdG8gdGhlIHJlc3BvbnNlLCBpbiBmYWN0IHRoZSBv
bmx5IGRpZmZlcmVuY2UgYWZ0ZXIgdGhlIG9wY29kZSBpcw0KdGhlIHJlc3BvbnNlIGNhbiBnZXQg
YW4gVU5QUk9DRVNTRUQgb3B0aW9uIGF0IHRoZSBlbmQgb2Ygb3B0aW9ucy4NCg0KUmVnYXJkcw0K
DQpGcmFuY2lzLkR1cG9udEBmZHVwb250LmZyDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KcGNwIG1haWxpbmcgbGlzdA0KcGNwQGlldGYub3JnDQpodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BjcA0K

From Francis.Dupont@fdupont.fr  Wed Oct 12 15:46:38 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 9382921F8B59 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 15:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.048
X-Spam-Level: 
X-Spam-Status: No, score=-2.048 tagged_above=-999 required=5 tests=[AWL=0.551,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e2Gwfo1WXc01 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 15:46:38 -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 D893C21F8B58 for <pcp@ietf.org>; Wed, 12 Oct 2011 15:46:37 -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 p9CMkY6T009037; Thu, 13 Oct 2011 00:46:34 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110122246.p9CMkY6T009037@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Wed, 12 Oct 2011 14:03:34 PDT. <02e201cc8922$67dde330$3799a990$@com> 
Date: Thu, 13 Oct 2011 00:46:34 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] PEER vs. explicit mappings
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, 12 Oct 2011 22:46:38 -0000

 In your previous mail you wrote:

   > As there are some NAT implementations where implicit dynamic mappings
   > and explicit dynamic mappings are essentially different this is *not* a
   > detail.
   
   Can those NATs, when they get a PEER request for mapping that does
   not already exist (that is, an explicit mapping), return an error?
   
   If so, I'll add text to the document explaining such.
   
=> these NATs always return a CANNOT_PROVIDE_EXTERNAL_PORT error when
the suggested external port is not zero if for instance associated
port pools are different.

Of course my prefered solution is to come back to the previous
behavior, i.e., PEER is about implicit dynamic mappings.

Regards

Francis.Dupont@fdupont.fr

PS: as in the other case, PCP before, one can use MAP to get the
explicit mapping (s)he wants IMHO this makes PEER useless.

From Francis.Dupont@fdupont.fr  Wed Oct 12 15:52:30 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 4F02721F8AFB for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 15:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level: 
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[AWL=0.482,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOd4k4+9anjh for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 15:52:27 -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 14DAF21F8AF9 for <pcp@ietf.org>; Wed, 12 Oct 2011 15:52:25 -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 p9CMqNri009390; Thu, 13 Oct 2011 00:52:23 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110122252.p9CMqNri009390@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Reinaldo Penno <rpenno@juniper.net>
In-reply-to: Your message of Wed, 12 Oct 2011 17:46:14 EDT. <CABB58B6.54D26%rpenno@juniper.net> 
Date: Thu, 13 Oct 2011 00:52:23 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] PEER vs. explicit mappings
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, 12 Oct 2011 22:52:30 -0000

 In your previous mail you wrote:

   If the NAT gets a PEER message before any connection it can install
   a session/flow. This is a useful property and I would like it to
   remain as is.  It is implementation dependent is those mappings are
   kept in a separate table or whatnot.
   
=> this is not question: the PEER was about implicit dynamic mappings
and without announce, discussion or even mention in the changes now
it is about explicit dynamic mappings. This is exactly the kind of
things which makes me to believe to work on PCP is just a waste of
my time.

Regards
   
Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Wed Oct 12 16:09:21 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 DC9BF21F8BE7 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 16:09:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.17
X-Spam-Level: 
X-Spam-Status: No, score=-2.17 tagged_above=-999 required=5 tests=[AWL=0.429,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C63BHqgxti4k for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 16:09:21 -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 1EBDD21F8BA8 for <pcp@ietf.org>; Wed, 12 Oct 2011 16:09:20 -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 p9CN9Ix5010534; Thu, 13 Oct 2011 01:09:18 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110122309.p9CN9Ix5010534@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Wed, 12 Oct 2011 14:50:16 PDT. <032801cc8928$eda7dc40$c8f794c0$@com> 
Date: Thu, 13 Oct 2011 01:09:18 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] clarification request about option processing
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, 12 Oct 2011 23:09:22 -0000

 In your previous mail you wrote:

   > so I interpret the 14 into the options are copied from the request
   > to the response, in fact the only difference after the opcode is
   > the response can get an UNPROCESSED option at the end of options.
   
   Right.  
   
=> fine, it should make the option post-parsing far simpler.

   If this causes heartburn related to the PCP maximum message size
   for a response, suggestions for how to better deal with this 
   are appreciated.
   
=> IMHO the simplest is to require requests to have enough room for a
possible UNPROCESSED option in response for all the option codes which
occur, and if the PCP server finds there is not enough room it MAY
reject a request with MALFORMED_REQUEST (the idea behind the MAY is to
allow proactive or reactive check, i.e., to check all requests for
the room or to check only requests with unprocessed options).
BTW this should be extended to any options which can be appended
to response, i.e., it is the responsability of the client to provide
enough rooms at the end of requests to keep response length <= 1024.
   
Regards

Francis.Dupont@fdupont.fr

From dwing@cisco.com  Wed Oct 12 17:23:59 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 024CA21F8B7C for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 17:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QgwWn2ljXUTA for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 17:23:58 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 1344A21F8B63 for <pcp@ietf.org>; Wed, 12 Oct 2011 17:23:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1194; q=dns/txt; s=iport; t=1318465438; x=1319675038; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=m4Oat/fqTELOmgv2Kj/gUHFihFy5xsxHFxCA5VBl2tQ=; b=l6XvdfiCwWwvXXCVC2U6pIXv8cbLUpq6F7FNbMDWagEUAHEDl6iiy33W irVZT8x/siGNPUxMxt90RMPmgzxCycsTMpZ/1GNs5ic40XrZK7G7RN4z2 R7baF5eTJIsXliOZBrBLv8DVGm0eR2OdByAx8ZtN432rx4K3RTY2IqCiQ Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnIAAB4vlk6rRDoJ/2dsb2JhbABDmSGBbI01gQWBUwEBAQEDCAoBFxA/DAEDAgkPAQEEAQEBJwcZIwoJCAEBBAESCxehdgGeSYdYBId/nWo
X-IronPort-AV: E=Sophos;i="4.69,337,1315180800";  d="scan'208";a="7549135"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 13 Oct 2011 00:23:58 +0000
Received: from dwingWS ([128.107.106.161]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9D0NvFo002642; Thu, 13 Oct 2011 00:23:57 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>, "'Reinaldo Penno'" <rpenno@juniper.net>
References: Your message of Wed, 12 Oct 2011 17:46:14 EDT. <CABB58B6.54D26%rpenno@juniper.net> <201110122252.p9CMqNri009390@givry.fdupont.fr>
In-Reply-To: <201110122252.p9CMqNri009390@givry.fdupont.fr>
Date: Wed, 12 Oct 2011 17:23:57 -0700
Message-ID: <03da01cc893e$65fd52a0$31f7f7e0$@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: AcyJMZ0o1n0Vw3Y5RS+QkrRf944j4gADHoyA
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] PEER vs. explicit mappings
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, 13 Oct 2011 00:23:59 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Wednesday, October 12, 2011 3:52 PM
> To: Reinaldo Penno
> Cc: Dan Wing; pcp@ietf.org
> Subject: Re: [pcp] PEER vs. explicit mappings
> 
> 
>  In your previous mail you wrote:
> 
>    If the NAT gets a PEER message before any connection it can install
>    a session/flow. This is a useful property and I would like it to
>    remain as is.  It is implementation dependent is those mappings are
>    kept in a separate table or whatnot.
> 
> => this is not question: the PEER was about implicit dynamic mappings
> and without announce, discussion or even mention in the changes now
> it is about explicit dynamic mappings. This is exactly the kind of
> things which makes me to believe to work on PCP is just a waste of
> my time.

I recall you objected to PEER being allowed to create mappings back 
when -09 was written, and objected to the use-case of PCP being 
allowed to re-create state in a crashed (home) NAT.

In PCP, we have long used the word "explicit" to mean "create a 
mapping", and as of -09, PEER can do that just like MAP can do 
that.

-d




From dwing@cisco.com  Wed Oct 12 17:28:29 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 3428721F8B0A for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 17:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1mI2ddKj5Hk0 for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 17:28:28 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 91F5821F863E for <pcp@ietf.org>; Wed, 12 Oct 2011 17:28:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1607; q=dns/txt; s=iport; t=1318465708; x=1319675308; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=naDexX75u89WGTFOIJp5URV4dcVZt7IbDbbK9hDJfYM=; b=cq0/ZaLs9QQwXtlU4HHRQ4QmeAhd8p/lCMSaxS3cOOnrAvx/S/RInrxI 6EDaKkR7J0/Z9+/uTRXnDT+HJ7lq8v7Ke+yDsp7Bzq+ZHUdFcdWQzWnGf 2t7pFBe2+lboJ7v+wa3dfLzB41hqVr8aAoWLJ2zYWSmiaASJqZ0yuCQkF k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkAAI0wlk6rRDoI/2dsb2JhbABDmSFDgSmNNYEFgVMBAQEBAgEICgEXED8FBwEDAgkPAQEEAQEBJwcZIwoJCAEBBBMLEAeHXJofAZ5Hh1gEh3+dag
X-IronPort-AV: E=Sophos;i="4.69,337,1315180800";  d="scan'208";a="7528431"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 13 Oct 2011 00:28:16 +0000
Received: from dwingWS ([128.107.106.161]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p9D0SGO6004973; Thu, 13 Oct 2011 00:28:16 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Wed, 12 Oct 2011 14:03:34 PDT. <02e201cc8922$67dde330$3799a990$@com> <201110122246.p9CMkY6T009037@givry.fdupont.fr>
In-Reply-To: <201110122246.p9CMkY6T009037@givry.fdupont.fr>
Date: Wed, 12 Oct 2011 17:28:16 -0700
Message-ID: <03db01cc893f$00167b00$00437100$@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: AcyJMM5UsT0hRFtdTiuuOJlZQ+DSMwADam8A
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] PEER vs. explicit mappings
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, 13 Oct 2011 00:28:29 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Wednesday, October 12, 2011 3:47 PM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] PEER vs. explicit mappings
> 
> 
>  In your previous mail you wrote:
> 
>    > As there are some NAT implementations where implicit dynamic
> mappings
>    > and explicit dynamic mappings are essentially different this is
> *not* a
>    > detail.
> 
>    Can those NATs, when they get a PEER request for mapping that does
>    not already exist (that is, an explicit mapping), return an error?
> 
>    If so, I'll add text to the document explaining such.
> 
> => these NATs always return a CANNOT_PROVIDE_EXTERNAL_PORT error when
> the suggested external port is not zero if for instance associated
> port pools are different.
> 
> Of course my prefered solution is to come back to the previous
> behavior, i.e., PEER is about implicit dynamic mappings.

PEER is still about implicit dynamic mappings.  Hopefully my upcoming
changes in -15 will soften this.

> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: as in the other case, PCP before, one can use MAP to get the
> explicit mapping (s)he wants IMHO this makes PEER useless.

They are certainly similar.  But they're not the same.

PEER's creation of an explicit mapping is supposed to work
exactly as if a TCP SYN were sent by the client.  Which on many 
NATs creates a different mapping and different filtering than 
if MAP or UPnP IGD or NAT-PMP or a web page is used to 
configure port forwarding.

-d



From dwing@cisco.com  Wed Oct 12 17:30: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 5F9EA21F8B7F for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 17:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1zvXMYM1I-rP for <pcp@ietfa.amsl.com>; Wed, 12 Oct 2011 17:30:13 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id EBCD721F8B0C for <pcp@ietf.org>; Wed, 12 Oct 2011 17:30:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1900; q=dns/txt; s=iport; t=1318465813; x=1319675413; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=5oNiGZkbEnx0WkarikMr5Ixt4y3ULBwOjHJeqNk4uaM=; b=RGCVWGCrFTf3d7yZ0C5Ljb1oHn3oDPW0wbdvhzctg4wnhfG7IjG8Iw4B hjoEkLs52ECt8VGcyCfS3nynmvcTBiH2d1PYgVbqWawMDvr7X58FTLtKk M+joVVbafjRZH3A45ODsx8RRsQeRrg/Cby0rXw3elsMyZphLoBcwQ+AsF Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkAAI0wlk6rRDoG/2dsb2JhbABDmSFDgSmNNYEFgVMBAQEBAgEICgEXED8FBwEDAgkPAQEEAQEBJwcZIwoJCAEBBBMLF4dcmh8BnkeHWASHf51q
X-IronPort-AV: E=Sophos;i="4.69,337,1315180800";  d="scan'208";a="7528663"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 13 Oct 2011 00:30:13 +0000
Received: from dwingWS ([128.107.106.161]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9D0UD3M005660; Thu, 13 Oct 2011 00:30:13 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Wed, 12 Oct 2011 14:50:16 PDT. <032801cc8928$eda7dc40$c8f794c0$@com> <201110122309.p9CN9Ix5010534@givry.fdupont.fr>
In-Reply-To: <201110122309.p9CN9Ix5010534@givry.fdupont.fr>
Date: Wed, 12 Oct 2011 17:30:13 -0700
Message-ID: <03dc01cc893f$46055000$d20ff000$@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: AcyJM/yHfQcmp6xmRgiLbB3hBMDmXwAAK+Cw
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] clarification request about option processing
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, 13 Oct 2011 00:30:14 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Wednesday, October 12, 2011 4:09 PM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] clarification request about option processing
> 
> 
>  In your previous mail you wrote:
> 
>    > so I interpret the 14 into the options are copied from the request
>    > to the response, in fact the only difference after the opcode is
>    > the response can get an UNPROCESSED option at the end of options.
> 
>    Right.
> 
> => fine, it should make the option post-parsing far simpler.
> 
>    If this causes heartburn related to the PCP maximum message size
>    for a response, suggestions for how to better deal with this
>    are appreciated.
> 
> => IMHO the simplest is to require requests to have enough room for a
> possible UNPROCESSED option in response for all the option codes which
> occur, and if the PCP server finds there is not enough room it MAY
> reject a request with MALFORMED_REQUEST (the idea behind the MAY is to
> allow proactive or reactive check, i.e., to check all requests for
> the room or to check only requests with unprocessed options).

Ok, so I am adding:

   If a PCP response would have
   exceeded the maximum PCP message size, the PCP server MAY
   respond with MALFORMED_REQUEST.</t>

> BTW this should be extended to any options which can be appended
> to response, i.e., it is the responsability of the client to provide
> enough rooms at the end of requests to keep response length <= 1024.

Ok, so I am adding:

  It is the responsibility of the
  PCP client to ensure the server has sufficient room to reply
  with an error including UNPROCESSED Options; this can be achieved
  by sending messages that don't exceed 1024-4*number_of_options
  octets.

-d

> 
> Regards
> 
> Francis.Dupont@fdupont.fr


From Francis.Dupont@fdupont.fr  Thu Oct 13 02:35:45 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 6C16021F84CE for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 02:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.213
X-Spam-Level: 
X-Spam-Status: No, score=-2.213 tagged_above=-999 required=5 tests=[AWL=0.386,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Au3E3czAkPL4 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 02:35:44 -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 8367A21F84C2 for <pcp@ietf.org>; Thu, 13 Oct 2011 02:35:44 -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 p9D9YLK5048321; Thu, 13 Oct 2011 11:34:21 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110130934.p9D9YLK5048321@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Wed, 12 Oct 2011 17:28:16 PDT. <03db01cc893f$00167b00$00437100$@com> 
Date: Thu, 13 Oct 2011 11:34:21 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] PEER vs. explicit mappings
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, 13 Oct 2011 09:35:45 -0000

 In your previous mail you wrote:

   > Of course my prefered solution is to come back to the previous
   > behavior, i.e., PEER is about implicit dynamic mappings.
   
   PEER is still about implicit dynamic mappings.  Hopefully my upcoming
   changes in -15 will soften this.
   
=> so we'll get what was in the draft 13 in sections 9.3 and 9.4 with
some "implicit dynamic mappings" in the text, shan't we?

   > PS: as in the other case, PCP before, one can use MAP to get the
   > explicit mapping (s)he wants IMHO this makes PEER useless.
   
   They are certainly similar.  But they're not the same.
   
   PEER's creation of an explicit mapping is supposed to work
   exactly as if a TCP SYN were sent by the client.

=> I can't parse this statement as a TCP SYN creates an
implicit dynamic mapping which is not the same than an explicit
dynamic mapping (here I use the PCP terminology, not the common
meaning of the word "explicit").

   Which (TCP SYN) on many NATs creates a different mapping and
   different filtering than if MAP or UPnP IGD or NAT-PMP or a web
   page is used to configure port forwarding.
   
=> so you agree on many NATs the implicit dynamic mapping from
a TCP SYN is different than an explicit dynamic mapping or
a static mapping? So I don't understand why PEER is no longer
specified to act on implicit dynamic mappings??

Regards   

Francis.Dupont@fdupont.fr

PS: I strongly suggest to replace the word explicit by a
synonym in the PEER text so the fact the PEER action is
by definition explicit can no longer lead to confusion
with the PCP terminology.

From Francis.Dupont@fdupont.fr  Thu Oct 13 06:13:14 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 CB71D21F8B31 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 06:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.278
X-Spam-Level: 
X-Spam-Status: No, score=-2.278 tagged_above=-999 required=5 tests=[AWL=0.322,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bcP74OmWC8go for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 06:13:14 -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 2206B21F8B2F for <pcp@ietf.org>; Thu, 13 Oct 2011 06:13:13 -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 p9DDD8d8061746 for <pcp@ietf.org>; Thu, 13 Oct 2011 15:13:08 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110131313.p9DDD8d8061746@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 13 Oct 2011 15:13:08 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] learning the external address
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, 13 Oct 2011 13:13:14 -0000

I am not happy with section 9.7 "Learning the External IP Address Alone",
first the term "costemic" ignores this is required to implement IWF,
second the proposed solution is inefficient and underspecified.
In conclusion this seems as nobody cares about addressing the problem...

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Thu Oct 13 06:20:39 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 C726921F847E for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 06:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level: 
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[AWL=0.297,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dfi7nfTpKEly for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 06:20:39 -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 750D621F8ABD for <pcp@ietf.org>; Thu, 13 Oct 2011 06:09:26 -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 p9DD9OOE061502 for <pcp@ietf.org>; Thu, 13 Oct 2011 15:09:24 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110131309.p9DD9OOE061502@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 13 Oct 2011 15:09:24 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] DS-Lite modes
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, 13 Oct 2011 13:20:39 -0000

Can you add a reference to draft-dupont-pcp-dslite in the section 8
"Introduction to MAP and PEER Opcodes" in the table comments?

Thanks

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Thu Oct 13 06:49:22 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 3A25121F8AF9 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 06:49:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.323
X-Spam-Level: 
X-Spam-Status: No, score=-2.323 tagged_above=-999 required=5 tests=[AWL=0.276,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aXXCujDqrz5l for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 06:49:21 -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 7F5E421F85A1 for <pcp@ietf.org>; Thu, 13 Oct 2011 06:49:21 -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 p9DDnK7C063828 for <pcp@ietf.org>; Thu, 13 Oct 2011 15:49:20 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110131349.p9DDnK7C063828@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 13 Oct 2011 15:49:20 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] fields to copy
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, 13 Oct 2011 13:49:22 -0000

In draft 14 section 7.2:

   ... Copying
   request fields such as Protocol and Internal Port (for MAP requests)
   and Protocol, Internal Port, Remote Peer IP Address and Port (for
   PEER requests) is important because this is what enables a client to
   identify to which request a given error response pertains.

=> in fact in some cases the external port too, and IMHO in all cases
the Internal address i.e. the THIRD_PARTY option, so I propos:

   ... Copying
   request fields such as Protocol and Internal Port, the THIRD_PARTY
   Option when it is present, and in some cases the External Port (for
   MAP requests) and Protocol, Internal Port, Remote Peer IP Address
   and Port, the THIRD_PARTY Option when it is present, and in some
   cases the External Port (for PEER requests) is important because
   this is what enables a client to identify to which request a given
   error response pertains.

Regards

Francis.Dupont@fdupont.fr

PS: BTW please note it is useless to copy the External Address in all cases.

From Francis.Dupont@fdupont.fr  Thu Oct 13 07:26:54 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 F2CDD21F8B31 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 07:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.342
X-Spam-Level: 
X-Spam-Status: No, score=-2.342 tagged_above=-999 required=5 tests=[AWL=0.257,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qxumDxzHgEGf for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 07:26:53 -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 2C41221F8B24 for <pcp@ietf.org>; Thu, 13 Oct 2011 07:26:45 -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 p9DEQgeY066141 for <pcp@ietf.org>; Thu, 13 Oct 2011 16:26:45 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110131426.p9DEQgeY066141@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 13 Oct 2011 16:26:42 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] NAT chains
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, 13 Oct 2011 14:26:54 -0000

In base 14 section 7.3 I can read:

   If the PCP Client's IP Address and PCP Client's Port fields of the
   PCP response header do not match the source address and port of the
   request, it indicates the presence of a NAT between the PCP client
   and PCP server.  If they don't match, then the PCP client (or the
   user on the client host) MUST ensure that an appropriate NAT mapping
   is created on the intervening NAT(s) (e.g., using UPnP IGD, NAT-PMP,
   or manual configuration), otherwise, the PCP-installed mapping will
   be ineffective.

I note PCP is not in the examples (i.e., then "e.g." list).
There are least two moderately incompatible ways to handle NAT chains
in PCP, I'll develop this point when the base spec will be ready.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Thu Oct 13 08:05:32 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 83EB521F8BA6 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 08:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.358
X-Spam-Level: 
X-Spam-Status: No, score=-2.358 tagged_above=-999 required=5 tests=[AWL=0.241,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6NUEB2kUbldS for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 08:05:32 -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 CA66B21F8B16 for <pcp@ietf.org>; Thu, 13 Oct 2011 08:05:31 -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 p9DF5UaP068562 for <pcp@ietf.org>; Thu, 13 Oct 2011 17:05:30 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110131505.p9DF5UaP068562@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 13 Oct 2011 17:05:30 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] small proposed addition in 8
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, 13 Oct 2011 15:05:32 -0000

In the base 14 section 8 in the figure 6 (table) intro:

change
   ... the 'remote peer' is the Remote
   Peer IP Address of the PEER request.
by
   ... the 'remote peer' is the Remote
   Peer IP Address of the PEER request or the FILTER option
   of the MAP request

BTW the 'internal' address definition is not complete, it is from
the THIRD_PARTY option (lowercase) when it is present or the source
address when it is not.

Regards

Francis.Dupont@fdupont.fr

From dwing@cisco.com  Thu Oct 13 10:01:26 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 4F79F21F8AC9 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 10:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.179
X-Spam-Level: 
X-Spam-Status: No, score=-102.179 tagged_above=-999 required=5 tests=[AWL=0.420, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j0XK25QmpzlE for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 10:01:25 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id BEFA521F8801 for <pcp@ietf.org>; Thu, 13 Oct 2011 10:01:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=749; q=dns/txt; s=iport; t=1318525285; x=1319734885; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=menbA9Huq9rIldiFlRttSw5eDh6twhwOI4Pn7origVk=; b=FcVvBKJ/Gc3U0YxBa4azb6r5N8asIWOCRHsmgk9njmDVds8lByU08VKk 5OPqwPEEAaJ4Tz0RQ+Yy39F3Pkfu1mHe3bH8dGzHqtTAS8VDaRMRmtKW+ 7N76kzpeJk9w1g8f1Vkb0sOnqXnZYWGK1cwF6n7xHOQGHhiRWrLiAkgNP I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEAABwYl06rRDoJ/2dsb2JhbABDmTOBbI05gQWBUwEBAQQICgEVAhA/DAEDAgkPAgQBAQEnBxkjCgkIAQEEEwsXoTUBni6HbQSIAZ1s
X-IronPort-AV: E=Sophos;i="4.69,341,1315180800";  d="scan'208";a="7665730"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 13 Oct 2011 17:01:24 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9DH1Oam032675; Thu, 13 Oct 2011 17:01:24 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'james woodyatt'" <jhw@apple.com>
References: <37F3317E-AB18-4F1E-8404-FEDBBBFBF076@apple.com> <56369024-31BD-4973-9799-012C490BBB02@apple.com> <676F8198-2CD3-425F-A074-DBA8E2BB6AC1@network-heretics.com> <C0E0A32284495243BDE0AC8A066631A80C1902A2@szxeml526-mbx.china.huawei.com> <176454D2-BF28-4907-884C-A6A6BD48CF19@apple.com> <05db01cc87c7$4d81b6d0$e8852470$@com> <6F582F15-C1BA-49AA-A5F7-AE4D9A542B0A@apple.com> <05f401cc87d0$23fe7dd0$6bfb7970$@com> <A27FCE51-E876-4A7C-85A6-C57BF1F8F8E6@apple.com>
In-Reply-To: <A27FCE51-E876-4A7C-85A6-C57BF1F8F8E6@apple.com>
Date: Thu, 13 Oct 2011 10:01:24 -0700
Message-ID: <007601cc89c9$bd46d730$37d48590$@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: AcyH1JgCbnEuhtaASwWq0RXajnTqCwB9OkPw
Content-Language: en-us
Cc: 'PCP' <pcp@ietf.org>
Subject: Re: [pcp] PCP and simple firewalls
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, 13 Oct 2011 17:01:26 -0000

> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]
> Sent: Monday, October 10, 2011 10:11 PM
> To: Dan Wing
> Cc: 'PCP'
> Subject: Re: [pcp] PCP and simple firewalls
> 
> On Oct 10, 2011, at 21:42 , Dan Wing wrote:
> >
> > You are asking for something different today than you have asked for
> previously.
> 
> The way I see it, I'm asking for something I started asking for-- and
> have not stopped asking for since-- back in July, when I wrote this:

-15 now allows a single message to request all firewalling be 
disabled, using a MAP request with protocol=0 and port=0.  This is
an optimization (reduction of PCP message round trips) compared
to -14.

You seemed to want/need the optimization.

-d




From dwing@cisco.com  Thu Oct 13 11:22:12 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 0D7EF21F8B48 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 11:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.255
X-Spam-Level: 
X-Spam-Status: No, score=-102.255 tagged_above=-999 required=5 tests=[AWL=0.344, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03oaD4ETQSno for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 11:22:10 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id A5AD921F8ACC for <pcp@ietf.org>; Thu, 13 Oct 2011 11:22:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3299; q=dns/txt; s=iport; t=1318530130; x=1319739730; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=hk4j4oGqxfibYebvXnyxzX+jIuCjqsrT/Rr9ydHQQ0A=; b=hG1AYOl/xk7Gj7V3Sgu8ludSJBDgXjX8OU1Fg6b3ncukmoKBUCtGES4J fWdkVTZkjTXKHMGlTYtzL4BfLly04jDUtDiAbaN6RU4spsTsG0lG0I5/l 0iKjzP2wDZ12ZtRyBncORIlZYniJFNDIBl5riHG1WFlIC4sgodnc4imyF I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEAADYrl06rRDoH/2dsb2JhbABDmTSBbI05gQWBUwEBAQMBCAoBFQIQPwwBAwIJDwEBBAEBAScHGSMKCQgBAQQTCxAHh1yZPgGeL4dtBIgBnWw
X-IronPort-AV: E=Sophos;i="4.69,341,1315180800";  d="scan'208";a="7703077"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 13 Oct 2011 18:22:10 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9DIMAsB023824; Thu, 13 Oct 2011 18:22:10 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Wed, 12 Oct 2011 17:28:16 PDT. <03db01cc893f$00167b00$00437100$@com> <201110130934.p9D9YLK5048321@givry.fdupont.fr>
In-Reply-To: <201110130934.p9D9YLK5048321@givry.fdupont.fr>
Date: Thu, 13 Oct 2011 11:22:10 -0700
Message-ID: <00fd01cc89d5$05b1cec0$11156c40$@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: AcyJi4HqFV/VXAOoSZGMb9IZTjCTXQAST9qQ
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] PEER vs. explicit mappings
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, 13 Oct 2011 18:22:12 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Thursday, October 13, 2011 2:34 AM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] PEER vs. explicit mappings
> 
> 
>  In your previous mail you wrote:
> 
>    > Of course my prefered solution is to come back to the previous
>    > behavior, i.e., PEER is about implicit dynamic mappings.
> 
>    PEER is still about implicit dynamic mappings.  Hopefully my
> upcoming
>    changes in -15 will soften this.
> 
> => so we'll get what was in the draft 13 in sections 9.3 and 9.4 with
> some "implicit dynamic mappings" in the text, shan't we?

Here is my current work-in-progress text regarding this point in -15,

   10.2.  Generating a PEER Request

   This section describes the operation of a client when generating a
   message with the PEER Opcode.

   The PEER Opcode MAY be sent before or after establishing bi-
   directional communication with the remote peer.

      If sent before, this is considered an "explicit dynamic mapping",
      and the PEER Opcode will create a new explicit mapping in the PCP-
      controlled device, which will be used for translating traffic to
      and from the remote peer; this mapping functions the same as if an
      implicit dynamic mapping were created (e.g., because of a TCP SYN
      from the client).  This is useful for restoring a mapping after a
      NAT has lost its implicit mapping state (e.g., due to a crash).
      Note that some PCP servers and some PCP-controlled devices are
      expected to not support this functionality and will respond with a
      PCP error.

      If sent after, this is considered an "implicit dynamic mapping".
      This allows the client to learn the IP address, port, and lifetime
      of the assigned External Address and Port for the implicit
      mapping, and to extend this lifetime (for the purpose described in
      Section 8.3).


Does this text help, or hurt?  

-d


>    > PS: as in the other case, PCP before, one can use MAP to get the
>    > explicit mapping (s)he wants IMHO this makes PEER useless.
> 
>    They are certainly similar.  But they're not the same.
> 
>    PEER's creation of an explicit mapping is supposed to work
>    exactly as if a TCP SYN were sent by the client.
> 
> => I can't parse this statement as a TCP SYN creates an
> implicit dynamic mapping which is not the same than an explicit
> dynamic mapping (here I use the PCP terminology, not the common
> meaning of the word "explicit").
> 
>    Which (TCP SYN) on many NATs creates a different mapping and
>    different filtering than if MAP or UPnP IGD or NAT-PMP or a web
>    page is used to configure port forwarding.
> 
> => so you agree on many NATs the implicit dynamic mapping from
> a TCP SYN is different than an explicit dynamic mapping or
> a static mapping? So I don't understand why PEER is no longer
> specified to act on implicit dynamic mappings??
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: I strongly suggest to replace the word explicit by a
> synonym in the PEER text so the fact the PEER action is
> by definition explicit can no longer lead to confusion
> with the PCP terminology.


From dwing@cisco.com  Thu Oct 13 14:03: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 171B521F8BE9 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.284
X-Spam-Level: 
X-Spam-Status: No, score=-102.284 tagged_above=-999 required=5 tests=[AWL=0.315, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2281AnyQpFf for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:03:47 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 8BBDC21F8B06 for <pcp@ietf.org>; Thu, 13 Oct 2011 14:03:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=828; q=dns/txt; s=iport; t=1318539827; x=1319749427; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=JSNrBTy0UVvxThPe/Jf1pRSVFMf0pZXWiu4rMSWExls=; b=hKuVfnoUxFF+gffRjUXXmlXhhF1AAsBbcwttUOMUtzYSx1ODmPHp4LZB r2u0JMB5Dbj7Wt6X9fHACVCaYTr2WxddVrdDlu1381+5VwCuS4pLvbr2M /xQexCP6VR5U7e7691L9+39YDWImgmH1YZeorfbuABThKT6nLZq6+EePI Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAAM1Rl06rRDoH/2dsb2JhbABDmTWBbI06gQWBUwEBAQQICgEXEDMYAQMCCQ8BAQQBASgHGSMKCQgBAQQBEgsQB6B8AZ4sh20EiAGdbA
X-IronPort-AV: E=Sophos;i="4.69,342,1315180800";  d="scan'208";a="7721393"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 13 Oct 2011 21:03:47 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9DL3lOl022980; Thu, 13 Oct 2011 21:03:47 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110131313.p9DDD8d8061746@givry.fdupont.fr>
In-Reply-To: <201110131313.p9DDD8d8061746@givry.fdupont.fr>
Date: Thu, 13 Oct 2011 14:03:47 -0700
Message-ID: <01fe01cc89eb$99a3a3e0$cceaeba0$@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: AcyJqeKIFiY6Y5Q5SLuSYDWTjqVH6AAQXdfQ
Content-Language: en-us
Subject: Re: [pcp] learning the external address
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, 13 Oct 2011 21:03:48 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, October 13, 2011 6:13 AM
> To: pcp@ietf.org
> Subject: [pcp] learning the external address
> 
> I am not happy with section 9.7 "Learning the External IP Address
> Alone",
> first the term "costemic" ignores this is required to implement IWF,
> second the proposed solution is inefficient and underspecified.
> In conclusion this seems as nobody cares about addressing the
> problem...

Then create a mapping, and keep the mapping alive.  If it expires,
the CGN is fully within its rights to change your IP address.  Same
as with DHCP -- once your lease expires you cannot reasonably expect
to get the same IP address later (it may have been given to somebody
else).

-d



From Francis.Dupont@fdupont.fr  Thu Oct 13 14:04:12 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 3425921F8BF6 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[AWL=0.227,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cFLjM0twYxL0 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:04:11 -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 6C27D21F8B37 for <pcp@ietf.org>; Thu, 13 Oct 2011 14:04:08 -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 p9DL45oM090309; Thu, 13 Oct 2011 23:04:05 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110132104.p9DL45oM090309@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 13 Oct 2011 11:22:10 PDT. <00fd01cc89d5$05b1cec0$11156c40$@com> 
Date: Thu, 13 Oct 2011 23:04:05 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] PEER vs. explicit mappings
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, 13 Oct 2011 21:04:12 -0000

 In your previous mail you wrote:

   Here is my current work-in-progress text regarding this point in -15,
   
      10.2.  Generating a PEER Request
   
      This section describes the operation of a client when generating a
      message with the PEER Opcode.
   
      The PEER Opcode MAY be sent before or after establishing bi-
      directional communication with the remote peer.
   
         If sent before, this is considered an "explicit dynamic mapping",

=> why the quotes? implicit dynamic mapping and explicit dynamic
mapping are defined in the terminology.

         and the PEER Opcode will create a new explicit mapping in the PCP-
         controlled device, which will be used for translating traffic to
         and from the remote peer; this mapping functions the same as if an
         implicit dynamic mapping were created (e.g., because of a TCP SYN
         from the client).

=> so why not create an implicit dynamic mapping?

         This is useful for restoring a mapping after a
         NAT has lost its implicit mapping state (e.g., due to a crash).

=> it is easier to restore the mapping with a mapping of the same
kind (I don't say it will always work but it reduces the number of
cases where it is sure to never work).

         Note that some PCP servers and some PCP-controlled devices are
         expected to not support this functionality and will respond with a
         PCP error.
   
=> I agree with this statement: NATs with strong port randomization
could return a CANNOT_PROVIDE_EXTERNAL_PORT error.

         If sent after, this is considered an "implicit dynamic mapping".

=> I have a real concern about a behavior depending on the NAT state
which is by definition unknown by the client, in particular after
NAt reboot. And I can't see any reason for such a complexity.

         This allows the client to learn the IP address, port, and lifetime
         of the assigned External Address and Port for the implicit
         mapping, and to extend this lifetime (for the purpose described in
         Section 8.3).
   
   Does this text help, or hurt?  
   
=> it is better but what I really want is the PEER command to act
in all cases on implicit dynamic mappings.
I have a proposal: just say for the first part the PCP server SHOULD
create an implicit dynamic mapping and if this operation is not supported
by the NAT it MAY create a mapping which cannot be distinguished from
an implicit dynamic mapping by the PCP client (for instance its lifetime
cannot be reduced, it is not deleted by MAP with lifetime=0, etc).

BTW this means we can get real implicit dynamic mappings and
similar to implicit dynamic mappings, or with other words the
definition of implicit dynamic mappings in PEER is behavioral.

Now you can explain what is the problem with 100% pure/real implicit
dynamic mappings because I can't see one.
   
Regards

Francis.Dupont@fdupont.fr

From dwing@cisco.com  Thu Oct 13 14:06:55 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 CFCCE21F8A91 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.308
X-Spam-Level: 
X-Spam-Status: No, score=-102.308 tagged_above=-999 required=5 tests=[AWL=0.291, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBO4qS2GyTBq for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:06:55 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3FDB121F8A64 for <pcp@ietf.org>; Thu, 13 Oct 2011 14:06:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1245; q=dns/txt; s=iport; t=1318540015; x=1319749615; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=dQCl8So2zA8itbKkQbDrkWoRA+vrR4yzbWfpIlt2s4w=; b=HFqNXFeX4EOIPgNrtKum0WPLUBN2WsPqulPfYQ0iCqmGzU9mHJv+zEJB MsUWYfznuU+mOx/SVLJrLXgCDxvRW5CN/uE0XDDicW+AWBSwcTfxngQDg qZYBoaP6LxxV8vENsn353n72nqcCGhjdq06VaszH/tz8qvksWruTJ2Qav 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAACJSl06rRDoG/2dsb2JhbABDmTWBbI06gQWBUwEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsXh1wImRgBnikDh20EiAGdbA
X-IronPort-AV: E=Sophos;i="4.69,342,1315180800";  d="scan'208";a="7737684"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 13 Oct 2011 21:06:55 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9DL6sfC011150; Thu, 13 Oct 2011 21:06:54 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110131426.p9DEQgeY066141@givry.fdupont.fr>
In-Reply-To: <201110131426.p9DEQgeY066141@givry.fdupont.fr>
Date: Thu, 13 Oct 2011 14:06:54 -0700
Message-ID: <020f01cc89ec$0969d640$1c3d82c0$@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: AcyJtCoUTRHhutcaQLmwzVYx+HdncwAN8y3Q
Content-Language: en-us
Subject: Re: [pcp] NAT chains
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, 13 Oct 2011 21:06:55 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, October 13, 2011 7:27 AM
> To: pcp@ietf.org
> Subject: [pcp] NAT chains
> 
> In base 14 section 7.3 I can read:
> 
>    If the PCP Client's IP Address and PCP Client's Port fields of the
>    PCP response header do not match the source address and port of the
>    request, it indicates the presence of a NAT between the PCP client
>    and PCP server.  If they don't match, then the PCP client (or the
>    user on the client host) MUST ensure that an appropriate NAT mapping
>    is created on the intervening NAT(s) (e.g., using UPnP IGD, NAT-PMP,
>    or manual configuration), otherwise, the PCP-installed mapping will
>    be ineffective.
> 
> I note PCP is not in the examples (i.e., then "e.g." list).

Examples are seldom, if ever, fully inclusive.

> There are least two moderately incompatible ways to handle NAT chains
> in PCP, I'll develop this point when the base spec will be ready.

-d


> Regards
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From Francis.Dupont@fdupont.fr  Thu Oct 13 14:22:47 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 E9B0A21F8B9B for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:22:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.385
X-Spam-Level: 
X-Spam-Status: No, score=-2.385 tagged_above=-999 required=5 tests=[AWL=0.214,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-WT+3kwY7LI for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:22:47 -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 3557021F8B72 for <pcp@ietf.org>; Thu, 13 Oct 2011 14:22:47 -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 p9DLMipq091439; Thu, 13 Oct 2011 23:22:44 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110132122.p9DLMipq091439@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 13 Oct 2011 14:03:47 PDT. <01fe01cc89eb$99a3a3e0$cceaeba0$@com> 
Date: Thu, 13 Oct 2011 23:22:44 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 13 Oct 2011 21:22:48 -0000

 In your previous mail you wrote:

   > I am not happy with section 9.7 "Learning the External IP Address
   > Alone",
   > first the term "costemic" ignores this is required to implement IWF,
   > second the proposed solution is inefficient and underspecified.
   > In conclusion this seems as nobody cares about addressing the
   > problem...
   
   Then create a mapping, and keep the mapping alive.

=> it is the obvious solution but IMHO it is important enough to get
its own document.

   Same as with DHCP -- once your lease expires you cannot reasonably
   expect to get the same IP address later (it may have been given to
   somebody else).
   
=> in fact I have seen only two behaviors from DHCP servers; either
they try hard to always give the same address, or they try hard
to change the address after a known delay, typically each 24 hours,
and reseting the underlying layer so no relying on the lease expiry...

I expect to get the same thing(s) with CGNs and BTW I already suggested
to change MAP and PEER responses to include the assigned external
address when the NAT has one (only one, i.e., not none or more than one)
external address candidate for the PCP client. Note to copy the
suggested external *address* to the response is useless...

Regards

Francis.Dupont@fdupont.fr

From rpenno@juniper.net  Thu Oct 13 14:28:17 2011
Return-Path: <rpenno@juniper.net>
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 B40B221F8ADE for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:28:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lmzlFq39FT-s for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:28:17 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 89E3B21F8ABD for <pcp@ietf.org>; Thu, 13 Oct 2011 14:28:14 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP;  Thu, 13 Oct 2011 14:28:16 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.83.0; Thu, 13 Oct 2011 14:25:26 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 13 Oct 2011 17:25:24 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, Dan Wing <dwing@cisco.com>
Date: Thu, 13 Oct 2011 17:25:22 -0400
Thread-Topic: [pcp] PEER vs. explicit mappings
Thread-Index: AcyJ66p7mu/7qGzeRm23Q449k60miwAAvK9X
Message-ID: <CABCA552.54F74%rpenno@juniper.net>
In-Reply-To: <201110132104.p9DL45oM090309@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] PEER vs. explicit mappings
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, 13 Oct 2011 21:28:17 -0000

I propose to drop 'implicit' vs. 'explicit' and just call 'PEER mappings'.

Whether a session was created by the PEER message or taken over by a PEER
message, the end result is the same. You have a peer map with the same
characteristic irrespective of how it got to be a peer map.

Thanks,

Reinaldo


On 10/13/11 2:04 PM, "Francis Dupont" <Francis.Dupont@fdupont.fr> wrote:

>  In your previous mail you wrote:
>=20
>    Here is my current work-in-progress text regarding this point in -15,
>   =20
>       10.2.  Generating a PEER Request
>   =20
>       This section describes the operation of a client when generating a
>       message with the PEER Opcode.
>   =20
>       The PEER Opcode MAY be sent before or after establishing bi-
>       directional communication with the remote peer.
>   =20
>          If sent before, this is considered an "explicit dynamic mapping"=
,
>=20
> =3D> why the quotes? implicit dynamic mapping and explicit dynamic
> mapping are defined in the terminology.
>=20
>          and the PEER Opcode will create a new explicit mapping in the PC=
P-
>          controlled device, which will be used for translating traffic to
>          and from the remote peer; this mapping functions the same as if =
an
>          implicit dynamic mapping were created (e.g., because of a TCP SY=
N
>          from the client).
>=20
> =3D> so why not create an implicit dynamic mapping?
>=20
>          This is useful for restoring a mapping after a
>          NAT has lost its implicit mapping state (e.g., due to a crash).
>=20
> =3D> it is easier to restore the mapping with a mapping of the same
> kind (I don't say it will always work but it reduces the number of
> cases where it is sure to never work).
>=20
>          Note that some PCP servers and some PCP-controlled devices are
>          expected to not support this functionality and will respond with=
 a
>          PCP error.
>   =20
> =3D> I agree with this statement: NATs with strong port randomization
> could return a CANNOT_PROVIDE_EXTERNAL_PORT error.
>=20
>          If sent after, this is considered an "implicit dynamic mapping".
>=20
> =3D> I have a real concern about a behavior depending on the NAT state
> which is by definition unknown by the client, in particular after
> NAt reboot. And I can't see any reason for such a complexity.
>=20
>          This allows the client to learn the IP address, port, and lifeti=
me
>          of the assigned External Address and Port for the implicit
>          mapping, and to extend this lifetime (for the purpose described =
in
>          Section 8.3).
>   =20
>    Does this text help, or hurt?
>   =20
> =3D> it is better but what I really want is the PEER command to act
> in all cases on implicit dynamic mappings.
> I have a proposal: just say for the first part the PCP server SHOULD
> create an implicit dynamic mapping and if this operation is not supported
> by the NAT it MAY create a mapping which cannot be distinguished from
> an implicit dynamic mapping by the PCP client (for instance its lifetime
> cannot be reduced, it is not deleted by MAP with lifetime=3D0, etc).
>=20
> BTW this means we can get real implicit dynamic mappings and
> similar to implicit dynamic mappings, or with other words the
> definition of implicit dynamic mappings in PEER is behavioral.
>=20
> Now you can explain what is the problem with 100% pure/real implicit
> dynamic mappings because I can't see one.
>   =20
> Regards
>=20
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From Francis.Dupont@fdupont.fr  Thu Oct 13 14:33: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 1398E21F8AD9 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.396
X-Spam-Level: 
X-Spam-Status: No, score=-2.396 tagged_above=-999 required=5 tests=[AWL=0.203,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ofMg80d925Jn for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:33: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 33F5E21F8564 for <pcp@ietf.org>; Thu, 13 Oct 2011 14:33:18 -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 p9DLXHuo092107 for <pcp@ietf.org>; Thu, 13 Oct 2011 23:33:17 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110132133.p9DLXHuo092107@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 13 Oct 2011 23:33:17 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] renewal time
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, 13 Oct 2011 21:33:19 -0000

I don't know what is the "renewal time" in (base 14 9.2.1):

   Regardless of the assigned lifetime of a mapping, the PCP client
   SHOULD impose an upper limit on the renewal time it uses for
   mappings.  A maximum renewal time of 2 hours is RECOMMENDED.

it seems it is the time before the expiry, i.e., the difference
between the expiry date and the renewal date, but IMHO a clarification
will be wellcome.

Regards

Francis.Dupont@fdupont.fr

From dwing@cisco.com  Thu Oct 13 14:36:06 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 83CCE21F8508 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.329
X-Spam-Level: 
X-Spam-Status: No, score=-102.329 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k4jA8oQ1aRas for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:36:06 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 07CD321F84C9 for <pcp@ietf.org>; Thu, 13 Oct 2011 14:36:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1794; q=dns/txt; s=iport; t=1318541766; x=1319751366; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=vQSVQn88OjtSNmoSsz2Vcw79xr4OwfcZjU9wSK+x86w=; b=Gkui8B8D0QuWQi1l7Qk05J/0qLefnxkIGBGW8RaQyX8+wPKzfZBVDRoz N+Cr/+rVuR8U0XE0nVf/LA1ThLbv5uVl7DjFp5Iao5K9wzhMZW1aebYmO bb4QXZF0V2hRLQ6qre6bHRcUc4gofiXk7oMdXD0JpaebBxp3mLVgzQVTm 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUBAJRYl06rRDoJ/2dsb2JhbABDmTVDgSmNOoEFgVMBAQEDAQgKARcQMwwFBwEDAgkPAQEEAQEBJwcZIwoJCAEBBBMLEAeHXJkZAZ4qh20EiAGdbA
X-IronPort-AV: E=Sophos;i="4.69,342,1315180800";  d="scan'208";a="7727781"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 13 Oct 2011 21:36:05 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9DLa5QQ015568; Thu, 13 Oct 2011 21:36:05 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Thu, 13 Oct 2011 14:03:47 PDT. <01fe01cc89eb$99a3a3e0$cceaeba0$@com> <201110132122.p9DLMipq091439@givry.fdupont.fr>
In-Reply-To: <201110132122.p9DLMipq091439@givry.fdupont.fr>
Date: Thu, 13 Oct 2011 14:36:05 -0700
Message-ID: <023201cc89f0$1cf7a5d0$56e6f170$@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: AcyJ7kFwzVObsSgwRLyFvgCByIVTEwAAax1g
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 13 Oct 2011 21:36:06 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Thursday, October 13, 2011 2:23 PM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] learning the external address
> 
> 
>  In your previous mail you wrote:
> 
>    > I am not happy with section 9.7 "Learning the External IP Address
>    > Alone",
>    > first the term "costemic" ignores this is required to implement
> IWF,
>    > second the proposed solution is inefficient and underspecified.
>    > In conclusion this seems as nobody cares about addressing the
>    > problem...
> 
>    Then create a mapping, and keep the mapping alive.
> 
> => it is the obvious solution but IMHO it is important enough to get
> its own document.
> 
>    Same as with DHCP -- once your lease expires you cannot reasonably
>    expect to get the same IP address later (it may have been given to
>    somebody else).
> 
> => in fact I have seen only two behaviors from DHCP servers; either
> they try hard to always give the same address, or they try hard
> to change the address after a known delay, typically each 24 hours,
> and reseting the underlying layer so no relying on the lease expiry...
> 
> I expect to get the same thing(s) with CGNs and BTW I already suggested
> to change MAP and PEER responses to include the assigned external
> address when the NAT has one (only one, i.e., not none or more than
> one)
> external address candidate for the PCP client. Note to copy the
> suggested external *address* to the response is useless...

Without a lifetime for that address, it is irresponsible to
tell the client the external IP address -- even if there is only
one external IP address.

-d


> Regards
> 
> Francis.Dupont@fdupont.fr


From Francis.Dupont@fdupont.fr  Thu Oct 13 14:46:28 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 279C921F8A64 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.406
X-Spam-Level: 
X-Spam-Status: No, score=-2.406 tagged_above=-999 required=5 tests=[AWL=0.193,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WZtsBIgU7MFP for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:46:27 -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 6C24121F8A58 for <pcp@ietf.org>; Thu, 13 Oct 2011 14:46:27 -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 p9DLkQpc092856 for <pcp@ietf.org>; Thu, 13 Oct 2011 23:46:26 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110132146.p9DLkQpc092856@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 13 Oct 2011 23:46:26 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] existing mapping and PREFER_FAILURE
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, 13 Oct 2011 21:46:28 -0000

In base 14 section 9.3 (Processing a MAP request):

   If a mapping already exists for the requested Internal Address and
   Port, the PCP server MUST refresh the lifetime of that already-
   existing mapping, and return the already-existing External Address
   and Port in its response, regardless of the Suggested External
   Address and Port
                   ^ missing . here

I believe this doesn't apply when the request has a PREFER_FAILURE
option, does it? So I'd like to get it in the text.

And BTW there is nothing when the already existing mapping is
not an explicit dynamic mapping:
 - the behavior when it is an implicit dynamic mapping is NAT dependent,
  i.e., the NAT should promote it to an explicit dynamic mapping or
  raise an error if it can't
 - the behavior when it is a static mapping is specified later but
  as it roughly follows the current text IMHO for this case we can keep it.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Thu Oct 13 14:56:11 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 AE89421F86AA for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.415
X-Spam-Level: 
X-Spam-Status: No, score=-2.415 tagged_above=-999 required=5 tests=[AWL=0.184,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pR6qM11KILsT for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 14:56:11 -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 E42CC21F85FF for <pcp@ietf.org>; Thu, 13 Oct 2011 14:56:10 -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 p9DLuA3n093447 for <pcp@ietf.org>; Thu, 13 Oct 2011 23:56:10 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110132156.p9DLuA3n093447@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 13 Oct 2011 23:56:10 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] minor incoherence in base 14 9.3
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, 13 Oct 2011 21:56:11 -0000

In base 14 section 9.3:

   o  The PREFER_FAILURE option is included in the request and the
      Suggested External Address is not assignable to the PCP client.

=> even I believe this should stand it is not (yet) compatible
with the current definition of PREFER_FAILURE and BTW there is
no (yet) a corresponding error...

Regards

Francis.Dupont@fdupont.fr

PS: BTW IMHO it is already covered by:

   o  The Suggested External Address and Port is otherwise prohibited by
      the PCP server's policy.

which is a previous item of the list...

From dwing@cisco.com  Thu Oct 13 15:26:11 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 7270321F8634 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.347
X-Spam-Level: 
X-Spam-Status: No, score=-102.347 tagged_above=-999 required=5 tests=[AWL=0.252, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LC93+vAqBkC1 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:26:09 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 96D9221F84FB for <pcp@ietf.org>; Thu, 13 Oct 2011 15:26:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2758; q=dns/txt; s=iport; t=1318544767; x=1319754367; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=pGznU2Nj2apnHwlzvqwX71m/zvr4dscmLfTPkbvYw+w=; b=TBnG0edm5LUfahEt4UUqZSKbkin2KEZNyCpTrK/xm1uUSUhnnDMhd/AV K7eoKSmalTA+fZxTIstVY+RoG0k1E4MWB3oG5QVK7nRcGiQ4KtqJhf6fB w6ph2/IOo8Oal4JcQzvO3sltmVkYIoFmGBUxiJkkhZI8mrdE+kka5YNCT k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAANtkl06rRDoJ/2dsb2JhbABDmTWBbI06gQWBUwEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsXh1wImQ0BnicDh20EiAGUWokS
X-IronPort-AV: E=Sophos;i="4.69,342,1315180800";  d="scan'208";a="7751986"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 13 Oct 2011 22:26:07 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9DMQ7MN013751; Thu, 13 Oct 2011 22:26:07 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110132146.p9DLkQpc092856@givry.fdupont.fr>
In-Reply-To: <201110132146.p9DLkQpc092856@givry.fdupont.fr>
Date: Thu, 13 Oct 2011 15:26:07 -0700
Message-ID: <027501cc89f7$1a182860$4e487920$@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: AcyJ8ZUwxJvBmnf5RJe4D0Mw0IWVGgAA2S0g
Content-Language: en-us
Subject: Re: [pcp] existing mapping and PREFER_FAILURE
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, 13 Oct 2011 22:26:11 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, October 13, 2011 2:46 PM
> To: pcp@ietf.org
> Subject: [pcp] existing mapping and PREFER_FAILURE
> 
> In base 14 section 9.3 (Processing a MAP request):
> 
>    If a mapping already exists for the requested Internal Address and
>    Port, the PCP server MUST refresh the lifetime of that already-
>    existing mapping, and return the already-existing External Address
>    and Port in its response, regardless of the Suggested External
>    Address and Port
>                    ^ missing . here
> 
> I believe this doesn't apply when the request has a PREFER_FAILURE
> option, does it? So I'd like to get it in the text.
>
> And BTW there is nothing when the already existing mapping is
> not an explicit dynamic mapping:
>  - the behavior when it is an implicit dynamic mapping is NAT
> dependent,
>   i.e., the NAT should promote it to an explicit dynamic mapping

Ok, new text:

        <t>If a mapping already exists for the requested Internal
        Address and Port and the PREFER_FAILURE Option is not present,
        the PCP server MUST refresh the lifetime of that
        already-existing mapping, and return the already-existing
        External Address and Port in its response, regardless of the
        Suggested External Address and Port in the request.  If a
        mapping already exists for the requested Internal Address and Port
        the request contains the PREFER_FAILURE Option, but the
        Suggested External Address and Port do not match the actual
        External Address and Port of the already existing mapping, the
        error CANNOT_PROVIDE_EXTERNAL_PORT is returned.  If an implicit
        mapping already exists for the requested Internal Address
        and Port, the mapping SHOULD be upgraded to an explicit mapping.</t>

I'm tempted to make it 'MUST upgrade', in fact, for reason I describe
below.

> or
>   raise an error if it can't

If it can't, it's broken.  We don't want to encourage such implementations,
because they push the problem back to the PCP client to resolve -- and 
sometimes the PCP client _cannot_ resolve it (try getting FTP or ssh
to listen on a non-default port makes it hard for all of the local 
devices connecting to deal with the non-default port).


-d

>  - the behavior when it is a static mapping is specified later but
>   as it roughly follows the current text IMHO for this case we can keep
> it.
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Thu Oct 13 15:26:57 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 DA87621F84FB for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.363
X-Spam-Level: 
X-Spam-Status: No, score=-102.363 tagged_above=-999 required=5 tests=[AWL=0.236, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LiAU44IpdT-M for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:26:57 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 77C0E21F8634 for <pcp@ietf.org>; Thu, 13 Oct 2011 15:26:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=192; q=dns/txt; s=iport; t=1318544817; x=1319754417; h=from:to:subject:date:message-id:mime-version: content-transfer-encoding; bh=N0iCApdzilb/5EDtJRW5uXCHSCGGILii+KoK2UIafyg=; b=gB1EYbPGDEIqp4Z5IgK/7I1dMbZTj3k6CO0Ukld0UDDSO83rm30uVn4R ZcgA/yUtNs9DYLI/tmyHxcpDOgFPIbPrpmf9WOw3X1VyL//JCvoZHiliv kCq1FZNg87Vg2BDcO3icQD2l2ff4Q3vREkcFxF9azkvzohtKgjUC41yYz c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak8IAIhkl06rRDoG/2dsb2JhbABDmXiBKY06gQWBWggKARcQTAUYUCMcAQQeF59SgSYBniqHbQSIAZRaiRI
X-IronPort-AV: E=Sophos;i="4.69,342,1315180800";  d="scan'208";a="7769415"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 13 Oct 2011 22:26:57 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9DMQvjt028341 for <pcp@ietf.org>; Thu, 13 Oct 2011 22:26:57 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <pcp@ietf.org>
Date: Thu, 13 Oct 2011 15:26:57 -0700
Message-ID: <027601cc89f7$37cb4ea0$a761ebe0$@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: AcyJ9zeRUfmn3CvrQTGIhCrRS8s2bA==
Content-Language: en-us
Subject: [pcp] combining errors SERVER_OVERLOADED and NO_RESOURCES
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, 13 Oct 2011 22:26:58 -0000

Can anyone describe where a client would do something different, or
otherwise care, to distinguish between SERVER_OVERLOADED and NO_RESOURCES?

If not, they will be combined in -15.

-d



From dwing@cisco.com  Thu Oct 13 15:31:44 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 D862F21F8B37 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:31:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.377
X-Spam-Level: 
X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2-4hOnIc-EnT for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:31:44 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 55D1B21F8AE9 for <pcp@ietf.org>; Thu, 13 Oct 2011 15:31:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1049; q=dns/txt; s=iport; t=1318545104; x=1319754704; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=xunpApxdYculHRw9pi/2iR2fkSz/ce1Vgaest76bv1Q=; b=GWLONlYEhCQ0C5HGrc86xDbKvnC+2At4gFOVVKrokODQPVrMjN8CDYly +uNiOyusuaNTuSDXvpCdmTV2xQtjedM/HF31HaOUGPFZyRGC3bk2Cofju AbncD1ppeTLinWSdkzhDSpjQuKg2Odm1c+zdo+paaAXrOCATvCJxb2bSI o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAAI5ll06rRDoJ/2dsb2JhbABDmTWBbI06gQWBUwEBAQQICgEXEEsBAwIJDwEBBAEBKAcZIwoJCAEBBAESCxegcQGeKYdtBIgBnWw
X-IronPort-AV: E=Sophos;i="4.69,343,1315180800";  d="scan'208";a="7770190"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 13 Oct 2011 22:31:44 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9DMVhJ5016248; Thu, 13 Oct 2011 22:31:44 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110132133.p9DLXHuo092107@givry.fdupont.fr>
In-Reply-To: <201110132133.p9DLXHuo092107@givry.fdupont.fr>
Date: Thu, 13 Oct 2011 15:31:43 -0700
Message-ID: <027701cc89f7$e2c0b7f0$a84227d0$@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: AcyJ77vt/Gj6bpRWQfyDS5TwCuAlagAB9jAw
Content-Language: en-us
Subject: Re: [pcp] renewal time
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, 13 Oct 2011 22:31:45 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, October 13, 2011 2:33 PM
> To: pcp@ietf.org
> Subject: [pcp] renewal time
> 
> I don't know what is the "renewal time" in (base 14 9.2.1):
> 
>    Regardless of the assigned lifetime of a mapping, the PCP client
>    SHOULD impose an upper limit on the renewal time it uses for
>    mappings.  A maximum renewal time of 2 hours is RECOMMENDED.
> 
> it seems it is the time before the expiry, i.e., the difference
> between the expiry date and the renewal date, but IMHO a clarification
> will be wellcome.

New text:

        Regardless of the Assigned Lifetime of a mapping, the PCP
        client SHOULD impose an upper limit on this returned value,
        and 2 hours is RECOMMENDED.  This means if the PCP server
        returns an absurdly long Assigned Lifetime (e.g., 5 years),
        the PCP client will behave as if it received a more sane value
        (e.g., 2 hours).

-d



From rpenno@juniper.net  Thu Oct 13 15:35:05 2011
Return-Path: <rpenno@juniper.net>
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 589CD21F8B61 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NB3XPIOjid6c for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:35:04 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 99C7921F8B53 for <pcp@ietf.org>; Thu, 13 Oct 2011 15:34:56 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP;  Thu, 13 Oct 2011 15:35:04 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.83.0; Thu, 13 Oct 2011 15:33:43 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 13 Oct 2011 18:33:42 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Dan Wing <dwing@cisco.com>, 'Francis Dupont' <Francis.Dupont@fdupont.fr>,  "pcp@ietf.org" <pcp@ietf.org>
Date: Thu, 13 Oct 2011 18:33:40 -0400
Thread-Topic: [pcp] renewal time
Thread-Index: AcyJ77vt/Gj6bpRWQfyDS5TwCuAlagAB9jAwAAAkyfA=
Message-ID: <CABCB554.54FA7%rpenno@juniper.net>
In-Reply-To: <027701cc89f7$e2c0b7f0$a84227d0$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] renewal time
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, 13 Oct 2011 22:35:05 -0000

This is confusing. Does it mean that lifetimes > 2 hours are no-op?


On 10/13/11 3:31 PM, "Dan Wing" <dwing@cisco.com> wrote:

>> will be wellcome.
>=20
> New text:
>=20
>         Regardless of the Assigned Lifetime of a mapping, the PCP
>         client SHOULD impose an upper limit on this returned value,
>         and 2 hours is RECOMMENDED.  This means if the PCP server
>         returns an absurdly long Assigned Lifetime (e.g., 5 years),
>         the PCP client will behave as if it received a more sane value
>         (e.g., 2 hours).
>=20
> -d


From dwing@cisco.com  Thu Oct 13 15:39:38 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 76C2821F8B75 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.389
X-Spam-Level: 
X-Spam-Status: No, score=-102.389 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Efs05FPx1BL9 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:39:38 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 17BCD21F8B72 for <pcp@ietf.org>; Thu, 13 Oct 2011 15:39:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1052; q=dns/txt; s=iport; t=1318545578; x=1319755178; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=vjUFmuFyE44LKqrNNmSN3jQV1araxV2HMuQfxx4xYjI=; b=FqKs1Jhc/XCHB2mN2rOkCam/yqgyfY+53uBYnvK6sLUmYbMgc9BfQDp9 6awwGUMpju5EfPB6za6/elyVSpvrRomlknDStxNxayiDdRN1fzzaNZREk UEC9yD1DKddOFe8DW+yfgXxrQDka0Gh0T/dFZvR48+TcpvhpSvP2J7B6I M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAAFtol06rRDoG/2dsb2JhbABDmTWBbI06gQWBUwEBAQMBCAoBFxBEBwEDAgkOAQEBBAEBAScHGSMKCQgBAQQBEgsXh1yZFwGeJ4dtBIgBnWw
X-IronPort-AV: E=Sophos;i="4.69,343,1315180800";  d="scan'208";a="7754157"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 13 Oct 2011 22:39:38 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9DMdb5d002635; Thu, 13 Oct 2011 22:39:37 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Reinaldo Penno'" <rpenno@juniper.net>, "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <027701cc89f7$e2c0b7f0$a84227d0$@com> <CABCB554.54FA7%rpenno@juniper.net>
In-Reply-To: <CABCB554.54FA7%rpenno@juniper.net>
Date: Thu, 13 Oct 2011 15:39:37 -0700
Message-ID: <028e01cc89f8$fd2a14f0$f77e3ed0$@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: AcyJ77vt/Gj6bpRWQfyDS5TwCuAlagAB9jAwAAAkyfAAACTG4A==
Content-Language: en-us
Subject: Re: [pcp] renewal time
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, 13 Oct 2011 22:39:38 -0000

> -----Original Message-----
> From: Reinaldo Penno [mailto:rpenno@juniper.net]
> Sent: Thursday, October 13, 2011 3:34 PM
> To: Dan Wing; 'Francis Dupont'; pcp@ietf.org
> Subject: Re: [pcp] renewal time
> 
> This is confusing. Does it mean that lifetimes > 2 hours are no-op?

We clearly need some sort of min() function on the returned Lifetime --
a lifetime of 5 years is a good example of an absurd value that
can legally be returned by the PCP server.

Do you want a higher value, such as 24 hours?

-d



> On 10/13/11 3:31 PM, "Dan Wing" <dwing@cisco.com> wrote:
> 
> >> will be wellcome.
> >
> > New text:
> >
> >         Regardless of the Assigned Lifetime of a mapping, the PCP
> >         client SHOULD impose an upper limit on this returned value,
> >         and 2 hours is RECOMMENDED.  This means if the PCP server
> >         returns an absurdly long Assigned Lifetime (e.g., 5 years),
> >         the PCP client will behave as if it received a more sane
> value
> >         (e.g., 2 hours).
> >
> > -d


From dwing@cisco.com  Thu Oct 13 15:42:50 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 E3B6821F8B75 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.4
X-Spam-Level: 
X-Spam-Status: No, score=-102.4 tagged_above=-999 required=5 tests=[AWL=0.199,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K8pct29G99QC for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:42:50 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 6C1FD21F8B26 for <pcp@ietf.org>; Thu, 13 Oct 2011 15:42:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=551; q=dns/txt; s=iport; t=1318545770; x=1319755370; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=0+ues8FtAnKZwktHzm2zjPZLZC/cYbcZXY6MrYVQ4qw=; b=nH2OgwpXZ5G0TaShcFRxqOXd0zvxvayI0/wedEeb9+s916s1nj2/GZkv bx5Jy/iZRoCWXe21oo0nZk+quguvTac6n4Q2oG7F45KsaA49H+6IhZAXn XyxX+iSja+YJ2vLUaQFxV3L5riOJEckXnBsH33X1fWQOehx1eTR/31jal k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAAEJpl06rRDoG/2dsb2JhbABDmTWBbI06gQWBUwEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsXh1wImQ4BniQDh20EiAGdbA
X-IronPort-AV: E=Sophos;i="4.69,343,1315180800";  d="scan'208";a="7771931"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 13 Oct 2011 22:42:50 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9DMgnhc004245; Thu, 13 Oct 2011 22:42:49 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110131309.p9DD9OOE061502@givry.fdupont.fr>
In-Reply-To: <201110131309.p9DD9OOE061502@givry.fdupont.fr>
Date: Thu, 13 Oct 2011 15:42:49 -0700
Message-ID: <028f01cc89f9$6f9c7b90$4ed572b0$@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: AcyJqulkNqhO+jTMS+e5/omt7pnJWgAToMNw
Content-Language: en-us
Subject: Re: [pcp] DS-Lite modes
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, 13 Oct 2011 22:42:51 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, October 13, 2011 6:09 AM
> To: pcp@ietf.org
> Subject: [pcp] DS-Lite modes
> 
> Can you add a reference to draft-dupont-pcp-dslite in the section 8
> "Introduction to MAP and PEER Opcodes" in the table comments?

Done.

-d


> Thanks
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Thu Oct 13 15:47:13 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 B648221F8B11 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:47:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.41
X-Spam-Level: 
X-Spam-Status: No, score=-102.41 tagged_above=-999 required=5 tests=[AWL=0.189, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dJH2p9nbbT7z for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:47:13 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 2EBF021F8713 for <pcp@ietf.org>; Thu, 13 Oct 2011 15:47:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1056; q=dns/txt; s=iport; t=1318546033; x=1319755633; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=F+1cvy5WbUU2CbbQTZs4KTn1/hraDLTEthuNHjKFlF4=; b=mlJ+jUpzaglQVLsmYiqOr1nIZfjNn2l9CVWwXKi+c5tXKx561g/zJ9O3 6MV07x4bC6gpWWIe1iW6HLCWHFVS9fhPePGaFwdvrP50z+w5iK6QVAaYa hwQFp5VTbfSWCkJaa59w5YqWi+qSDPXaq7Ta9Ulwska1w+eQf30LMSu4a E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAAI5pl06rRDoI/2dsb2JhbABDmTWBbI06gQWBUwEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsXh1wImQ8BniQDh20EiAGdbA
X-IronPort-AV: E=Sophos;i="4.69,343,1315180800";  d="scan'208";a="7755317"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 13 Oct 2011 22:47:12 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p9DMlCBX001629; Thu, 13 Oct 2011 22:47:12 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110132156.p9DLuA3n093447@givry.fdupont.fr>
In-Reply-To: <201110132156.p9DLuA3n093447@givry.fdupont.fr>
Date: Thu, 13 Oct 2011 15:47:12 -0700
Message-ID: <029001cc89fa$0c184c10$2448e430$@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: AcyJ8xBGao9PiSjqRJ+MlefTjKCNZwABraRQ
Content-Language: en-us
Subject: Re: [pcp] minor incoherence in base 14 9.3
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, 13 Oct 2011 22:47:13 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, October 13, 2011 2:56 PM
> To: pcp@ietf.org
> Subject: [pcp] minor incoherence in base 14 9.3
> 
> In base 14 section 9.3:
> 
>    o  The PREFER_FAILURE option is included in the request and the
>       Suggested External Address is not assignable to the PCP client.
> 
> => even I believe this should stand it is not (yet) compatible
> with the current definition of PREFER_FAILURE and BTW there is
> no (yet) a corresponding error...

How is it incompatible with the current definition of PREFER_FAILURE?

> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: BTW IMHO it is already covered by:
> 
>    o  The Suggested External Address and Port is otherwise prohibited
> by
>       the PCP server's policy.
> 
> which is a previous item of the list...

-d

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


From dwing@cisco.com  Thu Oct 13 15:53:46 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 55A5721F8B72 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.419
X-Spam-Level: 
X-Spam-Status: No, score=-102.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rRsCz5QYB1Nr for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 15:53:45 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id B188421F8B34 for <pcp@ietf.org>; Thu, 13 Oct 2011 15:53:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1469; q=dns/txt; s=iport; t=1318546425; x=1319756025; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=cvROSklkbUI2MPGl3+ucSfI+vDM8JWQE5UQzfKTid7Y=; b=VGzj2P21Ak6Xhd2440GU9VU5o0RFIkmN1IwIUHLf+Uc+65QrqY1haODv zbsAFcw3nqu3HaD0vLr7cVgUWjwYianNKN2eUXuhWorbm9Kqr62d86Ytr mHys+OaIr5MpvfA/YLx9a3aJA/LQfatSV9FsNshCUKEFO4JO4cgu4AO8M A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAAItrl06rRDoJ/2dsb2JhbABDmTWBbI06gQWBUwEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsXh1wImQ4BniMDh20EiAGdbA
X-IronPort-AV: E=Sophos;i="4.69,343,1315180800";  d="scan'208";a="7773561"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 13 Oct 2011 22:53:45 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9DMrjjo026119; Thu, 13 Oct 2011 22:53:45 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110131505.p9DF5UaP068562@givry.fdupont.fr>
In-Reply-To: <201110131505.p9DF5UaP068562@givry.fdupont.fr>
Date: Thu, 13 Oct 2011 15:53:45 -0700
Message-ID: <029701cc89fa$f6481450$e2d83cf0$@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: AcyJuY+3vB8a61FuSqi7e+dR6UJGEwAQVrTw
Content-Language: en-us
Subject: Re: [pcp] small proposed addition in 8
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, 13 Oct 2011 22:53:46 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, October 13, 2011 8:06 AM
> To: pcp@ietf.org
> Subject: [pcp] small proposed addition in 8
> 
> In the base 14 section 8 in the figure 6 (table) intro:
> 
> change
>    ... the 'remote peer' is the Remote
>    Peer IP Address of the PEER request.
> by
>    ... the 'remote peer' is the Remote
>    Peer IP Address of the PEER request or the FILTER option
>    of the MAP request
> 
> BTW the 'internal' address definition is not complete, it is from
> the THIRD_PARTY option (lowercase) when it is present or the source
> address when it is not.

New text, with both those changes:


The following table summarizes how various common PCP
deployments use IPv6 and IPv4 addresses.  The 'source' is the source
address of the PCP packet itself, 'internal' is the Internal IP
Address field of the THIRD_PARTY Option (if present) or the same as
the source address of the PCP packet iself (if the THIRD_PARTY Option
is not present), 'external' is the Requested External Address field of
the MAP or PEER request, the 'remote peer' is the Remote Peer IP
Address of the PEER request or the FILTER option of the MAP
request.
 
-d


> Regards
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Thu Oct 13 16:21: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 EFC5C21F8538 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 16:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.427
X-Spam-Level: 
X-Spam-Status: No, score=-102.427 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id syP+REPVz45I for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 16:21:14 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 3E0CC21F8532 for <pcp@ietf.org>; Thu, 13 Oct 2011 16:21:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=4111; q=dns/txt; s=iport; t=1318548074; x=1319757674; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=Gu3Kajrd8H0esc/IGtPYA4/eQHrJz5b+of6QHaCn8BA=; b=AMuFqTYt/zg6VALfftEbMyqeTtEfm8CZULKgvCLXxCIw/4BPe1oL7Pzj FTMInSQDZs37L/uTbv31n0XX4SknGqGIlo0djlnjiuQYYpJvwTnKSJzE9 LNrACJaxXEfVWPXa/2n8JFZj+sTUMGRvTAgLVjVmNVMx4vbkQ4MF6a5T8 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAAJ9xl06rRDoH/2dsb2JhbABDmTWBbI06gQWBUwEBAQMBAQEBBQoBFxA0CwUHAQMCCQ4BAQEEAQEBJwcZDhUKCQgBAQQBEgsXh1wImREBniQDh20EiAGdbA
X-IronPort-AV: E=Sophos;i="4.69,343,1315180800";  d="scan'208";a="7757451"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 13 Oct 2011 23:21:13 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9DNLD8K005014; Thu, 13 Oct 2011 23:21:13 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Reinaldo Penno'" <rpenno@juniper.net>, "'Francis Dupont'" <Francis.Dupont@fdupont.fr>
References: <201110132104.p9DL45oM090309@givry.fdupont.fr> <CABCA552.54F74%rpenno@juniper.net>
In-Reply-To: <CABCA552.54F74%rpenno@juniper.net>
Date: Thu, 13 Oct 2011 16:21:13 -0700
Message-ID: <02be01cc89fe$cce28ec0$66a7ac40$@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: AcyJ66p7mu/7qGzeRm23Q449k60miwAAvK9XAAQJo/A=
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] PEER vs. explicit mappings
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, 13 Oct 2011 23:21:15 -0000

> -----Original Message-----
> From: Reinaldo Penno [mailto:rpenno@juniper.net]
> Sent: Thursday, October 13, 2011 2:25 PM
> To: Francis Dupont; Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] PEER vs. explicit mappings
> 
> I propose to drop 'implicit' vs. 'explicit' and just call 'PEER
> mappings'.
> 
> Whether a session was created by the PEER message or taken over by a
> PEER
> message, the end result is the same. You have a peer map with the same
> characteristic irrespective of how it got to be a peer map.

Works for me.   I'll start making those changes.

-d


> Thanks,
> 
> Reinaldo
> 
> 
> On 10/13/11 2:04 PM, "Francis Dupont" <Francis.Dupont@fdupont.fr>
> wrote:
> 
> >  In your previous mail you wrote:
> >
> >    Here is my current work-in-progress text regarding this point in -
> 15,
> >
> >       10.2.  Generating a PEER Request
> >
> >       This section describes the operation of a client when
> generating a
> >       message with the PEER Opcode.
> >
> >       The PEER Opcode MAY be sent before or after establishing bi-
> >       directional communication with the remote peer.
> >
> >          If sent before, this is considered an "explicit dynamic
> mapping",
> >
> > => why the quotes? implicit dynamic mapping and explicit dynamic
> > mapping are defined in the terminology.
> >
> >          and the PEER Opcode will create a new explicit mapping in
> the PCP-
> >          controlled device, which will be used for translating
> traffic to
> >          and from the remote peer; this mapping functions the same as
> if an
> >          implicit dynamic mapping were created (e.g., because of a
> TCP SYN
> >          from the client).
> >
> > => so why not create an implicit dynamic mapping?
> >
> >          This is useful for restoring a mapping after a
> >          NAT has lost its implicit mapping state (e.g., due to a
> crash).
> >
> > => it is easier to restore the mapping with a mapping of the same
> > kind (I don't say it will always work but it reduces the number of
> > cases where it is sure to never work).
> >
> >          Note that some PCP servers and some PCP-controlled devices
> are
> >          expected to not support this functionality and will respond
> with a
> >          PCP error.
> >
> > => I agree with this statement: NATs with strong port randomization
> > could return a CANNOT_PROVIDE_EXTERNAL_PORT error.
> >
> >          If sent after, this is considered an "implicit dynamic
> mapping".
> >
> > => I have a real concern about a behavior depending on the NAT state
> > which is by definition unknown by the client, in particular after
> > NAt reboot. And I can't see any reason for such a complexity.
> >
> >          This allows the client to learn the IP address, port, and
> lifetime
> >          of the assigned External Address and Port for the implicit
> >          mapping, and to extend this lifetime (for the purpose
> described in
> >          Section 8.3).
> >
> >    Does this text help, or hurt?
> >
> > => it is better but what I really want is the PEER command to act
> > in all cases on implicit dynamic mappings.
> > I have a proposal: just say for the first part the PCP server SHOULD
> > create an implicit dynamic mapping and if this operation is not
> supported
> > by the NAT it MAY create a mapping which cannot be distinguished from
> > an implicit dynamic mapping by the PCP client (for instance its
> lifetime
> > cannot be reduced, it is not deleted by MAP with lifetime=0, etc).
> >
> > BTW this means we can get real implicit dynamic mappings and
> > similar to implicit dynamic mappings, or with other words the
> > definition of implicit dynamic mappings in PEER is behavioral.
> >
> > Now you can explain what is the problem with 100% pure/real implicit
> > dynamic mappings because I can't see one.
> >
> > Regards
> >
> > Francis.Dupont@fdupont.fr
> > _______________________________________________
> > pcp mailing list
> > pcp@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Thu Oct 13 16:28:03 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 4566421F8B34 for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 16:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.435
X-Spam-Level: 
X-Spam-Status: No, score=-102.435 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4N1UHznnS3-H for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 16:28:02 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 90E1B21F8B29 for <pcp@ietf.org>; Thu, 13 Oct 2011 16:28:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2365; q=dns/txt; s=iport; t=1318548482; x=1319758082; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=wRnyO0KhePIaKny/lVKZ9xuUuFeFd62BdScM3yrn1jY=; b=DKrlypvA1/bdSSxaAbtXqPpzDThAOLtKImz1PNElMy3SnHfFF3bHoRlF /EvhzLT7xqSlKdF7XvVwFA6hXd6w8JZUhcSmFGlC6kjEj8a7EdCrQ/04i VdTTPlOg09Yjc61WgiMO8EztZr/XLPEorc0fRJQHMTh3SO5qcZiYU/cYJ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAANZyl06rRDoH/2dsb2JhbAA5Cpk1gWyNOoEFgVMBAQEDAQEBAQUKARcQNBAHAQMCCQ8BAQQBASgHGQ4VCgkIAQEEARILF4dcCJkNAZ4kA4Q+gy8EiAGdbA
X-IronPort-AV: E=Sophos;i="4.69,343,1315180800";  d="scan'208";a="7758770"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 13 Oct 2011 23:28:02 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9DNS2VQ008872; Thu, 13 Oct 2011 23:28:02 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110131349.p9DDnK7C063828@givry.fdupont.fr>
In-Reply-To: <201110131349.p9DDnK7C063828@givry.fdupont.fr>
Date: Thu, 13 Oct 2011 16:28:01 -0700
Message-ID: <02bf01cc89ff$c051e4c0$40f5ae40$@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: AcyJrusvOyELgBhgQECZa31M+Z+pMAAUH1UQ
Content-Language: en-us
Subject: Re: [pcp] fields to copy
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, 13 Oct 2011 23:28:03 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, October 13, 2011 6:49 AM
> To: pcp@ietf.org
> Subject: [pcp] fields to copy
> 
> In draft 14 section 7.2:
> 
>    ... Copying
>    request fields such as Protocol and Internal Port (for MAP requests)
>    and Protocol, Internal Port, Remote Peer IP Address and Port (for
>    PEER requests) is important because this is what enables a client to
>    identify to which request a given error response pertains.
> 
> => in fact in some cases the external port too, and IMHO in all cases
> the Internal address i.e. the THIRD_PARTY option, so I propos:
> 
>    ... Copying
>    request fields such as Protocol and Internal Port, the THIRD_PARTY
>    Option when it is present, and in some cases the External Port (for
>    MAP requests) and Protocol, Internal Port, Remote Peer IP Address
>    and Port, the THIRD_PARTY Option when it is present, and in some
>    cases the External Port (for PEER requests) is important because
>    this is what enables a client to identify to which request a given
>    error response pertains.

I moved it into its own paragraph (rather than being in a paragraph
that appears to pertain only to errors), and it now reads:

        <t>Copying request fields are important because this is what
        enables a client to identify to which request a given
        error response pertains.  For MAP requests, this includes
        the Protocol, Internal Port, Requested External, and (if
        present) the THIRD_PARTY Option.  For PEER requests, this
        includes the Protocol, Internal Port, Remote Peer IP Address,
        and Remote Peer Port.</t>

> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: BTW please note it is useless to copy the External Address in all
> cases.

It's useful if the PCP client was trying to do both a NAT request 
and a firewall request -- e.g., it is an IPv6-only device listening 
on a single IPv6 address and port and wants to get both NAT64 
mapped and IPv6 firewall pinhole.  The server still needs to copy it,
even if it's useless in other cases to the PCP client.

-d

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


From rpenno@juniper.net  Thu Oct 13 16:46:59 2011
Return-Path: <rpenno@juniper.net>
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 8FC8121F85EF for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 16:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vNgWF-K6rTlz for <pcp@ietfa.amsl.com>; Thu, 13 Oct 2011 16:46:59 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id D3B8A21F85BB for <pcp@ietf.org>; Thu, 13 Oct 2011 16:46:58 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP;  Thu, 13 Oct 2011 16:46:58 PDT
Received: from P-EMHUB11-HQ.jnpr.net (172.24.192.58) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.83.0; Thu, 13 Oct 2011 16:41:31 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB11-HQ.jnpr.net (172.24.192.58) with Microsoft SMTP Server (TLS) id 8.3.83.0; Thu, 13 Oct 2011 16:41:31 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 13 Oct 2011 19:41:30 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Dan Wing <dwing@cisco.com>, 'Francis Dupont' <Francis.Dupont@fdupont.fr>,  "pcp@ietf.org" <pcp@ietf.org>
Date: Thu, 13 Oct 2011 19:41:28 -0400
Thread-Topic: [pcp] renewal time
Thread-Index: AcyJ77vt/Gj6bpRWQfyDS5TwCuAlagAB9jAwAAAkyfAAACTG4AACOWg+
Message-ID: <CABCC538.54FD2%rpenno@juniper.net>
In-Reply-To: <028e01cc89f8$fd2a14f0$f77e3ed0$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] renewal time
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, 13 Oct 2011 23:46:59 -0000

24 hrs is better.


On 10/13/11 3:39 PM, "Dan Wing" <dwing@cisco.com> wrote:

>> -----Original Message-----
>> From: Reinaldo Penno [mailto:rpenno@juniper.net]
>> Sent: Thursday, October 13, 2011 3:34 PM
>> To: Dan Wing; 'Francis Dupont'; pcp@ietf.org
>> Subject: Re: [pcp] renewal time
>>=20
>> This is confusing. Does it mean that lifetimes > 2 hours are no-op?
>=20
> We clearly need some sort of min() function on the returned Lifetime --
> a lifetime of 5 years is a good example of an absurd value that
> can legally be returned by the PCP server.
>=20
> Do you want a higher value, such as 24 hours?
>=20
> -d
>=20
>=20
>=20
>> On 10/13/11 3:31 PM, "Dan Wing" <dwing@cisco.com> wrote:
>>=20
>>>> will be wellcome.
>>>=20
>>> New text:
>>>=20
>>>         Regardless of the Assigned Lifetime of a mapping, the PCP
>>>         client SHOULD impose an upper limit on this returned value,
>>>         and 2 hours is RECOMMENDED.  This means if the PCP server
>>>         returns an absurdly long Assigned Lifetime (e.g., 5 years),
>>>         the PCP client will behave as if it received a more sane
>> value
>>>         (e.g., 2 hours).
>>>=20
>>> -d
>=20


From Francis.Dupont@fdupont.fr  Fri Oct 14 01:12:10 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 5002521F8AC3 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:12:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.424
X-Spam-Level: 
X-Spam-Status: No, score=-2.424 tagged_above=-999 required=5 tests=[AWL=0.175,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vewofb4E0MXR for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:12:02 -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 D223821F8A7A for <pcp@ietf.org>; Fri, 14 Oct 2011 01:12:01 -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 p9E8Acjq030837; Fri, 14 Oct 2011 10:10:38 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110140810.p9E8Acjq030837@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Reinaldo Penno <rpenno@juniper.net>
In-reply-to: Your message of Thu, 13 Oct 2011 17:25:22 EDT. <CABCA552.54F74%rpenno@juniper.net> 
Date: Fri, 14 Oct 2011 10:10:38 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] PEER vs. explicit mappings
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, 14 Oct 2011 08:12:10 -0000

 In your previous mail you wrote:

   I propose to drop 'implicit' vs. 'explicit' and just call 'PEER mappings'.
   
   Whether a session was created by the PEER message or taken over by a PEER
   message, the end result is the same. You have a peer map with the same
   characteristic irrespective of how it got to be a peer map.
   
=> but we want something which is not static or explicit dynamic too,
according to the terminology it should be implicit dynamic, and if
we define a forth kind of mappings how to explain they should behave
as implicit dynamic? It is not like NATs are not able to create
implicit dynamic mappings...

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 14 01:16:51 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 9C5E521F8AFB for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.431
X-Spam-Level: 
X-Spam-Status: No, score=-2.431 tagged_above=-999 required=5 tests=[AWL=0.168,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cfc-ghhH9900 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:16:51 -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 D0CF121F8AD3 for <pcp@ietf.org>; Fri, 14 Oct 2011 01:16:50 -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 p9E8GkHr031221; Fri, 14 Oct 2011 10:16:46 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110140816.p9E8GkHr031221@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 13 Oct 2011 14:36:05 PDT. <023201cc89f0$1cf7a5d0$56e6f170$@com> 
Date: Fri, 14 Oct 2011 10:16:46 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 14 Oct 2011 08:16:51 -0000

 In your previous mail you wrote:

   Without a lifetime for that address, it is irresponsible to
   tell the client the external IP address -- even if there is only
   one external IP address.
   
=> so it is irresponsible to implement an IWF because both
NAT-PMP and UPnP IGD (v1 or v2) provide a primitive which
returns the external IP address without a lifetime.
BTW is it the official position of the WG?

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 14 01:36: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 B4E2C21F8634 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[AWL=0.161,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nH59kljZ5ybi for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:36:19 -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 E4A3221F862F for <pcp@ietf.org>; Fri, 14 Oct 2011 01:36:18 -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 p9E8aGPe032413; Fri, 14 Oct 2011 10:36:16 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110140836.p9E8aGPe032413@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 13 Oct 2011 15:26:07 PDT. <027501cc89f7$1a182860$4e487920$@com> 
Date: Fri, 14 Oct 2011 10:36:16 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] existing mapping and PREFER_FAILURE
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, 14 Oct 2011 08:36:19 -0000

 In your previous mail you wrote:

   Ok, new text:
   
           <t>If a mapping already exists for the requested Internal
           Address and Port and the PREFER_FAILURE Option is not present,
           the PCP server MUST refresh the lifetime of that
           already-existing mapping, and return the already-existing
           External Address and Port in its response, regardless of the
           Suggested External Address and Port in the request.  If a
           mapping already exists for the requested Internal Address and Port
           the request contains the PREFER_FAILURE Option, but the
           Suggested External Address and Port do not match the actual
           External Address and Port of the already existing mapping, the
           error CANNOT_PROVIDE_EXTERNAL_PORT is returned.  If an implicit
           mapping already exists for the requested Internal Address
           and Port, the mapping SHOULD be upgraded to an explicit mapping.</t>
   
   I'm tempted to make it 'MUST upgrade', in fact, for reason I describe
   below.
   
=> I am for 'MUST upgrade or return an error'

   > or
   >   raise an error if it can't
   
   If it can't, it's broken.  We don't want to encourage such implementations,

=> I understand your reasons but here it is the PCP WG so we have to
live with any NAT implementations.

   because they push the problem back to the PCP client to resolve -- and 
   sometimes the PCP client _cannot_ resolve it (try getting FTP or ssh
   to listen on a non-default port makes it hard for all of the local 
   devices connecting to deal with the non-default port).
   
=> if there is an already existing implicit dynamic mapping it is
because a packet from the internal address and port was sent a short time
before. So these NATs push the problem back to which has caused it,
and BTW which has not followed the requirement to enforce the port
to not be used by another application.
   
Now we can perhaps reach an agreement if we define the word upgrade,
in my message I used the term "promote" because it suggests most of the
characterictics are kept, for instance the external address and port.
If we change it by "promote to or replace by" we cover all cases as
the explicit dynamic mapping has only to use the same internal address
and port (and to be the unique mapping to use them).

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 14 01:41:33 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 14FED21F8770 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.445
X-Spam-Level: 
X-Spam-Status: No, score=-2.445 tagged_above=-999 required=5 tests=[AWL=0.154,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JswxTIsS-Z-c for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:41:32 -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 5D19F21F86AA for <pcp@ietf.org>; Fri, 14 Oct 2011 01:41:32 -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 p9E8fTYH032728; Fri, 14 Oct 2011 10:41:29 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110140841.p9E8fTYH032728@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 13 Oct 2011 15:31:43 PDT. <027701cc89f7$e2c0b7f0$a84227d0$@com> 
Date: Fri, 14 Oct 2011 10:41:29 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] renewal time
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, 14 Oct 2011 08:41:33 -0000

 In your previous mail you wrote:

   New text:
   
           Regardless of the Assigned Lifetime of a mapping, the PCP
           client SHOULD impose an upper limit on this returned value,
           and 2 hours is RECOMMENDED.  This means if the PCP server
           returns an absurdly long Assigned Lifetime (e.g., 5 years),
           the PCP client will behave as if it received a more sane value
           (e.g., 2 hours).
   
=> fine if you add "but not 4294967295 (0xFFFFFFFF)" and something
explaining than anyway to renew a static mapping doesn't make sense.

Regards

Francis.Dupont@fdupont.fr

   

From Francis.Dupont@fdupont.fr  Fri Oct 14 01:46:17 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 BCA8821F8696 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.451
X-Spam-Level: 
X-Spam-Status: No, score=-2.451 tagged_above=-999 required=5 tests=[AWL=0.148,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lOp9ThSBUI-n for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:46:17 -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 1309421F8678 for <pcp@ietf.org>; Fri, 14 Oct 2011 01:46:16 -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 p9E8kE7b033042; Fri, 14 Oct 2011 10:46:14 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110140846.p9E8kE7b033042@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Reinaldo Penno <rpenno@juniper.net>
In-reply-to: Your message of Thu, 13 Oct 2011 18:33:40 EDT. <CABCB554.54FA7%rpenno@juniper.net> 
Date: Fri, 14 Oct 2011 10:46:14 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] renewal time
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, 14 Oct 2011 08:46:17 -0000

 In your previous mail you wrote:

   This is confusing. Does it mean that lifetimes > 2 hours are no-op?
   
=> with the context I believe the renewal timer should be set
to not more than 2 hours, i.e., if you get a 5 day lifetime
you schedule the renewal for now + 2 hours, not for between now + 2.5
and now + 3.125 days.
   
   On 10/13/11 3:31 PM, "Dan Wing" <dwing@cisco.com> wrote:
   
   > New text:
   >
   >         Regardless of the Assigned Lifetime of a mapping, the PCP
   >         client SHOULD impose an upper limit on this returned value,
   >         and 2 hours is RECOMMENDED.  This means if the PCP server
   >         returns an absurdly long Assigned Lifetime (e.g., 5 years),
   >         the PCP client will behave as if it received a more sane value
   >         (e.g., 2 hours).

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 14 01:49:36 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 93EE421F8C04 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.456
X-Spam-Level: 
X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jMV4vV2c+hZ5 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:49:36 -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 DCD5D21F8B5D for <pcp@ietf.org>; Fri, 14 Oct 2011 01:49:35 -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 p9E8nWh3033230; Fri, 14 Oct 2011 10:49:32 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110140849.p9E8nWh3033230@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 13 Oct 2011 15:39:37 PDT. <028e01cc89f8$fd2a14f0$f77e3ed0$@com> 
Date: Fri, 14 Oct 2011 10:49:32 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] renewal time
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, 14 Oct 2011 08:49:36 -0000

 In your previous mail you wrote:

   > -----Original Message-----
   > From: Reinaldo Penno [mailto:rpenno@juniper.net]
   > Sent: Thursday, October 13, 2011 3:34 PM
   > To: Dan Wing; 'Francis Dupont'; pcp@ietf.org
   > Subject: Re: [pcp] renewal time
   > 
   > This is confusing. Does it mean that lifetimes > 2 hours are no-op?
   
   We clearly need some sort of min() function on the returned Lifetime --
   a lifetime of 5 years is a good example of an absurd value that
   can legally be returned by the PCP server.
   
   Do you want a higher value, such as 24 hours?
   
=> IMHO it is not a good idea as it is fine to assure the PCP server
is still alive. BTW we had the same kind of discussion about the
TCP "keepalive" which finished by an agreement for 2 hours too!

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 14 01:54:29 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 C1CFC21F8BF4 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.461
X-Spam-Level: 
X-Spam-Status: No, score=-2.461 tagged_above=-999 required=5 tests=[AWL=0.138,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lE1cHxPZHbdN for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 01:54:29 -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 1532021F8B5D for <pcp@ietf.org>; Fri, 14 Oct 2011 01:54:28 -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 p9E8sQ7c033534; Fri, 14 Oct 2011 10:54:26 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110140854.p9E8sQ7c033534@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 13 Oct 2011 15:47:12 PDT. <029001cc89fa$0c184c10$2448e430$@com> 
Date: Fri, 14 Oct 2011 10:54:26 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] minor incoherence in base 14 9.3
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, 14 Oct 2011 08:54:29 -0000

 In your previous mail you wrote:

   > -----Original Message-----
   > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
   > Francis Dupont
   > Sent: Thursday, October 13, 2011 2:56 PM
   > To: pcp@ietf.org
   > Subject: [pcp] minor incoherence in base 14 9.3
   > 
   > In base 14 section 9.3:
   > 
   >    o  The PREFER_FAILURE option is included in the request and the
   >       Suggested External Address is not assignable to the PCP client.
   > 
   > => even I believe this should stand it is not (yet) compatible
   > with the current definition of PREFER_FAILURE and BTW there is
   > no (yet) a corresponding error...
   
   How is it incompatible with the current definition of PREFER_FAILURE?
   
=> there is no CANNOT_PROVIDE_EXTERNAL_ADDRESS...
BTW if you add it (and I strongly support this) it should take
precedence over CANNOT_PROVIDE_EXTERNAL_PORT as usually
it is useless to get the port without the address.

Regards

Francis.Dupont@fdupont.fr

PS: precedence here is about the rule order.

From Francis.Dupont@fdupont.fr  Fri Oct 14 02:02:50 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 5DBFB21F8C04 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 02:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vlS6b2dhsGFi for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 02:02:50 -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 9764521F8BF4 for <pcp@ietf.org>; Fri, 14 Oct 2011 02:02:49 -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 p9E92lgv034127; Fri, 14 Oct 2011 11:02:47 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110140902.p9E92lgv034127@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 13 Oct 2011 16:28:01 PDT. <02bf01cc89ff$c051e4c0$40f5ae40$@com> 
Date: Fri, 14 Oct 2011 11:02:47 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] fields to copy
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, 14 Oct 2011 09:02:50 -0000

 In your previous mail you wrote:

   I moved it into its own paragraph (rather than being in a paragraph
   that appears to pertain only to errors),
   
=> IMHO it is important to not attached this to errors where
the External Port at least should be copied to.

   and it now reads:

           <t>Copying request fields are important because this is what
           enables a client to identify to which request a given
           error response pertains.  For MAP requests, this includes
           the Protocol, Internal Port, Requested External, and (if
           present) the THIRD_PARTY Option.  For PEER requests, this
           includes the Protocol, Internal Port, Remote Peer IP Address,
           and Remote Peer Port.</t>
   
=> better!

   > PS: BTW please note it is useless to copy the External Address in all
   > cases.
   
   It's useful if the PCP client was trying to do both a NAT request 
   and a firewall request -- e.g., it is an IPv6-only device listening 
   on a single IPv6 address and port and wants to get both NAT64 
   mapped and IPv6 firewall pinhole.  The server still needs to copy it,
   even if it's useless in other cases to the PCP client.
   
=> following this argument the External Address and Port should be
copied in error responses too. Should we add a text?

Regards

Francis.Dupont@fdupont.fr

From rpenno@juniper.net  Fri Oct 14 02:24:40 2011
Return-Path: <rpenno@juniper.net>
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 E524321F8B3F for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 02:24:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RZgZWqzfQh0Y for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 02:24:40 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 413EC21F8B2A for <pcp@ietf.org>; Fri, 14 Oct 2011 02:24:09 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP;  Fri, 14 Oct 2011 02:24:40 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.83.0; Fri, 14 Oct 2011 02:23:17 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 14 Oct 2011 05:23:16 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, Dan Wing <dwing@cisco.com>
Date: Fri, 14 Oct 2011 05:23:13 -0400
Thread-Topic: [pcp] renewal time 
Thread-Index: AcyKTjWeV+AcsUiRQE+2X01AWpa85wABK/ul
Message-ID: <CABD4D91.55092%rpenno@juniper.net>
In-Reply-To: <201110140849.p9E8nWh3033230@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] renewal time
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, 14 Oct 2011 09:24:41 -0000

If the lifetime returned by the PCP Server is going to be discarded, do
still need a lifetime field?  We can convey 'deletion' by a single bit in
the header if necessary.


On 10/14/11 1:49 AM, "Francis Dupont" <Francis.Dupont@fdupont.fr> wrote:

>  In your previous mail you wrote:
>=20
>> -----Original Message-----
>> From: Reinaldo Penno [mailto:rpenno@juniper.net]
>> Sent: Thursday, October 13, 2011 3:34 PM
>> To: Dan Wing; 'Francis Dupont'; pcp@ietf.org
>> Subject: Re: [pcp] renewal time
>>=20
>> This is confusing. Does it mean that lifetimes > 2 hours are no-op?
>   =20
>    We clearly need some sort of min() function on the returned Lifetime -=
-
>    a lifetime of 5 years is a good example of an absurd value that
>    can legally be returned by the PCP server.
>   =20
>    Do you want a higher value, such as 24 hours?
>   =20
> =3D> IMHO it is not a good idea as it is fine to assure the PCP server
> is still alive. BTW we had the same kind of discussion about the
> TCP "keepalive" which finished by an agreement for 2 hours too!
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr


From rpenno@juniper.net  Fri Oct 14 02:32:07 2011
Return-Path: <rpenno@juniper.net>
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 6963821F87D3 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 02:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tpXYqhPpm+-6 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 02:32:07 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id EA68821F87C9 for <pcp@ietf.org>; Fri, 14 Oct 2011 02:32:04 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP;  Fri, 14 Oct 2011 02:32:06 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.83.0; Fri, 14 Oct 2011 02:29:30 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 14 Oct 2011 05:29:29 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Date: Fri, 14 Oct 2011 05:29:26 -0400
Thread-Topic: [pcp] PEER vs. explicit mappings 
Thread-Index: AcyKSPaugLt+05R8TiK0VvlE9UmbCwACs0wl
Message-ID: <CABD4F06.55097%rpenno@juniper.net>
In-Reply-To: <201110140810.p9E8Acjq030837@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] PEER vs. explicit mappings
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, 14 Oct 2011 09:32:07 -0000

I could not follow what is the issue you are worried about. I propose these
mappings as far as PCP is concerned.

- MAP
- PEER

I think your 'implicit mappings' are called 'sessions' and are already
defined elsewhere.=20

Thanks,

Reinaldo =20


On 10/14/11 1:10 AM, "Francis Dupont" <Francis.Dupont@fdupont.fr> wrote:

>  In your previous mail you wrote:
>=20
>    I propose to drop 'implicit' vs. 'explicit' and just call 'PEER mappin=
gs'.
>   =20
>    Whether a session was created by the PEER message or taken over by a P=
EER
>    message, the end result is the same. You have a peer map with the same
>    characteristic irrespective of how it got to be a peer map.
>   =20
> =3D> but we want something which is not static or explicit dynamic too,
> according to the terminology it should be implicit dynamic, and if
> we define a forth kind of mappings how to explain they should behave
> as implicit dynamic? It is not like NATs are not able to create
> implicit dynamic mappings...
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr


From moore@network-heretics.com  Fri Oct 14 04:46:35 2011
Return-Path: <moore@network-heretics.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 4B1F121F8ABD for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 04:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.349
X-Spam-Level: 
X-Spam-Status: No, score=-4.349 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UhHbEeeAzJp8 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 04:46:34 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 833D421F8A7A for <pcp@ietf.org>; Fri, 14 Oct 2011 04:46:34 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 2383820A2D; Fri, 14 Oct 2011 07:46:32 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 14 Oct 2011 07:46:32 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=MEuIO7dZwqFiksGl+xSPQJ/cosg=; b=HB XS6io5vzKrfBEVzNG9sFF/4grkioOLBWomeiovDXi/S6SkRZiYWtH9O/m1/9QuOR cGyWqS6s30Gek1i/z4Sg4rV4l8o7doXEA3QuwHO7KXmRI/n7UxwO9fZbyqMST+En kjPUkVuJDgQH8feSkQA94IP/aOMAevTPXmtfl5zdI=
X-Sasl-enc: ULLbonGK1oJ6bLxoCCgfY3SPQjJfBJ8rkLAZ9mWKs14d 1318592791
Received: from [192.168.1.16] (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 516F34833FD; Fri, 14 Oct 2011 07:46:31 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <201110140816.p9E8GkHr031221@givry.fdupont.fr>
Date: Fri, 14 Oct 2011 07:46:08 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <D70B1B1F-7210-4FF0-9ACD-9F27612A4435@network-heretics.com>
References: <201110140816.p9E8GkHr031221@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1084)
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 14 Oct 2011 11:46:35 -0000

On Oct 14, 2011, at 4:16 AM, Francis Dupont wrote:

> In your previous mail you wrote:
> 
>   Without a lifetime for that address, it is irresponsible to
>   tell the client the external IP address -- even if there is only
>   one external IP address.
> 
> => so it is irresponsible to implement an IWF because both
> NAT-PMP and UPnP IGD (v1 or v2) provide a primitive which
> returns the external IP address without a lifetime.
> BTW is it the official position of the WG?

FWIW, I don't agree with that position.

Keith


From simon.perreault@viagenie.ca  Fri Oct 14 06:00:24 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 5E92321F8BD3 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 06:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.489
X-Spam-Level: 
X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id de6xkHFRPZkq for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 06:00:23 -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 CB6BE21F8BC5 for <pcp@ietf.org>; Fri, 14 Oct 2011 06:00:23 -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 1F7C120CF1 for <pcp@ietf.org>; Fri, 14 Oct 2011 09:00:23 -0400 (EDT)
Message-ID: <4E983266.1090802@viagenie.ca>
Date: Fri, 14 Oct 2011 09:00:22 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110720 Thunderbird/5.0
MIME-Version: 1.0
To: pcp@ietf.org
References: <201110140816.p9E8GkHr031221@givry.fdupont.fr>
In-Reply-To: <201110140816.p9E8GkHr031221@givry.fdupont.fr>
X-Enigmail-Version: 1.2.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [pcp] learning the external address
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, 14 Oct 2011 13:00:24 -0000

On 2011-10-14 04:16, Francis Dupont wrote:
>  In your previous mail you wrote:
> 
>    Without a lifetime for that address, it is irresponsible to
>    tell the client the external IP address -- even if there is only
>    one external IP address.
>    
> => so it is irresponsible to implement an IWF because both
> NAT-PMP and UPnP IGD (v1 or v2) provide a primitive which
> returns the external IP address without a lifetime.
> BTW is it the official position of the WG?

I disagree. PCP should do things the right way (i.e. with a lifetime).
The IWF is allowed to be hackish to accommodate broken protocols (i.e.
strip off the lifetime).

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  Fri Oct 14 07:47:59 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 2115121F8CD0 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 07:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.75
X-Spam-Level: 
X-Spam-Status: No, score=-104.75 tagged_above=-999 required=5 tests=[AWL=1.849, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DMcFRoELv0Dw for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 07:47:58 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9AA21F8CCF for <pcp@ietf.org>; Fri, 14 Oct 2011 07:47:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1256; q=dns/txt; s=iport; t=1318603678; x=1319813278; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=suTWak/kkl9LxTTF/4j3D+SFFJ7o/ng8Ky/VCoRB9Kw=; b=dtdix0Vrjt2fx0tfUGoYtg9sF4HEGklmdYERIf30meYr9ti9QPdUmuDy /T/OI0nRQDl7/CkPeIifSG9r8/kaALBySxrxUIDBytMZnYyFqc5YXiT+T BRS9rJt0c5krbUgeqSCPf61ZZoIRwtmNtGl4cz0ctti1hR04gRnHf5/a5 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoMAACNLmE6rRDoJ/2dsb2JhbABDmTuBbI08gQWBbgEBAQMBCAoBFxAzDAUHAQMCCQ8BAQQBAQEnBxkjCgkIAQEEARILF4ddmH8BnkaHeQSIAZ1r
X-IronPort-AV: E=Sophos;i="4.69,346,1315180800";  d="scan'208";a="7918177"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 14 Oct 2011 14:47:58 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9EElw2R012985; Fri, 14 Oct 2011 14:47:58 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Keith Moore'" <moore@network-heretics.com>, "'Francis Dupont'" <Francis.Dupont@fdupont.fr>
References: <201110140816.p9E8GkHr031221@givry.fdupont.fr> <D70B1B1F-7210-4FF0-9ACD-9F27612A4435@network-heretics.com>
In-Reply-To: <D70B1B1F-7210-4FF0-9ACD-9F27612A4435@network-heretics.com>
Date: Fri, 14 Oct 2011 07:47:58 -0700
Message-ID: <04cc01cc8a80$43e638b0$cbb2aa10$@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: AcyKZvGBWYEjjpFRQYGvk4Som7MBQAAGPMrg
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 14 Oct 2011 14:47:59 -0000

> -----Original Message-----
> From: Keith Moore [mailto:moore@network-heretics.com]
> Sent: Friday, October 14, 2011 4:46 AM
> To: Francis Dupont
> Cc: Dan Wing; pcp@ietf.org
> Subject: Re: [pcp] learning the external address
> 
> 
> On Oct 14, 2011, at 4:16 AM, Francis Dupont wrote:
> 
> > In your previous mail you wrote:
> >
> >   Without a lifetime for that address, it is irresponsible to
> >   tell the client the external IP address -- even if there is only
> >   one external IP address.
> >
> > => so it is irresponsible to implement an IWF because both
> > NAT-PMP and UPnP IGD (v1 or v2) provide a primitive which
> > returns the external IP address without a lifetime.
> > BTW is it the official position of the WG?

Get a mapping, and maintain that mapping.  It is not PCP's
responsibility to perpetuate a mistake in UPnP IGD and in
NAT-PMP.

> FWIW, I don't agree with that position.

I don't see how to reconcile that 

  1.  networks change, and nothing lasts forever.  Hence,
      DNS has TTLs, lack of route advertisements means the
      route is no longer valid, DHCP has leases, and so on.
  2.  UPnP IGD and NAT-PMP both assume the IP address lasts
      forever.  It does not last forever.

-d



From Francis.Dupont@fdupont.fr  Fri Oct 14 08:46:02 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 6A65A21F8922 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 08:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.129,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DhfXBU5lBRa3 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 08:46:02 -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 8435921F8AD8 for <pcp@ietf.org>; Fri, 14 Oct 2011 08:46:01 -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 p9EFicH2058604; Fri, 14 Oct 2011 17:44:38 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110141544.p9EFicH2058604@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Reinaldo Penno <rpenno@juniper.net>
In-reply-to: Your message of Fri, 14 Oct 2011 05:23:13 EDT. <CABD4D91.55092%rpenno@juniper.net> 
Date: Fri, 14 Oct 2011 17:44:38 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] renewal time
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, 14 Oct 2011 15:46:02 -0000

 In your previous mail you wrote:

   If the lifetime returned by the PCP Server is going to be discarded

=> it is not discarded, it is round down to the 2 hour value for
the renewal, if the client wants to renew...

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 14 08:49:45 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 99D5921F8C9F for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 08:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level: 
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IVoKLOyco54h for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 08:49:45 -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 DE5C521F89B8 for <pcp@ietf.org>; Fri, 14 Oct 2011 08:49:44 -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 p9EFngOZ058913; Fri, 14 Oct 2011 17:49:42 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110141549.p9EFngOZ058913@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Reinaldo Penno <rpenno@juniper.net>
In-reply-to: Your message of Fri, 14 Oct 2011 05:29:26 EDT. <CABD4F06.55097%rpenno@juniper.net> 
Date: Fri, 14 Oct 2011 17:49:42 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] PEER vs. explicit mappings
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, 14 Oct 2011 15:49:45 -0000

 In your previous mail you wrote:

   I could not follow what is the issue you are worried about. I propose these
   mappings as far as PCP is concerned.
   
   - MAP
   - PEER
   
=> I want to use the PCP terminology, section 3 of base 14, which classifies
mappings into 3 types: static, explicit dynamic and implicit dynamic.

   I think your 'implicit mappings' are called 'sessions' and are already
   defined elsewhere.
   
=> I don't want to use another terminology without agreed definitions.
According to the terminology and base drafts until the version 14,
MAP clearly acts on explicit dynamic mappings and PEER on implicit
dynamic mappings.
So why to change this?

Regards

Francis.Dupont@fdupont.fr

From dwing@cisco.com  Fri Oct 14 08:59:10 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 AAE8A21F8C57 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 08:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.814
X-Spam-Level: 
X-Spam-Status: No, score=-104.814 tagged_above=-999 required=5 tests=[AWL=1.785, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5yUVFVgYwJ4 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 08:59:10 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id F107321F8B3C for <pcp@ietf.org>; Fri, 14 Oct 2011 08:59:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=4338; q=dns/txt; s=iport; t=1318607950; x=1319817550; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=uy3xZx30mB3GoYvpELtt2NSXjpBO5aI1rTcM0vbMwZM=; b=PtBE+cqrVu/Sj0taU8pKJkqZvTrnde4xcAYkqZx/Jeevp4cLLYIkXMp1 dku3AcGE54qsmvh3G1+9H8EUCnwlDvjHEyWv3ZGkHjCfX1pIgseYF2tE0 2iFAGiO0bHljgK84S9ETfBf7kx6bfkpAZRu6GvdRXOojntIbXDAOkCQys 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoMAAMJbmE6rRDoH/2dsb2JhbABDmTuBbI08gQWBbgEBAQMBCAoBFxA0CwUHAQMCCQ8BAQQBAQEnBxkjCgkIAQEEEwsXh12YeQGeWod5BIgBlFmJEg
X-IronPort-AV: E=Sophos;i="4.69,347,1315180800";  d="scan'208";a="7932369"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 14 Oct 2011 15:59:09 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9EFx9RB027403; Fri, 14 Oct 2011 15:59:09 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Thu, 13 Oct 2011 15:26:07 PDT. <027501cc89f7$1a182860$4e487920$@com> <201110140836.p9E8aGPe032413@givry.fdupont.fr>
In-Reply-To: <201110140836.p9E8aGPe032413@givry.fdupont.fr>
Date: Fri, 14 Oct 2011 08:59:09 -0700
Message-ID: <051b01cc8a8a$35a75360$a0f5fa20$@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: AcyKTFesxQKgop6rSrmdRy7TMOOY0AAPG0Mw
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] existing mapping and PREFER_FAILURE
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, 14 Oct 2011 15:59:10 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Friday, October 14, 2011 1:36 AM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] existing mapping and PREFER_FAILURE
> 
> 
>  In your previous mail you wrote:
> 
>    Ok, new text:
> 
>            <t>If a mapping already exists for the requested Internal
>            Address and Port and the PREFER_FAILURE Option is not
> present,
>            the PCP server MUST refresh the lifetime of that
>            already-existing mapping, and return the already-existing
>            External Address and Port in its response, regardless of the
>            Suggested External Address and Port in the request.  If a
>            mapping already exists for the requested Internal Address
> and Port
>            the request contains the PREFER_FAILURE Option, but the
>            Suggested External Address and Port do not match the actual
>            External Address and Port of the already existing mapping,
> the
>            error CANNOT_PROVIDE_EXTERNAL_PORT is returned.  If an
> implicit
>            mapping already exists for the requested Internal Address
>            and Port, the mapping SHOULD be upgraded to an explicit
> mapping.</t>
> 
>    I'm tempted to make it 'MUST upgrade', in fact, for reason I
> describe
>    below.
> 
> => I am for 'MUST upgrade or return an error'

But that is exactly what causes a problem.


>    > or
>    >   raise an error if it can't
> 
>    If it can't, it's broken.  We don't want to encourage such
> implementations,
> 
> => I understand your reasons but here it is the PCP WG so we have to
> live with any NAT implementations.

The NAT has to handle MAP in a way that works well.  

Here is the example problem, which has been discussed on the
mailing list before, and discussed in f2f meetings before -- but
for everyone's benefit:

Let's say an application starts listening on port N (e.g.,
TCP/22, TCP/80, TCP/8080, UDP/5061, etc.).  Then, through
no fault of that application, the OS's stack decides to use
that same port for an outgoing connection to the Internet
(from a completely unrelated application).  The application
listening on port N also has some incoming connections to
that port N, from hosts within the home network (e.g., the
music streaming devices).  Now, I click the "allow 
connections from the Internet" button on my application,
which causes it to make a PCP MAP request.  If that gets
denied, that means my application needs to start listening
on another port ("M"), try again, repeat.  That's a significant
burden for the application, and now it is listening on two
ports (N, where it has already accepted connections from
hosts on the same network, and the eventual M port which
is for connections from the Internet).


>    because they push the problem back to the PCP client to resolve --
> and
>    sometimes the PCP client _cannot_ resolve it (try getting FTP or ssh
>    to listen on a non-default port makes it hard for all of the local
>    devices connecting to deal with the non-default port).
> 
> => if there is an already existing implicit dynamic mapping it is
> because a packet from the internal address and port was sent a short
> time
> before. So these NATs push the problem back to which has caused it,
> and BTW which has not followed the requirement to enforce the port
> to not be used by another application.

Can this problem be entirely avoided by the application listening
on the port using INADDR_ANY or SO_EXCLUSIVEADDRUSE or something else?  
It has been my understanding that it's impossible for an application 
to prevent the OS from using its listening socket for the OS's outgoing
connections, from an explanation over a year ago from Simon.  

> Now we can perhaps reach an agreement if we define the word upgrade,
> in my message I used the term "promote" because it suggests most of the
> characterictics are kept, for instance the external address and port.
> If we change it by "promote to or replace by" we cover all cases as
> the explicit dynamic mapping has only to use the same internal address
> and port (and to be the unique mapping to use them).

-d

> Regards
> 
> Francis.Dupont@fdupont.fr


From moore@network-heretics.com  Fri Oct 14 09:05:30 2011
Return-Path: <moore@network-heretics.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 3194521F8BEC for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSxulbys-heR for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:05:29 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 78A7121F8C6B for <pcp@ietf.org>; Fri, 14 Oct 2011 09:05:24 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E6F8D210E8; Fri, 14 Oct 2011 12:05:23 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 14 Oct 2011 12:05:23 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=g7nX7t/jn1/5Bf5FFaWzNNV9b2I=; b=nK 0fFeSDV8Y8A1W26AzmXisxCjHzVFznWo/mH6Wgi0EKdlSb0+/jO68maUu5e116BC msCTtvp15xsd8lqa38CfWIxurIfsSLdQRFIRQDNGhLfirs09wg0UlNw65dhePFpV 9CFNPdsgf4ZpZ8qtCuOV0BHCYDo6vsO79aQePspqw=
X-Sasl-enc: BeDBbQK0wOYw2HPvObjhfynehDwMugPkcBxbh8qp37SY 1318608323
Received: from [192.168.1.16] (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id B3FB04833FE; Fri, 14 Oct 2011 12:05:22 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <04cc01cc8a80$43e638b0$cbb2aa10$@com>
Date: Fri, 14 Oct 2011 12:04:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C16E40EC-50A5-46DA-8342-738AFC172B68@network-heretics.com>
References: <201110140816.p9E8GkHr031221@givry.fdupont.fr> <D70B1B1F-7210-4FF0-9ACD-9F27612A4435@network-heretics.com> <04cc01cc8a80$43e638b0$cbb2aa10$@com>
To: "Dan Wing" <dwing@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 14 Oct 2011 16:05:30 -0000

On Oct 14, 2011, at 10:47 AM, Dan Wing wrote:

>> -----Original Message-----
>> From: Keith Moore [mailto:moore@network-heretics.com]
>> Sent: Friday, October 14, 2011 4:46 AM
>> To: Francis Dupont
>> Cc: Dan Wing; pcp@ietf.org
>> Subject: Re: [pcp] learning the external address
>>=20
>>=20
>> On Oct 14, 2011, at 4:16 AM, Francis Dupont wrote:
>>=20
>>> In your previous mail you wrote:
>>>=20
>>>  Without a lifetime for that address, it is irresponsible to
>>>  tell the client the external IP address -- even if there is only
>>>  one external IP address.
>>>=20
>>> =3D> so it is irresponsible to implement an IWF because both
>>> NAT-PMP and UPnP IGD (v1 or v2) provide a primitive which
>>> returns the external IP address without a lifetime.
>>> BTW is it the official position of the WG?
>=20
> Get a mapping, and maintain that mapping.  It is not PCP's
> responsibility to perpetuate a mistake in UPnP IGD and in
> NAT-PMP.
>=20
>> FWIW, I don't agree with that position.
>=20
> I don't see how to reconcile that=20
>=20
>  1.  networks change, and nothing lasts forever.  Hence,
>      DNS has TTLs, lack of route advertisements means the
>      route is no longer valid, DHCP has leases, and so on.
>  2.  UPnP IGD and NAT-PMP both assume the IP address lasts
>      forever.  It does not last forever.

An IP address binding does not last forever, because nothing lasts =
forever.   But it might last indefinitely.  NATs can be stateless, =
firewalls can have static rules.  =20

My understanding is that DHCP leasing was designed based on the =
assumption that PCs crash or get shut down without any warning.  If DHCP =
handed out addresses to PCs without some sort of expiration, eventually =
all of those addresses would be assigned to PCs that had crashed and =
lost their memory of previous address assignments.   Unfortunately, that =
design choice in DHCP led to a mentality that said that the network =
could change an address binding for frivolous reasons.  That was an =
unintended consequence, and not a desirable one.  The Internet =
architecture didn't then, and still doesn't, have a good, =
widely-applicable mechanism for allowing applications to tolerate =
addresses being changed out from under them.

DNS TTLs are similarly problematic, at least as a sole mechanism.  =
Obviously there's a need to expire stale RRs from caches.  But TTLs are =
at best a stopgap mechanism.  The problem is that you rarely know in =
advance when a RR needs to change, and even when you do, DNS doesn't =
give you a mechanism to gracefully manage that change.   Really you need =
additional mechanisms: the ability to instantly update or at least =
delete all replicas when an RR changes (dynamic update does address this =
problem to some degree); and for those cases where you do know in =
advance that an RR will change, you would like to have the ability to =
pre-propagate the new RR in advance of it being advertised, and set an =
absolute expiration date-time on the old RR (which would effectively =
cause the TTL on the old RR to decrease down to zero as that expiration =
date-time approached).

So I don't think either DNS or DHCP should be cited as good examples of =
how to manage cached bindings with finite lifetimes.

What I disagree with in the quoted statement above is that it's =
"irresponsible" to tell a client an external IP address without a =
lifetime.  What might be irresponsible is making up a lifetime where one =
did not exist.   If the binding is of indefinite duration, the protocol =
should allow the NAT or firewall to say so. =20

Realize also that even a DNS TTL or a DHCP lease time is no guarantee =
that the binding will be valid for that long.  RRs do get updated =
without advance notice; routers (especially consumer-grade routers) get =
wedged and have to be rebooted, causing all of their old leases to be =
forgotten.    For similar reasons, a stated lifetime in a PCP binding =
can't be expected to be a guarantee either.  But a TTL is a poor =
mechanism for dealing with that case.

Keith


From rpenno@juniper.net  Fri Oct 14 09:10:47 2011
Return-Path: <rpenno@juniper.net>
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 AD1C221F85B9 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:10:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0W81CdHbHXD for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:10:47 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 031FC21F84DD for <pcp@ietf.org>; Fri, 14 Oct 2011 09:10:44 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP;  Fri, 14 Oct 2011 09:10:46 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.83.0; Fri, 14 Oct 2011 09:09:59 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 14 Oct 2011 12:09:59 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Date: Fri, 14 Oct 2011 12:09:55 -0400
Thread-Topic: [pcp] PEER vs. explicit mappings 
Thread-Index: AcyKiOfmuWgrqgiPSY+O9hFCpQuflAAAs5cG
Message-ID: <CABDACE3.5513A%rpenno@juniper.net>
In-Reply-To: <201110141549.p9EFngOZ058913@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] PEER vs. explicit mappings
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, 14 Oct 2011 16:10:47 -0000

On 10/14/11 8:49 AM, "Francis Dupont" <Francis.Dupont@fdupont.fr> wrote:

>  In your previous mail you wrote:
>=20
>    I could not follow what is the issue you are worried about. I propose =
these
>    mappings as far as PCP is concerned.
>   =20
>    - MAP
>    - PEER
>   =20
> =3D> I want to use the PCP terminology, section 3 of base 14, which class=
ifies
> mappings into 3 types: static, explicit dynamic and implicit dynamic.
>=20
>    I think your 'implicit mappings' are called 'sessions' and are already
>    defined elsewhere.
>   =20
> =3D> I don't want to use another terminology without agreed definitions.
> According to the terminology and base drafts until the version 14,
> MAP clearly acts on explicit dynamic mappings and PEER on implicit
> dynamic mappings.
> So why to change this?

This a construct we defined. I see no problem in collapsing and simplifying
the concepts. 'Sessions' are defined and used in NAT64 and other RFCs.

>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr


From dwing@cisco.com  Fri Oct 14 09:12:27 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 1D2B121F8C60 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:12:27 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FAOGGGF+Lir8 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:12:26 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 6438D21F8C5F for <pcp@ietf.org>; Fri, 14 Oct 2011 09:12:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1791; q=dns/txt; s=iport; t=1318608746; x=1319818346; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=fDaRFwYFO/jGPMkInkrlikLwA+0N0oJ2f2JLPJHsAhM=; b=dgMss75sKsD9PqsLiQX4AogFpfGJcShc9c7pHFzWyztMW6nRrwyNMv5x E0qNmX21N6QPWbGmuTTD6LaA7KPAk+phuLBvp8X+BK4FnkX7yBaywjCnf mjBJPaaHZrmB3UyqCJ2tZ7kYiekeUBhQifPgTBXJWGwVjmfm0IprCCbcP Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsMAAPlemE6tJXHA/2dsb2JhbABDmTxDgSmNPIEFgW4BAQEDAQgKARcQPwUHAQMCGAEBBAEBAScHGSMKCQgBAQQTCxeHXZh/AZ5Xh3kEiAGUWYkS
X-IronPort-AV: E=Sophos;i="4.69,347,1315180800"; d="scan'208";a="28509993"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-9.cisco.com with ESMTP; 14 Oct 2011 16:12:25 +0000
Received: from dwingWS ([10.32.240.197]) by rcdn-core2-5.cisco.com (8.14.3/8.14.3) with ESMTP id p9EGCPbC018988;  Fri, 14 Oct 2011 16:12:25 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Thu, 13 Oct 2011 15:47:12 PDT. <029001cc89fa$0c184c10$2448e430$@com> <201110140854.p9E8sQ7c033534@givry.fdupont.fr>
In-Reply-To: <201110140854.p9E8sQ7c033534@givry.fdupont.fr>
Date: Fri, 14 Oct 2011 09:12:25 -0700
Message-ID: <053201cc8a8c$101e7db0$305b7910$@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: AcyKTuH2sgh5HqE8SJWYQpLYIRB4EwAPK0Lw
Content-Language: en-us
Cc: pcp@ietf.org
Subject: [pcp] CANNOT_PROVIDE_EXTERNAL_* error [was RE: minor incoherence in base 14 9.3]
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, 14 Oct 2011 16:12:27 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Friday, October 14, 2011 1:54 AM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] minor incoherence in base 14 9.3
> 
> 
>  In your previous mail you wrote:
> 
>    > -----Original Message-----
>    > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf
> Of
>    > Francis Dupont
>    > Sent: Thursday, October 13, 2011 2:56 PM
>    > To: pcp@ietf.org
>    > Subject: [pcp] minor incoherence in base 14 9.3
>    >
>    > In base 14 section 9.3:
>    >
>    >    o  The PREFER_FAILURE option is included in the request and the
>    >       Suggested External Address is not assignable to the PCP
> client.
>    >
>    > => even I believe this should stand it is not (yet) compatible
>    > with the current definition of PREFER_FAILURE and BTW there is
>    > no (yet) a corresponding error...
> 
>    How is it incompatible with the current definition of
> PREFER_FAILURE?
> 
> => there is no CANNOT_PROVIDE_EXTERNAL_ADDRESS...
> BTW if you add it (and I strongly support this) it should take
> precedence over CANNOT_PROVIDE_EXTERNAL_PORT as usually
> it is useless to get the port without the address.

Is there value in two different errors for cannot-provide-external-address
and cannot-provide-external-port, rather than a single error
CANNOT_PROVIDE_EXTERNAL (which could cover both inability to get the
requested external address and inability to get external port)?  Having one
error also eliminates the problem of which error takes precedence when both
the port and the external address cannot be assigned.

-d


> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: precedence here is about the rule order.


From Francis.Dupont@fdupont.fr  Fri Oct 14 09:14:02 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 14BD021F8C5F for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.478
X-Spam-Level: 
X-Spam-Status: No, score=-2.478 tagged_above=-999 required=5 tests=[AWL=0.121,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3DPWUMtLLTiW for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:14:01 -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 29AD521F8C14 for <pcp@ietf.org>; Fri, 14 Oct 2011 09:14:00 -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 p9EGDwdA060721; Fri, 14 Oct 2011 18:13:58 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110141613.p9EGDwdA060721@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Fri, 14 Oct 2011 08:59:09 PDT. <051b01cc8a8a$35a75360$a0f5fa20$@com> 
Date: Fri, 14 Oct 2011 18:13:58 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] existing mapping and PREFER_FAILURE
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, 14 Oct 2011 16:14:02 -0000

 In your previous mail you wrote:

   > => I am for 'MUST upgrade or return an error'
   
   But that is exactly what causes a problem.
   
=> this is why I propose "promote to or replace by" which
puts the eventual damage on the already existing implicit
dynamic mapping which should have never existed.
   
   > => I understand your reasons but here it is the PCP WG so we have to
   > live with any NAT implementations.
   
   The NAT has to handle MAP in a way that works well.  
   
=> but PCP explicitely can't change NAT behavior.

   Here is the example problem, which has been discussed on the
   mailing list before, and discussed in f2f meetings before -- but
   for everyone's benefit:
   
   Let's say an application starts listening on port N (e.g.,
   TCP/22, TCP/80, TCP/8080, UDP/5061, etc.).  Then, through
   no fault of that application, the OS's stack decides to use
   that same port for an outgoing connection to the Internet
   (from a completely unrelated application).  The application
   listening on port N also has some incoming connections to
   that port N, from hosts within the home network (e.g., the
   music streaming devices).  Now, I click the "allow 
   connections from the Internet" button on my application,
   which causes it to make a PCP MAP request.  If that gets
   denied, that means my application needs to start listening
   on another port ("M"), try again, repeat.  That's a significant
   burden for the application, and now it is listening on two
   ports (N, where it has already accepted connections from
   hosts on the same network, and the eventual M port which
   is for connections from the Internet).
   
=> I know this but in fact it is not a good example: if the
application can't get the exclusive use of the port in the OS
it will be in trouble anyway.

   Can this problem be entirely avoided by the application listening
   on the port using INADDR_ANY or SO_EXCLUSIVEADDRUSE or something else?  
   It has been my understanding that it's impossible for an application 
   to prevent the OS from using its listening socket for the OS's outgoing
   connections, from an explanation over a year ago from Simon.  
   
=> it is OS dependent, I can answer (yes) for BSDs, I have never been convinced
by SO_REUSEADDR implementation on Linux, and SO_EXCLUSIVEADDRUSE is
supposed to be the (other) solution on recent versions of Windows...

   > Now we can perhaps reach an agreement if we define the word upgrade,
   > in my message I used the term "promote" because it suggests most of the
   > characterictics are kept, for instance the external address and port.
   > If we change it by "promote to or replace by" we cover all cases as
   > the explicit dynamic mapping has only to use the same internal address
   > and port (and to be the unique mapping to use them).
   
=> can you answer to this proposal?
   
Regards

Francis.Dupont@fdupont.fr

From rpenno@juniper.net  Fri Oct 14 09:14:42 2011
Return-Path: <rpenno@juniper.net>
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 ABF9A21F8C5F for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FggAfa39FCYZ for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:14:42 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 2E02221F8C14 for <pcp@ietf.org>; Fri, 14 Oct 2011 09:14:40 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP;  Fri, 14 Oct 2011 09:14:42 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.83.0; Fri, 14 Oct 2011 09:10:55 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 14 Oct 2011 12:10:54 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Date: Fri, 14 Oct 2011 12:10:52 -0400
Thread-Topic: [pcp] renewal time 
Thread-Index: AcyKiGJ/ju8+T6f5TlGI3mAsWieYqAAA3XBC
Message-ID: <CABDAD1C.5513D%rpenno@juniper.net>
In-Reply-To: <201110141544.p9EFicH2058604@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] renewal time
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, 14 Oct 2011 16:14:42 -0000

So, if it is 5 years, it is 'rounded' to 2 hours?


On 10/14/11 8:44 AM, "Francis Dupont" <Francis.Dupont@fdupont.fr> wrote:

>  In your previous mail you wrote:
>=20
>    If the lifetime returned by the PCP Server is going to be discarded
>=20
> =3D> it is not discarded, it is round down to the 2 hour value for
> the renewal, if the client wants to renew...
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr


From dwing@cisco.com  Fri Oct 14 09:20:00 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 4966D21F8C60 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.873
X-Spam-Level: 
X-Spam-Status: No, score=-104.873 tagged_above=-999 required=5 tests=[AWL=1.726, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XskZVgQGWTfF for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:19:59 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id DA91B21F8C5F for <pcp@ietf.org>; Fri, 14 Oct 2011 09:19:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1772; q=dns/txt; s=iport; t=1318609199; x=1319818799; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=FOya+3IhYNiJAwtCht/GFLCwSaWK5mfExSEJA+wDqt8=; b=RB4AFT+1gp96bwXwTg64mhklfV6sZx7TMbD3E4Lpl8M5SAOOYjJq7dti M0xx6S0T+NjgBd9EgJ3OsT7xuurjiymF3cgOSv6YLmqtv4WmbF1BtuzUn 64Nx80Q5xJfah5CQ3QQG0Jy040KYF/j/hiiOApz64MCZGP/f8E9vqahfr A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsMAALFgmE6rRDoH/2dsb2JhbAA5Cpk9Q4EpjTyBBYFuAQEBAwEICgEXED8FBwEDAgkPAQEEAQEBJwcZIwoJCAEBBBMLF4ddmHsBnleESoMvBIgBnWs
X-IronPort-AV: E=Sophos;i="4.69,347,1315180800";  d="scan'208";a="7913488"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 14 Oct 2011 16:19:59 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9EGJxCM005468; Fri, 14 Oct 2011 16:19:59 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Thu, 13 Oct 2011 16:28:01 PDT. <02bf01cc89ff$c051e4c0$40f5ae40$@com> <201110140902.p9E92lgv034127@givry.fdupont.fr>
In-Reply-To: <201110140902.p9E92lgv034127@givry.fdupont.fr>
Date: Fri, 14 Oct 2011 09:19:59 -0700
Message-ID: <053301cc8a8d$1eaabeb0$5c003c10$@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: AcyKUAyUEeeCNTfAT5+8izJ/ncnUUgAPBvLQ
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] fields to copy
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, 14 Oct 2011 16:20:00 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Friday, October 14, 2011 2:03 AM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] fields to copy
> 
> 
>  In your previous mail you wrote:
> 
>    I moved it into its own paragraph (rather than being in a paragraph
>    that appears to pertain only to errors),
> 
> => IMHO it is important to not attached this to errors where
> the External Port at least should be copied to.
> 
>    and it now reads:
> 
>            <t>Copying request fields are important because this is what
>            enables a client to identify to which request a given
>            error response pertains.  For MAP requests, this includes
>            the Protocol, Internal Port, Requested External, and (if
>            present) the THIRD_PARTY Option.  For PEER requests, this
>            includes the Protocol, Internal Port, Remote Peer IP
> Address,
>            and Remote Peer Port.</t>
> 
> => better!
> 
>    > PS: BTW please note it is useless to copy the External Address in
> all
>    > cases.
> 
>    It's useful if the PCP client was trying to do both a NAT request
>    and a firewall request -- e.g., it is an IPv6-only device listening
>    on a single IPv6 address and port and wants to get both NAT64
>    mapped and IPv6 firewall pinhole.  The server still needs to copy
> it,
>    even if it's useless in other cases to the PCP client.
> 
> => following this argument the External Address and Port should be
> copied in error responses too. Should we add a text?

The Requested External Address and Requested External Port should be
copied, yes.  Added text.

-d


> Regards
> 
> Francis.Dupont@fdupont.fr


From Francis.Dupont@fdupont.fr  Fri Oct 14 09:29:39 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 11D3421F8CA9 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level: 
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=0.117,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0BLf1+jEwt7r for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:29:38 -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 4CA8321F8C9D for <pcp@ietf.org>; Fri, 14 Oct 2011 09:29:38 -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 p9EGTZcE061684; Fri, 14 Oct 2011 18:29:35 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110141629.p9EGTZcE061684@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Reinaldo Penno <rpenno@juniper.net>
In-reply-to: Your message of Fri, 14 Oct 2011 12:09:55 EDT. <CABDACE3.5513A%rpenno@juniper.net> 
Date: Fri, 14 Oct 2011 18:29:35 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] PEER vs. explicit mappings
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, 14 Oct 2011 16:29:39 -0000

 In your previous mail you wrote:

   >    I think your 'implicit mappings' are called 'sessions' and are already
   >    defined elsewhere.
   >
   > => I don't want to use another terminology without agreed definitions.
   > According to the terminology and base drafts until the version 14,
   > MAP clearly acts on explicit dynamic mappings and PEER on implicit
   > dynamic mappings.
   > So why to change this?
   
   This a construct we defined. I see no problem in collapsing and simplifying
   the concepts. 'Sessions' are defined and used in NAT64 and other RFCs.
   
=> if the idea is to say 'sessions' is a shorter name for implicit dynamic
mappings and PEER acts on sessions I have no objection.

Regards

Francis.Dupont@fdupont.fr

PS: as far as I can understand here and now the verb "act" means:
 - recreate with suggested external address and port,
  can fail the same way than for PREFER_FAILURE

 - create without suggested external port (or address)

 - eventually extend the lifetime if the implicit dynamic mapping
  (oops, the session) already exists (if it doesn't exist then
  we are in one of the two previous cases, this means in particular
  a PEER request without suggested address and port always succeed,
  which raises the two questions if the request matches an explicit
  dynamic mapping (return its remaining lifetime? it should not happen
  so is it useful to find a way to warn the client?) or a static
  mapping (obviously return UINT32_MAX lifetime))

From Francis.Dupont@fdupont.fr  Fri Oct 14 09:33:33 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 7799421F8C5F for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.113,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OmyvzCHEagDu for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:33:33 -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 BB8AE21F8BA0 for <pcp@ietf.org>; Fri, 14 Oct 2011 09:33:32 -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 p9EGXUpg061948; Fri, 14 Oct 2011 18:33:30 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110141633.p9EGXUpg061948@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Reinaldo Penno <rpenno@juniper.net>
In-reply-to: Your message of Fri, 14 Oct 2011 12:10:52 EDT. <CABDAD1C.5513D%rpenno@juniper.net> 
Date: Fri, 14 Oct 2011 18:33:30 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] renewal time
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, 14 Oct 2011 16:33:33 -0000

 In your previous mail you wrote:

   So, if it is 5 years, it is 'rounded' to 2 hours?
   
=> so if it is 5 years you launch an expire timer for in 5 years
and eventually a renew timer for in 2 hours.
As far as I can understand it is the meaning of the word "renewal"
and obviously I was right when I asked for a clarification (:-).
   
Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 14 09:49:27 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 9208421F8CB1 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.489
X-Spam-Level: 
X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eeTbQpLTHJL2 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:49:27 -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 A388C21F8CB4 for <pcp@ietf.org>; Fri, 14 Oct 2011 09:49:26 -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 p9EGnPm5062882 for <pcp@ietf.org>; Fri, 14 Oct 2011 18:49:25 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110141649.p9EGnPm5062882@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Fri, 14 Oct 2011 18:49:25 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] external address and port in deletes
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, 14 Oct 2011 16:49:27 -0000

It is clear in base 14 (and previous) the suggested external address and port
are ignored in deletes (MAP requests with lifetime == 0).
There is nothing specified about the assigned external address and port
in the response, IMHO they must be copied from the request exactly
for the reasons avanced for errors.
BTW the term "assigned" has no meaning in this case, and we have two
corner cases where it even doesn't exist at all: a delete for no
matching mapping, and a delete all where there is no mapping of
another type (i.e., no state for the subscriber after the processing
of the request).
Now should we add a statement about this? IMHO we should, I suggest
to add in:

   In requests where the requested lifetime is 0, the suggested external
   address and port fields MUST be set to zero on transmission and MUST
   be ignored on reception.

that the fields MUST be copied to the response.

Regards

Francis.Dupont@fdupont.fr

PS: an interesting side effect is the delete success response carries
one bit of information: the fact the corresponding (and identical at
the R bit exception :-) request was processed at least once.
And no more is needed...

From simon.perreault@viagenie.ca  Fri Oct 14 09:55:34 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 9D03021F8C65 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LRgqIiH0yd8B for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:55:34 -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 6739321F8B0F for <pcp@ietf.org>; Fri, 14 Oct 2011 09:55:27 -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 D0AAA21F70 for <pcp@ietf.org>; Fri, 14 Oct 2011 12:55:26 -0400 (EDT)
Message-ID: <4E98697E.4060804@viagenie.ca>
Date: Fri, 14 Oct 2011 12:55:26 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110720 Thunderbird/5.0
MIME-Version: 1.0
To: pcp@ietf.org
References: <201110141613.p9EGDwdA060721@givry.fdupont.fr>
In-Reply-To: <201110141613.p9EGDwdA060721@givry.fdupont.fr>
X-Enigmail-Version: 1.2.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [pcp] existing mapping and PREFER_FAILURE
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, 14 Oct 2011 16:55:34 -0000

On 2011-10-14 12:13, Francis Dupont wrote:
>    Can this problem be entirely avoided by the application listening
>    on the port using INADDR_ANY or SO_EXCLUSIVEADDRUSE or something else?  
>    It has been my understanding that it's impossible for an application 
>    to prevent the OS from using its listening socket for the OS's outgoing
>    connections, from an explanation over a year ago from Simon.  
>    
> => it is OS dependent, I can answer (yes) for BSDs, I have never been convinced
> by SO_REUSEADDR implementation on Linux, and SO_EXCLUSIVEADDRUSE is
> supposed to be the (other) solution on recent versions of Windows...

I heard my name! ;)

The point is that we cannot require PCP clients to go through the very
tricky steps that are needed to ensure exclusive use of a port. PCP has
to work without PCP clients having exclusive use of a port.

The current text is OK in this regard.

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  Fri Oct 14 09:55:47 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 64F6121F8558 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.929
X-Spam-Level: 
X-Spam-Status: No, score=-104.929 tagged_above=-999 required=5 tests=[AWL=1.670, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xaph5KAb2HP8 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 09:55:46 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 88ABC21F85A1 for <pcp@ietf.org>; Fri, 14 Oct 2011 09:55:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=5823; q=dns/txt; s=iport; t=1318611346; x=1319820946; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=swgy4QWyfVk72KkoKy2N7yjvQkJif+J1oO9kWwxRYxY=; b=j9lYhdDxvxCfwNWmVYcOQ1dgMLx57Q0YAQgt3xBqDXbZNUuMVQ6CWXmD WKGfyfjbeaphE6rGQfRHRROTTUvKMXxIsMTacSoJ+4Hpdan9kfoOkWxR1 erwUhqDyP5LMsWSGS7l0r8T86me7biu/QVkeLCfYU/s236hxDpyPIb7N4 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoMAAARpmE6rRDoH/2dsb2JhbABDmT2BbI08gQWBbgEBAQMBCAoBFxAzDAUHAQMCCQ8BAQEDAQEBJwcZIwoDBggBAQQTCw4Jh12ZBgGeXId5BIgBnWs
X-IronPort-AV: E=Sophos;i="4.69,347,1315180800";  d="scan'208";a="7928292"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 14 Oct 2011 16:55:45 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9EGthkR026172; Fri, 14 Oct 2011 16:55:43 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Keith Moore'" <moore@network-heretics.com>
References: <201110140816.p9E8GkHr031221@givry.fdupont.fr> <D70B1B1F-7210-4FF0-9ACD-9F27612A4435@network-heretics.com> <04cc01cc8a80$43e638b0$cbb2aa10$@com> <C16E40EC-50A5-46DA-8342-738AFC172B68@network-heretics.com>
In-Reply-To: <C16E40EC-50A5-46DA-8342-738AFC172B68@network-heretics.com>
Date: Fri, 14 Oct 2011 09:55:43 -0700
Message-ID: <055601cc8a92$1c8fb4a0$55af1de0$@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: AcyKixx9dWTINK8jSeOvWReMzBMjvAAAqHVw
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 14 Oct 2011 16:55:47 -0000

> -----Original Message-----
> From: Keith Moore [mailto:moore@network-heretics.com]
> Sent: Friday, October 14, 2011 9:05 AM
> To: Dan Wing
> Cc: 'Francis Dupont'; pcp@ietf.org
> Subject: Re: [pcp] learning the external address
> 
> 
> On Oct 14, 2011, at 10:47 AM, Dan Wing wrote:
> 
> >> -----Original Message-----
> >> From: Keith Moore [mailto:moore@network-heretics.com]
> >> Sent: Friday, October 14, 2011 4:46 AM
> >> To: Francis Dupont
> >> Cc: Dan Wing; pcp@ietf.org
> >> Subject: Re: [pcp] learning the external address
> >>
> >>
> >> On Oct 14, 2011, at 4:16 AM, Francis Dupont wrote:
> >>
> >>> In your previous mail you wrote:
> >>>
> >>>  Without a lifetime for that address, it is irresponsible to
> >>>  tell the client the external IP address -- even if there is only
> >>>  one external IP address.
> >>>
> >>> => so it is irresponsible to implement an IWF because both
> >>> NAT-PMP and UPnP IGD (v1 or v2) provide a primitive which
> >>> returns the external IP address without a lifetime.
> >>> BTW is it the official position of the WG?
> >
> > Get a mapping, and maintain that mapping.  It is not PCP's
> > responsibility to perpetuate a mistake in UPnP IGD and in
> > NAT-PMP.
> >
> >> FWIW, I don't agree with that position.
> >
> > I don't see how to reconcile that
> >
> >  1.  networks change, and nothing lasts forever.  Hence,
> >      DNS has TTLs, lack of route advertisements means the
> >      route is no longer valid, DHCP has leases, and so on.
> >  2.  UPnP IGD and NAT-PMP both assume the IP address lasts
> >      forever.  It does not last forever.
> 
> An IP address binding does not last forever, because nothing lasts
> forever.   But it might last indefinitely.  NATs can be stateless,
> firewalls can have static rules.
> 
> My understanding is that DHCP leasing was designed based on the
> assumption that PCs crash or get shut down without any warning.  If
> DHCP handed out addresses to PCs without some sort of expiration,
> eventually all of those addresses would be assigned to PCs that had
> crashed and lost their memory of previous address assignments.
> Unfortunately, that design choice in DHCP led to a mentality that said
> that the network could change an address binding for frivolous reasons.
> That was an unintended consequence, and not a desirable one.  The
> Internet architecture didn't then, and still doesn't, have a good,
> widely-applicable mechanism for allowing applications to tolerate
> addresses being changed out from under them.
> 
> DNS TTLs are similarly problematic, at least as a sole mechanism.
> Obviously there's a need to expire stale RRs from caches.  But TTLs are
> at best a stopgap mechanism.  The problem is that you rarely know in
> advance when a RR needs to change, and even when you do, DNS doesn't
> give you a mechanism to gracefully manage that change.   Really you
> need additional mechanisms: the ability to instantly update or at least
> delete all replicas when an RR changes (dynamic update does address
> this problem to some degree); and for those cases where you do know in
> advance that an RR will change, you would like to have the ability to
> pre-propagate the new RR in advance of it being advertised, and set an
> absolute expiration date-time on the old RR (which would effectively
> cause the TTL on the old RR to decrease down to zero as that expiration
> date-time approached).
> 
> So I don't think either DNS or DHCP should be cited as good examples of
> how to manage cached bindings with finite lifetimes.
> 
> What I disagree with in the quoted statement above is that it's
> "irresponsible" to tell a client an external IP address without a
> lifetime.  What might be irresponsible is making up a lifetime where
> one did not exist. 

Well, no matter if a subscriber gets their IP address via PPPoE 
(which doesn't have a concept of lease duration in IPCP)
or via DHCP (which has a lease duration).

> If the binding is of indefinite duration, the
> protocol should allow the NAT or firewall to say so.
>
> Realize also that even a DNS TTL or a DHCP lease time is no guarantee
> that the binding will be valid for that long. 

Never said it was.  It's an indication that the information may
not be valid beyond that time.

> RRs do get updated
> without advance notice; routers (especially consumer-grade routers) get
> wedged and have to be rebooted, causing all of their old leases to be
> forgotten.    For similar reasons, a stated lifetime in a PCP binding
> can't be expected to be a guarantee either.  But a TTL is a poor
> mechanism for dealing with that case.

Here is some Dan <philosophy>:  the socket APIs were designed back
in the days of the hosts file, when things were static.  The
introduction of DNS, which should have inspired movement towards
a more dynamic API to translate hostsnames to addresses, did not
cause such inspiration.  getaddrinfo defined in RFC3493 didn't
do it, either.  Networking, by its nature, is dynamic.  Encouraging
implementation

A thought experiment:  if we were to return an address and indicate 
it has infinite duration, and the ISP renumbers their network (or
the subscriber moves from ISP-A to ISP-B, due to cost or
dynamically because of failure of ISP-A) -- do we want a self-
recoverable system, or do we want a system that forces the
user to take manual action?

I would want a self-recoverable system, and the way I see
to achieve that is by having the PCP occasionally ask if
the mapping is still valid, exists, and has the same IP
address.  This causes applications to be coded expecting
these changes that do, really, occur in real life.  And
results in a better-working Internet for everyone.
</philosophy>

-d





From dwing@cisco.com  Fri Oct 14 10:00:38 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 71F5421F8C57 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 10:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.981
X-Spam-Level: 
X-Spam-Status: No, score=-104.981 tagged_above=-999 required=5 tests=[AWL=1.618, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ilm2xsCShPu for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 10:00:38 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 0FA9A21F8B09 for <pcp@ietf.org>; Fri, 14 Oct 2011 10:00:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1714; q=dns/txt; s=iport; t=1318611638; x=1319821238; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=fZhmep+QjEaN10qn+sdhKL1CQMOdU2PA6NtDnCtnnks=; b=Oj7UK1ZbYVEo27TXVJZXWzb5NTGgue19wnv/QCtrbwvPrUzOK0BapwRP Ue5ckPPYp6chrNU25u0xFaNmbrpT45DUVA1chpDmtz0+FzmQmgDnbA1xj 706wo92elNj0HFZj+T1sT9uTklbdOhbI3PKOuuPdABRBCXorCR5UTI2Jc I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoMAAPFpmE6rRDoH/2dsb2JhbABDmT6BbI08gQWBbgEBAQMBCAoBFxA/DAEDAgkOAQEBBAEBAScHGSMKCQgBAQQBEgsXh12ZBgGeWod5BIgBnWs
X-IronPort-AV: E=Sophos;i="4.69,347,1315180800";  d="scan'208";a="7946036"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 14 Oct 2011 17:00:38 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9EH0bL9030400; Fri, 14 Oct 2011 17:00:37 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Reinaldo Penno'" <rpenno@juniper.net>, "'Francis Dupont'" <Francis.Dupont@fdupont.fr>
References: <201110141544.p9EFicH2058604@givry.fdupont.fr> <CABDAD1C.5513D%rpenno@juniper.net>
In-Reply-To: <CABDAD1C.5513D%rpenno@juniper.net>
Date: Fri, 14 Oct 2011 10:00:37 -0700
Message-ID: <055701cc8a92$cc032c00$64098400$@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: AcyKiGJ/ju8+T6f5TlGI3mAsWieYqAAA3XBCAAGXE+A=
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] renewal time
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, 14 Oct 2011 17:00:38 -0000

> -----Original Message-----
> From: Reinaldo Penno [mailto:rpenno@juniper.net]
> Sent: Friday, October 14, 2011 9:11 AM
> To: Francis Dupont
> Cc: Dan Wing; pcp@ietf.org
> Subject: Re: [pcp] renewal time
> 
> So, if it is 5 years, it is 'rounded' to 2 hours?

Let's back up a minute.  

The maximum value for Lifetime is about 130 years, give or take a few years.
That's longer than any of our human lifetimes, and certainly longer than any
equipment will actually maintain state before crashing, losing power, or
getting swapped out with some fancy new equipment.

If the PCP server sends a large value of 130 years, do you find it
reasonable or unreasonable for the PCP client to accept that value as The
Truth?


Myself, I find it unreasonable to accept such a large value on its face.
Almost all DNS implementations, for example, provide a way for the DNS
administrator to enforce both a minimum TTL (to avoid thrashing with too
many DNS queries for the same RR) and a maximum TTL (to avoid consuming
memory for seldom-queried RRs).  The text in the document encourages
implementations to provide similar sanity checks on their implementations,
on both the PCP server (which nobody has complained about) and on the PCP
client (which you, Francis, and Keith all seem to object to).

-d


> 
> On 10/14/11 8:44 AM, "Francis Dupont" <Francis.Dupont@fdupont.fr>
> wrote:
> 
> >  In your previous mail you wrote:
> >
> >    If the lifetime returned by the PCP Server is going to be
> discarded
> >
> > => it is not discarded, it is round down to the 2 hour value for
> > the renewal, if the client wants to renew...
> >
> > Regards
> >
> > Francis.Dupont@fdupont.fr


From moore@network-heretics.com  Fri Oct 14 10:02:48 2011
Return-Path: <moore@network-heretics.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 110C421F8AEC for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 10:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.098
X-Spam-Level: 
X-Spam-Status: No, score=-4.098 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8dBQtQCcJ89J for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 10:02:47 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 37CCC21F84D5 for <pcp@ietf.org>; Fri, 14 Oct 2011 10:02:47 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id BB2B120DD2; Fri, 14 Oct 2011 13:02:46 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Fri, 14 Oct 2011 13:02:46 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=y+t 9lONCDqX3z/ne5iRtk3xvlSc=; b=hkDzGB6GRBQyeV9jjwfBYrOKyIpg8l1xlj4 BXfabtcMmprwIlkICpQ+40gNVpguSD94+VP91nWD7f8uSLEATEGQI8Jgg/z8jjO7 7A1ylojEXtePL+7OzfeCMp/Fo7ePgIeum8AVsQ70j6Myjs++A4pd1iKH+MnMeT5X Zg0mfUJM=
X-Sasl-enc: HqBEt30OGFa2/s0zxsOUsmSIVMxrpvBUsKuYruEFzNks 1318611765
Received: from [192.168.1.16] (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 7227948341B; Fri, 14 Oct 2011 13:02:45 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-10-1002126947
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <055601cc8a92$1c8fb4a0$55af1de0$@com>
Date: Fri, 14 Oct 2011 13:02:23 -0400
Message-Id: <488C16D1-CC44-4BB2-A914-913EE01080E8@network-heretics.com>
References: <201110140816.p9E8GkHr031221@givry.fdupont.fr> <D70B1B1F-7210-4FF0-9ACD-9F27612A4435@network-heretics.com> <04cc01cc8a80$43e638b0$cbb2aa10$@com> <C16E40EC-50A5-46DA-8342-738AFC172B68@network-heretics.com> <055601cc8a92$1c8fb4a0$55af1de0$@com>
To: "Dan Wing" <dwing@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 14 Oct 2011 17:02:48 -0000

--Apple-Mail-10-1002126947
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Oct 14, 2011, at 12:55 PM, Dan Wing wrote:

> Here is some Dan <philosophy>:  the socket APIs were designed back
> in the days of the hosts file, when things were static.  The
> introduction of DNS, which should have inspired movement towards
> a more dynamic API to translate hostsnames to addresses, did not
> cause such inspiration.  getaddrinfo defined in RFC3493 didn't
> do it, either.  Networking, by its nature, is dynamic.  Encouraging
> implementation

So let's make TCP and UDP address agile, with secure update.   Or define =
them in terms of tokens that aren't IP addresses, and build a mapping =
layer between endpoint identifiers and addresses that is fast, robust, =
low-overhead, and secure, and works well for both fixed and mobile hosts =
networks.   Anything short of that doesn't solve the problem.   LISP is =
making a stab at it, and so is HIP, but last I knew both of them still =
fell way short of fixing the problem.

> A thought experiment:  if we were to return an address and indicate=20
> it has infinite duration, and the ISP renumbers their network (or
> the subscriber moves from ISP-A to ISP-B, due to cost or
> dynamically because of failure of ISP-A) -- do we want a self-
> recoverable system, or do we want a system that forces the
> user to take manual action?

I want a self-recoverable system.  It's just that I recognize that a TTL =
(by itself) is a poor way to build such a system.

Keith



--Apple-Mail-10-1002126947
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div><div>On Oct 14, 2011, at 12:55 PM, Dan Wing wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Here is some =
Dan &lt;philosophy&gt;: &nbsp;the socket APIs were designed back<br>in =
the days of the hosts file, when things were static. =
&nbsp;The<br>introduction of DNS, which should have inspired movement =
towards<br>a more dynamic API to translate hostsnames to addresses, did =
not<br>cause such inspiration. &nbsp;getaddrinfo defined in RFC3493 =
didn't<br>do it, either. &nbsp;Networking, by its nature, is dynamic. =
&nbsp;Encouraging<br>implementation<br></span></blockquote><div><br></div>=
So let's make TCP and UDP address agile, with secure update. &nbsp; Or =
define them in terms of tokens that aren't IP addresses, and build a =
mapping layer between endpoint identifiers and addresses that is fast, =
robust, low-overhead, and secure, and works well for both fixed and =
mobile hosts networks. &nbsp; Anything short of that doesn't solve the =
problem. &nbsp; LISP is making a stab at it, and so is HIP, but last I =
knew both of them still fell way short of fixing the =
problem.</div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">A thought =
experiment: &nbsp;if we were to return an address and indicate<span =
class=3D"Apple-converted-space">&nbsp;</span><br>it has infinite =
duration, and the ISP renumbers their network (or<br>the subscriber =
moves from ISP-A to ISP-B, due to cost or<br>dynamically because of =
failure of ISP-A) -- do we want a self-<br>recoverable system, or do we =
want a system that forces the<br>user to take manual =
action?<br></span></blockquote><div><br></div>I want a self-recoverable =
system. &nbsp;It's just that I recognize that a TTL (by itself) is a =
poor way to build such a =
system.</div><div><br></div><div>Keith</div><div><br></div><br></div></bod=
y></html>=

--Apple-Mail-10-1002126947--

From rpenno@juniper.net  Fri Oct 14 10:34:35 2011
Return-Path: <rpenno@juniper.net>
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 46E4221F8C3A for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 10:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NnYd0I1zNFgU for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 10:34:34 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id E7B1421F8BA7 for <pcp@ietf.org>; Fri, 14 Oct 2011 10:34:32 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP;  Fri, 14 Oct 2011 10:34:34 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.83.0; Fri, 14 Oct 2011 10:31:04 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 14 Oct 2011 13:31:04 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Dan Wing <dwing@cisco.com>, 'Francis Dupont' <Francis.Dupont@fdupont.fr>
Date: Fri, 14 Oct 2011 13:31:02 -0400
Thread-Topic: [pcp] renewal time 
Thread-Index: AcyKiGJ/ju8+T6f5TlGI3mAsWieYqAAA3XBCAAGXE+AAATWrqQ==
Message-ID: <CABDBFE6.55162%rpenno@juniper.net>
In-Reply-To: <055701cc8a92$cc032c00$64098400$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] renewal time
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, 14 Oct 2011 17:34:35 -0000

On 10/14/11 10:00 AM, "Dan Wing" <dwing@cisco.com> wrote:

>> -----Original Message-----
>> From: Reinaldo Penno [mailto:rpenno@juniper.net]
>> Sent: Friday, October 14, 2011 9:11 AM
>> To: Francis Dupont
>> Cc: Dan Wing; pcp@ietf.org
>> Subject: Re: [pcp] renewal time
>>=20
>> So, if it is 5 years, it is 'rounded' to 2 hours?
>=20
> Let's back up a minute.
>=20
> The maximum value for Lifetime is about 130 years, give or take a few yea=
rs.
> That's longer than any of our human lifetimes, and certainly longer than =
any
> equipment will actually maintain state before crashing, losing power, or
> getting swapped out with some fancy new equipment.
>=20
> If the PCP server sends a large value of 130 years, do you find it
> reasonable or unreasonable for the PCP client to accept that value as The
> Truth?

Certainly not and I agree with both you and Francis but the point is: what
is reasonable?=20

If we define that 86400 is the threshold of reasonable, then the follow up
question is: what happens if the client receives a lifetime greater than
that? I'm okay with rounding down to 24 hrs but as the same time some kind
of warning must the exposed such that a problematic PCP server is fixed as
opposed to the PCP Client masking it out by silently 'fixing' the issue.

Thanks,

Reinaldo

>=20
>=20
> Myself, I find it unreasonable to accept such a large value on its face.
> Almost all DNS implementations, for example, provide a way for the DNS
> administrator to enforce both a minimum TTL (to avoid thrashing with too
> many DNS queries for the same RR) and a maximum TTL (to avoid consuming
> memory for seldom-queried RRs).  The text in the document encourages
> implementations to provide similar sanity checks on their implementations=
,
> on both the PCP server (which nobody has complained about) and on the PCP
> client (which you, Francis, and Keith all seem to object to).
>=20
> -d
>=20
>=20
>>=20
>> On 10/14/11 8:44 AM, "Francis Dupont" <Francis.Dupont@fdupont.fr>
>> wrote:
>>=20
>>>  In your previous mail you wrote:
>>>=20
>>>    If the lifetime returned by the PCP Server is going to be
>> discarded
>>>=20
>>> =3D> it is not discarded, it is round down to the 2 hour value for
>>> the renewal, if the client wants to renew...
>>>=20
>>> Regards
>>>=20
>>> Francis.Dupont@fdupont.fr
>=20


From rpenno@juniper.net  Fri Oct 14 11:18:16 2011
Return-Path: <rpenno@juniper.net>
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 232E121F8B66 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 11:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_24=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEV1ik23+pei for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 11:18:15 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 9C3BB21F8C7F for <pcp@ietf.org>; Fri, 14 Oct 2011 11:18:13 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP;  Fri, 14 Oct 2011 11:18:15 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.83.0; Fri, 14 Oct 2011 11:17:00 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 14 Oct 2011 14:16:59 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Date: Fri, 14 Oct 2011 14:16:56 -0400
Thread-Topic: [pcp] PEER vs. explicit mappings 
Thread-Index: AcyKjnoWWfaM45toREyjTu+2Sf2rvwADvqmB
Message-ID: <CABDCAA8.55188%rpenno@juniper.net>
In-Reply-To: <201110141629.p9EGTZcE061684@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] PEER vs. explicit mappings
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, 14 Oct 2011 18:18:16 -0000

On 10/14/11 9:29 AM, "Francis Dupont" <Francis.Dupont@fdupont.fr> wrote:

>  In your previous mail you wrote:
>=20
>>    I think your 'implicit mappings' are called 'sessions' and are alread=
y
>>    defined elsewhere.
>>=20
>> =3D> I don't want to use another terminology without agreed definitions.
>> According to the terminology and base drafts until the version 14,
>> MAP clearly acts on explicit dynamic mappings and PEER on implicit
>> dynamic mappings.
>> So why to change this?
>   =20
>    This a construct we defined. I see no problem in collapsing and simpli=
fying
>    the concepts. 'Sessions' are defined and used in NAT64 and other RFCs.
>   =20
> =3D> if the idea is to say 'sessions' is a shorter name for implicit dyna=
mic
> mappings and PEER acts on sessions I have no objection.
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr
>=20
> PS: as far as I can understand here and now the verb "act" means:
>  - recreate with suggested external address and port,
>   can fail the same way than for PREFER_FAILURE

Agreed but one nit. I'm not sure there is a 'recreate' per se in the PCP
Server but I understand it is useful for explaining the procedure.

As far as the PCP Server goes there are:

- New mappings
- Extension of lifetime

A 'recreate' is just a new mapping that might (or not) ask for a specific
external IP:port, with/out PREFER_FAILURE.


>=20
>  - create without suggested external port (or address)

Yep.

>=20
>  - eventually extend the lifetime if the implicit dynamic mapping
>   (oops, the session) already exists
> (if it doesn't exist then
>   we are in one of the two previous cases, this means in particular
>   a PEER request without suggested address and port always succeed,
>   which raises the two questions if the request matches an explicit
>   dynamic mapping (return its remaining lifetime? it should not happen
>   so is it useful to find a way to warn the client?) or a static
>   mapping (obviously return UINT32_MAX lifetime))


Yes.



From dwing@cisco.com  Fri Oct 14 12:39:37 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 5EC7A21F8D6E for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 12:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id URW9PEt4scb8 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 12:39:36 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id E9FD921F8D6D for <pcp@ietf.org>; Fri, 14 Oct 2011 12:39:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1936; q=dns/txt; s=iport; t=1318621177; x=1319830777; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=JZEQY4/qudgYk1cGxqfkeZJq6iJyhmJNts4ozCn12ds=; b=mgEfVZItWPkl+U4pdrldzCVOHECH1s05Jd5SFhOVE9XyoAS4xuVZ0Itc DGlIlElSfQLRa9HoSTD1dxFOgw0WzSsXHhD4tZ/fD/HZSy6a4Tpa/wR+q RcskAAJc/blFOtE5rCtiTotRHkczDZPLayBjCNK03+uA5wT6r0TvBHGAg w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoMAADWPmE6rRDoH/2dsb2JhbABDmT+BbI08gQWBbgEBAQQICgEXEDMMDAEDAgkPAQEEAQEBJwcZIwoJCAEBBBMLF6B+AZ5Ah3kEiAGdaw
X-IronPort-AV: E=Sophos;i="4.69,348,1315180800";  d="scan'208";a="7982167"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 14 Oct 2011 19:39:36 +0000
Received: from dwingWS ([128.107.106.33]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9EJda12013312; Fri, 14 Oct 2011 19:39:36 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Keith Moore'" <moore@network-heretics.com>
References: <201110140816.p9E8GkHr031221@givry.fdupont.fr> <D70B1B1F-7210-4FF0-9ACD-9F27612A4435@network-heretics.com> <04cc01cc8a80$43e638b0$cbb2aa10$@com> <C16E40EC-50A5-46DA-8342-738AFC172B68@network-heretics.com> <055601cc8a92$1c8fb4a0$55af1de0$@com> <488C16D1-CC44-4BB2-A914-913EE01080E8@network-heretics.com>
In-Reply-To: <488C16D1-CC44-4BB2-A914-913EE01080E8@network-heretics.com>
Date: Fri, 14 Oct 2011 12:39:36 -0700
Message-ID: <064901cc8aa9$01a70190$04f504b0$@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: AcyKkyCt8YipF6kISH6OVqUfuUi1/AAFa+TA
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 14 Oct 2011 19:39:37 -0000

> -----Original Message-----
> From: Keith Moore [mailto:moore@network-heretics.com]
> Sent: Friday, October 14, 2011 10:02 AM
> To: Dan Wing
> Cc: 'Francis Dupont'; pcp@ietf.org
> Subject: Re: [pcp] learning the external address
> 
> On Oct 14, 2011, at 12:55 PM, Dan Wing wrote:
> 
> 
> 	Here is some Dan <philosophy>:  the socket APIs were designed
> back
> 	in the days of the hosts file, when things were static.  The
> 	introduction of DNS, which should have inspired movement towards
> 	a more dynamic API to translate hostsnames to addresses, did not
> 	cause such inspiration.  getaddrinfo defined in RFC3493 didn't
> 	do it, either.  Networking, by its nature, is dynamic.
> Encouraging
> 	implementation
> 
> 
> 
> So let's make TCP and UDP address agile, with secure update.   Or
> define them in terms of tokens that aren't IP addresses, and build a
> mapping layer between endpoint identifiers and addresses that is fast,
> robust, low-overhead, and secure, and works well for both fixed and
> mobile hosts networks.   Anything short of that doesn't solve the
> problem.   LISP is making a stab at it, and so is HIP, but last I knew
> both of them still fell way short of fixing the problem.
> 
> 
> 	A thought experiment:  if we were to return an address and
> indicate
> 	it has infinite duration, and the ISP renumbers their network (or
> 	the subscriber moves from ISP-A to ISP-B, due to cost or
> 	dynamically because of failure of ISP-A) -- do we want a self-
> 	recoverable system, or do we want a system that forces the
> 	user to take manual action?
> 
> 
> 
> I want a self-recoverable system.  It's just that I recognize that a
> TTL (by itself) is a poor way to build such a system.

Sure.  But it's a step in the right direction.

A TTL of infinity makes it impossible, because then everything assumes
the returned values are valid until the end of time.

-d



From moore@network-heretics.com  Fri Oct 14 12:49:03 2011
Return-Path: <moore@network-heretics.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 183AB21F8D7A for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 12:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.027
X-Spam-Level: 
X-Spam-Status: No, score=-4.027 tagged_above=-999 required=5 tests=[AWL=-0.428, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q8s-8mPud8nI for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 12:49:02 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 9164821F8D45 for <pcp@ietf.org>; Fri, 14 Oct 2011 12:48:54 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id A09462118C; Fri, 14 Oct 2011 15:48:53 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 14 Oct 2011 15:48:53 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=SFPpg1AzyTIBUJ4R3F/pY464X3Y=; b=bz iAaN+lmhGGbfoG7g4DlL3U20peKsbohB7F/auoOuM4/ocW7anLOkhzVKCg1q8/l2 AWMyvNB20DTWdqxYjPXtmtJ5EdLrCY0Rb1WILelx0drblE7RQzB06yTaQZMu2xZe ZOsJUU9FKVGU4rr+NxsUn9RoAZwPlli+pylUDcNDo=
X-Sasl-enc: IVKRsmQpaXz5vw2zDhqy3tR5savhsuWjhHfqiYDOLka5 1318621733
Received: from [192.168.1.16] (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id C3640483437; Fri, 14 Oct 2011 15:48:52 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <064901cc8aa9$01a70190$04f504b0$@com>
Date: Fri, 14 Oct 2011 15:48:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E5B455D-002D-47C2-A1D5-D1ACE8AFD1F3@network-heretics.com>
References: <201110140816.p9E8GkHr031221@givry.fdupont.fr> <D70B1B1F-7210-4FF0-9ACD-9F27612A4435@network-heretics.com> <04cc01cc8a80$43e638b0$cbb2aa10$@com> <C16E40EC-50A5-46DA-8342-738AFC172B68@network-heretics.com> <055601cc8a92$1c8fb4a0$55af1de0$@com> <488C16D1-CC44-4BB2-A914-913EE01080E8@network-heretics.com> <064901cc8aa9$01a70190$04f504b0$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 14 Oct 2011 19:49:03 -0000

On Oct 14, 2011, at 3:39 PM, Dan Wing wrote:

>> I want a self-recoverable system.  It's just that I recognize that a
>> TTL (by itself) is a poor way to build such a system.
>=20
> Sure.  But it's a step in the right direction.
>=20
> A TTL of infinity makes it impossible, because then everything assumes
> the returned values are valid until the end of time.

Nah, it just means that every application and/or host picks its own =
maximum retry value.  And hopefully they don't rely exclusively on PCP =
to tell them when a binding is changing.

Ideally there would be a mechanism by which a NAT or firewall or =
whatever could let its clients know when there's been a disruptive =
event.    Maybe by sending a message (or three) to a multicast group.

Keith


From dwing@cisco.com  Fri Oct 14 13:16:23 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 064E321F8B4C for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 13:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.885
X-Spam-Level: 
X-Spam-Status: No, score=-104.885 tagged_above=-999 required=5 tests=[AWL=1.714, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rg1mDpyhAcR1 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 13:16:22 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 84C1721F8B43 for <pcp@ietf.org>; Fri, 14 Oct 2011 13:16:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1597; q=dns/txt; s=iport; t=1318623382; x=1319832982; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=sXrmKviQIzKgKUcBX1LpO8/nhb2mEjIEOoQWuGqQ+78=; b=gXO1gKN4VmTjXWaBUKv5RM5xtFgvKLH+zfQXveqNEp2Up7qudFEkwleS LSil0xAI6/obVzt59oV0wKxG804OpPIaxVRT+W7Pp0BeSECZWWzjr5/Lw ypWtwP4gJYY2CDf/Vm2bfJAtCw6g8pQJKX47W2YpodJTMjE98g7J2d1y0 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoMAAOKXmE6rRDoI/2dsb2JhbABDmT+BbI08gQWBbgEBAQQICgEXEDMMDAEDAgkPAQEEAQEBJwcZIwoJCAEBBBMLF6BwAZ5Ah3kEiAGdaw
X-IronPort-AV: E=Sophos;i="4.69,348,1315180800";  d="scan'208";a="7946040"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 14 Oct 2011 20:16:21 +0000
Received: from dwingWS ([128.107.106.33]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p9EKGLpv023167; Fri, 14 Oct 2011 20:16:21 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Keith Moore'" <moore@network-heretics.com>
References: <201110140816.p9E8GkHr031221@givry.fdupont.fr> <D70B1B1F-7210-4FF0-9ACD-9F27612A4435@network-heretics.com> <04cc01cc8a80$43e638b0$cbb2aa10$@com> <C16E40EC-50A5-46DA-8342-738AFC172B68@network-heretics.com> <055601cc8a92$1c8fb4a0$55af1de0$@com> <488C16D1-CC44-4BB2-A914-913EE01080E8@network-heretics.com> <064901cc8aa9$01a70190$04f504b0$@com> <8E5B455D-002D-47C2-A1D5-D1ACE8AFD1F3@network-heretics.com>
In-Reply-To: <8E5B455D-002D-47C2-A1D5-D1ACE8AFD1F3@network-heretics.com>
Date: Fri, 14 Oct 2011 13:16:21 -0700
Message-ID: <066801cc8aae$23ae7480$6b0b5d80$@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: AcyKqnDkBdXHURgGTSODLDbvEKUcwQAA2IZg
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 14 Oct 2011 20:16:23 -0000

> -----Original Message-----
> From: Keith Moore [mailto:moore@network-heretics.com]
> Sent: Friday, October 14, 2011 12:48 PM
> To: Dan Wing
> Cc: 'Francis Dupont'; pcp@ietf.org
> Subject: Re: [pcp] learning the external address
> 
> On Oct 14, 2011, at 3:39 PM, Dan Wing wrote:
> 
> >> I want a self-recoverable system.  It's just that I recognize that a
> >> TTL (by itself) is a poor way to build such a system.
> >
> > Sure.  But it's a step in the right direction.
> >
> > A TTL of infinity makes it impossible, because then everything
> assumes
> > the returned values are valid until the end of time.
> 
> Nah, it just means that every application and/or host picks its own
> maximum retry value.  And hopefully they don't rely exclusively on PCP
> to tell them when a binding is changing.
> 
> Ideally there would be a mechanism by which a NAT or firewall or
> whatever could let its clients know when there's been a disruptive
> event.    Maybe by sending a message (or three) to a multicast group.

draft-cheshire-pcp-recovery.  But that will only work if there is 
multicast between the PCP server and the client(s).  In different
environments this varies from impossible to trivial (e.g., non-
routed home network).  Impossible is that an SP isn't going to
deploy multicast between their PCP server and their subscribers
for the sole purpose of immediately informing the subscriber
equipment of an IP address change on the CGN itself.  

We need a way for PCP to work correctly without a multicast
message from the PCP server to the clients.

-d



From dwing@cisco.com  Fri Oct 14 15:11:34 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 7C2DB21F8C9D for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 15:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.266
X-Spam-Level: 
X-Spam-Status: No, score=-105.266 tagged_above=-999 required=5 tests=[AWL=1.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fF8LcZ75HBiF for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 15:11:29 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 3A30521F8BA0 for <pcp@ietf.org>; Fri, 14 Oct 2011 15:11:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2043; q=dns/txt; s=iport; t=1318630289; x=1319839889; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=YrMX9KfJSYyTuzMJzeAhxPgZtDj+M8Uqqs4n3GDn3zg=; b=hkoUpAZsfx3tyPQ6R2dbyCld0UK+sTAi3NYoKKWD4Cb+4lYxIBVz4P0j 6kY2nDgMWBNBRSUKKGJh9Xd0LvZBFGKfdHNMmmWs+n9DiHAPs14u8BIwu a9lL6vcn3w68WxDGA+/BOBiJ0N4me4uSSUBLMSDw4M2OpHl3uepLbqDYW o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApIAAHWymE6rRDoH/2dsb2JhbABDmT+BbI08gQWBbgEBAQECAQEBAQUKARcQLQcQBwEDAgkPAQEEAQEoBxkOFQoJCAEBBAESCxeHXQiZKQGeQAOHeQSIAZ1r
X-IronPort-AV: E=Sophos;i="4.69,348,1315180800";  d="scan'208";a="7974592"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 14 Oct 2011 22:11:29 +0000
Received: from dwingWS (dhcp-128-107-145-2.cisco.com [128.107.145.2]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9EMBSCR031906; Fri, 14 Oct 2011 22:11:28 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110141649.p9EGnPm5062882@givry.fdupont.fr>
In-Reply-To: <201110141649.p9EGnPm5062882@givry.fdupont.fr>
Date: Fri, 14 Oct 2011 15:11:28 -0700
Message-ID: <06ed01cc8abe$38ccd8b0$aa668a10$@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: AcyKkT569AsQRiiuSlaCouFthcK8tQALMzUA
Content-Language: en-us
Subject: Re: [pcp] external address and port in deletes
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, 14 Oct 2011 22:11:34 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Friday, October 14, 2011 9:49 AM
> To: pcp@ietf.org
> Subject: [pcp] external address and port in deletes
> 
> It is clear in base 14 (and previous) the suggested external address
> and port
> are ignored in deletes (MAP requests with lifetime == 0).
> There is nothing specified about the assigned external address and port
> in the response, IMHO they must be copied from the request exactly
> for the reasons avanced for errors.
> BTW the term "assigned" has no meaning in this case, and we have two
> corner cases where it even doesn't exist at all: a delete for no
> matching mapping, and a delete all where there is no mapping of
> another type (i.e., no state for the subscriber after the processing
> of the request).
> Now should we add a statement about this? IMHO we should, I suggest
> to add in:
> 
>    In requests where the requested lifetime is 0, the suggested
> external
>    address and port fields MUST be set to zero on transmission and MUST
>    be ignored on reception.
> 
> that the fields MUST be copied to the response.

So several can be in flight on the network at once?

How is this:

	<t>In requests where the requested Lifetime is 0, the
        Suggested External Address and Suggested External Port fields
        MUST be set to zero on transmission and MUST be ignored on
        reception, and these fields MUST be copied into the Assigned
        External IP Address and Assigned External Port of the response.</t>


> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: an interesting side effect is the delete success response carries
> one bit of information: the fact the corresponding (and identical at
> the R bit exception :-) request was processed at least once.
> And no more is needed...

-d

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


From Tina.Tsou.Zouting@huawei.com  Fri Oct 14 16:18:00 2011
Return-Path: <Tina.Tsou.Zouting@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 B74C821F8BF7 for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 16:18:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.029
X-Spam-Level: 
X-Spam-Status: No, score=-5.029 tagged_above=-999 required=5 tests=[AWL=1.570,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VZJSwMgBrlfE for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 16:18:00 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id E113121F8B1D for <pcp@ietf.org>; Fri, 14 Oct 2011 16:17:59 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LT200KXEWPWYB@szxga04-in.huawei.com> for pcp@ietf.org; Sat, 15 Oct 2011 07:17:56 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LT200LNDWPWOA@szxga04-in.huawei.com> for pcp@ietf.org; Sat, 15 Oct 2011 07:17:56 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEF97762; Sat, 15 Oct 2011 07:17:55 +0800
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sat, 15 Oct 2011 07:17:47 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.58]) by szxeml411-hub.china.huawei.com ([10.82.67.138]) with mapi id 14.01.0270.001; Sat, 15 Oct 2011 07:17:44 +0800
Date: Fri, 14 Oct 2011 23:17:43 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <A6A061BEE5DDC94A9692D9D81AF776DF0AAED40B@szxeml527-mbs.china.huawei.com>
X-Originating-IP: [10.193.34.158]
To: "pcp@ietf.org" <pcp@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C19635B@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: section 8
Thread-index: AQHMisd6AqbKitDQAEWxdFLEoPIx5w==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-hashedpuzzle: AOYX BIOG BYv2 BwYU B58K B9Ki CGLc CR3M EvBK E/yw FeN1 Fwz5 GSyO H9EU I38L I8IP; 1; cABjAHAAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {9C39B782-27DF-4909-8481-C49C3F17CEDC}; dABpAG4AYQAuAHQAcwBvAHUALgB6AG8AdQB0AGkAbgBnAEAAaAB1AGEAdwBlAGkALgBjAG8AbQA=; Fri, 14 Oct 2011 23:17:51 GMT;cwBlAGMAdABpAG8AbgAgADgA
x-cr-puzzleid: {9C39B782-27DF-4909-8481-C49C3F17CEDC}
X-CFilter-Loop: Reflected
References: <A6A061BEE5DDC94A9692D9D81AF776DF0AAEC289@szxeml527-mbs.china.huawei.com> <774B240D54DAB844B37EE80C2DD8E8BCB7E9DA@szxeml522-mbs.china.huawei.com> <A6A061BEE5DDC94A9692D9D81AF776DF0AAEC2F8@szxeml527-mbs.china.huawei.com> <A6A061BEE5DDC94A9692D9D81AF776DF0AAED40B@szxeml527-mbs.china.huawei.com>
Subject: [pcp] section 8
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, 14 Oct 2011 23:18:00 -0000

Hi,
In section 8, it reads:
  "It is REQUIRED that the PCP-controlled device assign the same
   external IP address to PCP-created explicit dynamic mappings and to
   implicit dynamic mappings for a given Internal Host.  In the absence
   of a PCP option indicating otherwise, it is REQUIRED that PCP-created
   explicit dynamic mappings be assigned the same external IP address."
It is not consistent with what we have discussed in the mailing list below. And it is a bit ambiguous in reading.

How about changing the second sentence from on of the 4 candidates as below?

Alternative 1:
PCP client should request same external IP address for an application if there is already any existing explicit mapping for that application.

Alternative 2:
PCP client should request the same external IP address if there are existing explict mappings, unless there is explicit reasons of not doing so, e.g. http://tools.ietf.org/html/draft-penno-pcp-zones-00

Alternative 3:
It is indicated by the PCP client that PCP-created explicit dynamic mappings be assigned the same external IP address, unless there are explicit reasons of not doing so, e.g. http://tools.ietf.org/html/draft-penno-pcp-zones-00"

Alternative 4:
It is indicated by the PCP client that PCP-created explicit dynamic mappings be assigned the same external IP address, unless a PCP option indicates different external IP address



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

From jhw@apple.com  Fri Oct 14 18:00:25 2011
Return-Path: <jhw@apple.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 34FCC21F8CEA for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 18:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wg-YNhtxxUqD for <pcp@ietfa.amsl.com>; Fri, 14 Oct 2011 18:00:24 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id C6C1F21F8C6F for <pcp@ietf.org>; Fri, 14 Oct 2011 18:00:24 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_I1Aneu4bUp9xo4R2CU5BfQ)"
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LT3007WQ1ELJRS1@mail-out.apple.com> for pcp@ietf.org; Fri, 14 Oct 2011 17:59:12 -0700 (PDT)
X-AuditID: 11807134-b7cc1ae0000078f0-4a-4e98dadf9e2a
Received: from ba0301a-dhcp89.apple.com (ba0301a-dhcp89.apple.com [17.193.14.217]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay14.apple.com (Apple SCV relay) with SMTP id 67.82.30960.FDAD89E4; Fri, 14 Oct 2011 17:59:11 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
Date: Fri, 14 Oct 2011 17:59:11 -0700
Message-id: <149DAB5A-3E9F-47C4-B710-5B00BDE544F8@apple.com>
To: PCP <pcp@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphluLIzCtJLcpLzFFi42IRPMh3U/f+rRl+BktWWVpMPvab1YHRY8mS n0wBjFFcNimpOZllqUX6dglcGfOmnmApOCxd8WPrWqYGxr/iXYycHBICJhINZ34zQthiEhfu rWfrYuTiEBJYwSSx53IzWIJNQEXi2+W7TCA2s0CCxIeD61hAbGEBWYlZNzcAxTk4WARUJR6c lgIJ8wrYSHSvXQ1WIgI0c/Xjh0wQcWOJNbfesUDskpdo+XqHbQIj9ywkU2chKYOIa0ssW/ia eRbQBmYBHYnJCxlRhSHsj+ePMC1gZFvFKFiUmpNYaWiil1hQkJOql5yfu4kRFEYNhSY7GA/+ 5D/EKMDBqMTD+zJnhp8Qa2JZcWXuIUYJDmYlEd7eVUAh3pTEyqrUovz4otKc1OJDjNIcLEri vD+3AKUE0hNLUrNTUwtSi2CyTBycUg2MxVl7jvec72OW0zo4Z9Jf1VizBKtjVttlxeLKFFvr 5A6tuHdGfu7k3Uujo74tZ55p+FDAobw84OSMC5pXe4Wvup5ddO7HhK9uLVFHwgS85K4nmZyu C/nfcXB2yvKnhiWLjwqy8jf4HL60UC1GbU1wSrvEprePv0re/b3c6k5RofF5/l9B1r7CSizF GYmGWsxFxYkAdh9HFx8CAAA=
Subject: [pcp] remapping sctp ports
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, 15 Oct 2011 01:00:25 -0000

--Boundary_(ID_I1Aneu4bUp9xo4R2CU5BfQ)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

everyone--

Question: is SCTP a transport protocol that uses 16-bit ports from the perspective of PCP servers?  NAT traversal for SCTP is not done by remapping the ports, and it doesn't make sense to ask for a NAT to redirect SCTP public port A to SCTP private port B where A != B due to the need to recalculate the CRC32 checksum it uses.

Perhaps a word about SCTP and its "unconventional" use of port numbers would be in order.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




--Boundary_(ID_I1Aneu4bUp9xo4R2CU5BfQ)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">everyone--<div><br></div><div>Question: is SCTP a transport protocol =
that uses 16-bit ports from the perspective of PCP servers? &nbsp;NAT =
traversal for SCTP is not done by remapping the ports, and it doesn't =
make sense to ask for a NAT to redirect SCTP public port A to SCTP =
private port B where A !=3D B due to the need to recalculate the CRC32 =
checksum it uses.</div><div><br></div><div>Perhaps a word about SCTP and =
its "unconventional" use of port numbers would be in =
order.</div><div><br><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Gill Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
12px; "><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><br =
class=3D"Apple-interchange-newline">--</span></span></div><div =
style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">james woodyatt &lt;<a =
href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&gt;</span></span></span></=
div><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">member of technical staff, core os =
networking</span></span></span></div><br =
class=3D"Apple-interchange-newline" style=3D"font-size: 11px; =
font-family: Geneva; "></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Boundary_(ID_I1Aneu4bUp9xo4R2CU5BfQ)--

From Francis.Dupont@fdupont.fr  Sat Oct 15 04:17:08 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 2C7F521F8ABE for <pcp@ietfa.amsl.com>; Sat, 15 Oct 2011 04:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qRX4q+tTsju8 for <pcp@ietfa.amsl.com>; Sat, 15 Oct 2011 04:17:07 -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 501C421F8AB9 for <pcp@ietf.org>; Sat, 15 Oct 2011 04:17:04 -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 p9FBGvwq029994; Sat, 15 Oct 2011 13:16:57 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110151116.p9FBGvwq029994@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Fri, 14 Oct 2011 10:00:37 PDT. <055701cc8a92$cc032c00$64098400$@com> 
Date: Sat, 15 Oct 2011 13:16:57 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] renewal time
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, 15 Oct 2011 11:17:08 -0000

 In your previous mail you wrote:

   on both the PCP server (which nobody has complained about) and on the PCP

=> in fact I complained not about the principle but about the
proposed value which is not compatible with UPnP IGD v2.

   client (which you, Francis, and Keith all seem to object to).
   
=> in fact I don't object yet, I am still trying to understand.
But about the principle I don't believe the client side should
overwrite what the server returns about the expiry (but as the
renewal responsability is a client one if the proposal is about
the renewal only it doesn't apply).
   
Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 15 04:30:20 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 BF59121F8B4F for <pcp@ietfa.amsl.com>; Sat, 15 Oct 2011 04:30:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTR2BQmLk23x for <pcp@ietfa.amsl.com>; Sat, 15 Oct 2011 04:30:20 -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 0FB9B21F8B3F for <pcp@ietf.org>; Sat, 15 Oct 2011 04:30:19 -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 p9FBUHJR030868; Sat, 15 Oct 2011 13:30:17 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110151130.p9FBUHJR030868@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Keith Moore <moore@network-heretics.com>
In-reply-to: Your message of Fri, 14 Oct 2011 15:48:29 EDT. <8E5B455D-002D-47C2-A1D5-D1ACE8AFD1F3@network-heretics.com> 
Date: Sat, 15 Oct 2011 13:30:17 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] learning the external address
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, 15 Oct 2011 11:30:20 -0000

 In your previous mail you wrote:

   Ideally there would be a mechanism by which a NAT or firewall or
   whatever could let its clients know when there's been a disruptive
   event.    Maybe by sending a message (or three) to a multicast group.
   
=> this doesn't scale... I prefer to put stable storage on
the NAT or firewall (BTW with the legal constraint in most countries
about logging a CGN must have stable storage so in fact it should not
be a real issue).

Regards

Francis.Dupont@fdupont.fr

PS: frivolous renumbering by the CGN has a critical impact on security:
Internet clients can no longer assume they talk to the right server,
and don't expect users which have to suffer from a CGN may use enough
crypto to be protected against this... my concern is the perception
is not only the IETF doesn't help these users but despises their interest.

From Francis.Dupont@fdupont.fr  Sat Oct 15 04:35:33 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 CDA6A21F8B3F for <pcp@ietfa.amsl.com>; Sat, 15 Oct 2011 04:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.497
X-Spam-Level: 
X-Spam-Status: No, score=-2.497 tagged_above=-999 required=5 tests=[AWL=0.102,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sCrx+0c2q2Yh for <pcp@ietfa.amsl.com>; Sat, 15 Oct 2011 04:35:33 -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 2080421F8B30 for <pcp@ietf.org>; Sat, 15 Oct 2011 04:35:32 -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 p9FBZT5X031180; Sat, 15 Oct 2011 13:35:29 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110151135.p9FBZT5X031180@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Fri, 14 Oct 2011 13:16:21 PDT. <066801cc8aae$23ae7480$6b0b5d80$@com> 
Date: Sat, 15 Oct 2011 13:35:29 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org, 'Keith Moore' <moore@network-heretics.com>
Subject: Re: [pcp] learning the external address
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, 15 Oct 2011 11:35:33 -0000

 In your previous mail you wrote:

   draft-cheshire-pcp-recovery.

=> clearly a port of the similar mechanism in NAT-PMP,
and limited to the same environment (NAT embedded in the
home gateway, not a CGN).
   
   We need a way for PCP to work correctly without a multicast
   message from the PCP server to the clients.
   
=> I already propose one: put stable storage on the CGN so
it no longer loses its state and there is no need for
a recovery...

Regards

Francis.Dupont@fdupont.fr
   
PS: BTW according to one of your arguments if we add the
external address to recovery messages it should be
associated with a lifetime.

From Francis.Dupont@fdupont.fr  Sat Oct 15 04:48:39 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 8444721F8B1E for <pcp@ietfa.amsl.com>; Sat, 15 Oct 2011 04:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0D+c9EK3vH80 for <pcp@ietfa.amsl.com>; Sat, 15 Oct 2011 04:48:39 -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 9059621F8AD2 for <pcp@ietf.org>; Sat, 15 Oct 2011 04:48:38 -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 p9FBljtN031911; Sat, 15 Oct 2011 13:47:47 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110151147.p9FBljtN031911@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: Your message of Fri, 14 Oct 2011 23:17:43 -0000. <C0E0A32284495243BDE0AC8A066631A80C19635B@szxeml526-mbx.china.huawei.com>
Date: Sat, 15 Oct 2011 13:47:45 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] section 8
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, 15 Oct 2011 11:48:39 -0000

 In your previous mail you wrote:

   Hi,
   In section 8, it reads:
     "It is REQUIRED that the PCP-controlled device assign the same
      external IP address to PCP-created explicit dynamic mappings and to
      implicit dynamic mappings for a given Internal Host.  In the absence
      of a PCP option indicating otherwise, it is REQUIRED that PCP-created
      explicit dynamic mappings be assigned the same external IP address."
   It is not consistent with what we have discussed in the mailing list below. And i
  t is a bit ambiguous in reading.
   
   How about changing the second sentence from on of the 4 candidates as below?
   
   Alternative 1:
   PCP client should request same external IP address for an application if there is
   already any existing explicit mapping for that application.
   
=> the section 8 rule is per subscriber+host so the alternative should be too.

   Alternative 2:
   PCP client should request the same external IP address if there are existing expl
  ict mappings, unless there is explicit reasons of not doing so, e.g. http://tools.
  ietf.org/html/draft-penno-pcp-zones-00
   
=> same issue

   Alternative 3:
   It is indicated by the PCP client that PCP-created explicit dynamic mappings be a
  ssigned the same external IP address, unless there are explicit reasons of not doi
  ng so, e.g. http://tools.ietf.org/html/draft-penno-pcp-zones-00"
   
=> same issue

   Alternative 4:
   It is indicated by the PCP client that PCP-created explicit dynamic mappings be a
  ssigned the same external IP address, unless a PCP option indicates different exte
  rnal IP address
   
=> same issue   
   
I can't see the problem, the text says all mappings (even there is nothing
about static mappings, is there a problem to add them?) get the same external
IP address if there is no option indicating otherwise.
BTW IWFs work far better if the affinity is per subscriber.

IMHO the best should be to make the affinity larger, i.e., per subscriber
and for all mappings, but at a lower level, i.e., with a RECOMMEND/SHOULD
in place of the current REQUIRE/MUST.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 15 04:52:34 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 8B68021F8A66 for <pcp@ietfa.amsl.com>; Sat, 15 Oct 2011 04:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R6BL6uW9vd9K for <pcp@ietfa.amsl.com>; Sat, 15 Oct 2011 04:52:34 -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 D3C8121F84A3 for <pcp@ietf.org>; Sat, 15 Oct 2011 04:52:33 -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 p9FBqOOq032226; Sat, 15 Oct 2011 13:52:24 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110151152.p9FBqOOq032226@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: james woodyatt <jhw@apple.com>
In-reply-to: Your message of Fri, 14 Oct 2011 17:59:11 PDT. <149DAB5A-3E9F-47C4-B710-5B00BDE544F8@apple.com> 
Date: Sat, 15 Oct 2011 13:52:24 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] remapping sctp ports
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, 15 Oct 2011 11:52:34 -0000

 In your previous mail you wrote:

   Question: is SCTP a transport protocol...

=> is there today a NAPT with SCTP support?

Regards

Francis.Dupont@fdupont.fr

PS: don't believe I don't like SCTP but IMHO you more likely
get IPv6 than SCTP...
PPS: the PCP text (but not the question) still applies to firewalls.

From jhw@apple.com  Mon Oct 17 10:47:07 2011
Return-Path: <jhw@apple.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 EF62121F8C04 for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 10:47:07 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Y+TmZn5wI9D for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 10:47:07 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 94C9021F8BB2 for <pcp@ietf.org>; Mon, 17 Oct 2011 10:47:07 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LT8000HX0QFXD81@mail-out.apple.com> for pcp@ietf.org; Mon, 17 Oct 2011 10:47:07 -0700 (PDT)
X-AuditID: 11807134-b7cc1ae0000078f0-db-4e9c6a1be9b0
Received: from kallisti.apple.com (kallisti.apple.com [17.193.13.64]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay14.apple.com (Apple SCV relay) with SMTP id D8.FF.30960.B1A6C9E4; Mon, 17 Oct 2011 10:47:07 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <201110151152.p9FBqOOq032226@givry.fdupont.fr>
Date: Mon, 17 Oct 2011 10:47:07 -0700
Message-id: <73EA3409-8ACD-4A91-855A-C819E9FAFED8@apple.com>
References: <201110151152.p9FBqOOq032226@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMLMWRmVeSWpSXmKPExsUieJDXQVc6a46fwZHJvBaPpu1ktZh87Der A5PHu6l/WD2WLPnJFMAUxWWTkpqTWZZapG+XwJUx/U9qwTvGignv21kaGDcxdjFyckgImEhM O9PJDGGLSVy4t56ti5GLQ0hgNpPEgwPf2UESwgLqEtfnLmcCsXkFjCXW3HrHAmIzC2hJ3Pj3 EizOJqAi8e3yXTCbU8Ba4silL2A1LAKqEn2L2tgh6sUk/s67zARhy0tsfzuHGWKmjcTvlz1g cSEBK4mv5w+CxUUE9CTeXT3IDnGcvETL1ztsExj5ZyE5YxaSM2YhGbuAkXkVo2BRak5ipaGJ XmJBQU6qXnJ+7iZGUNA1FJrsYDz4k/8QowAHoxIPr2TaHD8h1sSy4srcQ4wSHMxKIry68UAh 3pTEyqrUovz4otKc1OJDjNIcLErivP2pQCmB9MSS1OzU1ILUIpgsEwenVANjdMzJ3bYCmq5f DCf8NZ3WrWMsZnf/66n1osqHL66YLPm98tW5z28PH/98qS3bNDbnr6HX0eU3D80q0b2S+I5H f6v+/Zlzlxw9XdfRubmeQe9d1b4sqY6igANLbidPyTvlo/rwwP55t81WmzlYVwuXPjqtM7XJ TPK2wozNR/UPTOPi/s7pe7DonBJLcUaioRZzUXEiACGMDwQ2AgAA
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] remapping sctp ports
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, 17 Oct 2011 17:47:08 -0000

On Oct 15, 2011, at 04:52 , Francis Dupont wrote:
> 
> => is there today a NAPT with SCTP support?

Is there a NAPT today with PCP support?


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From dwing@cisco.com  Mon Oct 17 15:42:00 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 AD8E521F88A0 for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 15:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.067
X-Spam-Level: 
X-Spam-Status: No, score=-105.067 tagged_above=-999 required=5 tests=[AWL=1.532, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2YmBxkB1ebI for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 15:41:59 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id D3F7D21F8593 for <pcp@ietf.org>; Mon, 17 Oct 2011 15:41:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3893; q=dns/txt; s=iport; t=1318891319; x=1320100919; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=/a6Au5mbUEMx2FMd/LBYPyvFb60uUTRG5L8y6Rk5H4s=; b=jyptFy9VNtqO/f8q10Rz8rwJmr9HjHvIX855WX8IEYubcJcJYHpF83al XOeTqVy4o+/UtPaWJ9RBfDNzdpEyGGg5hHUEUufGh7af0WaOJL8to3cNC 3OzBJ4j6tvZkq8P0xRSLeaQqjqXbdIu+dNwK8Y4SUySktAWr11XLYMdlb E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEAAOKtnE6rRDoI/2dsb2JhbABDmTKBbI05gQWBbgEBAQIBAQgKARcQNAsFBwEDAgkPAQEEAQEBJwcZIwoJCAEBBBMJAhAHh10ImDYBnm+ICASIApRbiRE
X-IronPort-AV: E=Sophos;i="4.69,362,1315180800";  d="scan'208";a="8430124"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 17 Oct 2011 22:41:59 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p9HMfxYC003978; Mon, 17 Oct 2011 22:41:59 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Fri, 14 Oct 2011 08:59:09 PDT. <051b01cc8a8a$35a75360$a0f5fa20$@com> <201110141613.p9EGDwdA060721@givry.fdupont.fr>
In-Reply-To: <201110141613.p9EGDwdA060721@givry.fdupont.fr>
Date: Mon, 17 Oct 2011 15:41:59 -0700
Message-ID: <023601cc8d1d$fb425c60$f1c71520$@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: AcyKjEjmSy46gqodSXWKTq2QzXlkPACkKT/w
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] existing mapping and PREFER_FAILURE
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, 17 Oct 2011 22:42:00 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Friday, October 14, 2011 9:14 AM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] existing mapping and PREFER_FAILURE
> 
> 
>  In your previous mail you wrote:
> 
>    > => I am for 'MUST upgrade or return an error'
> 
>    But that is exactly what causes a problem.
> 
> => this is why I propose "promote to or replace by" which
> puts the eventual damage on the already existing implicit
> dynamic mapping which should have never existed.

The implicit mapping on the NAT might have been created by
a completely unrelated application running on the same host;
we can't encourage harming it.  It was completely legitimate
when the application created that mapping.

>    > => I understand your reasons but here it is the PCP WG so we have
> to
>    > live with any NAT implementations.
> 
>    The NAT has to handle MAP in a way that works well.
> 
> => but PCP explicitely can't change NAT behavior.

We have been through this since Stuart's presentation at
IETF80, http://www.ietf.org/proceedings/80/slides/pcp-8.pdf,
slides 9-15, when this was called IMPLICIT_MAPPING_EXISTS.


>    Here is the example problem, which has been discussed on the
>    mailing list before, and discussed in f2f meetings before -- but
>    for everyone's benefit:
> 
>    Let's say an application starts listening on port N (e.g.,
>    TCP/22, TCP/80, TCP/8080, UDP/5061, etc.).  Then, through
>    no fault of that application, the OS's stack decides to use
>    that same port for an outgoing connection to the Internet
>    (from a completely unrelated application).  The application
>    listening on port N also has some incoming connections to
>    that port N, from hosts within the home network (e.g., the
>    music streaming devices).  Now, I click the "allow
>    connections from the Internet" button on my application,
>    which causes it to make a PCP MAP request.  If that gets
>    denied, that means my application needs to start listening
>    on another port ("M"), try again, repeat.  That's a significant
>    burden for the application, and now it is listening on two
>    ports (N, where it has already accepted connections from
>    hosts on the same network, and the eventual M port which
>    is for connections from the Internet).
> 
> => I know this but in fact it is not a good example: if the
> application can't get the exclusive use of the port in the OS
> it will be in trouble anyway.

Then use Simon's example at
http://www.ietf.org/mail-archive/web/pcp/current/msg00474.html

>    Can this problem be entirely avoided by the application listening
>    on the port using INADDR_ANY or SO_EXCLUSIVEADDRUSE or something
> else?
>    It has been my understanding that it's impossible for an application
>    to prevent the OS from using its listening socket for the OS's
> outgoing
>    connections, from an explanation over a year ago from Simon.
> 
> => it is OS dependent, I can answer (yes) for BSDs, I have never been
> convinced
> by SO_REUSEADDR implementation on Linux, and SO_EXCLUSIVEADDRUSE is
> supposed to be the (other) solution on recent versions of Windows...
> 
>    > Now we can perhaps reach an agreement if we define the word
> upgrade,
>    > in my message I used the term "promote" because it suggests most
> of the
>    > characterictics are kept, for instance the external address and
> port.
>    > If we change it by "promote to or replace by" we cover all cases
> as
>    > the explicit dynamic mapping has only to use the same internal
> address
>    > and port (and to be the unique mapping to use them).
> 
> => can you answer to this proposal?

What are the side effects of the proposal?

-d


> Regards
> 
> Francis.Dupont@fdupont.fr


From dwing@cisco.com  Mon Oct 17 16:24:15 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 3962411E8096 for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 16:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.152
X-Spam-Level: 
X-Spam-Status: No, score=-105.152 tagged_above=-999 required=5 tests=[AWL=1.447, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BxhDH+UR7NYb for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 16:24:14 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id BF0FA11E8095 for <pcp@ietf.org>; Mon, 17 Oct 2011 16:24:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1453; q=dns/txt; s=iport; t=1318893855; x=1320103455; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=bRRAGxGLIamo7uQrPB7yKap8P4XllZj+wjt+vxPfxF8=; b=ZWilqbBKyzoIXXPD6F8XhvZMuh7u7PtB6a0mC5iUqgHubt1StExxYHNg pDep2XvpzEfo3NiZELeriHgTYJ0Bf9pfHQiHic8QJzc2N8nDeIt1/U0xI KLdlMP5PxV4pBtHJQlKE9b/aLOvfLIHeL7CvGjddFGO88wbtuU/8m3FnM c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEAALu4nE6rRDoI/2dsb2JhbABDmTKBbI05gQWBbgEBAQQICgEXEEsBAwIJDwIEAQEoBxkjCgkIAQEEARILF59+AZ55iAgEiAKdbA
X-IronPort-AV: E=Sophos;i="4.69,362,1315180800";  d="scan'208";a="8437877"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 17 Oct 2011 23:24:14 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p9HNOEd3026052; Mon, 17 Oct 2011 23:24:14 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'james woodyatt'" <jhw@apple.com>, "'PCP'" <pcp@ietf.org>
References: <149DAB5A-3E9F-47C4-B710-5B00BDE544F8@apple.com>
In-Reply-To: <149DAB5A-3E9F-47C4-B710-5B00BDE544F8@apple.com>
Date: Mon, 17 Oct 2011 16:24:14 -0700
Message-ID: <02be01cc8d23$e218ce30$a64a6a90$@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: AcyK1daa9sY891P3Sx2p0w0dATaxuQCTa70w
Content-Language: en-us
Subject: Re: [pcp] remapping sctp ports
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, 17 Oct 2011 23:24:15 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> james woodyatt
> Sent: Friday, October 14, 2011 5:59 PM
> To: PCP
> Subject: [pcp] remapping sctp ports
> 
> everyone--
> 
> Question: is SCTP a transport protocol that uses 16-bit ports from the
> perspective of PCP servers?  NAT traversal for SCTP is not done by
> remapping the ports, and it doesn't make sense to ask for a NAT to
> redirect SCTP public port A to SCTP private port B where A != B due to
> the need to recalculate the CRC32 checksum it uses.
> 
> Perhaps a word about SCTP and its "unconventional" use of port numbers
> would be in order.

Added to the Implementation Considerations section, which I have now
broken into normative and non-normative sections (this new text is
normative):

   12.3.3.  SCTP

   Although SCTP has port numbers like TCP and UDP, SCTP works
   differently when behind an address-sharing NAT, in that SCTP port
   numbers are not changed [I-D.ietf-behave-sctpnat].  Because of this,
   a PCP MAP or PEER request for an SCTP mapping MUST provide the same
   Internal Port and Requested External Port, or else the
   MALFORMED_REQUEST error is returned.  SCTP MAP or PEER requests for
   an SCTP mapping always imply PREFER_FAILURE semantics.  If the
   requested external port cannot be provided, the error
   CANNOT_PROVIDE_EXTERNAL_PORT is returned.

Feedback?

-d



From dwing@cisco.com  Mon Oct 17 16:32:55 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 9CDCA21F8A64 for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 16:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.191
X-Spam-Level: 
X-Spam-Status: No, score=-105.191 tagged_above=-999 required=5 tests=[AWL=1.408, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q-ziwIWiyeUL for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 16:32:55 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 18EBA21F8A58 for <pcp@ietf.org>; Mon, 17 Oct 2011 16:32:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2196; q=dns/txt; s=iport; t=1318894375; x=1320103975; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=D/aXTAf2FjHujrcXG54TXXpiCbfTrlDzwBcbztDMpY8=; b=JrvHuObVfnGiwz8ovZJ5eP+S3NqudrJUZZJLRn0yhzEz6SXRQDKlYAba er3eYWJYA+EH+EMg6UTJKeErGSDo6n6jZsI2JS7cbaVFLQR6nS+0QclqH OIbIqKc04JYiwCD+Es4vvjyRTarEvXkLRUzgzWq2fIGbBBO6t+KeoZbFA U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEAAEK6nE6rRDoG/2dsb2JhbABDmTKBbI05gQWBbgEBAQMBAQEBBQoBFxA0EAcBAwIJDwIEAQEoBxkOFQoJCAIEARILF4ddCJgWAZ56iAgEiAKdbA
X-IronPort-AV: E=Sophos;i="4.69,362,1315180800";  d="scan'208";a="8456500"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 17 Oct 2011 23:32:54 +0000
Received: from dwingWS ([10.32.240.197]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9HNWsjL021584; Mon, 17 Oct 2011 23:32:54 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Tina TSOU'" <Tina.Tsou.Zouting@huawei.com>, <pcp@ietf.org>
References: <A6A061BEE5DDC94A9692D9D81AF776DF0AAEC289@szxeml527-mbs.china.huawei.com>	<774B240D54DAB844B37EE80C2DD8E8BCB7E9DA@szxeml522-mbs.china.huawei.com>	<A6A061BEE5DDC94A9692D9D81AF776DF0AAEC2F8@szxeml527-mbs.china.huawei.com>	<A6A061BEE5DDC94A9692D9D81AF776DF0AAED40B@szxeml527-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C19635B@szxeml526-mbx.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80C19635B@szxeml526-mbx.china.huawei.com>
Date: Mon, 17 Oct 2011 16:32:54 -0700
Message-ID: <02d801cc8d25$183c8eb0$48b5ac10$@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: AQHMisd6AqbKitDQAEWxdFLEoPIx55WBNDag
Content-Language: en-us
Subject: Re: [pcp] section 8
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, 17 Oct 2011 23:32:55 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Tina TSOU
> Sent: Friday, October 14, 2011 4:18 PM
> To: pcp@ietf.org
> Subject: [pcp] section 8
> 
> Hi,
> In section 8, it reads:
>   "It is REQUIRED that the PCP-controlled device assign the same
>    external IP address to PCP-created explicit dynamic mappings and to
>    implicit dynamic mappings for a given Internal Host.  In the absence
>    of a PCP option indicating otherwise, it is REQUIRED that PCP-
> created
>    explicit dynamic mappings be assigned the same external IP address."
> It is not consistent with what we have discussed in the mailing list
> below. And it is a bit ambiguous in reading.

The text allows draft-penno-pcp-zones, provided that draft-penno-pcp-zones
defines and a PCP option (which it does) and the PCP request uses 
that option (which is up to the PCP client, of course).

I don't see the ambiguity in the existing text.  What is the problem?

-d


> How about changing the second sentence from on of the 4 candidates as
> below?
>
> Alternative 1:
> PCP client should request same external IP address for an application
> if there is already any existing explicit mapping for that application.
> 
> Alternative 2:
> PCP client should request the same external IP address if there are
> existing explict mappings, unless there is explicit reasons of not
> doing so, e.g. http://tools.ietf.org/html/draft-penno-pcp-zones-00
> 
> Alternative 3:
> It is indicated by the PCP client that PCP-created explicit dynamic
> mappings be assigned the same external IP address, unless there are
> explicit reasons of not doing so, e.g.
> http://tools.ietf.org/html/draft-penno-pcp-zones-00"
> 
> Alternative 4:
> It is indicated by the PCP client that PCP-created explicit dynamic
> mappings be assigned the same external IP address, unless a PCP option
> indicates different external IP address
> 
> 
> 
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From jhw@apple.com  Mon Oct 17 17:34:05 2011
Return-Path: <jhw@apple.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 24A9611E80A2 for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 17:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kSqNjW1C85xO for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 17:34:04 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id AE47011E8095 for <pcp@ietf.org>; Mon, 17 Oct 2011 17:34:04 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_6Zoz21KO+piPsfZdvvCmrA)"
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LT8000LLI57XDI2@mail-out.apple.com> for pcp@ietf.org; Mon, 17 Oct 2011 16:48:52 -0700 (PDT)
X-AuditID: 1180711d-b7b7dae000007623-cb-4e9cbedeb9a4
Received: from ba0301a-dhcp89.apple.com (ba0301a-dhcp89.apple.com [17.193.14.217]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 58.28.30243.EDEBC9E4; Mon, 17 Oct 2011 16:48:47 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <02be01cc8d23$e218ce30$a64a6a90$@com>
Date: Mon, 17 Oct 2011 16:48:46 -0700
Message-id: <2A7EF313-110A-4132-AE3A-442CD20F6CE2@apple.com>
References: <149DAB5A-3E9F-47C4-B710-5B00BDE544F8@apple.com> <02be01cc8d23$e218ce30$a64a6a90$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrNLMWRmVeSWpSXmKPExsUieJDvpu7jfXP8DH6sVLC4eO0hk8XkY79Z HZg8pvzeyOqxZMlPpgCmKC6blNSczLLUIn27BK6MCzd2MRZc0KpYsXAWUwNjm2oXIyeHhICJ xN+TT9kgbDGJC/fWA9lcHEICK5gk9my8yg6SEBZQl7g+dzkTiM0rYCyx5tY7FhCbWSBBon/7 DVYQm01AReLb5btgNZwCRhKnb29kBrFZBFQlLn6+wAxRLyGxsOEfO8QcG4n2ZXfAeoUEkiQu dLSB1YgIyEncnT+BGeIgeYmWr3fYJjDyzUKyehaS1RC2tsSyha+ZZzFyANk6EpMXMqIKQ9gf zx9hWsDItopRsCg1J7HS0FgvsaAgJ1UvOT93EyMoSBsKZXcw7v/Jf4hRgINRiYdXMm2OnxBr YllxZe4hRgkOZiUR3oe7gEK8KYmVValF+fFFpTmpxYcYpTlYlMR5e1KBUgLpiSWp2ampBalF MFkmDk6pBsatemvOLdorJZOi8qkzwf/qQWXFpfEuWs90xP9f4wnOjpL5pV07m7HEU8rbNfn/ /4+nL2068ye9uP3fu6fflm7o5UpZHCWw1JBBMZ4r/k+Boi6/Y2LknSCN8n773YrzfnmsWDA/ YP/NSh1D7qhdP39M/3d7ok3mooM8j8tmHr94dVHFlVMevtJKLMUZiYZazEXFiQAcbSqBTgIA	AA==
Cc: 'PCP' <pcp@ietf.org>
Subject: Re: [pcp] remapping sctp ports
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, 18 Oct 2011 00:34:05 -0000

--Boundary_(ID_6Zoz21KO+piPsfZdvvCmrA)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

On Oct 17, 2011, at 4:24 PM, Dan Wing wrote:
> 
>   If the requested external port cannot be provided, the error CANNOT_PROVIDE_EXTERNAL_PORT is returned.


I'm not sure whether or how much to say about implicit mappings the semantic difference between SCTP implicit dynamic mapping states, which are a 3-tuple of A) the Local [External/Internal] address, B) the Remote Peer Address and C) the SCTP verification tag, and the composition of explicit dynamic and static mappings for SCTP, which use the local and remote peer port numbers, and which do not [and cannot] use the verification tag.

Perhaps, "If the requested external port cannot be provided in an explicit dynamic SCTP mapping, then the error CANNOT_PROVIDE_EXTERNAL_PORT is return. Because implicit dynamic SCTP mappings use the verification tag of the association instead of the local and remote peer port numbers, explicit dynamic SCTP mappings need only be established by passive listeners expecting to receive new associations at the external port."


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




--Boundary_(ID_6Zoz21KO+piPsfZdvvCmrA)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Oct 17, 2011, at 4:24 PM, Dan Wing =
wrote:</div><blockquote type=3D"cite"><br =
class=3D"Apple-interchange-newline"></blockquote><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">&nbsp; If =
the&nbsp;requested external port cannot be provided, the =
error&nbsp;CANNOT_PROVIDE_EXTERNAL_PORT is =
returned.</span></blockquote></div><div><br></div><div>I'm not sure =
whether or how much to say about implicit mappings the semantic =
difference between SCTP implicit dynamic mapping states, which are a =
3-tuple of A) the Local [External/Internal] address, B) the Remote Peer =
Address and C) the SCTP verification tag, and the composition of =
explicit dynamic and static mappings for SCTP, which use the local and =
remote peer port numbers, and which do not [and cannot] use the =
verification tag.</div><div><br></div><div>Perhaps, "If the requested =
external port cannot be provided in an explicit dynamic SCTP mapping, =
then the error CANNOT_PROVIDE_EXTERNAL_PORT is return. Because implicit =
dynamic SCTP mappings use the verification tag of the association =
instead of the local and remote peer port numbers, explicit dynamic SCTP =
mappings need only be established by passive listeners expecting to =
receive new associations at the external port."</div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Gill Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
12px; "><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><br =
class=3D"Apple-interchange-newline">--</span></span></div><div =
style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">james woodyatt &lt;<a =
href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&gt;</span></span></span></=
div><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">member of technical staff, core os =
networking</span></span></span></div><br =
class=3D"Apple-interchange-newline" style=3D"font-size: 11px; =
font-family: Geneva; "></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Boundary_(ID_6Zoz21KO+piPsfZdvvCmrA)--

From adurand@juniper.net  Mon Oct 17 17:44:05 2011
Return-Path: <adurand@juniper.net>
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 7721011E80AE for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 17:44:05 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IOrU5shBTBOe for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 17:44:05 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id B7C4111E8095 for <pcp@ietf.org>; Mon, 17 Oct 2011 17:44:04 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP;  Mon, 17 Oct 2011 17:44:04 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Mon, 17 Oct 2011 17:41:09 -0700
From: Alain Durand <adurand@juniper.net>
To: Dan Wing <dwing@cisco.com>
Date: Mon, 17 Oct 2011 17:41:06 -0700
Thread-Topic: [pcp] remapping sctp ports
Thread-Index: AcyNLqCX8wBrS7UBR6+U3yQ6OB3eVQ==
Message-ID: <247A1883-7B62-42E0-8431-F00A3334F545@juniper.net>
References: <149DAB5A-3E9F-47C4-B710-5B00BDE544F8@apple.com> <02be01cc8d23$e218ce30$a64a6a90$@com>
In-Reply-To: <02be01cc8d23$e218ce30$a64a6a90$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] remapping sctp ports
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, 18 Oct 2011 00:44:05 -0000

How much user generated sctp traffic is there on the public Internet?
Last I checked, it was zero point zero... Maybe things have changed since I=
 checked, in that case I'd like to see actual numbers.

So, please, let's not over-engineer this, we need to ship the base PCP docu=
ment. We can always revisit this later.

Alain.

Sent from my iPad

On Oct 17, 2011, at 7:24 PM, "Dan Wing" <dwing@cisco.com> wrote:

>> -----Original Message-----
>> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
>> james woodyatt
>> Sent: Friday, October 14, 2011 5:59 PM
>> To: PCP
>> Subject: [pcp] remapping sctp ports
>>=20
>> everyone--
>>=20
>> Question: is SCTP a transport protocol that uses 16-bit ports from the
>> perspective of PCP servers?  NAT traversal for SCTP is not done by
>> remapping the ports, and it doesn't make sense to ask for a NAT to
>> redirect SCTP public port A to SCTP private port B where A !=3D B due to
>> the need to recalculate the CRC32 checksum it uses.
>>=20
>> Perhaps a word about SCTP and its "unconventional" use of port numbers
>> would be in order.
>=20
> Added to the Implementation Considerations section, which I have now
> broken into normative and non-normative sections (this new text is
> normative):
>=20
>   12.3.3.  SCTP
>=20
>   Although SCTP has port numbers like TCP and UDP, SCTP works
>   differently when behind an address-sharing NAT, in that SCTP port
>   numbers are not changed [I-D.ietf-behave-sctpnat].  Because of this,
>   a PCP MAP or PEER request for an SCTP mapping MUST provide the same
>   Internal Port and Requested External Port, or else the
>   MALFORMED_REQUEST error is returned.  SCTP MAP or PEER requests for
>   an SCTP mapping always imply PREFER_FAILURE semantics.  If the
>   requested external port cannot be provided, the error
>   CANNOT_PROVIDE_EXTERNAL_PORT is returned.
>=20
> Feedback?
>=20
> -d
>=20
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp

From jhw@apple.com  Mon Oct 17 18:02:10 2011
Return-Path: <jhw@apple.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 4F2EC21F8B08 for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 18:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.298
X-Spam-Level: 
X-Spam-Status: No, score=-106.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z+mfYS5qE34w for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 18:02:09 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1650F21F8AFD for <pcp@ietf.org>; Mon, 17 Oct 2011 18:01:58 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_bPOFmtfsKrRFdQ2Gllz7pg)"
Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LT800GG7LIPO1E2@mail-out.apple.com> for pcp@ietf.org; Mon, 17 Oct 2011 18:01:57 -0700 (PDT)
X-AuditID: 11807137-b7c56ae0000051ed-b6-4e9cd005a7c1
Received: from ba0301a-dhcp89.apple.com (ba0301a-dhcp89.apple.com [17.193.14.217]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay16.apple.com (Apple SCV relay) with SMTP id 85.A4.20973.500DC9E4; Mon, 17 Oct 2011 18:01:57 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <247A1883-7B62-42E0-8431-F00A3334F545@juniper.net>
Date: Mon, 17 Oct 2011 18:01:57 -0700
Message-id: <6B24022E-3648-4276-9124-1E4F123DA9F8@apple.com>
References: <149DAB5A-3E9F-47C4-B710-5B00BDE544F8@apple.com> <02be01cc8d23$e218ce30$a64a6a90$@com> <247A1883-7B62-42E0-8431-F00A3334F545@juniper.net>
To: Alain Durand <adurand@juniper.net>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsUieJDvpi7rhTl+Bsvu6lrcfj6J0eLitYdM FpOP/WZ1YPaY8nsjq8eSJT+ZPK43XWUPYI7isklJzcksSy3St0vgyph+Zi5bwQ7Vim9P/jA2 MB5Q6GLk5JAQMJG4vvQ+M4QtJnHh3no2EFtIYAWTxP6LXiC2sIC6xPW5y5lAbF4BY4k1t96x gNjMAgkSnetaGUFsNgEViW+X74LVcArYS6xd0wtWwyKgKjH/0EZGiHoTidaH11gg5thIHPy+ BWgvF9CuqYwSyzbOBWsWEVCTaLpyghXiIHmJlq932CYw8s1CsnsWkt0QtrbEsoWvmWcxcgDZ OhKTF6IJQ9gfzx9hWsDItopRsCg1J7HS0EwvsaAgJ1UvOT93EyMocBsKzXcwbv8rd4hRgINR iYdXMm2OnxBrYllxZe4hRgkOZiUR3oe7gEK8KYmVValF+fFFpTmpxYcYpTlYlMR5J6QCpQTS E0tSs1NTC1KLYLJMHJxSDYyTY1IOJBeu0/Ws1dsZ3bXVrXOhyaGDT1+prVS7XGCz0Fog9chj m3PHrnAdWv9jju7GtR+Srp3QfX7WsEVw16b5l2r6G+bteffGQD1v5z0HNbNosxb3UruFLSuf nTKTm7TFsdDmZe7us2EKIT1lzuG+6nUqnkYhteeSJ8V6MK7f3uI0xcqz87wSS3FGoqEWc1Fx IgCbrIRBWAIAAA==
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] remapping sctp ports
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, 18 Oct 2011 01:02:10 -0000

--Boundary_(ID_bPOFmtfsKrRFdQ2Gllz7pg)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

On Oct 17, 2011, at 5:41 PM, Alain Durand wrote:
> 
> So, please, let's not over-engineer this, we need to ship the base PCP document. We can always revisit this later.

I sympathize with your concerns, but none of this would have been an issue if A) the PCP working group had not insisted on making the protocol a candidate for meeting REC-48 of RFC 6092, or B) the various authors of external standards based on RFC 6204 had not insisted on adding support for PCP as a requirement in the revised draft now underway in V6OPS.

You guys are about to spec something that will be in every IPv6 CPE router on the Internet soon.  If you get it wrong, you will break the Internet.  Again.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




--Boundary_(ID_bPOFmtfsKrRFdQ2Gllz7pg)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Oct 17, 2011, at 5:41 PM, Alain Durand =
wrote:</div><blockquote type=3D"cite"><br =
class=3D"Apple-interchange-newline"></blockquote><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">So, please, =
let's not over-engineer this, we need to ship the base PCP document. We =
can always revisit this later.<br></span></blockquote></div><br><div>I =
sympathize with your concerns, but none of this would have been an issue =
if A) the PCP working group had not insisted on making the protocol a =
candidate for meeting REC-48 of RFC 6092, or B) the various authors of =
external standards based on RFC 6204 had not insisted on adding support =
for PCP as a requirement in the revised draft now underway in =
V6OPS.</div><div><br class=3D"webkit-block-placeholder"></div><div>You =
guys are about to spec something that will be in every IPv6 CPE router =
on the Internet soon. &nbsp;If you get it wrong, you will break the =
Internet. &nbsp;Again.</div><div><br></div><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Gill Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
12px; "><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><br =
class=3D"Apple-interchange-newline">--</span></span></div><div =
style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">james woodyatt &lt;<a =
href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&gt;</span></span></span></=
div><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">member of technical staff, core os =
networking</span></span></span></div><br =
class=3D"Apple-interchange-newline" style=3D"font-size: 11px; =
font-family: Geneva; "></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Boundary_(ID_bPOFmtfsKrRFdQ2Gllz7pg)--

From moore@network-heretics.com  Mon Oct 17 19:14:48 2011
Return-Path: <moore@network-heretics.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 D388121F8B2F for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 19:14:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.973
X-Spam-Level: 
X-Spam-Status: No, score=-3.973 tagged_above=-999 required=5 tests=[AWL=-0.375, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehhCXvmim-TW for <pcp@ietfa.amsl.com>; Mon, 17 Oct 2011 19:14:48 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 42EE021F8ACE for <pcp@ietf.org>; Mon, 17 Oct 2011 19:14:48 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 3EB59211AB; Mon, 17 Oct 2011 22:14:47 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Mon, 17 Oct 2011 22:14:47 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=Ebj YWWt30pwGnz1dxwfdX878JQs=; b=qkebA6OLwV2cm+H3y0F+jzJhsx1F+F6cQiE B3TyzUybwgULqNtIUnIa5/Vmmqm553Rf1g4s227rd9V529LjyQsvfH64eHniQP+j ea4NhBkbwhgSkeqm2mW3zdNU+nowOiTOTimoFDjJ+plUzrKlL2bFbVIyDPNfSSVL Utt8ROdY=
X-Sasl-enc: hsp1qQRs21sfqAdSXzUP6AGZvFNMQbSxl/rzicSuWkUK 1318904086
Received: from [192.168.1.16] (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 2B38D48340A; Mon, 17 Oct 2011 22:14:46 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-15--853036701
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <247A1883-7B62-42E0-8431-F00A3334F545@juniper.net>
Date: Mon, 17 Oct 2011 22:14:23 -0400
Message-Id: <43C20238-ADB3-407A-AD10-8CDCB71C68AF@network-heretics.com>
References: <149DAB5A-3E9F-47C4-B710-5B00BDE544F8@apple.com> <02be01cc8d23$e218ce30$a64a6a90$@com> <247A1883-7B62-42E0-8431-F00A3334F545@juniper.net>
To: Alain Durand <adurand@juniper.net>
X-Mailer: Apple Mail (2.1084)
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] remapping sctp ports
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, 18 Oct 2011 02:14:48 -0000

--Apple-Mail-15--853036701
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Oct 17, 2011, at 8:41 PM, Alain Durand wrote:

> So, please, let's not over-engineer this, we need to ship the base PCP =
document. We can always revisit this later.

That's the mentality that people had about NATs in the late 1990s... =
which is a good chunk of why the Internet is so screwed up now.



--Apple-Mail-15--853036701
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Oct 17, 2011, at 8:41 PM, Alain Durand wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">So, please, =
let's not over-engineer this, we need to ship the base PCP document. We =
can always revisit this =
later.<br></span></blockquote></div><br><div>That's the mentality that =
people had about NATs in the late 1990s... which is a good chunk of why =
the Internet is so screwed up =
now.</div><div><br></div><div><br></div></body></html>=

--Apple-Mail-15--853036701--

From Francis.Dupont@fdupont.fr  Tue Oct 18 02:29:55 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 3E2E421F8C8F for <pcp@ietfa.amsl.com>; Tue, 18 Oct 2011 02:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.505
X-Spam-Level: 
X-Spam-Status: No, score=-2.505 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HOjQfQ3LGqcb for <pcp@ietfa.amsl.com>; Tue, 18 Oct 2011 02:29:54 -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 6EBBE21F8C58 for <pcp@ietf.org>; Tue, 18 Oct 2011 02:29:54 -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 p9I9Tpq6085090; Tue, 18 Oct 2011 11:29:51 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110180929.p9I9Tpq6085090@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Mon, 17 Oct 2011 15:41:59 PDT. <023601cc8d1d$fb425c60$f1c71520$@com> 
Date: Tue, 18 Oct 2011 11:29:50 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] existing mapping and PREFER_FAILURE
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, 18 Oct 2011 09:29:55 -0000

 In your previous mail you wrote:

   > => this is why I propose "promote to or replace by" which
   > puts the eventual damage on the already existing implicit
   > dynamic mapping which should have never existed.
   
   The implicit mapping on the NAT might have been created by
   a completely unrelated application running on the same host;
   we can't encourage harming it.  It was completely legitimate
   when the application created that mapping.
   
=> there are two cases:
 - the colliding application got the port by accident: it is not
  legitimate at all as the service is supposed to have exclusive
  use of the port
 - the colliding application is the service itself and the implicit
  mapping was created for instance during a race after NAT reboot.
  In this case not only it is not a problem to delete the implicit
  mapping but it should be deleted.
In conclusion the "replace by" seems better than to raise an error.

   > => but PCP explicitely can't change NAT behavior.
   
   We have been through this since Stuart's presentation at
   IETF80, http://www.ietf.org/proceedings/80/slides/pcp-8.pdf,
   slides 9-15, when this was called IMPLICIT_MAPPING_EXISTS.
   
=> two comments:
 - this presentation didn't propose a solution to collision
  on the internal address and port
 - the charter is still the same: NAT behavior is out of scope
  (and out of the action field of the IETF too :-)
   
   > => can you answer to this proposal?
   
   What are the side effects of the proposal?
   
=> the colliding implicit dynamic mapping is deleted and no
error is raised for collision reason.
   
Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Tue Oct 18 02:33:39 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 3E57521F8C95 for <pcp@ietfa.amsl.com>; Tue, 18 Oct 2011 02:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtqxMbuMZbbY for <pcp@ietfa.amsl.com>; Tue, 18 Oct 2011 02:33:38 -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 8207D21F8C8F for <pcp@ietf.org>; Tue, 18 Oct 2011 02:33:38 -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 p9I9XVZ7085368; Tue, 18 Oct 2011 11:33:31 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110180933.p9I9XVZ7085368@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Mon, 17 Oct 2011 16:24:14 PDT. <02be01cc8d23$e218ce30$a64a6a90$@com> 
Date: Tue, 18 Oct 2011 11:33:31 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: 'PCP' <pcp@ietf.org>
Subject: Re: [pcp] remapping sctp ports
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, 18 Oct 2011 09:33:39 -0000

 In your previous mail you wrote:

   > Perhaps a word about SCTP and its "unconventional" use of port numbers
   > would be in order.
   
   Added to the Implementation Considerations section, which I have now
   broken into normative and non-normative sections (this new text is
   normative):
   
      12.3.3.  SCTP
   
      Although SCTP has port numbers like TCP and UDP, SCTP works
      differently when behind an address-sharing NAT, in that SCTP port
      numbers are not changed [I-D.ietf-behave-sctpnat].  Because of this,
      a PCP MAP or PEER request for an SCTP mapping MUST provide the same
      Internal Port and Requested External Port, or else the
      MALFORMED_REQUEST error is returned.  SCTP MAP or PEER requests for
      an SCTP mapping always imply PREFER_FAILURE semantics.  If the
      requested external port cannot be provided, the error
      CANNOT_PROVIDE_EXTERNAL_PORT is returned.
   
   Feedback?
   
=> I am not convinced implicit PREFER_FAILURE is the right choice
but I have no experience of SCTP NATs too...

Regards

Francis.Dupont@fdupont.fr

From Tina.Tsou.Zouting@huawei.com  Tue Oct 18 06:23:56 2011
Return-Path: <Tina.Tsou.Zouting@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 8B75621F8B1C for <pcp@ietfa.amsl.com>; Tue, 18 Oct 2011 06:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.152
X-Spam-Level: 
X-Spam-Status: No, score=-3.152 tagged_above=-999 required=5 tests=[AWL=-0.756, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iuDB-+SBaVbM for <pcp@ietfa.amsl.com>; Tue, 18 Oct 2011 06:23:56 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 9A83F21F8B08 for <pcp@ietf.org>; Tue, 18 Oct 2011 06:23:55 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LT9003UVJVSOL@szxga03-in.huawei.com> for pcp@ietf.org; Tue, 18 Oct 2011 21:23:53 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LT9006S4JVSFI@szxga03-in.huawei.com> for pcp@ietf.org; Tue, 18 Oct 2011 21:23:52 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEN14071; Tue, 18 Oct 2011 21:23:52 +0800
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 18 Oct 2011 21:23:48 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.58]) by szxeml403-hub.china.huawei.com ([10.82.67.35]) with mapi id 14.01.0270.001; Tue, 18 Oct 2011 21:23:42 +0800
Date: Tue, 18 Oct 2011 13:23:41 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <A6A061BEE5DDC94A9692D9D81AF776DF0AAED8F6@szxeml527-mbs.china.huawei.com>
X-Originating-IP: [10.212.244.143]
To: "pcp@ietf.org" <pcp@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C1985E9@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, zh-CN
Thread-topic: [pcp] section 8
Thread-index: AQHMizBr13yvB88tzkaCmzhKkDKJiJV/zDkAgABdyQCAAfEzkA==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: "14 Oct 2011 23:17:43 -0000." <C0E0A32284495243BDE0AC8A066631A80C19635B@szxeml526-mbx.china.huawei.com> <201110151147.p9FBljtN031911@givry.fdupont.fr> <A6A061BEE5DDC94A9692D9D81AF776DF0AAED7C8@szxeml527-mbs.china.huawei.com> <A6A061BEE5DDC94A9692D9D81AF776DF0AAED8F6@szxeml527-mbs.china.huawei.com>
Subject: Re: [pcp] section 8
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, 18 Oct 2011 13:23:56 -0000

RnJhbmNpcywNClJlcGx5IGlubGluZToNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCreivP7IyzogcGNwLWJvdW5jZXNAaWV0Zi5vcmcgW3BjcC1ib3VuY2VzQGlldGYu
b3JnXSC0+rHtIEZyYW5jaXMgRHVwb250IFtGcmFuY2lzLkR1cG9udEBmZHVwb250LmZyXQ0Kt6LL
zcqxvOQ6IDIwMTHE6jEw1MIxNcjVIDE5OjQ3DQq1vTogVGluYSBUU09VDQpDYzogcGNwQGlldGYu
b3JnDQrW98ziOiBSZTogW3BjcF0gc2VjdGlvbiA4DQoNCiBJbiB5b3VyIHByZXZpb3VzIG1haWwg
eW91IHdyb3RlOg0KDQogICBIaSwNCiAgIEluIHNlY3Rpb24gOCwgaXQgcmVhZHM6DQogICAgICJJ
dCBpcyBSRVFVSVJFRCB0aGF0IHRoZSBQQ1AtY29udHJvbGxlZCBkZXZpY2UgYXNzaWduIHRoZSBz
YW1lDQogICAgICBleHRlcm5hbCBJUCBhZGRyZXNzIHRvIFBDUC1jcmVhdGVkIGV4cGxpY2l0IGR5
bmFtaWMgbWFwcGluZ3MgYW5kIHRvDQogICAgICBpbXBsaWNpdCBkeW5hbWljIG1hcHBpbmdzIGZv
ciBhIGdpdmVuIEludGVybmFsIEhvc3QuICBJbiB0aGUgYWJzZW5jZQ0KICAgICAgb2YgYSBQQ1Ag
b3B0aW9uIGluZGljYXRpbmcgb3RoZXJ3aXNlLCBpdCBpcyBSRVFVSVJFRCB0aGF0IFBDUC1jcmVh
dGVkDQogICAgICBleHBsaWNpdCBkeW5hbWljIG1hcHBpbmdzIGJlIGFzc2lnbmVkIHRoZSBzYW1l
IGV4dGVybmFsIElQIGFkZHJlc3MuIg0KICAgSXQgaXMgbm90IGNvbnNpc3RlbnQgd2l0aCB3aGF0
IHdlIGhhdmUgZGlzY3Vzc2VkIGluIHRoZSBtYWlsaW5nIGxpc3QgYmVsb3cuIEFuZCBpDQogIHQg
aXMgYSBiaXQgYW1iaWd1b3VzIGluIHJlYWRpbmcuDQoNCiAgIEhvdyBhYm91dCBjaGFuZ2luZyB0
aGUgc2Vjb25kIHNlbnRlbmNlIGZyb20gb24gb2YgdGhlIDQgY2FuZGlkYXRlcyBhcyBiZWxvdz8N
Cg0KICAgQWx0ZXJuYXRpdmUgMToNCiAgIFBDUCBjbGllbnQgc2hvdWxkIHJlcXVlc3Qgc2FtZSBl
eHRlcm5hbCBJUCBhZGRyZXNzIGZvciBhbiBhcHBsaWNhdGlvbiBpZiB0aGVyZSBpcw0KICAgYWxy
ZWFkeSBhbnkgZXhpc3RpbmcgZXhwbGljaXQgbWFwcGluZyBmb3IgdGhhdCBhcHBsaWNhdGlvbi4N
Cg0KPT4gdGhlIHNlY3Rpb24gOCBydWxlIGlzIHBlciBzdWJzY3JpYmVyK2hvc3Qgc28gdGhlIGFs
dGVybmF0aXZlIHNob3VsZCBiZSB0b28uDQpbVFRdIERvIHlvdSBtZWFuIHRoYXQgc2VjdGlvbiA4
IGhhcyBkZWZpbmVkIHRoZSBzYW1lIGV4dGVybmFsIElQIGFkZHJlc3MgcGVyIHN1YnNjcmliZXIr
aG9zdCwgYW5kIHdlIGRvbid0IG5lZWQgdG8gcHJvcG9zZSB0aGUgYWx0ZXJuYXRpdmUgdGV4dHM/
IA0KSWYgc28sIGNvdWxkIHlvdSBwbGVhc2UgcG9pbnQgb3V0IHRoZSB0ZXh0cyBmb3IgbWU/IFRo
YW5rcy4NCg0KICAgQWx0ZXJuYXRpdmUgMjoNCiAgIFBDUCBjbGllbnQgc2hvdWxkIHJlcXVlc3Qg
dGhlIHNhbWUgZXh0ZXJuYWwgSVAgYWRkcmVzcyBpZiB0aGVyZSBhcmUgZXhpc3RpbmcgZXhwbA0K
ICBpY3QgbWFwcGluZ3MsIHVubGVzcyB0aGVyZSBpcyBleHBsaWNpdCByZWFzb25zIG9mIG5vdCBk
b2luZyBzbywgZS5nLiBodHRwOi8vdG9vbHMuDQogIGlldGYub3JnL2h0bWwvZHJhZnQtcGVubm8t
cGNwLXpvbmVzLTAwDQoNCj0+IHNhbWUgaXNzdWUNCg0KICAgQWx0ZXJuYXRpdmUgMzoNCiAgIEl0
IGlzIGluZGljYXRlZCBieSB0aGUgUENQIGNsaWVudCB0aGF0IFBDUC1jcmVhdGVkIGV4cGxpY2l0
IGR5bmFtaWMgbWFwcGluZ3MgYmUgYQ0KICBzc2lnbmVkIHRoZSBzYW1lIGV4dGVybmFsIElQIGFk
ZHJlc3MsIHVubGVzcyB0aGVyZSBhcmUgZXhwbGljaXQgcmVhc29ucyBvZiBub3QgZG9pDQogIG5n
IHNvLCBlLmcuIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXBlbm5vLXBjcC16b25l
cy0wMCINCg0KPT4gc2FtZSBpc3N1ZQ0KDQogICBBbHRlcm5hdGl2ZSA0Og0KICAgSXQgaXMgaW5k
aWNhdGVkIGJ5IHRoZSBQQ1AgY2xpZW50IHRoYXQgUENQLWNyZWF0ZWQgZXhwbGljaXQgZHluYW1p
YyBtYXBwaW5ncyBiZSBhDQogIHNzaWduZWQgdGhlIHNhbWUgZXh0ZXJuYWwgSVAgYWRkcmVzcywg
dW5sZXNzIGEgUENQIG9wdGlvbiBpbmRpY2F0ZXMgZGlmZmVyZW50IGV4dGUNCiAgcm5hbCBJUCBh
ZGRyZXNzDQoNCj0+IHNhbWUgaXNzdWUNCg0KSSBjYW4ndCBzZWUgdGhlIHByb2JsZW0sIHRoZSB0
ZXh0IHNheXMgYWxsIG1hcHBpbmdzIChldmVuIHRoZXJlIGlzIG5vdGhpbmcNCmFib3V0IHN0YXRp
YyBtYXBwaW5ncywgaXMgdGhlcmUgYSBwcm9ibGVtIHRvIGFkZCB0aGVtPykgZ2V0IHRoZSBzYW1l
IGV4dGVybmFsDQpJUCBhZGRyZXNzIGlmIHRoZXJlIGlzIG5vIG9wdGlvbiBpbmRpY2F0aW5nIG90
aGVyd2lzZS4NCg0KW1RUXSBGcm9tIHRoZSBjdXJyZW50IHRleHRzLCBpdCBpcyBlYXNpbHkgdW5k
ZXJzdG9vZCB0aGF0IHRoZSBhZGRyZXNzIGlzIGFsbG9jYXRlZCBieSBQQ1Agc2VydmVyLg0KSG93
ZXZlciwgIHRoZSBzYW1lIGV4dGVybmFsIElQIGFkZHJlc3MgZm9yIG9uZSBhcHBsaWNhdGlvbiBp
cyByZXF1aXJlZCBieSB0aGUgUENQIGNsaWVudC4NCg0KDQoNCkJUVyBJV0ZzIHdvcmsgZmFyIGJl
dHRlciBpZiB0aGUgYWZmaW5pdHkgaXMgcGVyIHN1YnNjcmliZXIuDQoNCklNSE8gdGhlIGJlc3Qg
c2hvdWxkIGJlIHRvIG1ha2UgdGhlIGFmZmluaXR5IGxhcmdlciwgaS5lLiwgcGVyIHN1YnNjcmli
ZXINCmFuZCBmb3IgYWxsIG1hcHBpbmdzLCBidXQgYXQgYSBsb3dlciBsZXZlbCwgaS5lLiwgd2l0
aCBhIFJFQ09NTUVORC9TSE9VTEQNCmluIHBsYWNlIG9mIHRoZSBjdXJyZW50IFJFUVVJUkUvTVVT
VC4NCg0KW1RUXSBBZ3JlZS4NCg0KUmVnYXJkcw0KDQpGcmFuY2lzLkR1cG9udEBmZHVwb250LmZy
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KcGNwIG1h
aWxpbmcgbGlzdA0KcGNwQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3BjcA0K

From Francis.Dupont@fdupont.fr  Tue Oct 18 07:48:40 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 D35CD21F8BAA for <pcp@ietfa.amsl.com>; Tue, 18 Oct 2011 07:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level: 
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NyAID3C-Rnof for <pcp@ietfa.amsl.com>; Tue, 18 Oct 2011 07:48:40 -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 145F721F8BA2 for <pcp@ietf.org>; Tue, 18 Oct 2011 07:48:39 -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 p9IEmU9U004782; Tue, 18 Oct 2011 16:48:31 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110181448.p9IEmU9U004782@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: Your message of Tue, 18 Oct 2011 13:23:41 -0000. <C0E0A32284495243BDE0AC8A066631A80C1985E9@szxeml526-mbx.china.huawei.com>
Date: Tue, 18 Oct 2011 16:48:30 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] section 8
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, 18 Oct 2011 14:48:40 -0000

I don't include the gb2312/base64 full text...

=> the section 8 rule is per subscriber+host so the alternative should be too.
[TT] Do you mean that section 8 has defined the same external IP
address per subscriber+host, and we don't need to propose the
alternative texts?

=> what I mean is this is not an alternative but a deep change.
And BTW I am not in its favor, I already consider the section 8 rule
far too permissive (I want an unique per subscriber and long term
external address).

Regards

Francis.Dupont@fdupont.fr

From internet-drafts@ietf.org  Wed Oct 19 22:53:52 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 0CB9E11E80C2; Wed, 19 Oct 2011 22:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ULZfkrVZwcer; Wed, 19 Oct 2011 22:53:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A11C821F8AEE; Wed, 19 Oct 2011 22:53:51 -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.61
Message-ID: <20111020055351.17869.30913.idtracker@ietfa.amsl.com>
Date: Wed, 19 Oct 2011 22:53:51 -0700
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-base-15.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, 20 Oct 2011 05:53:52 -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-15.txt
	Pages           : 79
	Date            : 2011-10-19

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


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pcp-base-15.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-15.txt

From dwing@cisco.com  Wed Oct 19 22:53:57 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 EA8E911E80D0 for <pcp@ietfa.amsl.com>; Wed, 19 Oct 2011 22:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.264
X-Spam-Level: 
X-Spam-Status: No, score=-105.264 tagged_above=-999 required=5 tests=[AWL=1.335, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id umI6PgjLe+1o for <pcp@ietfa.amsl.com>; Wed, 19 Oct 2011 22:53:57 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 8108E11E80C2 for <pcp@ietf.org>; Wed, 19 Oct 2011 22:53:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=894; q=dns/txt; s=iport; t=1319090037; x=1320299637; h=from:to:subject:date:message-id:mime-version: content-transfer-encoding; bh=Rpy5u+QBoqLvGGTYlWJ489xYvwaKihXPY40i3HXcC3k=; b=fxN2JnlWhfZeQ+NOfWb1G8x864WTkzhepeVXgSGdSRpHO0XPBcqk2sDe EhwoQlSMUuIB8W9ggKlWUn3WMdx+qvqmELjKtbuNWQx7BEX4bO9NZai99 weaLzB3tVoJIEGsbvR+WlQBiBNHmcpjzM5wPyEX9yPy1Wv5oUG0dcBz1w w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiUGABW3n06rRDoJ/2dsb2JhbABEmhiBKY1LgQWBdQgKARcQTAUYUCMcAQQeF4dmlUeBJgGeQognBIgDnXM
X-IronPort-AV: E=Sophos;i="4.69,377,1315180800";  d="scan'208";a="9062223"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 20 Oct 2011 05:53:57 +0000
Received: from dwingWS ([10.32.240.198]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9K5rv7p027417 for <pcp@ietf.org>; Thu, 20 Oct 2011 05:53:57 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <pcp@ietf.org>
Date: Wed, 19 Oct 2011 22:53:56 -0700
Message-ID: <01a301cc8eec$a81fe3b0$f85fab10$@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: AcyO7KfoLEnnuBsITFCaJ25i53nRKw==
Content-Language: en-us
Subject: [pcp] draft-ietf-pcp-base-15 posted
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, 20 Oct 2011 05:53:58 -0000

-15 has been posted, which should resolve all open issues.

Side-by-side diffs from -14 to -15,
  http://tools.ietf.org/rfcdiff?url2=draft-ietf-pcp-base-15.txt

document:
http://tools.ietf.org/html/draft-ietf-pcp-base-15

B.1.  Changes from draft-ietf-pcp-base-14 to -15

   o  Softened and removed text that was normatively explaining how PEER
      is implemented within a NAT.

   o  Allow a MAP request for protocol=0, which means "all protocols".
      This can work for an IPv6 or IPv4 firewall.  Its use with a NAPT
      is undefined.

   o  combined SERVER_OVERLOADED and NO_RESOURCES into one error code,
      NO_RESOURCES.

   o  SCTP mappings have to use same internal and requested external
      ports, and have implied PREFER_FAILURE semantics.

   o  Re-instated ADDRESS_MISMATCH error, which only checks the client
      address (not its port).

-d



From Tina.Tsou.Zouting@huawei.com  Thu Oct 20 01:38:59 2011
Return-Path: <Tina.Tsou.Zouting@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 3142F21F8BBF for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 01:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.552
X-Spam-Level: 
X-Spam-Status: No, score=-5.552 tagged_above=-999 required=5 tests=[AWL=1.047,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KF7LtMDN9RBl for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 01:38:58 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 60AEB21F8BBC for <pcp@ietf.org>; Thu, 20 Oct 2011 01:38:58 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LTC00MKYVXFVA@szxga03-in.huawei.com> for pcp@ietf.org; Thu, 20 Oct 2011 16:36:51 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LTC00GRHVXFXI@szxga03-in.huawei.com> for pcp@ietf.org; Thu, 20 Oct 2011 16:36:51 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEI35312; Thu, 20 Oct 2011 16:36:50 +0800
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 20 Oct 2011 16:36:35 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.58]) by szxeml410-hub.china.huawei.com ([10.82.67.137]) with mapi id 14.01.0270.001; Thu, 20 Oct 2011 16:36:31 +0800
Date: Thu, 20 Oct 2011 08:36:31 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <201110181448.p9IEmU9U004782@givry.fdupont.fr>
X-Originating-IP: [10.212.245.234]
To: "Francis.Dupont@fdupont.fr" <Francis.Dupont@fdupont.fr>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C19B540@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: [pcp] section 8
Thread-index: AQHMjaUA13yvB88tzkaCmzhKkDKJiJWE606A
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: "18 Oct 2011 13:23:41 -0000." <C0E0A32284495243BDE0AC8A066631A80C1985E9@szxeml526-mbx.china.huawei.com> <201110181448.p9IEmU9U004782@givry.fdupont.fr>
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] section 8
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, 20 Oct 2011 08:38:59 -0000

How about
In the absence of a PCP option indicating otherwise, it is REQUIRED that PCP-created explicit dynamic mappings be assigned the same external IP address as requested by PCP client.


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


-----Original Message-----
From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr] 
Sent: Tuesday, October 18, 2011 4:49 PM
To: Tina TSOU
Cc: pcp@ietf.org
Subject: Re: [pcp] section 8

I don't include the gb2312/base64 full text...

=> the section 8 rule is per subscriber+host so the alternative should be too.
[TT] Do you mean that section 8 has defined the same external IP
address per subscriber+host, and we don't need to propose the
alternative texts?

=> what I mean is this is not an alternative but a deep change.
And BTW I am not in its favor, I already consider the section 8 rule
far too permissive (I want an unique per subscriber and long term
external address).

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Thu Oct 20 01:53:58 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 0738B21F8AF1 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 01:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XV8xQeSjvIVX for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 01:53:57 -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 22B5C21F8AD9 for <pcp@ietf.org>; Thu, 20 Oct 2011 01:53:56 -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 p9K8rrf9059078; Thu, 20 Oct 2011 10:53:53 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110200853.p9K8rrf9059078@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Wed, 19 Oct 2011 22:53:56 PDT. <01a301cc8eec$a81fe3b0$f85fab10$@com> 
Date: Thu, 20 Oct 2011 10:53:53 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] draft-ietf-pcp-base-15 posted
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, 20 Oct 2011 08:53:58 -0000

 In your previous mail you wrote:

   -15 has been posted, which should resolve all open issues.
   
=> we don't have the same definition of "all"...

Regards

Francis.Dupont@fdupont.fr

PS: the PROCESSING_ERROR is still at the head of my (far to
be empty :-) list of open issues.
PPS: BTW looking at the diff in section 8 in the figure 6 comments:
either plain -> Plain or Encapsulation -> encapsulation

From Francis.Dupont@fdupont.fr  Thu Oct 20 02:13:48 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 91E6B21F8BA0 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 02:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.513
X-Spam-Level: 
X-Spam-Status: No, score=-2.513 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gkdRkyK5w4uI for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 02:13:48 -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 BFBAE21F84DF for <pcp@ietf.org>; Thu, 20 Oct 2011 02:13:47 -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 p9K9DjUp060432 for <pcp@ietf.org>; Thu, 20 Oct 2011 11:13:45 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110200913.p9K9DjUp060432@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 20 Oct 2011 11:13:45 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] suggested external address
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, 20 Oct 2011 09:13:48 -0000

I have two questions about the suggested external address
(for MAP but they are the same for PEER):

in 9.1 it is defined as:

   Suggested External IP Address:  Suggested external IPv4 or IPv6
      address.  This is useful for refreshing a mapping, especially
      after the PCP server loses state.  If the PCP client does not know
      the external address, or does not have a preference, it MUST use
      the address-family-specific all-zeroes address (see Section 5).

About the last statement, does it mean if an IPv4-IPv4 NAT receives
a MAP request with :: (NOT ::ffff:0.0.0.0) as the suggested external
address it replies with a malformed request error?
This is how I interpret the MUST but it requires the client to do the
right thing (and to know the address family to use), including
in the sections 7.[123].
(BTW I am in favor of this behavior because it helps the client
to understand what types of CGNs PCP servers control).

The second question is about the new "external address or port"
mismatch returns a CANNOT_PROVIDE_EXTERNAL_PORT. I like this
but the error definition is still about port even the cause can
be the address, so:
 - should a CANNOT_PROVIDE_EXTERNAL_ADDR be defined?
 - what is the exact behavior of PREFER_FAILURE (including implicit)
  with an external address != 0 but port == 0? (what I believe? is a
  clarification needed?)
BTW the PREFER_FAILURE section 11.2 obviously needs to be updated.

Regards

Francis.Dupont@fdupont.fr

PS: section 6.4:

   11 CANNOT_PROVIDE_EXTERNAL_PORT: the requested external port cannot
      be provided.  This error MUST only be returned for PEER requests,
      for MAP requests that included the PREFER_FAILURE Option (because
      otherwise a new external port could have been assigned), or PEER
                                                                      ^ ,
      or MAP requests for the SCTP protcool.  See Section 11.2 for
      processing details.  The error lifetime depends on the reason for
      the failure.

From Francis.Dupont@fdupont.fr  Thu Oct 20 02:31:52 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 7FF3221F8AF9 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 02:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level: 
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E8pSTcI8bRdI for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 02:31:52 -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 C871221F8A97 for <pcp@ietf.org>; Thu, 20 Oct 2011 02:31:51 -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 p9K9VbwB061571; Thu, 20 Oct 2011 11:31:38 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110200931.p9K9VbwB061571@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: Your message of Thu, 20 Oct 2011 08:36:31 -0000. <C0E0A32284495243BDE0AC8A066631A80C19B540@szxeml526-mbx.china.huawei.com>
Date: Thu, 20 Oct 2011 11:31:37 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] section 8
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, 20 Oct 2011 09:31:52 -0000

 In your previous mail you wrote:

   How about
   In the absence of a PCP option indicating otherwise, it is REQUIRED
   that PCP-created explicit dynamic mappings be assigned the same
   external IP address as requested by PCP client.
   
=> IMHO this is useless as the PREFER_FAILURE in base 15 (IMHO again)
provides this.
   
Regards
   
Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Thu Oct 20 02:44:31 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 63CB821F8B7B for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 02:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.873
X-Spam-Level: 
X-Spam-Status: No, score=-1.873 tagged_above=-999 required=5 tests=[AWL=-0.566, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HFnmgfkdmt2E for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 02:44:31 -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 B1CC021F8B71 for <pcp@ietf.org>; Thu, 20 Oct 2011 02:44:30 -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 p9K9iTX2062376 for <pcp@ietf.org>; Thu, 20 Oct 2011 11:44:29 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110200944.p9K9iTX2062376@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
cc: pcp@ietf.org
In-reply-to: Your message of Thu, 20 Oct 2011 11:13:45 +0200.
Date: Thu, 20 Oct 2011 11:44:29 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: Re: [pcp] suggested external address
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, 20 Oct 2011 09:44:31 -0000

 In your previous mail you wrote:

    - should a CANNOT_PROVIDE_EXTERNAL_ADDR be defined?
   
=> or CANNOT_PROVIDE_EXTERNAL_PORT renamed to CANNOT_PROVIDE_EXTERNAL
(a shorter name should never a bad idea :-)

Regards
   
Francis.Dupont@fdupont.fr

From Tina.Tsou.Zouting@huawei.com  Thu Oct 20 03:24:55 2011
Return-Path: <Tina.Tsou.Zouting@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 9EDCA21F8B64 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 03:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.639
X-Spam-Level: 
X-Spam-Status: No, score=-5.639 tagged_above=-999 required=5 tests=[AWL=0.960,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VJfALxTFpF7L for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 03:24:55 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 1308221F8B62 for <pcp@ietf.org>; Thu, 20 Oct 2011 03:24:55 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LTD00DF30W0AU@szxga05-in.huawei.com> for pcp@ietf.org; Thu, 20 Oct 2011 18:24:00 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LTD005N80VXBB@szxga05-in.huawei.com> for pcp@ietf.org; Thu, 20 Oct 2011 18:24:00 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEI43853; Thu, 20 Oct 2011 18:23:29 +0800
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 20 Oct 2011 18:23:04 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.58]) by szxeml411-hub.china.huawei.com ([10.82.67.138]) with mapi id 14.01.0270.001; Thu, 20 Oct 2011 18:23:02 +0800
Date: Thu, 20 Oct 2011 10:23:00 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <201110200944.p9K9iTX2062376@givry.fdupont.fr>
X-Originating-IP: [10.212.245.234]
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C19B8B9@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: [pcp] suggested external address
Thread-index: AQHMjwzcBpHKmw+83kSXPK+FdJm1k5WFBIfw
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: "20 Oct 2011 11:13:45 +0200." <201110200944.p9K9iTX2062376@givry.fdupont.fr>
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] suggested external address
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, 20 Oct 2011 10:24:55 -0000

Francis,
I meant client needs to proactively request same external IP.

Tina

-----Original Message-----
From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Francis Dupont
Sent: Thursday, October 20, 2011 11:44 AM
Cc: pcp@ietf.org
Subject: Re: [pcp] suggested external address

 In your previous mail you wrote:

    - should a CANNOT_PROVIDE_EXTERNAL_ADDR be defined?
   
=> or CANNOT_PROVIDE_EXTERNAL_PORT renamed to CANNOT_PROVIDE_EXTERNAL
(a shorter name should never a bad idea :-)

Regards
   
Francis.Dupont@fdupont.fr
_______________________________________________
pcp mailing list
pcp@ietf.org
https://www.ietf.org/mailman/listinfo/pcp

From Francis.Dupont@fdupont.fr  Thu Oct 20 03:39:22 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 8FB9D21F8A91 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 03:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d-GM2+2oFInw for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 03:39:22 -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 CE75B21F8A66 for <pcp@ietf.org>; Thu, 20 Oct 2011 03:39:21 -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 p9KAdHmI065718 for <pcp@ietf.org>; Thu, 20 Oct 2011 12:39:20 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110201039.p9KAdHmI065718@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 20 Oct 2011 12:39:17 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] blocking error in base 15
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, 20 Oct 2011 10:39:22 -0000

There is a blocking error in base 15: in 6.1 two 16 bit fields
in header request were added but not reflected in response request
in 6.2 so headers have no longer the same size!

I propose to change the two 96 into 128 in 6.2,
*and* from authors to reply in the list it is the correct fix
so we don't have to wait for the base 16 to work.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Thu Oct 20 04:08:00 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 69D0521F8B29 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 04:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level: 
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aFu0bNC07rIq for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 04:08:00 -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 B35EE21F8B24 for <pcp@ietf.org>; Thu, 20 Oct 2011 04:07:59 -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 p9KB7w6r067491 for <pcp@ietf.org>; Thu, 20 Oct 2011 13:07:58 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110201107.p9KB7w6r067491@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 20 Oct 2011 13:07:58 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] typo in base 15
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, 20 Oct 2011 11:08:00 -0000

in section 7.5:

  ... 3660 seconds <line break> (one hour)

I believe one should read 3600 seconds?

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Thu Oct 20 04:35:12 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 6CA1821F8AFF for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 04:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVIjwVnjuXwx for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 04:35:12 -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 B0C9221F8AFE for <pcp@ietf.org>; Thu, 20 Oct 2011 04:35:11 -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 p9KBU5wv068866; Thu, 20 Oct 2011 13:30:06 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110201130.p9KBU5wv068866@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: Your message of Thu, 20 Oct 2011 10:23:00 -0000. <C0E0A32284495243BDE0AC8A066631A80C19B8B9@szxeml526-mbx.china.huawei.com>
Date: Thu, 20 Oct 2011 13:30:05 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] suggested external address
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, 20 Oct 2011 11:35:12 -0000

 In your previous mail you wrote:

   I meant client needs to proactively request same external IP.
   
=> but they can easily do it by using a PREFER_FAILURE if
my interpretation of the MAP request processing is correct.

Regards
   
Francis.Dupont@fdupont.fr

From dwing@cisco.com  Thu Oct 20 08:08:08 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 88CF921F8BD3 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 08:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.297
X-Spam-Level: 
X-Spam-Status: No, score=-105.297 tagged_above=-999 required=5 tests=[AWL=1.302, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Wxipca589kN for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 08:08:08 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 0D38E21F8B65 for <pcp@ietf.org>; Thu, 20 Oct 2011 08:08:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=815; q=dns/txt; s=iport; t=1319123288; x=1320332888; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=HuXr72/0/18NznMQLdRqNNJg6F206Dl2PWtB96OInWg=; b=fujM5psvoUNiPEQUTvstCU624kb8RNtDZYe6pP43eM3Bny0amMhX+D3e bVY/Mr3/s1XOJAhi9y+pznMGGA+eUEHgctKJm507cbTuqYN7AAoLN5aW3 goiw4ILSVeMVrBoMPz/JWrSLb5HMUV7IBFgQLqzFX0Y2FdEJRsZa/erd9 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am0BAHs4oE6rRDoG/2dsb2JhbABDmVhDgSmNUoEFgW4BAQEECAoBFAMQPwwBAwIJDwEBBAEBAScHGSMKCQgBAQQTCxefMAGeN4gpBIgDnXQ
X-IronPort-AV: E=Sophos;i="4.69,379,1315180800";  d="scan'208";a="9142316"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 20 Oct 2011 15:08:08 +0000
Received: from dwingWS ([10.32.240.198]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9KF87L9013333; Thu, 20 Oct 2011 15:08:07 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Wed, 19 Oct 2011 22:53:56 PDT. <01a301cc8eec$a81fe3b0$f85fab10$@com> <201110200853.p9K8rrf9059078@givry.fdupont.fr>
In-Reply-To: <201110200853.p9K8rrf9059078@givry.fdupont.fr>
Date: Thu, 20 Oct 2011 08:08:07 -0700
Message-ID: <030601cc8f3a$13185a60$39490f20$@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: AcyPBczFjoRRSO24TtytuKyNgOZNmgANDZFw
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] draft-ietf-pcp-base-15 posted
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, 20 Oct 2011 15:08:08 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Thursday, October 20, 2011 1:54 AM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] draft-ietf-pcp-base-15 posted
> 
> 
>  In your previous mail you wrote:
> 
>    -15 has been posted, which should resolve all open issues.
> 
> => we don't have the same definition of "all"...
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: the PROCESSING_ERROR is still at the head of my (far to
> be empty :-) list of open issues.
> PPS: BTW looking at the diff in section 8 in the figure 6 comments:
> either plain -> Plain or Encapsulation -> encapsulation

I don't follow.  Please provide clearer feedback on the mistake
in that text.  RFC Editor's OLD / NEW syntax works well.

-d



From dwing@cisco.com  Thu Oct 20 08:32:20 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 F08DE21F8C1E for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 08:32:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.329
X-Spam-Level: 
X-Spam-Status: No, score=-105.329 tagged_above=-999 required=5 tests=[AWL=1.270, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0nyF2UqifBXz for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 08:32:19 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 1E0B621F8C12 for <pcp@ietf.org>; Thu, 20 Oct 2011 08:32:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=4037; q=dns/txt; s=iport; t=1319124739; x=1320334339; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=hPLSH77xzjF2+wLr6DpSb6uQBbEwiFWq4xcWITBRYDg=; b=jb8QxECkbJz0cz15fKibTw9veWf4CNkl/r8DQbTZSFwIQ+NEEk4BEO5R 5hJlzmWfrAYIMg/wfb5sVEqHN46eUftIwh/dtiPEmy+pkHF7M/c7vXDCN 0cvC5YLnNcbGnByQh1zVCu7xoq/cmVzpplR2fWPI1a3UZvOoa2UMaCjyv o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvQAABA+oE6rRDoH/2dsb2JhbABDmVqBbI1SgQWBbgEBAQMBCAoBFxBEBwEDAgkPAQEEAQEoBxkjCgkIAQEEARILF4del1oBnjmIKQSIA510
X-IronPort-AV: E=Sophos;i="4.69,379,1315180800";  d="scan'208";a="8711419"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 20 Oct 2011 15:32:17 +0000
Received: from dwingWS ([10.32.240.198]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9KFWGZI009612; Thu, 20 Oct 2011 15:32:16 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110200913.p9K9DjUp060432@givry.fdupont.fr>
In-Reply-To: <201110200913.p9K9DjUp060432@givry.fdupont.fr>
Date: Thu, 20 Oct 2011 08:32:16 -0700
Message-ID: <033001cc8f3d$72f6dda0$58e498e0$@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: AcyPCJWkPRTh6ThKTsqSuTYBin0rAgAMqn9g
Content-Language: en-us
Subject: Re: [pcp] suggested external address
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, 20 Oct 2011 15:32:20 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, October 20, 2011 2:14 AM
> To: pcp@ietf.org
> Subject: [pcp] suggested external address
> 
> I have two questions about the suggested external address
> (for MAP but they are the same for PEER):
> 
> in 9.1 it is defined as:
> 
>    Suggested External IP Address:  Suggested external IPv4 or IPv6
>       address.  This is useful for refreshing a mapping, especially
>       after the PCP server loses state.  If the PCP client does not
> know
>       the external address, or does not have a preference, it MUST use
>       the address-family-specific all-zeroes address (see Section 5).
> 
> About the last statement, does it mean if an IPv4-IPv4 NAT receives
> a MAP request with :: (NOT ::ffff:0.0.0.0) as the suggested external
> address it replies with a malformed request error?

The text quoted above doesn't say anything about what the PCP server
would do when it receives the IPv6 all-zeros address.

The text that is closest to describing this case is in 9.3,
"Processing a MAP Request",

   If
   the PCP server or PCP-controlled device does not support the Protocol
   or cannot create a mapping for the Protocol (e.g., because the
   request is for a NAT mapping instead of a firewall mapping and the
   PCP-controlled device is not a NAT or does not support NATting that
   specific Protocol), it MUST generate an UNSUPP_PROTOCOL error.

> This is how I interpret the MUST but it requires the client to do the
> right thing (and to know the address family to use), including
> in the sections 7.[123].

This encoding of IPV4 all-zeros and IPv6 all-zeros is how we managed
to collapse the MAP4 and MAP6 Opcodes into the MAP Opcode, and 
collapse the PEER4 and PEER6 Opcodes into the PEER Opcode.  The
functionality is the same as the separate MAP4/MAP6/PEER4/PEER6
Opcodes.

> (BTW I am in favor of this behavior because it helps the client
> to understand what types of CGNs PCP servers control).
> 
> The second question is about the new "external address or port"
> mismatch returns a CANNOT_PROVIDE_EXTERNAL_PORT. I like this
> but the error definition is still about port even the cause can
> be the address, so:
>  - should a CANNOT_PROVIDE_EXTERNAL_ADDR be defined?

Renaming the error, as you suggested in another email, seems
suitable.

>  - what is the exact behavior of PREFER_FAILURE (including implicit)
>   with an external address != 0 but port == 0? (what I believe? is a
>   clarification needed?)

Section 9.3 says this, which I believe covers the Internal Port=0
case, which prohibits using Internal Port=0 for protocols with port
numbers.  

   If
   the Protocol is supported and the Internal Port is zero but the
   protocol uses a 16 bit port number (e.g., TCP, SCTP), it generates a
   MALFORMED_REQUEST error.  

We may want to revisit the text above considering this addition 
in -15 to map all protocols:

   If the Protocol and Internal
   Port are both 0 (zero), all protocols and all ports, without any
   exception, are mapped; if this request cannot be fulfilled, the error
   UNSUPP_PROTOCOL MUST be returned.

Feedback from the WG is welcome on this point.

> BTW the PREFER_FAILURE section 11.2 obviously needs to be updated.
>
> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: section 6.4:
> 
>    11 CANNOT_PROVIDE_EXTERNAL_PORT: the requested external port cannot
>       be provided.  This error MUST only be returned for PEER requests,
>       for MAP requests that included the PREFER_FAILURE Option (because
>       otherwise a new external port could have been assigned), or PEER
>                                                                       ^
> ,
>       or MAP requests for the SCTP protcool.  See Section 11.2 for
>       processing details.  The error lifetime depends on the reason for
>       the failure.

Fixed, thanks.

-d



From dwing@cisco.com  Thu Oct 20 09:30:13 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 04AFA21F8CB4 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 09:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.359
X-Spam-Level: 
X-Spam-Status: No, score=-105.359 tagged_above=-999 required=5 tests=[AWL=1.240, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IeqEj7gomR0A for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 09:30:12 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 880CE21F8CAF for <pcp@ietf.org>; Thu, 20 Oct 2011 09:30:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2963; q=dns/txt; s=iport; t=1319128212; x=1320337812; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=eDXpkYD6gGCZEZdKXmX+pjWDG92TZgrq9XIt0fMEDIU=; b=l3ppMs7z6a8aG5SGneaKGAxDc016MA13hPzz2N3YQDKMXBQfNVS5QmkI ejse2Xyuxb/hccmjBD56FznYpnBMiFIINIUuCr5izGpb2iwqPbSLCYre+ bDXcZNwyKXybaA3/wyeHKB3aDHqOtdHhTCC/d/FVVW2tO8t7QiD6W8kh9 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvUAAAFMoE6rRDoG/2dsb2JhbABCmVqBbI1SgQWBbgEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsXh14Il14Bnj2IKQSIA510
X-IronPort-AV: E=Sophos;i="4.69,379,1315180800";  d="scan'208";a="9141689"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 20 Oct 2011 16:30:12 +0000
Received: from dwingWS ([10.32.240.198]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9KGUCsP028310; Thu, 20 Oct 2011 16:30:12 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110201039.p9KAdHmI065718@givry.fdupont.fr>
In-Reply-To: <201110201039.p9KAdHmI065718@givry.fdupont.fr>
Date: Thu, 20 Oct 2011 09:30:11 -0700
Message-ID: <03b201cc8f45$8a447780$9ecd6680$@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: AcyPFIkmaNaevVsOQ3+tCrvZiymENAAMFCCg
Content-Language: en-us
Subject: Re: [pcp] blocking error in base 15
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, 20 Oct 2011 16:30:13 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Thursday, October 20, 2011 3:39 AM
> To: pcp@ietf.org
> Subject: [pcp] blocking error in base 15
> 
> There is a blocking error in base 15: in 6.1 two 16 bit fields
> in header request were added but not reflected in response request
> in 6.2 so headers have no longer the same size!

You're right.  http://tools.ietf.org/html/draft-ietf-pcp-base-15#section-6.1
shows this, and the 32 bits marked with "**" shouldn't be there:

    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Version = 1  |R|   Opcode    |         Reserved              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                 Requested Lifetime (32 bits)                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   |            PCP Client's IP address (128 bits)                 |
   |                                                               |
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
** |    PCP Client's Port          |    Reserved (16 bits)         | **
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   :                                                               :
   :             (optional) Opcode-specific information            :
   :                                                               :
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   :                                                               :
   :             (optional) PCP Options                            :
   :                                                               :
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Those fields are not described in the text.


> I propose to change the two 96 into 128 in 6.2,

I don't understand.  By "96", I assume you mean "96 bit fields"; but
there is only one 96 bit field in 6.2 (response format).

By removing the extraneous 32 bits above (highlighted with "**")
we will have a request format with:

   32 bits header
   32 bits lifetime
  128 bits PCP client IP address
total: 192 bits

response format has:
   32 bits header
   32 bits lifetime
   32 bits epoch
   96 bits reserved
total: 192 bits

> *and* from authors to reply in the list it is the correct fix
> so we don't have to wait for the base 16 to work.

-d


> Regards
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From Francis.Dupont@fdupont.fr  Thu Oct 20 14:33:31 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 92A9621F8AF1 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 14:33:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JUV4WaAss0mJ for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 14:33:30 -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 57E9121F84DF for <pcp@ietf.org>; Thu, 20 Oct 2011 14:33:30 -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 p9KLXRQH005649; Thu, 20 Oct 2011 23:33:27 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110202133.p9KLXRQH005649@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 20 Oct 2011 08:08:07 PDT. <030601cc8f3a$13185a60$39490f20$@com> 
Date: Thu, 20 Oct 2011 23:33:27 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] draft-ietf-pcp-base-15 posted
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, 20 Oct 2011 21:33:31 -0000

 In your previous mail you wrote:

   > PS: the PROCESSING_ERROR is still at the head of my (far to
   > be empty :-) list of open issues.

=> get back (from base 12):

   6  PROCESSING_ERROR, server encountered an error after parsing while
      attempting to process a request.

(of course the important detail is the "after parsing")

   > PPS: BTW looking at the diff in section 8 in the figure 6 comments:
   > either plain -> Plain or Encapsulation -> encapsulation
   
   I don't follow.  Please provide clearer feedback on the mistake
   in that text.  RFC Editor's OLD / NEW syntax works well.
   
=> replace:

   Dual-Stack Lite plain mode and (2) showing Dual-Stack Lite
   Encapsulation mode [I-D.dupont-pcp-dslite].  In a Dual-Stack Lite

by

   Dual-Stack Lite Plain mode and (2) showing Dual-Stack Lite
   Encapsulation mode [I-D.dupont-pcp-dslite].  In a Dual-Stack Lite
   
or

   Dual-Stack Lite plain mode and (2) showing Dual-Stack Lite
   encapsulation mode [I-D.dupont-pcp-dslite].  In a Dual-Stack Lite

(I prefer the second: I am French, not German :-).

Regards

Francis.Dupont@fdupont.fr

From dwing@cisco.com  Thu Oct 20 14:46:30 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 99ECE11E8085 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 14:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.415
X-Spam-Level: 
X-Spam-Status: No, score=-105.415 tagged_above=-999 required=5 tests=[AWL=1.184, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Waf5JCYhPoHs for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 14:46:30 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 359C021F8B27 for <pcp@ietf.org>; Thu, 20 Oct 2011 14:46:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1818; q=dns/txt; s=iport; t=1319147190; x=1320356790; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=MsxWjulBzj/0sprGRltvjICMcAdlUrT4CMqhUytYRHQ=; b=LkHLTSTcLnHUYDToFRV/GfSQ9WTd+wJJJCFL+C7n6SV5n/osignaGom0 DWUq5n+WmVAh5x5e9b9+ZzxaFwyS6F46MmqJ4px4XOEaC67bCRwDMNr3+ l/3/sxM4Ua//K43FJR06sAC1ra/FxG4S0Qo8fFJPSfQ9l7ZgvzjqbYqwn 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjUBAMOVoE6rRDoH/2dsb2JhbABCmVpDgSmNVIEFgW4BAQEDAQgKARQDED8MAQMCCQ8BAQQBAQEnBxkjCgkIAQEEEwsXh14IlzQBniqIKQSIA510
X-IronPort-AV: E=Sophos;i="4.69,381,1315180800";  d="scan'208";a="9249423"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 20 Oct 2011 21:46:29 +0000
Received: from dwingWS ([10.32.240.198]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9KLkSUL009731; Thu, 20 Oct 2011 21:46:29 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Thu, 20 Oct 2011 08:08:07 PDT. <030601cc8f3a$13185a60$39490f20$@com> <201110202133.p9KLXRQH005649@givry.fdupont.fr>
In-Reply-To: <201110202133.p9KLXRQH005649@givry.fdupont.fr>
Date: Thu, 20 Oct 2011 14:46:28 -0700
Message-ID: <05ad01cc8f71$b959ac80$2c0d0580$@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: AcyPb+j9BXCdadEOT0Ga/z9vkRJzdAAAVyzQ
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] draft-ietf-pcp-base-15 posted
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, 20 Oct 2011 21:46:30 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Thursday, October 20, 2011 2:33 PM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] draft-ietf-pcp-base-15 posted
> 
> 
>  In your previous mail you wrote:
> 
>    > PS: the PROCESSING_ERROR is still at the head of my (far to
>    > be empty :-) list of open issues.
> 
> => get back (from base 12):
> 
>    6  PROCESSING_ERROR, server encountered an error after parsing while
>       attempting to process a request.
> 
> (of course the important detail is the "after parsing")

The change log at
http://tools.ietf.org/html/draft-ietf-pcp-base-15#appendix-B.3
says it was removed because:

   o  removed PROCESSING_ERROR error, which was too similar to
      MALFORMED_REQUEST.

I don't know how to write the important detail to differentiate
between the two errors for the server or for what the client would
do.

>    > PPS: BTW looking at the diff in section 8 in the figure 6
> comments:
>    > either plain -> Plain or Encapsulation -> encapsulation
> 
>    I don't follow.  Please provide clearer feedback on the mistake
>    in that text.  RFC Editor's OLD / NEW syntax works well.
> 
> => replace:
> 
>    Dual-Stack Lite plain mode and (2) showing Dual-Stack Lite
>    Encapsulation mode [I-D.dupont-pcp-dslite].  In a Dual-Stack Lite
> 
> by
> 
>    Dual-Stack Lite Plain mode and (2) showing Dual-Stack Lite
>    Encapsulation mode [I-D.dupont-pcp-dslite].  In a Dual-Stack Lite
> 
> or
> 
>    Dual-Stack Lite plain mode and (2) showing Dual-Stack Lite
>    encapsulation mode [I-D.dupont-pcp-dslite].  In a Dual-Stack Lite
> 
> (I prefer the second: I am French, not German :-).

Oh, it's a nit about uppercase/lowercase.  Fixed.

-d



From Francis.Dupont@fdupont.fr  Thu Oct 20 14:49:37 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 5503011E809D for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 14:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level: 
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2EC33dhc8L1b for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 14:49:36 -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 2D8241F0C45 for <pcp@ietf.org>; Thu, 20 Oct 2011 14:49:35 -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 p9KLnXhI006605; Thu, 20 Oct 2011 23:49:33 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110202149.p9KLnXhI006605@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 20 Oct 2011 08:32:16 PDT. <033001cc8f3d$72f6dda0$58e498e0$@com> 
Date: Thu, 20 Oct 2011 23:49:33 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] suggested external address
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, 20 Oct 2011 21:49:37 -0000

 In your previous mail you wrote:

   > -----Original Message-----
   > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
   > Francis Dupont
   > Sent: Thursday, October 20, 2011 2:14 AM
   > To: pcp@ietf.org
   > Subject: [pcp] suggested external address
   > 
   > I have two questions about the suggested external address
   > (for MAP but they are the same for PEER):
   > 
   > in 9.1 it is defined as:
   > 
   >    Suggested External IP Address:  Suggested external IPv4 or IPv6
   >       address.  This is useful for refreshing a mapping, especially
   >       after the PCP server loses state.  If the PCP client does not
   > know
   >       the external address, or does not have a preference, it MUST use
   >       the address-family-specific all-zeroes address (see Section 5).
   > 
   > About the last statement, does it mean if an IPv4-IPv4 NAT receives
   > a MAP request with :: (NOT ::ffff:0.0.0.0) as the suggested external
   > address it replies with a malformed request error?
   
   The text quoted above doesn't say anything about what the PCP server
   would do when it receives the IPv6 all-zeros address.
   
=> the "MUST" strongly suggest the PCP server should raise an error
if it is not happy with the suggested external address as I explained later.

   The text that is closest to describing this case is in 9.3,
   "Processing a MAP Request",
   
      If
      the PCP server or PCP-controlled device does not support the Protocol
      or cannot create a mapping for the Protocol (e.g., because the
      request is for a NAT mapping instead of a firewall mapping and the
      PCP-controlled device is not a NAT or does not support NATting that
      specific Protocol), it MUST generate an UNSUPP_PROTOCOL error.
   
   > This is how I interpret the MUST but it requires the client to do the
   > right thing (and to know the address family to use), including
   > in the sections 7.[123].
   
   This encoding of IPV4 all-zeros and IPv6 all-zeros is how we managed
   to collapse the MAP4 and MAP6 Opcodes into the MAP Opcode, and 
   collapse the PEER4 and PEER6 Opcodes into the PEER Opcode.  The
   functionality is the same as the separate MAP4/MAP6/PEER4/PEER6
   Opcodes.
   
=> so it seems the PCP server should raise an error on address family
mismatch. I suppose it is the MALFORMED_REQUEST one.

   > (BTW I am in favor of this behavior because it helps the client
   > to understand what types of CGNs PCP servers control).
   > 
   > The second question is about the new "external address or port"
   > mismatch returns a CANNOT_PROVIDE_EXTERNAL_PORT. I like this
   > but the error definition is still about port even the cause can
   > be the address, so:
   >  - should a CANNOT_PROVIDE_EXTERNAL_ADDR be defined?
   
   Renaming the error, as you suggested in another email, seems
   suitable.
   
=> thanks.

   >  - what is the exact behavior of PREFER_FAILURE (including implicit)
   >   with an external address != 0 but port == 0? (what I believe? is a
   >   clarification needed?)
   
   Section 9.3 says this, which I believe covers the Internal Port=0

=> the question is about the external port.

   case, which prohibits using Internal Port=0 for protocols with port
   numbers.  
   
      If
      the Protocol is supported and the Internal Port is zero but the
      protocol uses a 16 bit port number (e.g., TCP, SCTP), it generates a
      MALFORMED_REQUEST error.  
   
   We may want to revisit the text above considering this addition 
   in -15 to map all protocols:
   
      If the Protocol and Internal
      Port are both 0 (zero), all protocols and all ports, without any
      exception, are mapped; if this request cannot be fulfilled, the error
      UNSUPP_PROTOCOL MUST be returned.
   
   Feedback from the WG is welcome on this point.
   
=> I explain my idea: as the PREFER_FAILURE covers now both the external
address and the external port, we have 4 cases:
 - suggested external address != 0, suggested external port != 0:
  get a mapping with these two values or fail

 - suggested external address == 0, suggested external port != 0:
  get a mapping with the port and a suitable external address, or fail

 - suggested external address == 0, suggested external port == 0:
  fail with MALFORMED_OPTION

 - suggested external address != 0, suggested external port == 0:
   (new case) get a mapping with the address and an external port,
   or fail

So the last/new case is the way to force the use of the suggested external
address.

   > BTW the PREFER_FAILURE section 11.2 obviously needs to be updated.

=> still applies

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Thu Oct 20 14:53:53 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 DDFFC1F0C5A for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 14:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Z2ZhcC6yqe5 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 14:53:52 -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 A3DA31F0C58 for <pcp@ietf.org>; Thu, 20 Oct 2011 14:53:50 -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 p9KLrm33006884; Thu, 20 Oct 2011 23:53:48 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110202153.p9KLrm33006884@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 20 Oct 2011 09:30:11 PDT. <03b201cc8f45$8a447780$9ecd6680$@com> 
Date: Thu, 20 Oct 2011 23:53:48 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] blocking error in base 15
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, 20 Oct 2011 21:53:53 -0000

 In your previous mail you wrote:

   > -----Original Message-----
   > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
   > Francis Dupont
   > Sent: Thursday, October 20, 2011 3:39 AM
   > To: pcp@ietf.org
   > Subject: [pcp] blocking error in base 15
   > 
   > There is a blocking error in base 15: in 6.1 two 16 bit fields
   > in header request were added but not reflected in response request
   > in 6.2 so headers have no longer the same size!
   
   You're right.  http://tools.ietf.org/html/draft-ietf-pcp-base-15#section-6.1
   shows this, and the 32 bits marked with "**" shouldn't be there:
   
       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Version = 1  |R|   Opcode    |         Reserved              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                 Requested Lifetime (32 bits)                  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      |            PCP Client's IP address (128 bits)                 |
      |                                                               |
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ** |    PCP Client's Port          |    Reserved (16 bits)         | **
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                                                               :
      :             (optional) Opcode-specific information            :
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                                                               :
      :             (optional) PCP Options                            :
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   
   Those fields are not described in the text.
   
   
   > I propose to change the two 96 into 128 in 6.2,
   
   I don't understand.  By "96", I assume you mean "96 bit fields"; but
   there is only one 96 bit field in 6.2 (response format).
   
=> the number 96 occurs twice in 6.2 (but you decided to remove the
source port, BTW the text about the address and port in the response
should be removed from base 15).

   By removing the extraneous 32 bits above (highlighted with "**")
   we will have a request format with:
   
      32 bits header
      32 bits lifetime
     128 bits PCP client IP address
   total: 192 bits
   
   response format has:
      32 bits header
      32 bits lifetime
      32 bits epoch
      96 bits reserved
   total: 192 bits
   
=> so we came back to something sane

Thanks!

Francis.Dupont@fdupont.fr

From jhw@apple.com  Thu Oct 20 14:56:24 2011
Return-Path: <jhw@apple.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 B681621F8B55 for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 14:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level: 
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjUTGn4k5tcx for <pcp@ietfa.amsl.com>; Thu, 20 Oct 2011 14:56:24 -0700 (PDT)
Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 4ED1321F8B54 for <pcp@ietf.org>; Thu, 20 Oct 2011 14:56:24 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_m/olMHTbp+v8M0nuXvQ8bA)"
Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LTD00BW6WX3UYP2@mail-out.apple.com> for pcp@ietf.org; Thu, 20 Oct 2011 14:55:58 -0700 (PDT)
X-AuditID: 11807137-b7c56ae0000051ed-61-4ea098ee3ec7
Received: from ba0301a-dhcp89.apple.com (ba0301a-dhcp89.apple.com [17.193.14.217]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay16.apple.com (Apple SCV relay) with SMTP id E7.6C.20973.EE890AE4; Thu, 20 Oct 2011 14:55:58 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <201110202149.p9KLnXhI006605@givry.fdupont.fr>
Date: Thu, 20 Oct 2011 14:55:58 -0700
Message-id: <CA759C11-366E-476B-85BC-ED8AD14F852D@apple.com>
References: <201110202149.p9KLnXhI006605@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsUieJDvpu67GQv8DJZ9Ebe4eO0hk8WjaTtZ LSYf+83qwOwx5fdGVo93U/+weixZ8pMpgDmKyyYlNSezLLVI3y6BK2PN2vlsBYfkK1YdecbS wPhRuouRk0NCwETi2pReZghbTOLCvfVsXYxcHEICK5gkGub+BksIC+hKnPi3H8zmFTCWWHPr HQuIzSyQIPFo4U6wOJuAisS3y3eZQGxOAWuJP4e+MILYLAKqEj/23maEqNeTeDJ1LSvEHBuJ y91f2UFsIQEriYb3c9lAbBGgmndXD7JDHCQv0fL1DtsERr5ZSFbPQrIawtaWWLbwNZDNAWTr SExeyIgqDGF/PH+EaQEj2ypGwaLUnMRKQzO9xIKCnFS95PzcTYygwG0oNN/BuP2v3CFGAQ5G JR7eRYkL/IRYE8uKK3MPMUpwMCuJ8L4uAArxpiRWVqUW5ccXleakFh9ilOZgURLnFeqZ6yck kJ5YkpqdmlqQWgSTZeLglGpgzJ91MvHe4rj3j84uPmz8mn2uS0jQXf6PPzfzaHkfezPliuy/ 9hvRZ9dM7hUUdwqSdZcROsf05kZx5vNzv/a0rb9SJvhl+7/jVuL9EhanFI6cEtELbrb0W/5z tZpEXct5HbXtGWpbOF8nFzr/DUl7sPHKJWalCUyvWBfwib5kOhPB4XNGa7qNjhJLcUaioRZz UXEiAHzOD91YAgAA
Cc: pcp@ietf.org
Subject: Re: [pcp] suggested external address
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, 20 Oct 2011 21:56:24 -0000

--Boundary_(ID_m/olMHTbp+v8M0nuXvQ8bA)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

On Oct 20, 2011, at 2:49 PM, Francis Dupont wrote:
> 
> - suggested external address == 0, suggested external port == 0: fail with MALFORMED_OPTION

This shouldn't fail wth MALFORMED_OPTION.  If the PCP server is prepared to map all of the protocol's port numbers to the private address for a suitable external address, then it should succeed.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




--Boundary_(ID_m/olMHTbp+v8M0nuXvQ8bA)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Oct 20, 2011, at 2:49 PM, Francis Dupont =
wrote:</div><blockquote type=3D"cite"><br =
class=3D"Apple-interchange-newline"></blockquote><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">- suggested =
external address =3D=3D 0, suggested external port =3D=3D 0:&nbsp;fail =
with MALFORMED_OPTION<br></span></blockquote></div><br><div>This =
shouldn't fail wth MALFORMED_OPTION. &nbsp;If the PCP server is prepared =
to map all of the protocol's port numbers to the private address for a =
suitable external address, then it should =
succeed.</div><div><br></div><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Gill Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
12px; "><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><br =
class=3D"Apple-interchange-newline">--</span></span></div><div =
style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">james woodyatt &lt;<a =
href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&gt;</span></span></span></=
div><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">member of technical staff, core os =
networking</span></span></span></div><br =
class=3D"Apple-interchange-newline" style=3D"font-size: 11px; =
font-family: Geneva; "></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Boundary_(ID_m/olMHTbp+v8M0nuXvQ8bA)--

From internet-drafts@ietf.org  Fri Oct 21 12:26:47 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 CE4BB21F8B31; Fri, 21 Oct 2011 12:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ddwg-ZU0UYtm; Fri, 21 Oct 2011 12:26:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68BD621F8B23; Fri, 21 Oct 2011 12:26:47 -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.61
Message-ID: <20111021192647.15411.29692.idtracker@ietfa.amsl.com>
Date: Fri, 21 Oct 2011 12:26:47 -0700
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-base-16.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, 21 Oct 2011 19:26:48 -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-16.txt
	Pages           : 81
	Date            : 2011-10-21

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


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pcp-base-16.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-16.txt

From dwing@cisco.com  Fri Oct 21 12:34: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 9A01021F8B40 for <pcp@ietfa.amsl.com>; Fri, 21 Oct 2011 12:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.442
X-Spam-Level: 
X-Spam-Status: No, score=-105.442 tagged_above=-999 required=5 tests=[AWL=1.157, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qkE0+hwUUuXC for <pcp@ietfa.amsl.com>; Fri, 21 Oct 2011 12:34:16 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id F281221F8B4C for <pcp@ietf.org>; Fri, 21 Oct 2011 12:34:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=763; q=dns/txt; s=iport; t=1319225656; x=1320435256; h=from:to:subject:date:message-id:mime-version: content-transfer-encoding; bh=oqE0LATxdm2TvSXxjrizSuMVLN3ZT6CEaIr9wY51xV0=; b=kQgcaVP0LNzNPTS4XNrJQrFdsodfFXNwpOqr+BvZNg7Q5e9gYHQRhxkK YMqFMEq5iOHHFZxk47ccZLXjBgXAIDsPVZPOvIKkMyeKBpq0KSlVZqB5C akMcHHgEGAp4vraX67MZpyoukWK2sJWRWAxRMdKUgdXmdUxs3R+v9+q9s 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkEHANPIoU6rRDoG/2dsb2JhbABDmiOBKY1TgQWBdQgKARcQTAUYUCMcAQQeF4dmlBKBJgGeN4hABIgDnXg
X-IronPort-AV: E=Sophos;i="4.69,387,1315180800";  d="scan'208";a="9471852"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 21 Oct 2011 19:34:11 +0000
Received: from dwingWS ([10.21.73.154]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9LJYAcA007546 for <pcp@ietf.org>; Fri, 21 Oct 2011 19:34:10 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <pcp@ietf.org>
Date: Fri, 21 Oct 2011 12:34:10 -0700
Message-ID: <09b701cc9028$6841b510$38c51f30$@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: AcyQKGgDndM6UXgvToKSinP33dkQ+w==
Content-Language: en-us
Subject: [pcp] pcp-base-16 posted
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, 21 Oct 2011 19:34:16 -0000

I just posted -16 with the following changes:

   o  fixed mistake in PCP request format (had 32 bits of extraneous
      fields)
   o  Allow MAP to request all ports (port=0) for a specific protocol
      (protocol!=0), for the same reason we added support for all ports
      (port=0) and all protocols (protocol=0) in -15
   o  corrected text on Client Processing a Response related to
      receiving ADDRESS_MISMATCH error.
   o  updated Epoch text.
   o  Added text that MALFORMED_REQUEST is generated for MAP if Protocol
      is zero but Internal Port is non-zero.

Our last WGLC was against -13.  Diffs between -13 and the current document
are:
<http://tools.ietf.org/rfcdiff?url1=draft-ietf-pcp-base-13&url2=draft-ietf-p
cp-base>

-d



From adurand@juniper.net  Fri Oct 21 12:34:16 2011
Return-Path: <adurand@juniper.net>
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 DECA321F8B40 for <pcp@ietfa.amsl.com>; Fri, 21 Oct 2011 12:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level: 
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w6gkEjXR+iFH for <pcp@ietfa.amsl.com>; Fri, 21 Oct 2011 12:34:16 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 248AC21F8BA6 for <pcp@ietf.org>; Fri, 21 Oct 2011 12:34:16 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP;  Fri, 21 Oct 2011 12:34:16 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Fri, 21 Oct 2011 12:34:08 -0700
From: Alain Durand <adurand@juniper.net>
To: "pcp@ietf.org" <pcp@ietf.org>
Date: Fri, 21 Oct 2011 12:34:05 -0700
Thread-Topic: WG last call on draft-ietf-pcp-base-16.txt
Thread-Index: AcyQKGZJuyAAeDyvQ92Z+NnAeZgAYQ==
Message-ID: <9B2444EE-1C2C-4B4F-8BCD-C7D30BA050E6@juniper.net>
References: <20111021192647.15411.29692.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [pcp] WG last call on draft-ietf-pcp-base-16.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, 21 Oct 2011 19:34:17 -0000

VGhlIFBDUCB3ZyBjaGFpcnMgd291bGQgbGlrZSB0byBpc3N1ZSBhIG9uZSB3ZWVrIHdnIGxhc3Qg
Y2FsbCBvbiBkcmFmdC1pZXRmLXBjcC1iYXNlLTE2Lg0KDQpMYXN0IGNhbGwgZW5kcyBGcmlkYXkg
T2N0b2JlciAyOHRoIGF0IDVwbSBFU1QuDQoNCkFsYWluICYgRGF2ZQ0KDQpTZW50IGZyb20gbXkg
aVBob25lDQoNCkJlZ2luIGZvcndhcmRlZCBtZXNzYWdlOg0KDQpGcm9tOiAiaW50ZXJuZXQtZHJh
ZnRzQGlldGYub3JnPG1haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+IiA8aW50ZXJuZXQt
ZHJhZnRzQGlldGYub3JnPG1haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+Pg0KRGF0ZTog
T2N0b2JlciAyMSwgMjAxMSAzOjI2OjQ3IFBNIEVEVA0KVG86ICJpLWQtYW5ub3VuY2VAaWV0Zi5v
cmc8bWFpbHRvOmktZC1hbm5vdW5jZUBpZXRmLm9yZz4iIDxpLWQtYW5ub3VuY2VAaWV0Zi5vcmc8
bWFpbHRvOmktZC1hbm5vdW5jZUBpZXRmLm9yZz4+DQpDYzogInBjcEBpZXRmLm9yZzxtYWlsdG86
cGNwQGlldGYub3JnPiIgPHBjcEBpZXRmLm9yZzxtYWlsdG86cGNwQGlldGYub3JnPj4NClN1Ympl
Y3Q6IFtwY3BdIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtcGNwLWJhc2UtMTYudHh0DQoNCkEgTmV3
IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURy
YWZ0cyBkaXJlY3Rvcmllcy4gVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUgUG9ydCBD
b250cm9sIFByb3RvY29sIFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYuDQoNCiAgIFRpdGxlICAg
ICAgICAgICA6IFBvcnQgQ29udHJvbCBQcm90b2NvbCAoUENQKQ0KICAgQXV0aG9yKHMpICAgICAg
IDogRGFuIFdpbmcNCiAgICAgICAgICAgICAgICAgICAgICAgICBTdHVhcnQgQ2hlc2hpcmUNCiAg
ICAgICAgICAgICAgICAgICAgICAgICBNb2hhbWVkIEJvdWNhZGFpcg0KICAgICAgICAgICAgICAg
ICAgICAgICAgIFJlaW5hbGRvIFBlbm5vDQogICAgICAgICAgICAgICAgICAgICAgICAgUGF1bCBT
ZWxraXJrDQogICBGaWxlbmFtZSAgICAgICAgOiBkcmFmdC1pZXRmLXBjcC1iYXNlLTE2LnR4dA0K
ICAgUGFnZXMgICAgICAgICAgIDogODENCiAgIERhdGUgICAgICAgICAgICA6IDIwMTEtMTAtMjEN
Cg0KICBUaGUgUG9ydCBDb250cm9sIFByb3RvY29sIGFsbG93cyBhbiBJUHY2IG9yIElQdjQgaG9z
dCB0byBjb250cm9sIGhvdw0KICBpbmNvbWluZyBJUHY2IG9yIElQdjQgcGFja2V0cyBhcmUgdHJh
bnNsYXRlZCBhbmQgZm9yd2FyZGVkIGJ5IGENCiAgbmV0d29yayBhZGRyZXNzIHRyYW5zbGF0b3Ig
KE5BVCkgb3Igc2ltcGxlIGZpcmV3YWxsLCBhbmQgYWxzbyBhbGxvd3MNCiAgYSBob3N0IHRvIG9w
dGltaXplIGl0cyBvdXRnb2luZyBOQVQga2VlcGFsaXZlIG1lc3NhZ2VzLg0KDQoNCkEgVVJMIGZv
ciB0aGlzIEludGVybmV0LURyYWZ0IGlzOg0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1k
cmFmdHMvZHJhZnQtaWV0Zi1wY3AtYmFzZS0xNi50eHQNCg0KSW50ZXJuZXQtRHJhZnRzIGFyZSBh
bHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0KZnRwOi8vZnRwLmlldGYub3JnL2lu
dGVybmV0LWRyYWZ0cy8NCg0KVGhpcyBJbnRlcm5ldC1EcmFmdCBjYW4gYmUgcmV0cmlldmVkIGF0
Og0KZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLXBjcC1iYXNl
LTE2LnR4dA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
CnBjcCBtYWlsaW5nIGxpc3QNCnBjcEBpZXRmLm9yZzxtYWlsdG86cGNwQGlldGYub3JnPg0KaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wY3ANCg==

From bruno_henrik@hotmail.com  Fri Oct 21 14:56:01 2011
Return-Path: <bruno_henrik@hotmail.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 5B90B21F8696 for <pcp@ietfa.amsl.com>; Fri, 21 Oct 2011 14:56:01 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jkVWY1xcUDVv for <pcp@ietfa.amsl.com>; Fri, 21 Oct 2011 14:56:00 -0700 (PDT)
Received: from snt0-omc3-s3.snt0.hotmail.com (snt0-omc3-s3.snt0.hotmail.com [65.55.90.142]) by ietfa.amsl.com (Postfix) with ESMTP id A8AEB21F8677 for <pcp@ietf.org>; Fri, 21 Oct 2011 14:56:00 -0700 (PDT)
Received: from SNT132-W11 ([65.55.90.137]) by snt0-omc3-s3.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 21 Oct 2011 14:55:59 -0700
Message-ID: <SNT132-W111E331553D22FE900DFE3E7E80@phx.gbl>
X-Originating-IP: [186.215.93.195]
From: Bruno Faria <bruno_henrik@hotmail.com>
To: <pcp@ietf.org>
Date: Fri, 21 Oct 2011 19:55:59 -0200
Importance: Normal
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 21 Oct 2011 21:55:59.0695 (UTC) FILETIME=[37E2CDF0:01CC903C]
Subject: [pcp] PCP Protocol - Client side implementation
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, 21 Oct 2011 21:56:01 -0000

Hi all=2C
I wanted to share with you that we have implemented the PCP Protocol on the=
 client side on the Nokia N9 device (http://swipe.nokia.com). Our implement=
ation is based on the Rev 13 the I-D. We're ready to run interop tests with=
 any PCP Server implementation=2C so if any of you has already the PCP Serv=
er running of version 13=2C please contact me. Maybe we can have a good opp=
ortunity to show the protocol in action at Taipei.
Cheers=2C
- Bruno Faria 		 	   		  =

From Francis.Dupont@fdupont.fr  Sat Oct 22 03:32:47 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 5239221F8A55 for <pcp@ietfa.amsl.com>; Sat, 22 Oct 2011 03:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level: 
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JyKQTXVEwu3r for <pcp@ietfa.amsl.com>; Sat, 22 Oct 2011 03:32:46 -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 8297021F8A35 for <pcp@ietf.org>; Sat, 22 Oct 2011 03:32:46 -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 p9MAWgwc040260; Sat, 22 Oct 2011 12:32:42 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110221032.p9MAWgwc040260@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 20 Oct 2011 14:46:28 PDT. <05ad01cc8f71$b959ac80$2c0d0580$@com> 
Date: Sat, 22 Oct 2011 12:32:42 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] draft-ietf-pcp-base-15 posted
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, 22 Oct 2011 10:32:47 -0000

 In your previous mail you wrote:

   > => get back (from base 12):
   > 
   >    6  PROCESSING_ERROR, server encountered an error after parsing while
   >       attempting to process a request.
   > 
   > (of course the important detail is the "after parsing")
   
   The change log at
   http://tools.ietf.org/html/draft-ietf-pcp-base-15#appendix-B.3
   says it was removed because:
   
      o  removed PROCESSING_ERROR error, which was too similar to
         MALFORMED_REQUEST.
   
=> this argument is pretty wrong: MALFORMED_REQUEST is for error
in the parsing because the client sent something bad, PROCESSING_ERROR
is for error after the parsing because even the request is valid
for some reasons the server failed to process it.

   I don't know how to write the important detail to differentiate
   between the two errors for the server or for what the client would
   do.
   
=> for the server it is easy: just apply the "after parsing" vs
"during parsing" criterion. For the client it is less easy because
it just knows in the PROCESSING_ERROR error case something goes wrong
and it has no clear recovery way. But it is the case for any user
defined error too so the choice is to standardize this error or
to get all server implementations add it as an extended error
(i.e., code 128 & co). But we have already discuss this so
this has just to be addressed so this will be removed from the
open issue list.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 22 03:39:34 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 565E521F8B48 for <pcp@ietfa.amsl.com>; Sat, 22 Oct 2011 03:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.519
X-Spam-Level: 
X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50-9iXRNeKJe for <pcp@ietfa.amsl.com>; Sat, 22 Oct 2011 03:39:33 -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 83B3321F8BBC for <pcp@ietf.org>; Sat, 22 Oct 2011 03:39:33 -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 p9MAdRMD040709; Sat, 22 Oct 2011 12:39:27 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110221039.p9MAdRMD040709@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: james woodyatt <jhw@apple.com>
In-reply-to: Your message of Thu, 20 Oct 2011 14:55:58 PDT. <CA759C11-366E-476B-85BC-ED8AD14F852D@apple.com> 
Date: Sat, 22 Oct 2011 12:39:27 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] suggested external address
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, 22 Oct 2011 10:39:34 -0000

 In your previous mail you wrote:

   > - suggested external address == 0, suggested external port == 0:
       fail with MALFORMED_OPTION
   
=> please remember this is when an explicit PREFER_FAILURE option is
present, so it is a syntax issue.

   This shouldn't fail wth MALFORMED_OPTION.  If the PCP server is
   prepared to map all of the protocol's port numbers to the private
   address for a suitable external address, then it should succeed.
   
=> my answer is if the client wants this it MUST NOT add a
PREFER_FAILURE option. And BTW it is already specified as it:

   If an Option with value less than 128 exists (i.e., mandatory to
   process) but that Option does not make sense (e.g., the
   PREFER_FAILURE Option is included in a request with lifetime=0), the
   request is invalid and generates a MALFORMED_OPTION error.

so PREFER_FAILURE makes sense only when the request can fail because
of the suggested external address and port, for instance it doesn't
make sense if both are not specified, in a MAP delete, in a PEER, etc.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Mon Oct 24 08:22:17 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 9660621F8EA0 for <pcp@ietfa.amsl.com>; Mon, 24 Oct 2011 08:22:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CCpBeVPqxtuE for <pcp@ietfa.amsl.com>; Mon, 24 Oct 2011 08:22:14 -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 7859821F8EAB for <pcp@ietf.org>; Mon, 24 Oct 2011 08:22:11 -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 p9OFM8xd033562 for <pcp@ietf.org>; Mon, 24 Oct 2011 17:22:08 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110241522.p9OFM8xd033562@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Mon, 24 Oct 2011 17:22:08 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] base 16 review (1)
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, 24 Oct 2011 15:22:17 -0000

I began the base 16 review, here are my comments up to 7.3 page 21.

 - ToC page 3:
   12.4. Source Address and Port in PCP Header ->
   12.4. Source Address in PCP Header 
 (the source port is no longer in the header, BTW I'd like
  to understand why. IMHO it is just a simplication as the
  address is enough to detect unexpected on-path NATs)

 - 1 page 5 (not a comment about the document itself):
  an interception PCP proxy (cf draft-penno-pcp-nested-nat-01.txt)
  is an ALG (as it is commented) so is *bad*!

 - 2.1 page 3: [I-D.miles-behave-l2nat] points to an expired draft?
  Is it just because someone forgot to refresh it or for a more
  annoying reason?

 - 3 page 7 (Remote Host): Remote Host -> Remote Peer Host
  (remote host is used once, remote peer 52 times :-)

 - 3 page 8 (Mapping Types): web page -> web portal
  (just a suggestion, the term "web page" is very poor IMHO)

 - 3 page 9 (Mapping Types, at the end of the item, suggestion):
      ... they behave exactly the same as an
      explicit dynamic mapping.
   ->
      ... they behave exactly the same as
      explicit dynamic mappings.

 - 5 page 11: from a legal IPv6 address, -> from a native IPv6 address,
  (IPv4 mapped IPv6 addresses are legal, BTW native is better but not
   so good as it suggests it couldn't be a 6to4 address, seeking for
   a better term...)

 - 6.1 page 13 (end of 6.1): please remove the second / extra

   Reserved:  16 reserved bits, MUST be sent as 0 and MUST be ignored
      when received.

 - 6.3 page 15: 1024-4*number_of_options -> 1020-4*number_of_options
  (i.e., please add the UNPROCESSED option header too)

 - 6.4 page 18 (NO_RESOURCES): I have a concern with:
      ... This can be used as a catch-all
      error, should no other error message be suitable.

   by itself it is not a bad idea to provide a catch-all but
   NO_RESOURCES has a special processing, cf. 7.3 page 19:

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

   So we really need the PROCESSING_ERROR...

 - 6.4 page 18 (CANNOT_PROVIDE_EXTERNAL_PORT): please remember we
  still have an open issue about this

 - 6.4 page 18 (CANNOT_PROVIDE_EXTERNAL_PORT): protcool -> protocol

 - 6.4 page 18 (ADDRESS_MISMATCH): *3* fixes

   12 ADDRESS_MISMATCH: the source IP address or port of the request
      packet does not match the contents of the PCP Client's IP Address
      or UDP port.

  ->

   12 ADDRESS_MISMATCH: the source IP address of the request packet
      does not match the content of the PCP Client's IP Address.

 - 7.1 page 19: it is not a concern for me but BTW there is nothing
  about other (i.e., not first) members of the list of PCP Server(s)...

 - 7.2 page 20: between

     If the length of the message exceeds 1024 octets or is not a multiple

   and

    The PCP server compares the IP address (from the IP header) with the

   a sentence is needed for requests longer than 4 octets but shorter
   than the 6.1/Figure 2 request header, with of course a
   MALFORMED_REQUEST error. Note the response has the 24 octet check.

  - 7.3 page 21: remove from the processing a response:

   If the PCP Client's IP Address and PCP Client's Port fields of the
   PCP response header do not match the source address and port of the
   request, it indicates the presence of a NAT between the PCP client
   and PCP server.  If they don't match, then the PCP client (or the
   user on the client host) MUST ensure that an appropriate NAT mapping
   is created on the intervening NAT(s) (e.g., using UPnP IGD, NAT-PMP,
   or manual configuration), otherwise, the PCP-installed mapping will
   be ineffective.

Thanks

Francis.Dupont@fdupont.fr

From rja.lists@gmail.com  Tue Oct 25 07:24:09 2011
Return-Path: <rja.lists@gmail.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 7928821F84E1 for <pcp@ietfa.amsl.com>; Tue, 25 Oct 2011 07:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6N0JCYxXCKwr for <pcp@ietfa.amsl.com>; Tue, 25 Oct 2011 07:24:08 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 964C721F8560 for <pcp@ietf.org>; Tue, 25 Oct 2011 07:24:08 -0700 (PDT)
Received: by wwe6 with SMTP id 6so600212wwe.13 for <pcp@ietf.org>; Tue, 25 Oct 2011 07:24:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:date:subject:to :message-id:mime-version:x-mailer; bh=9bfRJ7bfETylQcnt78j3qmY+/+DvAKNPNBv1d91+XIY=; b=GIZDnAy4R6FPoFdqE2nbpMCsHz37KhO2bWuLAXGqtLfFJtbCX7+Xfue12s0k0vIkwV xbdSnyDmt8MAIAFs064z7ze1UDjSnwEJK80hw+SCUnP6FnfpXI7pjcgdHfItusznqvMI 2MuWXHJtQJ4WXeCIJ75u0PhSuo9A4ABIOY88o=
Received: by 10.227.197.20 with SMTP id ei20mr3950814wbb.26.1319552647838; Tue, 25 Oct 2011 07:24:07 -0700 (PDT)
Received: from dragonfly.cs.ucl.ac.uk (dragonfly.cs.ucl.ac.uk. [128.16.64.246]) by mx.google.com with ESMTPS id es5sm45373529wbb.11.2011.10.25.07.24.05 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 25 Oct 2011 07:24:06 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 25 Oct 2011 10:24:03 -0400
To: pcp@ietf.org
Message-Id: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
X-Mailman-Approved-At: Tue, 25 Oct 2011 08:11:58 -0700
Subject: [pcp]  WG last call on draft-ietf-pcp-base-16.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, 25 Oct 2011 14:24:09 -0000

> The PCP wg chairs would like to issue a one week wg last call
> on draft-ietf-pcp-base-16.
> 
> Last call ends Friday October 28th at 5pm EST.
> 
> Alain & Dave

(I apologise for the delayed reaction to the WG Last Call.
I only have intermittent network access at present.)

I object to this document moving forward on grounds that 
while this WG's primary objective is to standardise 
NAT-PMP/uPnP, an important commonly deployed operational 
capability of NAT-PMP is being omitted from this document.

There is significant operational experience with the 
"Rapid Recovery" capability of NAT-PMP.  It works well 
in the field.  Text exists in draft-cheshire-pcp-recovery-01, 
which is remarkably brief for an I-D, so there is no
work required to create text.

When this was discussed in early April this year on the 
IETF PCP mailing list, there was a single non-specific
and not-obviously-technical concern expressed by Rainaldo 
Penno on 1st April 2011.

That concern was addressed and seemed fully resolved by
Stuart Cheshire's clarification also on the IETF PCP
mailing list (posted the very next day).

Rainaldo did not follow up with any disagreement or concern
to Start's note of 2nd April, so he appears to be happy.  

No one else has expressed any concern about the Rapid
Recovery capability to the IETF PCP list.  


BOTTOM LINE:

I've reviewed the IETF PCP list archives and can't find 
any evidence of an unresolved concern about this feature.

So a reasonable member of this WG has no reason to believe 
the Rapid Recovery feature is controversial in any way, 
has any unresolved technical concern, and would not be 
included as part of the base specification (or at minimum 
placed into WG Last Call at the same time as the PCP base 
specification so they could proceed together).



PROPOSED RESOLUTION:

I see 2 different ways that my objection can be resolved.
Either one is fine with me.  Each seems quite simple.


A) IETF PCP WG Chairs place draft-cheshire-pcp-recovery-02 into
   WG Last Call immediately for publication on the IETF standards 
   track, with the document to be marked as an "Update" to the 
   draft-ietf-pcp-base-16.txt document.

or

B) IETF PCP WG Chairs suspend the current WG Last Call, 
   fold the text from draft-cheshire-pcp-recovery-02 into 
   a new version of the draft-ietf-pcp-base-* document, 
   and restart the WG Last Call on that revised version.


Yours, 

Ran Atkinson


From rpenno@juniper.net  Tue Oct 25 12:55:25 2011
Return-Path: <rpenno@juniper.net>
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 69DAF11E8080 for <pcp@ietfa.amsl.com>; Tue, 25 Oct 2011 12:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level: 
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ObNKPzCmNdSq for <pcp@ietfa.amsl.com>; Tue, 25 Oct 2011 12:55:24 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id 8C5AA11E807F for <pcp@ietf.org>; Tue, 25 Oct 2011 12:55:23 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP;  Tue, 25 Oct 2011 12:55:24 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 25 Oct 2011 12:47:18 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Tue, 25 Oct 2011 15:47:17 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: RJ Atkinson <rja.lists@gmail.com>, "pcp@ietf.org" <pcp@ietf.org>
Date: Tue, 25 Oct 2011 15:47:15 -0400
Thread-Topic: [pcp]  WG last call on draft-ietf-pcp-base-16.txt
Thread-Index: AcyTKHP9xqReWx8iSfK/YMNyna+eqwAJnFEU
Message-ID: <CACC6053.56439%rpenno@juniper.net>
In-Reply-To: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 25 Oct 2011 19:55:25 -0000

Hello RJ,

I did not follow up due to the fact that draft-cheshire-pcp-recovery-01
views things from a CPE/home perspective where multicast is pervasive. As
you point out, it is trying to recreate NAT-PMP's functionality.

My objection to draft-cheshire-pcp-recovery-01 is that relying on multicast
in service provider networks is not practical - although fine for home
networks.

Thanks,

Reinaldo



On 10/25/11 7:24 AM, "RJ Atkinson" <rja.lists@gmail.com> wrote:

>> The PCP wg chairs would like to issue a one week wg last call
>> on draft-ietf-pcp-base-16.
>>=20
>> Last call ends Friday October 28th at 5pm EST.
>>=20
>> Alain & Dave
>=20
> (I apologise for the delayed reaction to the WG Last Call.
> I only have intermittent network access at present.)
>=20
> I object to this document moving forward on grounds that
> while this WG's primary objective is to standardise
> NAT-PMP/uPnP, an important commonly deployed operational
> capability of NAT-PMP is being omitted from this document.
>=20
> There is significant operational experience with the
> "Rapid Recovery" capability of NAT-PMP.  It works well
> in the field.  Text exists in draft-cheshire-pcp-recovery-01,
> which is remarkably brief for an I-D, so there is no
> work required to create text.
>=20
> When this was discussed in early April this year on the
> IETF PCP mailing list, there was a single non-specific
> and not-obviously-technical concern expressed by Rainaldo
> Penno on 1st April 2011.
>=20
> That concern was addressed and seemed fully resolved by
> Stuart Cheshire's clarification also on the IETF PCP
> mailing list (posted the very next day).
>=20
> Rainaldo did not follow up with any disagreement or concern
> to Start's note of 2nd April, so he appears to be happy.
>=20
> No one else has expressed any concern about the Rapid
> Recovery capability to the IETF PCP list.
>=20
>=20
> BOTTOM LINE:
>=20
> I've reviewed the IETF PCP list archives and can't find
> any evidence of an unresolved concern about this feature.
>=20
> So a reasonable member of this WG has no reason to believe
> the Rapid Recovery feature is controversial in any way,
> has any unresolved technical concern, and would not be
> included as part of the base specification (or at minimum
> placed into WG Last Call at the same time as the PCP base
> specification so they could proceed together).
>=20
>=20
>=20
> PROPOSED RESOLUTION:
>=20
> I see 2 different ways that my objection can be resolved.
> Either one is fine with me.  Each seems quite simple.
>=20
>=20
> A) IETF PCP WG Chairs place draft-cheshire-pcp-recovery-02 into
>    WG Last Call immediately for publication on the IETF standards
>    track, with the document to be marked as an "Update" to the
>    draft-ietf-pcp-base-16.txt document.
>=20
> or
>=20
> B) IETF PCP WG Chairs suspend the current WG Last Call,
>    fold the text from draft-cheshire-pcp-recovery-02 into
>    a new version of the draft-ietf-pcp-base-* document,
>    and restart the WG Last Call on that revised version.
>=20
>=20
> Yours,=20
>=20
> Ran Atkinson
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From pselkirk@isc.org  Tue Oct 25 21:44:45 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 ED12811E808B for <pcp@ietfa.amsl.com>; Tue, 25 Oct 2011 21:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RlObEQIO0rDG for <pcp@ietfa.amsl.com>; Tue, 25 Oct 2011 21:44:45 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 5933E11E8082 for <pcp@ietf.org>; Tue, 25 Oct 2011 21:44:42 -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.ams1.isc.org (Postfix) with ESMTPS id 250895F98A2; Wed, 26 Oct 2011 04:44:29 +0000 (UTC) (envelope-from pselkirk@isc.org)
Received: by bikeshed.isc.org (Postfix, from userid 10300) id 6E6A2216C6B; Wed, 26 Oct 2011 04:44:22 +0000 (UTC)
From: Paul Selkirk <pselkirk@isc.org>
To: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com> (message from RJ Atkinson on Tue, 25 Oct 2011 10:24:03 -0400)
References: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com>
Date: Wed, 26 Oct 2011 04:44:22 +0000
Message-ID: <s1v4nywwee1.fsf@bikeshed.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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: Wed, 26 Oct 2011 04:44:46 -0000

So what you're objecting to is that draft-cheshire-pcp-recovery is not
part of the base PCP spec.

It's an optimization. PCP will work without it. PCP will work better
with it, in certain deployment scenarios (i.e. where IPv4 multicast
infrastructure is present, and the NAT is restarting often enough to be
an operational consideration).

OTOH, a) if we define it for IPv4 multicast, someone will surely and
immediately request it for IPv6 multicast; and b) the deployment
scenarios that PCP is looking at are CGN (DS-Lite, NAT444, or NAT64),
where NAT restarts should be much less frequent than in the home.

Also, c) we're under significant pressure from the v6ops WG to publish
the PCP base spec, because rfc6204bis supposedly depends on it.

That said, I would like to hear more about why you consider this such an
integral part of the protocol that we cannot publish the base spec
without it.

				paul

From Francis.Dupont@fdupont.fr  Wed Oct 26 05:44:07 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 5FB5021F8B57 for <pcp@ietfa.amsl.com>; Wed, 26 Oct 2011 05:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ItUEaH430RUA for <pcp@ietfa.amsl.com>; Wed, 26 Oct 2011 05:44:06 -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 A8EEE21F8B56 for <pcp@ietf.org>; Wed, 26 Oct 2011 05:44:05 -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 p9QCi49O098522 for <pcp@ietf.org>; Wed, 26 Oct 2011 14:44:04 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110261244.p9QCi49O098522@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Wed, 26 Oct 2011 14:44:04 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] base 16 review (2)
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, 26 Oct 2011 12:44:07 -0000

Second part of my editorial (*) review comments,
up to 11.3 / page 56.
(*) I have two concerns I am discussing internally which are clearly
not editorial at all.

(from 7.3 page 21 excluded)

 - 7.5 page 22: please choose between '1' and 'one', as I prefer
  the work this gives:

   by 1 every second -> by one every second

 - 7.5 page 23: I liked the one hour max drift rule, using the
  same style it gives an additional member of the if 'or':
  or 3600 < abs(server_delta - client_delta)

 - 7.6 page 24: perhaps from an older edit?

  these first two octets -> this first octet

 - 8 page 27: the paragraph:

   Note that PCP requests containing the MAP or PEER Opcodes cannot
   delete or shorten the lifetime of an existing implicit mapping for
   the indicated internal address and port.  Conceptually implicit and
   explicit mappings are different "layers" in the NAT forwarding state
   database.

  is in contradiction with the implementation-dependent text in
  the PEER opcode description. Note IMHO that text is wrong so I cite
  this paragraph only for the case the WG decision will be reversed.

 - 9 page 35: I suggest to move the text about ICMP from 9.5 to here:

   their MAP request, to ensure that no other clients on the same
   machine are also listening on the same Internal Port.
 
 moved text

   As a side-effect of creating a mapping, ICMP messages associated with
   the mapping MUST be forwarded (and also translated, if appropriate)
   for the duration of the mapping's lifetime.  This is done to ensure
   that ICMP messages can still be used by hosts, without application
   programmers or PCP client implementations needing to signal PCP
   separately to create ICMP mappings for those flows.

 resuming

   The operation of the MAP Opcode is described in this section.

 - 9.3 page 38: in fact

   ... If
   the requested Lifetime is non-zero, the Internal Port is zero, and
   the Protocol is non-zero, it indicates a request to map all incoming
   traffic for that entire Protocol.

  is valid only for protocols which don't use 16-bit port numbers.
  I don't know if it is a problem, i.e., if the text should be changed.
  IMHO the 9.1 definition of the internal port is clear enough.

 - 9.3 page 39: I suggest to swap the two paragraphs, i.e.:

   If the PCP-controlled device is stateless (that is, it does not
   establish any per-flow state, and simply rewrites the address and/or
   port in a purely algorithmic fashion), the PCP server simply returns
   an answer indicating the external IP address and port yielded by this
   stateless algorithmic translation.  This allows the PCP client to
   learn its external IP address and port as seen by remote peers.
   Examples of stateless translators include stateless NAT64, 1:1 NAT44,
   and NPTv6 [RFC6296], all of which modify addresses but not port
   numbers.

   If an Option with value less than 128 exists (i.e., mandatory to
   process) but that Option does not make sense (e.g., the
   PREFER_FAILURE Option is included in a request with lifetime=0), the
   request is invalid and generates a MALFORMED_OPTION error.

 ->

   If an Option with value less than 128 exists (i.e., mandatory to
   process) but that Option does not make sense (e.g., the
   PREFER_FAILURE Option is included in a request with lifetime=0), the
   request is invalid and generates a MALFORMED_OPTION error.

   If the PCP-controlled device is stateless (that is, it does not
   establish any per-flow state, and simply rewrites the address and/or
   port in a purely algorithmic fashion), the PCP server simply returns
   an answer indicating the external IP address and port yielded by this
   stateless algorithmic translation.  This allows the PCP client to
   learn its external IP address and port as seen by remote peers.
   Examples of stateless translators include stateless NAT64, 1:1 NAT44,
   and NPTv6 [RFC6296], all of which modify addresses but not port
   numbers.

 - 9.3 page 40: I still don't like the last paragraph, I propose:

   If all of the preceding operations were successful (did not generate
   an error response), then the requested mapping is created or
   refreshed as described in the request and a SUCCESS response is
   built.  This SUCCESS response contains the same Opcode as the
   request, but with the "R" bit set.

 ->

   If all of the preceding operations were successful (did not generate
   an error response), then the requested mapping is created or
   refreshed as described in the request and a SUCCESS response is
   built.  All responses, including this SUCCESS response contains
   the same Opcode as the request, but with the "R" bit set.

 - 9.4 page 41: I have a problem with this MUST:

   The PCP client MUST also set a timer or otherwise schedule an event
   to renew the mapping before its lifetime expires.

  due to the (poor) wording this can be read as infinite renewal is
  mandatory. Of course the issue is not in the requirement level,
  I strongly suggest to add a condition like:
 
   When renewal is desired, the PCP client MUST also...

 - 9.5 page 42: the all subscriber mapping delete is not in the list
  (but is in 11.1 page 51 about THIRD_PARTY). IMHO we should add
  a reference to it at the end of:

   o  If both the internal port and protocol are zero, it indicates a
      request to delete all mappings for this Internal Address for all
      transport protocols.  This is useful when a host reboots or joins
      a new network, to clear out prior stale state from the NAT gateway
      before beginning to install new mappings.

  BTW this could fix the missing fact the all subscriber mapping
  requires zero internal port and protocol.

 - 9.5 page 43: as written before about 9, this text has a better place:

   As a side-effect of creating a mapping, ICMP messages associated with
   the mapping MUST be forwarded (and also translated, if appropriate)
   for the duration of the mapping's lifetime.  This is done to ensure
   that ICMP messages can still be used by hosts, without application
   programmers or PCP client implementations needing to signal PCP
   separately to create ICMP mappings for those flows.

 - 9.7 page 44: I have still a concern about:

   Address for cosmetic purposes can achieve that by requesting a short-
   lived mapping and then displaying the resulting External IP Address.
   However, once that mapping expires a subsequent implicit or explicit
   dynamic mapping might be mapped to a different external IP address.

  as it is both pejorative and useless. I strongly suggest to remove it
  (and to keep the rest of 9.7).

 - 10 page 44: I can't see why the v4 is here and BTW it contradicts
  the NAT64 Figure 6 entry where the remote peer is IPv6, so I strongly
  suggest:

   a remote peer's IPv4 -> a remote peer's IP

 - 10 page 44: from the PEER4 and PEER6 time:

   The use of these Opcodes -> The use of this Opcode

 - 10.1 page 45 (Requested Lifetime): I note this as I have a concern
  I am discussing.

 - 10.1 page 46 (twice): the word 'preference' in the two Suggested
  and even the word 'Suggested' itself don't match the implicit
  PREFER_FAILURE semantic.

 - 10.1 page 46 (Remote Peer IP Address): add or replace the trailing

      ... and an IPv4 address is
      represented using the IPv4-mapped address syntax (80 bits of
      zeros, 16 bits of ones, and 32 bits of the IPv4 address).
 
   by a reference to Section 5?

 - 10.2 page 48: IMHO the 'If sent before' and 'If sent after'
  paragraphs should not get a particular indent.

 - 10.2 page 48: please change

  ... will respond with a PCP error.

 ->

  ... will respond with a CANNOT_PROVIDE_EXTERNAL_PORT error.

 - 10.3 page 49: again I note this as I have a concern about it
  I am discussing.

   The PEER Opcode MAY reduce the lifetime of an existing implicit
   dynamic mapping created by PEER; this is implementation-dependent.

  same for:

   Some transport protocols signal the end of a connection (e.g., TCP
   FIN, TCP RST, SCTP SHUTDOWN).  After a successful PEER response is
   sent, the receipt of such a transport-specific message MUST NOT cause
   the mapping to be destroyed.  Rather, the mapping is maintained until
   the PEER-signaled lifetime expires.  If the PCP client wishes to
   terminate the mapping prior to this, it will send a PEER request with
   Lifetime set to 0, which MAY be honored by the PCP server; as stated
   earlier, that is implementation-dependent.

  which BTW says the opposite of the previous paragraph.

 - 10.4 page 50: I suggest:

   inside->outside -> from inside to outside

 - 11.1 page 51: I suggest to consolidate this with 9.5:

      ... If the
      Option Length is zero, there is no Internal IP address for this
      mapping and this indicates "all Internal IPv4 and IPv6 Addresses
      for which this client is authorized" which is used to delete all
      pre-existing mappings with the MAP Opcode.

  and page 52:

   A PCP client can delete all PCP-created explicit dynamic mappings
   (i.e., those created by PCP MAP requests) that it is authorized to
   delete by sending a PCP MAP request including a zero-length
   THIRD_PARTY Option.

  BTW I suggest to add the internal port and protocol MUST be zero
  in this case.

 - 11.2 page 53: at one exception, the text is still about
  an 'external port only' (vs. 'external address and port') version
  of the PREFER_FAILURE option: it clearly needs to be updated!

 - 11.2 pages 53 and 54: again I note this as I have a concern
  I am discussing:

   This Option exists solely for use by UPnP IGD interworking
   ...
   adopt PCP natively and the need for UPnP IGD interworking declines.

 - 11.3 page 54 (remark only): some implementations also filter out
  incoming (i.e., received on the not public-facing interface) packets
  as it doesn't make sense to drop only the traffic one way.
  (BTW the text is correct as the from the Internet way is
   the critical one for the filtering).

 - 11.3 page 55: this text could be improved to take into account
  a possible error response with an UNPROCESSED added option:

      Maximum occurrences: as many as fit within maximum PCP message
      size

 - 11.3 page 55: I have another MALFORMED_OPTION case where the
  address has one bit after its prefix length, i.e., something
  like 192.168.0.0/8. IMHO these cases don't have to be exhaustive
  so it is not a request to add such a thing.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Wed Oct 26 08:07:09 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 68A8121F8772 for <pcp@ietfa.amsl.com>; Wed, 26 Oct 2011 08:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXP8urUipPn9 for <pcp@ietfa.amsl.com>; Wed, 26 Oct 2011 08:07:09 -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 8DB1321F877F for <pcp@ietf.org>; Wed, 26 Oct 2011 08:07:08 -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 p9QF7701007351 for <pcp@ietf.org>; Wed, 26 Oct 2011 17:07:07 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110261507.p9QF7701007351@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Wed, 26 Oct 2011 17:07:07 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] UNPROCESSED with SUCCESS
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, 26 Oct 2011 15:07:09 -0000

In base 16 7.7.1 page 26, UNPROCESSED is defined with:

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

I'd like to relax this to handle a corner case: a MAP request with at least
a FILTER option which matches a static mapping. The meaning is the FILTERs
don't make sense (in particular the MAP request doesn't change them) so
they are unprocessed, but the request still returns a SUCCESS.

BTW there are other solutions but worse, for instance an UNSUPP_OPTION
which suggests the PCP server doesn't support FILTER, and is not a SUCCESS.

Regards

Francis.Dupont@fdupont.fr

PS: I've found inconsistencies in the "May appear in:"'s, my next
message is abound them.

From Francis.Dupont@fdupont.fr  Wed Oct 26 08:16:18 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 4562121F8A56 for <pcp@ietfa.amsl.com>; Wed, 26 Oct 2011 08:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.528
X-Spam-Level: 
X-Spam-Status: No, score=-2.528 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HrFZZYTWF61y for <pcp@ietfa.amsl.com>; Wed, 26 Oct 2011 08:16:17 -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 BAC8021F8906 for <pcp@ietf.org>; Wed, 26 Oct 2011 08:16:15 -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 p9QFGECZ007874 for <pcp@ietf.org>; Wed, 26 Oct 2011 17:16:14 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110261516.p9QFGECZ007874@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Wed, 26 Oct 2011 17:16:14 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] inconsistent options in responses
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, 26 Oct 2011 15:16:18 -0000

With the new option style all options in a PCP request are copied to the
corresponding response, so some "May appear in:" are no longer consistent
so need to be upgrade:

 - 11.1 THIRD_PARTY page 51: small improvement, i.e., replace:

      May appear in: request.  May appear in response only if it
      appeared in the associated request.

  by

      May appear in: request.  MUST appear in response if it
      appeared in the associated request.

 - 11.2 PREFER_FAILURE page 53: copy THIRD_PARTY spec, i.e., replace:

      May appear in: requests

  by

      May appear in: request.  MUST appear in response if it
      appeared in the associated request.

 - 11.3 FILTER page 55: better but I suggest the same, i.e., replace:

      May appear in: requests, and MUST appear in successfully-processed
      responses

  by

      May appear in: request.  MUST appear in response if it
      appeared in the associated request.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Wed Oct 26 08:25: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 1547021F8B80 for <pcp@ietfa.amsl.com>; Wed, 26 Oct 2011 08:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.529
X-Spam-Level: 
X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8TjE3R0evm-t for <pcp@ietfa.amsl.com>; Wed, 26 Oct 2011 08:25: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 2247C21F8B7B for <pcp@ietf.org>; Wed, 26 Oct 2011 08:25: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 p9QFPFhg008402 for <pcp@ietf.org>; Wed, 26 Oct 2011 17:25:15 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110261525.p9QFPFhg008402@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Wed, 26 Oct 2011 17:25:15 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] a remak about 'upgraded'
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, 26 Oct 2011 15:25:19 -0000

In base 16 9.3 page 39:

   ... If an implicit mapping
   already exists for the requested Internal Address and Port, the
   mapping SHOULD be upgraded to an explicit mapping.

the term 'upgraded' is deliberately loose, in fact many things can
happen, for instance:
 - the implicit mapping is promoted to an explicit mapping (works
  well (only?) with EIM and shared external port space)
 - the implicit mapping is deleted and a new explicit mapping is
  created (EDM, the external port will remain the same if external
  port space is shared, i.e., 12.1 1 is not used)
 - the implicit mappings are deleted (because with EDM you can get
  more than one using of course different external ports), etc.

Regards

Francis.Dupont@fdupont.fr

PS: this is NOT a request to change the base spec (I proposed
the term 'upgraded' so you can assume I am fine with it :-).

From Francis.Dupont@fdupont.fr  Wed Oct 26 08:55:34 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 AB5B921F87C2 for <pcp@ietfa.amsl.com>; Wed, 26 Oct 2011 08:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.53
X-Spam-Level: 
X-Spam-Status: No, score=-2.53 tagged_above=-999 required=5 tests=[AWL=0.069,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GPDCJa-QLAgo for <pcp@ietfa.amsl.com>; Wed, 26 Oct 2011 08:55:33 -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 93A4121F8783 for <pcp@ietf.org>; Wed, 26 Oct 2011 08:55:33 -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 p9QFtWrv010137 for <pcp@ietf.org>; Wed, 26 Oct 2011 17:55:32 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110261555.p9QFtWrv010137@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Wed, 26 Oct 2011 17:55:32 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] base 16 review (3/last)
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, 26 Oct 2011 15:55:34 -0000

Here are my editorial comments about base 16 from 12 page 56:

 - 12.2 page 57: I can't find a real case for 'after' in:

   No matter if a NAT is EIM or EDM, it is possible that one (or more)
   implicit dynamic mappings, using the same internal port on the
   Internal Host, might be created before or after a MAP request.

  but is it a problem? IMHO it is not as it is better to document
  impossible cases than to forget possible cases...

 - 12.3 page 57: please at a reference to Stuart's I-D
  [draft-cheshire-pcp-recovery-01.txt]

 - 12.4 page 59: two extra 'and port' in the title and in the text

 - 13.2 page 60 (remark): about quotas they can be per protocol too...

 - 14.1 pages 60 to 62: I have a concern about this because the
  security constraints described here are not compatible with the
  previous (in the specs) operational requirements, i.e., this leads
  to a situation where an implementation can be secure or compliant
  but not both.

 - 14.1.2.2 page 62: I have a problem with the text as it is clearly
  for the DS-Lite encapsulation code when all implementors I know
  the opinion are for the plain mode.
  There are many ways to fix this, IMHO the simplest (so the best?)
  should to move the whole text to the DS-Lite draft and just leave
  a reference.

 - 14.1.2.2 page 62: possible typo in the last sentence:

   DS-Lite's security policies may also permit use of the MAP Opcode.
                                                          ^^^

 - 14.3.3 page 64: (again) I don't like the wording, I propose:

   ... This threat is reduced by using persistent storage of
   explicit dynamic mappings in the PCP server (so it does not lose
   explicit dynamic mapping state), or by ensuring the previous external
   IP address and port cannot be used by another host (e.g., by using a
   different IP address pool).

 ->

   ... This threat is suppressed by using persistent storage of
   explicit dynamic mappings in the PCP server (so it does not lose
   explicit dynamic mapping state), or reduced by ensuring the
   previous external IP address and port cannot be used by another
   host (e.g., by using a different IP address pool).

 (the idea is the second workaround replaced the direct threat by
  a possible denial of service, so they are not equivalent and
  the first should be prefered when applicable)

 - 15.2 page 65: draft-cheshire-pcp-recovery-01.txt uses the
  reserved value 0 but only in response, so I can't see
  whether this is legal or not...

 - 15.3 page 65: the private range was *silently* changed from
  128-254 to 192-254 between drafts 14 and 15 (grrr...!)

 - 17.2 page 68: the IGD reference is obsolete:


   [IGD]      UPnP Gateway Committee, "WANIPConnection:1",
              November 2001, <http://upnp.org/specs/gw/
              UPnP-gw-WANIPConnection-v1-Service.pdf>.

 ->


   [IGD]      UPnP Gateway Committee, "WANIPConnection:2",
              September 2010, <http://upnp.org/specs/gw/
              UPnP-gw-WANIPConnection-v2-Service.pdf>.

Done, regards

Francis.Dupont@fdupont.fr

PS; I could get other remarks or comments from implementing
experience but unfortunately perhaps not before the LC deadline.

From rja.lists@gmail.com  Thu Oct 27 03:11:44 2011
Return-Path: <rja.lists@gmail.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 4E0CD21F8532 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 03:11:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p3Sn-ZSgfYnI for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 03:11:43 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 81E6321F8486 for <pcp@ietf.org>; Thu, 27 Oct 2011 03:11:43 -0700 (PDT)
Received: by wyh22 with SMTP id 22so3093411wyh.31 for <pcp@ietf.org>; Thu, 27 Oct 2011 03:11:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=3Zlqds3JZNz1Y8FPJLTlpZWyEvRWfYsuGW24HYooT1o=; b=nOJFCkXx/pLbNpQXMTuluCkI2xXlVaE5JJuDhOiZ0R9lirJQwtR/u52ujJK9ZVfpqO vP0bOO0FzexWD6XFaLdBc/JF+nAWXGdPbjtOvCPk7139ryoRbLcvlsJckE2cKLTMetlF kvcYzspydh+MUdGa+D/ykuTl9tliSE84h/DGU=
Received: by 10.227.202.70 with SMTP id fd6mr15414744wbb.27.1319710302661; Thu, 27 Oct 2011 03:11:42 -0700 (PDT)
Received: from dragonfly.cs.ucl.ac.uk (dragonfly.cs.ucl.ac.uk. [128.16.64.246]) by mx.google.com with ESMTPS id 11sm8372174wby.15.2011.10.27.03.11.40 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 27 Oct 2011 03:11:41 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <CACC6053.56439%rpenno@juniper.net>
Date: Thu, 27 Oct 2011 06:11:39 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <767C47A8-5566-4122-BE8E-062F2A97C539@gmail.com>
References: <CACC6053.56439%rpenno@juniper.net>
To: pcp@ietf.org
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 27 Oct 2011 10:11:44 -0000

On 25  Oct 2011, at 15:47 , Reinaldo Penno wrote:
> I did not follow up due to the fact that draft-cheshire-pcp-recovery-01
> views things from a CPE/home perspective where multicast is pervasive.
> As you point out, it is trying to recreate NAT-PMP's functionality.

The Rapid Recovery capability is important to a large number 
of service providers and also to a large number of end sites
(academic, enterprise, residential, & other).  

For example, in most cases, the SP's own customers won't be satisfied 
if/when the PCP-capable device develops a fault and it takes a 
long time to recover.  Rapid Recovery is actually quite important 
for most service providers.


> My objection to draft-cheshire-pcp-recovery-01 is that relying
> on multicast in service provider networks is not practical

That claim is provably false as written.  You generalise 
to all service provider deployments, when in fact we all
know that most (possibly all, as you haven't provided any
specific counter-examples yet) SP deployments don't and won't
have any issues with this use of link-local multicasting.

I don't think we've met, but I have extensive Network Engineering 
experience with a multi-continent ISP, specifically including 
access engineering.  So I've got first-hand understanding of the 
SP environment, including a current client that operates a large
SP network on all continents and has a mixture of equipment
(including some from JNPR).  For many many SP deployments, 
I believe for the majority of service providers where PCP is likely 
to be applicable, multicast is available on the client-facing 
interfaces and the approach defined in Stuart Cheshire's I-D 
works fine.

* If you have some other approach to solve the same operational issue,
  please speak up.  I'm open-minded, but the time to put that on the table 
  was really last April.

* Alternately, if you were worried about some specific use case or
  specific narrow deployment model, you could propose some specific
  text to clarify the Rapid Recovery I-D's applicability.  Again,
  this really ought to have been done last April, but better late
  than never.


Yours,

Ran Atkinson







From rja.lists@gmail.com  Thu Oct 27 03:39:48 2011
Return-Path: <rja.lists@gmail.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 2A76121F8A7D for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 03:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nt9aFx4fAg8w for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 03:39:47 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 10DEC21F8A55 for <pcp@ietf.org>; Thu, 27 Oct 2011 03:39:46 -0700 (PDT)
Received: by wyh22 with SMTP id 22so3122801wyh.31 for <pcp@ietf.org>; Thu, 27 Oct 2011 03:39:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=Y4g3lpTLtMsbQZoeR1b9fN4V+ctcuvcGBdL7ALzdiow=; b=P4RubgUrp0UoBhUgJ402FBmp5pnG0hoVjYvJ6hDdXAUAEoYUbvv39bjMOTsxgFUNr+ bQQGGGdDTEI1okH5ym2IaWONxcDbjqt2BTnnA++jio5iXoy8cdYsM6E5H5zHZK1kC5Q0 e0CZ9KMp/3LL8m2A0e4jshEkrstJJssAIKNXw=
Received: by 10.216.36.9 with SMTP id v9mr2585855wea.58.1319711986180; Thu, 27 Oct 2011 03:39:46 -0700 (PDT)
Received: from dragonfly.cs.ucl.ac.uk (dragonfly.cs.ucl.ac.uk. [128.16.64.246]) by mx.google.com with ESMTPS id es5sm8524272wbb.11.2011.10.27.03.39.43 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 27 Oct 2011 03:39:45 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <s1v4nywwee1.fsf@bikeshed.isc.org>
Date: Thu, 27 Oct 2011 06:39:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <58C8AD88-589C-4ECE-8041-A0B461CE8EDD@gmail.com>
References: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com> <s1v4nywwee1.fsf@bikeshed.isc.org>
To: pcp@ietf.org
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 27 Oct 2011 10:39:48 -0000

On 26  Oct 2011, at 00:44 , Paul Selkirk wrote:
> So what you're objecting to is that draft-cheshire-pcp-recovery is not
> part of the base PCP spec.

That is not precisely correct; instead I object the absence of some=20
reasonable approach to Rapid Recovery being standardised/specified
at the same time as the base specification.

draft-cheshire-pcp-recovery happens to be the only proposal on the=20
table for Rapid Recovery that I'm aware of.  There is operational
experience indicating it works well -- and that its presence is
operationally important in real-world deployments.  If someone has
a different approach to propose, ideally one that also has operational
experience supporting that approach, there was ample time to present=20
that during the past year -- and such an alternate proposal really
ought to have been offered in April when this topic arose on the=20
WG mailing list.  Still, better to propose something late than never.

My original note outlined two different possible approaches=20
to resolving my objection.  If someone wants to propose an=20
alternative resolution -- one that will also specify a Rapid Recovery=20
capability at the same time as the base specification, then I'm all =
ears.

> It's an optimization. PCP will work without it. PCP will work better
> with it, in certain deployment scenarios (i.e. where IPv4 multicast
> infrastructure is present, and the NAT is restarting often enough to =
be
> an operational consideration).

The above is one view. =20

My own view, based on operational experience with uPnP and NAT-PMP is =
that=20
PCP without Rapid Recovery will NOT work sufficiently well to be viable=20=

in real world deployments (this includes, but is not limited to, SP =
deployments).

> OTOH, a) if we define it for IPv4 multicast, someone will surely
> and immediately request it for IPv6 multicast;

If true, that's a trivial edit that could be made within a day. =20
The IPv6 all-nodes link-local multicast address was defined=20
over a decade ago and is widely supported in environments=20
where native IPv6 is deployed.

> and b) the deployment scenarios that PCP is looking at are CGN
> (DS-Lite, NAT444, or NAT64),=20

That very narrow reading of which deployment scenarios are within scope
is NOT consistent with the WG Charter, which is posted online here:
	<http://www.ietf.org/dyn/wg/charter/pcp-charter>

The charter is NOT limited to CGN cases, but instead is very broadly
written to include ALL use cases involving either NAT, Firewall, or =
both.

In any case, many existing CGN deployments and also many other
NAT/firewall deployments support the IP multicast approach defined=20
in the current Rapid Recovery draft -- and those deployments are=20
a very large part of why this capability is important.  Many SP =
customers=20
need the rapid recovery property, which in turn means that many SPs
want to provide the rapid recovery property.

If one wants to edit the current Rapid Recovery I-D to clarify
some specific types of deployments where it is not applicable,
that also would appear to be a trivially simple edit.  Maybe one
could propose some suitable text for that, if that is one's
concern.

> where NAT restarts should be much less frequent than in the home.

Operational experience thus far indicates that NAT restarts are
common with CGN devices.

> Also, c) we're under significant pressure from the v6ops WG to publish
> the PCP base spec, because rfc6204bis supposedly depends on it.

Right, and the devices implementing that specification are among
those where this Rapid Recovery capability is both operationally=20
critical and also where the approach in the current Rapid Recovery=20
I-D is clearly supportable -- which means this capability needs=20
to be specified in an RFC right now, not later on.

> That said, I would like to hear more about why you consider this such =
an
> integral part of the protocol that we cannot publish the base spec
> without it.

As described above, operational experience from uPnP and NAT-PMP=20
is that the "slow recovery" property of the current specification
will make the PCP protocol difficult or impossible to use in many
real-world deployments that are within the scope of this WG's
charter.

Yours,

Ran Atkinson

NB:  I have intermittent network access, until ~ 1st November,
so please accept my apology that I can't respond in as timely
a manner as I might prefer.



From Francis.Dupont@fdupont.fr  Thu Oct 27 07:19:30 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 3A1AF21F8ADE for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 07:19:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level: 
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V9p9thJyWN00 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 07:19:29 -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 6FEBA21F8513 for <pcp@ietf.org>; Thu, 27 Oct 2011 07:19:29 -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 p9REJS9t091706 for <pcp@ietf.org>; Thu, 27 Oct 2011 16:19:28 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110271419.p9REJS9t091706@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 27 Oct 2011 16:19:28 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] bad version response
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, 27 Oct 2011 14:19:30 -0000

In base 16 7.2 page 20 I can read:

   If the received message is at least two octets long but the first
   octet (version) is a version that is not supported, a response is
   generated with the UNSUPP_VERSION result code, and the other steps
   detailed in Section 7.6 are followed.

the R bit set is after so a response with a bad version is not dropped,
I suggest to add a clause to change this, for instance:

   If the received message is at least two octets long but the first
   octet (version) is a version that is not supported, and R bit is
   not set, a response is generated with the UNSUPP_VERSION result
   code, and the other steps detailed in Section 7.6 are followed.

Regards

Francis.Dupont@fdupont.fr

PS: so the checks are in this order:

length < 2 => drop

R bit set => drop

bad version => UNSUPP_VERSION
(BTW the section 7.6 is underspecified, for instance it is not
clear the correct response is 4 octet long even there is no
reason to have more things in common between versions than
the 4 first octets, cf NAT-PMP :-)

length < 4 => drop

server overloaded, rate limit, etc => drop

length > 1024 => MALFORMED_REQUEST

length < 24 => MALFORMED_REQUEST
(this is *not* in base 16 but is required to apply
the address one)

length & 3 != 0 => MALFORMED_REQUEST

IP source address != PCP client address => ADDRESS_MISMATCH

etc

PPS: IMHO it makes sense to merge the length < 4 and
length < 24 checks, i.e., to drop all requests with
a supported version but shorter than the header.

From Francis.Dupont@fdupont.fr  Thu Oct 27 07:36:25 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 47F3421F8514 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 07:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHN8KaLbDaXh for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 07:36:24 -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 711EB21F8511 for <pcp@ietf.org>; Thu, 27 Oct 2011 07:36:24 -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 p9REaNmt092706 for <pcp@ietf.org>; Thu, 27 Oct 2011 16:36:23 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110271436.p9REaNmt092706@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: pcp@ietf.org
Date: Thu, 27 Oct 2011 16:36:23 +0200
Sender: Francis.Dupont@fdupont.fr
Subject: [pcp] unsupported version is underspecified
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, 27 Oct 2011 14:36:25 -0000

In particular there is nothing in 7.3 page 21, cf:

   The PCP client receives the response and verifies that the source IP
   address and port belong to the PCP server of an outstanding PCP
   request.  It validates that the Opcode matches an outstanding PCP
   request.  Responses shorter than 24 octets, longer than 1024 octets,
   or not a multiple of 4 octets are invalid and ignored, likely causing
   the request to be re-transmitted.  The response is further matched by
   comparing fields in the response Opcode-specific data to fields in
   the request Opcode-specific data, as described by the processing for
   that Opcode.  After these matches are successful, the PCP client
   checks the Epoch field to determine if it needs to restore its state
   to the PCP server (see Section 7.5).

=> IMHO we have to insert something before the 24 length check.
Note it is enough to have 4 octets for an unsupported version error
response...

Regards

Francis.Dupont@fdupont.fr

PS: 7.6 pages 24 and 25 don't help as it is only about the way to
find a common version between the client and the server, and
specifies nothing about the unsupported version error response
after the 4 version octets (this is why I argue the content
should be these 4 octets).

From rpenno@juniper.net  Thu Oct 27 12:09:27 2011
Return-Path: <rpenno@juniper.net>
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 2406621F8560 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 12:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OC4SnQL8xEwJ for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 12:09:26 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id 95BDF21F8549 for <pcp@ietf.org>; Thu, 27 Oct 2011 12:09:22 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP;  Thu, 27 Oct 2011 12:09:26 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 27 Oct 2011 12:05:51 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 27 Oct 2011 15:05:50 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: RJ Atkinson <rja.lists@gmail.com>, "pcp@ietf.org" <pcp@ietf.org>
Date: Thu, 27 Oct 2011 15:05:48 -0400
Thread-Topic: [pcp] WG last call on draft-ietf-pcp-base-16.txt
Thread-Index: AcyUkNz9wu450CPMQy2Dx9285bmIOwASpK5E
Message-ID: <CACEF99C.56857%rpenno@juniper.net>
In-Reply-To: <767C47A8-5566-4122-BE8E-062F2A97C539@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 27 Oct 2011 19:09:27 -0000

Hello RJ,

Thanks for the reply. I included comments inline.


On 10/27/11 3:11 AM, "RJ Atkinson" <rja.lists@gmail.com> wrote:

>=20
> On 25  Oct 2011, at 15:47 , Reinaldo Penno wrote:
>> I did not follow up due to the fact that draft-cheshire-pcp-recovery-01
>> views things from a CPE/home perspective where multicast is pervasive.
>> As you point out, it is trying to recreate NAT-PMP's functionality.
>=20
> The Rapid Recovery capability is important to a large number
> of service providers and also to a large number of end sites
> (academic, enterprise, residential, & other).
>=20
> For example, in most cases, the SP's own customers won't be satisfied
> if/when the PCP-capable device develops a fault and it takes a
> long time to recover.  Rapid Recovery is actually quite important
> for most service providers.

Certainly. Can you clarify rapid vs. long? 1sec/1min/5min/30min?

Also, I would like to understand in your opinion if recovery times should b=
e
the same across all end sites you mention. Should, say, residential
customers expect recovery in the same time as enterprise customers?

>=20
>=20
>> My objection to draft-cheshire-pcp-recovery-01 is that relying
>> on multicast in service provider networks is not practical
>=20
> That claim is provably false as written.  You generalise
> to all service provider deployments, when in fact we all
> know that most (possibly all, as you haven't provided any
> specific counter-examples yet) SP deployments don't and won't
> have any issues with this use of link-local multicasting.

Well, multicast recovery is applicable if several conditions are met:

1 - PCP Client, Server and NAT are in the same domain.
2 - Multicast is enabled on both devices
3 - SP prefers a fully distributed deployment - which has capex/opex
    implications.
4 - Finally, PCP Server (which sends the multicast packet), NAT (controlled
    device) and BNG/GGSN (which knows the interface to send multicast
    packet) should ideally be the same device which might be the case or
    not.

>=20
>=20
> * If you have some other approach to solve the same operational issue,
>   please speak up.  I'm open-minded, but the time to put that on the tabl=
e
>   was really last April.
>=20

I'm assuming you are asking the question assuming multicast is not
available. When multicast is not available one approach that comes to mind
is use shorter lifetimes. If an enterprise has hundreds of mappings it can
use a shorter lifetime for only a small % of mappings. That has the same
value of a keep-alive.


> * Alternately, if you were worried about some specific use case or
>   specific narrow deployment model, you could propose some specific
>   text to clarify the Rapid Recovery I-D's applicability.  Again,
>   this really ought to have been done last April, but better late
>   than never.

See above. In my opinion it is the other way around. Meaning, the general
case is when PCP Server and Client can be any number of layer-3 hops away
and all you need is IP reachability. The narrow, or specific case, is when
all the other conditions are met and you can use multicast.

My original suggestion is the same: introduce an applicability section in
the draft.


>=20
>=20
> Yours,
>=20
> Ran Atkinson
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From jhw@apple.com  Thu Oct 27 13:57:03 2011
Return-Path: <jhw@apple.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 747A121F8B19 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 13:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level: 
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0nT+zuGJjkJq for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 13:57:02 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id D822121F8A97 for <pcp@ietf.org>; Thu, 27 Oct 2011 13:57:02 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_kqFosGh9xLTYIaoaBEjhYw)"
Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LTQ004BVSSRKQS1@mail-out.apple.com> for pcp@ietf.org; Thu, 27 Oct 2011 13:57:02 -0700 (PDT)
X-AuditID: 11807136-b7c19ae0000072b0-29-4ea9c59dfe1f
Received: from ba0301a-dhcp89.apple.com (ba0301a-dhcp89.apple.com [17.193.14.217]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay15.apple.com (Apple SCV relay) with SMTP id 96.F8.29360.D95C9AE4; Thu, 27 Oct 2011 13:57:01 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com>
Date: Thu, 27 Oct 2011 13:57:00 -0700
Message-id: <0CDBCDE2-21CA-4287-A893-97D67BD1318B@apple.com>
References: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com>
To: PCP <pcp@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrNLMWRmVeSWpSXmKPExsUieJDvpu7coyv9DHbMsraYfOw3q8X9HT2M DkweO2fdZfdYsuQnUwBTFJdNSmpOZllqkb5dAlfG4ffnmQuOWVTsX9rO3sC4xaCLkZNDQsBE omPBC3YIW0ziwr31bF2MXBxCAiuYJF5uPcIMkhAWsJO4c+MQI4jNK2AssebWOxYQm1kgQaL/ 9hsmEJtNQEXi2+W7YDangK3ExVf7wXpZBFQl+r5+Y4eoV5VYtheil1fARuLFpdlsILYQkP3m 7huwuAjQEasfP2SCOEheouXrHbYJjHyzkKyehWQ1hK0tsWzha+ZZjBxAto7E5IWMqMIQ9sfz R5gWMLKtYhQsSs1JrDQ01UssKMhJ1UvOz93ECArShkKzHYw7/sodYhTgYFTi4eVsX+knxJpY VlyZe4hRgoNZSYRX2gsoxJuSWFmVWpQfX1Sak1p8iFGag0VJnHetwWI/IYH0xJLU7NTUgtQi mCwTB6dUA6PW59fVUdfnMHF75VpFvHrgHn80KueJaOWXc7ELGP8+lX1j373u49nUgvkpPFqi UsI3V58PWLXDtGPtp/b7DZGTPQqd2q8+lNy/2s6ya4/ieTfPL/GPXx+cvb1JWOt54KfXK9VP 8QbVR7XKCseWzi2P/GG6/phyY/ouDV5nTyERx7oCqeybAkosxRmJhlrMRcWJADtGL4lOAgAA
Cc: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 27 Oct 2011 20:57:03 -0000

--Boundary_(ID_kqFosGh9xLTYIaoaBEjhYw)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

everyone--

My apologies to working group for failing to notice this until Mr. Atkinson brought it to my attention.

On Oct 25, 2011, at 7:24 AM, RJ Atkinson wrote:
> 
> [...] an important commonly deployed operational 
> capability of NAT-PMP is being omitted from this document.
> 
> There is significant operational experience with the 
> "Rapid Recovery" capability of NAT-PMP.  It works well 
> in the field.

I am the original author of the NAT-PMP service in Apple's implementations, i.e. AirPort Base Station, Time Capsule and the Mobile Internet Sharing operating mode of iOS on the iPhone.  I have significant experience with this.

I have to say I'm surprised and dismayed at the way this capability has been dismissed from the PCP base specification.  I would have thought that the critical importance of Rapid Recovery would have been immediately recognizable to everyone, and that its inclusion in PCP would have been de rigeur and would have generated no controversy at all.  It is not merely an "optimization" but rather a core feature of the protocol.  I'm ashamed to admit that I didn't notice it was missing until now.

I agree with Mr. Atkinson.  I-D.ietf-pcp-base should not be approved unless the "Rapid Recovery" capability is immediately restored to the specification.  It's too important not to standardize right away, along with the base specification.

> [...]
> A) IETF PCP WG Chairs place draft-cheshire-pcp-recovery-02 into
>   WG Last Call immediately for publication on the IETF standards 
>   track, with the document to be marked as an "Update" to the 
>   draft-ietf-pcp-base-16.txt document.
> 
> or
> 
> B) IETF PCP WG Chairs suspend the current WG Last Call, 
>   fold the text from draft-cheshire-pcp-recovery-02 into 
>   a new version of the draft-ietf-pcp-base-* document, 
>   and restart the WG Last Call on that revised version.

Either of these would be fine with me too, but I think I would prefer the latter for the sake of simplicity.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




--Boundary_(ID_kqFosGh9xLTYIaoaBEjhYw)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>everyone--</div><div><br></div><div>My apologies to working =
group for failing to notice this until Mr. Atkinson brought it to my =
attention.</div><div><br></div><div>On Oct 25, 2011, at 7:24 AM, RJ =
Atkinson wrote:</div><div></div></div><div></div><blockquote =
type=3D"cite"><div><br></div><div>[...] an important commonly deployed =
operational&nbsp;<br>capability of NAT-PMP is being omitted from this =
document.<br><br>There is significant operational experience with =
the&nbsp;<br>"Rapid Recovery" capability of NAT-PMP. &nbsp;It works =
well&nbsp;<br>in the field.</div></blockquote><div><br></div><div>I am =
the original author of the NAT-PMP service in Apple's implementations, =
i.e. AirPort Base Station, Time Capsule and the Mobile Internet Sharing =
operating mode of iOS on the iPhone. &nbsp;I have significant experience =
with this.</div><div><br></div><div>I have to say I'm surprised and =
dismayed at the way this capability has been dismissed from the PCP base =
specification. &nbsp;I would have thought that the critical importance =
of Rapid Recovery would have been immediately recognizable to everyone, =
and that its inclusion in PCP would have been de rigeur and would have =
generated no controversy at all. &nbsp;It is not merely an =
"optimization" but rather a core feature of the protocol. &nbsp;I'm =
ashamed to admit that I didn't notice it was missing until =
now.</div><div><br></div><div>I agree with Mr. Atkinson. =
&nbsp;I-D.ietf-pcp-base should not be approved unless the "Rapid =
Recovery" capability is immediately restored to the specification. =
&nbsp;It's too important not to standardize right away, along with the =
base specification.</div><div><br></div><div><blockquote =
type=3D"cite">[...]</blockquote></div><blockquote type=3D"cite"><div>A) =
IETF PCP WG Chairs place draft-cheshire-pcp-recovery-02 =
into<br>&nbsp;&nbsp;WG Last Call immediately for publication on the IETF =
standards&nbsp;<br>&nbsp;&nbsp;track, with the document to be marked as =
an "Update" to the&nbsp;<br>&nbsp;&nbsp;draft-ietf-pcp-base-16.txt =
document.<br><br>or<br><br>B) IETF PCP WG Chairs suspend the current WG =
Last Call,&nbsp;<br>&nbsp;&nbsp;fold the text from =
draft-cheshire-pcp-recovery-02 into&nbsp;<br>&nbsp;&nbsp;a new version =
of the draft-ietf-pcp-base-* document,&nbsp;<br>&nbsp;&nbsp;and restart =
the WG Last Call on that revised =
version.</div></blockquote><div><br></div><div>Either of these would be =
fine with me too, but I think I would prefer the latter for the sake of =
simplicity.</div><br><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Gill Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
12px; "><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><br =
class=3D"Apple-interchange-newline">--</span></span></div><div =
style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">james woodyatt &lt;<a =
href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&gt;</span></span></span></=
div><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">member of technical staff, core os =
networking</span></span></span></div><br =
class=3D"Apple-interchange-newline" style=3D"font-size: 11px; =
font-family: Geneva; "></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Boundary_(ID_kqFosGh9xLTYIaoaBEjhYw)--

From cheshire@apple.com  Thu Oct 27 14:37:00 2011
Return-Path: <cheshire@apple.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 3A5FC11E8099 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 14:37:00 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id omcTXX517a-7 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 14:36:59 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 8489F11E8098 for <pcp@ietf.org>; Thu, 27 Oct 2011 14:36:59 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LTQ003UIUKNGBK2@mail-out.apple.com> for pcp@ietf.org; Thu, 27 Oct 2011 14:36:58 -0700 (PDT)
X-AuditID: 11807130-b7c1bae000001553-5f-4ea9cefaafe9
Received: from [17.193.13.41] (chesh1.apple.com [17.193.13.41]) by relay11.apple.com (Apple SCV relay) with SMTP id 93.70.05459.AFEC9AE4; Thu, 27 Oct 2011 14:36:58 -0700 (PDT)
In-reply-to: <CACC6053.56439%rpenno@juniper.net>
References: <CACC6053.56439%rpenno@juniper.net>
Message-id: <36E0DF10-3EBF-4501-8484-AD43D96B8691@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Thu, 27 Oct 2011 14:36:19 -0700
To: Reinaldo Penno <rpenno@juniper.net>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUieJBXU/fXuZV+BvsWsFpMPvab1eL+jh5G i/M/pzA7MHvsnHWX3WPJkp9MHtebrrIHMEdx2aSk5mSWpRbp2yVwZVz4cJu1oIOn4ua614wN jKc5uxg5OSQETCTmrN3OBmGLSVy4tx7I5uIQEtjIKHHy3HwmkASngIHE3HsbWEFsIQF9iVnn DoLZvAJGElcnT2XvYuTgYBZwkVg4JQ/E5BWwkeif5wRSwSzgJjF36x9WCFteYvvbOcwgNpuA lsSLz1fYQMqFBWwlnswwAgmzCKhKfJ7bxwJiiwioS/zofcQMcZmcxOHTrxgnMPLPQrJ3FsLe WUgWLGBkXsUoWJSak1hpaKiXWFCQk6qXnJ+7iREUgg2FBjsY1/7kP8QowMGoxMPL2b7ST4g1 say4MvcQowQHs5IIr7QXUIg3JbGyKrUoP76oNCe1+BCjNAeLkjjvaoPFfkIC6YklqdmpqQWp RTBZJg5OqQZGiwvm8/M5Z3kcc3A9HFdbpf35alVBveNpibkfTt+0dNi+6uGlFztmybls/2AY nN2YUfSupf2d9GRB+2cbVy6x+qKdOLf47cHo7V3hm6a4cMzzLw7VKi+sFin5++tSyEuu5EO6 1kl7PSZ76vfO/yU68ahFVYC41xRuj1XboisneV7p6vPd4yCixFKckWioxVxUnAgAecfjmj0C	AAA=
Cc: "pcp@ietf.org" <pcp@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 27 Oct 2011 21:37:00 -0000

On 25 Oct, 2011, at 12:47, Reinaldo Penno wrote:

> Hello RJ,
>
> I did not follow up due to the fact that draft-cheshire-pcp- 
> recovery-01 views things from a CPE/home perspective where  
> multicast is pervasive. As you point out, it is trying to recreate  
> NAT-PMP's functionality.
>
> My objection to draft-cheshire-pcp-recovery-01 is that relying on  
> multicast in service provider networks is not practical - although  
> fine for home networks.

The Rapid Recovery text does not say that relying on multicast in  
service provider networks is practical, nor does it say that anyone  
should think that.

What the Rapid Recovery text says is that multicast *is* practical in  
home networks, such as networks where DHCP is used (since a DHCP  
broadcast should generally reach the same set of hosts as an all- 
hosts multicast). Also, such home gateways typically forget all  
dynamic state when rebooted, so they have absolutely no idea who  
their erstwhile clients were, so the *only* option they have is to  
multicast a message to all potential clients saying, "Hey, I'm back."

Therefore multicast is both necessary and sufficient for these devices.

You may not yourself work on low-cost home gateways, but both Apple  
and Linksys do make home gateways for this market, and I would like  
those home gateways to continue to be at least as good as our  
existing NAT-PMP home gateways.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From moore@network-heretics.com  Thu Oct 27 15:36:52 2011
Return-Path: <moore@network-heretics.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 78A6F11E8096 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 15:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.263
X-Spam-Level: 
X-Spam-Status: No, score=-3.263 tagged_above=-999 required=5 tests=[AWL=0.336,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CNyx+yS9CJSy for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 15:36:51 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id D860911E807F for <pcp@ietf.org>; Thu, 27 Oct 2011 15:36:51 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E83F420458; Thu, 27 Oct 2011 18:36:50 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 27 Oct 2011 18:36:50 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=j7VMvv4n7AavPZkQ0ySEVf0dPc8=; b=Qk /RnmbIEUM5RNPLbA1Klz4sgj+DeyQEgxMaobxyk4mOB+Jikju/0E/docDnIfG3cZ 1b2Q4fwPibZVAIFhCaEByLT4robNGgwHQFo6kYNS21Y4umCJb8cHveBZdTti7H/l COTIWZSCXTvAbAlVsVMacX0YglFaoVZ9y6e7OAftM=
X-Sasl-enc: gGcJaq72/L2vsZePJKKV6Yj6Sqm+1nK5eAtdA2+kdWuB 1319755010
Received: from [192.168.1.16] (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 0EA4F483364; Thu, 27 Oct 2011 18:36:49 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <0CDBCDE2-21CA-4287-A893-97D67BD1318B@apple.com>
Date: Thu, 27 Oct 2011 18:36:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A56E9630-57D4-4888-90B6-A3E044B5BCFA@network-heretics.com>
References: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com> <0CDBCDE2-21CA-4287-A893-97D67BD1318B@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1084)
Cc: PCP <pcp@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 27 Oct 2011 22:36:52 -0000

On Oct 27, 2011, at 4:57 PM, james woodyatt wrote:

> I agree with Mr. Atkinson.  I-D.ietf-pcp-base should not be approved =
unless the "Rapid Recovery" capability is immediately restored to the =
specification.  It's too important not to standardize right away, along =
with the base specification.

I am also very concerned about this.  I believe that this mechanism =
needs to be either (preferably) part of the PCP specification, or =
approved at the same time as the PCP specification.=20

If there are cases for which it is truly infeasible to implement this =
capability, the specification can make exceptions for those cases.   But =
the default assumption should be that the rapid recovery capability =
exists and that server implementations should support it.   Particularly =
in IPv6.  (I care a bit less about IPv4 as it's at EOL.)

Keith


From dwing@cisco.com  Thu Oct 27 16:23:33 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 2EA201F0C43 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 16:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.508
X-Spam-Level: 
X-Spam-Status: No, score=-105.508 tagged_above=-999 required=5 tests=[AWL=1.091, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1mWSTebHJRDc for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 16:23:32 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 51AF21F0C36 for <pcp@ietf.org>; Thu, 27 Oct 2011 16:23:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=5426; q=dns/txt; s=iport; t=1319757812; x=1320967412; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=kpy3riWdDqGy7ggIE+5QjClK5ecFxGEUX2QH/tOi5Y8=; b=T/k+JXrfzrrS07QfZ3DgtkXJd+ll1FAOtIFZll0odty1oWWddr8xJzig MRGL88g5ezn1laoMdxWS9v2fLdMx5fmVJo2yKyhfmDhoPd/RmU21QC4QX 4K7AeOsYemc6A9arWTGl2cr/lTpo4iSsHMC7t4fiab/jf6j1gQcPKJXKu U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: At8AALrmqU6rRDoG/2dsb2JhbABCmhCBa41mgQWBcgEBAQMBAQEBBQoBFAMQNBAHAQMCCQ8BAQQBASgHGQ4VCgkIAQEEARILF4dgCJZ1AZ4uBIh+BIgGngY
X-IronPort-AV: E=Sophos;i="4.69,415,1315180800"; d="scan'208";a="10815370"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 27 Oct 2011 23:23:32 +0000
Received: from dwingWS ([128.107.106.79]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9RNNVY6013148; Thu, 27 Oct 2011 23:23:31 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110241522.p9OFM8xd033562@givry.fdupont.fr>
In-Reply-To: <201110241522.p9OFM8xd033562@givry.fdupont.fr>
Date: Thu, 27 Oct 2011 16:23:31 -0700
Message-ID: <0ffc01cc94ff$70f69000$52e3b000$@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: AcySYNG5Gnoc6dWVSTWlwM4VlZrLsQCnOnjw
Content-Language: en-us
Subject: Re: [pcp] base 16 review (1)
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, 27 Oct 2011 23:23:33 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Monday, October 24, 2011 8:22 AM
> To: pcp@ietf.org
> Subject: [pcp] base 16 review (1)
> 
> I began the base 16 review, here are my comments up to 7.3 page 21.
> 
>  - ToC page 3:
>    12.4. Source Address and Port in PCP Header ->
>    12.4. Source Address in PCP Header

Adjusted.

>  (the source port is no longer in the header, BTW I'd like
>   to understand why. IMHO it is just a simplication as the
>   address is enough to detect unexpected on-path NATs)

Correct.


>  - 1 page 5 (not a comment about the document itself):
>   an interception PCP proxy (cf draft-penno-pcp-nested-nat-01.txt)
>   is an ALG (as it is commented) so is *bad*!
> 
>  - 2.1 page 3: [I-D.miles-behave-l2nat] points to an expired draft?
>   Is it just because someone forgot to refresh it or for a more
>   annoying reason?

It was never progressed.  Citing an expired draft is perfectly
fine.


>  - 3 page 7 (Remote Host): Remote Host -> Remote Peer Host
>   (remote host is used once, remote peer 52 times :-)

Fixed.

>  - 3 page 8 (Mapping Types): web page -> web portal
>   (just a suggestion, the term "web page" is very poor IMHO)

Adjusted.


>  - 3 page 9 (Mapping Types, at the end of the item, suggestion):
>       ... they behave exactly the same as an
>       explicit dynamic mapping.
>    ->
>       ... they behave exactly the same as
>       explicit dynamic mappings.

Adjusted.


>  - 5 page 11: from a legal IPv6 address, -> from a native IPv6 address,
>   (IPv4 mapped IPv6 addresses are legal, BTW native is better but not
>    so good as it suggests it couldn't be a 6to4 address, seeking for
>    a better term...)

Adjusted.


>  - 6.1 page 13 (end of 6.1): please remove the second / extra
> 
>    Reserved:  16 reserved bits, MUST be sent as 0 and MUST be ignored
>       when received.

Removed.


>  - 6.3 page 15: 1024-4*number_of_options -> 1020-4*number_of_options
>   (i.e., please add the UNPROCESSED option header too)

Fixed.


>  - 6.4 page 18 (NO_RESOURCES): I have a concern with:
>       ... This can be used as a catch-all
>       error, should no other error message be suitable.
> 
>    by itself it is not a bad idea to provide a catch-all but
>    NO_RESOURCES has a special processing, cf. 7.3 page 19:
> 
>    If the result code is NO_RESOURCES, PCP client SHOULD NOT send *any*
>    further requests to that PCP server for the indicated error
> lifetime.
> 
>    So we really need the PROCESSING_ERROR...

Let's talk about PROCESSING_ERROR in a separate thread.  As you stated,
the difficulty is writing text to distinguish between a catch-all
PROCESSING_ERROR error and other errors.



>  - 6.4 page 18 (CANNOT_PROVIDE_EXTERNAL_PORT): please remember we
>   still have an open issue about this

Renamed to CANNOT_PROVIDE_EXTERNAL, and now says:

  the requested
  external port and/or external address cannot be provided.

Suitable?

 
>  - 6.4 page 18 (CANNOT_PROVIDE_EXTERNAL_PORT): protcool -> protocol

fixed.

>  - 6.4 page 18 (ADDRESS_MISMATCH): *3* fixes
> 
>    12 ADDRESS_MISMATCH: the source IP address or port of the request
>       packet does not match the contents of the PCP Client's IP Address
>       or UDP port.
> 
>   ->
> 
>    12 ADDRESS_MISMATCH: the source IP address of the request packet
>       does not match the content of the PCP Client's IP Address.

fixed.


>  - 7.1 page 19: it is not a concern for me but BTW there is nothing
>   about other (i.e., not first) members of the list of PCP Server(s)...

On purpose; that may be something another document discusses.


>  - 7.2 page 20: between
> 
>      If the length of the message exceeds 1024 octets or is not a
> multiple
> 
>    and
> 
>     The PCP server compares the IP address (from the IP header) with
> the
> 
>    a sentence is needed for requests longer than 4 octets but shorter
>    than the 6.1/Figure 2 request header, with of course a
>    MALFORMED_REQUEST error. Note the response has the 24 octet check.

Now says:

        <t>If the length of the message exceeds 1024 octets, is not a
        multiple of 4 octets, or its header is too short, it is
        invalid.



>   - 7.3 page 21: remove from the processing a response:
> 
>    If the PCP Client's IP Address and PCP Client's Port fields of the
>    PCP response header do not match the source address and port of the
>    request, it indicates the presence of a NAT between the PCP client
>    and PCP server.  If they don't match, then the PCP client (or the
>    user on the client host) MUST ensure that an appropriate NAT mapping
>    is created on the intervening NAT(s) (e.g., using UPnP IGD, NAT-PMP,
>    or manual configuration), otherwise, the PCP-installed mapping will
>    be ineffective.

Changed to:

        <t>If the error ADDRESS_MISMATCH is received, it indicates the
        presence of a NAT between the PCP client and PCP server.
        Procedures to resolve this problem are beyond the scope of
        this document.</t>

-d


> Thanks
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From jhw@apple.com  Thu Oct 27 16:32:17 2011
Return-Path: <jhw@apple.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 863E421F86A4; Thu, 27 Oct 2011 16:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.274
X-Spam-Level: 
X-Spam-Status: No, score=-106.274 tagged_above=-999 required=5 tests=[AWL=-0.276, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4m0finpGI7FS; Thu, 27 Oct 2011 16:32:17 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 04D8A21F869E; Thu, 27 Oct 2011 16:32:17 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_vIJQ59ilWEd951s7jcBJxA)"
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LTQ003TDZX0GBV2@mail-out.apple.com>; Thu, 27 Oct 2011 16:32:15 -0700 (PDT)
X-AuditID: 1180711d-b7b7dae000007623-b2-4ea9e9ffe908
Received: from ba0301a-dhcp89.apple.com (ba0301a-dhcp89.apple.com [17.193.14.217]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id D3.44.30243.FF9E9AE4; Thu, 27 Oct 2011 16:32:15 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
Date: Thu, 27 Oct 2011 16:32:15 -0700
In-reply-to: <58C8AD88-589C-4ECE-8041-A0B461CE8EDD@gmail.com>
To: PCP <pcp@ietf.org>, IPv6 Operations <v6ops@ietf.org>
References: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com> <s1v4nywwee1.fsf@bikeshed.isc.org> <58C8AD88-589C-4ECE-8041-A0B461CE8EDD@gmail.com>
Message-id: <7E14C89F-7497-443A-B812-8602733FB0D0@apple.com>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJLMWRmVeSWpSXmKPExsUieJDvpu7/lyv9DDoWalpMPvab1eL0sb3M DkweS5b8ZApgjOKySUnNySxLLdK3S+DKePPhNGPBGv2Kx5OeMjcwftHoYuTkkBAwkfjftJoR whaTuHBvPVsXIxeHkMAKJomtOztZQBJsAioS3y7fZQKxeQWMJdbcegcWZxZIkNjcMhOogYND WMBW4skMI5Awi4CqxMYHnawgNidQuOfIYbByEQEriVu/lrOB2EICExglDjT6QIy0kZhwaCkb xA3yEi1f77BNYOSdhWTbLCTbIGxtiWULXzPPAtrMLKAjMXkhI6owhP3x/BGmBYxsqxgFi1Jz EisNjfUSCwpyUvWS83M3MYICsKFQdgfj/p/8hxgFOBiVeHgTOlf6CbEmlhVX5h5ilOBgVhLh Db0OFOJNSaysSi3Kjy8qzUktPsQozcGiJM67ymCxn5BAemJJanZqakFqEUyWiYNTqoFxi0TQ 3vscXV2Vcmv/XJVsOPxzwYefST3iEkWR+//2aAu3F06dLc09pURuxr1f7+Tuq3dPmZTne8z1 PbtqmoJlqN6TupTjuSfK0zNaM9NT9UvSGE2j/Vj1MmTW66xse9M4ZcLFFbx3JI9XduwMzLas vxJv1nk9ak/R6dkztl08Hzj5wm/PnR+UWIozEg21mIuKEwG0cO5WPAIAAA==
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 27 Oct 2011 23:32:17 -0000

--Boundary_(ID_vIJQ59ilWEd951s7jcBJxA)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

On Oct 27, 2011, at 3:39 AM, RJ Atkinson wrote:
> On 26  Oct 2011, at 00:44 , Paul Selkirk wrote:
>> 
>> OTOH, a) if we define it for IPv4 multicast, someone will surely
>> and immediately request it for IPv6 multicast;
> 
> If true, that's a trivial edit that could be made within a day.  
> The IPv6 all-nodes link-local multicast address was defined 
> over a decade ago and is widely supported in environments 
> where native IPv6 is deployed.


I will stand up right now and say this is issue yet another reason for me to complain that PCP is not ready to meet requirements derived from REC-48 of RFC 6092 for IPv6 residential gateway simple security functions.

If responding to the "significant pressure" from V6OPS to publish a PCP base specification, so that RFC 6204bis can cite it, is a priority for the PCP working group, then that argues for stopping the current WGLC until the Rapid Recovery capability in I-D.cheshire-pcp-recovery is restored to the PCP base specification.

On the other hand, another option is for PCP to be withdrawn as a candidate for meeting REC-48 of RFC 6092, which would free V6OPS to consider another protocol for that purpose in RFC 6204bis instead.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




--Boundary_(ID_vIJQ59ilWEd951s7jcBJxA)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Oct 27, 2011, at 3:39 AM, RJ Atkinson =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">On 26 =
&nbsp;Oct 2011, at 00:44 , Paul Selkirk wrote:<br><blockquote =
type=3D"cite"><font class=3D"Apple-style-span" =
color=3D"#00721d"><br></font></blockquote><blockquote type=3D"cite">OTOH, =
a) if we define it for IPv4 multicast, someone will =
surely<br></blockquote><blockquote type=3D"cite">and immediately request =
it for IPv6 multicast;<br></blockquote><br>If true, that's a trivial =
edit that could be made within a day. &nbsp;<br>The IPv6 all-nodes =
link-local multicast address was defined<span =
class=3D"Apple-converted-space">&nbsp;</span><br>over a decade ago and =
is widely supported in environments<span =
class=3D"Apple-converted-space">&nbsp;</span><br>where native IPv6 is =
deployed.<br></span></blockquote></div><div><br></div><div>I will stand =
up right now and say this is issue yet another reason for me to complain =
that PCP is not ready to meet requirements derived from REC-48 of RFC =
6092 for IPv6 residential gateway simple security =
functions.</div><div><br></div><div>If responding to the "significant =
pressure" from V6OPS to publish a PCP base specification, so that RFC =
6204bis can cite it, is a priority for the PCP working group, then that =
argues for stopping the current WGLC until the Rapid Recovery capability =
in I-D.cheshire-pcp-recovery&nbsp;is restored to the PCP base =
specification.</div><div><br></div><div>On the other hand, another =
option is for PCP to be withdrawn as a candidate for meeting REC-48 of =
RFC 6092, which would free V6OPS to consider another protocol for that =
purpose in RFC 6204bis instead.</div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Gill Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
12px; "><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><br =
class=3D"Apple-interchange-newline">--</span></span></div><div =
style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">james woodyatt &lt;<a =
href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&gt;</span></span></span></=
div><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">member of technical staff, core os =
networking</span></span></span></div><br =
class=3D"Apple-interchange-newline" style=3D"font-size: 11px; =
font-family: Geneva; "></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Boundary_(ID_vIJQ59ilWEd951s7jcBJxA)--

From moore@network-heretics.com  Thu Oct 27 17:02:22 2011
Return-Path: <moore@network-heretics.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 6143011E80A2; Thu, 27 Oct 2011 17:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.974
X-Spam-Level: 
X-Spam-Status: No, score=-2.974 tagged_above=-999 required=5 tests=[AWL=0.024,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G4lw21WKq3zC; Thu, 27 Oct 2011 17:02:21 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 7368F11E80A3; Thu, 27 Oct 2011 17:02:21 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id F38B42071D; Thu, 27 Oct 2011 20:02:20 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 27 Oct 2011 20:02:21 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=hIu qkZae6CpxBctwBgB1VktJz9M=; b=Mnuq/RfDtgtVhkQ6wG4cSPf8oihD67jhw5+ kh8CBZ0IQUOsIt3ynLKPyfd2JWpcxO6MR0S1wmpe9POn+83y8f4l94BBhKU/C7ML ic66eBeZ+mFoYgXFYdawlRWBJKQZYHB3WKoilPf1qqykkkgo1x8z+YFxSI53cxzT g0Q2y5dk=
X-Sasl-enc: taPb4b82VQa7czpErwxxNuqt7p8EUL73/wpe0I/+9Q86 1319760140
Received: from [192.168.1.16] (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 94664483404; Thu, 27 Oct 2011 20:02:19 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-31-3038950
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <7E14C89F-7497-443A-B812-8602733FB0D0@apple.com>
Date: Thu, 27 Oct 2011 20:02:18 -0400
Message-Id: <247469E7-EF59-4919-AA60-C17BDDE3145C@network-heretics.com>
References: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com> <s1v4nywwee1.fsf@bikeshed.isc.org> <58C8AD88-589C-4ECE-8041-A0B461CE8EDD@gmail.com> <7E14C89F-7497-443A-B812-8602733FB0D0@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations <v6ops@ietf.org>, PCP <pcp@ietf.org>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 00:02:22 -0000

--Apple-Mail-31-3038950
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 27, 2011, at 7:32 PM, james woodyatt wrote:

> On Oct 27, 2011, at 3:39 AM, RJ Atkinson wrote:
>> On 26  Oct 2011, at 00:44 , Paul Selkirk wrote:
>>>=20
>>> OTOH, a) if we define it for IPv4 multicast, someone will surely
>>> and immediately request it for IPv6 multicast;
>>=20
>> If true, that's a trivial edit that could be made within a day. =20
>> The IPv6 all-nodes link-local multicast address was defined=20
>> over a decade ago and is widely supported in environments=20
>> where native IPv6 is deployed.
>=20
>=20
> I will stand up right now and say this is issue yet another reason for =
me to complain that PCP is not ready to meet requirements derived from =
REC-48 of RFC 6092 for IPv6 residential gateway simple security =
functions.
>=20
> If responding to the "significant pressure" from V6OPS to publish a =
PCP base specification, so that RFC 6204bis can cite it, is a priority =
for the PCP working group, then that argues for stopping the current =
WGLC until the Rapid Recovery capability in I-D.cheshire-pcp-recovery is =
restored to the PCP base specification.
>=20
> On the other hand, another option is for PCP to be withdrawn as a =
candidate for meeting REC-48 of RFC 6092, which would free V6OPS to =
consider another protocol for that purpose in RFC 6204bis instead.

I don't think we need two different protocols.  But IMO the emphasis in =
PCP on accommodating LSNs is misplaced.   Long term, the more important =
use of PCP is to interface between hosts/applications and IPv6 =
firewalls... and NATs should be eradicated.  That's not to say that I =
object to including IPv4/LSN support in PCP, but that feature should not =
be the primary driver of PCP's design.  PCP should be designed first for =
v6 and other uses considered secondary.

Keith


--Apple-Mail-31-3038950
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 27, 2011, at 7:32 PM, james woodyatt =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><div>On Oct 27, =
2011, at 3:39 AM, RJ Atkinson wrote:</div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">On 26 =
&nbsp;Oct 2011, at 00:44 , Paul Selkirk wrote:<br><blockquote =
type=3D"cite"><font class=3D"Apple-style-span" =
color=3D"#00721d"><br></font></blockquote><blockquote type=3D"cite">OTOH, =
a) if we define it for IPv4 multicast, someone will =
surely<br></blockquote><blockquote type=3D"cite">and immediately request =
it for IPv6 multicast;<br></blockquote><br>If true, that's a trivial =
edit that could be made within a day. &nbsp;<br>The IPv6 all-nodes =
link-local multicast address was defined<span =
class=3D"Apple-converted-space">&nbsp;</span><br>over a decade ago and =
is widely supported in environments<span =
class=3D"Apple-converted-space">&nbsp;</span><br>where native IPv6 is =
deployed.<br></span></blockquote></div><div><br></div><div>I will stand =
up right now and say this is issue yet another reason for me to complain =
that PCP is not ready to meet requirements derived from REC-48 of RFC =
6092 for IPv6 residential gateway simple security =
functions.</div><div><br></div><div>If responding to the "significant =
pressure" from V6OPS to publish a PCP base specification, so that RFC =
6204bis can cite it, is a priority for the PCP working group, then that =
argues for stopping the current WGLC until the Rapid Recovery capability =
in I-D.cheshire-pcp-recovery&nbsp;is restored to the PCP base =
specification.</div><div><br></div><div>On the other hand, another =
option is for PCP to be withdrawn as a candidate for meeting REC-48 of =
RFC 6092, which would free V6OPS to consider another protocol for that =
purpose in RFC 6204bis instead.</div></div></blockquote></div><br><div>I =
don't think we need two different protocols. &nbsp;But IMO the emphasis =
in PCP on accommodating LSNs is misplaced. &nbsp; Long term, the more =
important use of PCP is to interface between hosts/applications and IPv6 =
firewalls... and NATs should be eradicated. &nbsp;That's not to say that =
I object to including IPv4/LSN support in PCP, but that feature should =
not be the primary driver of PCP's design. &nbsp;PCP should be designed =
first for v6 and other uses considered =
secondary.</div><div><br></div><div>Keith</div><div><br></div></body></htm=
l>=

--Apple-Mail-31-3038950--

From dwing@cisco.com  Thu Oct 27 17:03:18 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 45EF71F0C3F for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 17:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.599
X-Spam-Level: 
X-Spam-Status: No, score=-105.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oSx4YaUxuwa2 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 17:03:17 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 2D9AF1F0C3E for <pcp@ietf.org>; Thu, 27 Oct 2011 17:03:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=12910; q=dns/txt; s=iport; t=1319760197; x=1320969797; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=JUE2XIc2oOp7oBw//3Uc/icsr5rtYkPPKR4m38WMhnU=; b=KJRRG5vQIsOG6LRUk+YXJBTrSWHHjkvaJmqc0tvlJiEfgemr7RMrBTzg XVCPKfBIgD89D0VL1eDKGSaBBygf/x069yXKZjpclxytBna+P06VfsZ7u bD1Y9jaMkDQ4/1b9B6UZxNshSmweOSP3+tlvqeNBami6ht3wHAtN7i2CD I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtgAAF7wqU6rRDoI/2dsb2JhbABCmhGBa41mgQWBcgEBAQMBAQEBBQoBFAMQNBAHAQMCCQ8BAQQBARYSBxkOFQoJCAEBBAESCxeHYAiXAgGeKASFYoMcBIgGngY
X-IronPort-AV: E=Sophos;i="4.69,415,1315180800"; d="scan'208";a="10809883"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 28 Oct 2011 00:03:17 +0000
Received: from dwingWS ([128.107.106.79]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p9S03GKa030784; Fri, 28 Oct 2011 00:03:16 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110261244.p9QCi49O098522@givry.fdupont.fr>
In-Reply-To: <201110261244.p9QCi49O098522@givry.fdupont.fr>
Date: Thu, 27 Oct 2011 17:03:16 -0700
Message-ID: <103001cc9504$fe6b3b70$fb41b250$@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: AcyT3PbS1s08gSRlSbyVmAlnZNeT9ABIokiA
Content-Language: en-us
Subject: Re: [pcp] base 16 review (2)
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, 28 Oct 2011 00:03:18 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Wednesday, October 26, 2011 5:44 AM
> To: pcp@ietf.org
> Subject: [pcp] base 16 review (2)
> 
> Second part of my editorial (*) review comments,
> up to 11.3 / page 56.
> (*) I have two concerns I am discussing internally which are clearly
> not editorial at all.
> 
> (from 7.3 page 21 excluded)
> 
>  - 7.5 page 22: please choose between '1' and 'one', as I prefer
>   the work this gives:
> 
>    by 1 every second -> by one every second

Fixed.


>  - 7.5 page 23: I liked the one hour max drift rule, using the
>   same style it gives an additional member of the if 'or':
>   or 3600 < abs(server_delta - client_delta)

I don't understand.


>  - 7.6 page 24: perhaps from an older edit?
> 
>   these first two octets -> this first octet

fixed.



>  - 8 page 27: the paragraph:
> 
>    Note that PCP requests containing the MAP or PEER Opcodes cannot
>    delete or shorten the lifetime of an existing implicit mapping for
>    the indicated internal address and port.  Conceptually implicit and
>    explicit mappings are different "layers" in the NAT forwarding state
>    database.
> 
>   is in contradiction with the implementation-dependent text in
>   the PEER opcode description. Note IMHO that text is wrong so I cite
>   this paragraph only for the case the WG decision will be reversed.

Let's bring this up in a separate thread, solely about this issue.



>  - 9 page 35: I suggest to move the text about ICMP from 9.5 to here:
> 
>    their MAP request, to ensure that no other clients on the same
>    machine are also listening on the same Internal Port.
> 
>  moved text
> 
>    As a side-effect of creating a mapping, ICMP messages associated
> with
>    the mapping MUST be forwarded (and also translated, if appropriate)
>    for the duration of the mapping's lifetime.  This is done to ensure
>    that ICMP messages can still be used by hosts, without application
>    programmers or PCP client implementations needing to signal PCP
>    separately to create ICMP mappings for those flows.
> 
>  resuming
> 
>    The operation of the MAP Opcode is described in this section.

Moved.


>  - 9.3 page 38: in fact
> 
>    ... If
>    the requested Lifetime is non-zero, the Internal Port is zero, and
>    the Protocol is non-zero, it indicates a request to map all incoming
>    traffic for that entire Protocol.
> 
>   is valid only for protocols which don't use 16-bit port numbers.
>   I don't know if it is a problem, i.e., if the text should be changed.
>   IMHO the 9.1 definition of the internal port is clear enough.

Will leave as-is.


>  - 9.3 page 39: I suggest to swap the two paragraphs, i.e.:
> 
>    If the PCP-controlled device is stateless (that is, it does not
>    establish any per-flow state, and simply rewrites the address and/or
>    port in a purely algorithmic fashion), the PCP server simply returns
>    an answer indicating the external IP address and port yielded by
> this
>    stateless algorithmic translation.  This allows the PCP client to
>    learn its external IP address and port as seen by remote peers.
>    Examples of stateless translators include stateless NAT64, 1:1
> NAT44,
>    and NPTv6 [RFC6296], all of which modify addresses but not port
>    numbers.
> 
>    If an Option with value less than 128 exists (i.e., mandatory to
>    process) but that Option does not make sense (e.g., the
>    PREFER_FAILURE Option is included in a request with lifetime=0), the
>    request is invalid and generates a MALFORMED_OPTION error.
> 
>  ->
> 
>    If an Option with value less than 128 exists (i.e., mandatory to
>    process) but that Option does not make sense (e.g., the
>    PREFER_FAILURE Option is included in a request with lifetime=0), the
>    request is invalid and generates a MALFORMED_OPTION error.
> 
>    If the PCP-controlled device is stateless (that is, it does not
>    establish any per-flow state, and simply rewrites the address and/or
>    port in a purely algorithmic fashion), the PCP server simply returns
>    an answer indicating the external IP address and port yielded by
> this
>    stateless algorithmic translation.  This allows the PCP client to
>    learn its external IP address and port as seen by remote peers.
>    Examples of stateless translators include stateless NAT64, 1:1
> NAT44,
>    and NPTv6 [RFC6296], all of which modify addresses but not port
>    numbers.

Swapped.



>  - 9.3 page 40: I still don't like the last paragraph, I propose:
> 
>    If all of the preceding operations were successful (did not generate
>    an error response), then the requested mapping is created or
>    refreshed as described in the request and a SUCCESS response is
>    built.  This SUCCESS response contains the same Opcode as the
>    request, but with the "R" bit set.
> 
>  ->
> 
>    If all of the preceding operations were successful (did not generate
>    an error response), then the requested mapping is created or
>    refreshed as described in the request and a SUCCESS response is
>    built.  All responses, including this SUCCESS response contains
>    the same Opcode as the request, but with the "R" bit set.

I see what you're getting at.  Such text really belongs in the
general PCP processing section, as we want this to apply to 
any and all PCP messages (not just MAP messages).  So, I added:

        All responses (both error and success) contain the same OpCode
        as the request, but with the "R" bit set.</t>

to the bottom of the general PCP processing section (7.2), and 
removed the discussion of the "R" bit from the MAP-specific 
section (9.3).


>  - 9.4 page 41: I have a problem with this MUST:
> 
>    The PCP client MUST also set a timer or otherwise schedule an event
>    to renew the mapping before its lifetime expires.
> 
>   due to the (poor) wording this can be read as infinite renewal is
>   mandatory. Of course the issue is not in the requirement level,
>   I strongly suggest to add a condition like:
> 
>    When renewal is desired, the PCP client MUST also...

Adjusted.


>  - 9.5 page 42: the all subscriber mapping delete is not in the list
>   (but is in 11.1 page 51 about THIRD_PARTY). IMHO we should add
>   a reference to it at the end of:
> 
>    o  If both the internal port and protocol are zero, it indicates a
>       request to delete all mappings for this Internal Address for all
>       transport protocols.  This is useful when a host reboots or joins
>       a new network, to clear out prior stale state from the NAT
> gateway
>       before beginning to install new mappings.
> 
>   BTW this could fix the missing fact the all subscriber mapping
>   requires zero internal port and protocol.

But we don't want a host to remove mappings for another host, unless
THIRD_PARTY is used.  Maybe I don't understand what you're proposing.
Please bring this up in its own thread.


>  - 9.5 page 43: as written before about 9, this text has a better
> place:
> 
>    As a side-effect of creating a mapping, ICMP messages associated
> with
>    the mapping MUST be forwarded (and also translated, if appropriate)
>    for the duration of the mapping's lifetime.  This is done to ensure
>    that ICMP messages can still be used by hosts, without application
>    programmers or PCP client implementations needing to signal PCP
>    separately to create ICMP mappings for those flows.

Yes, it was moved.


>  - 9.7 page 44: I have still a concern about:
> 
>    Address for cosmetic purposes can achieve that by requesting a
> short-
>    lived mapping and then displaying the resulting External IP Address.
>    However, once that mapping expires a subsequent implicit or explicit
>    dynamic mapping might be mapped to a different external IP address.
> 
>   as it is both pejorative and useless. I strongly suggest to remove it
>   (and to keep the rest of 9.7).

Noted.  But this question comes up often, and it seems useful and necessary 
to have in the document.  Will keep it as-is.


>  - 10 page 44: I can't see why the v4 is here and BTW it contradicts
>   the NAT64 Figure 6 entry where the remote peer is IPv6, so I strongly
>   suggest:
> 
>    a remote peer's IPv4 -> a remote peer's IP

Fixed.


>  - 10 page 44: from the PEER4 and PEER6 time:
> 
>    The use of these Opcodes -> The use of this Opcode

Fixed.


>  - 10.1 page 45 (Requested Lifetime): I note this as I have a concern
>   I am discussing.
> 
>  - 10.1 page 46 (twice): the word 'preference' in the two Suggested
>   and even the word 'Suggested' itself don't match the implicit
>   PREFER_FAILURE semantic.

I don't understand what change you're wanting to the document.


>  - 10.1 page 46 (Remote Peer IP Address): add or replace the trailing
> 
>       ... and an IPv4 address is
>       represented using the IPv4-mapped address syntax (80 bits of
>       zeros, 16 bits of ones, and 32 bits of the IPv4 address).
> 
>    by a reference to Section 5?

Done.

>  - 10.2 page 48: IMHO the 'If sent before' and 'If sent after'
>   paragraphs should not get a particular indent.
> 
>  - 10.2 page 48: please change
> 
>   ... will respond with a PCP error.
> 
>  ->
> 
>   ... will respond with a CANNOT_PROVIDE_EXTERNAL_PORT error.

Done.

>  - 10.3 page 49: again I note this as I have a concern about it
>   I am discussing.
> 
>    The PEER Opcode MAY reduce the lifetime of an existing implicit
>    dynamic mapping created by PEER; this is implementation-dependent.
> 
>   same for:
> 
>    Some transport protocols signal the end of a connection (e.g., TCP
>    FIN, TCP RST, SCTP SHUTDOWN).  After a successful PEER response is
>    sent, the receipt of such a transport-specific message MUST NOT
> cause
>    the mapping to be destroyed.  Rather, the mapping is maintained
> until
>    the PEER-signaled lifetime expires.  If the PCP client wishes to
>    terminate the mapping prior to this, it will send a PEER request
> with
>    Lifetime set to 0, which MAY be honored by the PCP server; as stated
>    earlier, that is implementation-dependent.
> 
>   which BTW says the opposite of the previous paragraph.

Let's discuss in a separate thread.


>  - 10.4 page 50: I suggest:
> 
>    inside->outside -> from inside to outside

Fixed.


>  - 11.1 page 51: I suggest to consolidate this with 9.5:
> 
>       ... If the
>       Option Length is zero, there is no Internal IP address for this
>       mapping and this indicates "all Internal IPv4 and IPv6 Addresses
>       for which this client is authorized" which is used to delete all
>       pre-existing mappings with the MAP Opcode.
> 
>   and page 52:
> 
>    A PCP client can delete all PCP-created explicit dynamic mappings
>    (i.e., those created by PCP MAP requests) that it is authorized to
>    delete by sending a PCP MAP request including a zero-length
>    THIRD_PARTY Option.
> 
>   BTW I suggest to add the internal port and protocol MUST be zero
>   in this case.

Done.


>  - 11.2 page 53: at one exception, the text is still about
>   an 'external port only' (vs. 'external address and port') version
>   of the PREFER_FAILURE option: it clearly needs to be updated!

Done.


>  - 11.2 pages 53 and 54: again I note this as I have a concern
>   I am discussing:
> 
>    This Option exists solely for use by UPnP IGD interworking
>    ...
>    adopt PCP natively and the need for UPnP IGD interworking declines.

Noted.


>  - 11.3 page 54 (remark only): some implementations also filter out
>   incoming (i.e., received on the not public-facing interface) packets
>   as it doesn't make sense to drop only the traffic one way.
>   (BTW the text is correct as the from the Internet way is
>    the critical one for the filtering).
> 
>  - 11.3 page 55: this text could be improved to take into account
>   a possible error response with an UNPROCESSED added option:
> 
>       Maximum occurrences: as many as fit within maximum PCP message
>       size

There is already sufficient admonishment in the general PCP 
section about message length.


>  - 11.3 page 55: I have another MALFORMED_OPTION case where the
>   address has one bit after its prefix length, i.e., something
>   like 192.168.0.0/8. IMHO these cases don't have to be exhaustive
>   so it is not a request to add such a thing.

-d


> Regards
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Thu Oct 27 17:08:26 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 484A411E8093 for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 17:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.676
X-Spam-Level: 
X-Spam-Status: No, score=-105.676 tagged_above=-999 required=5 tests=[AWL=0.923, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VqYwmiqbot0R for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 17:08:25 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id B69FA11E808F for <pcp@ietf.org>; Thu, 27 Oct 2011 17:08:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1590; q=dns/txt; s=iport; t=1319760505; x=1320970105; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=EF0dShe2EJfJHrIWcqo+tVYifNxJbV1OpvU++I2M7qA=; b=arVdM+rFAI+VY0zcnzsStwQd6sgPyXfE52nvutzMMzwTd6zyHJvoOQ7n cQhsEFFneFvr8U5Es6NGj+8A5qNbkqEX68vBY5JLazdnaZdMq+7tZzXQ/ qFPKaETc1NeLNV1WDH13Rbg3eGK/FNKP3trwAxpmsPKBYviuWfO82glTJ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtgAAGLxqU6rRDoG/2dsb2JhbABCmhGBa41mgQWBcgEBAQMBAQEBBQoBFxA0EAcBAwIJDwEBBAEBKAcZDhUKCQgBAQQBEgsQB4dgCJcGAZ4pBIh+BIgGngY
X-IronPort-AV: E=Sophos;i="4.69,415,1315180800"; d="scan'208";a="10823218"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 28 Oct 2011 00:08:25 +0000
Received: from dwingWS ([128.107.106.79]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9S08Poc000451; Fri, 28 Oct 2011 00:08:25 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110261507.p9QF7701007351@givry.fdupont.fr>
In-Reply-To: <201110261507.p9QF7701007351@givry.fdupont.fr>
Date: Thu, 27 Oct 2011 17:08:25 -0700
Message-ID: <103401cc9505$b66b1d30$23415790$@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: AcyT8PDmlyM3QfAZQuSIm/TVCfShYgBFJC8Q
Content-Language: en-us
Subject: Re: [pcp] UNPROCESSED with SUCCESS
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, 28 Oct 2011 00:08:26 -0000

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Wednesday, October 26, 2011 8:07 AM
> To: pcp@ietf.org
> Subject: [pcp] UNPROCESSED with SUCCESS
> 
> In base 16 7.7.1 page 26, UNPROCESSED is defined with:
> 
>       May appear in: responses, and only if the result code is non-
> zero.
> 
> I'd like to relax this to handle a corner case: a MAP request with at
> least
> a FILTER option which matches a static mapping. The meaning is the
> FILTERs
> don't make sense (in particular the MAP request doesn't change them) so
> they are unprocessed, but the request still returns a SUCCESS.
> 
> BTW there are other solutions but worse, for instance an UNSUPP_OPTION
> which suggests the PCP server doesn't support FILTER, and is not a
> SUCCESS.

Let's back away from the protocol a little bit, and think about what problem
we're trying to solve.

If the PCP client sends a MAP request with a FILTER option, the PCP client
either:

  * thinks there is an existing mapping, and is trying to adjust its
    filtering
  * wants to create a new mapping with specific filtering

It seems that the desired behavior of the protocol depends on what
we assume the PCP client is most likely to do -- no?

-d


> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: I've found inconsistencies in the "May appear in:"'s, my next
> message is abound them.
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From dwing@cisco.com  Thu Oct 27 17:20:37 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 57C7711E80AA for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 17:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.742
X-Spam-Level: 
X-Spam-Status: No, score=-105.742 tagged_above=-999 required=5 tests=[AWL=0.857, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cT1tBz2ov99b for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 17:20:35 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id E0F3611E80A5 for <pcp@ietf.org>; Thu, 27 Oct 2011 17:20:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1886; q=dns/txt; s=iport; t=1319761236; x=1320970836; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=0c++KjUbvixSwBvDppGkEydemxRGe59IUXjlQbP2k2I=; b=VigB2cDYTRX+/cw9lnWHPaQJvvgPDEnBWWCaSjvKOvtgICjsOgiNMTyY ek/zBs8WLaYSlbYOCSZOMlUGpd4jx02Lpd9lOnZLnmCedIHibA/D89hkm usHAXoR8rLbNDdWb7c5MCfybBMTxoP2+r9JutCyXdWm1wnMKI+jygRUPm Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtgAAC/1qU6rRDoG/2dsb2JhbABCmhGBa41mgQWBcgEBAQQBAQEFCgEXEDQXAQMCCQ8BAQQBASgHGQ4VCgkIAQEEARILF4dolxwBni0EiH4EiAaeBg
X-IronPort-AV: E=Sophos;i="4.69,415,1315180800"; d="scan'208";a="10812777"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 28 Oct 2011 00:20:36 +0000
Received: from dwingWS ([128.107.106.79]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9S0KZqM005765; Fri, 28 Oct 2011 00:20:35 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Francis Dupont'" <Francis.Dupont@fdupont.fr>, <pcp@ietf.org>
References: <201110261516.p9QFGECZ007874@givry.fdupont.fr>
In-Reply-To: <201110261516.p9QFGECZ007874@givry.fdupont.fr>
Date: Thu, 27 Oct 2011 17:20:35 -0700
Message-ID: <103501cc9507$69a9ff00$3cfdfd00$@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: AcyT8jghqfvSYKa+T2yaDhFjZXY47ABE9Enw
Content-Language: en-us
Subject: Re: [pcp] inconsistent options in responses
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, 28 Oct 2011 00:20:37 -0000

The MUST is too severe, because if an option is unprocessed, the
option shouldn't be in the response.  I think this is sufficient
for THIRD_PARTY, PREFER_FAILURE, and FILTER, and I changed 
them accordingly:

            <t>May appear in: requests, and MUST appear in
            successfully-processed responses</t>

-d


> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Francis Dupont
> Sent: Wednesday, October 26, 2011 8:16 AM
> To: pcp@ietf.org
> Subject: [pcp] inconsistent options in responses
> 
> With the new option style all options in a PCP request are copied to
> the
> corresponding response, so some "May appear in:" are no longer
> consistent
> so need to be upgrade:
> 
>  - 11.1 THIRD_PARTY page 51: small improvement, i.e., replace:
> 
>       May appear in: request.  May appear in response only if it
>       appeared in the associated request.
> 
>   by
> 
>       May appear in: request.  MUST appear in response if it
>       appeared in the associated request.


>  - 11.2 PREFER_FAILURE page 53: copy THIRD_PARTY spec, i.e., replace:
> 
>       May appear in: requests
> 
>   by
> 
>       May appear in: request.  MUST appear in response if it
>       appeared in the associated request.

The MUST is too severe, because if it was unprocessed it shouldn't
be in the response.

>  - 11.3 FILTER page 55: better but I suggest the same, i.e., replace:
> 
>       May appear in: requests, and MUST appear in successfully-
> processed
>       responses
> 
>   by
> 
>       May appear in: request.  MUST appear in response if it
>       appeared in the associated request.
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From pselkirk@isc.org  Thu Oct 27 18:48:14 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 CF6BC11E808D for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 18:48:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cpDfbf6JILpP for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 18:48:14 -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 4E76C11E8073 for <pcp@ietf.org>; Thu, 27 Oct 2011 18:48: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 340C9C941E; Fri, 28 Oct 2011 01:48:04 +0000 (UTC) (envelope-from pselkirk@isc.org)
Received: by bikeshed.isc.org (Postfix, from userid 10300) id 24CA0216C6B; Fri, 28 Oct 2011 01:48:04 +0000 (UTC)
From: Paul Selkirk <pselkirk@isc.org>
To: james woodyatt <jhw@apple.com>
In-Reply-To: <0CDBCDE2-21CA-4287-A893-97D67BD1318B@apple.com> (message from james woodyatt on Thu, 27 Oct 2011 13:57:00 -0700)
References: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com> <0CDBCDE2-21CA-4287-A893-97D67BD1318B@apple.com>
Date: Fri, 28 Oct 2011 01:48:04 +0000
Message-ID: <s1v62j9vqcr.fsf@bikeshed.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: pcp@ietf.org, rja.lists@gmail.com
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 01:48:14 -0000

Quoth James Woodyatt:
> I have to say I'm surprised and dismayed at the way this capability
> has been dismissed from the PCP base specification.  I would have
> thought that the critical importance of Rapid Recovery would have been
> immediately recognizable to everyone...

And yet you didn't bring it up at Quebec (where I know you were at the
WG meeting), or Prague, or at any point along the line.

> I agree with Mr. Atkinson.  I-D.ietf-pcp-base should not be approved
> unless the "Rapid Recovery" capability is immediately restored to the
> specification.

"Restored" only applies if this is viewed as NAT-PMP-bis, because it was
never in a draft-ietf-pcp-base specification.

Quoth Ran Atkinson:
> The charter is NOT limited to CGN cases, but instead is very broadly
> written to include ALL use cases involving either NAT, Firewall, or both.

And yet, I can report that all the energy in the WG has been devoted to
the CGN scenarios (NAT444, DS-Lite, and NAT64, in approximate order of
how much attention they've gotten in the last year). That's probably a
failure to attract the attention of the firewall and CPE folks.

> * If you have some other approach to solve the same operational issue,
>   please speak up.  I'm open-minded, but the time to put that on the table 
>   was really last April.

I could turn this around, and say that the time to insist on inclusion
of this feature was last April.

Note that I (as a co-author and implementor) am neither in favor of, nor
opposed to inclusion of Rapid Recovery in the base spec. OTOH, this is
the *third* WGLC on the base spec, which means we (as the WG) need to
take a rather skeptical view of any 11th-hour objections.

				paul

From rpenno@juniper.net  Thu Oct 27 18:49:22 2011
Return-Path: <rpenno@juniper.net>
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 DEDC121F847A for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 18:49:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.567
X-Spam-Level: 
X-Spam-Status: No, score=-6.567 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uS0mPcc2jWBh for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 18:49:22 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 7D57111E8073 for <pcp@ietf.org>; Thu, 27 Oct 2011 18:49:20 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP;  Thu, 27 Oct 2011 18:49:22 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 27 Oct 2011 18:47:30 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Thu, 27 Oct 2011 21:47:29 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Stuart Cheshire <cheshire@apple.com>
Date: Thu, 27 Oct 2011 21:47:31 -0400
Thread-Topic: [pcp] WG last call on draft-ietf-pcp-base-16.txt
Thread-Index: AcyU8I+AIZ+y0BoVRd+1RpuKzxC8GAAIv64D
Message-ID: <CACF57C3.5690F%rpenno@juniper.net>
In-Reply-To: <36E0DF10-3EBF-4501-8484-AD43D96B8691@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 01:49:23 -0000

Hello Stuart,

It seems we are in agreement then.

Thanks,

Reinaldo

On 10/27/11 2:36 PM, "Stuart Cheshire" <cheshire@apple.com> wrote:

> On 25 Oct, 2011, at 12:47, Reinaldo Penno wrote:
>=20
>> Hello RJ,
>>=20
>> I did not follow up due to the fact that draft-cheshire-pcp-
>> recovery-01 views things from a CPE/home perspective where
>> multicast is pervasive. As you point out, it is trying to recreate
>> NAT-PMP's functionality.
>>=20
>> My objection to draft-cheshire-pcp-recovery-01 is that relying on
>> multicast in service provider networks is not practical - although
>> fine for home networks.
>=20
> The Rapid Recovery text does not say that relying on multicast in
> service provider networks is practical, nor does it say that anyone
> should think that.
>=20
> What the Rapid Recovery text says is that multicast *is* practical in
> home networks, such as networks where DHCP is used (since a DHCP
> broadcast should generally reach the same set of hosts as an all-
> hosts multicast). Also, such home gateways typically forget all
> dynamic state when rebooted, so they have absolutely no idea who
> their erstwhile clients were, so the *only* option they have is to
> multicast a message to all potential clients saying, "Hey, I'm back."
>=20
> Therefore multicast is both necessary and sufficient for these devices.
>=20
> You may not yourself work on low-cost home gateways, but both Apple
> and Linksys do make home gateways for this market, and I would like
> those home gateways to continue to be at least as good as our
> existing NAT-PMP home gateways.
>=20
> Stuart Cheshire <cheshire@apple.com>
> * Wizard Without Portfolio, Apple Inc.
> * www.stuartcheshire.org
>=20


From cheshire@apple.com  Thu Oct 27 22:37:19 2011
Return-Path: <cheshire@apple.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 7A42121F853A for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 22:37:19 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZaBmYa-qHwR for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 22:37:18 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id CCD3A21F851F for <pcp@ietf.org>; Thu, 27 Oct 2011 22:37:18 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LTR004S3GY6KQD3@mail-out.apple.com> for pcp@ietf.org; Thu, 27 Oct 2011 22:37:18 -0700 (PDT)
X-AuditID: 11807130-b7c1bae000001553-c8-4eaa3f8d096b
Received: from kencur (kencur.apple.com [17.151.62.38]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay11.apple.com (Apple SCV relay) with SMTP id 07.4C.05459.D8F3AAE4; Thu, 27 Oct 2011 22:37:18 -0700 (PDT)
Received: from [10.0.1.201] ([173.164.252.149]) by kencur.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LTR002Y1GY5RB00@kencur.apple.com> for pcp@ietf.org; Thu, 27 Oct 2011 22:37:17 -0700 (PDT)
In-reply-to: <201110241522.p9OFM8xd033562@givry.fdupont.fr>
References: <201110241522.p9OFM8xd033562@givry.fdupont.fr>
Message-id: <122405C3-6FFD-4538-9EB0-6493712B35FE@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Thu, 27 Oct 2011 22:38:17 -0700
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMLMWRmVeSWpSXmKPExsUiON1OTbfPfpWfwcrlTBaTj/1mdWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRnP/apaCtRwVLzdaNDBeYeti5OSQEDCR2La2mxnCFpO4cG89 UJyLQ0ignUni6aObTCAJXgFBiR+T77F0MXJwMAvISxw8LwsSZhZwkdg6oYUdxBYS6GaSmPQe bCangLXE6a+fmSDiVhJ7Fr1kgRhjI7Fr9nxWiF4BiZsn+sD2sgloSbz4DHGPsICqxI5P3WC9 LED2g18TGUFsEQE9iXdXD7JD3Ckncfj0K8YJjAKzkFw3C+G6WUiuW8DIvIpRsCg1J7HS0FAv saAgJ1UvOT93EyMo6BoKDXYwrv3Jf4hRgINRiYeXs32lnxBrYllxZe4hRgkOZiUR3krRVX5C vCmJlVWpRfnxRaU5qcWHGKU5WJTEeeW0gFIC6YklqdmpqQWpRTBZJg5OqQZGvt9M7a2FInPk Hp6Q4AjItDj+rVj2T9z95Adh2l/+RYvJmDKV174/6M/7tsstvJRDMn+a18EZe16f2FAyvfKJ znrLP22JmS3spn8XfN53P7TppKcUY7D0Ni39jRaur3hP5fcdjig7wZoUdvXGJycrNq7Xt9L7 X6ww4+AXPSleeKVaoNbir6sSS3FGoqEWc1FxIgAhZwCcNgIAAA==
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (1)
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, 28 Oct 2011 05:37:19 -0000

On 24 Oct 2011, at 8:22 AM, Francis Dupont wrote:

>  - 3 page 8 (Mapping Types): web page -> web portal
>   (just a suggestion, the term "web page" is very poor IMHO)

Why "portal"?

What kind of home gateway has a web portal on it?

<http://en.wikipedia.org/wiki/Web_portal>

A web portal or links page is a web site that functions as a point of  
access to information in the World Wide Web. A portal presents  
information from diverse sources in a unified way.

Apart from the standard search engine feature, web portals offer  
other services such as e-mail, news, stock prices, information,  
databases and entertainment. Portals provide a way for enterprises to  
provide a consistent look and feel with access control and procedures  
for multiple applications and databases, which otherwise would have  
been different entities altogether.

Examples of public web portals are AOL, Excite, iGoogle, MSN,  
Netvibes, and Yahoo!.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From cheshire@apple.com  Thu Oct 27 23:28:59 2011
Return-Path: <cheshire@apple.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 1CE9B1F0C5E for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 23:28:59 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2trOyJ0Sc07G for <pcp@ietfa.amsl.com>; Thu, 27 Oct 2011 23:28:58 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 565521F0C54 for <pcp@ietf.org>; Thu, 27 Oct 2011 23:28:58 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LTR00430JBYKQG3@mail-out.apple.com> for pcp@ietf.org; Thu, 27 Oct 2011 23:28:53 -0700 (PDT)
X-AuditID: 11807137-b7c56ae0000051ed-33-4eaa4ba545d3
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay16.apple.com (Apple SCV relay) with SMTP id AD.CA.20973.5AB4AAE4; Thu, 27 Oct 2011 23:28:53 -0700 (PDT)
Received: from [10.0.1.201] ([173.164.252.149]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LTR006OXJC5XI00@koseret.apple.com> for pcp@ietf.org; Thu, 27 Oct 2011 23:28:53 -0700 (PDT)
In-reply-to: <201110241522.p9OFM8xd033562@givry.fdupont.fr>
References: <201110241522.p9OFM8xd033562@givry.fdupont.fr>
Message-id: <B2A742C5-4490-4BE4-BC2D-94DB402B600A@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Thu, 27 Oct 2011 23:29:52 -0700
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKLMWRmVeSWpSXmKPExsUiON1OXXep9yo/g2/XNS0mH/vN6sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujG9tL5gLHjNV7DxwhrWBcTFTFyMnh4SAiUT3+2PMELaYxIV7 69m6GLk4hAQ6mSTa7j5jBUnwCghK/Jh8j6WLkYODWUBe4uB5WZAws4ClxNX325gh6vuZJCaf vAg2lFPAWuL0189gtpCAlcSeRS9ZIObYSLQ2PGOBaBaQuHmiD2wxm4CWxIvPV9hAbGEBVYkd n7rBelmA7MVHWthBbBEBPYl3Vw+yQxwqJ3H49CvGCYwCs5CcNwvhvFlIzlvAyLyKUbAoNSex 0tBML7GgICdVLzk/dxMjKPAaCs13MG7/K3eIUYCDUYmHl6N9pZ8Qa2JZcWXuIUYJDmYlEd5K 0VV+QrwpiZVVqUX58UWlOanFhxilOViUxHmVtIBSAumJJanZqakFqUUwWSYOTqkGxrPrfna2 lGbeuN+luaJ31fsD7c+eOCswMor5eyvmeXpoSK7xuX/8dsO6kln9DIGSvyrCvCQDnV92HbGq ebqgyVtxzefONf+Wvbs9Z5Zkn/2O2tR5UUdrXdtU3O8beKT1dfb+vMOp1D7NsWNTXeTdq7Vm Ji82+R05aqn67sU3QYETso0v3xQ4KbEUZyQaajEXFScCAMSdjSQ4AgAA
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (1)
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, 28 Oct 2011 06:28:59 -0000

On 24 Oct 2011, at 8:22 AM, Francis Dupont wrote:

>  - 6.3 page 15: 1024-4*number_of_options -> 1020-4*number_of_options
>   (i.e., please add the UNPROCESSED option header too)

Where does this number come from? Why "4*number_of_options"?

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From cheshire@apple.com  Fri Oct 28 01:39:02 2011
Return-Path: <cheshire@apple.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 BF95421F8922 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 01:39:02 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uPxBhiOxUfcD for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 01:38:59 -0700 (PDT)
Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id B0EB121F86F6 for <pcp@ietf.org>; Fri, 28 Oct 2011 01:38:59 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LTR00MT8PCLBFB0@mail-out.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 01:38:58 -0700 (PDT)
X-AuditID: 11807137-b7c56ae0000051ed-d2-4eaa6a21c20c
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay16.apple.com (Apple SCV relay) with SMTP id 25.95.20973.22A6AAE4; Fri, 28 Oct 2011 01:38:58 -0700 (PDT)
Received: from [10.0.1.201] ([173.164.252.149]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LTR00JQWPCX1W40@cardamom.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 01:38:57 -0700 (PDT)
In-reply-to: <9B2444EE-1C2C-4B4F-8BCD-C7D30BA050E6@juniper.net>
References: <20111021192647.15411.29692.idtracker@ietfa.amsl.com> <9B2444EE-1C2C-4B4F-8BCD-C7D30BA050E6@juniper.net>
Message-id: <37526BA0-6EB9-4AC4-845D-261B0D2A2300@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Fri, 28 Oct 2011 01:39:57 -0700
To: pcp@ietf.org
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJLMWRmVeSWpSXmKPExsUiON1OVVcpa5WfQecLNovJx36zOjB6LFny kymAMYrLJiU1J7MstUjfLoEr4+zXvawFPQ+YKt6/ucXWwLj8J2MXIyeHhICJxJv7i9ggbDGJ C/fWg9lCAq1MEpf/l3YxcgHZE5kkFt5cDNTAwcErYCTRsaICpIZTwF7i4Ps3TBD1ZRKzpm0B m8ks4CKx5+ZpMJtXwEai++Q6doi4vMTmNW+ZQWw2AS2JF5+vsIGMFBawlXgywwgkzCKgKvGl 9SYriC0iICDxe/VlJojT5CQOn37FOIGRfxbCEbOQLJuFZMECRuZVjIJFqTmJlYZmeokFBTmp esn5uZsYQQHWUGi+g3H7X7lDjAIcjEo8vBztK/2EWBPLiitzDzFKcDArifBWiq7yE+JNSays Si3Kjy8qzUktPsQozcGiJM6rpAWUEkhPLEnNTk0tSC2CyTJxcEo1MLZkPK+f0K73wODA0jlX 73Nf23JP1Ynb+vzTEzdTNgvv37PFzGqV1amT7xquLWHYqcnv9G6VH9uUhZ7/9AM3PpPb5v7M Y+bXV7uqDGqzl7WbvBZYsk22JnzFK/aE+u+zxaS7ggL+CJTum2Y3T727eOu6/ENL9lzXaj9b t2Fv7D5mC7tDHuL7nlQosRRnJBpqMRcVJwIABpGZESwCAAA=
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 08:39:03 -0000

On 21 Oct 2011, at 12:34 PM, Alain Durand wrote:

> The PCP wg chairs would like to issue a one week wg last call on  
> draft-ietf-pcp-base-16.

I have made some minor edits for readability, spelling, consistency,  
ambiguity, etc. For transparency, these are attached below.

I also have some more substantive comments, which I will try to send  
to the list tomorrow.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org

Index: draft-ietf-pcp-base.xml
===================================================================
--- draft-ietf-pcp-base.xml	(revision 192)
+++ draft-ietf-pcp-base.xml	(working copy)
@@ -175,7 +175,7 @@
              <t>IPv4 and <xref target="RFC6092">IPv6 simple firewall
              control</xref></t>

-            <t><xref target="RFC6296">NPTv6</xref></t>
+            <t><xref target="RFC6296">IPv6-to-IPv6 Network Prefix  
Translation (NPTv6)</xref></t>

            </list></t>
        </section>
@@ -192,7 +192,8 @@
        <section anchor="single_homed" title="Single-homed Customer  
Premises Network">
          <t>PCP assumes a single-homed IP address model. That is,  
for a given
          IP address of a host, only one default route exists to  
reach the
-        Internet. This is important because after a PCP mapping is  
created and
+        Internet from that source IP address.
+        This is important because after a PCP mapping is created and
          an inbound packet (e.g., TCP SYN) arrives at the host, the  
outbound
          response (e.g., TCP SYNACK) has to go through the same path  
so it is
          seen by the firewall or rewritten by the NAT. This  
restriction exists
@@ -245,11 +246,8 @@
            request for that Internal Address and Port may be assigned
            yet another different External Port.  This term encompasses
            both Address-Dependent Mapping and Address and
-          Port-Dependent Mapping
-          from <xref target="RFC4787"></xref>.</t>
+          Port-Dependent Mapping <xref target="RFC4787"></xref>.</t>

-
-
            <t hangText="Remote Peer Address:"><vspace  
blankLines="0" />The
            address of a Remote Peer, as seen by the Internal Host. A  
Remote
            Address is generally a publicly routable address. In the  
case of a
@@ -277,8 +275,8 @@
            the internal IP and port, and vice versa. In the case of  
a pure
            firewall, the "Mapping" is the identity function,  
translating an
            internal IP address and port number to the same external  
IP address
-          and port number. Firewall filtering, applied to that identity
-          function, is separate from the mapping itself.</t>
+          and port number. Firewall filtering, applied in addition  
to that identity
+          mapping function, is separate from the mapping itself.</t>

            <t hangText="Mapping Types:"><vspace blankLines="0" />There
            are three different ways to create mappings: implicit
@@ -332,7 +330,7 @@

            <t hangText="Interworking Function:"><vspace  
blankLines="0" />A
            functional element responsible for translating or  
proxying another
-          protocol to PCP. For example interworking between
+          protocol to PCP. For example interworking
            <xref target="IGD">UPnP IGD</xref> with PCP.</t>

            <t hangText="Subscriber:"><vspace blankLines="0" /> The  
unit of
@@ -390,8 +388,8 @@
  deny unsolicited traffic from the Internet.  Some firewall devices  
deny
  certain unsolicited traffic from the Internet (e.g., TCP, UDP to
  most ports) but allow certain other unsolicited traffic from the
-Internet (e.g., UDP port 500 and IPsec ESP as described in
-<xref target="RFC6092"></xref>).  Such default filtering (or lack
+Internet (e.g., UDP port 500 and IPsec ESP)
+<xref target="RFC6092"></xref>.  Such default filtering (or lack
  thereof) is out of scope of PCP itself.  If a device supports PCP and
  wants to receive traffic, and does not possess knowledge of such
  filtering, it SHOULD use PCP to create the necessary mappings to  
receive
@@ -418,7 +416,7 @@

        <t>When checking for an IPv4-mapped IPv6 address, all of the
        first 96 bits MUST be checked for the pattern -- it is not
-      sufficient to check for 0xFF in bits 81-96.</t>
+      sufficient to check for ones in bits 81-96.</t>

        <t>The all-zeroes IPv6 address is expressed by filling the
        fixed-size 128-bit IP address field with all zeroes (::).</t>
@@ -530,12 +528,12 @@
          </figure>

          <t>These fields are described below:<list style="hanging">
-            <t hangText="Version:">Responses MUST use version 1.</t>
+            <t hangText="Version:">Responses MUST use version 1.  
This is set by the server.</t>

              <t hangText="R:">Indicates Request (0) or Response (1).  
All
-            Responses MUST use 1.</t>
+            Responses MUST use 1. This is set by the server.</t>

-            <t hangText="Opcode:">The 7-bit Opcode value, copied  
from the
+            <t hangText="Opcode:">The 7-bit Opcode value. The server  
copies this value from the
              request.</t>

              <t hangText="Reserved:">8 reserved bits, MUST be sent  
as 0, MUST
@@ -554,13 +552,17 @@
              mapping. If future Opcodes are defined that do not have  
a lifetime
              associated with them, then in success responses for  
those Opcodes
              the Lifetime MUST be set to zero on transmission and  
MUST be
-            ignored on reception.</t>
+            ignored on reception. This is set by the server.</t>

              <t hangText="Epoch:">The server's Epoch value. See
              <xref target="epoch"></xref> for discussion. This value  
is set by the server, in both success and error responses.</t>

              <t hangText="Reserved:">96 reserved bits, MUST be sent  
as 0, MUST
-            be ignored when received. This is set by the server.</t>
+            be ignored when received. This is set by the server.
+            This padding exists so that for unrecognized requests,  
the server
+            can blindly copy an entire request message into a response
+            message and have that response make some kind of  
reasonable sense
+            to the recipient.</t>

            </list></t>
        </section>
@@ -621,18 +623,17 @@
              <t hangText="Option Length:">16 bits. Indicates the  
length of the
              enclosed data, in octets. Options with length of 0 are  
allowed.
              Options that are not a multiple of four octets long are  
followed
-            by one, two, or three octets of zeros to pad their  
effective length
+            by one, two, or three zero octets to pad their effective  
length
              in the packet to be a multiple of four octets. The  
Option Length
-            reflects the semantic length of the option, not  
including the
+            reflects the semantic length of the option, not  
including any
              padding octets.</t>

-            <t hangText="data:">Option data. The Option data MUST  
end on a
-            32-bit boundary, padded with 0's when necessary.</t>
+            <t hangText="data:">Option data.</t>
            </list></t>

          <t>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
+        state 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
@@ -643,7 +644,6 @@
          by sending messages that don't exceed 1020-4*number_of_options
          octets.</t>

-
          <t>If, while processing an Option, an error is encountered  
that causes
          a PCP error response to be generated, the PCP request MUST  
cause no
          state change in the PCP server or the PCP-controlled device  
(i.e., it
@@ -658,8 +658,8 @@
  by the PCP server, the PCP server MUST respond with
          the MALFORMED_OPTION result code; if this occurs in a  
response, the
          PCP client processes the first occurrence and MAY log an  
error.
-        If an invalid option
-        length is encountered (e.g., option length extends beyond the
+        If the PCP server encounters an invalid option
+        (e.g., option length extends beyond the
          length of the PCP Opcode itself), the error  
MALFORMED_OPTION SHOULD
          be returned (rather than MALFORMED_REQUEST), as that helps the
          client better understand how the packet was malformed.  The
@@ -684,7 +684,7 @@

          <t>PCP clients are free to ignore any or all Options  
included in
          responses, although naturally if a client explicitly  
requests an
-        Option where correct handling of that Option requires  
processing the
+        Option where correct execution of that Option requires  
processing the
          Option data in the response, that client is expected to  
implement code
          to do that.</t>

@@ -696,9 +696,9 @@
          is valid only for the MAP Opcode (for the PEER Opcode it  
would have no
          meaning).</t>

+        <?rfc needLines="9" ?>
          <t>Option definitions MUST include the information below:</t>

-        <?rfc needLines="7" ?>
          <t><list style="empty">
              <?rfc subcompact="yes"?>
              <t>Option Name: &lt;mnemonic&gt;</t>
@@ -765,7 +765,7 @@
              example, the NAT device cannot create more mappings at
              this time, is short of CPU cycles or memory, or due to
              some other temporary condition.  The same request may
-            succeed in the future.  This is a system-wide error, and
+            succeed in the future.  This is a system-wide error,
              different from USER_EX_QUOTA. This is a short lifetime
              error.  This can be used as a catch-all error, should no
              other error message be suitable.</t>
@@ -776,7 +776,7 @@
              <t hangText="10">USER_EX_QUOTA: Mapping would exceed  
user's port
              quota. This is a short lifetime error.</t>

-            <t hangText="11">CANNOT_PROVIDE_EXTERNAL: the requested
+            <t hangText="11">CANNOT_PROVIDE_EXTERNAL: the suggested
              external port and/or external address cannot be provided.
              This error MUST only be returned for PEER requests, for
              MAP requests that included the PREFER_FAILURE Option
@@ -855,7 +855,9 @@
          the timer expires, the timer is doubled (to 4 seconds) and  
the request
          is re-transmitted. If no response is received before the timer
          expires, the timer is doubled again (to 8 seconds) and the  
request is
-        re-transmitted.</t>
+        re-transmitted again, and so on, up to a maximum retransmission
+        interval of fifteen minutes, at which point the PCP request is
+        re-transmitted once every fifteen minutes until it is  
sucessfully answered.</t>

          <t>Once a PCP client has successfully received a response  
from a PCP
          server on that interface, it sends subsequent PCP requests  
to that
@@ -929,12 +931,12 @@
          code to MALFORMED_REQUEST, and zero-padding the response to a
          multiple of 4 octets if necessary.</t>

-        <t>The PCP server compares the IP address (from the
+        <t>The PCP server compares the source IP address (from the  
received
  IP header) with the field PCP Client IP Adddress.  If they do not  
match, the error ADDRESS_MISMATCH MUST be
  returned.  This is done to detect and prevent accidental use of PCP
  where a non-PCP-aware NAT exists between the PCP client and PCP
  server.  If the PCP client wants such a mapping it needs to ensure the
-PCP field matches the IP address from the perspective of the PCP  
server.</t>
+PCP field matches its apparent IP address from the perspective of  
the PCP server.</t>

          <t>Error responses have the same packet layout as success  
responses,
          with fields from the request copied into the response, and  
fields
@@ -1074,7 +1076,7 @@
          <list style="symbols">

          <t>If this is the first PCP response the client has  
received from
-        this PCP server, it is treated as necessarily valid, otherwise
+        this PCP server, the Epoch time value is treated as  
necessarily valid, otherwise

          <list style="symbols">

@@ -1085,22 +1087,22 @@

          <list style="symbols">

-        <t>The client computes the difference between the
+        <t>The client computes the difference between its
          <vspace />
-        current PCP server Epoch time value (current_server_time)  
and the
+        current local time value (current_client_time) and the
          <vspace />
-        previously received Epoch time value (previous_server_time):
+        time the previous PCP response was received from this PCP
+        server (previous_client_time):
          <vspace />
-        server_delta = current_server_time - previous_server_time;</t>
+        client_delta = current_client_time - previous_client_time;</t>

          <t>The client computes the difference between the
          <vspace />
-        current local time value (current_client_time) and the
+        current PCP server Epoch time value (current_server_time)  
and the
          <vspace />
-        time the previous PCP response was received from this PCP
-        server (previous_client_time):
+        previously received Epoch time value (previous_server_time):
          <vspace />
-        client_delta = current_client_time - previous_client_time;</t>
+        server_delta = current_server_time - previous_server_time;</t>

          <t>If client_delta+2 < server_delta - server_delta/8
          <vspace />
@@ -1116,9 +1118,9 @@

          <t>The client records the current time values for use in  
its next comparison:
          <vspace />
-        previous_server_time = current_server_time
+        previous_client_time = current_client_time
          <vspace />
-        previous_client_time = current_client_time</t>
+        previous_server_time = current_server_time</t>

          </list></t>

@@ -1138,8 +1140,10 @@
          been discussed by the PCP working group. If we were to  
require more
          accurate clocks in low-cost devices then more restrictive  
error
          tolerances could be imposed, such as "/64" or "/256".</t>
-

+        <t>Note: The calculations above are constructed to allow
+        client_delta and server_delta to be computed as unsigned  
values.</t>
+
        </section>

        <section anchor="version" title="Version Negotiation">
@@ -1168,7 +1172,7 @@
              support a contiguous range of versions -- i.e., a  
lowest version
              and a highest version and all versions in between.</t>

-            <t>The client sends first request using highest (i.e.,  
presumably
+            <t>The client sends its first request using the highest  
(i.e., presumably
              'best') version number it supports.</t>

              <t>If the server supports that version it responds  
normally.</t>
@@ -1207,8 +1211,7 @@
            response, shown in <xref target="fig_unprocessed"></ 
xref>. This
            helps with debugging interactions between the PCP client  
and PCP
            server. This Option MUST NOT appear more than once in a PCP
-          response. The unprocessed Options are listed once, and the  
Option
-          data is zero-filled to the necessary 32 bit boundary. If a  
certain
+          response. The unprocessed Options are each listed at most  
once. If a certain
            Option appeared more than once in the PCP request, that  
Option value
            MAY appear once or as many times as it occurred in the  
request. The
            order of the Options in the PCP request has no  
relationship with the
@@ -1272,9 +1275,9 @@
        its IPv6 interface), and if to send one or two MAP requests for
        each of its interfaces (e.g., if the PCP client has only an IPv4
        address but wants both IPv6 and IPv4 listeners, it sends a MAP
-      request containing the all-zeros IPv6 address in the Requested
+      request containing the all-zeros IPv6 address in the Suggested
        External Address field, and sends a second MAP request  
containing
-      the all-zeros IPv4 address in the Requested External Address  
field.
+      the all-zeros IPv4 address in the Suggested External Address  
field.
        If the PCP
        client has both an IPv4 and IPv6 address, and only wants an IPv4
        listener, it sends one MAP request from its IPv4 interface (if
@@ -1288,15 +1291,15 @@

        <t>It is REQUIRED that the PCP-controlled device assign the same
        external IP address to PCP-created explicit dynamic mappings and
-      to implicit dynamic mappings for a given Internal Host. In the
+      to implicit dynamic mappings for a given Internal Address. In the
        absence of a PCP option indicating otherwise, it is
-      REQUIRED that PCP-created explicit dynamic mappings be assigned
+      REQUIRED that all PCP-created explicit dynamic mappings be  
assigned
        the same external IP address.  It is RECOMMENDED that static
-      mappings for that Internal Host (e.g., those created by a
+      mappings for that Internal Address (e.g., those created by a
        command-line interface on the PCP server or PCP-controlled
-      device) also be assigned to the same IP address. Once all
-      internal addresses assigned to a given Internal Host have no
-      implicit dynamic mappings and have no explicit dynamic mappings
+      device) also be assigned to the same IP address. Once an
+      Internal Address has no
+      implicit dynamic mappings and no explicit dynamic mappings
        in the PCP-controlled device, a subsequent PCP request for that
        Internal Address MAY be assigned to a different External
        Address. Generally, this re-assignment would occur when a CGN
@@ -1320,7 +1323,7 @@
  address of the PCP packet itself, 'internal' is the Internal IP
  Address field of the THIRD_PARTY Option (if present) or the same as
  the source address of the PCP packet iself (if the THIRD_PARTY Option
-is not present), 'external' is the Requested External Address field of
+is not present), 'external' is the Suggested External Address field of
  the MAP or PEER request, the 'remote peer' is the Remote Peer IP
  Address of the PEER request or the FILTER option of the MAP
  request.</preamble>
@@ -1353,8 +1356,6 @@
          port. Conceptually implicit and explicit mappings are
          different "layers" in the NAT forwarding state database.</t>

-
-
        <section anchor="operating_a_server" title="For Operating a  
Server">
          <t>A host operating a server (e.g., a web server) listens  
for traffic
          on a port, but the server never initiates traffic from that  
port. For
@@ -1390,6 +1391,7 @@
       * 1. Sending the first request
       * 2. Retransmitting requests due to packet loss
       * 3. Resending a request due to impending lease expiration
+     * 4. Resending a request due to server state loss
       * The PCP packet sent is identical in all cases, apart from the
       * Suggested External Address and Port which may differ between
       * (1), (2), and (3).
@@ -1481,6 +1483,7 @@
       * 1. Sending the first request
       * 2. Retransmitting requests due to packet loss
       * 3. Resending a request due to impending lease expiration
+     * 4. Resending a request due to server state loss
       * The PCP packet sent is identical in all cases, apart from the
       * Suggested External Address and Port which may differ between
       * (1), (2), and (3).
@@ -1560,6 +1563,7 @@
       * 1. Sending the first request
       * 2. Retransmitting requests due to packet loss
       * 3. Resending a request due to impending lease expiration
+     * 4. Resending a request due to server state loss
       * The PCP packet sent is identical in all cases, apart from the
       * Suggested External Address and Port which may differ between
       * (1), (2), and (3).
@@ -1614,7 +1618,7 @@
        <t>This section defines an Opcode which controls forwarding  
from a NAT
        (or firewall) to an Internal Host.<list hangIndent="8"  
style="hanging">
            <t hangText="  MAP:">Create an explicit dynamic mapping  
between an
-          Internal Address and an External IP address.</t>
+          Internal Address + Port and an External Address + Port.</t>
          </list></t>

        <t>PCP Servers SHOULD
@@ -1654,7 +1658,7 @@
        appropriate) for the duration of the mapping's lifetime. This  
is done
        to ensure that ICMP messages can still be used by hosts, without
        application programmers or PCP client implementations needing to
-      signal PCP separately to create ICMP mappings for those  
flows.</t>
+      use PCP separately to create ICMP mappings for those flows.</t>

        <t>The operation of the MAP Opcode is described in this  
section.</t>

@@ -1747,11 +1751,16 @@
          </figure>

          <t>These fields are described below:<list style="hanging">
-            <t hangText="Lifetime (in common header):">On a success  
response,
-            this indicates the lifetime for this mapping, in  
seconds. On an
-            error response, this indicates how long clients should  
assume
-            they'll get the same error response from the PCP server  
if they
-            repeat the same request.</t>
+            <t hangText="Lifetime (in common header):">On an error
+            response, this indicates how long clients should assume
+            they'll get the same error response from the PCP server if
+            they repeat the same request. On a success response, this
+            indicates the lifetime for this mapping, in seconds.
+            The PCP client SHOULD impose an upper limit on this  
returned
+            Assigned Lifetime value, and 24 hours is RECOMMENDED. This
+            means if the PCP server returns an absurdly long Assigned
+            Lifetime (e.g., 5 years), the PCP client will behave as if
+            it received a more sane value (e.g., 24 hours).</t>

              <t hangText="Protocol:">Copied from the request.</t>

@@ -1818,12 +1827,6 @@
          requests MUST NOT be sent less than four seconds apart (a PCP
          client MUST NOT send a flood of ever-closer-together requests
          in the last few seconds before a mapping expires).</t>
-
-        <t>The PCP client SHOULD impose an upper limit on this
-        returned Assigned Lifetime value, and 24 hours is RECOMMENDED.
-        This means if the PCP server returns an absurdly long Assigned
-        Lifetime (e.g., 5 years), the PCP client will behave as if it
-        received a more sane value (e.g., 24 hours).</t>
          </section>
        </section>

@@ -1833,10 +1836,9 @@
          Opcode. Processing SHOULD be performed in the order of the  
following
          paragraphs.</t>

-        <t>The following fields from the MAP request are copied into
-        the MAP response: Protocol, Internal Port, Requested External
-        Address, and (if present and processed by the PCP server) the
-        THIRD_PARTY Option.</t>
+        <t>The Protocol and Internal Port fields from the MAP request
+        are copied into the MAP response. If present and processed  
by the PCP server
+        the THIRD_PARTY Option is also copied into the MAP  
response.</t>

          <t>If the Requested Lifetime is non-zero, it indicates a
          request to create a mapping or extend the lifetime of an
@@ -1884,7 +1886,7 @@
          External Address and Port in its response, regardless of the
          Suggested External Address and Port in the request.  If a
          mapping already exists for the requested Internal Address  
and Port
-        the request contains the PREFER_FAILURE Option, but the
+        and the request contains the PREFER_FAILURE Option, but the
          Suggested External Address and Port do not match the actual
          External Address and Port of the already existing mapping, the
          error CANNOT_PROVIDE_EXTERNAL is returned.  If an implicit
@@ -1964,8 +1966,9 @@
          receives a PCP response for the MAP Opcode.</t>

          <t>After performing common PCP response processing, the  
response is
-        further matched with an outstanding request by comparing the  
protocol,
-        internal IP address, and internal port. Other fields are not  
compared,
+        further matched with an outstanding request by comparing the  
Protocol
+        and Internal Port (and, if THIRD_PARTY, Internal IP Address).
+        Other fields are not compared,
          because the PCP server sets those fields.</t>

          <t>On a success response, the PCP client can use the  
External IP
@@ -1979,13 +1982,12 @@
          in <xref target="map-opcode_client_operation"></xref>,  
except that the
          Suggested External Address and Port SHOULD be set to the  
values
          received in the response. From the PCP server's point of  
view a MAP
-        request to renew a mapping is identical to a MAP request to  
request a
+        request to renew a mapping is identical to a MAP request to  
create a
          new mapping, and is handled identically.  Indeed, in the  
event of PCP
          server state loss, a renewal request from a PCP client will  
appear to
-        the server to be a request for a new mapping, with a particular
+        the server to be a request to create a new mapping, with a  
particular
          Suggested External Address and Port, which happens to be  
what the PCP
-        server previously assigned. See also
-        <xref target="maintaining_mappings"></xref>.</t>
+        server previously assigned. See also <xref target="reboot"></ 
xref>.</t>

          <t>On an error response, the client SHOULD NOT repeat the  
same request
          to the same PCP server within the lifetime returned in the
@@ -2022,8 +2024,13 @@
          that already exists as a static mapping, the PCP server will
          return a successful result, confirming that the requested
          mapping exists. The lifetime the PCP server returns for such a
-        static mapping SHOULD be 4294967295 (0xFFFFFFFF).  There is no
-        need for a PCP client to renew a static mapping.</t>
+        static mapping SHOULD be 4294967295 (0xFFFFFFFF). Upon  
receipt of
+        such a MAP response with an absurdly long Assigned Lifetime the
+        PCP client SHOULD behave as if it received a more sane value
+        (e.g., 24 hours), and renew the mapping accordingly, to ensure
+        that if the static mapping is removed the client will continue
+        to maintain the mapping it desires.
+        </t>

          <t>If the requested lifetime is zero then: <list  
style="symbols">
              <t>If both the internal port and protocol are non-zero, it
@@ -2092,7 +2099,7 @@
        </section>

        <section anchor="renumbering" title="Address Change Events">
-        <t>A customer premises router might obtain a new IP address,  
for a
+        <t>A customer premises router might obtain a new External IP  
address, for a
          variety of reasons including a reboot, power outage, DHCP  
lease
          expiry, or other action by the ISP. If this occurs, traffic  
forwarded
          to the host's previous address might be delivered to  
another host
@@ -2166,8 +2173,8 @@
        support if they wish.</t>

        <t>Because a mapping created or managed by PEER behaves
-      almost exactly as if an implicit dynamic mapping were created by
-      a packet sent by the host (e.g., TCP SYN sent by the host),
+      almost exactly like an implicit dynamic mapping created as a  
side-effect of
+      a packet (e.g., TCP SYN) sent by the host,
        mappings created or managed using PCP PEER requests may be
        Endpoint Independent Mappings (EIM) or Endpoint Dependent  
Mappings
        (EDM), with Endpoint Independent Filtering (EIF) or Endpoint  
Dependent
@@ -2399,10 +2406,10 @@
          arriving at the NAT gateway first, and allow PEER to be  
used to
          recreate an implicit dynamic mapping (see last paragraph of
          <xref target="reboot"></xref>).  If the requested mapping does
-        not yet exist, but Suggested External Address and Port cannot
+        not yet exist, and Suggested External Address and Port cannot
          be honored, the error CANNOT_PROVIDE_EXTERNAL is
          returned.  If the requested mapping already exists, it is
-        a request to modify that existing mapping.</t>
+        a request to modify the lifetime of that existing mapping.</t>

          <t>The PEER Opcode MAY reduce the lifetime of an existing
          implicit dynamic mapping created by PEER; this is
@@ -2455,7 +2462,7 @@

          <t>After performing common PCP response processing, the  
response is
          further matched with a request by comparing the protocol,  
internal IP
-        address, internal port, remote peer address and remote peer  
port.
+        address (if THIRD_PARTY), internal port, remote peer address  
and remote peer port.
          Other fields are not compared, because the PCP server  
changes those
          fields to provide information about the mapping created by the
          Opcode.</t>
@@ -2628,14 +2635,14 @@
              <?rfc subcompact="no"?>
          </list></t>

-        <t>The result code CANNOT_PROVIDE_EXTERNAL is returned if both
-        the Suggested External Port and Suggested External Address
+        <t>The result code CANNOT_PROVIDE_EXTERNAL is returned if
+        the Suggested External Address and Port
          cannot be mapped. This can occur because the External Port is
          already mapped to another host's implicit dynamic mapping, an
          explicit dynamic mapping, a static mapping, or the same
          Internal Address and Port has an implicit dynamic mapping
          which is mapped to a different External Port than
-        requested. This can also occur because the External Address is
+        suggested. This can also occur because the External Address is
          no longer available (e.g., due to renumbering).  The server
          MAY set the Lifetime in the response to the remaining lifetime
          of the conflicting mapping, rounded up to the next larger
@@ -2756,7 +2763,7 @@
          MALFORMED_OPTION result code.</t>

          <t>If multiple occurrences of the FILTER Option exist in the
-        same MAP request, they are processed in the same order
+        same MAP request, they are processed in the order
          received (as per normal PCP Option processing) and they MAY
          overlap the filtering requested. If an existing mapping exists
          (with or without a filter) and the server receives a MAP
@@ -2765,7 +2772,7 @@
          lifetime of 0 and contains the FILTER Option, the error
          MALFORMED_OPTION is returned.</t>

-        <t>If any of occurrences of the FILTER Option in a request  
packet are
+        <t>If any occurrences of the FILTER Option in a request  
packet are
          not successfully processed then an error is returned (e.g.,
          MALFORMED_OPTION if one of the Options was malformed) and  
as with
          other PCP errors, returning an error causes no state to be  
changed in
@@ -2792,7 +2799,7 @@

          <t>The use of the FILTER Option can be seen as a performance
          optimization. Since all software using PCP to receive incoming
-        connections also has to deal with the case where may be  
directly
+        connections also has to deal with the case where it may be  
directly
          connected to the Internet and receive unrestricted incoming  
TCP
          connections and UDP packets, if it wishes to restrict  
incoming traffic
          to a specific source address or group of source addresses such
@@ -2854,7 +2861,7 @@
          unsuccessful at temporarily reserving the next-higher port  
for this
          PCP client, the server MUST NOT include the EVEN_PLUS_ONE  
Option in
          its response. If the server receives a PCP request with the
-        EVEN_PLUS_ONE Option for an odd-numbered requested-external- 
port, it
+        EVEN_PLUS_ONE Option for an odd-numbered suggested-external- 
port, it
          MUST return an error.</t>

          <t>This Option is permitted with the following OpCodes:  
MAP44, MAP64,
@@ -2975,8 +2982,9 @@
      <section anchor="implementation_considerations"  
title="Implementation Considerations">

        <section anchor="EDM" title="Implementing MAP with EDM port- 
mapping NAT">
-      <t>This section provides non-normative guidance that may be  
useful to
-      implementors.</t>
+        <t>This section provides non-normative guidance that may be  
useful to
+        implementers.</t>
+
          <t>For implicit dynamic mappings, some existing NAT devices  
have
          endpoint-independent mapping (EIM) behavior while other NAT  
devices
          have endpoint-dependent mapping (EDM) behavior. NATs which  
have EIM
@@ -3005,8 +3013,9 @@
        </section>

        <section title="Lifetime of Explicit and Implicit Dynamic  
Mappings">
-      <t>This section provides non-normative guidance that may be  
useful to
-      implementors.</t>
+        <t>This section provides non-normative guidance that may be  
useful to
+        implementers.</t>
+
          <t>No matter if a NAT is EIM or EDM, it is possible that  
one (or more)
          implicit dynamic mappings, using the same internal port on the
          Internal Host, might be created before or after a MAP  
request. When
@@ -3021,14 +3030,16 @@
        </section>

        <section anchor="failure" title="PCP Failure Scenarios">
-      <t>This section provides non-normative guidance that may be  
useful to
-      implementors.</t>
+        <t>This section provides non-normative guidance that may be  
useful to
+        implementers.</t>
+
          <t>If an event occurs that causes the PCP server to lose  
explicit
          dynamic mapping state (such as a crash or power outage),  
the mappings
-        created by PCP are lost. Such loss of state is expected to  
be rare in a service
-        provider environment (due to redundant power, disk drives  
for storage,
-        etc.), but more common in a residential NAT device which  
does not
-        write this information to non-volatile memory. Of course,  
due to
+        created by PCP are lost. Occasional loss of state may be  
unavoidable
+        in a residential NAT device which does not write transient
+        information to non-volatile memory. Loss of state is expected
+        to be rare in a service provider environment (due to redundant
+        power, disk drives for storage, etc.). Of course, due to
          outright failure of service provider equipment (e.g., software
          malfunction), state may still be lost.</t>

@@ -3040,7 +3051,7 @@
          <t>Further analysis of PCP failure scenarios is in
          <xref target="I-D.boucadair-pcp-failure"></xref>.</t>

-        <section anchor="reboot" title="Recreating Mappings">
+        <section title="Recreating Mappings" anchor="reboot">
  <!--
            <t>The PCP server SHOULD store mappings in persistent  
storage so
            when it is powered off or rebooted, it remembers the port  
mapping
@@ -3052,10 +3063,9 @@
            <t>However, maintaining this state is not essential for  
correct
            operation.
  -->
-      <t>This section provides non-normative guidance that may be  
useful to
-      implementors.</t>
+          <t>This section provides non-normative guidance that may  
be useful to
+          implementers.</t>

-
            <t>A mapping renewal packet is formatted identically to  
an original
            mapping request; from the point of view of the client it  
is a
            renewal of an existing mapping, but from the point of  
view of a
@@ -3065,31 +3075,35 @@
            mappings.</t>

            <t>When the PCP server loses state and begins processing  
new PCP
-          messages, its Epoch is reset and begins counting again  
from zero
-          (per the procedure of <xref target="epoch"></xref>). As  
the result
-          of receiving a packet where the Epoch field is outside the
-          expected range, indicating that a reboot or similar loss of
+          messages, its Epoch time is reset and begins counting  
again. As the result
+          of receiving a packet where the Epoch time field is  
outside the
+          expected range (<xref target="epoch"></xref>), indicating  
that a reboot or similar loss of
            state has occurred, the client can renew its port mappings
            sooner, without waiting for the normal routine renewal  
time.</t>
          </section>

          <section title="Maintaining Mappings"  
anchor="maintaining_mappings">
-      <t>This section provides non-normative guidance that may be  
useful to
-      implementors.</t>
+          <t>This section provides non-normative guidance that may  
be useful to
+          implementers.</t>
+
            <t>A PCP client refreshes a mapping by sending a new PCP  
request
            containing information from the earlier PCP response. The  
PCP server
            will respond indicating the new lifetime. It is possible,  
due to
            reconfiguration or failure of the PCP server, that the  
public IP
            address and/or public port, or the PCP server itself, has  
changed
-          (due to a new route to a different PCP server). To detect  
such
-          events more quickly, the PCP client may find it beneficial  
to use
-          shorter lifetimes (so that it communicates with the PCP  
server more
-          often). If the PCP client has several mappings, the Epoch
+          (due to a new route to a different PCP server). Such  
events are
+          not an error. The PCP server will simply return a new  
External
+          Address and/or External Port to the client, and the client  
should
+          record this new External Address and Port with its  
rendezvous service.
+          To detect such events more quickly, the PCP client may  
find it
+          beneficial to use shorter lifetimes (so that it communicates
+          with the PCP server more often).</t>
+
+          <t>If the PCP client has several mappings, the Epoch
            value only needs to be retrieved for one of them to  
determine
            whether or not it appears the PCP server may have suffered a
-          catastrophic loss of state.</t>
-
-          <t>If the client wishes to check the PCP server's Epoch,  
it sends a
+          catastrophic loss of state.
+          If the client wishes to check the PCP server's Epoch, it  
sends a
            PCP request for any one of the client's mappings. This  
will return
            the current Epoch value. In that request the PCP client  
could extend
            the mapping lifetime (by asking for more time) or  
maintain the
@@ -3119,15 +3133,15 @@

  <t>Because an SCTP-aware NAT does not rewrite SCTP port numbers (and
  firewalls never do), a PCP MAP or PEER request for an SCTP mapping
-SHOULD provide the same Internal Port and Requested External Port.  If
-the PCP server supports SCTP, and the requested external port cannot
+SHOULD provide the same Internal Port and Suggested External Port.  If
+the PCP server supports SCTP, and the suggested external port cannot
  be provided in an explicit dynamic SCTP mapping, then the error
  CANNOT_PROVIDE_EXTERNAL is returned.</t>
  </section>
        </section>

-<section title="Source Address in PCP Header"  
anchor="implement_source_address">
-<t>All PCP requests include the PCP client's IP address
+<section title="Source Address Replicated in PCP Header"  
anchor="implement_source_address">
+<t>All PCP requests include the PCP client's IP address replicated
  in the PCP header.  This is used to detect address rewriting (NAT)
  between the PCP client and its PCP server.  On operating systems that
  support the sockets API, the following steps are RECOMMENDED for a PCP
@@ -3139,7 +3153,7 @@
              <t>Create a UDP socket.</t>
              <t>Bind the UDP socket.</t>
              <t>Call the getsockname() function to retrieve a sockaddr
-            containing the source address and port the kernel will use
+            containing the source address the kernel will use
              for UDP packets sent through this socket.</t>
              <t>If the IP address is an IPv4 address, encode the
              address into an IPv4-mapped IPv6 address.  Place the IPv6
@@ -3286,10 +3300,10 @@
          or requesting a random port. These UPnP IGD requests are  
translated to
          PCP requests and sent to the PCP server. The requests  
include the
          PREFER_FAILURE Option, which causes the PCP server to  
return an error
-        if it cannot allocate the requested port. The interworking  
function
+        if it cannot allocate the suggested port. The interworking  
function
          translates the PCP error response to a UPnP IGD error  
response. This
          repeats until the UPnP IGD client gives up or until the PCP  
server is
-        able to return the requested port.</t>
+        able to return the suggested port.</t>

          <figure align="left" anchor="message-flow-upnp-1"
                  title="Message Flow: Interworking from UPnP IGD 1.0  
AddPortMapping action to PCP">
@@ -3344,6 +3358,7 @@

  -->

+    <?rfc needLines="6" ?>
      <section title="Deployment Considerations">
        <section title="Ingress Filtering">
          <t>As with implicit dynamic mappings created by outgoing  
TCP packets,
@@ -3554,7 +3569,7 @@
            <t>An attacker, on the path between the PCP client and PCP
            server, can drop PCP requests, drop PCP responses, or  
spoof a
            PCP error, all of which will effective deny service.   
Through
-          such actions, the PCP client would not be aware the PCP  
server
+          such actions, the PCP client might not be aware the PCP  
server
            might have actually processed the PCP request.</t>
          </section>

@@ -3904,7 +3919,7 @@
  is undefined.</t>
  <t>combined SERVER_OVERLOADED and NO_RESOURCES into one error code,
  NO_RESOURCES.</t>
-<t>SCTP mappings have to use same internal and requested
+<t>SCTP mappings have to use same internal and suggested
  external ports, and have implied PREFER_FAILURE semantics.</t>
  <t>Re-instated ADDRESS_MISMATCH error, which only checks the
  client address (not its port).</t>
@@ -4012,7 +4027,7 @@
              mapping state. Moved it to a new section, as well (it  
is now
              <xref target="restoring"></xref>).</t>

-            <t>MAP errors now copy the Requested IP Address (and  
port) fields
+            <t>MAP errors now copy the Suggested IP Address (and  
port) fields
              to Assigned IP Address (and port), to allow PCP client to
              distinguish among many outstanding requests when using
              PREFER_FAILURE.</t>
@@ -4026,7 +4041,7 @@

              <t>created new Implementation Considerations section  
(<xref
              target="implementation_considerations"></xref>) which  
discusses
-            non-normative things that might be useful to  
implementors. Some
+            non-normative things that might be useful to  
implementers. Some
              new text is in here, and the Failure Scenarios text (<xref
              target="failure"></xref>) has been moved to here.</t>



From rja.lists@gmail.com  Fri Oct 28 02:08:05 2011
Return-Path: <rja.lists@gmail.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 E3E5221F8ADE for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 02:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.549
X-Spam-Level: 
X-Spam-Status: No, score=-3.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6hJbyYvVnIGI for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 02:08:05 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2E9F321F8AC3 for <pcp@ietf.org>; Fri, 28 Oct 2011 02:08:05 -0700 (PDT)
Received: by wyh22 with SMTP id 22so4344513wyh.31 for <pcp@ietf.org>; Fri, 28 Oct 2011 02:08:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=7leWS4l25dlk5iVPte4lEu5kw/qDuT21NAcLAFNFdz0=; b=W9nMDRT+upzFbS/vOnClDVQNJQm0lAI3M+crpMago9AnkjW348sMjDIct+WcxdggQQ ij54MbfDIN6fGG2V7PCZeTz++qwKbHu+r6n/z3LDC4ikQCzdMTO9+9fBX83fPDNwR4nb 5xSsQcNQY6WeMnHr+U8umTbz+yU1WEYkW4oLA=
Received: by 10.216.166.15 with SMTP id f15mr610489wel.112.1319792884367; Fri, 28 Oct 2011 02:08:04 -0700 (PDT)
Received: from dragonfly.cs.ucl.ac.uk (dragonfly.cs.ucl.ac.uk. [128.16.64.246]) by mx.google.com with ESMTPS id l20sm14295679wbo.6.2011.10.28.02.08.03 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 28 Oct 2011 02:08:03 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <s1v62j9vqcr.fsf@bikeshed.isc.org>
Date: Fri, 28 Oct 2011 05:08:02 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <3ACAD798-0285-43E7-B680-A13C04598943@gmail.com>
References: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com> <0CDBCDE2-21CA-4287-A893-97D67BD1318B@apple.com> <s1v62j9vqcr.fsf@bikeshed.isc.org>
To: pcp@ietf.org
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 09:08:06 -0000

On 27  Oct 2011, at 21:48 , Paul Selkirk wrote:
> "Restored" only applies if this is viewed as NAT-PMP-bis,
> because it was never in a draft-ietf-pcp-base specification.

If one looks at the draft-ietf-pcp-base (e.g. IANA Considerations, 
transport-layer port number text) in the PCP base specification, 
it is hard to avoid concluding that PCP is a combination of
uPnP and NAT-PMP, and therefore that PCP really is NAT-PMP-bis.  

> Quoth Ran Atkinson:
>> The charter is NOT limited to CGN cases, but instead is very broadly
>> written to include ALL use cases involving either NAT, Firewall, or both.
> 
> And yet, I can report that all the energy in the WG has been devoted to
> the CGN scenarios (NAT444, DS-Lite, and NAT64, in approximate order of
> how much attention they've gotten in the last year). That's probably a
> failure to attract the attention of the firewall and CPE folks.

That sounds like an admission of process failure on the part of the WG.
It certainly does NOT change the actual WG charter text, which remains
normative on this WG.

> I could turn this around, and say that the time to insist on inclusion
> of this feature was last April.

Au Contraire.  

After watching the April PCP list discussion, a reasonable person
would conclude that Rapid Recovery feature EITHER would be included 
in the draft-ietf-pcp-base specification OR that the separate 
Rapid Recovery I-D would go into WG Last Call at the same time 
as the draft-ietf-pcp-base document.  IETF WG list discussions
are binding, unlike in-person meetings, and the list discussion
certainly ended with the impression that there were no unresolved
issues with the Rapid Recovery feature.

Yours,

Ran


From rja.lists@gmail.com  Fri Oct 28 03:00:55 2011
Return-Path: <rja.lists@gmail.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 C85F821F8ABE for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 03:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.556
X-Spam-Level: 
X-Spam-Status: No, score=-3.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e4hTx-5pMzaW for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 03:00:55 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2069D21F8A57 for <pcp@ietf.org>; Fri, 28 Oct 2011 03:00:54 -0700 (PDT)
Received: by wyh22 with SMTP id 22so4399735wyh.31 for <pcp@ietf.org>; Fri, 28 Oct 2011 03:00:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=OdhfMWOPdhCQ/dcWOV0UdwhD2m39iiUVo96b3M3ooao=; b=Lt9JFEYH//m1F4Zjy8zqJpwF2RwA11vgbXhWuJ2mTSgWfRRytljfka71+UHPHmhk7Z iE03s5r2BNjTGoYjsGrREuORESe+oVNJQ5gV5wf/ddtp10qFdiqFQuTX7NjlzVaz/Nmu 6D+QMKXQXI5jK40VfWhsDYUFZ4C4bbfZok2YI=
Received: by 10.216.24.13 with SMTP id w13mr616478wew.84.1319796054307; Fri, 28 Oct 2011 03:00:54 -0700 (PDT)
Received: from dragonfly.cs.ucl.ac.uk (dragonfly.cs.ucl.ac.uk. [128.16.64.246]) by mx.google.com with ESMTPS id gg13sm14553804wbb.8.2011.10.28.03.00.51 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 28 Oct 2011 03:00:53 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <s1v4nywwee1.fsf@bikeshed.isc.org>
Date: Fri, 28 Oct 2011 06:00:50 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <1393431B-D7C0-469C-B95B-54ADE29FE630@gmail.com>
References: <7F482FB4-237B-4379-B5C1-C74E70DFC7BC@gmail.com> <s1v4nywwee1.fsf@bikeshed.isc.org>
To: pcp@ietf.org
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 10:00:55 -0000

On 26  Oct 2011, at 00:44 , Paul Selkirk wrote:
> OTOH, a) if we define it for IPv4 multicast, someone
> will surely and immediately request it for IPv6 multicast;

As you predicted, in this morning's email, 
Keith Moore expressed interest in IPv6.

However, Stuart released draft-cheshire-pcp-recovery-02 overnight.
The revised I-D text is IP version agnostic, including language 
about link-local all-nodes multicast for both IPv4 and IPv6.

So the concern quoted at top is resolved at this point.

If other specific issues/concerns exist with draft-cheshire-pcp-recovery,
please make those issues/concerns known to the whole PCP WG list,
ideally with some concrete suggestions on how to resolve any
issues/concerns.

Yours,

Ran


From Francis.Dupont@fdupont.fr  Fri Oct 28 06:45:44 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 09CC221F8B58 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 06:45:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eOE5OTNmOCMr for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 06:45:43 -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 4325D21F8B1C for <pcp@ietf.org>; Fri, 28 Oct 2011 06:45:43 -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 p9SDjbp5077073; Fri, 28 Oct 2011 15:45:38 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281345.p9SDjbp5077073@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Thu, 27 Oct 2011 14:36:19 PDT. <36E0DF10-3EBF-4501-8484-AD43D96B8691@apple.com> 
Date: Fri, 28 Oct 2011 15:45:37 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "pcp@ietf.org" <pcp@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 13:45:44 -0000

 In your previous mail you wrote:

   What the Rapid Recovery text says is that multicast *is* practical in  
   home networks, such as networks where DHCP is used (since a DHCP  
   broadcast should generally reach the same set of hosts as an all- 
   hosts multicast).

=> I believe you mean DHCPv4.

   You may not yourself work on low-cost home gateways, but both Apple  
   and Linksys do make home gateways for this market, and I would like  
   those home gateways to continue to be at least as good as our  
   existing NAT-PMP home gateways.
   
=> BTW modern UPnP has the same feature too.

Note I have no concern to push the rapid recovery with the DHCP for
PCP server discovery I-D in the "to publish just after" list.

Regards

Francis.Dupont@fdupont.fr

PS: by modern I mean in the package where is IGD v2, and if I remember
well at least recommended to be used with IGD v2.
PPS: if the rapid recovery is something nice to have for a CPE in the
case of a CGN I prefer to get the explicit dynamic (and static of
course) mappings saved in a stable storage so there is nothing to
recovery. As in (too) many countries ISPs must log all the mappings by
law, IMHO it is not an issue to provide this. Now you can answer ISPs
could use a stateless solution...

From Francis.Dupont@fdupont.fr  Fri Oct 28 07:08:10 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 5EDEA21F8AD9 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 07:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l90HUiRFwuuk for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 07:08:09 -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 02A9021F86A5 for <pcp@ietf.org>; Fri, 28 Oct 2011 07:08:08 -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 p9SE85qr078586; Fri, 28 Oct 2011 16:08:05 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281408.p9SE85qr078586@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 27 Oct 2011 16:23:31 PDT. <0ffc01cc94ff$70f69000$52e3b000$@com> 
Date: Fri, 28 Oct 2011 16:08:05 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (1)
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, 28 Oct 2011 14:08:10 -0000

 In your previous mail you wrote:

   >  - 6.4 page 18 (NO_RESOURCES): I have a concern with:
   >       ... This can be used as a catch-all
   >       error, should no other error message be suitable.
   > 
   >    by itself it is not a bad idea to provide a catch-all but
   >    NO_RESOURCES has a special processing, cf. 7.3 page 19:
   > 
   >    If the result code is NO_RESOURCES, PCP client SHOULD NOT send *any*
   >    further requests to that PCP server for the indicated error
   > lifetime.
   > 
   >    So we really need the PROCESSING_ERROR...
   
   Let's talk about PROCESSING_ERROR in a separate thread.  As you stated,
   the difficulty is writing text to distinguish between a catch-all
   PROCESSING_ERROR error and other errors.
   
=> I limit this message to this item: PROCESSING_ERROR is for
problems *after parsing* (so the syntax is good, the request is valid
but for some reasons failed to be correctly processed) and not
bound to a lack of resources, including quotas, i.e., not
NO_RESOURCES or USER_EX_QUOTA. IMHO it is better than other result
code for not syntax errors as it doesn't carry another background,
for instance it is better than NOT_AUTHORIZED.

And as I explained the real choice is between a standardized name
and value, or to use 192 & co privately and everywhere.
   
Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 28 07:15:39 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 6BE9821F8AD3 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 07:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvyUPIfoQbcm for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 07:15:39 -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 93DA821F8AC3 for <pcp@ietf.org>; Fri, 28 Oct 2011 07:15:38 -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 p9SEFZdU079014; Fri, 28 Oct 2011 16:15:35 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281415.p9SEFZdU079014@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 27 Oct 2011 16:23:31 PDT. <0ffc01cc94ff$70f69000$52e3b000$@com> 
Date: Fri, 28 Oct 2011 16:15:35 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (1)
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, 28 Oct 2011 14:15:39 -0000

 In your previous mail you wrote:

   >  - 6.4 page 18 (CANNOT_PROVIDE_EXTERNAL_PORT): please remember we
   >   still have an open issue about this
   
   Renamed to CANNOT_PROVIDE_EXTERNAL, and now says:
   
     the requested
     external port and/or external address cannot be provided.
   
   Suitable?
   
=> perfect, I'll update my code (wireshark, tcpdump, client, server,
test suite, etc) as soon as I finish these messages.

   >  - 7.1 page 19: it is not a concern for me but BTW there is nothing
   >   about other (i.e., not first) members of the list of PCP Server(s)...
   
   On purpose; that may be something another document discusses.
   
=> I don't care but you could get the same question during the IETF LC

   Now says:
   
           <t>If the length of the message exceeds 1024 octets, is not a
           multiple of 4 octets, or its header is too short, it is
           invalid.
   
=> note I rewrote the whole list of checks to do at the beginning
of the request processing according to the code I ported to base 16+,
so there is another message more accurate and surely more useful
for you.
   
Thanks

Francis.Dupont@fdupont.fr

PS: I expect to not find new problems as I nearly finished to update
the corresponding code (i.e., I read and implemented base 16+).

From Francis.Dupont@fdupont.fr  Fri Oct 28 07:20:37 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 C332E21F85F7; Fri, 28 Oct 2011 07:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.236
X-Spam-Level: 
X-Spam-Status: No, score=-2.236 tagged_above=-999 required=5 tests=[AWL=-0.237, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oZYICwgkax+e; Fri, 28 Oct 2011 07:20:37 -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 1C58D21F84C1; Fri, 28 Oct 2011 07:20:36 -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 p9SEKXsx079332; Fri, 28 Oct 2011 16:20:33 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281420.p9SEKXsx079332@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: james woodyatt <jhw@apple.com>
In-reply-to: Your message of Thu, 27 Oct 2011 16:32:15 PDT. <7E14C89F-7497-443A-B812-8602733FB0D0@apple.com> 
Date: Fri, 28 Oct 2011 16:20:33 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: IPv6 Operations <v6ops@ietf.org>, PCP <pcp@ietf.org>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 14:20:37 -0000

 In your previous mail you wrote:

   On the other hand, another option is for PCP to be withdrawn as a
   candidate for meeting REC-48 of RFC 6092, which would free V6OPS to
   consider another protocol for that purpose in RFC 6204bis instead.
   
-> do you mean UPnP-gw-WANIPv6FirewallControl-v1-Service-20101210.pdf?
(part of UPnP IGD v2)

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 28 07:23:51 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 51C3721F8B00; Fri, 28 Oct 2011 07:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5HIZvxb6SJw; Fri, 28 Oct 2011 07:23:51 -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 6248C21F8ABD; Fri, 28 Oct 2011 07:23:50 -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 p9SENkB7079541; Fri, 28 Oct 2011 16:23:47 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281423.p9SENkB7079541@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Keith Moore <moore@network-heretics.com>
In-reply-to: Your message of Thu, 27 Oct 2011 20:02:18 EDT. <247469E7-EF59-4919-AA60-C17BDDE3145C@network-heretics.com> 
Date: Fri, 28 Oct 2011 16:23:46 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: IPv6 Operations <v6ops@ietf.org>, PCP <pcp@ietf.org>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 14:23:51 -0000

 In your previous mail you wrote:

   But IMO the emphasis in PCP on accommodating LSNs is misplaced.

=> there is a simple reason for this: the CPE control is
more than dominated in the current world by UPnP IGD...

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 28 07:36:04 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 9D70321F8ABD for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 07:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wkY33X-0Zogy for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 07:36:04 -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 D678621F8A96 for <pcp@ietf.org>; Fri, 28 Oct 2011 07:36:03 -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 p9SEa0CM080314; Fri, 28 Oct 2011 16:36:00 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281436.p9SEa0CM080314@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 27 Oct 2011 17:03:16 PDT. <103001cc9504$fe6b3b70$fb41b250$@com> 
Date: Fri, 28 Oct 2011 16:36:00 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 28 Oct 2011 14:36:04 -0000

 In your previous mail you wrote:

   >  - 7.5 page 23: I liked the one hour max drift rule, using the
   >   same style it gives an additional member of the if 'or':
   >   or 3600 < abs(server_delta - client_delta)
   
   I don't understand.
   
=> I'd like to translate this taken from base 15:

   ... or is more than 3660 seconds
   (one hour) above or below the expected Epoch value, the PCP client
   concludes that the PCP server lost state.

fixed and translated to base 16 terms it means the difference
between the two delta's must be less than 3600 seconds / one hour
or the epoch is invalid.
BTW if you don't want the abs() from the math library it can be
written with unsigned delta as:

   or client_delta+3600 < server_delta
   or server_delta+3600 < client_delta

so the last item (*) of the list gives for invalid epoch:

         +  If client_delta+2 < server_delta - server_delta/8
            or server_delta+2 < client_delta - client_delta/8
            then the client treats the Epoch time value as invalid,
            else the client treats the Epoch time value as valid

  ->

         +  If client_delta+2 < server_delta - server_delta/8
            or server_delta+2 < client_delta - client_delta/8
            or client_delta+3600 < server_delta
            or server_delta+3600 < client_delta
            then the client treats the Epoch time value as invalid,
            else the client treats the Epoch time value as valid

(*) there are in fact two other cases written in text:
server_delta must be positive and client_delta is positive by
construction, but I agree to keep them in text as it makes
the pseudo code still valid with unsigned delta's.
To summary I propose (only) this change.
   
Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 28 07:38:57 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 27A3721F8AE1 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 07:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iWgKlxEGdzNw for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 07:38:56 -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 6AB5521F8A6C for <pcp@ietf.org>; Fri, 28 Oct 2011 07:38:56 -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 p9SEcpj0080443; Fri, 28 Oct 2011 16:38:51 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281438.p9SEcpj0080443@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 27 Oct 2011 17:03:16 PDT. <103001cc9504$fe6b3b70$fb41b250$@com> 
Date: Fri, 28 Oct 2011 16:38:51 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 28 Oct 2011 14:38:57 -0000

 In your previous mail you wrote:

   >  - 8 page 27: the paragraph:
   > 
   >    Note that PCP requests containing the MAP or PEER Opcodes cannot
   >    delete or shorten the lifetime of an existing implicit mapping for
   >    the indicated internal address and port.  Conceptually implicit and
   >    explicit mappings are different "layers" in the NAT forwarding state
   >    database.
   > 
   >   is in contradiction with the implementation-dependent text in
   >   the PEER opcode description. Note IMHO that text is wrong so I cite
   >   this paragraph only for the case the WG decision will be reversed.
   
   Let's bring this up in a separate thread, solely about this issue.
   
=> agreed: we have an issue about PEER semantics we should discuss
by itself (and it is one of the two items I am discussing internally
as I explained in the 3rd part of my review).
   
Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 28 07:59:50 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 6CB7B21F8515 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 07:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fE+quISdX+7j for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 07:59:49 -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 82CA321F8509 for <pcp@ietf.org>; Fri, 28 Oct 2011 07:59:49 -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 p9SExkMM081670; Fri, 28 Oct 2011 16:59:46 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281459.p9SExkMM081670@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 27 Oct 2011 17:03:16 PDT. <103001cc9504$fe6b3b70$fb41b250$@com> 
Date: Fri, 28 Oct 2011 16:59:46 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 28 Oct 2011 14:59:50 -0000

 In your previous mail you wrote:

   >  - 9.5 page 42: the all subscriber mapping delete is not in the list
   >   (but is in 11.1 page 51 about THIRD_PARTY). IMHO we should add
   >   a reference to it at the end of:
   > 
   >    o  If both the internal port and protocol are zero, it indicates a
   >       request to delete all mappings for this Internal Address for all
   >       transport protocols.  This is useful when a host reboots or joins
   >       a new network, to clear out prior stale state from the NAT
   > gateway
   >       before beginning to install new mappings.
   > 
   >   BTW this could fix the missing fact the all subscriber mapping
   >   requires zero internal port and protocol.
   
   But we don't want a host to remove mappings for another host, unless
   THIRD_PARTY is used.  Maybe I don't understand what you're proposing.
   Please bring this up in its own thread.
   
=> it is misunderstandarding: my comment is the all subscriber mapping
delete (named all client mapping delete) should be referenced here,
and of course it requires a specific (i.e., "empty") THIRD_PARTY option.
   
   >  - 9.7 page 44: I have still a concern about:
   > 
   >    Address for cosmetic purposes can achieve that by requesting a
   > short-
   >    lived mapping and then displaying the resulting External IP Address.
   >    However, once that mapping expires a subsequent implicit or explicit
   >    dynamic mapping might be mapped to a different external IP address.
   > 
   >   as it is both pejorative and useless. I strongly suggest to remove it
   >   (and to keep the rest of 9.7).
   
   Noted.  But this question comes up often,

=> it comes often for *not cosmetic* purposes!

   and it seems useful and necessary to have in the document.  Will
   keep it as-is.
   
=> we have 3 choices:
 -1- think that the text in 9.7 up to but not including the "cosmetic" stuff
  is enough to implement the function (get external address) for not
  cosmetic purpose
 -2- the current text
 -3- standardize a way to provide the function for not cosmetic purpose
IMHO -1- or -3- are fine, -1- is easier as it supposes it will be done
in the documents requiring a not cosmetic purpose, this is why I support -1-.
-2- is bad because it implicitly assumes all purposes are cosmetic,
so it doesn't solve any real problems, it just makes people unhappy.
   
   >  - 10.1 page 45 (Requested Lifetime): I note this as I have a concern
   >   I am discussing.
   > 
   >  - 10.1 page 46 (twice): the word 'preference' in the two Suggested
   >   and even the word 'Suggested' itself don't match the implicit
   >   PREFER_FAILURE semantic.
   
   I don't understand what change you're wanting to the document.
   
=> the PEER Suggested external address and Suggested external port
are in fact Requested external address and Requested external port
as the PEER request will fail if they can't be fulfilled.
And they are requested values, not preferences: the text was copied
from MAP but IMHO the wording is no longer appropriate.
(now it is only a wording problem).

   >  - 11.3 page 55: this text could be improved to take into account
   >   a possible error response with an UNPROCESSED added option:
   > 
   >       Maximum occurrences: as many as fit within maximum PCP message
   >       size
   
   There is already sufficient admonishment in the general PCP 
   section about message length.
   
=> I note to add this case in my test suite (MAP request with FILTER
options, including a bad one, and an padding option up to 1020 octets).
As I am looking for interesting cases to add (:-)...

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 28 08:09:42 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 3732921F848F for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 08:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8IpUDsQg1hNt for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 08:09:41 -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 56D1621F848B for <pcp@ietf.org>; Fri, 28 Oct 2011 08:09:41 -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 p9SF9c4O082425; Fri, 28 Oct 2011 17:09:38 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281509.p9SF9c4O082425@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 27 Oct 2011 17:08:25 PDT. <103401cc9505$b66b1d30$23415790$@com> 
Date: Fri, 28 Oct 2011 17:09:38 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] UNPROCESSED with SUCCESS
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, 28 Oct 2011 15:09:42 -0000

 In your previous mail you wrote:

   > In base 16 7.7.1 page 26, UNPROCESSED is defined with:
   > 
   >       May appear in: responses, and only if the result code is non-
   > zero.
   > 
   > I'd like to relax this to handle a corner case: a MAP request with at
   > least
   > a FILTER option which matches a static mapping. The meaning is the
   > FILTERs
   > don't make sense (in particular the MAP request doesn't change them) so
   > they are unprocessed, but the request still returns a SUCCESS.
   > 
   > BTW there are other solutions but worse, for instance an UNSUPP_OPTION
   > which suggests the PCP server doesn't support FILTER, and is not a
   > SUCCESS.
   
   Let's back away from the protocol a little bit, and think about what problem
   we're trying to solve.
   
=> as I explained it is a corner case...

   If the PCP client sends a MAP request with a FILTER option, the PCP client
   either:
   
     * thinks there is an existing mapping, and is trying to adjust its
       filtering
     * wants to create a new mapping with specific filtering
   
=> in this case it should be the second because if the existence
of the static mapping is known the fact Web & co interface must
be used and not PCP is known too.

   It seems that the desired behavior of the protocol depends on what
   we assume the PCP client is most likely to do -- no?
   
=> perhaps we should look at what the caller of the PCP client
is most likely to do next. We can say:
 - the existence of a matching static mapping is an error but
  we have no clear ways to encode this by an error response,
  so we fall in one of the other cases

 - the FILTER options are obviously not processed so could
  be marked as them in a success response

 - the static mapping response implies the FILTER options
  are not relevant, so just ignore them and returns the
  INT32_MAX success response
   
To implement the second we need to relax the UNPROCESSED spec,
to implement the last one we just need to agree it is the
best acceptable thing.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 28 08:20:37 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 B3FD521F8726 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 08:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XRgbJodWZCAE for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 08:20:37 -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 9F5A821F86EE for <pcp@ietf.org>; Fri, 28 Oct 2011 08:20:36 -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 p9SFKXI1083088; Fri, 28 Oct 2011 17:20:33 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281520.p9SFKXI1083088@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Dan Wing" <dwing@cisco.com>
In-reply-to: Your message of Thu, 27 Oct 2011 17:20:35 PDT. <103501cc9507$69a9ff00$3cfdfd00$@com> 
Date: Fri, 28 Oct 2011 17:20:33 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] inconsistent options in responses
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, 28 Oct 2011 15:20:37 -0000

 In your previous mail you wrote:

   The MUST is too severe, because if an option is unprocessed, the
   option shouldn't be in the response.  I think this is sufficient
   for THIRD_PARTY, PREFER_FAILURE, and FILTER, and I changed 
   them accordingly:
   
               <t>May appear in: requests, and MUST appear in
               successfully-processed responses</t>
   
=> I disagree because when the word "omit" was removed in a
previous base document version I asked for a clarification
whether it was what we wanted.
I interpret the current specification as the options in the
request are unconditionally copied to the response (in fact
the whole message is copied as it). This is why we got the
maximum length issue.
So please consider to use my proposed text:
   
   >       May appear in: request.  MUST appear in response if it
   >       appeared in the associated request.
   
Regards

Francis.Dupont@fdupont.fr

PS: I am in favor of the new rule (unconditionally copy)
because it is very simple (i.e., can you find something
simpler :-).
Perhaps it should be made more explicit?

From Francis.Dupont@fdupont.fr  Fri Oct 28 08:27:31 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 979FF21F863E for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 08:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ycdkgaw8dQB8 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 08:27:31 -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 D31A121F85B9 for <pcp@ietf.org>; Fri, 28 Oct 2011 08:27:30 -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 p9SFRQd9083528; Fri, 28 Oct 2011 17:27:26 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281527.p9SFRQd9083528@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Thu, 27 Oct 2011 22:38:17 PDT. <122405C3-6FFD-4538-9EB0-6493712B35FE@apple.com> 
Date: Fri, 28 Oct 2011 17:27:26 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (1)
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, 28 Oct 2011 15:27:31 -0000

 In your previous mail you wrote:

   On 24 Oct 2011, at 8:22 AM, Francis Dupont wrote:
   
   >  - 3 page 8 (Mapping Types): web page -> web portal
   >   (just a suggestion, the term "web page" is very poor IMHO)
   
   Why "portal"?
   
=> just because I'd like to get something else than page,
but if you have a better idea you are very wellcome!
(being more serious some ISPs named this a portal which
makes sense for an ISP in its pure ISP job)

Thanks

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 28 08:31:10 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 B202521F8770 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 08:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level: 
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[AWL=0.061,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MjwN0SC83dt3 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 08:31:10 -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 05CBE21F86EC for <pcp@ietf.org>; Fri, 28 Oct 2011 08:31:09 -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 p9SFV6IX083771; Fri, 28 Oct 2011 17:31:06 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110281531.p9SFV6IX083771@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Thu, 27 Oct 2011 23:29:52 PDT. <B2A742C5-4490-4BE4-BC2D-94DB402B600A@apple.com> 
Date: Fri, 28 Oct 2011 17:31:06 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (1)
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, 28 Oct 2011 15:31:10 -0000

 In your previous mail you wrote:

   On 24 Oct 2011, at 8:22 AM, Francis Dupont wrote:
   
   >  - 6.3 page 15: 1024-4*number_of_options -> 1020-4*number_of_options
   >   (i.e., please add the UNPROCESSED option header too)
   
   Where does this number come from? Why "4*number_of_options"?
   
=> you can get one octet (filled with the option code) per option
in the request, you have 4 octets for the UNPROCESSED option header,
so it gives 1024 - 4 - number_of_options and I agree the
correct number is "1020 - number_of_options".

Thanks

Francis.Dupont@fdupont.fr

From jhw@apple.com  Fri Oct 28 09:50:08 2011
Return-Path: <jhw@apple.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 0634521F8AAA; Fri, 28 Oct 2011 09:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.56
X-Spam-Level: 
X-Spam-Status: No, score=-106.56 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QAU9G8AnLeC0; Fri, 28 Oct 2011 09:50:07 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 950A021F861E; Fri, 28 Oct 2011 09:50:07 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_kw2qp/mPcF7591q9Lzk55A)"
Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LTS0010MC21UR21@mail-out.apple.com>; Fri, 28 Oct 2011 09:49:59 -0700 (PDT)
X-AuditID: 11807136-b7c19ae0000072b0-e2-4eaadd3765cd
Received: from ba0301a-dhcp89.apple.com (ba0301a-dhcp89.apple.com [17.193.14.217]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay15.apple.com (Apple SCV relay) with SMTP id 92.B8.29360.73DDAAE4; Fri, 28 Oct 2011 09:49:59 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
Date: Fri, 28 Oct 2011 09:49:59 -0700
In-reply-to: <201110281420.p9SEKXsx079332@givry.fdupont.fr>
To: PCP <pcp@ietf.org>, IPv6 Operations <v6ops@ietf.org>
References: <201110281420.p9SEKXsx079332@givry.fdupont.fr>
Message-id: <72FB00E8-E198-419C-83A3-BB348ED9708E@apple.com>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOLMWRmVeSWpSXmKPExsUieJDvpq753VV+Bsv36FhMPvab1eL0sb3M DkweS5b8ZApgjOKySUnNySxLLdK3S+DK2HVsBmPBR7mKxYtvMDYw7pTuYuTgkBAwkXg2Gcjk BDLFJC7cW88GYgsJrGCSOHBbB8RmE1CR+Hb5LhOIzStgLLHm1jsWEJtZIEFi9plfbCBjhAVs JZ7MMAIJswioSuz98YcVxOYUsJY4+m8hWKuIgJXErV/LocZbSXQ/e8oGMdJGomnmbjaIE+Ql Wr7eYZvAyDsLybZZSLZB2NoSyxa+Zp4FtJlZQEdi8kJGVGEI++P5I0wLGNlWMQoWpeYkVhqa 6iUWFOSk6iXn525iBAVfQ6HZDsYdf+UOMQpwMCrx8HK2r/QTYk0sK67MPcQowcGsJML7vmWV nxBvSmJlVWpRfnxRaU5q8SFGaQ4WJXHey9eBUgLpiSWp2ampBalFMFkmDk6pBsYqtg7HvM0x mU5cG2ZOc0s+pP6l3W6GVUX8tZZF92JEhF/m8ySuao47ebvdd8PfutWM0aa3b9+/LlCtHaqR eGX1yd+XwpJF/HJE1q3k+Xj1atm0lwf3b9i70D9ZPfDIV4XaeC7znXNvmz1g/WzRLxQY6bvl ecP+CO+UJiXl36sjzrblFj5oE1NiKc5INNRiLipOBAD/JjtzOgIAAA==
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 16:50:08 -0000

--Boundary_(ID_kw2qp/mPcF7591q9Lzk55A)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

On Oct 28, 2011, at 7:20 AM, Francis Dupont wrote:
> 
> do you mean UPnP-gw-WANIPv6FirewallControl-v1-Service-20101210.pdf?
> (part of UPnP IGD v2)

RFC 6092 includes a list of marginally viable alternatives, including but not limited to UPnP IGD, which were current at the time of its publication.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




--Boundary_(ID_kw2qp/mPcF7591q9Lzk55A)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Oct 28, 2011, at 7:20 AM, Francis Dupont =
wrote:</div><blockquote type=3D"cite"><br =
class=3D"Apple-interchange-newline"></blockquote><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">do you mean =
UPnP-gw-WANIPv6FirewallControl-v1-Service-20101210.pdf?<br>(part of UPnP =
IGD v2)</span></blockquote></div><br><div>RFC 6092 includes a list of =
marginally viable alternatives, including but not limited to UPnP IGD, =
which&nbsp;were current at the time of its publication.</div><div><br =
class=3D"webkit-block-placeholder"></div><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Gill Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
12px; "><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><br =
class=3D"Apple-interchange-newline">--</span></span></div><div =
style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">james woodyatt &lt;<a =
href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&gt;</span></span></span></=
div><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">member of technical staff, core os =
networking</span></span></span></div><br =
class=3D"Apple-interchange-newline" style=3D"font-size: 11px; =
font-family: Geneva; "></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Boundary_(ID_kw2qp/mPcF7591q9Lzk55A)--

From cheshire@apple.com  Fri Oct 28 11:37:44 2011
Return-Path: <cheshire@apple.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 5AF9311E8095 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 11:37:44 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xYIgZDF6sZXq for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 11:37:43 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id A727111E8093 for <pcp@ietf.org>; Fri, 28 Oct 2011 11:37:43 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LTS007ZFH2UY490@mail-out.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 11:37:43 -0700 (PDT)
X-AuditID: 11807134-b7cc1ae0000078f0-94-4eaaf674b3df
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay14.apple.com (Apple SCV relay) with SMTP id 55.62.30960.476FAAE4; Fri, 28 Oct 2011 11:37:42 -0700 (PDT)
Received: from [10.0.1.201] ([173.164.252.149]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LTS00AEUH2RXW50@koseret.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 11:37:39 -0700 (PDT)
In-reply-to: <CACF57C3.5690F%rpenno@juniper.net>
References: <CACF57C3.5690F%rpenno@juniper.net>
Message-id: <FD2BEDDB-E7AB-45C1-A4B4-BE34673B59F1@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Fri, 28 Oct 2011 11:38:41 -0700
To: Reinaldo Penno <rpenno@juniper.net>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrELMWRmVeSWpSXmKPExsUiON1OXbfs2yo/gxt7LSwmH/vN6sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujD3zdjMWnOGsmPtlB0sD4xX2LkZODgkBE4kXT7ezQthiEhfu rWfrYuTiEBLoZJJ4c3k/I0iCV0BQ4sfkeyxdjBwczALyEgfPy4KEmQVcJLZOaGGHqO9nkphx p5MJpIZTwECi9bs7iCkkoC9xeI4DxBQbiReztjDBtHY+2At2ApuAlsSLz1fYQMqFBWwlnsww AgmzCKhK/Dt1B6xEREBd4kfvI2aIK+UkDp9+xTiBUWAWkttmIdw2C8ltCxiZVzEKFqXmJFYa muglFhTkpOol5+duYgSFXEOhyQ7Ggz/5DzEKcDAq8fA6PlnlJ8SaWFZcmXuIUYKDWUmE98Vj oBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXHeS9eBUgLpiSWp2ampBalFMFkmDk6pBsZc7dzX+pMC H52d84rH/s3DTduYV3226RHvmuV+4NZiUws1noD+c8ErLX++VTFfnSh07PXi0g15v5fNOtBV Gnxpst631m1/7J1YCxmMZur80LpoFD2P+7XYe78LD2LcMyxLlb6n/NDbe/xT8p9ryyoqSpjF J62WTX8xzyoq3stn4aZvMZobZNcpsRRnJBpqMRcVJwIAZgdBfjUCAAA=
Cc: "pcp@ietf.org" <pcp@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 18:37:44 -0000

On 10/27/11 2:36 PM, "Stuart Cheshire" <cheshire@apple.com> wrote:

> What the Rapid Recovery text says is that multicast *is* practical in
> home networks, such as networks where DHCP is used (since a DHCP
> broadcast should generally reach the same set of hosts as an all-
> hosts multicast). Also, such home gateways typically forget all
> dynamic state when rebooted, so they have absolutely no idea who
> their erstwhile clients were, so the *only* option they have is to
> multicast a message to all potential clients saying, "Hey, I'm back."
>
> Therefore multicast is both necessary and sufficient for these  
> devices.
>
> You may not yourself work on low-cost home gateways, but both Apple
> and Linksys do make home gateways for this market, and I would like
> those home gateways to continue to be at least as good as our
> existing NAT-PMP home gateways.

On 27 Oct 2011, at 6:47 PM, Reinaldo Penno wrote:

Hello Stuart,

> It seems we are in agreement then.
>
> Thanks,
>
> Reinaldo

Excellent. I will incorporate the Rapid Recovery section into draft- 
ietf-pcp-base today.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From cheshire@apple.com  Fri Oct 28 13:57:50 2011
Return-Path: <cheshire@apple.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 4A89711E80AC for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 13:57:50 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oz1s7zRb6E3a for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 13:57:49 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2232411E809F for <pcp@ietf.org>; Fri, 28 Oct 2011 13:57:49 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LTS007QANA3Y4P0@mail-out.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 13:57:47 -0700 (PDT)
X-AuditID: 1180711d-b7b7dae000007623-ab-4eab174b8406
Received: from kencur (kencur.apple.com [17.151.62.38]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 7A.AB.30243.B471BAE4; Fri, 28 Oct 2011 13:57:47 -0700 (PDT)
Received: from [10.0.1.201] ([173.164.252.149]) by kencur.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LTS001ARNKAID20@kencur.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 13:57:47 -0700 (PDT)
In-reply-to: <9B2444EE-1C2C-4B4F-8BCD-C7D30BA050E6@juniper.net>
References: <20111021192647.15411.29692.idtracker@ietfa.amsl.com> <9B2444EE-1C2C-4B4F-8BCD-C7D30BA050E6@juniper.net>
Message-id: <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Fri, 28 Oct 2011 13:58:49 -0700
To: pcp@ietf.org
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOLMWRmVeSWpSXmKPExsUiON1OTddbfLWfweKDWhaTj/1mdWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRsOBJcwF2/0qju+cy9TAOM2qi5GTQ0LARGLyir+sELaYxIV7 69m6GLk4hATamST+zHjEBpLgFRCU+DH5HksXIwcHs4C8xMHzsiBhZgEXia0TWthBbCGBbiaJ 2/8rQWxOAXuJg+/fMEHEyyRmTdvCCDHGRmL9lQ1gNpuAlsSLz1fYQEYKC9hKPJlhBBJmEVCV ePzuFthWEQEBid+rLzNBnCYncfj0K8YJjPyzkBw0C+GgWUgOWsDIvIpRsCg1J7HS0FgvsaAg J1UvOT93EyMouBoKZXcw7v/Jf4hRgINRiYfX8ckqPyHWxLLiytxDjBIczEoivC8eA4V4UxIr q1KL8uOLSnNSiw8xSnOwKInz2vKv9hMSSE8sSc1OTS1ILYLJMnFwSjUw7tzDf3rv7Gcs3Dld C+XuyHMHb1h69tf7NQ80ytRX13T3pTzVVX39bKPHDuvAltPKDG9YxX7M2h48b23JneSmm+rH d1RfEGf2WOvF/H6Ck/4rhQl1esoSz/yt7auZz2x/Mjliv+PsiyYedS468Ykt4YZsa6c/dLhv +4xJZe+Dp/eTeGI+6k/OVmIpzkg01GIuKk4EAJXBANoqAgAA
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 28 Oct 2011 20:57:50 -0000

On 21 Oct 2011, at 12:34 PM, Alain Durand wrote:

> The PCP wg chairs would like to issue a one week wg last call on  
> draft-ietf-pcp-base-16.
>
> Last call ends Friday October 28th at 5pm EST.

Here are some of my concerns about draft-ietf-pcp-base-16.txt.

>    Mapping Types:
>       There are three different ways to create mappings: implicit
>       dynamic mappings, explicit dynamic mappings, and static  
> mappings.
>       Implicit dynamic mappings are created as a result of a TCP  
> SYN or
>       outgoing UDP packet or a PCP PEER request, and allow Internal
>       Hosts to receive replies to their outbound packets.  Explicit
>       dynamic mappings are created as a result of a PCP MAP request.

This is bizarre. Everywhere else in the document the terms explicit  
and implicit are used with their usual meanings:

An explicit mapping is explicitly made via PCP.

An implicit mapping occurs implicitly as a side effect of something  
else (e.g. TCP SYN).

And then "Terminology" redefines the word "implicit" to mean  
"explicitly made (via a PCP PEER request)."

That's bogus. Let's stick with the usual word meanings.

>    PCP Server:
>       A PCP software instance that implements the server side of  
> the PCP
>       protocol, via which PCP clients request and manage explicit
>       mappings.  This is conceptually separate from the NAT or  
> firewall
>       itself

What is that last sentence there for?

What other protocol specification says, "This protocol is  
conceptually separate from what this protocol does"?

Does the DHCP spec say, "A DHCP server is conceptually separate from  
the thing that assigns IP addresses"?

Does the NFS spec say, "An NFS server is conceptually separate from  
the thing that stores files"?

Sure, you could make a diskless NFS front end that interfaces to some  
different back end storage, and everyone knows and understands that  
already. A protocol specification doesn't also need to be an  
introductory computer science tutorial.

> 7.7.1.  UNPROCESSED Option
>
>    If the PCP server cannot process a mandatory-to-process Option, for
>    whatever reason, it includes the UNPROCESSED Option in the  
> response,
>    shown in Figure 5.
>    ...
>    This Option MUST NOT appear in a response unless
>    the associated request contained at least one mandatory-to-process
>    Option.

Why only for mandatory-to-process options? If a PCP server ignores an  
optional option (e.g. because it doesn't understand it) I can imagine  
it might be *extremely* helpful for the client to know that.

Why not use the UNPROCESSED Option for *all* options that for  
whatever reason were not processed?

>                               source  internal  external  remote peer
>                               ------  --------  -------   -----------
>                 IPv4 firewall  IPv4     IPv4      IPv4      IPv4
>                 IPv6 firewall  IPv6     IPv6      IPv6      IPv6
>                         NAT44  IPv4     IPv4      IPv4      IPv4
>        DS-Lite plain mode (1)  IPv6     IPv4      IPv4      IPv4
>            DS-Lite encap. (2)  IPv4     IPv4      IPv4      IPv4
>                     NAT64 (3)  IPv6     IPv6      IPv4      IPv6
>                         NPTv6  IPv6     IPv6      IPv6      IPv6

I find this table a little confusing and misleading.

The source address family *always* matches the internal address  
family when you're not using THIRD_PARTY, and need not match when you  
are using THIRD_PARTY. So the source/internal address family is all  
about THIRD_PARTY or not, and not about the seven scenarios listed.

>    Note that PCP requests containing the MAP or PEER Opcodes cannot
>    delete or shorten the lifetime of an existing implicit mapping for
>    the indicated internal address and port.  Conceptually implicit and
>    explicit mappings are different "layers" in the NAT forwarding  
> state
>    database.

I don't care either way about this, but lots of other places in the  
document contradict it. E.g. an implicit mapping can be "upgraded" to  
an explicit mapping, and then the explicit mapping can be deleted. We  
need to decide what we want and be consistent about it.

>    In (1) and (2), 'source' refers to the PCP messaging between the
>    Dual-Stack Lite B4 element and the AFTR element, with (1) showing
>    Dual-Stack Lite plain mode and (2) showing Dual-Stack Lite

Where is the term "plain mode" introduced?

>    If
>    the PCP server or PCP-controlled device does not support the  
> Protocol
>    or cannot create a mapping for the Protocol (e.g., because the
>    request is for a NAT mapping instead of a firewall mapping and the
>    PCP-controlled device is not a NAT or does not support NATting that
>    specific Protocol), it MUST generate an UNSUPP_PROTOCOL error.

What does that mean? What is a "firewall mapping"? What is a "NAT  
mapping"? Why does the client know or care? The whole point of PCP is  
that the client doesn't know or care -- it asks for a mapping, and  
(except when using the stupid UPnP mode) the server gives it one. End  
of story.

>    If
>    the requested Lifetime is non-zero, the Internal Port is zero, and
>    the Protocol is non-zero, it indicates a request to map all  
> incoming
>    traffic for that entire Protocol.  If this request cannot be
>    fulfilled in its entirety, the error UNSUPP_PROTOCOL MUST be
>    returned.

I think NO_RESOURCES. The UNSUPP_PROTOCOL response says "I don't know  
what you're talking about." In this case the server understands the  
request; it just doesn't currently have the ability to grant it.

>    If the requested lifetime is zero then:
>    ...
>    o  If the internal port is zero and the protocol is non-zero, or  
> the
>       internal port is non-zero and the protocol is zero, then the
>       request is invalid and the PCP Server MUST return a
>       MALFORMED_REQUEST error to the client.

What about deleting an SCTP or port wildcard mapping (allowed  
elsewhere in the document).

>      PEER: Create an implicit dynamic mapping, or set or query an
>            existing implicit dynamic mapping to a remote peer's IP
>            address and port.

No, if we're *explicitly* creating it via a PCP request, it's an  
explicit dynamic mapping, not an implicit dynamic mapping.

> 10.1.  PEER Operation Packet Formats
> ...
>    Remote Peer IP Address:  Remote peer's IP address from the
>       perspective of the PCP client, so that the PCP client does not
>       need to concern itself with NAT64 or NAT46 (which both cause the
>       client's idea of the remote peer's IP address to differ from the
>       remote peer's actual IP address).  This field allows the PCP
>       client and PCP server to disambiguate multiple connections from
>       the same port on the Internal Host to different servers, and  
> does
>       not create or adjust the filtering associated with the mapping
>       (for that, the FILTER option is used, Section 11.3).

No, the FILTER option is not allowed with PEER requests.

>    On receiving the PEER Opcode, the PCP server examines the mapping
>    table.  If the requested mapping does not yet exist, and the
>    Suggested External Address and Port can be honored, the mapping is
>    created.  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
>
>    Note that some PCP servers and
>    some PCP-controlled devices are expected to not support this
>    functionality and will respond with the CANNOT_PROVIDE_EXTERNAL
>    error.

Why? Why are some PCP servers expected to be deficient and suffer  
from this race condition? We should remove this -- it gives the  
appearance of condoning shoddy implementation.

>    After a successful PEER response is sent, it is implementation-
>    specific if the PCP-controlled device destroys the mapping when the
>    lifetime expires, or if the PCP-controlled device's implementation
>    allows traffic to keep the mapping alive.  Thus, if the PCP client
>    wants the mapping to persist beyond the lifetime reported in the
>    response, it MUST refresh the mapping (by sending another PEER
>    message) prior to the expiration of the lifetime.
>
>    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 to outside traffic is not  
> sufficient to
>    ensure the mapping will continue to exist.

This is bogus. It means that a single PEER request 'poisons' a  
preexisting implicit mapping, causing it to then die even while TCP  
traffic is flowing thought it, unless subsequent PEER requests are  
used to keep it alive. A PEER request should be benign, not  
destructive. It may lengthen the life of an existing implicit  
mapping, but it should not kill it.

>    If the mapping is
>    terminated by the TCP client or server (e.g., TCP FIN or TCP RST),
>    the mapping will be destroyed normally; the mapping will not  
> persist
>    for the time indicated by Lifetime.  This means the Lifetime in a
>    PEER response indicates how long the mapping will persist in the
>    absence of a transport termination message (e.g., TCP RST).
>
>    Some transport protocols signal the end of a connection (e.g., TCP
>    FIN, TCP RST, SCTP SHUTDOWN).  After a successful PEER response is
>    sent, the receipt of such a transport-specific message MUST NOT  
> cause
>    the mapping to be destroyed.  Rather, the mapping is maintained  
> until
>    the PEER-signaled lifetime expires.

Which is it? TCP RST destroys a mapping or it does not?

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From cheshire@apple.com  Fri Oct 28 14:08:43 2011
Return-Path: <cheshire@apple.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 33E671F0C40 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 14:08:43 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AjkkTpEmNpOi for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 14:08:42 -0700 (PDT)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3DC1F0C34 for <pcp@ietf.org>; Fri, 28 Oct 2011 14:08:42 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LTS00152NQDURK1@mail-out.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 14:08:25 -0700 (PDT)
X-AuditID: 11807137-b7c56ae0000051ed-0d-4eab19c964c3
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay16.apple.com (Apple SCV relay) with SMTP id 87.E7.20973.9C91BAE4; Fri, 28 Oct 2011 14:08:25 -0700 (PDT)
Received: from [10.0.1.201] ([173.164.252.149]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LTS00LPEO20XG10@cardamom.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 14:08:25 -0700 (PDT)
In-reply-to: <201110261244.p9QCi49O098522@givry.fdupont.fr>
References: <201110261244.p9QCi49O098522@givry.fdupont.fr>
Message-id: <F5147FC1-259B-4DA0-856C-EB5622F1731B@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Fri, 28 Oct 2011 14:08:24 -0700
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrILMWRmVeSWpSXmKPExsUiON1OVfek5Go/g4+7VCwmH/vN6sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujMOHHrAVHGKvWLckoIHxMWsXIweHhICJxMzJNV2MnECmmMSF e+vZuhi5OIQEWpkkPnx4ywzhTGSSuH/tEwtIFaeAtcTcf4/YQZqFBKwk/h/LATF5BYwkOlZU gFQwC7hI7Ll5mhHE5hWwkdjzcw47RFxA4uaJPmYIW15i85q3YDabgJbEi89X2EBsYQFViVkH VzOBjGQBslu36IGERQT0JN5dPcgOcaacxOHTrxgnMArMQlg8C8niWUgWLGBkXsUoWJSak1hp aKaXWFCQk6qXnJ+7iREUcA2F5jsYt/+VO8QowMGoxMP78uEqPyHWxLLiytxDjBIczEoivC8e A4V4UxIrq1KL8uOLSnNSiw8xSnOwKInzOvKv9hMSSE8sSc1OTS1ILYLJMnFwSjUwGuqaMl26 NOn0Ioc9F21mSTc7rlilNN3Lw2m9fJXAv+NunH9Ztq87f2pd+MnVi06qtPouOVEWtLMzLklw TeEkDqcmGf0Vc5Ufzhb4K7mM9X+dc8SMI6mch9Y9C4o53mkmc9vN4un+xxPdRD81siVZ/Ir5 2Ph8hSeLt/7SW8dYz6U6MXz7wR7RqMRSnJFoqMVcVJwIAOSYOSQ0AgAA
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 28 Oct 2011 21:08:43 -0000

On 26 Oct 2011, at 5:44 AM, Francis Dupont wrote:

>  - 9.7 page 44: I have still a concern about:
>
>    Address for cosmetic purposes can achieve that by requesting a  
> short-
>    lived mapping and then displaying the resulting External IP  
> Address.
>    However, once that mapping expires a subsequent implicit or  
> explicit
>    dynamic mapping might be mapped to a different external IP address.
>
>   as it is both pejorative and useless. I strongly suggest to  
> remove it
>   (and to keep the rest of 9.7).

No, it's accurate and informative.

After years of NAT-PMP experience, we have found *no* non-cosmetic  
purpose for getting the external IP address without a mapping to go  
with it.

People have frequently made the mistake of thinking it's useful;  
hence we have this text to point out that it is not.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From cheshire@apple.com  Fri Oct 28 14:19:40 2011
Return-Path: <cheshire@apple.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 0313321F8485 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 14:19:40 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1dDgmIkgMz3n for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 14:19:39 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6F05221F8478 for <pcp@ietf.org>; Fri, 28 Oct 2011 14:19:39 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LTS007J7NVGY4R0@mail-out.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 14:12:14 -0700 (PDT)
X-AuditID: 11807130-b7c1bae000001553-36-4eab1aae9460
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay11.apple.com (Apple SCV relay) with SMTP id A3.56.05459.EAA1BAE4; Fri, 28 Oct 2011 14:12:14 -0700 (PDT)
Received: from [10.0.1.201] ([173.164.252.149]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LTS007QSO8EWH10@koseret.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 14:12:14 -0700 (PDT)
In-reply-to: <201110281436.p9SEa0CM080314@givry.fdupont.fr>
References: <201110281436.p9SEa0CM080314@givry.fdupont.fr>
Message-id: <3BA696AE-DAB4-47D7-8507-37E346085CC5@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Fri, 28 Oct 2011 14:12:13 -0700
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUiON1OXXed1Go/g46LRhaTj/1mdWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRvvri4wFU9gqJm2+wd7A+IGli5GTQ0LARKJr0iVmCFtM4sK9 9WxdjFwcQgKdTBJPry5hA0nwCghK/Jh8D6iBg4NZQF7i4HlZkDCzgIvE1gkt7BD1/UwS/14c ABvKKWAt8WXzFEYQW0jASmLKoy1sIL28AjYSl1/mQfTqSNz//RhsL5uAlsSLz1fAVgkLqErM OriaCcRmAbIv7v8DFhcR0JN4d/UgO8SdchKHT79inMAoMAvJdbMQrpuF5LoFjMyrGAWLUnMS Kw0N9RILCnJS9ZLzczcxgsKuodBgB+Pan/yHGAU4GJV4eGc+W+UnxJpYVlyZe4hRgoNZSYT3 xWOgEG9KYmVValF+fFFpTmrxIUZpDhYlcV47/tV+QgLpiSWp2ampBalFMFkmDk6pBsZsnz+P vIWcFeOeNP0RC/oQc+px4leBFMm8+FqhV9v7HqQn75qcevzbi7vpV7JrjFd6vMyLK/fXN/Dh cW3fu6X7XOvHoPv828sWLv/x/rW5ns0HGW3bu5nuf7kXXI9t5P7x74CTFFPqhqMhLh8+lt14 fbTMcO1iVXWeRz6s5roaUjMedKXMkFZiKc5INNRiLipOBAA+p3d/NwIAAA==
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 28 Oct 2011 21:19:40 -0000

On 28 Oct 2011, at 7:36 AM, Francis Dupont wrote:

> fixed and translated to base 16 terms it means the difference
> between the two delta's must be less than 3600 seconds / one hour
> or the epoch is invalid.

There is no basis for this arbitrary 3600-second value.

All thresholds need to be expressed as a function of the time since  
the last packet from the server and the acceptable clock drift rates.  
Any fixed constant cannot meet that requirement.

(And indeed, if the inter-packet interval is less than 8 hours, the  
test is *already* stricter than your fixed 3600 seconds, so *also*  
checking for 3600 seconds is a pointless waste of CPU cycles.)
>

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From Francis.Dupont@fdupont.fr  Fri Oct 28 16:58:33 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 9714221F84DA for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 16:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YmdDpcbt-l-x for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 16:58:33 -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 AA78B21F84D8 for <pcp@ietf.org>; Fri, 28 Oct 2011 16:58:32 -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 p9SNwSir014559; Sat, 29 Oct 2011 01:58:29 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110282358.p9SNwSir014559@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 14:08:24 PDT. <F5147FC1-259B-4DA0-856C-EB5622F1731B@apple.com> 
Date: Sat, 29 Oct 2011 01:58:28 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 28 Oct 2011 23:58:33 -0000

 In your previous mail you wrote:

   No, it's accurate and informative.
   
=> hum, it seems the only thing we could agree about is we disagree.
There is a procedure to resolve this kind of things, just apply it?

   After years of NAT-PMP experience, we have found *no* non-cosmetic  
   purpose for getting the external IP address without a mapping to go  
   with it.
   
=> I found a non-cosmetic purpose with UPnP IGD IWF and even with
NAT-PMP IWF when the NAT-PMP client is not a code provided by Apple.

   People have frequently made the mistake of thinking it's useful;  
   hence we have this text to point out that it is not.
   
=> you have your opinion, I have mine: they are different.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Fri Oct 28 17:12:34 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 CF2211F0C43 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 17:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8G6qKcDB2Pnb for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 17:12:34 -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 034C61F0C36 for <pcp@ietf.org>; Fri, 28 Oct 2011 17:12:33 -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 p9T0CSEP015556; Sat, 29 Oct 2011 02:12:28 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110290012.p9T0CSEP015556@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 14:12:13 PDT. <3BA696AE-DAB4-47D7-8507-37E346085CC5@apple.com> 
Date: Sat, 29 Oct 2011 02:12:28 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 29 Oct 2011 00:12:34 -0000

 In your previous mail you wrote:

   On 28 Oct 2011, at 7:36 AM, Francis Dupont wrote:
   
   > fixed and translated to base 16 terms it means the difference
   > between the two delta's must be less than 3600 seconds / one hour
   > or the epoch is invalid.
   
   There is no basis for this arbitrary 3600-second value.
   
=> for the value itself I agree, and I leave this point to the
person who added it in base 14.

   All thresholds need to be expressed as a function of the time since  
   the last packet from the server and the acceptable clock drift rates.  
   Any fixed constant cannot meet that requirement.
   
=> I disagree: a fixed threshold can catch insane cummulate drifts,
or clock jumps.

   (And indeed, if the inter-packet interval is less than 8 hours, the  
   test is *already* stricter than your fixed 3600 seconds, so *also*  
   checking for 3600 seconds is a pointless waste of CPU cycles.)

=> I consider you forgot the smiley here...

Regards

Francis.Dupont@fdupont.fr

PS: SEND (RFC 3971) has a delta, a drift and a fuzz. Even if SEND
is a bit different (security device using absolute clocks) there is
no reason to not look at it. This is why I was happy to get the
fixed threshold and less happy to lose it...

From jhw@apple.com  Fri Oct 28 17:45:35 2011
Return-Path: <jhw@apple.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 10D5B11E8089 for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 17:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.564
X-Spam-Level: 
X-Spam-Status: No, score=-106.564 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ljbDuHcC7QhM for <pcp@ietfa.amsl.com>; Fri, 28 Oct 2011 17:45:34 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9F3A911E8081 for <pcp@ietf.org>; Fri, 28 Oct 2011 17:45:34 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_LAYCJUxBN25Vx/1mBvbeVg)"
Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LTS0072GY3PY4S1@mail-out.apple.com> for pcp@ietf.org; Fri, 28 Oct 2011 17:45:33 -0700 (PDT)
X-AuditID: 11807136-b7c19ae0000072b0-d2-4eab4cac7f01
Received: from ba0301a-dhcp89.apple.com (ba0301a-dhcp89.apple.com [17.193.14.217]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay15.apple.com (Apple SCV relay) with SMTP id E8.A4.29360.DAC4BAE4; Fri, 28 Oct 2011 17:45:33 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
Date: Fri, 28 Oct 2011 17:45:32 -0700
In-reply-to: <201110282358.p9SNwSir014559@givry.fdupont.fr>
To: PCP <pcp@ietf.org>
References: <201110282358.p9SNwSir014559@givry.fdupont.fr>
Message-id: <5D00E208-6506-4ED9-B653-12FD9B1CFD80@apple.com>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrILMWRmVeSWpSXmKPExsUieJDvpu5an9V+Bq+PsVlMPvab1YHRY8mS n0wBjFFcNimpOZllqUX6dglcGZNPb2Qv+K1U8eWVUQPjRbkuRg4OCQETif77+l2MnECmmMSF e+vZuhi5OIQEVjBJTG45ywaSYBNQkfh2+S4TiM0rYCyx5tY7FhCbWSBBYuukE2BxYQFViVkH VzOBzGQBsi+8rwEJcwpYS3yf9Z8RxBYBmr/68UOwciEBK4nu2xvYQcp5BWwk7m9UgDhBXqLl 6x22CYy8s5Asm4VkGYStLbFs4WvmWUDdzAI6EpMXMqIKQ9gfzx9hWsDItopRsCg1J7HS0FQv saAgJ1UvOT93EyMo4BoKzXYw7vgrd4hRgINRiYfX4ckqPyHWxLLiytxDjBIczEoivC8eA4V4 UxIrq1KL8uOLSnNSiw8xSnOwKInzOvKv9hMSSE8sSc1OTS1ILYLJMnFwSjUw5rnu3WVrcurO qa1125llg/4xHz91fd3diJs7qgRjXLon931Y+7qWTzH+tfB0C8bS1hX7Qv0ilaWqu7z2524r c834+UsppzVSTyJyxdLyf8ffTHnItjuoec/8E+ULFO7lzd+9qMezJflk3YM0/rCKS6yma2Zo Kx/xXl/te+CzRsSKLUGZ82QClFiKMxINtZiLihMBF/WF0TQCAAA=
Subject: Re: [pcp] base 16 review (2)
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, 29 Oct 2011 00:45:35 -0000

--Boundary_(ID_LAYCJUxBN25Vx/1mBvbeVg)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

On Oct 28, 2011, at 4:58 PM, Francis Dupont wrote:
> 
>   After years of NAT-PMP experience, we have found *no* non-cosmetic  
>   purpose for getting the external IP address without a mapping to go  
>   with it.
> 
> => I found a non-cosmetic purpose with UPnP IGD IWF and even with
> NAT-PMP IWF when the NAT-PMP client is not a code provided by Apple.

I'm sure there is a truly marvelous demonstration of that proposition, which the margins of a standard Internet message are, alas and alack, too narrow to contain.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




--Boundary_(ID_LAYCJUxBN25Vx/1mBvbeVg)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Oct 28, 2011, at 4:58 PM, Francis Dupont =
wrote:</div><blockquote type=3D"cite"><br =
class=3D"Apple-interchange-newline"></blockquote><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">&nbsp;&nbsp;After years of NAT-PMP experience, we have found *no* =
non-cosmetic &nbsp;<br>&nbsp;&nbsp;purpose for getting the external IP =
address without a mapping to go &nbsp;<br>&nbsp;&nbsp;with =
it.<br><br>=3D&gt; I found a non-cosmetic purpose with UPnP IGD IWF and =
even with<br>NAT-PMP IWF when the NAT-PMP client is not a code provided =
by Apple.<br></span></blockquote></div><br><div>I'm sure there is a =
truly marvelous demonstration of that proposition, which the margins of =
a standard Internet message are, alas and alack, too narrow to =
contain.</div><div><br class=3D"webkit-block-placeholder"></div><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Gill Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
12px; "><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><br =
class=3D"Apple-interchange-newline">--</span></span></div><div =
style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">james woodyatt &lt;<a =
href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&gt;</span></span></span></=
div><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">member of technical staff, core os =
networking</span></span></span></div><br =
class=3D"Apple-interchange-newline" style=3D"font-size: 11px; =
font-family: Geneva; "></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Boundary_(ID_LAYCJUxBN25Vx/1mBvbeVg)--

From Francis.Dupont@fdupont.fr  Sat Oct 29 09:06:05 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 9181421F8A4B for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lWc-tSS+9F4n for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:06:05 -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 944B521F8A35 for <pcp@ietf.org>; Sat, 29 Oct 2011 09:06:04 -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 p9TG5x4S074321; Sat, 29 Oct 2011 18:05:59 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291605.p9TG5x4S074321@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: james woodyatt <jhw@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 17:45:32 PDT. <5D00E208-6506-4ED9-B653-12FD9B1CFD80@apple.com> 
Date: Sat, 29 Oct 2011 18:05:59 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: PCP <pcp@ietf.org>
Subject: Re: [pcp] base 16 review (2)
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, 29 Oct 2011 16:06:05 -0000

 In your previous mail you wrote:

   On Oct 28, 2011, at 4:58 PM, Francis Dupont wrote:
   > 
   >   After years of NAT-PMP experience, we have found *no* non-cosmetic  
   >   purpose for getting the external IP address without a mapping to go  
   >   with it.
   > 
   > => I found a non-cosmetic purpose with UPnP IGD IWF and even with
   > NAT-PMP IWF when the NAT-PMP client is not a code provided by Apple.
   
  I'm sure there is a truly marvelous demonstration of that
  proposition, which the margins of a standard Internet message are,
  alas and alack, too narrow to contain.
   
=> I believe you want a proof of the second (about NAT-PMP), so I can
put the URL in this message:

http://miniupnp.free.fr/files/download.php?file=libnatpmp-20110808.tar.gz

Regards

Francis.Dupont@fdupont.fr

PS: the details for interested people:

the sample client (and all the applications using this NAT-PMP client
library, for instance the transmission Torrent client) loops sending
public address requests and gives up after a reasonnable amount of
retries:

$ ./natpmpc-static 
initnatpmp() returned 0 (SUCCESS)
using gateway : 192.168.0.254
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -7 (FAILED)
readnatpmpresponseorretry() failed : the gateway does not support nat-pmp
  errno=11 'Resource temporarily unavailable'

And the tshark (wireshark output doesn't fit in this text message):

# tshark udp port 5351
no register file /usr/local/lib/wireshark/python/1.4.7/register-dissector.py
Running as user "root" and group "root". This could be dangerous.
Capturing on eth0
  0.000000 192.168.0.40 -> 192.168.0.254 NAT-PMP External Address Request
  0.250394 192.168.0.40 -> 192.168.0.254 NAT-PMP External Address Request
  0.750576 192.168.0.40 -> 192.168.0.254 NAT-PMP External Address Request
  1.751072 192.168.0.40 -> 192.168.0.254 NAT-PMP External Address Request
  3.752074 192.168.0.40 -> 192.168.0.254 NAT-PMP External Address Request
  7.754071 192.168.0.40 -> 192.168.0.254 NAT-PMP External Address Request
 15.750151 192.168.0.40 -> 192.168.0.254 NAT-PMP External Address Request
 31.766072 192.168.0.40 -> 192.168.0.254 NAT-PMP External Address Request
 63.782091 192.168.0.40 -> 192.168.0.254 NAT-PMP External Address Request


From Francis.Dupont@fdupont.fr  Sat Oct 29 09:21:38 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 8978A21F8AD3 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.058,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RG-pD7oEyAfc for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:21:37 -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 7D74121F8AAC for <pcp@ietf.org>; Sat, 29 Oct 2011 09:21:36 -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 p9TGLWYi075255; Sat, 29 Oct 2011 18:21:32 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291621.p9TGLWYi075255@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 18:21:32 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 16:21:39 -0000

 In your previous mail you wrote:

   On 21 Oct 2011, at 12:34 PM, Alain Durand wrote:
   
   > The PCP wg chairs would like to issue a one week wg last call on  
   > draft-ietf-pcp-base-16.
   >
   > Last call ends Friday October 28th at 5pm EST.
   
   Here are some of my concerns about draft-ietf-pcp-base-16.txt.
   
=> as far as I know you are one of the authors so you should not
still have heavy concerns about the document?

   >    Mapping Types:
   >       There are three different ways to create mappings: implicit
   >       dynamic mappings, explicit dynamic mappings, and static  
   > mappings.
   >       Implicit dynamic mappings are created as a result of a TCP  
   > SYN or
   >       outgoing UDP packet or a PCP PEER request, and allow Internal
   >       Hosts to receive replies to their outbound packets.  Explicit
   >       dynamic mappings are created as a result of a PCP MAP request.
   
   This is bizarre. Everywhere else in the document the terms explicit  
   and implicit are used with their usual meanings:
   
   An explicit mapping is explicitly made via PCP.
   
   An implicit mapping occurs implicitly as a side effect of something  
   else (e.g. TCP SYN).
   
   And then "Terminology" redefines the word "implicit" to mean  
   "explicitly made (via a PCP PEER request)."
   
   That's bogus. Let's stick with the usual word meanings.
   
=> the terminology was defined independently from PCP itself
(BTW I think the terminology was one of the big things the PCP work
brought so IMHO we should defend it if there is no clearly better
proposal).

I agree the fact a PEER request can create an implicit dynamic mapping
is a bit strange from the pure language point of view, now the solutions
are:
 - live with it as we have no better proposal

 - get rid of this function of PEER, i.e., make PEER requests only
  query and extend lifetime of implicit dynamic mappings

 - get rid of the PEER opcode as if it loses this function it has
  a low interest (or move it to another document)

 - rename implicit dynamic mappings, explicit dynamic mappings and
  static mappings into type one mappings, type two mappings and
  type three mappings so the document will be unreadable but
  correct

BTW the two middle solutions were already discussed (I asked for
them :-) and the WG decision seemed to be no in both cases,
so we have the choice between doing nothing and the renaming.

BTW if your intent is just to change the type managed by
the PEER opcode I'll strongly object.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 09:29:11 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 15CEE21F8AD3 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h3G-BTWCTM0Y for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:29:10 -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 2C7F321F8663 for <pcp@ietf.org>; Sat, 29 Oct 2011 09:29:09 -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 p9TGT6XF075728; Sat, 29 Oct 2011 18:29:06 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291629.p9TGT6XF075728@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 18:29:06 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 16:29:11 -0000

 In your previous mail you wrote:

   >    PCP Server:
   >       A PCP software instance that implements the server side of  
   > the PCP
   >       protocol, via which PCP clients request and manage explicit
   >       mappings.  This is conceptually separate from the NAT or  
   > firewall
   >       itself
   
   What is that last sentence there for?
   
=> it is just without entering into details the fact the PCP server
is a control plane device when the NAT (or firewall) itself is
a forwarding plane device.
IMHO the real reason is to kill the idea there is a mandatory 1:1
binding between the PCP server (essentially a protocol engine)
and the NAT/firewall it controls, i.e., a PCP server can control
more than one device or a device can be controlled by more than
one PCP server.

   What other protocol specification says, "This protocol is  
   conceptually separate from what this protocol does"?
   
=> s/does/controls/

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 09:33:11 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 AA50721F862F for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZ6t0hRsPnCn for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:33:10 -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 C261F21F84FD for <pcp@ietf.org>; Sat, 29 Oct 2011 09:32:21 -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 p9TGWI4k075907; Sat, 29 Oct 2011 18:32:18 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291632.p9TGWI4k075907@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 18:32:18 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 16:33:11 -0000

 In your previous mail you wrote:

   > 7.7.1.  UNPROCESSED Option
   >
   >    If the PCP server cannot process a mandatory-to-process Option, for
   >    whatever reason, it includes the UNPROCESSED Option in the  
   > response,
   >    shown in Figure 5.
   >    ...
   >    This Option MUST NOT appear in a response unless
   >    the associated request contained at least one mandatory-to-process
   >    Option.
   
   Why only for mandatory-to-process options? If a PCP server ignores an  
   optional option (e.g. because it doesn't understand it) I can imagine  
   it might be *extremely* helpful for the client to know that.
   
   Why not use the UNPROCESSED Option for *all* options that for  
   whatever reason were not processed?
   
=> in fact I have a related question: is there a known case where
an option could be optional with the current definition of optional
(i.e., the server can silently ignore it)?
If there is none we just waste the half of the option code space,
if there is at least one we have a counter example.

Regards

Francis.Dupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 09:37:37 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 3EE8D21F86EE for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qy4ievVLykRR for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:37:36 -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 5115821F8663 for <pcp@ietf.org>; Sat, 29 Oct 2011 09:37:36 -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 p9TGbT4n076214; Sat, 29 Oct 2011 18:37:29 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291637.p9TGbT4n076214@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 18:37:29 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 16:37:37 -0000

 In your previous mail you wrote:

   >                               source  internal  external  remote peer
   >                               ------  --------  -------   -----------
   >                 IPv4 firewall  IPv4     IPv4      IPv4      IPv4
   >                 IPv6 firewall  IPv6     IPv6      IPv6      IPv6
   >                         NAT44  IPv4     IPv4      IPv4      IPv4
   >        DS-Lite plain mode (1)  IPv6     IPv4      IPv4      IPv4
   >            DS-Lite encap. (2)  IPv4     IPv4      IPv4      IPv4
   >                     NAT64 (3)  IPv6     IPv6      IPv4      IPv6
   >                         NPTv6  IPv6     IPv6      IPv6      IPv6
   
   I find this table a little confusing and misleading.
   
   The source address family *always* matches the internal address  
   family when you're not using THIRD_PARTY, and need not match when you  
   are using THIRD_PARTY. So the source/internal address family is all  
   about THIRD_PARTY or not, and not about the seven scenarios listed.
   
=> if you mean when the source and the internal addresses have a
different family there must be a THIRD_PARTY option I can't disagree.
But how is this confusing? All the 4 kinds of addresses are
defined before the table, and the internal address definition says
exactly what we want, i.e.:

   ... 'internal' is the Internal IP Address field of the
   THIRD_PARTY Option (if present) or the same as the source address of
   the PCP packet iself (if the THIRD_PARTY Option is not present),

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 09:46:59 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 DFA7821F84C5 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HBegwQjJIHkB for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:46:59 -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 2FD4021F84B7 for <pcp@ietf.org>; Sat, 29 Oct 2011 09:46:59 -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 p9TGkttN076773; Sat, 29 Oct 2011 18:46:55 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291646.p9TGkttN076773@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 18:46:55 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 16:47:00 -0000

 In your previous mail you wrote:

   >    Note that PCP requests containing the MAP or PEER Opcodes cannot
   >    delete or shorten the lifetime of an existing implicit mapping for
   >    the indicated internal address and port.  Conceptually implicit and
   >    explicit mappings are different "layers" in the NAT forwarding  
   > state
   >    database.
   
   I don't care either way about this, but lots of other places in the  
   document contradict it.

=> if you concern is about the PEER edition glitch which got back
the implementation-dependent lifetime reduction and delete I agree
but I am afraid it is not...

   E.g. an implicit mapping can be "upgraded" to  
   an explicit mapping, and then the explicit mapping can be deleted. We  
   need to decide what we want and be consistent about it.
   
=> I have no problem with this, BTW you have the same thing for static
mappings, i.e., an explicit dynamic mapping can be upgraded (and
this word was carefully chosen) into a static mapping via the Web interface
for instance. And IMHO this could be not a rare operation
(at the opposite of the implicit -> explicit which comes a should not
happen condition)

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 09:54:06 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 66E9721F8A35 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OJdLCb4zjXwT for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 09:54:06 -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 B06D121F8888 for <pcp@ietf.org>; Sat, 29 Oct 2011 09:54:05 -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 p9TGs25i077229; Sat, 29 Oct 2011 18:54:02 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291654.p9TGs25i077229@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 18:54:02 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 16:54:06 -0000

 In your previous mail you wrote:

   >    In (1) and (2), 'source' refers to the PCP messaging between the
   >    Dual-Stack Lite B4 element and the AFTR element, with (1) showing
   >    Dual-Stack Lite plain mode and (2) showing Dual-Stack Lite
   
   Where is the term "plain mode" introduced?
   
=> [I-D.dupont-pcp-dslite] aka draft-dupont-pcp-dslite-00.txt
(and soon 01.txt as I have a pending request to add a line in it
from Mohammed). I can't see a formal issue to use this kind of
terms when:
 - they are very localized (and it is the case, the two occurrences
  of 'plain mode' are in the figure and its explanation
 - the document where they are defined is immediately referenced
(BTW I put they because you have also "encapsulation mode" and
my statement is a general one).

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 10:01:58 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 BB25F21F891D for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level: 
X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szxZEFNE-Yqg for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:01:58 -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 EDBF221F861E for <pcp@ietf.org>; Sat, 29 Oct 2011 10:01:57 -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 p9TH1sBg077719; Sat, 29 Oct 2011 19:01:54 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291701.p9TH1sBg077719@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 19:01:54 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 17:01:58 -0000

 In your previous mail you wrote:

   >    If
   >    the PCP server or PCP-controlled device does not support the  
   > Protocol
   >    or cannot create a mapping for the Protocol (e.g., because the
   >    request is for a NAT mapping instead of a firewall mapping and the
   >    PCP-controlled device is not a NAT or does not support NATting that
   >    specific Protocol), it MUST generate an UNSUPP_PROTOCOL error.
   
   What does that mean? What is a "firewall mapping"? What is a "NAT  
   mapping"?

=> explained in section 3 about terminology.

 Why does the client know or care?

=> if a device embeds both a NAT and a firewall (s)he can really care.

   The whole point of PCP is that the client doesn't know or care --
   it asks for a mapping, and (except when using the stupid UPnP mode)
   the server gives it one. End of story.
   
=> this is your opinion but I don't share it, I know a lot of people
who don't share it, including in the PCP WG and in NAT implementors.
If you really have the power to change the world, please first make
NATs to disappear (:-).

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 10:08:02 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 2D9D421F86D0 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YhyrMdJRJCLc for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:08:01 -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 52D9321F861E for <pcp@ietf.org>; Sat, 29 Oct 2011 10:08:01 -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 p9TH7vFe078167; Sat, 29 Oct 2011 19:07:57 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291707.p9TH7vFe078167@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 19:07:57 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 17:08:02 -0000

 In your previous mail you wrote:

   >    If
   >    the requested Lifetime is non-zero, the Internal Port is zero, and
   >    the Protocol is non-zero, it indicates a request to map all  
   > incoming
   >    traffic for that entire Protocol.  If this request cannot be
   >    fulfilled in its entirety, the error UNSUPP_PROTOCOL MUST be
   >    returned.
   
=> I have a concern about this but not the same: I believe it applies
only to protocols which have no 16-bit ports. I sent a comment
about this using as argument the internal port definition:

   Internal Port:  Internal port for the mapping.  The value 0 indicates
      "all ports", and is legal when the lifetime is zero (a delete
      request), if the Protocol does not use 16-bit port numbers, or the
      Protocol is 0 (meaning 'all protocols')

so if we add the two texts (your citation and mine) the specified error
is the right one.

   I think NO_RESOURCES. The UNSUPP_PROTOCOL response says "I don't know  
   what you're talking about." In this case the server understands the  
   request; it just doesn't currently have the ability to grant it.
   
=> so the question is whether the error is about ports or protocol,
BTW I believe the Editor answered so I can dig into my mails to
verify if my interpretation is the right one.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 10:18:12 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 9BA4021F8AB0 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7xr1Hef5Hpzz for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:18:12 -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 DA00321F8A95 for <pcp@ietf.org>; Sat, 29 Oct 2011 10:18:11 -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 p9THI8Mh078811; Sat, 29 Oct 2011 19:18:08 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291718.p9THI8Mh078811@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 19:18:08 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 17:18:12 -0000

 In your previous mail you wrote:

   >    ...
   >    o  If the internal port is zero and the protocol is non-zero, or  
   > the
   >       internal port is non-zero and the protocol is zero, then the
   >       request is invalid and the PCP Server MUST return a
   >       MALFORMED_REQUEST error to the client.
   
   What about deleting an SCTP

=> it is not the right example, cf 12.3.3

   or port wildcard mapping (allowed  elsewhere in the document).

=> they are not allowed in general but I agree there is a corner case
where it is possible to create a mapping but not to delete it.
The problem is in the first part when the non-zero protocol doesn't
use 16-bit ports, for instance IPsec ESP.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 10:20:40 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 0165A21F8514 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KRuROjmZh1bS for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:20:39 -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 D34A821F852E for <pcp@ietf.org>; Sat, 29 Oct 2011 10:20:38 -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 p9THKZFg078938; Sat, 29 Oct 2011 19:20:35 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291720.p9THKZFg078938@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 19:20:35 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 17:20:40 -0000

 In your previous mail you wrote:

   >      PEER: Create an implicit dynamic mapping, or set or query an
   >            existing implicit dynamic mapping to a remote peer's IP
   >            address and port.
   
   No, if we're *explicitly* creating it via a PCP request, it's an  
   explicit dynamic mapping, not an implicit dynamic mapping.
   
=> no, it is not an explicit dynamic mapping as defined in the
terminology, in particular on at least 70% of the existing NAT it
is not EIM/EIF, etc.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 10:26:43 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 17F4F21F87C2 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GdjcV169pWws for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:26:42 -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 2D99821F8505 for <pcp@ietf.org>; Sat, 29 Oct 2011 10:26:41 -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 p9THQcQr079302; Sat, 29 Oct 2011 19:26:38 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291726.p9THQcQr079302@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 19:26:38 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 17:26:43 -0000

 In your previous mail you wrote:

   > 10.1.  PEER Operation Packet Formats
   > ...
   >    Remote Peer IP Address:  Remote peer's IP address from the
   >       perspective of the PCP client, so that the PCP client does not
   >       need to concern itself with NAT64 or NAT46 (which both cause the
   >       client's idea of the remote peer's IP address to differ from the
   >       remote peer's actual IP address).  This field allows the PCP
   >       client and PCP server to disambiguate multiple connections from
   >       the same port on the Internal Host to different servers, and  
   > does
   >       not create or adjust the filtering associated with the mapping
   >       (for that, the FILTER option is used, Section 11.3).
   
   No, the FILTER option is not allowed with PEER requests.
   
=> it can be a wording problem: the note just says if you want
to create an EIM mapping with a specific filtering than you should
use a MAP request with a FILTER option, *and* this is deeply
different from the previous sentence which is about the *mode*
(as it can be shown by applying it to an EIM NAT: the remote peer
doesn't matter, in fact on an EIM NAT the remote peer address and
port are simply ignored by the NAT code handling PEER requests).

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 10:33:42 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 9A44821F8ADC for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.051,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qENoAeJtV08h for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:33:42 -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 CB51821F8AD6 for <pcp@ietf.org>; Sat, 29 Oct 2011 10:33:41 -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 p9THXcfh079724; Sat, 29 Oct 2011 19:33:38 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291733.p9THXcfh079724@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 19:33:38 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 17:33:42 -0000

 In your previous mail you wrote:

   >    On receiving the PEER Opcode, the PCP server examines the mapping
   >    table.  If the requested mapping does not yet exist, and the
   >    Suggested External Address and Port can be honored, the mapping is
   >    created.  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
   >
   >    Note that some PCP servers and
   >    some PCP-controlled devices are expected to not support this
   >    functionality and will respond with the CANNOT_PROVIDE_EXTERNAL
   >    error.
   
   Why? Why are some PCP servers expected to be deficient and suffer  
   from this race condition? We should remove this -- it gives the  
   appearance of condoning shoddy implementation.
   
=> what you want to remove? the text explaining there is a race
so you should do the things in the right order to avoid it,
or all the NATs which can show the race condition? or your
concern is about the last paragraph?

About the first IMHO users must understand what they do so
I object to remove it. About the others they are about NAT
implementations and if you don't like some I can say than
personally I hate NATs so I like none (:-).
To be serious NAT implementations are explicitly out of scope
by the WG charter.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 10:41:01 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 A596D21F84FD for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.051,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JJVxEhmTmj2I for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:41:01 -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 B7D1D21F84AC for <pcp@ietf.org>; Sat, 29 Oct 2011 10:41:00 -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 p9THesKt080129; Sat, 29 Oct 2011 19:40:54 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291740.p9THesKt080129@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 19:40:54 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 17:41:01 -0000

 In your previous mail you wrote:

   >    After a successful PEER response is sent, it is implementation-
   >    specific if the PCP-controlled device destroys the mapping when the
   >    lifetime expires, or if the PCP-controlled device's implementation
   >    allows traffic to keep the mapping alive.  Thus, if the PCP client
   >    wants the mapping to persist beyond the lifetime reported in the
   >    response, it MUST refresh the mapping (by sending another PEER
   >    message) prior to the expiration of the lifetime.
   >
   >    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 to outside traffic is not  
   > sufficient to
   >    ensure the mapping will continue to exist.
   
   This is bogus. It means that a single PEER request 'poisons' a  
   preexisting implicit mapping, causing it to then die even while TCP  
   traffic is flowing thought it, unless subsequent PEER requests are  
   used to keep it alive. A PEER request should be benign, not  
   destructive. It may lengthen the life of an existing implicit  
   mapping, but it should not kill it.
   
=> it is implementation-specific because the NAT behavior is
out of the scope by the WG charter. The remaining text is just
providing a way to avoid the dependence on the implementation
(i.e., works in all cases). I can't see a problem with this
as it is something we can't change.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Oct 29 10:53:45 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 5293921F85B1 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rB-WbD3jAPeP for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:53:42 -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 054BC21F8511 for <pcp@ietf.org>; Sat, 29 Oct 2011 10:53:30 -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 p9THrRcv080884; Sat, 29 Oct 2011 19:53:27 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291753.p9THrRcv080884@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 13:58:49 PDT. <DC404ED6-225A-4C4D-B361-18C71CCC90D5@apple.com> 
Date: Sat, 29 Oct 2011 19:53:27 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 17:53:46 -0000

 In your previous mail you wrote:

   >    If the mapping is
   >    terminated by the TCP client or server (e.g., TCP FIN or TCP RST),
   >    the mapping will be destroyed normally; the mapping will not  
   > persist
   >    for the time indicated by Lifetime.  This means the Lifetime in a
   >    PEER response indicates how long the mapping will persist in the
   >    absence of a transport termination message (e.g., TCP RST).
   >
   >    Some transport protocols signal the end of a connection (e.g., TCP
   >    FIN, TCP RST, SCTP SHUTDOWN).  After a successful PEER response is
   >    sent, the receipt of such a transport-specific message MUST NOT  
   > cause
   >    the mapping to be destroyed.  Rather, the mapping is maintained  
   > until
   >    the PEER-signaled lifetime expires.
   
   Which is it? TCP RST destroys a mapping or it does not?
   
=> yes, it is self contradicting in a few lines. But the text after is
worse:

   ... If the PCP client wishes to
   terminate the mapping prior to this, it will send a PEER request with
   Lifetime set to 0, which MAY be honored by the PCP server; as stated
   earlier, that is implementation-dependent.

=> as far as I can remember we (WG in previous discussions) agreed:
 - there should be *no* implementation-dependent lifetime reductions
  (at least two arguments: it is useless if it is implementation
   dependent; it is incompatible with the query function)

 - there is no use case for the "0 deleting" so it was removed

BTW if you believe the PEER opcode should be limited to the query
and lifetime extension of existing implicit dynamic mappings,
putting creation and other dubious functions to further studies,
I'll jump on the table to support you (:-)! (*)

Regards

Francis.Dupont@fdupont.fr

PS (*): BTW it seems I am the only implementor which really
want to support the PEER opcode, so if you don't receive
complains about some insane ideas about PEER, please ask why...

From cheshire@apple.com  Sat Oct 29 10:56:22 2011
Return-Path: <cheshire@apple.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 B976F21F84C3 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:56:22 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VkcgHl0UKIzM for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 10:56:22 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 19F1721F84BD for <pcp@ietf.org>; Sat, 29 Oct 2011 10:56:22 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LTU007GQ9N3ZRO0@mail-out.apple.com> for pcp@ietf.org; Sat, 29 Oct 2011 10:56:19 -0700 (PDT)
X-AuditID: 1180711d-b7b7dae000007623-27-4eac3e43ab67
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id A3.DC.30243.34E3CAE4; Sat, 29 Oct 2011 10:56:19 -0700 (PDT)
Received: from [10.0.1.201] ([173.164.252.149]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LTU00AT69TUXP10@cardamom.apple.com> for pcp@ietf.org; Sat, 29 Oct 2011 10:56:19 -0700 (PDT)
In-reply-to: <201110282358.p9SNwSir014559@givry.fdupont.fr>
References: <201110282358.p9SNwSir014559@givry.fdupont.fr>
Message-id: <2E1BEE18-97E6-4C15-A6BE-291502778044@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Sat, 29 Oct 2011 10:56:21 -0700
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKLMWRmVeSWpSXmKPExsUiON1OVdfZbo2fwbtHhhaTj/1mdWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxtWpN1gLjrFX3Fj9lrGB8TNrFyMnh4SAiUT7l5ksELaYxIV7 69m6GLk4hARamSQ+/5rOAuFMZJI4fWgfG0gVp4C1xP1VnxhBbCEBK4nu2xvYuxg5OHgFjCQ6 VlSAhJkFXCT23DwNVsIrYCOxZe8+Joi4gMTNE33MELa8xOY1b8FsNgEtiRefr4CNFxZQlZh1 cDVYPQuQvXn6Y7AaEQE9iXdXD7JDHConcfj0K8YJjAKzEDbPQrJ5FpINCxiZVzEKFqXmJFYa GuslFhTkpOol5+duYgQFXkOh7A7G/T/5DzEKcDAq8fA6PlnlJ8SaWFZcmXuIUYKDWUmE9+eE 1X5CvCmJlVWpRfnxRaU5qcWHGKU5WJTEeW35gVIC6YklqdmpqQWpRTBZJg5OqQbGvLOJpdP3 XlZqfyfw7JnArtnf6grLe0sUOKbyl3uU2rG811s8efrGVXnm9w0W7Ot39JkTcnZLe4Sn9Gb/ VpOJ9aWBL448an7t6Xoxa/8u3y2/7Eu+ZPyyd13aoPG9KvLL/qJ/GjueGByL/Fjv3T2v+f6d aX6PS0975E9fk/sk+eZdHymOqpmaSizFGYmGWsxFxYkAV3AfnDgCAAA=
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 29 Oct 2011 17:56:22 -0000

On 28 Oct 2011, at 4:58 PM, Francis Dupont wrote:

> => I found a non-cosmetic purpose with UPnP IGD IWF and even with
> NAT-PMP IWF when the NAT-PMP client is not a code provided by Apple.

Are you going to tell us, or is it a secret?

NAT-PMP has an opcode to request the external address.

The reason PCP does *not* have such an opcode is that it was agreed  
on the list to have no useful purpose.

While I've argued that PCP generally ought to be a superset of NAT- 
PMP, this is one area where I conceded that this aspect of NAT-PMP  
turned out to not be necessary.

I'm surprised to hear you, Francis, arguing for feature parity with  
NAT-PMP, when the NAT-PMP authors themselves accept that an opcode to  
request the external address was a mistake. (What does it even mean  
for a CGN with a large pool of external addresses?)

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From cheshire@apple.com  Sat Oct 29 11:16:01 2011
Return-Path: <cheshire@apple.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 9E76321F84D2 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 11:16:01 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SOPlqPjuOH-S for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 11:16:00 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id BCB7221F84CE for <pcp@ietf.org>; Sat, 29 Oct 2011 11:16:00 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LTU006UPAQ6PGF0@mail-out.apple.com> for pcp@ietf.org; Sat, 29 Oct 2011 11:16:00 -0700 (PDT)
X-AuditID: 11807136-b7c19ae0000072b0-00-4eac42e0993b
Received: from kencur (kencur.apple.com [17.151.62.38]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay15.apple.com (Apple SCV relay) with SMTP id C6.56.29360.0E24CAE4; Sat, 29 Oct 2011 11:16:00 -0700 (PDT)
Received: from [10.0.1.201] ([173.164.252.149]) by kencur.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LTU00A80AQNK430@kencur.apple.com> for pcp@ietf.org; Sat, 29 Oct 2011 11:16:00 -0700 (PDT)
In-reply-to: <201110290012.p9T0CSEP015556@givry.fdupont.fr>
References: <201110290012.p9T0CSEP015556@givry.fdupont.fr>
Message-id: <4F967664-2782-48FF-8896-B609289ED797@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Sat, 29 Oct 2011 11:16:02 -0700
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMLMWRmVeSWpSXmKPExsUiON1OTfeB0xo/g54mcYvJx36zOjB6LFny kymAMYrLJiU1J7MstUjfLoEr4+TKkywFR3kqPpx7xtLAeIuzi5GTQ0LAROLW7AWsELaYxIV7 69lAbCGBdiaJH6eMQWxeAUGJH5PvsXQxcnAwC8hLHDwvCxJmFnCR2Dqhhb2LkQuovJtJ4vun KYwgCU4Ba4m9Xe8YIeZYSaxY3MsE0ssrYCNxf6kPRK+OxP3fj5lBbDYBLYkXn6+ArRUWUJWY dXA1E4jNAmRvfLENLC4ioCfx7upBdogz5SQOn37FOIFRYBaS62YhXDcLyXULGJlXMQoWpeYk Vhqa6iUWFOSk6iXn525iBAVdQ6HZDsYdf+UOMQpwMCrx8Do8WeUnxJpYVlyZe4hRgoNZSYT3 54TVfkK8KYmVValF+fFFpTmpxYcYpTlYlMR5HfmBUgLpiSWp2ampBalFMFkmDk6pBsbtOx+2 xW7ukeox2PP3w+FjDX4vcz6kPchvNtLhYshf36m3fn6ViNv2Q1KPQldX3Jx7kyP3/NcbXzc4 zn4tHR7yZj3Pu5Jbr7XkPFsOrT39aG19jHLKy583J+eVLbmd2xMSfvTM293lpen9V7ZzsFr/ jmY6sMRo35M5z0z8+jRanHsFfLY92vxKiaU4I9FQi7moOBEA/Wx3OTYCAAA=
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 29 Oct 2011 18:16:01 -0000

On 28 Oct 2011, at 5:12 PM, Francis Dupont wrote:

>    There is no basis for this arbitrary 3600-second value.
>
> => for the value itself I agree, and I leave this point to the  
> person who added it in base 14.

The text was added by Dan Wing, at Reinaldo's request, and  
subsequently refined to something a little more rigorous by me, at  
Dan Wing's request (since I was the designer of the NAT-PMP Epoch  
time mechanism).

>    All thresholds need to be expressed as a function of the time since
>    the last packet from the server and the acceptable clock drift  
> rates.
>    Any fixed constant cannot meet that requirement.
>
> => I disagree: a fixed threshold can catch insane cummulate drifts,  
> or clock jumps.

The definition of "insane" depends on (i) the time since the last  
packet from the server and (ii) the acceptable clock drift rates.

>    (And indeed, if the inter-packet interval is less than 8 hours, the
>    test is *already* stricter than your fixed 3600 seconds, so *also*
>    checking for 3600 seconds is a pointless waste of CPU cycles.)
>
> => I consider you forgot the smiley here...

This is a technical discussion, not amateur comedy night. You of all  
people should know that language and cultural differences mean that  
attempted jokes are not productive.

If you have a point to make, please make it directly, instead of  
hinting at it and hoping other people will manage to guess what  
you're trying to say.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From Francis.Dupont@fdupont.fr  Sat Oct 29 12:42:40 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 38A2321F869E for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 12:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id atp2-2KRKbI8 for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 12:42:39 -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 6C3C421F8696 for <pcp@ietf.org>; Sat, 29 Oct 2011 12:42:39 -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 p9TJgZR0087531; Sat, 29 Oct 2011 21:42:35 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291942.p9TJgZR0087531@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Sat, 29 Oct 2011 10:56:21 PDT. <2E1BEE18-97E6-4C15-A6BE-291502778044@apple.com> 
Date: Sat, 29 Oct 2011 21:42:35 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 29 Oct 2011 19:42:40 -0000

 In your previous mail you wrote:

   > => I found a non-cosmetic purpose with UPnP IGD IWF and even with
   > NAT-PMP IWF when the NAT-PMP client is not a code provided by Apple.
   
   Are you going to tell us, or is it a secret?
   
=> I sent to James and the list the details for NAT-PMP (even I
already explained it, but it seems repetition is required :-).

   NAT-PMP has an opcode to request the external address.
   
   The reason PCP does *not* have such an opcode is that it was agreed  
   on the list to have no useful purpose.
   
=> written yes, agreed I don't know: they are some sharing your opinion,
some sharing mine, and as usual the large majority who don't matter.

   While I've argued that PCP generally ought to be a superset of NAT- 
   PMP, this is one area where I conceded that this aspect of NAT-PMP  
   turned out to not be necessary.
   
   I'm surprised to hear you, Francis, arguing for feature parity with  
   NAT-PMP,

=> no, I don't want feature parity, I just want to make IWFs feasible.
Note here it is a matter of taste as it is enough for the IWF to
maintain a mapping.

   when the NAT-PMP authors themselves accept that an opcode to  
   request the external address was a mistake. (What does it even mean  
   for a CGN with a large pool of external addresses?)
   
=> this doesn't mean the external address should be arbitrary,
highly and per mapping. It seems than both we already had this
discussion and the current base spec required to use the same
address for all implicit and explicit dynamic mappings.
Now you can thinl it is too much or not enough.

Regards

Francis.Dupont@fdupont.fr

PS: IMHO it was a bug mistake to not put the IWF in the charter as
it is required for the early deployment.

From rpenno@juniper.net  Sat Oct 29 12:55:34 2011
Return-Path: <rpenno@juniper.net>
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 858FA21F86EE for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 12:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.569
X-Spam-Level: 
X-Spam-Status: No, score=-6.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U+N9d9floqgl for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 12:55:34 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 206C321F86DD for <pcp@ietf.org>; Sat, 29 Oct 2011 12:55:32 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP;  Sat, 29 Oct 2011 12:55:33 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sat, 29 Oct 2011 12:54:12 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Sat, 29 Oct 2011 15:54:10 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, Stuart Cheshire <cheshire@apple.com>
Date: Sat, 29 Oct 2011 15:54:09 -0400
Thread-Topic: [pcp] WG last call on draft-ietf-pcp-base-16.txt
Thread-Index: AcyWY7d5yPi7wvrLTZmju1VNDVFccAAEM41c
Message-ID: <CAD1A7F1.56C04%rpenno@juniper.net>
In-Reply-To: <201110291753.p9THrRcv080884@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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, 29 Oct 2011 19:55:34 -0000

But I believe the issue you brought up is not solved. What if the lifetime
is extended and a FIN/RST is received?

I have been back and forth with this. I believe the PCP Client sends a peer
message to extend the lifetime but has no way of knowing when the connectio=
n
will actually end. It could be 1s second from now due to user intervention
or server RST, or 1 day from now. Therefore it is just a educated guess fro=
m
the part of the client. Keeping the connection after TCP FIN/RST is receive=
d
might serve no purpose.

On the other hand is there such a case where a client/server terminates a
connection and expects the exact same session to be in the NAT after
sometime? I mean it might not even be able to get the same source port on
the host it is running so I wonder about it. If there is a strong use case
then the session/connection can remain for the lifetime independent of TCP
FIN/RST.

Thanks,

Reinaldo




On 10/29/11 10:53 AM, "Francis Dupont" <Francis.Dupont@fdupont.fr> wrote:

> BTW if you believe the PEER opcode should be limited to the query
> and lifetime extension of existing implicit dynamic mappings,
> putting creation and other dubious functions to further studies,
> I'll jump on the table to support you (:-)! (*)


From Francis.Dupont@fdupont.fr  Sat Oct 29 12:58:04 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 F18D121F886A for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 12:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZp2YUbZEd9y for <pcp@ietfa.amsl.com>; Sat, 29 Oct 2011 12:58:03 -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 3729321F8770 for <pcp@ietf.org>; Sat, 29 Oct 2011 12:58:03 -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 p9TJvv87088422; Sat, 29 Oct 2011 21:57:57 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110291957.p9TJvv87088422@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Sat, 29 Oct 2011 11:16:02 PDT. <4F967664-2782-48FF-8896-B609289ED797@apple.com> 
Date: Sat, 29 Oct 2011 21:57:57 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] base 16 review (2)
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, 29 Oct 2011 19:58:04 -0000

 In your previous mail you wrote:

   The text was added by Dan Wing, at Reinaldo's request

=> so I leave the defense of the 3600 value to Reinaldo:
I just support the idea to have a fixed threshold.
   
   > => I disagree: a fixed threshold can catch insane cummulate drifts,  
   > or clock jumps.
   
   The definition of "insane" depends on (i) the time since the last  
   packet from the server and (ii) the acceptable clock drift rates.
   
=> no, insane here refers to a fixed threshold so is not related to
(i) or (ii).

   >    (And indeed, if the inter-packet interval is less than 8 hours, the
   >    test is *already* stricter than your fixed 3600 seconds, so *also*
   >    checking for 3600 seconds is a pointless waste of CPU cycles.)
   >
   > => I consider you forgot the smiley here...
   
   This is a technical discussion, not amateur comedy night.

=> I just tried to remain calm... but I still shan't reply to
your provocation.

Regards

Francis.Dupont@fdupont.fr

PS: to make the point: I think a fixed threshold is a good idea,
I don't care about the value even the proposed 3600 value seems
right, and I consider to argue about the value until the principle
is adopted.

From Francis.Dupont@fdupont.fr  Sun Oct 30 09:08:34 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 EBE1921F8B58 for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OSglkPF1ueoQ for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:08:33 -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 0348621F8B56 for <pcp@ietf.org>; Sun, 30 Oct 2011 09:08:32 -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 p9UG8Rwm063388; Sun, 30 Oct 2011 17:08:27 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110301608.p9UG8Rwm063388@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 01:39:57 PDT. <37526BA0-6EB9-4AC4-845D-261B0D2A2300@apple.com> 
Date: Sun, 30 Oct 2011 17:08:27 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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: Sun, 30 Oct 2011 16:08:34 -0000

 In your previous mail you wrote:

   I have made some minor edits for readability, spelling, consistency,  
   ambiguity, etc. For transparency, these are attached below.
   
=> I trust you for the language improvements but there is something
which needs discussion in your proposed changes:

   @@ -855,7 +855,9 @@
             the timer expires, the timer is doubled (to 4 seconds) and  
   the request
             is re-transmitted. If no response is received before the timer
             expires, the timer is doubled again (to 8 seconds) and the  
   request is
   -        re-transmitted.</t>
   +        re-transmitted again, and so on, up to a maximum retransmission
   +        interval of fifteen minutes, at which point the PCP request is
   +        re-transmitted once every fifteen minutes until it is  
   sucessfully answered.</t>
   
             <t>Once a PCP client has successfully received a response  
   from a PCP
             server on that interface, it sends subsequent PCP requests  
   to that

=> to summary you propose to change:

   When attempting to contact a PCP server, the PCP client initializes a
   timer to 2 seconds.  The PCP client sends a PCP message to the first
   server in its list of PCP servers.  If no response is received before
   the timer expires, the timer is doubled (to 4 seconds) and the
   request is re-transmitted.  If no response is received before the
   timer expires, the timer is doubled again (to 8 seconds) and the
   request is re-transmitted.

into:

   When attempting to contact a PCP server, the PCP client initializes a
   timer to 2 seconds.  The PCP client sends a PCP message to the first
   server in its list of PCP servers.  If no response is received before
   the timer expires, the timer is doubled (to 4 seconds) and the
   request is re-transmitted.  If no response is received before the
   timer expires, the timer is doubled again (to 8 seconds) and the
   request is re-transmitted again, and so on, up to a maximum
   retransmission interval of fifteen minutes, at which point the PCP
   request is re-transmitted once every fifteen minutes until it is
   sucessfully answered.

to summary we come from a 0s, 2s, 4s, 8s then give up scheme to a
0s, 2s, 4s, 8s, 16s, 32s, 1mn04s, 2mn08s, 4mn16s, 8mn32s, 15mn,
15mn, ..., forever scheme, putting the responsability of an optional
final failure report to the application.

This is a big change and IMHO we must discuss it first to understand
if it is want we want.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sun Oct 30 09:15:17 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 1C4AB21F8B06 for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[AWL=0.048,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WriI5x+oo8Sq for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:15:16 -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 619E721F8AF1 for <pcp@ietf.org>; Sun, 30 Oct 2011 09:15:16 -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 p9UGFC97063811; Sun, 30 Oct 2011 17:15:12 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110301615.p9UGFC97063811@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 01:39:57 PDT. <37526BA0-6EB9-4AC4-845D-261B0D2A2300@apple.com> 
Date: Sun, 30 Oct 2011 17:15:12 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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: Sun, 30 Oct 2011 16:15:17 -0000

 In your previous mail you wrote:

(about the epoch checks)
   
   
   +        <t>Note: The calculations above are constructed to allow
   +        client_delta and server_delta to be computed as unsigned  
   values.</t>
   +

=> if we add this (and I think it is a good idea) we have to add first
a requirement about the client clock which must not go backward
(and in this case IMHO one should directly consider the epoch as
invalid).

Thanks

Francis.Dupont@fdupont.fr

PS: I propose to add it in the condition in:

      *  If the current PCP server Epoch time value
         (current_server_time) is less than the previously received PCP
         server Epoch time value (previous_server_time) then the client
         treats the Epoch time value as obviously invalid (time should
         not go backwards), else

From Francis.Dupont@fdupont.fr  Sun Oct 30 09:26:08 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 06F6C21F8A62 for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[AWL=0.048,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qZH+dlSCclCU for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:26:07 -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 4F9DC21F87D6 for <pcp@ietf.org>; Sun, 30 Oct 2011 09:26:07 -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 p9UGQ3lR064449; Sun, 30 Oct 2011 17:26:03 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110301626.p9UGQ3lR064449@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 01:39:57 PDT. <37526BA0-6EB9-4AC4-845D-261B0D2A2300@apple.com> 
Date: Sun, 30 Oct 2011 17:26:03 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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: Sun, 30 Oct 2011 16:26:08 -0000

 In your previous mail you wrote:

   @@ -1964,8 +1966,9 @@
             receives a PCP response for the MAP Opcode.</t>
   
             <t>After performing common PCP response processing, the  
   response is
   -        further matched with an outstanding request by comparing the  
   protocol,
   -        internal IP address, and internal port. Other fields are not  
   compared,
   +        further matched with an outstanding request by comparing the  
   Protocol
   +        and Internal Port (and, if THIRD_PARTY, Internal IP Address).
   +        Other fields are not compared,
             because the PCP server sets those fields.</t>
   
=> I disagree: the Internal Address should be compared in all cases,
i.e., I am in favor to keep the original wording which is simpler.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sun Oct 30 09:39: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 5421F21F8B34 for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:39:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YTNFxCsf4JiY for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:39: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 8F06021F8B32 for <pcp@ietf.org>; Sun, 30 Oct 2011 09:39:18 -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 p9UGdEbT065215; Sun, 30 Oct 2011 17:39:14 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110301639.p9UGdEbT065215@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 01:39:57 PDT. <37526BA0-6EB9-4AC4-845D-261B0D2A2300@apple.com> 
Date: Sun, 30 Oct 2011 17:39:14 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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: Sun, 30 Oct 2011 16:39:19 -0000

 In your previous mail you wrote:

   @@ -2022,8 +2024,13 @@
             that already exists as a static mapping, the PCP server will
             return a successful result, confirming that the requested
             mapping exists. The lifetime the PCP server returns for such a
   -        static mapping SHOULD be 4294967295 (0xFFFFFFFF).  There is no
   -        need for a PCP client to renew a static mapping.</t>
   +        static mapping SHOULD be 4294967295 (0xFFFFFFFF). Upon  
   receipt of
   +        such a MAP response with an absurdly long Assigned Lifetime the
   +        PCP client SHOULD behave as if it received a more sane value
   +        (e.g., 24 hours), and renew the mapping accordingly, to ensure
   +        that if the static mapping is removed the client will continue
   +        to maintain the mapping it desires.
   +        </t>
   
=> I strongly oppose to this change: we don't know what the user
wants, a priori (s)he should never ask for an explicit dynamic mapping
when a static mapping already exists first... So the right thing is to
return an easy to recognize condition with the infos, this is what is
specified here, and what to do next must be left to the user (i.e.,
(s)he can do what you suggest or something very different, anyway
you could not solve by a program a condition which requires a manual
action).

Regards

Francis.Dupont@fdupont.fr

PS: there are at least two other ways to handle the condition which
are IMHO more likely than the one you want to recommend:
 - delete the static mapping and retry with PCP
 - give up on PCP as the mapping is already installed

From Francis.Dupont@fdupont.fr  Sun Oct 30 09:41:45 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 6F07021F8B32 for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u4L0DfuKkNrN for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:41:45 -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 AAA1F21F8B21 for <pcp@ietf.org>; Sun, 30 Oct 2011 09:41:44 -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 p9UGffJb065748; Sun, 30 Oct 2011 17:41:41 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110301641.p9UGffJb065748@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 01:39:57 PDT. <37526BA0-6EB9-4AC4-845D-261B0D2A2300@apple.com> 
Date: Sun, 30 Oct 2011 17:41:41 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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: Sun, 30 Oct 2011 16:41:45 -0000

 In your previous mail you wrote:

   @@ -2455,7 +2462,7 @@
   
             <t>After performing common PCP response processing, the  
   response is
             further matched with a request by comparing the protocol,  
   internal IP
   -        address, internal port, remote peer address and remote peer  
   port.
   +        address (if THIRD_PARTY), internal port, remote peer address  
   and remote peer port.
             Other fields are not compared, because the PCP server  
   changes those
             fields to provide information about the mapping created by the
             Opcode.</t>

=> for the same reason than in the MAP case IMHO we must keep
the original and simpler wording.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sun Oct 30 09:52:03 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 6323921F8B19 for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLYFBNvGUQUr for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:52:02 -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 9445D21F8B17 for <pcp@ietf.org>; Sun, 30 Oct 2011 09:52:01 -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 p9UGpwCf066365; Sun, 30 Oct 2011 17:51:58 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110301651.p9UGpwCf066365@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 01:39:57 PDT. <37526BA0-6EB9-4AC4-845D-261B0D2A2300@apple.com> 
Date: Sun, 30 Oct 2011 17:51:58 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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: Sun, 30 Oct 2011 16:52:03 -0000

 In your previous mail you wrote:

               <t>A PCP client refreshes a mapping by sending a new PCP  
   request
               containing information from the earlier PCP response. The  
   PCP server
               will respond indicating the new lifetime. It is possible,  
   due to
               reconfiguration or failure of the PCP server, that the  
   public IP
               address and/or public port, or the PCP server itself, has  
   changed
   -          (due to a new route to a different PCP server). To detect  
   such
   -          events more quickly, the PCP client may find it beneficial  
   to use
   -          shorter lifetimes (so that it communicates with the PCP  
   server more
   -          often). If the PCP client has several mappings, the Epoch
   +          (due to a new route to a different PCP server). Such  
   events are
   +          not an error. The PCP server will simply return a new  
   External
   +          Address and/or External Port to the client, and the client  
   should
   +          record this new External Address and Port with its  
   rendezvous service.
   +          To detect such events more quickly, the PCP client may  
   find it
   +          beneficial to use shorter lifetimes (so that it communicates
   +          with the PCP server more often).</t>

=> I disagree about 'is not an error' because it depends on the
service users expect. To avoid another long and sterile discussion I
suggest to only soften the wording, for instance 'not always an error'
or 'not a priori an error', etc.

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sun Oct 30 09:55:21 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 716E821F8B33 for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVoNf6t4AfFe for <pcp@ietfa.amsl.com>; Sun, 30 Oct 2011 09:55:21 -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 B670721F8B19 for <pcp@ietf.org>; Sun, 30 Oct 2011 09:55:20 -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 p9UGtHcA066613; Sun, 30 Oct 2011 17:55:17 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110301655.p9UGtHcA066613@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Stuart Cheshire <cheshire@apple.com>
In-reply-to: Your message of Fri, 28 Oct 2011 01:39:57 PDT. <37526BA0-6EB9-4AC4-845D-261B0D2A2300@apple.com> 
Date: Sun, 30 Oct 2011 17:55:17 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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: Sun, 30 Oct 2011 16:55:21 -0000

 In your previous mail you wrote:

   @@ -3119,15 +3133,15 @@
   
     <t>Because an SCTP-aware NAT does not rewrite SCTP port numbers (and
     firewalls never do), a PCP MAP or PEER request for an SCTP mapping
   -SHOULD provide the same Internal Port and Requested External Port.  If
   -the PCP server supports SCTP, and the requested external port cannot
   +SHOULD provide the same Internal Port and Suggested External Port.  If
   +the PCP server supports SCTP, and the suggested external port cannot
     be provided in an explicit dynamic SCTP mapping, then the error
     CANNOT_PROVIDE_EXTERNAL is returned.</t>
     </section>
           </section>
   
=> I have a problem here as on one side the names of the fields
are *Suggested* External Address and Port, on the other side
they are not suggested but really *Requested* because of the
implicit PREFER_FAILURE semantics...

Regards

Francis.Dupont@fdupont.fr

From mohta@necom830.hpcl.titech.ac.jp  Mon Oct 31 02:06:49 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 0D5D621F8CD4 for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 02:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.032
X-Spam-Level: 
X-Spam-Status: No, score=-0.032 tagged_above=-999 required=5 tests=[AWL=0.058,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jNS+bXpLVwN2 for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 02:06:48 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id E79EA21F87D9 for <pcp@ietf.org>; Mon, 31 Oct 2011 02:06:47 -0700 (PDT)
Received: (qmail 7063 invoked from network); 31 Oct 2011 09:29:36 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 31 Oct 2011 09:29:36 -0000
Message-ID: <4EAE6540.7040104@necom830.hpcl.titech.ac.jp>
Date: Mon, 31 Oct 2011 18:07:12 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: pcp@ietf.org
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: [pcp] Using dynamically assigned port numbers with static URLs
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, 31 Oct 2011 09:06:49 -0000

Hi,

Are there anyone who are interested in application aspect
of port control, here?

That is, if a server is dynamically assigned a global port
number through PCP, it should somehow be publicly advertised
to make the server reachable from the rest of the world.

But, it is not possible to modify old port numbers encoded
in URLs of clients' bookmarks.

Thus, it is necessary to have a mechanism to map a static
URLs to dynamically assigned IP addresses and port numbers.

Dynamic update on DNS address records can change IP addresses
of URLs but there is no well defined way to do so with port
numbers.

So, I wrote an ID "Using DNS SRV RRs with URLs":

	http://tools.ietf.org/html/draft-ohta-urlsrv-00.txt

Comments, which may be directed to dnsext list, are welcome.

					Masataka Ohta

From moore@network-heretics.com  Mon Oct 31 05:09:26 2011
Return-Path: <moore@network-heretics.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 09BCB21F84DC for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 05:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O5bhQDMdjhDx for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 05:09:25 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 2B07D21F84A4 for <pcp@ietf.org>; Mon, 31 Oct 2011 05:09:25 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 55F95204AD; Mon, 31 Oct 2011 08:09:24 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 31 Oct 2011 08:09:24 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=KLQuAbveYpHcYbg8jHlJpOMG7BE=; b=LT ZesBDi7hAyhXBbHSPBE3Yb6FTA0darjLaDo/gcKOZh3v8tqQQ2MBfx9fODKlj6gt AkUO2HWGY9LEMg72z/GzG2G74iWLbKbJUXHS1VXM34xwqMg2ivKszmhAtK1dArER 3ULMMBDcNV13cSVu90tkK8ufcqeg+Fbk2zn3a69f4=
X-Sasl-enc: Kyphw1+fp4JC2npvmntXOGhF7KFY8sftJoaAONYQrggP 1320062964
Received: from [10.59.1.8] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id E801E8E0FDD; Mon, 31 Oct 2011 08:09:23 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4EAE6540.7040104@necom830.hpcl.titech.ac.jp>
Date: Mon, 31 Oct 2011 08:09:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0BD7102-8E0D-4B4D-9B8C-90E578E6F49A@network-heretics.com>
References: <4EAE6540.7040104@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.1084)
Cc: pcp@ietf.org
Subject: Re: [pcp] Using dynamically assigned port numbers with static URLs
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, 31 Oct 2011 12:09:26 -0000

I think this is a Very Bad Idea.

IPv4 is at EOL.  Port mapping NATs should also be considered at EOL.  I =
understand that the motivation for creating PCP was LSNs and the loss of =
UPnP/NAT-PMP capability, but PCP is useful even without port-mapping =
NATs.  We should not be destroying a valuable capability to explicitly =
specify port numbers and have those literal port numbers mean what they =
say, just because of LSNs.

Keith

On Oct 31, 2011, at 5:07 AM, Masataka Ohta wrote:

> Hi,
>=20
> Are there anyone who are interested in application aspect
> of port control, here?
>=20
> That is, if a server is dynamically assigned a global port
> number through PCP, it should somehow be publicly advertised
> to make the server reachable from the rest of the world.
>=20
> But, it is not possible to modify old port numbers encoded
> in URLs of clients' bookmarks.
>=20
> Thus, it is necessary to have a mechanism to map a static
> URLs to dynamically assigned IP addresses and port numbers.
>=20
> Dynamic update on DNS address records can change IP addresses
> of URLs but there is no well defined way to do so with port
> numbers.
>=20
> So, I wrote an ID "Using DNS SRV RRs with URLs":
>=20
> 	http://tools.ietf.org/html/draft-ohta-urlsrv-00.txt
>=20
> Comments, which may be directed to dnsext list, are welcome.
>=20
> 					Masataka Ohta
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From Francis.Dupont@fdupont.fr  Mon Oct 31 05:10:14 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 54E4821F858D for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 05:10:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.254
X-Spam-Level: 
X-Spam-Status: No, score=-2.254 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, J_CHICKENPOX_44=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jnEgPWFYO7hT for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 05:10:13 -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 AFDF621F8532 for <pcp@ietf.org>; Mon, 31 Oct 2011 05:09:59 -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 p9VC9DEm037623; Mon, 31 Oct 2011 13:09:35 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110311209.p9VC9DEm037623@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-reply-to: Your message of Mon, 31 Oct 2011 18:07:12 +0900. <4EAE6540.7040104@necom830.hpcl.titech.ac.jp> 
Date: Mon, 31 Oct 2011 13:09:13 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] Using dynamically assigned port numbers with static URLs
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, 31 Oct 2011 12:10:14 -0000

 In your previous mail you wrote:

   Are there anyone who are interested in application aspect
   of port control, here?
   
=> there is some indications in the base draft, even only
in non-normative sections (this is out of scope of the PCP WG)
and more DNS SD than SRV oriented.

   Dynamic update on DNS address records can change IP addresses
   of URLs but there is no well defined way to do so with port
   numbers.
   
=> SRV and DNS SD...

   So, I wrote an ID "Using DNS SRV RRs with URLs":
   
   	http://tools.ietf.org/html/draft-ohta-urlsrv-00.txt
   
   Comments, which may be directed to dnsext list, are welcome.
   
=> IMHO it is more dnsop than dnsext as you propose a clever
use of SRV RRs, not a new protocol/RR/etc.

I have a concern about using (dynamic) DNS is this context:
DNS answers are cached, in fact even with TTL=0 by most applications,
so it doesn't survive a CGN address or port renumbering from a reboot.

Note this is not an issue for the now traditional DHCP+DDNS used
for nomadism because in that context the nomad server releases/
deregisters before being shutdowned and no longer available for
a delay greater than the DNS lifetime, i.e., in the rare cases
a nomad computer provides a service this can be done in a
secure way. This is not the case for a server behind a CGN
which doesn't enforce mapping stability using for instance
stable storage.

Regards

Francis.Dupont@fdupont.fr

From jhw@apple.com  Mon Oct 31 10:04:52 2011
Return-Path: <jhw@apple.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 E6E5A11E815A for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 10:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.565
X-Spam-Level: 
X-Spam-Status: No, score=-106.565 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JsttoPMqW2sQ for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 10:04:51 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB9B11E810C for <pcp@ietf.org>; Mon, 31 Oct 2011 10:04:47 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_H7BAxkYF+KG2mbaquV8LRw)"
Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LTX00I5WWR4IW91@mail-out.apple.com> for pcp@ietf.org; Mon, 31 Oct 2011 10:04:46 -0700 (PDT)
X-AuditID: 11807130-b7c1bae000001553-1a-4eaed52d8633
Received: from ba0301a-dhcp89.apple.com (ba0301a-dhcp89.apple.com [17.193.14.217]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay11.apple.com (Apple SCV relay) with SMTP id 59.CB.05459.E25DEAE4; Mon, 31 Oct 2011 10:04:46 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <201110301655.p9UGtHcA066613@givry.fdupont.fr>
Date: Mon, 31 Oct 2011 10:04:46 -0700
Message-id: <4097E530-3AB1-4E71-BF1A-1B4A1FF61EE9@apple.com>
References: <201110301655.p9UGtHcA066613@givry.fdupont.fr>
To: PCP <pcp@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJLMWRmVeSWpSXmKPExsUieJDvpq7e1XV+BqtvMVk8mraT1WLysd+s Dkwe76b+YfVYsuQnUwBTFJdNSmpOZllqkb5dAlfGx1vtbAUz1Cr2X/rH1MDYo9jFyMkhIWAi 8fTXGmYIW0ziwr31bF2MXBxCAiuYJBZNXwSU4OAQFrCVeDLDCKSGV8BYYs2tdywgNrNAgkTL h1mMIDabgIrEt8t3mUBsTgFriedfnoHZLAKqEts3zWcCGcMsoCdx/5QuxBgbiWfHLoG1CglY Sdxe8YgdxBYBOmH144dMEOfIS7R8vcM2gZFvFpLNs5BshrC1JZYtfM08C2yDjsTkhWjCEPbH 80eYFjCyrWIULErNSaw0NNRLLCjISdVLzs/dxAgK0IZCgx2Ma3/yH2IU4GBU4uENPLjOT4g1 say4MvcQowQHs5IIr/8yoBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFeO/7VfkIC6YklqdmpqQWp RTBZJg5OqQZGLedwi9Of756dYfbnWpx92cLVWvXe5vNMJ9Te03ZaztkV3HZd3+nvi/Jj535v CW2/+Occu82Dub65N5ynmjjd4p/QXfWt89TyUO+ELhahiPvqhzUCywviWQNVVjO82Lm/NTzw fqXrl2BdJXnvq/PkJS2W7jsVubSv9ONB9X/Oz7a4/LFxaExUYinOSDTUYi4qTgQA51O+kEwC	AAA=
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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: Mon, 31 Oct 2011 17:04:52 -0000

--Boundary_(ID_H7BAxkYF+KG2mbaquV8LRw)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

On Oct 30, 2011, at 9:55 AM, Francis Dupont wrote:
> 
> I have a problem here as on one side the names of the fields are *Suggested* External Address and Port, on the other side they are not suggested but really *Requested* because of the implicit PREFER_FAILURE semantics...


You're right.  Every standard transport protocol that uses 16-bit port numbers, with the singular exception of SCTP, admits network address-port translation that floats the port number.  SCTP is unique among standard transports in that it was designed with a mechanism, i.e. the verification tag, to facilitate address amplification by network address translators without requiring the port number to float.

So, yes... the implicit PREFER_FAILURE sematics also imply that, in the special case of SCTP, the fields are sematically equivalent to Internal/External Port and Suggested External Address.  That said, I fail to see how leaving this implication for the reader to infer could lead to an ambiguous interpretation of the base specification.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




--Boundary_(ID_H7BAxkYF+KG2mbaquV8LRw)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Oct 30, 2011, at 9:55 AM, Francis Dupont =
wrote:</div><div><blockquote =
type=3D"cite"><br></blockquote></div><blockquote type=3D"cite">I have a =
problem here as on one side the names of the fields&nbsp;are *Suggested* =
External Address and Port, on the other side&nbsp;they are not suggested =
but really *Requested* because of the&nbsp;implicit PREFER_FAILURE =
semantics...</blockquote></div><div><br></div><div>You're right. =
&nbsp;Every standard transport protocol that uses 16-bit port numbers, =
with the singular exception of SCTP, admits network address-port =
translation that floats the port number. &nbsp;SCTP is unique among =
standard transports in that it was designed with a mechanism, i.e. the =
verification tag, to facilitate address amplification by network address =
translators without requiring the port number to =
float.</div><div><br></div><div>So, yes... the implicit PREFER_FAILURE =
sematics also imply that, in the special case of SCTP, the fields are =
sematically equivalent to Internal/External Port and Suggested External =
Address. &nbsp;That said, I fail to see how leaving this implication for =
the reader to infer could lead to an ambiguous interpretation of the =
base specification.</div><br><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Gill Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
12px; "><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><br =
class=3D"Apple-interchange-newline">--</span></span></div><div =
style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">james woodyatt &lt;<a =
href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&gt;</span></span></span></=
div><div style=3D"font-size: 11px; font-family: Geneva; "><span =
class=3D"Apple-style-span" style=3D"font-family: Geneva; font-size: =
11px; "><span class=3D"Apple-style-span" style=3D"font-family: Geneva; =
font-size: 11px; "><span class=3D"Apple-style-span" style=3D"font-family: =
Geneva; font-size: 11px; ">member of technical staff, core os =
networking</span></span></span></div><br =
class=3D"Apple-interchange-newline" style=3D"font-size: 11px; =
font-family: Geneva; "></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Boundary_(ID_H7BAxkYF+KG2mbaquV8LRw)--

From dthaler@microsoft.com  Mon Oct 31 10:09:16 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 E29E211E8185 for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 10:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.608
X-Spam-Level: 
X-Spam-Status: No, score=-110.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vkFd1saYNBjF for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 10:09:15 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id F292821F8B14 for <pcp@ietf.org>; Mon, 31 Oct 2011 10:09:14 -0700 (PDT)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 31 Oct 2011 10:09:14 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) with Microsoft SMTP Server (TLS) id 14.1.339.2; Mon, 31 Oct 2011 10:09:14 -0700
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.162]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.01.0355.003; Mon, 31 Oct 2011 10:09:14 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, Stuart Cheshire <cheshire@apple.com>
Thread-Topic: [pcp] WG last call on draft-ietf-pcp-base-16.txt
Thread-Index: AQHMlx4oQmCaw3A9Lku96UuEkELPBpWWsO6Q
Date: Mon, 31 Oct 2011 17:09:13 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B2D5A1B@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: Your message of Fri, 28 Oct 2011 01:39:57 PDT. <37526BA0-6EB9-4AC4-845D-261B0D2A2300@apple.com> <201110301608.p9UG8Rwm063388@givry.fdupont.fr>
In-Reply-To: <201110301608.p9UG8Rwm063388@givry.fdupont.fr>
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.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: Mon, 31 Oct 2011 17:09:16 -0000

Francis Dupont wrote (responding to Stuart):
> =3D> I trust you for the language improvements but there is something whi=
ch
> needs discussion in your proposed changes:
>=20
>    @@ -855,7 +855,9 @@
>              the timer expires, the timer is doubled (to 4 seconds) and
>    the request
>              is re-transmitted. If no response is received before the tim=
er
>              expires, the timer is doubled again (to 8 seconds) and the
>    request is
>    -        re-transmitted.</t>
>    +        re-transmitted again, and so on, up to a maximum retransmissi=
on
>    +        interval of fifteen minutes, at which point the PCP request i=
s
>    +        re-transmitted once every fifteen minutes until it is
>    sucessfully answered.</t>
>=20
>              <t>Once a PCP client has successfully received a response
>    from a PCP
>              server on that interface, it sends subsequent PCP requests
>    to that
>=20
> =3D> to summary you propose to change:
>=20
>    When attempting to contact a PCP server, the PCP client initializes a
>    timer to 2 seconds.  The PCP client sends a PCP message to the first
>    server in its list of PCP servers.  If no response is received before
>    the timer expires, the timer is doubled (to 4 seconds) and the
>    request is re-transmitted.  If no response is received before the
>    timer expires, the timer is doubled again (to 8 seconds) and the
>    request is re-transmitted.
>=20
> into:
>=20
>    When attempting to contact a PCP server, the PCP client initializes a
>    timer to 2 seconds.  The PCP client sends a PCP message to the first
>    server in its list of PCP servers.  If no response is received before
>    the timer expires, the timer is doubled (to 4 seconds) and the
>    request is re-transmitted.  If no response is received before the
>    timer expires, the timer is doubled again (to 8 seconds) and the
>    request is re-transmitted again, and so on, up to a maximum
>    retransmission interval of fifteen minutes, at which point the PCP
>    request is re-transmitted once every fifteen minutes until it is
>    sucessfully answered.
>=20
> to summary we come from a 0s, 2s, 4s, 8s then give up scheme to a 0s, 2s,=
 4s,
> 8s, 16s, 32s, 1mn04s, 2mn08s, 4mn16s, 8mn32s, 15mn, 15mn, ..., forever
> scheme, putting the responsability of an optional final failure report to=
 the
> application.
>=20
> This is a big change and IMHO we must discuss it first to understand if i=
t is want
> we want.

I agree with Stuart's proposed change (the main point of which is to keep
retrying rather than give up).

-Dave

From dthaler@microsoft.com  Mon Oct 31 11:02:01 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 14C961F0CA0 for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 11:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.607
X-Spam-Level: 
X-Spam-Status: No, score=-110.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kx9osoZ+4PGQ for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 11:02:00 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id 8D28A1F0C9F for <pcp@ietf.org>; Mon, 31 Oct 2011 11:02:00 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 31 Oct 2011 11:02:00 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.1.339.2; Mon, 31 Oct 2011 11:01:59 -0700
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.162]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi id 14.01.0355.003; Mon, 31 Oct 2011 11:00:21 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: Comments on draft-cheshire-pcp-recovery-02 
Thread-Index: AcyX9nHXPr0Qiwe0RSezfZPVlcreWA==
Date: Mon, 31 Oct 2011 18:00:20 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B2D5DC9@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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [pcp] Comments on draft-cheshire-pcp-recovery-02
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, 31 Oct 2011 18:02:01 -0000

Two comments:

1) This draft uses port 5350 rather than the existing PCP port 5351.
It contains no justification that I saw as to why it cannot use the same po=
rt number.
Port space is scarce, so this should either justify why it needs two, or el=
se
(my preference) use the same port number as PCP.

2) It says "MUST inform PCP clients of this fact by
multicasting the UDP packet shown below on all multicast-capable
interfaces".   The implication is that it must do so even if it has some wa=
y to
know (e.g. a CGN being manually configured with that topological knowledge)
that there are no PCP clients on that interface, which results in extra ove=
rhead.
I wanted to point this out in case anyone felt this is an issue and there i=
s some
reason to change to a SHOULD.   I'm personally fine either way.

-Dave

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of RJ
> Atkinson
> Sent: Friday, October 28, 2011 3:01 AM
> To: pcp@ietf.org
> Subject: Re: [pcp] WG last call on draft-ietf-pcp-base-16.txt
>=20
>=20
> On 26  Oct 2011, at 00:44 , Paul Selkirk wrote:
> > OTOH, a) if we define it for IPv4 multicast, someone will surely and
> > immediately request it for IPv6 multicast;
>=20
> As you predicted, in this morning's email, Keith Moore expressed interest=
 in
> IPv6.
>=20
> However, Stuart released draft-cheshire-pcp-recovery-02 overnight.
> The revised I-D text is IP version agnostic, including language about lin=
k-local
> all-nodes multicast for both IPv4 and IPv6.
>=20
> So the concern quoted at top is resolved at this point.
>=20
> If other specific issues/concerns exist with draft-cheshire-pcp-recovery,=
 please
> make those issues/concerns known to the whole PCP WG list, ideally with s=
ome
> concrete suggestions on how to resolve any issues/concerns.
>=20
> Yours,
>=20
> Ran
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From internet-drafts@ietf.org  Mon Oct 31 16:59:48 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 4AFA811E816A; Mon, 31 Oct 2011 16:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVtfjwME8Iub; Mon, 31 Oct 2011 16:59:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FBC011E8100; Mon, 31 Oct 2011 16:59:47 -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.62
Message-ID: <20111031235947.15816.95227.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2011 16:59:47 -0700
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-base-17.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: Mon, 31 Oct 2011 23:59:48 -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-17.txt
	Pages           : 84
	Date            : 2011-10-31

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


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pcp-base-17.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-17.txt

From cheshire@apple.com  Mon Oct 31 18:13:20 2011
Return-Path: <cheshire@apple.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 EE1341F0C48 for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 18:13:20 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VFj6pSx8G1TW for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 18:13:20 -0700 (PDT)
Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 49E641F0C42 for <pcp@ietf.org>; Mon, 31 Oct 2011 18:13:20 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LTY00A73JBSX8N2@mail-out.apple.com> for pcp@ietf.org; Mon, 31 Oct 2011 18:12:26 -0700 (PDT)
X-AuditID: 11807130-b7c1bae000001553-9f-4eaf477aa311
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay11.apple.com (Apple SCV relay) with SMTP id 73.91.05459.A774FAE4; Mon, 31 Oct 2011 18:12:26 -0700 (PDT)
Received: from [10.0.1.201] ([173.164.252.149]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LTY00BZLJCQZH60@koseret.apple.com> for pcp@ietf.org; Mon, 31 Oct 2011 18:12:26 -0700 (PDT)
Message-id: <8A86BEC0-6BE0-4563-8D89-533D370897C9@apple.com>
To: pcp@ietf.org
From: Stuart Cheshire <cheshire@apple.com>
Date: Mon, 31 Oct 2011 18:12:25 -0700
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkluLIzCtJLcpLzFFi42IRnG6nrlvlvt7PYPcSHYvJx36zOjB6LFny kymAMYrLJiU1J7MstUjfLoErY9XON+wFu0Uqnpy6yd7AuIW/i5GTQ0LAROLGtvmsELaYxIV7 69m6GLk4hAQ6mSTWTOhlA0nwCghK/Jh8j6WLkYODWUBe4uB5WZAws4CLxNYJLewQ9f1MEqfW 3WSEqLeROPvtPDuILSIgIPF79WUmEJtNQEvixecrYDOFgeZsmvwSbDGLgKrEo1WNjBBHyEkc Pv2KcQIj7ywkq2chrJ6FZPUCRuZVjIJFqTmJlYaGeokFBTmpesn5uZsYQQHTUGiwg3HtT/5D jAIcjEo8vIEH1/kJsSaWFVfmHmKU4GBWEuH1XwYU4k1JrKxKLcqPLyrNSS0+xCjNwaIkztv7 FiglkJ5YkpqdmlqQWgSTZeLglGpgXLJ1hkjmh9zi5U/lNm9qyDCqstopuTt9/+Frn6ZlMXNd Fbmbu85te7t5NtN9ZyvWW6vF0o19cidu+F9hkaFhuv7M7Yu6S27FuJvcjvlwrGnt2Y7q7n1Z 9d6FTyd5L3peK3Wq4sra1g9rmDpMZy9ztZ0llMK4cWeLZJYwu6aa3s/rfFfM3DJdlViKMxIN tZiLihMBN72oqBQCAAA=
Subject: [pcp] draft-ietf-pcp-base-17
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, 01 Nov 2011 01:13:21 -0000

I just submitted draft-ietf-pcp-base-17.

This incorporates the changes from the one-week Working Group Last Call.

I only just got it in by 5pm, and a couple of minor changes,  
described below, didn't make it. These are checked in to the  
Subversion repository but did not make it into the draft-ietf-pcp- 
base-17 submission.

The changes cued up for draft-ietf-pcp-base-18 are:

1. Clarification requested by Francis Dupont:

> 7.3.  General PCP Client: Processing a Response
>
>    The PCP client receives the response and verifies that the  
> source IP
>    address and port belong to the PCP server of an outstanding PCP
>    request.  If not, the response is silently dropped.
>
>    If the received PCP response message is less than four octets  
> long it
>    is silently dropped.
>
>    If the R bit is clear the message is silently dropped.
>
>    If the error code is UNSUPP_VERSION processing continues as  
> described
>    in Section 7.7
>
>    ...

2. Dave Thaler asked for an explanation of why Rapid Recovery uses  
port 5350:

>    Note: The reason that server-to-client restart announcements use a
>    port (5350) that's different from the client-to-server request port
>    (5351) is for pragmatic implementation reasons.  A single device  
> may
>    have multiple roles.  A multi-function home gateway may also  
> provide
>    printer sharing.  A home computer may also provide "Internet  
> Sharing"
>    (NAT) functionality.  Such devices need to act as both a PCP Server
>    and a PCP Client at the same time, and the software that implements
>    the PCP Server on the device may not be the same software component
>    that implements the PCP Client.
>
>    o  The software that implements the PCP Server needs to listen for
>       unicast client requests.
>
>    o  The software that implements the PCP Client needs to listen for
>       multicast Rapid Recovery restart announcements.
>
>    In most networking APIs is is difficult or impossible to have two
>    independent clients listening for both unicasts and multicasts  
> on the
>    same port at the same time.  For this reason it makes sense to  
> have:
>
>    o  A single PCP Server listening for unicast client requests on  
> port
>       5351, and
>
>    o  Zero, one, or more independent PCP Clients listening (using
>       SO_REUSEPORT or equivalent) for multicast restart  
> announcements on
>       port 5350.

That is all for now.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From rpenno@juniper.net  Mon Oct 31 18:20:46 2011
Return-Path: <rpenno@juniper.net>
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 3ED991F0C40 for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 18:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.57
X-Spam-Level: 
X-Spam-Status: No, score=-6.57 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-B+-PZJlIc9 for <pcp@ietfa.amsl.com>; Mon, 31 Oct 2011 18:20:43 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 9B0101F0C52 for <pcp@ietf.org>; Mon, 31 Oct 2011 18:20:41 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP;  Mon, 31 Oct 2011 18:20:42 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 31 Oct 2011 18:17:13 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Mon, 31 Oct 2011 21:17:10 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Dave Thaler <dthaler@microsoft.com>, "pcp@ietf.org" <pcp@ietf.org>
Date: Mon, 31 Oct 2011 21:17:08 -0400
Thread-Topic: [pcp] Comments on draft-cheshire-pcp-recovery-02
Thread-Index: AcyX9nHXPr0Qiwe0RSezfZPVlcreWAAPYdx0
Message-ID: <CAD496A4.56EC5%rpenno@juniper.net>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF653B2D5DC9@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] Comments on draft-cheshire-pcp-recovery-02
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, 01 Nov 2011 01:20:46 -0000

You are not alone. I support a 'qualified' SHOULD.

I pointed out in the thread that one of the requirements for recovery
multicast working efficiently was that PCP Server and BNG/Edge router/NAT
needed to be the same device so it knows through which interfaces to
multicast the recovery packet.

" Well, multicast recovery is applicable if several conditions are met:

....

4 - Finally, PCP Server (which sends the multicast packet), NAT (controlled
    device) and BNG/GGSN (which knows the interface to send multicast
    packet) should ideally be the same device which might be the case or
    not."

In the worst (but simpler) case firewall/NAT router would send packet on al=
l
(possibly thousands of interfaces). Still works but it will trigger an
avalanche of renewal that the PCP Server will need to handle. Apart from
that, text is okay.

Thanks,

Reinaldo

On 10/31/11 11:00 AM, "Dave Thaler" <dthaler@microsoft.com> wrote:

> 2) It says "MUST inform PCP clients of this fact by
> multicasting the UDP packet shown below on all multicast-capable
> interfaces".   The implication is that it must do so even if it has some =
way
> to
> know (e.g. a CGN being manually configured with that topological knowledg=
e)
> that there are no PCP clients on that interface, which results in extra
> overhead.
> I wanted to point this out in case anyone felt this is an issue and there=
 is
> some
> reason to change to a SHOULD.   I'm personally fine either way.

