datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

HIP Diet EXchange (DEX)
draft-moskowitz-hip-dex-01

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-03-04
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                  R. Moskowitz, Ed.
Internet-Draft                                                   Verizon
Intended status: Standards Track                               R. Hummen
Expires: September 5, 2014                           COMSYS, RWTH Aachen
                                                          March 04, 2014

                        HIP Diet EXchange (DEX)
                       draft-moskowitz-hip-dex-01

Abstract

   This document specifies the Host Identity Protocol Diet EXchange (HIP
   DEX), a variant of the HIP Base EXchange (HIP BEX) [rfc5201-bis].
   The HIP DEX protocol design aims at reducing the overhead of the
   employed cryptographic primitives by omitting public-key signatures
   and hash functions.  In doing so, the main goal is to still deliver
   similar security properties to HIP BEX.

   The HIP DEX protocol is primarily targeted at computation or memory-
   constrained sensor devices.  Like HIP BEX, it is expected to be used
   together with another suitable security protocol such as the
   Encapsulated Security Payload (ESP) [rfc5202-bis] for the protection
   of upper layer protocols.  HIP DEX can also be used as a keying
   mechanism for a MAC layer security protocol as is supported by IEEE
   802.15.4 [IEEE.802-15-4.2011].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 5, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Moskowitz & Hummen      Expires September 5, 2014               [Page 1]
Internet-Draft           HIP Diet EXchange (DEX)              March 2014

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  The HIP Diet EXchange (DEX) . . . . . . . . . . . . . . .   4
     1.2.  Memo Structure  . . . . . . . . . . . . . . . . . . . . .   5
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Requirements Terminology  . . . . . . . . . . . . . . . .   5
     2.2.  Notation  . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Host Identity (HI) and its Structure  . . . . . . . . . . . .   7
     3.1.  Host Identity Tag (HIT) . . . . . . . . . . . . . . . . .   8
     3.2.  Generating a HIT from an HI . . . . . . . . . . . . . . .   8
   4.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Creating a HIP Association  . . . . . . . . . . . . . . .   8
       4.1.1.  HIP Puzzle Mechanism  . . . . . . . . . . . . . . . .  10
       4.1.2.  HIP State Machine . . . . . . . . . . . . . . . . . .  11
       4.1.3.  HIP DEX Security Associations . . . . . . . . . . . .  14
       4.1.4.  User Data Considerations  . . . . . . . . . . . . . .  14
   5.  Packet Formats  . . . . . . . . . . . . . . . . . . . . . . .  15

[include full document text]