D

DNS-Based Authentication of Named Entities. It lets a domain publish, in DNSSEC-signed DNS records, which certificates or keys its TLS servers use.

Plain language DNS-Based Authentication of Named Entities; lets a domain publish in DNSSEC-signed DNS records which certificates its TLS servers use.

Used in RFC 6698 RFC 7250 RFC 7305 RFC 7671 RFC 7672 RFC 8310 RFC 8460 RFC 8689 RFC 9102

A large contiguous block of routed IP addresses that are not assigned to any real hosts, allowing the network operator to detect any traffic arriving for those addresses as suspicious or unauthorized.

Used in RFC 4948 RFC 6018

A WebRTC channel for sending arbitrary application data between peers. It is built from a pair of SCTP streams that share the same stream identifier.

Plain language A WebRTC channel for sending arbitrary application data between peers, built from SCTP streams sharing the same stream identifier.

Used in RFC 1037 RFC 8831 RFC 8832 RFC 8848 RFC 8850 RFC 8864 RFC 8865

A separate TCP connection that FTP opens to carry a file or a directory listing. By default the server uses the port one below its control port (port 20), and the user may choose other ports with PORT or PASV.

Plain language A separate TCP connection FTP opens to carry a file or directory listing, by default on the port one below the control port.

Used in RFC 294 RFC 354 RFC 454 RFC 463 RFC 542 RFC 604 RFC 624 RFC 959 RFC 1579 RFC 1639 RFC 2228 RFC 2428 RFC 2577 RFC 3659 RFC 4217 RFC 7663

A cryptographic key used to encrypt the plaintext of a message and to compute message integrity checks. A new DEK is generated for each message.

Plain language A cryptographic key encrypting plaintext and computing message integrity checks; a new DEK is generated for each message.

Used in RFC 989 RFC 1040 RFC 1113 RFC 1848

DES is a symmetric cipher standardized in 1977, with a 56-bit key. It was widely used for decades but is now considered insecure against modern attacks.

Plain language Data Encryption Standard; a symmetric cipher standardized in 1977 with a 56-bit key, now considered insecure.

Used in RFC 1507 RFC 1750 RFC 1825 RFC 1968 RFC 2268 RFC 2574 RFC 3607 RFC 4131 RFC 4772 RFC 5469 RFC 6649

In TRILL, the label that scopes MAC address learning: either a VLAN or a Fine-Grained Label (FGL).

Plain language In TRILL, the label scoping MAC address learning: either a VLAN or a Fine-Grained Label (FGL).

Used in RFC 7067 RFC 7174 RFC 7357 RFC 8383

A protocol for bridging data link layer traffic (such as SNA and NetBIOS) over TCP/IP networks, used to connect legacy systems.

Plain language Data Link Switching; a protocol for bridging data link layer traffic over TCP/IP networks.

Used in RFC 2114 RFC 2166

A privacy principle of limiting the amount of data disclosed to only what is absolutely necessary to complete a specific protocol exchange or service.

Plain language A privacy principle limiting disclosed data to only what is necessary to complete a specific protocol exchange or service.

Used in RFC 6973 RFC 8165 RFC 9614

A lower-level model of managed objects that includes the implementation and protocol-specific details needed to build and use them.

Plain language A lower-level model of managed objects including implementation and protocol-specific details needed to build and use them.

Used in RFC 3216 RFC 3444 RFC 5070 RFC 5706 RFC 6020 RFC 6244 RFC 8477 RFC 8949

The part of a network device that performs per-packet operations: receiving packets, looking up routes, and forwarding them to the correct output interface.

Plain language The part of a network device performing per-packet operations: receiving, looking up routes, and forwarding packets.

Used in RFC 5493 RFC 5818 RFC 6041 RFC 8029

A self-contained packet of data sent across a network with enough addressing information to be delivered on its own, without a connection set up beforehand.

Plain language A self-contained packet sent across a network with enough addressing information to be delivered on its own.

Used in RFC 59 RFC 60 RFC 68 RFC 71 RFC 240 RFC 252 RFC 255 RFC 267 RFC 270 RFC 298 RFC 303 RFC 306 RFC 321 RFC 335 RFC 342 RFC 344 RFC 353 RFC 362 RFC 366 RFC 515 RFC 528 RFC 618 RFC 662 RFC 677 and 272 more

A protocol for sending queries and results between programs over the network to access data stored in a remote database.

Plain language A protocol for sending queries and results between programs over the network to access remote database data.

Used in RFC 420 RFC 610

A conceptual place to store and access information. It might be implemented with files, a database, flash memory locations or a mix of these.

Plain language A conceptual place to store and access information, implemented with files, a database, flash memory, or a mix.

Used in RFC 6110 RFC 6241 RFC 6244 RFC 7950 RFC 7952 RFC 8040 RFC 8072 RFC 8341 RFC 8342 RFC 8344 RFC 8345 RFC 8346 RFC 8407 RFC 8525 RFC 8526 RFC 8527 RFC 8641

The Datagram Congestion Control Protocol, a transport protocol that delivers datagrams without guaranteeing delivery but with a choice of congestion control.

Plain language The Datagram Congestion Control Protocol; a transport protocol delivering datagrams without guaranteeing delivery but with congestion control options.

Used in RFC 4341 RFC 4342 RFC 5238 RFC 5595 RFC 5596 RFC 5597 RFC 5762 RFC 6012 RFC 6773 RFC 8311 RFC 9897

The Dynamic Delegation Discovery System, an abstract algorithm that applies dynamically retrieved string transformation rules to an application-unique string until a terminal condition is reached.

Plain language The Dynamic Delegation Discovery System; an abstract algorithm applying dynamically retrieved string transformation rules until a terminal condition is reached.

Used in RFC 3401 RFC 3403 RFC 3406 RFC 3761 RFC 3764 RFC 3958 RFC 4848 RFC 5986 RFC 6116 RFC 6950

A distributed denial-of-service attack, in which traffic from many sources is directed at a target to harm its availability or functionality.

Plain language Distributed denial-of-service attack; traffic from many sources directed at a target to harm its availability or functionality.

Used in RFC 4778 RFC 4832 RFC 4948 RFC 5635 RFC 6545 RFC 8612 RFC 8783 RFC 8903 RFC 9066 RFC 9132 RFC 9244 RFC 9387

A receiver buffer that holds arriving packets for a short time before playing them out, so that variation in arrival times does not disturb real-time media.

Plain language A receiver buffer holding arriving packets for a short time before playing them out so arrival variation does not disturb real-time media.

Used in RFC 2215 RFC 4737 RFC 7002 RFC 7003 RFC 8015 RFC 9801

