(file) Return to CIM_IKERule.mof CVS log (file) (dir) Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / IPsecPolicy

File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / IPsecPolicy / CIM_IKERule.mof (download)
Revision: 1.1, Tue Jan 24 13:50:15 2012 UTC (12 years, 5 months ago) by marek
Branch: MAIN
CVS Tags: preBug9676, postBug9676, TASK-TASK_PEP362_RestfulService_branch-root, TASK-TASK_PEP362_RestfulService_branch-merged_out_from_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_to_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_from_branch, TASK-TASK_PEP362_RestfulService_branch-branch, TASK-PEP362_RestfulService-root, TASK-PEP362_RestfulService-merged_out_to_branch, TASK-PEP362_RestfulService-merged_out_from_trunk, TASK-PEP362_RestfulService-merged_in_to_trunk, TASK-PEP362_RestfulService-merged_in_from_branch, TASK-PEP362_RestfulService-branch, TASK-PEP317_pullop-merged_out_from_trunk, TASK-PEP317_pullop-merged_in_to_trunk, RELEASE_2_14_1, RELEASE_2_14_0-RC2, RELEASE_2_14_0-RC1, RELEASE_2_14_0, RELEASE_2_14-root, RELEASE_2_14-branch, RELEASE_2_13_0-RC2, RELEASE_2_13_0-RC1, RELEASE_2_13_0-FC, RELEASE_2_13_0, RELEASE_2_13-root, RELEASE_2_13-branch, RELEASE_2_12_1-RC1, RELEASE_2_12_1, RELEASE_2_12_0-RC1, RELEASE_2_12_0-FC, RELEASE_2_12_0, RELEASE_2_12-root, RELEASE_2_12-branch, HEAD, CIMRS_WORK_20130824
Branch point for: TASK-PEP317_pullop-branch
BUG#:9155
TITLE: Upgrade Pegasus to Include the CIM 2.31 Schema in CVS

DESCRIPTION:

// Copyright (c) 2005 DMTF.  All rights reserved.
   [Version ( "2.8.0" ), 
    UMLPackagePath ( "CIM::IPsecPolicy" ), 
    Description ( 
       "IKERule contains the Conditions and Actions for IKE phase 1 "
       "negotiations or to specify static actions such as Discard." ), 
    MappingStrings { "IPSP Policy Model.IETF|IKERule" }]
class CIM_IKERule : CIM_SARule {

      [Description ( 
          "An IP endpoint may have multiple identities for use in "
          "different situations. The IdentityContext property "
          "specifies the specific context/identities which pertain "
          "to this Rule. The property\'s function is similar to "
          "that of PolicyRoles. A context may be a VPN name or "
          "other identifier that selects the appropriate identity. \n"
          "\n"
          "IdentityContext is an array of strings. The multiple "
          "values in the array are logically ORed together in "
          "matching an IPNetworkIdentity\'s IdentityContext. Each "
          "value in the array may be a composition of multiple "
          "context names. When an array value is a composition, the "
          "individual values are logically ANDed together for "
          "evaluation purposes. The syntax is: \n"
          "<ContextName>[&&<ContextName>]* \n"
          "where the individual context names appear in "
          "alphabetical order (according to the collating sequence "
          "for UCS-2). So, for example, the values \'CompanyXVPN\', "
          "\'CompanyYVPN&&TopSecret\', \'CompanyZVPN&&Confidential\' "
          "are possible contexts for a Rule. They are matched "
          "against an IPNetworkIdentity\'s IdentityContext. Any of "
          "the values may indicate a match and select an Identity, "
          "since the values in the array are logically ORed." ), 
       MappingStrings { 
          "IPSP Policy Model.IETF|IKERule.IdentityContexts" }, 
       ModelCorrespondence { "CIM_IdentityContext" }]
   string IdentityContexts[];


};

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2