RFC 2619
RADIUS Authentication Server MIB
RFC 2619: RADIUS Authentication Server MIB 🎀
okay bestie, let's get into this one 💅 It's a Standards Track doc from the Network Working Group, dated June 1999. The authors are G. Zorn and B. Aboba, both from Microsoft 🦋 The header doesn't list any "Obsoletes" or "Updates" lines, so this one doesn't replace or modify another RFC.
Status of this Memo
Okay so this doc is an Internet standards track protocol for the whole Internet community, and it's basically asking everyone to talk about it and suggest improvements 🗣️✨ If you want to know where it stands officially, check the current edition of the "Internet Official Protocol Standards" (STD 1) 📜 And yes, you're allowed to share it as much as you like, since distribution is unlimited 🌸
Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. 💜
Abstract
This memo is all about adding extensions that instrument RADIUS authentication server functions 📊 These extensions are part of the Management Information Base (MIB), which network management protocols use. With them, IP-based management stations can manage RADIUS authentication servers, which is so useful 🔥
1. Introduction ✨
This memo defines a piece of the Management Information Base (MIB) that network management protocols in the Internet community use. Specifically, it describes the managed objects you use to manage RADIUS authentication servers 🎀
RADIUS authentication servers are everywhere now, especially with dialup Internet Service Providers that use them to provide authentication services 🌈 Because they're so widely deployed, managing them well is a really big deal 👑
2. The SNMP Management Framework 🧚
The SNMP Management Framework is currently made up of five major components 💅
- An overall architecture, described in RFC 2571 [1].
- Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and is described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in STD 58, RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7].
- Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and is described in STD 15, RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and is described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and is described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12].
- Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13].
- A set of fundamental applications described in RFC 2573 [14] and the view-based access control mechanism described in RFC 2575 [15].
Managed objects are accessed through a virtual information store called the Management Information Base, or MIB 🗂️ Objects in the MIB are defined using the mechanisms in the SMI.
This memo specifies a MIB module that is compliant to SMIv2 🎯 A MIB conforming to SMIv1 can be produced through the appropriate translations. The translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be turned into textual descriptions in SMIv1 during the translation process. Still, losing that machine readable information is not considered to change the semantics of the MIB 🫶
3. Overview 🦋
The RADIUS authentication protocol, described in [16], splits things into a client function and a server function. In RADIUS authentication, clients send Access-Requests, and servers reply with Access-Accepts, Access-Rejects, and Access-Challenges 💜 Usually, NAS devices implement the client function, so they would be expected to implement the RADIUS authentication client MIB. RADIUS authentication servers implement the server function, so they would be expected to implement the RADIUS authentication server MIB 🌸
That said, a single RADIUS authentication entity can do both client and server functions 🔥 For example, a RADIUS proxy might act as a server to one or more RADIUS authentication clients while also acting as an authentication client to one or more authentication servers. In those situations, RADIUS entities that combine client and server functionality are expected to support both the client and server MIBs 👑
3.1. Selected objects 🍓
This MIB module contains fourteen scalars as well as a single table 📋
- The RADIUS Authentication Client Table contains one row for each RADIUS authentication client that the server shares a secret with.
Each entry in the RADIUS Authentication Client Table includes twelve columns presenting a view of the activity of the RADIUS authentication server ✨
4. Definitions 💖
RADIUS-AUTH-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Integer32,
IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
radiusAuthServMIB MODULE-IDENTITY
LAST-UPDATED "9906110000Z"
ORGANIZATION "IETF RADIUS Working Group."
CONTACT-INFO
" Bernard Aboba
Microsoft
One Microsoft Way
Redmond, WA 98052
US
Phone: +1 425 936 6605
EMail: bernarda@microsoft.com"
DESCRIPTION
"The MIB module for entities implementing the server
side of the Remote Access Dialin User Service (RADIUS)
authentication protocol."
REVISION "9906110000Z" -- 11 Jun 1999
DESCRIPTION "Initial version as published in RFC 2619"
::= { radiusAuthentication 1 }
radiusMIB OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA."
::= { mib-2 67 }
radiusAuthentication OBJECT IDENTIFIER ::= {radiusMIB 1}
radiusAuthServMIBObjects OBJECT IDENTIFIER ::=
{ radiusAuthServMIB 1 }
radiusAuthServ OBJECT IDENTIFIER ::= { radiusAuthServMIBObjects 1 }
radiusAuthServIdent OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The implementation identification string for the
RADIUS authentication server software in use on the
system, for example; `FNS-2.1'"
::= {radiusAuthServ 1}
radiusAuthServUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the server has a persistent state (e.g., a process),
this value will be the time elapsed (in hundredths of a
seco) since the server process was started.
For software without persistent state, this value will
be zero."
::= {radiusAuthServ 2}
radiusAuthServResetTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the server has a persistent state (e.g., a process)
and supports a `reset' operation (e.g., can be told to
re-read configuration files), this value will be the
time elapsed (in hundredths of a second) since the
server was `reset.' For software that does not
have persistence or does not support a `reset' operation,
this value will be zero."
::= {radiusAuthServ 3}
radiusAuthServConfigReset OBJECT-TYPE
SYNTAX INTEGER { other(1),
reset(2),
initializing(3),
running(4)}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Status/action object to reinitialize any persistent
server state. When set to reset(2), any persistent
server state (such as a process) is reinitialized as if
the server had just been started. This value will
never be returned by a read operation. When read, one of
the following values will be returned:
other(1) - server in some unknown state;
initializing(3) - server (re)initializing;
running(4) - server currently running."
::= {radiusAuthServ 4}
-- New Stats proposed by Dale E. Reed Jr (daler@iea-software.com)
radiusAuthServTotalAccessRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received on the
authentication port."
::= { radiusAuthServ 5}
radiusAuthServTotalInvalidRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Access-Request packets
received from unknown addresses."
::= { radiusAuthServ 6 }
radiusAuthServTotalDupAccessRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of duplicate RADIUS Access-Request
packets received."
::= { radiusAuthServ 7 }
radiusAuthServTotalAccessAccepts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Access-Accept packets sent."
::= { radiusAuthServ 8 }
radiusAuthServTotalAccessRejects OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Access-Reject packets sent."
::= { radiusAuthServ 9 }
radiusAuthServTotalAccessChallenges OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Access-Challenge packets sent."
::= { radiusAuthServ 10 }
radiusAuthServTotalMalformedAccessRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of malformed RADIUS Access-Request
packets received. Bad authenticators
and unknown types are not included as
malformed Access-Requests."
::= { radiusAuthServ 11 }
radiusAuthServTotalBadAuthenticators OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Authentication-Request packets
which contained invalid Signature attributes received."
::= { radiusAuthServ 12 }
radiusAuthServTotalPacketsDropped OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of incoming packets
silently discarded for some reason other
than malformed, bad authenticators or
unknown types."
::= { radiusAuthServ 13 }Okay bestie, the next bit is where the MIB really shows off. 🦋 The radiusAuthServTotalUnknownTypes counter comes first, then the big client table (the per-NAS stats) and all the conformance stuff at the bottom. Let's go ✨
radiusAuthServTotalUnknownTypes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets of unknown type which
were received."
::= { radiusAuthServ 14 }
-- End of new
radiusAuthClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAuthClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the RADIUS authentication
clients with which the server shares a secret."
::= { radiusAuthServ 15 }
radiusAuthClientEntry OBJECT-TYPE
SYNTAX RadiusAuthClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) representing a RADIUS
authentication client with which the server shares a
secret."
INDEX { radiusAuthClientIndex }
::= { radiusAuthClientTable 1 }
RadiusAuthClientEntry ::= SEQUENCE {
radiusAuthClientIndex Integer32,
radiusAuthClientAddress IpAddress,
radiusAuthClientID SnmpAdminString,
radiusAuthServAccessRequests Counter32,
radiusAuthServDupAccessRequests Counter32,
radiusAuthServAccessAccepts Counter32,
radiusAuthServAccessRejects Counter32,
radiusAuthServAccessChallenges Counter32,
radiusAuthServMalformedAccessRequests Counter32,
radiusAuthServBadAuthenticators Counter32,
radiusAuthServPacketsDropped Counter32,
radiusAuthServUnknownTypes Counter32
}
radiusAuthClientIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A number uniquely identifying each RADIUS
authentication client with which this server
communicates."
::= { radiusAuthClientEntry 1 }
radiusAuthClientAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAS-IP-Address of the RADIUS authentication client
referred to in this table entry."
::= { radiusAuthClientEntry 2 }
radiusAuthClientID OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAS-Identifier of the RADIUS authentication client
referred to in this table entry. This is not necessarily
the same as sysName in MIB II."
::= { radiusAuthClientEntry 3 }
-- Server Counters
--
-- Responses = AccessAccepts + AccessRejects + AccessChallenges
--
-- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped - Responses = Pending
--
-- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped = entries logged
radiusAuthServAccessRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received on the authentication
port from this client."
::= { radiusAuthClientEntry 4 }
radiusAuthServDupAccessRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of duplicate RADIUS Access-Request
packets received from this client."
::= { radiusAuthClientEntry 5 }
radiusAuthServAccessAccepts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Access-Accept packets
sent to this client."
::= { radiusAuthClientEntry 6 }
radiusAuthServAccessRejects OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Access-Reject packets
sent to this client."
::= { radiusAuthClientEntry 7 }
radiusAuthServAccessChallenges OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Access-Challenge packets
sent to this client."
::= { radiusAuthClientEntry 8 }
radiusAuthServMalformedAccessRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of malformed RADIUS Access-Request
packets received from this client.
Bad authenticators and unknown types are not included as
malformed Access-Requests."
::= { radiusAuthClientEntry 9 }
radiusAuthServBadAuthenticators OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Authentication-Request packets
which contained invalid Signature attributes received
from this client."
::= { radiusAuthClientEntry 10 }
radiusAuthServPacketsDropped OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of incoming packets from this
client silently discarded for some reason other
than malformed, bad authenticators or
unknown types."
::= { radiusAuthClientEntry 11 }
radiusAuthServUnknownTypes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets of unknown type which
were received from this client."
::= { radiusAuthClientEntry 12 }
-- conformance information
radiusAuthServMIBConformance
OBJECT IDENTIFIER ::= { radiusAuthServMIB 2 }
radiusAuthServMIBCompliances
OBJECT IDENTIFIER ::= { radiusAuthServMIBConformance 1 }
radiusAuthServMIBGroups
OBJECT IDENTIFIER ::= { radiusAuthServMIBConformance 2 }
-- compliance statements
radiusAuthServMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for authentication servers
implementing the RADIUS Authentication Server MIB."
MODULE -- this module
MANDATORY-GROUPS { radiusAuthServMIBGroup }
OBJECT radiusAuthServConfigReset
WRITE-SYNTAX INTEGER { reset(2) }
DESCRIPTION "The only SETable value is 'reset' (2)."
::= { radiusAuthServMIBCompliances 1 }
-- units of conformance
radiusAuthServMIBGroup OBJECT-GROUP
OBJECTS {radiusAuthServIdent,
radiusAuthServUpTime,
radiusAuthServResetTime,
radiusAuthServConfigReset,
radiusAuthServTotalAccessRequests,
radiusAuthServTotalInvalidRequests,
radiusAuthServTotalDupAccessRequests,
radiusAuthServTotalAccessAccepts,
radiusAuthServTotalAccessRejects,
radiusAuthServTotalAccessChallenges,
radiusAuthServTotalMalformedAccessRequests,
radiusAuthServTotalBadAuthenticators,
radiusAuthServTotalPacketsDropped,
radiusAuthServTotalUnknownTypes,
radiusAuthClientAddress,
radiusAuthClientID,
radiusAuthServAccessRequests,
radiusAuthServDupAccessRequests,
radiusAuthServAccessAccepts,
radiusAuthServAccessRejects,
radiusAuthServAccessChallenges,
radiusAuthServMalformedAccessRequests,
radiusAuthServBadAuthenticators,
radiusAuthServPacketsDropped,
radiusAuthServUnknownTypes
}
STATUS current
DESCRIPTION
"The collection of objects providing management of
a RADIUS Authentication Server."
::= { radiusAuthServMIBGroups 1 }
END5. References 📚
Here's the reading list, all the refs the spec leans on, with every detail kept. It's giving bibliography energy 💅
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[2] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model for Version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", RFC 2573, April 1999.
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[16] Rigney, C., Rubens, A., Simpson W. and S. Willens, "Remote Authentication Dial In User Service (RADIUS)", RFC 2138, April 1997.
6. Security Considerations 🔐💅
Okay bestie, security is where things get dramatic 😭 Quick heads up: a bunch of the objects in this MIB have a MAX-ACCESS clause of read-write and/or read-create. Those are the ones that can be sensitive or vulnerable in some network environments. Doing SET operations in a non-secure environment without proper protection can seriously mess with network operations 💀
There are also some managed objects in this MIB that can hold sensitive info:
radiusAuthClientAddress: This can be used to figure out the address of the RADIUS authentication client that the server is talking to. That info could be super useful for impersonating the client 👀radiusAuthClientID: This can be used to find the client ID of the authentication client that the server is talking to. That could also be used for impersonating the client 🙈
So it's really important to control even GET access to these objects, and maybe even encrypt their values when they go over the network via SNMP. Not every version of SNMP has features for a secure environment, so keep that in mind 🫶
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (like if you're using IPSec), there's no control over who on that secure network can GET or SET (read, change, create, delete) the objects in this MIB. Not it, SNMPv1 🙅♀️
Implementers should seriously consider the security features that come with the SNMPv3 framework. Specifically, the User-based Security Model (RFC 2574 [12]) and the View-based Access Control Model (RFC 2575 [15]) are recommended. With these features, customers and users can give access to the objects only to the principals (users) who legitimately have the right to GET or SET (change, create, delete) them. Main character security energy ✨
7. Acknowledgments 🫶🎀
The authors shout out the RADIUS Working Group for helping develop this MIB, which is so sweet 🥹 They also thank Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT, Carl Rigney of Livingston, and Peter Heitman of American Internet Corporation for the useful discussions about this problem space 🌸
8. Authors' Addresses 💌
Here's where you can find the authors, the real ones 🦋
Bernard Aboba
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
Phone: 425-936-6605
EMail: bernarda@microsoft.comGlen Zorn
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
Phone: 425-703-1559
EMail: glennz@microsoft.com9. Intellectural Property Statement ⚖️
Okay, legal bit, but it's important 🧚 The IETF takes no position on whether any intellectual property or other rights that might be claimed to apply to the implementation or use of the technology in this document are valid or in scope. It also doesn't say whether licenses under those rights might or might not be available, and it doesn't claim to have tried to identify any such rights. You can find info about the IETF's procedures for rights in standards-track and standards-related documentation in BCP-11. Copies of claims of rights made available for publication, and any assurances of licenses to be made available, or the result of an attempt to get a general license or permission for implementors or users to use such proprietary rights, can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any copyrights, patents, patent applications, or other proprietary rights that may cover technology required to practice this standard. Send that info to the IETF Executive Director.
10. Full Copyright Statement 📜🌈
Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implmentation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement 💖
Funding for the RFC Editor function is currently provided by the Internet Society. Thank you for reading the whole thing with me, bestie 🌸✨
📦 where this page comes from
- ietf: rfc2619 1999-06
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms