Top > JANOG24 Programs

JANOG24 general information

  • Who is hosting?
  • When?
    • 9th & 10th July 2009
  • Where?
    • This meeting will take place in Otemachi, Chiyoda-ku, Tokyo.
    • The General meeting will be held at "Nikkei Hall" in new Nikkei headquarter building.
      • Address : 1 chome, Chiyoda-ku, Tokyo, Japan
      • Map
    • Reception Party: TBD
  • How much?
    • Participation fees:
      • Meeting: free!
      • Party: around 6,000yen
  • How to get there?
    • From Narita Airport: please check here. We recommend the Narita Express
    • Once in Central Tokyo there are several choices
  • Hotel info
    • Please arrange your own lodging. The KKR and the Green Hotel Ochanmizu are somewhat convenient inexpensive hotels. Reserving at the KKR is only in Japanese.
  • Other info
    • Laptop power and connectivity
      • Usually provided outside the conference room near the refreshments.
      • Don't expect to get any inside the conference room.
      • Do not expect mains power in the meeting room.
      • You can rent mobile phones and wireless internet gadgets at Narita Airport before the trains.

JANOG24 Registration

Registration capacity

  • Plenary session: 450 people
  • Social event: 150 people
  • Newcomers' Orientation: 450 people

The registration deadline is Friday, June 6, 2009 17:00 (JST,GMT+9) or until fully booked, whichever is earlier. I.e. book early!


  • Sessions and orientation: Free
  • Social dinner : 6,000 Yen
    • JP residents: wire transfer
    • Overseas: on-site

Want to register?

The registration page is in Japanese only. So if you are interested in coming, please contact secretariat[at-mark]

Time table

Day1 - Thursday, July 9, 2009

JANOG update
11:00Mis-operationsYoshinobu 'maz' Matsuzaki (IIJ)
12:00[Lightning Talk]
12:15Lunch Break
13:45Are you ready to operate DNSSEC-enabled DNS environment?Masato Minda(JPRS)
15:00Tools - A Better Network Operation Experience -Seiichi Kawamura (NEC Biglobe, Ltd.)
15:30An index of IPv6 deployment - an investigation of communication quality and the diffusion rateYoshiaki Kitaguchi (Intec NetCore), Nobuaki Nasu(Intec NetCore)
16:00[Lightning Talk]
Let's play with BGP4 - Introduction to IHANetGenta Iha (Teeda Networks)
Let's talk about monitoring and operations - Monitoring framework and Research on Operation MethologyYuuichi Hatano (Japan Unix Society)
16:40Confronting the IPv4 address exhaustion - What content providers should do? -Katsuyasu TOYAMA (Internet Multifeed, Co.)
Hiroyuki ICHIKI (Nikkei, Inc.)
Tetsushi KOYAMA (Techstyle, Co. Ltd.)
Yosuke IIJIMA (Internet Multifeed, Co.)

Day2 - Friday, July 8, 2009

10:00Deeply inspecting DPI technologyKazuyuki Shudo (Tokyo Institute of Technology)
Yaniv Sulkes (Allot Communications)
Wataru Ono (Mitsubishi Corporation)
Taira Kato (Cisco Systems)
11:15Are you taking actions to deploy IPv6 in your intranet? - Trends of IPv6 deployment for enterprise network and related problemsKousuke Shishikura (NTT Communications)
Kenji Arai (NTT Communications)
12:00Introduction of INOC-DBAGaurab Raj Upadhaya(PCH)
Jonny Martin(PCH)
12:15Lunch Break
13:45What's up with world-wide topics about IPv4/IPv6 coexistence network models?Masataka Mawatari (JPIX)
Akira Nakagawa (KDDI)
Randy Bush (IIJ)
Alain Durand (Comcast)
15:30Careful planning is needed for introducing NATHiroyuki Ashida (ITSCOM)
Introduction of next JANOG




Yoshinobu 'maz' Matsuzaki (IIJ)


