Re: [i2rs] Mirja Kühlewind's No Objection on draft-ietf-i2rs-ephemeral-state-19: (with COMMENT)

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Mon, 24 October 2016 13:18 UTC

Return-Path: <ietf@kuehlewind.net>
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 0C20312957A for <i2rs@ietfa.amsl.com>; Mon, 24 Oct 2016 06:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.333
X-Spam-Level:
X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable 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 cbohK5strbKU for <i2rs@ietfa.amsl.com>; Mon, 24 Oct 2016 06:18:40 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66DE912957E for <i2rs@ietf.org>; Mon, 24 Oct 2016 06:18:38 -0700 (PDT)
Received: (qmail 32074 invoked from network); 24 Oct 2016 15:18:26 +0200
Received: from p5dec2f7e.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (93.236.47.126) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 24 Oct 2016 15:18:24 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <098b01d22de7$f4edb4c0$dec91e40$@ndzh.com>
Date: Mon, 24 Oct 2016 15:18:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <83CFB624-2DFD-4E87-9559-798015D7BA53@kuehlewind.net>
References: <147730513633.15463.2064365068681638626.idtracker@ietfa.amsl.com> <098b01d22de7$f4edb4c0$dec91e40$@ndzh.com>
To: Susan Hares <shares@ndzh.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/ZrvGCBY18Za1rXVwawgXLjXdHnw>
Cc: draft-ietf-i2rs-ephemeral-state@ietf.org, i2rs@ietf.org, jclarke@cisco.com, The IESG <iesg@ietf.org>, i2rs-chairs@ietf.org
Subject: Re: [i2rs] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-i2rs-ephemeral-state-19=3A_=28with_COMMENT=29?=
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: Mon, 24 Oct 2016 13:18:44 -0000

Hi Susan,

> I2RS is specified to have data which is just ephemeral state.

Missed that part. So basically you only need to address comment one and mention that.

Thanks,
Mirja


> Am 24.10.2016 um 13:15 schrieb Susan Hares <shares@ndzh.com>;:
> 
> Mirja: 
> 
> 
> 1) "I2RS requires ephemeral state; i.e. state that does
>   not persist across reboots." -> why? Maybe add 1-2 sentences about the use (case) in the introduction.
> 
> I will add a few sentences to the introduction.  
> 
> 2) Are all these requirements specific to ephemeral state? I would assume that some requirements are more general, e.g. don't you need priorities also for all other state updates?
> 
> All of these requirements are required in order to do ephemeral state.   I2RS is specified to have data which is just ephemeral state.  So... I'm not sure what the question is. 
> 
> Sue 
> 
> -----Original Message-----
> From: Mirja Kuehlewind [mailto:ietf@kuehlewind.net] 
> Sent: Monday, October 24, 2016 6:32 AM
> To: The IESG
> Cc: draft-ietf-i2rs-ephemeral-state@ietf.org; Joe Clarke; i2rs-chairs@ietf.org; jclarke@cisco.com; i2rs@ietf.org
> Subject: Mirja Kühlewind's No Objection on draft-ietf-i2rs-ephemeral-state-19: (with COMMENT)
> 
> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-i2rs-ephemeral-state-19: No Objection
> 
> When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-i2rs-ephemeral-state/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Two comments:
> 
> 1) "I2RS requires ephemeral state; i.e. state that does
>   not persist across reboots." -> why? Maybe add 1-2 sentences about the use (case) in the introduction.
> 
> 2) Are all these requirements specific to ephemeral state? I would assume that some requirements are more general, e.g. don't you need priorities also for all other state updates?
> 
> 
>