On Mon, Aug 17, 2015 at 01:01:04PM +1200, Brian E Carpenter wrote:
> That may be desirable to limit churn, but must not be depended on. The
> architecture is explicit on pp 25-26 that renumbering is an expected event:
> https://tools.ietf.org/html/rfc7368#page-25
> The addressing, routing and naming architecture has to be ready for
> renumbering at any time. Anything else is broken.
What analysis is there about application and API level problems in supprting
this model today ? My gut feeling is that a lot of applications or
even APIs like bind(::) may have problems, but thats just because i am paranoid.
Cheers
Toerless
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
