This is 2000 annual report of ITJIT-NET IPv6 activity.
This report was made by Takahiro Yugawa(yugawa@as4682.spin.ad.jp) on 2001/1/5.

Network name

ITJIT-NET

History

before 2000
assigned pTLA address 3ffe:504:200::/48 from IRI and connected to IRI via IPv6 over IPv4 tunnel. routing protocol was RIPng(KAME route6d)
2000/1
assignd sNLA1 from WIDE.
- address: 2001:200:200::/40
- connection: IPv6 over IPv4 tunnel
- routing: BGP4+(zebra)
2000/1
Renumberd edge nodes(/64 network) to newly assigned sNLA1 address.
2000/1
assigned two external parties.
- ichiro.org:2001:200:202::/48, tunnel, BGP4+
- cyber-fleet:2001:200:203::/48, tunnel, BGP4+
2000/1
connected to IMASY via tunnel, no address assign, BGP4+ private peer.
2000/2
assigned one external party.
- TokyoNet.GR.JP:2001:200:204::/48, tunnel, RIPng
2000/9
connected to JENS IPv6 network. assignd 2001:228:c00::/48. tunnel, BGP4+
applications
- DNS: bind8 + KAME patch
- HTTP: apache + KAME patch
- FTP: wu-ftpd + KAME patch
  ftp.itjit.ne.jp is available for anonymous ftp.
- SMTP: sendmail + KAME patch
- SSH: ssh + KAME patch

Network topology

            WIDE       JENS                    (upstreams)
              |          |
              |          |
              +---+ +----+
                  | |
                  | |
               ITJIT-NET-------IMASY           (peer)
                 | | |
                 | | |
   +-------------+ | +------------+
   |               |              |
   |               |              |
ichiro.org    cyber-fleet    TokyoNet.GR.JP    (downstreams)

Routing Protocol

for upstreams & peer, we use BGP4+.
for downstreams, we use both BGP4+ and RIPng according to the user's request.
for IGP we use RIPng.

Address assingment

We currently assign /48 address window, because it is a WIDE rule.

2001:200:200::/48 ITJIT-NET internal use
2001:200:202::/48 ichiro.org
2001:200:203::/48 cyber-fleet
2001:200:204::/48 TokyoNet.GR.JP

Troubles

We have experienced some routing troubles. They are categorized as follows.

bug issue of KAME or Zebra.
troubleshooted by reporting/quickhack/version up.
configuration issue
troubleshooted by correcting configuration.