KB-COMMENT-22: Section 4.1.7, 4 - revisited

[ragges]

KB-COMMENT-22: Section 4.1.7, 4 - revisited

[ragges]

It seems the not-/N style, that Benjamin proposes, is what is mainly used today.
I am ok with a change.

[ragges]

NOTE - the second patch includes an incorrectly correct extra space - it is needed for the table for the IANA application.

[ragges]

NOTE - we also apply for the "TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs registry" entry:
ntske/1
Should we remote the /1 there too? Here is the registry today:
https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids

[KTeichel]

I have no strong opinion on this either way.

[dansarie]

@ragges: the space you removed in db02aa4 is there to ensure proper line breaking in the table in section 7.3.

This change will break compatibility with existing implementations, though that may be a feature...

As for removing the /1 from the ALPN registry entry, I'm opposed. It appears to be more or less the standard to include the version number there, thus enabling protocol version negotiation.

[ragges]

@dansarie (I understood that later, that is why I put it back in the next commit.)

[dansarie]

Oh. I missed that. Sorry.