Skip to main content

Minutes interim-1993-iesg-27 1993-12-30 16:30
minutes-interim-1993-iesg-27-199312301630-00

Meeting Minutes Internet Engineering Steering Group (iesg) IETF
Date and time 1993-12-30 16:30
Title Minutes interim-1993-iesg-27 1993-12-30 16:30
State (None)
Other versions plain text
Last updated 2024-02-23

minutes-interim-1993-iesg-27-199312301630-00
											
Minutes of the IESG Teleconferences

    Internet Engineering Steering Group (IESG)

    December 30, 1993

    Reported by: Steve Coya, Acting 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
    ---------

    Bradner, Scott / Harvard
    Coya, Steve / CNRI
    Crocker, Dave / SGI
    Crocker, Steve / TIS
    Gross, Phillip / ANS
    Huizer, Erik / SURFnet
    Klensin, John / UNU
    Knowles, Stev / FTP Software
    Reynolds, Joyce / ISI
    Piscitello, Dave / Core Competence
    Rekhter, Yakov / IBM (IAB Liaison)
    Rose, Marshall / DBC

    Regrets

    Chapin, Lyman / BBN
    Hinden, Robert / SUN
    Huitema, Christian / INRIA (IAB Liaison)
    Mankin, Allison / NRL

    1. The minutes of the December 16 meeting were approved. Coya to
    place into public archives.

    2. The IESG approved the publication of "Classical IP and ARP over
    ATM" as a Proposed Standard. It was asserted that while this has
    been approved for the standards track, this document is technically
    deficient as it may not scale well in the future, and will not move
    to DRAFT status without changes. Coya to send announcement to the
    IETF List and the RFC-Editor.

    3. The IESG approved the publication of "PPP LCP Extensions" as a
    Proposed Standard. Coya to send announcement to the IETF List and
    the RFC-Editor.

    4. The IESG approved the publication of "Evolution of the Interfaces
    Group of MIB-II" as a proposed standard. The IESG also decided to
    reclassify RFC 1229 as Historic. Coya to send announcement to the
    IETF List and the RFC-Editor.

    5. The IESG approved the elevation of RFC 1356 "Multiprotocol
    Interconnect on X.25 and ISDN in the Packet Mode" to DRAFT
    standard. Coya to send announcement to the IETF List and the
    RFC-Editor.

    6. The IESG approved the creation of the ALE Working Group in the IPNG
    Area. Coya to send announcement to the IETF list.

    Note: Announcement can not be sent until the administrative
    information (list name, archive location, etc.) is provided.

    7. Stev Knowles was selected as the IESG Liaison to the IAB/IESG
    Nominating Committee. Coya to convey this information to the Chair
    of the Nominating Commitee.

    8. The IESG discussed the SNPP Informational RFC-to-be and the text
    that was cirulated by e-mail was tolerable and will be forwarded to
    the RFC Editor.

    9. The IESG then reviewed e-mail messages pertaining to the text that
    might be added to RFCs conveying the opinion of the IESG. The
    revised text sent by Jon Postel was deemed acceptable, with the
    notation that all WG references be explicit. There was another set
    of text that explained the purpose and need for including such
    statemets which was also approved by the IESG. Phill Gross to
    incorporate this explanatory text into the revision of 1310bis.

    10. There was some discussion on what steps should be taken when RFCs
    are not accurate, up-to-date, or reflect current practices, but the
    protocols themselves are widely used. There was no consensus
    reached during the teleconference, but the topic can (and probably
    will) re-appear on the IESG Mailing list.

    11. The IESG members individually reviewed the status and plans for
    some of their Working Groups.

    12. It was suggested that the Host Requirements Document might be out
    of date as it does not include references to CIDR.

    13. The message suggesting a set of Default IETF Meeting sites was
    discussed. Though no consensus was reached wrt the suggestions for
    implementing, the main point of agreement was that IETF meetings
    need to be scheduled further out, at least 2 years.