On 30/03/2017 10:38, Michael Richardson wrote:
>
> Brian E Carpenter <[email protected]> wrote:
> >> I just don't see the point of the ASA here.
>
> > There's already a thing called an HNCP agent. Why couldn't
> > it be enhanced to negotiate with an upstream ASA for resources?
>
> Because it's already done. It's called DHCPv6.
> It already has extensive running code :-)
> It's not even that complex.
All true. But it isn't designed for negotiation as far as I know,
just a request/response.
> I would love to request address space via ASA from the DHCPv6 server.
> That would all happen within the ISP's ACP though.
Agreed, that is a little higher up the food chain. Maybe that is as close
to the user as an ASA will get. I don't really care; I just wanted to
explore the way we might fit our various tools together.
> Right now (on DSL lines), the address space mostly comes via radius.
> Which is to say that the problem has been centralized by MBS builders into
> being someone else's problem. Advertising the address space is often done by
> OSPFv3, but there are additional things that would be easier for the DHCPv6
> server to do, such as the DNS delegations that homenet is working on
> finishing.
Yes, indeed, and then we could discuss how the radius server gets new
address space when it runs out.
> I think that CASM could very nicely define/extend the prefix ASA to deal with
> DNS reverse names, and as the RIRs (George) said, better link the delegated
> prefix to clear ownership records.
Yes, by defining a full set of relevant objectives.
Brian
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
