RFC 3052: Service Management Architectures Issues and Review
In plain English — editorial summary, not part of the RFC
The purpose of this document is to explore the problems of defining a Service management framework and to examine some of the issues that still need to be resolved. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3052
- Published
- January 2001
- Authors
- M. Eder; S. Nag
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2448AT&T's Error Resilient Video Transmission TechniqueCurrent
November 1998
- RFC 2791Scalable Routing Design PrinciplesCurrent
July 2000
- RFC 3069VLAN Aggregation for Efficient IP Address AllocationCurrent
February 2001
- RFC 3018Unified Memory Space Protocol SpecificationCurrent
December 2000
- RFC 3094Tekelec's Transport Adapter Layer InterfaceCurrent
April 2001
- RFC 2992Analysis of an Equal-Cost Multi-Path AlgorithmCurrent
November 2000
- RFC 2991Multipath Issues in Unicast and Multicast Next-Hop SelectionCurrent
November 2000
- RFC 3147Generic Routing Encapsulation over CLNS NetworksCurrent
July 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?