L

A Local Active-Active Link Protocol, such as MC-LAG or DRNI. It lets one end station treat links to several edge switches as one bundle and send traffic over all of them.

Plain language A Local Active-Active Link Protocol letting one device use links to multiple switches as one bundle.

Used in RFC 7781 RFC 7782 RFC 7783

The MPLS protocol (LDP) that routers use to tell their neighbors which labels to use for which destinations.

Plain language The MPLS protocol that routers use to tell neighbors which labels to use for destinations.

Used in RFC 3031 RFC 3034 RFC 3036 RFC 3037 RFC 3478 RFC 3479 RFC 4447 RFC 4798 RFC 5283 RFC 5561 RFC 5695 RFC 5918 RFC 5919 RFC 6389 RFC 6667 RFC 6720 RFC 7275 RFC 7358 RFC 7473 RFC 8338 RFC 9070

An MPLS router at the ingress or egress of a label-switched path, responsible for pushing or popping labels.

Plain language An MPLS router at the ingress or egress of a label-switched path that pushes or pops labels.

Used in RFC 5921 RFC 6178 RFC 7087

A set of rules, written in a standard XML format, that decides which identifier labels are allowed. It lists permitted code points, variant mappings and rules that assign each label a disposition.

Plain language A set of rules in XML format that decides which identifier labels are allowed.

Used in RFC 7940 RFC 8228

Imposition is the act of modifying or adding labels to the outgoing label stack of a packet, either by replacing the top label or by pushing new ones. The number of labels imposed is the replaced labels plus the pushed ones.

Plain language Adding or modifying labels on a packet's outgoing label stack.

Used in RFC 4798 RFC 8476 RFC 8491 RFC 8669

A sequence of 4-octet label stack entries placed after the data link header and before the network layer header. The entry with the S bit set is the bottom.

Plain language A sequence of 4-octet labels placed before the network layer header.

Used in RFC 2430 RFC 2547 RFC 2702 RFC 2917 RFC 3031 RFC 3032 RFC 3034 RFC 3035 RFC 3036 RFC 3038 RFC 3107 RFC 3209 RFC 3270 RFC 3292 RFC 3429 RFC 3443 RFC 3469 RFC 3472 RFC 3478 RFC 3811 RFC 3813 RFC 4023 RFC 4090 RFC 4110 and 164 more

A path through an MPLS network that uses labels (tags) instead of destination IP addresses to forward packets.

Plain language A path through an MPLS network using labels instead of destination addresses.

Used in RFC 2430 RFC 3031 RFC 3035 RFC 3036 RFC 3038 RFC 3063 RFC 3107 RFC 3209 RFC 3210 RFC 3212 RFC 3213 RFC 3214 RFC 3215 RFC 3270 RFC 3353 RFC 3469 RFC 3471 RFC 3472 RFC 3473 RFC 3478 RFC 3496 RFC 3812 RFC 3813 RFC 3906 and 160 more

A forwarding technique that uses short fixed-length labels instead of full address lookups, enabling faster routing in ATM or MPLS networks.

Plain language A forwarding technique using short labels instead of full address lookups.

Used in RFC 2105 RFC 2340 RFC 2682 RFC 3038 RFC 3292 RFC 4054 RFC 4139 RFC 4182 RFC 4929 RFC 5695 RFC 6383 RFC 7439

A router that supports MPLS. It looks up the label at the top of a packet's stack to find the next hop and what to do to the stack.

Plain language A router that looks up labels to find the next hop and what to do with the label stack.

Used in RFC 2702 RFC 3031 RFC 3032 RFC 3034 RFC 3035 RFC 3036 RFC 3037 RFC 3038 RFC 3063 RFC 3107 RFC 3209 RFC 3210 RFC 3212 RFC 3213 RFC 3214 RFC 3215 RFC 3270 RFC 3272 RFC 3292 RFC 3295 RFC 3429 RFC 3443 RFC 3468 RFC 3469 and 307 more

A DNS error in which a parent zone delegates authority for a child zone to a server that does not consider itself authoritative for that zone, causing resolution failures.

Plain language A DNS error where a parent delegates to a server that does not consider itself authoritative.

Used in RFC 1612 RFC 1713 RFC 1912 RFC 4074 RFC 7535

A language range is a pattern that stands for a set of language tags. It is written as subtags separated by hyphens, and it may contain the wildcard character '*' to stand for any sequence of subtags.

Plain language The way a language preference is written. It looks like a language tag, but stands for a whole group of them.

Used in RFC 3066 RFC 4647

A short ASCII label such as en that names the language of a piece of text. The format is defined in RFC 5646.

Plain language A short ASCII label such as en that names the language of text.

