There is confusion in regards to the appropriate response to a FileDirectory request that is issued with a ContinueAfter value of a file that no longer exists. Due to lack of a timing specification, and some ambiguity in ISO 9506-1, 61850-8-1 needs to specify a testable behavior that is consistent with current implementation strategies.
ISO 9506-1 specifies that if a FileName was returned in a FileDirectory-Response+, at any time, any name can be used as a valid ContinueAfter even if the file does not exist. This creates an implementation issue in regards to how long to "remember" the list of names (could be forever for any FileDirectory request as long as the MMS-Context is active). This creates resource and implementation issues for no good reason.
Therefore, a FileDirectory-Response- needs to be specified if the ContinueAfter value contains a value where the specified file no longer exists.
Proposal
Add the following text:
A FileDirectory-Request that specifies a ContinueAfter Filename, that does not exist, the MMPM shall
return a a MMS Confirmed-Error PDU. The ServiceError, within the Confirmed-ErrorPDU
shall be errorClass=”file” with an errorCode=”file-non-existent”.
Discussion
Created
Status
06 Feb 15
In Force (green)
18 Dec 14
Ballot Period
There is agreement with Joel's proposal within the UCA Testing Committee. The conclusion is:
"A FileDirectory-Request that specifies a ContinueAfter Filename, that does not exist, the MMPM may return a a MMS Confirmed-Error PDU. The ServiceError, within the Confirmed-ErrorPDU shall be errorClass=”file” with an errorCode=”file-non-existent”."
02 Sep 14
Discussion (red)
Per discussion in Test Committee meeting 19/08/2014 and discussion with Thierry, Herb, and myself 26/08/2014:
"the MMPM shall return a a MMS Confirmed-Error PDU" is changed to: