Re: [pcp] PCP Server Selection - Address Family Selection

Dan Wing <dwing@cisco.com> Sat, 26 April 2014 20:38 UTC

Return-Path: <dwing@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF95F1A06B3 for <pcp@ietfa.amsl.com>; Sat, 26 Apr 2014 13:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.724
X-Spam-Level:
X-Spam-Status: No, score=-13.724 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iSTKvvq-wGRb for <pcp@ietfa.amsl.com>; Sat, 26 Apr 2014 13:38:48 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 3F7E91A02F2 for <pcp@ietf.org>; Sat, 26 Apr 2014 13:38:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1205; q=dns/txt; s=iport; t=1398544721; x=1399754321; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=0gRS3kepMinoIquM5Y2WdrrW3C5mm3cUqAizv9aYXMg=; b=IErGZFiylVy6zhFKLY+5YgWq501AGu/DyQ1HT+PQGPLF6wbBtyEteQQv NSheJX+gaDwNAsWzBOdgkbQpD9oiY5hr+wlIaOzpn0RKp5zurrvE9WvjR rvqOmnb8LO0s2cgrDyt6IeSilcfFLBbVyICATIuapWOB02b9Rc0qBVWEI A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAPoXXFOrRDoG/2dsb2JhbABZgwbGBIELFnSCJQEBAQMBeQULC0ZXBgESiDkHyWMXjiYzB4MkgRUEiXGPG4ZdjAGDUR0
X-IronPort-AV: E=Sophos;i="4.97,934,1389744000"; d="scan'208";a="108662843"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 26 Apr 2014 20:38:41 +0000
Received: from [10.21.102.114] ([10.21.102.114]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3QKcNrf030177; Sat, 26 Apr 2014 20:38:40 GMT
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <535A77E8.7010201@viagenie.ca>
Date: Fri, 25 Apr 2014 18:42:53 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <79E3AFAF-D801-4152-94AC-57FA4B5D1BED@cisco.com>
References: <20140425145138.GC4891@gw01.ehlo.wurstkaes.de> <535A77E8.7010201@viagenie.ca>
To: Simon Perreault <simon.perreault@viagenie.ca>, Sebastian Kiesel <ietf-pcp@skiesel.de>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/pQLs3kHcCylV4Ur71lP3WNBmUh0
Cc: PCP Working Group <pcp@ietf.org>
Subject: Re: [pcp] PCP Server Selection - Address Family Selection
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 26 Apr 2014 20:38:50 -0000

On Apr 25, 2014, at 7:57 AM, Simon Perreault <simon.perreault@viagenie.ca> wrote:

> Le 2014-04-25 10:51, Sebastian Kiesel a écrit :
>> draft-ietf-pcp-server-selection-02  says in Section 3:
>> 
>>   1.  If the PCP client can use both address families when
>>       communicating to a particular PCP server, the PCP client SHOULD
>>       select the source address of the PCP request to be of the same IP
>>       address family as its requested PCP mapping (i.e., the address
>>       family of the Requested External IP Address).
>> 
>> 
>> What is the reason for saying it SHOULD use the same familiy as the
>> requested EXTERNAL IP address?  I think it would make more sense to use
>> the same familiy as the INTERNAL address (if there is a difference at
>> all).
> 
> +1
> 
> I stated this in my review.

The intent of the wording is to avoid NAT64 (or NAT46) where NAT44 or no NAT was necessary at all.  If the wording is backwards, let's fix it.  I have now read it three times, and the existing text seems to avoid NAT64.  In any event, yes, there should be an explanation ("To avoid unnecessary IP address family translation, ...").

-d