/contrib/bind9/doc/misc/rfc-compliance

https://bitbucket.org/freebsd/freebsd-head/ · #! · 62 lines · 53 code · 9 blank · 0 comment · 0 complexity · 9379fd42fb3b3a5653ffb5191e6f8656 MD5 · raw file 

    

  1. Copyright (C) 2004  Internet Systems Consortium, Inc. ("ISC")
    2. 

  2. Copyright (C) 2001  Internet Software Consortium.
    3. 

  3. See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
    4. 

  4. 

  5. $Id: rfc-compliance,v 1.4 2004/03/05 05:04:53 marka Exp $
    6. 

  6. 

  7. BIND 9 is striving for strict compliance with IETF standards.  We
    8. 

  8. believe this release of BIND 9 complies with the following RFCs, with
    9. 

  9. the caveats and exceptions listed in the numbered notes below.  Note
    10. 

  10. that a number of these RFCs do not have the status of Internet
    11. 

  11. standards but are proposed or draft standards, experimental RFCs, 
    12. 

  12. or Best Current Practice (BCP) documents.
    13. 

  13. 

  14.   RFC1034
    15. 

  15.   RFC1035 [1] [2]
    16. 

  16.   RFC1123
    17. 

  17.   RFC1183
    18. 

  18.   RFC1535
    19. 

  19.   RFC1536
    20. 

  20.   RFC1706
    21. 

  21.   RFC1712
    22. 

  22.   RFC1750
    23. 

  23.   RFC1876
    24. 

  24.   RFC1982
    25. 

  25.   RFC1995
    26. 

  26.   RFC1996
    27. 

  27.   RFC2136
    28. 

  28.   RFC2163
    29. 

  29.   RFC2181
    30. 

  30.   RFC2230
    31. 

  31.   RFC2308
    32. 

  32.   RFC2535 [3] [4]
    33. 

  33.   RFC2536
    34. 

  34.   RFC2537
    35. 

  35.   RFC2538
    36. 

  36.   RFC2539
    37. 

  37.   RFC2671
    38. 

  38.   RFC2672
    39. 

  39.   RFC2673
    40. 

  40.   RFC2782
    41. 

  41.   RFC2915
    42. 

  42.   RFC2930
    43. 

  43.   RFC2931 [5]
    44. 

  44.   RFC3007
    45. 

  45. 

  46. 

  47. [1] Queries to zones that have failed to load return SERVFAIL rather
    48. 

  48. than a non-authoritative response.  This is considered a feature.
    49. 

  49. 

  50. [2] CLASS ANY queries are not supported.  This is considered a feature.
    51. 

  51. 

  52. [3] Wildcard records are not supported in DNSSEC secure zones.
    53. 

  53. 

  54. [4] Servers authoritative for secure zones being resolved by BIND 9
    55. 

  55. must support EDNS0 (RFC2671), and must return all relevant SIGs and
    56. 

  56. NXTs in responses rather than relying on the resolving server to
    57. 

  57. perform separate queries for missing SIGs and NXTs.
    58. 

  58. 

  59. [5] When receiving a query signed with a SIG(0), the server will only
    60. 

  60. be able to verify the signature if it has the key in its local
    61. 

  61. authoritative data; it will not do recursion or validation to
    62. 

  62. retrieve unknown keys.
    63.