 |
Name: Jun-ichiro HAGINO |
The role I played in the KAME project
I was mainly in charge of porting to platforms, feed back of the outcomes to NetBSD and OpenBSD, liaison with *BSD groups, and all kinds of debugging and rewriting (in short, I was a jack-of-all-trades). Also, at the same time, I assisted, and sometimes took initiative, in the standardization of IPv6-related things at the IETF. With regards to these two (KAME project and IETF activities), they were two sides of the same coin. For example, I found issues in the IETF specs while programming for the KAME project, or, while working on the creation of the IETF specs I implemented test code for the specs using KAME, and so on.
What I gained from working in the KAME project
I felt deeply that we could accomplish great things within the KAME project if talented engineers assembled and worked together. I look forward to more collaborative opportunities (and their outcomes) that break down the walls between companies, just like the KAME project did. As for international matters, what sticks out in my mind is that I was able to carve my way into the IETF and each US vendor community through the KAME project. At the IETF, I worked as an IAB member for two years and I was also the chair, albeit for a short time, for the v6ops Working Group. I really appreciate that, while wearing a KAME hat, I was able to prod on US vendors and was able to mingle with members of the development teams for US vendors.
What professional activities I would like to work on (not related to the KAME project) in the future
My activities on the KAME Project are completed for now, however, the level of IPv6 propagation is not satisfactory. Until anyone can buy an IPv6-ready router in Akihabara and until all the ISPs start IPv6 service, IPv6 supporters, including us, will continue to fight. I don’t mean to get too personal, but I became very sick because I was too eager towards the KAME project activities. (I’m currently on leave from work.) So, I would like to teach young people how to work moderately or what would be a moderate amount of work. When you have a career in research, sometimes you get too involved in the topic, but I don’t think people really know how dangerous it is.
 |
Name: Kazuhiko YAMAMOTO |
The role I played in the KAME project
My two biggest contributions were that I triggered the idea to found the KAME project and that I served as the technical leader for eight years. What I wanted to do the most was programming, but I satisfied this desire by creating a mail reader for a different project. So, I devoted myself to the tasks that other “core” members didn’t do much. These tasks include reporting to “papa”, public relations, propagation, writing, and administrative work. I appreciate my employer, Internet Initiative, for allowing me to undertake activities freely, and at the same time, I am proud to be their employee.
What I gained from working in the KAME project
What I learned, not just from the KAME project, but also from various activities was that “perseverance leads to success”. I’ve known this proverb since my childhood, but I was finally able to learn that every day efforts create big results. Other than this, there isn’t much difference among technologies suggested by people. Someone else’s suggestion might sound bad at first glance, but actually was appropriate in the long run, or my suggestion might be vice versa. I was able to learn to eliminate my bias, as much as possible, against technologies and people that I’m not familiar with.
Professional activities I would like to work on (not related to the KAME project) in the future
I would like to think about network technology, including IPv6, in terms of applications. Also, I’m working on the propagation of anti-spam mail technology these days. I would like to kick spam mail out of the Internet and would like to get the good old e-mail environment back.
 |
Name: Tatuya JINMEI |
The role I played in the KAME project
As with the other “core” members, my direct contribution was probably the code I wrote. Among the code I provided were features, such as DNS, multicasting, DHCPv6, etc., that were lacking from IPv6 at the time, and I tried my best to make the KAME project continuously be on the cutting-edge, implementation, I learned that I was able to debate with engineers in the same field as more than their equal even when there was a language handicap. It also gave me greater confidence and supported me when I tried something new. I marched right into the ISC alone and learned the details of BIND. I issued an RFC, and in the end, I received a Ph.D degree. I think that I was able to achieve all these due to the accumulation of the above-mentioned small gains in confidence.
What I gained from working in the KAME project
There is so much that I learned, but the biggest thing, I think, in terms of things that became my sustenance, was “confidence”. With the confidence that I gained from the fact that I myself was working on this cutting-edge implementation, I learned that I was able to debate with engineers in the same field as more than their equal even when there was a language handicap. It also gave me greater confidence and supported me when I tried something new. I marched right into the US ISC by myself and learned the details of BIND. I issued an RFC, and in the end, I received a PhD degree. I think that I was able to achieve all these due to the accumulation of the above-mentioned small gains in confidence.
Professional activities I would like to work on (not related to the KAME project) in the future
Through the KAME project activities, I became convinced that programming is what I have been called to do. There seems to be, in society, a “theory “ that programmers’ retirement age is 30or 40 years old. However, now that I’ve been so involved in it, I would like to keep programming until I can’t any more, being fixated on contributing to society with the code that I write in order to be the counterexample for that theory. I think the technologies that I will work on in the future include ones other than IPv6; however, I will, of course, try contributing in the further growth of my dear IPv6.
 |
