IETF STEERING GROUP (IESG)
REPORT FROM THE IETF MEETING
February 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
---------
Almquist, Philip / Consultant
Borman, David / Cray Research
Chapin, Lyman / BBN
Crocker, Dave / TBO
Crocker, Steve / TIS
Coya, Steve / CNRI
Davin, Chuck / Bellcore
Gross, Philip / ANS
Hinden, Robert / SUN
Hobby, Russ / UC-DAVIS
Knowles, Stev / FTP Software
Reynolds, Joyce / ISI
Stockman, Bernard / SUNET/NORDUnet
Piscitello, Dave/ Bellcore
Vaudreuil, Greg / CNRI
Regrets
Huizer, Erik / SURFnet
AGENDA
------
1) Administrivia
o Approval of the Minutes
January 25th
2) Protocol Actions
o SMTP Extensions
o Directed ARP
o Token Ring MIB
o NFS
o RPC
o IP Address Guidelines
o Lightweight Directory Access Protocol
3) Technical Management Issues
o SNMP Security o Policy Statements
o RIP Applicability Statement
o Wide Area Routing with RIP
o BOF Policy
4) RFC Editor Actions
o Secure FTP
5) Working Group Actions
o IP Security (ipsec)
o Skinny Stack (skinstak)
o Remote Conferencing (remconf)
o Integrated Directory Services (ids)
o Directory Information Services Infrastructure (disi)
MINUTES
---------
1) Administrivia
o Approval of the Minutes
Approval of the minutes of the 25th was deferred until the next meeting.
o Next Meeting
Monday February 8th, 11:30 ET.
2) Protocol Actions
o SMTP Extensions
Revised documents were submitted to the IESG. The ballot was
completed and the SMTP Extensions documents were passed as a
Proposed Standard.
ACTION: Vaudreuil -- Send the Protocol Action for the SMTP Extensions
documents.
o Directed Arp
A specification for Directed ARP was submitted to the IESG by the
IPLPDN Working Group for approval as an Experimental Protocol. As an
Experimental Protocol, the IESG is to review the specification for
basic IETF quality control. The proposal is a significant departure
from the traditional IP architecture and the IESG was not confident
this would work or comfortable with this proposal as a Working
Group product. There does not appear to be a strong constituency
nor much desire to utilize this approach within the Working Group.
ACTION: Piscitello -- Notify the IPLPDN Working Group chair of the IESG
concerns about the Directed ARP protocol and ascertain the extent to
which the proposal has the backing of the Working Group.
o Token Ring MIB
o Token Bus MIB
A last call for the Token Ring and Token Bus MIBS was sent to the
IETF mailing list. After almost two years, there does not appear to
be sufficient implementation or operational experience to warrant
elevation Draft Standard status. The IESG agreed to pursue moving
these MIBs to Historic Status.
ACTION: Vaudreuil -- Send a second last call for the Token Ring and
Token BUS MIBS for Historic Status.
o NFS
o RPC
Progress continues to be made in securing the necessary releases to
charter an IETF Working Group to standardize NFS. The IESG
discussed the circumstances by which a Working Group could be formed
to work on evolving a proprietary protocol, and agreed that a letter
of release to the ISOC should be a prerequisite to the formation of
a Working Group.
POSITION: Working groups can be formed to evolve and standardize
formerly proprietary protocols only after a letter of release giving
the ISOC the rights to standardize further evolutions of the protocol.
o IP Addressing Guidelines
The IP addressing guidelines will be considered as part of a set of
CIDR related documents. Until these documents are submitted to the
IESG, the IP addressing document will remain on the IESG Agenda.
o Lightweight Directory Protocol/ String representation of Attribute Syntaxes
These two protocols were presented as a candidate for Proposed
Standard. It is not clear whether these should be one standard or
two. Further consideration was deferred until the more Area
Director familiar with these protocols returns from vacation.
o PEM
A discussion has begun on the IETF mailing list on the initial lack
of PEM and MIME integration. The IESG briefly discussed the
comments and concluded that the issues had been addressed and that
work to integrate PEM and MIME is progressing in parallel.
3) Technical Management Issues
o Special documents (AS, Policy Documents)
The IAB has suggested to the IESG that because of the significant
impact among external organizations, it may be helpful have
Applicability Statements and policy statements reviewed by the IAB.
The IESG agreed that it would be entirely reasonable to submit such
documents for review provided that the review does not require an
additional level of formal approval in addition to the normal
standards process including the last call.
POSITION: Review of Applicability Statements will be conducted with the
IAB in such a manner that input and guidance can be provided without
adding an additional level of formal approval.
o SNMP Security
The IESG did not discuss the continuing problems in the SNMP
Security Working Group. Efforts at mediation through Steve Crocker
are continuing. It was noted and acknowledged by the Security Area
Director that the SNMP Security Working Group is not yet scheduled
for the Columbus IETF Meeting.
o Policy Statements.
Several Proposals for a new series of documents for statements of
policy have been proposed to address the need to give weight to
statements which are not protocols. While an additional document
series may be useful, the IESG concluded that the range of possible
documents were likely to make any such series less than adequate.
The current mechanism for standards track Applicability Statements
and Informational documents was considered adequate as a rough
general mechanism for the needs of IESG expression.
POSITION: The current system of standards track Applicability
Statements and Informational documents is adequate for publication of
Statements of Policy.
o RIP Applicability Statement
No progress to report.
o Wide Area Routing with RIP
No progress to report.
o BOF Policy
There does not exist a uniform policy for the approval of BOF
sessions at IETF meetings. The variation of practices among the
Area Directors is causing confusion. The discussion reached
consensus on several key points. BOFs should meet only once, with a
second meeting possible to write an IETF Working Group charter.
Non-IETF groups could meet as IETF BOFs provided they meet normal
requirements for openness, minutes preparation and do not compete
for limited space.
ACTION Coya -- Summarize the IESG discussions on BOF policy.
o US Domain
A heads up was given to the IESG on possible issues in the use of
the US domain.
ACTION: IESG - Review RFC 1386 for possible issues.
4) RFC Editor Actions
o Secure FTP
A request was made to the RFC Editor for the source to the FTP RFC.
This request was made to allow easy updating of the FTP protocol
document to add security. A BOF was held during the San Diego IETF
meeting and resulted in a list of potential changes to FTP.
ACTION: Russ Hobby -- Investigate the viability of a Working Group to
revise the FTP protocol to include security as well as other additional
features.
ACTION: Vaudreuil -- Report the IESG intention of forming an FTP
Working Group to the RFC Editor.
5) Working Group Actions.
o IP Security Protocol
Revised text for the charter is still expected.
o Minimal OSI Upper Layers (thinosi)
The IESG accepted the charter for the thinosi Working Group.
ACTION: Vaudreuil -- Announce the Minimal OSI Upper Layers Working
Group to the IETF-Announce mailing list.
o Directory Information Services Infrastructure (disi)
The disi Working Group is to be replaced by the Integrated Directory
Services Working Group and was concluded by the User Services Area
Director.
ACTION: Vaudreuil -- Announce the conclusion of the DISI Working Group
to the IETF-Announce mailing list.
o Integrated Directory Services (ids)
Consideration of the IDS Working Group was deferred.
o Remote Conferencing
Work on chartering the Remote Conferencing Working Groups has
stalled. The IESG agreed to discuss this at the next
teleconference.
APPENDIX -- Summary of Action Items
ACTION: Vaudreuil -- Send the Protocol Action for the SMTP Extensions
documents.
ACTION: Piscitello -- Notify the IPLPDN Working Group chair of the IESG
concerns about the Directed ARP protocol and ascertain the extent to
which the proposal has the backing of the Working Group.
ACTION: Vaudreuil -- Send a second last call for the Token Ring and
Token BUS MIBS for Historic Status.
ACTION: IESG - Review RFC 1386 for possible issues.
ACTION Coya -- Summarize the IESG discussions on BOF policy.
ACTION: Russ Hobby -- Investigate the viability of a Working Group to
revise the FTP protocol to include security as well as other additional
features.
ACTION: Vaudreuil -- Report the IESG intention of forming an FTP
Working Group to the RFC Editor.
ACTION: Russ Hobby -- Investigate the viability of a Working Group to
revise the FTP protocol to include security as well as other additional
features.
ACTION: Vaudreuil -- Report the IESG intention of forming an FTP
Working Group to the RFC Editor.
