IETF Logo Mail Archive

Re: [I2rs-proto-dt] I2RS Protocol Document - Please review on Tuesday (10/20/2015)

"Dongjie (Jimmy)" <jie.dong@huawei.com> Wed, 21 October 2015 02:52 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: i2rs-proto-dt@ietfa.amsl.com
Delivered-To: i2rs-proto-dt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4A661A013B for <i2rs-proto-dt@ietfa.amsl.com>; Tue, 20 Oct 2015 19:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 fnwCCBH7SN_A for <i2rs-proto-dt@ietfa.amsl.com>; Tue, 20 Oct 2015 19:52:28 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47BBD1B2D62 for <i2rs-proto-dt@ietf.org>; Tue, 20 Oct 2015 19:52:27 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CCU94299; Wed, 21 Oct 2015 02:52:25 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 21 Oct 2015 03:52:24 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.203]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0235.001; Wed, 21 Oct 2015 10:52:19 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Susan Hares <shares@ndzh.com>, "i2rs-proto-dt@ietf.org" <i2rs-proto-dt@ietf.org>
Thread-Topic: [I2rs-proto-dt] I2RS Protocol Document - Please review on Tuesday (10/20/2015)
Thread-Index: AdEKnJ6Tj1l838LmSjGyQns/830hbQBCwKzg
Date: Wed, 21 Oct 2015 02:52:18 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C927743BEE6A@nkgeml512-mbx.china.huawei.com>
References: <03c601d10a9c$c407b370$4c171a50$@ndzh.com>
In-Reply-To: <03c601d10a9c$c407b370$4c171a50$@ndzh.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.97.131]
Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C927743BEE6Ankgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs-proto-dt/52HKW8Ftfw62sIBikVkuXIvchvE>
Cc: 'Kent Watsen' <kwatsen@juniper.net>, 'Andy Bierman' <andy@yumaworks.com>
Subject: Re: [I2rs-proto-dt] I2RS Protocol Document - Please review on Tuesday (10/20/2015)
X-BeenThere: i2rs-proto-dt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: I2RS protocol design team <i2rs-proto-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs-proto-dt>, <mailto:i2rs-proto-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs-proto-dt/>
List-Post: <mailto:i2rs-proto-dt@ietf.org>
List-Help: <mailto:i2rs-proto-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs-proto-dt>, <mailto:i2rs-proto-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2015 02:52:30 -0000

Hi Sue,

A couple of comments on this draft:


1.       Section 2 says:

"The [I-D.openconfig-netmod-opstate] denotes the actual configuration as derived state."

While draft-openconfig-opstate says: The applied configuration and derived state can be considered as the overall 'operational' state of the NE."
Thus the applied(actual) configuration belongs to the operational state, but does not belong to derived state.

Section 2 also says: ""Recently the [I-D.openconfig-netmod-opstate] has proposed that intended configuration, actual configuration, and the traditional type of operational data be included as operational state."

Maybe there is a typo here, the intended configuration should belong to configuration.

2. Since Ephemeral is about data not persisting over a reboot, maybe a requirement for ephemeral states is that they MUST never be copied to the startup configuration datastore?

Best regards,
Jie

From: I2rs-proto-dt [mailto:i2rs-proto-dt-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, October 20, 2015 2:34 AM
To: i2rs-proto-dt@ietf.org
Cc: 'Kent Watsen'; 'Andy Bierman'
Subject: [I2rs-proto-dt] I2RS Protocol Document - Please review on Tuesday (10/20/2015)

HI all:

Here's the I2RS protocol design document.  Would you review this on Tuesday and send me comments?  If it is helpful, we could meet as a design team at 10:00-11:30am.

I would like to get comments and feedback before Wednesday's 10/21/2015 interim meeting.

Sue

v2.23.0 | Report a Bug | By Email