[quicwg/base-drafts] Backticks around parameter names (#3609)

Mike Bishop <notifications@github.com> Wed, 29 April 2020 15:55 UTC

Date: Wed, 29 Apr 2020 08:55:09 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3TRLVIDJX7D5KXDA54WWCF3EVBNHHCITZMLA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3609@github.com>
Subject: [quicwg/base-drafts] Backticks around parameter names (#3609)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ea9a35dec4ff_67dd3fdf4facd96018048fb"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/uZgqTexhxay9cQoyY5BN-dOxMLQ>

We're somewhat inconsistent about whether transport parameters et al. get backticks or not across the documents.  For example,

>   the ACK Delay field is scaled by multiplying the encoded value by 2 to the
>  power of the value of the `ack_delay_exponent` transport parameter set by the
>  sender of the ACK frame; see {{transport-parameter-definitions}}.  Scaling in

> The Retire Prior To field counts connection IDs established during connection
> setup and the preferred_address transport parameter; see {{retiring-cids}}. The
> Retire Prior To field MUST be less than or equal to the Sequence Number field.

Same goes for error code names, frame types, etc.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3609

[quicwg/base-drafts] Backticks around parameter n… Mike Bishop
Re: [quicwg/base-drafts] Backticks around paramet… Martin Thomson
Re: [quicwg/base-drafts] Backticks around paramet… Martin Thomson