Re: [Netconf] [i2rs] FW: New Version Notification for draft-hares-i2rs-protocol-strawman-02.txt - 3.1.1

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 10 May 2016 15:11 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0375412D1C2; Tue, 10 May 2016 08:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level:
X-Spam-Status: No, score=-2.722 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 Pm6JuMf0IKpz; Tue, 10 May 2016 08:10:59 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6D4312D1B7; Tue, 10 May 2016 08:10:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 893A31C0ADE; Tue, 10 May 2016 08:10:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1462893059; bh=ezCJLbyAj5IWw44TMffc8bjdpV+TWSPrRNn+KKGWeoE=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=ZQfmeHnBtECYICBDGbFIG9vCiCsvreePVufZlDLCDgXF74+Sy4YDz/Igp7sERJpWL 4+uDOOUv/qSVYapcRPpbi6gVk1RybOLAEe0vV6ah6dvzsl2uvhL/VDWsTb3V3bJDCl 77HVB8RgKUXxyb6bcBSRLHDVPOswUWhFHUTUZ5Hw=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (sessfw99-sesbfw99-81.ericsson.net [192.176.1.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 3C3C31C069E; Tue, 10 May 2016 08:10:58 -0700 (PDT)
To: Susan Hares <shares@ndzh.com>, 'Andy Bierman' <andy@yumaworks.com>
References: <7eqdbrhnm368w3aqvlarweoi.1462882301561@email.android.com> <010901d1aacb$ddabec90$9903c5b0$@ndzh.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <5b422567-7120-16c8-7a7d-2ee5227165c1@joelhalpern.com>
Date: Tue, 10 May 2016 11:10:55 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <010901d1aacb$ddabec90$9903c5b0$@ndzh.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/netconf/8bvJsmLNmTYA71gRMkOUsRJ9gCc>
Cc: i2rs@ietf.org, 'Netconf' <netconf@ietf.org>
Subject: Re: [Netconf] [i2rs] FW: New Version Notification for draft-hares-i2rs-protocol-strawman-02.txt - 3.1.1
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 10 May 2016 15:11:02 -0000

Yes, you interpreted my awful typing correctly.

I don't see any need for anything more, but was allowing that I am not 
fully current on the groups thinking.

Yours,
Joel

On 5/10/16 10:54 AM, Susan Hares wrote:
> Joel:
>
>
>
> See below.   Just trying to wrap up the discussion.
>
>
>
> *From:*jmh.direct [mailto:jmh.direct@joelhalpern.com]
> *Sent:* Tuesday, May 10, 2016 8:12 AM
> *To:* Susan Hares; 'Joel M. Halpern'; 'Andy Bierman'
> *Cc:* i2rs@ietf.org; 'Netconf'
> *Subject:* RE: [i2rs] FW: New Version Notification for
> draft-hares-i2rs-protocol-strawman-02.txt - 3.1.1
>
>
>
> If the I2RS aren't is off then the system does not currently support
> this models.  This is just like any other optional YANG module.  If you
> are not currently prepared to use it, you don't claim to support it.
>
>
>
> Sue: I assume you desired to say…  if the I2RS is not on, then the
> system does not support this model.
>
>
>
> Caveat: The NetMod folks may have come up with a more nuanced mechanism.
>
>
>
> Sue: Do we need them to come up with mechanism that indicates I2RS is
> there but off?
>
>
>
> Yours,
>
> Joel
>
>
>
>
>
>
>
> Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone
>
> -------- Original message --------
>
> From: Susan Hares <shares@ndzh.com <mailto:shares@ndzh.com>>
>
> Date: 5/10/2016 1:25 PM (GMT+01:00)
>
> To: "'Joel M. Halpern'" <jmh@joelhalpern.com
> <mailto:jmh@joelhalpern.com>>, 'Andy Bierman' <andy@yumaworks.com
> <mailto:andy@yumaworks.com>>
>
> Cc: i2rs@ietf.org <mailto:i2rs@ietf.org>, 'Netconf' <netconf@ietf.org
> <mailto:netconf@ietf.org>>
>
> Subject: RE: [i2rs] FW: New Version Notification for
> draft-hares-i2rs-protocol-strawman-02.txt - 3.1.1
>
>
>
> Joel:
>
> What happens if the code supports the I2RS agent, but the I2RS agent is
> configured to be "off"?  Is this covered by the deviations or is this
> variable configuration?
>
> Sue
>
> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: Tuesday, May 10, 2016 1:34 AM
> To: Susan Hares; Andy Bierman
> Cc: i2rs@ietf.org <mailto:i2rs@ietf.org>; Netconf
> Subject: Re: [i2rs] FW: New Version Notification for
> draft-hares-i2rs-protocol-strawman-02.txt - 3.1.1
>
> As I understand it, if a model requires ephemeral elements, and the
> agent does not support ephemeral, then the agent can not claim to
> support the model.
>
> Yes, deviations allow you to specify this, as Andy says.  But this is
> specifying a failure to conform.
>
> I would go far as to say that such an agent is not an I2RS agent, but
> that is a step beyond the NetConf compliance definitions.
>
> Yours,
> Joel
>
> On 5/9/16 6:09 PM, Susan Hares wrote:
>> Andy and Joel:
>>
>> These are good points.
>>
>> What happens if the data model has some ephemeral sections and the
>> I2RS agent is not supported by the routing system.  The data model
>> would specify the ephemeral section, but there would be no support by
> i2rs.
>>  Is the support of the ephemeral not a variable  condition to be
>> indicated in Yang module library?
>>
>> Sue
>> Sent via the Samsung Galaxy Note5, an AT&T 4G LTE smartphone
>> -------- Original message --------
>> From: Andy Bierman <andy@yumaworks.com <mailto:andy@yumaworks.com>>
>> Date: 5/7/2016 12:53 PM (GMT-05:00)
>> To: "Joel M. Halpern" <jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>
>> Cc: i2rs@ietf.org <mailto:i2rs@ietf.org>, Netconf <netconf@ietf.org
> <mailto:netconf@ietf.org>>, Susan Hares
>> <shares@ndzh.com <mailto:shares@ndzh.com>>
>> Subject: Re: [i2rs] FW: New Version Notification for
>> draft-hares-i2rs-protocol-strawman-02.txt - 3.1.1
>>
>>
>>
>> On Fri, May 6, 2016 at 8:51 AM, Joel M. Halpern <jmh@joelhalpern.com
> <mailto:jmh@joelhalpern.com%20%0b>> <mailto:jmh@joelhalpern.com>> wrote:
>>
>>     Reading the latest revision, in section 3.1.1, the text in bullet 5
>>     says that the data model indicates which portions are ephemeral.
>>     That makes sense to me.
>>
>>     Then bullet 6 says that the management protocol needs to signal (in
>>     its yang library) which parts are ephemeral.
>>
>>     Why the second requirement?  If the data model is supported, and the
>>     data model states that certain items are ephemeral, what would it
>>     mean if the signaling did not also say that.  Conversely, what would
>>     it mean if the signaling said something was ephemeral that the model
>>     does not define as ephemeral?
>>
>>     It may be that I am misreading bullet 6.  Please explain.
>>
>>
>>
>> I think you are correct that the YANG library does not need any
>> changes to identify ephemeral data.  Only the variable components of
>> YANG conformance are contained in the library.
>>
>>
>>     Thank you,
>>     Joel
>>
>>
>>
>> Andy
>>
>>
>>     _______________________________________________
>>     i2rs mailing list
>>     i2rs@ietf.org <mailto:i2rs@ietf.org> <mailto:i2rs@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/i2rs
>>
>>
>