[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
TE-WG/NEW draft-chadha-policy-mpls-te-01.txt
- To: idsummary@subip.ietf.org
- Subject: TE-WG/NEW draft-chadha-policy-mpls-te-01.txt
- From: Marcus.Brunner@ccrle.nec.de
- Date: Fri, 18 May 2001 22:16:33 +0200 (CEST)
- Delivery-date: Fri, 18 May 2001 13:16:53 -0700
- Envelope-to: idsummary-data@psg.com
- User-Agent: IMP/PHP IMAP webmail program 2.2.3
NAME OF I-D:
http://www.ietf.org/internet-drafts/draft-chadha-policy-mpls-te-01.txt
SUMMARY
The purpose of this draft is to describe an information model for
representing MPLS policies, including MPLS for traffic engineering
and QoS. RFC 2702, "Requirements for Traffic Engineering over MPLS",
is used as a basis for determining the types of information that
need to be represented in the traffic engineering part of the
information model. The latter document describes the functional
capabilities required to implement policies that facilitate
efficient and reliable network operations in an MPLS domain.
For the QoS-related part, the Policy Framework QoS Information Model
(QPIM) is extended with new classes for controlling and managing the
lifecycle of Label Switched Paths (LSPs) and for mapping of traffic
onto existing LSPs. The control and management of LSP lifecycles
includes mainly the creation, update, and deletion of LSPs and the
assignment of QoS properties to LSPs.
This information model may be used by a management system to
optimize network performance through the necessary network
provisioning actions and any other management actions related
to MPLS and its signalling protocols.
RELATED DOCUMENTS
Requirements for Traffic Engineering Over MPLS
http://www.ietf.org/rfc/rfc2702
Policy QoS Information Model
http://www.ietf.org/internet-drafts/draft-ietf-policy-qos-info-model-03.txt
Policy Core Information Model - Version 1 Specification
http://www.ietf.org/rfc/rfc3060.txt
Policy Core Information Model Extensions
http://www.ietf.org/internet-drafts/draft-ietf-policy-pcim-ext-01.txt
A COPS client-type for IP traffic engineering
http://www.ietf.org/internet-drafts/draft-jacquenet-ip-te-cops-01.txt
A Traffic Engineering MIB
http://www.ietf.org/internet-drafts/draft-ietf-tewg-mib-00.txt
MPLS Traffic Engineering Management Information Base Using SMIv2
http://www.ietf.org/internet-drafts/draft-ietf-mpls-te-mib-06.txt
WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK
TE-WG or NEW-WG
Applications +-------+ +-------+ (new) Hour glass
that use CCAMP: \ | TE-WG | | PPVPN | ... /
\ +-------+ +-------+ /
\ +----------------------+ /
\ | CCAMP | /
\ |-----------+----------| /
/ | C | M --|------ IGP LSA ext
/ | control | measure | \
/ +----------------------+ \
Technologies to / +----+ +----+ +----+ +----+ +----+ \
measure/control:/ |MPLS| |OPT | |RPR | |ATM | | FR |...\
+----+ +----+ +----+ +----+ +----+
WHY IS IT TARGETED AT THIS WG
The target of the draft is an information model, which may be used by
traffic engineering systems and other systems managing MPLS networks.
It also fits together with the TE-MIB, MPLS-MIB, and all kind of MPLS PIBs.
It does not cover the work items listed so far in TE. Therefore and because of
the other work (TE-PIB, MPLS-PIB, etc.)
it may even make sense in a seperate WG.
JUSTIFICATION
Especially, operator, should care about a model for MPLS, that different
TE and management systems, and MPLS databases to store the configuration in
may interoperate more easily using a uniform model.
And there is enough room for algorithms for TE toio differentiate products.
The new work item would be an Informational Model of MPLS
We understand that the work has not got enough support from parts
of the TE-WG. Also, because the WG has enough things to finish first.