Measurement of Round Trip Time and Fractional Loss Using STUN
draft-ietf-tram-stun-path-data-04

The information below is for an old version of the document
Document Type Active Internet-Draft (tram WG)
Last updated 2016-08-19 (latest revision 2016-06-20)
Replaces draft-ietf-tram-measurement-rtt-loss
Replaced by draft-ietf-tram-measurement-rtt-loss
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Simon Perreault
Shepherd write-up Show (last changed 2016-01-08)
IESG IESG state IESG Evaluation::External Party
Consensus Boilerplate Yes
Telechat date
Needs 4 more YES or NO OBJECTION positions to pass.
Responsible AD Spencer Dawkins
Send notices to "Simon Perreault" <sperreault@jive.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state None
TRAM                                                        P. Martinsen
Internet-Draft                                                  T. Reddy
Intended status: Standards Track                                 D. Wing
Expires: December 22, 2016                                         Cisco
                                                                V. Singh
                                                            callstats.io
                                                           June 20, 2016

     Measurement of Round Trip Time and Fractional Loss Using STUN
                   draft-ietf-tram-stun-path-data-04

Abstract

   A host with multiple interfaces needs to choose the best interface
   for communication.  Oftentimes, this decision is based on a static
   configuration and does not consider the path characteristics, which
   may affect the user experience.

   This document describes a mechanism for an endpoint to measure the
   path characteristics fractional loss and RTT using Session Traversal
   Utilities for NAT (STUN) messages.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 22, 2016.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of

Martinsen, et al.       Expires December 22, 2016               [Page 1]
Internet-Draft           RTT and Fractional Loss               June 2016

   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   3
   3.  Measuring RTT and Fractional Loss . . . . . . . . . . . . . .   3
     3.1.  TRANSACTION_TRANSMIT_COUNTER attribute  . . . . . . . . .   4
     3.2.  Usage in Requests . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Usage in Responses  . . . . . . . . . . . . . . . . . . .   5
     3.4.  Example Operation . . . . . . . . . . . . . . . . . . . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   This document extends STUN [RFC5389] to make it possible to correlate
   STUN responses to specific request when re-transmits occur.  This
   assists the client in determining path characteristics like round-
   trip time (RTT) and fractional packet loss.

   The TRANSACTION_TRANSMIT_COUNTER attribute introduced in section
   Section 3.1 can be used in ICE [RFC5245] connectivity checks (STUN
   Binding request and response).  It can also be used with TURN
   [RFC5766] by adding this attribute to Allocate requests and responses
   to measure loss and RTT between the client and respective TURN
   server.

   ICE is a mechanism commonly used in VoIP applications to traverse
   NATs, and it uses a static prioritization formula to order the
   candidate pairs and perform connectivity checks, in which the most
   preferred address pairs are tested first and when a sufficiently good
   pair is discovered, that pair is used for communications and further
   connectivity tests are stopped.

   When multiple paths are available for communication, the endpoint
   sends ICE connectivity checks across each path (candidate pair).
   Choosing the path with the lowest round trip time is a reasonable
Show full document text