idnits 2.17.1 draft-ietf-rap-acct-fr-pib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 2 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([COPS-PR], [COPS]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 98 has weird spacing: '...� the selec...' == Line 116 has weird spacing: '... PDP of the s...' == Line 251 has weird spacing: '...n of an acco...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC-2119' is mentioned on line 41, but not defined == Unused Reference: 'SPPI' is defined on line 654, but no explicit reference was found in the text == Unused Reference: 'DSPIB' is defined on line 661, but no explicit reference was found in the text -- No information found for draft-ietf-rap-cops-pr - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'COPS-PR' == Outdated reference: A later version (-07) exists of draft-ietf-rap-sppi-05 ** Downref: Normative reference to an Historic draft: draft-ietf-rap-sppi (ref. 'SPPI') == Outdated reference: A later version (-09) exists of draft-ietf-rap-frameworkpib-03 ** Downref: Normative reference to an Historic draft: draft-ietf-rap-frameworkpib (ref. 'FR-PIB') == Outdated reference: A later version (-09) exists of draft-ietf-diffserv-pib-02 ** Downref: Normative reference to an Historic draft: draft-ietf-diffserv-pib (ref. 'DSPIB') == Outdated reference: A later version (-01) exists of draft-gross-sipaq-00 -- Possible downref: Normative reference to a draft: ref. 'SIP-AAA-QOS' Summary: 7 errors (**), 0 flaws (~~), 13 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Diana Rawlins 3 Expiration: March 2001 WorldCom 4 File: draft-ietf-rap-acct-fr-pib-01.txt Amol Kulkarni 5 Intel 6 Kwok Ho Chan 7 Nortel Networks 8 Dinesh Dutt 9 Cisco 11 Framework of COPS-PR Policy Information Base for Accounting Usage 13 Last Updated March 2 2001 15 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC2026. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months and may be updated, replaced, or obsoleted by other 26 documents at any time. It is inappropriate to use Internet-Drafts 27 as reference material or to cite them other than as "work in 28 progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Conventions used in this document 37 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 38 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 39 "OPTIONAL" in this document are to be interpreted as described in 40 [RFC-2119]. 42 Abstract 43 Currently there are no policy classes defined for the PEP to convey 44 provisioned policy usage feedback to the PDP. The purpose of this 45 document is to define the accounting framework PIB that specifies the 46 policy classes common for COPS accounting type reports. The basic 47 operation and objects for reporting usage information are defined in 48 [COPS]. A specific clientSI accounting type object named REPORT is 49 defined in [COPS-PR]. This document further describes operational 50 behavior that is implied in [COPS] and [COPS-PR.] 52 Table Of Contents 54 1 Introduction.....................................................3 55 2 General Concepts.................................................3 56 2.1 Overview.......................................................3 57 2.2 Normal Operation...............................................3 58 2.3 Failover.......................................................4 59 2.4 Context........................................................4 60 2.5 Delete Request States..........................................4 61 2.6 Periodic nature of report accounting...........................4 62 3 Definition of Accounting Type Report Policy......................5 63 4 Summary of the Accounting Framework Policy Information Base......6 64 4.1 SPPI ACCESS clause report-only.................................6 65 4.2 Textual Conventions Counts.....................................6 66 4.3 Accounting Type Report Group and PRCs..........................6 67 4.3.1 The Accounting Type Report Resume Table......................7 68 4.3.2 The Accounting Type Report Linkage Table.....................7 69 4.3.3 The Filter Usage Table.......................................7 70 5 The Accounting Framework PIB Module..............................7 71 6 Security Considerations.........................................13 72 7 Acknowledgements................................................13 73 8 Authors' Addresses..............................................13 74 9 References......................................................13 76 1 Introduction 78 Policy usage reported by the PEP makes a richer set of information 79 available to the PDP for decision-making. This report accounting 80 information can influence future decisions made by the PDP and the 81 resulting policy installed by the PDP at the PEP. For example, A PDP 82 determining policy for a SIP signaled multimedia session may need to 83 base the decision in part on usage information related to previously 84 installed QoS policy decisions. Further, the PDP may coordinate this 85 usage information with other external systems to determine the future 86 policy such as the case with the PDP coordinating multimedia session 87 QoS and clearinghouse authorizations [SIP-AAA-QOS] 89 The scope of this document is to describe the policy class framework 90 for policy usage monitored and reported by the PEP and collected at 91 the PDP. The charging and billing models as well as other accounting 92 events detectable by the PDP are beyond the scope of this framework. 94 2 General Concepts 96 2.1 Overview 97 There are two aspects to defining policies for an accounting type 98 report � the selection aspect and the policy usage aspect. The 99 usage policy and selection policy are associated with one another. 100 The usage criteria policy class defines what metrics are monitored, 101 recorded and reported by the PEP. The selection criteria policy class 102 specifies the conditions for the monitoring and recording of the 103 associated usage policy. For example, a usage policy may be defined 104 to provide counts of packets received. The selection criteria policy 105 may identify the filter on which to base the packet counts. A third 106 policy may be used to associate, or link, the selection and usage 107 policies. The linking is performed by the accounting type report 108 linkage policy. 110 2.2 Normal Operation 112 The PDP specifies the minimum accounting interval in the Accounting 113 Timer object that is included in the Client Accept message during 114 connection establishment. This specifies the maximum frequency with 115 which the PEP issues unsolicited accounting type reports. The PEP 116 notifies the PDP of the selection criteria policy classes and usage 117 policy classes it supports during the initial request for 118 configuration data using the frwkPRCSupportTable entries[FR-PIB]. 120 The PDP responds to the initial request for configuration with a 121 DECISION that installs policies. The PDP may also specify maximum 122 reporting intervals associated with each of the policies. The PEP 123 monitors and records the usage per the selection criteria defined by 124 the PDP. Periodically the PEP reports the usage with an accounting 125 type REPORT. 127 The PDP is the collection point for the usage information monitored 128 and reported by the PEP clients within the administrative domain. The 129 PDP may also collect other accounting event information that is 130 outside the scope of this document. 132 2.3 Failover 134 In the event the connection is lost between the PEP and PDP, the PEP 135 continues to track usage information as long as it continues to 136 operate with the installed policy. When the locally installed policy 137 at the PEP expires, the usage policy data also expires. 139 Upon successful reconnection where the PEP is still caching policy, 140 the PDP indicates to the PEP that the PEP may resume sending of the 141 accounting type report messages. The PDP does this deterministically. 142 It issues an unsolicited decision containing the 143 frwkAtRptResumeIndicator set to resume reporting. The PDP is aware of 144 the request state Handle(s) and the supported PRCs either through the 145 state synchronization mechanism or because the PDP considers itself 146 synchronized with the PEP upon reconnection. 148 2.4 Context 150 The monitoring and recording of usage policies is subject to context 151 switches in a manner similar to enforcement policy. The usage policy 152 is monitored, recorded and reported while the associated PIB instance 153 is active. The PEP should retain existing accounting data during 154 inactive contexts and resume it's monitoring and reporting when the 155 PIB instance becomes active again. 157 2.5 Delete Request States 159 The PEP may send any outstanding accounting data monitored during the 160 interval to the PDP via an unsolicited report immediately prior to 161 issuing a Delete Request State if the time interval since the last 162 report is not less than the interval defined by the Accounting Timer. 163 This is also the case when the PDP initiates the Delete Request State 164 with a decision request delete state. In this case where a PDP 165 initiates a Decision Request State Remove, the PEP acknowledges with 166 the Report, but the actual Delete Request State may be delayed until 167 the next reporting interval has completed. 169 2.6 Periodic nature of report accounting 171 The PDP informs the PEP of the minimal accounting interval it 172 supports in the Accounting Timer object during client connection 173 establishment. The PDP may specify accounting intervals in the 174 specific accounting policies per the PEP's indicated capabilities. 175 The PDP may also halt reporting for a request state by issuing an 176 unsolicited decision with the frwkAtRptResumeIndicator set to halt 177 reporting. Any usage information associated with that request state 178 at the PEP since the last accounting interval is discarded by the 179 PEP. 181 Generally the accounting policy is periodic in nature and the 182 reporting is unsolicited. The unsolicited reports are supplied within 183 the interval decided by the PDP. Note that periodic unsolicited 184 reports (as dictated by timer intervals) use a deterministic amount 185 of network resources. 187 There may be instances where the nature of the accounting policy for 188 a given client type or accounting PIB module is such that it is 189 useful for the PDP to control when it receives the feedback. The PDP 190 may therefore have the capability to solicit the accounting report 191 for a request state. 193 3 Definition of Accounting Type Report Policy 195 There are three basic types of policy used to define what the PEP is 196 to monitor, record and report. These are the selection criteria 197 policy, the usage policy and the accounting type report linkage 198 policy. 200 The selection criteria policy is installed by the PDP. It defines the 201 conditions used by the PEP to monitor and record a usage policy. 202 Generally, the selection criterion is an existing PRC such as the 203 frwkIPFilterTable. This PRC is useful for specifying conditions on 204 which to base usage - i.e. count the number of packets received for 205 this filter. The filter (source address, destination address, etc.) 206 in this case defines the conditions. In the case of the accounting 207 framework PIB, the frwkIPFilterTable is the only PRC used to base 208 selection on. 210 The usage policy defines what attributes are monitored and recorded 211 by the PEP. These policies have an ACCESS clause of Report. 212 Generally, the usage policies specify counts related to a specific 213 action such as a packet being dropped. The accounting framework PIB 214 defines one usage policy class, frwkAtRptFilterStats. It counts 215 packets and bytes as well as records the timestamp when the last 216 packet was received. Usage PRCs may be generic, collecting basic 217 statistics, or they may be specific to a particular usage. The PDP 218 decides which PRC(s) best suit(s) its requirements. The PEP may 219 support only one usage PRC, in which case all statistics are gathered 220 using instances of that PRC. Alternatively, the PEP may support 221 multiple usage PRCs. The PDP then decides which PRC to associate with 222 a particular selection criterion. 224 The accounting type report linkage permits the same selection 225 criteria instance to be re-used for various usage policies. For 226 example, the same IP Filter selection criteria could be the basis of 227 different usage policies such as packet count, drop count, and remark 228 count. The accounting type report linkage references the selection 229 criteria instance as well as defines the policy class of the usage 230 PRC. As noted above, the selection criteria policy may be used for 231 enforcement policies as well as usage policies. This is the case with 232 the frwkIPFilterTable. 234 ----------------- ------------------ ----------------- 235 | | | | | | 236 | Select Criteria | |Linkage Instance | |Usage Instance | 237 | | |-instance ID | |- instance ID | 238 | -instance ID |<--|-PRID of selection|--->|- PRID of Linkage| 239 | -conditions... | |-PRC of usage | |- counts... | 240 | | | | | | 241 ----------------- ------------------ ----------------- 243 Figure 1 245 Figure 1 illustrates the relationship between a selection criteria, 246 linkage and usage policies. 248 The PDP is not aware of the instance identifier of the usage policy 249 when installing the selection criteria and accounting type report 250 linkage policies. The usage policy is enabled on the PEP by the 251 installation of an accounting type report linkage and the PEP 252 designates the instance identifier. The usage policy class always 253 contains an attribute of type Prid. This attribute contains the value 254 of the accounting type report linkage PRID [COPS-PR] installed by the 255 PDP that is associated with the usage policy. Note that the Prid type 256 is a textual convention for an object identifier that is the PRC of 257 the table used for the selection criteria and where the last sub- 258 identifier is an instance ID of the accounting type report linkage. 260 4 Summary of the Accounting Framework Policy Information Base 262 4.1 SPPI ACCESS clause report-only 264 The selection criteria and linkage policy classes follow the 265 definitions specified by [SPPI.] This structure specifies well- 266 defined policy classes and their instances residing in a common, 267 virtual repository [FR-PIB.] The additional PIB-ACCESS clause 268 attribute of "report-only" denotes the usage policy class reported by 269 the PEP. 271 4.2 Textual Conventions Counts 273 The usage policy attributes are often defined in the terms of counts. 274 This type is a non-negative value that is incremented. This value is 275 to "stick" at the maximum value if the maximum value is reached 276 before the reporting interval. It is reset to the value zero after 277 the usage is reported to the PDP and continues the incremental 278 operation. A textual convention defining the counts is defined in the 279 Accounting Framework PIB. 281 4.3 Accounting Type Report Group and PRCs 282 It is useful to define reporting intervals and restart 283 characteristics as well as the common usage and selection criteria 284 polices. These policy classes are common to account type reporting 285 for various technologies and apply to ALL SUBJECT-CATEGORIES. The 286 policy classes belong to a new group, Accounting Type Report Group. 287 The policy classes in the Accounting Type Report Group are: 289 1) Accounting Type Report Device Intervals Table 290 2) Accounting Type Report Linkage Table 291 3) Accounting Type Filter Statistics Usage Table 293 4.3.1 The Accounting Type Report Resume Table 295 This table contains one row. It indicates that the PDP, to which a 296 PEP having cached usage policy has reconnected, is ready to receive 297 the accounting type report messages from the PEP. 299 4.3.2 The Accounting Type Report Linkage Table 301 This table links the selection criteria instance with the usage 302 instance. It specifies the PRID of the selection criteria and the PRC 303 of the usage instance. This table permits the reuse of a selection 304 criteria instance for multiple usage policies. 306 The linkage table also permits the definition of a maximum reporting 307 interval to use when issuing the accounting type reports for the 308 usage instance. This interval is defined in units of the Accounting 309 Timer Interval specified in the client accept message. 311 4.3.3 The Filter Usage Table 313 This table describes the packet counts, byte counts, last timestamp 314 when a packet was received and the PRID of the associated Accounting 315 Type Report Linkage instance. The count and timestamp information is 316 monitored and recorded by the PEP and supplied to the PDP with the 317 accounting type report message within the maximum interval specified. 319 5 The Accounting Framework PIB Module 321 ACCOUNTING-FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN 323 IMPORTS 324 ExtUTCTime, Unsigned32, Unsigned64, 325 Integer32, MODULE-IDENTITY, OBJECT-TYPE 326 FROM COPS-PR-SPPI 327 TruthValue, TEXTUAL-CONVENTION 328 FROM SNMPv2-TC 329 PolicyInstanceId, PolicyReferenceId 330 FROM COPS-PR-SPPI-TC; 331 RoleCombination 332 FROM POLICY-DEVICE-AUX-MIB; 334 acctPolFrameworkPib MODULE-IDENTITY 335 SUBJECT-CATEGORIES { all } 336 LAST-UPDATED "200011171000Z" 337 ORGANIZATION "IETF RAP WG" 338 CONTACT-INFO " 339 Diana Rawlins 340 WorldCom 341 901 International Parkway 342 Richardson, TX 75081 343 Phone: 972 729 1044 344 Email: diana.rawlins@wcom.com 346 Amol Kulkarni 347 JF3-206 348 2111 NE 25th Ave 349 Hillsboro, Oregon 97124 350 Phone: 503-712-1168 351 Email: amol.kulkarni@intel.com 353 Kwok Ho Chan 354 Nortel Networks, Inc. 355 600 Technology Park Drive 356 Billerica, MA 01821 USA 357 Phone: 978-288-8175 358 Email: khchan@nortelnetworks.com " 360 DESCRIPTION 361 "The PIB module containing the base set of policy rule 362 classes that are required for support of all accounting 363 and reporting policies" 365 ::= { tbd } 366 -- 367 -- The accounting type report group 368 -- 370 frwkAtRptGroupClasses 371 OBJECT IDENTIFIER ::= { acctPolFrameworkPib 2 } 373 -- 374 -- Textual Conventions 375 -- 376 Count ::= TEXTUAL-CONVENTION 377 STATUS current 378 DESCRIPTION 379 "A count represents a value used by attributes that 380 record policy usage. A count is of value zero or 381 greater and is incremented according to defined 382 policy usage. When the maximum value is reached, the 383 value sticks. The value is reset to zero upon 384 reporting the value to the PDP." 386 SYNTAX Unsigned64 ( 0..18446744073709551615) 388 -- 389 -- resume reporting indicator 390 -- 392 frwkAtRptResumeTable OBJECT-TYPE 393 SYNTAX SEQUENCE OF FrwkAtRptResumeEntry 394 PIB-ACCESS install 395 STATUS current 396 DESCRIPTION 397 "This class contains a single PRI that indicates 398 that the PEP is to resume the sending of 399 accounting type reports." 401 ::= { frwkAtRptGroupClasses 1} 403 frwkAtRptResumeEntry OBJECT-TYPE 404 SYNTAX FrwkAtRptResumeEntry 405 STATUS current 406 DESCRIPTION 407 "An instance of this class can indicate when to 408 resume sending accounting type reports 409 by the PEP." 410 PIB-INDEX { frwkAtRptResumeId} 412 ::= { frwkAtRptResumeTable 1} 414 FrwkAtRptResumeEntry ::= SEQUENCE { 415 frwkAtRptResumeId InstanceId, 416 frwkAtRptResumeIndicator INTEGER 417 } 419 frwkAtRptResumeId OBJECT-TYPE 420 SYNTAX InstanceID 421 STATUS current 422 DESCRIPTION 423 " An arbitrary integer index that uniquely identifies an 424 instance of the frwkAtRptResumeTable class." 426 ::= { frwkAtRptResumeEntry 1} 428 frwkAtRptResumeIndicator OBJECT-TYPE 429 SYNTAX INTEGER { 430 NO_REPORTS(0), 431 SEND_REPORTS(1) 432 } 433 STATUS current 434 DESCRIPTION 435 "The value indicates if the PEP is to send cached 436 usage policies via accounting type report messages. 437 The enumeration values are: 438 (0) Don�t send accounting type report messages 439 (1) Resume accounting type report messages. Send 440 cached usage policies now " 442 ::= { frwkAtRptResumeEntry 2 } 444 -- 445 -- The Accounting Type Report Linkage Table 446 -- 448 frwkAtRptLinkTable OBJECT-TYPE 449 SYNTAX SEQUENCE OF FrwkAtRptLinkEntry 450 PIB-ACCESS notify 451 STATUS current 452 DESCRIPTION 453 "This class associates the selection criteria with the 454 usage policy. It also permit the defining of the max 455 interval used for reporting the usage instance." 457 ::= { frwkAtRptGroupClasses 2} 459 frwkAtRptLinkEntry OBJECT-TYPE 460 SYNTAX FrwkAtRptLinkEntry 461 STATUS current 462 DESCRIPTION 463 "This class associates the selection criteria with the 464 usage policy. It also permit the defining of the max 465 interval used for reporting the usage instance." 466 PIB-INDEX {frwkAtRptLinkId} 467 UNIQUENESS { frwkAtRptLinkId, 468 frwkAtRptLinkSel, 469 frwkAtRptLinkUsage } 470 ::= {frwkAtRptLinkTable 1} 472 FrwkAtRptLinkEntry ::= SEQUENCE { 473 frwkAtRptLinkId InstanceID, 474 frwkAtRptLinkSel Prid, 475 frwkAtRptLinkUsage OBJECT IDENTIFIER, 476 frwkAtRptLinkInterval Integer32 477 } 479 frwkAtRptLinkId OBJECT-TYPE 480 SYNTAX InstanceID 481 STATUS current 482 DESCRIPTION 483 " An arbitrary integer index that uniquely identifies an 484 instance of the frwkAtRptLinkTable class." 485 ::= { frwkAtRptLinkEntry 1} 487 frwkAtRptLinkSel OBJECT-TYPE 488 SYNTAX Prid 489 STATUS current 490 DESCRIPTION 491 "The PRID of the selection criteria instance that 492 defines the conditions to use by the PEP for 493 monitoring the usage." 495 ::= { frwkAtRptLinkEntry 2} 497 frwkAtRptLinkUsage OBJECT-TYPE 498 SYNTAX OBJECT IDENTIFIER 499 STATUS current 500 DESCRIPTION 501 "The PRC of the usage policy class that the PEP uses to 502 monitor,record and report." 504 ::= { frwkAtRptLinkEntry 3} 506 frwkAtRptInterval OBJECT-TYPE 507 SYNTAX Integer32 508 STATUS current 509 DESCRIPTION 510 "Maximum interval in units of the value of the 511 Accounting Timer specificed by the PDP in the client 512 accept message. A frwkAtRptInterval of 1 is equal to 513 the value of the Accounting Timer. This value must be 1 514 or greater. " 516 ::= { frwkAtRptLinkEntry 4} 518 -- 519 -- The filter statistics usage 520 -- 522 frwkAtRptFilterStatsUsageTable OBJECT-TYPE 523 SYNTAX SEQUENCE OF FrwkAtRptFilterStatsUsageEntry 524 PIB-ACCESS report-only 525 STATUS current 526 DESCRIPTION 527 "This class defines the usage attributes that the PEP 528 is to monitor, record and report. It contains the 529 of the PRID of the linkage instance associating 530 the selection criteria instance with the usage 531 instance." 533 ::= { frwkAtRptGroupClasses 3} 535 frwkAtRptFilterStatsUsageEntry OBJECT-TYPE 536 SYNTAX FrwkAtRptFilterStatsUsageEntry 537 STATUS current 538 DESCRIPTION 539 "Defines the attributes the PEP is to monitor, 540 record and report." 542 PIB-INDEX {frwkAtRptFilterStatsUsageId} 543 UNIQUENESS { frwkAtRptFilterStatsUsageLinkPRID } 545 ::= {frwkAtRptFilterStatsUsageTable 1} 547 FrwkAtRptFilterStatsUsageEntry ::= SEQUENCE { 548 frwkAtRptFilterStatsUsageId InstanceID, 549 frwkAtRptFilterStatsUsageLinkPRID Prid, 550 frwkAtRptFilterStatsUsagePacketCount Counts, 551 frwkAtRptFilterStatsUsageByteCount Counts, 552 fwkAtRptFilterStatsUsageTimeStamp ExtUTCTime 554 } 556 frwkAtRptFilterStatsUsageId OBJECT-TYPE 557 SYNTAX InstanceId 558 STATUS current 559 DESCRIPTION 560 "Arbitrary integer index that uniquely identifies 561 an instance of the class." 562 ::= { frwkAtRptFilterStatsUsageEntry 1 } 564 frwkAtRptFilterStatsUsageLinkPRID OBJECT-TYPE 565 SYNTAX Prid 566 STATUS current 567 DESCRIPTION 568 "The PRID of the Linkage policy instance used to base 569 this usage policy instance upon." 571 ::= { frwkAtRptFilterStatsUsageEntry 2 } 573 frwkAtRptFilterStatsUsagePacketCount OBJECT-TYPE 574 SYNTAX Unsigned32 575 STATUS current 576 DESCRIPTION 577 "The count of packets matching the specified filter 578 during the reporting interval." 580 ::= {frwkAtRptFilterStatsUsageEntry 3} 582 frwkAtRptFilterStatsUsageByteCount OBJECT-TYPE 583 SYNTAX Unsigned64 584 STATUS current 585 DESCRIPTION 586 "The byte count of packets matching the 587 specified filter during the reporting interval." 589 ::= { frwkAtRptFilterStatsUsageEntry 4} 591 frwkAtRptFilterStatsSelectTimeStamp OBJECT-TYPE 592 SYNTAX ExtUTCTime 593 STATUS current 594 DESCRIPTION 595 "The last timestamp when a packet was received." 597 ::= { frwkAtRptFilterStatsSelectEntry 5} 599 END 601 6 Security Considerations 603 The accounting information is sensitive and requires that 604 authorized messaging occur between the PEP and the PDP. This 605 protection can be accomplished with IPSEC between the PEP and the 606 PDP or using the security mechanisms described in the base COPS 607 protocol. 609 7 Acknowledgements 610 The authors would like to thank Dave Durham and Russell Fenger of 611 Intel and John K. Gallant of WorldCom for their contribution to 612 this document. 614 8 Authors' Addresses 616 Diana Rawlins 617 WorldCom 618 901 International Parkway 619 Richardson, Texas 75081 620 Phone: 972-729-1044 621 Email: Diana.Rawlins@wcom.com 623 Amol Kulkarni 624 JF3-206 625 2111 NE 25th Ave 626 Hillsboro, Oregon 97124 627 Phone: 503-712-1168 628 Email: amol.kulkarni@intel.com 630 Kwok Ho Chan 631 Nortel Networks, Inc. 632 600 Technology Park Drive 633 Billerica, MA 01821 USA 634 Phone: 978-288-8175 635 Email: khchan@nortelnetworks.com 637 Dinesh G Dutt 638 Cisco Systems, Inc. 639 170 Tasman Dr. 640 San Jose, CA 95134-1706 641 Phone: 408-527-0955 642 Email: ddutt@cisco.com 644 9 References 646 [COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., 647 and A. Sastry, "The COPS (Common Open Policy Service) Protocol" 648 RFC 2748, January 2000. 650 [COPS-PR] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. 651 Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for 652 Policy Provisioning," draft-ietf-rap-cops-pr-05.txt, March 2000. 654 [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning 655 Information," draft-ietf-rap-sppi-05.txt, February 2001. 657 [FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A. 658 Smith, F. Reichmeyer "Framework Policy Information Base", draft- 659 ietf-rap-frameworkpib-03.txt, November 2000 661 [DSPIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Han, A. 662 Smith, F. Reichmeyer, "Differentiated Services Quality of Service 663 Policy Information Base", draft-ietf-diffserv-pib-02.txt, November 664 2000 666 [SIP-AAA-QOS] Gross, G.,Sinnreich, H. Rawlins D., Havinis, T. " QoS 667 and AAA Usage with SIP Based IP Communications" draft-gross-sipaq- 668 00.txt, November 2000.