Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)
draft-ietf-manet-rfc6622-bis-03

The information below is for an old version of the document
Document Type Active Internet-Draft (manet WG)
Last updated 2013-07-23 (latest revision 2013-07-02)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Joseph Macker
Shepherd write-up Show (last changed 2013-05-29)
IESG IESG state Waiting for AD Go-Ahead::Revised I-D Needed
Telechat date
Responsible AD Adrian Farrel
IESG note The Document Shepherd is Joseph Macker (jpmacker@gmail.com).
Send notices to manet-chairs@tools.ietf.org, draft-ietf-manet-rfc6622-bis@tools.ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state None
Mobile Ad hoc Networking (MANET)                              U. Herberg
Internet-Draft                           Fujitsu Laboratories of America
Obsoletes: 6622 (if approved)                                 T. Clausen
Intended status: Standards Track                LIX, Ecole Polytechnique
Expires: January 3, 2014                                     C. Dearlove
                                                         BAE Systems ATC
                                                            July 2, 2013

          Integrity Check Value and Timestamp TLV Definitions
                  for Mobile Ad Hoc Networks (MANETs)
                    draft-ietf-manet-rfc6622-bis-03

Abstract

   This document revises, extends and replaces RFC 6622.  It describes
   general and flexible TLVs for representing cryptographic Integrity
   Check Values (ICVs) and timestamps, using the generalized Mobile Ad
   Hoc Network (MANET) packet/message format defined in RFC 5444.  It
   defines two Packet TLVs, two Message TLVs, and two Address Block TLVs
   for affixing ICVs and timestamps to a packet, a message, and one or
   more addresses, respectively.

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 January 3, 2014.

Copyright Notice

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

   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

Herberg, et al.          Expires January 3, 2014                [Page 1]
Internet-Draft      ICV and Timestamp TLVs for MANETs          July 2013

   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.

Herberg, et al.          Expires January 3, 2014                [Page 2]
Internet-Draft      ICV and Timestamp TLVs for MANETs          July 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.   Differences from RFC6622  . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  Applicability Statement  . . . . . . . . . . . . . . . . . . .  5
   4.  Security Architecture  . . . . . . . . . . . . . . . . . . . .  6
   5.  Overview and Functioning . . . . . . . . . . . . . . . . . . .  7
   6.  General ICV TLV Structure  . . . . . . . . . . . . . . . . . .  8
   7.  General Timestamp TLV Structure  . . . . . . . . . . . . . . .  8
   8.  Packet TLVs  . . . . . . . . . . . . . . . . . . . . . . . . .  9
     8.1.   ICV Packet TLV  . . . . . . . . . . . . . . . . . . . . .  9
     8.2.   TIMESTAMP Packet TLV  . . . . . . . . . . . . . . . . . . 10
   9.  Message TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 10
     9.1.   ICV Message TLV . . . . . . . . . . . . . . . . . . . . . 10
     9.2.   TIMESTAMP Message TLV . . . . . . . . . . . . . . . . . . 11
   10. Address Block TLVs . . . . . . . . . . . . . . . . . . . . . . 11
     10.1.  ICV Address Block TLV . . . . . . . . . . . . . . . . . . 11
     10.2.  TIMESTAMP Address Block TLV . . . . . . . . . . . . . . . 11
   11. ICV: Basic . . . . . . . . . . . . . . . . . . . . . . . . . . 12
   12. ICV: Hash Function and Cryptographic Function  . . . . . . . . 12
     12.1.  General ICV TLV Structure . . . . . . . . . . . . . . . . 12
       12.1.1.  Rationale . . . . . . . . . . . . . . . . . . . . . . 14
     12.2.  Considerations for Calculating the ICV  . . . . . . . . . 14
       12.2.1.  Packet ICV TLV  . . . . . . . . . . . . . . . . . . . 14
       12.2.2.  Message ICV TLV . . . . . . . . . . . . . . . . . . . 15
       12.2.3.  Address Block ICV TLV . . . . . . . . . . . . . . . . 15
     12.3.  Example of a Message Including an ICV . . . . . . . . . . 16
   13. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 16
Show full document text