1 / 12

MIH DT UPDATE

MIH DT UPDATE. Telemaco Melia(ed), Gabor Bajko, Subir Das, Nada Golmie, Sam Xia, Juan Carlos Zuniga draft-melia-mipshop-mstp-solution-01. Documents structure. The main document: draft-melia-mipshop-mstp-01

audra-chambers
Download Presentation

MIH DT UPDATE

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MIH DT UPDATE Telemaco Melia(ed), Gabor Bajko, Subir Das, Nada Golmie, Sam Xia, Juan Carlos Zuniga draft-melia-mipshop-mstp-solution-01

  2. 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 • Version -01 includes the comments received from Yoshi, David, Srini, Gorry (processing the ID) • Accompanying documents: • DHCP based MoS discovery mechanism • draft-bajko-mos-dhcp-options-01 • Discovers MoS @home or @visited, based on home network policy • DNS based MoS discovery mechanism • draft-bajko-mos-dns-discovery-01 • Uses NAPTR and SRV records • AAA extensions • …. yet to come

  3. 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.

  4. 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).

  5. 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…

  6. 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 policy set in the home network will determine whether the MN gets an MoS @home or @local • The defined DHCP discovery supports both

  7. 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. • MN MUST use the DNS based MoS discovery method (upon learning the domain name of the target network)

  8. Transport – General guidelines • MoS server MUST support both UDP and TCP for MIH transport, and the MN MUST support 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). • 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. • IS messages could exceed the MTU of the path to the destination. Therefore, TCP SHOULD be used for transporting IS messages.

  9. 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

  10. IS -- An example for IS discovery

  11. Backup

  12. Transport --considerations • MIH message size • a typical MIH message size for the ES/CS service ranges between 50 to100 bytes • a typical MIH message size for IS is around 65000 bytes (for an IS MIH_Get_Information response primitive) • MIH message rate • CS/ES message arrive at a rate of one in hundreds of milliseconds • IS messages are exchanged mainly every time a new network is visited which may be in order of hours or days • Retransmission • TCP back off mechanisms increase with packet loss • If UDP is used MIH should use MIH ACKs • Appealing for ES/CS • NAT traversal • No known issues with TCP • Well known issues with UDP • MIH messages (e.g. ES) as keep alive messages • As [RFC4787] requires a minimum state timeout of two minutes or more, MIH messages using UDP as transport SHOULD be sent once every two minutes.

More Related