RFC 6025 on ASN.1 Translation

rfc-editor@rfc-editor.org Sat, 30 October 2010 02:05 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 65A443A679F; Fri, 29 Oct 2010 19:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.114
X-Spam-Level:
X-Spam-Status: No, score=-102.114 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_BAYES_5x7=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Do8pITembEdh; Fri, 29 Oct 2010 19:05:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 96E5C3A657C; Fri, 29 Oct 2010 19:05:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9EAD3E06E4; Fri, 29 Oct 2010 19:07:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6025 on ASN.1 Translation
From: rfc-editor@rfc-editor.org
Message-Id: <20101030020721.9EAD3E06E4@rfc-editor.org>
Date: Fri, 29 Oct 2010 19:07:21 -0700
Cc: pkix@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 30 Oct 2010 02:05:26 -0000

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

        
        RFC 6025

        Title:      ASN.1 Translation 
        Author:     C. Wallace, C. Gardiner
        Status:     Informational
        Stream:     IETF
        Date:       October 2010
        Mailbox:    cwallace@cygnacom.com, 
                    gardiner@bbn.com
        Pages:      19
        Characters: 39221
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pkix-asn1-translation-03.txt

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

Abstract Syntax Notation One (ASN.1) is widely used throughout the
IETF Security Area and has been for many years.  Some specifications
were written using a now deprecated version of ASN.1 and some were
written using the current version of ASN.1.  Not all ASN.1 compilers
support both older and current syntax.  This document is intended to
provide guidance to specification authors and to implementers
converting ASN.1 modules from one version of ASN.1 to another version
without causing changes to the "bits on the wire".  This document
does not provide a comprehensive tutorial of any version of ASN.1.
Instead, it addresses ASN.1 features that are used in IETF Security
Area specifications with a focus on items that vary with the ASN.1
version.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.

This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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