1.
|
Clear description of the referenced document:
|
|
Name:
|
BBF TR-143
|
Title:
|
Enabling network throughput performance tests and statistical monitoring.
|
|
2.
|
Status of approval:
|
|
TR-143 was approved in May 2008.
|
3.
|
Justification for the specific reference:
|
|
TR-143 is an essential part of the CWMP and is included as normative reference rather than including the full text.
|
4.
|
Current information, if any, about IPR issues:
|
|
None.
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
TR-143 was approved in May 2008. Specification is publicly available from BBF.
|
6.
|
The degree of stability or maturity of the document:
|
|
TR-143 was approved in May 2008.
|
7.
|
Relationship with other existing or emerging documents:
|
|
TR-143 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 2, CPE WAN Management Protocol, Broadband Forum Technical Report, 2007/
[2] RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1, http://www.ietf.org/rfc/rfc2616.txt, 1999/
[3] RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, http://www.ietf.org/rfc/rfc3986.txt, 2005/
[4] RFC 862, Echo Protocol, http://www.ietf.org/rfc/rfc862.txt, 1983/
[5] RFC 3393, IP Packet Delay Variation Metric for IP Performance Metrics (IPPM), http://www.ietf.org/rfc/rfc3393.txt, 2002/
[6] RFC 959, File Transfer Protocol, http://www.ietf.org/rfc/rfc959.txt, 1985/
[7] RFC 3449, TCP Performance Implications of Network Path Asymmetry, http://www.ietf.org/rfc/rfc3449.txt, 2002/
[8] TR-106 Amendment 1, Data Model Template for TR-069-Enabled Devices, Broadband Forum Technical Report, 2006/
[9] TR-098 Amendment 1, Internet Gateway Device Version 1.1 Data Model for TR-069, Broadband Forum Technical Report, 2006/
|
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.
|