ISP Readiness IPV6 Route Objects

An NTT Example
Teoh Kiat Jin NTT MSC Sdn Bhd Cyberjaya

NTT MSC Sdn Bhd

What is a Route Registry

http://en.wikipedia.org/wiki/Internet_Routing_Registry Its a Database Shares Route & Related Information Mainly used by ISPs Appropriate format for programming/configurating routers Network Engineers from ISPs are Authorised to modify RPSL Objects Any Network Engineer or Public persons may query RR for related information

NTT MSC Sdn Bhd

Components

AS Number Aut-Num / AS-Name / Inetnum

eg: whois AS10204 or AS2914 Aut-num: AS10204 As-name: ARCNET-NTTMSC-MY Descr: Arcnet NTT MSC ISP

Aut-num: AS2914 As-name: NTTC-GIN-AS Descr: NTT Communications Global IP Network

NTT MSC Sdn Bhd

Ipv4 Example:

Eg. whois 203.115.224.0 / 129.250.50.0 Inetnum: Netname: Descr: NetRange: CIDR: NetName: NetHandle:
.

203.115.224.0 - 203.115.255.255 ARCNET NTT MSC Arcnet ISP 129.250.0.0 - 129.250.255.255 129.250.0.0/16 NTTA-129-250 NET-129-250-0-0-1 NTT America, Inc. NTTAM-1 8005 South Chester Street
NTT MSC Sdn Bhd

OrgName: OrgId: Address:

Ipv6 Example: Eg. whois 2001:c18::/32 / 2401:3C00::/32 whois 2001:c18::/32 Inet6num: 2001:0C18::/32 Netname: ARCNET6-20020723 Descr: Arcnet6 -NTT MSC Sdn. Bhd.
These are NOT Route Objects!

whois 2001:218::/32 Inet6num: 2001:0218::/32 Netname: NTT-JP-19990922 Descr: NTT Communications Global IP Network whois 2401:3c00::/32 Inet6num: 2401:3C00::/32 Netname: PACKETONE-AS-AP Descr: Packet One Networks (Malaysia) SDN BHD
NTT MSC Sdn Bhd

Route Objects (v4 & v6)

Record (Database Entry) of CIDR range which you'd like to advertise to your upstream.
whois -h rr.ntt.net 203.115.224.0/24 Route: 203.115.224.0/24 Descr: Arcnet NTT MSC ISP Origin: AS10204 whois -h rr.ntt.net 203.115.224.0/18 Route: 203.115.192.0/18 Descr: Arcnet NTT MSC ISP Origin: AS10204
Route Object are obtained from Route-Registry

NTT MSC Sdn Bhd

Route Objects (v4 & v6 cont)

whois -h rr.ntt.net 2001:0c18::/32 Route6: 2001:c18::/32 Descr: Proxy RO for Arcnet NTT MSC ISP Origin: AS10204 Source: NTTCOM Note: Route6:
Objects

whois -h rr.ntt.net 2001:328::/32 Route6: 2001:328::/32 Descr: JARING MIMOS BHD MY Origin: AS2042 Notify: nic@jaring.my Mnt-by: MAINT-AS2042 Changed: zamzuri@jaring.my 20061213 Source: RADB
NTT MSC Sdn Bhd

Note: Origin

Why are Route Objects Important

When you do BGP with an ISP:

ISP needs to ensure your v4 & v6 blocks are valid/correct ISP needs to build filters/route-maps Your AS-Number must be correct The same applies to Your downstream and this is achieved with an AS-SET

NTT MSC Sdn Bhd

What are AS-SETs

Its a container for downstream customers to include their members (with whom they do BGP with). Example: AS-2914 AS-00000 AS-1111 AS2222
AS-SET

AS-SET

AS-SET

AS-Num

In this example, AS2222 does not have downstream customers, so they do not require an AS-SET
NTT MSC Sdn Bhd

This is what it looks like!

