Subject: [Rmt] 52nd IETF [SLC] rmt minutes

From: Roger Kermode <[email-masked]>
Date: Tue, 08 Jan 2002 16:24:16 +1100

Reliable Multicast Transport WG (rmt)
52nd IETF, Salt Lake City

Monday, December 10, at 0900-1130
Tuesday, December 11 at 1545-1645
================================

CHAIRS: Roger Kermode <[email-masked]>
        Lorenzon Vicisano <[email-masked]>

AGENDA:

Monday
======
1) Roger K./Lorenzo V.  WG status and agenda updates    10 mins

2) Mike Luby    Draft updates and call to move forward  20 mins
   draft-ietf-rmt-bb-fec-05.txt
   draft-ietf-rmt-info-fec-01.txt
   draft-ietf-rmt-bb-lct-03.txt
   draft-ietf-rmt-pi-alc-04.txt

3) Mike Luby    New draft ALC-related CC-PI             25 mins
   draft-ietf-rmt-bb-webrc-00.txt

4) Joerg Widmer New draft TFMCC CC-PI                   25 mins
   draft-ietf-rmt-bb-tfmcc-00.txt

Tuesday
=======
6) Lorenzo Vicisano (for Brian Adamson) Draft updates   15 mins
   draft-ietf-rmt-pi-norm-03.txt
   draft-ietf-rmt-bb-norm-03.txt

7) Chairs/AD    ALC security discussion                 15 mins

Monday
======
[Notes taken by Chuck Hardin <[email-masked]>]

Comments on IPR for FEC:
  Luigi Rizzo's codes should be available.
  There may be other open codecs available,
    at least one unencumbered codec should be
    made available for each type of FEC scheme
  Need to identify another codec in addition to
    the Digital Fountain codec for long block codes.

WEBRC comments:
  are you tied to PIM or is it just specified because of popularity?
    A: the latter
  do we have data for other protocols?
    A: no

  MRTT comments for WEBRC
   needn't be perfect now, can always be adjusted; also it's safe
   unused protocols are always safe
   safety is not security
   need more data on join leave latency times from vendors,
   but we need to think about this stuff now to ensure usability

TFMCC comments:
  what convergence times would you expect?
    A: on the order of 10-20 seconds;
  TCP will ramp up more quickly, TFMCC will slowly
    ramp up to match
  simulation results available in this year's sigcom paper
  what simulation tool to get to 10K receivers?
    A: ns
  simulation code is not available on ns website;
    it's available on Joerg Widmer's website

Tuesday
=======
[Notes taken by Bill Nickless <[email-masked]>]

Updates on the discussion of the NORM-BB and NORM-PI drafts.
   NRL implementation in open source by March 2002 IETF
     http://pf.itd.nrl.navy.mil  - "source forge like site"

ALC Security Updates
   Transport vulnerability to spoofed packets
   Congestion control vulnerability

What's happening with TRACK 
   Not much has happened since the last meeting
   working on congestion building block
   drafts coming out shortly

Discussing getting the draft authors together in January
   possibly in Berkeley
   ** Lorenzo to coordinate with Mark Handley **

PGM is an experimental RFC as of 3 days ago

Roger remarks to Protocol Instantiation Authors
   PI docs should contain sufficient detail for someone
   to implement a working protocol. 
   All references 

Allison (AD) remarks
   Creating cross working group design team, considering security
   mechanisms for multicast SSM.  PIM, MSEC, MAGMA.  Under 10
   people.  Could be anchored in this WG.
   - WG chairs from the above WGs will cut a first pass for
     people to look at.

   Secure Session Management: would the chairs like to add
   this to the charter?
   - short discussion about relationship to MAGMA

   Creating a small design team to work on this issue too.