DESCRIPTION The destination IPv6 address of the RSVP signaled
flow, as defined in the RSVP PATH and RESV SESSION
[RSVP] objects.
ALLOWED VALUE TYPES: PolicyIPv6AddrValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.18. The Class "QoSPolicyRSVPSourcePortVariable"
This class contains the source port of the RSVP signaled flow, as
defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC
[RSVP] objects. The class definition is as follows:
NAME QoSPolicyRSVPSourcePortVariable
DESCRIPTION The source port of the RSVP signaled flow, as defined
in the RSVP PATH SENDER_TEMPLATE and RSVP RESV
FILTER_SPEC [RSVP] objects.
ALLOWED VALUE TYPES: PolicyIntegerValue (0..65535)
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.19. The Class "QoSPolicyRSVPDestinationPortVariable"
This is a concrete class that contains the destination port of the
RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and
RSVP RESV FILTER_SPEC [RSVP] objects. The class definition is as
follows:
NAME QoSPolicyRSVPDestinationPortVariable
DESCRIPTION The destination port of the RSVP signaled flow, as
defined in the RSVP PATH and RESV SESSION [RSVP]
objects.
ALLOWED VALUE TYPES: PolicyIntegerValue (0..65535)
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.20. The Class "QoSPolicyRSVPIPProtocolVariable"
This is a concrete class that contains the IP Protocol number of the
RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION
[RSVP] objects. The class definition is as follows:
NAME QoSPolicyRSVPIPProtocolVariable
DESCRIPTION The IP Protocol number of the RSVP signaled flow, as
defined in the RSVP PATH and RESV SESSION [RSVP]
objects.
ALLOWED VALUE TYPES: PolicyIntegerValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.21. The Class "QoSPolicyRSVPIPVersionVariable"
This is a concrete class that contains the IP Protocol version number
of the RSVP signaled flow, as defined in the RSVP PATH and RESV
SESSION [RSVP] objects. The well-known version numbers are 4 and 6.
This variable allows a policy definition of the type:
"If IP version = IPv4 then ...".
The class definition is as follows:
NAME QoSPolicyRSVPIPVersionVariable
DESCRIPTION The IP version number of the IP Addresses carried the
RSVP signaled flow, as defined in the RSVP PATH and
RESV SESSION [RSVP] objects.
ALLOWED VALUE TYPES: PolciIntegerValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.22. The Class "QoSPolicyRSVPDCLASSVariable"
This is a concrete class that contains the DSCP value as defined in
the RSVP DCLASS [DCLASS] object. The class definition is as follows:
NAME QoSPolicyRSVPDCLASSVariable
DESCRIPTION The DSCP value as defined in the RSVP DCLASS [DCLASS]
object.
ALLOWED VALUE TYPES: PolicyIntegerValue,
PolicyBitStringValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.23. The Class "QoSPolicyRSVPStyleVariable"
This is a concrete class that contains the reservation style as
defined in the RSVP STYLE object in the RESV message [RSVP]. The
class definition is as follows:
NAME QoSPolicyRSVPStyleVariable
DESCRIPTION The reservation style as defined in the RSVP STYLE
object in the RESV message [RSVP].
ALLOWED VALUE TYPES: PolicyBitStringValue,
PolicyIntegerValue (Integer has
an enumeration of
{ Fixed-Filter=1,
Shared-Explicit=2,
Wildcard-Filter=3}
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.24. The Class "QoSPolicyIntServVariable"
This is a concrete class that contains the Integrated Service
requested in the RSVP Reservation message, as defined in the FLOWSPEC
RSVP Object [RSVP]. The class definition is as follows:
NAME QoSPolicyRSVPIntServVariable
DESCRIPTION The integrated Service requested in the RSVP
Reservation message, as defined in the FLOWSPEC RSVP
Object [RSVP].
ALLOWED VALUE TYPES: PolicyIntegerValue (An enumerated
value of { CL=1 , GS=2, NULL=3}
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.25. The Class "QoSPolicyRSVPMessageTypeVariable"
This is a concrete class that contains the RSVP message type, as
defined in the RSVP message common header [RSVP] object. The class
definition is as follows:
NAME QoSPolicyRSVPMessageTypeVariable
DESCRIPTION The RSVP message type, as defined in the RSVP message
common header [RSVP] object.
ALLOWED VALUE TYPES: Integer (An enumerated value of
{PATH=1 , PATHTEAR=2, RESV=3,
RESVTEAR=4, RESVERR=5, CONF=6,
PATHERR=7}
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.26. The Class "QoSPolicyRSVPPreemptionPriorityVariable"
This is a concrete class that contains the RSVP reservation priority,
as defined in [RFC3181] object. The class definition is as follows:
NAME QoSPolicyRSVPPreemptionPriorityVariable
DESCRIPTION The RSVP reservation priority as defined in [RFC3181].
ALLOWED VALUE TYPES: PolicyIntegerValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.27. The Class "QoSPolicyRSVPPreemptionDefPriorityVariable"
This is a concrete class that contains the RSVP reservation defending
priority, as defined in [RFC3181] object. The class definition is as
follows:
NAME QoSPolicyRSVPPreemptionDefPriorityVariable
DESCRIPTION The RSVP preemption reservation defending priority as
defined in [RFC3181].
ALLOWED VALUE TYPES: PolicyIntegerValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.28. The Class "QoSPolicyRSVPUserVariable"
This is a concrete class that contains the ID of the user that
initiated the flow as defined in the User Locator string in the
Identity Policy Object [RFC3182]. The class definition is as
follows:
NAME QoSPolicyRSVPUserVariable
DESCRIPTION The ID of the user that initiated the flow as defined
in the User Locator string in the Identity Policy
Object [RFC3182].
ALLOWED VALUE TYPES: QoSPolicyDNValue,
PolicyStringValue,
QoSPolicyAttributeValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.29. The Class "QoSPolicyRSVPApplicationVariable"
This is a concrete class that contains the ID of the application that
generated the flow as defined in the application locator string in
the Application policy object [RFC2872]. The class definition is as
follows:
NAME QoSPolicyRSVPApplicationVariable
DESCRIPTION The ID of the application that generated the flow as
defined in the application locator string in the
Application policy object [RFC2872].
ALLOWED VALUE TYPES: QoSPolicyDNValue,
PolicyStringValue,
QoSPolicyAttributeValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.30. The Class "QoSPolicyRSVPAuthMethodVariable"
This is a concrete class that contains the type of authentication
used in the Identity Policy Object [RFC3182]. The class definition
is as follows:
NAME QoSPolicyRSVPAuthMethodVariable
DESCRIPTION The RSVP Authentication type used in the Identity
Policy Object [RFC3182].
ALLOWED VALUE TYPES: PolicyIntegerValue (An enumeration
of { NONE=0, PLAIN-TEXT=1,
DIGITAL-SIG = 2, KERBEROS_TKT=3,
X509_V3_CERT=4, PGP_CERT=5}
DERIVED FROM QoSPolicyRSVPVariable (defined in this document)
ABSTRACT FALSE
PROPERTIES None
8.31. The Class QoSPolicyDNValue
This class is used to represent a single or set of Distinguished Name
[DNDEF] values, including wildcards. A Distinguished Name is a name
that can be used as a key to retrieve an object from a directory
service. This value can be used in comparison to reference values
carried in RSVP policy objects, as specified in [RFC3182]. The class
definition is as follows:
NAME QoSPolicyDNValue
DERIVED FROM PolicyValue
ABSTRACT FALSE
PROPERTIES qpDNList
8.31.1. The Property qpDNList
This attribute provides an unordered list of strings, each
representing a Distinguished Name (DN) with wildcards. The format of
a DN is defined in [DNDEF]. The asterisk character ("*") is used as
wildcard for either a single attribute value or a wildcard for an
RDN. The order of RDNs is significant. For example: A qpDNList
attribute carrying the following value:
"CN=*, OU=Sales, O=Widget Inc., *, C=US" matches:
"CN=J. Smith, OU=Sales, O=Widget Inc, C=US"
and also matches:
"CN=J. Smith, OU=Sales, O=Widget Inc, L=CA, C=US".
The attribute is defined as follows:
NAME qpDNList
SYNTAX List of Distinguished Names implemented as strings, each of
which serves as a reference to another object.
8.32. The Class QoSPolicyRSVPSimpleAction
This action controls the content of RSVP messages and the way RSVP
requests are admitted. Depending on the value of its
qpRSVPActionType property, this action directly translates into
either a COPS Replace Decision or a COPS Stateless Decision, or both
as defined in COPS for RSVP. Only variables that are subclasses of
the QoSPolicyRSVPVariable are allowed to be associated with this
action. The property definition is as follows:
NAME QoSPolicyRSVPSimpleAction
DESCRIPTION This action controls the content of RSVP messages and
the way RSVP requests are admitted.
DERIVED FROM SimplePolicyAction (defined in [PCIMe])
ABSTRACT FALSE
PROPERTIES qpRSVPActionType
8.32.1. The Property qpRSVPActionType
This property is an enumerated integer denoting the type(s) of RSVP
action. The value ’REPLACE’ denotes a COPS Replace Decision action.
The value ’STATELESS’ denotes a COPS Stateless Decision action. The
value REPLACEANDSTATELESS denotes both decision actions. Refer to
[RFC2749] for details.
NAME qpRSVPActionType
DESCRIPTION This property specifies whether the action type is for
COPS Replace, Stateless, or both types of decisions.
SYNTAX Integer
VALUE This is an enumerated integer. A value of 0 specifies
a COPS Replace decision. A value of 1 specifies a COPS
Stateless Decision. A value of 2 specifies both COPS
Replace and COPS Stateless decisions.
9. Intellectual Property Rights Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF’s procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11.
Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
10. Acknowledgements
The authors wish to thank the input of the participants of the Policy
Framework working group, and especially the combined group of the
PCIMe coauthors, Lee Rafalow, Andrea Westerinen, Ritu Chadha and
Marcus Brunner. In addition, we’d like to acknowledge the valuable
contribution from Ed Ellesson, Joel Halpern and Mircea Pana. Thank
you all for your comments, critique, ideas and general contribution.
11. Security Considerations
The Policy Core Information Model [PCIM] describes the general
security considerations related to the general core policy model.
The extensions defined in this document do not introduce any
additional considerations related to security.
12. References
12.1. Normative References
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[PCIM] Moore, B., Ellesson, E., Strassner, J. and A. Westerinen,
"Policy Core Information Model -- Version 1
Specification", RFC 3060, February 2001.
[PCIMe] Moore, B., Ed., "Policy Core Information Model
Extensions", RFC 3460, January 2003.
12.2. Informative References
[TERMS] Westerinen, A., Schnizlein, J., Strassner, J., Scherling,
M., Quinn, B., Herzog, S., Huynh, A., Carlson, M., Perry,
J. and M. Waldbusser, "Terminology for Policy-based
Management", RFC 3198, November 2001.
[DIFFSERV] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z.
and W. Weiss, "An Architecture for Differentiated
Services", RFC 2475, December 1998.
[INTSERV] Braden, R., Clark, D. and S. Shenker, "Integrated Services
in the Internet Architecture: an Overview", RFC 1633, June
1994.
[RSVP] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S. and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, September 1997.
[RFC2749] Herzog, S., Ed., Boyle, J., Cohen, R., Durham, D., Rajan,
R. and A. Sastry, "COPS usage for RSVP", RFC 2749, January
2000.
[RFC3181] Herzog, S., "Signaled Preemption Priority Policy Element",
RFC 3181, October 2001.
[DIFF-MIB] Baker, F., Chan, K. and A. Smith, "Management Information
Base for the Differentiated Services Architecture", RFC
3289, May 2002.
[AF] Heinanen, J., Baker, F., Weiss, W. and J. Wroclawski,
"Assured Forwarding PHB Group", RFC 2597, June 1999.
[CL] Wroclawski, J., "Specification of the Controlled-Load
Network Element Service", RFC 2211, September 1997.
[RSVP-IS] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services", RFC 2210, September 1997.
[GS] Shenker, S., Partridge, C. and R. Guerin, "Specification
of the Guaranteed Quality of Service", RFC 2212, September
1997.
[DCLASS] Bernet, Y., "Format of the RSVP DCLASS Object", RFC 2996,
November 2000.
[RFC3182] Yadav, S., Yavatkar, R., Pabbati, R., Ford, P., Moore, T.,
Herzog, S. and R. Hess, "Identity Representation for
RSVP", RFC 3182, October 2001.
[RFC2872] Bernet, Y. and R. Pabbati, "Application and Sub
Application Identity Policy Element for Use with RSVP",
RFC 2872, June 2000.
[DNDEF] Wahl, M., Kille, S. and T. Howes, "Lightweight Directory
Access Protocol (v3): UTF-8 String Representation of
Distinguished Names", RFC 2253, December 1997.
13. Authors’ Addresses
Yoram Ramberg
Cisco Systems
4 Maskit Street
Herzliya Pituach, Israel 46766
Phone: +972-9-970-0081
Fax: +972-9-970-0219
EMail: yramberg@cisco.com
Yoram Snir
Cisco Systems
300 East Tasman Drive
San Jose, CA 95134
Phone: +1 408-853-4053
Fax: +1 408 526-7864
EMail: ysnir@cisco.com
John Strassner
Intelliden Corporation
90 South Cascade Avenue
Colorado Springs, Colorado 80903
Phone: +1-719-785-0648
Fax: +1-719-785-0644
EMail: john.strassner@intelliden.com
Ron Cohen
Ntear LLC
Phone: +972-8-9402586
Fax: +972-9-9717798
EMail: ronc@lyciumnetworks.com
Bob Moore
IBM Corporation
P. O. Box 12195, BRQA/501/G206
3039 Cornwallis Rd.
Research Triangle Park, NC 27709-2195
Phone: +1 919-254-4436
Fax: +1 919-254-6243
EMail: remoore@us.ibm.com
14. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.