idnits 2.17.1 draft-yourtchenko-cisco-ies-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 678 has weird spacing: '... as per apply...' -- The document date (July 11, 2011) is 4673 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 5101 (Obsoleted by RFC 7011) == Outdated reference: A later version (-10) exists of draft-claise-export-application-info-in-ipfix-01 == Outdated reference: A later version (-18) exists of draft-ietf-ipfix-flow-selection-tech-06 == Outdated reference: A later version (-07) exists of draft-kashima-ipfix-data-link-layer-monitoring-05 -- Obsolete informational reference (is this intentional?): RFC 5102 (Obsoleted by RFC 7012) Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Yourtchenko 3 Internet-Draft P. Aitken 4 Intended status: Informational B. Claise 5 Expires: January 12, 2012 Cisco Systems, Inc. 6 July 11, 2011 8 IPFIX Cisco Vendor Specific Information Elements 9 draft-yourtchenko-cisco-ies-01 11 Abstract 13 This document describes some additional Information Elements of Cisco 14 Systems, Inc. that are not listed in RFC3954. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on January 12, 2012. 33 Copyright Notice 35 Copyright (c) 2011 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 3. Information Elements . . . . . . . . . . . . . . . . . . . . . 3 53 3.1. fsFlowEntryTotalCount . . . . . . . . . . . . . . . . . . 3 54 3.2. samplingInterval . . . . . . . . . . . . . . . . . . . . . 3 55 3.3. samplingAlgorithm . . . . . . . . . . . . . . . . . . . . 4 56 3.4. engineType . . . . . . . . . . . . . . . . . . . . . . . . 4 57 3.5. engineId . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 3.6. ipv4RouterSc . . . . . . . . . . . . . . . . . . . . . . . 5 59 3.7. flowSamplerId . . . . . . . . . . . . . . . . . . . . . . 5 60 3.8. flowSamplerMode . . . . . . . . . . . . . . . . . . . . . 5 61 3.9. flowSamplerRandomInterval . . . . . . . . . . . . . . . . 5 62 3.10. classId . . . . . . . . . . . . . . . . . . . . . . . . . 6 63 3.11. samplerName . . . . . . . . . . . . . . . . . . . . . . . 6 64 3.12. flagsAndSamplerId . . . . . . . . . . . . . . . . . . . . 6 65 3.13. forwardingStatus . . . . . . . . . . . . . . . . . . . . . 6 66 3.14. srcTrafficIndex . . . . . . . . . . . . . . . . . . . . . 8 67 3.15. dstTrafficIndex . . . . . . . . . . . . . . . . . . . . . 8 68 3.16. className . . . . . . . . . . . . . . . . . . . . . . . . 8 69 3.17. layer2packetSectionOffset . . . . . . . . . . . . . . . . 9 70 3.18. layer2packetSectionSize . . . . . . . . . . . . . . . . . 9 71 3.19. layer2packetSectionData . . . . . . . . . . . . . . . . . 9 72 4. Other Information Elements . . . . . . . . . . . . . . . . . . 9 73 4.1. Application Information IEs . . . . . . . . . . . . . . . 10 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 75 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 76 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 77 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 78 7.2. Informative References . . . . . . . . . . . . . . . . . . 11 79 Appendix A. XML Specification of IPFIX Information Elements . . . 12 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 82 1. Introduction 84 The section 4 of [RFC5102] defines the IPFIX Information Elements in 85 the range of 1-127 to be compatible with the NetFlow version 9 86 fields, as specified in the "Cisco Systems NetFlow Services Export 87 Version 9" [RFC3954]. As [RFC3954] was specified in 2004, it does 88 not contain all NetFlow version 9 specific fields in the range 1-127. 89 The question was asked whether IPFIX Devices should exclusively 90 report the IPFIX IANA IEs [IPFIX-IANA] ? In other words, when 91 upgrading from a NetFlow metering process to an IPFIX Metering 92 Process, should the IPFIX Devices stop reporting NetFlow version 9 93 specific IEs that were not registered in IANA [IPFIX-IANA] ? 95 This document is intended to fill the gap in this IE range. That 96 way, IPFIX implementations could export all the IEs specified in 97 IANA, regardless of the range. 99 2. Terminology 101 IPFIX-specific terminology used in this document is defined in 102 Section 2 of [RFC5101]. As in [RFC5101], these IPFIX-specific terms 103 have the first letter of a word capitalized when used in this 104 document. 106 3. Information Elements 108 3.1. fsFlowEntryTotalCount 110 Description: 111 This Information Element specifies the current number of all Flow 112 Records that form the parent population as input to the Flow 113 Selection Process. 114 Abstract Data Type: unsigned64 115 ElementId: 3 116 Semantics: quantity 117 Status: current 118 Units: flows 119 RFC EDITOR NOTE: if the Flow Selection Techniques document 120 [I-D.ietf-ipfix-flow-selection-tech] is published before this, 121 then remove this entry. This Information Element is similar to 122 'fsFlowEntryTotalCount' there. 124 3.2. samplingInterval 125 Description: 126 When using sampled NetFlow, the rate at which packets are sampled 127 - e.g. a value of 100 indicates that one of every 100 packets is 128 sampled. Deprecated in favor of 305 samplingPacketInterval. 129 Abstract Data Type: unsigned32 130 ElementId: 34 131 Semantics: quantity 132 Status: deprecated 133 Units: packets 135 3.3. samplingAlgorithm 137 Description: 138 The type of algorithm used for sampled NetFlow: 0x01 139 Deterministic Sampling, 0x02 Random Sampling. The values are not 140 compatible with the selectorAlgorithm field, where "Deterministic" 141 has been replaced by "Systematic count-based" (1) or "Systematic 142 time-based" (2), and "Random" is (3). Conversion is required, see 143 PSAMP parameters [PSAMP-IANA]. Deprecated in favor of 304 144 selectorAlgorithm. 145 Abstract Data Type: unsigned8 146 ElementId: 35 147 Semantics: identifier 148 Status: deprecated 150 3.4. engineType 152 Description: 153 Type of flow switching engine in a router/switch: RP = 0, VIP/ 154 Line card = 1, PFC/DFC = 2. Reserved for internal use on the 155 collector. 156 Abstract Data Type: unsigned8 157 ElementId: 38 158 Semantics: identifier 159 Status: deprecated 161 3.5. engineId 163 Description: 164 VIP or line card slot number of the flow switching engine in a 165 router/switch. Reserved for internal use on the collector. 166 Abstract Data Type: unsigned8 167 ElementId: 39 168 Semantics: identifier 169 Status: deprecated 171 3.6. ipv4RouterSc 173 Description: 174 This is a platform-specific field. It is used to store the 175 address of a router that is being shortcut when performing the 176 MultiLayer Switching. 177 Abstract Data Type: ipv4Address 178 ElementId: 43 179 Semantics: ipv4Address 180 Status: deprecated 181 Reference: [CCO-MLS] describes the MultiLayer Switching. 183 3.7. flowSamplerId 185 Description: 186 The unique identifier associated with samplerName. Deprecated in 187 favor of 302 selectorId. 188 Abstract Data Type: unsigned8 189 ElementId: 48 190 Semantics: identifier 191 Status: deprecated 193 3.8. flowSamplerMode 195 Description: 196 The type of algorithm used for sampling data: 0x01 - 197 deterministic, 0x02 - random sampling. Use with 198 flowSamplerRandomInterval. Deprecated in favor of 304 199 selectorAlgorithm. The values are not compatible: 200 selectorAlgorithm=3 is random sampling. 201 Abstract Data Type: unsigned8 202 ElementId: 49 203 Semantics: identifier 204 Status: deprecated 206 3.9. flowSamplerRandomInterval 208 Description: 209 Packet interval at which to sample - in case of random sampling. 210 Used in connection with flowSamplerMode 0x02 (random sampling) 211 value. Deprecated in favour of 305 samplingPacketInterval. 212 Abstract Data Type: unsigned32 213 ElementId: 50 214 Semantics: quantity 215 Status: deprecated 217 3.10. classId 219 Description: 220 Characterizes the traffic class, i.e. QoS treatment. Deprecated 221 in favour of 302 selectorId. 222 Abstract Data Type: unsigned8 223 ElementId: 51 224 Semantics: identifier 225 Status: deprecated 227 3.11. samplerName 229 Description: 230 Name of the flow sampler. Deprecated in favor of 335 231 selectorName. 232 Abstract Data Type: string 233 ElementId: 84 234 Status: deprecated 236 3.12. flagsAndSamplerId 238 Description: 239 Flow flags and the value of the sampler ID (flowSamplerId) 240 combined in one bitmapped field. Reserved for internal use on the 241 collector. 242 Abstract Data Type: unsigned32 243 ElementId: 87 244 Semantics: identifier 245 Status: deprecated 247 3.13. forwardingStatus 249 Description: 250 The field describes the forwarding status of the flow and any 251 attached reasons. The Reduced Size Encoding rules as per 252 [RFC5101] apply. 254 The basic encoding is 8 bits. The future extensions 255 could add one or three bytes. The layout of the basic 256 encoding is as follows: 258 MSB - 0 1 2 3 4 5 6 7 - LSB 259 +---+---+---+---+---+---+---+---+ 260 | Status| Reason code or flags | 261 +---+---+---+---+---+---+---+---+ 263 Status: 265 00b = Unknown 266 01b = Forwarded 267 10b = Dropped 268 11b = Consumed 270 Reason Code (status = 01b, Forwarded) 272 01 000000b = 64 = Unknown 273 01 000001b = 65 = Fragmented 274 01 000010b = 66 = Not Fragmented 276 Reason Code (status = 10b, Dropped) 278 10 000000b = 128 = Unknown 279 10 000001b = 129 = ACL deny 280 10 000010b = 130 = ACL drop 281 10 000011b = 131 = Unroutable 282 10 000100b = 132 = Adjacency 283 10 000101b = 133 = Fragmentation and DF set 284 10 000110b = 134 = Bad header checksum 285 10 000111b = 135 = Bad total Length 286 10 001000b = 136 = Bad header length 287 10 001001b = 137 = bad TTL 288 10 001010b = 138 = Policer 289 10 001011b = 139 = WRED 290 10 001100b = 140 = RPF 291 10 001101b = 141 = For us 292 10 001110b = 142 = Bad output interface 293 10 001111b = 143 = Hardware 295 Reason Code (status = 11b, Consumed) 297 11 000000b = 192 = Unknown 298 11 000001b = 193 = Punt Adjacency 299 11 000010b = 194 = Incomplete Adjacency 300 11 000011b = 195 = For us 302 Examples: 304 value : 0x40 = 64 305 binary: 01000000 306 decode: 01 -> Forward 307 000000 -> No further information 309 value : 0x89 = 137 310 binary: 10001001 311 decode: 10 -> Drop 312 001001 -> Fragmentation and DF set 314 Abstract Data Type: unsigned32 315 ElementId: 89 316 Semantics: identifier 317 Status: current 318 Reference: 319 See NetFlow Version 9 Record Format [CCO-NF9FMT]. 321 3.14. srcTrafficIndex 323 Description: 324 BGP Policy Accounting Source Traffic Index 325 Abstract Data Type: unsigned32 326 ElementId: 92 327 Semantics: identifier 328 Status: current 329 Reference: 330 BGP policy accounting as described in [CCO-BGPPOL] 332 3.15. dstTrafficIndex 334 Description: 335 BGP Policy Accounting Destination Traffic Index 336 Abstract Data Type: unsigned32 337 ElementId: 93 338 Semantics: identifier 339 Status: current 340 Reference: 341 BGP policy accounting as described in [CCO-BGPPOL] 343 3.16. className 345 Description: 346 Traffic Class Name, associated with the classId Information 347 Element. Deprecated in favor of 335 selectorName. 348 Abstract Data Type: string 349 ElementId: 100 350 Status: deprecated 352 3.17. layer2packetSectionOffset 354 Description: 355 Layer 2 packet section offset. Potentially a generic packet 356 section offset. 357 Abstract Data Type: unsigned16 358 ElementId: 102 359 Semantics: quantity 360 Status: current 361 EDITOR'S NOTE: [I-D.kashima-ipfix-data-link-layer-monitoring] 362 contains a corresponding field 'sectionOffset' with a better 363 description. One solution is to assign the value 102 for the 364 'sectionOffset' in [I-D.kashima-ipfix-data-link-layer-monitoring]. 366 3.18. layer2packetSectionSize 368 Description: 369 Layer 2 packet section size. Potentially a generic packet section 370 size. 371 Abstract Data Type: unsigned16 372 ElementId: 103 373 Semantics: quantity 374 Status: current 375 EDITOR'S NOTE: [I-D.kashima-ipfix-data-link-layer-monitoring] 376 contains a corresponding field 'sectionObservedOctets' with a 377 better description. One solution is to assign the value 103 to 378 'sectionObservedOctets' in 379 [I-D.kashima-ipfix-data-link-layer-monitoring]. 381 3.19. layer2packetSectionData 383 Description: 384 Layer 2 packet section data. 385 Abstract Data Type: octetArray 386 ElementId: 104 387 Status: current 388 EDITOR's NOTE: [I-D.kashima-ipfix-data-link-layer-monitoring] 389 contains a corresponding field 'dataLinkFrameSection' with a 390 better description. One solution is to assign the value 104 to 391 'dataLinkFrameSection' in 392 [I-D.kashima-ipfix-data-link-layer-monitoring]. 394 4. Other Information Elements 395 4.1. Application Information IEs 397 ElementId: 101 399 ElementId: 94 .. 97 401 Please refer to the Export of Application Information in IPFIX 402 [I-D.claise-export-application-info-in-ipfix] 404 5. IANA Considerations 406 This document specifies several new IPFIX Information Elements in the 407 IPFIX Information Element registry as defined in Section 3 above. 408 The following Information Elements must be assigned: 410 o Information Element Number 3 for the fsFlowEntryTotalCount 411 Information Element 412 o Information Element Number 34 for the samplingInterval Information 413 Element 414 o Information Element Number 35 for the samplingAlgorithm 415 Information Element 416 o Information Element Number 38 for the engineType Information 417 Element 418 o Information Element Number 39 for the engineId Information Element 419 o Information Element Number 43 for the ipv4RouterSc Information 420 Element 421 o Information Element Number 48 for the flowSamplerId Information 422 Element 423 o Information Element Number 49 for the flowSamplerMode Information 424 Element 425 o Information Element Number 50 for the flowSamplerRandomInterval 426 Information Element 427 o Information Element Number 51 for the classId Information Element 428 o Information Element Number 84 for the samplerName Information 429 Element 430 o Information Element Number 87 for the flagsAndSamplerId 431 Information Element 432 o Information Element Number 89 for the forwardingStatus Information 433 Element 434 o Information Element Number 92 for the srcTrafficIndex Information 435 Element 436 o Information Element Number 93 for the dstTrafficIndex Information 437 Element 438 o Information Element Number 100 for the className Information 439 Element 441 o Information Element Number 102 for the layer2packetSectionOffset 442 Information Element 443 o Information Element Number 103 for the layer2packetSectionSize 444 Information Element 445 o Information Element Number 104 for the layer2packetSectionData 446 Information Element 448 6. Security Considerations 450 This document specifies the definitions and does not alter the 451 security considerations of the base protocol. Please refer to the 452 security considerations sections of RFC 3954 [RFC3954] and RFC 5102 453 [RFC5102]. 455 7. References 457 7.1. Normative References 459 [RFC5101] Claise, B., "Specification of the IP Flow Information 460 Export (IPFIX) Protocol for the Exchange of IP Traffic 461 Flow Information", RFC 5101, January 2008. 463 7.2. Informative References 465 [CCO-BGPPOL] 466 Cisco, "BGP Policy Accounting and BGP Policy Accounting 467 Output Interface Accounting Features", . 471 [CCO-MLS] Cisco, "IP MultiLayer Switching Sample Configuration", . 475 [CCO-NF9FMT] 476 Cisco, "NetFlow version 9 Flow-Record format", . 480 [I-D.claise-export-application-info-in-ipfix] 481 Claise, B., Aitken, P., and N. Ben-Dvora, "Export of 482 Application Information in IPFIX", 483 draft-claise-export-application-info-in-ipfix-01 (work in 484 progress), March 2011. 486 [I-D.ietf-ipfix-flow-selection-tech] 487 D'Antonio, S., Zseby, T., Henke, C., and L. Peluso, "Flow 488 Selection Techniques", 489 draft-ietf-ipfix-flow-selection-tech-06 (work in 490 progress), May 2011. 492 [I-D.kashima-ipfix-data-link-layer-monitoring] 493 Kashima, S., Nakata, K., and A. Kobayashi, "Information 494 Elements for Data Link Layer Traffic Measurement", 495 draft-kashima-ipfix-data-link-layer-monitoring-05 (work in 496 progress), March 2011. 498 [IPFIX-IANA] 499 IANA, "IP Flow Information Export (IPFIX) Entities", 500 . 502 [PSAMP-IANA] 503 IANA, "Packet Sampling (PSAMP) Parameters", . 507 [RFC3954] Claise, B., "Cisco Systems NetFlow Services Export Version 508 9", RFC 3954, October 2004. 510 [RFC5102] Quittek, J., Bryant, S., Claise, B., Aitken, P., and J. 511 Meyer, "Information Model for IP Flow Information Export", 512 RFC 5102, January 2008. 514 Appendix A. XML Specification of IPFIX Information Elements 516 518 523 527 528 529 This Information Element specifies the current number of all 530 Flow Records that form the parent population as input to the 531 Flow Selection Process. 532 533 535 536 540 541 542 When using sampled NetFlow, the rate at which packets are 543 sampled - e.g. a value of 100 indicates that one of every 100 544 packets is sampled. Deprecated in favor of 305 545 samplingPacketInterval. 546 547 548 549 553 554 555 The type of algorithm used for sampled NetFlow: 0x01 556 Deterministic Sampling, 0x02 Random Sampling. The values are not 557 compatible with the selectorAlgorithm field, where 558 "Deterministic" has been replaced by "Systematic count-based" 559 (1) or "Systematic time-based" (2), and "Random" is (3). 560 Conversion is required, see PSAMP parameters. Deprecated in 561 favor of 304 selectorAlgorithm. 562 563 564 565 569 570 571 Type of flow switching engine in a router/switch: RP = 0, 572 VIP/Line card = 1, PFC/DFC = 2. Reserved for internal use on the 573 collector. 574 575 576 577 581 582 583 VIP or line card slot number of the flow switching engine in a 584 router/switch. Reserved for internal use on the collector. 585 586 587 588 592 593 594 This is a platform-specific field. It is used to store the 595 address of a router that is being shortcut when performing the 596 MultiLayer Switching. 597 598 599 600 604 605 606 The unique identifier associated with samplerName. Deprecated in 607 favor of 302 selectorId. 608 609 610 611 615 616 617 The type of algorithm used for sampling data: 0x01 - 618 deterministic, 0x02 - random sampling. Use with 619 flowSamplerRandomInterval. Deprecated in favor of 304 620 selectorAlgorithm. The values are not compatible: 621 selectorAlgorithm=3 is random sampling. 622 623 624 625 629 630 631 Packet interval at which to sample - in case of random sampling. 632 Used in connection with flowSamplerMode 0x02 (random sampling) 633 value. Deprecated in favour of 305 samplingPacketInterval. 634 635 636 637 641 642 643 Characterizes the traffic class, i.e. QoS treatment. Deprecated 644 in favour of 302 selectorId. 645 646 647 648 652 653 654 Name of the flow sampler. Deprecated in favor of 335 655 selectorName. 656 657 658 659 663 664 665 Flow flags and the value of the sampler ID (flowSamplerId) 666 combined in one bitmapped field. Reserved for internal use on 667 the collector. 668 669 670 671 675 676 677 The field describes the forwarding status of the flow and any 678 attached reasons. The Reduced Size Encoding rules as per apply. 680 681 682 The basic encoding is 8 bits. The future extensions 683 could add one or three bytes. The layout of the basic 684 encoding is as follows: 686 MSB - 0 1 2 3 4 5 6 7 - LSB 687 +---+---+---+---+---+---+---+---+ 688 | Status| Reason code or flags | 689 +---+---+---+---+---+---+---+---+ 690 Status: 692 00b = Unknown 693 01b = Forwarded 694 10b = Dropped 695 11b = Consumed 697 Reason Code (status = 01b, Forwarded) 699 01 000000b = 64 = Unknown 700 01 000001b = 65 = Fragmented 701 01 000010b = 66 = Not Fragmented 703 Reason Code (status = 10b, Dropped) 705 10 000000b = 128 = Unknown 706 10 000001b = 129 = ACL deny 707 10 000010b = 130 = ACL drop 708 10 000011b = 131 = Unroutable 709 10 000100b = 132 = Adjacency 710 10 000101b = 133 = Fragmentation and DF set 711 10 000110b = 134 = Bad header checksum 712 10 000111b = 135 = Bad total Length 713 10 001000b = 136 = Bad header length 714 10 001001b = 137 = bad TTL 715 10 001010b = 138 = Policer 716 10 001011b = 139 = WRED 717 10 001100b = 140 = RPF 718 10 001101b = 141 = For us 719 10 001110b = 142 = Bad output interface 720 10 001111b = 143 = Hardware 722 Reason Code (status = 11b, Consumed) 724 11 000000b = 192 = Unknown 725 11 000001b = 193 = Punt Adjacency 726 11 000010b = 194 = Incomplete Adjacency 727 11 000011b = 195 = For us 729 Examples: 731 value : 0x40 = 64 732 binary: 01000000 733 decode: 01 -> Forward 734 000000 -> No further information 736 value : 0x89 = 137 737 binary: 10001001 738 decode: 10 -> Drop 739 001001 -> Fragmentation and DF set 740 741 742 743 747 748 749 BGP Policy Accounting Source Traffic Index 750 751 752 753 757 758 759 BGP Policy Accounting Destination Traffic Index 760 761 762 763 767 768 769 Traffic Class Name, associated with the classId Information 770 Element. Deprecated in favor of 335 selectorName. 771 772 773 774 778 779 780 Layer 2 packet section offset. Potentially a generic packet 781 section offset. 782 783 784 785 789 790 791 Layer 2 packet section size. Potentially a generic packet 792 section size. 793 794 795 796 800 801 802 Layer 2 packet section data. 803 804 805 806 808 Authors' Addresses 810 Andrew Yourtchenko 811 Cisco Systems, Inc. 812 De Kleetlaan, 7 813 Brussels, Diegem B-1831 814 Belgium 816 Phone: +32 2 704 5494 817 Email: ayourtch@cisco.com 818 Paul Aitken 819 Cisco Systems, Inc. 820 96 Commercial Quay 821 Edinburgh EH6 6LX 822 Scotland 824 Phone: +44 131 561 3616 825 Email: paitken@cisco.com 827 Benoit Claise 828 Cisco Systems, Inc. 829 De Kleetlaan, 6a b1 830 Diegem B-1831 831 Belgium 833 Phone: +32 2 704 5622 834 Email: bclaise@cisco.com