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

Sebastian Kiesel <ietf-pcp@skiesel.de> Sat, 26 April 2014 21:38 UTC

Return-Path: <sebi@gw01.ehlo.wurstkaes.de>
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 3FC801A069C for <pcp@ietfa.amsl.com>; Sat, 26 Apr 2014 14:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.822
X-Spam-Level:
X-Spam-Status: No, score=-1.822 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.272] 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 D6WsZi0gEX7L for <pcp@ietfa.amsl.com>; Sat, 26 Apr 2014 14:38:13 -0700 (PDT)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id 23A4B1A0663 for <pcp@ietf.org>; Sat, 26 Apr 2014 14:38:12 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.80) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1WeAIH-00009g-Sa; Sat, 26 Apr 2014 23:37:57 +0200
Date: Sat, 26 Apr 2014 23:37:57 +0200
From: Sebastian Kiesel <ietf-pcp@skiesel.de>
To: Dan Wing <dwing@cisco.com>
Message-ID: <20140426213757.GD4891@gw01.ehlo.wurstkaes.de>
References: <20140425145138.GC4891@gw01.ehlo.wurstkaes.de> <535A77E8.7010201@viagenie.ca> <79E3AFAF-D801-4152-94AC-57FA4B5D1BED@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <79E3AFAF-D801-4152-94AC-57FA4B5D1BED@cisco.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/21PrMn38ykxbZC5SdR8PYsU78_A
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 21:38:15 -0000

On Fri, Apr 25, 2014 at 06:42:53PM -0700, Dan Wing wrote:
> 
> 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. 

reasonable goal, but does text about that belong here?

this text is about PCP messages, and I think they should use the
same address family as the actual user data flow on their side of
the NAT.

> 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, ...").

Thanks
Sebastian