On 2/07/2012 4:54 PM, John Leiseboer wrote:
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.
Port 5696 is registered with IANA for kmip and that means registered
for what is in the official specification and hence the TTLV
encoding.
Suggesting using 5696 for something other than the encoding defined
would be like running KMIP on port 25 instead of SMTP - you can of
course technically do that however that isn't what a client would
expect.
Having been the lucky person that was selected to answer the various
technical questions from IANA on the port allocation I'm quite
familiar with their views on such things.
From a pragmatic point of view, if you offer services on port 5696
you really need to ensure that the server on that port will respond
in a manner that a client using the officially registered port would
expect. If you elect to not support TTLV then you will impact
interoperability - and as the purpose of KMIP is interoperability
and each time we have looked at an issue the direction we have taken
is to err on the side of what will help ensure interoperability is
the result.
For reference, some vendors operate on port 5696, some on 443, some
on both, and some on an entirely different port.
Naturally enough you can elect to ignore the conformance statements
in the specification, the profile, and this document too but in
doing so you cannot claim conformance as that requires implementing
and supporting each of the mandatory statements in each of the
documents.
Thanks,
Tim.
|