[secdir] draft-ietf-clue-data-model-schema

"Salz, Rich" <rsalz@akamai.com> Thu, 19 May 2016 19:02 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id C5F4912D1EC; Thu, 19 May 2016 12:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.127
X-Spam-Status: No, score=-4.127 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_LOW=-0.7, 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=akamai.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id EYEN9HQVmIjy; Thu, 19 May 2016 12:02:51 -0700 (PDT)
Received: from prod-mail-xrelay05.akamai.com (prod-mail-xrelay05.akamai.com []) by ietfa.amsl.com (Postfix) with ESMTP id E811312DBEE; Thu, 19 May 2016 12:02:33 -0700 (PDT)
Received: from prod-mail-xrelay05.akamai.com (localhost.localdomain []) by postfix.imss70 (Postfix) with ESMTP id DA7DD42374B; Thu, 19 May 2016 19:02:32 +0000 (GMT)
Received: from prod-mail-relay11.akamai.com (prod-mail-relay11.akamai.com []) by prod-mail-xrelay05.akamai.com (Postfix) with ESMTP id C36844F0B8; Thu, 19 May 2016 19:02:32 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; s=a1; t=1463684552; bh=9T3k12/RVf9+J3wWBzjtJGYTGlOZAhhgCo2sFc/m5eo=; l=925; h=From:To:Date:From; b=SYpT4zfV8Sn63OAxiZrPxPOrYT9N5B/tzHEer3C/quo4bxyPYT8EkvmeLTgm2TAlO eMoLIqSFMK3RzKEv5yLt8i3d8wqXE4vSGObffbDOBX6scaoXP2qICigPeP5y6onKui OFRaUjzTMH0Ht6f6Yw8UUjJSCvVnhXoOwC6+oCHE=
Received: from email.msg.corp.akamai.com (ecp.msg.corp.akamai.com []) by prod-mail-relay11.akamai.com (Postfix) with ESMTP id BD14D1FC90; Thu, 19 May 2016 19:02:32 +0000 (GMT)
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ( by usma1ex-dag1mb6.msg.corp.akamai.com ( with Microsoft SMTP Server (TLS) id 15.0.1130.7; Thu, 19 May 2016 12:02:32 -0700
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([]) by usma1ex-dag1mb1.msg.corp.akamai.com ([]) with mapi id 15.00.1130.005; Thu, 19 May 2016 15:02:32 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "draft-ietf-clue-data-model-schema.all@ietf.org" <draft-ietf-clue-data-model-schema.all@ietf.org>, "'iesg@ietf.org'" <iesg@ietf.org>, "'secdir@ietf.org'" <secdir@ietf.org>
Thread-Topic: draft-ietf-clue-data-model-schema
Thread-Index: AdGx/5ZRRz2IzcDwTGqkTnDMmDGhPQ==
Date: Thu, 19 May 2016 19:02:31 +0000
Message-ID: <b47a27163186487e95f4eca2664dc860@usma1ex-dag1mb1.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/secdir/wULJF_cqzQghtxn3TV9I6r5VkoE>
Subject: [secdir] draft-ietf-clue-data-model-schema
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 19 May 2016 19:02:53 -0000

I have reviewed this document as part of the security directorate's  ongoing effort to review all IETF documents being processed by the 
IESG.  These comments were written primarily for the benefit of the security area directors.  Document editors and WG chairs should treat  these comments just like any other last call comments.

Summary: this document is ready, perhaps with nits.

You might consider reducing the security considerations part, just to increase emphasis on the fact that while the data described by this schema is potentially very privacy-impacting, it is the *protocol(s)* that need to address those issues.    Perhaps adding an intro sentence like that to the Sec 15 would be useful.

Thanks for the trip down my personal memory line.  Haven't deal with XML Schema since WS-star days :)

Senior Architect, Akamai Technologies
IM: richsalz@jabber.at Twitter: RichSalz