Authoritative Server

14,000,000 Leading Edge Experts on the ideXlab platform

Scan Science and Technology

Contact Leading Edge Experts & Companies

Scan Science and Technology

Contact Leading Edge Experts & Companies

The Experts below are selected from a list of 435 Experts worldwide ranked by ideXlab platform

Francetelecom Orange - One of the best experts on this subject based on the ideXlab platform.

  • DHC Internet-Draft Intended status: Standards Track
    2013
    Co-Authors: D. Migault, Francetelecom Orange, W. Cloetens, C. Griffiths, R. Weber
    Abstract:

    DHCP DNS Public Authoritative Server Option draft-mglt-dhc-public-Authoritative-Server-option-00.txt The home network naming architecture as described in [I-D.mglt-homenet-front-end-naming-delegation] requires a complex naming configuration on the CPE. This configuration MAY not be handled easily by the average end user. Furthermore, such misconfiguration MAY result in making home network unreachable. This document proposes a DHCP option that provides the CPE all necessary parameters to set up the home network naming architecture. First, this DHCP option provides automatic configuration and avoids most end users ’ misconfigurations. Most average end users may not require specific configuration, and their ISP default configuration MAY fully address their needs. In that case, the naming homenet architecture configuration will be completely transparent to the end users. Then, saving naming configuration outside the CPE, makes it resilient to change of CPE or CPE upgrades. Such configuration may also be configured by the end user, via the customer area of their ISP

  • HOMENET Internet-Draft Intended status: Standards Track
    2013
    Co-Authors: D. Migault, Francetelecom Orange, W. Cloetens, C. Griffiths, R. Weber
    Abstract:

    DHCP DNS Public Authoritative Server Options draft-mglt-homenet-naming-architecture-dhc-options-00.txt The home network naming architecture as described in [I-D.mglt-homenet-front-end-naming-delegation] requires a complex naming configuration on the CPE. This configuration MAY not be handled easily by the average end user. Furthermore, such misconfiguration MAY result in making home network unreachable. This document proposes a DHCP options that provide the CPE all necessary parameters to set up the home network naming architecture. First, this DHCP options provide automatic configuration and avoid most end users ’ misconfiguration. Most average end users may not require specific configuration, and their ISP default configuration MAY fully address their needs. In that case, the naming homenet architecture configuration will be completely transparent to the end users. Then, saving naming configuration outside the CPE, makes it resilient to change of CPE or CPE upgrades. Such configuration may also be configured by the end user, via the customer area of their ISP

  • IPv6 Home Network Naming Delegation Architecture", draft-mglt-naming-delegation-00
    2012
    Co-Authors: W. Cloetens, D. Migault, P. Lemordant, Francetelecom Orange
    Abstract:

    draft-mglt-naming-delegation-00.txt This document describes the Naming Delegation Architecture that makes IPv6 Home Network globally reachable with Names or Fully Qualified Domain Names (FQDN). In this architecture, the Customer Premise Equipment (CPE) acts as the DNS Authoritative Server of the Home Network also called the Delegated DNS Server. The Naming Delegation is configured between the Delegated DNS Server and the Delegating DNS Server managed by the ISP. The use case considered in this document is an End User that subscribes its ISP a specific Delegated Domain for its Home Network. This document describes how the CPE automatically sets the Naming Delegation between the Delegating and Delegated DNS Server. The Naming Delegation is requested by the CPE. The CPE DHCP Client and the ISP DHCP Server exchange DHCP Options to properly set th

  • IPv6 Home Network Naming Delegation Architecture", Internet-Draft draft-mglt-homenet-naming-delegation-00
    2012
    Co-Authors: W. Cloetens, D. Migault, P. Lemordant, Francetelecom Orange
    Abstract:

    draft-mglt-homenet-naming-delegation-00.txt This document describes the Naming Delegation Architecture that makes IPv6 Home Network globally reachable with Names or Fully Qualified Domain Names (FQDN). In this architecture, the Customer Premise Equipment (CPE) acts as the DNS Authoritative Server of the Home Network also called the Delegated DNS Server. The Naming Delegation is configured between the Delegated DNS Server and the Delegating DNS Server managed by the ISP. The use case considered in this document is an End User that subscribes its ISP a specific Delegated Domain for its Home Network. This document describes how the CPE automatically sets the Naming Delegation between the Delegating and Delegated DNS Server. The Naming Delegation is requested by the CPE. The CPE DHCP Client and the ISP DHCP Server exchange DHCP Options to properly set th

D. Migault - One of the best experts on this subject based on the ideXlab platform.

  • DHC Internet-Draft Intended status: Standards Track
    2013
    Co-Authors: D. Migault, Francetelecom Orange, W. Cloetens, C. Griffiths, R. Weber
    Abstract:

    DHCP DNS Public Authoritative Server Option draft-mglt-dhc-public-Authoritative-Server-option-00.txt The home network naming architecture as described in [I-D.mglt-homenet-front-end-naming-delegation] requires a complex naming configuration on the CPE. This configuration MAY not be handled easily by the average end user. Furthermore, such misconfiguration MAY result in making home network unreachable. This document proposes a DHCP option that provides the CPE all necessary parameters to set up the home network naming architecture. First, this DHCP option provides automatic configuration and avoids most end users ’ misconfigurations. Most average end users may not require specific configuration, and their ISP default configuration MAY fully address their needs. In that case, the naming homenet architecture configuration will be completely transparent to the end users. Then, saving naming configuration outside the CPE, makes it resilient to change of CPE or CPE upgrades. Such configuration may also be configured by the end user, via the customer area of their ISP

  • HOMENET Internet-Draft Intended status: Standards Track
    2013
    Co-Authors: D. Migault, Francetelecom Orange, W. Cloetens, C. Griffiths, R. Weber
    Abstract:

    DHCP DNS Public Authoritative Server Options draft-mglt-homenet-naming-architecture-dhc-options-00.txt The home network naming architecture as described in [I-D.mglt-homenet-front-end-naming-delegation] requires a complex naming configuration on the CPE. This configuration MAY not be handled easily by the average end user. Furthermore, such misconfiguration MAY result in making home network unreachable. This document proposes a DHCP options that provide the CPE all necessary parameters to set up the home network naming architecture. First, this DHCP options provide automatic configuration and avoid most end users ’ misconfiguration. Most average end users may not require specific configuration, and their ISP default configuration MAY fully address their needs. In that case, the naming homenet architecture configuration will be completely transparent to the end users. Then, saving naming configuration outside the CPE, makes it resilient to change of CPE or CPE upgrades. Such configuration may also be configured by the end user, via the customer area of their ISP

  • IPv6 Home Network Naming Delegation Architecture", draft-mglt-naming-delegation-00
    2012
    Co-Authors: W. Cloetens, D. Migault, P. Lemordant, Francetelecom Orange
    Abstract:

    draft-mglt-naming-delegation-00.txt This document describes the Naming Delegation Architecture that makes IPv6 Home Network globally reachable with Names or Fully Qualified Domain Names (FQDN). In this architecture, the Customer Premise Equipment (CPE) acts as the DNS Authoritative Server of the Home Network also called the Delegated DNS Server. The Naming Delegation is configured between the Delegated DNS Server and the Delegating DNS Server managed by the ISP. The use case considered in this document is an End User that subscribes its ISP a specific Delegated Domain for its Home Network. This document describes how the CPE automatically sets the Naming Delegation between the Delegating and Delegated DNS Server. The Naming Delegation is requested by the CPE. The CPE DHCP Client and the ISP DHCP Server exchange DHCP Options to properly set th

  • IPv6 Home Network Naming Delegation Architecture", Internet-Draft draft-mglt-homenet-naming-delegation-00
    2012
    Co-Authors: W. Cloetens, D. Migault, P. Lemordant, Francetelecom Orange
    Abstract:

    draft-mglt-homenet-naming-delegation-00.txt This document describes the Naming Delegation Architecture that makes IPv6 Home Network globally reachable with Names or Fully Qualified Domain Names (FQDN). In this architecture, the Customer Premise Equipment (CPE) acts as the DNS Authoritative Server of the Home Network also called the Delegated DNS Server. The Naming Delegation is configured between the Delegated DNS Server and the Delegating DNS Server managed by the ISP. The use case considered in this document is an End User that subscribes its ISP a specific Delegated Domain for its Home Network. This document describes how the CPE automatically sets the Naming Delegation between the Delegating and Delegated DNS Server. The Naming Delegation is requested by the CPE. The CPE DHCP Client and the ISP DHCP Server exchange DHCP Options to properly set th

