The Experts below are selected from a list of 14670 Experts worldwide ranked by ideXlab platform
James Polk - One of the best experts on this subject based on the ideXlab platform.
-
dynamic Host Configuration protocol dhcp ipv4 and ipv6 option for a location uniform resource identifier uri
2013Co-Authors: James PolkAbstract:This document creates a Dynamic Host Configuration Protocol (DHCP) Option for transmitting a client's geolocation Uniform Resource Identifier (URI). This Location URI can then be dereferenced in a separate transaction by the client or sent to another entity and dereferenced to learn physically where the client is located, but only while valid.
-
discovering location to service translation lost servers using the dynamic Host Configuration protocol dhcp
RFC, 2008Co-Authors: Henning Schulzrinne, Hannes Tschofenig, James PolkAbstract:The Location-to-Service Translation Protocol (LoST) describes an XML- based protocol for mapping service identifiers and geospatial or civic location information to service contact Uniform Resource Locators (URLs). LoST servers can be located anywhere but a placement closer to the end Host, e.g., in the access network, is desireable. Such a LoST server placement provides benefits in disaster situations with intermittent network connectivity regarding the resiliency of emergency service communication. This document describes how a LoST client can discover a LoST server using the Dynamic Host Configuration Protocol (DHCP).
-
dynamic Host Configuration protocol dhcp option for a location by reference lbyr uniform resource identifier uri
2007Co-Authors: James PolkAbstract:This document creates a Dynamic Host Configuration Protocol (DHCP) Option for the Location-by-Reference (LbyR) Uniform Resource Identifier (URI) of an endpoint. For example, an endpoint can be a Session Initiation Protocol (SIP) User Agent (i.e., a phone). This LbyR URI can be included in a UA's messages to inform other nodes of that entity's geographic location, once the URI is dereferenced by a Location Recipient.
-
a dynamic Host Configuration protocol dhcp based location to service translation protocol lost discovery procedure
2006Co-Authors: Henning Schulzrinne, James Polk, Hannes TschofenigAbstract:The Location-to-Service Translation Protocol (LoST) describes an XML- based protocol for mapping service identifiers and geospatial or civic location information to service contact Uniform Resource Locators (URLs). LoST servers can be located anywhere but a placement closer to the end Host, e.g., in the access network, is desireable. Such a LoST server placement provides benefits in disaster situations with intermittent network connectivity regarding the resiliency of emergency service communication. This document describes how a LoST client can discover a LoST server using the Dynamic Host Configuration Protocol (DHCP).
-
A Dynamic Host Configuration Protocol Option for Requesting and Receiving a Uniform Resource Identifier
2006Co-Authors: James PolkAbstract:This document defines a new Dynamic Host Configuration Protocol (DHC) Option to deliver a Location-to-Service Translation (LoST) Protocol URI to a client. This SIP(S)-URI will be become the destination URI in any call set-up message to a Public Safety Answering Point (PSAP) in times of an emergency.
Bernie Volz - One of the best experts on this subject based on the ideXlab platform.
-
Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
2018Co-Authors: J. Bound, Ted Lemon, Bernie Volz, Charles E. Perkins, M. Carney, Ralph DromsAbstract:The Dynamic Host Configuration Protocol for IPv6 (DHCP) enables DHCP servers to pass Configuration parameters such as IPv6 network addresses to IPv6 nodes. It offers the capability of automatic allocation of reusable network addresses and additional Configuration flexibility. This protocol is a stateful counterpart to "IPv6 Stateless Address AutoConfiguration" (RFC 2462), and can be used separately or concurrently with the latter to obtain Configuration parameters.
-
Security of Messages Exchanged Between Servers and Relay Agents
2017Co-Authors: Yogendra Pal, Bernie VolzAbstract:The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has no guidance for how to secure messages exchanged between servers and relay agents. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) states that IPsec should be used to secure messages exchanged between servers and relay agents but does not require encryption. With recent concerns about pervasive monitoring and other attacks, it is appropriate to require securing relay-to-relay and relay-to-server communication for DHCPv6 and relay-to-server communication for DHCPv4.
-
Dynamic Host Configuration Protocol for IPv6 (DHCPv6) bis
2015Co-Authors: Ted Lemon, Sheng Jiang, Bernie Volz, Tomek Mrugalski, Andrew Yourtchenko, Marcin Siodelski, Michael RichardsonAbstract:The Dynamic Host Configuration Protocol for IPv6 (DHCP) enables DHCP servers to pass Configuration parameters such as IPv6 network addresses to IPv6 nodes. It offers the capability of automatic allocation of reusable network addresses and additional Configuration flexibility. This protocol is a stateful counterpart to "IPv6 Stateless Address AutoConfiguration" (RFC 2462), and can be used separately or concurrently with the latter to obtain Configuration parameters.
-
resolution of fully qualified domain name fqdn conflicts among dynamic Host Configuration protocol dhcp clients
RFC, 2006Co-Authors: Mark Stapp, Bernie VolzAbstract:The Dynamic Host Configuration Protocol (DHCP) provides a mechanism for Host Configuration that includes dynamic assignment of IP addresses and fully qualified domain names. To maintain accurate name- to-IP-address and IP-address-to-name mappings in the DNS, these dynamically assigned addresses and fully qualified domain names (FQDNs) require updates to the DNS. This document identifies situations in which conflicts in the use of fully qualified domain names may arise among DHCP clients and servers, and it describes a strategy for the use of the DHCID DNS resource record (RR) in resolving those conflicts. [STANDARDS-TRACK]
-
the dynamic Host Configuration protocol dhcp client fully qualified domain name fqdn option
RFC, 2006Co-Authors: Mark Stapp, Yakov Rekhter, Bernie VolzAbstract:This document describes a Dynamic Host Configuration Protocol for IPv4 (DHCPv4) option that can be used to exchange information about a DHCPv4 client's fully qualified domain name and about responsibility for updating the DNS RR related to the client's address assignment. [STANDARDS-TRACK]
Mark Stapp - One of the best experts on this subject based on the ideXlab platform.
-
The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption
2007Co-Authors: Kim Kinnear, Marie Normoyle, Mark StappAbstract:This memo defines a new suboption of the Dynamic Host Configuration Protocol (DHCP) relay agent information option that allows the DHCP relay to specify flags for the forwarded packet. One flag is defined to indicate whether the DHCP relay received the packet via a unicast or broadcast packet. This information may be used by the DHCP server to better serve clients based on whether their request was originally broadcast or unicast. [STANDARDS-TRACK]
-
resolution of fully qualified domain name fqdn conflicts among dynamic Host Configuration protocol dhcp clients
RFC, 2006Co-Authors: Mark Stapp, Bernie VolzAbstract:The Dynamic Host Configuration Protocol (DHCP) provides a mechanism for Host Configuration that includes dynamic assignment of IP addresses and fully qualified domain names. To maintain accurate name- to-IP-address and IP-address-to-name mappings in the DNS, these dynamically assigned addresses and fully qualified domain names (FQDNs) require updates to the DNS. This document identifies situations in which conflicts in the use of fully qualified domain names may arise among DHCP clients and servers, and it describes a strategy for the use of the DHCID DNS resource record (RR) in resolving those conflicts. [STANDARDS-TRACK]
-
the dynamic Host Configuration protocol dhcp client fully qualified domain name fqdn option
RFC, 2006Co-Authors: Mark Stapp, Yakov Rekhter, Bernie VolzAbstract:This document describes a Dynamic Host Configuration Protocol for IPv4 (DHCPv4) option that can be used to exchange information about a DHCPv4 client's fully qualified domain name and about responsibility for updating the DNS RR related to the client's address assignment. [STANDARDS-TRACK]
-
A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR)
2006Co-Authors: Mark Stapp, Ted Lemon, Andreas GustafssonAbstract:It is possible for Dynamic Host Configuration Protocol (DHCP) clients to attempt to update the same DNS Fully Qualified Domain Name (FQDN) or to update a DNS FQDN that has been added to the DNS for another purpose as they obtain DHCP leases. Whether the DHCP server or the clients themselves perform the DNS updates, conflicts can arise. To resolve such conflicts, RFC 4703 proposes storing client identifiers in the DNS to unambiguously associate domain names with the DHCP clients to which they refer. This memo defines a distinct Resource Record (RR) type for this purpose for use by DHCP clients and servers: the "DHCID" RR. [STANDARDS-TRACK]
-
vendor specific information suboption for the dynamic Host Configuration protocol dhcp relay agent option
RFC, 2005Co-Authors: Theyn Palaniappan, Richard Johnson, Mark StappAbstract:This memo defines a new Vendor-Specific Information suboption for the Dynamic Host Configuration Protocol's (DHCP) relay agent information option. The suboption allows a DHCP relay agent to include vendor-specific information in the DHCP messages it forwards, as configured by its administrator. [STANDARDS-TRACK]
Ralph Droms - One of the best experts on this subject based on the ideXlab platform.
-
Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
2018Co-Authors: J. Bound, Ted Lemon, Bernie Volz, Charles E. Perkins, M. Carney, Ralph DromsAbstract:The Dynamic Host Configuration Protocol for IPv6 (DHCP) enables DHCP servers to pass Configuration parameters such as IPv6 network addresses to IPv6 nodes. It offers the capability of automatic allocation of reusable network addresses and additional Configuration flexibility. This protocol is a stateful counterpart to "IPv6 Stateless Address AutoConfiguration" (RFC 2462), and can be used separately or concurrently with the latter to obtain Configuration parameters.
-
dhcp relay agent Configuration option
2010Co-Authors: Rajiv Asati, Ralph DromsAbstract:This document defines a Dynamic Host Configuration Protocol (DHCP) Relay Agent Configuration option and associated machinery to configure the Relay Agent.
-
Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6
2004Co-Authors: Ralph DromsAbstract:Stateless Dynamic Host Configuration Protocol service for IPv6 (DHCPv6) is used by nodes to obtain Configuration information, such as the addresses of DNS recursive name servers, that does not require the maintenance of any dynamic state for individual clients. A node that uses stateless DHCP must have obtained its IPv6 addresses through some other mechanism, typically stateless address autoConfiguration. This document explains which parts of RFC 3315 must be implemented in each of the different kinds of DHCP agents so that agent can support stateless DHCP.
-
unused dynamic Host Configuration protocol dhcp option codes
RFC, 2004Co-Authors: Ralph DromsAbstract:Prior to the publication of RFC 2489 (which was updated by RFC 2939), several option codes were assigned to proposed Dynamic Host Configuration Protocol (DHCP) options that were subsequently never used. This document lists those unused option codes and directs IANA to make these option codes available for assignment to other DHCP options in the future.
-
DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
2003Co-Authors: Ralph DromsAbstract:This document describes Dynamic Host Configuration Protocol for IPv6 (DHCPv6) options for passing a list of available DNS recursive name servers and a domain search list to a client.
Kuo-chih Chu - One of the best experts on this subject based on the ideXlab platform.
-
Networking without Dynamic Host Configuration Protocol server in Ethernet and Wireless Local Area Network
Journal of Network and Computer Applications, 2011Co-Authors: Tzu-chi Huang, Kuo-chih ChuAbstract:A Dynamic Host Configuration Protocol (DHCP) server is a well-known server deployed at a network to manage Internet Protocol (IP) addresses temporarily rentable to Hosts in the network. Besides, a DHCP server provides Hosts with important network information such as the subnet mask and the gateway IP address. However, a DHCP server has many drawbacks and should not be considered necessary in each network. If no DHCP server exists in a network to serve Hosts and no network administrator helps users manually configure the Hosts, currently no practical solution can make the Hosts access networks. In this paper, Automatic Host Configuration Mechanism (AHCM) is proposed to make a Host access Ethernet and Wireless Local Area Network (WLAN) without a DHCP server. AHCM can automatically locate IP addresses usable to Hosts and find network information in a transparent way without any user interference. Working like protocol software inside an Operating System (OS), AHCM has high compatibility because of neither modifying any application nor deploying a third party server in a network. Most importantly, AHCM does not have drawbacks in a DHCP server. AHCM is implemented in the protocol stack on Windows XP and tested in several experiments to identify its overheads and performances.