Re: [Netconf] 4741bis -- :url capability issues

Andy Bierman <andyb@iwl.com> Sat, 01 May 2010 22:43 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 8F0893A67FB for <netconf@core3.amsl.com>; Sat, 1 May 2010 15:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.72
X-Spam-Level:
X-Spam-Status: No, score=-0.72 tagged_above=-999 required=5 tests=[AWL=-1.055, BAYES_50=0.001, 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 HDzXtWmVa7Ha for <netconf@core3.amsl.com>; Sat, 1 May 2010 15:43:30 -0700 (PDT)
Received: from smtp114.dfw.emailsrvr.com (smtp114.dfw.emailsrvr.com [67.192.241.114]) by core3.amsl.com (Postfix) with ESMTP id C302C3A679C for <netconf@ietf.org>; Sat, 1 May 2010 15:43:30 -0700 (PDT)
Received: from relay21.relay.dfw.mlsrvr.com (localhost [127.0.0.1]) by relay21.relay.dfw.mlsrvr.com (SMTP Server) with ESMTP id 55D372E401EA; Sat, 1 May 2010 18:43:16 -0400 (EDT)
Received: by relay21.relay.dfw.mlsrvr.com (Authenticated sender: andyb-AT-iwlcorp.com) with ESMTPSA id 150A22E4011C; Sat, 1 May 2010 18:43:16 -0400 (EDT)
Message-ID: <4BDCAE86.7050906@iwl.com>
Date: Sat, 01 May 2010 15:43:18 -0700
From: Andy Bierman <andyb@iwl.com>
Organization: Interworking Labs, Inc.
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Phil Shafer <phil@juniper.net>
References: <201005012040.o41Ke4RF019392@idle.juniper.net>
In-Reply-To: <201005012040.o41Ke4RF019392@idle.juniper.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: netconf@ietf.org
Subject: Re: [Netconf] 4741bis -- :url capability issues
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: Sat, 01 May 2010 22:43:31 -0000

Phil Shafer wrote:
> Martin Bjorklund writes:
>   
>> (But I don't think this is an important feature, and would rather see
>> it removed.)
>>     
>
> I'm not on board with a 4741bis that removes features or "breaks"
> previously working implementations.
>
>   

But there are no implementations of 4741bis yet,
because it isn't done yet.  Your conformance to RFC 4741
is not affected by this document.

> There are many things that NETCONF allows that YANG does not, but
> that doesn't mean we can reasonably redesign NETCONF into a YANG-only
> transport.
>   

I agreed with you that the 4741bis document
does not have to forbid a string <config> element instead
of an XML sub-tree.  But there is no need to support a string
<config> element in the standard.  If the NETCONF vendor does not
choose to implement any modular XML content, which may include
YANG modules, then the market can decide if that is useful.

I think it is better to define modular content in XML namespaces.
An un-versioned, no-schema, string database seems to retain all
the bad parts of CLI.  Why bother?


> Thanks,
>  Phil
>
>   

Andy