N

A negative acknowledgement, sent by a receiver to report that data is missing so the sender or another agent can repair the loss.

Plain language A message indicating data was not received and should be retransmitted.

Used in RFC 2887 RFC 3048 RFC 4410 RFC 4588 RFC 5401 RFC 5740 RFC 6285

A technique in which receivers delay sending negative acknowledgments and suppress their own NACK if they hear a similar request from another receiver, reducing feedback traffic in large groups.

Used in RFC 3941 RFC 5740

A TCP technique that holds back small segments while earlier data is unacknowledged, so that many tiny writes are combined into fewer packets.

Plain language A TCP technique combining small data segments to reduce the number of packets.

Used in RFC 896 RFC 1122 RFC 2126 RFC 3539 RFC 3821 RFC 4172 RFC 4653 RFC 5044 RFC 6897 RFC 7661 RFC 7805 RFC 8303 RFC 8490 RFC 8831 RFC 9648 RFC 9923

A user identity in the form user@realm, used for roaming authentication in wireless networks.

Plain language A user identity like an email address used for wireless network authentication.

Used in RFC 2477 RFC 2794 RFC 2977 RFC 2989 RFC 3141 RFC 3169 RFC 3846 RFC 4186 RFC 4187 RFC 4282 RFC 4283 RFC 4284 RFC 5149 RFC 5216 RFC 5729 RFC 6155 RFC 6572 RFC 6696 RFC 7542 RFC 7585 RFC 7831 RFC 8559 RFC 9140 RFC 9190 and 2 more

A Network Abstraction Layer unit is the packet-sized chunk in which H.264 video data is organized. Each starts with a header byte that gives its type.

Plain language A packet-sized unit of H.264 video data with a header identifying its type.

Used in RFC 3984 RFC 6184 RFC 6190 RFC 7798 RFC 9328 RFC 9584 RFC 10034

A DNS message scheme in which a repeated name suffix is replaced by a 2-byte pointer to an earlier occurrence within the same message.

Plain language A DNS technique using pointers to avoid repeating domain name suffixes.

Used in RFC 883 RFC 1002 RFC 1035 RFC 3361 RFC 3397 RFC 3597 RFC 5855 RFC 8618 RFC 9139 RFC 9665

A limit in a CA certificate that restricts which names the certificates beneath it may contain. Path validation checks each name against these limits.

Plain language A restriction in a certificate limiting which domain names the issuer can vouch for.

Used in RFC 5914 RFC 9549 RFC 9598

A server that holds DNS data for some part of the name space, or knows where to refer queries.

Plain language A server holding DNS records for a domain or directing queries elsewhere.

Used in RFC 620 RFC 621 RFC 623 RFC 811 RFC 812 RFC 814 RFC 819 RFC 830 RFC 878 RFC 881 RFC 882 RFC 883 RFC 897 RFC 920 RFC 921 RFC 955 RFC 973 RFC 1001 RFC 1002 RFC 1031 RFC 1032 RFC 1033 RFC 1034 RFC 1386 and 69 more

An SSH data type: a comma-separated list of algorithm names, ordered from most to least preferred, such as the list of ciphers in a KEXINIT message.

Plain language A list of algorithms ordered by preference for negotiation in SSH.

Used in RFC 4253 RFC 8308

Another ICN architecture (NDN) that emphasizes named data objects as the primary abstraction, with native support for caching, multicast, and mobility.

Used in RFC 7476 RFC 7945 RFC 9064 RFC 9139 RFC 9531

An addressable unit of data in an information-centric network that has a name bound to it, usually with a way to check that binding.

Plain language Data requested by name rather than location in an information-centric network.

Used in RFC 7927 RFC 9138

A profile of stringprep designed for domain names and used in IDNA (Internationalized Domain Names in Applications).

Plain language A standard for preparing internationalized domain names for consistent handling.

Used in RFC 3490 RFC 3491 RFC 4690 RFC 4713 RFC 6122 RFC 6885

A named region of a larger naming space, identified by a prefix. In IMAP, a namespace groups mailboxes such as a user's own, other users' or shared ones.

Plain language A named region of a larger space, like user or shared mailboxes in IMAP.

