Lars,
- Conflicts between configuration parameters.
- Issues with address selection.
I agree that both of these are important and should be worked on (and
with the rest of your email, basically).
The first one is what I thought MIF would be focusing on, as an INT WG
is IMO the right venue for this.
The second one is also important, but much more tricky, because it
ties in with transports and applications (as Keith and others have
pointed out already). Topics that cross area boundaries are always a
bit difficult to charter. I'm at this point not fully convinced that
simply throwing this in with topic #1 into one WG is going to work.
First, a minor point: I think everyone is mindful about the fact that
address selection is a problem that affects apps, transports, and IP
layer. However, I'll note that address selection has been an Internet
area topic for some time (RFC 3484, 6MAN work, etc).
But my main point is that the MIF charter covers -- on purpose -- a
relatively large problem area. We need to describe the problem as
experienced by real-life implementations without constraining ourselves
too much at this stage. Once we finally understand the problem fully,
then it is a time to start narrowing down the scope to something
implementable. However, we are not there yet. The WG needs to complete
its problem definition task first. When it does, it may be that we no
longer need a specific WG and the rest can be handled in, say, DHC -- if
the chosen scope is just parameters conflicts, for instance.
I would also echo what Margaret said about this discussion being
excellent input for the problem definition work. From my point of view
I'd like to get the group chartered so that they can do that work, as
opposed to us writing the full problem definition into the charter. The
latter would consume quite a bit of IETF discussion list and AD cycles :-)
Jari
_______________________________________________
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf