TESTA-II IP Addressing Tim Duckett Enterprise Solutions Group 6th June 2000

Agenda This presentation covers the following areas: Purpose and definitions Addressing policy Approach Assumptions Allocation & Control Network Address Translation Registration

Purpose of this presentation The purpose of this presentation is to : define some common terms outline the address space management approach outline the allocation management approach This presentation is based on a draft paper, and is open for discussion!

Some brief definitions EuroDomain The backbone TESTA network bounded by PE routers Local Domain the local networks of the connected organizations extends from the CE router inwards Global One management domain CE router outwards

Some brief definitions - 2 “TESTA public” any device which can be accessed over the EuroDomain available to the EuroDomain does NOT imply Internet connection (although the host may be accessible from the Internet, Internet traffic is not routed across the EuroDomain) therefore a “TESTA public Host” is any host which will be accessed across the EuroDomain backbone e.g. a publicly-available webserver “Internet public” available to the Internet can be accessed from the public Internet, and from other TESTA locations

Some brief definitions - 3 “private” only available to local domains any device on a local domain which will NOT be accessed across the EuroDomain “registered address” An address from a range allocated by RIPE

Backbone routing WAN backbone routing is performed by EBGP IBGP can be utilized internally (more later)

Addressing Policy - Policy approach The addressing policy is driven by the physical structure of the TESTA network it is a hierarchical approach, with the EuroDomain at the top and local domains below allocation of address ranges will reflect this EuroDomain Local Domain Local Domain Local Domain Local network Local network Local network Local network Local network Local network

Addressing Policy - Policy approach The logical structure of local domains COINs does NOT influence the addressing policy. The logical structure is managed by the combination of IP routing and VPNs

Addressing Policy - range allocation The IP range(s) allocated to TESTA-II will conform to the following standards : they will be allocated by RIPE they will be registered and administered by Global One on behalf of the European Commission they will be provider-independent (i.e. they don’t belong to Global One) they will be allocated to local domains on an “on-demand” basis they will not be used by local domains for internal purposes (e.g. for DHCP scopes etc)

Addressing Policy - assumptions All TESTA public hosts will be allocated registered IP addresses from the RIPE-allocated range Only the registered address range will be routed across the EuroDomain Internet traffic from local domains will not be routed over the EuroDomain Local security requirements will be addressed locally

Network Address Translation Will be used : throughout the TESTA-II network to translate between private ranges on local domains and the registered addresses Will act on both source and destination addresses The NAT will be : applied at the CE Router

Network Address Translation - example The two hosts have been allocated public addresses TESTA public addresses : Host A = 210.15.91.2 Host B = 205.21.14.2 Local addresses : Host A = 10.1.1.2 Host B = 172.1.1.2 Domain A is aware of TESTA addresses Domain B uses an internal address to route to host in Domain A All NAT takes place at local CE routers

Network Address Translation - example Client in Domain A accesses host in Domain B

Network Address Translation - example Client in Domain B accesses host in Domain A

Address Registration NOTE! The following information is subject to confirmation from RIPE, so is not binding until then!

Address Registration A full Class-B address range will be allocated by RIPE it will be reserved... …but not provided in its entirety RIPE will assign an initial address range within the Class B i.e. a smaller number of class C ranges Additional ranges will be requested and allocated to cover the future expansion of the network

Classification of networks Networks will be classified according to their function backbone network (EuroDomain) local domains networks within local domains Networks will be further classified according to size small, medium, large networks will then be allocated a range(s) of the appropriate size.

Address allocations IP ranges will be allocated according to the following guidelines IP addresses should be allocated to maximize the availability of what is a limited resource Addresses will be allocated in the following order TESTA public host addresses clients that require static addresses for specific application requirements clients that can handle dynamic addresses As a general rule, client addresses should be allocated using dynamic address translation to reduce the number of fixed addresses required Ranges should not be used for internal purposes e.g. DHCP scopes

Allocation procedures Allocation procedures are handled by Global One IP Engineering in Reston Reston act as guardians of the RIPE-provided ranges They are responsible for the allocation and management RIPE requires detailed justification for usage of public address space, hence it is necessary to keep close control of space of space delegated to Global One

Allocation procedures When a domain connects to TESTA-II, they must request an address range The request is submitted on a technical questionnaire, which provides information on: number of hosts with fixed addressing number of clients with dynamic addressing future numbers of hosts future numbers of workstations

Allocation procedures Additional allocation procedure will be required when a domain “out-grows” its initial allocation This will require the completion of a simplified technical questionnaire The additional allocation procedure will be controlled as a change request

Technical Questionnaire