Jehanzeb Qayyum

netty jdiameter impl is only RFC 3588 at the moment. I tried that with seagull client using TLS and it sent Client Hello without sending a CER. So seagull is...

thanks @coolface88. netty jdiameter impl waits for StartTlsRequest whereas seagull client sends ClientHello after CEA.

I removed startTls and change to simple tls handshake impl. For some reason seagull sends CER again, after receiving CEA, during/after handshake which makes the whole communication out of synch....

By simple i mean not StartTLS which starts with StartTlsRequest and StartTlsResponse befor ClientHello. I will share my branch. But i have a problem that seagull goes to init section...

@coolface88 Here it is: [netty-tls](https://github.com/jehanzebqayyum/jdiameter/tree/netty-tls) for your ref: I originally created keys & certs using keytool. And later converted the same to pem files for use with seagull. Changes in...

TCPClientConnection & TCPTransportClient are used by both diameter server and client. To move to netty this should be refactored into server and client specific transport. Since server will have both...

I went through the code and seems like changing to netty requires a bit of refactoring or may be i need more understanding of the code. The problems i am...

Thanks for the guidance. Base on the input i updated TCPClientConnection, TCPClientTransport (NettyTransportClient) and NetworkGuard. Attached updated. A couple of more questions, hope you do not mind: 1- Should we...

Done. Please review the pull request and provide your comments. Meanwhile i continue to work on my fork. Best Regards, Jehanzeb Qayyum +971 52 898 2285 +92 3311337064 On Thu,...

Should TLS negotiation happen in connection establishment or CER/CEA? Below is what i found out: For RFC3588 compliant peers TLS (Transport Layer Security) may optionally be negotiated. For RFC6733 compliant...