OASIS Key Management Interoperability Protocol (KMIP) TC

 View Only
Expand all | Collapse all

Groups - KMIP Profiles (kmip-profiles-1.0-editors-draft-0.99.doc) uploaded

  • 1.  Groups - KMIP Profiles (kmip-profiles-1.0-editors-draft-0.99.doc) uploaded

    Posted 10-21-2009 21:34
    The document revision named KMIP Profiles
    (kmip-profiles-1.0-editors-draft-0.99.doc) has been submitted by Subhash
    Sankuratripati to the OASIS Key Management Interoperability Protocol (KMIP)
    TC document repository.  This document is revision #3 of
    kmip-1.0-profiles-0.98.doc.
    
    Document Description:
    Definition of KMIP profiles for conformance and interoperability
    
    View Document Details:
    http://www.oasis-open.org/committees/document.php?document_id=34785
    
    Download Document:  
    http://www.oasis-open.org/committees/download.php/34785/kmip-profiles-1.0-editors-draft-0.99.doc
    
    Revision:
    This document is revision #3 of kmip-1.0-profiles-0.98.doc.  The document
    details page referenced above will show the complete revision history.
    
    
    PLEASE NOTE:  If the above links do not work for you, your email application
    may be breaking the link into two pieces.  You may be able to copy and paste
    the entire link address into the address field of your web browser.
    
    -OASIS Open Administration
    


  • 2.  RE: [kmip] Groups - KMIP Profiles(kmip-profiles-1.0-editors-draft-0.99.doc) uploaded

    Posted 10-22-2009 04:23
    Subhash,
    
    I believe on line 72 you intend SHALL NOT rather than SHOULD NOT. 
    
    In addition, I do not understand the purpose or value of the 5.1 Raw Server Conformance Profile.  This among other things would permit servers to assert KMIP conformance, without supporting any identified real-world client use cases.  If we want a minimalist server profile, what's wrong with the Base profile in Spec-12.1 which already requires Query?  With Query clients can (and must) already determine server capabilities before further activity.
    
    Regards,
    Steve W.
    HP