|
|
| (14 intermediate revisions by 9 users not shown) |
| Line 3: |
Line 3: |
| | == Technical specifications == | | == Technical specifications == |
| | | | |
| − | * [http://filezilla-project.org/specs/rfc2616.txt <nowiki>RFC 2616</nowiki>] "HTTP/1.1 Hypertext Transfer Protocol" | + | * [https://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 /> | + | * [https://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. |
| − | Defines how NAT devices and firewalls should behave, in particular regarding idle timeouts. | |
| | | | |
| − | Ye Angelo, I have also heard a little about 4G, but who knows what's going to hpepan. I definitely think that 2010 is going to see some amazing developments in the mobile space, it's sort of like how 56k modems moved to ADSL with so much demand, the same thing's going to start hpepaning with the public wanting faster and faster mobile devices.I look forward to it!
| + | == See also == |
| | + | |
| | + | * [[File Transfer Protocol]] |
| | + | * [[TLS specifications]] |
| | + | * [[SFTP specifications]] |
Latest revision as of 21:03, 12 October 2016
This is a collection of various RFCs and IETF drafts.
Technical specifications[edit]
- RFC 2616 "HTTP/1.1 Hypertext Transfer Protocol"
- RFC 5382 "NAT Behavioral Requirements for TCP"
Defines how NAT devices and firewalls should behave, in particular regarding idle timeouts.
See also[edit]
