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

[John Leiseboer <jl@quintessencelabs.com>]

> From: kmip@lists.oasis-open.org [mailto:kmip@lists.oasis-open.org] On
> Behalf Of Tim Hudson
> Sent: Friday, 27 July 2012 4:14 AM
> To: kmip@lists.oasis-open.org
> Subject: Re: [kmip] Groups - kmip-https-profile-v1.0-wd04.pdf uploaded
...
> 4) if a vendor elects to use the IANA registered port (5696) for
> offering KMIP services then in order to conform with this profile they
> must support the protocol registered with IANA for that port as well
Practical implications of this for server vendors who wish to ensure that their servers remain compliant with the standard if this proposal is accepted:

If a user elects to enable KMIP/HTTPS and disable KMIP/TTLV must either
a. Disallow the user from configuring port 5696 for KMIP/HTTPS, or
b. Override user's wishes and enable KMIP/TTLV on port 5696

Reason given: because port 5696 is assigned for KMIP/TTLV and another service cannot use that same port unless KMIP/TTLV uses that port at the same time as well.

The same logic leading to a and b above, if applied consistently to other services with ports assigned by IANA, would require:
aa. Disallow user from configuring port 22 for KMIP/TTLV, KMIP/HTTPS, or any service other than SSH, or
ab. Enable SSH on port 22 if a user configures [KMIP/TTLV | KMIP/HTTPS | Telnet | SMTP | ...] on port 22

ba. Disallow user from configuring port 25 for KMIP/TTLV, KMIP/HTTPS, or any service other than SMTP, or
bb. Enable SMTP on port 25 if a user configures [KMIP/TTLV | KMIP/HTTPS | Telnet | SSH | ...] on port 25

etc.

John