[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: [kmip-comment] Comments on KMIP public review drafts
For reference - these are the three comment spreadsheets that are not across the profiles. Tim.
,,,,,,,,,,,,,,,,,,,,,,,,,,,
OASIS Technical Committees Issue Tracker ,,,,,,,,,,,,,,,,,,,,,,,,,,,
Displaying 59 issues at 21/Mar/14 9:18 AM.,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project,Key,Summary,Issue Type,Status,Priority,Resolution,Assignee,Reporter,Created,Last Viewed,Updated,Resolved,Affects Version/s,Fix Version/s,Component/s,Due Date,Watchers,Images,Work Ratio,Sub-Tasks,Linked Issues,Environment,Description,Security Level,Labels,Proposal,Resolution
Technical Advisory Board,TAB-967 ,Hanging Paragraphs (19),Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,20/Mar/14 10:47 AM,21/Mar/14 9:18 AM,20/Mar/14 10:47 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,Style,"Sections 1 and 1.1 illustrate the issue with hanging paragraphs. If I say see Section 1, do I mean the two paragraphs following section 1 or do I mean that + 1.1 - 1.3? Hanging paragraphs in this draft: 1, 1.1 2, 2.1 2.1, 2.1.1 2.1.7, 2.1.7.1 2.2, 2.2.1 3, 3.1 3.18, 3.18.1 3.18.2, 3.18.2.1 4, 4.1 5, 5.1 6, 6.1 7, 7.1 9, 9.1 9.1, 9.1.1 9.1.1, 9.1.1.1 9.1.3, 9.1.3.1 9.1.3.2, 9.1.3.2.1 9.1.3.3, 9.1.3.3.1 11, 11.1",,,Re-section the draft to remove hanging paragraphs,
Technical Advisory Board,TAB-889 ,Subsections as lists?,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:41 AM,19/Mar/14 5:14 PM,18/Mar/14 10:41 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,Style,"9.1.1 TTLV Encoding Fields reads in part: Every Data object encoded by the TTLV scheme consists of four items, in order: In addition to being a hanging paragraph, it is followed by four subsections of 9.1.1.1 Item Tag, 9.1.1.2 Item Type, 9.1.1.3 Item Length, and 91.1.4 Item Value. Which requires the reader to make a leap to connect the following subsections with 9.1.1 To avoid both the leap by the reader and the hanging paragraph, why not: 9.1.1 TTLV Encoding Fields 9.1.1.1 General Every Data object encoded by the TTLV scheme consists of Item Tag (9.1.1.2), Item Type (9.1.1.3), Item Length (9.1.1.4), and Item Value (9.1.1.5), in that order. 9.1.1.2 - 9.1.1.5 follow here. I would make the (9.1.12) into hyperlinks.",,,Avoid hanging paragraph and use of sub-sections as list as shown.,
Technical Advisory Board,TAB-888 ,General Comment on non-cited RFCs,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:39 AM,,18/Mar/14 10:39 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"I checked for citation of RFCs by searching for the keys you defined for each one, hence [RFC6818] but without the brackets, just in case it was cited as a sub-string. All of the citations of the non-cited RFCs are incorrect but I omitted the corrected text on the assumption that you will be deleting non-cited references. Should you decide to cite any of the non-cited RFCs, please consult: The RFC Editor's Bibliographic Table, http://www.rfc-editor.org/in-notes/rfc-ref.txt, or my formatted listing of current RFCs: http://www.durusau.net/standards/rfc/current/ for the correct citations.",,,"If non-cited RFCs become cited, use the correct citations for each one.",
Technical Advisory Board,TAB-887 ,"ANSI, X9.63 - question",Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:33 AM,,18/Mar/14 10:33 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"Appendix E. Acronyms Is Appendix E normative? I ask because it is the only place where: [X9.63] ANSI, X9.63: Public Key Cryptography for the Financial Services Industry, Key Agreement and Key Transport Using Elliptic Curve Cryptography, 2011. is cited in this draft. If Appendix E is normative, then this can remain a normative reference. If Appendix E is non-normative, this reference should be moved into non-normative refernces.",,,Citation is normative or non-normative depending upon your answer on Appendix E. Leave or move as appropriate.,
Technical Advisory Board,TAB-886 ,Normative Reference [X9.57] Not used.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:32 AM,,18/Mar/14 10:32 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"X9.57 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-885 ,Normative Reference [X9.24-1] Not used.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:31 AM,,18/Mar/14 10:31 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"X9.24-1 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-884 ,Normative Reference [SP800-67] Not used.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:31 AM,,18/Mar/14 10:31 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"SP800-67 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-883 ,Normative Reference [SP800-56B] Not used.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:30 AM,,18/Mar/14 10:30 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"SP800-56B is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-882 ,Normative Reference [SP800-38F] Not used.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:29 AM,,18/Mar/14 10:29 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"SP800-38F is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-881 ,Normative Reference [SP800-38E] Not used.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:29 AM,,18/Mar/14 10:29 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"SP800-38E is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-880 ,Normative Reference [SP800-38C] Not used.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:28 AM,,18/Mar/14 10:28 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"SP800-38C is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-879 ,Normative Reference [SP800-38B] Not used.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:28 AM,,18/Mar/14 10:28 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"SP800-38B is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-878 ,Normative Reference [RFC6818] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:27 AM,,18/Mar/14 10:27 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC6818 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-877 ,Normative Reference [RFC6402] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:27 AM,,18/Mar/14 10:27 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC6402 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-876 ,Normative Reference [RFC5756] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:26 AM,,18/Mar/14 10:26 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC5756 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-875 ,Normative Reference [RFC5649] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:25 AM,,18/Mar/14 10:25 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC5649 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-874 ,Normative Reference [RFC5280] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:25 AM,,18/Mar/14 10:25 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC5280 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-873 ,Normative Reference [RFC5272] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:24 AM,,18/Mar/14 10:24 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC5272 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-872 ,Normative Reference [RFC5208] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:24 AM,,18/Mar/14 10:24 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC5208 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-871 ,Normative Reference [RFC4949] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:23 AM,,18/Mar/14 10:23 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC4949 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-870 ,Normative Reference [RFC4880] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:23 AM,,18/Mar/14 10:23 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC4880 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-869 ,Normative Reference [RFC4868] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:22 AM,,18/Mar/14 10:22 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC4868 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-868 ,Normative Reference [RFC4211] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:21 AM,,18/Mar/14 10:21 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC4211 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-867 ,Normative Reference [RFC2510] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:21 AM,,18/Mar/14 10:21 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC2510 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-866 ,Normative Reference [RFC4210] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:20 AM,,18/Mar/14 10:20 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC4210 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-865 ,"Normative Reference [RFC4210], confusion of RFC with its superseding RFC",Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:19 AM,,18/Mar/14 10:19 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC4210] C. Adams, S. Farrell, T. Kause and T. Mononen, Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP), IETF RFC 2510, September 2005, http://www.ietf.org/rfc/rfc4210.txt. Attempting to cite both RFC2510 and its superceding RFC4210. The correct citation for RFC2510 (superseded by RFC4210) reads: [RFC2510] Adams, C. and S. Farrell, ""Internet X.509 Public Key Infrastructure Certificate Management Protocols"", RFC 2510, March 1999. http://www.ietf.org/rfc/rfc2510.txt As a superceded RFC, RFC2510 should not appear as a normative reference. The correct citation for RFC4210 reads: Adams, C., Farrell, S., Kause, T., and T. Mononen, ""Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)"", RFC 4210, September 2005. According to the RFC Editor's Bibliographic Table, http://www.rfc-editor.org/in-notes/rfc-ref.txt, and my formatted listing of current RFCs: http://www.durusau.net/standards/rfc/current/",,,Correct citation.,
Technical Advisory Board,TAB-864 ,Normative Reference [RFC4055] incorrect citation.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:18 AM,,18/Mar/14 10:18 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC4055] J. Schadd, B. Kaliski, and R, Housley, Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile, IETF RFC 4055, June 2055, http://www.ietf.org/rfc/rfc4055.txt. The correct citation reads: RFC4055] Schaad, J., Kaliski, B., and R. Housley, ""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"", RFC 4055, June 2005. http://www.ietf.org/rfc/rfc4055.txt According to the RFC Editor's Bibliographic Table, http://www.rfc-editor.org/in-notes/rfc-ref.txt, and my formatted listing of current RFCs: http://www.durusau.net/standards/rfc/current/",,,Correct citation.,
Technical Advisory Board,TAB-863 ,Normative References [RFC3686] - References collapsed into single listing,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:18 AM,,18/Mar/14 10:18 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC3686] R. Housley, Using Advanced Encryption Standard (AES) Counter Mode with IPsec Encapsulating Security Payload (ESP), IETF RFC 3686, January 2004, http://www.ietf.org/rfc/rfc3686.txt. [RFC4055] J. Schadd, B. Kaliski, and R, Housley, Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile, IETF RFC 4055, June 2055, http://www.ietf.org/rfc/rfc4055.txt. The citations should be broken into separate listing and [RFC4055] should be place in its proper numerical order.",,,"Separate citations, re-order.",
Technical Advisory Board,TAB-862 ,Normative Reference [RFC3686] incorrect citation.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:17 AM,,18/Mar/14 10:17 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC3686] R. Housley, Using Advanced Encryption Standard (AES) Counter Mode with IPsec Encapsulating Security Payload (ESP), IETF RFC 3686, January 2004, http://www.ietf.org/rfc/rfc3686.txt. The correct citation reads: [RFC3686] Housley, R., ""Using Advanced Encryption Standard (AES) Counter Mode With IPsec Encapsulating Security Payload (ESP)"", RFC 3686, January 2004. http://www.ietf.org/rfc/rfc3686.txt According to the RFC Editor's Bibliographic Table, http://www.rfc-editor.org/in-notes/rfc-ref.txt, and my formatted listing of current RFCs: http://www.durusau.net/standards/rfc/current/",,,Correct citation.,
Technical Advisory Board,TAB-861 ,Normative Reference [RFC3647] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:16 AM,,18/Mar/14 10:16 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC3647 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-860 ,Normative Reference [RFC3629] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:15 AM,,18/Mar/14 10:15 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC3629 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-859 ,Normative Reference [RFC3447] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:14 AM,,18/Mar/14 10:14 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC3447 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-858 ,Normative Reference [RFC3394] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:14 AM,,18/Mar/14 10:14 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC3394 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-857 ,Normative Reference [RFC2986] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:13 AM,,18/Mar/14 10:13 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"RFC2986 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Delete citation.,
Technical Advisory Board,TAB-856 ,Normative Reference [RFC2898] incorrect citation.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:12 AM,,18/Mar/14 10:12 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC2898] B. Kaliski, PKCS #5: Password-Based Cryptography Specification Version 2.0, IETF RFC 2898, September 2000, http://www.ietf.org/rfc/rfc2898.txt. The correct citation reads: [RFC2898] Kaliski, B., ""PKCS #5: Password-Based Cryptography Specification Version 2.0"", RFC 2898, September 2000. http://www.ietf.org/rfc/rfc2898.txt According to the RFC Editor's Bibliographic Table, http://www.rfc-editor.org/in-notes/rfc-ref.txt, and my formatted listing of current RFCs: http://www.durusau.net/standards/rfc/current/",,,Correct citation.,
Technical Advisory Board,TAB-855 ,Normative Reference [RFC2315] incorrect citation.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:09 AM,,18/Mar/14 10:09 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC2315] B. Kaliski, PKCS #7: Cryptographic Message Syntax Version 1.5, IETF RFC2315, March 1998, http://www.rfc-editor.org/rfc/rfc2315.txt. The correct citation reads: [RFC2315] Kaliski, B., ""PKCS #7: Cryptographic Message Syntax Version 1.5"", RFC 2315, March 1998. http://www.ietf.org/rfc/rfc2315.txt According to the RFC Editor's Bibliographic Table, http://www.rfc-editor.org/in-notes/rfc-ref.txt, and my formatted listing of current RFCs: http://www.durusau.net/standards/rfc/current/",,,Correct citation.,
Technical Advisory Board,TAB-854 ,Normative Reference [RFC2119] incorrect citation.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:09 AM,,18/Mar/14 10:09 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, IETF RFC 2119, March 1997, http://www.ietf.org/rfc/rfc2119.txt. The correct citation reads: [RFC2119] Bradner, S., ""Key words for use in RFCs to Indicate Requirement Levels"", BCP 14, RFC 2119, March 1997. http://www.ietf.org/rfc/rfc2119.txt According to the RFC Editor's Bibliographic Table, http://www.rfc-editor.org/in-notes/rfc-ref.txt, and my formatted listing of current RFCs: http://www.durusau.net/standards/rfc/current/",,,Correct citation.,
Technical Advisory Board,TAB-853 ,Normative Reference [RFC2104] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:08 AM,,18/Mar/14 10:08 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: H. Krawczyk, M. Bellare, R. Canetti, HMAC: Keyed-Hashing for Message Authentication, IETF RFC 2104, February 1997, http://www.ietf.org/rfc/rfc2104.txt. RFC2104 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Suggest deletion of non-cited reference.,
Technical Advisory Board,TAB-852 ,Normative Reference [RFC1945] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:07 AM,,18/Mar/14 10:07 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: T. Berners-Lee, R. Fielding, H. Frystyk, Hypertext Transfer Protocol -- HTTP/1.0, IETF RFC 1945, May 1996, http://www.ietf.org/rfc/rfc1945.txt. RFC1945 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Suggest deletion of non-cited reference.,
Technical Advisory Board,TAB-851 ,Normative Reference [RFC1424] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:07 AM,,18/Mar/14 10:07 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC1424] B. Kaliski, Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services, IETF RFC 1424, Feb 1993, http://www.ietf.org/rfc/rfc1424.txt. RFC1424 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Suggest deletion of non-cited reference.,
Technical Advisory Board,TAB-850 ,Normative Reference [RFC1421] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:06 AM,,18/Mar/14 10:06 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC1421] J. Linn, Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures, IETF RFC 1421, February 1993, http://www.ietf.org/rfc/rfc1421.txt. RFC1421 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Suggest deletion of non-cited reference.,
Technical Advisory Board,TAB-849 ,Normative Reference [RFC1321] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:06 AM,,18/Mar/14 10:06 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC1321] R. Rivest, The MD5 Message-Digest Algorithm, IETF RFC 1321, April 1992, http://www.ietf.org/rfc/rfc1321.txt. RFC1321 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Suggest deletion of non-cited reference.,
Technical Advisory Board,TAB-848 ,Normative Reference [RFC1320] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:05 AM,,18/Mar/14 10:05 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC1320] R. Rivest, The MD4 Message-Digest Algorithm, IETF RFC 1320, April 1992, http://www.ietf.org/rfc/rfc1320.txt. RFC1320 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Suggest deletion of non-cited reference.,
Technical Advisory Board,TAB-847 ,Normative Reference [RFC1319] not cited.,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:04 AM,,18/Mar/14 10:04 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [RFC1319] B. Kaliski, The MD2 Message-Digest Algorithm, IETF RFC 1319, Apr 1992, http://www.ietf.org/rfc/rfc1319.txt. RFC1319 is not cited in this draft. Not needed as a normative reference, suggest deletion.",,,Suggest deletion of non-cited reference.,
Technical Advisory Board,TAB-846 ,1.2 Normative References - Broken RSA Links,Bug,New,Major,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:03 AM,,18/Mar/14 10:03 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"Broken RSA Links (5) 1.2 Normative References reads in part: ***** [PKCS#1] RSA Laboratories, PKCS #1 v2.1: RSA Cryptography Standard, June 14, 2002, http://www.rsa.com/rsalabs/node.asp?id=2125. [PKCS#5] RSA Laboratories, PKCS #5 v2.1: Password-Based Cryptography Standard, October 5, 2006, http://www.rsa.com/rsalabs/node.asp?id=2127. [PKCS#7] RSA Laboratories, PKCS#7 v1.5: Cryptographic Message Syntax Standard, November 1, 1993, http://www.rsa.com/rsalabs/node.asp?id=2129. [PKCS#8] RSA Laboratories, PKCS#8 v1.2: Private-Key Information Syntax Standard, November 1, 1993, http://www.rsa.com/rsalabs/node.asp?id=2130. [PKCS#10] RSA Laboratories, PKCS #10 v1.7: Certification Request Syntax Standard, May 26, 2000, http://www.rsa.com/rsalabs/node.asp?id=2132. ***** None of those links resolve to the cited material. They all resolve to: http://www.emc.com/domains/rsa/index.htm?id=2125 (with the appropriate id number at the end of the hyperlink)",,,Supply correct links for RSA Laboratories standards cited.,
Technical Advisory Board,TAB-845 ,1.2 Normative References - OASIS Login required?,Bug,New,Major,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:02 AM,,18/Mar/14 10:08 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,2,,,,,References,"1.2 Normative References reads in part: [KMIP-Prof] Key Management Interoperability Protocol Profiles Version 1.2 wd02, June 27, 2013, https://www.oasis-open.org/apps/org/workgroup/kmip/download.php/49689/kmip-profiles-v1.2-wd02.doc. The URL given requires an OASIS login to obtain the document. Did you intend to base conformance on a document that isn't available to others?",,,Supply a public URL for KMIP-Prof.,
Technical Advisory Board,TAB-844 ,1.2 Normative References - out dated reference,Bug,New,Major,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 10:00 AM,,18/Mar/14 10:00 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,References,"1.2 Normative References reads in part: [ECC-Brainpool] ECC Brainpool Standard Curves and Curve Generation v. 1.0.19.10.2005, http://www.ecc-brainpool.org/download/Domain-parameters.pdf. Was there some reason to not cite: [RFC5639] Lochter, M. and J. Merkle, ""Elliptic Curve Cryptography (ECC) Brainpool Standard Curves and Curve Generation"", RFC 5639, March 2010. http://www.ietf.org/rfc/rfc5639.txt, which relies on ECC-Brainpool as a source? You cite [ECC-Brainpool] at 9.1.3.2.5 as a ""recommended"" curve. Would the later reference be better?",,,"Adopt RFC5639 as the appropriate reference and update normative reference to: [RFC5639] Lochter, M. and J. Merkle, ""Elliptic Curve Cryptography (ECC) Brainpool Standard Curves and Curve Generation"", RFC 5639, March 2010. http://www.ietf.org/rfc/rfc5639.txt Delete the current reference.",
Technical Advisory Board,TAB-843 ,Table numbering and captions,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 9:51 AM,,18/Mar/14 9:51 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,Style,"Table numbering and captions should be centered under the appropriate table. See Table 1: Terminology for instance, which is aligned on the left margin. The better practice is centering as was done in KMIP Additional Message Encodings Version 1.0, 4.1.3 Normalizing Names, centered: ""Example python name normalization code""",,,Center table numbers and captions,
Technical Advisory Board,TAB-842 ,Normative versus Non-Normative Text,Bug,New,Major,Unresolved,Unassigned,Patrick Durusau,18/Mar/14 9:48 AM,19/Mar/14 5:15 PM,18/Mar/14 9:48 AM,,Key Management Interoperability Protocol Specification Version 1.2,,,,1,,,,,Normative,"No statement of normative versus non-normative text. Which leads to failure to distinguish normative text from non-normative text. True enough, tables in Appendices B, C, D are marked: ""This table is not normative."" but the same statement is omitted from 9.1.2 Examples, which appears to be non-normative text as well. I assume the Introduction is non-normative? Other examples should be non-normative as well.",,,"Mark sections as normative vs. non-normative or state at the outset that introductions, notes, examples, etc. are all non-normative.",
Technical Advisory Board,TAB-839 ,XML listed in acronyms but not used,Improvement,New,Minor,Unresolved,Unassigned,Jacques Durand,17/Mar/14 8:57 PM,,17/Mar/14 8:57 PM,,Key Management Interoperability Protocol Specification Version 1.2,,Public reviews,,1,,,,,Technical,"""XML"" listed in Appendix E but not used",,,,
Technical Advisory Board,TAB-838 ,Self-referencing and confusing statement in KMIP Client conformance clause,Improvement,New,Major,Unresolved,Unassigned,Jacques Durand,17/Mar/14 8:14 PM,,17/Mar/14 8:14 PM,,Key Management Interoperability Protocol Specification Version 1.2,,Public reviews,,1,,,,,,"Self-referencing and confusing statement in KMIP Client conformance clause: In 12.2: "" A KMIP client implementation SHALL be a conforming KMIP Client ."" Is this an attempt to define what is an [KMIP Client ] implementation ? That should be done independently from the notion of conformance, i.e. in a ""functional"" way, e.g. in a glossary. Then the conformance clause would come in later and say: "" a conforming KMIP Client implementation SHALL satisfy...X, Y Z"". But in any case, the conformance clause should avoid referring to itself (""... SHALL be a conforming KMIP Client ."" where the way to ""conform"" is precisely the object of the clause containing that statement.) Or, if you want to reserve the name ""KMIP Client "" exclusively to designate implementations that fulfill this conformance profile, then assuming that you have previously defined a notion of ""Key management Client "" (actually used in the specification narrative, but undefined), you could say as a general introduction to the KMIP Client conformance profile: ""In order to qualify as a KMIP Client , a Key management Client implementation SHALL satisfy X, Y Z"". Where X, Y, Z are the actual meat of the conformance clause for KMIP Client , i.e. statements that refer to normative content in the specificaiton (e.g. ""satisfy all the mandatory (SHALL) statements in Section 123"" or ""Supports the Client-to-Server operations as defined in sections N to M"")",,,,
Technical Advisory Board,TAB-837 ,Self-referencing and confusing statement in KMIP Server conformance clause,Improvement,New,Major,Unresolved,Unassigned,Jacques Durand,17/Mar/14 8:09 PM,,17/Mar/14 8:15 PM,,Key Management Interoperability Protocol Specification Version 1.2,,Public reviews,,1,,,,,Conformance,"Self-referencing and confusing statement in KMIP Server conformance clause: In 12.1: "" A KMIP server implementation SHALL be a conforming KMIP Server."" Is this an attempt to define what is an [KMIP server] implementation ? That should be done independently from the notion of conformance, i.e. in a ""functional"" way, e.g. in a glossary. Then the conformance clause would come in later and say: "" a conforming KMIP Server implementation SHALL satisfy...X, Y Z"". But in any case, the conformance clause should avoid referring to itself (""... SHALL be a conforming KMIP Server."" where the way to ""conform"" is precisely the object of the clause containing that statement.) Or, if you want to reserve the name ""KMIP Server"" exclusively to designate implementations that fulfill this conformance profile, then assuming that you have previously defined a notion of ""Key management Server "" (actually used a lot in the specification narrative, but undefined), you could say as a general introduction to the KMIP Server conformance profile: ""In order to qualify as a KMIP Server , a Key management Server implementation SHALL satisfy X, Y Z"". Where X, Y, Z are the actual meat of the conformance clause for KMIP Server, i.e. statements that refer to normative content in the specificaiton (e.g. ""satisfy all the mandatory (SHALL) statements in Section 123"" or ""Supports the Server-to-Client operations as defined in sections 4.n to 4.m"")",,,,
Technical Advisory Board,TAB-836 ,"Baseline Server /Client conformance amiss, while too much reliance on externally defined ""Profiles"" conformance",Improvement,New,Major,Unresolved,Unassigned,Jacques Durand,17/Mar/14 7:26 PM,,17/Mar/14 8:17 PM,,Key Management Interoperability Protocol Specification Version 1.2,,Public reviews,,1,,,,,Conformance,"Baseline Server /Client conformance amiss, while too much reliance on externally defined ""Profiles"" conformance: In 12.1: ""An implementation is a conforming KMIP Server if the implementation meets the conditions specified in one or more server profiles specified in [KMIP-Prof]."" I was expecting a notion of ""Server"" conformance independent from Profiles: There are many normative statement is this document that seem to apply regardless of profiles. But they donâ??t seem to be referred to or used in the conformance clause? They should be. There is too much reliance on external documents (â??profilesâ??) in defining conformance to THIS specification. For example, why arenâ??t the Baseline Server and the Baseline Client defined in this spec? Instead they are defined in the [KMIP-Prof] spec which abundantly (and exclusively) refers to the present specification for defining these: too much circularity here... Also: What is referred here (KMIP-Prof) has merely WD status.It is not even part of the set of CSDs. These server ""profiles"" should at least be named explicitly here. Same for Client conformance.",,,,
Technical Advisory Board,TAB-835 ,Server and Client undefined,Improvement,New,Major,Unresolved,Unassigned,Jacques Durand,17/Mar/14 7:12 PM,,17/Mar/14 7:12 PM,,Key Management Interoperability Protocol Specification Version 1.2,,Public reviews,,1,,,,,Conformance,"Section 12 Conformance: ""KMIP Server and Client implementation"" These are not defined anywhere in this document. There should be a functional definition of these types of implementation. Ideally in a glossary.",,,,
Technical Advisory Board,TAB-783 ,Link Redirects - 14,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,24/Feb/14 9:24 AM,,24/Feb/14 9:24 AM,,Key Management Interoperability Protocol Specification Version 1.2,,Public reviews,,0,,,,,Style,"The link checker at: http://validator.w3.org/checklink reports 14 redirects of links in this draft as follows: ***** Line: 4957 http://www.rsa.com/rsalabs/node.asp?id=2129 redirected to http://www.emc.com/domains/rsa/index.htm?id=2129 Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 3545 http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip redirected to https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 3424 http://www.emc.com/ redirected to http://www.emc.com/index.htm Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 4944 http://www.rsa.com/rsalabs/node.asp?id=2125 redirected to http://www.emc.com/domains/rsa/index.htm?id=2125 Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 5233 http://www.itu.int/rec/recommendation.asp?lang=en&parent=T-REC-X.509-200811-1 redirected to http://www.itu.int/rec/T-REC-X.509-200811-1/en Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 4967 http://www.rsa.com/rsalabs/node.asp?id=2132 redirected to http://www.emc.com/domains/rsa/index.htm?id=2132 Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Lines: 3416, 3548 http://www.oasis-open.org/committees/kmip/ redirected to https://www.oasis-open.org/committees/kmip/ Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 3642 http://www.oasis-open.org/ redirected to https://www.oasis-open.org/ Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 3647 http://www.oasis-open.org/policies-guidelines/trademark redirected to https://www.oasis-open.org/policies-guidelines/trademark Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 4962 http://www.rsa.com/rsalabs/node.asp?id=2130 redirected to http://www.emc.com/domains/rsa/index.htm?id=2130 Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 3429 http://www.netapp.com/ redirected to http://www.netapp.com/us/ Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 3553 http://www.oasis-open.org/committees/kmip/ipr.php redirected to https://www.oasis-open.org/committees/kmip/ipr.php Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 3586 http://www.oasis-open.org/policies-guidelines/ipr redirected to https://www.oasis-open.org/policies-guidelines/ipr Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 4951 http://www.rsa.com/rsalabs/node.asp?id=2127 redirected to http://www.emc.com/domains/rsa/index.htm?id=2127 Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. *****",,,Update all redirects to their current links.,
Technical Advisory Board,TAB-782 ,Broken HTML link,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,24/Feb/14 9:21 AM,,24/Feb/14 9:21 AM,,Key Management Interoperability Protocol Specification Version 1.2,,Public reviews,,0,,,,,Style,"Appendix F. List of Figures and Tables reads in part: Figure 1: Cryptographic Object States and Transitions, but the tricky bit is the unseen link which reads: ***** file:///C:%5CUsers%5CPaul%20Knight%5CDocuments%5COASIS-TC%5CKMIP%5Cv1.2%5Ckmip-spec-v1.2%5Ccsd01%5Cpaul3a%5Ckmip-spec-v1.2-csd01.doc#_Toc374104146 ***** The link checker skips local references but this is clearly broken with regard to the draft. It should point to figure 1 in the draft.",,,"Replace the present link under ""Figure 1: Cryptographic Object States and Transitions"" with the correct link to Figure 1 in the document.",
Technical Advisory Board,TAB-781 ,Broken Normative Reference Link,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,24/Feb/14 9:12 AM,,24/Feb/14 9:12 AM,,Key Management Interoperability Protocol Specification Version 1.2,,Public reviews,,0,,,,,References,"1.2 Normative References reads in part: ***** [SP800-57-1] E. Barker, W. Barker, W. Burr, W. Polk, and M. Smid, Recommendations for Key Management - Part 1: General (Revision 3), NIST Special Publication 800-57 Part 1 Revision 3, July 2012, http://csrc.nist.gov/publications/nistpubs/800-57/sp800-57-part1-rev3_general.pdf. ***** The link checker at: http://validator.w3.org/checklink reports: ***** Line: 5212 http://csrc.nist.gov/publications/nistpubs/800-57/sp800-57-part1-rev3_general.pdf Status: 404 Not Found The link is broken. Double-check that you have not made any typo, or mistake in copy-pasting. If the link points to a resource that no longer exists, you may want to remove or fix the link. *****",,,Replace the link for SP800-57-1.,
Technical Advisory Board,TAB-780 ,Broken Normative Reference link,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,24/Feb/14 9:09 AM,,24/Feb/14 9:09 AM,,Key Management Interoperability Protocol Specification Version 1.2,,Public reviews,,0,,,,,References,"1.2 Normative References reads in part: ***** [FIPS186-4] Digital Signature Standard (DSS), FIPS PUB 186-4, July 2013, http://csrc.nist.gov/publications/FIPS/NIST.FIPS.186-4.pdf. ***** The link checker at: http://validator.w3.org/checklink reports: ***** Line: 4904 http://csrc.nist.gov/publications/FIPS/NIST.FIPS.186-4.pdf Status: 404 Not Found The link is broken. Double-check that you have not made any typo, or mistake in copy-pasting. If the link points to a resource that no longer exists, you may want to remove or fix the link. error *****",,,Correct the link for FIPS186-4.,
Technical Advisory Board,TAB-779 ,HTML redirects - 8,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,23/Feb/14 8:14 PM,,23/Feb/14 8:14 PM,,Key Management Interoperability Protocol Specification Version 1.2,,Public reviews,,0,,,,,Style,"The link checker at http://validator.w3.org/checklink reports 8 redirects in links for this draft as follows: ***** warning Line: 706 http://www.oracle.com/ redirected to http://www.oracle.com/index.html Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Lines: 699, 746 http://www.oasis-open.org/committees/xacml/ redirected to https://www.oasis-open.org/committees/xacml/ Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 751 http://www.oasis-open.org/committees/xacml/ipr.php redirected to https://www.oasis-open.org/committees/xacml/ipr.php Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 743 http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=xacml redirected to https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=xacml Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 837 http://www.oasis-open.org/ redirected to https://www.oasis-open.org/ Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 842 http://www.oasis-open.org/policies-guidelines/trademark redirected to https://www.oasis-open.org/policies-guidelines/trademark Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 715 http://www.axiomatics.com/ redirected to https://www.axiomatics.com/ Status: 303 -> 200 OK warning Line: 781 http://www.oasis-open.org/policies-guidelines/ipr redirected to https://www.oasis-open.org/policies-guidelines/ipr Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. *****",,,Update the links to cure the redirects.,
Generated at Fri Mar 21 13:18:55 UTC 2014 by Patrick Durusau using JIRA 6.1.1#6155-sha1:7188aeec9a6b57d61ea04c52f235f15f55c105e2.,,,,,,,,,,,,,,,,,,,,,,,,,,,
,,,,,,,,,,,,,,,,,,,,,,,,,,, OASIS Technical Committees Issue Tracker ,,,,,,,,,,,,,,,,,,,,,,,,,,, Displaying 2 issues at 21/Mar/14 9:43 AM.,,,,,,,,,,,,,,,,,,,,,,,,,,, Project,Key,Summary,Issue Type,Status,Priority,Resolution,Assignee,Reporter,Created,Last Viewed,Updated,Resolved,Affects Version/s,Fix Version/s,Component/s,Due Date,Watchers,Images,Work Ratio,Sub-Tasks,Linked Issues,Environment,Description,Security Level,Labels,Proposal,Resolution Technical Advisory Board,TAB-807 ,Link Redirects 6,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,25/Feb/14 10:47 AM,21/Mar/14 9:43 AM,25/Feb/14 10:47 AM,,Key Management Interoperability Protocol Test Cases Version 1.2,,Public reviews,,0,,,,,Style,"The link checker at: http://validator.w3.org/checklink reports 6 link redirects as follows: ***** Line: 992 http://www.thales-esecurity.com/ redirected to https://www.thales-esecurity.com/ Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 1049 http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip redirected to https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 978 http://www.emc.com/ redirected to http://www.emc.com/index.htm Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Lines: 970, 1051 http://www.oasis-open.org/committees/kmip/ redirected to https://www.oasis-open.org/committees/kmip/ Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 983 http://www.netapp.com/ redirected to http://www.netapp.com/us/ Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 1077 http://www.oasis-open.org/policies-guidelines/ipr redirected to https://www.oasis-open.org/policies-guidelines/ipr Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. *****",,,Update links to their exact URLs., Technical Advisory Board,TAB-806 ,Broken HTML Links,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,25/Feb/14 10:45 AM,,25/Feb/14 10:45 AM,,Key Management Interoperability Protocol Test Cases Version 1.2,,Public reviews,,0,,,,,References,"1.1 References (non-normative) reads in part: ***** [KMIP-SPEC-1_1] Key Management Interoperability Protocol Usage Guide Version 1.1. 01 December 2011. OASIS Standard. http://docs.oasis-open.org/kmip/spec/v1.1/cd01/kmip-spec-1.1-cd-01.doc [KMIP-SPEC-1_2] Key Management Interoperability Protocol Usage Guide Version 1.2. DDD MMM YYYY. Candidate OASIS Standard 01. URL [KMIP-ENCODINGS] KMIP Additional Message Encodings Version 1.0. DDD MMM YYYY. Candidate OASIS Standard 01. URL ***** The link checker at: http://validator.w3.org/checklink reports as follows: ***** Lines: 1731, 1738, 1745 http://docs.oasis-open.org/kmip/spec/v1.1/cd01/kmip-spec-1.1-cd-01.doc Status: 404 Not Found The link is broken. Double-check that you have not made any typo, or mistake in copy-pasting. If the link points to a resource that no longer exists, you may want to remove or fix the link. Broken fragments: http://docs.oasis-open.org/kmip/spec/v1.1/cd01/kmip-spec-1.1-cd-01.doc#_blank (lines 1731, 1738, 1745) ***** The one visible link and the two URL placeholders are broken.",,,Update links to a valid URL., Generated at Fri Mar 21 13:43:27 UTC 2014 by Patrick Durusau using JIRA 6.1.1#6155-sha1:7188aeec9a6b57d61ea04c52f235f15f55c105e2.,,,,,,,,,,,,,,,,,,,,,,,,,,,
,,,,,,,,,,,,,,,,,,,,,,,,,,, OASIS Technical Committees Issue Tracker ,,,,,,,,,,,,,,,,,,,,,,,,,,, Displaying 3 issues at 21/Mar/14 9:41 AM.,,,,,,,,,,,,,,,,,,,,,,,,,,, Project,Key,Summary,Issue Type,Status,Priority,Resolution,Assignee,Reporter,Created,Last Viewed,Updated,Resolved,Affects Version/s,Fix Version/s,Component/s,Due Date,Watchers,Images,Work Ratio,Sub-Tasks,Linked Issues,Environment,Description,Security Level,Labels,Proposal,Resolution Technical Advisory Board,TAB-934 ,Citations without section numbers,Bug,New,Major,Unresolved,Unassigned,Patrick Durusau,19/Mar/14 5:30 PM,21/Mar/14 9:41 AM,20/Mar/14 10:02 AM,,"KMIP Tape Library Profile Version 1.0, KMIP Symmetric Key Lifecycle Profile Version 1.0, KMIP Symmetric Key Foundry for FIPS 140-2 Profile Version 1.0, KMIP Suite B Profile Version 1.0, KMIP Storage Array with Self-Encrypting Drives Profile Version 1.0, KMIP Opaque Managed Object Store Profile Version 1.0, KMIP Cryptographic Services Profile Version 1.0, KMIP Asymmetric Key Lifecycle Profile Version 1.0, Key Management Interoperability Protocol Usage Guide Version 1.2, KMIP Additional Message Encodings Version 1.0",,,,1,,,,,Style,"Just by way of example, 2.2 Suite B minLOS_128 (KMIP Suite B Profile Version 1.0) reads in part: ***** SHALL conform to the Baseline Server profile in [KMIP-PROF] and [KMIP-SPEC] and SHALL support the following Objects [KMIP-SPEC] Certificate [KMIP-SPEC] Symmetric Key [KMIP-SPEC] Public Key [KMIP-SPEC] Private Key [KMIP-SPEC] ***** Citations should include specific section numbers and titles in the cited document. I say that for two reasons: 1) The expert reader (members of this TC) are more likely to recognize an incorrect section citation by its title than by either [KMIP-SPEC] or [KMIP-SPEC:2.2.3]. Say for example if the citation were incorrect and read: [KMIP-SPEC:2.2.7], even an expert reader would be hard pressed to spot that error. On the other hand, if it read: ""Public Key [KMIP-SPEC:2.2.7 Secret Data]"" a TC member would know that wasn't the correct citation. 2) Assuming that all KMIP references between parts of this specification are written KMIP-(key):(number) (title), then it will be possible to automatically validate all of those references. For example, for KMIP-SPEC (the main document), all the section numbers and titles could be automatically extracted and then applied to a document with references to the KMIP-SPEC. By ""applied"" I mean compared to the citations in the text. Where it matches, nothing happens, but, where for whatever reason there is a KMIP cite that does not match, it is highlighted in red (for example). Proofing all the citations, at least to KMIP work, becomes a process of simply scrolling through the document looking for highlights. That won't help if the section citation is correct but substantively incorrect but only a human reader could catch that sort of error. The scripting, assuming reformation of the citations, would not take long and the actual running of the script against all the files would take less than 10 minutes. If not less. I note the work that went into Appendix B and if that effort is to be made on behalf of old users, it is much more necessary for new users of your latest work.",,,"Insert section numbers and titles for all citations of references, thus c. Public Key [KMIP-SPEC:2.2.3 Public Key] noting that ""public key"" appears all over KMIP-SPEC. The section reference makes it clear what is being referenced.", Technical Advisory Board,TAB-805 ,Link Redirects 8,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,25/Feb/14 10:38 AM,,25/Feb/14 10:38 AM,,Key Management Interoperability Protocol Usage Guide Version 1.2,,Public reviews,,0,,,,,Style,"The link checker at: http://validator.w3.org/checklink reports 8 link redirects as follows: ***** Line: 3709 http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip redirected to https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Lines: 3608, 3622 http://www.emc.com/ redirected to http://www.emc.com/index.htm Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 4327 http://www.rsa.com/rsalabs/node.asp?id=2125 redirected to http://www.emc.com/domains/rsa/index.htm?id=2125 Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 4334 http://www.rsa.com/rsalabs/node.asp?id=2132 redirected to http://www.emc.com/domains/rsa/index.htm?id=2132 Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Lines: 3600, 3712 http://www.oasis-open.org/committees/kmip/ redirected to https://www.oasis-open.org/committees/kmip/ Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 4493 http://www.itu.int/rec/recommendation.asp?lang=en&parent=T-REC-X.509-200811-I redirected to http://www.itu.int/rec/T-REC-X.509-200811-I/en Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 3613 http://www.netapp.com/ redirected to http://www.netapp.com/us/ Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. warning Line: 3742 http://www.oasis-open.org/policies-guidelines/ipr redirected to https://www.oasis-open.org/policies-guidelines/ipr Status: 301 -> 200 OK This is a permanent redirect. The link should be updated. *****",,,Update links to their exact URLs., Technical Advisory Board,TAB-804 ,Broken HTML Link,Bug,New,Minor,Unresolved,Unassigned,Patrick Durusau,25/Feb/14 10:36 AM,,25/Feb/14 10:36 AM,,Key Management Interoperability Protocol Usage Guide Version 1.2,,Public reviews,,0,,,,,References,"1.1 References (Normative) reads in part: ***** [FIPS186-4] Digital Signature Standard (DSS). FIPS PUB 186-4. July 2013. http://csrc.nist.gov/publications/fips/fips186-3/fips_186-4.pdf ***** The link checker at: http://validator.w3.org/checklink reports: ***** Line: 4278 http://csrc.nist.gov/publications/fips/fips186-3/fips_186-4.pdf Status: 404 Not Found The link is broken. Double-check that you have not made any typo, or mistake in copy-pasting. If the link points to a resource that no longer exists, you may want to remove or fix the link. ***** The URL I found for this document is: http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf",,,Update the link., Generated at Fri Mar 21 13:41:17 UTC 2014 by Patrick Durusau using JIRA 6.1.1#6155-sha1:7188aeec9a6b57d61ea04c52f235f15f55c105e2.,,,,,,,,,,,,,,,,,,,,,,,,,,,
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]