Re: [pcp] WG Call for Adoption: draft-tsou-pcp-natcoord-09

Sam Hartman <hartmans@painless-security.com> Mon, 07 January 2013 17:15 UTC

Return-Path: <hartmans@painless-security.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 4D6FC21F8A08 for <pcp@ietfa.amsl.com>; Mon, 7 Jan 2013 09:15:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 yBVr1JgJvobC for <pcp@ietfa.amsl.com>; Mon, 7 Jan 2013 09:15:12 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id C24DC21F893D for <pcp@ietf.org>; Mon, 7 Jan 2013 09:15:12 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 052D920144; Mon, 7 Jan 2013 12:12:08 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 5A7B343F0; Mon, 7 Jan 2013 12:15:03 -0500 (EST)
From: Sam Hartman <hartmans@painless-security.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
References: <45A697A8FFD7CF48BCF2BE7E106F06041E9D48@xmb-rcd-x04.cisco.com> <82256834F867D44BBB8E49E40D5448BB065955DC@BL2PRD0510MB386.namprd05.prod.outlook.com> <50EA9BF9.2010302@viagenie.ca> <023601cdecf7$fd33cc80$f79b6580$@cisco.com> <50EB001E.3030003@viagenie.ca>
Date: Mon, 07 Jan 2013 12:15:03 -0500
In-Reply-To: <50EB001E.3030003@viagenie.ca> (Simon Perreault's message of "Mon, 07 Jan 2013 18:04:30 +0100")
Message-ID: <tsltxqs29uw.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: pcp@ietf.org
Subject: Re: [pcp] WG Call for Adoption: draft-tsou-pcp-natcoord-09
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, 07 Jan 2013 17:15:13 -0000

>>>>> "Simon" == Simon Perreault <simon.perreault@viagenie.ca> writes:

    Simon> Right, but I was thinking about a slightly different use case
    Simon> than draft-boucadair: some applications just like to get
    Simon> ownership of a chunk of ports when they start. This is mostly
    Simon> an implementation artifact, not really a protocol
    Simon> constraint. I had SIP apps in mind, but I guess the same
    Simon> could be said of BitTorrent apps or other apps that eat
    Simon> ports.

Let me give a concrete example.
A SIP PBX starts.
It wants to get a number of ports to use for media termination; probably
one or two for however many calls it might handle concurrently.
That's on over-estimate because of course ports can be reused if the
endpoints don't overlap.
The PBX doesn't want to generate PCP requests during call setup if it
has another option, so reserving a chunk of ports up front would be
valuable.

--Sam