
From wwwrun@rfc-editor.org  Fri Jan 10 15:27:19 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB81B1AD190 for <smime@ietfa.amsl.com>; Fri, 10 Jan 2014 15:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 gzrjV8_2u7XS for <smime@ietfa.amsl.com>; Fri, 10 Jan 2014 15:27:16 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 131741ACC88 for <smime@ietf.org>; Fri, 10 Jan 2014 15:27:16 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 192777FC158; Fri, 10 Jan 2014 15:27:06 -0800 (PST)
To: khopri@kisa.or.kr, sjlee@kisa.or.kr, jykim@kisa.or.kr, jilee@kisa.or.kr, stephen.farrell@cs.tcd.ie, turners@ieca.com, paul.hoffman@vpnc.org, blaker@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140110232706.192777FC158@rfc-editor.org>
Date: Fri, 10 Jan 2014 15:27:06 -0800 (PST)
Cc: rfc-editor@rfc-editor.org, smime@ietf.org
Subject: [smime] [Technical Errata Reported] RFC4010 (3865)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime/>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 23:27:20 -0000

The following errata report has been submitted for RFC4010,
"Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4010&eid=3865

--------------------------------------
Type: Technical
Reported by: Russ Housley <housley@vigilsec.com>

Section: Appendix A.

Original Text
-------------
     SeedEncryptionAlgorithmInCMS
         { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
           pkcs9(9) smime(16) modules(0) id-mod-cms-seed(24) }


Corrected Text
--------------
     SeedEncryptionAlgorithmInCMS
         { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
           pkcs9(9) smime(16) modules(0) id-mod-cms-seed(25) }


Notes
-----
The value assigned for id-mod-cms-seed in 25, not 24.  This error will not impact interoperability, but it could impact developers using some ASN.1 tools.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC4010 (draft-ietf-smime-cms-seed-02)
--------------------------------------
Title               : Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS)
Publication Date    : February 2005
Author(s)           : J. Park, S. Lee, J. Kim, J. Lee
Category            : PROPOSED STANDARD
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG

From wwwrun@rfc-editor.org  Sun Jan 12 14:29:53 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19F851A1F56; Sun, 12 Jan 2014 14:29:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 4f8ePMPDW3cU; Sun, 12 Jan 2014 14:29:51 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id C6FB21A1F3F; Sun, 12 Jan 2014 14:29:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1539C7FC175; Sun, 12 Jan 2014 14:29:40 -0800 (PST)
To: housley@vigilsec.com, khopri@kisa.or.kr, sjlee@kisa.or.kr, jykim@kisa.or.kr, jilee@kisa.or.kr
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140112222940.1539C7FC175@rfc-editor.org>
Date: Sun, 12 Jan 2014 14:29:40 -0800 (PST)
Cc: rfc-editor@rfc-editor.org, iesg@ietf.org, smime@ietf.org
Subject: [smime] [Errata Verified] RFC4010 (3865)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime/>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jan 2014 22:29:53 -0000

The following errata report has been verified for RFC4010,
"Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS)". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4010&eid=3865

--------------------------------------
Status: Verified
Type: Technical

Reported by: Russ Housley <housley@vigilsec.com>
Date Reported: 2014-01-10
Verified by: Sean Turner (IESG)

Section: Appendix A.

Original Text
-------------
     SeedEncryptionAlgorithmInCMS
         { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
           pkcs9(9) smime(16) modules(0) id-mod-cms-seed(24) }


Corrected Text
--------------
     SeedEncryptionAlgorithmInCMS
         { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
           pkcs9(9) smime(16) modules(0) id-mod-cms-seed(25) }


Notes
-----
The value assigned for id-mod-cms-seed in 25, not 24.  This error will not impact interoperability, but it could impact developers using some ASN.1 tools.

--------------------------------------
RFC4010 (draft-ietf-smime-cms-seed-02)
--------------------------------------
Title               : Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS)
Publication Date    : February 2005
Author(s)           : J. Park, S. Lee, J. Kim, J. Lee
Category            : PROPOSED STANDARD
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG

From alexey.melnikov@isode.com  Wed Jan 15 06:07:12 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 970761AE0D7 for <smime@ietfa.amsl.com>; Wed, 15 Jan 2014 06:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
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 6KESfIwleud7 for <smime@ietfa.amsl.com>; Wed, 15 Jan 2014 06:07:10 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 4D6691AE37C for <smime@ietf.org>; Wed, 15 Jan 2014 06:07:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1389794818; d=isode.com; s=selector; i=@isode.com; bh=dvL8YWtysw4MXk92s8af3F9AxxGcYoe2xmI2UgzhPQQ=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=R70MMfzPhIQuOt6qw2zP/H6HCy2lXmJCN2rrUcJw3SrapsFXOBTAVCR1DU9o/mVgYbfoD2 wzMadYd8ws+p1PXHHWCP8M/9mu5vgyM5CTPjUB/XSk9RX55HXa8RDqbengKSdBHU8UtSCY OgaDkJ4CH9Svuqjhbh5DZ2hgsflTeuI=;
Received: from [172.16.1.29] (richard.isode.com [62.3.217.249])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UtaV=wAIP52a@waldorf.isode.com>; Wed, 15 Jan 2014 14:06:58 +0000
Message-ID: <52D69605.7010809@isode.com>
Date: Wed, 15 Jan 2014 14:07:01 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
To: smime@ietf.org
References: <20140114193639.17836.64885.idtracker@ietfa.amsl.com>
In-Reply-To: <20140114193639.17836.64885.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140114193639.17836.64885.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [smime] Fwd: I-D Action: draft-melnikov-smime-msa-to-mda-02.txt
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime/>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 14:07:12 -0000

Hi,
I've posted a new version of the document describing how MSA/MTA can 
sign/encrypt messages with S/MIME. This is effectively an update to 
Experimental RFC 3183. Changes from RFC 3183 are:

1) The draft only includes domain signatures from RFC 3183 (i.e. 
Additional Attributes Signatures and Review Signatures are not mentioned).
2) Naming conventions for X.509 certificates were simplified. Unlike RFC 
3183, subject names of domain signing/encrypting X.509 certificates 
don't have to have a specific form. But Subject Alternative Names need 
to include URIs for domain being protected.
3) Incorporated erratum 3757 resolution.
4) Updated references and some minor editorial corrections.

I would be happy to hear comments/see reviews of the draft.

Thank you,
Alexey

-------- Original Message --------
Subject: 	I-D Action: draft-melnikov-smime-msa-to-mda-02.txt
Date: 	Tue, 14 Jan 2014 11:36:39 -0800
From: 	internet-drafts@ietf.org
Reply-To: 	internet-drafts@ietf.org
To: 	i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts directories.


         Title           : MSA and MTA S/MIME signing & encryption
         Authors         : William Ottaway
                           Alexey Melnikov
	Filename        : draft-melnikov-smime-msa-to-mda-02.txt
	Pages           : 20
	Date            : 2014-01-14

Abstract:
    This document specifies how S/MIME signing and encryption can be
    applied between a Message Submission Agent (MSA) and a Message
    Delivery Agent (MDA) or between 2 Message Transfer Agents (MTA).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-melnikov-smime-msa-to-mda/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-melnikov-smime-msa-to-mda-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-melnikov-smime-msa-to-mda-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From wwwrun@rfc-editor.org  Thu Jan 16 00:49:26 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC95B1ADFE5 for <smime@ietfa.amsl.com>; Thu, 16 Jan 2014 00:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 mzZhxmwZaS2b for <smime@ietfa.amsl.com>; Thu, 16 Jan 2014 00:49:25 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 65B511A8032 for <smime@ietf.org>; Thu, 16 Jan 2014 00:49:25 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6E1067FC39A; Thu, 16 Jan 2014 00:49:13 -0800 (PST)