Processing a biased or lopsided stream of bits, for example one that has too many ones, to make it closer to an even mix of zeros and ones. Simple methods are taking the parity of a run of bits and von Neumann's pair-dropping trick.

Plain language Processing a biased bit stream to make it closer to an even mix of zeros and ones.

Used in RFC 4086

An IKE mechanism by which a node concludes that its remote peer is dead or has rebooted. RFC 5660 lets such a conclusion break connection latches with that peer.

Plain language An IKE mechanism concluding that a remote peer is dead or has rebooted.

Used in RFC 4555 RFC 5660

The node that decides which PCN flows to admit and which to terminate. It can be the PCN-ingress-node itself or a separate centralized control node. In both cases the PCN-ingress-node is the point where the decisions are enforced.

Plain language The node that makes the call on which new flows to let in and which existing ones to shut down.

Used in RFC 6661 RFC 6662

A bit string, sent in one or more RTP packets, that completely resets a media decoder to a known state. Examples include Intra pictures, IDR pictures and keyframes.

Plain language A bit string sent in one or more RTP packets completely resetting a media decoder to a known state.

Used in RFC 5104 RFC 8082

Examination of the full content of network packets to identify traffic types and apply network policies. DPI can see the content of user communications and raises privacy concerns.

Plain language Examination of the full content of network packets to identify traffic types and apply network policies.

Used in RFC 6108 RFC 7754 RFC 8404 RFC 9505

A lossless compression method that other formats, such as zlib and gzip, use to store their compressed data.

Plain language A lossless compression method used by other formats such as zlib and gzip to store compressed data.

Used in RFC 1950 RFC 1952 RFC 1979 RFC 2083 RFC 3274 RFC 5402 RFC 8054

A networking approach for links that are slow, intermittent or disrupted. Nodes pass data along as self-contained bundles using store-and-forward delivery.

Plain language A networking approach for slow, intermittent, or disrupted links where nodes pass self-contained bundles using store-and-forward delivery.

Used in RFC 4838 RFC 5050 RFC 6257 RFC 8884 RFC 9171 RFC 9173 RFC 9891

A short-lived credential, issued under a certificate holder's authority, that lets another server prove its identity in a TLS handshake without using the certificate's own private key.

Plain language A short-lived credential issued under a certificate holder's authority, letting another server prove identity without the certificate's private key.

Used in RFC 5588 RFC 9677

Handing responsibility for part of a name or number space to another party, who then manages the data for that part.

Plain language Handing responsibility for part of a name or number space to another party who then manages it.

Used in RFC 882 RFC 1507 RFC 2317 RFC 2693 RFC 2743 RFC 3010 RFC 3402 RFC 3530 RFC 3755 RFC 5074 RFC 5158 RFC 5661 RFC 5662 RFC 7477 RFC 7530 RFC 7553 RFC 7863 RFC 8111 RFC 8244 RFC 8499 RFC 8693 RFC 8751 RFC 8881 RFC 9156 and 2 more

A message generated by a mail system to tell a sender whether a message was delivered or failed. It is often shortened to DSN.

Plain language A message generated by a mail system telling a sender whether a message was delivered or failed.

Used in RFC 1893 RFC 1894 RFC 2034 RFC 2532 RFC 2852 RFC 3459 RFC 3461 RFC 3463 RFC 3464 RFC 3886 RFC 3888 RFC 5429 RFC 6009 RFC 6522 RFC 6533 RFC 7505

Representing a new version of data as a set of differences from an older version, so only the changes need to be stored or sent.

Plain language Representing a new data version as differences from an older version so only changes need to be stored or sent.

Used in RFC 1144 RFC 2509 RFC 3229 RFC 3284

Sampling a value twice and using the difference between the two samples rather than the raw value. It is how counters, which only grow, are made meaningful.

Plain language Sampling a value twice and using the difference, rather than the raw value; this makes counters meaningful.

Used in RFC 2981 RFC 2982

The time between one event and the one before it, written in a compact form. In RTP MIDI each command's timestamp is built by adding up delta times.

Plain language The time between one event and the previous one, written in compact form.

Used in RFC 4695 RFC 6295

A link that is brought up only when there is traffic to send and may be torn down when idle. OSPF suppresses periodic Hello packets on such links to avoid keeping them up.

Plain language A link brought up only when there is traffic to send and torn down when idle.

Used in RFC 1793 RFC 3883

A subnet between a private network and the external internet, containing servers (like web and mail) that need to be accessible from outside.

Plain language A subnet between a private network and external Internet containing servers that need outside accessibility.

Used in RFC 2647 RFC 2694

Sorting arriving data to the right receiver, for example by looking at the first byte of a packet or the destination port.

Plain language Sorting arriving data to the right receiver, for example by looking at destination port.

Used in RFC 817 RFC 928 RFC 1270 RFC 1928 RFC 7983 RFC 9443

An attack that floods a network or service with traffic to prevent legitimate users from accessing it.

Plain language An attack flooding a network or service with traffic to prevent legitimate users from accessing it.

Used in RFC 1281 RFC 2350 RFC 2521 RFC 2678 RFC 3552 RFC 3837 RFC 3897 RFC 4732 RFC 5182 RFC 5327 RFC 5360 RFC 5363 RFC 5635 RFC 5694 RFC 5713 RFC 5836 RFC 5920 RFC 6045 RFC 6192 RFC 6202 RFC 6274 RFC 6324 RFC 6398 RFC 6584 and 9 more

The Distinguished Encoding Rules, a strict form of BER in which every value has exactly one possible encoding. That uniqueness is needed when bytes are signed or hashed, so CMS requires signed and authenticated attributes to use it.

Plain language Distinguished Encoding Rules; a strict form of BER where every value has exactly one possible encoding.

Used in RFC 2025 RFC 2315 RFC 2437 RFC 2503 RFC 2585 RFC 2630 RFC 2943 RFC 2984 RFC 2985 RFC 2986 RFC 3125 RFC 3274 RFC 3279 RFC 3369 RFC 3560 RFC 3641 RFC 3657 RFC 3709 RFC 3779 RFC 3852 RFC 4010 RFC 4055 RFC 4108 RFC 4134 and 59 more

A new work that is based on or includes all or part of an earlier work, such as a revised or adapted version of a document.

Plain language A new work based on or including all or part of an earlier work, such as a revised or adapted version.

Used in RFC 3978 RFC 5378

An expert selected by IANA to review specifications for IANA registries and make registration decisions without requiring a full RFC.

Plain language An expert selected by IANA to review specifications for IANA registries and make registration decisions.

Used in RFC 3864 RFC 5226 RFC 5727 RFC 6117 RFC 6118 RFC 7451 RFC 7595 RFC 8126 RFC 8726 RFC 9748

