Skip to main content

Minutes interim-1994-iesg-18 1994-10-06 15:30
minutes-interim-1994-iesg-18-199410061530-00

Meeting Minutes Internet Engineering Steering Group (iesg) IETF
Date and time 1994-10-06 15:30
Title Minutes interim-1994-iesg-18 1994-10-06 15:30
State (None)
Other versions plain text
Last updated 2024-02-23

minutes-interim-1994-iesg-18-199410061530-00
											
Minutes of the IESG Teleconferences

    INTERNET ENGINEERING STEERING GROUP (IESG)
    6 October 1994

    Reported by: John Stewart, 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 at
    <iesg-secretary@cnri.reston.va.us>.

    ATTENDEES
    ---------
    Coya, Steve / CNRI
    Halpern, Joel / Newbridge Networks
    Huizer, Erik / SURFnet
    Klensin, John / MCI
    O'Dell, Mike / UUNET
    Reynolds, Joyce / ISI
    Rose, Marshall / DBC
    Schiller, Jeff / MIT
    Stewart, John / CNRI
    Topolcic, Claudio / BBN

    Regrets
    -------
    Bradner, Scott / Harvard
    Huitema, Christian / INRIA (IAB Liaison)
    Knowles, Stev / FTP Software
    Mankin, Allison / NRL
    Mockapetris, Paul / ISI
    Rekhter, Yakov / IBM (IAB Liaison)

    1. The minutes of the 22 September IESG teleconference were
    approved.

    2. Protocol Actions

    o The IESG approved "AppleTalk Management Information Base II"
    <draft-ietf-appleip-mib2-02.txt> for the status of Proposed
    Standard.

    o The IESG approved "IEEE 802.5 MIB"
    <draft-ietf-ifmib-tokenringmib-00.txt> for the status of
    Draft Standard.

    3. Working Group Actions

    o The IESG approved the creation of the Authenticated Firewall
    Traversal Working Group (AFT) in the Security Area.

    o The IESG approved the creation of the TFTP Extensions Working
    Group (TFTPEXTS) in the Applications Area.

    o The IESG approved the creation of the SNMPv2 Working Group
    (SNMPV2) in the Network Management Area.

    o The IESG approved the creation of the Responsible Use of the
    Network Working Group (RUN) in the User Services Area.

    4. Working Group Informational Documents

    o The IESG agreed to recommend to the RFC Editor that "Introducing
    Project Long Bud: Internet Pilot Project for the Deployment of
    X.500 Directory Information in Support of X.400 Routing"
    <draft-ietf-mhsds-long-bud-intro-02.txt> be published as an
    Informational RFC.

    5. Management Issues

    o Marshall Rose proposed to move the Router Requirements Working
    Group out of the Internet Area and into the Network Management
    Area in the interest of moving forward on it. While the IESG
    felt that RREQ was important, and might benefit from such a
    move, it chose not to move the working group when the currently-
    responsible area director was not in the meeting.

    Action(Stewart): Put Host Requirements on the agenda for the next
    IESG teleconference.

    o It was reported that there would be no sponsor for the IETF
    track at Networld+INTEROP'95/Vegas.

    o The IESG agreed on the following schedule for meetings/meals at
    the San Jose IETF meeting:
    (1) dinner on Sunday evening, with each IESG member paying
    for his/her own meal, and
    (2) catered breakfasts, including both hot and cold food,
    Tuesday-Friday (Monday is the working group chair get-
    together), paid for by an IESG member (i.e., not financed
    by Secretariat or attendees)

    o It was reported that there will be a European IPng walk-through
    done from INTEROP/Paris, though there are still some details to
    be worked out between Allison, Erik and Scott.

    o It was reported that Paul Mockapetris and Bob Hinden are now
    working directly with each other over Sun's offer to give RPC
    and XDR to the IETF.

    o The IESG agreed that it is reasonable to expect IETF working
    group mailing lists to behave certains ways -- there have been
    problems with, for example, Majordomo-administered lists. The
    IESG further agreed that it would support area directors asking
    the person responsible for the list to change it or have the
    list moved to another site. Text discussing the expected
    behavior of lists will be added to the next revision of Huizer/
    Crocker's "IETF Working Group Guidelines" RFC.

    ACTION(Halpern): Work with Erik Huizer to get text about mailing
    list behavior into the update to "IETF Working Group Guidelines."

    o Erik Huizer reported that he was stepping down as a RARE
    technical committee member.

    7. Waiting for AD Action

    ACTION(Mankin): Send the write-up of the "partial ordering in TCP"
    RFC-to-be to RFC-Editor@ISI.Edu.