[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[DNA] comments on draft-ietf-dna-hosts-00
Hi,
Here are few comments and questions on host BCP document.
1. In Section 4.1,
".....When a host attaches itself to a new L2 link, if the
corresponding stored prefix list doesn't contain the prefix it is
using, the host SHOULD conclude that it has changed link and initiate
new configuration procedure. If the host finds the prefix it is
using in the stored list of prefixes, a host MAY conclude that it is
on the same link...."
I think here "SHOULD" and "MAY" need to be swapped. In section 4.3.1,
it is correctly mentioned as follows
".... A host SHOULD conclude that it is on the same link if any of the
following events happen.
Reception of a RA with a known prefix on the link...."
2. In section 4.5, in the table, for RS/multicast RA case, I think Upstream
is N and
Downstream is Y. Downstream is Y because we received multicast RA. We
are not
sure whether RS host sent was received by router or not amd hence
Upstream is N.
3. In section 4.2,
"... While hosts performing DNA do not know if they have arrived on a
new
link, they SHOULD treat their addresses as if they were. This means
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
that link-local addresses SHOULD be treated as either optimistic or
tentative, and globally unique addresses SHOULD NOT be used in a way
which creates neighbor cache state on their peers, while DNA
procedures are underway. The different treatment of IP addressing
comes from the fact that on the global addresses cannot have an
address conflict if they move to a topologically incorrect network
where link-local addresses may. Even though global addresses will
not collide, the incorrect creation of neighbor cache entries on
legacy peers may cause them some harm...."
Can you please elaborate as what "SHOULD treat their addresses
as if they were" underlined above means?
I am little confused with this line. Also IMHO, this paragraph is a bit
difficult
to understand. It may be better to rephrase it in simple terms.
4.
Some typos
1. In section 4.5, last paragraph bracket is not closed.
"... Whenever a host receives a hint (see Section 5, after identifying
the
link, it SHOULD verify partial reachability from its default router
to itself."
2. In section 6,
".... Invalidationof router and prefix list ..."
s/Invalidation of/Invalidationof
3. In section 7.2,
".......If a host is changing is IPv6 link, the new
^^^
router on that link may have a different configuration and may
introduce more delay than the previous default router of the host...."
s/its/is
4.In section 8.2,
".... If a non-SEND node forges a DAD defense for an address which is
still
in peers' neighbor cache entries, a host may send a SEND protected
unicast neighbor solicitation without a source link-layer address
option to one its peers (which also uses SEND). ...."
^^^^^^^^^
s/one of its/one its
Regards
Subba Reddy