The one provider edge chosen to handle forwarding for a given segment or VLAN so that traffic is not duplicated or looped.

Plain language The one provider edge chosen to handle forwarding for a given segment or VLAN so traffic is not duplicated or looped.

Used in RFC 5015 RFC 7432 RFC 7734 RFC 7781 RFC 8584 RFC 9722 RFC 9784 RFC 9785 RFC 9786 RFC 9856

The single RBridge elected on each link to choose the Designated VLAN and to appoint which RBridge forwards each VLAN's traffic.

Plain language The single RBridge elected on each link to choose the Designated VLAN and appoint which RBridge forwards each VLAN's traffic.

Used in RFC 6325 RFC 6327 RFC 6439 RFC 7177 RFC 8139

On a multi-access network such as Ethernet, the router elected to form adjacencies with all others and originate the network's Network-LSA, so not every pair of routers needs to synchronize.

Plain language On a multi-access network such as Ethernet, the router elected to form adjacencies with all others and originate the network's Network-LSA.

Used in RFC 1075 RFC 1131 RFC 1195 RFC 1245 RFC 1246 RFC 1247 RFC 1252 RFC 1583 RFC 1584 RFC 1586 RFC 1629 RFC 1793 RFC 2117 RFC 2178 RFC 2189 RFC 2328 RFC 2362 RFC 2642 RFC 2740 RFC 2934 RFC 3623 RFC 3630 RFC 4061 RFC 4062 and 42 more

A signed payload that is not carried inside the signature object and is sent or stored separately. The signature still covers it, so the verifier needs both pieces.

Plain language A signed payload not carried inside the signature object, sent or stored separately; the signature still covers it.

Used in RFC 7797 RFC 8055

A digital signature stored in a separate file from the data it signs. The original file stays unchanged, so programs that read it are unaffected.

Plain language A digital signature stored in a separate file from the data it signs, leaving the original file unchanged.

Used in RFC 2015 RFC 2633 RFC 3156 RFC 3851 RFC 4880 RFC 5485 RFC 5655 RFC 5751 RFC 8358

The period without receiving expected liveness packets after which a session is declared to have failed. The receiver works it out from the agreed interval and a multiplier.

Plain language The period without receiving expected liveness packets after which a session is declared to have failed.

Used in RFC 5880 RFC 8562

A service a network can offer to DetNet flows, giving them extremely low packet loss rates and an assured maximum end-to-end delivery latency.

Plain language A service offering extremely low packet loss rates and an assured maximum end-to-end delivery latency.

Used in RFC 8557 RFC 8578 RFC 8939 RFC 8964 RFC 9016 RFC 9024 RFC 9025 RFC 9034 RFC 9055 RFC 9056 RFC 9550 RFC 9634

Deterministic Networking: carrying real-time unicast or multicast flows with extremely low packet loss and an assured maximum end-to-end delivery latency.

Plain language Deterministic Networking; carrying real-time unicast or multicast flows with extremely low packet loss and assured latency.

Used in RFC 8655 RFC 8939 RFC 9633

Identifying a device, or its software type and version, from small characteristic differences such as which protocol options it sends and in what order. It works even when no explicit identifier is present.

Plain language Identifying a device or its software type and version from characteristic differences such as protocol options sent.

Used in RFC 6462 RFC 7844

The switch, router or other piece of equipment being measured in a benchmark. It is usually abbreviated DUT.

Plain language The switch, router, or equipment being measured in a benchmark.

Used in RFC 2544 RFC 3918 RFC 4061 RFC 4062 RFC 4098 RFC 6201 RFC 6412 RFC 7501 RFC 7502 RFC 8219 RFC 8238 RFC 8239 RFC 8456 RFC 9004 RFC 9411

The Dynamic Host Configuration Protocol. It leases IP addresses to clients and delivers options such as gateway and DNS servers. It grew out of BOOTP and is what most devices use today.

Plain language The Dynamic Host Configuration Protocol; it leases IP addresses to clients and delivers options such as gateway and DNS servers.

Used in RFC 903 RFC 950 RFC 951 RFC 1048 RFC 1084 RFC 1350 RFC 1395 RFC 1531 RFC 1533 RFC 1534 RFC 1541 RFC 1542 RFC 1628 RFC 1678 RFC 1787 RFC 1900 RFC 1931 RFC 2008 RFC 2071 RFC 2072 RFC 2131 RFC 2132 RFC 2136 RFC 2165 and 300 more

The record a DHCP server keeps that ties an address or delegated prefix to a client, together with related data such as lease times.

Plain language A record a DHCP server keeps tying an address or delegated prefix to a client, with related data such as lease times.

Used in RFC 1531 RFC 7653 RFC 7724

A tagged item of configuration carried in the variable-length options field of a DHCP message, such as the subnet mask, the router list or the lease time. Each option has a numeric code that says what it is.

Plain language A tagged item of configuration in the variable-length options field of a DHCP message, such as subnet mask or lease time.

Used in RFC 1048 RFC 1497 RFC 1533 RFC 1534 RFC 1541 RFC 2131 RFC 2132 RFC 2165 RFC 2241 RFC 2242 RFC 2489 RFC 2563 RFC 2610 RFC 2939 RFC 3004 RFC 3011 RFC 3046 RFC 3118 RFC 3203 RFC 3315 RFC 3319 RFC 3361 RFC 3396 RFC 3397 and 109 more

The Dynamic Host Configuration Protocol for IPv6. It allows IPv6 hosts to obtain network configuration information and addresses from servers on the network.

Plain language The Dynamic Host Configuration Protocol for IPv6; it allows IPv6 hosts to obtain network configuration and addresses.

Used in RFC 2462 RFC 2794 RFC 3646 RFC 4057 RFC 4704 RFC 4818 RFC 4852 RFC 4968 RFC 5007 RFC 5375 RFC 5558 RFC 5720 RFC 5986 RFC 6225 RFC 6334 RFC 6422 RFC 6603 RFC 7051 RFC 7083 RFC 7084 RFC 7227 RFC 7283 RFC 7341 RFC 7421 and 9 more

A mechanism in DHCPv6 that allows a server to delegate entire IPv6 address prefixes to clients, who can then use these prefixes for their own addressing or extend them to networks they manage.

Plain language A DHCPv6 mechanism allowing a server to delegate entire IPv6 address prefixes to clients for their own addressing.

Used in RFC 4029 RFC 4818 RFC 7010 RFC 7227 RFC 9663

A AAA protocol defined in RFC 3588. Clients such as network access servers send it requests, and a Diameter server answers them.

Plain language A AAA protocol defined in RFC 3588 where clients send requests and a Diameter server answers them.

