From: jamal <hadi@cyberus.ca>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Cc: netdev@oss.sgi.com
Subject: Re: Netlink as an IP Services Protocol to Informational
Date: Thu, 10 Apr 2003 14:25:59 -0400 (EDT) [thread overview]
Message-ID: <20030410142253.V86925@shell.cyberus.ca> (raw)
In-Reply-To: <200304091749.h39Hn6XU029346@marajade.sandelman.ottawa.on.ca>
Question for you, since you are a security expert:
We are having problems deciding whethet TLS needs reliability or whether
it needs connection orientedness.
Connection orientedness is essentially being able to connect and leave
(example TCP SYN,SYNACK,ACK...FIN,FINACK)
Reliability is ensuring delivery i.e Retransmits and keeping state of
dataflow vs ACKs and sequence numbers.
Does TLS just need somehow to setup the connection or does it need both?
cheers,
jamal
prev parent reply other threads:[~2003-04-10 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200304091518.LAA02420@ietf.org>
2003-04-09 17:49 ` Netlink as an IP Services Protocol to Informational Michael Richardson
2003-04-09 17:58 ` Andi Kleen
2003-04-09 18:57 ` Robert Olsson
2003-04-10 18:22 ` jamal
2003-04-10 18:25 ` jamal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030410142253.V86925@shell.cyberus.ca \
--to=hadi@cyberus.ca \
--cc=mcr@sandelman.ottawa.on.ca \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).