W. Cloetens - One of the best experts on this subject based on the ideXlab platform.

  • DHC Internet-Draft Intended status: Standards Track
    2013
    Co-Authors: D. Migault, Francetelecom Orange, W. Cloetens, C. Griffiths, R. Weber
    Abstract:

    DHCP DNS Public Authoritative Server Option draft-mglt-dhc-public-Authoritative-Server-option-00.txt The home network naming architecture as described in [I-D.mglt-homenet-front-end-naming-delegation] requires a complex naming configuration on the CPE. This configuration MAY not be handled easily by the average end user. Furthermore, such misconfiguration MAY result in making home network unreachable. This document proposes a DHCP option that provides the CPE all necessary parameters to set up the home network naming architecture. First, this DHCP option provides automatic configuration and avoids most end users ’ misconfigurations. Most average end users may not require specific configuration, and their ISP default configuration MAY fully address their needs. In that case, the naming homenet architecture configuration will be completely transparent to the end users. Then, saving naming configuration outside the CPE, makes it resilient to change of CPE or CPE upgrades. Such configuration may also be configured by the end user, via the customer area of their ISP

  • HOMENET Internet-Draft Intended status: Standards Track
    2013
    Co-Authors: D. Migault, Francetelecom Orange, W. Cloetens, C. Griffiths, R. Weber
    Abstract:

    DHCP DNS Public Authoritative Server Options draft-mglt-homenet-naming-architecture-dhc-options-00.txt The home network naming architecture as described in [I-D.mglt-homenet-front-end-naming-delegation] requires a complex naming configuration on the CPE. This configuration MAY not be handled easily by the average end user. Furthermore, such misconfiguration MAY result in making home network unreachable. This document proposes a DHCP options that provide the CPE all necessary parameters to set up the home network naming architecture. First, this DHCP options provide automatic configuration and avoid most end users ’ misconfiguration. Most average end users may not require specific configuration, and their ISP default configuration MAY fully address their needs. In that case, the naming homenet architecture configuration will be completely transparent to the end users. Then, saving naming configuration outside the CPE, makes it resilient to change of CPE or CPE upgrades. Such configuration may also be configured by the end user, via the customer area of their ISP

  • IPv6 Home Network Naming Delegation Architecture", draft-mglt-naming-delegation-00
    2012
    Co-Authors: W. Cloetens, D. Migault, P. Lemordant, Francetelecom Orange
    Abstract:

    draft-mglt-naming-delegation-00.txt This document describes the Naming Delegation Architecture that makes IPv6 Home Network globally reachable with Names or Fully Qualified Domain Names (FQDN). In this architecture, the Customer Premise Equipment (CPE) acts as the DNS Authoritative Server of the Home Network also called the Delegated DNS Server. The Naming Delegation is configured between the Delegated DNS Server and the Delegating DNS Server managed by the ISP. The use case considered in this document is an End User that subscribes its ISP a specific Delegated Domain for its Home Network. This document describes how the CPE automatically sets the Naming Delegation between the Delegating and Delegated DNS Server. The Naming Delegation is requested by the CPE. The CPE DHCP Client and the ISP DHCP Server exchange DHCP Options to properly set th

  • IPv6 Home Network Naming Delegation Architecture", Internet-Draft draft-mglt-homenet-naming-delegation-00
    2012
    Co-Authors: W. Cloetens, D. Migault, P. Lemordant, Francetelecom Orange
    Abstract:

    draft-mglt-homenet-naming-delegation-00.txt This document describes the Naming Delegation Architecture that makes IPv6 Home Network globally reachable with Names or Fully Qualified Domain Names (FQDN). In this architecture, the Customer Premise Equipment (CPE) acts as the DNS Authoritative Server of the Home Network also called the Delegated DNS Server. The Naming Delegation is configured between the Delegated DNS Server and the Delegating DNS Server managed by the ISP. The use case considered in this document is an End User that subscribes its ISP a specific Delegated Domain for its Home Network. This document describes how the CPE automatically sets the Naming Delegation between the Delegating and Delegated DNS Server. The Naming Delegation is requested by the CPE. The CPE DHCP Client and the ISP DHCP Server exchange DHCP Options to properly set th

