Application for Service Names and User Port Numbers (original) (raw)

  1. If broadcast/multicast is used, how and what for?

See RFC 7605, section 7.6.

  1. If UDP is requested, please explain how traffic is limited, and whether the protocol reacts to congestion.

See RFC 7605, section 7.6, and RFC 8085. Please address RFC 8085 recommendations directly.

  1. If UDP is requested, please indicate whether the service is solely for the discovery of hosts supporting this protocol.

See RFC 7605, sections 7.1, 7.2, and 7.6.

  1. Please explain how your protocol supports versioning.

See RFC 7605, sections 7.1 and 7.5.

  1. If your request is for more than one transport, please explain in detail how the protocol differs over each transport.

See RFC 7605, section 7.6.

  1. Please describe how your protocol supports security. Note that new services are expected to support security capabilities and to avoid insecure variants.

See RFC 7605, sections 7.1, 7.4, and 8.

  1. Please explain why a unique port assignment is necessary as opposed to a port in range (49152-65535) or existing port.

See RFC 7605, sections 7.1 and 7.2.

  1. Please explain the state of development of your protocol.

See RFC 7605, sections 7.7 and 7.8.

  1. If SCTP is requested, is there an existing TCP and/or UDP service name or port number assignment? If yes, provide the existing service name and port number.

  2. What specific SCTP capability is used by the application such that a user who has the choice of both TCP (and/or UDP) and SCTP ports for this application would choose SCTP?

See RFC 4960, section 7.1, and RFC 7605, section 7.6.

  1. Please provide any other information that would be helpful in understanding how this protocol differs from existing assigned services.

See RFC 7605 as a whole, but especially sections 7.2, 7.3, and 7.9.