Re: [Hipsec] WGLC draft-ietf-hip-native-nat-traversal

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Mon, 15 February 2016 07:06 UTC

Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 576EE1A8992 for <hipsec@ietfa.amsl.com>; Sun, 14 Feb 2016 23:06:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.801
X-Spam-Level:
X-Spam-Status: No, score=-102.801 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 PM9UXsuvobKu for <hipsec@ietfa.amsl.com>; Sun, 14 Feb 2016 23:06:50 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC9091ACD42 for <hipsec@ietf.org>; Sun, 14 Feb 2016 23:06:49 -0800 (PST)
X-AuditID: c1b4fb3a-f79ce6d000005138-a1-56c179079904
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id F7.D8.20792.70971C65; Mon, 15 Feb 2016 08:06:47 +0100 (CET)
Received: from [131.160.36.84] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.71) with Microsoft SMTP Server id 14.3.248.2; Mon, 15 Feb 2016 08:06:47 +0100
To: Petri Jokela <petri.jokela@ericsson.com>, HIP <hipsec@ietf.org>
References: <A6792EE5-731B-4413-A3E2-37791A972C03@ericsson.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <56C17906.8030803@ericsson.com>
Date: Mon, 15 Feb 2016 09:06:46 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <A6792EE5-731B-4413-A3E2-37791A972C03@ericsson.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyM2K7qy575cEwg2VfzCymLprM7MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujHXNDYwFO7kqrv9tZ2pg7OHoYuTkkBAwkbg7aQc7hC0mceHe erYuRi4OIYHDjBIT2k8yQTirGSVufN/GAlIlLGAqcfN3IxOILSLgLHHiygdGEFtIwF7i8old YDazQKLE/yenwaayCVhIbLl1H6yXV0Bboru3FayXRUBVYvmKCWBxUYEYiYudR5ggagQlTs58 AhbnFHCQOPJnKlCcA2impsT6XfoQ4+UlmrfOZoZYqy2x/FkLywRGwVlIumchdMxC0rGAkXkV o2hxanFxbrqRkV5qUWZycXF+nl5easkmRmBgHtzy22oH48HnjocYBTgYlXh4N5w7ECbEmlhW XJl7iFGCg1lJhNcv/WCYEG9KYmVValF+fFFpTmrxIUZpDhYlcd41zuvDhATSE0tSs1NTC1KL YLJMHJxSDYw5c3KZ9gd3VnxQs97Aafj/XqdpFm9wjmm9ZdWC3nXrfj2ezmzcoR00pe4bn79H +U/Nb7LFzAIsicXtCy6xJu3k6V95aL2gzBG98l6NpLTfH1m/+GcdTGUrvVytueOa1OHVsm49 u6S2B9rzsGwS1D6dcuyjVMKr/abf2n5PKHHOOfXTctv/YCWW4oxEQy3mouJEAONrNYRIAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/hipsec/DTiw4PNpAyQt1DDgEfuxCvuMa28>
Cc: Jan Melen <jan.melen@ericsson.com>, =?UTF-8?Q?Ari_Ker=c3=a4nen?= <ari.keranen@ericsson.com>
Subject: Re: [Hipsec] WGLC draft-ietf-hip-native-nat-traversal
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2016 07:06:51 -0000

Hi,

I am resending Petri's comments below.

Cheers,

Gonzalo

On 15/02/2016 8:08 AM, Petri Jokela wrote:
> Hi, 
> 
> I read through the draft (draft-ietf-hip-native-nat-traversal) and from
> technical perspective it seems to be ok. Some thoughts about the
> document itself:
> 
> HIP Relay server came up suddenly and it was hard to understand the
> operation of the node.  At some point I also mixed HIP data relay and
> HIP relay server. Which node is doing NATting? A short intro that would
> explain the operation of these nodes would help.
> 
> The same issue came up with Address candidates. Reading the referenced
> document might help, but now the document does not give direct
> understanding what candidates we are looking after. Again, a short intro
> makes it clearer.
> 
> Flow charts would help to understand the message exchange. 
> 
> In general, the document refers a lot to other RFCs. My suggestion is to
> check the document and add some introductory sentences for
> clarifications whenever a “new” node or operation is introduced.
> 
> Petri
> 
> -- 
> Petri Jokela
> Senior researcher
> NomadicLab, Ericsson Research
> Oy L M Ericsson Ab                  
> 
> E-mail: petri.jokela@ericsson.com <mailto:petri.jokela@ericsson.com>
> Mobile: +358 44 299 2413
> 
> 
>