R. Weber - One of the best experts on this subject based on the ideXlab platform.

  • DHC Internet-Draft Intended status: Standards Track
    2013
    Co-Authors: D. Migault, Francetelecom Orange, W. Cloetens, C. Griffiths, R. Weber
    Abstract:

    DHCP DNS Public Authoritative Server Option draft-mglt-dhc-public-Authoritative-Server-option-00.txt The home network naming architecture as described in [I-D.mglt-homenet-front-end-naming-delegation] requires a complex naming configuration on the CPE. This configuration MAY not be handled easily by the average end user. Furthermore, such misconfiguration MAY result in making home network unreachable. This document proposes a DHCP option that provides the CPE all necessary parameters to set up the home network naming architecture. First, this DHCP option provides automatic configuration and avoids most end users ’ misconfigurations. Most average end users may not require specific configuration, and their ISP default configuration MAY fully address their needs. In that case, the naming homenet architecture configuration will be completely transparent to the end users. Then, saving naming configuration outside the CPE, makes it resilient to change of CPE or CPE upgrades. Such configuration may also be configured by the end user, via the customer area of their ISP

  • HOMENET Internet-Draft Intended status: Standards Track
    2013
    Co-Authors: D. Migault, Francetelecom Orange, W. Cloetens, C. Griffiths, R. Weber
    Abstract:

    DHCP DNS Public Authoritative Server Options draft-mglt-homenet-naming-architecture-dhc-options-00.txt The home network naming architecture as described in [I-D.mglt-homenet-front-end-naming-delegation] requires a complex naming configuration on the CPE. This configuration MAY not be handled easily by the average end user. Furthermore, such misconfiguration MAY result in making home network unreachable. This document proposes a DHCP options that provide the CPE all necessary parameters to set up the home network naming architecture. First, this DHCP options provide automatic configuration and avoid most end users ’ misconfiguration. Most average end users may not require specific configuration, and their ISP default configuration MAY fully address their needs. In that case, the naming homenet architecture configuration will be completely transparent to the end users. Then, saving naming configuration outside the CPE, makes it resilient to change of CPE or CPE upgrades. Such configuration may also be configured by the end user, via the customer area of their ISP