Used in RFC 1766 RFC 2609 RFC 3066 RFC 3282 RFC 3866 RFC 4645 RFC 4646 RFC 4647 RFC 4819 RFC 5255 RFC 5646 RFC 5890 RFC 8187 RFC 8255 RFC 8373

A final review period before an Internet-Draft is sent to the IESG for a decision to publish as an RFC. Review teams perform reviews during Last Call to catch issues before publication.

Plain language A public review period lasting at least two weeks before an Internet-Draft is sent to the IESG for publication as an RFC.

Used in RFC 1602 RFC 3683 RFC 6385 RFC 6701 RFC 7282 RFC 7735

A public announcement, lasting at least two weeks, giving anyone a final chance to comment before the IESG decides on a standards action.

Plain language A public announcement lasting at least two weeks giving a final chance to comment before IESG decision.

Used in RFC 1603 RFC 2026 RFC 2418 RFC 3683 RFC 3929 RFC 3933 RFC 3967 RFC 6410 RFC 8067

A virtual circuit service at the physical layer (wavelengths, time slots, or physical ports) where a service provider creates isolated connections for customers over shared infrastructure.

Plain language A virtual circuit service at the physical layer creating isolated connections over shared infrastructure.

Used in RFC 5253 RFC 5523

A private network service where a provider carries customers' Layer 2 frames over a shared backbone. The service can be point-to-point or LAN-like.

Plain language A private network service where a provider carries customers' Layer 2 frames over a shared backbone.

Used in RFC 2685 RFC 4664 RFC 4665 RFC 5254 RFC 6074 RFC 6624 RFC 7152 RFC 7275 RFC 7387 RFC 7623 RFC 8466 RFC 9291

A protocol for tunneling Layer 2 frames (such as PPP packets) through an IP network, allowing the transmission of non-IP data over IP networks.

Plain language A protocol for tunneling Layer 2 frames through an IP network.

Used in RFC 2701 RFC 2764 RFC 2809 RFC 2881 RFC 3193 RFC 3308 RFC 3355 RFC 3573 RFC 3817 RFC 3985 RFC 4045 RFC 4170 RFC 4349 RFC 4365 RFC 4454 RFC 4591 RFC 4623 RFC 4667 RFC 4719 RFC 5565 RFC 5571 RFC 5619 RFC 5640 RFC 5641 and 1 more

The Link Control Protocol of PPP. It opens, configures, tests and closes the link, and negotiates link-wide options such as the maximum packet size and authentication.

Plain language The Link Control Protocol of PPP that opens, configures, tests, and closes the link.

Used in RFC 1331 RFC 1332 RFC 1377 RFC 1471 RFC 1473 RFC 1548 RFC 1552 RFC 1570 RFC 1598 RFC 1618 RFC 1638 RFC 1661 RFC 1662 RFC 1663 RFC 1762 RFC 1962 RFC 1967 RFC 1968 RFC 1973 RFC 1974 RFC 1979 RFC 1989 RFC 1990 RFC 1994 and 26 more

The Lightweight Directory Access Protocol, used by clients to search and read entries in a directory server.

Plain language The Lightweight Directory Access Protocol used to search and read entries in a directory server.

Used in RFC 1430 RFC 1431 RFC 1558 RFC 1588 RFC 1777 RFC 1778 RFC 1823 RFC 1844 RFC 1959 RFC 1960 RFC 2247 RFC 2251 RFC 2252 RFC 2253 RFC 2254 RFC 2255 RFC 2256 RFC 2589 RFC 2596 RFC 2651 RFC 2654 RFC 2696 RFC 2739 RFC 2798 and 37 more

An attribute is a named data field in an LDAP entry. For example, the 'cn' (common name) attribute stores a person's name. Each attribute can have one or more values.

Plain language A named data field in an LDAP entry, such as common name or phone number.

Used in RFC 1558 RFC 2252 RFC 2254 RFC 2256 RFC 3045 RFC 3112 RFC 3698

The LDAP operation in which a client states its identity and credentials to a server, which either accepts them and creates an authenticated association or rejects them. After a Turn, each peer is expected to bind again in its new role.

Plain language The operation where a client tells the server who it is and gives its password or certificate. After the roles are reversed, each side does this again in its new role.

Used in RFC 2830 RFC 4531

An extension carried with an LDAP request message that modifies how the operation is processed. Each control has an object identifier, a criticality flag and an optional value.

Plain language An extension carried with an LDAP request that modifies how the operation is processed.

Used in RFC 2696 RFC 2891 RFC 3829 RFC 3876 RFC 4370 RFC 4521 RFC 4527 RFC 4528 RFC 5805