Misses are always around operations. In some cases operators just break out in a cold sweat, but other cases misses result in big outages.

To reduces mis-operations, every operator develops various fail-safe systems, trains the staff, and builds special functions. Nevertheless, we can not completely eliminate misses. Some operators get discouraged with additional barren procedures to prevent misses.

In this session, we talk about mis-operations, share failure cases, lessons learned and countermeasures for various operators.

Are you ready to operate DNSSEC-enabled DNS environment?


  • Masato Minda (Japan Registry Services Co., Ltd.(JPRS))


Dan Kaminsky disclosed the DNS vulnerability, Verisign has promised to deploy DNSSEC, and some TLDs have already signed their zones with DNSSEC. It is only a matter of time before DNSSEC is enabled in your DNS environment.

This session will provide you an overview of DNSSEC, share the current status of DNSSEC, and discuss how DNSSEC has an impact on DNS operations on both authoritative servers and cache servers to prepare for coming DNSSEC-enabled DNS environment.

Tools - A Better Network Operation Experience -


Seiichi Kawamura (NEC Biglobe, Ltd.)


Network operations seem to becoming more complex then ever (i.e. dual stack, 4byte-AS, RPKI, etc). Tools will help provide for a fast, accurate, optimized operator experience. Also, as technology evolves, network operation tools must also evolve with them. There seems to be a lot of network tool sites and portals overseas. NANOG has a page for tools on their web site. However, we do not see much of these in Japan. We will discuss how and what kind of tools can be used in network operations, and discuss how we can share knowledge and information about them.

An index of IPv6 deployment - an investigation of communication quality and the diffusion rate


  • Yoshiaki Kitaguchi (Intec NetCore)
  • Nobuaki Nasu(Intec NetCore)


While IPv4 address exhaustion is coming soon, a network company who has the interest in IPv6 introduction increases, but we think the situation that you worry about what kind of timing you should work on IPv6. So we think the communication quality and the diffusion rate is important as an index of IPv6 introduction, and estimate the current state of IPv6 internet based on various measuring result.

The communication quality compared with IPv4 will be reported by this presentation if the first half and the value of IPv6 diffusion rate in the user/network/each segment of service will be reported in the second half. Further, it's the one which includes the measuring result which was obtained by "IPv4/IPv6 meter" introduced in JANOG23 in this measurement.

We'd like to hear an opinion from a person in the meeting place about the evaluation method put into effect to grasp the current state of the information which is needed when the IPv6 start is made.

Confronting the IPv4 address exhaustion - What content providers should do? -


  • Katsuyasu TOYAMA (Internet Multifeed, Co.)
  • Hiroyuki ICHIKI (Nikkei, Inc.)
  • Tetsushi KOYAMA (Techstyle, Co. Ltd.)
  • Yosuke IIJIMA (Internet Multifeed, Co.)


Sooner or later due to IPv4 address depletion content providers will be forced to deploy IPv6. A lot of content providers make full use of new technologies to develop sophisticated content in order to attract users. Content provider developers on the other hand usually do not have sufficient expertise in IPv4 and IPv6. This program will discuss what content providers should do to plan for the deployment of IPv6, analysing possible risks that IPv4 address depletion will bring.

This program will seek the direction for content providers in the future among the panel and people on the floor, from content providers, content development and the server administration fields.

The session will include discussions on the following;

Deeply inspecting DPI technology


  • Kazuyuki Shudo (Tokyo Institute of Technology)
  • Yaniv Sulkes (Allot Communications)
  • Wataru Ono (Mitsubishi Corporation)
  • Taira Kato (Cisco Systems)


DPI(Deep Packet Inspection) technology is not a technology only to detect and shape traffic, on which some might have unfavorable impression. DPI technology is playing a key role in traffic monitoring, detecting denial of service attack and protection against it, UTM (Unified Threat Management), policy server and many other applications, and being utilized in many networks in various sizes from small to large scale. This session will "DEEPLY" discuss the future outlook of DPI technology.

