distributed mobility for future internet rfc 7333, august ...mdoallo/descargas/distributed... ·...

Distributed Mobility for Future InternetInternet

H. Anthony ChanHuawei Technologies, Dallas

[email protected]

What I have is only borrowed from God so that I may serve others. H Anthony Chan October 24, 2014Distributed Mobility

References

♦ H. Chan, et al “Requirements of distributed mobility management,” Internet Engineering Task Force (IETF) g g g ( )RFC 7333, August 2014.

♦ H Anthony Chan, Hidetoshi Yokota, Jiang Xie, PierrickSeite, and Dapeng Liu, “Distributed and Dynamic Mobility Management in Mobile Internet: Current A h d I ” J l f C i tiApproaches and Issues,” Journal of Communications, vol. 6, no. 1, pp. 4-15, Feb 2011.

♦ H Anthony Chan “Proxy Mobile IP with Distributed♦ H. Anthony Chan, Proxy Mobile IP with Distributed Mobility Anchors,” Proceedings of GLOBECOM 2010 Workshop on Seamless Wireless Mobility Miami

What I have is only borrowed from God so that I may serve others. H Anthony Chan Page 2 October 24, 2014Distributed Mobility

Workshop on Seamless Wireless Mobility, Miami, USA, 6-10 December 2010.

Already in Internet

♦ Core network: converge (cellular and Internet – no more IPv4 blocks available)

3GPP

♦ Access networks: diverse 802.11

802.16 3GPP;3GPP2

Ethernet

OtherNets?Ethernet

♦ Devices: multiple interfaces, multiple functions, mobile

♦ Traffic from Wireless device grows 3 times faster than (exceeding soon) that of wireline devices(exceeding soon) that of wireline devices

♦ Internet lacks native support for wireless


♦ Internet lacks native support for wireless

Internet: ID-Locator split problem

ID-Locator Split networkProcess

IP networkProcess

Socket

Uses ID Transport

ID (of host)

Socket = IP addr + Port #

