Skip to content

Commit 92e2279

Browse files
authored
Apply suggestion from @suhasHere
1 parent 23d908a commit 92e2279

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

draft-ietf-moq-transport.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -326,11 +326,11 @@ Reason Phrase {
326326

327327
## Representing Namespace and Track Names
328328

329-
There is often the need to render namespace tuples and track names in
330-
logs or other places. The namespace and track name are binary so they
331-
need to be converted to a safe form for logging. Having a common way to
332-
do this is particularly useful for tools that monitor security
333-
incidents across relays from different vendors. The following format is
329+
There is often the need to render namespace tuples and track names
330+
to be consumed for logging, representing track filename or in
331+
certain authorization verification schemes, for example. The namespace
332+
and track name are binary so they need to be converted to a safe
333+
form. The following format is
334334
RECOMMONDED:
335335

336336
* Each of the namespace tuples are rendered in order with a period

0 commit comments

Comments
 (0)