[Netconf] namespace in ietf-netconf-monitoring
Andy Bierman <andyb@iwl.com> Tue, 30 March 2010 21:28 UTC
Return-Path: <andyb@iwl.com>
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A58B3A6B3D for <netconf@core3.amsl.com>; Tue, 30 Mar 2010 14:28:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.305
X-Spam-Level:
X-Spam-Status: No, score=-0.305 tagged_above=-999 required=5 tests=[AWL=0.830, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ci+S4CNFHhAt for <netconf@core3.amsl.com>; Tue, 30 Mar 2010 14:28:27 -0700 (PDT)
Received: from smtp114.dfw.emailsrvr.com (smtp114.dfw.emailsrvr.com [67.192.241.114]) by core3.amsl.com (Postfix) with ESMTP id E49C93A6A6B for <netconf@ietf.org>; Tue, 30 Mar 2010 14:28:26 -0700 (PDT)
Received: from relay11.relay.dfw.mlsrvr.com (localhost [127.0.0.1]) by relay11.relay.dfw.mlsrvr.com (SMTP Server) with ESMTP id 72B3A180329 for <netconf@ietf.org>; Tue, 30 Mar 2010 17:28:56 -0400 (EDT)
Received: by relay11.relay.dfw.mlsrvr.com (Authenticated sender: andyb-AT-iwlcorp.com) with ESMTPSA id 529911803C8 for <netconf@ietf.org>; Tue, 30 Mar 2010 17:28:56 -0400 (EDT)
Message-ID: <4BB26D08.8090806@iwl.com>
Date: Tue, 30 Mar 2010 14:28:40 -0700
From: Andy Bierman <andyb@iwl.com>
Organization: Interworking Labs, Inc.
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: NETCONF <netconf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Netconf] namespace in ietf-netconf-monitoring
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: andyb@iwl.com
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netconf>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Mar 2010 21:28:27 -0000
Hi, This namespace stuff sure is confusing us... monitoring-12, sec 2, para 1: A server that implements the data model defined in this document MUST advertise the capability URI "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring". *** I think this is wrong *** NEW: A server that implements the data model defined in this document MUST advertise the capability URI for the ietf-netconf-monitoring.yang module, as specified in [yang-spec]. monitoring-12, page 14 (current YANG namespace): namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring:DRAFT-12"; monitoring-12: sec. 8 (IANA considerations): URI: urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. This document registers one YANG module in the YANG Module Names registry [RFC XXXX]. name: ietf-netconf-monitoring namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring:rfcXXXX prefix: ns reference: rfcXXXX So the XML namespace will change every time a new I-D or RFC is published, right? There will never be a server that advertises the plain URI, as the 'MUST' in sec. 2 says. Andy
- [Netconf] namespace in ietf-netconf-monitoring Andy Bierman
- Re: [Netconf] namespace in ietf-netconf-monitoring Martin Bjorklund
- Re: [Netconf] namespace in ietf-netconf-monitoring Juergen Schoenwaelder
- Re: [Netconf] namespace in ietf-netconf-monitoring Andy Bierman