Re: [pcp] PCP proxying / relaying

"Dan Wing" <dwing@cisco.com> Wed, 16 March 2011 18:53 UTC

Return-Path: <dwing@cisco.com>
X-Original-To: pcp@core3.amsl.com
Delivered-To: pcp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 880593A69F4 for <pcp@core3.amsl.com>; Wed, 16 Mar 2011 11:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.332
X-Spam-Level:
X-Spam-Status: No, score=-110.332 tagged_above=-999 required=5 tests=[AWL=0.267, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSUnIP8FWE4y for <pcp@core3.amsl.com>; Wed, 16 Mar 2011 11:53:49 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 9C14E3A6997 for <pcp@ietf.org>; Wed, 16 Mar 2011 11:53:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1274; q=dns/txt; s=iport; t=1300301716; x=1301511316; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=Zj+2aqIwHleaIZYhFnJ+IVgdPUI6zyJnn50lPuK2tkE=; b=QYBXsFgKlQbgbOdjr/r8yEcqOAJBr26dpfZCgTkxPIbiKyxKNjygmbVZ ++02w0GY4V5c/ubN6letuyvNhdjK4pvb0Lwc3UZuT31OjAbB3+IDCZXGG DX81HJ8OiHW+zjJg5cHE4NP4f4i0thEiMQBmg9pU4+yPInd+NALtBSqpc c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnwBAPajgE2tJXHB/2dsb2JhbACYVz+BJYtRd6UCnFqFYwSFLw
X-IronPort-AV: E=Sophos;i="4.63,195,1299456000"; d="scan'208";a="276702502"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by sj-iport-4.cisco.com with ESMTP; 16 Mar 2011 18:55:16 +0000
Received: from dwingWS ([10.32.240.196]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id p2GItFpM017053; Wed, 16 Mar 2011 18:55:15 GMT
From: Dan Wing <dwing@cisco.com>
To: Francis.Dupont@fdupont.fr
References: Your message of Wed, 16 Mar 2011 09:29:26 MST. <16fd01cbe3f7$5156ee70$f404cb50$@com> <201103161649.p2GGnfY8088247@givry.fdupont.fr>
In-Reply-To: <201103161649.p2GGnfY8088247@givry.fdupont.fr>
Date: Wed, 16 Mar 2011 11:55:15 -0700
Message-ID: <011801cbe40b$b0691140$113b33c0$@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: Acvj+jFhYJz00QuZRnm28UMomM1vmwAES9SQ
Content-language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] PCP proxying / relaying
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2011 18:53:50 -0000

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Wednesday, March 16, 2011 9:50 AM
> To: Dan Wing
> Cc: 'Alain Durand'; pcp@ietf.org
> Subject: Re: [pcp] PCP proxying / relaying
> 
> 
>  In your previous mail you wrote:
> 
>    > => If you do that you'll be in trouble to send packets to this
> address.
> 
>    If we were to standardize on 1.1.1.1, it should be a single command
>    during startup:
> 
> => this is not the problem: if you use *one* address you can't at
> the same time assign this address at one of your interfaces *and*
> be able to forward packets further to the *same* address.
> 
>    which the daemon would then listen on.
> 
> => but the daemon won't be able to send request to the *next*
> PCP server at 1.1.1.1.

This seems quite similar to how today's ALGs function.  Can this be modeled
in the CPE router like an ALG?

A difference from a normal ALG is that sometimes a PCP response needs to be
generated by the CPE router itself (rather than forwarding the request to
the upstream PCP server).  But perhaps that is why the earlier PCP Proxy
paper (draft-bpw-pcp-proxy-00) mentioned 'faking' a response.

-d

> Regards
> 
> Francis.Dupont@fdupont.fr