Hello, everyone.
Attached is an updated version to our personal draft on
draft-wang-tls-raw-public-key-with-ibc-10.
The target of the draft is to use identity as raw public key over TLS.
Idenitty-based signature (IBS) algorithms are used for peer/server
authentication.
The draft has been
Good point. Furthering that point:
- what about DTLS/SRTP when that is used with ICE (RFC8445 and its precursor
RFC5245) and QUIC (c.f., https://w3c.github.io/webrtc-quic/). Need guidance in
the document to use ICE and/or quic-address-extension, as well as what it means
if they differ (heaven
I have taken an initial look at this draft [0]. Comments follow.
First the motivation for this technique appears rather
weak. Primarily, you argue that a PKI is complicated to implement and
this is simpler. However, there are a number of factors to consider.
First, I believe the design you have s
I see this draft describes the format of a network address as
NetworkAddress.address carries the raw network-order byte-wise
representation of the client IP address.
...
Clients which receive a non-empty NetworkAddress extension may use
it to record their public IP address.
This
Hi!
I try to find authoritative explanation for some aspects in RFC 5246 (TLS
1..2). I hope this is right place to ask.
Background: Company A has client/browser and company B has web server. Server
has certificate and it also requires certificate from client. Client do not
advertise signature_
