[YANG] capability-stmt
Andy Bierman <ietf@andybierman.com> Fri, 25 January 2008 16:00 UTC
Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1JIQz9-0004JK-UU; Fri, 25 Jan 2008 11:00:55 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43)
id 1JIQz9-0004EX-3I
for yang-confirm+ok@megatron.ietf.org; Fri, 25 Jan 2008 11:00:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1JIQz8-0004AZ-MD
for yang@ietf.org; Fri, 25 Jan 2008 11:00:54 -0500
Received: from smtp118.sbc.mail.sp1.yahoo.com ([69.147.64.91])
by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JIQz8-0001I0-80
for yang@ietf.org; Fri, 25 Jan 2008 11:00:54 -0500
Received: (qmail 71691 invoked from network); 25 Jan 2008 16:00:53 -0000
Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.127.97.95
with plain)
by smtp118.sbc.mail.sp1.yahoo.com with SMTP; 25 Jan 2008 16:00:53 -0000
X-YMail-OSG: ccmp6rkVM1lpaUst0S5xTkmtr_wdiAW094zo7InDY_UZN1n2
X-Yahoo-Newman-Property: ymail-3
Message-ID: <479A073D.2070309@andybierman.com>
Date: Fri, 25 Jan 2008 07:58:53 -0800
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: yang <yang@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [YANG] capability-stmt
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>,
<mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>,
<mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org
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
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang
- [YANG] capability-stmt Andy Bierman