Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changelogs for -17 #2139

Merged
merged 8 commits into from Dec 14, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
12 changes: 12 additions & 0 deletions draft-ietf-quic-http.md
Expand Up @@ -1916,6 +1916,18 @@ Error codes need to be defined for HTTP/2 and HTTP/3 separately. See
## Since draft-ietf-quic-http-16

- Rename "HTTP/QUIC" to "HTTP/3" (#1973)
- Changes to PRIORITY frame (#1865, #2075)
- Permitted as first frame of request streams
- Remove exclusive reprioritization
- Changes to Prioritized Element Type bits
- Define DUPLICATE_PUSH frame to refer to another PUSH_PROMISE (#2072)
- Set defaults for settings, allow request before receiving SETTINGS (#1809,
#1846, #2038)
- Clarify message processing rules for streams that aren't closed (#1972, #2003)
- Removed reservation of error code 0 and moved HTTP_NO_ERROR to this value
(#1922)
- Removed prohibition of zero-length DATA frames (#2098)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change in PR #2098 was reverted.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reverted the change in definition of zero, but I kept the un-prohibition of sending zero-length frames. There seemed to be clear agreement that this was a preference, and there's no technical reason to prohibit it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh. Sorry for the noise.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problem -- CONSTANT VIGILANCE!!! 😉

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, right. Thanks for reverting my change @MikeBishop :-)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See, I knew that I'd checked that :)



## Since draft-ietf-quic-http-15

Expand Down
5 changes: 5 additions & 0 deletions draft-ietf-quic-qpack.md
Expand Up @@ -1252,6 +1252,11 @@ return controlBuffer, prefixBuffer + streamBuffer
> **RFC Editor's Note:** Please remove this section prior to publication of a
> final version of this document.

## Since draft-ietf-quic-qpack-04

- Changed calculation of Delta Base Index to avoid an illegal value (#2002,
#2005)

## Since draft-ietf-quic-qpack-03

Substantial editorial reorganization; no technical changes.
Expand Down
14 changes: 14 additions & 0 deletions draft-ietf-quic-recovery.md
Expand Up @@ -1259,6 +1259,20 @@ This document has no IANA actions. Yet.
> **RFC Editor's Note:** Please remove this section prior to
> publication of a final version of this document.

## Since draft-ietf-quic-recovery-15

- Redefine how congestion avoidance in terms of when the period starts (#1928,
#1930)
- Document what needs to be tracked for packets that are in flight (#765, #1724,
#1939)
- Integrate both time and packet thresholds into loss detection (#1969, #1212,
#934, #1974)
- Reduce congestion window after idle, unless pacing is used (#2007, #2023)
- Disable RTT calculation for packets that don't elicit acknowledgment (#2060,
#2078)
- Limit ack_delay by max_ack_delay (#2060, #2099)


## Since draft-ietf-quic-recovery-14

- Used max_ack_delay from transport params (#1796, #1782)
Expand Down
12 changes: 12 additions & 0 deletions draft-ietf-quic-tls.md
Expand Up @@ -1379,6 +1379,18 @@ values in the following registries:
Issue and pull request numbers are listed with a leading octothorp.


## Since draft-ietf-quic-tls-14

- Update the salt used for Initial secrets (#1970)
- Clarify that TLS_AES_128_CCM_8_SHA256 isn't supported (#2019)
- Change header protection
- Sample from a fixed offset (#1575, #2030)
- Cover part of the first byte, including the key phase (#1322, #2006)
- TLS provides an AEAD and KDF function (#2046)
- Clarify that the TLS KDF is used with TLS (#1997)
- Change the labels for calculation of QUIC keys (#1845, #1971, #1991)


## Since draft-ietf-quic-tls-13

- Updated to TLS 1.3 final (#1660)
Expand Down
24 changes: 24 additions & 0 deletions draft-ietf-quic-transport.md
Expand Up @@ -5441,6 +5441,30 @@ DecodePacketNumber(largest_pn, truncated_pn, pn_nbits):

Issue and pull request numbers are listed with a leading octothorp.

## Since draft-ietf-quic-transport-16

- Stream limits are defined as counts, not maximums (#1850, #1906)
- Require amplification attack defense after closing (#1905, #1911)
- Remove reservation of application error code 0 for STOPPING (#1804, #1922)
- Renumbered frames (#1945)
- Renumbered transport parameters (#1946)
- Numeric transport parameters are expressed as varints (#1608, #1947, #1955)
- Reorder the NEW_CONNECTION_ID frame (#1952, #1963)
- Rework the first byte (#2006)
- Fix the 0x40 bit
- Change type values for long header
- Add spin bit to short header (#631, #1988)
- Encrypt the remainder of the first byte (#1322)
- Move packet number length to first byte
- Simplify packet number protection (#1575)
- Allow STOP_SENDING to open a remote bidirectional stream (#1797, #2013)
- Added mitigation for off-path migration attacks (#1278, #1749, #2033)
- Don't let the PMTU to drop below 1280 (#2063, #2069)
- Require peers to replace retired connection IDs (#2085)
- Servers are required to ignore Version Negotiation packets (#2088)
- Tokens are repeated in all Initial packets (#2089)
- Clarified how PING frames are sent after loss (#2094)

## Since draft-ietf-quic-transport-15

Substantial editorial reorganization; no technical changes.
Expand Down