SDP Mapping into HTTP structured headers
draft-gruessing-sdp-http-00

Document Type Active Internet-Draft (individual)
Last updated 2020-02-19
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized 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)
Multiparty Multimedia Session Control                       J. Gruessing
Internet-Draft                          British Broadcasting Corporation
Intended status: Standards Track                        19 February 2020
Expires: 22 August 2020

                SDP Mapping into HTTP structured headers
                      draft-gruessing-sdp-http-00

Abstract

   This document specifies a HTTP header based representation of the
   Session Description Protocol which can be used in describing media
   being negotiated or delivered via HTTP.

Note to Readers

   _RFC Editor: please remove this section before publication_

   Source code and issues for this draft can be found at
   https://github.com/bbc/draft-gruessing-sdp-http
   (https://github.com/bbc/draft-gruessing-sdp-http).

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 https://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 22 August 2020.

Copyright Notice

   Copyright (c) 2020 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 (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.

Gruessing                Expires 22 August 2020                 [Page 1]
Internet-Draft  SDP Mapping into HTTP structured headers   February 2020

   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
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   2
   2.  The Session-Description Header  . . . . . . . . . . . . . . .   3
     2.1.  Session Description . . . . . . . . . . . . . . . . . . .   3
       2.1.1.  Time Description  . . . . . . . . . . . . . . . . . .   4
     2.2.  The Session-Media Header  . . . . . . . . . . . . . . . .   4
     2.3.  Implementation Considerations . . . . . . . . . . . . . .   4
       2.3.1.  Character set usage . . . . . . . . . . . . . . . . .   5
   3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Session Description Protocol [RFC4566] describes multimedia
   sessions for the purpose of session announcement and initiation.

   The Session-Description and Session-Media headers may be used for
   either a HTTP request or response and may be included as part of any
   HTTP method.

1.1.  Notational Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Gruessing                Expires 22 August 2020                 [Page 2]
Internet-Draft  SDP Mapping into HTTP structured headers   February 2020

2.  The Session-Description Header

   The Session-Description header field conveys the entire session
   description information, using [I-D.ietf-httpbis-header-structure] to
   describe the structure.  Its value MUST be a dictionary containing
   containing only the following keys, receivers MUST ignore all other
   values.  Dictionary keys MUST be ordered in the order presented in
   this document, but MAY be omitted where they are explicitly declared
   as OPTIONAL.

2.1.  Session Description

   v  The version, represented as an sh-integer that MUST be set 0.
   o  The originator of the session, whose value is an sh-list.  The
      order of values present in the list MUST map to the order
      specified in Section 5.2 of [RFC4566].
   s  The name of the SDP, whose values is a string and MUST NOT be
Show full document text