MIH DT UPDATE

Telemaco Melia, Subir Das, Gabor Bajko,

Juan Carlos Zuniga, Nada Golmie, Sam Xia

draft-melia-mipshop-mstp-solution-01

Documents structure The main document:

draft-melia-mipshop-mstp-01 Defines the possible scenarios, what mechanism to

use to discover the MIH server and how to transport MIH data

Accompanying documents: DHCP based MoS discovery mechanism

draft-bajko-mos-dhcp-options-01 DNS based MoS discovery mechanism

draft-bajko-mos-dns-discovery-01 AAA extensions

…. yet to come

Deployment Scenarios (i) Scenario S1: Home Network MoS

In this scenario, the MN and the services are located in the home network.

MN SHOULD use the DNS based MoS discovery method Needs: domain name of its home

network.

+--------------+ +====+ | HOME NETWORK | |MoSh| +--------------+ +====+ /\ || \/ +--------+ | MN | +--------+

Deployment Scenarios (ii) Scenario S2: Visited Network MoS

In this scenario, the MN is in the visited network and mobility services are also provided by the visited network. We refer to this as MoSv.

MN SHOULD attempt to use the DHCP

options for MoS discovery. If the DHCP method fails, the MN SHOULD

attempt to use the DNS based MoS discovery method.

MN MUST first learn the domain name of the local network (DHCP, reverse DNS query).

+--------------+ | HOME NETWORK | +--------------+ /\ || \/ +====+ +-----------------+ |MoSv| | VISITED NETWORK | +====+ +-----------------+ /\ || \/ +--------+ | MN | +--------+

Deployment Scenarios (iii) Scenario S3: Roaming MoS

In this scenario, the MN is located in the visited network and all MIH services are provided by the home network.

both the DNS based discovery method and the DHCP based discovery method are applicable.

DNS based mechanism similar to Scenario 1 DCHP method follows in next slides…

+====+ +--------------+ |MoSh| | HOME NETWORK | +====+ +--------------+ /\ || \/ +-----------------+ | VISITED NETWORK | +-----------------+ /\ || \/ +--------+ | MN | +--------+

Deployment Scenarios (iii) - cont

MN roaming and discovering MoS in home network

Very similar to MIP6 bootstrapping integrated scenario

MN performs network access authentication with the home network, and the home AAA sends the MoS address to the NAS through the visited AAA

The MN uses DHCP options to learn the address of the MoS in the home network

The policy set in the home network will determine whether the MN gets an MoS @home or @local

The defined DHCP discovery supports both

Visited | Home | | +-------+ | +-------+ | | | | | |AAAV |-----------|--------|AAAH | | | | | | | | | | | +-------+ | +-------+ | | | | | | | | | | +--------+ | | | | | | | MoSh | +-----+ +------+ | +--------+ +----+ | | |DHCP | | | MN |------| NAS/|----|Server| | +----+ | DHCP| | | | |Relay| | | | +-----+ +------+ | | AAAv -- Visited AAA AAAH -- Home AAA NAS -- Network Access Server

Deployment Scenarios (iv)

Scenario S3: Roaming MoS

In this scenario, the MN is in its home network or in a visited network and services are provided by a 3rd party network.

+--------------+ | HOME NETWORK | +====+ +--------------+ +--------------+ |MoS3| | THIRD PARTY | <===> /\ +====+ +--------------+ || \/ +-----------------+ | VISITED NETWORK | +-----------------+ /\ || \/ +--------+ | MN | +--------+

•MN MUST use the DNS based MoS discovery method (upon learning the domain name of the target network)

Transport – General guidelines

MoS server MUST support both UDP and TCP for MIH transport (because both UDP and TCP can meet with the basic transport requirements for MoS, they are selected as default protocols), and the MN MAY support either UDP or TCP. Additionally, the server and MN MAY support additional transport mechanisms. (MN to use DNS based procedures to discover additional transport protocols supported by the server).

Since ES and CS messages are small in nature and have tight latency requirements, UDP in combination with MIH acknowledgement SHOULD be used for transporting ES and CS messages.

On the other hand, IS messages are more resilient in terms of latency constraints and some long IS messages could exceed the MTU of the path to the destination. Therefore, TCP SHOULD be used for transporting IS messages.

Other Considerations Security Considerations

DHCP: authentication option (RFC3118) DNS: DNS Security Extensions (RFC4033) TCP: TLS (Transport Layer Security) for message

confidentiality and data integrity (RFC4346) UDP: DTLS (RFC4347) IPsec

IANA Considerations I-D Registers TCP and UDP ports for MIH Transport If a port is not explicitly assigned, the default port

number MUST be used

An example

MNMIH USER

MIHF

TCP CLIENT

DHCP CLIENT DHCP

SERVER

MOS

MIH USER

MIHF

TCP CLIENT

MIH Discovery Request (MIH User to MIHF)

Invoke DHCP client(MoS)

DHCP INFORM

DHCP ACK

Inform MoS address

IS Query (MIH User to MIHF)

Invoke TCP client

TCP SESSION ESTABLISHED

MIH GET INFORMATION REQUEST

MIH GET INFORMATION RESPONSE

Internal MIH operation

IS Query confrim