Used in RFC 2342 RFC 3085 RFC 3920 RFC 4910 RFC 5013 RFC 5226 RFC 5255 RFC 5716 RFC 7061 RFC 7076 RFC 7254 RFC 8126 RFC 9051

The first component of a URN identifying which organization or standard manages that URN space. For example, 'urn:geant:' has the namespace ID 'geant'.

Plain language The prefix in a URN identifying the organization managing that namespace.

Used in RFC 2611 RFC 4926 RFC 9326

A short code that identifies a specific URN namespace and appears after 'urn:' in a URN, such as 'fipa' in urn:fipa:language:acl.

Plain language A code after 'urn:' in a URN identifying the managing organization.

Used in RFC 2141 RFC 3406 RFC 3616 RFC 6061 RFC 6588 RFC 6963 RFC 8057 RFC 8141 RFC 9517

The part of a URN after the namespace identifier, containing the actual name assigned to a resource within that namespace.

Plain language The part of a URN after the namespace identifier containing the resource name.

Used in RFC 2141 RFC 3121 RFC 3613 RFC 3937 RFC 8458

An organization or group responsible for assigning unique names within a branch of the namespace and ensuring that those names are not reused.

Plain language An organization responsible for assigning and managing names in a namespace.

Used in RFC 819 RFC 1737 RFC 3613 RFC 3650 RFC 3651

A form of NAT that maps (private address, TCP/UDP port or ICMP query ID) tuples onto one public address with assigned ports, letting many hosts share a single public IP address.

Plain language A form of NAT where multiple devices share one public IP address with different ports.

Used in RFC 2663 RFC 2993 RFC 3022 RFC 3027 RFC 3235 RFC 3303 RFC 3715 RFC 4008 RFC 4787 RFC 5135 RFC 5508 RFC 5571 RFC 5902 RFC 6056 RFC 6146 RFC 6619 RFC 6736 RFC 7596 RFC 7597 RFC 7857 RFC 8676 RFC 9109 RFC 9313

The Naming Authority Pointer, a DNS resource record type that holds DDDS rules. Each record carries order, preference, flags, services, regexp and replacement fields.

Plain language A DNS record type carrying rules for converting one identifier format to another.

Used in RFC 2168 RFC 2169 RFC 3761 RFC 3764 RFC 4238 RFC 4725 RFC 5483 RFC 5986 RFC 6116 RFC 6950 RFC 7553

A DNS record type that holds a service name and a rewrite rule. ENUM uses it to turn a telephone number into a URI.

Plain language A DNS record specifying how to convert a telephone number to an internet address.

Used in RFC 2168 RFC 2916 RFC 3263 RFC 3401 RFC 3403 RFC 3404 RFC 3405 RFC 3761 RFC 3764 RFC 3824 RFC 3953 RFC 3958 RFC 4002 RFC 4095 RFC 4114 RFC 4355 RFC 4415 RFC 4759 RFC 4769 RFC 4848 RFC 4969 RFC 4979 RFC 5278 RFC 5679 and 5 more

The device that gives users access to a network, such as a modem pool or a VPN gateway. In RADIUS it is the client: it collects the credentials, asks the server, and enforces the answer.

Plain language A device controlling network access and enforcing policies from an authentication server.

Used in RFC 2058 RFC 2138 RFC 2139 RFC 2194 RFC 2284 RFC 2341 RFC 2548 RFC 2607 RFC 2618 RFC 2619 RFC 2637 RFC 2805 RFC 2809 RFC 2865 RFC 2866 RFC 2867 RFC 2868 RFC 2869 RFC 2881 RFC 2882 RFC 2989 RFC 3127 RFC 3162 RFC 3169 and 50 more

A method where a border router rewrites IP addresses, and sometimes ports, in packets so that hosts with private addresses can communicate with the external Internet. RFC 3022 describes the traditional forms, Basic NAT and NAPT.

Plain language A router rewriting addresses in packets so private networks can access the internet.

