RE: [kmip] Groups - kmip-https-profile-v1.0-wd04.pdf uploaded

> The reason for requiring that TTLV is supported is that TCP port 5696

> is registered for OASIS KMIP and that means the TTLV encoding and not

> HTTPS as HTTPS is not in the specification. This basically requires

> that TTLV is supported if you are using the port that is defined for

> that protocol but also allows the server to support the HTTPS profile

> in addition - but disallows the use of port 5696 for only HTTPS.

Thanks for the explanation. But I don’t understand where “disallows the use of port 5696 for only HTTPS” comes from (other than in the proposed HTTPS profile document).

Who disallows port 5696 for KMIP/TTLV/HTTP/TLS? Surely not IANA. Port 5696 is recommended but not required for KMIP/TTLV/TLS in the KMIP standard.

What would happen in future with, for example, KMIP/JSON/TLS, KMIP/XML/TLS, KMIP/JSON/HTTP/TLS, KMIP/TTLV/TCP/IPSEC, etc.? Would these all be disallowed from using port 5696 unless KMIP/TTLV/TLS was also running on port 5696?

John

From: Tim Hudson [mailto:tjh@cryptsoft.com]
Sent: Monday, 2 July 2012 3:55 PM
To: John Leiseboer
Cc: kmip@lists.oasis-open.org
Subject: Re: [kmip] Groups - kmip-https-profile-v1.0-wd04.pdf uploaded

On 2/07/2012 3:21 PM, John Leiseboer wrote:

> Submitter's message
> Updated draft including test case (using test case 12.1).
> Applied comments from other TC members.
> -- Tim Hudson

"2.2 KMIP Port Number

KMIP servers conformant to this profile MAY use TCP port number 5696, as assigned by IANA, to receive and send KMIP messages provided that both HTTP and non-HTTP encoded messages are supported."

What’s the reason for requiring both message formats if TCP port 5696 is used?

Why not allow both message formats to use the same port number without making it mandatory?

Suggested replacement text:

"2.2 KMIP Port Number

KMIP servers conformant to this profile MAY use TCP port number 5696, as assigned by IANA, to receive and send KMIP messages ~~provided that both HTTP and non-HTTP encoded messages are supported~~."

John Leiseboer

Thanks for the feedback.

The reason for requiring that TTLV is supported is that TCP port 5696 is registered for OASIS KMIP and that means the TTLV encoding and not HTTPS as HTTPS is not in the specification. This basically requires that TTLV is supported if you are using the port that is defined for that protocol but also allows the server to support the HTTPS profile in addition - but disallows the use of port 5696 for only HTTPS.

That matches the previous discussions on this profile and the discussions around the IANA port allocation.

Thanks,
Tim.

kmip message