pTLA request for CNIT - review closes 24 December 2001

Bob Fink fink@es.net
Mon, 10 Dec 2001 20:43:34 -0800


6bone Folk,

CNIT has requested a pTLA allocation. The open review period for this will 
close 24 December 2001. Please send your comments to me or the list.

<http://whois.6bone.net/cgi-bin/whois?cnit>


Thanks,

Bob

===
>Date: Mon, 10 Dec 2001 17:27:50 +0100
>From: Gianluca Mazzini <g.mazzini@ieee.org>
>To: Bob Fink <fink@es.net>
>Cc: ipv6@cnit.it
>Subject: pTLA request
>
>Dear Bob,
>
>by following the suggestion you give me the last week, I have work a
>lot around the submission of a IPv6 space request with a /24 or /28
>for the CNIT. In the following you can find our request that I hope
>you will process.
>
>Best Regards
>
>Gianluca Mazzini
>
>7. Guidelines for 6Bone pTLA sites
>
>   The following rules apply to qualify for a 6Bone pTLA allocation. It
>   should be recognized that holders of 6Bone pTLA allocations are
>   expected to provide production quality backbone network services for
>   the 6Bone.
>
>   1. The pTLA Applicant must have a minimum of three (3) months
>      qualifying experience as a 6Bone end-site or pNLA transit.   During
>      the entire qualifying period the Applicant must be operationally
>      providing the following:
>
>
>The applicance is for CNIT. This acronymous is for National Consortium
>Inter-University for telecommunications. This consortium links a large
>number of italian universities involved in projects, developments and
>researches in the telecommunications field. The web site of the
>consortium is www.cnit.it, where a lot of information about the
>consortium and its parters are hosted.
>
>Since the beginning of 2001 the consortium has developed a proprietary
>network based on ATM, HDSL, Frame relay and Satellite links with more
>than 20 site connected. CNIT is an autonous system on IPv4 (AS20754)
>with allocation 217.9.64.0/20.
>
>In parallel, University of Ferrara (UNIFE), a CNIT member has
>performed a lot of activities on IPv6 since 1997, working on proxy
>IPv6/v4 developing, multicast streaming (with CSELT now TILAB) and
>redundant routing (European project www.depaude.org). CNIT has
>recently ask to UNIFE some helps to create a native IPv6 network with
>the aim of using it both in all the local site and in the geographic
>connection. Where the native IPv6 is not supported, tunnelling has
>been used.
>
>Actually the system is running with some /48 given by public tunnel
>broker service but the potentially high number of users (researchers
>and students), the large dimension of the network and the planned
>developing and research activities need to migrate to a /24 or /28.
>
>      a. Fully maintained, up to date, 6Bone Registry entries for their
>         ipv6-site inet6num, mntner, and person objects, including each
>         tunnel that the Applicant has.
>
>This point is satisfied as you can check searching for CNIT on the
>6BONE database.
>
>
>ipv6-site:    CNIT
>origin:       AS20745
>descr:        Consorzio Nazionale Interuniversitario per le Telecomunicazioni
>country:      IT
>prefix:       3FFE:8171:49::/48
>tunnel:       IPv6 in IPv4 gw-cnit-fe-na.cnit.it -> 6bone-gw1.edisontel.it 
>EDISONTEL BGP4+
>tunnel:       IPv6 in IPv4 gw-cnit-fe-na.cnit.it -> 
>100tx-f1-0.c7206.ipv6.he.net HE BGP4+
>tunnel:       IPv6 in IPv4 gw-cnit-fe-na.cnit.it -> 
>6bone-gw3.ipv6.cselt.it TILAB BGP4+
>contact:      GM1-6BONE
>contact:      SZ-6BONE
>contact:      SV-6BONE
>mnt-by:       UNIFE-MNT
>changed:      g.mazzini@ieee.org 20010731
>changed:      g.mazzini@ieee.org 20011206
>changed:      g.mazzini@ieee.org 20011207
>source:       6BONE
>
>inet6num:     3FFE:8171:49::/48
>netname:      CNIT
>descr:        Consorzio Nazionale Interuniversitario per le Telecomunicazioni
>country:      IT
>admin-c:      GM1-6BONE
>tech-c:       SZ-6BONE
>tech-c:       SV-6BONE
>mnt-by:       UNIFE-MNT
>changed:      g.mazzini@ieee.org 20010731
>changed:      g.mazzini@ieee.org 20011206
>changed:      g.mazzini@ieee.org 20011210
>source:       6BONE
>
>person:       Gianluca Mazzini
>address:      University of Ferarra
>address:      Via Saragat 1
>address:      44100 Ferrara
>address:      Italy
>phone:        +39 335 8160916
>fax-no:       +39 0532 768602
>e-mail:       g.mazzini@ieee.org
>nic-hdl:      GM1-6BONE
>notify:       g.mazzini@ieee.org
>mnt-by:       UNIFE-MNT
>changed:      g.mazzini@ieee.org 20010731
>source:       6BONE
>
>person:       Sandro Zappatore
>address:      Consorzio Nazionale Interuniversitario per le Telecomunicazioni
>address:      Via Diocleziano 328
>address:      I- 80125 Napoli NA
>address:      Italy
>phone:        +39 081 2303311
>fax-no:       +39 081 2303311
>e-mail:       sandro.zappatore@cnit.it
>nic-hdl:      SZ-6BONE
>mnt-by:       UNIFE-MNT
>changed:      g.mazzini@ieee.org 20010731
>source:       6BONE
>
>person:       Stefano Vignola
>address:      Consorzio Nazionale Interuniversitario per le Telecomunicazioni
>address:      Via Diocleziano 328
>address:      I- 80125 Napoli NA
>address:      Italy
>phone:        +39 081 2303311
>fax-no:       +39 081 2303311
>e-mail:       stefano.vignola@cnit.it
>nic-hdl:      SV-6BONE
>mnt-by:       UNIFE-MNT
>changed:      g.mazzini@ieee.org 20010731
>source:       6BONE
>
>      b. Fully maintained, and reliable, BGP4+ peering and connectivity
>         between the Applicant's boundary router and the appropriate
>         connection point into the 6Bone. This router must be IPv6
>         pingable. This criteria is judged by members of the 6Bone
>         Operations Group at the time of the Applicant's pTLA request.
>
>Three differents connection between our autonomous system and the
>6bone is active with BGP4+. Our router has IPv4 217.9.66.10, it is
>pingable (also in ipv6 to 3FFE:8171:49::1, 3FFE:1200:3028:8116::1,
>3FFE:1001:580::1) and the tunnels are
>
>tunnel:       IPv6 in IPv4 gw-cnit-fe-na.cnit.it -> 6bone-gw1.edisontel.it 
>EDISONTEL BGP4+
>tunnel:       IPv6 in IPv4 gw-cnit-fe-na.cnit.it -> 
>100tx-f1-0.c7206.ipv6.he.net HE BGP4+
>tunnel:       IPv6 in IPv4 gw-cnit-fe-na.cnit.it -> 
>6bone-gw3.ipv6.cselt.it TILAB BGP4+
>
>Furthermore, our main IPv6 router, a CISCO with IOS 12.2, give the
>following output for the bgp
>
>BGP router identifier 217.9.66.10, local AS number 20745
>BGP table version is 956, main routing table version 956
>301 network entries and 706 paths using 86837 bytes of memory
>503 BGP path attribute entries using 30180 bytes of memory
>483 BGP AS-PATH entries using 13292 bytes of memory
>956 BGP route-map cache entries using 15296 bytes of memory
>0 BGP filter-list cache entries using 0 bytes of memory
>BGP activity 1447/5859 prefixes, 4548/3842 paths, scan interval 15 secs
>
>Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down
>State/PfxRcd
>2001:750:E::C   4 15589    6480   12175      956    0    0 05:11:09      190
>3FFE:1001:1:F022::1
>                4  5609    7377    6794      956    0    0 05:20:01      280
>3FFE:1200:3028:FF01::4B04
>                4  6939   12990    6164      956    0    0 05:19:23      233
>
>
>      c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>         entries for the Applicant's router(s) and at least one host
>         system.
>
>An AAAA on cnit.it domain is available on the subdomain
>ipv6.cnit.it. The actual dns are 217.9.64.3 and 192.167.215.104. This
>works also for the reverse lookup for the network 3FFE:8171:49::/48 we
>actually use. The dns is pingable and accessible but it is forbitten
>to obtain the host list for security and privacy reason. The following
>list of IPv6 host is actually registered and running but we are
>strongly working to expand them.
>
>fs              IN AAAA         3ffe:8171:0049:0002:201:2ff:fe94:df20
>dns             IN AAAA         3ffe:8171:0049:0002:201:2ff:fe94:df49
>tlc1            IN AAAA         3ffe:8171:0049:0002:2c0:26ff:fe10:8d08
>tlc2            IN AAAA         3ffe:8171:0049:0002:201:2ff:fe94:df09
>tlc3            IN AAAA         3ffe:8171:0049:0002:201:2ff:fe94:df22
>tlc8            IN AAAA         3ffe:8171:0049:0002:201:2ff:fe94:df34
>tlc9            IN AAAA         3ffe:8171:0049:0002:201:2ff:fe94:df19
>tlc10           IN AAAA         3ffe:8171:0049:0002:201:2ff:fe94:df21
>tlc11           IN AAAA         3ffe:8171:0049:0002:201:2ff:fe94:df32
>tlc12           IN AAAA         3ffe:8171:0049:0002:201:2ff:fe94:df12
>tlc13           IN AAAA         3ffe:8171:0049:0002:201:2ff:fef2:d147
>tlc14           IN AAAA         3ffe:8171:0049:0002:201:2ff:fe94:df15
>tlc20           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:3620
>tlc21           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:45e5
>tlc23           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:45e0
>tlc25           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:3893
>tlc26           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:3618
>tlc27           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:3619
>tlc28           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:3892
>tlc29           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:3894
>tlc30           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:45cc
>tlc32           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:460f
>tlc33           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:45ea
>tlc34           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:3617
>tlc36           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:3616
>tlc38           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:4628
>tlc39           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:45f2
>tlc40           IN AAAA         3ffe:8171:0049:0002:2e0:18ff:fe21:3621
>
>
>      d. A fully maintained, and reliable, IPv6-accessible system
>         providing, at a mimimum, one or more web pages, describing the
>         Applicant's IPv6 services.  This server must be IPv6 pingable.
>
>A web site at the address www.ipv6.cnit.it is available and
>pingable. It is working in IPv6 only. The server actually does not
>offer any service but it declare the service that we will implement
>soon.
>
>   2. The pTLA Applicant MUST have the ability and intent to provide
>      "production-quality" 6Bone backbone service. Applicants must
>      provide a statement and information in support of this claim.
>      This MUST include the following:
>
>      a. A support staff of two persons minimum, three preferable, with
>         person attributes registered for each in the ipv6-site object
>         for the pTLA applicant.
>
>As you can see from the previous reported list 3 persons is registered
>for the CNIT IPv6 management, their name are Sandro Zappatore, Stefano
>Vignola and Gianluca Mazzini.
>
>      b. A common mailbox for support contact purposes that all support
>         staff have acess to, pointed to with a notify attribute in the
>         ipv6-site object for the pTLA Applicant.
>
>A common mailbox with address ipv6@cnit.it has been created for
>technical contact and it is internally accessible by all the technical
>person involved in the IPv6 management.
>
>   3. The pTLA Applicant MUST have a potential "user community" that
>      would be served by its becoming a pTLA, e.g., the Applicant is a
>      major provider of Internet service in a region, country, or focus
>      of interest. Applicant must provide a statement and information in
>      support this claim.
>
>As underlined in the 7.1 topic, the CNIT as broad consortium of
>italian University cover the whole country and it will give access to
>a potentially huge number of student, researcher and people. A lot of
>projects in which CNIT is involved require network extension to final
>users and to other company. Furthermore, the number of university
>directly linked with CNIT growth every mounth with a very interesting
>trend. The basic persons in the CNIT permanent staff is about 300 and
>the number of students directly managed, and potentially involved in
>the IPV6 use, are around a million.
>
>
>   4. The pTLA Applicant MUST commit to abide by the current 6Bone
>      operational rules and policies as they exist at time of its
>      application, and agree to abide by future 6Bone backbone
>      operational rules and policies as they evolve by consensus of the
>      6Bone backbone and user community.
>
>We agree with the actual policy and we will accept any future
>decisions the 6bone will take, by operating as a consequence of these
>actions.
>
>   When an Applicant seeks to receive a pTLA allocation, it will apply
>   to the 6Bone Operations Group (see section 8 below) by providing to
>   the Group information in support of its claims that it meets the
>   criteria above.
>
>All the people involved in this request are directly interested on the
>IPv6 and they are subscripted to the mailing list before the beginning
>of this project.
>
>8. 6Bone Operations Group
>
>   The 6Bone Operations Group is the group in charge of monitoring and
>   policing adherence to the current rules. Membership in the 6Bone
>   Operations Group is mandatory for, and restricted to, sites connected
>   to the 6Bone.
>
>   The 6Bone Operations Group is currently defined by those members of
>   the existing 6Bone mailing list who represent sites participating in
>   the 6Bone. Therefore it is incumbent on relevant site contacts to
>   join the 6Bone mailing list. Instructions on how to join the list are
>   maintained on the 6Bone web site at < http://www.6bone.net>.
>
>In am registered in the 6BONE mailing list since a lot of years ago.