The set of rules in a directory that defines which attribute types and object classes exist and what values they may hold.

Used in RFC 1274 RFC 2256 RFC 2739 RFC 4523 RFC 4524

A uniform resource locator whose scheme is ldap, naming a directory server and a search operation. Its parts are a server, a base distinguished name, attributes, a scope, a filter and optional extensions, separated by question marks.

Plain language A link that describes a directory lookup, including which server and what to ask for.

Used in RFC 2255 RFC 4516

The rule that DNS labels may contain only ASCII Letters, Digits, and Hyphens. Hyphens cannot appear at the start or end of a label.

Plain language The DNS rule that labels may contain only ASCII letters, digits, and hyphens (not at start or end).

Used in RFC 3696 RFC 8222

The Label Distribution Protocol, which lets MPLS routers discover each other, open sessions and exchange label bindings for FECs.

Plain language The Label Distribution Protocol that lets MPLS routers exchange label bindings.

Used in RFC 3035 RFC 3036 RFC 3038 RFC 3213 RFC 3215 RFC 5254 RFC 5443 RFC 5695 RFC 5824 RFC 5919 RFC 6074 RFC 6138 RFC 6373 RFC 6720 RFC 6862 RFC 7140 RFC 7275 RFC 7439 RFC 7490 RFC 7552 RFC 8661 RFC 9291 RFC 10041

A rate-limiting method in which a counter drains at a steady pace and rises with each admitted item. An item is admitted only if the counter is below a limit.

Plain language A rate-limiting method where a counter drains at a steady pace.

Used in RFC 2761 RFC 3247 RFC 3289 RFC 7415 RFC 8582

An extra second occasionally added to (or, in principle, removed from) UTC to keep it in step with the Earth's rotation. In RFC 3339 it appears as a seconds value of 60 at the end of a month, such as 23:59:60Z.

Plain language An extra second occasionally added to UTC to keep it in step with Earth's rotation.

Used in RFC 958 RFC 1305 RFC 3339 RFC 4765 RFC 5905 RFC 5907 RFC 6019 RFC 7164 RFC 7808 RFC 8536 RFC 8633 RFC 8877 RFC 9327 RFC 9557 RFC 9581 RFC 9636 RFC 9760 RFC 9911 RFC 10049

The time for which a DHCP server lends an IP address to a client. When the lease runs out the client must renew it or give the address up.

Plain language The time for which a DHCP server lends an IP address to a client.

Used in RFC 1533 RFC 1534 RFC 1541 RFC 2131 RFC 2132 RFC 2730 RFC 2771 RFC 2907 RFC 3010 RFC 3102 RFC 3103 RFC 3203 RFC 3315 RFC 3456 RFC 3530 RFC 3736 RFC 3995 RFC 4039 RFC 4361 RFC 4388 RFC 4436 RFC 4702 RFC 4703 RFC 4704 and 43 more

A DHCP extension that lets an outside entity, such as a relay agent, ask a DHCP server about the lease state of an address or client.

Plain language A DHCP extension letting an outside entity ask about the lease state of an address.

Used in RFC 5007 RFC 6926 RFC 7653 RFC 7724 RFC 7819

Low Extra Delay Background Transport, a delay-based congestion control algorithm that watches one-way delay and slows down early. It lets background transfers run without disturbing the user's other traffic.

Used in RFC 7574 RFC 8303 RFC 8923

A measure of how strongly a subject's identity was checked during authentication. A higher level means more confidence that the subject is who they claim to be.

Plain language A measure of how strongly a subject's identity was verified during authentication.

Used in RFC 7773 RFC 8485

A formal relationship between two standards organizations where appointed representatives communicate regularly, exchange documents, and coordinate work to avoid conflicts and improve interoperability.

Used in RFC 4441 RFC 7437

A formal written communication between standards organizations, following defined procedures, typically published to allow public visibility into cross-organizational coordination.

Plain language A formal written communication between standards organizations.

Used in RFC 3975 RFC 4052 RFC 4053 RFC 4965 RFC 6756

An optical channel that carries data from one end of a network to the other on a single wavelength, without conversion to electrical signals along the way.

Plain language An end-to-end path for light on one wavelength, through fibre and optical equipment.

Used in RFC 3717 RFC 4054 RFC 7449

Splitting a long content line by inserting a CRLF followed by one space or tab. Parsers unfold it by removing both before reading the line.

Plain language Splitting a long line by inserting a CRLF followed by space, which parsers unfold.

Used in RFC 2445 RFC 2646 RFC 2822 RFC 2849 RFC 3676 RFC 5293 RFC 5545 RFC 6350 RFC 6351 RFC 7095 RFC 7265 RFC 8792

