[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ngrans summary, chicago IETF

Summary of NGTRANS WG Meeting - 25 August 1998 - Chicago IETF

Chairs: Bob Fink, Bob Gilligan and Tony Hain

Attendance: 218 signed in, more than 250 actually present

Marc Blanchet, of Viagenie, announced that he had placed a Cisco IPv6 capable router on the IETF terminal room network for anyone's use to reach the 6bone. The KAME project's IPv6 stack operating on a unix workstation in the terminal room was soon operating over this router using ssh6 back to Japan.  Congrats, folks!

Tony Hain discussed changes that will be made to the ngtrans charter to more accurately reflect the actual work of the group, which is to develop tools and advice to aid in the eventual transition to IPv6, and to make clear that it is not to specify timelines, plans and policies for such a conversion.

Bob Fink discussed the processing of drafts beyond RFC 1933, noting that Experimental will be the preferred status of tools such as SIIT and NAT-PT, and Informational for practice/advice such as 6bone Routing Practice. The Experimental status will allow various ideas to be tried out without full understanding of their final role in transition to IPv6.

Erik Nordmark presented recent changes in the "IPv6 Transitions Mechanisms" draft <draft-ietf-ngtrans-mech-01.txt> for advancement to replace RFC 1933. He also presented a few remaining issues to be resolved on the mailing list. As soon as Erik finishes these few remaining issues up a working group last call will be done to approve sending the draft in to replace the current version, RFC 1933, which is at Proposed Standard status.

Erik Nordmark presented recent changes in the "Stateless IP/ICMP Translator (SIIT)" draft <draft-ietf-ngtrans-header-trans-02.txt> for advancement to Experimental RFC. A working group last call for comments will now be made to send this in for processing as Experimental.

George Tsirtsis presented recent changes in the "Network Address Translation-Protocol Translation (NAT-PT)" draft <draft-ietf-ngtrans-natpt-02.txt> for advancement to Experimental RFC. A working group last call for comments will now be made to send this in for processing as Experimental.

Bertrand Buclin presented recent changes in the "6bone Routing Practices" draft <draft-ietf-ngtrans-6bone-routing-01.txt> for advancement to Informational RFC. A working group last call for comments will now be made to send this in for processing as Informational. 

Kazuaki Tsuchiya presented the Hitachi protocol exchange software for Windows95/98/NT4 systems based on their draft <draft-tsuchiya-ipv4-ipv6-translator-00.txt>. This software is available now for use at http://www.hitachi.co.jp/Prod/comp/network/pexv6-e.htm. The draft of this work should move forward through ngtrans to Experimental RFC.

David Kessens and Bob Fink gave a brief review of the status of the 6bone. There are now 303 sites in 36 countries participating. There are 47 sites participating as backbone sites.

Greg Miller presented the vBNS 6bone plans, which basically is to provide native IPv6 transport across the US with IPv6 routers located in the Wash. DC, Chicago and San Francisco Bay areas operating over OC3c links into the vBNS OC12c ATM network. This will make a full native cross country IPv6 backbone available to the 6bone!  See http://www.vbns.net/IPv6/index.html for more information.

Ivano Guardini presented his new ASpath-tree tool features for monitoring BGP4+ routing inside the 6bone. These tools are up and available at http://carmen.cselt.it/ipv6/bgp/index.htm.
Two updated drafts were then presented from previous work presented at the AATN BOF at the previous IETF as a courtesy to that group as they could not easily schedule there own meeting at this IETF.

Gabriel Montenegro presented the "Negotiated Address Reuse" draft <draft-montenegro-aatn-nar-00.txt>.

Michael Borella presented the "Distributed Network Address Translation" draft <draft-borella-aatn-dnat-00.txt>

It is most likely that work on these two drafts will continue elsewhere, unless they have more ready transition application to IPv6 than currently observed.