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

Ari Keränen <ari.keranen@ericsson.com> Tue, 16 February 2016 13:59 UTC

Return-Path: <ari.keranen@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 47D681B2D3E for <hipsec@ietfa.amsl.com>; Tue, 16 Feb 2016 05:59:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level:
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 JDVwapWshZee for <hipsec@ietfa.amsl.com>; Tue, 16 Feb 2016 05:59:34 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4075B1B317A for <hipsec@ietf.org>; Tue, 16 Feb 2016 05:59:33 -0800 (PST)
X-AuditID: c1b4fb2d-f794c6d000006f31-51-56c32b433ed2
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id D4.7F.28465.34B23C65; Tue, 16 Feb 2016 14:59:31 +0100 (CET)
Received: from m46.nomadiclab.com (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.29) with Microsoft SMTP Server id 14.3.248.2; Tue, 16 Feb 2016 14:59:31 +0100
To: Petri Jokela <petri.jokela@ericsson.com>, HIP <hipsec@ietf.org>
References: <A6792EE5-731B-4413-A3E2-37791A972C03@ericsson.com> <56C17906.8030803@ericsson.com>
From: =?UTF-8?Q?Ari_Ker=c3=a4nen?= <ari.keranen@ericsson.com>
Message-ID: <56C32B41.8020209@ericsson.com>
Date: Tue, 16 Feb 2016 15:59:29 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56C17906.8030803@ericsson.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyM2K7tK6z9uEwgyVvTC2mLprM7MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujMt9bxgL2ngrFn0VamDcxdXFyMkhIWAi8fxXNzuELSZx4d56 ti5GLg4hgcOMEjc2fmWFcNYxSvzu3MsEUiUsYCfxeO5ERhBbRMBZ4sSVD2C2kECixNvpv1hA bGYBNYllP3aC1bMJ2Er8bt8DZvMKaEtsuDITqJ6Dg0VAVeLeVheQsKhAmsT+2b+hSgQlTs58 AjaGU0BHovHRXDaIkRYSM+efZ4Sw5SWat85mhlirKnH13yvGCYyCs5C0z0LSMgtJywJG5lWM osWpxcW56UbGeqlFmcnFxfl5enmpJZsYgYF5cMtv3R2Mq187HmIU4GBU4uEtiDgUJsSaWFZc mXuIUYKDWUmE998roBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXHeNc7rw4QE0hNLUrNTUwtSi2Cy TBycUg2M0wI0zcq87SOqXu6aNdno58GDyr76K5pnft35l/GizsSCxSevCZ8oUXV/s/qkkvYd /RsL203eLOS5NvNF6YEPkWnLr6XueKbBtfJKYOw5lvRFYQL8jqfsPpbH/DrlyKaeyzapM2My L+PznUzn5B5VFE1J3DdHe6Jy/6QY2a5cd0Vd5S3x/04fUGIpzkg01GIuKk4EAE8t0yxIAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/hipsec/ZJTmVh3xanQ5qWQiZYdFAuP7wfQ>
Cc: Jan Melen <jan.melen@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: Tue, 16 Feb 2016 13:59:36 -0000

Thank you for the review Petri! We will add introductory text to the 
draft to cover your comments.


Cheers,
Ari

On 15/02/16 09:06, Gonzalo Camarillo wrote:
> 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
>>
>>
>>
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
>