The document discusses a proposed "Routing Resilience Manifesto" which aims to promote collective responsibility and collaboration among network operators to address issues of routing resilience and security. The manifesto would establish principles like interdependence, best practices, and guidelines for actions like filtering, anti-spoofing, and coordination. It is being drafted by a small group and the Internet Society would serve as a neutral platform to publish and promote the manifesto.

1. Collec&ve
responsibility
and
collabora&on
for
Rou&ng
Resilience
and
Security
aka
Rou&ng
Resilience
Manifesto
Update
robachevsky@isoc.org

2. Routing Resilience Manifesto
- Principles of addressing issues of routing resilience
- Interdependence and reciprocity (including collaboration)
- Commitment to Best Practices
- Encouragement of customers and peers
- Guidelines indicating the most important actions
- BGP Filtering
- Anti-spoofing
- Coordination and collaboration
- High-level document specifying “what”
- “How” is in external documents (e.g. BCPs)

3. Where
does
the
Manifesto
fit?
13
May
2014
3
BCPs,
BCOPs,
RFCs,
Opera&onal
documenta&on,
etc.
HOW?
WHAT
is
the
minimum
“PACKAGE”
and
WHO
supports
it?
Real-­‐life
examples,
threat
analysis,
community
aspira&ons
PROBLEM?
Manifesto

4. Objec&ves
• Raise awareness and encourage actions by
demonstrating commitment of the growing
group of supporters
• Demonstrate industry ability to address
complex issues
• Clear and tangible message:
“We do at least this and expect you to do the same”
13
May
2014
4

5. The
end
product
• Landing
page
• Published
document
• Growing
list
of
supporters
• Pointers
to
more
specific
informa&on,
e.g.
BCOPs
13
May
2014
5

6. Work
in
progress
• A
small
group
of
network
operators
draZing
text
• ISOC
as
a
neutral
plaorm
(convener
and
promoter)
• Following
slides
should
be
seen
as
an
illustra&on,
rather
then
fait
accompli
13
May
2014
6

7. Guidelines
–
3
requested
ac&ons
1. Prevent
propaga&on
of
incorrect
rou&ng
informa&on
2. Prevent
traffic
with
spoofed
source
IP
address
3. Facilitate
global
opera&onal
communica&on
and
coordina&on
between
the
network
operators
13
May
2014
7

8. Guidelines
–
requested
ac&ons
Prevent
propaga&on
of
incorrect
rou&ng
informa&on
- At least own and customer networks
- Prefix-based filtering
- Ability (and willingness) to communicate information
about correctness
13
May
2014
8

9. Guidelines
–
requested
ac&ons
Prevent
traffic
with
spoofed
source
IP
address
- At least single-homed stub customer networks
- Own end-users
- Own infrastructure.
- Ingress and Egress
13
May
2014
9

10. Guidelines
–
requested
ac&ons
Facilitate
global
opera&onal
communica&on
and
coordina&on
between
the
network
operators
Globally accessible up-to-date contact information.
13
May
2014
10

11. Next
steps
• Finalize
the
draZ
–
if
you
are
interested
find
me
in
the
hallway
• Solicit
wider
feedback
from
network
operators
• Create
a
webspace,
“founding
members”
• Launch
and
promote
13
May
2014
11

12. Ques&ons
• Is
this
needed,
useful?
• Is
this
the
right
direc&on?
• Is
something
missing?
– Overall
framework,
specific
guidelines?
• Are
you
interested
in
contribu&ng?
• Will
you
support
the
Manifesto?
13
May
2014
12

13. 13
May
2014
13
?
robachevsky@isoc.org