http://www.ietf.org/internet-drafts/draft-iyer-ipvpn-infomodel-00.txt
SUMMARY
This document represents the object oriented information
model for
representing policy information associated with provisioning
IP VPN
services such as firewall, address translation, quality
of service,
encryption. This draft extends the core policy information
model to
cover the policies that need to be enforced to configure
IP VPN
services mentioned earlier. The information model defined
in this
document is independent of any implementation specifics
related to
the repository used to store the policy information.
RELATED DOCUMENTS
[PFRAME] W. Weiss, H. Mahon, B. Moore, J. Strassner
, G. Waters, A.
Westerinen, J. Wheeler, "Policy Framework",
<draft-ietf-policy-framework-00.txt>, Sept 99.
[PCIM] J. Strassner, E. Ellesson, B. Moore, "Policy Core
Information
Model _ Version 1 Specification", RFC 3060
[PPVPNREQ] M. Carugi, D. McDysan et all, "Service requirements
for Provider Provisioned Virtual Private
Networks", Internet Draft <draft-ietf-ppvpn-requirements-00.txt>,
August 2001
WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK
PPVPN - Provider Provisioned VPN
WHY IS IT TARGETED AT THIS WG
From the charter :
"Particular attention will be placed on SP requirements
for security, privacy, scalability and manageability
considering such factors as Service Provider's projections
for number, complexity, and rate of change of
customer VPNs over the next several years."
A significant portion of the managebility requirements
should be cordinated with, or addressed by the
management solution. The provisioning component
of the management solution needs to adopt a commonly
agreed upon schema for capturing VPN requirements
on the network. This schema can be defined in
the form of an information model, which can later
on be implemented over SNMP or LDAP or any
other deployment choice.
The information model leverages the policy based
configuration work being done in the policy framework
WG to represent the information model in terms of
policy constructs. These policy constructs are defind
in the policy core information model RFC
JUSTIFICATION
-----------------
| Service Level | --> SLS capture customer requirement/service
goals
-----------------
<>--------->
Service goal to network policy translation
-----------------
| Network Level | --> IP VPN policies capture network
requirements
-----------------
<>--------->
Network policy to devices level specifications
-----------------
| Device Level | --> Device specific configuration
-----------------
The network requirements can be effectively captured
using policies. The policy constructs defined in the
policy core information model is used as the basis
for the policy structure. Various classes defined in
supporting drafts within the policy framework WG
are used as building blocks in the information model.
The translation of the service goals to network requirements
will ensure that there is a common understanding
between the service level and network itself on
how the service is to be provisioned in the network.
The requirements on the information model have be captured in a related draft
http://www.ietf.org/internet-drafts/draft-iyer-ipvpn-infomodel-req-00.txt
Thanks