A method of estimating each sample as a weighted sum of the samples just before it. Only the weights and the leftover error need to be stored, which is often smaller than the samples themselves.

Plain language A compression method estimating each sample as a weighted sum of previous samples.

Used in RFC 6716 RFC 9639

A protection scheme where traffic is carried on a primary path and switched to a secondary path if the primary fails. Both paths are monitored, and switching is coordinated between endpoints.

Plain language A protection scheme with a primary and secondary path, with switching if the primary fails.

Used in RFC 6974 RFC 7347

A bundle of parallel links treated as one logical link, with traffic spread across the member links.

Plain language A bundle of parallel links treated as one logical link with traffic spread across them.

Used in RFC 6437 RFC 6438 RFC 7130 RFC 7325 RFC 7510 RFC 7938 RFC 8611 RFC 8668 RFC 9356 RFC 9533 RFC 9534

The lowest layer of the Internet protocol suite, covering how hosts on the same physical network exchange frames. ARP and RARP work here and do not cross routers.

Plain language The lowest layer of the Internet protocol suite, covering frame exchange on one physical network.

Used in RFC 826 RFC 893 RFC 894 RFC 903 RFC 907 RFC 929 RFC 935 RFC 1044 RFC 1112 RFC 1122 RFC 1134 RFC 1172 RFC 1188 RFC 1307 RFC 1329 RFC 1374 RFC 1390 RFC 1551 RFC 1552 RFC 1661 RFC 1717 RFC 1761 RFC 1764 RFC 1937 and 59 more

A protocol that runs between neighboring nodes to manage control channels, correlate link properties, verify connectivity and handle faults for the links between them.

Plain language A protocol managing control channels and verifying connectivity between neighboring nodes.

Used in RFC 3945 RFC 4207 RFC 4209 RFC 5818 RFC 5828

A dimensionless cost value assigned to each link in a routing protocol, used to steer routing decisions toward better paths.

Plain language A cost value assigned to each link in a routing protocol to steer routing decisions.

Used in RFC 3784 RFC 3787 RFC 5578 RFC 7185 RFC 7722 RFC 7779 RFC 8379 RFC 9843 RFC 10041

A named label on a link, such as next or prev-archive, that says how the linked document relates to the current one.

Plain language A named label on a link saying how the linked document relates to the current one.

Used in RFC 5005 RFC 5829 RFC 5988 RFC 5989 RFC 6573 RFC 6690 RFC 6861 RFC 6906 RFC 7033 RFC 8574

A label that says how a link's context relates to its target, such as next or copyright. It is either a registered short name or an extension written as a URI.

Plain language A label saying how a link's context relates to its target, such as next or copyright.

Used in RFC 5988 RFC 6903 RFC 6906 RFC 8288 RFC 8631 RFC 9264

A unit of OSPF routing information describing part of the topology, such as a router's links or a route to another area. LSAs are flooded reliably and stored in each router's link-state database.

Plain language A unit of OSPF routing information describing part of the topology.

Used in RFC 1131 RFC 1245 RFC 1247 RFC 1248 RFC 1252 RFC 1253 RFC 1583 RFC 1584 RFC 1765 RFC 1793 RFC 2154 RFC 2178 RFC 2328 RFC 2370 RFC 2642 RFC 2676 RFC 2740 RFC 3101 RFC 3277 RFC 3509 RFC 3567 RFC 3623 RFC 3630 RFC 3787 and 120 more

A message that an OSPF router sends to announce the state of one of its links to the network.

Plain language A message an OSPF router sends to announce the state of its links.

Used in RFC 1246 RFC 1765 RFC 2370 RFC 3101 RFC 3137 RFC 4061 RFC 4167 RFC 4915 RFC 4970 RFC 5250 RFC 5329 RFC 5817 RFC 7770 RFC 8379

The collection of link state information a router holds about the network. Routing calculations are made from it.

Plain language The collection of link state information a router holds about the network.

Used in RFC 1245 RFC 1246 RFC 1765 RFC 3101 RFC 3719 RFC 4915 RFC 5250 RFC 5309 RFC 5340 RFC 7356 RFC 8202 RFC 8243 RFC 9129 RFC 9552 RFC 9666 RFC 9667

A message in IS-IS that advertises the state of a router's links and the routes it knows about to other routers in the network.

Plain language A message in IS-IS announcing the state of a router's links.

Used in RFC 3719 RFC 3784 RFC 3787 RFC 5311 RFC 6165 RFC 7356 RFC 7357 RFC 7645 RFC 7987 RFC 8243

