INTERNET ENGINEERING STEERING GROUP (IESG)
                      January 13, 1994

        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
   Coya, Steve / CNRI
   Crocker, Dave / SGI
   Crocker, Steve / TIS
   Gross, Phillip / ANS
   Hinden, Robert / SUN
   Huizer, Erik / SURFnet
   Klensin, John / UNU
   Knowles, Stev / FTP Software
   Mankin, Allison / NRL
   Reynolds, Joyce / ISI
   Rekhter, Yakov / IBM (IAB Liaison)
   Rose, Marshall / DBC


Regrets

   Huitema, Christian  / INRIA (IAB Liaison)
   Chapin, Lyman / BBN
   Piscitello, Dave / Core Competence


1. The minutes of the December 30 IESG teleconference were approved.
   Coya to make minutes available in the shadow directories.

2. The IESG approved OSPF NSSA Option
   <draft-ietf-ospf-nssa-option-01.txt> as a Proposed Standard. Coya
   to send announcement to IETF and RFC Editor.

3. The IESG approved Extensions to RIP to Support Demand Circuits
   <draft-meyer-demandrouting-03.txt> as a Proposed Standard. Coya to
   send announcement to IETF and RFC Editor.

4. The IESG approved the publication of Protocol Analysis for
   Extensions to RIP to Support Demand Circuits
   <draft-meyer-rip-analysis-02.txt> for publication as an
   Informational RFC. Coya to to RFC Editor and the IETF.

5. The IESG approved the publication of TN3270 Current Practices
   <draft-ietf-tn3270e-current-pract-04.txt> as an Informational RFC.
   Coya to send announcement to RFC Editor and the IETF.

6. Some changes to internal IESG procedures were proposed and accepted:

   a. At least one week's notice will be given prior to any protocol
      actions appearing on the agenda. This is to give IESG members
      sufficient time to obtain and review the relevant documents.

   b. Associated documents being submitted as Informational RFCs will
      be listed under the Agenda Section on Protocol Actions, and NOT
      under WG Documents.

   c. When a document has been written/submitted by an individual, as
      opposed to being the output of a WG effort, the individual's
      name will be cited.

You are viewing proxied material from infinitelyremote.com. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.