Chicago RPC Developer's Kit Notes for Beta release M6:
------------------------------------------------------

1. Protocol Sequences supported:
    Client:
        ncalrpc
        ncacn_np
        ncacn_nb_nb
        ncacn_spx

    Server:
        ncalrpc
        ncacn_nb_nb
        ncacn_spx

2. MIDL generated stubs using auto handles are not supported.

3. API's not supported:
    Authentication and authorization (none supported):
        RpcBindingInqAuthClient
        RpcBindingInqAuthInfo
        RpcBindingSetAuthInfo
	RpcIfRegisterAuthInfo
        RpcImpersonateClient
        RpcMgmtInqDfltAuthnLevel
        RpcMgmtInqServerPrincName
        RpcMgmtSetAuthorizationFn
        RpcRevertToSelf
        RpcServerRegisterAuthInfo

    Cancel support (not supported):
        RpcMgmtSetCancelTimeout

    Name Service (none supported):
        RpcNsBindingExport
        RpcNsBindingImportBegin
        RpcNsBindingImportDone
        RpcNsBindingImportNext
        RpcNsBindingInqEntryName
        RpcNsBindingLookupBegin
        RpcNsBindingLookupDone
        RpcNsBindingLookupNext
        RpcNsBindingSelect
        RpcNsBindingUnexport
        RpcNsEntryExpandName
        RpcNsEntryObjectInqBegin
        RpcNsEntryObjectInqDone
        RpcNsEntryObjectInqNext
        RpcNsGroupDelete
        RpcNsGroupMbrAdd
        RpcNsGroupMbrInqBegin
        RpcNsGroupMbrInqDone
        RpcNsGroupMbrInqNext
        RpcNsGroupMbrRemove
        RpcNsMgmtBindingUnexport
        RpcNsMgmtEntryCreate
        RpcNsMgmtEntryDelete
        RpcNsMgmtEntryInqIfIds
        RpcNsMgmtHandleSetExpAge
        RpcNsMgmtInqExpAge
        RpcNsMgmtSetExpAge
        RpcNsProfileDelete
        RpcNsProfileEltAdd
        RpcNsProfileEltInqBegin
        RpcNsProfileEltInqDone
        RpcNsProfileEltInqNext
        RpcNsProfileEltRemove

    Endpoint Mapper (no server support):
        RpcEpRegister
        RpcEpRegisterNoReplace
        RpcEpResolveBinding
        RpcEpUnregister
        RpcMgmtEpEltInqBegin
        RpcMgmtEpEltInqDone
        RpcMgmtEpEltInqNext
        RpcMgmtEpUnregister

4. Known problems

    RpcServerUseProtseqIf returns RPC_S_PROTSEQ_NOT_FOUND if the
    protocol sequence is not found in the interface.  It should return
    RPC_S_PROTSEQ_NOT_SUPPORTED.

    RpcEpRegister returns an undefined error code.  For this release, it
    should return RPC_S_CANNOT_SUPPORT.

    For the ncalrpc protocol sequence only: Server processes will not
    terminate until client closes all ncalrpc binding handles.

    Registering
        interface 1 with object X
        interface 2 with object X
        interface 3 with object Y
    and calling RpcServerUnregisterIf(NULL, X) will fail because object X is
    not present for all interfaces.  The call should unregister X from
    interface 1 & 2 and ignore 3.  
