pTLA request for WEBONLINE-NET (www.webonline.no) - review
closes 15 November 2001
Bob Fink
fink@es.net
Fri, 02 Nov 2001 06:14:29 -0800
6bone Folk,
WEBONLINE-NET (www.webonline.no) has requested a pTLA allocation. The open
review period for this will close 16 November 2001. Please send your
comments to me or the list.
Thanks,
Bob
===
>From: Jørgen Hovland <jorgen@hovland.cx>
>To: "Bob Fink" <fink@es.net>
>Subject: pTLA request (WO)
>Date: Fri, 2 Nov 2001 13:27:53 +0100
>
>Hi
>
>
>
>I think everything is right this time.
>
>
>
>Sincerly,
>
>Joergen Hovland
>
>WebOnline AS
>
>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:
>
>WebOnline is an isp/asp in Norway.
>
>We have a 6bonelink through td.org.uit.no/ Roger Jørgensen since he got it
>in November last year from Toledo. IP-prefix is 3ffe:1ce3:12:a::/64
>
>
>Also a 2 prefixes from Hot-web in Germany ( 2001:740:102:a::/64 and
>2001:740:102:b::/80)
>
>
>Just for the record:
>traceroute to www.6bone.net (3ffe:b00:c18:1::10)
>1 ipv6-gw.webonline.no (2001:740:102:a::0) 0.419 ms 0.309 ms 0.318 ms
>2 3ffe:1ce3:12::2:1 (3ffe:1ce3:12::2:1) 23.133 ms 22.927 ms 23.329 ms
>3 server.pasta.cs.uit.no (3ffe:2a00:100:3001::2) 249.963 ms 256.741 ms
>251.527 ms
>
>
> 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.
>
>
>
>We dont have any inet6num cause they are owned by the somebody else.
>
>ipv6-site: WEBONLINE-NET
>origin: AS16186
>descr: WebOnline AS
>location: Drammen
>country: NO
>prefix: 3FFE:1CE3:12:A::/64
>prefix: 2001:740:102:A::/64
>prefix: 2001:740:102:B::/80
>tunnel: IPv6 in IPv4 webonline.no -> chello.no CHELLO-MNT BGP4+
>tunnel: IPv6 in IPv4 webonline.no -> uit.no JAMESB BGP4+
>tunnel: IPv6 in IPv4 webonline.no -> hot-web.net JF7286-RIPE BGP4+
>contact: JH
>remarks: Mail jorgen@ssc.net for any questions or peering requests
>remarks: We do not announce any prefixes yet
>url: http://www.webonline.no
>notify: noc@webonline.no
> mnt-by: WEBONLINE
> changed: jorgen@ssc.net 20011102
>source: 6BONE
>
>person: Joergen Hovland
>address: Nedre storgate 10
>phone: +47 98456333
>e-mail: ipv6@hovland.cx
>nic-hdl: JH
>mnt-by: WEBONLINE
>changed: jorgen@ssc.net 20010921
>source: 6BONE
>
>mntner: WEBONLINE
>descr: WebOnline AS
>admin-c: JH
>upd-to: hostmaster@webonline.no
>auth: CRYPT-PW *
>mnt-by: WEBONLINE
>changed: jorgen@ssc.net 20011030
>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.
>
>
>
>Linux bgp+ has been running almost since last year I think.
>Bgp4+ on the cisco's was newly implemented because the non-beta ios is kinda
>new.
>
>We have 1 ipv6 peer: Chello broadband (also ipv4)
>
>Native peering in Norway will come when the ix is ready.
>
>The 2 other's are default routes ( 2000::/3)
>
>We do not announce anything because we dont have anything to announce yet.
>
>#sh bgp ipv6
>BGP table version is 18, local router ID is 10.0.3.2
>Status codes: s suppressed, d damped, h history, * valid, > best, i -
>internal
>Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
>*>i2000::/3 2001:740:102:A::F
> 100 0 65001 i
>*> 2001:730::/35 2001:730:3::1:C 0 6830 i
>*> 2001:740:102:A::/64
> :: 32768 i
>*>i2001:740:102:C::/64
> 2001:740:102:A::F
> 100 0 65001 i
>*> 3FFE:1CE3:12:A::/64
> :: 32768 i
>
>BGP router identifier 10.0.3.2, local AS number 16186
>BGP table version is 18, main routing table version 18
>5 network entries and 5 paths using 985 bytes of memory
>17591 BGP path attribute entries using 1056420 bytes of memory
>15446 BGP AS-PATH entries using 397332 bytes of memory
>23 BGP community entries using 776 bytes of memory
>0 BGP route-map cache entries using 0 bytes of memory
>2 BGP filter-list cache entries using 24 bytes of memory
>BGP activity 109424/507859 prefixes, 112573/7642 paths, scan interval 15
>secs
>
>
>
> c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
> entries for the Applicant's router(s) and at least one host
> system.
>
>
>
>This should be already working see section 1.
>
>
> 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.
>
>our smtp.webonline.no runs ipv6. Also sshd, telnet, imap, pop3, ircd on a
>couple of servers.
>
>www.webonline.no does not run ipv6 (yet). its a nt-server...
>
>www.ipv6.webonline.no is up.
>
>
>
> 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.
>
>Iver Olsen (iver.olsen@webonline.no)
>Oyvind Ellefsen (oyvind@webonline.no)
>and me
>
>
> 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.
>
>noc@webonline.no
>
> 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.
>
>We will serve all customers who support and wishes to use ipv6.
>
>All leased lines customers will be allocated ipv6 and ipv4.
>All servers will be allocated ipv6 (if supported) and ipv4.
>
>All dsl-customers will be allocated ipv6 if supported. (router
>advertisement)
>Dialup has its own ipv6 number.
>We have a lot of hosted websites (win2k and unix servers). They will support
>ipv6 when there are non-beta software availible.
>
>Free tunnels will be given out for non-commercial purposes for
>non-customers.
>
>
>
> 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.
>
>
>
>Iver, Oyvind and I will abide the 6bone rules and policies as they exist
>today and future rules and policies as they evolve.
>
>
>http://www.ietf.org/rfc/rfc2772.txt
>
>
>
> 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.
>
>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>.
>
>I have joined the mailinglist.