Used in RFC 959 RFC 1335 RFC 1347 RFC 1597 RFC 1621 RFC 1627 RFC 1669 RFC 1754 RFC 1917 RFC 1918 RFC 1958 RFC 2008 RFC 2071 RFC 2072 RFC 2101 RFC 2182 RFC 2194 RFC 2391 RFC 2428 RFC 2505 RFC 2549 RFC 2647 RFC 2663 RFC 2694 and 367 more

An association of two IP address and port pairs, typically one private and one public, that lets a NAT device translate traffic for one flow or endpoint.

Plain language A mapping between private and public addresses allowing reply traffic to return.

Used in RFC 3989 RFC 4540 RFC 6736 RFC 7857

The IKE and ESP techniques for working through a NAT, mainly detecting it with hashed address notifications and moving to UDP port 4500 with UDP-encapsulated ESP.

Plain language Techniques for establishing encrypted connections through network address translators.

Used in RFC 3235 RFC 3424 RFC 3489 RFC 3519 RFC 3581 RFC 3605 RFC 3723 RFC 3904 RFC 3947 RFC 3948 RFC 4008 RFC 4306 RFC 4380 RFC 4555 RFC 4787 RFC 4961 RFC 5128 RFC 5164 RFC 5189 RFC 5207 RFC 5245 RFC 5265 RFC 5266 RFC 5382 and 118 more

A translation mechanism that lets client devices using IPv6 communicate with servers that have only IPv4 connectivity.

Plain language A translator enabling IPv6 devices to communicate with IPv4-only servers.

Used in RFC 6147 RFC 6312 RFC 6342 RFC 6535 RFC 6889 RFC 6967 RFC 7050 RFC 7051 RFC 7225 RFC 7269 RFC 7393 RFC 7599 RFC 7849 RFC 8219 RFC 8305 RFC 8368 RFC 8512 RFC 8781 RFC 8880 RFC 8925 RFC 9386

A network link technology that supports multiple connected devices but does not provide broadcast or multicast capabilities, such as ATM, SMDS, or X.25 networks.

Plain language A network where messages cannot reach all devices at once, requiring individual delivery.

Used in RFC 1586 RFC 1735 RFC 2332 RFC 2491 RFC 2844

A Non-Broadcast Multiple Access network, such as ATM, SMDS or X.25, where many stations attach to one network but a message cannot simply be broadcast to all of them.

Plain language A network supporting many devices but not broadcast, requiring individual addressing.

Used in RFC 2333 RFC 2334 RFC 2491

A Network Control Protocol. PPP has one NCP per network-layer protocol, and each sets up and configures its protocol, for example the address, once the link is open.

Plain language A PPP protocol that sets up and configures one network-layer protocol.

Used in RFC 1 RFC 33 RFC 36 RFC 39 RFC 40 RFC 42 RFC 44 RFC 48 RFC 54 RFC 55 RFC 57 RFC 60 RFC 66 RFC 74 RFC 78 RFC 80 RFC 91 RFC 97 RFC 98 RFC 100 RFC 101 RFC 102 RFC 105 RFC 107 and 121 more

A message from a receiver saying that specific data did not arrive. Often shortened to NACK, it is the opposite of a positive acknowledgement (ACK).

Used in RFC 1301 RFC 4585

A message from a receiver saying that a particular piece of data did not arrive. The sender only has to react to losses, not to every success.

Plain language A message indicating which data did not arrive, requiring only selective retransmission.

Used in RFC 2887 RFC 3208 RFC 3940 RFC 5740

Remembering that a name or record does not exist, so the same question need not be asked again until a stored timer runs out.

Plain language Caching a negative result so the same failed query is not repeated.

Used in RFC 1536 RFC 2308 RFC 2505 RFC 4074 RFC 4388 RFC 4697 RFC 5074 RFC 5518 RFC 6303 RFC 6651 RFC 7535 RFC 7945 RFC 8020 RFC 8145 RFC 8198 RFC 8686 RFC 8749 RFC 8766 RFC 8767 RFC 9077 RFC 9301 RFC 9437 RFC 9520 RFC 9567

A table of recently contacted on-link neighbors that maps each IPv6 address to its link-layer address and tracks a reachability state (INCOMPLETE, REACHABLE, STALE, DELAY or PROBE). It is IPv6’s counterpart to the ARP cache.

