Other specifications: Difference between revisions

Revision as of 22:24, 23 July 2012

This is a collection of various RFCs and IETF drafts.

Defines how NAT devices and firewalls should behave, in particular regarding idle timeouts.

@@ Line 1: / Line 1: @@
-Hey AbrahamSo in a broadcast multi aeccss networks, the neighbour should send four separate unicast packets to the nieghbors to set up a BFD session. Because BFD uses unicast session with all its neighbours , So it should send a unicast packet to every one in a broadcast multi aces snetowrk Am i right ?Yes i got the Discriminator logic in BFD.So BFD  echoes the BFD data packets with its neighbors. So whether BFD is a control palne protocol or a dat aplane protocolAs per the RFC , BFD has the tendency to work on both control plane and data palce.In which cases it works in Data plane and in which case it is a control plane protocol. Cheers mate
+This is a collection of various RFCs and IETF drafts.
+== Technical specifications ==
+* [http://filezilla-project.org/specs/rfc2616.txt <nowiki>RFC 2616</nowiki>] "HTTP/1.1 Hypertext Transfer Protocol"
+* [http://filezilla-project.org/specs/rfc5382.txt <nowiki>RFC 5382</nowiki>] "NAT Behavioral Requirements for TCP"<br />
+Defines how NAT devices and firewalls should behave, in particular regarding idle timeouts.
+== See also ==
+* [[File Transfer Protocol]]
+* [[TLS specifications]]
+* [[SFTP specifications]]