Opened 13 years ago

Closed 13 years ago

#7 closed protocol defect (fixed)

CoAP ports

Reported by: zach@… Owned by: zach@…
Priority: minor Milestone:
Component: coap Version:
Severity: - Keywords:


The current coap-00 has text on the CoAP port that needs work:

"4.2. Default Port

CoAP SHOULD use a default port of 61616 which is within the compressed UDP port space defined in [RFC4944]. As this port is in the dynamic port space, it however can not be reserved for CoAP use."

On 2010-6-11, at 13:49, Zach Shelby wrote:
I was just about to make a ticket on this Lars. What do you suggest we do here, I mean we can live with ports outside of 61616-61632. Should we define a default CoAP port in the registered range, and then recommend (SHOULD/MUST?) that a port in the LoWPAN range is also supported on 6LoWPAN end-nodes?

I think you should definitely (also) ask for a port in the registered range, for deployments that may need this. Whether you want to recommend this port as the default I don't know, because the compression then becomes slightly less efficient.

Change History (1)

comment:1 Changed 13 years ago by zach@…

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in coap-01 with the following text:

4.2.  Default Port

   The CoAP default port number [TBD1] MUST be supported by a server for
   resource discovery (see Section 6) and SHOULD be supported for
   providing access to other resources.  In addition other end-points
   may be hosted in the dynamic port space.

   When a CoAP server is hosted by a 6LoWPAN node, it SHOULD support a
   port in the 61616-61632 compressed UDP port space defined in

Note: See TracTickets for help on using tickets.