[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SOHO/Profiles
First, I think *all* devices need at least the ability to filter
traffic directed *to* it, particularly devices that allow in-band
management. See CA-2003-17 for justification.
I agree - no problem there
Second, your current profile does not seem to anticipate any sort
of ongoing management (or even capability to do so). I think,
given the current definition of scope, for a device to be covered
by these requirements, it would have to be at least potentially
managable by the network operator.
Yeah...probably best to include *some* management capability and if
joe-cheapo-fw/router/switch wants to play in bigger world they can do the
right thing in terms of what this profile requires.
This is not to say that you can't define a profile out of the
existing requiremnts that is intended to be useful as guidance
for joes firewall, it simply means we're not going to add and
requirements for it.
Joe firewall/switch/dareIsayrouter can look towards SOHO requirements for
guidance....no further subset needed....
If you want to define profiles for unmanagable (by the operator)
or customer managed devices, that's fine, just indicate clearly
in the intro text that that's what's being done.
nope....see above...
I'm attaching a copy of prof.all.xml, which is the source for
set of profile requirements that has every currently defined
profile. Simply change the intro paragraph text and edit out
all the sections/requirements that don't apply and send back to
me.
OK
[1] I do have some question about including any CPE since physical
access then becomes an issue.
it's always an issue....and overlooked I can't even tell you how many
times......and not just in CPE type equipment......
- merike