Re: [pcp] Fw:I-D Action: New Version Notification for draft-tsou-pcp-natcoord-08.txt

Simon Perreault <simon.perreault@viagenie.ca> Thu, 01 November 2012 21:04 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 A8DDB21F9732 for <pcp@ietfa.amsl.com>; Thu, 1 Nov 2012 14:04:51 -0700 (PDT)
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 jExCFAGmhRYr for <pcp@ietfa.amsl.com>; Thu, 1 Nov 2012 14:04:51 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id E613E21F9731 for <pcp@ietf.org>; Thu, 1 Nov 2012 14:04:50 -0700 (PDT)
Received: from porto.nomis80.org (85-169-39-219.rev.numericable.fr [85.169.39.219]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 01C2841A0B; Thu, 1 Nov 2012 17:04:48 -0400 (EDT)
Message-ID: <5092E3EF.7090308@viagenie.ca>
Date: Thu, 01 Nov 2012 22:04:47 +0100
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121016 Thunderbird/16.0.1
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <CAH3bfAAn79BdM+F9G2WkJwvwxo08y89Fa3D6VKRX6cOZu98FYA@mail.gmail.com> <0c8701cdb792$8ee8c4a0$acba4de0$@cisco.com> <CAH3bfABZOjVZqHzZ7PTJfQ5WQT0wUnbZRtMCoJJfVsMw==U8bQ@mail.gmail.com> <01ac01cdb840$0ef753c0$2ce5fb40$@cisco.com> <5092A3EB.2030500@viagenie.ca> <046101cdb872$e9c448f0$bd4cdad0$@cisco.com>
In-Reply-To: <046101cdb872$e9c448f0$bd4cdad0$@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: pcp@ietf.org
Subject: Re: [pcp] Fw:I-D Action: New Version Notification for draft-tsou-pcp-natcoord-08.txt
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: Thu, 01 Nov 2012 21:04:51 -0000

Le 2012-11-01 21:53, Dan Wing a écrit :
>> Le 2012-11-01 15:49, Dan Wing a écrit :
>>> Ok.  Which UDP port does the CPE send that PCP request, if it does not
>>> yet already know the port range assigned to the CPE?
>>
>> Uh?
>
> Sorry, I meant to ask:
>
>    *from* which UDP port does the CPE send that PCP request.
>
> or can it use any source UDP port for its PCP request, or does it have
> to be one of its assigned UDP ports (which aren't yet assigned until
> PCP exchange)?

That's what I understood. And the answer is still the same:

Q: From which UDP port does the CPE send a MAP request?
A: From any UDP port on the internal address it already has.

Q: From which UDP port does the CPE send a MAP_PORT_SET request?
A: From any UDP port on the internal address it already has.

There must be something else I'm not getting...

Simon

>> MAP gives one port.
>> MAP_PORT_SET gives a set of ports.
>>
>> MAP and MAP_PORT_SET have the same answer to your question.
>>
>> 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
>


-- 
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