[dhcwg] Re: Request for review: draft-drew-dhc-v4-routed-p refix-00

Michael Richardson <[email protected]>
Newsgroups gmane.ietf.dhc
Message-ID <[email protected]>
Brendon Drew <[email protected]> wrote:
    > My intention has been to leave the mechanism by which the DHCP server
    > determines which routed prefixes belong
    > to a subscriber out of scope. That information could come from RADIUS, static provisioning, an OSS/BSS, or
    > another provider-specific mechanism.

It's a mistake we make in DHCPv6-PD in my opinion.
Today, DHCP relays inspect the DHCP relies from the server to learn the
routing.   I complained about this a decade ago... but some felt that it was
code/water under the bridge, and not worth fixing.   We should have created
DHCP relay options to communicate this.

{In my DHCPv6-PD server for a BNG/BMS a decade ago, the relay was irrelevant, as
there was a very small DHCPv6-PD server for each PPP link, and it received
RADIUS attributes directly, so it could do the routing directly, and OSPFv3
would then pick up the connected routes}

    > I also agree that TR-069/ACS should be mentioned as an existing way of achieving automatic configuration. I
    > think there is an important distinction, though, in that TR-069
    > requires a management relationship between the
    > provider and the CPE and depends on the required configuration being
    > exposed through the device's management model.

Yes, and it makes no sense for a virtual cloud provider, nor for the case for
a small office where the home router delegates a /32 to some special box.


--
Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

**       My working hours and your working hours may be different.         **
** Please do not feel obligated to reply outside your normal working hours **

_______________________________________________
dhcwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]
signature.asc (application/pgp-signature, 487 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmp/W2MACgkQgItw+93Q
3WWF1wgAvnJkguo9R3a6w2Wv8Gvrs9EPYT3w/UUwbAnH9Nrc+XS0ss8ZYEAuKMbh
ns/VuOI4k10xd14GsYv4OalYXKp4ArZX4zbWY3FXv4nU4C3/jHSt6ZIUogK8eqSy
aQp2CdtepyA/d2kw4x540NTy0jkX3m3DON01cNxJbDx2pHnsOKuGNk6I+//86U9T
GA0Lzo2bAWvfmsF2oEb1NcQ8h69Vq3Nt5sIB+s9lgyS2Ugr8pup95EYoImY7vnAw
IFmBI+blMbuNkWOsh/9hivCoHAx9zgQij9DLFdJxDgadOxfJyVxErEH5NfsFCc2R
Ba94V03B7wRoEey3q2W5TpULK4cWmA==
=lwIM
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.