1 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-10-0168-00-srho Title: DNS Based SFF Discovery Date Submitted: 2010-8-11 Authors or Source(s): Dapeng.

Slides:



Advertisements
Similar presentations
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Your Title Here Date Submitted: Month, NN, 200x Presented at IEEE.
Advertisements

IEEE MEDIA INDEPENDENT HANDOVER DCN: MuGM Title: Multicast Group Management TG Closing Note Date Submitted: May 15, 2012 Presented.
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: Merging Plan for Pull Key Distribution Date Submitted: Presented at IEEE Authors.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: PoA Capabilities of IE with IPv6 Prefix Availability Date Submitted: May 2006 Authors.
IEEE DCN: Title: Open SLMCP use case Date Submitted: January 10, 2015 IEEE session #66 in Atlanta, USA Authors or Source(s):
MuGM IEEE MEDIA INDEPENDENT HANDOVER DCN: MuGM Title: Definition of IEEE d multicast identifiers Date Submitted:
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: Policy concept in 3GPP ANDSF Date Submitted: June 30, 2010 Presented at IEEE c.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Instructions to get a Free IEEE Web Account Date Submitted: January.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Message Flow Date Submitted: March 1, 2011 Authors or Source(s): Fernando Bernal-Hidalgo,
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Problem Scenario Date Submitted: September, 2007 Presented at.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: FMCA MIH Work Item Date Submitted: March, 2009 Presented at IEEE.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Handover Initiation Strategy Consistency Date Submitted: November,
IEEE MEDIA INDEPENDENT HANDOVER DCN: SAUC-Handover-Use-Case Title: Handover Use Case Date Submitted: January 22, 2014 To.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: January 17, 2013 Presented at IEEE session.
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: IEEE c TG November 2012 Report and Agenda Date Submitted: November.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: Consideration for MGW discovery Date Submitted: July 18, 2012 Presented at IEEE.
IEEE MEDIA INDEPENDENT HANDOVER DCN: 100 Title: Cross Domain Trigger and Handover Talking Points Date Submitted: July 13, 2004.
IEEE DCN: SAUC Title: TG Closing Note Date Submitted: November 14, 2013 Presented at IEEE session #59 in Dallas, Texas,
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: MuGM
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE DCN: Title: TG Opening Note Date Submitted: November 09, 2015
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP Title: m Session #72 Closing Notes Date Submitted: January 21, 2016 IEEE session.
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE DCN: Title: TG Opening Note Date Submitted: Mar 09, 2015
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP Title: m Session #70 Opening Notes Date Submitted: September 14, 2015 IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Your Title Here
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: Missing Gaps Related with MGW Date Submitted: June 13, 2012 Presented at IEEE c.
IEEE MEDIA INDEPENDENT HANDOVER DCN: mugm
IEEE MEDIA INDEPENDENT HANDOVER
Presentation transcript:

1 IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: DNS Based SFF Discovery Date Submitted: Authors or Source(s): Dapeng Liu(China Mobile) Abstract: Discussion of DNS based SFF IP address discovery. 1

22 IEEE presentation release statements This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws and in Understanding Patent Issues During IEEE Standards Development Section 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/board/pat/faq.pdf

Background 1 、 DNS Resource Record A domain name identifies a node. Each node has a set of resource record which is the resource information associated with the particular name. 2 、 RR type A:a host address In DNS queries, the result of a query for a name may contain multiple IP addresses.

Question srho4 How to select an IP address from the RR which satisfies the two requirement: Provide basic load-balancing functionality among the hosts corresponding to the selected IP address. Assure that the selected IP address is the closest result.

Example For example,if we want to visit sina’s webserver,the return result is : You have eight type A records for the same DNS name. Each of your eight type A records has a separate address srho5

Solution DNS Round Robin is a mechanism for choosing an IP address from the list returned by a DNS server so that all clients won't get the same IP address every time. Netmask ordering is a mechanism for further optimizing which IP address is used by attempting to determine the closest result srho6

DNS Round Robin The order in which IP addresses from the list are returned is the basis for the term round robin. With each DNS response, the IP address sequence in the list is permuted. Usually, basic IP clients attempt connections with the first address returned from a DNS query so that on different connection attempts clients would receive service from different providers, thus distributing the overall load among servers srho7

Netmask Ordering we should use the longest match and not just pull the first IP address off the list. Longest match rule in destination address selection described in RFC 3484: Rule 9: Use longest matching prefix. When DA and DB belong to the same address family (both are IPv6 or both are IPv4): If CommonPrefixLen(DA, Source(DA)) > CommonPrefixLen(DB, Source(DB)), then prefer DA. Similarly, if CommonPrefixLen(DA, Source(DA)) < CommonPrefixLen(DB, Source(DB)), then prefer DB srho8

Example2: A client with an IP address of queries for Webserver.test.net and receives the following list: Webserver.test.net A Webserver.test.net A Webserver.test.net A Webserver.test.net A Webserver.test.net A With RFC3484 in effect, the client will always use the address as it is the longest match, negating the effects of DNS round-Robin srho9

Reference 1 、 、 、 archive/2009/04/17/dns-round-robin-and-destination-ip-address- selection.aspx 4 、 Computer Network(Fourth Edition) Andrew S.Tanenbaum srho10

11 Thanks!