"Scharf, Michael (Nokia - DE)" <[email protected]> writes:
> Has the WG discussed the applicability of > https://www.ietf.org/iesg/statement/writable-mib-module.html to > Section 2.2? > > I know that this question may be a bit unusal for TSV area and even > more unusal for this specific use case ;-) > > Also, it may not apply to an informational document. But it could be > worthwile to review if CLI ("sysctl") is indeed the only known method > in industry for configuration of network elements implementing TCP. To be clear, the API document presents an abstract API. The suggestion of sysctl is for OSes that already do a bunch of TCP configuration via sysctl. For an OS that loads TCP configuration in some other way, or user-level implementations that cannot extend sysctl, the same knobs will have to be made available through a different mechanism. The goal is to ensure that whatever mechanism provides these configuration knobs, roughly the same knobs will be available everywhere so that configurations can easily be translated between OSes. If we believe devices currently configured with netconf will someday support TCPINC, then we can include a paragraph explaining how the API would map to netconf. Presumably this would specify some XML path under which to mount the system-wide options? Is there precedent for configuring other TCP parameters with netconf, and if so what does it look like? Do you want to suggest some language to include? Thanks, David _______________________________________________ Tcpinc mailing list [email protected] https://www.ietf.org/mailman/listinfo/tcpinc
