rfc-2514

Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management

M. Noto, E. Spiegel, K. Tesink
date1999-02 streamIETF areaops wgatommib statusPROPOSED STANDARD pages20 canonicalhttps://www.rfc-editor.org/rfc/rfc2514 doi10.17487/RFC2514
This memo describes Textual Conventions and OBJECT-IDENTITIES used for managing ATM-based interfaces, devices, networks and services. [STANDARDS-TRACK]

Extracted elements (25)

design-rationale §1

OBJECT-IDENTITIES for atmTrafficDescriptorTypes were moved from RFC 1695 to this specification to consolidate ATM textual conventions and OIDs in one place. The original OBJECT IDENTIFIERs were preserved to maintain backward compatibility with implementations referencing RFC 1695.

snmp

design-rationale §1

Textual conventions are defined separately from ATM-MIB (RFC 2515) so that multiple ATM MIB modules can import them from a single authoritative source. This avoids duplication and ensures consistent semantics across all ATM-related MIB modules.

snmp

interoperability-note §2

atmClpTransparentNoScr (type 9) and atmClpTransparentScr (type 10) connections will be rejected at UNI 3.0 or UNI 3.1 interfaces. Implementors targeting those interfaces should use atmNoClpNoScr (type 2) or atmNoClpScr (type 5) instead.

snmp

protocol-element §2

AtmAddr is a textual convention for ATM addresses. Address type is implied by length: 0 octets (no address), 8 octets (E.164), 20 octets (NSAP), or concatenated address+subaddress forms up to 40 octets. E.164 is BCD-encoded.

snmp

protocol-element §2

atmClpTaggingScr (type 7): Traffic descriptor with CLP tagging and SCR. Parameters include PCR (CLP=0+1), SCR for CLP=0 traffic (excess tagged as CLP=1), and maximum burst size.

snmp, qos

protocol-element §2

atmClpTaggingScrCdvt (type 15): Most complete traffic descriptor type, applicable to VBR.3 conformance. Parameters: PCR (CLP=0+1), SCR for CLP=0 with excess tagged as CLP=1, maximum burst size, and CDVT in tenths of microseconds.

snmp, qos

protocol-element §2

atmClpTransparentNoScr (type 9): CLP-transparent model without SCR, applicable to CBR.1 conformance. Connections using this type will be rejected at UNI 3.0 or UNI 3.1 interfaces; atmNoClpNoScr should be used instead for those interfaces.

snmp, qos

protocol-element §2

AtmConnCastType identifies the topology type of a connection: p2p(1) for point-to-point, p2mpRoot(2) when the host or interface is the root of a point-to-multipoint connection, p2mpLeaf(3) when it is a leaf.

snmp

protocol-element §2

AtmConnKind identifies the call-control type of an ATM virtual link: pvc(1), svcIncoming(2), svcOutgoing(3), spvcInitiator(4), or spvcTarget(5). PVC links cross-connect only to PVC links; SVC incoming always cross-connects to SVC outgoing.

snmp

protocol-element §2

AtmIlmiNetworkPrefix is used for ILMI address registration. For ATM endsystem addresses (AESAs), the prefix is the first 13 octets (AFI+IDI+HO-DSP). For native E.164 addresses, the prefix is the full 8-octet E.164 address encoded as if it were an E.164 IDP.

snmp

protocol-element §2

AtmInterfaceType enumerates connection setup procedures for ATM interfaces, including other(1), autoConfig(2), ituDss2(3), atmfUni3Dot0(4), atmfUni3Dot1(5), atmfUni4Dot0(6), IISP variants (7-9), atmfPnni1Dot0(10), atmfBici2Dot0(11), and PVC-only UNI/NNI (12-13).

snmp

protocol-element §2

atmNoClpNoScr (type 2): Traffic descriptor with peak cell rate (CLP=0+1) only; no CLP separation and no Sustained Cell Rate. Referenced by UNI 3.0 and 3.1 conformance definitions.

snmp, qos

protocol-element §2

atmNoClpScr (type 5): Traffic descriptor with peak cell rate (CLP=0+1), sustainable cell rate (CLP=0+1), and maximum burst size. No CLP separation and no tagging.

snmp, qos

protocol-element §2

AtmServiceCategory specifies the QoS service category for an ATM connection: other(1), cbr(2) constant bit rate, rtVbr(3) real-time VBR, nrtVbr(4) non-real-time VBR, abr(5) available bit rate, ubr(6) unspecified bit rate.

snmp, qos

protocol-element §2

AtmSigDescrParamIndex is an INTEGER (0..2147483647) identifying a row in atmSigDescrParamTable; value 0 means no signalling parameters from that table apply.

snmp

protocol-element §2

AtmTrafficDescrParamIndex is an INTEGER (0..2147483647) identifying a row in atmTrafficDescrParamTable; value 0 means no row has been identified.

snmp

protocol-element §2

AtmVcIdentifier encodes the VCI for a VCL as INTEGER (0..65535). The actual maximum is further constrained by atmInterfaceMaxVciBits defined in ATM-MIB.

snmp

protocol-element §2

AtmVorXAdminStatus indicates the desired administrative state of a virtual link or cross-connect: up(1) enables traffic flow, down(2) disables it.

snmp

protocol-element §2

AtmVorXLastChange records the value of sysUpTime when a virtual link or cross-connect entered its current operational state. Returns zero if the current state was entered before the last agent re-initialization.

snmp

protocol-element §2

AtmVorXOperStatus indicates the operational state of a virtual link or cross-connect: up(1), down(2), or unknown(3). The state is down or unknown if the supporting ATM interface(s) is down or unknown respectively.

snmp

protocol-element §2

AtmVpIdentifier encodes the VPI for a VPL or VCL. VPI=0 is only allowed for a VCL. UNI VPI ranges 0-255; NNI VPI ranges 0-4095. The maximum is further constrained by atmInterfaceMaxVpiBits defined in ATM-MIB.

snmp

registry §2

The atmTrafficDescriptorTypes subtree (mib-2 37 1 1) registers OBJECT-IDENTITIES for ATM traffic descriptor types. This document defines types 1-15 under that subtree, covering no-descriptor through CLP-with-tagging-SCR-CDVT variants.

snmp, registry

security-consideration §5

This memo only defines textual conventions and object identities for use in ATM MIB modules; it does not itself introduce management operations. Security issues are deferred to the memos defining the specific MIB modules that use these constructs.

snmp, security

wire-format §2

AtmAddr SYNTAX is OCTET STRING (SIZE 0..40). E.164 addresses are 8 octets in BCD format; NSAP addresses are 20 octets; concatenated pairs (E.164+E.164, E.164+NSAP, NSAP+NSAP) are 16, 28, and 40 octets respectively.

snmp

wire-format §2

AtmIlmiNetworkPrefix SYNTAX is OCTET STRING (SIZE 8|13), encoding either an 8-octet native E.164 network prefix or a 13-octet AESA prefix covering AFI, IDI, and HO-DSP fields.

snmp