draft-ietf-avt-rtp-rfc3984bis-11.txt   draft-ietf-avt-rtp-rfc3984bis-12.txt 
Obsoletes RFC 3984 Obsoletes RFC 3984
Audio/Video Transport WG Y.-K. Wang Audio/Video Transport WG Y.-K. Wang
Internet Draft Huawei Technologies Internet Draft Huawei Technologies
Intended status: Standards track R. Even Intended status: Standards track R. Even
Expires: December 2010 Self-employed Expires: April 2011 Self-employed
T. Kristensen T. Kristensen
Tandberg Tandberg
R. Jesup R. Jesup
WorldGate Communications WorldGate Communications
June 25, 2010 October 9, 2010
RTP Payload Format for H.264 Video RTP Payload Format for H.264 Video
draft-ietf-avt-rtp-rfc3984bis-11.txt draft-ietf-avt-rtp-rfc3984bis-12.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 38 skipping to change at page 1, line 38
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 December 25, 2010. This Internet-Draft will expire on April 9, 2009.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 3, line 28 skipping to change at page 3, line 28
6.3. Non-Interleaved Mode....................................34 6.3. Non-Interleaved Mode....................................34
6.4. Interleaved Mode........................................35 6.4. Interleaved Mode........................................35
7. De-Packetization Process.....................................35 7. De-Packetization Process.....................................35
7.1. Single NAL Unit and Non-Interleaved Mode................35 7.1. Single NAL Unit and Non-Interleaved Mode................35
7.2. Interleaved Mode........................................36 7.2. Interleaved Mode........................................36
7.2.1. Size of the De-interleaving Buffer.................36 7.2.1. Size of the De-interleaving Buffer.................36
7.2.2. De-interleaving Process............................37 7.2.2. De-interleaving Process............................37
7.3. Additional De-Packetization Guidelines..................38 7.3. Additional De-Packetization Guidelines..................38
8. Payload Format Parameters....................................39 8. Payload Format Parameters....................................39
8.1. Media Type Registration.................................39 8.1. Media Type Registration.................................39
8.2. SDP Parameters..........................................57 8.2. SDP Parameters..........................................58
8.2.1. Mapping of Payload Type Parameters to SDP..........57 8.2.1. Mapping of Payload Type Parameters to SDP..........58
8.2.2. Usage with the SDP Offer/Answer Model..............59 8.2.2. Usage with the SDP Offer/Answer Model..............59
8.2.3. Usage in Declarative Session Descriptions..........68 8.2.3. Usage in Declarative Session Descriptions..........69
8.3. Examples................................................70 8.3. Examples................................................70
Offer SDP:......................................................75 Offer SDP:......................................................76
Answer SDP:.....................................................76 Answer SDP:.....................................................76
8.4. Parameter Set Considerations............................77 8.4. Parameter Set Considerations............................77
8.5. Decoder Refresh Point Procedure using In-Band Transport of 8.5. Decoder Refresh Point Procedure using In-Band Transport of
Parameter Sets (Informative).................................80 Parameter Sets (Informative).................................80
8.5.1. IDR Procedure to Respond to a Request for a Decoder 8.5.1. IDR Procedure to Respond to a Request for a Decoder
Refresh Point.............................................80 Refresh Point.............................................80
8.5.2. Gradual Recovery Procedure to Respond to a Request for 8.5.2. Gradual Recovery Procedure to Respond to a Request for
a Decoder Refresh Point...................................81 a Decoder Refresh Point...................................81
9. Security Considerations......................................81 9. Security Considerations......................................82
10. Congestion Control..........................................82 10. Congestion Control..........................................82
11. IANA Consideration..........................................83 11. IANA Consideration..........................................83
12. Informative Appendix: Application Examples..................83 12. Informative Appendix: Application Examples..................83
12.1. Video Telephony according to ITU-T Recommendation H.241 12.1. Video Telephony according to ITU-T Recommendation H.241
Annex A......................................................83 Annex A......................................................84
12.2. Video Telephony, No Slice Data Partitioning, No NAL Unit 12.2. Video Telephony, No Slice Data Partitioning, No NAL Unit
Aggregation..................................................84 Aggregation..................................................84
12.3. Video Telephony, Interleaved Packetization Using NAL Unit 12.3. Video Telephony, Interleaved Packetization Using NAL Unit
Aggregation..................................................84 Aggregation..................................................84
12.4. Video Telephony with Data Partitioning.................85 12.4. Video Telephony with Data Partitioning.................85
12.5. Video Telephony or Streaming with FUs and Forward Error 12.5. Video Telephony or Streaming with FUs and Forward Error
Correction...................................................85 Correction...................................................86
12.6. Low Bit-Rate Streaming.................................88 12.6. Low Bit-Rate Streaming.................................88
12.7. Robust Packet Scheduling in Video Streaming............89 12.7. Robust Packet Scheduling in Video Streaming............89
13. Informative Appendix: Rationale for Decoding Order Number...90 13. Informative Appendix: Rationale for Decoding Order Number...90
13.1. Introduction...........................................90 13.1. Introduction...........................................90
13.2. Example of Multi-Picture Slice Interleaving............90 13.2. Example of Multi-Picture Slice Interleaving............90
13.3. Example of Robust Packet Scheduling....................92 13.3. Example of Robust Packet Scheduling....................92
13.4. Robust Transmission Scheduling of Redundant Coded Slices96 13.4. Robust Transmission Scheduling of Redundant Coded Slices96
13.5. Remarks on Other Design Possibilities..................96 13.5. Remarks on Other Design Possibilities..................96
14. Backward Compatibility to RFC 3984..........................97 14. Backward Compatibility to RFC 3984..........................97
15. Changes from RFC 3984.......................................99 15. Changes from RFC 3984.......................................99
skipping to change at page 44, line 22 skipping to change at page 44, line 22
with the specified profile and level. with the specified profile and level.
max-mbps: The value of max-mbps is an integer indicating the max-mbps: The value of max-mbps is an integer indicating the
maximum macroblock processing rate in units of macroblocks maximum macroblock processing rate in units of macroblocks
per second. The max-mbps parameter signals that the receiver per second. The max-mbps parameter signals that the receiver
is capable of decoding video at a higher rate than is is capable of decoding video at a higher rate than is
required by the signaled highest level conveyed in the value required by the signaled highest level conveyed in the value
of the profile-level-id parameter or the max-recv-level of the profile-level-id parameter or the max-recv-level
parameter. When max-mbps is signaled, the receiver MUST be parameter. When max-mbps is signaled, the receiver MUST be
able to decode NAL unit streams that conform to the signaled able to decode NAL unit streams that conform to the signaled
highestlevel, with the exception that the MaxMBPS value in highest level, with the exception that the MaxMBPS value in
Table A-1 of [1] for the signaled highest level is replaced Table A-1 of [1] for the signaled highest level is replaced
with the value of max-mbps. The value of max-mbps MUST be with the value of max-mbps. The value of max-mbps MUST be
greater than or equal to the value of MaxMBPS given in Table greater than or equal to the value of MaxMBPS given in Table
A-1 of [1] for the highest level. Senders MAY use this A-1 of [1] for the highest level. Senders MAY use this
knowledge to send pictures of a given size at a higher knowledge to send pictures of a given size at a higher
picture rate than is indicated in the signaled highest level. picture rate than is indicated in the signaled highest level.
max-smbps: The value of max-smbps is an integer indicating the max-smbps: The value of max-smbps is an integer indicating the
maximum static macroblock processing rate in units of static maximum static macroblock processing rate in units of static
macroblocks per second, under the hypothetical assumption macroblocks per second, under the hypothetical assumption
that all macroblocks are static macroblocks. When max-smbps that all macroblocks are static macroblocks. When max-smbps
is signalled the MaxMBPS value in Table A-1 of [1] should be is signaled the MaxMBPS value in Table A-1 of [1] should be
replaced with the result of the following computation: replaced with the result of the following computation:
o If the parameter max-mbps is signalled, set a variable o If the parameter max-mbps is signaled, set a variable
MaxMacroblocksPerSecond to the value of max-mbps. MaxMacroblocksPerSecond to the value of max-mbps.
Otherwise, set MaxMacroblocksPerSecond equal to the value Otherwise, set MaxMacroblocksPerSecond equal to the value
of MaxMBPS in Table A-1 [1] for the highest level. of MaxMBPS in Table A-1 [1] for the signaled highest level
conveyed in the value of the profile-level-id parameter or
the max-recv-level parameter.
o Set a variable P_non-static to the proportion of non- o Set a variable P_non-static to the proportion of non-
static macroblocks in picture n. static macroblocks in picture n.
o Set a variable P_static to the proportion of static o Set a variable P_static to the proportion of static
macroblocks in picture n. macroblocks in picture n.
o The value of MaxMBPS in Table A-1 of [1] should be o The value of MaxMBPS in Table A-1 of [1] should be
considered by the encoder to be equal to: considered by the encoder to be equal to:
MaxMacroblocksPerSecond * max-smbps / (P_non-static * MaxMacroblocksPerSecond * max-smbps / (P_non-static *
max-smbps + P_static * MaxMacroblocksPerSecond) max-smbps + P_static * MaxMacroblocksPerSecond)
The encoder should recompute this value for each picture. The The encoder should recompute this value for each picture. The
value of max-smbps MUST be greater than the value of MaxMBPS value of max-smbps MUST be greater than or equal to the value
given in Table A-1 of [1] for the highest level. Senders MAY of MaxMBPS given explicitly as the value of the max-mbps
use this knowledge to send pictures of a given size at a parameter or implicitly in Table A-1 of [1] for the signaled
higher picture rate than is indicated in the signaled highest highest level. Senders MAY use this knowledge to send
level. pictures of a given size at a higher picture rate than is
indicated in the signaled highest level.
max-fs: The value of max-fs is an integer indicating the maximum max-fs: The value of max-fs is an integer indicating the maximum
frame size in units of macroblocks. The max-fs parameter frame size in units of macroblocks. The max-fs parameter
signals that the receiver is capable of decoding larger signals that the receiver is capable of decoding larger
picture sizes than are required by the signaled highest level picture sizes than are required by the signaled highest level
conveyed in the value of the profile-level-id parameter or conveyed in the value of the profile-level-id parameter or
the max-recv-level parameter. When max-fs is signaled, the the max-recv-level parameter. When max-fs is signaled, the
receiver MUST be able to decode NAL unit streams that conform receiver MUST be able to decode NAL unit streams that conform
to the signaled highest level, with the exception that the to the signaled highest level, with the exception that the
MaxFS value in Table A-1 of [1] for the signaled highest MaxFS value in Table A-1 of [1] for the signaled highest
skipping to change at page 56, line 38 skipping to change at page 56, line 46
therein is 14. therein is 14.
When sar-understood is not present, the value MUST be When sar-understood is not present, the value MUST be
inferred to be equal to 13. inferred to be equal to 13.
sar-supported: sar-supported:
This parameter MAY be used to indicate a receiver capability This parameter MAY be used to indicate a receiver capability
and not anything else. The value of this parameter is an and not anything else. The value of this parameter is an
integer in the range of 1 to sar-understood, inclusive, equal integer in the range of 1 to sar-understood, inclusive, equal
to 255. The value of sar-supported equal to N smaller than to 255. The value of sar-supported equal to N smaller than
255 indicates that the reciever supports all the SARs 255 indicates that the receiver supports all the SARs
corresponding to H.264 aspect_ratio_idc values (see Table E-1 corresponding to H.264 aspect_ratio_idc values (see Table E-1
of [1]) in the range from 1 to N, inclusive, without of [1]) in the range from 1 to N, inclusive, without
geometric distortion. The value of sar-supported equal to geometric distortion. The value of sar-supported equal to
255 indicates that the receiver supports all sample aspect 255 indicates that the receiver supports all sample aspect
ratios which are expressible using two 16-bit integer values ratios which are expressible using two 16-bit integer values
as the numerator and denominator, i.e., those that are as the numerator and denominator, i.e., those that are
expressible using the H.264 aspect_ratio_idc value of 255 expressible using the H.264 aspect_ratio_idc value of 255
(Extended_SAR, see Table E-1 of [1]), without geometric (Extended_SAR, see Table E-1 of [1]), without geometric
distortion. distortion.
 End of changes. 16 change blocks. 
21 lines changed or deleted 24 lines changed or added

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