[Netconf] 4741bis - multiple namespaces

Martin Bjorklund <mbj@tail-f.com> Thu, 30 April 2009 14:03 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id EB15B3A6844 for <netconf@core3.amsl.com>; Thu, 30 Apr 2009 07:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.969
X-Spam-Status: No, score=-0.969 tagged_above=-999 required=5 tests=[AWL=-0.782, BAYES_20=-0.74, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id QEMwPkc00SUA for <netconf@core3.amsl.com>; Thu, 30 Apr 2009 07:03:11 -0700 (PDT)
Received: from mail.tail-f.com (de-0316.d.ipeer.se []) by core3.amsl.com (Postfix) with ESMTP id 21BB63A6829 for <netconf@ietf.org>; Thu, 30 Apr 2009 07:03:11 -0700 (PDT)
Received: from localhost (c213-100-167-236.swipnet.se []) by mail.tail-f.com (Postfix) with ESMTPSA id C7B46616010 for <netconf@ietf.org>; Thu, 30 Apr 2009 16:04:33 +0200 (CEST)
Date: Thu, 30 Apr 2009 16:04:28 +0200
Message-Id: <20090430.160428.110485974.mbj@tail-f.com>
To: netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
X-Mailer: Mew version 6.0.51 on Emacs 22.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: [Netconf] 4741bis - multiple namespaces
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Thu, 30 Apr 2009 14:03:12 -0000


Section 7.1 says:

     If the configuration is available in multiple formats, such as
     XML and text, an XML namespace can be used to specify which
     format is desired.  In the following example, the client uses a
     specific element (<config-text>) in a specific namespace to
     indicate to the server the desire to receive the configuration in
     an alternative format.  The server may support any number of
     distinct formats or views into the configuration data, with the
     client using the <filter> parameter to select between them.

It looks like namespaces are used for two different purposes;
different data models and different formats.  This leads to some

  Can the same be achieved with XPath? 

  If no filter is specified, what should the server return - *all*
  namespaces (mulitple data models, multiple formats), or all
  namespaces for *some* format?  How would you get all data for the
  text format?

IMO this feature looks broken.

Does anyone implement this?  Can we remove this paragraph?