On 27 Jun, [EMAIL PROTECTED] wrote:
| A New Internet-Draft is available from the on-line Internet-Drafts
directories.
| This draft is a work item of the Domain Name System Operations Working Group
of the IETF.
|
| Title : DNS Response Size Issues
| Author(s) : P. Vixie, . Kato
| Filename : draft-ietf-dnsop-respsize-03.txt
| Pages : 10
| Date : 2006-6-27
==> I have read this version as I did for the previous ones. I keep
supporting this draft and I believe we should make it move forward.
This draft may be very useful for DNS operators managing zones with a
relatively large number of NS's and supporting IPv6 transport, such as
TLD operators.
Apart from sections numbering which is missing after section 5 (Perl
source code), I have one comment and one question (inline) on section 2.8:
> 2.8. The minimum useful number of address records is two, since giving
> only one address undermines the redundancy requirement. Implicit
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
==> When IPv6 transport is supported (presence of AAAA RRs), the
redundancy requirement is not necessarily fulfilled with 2 IP
addresses in the additional section. If both IP addresses are
associated with the same NS (for example one in v4 and the other in
v6) then there is a high probability that both of the become
unreachable if the NS encounters trouble (electricity outage, hardware
crash, DNS server stopped, ...). But in the same time, I presume that
the probability of getting in the additional section 2 IP addresses
associated with the same NS is quite low (assuming of course that the
total NS number is relatively large). So should we keep considering
that the "redundancy requirement" is fulfilled when/if the additional
section contains at least 2 IP addresses?
> truncation (truncation without setting TC bit) which occurs after two
> address records have been added to the additional data section is
> therefore less operationally significant than truncation which occurs
> earlier.
Regards,
Mohsen.
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
