Ordering of Service Instance Name Components. RFC 6763 DNS-Based Service Discovery February 2013 Appendix B. Rationale for Using DNS as a Basis for Serviceĭiscovery. How do I access the web page called "Serviceĭiscovery"?. What printer-configuration web pages are there?. What web pages are being advertised from ?. Discovery of Browsing and Registration Domains (DomainĮnumeration). Selective Instance Enumeration (Subtypes). Service Instances with Multiple TXT Records. Rules for Values in DNS-SD Key/Value Pairs. Rules for Keys in DNS-SD Key/Value Pairs. DNS TXT Record Format Rules for Use in DNS-SD. General Format Rules for DNS TXT Records. Conventions and Terminology Used in This Document. RFC 6763 DNS-Based Service Discovery February 2013ġ. The Trust Legal Provisions and are provided without warranty asĬheshire & Krochmal Standards Track Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal
#ZERO CONFIGURATION NETWORKING PDF NOTES HOW TO#
Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained atĬopyright (c) 2013 IETF Trust and the persons identified as the Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. This mechanism is referred to as DNS-based Service Looking for that service, this mechanism allows clients to discoverĪ list of named instances of that desired service, using standardĭNS queries. That a client is looking for, and a domain in which the client is Structured to facilitate service discovery. This document specifies how DNS resource records are named and Internet Engineering Task Force (IETF) S.
0 kommentar(er)