Name: Shoichi SAKANE |
The role I played in the KAME project
One day in March 1998, I was very excited when I heard about a project that aimed to propagate IPv6 worldwide because I was implementing IPsec, which just had its specs released, on BSD/OS. “My work will be spread around the world.” There is no other work as worthwhile as this to an engineer. I implemented a feature that managed the IPsec stack and key on early versions of the kernel. Also, I implemented the kernel interface and the API along with a program that adjusted IPsec parameters between the communication devices. Aside from this work, I created various tools; especially, I created a method of delivering music over IPv6 and had fun using it within the project. Also, I think the role I played as a key person in the sharing of information among IPsec implementers was important as well.
What I gained from working in the KAME project
More than anything, I really treasured getting to know many engineers from all over the world. This was because, if you collaborate with many others, things that you could not do by yourself become possible, and even things you could do will become better. Being able to debate problems with, and suggestions for, specs at the IETF meetings and interoperability tests was also a good experience for me to learn the process of standardization of Internet technology. Around that time, I didn’t know anything about the IETF’s standardization process and believed that specs just existed. However, I have come to learn that specs are something that you create on your own. Furthermore, this is one of the fundamentals for research and development, but since I didn’t have a habit of writing documentation and performing assessments after implementing something, I’m glad that I learned quite a bit on the importance of these matters.
Professional activities I would like to work on (not related to the KAME project) in the future
I would like to make a more stable implementation of racoon version 2, which is what I’m developing right now, and I would like people from all over the world to use it, as they did with version 1. Also, if I have the opportunity, I would like to implement the revised portions of the IPsec specs, and think about how to make IPsec easy to use. Furthermore, using the personal contacts and the experience that I gained through the KAME project, I would like to think about how to automatically build sensor-based networks that enables secure communications.
 |
Name: Shinsuke SUZUKI |
The role I played in the KAME Project
Because I am involoved in routers/switches business in my company, I’ve worked on the development of multicast-related technologies (PIM-SM extensions and IGMPv3/MLDv2). Aside from that, I’ve also contributed to the implementations of Router-Preference, ISATAP, DHCPv6 address distribution, etc. In addition to these implementation activities, I also performed many activities to deploy IPv6. The details of these activities are: IPv6-related merging work for FreeBSD, obtaining IPv6-Ready Logo, various educational activities for IPv6-related matters, etc.
What I gained from working in the KAME project
What I felt the most throughout the KAME development process was that it is important to keep a record of the design philosophy. This is because, after a while, you can’t work on code that doesn’t explain its design philosophy, even though people tend to say that “the code explains everything” in this kind of open source development. (Since old BSD code was like that more often than you might think, TCP/IP Illustrated Vol.2 was really like a bible to us.) There were also various things that I gained from the KAME project other than from the development activities themselves. The biggest thing, I think, is that “through the KAME project’s IPv6-related activities, I made a lot of companions in the Internet community”.
Professional activities I would like to work on (not related to the KAME project) in the future
Even though the IPv6 protocol/implementation has matured more than enough, it hasn’t been propagated enough in the real world. Because of that, I would like to play an active part in filling the gap, which also means, to return the KAME project’s outcomes to society. Multicast had a similar problem, but now it is finally about to start propagating in Japan with the upsurge of IP support in terrestrial digital broadcasting. I have been working on the implementation of multicasting protocols up until now. So, in addition, I would like to contribute to the research and development of multicast technologies that can actually be put to use.
 |
