[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[6bone] pTLA request ICPNET-PL - review closes 27 June 2002



6bone Folk,

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

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

<http://www.ipv6.icpnet.pl>


Thanks,

Bob

===
>Date: Thu, 13 Jun 2002 09:50:16 +0200
>From: Bartosz Waszak <[email protected]>
>To: Bob Fink <[email protected]>
>Subject: pTLA Request for ICPNET (AS13110), resubmit
>
>Hello!
>
>Here we present our corrected application for a 6Bone pTLA.
>
>RFC 2772:
> >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:
>
>We have about 6 months experience as a 6bone end-site.
>
> > 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.
>
>ipv6-site:    ICPNET-PL
>origin:       AS13110
>descr:        Internet Cable Provider (major broadband service in country)
>country:      PL
>prefix:       3FFE:8010:7:11::/64
>prefix:       3FFE:8010:7:F00::/56
>prefix:       3FFE:8320:2:5::/64
>application:  ping ontario.ipv6.icpnet.pl
>application:  www www.ipv6.icpnet.pl
>application:  smtp ontario.ipv6.icpnet.pl
>application:  ftp ftp.ipv6.icpnet.pl
>tunnel:       IPv6 in IPv4 ontario.ipv6.icpnet.pl -> 6bone-gw.6bone.pl 
>ICM-PL BGP4+
>tunnel:       IPv6 in IPv4 ontario.ipv6.icpnet.pl -> ipv6-gw.man.poznan.pl 
>POZMAN BGP4+
>tunnel:       IPv6 in IPv4 ontario.ipv6.icpnet.pl -> 
>nautilus.ipv6.icpnet.pl ICPNET STATIC
>tunnel:       IPv6 in IPv4 ontario.ipv6.icpnet.pl -> chaos.wmid.amu.edu.pl 
>UNDEFINE BGP4+
>contact:      IS2-6BONE
>remarks:      joined projects: SCIFI (operational since Sep 2000) and UNISOFT
>notify:       [email protected]
>mnt-by:       MNT-SCIFI
>changed:      [email protected] 20020611
>source:       6BONE
>
>inet6num:     3FFE:8010:7:F00::/56
>netname:      ICPNET-PL
>descr:        Internet Cable Provider
>country:      PL
>admin-c:      BW3-6BONE
>tech-c:       IS2-6BONE
>remarks:      ICPNET, pilot project for transition Cable Modem access to ipv6
>notify:       [email protected]
>mnt-by:       MNT-SCIFI
>changed:      [email protected] 20020611
>source:       6BONE
>
>inet6num:     3FFE:8010:7:11::/64
>netname:      ICPNET-PL
>descr:        Internet Cable Provider
>country:      PL
>admin-c:      BW3-6BONE
>tech-c:       IS2-6BONE
>remarks:      ICPNET, pilot project for transition Cable Modem access to ipv6
>notify:       [email protected]
>mnt-by:       MNT-SCIFI
>changed:      [email protected] 20020611
>source:       6BONE
>
>inet6num:     3FFE:8320:2:5::/64
>netname:      ICPNET-PL
>descr:        Internet Cable Provider
>country:      PL
>admin-c:      BW3-6BONE
>tech-c:       IS2-6BONE
>remarks:      ICPNET, pilot project for transition Cable Modem access to ipv6
>notify:       [email protected]
>mnt-by:       MNT-SCIFI
>changed:      [email protected] 20020611
>source:       6BONE
>
>role:         ICP Staff
>address:      ul. Owsiana 17
>address:      61-666 Poznan
>address:      POLAND
>e-mail:       [email protected]
>admin-c:      BW3-6BONE
>tech-c:       KP4-6BONE
>nic-hdl:      IS2-6BONE
>mnt-by:       MNT-SCIFI
>changed:      [email protected] 20020611
>source:       6BONE
>
>person:       Bartosz Waszak
>address:      ul. Owsiana 17
>address:      61-666 Poznan
>address:      POLAND
>phone:        +48618280132
>e-mail:       [email protected]
>nic-hdl:      BW3-6BONE
>url:          http://www.ipv6.icpnet.pl/
>notify:       [email protected]
>changed:      [email protected] 20020603
>source:       6BONE
>
>person:       Krzysztof Palicki
>address:      ul. Owsiana 17
>address:      61-666 Poznan
>address:      POLAND
>phone:        +48618280132
>e-mail:       [email protected]
>nic-hdl:      KP4-6BONE
>url:          http://www.ipv6.icpnet.pl/
>notify:       [email protected]
>changed:      [email protected] 20020612
>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.
>
>We have three BGP4+ peerings, and some static tunnels + native IPv6
>connections.
>
>BGP router identifier 62.21.98.6, local AS number 13110
>451 BGP AS-PATH entries
>7 BGP community entries
>
>Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ 
>Up/Down  State/PfxRcd
>
>ICM:
>3ffe:8010:7:11::1
>                 4  8664   32644    5793        0    0    0 01:02:02      217
>
>AMUWMID:
>3ffe:8010:7:6a00::3e
>                 4 58502    4991    1295        0    0    0 21:22:09      217
>
>POZMAN:
>3ffe:8320:1::30 4  9112   15817   10549        0    0    0 01w0d05h      211
>
>router is pingable via IPv6:
>[[email protected] /]# ping6 ontario.ipv6.icpnet.pl
>PING ontario.ipv6.icpnet.pl(3ffe:8320:2:5:2::1) 56 data bytes
>64 bytes from 3ffe:8320:2:5:2::1: icmp_seq=1 ttl=63 time=8.792 msec
>64 bytes from 3ffe:8320:2:5:2::1: icmp_seq=2 ttl=63 time=7.087 msec
>
> > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
> > entries for the Applicant's router(s) and at least one host
> > system.
>
>We maintain DNS entries for ipv6.icpnet.pl and for 3ffe:8010:7:f00::/56
>
>Our primary DNS server for IPv6 is: ontario.icpnet.pl
>Secondary: ww2.icpnet.pl
>
>;; global options:  printcmd
>ipv6.icpnet.pl.         600     IN      SOA     ontario.icpnet.pl. 
>hostmaster.ontario.icpnet.pl. 2002061101 10800 600 604800 86400
>ipv6.icpnet.pl.         600     IN      NS      ww2.icpnet.pl.
>ipv6.icpnet.pl.         600     IN      NS      ontario.icpnet.pl.
>ipv6.icpnet.pl.         600     IN      MX      0 voyager.ipv6.icpnet.pl.
>ipv6.icpnet.pl.         600     IN      MX      10 ontario.ipv6.icpnet.pl.
>z-portal-gw.amuwmid-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:11:2::1
>ftp.ipv6.icpnet.pl.     600     IN      CNAME   ontario.ipv6.icpnet.pl.
>z-voyager-gw.icm-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:11::1
>z-portal-gw.icpnet-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::c
>z-voyager-gw.icpnet-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::a
>irc.ipv6.icpnet.pl.     600     IN      CNAME   ontario.ipv6.icpnet.pl.
>z-portal-gw.ktnet-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::1
>localhost.ipv6.icpnet.pl. 600   IN      A       127.0.0.1
>nautilus.ipv6.icpnet.pl. 600    IN      A       62.21.3.239
>nautilus.ipv6.icpnet.pl. 600    IN      AAAA    3ffe:8320:2:5:1::2
>news.ipv6.icpnet.pl.    600     IN      CNAME   ontario.ipv6.icpnet.pl.
>ontario.ipv6.icpnet.pl. 600     IN      A       62.21.98.6
>ontario.ipv6.icpnet.pl. 600     IN      AAAA    3ffe:8320:2:5:2::1
>z-portal-gw.pbern-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::7
>z-portal-gw.pollus-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::5
>z-amuwmid-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:11:2::
>z-icpnet-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::d
>z-ktnet-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::
>z-pbern-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::6
>z-pollus-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::4
>z-thelema-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::2
>z-undefine-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::8
>z-portal-gw.thelema-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::3
>z-portal-gw.undefine-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::9
>voyager.ipv6.icpnet.pl. 600     IN      A       62.21.3.1
>voyager.ipv6.icpnet.pl. 600     IN      AAAA    3ffe:8320:2:5:1::1
>z-icm-gw.voyager-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:11::2
>z-icpnet-gw.voyager-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::b
>www.ipv6.icpnet.pl.     600     IN      CNAME   ontario.ipv6.icpnet.pl.
>ipv6.icpnet.pl.         600     IN      SOA     ontario.icpnet.pl. 
>hostmaster.ontario.icpnet.pl. 2002061101 10800 600 604800 86400
>;; Query time: 23 msec
>;; SERVER: 62.21.98.6#53(ontario.icpnet.pl)
>;; WHEN: Wed Jun 12 21:03:10 2002
>;; XFR size: 36 records
>
>$ORIGIN .
>$TTL 600        ; 10 minutes
>f.0.7.0.0.0.0.1.0.8.e.f.f.3.ip6.int IN SOA dns.portalcafe.pl. 
>root\@scifi.eu.org. (
>                                 2002051806 ; serial
>                                 10800      ; refresh (3 hours)
>                                 600        ; retry (10 minutes)
>                                 604800     ; expire (1 week)
>                                 86400      ; minimum (1 day)
>                                 )
>                         NS      dns.portalcafe.pl.
>                         NS      voyager.ipv6.icpnet.pl.
>$ORIGIN f.0.7.0.0.0.0.1.0.8.e.f.f.3.ip6.int.
>$ORIGIN 0.0.0.0.0.0.0.0.0.0.0.d.e.e.f.0.0.f.0.7.0.0.0.0.1.0.8.e.f.f.3.ip6.int.
>0                       PTR     z-ktnet-gw.portal-gw.ipv6.icpnet.pl.
>1                       PTR     z-portal-gw.ktnet-gw.ipv6.icpnet.pl.
>2                       PTR     z-thelema-gw.portal-gw.ipv6.icpnet.pl.
>3                       PTR     z-portal-gw.thelema-gw.ipv6.icpnet.pl.
>4                       PTR     z-pollus-gw.portal-gw.ipv6.icpnet.pl.
>5                       PTR     z-portal-gw.pollus-gw.ipv6.icpnet.pl.
>6                       PTR     z-pbern-gw.portal-gw.ipv6.icpnet.pl.
>7                       PTR     z-portal-gw.pbern-gw.ipv6.icpnet.pl.
>8                       PTR     z-undefine-gw.portal-gw.ipv6.icpnet.pl.
>9                       PTR     z-portal-gw.undefine-gw.ipv6.icpnet.pl.
>a                       PTR     z-voyager-gw.icpnet-gw.ipv6.icpnet.pl.
>b                       PTR     z-icpnet-gw.voyager-gw.ipv6.icpnet.pl.
>c                       PTR     z-portal-gw.icpnet-gw.ipv6.icpnet.pl.
>d                       PTR     z-icpnet-gw.portal-gw.ipv6.icpnet.pl.
>
> > 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 new IPv6 Accessible web page is under construction.
>Currently on http://www.ipv6.icpnet.pl/ is info about how
>to contact with us.
>
> > 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.
>
>person:       Bartosz Waszak
>e-mail:       [email protected]
>nic-hdl:      BW3-6BONE
>
>person:       Krzysztof Palicki
>e-mail:       [email protected]
>nic-hdl:      KP4-6BONE
>
> > 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.
>
>[email protected]
>
>This address is configured as a "e-mail" attribute in the "role" object.
>
> > 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.
>
>ICP is providing internet access by cable modems or directly to
>our backbone by Ethernet. We have about 10'000 users,
>so we are in Poland one of the major ISPs.
>
> > 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 to abide by the rules as they exist now and as they may evolve in
>the 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.
> >
> >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>.
>
>Regards
>
>--
>Bartosz Waszak <[email protected]>
>Internet Cable Provider Sp. z o.o.
>(http://www.icpnet.pl/)