Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-state-10
Robert Wilton <rwilton@cisco.com> Thu, 23 June 2016 16:40 UTC
Return-Path: <rwilton@cisco.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 3FE2C12D0B7 for <i2rs@ietfa.amsl.com>; Thu, 23 Jun 2016 09:40:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.948
X-Spam-Level:
X-Spam-Status: No, score=-15.948 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_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 WNVdy-XIK2oN for <i2rs@ietfa.amsl.com>; Thu, 23 Jun 2016 09:40:32 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FE1012B046 for <i2rs@ietf.org>; Thu, 23 Jun 2016 09:40:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4711; q=dns/txt; s=iport; t=1466700031; x=1467909631; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=pSHSsd4yEX4WnhLpAj56/JMJB5yp72egRYLdB2PpT7M=; b=LQQLWI6OmkLv2zMz0MBwFpI+G/XqIQcFAUFINJmsrCWERJMzTZ4bYTGo cLoO/NPwGsdw9kjdMrIZv5ROwcnUX4Up8vQ2nJSkbl7ZQ3BuaZxl0/onB fu+nmhsKh7WDT7VRuOVhGEmhgKVkYlQhmG54tiyZqxUuCq2PMOKxvlNz0 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DPAQAlEGxX/xbLJq1dhBQrUro6gXoXC4V2AoFkFAEBAQEBAQFlJ4RMAQEBBAEBATU2CwwECw4DBAEBAScHJx8JCAYBDAYCAQGILA7GfQEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhieBd4JWihsBBJh/jjGJR4Vdj34eNoIIHIFNOzKIYCqBGgEBAQ
X-IronPort-AV: E=Sophos;i="5.26,517,1459814400"; d="scan'208";a="677886871"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jun 2016 16:40:29 +0000
Received: from [10.63.23.64] (dhcp-ensft1-uk-vla370-10-63-23-64.cisco.com [10.63.23.64]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u5NGeTR8030903; Thu, 23 Jun 2016 16:40:29 GMT
To: Susan Hares <shares@ndzh.com>, 'Juergen Schoenwaelder' <j.schoenwaelder@jacobs-university.de>
References: <20160623120251.GA46183@elstar.local> <085cf0e5-414d-7bfc-203e-b98e75a1337a@cisco.com> <20160623154138.GA46519@elstar.local> <013f01d1cd66$89680930$9c381b90$@ndzh.com> <cbd8985a-d1b8-bf57-d607-362013e4cd04@cisco.com> <029401d1cd6b$15b12260$41136720$@ndzh.com>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <b67ea204-cd88-a73f-a394-b575a29eb303@cisco.com>
Date: Thu, 23 Jun 2016 17:40:29 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <029401d1cd6b$15b12260$41136720$@ndzh.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/NTp7CEgRHacAHj6NskthTA2s7jI>
Cc: i2rs@ietf.org
Subject: Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-state-10
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, 23 Jun 2016 16:40:34 -0000
Yes. Thanks, Rob On 23/06/2016 17:19, Susan Hares wrote: > Robert: > > I changed Ephemeral-REQ-03 to: > > Ephemeral-REQ-03: Ephemeral state may have constraints that refer > to operational state, this includes potentially fast changing or > short lived operational state nodes, such as MPLS LSP-ID or a BGP > IN-RIB. > > Is this OK? > > Sue > > -----Original Message----- > From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Robert Wilton > Sent: Thursday, June 23, 2016 12:00 PM > To: Susan Hares; 'Juergen Schoenwaelder' > Cc: i2rs@ietf.org > Subject: Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-state-10 > > Hi, > > > On 23/06/2016 16:47, Susan Hares wrote: >> Juergen and Robert: >> >> I will use the following for Ephemeral-REQ-03. >> >> Ephemeral-REQ-03: Ephemeral state must be able to utilized temporary >> operational state (e.g. MPLS LSP-ID or a BGP IN-RIB) as a >> constraints. > That is the original text. Am I correct in assuming that you meant this > text instead?: > > Ephemeral-REQ-03: Ephemeral state must be able to utilize operational state > (e.g. MPLS LSP-ID or BGP In-RIB) as a constraint. > > If so, this proposed text is OK with me. > > >> On Ephemeral-REQ-04, >> >>> Ephemeral-REQ-04: Ephemeral state MAY refer to non-ephemeral state >>> for purposes of implementing constraints. >> Non-ephemeral state is both configuration state (config true), and >> operational state (config false). >> >> I believe these are two different requirements. > Yes. Given that REQ-03 covers using operational state as a constraint, then > would it be sufficient to word REQ-04 as: > > Ephemeral-REQ-04: Ephemeral state MAY refer to non-ephemeral configuration > for purposes of implementing constraints. > > Or perhaps to relate it more closely to REQ-03, as: > > Ephemeral-REQ-03: Ephemeral state must be able to utilize non-ephemeral > configuration as a constraint. > > Or is this missing something out? > > Thanks, > Rob > > >> Sue >> >> -----Original Message----- >> From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Juergen >> Schoenwaelder >> Sent: Thursday, June 23, 2016 11:42 AM >> To: Robert Wilton >> Cc: i2rs@ietf.org >> Subject: Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-state-10 >> >> On Thu, Jun 23, 2016 at 03:12:50PM +0100, Robert Wilton wrote: >>> Hi, >>> >>> On 23/06/2016 13:02, Juergen Schoenwaelder wrote: >>>> Hi, >>>> >>>> here are few comments on the latest version. >>>> >>>> Ephemeral-REQ-03: Ephemeral state must be able to utilized > temporary >>>> operational state (e.g. MPLS LSP-ID or a BGP IN-RIB) as a >>>> constraints. >>>> >>>> I am not sure what 'must be able to utilized temporary operational >>>> state as constraints' means. The text in the parenthesis does not >>>> help me understand this better. Did you want to say something like: >>>> 'Ephemeral configuration state may have constraints that refer to >>>> operational state'? I am using 'ephemeral configuration state' since >>>> this is used in other places (although sometimes worded slightly >>>> different). >>> I asked a similar question in the I2RS interim meeting yesterday, I >>> think that Sue's spoken explanation of the requirement was effectively: >>> >>> Ephemeral-REQ-03: Ephemeral state may have constraints that refer >>> to operational state, this includes potentially fast changing or >>> short lived operational state nodes, such as MPLS LSP-ID or a BGP >> IN-RIB. >>> Perhaps this wording is more clear? >> Yes, this is clearer. One question of course is what is expected to >> happen if constraints are becoming false due to (fast) operational >> state changes, that is, what the expected consequence of this is. >> >>>> Ephemeral-REQ-04: Ephemeral state MAY refer to non-ephemeral state >>>> for purposes of implementing constraints. >>>> >>>> Hm, now I wonder whether this is just a special case of >>>> Ephemeral-REQ-03 and if so it is not clear why we need this as a >>>> separate requirement. If this is not the case but something >>>> different, then likely my interpretation of Ephemeral-REQ-03 is wrong. >>> I think that ephemeral state could also use configuration nodes as a >>> constraint, so it isn't just operational state covered by REQ-3. >> Well, the Ephemeral-REQ-04 text says 'non-ephemeral state' - if your >> interpretation is correct than this phrase is wrong or possibly > misleading. >> /js >> > _______________________________________________ > i2rs mailing list > i2rs@ietf.org > https://www.ietf.org/mailman/listinfo/i2rs > > . >
- [i2rs] comments on draft-ietf-i2rs-ephemeral-stat… Juergen Schoenwaelder
- Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-… Robert Wilton
- Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-… Juergen Schoenwaelder
- Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-… Susan Hares
- Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-… Robert Wilton
- Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-… Susan Hares
- Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-… Susan Hares
- Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-… Robert Wilton
- Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-… Susan Hares
- Re: [i2rs] comments on draft-ietf-i2rs-ephemeral-… Susan Hares