IETF Logo Mail Archive

Re: [pcp] FW: New Version Notification for draft-ripke-pcp-tunnel-id-option-00.txt

Andreas Ripke <Andreas.Ripke@neclab.eu> Fri, 14 February 2014 16:09 UTC

Return-Path: <Andreas.Ripke@neclab.eu>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC2611A0242 for <pcp@ietfa.amsl.com>; Fri, 14 Feb 2014 08:09:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.15
X-Spam-Level:
X-Spam-Status: No, score=-3.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vQL96DdF6RRx for <pcp@ietfa.amsl.com>; Fri, 14 Feb 2014 08:09:28 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1AD1A02FB for <pcp@ietf.org>; Fri, 14 Feb 2014 08:09:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 5204C106CD5; Fri, 14 Feb 2014 17:09:21 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZHrxDnrvoKj; Fri, 14 Feb 2014 17:09:21 +0100 (CET)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 37EC3106CDD; Fri, 14 Feb 2014 17:09:11 +0100 (CET)
Received: from PALLENE.office.hd ([169.254.1.233]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Fri, 14 Feb 2014 17:09:11 +0100
From: Andreas Ripke <Andreas.Ripke@neclab.eu>
To: Simon Perreault <simon.perreault@viagenie.ca>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] FW: New Version Notification for draft-ripke-pcp-tunnel-id-option-00.txt
Thread-Index: AQHPKNN183BuJolhBUq4sUpr4CoLq5q0dB4QgABWtACAAB34wA==
Date: Fri, 14 Feb 2014 16:09:11 +0000
Message-ID: <2D2FFE4726FAF74285C45D69FDC30E79631D69FE@PALLENE.office.hd>
References: <20140213155106.26257.47053.idtracker@ietfa.amsl.com> <2D2FFE4726FAF74285C45D69FDC30E79631D6915@PALLENE.office.hd> <52FE316E.7000708@viagenie.ca>
In-Reply-To: <52FE316E.7000708@viagenie.ca>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.6.215]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/0k1rYqZR0AJFBjAqrMvO15d35Cs
Cc: Rolf Winter <Rolf.Winter@neclab.eu>, Thomas Dietz <Thomas.Dietz@neclab.eu>
Subject: Re: [pcp] FW: New Version Notification for draft-ripke-pcp-tunnel-id-option-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@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 Feb 2014 16:09:31 -0000

Hi Simon,

The use-case in draft-ietf-pcp-dslite is a different one.
There, the PCP proxy or client is located in the customer's realm.
What we describe is a scenario with one central PCP client located on a web portal serving all customers.
Therefore, an additional identifier is needed by the PCP server to associate the connection to be mapped with the customer's tunnel.

Best,

Andreas

> -----Original Message-----
> From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of Simon Perreault
> Sent: Friday, February 14, 2014 4:09 PM
> To: pcp@ietf.org
> Subject: Re: [pcp] FW: New Version Notification for draft-ripke-pcp-tunnel-id-
> option-00.txt
> 
> Le 2014-02-14 04:07, Andreas Ripke a écrit :
> > The below draft describes a scenario in that
> >   (1) the subscribers behind a CGN can freely choose their internal IP
> addresses
> >        (which potentially leads to overlapping IP address spaces)
> >   (2) a central PCP client is used for port mapping requests.
> > The CGN, acting as PCP server, cannot identify the subscriber just by the
> internal IP address provided with the THIRD_PARTY option.
> > Therefore, an additional identifier (the subscriber’s tunnel ID) to the PCP
> mapping request is needed.
> 
> Eerily similar to draft-ietf-pcp-dslite...
> 
> Why not send the PCP request inside the tunnel?
> 
> Simon
> --
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> STUN/TURN server               --> http://numb.viagenie.ca
> 
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp

v2.23.0 | Report a Bug | By Email