[manet] RFC 6622 on Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)

rfc-editor@rfc-editor.org Tue, 15 May 2012 00:04 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92A1A21F8971; Mon, 14 May 2012 17:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.115
X-Spam-Level:
X-Spam-Status: No, score=-102.115 tagged_above=-999 required=5 tests=[AWL=-0.115, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f9vR2zn0Lc-8; Mon, 14 May 2012 17:04:02 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD6721F8973; Mon, 14 May 2012 17:04:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8AC04B1E010; Mon, 14 May 2012 17:01:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120515000118.8AC04B1E010@rfc-editor.org>
Date: Mon, 14 May 2012 17:01:16 -0700
Cc: manet@ietf.org, rfc-editor@rfc-editor.org
Subject: [manet] RFC 6622 on Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 00:04:02 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6622

        Title:      Integrity Check Value and Timestamp 
                    TLV Definitions for Mobile Ad Hoc 
                    Networks (MANETs) 
        Author:     U. Herberg, T. Clausen
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2012
        Mailbox:    ulrich@herberg.name, 
                    T.Clausen@computer.org
        Pages:      21
        Characters: 48083
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-manet-packetbb-sec-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6622.txt

This document describes general and flexible TLVs for representing
cryptographic Integrity Check Values (ICVs) (i.e., digital signatures
or Message Authentication Codes (MACs)) as well as 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 an address, respectively.  [STANDARDS-TRACK]

This document is a product of the Mobile Ad-hoc Networks Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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