Comment Template SP500-291 Time Server 20Dec2012
2
SAW CONCEPTS LLC [email protected] Date: 21 Dec 2012 Comments on SP 500-291, July 2011 1 2 (3) 4 5 (6) (7) ORG 1 / # (e.g. GSA/1) Clause No./ Annex (e.g.3, 3.1, Annex A, A.1) Page No./ Figure/Tab le/Note (e.g. 27 OR Table 1) Type of com- ment 2 GE, TE, ED Comment (justification for change) by the ORG Proposed change by the ORG (e.g. Replace X text with Y text. Or Delete text X. Or Insert the following text after line 2367....) Editors Disposition ORG/1 NIST SP 500-291 Page 61: Line 9: TE Reliability: a measure of the ability of a functional unit to perform a required function under given conditions for a given time interval. [SOURCE: American National Standard Dictionary of Information Technology (ANSDIT)] A time server / time service provides accurate and reliable network time where various vendors products are calibrated to NIST's Time Server / Time Service for example in wide area computing time sharing, metrics and metering of computational node, cloud center traversals using industry standard groups protocols such as IEEE C37.118, IEC 61850, and IEEE 802.1AG for execution management, governance of execution run time where a reference time stamp marks the scheduling e.g., start, stop and time to live of a run time service or distributed algorithm 1 ORG = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = minor general Ge = major general te =minor technical Te =major technical ed = minor editorial Ed = major editorial. (Take care of Word changing te to Te etc. NOTE 1 Columns 1, 2, 4, 5 and 6 are compulsory. If column 4 is ge, use ge in column two also (and leave column 3 blank) if it applies to the whole document. NOTE 2 NBs should not change the width of columns, in order to make merging easier. Note 3 Please submit this document in .doc format and NOT .pdf
-
Upload
steven-mcgee -
Category
Documents
-
view
18 -
download
2
Transcript of Comment Template SP500-291 Time Server 20Dec2012
SAW CONCEPTS LLC [email protected]
Date: 21 Dec 2012 Comments on SP 500-291, July 2011
1 2 (3) 4 5 (6) (7)
ORG1/ #
(e.g. GSA/1)
Clause No./
Annex(e.g.3, 3.1, Annex A,
A.1)
Page No./Figure/Table/
Note(e.g. 27 OR
Table 1)
Type of
com-ment2
GE, TE,
ED
Comment (justification for change) by the ORG Proposed change by the ORG
(e.g. Replace X text with Y text. Or Delete text X. Or Insert the following text after line 2367....)
Editors Disposition
ORG/1 NIST SP 500-291
Page 61: Line 9:
TE Reliability: a measure of the ability of a functional unit to perform a required function under given conditions for a given time interval. [SOURCE: American National Standard Dictionary of Information Technology (ANSDIT)]
A time server / time service provides accurate and reliable network time where various vendors products are calibrated to NIST's Time Server / Time Service for example in wide area computing time sharing, metrics and metering of computational node, cloud center traversals using industry standard groups protocols such as IEEE C37.118, IEC 61850, and IEEE 802.1AG for execution management, governance of execution run time where a reference time stamp marks the scheduling e.g., start, stop and time to live of a run time service or distributed algorithm
ORG/2 P 36 paragraph 5.4:
Cloud Computing Standards for Portability .. ..temporal synchronization of state metadata snapshots and federated identification by organization and devices with organizations.
"temporal synchronization of state metadata snapshots and federated identification by organization and devices with organizations" where NIST's time server provides reference time stamps between state meta data snapshots samples which are then aggregated into sync delta state meta data summary messages shared within and between cloud instantiations where state meta data refresh intervals are established and made referential in time using NIST time server time stamps
ORG/3
1 ORG = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)2 Type of comment: ge = minor general Ge = major general te =minor technical Te =major technical ed = minor editorial Ed = major editorial. (Take care of Word changing te to Te etc.NOTE 1 Columns 1, 2, 4, 5 and 6 are compulsory. If column 4 is ge, use ge in column two also (and leave column 3 blank) if it applies to the whole document.NOTE 2 NBs should not change the width of columns, in order to make merging easier.Note 3 Please submit this document in .doc format and NOT .pdf
SAW CONCEPTS LLC [email protected]
Date: 21 Dec 2012 Comments on SP 500-291, July 2011
1 2 (3) 4 5 (6) (7)
ORG1/ #
(e.g. GSA/1)
Clause No./
Annex(e.g.3, 3.1, Annex A,
A.1)
Page No./Figure/Table/
Note(e.g. 27 OR
Table 1)
Type of
com-ment2
GE, TE,
ED
Comment (justification for change) by the ORG Proposed change by the ORG
(e.g. Replace X text with Y text. Or Delete text X. Or Insert the following text after line 2367....)
Editors Disposition
ORG/4
ORG/5
1 ORG = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)2 Type of comment: ge = minor general Ge = major general te =minor technical Te =major technical ed = minor editorial Ed = major editorial. (Take care of Word changing te to Te etc.NOTE 1 Columns 1, 2, 4, 5 and 6 are compulsory. If column 4 is ge, use ge in column two also (and leave column 3 blank) if it applies to the whole document.NOTE 2 NBs should not change the width of columns, in order to make merging easier.Note 3 Please submit this document in .doc format and NOT .pdf
