Re: [mile] early AD-review of draft-ietf-mile-template
<kathleen.moriarty@emc.com> Wed, 09 May 2012 21:00 UTC
Return-Path: <kathleen.moriarty@emc.com>
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 EEB8621F847F for <mile@ietfa.amsl.com>; Wed, 9 May 2012 14:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.554
X-Spam-Level:
X-Spam-Status: No, score=-10.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KnTo8clE1Dof for <mile@ietfa.amsl.com>; Wed, 9 May 2012 14:00:28 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 39BB021F847E for <mile@ietf.org>; Wed, 9 May 2012 14:00:27 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q49L0Oju020651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 May 2012 17:00:26 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 9 May 2012 17:00:15 -0400
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.222.70.135]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q49L0FeH020992; Wed, 9 May 2012 17:00:15 -0400
Received: from mx06a.corp.emc.com ([169.254.1.116]) by mxhub23.corp.emc.com ([128.222.70.135]) with mapi; Wed, 9 May 2012 17:00:15 -0400
From: kathleen.moriarty@emc.com
To: turners@ieca.com, trammell@tik.ee.ethz.ch
Date: Wed, 09 May 2012 17:00:14 -0400
Thread-Topic: [mile] early AD-review of draft-ietf-mile-template
Thread-Index: Ac0t/eR0jj8FGC3USY+NI1En5oltAgAKKVRw
Message-ID: <AE31510960917D478171C79369B660FA0E969C04E8@MX06A.corp.emc.com>
References: <4F999FB4.5070403@ieca.com> <4DE7695F-C053-4676-A313-DA08652082C6@tik.ee.ethz.ch> <4FAA81D2.8050802@ieca.com> <B037668C-B6FA-486A-B1A2-FB6F04F4FFC6@tik.ee.ethz.ch> <A31D5C9F-F47C-447D-91DA-247B68CA66FD@ieca.com>
In-Reply-To: <A31D5C9F-F47C-447D-91DA-247B68CA66FD@ieca.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] early AD-review of draft-ietf-mile-template
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 May 2012 21:00:29 -0000
Hello Brian, Thank you for making all of the requested changes. It appears all recommended changes were addressed in this WGLC. The document is ready for IESG last call. Thank you, Kathleen -----Original Message----- From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Sean Trner Sent: Wednesday, May 09, 2012 11:55 AM To: Brian Trammell Cc: mile@ietf.org Subject: Re: [mile] early AD-review of draft-ietf-mile-template Absolutely. Spt Sent from my iPhone On May 9, 2012, at 11:47 AM, Brian Trammell <trammell@tik.ee.ethz.ch> wrote: > > On May 9, 2012, at 4:40 PM, Sean Turner wrote: > >>>> 12) A.8 and A.9 and I guess all appendices in this draft, should we require that they explicitly be marked as normative parts of the document? >>> >>> A.8 and A.9 are weird, in that they're appendices within an appendix. Examples are definitely informative. The XML schema should be normative; however, technically, I would presume it's the schema that goes into the IANA registry (which, of course, in the normal case, gets taken from the schema in Appendix A of an extension document) which is normative. >> >> So I guess adding a sentence in A.8/A.9 to say something like "When the draft is produced this Appendix should be marked as normative" and "When the draft is produced this Appendix should be marked as informative" would work for me. > > Okay, that makes sense. (As I've already submitted an -04, would it be okay to hold this for -05 pending other IESG commentary, presuming there's nothing else that needs to be done before then?) > > Cheers, > > Brian (author hat) >
- [mile] early AD-review of draft-ietf-mile-template Sean Turner
- Re: [mile] early AD-review of draft-ietf-mile-tem… kathleen.moriarty
- Re: [mile] early AD-review of draft-ietf-mile-tem… Sean Turner
- Re: [mile] early AD-review of draft-ietf-mile-tem… Brian Trammell
- Re: [mile] early AD-review of draft-ietf-mile-tem… Sean Turner
- Re: [mile] early AD-review of draft-ietf-mile-tem… Brian Trammell
- Re: [mile] early AD-review of draft-ietf-mile-tem… Sean Trner
- Re: [mile] early AD-review of draft-ietf-mile-tem… kathleen.moriarty