Are you taking actions to deploy IPv6 in your intranet? - Trends of IPv6 deployment for enterprise network and related problems


  • Kousuke Shishikura (NTT Communications)
  • Kenji Arai (NTT Communications)


We can find many discussions about how to deploy IPv6 for production networks of xSP and iDC players.

As you know, IPv4 addresses will run out in a few years. On the other hand generally speaking, IT people in charge of corporate Intranets should be discussing plans for their network a few years in advance. Some cutting-edge network operators my just be beginning to think about deploying IPv6 for their own Intranet at this stage. Some SIers and NIers may be getting inquiries about IPv6 deployment for such Intranets now.

We would like to share case studies of IPv6 deployment for Intranets and related problems, and to have discussions on these items.

Introduction of INOC-DBA


  • Gaurab Raj Upadhaya(PCH)
  • Jonny Martin (PCH)


INOC DBA stands for 'Inter NOC dial by ASN'. It's been in use since late 2002 to connect NOCs of ISPs, CERTS, SIRTs and other organizations on the Internet. It uses SIP for signalling and AS Numbers for dial-plan. This presentation will provide a brief overview.

What's up with world-wide topics about IPv4/IPv6 coexistence network models?


  • Masataka Mawatari (JPIX)
  • Akira Nakagawa (KDDI)
  • Randy Bush (IIJ)
  • Alain Durand (Comcast)


IPv4/IPv6 coexistence and transition network models are still being discussed at IETF, APRICOT, NANOG etc..., and that's going to continue.

What else can prepare Network Engineers for when IPv4 global address depletion occurs? What kind of solutions, ideas and suggestions are being discussedamong world wide engineers? We want to have a discussion at the JANOG 24 meeting with network operators in mind, not researchers.

In this program, I will explain 4 network models (A+P, Dual Stack Lite, NAT444-LSN, NAT-PT), and I would like to clarify some questions and issues.

Careful planning is needed for introducing NAT


  • Hiroyuki Ashida (ITSCOM)


At Janog22 the technologies and implications of introducing NAT into an ISP/SP infrastructure was raised and discussed. Now an organised planing effort for LSN(*) deployment is required to cope with IPv4 address depletion. Also it should be noted that LSNs need to be deployed *before* IPv4 depletion occurs, because it requires global IPv4 addresses.

In this environment, I will evaluate how many resources would be required for actual LSNs and their ancillary facilities through a quantitative analysis of some of the elements such as port number restrictions and logging issues.

  • Prediction of required number of addresses and ports, through actual traffic flows.
  • Difference of capacity by design policy.
  • Volume of information in the logs and the required storage.
  • Timing to deploy.

In addition, I'd like to address the following topics.

  • Issues regarding the location of LSNs and the routing
  • Impacts for operation and usage after NAT deployment
    • access control
    • application restriction
  • Address space to be used internally and externally
    • consideration for assigning addresses to subscribers

Further, I'd like to discuss LSN deployments in ISPs and get feedback from a users point of view.

(*) LSN: Large Scale NAT, previously called as CGN (Carrier-Grade NAT).

[Points I'd like to focus in this session]

  • Address and Port translation technologies for sharing IPv4 address space. (This time, I focus on 4to4 NAPT, which is an off-the-shelf technology and does not require additional cost for end users, but required resources would be common among other technologies which share IPv4 address space.)
  • Concrete technical discussion for deploying LSN.

[Points I won't focus in this session]

  • Denial of the supposed architecture, i.e. IPv4 address sharing by using NAT
  • NAT taxonomy, NAT traversal technologies (already discussed in Janog22)

  • Presentation (Japanese)

Reload   New Lower page making Edit Freeze Diff Upload Copy Rename   Front page List of pages Search Recent changes Backup Referer     RSS of recent changes
Last-modified: (2487d)