Re: [STDS-802-16] Configuration File TLVs
Eyal,
On the second item ,you are right. The word is useless.
On the first item , there are vestiges of the past. People from 802.16 decided that configuring Service Flows by means of Configuration File is not good.
This is what I know...
-----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 10: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
IMPORTANT NOTICE: This message is intended only for the use of the individual or entity to which it is addressed. The message may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify Redline immediately by email at postmaster@redlinecommunications.com.
Thank you.