Managed Objects for ATM over Packet Switched Networks (PSNs)
RFC 5605
|
Document |
Type |
|
RFC - Proposed Standard
(July 2009; No errata)
|
|
Authors |
|
Thomas Nadeau
,
Orly Nicklass
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
RFC 5605 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Mark Townsley
|
|
Send notices to |
|
(None)
|
Network Working Group O. Nicklass
Request for Comments: 5605 RADVISION Ltd.
Category: Standards Track T. Nadeau
BT
July 2009
Managed Objects for ATM over Packet Switched Networks (PSNs)
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling ATM
Pseudowire (PW) carrying ATM cells over Packet Switched Networks
(PSNs).
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Nicklass & Nadeau Standards Track [Page 1]
RFC 5605 Manage ATM over PSN July 2009
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. The Internet-Standard Management Framework . . . . . . . . . . 4
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Relation to Other PW-MIB Modules . . . . . . . . . . . . . . . 5
7. ATM-PW MIB Usage . . . . . . . . . . . . . . . . . . . . . . . 6
8. Structure of the MIB Module . . . . . . . . . . . . . . . . . 7
9. Object Definition . . . . . . . . . . . . . . . . . . . . . . 8
10. Security Considerations . . . . . . . . . . . . . . . . . . . 33
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34
12.1. Normative References . . . . . . . . . . . . . . . . . . 34
12.2. Informative References . . . . . . . . . . . . . . . . . 36
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 36
1. Introduction
This document describes a model for managing "emulated" ATM services
over a Packet Switched Network (PSN).
The document follows the requirements for Pseudowire Emulation Edge-
to-Edge [PWREQ]; it is closely related to [ATMENCAP] and [ATMTRANS],
which describe the encapsulation of ATM signals and provide the
Emulation Service over a Packet Switched Network.
The ATM management model consists of several MIB modules, following
the layering model described in the PWE3 Architecture [PWARCH]
document. The ATM MIB module described in this document works
closely with the MIB modules described in [AToMTC], [AToM], [IFMIB],
[PWMIB], and the textual conventions defined in [PWTC]. The
conceptual layering and relationship among all of those is described
in Figure 1 and in the "Relation to Other PW-MIB Modules" section
listed below. An ATM connection will be a pseudowire (PW)
connection. It will not be treated as an interface and will
therefore not be represented in the ifTable.
Nicklass & Nadeau Standards Track [Page 2]
RFC 5605 Manage ATM over PSN July 2009
Figure 1: Conceptual Layering
+-------------------+
| ATM MIB | ATM-TC-MIB,
+-------------------+ ATMMIB
|
Show full document text