Re: [pcp] To change a mapping does the pcp source port need remain the same?
Simon Perreault <simon.perreault@viagenie.ca> Mon, 17 September 2012 13:36 UTC
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 08CA321F84F1 for <pcp@ietfa.amsl.com>; Mon, 17 Sep 2012 06:36:03 -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.055, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 mK9e3zts3jzP for <pcp@ietfa.amsl.com>; Mon, 17 Sep 2012 06:36:02 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7E65E21F863F for <pcp@ietf.org>; Mon, 17 Sep 2012 06:36:02 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:6c52:66b:8aa8:775f]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E67BD400AB for <pcp@ietf.org>; Mon, 17 Sep 2012 09:36:01 -0400 (EDT)
Message-ID: <50572741.4020802@viagenie.ca>
Date: Mon, 17 Sep 2012 09:36:01 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0
MIME-Version: 1.0
To: pcp@ietf.org
References: <877grv5pnk.fsf@xmission.com>
In-Reply-To: <877grv5pnk.fsf@xmission.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [pcp] To change a mapping does the pcp source port need remain the same?
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 Sep 2012 13:36:03 -0000
Le 2012-09-15 10:25, Eric W. Biederman a écrit : > Would it be an error for a pcp server to require pcp clients to use > the same source port that a mapping was established with to change > that mapping? Yes it would. > As a trivial way to keep different clients from stepping on each other > by accident I would certainly require the source port to remain constant > to change a mapping. Two issues I see: - It would only be a convenience, not secure, because it would be trivial to guess and spoof. - With long-lived mappings it becomes hard to guarantee that the same port will be used for all requests. 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] To change a mapping does the pcp source por… Eric W. Biederman
- Re: [pcp] To change a mapping does the pcp source… Simon Perreault