Subject: [YANG] capability-stmt

From: Andy Bierman <[email-masked]>
Date: Fri, 25 Jan 2008 07:58:53 -0800

Hi,

IMO, the concept of capability-based features is one of the
important components of NETCONF, but 2 new standard mechanisms are needed
to make it better:

  A) definition of a NETCONF capability in YANG
  B) standard data model containing the agent capabilities (for <get>)

A) capability-stmt (allowed at top-level only, like error-stmt)

    capability identifier-str {
      [description-stmt]
      [reference-stmt]
      [status-stmt]
       uri-stmt
    }

    capability uri {
        description
            "The NETCONF peer has the ability to accept the 'url' element in
             'source' and 'target' parameters.  The capability is further
             identified by URL arguments indicating the URL schemes supported.";
        reference "RFC 4741";
        status current;
        uri "urn:ietf:params:netconf:capability:url:1.0";
    }

    The capability statement serves as a documentation mechanism to describe
    any capabilities associated with the data model or NETCONF protocol.  The agent
    is required to advertise the capability if it is supported (per RFC 4741)
    and also required to support the agent-capabilities data model for <get>
    retrieval.

B) agent-capabilities DM

    This data model (whatever it is called) is already under development
    in the NETCONF WG within the NETCONF Monitoring data model.  This object
    must be supported by the agent (NETCONF 1.1?)

Comments?

_______________________________________________
YANG mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/yang