[Rmt] RFC 6584 on Simple Authentication Schemes for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols

rfc-editor@rfc-editor.org Fri, 13 April 2012 18:02 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rmt@ietfa.amsl.com
Delivered-To: rmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4464511E8086; Fri, 13 Apr 2012 11:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.182
X-Spam-Level:
X-Spam-Status: No, score=-102.182 tagged_above=-999 required=5 tests=[AWL=-0.182, 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 mFrvP2Ygp-BK; Fri, 13 Apr 2012 11:02:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id D260111E8072; Fri, 13 Apr 2012 11:02:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3FDECB1E003; Fri, 13 Apr 2012 11:01:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120413180145.3FDECB1E003@rfc-editor.org>
Date: Fri, 13 Apr 2012 11:01:44 -0700 (PDT)
Cc: rmt@ietf.org, rfc-editor@rfc-editor.org
Subject: [Rmt] RFC 6584 on Simple Authentication Schemes for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmt>, <mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmt>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2012 18:02:29 -0000

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

        
        RFC 6584

        Title:      Simple Authentication Schemes for the 
                    Asynchronous Layered Coding (ALC) and NACK-Oriented 
                    Reliable Multicast (NORM) Protocols 
        Author:     V. Roca
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2012
        Mailbox:    vincent.roca@inria.fr
        Pages:      30
        Characters: 67466
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmt-simple-auth-for-alc-norm-06.txt

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

This document introduces four schemes that provide per-packet
authentication, integrity, and anti-replay services in the context of
the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable
Multicast (NORM) protocols.  The first scheme is based on RSA Digital
Signatures.  The second scheme relies on the Elliptic Curve Digital
Signature Algorithm (ECDSA).  The third scheme relies on a Group-
keyed Message Authentication Code (MAC).  Finally, the fourth scheme
merges the Digital Signature and group schemes.  These schemes have
different target use cases, and they do not all provide the same
service.  [STANDARDS-TRACK]

This document is a product of the Reliable Multicast Transport 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