… Scharf SCTP: Michael Tuexen DCCP: Eddie Kohler and Yoshifumi Nishida Reference RFC6335 Note Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP. Service names are assigned on a first…

… Scharf SCTP: Michael Tuexen DCCP: Eddie Kohler and Yoshifumi Nishida Reference RFC6335 Note Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP. Service names are assigned on a first…

…d the registration of the TCP well-known port 995 using the following template [RFC6335]: Service Name: pop3s Transport Protocol: TCP Assignee: IESG <iesg@ietf.org> Contact: IETF Chair <chair@ietf.org> Description: POP3 over TLS protocol Reference: RFC 8314 Port Number: 995 Moore…

… the registration of the TCP well-known port 995 using the following template [ RFC6335 ]: Service Name: pop3s Transport Protocol: TCP Assignee: IESG <iesg@ietf.org> Contact: IETF Chair <chair@ietf.org> Description: POP3 over TLS protocol Reference: RFC 8314 Port Number: 995 Moor…

…unneling). IANA has updated this assignment to refer to this document. As per [ RFC6335 ], the Assignee is [IESG] and the Contact is [IETF_Chair]. Please note that the TCP port 9899 (sctp-tunneling) assignment is not needed anymore, and IANA has removed this TCP port number assig…

…e record types are used -- notably "TXT", "SRV", and "URI" [RFC1035] [RFC2782] [RFC6335] [RFC7553]. It provides efficient separation of one use of them from others. Absent this separation, an undifferentiated mass of these RRsets is returned to the DNS client, which then must par…

…alue into Service Name and Transport Protocol Port Number Registry defined in [ RFC6335 ]. Service Name: wot Transport Protocol: TCP, UDP Description: Service name to search for the Thing Description of a Thing or a Thing Description Directory in the W3C Web of Things Port Number…

…ord types are used -- notably "TXT", "SRV", and "URI" [ RFC1035 ] [ RFC2782 ] [ RFC6335 ] [ RFC7553 ]. It provides efficient separation of one use of them from others. Absent this separation, an undifferentiated mass of these RRsets is returned to the DNS client, which then must …

…port 53 but MAY be from the "first-come, first-served" port range (User Ports [ RFC6335 ], range 1024-49151). This recommendation against the use of port 53 for DNS over DTLS is to avoid complications in selecting use or non-use of DTLS and to reduce risk of downgrade attacks. A …

… may also be used for other purposes, such as in DNS SRV records." (Quoted from RFC6335 ], Section 5 8. Wildcards Wildcard: RFC1034 defined "wildcard", but in a way that turned out to be confusing to implementers. For an extended discussion of wildcards, including clearer definit…

…System range. The registry for that range requires IETF Review or IESG Approval RFC6335 Service Name: domain-s Port Number: 853 Transport Protocol(s): UDP Assignee: IESG Contact: IETF Chair Description: DNS query-response protocol run over DTLS or QUIC Reference: RFC7858 RFC8094 …

…e is not a "protocol." However, like a service name as defined in Section 5 of [RFC6335] , it often identifies a particular protocol or application. If a scheme name has a one-to-one correspondence with a service name, then the names SHOULD be the same. Some organizations desire …

…e is not a "protocol." However, like a service name as defined in Section 5 of [RFC6335] , it often identifies a particular protocol or application. If a scheme name has a one-to-one correspondence with a service name, then the names SHOULD be the same. Some organizations desire …

…stem Range. The registry for that range requires IETF Review or IESG Approval [ RFC6335 ], and such a review was requested using the early allocation process [ RFC7120 for the well-known TCP port in this document. IANA has reserved the same port number over UDP for the proposed D…

…may also be used for other purposes, such as in DNS SRV records." (Quoted from [RFC6335], Section 5 . Wildcards Wildcard: [ RFC1034 ] defined "wildcard", but in a way that turned out to be confusing to implementers. For an extended discussion of wildcards, including clearer defin…