Re: [IPFIX] Updated agenda for San Francisco meeting

["Boschi, Elisa" <[e-mail]>]

Nevil, all,

we have a new revision of the anonymisation draft, which we would like to present and discuss at the meeting:
draft-boschi-ipfix-anon-03.txt
Unfortunately we missed the submission deadline, but the document can be accessed here:
http://people.ee.ethz.ch/~boschie/draft-boschi-ipfix-anon-03.txt

thanks,
Elisa

Nevil Brownlee wrote:
> Hi all:
> 
> If you have any further changes, please send them to me
> pronto :-)
> 
> Cheers, Nevil
> 
> 
> ======================================================
> Ip Flow Information Export WG (ipfix)
> IETF #74, San Francisco
> Monday, 23 Mar 09 at 1300-1500
> ======================================================
> 
> Chairs:
> Juergen Quittek <[e-mail]>
> Nevil Brownlee  <[e-mail]>
> 
>  >>> DRAFT <<<  AGENDA:
> 
> 1. Agenda review WG Status                              = 5 min
> 
> 2. Internet-Draft status                                = 5 min
>      [In RFC Editor queue:
>        - draft-ietf-ipfix-architecture-12.txt
>        - draft-ietf-ipfix-as-12.txt
>        - draft-ietf-ipfix-reducing-redundancy-04.txt
>        - draft-ietf-ipfix-testing-04.txt
>        - draft-ietf-psamp-framework-13.txt
>        - draft-ietf-psamp-sample-tech-10.txt
>        - draft-ietf-psamp-protocol-09.txt
>        - draft-ietf-psamp-info-11.txt]
> 
> 3. Information Element Registry status                 = 5 min
>       IANA's XML page for this are now at
>         http://www.iana.org/assignments/ipfix/ipfix.xhtml
>       We are now handling errata found in RFC 5102, IANA should
>       change the registry for such changes;  We need to establish
>       a procedure for handling changes in other IEs
> 
> 4. Drafts submitted to IESG                             = 15 min
>    a) IPFIX File Format (Brian Trammell)                    ( 3 min)
>       - draft-ietf-ipfix-file-03.txt  24 Oct 08
>    b) Exporting Type Information for IPFIX IEs (Elisa Boschi)
>       - draft-ietf-ipfix-exporting-type-02.txt  14 Jul 08   ( 3 min)
> 
>    c) IPFIX MIB (Thomas Dietz)
>       - draft-dietz-ipfix-mib-05.txt  3 Nov 08
>           MIB Doctors have requested a revised draft        ( 9 min)
> 
> 5. Current WG drafts                                    = 50 min
>    a) IPFIX Per-Stream SCTP reporting (Benoit CLaise)       ( 5 min)
>       - draft-ietf-ipfix-export-per-sctp-stream-02.txt
>           26 Jan 09
>    b) Configuration Data Model                              ( 5 min)
>       - draft-ietf-ipfix-configuration-model-01.txt
>            3 Nov 08
>    c) IPFIX Mediation: (Kobayashi Atsushi)                  (15 min)
>       - draft-ietf-ipfix-mediators-problem-statement-02.txt
>            4 Feb 09
>       - draft-ietf-ipfix-mediators-framework-02.txt         (25 min)
>           10 Feb 09
> 
> 6. Other drafts                                         = 30 min
>    a) Flow Selection (Lorenzo Peluso, Tanja Zseby)          (10 min)
>        - draft-peluso-flowselection-tech-02
> 
>    b) IP Flow Anonymization Support (Elisa Bschi, Brian Trammel)
>        - draft-boschi-ipfix-anon-02  12 Jan 09              (10 min)
> 
>    c) Handling Structured Data (Benoit Claise)
>        - draft-claise-structured-data-in-ipfix-00.txt       (10 min)
> 
> 7. Any Other Drafts ???                                 = 10 min
> 
> 
> Presentation slides will be available at
>  https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=74
>  (search for IPFIX in the Operations and Management Area)
> 
> Participation via jabber is offered at [e-mail]
> 

************************************************************************************************** 
E-mail Confidentiality Notice and Disclaimer. 

This e-mail and any files transmitted with it are confidential and are intended solely for the use 
of the individual or entity to which they are addressed. Access to this e-mail by anyone else is 
unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited. E-mail messages are not 
necessarily secure. Hitachi does not accept responsibility for any changes made to this message 
after it was sent. 
Hitachi checks outgoing e-mail messages for the presence of computer viruses. 
**************************************************************************************************