Alexandre Gerber - One of the best experts on this subject based on the ideXlab platform.

  • cellular data network infrastructure characterization and implication on mobile content placement
    Measurement and Modeling of Computer Systems, 2011
    Co-Authors: Qiang Xu, Junxian Huang, Zhaoguang Wang, Feng Qian, Alexandre Gerber
    Abstract:

    Despite the tremendous growth in the cellular data network usage due to the popularity of smartphones, so far there is rather limited understanding of the network infrastructure of various cellular carriers. Understanding the infrastructure characteristics such as the network topology, routing design, address allocation, and DNS service configuration is essential for predicting, diagnosing, and improving cellular network services, as well as for delivering content to the growing population of mobile wireless users. In this work, we propose a novel approach for discovering cellular infrastructure by intelligently combining several data sources, i.e., Server logs from a popular location search application, active measurements results collected from smartphone users, DNS request logs from a DNS Authoritative Server, and publicly available routing updates. We perform the first comprehensive analysis to characterize the cellular data network infrastructure of four major cellular carriers within the U.S. in our study. We conclude among other previously little known results that the current routing of cellular data traffic is quite restricted, as it must traverse a rather limited number (i.e., 4-6) of infrastructure locations (i.e., GGSNs), which is in sharp contrast to wireline Internet traffic. We demonstrate how such findings have direct implications on important decisions such as mobile content placement and content Server selection. We observe that although the local DNS Server is a coarse-grained approximation on the user's network location, for some carriers, choosing content Servers based on the local DNS Server is accurate enough due to the restricted routing in cellular networks. Placing content Servers close to GGSNs can potentially reduce the end-to-end latency by more than 50% excluding the variability from air interface.

  • SIGMETRICS - Cellular data network infrastructure characterization and implication on mobile content placement
    Proceedings of the ACM SIGMETRICS joint international conference on Measurement and modeling of computer systems - SIGMETRICS '11, 2011
    Co-Authors: Junxian Huang, Zhaoguang Wang, Alexandre Gerber, Feng Qian, Zhuoqing Morley Mao
    Abstract:

    Despite the tremendous growth in the cellular data network usage due to the popularity of smartphones, so far there is rather limited understanding of the network infrastructure of various cellular carriers. Understanding the infrastructure characteristics such as the network topology, routing design, address allocation, and DNS service configuration is essential for predicting, diagnosing, and improving cellular network services, as well as for delivering content to the growing population of mobile wireless users. In this work, we propose a novel approach for discovering cellular infrastructure by intelligently combining several data sources, i.e., Server logs from a popular location search application, active measurements results collected from smartphone users, DNS request logs from a DNS Authoritative Server, and publicly available routing updates. We perform the first comprehensive analysis to characterize the cellular data network infrastructure of four major cellular carriers within the U.S. in our study. We conclude among other previously little known results that the current routing of cellular data traffic is quite restricted, as it must traverse a rather limited number (i.e., 4-6) of infrastructure locations (i.e., GGSNs), which is in sharp contrast to wireline Internet traffic. We demonstrate how such findings have direct implications on important decisions such as mobile content placement and content Server selection. We observe that although the local DNS Server is a coarse-grained approximation on the user's network location, for some carriers, choosing content Servers based on the local DNS Server is accurate enough due to the restricted routing in cellular networks. Placing content Servers close to GGSNs can potentially reduce the end-to-end latency by more than 50% excluding the variability from air interface.

  • Cellular data network infrastructure characterization and implication on mobile content placement
    2011
    Co-Authors: Feng Qian, Junxian Huang, Zhaoguang Wang, Alexandre Gerber, Morley Z. Mao
    Abstract:

    Despite the tremendous growth in the cellular data network usage due to the popularity of smartphones, so far there is rather limited understanding of the network infrastructure of various cellular carriers. Understanding the infrastructure characteristics such as the network topology, routing design, address allocation, and DNS service configuration is essential for predicting, diagnosing, and improving cellular network services, as well as for delivering content to the growing population of mobile wireless users. In this work, we propose a novel approach for discovering cellular infrastructure by intelligently combining several data sources, i.e., Server logs from a popular location search application, active measurements results collected from smartphone users, DNS request logs from a DNS Authoritative Server, and publicly available routing updates. We perform the first comprehensive analysis to characteriz