Used in RFC 2903 RFC 3127 RFC 3539 RFC 3588 RFC 3955 RFC 4006 RFC 4072 RFC 4097 RFC 4282 RFC 4740 RFC 4818 RFC 5169 RFC 5176 RFC 5193 RFC 5281 RFC 5447 RFC 5580 RFC 5777 RFC 5778 RFC 5779 RFC 5836 RFC 5866 RFC 6159 RFC 6733 and 15 more

An attack that guesses a password by trying a long list of likely candidates and checking each against captured or stored data.

Plain language An attack guessing a password by trying a long list of likely candidates against captured or stored data.

Used in RFC 2945 RFC 3767 RFC 4279 RFC 4851 RFC 5018 RFC 5281 RFC 5433 RFC 5802 RFC 5931 RFC 6124 RFC 6617 RFC 7664 RFC 8125 RFC 8146 RFC 9588

The basic unit of DV stream data, exactly 80 bytes in size, containing either video, audio, timing, or metadata information.

Plain language The basic unit of DV stream data, exactly 80 bytes, containing video, audio, timing, or metadata information.

Used in RFC 3189 RFC 6469

A QoS architecture (DiffServ) in which routers treat packets based on a service code point marked in the packet header, without maintaining per-flow state.

Plain language A QoS architecture where routers treat packets based on a service code point marked in the header.

Used in RFC 2430 RFC 2638 RFC 2698 RFC 2990 RFC 3289 RFC 3292 RFC 3308 RFC 4115 RFC 4124 RFC 4190 RFC 4594 RFC 5594 RFC 5882 RFC 8257 RFC 9894

A way for two parties to arrive at the same shared secret over a public channel, so that an eavesdropper who sees everything cannot work it out.

Plain language A way for two parties to arrive at the same shared secret over a public channel.

Used in RFC 1057 RFC 1750 RFC 2025 RFC 2094 RFC 2228 RFC 2356 RFC 2409 RFC 2412 RFC 2522 RFC 2523 RFC 2539 RFC 2630 RFC 2631 RFC 2636 RFC 2660 RFC 2695 RFC 2785 RFC 2786 RFC 2847 RFC 2875 RFC 2930 RFC 2945 RFC 2946 RFC 3268 and 140 more

Differentiated Services, a QoS architecture that marks packets with priority levels and handles them according to their marking, without per-flow reservations.

Plain language Differentiated Services; a QoS architecture marking packets with priority levels for handling without per-flow reservations.

Used in RFC 2475 RFC 2638 RFC 2997 RFC 3247 RFC 3272 RFC 3317 RFC 3726 RFC 4128 RFC 4182 RFC 4594 RFC 5127 RFC 5129 RFC 5670 RFC 5777 RFC 5975 RFC 6660 RFC 6661 RFC 6662 RFC 8100 RFC 9064 RFC 9332 RFC 9894 RFC 9895 RFC 9956

An authentication method where a client proves knowledge of a password by hashing the password along with a server-provided nonce, avoiding transmission of the password itself.

Plain language An authentication method where a client proves password knowledge by hashing the password with a server-provided nonce.

Used in RFC 2617 RFC 2829 RFC 2831 RFC 3325 RFC 3665 RFC 3744 RFC 3891 RFC 3911 RFC 4245 RFC 4474 RFC 4590 RFC 4643 RFC 7616

A dialing plan stored in a gateway that lists digit patterns to match. It lets the gateway report a complete dialed number at once instead of reporting every digit separately.

Plain language A dialing plan stored in a gateway listing digit patterns to match, letting the gateway report a complete dialed number at once.

Used in RFC 3015 RFC 3435

Encrypted content packaged together with the content-encryption key, itself encrypted for one recipient. Opening it means decrypting the key first and then the content.

Plain language Encrypted content packaged with the content-encryption key, itself encrypted for one recipient.

Used in RFC 2315 RFC 2630 RFC 3369

A value computed from some data with a private key, which anyone holding the matching public key can check. A valid signature shows the data has not changed since signing and that the holder of the private key produced it.

Plain language A value computed from data with a private key, which anyone holding the matching public key can verify.

Used in RFC 1113 RFC 1114 RFC 1186 RFC 1319 RFC 1320 RFC 1321 RFC 1421 RFC 1422 RFC 1423 RFC 1424 RFC 1505 RFC 1507 RFC 1704 RFC 1805 RFC 1824 RFC 1826 RFC 1847 RFC 1848 RFC 1898 RFC 1984 RFC 1991 RFC 2015 RFC 2025 RFC 2065 and 452 more

A graph search algorithm that finds the shortest path between a source and all other nodes by iteratively visiting the closest unvisited node and updating distance estimates.

Plain language A graph search algorithm finding the shortest path between a source and all other nodes.

Used in RFC 1245 RFC 3906 RFC 6987 RFC 8218

A way of moving a data payload straight into a pre-arranged region of the receiver's memory instead of passing it through intermediate message buffers.

Plain language A way of moving a data payload directly into a pre-arranged region of the receiver's memory.

Used in RFC 3347 RFC 5041 RFC 5043 RFC 5044 RFC 6581 RFC 8267

A routing structure with no loops where edges point toward a root, used by RPL to organize LLN traffic flow.

Plain language Directed Acyclic Graph; a routing structure with no loops where edges point toward a root, used by RPL for LLN traffic flow.

Used in RFC 6551 RFC 6687 RFC 7102

A server that stands between client software and the directory servers that hold the data. It answers a query from an index of what its providers hold, and points the client at the providers likely to have a matching answer.

Plain language A middle server. It takes a search from a client, works out which providers probably have the answer, and sends the client to them.

Used in RFC 2967 RFC 2968

An SLP component that automatically gathers service advertisements from Service Agents so that User Agents can query them in one place.

Plain language An SLP component gathering service advertisements from Service Agents so User Agents can query them in one place.

Used in RFC 1107 RFC 1202 RFC 1249 RFC 2614 RFC 3082 RFC 3528 RFC 3822 RFC 3832 RFC 4018

A record in an LDAP directory representing a person, organization, or resource, stored as a set of attributes with values.

Plain language A record in an LDAP directory representing a person, organization, or resource, stored as a set of attributes.

Used in RFC 1274 RFC 2255 RFC 2256 RFC 2596 RFC 3671 RFC 3703 RFC 4681

The hierarchy of entries in an X.500 or LDAP directory. Each entry is found by a name made of its position in the tree.

Plain language The hierarchy of entries in an X.500 or LDAP directory, with each entry found by its position in the tree.

Used in RFC 1255 RFC 1274 RFC 1279 RFC 1430 RFC 1588 RFC 1617 RFC 1803 RFC 1943 RFC 2164 RFC 2251 RFC 2293 RFC 2654 RFC 3672 RFC 3703 RFC 3829 RFC 4104 RFC 4512

