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

Simon Pietro Romano <spromano@unina.it> Tue, 31 May 2016 22:56 UTC

Return-Path: <spromano@unina.it>
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 4001E12D689 for <secdir@ietfa.amsl.com>; Tue, 31 May 2016 15:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level:
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=unavailable 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 hbZH6wdq0vth for <secdir@ietfa.amsl.com>; Tue, 31 May 2016 15:56:25 -0700 (PDT)
Received: from brc2.unina.it (brc2.unina.it [192.132.34.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1110312D8CA for <secdir@ietf.org>; Tue, 31 May 2016 15:56:20 -0700 (PDT)
X-ASG-Debug-ID: 1464733575-05f27567943a340001-mFDwdl
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by brc2.unina.it with ESMTP id r4PyzVnlLfBoZx3u (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO); Wed, 01 Jun 2016 00:26:15 +0200 (CEST)
X-Barracuda-Envelope-From: spromano@unina.it
X-Barracuda-Apparent-Source-IP: 192.132.34.62
Received: from [192.168.178.20] ([151.70.36.98]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id u4VMPvZM019594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Jun 2016 00:26:13 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail=_BF703B39-5497-45CF-B02A-2BF22C7A2829"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Simon Pietro Romano <spromano@unina.it>
X-ASG-Orig-Subj: Re: draft-ietf-clue-data-model-schema
In-Reply-To: <b47a27163186487e95f4eca2664dc860@usma1ex-dag1mb1.msg.corp.akamai.com>
Date: Wed, 1 Jun 2016 00:26:13 +0200
Message-Id: <64FC0FC3-A963-431B-ACD2-575720937AE9@unina.it>
References: <b47a27163186487e95f4eca2664dc860@usma1ex-dag1mb1.msg.corp.akamai.com>
To: "Salz, Rich" <rsalz@akamai.com>
X-Mailer: Apple Mail (2.2104)
X-Barracuda-Connect: smtp2.unina.it[192.132.34.62]
X-Barracuda-Start-Time: 1464733575
X-Barracuda-Encrypted: AES256-SHA
X-Barracuda-URL: http://192.132.34.42:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at unina.it
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=BSF_SC0_MISMATCH_TO, HTML_MESSAGE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.30065 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO Envelope rcpt doesn't match header 0.00 HTML_MESSAGE BODY: HTML included in message
Archived-At: <http://mailarchive.ietf.org/arch/msg/secdir/WTu-MyDkz1hQP8yxMf6Y-ckqkzU>
Cc: "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>
Subject: Re: [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: Tue, 31 May 2016 22:56:26 -0000

Hello Rich,

> Summary: this document is ready, perhaps with nits.

Great!

> 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.

No problem for us wrt to this. What do the chairs suggest?

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

:-))

Cheers,

Simon

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

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico II
                		     Computer Engineering Department 
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento รจ l'alibi degli 
		    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            (   )
			                                  \_)          ) /
                                                                       (_/