[pcp] Same vs different port

Alper Yegin <alper.yegin@yegin.org> Fri, 21 September 2012 16:37 UTC

Return-Path: <alper.yegin@yegin.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 6D3E221F877C for <pcp@ietfa.amsl.com>; Fri, 21 Sep 2012 09:37:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level:
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id csp30x2X3DC0 for <pcp@ietfa.amsl.com>; Fri, 21 Sep 2012 09:37:03 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 370D521F8777 for <pcp@ietf.org>; Fri, 21 Sep 2012 09:37:03 -0700 (PDT)
Received: from [192.168.2.5] (88.247.135.202.static.ttnet.com.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0Lj0D8-1TlPZH2fra-00dN5i; Fri, 21 Sep 2012 12:37:01 -0400
From: Alper Yegin <alper.yegin@yegin.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 21 Sep 2012 19:36:43 +0300
Message-Id: <12D3A1D0-1F9F-4453-BC6A-D4AD3DEFCABA@yegin.org>
To: Stuart Cheshire <cheshire@apple.com>, Dave Thaler <dthaler@microsoft.com>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-Provags-ID: V02:K0:1P9xlyEUwJh+jujLfn+POqdFdLREYdm7xtqYO4Wxwzw b/zndm37ity513wNIfXWEHmlYYoVWsp23B3Oa2Z1mWz+Db78zR l/4KoQqw8fMR3kzHNWk1GKwOG+vZRa1svn3v64rDp0Xtf9fOBz 8OPmr7Wu7X2+yxx8iCnpukH9zyam9Ys3VP+WuNZr6PLcB6zGO0 mqbE89IPLk3IfNDTkJv8GGGG6hRg63XoluzH6cqWI1Ottjf+VW hTF2oS/HT69CLfPbX8gO8rzUPsnN5A5cI373oZD2zf+eFf05OU COVizZozjovg4Xl3cBsMIpIEmUqvEkywUU7o+dj02JH/3egk/K IOMYVamOp53KA6dSOQE2pQ8p3DX6qGI/c3j3JJa0aX2jPvOgYB XDzGiSybR0fbQ==
Cc: pcp@ietf.org
Subject: [pcp] Same vs different port
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@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 Sep 2012 16:37:04 -0000

Hello,

I didn't want to use precious CC time on this, but I'm under the impression that the reasons used for ruling out running PANA and PCP over their dedicated ports are not plausible. 

I wasn't on the jabber at previous IETF, so maybe I missed some of the discussions. But from today's discussion, here's what I heard:

Following points were raised about running PANA and PCP over their dedicated ports (as opposed to running both over the PCP port):

1. Binding
2. Server discovery
3. Management 
Anything else?


For (1) binding, whether it's crypto-binding, or state-binding, whatever you call it -- one does not have to run the two protocols on the same port to achieve any of that. In fact, it is achieved thru use of common identifiers. The authenticated entity is provided a "session id" which gets used over PCP to indicate who the sender is. 

Using the same port is irrelevant.

For (2) server discovery, we're going with the PAA and PCP Server running on the same node assumption. However PCP server is discovered automatically reveals where the PAA is. Using the same port does not add any value here.

For (3) Stuart made a reference to complications, but I'd appreciate some more elaboration. 

 
Comments appreciated.

Alper