RFC 4085:Embedding Globally-Routable Internet Addr...
RFC-Ref

service


Click on the red underlined text to get to the source

... IP subnet prefixes. Thus, they are sometimes used as service identifiers, to which unsolicted requests are directed, or as subnet ...


... number of Internet hosts to rely on a single central Internet service. This can result in a service outage when the aggregate workload overwhelms that service ...
... Internet hosts to rely on a single central Internet service. This can result in a service outage when the aggregate workload overwhelms that service. When fixed addresses ...
... Internet service. This can result in a service outage when the aggregate workload overwhelms that service. When fixed addresses are embedded ...
... directly counter to the design intent of hierarchically deployed services that would otherwise be robust solutions. The reliability ...
... reliability, scalability, and performance of many Internet services require that the pool of users not access a service using its IP address ...
... scalability, and performance of many Internet services require that the pool of users not access a service using its IP address directly. Instead, they typically rely on a level of ...
... 6]. When appropriately utilized, the DNS permits the service operator to reconfigure the resources for maintenance and to perform load balancing, without the participation of the users and without a ...
... IP address or block has been reassigned and no longer hosts the service for which that traffic was intended. Circa 1997, the authors of RFC 2101 ...
... IP address reuse, RFC 2050 [1], encourages Internet Service Providers (ISPs) to treat address ...


... Use Domain Names as Service Identifiers ...
... hosts should use the Domain Name System to determine the IP addresses associated with the Internet services they require. When using domain names ...
... When using domain names as service identifiers in the configurations of deployed Internet ...
... hosts, designers and vendors are encouraged to introduce service names. These names should be within a domain that they either control or are permitted to utilize by an agreement ...
... they either control or are permitted to utilize by an agreement with its operator (such as for public services provided by the Internet community). This is commonly done by introducing a service-specific ...
... its operator (such as for public services provided by the Internet community). This is commonly done by introducing a service-specific prefix to the domain name ...
... domain names enable ongoing maintenance and reconfiguration of the services for their client hosts and can aid in the ongoing measurement of service ...
... services for their client hosts and can aid in the ongoing measurement of service usage throughout the product's lifetime. ...
... vendor-specific domain naming conventions for a product's service identifiers is to utilize SRV resource records ...
... SRV records are a generic type of RR that uses a service-specific prefix in combination with a base domain name ...
... However, note that simply hard-coding DNS name service identifiers rather than IP addresses ...
... Discover and Utilize Local Services ...
... Service providers and enterprise network operators should advertise the identities of suitable local services ...
... Service providers and enterprise network operators should advertise the identities of suitable local services, such as NTP. Very often these services ...
... services, such as NTP. Very often these services exist, but the advertisement and automated configuration of their use is missing. For instance, the DHCP ...
... server to answer client queries for service identifiers. When local services ...
... service identifiers. When local services, including NTP, are available but not pervasively advertised using such common protocols, designers are more likely to deploy ad ...
... hoc initialization mechanisms that unnecessarily rely on central services. ...
... Avoid Mentioning the IP Addresses of Services ...
... Operators who provide public services on the global Internet, such as those in the NTP ...
... NTP community, should deprecate the explicit advertisement of the IP addresses of public services. These addresses are ephemeral. As such, their widespread citation in ...
... addresses are ephemeral. As such, their widespread citation in public service indexes interferes with the ability to reconfigure the service when necessary to address ...
... public service indexes interferes with the ability to reconfigure the service when necessary to address unexpected, increased traffic and ...


... Implementors of host services should avoid any kind of use of unique globally-routable IP addresses within a fixed configuration part of ...
... globally-routable IP addresses within a fixed configuration part of the service implementation. If there is a requirement for pre- configured state ...
... configured state, then care should be taken to use an appropriate service identifier and to use standard mechanisms for dynamically resolving the identifier ...
... identifiers should be alterable in the field through a conventional command and control interface for the service. ...


... Hamilton, M. and R. Wright, "Use of DNS Aliases for Network Services", BCP 17, RFC 2219, October 1997. ...
... Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV)", RFC 2782prop, February 2000. ...


... the University of Wisconsin, with the cooperation of NetGear, will build a new anycast time service that aims to mitigate the damage caused by the misbehavior of these flawed routers. ...



Google
Web
RFC-Ref