IETF Logo Mail Archive

Re: [pcp] PREFIX64 PCP Option for NAT64: draft-boucadair-pcp-nat64-prefix64-option

Simon Perreault <simon.perreault@viagenie.ca> Tue, 11 September 2012 17:12 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 DCF0C21F84B9 for <pcp@ietfa.amsl.com>; Tue, 11 Sep 2012 10:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level:
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038, 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 67vrlRkkM8Lj for <pcp@ietfa.amsl.com>; Tue, 11 Sep 2012 10:12:44 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4187B21F8498 for <pcp@ietf.org>; Tue, 11 Sep 2012 10:12:44 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:1d7c:5db4:d43e:122c]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 64AB445BCC; Tue, 11 Sep 2012 13:12:38 -0400 (EDT)
Message-ID: <504F7105.6010108@viagenie.ca>
Date: Tue, 11 Sep 2012 13:12:37 -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: Dan Wing <dwing@cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36E57B08381@PUEXCB1B.nanterre.francetelecom.fr> <504898BD.7000702@viagenie.ca> <94C682931C08B048B7A8645303FDC9F36E57B08524@PUEXCB1B.nanterre.francetelecom.fr> <5048AC63.50700@viagenie.ca> <94C682931C08B048B7A8645303FDC9F36E57B085C5@PUEXCB1B.nanterre.francetelecom.fr> <5048C127.50704@viagenie.ca> <94C682931C08B048B7A8645303FDC9F36E5A10BF57@PUEXCB1B.nanterre.francetelecom.fr> <074001cd903f$ffc7b570$ff572050$@com>
In-Reply-To: <074001cd903f$ffc7b570$ff572050$@com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: pcp@ietf.org
Subject: Re: [pcp] PREFIX64 PCP Option for NAT64: draft-boucadair-pcp-nat64-prefix64-option
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: Tue, 11 Sep 2012 17:12:45 -0000

Le 2012-09-11 13:08, Dan Wing a écrit :
> The message flow for the new PCP Opcode implies there is always
> an additional round trip.  There is only an additional round-trip
> if MAP (or PEER) is used.  If, on the other hand, the host only
> needed to learn the NAT64 prefix (and then it set up a TCP
> connection), the number of messages on the network is exactly
> the same for the MAP option or the new Opcode, assuming the PCP
> client simply leaves the dangling MAP-created mapping until its
> Lifetime expires.

Can't the two opcodes be sent simultaneously? No need to wait for one 
request to finish before starting another one...

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

v2.23.0 | Report a Bug | By Email