Supported by the GlobalNOC at Indiana University


IPv4 Address Allocations

Keywords: address, allocations, indiana gigapop, ipv4, members

The Indiana Gigapop will allocate IPv4 addresses to members who cannot obtain their own provider independent addresses.   

Allocations made so far by the Indiana Gigapop to its members are:

IPv4 Address
NCAA IU Research Notre Dame IU LHCONE VRF
Gigapop Zayo K12 Pilot Project Akamai Caching Service Google Caching Service

Netflix Caching Service


last edited 10 April 2007

IPv6 Address Allocations

Keywords: address, allocation, indiana gigapop, ipv6

The Indiana Gigapop has a direct IPv6 address allocation from ARIN of 2001:18e8::/32. The Gigapop delegates prefixes in the range of /40s through /48s to its members depending on the size of their networks.   A member with a single campus may receive a /48 whereas a member with 8 campuses may receive a /45.   Each Gigapop member can in turn divide their prefix into a /48 for each campus and further into /64s for individual broadcast domains. (See RFC2374 and RFC3177 for guidelines on address allocation). It is expected that all suballocations are SWIPed to ARIN so that they are documented to the world.

Because of the way v6 address space is aggregated, these delegated /48 addresses will (likely) not be accepted from end-sites and routed by other carriers and are not "portable".

Allocations made so far by the Indiana Gigapop for its internal use and to its members are recorded here - Gigapop Members IPv6 Allocations.

The table below references the intitial allocations, please use the link above for future allocations.


  2001:18e8::/36 Gigapop Member Blocks
  2001:18e8:0000::/44 Indiana University System
    2001:18e8:0001::/48 IUPUI (suballocation)
    2001:18e8:0002::/48 IUB (suballocation)
    2001:18e8:0003::/48 IUE (suballocation)
    2001:18e8:0004::/48 IUK (suballocation)
    2001:18e8:0005::/48 IUNE (suballocation)
    2001:18e8:0006::/48 IUSB (suballocation)
    2001:18e8:0007::/48 IUSE (suballocation)
  2001:18e8:0400::/40 I-Light
  2001:18e8:0800::/44 Purdue University System
  2001:18e8:0c00::/48 Notre Dame
  2001:18e8:0c02::/46 IU Research (Bloomington)
  2001:18e8:ff00::/48 Indiana Gigapop Internal

Following recommended ipv6 allocation practice, each site is expected to be allocated one or more /48s as needed.

The Indiana Gigapop also has an IPv6 allocation from Internet2 (2001:468:0400::/40), but these addresses should never be allocated.   


BGP Communities

This document describes the BGP Communities used by the Indiana Gigapop. This includes communities that the Gigapop tags simply to add meta-data to BGP prefixes and communities that Gigapop members can set to influence routing behavior at the Gigapop.

BGP Communities the Indiana Gigapop sets:

