[Hipsec] 4 Internet drafts
Robert Moskowitz <rgm@htt-consult.com> Wed, 28 September 2016 12:24 UTC
Return-Path: <rgm@htt-consult.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 AF29612B10C for <hipsec@ietfa.amsl.com>; Wed, 28 Sep 2016 05:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.507
X-Spam-Level:
X-Spam-Status: No, score=-6.507 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] 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 qFfcJCy4YHQK for <hipsec@ietfa.amsl.com>; Wed, 28 Sep 2016 05:24:19 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [50.253.254.3]) (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 CEC4812B115 for <hipsec@ietf.org>; Wed, 28 Sep 2016 05:24:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 094DB62240 for <hipsec@ietf.org>; Wed, 28 Sep 2016 08:24:18 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LDxzyydEHTkR for <hipsec@ietf.org>; Wed, 28 Sep 2016 08:24:12 -0400 (EDT)
Received: from lx120e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 5344B62234 for <hipsec@ietf.org>; Wed, 28 Sep 2016 08:24:12 -0400 (EDT)
To: hip WG <hipsec@ietf.org>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <a7ef8700-6ee8-1dbe-43da-3a825aaa26c4@htt-consult.com>
Date: Wed, 28 Sep 2016 08:24:04 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/vNFhIL3Fh63Tise2XJ5qqioRYQo>
Subject: [Hipsec] 4 Internet 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, 28 Sep 2016 12:24:23 -0000
I have just uploaded 4 drafts. One a revision of my earlier Hierarchical HIT draft. With the other 3 you will begin to see where I am going with all this. I request and welcome all comments. I will be a Seoul for extended discussions on this and next steps. There are probably 2 more drafts minimal to put the proposal together. Bob A new version of I-D, draft-moskowitz-hip-based-5gpp-ip-mobility-00.txt has been successfully submitted by Robert Moskowitz and posted to the IETF repository. Name: draft-moskowitz-hip-based-5gpp-ip-mobility Revision: 00 Title: HIP Enabled ID/Loc separation for fast 5GPP IP mobility Document date: 2016-09-27 Group: Individual Submission Pages: 7 URL: https://www.ietf.org/internet-drafts/draft-moskowitz-hip-based-5gpp-ip-mobility-00.txt Status: https://datatracker.ietf.org/doc/draft-moskowitz-hip-based-5gpp-ip-mobility/ Htmlized: https://tools.ietf.org/html/draft-moskowitz-hip-based-5gpp-ip-mobility-00 Abstract: HIP [RFC7401] stands alone in providing a secure Endpoint ID for decoupling the Internetworking and Transport protocol layers. The addition of a secure rendezvous service to facilitate mobility will form the cornerstones for this 5GPP mobility technology. This document will describe complete mobility environment and the additional components needed. ====================================================================== A new version of I-D, draft-moskowitz-hierarchical-hip-01.txt has been successfully submitted by Robert Moskowitz and posted to the IETF repository. Name: draft-moskowitz-hierarchical-hip Revision: 01 Title: Hierarchical HITs for HIPv2 Document date: 2016-09-26 Group: Individual Submission Pages: 14 URL: https://www.ietf.org/internet-drafts/draft-moskowitz-hierarchical-hip-01.txt Status: https://datatracker.ietf.org/doc/draft-moskowitz-hierarchical-hip/ Htmlized: https://tools.ietf.org/html/draft-moskowitz-hierarchical-hip-01 Diff: https://www.ietf.org/rfcdiff?url2=draft-moskowitz-hierarchical-hip-01 Abstract: This document describes using a hierarchical HIT to facilitate large deployments in mobile networks. ====================================================================== A new version of I-D, draft-moskowitz-hip-fast-mobility-00.txt has been successfully submitted by Robert Moskowitz and posted to the IETF repository. Name: draft-moskowitz-hip-fast-mobility Revision: 00 Title: Fast HIP Host Mobility Document date: 2016-09-26 Group: Individual Submission Pages: 10 URL: https://www.ietf.org/internet-drafts/draft-moskowitz-hip-fast-mobility-00.txt Status: https://datatracker.ietf.org/doc/draft-moskowitz-hip-fast-mobility/ Htmlized: https://tools.ietf.org/html/draft-moskowitz-hip-fast-mobility-00 Abstract: This document describes mobility scenarios and how to aggressively support them in HIP. The goal is minimum lag in the mobility event. ====================================================================== A new version of I-D, draft-moskowitz-hip-ipnhip-00.txt has been successfully submitted by Robert Moskowitz and posted to the IETF repository. Name: draft-moskowitz-hip-ipnhip Revision: 00 Title: Encapsulation of IP within IP managed by HIP Document date: 2016-09-28 Group: Individual Submission Pages: 10 URL: https://www.ietf.org/internet-drafts/draft-moskowitz-hip-ipnhip-00.txt Status: https://datatracker.ietf.org/doc/draft-moskowitz-hip-ipnhip/ Htmlized: https://tools.ietf.org/html/draft-moskowitz-hip-ipnhip-00 Abstract: This document defines how to encapsulate IP within IP when the tunnel is managed with HIPv2 [RFC7401]. The goal is reduced header size and improved security over IPnIP [RFC2003] and RFC2004 [RFC2004].
- [Hipsec] 4 Internet drafts Robert Moskowitz