A service that maintains information about people, resources, or entities and allows clients to query and retrieve that information using a defined protocol.

Plain language A service maintaining information about people, resources, or entities and allowing clients to query it.

Used in RFC 1107 RFC 1202 RFC 1249 RFC 1277 RFC 1309 RFC 1558 RFC 1616 RFC 1727 RFC 1913 RFC 1914 RFC 2256 RFC 2345 RFC 2798 RFC 2968 RFC 2969 RFC 2970 RFC 3377 RFC 3712 RFC 4157 RFC 7067

A server that holds a portion of the directory tree and responds to directory queries (binds) from clients.

Plain language A server holding a portion of the directory tree and responding to queries from clients.

Used in RFC 1292 RFC 1309 RFC 1430 RFC 1567 RFC 1588 RFC 2116

An X.500 client component that allows users or applications to query and interact with Directory System Agents.

Plain language An X.500 client component allowing users or applications to query and interact with Directory System Agents.

Used in RFC 1107 RFC 1202 RFC 1292 RFC 1309 RFC 1430 RFC 1588 RFC 1803 RFC 2116

A client application that users interact with to search and retrieve information from an X.500 directory.

Plain language Directory User Agent; a client application letting users search and retrieve information from an X.500 directory.

Used in RFC 1274 RFC 1491 RFC 1632 RFC 2307

A packet that arrived within the receiver's time window but was thrown away before it could be played, because it arrived too early, arrived too late, or was a duplicate. A packet dropped later by a decoder is not discarded.

Plain language A packet that got to the receiver safely but was then thrown away instead of being played.

Used in RFC 7002 RFC 7003

A technique where a sender reduces or stops sending packets during silence. The receiver fills the gaps, which saves bandwidth.

Plain language A technique where a sender reduces or stops sending during silence, saving bandwidth.

Used in RFC 3389 RFC 4348 RFC 4788 RFC 4867 RFC 6884 RFC 7587

A named group that limits which entities are allowed to discover each other within a larger scope. An entity can belong to several domains.

Plain language A named group limiting which entities are allowed to discover each other within a larger scope.

Used in RFC 3822 RFC 4171 RFC 4174 RFC 4939

Cryptographic operations based on the difficulty of computing logarithms in finite groups. In these algorithms, exponentiation is performed modulo a large prime number (mod q).

Plain language Cryptographic operations based on the difficulty of computing logarithms in finite groups.

Used in RFC 2539 RFC 3766 RFC 7664 RFC 8121 RFC 8235 RFC 9496 RFC 9497

A way of writing a logical condition as an OR of AND lists. It is true when every item in at least one of the AND lists is true.

Plain language A way of writing a logical condition as an OR of AND lists, true when every item in at least one AND list is true.

Used in RFC 2533 RFC 3060

A computer with no local disk that loads its operating system over the network at boot. It must first learn its own network address from outside.

Plain language A computer with no local disk that loads its operating system over the network at boot.

Used in RFC 903 RFC 906 RFC 917 RFC 950 RFC 951 RFC 1123 RFC 1350 RFC 1931 RFC 2603 RFC 4173

A routing approach in which each router tells its neighbours only the distance to every destination and picks the neighbour giving the smallest total. RIP is the classic example.

Plain language A routing approach where each router tells neighbors only the distance to every destination.

Used in RFC 823 RFC 891 RFC 975 RFC 1058 RFC 1075 RFC 1322 RFC 1387 RFC 1388 RFC 1476 RFC 1582 RFC 1634 RFC 1722 RFC 1723 RFC 1724 RFC 1762 RFC 1774 RFC 1923 RFC 2080 RFC 2081 RFC 2091 RFC 2174 RFC 2328 RFC 2453 RFC 3561 and 17 more

An X.500 name that identifies something through a hierarchy of parts. In RFC 2872 it carries the application locator.

Plain language An X.500 name identifying something through a hierarchy of parts, such as country, state, and organization.

Used in RFC 1107 RFC 1114 RFC 1202 RFC 1214 RFC 1249 RFC 1255 RFC 1309 RFC 1373 RFC 1430 RFC 1487 RFC 1567 RFC 1588 RFC 1779 RFC 1781 RFC 1804 RFC 1823 RFC 1836 RFC 1837 RFC 1959 RFC 2247 RFC 2251 RFC 2252 RFC 2253 RFC 2254 and 32 more

A data structure distributed across a network of peers that allows any peer to store and retrieve data by key without a central server.

Plain language A data structure distributed across network peers allowing any peer to store and retrieve data by key.

Used in RFC 4981 RFC 5694 RFC 5765 RFC 6029 RFC 6537 RFC 6940 RFC 7019 RFC 7374 RFC 7851 RFC 7890

A design in which a device does the first signal processing of speech and sends a compact representation to a server. The server then finishes the recognition.

Plain language A design where a device does the first speech signal processing and a server finishes the recognition.

Used in RFC 3557 RFC 4060

A loop-free tree of links over which a network sends multi-destination traffic, so that every interested switch receives a copy exactly once.

Plain language A loop-free tree of links over which a network sends multi-destination traffic, reaching each interested switch exactly once.

Used in RFC 2201 RFC 6325 RFC 7172 RFC 7968 RFC 8361 RFC 8377

A change to the ultimate destination endpoint of a SIP request that was not caused by a routing decision. It is also called a deflection or a redirection, and the entity that makes it is the divertor.

Plain language A change of where a call is going that is not just normal routing.

Used in RFC 5806 RFC 7683

DomainKeys Identified Mail; the successor to DomainKeys, defined in RFC 4871, with improved design and wider deployment.

Plain language DomainKeys Identified Mail; the successor to DomainKeys with improved design and wider deployment.

Used in RFC 4686 RFC 4870 RFC 4871 RFC 5451 RFC 5518 RFC 5585 RFC 5703 RFC 6008 RFC 6449 RFC 6541 RFC 6651 RFC 7001 RFC 7070 RFC 7489 RFC 7960 RFC 8058 RFC 8301 RFC 8463 RFC 8601 RFC 8617 RFC 9989 RFC 9990 RFC 9991

A label chosen by a signing domain that picks one of its DKIM keys. It appears in the s= tag of a signature, and the public key is published at selector._domainkey.domain. Selectors let a domain run several keys and rotate them without interruption.

Plain language A label chosen by a signing domain picking one of its DKIM keys, appearing in the s= tag of a signature.

Used in RFC 4686 RFC 4871 RFC 5451 RFC 5585 RFC 5617 RFC 5672 RFC 5863 RFC 6376 RFC 6591 RFC 6651 RFC 7073 RFC 8301 RFC 8463 RFC 8616 RFC 8617 RFC 9091 RFC 9991

