Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, RFC 7991, In Section 2.12, <br>

Heather Flanagan <rse@rfc-editor.org> Sat, 06 October 2018 15:03 UTC

Return-Path: <rse@rfc-editor.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6075127133 for <xml2rfc-dev@ietfa.amsl.com>; Sat, 6 Oct 2018 08:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 Ia_xf-GPV_0T for <xml2rfc-dev@ietfa.amsl.com>; Sat, 6 Oct 2018 08:03:25 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6020612426A for <xml2rfc-dev@ietf.org>; Sat, 6 Oct 2018 08:03:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 348EA1CA42E; Sat, 6 Oct 2018 08:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPWv-ANkoV_k; Sat, 6 Oct 2018 08:03:08 -0700 (PDT)
Received: from Heathers-MacBook-Pro.local (unknown [IPv6:2603:3023:30a:e7e0:1d1b:43c9:5488:d7d6]) by c8a.amsl.com (Postfix) with ESMTPSA id EF7B41C6297; Sat, 6 Oct 2018 08:03:07 -0700 (PDT)
To: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc-dev@ietf.org
References: <E1g6wQ8-00057n-85@durif.tools.ietf.org> <70ee4cff-7533-13e0-d71a-ffecf2dc56f0@gmx.de> <24828f94-dbbd-4c18-8d85-333487bda367@levkowetz.com> <3ac63652-2df2-03c7-eee6-bad2cbd326d8@levkowetz.com> <B63F3A7C-AAB6-4281-BC5F-BC28E9693E43@icann.org> <2ab7b797-4a01-5327-10fb-5ae13587944f@nostrum.com> <c9dc6869-148c-cdcc-06a4-94aeb2d6df57@levkowetz.com> <65f7d2f9-21ed-c7a1-a234-05e00e1c7dae@rfc-editor.org> <07c79cc9-5228-3eb4-32db-b2de53b480e7@levkowetz.com>
From: Heather Flanagan <rse@rfc-editor.org>
Message-ID: <38d5e402-cfc9-6927-cd7e-2c03feede59a@rfc-editor.org>
Date: Sat, 06 Oct 2018 08:03:20 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <07c79cc9-5228-3eb4-32db-b2de53b480e7@levkowetz.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/BVl0ij2lqV4jR9k7LpxIrbZBSj0>
Subject: Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, RFC 7991, In Section 2.12, <br>
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Oct 2018 15:03:27 -0000

On 10/6/18 6:04 AM, Henrik Levkowetz wrote:
> Hi Heather,
>
> On 2018-10-06 01:13, Heather Flanagan wrote:
>> Hola a todos!
>>
>> Apologies for letting this thread get a bit out of hand. Airplanes and
>> small, on-site meetings are not conducive to handling active threads.
>>
>> This isn't an IETF WG, but we're going to work along those models for
>> sake of clarity. Consider me the WG chair for the purpose of consensus
>> calls and breaking deadlock decisions.
> Thank you.  Much appreciated :-)  And good to have a decision on issue #37.
>
> Will you be summarizing where we stand on the other issues that have been
> posted to the list last week?  I expect to post a new batch of 5 on Monday.


Decisions are definitely good things! And I'm looking forward to the 
next batch - we are all working out some kinks on how we discuss these 
items, but that's not terribly surprising, and it will improve as we 
move ahead. That said, my current plan is to step in only where 
consensus is not clear. For issues like 34, 35, 36, and 39, the 
consensus seems straightforward. Any reason not to stay with that plan? 
If an issue is closed prematurely because of a misread on consensus, 
definitely make sure I'm aware (in case I miss it myself).

-Heather