Re: [Hipsec] Updated hip drafts

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Wed, 02 November 2016 14:06 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 55A381294B6 for <hipsec@ietfa.amsl.com>; Wed, 2 Nov 2016 07:06:09 -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 G_Re816Z92PI for <hipsec@ietfa.amsl.com>; Wed, 2 Nov 2016 07:06:06 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 6E5DD12964E for <hipsec@ietf.org>; Wed, 2 Nov 2016 07:06:05 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-5a-5819f2cbd2f8
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by (Symantec Mail Security) with SMTP id 5D.CE.02551.BC2F9185; Wed, 2 Nov 2016 15:06:03 +0100 (CET)
Received: from [100.94.10.152] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.86) with Microsoft SMTP Server id 14.3.319.2; Wed, 2 Nov 2016 15:06:02 +0100
To: Robert Moskowitz <rgm@htt-consult.com>, HIP <hipsec@ietf.org>
References: <521c8747-2653-b1be-aa58-3c3e79410beb@htt-consult.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <513d3eab-c0d5-de7f-2b01-be146f6aef25@ericsson.com>
Date: Wed, 02 Nov 2016 16:06:01 +0200
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: <521c8747-2653-b1be-aa58-3c3e79410beb@htt-consult.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOLMWRmVeSWpSXmKPExsUyM2J7iO7pT5IRBj8atSymLprMbNGw7jOj A5PH7klN7B5LlvxkCmCK4rJJSc3JLEst0rdL4Mpo3PKMseAfd8Ws7j72BsYfnF2MnBwSAiYS 0ya9ZO5i5OIQEljHKLHvzDQ2CGcVo8S7ZceYQaqEBTQkbtyaBGaLCDhK/Ot+wAZiCwk4Sfzc cY0VxGYTsJDYcus+C4jNK2Av8WvXJnYQm0VARaJ9URdYXFQgRuL6s0dsEDWCEidnPgGLcwo4 S2xc+ReonoODWUBTYv0ufZAws4C8xPa3c5ghVmlLLH/WwjKBkX8Wku5ZCB2zkHQsYGRexSha nFpcnJtuZKyXWpSZXFycn6eXl1qyiREYfAe3/Nbdwbj6teMhRgEORiUe3g9rJSKEWBPLiitz DzFKcDArifC+eC8ZIcSbklhZlVqUH19UmpNafIhRmoNFSZzXbOX9cCGB9MSS1OzU1ILUIpgs EwenVAOjj7PE7wXBv5/xPzpyL3KTQZnfSvagjN1NelmC/Gdu7rtzcKO39h85/s8V56t+PlkU viGNrfTm5WVemW6tm84dTvgvdkRrruOLPXOatUUtZ5/Rn6Sw28juxJ445aJdG1M0D4Wryr2Q KD31rU5yccLufcv36+kzfNpasj+5MGq+0fcv9hXp2+OuKLEUZyQaajEXFScCAP1/txM6AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/52xGtOOa_dK3ODRj__fd1O2dB2k>
Subject: Re: [Hipsec] Updated hip drafts
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: Wed, 02 Nov 2016 14:06:09 -0000

Hi Bob,

as you know, this WG is scheduled to close down soon, per our charter:

https://datatracker.ietf.org/wg/hip/charter/

The plan is to publish the native NAT traversal, HIP DEX, and
architecture specs and then close it down.

So, at this point we would need to find a home for these new drafts. The
idea would be to socialize them, get some traction in the community, and
then talk with our AD.

If there is energy behind them, our AD will for sure find or create a
home for them. If there is not enough energy... well...

Cheers,

Gonzalo

On 28/10/2016 3:31 AM, Robert Moskowitz wrote:
> I just updated a a set of drafts:
> 
> These define a Secure Session Layer Service.  The last has how to manage
> it with HIP and defines some new HIP parameters to negotiate sse and
> gpcomp:
> 
> https://www.ietf.org/internet-drafts/draft-moskowitz-sse-04.txt
> https://www.ietf.org/internet-drafts/draft-moskowitz-gpcomp-01.txt
> https://www.ietf.org/internet-drafts/draft-moskowitz-ssls-hip-01.txt
> 
> These propose a hip-based mobility solution for 5gpp.  IPnHIP can use
> gpcomp:
> 
> https://www.ietf.org/internet-drafts/draft-moskowitz-hierarchical-hip-02.txt
> 
> https://www.ietf.org/internet-drafts/draft-moskowitz-hip-ipnhip-01.txt
> https://www.ietf.org/internet-drafts/draft-moskowitz-hip-fast-mobility-01.txt
> 
> https://www.ietf.org/internet-drafts/draft-moskowitz-hip-based-5gpp-ip-mobility-01.txt
> 
> 
> I welcome all comments.
> 
> Thank you
> 
> Robert Moskowitz
>