[ltans] RFC 6283 on Extensible Markup Language Evidence Record Syntax (XMLERS)

rfc-editor@rfc-editor.org Tue, 19 July 2011 23:47 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ltans@ietfa.amsl.com
Delivered-To: ltans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D53CB21F84DC; Tue, 19 Jul 2011 16:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.157
X-Spam-Level:
X-Spam-Status: No, score=-102.157 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xCOAaVlKIKwj; Tue, 19 Jul 2011 16:47:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 7E89521F84D8; Tue, 19 Jul 2011 16:47:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7285D98C508; Tue, 19 Jul 2011 16:47:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110719234747.7285D98C508@rfc-editor.org>
Date: Tue, 19 Jul 2011 16:47:47 -0700 (PDT)
Cc: ltans@ietf.org, rfc-editor@rfc-editor.org
Subject: [ltans] RFC 6283 on Extensible Markup Language Evidence Record Syntax (XMLERS)
X-BeenThere: ltans@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: LTANS Working Group <ltans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ltans>, <mailto:ltans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltans>
List-Post: <mailto:ltans@ietf.org>
List-Help: <mailto:ltans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltans>, <mailto:ltans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 23:47:54 -0000

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

        
        RFC 6283

        Title:      Extensible Markup Language Evidence Record 
                    Syntax (XMLERS) 
        Author:     A. Jerman Blazic, S. Saljic,
                    T. Gondrom
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2011
        Mailbox:    aljosa@setcce.si, 
                    svetlana.saljic@setcce.si, 
                    tobias.gondrom@gondrom.org
        Pages:      43
        Characters: 99031
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ltans-xmlers-11.txt

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

In many scenarios, users must be able to demonstrate the (time of)
existence, integrity, and validity of data including signed data for
long or undetermined periods of time.  This document specifies XML
syntax and processing rules for creating evidence for long-term non-
repudiation of existence and integrity of data.  The Extensible Markup
Language Evidence Record Syntax XMLERS provides alternative syntax and
processing rules to the ASN.1 (Abstract Syntax Notation One) ERS
(Evidence Record Syntax) (RFC 4998) syntax by using XML.  [STANDARDS-TRACK]

This document is a product of the Long-Term Archive and Notary Services 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