Re: [v6ops] Discussion focus: draft-ietf-v6ops-ipv6rtr-reqs

[<[e-mail]>]

> > The primary focus is routers for enterprise or carrier use, however
> > most of the features also have broad applicability to all routers.

But, having said I'm happy to include whatever -- I will point out there are lots of exceptions in this scoping. Just to name a few --

- I'm not really crazy about the "enterprise/service provider" divide, as it doesn't really describe a lot of network operators

- Given a WISP is a "service provider," and a WISP (by definition) runs a large wireless network, and there have been a lot of objections on the list about applying these requirements to edge wireless devices, I don't think this scoping will work

- Would this also cover, say, a route server at an IX? It seems it would, and yet route servers do not forward traffic, so this is another exception

- Would the routing component of a "firewall" or "load balancer," running in an "enterprise network" be considered a "router?" If so, there a number of requirements in this document do not apply

- Would a virtual router sitting in any network service be considered a "router?" If so, I can imagine a number of situations where many of the requirements here might not be necessary

I could probably give tens of more examples of exceptions to the above scoping.

IMHO, it is much safer to include "if there are exceptions, please tell me what they are" -- something like this:

==
This document describes a minimal set of features any device designed to run a control plane capable of computing loop free paths for IPv6, and forwarding IPv6 packets, is expected to support. In some cases, it might be that a device designed for a specific situation will not need a particular feature listed in this document as a SHOULD or a MUST. In these situations, the manufacturer or developer SHOULD provide a list of features described either as SHOULD SUPPORT or MUST SUPPORT to operators and consumers of the device. This will aid the operator by providing a clear list of what is, and is not, supported by the device.
==

😊 /r