IPFIX Protocol Specifications IPFIX IETF-62 March 12th, 2005 <draft-ietf-ipfix-protocol-09.txt> Benoit Claise <bclaise@cisco.com> Stewart Bryant <stbryant@cisco.com>

Slides:



Advertisements
Similar presentations
Draft-ietf-pim-port-06. port-06 update Changes made in response to second wglc comments and following discussion Many minor editorial issues fixed Changed.
Advertisements

Geneva, 24 March 2011 Cisco experiences of IP traffic flow measurement and billing with NetFlow Benoit Claise, Distinguished Engineer, Cisco ITU-T Workshop.
Tunnel congestion Feedback (draft-wei-tunnel-congestion-feedback-01) Xinpeng Wei Lei Zhu Lingli Deng Huawei Huawei China Mobile IETF 89 London, UK.
1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.
XCON Framework Overview & Issues Editors: Mary Barnes Chris Boulton
Hypertext Transfer Protocol Kyle Roth Mark Hoover.
ARP and RARP The left side of this slide gives an ARP message in hexadecimal format, identify the ARP header fields, and work out their corresponding values.
TCP/IP Protocol Suite 1 Chapter 11 Upon completion you will be able to: User Datagram Protocol Be able to explain process-to-process communication Know.
Microsoft Office Word 2013 Expert Microsoft Office Word 2013 Expert Courseware # 3251 Lesson 4: Working with Forms.
Request History – Solution Mary Barnes SIP WG Meeting IETF-57 draft-ietf-sip-history-info-00.txt.
1 PSAMP Protocol Specifications IPFIX IETF-64 November 10th, 2005 Benoit Claise Juergen Quittek Andrew Johnson.
Electronic Mail Originally –Memo sent from one user to another Now –Memo sent to one or more mailboxes Mailbox –Destination point for messages.
Microsoft Word 2000: Mail Merge Basics Peggy Serfazo Marple Molly Calvello Support Professionals Business Applications - Desktop Microsoft Corporation.
David A. Bryan, PPSP Workshop, Beijing, China, June 17th and 18th 2010 Tracker Protocol Proposal.
1 IPFIX Protocol Specifications IPFIX IETF-59 March 3, 2004 Benoit Claise Mark Fullmer Reinaldo Penno Paul Calato Stewart Bryant Ganesh Sadasivan.
Forms and Server Side Includes. What are Forms? Forms are used to get user input We’ve all used them before. For example, ever had to sign up for courses.
1 Virtual Router Redundancy Protocol (VRRP) San Francisco IETF VRRP Working Group March 2003 San Francisco IETF Mukesh Gupta / Nokia Chair.
CCS – Mail Merge Mail Merge This presentation is incomplete without the associated discussion 1 Coloma Community Schools In-service 21 March 2014.
SIP working group IETF#70 Essential corrections Keith Drage.
Draft-ietf-fecframe-config-signaling-02 1 FEC framework Configuration Signaling draft-ietf-fecframe-config-signaling-02.txt IETF 76 Rajiv Asati.
Evaluation of NetFlow Version 9 Against IPFIX Requirements: changes from version 03 to 04 draft-claise-ipfix-eval-netflow-04.txt Benoit Claise, Cisco Systems.
1 PSAMP Protocol Specifications PSAMP IETF-59 March 2, 2004 Benoit Claise Juergen Quittek.
Net Flow Network Protocol Presented By : Arslan Qamar.
Abierman-netconf-mar07 1 NETCONF WG 68 th IETF Prague, CZ March 19, 2007.
RADEXT WG RADIUS Attribute Guidelines Greg Weber March 21 st, 2006 IETF-65, Dallas v1 draft-weber-radius-attr-guidelines-02.txt draft-wolff-radext-ext-attribute-00.txt.
IP Flow Information eXport (IPFIX) 57 th IETF - Vienna, 16 July 2003 " Web Site: " Mailing list info:
A Framework for Session Initiation Protocol User Agent Profile Delivery (draft-ietf-sipping-config-framework-11) SIPPING – IETF 68 Mar 19, 2007 Sumanth.
Microsoft Office 2013 Try It! Chapter 4 Storing Data in Access.
1 IPFIX WG 59th IETF Seoul March 3, 2004 Chairs: Nevil Brownlee, Dave Plonka Discussion:
July 2007 CAPWAP Protocol Specification Editors' Report July 2007
1 IPFIX Default Transport IPFIX IETF-58 November 10, 2003 Stewart Bryant Benoit Claise.
1 PSAMP Protocol Specifications PSAMP IETF-58 November 11, 2003 Benoit Claise Juergen Quittek.
PSAMP Information Model Status Information Model for Packet Sampling A Status Report Thomas Dietz Falko Dressler.
IPFIX MIB Status Managed Object for IP Flow Export A Status Report Thomas Dietz Atsushi Kobayashi
IPFIX Protocol Draft Benoit Claise, Cisco Systems Mark Fullmer, OARnet Reinaldo Penno, Nortel Networks Paul Calato, Riverstone Networks.
Draft-ietf-p2psip-base-08 Cullen Jennings Bruce Lowekamp Eric Rescorla Salman Baset Henning Schulzrinne March 25, 2010.
IPFIX Requirements: Document Changes and New Issues Raised Jürgen Quittek, NEC Benoit Claise, Cisco Tanja Zseby, Sebstian Zander, FhG FOKUS.
Globally Identifiable Number (GIN) Registration Adam Roach draft-martini-roach-gin-01 IETF 77 – Anaheim, CA, USA March 22, 2010.
1 PSAMP WGIETF, November 2003PSAMP WG PSAMP Framework Document draft-ietf-psamp-framework-04.txt Duffield, Greenberg, Grossglauser, Rexford: AT&T Chiou:
Draft-ietf-ccamp-lmp-02.txt Link Management Protocol (LMP) LMP draft updates…  draft-ietf-ccamp-lmp-07.txt  draft-ietf-ccamp-lmp-wdm-01.txt  draft-ietf-ccamp-lmp-test-sonet-sdh-00.txt.
IP Flow Information eXport (IPFIX)
Residence Time Measurement draft-mirsky-mpls-residence-time-02
IPFIX Aggregation draft-dressler-ipfix-aggregation-01.txt.
XCON WG IETF-64 Meeting XCON Framework Overview & Issues
Managed Objects for Packet Sampling
PANA Issues and Resolutions
An IPv6 Flow Label Specification Proposal
Required Data Files Review
IPFIX WG 66th IETF San Diego November 9, 2006
IETF#67 – 5-10 November 2006 FECFRAME requirements (draft-ietf-fecframe-req-01) Mark Watson.
Transport Layer.
Topic #1 & #5 “All that has to do with header formats”
NAT Behavioral Requirements for Unicast UDP
IPFIX Requirements: Document Changes from Version -07 to Version -09
Data File Import / Export
M3UA (MTP3-User Adaptation Layer)
Configuration Framework draft-ietf-sipping-config-framework-06
PSAMP MIB Status: Document Changes
OSPF Extensions for ASON Routing draft-ietf-ccamp-gmpls-ason-routing-ospf-03.txt IETF67 - Prague - Mar’07 Dimitri.
IPv4 Support for Proxy Mobile IPv6 Ryuji Wakikawa & Sri Gundavelli
Export BGP community information in IPFIX draft-ietf-opsawg-ipfix-bgp-community-02.txt Zhenqiang Li Rong Gu China Mobile Jie Dong Huawei Technologies.
UDP based Publication Channel for Streaming Telemetry
Falling Back! … and: a Functional Decomposition of Post-Sockets
Updates to Draft Specification for DTN TCPCLv4
TCP Friendly Rate Control (TFRC): Protocol Specification RFC3448bis
Export BGP community information in IPFIX draft-ietf-opsawg-ipfix-bgp-community-05.txt Zhenqiang Li Rong Gu China Mobile Jie Dong Huawei Technologies.
Export BGP community information in IPFIX draft-ietf-opsawg-ipfix-bgp-community-01.txt Zhenqiang Li Rong Gu China Mobile Jie Dong Huawei Technologies.
A Minimal Set of Transport Services for TAPS Systems draft-ietf-taps-minset-02 Michael Welzl, Stein Gjessing IETF
O&M Area Working Group WG
Working Group Draft for TCPCLv4
Presentation transcript:

