Merging a few of the replies into a single response:
> I like all of this plan, except for the name "Overview". To me,
"Overview" suggests a high-level summary rather than being "one of the
beefier sections of a spec". Something like "Detail" or "Detailed
overview" (because the low-level detai
On 21/05/14 22:56, James Slagle wrote:
> On Wed, May 21, 2014 at 4:37 PM, Jay Dobies wrote:
>> Currently, there is the following in the template:
>>
>>
>>
>> Proposed change
>> ===
>>
>> [snip]
>>
>> Alternatives
>>
>>
>> [snip]
>>
>> Security impact
>> ---
>>
We just landed a change to permit the third level subsections, but the
intent AIUI of requiring exact titles to constrain the expression
space in the interests of clarity. We can (and should) add more
standard sections as needed.
-Rob
On 22 May 2014 08:37, Jay Dobies wrote:
> Currently, there is
On Wed, May 21, 2014 at 4:37 PM, Jay Dobies wrote:
> Currently, there is the following in the template:
>
>
>
> Proposed change
> ===
>
> [snip]
>
> Alternatives
>
>
> [snip]
>
> Security impact
> ---
>
>
>
> The unit tests assert the top and second level secti
On Wed, May 21, 2014 at 4:37 PM, Jay Dobies wrote:
> Currently, there is the following in the template:
>
>
>
> Proposed change
> ===
>
> [snip]
>
> Alternatives
>
>
> [snip]
>
> Security impact
> ---
>
>
>
> The unit tests assert the top and second level sect
Currently, there is the following in the template:
Proposed change
===
[snip]
Alternatives
[snip]
Security impact
---
The unit tests assert the top and second level sections are standard, so
if I add a section at the same level as Alternatives under
