Hi Thomas,
Thomas Narten wrote:
I still believe stub is poor explanation and I emphatically do not want
to exclude AHN as transit to reach another fixed Internet.
While I suspect that most AHN's will be stub, I'd offer the following
observations/questions:
- how does restricting AHNs to stub networks simplify any aspect of
the problem? (if it doesn't, why add the restriction or make such
an assmption?)
- how can one enforce such a restiction? (one probably can't --
people will use them for transit), so better go ahead and plan for
it so that things don't break in horrible ways when it happens in
practice...
I think the stub argument is really irrelevant for
autoconf. It's a routing issue, rather than a
configuration issue. It doesn't matter a gnat
whether the routers at the edge of the adhoc domain
wish to learn each other's routes, or forward to
each other.
We should concentrate on the issue of applying addressing
to the chosen subnet model, when that's clearly explained.
Greg
_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area
