Skip to content

Consolidate security sections in Hyper-Schema? #376

Closed
@handrews

Description

@handrews

I find that having three big blobs of security discussion in the middle of the LDO definition makes it harder to follow what is going on.

Does anyone feel strongly about keeping them where they are, or can I just stuff them down as three subsections under a "Security Considerations" section? Such a section is definitely common in RFCs.

I would also add a cross-reference from the keywords with specific security concerns to the appropriate "Security Considerations" subsection.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions