ietf - eurecom

36
[email protected] http://www.thomasclausen.org IETF MANET, AUTOCONF, MANEMO

Upload: others

Post on 11-May-2022

11 views

Category:

Documents


0 download

TRANSCRIPT

Page 2: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Agenda

• A Bit of Background

• IETF Status

• MANET

• AUTOCONF

• The New Kid In Town

• MANEMO Background

• MANEMO Status

Page 3: IETF - EURECOM

[email protected] http://www.thomasclausen.org

MANET

~1997

~2002

~2004

Phase 0: Exploration

Phase 1: Experimental

Phase 2: Standardization

- OLSR (RFC3626), AODV (RFC3561)

- TBRPF (RFC3684), DSR (RFC4728)

- OLSRv2, DYMO

- SMF

~2007

Page 4: IETF - EURECOM

[email protected] http://www.thomasclausen.org

MANET

~1997

~2002

~2004

Phase 0: Exploration

Phase 1: Experimental

Phase 2: Standardization

- OLSR (RFC3626), AODV (RFC3561)

- TBRPF (RFC3684), DSR (RFC4728)

- OLSRv2, DYMO

- SMF

~2007

AUTOCONF

Phase 0: War of the Worlds

Phase 1: Architecture

Page 5: IETF - EURECOM

[email protected] http://www.thomasclausen.org

MANET

~1997

~2002

~2004

Phase 0: Exploration

Phase 1: Experimental

Phase 2: Standardization

- OLSR (RFC3626), AODV (RFC3561)

- TBRPF (RFC3684), DSR (RFC4728)

- OLSRv2, DYMO

- SMF

~2007

AUTOCONF

Phase 0: War of the Worlds

Phase 1: Architecture

MANEMO

Page 6: IETF - EURECOM

[email protected] http://www.thomasclausen.org

R + H

MANET interface

MANET "node"

IP address +

MANET Subnet Prefix

R + Hp::5

R +

Hp::2

R + Hp::1

R +

Hp::4

R + Hp::3

MANET with Subnet Prefix

p::

Individual MANET nodeswith addresses assigned

from and configured with prefix p::

Hp::1

Hp::3

Hp::2

Classic IP link withSubnet Prefix p::

R

Architectural Misperception

Page 7: IETF - EURECOM

[email protected] http://www.thomasclausen.org

MANET ArchitecturalModel

R

H

MANET interface

MANET "node"

Classic IP Linkswith classic H(osts)

H HH

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

MANET Interfaces &

Link Model

Classic IP

Link Model

R

HH H

192.168.1.0/24

192.168.1.1/24

192.168.1.2/24

192.168.1.3/24 192.168.1.4/24

192.168.1.5/24

H

192.168.1.1/32

Page 8: IETF - EURECOM

[email protected] http://www.thomasclausen.org

The MANET Interface

N1 N2

N1 N2 N3 N4 N5 N6N0

R

H

HH H

MANET Interface

Classic IP Link Model

MANET node

p::

p:1::

p:2::

p:2::1 p:2::2 p:2::n

5

4

1

2

3

5

4

1

2

3

Page 9: IETF - EURECOM

[email protected] http://www.thomasclausen.org

MANET

~1997

~2002

~2004

Phase 0: Exploration

Phase 1: Experimental

Phase 2: Standardization

- OLSR (RFC3626), AODV (RFC3561)

- TBRPF (RFC3684), DSR (RFC4728)

- OLSRv2, DYMO

- SMF

~2007

AUTOCONF

Phase 0: War of the Worlds

Phase 1: Architecture

MANEMO

Page 10: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Agenda

• A Bit of Background

• IETF Status

• MANET

• AUTOCONF

• The New Kid In Town

• MANEMO Background

• MANEMO Status

Page 11: IETF - EURECOM

[email protected] http://www.thomasclausen.org

MANET Goals

• ROUTING Area:

• Proactive Routing Protocol

• Reactive Routing Protocol

• Simple Multicast Framework

Page 12: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Generalized MANET Packet and Message

Format

Exchange formatSyntax only

NeighborHood Discovery Protocol

Bidirectionality checkLocal topology (1 & 2hop)Extensible via packetbb

OLSRv2

SMF

DYMO

...

MANET Building Blocks - Common elements MANET Routing Protocols

Workblock sequencing in MANET wg

(c) 2007, Thomas Heide Clausen, LIX, Ecole Polytechnique

Representing Multi Value

time in MANETs

Jitter Considerations

in MANETs

IANA Allocations in MANETs

Legend:

"Must be done before..."

Must be stabilized before progress can be made in MANET Routing Protocols

...

...

Page 13: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Agenda

• A Bit of Background

• IETF Status

• MANET

• AUTOCONF

• The New Kid In Town

• MANEMO Background

• MANEMO Status

Page 14: IETF - EURECOM

[email protected] http://www.thomasclausen.org

AUTOCONF Goals

• INTERNET Area

• MANET Architecture formalisation

• Initial prefix assignment

• Continued prefix uniqueness

Page 15: IETF - EURECOM

[email protected] http://www.thomasclausen.org

AUTOCONF Goals

• INTERNET Area

• MANET Architecture formalisation

• Initial prefix assignment

• Continued prefix uniqueness

In Progress

WGLC RSNProblemStatement

Page 16: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Agenda

• A Bit of Background

• IETF Status

• MANET

• AUTOCONF

• The New Kid In Town

• MANEMO Background

• MANEMO Status

Page 17: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Where did MANEMO come from?

MR

Internet

HHH

egress interface

ingress interface

Access Router

HomeAgent

H

AR

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

HR

IGW

Internet

Page 18: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Where did MANEMO come from?

MR

Internet

HHH

egress interface

ingress interface

Access Router

HomeAgent

H

AR

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

IGW

Internet

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

Page 19: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Where did MANEMO come from?

MR

Internet

HHH

egress interface

ingress interface

Access Router

HomeAgent

H

AR

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

IGW

Internet

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

Page 20: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Where did MANEMO come from?

MR

Internet

HHH

egress interface

ingress interface

Access Router

HomeAgent

H

AR

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

IGW

Internet

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

MR1

MR2

MR3

Page 21: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Where did MANEMO come from?

AR

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

IGW

Internet

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

MANET Interfaces &

Link Model

Classic IP

Link Model

NEMO

MANET

Page 22: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Where did MANEMO come from?

Configure MRs as MANET nodesRun MANET RP

MR4hp4::r:4:: q:4::

MR

5hp5::

r:5::

q:5

::

MR1hp1::r:1::

q:1::

MR

3hp3::

r:3:: q:3::

MR2hp2::r:2:: q:2::

IGWq::

IGWr::

Internet

AR

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

IGW

Internet

Page 23: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Where did MANEMO come from?

MR4hp4::r:4:: q:4::

MR

5hp5::

r:5::

q:5

::

MR1hp1::r:1::

q:1::

MR

3hp3::

r:3:: q:3::

MR2hp2::r:2:: q:2::

IGWq::

IGWr::

Internet

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

Sending RAs with ARs prefix &

off-link flag

Get "care-of" address from

ARs prefix

Send binding updates using

that prefix

AR

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

IGW

Internet

Page 24: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Where did MANEMO come from?

MR4hp4::r:4:: q:4::

MR

5hp5::

r:5::

q:5

::

MR1hp1::r:1::

q:1::

MR

3hp3::

r:3:: q:3::

MR2hp2::r:2:: q:2::

IGWq::

IGWr::

Internet

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

Sending RAs with ARs prefix &

off-link flag

Get "care-of" address from

ARs prefix

Send binding updates using

that prefix

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

AR

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

IGW

Internet

Page 25: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Where did MANEMO come from?

MR4hp4::r:4:: q:4::

MR

5hp5::

r:5::

q:5

::

MR1hp1::r:1::

q:1::

MR

3hp3::

r:3:: q:3::

MR2hp2::r:2:: q:2::

IGWq::

IGWr::

Internet

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

Sending RAs with ARs prefix &

off-link flag

Get "care-of" address from

ARs prefix

Send binding updates using

that prefix

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

MR1

MR2

MR3

AR

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

IGW

Internet

Page 26: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Where did MANEMO come from?

MR4hp4::r:4:: q:4::

MR

5hp5::

r:5::

q:5

::

MR1hp1::r:1::

q:1::

MR

3hp3::

r:3:: q:3::

MR2hp2::r:2:: q:2::

IGWq::

IGWr::

Internet

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

Sending RAs with ARs prefix &

off-link flag

Get "care-of" address from

ARs prefix

Send binding updates using

that prefix

Internet

MR1

HHH1

Access Router

HomeAgent1

H0

MR2

H2

HomeAgent2

MR1

MR2

MR3

MANEMOOriginal Thesis:“Manage Nested

Mobile Networks as MANETs”

AR

R

HH

H

H

R

H

H

H

H

R

H

H

H

H

R

HH

H

H

R

IGW

Internet

Page 27: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Manage Nested Mobile Networks as MANETs

MR4hp4::r:4:: q:4::

MR

5hp5::

r:5::

q:5

::

MR1hp1::r:1::

q:1::

MR

3hp3::

r:3:: q:3::

MR2hp2::r:2:: q:2::

IGWq::

IGWr::

Internet

HA2

MR2 @ r::

MR2 @ q::

MR4hp4::r:4:: q:4::

MR

5hp5::

r:5::

q:5

::

MR1hp1::r:1::

q:1::

MR

3hp3::

r:3:: q:3::

MR2hp2::r:2:: q:2::

IGWq::

IGWr::

Internet

Gateway Selection?

PathSelection?

Page 28: IETF - EURECOM

[email protected] http://www.thomasclausen.org

(MA)NEMO DOGMAs“Thou shall not run any

protocols other than MobileIP on either

interface of a Mobile Router”

“Thou shall not propagate topology on thy ingress interface”

MR1

MR2

MR3

MR4 AR

?

Page 29: IETF - EURECOM

[email protected] http://www.thomasclausen.org

(MA)NEMO DOGMAs“Thou shall not run any

protocols other than MobileIP on either

interface of a Mobile Router”

“Thou shall not propagate topology on thy ingress interface”

MR1

MR2

MR3

MR4 AR

?

BUMMER!

Page 30: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Agenda

• A Bit of Background

• IETF Status

• MANET

• AUTOCONF

• The New Kid In Town

• MANEMO Background

• MANEMO Status

Page 31: IETF - EURECOM

[email protected] http://www.thomasclausen.org

MANEMO Status?“Unfortunately, MANEMO is still not yet clearly defined and understood by IETF

community.”

“MANEMO may be just another configuration of MANET/AUTOCONF. The answer is still not clear..... “

“It depends on how you can see this MANEMO world in terms of addressing, wireless technology, topology formation, etc. You may approach the MANEMO

problem with existing solutions. However, existing solutions cannot cover whole idea of MANEMO. We believe there are also missing pieces for MANEMO in IETF. What

are the missing pieces?”

draft-wakikawa-manemoarch-00.txt

Page 32: IETF - EURECOM

[email protected] http://www.thomasclausen.org

So...MANEMO Status?

• Non-official meetings at 68th IETF:

• manet-centric vs. non-manet-centric views

• solution-space rather than problem-space

• 69th IETF and beyond?

Page 33: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Recent Contributions

• Understanding the topology & architecture

• draft-wakikawa-manemoarch-00.txt

• Understanding scenarios and deployments

• draft-mccarthy-manemo-configuration-problems-00.txt

• Then, understanding the (potential) solution space.

Page 34: IETF - EURECOM

[email protected] http://www.thomasclausen.org

MANET

~1997

~2002

~2004

Phase 0: Exploration

Phase 1: Experimental

Phase 2: Standardization

- OLSR (RFC3626), AODV (RFC3561)

- TBRPF (RFC3684), DSR (RFC4728)

- OLSRv2, DYMO

- SMF

~2007

AUTOCONF

Phase 0: War of the Worlds

Phase 1: Architecture

MANEMO

Phase 0:

Exploration

Phase 1:

WG formation

Phase 1:

Requirements

???

Page 35: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Conclusion(Or, a personal view)

• MANET/AUTOCONF offers:• architecture: routers + hosts• routers (can) run routing (& other) protocols• management of MANET interface characteristics

• MANEMO deployments • share many MANET characteristics• nesting problems solved MANET-centric• may have additional requirements

• Unified solution preferential.....

Page 36: IETF - EURECOM

[email protected] http://www.thomasclausen.org

Conclusion(Or, a personal view)

• MANET/AUTOCONF offers:• architecture: routers + hosts• routers (can) run routing (& other) protocols• management of MANET interface characteristics

• MANEMO deployments • share many MANET characteristics• nesting problems solved MANET-centric• may have additional requirements

• Unified solution preferential.....

Maybe the (MA)NEMO

DOGMA needs

revision?