home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
iesg
/
iesg.93-01-11
< prev
next >
Wrap
Text File
|
1993-08-31
|
6KB
|
212 lines
IETF STEERING GROUP (IESG)
REPORT FROM THE IETF MEETING
January 11th, 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.
iesg-secretary@cnri.reston.va.us.
ATTENDEES
---------
Borman, David / Cray Research
Chapin, Lyman / BBN
Crocker, Steve / TIS
Coya, Steve / CNRI
Gross, Philip / ANS
Hinden, Robert / SUN
Hobby, Russ / UC-DAVIS
Huizer, Erik / SURFnet
Knowles, Stev / FTP Software
Reynolds, Joyce / ISI
Stockman, Bernard / SUNET/NORDUnet
Vaudreuil, Greg / CNRI
Regrets
Almquist, Philip / Consultant
Crocker, Dave / TBO
Davin, Chuck / Bellcore
Piscitello, Dave/ Bellcore
AGENDA
------
1) Administrivia
o Role Call
o Bash the Agenda
o Approval of the Minutes
- December 21st
- January 4th
2) Protocol Actions
o PEM
o SMTP Extensions
o DS1 MIB
o DS3 MIB
3) Technical Management Issues
o IP Addressing Guidelines
o ROAD Communications
4) RFC Editor Actions
o RIP (Wide Area Routing with RIP)
o BGP Default Route
o SNMP over Various Protocols
5) Working Group Actions
o IP Security (ipsec)
o Skinny Stack
MINUTES
-------
1) Administrivia
o Bash the Agenda
Agenda was adjusted to accommodate the limited participation of Lyman
Chapin and Steve Crocker.
o Next Meeting Arrangements
The IESG will not meet January 18th, a U.S. federal holiday. The next
meeting will be January 25th.
o Approval of the Minutes
The IESG approved the minutes of December 21st. Approval of the
January 4th minutes was deferred.
The IESG minutes are made publicly available shortly after being
approved. The availability of these minutes is not announced to the
IETF list and there was agreement that periodic announcements should
be made on the IETF mailing list and the in the Internet Monthly
Report.
ACTION: Coya -- Announce the availability of the IESG minutes in the
IMR and periodically to the IETF mailing list.
2) Protocol Actions
o PEM
Steve Crocker provided the IESG shortly before the meeting with a
copy of the correspondence between the IAB and the principal patent
holders for the PEM security technology. Final approval of PEM was
deferred until the material could be studied.
ACTION: Vaudreuil -- Incorporate changes suggested into the protocol
action and send a ballot to the IESG.
There was discussion on the process by which future protocols using
patented technology can be handled more efficiently. The IETF needs
a clear statement of policy and a standard procedure for the next
issue to arise. IEEE and ANSI procedures were discussed as a
model. Among the items to be resolved are the establishment of a
repository for release letters, and a clear understanding of what
are "reasonable" terms for purposes of standardization.
o SMTP
The IESG deferred consideration of the SMTP Extension protocols.
o DS1 MIB and DS3 MIB
The IESG approved the revised DS1 and DS3 specifications for
re-publication as Proposed Standards. The previous versions, RFC
1233 and RFC 1332 were moved to Historic.
ACTION: Vaudreuil -- Announce the DS1 and DS3 Protocol Action to the
IETF-Announce list.
3) Technical Management.
o IESG Balloting.
During the IESG discussion on the SMTP Extensions, an inconsistency
was noted between the various ballots sent to the IESG. Discussion
resulted the following ballot choices.
"Yes" - The specification was explicitly reviewed and no objections
were found
"No Objection" - The specification was not reviewed explicitly but a
review of the protocol action raised no objections
"Discuss" - A review of the protocol action or the specification
raised an item of concern which needs to be addressed.
"Abstain" - A conflict of interest may exist and the IESG member
choose not to register a vote.
Eight "Yes" or "No Objection" and no "Discuss" votes will result in
passage by a protocol.
o IP Addressing
A teleconference was scheduled for Wednesday to discuss and reach
resolution on the status of the IP Addressing Guidelines document.
ACTION: Gross - Schedule a teleconference to reach closure on the
status of the IP addressing guidelines document.
o ROAD Communication
Stev Knowles sent out a note soliciting comments on whether the IESG
should make an explicit decision for a particular next IP protocol.
Emerging consensus seems to be that an early decision in March is
unwarranted. There is some feeling that all competitors should be
put in the pressure cooker until they reach a common proposal. There
was some discussion that a new packet format was not needed at all,
just a new routing architecture.
ACTION: Knowles -- When the discussion subsides, send a note to the
IETF list summarizing any consensus that emerges.
4) RFC Editor Actions
o Wide Area Routing with RIP
There was no discussion on this proposal. This was forwarded by the
RFC Editor to the IESG to be considered for Proposed Standard.
o BGP Default Route
The Internet Draft approved by the IESG and IAB was incomplete,
missing references and a security considerations section. This was
not discussed by the IESG.
o SNMP over [OSI, Appletalk, IPX]
These documents approved by the IESG contain sections which appear
to be obsolete given the work in the SNMP Security Working Group.
The RFC Editor wants to know if they should be updated prior to
publication. This was not discussed.
APPENDIX - Action Items taken
ACTION: Coya -- Announce the availability of the IESG minutes in the
IMR and periodically to the IETF mailing list.
ACTION: Vaudreuil -- Announce the DS1 and DS3 Protocol Action to the
IETF-Announce list.
ACTION: Gross - Schedule a teleconference to reach closure on the
status of the IP addressing guidelines document.
ACTION: Knowles -- When the discussion subsides, send a note to the
IETF list summarizing any consensus that emerges.