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

 1 marek 1.1 // Copyright (c) 2005 DMTF.  All rights reserved.
 2              [Version ( "2.8.0" ), 
 3               UMLPackagePath ( "CIM::IPsecPolicy" ), 
 4               Description ( 
 5                  "IKERule contains the Conditions and Actions for IKE phase 1 "
 6                  "negotiations or to specify static actions such as Discard." ), 
 7               MappingStrings { "IPSP Policy Model.IETF|IKERule" }]
 8           class CIM_IKERule : CIM_SARule {
 9           
10                 [Description ( 
11                     "An IP endpoint may have multiple identities for use in "
12                     "different situations. The IdentityContext property "
13                     "specifies the specific context/identities which pertain "
14                     "to this Rule. The property\'s function is similar to "
15                     "that of PolicyRoles. A context may be a VPN name or "
16                     "other identifier that selects the appropriate identity. \n"
17                     "\n"
18                     "IdentityContext is an array of strings. The multiple "
19                     "values in the array are logically ORed together in "
20                     "matching an IPNetworkIdentity\'s IdentityContext. Each "
21                     "value in the array may be a composition of multiple "
22 marek 1.1           "context names. When an array value is a composition, the "
23                     "individual values are logically ANDed together for "
24                     "evaluation purposes. The syntax is: \n"
25                     "<ContextName>[&&<ContextName>]* \n"
26                     "where the individual context names appear in "
27                     "alphabetical order (according to the collating sequence "
28                     "for UCS-2). So, for example, the values \'CompanyXVPN\', "
29                     "\'CompanyYVPN&&TopSecret\', \'CompanyZVPN&&Confidential\' "
30                     "are possible contexts for a Rule. They are matched "
31                     "against an IPNetworkIdentity\'s IdentityContext. Any of "
32                     "the values may indicate a match and select an Identity, "
33                     "since the values in the array are logically ORed." ), 
34                  MappingStrings { 
35                     "IPSP Policy Model.IETF|IKERule.IdentityContexts" }, 
36                  ModelCorrespondence { "CIM_IdentityContext" }]
37              string IdentityContexts[];
38           
39           
40           };

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2