Re: [secdir] Adrian Farrel's Discuss on draft-ietf-ippm-rt-loss-03: (with DISCUSS and COMMENT): new (temp) draft?

"Murphy, Sandra" <Sandra.Murphy@sparta.com> Thu, 12 April 2012 16:20 UTC

Return-Path: <Sandra.Murphy@sparta.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 684E421F86CB; Thu, 12 Apr 2012 09:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level:
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ulWUFhHyy9QW; Thu, 12 Apr 2012 09:20:05 -0700 (PDT)
Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0F021F8693; Thu, 12 Apr 2012 09:20:05 -0700 (PDT)
Received: from Beta5.sparta.com (beta5.sparta.com [157.185.63.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id q3CGJw6p011836; Thu, 12 Apr 2012 11:19:58 -0500
Received: from Hermes.columbia.ads.sparta.com ([157.185.80.107]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id q3CGJviK023404; Thu, 12 Apr 2012 11:19:58 -0500
Received: from HERMES.columbia.ads.sparta.com ([2002:9db9:506b::9db9:506b]) by Hermes.columbia.ads.sparta.com ([::1]) with mapi id 14.01.0355.002; Thu, 12 Apr 2012 12:19:57 -0400
From: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
To: Wesley Eddy <wes@mti-systems.com>, Benoit Claise <bclaise@cisco.com>
Thread-Topic: Adrian Farrel's Discuss on draft-ietf-ippm-rt-loss-03: (with DISCUSS and COMMENT): new (temp) draft?
Thread-Index: AQHNF96ejwUj+YcaD0u34eQkYbvUTZaWMHkAgAEoeGg=
Date: Thu, 12 Apr 2012 16:19:56 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F60F6F2DD0@Hermes.columbia.ads.sparta.com>
References: <20120406144445.4188.3196.idtracker@ietfa.amsl.com> <201204061553.q36FrBRV007699@alpd052.aldc.att.com> <07e001cd14e0$41b408c0$c51c1a40$@olddog.co.uk> <201204080018.q380I1VK007743@alpd052.aldc.att.com> <099701cd15b1$fc18c990$f44a5cb0$@olddog.co.uk> <201204091344.q39Di1rK002725@alpd052.aldc.att.com> <0bea01cd168a$7ed8ae80$7c8a0b80$@juniper.net> <4F8578DE.1020808@cisco.com>, <4F85C96C.4050705@mti-systems.com>
In-Reply-To: <4F85C96C.4050705@mti-systems.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.185.63.118]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'Al Morton' <acmorton@att.com>, "secdir@ietf.org" <secdir@ietf.org>, "afarrel@juniper.net" <afarrel@juniper.net>, 'Samuel Weiler' <weiler@watson.org>, "ippm-chairs@tools.ietf.org" <ippm-chairs@tools.ietf.org>, 'The IESG' <iesg@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'Dan Frost' <danfrost@cisco.com>, "draft-ietf-ippm-rt-loss@tools.ietf.org" <draft-ietf-ippm-rt-loss@tools.ietf.org>
Subject: Re: [secdir] Adrian Farrel's Discuss on draft-ietf-ippm-rt-loss-03: (with DISCUSS and COMMENT): new (temp) draft?
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: Thu, 12 Apr 2012 16:20:06 -0000

Dan Frost and I brought up some of the same comments, wrt the active or passive use of the metric and the suggestion of cryptographic hashes to solve security considerations.

The latest revision satisfies me.

There's one question I'm not adequate to address, and I leave it to the authors and ADs to address:

   Although this metric MAY be applicable in
   passive measurement as well, discussion of additional considerations
   for the passive scenario are beyond the normative scope of this memo.

Does that "MAY" mean "optional" in the 2119 sense, or "might"/"could" in normal English usage sense?  

It sounds like this is saying "there are considerations if this metric is used in a passive scenario, which we aren't going to discuss, but even so you have the option to use this".

I don't know what the "additional considerations" would be.  If they are considerations that a measurement implementer should heed, that's not much of a worry.  If they are considerations that impact others, that's more of a worry.  (Section 9.2's discussion of keeping info confidential (for passive measurements) is an example of considerations that impact others.) 

So I'll leave it to those who know whether that "MAY" is OK or not.

--Sandy 

________________________________________
From: Wesley Eddy [wes@mti-systems.com]
Sent: Wednesday, April 11, 2012 2:11 PM
To: Benoit Claise
Cc: afarrel@juniper.net; 'Al Morton'; adrian@olddog.co.uk; 'Samuel Weiler'; 'The IESG'; ippm-chairs@tools.ietf.org; draft-ietf-ippm-rt-loss@tools.ietf.org; 'Dan Frost'; Murphy, Sandra; secdir@ietf.org
Subject: Re: Adrian Farrel's Discuss on draft-ietf-ippm-rt-loss-03:     (with DISCUSS and COMMENT): new (temp) draft?

On 4/11/2012 8:28 AM, Benoit Claise wrote:
> Al, Wes
>
> I want to review this draft before the IESG telechat tomorrow.
> However, it's getting difficult to keep track of the all the changes
> between
>     - the posted version 3
>     - the diff-03-04 you sent
>     - the extra proposal.
>
> What is the best way to proceed?
>     - Al, have you kept a temp version with all the changes?
>     - Are we shooting for "revised-ID" at the telechat? I could start my
> review from there
>     - Do we want to have a version 4 posted now?
>
> What is the best way to proceed?


I noticed Al sent a copy with updates that have been suggested
so far.

Please feel free to hit the "Defer" button if you don't feel
there's adequate time to review this one; it looks like a busy
telechat agenda this week!

--
Wes Eddy
MTI Systems