Re: [TLS] Registry for ALPN

[Yoav Nir <[e-mail]>]

Hi Martin

Any reason for "expert review" rather than "first come first serve"? 

What meaningful input can a designated expert have on someone asking for a string for their proprietary protocol?

Yoav

On Aug 26, 2013, at 10:55 PM, Martin Thomson <[e-mail]> wrote:

> draft-ietf-tls-applayerprotoneg-01 describes a registry for new
> strings, but it does not describe what rules that registry operates
> under, nor does it describe what information a registration is
> expected to contain.
> 
> I'm going to suggest that "Expert Review" [RFC5226] is sufficient for
> this registry.  Here's what I propose the document describe.
> 
> OLD:
>   This document also requires the IANA to create a registry of
>   Application Layer Protocol Negotiation protocol byte strings,
>   initially containing the following entries:
> 
>   [... registrations ...]
> 
>   We propose that this new registry be created in a new page entitled:
>   "Application Layer Protocol Negotiation (ALPN) Protocol IDs" beneath
>   the existing heading of "Transport Layer Security (TLS)".
> 
> NEW:
>  This document establishes a registry for protocol identifiers entitled
>   "Application Layer Protocol Negotiation (ALPN) Protocol IDs" under the
>   existing "Transport Layer Security (TLS)" heading.
> 
>   Entries in this registry require the following fields:
> 
>    Protocol: The name of the protocol.
>    Identification Sequence: The precise set of octet values that identifies
>       the protocol.  This could be the UTF-8 encoding [RFC3269] of the
>       protocol name.
>    Specification: A reference to a specification that defines the protocol.
> 
>   This registry operates under the "Expert Review" policy as defined
>   in [RFC5226].  The designated expert is advised to encourage the
>   inclusion of a reference to a permanent and readily available
>   specification that enables the creation of interoperable
>   implementations of the identified protocol.
> 
>   An initial set of registrations for this registry follow:
> 
>    Protocol: HTTP/1.1
>    Identification Sequence:
>       0x68 0x74 0x74 0x70 0x2f 0x31 0x2e 0x31 ("http/1.1")
>    Specification: RFC 2616
> 
>    Protocol: SPDY/1
>    Identification Sequence:
>       0x68 0x74 0x74 0x70 0x2f 0x31 0x2e 0x31 ("http/1.1")
>   Specification:
>       http://dev.chromium.org/spdy/spdy-protocol/spdy-protocol-draft1
> 
> etc...
> _______________________________________________
> TLS mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tls