>> I'm not sure DHCP configuration is really needed. It seems like overkill. > > Other reviewers/commenters previously felt that this was a useful > addition. This would allow Network Operators to trigger or influence > the connectivity check on CE routers that they are not in TR.069/etc. > control of.
Requiring the DHCP option makes a big difference in deployability. Without it, I can implement this feature today. With it, I have to wait until the DHCP option is standardised. And we would presumably get into a big debate about what CE routers should do in the cases where they don’t get a DHCP option. Should they try this mechanism anyway? We have not requied explicit configuration in the other cases where we have recommended this mechanism. Ref. RFC5969. While the echo mechanism requires some special provisioning on the local system (ensure that ingress filtering isn’t blocking packets with yourself as source) I am not aware of anything on the PE that woukd block this. If there is consensus on that, I think it’s perfectly fine to require this mechanism on by default in CE routers. Although we might add some specifics to deal with a case where DHCP was successful, state in PE was correct, but health check still failed. Cheers, Ole _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
