Searched refs:rfc (Results 1 – 25 of 191) sorted by relevance
12345678
/third_party/python/Doc/library/ |
D | http.rst | 62 ``100`` ``CONTINUE`` HTTP/1.1 :rfc:`7231`, Section 6.2.1 63 ``101`` ``SWITCHING_PROTOCOLS`` HTTP/1.1 :rfc:`7231`, Section 6.2.2 64 ``102`` ``PROCESSING`` WebDAV :rfc:`2518`, Section 10.1 65 ``103`` ``EARLY_HINTS`` An HTTP Status Code for Indicating Hints :rfc:`8297` 66 ``200`` ``OK`` HTTP/1.1 :rfc:`7231`, Section 6.3.1 67 ``201`` ``CREATED`` HTTP/1.1 :rfc:`7231`, Section 6.3.2 68 ``202`` ``ACCEPTED`` HTTP/1.1 :rfc:`7231`, Section 6.3.3 69 ``203`` ``NON_AUTHORITATIVE_INFORMATION`` HTTP/1.1 :rfc:`7231`, Section 6.3.4 70 ``204`` ``NO_CONTENT`` HTTP/1.1 :rfc:`7231`, Section 6.3.5 71 ``205`` ``RESET_CONTENT`` HTTP/1.1 :rfc:`7231`, Section 6.3.6 [all …]
|
D | email.header.rst | 19 :rfc:`2822` is the base standard that describes the format of email messages. 20 It derives from the older :rfc:`822` standard which came into widespread use at 21 a time when most email was composed of ASCII characters only. :rfc:`2822` is a 29 :rfc:`2822`\ -compliant format. These RFCs include :rfc:`2045`, :rfc:`2046`, 30 :rfc:`2047`, and :rfc:`2231`. The :mod:`email` package supports these standards 54 field was properly :rfc:`2047` encoded. MIME-aware mail readers would show this 84 Optional *continuation_ws* must be :rfc:`2822`\ -compliant folding 110 In either case, when producing an :rfc:`2822`\ -compliant header using 111 :rfc:`2047` rules, the string will be encoded using the output codec of
|
D | base64.rst | 19 :rfc:`4648`, which defines the Base16, Base32, and Base64 algorithms, 22 The :rfc:`4648` encodings are suitable for encoding binary data so that it can be 31 defined in :rfc:`4648` (normal, and URL- and filesystem-safe) are supported. 36 newlines every 76 characters as per :rfc:`2045`. Note that if you are looking 37 for :rfc:`2045` support you probably want to be looking at the :mod:`email` 127 :rfc:`4648` allows for optional mapping of the digit 0 (zero) to the letter O 142 :rfc:`4648`. 150 :rfc:`4648`. 267 always ends with a newline, as per :rfc:`2045` (MIME). 275 there is a trailing newline, as per :rfc:`2045` (MIME). [all …]
|
D | email.utils.rst | 32 Returns a string suitable for an :rfc:`2822`\ -compliant 78 Optional *charset* is the character set that will be used in the :rfc:`2047` 105 Attempts to parse a date according to the rules in :rfc:`2822`. however, some 107 guess correctly in such cases. *date* is a string containing an :rfc:`2822` 149 Returns a date string as per :rfc:`2822`, e.g.:: 184 Decode the string *s* according to :rfc:`2231`. 189 Encode the string *s* according to :rfc:`2231`. Optional *charset* and 197 When a header parameter is encoded in :rfc:`2231` format, 204 :rfc:`2231` header is not known by Python; it defaults to ``'us-ascii'``. 212 Decode parameters list according to :rfc:`2231`. *params* is a sequence of [all …]
|
D | http.cookiejar.rst | 20 :rfc:`2965` are handled. RFC 2965 handling is switched off by default. 21 :rfc:`2109` cookies are parsed as Netscape cookies and subsequently treated 97 Netscape and :rfc:`2965` cookies. By default, :rfc:`2109` cookies (ie. cookies 109 This class represents Netscape, :rfc:`2109` and :rfc:`2965` cookies. It is not 125 https://curl.se/rfc/cookie_spec.html 131 :rfc:`2109` - HTTP State Management Mechanism 132 Obsoleted by :rfc:`2965`. Uses :mailheader:`Set-Cookie` with version=1. 134 :rfc:`2965` - HTTP State Management Mechanism 139 Unfinished errata to :rfc:`2965`. 141 :rfc:`2964` - Use of HTTP State Management [all …]
|
D | quopri.rst | 16 defined in :rfc:`1521`: "MIME (Multipurpose Internet Mail Extensions) Part One: 29 described in :rfc:`1522`: "MIME (Multipurpose Internet Mail Extensions) 42 as per :rfc:`1521`. *header* is a flag which controls if spaces are encoded 43 as underscores as per :rfc:`1522`.
|
D | email.rst | 17 (:rfc:`2821`), NNTP, or other servers; those are functions of modules such as 19 RFC-compliant as possible, supporting :rfc:`5322` and :rfc:`6532`, as well as 20 such MIME-related RFCs as :rfc:`2045`, :rfc:`2046`, :rfc:`2047`, :rfc:`2183`, 21 and :rfc:`2231`.
|
/third_party/libcoap/man/ |
D | coap.txt.in | 25 standardized by the IETF as https://rfc-editor.org/rfc/rfc7252[RFC7252]. 57 "https://rfc-editor.org/rfc/rfc7252[RFC7252: The Constrained Application Protocol (CoAP)]" 59 "https://rfc-editor.org/rfc/rfc7390[RFC7390: Group Communication for the Constrained Application Pr… 61 "https://rfc-editor.org/rfc/rfc7641[RFC7641: Observing Resources in the Constrained Application Pro… 63 "https://rfc-editor.org/rfc/rfc7959[RFC7959: Block-Wise Transfers in the Constrained Application Pr… 65 "https://rfc-editor.org/rfc/rfc7967[RFC7967: Constrained Application Protocol (CoAP) Option for No … 67 "https://rfc-editor.org/rfc/rfc8132[RFC8132: PATCH and FETCH Methods for the Constrained Applicatio… 69 "https://rfc-editor.org/rfc/rfc8323[RFC8323: CoAP (Constrained Application Protocol) over TCP, TLS,… 71 "https://rfc-editor.org/rfc/rfc8516[RFC8516: "Too Many Requests" Response Code for the Constrained … 73 "https://rfc-editor.org/rfc/rfc8613[RFC8613: Object Security for Constrained RESTful Environments (… [all …]
|
D | coap-oscore-conf.txt.in | 21 between endpoints (https://rfc-editor.org/rfc/rfc8613[RFC8613]). 67 "https://rfc-editor.org/rfc/rfc8613#section-3.1[RFC8613 Section 3.1. 74 "https://rfc-editor.org/rfc/rfc8613#section-3.1[RFC8613 Section 3.1. 81 "https://rfc-editor.org/rfc/rfc8613#section-3.1[RFC8613 Section 3.1. 88 "https://rfc-editor.org/rfc/rfc8613#section-3.1[RFC8613 Section 3.1. 95 "https://rfc-editor.org/rfc/rfc8613#section-3.1[RFC8613 Section 3.1. 106 "https://rfc-editor.org/rfc/rfc8613#section-3.1[RFC8613 Section 3.1. 112 "https://rfc-editor.org/rfc/rfc8613#section-3.1[RFC8613 Section 3.1. 119 "https://rfc-editor.org/rfc/rfc8613#section-3.1[RFC8613 Section 3.1. 126 "https://rfc-editor.org/rfc/rfc8613#appendix-B.1.2[RFC8613 Appendix B.1.2. [all …]
|
D | coap_recovery.txt.in | 106 https://rfc-editor.org/rfc/rfc7252[RFC7252], as well CoAP Non-Confirmable 108 https://rfc-editor.org/rfc/rfc9177[RFC9177]. 112 "https://rfc-editor.org/rfc/rfc7252#section-4.2[RFC7272 4.2. Messages 115 "https://rfc-editor.org/rfc/rfc7252#section-4.8[RFC7272 4.8. Transmission 144 "https://rfc-editor.org/rfc/rfc7252#section-4.8.2[RFC7252 4.8.2. 154 https://rfc-editor.org/rfc/rfc9177[RFC9177] enabled at both ends of a 157 "https://rfc-editor.org/rfc/rfc9177#section-7.2[RFC9177 167 The following functions reflect the https://rfc-editor.org/rfc/rfc7252[RFC7252] 168 and https://rfc-editor.org/rfc/rfc9177[RFC9177] uppercase names 342 "https://rfc-editor.org/rfc/rfc7252[RFC7252: The Constrained Application Protocol (CoAP)]" [all …]
|
D | coap_pdu_access.txt.in | 90 "https://rfc-editor.org/rfc/rfc7252#section-1.2[RFC7252 1.2. Terminology]". 111 *NOTE:* For reliable messages https://rfc-editor.org/rfc/rfc8323[RFC8323], 164 *NOTE:* For reliable messages "ttps://rfc-editor.org/rfc/rfc8323[RFC8323], 171 *NOTE:* For reliable messages https://rfc-editor.org/rfc/rfc8323[RFC8323], 191 * https://rfc-editor.org/rfc/rfc7252#section-5.10 196 * as per https://rfc-editor.org/rfc/rfc7252#section-5.4.6 203 * https://rfc-editor.org/rfc/rfc8613#section-4 goes on to define E, I and U 426 "https://rfc-editor.org/rfc/rfc7252[RFC7252: The Constrained Application Protocol (CoAP)]" 428 "https://rfc-editor.org/rfc/rfc8613[RFC8613: Object Security for Constrained RESTful Environments (…
|
D | coap_context.txt.in | 150 support for https://rfc-editor.org/rfc/rfc8974[RFC8974] up to _max_token_size_ 151 bytes, else 8 to disable https://rfc-editor.org/rfc/rfc8974[RFC8974] 156 "https://rfc-editor.org/rfc/rfc8974.html#section-2.2.2[RFC8794 Section 2.2.2]" 183 "https://rfc-editor.org/rfc/rfc7252[RFC7252: The Constrained Application Protocol (CoAP)]" 185 "https://rfc-editor.org/rfc/rfc8974[RFC8974: Extended Tokens and Stateless Clients in the Constrain…
|
D | coap_observe.txt.in | 43 https://rfc-editor.org/rfc/rfc7641[RFC7641] extends the CoAP protocol to be 55 (https://rfc-editor.org/rfc/rfc8132[RFC8132]). 110 "https://rfc-editor.org/rfc/rfc7641#section-3.5[RFC7641 3.5. Transmission]". 117 as per "https://rfc-editor.org/rfc/rfc7641#section-4.5[RFC7641 122 "https://rfc-editor.org/rfc/rfc7641#section-4.5[RFC7641 4.5. Transmission]" 419 "https://rfc-editor.org/rfc/rfc7252[RFC7252: The Constrained Application Protocol (CoAP)]" 421 "https://rfc-editor.org/rfc/rfc7641[RFC7641: Observing Resources in the Constrained Application Pro… 423 "https://rfc-editor.org/rfc/rfc8132[RFC8132: PATCH and FETCH Methods for the Constrained Applicatio…
|
D | coap_resource.txt.in | 99 CoAP Observe (https://rfc-editor.org/rfc/rfc7641[RFC7641]) is not supported 122 "https://rfc-editor.org/rfc/rfc7641#section-4.5[RFC7641 4.5. Transmission]". 164 "https://rfc-editor.org/rfc/rfc7252#section-8.2[RFC7252 8.2. Request/Response 171 (overridden by https://rfc-editor.org/rfc/rfc7967[RFC7967] No-Response option) 176 https://rfc-editor.org/rfc/rfc7967[RFC7967] No-Response option) for multicast 181 https://rfc-editor.org/rfc/rfc7967[RFC7967] No-Response option) for multicast 186 https://rfc-editor.org/rfc/rfc7967[RFC7967] No-Response option) for multicast 191 "https://rfc-editor.org/rfc/rfc3986#section-2.1[RFC3986 2.1. Percent-Encoding]". 597 "https://rfc-editor.org/rfc/rfc7252[RFC7252: The Constrained Application Protocol (CoAP)]" 599 "https://rfc-editor.org/rfc/rfc3986[RFC3986: Uniform Resource Identifier (URI): Generic Syntax]"
|
D | coap_websockets.txt.in | 75 "https://rfc-editor.org/rfc/rfc7252[RFC7252: The Constrained Application Protocol (CoAP)]" 77 "https://rfc-editor.org/rfc/rfc8323[RFC8323: CoAP (Constrained Application Protocol) over TCP, TLS,…
|
D | coap_attribute.txt.in | 51 See "https://rfc-editor.org/rfc/rfc6690#section-5[RFC6690 5. Examples]" for 174 "https://rfc-editor.org/rfc/rfc7252[RFC7252: The Constrained Application Protocol (CoAP)]" 176 "https://rfc-editor.org/rfc/rfc6690[RFC6690: Constrained RESTful Environments (CoRE) Link Format]"
|
D | coap_cache.txt.in | 78 "https://rfc-editor.org/rfc/rfc7252#section-5.6[RFC7252 5.6. Caching]" 80 "https://rfc-editor.org/rfc/rfc7641#section-2[RFC7641 2. The Observe Option]" 82 "https://rfc-editor.org/rfc/rfc8132#section-2[RFC8132 2. Fetch Method]". 283 * https://rfc-editor.org/rfc/rfc7959#section-4 413 "https://rfc-editor.org/rfc/rfc7252[RFC7252: The Constrained Application Protocol (CoAP)]" 415 "https://rfc-editor.org/rfc/rfc7959[RFC7959: Block-Wise Transfers in the Constrained Application Pr…
|
/third_party/libcoap/doc/ |
D | main.md | 25 * [RFC7252: The Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7252) 27 … Communication for the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7390) 29 …rving Resources in the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7641) 31 …-Wise Transfers in the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7959) 33 …ined Application Protocol (CoAP) Option for No Server Response](https://rfc-editor.org/rfc/rfc7967) 35 … FETCH Methods for the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc8132) 37 …onstrained Application Protocol) over TCP, TLS, and WebSockets](https://rfc-editor.org/rfc/rfc8323) 39 …quests" Response Code for the Constrained Application Protocol](https://rfc-editor.org/rfc/rfc8516) 41 … Object Security for Constrained RESTful Environments (OSCORE)](https://rfc-editor.org/rfc/rfc8613) 43 * [RFC8768: Constrained Application Protocol (CoAP) Hop-Limit Option](https://rfc-editor.org/rfc/rf… [all …]
|
/third_party/libcoap/ |
D | README.md | 42 * [RFC7252: The Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7252) 44 … Communication for the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7390) 46 …rving Resources in the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7641) 48 …-Wise Transfers in the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7959) 50 …ined Application Protocol (CoAP) Option for No Server Response](https://rfc-editor.org/rfc/rfc7967) 52 … FETCH Methods for the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc8132) 54 …onstrained Application Protocol) over TCP, TLS, and WebSockets](https://rfc-editor.org/rfc/rfc8323) 56 …quests" Response Code for the Constrained Application Protocol](https://rfc-editor.org/rfc/rfc8516) 58 … Object Security for Constrained RESTful Environments (OSCORE)](https://rfc-editor.org/rfc/rfc8613) 60 * [RFC8768: Constrained Application Protocol (CoAP) Hop-Limit Option](https://rfc-editor.org/rfc/rf… [all …]
|
D | README | 42 * [RFC7252: The Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7252) 44 … Communication for the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7390) 46 …rving Resources in the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7641) 48 …-Wise Transfers in the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7959) 50 …ined Application Protocol (CoAP) Option for No Server Response](https://rfc-editor.org/rfc/rfc7967) 52 … FETCH Methods for the Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc8132) 54 …onstrained Application Protocol) over TCP, TLS, and WebSockets](https://rfc-editor.org/rfc/rfc8323) 56 …quests" Response Code for the Constrained Application Protocol](https://rfc-editor.org/rfc/rfc8516) 58 … Object Security for Constrained RESTful Environments (OSCORE)](https://rfc-editor.org/rfc/rfc8613) 60 * [RFC8768: Constrained Application Protocol (CoAP) Hop-Limit Option](https://rfc-editor.org/rfc/rf… [all …]
|
/third_party/mbedtls/tests/suites/ |
D | test_suite_ecdsa.data | 41 ECDSA primitive rfc 4754 p256 45 ECDSA primitive rfc 4754 p384 49 ECDSA primitive rfc 4754 p521 93 ECDSA deterministic test vector rfc 6979 p192 sha1 [#1] 97 ECDSA deterministic test vector rfc 6979 p192 sha224 [#1] 101 ECDSA deterministic test vector rfc 6979 p192 sha256 [#1] 105 ECDSA deterministic test vector rfc 6979 p192 sha384 [#1] 109 ECDSA deterministic test vector rfc 6979 p192 sha512 [#1] 113 ECDSA deterministic test vector rfc 6979 p192 sha1 [#2] 117 ECDSA deterministic test vector rfc 6979 p192 sha224 [#2] [all …]
|
D | test_suite_ecdh.data | 24 ECDH primitive rfc 5903 p256 28 ECDH primitive rfc 5903 p384 32 ECDH primitive rfc 5903 p521 44 ECDH restartable rfc 5903 p256 restart enabled max_ops=0 (disabled) 48 ECDH restartable rfc 5903 p256 restart enabled max_ops=1 52 ECDH restartable rfc 5903 p256 restart enabled max_ops=10000 56 ECDH restartable rfc 5903 p256 restart enabled max_ops=250 60 ECDH restartable rfc 5903 p256 restart disabled max_ops=0 (disabled) 64 ECDH restartable rfc 5903 p256 restart disabled max_ops=1 68 ECDH restartable rfc 5903 p256 restart disabled max_ops=10000 [all …]
|
/third_party/skia/third_party/externals/brotli/scripts/dictionary/ |
D | step-01-download-rfc.py | 13 with open(path, "w") as rfc: 14 rfc.write(text)
|
D | step-02-rfc-to-bin.py | 10 with open(rfc_path, "r") as rfc: 11 lines = rfc.readlines()
|
/third_party/node/deps/openssl/openssl/providers/common/der/ |
D | EC.asn1 | 10 -- (https://www.rfc-editor.org/rfc/rfc3279.html#section-3) 67 -- (https://www.rfc-editor.org/rfc/rfc5758.html#section-3.2)
|
12345678