An IPv6 address valid only on one link. Routers send Router Advertisements from their link-local address, and every IPv6 interface has one.

Plain language An IPv6 address valid only on one link, not sent to other networks.

Used in RFC 1970 RFC 1972 RFC 2019 RFC 2023 RFC 2080 RFC 2373 RFC 2461 RFC 2462 RFC 2464 RFC 2465 RFC 2467 RFC 2470 RFC 2491 RFC 2497 RFC 2529 RFC 2545 RFC 2563 RFC 2590 RFC 2710 RFC 2740 RFC 2772 RFC 2893 RFC 3111 RFC 3146 and 97 more

A technique for OSPF routers to exchange arbitrary data on a direct link without modifying the standard OSPF message structure. Data is appended as optional TLV blocks.

Plain language A technique for OSPF routers to exchange data on a direct link using optional TLV blocks.

Used in RFC 4812 RFC 4813 RFC 5613 RFC 9355

A routing method in which every router learns the full map of routers and links and computes shortest paths from it, rather than trusting distance figures from neighbors.

Plain language A routing method where each router learns the full topology and computes shortest paths.

Used in RFC 816 RFC 898 RFC 981 RFC 1074 RFC 1093 RFC 1131 RFC 1142 RFC 1167 RFC 1195 RFC 1245 RFC 1246 RFC 1247 RFC 1299 RFC 1322 RFC 1371 RFC 1455 RFC 1476 RFC 1478 RFC 1583 RFC 1584 RFC 1629 RFC 1716 RFC 1765 RFC 1774 and 254 more

A raw byte of uncompressed data in a zstd block, stored either directly, repeated (RLE), or Huffman-compressed.

Used in RFC 2060 RFC 7888 RFC 8478

An IEEE 802.2 standard providing the upper portion of the data link layer, offering connection-oriented and connectionless services above the MAC layer.

Plain language An IEEE standard providing the upper part of the data link layer.

Used in RFC 1103 RFC 1188 RFC 1329 RFC 1390 RFC 1538 RFC 1932 RFC 2225 RFC 2297 RFC 2684

A way of wrapping a packet with an 8-octet header that says what kind of data follows. Here it is the default for IP and ATMARP packets sent over AAL5.

Used in RFC 1188 RFC 1755 RFC 2225 RFC 2470 RFC 2684

The Local Mail Transfer Protocol, defined in RFC 2033. Unlike SMTP, it can reject a message for one recipient while accepting the same message for others.

Plain language A local version of SMTP that can accept a message for one recipient and refuse it for another in the same session.

Used in RFC 5429 RFC 9422

Spreading requests across several servers so no single one is overloaded. SRV weights let an administrator express static proportions, such as sending three quarters of logins to a faster machine.

Plain language Spreading requests across several servers so no single one is overloaded.

Used in RFC 1329 RFC 1794 RFC 2052 RFC 2193 RFC 2391 RFC 2702 RFC 2782 RFC 2991 RFC 2992 RFC 3040 RFC 3049 RFC 3074 RFC 3237 RFC 3263 RFC 3466 RFC 3539 RFC 3568 RFC 3868 RFC 4085 RFC 4311 RFC 4655 RFC 4666 RFC 4678 RFC 4814 and 72 more

The Loc-RIB is the routing table a BGP speaker builds from the routes it has received. A route server usually keeps one Loc-RIB for all its clients, but it can keep a separate Loc-RIB per client where clients have conflicting routing policies, at the cost of more CPU and memory.

Plain language The routing table the route server itself uses when it decides which paths to send out to each client.

Used in RFC 1771 RFC 7948 RFC 9069

The special-use domain name .local, which mDNS reserves for names that are resolved by multicast on the local link instead of by ordinary unicast DNS.

Plain language The special-use .local domain name reserved for mDNS resolution on the local link.

Used in RFC 1535 RFC 6440 RFC 6731 RFC 6762

An architecture in which the 802.11 MAC ends at the access point, which handles more of the work itself, while the controller still receives association and key exchange frames.

Plain language An architecture where the 802.11 MAC ends at the access point.

Used in RFC 4564 RFC 5414 RFC 5416

The Proxy Mobile IPv6 router that assigns and anchors a mobile node's home network prefix and tracks where the node is attached.

Plain language The Proxy Mobile IPv6 router that assigns and anchors a mobile node's home prefix.

Used in RFC 4830 RFC 4831 RFC 4832 RFC 5213 RFC 5779 RFC 5844 RFC 5845 RFC 5846 RFC 5847 RFC 5949 RFC 6097 RFC 6279 RFC 6463 RFC 6572 RFC 6602 RFC 6705 RFC 6757 RFC 6909 RFC 7028 RFC 7156 RFC 7222 RFC 7389 RFC 7563 RFC 7864 and 1 more

