Re: [i2rs] Comments on I2RS and YANG suggestions (aka, finally woke up)

Joe Clarke <jclarke@cisco.com> Thu, 30 March 2017 15:49 UTC

Return-Path: <jclarke@cisco.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6A3E129531 for <i2rs@ietfa.amsl.com>; Thu, 30 Mar 2017 08:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HU8I7MrtrMmY for <i2rs@ietfa.amsl.com>; Thu, 30 Mar 2017 08:49:01 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 464481294BF for <i2rs@ietf.org>; Thu, 30 Mar 2017 08:49:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1404; q=dns/txt; s=iport; t=1490888941; x=1492098541; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=6qA6fl28NcEFFE5lewG8JMACfVP6mlSndoJLEZlfmVM=; b=KJBvn9jsQa55ynfCfHJEzlCB3B4WqT0BxK+WA5w7+QVXLYYT47ULsD52 41fZzw06L+460bebZk9jmcD30CkGqme1TOpBaWzj3gt8axe07bZmVbfEg e957vFXEoV+Q6M4tInm8uBlzqwZAtruX0m7GQSTgoT7ijkDbb66zlCOtM I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AUAQBVKN1Y/49dJa1dGQEBAQEBAQEBAQEBBwEBAQEBg1aPX5FSk0GCD4IOhiICgzY/GAECAQEBAQEBAWsohRUBAQEBAgF5EAsYLlcGDQgBAYl/CLAwilUBAQEBAQEBAQEBAQEBAQEBASGGToIFgmqKOQEElgKGaJJQilyBP4Uck20fOIEFOyAVhzYkhw4rghABAQE
X-IronPort-AV: E=Sophos;i="5.36,247,1486425600"; d="scan'208";a="405237821"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Mar 2017 15:49:00 +0000
Received: from [10.24.144.94] ([10.24.144.94]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v2UFmxiD013269; Thu, 30 Mar 2017 15:49:00 GMT
To: Phil Shafer <phil@juniper.net>
References: <201703292057.v2TKvAQL012786@idle.juniper.net>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
Message-ID: <1f0b3cdc-bbe5-6dad-9a9f-66bf27b009f4@cisco.com>
Date: Thu, 30 Mar 2017 11:48:59 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <201703292057.v2TKvAQL012786@idle.juniper.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/4H2aOrakof_ihDmY4LPKB6wXL30>
Subject: Re: [i2rs] Comments on I2RS and YANG suggestions (aka, finally woke up)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Mar 2017 15:49:03 -0000

On 3/29/17 16:57, Phil Shafer wrote:
> Joe Clarke writes:
>> Additionally, if the revised DS draft progresses (and it seems like it will), do
>> we need <write-data> at all?  Yes, we need to sort out validation, but why can't
>> we use <edit-config> (revised DS already gives us <get-data>).
> 
> <edit-config> is defined in the base NETCONF spec, and we're trying
> to avoid reving that.  Instead we're proposing edits to dynamic
> datastores (like i2rs-defined ones) will be performed using a new
> <edit-data> operation (patterned after <edit-config>, named to
> mirror <get-data>).  This operation will take an argument to indicate
> the target datastore.

Thanks, Phil.  I had to keep popping in and out of netmod and netconf,
so I missed this discussion.  This does make sense.

> 
> Following the outcome of Tuesday NETCONF meeting, we'll be preparing
> individual drafts for NETCONF and RESTCONF based on the "impact to
> ..." sections that are currently in the datastore draft.  (Those
> sections will be removed from the datastore draft.)
> 
> And based on Sue's comments, we'll be adding more details re: dynamic
> datastores to the datastore draft.

Thanks.  I still think it would be worth revising or spinning down the
i2rs drafts as they have diverged from the revised DS draft, and this is
adding to at least my confusion.

Joe

> 
> Thanks,
>  Phil
>