19782:1001 Tagged to all Indiana Gigapop Member prefixes that receive R&E (ie connectivity to Internet2 and other Gigapop members) connectivity.
19782:1002 Tagged to all Indiana Gigapop Member ipv4 prefixes that receive Commodity Internet connectivity.
19782:1003 Tagged to all Indiana Gigapop Member ipv4 prefixes that receive Settlement-Free Commodity Internet connectivity.
19782:1006 Tagged to all Indiana Gigapop Member ipv6 prefixes that receive R&E (ie connectivity to Internet2 and other Gigapop members) connectivity.
19782:2001 Tagged to all prefixes received from Commodity Internet providers (currently Sprint and Timewarner)
19782:2002 Tagged to all prefixes received from Settlement-Free Peer Networks (currently IQuest, Wintek, and Internet2's Peering Service)
19782:2003 Tagged to all prefixes received from R&E network (currently Internet2 and MREN)
19782:2004 Tagged to all ipv6 prefixes received from R&E network (currently Internet2, BTAA and MREN)

BGP Communities that Gigapop Members can set:


Blackhole/Discard, GigaPOP will discard traffic toward this prefix and trigger upstream providers to discard traffic towards this prefix.  Only members who “own” the prefix may set the 19782:911 community.

Upstream Provider Participation

  • Internet2 (BGP Community 11537:911 or 65536:666)
  • Internet2 TR-CPS (BGP Community 65536:666)
  • Hurricane Electric (BGP Community 6939:666)
  • WiscNet Regional Internet Peering Service (2381:911)
  • TeliaSonera (BGP Community 1299:999)
  • Cogent Communications (triggered from 19782:911)

Local-preference modification (member default is 400, R&E Peer default is 300, Settlement-Free Peers 275, Commodity Peer default is 250 and Commodity Transit default is 200):

19782:150 Causes the Gigapop to add 50 to the default BGP Local-Preference applied to Member prefixes.
19782:50 Causes the Gigapop to subtract 50 from the default BGP Local-Preference applied to Member prefixes
19782:600 Causes the Gigapop to set BGP Local-Prefernece to 600
19782:500 Causes the Gigapop to set BGP Local-Prefernece to 500
19782:200 Causes the Gigapop to set BGP Local-Prefernece to 200

Export modification: default behavior is to send all learned GigaPOP prefixes to all BGP peers. The following communities are available per-prefix to allow members and peers to modify the default behavior (XXXXX=remote ASN. i.e. 65100:87 to block prefix to IU):

65000:XXXX Do not send this prefix to R&E Peer network.
65000:65000 Do not send this prefix to any R&E Peer network.
65001-65003:XXXX GigaPOP should prepend one-three ASs to R&E Peer network.
65100:XXXX Do not send this prefix to GigaPOP member.
65100:65100 Do not send this prefix to any GigaPOP member.
65101-65103:XXXX GigaPOP should prepend one-three ASs to GigaPOP member.
65400:XXXX Do not send this prefix to GigaPOP transit.
65400:65400 Do not send this prefix to any GigaPOP transit.
65401-65403:XXXX GigaPOP should prepend one-three ASs to GigaPOP transit.

Note: The Gigapop may need to change the BGP Communities it tags to prefixes in the future. If this is necessary, we will provide sufficient notification so that any routing policy members may have based on these communities can be updated.

Indiana Gigapop NOC Support - DDoS Mitigation (Scrubbing) Service FAQ

GigaPOP / I-Light DDoS Mitigation (Scrubbing) Service FAQ


Q: What is the cost to Indiana GigaPOP and I-Light Members?

A: The cost for the scrubbing service will be shared between Indiana GigaPOP members, including I-Light.   Once we know how many of the GigaPOP members are going to participate we will spread the costs proportionally.  We’ll be InTouch with the individual GigaPOP members to discuss these costs in more detail in the near future.

Q: Can members Opt-In and Opt-Out?

A: We think so, initially the scrubbing service will be a manual action by either the Indiana GigaPOP and I-Light Network Engineers or members themselves via BGP Communities.  A future automated process would need to take into account prefixes which would be excluded.  Considerations may need to be made for frequency of Opt-In/Opt-Out changes as well as time required to process changes.

Q: How do members Opt-In and Opt-Out?

A: Members may Opt-In or Opt-Out by notifying the appropriate NOC; Indiana GigaPOP or I-Light.  **Please note the anticipated turnaround time to be three (3) days to change a members status.

Q: Is BGP required to participate in the scrubbing service?

            A: No.  BGP allows the Indiana GigaPOP or I-Light member to initiate the scrubbing service independently of Indiana GigaPOP or I-Light Engineers.  Without BGP, a manually process will be implemented by Indiana GigaPOP or I-Light Engineers.

Q: Will Indiana GigaPOP and I-Light Engineers be available to assist with members BGP administration and verification?

A:  Yes!  Indiana GigaPOP and I-Light Engineers can help in three ways.

  1. Documentation of examples
  2. Proactive discussion on BGP Configuration
  3. Reactive assistance for BGP Configuration Verification


Q: How will members be notified when a DDoS attack is occurring against the network or the member?  How will members be notified when DDoS scrubbing is active?

            A:  The NOC for Indiana GigaPOP or I-Light will send targeted notifications to member institutions when an attack is observed and when the attack has subsided.  Members which Opt-In for the scrubbing service will also receive a notification when scrubbing is activated and deactivated.  Members who request confirmation will only receive the scrubbing notifications after a representative acknowledges activation or deactivation.

Q: How will the DDoS Scrubbing service affect Multicast?

            A: The DDoS Scrubbing service only functions on commodity traffic from transit providers.  Currently no active transit providers support Multicast.  Multicast traffic should not be affected internal the Indiana GigaPOP or I-Light, although public senders or receives can still be attacked and external traffic to those hosts may be scrubbed.


Q: Will scrubbed traffic induce latency?

            A: Yes.  Exactly how much latency is unknown, dependent on the external endpoint and path to Indiana GigaPOP or I-Light member.  To provide reference, latency from Indiana to the West coast is approximately 48ms round trip, to the East coast is approximately 22ms round trip.  Using these reference points, a maximum of an additional 50ms of latency may be encountered when the scrubbing service is active.

VLAN Allocations

Layer 2 Switched Vlans
2 Futuregrid OOB via Starlight (lan.ictc)
10 Indiana University - Bloomington (R&E)
12 Indiana University - Bloomington (Commodity)
14 IU 4-external VRF
15 IU IPV6 (IUB Commodity)
16 IU IPV6 (IUPUI Commodity)
104 Monon100 OSC 15454 Mgmt Net (lan.ictc)
112 Interfonnect ICTC T640 to LL T640
125 Smithville Digital | GLOBAL-ICTC-BLDC-VLAN-01706
129 GP-RackLAN (lan.ictc)
130 Internet2 Optical management vlan
131 GP-RackLAN 2 (lan.ictc)
134 Indiana Gigapop HP5400 Server Management
135 Indiana Gigapop HP5400 Management
136 Incntr
137 Indiana Gigapop 2nd Server Management Vlan
149 Google Global Caching
305 IU Research Network (IUB Commodity) Backup
306 IU Research Network (IUB R&E) Backup
541 Internet2 DCN router LifeLine
667 City of BLTN bus-chum political conferences

Chicago-ICTC Layer2 Vlans
5 srv.chic 600W Testpoint Server [PENDING]
89    L2 BB to CIC OmniPOP | GLOBAL-CIC-ING-VLAN-01646
90    MOXI Racklan via CIC OmniPOP | GLOBAL-CIC-ING-VLAN-01707
116   N-WAVE MGT via CIC (No notification) | GLOBAL-CIC-ING-VLAN-01647
211   TR/CPS via I2 Chic | GLOBAL-CIC-ING-VLAN-01648
541   Internet2 DCN router LifeLine
945   Wiscnet RPS via CIC | GLOBAL-CIC-ING-VLAN-01651
982   U Wisconsin-Madison via CIC  | GLOBAL-CIC-ING-VLAN-01652
2001  L2 BB 100G to sw.chic  | GLOBAL-ING-ING-VLAN-01653
2013  FutureGrid (Commodity) | GLOBAL-FG-ING-VLAN-1509
2014  FutureGrid (R&E) | GLOBAL-FG-ING-VLAN-1510
2023  BigTenNetwork via CIC | GLOBAL-CIC-ING-VLAN-01654
2030  BTN to Purdue | GLOBAL-CIC-ING-VLAN-01709
2048  Internet2 CPS v6  | GLOBAL-I2-ING-VLAN-01655
2063  Internet2 R&E via 600W  | GLOBAL-I2-ING-VLAN-01656
2091  NLR (R&E) | GLOBAL-CIC-ING-VLAN-01658
2152  U of Chicago via CIC  | GLOBAL-CIC-ING-VLAN-01660
2171  UIUC via CIC  | GLOBAL-CIC-ING-VLAN-01661
2180  Iowa via CIC  | GLOBAL-CIC-ING-VLAN-01662
2182  MERIT via CIC  | GLOBAL-CIC-ING-VLAN-01663
2183  UMN via CIC  | GLOBAL-CIC-ING-VLAN-01664
2184  Northwestern via CIC  | GLOBAL-CIC-ING-VLAN-01665
2185  OSU/OARnet via CIC | GLOBAL-CIC-ING-VLAN-01666
2221  Wiscnet via CIC  | GLOBAL-CIC-ING-VLAN-01667
2225  OSU/OARnet I2 Members via CIC  | GLOBAL-CIC-ING-VLAN-01668
2247  Wiscnet RPS via CIC 600W | GLOBAL-CIC-ING-VLAN-01702
2298  Inband mgt to CIC Force10  | GLOBAL-CIC-ING-VLAN-01669
2300  ESnet via CIC  | GLOBAL-CIC-ING-VLAN-01670
2494  MOXI via CIC 600W

2510 Purdue/LHCOne Peer via I2 | GLOBAL-I2-ING-VLAN-03636
2547  Purdue Calumet via CIC - ING | GLOBAL-ING-PU-VLAN
2548  NLR (R&E) to Purdue- ING | GLOBAL-CIC-PU-VLAN
2549  CMS (R&E) to Purdue- ING | GLOBAL-ING-PU-VLAN
2550 Purdue RE data center peering vlan

Indiana GigaPOP Cache Node Information

Indiana GigaPOP Caching Information


Akamai Peering -
Akamai V6 Peering - 2600:1400:5:15::c16c:5c3e
Akamai IPv6 Cache Node - 2001:18E8:FFFF:C::/64
Akamai Server Farm -
Akamai BGP point-to-point peering to ICTC T640 -
Akamai Cache Server Farm -


Google V6 Caching Service - 2001:18E8:FFFF:48::/64
Google Caching Service -
Google Caching Service -


Netflix Cache 20G Node - 2001:18E8:FFFF:9::/64
Netflix Commodity Cache Appliance Gateway RTR.ICTC -
Netflix Commodity Cache Appliance #1 -
Netflix Commodity Cache Appliances -
Netflix Commodity Cache Appliance #3 -
Netflix Commodity Cache Appliance BGP Peering -
Netflix Open Connect Cache IPv4 ICTC #3 - 2001:18E8:FFFF:D::/64
Netflix Commodity Cache Appliance v6 BGP Peering - 2001:18e8:ffff:6::/64
Netflix OpenConnect Cache 20G Node #2 - 2001:18E8:FFFF:A::/64
Netflix Cache #3 - 2001:18E8:FFFF:5::4/128
Netflix Commodity Cache Appliance v6 - 2001:18e8:ffff:5::/64
Netflix Commodity Cache Appliance #2 -
Netflix Cache #1 - 2001:18E8:FFFF:5::2/128
Netflix Cache #2 - 2001:18E8:FFFF:5::3/128
RTR.ICTC Netflix Cache Gateway - 2001:18E8:FFFF:5::1/128


Apple CDN via 350 Cermak Chicago - on with ASN 714

Apple CDN IPv6 via 350 Cermak Chicago - 2620:149:bb:9520::1 on with ASN 714

Apple CDN received v4 routes -

Apple CDN received v6 routes:

Apple CDN subnets:

Your request has been completed.