mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-30 22:15:20 +00:00
Code Issues Releases Wiki Activity

new draft

Browse Source
This commit is contained in:
Mark Andrews
2003-01-07 20:44:52 +00:00
parent 3d00f74888
commit 10d63f4cef
1 changed files with 33 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

56
doc/draft/draft-dnsext-opcode-discover-00.txt → doc/draft/draft-dnsext-opcode-discover-01.txt
View File

@@ -1,10 +1,11 @@
IETF DNSEXT WG Bill Manning IETF DNSEXT WG Bill Manning
draft-dnsext-opcode-discover-00.txt ISI draft-dnsext-opcode-discover-01.txt ISI
Paul Vixie Paul Vixie
ISC ISC
Erik Guttman Erik Guttman
SUN SUN
11 Apr 2002 21 Dec 2002
The DISCOVER opcode The DISCOVER opcode
@@ -36,7 +37,7 @@ The capitalized keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 document are to be interpreted as described in RFC 2119
Abstract: 0. Abstract:
The QUERY opcode in the DNS is designed for unicast. With the The QUERY opcode in the DNS is designed for unicast. With the
development of multicast capabilities in the DNS, it is desireable development of multicast capabilities in the DNS, it is desireable
@@ -51,7 +52,7 @@ Abstract:
was developed as part of the TBDS project, funded under DARPA grant was developed as part of the TBDS project, funded under DARPA grant
F30602-99-1-0523. F30602-99-1-0523.
Introduction: 1. Introduction:
This document describes an experimental extension to the DNS to receive This document describes an experimental extension to the DNS to receive
multiple responses which is the likely result when using DNS that has multiple responses which is the likely result when using DNS that has
@@ -60,7 +61,7 @@ Introduction:
full processing rules used by TBDS are documented here for possible full processing rules used by TBDS are documented here for possible
incorporation in a future revision of the DNS specification." incorporation in a future revision of the DNS specification."
Method: 2. Method:
DISCOVER works like QUERY except: DISCOVER works like QUERY except:
@@ -88,7 +89,7 @@ Method:
address of the requester and the source address should reflect address of the requester and the source address should reflect
the unicast address of the responder. the unicast address of the responder.
Example usage for gethostby{name,addr}-style requestors: Example usage for gethostby{name,addr}-style requestors:
Compute the zone name of the enclosing in-addr.arpa, ip6.int, or Compute the zone name of the enclosing in-addr.arpa, ip6.int, or
ip6.arpa domain. ip6.arpa domain.
@@ -118,7 +119,7 @@ Example usage for gethostby{name,addr}-style requestors:
Cache all NS and A data learned in this process, respecting TTL's. Cache all NS and A data learned in this process, respecting TTL's.
TBDS usage for SRV requestors: TBDS usage for SRV requestors:
Do the gethostbyaddr() and gethostbyname() on one's own link-local Do the gethostbyaddr() and gethostbyname() on one's own link-local
address, using the above process. address, using the above process.
@@ -173,22 +174,22 @@ TBDS usage for SRV requestors:
zone names which match QNAME's, not with zone names which are owned zone names which match QNAME's, not with zone names which are owned
by QNAME's. by QNAME's.
The only deviation from the DNS[3][4] model is that a host (like, say, a The only deviation from the DNS[3][4] model is that a host (like, say, a
printer offering LPD services) has a DNS server which answers authoritatively printer offering LPD services) has a DNS server which answers authoritatively
for something which hasn't been delegated to it. However, the only way that for something which hasn't been delegated to it. However, the only way that
such DNS servers can be discovered is with a new opcode, DISCOVER, which such DNS servers can be discovered is with a new opcode, DISCOVER, which
is explicitly defined to discover undelegated zones for tightly scoped is explicitly defined to discover undelegated zones for tightly scoped
purposes. Therefore this isn't officially a violation of DNS's coherency purposes. Therefore this isn't officially a violation of DNS's coherency
principles. principles. In some cases, a responder to DISCOVER, may not be traditional
DNS software, it could be special purpose software.
3. IANA Considerations
IANA Considerations
As a new opcode, the IANA will need to assign a numeric value As a new opcode, the IANA will need to assign a numeric value
for the memnonic. The last OPCODE assigned was "5", for UPDATE. for the memnonic. The last OPCODE assigned was "5", for UPDATE.
Test implementations have used OPCODE "6". Test implementations have used OPCODE "6".
Security Considerations 4. Security Considerations
No new security considerations are known to be introduced with a new No new security considerations are known to be introduced with a new
opcode, however using multicast for service discovery has the potential opcode, however using multicast for service discovery has the potential
@@ -229,8 +230,17 @@ Erik Guttman and Bill Manning were active contributors.
7. References 7. References
[1] draft-ietf-dnsext-mdns-00.txt Informational References:
[2] draft-manning-dnsext-mdns-00.txt
[3] RFC 1034 [1] Esibov, L., Aboba, B., Thaler, D., "Multicast DNS",
[4] RFC 1035 draft-ietf-dnsext-mdns-00.txt, November 2000. Expired
----------------------------------------------------------
[2] Woodcock, B., Manning, B., "Multicast Domain Name Service",
draft-manning-dnsext-mdns-00.txt, August 2000. Expired.
Normative References:
[3] Mockapetris, P., "DOMAIN NAMES - CONCEPTS AND FACILITIES",
RFC 1034, November 1987.
[4] Mockapetris, P., "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION",
RFC 1035, November 1987