Plain language A table of nearby IPv6 devices with their addresses and reachability status.

Used in RFC 1971 RFC 2461 RFC 2491 RFC 2590 RFC 2641 RFC 3122 RFC 3756 RFC 3964 RFC 3971 RFC 4293 RFC 4311 RFC 4389 RFC 4429 RFC 4861 RFC 5568 RFC 5648 RFC 5942 RFC 5949 RFC 6059 RFC 6106 RFC 6164 RFC 6583 RFC 6706 RFC 6775 and 21 more

The IPv6 protocol that nodes on a link use to find routers, learn each other's link-layer addresses and track whether neighbors are reachable.

Plain language An IPv6 protocol for discovering nearby devices and routers on the same link.

Used in RFC 2462 RFC 2463 RFC 2466 RFC 2470 RFC 2491 RFC 2497 RFC 2529 RFC 2590 RFC 3041 RFC 3146 RFC 3756 RFC 3971 RFC 4260 RFC 4429 RFC 4832 RFC 4862 RFC 4943 RFC 4957 RFC 4968 RFC 5121 RFC 5154 RFC 5309 RFC 5380 RFC 5461 and 20 more

The part of Neighbor Discovery that checks whether a neighbor is still reachable, using hints from upper-layer protocols or unicast Neighbor Solicitations, but only for neighbors the node is sending to.

Plain language Checking whether nearby devices still respond before using cached addresses.

Used in RFC 823 RFC 2461 RFC 3756 RFC 3971 RFC 4191 RFC 4213 RFC 4294 RFC 4429 RFC 4861 RFC 4943 RFC 5180 RFC 5214 RFC 5534 RFC 5798 RFC 5942 RFC 6434 RFC 6550 RFC 6583 RFC 6775 RFC 6820 RFC 6957 RFC 7048 RFC 7066 RFC 7219 and 5 more

The text mode in TFTP: 8-bit ASCII with the modifications from the Telnet specification. The receiver converts it to its own text format.

Plain language A standard text format compatible with most computers for TFTP transfers.

Used in RFC 294 RFC 1350 RFC 5198

An older network protocol used by Windows systems for name resolution and file sharing, predating modern TCP/IP-based approaches.

Plain language An outdated protocol Windows used for name resolution and file sharing.

Used in RFC 1001 RFC 1795 RFC 2097 RFC 2114 RFC 2166

The Network Configuration Protocol, defined in RFC 6241, used to configure network devices and read their datastores.

Plain language A standard protocol for configuring network devices and retrieving their settings.

Used in RFC 4743 RFC 4744 RFC 5277 RFC 5381 RFC 5493 RFC 5671 RFC 5717 RFC 5950 RFC 6020 RFC 6022 RFC 6087 RFC 6110 RFC 6242 RFC 6470 RFC 6536 RFC 6632 RFC 6643 RFC 6728 RFC 7277 RFC 7317 RFC 7407 RFC 7576 RFC 7589 RFC 7803 and 51 more

A named piece of functionality that supplements the base NETCONF protocol, identified by a URI and announced in the hello message at the start of a session.

Plain language A feature a device announces it supports at the start of a NETCONF session.

Used in RFC 6241 RFC 7758

The loss of a link between two servers in a chat network, which divides the network into separate parts. Each side then sees only the users who are connected to servers on its own side.

Plain language A link failure between network servers dividing them into isolated groups.

Used in RFC 1459 RFC 2813

A device that aggregates subscriber traffic from many access nodes. It enforces policy and IP quality of service and is also called a BNG or BRAS.

Plain language A device managing subscriber traffic and enforcing network policies.

Used in RFC 2477 RFC 2881 RFC 3169 RFC 3539 RFC 4014 RFC 4282 RFC 5176 RFC 5447 RFC 5713 RFC 5851 RFC 6320 RFC 6929 RFC 9887

A PPP protocol that sets up and configures one particular network-layer protocol on a link. Each network protocol that PPP carries has its own.

Plain language A PPP protocol establishing rules for a particular network-layer protocol.

