Search results
Results from the WOW.Com Content Network
RFC 2474: Rate: Yes Telephony: EF 46: Police using sr+bs: RFC 3246: Priority: No Signaling: CS5 40: Police using sr+bs: RFC 2474: Rate: No Multimedia conferencing AF41, AF42, AF43 34, 36, 38 Using two-rate, three-color marker (such as RFC 2698) RFC 2597 Rate Yes per DSCP Real-time interactive CS4 32 Police using sr+bs RFC 2474 Rate No ...
Class Selector (RFC 2474) AFxy Assured Forwarding (x=class, y=drop precedence) (RFC 2597) EF Expedited Forwarding (RFC 3246) LE Lower-Effort (RFC 8622) The above table, with individual values written out for values of the entire ToS field (not to be confused with the little-used 5-bit part):
The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams. 207 Multi-Status (WebDAV; RFC 4918) The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made. [7]
This is a partial list of RFCs (request for comments memoranda). A Request for Comments (RFC) is a publication in a series from the principal technical development and standards-setting bodies for the Internet, most prominently the Internet Engineering Task Force (IETF).
The meaning of the "detail" field depends on the class and the subject, and are listed in RFC 3463 and RFC 5248. A server capable of replying with an Enhanced Status Code MUST preface (prepend) the Text Part of SMTP Server responses with the Enhanced Status Code followed by one or more spaces.
RFC 2228 introduced the concept of protected replies to increase security over FTP communications. The 6xx replies are Base64 encoded protected messages that serves as responses to secure commands. When properly decoded, these replies fall into the above categories.
This is a list of all Internet Relay Chat commands from RFC 1459, RFC 2812, and extensions added to major IRC daemons. Most IRC clients require commands to be preceded by a slash (" / "). Some commands are actually sent to IRC bots ; these are treated by the IRC protocol as ordinary messages, not as / -commands.
The procedure is explained in detail in RFC 1071 "Computing the Internet Checksum". [1] Optimisations are presented in RFC 1624 "Computation of the Internet Checksum via Incremental Update", [ 2 ] to cover the case in routers which need to recompute the header checksum during packet forwarding when only a single field has changed.