Minutes interim-1999-iesg-17 1999-10-07 15:30
minutes-interim-1999-iesg-17-199910071530-00

											
Minutes of the IESG Teleconferences

    INTERNET ENGINEERING STEERING GROUP (IESG)
    October 7, 1999

    Reported by: Steve Coya, IETF Executive Director

    ATTENDEES
    ---------

    Baker, Fred / Cisco Systems
    Bradner, Scott / Harvard
    Bush, Randy / Verio
    Carpenter, Brian / IBM (IAB Liaison)
    Coya, Steve / IETF
    Faltstrom, Patrik / Tele2
    Freed, Ned / Innosoft (IAB Liaison)
    Marine, April / Internet Engines
    Narten, Thomas / IBM
    Nordmark, Erik / Sun
    Oran, Dave / Cisco
    Paxson, Vern / ACIRI/ICSI
    Reynolds, Joyce K. / ISI (IANA Liaison)
    Schiller, Jeff / MIT
    Wijnen, Bert / IBM

    Regrets
    -------
    Coltun, Rob / Siara Systems
    Leech, Marcus / Nortel
    Moore, Keith / U of Tennessee

    Minutes
    -------

    1. The minutes of the September 23 Teleconference were approved with
    the addition of a note that the IESG approved the rechartering of
    the AAA WG. Steve to incorporate change and place in public
    archives.

    2. The IESG approved publication of An RTP Payload Format for Generic
    Forward Error Correction <draft-ietf-avt-fec-08.txt> as a Proposed
    Standard. Steve to send announcement.

    3. The IESG approved publication of the following documents as Proposed
    Standards:

    RSVP Diagnostic Messages
    <draft-ietf-rsvp-diagnostic-msgs-08.txt>
    RSVP Operation Over IP Tunnels
    <draft-ietf-rsvp-tunnel-04.txt>
    RSVP Cryptographic Authentication
    <draft-ietf-rsvp-md5-08.txt>

    Steve to send announcement.

    4. The IESG approved publication of IPv4 over IEEE 1394
    <draft-ietf-ip1394-ipv4-18.txt> as a Proposed Standard. Steve to
    send announcement.

    5. The IESG approved publication of Format for Literal IPv6 Addresses
    in URL's <draft-ietf-ipngwg-url-literal-04.txt> as a Proposed
    Standard. Steve to send announcement.

    6. The IESG approved publication of Entity MIB (Version 2)
    <draft-ietf-entmib-v2-06.txt> as a Proposed Standard. Steve to send
    announcement.

    7. The IESG approved formation of the Internet Traffic Engineering
    (tewg) Working Group. Steve to send announcement.

    8. The IESG approved formation of the Transport Area Working Group
    (tsvwg) Working Group. Steve to send announcement.

    9. Steve to send the WG Review message to the IETF and new-work lists
    for Layer Two Tunneling Protocol Extensions (l2tpext).

    10. Steve to send the WG Review message to the IETF and new-work lists
    for Endpoint Congestion Management

    11. Steve to send the WG Review message to the IETF and new-work lists
    for Telephone Number Mapping (enum)

    12. Steve to send the WG Review message to the IETF and new-work lists
    for Service in the PSTN/IN Requesting InTernet Service (spirits).

    13. The IESG consensus was to NOT publish Simple Protocol Application
    Data Encoding <draft-hudson-spade-03.txt> as an Experimental
    Protocol. Patrik to provide text to Steve who is to notify the RFC
    Editor.

    14. The IESG consensus was to NOT publish MTU discovery using TCP MSS
    and Discussion on MSS value in SYN reply
    <draft-bvenkat-mtu-tcpmss-03.txt> as an Experimental RFC. Steve to
    convey to RFC Editor.

    15. The IESG requested Thomas to draft a message to be sent to the
    author of Internet Protocol Specifications for IPv7 and IPv8 Address
    Classes <draft-terrell-ip-spec-ipv7-ipv8-addr-cls-00.txt> stating
    that the IESG does not feel this document should be published as a
    Proposed Standard.

    16. The IESG reiterated its decision to recommend against the
    publication of the following Internet-Drafts:
    draft-simpson-cbc-01.txt
    draft-simpson-desx-02.txt
    draft-simpson-des3v2-03.txt

    The reason (to be included in the messgage) is: these
    recommendations describe and document procedures for IPSEC
    interoperation which differs from that described in RFC 2451,
    resulting in non-inoperability, and is indistinguishable by the
    usual markers such as version number, IP Protocol number, and the
    like.

    Steve to convey to RFC Editor.