Skip to content

Commit

Permalink
Rephrase qlog field serialization rules
Browse files Browse the repository at this point in the history
This avoids any ambiguity about what we are talking about, avoiding
the need to import JSON terms.

Closes #340
  • Loading branch information
LPardue committed Dec 9, 2023
1 parent bd070df commit 2e5186b
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions draft-ietf-quic-qlog-main-schema.md
Original file line number Diff line number Diff line change
Expand Up @@ -1247,8 +1247,8 @@ be ".qlog". The Media Type, if any, SHOULD be "application/qlog+json" per
{{!RFC6839}}.

In accordance with {{Section 8.1 of !RFC8259}}, JSON files are required to use
UTF-8 both for the file itself and the string values it contains. In addition, all qlog
field names in a JSON serialization MUST be lowercase.
UTF-8 both for the file itself and the string values it contains. In addition,
all qlog field names MUST be lowercase when serialized to JSON.

In order to serialize CDDL-based qlog event and data structure
definitions to JSON, the official CDDL-to-JSON mapping defined in
Expand Down Expand Up @@ -1321,8 +1321,8 @@ When mapping qlog to JSON-SEQ, the "qlog_format" field MUST have the value
"JSON-SEQ". The file extension/suffix SHOULD be ".sqlog" (for "streaming" qlog).
The Media Type, if any, SHOULD be "application/qlog+json-seq" per {{!RFC8091}}.

While not specifically required by the JSON-SEQ specification, all qlog
field names in a JSON-SEQ serialization MUST be lowercase.
While not specifically required by the JSON-SEQ specification, all qlog field
names MUST be lowercase when serialized to JSON-SEQ.

In order to serialize all other CDDL-based qlog event and data structure
definitions to JSON-SEQ, the official CDDL-to-JSON mapping defined in
Expand Down

0 comments on commit 2e5186b

Please sign in to comment.