Re: [pcp] I-D Action: draft-ietf-pcp-proxy-04.txt

<mohamed.boucadair@orange.com> Mon, 29 July 2013 06:25 UTC

Return-Path: <mohamed.boucadair@orange.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 BD4D221F99AE for <pcp@ietfa.amsl.com>; Sun, 28 Jul 2013 23:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=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 jTfA+voPIXy3 for <pcp@ietfa.amsl.com>; Sun, 28 Jul 2013 23:25:22 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 69E2721F96D9 for <pcp@ietf.org>; Sun, 28 Jul 2013 23:25:22 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 6FC1122E943 for <pcp@ietf.org>; Mon, 29 Jul 2013 08:25:20 +0200 (CEST)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 59732238055 for <pcp@ietf.org>; Mon, 29 Jul 2013 08:25:20 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Mon, 29 Jul 2013 08:25:20 +0200
From: mohamed.boucadair@orange.com
To: "pcp@ietf.org" <pcp@ietf.org>
Date: Mon, 29 Jul 2013 08:25:17 +0200
Thread-Topic: [pcp] I-D Action: draft-ietf-pcp-proxy-04.txt
Thread-Index: Ac6MIpfT/OWbBnPDQNKkaAVbKuqd7AAAUYJg
Message-ID: <94C682931C08B048B7A8645303FDC9F36EE6E83440@PUEXCB1B.nanterre.francetelecom.fr>
References: <20130729061206.24586.72780.idtracker@ietfa.amsl.com>
In-Reply-To: <20130729061206.24586.72780.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.29.54526
Subject: Re: [pcp] I-D Action: draft-ietf-pcp-proxy-04.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, 29 Jul 2013 06:25:26 -0000

Dear all,

The main changes in the new version are:

* Add explicit text about configuring which interface(s) the PCP Proxy will act on as a PCP Server
* Explicit the PCP error code to be returned
* Explicit the ICMP error code to be returned when an error on the UDP socket is experienced
* The PCP Proxy is now in charge to enforce the message size limit instead of relaying the message to the ultimate server
* If the PCP Proxy processing (e.g., adding a THIRD_PARTY Option) makes a request that exceeds 1100 octets, a MALFORMED_REQUEST response is sent to the PCP client
* Update the security considerations section with some text about THIRD_PARTY

To check the detailed modifs, a diff is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-proxy-04 

Cheers,
Med


>-----Message d'origine-----
>De : pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] De la part de
>internet-drafts@ietf.org
>Envoyé : lundi 29 juillet 2013 08:12
>À : i-d-announce@ietf.org
>Cc : pcp@ietf.org
>Objet : [pcp] I-D Action: draft-ietf-pcp-proxy-04.txt
>
>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
> This draft is a work item of the Port Control Protocol Working Group of
>the IETF.
>
>	Title           : Port Control Protocol (PCP) Proxy Function
>	Author(s)       : Mohamed Boucadair
>                          Reinaldo Penno
>                          Dan Wing
>	Filename        : draft-ietf-pcp-proxy-04.txt
>	Pages           : 11
>	Date            : 2013-07-28
>
>Abstract:
>   This document specifies a new PCP functional element denoted as a PCP
>   Proxy.  The PCP Proxy relays PCP requests received from PCP clients
>   to upstream PCP server(s).  A typical deployment usage of this
>   function is to help establish successful PCP communications for PCP
>   clients that can not be configured with the address of a PCP server
>   located more than one hop away.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-pcp-proxy
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-pcp-proxy-04
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-proxy-04
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp