Re: Gen-ART LC Review of draft-ietf-mipshop-mos-dhcp-options-13

2009-04-28 Thread Jari Arkko
Thanks for your review! Authors, can you prepare a new version that addresses these issues? Jari Ben Campbell wrote: I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, please see

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: [ietf-dkim] Last Call: draft-ietf-dkim-rfc4871-errata (RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update) to Proposed Standard

2009-04-28 Thread Doug Otis
http://tools.ietf.org/html/draft-ietf-dkim-rfc4871-errata-04 Errata: Original Text: ,--- The tendency is to have the MUA highlight the address associated with this *signing identity* in some way, in an attempt to show the user the address from which the mail was sent. '--- Corrected Text:

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: Beyond reproach, accountability and regulation

2009-04-28 Thread Bernard Aboba
Here is a dictionary definition of Beyond reproach: Beyond reproach: So good as to preclude any possibility of criticism. Last time I looked, RFC 3777 did not include this definition as a requirement for the nomcom in selection of I* candidates. Good thing, too. We seem to have gotten by

Re: Beyond reproach, accountability and regulation

2009-04-28 Thread Joel Jaeggli
Bernard Aboba wrote: Here is a dictionary definition of Beyond reproach: Beyond reproach: So good as to preclude any possibility of criticism. Last time I looked, RFC 3777 did not include this definition as a requirement for the nomcom in selection of I* candidates. Good thing, too.

Last Call: draft-ietf-geopriv-sip-lo-retransmission (Implications of 'retransmission-allowed' for SIP Location Conveyance) to Informational RFC

2009-04-28 Thread The IESG
The IESG has received a request from the Geographic Location/Privacy WG (geopriv) to consider the following document: - 'Implications of 'retransmission-allowed' for SIP Location Conveyance ' draft-ietf-geopriv-sip-lo-retransmission-02.txt as an Informational RFC The IESG plans to make a

Protocol Action: 'Mobile IPv6 Support for Dual Stack Hosts and Routers' to Proposed Standard

2009-04-28 Thread The IESG
The IESG has approved the following document: - 'Mobile IPv6 Support for Dual Stack Hosts and Routers ' draft-ietf-mext-nemo-v4traversal-10.txt as a Proposed Standard This document is the product of the Mobility EXTensions for IPv6 Working Group. The IESG contact persons are Jari Arkko and

WG Action: Multiple Interfaces (mif)

2009-04-28 Thread IESG Secretary
A new IETF working group has been formed in the Internet Area. For additional information, please contact the Area Directors or the WG Chairs. Multiple Interfaces (mif) --- Current Status: Active Working Group Chairs: Margaret Wasserman

Protocol Action: 'Internet Calendaring and Scheduling Core Object Specification (iCalendar)' to Proposed Standard

2009-04-28 Thread The IESG
The IESG has approved the following document: - 'Internet Calendaring and Scheduling Core Object Specification (iCalendar) ' draft-ietf-calsify-rfc2445bis-10.txt as a Proposed Standard This document is the product of the Calendaring and Scheduling Standards Simplification Working Group.

Protocol Action: 'BGP IPsec Tunnel Encapsulation Attribute' to Proposed Standard

2009-04-28 Thread The IESG
The IESG has approved the following document: - 'BGP IPsec Tunnel Encapsulation Attribute ' draft-ietf-softwire-encaps-ipsec-03.txt as a Proposed Standard This document is the product of the Softwires Working Group. The IESG contact persons are Ralph Droms and Jari Arkko. A URL of this

WG Action: Locator/ID Separation Protocol (lisp)

2009-04-28 Thread IETF Secretariat
A new IETF working group has been formed in the Internet Area. For additional information, please contact the Area Directors or the WG Chairs. Locator/ID Separation Protocol (lisp) -- Last Modified: 2009-04-23 Current status: Working Group

75th IETF - Hotels

2009-04-28 Thread IETF Secretariat
75th IETF Meeting Stockholm, Sweden July 26-31, 2009 Host: .SE Be sure to make your reservation at one of the four Stockholm hotels where we have a block of rooms held. Cut-off dates for release of our block are earlier than usual. Hotel information can be found at:

RFC 5510 on Reed-Solomon Forward Error Correction (FEC) Schemes

2009-04-28 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 5510 Title: Reed-Solomon Forward Error Correction (FEC) Schemes Author: J. Lacan, V. Roca, J. Peltotalo, S. Peltotalo Status:

RFC 5511 on Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications

2009-04-28 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 5511 Title: Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications Author: A.

RFC 5520 on Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism

2009-04-28 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 5520 Title: Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism Author: R. Bradford, Ed.,

RFC 5521 on Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions

2009-04-28 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 5521 Title: Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions Author: E. Oki, T. Takeda,