draft-ietf-mpls-p2mp-te-mib-05.txt   draft-ietf-mpls-p2mp-te-mib-06.txt 
Network Working Group A. Farrel (Editor) Network Working Group A. Farrel (Editor)
INTERNET-DRAFT Old Dog Consulting INTERNET-DRAFT Old Dog Consulting
Updates: RFC3812, RFC4802 Updates: RFC3812, RFC4802
Intended Status: Standards Track S. Yasukawa Intended Status: Standards Track S. Yasukawa
Created: September 24, 2007 NTT Created: February 14, 2008 NTT
Expires: March 24, 2008 Expires: August 24, 2008
T. Nadeau T. Nadeau
BT BT
Point-to-Multipoint Multiprotocol Label Switching (MPLS) Point-to-Multipoint Multiprotocol Label Switching (MPLS)
Traffic Engineering (TE) Management Information Base (MIB) module Traffic Engineering (TE) Management Information Base (MIB) module
draft-ietf-mpls-p2mp-te-mib-05.txt draft-ietf-mpls-p2mp-te-mib-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 2, line 39 skipping to change at page 2, line 39
11.1. Normative References .................................... 55 11.1. Normative References .................................... 55
11.2. Informative References .................................. 56 11.2. Informative References .................................. 56
12. Authors' Addresses ........................................... 57 12. Authors' Addresses ........................................... 57
13. Intellectual Property ........................................ 57 13. Intellectual Property ........................................ 57
14. Full Copyright Statement ..................................... 58 14. Full Copyright Statement ..................................... 58
0. Changes Since Previous Revision 0. Changes Since Previous Revision
[This section to be removed before publication as an RFC.] [This section to be removed before publication as an RFC.]
- Clarify that this MIB module is equally applicable to GMPLS - Update author coordinates
(Abstract and section 1).
- Add explanation of how backward compatibility is not impacted by
the modification of semantics for objects in the MPLS-TE-STD-MIB.
(Sections 4.2.1 and 4.2.2.)
- Add section 5.2 for transit node example.
- Expand conformance statements for read-only and read-create cases. - Expand conformance statements for read-only and read-create cases.
- Fix smilint warnings.
- Typos. - Typos.
- Add mplsTeP2mpScalarGroup.
1. Introduction 1. Introduction
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 In particular, it describes managed objects for modeling
point-to-multipoint (P2MP) Multiprotocol Label Switching (MPLS) point-to-multipoint (P2MP) Multiprotocol Label Switching (MPLS)
traffic engineering (TE). traffic engineering (TE).
MPLS is defined in [RFC3031] and a signaling protocol for MPLS is defined in [RFC3031] and a signaling protocol for
skipping to change at page 27, line 34 skipping to change at page 27, line 34
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId mplsTunnelEgressLSRId
FROM MPLS-TE-STD-MIB -- RFC 3812 FROM MPLS-TE-STD-MIB -- RFC 3812
IndexInteger, IndexIntegerNextFree IndexInteger, IndexIntegerNextFree
FROM DIFFSERV-MIB -- RFC 3289 FROM DIFFSERV-MIB -- RFC 3289
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB -- RFC 4001 FROM INET-ADDRESS-MIB -- RFC 4001
; ;
mplsTeP2mpStdMIB MODULE-IDENTITY mplsTeP2mpStdMIB MODULE-IDENTITY
LAST-UPDATED "200709170000Z" -- Setember 17, 2007 LAST-UPDATED "200802140000Z" -- February 14, 2008
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Adrian Farrel " Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Seisho Yasukawa Seisho Yasukawa
NTT Corporation NTT Corporation
Email: s.yasukawa@hco.ntt.co.jp Email: s.yasukawa@hco.ntt.co.jp
Thomas D. Nadeau Thomas D. Nadeau
British Telecom British Telecom
Email: thomas.nadeau@bt.com Email: tom.nadeau@bt.com
Comments about this document should be emailed Comments about this document should be emailed
directly to the MPLS working group mailing list at directly to the MPLS working group mailing list at
mpls@lists.ietf.org" mpls@lists.ietf.org"
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2007). The initial version of "Copyright (C) The IETF Trust (2008). The initial version of
this MIB module was published in RFC XXXX. For full legal this MIB module was published in RFC XXXX. For full legal
notices see the RFC itself or see: notices see the RFC itself or see:
http://www.ietf.org/copyrights/ianamib.html http://www.ietf.org/copyrights/ianamib.html
-- RFC Editor. Please replace XXXX with the RFC number for this -- RFC Editor. Please replace XXXX with the RFC number for this
-- document and remove this note. -- document and remove this note.
This MIB module contains managed object definitions This MIB module contains managed object definitions
for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE)
defined in: defined in:
1. Signaling Requirements for Point-to-Multipoint 1. Signaling Requirements for Point-to-Multipoint
Traffic-Engineered MPLS Label Switched Paths (LSPs), Traffic-Engineered MPLS Label Switched Paths (LSPs),
S. Yasukawa, RFC 4461, April 2006. S. Yasukawa, RFC 4461, April 2006.
2. Extensions to Resource Reservation Protocol - Traffic 2. Extensions to Resource Reservation Protocol - Traffic
Engineering (RSVP-TE) for Point-to-Multipoint TE Label Engineering (RSVP-TE) for Point-to-Multipoint TE Label
Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D., Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D.,
and Yasukawa, S., RFC 4875, May 2007." and Yasukawa, S., RFC 4875, May 2007."
-- Revision history. -- Revision history.
REVISION REVISION
"200709170000Z" -- Setember 17, 2007 "200802140000Z" -- February 14, 2008
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC XXXX." "Initial version issued as part of RFC XXXX."
-- RFC Editor. Please replace XXXX with the RFC number for this -- RFC Editor. Please replace XXXX with the RFC number for this
-- document and remove this note. -- document and remove this note.
::= { mplsStdMIB YYY } ::= { mplsStdMIB YYY }
-- RFC Editor. Please replace YYY with the codepoint issued by IANA -- RFC Editor. Please replace YYY with the codepoint issued by IANA
-- and remove this note. -- and remove this note.
skipping to change at page 49, line 27 skipping to change at page 49, line 27
also be configured using this MIB module. also be configured using this MIB module.
The Module is implemented with support for read-create and The Module is implemented with support for read-create and
read-write. In other words, both monitoring and read-write. In other words, both monitoring and
configuration are available when using this configuration are available when using this
MODULE-COMPLIANCE." MODULE-COMPLIANCE."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsTeP2mpGeneralGroup, mplsTeP2mpGeneralGroup,
mplsTeP2mpNotifGroup mplsTeP2mpNotifGroup,
mplsTeP2mpScalarGroup
} }
-- mplsTeP2mpTunnelTable -- mplsTeP2mpTunnelTable
OBJECT mplsTeP2mpTunnelSubGroupOriginType OBJECT mplsTeP2mpTunnelSubGroupOriginType
SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2)} SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2)}
DESCRIPTION DESCRIPTION
"An implementation is only required to support "An implementation is only required to support
unknown(0), IPv4(1) and IPv6(2) addresses." unknown(0), IPv4(1) and IPv6(2) addresses."
skipping to change at page 50, line 18 skipping to change at page 50, line 18
support for MPLS-TE-P2MP-STD-MIB. Such devices can only be support for MPLS-TE-P2MP-STD-MIB. Such devices can only be
monitored using this MIB module. monitored using this MIB module.
The Module is implemented with support for read-only. In The Module is implemented with support for read-only. In
other words, only monitoring is available by implementing other words, only monitoring is available by implementing
this MODULE-COMPLIANCE." this MODULE-COMPLIANCE."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsTeP2mpGeneralGroup, mplsTeP2mpGeneralGroup,
mplsTeP2mpScalarGroup,
mplsTeP2mpNotifGroup mplsTeP2mpNotifGroup
} }
-- mplsTeP2mpTunnelTable -- mplsTeP2mpTunnelTable
OBJECT mplsTeP2mpTunnelP2mpIntegrity OBJECT mplsTeP2mpTunnelP2mpIntegrity
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTeP2mpTunnelBranchRole OBJECT mplsTeP2mpTunnelBranchRole
skipping to change at page 52, line 34 skipping to change at page 52, line 34
mplsTeP2mpNotifGroup NOTIFICATION-GROUP mplsTeP2mpNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
mplsTeP2mpTunnelDestUp, mplsTeP2mpTunnelDestUp,
mplsTeP2mpTunnelDestDown mplsTeP2mpTunnelDestDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notifications implemented in this module." "Notifications implemented in this module."
::= { mplsTeP2mpGroups 2 } ::= { mplsTeP2mpGroups 2 }
mplsTeP2mpScalarGroup OBJECT-GROUP
OBJECTS {
mplsTeP2mpTunnelConfigured,
mplsTeP2mpTunnelActive,
mplsTeP2mpTunnelTotalMaxHops
}
STATUS current
DESCRIPTION
"Scalar objects needed to implement P2MP MPLS tunnels."
::= { mplsTeP2mpGroups 3 }
END END
8. Security Considerations 8. Security Considerations
It is clear that this MIB module is potentially useful for the It is clear that this MIB module is potentially useful for the
monitoring of P2MP MPLS TE tunnels. This MIB module can also be used monitoring of P2MP MPLS TE tunnels. This MIB module can also be used
for the configuration of certain objects, and anything that can be for the configuration of certain objects, and anything that can be
configured can be incorrectly configured, with potentially disastrous configured can be incorrectly configured, with potentially disastrous
results. results.
skipping to change at page 57, line 40 skipping to change at page 57, line 40
Musashino-Shi, Tokyo 180-8585 Japan Musashino-Shi, Tokyo 180-8585 Japan
Phone: +81 422 59 4769 Phone: +81 422 59 4769
EMail: s.yasukawa@hco.ntt.co.jp EMail: s.yasukawa@hco.ntt.co.jp
Thomas D. Nadeau Thomas D. Nadeau
BT BT
BT Centre BT Centre
81 Newgate Street 81 Newgate Street
EC1A 7AJ EC1A 7AJ
London London
Email: thomas.nadeau@bt.com Email: tom.nadeau@bt.com
13. Intellectual Property 13. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 58, line 15 skipping to change at page 58, line 15
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
14. Full Copyright Statement 14. Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 14 change blocks. 
17 lines changed or deleted 25 lines changed or added

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