|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
>>>>> "David" == David Harrington <ietfdbh@xxxxxxxxxxx> writes: David> The IETF could mandate a specific protocol to try to ensure David> interoperability, but doing this takes the decision out of the David> responsibility of the deployer to choose the best solution for the David> deployment environment, and out of the responsibility of the vendor to David> best meet their customers' demands. This doesn't make any sense to me at all. It makes sense if the vendor that the ISP is going to use (the CGN vendor) is somehow related to the vendor that the customer is going to use (the CPE vendor). However, one of the explicitly stated assumptions in the behave-lsn document is that is not the case. The customer gets to choose a CPE vendor and the operator gets to choose a CGN vendor. The deployment environment here is the Internet. In cases like this in the past we have chosen a technology. I'm reasonably sure that host requirements mandate DNS as the name service protocol. We don't want one isp to choose some big LDAP directory and one ISP to choose DNS. We want customers name resolution to continue to work (with the same CPE they already have) as they move from one ISP to another. The same arguments apply here . Under the assumptions of this BCP, there is not a boundary between deployment environments across which one deployment could use PCP and another SNMP. (I am not aware of netconf schema that does anything similar to PCP that has been standardized.) Even obvious deployment environments like cable vs DSL don't make sense. I can buy my own router and stick it behind either a cable modem or a DSL router. People often do this. With some ISPs the configuration gets a little tricky and you may introduce an extra level of NAT. However, people deploy their own customer gateways on cable, DSL, even in some cases mobile wireless. BGP was held up as an example, namely that we don't mandate the implementation of BGP. Well, not all routers should implement BGP. My little Linksys box has no need for it. However, if we wrote requirements for routers participating in the core routing infrastructure--routers between large organizations and ISP--we'd almost certainly mandate BGP. Not all NATs need the same middlebox control protocol. However, this document does not apply to all NATs. It applies to NATs that cross organizational boundaries. That's exactly the environment where saying something like "this is an SNMP deployment," confuses me because I don't think there will be uniform characterizations of the deployment.