Used in RFC 1171 RFC 1331 RFC 1378 RFC 1548 RFC 1552

NEA is an open architecture that lets network operators collect information about the configuration and state of endpoints. The information can be used to enforce policies and monitor endpoint health.

Used in RFC 6813 RFC 8412

A component of the 5G System's service-based architecture, specified by 3GPP. Each type of network function is identified by a short ASCII string such as AMF.

Plain language A specialized component in a 5G network assigned a specific role.

Used in RFC 8192 RFC 9310 RFC 9509

The process of overseeing, monitoring, and controlling network devices and their performance using protocols and systems such as SNMP.

Plain language Remotely monitoring and controlling network devices from a central system.

Used in RFC 1022 RFC 1028 RFC 1155 RFC 1441 RFC 1446 RFC 1573 RFC 1857 RFC 2108 RFC 2515 RFC 2574 RFC 2790 RFC 2925 RFC 4113 RFC 5066 RFC 5345 RFC 5493 RFC 5950 RFC 8368

A protocol that allows an entire mobile network to maintain connectivity while moving. Mobile routers establish tunnels with home agents to continue receiving traffic even when away from home.

Plain language A protocol maintaining connectivity for an entire moving network like on an aircraft.

Used in RFC 4888 RFC 4889 RFC 6089

A server that forwards network packets from one endpoint to another, often used when the endpoints cannot connect directly due to firewalls or NATs.

Used in RFC 974 RFC 3340 RFC 5128 RFC 6012 RFC 6156

A set of network resources (buffers, bandwidth, routing state) reserved for a group of network slices, enabling isolation and predictable service delivery.

Plain language A reserved portion of network resources for a group of network slices.

Used in RFC 9732 RFC 9889

A packet-processing engine that inspects and optionally modifies packets traversing a network, such as a firewall, intrusion detection system, or deep packet inspection engine.

Plain language A device like a firewall that inspects and filters network traffic.

Used in RFC 8192 RFC 8329 RFC 9061

The NSH is the encapsulation used in the Service Function Chaining architecture to carry packets and metadata along a chain of services.

Plain language A header specifying the sequence of services a packet must traverse.

Used in RFC 8459 RFC 8595 RFC 8596 RFC 8677 RFC 8924 RFC 8979 RFC 9015 RFC 9451 RFC 9452 RFC 9516

An isolated logical network tailored to support specific service requirements, such as guaranteed bandwidth or low latency, using shared physical infrastructure.

Plain language An isolated logical network with specific performance characteristics on shared infrastructure.

Used in RFC 9543 RFC 9732 RFC 9889

A protocol for synchronizing clocks on computer networks to a common time within milliseconds.

Plain language A protocol synchronizing computer clocks to a common time.

Used in RFC 1165 RFC 1291 RFC 1305 RFC 1708 RFC 2375 RFC 2679 RFC 2681 RFC 3432 RFC 4778 RFC 5906 RFC 5908 RFC 6051 RFC 6776 RFC 6812 RFC 7576 RFC 7822 RFC 8633 RFC 8877 RFC 8915

The basic terminal that every Telnet implementation must support: 7-bit ASCII text with escape sequences for control functions, used when no fancier options are negotiated.

Plain language A standard terminal interface every Telnet implementation must support.

Used in RFC 137 RFC 139 RFC 318 RFC 354 RFC 357 RFC 435 RFC 495 RFC 513 RFC 529 RFC 596 RFC 658 RFC 764 RFC 855 RFC 856 RFC 857 RFC 858 RFC 860 RFC 937 RFC 1041 RFC 1079 RFC 1091 RFC 1096 RFC 1123 RFC 1184 and 6 more

The imaginary standard terminal that both ends of a Telnet connection pretend to be: a seven-bit USASCII printer and keyboard, line-buffered by default. Each host maps its real devices to the NVT.

Plain language A standard terminal interface that Telnet implementations emulate for compatibility.

Used in RFC 15 RFC 106 RFC 110 RFC 158 RFC 216 RFC 295 RFC 327 RFC 328 RFC 377 RFC 407 RFC 452 RFC 470 RFC 524 RFC 542 RFC 560 RFC 563 RFC 730 RFC 735 RFC 749 RFC 782 RFC 854 RFC 930 RFC 1043 RFC 1205 and 8 more

