IETF Logo Mail Archive

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

"Roman D. Danyliw" <rdd@cert.org> Fri, 24 June 2016 18:09 UTC

Return-Path: <rdd@cert.org>
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 1802E12DD30; Fri, 24 Jun 2016 11:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 KIo__fK877Ru; Fri, 24 Jun 2016 11:09:37 -0700 (PDT)
Received: from shetland.sei.cmu.edu (shetland.sei.cmu.edu [192.58.107.44]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B98812DD1D; Fri, 24 Jun 2016 11:09:37 -0700 (PDT)
Received: from timber.sei.cmu.edu (timber.sei.cmu.edu [10.64.21.23]) by shetland.sei.cmu.edu (8.14.4/8.14.4/1543) with ESMTP id u5OI9XtL004343; Fri, 24 Jun 2016 14:09:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1466791773; bh=iw5WNPN/08gHE1R6qrPIIr9TFF2Nuw9fZbgJpbxYVOo=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version:Sender: Reply-To; b=DJTULQtXX37t/ehb+Y+fxVcz/6l7+dnepDxcJK2fJHcPEPeLTXngicSKQsQ/PDcpg etbNYcB1vTJ4+LvP2W5UN3I+/mxP2T1OI/QcLLAsRNrWEd6WsTB9WQDo8ELbCq3+99 EJ1aQkgH7SdUwWeVUvH/ItivQIzuWpnjhHyM0UH0=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by timber.sei.cmu.edu (8.14.4/8.14.4/1543) with ESMTP id u5OI9TO1013710; Fri, 24 Jun 2016 14:09:29 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0279.002; Fri, 24 Jun 2016 14:09:28 -0400
From: "Roman D. Danyliw" <rdd@cert.org>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Thread-Topic: Alexey Melnikov's Discuss on draft-ietf-mile-rfc5070-bis-22: (with DISCUSS and COMMENT)
Thread-Index: AQHRu9fuAmI2hngXOkWJ/PMYG+ecCJ/VoSKAgACF3wD///OT0IAcbq6wgAPBtgCAAvP7AP//zv6A
Date: Fri, 24 Jun 2016 18:09:28 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD976BA0C@marathon>
References: <20160601073339.16171.59393.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFCD974F85C@marathon> <1464858290.1234564.625673017.7541014D@webmail.messagingengine.com> <359EC4B99E040048A7131E0F4E113AFCD97500C7@marathon> <359EC4B99E040048A7131E0F4E113AFCD976686D@marathon> <CAHbuEH54VwDJsoTFBik6Tr20WCHNgXea1DMzcHGQiBK_dMV8bA@mail.gmail.com> <1466787578.3424901.647604393.320171FC@webmail.messagingengine.com>
In-Reply-To: <1466787578.3424901.647604393.320171FC@webmail.messagingengine.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/InQjuqREsq7AjXnKJlPxfUW_XFI>
Cc: "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "mile-chairs@ietf.org" <mile-chairs@ietf.org>, "mile@ietf.org" <mile@ietf.org>, "draft-ietf-mile-rfc5070-bis@ietf.org" <draft-ietf-mile-rfc5070-bis@ietf.org>
Subject: Re: [mile] Alexey Melnikov'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 18:09:39 -0000

Hello Alexey!

> -----Original Message-----
> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
> Sent: Friday, June 24, 2016 1:00 PM
> To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>; Roman D.
> Danyliw <rdd@cert.org>
> Cc: mile-chairs@tools.ietf.org; takeshi_takahashi@nict.go.jp; The IESG
> <iesg@ietf.org>; mile-chairs@ietf.org; mile@ietf.org; draft-ietf-mile-rfc5070-
> bis@ietf.org
> Subject: Re: Alexey Melnikov's Discuss on draft-ietf-mile-rfc5070-bis-22:
> (with DISCUSS and COMMENT)
> 
> Hi Kathleen/Roman,
> 
> On Wed, Jun 22, 2016, at 08:53 PM, Kathleen Moriarty wrote:
> > Hi Alexey,
> >
> > Do the recent updates address your concerns?
> 
> The latest version is an improvement.
> 
> One final point I am uncomfortable with:
> 
> 4.3.  Validation
> 
>    IODEF documents MUST be well-formed XML.  It is RECOMMENDED that
>    recipients validate the document against the schema described in
>    Section 8.  However, mere conformance to this schema is not
>    sufficient for a semantically valid IODEF document.  The text of
>    Section 3 describes further formatting and constraints; some that
>    cannot be conveniently encoded in the schema.  These MUST also be
>    considered by an IODEF implementation.  Furthermore, the enumerated
>    values present in this document are a static list that will be
>    incomplete over time as select attributes can be extended by a
>    corresponding IANA registry per Section 10.2.  Therefore, IODEF
>    implementations MUST periodically update their schema and MAY need to
>    update their parsing algorithms to incorporate newly registered
>    values.
> 
> How realistic is this to require all implementations to update their schema? Is
> IODEFv2 intended to be used by IoT devices that might not have much
> battery/CPU power to do this?
> (I appreciate that this is different from my original DISCUSS point, but this is
> related to a change that was caused by my DISCUSS. So I would like to discuss
> this quickly.)

Makes sense.  What about updating the text to read: "IODEF implementation SHOULD periodically ... ".

Roman

v2.23.0 | Report a Bug | By Email