Re: [secdir] secdir review of draft-ietf-dime-overload-reqs-11

Jouni Korhonen <jouni.nospam@gmail.com> Tue, 10 September 2013 03:55 UTC

Return-Path: <jouni.nospam@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3887121F9B12; Mon, 9 Sep 2013 20:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.394
X-Spam-Level:
X-Spam-Status: No, score=-1.394 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_RECV_IP_211216=0.978, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W6avEl6Nnw-v; Mon, 9 Sep 2013 20:55:43 -0700 (PDT)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 9F37D21F99CD; Mon, 9 Sep 2013 20:55:43 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id y10so6998097pdj.8 for <multiple recipients>; Mon, 09 Sep 2013 20:55:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Z81gtmzJc0IvBBu2pxRrwscMO9doPbh2NCeie9gb6oI=; b=uKAO72+FuFDNWLsQU1s+u1pbj+VcFVeHYDcLN1rao3gQhuq/x+qgWQ6lAdT3xEG3Mb GgiXSKZm2WnE5EATSXdFFDcg9q1hhhOeypEgvCcbQ24TX8RPDny1ND1RdRIdbVmuJlK5 snAH2mzz23xTMl/HoZ/4djRc21pZYXAQ75m0IFFHiRpfcV0GM7qagrjOJ88855jYSZOP JXP0DWy/5yyocWzENsA13kp0PeO/i62NstKAFFHmtSzcMUEq9p6AMdjmSHFPh5vX7iVi zwtVz/nRliC8MGB5DbxskeDSR2XB43+GIkLPLicKmH6MRHSsXmPpXaLacI05JyW4WupT mw8A==
X-Received: by 10.68.232.134 with SMTP id to6mr6583597pbc.163.1378785342986; Mon, 09 Sep 2013 20:55:42 -0700 (PDT)
Received: from [10.5.8.117] ([211.219.0.130]) by mx.google.com with ESMTPSA id qa9sm19862435pbc.7.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Sep 2013 20:55:42 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <271A8F02-3A74-46E9-B08E-2D155EC3DDD3@computer.org>
Date: Tue, 10 Sep 2013 06:55:37 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <351B6399-E47D-4041-A09F-712ED4570F40@gmail.com>
References: <CE53ED6D.1CBD%carl@redhoundsoftware.com> <8D9934B4-948F-47A5-AB5E-02DEDD5277F0@gmail.com> <271A8F02-3A74-46E9-B08E-2D155EC3DDD3@computer.org>
To: Eric McMurry <emcmurry@computer.org>
X-Mailer: Apple Mail (2.1508)
Cc: Ben Campbell <ben@nostrum.com>, secdir@ietf.org, draft-ietf-dime-overload-reqs.all@tools.ietf.org, "lionel.morand@orange.com Morand" <lionel.morand@orange.com>, iesg@ietf.org, "bclaise@cisco.com Claise" <bclaise@cisco.com>
Subject: Re: [secdir] secdir review of draft-ietf-dime-overload-reqs-11
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 03:55:44 -0000

I would note down the change but implement/submit a revision after we get
the rest of the IESG comments (the doc is in next week's telechat). That's
because ADs (and others) are now reading the -11.

- Jouni


On Sep 10, 2013, at 6:24 AM, Eric McMurry <emcmurry@computer.org> wrote:

> that matches what I came away with.  How would you like us to address that?
> 
> 
> On Sep 9, 2013, at 22:22 , Jouni Korhonen <jouni.nospam@gmail.com> wrote:
> 
>> 
>> Folks,
>> 
>> So if I got it right, the last sentence of the Req13 will be removed and
>> the Req31 stays as it is now.
>> 
>> This would be fine with me.
>> 
>> - JOuni
>> 
>> On Sep 10, 2013, at 4:27 AM, Carl Wallace <carl@redhoundsoftware.com> wrote:
>> 
>>>> 
>>>> 
>>>> 
>>>> The intent was that the overload condition has granularity. That is, the
>>>> overloaded node indicates an overload condition with some granularity,
>>>> and later ends it. The act of ending doesn't change the granularity. We
>>>> don't have an explicit requirement to be able to change the granularity
>>>> of an existing condition. (Although we do not prevent a solution from
>>>> offering that ability--but I suspect if the solution did that, it would
>>>> involve multiple concurrent overload conditions, or ending one condition
>>>> and starting another.)
>>> 
>>> Got it.  Thanks.  
>>> 
>>> 
>> 
>