whois -h rr.ntt.net as2914:as-asia as-set: AS2914:AS-ASIA descr: NTT Communications Global IP Network transit for Asian Customers members: AS2914, AS3949, AS-10099NTT, AS-10204, AS-17444-TRANSIT, AS-17666, AS-37997, AS-38322, AS-45419, AS-4648-CUSTOMERS, AS-4788, AS-4818, AS-5713, AS-7552, AS-9381, AS-9513VERIO, AS-9908VERIO, AS-AKAMAI, AS-AMAZON, AS-BESTPATH, AS-CN2, AS-CTMTELEONE, AS-CWASIA, AS-DIYIXIAN, AS-DRUKNET, AS-DTN, AS-DYNINC, AS-EDGECAST, AS-EMIX, AS-GTLD, AS-HKBN, AS-HKNET, AS-HUTCHCITY, AS-IHENDERSON, AS-IXTECH-CUSTOMER, AS-KINX-TRANSIT, AS-LINKAGE, AS-LYNX, AS-MAGIX, AS-MICROSOFT, AS-NTTNETID, AS-OCN-ALL, AS-OPENDNS, AS-PLDT, AS-PNAPSYD001, AS-PROLE, AS-QTEL-SET, AS-SAMSUNGNETWORKS, AS-SET-10143EXETEL, AS-SET-GTI-PIP, AS-SINGNET, AS-SKYINTERNET, AS-SLTNET-TRANSIT, AS-SPT, AS-STARHUBINTERNET, AS-THIX, AS-TIG-GROUP, AS-TMHK, AS-TRIPLETNET, AS-UDOMAIN, AS-VDC, AS-VIPNETNTT, AS-VSNL-IN, AS-WHS-AP, AS17645:AS-NTTS-GIN, AS23649:AS-STANLEY-CUSTOMERS, AS23947:AS-GLOBAL, AS2914:AS-64600, AS2914:AS-64601, AS2914:AS-64602, AS2914:AS-64603, AS2914:AS-64604, AS2914:AS-64605, AS2914:AS-64606, AS2914:AS-64607, AS2914:AS-64696, AS2914:AS-64697, AS2914:AS-64951, AS2914:AS-65001, AS38040:AS-PEERS, AS38193:AS-PEERS, AS4641:AS-CUHK-TRANSIT, AS721:AS-JAPAN, AS7713:AS-TELKOM-TRANSIT, AS9498:AS-BHARTI-IN, AS4611, AS6447, AS9229, AS9420, AS9765, AS9808, AS10030, AS10031, AS10146, AS17924, AS23693, AS24334, AS29457, AS38757, AS38819, AS41625, AS45182, AS45422, AS45960, AS56180, AS-NHN admin-c: NCGE-VRIO tech-c: NCGE-VRIO remarks: contacts per RFC2142: remarks: Abuse / UCE reports abuse@ntt.net remarks: Security issues security@ntt.net NTT MSC Sdn Bhd mnt-by: MAINT-NTTCOM-BB changed: mivatury@us.ntt.net 20110419 source: NTTCOM

AS-38322

NB: AS-SET

AS_Number Ie, no downstream customers Mnt-By Account

Who are MEMBERS of AS-38322?

Note: Members whois -h rr.ntt.net as-38322 As-set: AS-38322 Descr: Packet-Hub 159 Jalan Templer, Members:AS38322, AS23678, AS45785, AS17736

What Route-Object have they registered?

Ipv4 Route-Objects: whois -h rr.ntt.net -i origin 38322 | grep 'route:' route: 120.139.0.0/16 route: 120.140.0.0/15 route: 122.255.96.0/19 IPV6 Route-Objects: route: 120.140.0.0/18 route: 120.140.64.0/20 whois -h rr.ntt.net -i origin 38322 | grep 'route6:' route: 120.140.80.0/20 route6: 2401:3C00::/32 route: 120.141.16.0/20 route: 120.140.128.0/17 route: 120.141.128.0/17 route: 120.141.0.0/19 route: 120.141.32.0/20 NTT MSC Sdn Bhd

Putting it All Together

You will need:

Inetnum | Inet6num AS-Number An Account (MNTNER) on a Route Registry An AS-SET provided by the RR
(in some cases you may need to apply for it)

Route Objects ipv4 & ipv6 will need to be created Your ISP will place it under their AS-Set Tree Once this is done, and depending on how your ISP behaves, BGP Filters / Routes Maps will be build accordingly.
NTT MSC Sdn Bhd

Route Objects v4 & v6 Exchange/Mirrored

RR RADB RR NTT

RR APNIC

Daily Loads

Daily Loads AS2914

ASXXXX

AS2914
as-set: AS2914:AS-ASIA descr: NTT Asian Cu members: AS2914, AS3949, AS-00000, ASXXXX, ...

AS00000
As-set: AS-00000 Descr: I am AS00000 members: AS00000, members: AS-1111 members: ASXXXX

AS1111
as-set: AS-1111 descr: I am AS1111 members: AS1111, members: AS2222

AS2222

NTT MSC Sdn Bhd

Question?

How to create Route Objects v4 & v6? If Route Objects are created, how long will it take for the ISPs BGP Filters to build? What if my Route Objects are on third party Route Registries? Can my Route Objects / AS-SET & Members be made private? What does it mean when it is ProxyRegistered? Are there Best Practices?
NTT MSC Sdn Bhd