IETF Logo Mail Archive

Re: [clue] Kathleen Moriarty's Discuss on draft-ietf-clue-data-model-schema-14: (with DISCUSS)

kathleen.moriarty.ietf@gmail.com Wed, 01 June 2016 18:10 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC0F12D1AF; Wed, 1 Jun 2016 11:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WLMHqsyVOnCq; Wed, 1 Jun 2016 11:10:09 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8727B12D09D; Wed, 1 Jun 2016 11:10:09 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id y126so20968900qke.1; Wed, 01 Jun 2016 11:10:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4f3yZC0szKsXnY7m9L6qJ+1yFUfvFgbiDhw1fJ4zROE=; b=rSL5Brxj91ByWNSHhMYRWHEZIh5z1QxophsNqytMu9yNyXp2OKoQVzdhA765j0A3s9 6TSlXo8c0QCd7/LHPqXX/xnGqojt8GvUAqMdPnta2iH36cwQkqgW7eTjTBcRf1b8+1yL hiJsTV8oel5+FtJ12z8fQFt/MHpxKsAR+2TCTpuyTAWr+wgmudyRFtI/RrWV1MLmzRNN 5KUGe7g93oASHH2T3CZgkDZ+Q5sqbZpLyeUoAEELIuiISYeLVb+q593HkXlnx6ZY/Mh7 4whRdzO3hgCgAbCGfmLCtsJwDfz9OcCZ05YNm+rmvl9XrPfkuJ4JPoke7cG1HEL3AVYb SFPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4f3yZC0szKsXnY7m9L6qJ+1yFUfvFgbiDhw1fJ4zROE=; b=KJVwgIWaiMuhO4Rv2aNYzeWTClkhEaIz5VRQ4XxoZAscWG7SaPQWLWLXjJi4KvQ0X3 lL6ogq+b36YsEyatVuv+v7ctW+b/zgqHHurV+VKdg8QJFR9nVcpzRYN21VrjXcPKyHAt bq7SoVorsg4K/wdTMKWrlwJmj0YEmUDgt9DWI/Z7s52/gZF9d8AaZQnD8UK+BVCyZOpw 5KO3bjfoaobjQ/XChKLrLq4sE0Y8FJmuRuacLmXH2xGdQ2RH4hFBVF6syi/rWAeo3pXk UWWhvzBwxWRNYcxbWflZptmNgrSw6efsmlJYBO2ms3DQPA9WY5meCHG7hf6mAQQ8+2YH WqbQ==
X-Gm-Message-State: ALyK8tL0eyioOoMJsXabfVIZtf1yvWOK6WIIZ0hQo3r0Gx3RkauYnA8shMDtcgC85FtQGg==
X-Received: by 10.55.104.68 with SMTP id d65mr18321503qkc.190.1464804608469; Wed, 01 Jun 2016 11:10:08 -0700 (PDT)
Received: from [192.168.1.6] (209-6-124-204.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.124.204]) by smtp.gmail.com with ESMTPSA id 7sm9887328qto.21.2016.06.01.11.10.07 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 01 Jun 2016 11:10:07 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: kathleen.moriarty.ietf@gmail.com
X-Mailer: iPhone Mail (12H143)
In-Reply-To: <45F69808-DBC1-4A03-95B2-7E8357F59034@cooperw.in>
Date: Wed, 01 Jun 2016 14:10:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A74E266-B15A-4449-9258-7AB19449D1C7@gmail.com>
References: <20160531213800.20195.51327.idtracker@ietfa.amsl.com> <45F69808-DBC1-4A03-95B2-7E8357F59034@cooperw.in>
To: Alissa Cooper <alissa@cooperw.in>
Archived-At: <http://mailarchive.ietf.org/arch/msg/clue/G2dwnmsiuiPo5MEe3hGI-Z5f5u8>
Cc: "clue-chairs@ietf.org" <clue-chairs@ietf.org>, CLUE <clue@ietf.org>, IESG <iesg@ietf.org>, "draft-ietf-clue-data-model-schema@ietf.org" <draft-ietf-clue-data-model-schema@ietf.org>
Subject: Re: [clue] Kathleen Moriarty's Discuss on draft-ietf-clue-data-model-schema-14: (with DISCUSS)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2016 18:10:12 -0000


Sent from my iPhone

> On Jun 1, 2016, at 1:27 PM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> Hi Kathleen,
> 
>> On May 31, 2016, at 2:38 PM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> wrote:
>> 
>> Kathleen Moriarty has entered the following ballot position for
>> draft-ietf-clue-data-model-schema-14: Discuss
>> 
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>> 
>> 
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>> 
>> 
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-clue-data-model-schema/
>> 
>> 
>> 
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>> 
>> The document looks good, I just have a couple of items on the security
>> considerations to discuss as they are not mentioned and I'm not sure if
>> they have a good reason to be excluded.
>> 
>> 1. Session encryption to prevent active (tampering) or passive
>> (information gathering for example) attacks.  Integrity protection and
>> authentication are mentioned, but without looking through a few
>> documents, I don't know if that means encryption or some hash value
>> comparisons or something else.
> 
> This is covered in the documents referenced in Section 25: draft-ietf-clue-framework, draft-ietf-clue-datachannel, and draft-ietf-clue-protocol.
> 
Thanks, Alissa!  I should have checked, but ran out of time yesterday and wanted yo get this out.  I'll wait for a response on #2, then update comments.

Kathleen 

> Alissa
> 
>> 
>> 2. Schema drafts tend to cover the need for well-formed schemas as part
>> of the security considerations.  Can you add something in about that (not
>> much is required, but it's good for implementers to know this is
>> important)?  You can see two recent examples for guidance:
>> YANG - https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc6020bis/
>> IODEF - https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/
>> 
>> 
>> 
>> 
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>

v2.23.0 | Report a Bug | By Email