DRAFT * DRAFT * DRAFT * DRAFT *  DRAFT * DRAFT * DRAFT * DRAFT *

           INTERNET ENGINEERING STEERING GROUP (IESG)
                      December 16, 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.
[email protected].



ATTENDEES
---------

   Bradner, Scott / Harvard
   Chapin, Lyman / BBN
   Coya, Steve / CNRI
   Crocker, Dave / SGI
   Gross, Philip / ANS
   Huitema, Christian  / INRIA (IAB Liaison)
   Huizer, Erik / SURFnet
   Klensin, John / UNU
   Knowles, Stev / FTP Software
   Mankin, Allison / NRL
   Reynolds, Joyce / ISI
   Piscitello, Dave/ Bellcore
   Rekhter, Yakov / IBM (IAB Liaison)
   Rose, Marshall / DBC

Regrets
   Hinden, Robert / SUN
   Crocker, Steve / TIS

1. The minutes of the December 2, 1993 meeting were approved. Coya will
  place copy in the public directories

2. The IESG approved the publication of the following three
  Internet-Drafts as Proposed Standard:

       Network Services Monitoring MIB
       Mail Monitoring MIB
       X.500 Directory Monitoring MIB

  Coya to send notification to the IETF and the RFC Editors


3. The IESG discussed the status of the Classical IP and ARP over ATM
  document that has been submitted for Proposed Status. The WG needs
  to clarify the meaning of "Classical" as used in the document. If it
  refers to IPv4, the use of the word MUST in requiring a router
  between virtual lans must be changed. If it refers to the classical
  paradigm, then it would be acceptable. A revision of the document
  clarifying the definition of Classical is required.

  Scott will send message to the WG conveying the concerns of the IESG
  and requesting that a revision be submitted as an Internet-Draft
  which clarifies the definition of the word Classical.


4. The IESG approved the publication of Questions and Answers to
  Commonly Asked "Primary and Secondary School Internet User" Questions"
  <draft-ietf-isn-faq-02.txt> as an Informational FYI RFC.

5. The IESG approved the publication of Essential Tools for the OSI
  Internet <draft-ietf-noop-tools-03.txt> as an Informational FYI RFC.

6. The status of the Router Requirements document was discussed. The
  current document will be submitted as an Internet-Draft, and a
  new Router Requirements Working Group will be established. Stev and
  Dave P. will work together on identifying and choosing the WG Chair.

7. The IESG approved RSVP as a Working Group in the Transport Services
  Area. Coya to enter charter and milestone information and send an
  announcement to the IETF community.

8. Scott Bradner requested that if any Area Director knows of a
  proposal that might have some operational impact, they should give
  the OPS Area Director an explicit referral.

9. The IESG discussed the Simple Network Paging Protocol document which
  is an individual submission. Discussion moved to the more general
  topic of whether the IESG can insist or request that text reflecting
  the IESG's opinion on the subject be included as part of the
  document. While this has been done in the past for experimental
  protocols, there was a difference of opinion as to whether this
  ability could or should be expanded to include Informational RFCs.
  It was noted that the RFC Editor had implied that additional text
  would be considered. No consensus was reached.