On Thu, May 20, 2021 at 04:15:27PM -0700, Nick Harper wrote:
> > But, it makes for a fairly terrible user interface for the human
> > operator. Compare:
> >
> > * managesieve
> > * 6d616e6167657369657665
> >
> > Typos in hex values are easy to make and hard to recognise.
>
> I agree that
On Thu, May 20, 2021 at 3:56 PM Viktor Dukhovni
wrote:
> I agree it is a straight-forwarding encoding for machines, and it is
> well suited for the GREASE code points.
>
> But, it makes for a fairly terrible user interface for the human
> operator. Compare:
>
> * managesieve
> * 6d616e61
On Thu, May 20, 2021 at 11:52:50AM -0700, Nick Harper wrote:
> > Since the likelihood of actually adding exotic ALPN values to the
> > registry appears slim, why not say so. That would leave the exotic
> > values for private on-the-wire use, while allowing DNS and other
> > configuration serialis
On Thu, May 20, 2021 at 11:19 AM Viktor Dukhovni
wrote:
> On Thu, May 20, 2021 at 01:46:38PM -0400, Ryan Sleevi wrote:
>
> > > It is fine for the TLS protocol to not care, but the *standard* ALPN
> > > values in the IANA registry (that might then also appear in DNS
> > > zone files, configuration
On Thu, May 20, 2021 at 01:46:38PM -0400, Ryan Sleevi wrote:
> > It is fine for the TLS protocol to not care, but the *standard* ALPN
> > values in the IANA registry (that might then also appear in DNS
> > zone files, configuration files, ...) a more restricted character
> > set would actually be
On Thu, May 20, 2021 at 1:03 PM Viktor Dukhovni
wrote:
> On Thu, May 20, 2021 at 04:45:23PM +, Andrei Popov wrote:
>
> > ALPN IDs are byte strings; the fact that some of them can be displayed
> > as ASCII character strings merely reflects the fact that those ALPN
> > IDs were chosen by humans
On Thu, May 20, 2021 at 04:45:23PM +, Andrei Popov wrote:
> ALPN IDs are byte strings; the fact that some of them can be displayed
> as ASCII character strings merely reflects the fact that those ALPN
> IDs were chosen by humans😊.
That's fine when they're just private signalling between a hom
+1 what Ryan said. Especially the point that added restrictions aren’t a viable
path to better interoperability.
ALPN IDs are byte strings; the fact that some of them can be displayed as ASCII
character strings merely reflects the fact that those ALPN IDs were chosen by
humans😊.
Cheers,
Andre
