1 IPFIX Default Transport IPFIX IETF-58 November 10, 2003 Stewart Bryant Benoit Claise.

Slides:

Advertisements

Similar presentations

Tunnel congestion Feedback (draft-wei-tunnel-congestion-feedback-01) Xinpeng Wei Lei Zhu Lingli Deng Huawei Huawei China Mobile IETF 89 London, UK.

Advertisements

1 Specifying New Congestion Control Algorithms Sally Floyd and Mark Allman draft-floyd-cc-alt-00.txt November 2006 TSVWG Slides:

TCP/IP MODEL Maninder Kaur

1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.

Umut Girit  One of the core members of the Internet Protocol Suite, the set of network protocols used for the Internet. With UDP, computer.

SCTP Tutorial Randall Stewart

TSVWG #1 IETF-92 (Dallas) 24 th March 2015 Gorry Fairhurst David Black WG chairs.

Telematics group University of Göttingen, Germany Overhead and Performance Study of the General Internet Signaling Transport (GIST) Protocol Xiaoming.

EE228A Project, Fall 2000 Yunfei Deng, Kenneth Cheung, Daniil Khidekel Professor Jean Walrand 12/5/2000 Modular TCP.

Introduction to Transport Layer. Transport Layer: Motivation A B R1 R2 r Recall that NL is responsible for forwarding a packet from one HOST to another.

SIP Security Michael Thomas Status First Cut of Requirements Draft –draft-thomas-sip-sec-reqt-00.txt –Will be basis going forward –Design.

Department of Electronic Engineering City University of Hong Kong EE3900 Computer Networks Transport Protocols Slide 1 Transport Protocols.

DCP: The Datagram Control Protocol Eiman Zolfaghari E190 – Technical Communications Professor Hatton April 2002.

1 Summer Report Reporter : Yi-Cheng Lin Data: 2008/09/02.

Draft-novak-bmwg-ipflow-meth-05.txt IP Flow Information Accounting and Export Benchmarking Methodology

1 PSAMP Protocol Specifications IPFIX IETF-64 November 10th, 2005 Benoit Claise Juergen Quittek Andrew Johnson.

Draft-loughney-what-standards-01.txt IETF 59 NEWTRK WG Presented by Spencer Dawkins.

Fraunhofer FOKUSCompetence Center NET T. Zseby, CC NET1 IPFIX – IP Flow Information Export Overview Tanja Zseby Fraunhofer FOKUS, Network Research.

Adaptive Failover Mechanism Motivation End-to-end connectivity can suffer during net failures Internet path outage detection and recovery is slow (shown.

1 IPFIX Protocol Specifications IPFIX IETF-59 March 3, 2004 Benoit Claise Mark Fullmer Reinaldo Penno Paul Calato Stewart Bryant Ganesh Sadasivan.

1 Transport Protocols Relates to Lab 5. An overview of the transport protocols of the TCP/IP protocol suite. Also, a short discussion of UDP.

RPR-SCTP Will Jenkins and Kennabec Walp Adv. Comp. Net. SystemsElectrical & Computer Engineering Mississippi State University Advanced Computer Network.

MPTCP – MULTIPATH TCP Interim meeting #3 20 th October 2011 audio Yoshifumi Nishida Philip Eardley.

Byte and Packet Congestion Notification draft-briscoe-tsvwg-byte-pkt-mark-00.txt draft-briscoe-tsvwg-byte-pkt-mark-00.txt Bob Briscoe, BT & UCL IETF-69.

(we need your advice!) Jon Peterson MIT– December 2010 IETF & Privacy.

TSVWG IETF-76 (Hiroshima) James Polk Gorry Fairhurst With an assist for this meeting from **Magnus Westerlund**

DCCP: Issues From the Mailing List Sally Floyd, Eddie Kohler, Mark Handley, et al. DCCP WG March 4, 2004.

CSC 600 Internetworking with TCP/IP Unit 5: IP, IP Routing, and ICMP (ch. 7, ch. 8, ch. 9, ch. 10) Dr. Cheer-Sun Yang Spring 2001.

Standards Activities on Traffic Measurement. 2 Outline Applications requiring traffic measurement Packet capturing and flow measurement Existing protocols.

Network and the internet Part eight Introduction to computer, 2nd semester, 2009/2010 Mr.Nael Aburas Faculty of Information.

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.

SCTP: A new networking protocol for super-computing Mohammed Atiquzzaman Shaojian Fu Department of Computer Science University of Oklahoma.

Update on the IETF Diffserv Working Group NANOG 13 Detroit, MI June 8, 1998 Kathleen M. Nichols

IP Flow Information eXport (IPFIX) 57 th IETF - Vienna, 16 July 2003 " Web Site: " Mailing list info:

Site Multihoming for IPv6 Brian Carpenter IBM TERENA Networking Conference, Poznan, 2005.

1 Transport Layer: Basics Outline Intro to transport UDP Congestion control basics.

4343 X2 – The Transport Layer Tanenbaum Ch.6.

1 PSAMP Protocol Specifications PSAMP IETF-58 November 11, 2003 Benoit Claise Juergen Quittek.

Uni Innsbruck Informatik th IETF, PMTUD WG: Path MTU Discovery Using Options draft-welzl-pmtud-options-01.txt Michael Welzl

IPFIX MIB Status Managed Object for IP Flow Export A Status Report Thomas Dietz Atsushi Kobayashi

December 5, 2007IETF 70 L3VPN WG1 MVPN Profiles Why do we need “profiles”? –By design, architecture provides many choices: PE-PE C-multicast routing info.

TSVWG IETF-89 (London) 5 th & 7 th March 2014 Gorry Fairhurst David Black James Polk WG chairs 1.

Lect1..ppt - 01/06/05 CDA 6505 Network Architecture and Client/Server Computing Lecture 3 TCP and IP by Zornitza Genova Prodanoff.

Chapter 3 TCP and IP 1 Chapter 3 TCP and IP. Chapter 3 TCP and IP 2 Introduction Transmission Control Protocol (TCP) User Datagram Protocol (UDP) Internet.

IPFIX Protocol Draft Benoit Claise, Cisco Systems Mark Fullmer, OARnet Reinaldo Penno, Nortel Networks Paul Calato, Riverstone Networks.

IPFIX Requirements: Document Changes and New Issues Raised Jürgen Quittek, NEC Benoit Claise, Cisco Tanja Zseby, Sebstian Zander, FhG FOKUS.

1 PSAMP WGIETF, November 2003PSAMP WG PSAMP Framework Document draft-ietf-psamp-framework-04.txt Duffield, Greenberg, Grossglauser, Rexford: AT&T Chiou:

David B. Johnson Rice University Department of Computer Science DSR Draft Status Monarch Project 57th IETF.

IP Security (IPSec) Matt Hermanson. What is IPSec? It is an extension to the Internet Protocol (IP) suite that creates an encrypted and secure conversation.

U Innsbruck Informatik - 1 Specification of a Network Adaptation Layer for the Grid GGF7 presentation Michael Welzl University.

Minion: An All-Terrain Packet Packhorse to Jump-Start Stalled Internet Transports Jana Iyengar*, Bryan Ford+ Dishant Ailawadi+, Syed Obaid Amin*,

IP Flow Information eXport (IPFIX)

Chapter 3 TCP and IP Chapter 3 TCP and IP.

IPFIX Protocol Specifications IPFIX IETF-62 March 12th, Benoit Claise Stewart Bryant

AMS Prototyping Activities

IETF#67 – 5-10 November 2006 FECFRAME requirements (draft-ietf-fecframe-req-01) Mark Watson.

15th November 2016 Gorry Fairhurst (via webrtc) David Black WG chairs

IPFIX Requirements: Document Changes from Version -07 to Version -09

Transport Protocols Relates to Lab 5. An overview of the transport protocols of the TCP/IP protocol suite. Also, a short discussion of UDP.

Stream Control Transmission Protocol (SCTP)

ECN Experimentation draft-black-ecn-experimentation

SCTP-based Middleware for MPI

CPEG514 Advanced Computer Networkst

Binary Floor Control Protocol BIS (BFCPBIS)

Course: CISC 856: TCP/IP and Upper Layer Protocols

16th November 2016 Gorry Fairhurst (via webrtc) David Black WG chairs

William Lupton | | 04-Nov-2018

James Polk Gorry Fairhurst

How Applications (Will Hopefully Soon) Use the Internet

Presentation transcript:

1 IPFIX Default Transport IPFIX IETF-58 November 10, 2003 Stewart Bryant Benoit Claise

222 IPFIX Transport IETF-58 The Issue IPFIX needs to specify a default, TCP friendly transport protocol. TCP friendly IETF transports defined, or in late stages of specification are: TCP, SCTP, PR-SCTP and DCCP. Some members of the WG propose that we standardise on TCP because it is ubiquitous. Other members of the WG propose that we standardise on PR-SCTP because its greater range of functionality better addresses the spectrum of IPFIX needs.

333 IPFIX Transport IETF-58 Why SCTP + PR-SCTP Architecturally it’s the right protocol for the job.

444 IPFIX Transport IETF-58 Best Fit to Architecture. SCTP with the PR-SCTP extensions Delivers reliable information just as TCP does. During uncongested periods, all the records marked for deletion under congestion will be reliably delivered. During congested periods, the sender will begin to drop packets to protect the network. PR-SCTP therefore offers all the advantages of TCP together with much of the flexibility of UDP, and is at all times TCP-friendly.

555 IPFIX Transport IETF-58 PR-SCTP Flexibility PR-SCTP allows the IPFIX application the flexibility to use reliable, partially reliable and unreliable, over one association with multiple streams. For example some Options Template reporting and some metering info might use the reliable stream while the Data Records would use the partially reliable stream.

666 IPFIX Transport IETF-58 Availability promotes use Choosing PR-SCTP as the default protocol means that PR-SCTP will be available to all exporters and collectors. quicker failover multihoming These would otherwise have to be constructed at applications level.

777 IPFIX Transport IETF-58 PR-SCTP availability "PR-SCTP is not deployed widely enough to be considered a default for any IETF technology." There are about 20 implementations for SCTP. PR-SCTP is an extension of SCTP which is available. PR-SCTP may not yet be there in all of the implementations, but that is not a problem either since if you don't have PR-SCTP then you end up with basic SCTP with full reliability, which is no different than TCP.

888 IPFIX Transport IETF-58 We need a Transport with an RFC "The default transport for a standards track protocol should at least be an RFC. " RFC PR-SCTP finished TSVWG last call quite some time ago, and will go to IESG last call as soon as the AD review phase is complete. This will happen shortly. PR-SCTP will be an RFC long before IPFIX.

999 IPFIX Transport IETF-58 Weaning the Internet off UDP Ultimately the IPFIX RFC is only a guide. The customer will specify the system they need for their business, and vendors will build them. UDP is available today for export and demand for this is likely to continue. UDP is a very low overhead protocol and is available on ALL platforms under consideration. The IETF needs to migrate users away from UDP and SCTP better provides better prospect for this than TCP.

10 IPFIX Transport IETF-58 Availability Assertion: "SCTP is not widely implemented" SCTP is available on: HP-UX Solaris Linux BSD Windows

11 IPFIX Transport IETF-58 Why not TCP? TCP has a single mode - reliable congestion aware. Partial reliability has to be synthesised in the application. By the time you have the code to do this synthesis, you have implemented an inferior version of SCTP in the application.