Re: [Webpush] [IANA #929427] Last Call: <draft-ietf-webpush-protocol-10.txt> (Generic Event Delivery Using HTTP Push) to Proposed Standard

[Brian Raymor <[e-mail]>]

On October 11, 2016, at 6:17 AM, Alissa Cooper <[e-mail]> wrote:

> I had assumed that port 1001 was specified in this document because it’s already in use.
> Assuming the authors definitely want 1001 assigned for this purpose, the WG chairs will
> need to do a quick consensus call about requesting early allocation for port 1001. Assuming
> the WG has consensus to do that, the chairs can then send a request for early allocation to IANA.

If it would be simpler, then it would be acceptable to change 1001 to TBD and request IANA to
make the assignment.

This is related to https://github.com/webpush-wg/webpush-protocol/issues/37. We could not specify the port
numbers that are currently in use for push services because 5223 and 5228 are already registered with IANA for 
other protocols. (The ports are registered to hpvirtgrp and hpvroom, although unofficially used by APNS and GCM.)
In reviewing RFC6335 Section 8.1.1, perhaps I misinterpreted the guidance to provide a suggestion to IANA, which
is why 1001 was requested:

https://tools.ietf.org/html/rfc6335

   o  Port Number: If assignment of a port number is desired, either the
      port number the requester suggests for assignment or indication of
      port range (user or system) MUST be provided.  If only a service
      name is to be assigned, this field is left empty.  If a specific
      port number is requested, IANA is encouraged to assign the
      requested number.  If a range is specified, IANA will choose a
      suitable number from the User or System Ports ranges.  Note that
      the applicant MUST NOT use the requested port in implementations
      deployed for use on the public Internet prior to the completion of
      the assignment, because there is no guarantee that IANA will
      assign the requested port.

...Brian