Transport (Port #)

Network (IP address of interface)

♦ IP address (of interface) changes h ti h T t

♦ ID (of host): Used for session, rarely h

Uses Locator Network (IP address)

when routing changes. Transport session does not survive under IP changes.

changes. ♦ Locator (IP address): Used for

network routing. ♦ Mapping system (control plane): maps♦ Mapping system (control plane): maps

ID with a set of locators (IP addr)


ID-Locator Split families

♦ Protocol stack (e.g. HIP)Application ApplicationTransport TransportTransport Transport

ID IDIP IP IP IPL2 L2 L2 L2

♦ Core edge separation: tunneling (e g LISP) or

L1 L1 L1 L1Source Router Router Destination

♦ Core-edge separation: tunneling (e.g. LISP) or translation

Application ApplicationTransport TransportTransport TransportIP(PIS,PID) IP(PIS,PID) IP(PAIR,PAER) IP(PAIR,PAER) IP(PIS,PID) IP(PIS,PID)

L2 L2 L2 L2 L2 L2L1 L1 L1 L1 L1 L1


Source Ingress router (IR) Egress router (ER) DestinationEDEG ROUTING CORE ROUTING EDGE ROUTING

Mobile IP

CDNserver

CDNserver

CDNserver

Home network Visited network

MN CNMN Move

mobile node

Process

correspondent node

SocketTransport

Session Identifier IP address before move


Session Identifier IP address before moveLocator (CoA) Current IP address

Proxy mobile IP (PMIP) with triangle routing problem

♦ Packets between MN and CN need to tunnel between MAG and LMA, even when MN is far from home network but is close to CN

Home networkwith LMA

Visited networkwith MAG

CDNserver

CDNserver

CDNserver

LMA: Local mobility anchor = Home agent (HA) + PMIP function= Home agent (HA) + PMIP function

MN: mobile nodeCN: correspondent node

MN CN


Distributed mobility management (DMM)

♦ IP mobility, network access and forwarding solutions provided by DMM MUST enable traffic to avoid p ytraversing single mobility anchor far from the optimal route.


Evolutionary trends in network architectures

♦ Mobile networks have generally been evolving towards a flatter and flatter network.

♦ Centralized mobility management, which is non-optimal with a flatter network architecture, does not support this evolution.

GMSC GGSN P-GWGSM GPRS/UMTS:WCDMA EPC:LTE next?

MSC

RNC

SGSN

RNC

S-GW P-GW/S-GW

?RNC

BS

RNC

BS BS BS


MN MN MN MN

What is the ID/Locator Split Protocol?

Client based / Client-network changes♦ Architectural change to the TCP/IP stack

A new layer between IP and transport

Network based: No change to client stack♦ Locator = globally routable IP addr in

backbone/Internet only♦ Session between Host IDs not affected by

locator changesMajor protocols/proposals:♦ HIP (Ericsson/HIIT)

♦ ID = edge network IP addr; session not affected by locator changes in Internet.

Major protocols:♦ LISP (Cisco);♦ HIP (Ericsson/HIIT)

♦ I3 (UC Berkeley)♦ Clean slate design (Stanford)♦ Internet 3.0 (WashU)

♦ LISP (Cisco); ♦ APT (UCLA)

Backbone/Transit Network

U L( )

ProcessProcess

Transport

ProcessProcess

T t

Before After Uses Locator

Edge network

Ingress router (IR)

Edge network

Egress router (ER)

TransportTransport Uses ID Uses ID

IP layerLocator (IP layer)

Host Identity


yLink layerLink layer

Source node (S)

Locator (IP layer) Destination node (D)

ID-Locator Split families

♦ Protocol stack (e.g. HIP)Application ApplicationTransport TransportTransport Transport

ID IDIP IP IP IPL2 L2 L2 L2

♦ Core edge separation: tunneling (e g LISP) or

L1 L1 L1 L1Source Router Router Destination

♦ Core-edge separation: tunneling (e.g. LISP) or translation

Application ApplicationTransport TransportTransport TransportIP(PIS,PID) IP(PIS,PID) IP(PAIR,PAER) IP(PAIR,PAER) IP(PIS,PID) IP(PIS,PID)

L2 L2 L2 L2 L2 L2L1 L1 L1 L1 L1 L1


Source Ingress router (IR) Egress router (ER) DestinationEDEG ROUTING CORE ROUTING EDGE ROUTING

Needs are diverse

♦ Mobility event Delay tolerance: wide range from very short to very longPacket loss tolerance: wide range from with to withoutPacket loss tolerance: wide range from with to without mechanism to recover lost packet.

M h i i ti it b id d t IP l♦ Many choices: session continuity can be provided at IP layer, L2, transport layer or application layer, or is not needed at all.

I♦ Issues Current mobility management protocols lack the intelligence to determine the need and to provide the appropriate

bilit t di t th dmobility management according to the needs.Current mobility management is either provided with short handover delay and little or no packet loss by default at net ork la er or is not pro ided at all


network layer or is not provided at all.

Diverse mobility events

♦ Heterogeneous networks (e.g., 3GPP to/from Wi-Fi) mobility events more common

♦ As network becomes dense or as small cells increase in number, and GW become closer to user, mobility from one EPC site to another becomes more frequentfrom one EPC site to another becomes more frequent.

♦ Large increase expected in stationary wireless nodes (e.g., sensors). ( g , )

♦ Issue Existing mobility protocols lacks capability to determine the need when both mobile and t ti d i l


stationary nodes are wireless.

Change of paradigm

♦ Mobility management is no longer a default one-size-fit-all support at the network layer. It involves many different but optional choices and may even need to be customized for each p yapplication of a subscriber/device.

♦ Issue♦ IssueOffering more choices in mobility management must not waste resources and add costs. In particular, keeping excessive states and tunneling are expensive. The future e cess e states a d tu e g a e e pe s e e utu eMM must drastically reduce in cost.

♦ Standards♦ StandardsNeed to be studied in standards bodies like IETF, 3GPP, NFV, ONFSome of above issues are already being studied at the IETF


Some of above issues are already being studied at the IETF distributed mobility management (DMM) wg.

IETF DMM WG

LM FM-CP

Mobile CoreInternet trafficOff-load

Data center

Access

FM-DP

Access

FM-DP FM-DP

Access

FM-DP

AccessNetwork

MN11

AccessNetwork

CN4

AccessNetwork

MN21MN11


MN11 CN4MN21MN11Move

Bypassable network-layer mobility support for each application session

♦ DMM solutions MUST enable network-layer mobility but it MUST be possible for any individual active application session (flow) to not use it.

♦ Mobility support is needed, for example, when a mobile host moves and an li ti t ith h i th IP dd M bilit t iapplication cannot cope with a change in the IP address. Mobility support is

also needed when a mobile router changes its IP address as it moves together with a host and, in the presence of ingress filtering, an application in the host is interrupted. However mobility support at the network-layer is not l d d bil d ft b t ti d bilit talways needed; a mobile node can often be stationary, and mobility support

can also be provided at other layers. It is then not always necessary to maintain a stable IP address or prefix for an active application session.

♦ Different active sessions can also differ in whether network-layer mobility y ysupport is needed. IP mobility, network access and forwarding solutions provided by DMM MUST then enable the possibility of independent handling for each application session of a user or mobile device.

♦ The handling of mobility management to the granularity of an individual♦ The handling of mobility management to the granularity of an individual session of a user/device SHOULD need proper session identification in addition to user/device identification.


Unified formulation of Internet mobility standards

3 basic functions

Existing network functions Mobility management needs

Forwarding Switch/router forwards packets more generalized ForwardingForwarding Switch/router forwards packets using appropriate routing information, e.g. in its routing table or from controller.

more generalized Forwarding Management (FM): which extendsexisting forwarding capabilityControl-data plane separation: FM-CP and FM-DP

Information processing

Manage information needed for routing, e.g., message

Location management (LM)may use database with client

exchanged between routers or passed from controller to switch, DNS.

(LMc) and server (LMs)

Identifier IP/L2 address is a routing address of interface. No separation between identifier and IP address

Managing to a granularity of an individual application session (flow) of a subscribe/device. Separate session identifier (SID) from


and IP address session identifier (SID) from routing address

Distributed mobility anchors-Architecture

FM: Forwarding mgntfunction (data plane)

Location Management function (control plane)

N t k b d MR i LM i t d b♦ Network-based: MR in every network, at GW which may move down

♦ LM is supported by distributed database

which may move down to AR in flat net

♦ Host-based: FM at host LM3LM2LM1♦ Host based: FM at host

LM

LM3LM2LM1

FM FM FM1 FM2 FM3


MN MN31MN MN32 MN11

Session continuity

♦ Session may continue when Session Identifier (original IP address) does not change.( g ) g

ProcessSocketSocket

TransportSession Identifier =original IP address of session

Locator (CoA) IP address


Decouple Session ID (SID) from forwarding address

♦ Tunneling: Session ID (Socket) coupled to old IP addrEnds of tunnel need FM even in data-plane (added cost)

L3 mobility management with tunneling SID includes old IPIP original IP original IP original IP

New IP of MN New IP of MN

♦ MPTCP: SID with multiple IP addresses (either new or old IP)

New IP of MN New IP of MNCN Forwarding Management MN+FM+LMc

♦ C S t u t p e add esses (e t e e o o d )MN needs LM to acquire new address when moving and needs FM to associate SID with multiple IP addresses (cost primarily at end points)p y p )