A BGP attribute that overrides AS path length in route selection, allowing administrators to prefer routes from certain sources (like customers) over others.

Plain language A BGP attribute letting administrators prefer certain routes over others.

Used in RFC 1745 RFC 1998 RFC 4264

A 32-bit local stand-in for a host identity that fits where an IPv4 address would go. It is only meaningful on the local host and is never sent on the wire.

Plain language A 32-bit local stand-in for a host identity used only on the local host.

Used in RFC 5338 RFC 6538 RFC 9063

A BGP attribute used inside one autonomous system to tell other internal routers how much the advertising router prefers a route. Higher values win, and it is not sent to external peers.

Plain language A BGP attribute used inside one AS to tell routers how much it prefers a route.

Used in RFC 1773 RFC 2622 RFC 3345 RFC 4271 RFC 4760 RFC 5004 RFC 5065 RFC 6368 RFC 8207 RFC 8326 RFC 9026 RFC 9494

A MAC address with the U/L bit set to 1, indicating it was assigned by the operating system or network administrator rather than a manufacturer.

Plain language A MAC address assigned by the operating system or administrator rather than a manufacturer.

Used in RFC 9724 RFC 9797

The set of geographic coordinates (latitude, longitude, and altitude) with resolution and datum information, delivered by a DHCP server to a client to inform it of its physical location.

Plain language Geographic coordinates and resolution information delivered by a DHCP server.

Used in RFC 3825 RFC 6225

A server run by an access network provider that knows or can work out where devices on its network are. Devices ask it for their location.

Plain language A server that knows or can determine where devices on its network are located.

Used in RFC 5687 RFC 5985 RFC 5986 RFC 6155 RFC 6881 RFC 7105 RFC 7378 RFC 7840

A data object that carries location information about a person or device together with the privacy rules that govern how that location may be used.

Plain language A data object carrying location information with privacy rules governing its use.

Used in RFC 3693 RFC 6280

A server that speaks a telephony routing protocol, exchanging reachability information about telephone destinations with other such servers.

Plain language A server that exchanges reachability information about telephone destinations.

Used in RFC 3219 RFC 3693 RFC 6772

A URI that stands for a device's location instead of containing it. Anyone authorized who holds the URI can use it to ask for the current location.

Plain language A URI standing for a device's location, allowing authorized parties to ask for current location.

Used in RFC 5985 RFC 5986 RFC 6753 RFC 7378

A method where a location information server issues a URI reference, and the recipient fetches location separately by dereferencing the URI.

Plain language A method where a location server issues a URI reference instead of the location itself.

Used in RFC 5606 RFC 5687 RFC 6442 RFC 6444 RFC 7378

A method where location information is directly conveyed within a signaling message, carrying the actual coordinates or civic address.

Plain language A method where location information is directly conveyed in the signaling message.

Used in RFC 6444 RFC 7378

An IP address that represents the current attachment point of a host to the Internet, used for actual routing of packets.

Plain language An IP address representing the current attachment point of a host.

Used in RFC 1753 RFC 1992 RFC 2101 RFC 4177 RFC 4214 RFC 4423 RFC 5206 RFC 5533 RFC 6316 RFC 6317 RFC 6740 RFC 6742 RFC 6743 RFC 6744 RFC 6745 RFC 6746 RFC 6748 RFC 8046 RFC 9063 RFC 9300 RFC 9602

An ICMP message sent by an ILNP node to inform correspondent nodes that its set of valid Locators has changed. Authenticated using the ILNP Nonce to prevent spoofing. Enables session continuity across mobility events.

Plain language An ICMP message sent when an ILNP node's set of valid locators changes.

Used in RFC 6740 RFC 6741

A routing protocol that separates the identity of a network node from its location, allowing more flexible network architectures and easier host mobility.

Plain language A routing protocol separating a node's identity from its location.

Used in RFC 6830 RFC 6832 RFC 6835 RFC 6836 RFC 7052 RFC 7215 RFC 8059 RFC 8111 RFC 8113 RFC 9299 RFC 9300 RFC 9301 RFC 9303 RFC 9304 RFC 10040

A routing idea that splits an address into an identifier for the endpoint and a locator for where it is attached. LISP implements it with EIDs and RLOCs.

Plain language A routing idea splitting an address into an endpoint identifier and attachment location.

Used in RFC 4218 RFC 5533 RFC 5558 RFC 5720 RFC 6115 RFC 6830 RFC 7215 RFC 9299 RFC 9300

A scheme in which a sender transmits one packet and waits for its acknowledgment before sending the next. It gives flow control with almost no state, at the cost of speed.

