NomCom 2023 Needs Your Feedback
Hi, The NomCom met yesterday decided to keep feedback open until 1200 Friday (CET). We hope to be able to make some decisions on Friday afternoon. Feedback is welcome in many forms: - The web: https://datatracker.ietf.org/nomcom/2023/feedback/ - Email: nomcom-2...@ietf.org - In person: The NomCom will be operating office hours during IETF 118 (see below). Look for NomCom members (we will have an orange dot on our badges). - Anonymously/indirectly: We don't have an anonymous feedback system, but any member of the IETF community can submit feedback on behalf of another person. I am happy to do this for you and have asked that NomCom members also offer to accept anonymous feedback. The NomCom has an office on the Lobby level of the Hilton if you want to come in person to provide feedback. The following times are when the London room is currently open (all Prague local time): Monday: 10:30-12:00, 13:00-16:30, 17:30-18:30 Tuesday: 08:30-09:30, 11:30-12:00, 15:00-15:30, 16:30-18:00 Wednesday: 09:30-10:30, 11:30-12:00, 14:00-14:30, 15:30-16:30 Thursday: 08:30-09:30, 11:30-12:00, 14:30-18:30 Friday: 08:30-12:00 Please knock if the door is closed. We might be interviewing or talking to someone. If you would like to reserve some of the above time in advance, send me a note. If the room is vacant, send me a note, I might be conducting interviews in the Brussels room next door. Thanks to everyone who has provided feedback already. The NomCom depends greatly on community feedback for making the best decisions. We treat all feedback as confidential. Thanks, Martin nomcom-chair-2...@ietf.org ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
IETF Chair and IESG Report to the Community for IETF 118
Hello, The IETF Chair and the IESG has uploaded their report to the community for IETF 118 to the datatracker. To access the full report: https://datatracker.ietf.org/meeting/118/materials/slides-118-ietf-sessb-ietf-chair-and-iesg-report-ietf-118-00 Hope to see you at IETF 118 either in person or online! Best regards, IESG Secretary on behalf of the IETF Chair and the IESG ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 9483 on Lightweight Certificate Management Protocol (CMP) Profile
A new Request for Comments is now available in online RFC libraries. RFC 9483 Title: Lightweight Certificate Management Protocol (CMP) Profile Author: H. Brockhaus, D. von Oheimb, S. Fries Status: Standards Track Stream: IETF Date: November 2023 Mailbox:hendrik.brockh...@siemens.com, david.von.ohe...@siemens.com, steffen.fr...@siemens.com Pages: 83 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-lamps-lightweight-cmp-profile-21.txt URL:https://www.rfc-editor.org/info/rfc9483 DOI:10.17487/RFC9483 This document aims at simple, interoperable, and automated PKI management operations covering typical use cases of industrial and Internet of Things (IoT) scenarios. This is achieved by profiling the Certificate Management Protocol (CMP), the related Certificate Request Message Format (CRMF), and transfer based on HTTP or Constrained Application Protocol (CoAP) in a succinct but sufficiently detailed and self-contained way. To make secure certificate management for simple scenarios and constrained devices as lightweight as possible, only the most crucial types of operations and options are specified as mandatory. More specialized or complex use cases are supported with optional features. This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. This is now a Proposed Standard. 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 Official Internet Protocol Standards (https://www.rfc-editor.org/standards) 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 https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk 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
RFC 9482 on Constrained Application Protocol (CoAP) Transfer for the Certificate Management Protocol
A new Request for Comments is now available in online RFC libraries. RFC 9482 Title: Constrained Application Protocol (CoAP) Transfer for the Certificate Management Protocol Author: M. Sahni, Ed., S. Tripathi, Ed. Status: Standards Track Stream: IETF Date: November 2023 Mailbox:msa...@paloaltonetworks.com, stripa...@paloaltonetworks.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ace-cmpv2-coap-transport-10.txt URL:https://www.rfc-editor.org/info/rfc9482 DOI:10.17487/RFC9482 This document specifies the use of the Constrained Application Protocol (CoAP) as a transfer mechanism for the Certificate Management Protocol (CMP). CMP defines the interaction between various PKI entities for the purpose of certificate creation and management. CoAP is an HTTP-like client-server protocol used by various constrained devices in the Internet of Things space. This document is a product of the Authentication and Authorization for Constrained Environments Working Group of the IETF. This is now a Proposed Standard. 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 Official Internet Protocol Standards (https://www.rfc-editor.org/standards) 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 https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk 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
RFC 9481 on Certificate Management Protocol (CMP) Algorithms
A new Request for Comments is now available in online RFC libraries. RFC 9481 Title: Certificate Management Protocol (CMP) Algorithms Author: H. Brockhaus, H. Aschauer, M. Ounsworth, J. Gray Status: Standards Track Stream: IETF Date: November 2023 Mailbox:hendrik.brockh...@siemens.com, hans.ascha...@siemens.com, mike.ounswo...@entrust.com, john.g...@entrust.com Pages: 28 Updates:RFC 4210 I-D Tag:draft-ietf-lamps-cmp-algorithms-15.txt URL:https://www.rfc-editor.org/info/rfc9481 DOI:10.17487/RFC9481 This document describes the conventions for using several cryptographic algorithms with the Certificate Management Protocol (CMP). CMP is used to enroll and further manage the lifecycle of X.509 certificates. This document also updates the algorithm use profile from Appendix D.2 of RFC 4210. This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. This is now a Proposed Standard. 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 Official Internet Protocol Standards (https://www.rfc-editor.org/standards) 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 https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk 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
RFC 9480 on Certificate Management Protocol (CMP) Updates
A new Request for Comments is now available in online RFC libraries. RFC 9480 Title: Certificate Management Protocol (CMP) Updates Author: H. Brockhaus, D. von Oheimb, J. Gray Status: Standards Track Stream: IETF Date: November 2023 Mailbox:hendrik.brockh...@siemens.com, david.von.ohe...@siemens.com, john.g...@entrust.com Pages: 55 Updates:RFC 4210, RFC 5912, RFC 6712 I-D Tag:draft-ietf-lamps-cmp-updates-23.txt URL:https://www.rfc-editor.org/info/rfc9480 DOI:10.17487/RFC9480 This document contains a set of updates to the syntax of Certificate Management Protocol (CMP) version 2 and its HTTP transfer mechanism. This document updates RFCs 4210, 5912, and 6712. The aspects of CMP updated in this document are using EnvelopedData instead of EncryptedValue, clarifying the handling of p10cr messages, improving the crypto agility, as well as adding new general message types, extended key usages to identify certificates for use with CMP, and well-known URI path segments. CMP version 3 is introduced to enable signaling support of EnvelopedData instead of EncryptedValue and signal the use of an explicit hash AlgorithmIdentifier in certConf messages, as far as needed. This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. This is now a Proposed Standard. 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 Official Internet Protocol Standards (https://www.rfc-editor.org/standards) 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 https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk 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
New Non-WG Mailing List: pdap (Personal Digital Agent Protocol)
A new IETF non-working group email list has been created. List address: p...@ietf.org Archive: https://mailarchive.ietf.org/arch/browse/pdap/ To subscribe: https://www.ietf.org/mailman/listinfo/pdap Purpose: The list will discuss and develop a charter for a new protocol workgroup designed to enable a shift from proprietary platforms to personal agents. Our perspective derives from the universal human right of Freedom of Association and Assembly (FAA). We leverage research on FAA in the IRTF HRPC and the IETF GNAP protocol now in Last Call. On top of this work, we will consider how a digital agent is hosted, how the agent is provisioned with authorization policies that are simultaneously human and machine-readable, and how entities, vendors, and other service providers are directed to access the agent. This list belongs to IETF area: ART For additional information, please contact the list administrators. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
