draft-ietf-quic-spin-exp-00.txt   draft-ietf-quic-spin-exp-01.txt 
QUIC B. Trammell, Ed. QUIC B. Trammell, Ed.
Internet-Draft M. Kuehlewind Internet-Draft M. Kuehlewind
Intended status: Experimental ETH Zurich Intended status: Experimental ETH Zurich
Expires: October 28, 2018 April 26, 2018 Expires: April 26, 2019 October 23, 2018
The QUIC Latency Spin Bit The QUIC Latency Spin Bit
draft-ietf-quic-spin-exp-00 draft-ietf-quic-spin-exp-01
Abstract Abstract
This document specifies the addition of a latency spin bit to the This document specifies the addition of a latency spin bit to the
QUIC transport protocol and describes how to use it to measure end- QUIC transport protocol and describes how to use it to measure end-
to-end latency. to-end latency.
Note to Readers Note to Readers
This document specifies an experimental delta to the QUIC transport This document specifies an experimental delta to the QUIC transport
skipping to change at page 2, line 12 skipping to change at page 2, line 12
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 28, 2018. This Internet-Draft will expire on April 26, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Spin Bit Mechanism . . . . . . . . . . . . . . . . . . . 3 2. The Spin Bit Mechanism . . . . . . . . . . . . . . . . . . . 3
2.1. Proposed Short Header Format Including Spin Bit . . . . . 3 2.1. Proposed Short Header Format Including Spin Bit . . . . . 3
2.2. Setting the Spin Bit on Outgoing Packets . . . . . . . . 4 2.2. Setting the Spin Bit on Outgoing Packets . . . . . . . . 4
2.3. Resetting Spin Value State . . . . . . . . . . . . . . . 4 2.3. Resetting Spin Value State . . . . . . . . . . . . . . . 4
3. Using the Spin Bit for Passive RTT Measurement . . . . . . . 4 3. Using the Spin Bit for Passive RTT Measurement . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security and Privacy Considerations . . . . . . . . . . . . . 5 5. Security and Privacy Considerations . . . . . . . . . . . . . 6
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 6. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.1. Since draft-ietf-spin-exp-00 . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 7
8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
The QUIC transport protocol [QUIC-TRANSPORT] uses Transport Layer The QUIC transport protocol [QUIC-TRANSPORT] uses Transport Layer
Security (TLS) [TLS] to encrypt most of its protocol internals. In Security (TLS) [TLS] to encrypt most of its protocol internals. In
contrast to TCP where the sequence and acknowledgement numbers and contrast to TCP where the sequence and acknowledgement numbers and
timestamps (if the respective option is in use) can be seen by on- timestamps (if the respective option is in use) can be seen by on-
path observers and used to estimate end-to-end latency, QUIC's wire path observers and used to estimate end-to-end latency, QUIC's wire
image (see [WIRE-IMAGE]) currently does not expose any information image (see [WIRE-IMAGE]) currently does not expose any information
skipping to change at page 3, line 34 skipping to change at page 3, line 41
2.1. Proposed Short Header Format Including Spin Bit 2.1. Proposed Short Header Format Including Spin Bit
As of the current editor's version of [QUIC-TRANSPORT], this proposal As of the current editor's version of [QUIC-TRANSPORT], this proposal
specifies using the sixth most significant bit (0x04) of the first specifies using the sixth most significant bit (0x04) of the first
octet in the short header for the spin bit. octet in the short header for the spin bit.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|0|K|1|1|0|S|T T| |0|K|1|1|0|S|R R|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0..144) ... | Destination Connection ID (0..144) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packet Number (8/16/32) ... | Packet Number (8/16/32) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protected Payload (*) ... | Protected Payload (*) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Short Header Format including proposed Spin Bit Figure 1: Short Header Format including proposed Spin Bit
S: The Spin bit is set 0 or 1 depending on the stored spin value that S: The Spin bit is set 0 or 1 depending on the stored spin value that
is updated on packet reception as explained in Section 2.2. is updated on packet reception as explained in Section 2.2.
R: Two additional bits are reserved for experimentation in the short
header.
2.2. Setting the Spin Bit on Outgoing Packets 2.2. Setting the Spin Bit on Outgoing Packets
Each endpoint, client and server, maintains a spin value, 0 or 1, for Each endpoint, client and server, maintains a spin value, 0 or 1, for
each QUIC connection, and sets the spin bit in the short header to each QUIC connection, and sets the spin bit in the short header to
the currently stored value when a packet with a short header is sent the currently stored value when a packet with a short header is sent
out. The spin value is initialized to 0 at each endpoint, client and out. The spin value is initialized to 0 at each endpoint, client and
server, at connection start. Each endpoint also remembers the server, at connection start. Each endpoint also remembers the
highest packet number seen from its peer on the connection. highest packet number seen from its peer on the connection.
The spin value is then determined at each endpoint within a single The spin value is then determined at each endpoint within a single
skipping to change at page 6, line 4 skipping to change at page 6, line 10
4. IANA Considerations 4. IANA Considerations
This document has no actions for IANA. This document has no actions for IANA.
5. Security and Privacy Considerations 5. Security and Privacy Considerations
The spin bit is intended to expose end-to-end RTT to observers along The spin bit is intended to expose end-to-end RTT to observers along
the path, so the privacy considerations for the latency spin bit are the path, so the privacy considerations for the latency spin bit are
essentially the same as those for passive RTT measurement in general. essentially the same as those for passive RTT measurement in general.
It has been shown [PAM-RTT] that RTT measurements do not provide more It has been shown [PAM-RTT] that RTT measurements do not provide more
information for geolocation than is available in the most basic, information for geolocation than is available in the most basic,
freely-available IP address based location databases. The risk of freely-available IP address based location databases. The risk of
exposure of per-flow network RTT to on-path devices is therefore exposure of per-flow network RTT to on-path devices is therefore
negligible. negligible.
6. Acknowledgments 6. Change Log
This document is derived from [I-D.trammell-quic-spin], which was the *RFC Editor's Note:* Please remove this section prior to
work of the following authors in addition to the editor of this publication of a final version of this document.
document:
6.1. Since draft-ietf-spin-exp-00
Nothing yet.
Acknowledgments
This document is derived from [QUIC-SPIN], which was the work of the
following authors in addition to the editor of this document:
o Piet De Vaere, ETH Zurich o Piet De Vaere, ETH Zurich
o Roni Even, Huawei o Roni Even, Huawei
o Giuseppe Fioccola, Telecom Italia o Giuseppe Fioccola, Telecom Italia
o Thomas Fossati, Nokia o Thomas Fossati, Nokia
o Marcus Ihlar, Ericsson o Marcus Ihlar, Ericsson
skipping to change at page 6, line 40 skipping to change at page 7, line 5
The QUIC Spin Bit was originally specified in a slightly different The QUIC Spin Bit was originally specified in a slightly different
form by Christian Huitema. form by Christian Huitema.
This work is partially supported by the European Commission under This work is partially supported by the European Commission under
Horizon 2020 grant agreement no. 688421 Measurement and Architecture Horizon 2020 grant agreement no. 688421 Measurement and Architecture
for a Middleboxed Internet (MAMI), and by the Swiss State Secretariat for a Middleboxed Internet (MAMI), and by the Swiss State Secretariat
for Education, Research, and Innovation under contract no. 15.0268. for Education, Research, and Innovation under contract no. 15.0268.
This support does not imply endorsement. This support does not imply endorsement.
7. References 8. References
7.1. Normative References 8.1. Normative References
[QUIC-TRANSPORT] [QUIC-TRANSPORT]
Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
Multiplexed and Secure Transport", draft-ietf-quic- Multiplexed and Secure Transport", draft-ietf-quic-
transport-12 (work in progress), April 2018. transport-15 (work in progress), October 2018.
7.2. Informative References 8.2. Informative References
[CACM-TCP] [CACM-TCP]
Strowes, S., "Passively Measuring TCP Round-Trip Times (in Strowes, S., "Passively Measuring TCP Round-Trip Times (in
Communications of the ACM)", October 2013. Communications of the ACM)", October 2013.
[I-D.trammell-quic-spin]
Trammell, B., Vaere, P., Even, R., Fioccola, G., Fossati,
T., Ihlar, M., Morton, A., and S. Emile, "Adding Explicit
Passive Measurability of Two-Way Latency to the QUIC
Transport Protocol", draft-trammell-quic-spin-02 (work in
progress), April 2018.
[PAM-RTT] Trammell, B. and M. Kuehlewind, "Revisiting the Privacy [PAM-RTT] Trammell, B. and M. Kuehlewind, "Revisiting the Privacy
Implications of Two-Way Internet Latency Data (in Proc. Implications of Two-Way Internet Latency Data (in Proc.
PAM 2018)", March 2018. PAM 2018)", March 2018.
[QUIC-SPIN] [QUIC-SPIN]
Trammell, B., Vaere, P., Even, R., Fioccola, G., Fossati, Trammell, B., Vaere, P., Even, R., Fioccola, G., Fossati,
T., Ihlar, M., Morton, A., and S. Emile, "Adding Explicit T., Ihlar, M., Morton, A., and S. Emile, "Adding Explicit
Passive Measurability of Two-Way Latency to the QUIC Passive Measurability of Two-Way Latency to the QUIC
Transport Protocol", draft-trammell-quic-spin-02 (work in Transport Protocol", draft-trammell-quic-spin-03 (work in
progress), April 2018. progress), May 2018.
[TLS] Rescorla, E., "The Transport Layer Security (TLS) Protocol [TLS] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", draft-ietf-tls-tls13-28 (work in progress), Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
March 2018. <https://www.rfc-editor.org/info/rfc8446>.
[TMA-QOF] Trammell, B., Gugelmann, D., and N. Brownlee, "Inline Data [TMA-QOF] Trammell, B., Gugelmann, D., and N. Brownlee, "Inline Data
Integrity Signals for Passive Measurement (in Proc. TMA Integrity Signals for Passive Measurement (in Proc. TMA
2014)", April 2014. 2014)", April 2014.
[WIRE-IMAGE] [WIRE-IMAGE]
Trammell, B. and M. Kuehlewind, "The Wire Image of a Trammell, B. and M. Kuehlewind, "The Wire Image of a
Network Protocol", draft-trammell-wire-image-04 (work in Network Protocol", draft-trammell-wire-image-04 (work in
progress), April 2018. progress), April 2018.
7.3. URIs 8.3. URIs
[1] https://mailarchive.ietf.org/arch/search/?email_list=quic [1] https://mailarchive.ietf.org/arch/search/?email_list=quic
[2] https://github.com/quicwg [2] https://github.com/quicwg
[3] https://github.com/quicwg/base-drafts/labels/-spin [3] https://github.com/quicwg/base-drafts/labels/-spin
Authors' Addresses Authors' Addresses
Brian Trammell (editor) Brian Trammell (editor)
 End of changes. 18 change blocks. 
32 lines changed or deleted 37 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/