MPTCPSID SID includes new IPIP IP IP of MN IP of MN


♦ CN+FM Switch / Router MN+FM+LM

Decouple Session ID (SID) from forwarding address

♦ L2 mobility management: Session ID includes IP (no change)g )

No change to IP layer with its coupling to application (socket) in data-planeEnds of L2 path needs FM to associate IP with the proper L2 address.

L2 mobility management SID includes IPIP IP IP IP IP IP

L2(Ethernet) L2(Ethernet) L2 L2CN F di M t AR+FM+LM MN+FM+LMCN Forwarding Management AR+FM+LMc MN+FM+LMc


network- versus host-based

♦ Host-basedGlobal

L3 bilit t ith t liL3 mobility management with tunneling SID includes old IPIP original IP original IP original IP

New IP of MN New IP of MNCN Forwarding Management MN+FM+LMc

♦ Network-based: (To the network, AR for network-based MM is equivalent to MN in host-based MM)

CN Forwarding Management MN+FM+LMc

MM is equivalent to MN in host based MM)Local

L3 mobility management with tunneling SID includes old IPIP i i l IP i i l IP IP IP i i l IPIP original IP original IP IP IP original IP

IP of AR IP of ARL2 L2

CN Forwarding Management AR+FM+LMc MN


♦CN Forwarding Management AR+FM+LMc MN

Existing protocol: MIPv6

LI

