|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
TR-135 Amd 3 was approved in November 2012.
|
|
3.
|
Justification for the specific reference:
|
|
|
BBF TR-135 defines data models which specify objects and parameters used in messages between ACS and STB to conduct the functions defined by TR-069 which is a management protocol for communication between a CPE and Auto-Configuration Server (ACS).
J.299 (ex J.acs-stb) requires a remote management function that allows to remotely configuring STB and collecting measurement information from STB as CPE and needs to refer the existing device management protocol and its data model.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
None.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
TR-135 was approved in December 2007. Specification is publicly available from BBF at http://www.broadband-forum.org/technical/trlist.php
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
TR-135 was approved in December 2007. Issue: 1 Amendment 3 was approved in November 2012
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
TR-135 is part of a set of specifications related to remote management of CPE.
The set consists of TR-069, TR-104, TR-106, TR-135, TR-140, TR-143, TR-157, TR-181 Issue 2, and TR-196.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] TR-069 Amendment 4, CPE WAN Management Protocol, Broadband Forum Technical/
Report /
Data Model for a TR-069 Enabled STB TR-135 Issue 1 Amendment 3/
November 2012 © The Broadband Forum. All rights reserved 13 of 69/
[2] TR-106 Amendment 6, Home Network Data Model Template for TR-069-Enabled Devices,/
Broadband Forum Technical Report/
[3] TR-126, Triple-Play Services Quality of Experience (QoE) Requirements, Broadband/
Forum Technical Report/
[4] TR-140 Issue 1 Amendment 1, TR-069 Data Model for Storage Service Devices,/
Broadband Forum Technical Report/
[5] RFC 1350, The TFTP Protocol (Revision 2), http://www.ietf.org/rfc/rfc1350.txt/
[6] RFC 2119, Key words for use in RFCs to Indicate Requirement Levels,/
http://www.ietf.org/rfc/rfc2119.txt/
[7] RFC 2228, FTP Security Extensions, http://www.ietf.org/rfc/rfc2228.txt/
[8] RFC 2326, Real Time Streaming Protocol (RTSP), http://www.ietf.org/rfc/rfc2326.txt/
[9] RFC 2960, Stream Control Transmission Protocol (SCTP),/
http://www.ietf.org/rfc/rfc2960.txt/
[10] RFC 3066, Tags for the Identification of Languages, http://www.ietf.org/rfc/rfc3066.txt/
[11] RFC 3376, Internet Group Management Protocol (IGMP), Version 3,/
http://www.ietf.org/rfc/rfc3376.txt/
[12] RFC 3986, Uniform Resource Identifier (URI): Generic Syntax,/
http://www.ietf.org/rfc/rfc3986.txt/
[13] RFC 3550, RTP: A Transport Protocol for Real-Time Applications,/
http://www.ietf.org/rfc/rfc3550.txt/
[14] RFC 4340, Datagram Congestion Control Protocol (DCCP),/
http://www.ietf.org/rfc/rfc4340.txt/
[15] RFC 4585, Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based/
Feedback (RTP/AVPF), http://www.ietf.org/rfc/rfc4585.txt/
[16] RFC 4588, RTP Retransmission Packet Format, http://www.ietf.org/rfc/rfc4588.txt/
[17] ETSI EN 300 744, Digital Video Broadcasting (DVB): Framing structure, channel coding/
and modulation for digital terrestrial television/
[18] ETSI TS 102 034, Digital Video Broadcasting (DVB); Transport of MPEG-2 Based DVB/
Services/
[19] ISO/IEC 11172-1 (1993), Information Technology - Coding of moving pictures and/
associated audio for digital storage media at up to about 1,5 Mbit/s - Part 1: System/
[20] ISO/IEC 11172-2 (1993), Information Technology - Coding of moving pictures and/
associated audio for digital storage media at up to about 1,5 Mbit/s - Part 2: Video/
[21] ISO/IEC 11172-3 (1993), Information Technology - Coding of moving pictures and/
associated audio for digital storage media at up to about 1,5 Mbit/s - Part 3: Audio/
[22] ISO/IEC 13818-1 (2nd edition, 2000), Information technology - Generic coding of moving/
picture and associated audio information: Systems /
Data Model for a TR-069 Enabled STB TR-135 Issue 1 Amendment 3/
November 2012 © The Broadband Forum. All rights reserved 14 of 69/
[23] ITU-T Rec. H.262 | ISO/IEC 13818-2 (2nd edition, 2000), Information Technology -/
Generic Coding of moving pictures and associated audio information: Video/
[24] ISO/IEC 13818-3 (2nd edition, 1998), Information technology - Generic coding of moving/
picture and associated audio information: Audio/
[25] ISO/IEC 13818-6 (2nd edition, 1998), Information technology - Generic coding of moving/
picture and associated audio information: Extensions for DSM-CC/
[26] ISO/IEC 14496-2:2001, Information technology – Generic coding of audio-visual objects –/
Part 2: Visual/
[27] ISO/IEC 14496-3:2001, Information technology – Coding of Audio-Visual objects – Part/
3: Audio/
[28] ISO/IEC 23003-1:2007, Information technology – MPEG audio technologies – Part 1:/
MPEG Surround/
[29] ITU-T Rec. H.264 | ISO/IEC 14496-10:2004/AM 1, Part 10, Advanced Video Coding/
AMENDMENT 1: AVC fidelity range extensions/
[30] ITU-T Rec X.700, Management Framework for Open Systems Interconnection (OSI) FOR/
CCITT Applications/
[31] ISMA white paper, Planning the Future of IPTV with ISMA/
[32] DGTVi D-Book v1.0, Sep 2004, Compatible receivers for the Italian market/
[33] CENELEC technical standard EN 50049-1:1997/
[34] SMPTE 20022-1 Application Layer Forward Error Correction/
[35] ATIS IIF (IPTV Interoperability Forum), Quality of Service Metrics for Linear Broadcast/
IPTV, document number: ATIS-0800008, August 2007/
[36] ATSC, Digital Audio Compression (AC-3) (E-AC-3) Standard, Rev. B, document number/
A/52B, June 2005/
[37] SMPTE, Television – VC-1 Compressed Video Bitstream Format and Decoding Process,/
document number 421M, 2006/
[38] SSH File Transfer Protocol, http://tools.ietf.org/wg/secsh/draft-ietf-secsh-filexfer/
[39] ITU-T Rec. H.770 "Mechanisms for service discovery and selection for IPTV"
|
|
9.
|
Qualification of
Broadband Forum:
|
|
|
The Broadband Forum was qualified in accordance with ITU-T A.4 and ITU-T A.5 on 27 January 2010.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None.
|
|