Plain language Sending one packet and waiting for acknowledgment before the next.

Used in RFC 203 RFC 916 RFC 998 RFC 1350 RFC 2347 RFC 2348 RFC 2349 RFC 3366

A management function (such as a router, bridge, or repeater instance) that an SNMP agent manages and that may depend on one or more physical components.

Plain language A management function such as a router or bridge instance that an SNMP agent manages.

Used in RFC 2037 RFC 4133 RFC 6933

A modular processing stage in a network forwarding element, connected to other LFBs in a pipeline to forward packets according to defined rules.

Plain language A modular processing stage in network forwarding, connected to other blocks in a pipeline.

Used in RFC 5810 RFC 6956 RFC 6984 RFC 7409

A fine-grained, logically separable piece of forwarding element processing, such as a classifier or a meter. Blocks are connected in a directed graph along a data path.

Plain language A fine-grained, logically separable piece of forwarding processing.

Used in RFC 5812 RFC 6053 RFC 6369 RFC 7121 RFC 7729 RFC 8013

In Classical IP over ATM, a group of computers on an ATM network that share the same IP subnet and can communicate directly without using routers.

Plain language In Classical IP over ATM, a group of computers sharing an IP subnet and communicating directly.

Used in RFC 1735 RFC 2583

A group of hosts and routers on an ATM network that are administratively treated as one IP subnet. Each one is served by its own ATM ARP Server.

Plain language A group of hosts and routers on an ATM network treated as one IP subnet.

Used in RFC 2225 RFC 2226 RFC 2332 RFC 2335 RFC 2443 RFC 2834 RFC 2835

A collection of hosts and routers on the same physical data link that share an IP subnet address prefix, used in classical IP over ATM.

Plain language A collection of hosts and routers sharing an IP subnet on the same physical data link.

Used in RFC 1577 RFC 1937

A tree of keys that lets a group server rekey efficiently. Each member holds the keys along one path, so a compromised member can be cut off without redoing every key.

Plain language A tree of keys letting a group server rekey efficiently.

Used in RFC 4535 RFC 9838

In VTAM/SNA, a terminal or printer identified by a unique name, through which applications communicate with users or devices.

Plain language In VTAM/SNA, a terminal or printer identified by a unique name.

Used in RFC 1646 RFC 1665 RFC 2232 RFC 7143

The address of a logical unit, such as a disk, inside a SCSI target. A single target can contain several logical units, each with its own number.

Plain language The address of a logical unit such as a disk inside a SCSI target.

Used in RFC 1666 RFC 3720 RFC 4173 RFC 4455

A network with high bandwidth and long propagation delay, characterized by a large bandwidth-delay product. Examples include transcontinental fiber links and satellite links.

Plain language A network with high bandwidth and long propagation delay, like transcontinental fiber or satellite links.

Used in RFC 1185 RFC 2760 RFC 7323

A way of polling in which the server holds the request open until new data is available or a timeout passes, instead of answering immediately with nothing.

Plain language A polling method where the server holds the request open until new data is available.

Used in RFC 6202 RFC 8936 RFC 9569

The forwarding rule that, when several routes match a destination, chooses the one with the longest prefix, that is, the most specific.

Plain language The forwarding rule choosing the route with the longest prefix when several match.

Used in RFC 1519 RFC 1629 RFC 1812 RFC 2519 RFC 2725 RFC 3036 RFC 3484 RFC 3675 RFC 3956 RFC 4191 RFC 4632 RFC 5036 RFC 5283 RFC 6226 RFC 6724 RFC 6956 RFC 7115 RFC 7267 RFC 7285 RFC 7421 RFC 7484 RFC 7596 RFC 7597 RFC 7598 and 19 more

An alternate next-hop guaranteed by its routing computation not to create a loop back toward the source. Used as the secondary path in MoFRR.

Plain language An alternate next-hop guaranteed not to create a loop back toward the source.

Used in RFC 5286 RFC 5714 RFC 6571 RFC 7431 RFC 7473 RFC 7490 RFC 7777 RFC 7812 RFC 7916 RFC 8102 RFC 8518 RFC 8966 RFC 9479 RFC 9492

A test mode in which a signal is sent back toward where it came from instead of being passed on. It lets operators check a line or device from one end.

Plain language A test mode where a signal is sent back toward where it came from.

Used in RFC 3330 RFC 3896 RFC 5735 RFC 6136 RFC 6761 RFC 8252

The number of loss events as a fraction of the packets transmitted. A loss event is one or more lost or marked packets within a window of data.

Plain language The number of loss events as a fraction of packets transmitted.

