Skip to main content

Minutes interim-1999-iesg-14 1999-08-26 15:30
minutes-interim-1999-iesg-14-199908261530-00

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

minutes-interim-1999-iesg-14-199908261530-00
											
Minutes of the IESG Teleconferences

    INTERNET ENGINEERING STEERING GROUP (IESG)
    August 26, 1999

    Reported by: Steve Coya, IETF Executive Director

    ATTENDEES
    ---------

    Bradner, Scott / Harvard
    Coltun, Rob / Siara Systems
    Coya, Steve / IETF
    Faltstrom, Patrik / Swipnet
    Freed, Ned / Innosoft (IAB Liaison)
    Marine, April / Internet Engines
    Moore, Keith / U of Tennessee
    Narten, Thomas / IBM
    Nordmark, Erik / Sun
    Paxson, Vern / ACIRI/ICSI
    Reynolds, Joyce K. / ISI (IANA Liaison)
    Schiller, Jeff / MIT
    Wijnen, Bert / IBM

    Regrets
    -------
    Baker, Fred / Cisco Systems
    Bush, Randy / Verio
    Carpenter, Brian / IBM (IAB Liaison)
    Leech, Marcus / Nortel
    Oran, Dave / Cisco

    Minutes
    -------

    1. The minutes of the August 12 Teleconference were approved. Steve to
    place in public archives.

    2. The IESG approved publication of IPv6 Router Alert Option
    <draft-ietf-ipngwg-ipv6router-alert-06.txt> as a Proposed Standard.
    Steve to send announcement.

    3. The IESG approved publication of Multicast Listener Discovery (MLD)
    for IPv6 <draft-ietf-ipngwg-mld-02.txt> as a Proposed Standard.
    Steve to send announcement.

    4. The IESG approved creation of the Border Gateway Multicast Protocol
    (bgmp)Working Group in the Routing Area. Steve to send announcement.

    5. The IESG approved publication of Taxonomy of Communication
    Requirements for Large-scale Multicast Applications
    <draft-ietf-lsma-requirements-03.txt> as an Informational RFC. Steve
    to send announcement.

    6. The IESG tentatively Traffic Flow Measurement: Meter MIB
    <draft-ietf-rtfm-meter-mib-10.txt> as a Proposed Standard and the
    following documents as noted:

    o RTFM: Applicability Statement [Informational]
    <draft-ietf-rtfm-applicability-statement-04.txt>
    o Traffic Flow Measurement: Architecture [Informational]
    <draft-ietf-rtfm-architecture-08.txt>
    o SRL: A Language for Describing Traffic Flows and Specifying
    Actions for Flow Groups [Informational]
    <draft-ietf-rtfm-ruleset-language-07.txt>
    o RTFM Working Group - New Attributes for Traffic Flow
    Measurement [Experimental]
    <draft-ietf-rtfm-new-traffic-flow-09.txt>

    Bert to coordinate with author to get an updated document. Once
    available, Bert to contact Steve who will then send the
    announcement.

    7. The IESG approved publication of Security Model with Tunnel-mode
    IPsec for NAT Domains <draft-ietf-nat-security-02.txt> as an
    Informational RFC. Steve to send announcement.

    8. The IESG had no problem with the publication of ECML v1: Field Names
    for E-Commerce <draft-eastlake-ecom-fields-01.txt> as an
    Informational RFC. Steve to notify RFC Editor and ask that the
    following be included as an IESG Note:

    This document is the output of a vendor consortium, and is not the
    output of an IETF Working Group. Implementors of this
    specification are warned that this data model is heavily biased
    toward conventions used in the United States, and the English
    language. As such it is unlikely to be suitable for international
    or multilingual use in the global Internet.

    9. The IESG had no problem with the publication of A Single Rate Three
    Color Marker <draft-heinanen-diffserv-srtcm-01.txt> as an
    Informational RFC. Steve to notify RFC Editor and ask that the
    single occurances of MUST and RECOMMENDED be lowercased.

    10. The IESG had no problem with the publication of A Two Rate Three
    Color Marker <draft-heinanen-diffserv-trtcm-01.txt> as an
    Informational RFC.Steve to notify RFC Editor and ask that the single
    occurances of MUST and RECOMMENDED be lowercased.

    11. The IESG briefly discussed the topic of whether expired Internet-
    Drafts should be maintained on-line (as opposed to being retrievable
    by the Secretariat when necessary), and to what extent non-IETF
    sites performing this should be supported. Scott volunteered to help
    Steve work on clearly stating the issues to be addressed before
    Steve drafted him to help.

    12. The IESG reached the conclusion that appendices which include
    changes from previous versions of Internet-Drafts whould be removed
    when the approved draft is published as an RFC. It was noted that
    when an I-D is updating or replacing a pre-existing protocol, the
    Internet-Draft should document the changes from the previous RFC,
    and the text should be included as part of the document when
    published. Steve to send a note to the RFC Editor conveying this
    position.

    13. Steve reported that organizing two IESG/WGchair lunches during the
    IETF meeting in Washington could be done, but the cost would include
    the loss of two WG/BOF slots on both days (based on the time needed
    to reconfigure the rooms and cleanup). Marcia is investigating all
    possibilities, and Steve will update the IESG at the next telechat.