On Wed, 28 Apr 2004, JINMEI Tatuya / [ISO-2022-JP] [EMAIL PROTECTED]@C#:H wrote:
> >>>>> On Tue, 27 Apr 2004 17:26:23 +0300 (EEST),
> >>>>> Pekka Savola <[EMAIL PROTECTED]> said:
>
> > I've updated the text a bit, trying to make this clearer:
>
> > http://www.netcore.fi/pekkas/ietf/temp/draft-ietf-dnsop-ipv6-dns-issues-06pre-diff.html
> > http://www.netcore.fi/pekkas/ietf/temp/draft-ietf-dnsop-ipv6-dns-issues-06pre.txt
>
> > Please see if these reflect to what you had in mind; I'm hoping of
> > submitting this within a day.
>
> From a quick check, I suspect you typed the keyboard too fast, because
> I could not understand the following part
>
> In other words, there are two kinds of additional data: the kind that
> must be included (all RRsets) no matter what (an example of this is
> below), and the kind which could be omitted in full or in part, but
> could cause nonoptimal results (an example of this is in the next
> section):
>
> child.example.com. IN NS ns.child.example.com.
> ns.child.example.com. IN A 192.0.2.1
> ns.child.example.com. IN AAAA 2001:db8::Y
>
> I'm even not sure if this is a complete set of paragraphs you intended
> to add...
Hmm. I can find no problems with this. What may be confusing is at
the end I said next _section_, not next paragraph, and the example I
quoted from you relates to the first case.
I tried to reword it for clarity:
=======
In other words, there are two kinds of additional data:
1. "critical" additional data; this must be included (all the
possible RRsets) in all scenarios, and
2. "courtesy" additional data; this could be sent in full, with only
a few RRsets, or with no RRsets, and can be fetched separately as
well.
An example of the latter are A/AAAA records in conjunction of MX
records as shown in the next section; an example of the former is
shown below:
child.example.com. IN NS ns.child.example.com.
ns.child.example.com. IN A 192.0.2.1
ns.child.example.com. IN AAAA 2001:db8::Y
In the case of too much additional data, [...]
=======
Is this better?
> Another minor nit:
>
> Additionally, to avoid the case where an application would not get an
> address at all due to non-critical additional data being omitted, the
> applications should be able to query the specific records of the
> desired protocol, not just rely getting all the required RRsets in
> the additional section.
>
> I guess "rely getting" should actually be "rely on getting".
Yep.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
