eap Mailing List: RE: Issue 287: Roaming Model

[Bernard Aboba (aboba]

> My response
> 1.    Bigco can have its employee's handsets/laptops provisioned with
> a list of its preferred roaming partners lists which in this case would
> include Consort.com.

I think the question is what assumptions this document makes about how AAA
proxy routing tables are transformed into EAP network announcements.
Essentially, what is being defined here is a peer-AAA proxy routing
protocol into which static AAA proxy routes are redistributed.  Once the
peer obtains the routing table, it uses it to form the "source routes"
utilized within the NAI.

Multiple issues are brought up by Glen's comments:

a) Is the roaming model proposed by the document adequately specified and
analyzed?

b) Does the proposed model scale?  What are its limitations?

> One possible scenario is that:
> The Bigco employee with her Bigco credentials tries to authenticate
> herself. Megatel does not recognize her

It would be more clear if you described the scenario in terms of the
entries present in the AAA proxy routing table and the ensuing
announcements.  Are you saying that a bigco.com entry is present in the
routing table, but that this document specifies that a "filter" is to be
applied to that entry so that it is not announced?  Or are you saying that
the entry is not present at all, and therefore is not announced?  There is
a considerable difference between these two scenarios.