>>>>> On Mon, 9 May 2005 10:56:35 -0400,
>>>>> Brian Haberman <[EMAIL PROTECTED]> said:
> A refreshed version of the ICMP Name Lookups draft is available.
> I would especially like WG members who have implementations to
> review the draft and point out discrepancies between the spec and
> their code (e.g. unimplemented features).
Thanks for your effort of revising the document. I've reviewed the
latest draft, and have some comments. (I must confess in advance that
I don't fully remember the past discussions on this document, and that
I may be repeating points already discussed before.)
Regarding discrepancy with our (KAME/BSD) implementation, whereas I've
not done "line-by-line" checks between the spec and the implementation,
it seems the implementation supports all the features described in the
latest draft type/code/Qtype-wise.
However,
- our implementation currently does NOT delay the response to an
anycasted or multicasted query.
- it does NOT support the proxy responder service.
- it still supports the "Supported Qtypes" Qtype which is now marked
as "unused" (as far as I know this is just because we've not fully
followed recent changes of the spec).
Other general comments follow:
1. In section 2, this document is too specific about particular
implementations:
[...] An example of a IPv6 debugging tool using IPv6 Node
Information Queries is the ping6 program in the KAME, USAGI, and
other IPv6 implementations <http://www.kame.net>.
I'm afraid this is not very appropriate for a general specification
document. Instead, we might say:
[...] An example of an IPv6 debugging tool using IPv6 Node
Information Queries is the ping6 program in some platforms.
2. it seems to me that the notion of "proxy" is suddenly introduced in
Section 5. I think it should be clearly defined beforehand, e.g.,
in Section 3.
3. In Section 3, the draft reads:
The Query concerns a "Subject Address" (which may
differ from the Queried Address) or a "Subject Name".
We may also want to note that the Subject Address is not even an
IPv6 address (i.e., it can be an IPv4 address).
4. I'm afraid the reference to the MD5 spec (RFC1321) in Section 5
should be a normative reference in this context. (If
icmp-name-lookups is expected to be published as a PS, this may
cause a problem since RFC1321 is informational.)
5. I don't see why we need the TTL field for Node Name, Node
Addresses, and IPv4 Addresses if it MUST be always 0. Perhaps this
is just for backward compatibility to existing implementations,
though...(if so, I believe we should explicitly note that, since
otherwise future readers will have the same question)
6. In section 5, the draft reads:
[...] If the
Queried Address was anycast or multicast, the source address for the
Reply SHOULD be one belonging to the interface on which the Query was
received.
I don't see the strong reason in this case for choosing the source
address on the receiving interface. If we need to give guidance
about the source address in these cases, I think we can (or even
should) just refer to RFC3484.
7. Should we still need the "S" and "C" flags for the Node Addresses
Query even though site-local unicast addresses and IPv4-compatible
IPv6 addresses are now deprecated?
8. RFC2535 (DNSSEC) was updated by RFC4033-4035. We may want to
update the reference as well.
And here are some editorial comments:
(throughout the document)
"a NI" should be "an NI"? (depending on how we pronounce the acronym,
of course).
(section 2)
[...] An example of a IPv6 debugging tool using IPv6 Node
=> An example of an IPv6 debugging tool...
(section 5)
Providing the infrastructure to authenticate NI Queries and Replies
may be quote difficult outside of a well-defined community.
=>
... may be quite difficult(?)
(section 6.3)
[...] The Reply Data is a sequence of 128-bit IPv6
addresses, each address preceded by separate a 32-bit TTL value, with
=> ... by a separate 32-bit TTL value (?)
(section 7)
The IANA is requested to assign the IPv6 multicast prefix FF02:0:0:0:
0:2::/96 for use in Node Information Queries as defined in section
Section 5.
=> ... in Section 5.
(i.e., remove the redundant "section")
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------