NomCom 2010-2011: List of Willing Nominees has been Updated
Hi Folks, List of Willing Nominees has been updated: -- The second announced listing of willing nominees for the IETF open positions is now available at https://wiki.tools.ietf.org/group/nomcom/10/input/ In the past, such information was available only to a subset of the community. Now, for this NomCom, it is made available to everyone in the community and it is easy to obtain. How to access the list: --- To access the list (which is available to anyone), you will be asked to login. Any login you've used to subscribe to an IETF mailing list should work here. But if it doesn't, then you can easily obtain a username/password from tools.ietf.org as follows: Just select Get Passwd from the left margin and it will take you to the new login page. User name will be your email address and you can then request a password at this page http://trac.tools.ietf.org/newlogin Who is listed? -- The names you see are only the nominees who have accepted a nomination for one (or more) of the open IETF positions at this point in time. Since the Call for Nominations remains open until October 1, 2010, this list is expected to grow. Who is not listed? -- It is important to realize this list does not include the names of people who have been nominated for a position and who either (a) have not accepted a nomination or (b) may have accepted but have yet to be listed. If you sent an acceptance more than 24 hours ago, and are not listed please contact the NomCom chair. Additional Nominations needed: -- More nominations are needed, particularly for most IESG open positions. Self nomination is welcome. Nominations remain open until October 1. Instructions on how to nominate someone for one or more of the IETF open positions is found in the call for nominations at https://datatracker.ietf.org/ann/nomcom/2468/ The list of open positions can be found at: http://wiki.tools.ietf.org/group/nomcom/10/ Feedback: - The open list disclosure by this NomCom is to support the feedback process. NomCom can accept feedback at any time. Detailed instructions on submitting feedback will be posted in a separate message. If you wish to provide anonymous feedback, the chair and any of the members will be happy to handle this for you. The Nominating Committee chair can be reached at nomcom-ch...@ietf.org and the entire nominating committee can be reached at nomco...@ietf.org. The email addresses of individual NomCom members is also on the NomCom 2010-2011 pages a https://wiki.tools.ietf.org/group/nomcom/10/ Thank you, Thomas Walsh Chair, NomCom 2010-2011 nomcom-ch...@ietf.org twa...@juniper.net ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Second Last Call: draft-nottingham-http-link-header-10.txt (Web Linking) to Proposed Standard
The IESG has received a request from an individual submitter to consider the following document: - 'Web Linking' draft-nottingham-http-link-header-10.txt as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2010-10-08. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via https://datatracker.ietf.org/doc/draft-nottingham-http-link-header/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-nottingham-http-link-header/ The purpose of this Second Last Call is to confirm some late changes to the IANA procedure/registry. The following changes are proposed: In Section 6.2 (Link Relation Type Registry), add the 2nd paragraph that reads: The underlying registry data (e.g., the XML file) must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions (http://trustee.ietf.org/license-info). In Section 6.2.1 (Registering New Link Relation Types), delete the following paragraph: When a registration request is successful, the Designated Expert(s) will update the registry XML file (using the format described in Appendix A including the MIT license) and send it to the link-relations-annou...@ietf.org mailing list (which SHOULD NOT be centrally archived, so as to avoid load issues from automated agents, and only accept posts from the Designated Expert(s)), so that implementers interested in receiving a machine-readable registry can do so. Simultaneously, they will send a text (not XML) version of the registry to IANA for publication. And finally, delete the whole Appendix A (together with A.1, which describes the Relax NG grammar) which reads: Appendix A. Link Relation Registry Format To facilitate applications that wish to use registry data in an automated fashion, this specification defines an XML-based format for the registry entries. Each registered relation type is represented by a RelationType element, and if any of the app data values are other than the default value identified in the Application Data registry, they will be represented by appdata elements. Note that this format is NOT that in which IANA publishes the registry, because doing so would subject IANA's servers to, potentially, very high load (e.g., if Web browsers were to automatically update their copies of the registry). Instead, this format is published to the link-relations-annou...@ietf.org mailing list, so that interested implementers can subscribe and distribute the machine-readable document using their own infrastructure. No IPR declarations were found that appear related to this I-D. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 6019 on BinaryTime: An Alternate Format for Representing Date and Time in ASN.1
A new Request for Comments is now available in online RFC libraries. RFC 6019 Title: BinaryTime: An Alternate Format for Representing Date and Time in ASN.1 Author: R. Housley Status: Standards Track Stream: IETF Date: September 2010 Mailbox:hous...@vigilsec.com Pages: 6 Characters: 11394 Obsoletes: RFC4049 URL:http://www.rfc-editor.org/rfc/rfc6019.txt This document specifies a new ASN.1 type for representing time: BinaryTime. This document also specifies an alternate to the signing-time attribute for use with the Cryptographic Message Syntax (CMS) SignedData and AuthenticatedData content types; the binary-signing-time attribute uses BinaryTime. CMS and the signing-time attribute are defined in RFC 5652. [STANDARDS TRACK] This is now a Proposed Standard Protocol. 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. 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-edi...@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 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
