RFC Editor Report to the IETF
Greetings, The RFC Editor report to the IETF is available at ftp://ftp.rfc-editor.org/in-notes/IETFreports/2009/ietf75.pdf Please let us know if you have any questions. Thank you. RFC Editor ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: Protocol Action: 'Cryptographic Message Syntax (CMS)' to Draft Standard
The IESG has approved the following document: - 'Cryptographic Message Syntax (CMS) ' as a Draft Standard This document is the product of the S/MIME Mail Security Working Group. The IESG contact persons are Tim Polk and Pasi Eronen. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-smime-rfc3852bis-00.txt Technical Summary This document specifies the Cryptographic Message Syntax (CMS), which is used to digitally sign, digest, authenticate, or encrypt arbitrary message content. The content of this document is based on RFC 3852 but also incorporates errata and the clarifications previously published as RFC 4853. Working Group Summary RFC 3852 was a product of the smime working group. CMS is widely referenced, and is a key building block for specifications developed by the S/MIME, ltans, and keyprov working groups. Document Quality Two or more interoperable implementations have been identified for all features. The implementation report is available at: http://www.ietf.org/iesg/implementation/report-rfc3852.txt Personnel Tim Polk is the responsible Area Director ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Cryptographic Message Syntax (CMS)' to Draft Standard
The IESG has approved the following document: - 'Cryptographic Message Syntax (CMS) ' as a Draft Standard This document is the product of the S/MIME Mail Security Working Group. The IESG contact persons are Tim Polk and Pasi Eronen. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-smime-rfc3852bis-00.txt Technical Summary This document specifies the Cryptographic Message Syntax (CMS), which is used to digitally sign, digest, authenticate, or encrypt arbitrary message content. The content of this document is based on RFC 3852 but also incorporates errata and the clarifications previously published as RFC 4853. Working Group Summary RFC 3852 was a product of the smime working group. CMS is widely referenced, and is a key building block for specifications developed by the S/MIME, ltans, and keyprov working groups. Document Quality Two or more interoperable implementations have been identified for all features. The implementation report is available at: http://www.ietf.org/IESG/Implementations/CMS-Interoperability-Report.txt Personnel Tim Polk is the responsible Area Director ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Document Action: 'Simple SIP Usage Scenario for Applications in the Endpoints' to Informational RFC
The IESG has approved the following document: - 'Simple SIP Usage Scenario for Applications in the Endpoints ' as an Informational RFC This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Cullen Jennings. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-sinnreich-sip-tools-07.txt Technical Summary This document describes a way of using a relatively small set of existing IETF standards to achieve a functionally simple unified communications system. Working Group Summary This is not a product of a working group. Document Quality Several people read this document and provided feedback. Personnel Cullen Jennings is the Responsible Area Director. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Document Action: 'Advanced Encryption Standard (AES) Key Wrap with Padding Algorithm' to Informational RFC
The IESG has approved the following document: - 'Advanced Encryption Standard (AES) Key Wrap with Padding Algorithm ' as an Informational RFC This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Tim Polk. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-housley-aes-key-wrap-with-pad-04.txt Technical Summary This document specifies a padding convention for use with the AES Key Wrap algorithm specified in RFC 3394. This convention eliminates the requirement that the length of the key to be wrapped is a multiple of 64 bits, allowing a key of any practical length to be wrapped. Working Group Summary This document is not the product of any IETF working group. Document Quality Expert reviews have not found any concerns. Personnel Russ Housley is the Document Shepherd for this document. Tim Polk is the Responsible Area Director. RFC Editor Note License Note: This document is being forwarded for publication assuming that the proposed update to the TLP will be completed by the IETF Trust prior to completion of the RFC publication process. If that process does not terminate successfully, please make the following substitution in both sections A.1 and A.2, replacing RFC with the number assigned to this RFC: OLD DEFINITIONS IMPLICIT TAGS ::= NEW DEFINITIONS IMPLICIT TAGS ::= -- Copyright (c) 2009 IETF Trust and the persons identified as -- authors of the code. All rights reserved. -- -- Redistribution and use in source and binary forms, with or without -- modification, are permitted provided that the following conditions -- are met: -- -- - Redistributions of source code must retain the above copyright -- notice, this list of conditions and the following disclaimer. -- -- - Redistributions in binary form must reproduce the above copyright -- notice, this list of conditions and the following disclaimer in -- the documentation and/or other materials provided with the -- distribution. -- -- - Neither the name of Internet Society, IETF or IETF Trust, nor the -- names of specific contributors, may be used to endorse or promote -- products derived from this software without specific prior -- written permission. -- -- -- -- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS -- 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT -- LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR -- A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT -- OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, -- SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT -- LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, -- DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY -- THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT -- (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE -- OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. -- -- This code is part of RFC ; see the RFC itself for full legal notices. -- -- ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'TCP Congestion Control' to Draft Standard
The IESG has approved the following document: - 'TCP Congestion Control ' as a Draft Standard This document is the product of the TCP Maintenance and Minor Extensions Working Group. The IESG contact persons are Lars Eggert and Magnus Westerlund. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-tcpm-rfc2581bis-07.txt Technical Summary The congestion control algorithms described in RFC 2581 are widely implemented and used. This document clarifies some specific points that have created questions for implementers in the past. Working Group Summary The working group saw the need for this document based on a small number of commonly recurring questions about what is meant by certain wordings in RFC2581. The working group was easily able to agree on the clarifications that this document provides. Document Quality The document was reviewed for quality by a large number of TCPM WG members. Personnel Wes Eddy (wesley.m.e...@nasa.gov) is the document shepherd. Lars Eggert (lars.egg...@nokia.com) reviewed the document for the IESG. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
