Re: [Hipsec] RFC 4423bis and hip-dex

Miika Komu <miika.komu@ericsson.com> Thu, 27 October 2016 10:57 UTC

Return-Path: <miika.komu@ericsson.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6539A129C78 for <hipsec@ietfa.amsl.com>; Thu, 27 Oct 2016 03:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 90vpZlXdpjRk for <hipsec@ietfa.amsl.com>; Thu, 27 Oct 2016 03:57:14 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72515129A73 for <hipsec@ietf.org>; Thu, 27 Oct 2016 03:57:14 -0700 (PDT)
X-AuditID: c1b4fb30-f60a598000000cb2-be-5811dd880e65
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by (Symantec Mail Security) with SMTP id BC.79.03250.88DD1185; Thu, 27 Oct 2016 12:57:12 +0200 (CEST)
Received: from [131.160.51.186] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.77) with Microsoft SMTP Server id 14.3.319.2; Thu, 27 Oct 2016 12:57:10 +0200
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
References: <d0a5a44c-bf5c-399b-90c1-e379b4b8f39b@ericsson.com>
From: Miika Komu <miika.komu@ericsson.com>
Organization: Ericsson AB
Message-ID: <05261b68-ce2d-f6cc-7ce9-807b64151a4f@ericsson.com>
Date: Thu, 27 Oct 2016 13:57:09 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <d0a5a44c-bf5c-399b-90c1-e379b4b8f39b@ericsson.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms080109030206080204080503"
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrHLMWRmVeSWpSXmKPExsUyM2K7t27HXcEIg/0fzS2mLprMbNGw7jOj A5PH7klN7B5LlvxkCmCK4rJJSc3JLEst0rdL4Mq4e/ISU8FEo4qHFzYyNjD2GXQxcnJICJhI HP21grGLkYtDSGA9o8TWFRehnDWMEp2XbrCBVAkLqEhMujGXFcQWETCTeP9vFROILSRgL/Hi 6msWEJtZwFFi0vtHYDVsAloSq+5cZwax+QUkJTY07AazeYHqW369AqtnEVCVuH12HVi9qECE xK2HHSwQNYISJ2c+AbM5BRwkTl+9xg5yELNAN6PExUsXgRo4gBarSFw8FjyBUWAWkpZZyMpm gd1kJjFv80NmCFtbYtnC11C2tcSMXwfZIGxFiSndD9khbFOJ10c/MkLYxhLL1v1lW8DIsYpR tDi1OCk33chIL7UoM7m4OD9PLy+1ZBMjMCYObvltsIPx5XPHQ4wCHIxKPLwPtglECLEmlhVX 5h5iVAGa82jD6guMUix5+XmpSiK84XcEI4R4UxIrq1KL8uOLSnNSiw8xSnOwKInzmq28Hy4k kJ5YkpqdmlqQWgSTZeLglGpg1L5u2bXtq0+n0UoR9pV6X2Vu3/s6r5NVzaxJyvUHrz3zyx2W rm8ddxnuuz8p53Ez5yXFj///Z776pWl9O81JTtY76bhsknsNq+us1YdYN++8Urd6kdApTmPn ZSm/I3+qpd4wdyw4fdwuQ/9KTNycSZ8ON27lWfVnXcfNs8zybIdCX8XdfnrrmBJLcUaioRZz UXEiAJqjFKWRAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/FUGGF1Jek87cVnAkwgT1uocqn1Y>
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] RFC 4423bis and hip-dex
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 27 Oct 2016 10:57:22 -0000

Hi Gonzalo,

On 10/21/2016 10:28 AM, Gonzalo Camarillo wrote:
> Bob, Miika,
>
> RFC 4423bis does not reference the hip-dex draft. Should it?
>
> https://tools.ietf.org/html/draft-ietf-hip-rfc4423-bis-14

we can add it if needed. The only problem is that we should push back 
the 4423bis draft in the IETF queue since dex creates an additional 
dependency.