Protocol independent netfilter infrastructure basically done do we need NAT? Neighbor state transition does not confrom to the spec. amount of "fragment header" (8 bytes) are always eaten in case fragmentation is required. It's time to remove "EXPERIMENTAL" and say Y! "Fragment header" (8 bytes) is always reserved. how to select an entry in the list? Discussed with HUT GO/Core Project search first rule what the request conforms to. lookup route in the table which is specified by the rule if returned route conforms to the rule, use it. Copy "ipv4/ipmr.c" is not good, I think. like Binding Cache, but it is not the same.

This article is a brief introduction to the new IPv6 protocol. The TCP (Transmission Control Protocol) provides a reliable bidirectional connection between two hosts, using the communication facilities provided by the IP (Internet Protocol). In fact, IP is a network layer protocol and its task is to deliver packets of data from a source host to a destination host. IPv4 has been used since the Internet was born and has worked very well until now, but it has many serious limits that IPv6 has been designed to overcome. The authentication header mechanism allows the receiver to be reasonably sure about the origin of the data, and the IPSEC privacy facilities provide end-to-end encryption of data at the network layer.

· RFC 2535 vs DS vs ??? · Most issues appear to be known. · fast, edns0 capable code is becoming available. · a draft recommendation to ICANN/DoC for formally augmenting the roots with IPv6 transport is being circulated. · IPv6 DNS will appear sporadic, less stable due to local optimizations for IPv4, common case capabilities, e.g. firewalls, proxy DNS servers, load balancers. · These "landmines" must be eradicated for seamless integration of IPv6.

Services Extension for Message Size Declaration, November 1995. Services Extension for Message Size Declaration, November 1995. Incremental Zone Transfer in DNS, August 1996. IETF RFC 2205, Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification, September 1997. Payload (ESP), November 1998 IETF RFC 2407, The Internet IP Security Domain of Interpretation for ISAKMP, November 1998. 1. Hosts / Operating Systems - Hosts are computers that generally execute application programs on behalf of users and share information with other hosts. 2. Routers - Networks are made up of subnetworks, and the internetworking (router) elements needed for information transfer. This section identifies the standards needed to access certain subnetworks and for routing and interoperability between the subnetworks.

Applications may have problems demultiplexing packets from multiple sources Not a problem with RTP applications using Sync. Can addresses be reused between multicast groups? That is, two different IPv6 sources get same IPv4 address if same group. In order to apply it to large-scale network systems, it is necessary to automate the setup which the administrator carries out according to the requests of the receivers. Gateway solves this using PIM for signaling What now? Is IPv4-IPv6 coexistence/transition multicast solutions like this worth looking into? Would this be the right WG for any further work?

Addresses formed from network pre>x + host id. NB: manual or DHCPv6 assignment also possible. WinXP ipv6 enable OS X Enabled in Jaguar/Panther. Redhat AddNETWORKINGIPV6="yes" to /etc/sysconfig/network FreeBSD Addipv6enable="YES" to /etc/rc.conf Solaris Create/etc/hostname6.ifname. Can be same as IPv4 router, but doesn't need to be the same or use specialised hardware.

To research and develop test and measurement tools for IPv6 and to facilitate early vendor interoperability testing and pilot deployment activities on the 6Bone. · Establish IPv6 interoperability testbed & facilitate vendor testing. · Facilitate the establishment of the 6Bone. · Devise test and measurement tools for IPv6 and 6Bone network. · Deliver testing technology that makes a demonstrable impact on the IPv6 research and development community.

In parallel with the protocol suite, the IETF has also built a toolkit to help ensure a seamless transition from IPv4. IPv6 does not provide any better (or worse) support for quality of service than IPv4, but it does have many features you might already be familiar with, including larger address space, integrated security capabilities, easier configuration, and a simplified packet header format. Networks that offer IPv6 connectivity are already popping up around the globe; NTT currently offers a dual-stack service in Japan, for example (www.ipv6style.jp/en/ news/2003/0313_ntt.shtml). Egged on by competing interests, proponents of various network architectures, protocols, and products have stridently denounced one another --- creating headlines and lively conference panels, but little agreement.

This insightful volume covers IPv6 in detail and explains how the protocol works, what the new features and mechanisms are, and how they are implemented. Aimed at a broad range of professionals, including system and network administrators, engineers, network designers, and IT managers, IPv6 Essentials is for anyone who wants to understand how to plan for, design, and integrate IPv6 into a current IPv4 infrastructure. The book teaches networking professionals what they need to know in order to get started, how to configure IPv6 on hosts and routers, and how to find the right applications that support IPv6.

· Status in Linux 2.4 Why do we need IPv6? · IPv4 was invented in 1975; needs have changed. -- No confidential data being transmitted Why do we need IPv6? -- Not required in all IPv4 implementations -- Multicast "islands in the Net" (MBONE) Why do we need IPv6? -- Limited auto-configuration support (needs DHCP) What's changed in IPv6? -- Confined to the subnet; not routable! -- Confined to the Organization; limited routing. -- Provide optional enhancements to vanilla header. -- Must be a multiple of 8 bytes in length. · Complement the 2nd low-order bit of the MAC addr.

What innovative uses might we have for those 20 bits? · Or is the 20-bit Flow Label simply a waste of space? -- What are the implications of end-to-end security? · Will we require stronger host security as a result? · We live in a world of middleboxes - proxies, firewalls, NATs, as discussed in IETF documents including RFC2775. · Should we have stateless DNS discovery? · There will be no NAT in IPv6? · Multicast support is better in IPv6? · Don't deduce IPv6 connectivity via DNS records! · IPv6 forwarding handled in hardware (e.g. Juniper) · Site local addressing is needed in IPv6?

IPv6 will support the deployment of Internet services to the vast number of devices around the world that are likely to join the network over the next few years. This paper explains Nortel Networks views of the development of IPv6 and its interplay with the Nortel Networks robust networking architecture. The success of IPv6 as a new architecture and technology will likely be determined by its ability to integrate smoothly into the existing infrastructure without significant disruption to existing services. Nortel Networks recognizes the size of this task and is working to develop solution recommendations which can be used as the basis for customers' planning in various scenarios.