Skip to main content

Minutes interim-1994-iesg-14 1994-08-11 15:30
minutes-interim-1994-iesg-14-199408111530-00

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

minutes-interim-1994-iesg-14-199408111530-00
											
Minutes of the IESG Teleconferences

    INTERNET ENGINEERING STEERING GROUP (IESG)
    11 August 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
    ---------

    Bradner, Scott / Harvard
    Coya, Steve / CNRI
    Halpern, Joel / Newbridge Networks
    Mankin, Allison / NRL
    Mockapetris, Paul / ISI
    O'Dell, Mike / UUNET
    Reynolds, Joyce / ISI
    Rekhter, Yakov / IBM (IAB Liaison)
    Rose, Marshall / DBC
    Stewart, John / CNRI
    Topolcic, Claudio / BBN

    Regrets
    -------
    Huitema, Christian / INRIA (IAB Liaison)
    Huizer, Erik / SURFnet
    Klensin, John / MCI
    Knowles, Stev / FTP Software
    Schiller, Jeff / MIT

    Internet Engineering Steering Group (IESG)
    Draft Agenda for the 11 August 1994 IESG Teleconference

    1. The IESG approved the minutes for 23 June, 7 July, and 14 July.

    2. Protocol Actions

    o The IESG approved "Transport Multiplexing Protocol (TMux)"
    <draft-cameron-tmux-03.txt> for the status of Proposed
    Standard.

    3. Working Group Informational Documents

    o The IESG recommends that the RFC Editor publish "Octet
    sequences for upper-layer OSI to support basic
    communications applications"
    <draft-ietf-thinosi-cookbook-03.txt> as an Informational
    RFC.

    o The IESG recommends that the RFC Editor publish "K-12
    Internetworking Guidelines"
    <draft-ietf-isn-k12-guide-01.txt,ps> as an Informational
    RFC.

    4. RFC Editor Actions

    o The IESG has no objections to the RFC Editor publishing
    "The Document Architecture for the Cornell Digital
    Library" as an Informational RFC.

    5. Working Group Actions

    o The charter of the Inter-domain Routing Working Group (IDR)
    was approved. This group represents the merging of the BGP
    and IPIDRP Working Groups.

    o The charter of the New Internet Routing Architecture Working
    Group (NIMROD) was approved.

    6. Management Issues

    o There will be an "IP6 walk-through" multicasted on the MBone
    on 22 August. Presenters will be primarily at Xerox PARC and
    MIT; there will be an additional conference room at ISI.

    o IBM asked Scott Bradner if they could convene a BOF on their |
    MPTN (Multi-Protocol Transport Networking) at the next IETF |
    meeting. The IESG had no objections. |

    o Interop has offered to give meeting space to the IESG at no
    charge at its INTEROP show in Las Vegas 27-31 March 1995.
    Interop will advertise it, but the IESG has complete control
    over the speakers, content, etc. The IESG agreed to accept
    the offer and will decide on the format later.

    ACTION(Rose): Send tentative conference agenda to the IESG to help
    the IESG in scheduling.

    o Interop has scheduled their Japan conference in the summer of
    1995 for the same week as the Stockholm IETF meeting. The
    IETF Secretariat is investigating if the Stockholm meeting
    can be rescheduled.

    o Steve Coya has been trying, with some, albeit little, success,
    to reach Motorola to see what they think their patent covers
    relative to PPPEXT's compression negotiation protocol. The
    IESG cannot do anything with the protocol, with respect to the
    standards track, without assurances from Motorola.

    o The negotiations with Sun over bringing RPC and XDR into the IETF
    have, to date, been between SunSoft and the IETF. Now SunSoft's
    patent lawyer has gotten involved, and the situation is even more
    complex. The topic will be on the agenda for the next meeting.

    ACTION(Stewart): Put Sun/ONC issue on next agenda.

    o The IESG decided that it should consider moving EGP and
    "Requirements for Internet Gateways" (RFC 1009) to Historic.

    ACTION(Halpern,Rekhter): Do write-up for moving EGP and "router
    requirements" to Historic.

    This once again brought up the question of the status of host
    and router requirements.

    ACTION(Bradner,Knowles,O'Dell,Topolcic): Discuss how to motivate the
    Router Requirements Working Group to complete its charter.

    o The IESG agreed that titles of Informational RFCs should not
    imply any kind of status or applicability.

    ACTION(Mockapetris): Communicate the above to the RFC Editor.