draft-ietf-avtcore-rfc5285-bis-10.txt   draft-ietf-avtcore-rfc5285-bis-11.txt 
AVTCore D. Singer AVTCore D. Singer
Internet-Draft Apple, Inc. Internet-Draft Apple, Inc.
Obsoletes: 5285 (if approved) H. Desineni Obsoletes: 5285 (if approved) H. Desineni
Intended status: Standards Track Qualcomm Intended status: Standards Track Qualcomm
Expires: November 1, 2017 R. Even, Ed. Expires: November 3, 2017 R. Even, Ed.
Huawei Technologies Huawei Technologies
April 30, 2017 May 2, 2017
A General Mechanism for RTP Header Extensions A General Mechanism for RTP Header Extensions
draft-ietf-avtcore-rfc5285-bis-10.txt draft-ietf-avtcore-rfc5285-bis-11.txt
Abstract Abstract
This document provides a general mechanism to use the header This document provides a general mechanism to use the header
extension feature of RTP (the Real-Time Transport Protocol). It extension feature of RTP (the Real-Time Transport Protocol). It
provides the option to use a small number of small extensions in each provides the option to use a small number of small extensions in each
RTP packet, where the universe of possible extensions is large and RTP packet, where the universe of possible extensions is large and
registration is de-centralized. The actual extensions in use in a registration is de-centralized. The actual extensions in use in a
session are signaled in the setup information for that session. This session are signaled in the setup information for that session. This
document obsoletes RFC5285. document obsoletes RFC5285.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 November 1, 2017. This Internet-Draft will expire on November 3, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 2, line 32 skipping to change at page 2, line 32
6. SDP Signaling for support of mixed one byte and two bytes 6. SDP Signaling for support of mixed one byte and two bytes
header extensions. . . . . . . . . . . . . . . . . . . . . . 12 header extensions. . . . . . . . . . . . . . . . . . . . . . 12
7. SDP Offer/Answer . . . . . . . . . . . . . . . . . . . . . . 13 7. SDP Offer/Answer . . . . . . . . . . . . . . . . . . . . . . 13
8. BNF Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. BNF Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 15
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16 9. Security Considerations . . . . . . . . . . . . . . . . . . . 16
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
10.1. Identifier Space for IANA to Manage . . . . . . . . . . 17 10.1. Identifier Space for IANA to Manage . . . . . . . . . . 17
10.2. Registration of the SDP extmap Attribute . . . . . . . . 18 10.2. Registration of the SDP extmap Attribute . . . . . . . . 18
10.3. Registration of the SDP extmap-allow-mixed Attribute . . 19 10.3. Registration of the SDP extmap-allow-mixed Attribute . . 19
11. Changes from RFC5285 . . . . . . . . . . . . . . . . . . . . 19 11. Changes from RFC5285 . . . . . . . . . . . . . . . . . . . . 19
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
13.1. Normative References . . . . . . . . . . . . . . . . . . 20 13.1. Normative References . . . . . . . . . . . . . . . . . . 20
13.2. Informative References . . . . . . . . . . . . . . . . . 21 13.2. Informative References . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
The RTP specification [RFC3550] provides a capability to extend the The RTP specification [RFC3550] provides a capability to extend the
RTP header. It defines the header extension format and rules for its RTP header. It defines the header extension format and rules for its
use in Section 5.3.1. The existing header extension method permits use in Section 5.3.1. The existing header extension method permits
skipping to change at page 18, line 40 skipping to change at page 18, line 40
unique. unique.
o Size and format of entries: a mapping from a naming URI string to o Size and format of entries: a mapping from a naming URI string to
a formal reference to a publicly available specification, with a a formal reference to a publicly available specification, with a
descriptive phrase and contact information. descriptive phrase and contact information.
o Initial assignments: none. o Initial assignments: none.
10.2. Registration of the SDP extmap Attribute 10.2. Registration of the SDP extmap Attribute
IANA is requested to register the extmap SDP [RFC4566] attribute. IANA is requested to update the registeration of the extmap SDP
[RFC4566] attribute.
SDP Attribute ("att-field"): o Contact Name and email address: IETF, contacted via
Attribute name: extmap mmusic@ietf.org, or a successor address designated by IESG
Long form: generic header extension map definition Attribute Name: extmap
Type of name: att-field
Type of attribute: Media or session level o Attribute Syntax: See section 8 of [RFCXXXX].
Subject to charset: No
Purpose: defines the mapping from the extension o Attribute Semantics: The details of appropriate values are given
numbers used in packet headers in [RFC XXXX].
into extension names.
Reference: [RFCXXXX] o Usage Level: Media or session level.
Values: See [RFCXXXX]
o Charset Dependent: No.
o Purpose: defines the mapping from the extension numbers used in
packet headers into extension names.
o O/A Procedures: See section 7 of [RFCXXXX].
o Mux Category: Special.
o Reference: [RFCXXXX]
10.3. Registration of the SDP extmap-allow-mixed Attribute 10.3. Registration of the SDP extmap-allow-mixed Attribute
The IANA is requested to register one new SDP attribute: The IANA is requested to register one new SDP attribute:
SDP Attribute ("att-field"): o Contact Name and email address: IETF, contacted via
Attribute name: extmap-allow-mixed mmusic@ietf.org, or a successor address designated by IESG.
Long form: One and Two bytes mixed mode
Type of name: att-field o Attribute Name: extmap-allow-mixed.
Type of attribute: Media or session level
Subject to charset: No o Attribute Syntax: See section 6 of [RFCXXXX].
Purpose: Negotiate the use of One and Two bytes
in the same RTP stream. o Attribute Semantics: See section 6 of [RFCXXXX].
Reference: [RFCXXXX]
Values: None o Attribute Value: None.
o Usage Level: Media or session level.
o Charset Dependent: no.
o Purpose: Negotiate the use of One and Two bytes in the same RTP
stream.
o O/A Procedures: See section 6 of [RFCXXXX].
o Mux Category: Normal
o Reference: [RFCXXXX]
11. Changes from RFC5285 11. Changes from RFC5285
The major motivation for updating [RFC5285] was to allow having one The major motivation for updating [RFC5285] was to allow having one
byte and two bytes RTP header extensions in the same RTP stream (but byte and two bytes RTP header extensions in the same RTP stream (but
not in the same RTP packet). The support for this case is negotiated not in the same RTP packet). The support for this case is negotiated
using a new SDP attribute "extmap-allow-mixed" specified in this using a new SDP attribute "extmap-allow-mixed" specified in this
document. document.
The other major change is to update the requirement from the RTP The other major change is to update the requirement from the RTP
 End of changes. 8 change blocks. 
27 lines changed or deleted 51 lines changed or added

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