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

Phil Shafer <phil@juniper.net> Sat, 01 May 2010 22:41 UTC

Return-Path: <phil@juniper.net>
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 D87633A67FB for <netconf@core3.amsl.com>; Sat, 1 May 2010 15:41:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.484
X-Spam-Level:
X-Spam-Status: No, score=-5.484 tagged_above=-999 required=5 tests=[AWL=1.115, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Og7vpNSHce7y for <netconf@core3.amsl.com>; Sat, 1 May 2010 15:41:41 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by core3.amsl.com (Postfix) with ESMTP id F00193A68AD for <netconf@ietf.org>; Sat, 1 May 2010 15:41:40 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKS9yuFiha87lCo7ab0/JbH3OAWWRGMgdi@postini.com; Sat, 01 May 2010 15:41:27 PDT
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.436.0; Sat, 1 May 2010 14:17:47 -0700
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.4675); Sat, 1 May 2010 14:17:47 -0700
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 1 May 2010 14:17:46 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.4675); Sat, 1 May 2010 14:17:46 -0700
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id o41LHjD91768; Sat, 1 May 2010 14:17:45 -0700 (PDT) (envelope-from phil@juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.3/8.14.3) with ESMTP id o41L0gWl020720; Sat, 1 May 2010 21:00:42 GMT (envelope-from phil@idle.juniper.net)
Message-ID: <201005012100.o41L0gWl020720@idle.juniper.net>
To: andyb@iwl.com
In-Reply-To: <4BDC81A3.1080409@iwl.com>
Date: Sat, 01 May 2010 17:00:42 -0400
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 01 May 2010 21:17:46.0188 (UTC) FILETIME=[BE9BE8C0:01CAE973]
MIME-Version: 1.0
Content-Type: text/plain
Cc: NETCONF <netconf@ietf.org>
Subject: Re: [Netconf] 4741bis -- :url capability issues
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: Sat, 01 May 2010 22:41:43 -0000

Andy Bierman writes:
>> What's an "URL database"?
>Good question.
>The standard does a really awful job of explaining that.

The standard does not use that term.  IMHO these were meant
as files, not databases.  This seems plain since, e.g. an url cannot
be the target of an edit-config.

Thanks,
 Phil