RFC relevance of extended

As per Relevance of the word extended, we have this rfc below:

Network Working Group B.
Request for Comments: 2457 Cisco
Category: Standards Track B.
IBM
November 1998

Definitions of Managed
for Extended Border

Status of this

This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited

Copyright

Copyright (C) The Internet Society (1998). All Rights Reserved

This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it defines objects for monitoring and
network devices with APPN (Advanced Peer-to-Peer Network)
(Extended Border Node) capabilities. This memo identifies
objects for the EBN architecture

Table of

1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . 2
3.0 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1 EBN MIB Structure . . . . . . . . . . . . . . . . . . . . 4
3.1.1 enbDir group . . . . . . . . . . . . . . . . . . . . . 5
3.1.2 ebnIsRscv group . . . . . . . . . . . . . . . . . . . 5
3.1.3 ebnDirConfig group . . . . . . . . . . . . . . . . . . 7
3.1.4 ebnCos group . . . . . . . . . . . . . . . . . . . . . 8
3.1.5 ebnSubnetRoutingList group . . . . . . . . . . . . . . 8
3.1.6 hbn group . . . . . . . . . . . . . . . . . . . . . . 8
4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . 9
5.0 Security Considerations . . . . . . . . . . . . . . . . . 24
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . 25
7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . 25
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . 25

Clouston & Moore Standards Track [Page 1]

RFC 2457 Extended Border Node MIB November 1998

9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 27
10.0 Full Copyright Statement . . . . . . . . . . . . . . . . 28

1.0

This document is a product of the SNA NAU Services MIB Working Group
It defines a MIB module for managing devices with Advanced Peer-to
Peer Networking (APPN) Extended Border Node (EBN) capabilities

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
document are to be interpreted as described in RFC 2119,
[13].

2.0 The SNMP Network Management

The SNMP Network Management Framework presently consists of six
components. They are

o the overall architecture, described in RFC 2271 [7].

o the SMI, described in RFC 1902 [3], - the mechanisms used
describing and naming objects for the purpose of management

o the MIB-II, STD 17, RFC 1213 [2], - the core set of
objects for the Internet suite of protocols

o the protocol, STD 15, RFC 1157 [1] and/or RFC 1905 [6] and/or
2272 [8] -- the protocol for accessing managed information

o the user-based security model defined in RFC 2274 [10].

o the view-based access control model defined in RFC 2275 [11].

Textual conventions are defined in RFC 1903 [4], and
statements are defined in RFC 1904 [5]. Common applications
defined in RFC 2273 [9].

The Framework permits new objects to be defined for the purpose
experimentation and evaluation

This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translation

Clouston & Moore Standards Track [Page 2]

RFC 2457 Extended Border Node MIB November 1998

3.0

This document identifies the proposed set of objects for
the configuration and active characteristics of devices with
capabilities. The Extended Border Node function is an
enhancement for an APPN network node (NN). It supports
isolation, subnet interconnection, and session establishment
subnets

In a single APPN network, all network topology information
propagated to all network nodes. Directory searches can also
forwarded to all network nodes. As the network grows, this
traffic could become prohibitive. Also, in networks where
enterprises are connected via APPN, it may be desirable to shield
enterprise from the network traffic of another enterprise.
allow customers to partition a network into subnets to reduce
shield such network traffic

An EBN provides this function by blocking topology
exchange between subnets, and controlling where directory
are forwarded. A subnetwork is a cluster of APPN NNs which share
same network topology. Subnetwork boundaries, or partitions,
where an EBN and an NN adjacent to it have different
identifiers (NETIDs). They may also occur where an EBN and
NN have the same NETID but are configured to have a
boundary

The connection between two APPN nodes is an APPN transmission
(TG). A TG at a subnet boundary is called an
Transmission Group (ISTG).

The subnet in which an EBN resides is called its native subnetwork
The subnet across the subnet boundary is called the non-
subnetwork, with respect to the EBN

A cost of the EBN function is that customers may have
determining the end-to-end route of sessions that cross
boundaries, and understanding how the EBN will control
searches between subnets. This MIB addresses these issues

Another challenge facing customers is to identify subnet
formed by EBNs. The SNANAU APPN MIB [14] identifies
boundaries in the appnNnTopology group. The SNANAU APPN MIB
management of APPN objects, and contains some tables that
extended by this MIB

In this document, we describe EBN managed objects

Clouston & Moore Standards Track [Page 3]

RFC 2457 Extended Border Node MIB November 1998

The EBN terms and overall architecture are available from
networking.raleigh.ibm.com ftp site [15].

Highlights of the management functions supported by the EBN
module include the following