A cryptographic signature added to an email message by the sending domain to prove the message was sent by that domain and to prevent tampering during transport.

Used in RFC 4871 RFC 8823

A Data Link Connection Identifier is the number that identifies a virtual circuit at a Frame Relay interface. It usually has only local meaning.

Plain language Data Link Connection Identifier; the number identifying a virtual circuit at a Frame Relay interface.

Used in RFC 1294 RFC 1490 RFC 1586 RFC 1973 RFC 2115 RFC 2390 RFC 2427 RFC 2590 RFC 3034 RFC 4233 RFC 4591

The Dynamic Link Exchange Protocol lets a radio or other modem tell its attached router about the state of a link. It is defined in RFC 8175 and can be extended.

Plain language The Dynamic Link Exchange Protocol lets a radio or modem tell its attached router about link state.

Used in RFC 8175 RFC 8629 RFC 8651 RFC 9892 RFC 9893 RFC 9894 RFC 9895

Domain-based Message Authentication, Reporting, and Conformance, a mechanism that lets a domain owner publish a policy for mail that uses its domain and request reports about it.

Plain language Domain-based Message Authentication, Reporting, and Conformance; lets a domain owner publish a mail policy and request reports.

Used in RFC 5451 RFC 7489 RFC 7960 RFC 8601 RFC 8617 RFC 9989 RFC 9990 RFC 9991

A DNS record that redirects a whole subtree of the namespace to another name. Names below the owner name are answered as if they were under the target.

Used in RFC 2672 RFC 4592 RFC 6672 RFC 7535

The Domain Name System, which maps names such as example.com to data such as IP addresses. Domain labels in the DNS are traditionally limited to 63 characters.

Plain language The Domain Name System, which maps names such as example.com to data such as IP addresses.

Used in RFC 87 RFC 616 RFC 620 RFC 623 RFC 805 RFC 810 RFC 814 RFC 819 RFC 830 RFC 849 RFC 881 RFC 882 RFC 883 RFC 887 RFC 897 RFC 899 RFC 920 RFC 921 RFC 952 RFC 973 RFC 974 RFC 1001 RFC 1011 RFC 1026 and 644 more

Sending ordinary DNS messages inside a TLS-protected TCP connection, by default to port 853, so that the queries and answers cannot be read on the network path.

Plain language Sending ordinary DNS messages inside a TLS-protected TCP connection so queries and answers cannot be read on the network path.

Used in RFC 7766 RFC 7858 RFC 8094 RFC 8310 RFC 8467 RFC 8490 RFC 8765 RFC 8781 RFC 8932 RFC 9076 RFC 9103 RFC 9210 RFC 9250 RFC 9445 RFC 9461 RFC 9462 RFC 9463 RFC 9464 RFC 9527 RFC 9539 RFC 9606 RFC 9726 RFC 9852 RFC 9953

The list of DNS suffix domain names used by a host when it performs a DNS query for a short, unqualified domain name.

Plain language The list of endings a host tries when you give a name without its full domain.

Used in RFC 6106 RFC 8106

A kind of DNS record that holds free-form text for a name. It is used for many things, including publishing DKIM public keys, where the text is a list of tag=value pairs.

Plain language A DNS record holding free-form text for a name, used for many things including publishing DKIM public keys.

Used in RFC 1183 RFC 1383 RFC 1464 RFC 4408 RFC 4871 RFC 5451 RFC 5507 RFC 5518 RFC 5585 RFC 5617 RFC 5782 RFC 5863 RFC 6376 RFC 6591 RFC 6651 RFC 6686 RFC 6762 RFC 6763 RFC 6764 RFC 7208 RFC 7489 RFC 7808 RFC 8301 RFC 8460 and 15 more

A DNS-based list of IP addresses or domain names with good reputation, used to identify legitimate email senders. The opposite of a blocklist.

Plain language DNS Whitelist; a DNS-based list of IP addresses or domain names with good reputation, identifying legitimate email senders.

Used in RFC 6471 RFC 8904

A mechanism that synthesizes AAAA records from A records, so an IPv6-only host gets an IPv6 address to use for an IPv4-only name.

Plain language A mechanism synthesizing AAAA records from A records so an IPv6-only host gets an IPv6 address for an IPv4-only name.

Used in RFC 6146 RFC 6342 RFC 6889 RFC 7050 RFC 7051 RFC 7269 RFC 8219 RFC 8305 RFC 8781 RFC 8880

The DNSSEC record that publishes a zone's public key so resolvers can verify signatures made with the matching private key.

Plain language The DNSSEC record publishing a zone's public key so resolvers can verify signatures made with the matching private key.

Used in RFC 2065 RFC 3110 RFC 3445 RFC 3755 RFC 3757 RFC 4033 RFC 4034 RFC 4035 RFC 4310 RFC 4398 RFC 4470 RFC 4509 RFC 4986 RFC 5011 RFC 5585 RFC 5702 RFC 5910 RFC 5933 RFC 6605 RFC 6725 RFC 6781 RFC 6840 RFC 6944 RFC 6975 and 21 more

The DNS Security Extensions: new record types and protocol changes that add digital signatures to DNS data, giving data origin authentication and integrity (but not confidentiality).

Plain language DNS Security Extensions; new record types and protocol changes adding digital signatures to DNS data.

Used in RFC 2065 RFC 2137 RFC 2146 RFC 2181 RFC 2230 RFC 2308 RFC 2316 RFC 2535 RFC 2536 RFC 2539 RFC 2540 RFC 2541 RFC 2672 RFC 2673 RFC 2826 RFC 2870 RFC 2874 RFC 2916 RFC 2931 RFC 3007 RFC 3008 RFC 3090 RFC 3110 RFC 3130 and 229 more

DNSSEC OK. A flag in the EDNS OPT pseudo-record of a query. When set, it tells the server the client understands DNSSEC and wants RRSIG, NSEC and DS records in the response.

Plain language DNSSEC OK; a flag in the EDNS OPT pseudo-record telling the server the client understands DNSSEC.

Used in RFC 4035

Data Over Cable Service Interface Specifications, the set of specifications that define how cable modems and the head-end equipment carry data over a cable television network.

Plain language Data Over Cable Service Interface Specifications; the specifications defining how cable modems carry data over cable networks.

Used in RFC 3256 RFC 4131 RFC 4323 RFC 4546 RFC 4547 RFC 4639 RFC 5594 RFC 5632 RFC 8034

An experienced community member designated to shepherd a document through the final stages of review and into the IESG, ensuring quality and completeness.

Plain language An experienced community member designated to shepherd a document through final review into the IESG.

Used in RFC 4858 RFC 6175

