日本語版はこちら

Abstract

Is it THAT difficult to operate RPKI? This is not the case.

RPKI has started to spread as an approach to achieve higher routing security. The ratio of ROA-covered IP addresses delegated from JPNIC has continuously been rising. Route validation using ROAs by BGP routers (Route Origin Validation – ROV) is also spreading among international ISPs. While on the other hand, many ISPs (most likely those providing network connection to local areas) are reluctant to introducing RPKI; “Have no idea what exactly to do” or “Not welcome in the production environment”.

We provide a session that assists you to take the first step from zero to effective RPKI operation.

(1) RPKI technical summary – Intro “It actually is easy to publish a ROA” to ROV operation
(2) To take a step forward to RPKI – Promotion activities in various communities and what awaits after the first step

In section (1), we start with the overall topics such as RPKI coverage rate in recent years, then we summarise the actual flow to ROA publication. In addition, we also share what we have learnt from operating route validation with ROAs (ROV) i.e., ROA cache server configuration, what to do with Invalid routes, Full route operation, etc.

In section (2), we focus on our RPKI promotion activities in various communities – and the actual situations at local ISPs. We seek for insight into what is required for further RPKI promotion and the future consequences.

At the end of our session, we have a discussion time to consider what is required to exercise RPKI to the full extent. Main issues to discuss in this section are: “What to resolve before introducing RPKI”, What is required to introduce RPKI”, “How it went after introducing RPKI”.

Place

Mt.Fuji Hall

Date

Day2 Thursday, Jan 26th, 2023/10:00~11:15(1Hour 15Minutes)

Presenter

花井 直樹
一般社団法人日本ネットワークインフォメーションセンター

Naoki Hanai (JPNIC)

塩沢
一般社団法人日本ネットワークインフォメーションセンター

Hiromu Shiozawa (JPNIC)

山本 伸介
株式会社インターネットイニシアティブ

Shinsuke Yamamoto (Internet Initiative Japan Inc.)

中山
株式会社エディオン

Hisashi Nakayama (EDION Corporation)