| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This removes the CDAP flow class, which is no longer needed.
|
| |
|
|
|
|
|
|
|
| |
By removing authentication as part of CACEP, all policies
disappear. CACEP becomes a policy-free connection establishment
protocol between Application Entities. Authentication can later be
added cleanly as a pure policy function when needed.
|
|
|
|
|
| |
The AE name should not be passed over the layer boundaries. If an
application has more than one AE it should exchange this in CACEP.
|
|
|
|
|
|
| |
The information passed to CACEP is split between the information about
the connection and the information to be used during the
authentication exchange.
|
|
|
|
|
|
|
|
|
| |
This exchanges a protocol name, a protocol version and concrete syntax
for the protocol upon CACEP. For CDAP, only version 1 and GPB are
supported. No lists for other supported versions or syntaxes are
exchanged (but the proto file supports it). CACEP fails if there is a
mismatch between the protocol names, version and syntax specified by
the communicating parties.
|
|
Avoids some code duplication in the normal IPCP with respect to
establishing authenticated CDAP flows.
|