A set of rules that defines the structure and syntax of valid XML documents, including which elements are allowed, their attributes, and how they can be nested.

Plain language Document Type Definition; a set of rules defining the structure and syntax of valid XML documents.

Used in RFC 3017 RFC 3504 RFC 4911

A Destination-Oriented Directed Acyclic Graph: a set of nodes and one-way links with no cycles, in which every path leads toward a single root.

Plain language Destination-Oriented Directed Acyclic Graph; a set of nodes and one-way links with no cycles, where every path leads toward a single root.

Used in RFC 6550 RFC 6551 RFC 6552 RFC 8036 RFC 8138 RFC 9008 RFC 9010 RFC 9035 RFC 9854 RFC 9866 RFC 9914

A protocol that carries each DNS query and response as one HTTP exchange over an https URI, so TLS protects it. Defined in RFC 8484.

Plain language DNS over HTTPS; a protocol carrying DNS queries and responses as HTTP exchanges over HTTPS.

Used in RFC 8484 RFC 8932 RFC 9076 RFC 9230 RFC 9445 RFC 9458 RFC 9461 RFC 9462 RFC 9463 RFC 9464 RFC 9540 RFC 9606 RFC 9726 RFC 9761 RFC 9953

A unique identifier assigned to an AppleTalk network to distinguish it from other networks on an AURP tunnel.

Plain language A unique identifier assigned to an AppleTalk network to distinguish it from others on an AURP tunnel.

Used in RFC 1504 RFC 2528

The tree of names used by DNS. Each node has a label, and a domain name is the labels from a node up to the root, separated by dots.

Plain language The tree of names used by DNS, where a domain name is the labels from a node up to the root, separated by dots.

Used in RFC 799 RFC 805 RFC 819 RFC 830 RFC 882 RFC 897 RFC 920 RFC 921 RFC 952 RFC 974 RFC 976 RFC 1032 RFC 1034 RFC 1118 RFC 1124 RFC 1178 RFC 1206 RFC 1279 RFC 1394 RFC 1480 RFC 1535 RFC 1591 RFC 1706 RFC 1714 and 62 more

A specification that fills in algorithm choices, naming schemes, and payload formats for ISAKMP in a particular context, such as the Internet IP Security DOI for IPsec.

Plain language A specification filling in algorithm choices and payload formats for ISAKMP in a particular context.

Used in RFC 2408 RFC 5570

The second major part of an NSAP address, allocated and interpreted by the authority identified by the IDI; contains the actual address within a domain.

Plain language Domain-Specific Part; the second major part of an NSAP address, containing the actual address within a domain.

Used in RFC 941 RFC 1277 RFC 1564

A flag in the IP header. When it is set, a router must not split the datagram; if the datagram is too big for the next link the router throws it away and reports an error instead.

Plain language Don't Fragment (DF) bit; a flag in the IP header that, when set, prevents a router from splitting the datagram.

Used in RFC 791 RFC 792 RFC 1191 RFC 2923 RFC 4149 RFC 4213 RFC 4413 RFC 4459 RFC 4787 RFC 4821 RFC 6145 RFC 6864 RFC 7915 RFC 9869

The four-message DHCP exchange of Discover, Offer, Request and Acknowledge by which a client obtains an address and lease.

Plain language The four-message DHCP exchange of Discover, Offer, Request, and Acknowledge by which a client obtains an address.

Used in RFC 2131

A power-saving state where a mobile host is no longer listening for packets but is still reachable by paging through a specialized protocol or link-layer mechanism.

Plain language A power-saving state where a mobile host is no longer listening but is still reachable through specialized protocols.

Used in RFC 3154 RFC 4968 RFC 5383

The path segments . (stay here) and .. (go up one level). They are only meaningful in relative references and are removed during reference resolution.

Plain language The path segments . (stay here) and .. (go up one level); they are only meaningful in relative references.

Used in RFC 1630 RFC 3986

A way to send multi-line text that ends with a line holding a single dot. Any data line that begins with a dot gets an extra dot added by the sender, and the receiver removes it.

Plain language A way to send multi-line text ending with a dot, where any line starting with a dot gets an extra dot added.

Used in RFC 3887 RFC 3977

DDoS Open Threat Signaling, an architecture in which a DOTS client asks an upstream DOTS server to mitigate a distributed denial-of-service attack. It uses a signal channel and a data channel.

Plain language DDoS Open Threat Signaling; an architecture where a DOTS client asks an upstream DOTS server to mitigate a DDoS attack.

Used in RFC 8783 RFC 8903 RFC 9066 RFC 9132 RFC 9244 RFC 9362

A way of writing a 32-bit IPv4 address as four 8-bit values in decimal, separated by periods, such as 10.1.0.52.

Plain language A way of writing a 32-bit IPv4 address as four 8-bit values in decimal, separated by periods.

Used in RFC 1117 RFC 1166

An active attack that alters negotiation messages so that both sides end up using the weakest security option they both support.

Plain language An active attack altering negotiation messages so both sides use the weakest security option they both support.

Used in RFC 4178 RFC 4422 RFC 4509 RFC 4991 RFC 5021 RFC 6678 RFC 7401 RFC 7457 RFC 7672 RFC 7696 RFC 8164 RFC 8461 RFC 8996 RFC 9368 RFC 9848

A maturity level in RFC 2026 requiring two independent, interoperable implementations. RFC 6410 later removed it as a step for new advancement.

Plain language A maturity level in RFC 2026 requiring two independent, interoperable implementations.

Used in RFC 1100 RFC 1140 RFC 1160 RFC 1264 RFC 1266 RFC 1280 RFC 1410 RFC 1500 RFC 1540 RFC 1600 RFC 1602 RFC 1610 RFC 1773 RFC 1780 RFC 1796 RFC 1880 RFC 2000 RFC 2026 RFC 2200 RFC 2438 RFC 2499 RFC 2600 RFC 2700 RFC 2800 and 12 more

The name for a HHIT when it is used as an Unmanned Aircraft System Remote ID. It identifies a drone and points to the registry that holds its record.

Plain language The name for a HHIT when used as an Unmanned Aircraft System Remote ID, identifying a drone.

Used in RFC 9374 RFC 9575 RFC 9886

A contiguous part of the Internet where a consistent set of differentiated services policies is administered together. Its edge is the DS boundary, where packets are classified and marked.

Plain language A contiguous part of the Internet where a consistent set of differentiated services policies is administered together.

Used in RFC 2474 RFC 2983 RFC 3086 RFC 3246

The 8-bit IP header octet (the IPv4 TOS octet or IPv6 Traffic Class octet) when read as defined in RFC 2474: a 6-bit DSCP followed by 2 currently unused bits.

