…iate security association for incoming records. Some transports, such as DCCP [ RFC4340 ], provide their own sequence numbers. When carried over those transports, both the DTLS and the transport sequence numbers will be present. Although this introduces a small amount of ineffici…

…ty association for incoming records without CIDs. Some transports, such as DCCP RFC4340 , provide their own sequence numbers. When carried over those transports, both the DTLS and the transport sequence numbers will be present. Although this introduces a small amount of inefficie…

…ding a complete specification. The Datagram Congestion Control Protocol (DCCP) [RFC4340] requires implementations to support Classical PMTUD and states that a DCCP sender "MUST maintain the MPS allowed for each active DCCP session". It also defines the current congestion control …

…LMTUD) [ RFC4821 ], as well as mechanisms inside transport protocols [ RFC793 ][RFC4340][ RFC4960 ]. The following subsections summarize the interactions between tunnels and MTU issues, including minimum tunnel MTUs, tunnel fragmentation and reassembly, and MTU discovery. 4.2.1 .…

…m such as a Selective Acknowledgment (SACK) scoreboard [RFC3517] or ACK Vector [RFC4340] to distinguish real losses from reordered data, although implicit mechanisms such as TCP Reno style duplicate acknowledgments counting are sufficient. PLPMTUD can also be implemented in proto…

…tocol (SCTP) [ RFC4960 ], and the Datagram Congestion Control Protocol (DCCP) [ RFC4340 ]. In this case, the transport is responsible for ensuring that transmitted segments (except probes) conform to the Path MTU, including supporting PMTU Discovery probe transmissions as needed.…

…eader. Since the ICMPv6 [ RFC4443 ], TCP [ RFC793 ], UDP [ RFC768 ], and DCCP [ RFC4340 ] headers contain checksums that cover the IP header, if the address mapping algorithm is not checksum neutral, the checksum MUST be evaluated before translation and the ICMP and transport-lay…

…eader. Since the ICMPv6 [ RFC4443 ], TCP [ RFC793 ], UDP [ RFC768 ], and DCCP [ RFC4340 ] headers contain checksums that cover the IP header, if the address mapping algorithm is not checksum neutral, the checksum MUST be evaluated before translation and the ICMP and transport-lay…

…FC4283 TLS ClientCertificateType Identifiers 0-63 [ RFC5246 DCCP Packet Types [ RFC4340 4.10 . IESG Approval New assignments may be approved by the IESG. Although there is no requirement that the request be documented in an RFC, the IESG has the discretion to request documents or…

…FC4283 TLS ClientCertificateType Identifiers 0-63 [ RFC5246 DCCP Packet Types [ RFC4340 4.10 . IESG Approval New assignments may be approved by the IESG. Although there is no requirement that the request be documented in an RFC, the IESG has the discretion to request documents or…

…FC4283 TLS ClientCertificateType Identifiers 0-63 [ RFC5246 DCCP Packet Types [ RFC4340 4.10 . IESG Approval New assignments may be approved by the IESG. Although there is no requirement that the request be documented in an RFC, the IESG has the discretion to request documents or…

… used with ICE, such as TCP or the Datagram Congestion Control Protocol (DCCP) [RFC4340]. <foundation>: is composed of 1 to 32 <ice-char>s. It is an identifier that is equivalent for two candidates that are of the same type, share the same base, and come from the same STUN server…

…used with ICE, such as TCP or the Datagram Congestion Control Protocol (DCCP) [ RFC4340 ]. <foundation>: is composed of 1 to 32 <ice-char>s. It is an identifier that is equivalent for two candidates that are of the same type, share the same base, and come from the same STUN serve…

…used with ICE, such as TCP or the Datagram Congestion Control Protocol (DCCP) [ RFC4340 ]. <foundation>: is composed of 1 to 32 <ice-char>s. It is an identifier that is equivalent for two candidates that are of the same type, share the same base, and come from the same STUN serve…

…used with ICE, such as TCP or the Datagram Congestion Control Protocol (DCCP) [ RFC4340 ]. <foundation>: is composed of 1 to 32 <ice-char>s. It is an identifier that is equivalent for two candidates that are of the same type, share the same base, and come from the same STUN serve…