Re: [STDS-802-16] Configuration File TLVs
Eyal,
Since DSA messages needed to be supported in any case, we intentionally left
service flows out of the configuration file rather than have two methods for
setting up connections. The wording "configuration" comes from the past
when setting up the initial provisioned services via DSA was considered part
of "configuring" the SS.
Ken
-----Original Message-----
From: owner-stds-802-16@LISTSERV.IEEE.ORG
[mailto:owner-stds-802-16@LISTSERV.IEEE.ORG] On Behalf Of Eyal Verbin
Sent: Tuesday, June 15, 2004 7:05 AM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: [STDS-802-16] Configuration File TLVs
Request for clarification:
1. Does a configuration file may include service flow parameters (TLV
types 145/146) as standard configuration settings? Currently section
9.2.2 of D5 lists only 5 standard configuration settings that may be
included, however section 11.13.19.3 reads "Packet CS encodings for
configuration and MAC messaging" - what is the meaning of
"configuration" in this header. In other words, is the SS required to
decode standard settings besides those specified in section 9.2.2
2. The configuration file includes TFTP server timestamp (section
9.2.1). In Docsis, IP connectivity precedes registration and REG-REQ
sent by the SS includes this timestamp in order to prevent replay
attacks. However, in our case registration precedes IP connectivity, so
it seems that this parameter is useless
Eyal