Net1(P1::/) Net2(P2::/)Net3(P3::/)(a):(SID11 P31::mn11)

FMFM

SID11=MN{FM+LI}

(a)CN

SID11=P11::mn11,Move(a)

MN{FM+LI}

P11::mn11,

P31::mn11


Existing protocol: PMIPv6

LI(b):(SID12 P32::ar32)

Net1(P1::/) Net2(P2::/)Net3(P3::/)

FMFM

(b)

CNP32::ar32AR{FM+LI}

(b)

MNMN Move(b)(b)


SID12=P12::mn12

MNMN Move SID12=P12::mn12

MIPv6/PMIPv6

LI

(a):(SID11 P31::mn11)(b):(SID12 P32::ar32)

Net1(P1::/) Net2(P2::/)Net3(P3::/)

FMFM

(b)

SID11=MN{FM+LI}MN{FM+LI} CNMove

P32::ar32AR{FM+LI}(a)

(b)

(a)

SID11=P11::mn11,P11::mn11

MNMN Move(b)(b)

,P31::mn11


SID12=P12::mn12


Host-based versus Network-based mobility management

(a) Host-based mobility managementSID SID SID SID

IP of MN IP of MNIP of MN IP of MNCN Forwarding Management MN+FM+LIc

(b) Network-based mobility managementSID SID SID SID SID SID

IP of AR IP of ARIP of AR IP of ARL2 L2

CN Forwarding Management AR+FM+LIc MN


Hierarchical

LI

(a):(SID11 P31::fm3)(b):(SID12 P32::fm3)

Net1(P1::/) Net2(P2::/)Net3(P3::/)

FM FM+LI

(a):(SID11 P31::mn11)(b):(SID12 P32::ar32)FM

(b)

FM+LIP3::fm3



(b)

(a)

SID11P11::mn11

MNMN Move(b)(b)

P31::mn11


SID12=P12::mn12


Deploying MM in each network

LI LI LI

(a):(SID11 P31::fm3)(b):(SID12 P32::fm3)

Net1(P1::/) Net2(P2::/)Net3(P3::/)

FM FMFM+LI

(a):(SID11 P31::mn11)(b):(SID12 P32::ar32)FM FM

(b)

FM+LIP3::fm3



(b)

(a)

SID11P11::mn11

MNMN Move(b)(b)

P31::mn11


SID12=P12::mn12


Selective mobility supportwithout ongoing application requiring session continuity

LI LI LI

(a):(SID11 P31::fm3)(b):(SID12 P32::fm3)

Net1(P1::/) Net2(P2::/)Net3(P3::/)

FM FMFM+LI

(a):(SID11 P31::mn11)(b):(SID12 P32::ar32)FM FM

(b)

FM+LIP3::fm3



(b)

(a)

P11::mn11

MNMN

SID31=P31::mn11

Move(b)(b)


SID12=P12::mn12

MNMN

SID321=P321::mn12

Move

Selective mobility supportwith ongoing application requiring session continuity

LI LI LI

(a):(SID11 P31::fm3)(b):(SID12 P32::fm3)

Net1(P1::/) Net2(P2::/)Net3(P3::/)

FM FM

(a):(SID11 P31::mn11)(b):(SID12 P32::ar32)FM+LIFM FM

(b)

FM+LIP3::fm3



(b)

(a)

SID11P11::mn11

MNMN Move(b)(b)

P31::mn11


SID12=P12::mn12

MNMN Move SID12

Selective mobility support

LI LI LI

(a):(SID11 P31::fm3)(b):(SID12 P32::fm3)

Net1(P1::/) Net2(P2::/)Net3(P3::/)

FM FM


(b)

FM+LIP3::fm3

SID11=MN{FM+LI}MN{FM+LI} CN

SID11MoveP32::ar32AR{FM+LI}

(a)

(b)

(a)

P11::mn11

MNMN

SID31=P31::mn11

Move(b)(b)


SID12=P12::mn12

MNMNSID12SID321=P321::mn12

Move

Mobility Management Framework:Home network of application (where appl started)

LI LI LI

(a):(SID11 P31::fm3)(b):(SID12 P32::fm3)

Net1(P1::/) Net2(P2::/)Net3(P3::/)

FM FM


(b)

FM+LIP3::fm3

SID11=MN{FM+LI}MN{FM+LI} CN

