Re: [mile] Stephen Farrell's Discuss on draft-ietf-mile-rfc5070-bis-22: (with DISCUSS and COMMENT)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 24 June 2016 19:15 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BBEE12D5AA; Fri, 24 Jun 2016 12:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level:
X-Spam-Status: No, score=-5.727 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_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 HectwGY8LQG2; Fri, 24 Jun 2016 12:15:15 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0910F12D59E; Fri, 24 Jun 2016 12:15:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id AD05FBDF9; Fri, 24 Jun 2016 20:15:12 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kruf8D1Mbh2m; Fri, 24 Jun 2016 20:15:11 +0100 (IST)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 69C7ABE29; Fri, 24 Jun 2016 20:15:10 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1466795710; bh=7MDjmAXjDyRp7SihAsBQ/taHWW6SK0kNj+Wa1EvpxG8=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=hfXpjVeHT4Icj80mRJY4Nuh4YZ35uaMYqFBjK4ibb2s0cBJSmHDHQeuY7cg7L7+OH 0Tskj6i/rIvgsLA25WwuoIrk3pBP+gYNI2Wl0G9503RrnaR9AvV4JkdPI/Sym1VEIr Q55CmsYQvDF7g85S5vB2aOEjxLIs8paIdKIvbXL8=
To: "Roman D. Danyliw" <rdd@cert.org>, The IESG <iesg@ietf.org>
References: <20160601234150.16188.9970.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFCD974F737@marathon> <5750568A.7020302@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD97669C8@marathon> <576C2DDC.8000606@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD976BA35@marathon>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <576D86BE.8010301@cs.tcd.ie>
Date: Fri, 24 Jun 2016 20:15:10 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD976BA35@marathon>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms040202010304030703080008"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/P9DMAso6MFi5CD1BeUCIsP8fI9A>
Cc: "mile@ietf.org" <mile@ietf.org>, "draft-ietf-mile-rfc5070-bis@ietf.org" <draft-ietf-mile-rfc5070-bis@ietf.org>, "mile-chairs@ietf.org" <mile-chairs@ietf.org>, "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>
Subject: Re: [mile] Stephen Farrell's Discuss on draft-ietf-mile-rfc5070-bis-22: (with DISCUSS and COMMENT)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2016 19:15:17 -0000

Hiya,

On 24/06/16 19:22, Roman D. Danyliw wrote:
>> > TBH, I wonder if the right thing here is to say that documents
>> > with ambiguous confidence elements MUST be treated as if the
>> > confidence element were omitted.
>> > 
>> > Would that work?
> Definitely.  Would this last sentence address your concern:
> 
> "... While the sender of the 
> document may explicitly convey confidence in the data in a granular
> way using the Confidence class, the recipient is free to ignore or
> refine this information to make its own assessment.  
> [start new text]
> Ambiguous Confidence elements in a document MUST be ignored by the recipient.
> "
> 
> It's a restatement of your suggestion to match the existing style of the text.

That'd work for me. I'd word it more like:

"Ambiguous Confidence elements (where it is unclear to which of a set
of other elements the Confidence element relates) in a document MUST be
ignored by the recipient."

I'd still clear on yours, but saying what we mean by ambiguous would I
think be better. I'm fine if you want to use more words to be even more
precise about that.

Cheers,
S.