Skip to main content

Minutes interim-1996-iesg-04 1996-03-28 16:30
minutes-interim-1996-iesg-04-199603281630-00

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

minutes-interim-1996-iesg-04-199603281630-00
											
Minutes of the IESG Teleconferences

    INTERNET ENGINEERING STEERING GROUP (IESG)
    March 28, 1996

    Reported by: Steve Coya, IETF Executive Director

    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-9528103

    For more information please contact the IESG Secretary at
    <iesg-secretary@ietf.cnri.reston.va.us>.

    ATTENDEES
    ---------

    Alvestrand, Harald / Uninett
    Baker, Fred / cisco
    Bradner, Scott / Harvard
    Burgan, Jeff / Baynetworks
    Carpenter, Brian / CERN (IAB Liaison)
    Coya, Steve / CNRI
    Elz, Robert / U of Melbourne (IAB Liaison)
    Halpern, Joel / Newbridge Networks
    Kastenholz, Frank / FTP Software
    Kostick, Deirdre / AT&T Bell Labs
    Mankin, Allison / Information Sciences Institute
    Moore, Keith / U of Tennessee
    O'Dell, Mike / UUNET
    Reynolds, Joyce / ISI
    Schiller, Jeff / MIT

    Minutes
    -------
    1. The IESG approved the minutes of the February 22, 1996. Coya to
    place in shadow directories.

    2. The IESG approved publication of PPP in Frame Relay
    <draft-ietf-pppext-frame-relay-03.txt> as a Proposed Standard. Jeff
    is to provide a list of specific RFC references that need to be
    updated. When received, Steve will send the Protocol Action
    announcement.

    3. The IESG approved publication of The PPP Encryption Control
    Protocol (ECP) <draft-ietf-pppext-encryption-04.txt> as a Proposed
    Standard. Keith is to provide replacement text for the Working Group
    summary prior to the Protocol Action announcement being sent.

    The IESG also approved publication of PPP DES Encryption Protocol
    (DESE) <draft-ietf-pppext-des-encrypt-01.txt> as an Informational
    RFC.

    4. The IESG approved publication of The PPP Compression Control
    Protocol (CCP) <draft-ietf-pppext-compression-04.txt> as a Proposed
    Standard. Keith is to provide replacement text for the Working Group
    summary prior to the Protocol Action announcement being sent.

    The IESG also approved publication of the following 10
    Internet-Drafts as Informational RFCs:

    1. PPP Stac LZS Compression Protocol
    <draft-ietf-pppext-stacker-06.txt>
    2. PPP Hewlett-Packard Packet-by-Packet Compression (HP PPC) Protocol
    <draft-ietf-pppext-hpppc-00.txt>
    3. PPP Gandalf FZA Compression Protocol
    <draft-ietf-pppext-gandalf-00.txt>
    4. PPP Predictor Compression Protocol'
    <draft-ietf-pppext-predictor-00.txt>
    5. PPP BSD Compression Protocol
    <draft-ietf-pppext-bsd-compress-05.txt
    6. PPP Deflate Protocol
    <draft-ietf-pppext-deflate-00.txt>
    7. PPP LZS-DCP Compression Protocol (LZS-DCP)
    <draft-ietf-pppext-lzs-dcp-01.txt>
    8. PPP Magnalink Variable Resource Compression
    <draft-ietf-pppext-magnalink-01.txt>
    9. PPP for Data Compression in Data Circuit-Terminating Equipment (DCE)
    <draft-ietf-pppext-dce-compress-00.txt>
    10. PPP Serial Data Transport Protocol (SDTP)
    <draft-ietf-pppext-sdtp-00.txt>

    5. The IESG tentatively approved creation of the MIME Encapsulation of
    Aggregate HTML Documents (mhtml) Working Group in the Applications
    Area. Once the one week review period has passed, and assuming no
    requests to defer are received, the announcement will be sent.

    6. The IESG had no problem with the publication of Hypertext Transfer
    Protocol -- HTTP/1.0 <draft-ietf-http-v10-spec-05.txt> as an
    Informational RFC with the following IESG Note:

    The IESG has concerns about this protocol, and expects this
    document to be replaced relatively soon by a standards track
    document.

    7. The IESG had no problem with the publication of Benchmarking
    Methodology for Network Interconnect Devices
    <draft-ietf-bmwg-methodology-03.txt> as an Informational RFC.

    8. The IESG had no problem with the publication of the following:

    o ZLIB Compressed Data Format Specification version 3.3
    <draft-deutsch-zlib-spec-03.txt , .ps>
    o DEFLATE Compressed Data Format Specification version 1.3
    <draft-deutsch-deflate-spec-03.txt , .ps>
    o GZIP file format specification version 4.3
    <draft-deutsch-gzip-spec-03.txt , .ps>

    as Informational RFCs. However, the following text is to be
    included as an IESG note:

    The IESG takes no position on the validity of any Intellectual
    Property Rights statments contained in this document.

    9. Internet Registry IP Allocation Guidelines was removed from the
    IESG's agenda. A revision is expected, after which it may be
    resubmitted to the IESG.

    10. The IESG had no problem with the publication of Ipsilon Flow
    Management Protocol Specification for IPv4 Version 1.0
    <draft-rfced-info-flowman-00.txt> or The Transmission of Flow
    Labelled IPv4 on ATM Data Links Version 1.0
    <draft-rfced-info-flowlabel-00.txt> as Informational RFCs, but
    request the following text be included as an IESG Note:

    This note documents a private protocol for IPv4-based flows.
    This protocol is NOT the product of an IETF working group nor
    is it a standards track document. It has not necessarily
    benefited from the widespread and in depth community review
    that standards track documents receive.

    Additionally, the IESG requests that title of the second document,
    The Transmission of Flow Labelled IPv4 on ATM Data Links Version
    1.0 be changed to reflect that this is Ipsilon's protocol, as was
    done in the protocol specification document.

    11. The IESG had no problem with the publication of Multilink Protocol
    Plus (MP+) <draft-rfced-info-smith-00.txt>, but request the title
    be changed to "Ascend's Multilink Protocol Plus (MP+)" when
    published as an Informational RFC.

    12. Deirdre announced that she has sent mail to the author of
    Definitions of Managed Objects for DDS Interface Types, an
    individual submission to the RFC Editor, noting that their document
    overlaps with existing standards track efforts. Steve will send a
    note to the RFC Editor requesting that they not publish this
    document until Deirdre has concluded her discussions.

    13. Steve will send a note to the RFC Editor requesting an extension on
    the timeout period for Native ATM Support in the Internet
    <draft-rfced-info-jackowski-00.txt> to allow more time for IESG
    review and comment.

    14. The IESG had no problem with the publication of What is the
    Internet, Anyway? <draft-rfced-info-quarterman-00.txt> as an
    Informational RFC.

    15. Action on Greek Character Encoding for Electronic Mail Messages
    <draft-rfced-info-spinellis-00.txt> was deferred as the author
    intends to submit a revised document. Steve will convey this
    information to the RFC Editor.