| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hello folks,
I've been puzzling over the definition of "proxy" as it is used
in 802.21.
Here's the current definition:
> Proxy function: A function to bridge the mobility signaling between
> a mobile node (MN) and a target point of attachment via the
> source network. To the MN, the Proxy function acts like a
> virtual point of attachment (PoA) to the target network.
> It enables such functions as preregistration and proactive
> authentication of the MN.
I think it's probably better to refocus this definition.
We possibly could have three proxy functions:
Proxy MIHF:
an entity that appears to an MN to be an MIHF, but which in
reality simply interfaces to another device which actually
performs the MIHF functions
Proxy PoA:
an entity that appears to an MN to be an PoA, but which in
reality simply interfaces to another device which actually
performs the PoA functions
Proxy PoS:
an entity that appears to an MN to be an PoS, but which in
reality simply interfaces to another device which actually
performs the PoS functions
This may still need more refinement, for instance to describe how
PoS functions are different than MIHF functions, but I think it's
a lot more understandable. In the body of the text, then, it could
be explained how a Proxy PoA does "proxy authentication", or
other proxy preregistration activities.
Regards,
Charlie P.