IPFIX Protocol Specifications IPFIX IETF-62 March 12th, 2005 <draft-ietf-ipfix-protocol-09.txt> Benoit Claise <bclaise@cisco.com> Stewart Bryant <stbryant@cisco.com> Ganesh Sadasivan <gsadasiv@cisco.com> Simon Leinen <simon@switch.ch> Thomas Dietz <dietz@netlab.nec.de> Mark Fullmer <maf@eng.oar.net>

Closed Issues in version 07 SCTP section improved The sections "Template Management" and "The Collecting Process's Side" updated according to the default transport protocol treat UDP as the exception Inserted an Enterprise Specific Information Element example Editorial changes +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enterprise Number 1.1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -+-+-+-+-+-+-+-+-+-+-+-+ | Field Type 2 | Field Length 2 | +-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Closed Issues in version 08 TCP section inserted Sequence Number is now: The total number of IPFIX data records … (and not the number of IPFIX Messages anymore) Editorial changes +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enterprise Number 1.1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -+-+-+-+-+-+-+-+-+-+-+-+ | Field Type 2 | Field Length 2 | +-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Closed Issues in version 09 New sections for the protocol format: now contains generic format and separate examples Improved readability of the examples New section specifying the data types encoding Simplified specific Option Templates, removed ipfixOption Better clarification of the scope Consistence of Information Element versus field Editorial changes +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enterprise Number 1.1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -+-+-+-+-+-+-+-+-+-+-+-+ | Field Type 2 | Field Length 2 | +-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Changes in version 10 (results of this week meeting, not yet posted) Improved text regarding the protocol format (some confusion with the terminology) Remove the flow expiration section; only kept the one in [IPIFX-ARCH] Editorial Changes +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enterprise Number 1.1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -+-+-+-+-+-+-+-+-+-+-+-+ | Field Type 2 | Field Length 2 | +-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Open Issues, with consensus +------------------+---------------------------------------------+ | | Contents | | +--------------------+------------------------+ | Set | Template | Record | +------------------+--------------------+------------------------+ | Data Set | / | Data Record(s) | | Template Set | Template Record(s) | / | | Options Template | Options Template | / | | Set | Record(s) | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enterprise Number 1.1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -+-+-+-+-+-+-+-+-+-+-+-+ | Field Type 2 | Field Length 2 | +-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Data Record instead of Flow Data Record or Options Data Record

Open Issues Positive only offset for flowStartDeltaUsec, flowEndDeltaUsec (because unsinged32) => this implies the IPFIX Message “Export Time” must be a lower value Note: By default, “Export Time” is the time at which the IPFIX Message leave the exporter. For a Data Set with Flow Records requiring microsecond precision, the IPFIX Message Header "Export Time" field SHOULD be calculated … dateTimeMicroSeconds base type: "Its encoding is not defined yet.“ Information Elements for the specific option templates must be first defined in [IPFIX-INFO] Some emails on the mailing list Anything else to discuss here? +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enterprise Number 1.1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -+-+-+-+-+-+-+-+-+-+-+-+ | Field Type 2 | Field Length 2 | +-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

IPFIX Protocol Specifications IPFIX IETF-62 March 12th, 2005 <draft-ietf-ipfix-protocol-08.txt> Benoit Claise <bclaise@cisco.com> Stewart Bryant <stbryant@cisco.com> Ganesh Sadasivan <gsadasiv@cisco.com> Mark Fullmer <maf@eng.oar.net> Simon Leinen <simon@switch.ch> Thomas Dietz <dietz@netlab.nec.de>