The first-hop device that encapsulates packets from tenant systems and tunnels them to a remote edge, which decapsulates them before delivery.

Plain language A device encapsulating packets into tunnels and decapsulating them at the destination.

Used in RFC 7364 RFC 7365 RFC 8293 RFC 8365 RFC 8394 RFC 9574

The boundary point where tenant traffic enters and leaves the overlay network. It encapsulates outgoing packets into tunnels and decapsulates arriving tunnel packets. Can be implemented on a hypervisor, switch, or appliance.

Plain language A device encapsulating packets into overlay tunnels and decapsulating them.

Used in RFC 8014 RFC 9469

An IPv6 prefix chosen by an organization from its own address space for use in algorithmic mapping. It can be 32, 40, 48, 56, 64 or 96 bits long.

Used in RFC 6052 RFC 6145 RFC 7051

A named category of news articles, such as net.unix-wizards, that readers can select and read, and to which articles are posted.

Plain language A named discussion category where articles are posted and read.

Used in RFC 977 RFC 1855 RFC 2076 RFC 2980 RFC 3977 RFC 4643 RFC 4707 RFC 5536 RFC 5537 RFC 6048

A field in an IPv6 header or extension header that says what comes next. The value 58 means the next thing is an ICMPv6 message.

Plain language A field in an IPv6 packet indicating the type of the next header.

Used in RFC 1826 RFC 2402 RFC 2406 RFC 2460 RFC 2463 RFC 2780 RFC 3173 RFC 3843 RFC 4443 RFC 4727 RFC 5095 RFC 5856 RFC 5858 RFC 6145 RFC 6282 RFC 6438 RFC 7045 RFC 7112 RFC 7280 RFC 7676 RFC 8754 RFC 9098 RFC 9837 RFC 9947

The address of the next router to which a packet for a destination should be sent.

Plain language The address of the next router on the path to a destination.

Used in RFC 827 RFC 1267 RFC 1322 RFC 1388 RFC 1403 RFC 1479 RFC 1716 RFC 1722 RFC 1723 RFC 1745 RFC 1771 RFC 2080 RFC 2332 RFC 2333 RFC 2335 RFC 2453 RFC 2545 RFC 2598 RFC 2603 RFC 2677 RFC 2735 RFC 2858 RFC 2991 RFC 2992 and 49 more

Network File System, a protocol that allows computers on a network to access files on remote servers as if they were local.

Plain language A protocol for accessing files on a remote server as if they were local.

Used in RFC 1207 RFC 2055 RFC 2755 RFC 5661 RFC 5662 RFC 5716 RFC 6641 RFC 7204 RFC 7532 RFC 7861 RFC 7862 RFC 7863 RFC 8178 RFC 8881

The Next Hop Resolution Protocol, defined in RFC 2332, in which NHRP clients (NHCs) ask NHRP servers (NHSes) to resolve addresses on a non-broadcast network.

Plain language A protocol for discovering direct paths to devices on non-broadcast networks.

Used in RFC 1932 RFC 1937 RFC 2332 RFC 2333 RFC 2334 RFC 2491 RFC 2520 RFC 2583 RFC 2677

A group of four bits, which is exactly one hexadecimal digit. Two nibbles make one byte.

Plain language A group of four bits equal to one hexadecimal digit.

Used in RFC 1886 RFC 3596

A short 16-bit name that identifies a TRILL switch in the TRILL header, used instead of a long hardware address.

Plain language A short identifier for a switch used instead of a long hardware address.

Used in RFC 1459 RFC 7067 RFC 7174 RFC 7455 RFC 7978 RFC 8139 RFC 8243 RFC 8380 RFC 8383 RFC 8384 RFC 8397

The Network Level Protocol ID is a one-octet field that tells the receiver which protocol or encapsulation follows in the frame.

Plain language A field indicating which protocol follows in a frame.

Used in RFC 1294 RFC 1356 RFC 1490 RFC 1598 RFC 2363 RFC 2427 RFC 2684 RFC 6328

