< draft-aranda-dispatch-q4s-09.txt   draft-aranda-dispatch-q4s-10.txt >
Internet Draft Internet Draft
Intended status: Informational J.J. Garcia Aranda Intended status: Informational J.J. Garcia Aranda
Expires: November 2019 Nokia Expires: January 2020 Nokia
M. Cortes M. Cortes
J. Salvachua J. Salvachua
Univ. Politecnica de Madrid Univ. Politecnica de Madrid
M. Narganes M. Narganes
Tecnalia Tecnalia
I. Martinez Sarriegui I. Martinez Sarriegui
Optiva Optiva Media
May 13, 2019 July 5, 2019
The Quality for Service Protocol The Quality for Service Protocol
draft-aranda-dispatch-q4s-09.txt draft-aranda-dispatch-q4s-10.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on November 13, 2019. This Internet-Draft will expire on January 5, 2020.
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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
skipping to change at page 33, line 5 skipping to change at page 33, line 5
server it accessed in attempting to process the request. server it accessed in attempting to process the request.
6.5.5 505 Version Not Supported 6.5.5 505 Version Not Supported
The server does not support, or refuses to support, the Q4S The server does not support, or refuses to support, the Q4S
protocol version that was used in the request. The server is protocol version that was used in the request. The server is
indicating that it is unable or unwilling to complete the request indicating that it is unable or unwilling to complete the request
using the same major version as the client, other than with this using the same major version as the client, other than with this
error message. error message.
In the case that Q4S version is not supported, this error may be
sent by the server in handshake phase just after receiving the
first BEGIN message from client.
6.5.6 513 Message Too Large 6.5.6 513 Message Too Large
The server was unable to process the request since the message The server was unable to process the request since the message
length exceeded its capabilities. length exceeded its capabilities.
6.6 Global Failures 6xx 6.6 Global Failures 6xx
6xx responses indicate that a server has definitive information 6xx responses indicate that a server has definitive information
about a particular policy not satisfied for processing the about a particular policy not satisfied for processing the
request. request.
skipping to change at page 73, line 8 skipping to change at page 73, line 8
possible network degradation. possible network degradation.
9.6 Instability Treatments 9.6 Instability Treatments
There are two scenarios in which Q4S can be affected by network There are two scenarios in which Q4S can be affected by network
problems: loss of Q4S packets and outlier samples. problems: loss of Q4S packets and outlier samples.
9.6.1 Loss of Control Packets 9.6.1 Loss of Control Packets
Lost UDP packets (PING or BWIDTH messages) don't cause any Lost UDP packets (PING or BWIDTH messages) don't cause any
problems for the Q4S state machine, but if TCP packets are lost, problems for the Q4S state machine, but if TCP packets are
some undesirable consequences could arise. delivered too late (which we will consider as "lost"), some
undesirable consequences could arise.
Q4S does have protection mechanisms to overcome these situations. Q4S does have protection mechanisms to overcome these situations.
Examples: Examples:
o If a BEGIN packet is lost or its corresponding answer, after o If a BEGIN packet is lost or its corresponding answer, after
a certain timeout, the client SHOULD resend another BEGIN a certain timeout, the client SHOULD resend another BEGIN
packet, resetting the session packet, resetting the session
o If a READY packet is lost, after a certain timeout, the o If a READY packet is lost, after a certain timeout, the
client SHOULD resend another READY packet. client SHOULD resend another READY packet.
 End of changes. 8 change blocks. 
8 lines changed or deleted 13 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/