Searched refs:rfc (Results 1 – 25 of 117) sorted by relevance
12345
13 ${SSHKEYGEN} -q -e -f $OBJ/$t-key >$OBJ/$t-key-rfc || \17 ${SSHKEYGEN} -q -e -f $OBJ/$t-key.pub >$OBJ/$t-key-rfc.pub || \20 cmp $OBJ/$t-key-rfc $OBJ/$t-key-rfc.pub || \24 ${SSHKEYGEN} -q -i -f $OBJ/$t-key-rfc >$OBJ/$t-rfc-imported || \28 cmp $OBJ/$t-key-nocomment.pub $OBJ/$t-rfc-imported || \31 rm -f $OBJ/$t-key $OBJ/$t-key.pub $OBJ/$t-key-rfc $OBJ/$t-key-rfc.pub \32 $OBJ/$t-rfc-imported $OBJ/$t-key-nocomment.pub
8 :rfc:`2822` is the base standard that describes the format of email messages.9 It derives from the older :rfc:`822` standard which came into widespread use at10 a time when most email was composed of ASCII characters only. :rfc:`2822` is a18 :rfc:`2822`\ -compliant format. These RFCs include :rfc:`2045`, :rfc:`2046`,19 :rfc:`2047`, and :rfc:`2231`. The :mod:`email` package supports these standards43 field was properly :rfc:`2047` encoded. MIME-aware mail readers would show this75 Optional *continuation_ws* must be :rfc:`2822`\ -compliant folding whitespace,100 producing an :rfc:`2822`\ -compliant header using :rfc:`2047` rules, the114 split long ASCII lines on, in rough support of :rfc:`2822`'s *highest115 level syntactic breaks*. This doesn't affect :rfc:`2047` encoded lines.
58 Attempts to parse a date according to the rules in :rfc:`2822`. however, some60 guess correctly in such cases. *date* is a string containing an :rfc:`2822`86 Returns a date string as per :rfc:`2822`, e.g.::109 Returns a string suitable for an :rfc:`2822`\ -compliant116 Decode the string *s* according to :rfc:`2231`.121 Encode the string *s* according to :rfc:`2231`. Optional *charset* and129 When a header parameter is encoded in :rfc:`2231` format,136 :rfc:`2231` header is not known by Python; it defaults to ``us-ascii``.144 Decode parameters list according to :rfc:`2231`. *params* is a sequence of164 the POSIX standard while this module follows :rfc:`2822`.
16 message" as defined by the Internet standard :rfc:`2822`. [#]_ Such messages18 also defines a helper class :class:`AddressList` for parsing :rfc:`2822`20 :rfc:`2822` messages.62 parameter, a comma-separated list of :rfc:`2822` addresses to be parsed. (The97 Attempts to parse a date according to the rules in :rfc:`2822`. however, some99 guess correctly in such cases. *date* is a string containing an :rfc:`2822`114 while this module follows :rfc:`2822`.) If the input string has no timezone,157 to index it) if the line is a legal :rfc:`2822` header; otherwise returns351 .. [#] This module originally conformed to :rfc:`822`, hence the name. Since then,352 :rfc:`2822` has been released as an update to :rfc:`822`. This module should be[all …]
26 Raised under some error conditions when parsing the :rfc:`2822` headers of a32 first :rfc:`2822` header of the message, finding a continuation line before the33 first :rfc:`2822` header is found, or finding a line in the headers which is39 Raised under some error conditions when parsing the :rfc:`2822` headers of a
17 defined in :rfc:`1521`: "MIME (Multipurpose Internet Mail Extensions) Part One:31 "Q"-encoded headers as described in :rfc:`1522`: "MIME (Multipurpose Internet43 and tabs appearing at the end of lines are always encoded, as per :rfc:`1521`.
24 :rfc:`2109` and :rfc:`2068` specifications. It has since been discovered that43 Exception failing because of :rfc:`2109` invalidity: incorrect attributes,98 :rfc:`2109` - HTTP State Management Mechanism162 Abstract a key/value pair, which has some :rfc:`2109` attributes.165 :rfc:`2109` attributes, which are
65 Following the syntax specifications in :rfc:`1808`, urlparse recognizes190 of the URL (see :rfc:`2396`) is wanted. A separate function is needed to279 :rfc:`3986` - Uniform Resource Identifiers285 :rfc:`2732` - Format for Literal IPv6 Addresses in URL's.288 :rfc:`2396` - Uniform Resource Identifiers (URI): Generic Syntax292 :rfc:`2368` - The mailto URL scheme.295 :rfc:`1808` - Relative Uniform Resource Locators300 :rfc:`1738` - Uniform Resource Locators (URL)
15 MIME and other :rfc:`2822`\ -based message documents. It subsumes most of the19 messages to SMTP (:rfc:`2821`), NNTP, or other servers; those are functions of22 :rfc:`2822`, such MIME-related RFCs as :rfc:`2045`, :rfc:`2046`, :rfc:`2047`,23 and :rfc:`2231`.121 * Fixes have been added for :rfc:`2231` support which can change some of the346 .. [#] Delivery Status Notifications (DSN) are defined in :rfc:`1894`.
12 This module provides data encoding and decoding as specified in :rfc:`3548`.20 in :rfc:`3548` (normal, and URL- and filesystem-safe). The legacy93 :rfc:`3548` allows for optional mapping of the digit 0 (zero) to the letter O173 …:rfc:`1521` - MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and…
19 details of SMTP and ESMTP operation, consult :rfc:`821` (Simple Mail Transfer20 Protocol) and :rfc:`1869` (SMTP Service Extensions).140 :rfc:`821` - Simple Mail Transfer Protocol144 :rfc:`1869` - SMTP Service Extensions238 tuple consisting of code 250 and a full :rfc:`822` address (including human293 Send mail. The required arguments are an :rfc:`822` from-address string, a list294 of :rfc:`822` to-address strings (a bare string will be treated as a list with 1366 example doesn't do any processing of the :rfc:`822` headers. In particular, the
17 described in :rfc:`1014`, written by Sun Microsystems, Inc. June 1987. It39 :rfc:`1014` - XDR: External Data Representation Standard41 originally written. It has apparently been obsoleted by :rfc:`1832`.43 :rfc:`1832` - XDR: External Data Representation Standard
11 :rfc:`7159` (which obsoletes :rfc:`4627`) and by15 (although it is not a strict subset of JavaScript [#rfc-errata]_ ).497 The JSON format is specified by :rfc:`7159` and by584 The old version of JSON specified by the obsolete :rfc:`4627` required that587 boolean, number, or string value. :rfc:`7159` removed that restriction, and619 .. [#rfc-errata] As noted in `the errata for RFC 7159620 <https://www.rfc-editor.org/errata_search.php?rfc=7159>`_,
20 The mailcap format is documented in :rfc:`1524`, "A User Agent Configuration36 MIME type or alter the existing body data. See :rfc:`1524` for a complete list
14 Headers are :rfc:`2822` style field names and values where the field name and172 message's :rfc:`2822` headers. Note that there are some semantic differences323 :rfc:`2045`, messages always have a default type, :meth:`get_content_type`326 :rfc:`2045` defines a message's default type to be :mimetype:`text/plain`330 :rfc:`2045` mandates that the default type be :mimetype:`text/plain`.400 can either be a string, or a 3-tuple if the parameter was :rfc:`2231`408 :rfc:`2231`, you can collapse the parameter value by calling431 parameter value will be appended as per :rfc:`2045`.438 according to :rfc:`2231`. Optional *language* specifies the RFC 2231
15 generating version 1, 3, 4, and 5 UUIDs as specified in :rfc:`4122`.199 Specifies the UUID layout given in :rfc:`4122`.214 :rfc:`4122` - A Universally Unique IDentifier (UUID) URN Namespace
15 http://www.ietf.org/rfc/rfc1951.txt17 http://www.ietf.org/rfc/rfc1950.txt19 http://www.ietf.org/rfc/rfc1952.txt
47 all, scheme, rfc, pep, selfdot, name = match.groups()51 elif rfc:52 url = 'http://www.rfc-editor.org/rfc/rfc%d.txt' % int(rfc)
26 <ulink url="http://tools.ietf.org/rfc/rfc903.txt">RARP</ulink>45 <ulink url="http://tools.ietf.org/rfc/rfc951.txt">BOOTP</ulink>47 <ulink url="http://tools.ietf.org/rfc/rfc2131.txt">DHCP</ulink> protocols.
96 <ulink url="http://tools.ietf.org/rfc/rfc792.txt">101 <ulink url="http://tools.ietf.org/rfc/rfc792.txt">106 <ulink url="http://tools.ietf.org/rfc/rfc791.txt">
5 # http://www.rfc-editor.org/rfc/rfc4646.txt
366 String javaName, int value, int rfc, int sinceJavaVersion, int sinceAndroidVersion) { in CipherSuite() argument
54 // See [https://www.ietf.org/rfc/rfc3339.txt](https://www.ietf.org/rfc/rfc3339.txt).
18 original [Netscape spec from 1994](https://curl.haxx.se/rfc/cookie_spec.html).20 In 2011, [RFC6265](https://www.ietf.org/rfc/rfc6265.txt) was finally