CASM (Coordinated Address Space Management) Draft-Xie-Ps-Centralized-Address-Management-02 Draft-Kumar-Casm-Problem-And-Use-Cases-00

Use Cases of CASM (Coordinated Address Space Management) draft-xie-ps-centralized-address-management-02 draft-kumar-casm-problem-and-use-cases-00

Chongfeng Xie, Qiong Sun (China Telecom) Weiping Xu, Will Liu (Huawei) Ian Farrer, Normen Kowalewski (Deutsche Telekom AG) Ying Cheng (China Telecom) Rakesh Kumar, Anil Lohiya (Juniper Networks) Marc Blanchet (Viagenie) Fioccola Giuseppe (Telecom Italia) Declan Ma (ZDNS)

1 Use Cases List

• Address pools configuration on (v)Devices / (v)Functions – DHCP server pool – Static address configuration • NAT & CGN – Public IP address pool • Address configuration API of IPAM • Interfaces to the RPKI – Resource Certificates and Signed Objects – Local Trust Anchor and RPKI RPs in ISPs • SDN/NFV scenarios

2 Use case 1 – sharing address among devices/(v)devices

• Our problem: Address allocation in broadband access users – With address shortage Configured with IPv4/v6 problem, the remaining IPv4 address pools, and Configured with address pools are usually quite announce the user domain for corresponding routing into subscribers scattered. Internet – It is complicated to manually configure all the address pools statically in BNGs (large MAN Client BRAS AAA may have more than 100 Access BNGs). request – Sometimes, the address pools Authentication are needed to be transited from Allocate address one BNG to another. from user domain – The same requirement for address pools Mobile is to manage PGW

3 Use case 2 - sharing address among functions/(v)functions

• Our problem – For IPv6 transition technologies, e.g. DS-Lite, lw4over6, etc., they Configured with IPv4 For HA support, address pools, and need to be configured with different address announce the pools are needed to address pools as translated corresponding routing into addresses. configure in one Internet CGN device – Different address pools are needed to be configured on each transition instance for HA support. Client DS-Li te/CGN DS-Li te/CGN – The occupation of the address Access with private addr Translate pools may vary during different to public transition periods. address – The same requirement for Failover managing address of dynamic occurs Translate Access to a to public created SFC functions backup device address It is too complicated to configure all these address pools manually

4 Use case 3 - NAT & CGN

• Our problem:

– With address shortage Configured with public IPv4 address problem, the remaining IPv4 pools, available port-range; Configured with private and public address pools are usually IPv4 address mapping rules quite scattered. – It is complicated to manually configure all the address pools statically in NAT. Public network Client BNG imbedded – Sometimes, the public with NAT/CGN address pools are needed to be transited from one NAT to Public network BNG another. Client NAT/CGN

5 Use case 4 - Address configuration API

MNS/OSS and IPAM perform address Address configuration API management on different levels of of IPAM granularity

6 Use case 5 - RPKI

ISP’s RPKI System IP Address Block Allocation>> Resources Certificate Issuance CA

IP Address Block Assignment>> Signed Object Management Repository IPAM

Private/Protected Addresses Allocation>> Local Routing Origin Assertion Local Trust Anchor

RPKI Relying Party

7 Use case 6 - SDN scenarios

SDN Controller (e.g., Neutron) allocation and de-allocation of subnets and IP addresses

CASM (e.g., IPAM)

Virtual Machine DHCP Virtual Machine Agent Virtual Virtual Function Function

Overlay Network Overlay Network Private or public clouds 8 Discussion

• Do you have similar address management problem in your network ? • What’s the current approach for address management in your network ? • Is it useful to have a common address management specification? • Do you have same requirement in your network? • Do you have interests to work on this topic ?

9 Backup slides

10 Description

• Organizations use IP Address Space Management (IPAM) tools to manage their IP address space, often with proprietary database and interfaces. • This work intends to evolve IPAM into standardized interfaces for coordinated management of IP addresses, including SDN/NFV networks and other forms of virtualization. • Use cases include dynamic allocation and release of IP addresses and prefixes based on usage (reallocation in case of no more in use) and/or user intent (for specific services).