Re: [i2rs] Comments on Ephemeral-REQ-07 (local config vs. ephemeral)

"Robert Wilton -X (rwilton - ENSOFT LIMITED at Cisco)" <> Wed, 20 July 2016 09:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7215B12D0E9 for <>; Wed, 20 Jul 2016 02:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -15.807
X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EsHgM0ib1_qc for <>; Wed, 20 Jul 2016 02:10:18 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E84F612B004 for <>; Wed, 20 Jul 2016 02:10:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=10272; q=dns/txt; s=iport; t=1469005817; x=1470215417; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=MQIHNmuw5VF9MOe9sohJsy4f3F4XicV6ly4hofuI7LY=; b=ZMGSwx/vQDUnL6ab9sRjUTbktig661CnsXQlW3Ff0boBZlO88tjmB9Nm cFMokS8Fpcb0Gp3gwqsCOHCVKxVfsI3v1G2IrvrCc7xEwIUFQws2hN4gq 5QDZK9nW2L0qsCoSuPtbw+gvobRDVBfjqwzotUhzS2THgEJwSoMBaHpRs k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.28,393,1464652800"; d="scan'208,217";a="299844398"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jul 2016 09:10:16 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u6K9AG7e019694 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 20 Jul 2016 09:10:16 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 20 Jul 2016 04:10:16 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Wed, 20 Jul 2016 04:10:16 -0500
From: "Robert Wilton -X (rwilton - ENSOFT LIMITED at Cisco)" <>
To: Susan Hares <>, 'Russ White' <>, "" <>, "Joe Clarke (jclarke)" <>
Thread-Topic: [i2rs] Comments on Ephemeral-REQ-07 (local config vs. ephemeral)
Date: Wed, 20 Jul 2016 09:10:16 +0000
Message-ID: <>
References: <> <016201d1e11b$6c0c3140$442493c0$> <> <009801d1e24d$3b92a340$b2b7e9c0$> <019b01d1e24e$8ea9bc70$abfd3550$> <> <009201d1e25a$35af9b10$a10ed130$>, <>
In-Reply-To: <>
Accept-Language: en-GB, en-US
Content-Language: en-GB
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_eniiljkadm7ncjq8p2nkjn9d1469003679596emailandroidcom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [i2rs] Comments on Ephemeral-REQ-07 (local config vs. ephemeral)
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 20 Jul 2016 09:10:24 -0000


Sorry, but I can't make the I2RS meeting because I'm presenting at the end of NETCONF.

I've spoken to Sue and understand that the requirement isn't changing here - just the text to describe it.

I think that I'm OK with this new text.

One suggestion: Possibly It might help if the text made it clear that the priotiy resolution applies to the complete set of ephemeral config vs the complete set of local config. I.e. the requirement is not asking for priority resolution between the two config sets on a per datanode basis.

But I strongly support getting the requirements draft completed, and hence I suspect that whatever text that you agree in the 2nd I2RS meeting will be fine.


Sent from my Xperia™ tablet

---- Joe Clarke (jclarke) wrote ----

On 7/20/16 03:42, Susan Hares wrote:
> Joe:
> Yes - you are correct.  Can you help me state this requirement -07 better?

What about:

Ephemeral-REQ-07: Ephemeral configuration and local configuration MUST
each have a priority.  This priority will determine whether ephemeral
configuration or local configuration take precedence.  The I2RS protocol
MUST support this mechanism.

Is this clear and correct enough?


> Sue
> -----Original Message-----
> From: Joe Clarke []
> Sent: Wednesday, July 20, 2016 3:40 AM
> To: Susan Hares; 'Russ White';
> Subject: Re: [i2rs] Comments on Ephemeral-REQ-07 (local config vs.
> ephemeral)
> On 7/20/16 02:18, Susan Hares wrote:
>> <WG hat off> <author hat on>
>> Here's text that might replace it:
>> Ephemeral-REQ-07: Ephemeral configuration state MUST be able to set a
>> priority on local configuration and ephemeral state.  Based on this
>> priority implementations MUST be able to provide a mechanism to choose
>> which takes precedence. The I2RS Protocol MUST be able to support this
> mechanisms.
>> Any thoughts?
> I'm a bit confused by the first sentence.  I think what you're stating is
> that both ephemeral and local configurations MUST have a priority.
> This priority will determine whether ephemeral configuration or local
> configuration take precedence.  The I2RS protocol MUST support this
> mechanism.
> Am I correct in my interpretation?
> Joe
>> Sue
>> -----Original Message-----
>> From: Russ White []
>> Sent: Wednesday, July 20, 2016 2:09 AM
>> To: 'Joe Clarke'; 'Susan Hares';
>> Subject: RE: [i2rs] Comments on Ephemeral-REQ-07 (local config vs.
>> ephemeral)
>> (wg chair hat off) --
>>> I think the idea of extending I2RS priority to local config operators
>> (e.g., CLI)
>>> will still work.  Let's take knob 1.  Knob 1 is kind of like the
>>> on/off
>> switch.  If I
>>> don't want I2RS to have any effect on operational state, I'd have
>>> this
>> off.  In
>>> the I2RS priority case, by default my local config could will have
>>> the
>> highest
>>> priority (let's say that's 255 to make it concrete).  In this case no
>> ephemeral
>>> config can win.
>> I wanted to extend Joe's remarks a bit... On reflection, I actually
>> think having priority + "this wins" bits is rather confusing, and
>> opens the door to all sorts of strange behavior. Say I have two items
>> thus --
>> Local config item -- priority 100
>> I2RS config item -- priority 200, don't overwrite bit set
>> If the higher priority is supposed to win, then which item should the
>> operator find in the resulting running config? Should it be the I2RS
>> version, because the priority is higher, or the local config, because
>> the "don't overwrite" bit is set? There doesn't seem to be any clear
>> way to interpret such a situation.
>> It's better to have a single "thing" that determines which
>> configuration among many wins, rather than two.
>> -r

i2rs mailing list