Name: Keiichi SHIMA |
The role I played in the KAME project
I was in charge of the IPv6 mobility implementation for the KAME project. The biggest outcome was That I implemented an original mobility stack and distributed it through the KAME project. Particularly in regards to the Mobile IPv6 implementation, I was able to greatly contribute to the KAME project’s principle of always providing cutting-edge technology by promptly keeping pace with the frequently changing specification. Currently, the KAME mobility stack is in fact the only available implementation for BSD systems. I feel proud that I was able to contribute to the entire filed by providing the IETF’s cutting-edge mobility environment to many researchers and developers.
What I gained from working in the KAME project
Many of Japan’s leading programmers gathered for the KAME project. Joining the group, exchanging opinions, and examining each other’s code helped me improve my skills and senses as a programmer, and the time I spent in the project became valuable to me. At the same time, If there was no KAME Project activities, I could'nt take part in standardization efforts at the IETF and not to have intense debates with people involved with IPv6 both inside, and outside, of the country. I would like to express my deepest appreciation to everyone involved for giving me these opportunities.
Professional activities I would like to work on (not related to the KAME project) in the future
I have been working on IPv6 mobility through KAME project activities, but I feel we still need to make more effort to deploy the technology.. I believe that, in the future, the significant advancement of computers and communication technology will create a world where so many computers, more that we can imagine, are connected by various communication technologies. With regards to IPv6 mobility, we have finished standardizing the core specifications, and it is now at the phase where more advanced specifications are standardized and, at the same time, where real-world applications of the technology are considered. In any case, wanting to follow how far IPv6 mobility will be developed is a strong passion for me.
 |
Name: Tsuyoshi MOMOSE |
The role I played in the KAME project
Before I joined the KAME project, I was implementing another KAME-based Mobile IPv6 at the company. Making use of that experience, I’ve worked consistently on Mobile IPv6 development since I started working at the KAME Project. I am proud that this Mobile IPv6 stack showed the existence of the KAME Mobile IPv6 through various interoperability testing events and such, and played a role as a reference implementation just as was the case with the IPv6 core part.
What I gained from working in the KAME project
The KAME Project is a group of extremely talented engineers. Since I realized this even when I was not a part of the project, there were times that I felt a little daunted, worrying whether I would be able to work among them, when I was asked to join the project. However, I think that making the acquaintance of these talented people and being able to participate in meaningful debates were more worthwhile experiences than anything else. Also, the credibility of the KAME brand, which was established by the forefathers who have been working on it since the first term of the KAME project, was very high. So, I was able to have debates and mingle with participants at the IETF and interoperability testing events. That experience was very meaningful and valuable to me.
Professional activities I would like to work on (not related to the KAME project) in the future
The implementations of the current KAME Mobile IPv6/NEMO of the basic specifications are mostly completed. So, if I will be able to contribute to the growth of IPv6 and mobility technology through my work at the office, making use of my experiences at the KAME project and my accumulated skills, that would be a great pleasure beyond my wildest dreams. Also, it would be really great if I can let my juniors at the office know about the exchanges I had with talented people outside of my office; at the same time, it would be also great if I can help them to have similar experiences.
Name: Yoshinobu INOUE
Employer at time of joining the KAME Project: Fujitsu Limited
Current employer: Same as above
The role I played in the KAME project
After working on IPv6-readiness for PPP and Mozilla, Prefix Renumbering, etc., I worked on importing the outcomes of the KAME project into FreeBSD4.0 as my final task. I think that was the biggest contribution I made to the Project.
What I gained from working in the KAME project
What was a big deal to me was that, with the adoption of a new protocol, IPv6, I was given an opportunity to take another good look at the entire design of the Internet architecture. During that process, I was able to receive valuable stimulation and influence that I couldn’t get anywhere else by debating and working together with many first-class developers. Also, FreeBSD was, and still is even now, the most comfortable environment to me. So, I think being able to join the FreeBSD development community and work in it was an exceptionally valuable experience.
Professional activities I would like to work on (not related to the KAME project) in the future
The immediate pressing issue for the Internet is to improve the reliability of its backbone and I am concentrating on that, too. This is because other services are dependent on it to continue working. The real issue in the future is that we need to establish a platform that lets everyone in the world, including people who cannot use computers at all, easily access the information on the Internet, and easily and securely communicate with each other. I would like to take part in this sort of work.
Name: Shin’ichi FUJISAWA
Employer at time of joining the KAME project: Yokogawa Electric Corporation
Current employer: Same as above
The role I played in the KAME project
I was part of the KAME project from April 1998 to March 2002. During that time, I implemented NAT-PT for FreeBSD. After leaving the KAME project, I participated in the development of NAT-PT as a commercial product. Right now, I can’t work on KAME NAT-PT because of my work. However, though I doubt it was much, I think that I was able to contribute to the propagation of v6 through KAME and the work I did afterwards.
What I gained from working in the KAME project
I clearly saw what great things could be done when you break down the walls between companies and gather talented engineers. People who have far greater talent than I have were gathering under one roof. Among them, I felt powerless; at the same time, I really realized that I could do it if I tried hard. I would like to thank those who gave me the opportunity to participate in such a project.
Professional activities I would like to work on (not related to the KAME project) in the future
It is also related to my work, but I’m interested in wireless and built-in stuff. I’ve been wondering if we can make a good use of v6 in a situation where wireless devices are connected to each other using a small device. For a small device that needs to conserve power, that big v6 address becomes a major burden. However, on the other hand, I think we can create a device that is only possible using v6 (for example, something that you can use right after you take it out of the box).
 |
