RE: [Seamoby] CAR Discovery Requirements

Hi James,

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?

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.

Regards,

Dirk

-----Original Message-----
From: ext James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Tuesday, March 12, 2002 3:27 PM
To: Trossen Dirk (NRC/Boston); seamoby@ietf.org
Subject: Re: [Seamoby] CAR Discovery Requirements

Dirk,

</wg-chair-hat-off>

> "3.xx Providing MN's requirement for Determination of CARs
> 
> The fundamental task of CAR discovery is to determine candidate
> access routers (from the set of GAARs) that meet MN's requirements,
> if known at the time of handoff. A CAR discovery protocol MUST 
> determine a set of CARs that meet MN's requirements. For this, 
> a CAR discovery protocol MUST provide means for the MN to express 
> these requirements."
> 

I think this is confusing two issues:

    - Distribution of routing reachability and capability information.

    - Expression of MN requirements or rights.

The second issue may require, for example, AAA, or it 
may be implemented using an AAA protocol.

I think it would make more sense to keep these issues separate.

</wg-chair-hat-on>

            jak

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