Re: [Hipsec] RFC 4423bis and hip-dex
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Thu, 27 October 2016 11:07 UTC
Return-Path: <gonzalo.camarillo@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 7EAFE129445 for <hipsec@ietfa.amsl.com>; Thu, 27 Oct 2016 04:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.221
X-Spam-Level:
X-Spam-Status: No, score=-104.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, USER_IN_WHITELIST=-100] 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 vzcTa96C77KH for <hipsec@ietfa.amsl.com>; Thu, 27 Oct 2016 04:07:04 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 539C2129A67 for <hipsec@ietf.org>; Thu, 27 Oct 2016 04:07:04 -0700 (PDT)
X-AuditID: c1b4fb25-93fff70000001e3e-fe-5811dfd61cc9
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by (Symantec Mail Security) with SMTP id 19.79.07742.6DFD1185; Thu, 27 Oct 2016 13:07:02 +0200 (CEST)
Received: from [100.94.10.26] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.68) with Microsoft SMTP Server id 14.3.319.2; Thu, 27 Oct 2016 13:07:02 +0200
To: Miika Komu <miika.komu@ericsson.com>
References: <d0a5a44c-bf5c-399b-90c1-e379b4b8f39b@ericsson.com> <05261b68-ce2d-f6cc-7ce9-807b64151a4f@ericsson.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <66ff7348-c953-9f76-af59-68e1fbac56db@ericsson.com>
Date: Thu, 27 Oct 2016 14:07:01 +0300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <05261b68-ce2d-f6cc-7ce9-807b64151a4f@ericsson.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM2K7k+61+4IRBpfmGVhMXTSZ2aJh3WdG ByaP3ZOa2D2WLPnJFMAUxWWTkpqTWZZapG+XwJUxfe5s9oIu1orurs1MDYxNLF2MnBwSAiYS 86Y/Ze9i5OIQEljPKPF42W42CGcVo8Tu7f8YQaqEBVQkJt2YywpiiwhoSDSe3ARmCwmUSnw4 OQushlnAUWLS+0dgcTYBC4ktt+6DbeAVsJe48HouE4jNIqAqsfP3WWYQW1QgRuL6s0dsEDWC EidnPgGr5xRwkFjS+wBoDgfQTE2J9bv0IcbLS2x/O4cZYq22xPJnLSwTGAVmIemehdAxC0nH AkbmVYyixanFSbnpRsZ6qUWZycXF+Xl6eaklmxiBQXlwy2/VHYyX3zgeYhTgYFTi4X2wTSBC iDWxrLgy9xCjBAezkghv7l3BCCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8ZivvhwsJpCeWpGan phakFsFkmTg4pRoYQz6dmaNX9SxtrZHnb+U/MyOVGOf+vPH9qMiu93Pk1D/smpBw9fT1Cfqy PwymXhdj2GpgZqnyLMvTMH7eSn6GV0zhlo9qJmodDPuY/oiR4ZegofXZzVZST1jK80483fk8 7PqF0B+XlnyZtbWn5HbP1+NXFk8P2fDnZXBPWL0aF6P4uyP/pwmLMiqxFGckGmoxFxUnAgAS FU1TRgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/DIoJgg5L3Ah8tBy9CYjM6RZXOD4>
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 11:07:08 -0000
Hi Miika, the plan is to publish rfc4423bis last, after all other drafts in our charter (including HIP DEX) have been published. So, this would not have any influence in the planned queue. Cheers, Gonzalo On 27/10/2016 1:57 PM, Miika Komu wrote: > 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. >
- [Hipsec] RFC 4423bis and hip-dex Gonzalo Camarillo
- Re: [Hipsec] RFC 4423bis and hip-dex Miika Komu
- Re: [Hipsec] RFC 4423bis and hip-dex Gonzalo Camarillo
- Re: [Hipsec] RFC 4423bis and hip-dex Miika Komu