Minutes interim-1998-iesg-08 1998-05-07 15:30
minutes-interim-1998-iesg-08-199805071530-00

											
Minutes of the IESG Teleconferences

    INTERNET ENGINEERING STEERING GROUP (IESG)
    May 7, 1998

    Reported by: Fred Baker

    ATTENDEES
    ---------

    Baker, Fred / cisco
    Carpenter, Brian / IBM (IAB Liaison)
    Faltstrom, Patrik / Swipnet
    Leech, Marcus / Nortel
    Marine, April / Sterling Software
    Moore, Keith / U of Tennessee
    Narten, Thomas / IBM
    Paxson, Vern / Lawrence Berkeley Laboratory
    Wijnen, Bert / IBM
    John Klensin / MCI (IAB Liaison)
    Joyce K. Reynolds / ISI (IANA Liaison)

    Regrets
    -------
    Alvestrand, Harald / Maxware
    Bradner, Scott / Harvard
    Burgan, Jeff / @home
    Coltun, Rob / Fore Systems
    Coya, Steve / CNRI
    Schiller, Jeff / MIT

    Minutes
    -------
    The IESG approved publication of

    1. The minutes of the April 23 Teleconference were approved. Steve to
    place in public archives.

    2. The IESG approved publication of the following documents as DRAFT
    Standards:

    TFTP Blocksize Option [DRAFT]
    <draft-malkin-tftpexts-blksize-opt-03.txt>
    TFTP Option Extension [DRAFT]
    <draft-malkin-tftpexts-option-ext-00.txt>
    TFTP Timeout Interval and Transfer Size Options [DRAFT]
    <draft-malkin-tftpexts-options-01.txt>

    Steve to send announcement.

    3. The IESG tentatively approved publication of A Distributed MARS
    Service Using SCSP <draft-ietf-ion-scsp-mars-02.txt> when it is
    submitted. When Steve notified by the ADs that the new version is
    acceptable, an announcement will be sent.

    4. The IESG had no problem with the publication of Making Postscript
    and PDF International <draft-palme-int-print-03.txt>, but suggested
    the RFC Editor add text noting that these are trademarks of Adobe.
    Steve to convey to RFC Editor.

    6. The IESG felt that A Legal Basis for Domain Name Allocation
    <draft-rfced-info-vaughan-v2-00.txt> was outside the scope of the
    IETF. The IESG takes no position on whether it should be published,
    and suggests that the RFC Editor consults the IANA about it. That
    said, it appears to depend on corporations changing their domain
    names from their present form to more cumbersome handles, such as
    changing cisco.com to cisco-systems.co.ca.us or ibm.com to
    international-business-machines.co.ny.us, without giving them an
    incentive to do so, such as deprecating the .com and .net gTLDs. It
    also appears to legislate the structure each national registry
    applies to its name space, something which the document itself
    asserts is within national purview and not for global
    standardization. The IESG suggests that it may not be politically
    feasible to implement as described.

    If it is published, the IESG recommends that the title be changed to
    "A Convention for using Legal Names in DNS Names", as that better
    describes the intent of the document.

    Steve to convey this to the RFC Editor.

    7. The IESG had no problem with the publication of Domain Names and
    Company Name Retrieval <draft-klensin-tld-whois-03.txt> as an
    Experimental RFC. Steve to convey to RFC Editor.

    8. The IESG had no problems with the publication of the NEXT version
    (assuming one is submitted) of PF_KEY Key Management API, Version 2
    <draft-mcdonald-pf-key-v2-05.txt>. Steve to notify RFC Editor.

    9. The IESG felt the following individual submissions should not be
    published at this time:

    o Distributed Robots: a Technology for Fast Web Indexing
    [EXPERIMENTAL]
    <draft-rfced-exp-cosmo-00.txt>
    o A Protocol for the Transmission of Net News Articles over
    IP multicast [EXPERIMENTAL]
    <draft-rfced-exp-rupp-04.txt>

    Authors will be contacted with comments. Steve to inform the RFC
    Editor.

    10. The IESG's consensus on Day passes is that while it seems like a
    reasonable idea on the surface, it encourages rubber-neckers and
    limited players. It seems like unnecessary complexity for something
    we don't want to encourage. We want to encourage cross-attendance.

    Take no action now.

    11. Gate crashing: Brian's suggestion that we bill the company is wrong
    - we should invoice the person. We should also announce that the
    security folks will spot check working group attendees, and have
    them do so. It would be worth mentioning that legitimate cases, such
    as students, can be brought to the Executive Director, who has
    discretion to offer a reduced rate or to waive the fee.

    It was suggest that we find out what USENIX did about this problem
    ten years ago.

    12. The IESG thought the time was right to initiate the process to
    publish Some Thoughts on the Importance of Modesty and Decorum and
    the Need for an IETF Code of Conduct
    <draft-odell-code-of-conduct-02.txt> as a BCP.

    Steve to send Last Call.