SID11MoveP32::ar32AR{FM+LI}

(a)

(b)

(a)

P11::mn11

MNMN

SID31=P31::mn11

Move(b)(b)


SID12=P12::mn12

MNMNSID12SID321=P321::mn12

Move

Selective mobility management

LIs1

Net1 Net2Net3(SID11,P3::fm3)(SID12,P3::fm3)

LIs3 LIs2

FM1 FM3+LI FM2

AllocateP1::/64

AllocateP3::/64

AllocateP2::/64

1 t k t

(SID11,P31::mn11)(SID12,P32::ar32)FM1 FM3+LI FM21st packet P3::fm3

SID11=MN11+FM+LIcMN11

(a)CN21

SID11 SID21=MoveP32::ar32AR32+FM+LIc

P11::mn11

MN12MN12(b)

SID31=P31::mn11

SID21P21::cn21

Move


SID12=P12::mn12

MN12MN12SID12SID321=P321::mn12

Move

Copying LI info to all networks

LIs1+LIs2+LIs3


LIs3+LIs1+LIs2 LIs2+LIs3+LIs1

(SID11,P3::fm3)(SID12,P3::fm3)


FM1 FM2

AllocateP1::/64

AllocateP3::/64

AllocateP2::/64

FM3+LI

(SID11,P31::mn11)(SID12,P32::ar32)FM1 FM2P3::fm3FM3+LI


(a)

SID11MoveP32::ar32AR32+FM+LIc

SID21=MN21

P11::mn11

MN12MN12(b)

SID31=P31::mn11

Move

P21::mn21

MN22


SID12=P12::mn12


Move SID22=P22::mn22

MN22

Copying LI info to all networksbefore handover

LIs1+LIs2+LIs3

Net1 Net2Net3


FM1 FM2

AllocateP1::/64

AllocateP3::/64

AllocateP2::/64

FM3+LIFM1 FM2P3::fm3FM3+LI

SID11=MN11

(a) P32::ar32AR32+FM+LIc

SID21=MN21

P11::mn11

MN12(b)

P21::mn21

MN22


SID12=P12::mn12

MN12SID22=P22::mn22

MN22

Copying LI info to all networks

LIs1+LIs2+LIs3





FM1 FM2

AllocateP1::/64

AllocateP3::/64

AllocateP2::/64

FM3+LI

(SID11,P31::mn11)(SID12,P32::ar32)FM1 FM2P3::fm3FM3+LI


(a)

SID11MoveP32::ar32AR32+FM+LIc

SID21=MN21

P11::mn11

MN12MN12(b)

SID31=P31::mn11

Move

P21::mn21

MN22


SID12=P12::mn12


Move SID22=P22::mn22

MN22

DMM configuration

LI LI LI

(SID12 P30::fm3)Net1(P1::/) Net2(P2::/)Net3(P3::/,P12::/64)

FM FM+LI FMFM FM+LI FM

Red dotted route: Optimized route

Delegate prefixP12::/64

P l d h d t

P30::fm3

Black solid route: Direct routewith session SID32

Optimized routewith session SID12Purple dashed route:

Centralized mobilitywith session SID12

MNMN Move

with session SID32

CN


SID12=MNMN

SID12Move

SID32=P32::mn12P12::mn12

CN

DMM configuration (2)

LIs1 LIs3 LIs2

Net1(P1::/) Net2(P2::/)Net3(P3::/)

FM1 FM3+LIc FM2FM1 FM3+LIc FM2P30::fm3

MN12MN12 Move CN21


SID12=MN12MN12

SID12Move

SID32=P32::mn12P12::mn12

SID21=P21::cn21

CN21


LIs1 LIs3 LIs2

Net1(P1::/) Net2(P2::/)Net3(P3::/)


Black (solid) route: Direct routewith session SID32

MN12MN12 Move

with session SID32

CN21


SID12=MN12MN12

SID12Move

SID32=P32::mn12P12::mn12

SID21=P21::cn21

CN21


LIs1 LIs3 LIs2

(SID12,P30::fm3)Net1(P1::/) Net2(P2::/)Net3(P3::/)



Purple dashed route: Centralized mobilitywith session SID12

MN12MN12 Move

with session SID32

CN21


SID12=MN12MN12

SID12Move

SID32=P32::mn12P12::mn12

SID21=P21::cn21