Used in RFC 3448 RFC 4342 RFC 4654

Compression that lets you rebuild exactly the original data. No lossless method can shrink every possible input, so some inputs stay the same size or grow slightly.

Plain language Compression that lets you rebuild exactly the original data.

Used in RFC 468 RFC 798 RFC 804 RFC 1144 RFC 1314 RFC 1553 RFC 1663 RFC 1789 RFC 1950 RFC 1951 RFC 1952 RFC 1962 RFC 1967 RFC 1974 RFC 1975 RFC 1976 RFC 1977 RFC 1978 RFC 1979 RFC 1993 RFC 2032 RFC 2083 RFC 2118 RFC 2302 and 53 more

LoST, the Location-to-Service Translation protocol, maps a location and a service type to the URI of the right provider. For emergency calls it returns the PSAP that covers the caller's location.

Plain language The Location-to-Service Translation protocol that returns the PSAP covering a caller's location.

Used in RFC 6443 RFC 6739 RFC 6881

The Location-to-Service Translation protocol. It lets a client send a location and a service type and get back the URIs of the matching service providers.

Plain language The Location-to-Service Translation protocol mapping a location and service type to matching provider URIs.

Used in RFC 5582 RFC 6444 RFC 6451

When one author's changes are overwritten because a second author saves without merging the first author's edits. Locking is meant to prevent it.

Plain language When one author's changes are overwritten because another author saves without merging edits.

Used in RFC 2291 RFC 4918 RFC 7232

A network of constrained devices and links where energy is limited and packets are often lost. LLNs can be built as star or mesh topologies.

Plain language A network of constrained devices with limited energy and unreliable links.

Used in RFC 6550 RFC 6574 RFC 6606 RFC 8505 RFC 9010 RFC 9139 RFC 9685

A network of small, often battery-powered devices with limited memory, connected by links that can be unreliable and change quality over time.

Plain language A network of small, battery-powered devices with limited memory on unreliable links.

Used in RFC 5548 RFC 5673 RFC 5826 RFC 6551 RFC 6552 RFC 6574 RFC 6997 RFC 7102 RFC 7400 RFC 7416 RFC 7731 RFC 7733 RFC 9008 RFC 9010

A Low-Power Wide-Area Network is a wireless network built for large coverage areas, low bandwidth, very small packets and long battery life.

Plain language A Low-Power Wide-Area Network for large coverage areas and small packets with long battery life.

Used in RFC 8376 RFC 8724 RFC 9011 RFC 9442

Sending only the least significant bits of a number that changes slowly. The receiver combines them with the last known value to recover the full number.

Plain language Sending only the least significant bits of a slowly changing number.

Used in RFC 3095 RFC 4224 RFC 5225 RFC 6846

A packet flooded throughout an IS-IS domain describing the links and reachability of a particular router or pseudonode.

Plain language A packet flooded throughout an IS-IS domain describing a router's links and reachability.

Used in RFC 2973 RFC 3272 RFC 3719 RFC 3784 RFC 3787 RFC 3812 RFC 3847 RFC 4128 RFC 4182 RFC 4208 RFC 4428 RFC 5127 RFC 5303 RFC 5317 RFC 5440 RFC 5994 RFC 6001 RFC 6003 RFC 6119 RFC 6165 RFC 6371 RFC 6424 RFC 6426 RFC 7110 and 8 more

A temporary grant from a PCC to a PCE of the right to update some attributes of a label switched path. The PCC can revoke it at any time, and the PCE can return it.

Plain language A temporary grant of the right to update attributes of a label-switched path.

Used in RFC 8231 RFC 8741

The process of passing each new LSP from router to router until every router in the area has a copy. Unnecessary regeneration of LSPs makes this happen more often than needed.

Plain language Passing each new LSP from router to router until every router has a copy.

Used in RFC 7987 RFC 9681

A tool for detecting data plane failures along an MPLS Label Switched Path, defined in RFC 4379. It uses fields and TLVs whose code points are tracked in IANA registries.

Plain language A tool for detecting data plane failures along an MPLS label-switched path.

Used in RFC 5884 RFC 6424 RFC 6426 RFC 7110 RFC 7276 RFC 7506 RFC 7537

A dictionary-style method that replaces a repeated string with a pointer made of a length and a backward distance to an earlier copy. DEFLATE limits distances to 32K bytes and lengths to 258 bytes.

Plain language A dictionary-style compression method replacing repeated strings with pointers.

Used in RFC 1505 RFC 1950 RFC 1951 RFC 1974 RFC 1979 RFC 2118 RFC 2395 RFC 3284 RFC 7400 RFC 7692 RFC 7932 RFC 9841