[Anima] Last Call: (JWS signed Voucher Artifacts for Bootstrapping Protocols) to Proposed Standard
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'JWS signed Voucher Artifacts for Bootstrapping Protocols' as 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 last-c...@ietf.org mailing lists by 2024-10-14. 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. Abstract I-D.ietf-anima-rfc8366bis defines a digital artifact called voucher as a YANG-defined JSON document that is signed using a Cryptographic Message Syntax (CMS) structure. This document introduces a variant of the voucher artifact in which CMS is replaced by the JSON Object Signing and Encryption (JOSE) mechanism described in RFC7515 to support deployments in which JOSE is preferred over CMS. In addition to explaining how the format is created, the "application/voucher-jws+json" media type is registered and examples are provided. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-jws-voucher/ No IPR declarations have been submitted directly on this I-D. ___ Anima mailing list -- anima@ietf.org To unsubscribe send an email to anima-le...@ietf.org
[Anima] Protocol Action: 'BRSKI-AE: Alternative Enrollment Protocols in BRSKI' to Proposed Standard (draft-ietf-anima-brski-ae-13.txt)
The IESG has approved the following document: - 'BRSKI-AE: Alternative Enrollment Protocols in BRSKI' (draft-ietf-anima-brski-ae-13.txt) as Proposed Standard This document is the product of the Autonomic Networking Integrated Model and Approach Working Group. The IESG contact persons are Warren Kumari and Mahesh Jethanandani. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-brski-ae/ Technical Summary This document defines an enhancement of Bootstrapping Remote Secure Key Infrastructure (BRSKI, RFC 8995). It supports alternative certificate enrollment protocols, such as CMP, that use authenticated self-contained signed objects for certification messages. About This Document This note is to be removed before publishing as an RFC. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-ietf-anima-brski-ae/. Source for this draft and an issue tracker can be found at https://github.com/anima-wg/anima-brski-ae. Working Group Summary Was there anything in the WG process that is worth noting? For example, was there controversy about particular points or were there decisions where the consensus was particularly rough? Document Quality Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, Media Type, or other Expert Review, what was its course (briefly)? In the case of a Media Type Review, on what date was the request posted? Personnel The Document Shepherd for this document is Toerless Eckert. The Responsible Area Director is Mahesh Jethanandani. ___ Anima mailing list -- anima@ietf.org To unsubscribe send an email to anima-le...@ietf.org
[Anima] Last Call: (BRSKI-AE: Alternative Enrollment Protocols in BRSKI) to Proposed Standard
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'BRSKI-AE: Alternative Enrollment Protocols in BRSKI' as 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 last-c...@ietf.org mailing lists by 2024-06-19. 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. Abstract This document defines an enhancement of Bootstrapping Remote Secure Key Infrastructure (BRSKI, RFC 8995). It supports alternative certificate enrollment protocols, such as CMP, that use authenticated self-contained signed objects for certification messages. About This Document This note is to be removed before publishing as an RFC. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-ietf-anima-brski-ae/. Source for this draft and an issue tracker can be found at https://github.com/anima-wg/anima-brski-ae. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-brski-ae/ No IPR declarations have been submitted directly on this I-D. ___ Anima mailing list -- anima@ietf.org To unsubscribe send an email to anima-le...@ietf.org
[Anima] Last Call: (Constrained Join Proxy for Bootstrapping Protocols) to Proposed Standard
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'Constrained Join Proxy for Bootstrapping Protocols' as 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 last-c...@ietf.org mailing lists by 2022-04-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. Abstract This document defines a protocol to securely assign a Pledge to a domain, represented by a Registrar, using an intermediary node between Pledge and Registrar. This intermediary node is known as a "constrained Join Proxy". An enrolled Pledge can act as a constrained Join Proxy. This document extends the work of Bootstrapping Remote Secure Key Infrastructures (BRSKI) by replacing the Circuit-proxy between Pledge and Registrar by a stateless/stateful constrained Join Proxy. It relays join traffic from the Pledge to the Registrar. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-constrained-join-proxy/ No IPR declarations have been submitted directly on this I-D. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Document Action: 'Guidelines for Autonomic Service Agents' to Informational RFC (draft-ietf-anima-asa-guidelines-07.txt)
The IESG has approved the following document: - 'Guidelines for Autonomic Service Agents' (draft-ietf-anima-asa-guidelines-07.txt) as Informational RFC This document is the product of the Autonomic Networking Integrated Model and Approach Working Group. The IESG contact persons are Warren Kumari and Robert Wilton. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-asa-guidelines/ Technical Summary The ANIMA WG has defined a set of mechanisms through its RFCs most of whom where released earlier in 2021. One key benefit of these mechanisms is to make it easier to develop and deploy network automation software agents on network devices. These agents are called "Autonomic Service Agents" (ASA). This simplification is achieved through the autonomic services offered by ANIMAs "Autonomic Networking Infrastructure" and its services provided to those ASA. This document gives an overview of the structure of ASA and guidance for its interaction mechanisms with those services. These functions are primarily service (objective) interactions with other ASA via the ANI GRASP protocol, use of the ANI's ACP for any other secure communication between ASA and ASA Lifecycles. Working Group Summary This document was worked on and improved by several members of the WG for a long time (Since Sep 2016) without being adopted because work on ASA and potocols/mechanisms for them was out of charter for a long time. Most issues where resolved during this time, which is why the document only needed to receive few revisions after being adopted by the WG when the charter allowed for it. Document Quality This document is of an architectural/design nature. It predates significant implementation experience. It does not discuss any protocols but primarily use of abstract service interfaces within a network device. A simple proof of concept of some of the aspects described in this document was done by Brian Carpenter (co-author) Personnel Document Shepherd: Toerless Eckert Responsible AD: Rob Wilton (OPS). ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (Guidelines for Autonomic Service Agents) to Informational RFC
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'Guidelines for Autonomic Service Agents' as Informational RFC 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 last-c...@ietf.org mailing lists by 2021-12-13. 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. Abstract This document proposes guidelines for the design of Autonomic Service Agents for autonomic networks. Autonomic Service Agents, together with the Autonomic Network Infrastructure, the Autonomic Control Plane and the Generic Autonomic Signaling Protocol constitute base elements of a so-called autonomic networking ecosystem. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-asa-guidelines/ No IPR declarations have been submitted directly on this I-D. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Document Action: 'Generic Autonomic Signaling Protocol Application Program Interface (GRASP API)' to Informational RFC (draft-ietf-anima-grasp-api-10.txt)
The IESG has approved the following document: - 'Generic Autonomic Signaling Protocol Application Program Interface (GRASP API)' (draft-ietf-anima-grasp-api-10.txt) as Informational RFC This document is the product of the Autonomic Networking Integrated Model and Approach Working Group. The IESG contact persons are Warren Kumari and Robert Wilton. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-grasp-api/ Technical Summary This document is a conceptual outline of an application programming interface (API) for the Generic Autonomic Signaling Protocol (GRASP). Such an API is needed for Autonomic Service Agents (ASA) calling the GRASP protocol module to exchange autonomic network messages with other ASAs. Working Group Summary This document went through a relevant long document development period (20 months for individual document period, 30 month for WG document period). It has been reviewed well. Document Quality This document went through multiple reviews by multiple WG participants. There are at least two existing implementations. The document looks to be in good shape. Personnel Sheng Jiang is the document shepherd. Robert Wilton is the responsible AD. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Protocol Action: 'An Autonomic Control Plane (ACP)' to Proposed Standard (draft-ietf-anima-autonomic-control-plane-30.txt)
The IESG has approved the following document: - 'An Autonomic Control Plane (ACP)' (draft-ietf-anima-autonomic-control-plane-30.txt) as Proposed Standard This document is the product of the Autonomic Networking Integrated Model and Approach Working Group. The IESG contact persons are Warren Kumari, Robert Wilton and Éric Vyncke. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/ Technical Summary This document defines a so-called "Autonomic Control Plane", with the primary use as a control plane for autonomic functions. It is self-managing and zero configuration for basic scenarios. Working Group Summary This document was called draft-behringer-anima-autonomic-control-plane prior to its adoption. There was unanimous support for it in favor of adoption and none against, so this document was adopted in August 2015. There was interest in this work posts since its adoption. There was never any opposition for this work. This document went through a relevant long document development period (10 months for individual document period, 29 month for WG document period). It has been reviewed well. Document Quality This document went through multiple reviews by multiple participants. So far, there is no existing implementations. Personnel Sheng Jiang is the document shepherd. Éric Vyncke is the responsible AD. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (Generic Autonomic Signaling Protocol Application Program Interface (GRASP API)) to Informational RFC
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'Generic Autonomic Signaling Protocol Application Program Interface (GRASP API)' as Informational RFC 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 last-c...@ietf.org mailing lists by 2020-10-28. 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. Abstract This document is a conceptual outline of an application programming interface (API) for the Generic Autonomic Signaling Protocol (GRASP). Such an API is needed for Autonomic Service Agents (ASA) calling the GRASP protocol module to exchange autonomic network messages with other ASAs. Since GRASP is designed to support asynchronous operations, the API will need to be adapted to the support for asynchronicity in various programming languages and operating systems. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-grasp-api/ No IPR declarations have been submitted directly on this I-D. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Protocol Action: 'Bootstrapping Remote Secure Key Infrastructures (BRSKI)' to Proposed Standard (draft-ietf-anima-bootstrapping-keyinfra-41.txt)
The IESG has approved the following document: - 'Bootstrapping Remote Secure Key Infrastructures (BRSKI)' (draft-ietf-anima-bootstrapping-keyinfra-41.txt) as Proposed Standard This document is the product of the Autonomic Networking Integrated Model and Approach Working Group. The IESG contact persons are Warren Kumari and Robert Wilton. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/ Technical Summary This document specifies a mechanism for automated bootstrapping of an Autonomic Control Plane. To do this, a remote secure key infrastructure (BRSKI) is created using manufacturer installed X.509 certificate, in combination with a manufacturer's authorizing service, both online and offline. Support for lower security models, including devices with minimal identity, is described for legacy reasons but not encouraged Bootstrapping is complete when the cryptographic identity of the new key infrastructure is successfully deployed to the device but the established secure connection can be used to deploy a locally issued certificate to the device as well. Working Group Summary The document has been through two IETF Last Calls as the first one resulted in significant and substantial changes to the proposed mechanisms. Working Group had sufficient interest from the community on evolving the document since 2016. One topic that raised controversy was the reliance of the proposed mechanism on the manufacturer’s identity management systems. The consensus was eventually reached on this topic. Document Quality There are indications of multiple independent implementations available and in progress, both open and closed source. The document went through multiple iterations of WG LCs by the core interest group, has received several directorate and Doctors’ reviews, and went through two IETF wide last calls. Personnel Document Shepherd is Toerless Eckert. Responsible Area Director is Ignas Bagdonas. Suggested IANA Designated Experts for newly created registries are Michael Richardson and Max Pritikin. IANA Note This document requests to add new entries to existing Well-known EST, PKIX, DNS Service Names, and MUD Extensions registries, as well as creating new registry for BRSKI Parameters. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (An Autonomic Control Plane (ACP)) to Proposed Standard
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'An Autonomic Control Plane (ACP)' as 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 last-c...@ietf.org mailing lists by 2020-04-21. 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. Abstract Autonomic functions need a control plane to communicate, which depends on some addressing and routing. This Autonomic Control Plane should ideally be self-managing, and as independent as possible of configuration. This document defines such a plane and calls it the "Autonomic Control Plane", with the primary use as a control plane for autonomic functions. It also serves as a "virtual out-of-band channel" for Operations, Administration and Management (OAM) communications over a network that provides automatically configured hop-by-hop authenticated and encrypted communications via automatically configured IPv6 even when the network is not configured, or misconfigured. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/ballot/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/2407/ ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] WG Action: Rechartered Autonomic Networking Integrated Model and Approach (anima)
The Autonomic Networking Integrated Model and Approach (anima) WG in the Operations and Management Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the WG Chairs. Autonomic Networking Integrated Model and Approach (anima) --- Current status: Active WG Chairs: Toerless Eckert Sheng Jiang Assigned Area Director: Ignas Bagdonas Operations and Management Area Directors: Warren Kumari Ignas Bagdonas Technical advisors: Nancy Cam-Winget Mailing list: Address: anima@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/anima Archive: https://mailarchive.ietf.org/arch/browse/anima/ Group page: https://datatracker.ietf.org/group/anima/ Charter: https://datatracker.ietf.org/doc/charter-ietf-anima/ The Autonomic Networking Integrated Model and Approach (ANIMA) working group develops and maintains specifications and documentation for interoperable protocols and procedures for automated network management and control of professionally-managed networks. The vision is a network that configures, heals, optimizes and protects itself. The strategy is the incremental introduction of components to smoothly evolve existing and new networks accordingly. ANIMA work will rely on the framework described in draft-ietf-anima-reference-model already approved for publication. Work not related to this framework is welcome for review, but WG adoption of such work requires explicit rechartering. The two concrete areas of the reference model are (1) the Autonomic Networking Infrastructure (ANI), and (2) Autonomic Functions (AF) built from software modules called Autonomic Service Agents (ASA). The ANI is specified through prior ANIMA work. It is composed of the Autonomic Control Plane (ACP; RFC 8368), Bootstrap over Secure Key Infrastructures (BRSKI) including Vouchers (RFC8366), and the Generic Autonomic Signaling Protocol (GRASP). ANIMA will work on closing gaps and extending the ANI and its components. ANIMA will start to define Autonomic Functions (AF) to enable service automation in networks; it will also work on generic aspects of ASA including design guidelines and lifecycle management, coordination and dependency management. The reference model also discusses Intent, but ANIMA will not work on this without explicit rechartering. It will rely on the Network Management Research Group (NMRG) to define the next steps for this topic. ANIMA will coordinate with other IETF and IRTF groups as needed. The scope of possible work items are (additional works are subject to extra approval from the responsible AD): - Extensions to the ANI, including variations of ANI deployment (e.g. in virtualised environments), information distribution within an AN, ANI OAMP interfaces (Operations, Administration, Management, Provisioning), interaction with YANG-based mechanisms, defining the domain boundary and membership management of the domain. - Support for Autonomic Service Agents, including design and implementation guidelines for ASAs, life cycle management, authorization and coordination of ASA. - BRSKI features, including proxies, enrollment, adaptions over various network protocols, variations of voucher formats. - Generic use cases of Autonomic Network and new GRASP extensions/options for them, including bulk transfer, DNS-SD interworking, autonomic resource management, autonomic SLA assurance, autonomic multi-tenant management, autonomic network measurement. - Integration with Network Operations Centers (NOCs), including autonomic discovery/connectivity to NOC, YANG-based ANI/ASA management by the NOC and reporting AF from node to NOC. Milestones: Nov 2019 - Submit Information distribution over GRASP to the IESG Dec 2019 - Submit Constrained Voucher Artifacts for Bootstrapping Protocols to the IESG Dec 2019 - Submit Constrained Join Proxy for Bootstrapping Protocols to the IESG Mar 2020 - Submit Lifecycle and Management of Autonomic Service Agents to the IESG Mar 2020 - Submit Guidelines for Developing Autonomic Service Agents to the IESG Jul 2020 - Recharter or close the WG ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] WG Review: Autonomic Networking Integrated Model and Approach (anima)
The Autonomic Networking Integrated Model and Approach (anima) WG in the Operations and Management Area of the IETF is undergoing rechartering. The IESG has not made any determination yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (i...@ietf.org) by 2019-08-30. Autonomic Networking Integrated Model and Approach (anima) --- Current status: Active WG Chairs: Toerless Eckert Sheng Jiang Assigned Area Director: Ignas Bagdonas Operations and Management Area Directors: Warren Kumari Ignas Bagdonas Technical advisors: Nancy Cam-Winget Mailing list: Address: anima@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/anima Archive: https://mailarchive.ietf.org/arch/browse/anima/ Group page: https://datatracker.ietf.org/group/anima/ Charter: https://datatracker.ietf.org/doc/charter-ietf-anima/ The Autonomic Networking Integrated Model and Approach (ANIMA) working group develops and maintains specifications and documentation for interoperable protocols and procedures for automated network management and control of professionally-managed networks. The vision is a network that configures, heals, optimizes and protects itself. The strategy is the incremental introduction of components to smoothly evolve existing and new networks accordingly. ANIMA work will rely on the framework described in draft-ietf-anima-reference-model already approved for publication. Work not related to this framework is welcome for review, but WG adoption of such work requires explicit rechartering. The two concrete areas of the reference model are (1) the Autonomic Networking Infrastructure (ANI), and (2) Autonomic Functions (AF) built from software modules called Autonomic Service Agents (ASA). The ANI is specified through prior ANIMA work. It is composed of the Autonomic Control Plane (ACP; RFC 8368), Bootstrap over Secure Key Infrastructures (BRSKI) including Vouchers (RFC8366), and the Generic Autonomic Signaling Protocol (GRASP). ANIMA will work on closing gaps and extending the ANI and its components. ANIMA will start to define Autonomic Functions (AF) to enable service automation in networks; it will also work on generic aspects of ASA including design guidelines and lifecycle management, coordination and dependency management. The reference model also discusses Intent, but ANIMA will not work on this without explicit rechartering. It will rely on the Network Management Research Group (NMRG) to define the next steps for this topic. ANIMA will coordinate with other IETF and IRTF groups as needed. The scope of possible work items are (additional works are subject to extra approval from the responsible AD): - Extensions to the ANI, including variations of ANI deployment (e.g. in virtualised environments), information distribution within an AN, ANI OAMP interfaces (Operations, Administration, Management, Provisioning), interaction with YANG-based mechanisms, defining the domain boundary and membership management of the domain. - Support for Autonomic Service Agents, including design and implementation guidelines for ASAs, life cycle management, authorization and coordination of ASA. - BRSKI features, including proxies, enrollment, adaptions over various network protocols, variations of voucher formats. - Generic use cases of Autonomic Network and new GRASP extensions/options for them, including bulk transfer, DNS-SD interworking, autonomic resource management, autonomic SLA assurance, autonomic multi-tenant management, autonomic network measurement. - Integration with Network Operations Centers (NOCs), including autonomic discovery/connectivity to NOC, YANG-based ANI/ASA management by the NOC and reporting AF from node to NOC. Milestones: Nov 2019 - Submit Information distribution over GRASP to the IESG Dec 2019 - Submit Constrained Voucher Artifacts for Bootstrapping Protocols to the IESG Dec 2019 - Submit Constrained Join Proxy for Bootstrapping Protocols to the IESG Mar 2020 - Submit Lifecycle and Management of Autonomic Service Agents to the IESG Mar 2020 - Submit Guidelines for Developing Autonomic Service Agents to the IESG Jul 2020 - Recharter or close the WG ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (Bootstrapping Remote Secure Key Infrastructures (BRSKI)) to Proposed Standard
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'Bootstrapping Remote Secure Key Infrastructures (BRSKI)' as Proposed Standard This is a second Last Call. IoT Directorate review was done after the ANIMA WG Last Call and consensus to request the publication, and that review resulted in substantial changes to the document. 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 2019-06-04. 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. Abstract This document specifies automated bootstrapping of an Autonomic Control Plane. To do this a remote secure key infrastructure (BRSKI) is created using manufacturer installed X.509 certificate, in combination with a manufacturer's authorizing service, both online and offline. Bootstrapping a new device can occur using a routable address and a cloud service, or using only link-local connectivity, or on limited/disconnected networks. Support for lower security models, including devices with minimal identity, is described for legacy reasons but not encouraged. Bootstrapping is complete when the cryptographic identity of the new key infrastructure is successfully deployed to the device but the established secure connection can be used to deploy a locally issued certificate to the device as well. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/ballot/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/2816/ https://datatracker.ietf.org/ipr/3233/ https://datatracker.ietf.org/ipr/2463/ The document contains these normative downward references. See RFC 3967 for additional information: rfc8368: Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM) (Informational - IETF stream) ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Document Action: 'A Reference Model for Autonomic Networking' to Informational RFC (draft-ietf-anima-reference-model-10.txt)
The IESG has approved the following document: - 'A Reference Model for Autonomic Networking' (draft-ietf-anima-reference-model-10.txt) as Informational RFC This document is the product of the Autonomic Networking Integrated Model and Approach Working Group. The IESG contact persons are Warren Kumari and Ignas Bagdonas. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-reference-model/ Technical Summary This document defines a reference model for RFC7575 based Autonomic Networks, with the focus on how autonomic and traditional network nodes could coexist and operate and be managed together. This document focuses on an initial phases of autonomic network deployments, relying for its operation on existence of at least portions of fully managed non-autonomic network domains. Networks consisting only of autonomic nodes are explicitly out of scope due to much stringent security and trust aspects needed to be covered. Working Group Summary The document has been through several WG reviews and WG last calls. No major disagreement points were discovered during the process, there is a strong consensus with the WG on the contents of the document. Document Quality The deliverable of this document is not directly a protocol, but a set of guidelines on how both systems and networks implementing autonomic functionality should be built and deployed. Some use cases described in the document have shipping implementations. Overall there is an interest within operator community for autonomic network functionality. Personnel Document Shepherd is Sheng Jiang. Responsible AD is Ignas Bagdonas. No IANA experts are needed for this document as there are no registries defined or modified. IANA Note This document contains no actions for IANA. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (Bootstrapping Remote Secure Key Infrastructures (BRSKI)) to Proposed Standard
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'Bootstrapping Remote Secure Key Infrastructures (BRSKI)' as 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 2018-10-02. 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. Abstract This document specifies automated bootstrapping of a remote secure key infrastructure (BRSKI) using manufacturer installed X.509 certificate, in combination with a manufacturer's authorizing service, both online and offline. Bootstrapping a new device can occur using a routable address and a cloud service, or using only link-local connectivity, or on limited/disconnected networks. Support for lower security models, including devices with minimal identity, is described for legacy reasons but not encouraged. Bootstrapping is complete when the cryptographic identity of the new key infrastructure is successfully deployed to the device but the established secure connection can be used to deploy a locally issued certificate to the device as well. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/ballot/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/2816/ https://datatracker.ietf.org/ipr/3233/ https://datatracker.ietf.org/ipr/2463/ The document contains these normative downward references. See RFC 3967 for additional information: rfc3542: Advanced Sockets Application Program Interface (API) for IPv6 (Informational - IETF stream) rfc7228: Terminology for Constrained-Node Networks (Informational - IETF stream) ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (A Reference Model for Autonomic Networking) to Informational RFC
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'A Reference Model for Autonomic Networking' as Informational RFC 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 2018-08-21. 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. Abstract This document describes a reference model for Autonomic Networking. It defines the behaviour of an autonomic node, how the various elements in an autonomic context work together, and how autonomic services can use the infrastructure. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-reference-model/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-anima-reference-model/ballot/ No IPR declarations have been submitted directly on this I-D. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Document Action: 'Using Autonomic Control Plane for Stable Connectivity of Network OAM' to Informational RFC (draft-ietf-anima-stable-connectivity-10.txt)
The IESG has approved the following document: - 'Using Autonomic Control Plane for Stable Connectivity of Network OAM' (draft-ietf-anima-stable-connectivity-10.txt) as Informational RFC This document is the product of the Autonomic Networking Integrated Model and Approach Working Group. The IESG contact persons are Warren Kumari, Benoit Claise and Terry Manderson. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-stable-connectivity/ Technical Summary This document describes how to integrate OAM processes with the autonomic control plane (ACP) in Autonomic Networks (AN) in order to provide stable and secure connectivity for those OAM processes. Working Group Summary This document was called draft-eckert-anima-stable-connectivity prior to its adoption. There was unanimous support for it in favor of adoption and none against, so this document was adopted in December 2015. There was interest in this work posts since its adoption. There was never any opposition for this work. This document went through a relevant long document development period (12 months for individual document period, 22 month for WG document period). It has been reviewed well. Document Quality This document went through multiple reviews by multiple participants. So far, there is no existing implementations. Personnel Sheng Jiang is the document shepherd. Terry Manderson is the responsible AD. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Protocol Action: 'Voucher Profile for Bootstrapping Protocols' to Proposed Standard (draft-ietf-anima-voucher-07.txt)
The IESG has approved the following document: - 'Voucher Profile for Bootstrapping Protocols' (draft-ietf-anima-voucher-07.txt) as Proposed Standard This document is the product of the Autonomic Networking Integrated Model and Approach Working Group. The IESG contact persons are Warren Kumari, Benoit Claise and Terry Manderson. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-voucher/ Technical Summary This document defines a strategy to securely assign a pledge to an owner, using an artifact signed, directly or indirectly, by the pledge's manufacturer. This artifact is known as a "voucher". This document only defines the voucher artifact, leaving it to other documents to describe specialized protocols for accessing it. Working Group Summary This document was called draft-kwatsen-anima-voucher prior to its adoption. There was unanimous support for it in favor of adoption and none against), so this document was adopted in January, 2017, as a accompanying document along with another ANIMA WG document draft-ietf-anima-bootstrapping-keyinfra, which have been adopted in Auguest 2015. It is worthy to clarifying that this document is actually independent from draft-ietf-anima-bootstrapping-keyinfra. There was interest in this work posts since its adoption. There was never any opposition for this work. This document went through a relevant shorter document development period (3 months for individual document period, 8 month for WG document period). It has been reviewed well. Document Quality This document went through multiple reviews by multiple WGs (ANIMA, 6tisch, NETCONF) participants. And this document went through a cross-group WGLC, which did receive comments to help improving the document. So far, there is no existing implementations. Personnel Sheng Jiang is the document shepherd. Terry Manderson is the responsible AD. IANA Note IANA is asked to registers a URIs in the IETF XML registry: URI: urn:ietf:params:xml:ns:yang:ietf-voucher IANA is requested to registers a YANG module in the YANG Module Names registry: ietf-voucher. All the necessary information is in the IANA considerations document. It is clear enough that the IANA will be able to implement it. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (An Autonomic Control Plane (ACP)) to Proposed Standard
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'An Autonomic Control Plane (ACP)' as 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 2018-02-26. 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. Abstract Autonomic functions need a control plane to communicate, which depends on some addressing and routing. This Autonomic Management and Control Plane should ideally be self-managing, and as independent as possible of configuration. This document defines such a plane and calls it the "Autonomic Control Plane", with the primary use as a control plane for autonomic functions. It also serves as a "virtual out of band channel" for OAM (Operations Administration and Management) communications over a network that is secure and reliable even when the network is not configured, or not misconfigured. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/ballot/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/2407/ The document contains these normative downward references. See RFC 3967 for additional information: draft-behringer-anima-autonomic-control-plane: An Autonomic Control Plane (None - ) draft-carpenter-anima-ani-objectives: Technical Objective Formats for the Autonomic Network Infrastructure (None - ) draft-behringer-autonomic-control-plane: An Autonomic Control Plane (None - ) draft-ietf-roll-applicability-template: ROLL Applicability Statement Template (None - IETF stream) draft-behringer-anima-autonomic-addressing: An Autonomic IPv6 Addressing Scheme (None - ) ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Document Action: 'Autonomic IPv6 Edge Prefix Management in Large-scale Networks' to Informational RFC (draft-ietf-anima-prefix-management-07.txt)
The IESG has approved the following document: - 'Autonomic IPv6 Edge Prefix Management in Large-scale Networks' (draft-ietf-anima-prefix-management-07.txt) as Informational RFC This document is the product of the Autonomic Networking Integrated Model and Approach Working Group. The IESG contact persons are Warren Kumari, Benoit Claise and Terry Manderson. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-prefix-management/ Technical Summary Relevant content can frequently be found in the abstract This document describes an autonomic solution for IPv6 prefix management at the edge of large-scale ISP networks, with an extension to support IPv4 prefixes. An important purpose of the document is to use it for validation of the design of various components of the autonomic networking infrastructure. Working Group Summary This document was called draft-jiang-anima-prefix-management prior to its adoption. There was consenus support for it in favor of adoption, so this document was adopted in January 2016. There was interest in this work posts since its adoption. There was no opposition to this work. This document went through a relevant long document development period (15 months for individual document period, 30 month for WG document period). It has been reviewed well. Document Quality Huawei has expressed interest in implementation. There is a prototype implementation at: https://github.com/becarpenter/graspy/blob/master/pfxm3.pdf https://github.com/becarpenter/graspy/blob/master/pfxm3.py Personnel Toerless Eckert is the document shepherd. Terry Manderson is the responsible AD. IANA Note The IANA is requested to add two names to GRASP Objective Names Table registry defined by [I-D.ietf-anima-grasp] (registry already crated). "PrefixManager" and "PrefixManager.Params". I did review/discuss these names during shepherd review. I think these allocations establish a useful precedent of making multiple objectives of one functional area use a common prefix. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (Using Autonomic Control Plane for Stable Connectivity of Network OAM) to Informational RFC
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'Using Autonomic Control Plane for Stable Connectivity of Network OAM' as Informational RFC 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 2017-11-26. 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. Abstract OAM (Operations, Administration and Maintenance - as per BCP161, (RFC6291) processes for data networks are often subject to the problem of circular dependencies when relying on connectivity provided by the network to be managed for the OAM purposes. Provisioning while bringing up devices and networks tends to be more difficult to automate than service provisioning later on, changes in core network functions impacting reachability cannot be automated because of ongoing connectivity requirements for the OAM equipment itself, and widely used OAM protocols are not secure enough to be carried across the network without security concerns. This document describes how to integrate OAM processes with the autonomic control plane (ACP) in Autonomic Networks (AN) in order to provide stable and secure connectivity for those OAM processes. This connectivity is not subject to aforementioned circular dependencies. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-stable-connectivity/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-anima-stable-connectivity/ballot/ No IPR declarations have been submitted directly on this I-D. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (Voucher Profile for Bootstrapping Protocols) to Proposed Standard
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'Voucher Profile for Bootstrapping Protocols' as 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 2017-10-12. 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. Abstract This document defines a strategy to securely assign a pledge to an owner, using an artifact signed, directly or indirectly, by the pledge's manufacturer. This artifact is known as a "voucher". The voucher artifact is a YANG-defined JSON document that has (by default) been signed using a PKCS#7 structure. The voucher artifact is normally generated by the pledge's manufacturer or delegate (i.e. the Manufacturer Authorized Signing Authority). This document only defines the voucher artifact, leaving it to other documents to describe specialized protocols for accessing it. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-voucher/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-anima-voucher/ballot/ No IPR declarations have been submitted directly on this I-D. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (Autonomic IPv6 Edge Prefix Management in Large-scale Networks) to Informational RFC
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'Autonomic IPv6 Edge Prefix Management in Large-scale Networks' as Informational RFC 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 2017-10-12. 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. Abstract This document describes an autonomic solution for IPv6 prefix management at the edge of large-scale ISP networks, with an extension to support IPv4 prefixes. An important purpose of the document is to use it for validation of the design of various components of the autonomic networking infrastructure. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-prefix-management/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-anima-prefix-management/ballot/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/3026/ https://datatracker.ietf.org/ipr/3027/ ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Protocol Action: 'A Generic Autonomic Signaling Protocol (GRASP)' to Proposed Standard (draft-ietf-anima-grasp-15.txt)
The IESG has approved the following document: - 'A Generic Autonomic Signaling Protocol (GRASP)' (draft-ietf-anima-grasp-15.txt) as Proposed Standard This document is the product of the Autonomic Networking Integrated Model and Approach Working Group. The IESG contact persons are Warren Kumari, Benoit Claise and Terry Manderson. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-grasp/ Technical Summary This document describes the requirements for a signaling protocol that enables autonomic devices and autonomic service agents to dynamically discover peers, to synchronize state with them, and to negotiate parameter settings mutually with them. The document then defines a general protocol for discovery, synchronization and negotiation, which can be suitable for variable technical objectives. The technical objectives for specific scenarios out of scope. Working Group Summary This document was called draft-carpenter-anima-gdn-protocol prior to its adoption. There was unanimous support for it in favor of adoption and none against), so this document was adopted in August 2015. There was interest in this work posts since its adoption. There was never any opposition for this work. This document went through a relevant long document development period (10 months for individual document period, 17 month for WG document period). It has been reviewed well. Document Quality This document went through multiple reviews by multiple WG participants. There are at least two existing implementations. Both Cisco and Huawei showed interests to implement the specification Personnel Sheng Jiang is the document shepherd. Terry Manderson is the responsible AD. IANA Note IANA is asked to assign 2 multicast addresses for ALL_GRASP_NEIGHBOR multicast address (IPv6) and ALL_GRASP_NEIGHBOR multicast address (IPv4); 1 port for both UDP and TCP: GRASP_LISTEN_PORT. IANA is requested to create a GRASP Parameter Registry including two registry tables: the GRASP Messages and Options Table and the GRASP Objective Names Table. In the the GRASP Messages and Options Table, 18 intial values are assigned for M_NOOP, M_DISCOVERY, M_RESPONSE, M_REQ_NEG, M_REQ_SYN, M_NEGOTIATE, M_END, M_WAIT, M_SYNCH, M_FLOOD, M_INVALID, O_DIVERT, O_ACCEPT, O_DECLINE, O_IPv6_LOCATOR, O_IPv4_LOCATOR, O_FQDN_LOCATOR and O_URI_LOCATO. There is no initial value assigned in the GRASP Objective Names Table. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] Last Call: (A Generic Autonomic Signaling Protocol (GRASP)) to Proposed Standard
The IESG has received a request from the Autonomic Networking Integrated Model and Approach WG (anima) to consider the following document: - 'A Generic Autonomic Signaling Protocol (GRASP)' as 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 2017-03-02. 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. Abstract This document establishes requirements for a signaling protocol that enables autonomic devices and autonomic service agents to dynamically discover peers, to synchronize state with them, and to negotiate parameter settings mutually with them. The document then defines a general protocol for discovery, synchronization and negotiation, while the technical objectives for specific scenarios are to be described in separate documents. An Appendix briefly discusses existing protocols with comparable features. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-anima-grasp/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-anima-grasp/ballot/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: draft-greevenbosch-appsawg-cbor-cddl: CBOR data definition language (CDDL): a notational convention to express CBOR data structures (None - IETF stream) Note that some of these references may already be listed in the acceptable Downref Registry. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