CN21


LI LI LI





P l d h d t

P30::fm3


Centralized mobilitywith session SID12

MNMN Move CN


SID12=MNMN

SID12Move

SID32=P32::mn12P12::mn12

CN


LI LI LI




P30::fm3

Optimized routewith session SID12

MNMN Move CN


SID12=MNMN

SID12Move

SID32=P32::mn12P12::mn12

CN


LI LI LI

(SID12 P30::fm3)Net1(P1::/) Net2(P2::/)Net3(P3::/)

FM FM+LI FMFM FM+LI FMP30::fm3


MNMN Move CN

with session SID32


SID12=MNMN Move

SID32=P32::mn12P12::mn12

CN


LI LI LI

Net1(P1::/) Net2(P2::/)Net3(P3::/)

FM FM+LI FMFM FM+LI FMP30::fm3


MNMN Move CN

with session SID32


SID12=MNMN Move

SID32=P32::mn12P12::mn12

CN

Separate data plane and control plane

♦ Separate control and data planes

♦ Centralized control planep

Controller


DMM configurationwith CP-DP separation

LIs1 LIs3 LIs2(SID12,P3::fm3) Controller

Net1(P1::/) Net2(P2::/)Net3(P3::/,P12::/64)

FM1 CP FM3 CP+LIc FM2 CP(SID12,P32::mn12) (SID12,P3::fm3)

FM1-CP FM3-CP+LIc FM2-CP

FM1-DP FM3-DP FM2-DPP3 f 3


P3::fm3Red dotted route: Optimized routewith session SID12Purple dashed route:

I fli ht k t

MN12MN12 Move CN21


SIn-flight packetswith session SID12


SID12=MN12MN12

SID12Move

SID32=P32::mn12P12::mn12

SID21=P21::cn21

CN21

DMM configuration (9)with CP-DP separation

LI LI LI

ControllerNet1(P1::/) Net2(P2::/)Net3(P3::/,P12::/64)

FM CP FM CP+LI FM CPFM-CP FM-CP+LI FM-CP

FM-DP FM-DP FM-DPP3 f 3P3::fm3

MNMN Move CN


MNMN Move CNSID12SID32=P32::mn12

SID12=P12::mn12


LI LI LI

ControllerNet1(P1::/) Net2(P2::/)Net3(P3::/)



MNMN Move CN



SID12=MNMN Move

P12::mn12CN

SID12SID32=P32::mn12


LI LI LI(SID12 P3::fm3) Controller

Net1(P1::/) Net2(P2::/)Net3(P3::/,P12::/64)

FM CP FM CP+LI FM CP(SID12 P3::fm3)

FM-CP FM-CP+LI FM-CP

FM-DP FM-DP FM-DPP3 f 3

Delegate prefixP12::/64 Red dotted route:

Optimized routewith session SID12

P3::fm3

MNMN Move CN

S


SID12=MNMN Move

P12::mn12CN




Net1(P1::/) Net2(P2::/)Net3(P3::/,P12::/64)

FM CP FM CP+LI FM CP(SID12 P32::mn12) (SID12 P3::fm3)

FM-CP FM-CP+LI FM-CP

FM-DP FM-DP FM-DPP3 f 3

Delegate prefixP12::/64 Red dotted route:


I fli ht k t

P3::fm3

MNMN Move CN

SIn-flight packetswith session SID12


SID12=MNMN Move

P12::mn12CN




Net1(P1::/) Net2(P2::/)Net3(P3::/)



MNMN Move CN



SID12=MNMN Move

SID32=P32::mn12P12::mn12

CN


LI LI LI

ControllerNet1(P1::/) Net2(P2::/)Net3(P3::/)



MNMN Move CN



SID12=MNMN Move

SID32=P32::mn12P12::mn12

CN

Control plane – data plane separation

M bil CInternet traffic

LM FM-CP

Mobile CoreInternet trafficOff-load

Data center

AccessN t k

FM-DP

AccessN t k

FM-DP FM-DP

AccessN t k

FM-DP

Network

MN11

Network

CN4

Network

MN21MN11Move


Thank youy

H. Anthony ChanHuawei [email protected]

I do not posses anything. What I have is only borrowed


from God so that I may serve others

distributed mobility for future internet rfc 7333, august ...mdoallo/descargas/distributed... ·...

Documents