1 / 13

PSAMP Framework Document Draft

This draft outlines technical changes, clarifications, and organizational updates to the PSAMP framework document. It covers selection states, packet reports, PSAMP device definitions, input sequence numbers, and more. The document emphasizes the generic requirements, selection operations, reporting process, and export process. It also addresses open issues and the status of the last call for changes.

rlee
Download Presentation

PSAMP Framework Document Draft

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PSAMP Framework Documentdraft-ietf-psamp-framework-06.txt Duffield, Greenberg, Grossglauser, Rexford: AT&T Chiou: Avici Claise, Marimuthu, Sadasivan: Cisco

  2. Summary • Changes to document since previous version • Additional changes required • Open issues • Status of last call

  3. Changes to Document since Version 05

  4. Status • Framework draft is informational • Other drafts will become PSAMP normative references • Language issues • “must”, “should”, and “may”, for guidance

  5. Technical Changes and Clarifications • Section 3.3. Selection State • Selection state is post processing of packets • Section 3.4 Packet Reports • Definition explicitly includes selection state • Section 3.7. PSAMP Device • Definition added • Similar to IPFIX device • Section 5.3. Input Sequence Numbers • In a composite selector, report input sequence numbers for each component selector

  6. Organizational Changes • Substantial rewriting in response to feedback • Abstract • Rewritten to reflect changes • Section 1. • Added PSAMP documents overview • Section 3.1 • Added PSAMP architecture overview • Section 3.2-3.7 Terminology • Terminology broken out by selection/reporting/export process • Ordering not alphabetic, but forward dependencies now removed • Section 3.10 • Added description/pointer on interaction with IPFIX

  7. Organizational Changes (2) • Section 4. Generic requirements • Emphasize generic nature of requirements • Section 4.1. Generic selection requirements • Minor tweaking of “extensibility”, “flexibility” and “parallel measurement process” (last one needs moving) • Encrypted packets: • can be ignored when detected • detection mechanisms left unspecified • Section 4.2 Generic reporting requirements • Minor tweaking of “self-defining” and “accuracy” • “Transparency” retermed as “indication of information loss”

  8. Organizational Changes (3) • Section 5. Packet selection operations • Section 5.1. Terminology • Normative reference will be [PSAMP-TECH] • Options for Framework doc: include none/all/used? • Intent: include only terms used in framework draft • Omission was over-aggressive: need to restore some hashing terms • Section 5.2. Selection Operations • Retained high level descriptions of selection operation • Removed material from old Section 4.2 on hashing applications • Will appear in [PSAMP-TECH] • Removed old Section 4.6 on criteria for choice of selectors

  9. Organizational Changes (4) • Section 6. Reporting Process • Question arose: whether to use IPFIX terminology • Resolution: retain PSAMP terminology • Better to have clean and consistent set of definitions • IPFIX still in flux • Sections 6.1. and 6.2 • Clarification that Basic Reporting (i.e. first N bytes of packets) is mandatory to support but optional to use. May want to use extended reporting instead, if supported.

  10. Organizational Changes (5) • Section 8. Export Process • Section 8.1. Reflect choice of IPFIX for export • IPFIX must support STCP-PR • congestion avoiding unreliable transport • Substantial reorganization • Omit old Section 7.7 on collector based rate reconfiguration • Section 13. Normative References • Placeholders for other PSAMP documents • Consequence: submission as RFC must wait till other docs complete

  11. Additional Changes Required • Section 11. Applications • Rewrite and streamline to bring out unique advantages of PSAMP • Enhanced and new applications • Section 13. Intellectual Property Statements • Update to reflect recent IP statement by AT&T to IETF • http://www.ietf.org/ietf/IPR/att-ipr-draft-ietf-psamp-framework.txt • Add reference to Cisco’s assertion of IP to IETF • http://www.ietf.org/ietf/IPR/cisco-ipr-draft-ietf-psamp-protocol.txt • Essentially the same (usual) terms • License under fair and reasonable terms, non-discriminatory, reciprocity

  12. Open Issues • Section 8. PSAMP Requires explicit rate limit for export • Useful e.g. to limit rate implosion at collector when multiple PSAMP devices export to a collector • Even when no network congestion • Does IPFIX support an explicit rate limit? • Status of Last Call • Wait for other PSAMP WG documents to be completed?

  13. Please read the Framework Draft! • Technical content (almost) stable • Organization substantially changed in this version • Needs careful reading • Please send comments to list

More Related