Re: [Seamoby] CAR Discovery Requirements

> I don't see that the requirement is addressing the distribution
> of the information. There is another requirement for this, namely
> 3.4. The present one is merely addressing that a solution has to
> match the set of GAAR+capabilities with MN's requirements to determine
> the set of CARs. This is essentially what CAR discovery is about,
isn't
> it?
>

What 3.4 states is:

    3.4. CAPABILITY DISCOVERY

    The other fundamental function of CAR discovery protocols is that of
    identifying the capabilities of GAARs. The protocol MUST provide
    functionality to allow ARs to discover their GAAR's capabilities.
These
    capabilities MUST be communicated in a secure fashion.

This says nothing about the MN's capability requirements.

In fact, if you look at the last item in Section 3 of
draft-ietf-seamoby-cardiscovery-issues-02.txt, TAR Selection Algorithm,
the selection of a target router, which would involve matching the MN's
requests with the AR capabilities, is explicitly excluded from the
problem
statement.

> Whether you use existing protocols for certain parts is not
> prohibited by the chosen wording. You might use AAA to express
> the requirements. Still, a CAR discovery protocol has to match
> these requirements onto the available GAAR+cap info. How this
> is done depends on the solution.
>

According to Section 3 of draft-ietf-seamoby-cardiscovery-issues-02.txt,
this is out of scope of the problem.

            jak

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