IETF Logo Mail Archive

Re: [mile] [IANA #921487] Protocol Action: 'The Incident Object Description Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-25.txt)

"Roman D. Danyliw" <rdd@cert.org> Mon, 22 August 2016 20:10 UTC

Return-Path: <rdd@cert.org>
X-Original-To: expand-draft-ietf-mile-rfc5070-bis.all@virtual.ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 5D7A512D7F7; Mon, 22 Aug 2016 13:10:31 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C9F12D80C for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Mon, 22 Aug 2016 13:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level:
X-Spam-Status: No, score=-4.32 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 8urhzydAIAoO for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Mon, 22 Aug 2016 13:10:29 -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 E795912D7F7 for <draft-ietf-mile-rfc5070-bis.all@ietf.org>; Mon, 22 Aug 2016 13:10:25 -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 u7MK8dfI002039; Mon, 22 Aug 2016 16:08:39 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1471896519; bh=ftsDVnuOK0ra9l/gsEtd8Ggbb1OACbaJUwdmABpBH28=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version:Sender: Reply-To; b=gjX0jrgywzdlgo0StT+bX6tmmnSJP8xhMiN69I8wP4S77bD+B8rbui6wDLT+6iG+l nUVK5eZ3O4Loriv+rOWhajOhui5X2UYK4ruq6LEZ8EtHDoDqW9vcprSvumvYqvMGpX 1Q90zK7K6e4rxmw7cqfnUKGitkk9P6MIyKhrWtD8=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by timber.sei.cmu.edu (8.14.4/8.14.4/1543) with ESMTP id u7MK8cAG020477; Mon, 22 Aug 2016 16:08:38 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0279.002; Mon, 22 Aug 2016 16:08:38 -0400
From: "Roman D. Danyliw" <rdd@cert.org>
To: "drafts-approval@iana.org" <drafts-approval@iana.org>
Thread-Topic: [IANA #921487] Protocol Action: 'The Incident Object Description Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-25.txt)
Thread-Index: AQHR+LypxT+z9uAV0E6+i4uYGkmJ76BVby2A
Date: Mon, 22 Aug 2016 20:08:38 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC0104E3AFB6@marathon>
References: <RT-Ticket-921487@icann.org> <20160803150200.6140.54785.idtracker@ietfa.amsl.com> <rt-4.2.9-15788-1471460942-1043.921487-7-0@icann.org>
In-Reply-To: <rt-4.2.9-15788-1471460942-1043.921487-7-0@icann.org>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Resent-From: alias-bounces@ietf.org
Resent-To: rdd@cert.org, ncamwing@cisco.com, takeshi_takahashi@nict.go.jp, david.waltermire@nist.gov, Kathleen.Moriarty.ietf@gmail.com, stephen.farrell@cs.tcd.ie, mile-chairs@tools.ietf.org, mile@ietf.org
Resent-Message-Id: <20160822201032.5D7A512D7F7@ietfa.amsl.com>
Resent-Date: Mon, 22 Aug 2016 13:10:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/sZ4_Qr-nLarADUtI6JJ3H5TgN3Q>
Cc: "draft-ietf-mile-rfc5070-bis.all@ietf.org" <draft-ietf-mile-rfc5070-bis.all@ietf.org>
Subject: Re: [mile] [IANA #921487] Protocol Action: 'The Incident Object Description Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-25.txt)
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: Mon, 22 Aug 2016 20:10:32 -0000

Good afternoon Amanda!

Coming back from vacation.

Ack on this email and thank you for the review!

(1) Let me check on the TimeZone issue.  This was a requested change from IESG review.

(2) Could the reviewer share a bit more context on "schemaLocation" not being a good idea.  Is there a better way?

I'd prefer to change now rather than AUTH48 if there is anything to do.

Roman

> -----Original Message-----
> From: Amanda Baber via RT [mailto:drafts-approval@iana.org]
> Sent: Wednesday, August 17, 2016 3:09 PM
> Cc: draft-ietf-mile-rfc5070-bis.all@ietf.org
> Subject: [IANA #921487] Protocol Action: 'The Incident Object Description
> Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-
> 25.txt)
> 
> Dear Roman,
> 
> The actions for this document are complete. The designated expert for the
> XML registries, however, has comments:
> 
> "It looks good. Two nits:
> 
> schemaLocation attributes are a bad idea the definition of TimeZone allows
> for seconds, which is unnecessary (I think)"
> 
> If you want to make changes during AUTH48, the RFC Editor will contact us
> and tell us which updates to make. Alternatively, if you want to make
> changes now, just let us know.
> 
> Please review the actions below and let us know whether we've completed
> them correctly. When we receive your confirmation, we'll tell the RFC Editor
> the IANA actions are complete.
> 
> ACTION 1:
> 
> IANA has added the following entry to the IETF XML ns registry:
> 
> iodef-2.0
> urn:ietf:params:xml:ns:iodef-2.0
> http://www.iana.org/assignments/xml-registry/ns/iodef-2.0.txt
> [RFC-ietf-mile-rfc5070-bis-25]
> 
> Please see
> http://www.iana.org/assignments/xml-registry
> 
> 
> ACTION 2:
> 
> IANA has added the following entry to the IESG XML schema registry:
> 
> iodef-2.0
> urn:ietf:params:xml:schema:iodef-2.0
> http://www.iana.org/assignments/xml-registry/schema/iodef-2.0.xsd
> [RFC-ietf-mile-rfc5070-bis-25]
> 
> Please see
> http://www.iana.org/assignments/xml-registry
> 
> 
> ACTION 3:
> 
> IANA has created 34 registries under the "Incident Object Description
> Exchange Format v2 (IODEF)" heading at
> 
> http://www.iana.org/assignments/iodef2
> 
> 
> Can we tell the RFC Editor these are complete?
> 
> Best regards,
> 
> Amanda Baber
> IANA Lead Specialist
> ICANN

v2.23.0 | Report a Bug | By Email