The slides will be in the IETF 90 proceedings. The minutes are at
Here is a dump of the BOF description:
UCAN (Approved for IETF 90)
However, human administrators will still want to influence the network and set policy. Where devices require such input, it should be provided in a highly abstract, network-wide form referred to as "intent".
Autonomic Networking focuses on self-management of network elements. An autonomic function works in a distributed way across various network elements, allowing however central guidance and reporting. Autonomic functions already exist today, for example IGP routing protocols such as OSPF. However, all such functions have their own discovery, messaging and security mechanisms.
To transform this somewhat abstract Autonomic Networking concept into concrete, realisable requirements, the first stage, undertaken in the IRTF, was to define terminology and design goals, and to derive a high-level gap analysis. To take this further, there is a need for several realistic and specific use cases that can be used as a reference and as a plausibility test for developing requirements. Therefore, this BoF collects and analyses use cases for Autonomic Networking. The goal is to find commonalities between various use cases, to be able to determine generic requirements for Autonomic Networking functions and to conclude whether there is scope for a common, generic Autonomic Networking Infrastructure for all autonomic functions.
The UCAN BOF is intended to expose several use cases to community review and to identify other possible use cases. Several use cases assume that some sort of general discovery and negotiation protocol is available. The goal of the UCAN BoF is NOT to develop solutions for the use cases listed. However, the type of solution envisaged, its design goals, and sketches of solution approaches will be covered.
The next stage will be to consolidate the use cases and to to extract common requirements for an autonomic infrastructure. These requirements are in the following areas:
Preliminary directions for possible protocol work are indicated in a problem statement (draft-jiang-config-negotiation-ps) and strawman protocol (draft-jiang-config-negotiation-protocol) but these are indicative only.
The content of this page was last updated on 2019-05-14. It was migrated from the old Trac wiki on 2023-01-30.