Name: Shuichi KARINO |
The role I played in the KAME project
I participated in the project from 2000 to 2002 as a core member and mainly worked on Mobile IPv6 implementation. Although the code I implemented didn’t stay in the end, by providing one of the first KAME Mobile IPv6 implementations, I think I was able to contribute to its further development.
What I gained from working in the KAME project
Not only did working together with top-class TCP/IP implementers enrich my insights, but I was also able to learn quite a bit as an engineer on things like how to deal with technology and I was able to grow as a result. On the other hand, I became keenly aware of the difficulties of standardization. It’s not just about creating a good specs or implementations. Unless you get agreement from other vendors and organizations, the specs and implementations won’t be adopted as a standard. I felt that the ability to negotiate when communicating with other vendors and getting their agreement is a necessity in a consortium, even if you join it as an engineer.
Professional activities I would like to work on (not related to the KAME project) in the future
I am currently working on the technology for improving availability and virtualization of IP nodes. Using my experience at the KAME project, I would like to continuously work on developing technology for network software.
 |
Name: Munechika SUMIKAWA |
The role I played in the KAME project
I started out working on kernel-related development, but I came to think that propagation of applications is important for the growth of IPv6. So, I focused on increasing the number of IPv6 applications. I modified code of well-known applications so that they run on IPv6, and sent the patches back to the authors, asking them to apply them. I made it so that when KAME is merged into FreeBSD 4.0-Release, a virtual category called IPv6 is created and many IPv6-ready ports are created. So, users can enjoy IPv6 without difficulty. I am proud that I expanded the horizon of IPv6 users by making it easy to adopt it. It’s already been 6 years since I left the KAME “core” group, but I’m continuously working on ports maintenance for FreeBSD.
What I gained from working in the KAME project
I became involved with Hydrangea, the predecessor to KAME, when I was in school. I also worked as a member of the KAME project after I started working. KAME played a central role in the IPv6 world and it means the world to me in terms of my career. Also, not only do I use IPv6 as a key technology, but my employer, ALAXALA Networks, does as well. Our company has become highly regarded internationally due to its collaboration with the KAME project.
Professional activities I would like to work on (not related to the KAME project) in the future
One night, in the middle of the night, Mr. SAKANE and I got excited when we were talking about trying to broadcast mp3, like over radio, using IPv6 multicasting. I still remember spending all night throwing together some code like crazy. I would like to continue this practice of working right away on the implementation of a spur-of-the-moment idea and also its trial in my research and development for products.
 |
Name: Hideki ONO |
The role I played in the KAME project
I participated in the KAME project as a “core” member for a little less than 2 years, and worked on implementations of VRRP and DCCP. My primary contribution was providing code. VRRP was not released for some reasons, but it meant a lot to me in terms of my later activities. Also, DCCP is a protocol that is expected to grow in the future and I contributed code for its basic part.
What I gained from working in the KAME project
I joined in the middle of the project, and I really realized that many members were performing KAME activities with conviction. Since they are in fact successful in various places, I learned the importance of having conviction when doing things. It was really a great experience to me that I was able to participate in a project where such first-class engineers are gathered and that I was able to have such great debates.
Professional activities I would like to work on (not related to the KAME project) in the future
As a freelance engineer whose expertise is in network software, I would like to work on various networks, to say nothing of IPv6. At the same time, I also want to explore and develop some new technologies around the networks.