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

"Susan Hares" <shares@ndzh.com> Mon, 24 October 2016 11:17 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 C06A9129675; Mon, 24 Oct 2016 04:17:33 -0700 (PDT)
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 GhGSHkKHEiAu; Mon, 24 Oct 2016 04:17:32 -0700 (PDT)
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 3A2A21294EF; Mon, 24 Oct 2016 04:17:32 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.86.225;
From: "Susan Hares" <shares@ndzh.com>
To: "'Mirja Kuehlewind'" <ietf@kuehlewind.net>, "'The IESG'" <iesg@ietf.org>
References: <147730513633.15463.2064365068681638626.idtracker@ietfa.amsl.com>
In-Reply-To: <147730513633.15463.2064365068681638626.idtracker@ietfa.amsl.com>
Date: Mon, 24 Oct 2016 07:15:36 -0400
Message-ID: <098b01d22de7$f4edb4c0$dec91e40$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFZ376eBA7GLubUqS2dij+H/4ZjJaGoD56w
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/tcRRP_dSVALKd0kViyW_uycNB0c>
Cc: jclarke@cisco.com, draft-ietf-i2rs-ephemeral-state@ietf.org, i2rs-chairs@ietf.org, i2rs@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 11:17:34 -0000

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?