Re: TCP response with truncated bit set?

[Mark Andrews <Mark_Andrews@isc.org>]

> >	It means that the answer would not fit into the buffer used to
> >	assemble the TCP response.  Note not all implementations use /
> >	have used 64k buffers.
> > 
> >	Mark
> 
> Presumably, even when both the client and authoritative server can handle 
> the RR Set, a caching server between them could introduce this behaviour?

	Yes.
 
> Is there any reasonable action a client can take in this case, or is 
> giving up the only option?

	Give up at this point.  There have been a number of proposals
	to extend TCP handling to support answers bigger than 64k.

	AXFR really should have been implemented this way rather
	than the way it was.  In other words we knew when the DNS
	was being designed that answers to certian queries would
	exceed 64k and we should have provided a mechanism to handle
	those cases in a standard way.
 
> Stuart Cheshire <cheshire@apple.com>
>  * Wizard Without Portfolio, Apple Computer, Inc.
>  * www.stuartcheshire.org
> 
> 
> --
> to unsubscribe send a message to namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>