Identity-Based Signatures for Mobile Ad Hoc Network (MANET) Routing Protocols
RFC 7859

Document Type RFC - Experimental (May 2016; No errata)
Last updated 2016-05-25
Replaces draft-dearlove-manet-ibs
Stream IETF
Formats plain text pdf html 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
Internet Engineering Task Force (IETF)                       C. Dearlove
Request for Comments: 7859                                   BAE Systems
Category: Experimental                                          May 2016
ISSN: 2070-1721

                     Identity-Based Signatures for
            Mobile Ad Hoc Network (MANET) Routing Protocols

Abstract

   This document extends RFC 7182, 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 RFC
   5444.  It does so by defining an additional cryptographic function
   that allows the creation of an ICV that is an Identity-Based
   Signature (IBS), defined according to the Elliptic Curve-Based
   Certificateless Signatures for Identity-Based Encryption (ECCSI)
   algorithm specified in RFC 6507.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Engineering
   Task Force (IETF).  It represents the consensus of the IETF
   community.  It has received public review and has been approved for
   publication by the Internet Engineering Steering Group (IESG).  Not
   all documents approved by the IESG are a candidate for any level of
   Internet Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7859.

Dearlove                      Experimental                      [Page 1]
RFC 7859                Identity-Based Signatures               May 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
   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 . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
     6.1.  Experimental Status . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Appendix A.  Example  . . . . . . . . . . . . . . . . . . . . . .  12
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  17
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

Dearlove                      Experimental                      [Page 2]
RFC 7859                Identity-Based Signatures               May 2016

1.  Introduction

   [RFC7182] defines Integrity Check Value (ICV) 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.

   Two options for the choice of identity are supported (as reflected by
   the two code points allocated).  In the first option, the identity
Show full document text