RFC 7859 on Identity-Based Signatures for Mobile Ad Hoc Network (MANET) Routing Protocols
rfc-editor@rfc-editor.org Wed, 25 May 2016 23:51 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2C9112DE64; Wed, 25 May 2016 16:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGDck26YCot6; Wed, 25 May 2016 16:51:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 531FD12DE37; Wed, 25 May 2016 16:50:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7A22218000C; Wed, 25 May 2016 16:49:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7859 on Identity-Based Signatures for Mobile Ad Hoc Network (MANET) Routing Protocols
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160525234953.7A22218000C@rfc-editor.org>
Date: Wed, 25 May 2016 16:49:53 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/-BhAwM6WI04ooqtz31E0zTSHNZQ>
Cc: drafts-update-ref@iana.org, manet@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 23:51:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7859
Title: Identity-Based Signatures for Mobile Ad
Hoc Network (MANET) Routing Protocols
Author: C. Dearlove
Status: Experimental
Stream: IETF
Date: May 2016
Mailbox: chris.dearlove@baesystems.com
Pages: 17
Characters: 36651
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-manet-ibs-05.txt
URL: https://www.rfc-editor.org/info/rfc7859
DOI: http://dx.doi.org/10.17487/RFC7859
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.
This document is a product of the Mobile Ad-hoc Networks Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC