IP Flow Information Export WG (ipfix)

Monday, November 10 at 0900-1130
================================

CHAIRS: Nevil Brownlee <[email protected]>
       Dave Plonka


minutes

5  1) Agenda Review

   2) Requirements draft, Juergen Quittek
      (status as at 28 Oct 03: waiting for IESG feedback on anonymisation)
10       draft-ietf-ipfix-reqs-11.txt

   3) New drafts - brief overview presentation for each,
      discussion of as-yet-unwritten sections and unresolved issues.
      The drafts are
10      * draft-ietf-ipfix-arch-02.txt
15      * draft-ietf-ipfix-info-01.txt
15      * draft-ietf-ipfix-protocol-01.txt
5      * draft-ietf-ipfix-as-01.txt

   4) Short Presentations
       * IPFIX Vendor Specific Information Elements (dor IPFIX and PSAMP)
15          draft-bryant-ipfix-vendor-ie-00.txt
              [Stewart Bryant]
       * Flow selection support in IPFIX
15          draft-molina-flow-selection-00.txt
              [Maurizio Molina]

   5) Discussion: IPFIX transport and Congestion Control
35       The IPFIX charter clearly says "must run over a congestion-aware
        transport protocol."  So far we have identified SCTP and TCP
        as suitable transport protocols, with both being discussed in
        the IPFIX protocol draft.  We need to select a default transport,
        i.e. one wich will be 'mandatory to implement.'

        This will be an open-mike . search for consensus discussion,
        be prepared to make compelling *technical* arguments.

        Also, maybe we should recognise that there will be situations
        which any chosen default may not be the 'most suitable,' i.e.
        vendors can implement other protocols besides the default.

        Note that there's no question of IPFIX being limited to any
        one transport protocol.

5  6) Review of WG Milestones

5  7) Anything else

If you have other items you'd like to see discussed, please advise
the WG chairs, by email to [email protected]

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.