[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [kmip] KMIP Spec 3.0 wd07 question
Thanks Bruce I missed that. ÂSo we are getting rid of the old form of Link attribute and just making them allTText Strings of varying length.Essentially getting ride of the old structure and Link Type fields, right?ÂÂFrom Section 4.32 Links"The Link identifies the target Managed Object by its Unique Identifier (or by a reference to a Unique Identifier in the current batch of operations) or bhy the Name of the Managed Object."So no way is this clear.One UTF-8 encoding for what exactly:"Name Reference" : supposed to hold a Name value attribute? ÂHow is it encoded?"Reference" : a reference into a current request how?Are there example somewhere for each of these formsBest,
MarkFrom: Bruce Rich <bar@cryptsoft.com>
To: Mark Joseph <mark@p6r.com>
Cc: Tony Cox <tony.cox@cryptsoft.com>, OASIS KMIP Technical Committee <kmip@lists.oasis-open.org>
Sent: 10/27/2020 12:36 PM
Subject: Re: [kmip] KMIP Spec 3.0 wd07 questionMark,I think what you're looking for can be found in sections 10.1.2, 10.1.3 and 11.23. They are new TTLV "types", which look remarkably like TextString.You may not have noticed them, what with the COVID mask and smoke from the fires...(stay safe!)BruceOn Tue, Oct 27, 2020 at 2:22 PM Mark Joseph <mark@p6r.com> wrote:My question is on Section 4.32 LinksEach link type is defined as a "Reference or Name Reference" I cannot find the detailed definition of these structures in the document.Are they defined or to be defined? ÂIf defined can someone point me to the section in the document where a defined structure is defined for these.BestMark JosephP6R, Inc
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]