Skip to main content

Minutes interim-1995-iesg-15 1995-09-14 15:30
minutes-interim-1995-iesg-15-199509141530-00

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

minutes-interim-1995-iesg-15-199509141530-00
											
Minutes of the IESG Teleconferences

    INTERNET ENGINEERING STEERING GROUP (IESG)
    September 14, 1995

    Reported by: Steve Coya, IETF Executive Director

    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-9528103

    For more information please contact the IESG Secretary at
    <iesg-secretary@ietf.cnri.reston.va.us>.

    ATTENDEES
    ---------

    Coya, Steve / CNRI
    Halpern, Joel / Newbridge Networks
    Kastenholz, Frank / FTP Software
    Klensin, John / MCI
    Mankin, Allison & family / ISI & Mankin Productions
    O'Dell, Mike / UUNET
    Schiller, Jeff / MIT
    Thomson, Susan / Bellcore

    Regrets
    -------

    Alvestrand, Harald / Uninett
    Bradner, Scott / Harvard
    Carpenter, Brian / CERN (IAB Liaison)
    Kostick, Deirdre / AT&T Bell Labs
    Mockapetris, Paul / @home
    Rekhter, Yakov / cisco (IAB Liaison)
    Reynolds, Joyce / ISI

    Minutes
    -------
    1. The minutes from the August 31 teleconference were approved. Coya to
    place in Shadow directories.

    2. The IESG deferred action on Hypertext Markup Language -2.0
    <draft-ietf-html-spec-05.txt>, a candidate for Proposed Standard. A
    request was made to add clarification text to the document so that
    implementation will not require historical (i.e. undocumented
    folklore) knowledge to understand the applicability of the
    specification. John will take this up with the working
    group/document authors.

    3. The IESG approved the publication of Internet Protocol, Version 6
    (IPv6) Specification <draft-ietf-ipngwg-ipv6-spec-02.txt> as a
    Proposed Standard. Coya to send announcement.

    4. The IESG approved the publication of IP Version 6 Addressing
    Architecture <draft-ietf-ipngwg-addr-arch-03.txt> as a Proposed
    Standard. Coya to send announcement.

    5. The IESG approved the publication of Internet Control Message
    Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)
    <draft-ietf-ipngwg-icmp-02.txt> as a Proposed Standard. Coya to send
    announcement.

    6. The IESG approved the publication of DNS Extensions to Support IP
    Version 6 <draft-ietf-ipngwg-dns-00.txt> as a Proposed Standard.
    Coya to send announcement.

    A concern was raised pertaining to the coexistence of A and AAAA
    records. It was explained that this is a transition issue and
    addressed in the transition document, currently in last call. Coya
    to send a separate note will be sent to the RFC Editors informing
    them that Sue will be adding a reference to the approved document
    prior to publication.

    7. The IESG approved the publication of An Architecture for IPv6
    Unicast Address Allocation
    <draft-ietf-ipngwg-unicst-addr-allo-01.txt> as an Informational
    RFC. Coya to send announcement.

    8. The IESG approved the publication of A BGP/IDRP Route Server
    alternative to a full mesh routing
    <draft-haskin-bgp-idrp-mesh-routing-01.txt> as an Experimental
    Protocol. Coya to send announcement.

    9. The IESG tentatively approved the Guide for Internet Standards
    Writers Working Group pending a revised charter from Mike. The
    revision will clear up some items, and change the milestone so the
    output is a BCP document instead of an Informational RFC.

    If the revised charter meets these new requirements, the WG will be
    announced. Otherwise, it will appear on the next telechat agenda.

    10. Allison reported that some members of the IAB are concerned about
    the MIME type registration procedures. John is concerned too :-)

    The IAB asked the IESG to devise a process which is expeditious and
    requires a last call period for registering new mime types. It was
    noted that the last call period would not address the concerns
    being raised. Further, there is no conflict resolution procedures
    for mime types (two requests to register the same/some one else's
    type).

    However, John saw no problem with initiating a last call process,
    but as it is a policy change, the IANA needs to agree to it.

    John also reported a design team effort currently underway that
    proposed to eliminate flat addresses space, which should go far in
    addressing the current IAB concerns, but not all of them. The
    proposal is expected in the next few weeks.