Re: [Dime] rfc3588bis version number
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Dime] rfc3588bis version number



Hi,
> The original plan for 3588bis was sound and is still required. IMO the decision to address TLS negotiation in bis knowing that the fix was not backwards compatible was our error. I vote we deprecate this feature in 3588bis, move the proposed solution to a new draft (Diameter v2 if required) and get 3588bis out the door.
>   
This sounds reasonable to me, and I support this approach.

Although this issue with TLS *is* a security vulnerability and should
result in the Diameter protocol version 1 be deprecated quite soon to
the benefit of a secure version 2...

Best regards,
Sebastien.

-- 
Sebastien Decugis
Research fellow
Network Architecture Group
NICT (nict.go.jp)


Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.