Skip to contentSkip to conversation

Netlink as an IP Services Protocol to Informational

DISCUSSION Michael Richardson 4 participants 5 messages Apr 9, 2003 – Apr 10, 2003 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

"The" == The IESG <[email protected]> writes:

The> The IESG has approved the Internet-Draft 'Netlink as an IP Services The> Protocol' <draft-ietf-forces-netlink-04.txt> as an Informational RFC. The> This document is the product of the Forwarding and Control Element The> Separation Working Group. The IESG contact persons are Bill Fenner The> and Alex Zinin.

....

Congrats to Jamal for this hard work on this.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] [email protected] http://www.sandelman.ottawa.on.ca/ |device driver[

] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [

#2 lore raw
Quoted 11 lines · Michael Richardson
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

"The" == The IESG <[email protected]> writes:

The> The IESG has approved the Internet-Draft 'Netlink as an IP Services The> Protocol' <draft-ietf-forces-netlink-04.txt> as an Informational RFC. The> This document is the product of the Forwarding and Control Element The> Separation Working Group. The IESG contact persons are Bill Fenner The> and Alex Zinin.

....

Congrats to Jamal for this hard work on this.

Yes congratulations from me too.

-Andi (who unfortunately wasn't much help I guess on this :/)

#3 lore raw
Quoted 4 lines
Quoted 2 lines

Congrats to Jamal for this hard work on this.

Yes congratulations from me too.

From me as well... This was not was an easy job.

Cheers.

					--ro
#5 lore raw
In reply to Michael Richardson

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