Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!A.ISI.EDU!CERF
From: CERF@A.ISI.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Announcing a little board-room shakeup
Message-ID: <[A.ISI.EDU]26-Jul-89.01:29:37.CERF>
Date: 26 Jul 89 05:29:00 GMT
References: <8907250403.AA04627@bear.NISC.SRI.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 61


1. IRTF will meet on a schedule to be determined by Dave Clark.
   He is just as interested as you are in reducing the number of meetings
   we all have to attend.

2. IRTF will have access to the same clearinghouse mechanisms that
   the rest of the IAB system has (RFCs, Internet-Drafts Directory,
   etc.)

3. Annual IAB meeting... In some sense, the Interop meetings
   seem to fill a part of that need. And the IETF meeting 
   minutes are reported quarterly. I'm not sure we need another
   meeting...

4. The IAB itself is responsible for technical policy, for
   setting the objectives for IRTF and IETF (which are reduced
   to practice by the IRSG and IESG), dealing with external
   liaison (e.g. with FRICC, CCIRN, RARE, NIST, ...), breaking
   logjams impeding progress on standards for the Internet, and
   so on. The members of IAB proper have other roles in the Internet
   community, as should be obvious from the list that Braden provided.

5. Security has become such a visible issue for the Internet
   (see GAO report and recent hearings on the Hill) that I wanted
   top-level attention to policy matters. There may, indeed, 
   continue to be an IRTF group focused on security/privacy
   chaired by Steve Kent - but this remains to be seen as Dave
   Clark works out the structure of IRTF.

6. IAB has liaison with FRICC in several ways. I am generally
   invited to FRICC meetings except when they are for gov't only;
   Phill Gross runs the special FRICC engineering planning group;
   FRICC is invited to IAB meetings ex officio. IAB has had
   NIST visitors and will be working out specific IETF and possibly
   IRTF working group/research group joint efforts with them.
   Network management and white pages registrations are examples
   of areas where we expect some specific work. It is not clear
   that we need a NIST representative on the IAB if we can work out
   specific working group interactions.

   Collaboration with ANSI and IEEE is under consideration but, again,
   I suspect that we may find this working better through specific
   IETF working groups or IRTF research groups because ANSI and IEEE
   are not easily representable by a single individual. Rather, they are
   represented by each working group on particular topics, which matches
   our IRTF and IETF structure.

7. IAB will resolve standards matters when they cannot be resolved
   within the IETF or IRTF.

8. IAB will represent the Internet community and its standards,
   when necessary, before the Defense Protocol Standards Steering
   Group, ANSI, NIST, CCIRN, FRICC, RARE, and so on.

9. IETF and IRTF structures are being worked out in detail and
   will be reported by Phill Gross and Dave Clark as soon as these
   details are settled.

Vint Cerf
Chairman
IAB