To: housley@vigilsec.com, stephen.farrell@cs.tcd.ie, turners@ieca.com, paul.hoffman@vpnc.org, blaker@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140116084913.6E1067FC39A@rfc-editor.org>
Date: Thu, 16 Jan 2014 00:49:13 -0800 (PST)
Cc: rfc-editor@rfc-editor.org, smime@ietf.org, jos.breek@ul.com
Subject: [smime] [Technical Errata Reported] RFC5652 (3867)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime/>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 08:49:26 -0000

The following errata report has been submitted for RFC5652,
"Cryptographic Message Syntax (CMS)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5652&eid=3867

--------------------------------------
Type: Technical
Reported by: Jos Breek <jos.breek@ul.com>

Section: 5.3

Original Text
-------------
digestAlgorithm identifies the message digest algorithm, and any
associated parameters, used by the signer.

Corrected Text
--------------
digestAlgorithm identifies the message digest algorithm, and any
associated parameters, used by the signer in the signature Generation 
Process. The message digest algorithm shall be equal to the message 
digest algorithm used in the signatureAlgorithm field.

Notes
-----
The text stated that the message digest algorithm is "used by the signer". It is unclear for what purpose the message digest algorithm is used. 

There are implementations that use the message digest algorithm specified in the messageDigest field instead of the message digest algorithm specified in the signatureAlgorithm.

Is the purpose of the messageDigest field to nest the hashing algorithm used in the signing process? If so, please use the corrected text to clarify the goal of the field.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5652 (draft-ietf-smime-rfc3852bis-00)
--------------------------------------
Title               : Cryptographic Message Syntax (CMS)
Publication Date    : September 2009
Author(s)           : R. Housley
Category            : DRAFT STANDARD
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG

From housley@vigilsec.com  Wed Jan 29 13:57:57 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD9691A041A for <smime@ietfa.amsl.com>; Wed, 29 Jan 2014 13:57:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 M8OxDD6PwjKs for <smime@ietfa.amsl.com>; Wed, 29 Jan 2014 13:57:55 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 8ABE01A03FF for <smime@ietf.org>; Wed, 29 Jan 2014 13:57:55 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id AA1BF9A42C4 for <smime@ietf.org>; Wed, 29 Jan 2014 16:57:42 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id vm6UWbimbx8h for <smime@ietf.org>; Wed, 29 Jan 2014 16:57:21 -0500 (EST)
Received: from [192.168.2.110] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 7E1269A42B4 for <smime@ietf.org>; Wed, 29 Jan 2014 16:57:21 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 29 Jan 2014 16:57:10 -0500
References: <20140129215021.F1FF27FC39B@rfc-editor.org>
To: IETF SMIME <smime@ietf.org>
Message-Id: <AB98C562-BC2D-4C3F-A066-7D5D2F757D96@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Subject: [smime] Fwd: RFC 7114 on Creation of a Registry for smime-type Parameter Values
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime/>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 21:57:58 -0000

Begin forwarded message:

> From: rfc-editor@rfc-editor.org
> Date: January 29, 2014 4:50:21 PM EST
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
> Subject: RFC 7114 on Creation of a Registry for smime-type Parameter =
Values
> Reply-To: ietf@ietf.org
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>=20
>        RFC 7114
>=20
>        Title:      Creation of a Registry for=20
>                    smime-type Parameter Values=20
>        Author:     B. Leiba
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       January 2014
>        Mailbox:    barryleiba@computer.org
>        Pages:      4
>        Characters: 7176
>        Updates/Obsoletes/SeeAlso:   None
>=20
>        I-D Tag:    draft-leiba-smime-type-registry-02.txt
>=20
>        URL:        http://www.rfc-editor.org/rfc/rfc7114.txt
>=20
> Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the
> Content-Type parameter "smime-type".  As the list of defined values
> for that parameter has increased, it has become clear that a registry
> is needed to document these values.  This document creates the
> registry, registers the current values, and specifies the policies
> for registration of new values.
>=20
> This is now a Proposed Standard.
>=20
> 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.
>=20
> 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
>=20
> For searching the RFC series, see =
http://www.rfc-editor.org/search/rfc_search.php
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>=20
> 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.
>=20
>=20
> The RFC Editor Team
> Association Management Solutions, LLC

