2009
DOI: 10.17487/rfc5679
|View full text |Cite
|
Sign up to set email alerts
|

Locating IEEE 802.21 Mobility Services Using DNS

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2009
2009
2012
2012

Publication Types

Select...
3
3
1

Relationship

1
6

Authors

Journals

citations
Cited by 7 publications
(5 citation statements)
references
References 6 publications
0
5
0
Order By: Relevance
“…MIH protocol messages are either sent at layer 2 or by using higher layer communication mechanisms [10,11,12,13].…”
Section: Fig 1 Media-independent Handover Frameworkmentioning
confidence: 99%
“…MIH protocol messages are either sent at layer 2 or by using higher layer communication mechanisms [10,11,12,13].…”
Section: Fig 1 Media-independent Handover Frameworkmentioning
confidence: 99%
“…Hence, the performance of this solution is dependent on the actual underlying protocol used to carry the MIH messages. Locating IEEE 802.21 mobility servers using DNS was introduced in [10]. The performance analysis using UDP and TCP was proposed in [11].…”
Section: Related Workmentioning
confidence: 99%
“…The client MUST try the records in the order listed, applying the mechanism described in [RFC5679] for each. The client only resolves the subsequent domain names if attempts to contact the first one failed or yielded no common transport protocols between the MN and the server.…”
Section: Mos Domain Name List Option For Dhcpv4mentioning
confidence: 99%
“…Regarding domain name resolution, it is recommended to consider the usage of DNSSEC [RFC4033] and the aspects of DNSSEC Operational Practices [RFC4641]. Security considerations described in [RFC5679] also apply.…”
Section: Security Considerationsmentioning
confidence: 99%