< draft-ietf-pwe3-cep-mib-15.txt   draft-ietf-pwe3-cep-mib-16.txt >
Pseudowire Edge-to-Edge Emulation D. Zelig, Ed. Pseudowire Edge-to-Edge Emulation D. Zelig, Ed.
Internet-Draft Oversi Systems Internet-Draft Oversi Systems
Intended status: Standards Track R. Cohen, Ed. Intended status: Standards Track R. Cohen, Ed.
Expires: September 7, 2011 Resolute Networks Expires: September 7, 2011 Resolute Networks
T. Nadeau, Ed. T. Nadeau, Ed.
LucidVision Huawei
March 7, 2011 March 8, 2011
SONET/SDH Circuit Emulation Service Over Packet (CEP) Management SONET/SDH Circuit Emulation Service Over Packet (CEP) Management
Information Base (MIB) Using SMIv2 Information Base (MIB) Using SMIv2
draft-ietf-pwe3-cep-mib-15 draft-ietf-pwe3-cep-mib-16
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling SONET/SDH In particular, it describes managed objects for modeling SONET/SDH
circuits over a Packet Switch Network (PSN). circuits over a Packet Switch Network (PSN).
Requirements Language Requirements Language
skipping to change at page 3, line 36 skipping to change at page 3, line 36
stack is modeled within [RFC3592]. stack is modeled within [RFC3592].
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
described in [RFC3985]. Unless otherwise stated, the mechanisms of described in [RFC3985]. Unless otherwise stated, the mechanisms of
[RFC3985] apply and will not be re-described here. [RFC3985] apply and will not be re-described here.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [BCP14]. document are to be interpreted as described in [RFC2119].
2. Terminology 2. Terminology
CEP terminology comes from [RFC4842] that describes a mechanism for CEP terminology comes from [RFC4842] that describes a mechanism for
transporting SONET/SDH Time Division Multiplexed (TDM) digital transporting SONET/SDH Time Division Multiplexed (TDM) digital
signals over a packet-oriented network. The mechanism for structured signals over a packet-oriented network. The mechanism for structured
emulation (as outlined in the CEP draft) terminates the SONET/SDH emulation (as outlined in [RFC4842]) terminates the SONET/SDH
section and line overhead and then breaks the SONET/SDH path's section and line overhead and then breaks the SONET/SDH path's
Synchronous Payload Envelope (SPE) into fragments for transmission Synchronous Payload Envelope (SPE) into fragments for transmission
over a PSN. Mechanism for terminating of the SONET/SDH path overhead over a PSN. Mechanism for terminating of the SONET/SDH path overhead
and extracting SONET VTs are also described in [RFC4842]. Mechanisms and extracting SONET VTs are also described in [RFC4842]. Mechanisms
for Fractional SONET/SDH SPE emulation are described in [RFC4842]. A for Fractional SONET/SDH SPE emulation are described in [RFC4842]. A
CEP header is appended at the beginning of each fragment to provide CEP header is appended at the beginning of each fragment to provide
information regarding where the SPE begins within the packet stream, information regarding where the SPE begins within the packet stream,
a sequence number and pointer adjustment information (see [RFC4842]). a sequence number and pointer adjustment information (see [RFC4842]).
"Outbound" references the traffic direction where a SONET/SDH path's "Outbound" references the traffic direction where a SONET/SDH path's
skipping to change at page 9, line 32 skipping to change at page 9, line 32
PwCfgIndexOrzero PwCfgIndexOrzero
FROM PW-TC-STD-MIB -- RFC 5542 FROM PW-TC-STD-MIB -- RFC 5542
-- RFC Editor: Please replace PWTC with actual RFC number and -- RFC Editor: Please replace PWTC with actual RFC number and
-- remove this note -- remove this note
; ;
-- The PW CEP MIB -- The PW CEP MIB
pwCepStdMIB MODULE-IDENTITY pwCepStdMIB MODULE-IDENTITY
LAST-UPDATED "201103071200Z" -- 7 March 2011 12:00:00 GMT LAST-UPDATED "201103081200Z" -- 8 March 2011 12:00:00 GMT
ORGANIZATION "Pseudowire Emulation Edge-to-Edge (PWE3) ORGANIZATION "Pseudowire Emulation Edge-to-Edge (PWE3)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" "
David Zelig (Ed.) David Zelig (Ed.)
E-mail: David Zelig <davidz@oversi.com> E-mail: David Zelig <davidz@oversi.com>
Ron Cohen (Ed.) Ron Cohen (Ed.)
Email: ronc@resolutenetworks.com Email: ronc@resolutenetworks.com
skipping to change at page 10, line 17 skipping to change at page 10, line 16
Copyright (c) 2011 IETF Trust and the persons identified Copyright (c) 2011 IETF Trust and the persons identified
as the document authors. All rights reserved. This version as the document authors. All rights reserved. This version
of this MIB module is part of RFC xxxx; See the RFC itself of this MIB module is part of RFC xxxx; See the RFC itself
for full legal notices. for full legal notices.
-- RFC Editor: Please replace XXXX with actual RFC number and -- RFC Editor: Please replace XXXX with actual RFC number and
-- remove this note -- remove this note
" "
-- Revision history. -- Revision history.
REVISION "201103071200Z" -- 7 March 2011 12:00:00 GMT REVISION "201103081200Z" -- 8 March 2011 12:00:00 GMT
DESCRIPTION "Initial version published as part of RFC XXXX." DESCRIPTION "Initial version published as part of RFC XXXX."
-- RFC Editor: Please replace XXXX with actual RFC number and remove -- RFC Editor: Please replace XXXX with actual RFC number and remove
-- this note -- this note
::= { mib-2 XXXX } -- To be assigned by IANA ::= { mib-2 XXXX } -- To be assigned by IANA
-- RFC Editor: Please replace the XXXX with the -- RFC Editor: Please replace the XXXX with the
-- IANA assigned value and remove this note -- IANA assigned value and remove this note
-- Local Textual conventions -- Local Textual conventions
skipping to change at page 15, line 12 skipping to change at page 15, line 12
current interval exceeds the maximum value, the current interval exceeds the maximum value, the
agent will return the maximum value." agent will return the maximum value."
::= { pwCepEntry 5 } ::= { pwCepEntry 5 }
pwCepValidIntervals OBJECT-TYPE pwCepValidIntervals OBJECT-TYPE
SYNTAX HCPerfValidIntervals SYNTAX HCPerfValidIntervals
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of previous 15-minute intervals for which data "The number (n) of previous 15-minute intervals for which data
was collected. was collected.
An agent with CEP capability MUST be capable of supporting An agent with CEP capability MUST be capable of supporting
at least n intervals. The minimum value of n is 4, the at least 4 intervals. The RECOMMENDED default of value for
default of n is 32 and the maximum value of n is 96. n is 32 and n MUST NOT exceed 96."
"
::= { pwCepEntry 6 } ::= { pwCepEntry 6 }
pwCepIndications OBJECT-TYPE pwCepIndications OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
missingPkt ( 0), missingPkt ( 0),
ooRngDropped( 1), ooRngDropped( 1),
jtrBfrUnder ( 2), jtrBfrUnder ( 2),
pktMalformed( 3), pktMalformed( 3),
lops ( 4), lops ( 4),
cepRdi ( 5), cepRdi ( 5),
skipping to change at page 39, line 40 skipping to change at page 39, line 38
pwCepPerfIntervalSESs PerfIntervalCount, pwCepPerfIntervalSESs PerfIntervalCount,
pwCepPerfIntervalUASs PerfIntervalCount, pwCepPerfIntervalUASs PerfIntervalCount,
pwCepPerfIntervalFC PerfIntervalCount pwCepPerfIntervalFC PerfIntervalCount
} }
pwCepPerfIntervalNumber OBJECT-TYPE pwCepPerfIntervalNumber OBJECT-TYPE
SYNTAX Integer32 (1..96) SYNTAX Integer32 (1..96)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number (normally between 1 and 96 to cover a 24 hour "A number (between 1 and 96 to cover a 24 hour
period) which identifies the interval for which the set period) which identifies the interval for which the set
of statistics is available. The interval identified by 1 of statistics is available. The interval identified by 1
is the most recently completed 15-minute interval and is the most recently completed 15-minute interval and
the interval identified by N is the interval immediately the interval identified by N is the interval immediately
preceding the one identified by N-1. The minimum range of preceding the one identified by N-1. The minimum range of
N is 1 through 4. The default range is 1 through 32. The N is 1 through 4. The default range is 1 through 32. The
maximum value of N is 1 through 96." maximum value of N is 1 through 96."
::= { pwCepPerfIntervalEntry 1 } ::= { pwCepPerfIntervalEntry 1 }
pwCepPerfIntervalValidData OBJECT-TYPE pwCepPerfIntervalValidData OBJECT-TYPE
 End of changes. 9 change blocks. 
14 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/