pTLA request SSVL - review closes 3 May 2002

Bob Fink fink@es.net
Fri, 19 Apr 2002 09:36:59 -0700
Previous message: A DNS question re 6to6/IPv6 host IN A records.
Next message: pTLA request SSVL - review closes 3 May 2002
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
6bone Folk,

SSVL has requested a pTLA allocation and I find their request fully 
compliant with RFC2772. The open review period for this will close 3 May 
2002. Please send your comments to me or the list.

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

<http://www-v6.ssvl.kth.se>


Thanks,

Bob
===
>Date: Fri, 19 Apr 2002 14:51:28 +0200
>From: Bjorn Pehrson <bjorn@it.kth.se>
>User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.3) 
>Gecko/20010801
>To: Bob Fink <fink@es.net>
>CC: "Americo F. Muchanga" <americo@it.kth.se>,
>         Fredrik Lilieblad
>         <fli@it.kth.se>,
>         Jonas Willén <jwi@it.kth.se>,
>         Martin
>         Hedenfalk <mhe@home.se>
>Subject: pTLA application
>
>Bob,
>Enclosed, please find an application for a 6Bone pTLA allocation from SSVL.
>
>Sincerely
>
>Björn Pehrson
>SSVL admin-c
>(bp2-6bone)
>----------------------------
> > 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:
> >
> > 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.
>
>Our ipv6 site SSVL (AS8973) is registered with RIPE and the 6bone registry 
>since 1999-06-05. We are currently connected to the following pTLAs
>- SICS (peering via BGP4+)
>- FreeNet (static route)
>When upgraded to pTLA, we will continue peering with these pTLAs and add a 
>few more, including Sunet, the Swedish academic netwok provider.
>
> > 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.
>
>Our BGP4+ is stable running on our Cisco 7513 router at
>kth-gateway-loopback0.ssvl.kth.se 3ffe:200:15:6::1
>
> > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
> > entries for the Applicant's router(s) and at least one host
> > system.
>
>We have AAAA and ipv6.int for all our ipv6 hosts and networks at 
>ns.ssvl.kth.se. Another host is the webserver www-v6.ssvl.kth.se
>
> >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.
>
>www-v6.ssvl.kth.se  3ffe:200:15:5::1
>
> >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.
>
>Statement: We hereby claim that we have the ability and intent to
>provide production quality 6Bone backbone service.
>
> >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.
>
>The following persons are listed under MNT-SSVL
>- Fredrik Lilieblad <fli@it.kth.se>
>- Björn Pehrson <bjorn@it.kth.se>
>- Jonas Willén <jwi@it.kth.se>
>
> >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.
>
>The mailinglist noc@ssvl.kth.se includes
>- Fredrik Lilieblad <fli@it.kth.se>
>- Björn Pehrson <bjorn@it.kth.se>
>- Jonas Willén <jwi@it.kth.se>
>
> >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.
>
>KTH is a leading academic research organization in the Internetworking 
>area conducting long term research on the next generation networks. Our 
>current research program includes the next generation network topology and 
>scalability, interdomain issues, support for mobility, multicast and
>QoS, security, privacy, etc. The SSVL group provides regional, national 
>and global testbeds for experimental research also for other 
>organizations. We also provide an operator-neutral access network in the
>Greater Stockholm area.
>
>Our current user community (pingable now)includes
>- The IT-University, Stockholm, 3ffe:200:15:44::1, native link, routing 
>via rip
>- Stanford University, ssvl.stanford.edu 3ffe:200:15:802:240:5ff:fea2:242b 
>native link, routing via rip
>- stockholmopen.net 3ffe:200:15:3:a00:02ff:fe9c:62b3, native link, routing 
>via rip
>
>Users being connected
>- University Eduardo Mondlane, Maputo, dzowo.uem.mz, 
>(3ffe:200:15:60::1)tunnel and static route
>- Tallin Technical University (), native link, routing via rip
>- imit.kth.se (), native link
>- kistaip.net (), native link
>- networks connected to the Solix IXP (www.sol-ix.com) that request 
>transit to the 6Bone backbone for R&D purposes.
>- scint.org ()
>- lanman2002.org
>- lanman2002.net
>
> >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 commit to abide by the 6Bone operational rules and policies, current
>and future.
>
> > 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.
>
>We commit to provide the necessary information requested by the 6Bone
>Operations Group.
>
> > 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>.
>
>All three persons mentioned above are memmbers of the list 6bone@isi.edu
>and are prepared to join additional lists if required to fulfill this
>commitment
>
>Sincerely
>
>Bjorn Pehrson
>SSVL admin-c
Previous message: A DNS question re 6to6/IPv6 host IN A records.
Next message: pTLA request SSVL - review closes 3 May 2002
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]