Re: [i2rs] Question on opstate/ephemeral update

"Susan Hares" <shares@ndzh.com> Thu, 17 November 2016 04:24 UTC

Return-Path: <shares@ndzh.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 F0BC212948D for <i2rs@ietfa.amsl.com>; Wed, 16 Nov 2016 20:24:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=no
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 9P10Y0US9gyF for <i2rs@ietfa.amsl.com>; Wed, 16 Nov 2016 20:24:24 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7069E127A90 for <i2rs@ietf.org>; Wed, 16 Nov 2016 20:24:24 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=31.133.133.143;
From: "Susan Hares" <shares@ndzh.com>
To: "'Joel M. Halpern'" <jmh@joelhalpern.com>, "'Joe Clarke'" <jclarke@cisco.com>, <i2rs@ietf.org>
References: <8419df8b-4861-edb7-0a66-c2c123148727@cisco.com> <015201d2404d$ef173260$cd459720$@ndzh.com> <d17fc9d5-3f94-a50c-817b-a1abeb30b094@joelhalpern.com>
In-Reply-To: <d17fc9d5-3f94-a50c-817b-a1abeb30b094@joelhalpern.com>
Date: Wed, 16 Nov 2016 23:21:48 -0500
Message-ID: <00de01d2408a$1ec299a0$5c47cce0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJQdUo40QgeWLTd4TLWDuCDLWhaGgG5eFvFAUtIt36fyADi4A==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/INnwqqYY33n9XYSyFwwyfg8ijgc>
Subject: Re: [i2rs] Question on opstate/ephemeral update
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
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, 17 Nov 2016 04:24:26 -0000

Joel: 

My description is one 1 way to implement 3.4.   -Resolve the multi-write
conflict via client priorities.   Then install configuration into node using
the data store priorities (config = priority 3, ephemeral = priority 4, dhcp
= priority 2).  

Your way is to assign the priorities so it is a complete scheme.    Common
algebra techniques indicates these are the same.  Let's see what happens
when we implemented both ways. 

Cheers, 

Seu 


-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Joel M. Halpern
Sent: Wednesday, November 16, 2016 8:21 PM
To: Susan Hares; 'Joe Clarke'; i2rs@ietf.org
Subject: Re: [i2rs] Question on opstate/ephemeral update

My read of the ephemeral state requirements in this regard (3.4) was that we
are simply assigning Intended Conifg and the specific other cynamic control
protocols priorities in the same space we are using for deciding between
I2RS clients in the case of conflict.

So if I2RS Clients have priorities ranging from min+2 to Max-2, then
assuming higher is better, to get the result in your first example, one
would set intended to min-1 and dhcp to min-2.
And the reverse for your second example.

As an operator, one could assign ones clients priorities in various ranges,
and arrange the dhcp and intended config priorities at other points to get
more complex results.
And of course, one could set dhcp to max+1 and intended config to max+2 to
max I2RS yield to all the others, and intended config take precedence over
everything.

Yours,
Joel

On 11/16/16 4:10 PM, Susan Hares wrote:
> Joe:
>
> I've updated the examples in the yang document.  Here's my 
> understanding with priorities (see ephemeral state requirements) with 
> highest priority winning.
>
> Set
> Intended configuration priority = 2
> Dhcp configuration priority = 1
> Ephemeral state = 3
>
> Dhcp - would never update things, and I2RS would win over intended 
> configuration.
>
> Set
> Intended configuration priority = 1
> Dhcp configuration priority = 2
> Ephemeral state = 3
>
> Dhcp takes precedence (wins) over intended configuration - so dhcp 
> received configurations are installed.  Ephemeral state wins over dhcp
values.
>
> Does this make sense?
>
> Sue
>
> -----Original Message-----
> From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Joe Clarke
> Sent: Wednesday, November 16, 2016 1:56 AM
> To: i2rs@ietf.org
> Subject: [i2rs] Question on opstate/ephemeral update
>
> Given the tight timing of the meeting, I don't want to derail things.
> If we have time, I'll raise this at the mic.
>
> But I do have a question on slide 2 of 
> https://www.ietf.org/proceedings/97/slides/slides-97-i2rs-i2rs-opstate
> -and-e
> phemeral-00.pdf
> .  I see DHCP along side the [I2RS] control plane DSes.  I understand 
> that the I2RS agent will handle the resolution of multiple client 
> writes using priorities.
>
> But how does that play with DHCP or local config?  In our ephemeral 
> requirements draft we say that local config (<intended> in this 
> drawing) would have a priority.  And that in the <applied> state the 
> device would have to resolve the local priorities with the "winning" 
> config from the I2RS agent.  But then DHCP writes a route.  How will that
be handled?
>
> I would like some clarity with respect to our priority requirements in 
> the ephemeral state draft.
>
> Joe
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>

_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs