On 2011-1-27, at 18:58, t.petch wrote:
And what happens when we have ProtocolX over SSH and ProtocolX over TLS?
Must they share a port, with ProtocolX, which has been quietly using its
assigned port for
No. The expert reviewer can obviously assign a second port in that case (if
ProtocolX doesn't have a feature negotiation capability built in so that the
port could be shared.)
But we don't want to allocate multiple ports for the different security flavors
of *new* protocols. At least we want this to be the exception.
The expert team is (from what I hear) seeing frequent applications that look
like "Hi, we're company X and our foo protocol runs on TCP. We'd like a port
for that, and one for when we run foo over TLS."
Description: S/MIME cryptographic signature
Ietf mailing list