Re: [BEHAVE] Comments on draft-ietf-behave-v4v6-bih-02

[<[e-mail]>]

> > The (a) is definitely the most powerful and works best with DNSSEC, but at
> the
> > same time I believe most difficult to implement. The (b) and (c) are
> possible to
> > have as plug-ins, which gives them some merit (especially for the time being
> > when host based DNSSEC validation is quite rare). What if document would say
> > (a) is MUST if it is feasible to implement (i.e. acknowledging sometimes the
> > "MUST" may not hold)?
> 
> "MUST if it is feasible to implement" means the same as "SHOULD", and the
> latter is more concise.

SHOULD then, for the next revision, perhaps:
--
In order to properly support DNSSEC, the ENR SHOULD be implemented at the 
socket API level. If the socket API level implementation is not possible, 
DNSSEC support SHOULD be provided by other means.
--

> My main point is that DNS is not the only protocol for off-link name
> resolution,
> and implementation option (a) is better than the others.

Maybe:
--
In the case of the socket API layer implementation option, when an IPv4 application
tries to do a forward lookup to resolve names via the resolver
library (e.g., gethostbyname()), BIH intercepts the function call and
instead calls the IPv6 equivalent functions (e.g., getnameinfo()) that
will resolve both A and AAAA records. This implementation option is name resolution
protocol agnostic, and hence supports techniques such as "hosts-file",
NetBIOS, mDNS, and essentially anything underlying operating system uses.
--

> Section 4 of draft-ietf-behave-v6v4-xlate already contains sufficient
> discussion.  So I think the text on fragmentation can be removed, since
> the previous paragraph already references the entirety of that document.

Probably the same applies then for checksum as well, and hence the whole section could be:
--
2.2.  Protocol translator

   The protocol translator translates IPv4 into IPv6 and vice versa
   using the IP conversion mechanism defined in SIIT
   [I-D.ietf-behave-v6v4-xlate].  To avoid unnecessary fragmentation,
   host's IPv4 module should be configured with small enough MTU (IPv6
   link MTU - 20 bytes).
--