>>>>> On Mon, 23 Feb 2004 20:36:29 +0900, 
>>>>> "S. Daniel Park" <[EMAIL PROTECTED]> said:

>> I think there is no outstanding issue on this draft (except that we'll
>> need to remove the appendix with live examples before official
>> publication).  In this sense, this document should be ready for a wg
>> last call.

> I am not sure this draft is ready to go to the IESG, but I quite agree
> it
> is a valuable draft for us. 

Excuse me, but what do you mean by "not sure"?  (BTW: I didn't say
anything about the IESG.  I just mentioned (the possibility of) a wg
last call)

If you are making an objection to publishing the draft as an RFC,
please explicitly say so.  If you find a significant problem in the
draft that prevents the publication, please explicitly point it out.

Or, did you just mean you did not have any particular opinion on
whether this document should be published or not?

> One minor editorial;

> Current RFCs used " an AAAA RR ", perhaps all " a AAAA RR " in this
> draft 
> should be revised as wrote in RFCs.

Hmm, there is at least one counter example, RFC3338, which contains
the following sentence:

   If a server application you are using does not support IPv6 yet, but
   runs on a machine that supports other IPv6 services and this is
   listed with a AAAA record in the DNS, a client IPv4 application using
               ^^^^^^^^^^^^^
   BIA might fail to connect to the server application, because there is
   a mismatch between DNS query result (i.e., AAAA) and a server
   application version(i.e., IPv4).

For me, "a AAAA RR" looks more appropriate, because I would pronounce
the phrase as "a quad-A RR".  But I don't stick to this point, and if
there's a clear convention from RFC-editor's point of view, I'll
simply follow the convention.  For now, I'll leave the phrase as is.

Thanks anyway,

                                        JINMEI, Tatuya
                                        Communication Platform Lab.
                                        Corporate R&D Center, Toshiba Corp.
                                        [EMAIL PROTECTED]
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html

Reply via email to