Router advertisements for routing between moving networks
Download
1 / 14

Router Advertisements for Routing between Moving Networks - PowerPoint PPT Presentation


  • 58 Views
  • Uploaded on

Router Advertisements for Routing between Moving Networks. draft-petrescu-autoconf-ra-based-routing-00.txt Presenter : Alexandru Petrescu IETF 78 Maastricht 26 July 2010, MEXT Working Group. Slide 1. Outline.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Router Advertisements for Routing between Moving Networks' - pennie


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Router advertisements for routing between moving networks

Router Advertisements for Routing between Moving Networks

draft-petrescu-autoconf-ra-based-routing-00.txt

Presenter: Alexandru Petrescu

IETF 78 Maastricht

26 July 2010, MEXT Working Group

Slide 1


Outline
Outline

  • Problems: MIP6 Route Optimization, and Vehicular-to-Vehicular communications in the absence of infrastructure

  • ICMPv6 extension

  • Topology and Message Exchange Diagrams

  • ConceptualAlgorithm on MR3; scalability

  • Differencesfromdraft-jhlee-mext-mnpp-00

  • Otherrecentremarks (from AUTOCONF, MEXT and private).

  • Implementation

Slide 2


Problems
Problems

  • Route OptimizationbetweenMoving Networks (typical):

  • Moving to Network to Moving Network when infrastructure is absent (e.g. vehicularformings: cars, wagons, convoy, tow)

HA1

HA2

Internet

MR1

MR2

LFN

LFN

?

MR1

MR2

LFN

LFN

Slide 3


Icmpv6 extension
ICMPv6 Extension

Router Advertisement is a message format defined in [RFC4861] as an

ICMPv6 message. The document [RFC5175] proposes an option for RA

extensibility: IPv6 Router Advetisement Flags Option. We propose to

reserve bit 16 for Mobile Network Prefixes.

0 1 2 3

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Type | Length |M| Bit fields available ...

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

... for assignment |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

'M' - Mobile Network Prefix present. Set to 1 if this Router

Advertisement contains a Mobile Network Prefix.

If the RA Flags Option contais the flag M, and set to 1, then the

Router Advertisement MUST contain a Route Information Option

[RFC4191] followed optionally by a Source-Link Layer Address Option

[RFC4861]. (If this SLLAO option is used then it avoids the

necessity of doing NS/NA exchange for the link-local address of the

Gateway entry in the data structure mentioned earlier.)

Slide 4


Topology and message exchange diagrams
Topology and Message Exchange Diagrams

WiFi

essid: “V2V”

channel: 3

mode: ad-hoc

egress

egress

egress

fe80::MR1_egress

fe80::MR3_egress

fe80::MR2_egress

Net3

Net2

Net1

MR1

MR3

MR2

fe80::MR1_ingress

fe80::MR3_ingress

fe80::MR2_ingress

WiFi

essid: “V3”

channel: 9

mode: managed

2001:db8:3::/64

WiFi

essid: “V2”

channel: 9

mode: managed

2001:db8:2::/64

2001:db8:1::/64

WiFi

essid: “V1”

channel: 9

mode: managed

eth0

eth0

eth0

LFN31

LFN21

LFN11

MR1

MR2

MR3

Simultaneous

MLD

“JOIN”

Phase 1

Simultaneous power-up

of 3 MRs.

RA1:

Phase 2

RA3:

RA2:

Slide 5


More message exchange diagrams
More Message Exchange Diagrams

MR1

MR2

MR3

MR1

MR2

MR3

Arrival of MR3 in a setting

of MR1 and MR2.

Timeout

RA1 used for deletion

MNP1, flag ‘D’, or lifetime ‘0’

Deletion

RS

Uponreceipt of this RA,

MR2 and 3 deletetheir

routes for MNP1 from

theirrouting tables.

RA1:

Renewal, eventually

RA2:

MR1

MR2

MR3

Timed out

expiration

and deletion.

RA3:

MLD “JOIN”

RS

RA1:

Explicit

deletion.

RA2:

Slide 6


Conceptually an algorithm on mr3
Conceptually – an Algorithmon MR3

(1)Send an RA containing the prefix(es) allocated to its subnets to which the ingress interfaces are connected

(2) "Join" the all-routers multicast address with link-scope, on its egress interface

(3) Send a Router Solicitation (RS) on its egress interface requesting RAs from MR1 and MR2

(4) Receive their special RAs: RA1 and RA2

(5) For each received RA, extract the source address and the prefixes and insert the corresponding number of routing table entries; these entries will help reach the LFNs in the moving networks of MR1 and MR2.

Slide 7


Scalability
Scalability

MRn

MR3

LFN11

LFN21

LFN1n

LFN2m

LFN12

LFN22

MR1

MR2

LFN11

LFN21

LFN1n

LFN2m

LFN12

LFN22

Routing table on MR1

Number of entries equals the

number of Mobile Routers

at the scene.

Routing table on LFN11

Number of entries

is constant.

Slide 8


Security
Security

  • Examplerisk: attacker MR claims towardsotherMRsthatitowns the MNP of a victim MR – victim MR no longer receivesitstraffic.

  • More threats.

  • Is SeNDappropriate.

  • Certificateswhen PKI infrastructure is absent.

  • Ongoingwork.

Slide 9


  • Additional scenarios: arrival of a router, deletion of entries (MNPP doesn’t);

  • Cases with or without Access Point (MNPP) – cases exclusivelywithout AP (thisdraft).

Slide 10


  • Deletion: how does MR know itwillleave?

  • Obscurelywrittenrt update

  • Format of RS message? (any extension?)

  • Security: thisintroduces more risksthan rfc3756; need to use certs.

  • Need of textdescribing use cases [Jong-Hyouk]

  • Bug in distinctor of prefixes (/64 instead of /24).

  • Use of distinctive ESSIDs on egress and ingress interfaces.

  • Use of link-local addresses (notation, pertinence)

  • How is MNP providedinitially?

  • Adapted to MEXT or AUTOCONF? [AUTOCONF member]

Slide 11


  • Wrong email address of a co-author

Slide 12


  • Extensions to ICMP Router Advertisements sent on the egress interface

  • Implementation on linux withradvd 1.4

  • PacketDissectors for Wireshark, for the packet formats

  • Link-layer security on egressusing WPA-NONE PSK TKIP/AES (yes, itissecure); and WEP toosome times.

Slide 13


  • Thanks in advance to the note takers!

Slide 14


ad