Appendix A: TFTP Configuration File Extensions

All of a CMs Baseline Privacy configuration parameter values are specified
in the configuration file TFTP-downloaded by the CM during RF MAC
initialization. Baseline Privacy configuration setting fields are included
in both the CM MIC and CMTS MIC calculations, and in a CMs registration
requests. Refer to [MCNS1] for the order in which Baseline Privacy
configuration setting fields are included in the CMTS MICs MD5 digest.

A.1 Encodings

The following type/length/value encodings for Baseline Privacy
configuration settings MUST be used in both the configuration file and in
RF MAC CM registration requests. All multi-octet quantities are in
network-byte order, i.e., the octet containing the most-significant bits is
the first transmitted on the wire.

A.1.1 Baseline Privacy Configuration Setting

The presence of this configuration setting serves as an indication that the
CM is configured to run Baseline Privacy. Therefore, the configuration
setting MUST be present if the CM is provisioned to run Baseline Privacy,
and MUST NOT be present if the CM is provisioned not to run baseline
privacy.

This field defines the parameters associated with Baseline Privacy
operation. It is composed of a number of encapsulated type/length/value
fields. The type fields defined are only valid within the encapsulated
Baseline Privacy configuration setting string.

type	length	value
BP_CFG	n

[MCNS1] defines the specific value of BP_CFG.

A.1.1.1 Internal Baseline Privacy Encodings

A.1.1.1.1 Authorize Wait Timeout

The value of the field specifies retransmission interval, in seconds, of
Authorization Request messages from the Authorize Wait state.

sub-type	length	value
1		4
Valid Range: 1 - 30

A.1.1.1.2 Reauthorize Wait Timeout

The value of the field specifies retransmission interval, in seconds, of
Authorization Request messages from the Authorize Wait state.

sub-type	length	value
2		4

Valid Range: 1 - 20

A.1.1.1.3 Authorization Grace Time

The value of this field specifies the grace period for re-authorization, in
seconds.

sub-type	length	value
3		4

Valid Range: 1 - 1800

A.1.1.1.4 Operational Wait Timeout

The value of this field specifies the retransmission interval, in seconds,
of Key Requests from the Operational Wait state.

sub-type	length	value
4		4
Valid Range: 1 - 10

A.1.1.1.5 Rekey Wait Timeout

The value of this field specifies the retransmission interval, in seconds,
of Key Requests from the Rekey Wait state.

sub-type	length	value
5		4
Valid Range: 1 - 10

A.1.1.1.6 TEK Grace Time

The value of this field specifies the grace period for re-keying, in
seconds.

sub-type	length	value
6		4

Valid Range: 1 - 1800

A.1.1.1.7 Authorize Reject Wait Timeout

The value of this field specifies how long a CM waits in the Authorize
Reject Wait state after receiving an Authorization Reject.

sub-type	length	value
7		4

A.1.2 Class-of-Service Privacy Enable

This configuration setting is one of the type/length/value fields
encapsulated within the Class of Service Configuration Setting (type 4),
defined in [MCNS1]. Its value indicates whether Baseline Privacy is enabled
for a particular provisioned class of service. If the value field is 1,
Baseline Privacy will run on the SID that gets associated with the class of
service; if the value field is 0, Baseline Privacy will not run on the
associated SID. Note that SIDs are assigned to a provisioned class of
service during CMTS registration.

sub-type	length	on/off
CoS_BP_ENABLE	1	1 or 0

[MCNS1] defines the specific value of CoS_BP_ENABLE.

A.2 Parameter Guidelines

Below are recommended ranges and values for Baseline Privacys various
configuration and operational parameters. These ranges and default values
may change as service providers gain operational experience running
Baseline Privacy.

Table A-1. Recommended Operational Ranges for BPI Configuration Parameters

The valid range (vs. recommended operational range) for Authorization and
TEK lifetimes are:
* Authorization Lifetime Valid Range: 1 - 6,048,000 seconds
* TEK Lifetime Valid Range: 1 - 604,800 seconds

Note that valid ranges defined for each of BPIs configuration parameters
extend below the recommended operational ranges. For the purposes of
protocol testing, it is useful to run the BPI protocol with timer values
well below the low end of the recommended operational ranges. The shorter
timer values speed up BPIs clock, causing BPI protocol state machine
events to occur far more rapidly than they would under an operational
configuration. While BPI implementations need not be designed to operate
efficiently at this accelerated BPI pace, the protocol implementation
SHOULD operate correctly under these shorter timer values.  Table A-2
provides a list of shortened parameter values which are likely to be
employed in protocol conformance and certification testing.

The TEK Grace Time MUST be less than half the TEK Lifetime; this insures
there are at most two active (not expired) TEKs per SID at any time.
