IETF STEERING GROUP (IESG)
REPORT FROM THE IETF MEETING
March 1st, 1993
Reported by: Greg Vaudreuil, IESG Secretary
This report contains IESG meeting notes, positions and action items.
These minutes were compiled by the IETF Secretariat which is supported
by the National Science Foundation under Grant No. NCR 8820945.
For more information please contact the IESG Secretary.
[email protected].
ATTENDEES
---------
Borman, David / Cray Research
Crocker, Steve / TIS
Coya, Steve / CNRI
Davin, Chuck / Bellcore
Gross, Philip / ANS
Hinden, Robert / SUN
Hobby, Russ / UC-DAVIS
Huizer, Erik / SURFnet
Knowles, Stev / FTP Software
Reynolds, Joyce / ISI
Piscitello, Dave/ Bellcore
Stockman, Bernard / SUNET/NORDUnet
Vaudreuil, Greg / CNRI
IAB liaison
Chapin, Lyman / BBN
Regrets
Almquist, Philip / Consultant
Crocker, Dave / SGI
Christian Huitema / INRIA
AGENDA
------
1) Administrivia
o Role Call
o Bash the Agenda
o Approval of the Minutes
o New PPP Working Group Chair
o IESG Liaison to IAB
2) Protocol Actions
o Tools RFC
o MIBs in Waiting
- PPP LCP MIB
- PPP IP NCP MIB
- PPP Bridge MIB
- PPP Security MIB
- Token Bus MIB
- Token Ring MIB
3) Management Issues
o Router Requirements
o The US Domain, Farnet, and NWnet
o SNMP Version2
4) Working Group Actions
o Secure FTP
5) Tasked Items
o NFS and RPC
o IP Address Guidelines A/S
o WAR with RIP
o RIP Applicability Statement
o IP Security Working Group
o Summarize the ROAD Discussions
o Dynamic Host Configuration Protocol
o IPLPDN
o Compressing TCP/IP Headers
o Extensions to Generic-Interface MIB
MINUTES
-------
1) Administrivia
o Minutes
Approval of the minutes of the February 22nd teleconference was
deferred.
o Next Meeting
The next meeting was scheduled for February 8th, 11:30 to 1:30 ET.
o New PPP Working Group Chairman
The IESG was notified that Fred Baker will be assuming the PPP
Working Group chair, replacing Brian Lloyd.
o IAB/IESG Liaison
The IAB has chosen Christian Huitema as a second liaison person to
the IESG. The IESG discussed possible liaisons with the IAB and
agreed to postpone a choice until after the new IESG members are
selected.
2) Protocol Actions
o NOOP Tools
The NOOP Working Group is currently editing this document for
re-submission as a Proposed Standard requirements document. No
further IESG action is needed at this time.
o Many MIBs
Vaudreuil investigated the status of the current Network Management
Directorate and found that most activity is conducted at quarterly
IETF meetings. Their does not appear to be an compelling reason to
advance the outstanding Network Management protocols without an Area
Director. No further action will be taken until the next IETF
meeting.
3) Management Issues
o SNMP Version2
There were no specific results to report. The action item to poll
the SNMP Version 2 participants has not been completed. The process
by which the IESG was to ask for comments is new and the rationale
is not well understood. Concerns centered on the role of the IESG
in explicitly polling for comments when an open process via the
Working Group nominally exists for expressing process objections.
Several private comments made to each of several IESG members were
made expressing concern about the working group process and result.
A review of the snmpv2 working group message archive, by Dave
Crocker, revealed some heated exchanges but no specific problems.
There was continuing agreement by most IESG members that the "where
there smoke there may be fire" principle required further
investigation. Erik Huizer as a neutral IESG member volunteered to
send the request for more information.
ACTION: Huizer -- Send a query to the SNMPv2 and SNMP Security Mailing
lists asking for specific comments on the process by which SNMP V2 was
proposed and reviewed. Report back by the March 8th teleconference.
o IESG Nomination Committee.
The Nomination Committee is expected to have a slate of Area
Directors ready to be approved by the IAB at the Columbus IETF
meeting. The IESG was delighted by the prospect for a smooth
transition and asked that the dates be changed slightly so the IAB
could review the nominees before the IETF meeting and thus
facilitate a smooth transition between the current and the
replacement Area Directors throughout the week.
ACTION: Huizer -- Relay the IESG request to have the slate of IESG
Nominees ready in time for IAB review before the IETF meeting.
ACTION: Chapin -- Schedule an IAB meeting to review the list of IESG
directors for the week before the IETF meeting in anticipation of
speedy nomination committee action.
o Router Requirements.
The Router Requirements documents are now over a year old and need
to be published. Repeated inquiries to Almquist have not resulted
in progress. The IESG agreed to offer help in editing the document
if needed.
ACTION: Knowles -- Offer Almquist help if needed to get the Router
Requirements documents submitted before the next IETF meeting.
o TCP Header Compression
TCP Header Compression has been on the IESG plate for over eight
months waiting for a revision from Van Jacobsen. The IESG agreed
that the changes are sufficiently small that they could be made to
the ASCII copy and published as a text-only Draft Standard should
Jacobsen be unable to edit the postscript before the next IETF
meeting.
ACTION: Borman -- Edit the ASCII Version of the Header Compression
document and offer to submit it as a Draft Standard if Jacobsen is
unable to update the Postscript.
o Working Smarter
The IESG workload has been rising and is expected to continue to do
do. Gross began a discussion of additional procedures and structures
the IESG could implement to "Work Smarter, not Harder". A focus of
the discussion was the creation of Area Directorates for each area.
There was some disagreement on whether a directorate should be a
formal body with named membership or a looser "kitchen cabinet" group
of trusted advisors to the Area Director. No resolution on the model
was reached.
The Secretariat produces several status tracking reports. As the
Working Group Goals and Milestone definitions have improved to enable
more useful reporting on the status of Area Progress. These reports,
currently available on the public ~/ftp/iesg directory will now be
mailed on a weekly basis.
Further discussion on this topic was scheduled for the face-to-face
get-to-know the new Area Directors meeting at the next IETF Plenary.
4) Working Group actions
o FTP Security
The question of whether the FTP Security Extensions Working Group
should be chartered in the Applications or the Security Area depends
both upon whether a straight forward application of CAT technology
will suffice and the scope of other non-security enhancements
needed.
ACTION: Hobby, SCrocker -- Discuss the possible approaches to FTP
Security and resolve the technical issues necessary to properly charter
the FTP Security Working Group.
5) Tasked Items
Not all listed items were reviewed.
o IP Security
This proposed working group still needs a revision to the charter.
It is expected before the next IESG meeting.
General question: Do it on a case-by-case basis depending on what is
most appropriate.
APPENDIX -- Summary of Action Items Assigned
ACTION: Huizer -- Send a query to the SNMPv2 and SNMP Security Mailing
lists asking for specific comments on the process by which SNMP V2 was
proposed and reviewed. Report back by the March 8th teleconference.
ACTION: Huizer -- Relay the IESG request to have the slate of IESG
Nominees ready in time for IAB review before the IETF meeting.
ACTION: Chapin -- Schedule an IAB meeting to review the list of IESG
directors for the week before the IETF meeting in anticipation of
speedy nomination committee action.
ACTION: Knowles -- Offer Almquist help if needed to get the Router
Requirements documents submitted before the next IETF meeting.
ACTION: Borman -- Edit the ASCII Version of the Header Compression
document and offer to submit it as a Draft Standard if Jacobsen is
unable to update the Postscript.
ACTION: Hobby, SCrocker -- Discuss the possible approaches to FTP
Security and resolve the technical issues necessary to properly charter
the FTP Security Working Group.