Network Layer Reachability Information: the list of IP prefixes, each encoded as a length in bits followed by just enough octets to hold the prefix, that an UPDATE message advertises as reachable via its path attributes.

Plain language The list of IP address ranges announced as reachable in a BGP update.

Used in RFC 1745 RFC 1771 RFC 1772 RFC 1774 RFC 2439 RFC 2545 RFC 2858 RFC 3107 RFC 4271 RFC 4272 RFC 4364 RFC 4659 RFC 4684 RFC 4724 RFC 4760 RFC 4761 RFC 4781 RFC 5195 RFC 5565 RFC 5575 RFC 6074 RFC 6396 RFC 6514 RFC 6515 and 41 more

The Network Management Datastore Architecture. A model that conforms to it keeps operational state in the same tree as configuration, rather than in a separate state tree.

Plain language An architecture storing device configuration and operational state together.

Used in RFC 8344 RFC 8407 RFC 8791 RFC 8795 RFC 9127 RFC 9129 RFC 9314 RFC 9363 RFC 9907

The Network News Transfer Protocol, used by clients and servers to read, post and exchange Netnews articles.

Plain language A protocol for reading, posting, and exchanging network news articles.

Used in RFC 977 RFC 1011 RFC 2980 RFC 3977 RFC 4642 RFC 4643 RFC 4644 RFC 5536 RFC 5538 RFC 8054

A DNS answer with RCODE NOERROR but no records of the type asked for. The name exists, but not with that kind of record. It is inferred from the answer, not signalled by a code.

Plain language A DNS response indicating the name exists but no records of the requested type.

Used in RFC 2308 RFC 8020 RFC 9660 RFC 9975

The nominations committee that nominates the members of the IESG and the IAB. Its nominees are then approved by another body.

Plain language The committee nominating candidates for Internet governance positions.

Used in RFC 2028 RFC 3677 RFC 3797 RFC 8713 RFC 9281 RFC 9389

A committee formed annually to review open IESG and IAB positions, propose candidates to fill them, and manage the confirmation process. Often shortened to NomCom.

Plain language An annual committee nominating candidates for Internet leadership positions.

Used in RFC 2027 RFC 2282 RFC 3777 RFC 7437 RFC 8714 RFC 8718 RFC 9389

Four zero-valued bytes placed before an IKE message so that it can be told apart from an ESP packet carried between the same addresses and ports.

Used in RFC 3947 RFC 9329

Evidence that lets someone prove a fact, such as that data existed at a certain time, so that it cannot credibly be denied later.

Plain language Evidence proving a fact such that it cannot credibly be denied later.

Used in RFC 2025 RFC 2479 RFC 2807 RFC 3039 RFC 3335 RFC 3552 RFC 4130 RFC 4810 RFC 4823 RFC 4998 RFC 5126

A random value used once. IKE peers exchange nonces so that keys and signatures are tied to this specific exchange and cannot be replayed.

Plain language A random value used once to tie exchanges to a specific session.

Used in RFC 1446 RFC 1731 RFC 1969 RFC 2006 RFC 2069 RFC 2409 RFC 2412 RFC 2419 RFC 2420 RFC 2510 RFC 2560 RFC 2617 RFC 2660 RFC 2759 RFC 2930 RFC 2943 RFC 2951 RFC 2985 RFC 3097 RFC 3118 RFC 3161 RFC 3168 RFC 3310 RFC 3540 and 225 more

A property of encryption schemes where catastrophic failure is avoided if a nonce is reused. Under reuse, only the equality of identical plaintexts is revealed.

Plain language An encryption scheme that resists compromise if a nonce is reused.

Used in RFC 5297 RFC 8452

The transformation of text to a standard form so that different character sequences representing the same visual string can be reliably compared for equivalence.

Plain language Converting text to a standard form for consistent comparison of different representations.

Used in RFC 3491 RFC 3536 RFC 4013 RFC 5198 RFC 5895 RFC 6365 RFC 6532 RFC 7997

A reference to a document that is essential to implementing or understanding an RFC. Other references, which only provide additional information, are called informative.

Plain language A reference to a document essential for implementing an RFC.

