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

"Susan Hares" <> Wed, 21 October 2015 09:59 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 39F9B1A1B53 for <>; Wed, 21 Oct 2015 02:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id N26neo4giuor for <>; Wed, 21 Oct 2015 02:59:17 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D00391A1B51 for <>; Wed, 21 Oct 2015 02:59:16 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: Susan Hares <>
To: "'Dongjie (Jimmy)'" <>,
References: <03c601d10a9c$c407b370$4c171a50$> <>
In-Reply-To: <>
Date: Wed, 21 Oct 2015 05:59:01 -0400
Message-ID: <008e01d10be7$1d28a950$5779fbf0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_008F_01D10BC5.961A1690"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIlGqCjUdvHxeSKf9bqQHjVarPvfQFCvF3LncN82XA=
Content-Language: en-us
Archived-At: <>
Cc: 'Kent Watsen' <>, 'Andy Bierman' <>
Subject: Re: [I2rs-proto-dt] I2RS Protocol Document - Please review on Tuesday (10/20/2015)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: I2RS protocol design team <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 21 Oct 2015 09:59:19 -0000



Thank you for sending in comments.  You are correct that 



From: I2rs-proto-dt [] On Behalf Of
Dongjie (Jimmy)
Sent: Tuesday, October 20, 2015 10:52 PM
To: Susan Hares;
Cc: 'Kent Watsen'; 'Andy Bierman'
Subject: Re: [I2rs-proto-dt] I2RS Protocol Document - Please review on
Tuesday (10/20/2015)


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.


[Sue]: You are correct.  Good catch.  Jeff mentioned the same in his review.



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


[Sue]: You are correct - there is an error here.  Intended configuration
belongs 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? 


[Sue]: I will add this to the ephemeral state. 


Best regards,



From: I2rs-proto-dt [] On Behalf Of
Susan Hares
Sent: Tuesday, October 20, 2015 2:34 AM
Cc: 'Kent Watsen'; 'Andy Bierman'
Subject: [I2rs-proto-dt] I2RS Protocol Document - Please review on Tuesday


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


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