o Identifying the subnet affiliation of LUs (logical units

o Identifying session routes in non-native subnets,
correlation to the route in the native subnet provided in
SNANAU APPN MIB

o Identifying the COS (Class of Service) mappings between subnets

o Identifying the subnet routing

This MIB module does not support

o Configuration of EBN nodes

o Historical information about session initiation failures

o Peripheral Border Node (PBN) support. PBN is an APPN
that only supports communication to adjacent subnetworks, and
not expected to be widely implemented

o Traps. The APPN MIB contains a trap for Alert conditions
may affect EBN resources. Although no APPN/EBN Alerts
defined today in the APPN MIB [14], they could exist in
future. The value for the affectedObject object contained in
alertTrap is determined by the implementation. It may contain
VariablePointer from the EBN MIB

3.1 EBN MIB

The EBN MIB module contains the following groups of objects

o ebnDir - subnet information about LUs

o ebnIsRscv - provides the RSCV (Route Selection
Vector) and COS for the subnetwork on the BIND destination
of the EBN

o ebnDirConfig - objects related to the EBN directory

o ebnCos - COS mapping between subnetworks

Clouston & Moore Standards Track [Page 4]

RFC 2457 Extended Border Node MIB November 1998

o ebnSubnetRoutingList - the customer-supplied list of where
forward search requests

o hbn - HPR (High Performance Routing) EBN intermediate
information

These groups are described below in more detail

3.1.1 enbDir

The ebnDir group contains the ebnDirTable, which is an extension
the appnDirTable. It specifies the subnet affiliation of LUs in
EBN's directory

3.1.2 ebnIsRscv

The ebnIsRscv group contains the ebnIsRscvTable, which is
extension to the appnIsInTable. The appnIsInTable only allows
the RSCV and COS name for one subnetwork traversed by a session
This extension contains the RSCV and COS name for the
subnetwork

When an EBN changes RSCVs before forwarding a BIND,
contains the incoming RSCV, and ebnIsRscvDestinationRoute
the outgoing RSCV

The following three cases illustrate the contents
appnIsInRouteInfo and ebnIsRscvDestinationRoute at Extended
Nodes

1. EBN connected to another

**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 EBN
PLU
---------------------------->|
(1) |--------------->|
(2) |---------->
(3)

PLU = Primary Logical Unit (session initiator
SLU = Secondary Logical Unit (session destination

The value of the appnIsInRouteInfo object at EBN1 is the
containing the route, represented by (1), from the PLU (or
entry EBN in its subnet) to EBN2. The value
ebnIsRscvDestinationRoute object at EBN1 is the RSCV,
by (2), containing the one-hop route from EBN1 to EBN2.

Clouston & Moore Standards Track [Page 5]

RFC 2457 Extended Border Node MIB November 1998

appnIsInRouteInfo object at EBN2 also contains the
represented by (2). The value of ebnIsRscvDestinationRoute
EBN2 is the RSVC containing the route to the SLU (or to the
subnet's entry EBN), represented by (3).

2. EBN connected to a NN or

**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 NN/
PLU
---------------------------->|
(1) |--------------------------->
(2)

The value of the appnIsInRouteInfo object at EBN1 is the
containing the route from the PLU (or the entry EBN in
subnet) to the NN or PBN, represented by (1). The value of
ebnIsRscvDestinationRoute object at EBN1 is the RSCV
the route from EBN1 to the SLU, represented by (2). Note
the SLU must be in subnet 2, because the entry node is an NN
PBN rather than an EBN. The appnIsInRouteInfo object at NN/
contains the same RSCV, as represented by (2).

3. NN or PBN connected to

**subnet 1**|-----ISTG ------|**subnet 2**
NN/PBN EBN
PLU
---------------------------->|
(1) |---------->
(2)

The value of the appnIsInRouteInfo object at the NN/PBN is
RSCV containing the route from the PLU to EBN1, represented
(1). Note that the PLU must be in subnet 1, because the
node is an NN/PBN rather than an EBN. The
object at EBN1 contains the same RSCV. The value of
ebnIsRscvDestinationRoute object at EBN1 is the RSCV
the route from EBN1 to the SLU (or the next subnet's entry
node), as represented by (2).

The following three cases illustrate the contents
ebnIsRscvDestinationCos at Extended Border Nodes

Clouston & Moore Standards Track [Page 6]

RFC 2457 Extended Border Node MIB November 1998

1. EBN connected to another

**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 EBN
PLU
COS
---------------------------->|
COS
|---------->

PLU = Primary Logical Unit (session initiator
SLU = Secondary Logical Unit (session destination

The value of ebnIsRscvDestinationCos object at EBN1 is COS A
The value of ebnIsRscvDestinationCos object at EBN2 is COS B

2. EBN connected to a NN or

**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 NN/
PLU
COS
----------->|
COS
|--------------------------->

The value of the ebvIsRscvDestinationCos object at EBN1 is COS B

3. NN or PBN connected to

**subnet 1**|-----ISTG ------|**subnet 2**
NN/PBN EBN
PLU
COS
---------------------------->|
COS
|---------->

The value of the ebnIsRscvDestinationCos object at the EBN2
COSB

3.1.3 ebnDirConfig

The ebnDirConfig group consists of simple objects that provide EBN
specific information about directory caching and the local
value for the maximum number of subnetworks a LOCATE search
may traverse

Clouston & Moore Standards Track [Page 7]

RFC 2457 Extended Border Node MIB November 1998

3.1.4 ebnCos

The ebnCos group contains the ebnCosMapTable, which specifies how
values are mapped between the non-native subnetwork and the
subnetwork

3.1.5 ebnSubnetRoutingList

The ebnSubnetRoutingList group contains information about
customer-supplied EBN subnetwork routing list, which indicates
which adjacent nodes an EBN will forward LOCATE search requests.
consists of the following tables

1.

This table has an entry for each LU name that has a
subnet routing list. The LU name may identify a single LU, or
may contain a wildcard character that could identify a group
LUs (partial wildcard) or all LUs (full wildcard). The
in the table indicate whether the EBN may add dynamic entries
the subnet routing list, and whether the subnet routing
entries may be reordered for better search performance

2.

This table has an entry for each control point name which
included in a multi-subnet search for a particular LU name.
index to the table is the LU name to be searched for, and
index which lists the order in which the CP names are to
searched. Both the CP name and the LU name entries in the
allow for partial and full wildcards. The CP name also
for special entries that indicate that the EBN will
itself and its own native subnetwork at this point in the search
or will search all native EBNs

3.1.6 hbn

The hbn group contains information about HBN (HPR EBN)
sessions. The hbnIsInTable is an extension to the appnIsInTable
This table is present for intermediate sessions when there are back
to-back RTP (Rapid Transport Protocol) connections in an HBN.
provides the NCE ID (network connection endpoint identifier) and
(transport connection identifier) for the second RTP connection

Clouston & Moore Standards Track [Page 8]

RFC 2457 Extended Border Node MIB November 1998

4.0

EBN-MIB DEFINITIONS ::=

MODULE-IDENTITY, OBJECT-TYPE, Unsigned32
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-
DisplayString, TEXTUAL-
FROM SNMPv2-

-- Because the characters allowed in an SNA
-- point name come from a restricted character set
-- these names are not subject to internationalization
FROM APPN-

FROM SNA-NAU-MIB

ebnMIB MODULE-
LAST-UPDATED "9804281800Z" -- April 28, 1998
ORGANIZATION "IETF SNA NAU MIB WG / AIW APPN MIBs SIG
CONTACT-
"
Bob
Cisco
7025 Kit Creek
P.O. Box 14987
Research Triangle Park, NC 27709,
Tel: 1 919 472 2333
E-mail: clouston@cisco.

Bob
IBM
BRQA/501
P.O. Box 12195
Research Triangle Park, NC 27709,
Tel: 1 919 254 4436
E-mail: remoore@us.ibm.
"

" The MIB Module for Extended Border Node

::= { snanauMIB 7 }

-- snanauMIB ::= { mib-2 34 }

Clouston & Moore Standards Track [Page 9]

RFC 2457 Extended Border Node MIB November 1998

-- ******************************************************************
-- Textual
-- ------------------------------------------------------------------
SnaNAUWildcardName ::= TEXTUAL-
STATUS

"Fully-qualified network NAU name. Entries take one of
forms
- Explicit entries do not contain the character '*'.
- Partial Wildcard entries have the form 'ccc*',
'ccc' represents one to sixteen characters in a
SNA NAU Name
- A full wildcard consists of a single character '*'.

Because the characters allowed in an SNA NAU name come
a restricted character set, these names are not subject
internationalization."

SYNTAX DisplayString(SIZE(1..17))

-- ******************************************************************
ebnObjects OBJECT IDENTIFIER ::= { ebnMIB 1 }
-- ******************************************************************

-- ******************************************************************
-- EBN Directory
-- The ebnDirTable is an extension to the appnDirTable. It
-- the subnet affiliation for LUs in the EBN's directory
-- ******************************************************************

ebnDir OBJECT IDENTIFIER ::= { ebnObjects 1 }

ebnDirTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The EBN Directory Table. This table is an
to the APPN MIB's appnDirTable. Entries in this
are in one-to-one correspondence with entries in
appnDirTable, with corresponding entries having
values for their respective indexes."

::= { ebnDir 1 }

ebnDirEntry OBJECT-
SYNTAX
MAX-ACCESS not-

Clouston & Moore Standards Track [Page 10]

RFC 2457 Extended Border Node MIB November 1998

STATUS

"Entry in the EBN Directory Table."

INDEX { ebnDirLuName }

::= { ebnDirTable 1 }

EbnDirEntry ::= SEQUENCE {
ebnDirLuName SnaNAUWildcardName
ebnDirSubnetAffiliation INTEGER }

ebnDirLuName OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"Fully qualified network LU name in the domain of a
network node. If this object has the same value as
appnDirLuName object in the APPN MIB, then the two
are referring to the same LU."

::= { ebnDirEntry 1 }

ebnDirSubnetAffiliation OBJECT-
SYNTAX INTEGER { native (1),
nonNative (2),
subarea (3) }
MAX-ACCESS read-
STATUS

"Specifies the subnetwork affiliation of the LU
- native(1) : The LU is in the native APPN subnetwork
- nonNative(2) : The LU is in a non-native APPN subnetwork
- subarea(3) : The LU is in a subarea network."

::= { ebnDirEntry 2 }

-- ******************************************************************
-- EBN Intermediate Session RSCV
-- This table is a sparse extension to the appnIsInTable.
-- sessions crossing ISTGs adjacent to the EBN, it contains the
-- and COS used in the direction of the BIND destination
-- ******************************************************************

ebnIsRscv OBJECT IDENTIFIER ::= { ebnObjects 2 }

ebnIsRscvTable OBJECT-

Clouston & Moore Standards Track [Page 11]

RFC 2457 Extended Border Node MIB November 1998

SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The EBN Intermediate Session RSCV table. This table is
extension to the appnIsInTable. It contains the RSCV and
used in the direction of the BIND destination. There is
entry in this table for each session that traverses an
when it enters or leaves this EBN, with corresponding
having identical values for their respective indexes."

::= { ebnIsRscv 1}

ebnIsRscvEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"Entry in ebnIsRscvTable."
INDEX { ebnIsRscvCpName
ebnIsRscvPcid }

::= { ebnIsRscvTable 1 }

EbnIsRscvEntry ::= SEQUENCE {
ebnIsRscvCpName SnaControlPointName
ebnIsRscvPcid OCTET STRING
ebnIsRscvDestinationRoute OCTET STRING
ebnIsRscvDestinationCos DisplayString }

ebnIsRscvCpName OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The network-qualified control point name of the node
which the session and PCID originated. For APPN and
nodes, this is either CP name of the APPN node at
the origin LU is located or the CP name of the NN
the LEN node at which the origin LU is located. For
resources it is the name of the owning SSCP

If this object has the same value as the
object in the APPN MIB, then the two objects are referring
the same APPN control point."

::= { ebnIsRscvEntry 1 }

Clouston & Moore Standards Track [Page 12]

RFC 2457 Extended Border Node MIB November 1998

ebnIsRscvPcid OBJECT-
SYNTAX OCTET STRING (SIZE (8))
MAX-ACCESS not-
STATUS

"The procedure correlation identifier (PCID) of a session
It is an 8-octet value

If this object has the same value as the appnIsInPcid
in the APPN MIB, and if the corresponding
object has the same value as the
appnIsInFqCpName object, then the entries indexed by
objects are referring to the same session."

::= { ebnIsRscvEntry 2 }

ebnIsRscvDestinationRoute OBJECT-
SYNTAX OCTET STRING(SIZE (0..255))
MAX-ACCESS read-

STATUS

"The route selection control vector (RSCV x'2B') used in
direction towards the SLU."

::= { ebnIsRscvEntry 3 }

ebnIsRscvDestinationCos OBJECT-
SYNTAX DisplayString (SIZE (1..8))
MAX-ACCESS read-
STATUS

"The Class of Service (COS) name used in the
towards the SLU

Because the characters allowed in an SNA COS name come
a restricted character set, these names are not subject
internationalization."

::= { ebnIsRscvEntry 4 }

-- ******************************************************************
-- EBN Directory Config
-- The following simple objects provide information about
-- directory
-- ******************************************************************

ebnDirConfig OBJECT IDENTIFIER ::= { ebnObjects 3 }

Clouston & Moore Standards Track [Page 13]

RFC 2457 Extended Border Node MIB November 1998

ebnSearchCacheTime OBJECT-
SYNTAX Unsigned32
UNITS "minutes
MAX-ACCESS read-
STATUS

"The amount of time in minutes an extended border node
retain information about a multi-subnetwork search,
that that search terminates. A value 0 indicates that
EBN has no defined limit, and the number of entries
bounded only by memory."

::= { ebnDirConfig 1 }

ebnMaxSearchCache OBJECT-
SYNTAX Unsigned32
UNITS "entries
MAX-ACCESS read-
STATUS

"The maximum number of multi-subnet entries to be cached
The value 0 indicates that the local node has no
limit, and the number of entries is bounded only
memory."

::= { ebnDirConfig 2 }

ebnDefaultSubnetVisitCount OBJECT-
SYNTAX Unsigned32
UNITS "topology subnetworks
MAX-ACCESS read-
STATUS

"The default maximum number of subnetworks a LOCATE
procedure may traverse."

::= { ebnDirConfig 3 }

-- ******************************************************************
-- EBN COS Mapping
-- The ebnCosMap Table specifies how non-native COS values are
-- to COS values defined in the native subnetwork. The COS
-- that an EBN performs are determined by multiple factors, one
-- which is a set of user-defined mappings. This table returns
-- COS mappings that the EBN is actually performing, rather
-- the user-defined mappings
-- ******************************************************************

Clouston & Moore Standards Track [Page 14]

RFC 2457 Extended Border Node MIB November 1998

ebnCOS OBJECT IDENTIFIER ::= { ebnObjects 4 }

ebnCosMapTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The EBN COS Mapping Table. This table specifies how non
native COS values are mapped to COS values defined in
native subnetwork

Note: The COS mappings that an EBN performs are
by multiple factors, one of which is a set of user-
initial mappings. This table returns the COS mappings
the EBN is actually performing at the time it is queried
rather than the user-defined initial ones."

::= { ebnCOS 1 }

ebnCosMapEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the EBN COS Mapping table."

INDEX { ebnCosMapCpName
ebnCosMapNonNativeCos }

::= { ebnCosMapTable 1 }

EbnCosMapEntry ::= SEQUENCE {
ebnCosMapCpName SnaNAUWildcardName
ebnCosMapNonNativeCos DisplayString
ebnCosMapNativeCos DisplayString }

ebnCosMapCpName OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"Fully qualified network CP name for which the COS
applies."

::= { ebnCosMapEntry 1 }

ebnCosMapNonNativeCos OBJECT-
SYNTAX DisplayString (SIZE(1..8))

Clouston & Moore Standards Track [Page 15]

RFC 2457 Extended Border Node MIB November 1998

MAX-ACCESS not-
STATUS

"This object contains one of the following values

- An 8-character COS name used in a non-native subnetwork
- The single character '*', identifying the entry with
default native COS for a non-native CP name. This
is used when there is no entry in the table for
non-native CP name / non-native COS pair

Because the characters allowed in an SNA COS name come
a restricted character set, these names are not subject
internationalization."

::= { ebnCosMapEntry 2 }

ebnCosMapNativeCos OBJECT-
SYNTAX DisplayString (SIZE(1..8))
MAX-ACCESS read-
STATUS

"An 8-byte name for the class-of-service, as known in
native subnetwork

Because the characters allowed in an SNA COS name come
a restricted character set, these names are not subject
internationalization."

::= { ebnCosMapEntry 3 }

-- ******************************************************************
-- EBN Subnet Routing List
-- The EBN Subnet Routing List indicates to which nodes an
-- forwards search request. This group contains
-- pertaining to the CONFIGURED Subnet Routing List at an EBN. How
-- particular search request is routed is determined by a
-- list that the EBN creates based on the configured list and
-- factors
-- *******************************************************************

ebnSubnetRoutingList OBJECT IDENTIFIER ::= { ebnObjects 5 }

ebnSubnetSearchTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

Clouston & Moore Standards Track [Page 16]

RFC 2457 Extended Border Node MIB November 1998

"This table contains one entry for each fully qualified
name for which an associated subnet routing list has
defined. An entry in this table contains
characteristics of the subnet search routing list for
LU name. The routing list itself is represented by a
of contiguous entries in the ebnSearchTable."

::= { ebnSubnetRoutingList 1 }

ebnSubnetSearchEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry for the ebnSubnetSearchTable. The
represents the configured parameters the EBN uses when
is determining how to search for the LU identified by
ebnSubnetSearchLuName object."

INDEX { ebnSubnetSearchLuName }

::= { ebnSubnetSearchTable 1 }

EbnSubnetSearchEntry ::= SEQUENCE {
ebnSubnetSearchLuName SnaNAUWildcardName
ebnSubnetSearchDynamics INTEGER
ebnSubnetSearchOrdering INTEGER }

ebnSubnetSearchLuName OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"Fully qualified network LU name."

::= { ebnSubnetSearchEntry 1 }

ebnSubnetSearchDynamics OBJECT-
SYNTAX INTEGER { none(1),
limited (2),
full (3) }
MAX-ACCESS read-
STATUS

"Indicates whether an EBN may add dynamic entries to
subnetwork routing list. none(1) means no entries may
added to the subnetwork routing list. limited(2)
only likely entries may be added to the subnetwork

Clouston & Moore Standards Track [Page 17]

RFC 2457 Extended Border Node MIB November 1998

list. full(3) means all native extended border nodes
adjacent, non-native EBNs and NNs will be added to
subnetwork routing list."

::= { ebnSubnetSearchEntry 2 }

ebnSubnetSearchOrdering OBJECT-
SYNTAX INTEGER{ priority(1),
defined(2) }
MAX-ACCESS read-
STATUS

"Indicates whether an EBN may reorder a subnetwork
list so that entries which are more likely to be
move to the top of the subnetwork routing list and
which are more likely to be unsuccessful move to the
of the list
The following values are defined

- priority(1): Entries may be reordered
- defined(2): Entries must not be reordered."

::= { ebnSubnetSearchEntry 3 }

-- Border node search

ebnSearchTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"This table indicates the CONFIGURED list of control
to which the EBN sends Locate searches for a given
qualified LU name. Each entry in the table indicates
control point that should be included in a multi-
search for a particular LU name."

::= { ebnSubnetRoutingList 2 }

ebnSearchEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the ebnSearchTable. An entry can exist
this table only if an entry exists in
ebnSubnetSearchTable with an ebnSubnetSearchLuName
matching this entry's ebnSearchLuName

Clouston & Moore Standards Track [Page 18]

RFC 2457 Extended Border Node MIB November 1998

For a given ebnSearchLuName value, the ordering of
provides by the ebnSearchIndex values corresponds to
order in which the control points to be searched appear
the CONFIGURED search list for the ebnSearchLuName."

INDEX { ebnSearchLuName
ebnSearchIndex }

::= { ebnSearchTable 1 }

EbnSearchEntry ::= SEQUENCE {
ebnSearchLuName SnaNAUWildcardName
ebnSearchIndex Unsigned32,
ebnSearchCpName DisplayString
ebnSearchSNVC Unsigned32 }

ebnSearchLuName OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"Fully qualified network LU name. If this object has
same value as the ebnSubnetSearchLuName object, then
two objects are referring to the same LU."

::= { ebnSearchEntry 1 }

ebnSearchIndex OBJECT-
SYNTAX Unsigned32
MAX-ACCESS not-
STATUS

"Secondary index enumerating the CONFIGURED order in
a search is forwarded to CPs for a particular LU name.
order for an actual search is determined dynamically by
EBN, based on this configured information and on
factors, including whether search dynamics and
ordering are enabled. Information on these last two
is available in, respectively, the
and ebnSubnetSearch ordering objects."

::= { ebnSearchEntry 2 }

ebnSearchCpName OBJECT-
SYNTAX DisplayString(SIZE(1..17))
MAX-ACCESS read-
STATUS

Clouston & Moore Standards Track [Page 19]

RFC 2457 Extended Border Node MIB November 1998

"This object specifies the CP(s) to which a search should
forwarded. It either follows the SnaNAUWildcardName
convention or takes one of the following special formats

'*' indicates that all native EBNs and all adjacent non
native EBNs and NNs may be added to the routing
dynamically

'*SELF' indicates that the EBN should search itself
its native subnetwork at this time during
cross-subnet search

'*EBNS' indicates all native EBNs

Because the characters allowed in a CP name come from
restricted character set, and because the three
listed here use no special characters, this object is
subject to internationalization."

::= { ebnSearchEntry 3 }

ebnSearchSNVC OBJECT-
SYNTAX Unsigned32
MAX-ACCESS read-
STATUS

"The maximum number of subnets a Locate search procedure
traverse. "

::= { ebnSearchEntry 4 }

-- *******************************************************************
-- HPR Extended Border Node Intermediate Session
-- The hbnIsInTable is a sparse extension to the appnIsInTable
-- For sessions that use back-to-back RTP connections in an HBN
-- this table provides the network connection endpoint
-- (NceId) and the transport connection identifier (Tcid) for
-- second RTP connection
-- *******************************************************************

hbn OBJECT IDENTIFIER ::= { ebnObjects 6 }

hbnIsInTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The HBN Intermediate Session table."

Clouston & Moore Standards Track [Page 20]

RFC 2457 Extended Border Node MIB November 1998

::= { hbn 1}

hbnIsInEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"Entry of the HBN Intermediate Session Table. An
exists in this table for every intermediate session
routed between back-to-back RTP connections in the HBN

When an entry for a session exists in this table,
NceIds and Tcids for the back-to-back RTP connections
made available in the following four objects

RTP connection in the direction of the PLU
- NceId: appnIsInRtpNceId (in the APPN MIB
- Tcid: appnIsinRtpTcid (in the APPN MIB).

RTP connection in the direction of the SLU
- NceId: hbnIsInRtpNceId (in this table
- Tcid: hbnIsInRtpTcid (in this table)."

INDEX { hbnIsInFqCpName
hbnIsInPcid }

::= { hbnIsInTable 1 }

HbnIsInEntry ::= SEQUENCE {
hbnIsInFqCpName SnaControlPointName
hbnIsInPcid OCTET STRING
hbnIsInRtpNceId OCTET STRING
hbnIsInRtpTcid OCTET STRING }

hbnIsInFqCpName OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The network-qualified control point name of the node
which the session and PCID originated. For APPN and
nodes, this is either the CP name of the APPN node
which the origin LU is located or the CP name of the
serving the LEN node at which the origin LU is located

If this object has the same value as the
object in the APPN MIB, then the two objects are
to the same APPN control point."

Clouston & Moore Standards Track [Page 21]

RFC 2457 Extended Border Node MIB November 1998

::= { hbnIsInEntry 1 }

hbnIsInPcid OBJECT-
SYNTAX OCTET STRING (SIZE(8))
MAX-ACCESS not-
STATUS

"The procedure correlation identifier (PCID) of a session
It is an 8-octet value

If this object has the same value as the appnIsInPcid
in the APPN MIB, and if the corresponding
object has the same value as the
appnIsInFqCpName object, then the entries indexed by
objects are referring to the same session."

::= { hbnIsInEntry 2 }

hbnIsInRtpNceId OBJECT-
SYNTAX OCTET STRING (SIZE(1..8))
MAX-ACCESS read-
STATUS

"The HPR local Network Connection Endpoint of the session
the direction of the SLU."

::= { hbnIsInEntry 3 }

hbnIsInRtpTcid OBJECT-
SYNTAX OCTET STRING (SIZE(8))
MAX-ACCESS read-
STATUS

"The RTP connection local TCID of the session in the
of the SLU."

::= { hbnIsInEntry 4 }

-- *******************************************************************
-- Conformance
-- *******************************************************************
ebnConformance OBJECT IDENTIFIER ::= { ebnMIB 2 }

ebnCompliances OBJECT IDENTIFIER ::= { ebnConformance 1 }
ebnGroups OBJECT IDENTIFIER ::= { ebnConformance 2 }

-- Compliance
ebnCompliance MODULE-

Clouston & Moore Standards Track [Page 22]

RFC 2457 Extended Border Node MIB November 1998

STATUS

"The compliance statement for the SNMPv2 entities
implement the ebnMIB."

MODULE -- this

-- Unconditionally mandatory
MANDATORY-GROUPS {
ebnDirectoryGroup
ebnIsRscvGroup
ebnDirectoryConfigGroup
ebnCosMappingGroup
ebnSubnetRoutingListGroup }

-- Conditionally mandatory
GROUP

"The hbnIsInGroup is mandatory only for HPR extended
nodes."

::= {ebnCompliances 1 }

-- Group
ebnDirectoryGroup OBJECT-
OBJECTS { ebnDirSubnetAffiliation }
STATUS

"The EBN-related directory objects."

::= { ebnGroups 1 }

ebnIsRscvGroup OBJECT-
OBJECTS { ebnIsRscvDestinationRoute
ebnIsRscvDestinationCos }
STATUS

"Two objects representing RSCV and class of
information saved by an EBN."

::= { ebnGroups 2 }

ebnDirectoryConfigGroup OBJECT-
OBJECTS { ebnSearchCacheTime
ebnMaxSearchCache
ebnDefaultSubnetVisitCount }
STATUS

Clouston & Moore Standards Track [Page 23]

RFC 2457 Extended Border Node MIB November 1998

"The EBN Directory Configuration Group."

::= { ebnGroups 3 }

ebnCosMappingGroup OBJECT-
OBJECTS { ebnCosMapNativeCos }
STATUS

"The EBN COS Mapping Group."

::= { ebnGroups 4 }

ebnSubnetRoutingListGroup OBJECT-
OBJECTS { ebnSubnetSearchDynamics
ebnSubnetSearchOrdering
ebnSearchCpName
ebnSearchSNVC }
STATUS

"The Subnet Routing List Group."

::= { ebnGroups 5 }

hbnIsInGroup OBJECT-
OBJECTS { hbnIsInRtpNceId, hbnIsInRtpTcid }
STATUS

"The HBN-related Intermediate Session Objects."

::= { ebnGroups 6 }

5.0 Security

Certain management information defined in this MIB may be
sensitive in some network environments. Therefore, authentication
received SNMP requests and controlled access to
information SHOULD be employed in such environments.
authentication protocol is defined in [10]. A protocol for
control is defined in [11].

None of the read-only objects in the EBN MIB reports a password,
data, or anything else that is particularly sensitive.
enterprises view their network configuration itself, as well
information about network usage and performance, as corporate assets

Clouston & Moore Standards Track [Page 24]

RFC 2457 Extended Border Node MIB November 1998

such enterprises may wish to restrict SNMP access to most of
objects in the MIB

There are no read-write objects in the EBN MIB

6.0 Intellectual

The IETF takes no position regarding the validity or scope of
intellectual property or other rights that might be claimed
pertain to the implementation or use of the technology described
this document or the extent to which any license under such
might or might not be available; neither does it represent that
has made any effort to identify any such rights. Information on
IETF's procedures with respect to rights in standards-track
standards-related documentation can be found in BCP-11. Copies
claims of rights made available for publication and any assurances
licenses to be made available, or the result of an attempt made
obtain a general license or permission for the use of
proprietary rights by implementers or users of this specification
be obtained from the IETF Secretariat

The IETF invites any interested party to bring to its attention
copyrights, patents or patent applications, or other
rights which may cover technology that may be required to
this standard. Please address the information to the IETF
Director

7.0

This MIB module is the product of the IETF SNA NAU MIB WG and the
APPN/HPR MIBs SIG. Thanks to Dave Billing, Cisco Systems; Katie Lee
IBM Corporation; and Marcia Peters, IBM Corporation, for
contributions and review

8.0

[1] Case, J., Fedor, M. Schoffstall, M. and J. Davin, "
Network Management Protocol", STD 15, RFC 1157, May 1990.

[2] McCloghrie, K., and M. Rose, "Management Information Base
Network Management of TCP/IP-based internets: MIB-II", STD 17,
RFC 1213, March 1991.

[3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S.,
"Structure of Management Information for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1902, January 1996.

Clouston & Moore Standards Track [Page 25]

RFC 2457 Extended Border Node MIB November 1998

[4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "
Conventions for Version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1903, January 1996.

[5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
"Conformance Statements for Version 2 of the Simple
Management Protocol (SNMPv2)", RFC 1904, January 1996.

[6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
"Protocol Operations for Version 2 of the Simple
Management Protocol (SNMPv2)", RFC 1905, January 1996.

[7] Harrington D., Presuhn, R. and B. Wijnen, "An Architecture
Describing SNMP Management Frameworks", RFC 2271, January 1998.

[8] Harrington D., Presuhn, R. and B. Wijnen, "Message
and Dispatching for the Simple Network Management
(SNMP)", RFC 2272, January 1998.

[9] Levi D., Meyer P. and B. Stewart, "SNMPv3 Applications",
2273, January 1998.

[10] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM
for version 3 of the Simple Network Management
(SNMPv3)", RFC 2274, January 1998.

[11] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Control Model (VACM) for the Simple Network Management
(SNMP)", RFC 2275, January 1998.

[12] Hovey, R. and S. Bradner, "The Organizations Involved in
IETF Standards Process", BCP 11, RFC 2028, October 1996.

[13] Bradner, S., "Key words for use in RFCs to Indicate
Levels", BCP 14, RFC 2119, March 1997.

[14] Clouston, B. and B. Moore, "Definition of Managed Objects
APPN", RFC 2455, November 1998.

[15] IBM, APPN Extended Border Node Architecture Reference
1.0, available only via anonymous FTP
networking.raleigh.ibm.com,
/pub/standards/aiw/appn/bordernode/ebn4.psbin

[16] IBM, SNA/MS Formats, GC31-8302-01

Clouston & Moore Standards Track [Page 26]

RFC 2457 Extended Border Node MIB November 1998

9.0 Authors'

Bob
Cisco
7025 Kit Creek
P.O. Box 14987
Research Triangle Park, NC 27709,

Phone: +1-919-472-2333
EMail: clouston@cisco.

Robert
Dept. BRQA/Bldg. 501/G114
IBM
P.O.Box 12195
3039
Research Triangle Park, NC 27709,

Phone: +1-919-254-4436
EMail: remoore@us.ibm.

Clouston & Moore Standards Track [Page 27]

RFC 2457 Extended Border Node MIB November 1998

10.0 Full Copyright

Copyright (C) The Internet Society (1998). All Rights Reserved

This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English

The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns

This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE

Clouston & Moore Standards Track [Page 28]

if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.

RFC documents can be found at I.E.T.F.

Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX