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

"Dan Wing" <dwing@cisco.com> Thu, 01 November 2012 22:40 UTC

Return-Path: <dwing@cisco.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 B594C21F9731 for <pcp@ietfa.amsl.com>; Thu, 1 Nov 2012 15:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.543
X-Spam-Level:
X-Spam-Status: No, score=-110.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 dptZJxKJovZz for <pcp@ietfa.amsl.com>; Thu, 1 Nov 2012 15:40:52 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id DA9B321F9676 for <pcp@ietf.org>; Thu, 1 Nov 2012 15:40:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2038; q=dns/txt; s=iport; t=1351809653; x=1353019253; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=Xwz0qNglCYQjxSalIGs0JHBe+JvhG/mV4OZ+N9L5T+U=; b=YOl6cpefjtYf5kz8OzzMPckSMpoyDubVDuFII3AVl5ZcHkPPYTQMmoQZ 5wckLwrIpL/aaJoQ8UbKCE6fRF8VE74ZCY3X/veJTkMDvEfBpZE+vEn1d jmB/Ngov0eZ6KQ9OPWN54G1/JBcgM8ny8tM+6Zyb4ofcBWA9/npafMSgo M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAKAAf5klCrRDoG/2dsb2JhbABEwi0DgQWBCIIeAQEBAwEBAQEFAggBFEcJAgUHAQMCCREEAQEoBxkOHwkIAgQTCwUSh14FDJx4oCuLe3SFRwOIJTWFF4gHgRuNPYFrgw8
X-IronPort-AV: E=Sophos;i="4.80,695,1344211200"; d="scan'208";a="62914550"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 01 Nov 2012 22:40:52 +0000
Received: from DWINGWS01 ([10.154.161.158]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qA1MeqB4007259; Thu, 1 Nov 2012 22:40:52 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Simon Perreault' <simon.perreault@viagenie.ca>
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> <5092E3EF.7090308@viagenie.ca>
In-Reply-To: <5092E3EF.7090308@viagenie.ca>
Date: Thu, 01 Nov 2012 15:40:51 -0700
Message-ID: <04a301cdb881$f26cc900$d7465b00$@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQNPFg3hnot8iaQn7dMg74vbEf4q5wHPoD1sAYkIPtMBOHUi3AFnS4+SAeZ6klcCPyvAa5SB5yGg
Content-Language: en-us
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 22:40:53 -0000

> -----Original Message-----
> From: Simon Perreault [mailto:simon.perreault@viagenie.ca]
> Sent: Thursday, November 01, 2012 2:05 PM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] Fw:I-D Action: New Version Notification for draft-
> tsou-pcp-natcoord-08.txt
> 
> 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...

If it doesn't get (learn) that UDP port via PCP, how does it
learn it?

-d


> 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