Identity-Based Signatures for MANET Routing Protocols
draft-ietf-manet-ibs-01
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (manet WG)
|
|
Author |
|
Christopher Dearlove
|
|
Last updated |
|
2014-07-24
|
|
Stream |
|
Internet Engineering Task Force (IETF)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Mobile Ad hoc Networking (MANET) C. Dearlove
Internet-Draft BAE Systems ATC
Updates: 7182 (if approved) July 24, 2014
Intended status: Standards Track
Expires: January 25, 2015
Identity-Based Signatures for MANET Routing Protocols
draft-ietf-manet-ibs-01
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 January 25, 2015.
Copyright Notice
Copyright (c) 2014 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
Dearlove Expires January 25, 2015 [Page 1]
Internet-Draft Identity-Based Signatures July 2014
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 . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . . 9
Appendix A. Example . . . . . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14
Dearlove Expires January 25, 2015 [Page 2]
Internet-Draft Identity-Based Signatures July 2014
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 that
allow the use of an identity-based signature (IBS) as an ICV. An IBS
has an additional property that is not shared by any 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 (protocol participant)
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 (the two code
points allocated). In the first the identity can be any octet
sequence (up to 255 octets) included in the ICV TLV. In the second,
Show full document text