Used in RFC 4897 RFC 7322

An OSPF area that behaves like a stub area, keeping a small link state database, but that can import external routes from another autonomous system as Type-7 LSAs and pass selected ones on to the rest of the domain as Type-5 LSAs.

Plain language A small OSPF area that keeps a short route list but can still accept a few routes from outside the network and forward the ones that are marked for it.

Used in RFC 1587 RFC 1765 RFC 3101 RFC 5250

National Research and Education Network. A U.S. initiative starting in the 1980s to create high-speed networking infrastructure for research and education. The network evolved into the modern Internet.

Plain language A U.S. initiative to build high-speed networks for research and education.

Used in RFC 1167 RFC 1527

A Network Service Access Point address used in OSI networks to identify a computer and transport service, analogous to an IP address in the Internet.

Plain language An address format for OSI networks similar to an IP address.

Used in RFC 926 RFC 941 RFC 982 RFC 986 RFC 994 RFC 1069 RFC 1237 RFC 1238 RFC 1277 RFC 1301 RFC 1561 RFC 1608 RFC 1629 RFC 1637 RFC 1706 RFC 1932 RFC 4048

A 20-octet Open Systems Interconnection network address made of an Initial Domain Part and a Domain Specific Part.

Plain language A 20-byte OSI network address composed of domain and specific parts.

Used in RFC 941 RFC 982 RFC 995 RFC 1069 RFC 1277 RFC 1348 RFC 1574 RFC 1707 RFC 1888 RFC 4548

Next Secure. A signed record that links an existing name to the next one in canonical order and lists the types present, allowing authenticated proof that a name or type does not exist.

Plain language A signed DNS record proving that a name or record type does not exist.

Used in RFC 3755 RFC 3845 RFC 4033 RFC 4034 RFC 4035 RFC 4470 RFC 4471 RFC 4592 RFC 4956 RFC 4969 RFC 5074 RFC 5155 RFC 5702 RFC 5933 RFC 6605 RFC 6672 RFC 6781 RFC 6840 RFC 6841 RFC 6944 RFC 7129 RFC 7477 RFC 7646 RFC 8020 and 10 more

A DNSSEC record type that proves a name does not exist by chaining hashed names instead of clear-text names. It makes it harder to list all the names in a zone.

Plain language A DNSSEC record proving a name doesn't exist without exposing the zone contents.

Used in RFC 5155 RFC 6781 RFC 7646 RFC 8198 RFC 9276

Next Steps in Signaling, a framework for signaling protocols that allows applications to request network services such as QoS reservations across networks.

Plain language A framework allowing applications to request network services like quality guarantees.

Used in RFC 3726 RFC 5971 RFC 5973 RFC 5979 RFC 5980 RFC 5981 RFC 6084

A 64-bit time value with 32 bits of unsigned seconds and 32 bits of fraction, counted from 0 h on 1 January 1900 UTC. Era 0 ends in 2036 when the seconds field wraps.

Plain language A 64-bit time value counted from 1 January 1900 with high precision.

Used in RFC 957 RFC 958 RFC 1059 RFC 1305 RFC 1361 RFC 1769 RFC 2002 RFC 2030 RFC 2327 RFC 2626 RFC 2745 RFC 2783 RFC 3432 RFC 3520 RFC 3611 RFC 3643 RFC 4285 RFC 4330 RFC 4442 RFC 4656 RFC 4710 RFC 4712 RFC 4765 RFC 5450 and 36 more

The ability of a telecommunications customer to keep the same telephone number when changing service providers or location.

Plain language The ability to keep a telephone number when changing providers or location.

Used in RFC 3482 RFC 4694 RFC 4769

The DNS "Name Error" response code: the domain name asked about does not exist at all.

Plain language A DNS response indicating the domain name does not exist.

Used in RFC 1536 RFC 2136 RFC 2308 RFC 4074 RFC 5617 RFC 6303 RFC 6731 RFC 6761 RFC 7208 RFC 7686 RFC 8020 RFC 8198 RFC 8767 RFC 8914 RFC 9156 RFC 9476 RFC 9567 RFC 9660 RFC 9824