Plain language The 8-bit IP header octet when read as a 6-bit DSCP followed by 2 unused bits.

Used in RFC 2474 RFC 2475 RFC 2780 RFC 2836 RFC 3086 RFC 5696 RFC 9892

Delegation Signer. A record in a parent zone, at the delegation point, that holds a hash of a child zone's DNSKEY and so links the parent's signatures to the child's keys.

Plain language Delegation Signer; a record at the delegation point holding a hash of a child zone's DNSKEY.

Used in RFC 3658 RFC 3755 RFC 4033 RFC 4034 RFC 4035 RFC 4509 RFC 4955 RFC 4956 RFC 4986 RFC 5011 RFC 5074 RFC 5155 RFC 5910 RFC 5933 RFC 6605 RFC 6781 RFC 6840 RFC 6841 RFC 6975 RFC 7344 RFC 7477 RFC 7583 RFC 7646 RFC 8027 and 18 more

Directory Service Agent; a server implementing the X.500 directory protocol.

Plain language Directory Service Agent; a server implementing the X.500 directory protocol.

Used in RFC 1274 RFC 1491 RFC 1564 RFC 1632 RFC 1803 RFC 2120 RFC 2459 RFC 2792 RFC 5754 RFC 7427 RFC 9500

Differentiated Services Codepoint: the 6-bit part of the DS field. Routers match the whole value, usually through a table, to pick a per-hop behavior. There are 64 possible values.

Plain language Differentiated Services Codepoint; the 6-bit part of the DS field determining which per-hop behavior applies.

Used in RFC 1349 RFC 2474 RFC 2475 RFC 2584 RFC 2597 RFC 2697 RFC 2698 RFC 2724 RFC 2836 RFC 2873 RFC 2983 RFC 2990 RFC 2996 RFC 2997 RFC 2998 RFC 3086 RFC 3140 RFC 3168 RFC 3175 RFC 3246 RFC 3270 RFC 3287 RFC 3289 RFC 3290 and 113 more

Digital Subscriber Line Access Multiplexer, the device at the central office that terminates many DSL lines. One such device can be managed by a single SNMP agent.

Plain language Digital Subscriber Line Access Multiplexer; the device at the central office terminating many DSL lines.

Used in RFC 4679 RFC 4706 RFC 5713 RFC 5851 RFC 6320

Datagram Transport Layer Security, a version of TLS designed to protect datagram traffic such as UDP packets.

Plain language Datagram Transport Layer Security; a version of TLS designed to protect datagram traffic such as UDP packets.

Used in RFC 4347 RFC 5238 RFC 5405 RFC 5415 RFC 5479 RFC 5763 RFC 5764 RFC 5953 RFC 6012 RFC 6083 RFC 6084 RFC 6353 RFC 6655 RFC 7011 RFC 7027 RFC 7247 RFC 7252 RFC 7345 RFC 7350 RFC 7366 RFC 7397 RFC 7510 RFC 7585 RFC 7879 and 37 more

Dual-tone multi-frequency signaling, the tones a phone keypad makes when a key is pressed. MSML can detect, collect and generate these digits.

Plain language Dual-tone multi-frequency signaling; the tones a phone keypad makes when a key is pressed.

Used in RFC 1789 RFC 2806 RFC 2833 RFC 2846 RFC 3372 RFC 3660 RFC 4730 RFC 4733 RFC 4734 RFC 5022 RFC 5552 RFC 5707 RFC 6231 RFC 6787 RFC 7195 RFC 7478

The protocol data unit in Delay-Tolerant Networking, containing a primary block, optional extension blocks including PHIB, and a payload.

Plain language The protocol data unit in Delay-Tolerant Networking, containing a primary block, optional extension blocks, and a payload.

Used in RFC 6258 RFC 6259

A network node or service that supports both IPv4 and IPv6 simultaneously.

Plain language A network node or service supporting both IPv4 and IPv6 simultaneously.

Used in RFC 2893 RFC 3053 RFC 3089 RFC 3338 RFC 3750 RFC 3795 RFC 3974 RFC 4029 RFC 4038 RFC 4057 RFC 4213 RFC 4472 RFC 4477 RFC 4554 RFC 4852 RFC 4977 RFC 5454 RFC 5461 RFC 6036 RFC 6127 RFC 6180 RFC 6312 RFC 6333 RFC 6342 and 17 more

A way to give customers IPv4 connectivity across an IPv6-only provider network, using an IPv4-in-IPv6 tunnel and a carrier-grade NAT.

Plain language Dual-Stack Lite; a way to give IPv4 connectivity across an IPv6-only provider network.

Used in RFC 6334 RFC 6908 RFC 7084 RFC 7393 RFC 7596 RFC 7870 RFC 8114

DHCPv6 Unique Identifier. A unique identifier assigned to each DHCPv6 client to distinguish it from other clients on the network.

Plain language DHCPv6 Unique Identifier; a unique identifier assigned to each DHCPv6 client.

Used in RFC 3315 RFC 4361 RFC 4477 RFC 4701 RFC 5460 RFC 6155 RFC 7824 RFC 7844 RFC 7943 RFC 8371 RFC 8415 RFC 9243 RFC 9915

An acknowledgment that repeats the same cumulative sequence number as an earlier one. A TCP receiver sends one whenever a segment arrives out of order.

Plain language An acknowledgment repeating the same cumulative sequence number as an earlier one.

Used in RFC 2416 RFC 2757 RFC 2883 RFC 3042 RFC 3465 RFC 4653 RFC 5681 RFC 5690 RFC 5827 RFC 6582 RFC 6675

A check, done with a Neighbor Solicitation sent from the unspecified address, that nobody else on the link already uses an address a node wants to configure. It is specified in the autoconfiguration RFC and uses Neighbor Discovery messages.

Plain language A check that nobody else on the link already uses an address a node wants to configure.

Used in RFC 1971 RFC 2461 RFC 2462 RFC 2590 RFC 3572 RFC 3590 RFC 3627 RFC 3756 RFC 3775 RFC 3927 RFC 3971 RFC 3972 RFC 4294 RFC 4429 RFC 4489 RFC 4861 RFC 4862 RFC 4890 RFC 4941 RFC 4968 RFC 5072 RFC 5121 RFC 5568 RFC 6059 and 35 more

A mechanism in which a router records recently processed packets and silently drops later copies. SMF supports identification-based and hash-based forms of it.

Plain language A mechanism where a router records recently processed packets and silently drops later copies.

Used in RFC 6621 RFC 7985

Periodically switching off some function and leaving it on only for a certain percentage of time, the duty cycle, to save power.

Plain language Periodically switching off a function and leaving it on only for a certain percentage of time to save power.

Used in RFC 7228 RFC 8352