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

[Tim Hudson <tjh@cryptsoft.com>]

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.