Re: RFC2181 section 9.1: TC bit handling and additional data

[JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>]

[ Moderators note: Post was moderated, either because it was posted by
   a non-subscriber, or because it was over 20K.  
   With the massive amount of spam, it is easy to miss and therefore 
   delete relevant posts by non-subscribers. 
   Please fix your subscription addresses. ]

>>>>> On Wed, 29 Jun 2005 21:00:36 +0300 (EEST), 
>>>>> Pekka Savola <pekkas@netcore.fi> said:

> In the process of finalizing draft-ietf-dnsop-ipv6-issues-xx.txt, 
> we've had off-list discussion about TC bit handling when the 
> criticial/courtesy additional data section should include both A and 
> AAAA records.

> We would like to get some additional feedback especially on what's in 
> the implementations out there (the recommendations in the 
> specification seem clear enough).

> Specific questions (offlist responses are also fine):

Did you get sufficient information about these questions?  As far as I
know, there has been no public response on the list.  If there has
been no off-list response either, I'll try to answer the questions on
one implementation I know of a bit.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp


--
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/>