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

Simon Perreault <simon.perreault@viagenie.ca> Mon, 07 January 2013 09:44 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 DBC6421F869C for <pcp@ietfa.amsl.com>; Mon, 7 Jan 2013 01:44:44 -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 5vnkIeM+-nFX for <pcp@ietfa.amsl.com>; Mon, 7 Jan 2013 01:44:44 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4667321F868F for <pcp@ietf.org>; Mon, 7 Jan 2013 01:44:43 -0800 (PST)
Received: from porto.nomis80.org (85-169-40-152.rev.numericable.fr [85.169.40.152]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 97FB140110 for <pcp@ietf.org>; Mon, 7 Jan 2013 04:44:42 -0500 (EST)
Message-ID: <50EA9909.4040401@viagenie.ca>
Date: Mon, 07 Jan 2013 10:44:41 +0100
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: pcp@ietf.org
References: <45A697A8FFD7CF48BCF2BE7E106F06041E9D32@xmb-rcd-x04.cisco.com> <45A697A8FFD7CF48BCF2BE7E106F06041E9D48@xmb-rcd-x04.cisco.com> <01ab01cde953$1cbfed70$563fc850$@cisco.com> <CAH3bfAD+xumMtSWAm8bc_C-0FUBJZ_YXDJHwN9Xw0MNBnon=6w@mail.gmail.com> <037201cdeae9$b4109e80$1c31db80$@cisco.com>
In-Reply-To: <037201cdeae9$b4109e80$1c31db80$@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
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 09:44:45 -0000

Dan,

Just trying to provide some more clarification...

Le 2013-01-05 03:09, Dan Wing a écrit :
> Can it work with a CGN?

Depends what you mean by CGN.

In the current draft version (-09), MAP_PORT_SET assumes that the NAT 
never changes port numbers. The NAT MAY change addresses.

It is possible to remove that assumption. We are planning to do that 
after the call for adoption. Then MAP_PORT_SET will be exactly like MAP, 
except that it works with port *sets* (obviously).

> With the current document text, I cannot understand what sort of
> deployments where NATCOORD can or cannot be used.  Until I understand
> that, I can't decide if this document is a good idea or a bad idea.

Hopefully the above explanation of the protocol will be sufficient for 
you to figure out its applicability. :)

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