Identity-Based Signatures for Mobile Ad Hoc Network (MANET) Routing Protocols
draft-ietf-manet-ibs-05

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (manet WG)
Author Christopher Dearlove 
Last updated 2016-05-25 (latest revision 2016-03-21)
Replaces draft-dearlove-manet-ibs
Stream Internet Engineering Task Force (IETF)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Thomas Clausen
Shepherd write-up Show (last changed 2014-09-04)
IESG IESG state RFC 7859 (Experimental)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to aretana@cisco.com
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Mobile Ad hoc Networking (MANET)                             C. Dearlove
Internet-Draft                          BAE Systems Applied Intelligence
Intended status: Experimental                               Laboratories
Expires: September 22, 2016                               March 21, 2016

         Identity-Based Signatures for MANET Routing Protocols
                        draft-ietf-manet-ibs-05

Abstract

   This document extends RFC7182, which specifies a framework for, and
   specific examples of, integrity check values (ICVs) for packets and
   messages using the generalized packet/message format specified in
   RFC5444.  It does so by defining an additional cryptographic function
   that allows the creation of an ICV that is an identity-based
   signature, defined according to the ECCSI (Elliptic Curve-Based
   Certificateless Signatures for Identity-Based Encryption) algorithm
   specified in RFC6507.

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 22, 2016.

Copyright Notice

   Copyright (c) 2016 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
   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

Dearlove               Expires September 22, 2016               [Page 1]
Internet-Draft          Identity-Based Signatures             March 2016

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  Applicability Statement  . . . . . . . . . . . . . . . . . . .  5
   4.  Specification  . . . . . . . . . . . . . . . . . . . . . . . .  5
     4.1.  Cryptographic Function . . . . . . . . . . . . . . . . . .  5
     4.2.  ECCSI parameters . . . . . . . . . . . . . . . . . . . . .  6
     4.3.  Identity . . . . . . . . . . . . . . . . . . . . . . . . .  7
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
     6.1.  Experimental Status  . . . . . . . . . . . . . . . . . . .  9
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  9
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Appendix A.  Example . . . . . . . . . . . . . . . . . . . . . . . 11
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 15

Dearlove               Expires September 22, 2016               [Page 2]
Internet-Draft          Identity-Based Signatures             March 2016

1.  Introduction

   [RFC7182] defines ICV (integrity check value) TLVs for use in packets
   and messages that use the generalized MANET packet/message format
   defined in [RFC5444].  This specification extends the TLV definitions
   therein by defining two new cryptographic function code points from
   within the registries set up by [RFC7182].  This allows the use of an
   identity-based signature (IBS) as an ICV.  An IBS has an additional
   property that is not shared by all of the previously specified ICVs,
   it not only indicates that the protected packet or message is valid,
   but also verifies the originator of the packet/message.

   This specification assumes that each router (i.e., each originator of
   [RFC5444] format packets/messages) has an identity that may be tied
   to the packet or message.  The router may have more than one
   identity, but will only use one for each ICV TLV.  The cryptographic
   strength of the IBS is not dependent on the choice of identity.

Show full document text