Minutes interim-1994-iesg-17 1994-09-22 15:30
minutes-interim-1994-iesg-17-199409221530-00

											
Minutes of the IESG Teleconferences

    INTERNET ENGINEERING STEERING GROUP (IESG)
    22 September 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
    Huitema, Christian / INRIA (IAB Liaison)
    Klensin, John / MCI
    Knowles, Stev / FTP Software
    Mankin, Allison / NRL
    Mockapetris, Paul / ISI
    O'Dell, Mike / UUNET
    Rose, Marshall / DBC
    Schiller, Jeff / MIT
    Stewart, John / CNRI
    Topolcic, Claudio / BBN

    Regrets
    -------
    Huizer, Erik / SURFnet
    Rekhter, Yakov / IBM (IAB Liaison)
    Reynolds, Joyce / ISI

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

    2. Protocol Actions

    The IESG decided to wait until the next meeting before moving
    "Requirements for Internet Gateways" (RFC 1009) to Historic. The
    reason for the delay is to get an update on the progress of the
    "RREQing crew," to see if a replacement for RFC 1009 will be
    completed in the near future.

    ACTION(O'Dell): Be prepared to give an update on the "RREQing crew"
    during the next IESG teleconference.

    3. RFC Editor Actions

    The Transport Area Directorate completed its review of the RFC
    submission "An Extension to TCP : Partial Order Service," and
    found several problems with it. The directorate is writing text
    discouraging people from implementing the TCP extension, and
    will request that the IESG ask the RFC Editor to place that text
    on the front page of the RFC.

    ACTION(Mankin): Complete the write-up and send it to the RFC Editor
    (cc'ing the IESG) in a timely manner.

    4. Management Issues

    o The Internet Monthly Report's "Internet Engineering Reports"
    section will now announce the availability of new IESG
    meeting minutes.

    ACTION(Coya): Add a new section for 'new IESG minutes' in the text
    submitted for the IMR.

    o The IPng recommendation has been announced as an Internet-
    Draft. Very shortly a month-long Last Call will be made for
    moving the document to Proposed Standard. Immediately after
    the Last Call expires, the IESG will have a single-topic
    meeting to discuss the recommendation and comments received
    during the Last Call.

    o On the agenda for an up-coming ATM Forum meeting, there are
    items for integrated IP over ATM and an IP routing protocol.
    There is some concern that this represents too much of an
    over-lap with IETF activities.

    ACTION(Halpern, Mockapetris): Halpern will put his concerns in
    writing for Mockapetris who will decide what next step should be
    taken (if any).

    o A list of issues related to the "IETF part of ISOC?" question
    will be developed to serve as a starting point for IESG
    discussion on that topic.

    ACTION(Mockapetris): Create the list mentioned above.

    o For the IETF logo contest, a judging panel consisting of Stev
    Knowles, Paul Mockapetris, and Mike O'Dell has been formed.

    ACTION(Mockapetris): Announce the logo contest, along with details
    for how to make a submission.

    o Masataka Ohta has requested that his Internet-Draft on multi-
    lingual encoding be made a Proposed Standard. Character sets
    is an agenda item for the up-coming IAB workshop, and the
    IESG decided that it does not want to standardize something
    on this issue until some architectural decisions have been
    made.

    ACTION(Klensin): Communicate the above to Masataka Ohta.

    o A representative from OSF/DCE responded to the Last Call for
    "URL to Proposed and URN- and IRL-Reqs to Information"; he
    has asked that publication of URN requirements be delayed on
    the grounds that OSF/DCE is working on related technology.
    The IESG agreed that it should not delay the progression of
    these documents; furthermore, such a request is more
    appropriately directed to the author of the document (the
    URI Working Group).

    ACTION(Coya): Communicate the above to the OSF/DCE representative.