Re: [Seamoby] CAR Discovery Requirements

Hi James,

> And, in fact, this brings up another issue. The current requirements are
> completely lacking *any* mention of security. But I will address that in
> another note so as not to confuse the threads.

They at least mention the secure transfer of capability information.
However,
I'm looking forward to seeing requirements or additions to requirements,
folding in security aspects.

> I have no objection to including this requirement as long as:
>
>     - The language makes clear that the requirement is not to force the
> same protocol to perform CAR discovery and to communicate MN
> preferences.

Agree, sorry for any inappropriate wording that didn't make this clear
enough.
From my perpective, CAR discovery has been seen as a problem that needs
certain
aspects to be addressed. Expressing MN's requirements is one of them to
determine the CARs. A solution for the CAR discovery problem is comprised
of different parts that fulfil as a whole the requirements we're currently
talking about. Parts of
the solution could be defined as a new protocol, for other parts we could
and should
use existing infrastructure. This was implicitly in my mind for ALL
requirements,
e.g., for the transfer of capability information. That's why I didn't put it
specifically
in the one we're currently discussing.
To expedite the process, what would an appropriate wording to make this
clear?
Or would it be more useful to have a general statement in the introduction
of the
requirements, that this is the case for ALL requirements, following the line
of
argumentation I tried to outline in the previous paragraph?

>
>     - The distinction between routing security/AAA requirements for CAR
> discovery and MN security/AAA requirements for MN preferences is
> maintained.

I see this more as security aspects in general. Could you provide
requirement(s)
for this aspect (actually your above sentence is pretty much one, isn't it)?

Regards,

Dirk

_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby