TLS Candidates for ICE
draft-martinsen-ice-tls-candidates-00

Document Type Active Internet-Draft (individual)
Last updated 2017-01-20
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ICE                                                         P. Martinsen
Internet-Draft                                                N. Buckles
Intended status: Standards Track                                   Cisco
Expires: July 24, 2017                                  January 20, 2017

                         TLS Candidates for ICE
                 draft-martinsen-ice-tls-candidates-00

Abstract

   This document introduces TLS candidates to ICE.

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 July 24, 2017.

Copyright Notice

   Copyright (c) 2017 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
   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.

Martinsen & Buckles       Expires July 24, 2017                 [Page 1]
Internet-Draft                   ICE TLS                    January 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   2
   3.  Overview of Operations  . . . . . . . . . . . . . . . . . . .   2
   4.  ICE-TLS-Candidates  . . . . . . . . . . . . . . . . . . . . .   3
   5.  Sending Packets . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  HTTP Proxy  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  RTCP Multiplexing . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Compatibility . . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   5
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   12. Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   In use-cases where media is terminated by a public reachable server
   it is desirable to be able to negotiate a TLS connection in addition
   to UDP as described in ICEbis [I-D.ietf-ice-rfc5245bis] and TCP as
   described in ICE-TCP [RFC6544].  This will increase the chances of
   successfully traversing any firewall between the client and the
   public server.

   Due to the problems associated with p2p connections and TCP
   (Synchronously opening up the two necessary pinholes at two different
   NAT/FWs), this specification focuses on the use case where one side
   is publicly reachable and runs ICE-lite.

2.  Notational Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   This specification uses terminology defined in ICEbis
   [I-D.ietf-ice-rfc5245bis].

3.  Overview of Operations

   ICE performs connectivity checks between clients and servers.  ICE
   candidates are usually exchanged via SDP and connectivity checks are
   performed on each candidate pair.  In the scenario where the client
   implements a full ICE stack and the server implements a ICE lite
   stack.  The client is in the ICE controlling role, so the client has
   ultimate control over which candidate pair is selected.

Martinsen & Buckles       Expires July 24, 2017                 [Page 2]
Internet-Draft                   ICE TLS                    January 2017

4.  ICE-TLS-Candidates

   The grammar for ICE candidates in SDP is described in ICEbis and ICE-
Show full document text