Internet Area Summary for IETF 48 (Pittsburgh, Summer, 2000) The following WGs did not meet: AToM MIB (atommib) ICMP Traceback (itrace) Interfaces MIB (ifmib) Point-to-Point Protocol Extensions (pppext) Service Location Protocol (svrloc) The following WGs did not supply a Meeting Summary: IP Over Fibre Channel (ipfc) [note to murali, raj] IP over Cable Data Network (ipcdn) [ no charter yet] The following BOF did not supply a Meeting Summary: IPoPTR Summaries from the following WGs are supplied below: IPNG (ipngwg) Frame Relay Service MIB (frnetmib) [future of WG discusion needed] DNS Extensions (dnsext) Zero Configuration Networking (zeroconf) Layer Two Tunneling Protocol Extensions (l2tpext) Dynamic Host Configuration (dhc) Internationalized Domain Name (idn) Bluetooth. ------------- IPNG (ipngwg) ------------- Meeting summary provided by Bob Hinden . IPng Working Group Met for two sessions August 1, 2, 2000 Steve Deering and Bob Hinden / Chairs Bob Hinden / Document Editor The working group reviewed and approved revised working group charter. Working group will renamed "IP Version 6". Chairs will send charter to the AD's for IESG approval. Summarized meeting between IPv6 directorate and representatives from Internet Address Registries (RIPE, ARIN, APNIC) to talk about the minimum allocation to IPv6 customers from ISP's. Discussion on mailing list reached a consensus on /48 to every subscriber. Deering, Carpenter, Hinden will write a white paper to be submitted to the IAR's. People will attend the next IAR meetings in September and October. Paper will be sent to IPng list. "IPv6 Addressing Architecture" will be submitted to IESG for Draft Standard once new draft is out. Changes needed are clarification on the use of mapped addresses and prohibition on use of unspecified address as source address in a packet. Working group last calls will be started on the following documents: IPv6 Multihoming using RFC2060 (Informational) Privacy Extensions For Stateless Address Autoconfiguration (Proposed) ICMP Name Lookups (Proposed) "Transmission of IPv6 Packets over IEEE 1394 Networks" will be ready for last call after a new draft is produced. The group agreed to take on Dynamic Update of A6 records as an working group work item. The group agreed to make the draft "Bi-Directional Tunneling" a working group document. ---------------------------------- Frame Relay Service MIB (frnetmib) ---------------------------------- Summary received from "Andrew G. Malis" Frame Relay Service MIB WG (frnetmib) Summary Chair: Andy Malis The frnetmib working group met Tuesday, August 1, 2000 from 1415 to 1515. We discussed two MIBs, the Frame Relay Circuit Interface MIB (raft-steinberger-frsi-00.txt) and Definitions of Managed Objects for Frame Relay Service Level Definitions (draft-ietf-frnetmib-frmrelay-service-01.txt). We agreed that work on the first MIB should continue, and it should be generalized to include ATM if possible. We agreed to three action items on the second MIB, after which it will be forwarded to the IESG for PS. ----------------------- DNS Extensions (dnsext) ----------------------- Summary received from Olafur Gudmundsson . Consensus in the WG to propose to extend the WG Charter add standardize MDNS and IDN extensions. Newly admitted WG documents include "DNSSEC road map", "NO record", "Want DNSSEC Record", "DNS for Link Local", "MDNS for admin scope". WG identified a problem that no document describes how an IPv6 host learns the name it's address belongs to thus it can not issue an A6 dynamic update. We will work with IPng and DNSOPS on resolving how do this. Lively discussion on the value in Message size. IPng WG chair has suggested that the Message Size document add the requirement that IPv6 hosts support EDNS0. The WG agreed to update RFC2537 in such a way that RSA is mandatory but change the hash algorithm to SHA/1, and retire RSA/MD5 at the same time this will happen around Sept. 20'th. ---------------------------------------- Zero Configuration Networking (zeroconf) ---------------------------------------- Summary provided by Erik Guttman The Zeroconf WG meeting discussed rechartering. Goals which were presented in the 'straw man' charter were accepted - namely, timely completion of the requirements draft, taking on of the autoconf for IPv4 and multicast address allocation protocol for zeroconf networks. We also discussed outstanding Big Issues in the requirements draft. There was broad support for support of allowing zeroconfiguration protocols to coexist with configured ones - that is not requiring detection and transition of configuration. Other issues were also discussed and will lead to revision of the requirements document if agreed to on the mailing list. ------------------------------------------------- Layer Two Tunneling Protocol Extensions (l2tpext) ------------------------------------------------- L2TPEXT summary provide by "W. Mark Townsley" draft-ietf-l2tpext-ppp-discinfo-00.txt generally accepted as a Good Thing. draft-ietf-l2tpext-l2tp-security-01.txt is fairly stable and should move forward. Some discussion about ipsra, Xauth, etc. ensued. It was noted that this draft defines how to protect L2TP with IPsec only. Changes to IPsec are clearly outside the scope of the WG. The following drafts are ready for WG last call: draft-ietf-l2tpext-ppp-discinfo-00.txt draft-ietf-l2tpext-atmext-03.txt draft-ietf-l2tpext-l2tphc-02.txt draft-ietf-l2tpext-sessinfo-01.txt draft-ietf-l2tp-security-00.txt draft-ietf-l2tpext-fr-00.txt draft-ietf-l2tpext-l2tp-atm-01.txt, The following draft needs resubmission with last call changes before IETF last call. draft-ietf-l2tpext-l2tp-mib-00.txt linkinfo draft will be resubmitted. Much discussion ensued about L2TP being used to carry PDUs other than PPP after presentation of draft-nanji-l2tp-eth-00.txt and draft-mcpherson-l2tp-es-01.txt. It is fairly clear that there are multiple vendors choosing L2TP to tunnel protocols other than PPP. There was discussion about L2TP vs. other tunneling methods, particularly GRE. Proponents cite L2TP's call setup and well standardized tunnel/session aggregation as reasons for choosing the protocol as their solution. Consensus in the meeting was that l2tpext will define only the extensions necessary to L2TP for carrying other PDUs, within the confines of L2TP's extensibility framework (e.g. new AVPs, but no changes in the L2TP protocol itself). This will involve standardization of the AVP(s) that identify the type of PDU to be carried, and new or existing AVPs that will be used during L2TP call setup or teardown. Any real time signaling or modifications to the particular protocol being carried by L2TP are outside the scope of l2tpext WG. If consensus is concurred on the mailing list, l2tp-bis and the l2tpext charter will be revised accordingly. -------------------------------- Dynamic Host Configuration (dhc) -------------------------------- Summary received from Ralph Droms Monday, Jul 31 at 1930-2200 (DHCPv4) Droms made annuncements of recent IETF and WG actions Mark Stapp presented the details of the revised DHCP-DNS interaction mechanism, which is now described in two HC WG drafts and one DNSEXT WG draft. The WG accepted these changes and made suggestions for additional enahncements to be made in the drafts. Stapp to revise with changes based on WG input: add flag so client can request no DNS updates and change to base-64 encoding in DHCID RR. Stapp also to initiate discussion of other input on WG mailing list. Poornima Lalwaney presented Kerberos-based authentication scheme in draft-smedvinksy-dhc-kerbauth-00.txt. WG will discuss and compare draft-smedvinksy-dhc-kerbauth-00.txt and draft-hornstein-dhc-kerbauth-02.txt. Ralph Droms lead discussion of WG charter and milestones. WG developed new charter. Droms to publish updated charter and develop new milestones. Bernie Volz gave update on status of LDAP schema. New version will be published in August. Bernie Volz discussed DHCP load balancing in draft-ietf-dhc-loadb-02.txt. WG agreed to hold WG last call. Bernie Volz gave update on failover protocol in draft-ietf-dhc-failover-07.txt. authors and interested WG members will hold design team phone call in October. Draft will be ready for final WG review in San Diego. Barr Hibbs gave update on the DHCP MIB in draft-ietf-dhc-server-mib-04.txt. He will publish a new revision by the end of August. Subir Das presented DRCP in draft-itsumo-drcp-00.txt. The WG expressed interest in considering the ideas for integration into DHCP at some point in the future. Tuesday, Aug 1 at 0900-1130 (DHCPv6) Mike Carney lead a discussion of the current revision of DHCPv6 in draft-ietf-dhc-dhcpv6-15.txt, and draft-ietf-dhc-dhchpv6exts-12.txt. The WG discussed several specific issues and came to consensus about changes to the specs. The WG also aired concerns about WG input to the spec and progress on the spec. ----------------------------------- Internationalized Domain Name (idn) ----------------------------------- Received from Marc Blanchet ietf idn wg ietf48 meeting, aug 2000 Summary from the chairs At ietf48-pittsburg, idn wg met two times for a total time of 4.5 hours. Agenda covered requirement and comparaison documents, current proposals as idn wg or individual documents, and preliminary deployment experience of proprietary solutions. Seen concensus was: - requirement document should cycle another time in a short period for final changes and then go to wg last call; - comparaison document should continue to be enhanced with the on-going work and new proposals; - design team to work on a converged proposal. IAB also announced a i18n workshop where idn issues will be discussed. ------------------------------------- IP over Bluetooth (ipobt) BOF summary ------------------------------------- Received from Pravin Bhagwat chairs: Pravin Bhagwat (pravinb@research.att.com) Kris Fleming (kris.d.fleming@intel.com) IP over Bluetooth BOF was held on July 31, 2000 during the 48th IETF meeting in Pittsburgh. The BOF was informational; its objective was to provide an open forum for the members of the Bluetooth PAN working group and the IETF to exchange information, debate design issues, and learn about each other's work. Version 1.0 release of the Bluetooth specifications support point-to-point communication between devices. The next release is aimed at making Bluetooth devices IP addressable and supporting IP based any-to-any connectivity among a group of devices. A number of design issues related to address assignment, name resolution, and packet forwarding are being finalized in the Bluetooth PAN working group. The Bluetooth PAN working group is interested in leveraging the output of zero-conf and MANET working groups to the maximum extent possible. The BOF agenda included a number of presentations from the members of the Bluetooth PAN working group. These presentations summarized the status of the current specifications and the features planned for the next realease. During the question answer session, the following key suggestions were made by the attendees. 1) Bluetooth PAN working group should build an Ethernet emulation layer on top of Bluetooth piconets and scatternets. This layer will hide any Bluetooth specific details from the IP layer. 2) The members of the IETF would like to see the Bluetooth SIG and its standardization process opened up. Some IETF members would like to get early access to 2.0 specifications and be interested in providing feedback to the PAN working group. 3) Both the IETF and the Bluetooth PAN working group members agreed that closer interaction is mutually benefitial. To accomplish this, the PAN working group members will participate more actively in relevant IETF working groups. The following action items have been finalized. o A mailing list is set up where further discussions will take place. General Discussion: Bluetooth-BOF@mailbag.intel.com To Subscribe: listserv@mailbag.intel.com In Body: subscribe Bluetooth-BOF first_name last_name o PAN working group members will take feedback from the BOF to the PAN Working Group. o Members of the Bluetooth PAN working group will join relevant IETF working group mailing lists and bring up any Bluetooth specific issues when appropriate.