Re: Second Last Call: rfc3852 (Cryptographic Message Syntax (CMS)) to Draft Standard

2009-04-28 Thread Nelson B Bolyard
The IESG wrote, On 2009-04-27 06:58 PDT: The IESG has received a request from the smime WG (smime) to consider the following document: - 'Cryptographic Message Syntax (CMS) ' RFC 3852 as a Draft Standard No technical issues were raised during the first Last Call. However, the Last

Re: Second Last Call: rfc3852 (Cryptographic Message Syntax (CMS)) to Draft Standard

2009-04-28 Thread Tim Polk
Nelson, I was referring to the maturity level as defined in RFC 2026, not the date of publication. For standards track specifications, Section 4.1 of RFC 2026 states Internet specifications go through stages of development, testing, and acceptance. Within the Internet Standards Process,

Re: Second Last Call: rfc3852 (Cryptographic Message Syntax (CMS)) to Draft Standard

2009-04-28 Thread Russ Housley
Nelson: The IESG has received a request from the smime WG (smime) to consider the following document: - 'Cryptographic Message Syntax (CMS) ' RFC 3852 as a Draft Standard No technical issues were raised during the first Last Call. However, the Last Call failed to highlight two

Re: Second Last Call: rfc3852 (Cryptographic Message Syntax (CMS)) to Draft Standard

2009-04-27 Thread Alexey Melnikov
The IESG wrote: The IESG has received a request from the smime WG (smime) to consider the following document: - 'Cryptographic Message Syntax (CMS) ' RFC 3852 as a Draft Standard No technical issues were raised during the first Last Call. However, the Last Call failed to highlight two

Re: Second Last Call: rfc3852 (Cryptographic Message Syntax (CMS)) to Draft Standard

2009-04-27 Thread Paul Hoffman
At 5:15 PM +0100 4/27/09, Alexey Melnikov wrote: The IESG wrote: The IESG has received a request from the smime WG (smime) to consider the following document: - 'Cryptographic Message Syntax (CMS) ' RFC 3852 as a Draft Standard No technical issues were raised during the first Last Call.

Re: Second Last Call: rfc3852 (Cryptographic Message Syntax (CMS)) to Draft Standard

2009-04-27 Thread John Leslie
Alexey Melnikov alexey.melni...@isode.com wrote: The IESG wrote: The IESG has received a request from the smime WG (smime) to consider the following document: - 'Cryptographic Message Syntax (CMS)' RFC 3852 as a Draft Standard This appeared on the agenda for last week's telechat, and

Re: Second Last Call: rfc3852 (Cryptographic Message Syntax (CMS)) to Draft Standard

2009-04-27 Thread Tim Polk
Alexey, The goal of this particular exercise is to advance RFC 3852 *without* revision, so I called out the normative references as specified in the document: RFCs 3280 and 3281. It is true that RFC 3280 has been obsoleted by RFC 5280, and that draft-ietf-pkix-3281update is intended to

Re: Second Last Call: rfc3852 (Cryptographic Message Syntax (CMS)) to Draft Standard

2009-04-27 Thread Alexey Melnikov
John Leslie wrote: Alexey Melnikov alexey.melni...@isode.com wrote: The IESG wrote: The IESG has received a request from the smime WG (smime) to consider the following document: - 'Cryptographic Message Syntax (CMS)' RFC 3852 as a Draft Standard This appeared on the agenda

Second Last Call: rfc3852 (Cryptographic Message Syntax (CMS)) to Draft Standard

2009-04-27 Thread The IESG
The IESG has received a request from the smime WG (smime) to consider the following document: - 'Cryptographic Message Syntax (CMS) ' RFC 3852 as a Draft Standard No technical issues were raised during the first Last Call. However, the Last Call failed to highlight two normative references