<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.3.13) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>


<rfc ipr="trust200902" docName="draft-ietf-calext-vcard4-bis-01" category="std" consensus="true" submissionType="IETF" obsoletes="6350" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="vCard">vCard Format Specification</title>

    <author fullname="Ricardo Signes" role="editor">
      <organization>Fastmail</organization>
      <address>
        <email>rjbs@semiotic.systems</email>
      </address>
    </author>

    <date year="2026" month="November" day="18"/>

    <area>Applications and Real-Time</area>
    <workgroup>Calendar Extensions</workgroup>
    <keyword>vcard</keyword>

    <abstract>


<?line 88?>

<t>This document defines the vCard data format for representing and
exchanging a variety of information about individuals and other
entities (e.g., formatted and structured name and delivery addresses,
email address, multiple telephone numbers, photograph, logo, audio
clips, etc.).  This document obsoletes RFC 6350.</t>



    </abstract>



  </front>

  <middle>


<?line 96?>

<section anchor="introduction"><name>Introduction</name>

<t>Electronic address books have become ubiquitous.  Their increased
presence on portable, connected devices as well as the diversity of
platforms that exchange contact data call for a standard.  This memo
defines the vCard format, which allows the capture and exchange of
information normally stored within an address book or directory
application.</t>

<t>A high-level overview of the differences from RFCs 2425 and 2426 can
be found in <xref target="changes-from-2426"></xref>.  A summary of the changes from
<xref target="RFC6350"/> can be found in <xref target="changes-from-6350"></xref>.</t>

</section>
<section anchor="conventions"><name>Conventions</name>

<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
<xref target="RFC2119"/>.</t>

</section>
<section anchor="vcard-format-specification"><name>vCard Format Specification</name>

<t>The text/vcard MIME content type (hereafter known as "vCard"; see
<xref target="media-type-reg"></xref>) contains contact information, typically pertaining to a
single contact or group of contacts.  The content consists of one or
more lines in the format given below.</t>

<section anchor="charset"><name>Charset</name>

<t>The charset (see <xref target="RFC3536"/> for internationalization terminology) for
vCard is UTF-8 as defined in <xref target="RFC3629"/>.  There is no way to override
this.  It is invalid to specify a value other than "UTF-8" in the
"charset" MIME parameter (see <xref target="media-type-reg"></xref>).</t>

</section>
<section anchor="line-folding"><name>Line Delimiting and Folding</name>

<t>Individual lines within vCard are delimited by the <xref target="RFC5322"/> line
break, which is a CRLF sequence (U+000D followed by U+000A).  Long
logical lines of text can be split into a multiple-physical-line
representation using the following folding technique.  Content lines
SHOULD be folded to a maximum width of 75 octets, excluding the line
break.  Multi-octet characters MUST remain contiguous.  The rationale
for this folding process can be found in <xref target="RFC5322"/>, Section 2.1.1.</t>

<t>A logical line MAY be continued on the next physical line anywhere
between two characters by inserting a CRLF immediately followed by a
single white space character (space (U+0020) or horizontal tab
(U+0009)).  The folded line MUST contain at least one character.  Any
sequence of CRLF followed immediately by a single white space
character is ignored (removed) when processing the content type.  For
example, the line:</t>

<figure><artwork><![CDATA[
  NOTE:This is a long description that exists on a long line.
]]></artwork></figure>

<t>can be represented as:</t>

<figure><artwork><![CDATA[
  NOTE:This is a long description
    that exists on a long line.
]]></artwork></figure>

<t>It could also be represented as:</t>

<figure><artwork><![CDATA[
  NOTE:This is a long descrip
   tion that exists o
   n a long line.
]]></artwork></figure>

<t>The process of moving from this folded multiple-line representation
of a property definition to its single-line representation is called
unfolding.  Unfolding is accomplished by regarding CRLF immediately
followed by a white space character (namely, HTAB (U+0009) or SPACE
(U+0020)) as equivalent to no characters at all (i.e., the CRLF and
single white space character are removed).</t>

<t>Note: It is possible for very simple implementations to generate
improperly folded lines in the middle of a UTF-8 multi-octet
sequence.  For this reason, implementations SHOULD unfold lines in
such a way as to properly restore the original sequence.</t>

<t>Note: Unfolding is done differently than in <xref target="RFC5322"/>.  Unfolding
in <xref target="RFC5322"/> only removes the CRLF, not the space following it.</t>

<t>Folding is done after any content encoding of a type value.
Unfolding is done before any decoding of a type value in a content
line.</t>

</section>
<section anchor="abnf-format-definition"><name>ABNF Format Definition</name>

<t>The following ABNF uses the notation of <xref target="RFC5234"/>, which also defines
CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.</t>

<figure><sourcecode type="abnf"><![CDATA[
vcard-entity = 1*vcard

vcard = "BEGIN:VCARD" CRLF
        "VERSION:4.0" CRLF
        1*contentline
        "END:VCARD" CRLF
  ; A vCard object MUST include the VERSION and FN properties.
  ; VERSION MUST come immediately after BEGIN:VCARD.

contentline = [group "."] name *(";" param) ":" value CRLF
  ; When parsing a content line, folded lines must first
  ; be unfolded according to the unfolding procedure
  ; described in Section 3.2.
  ; When generating a content line, lines longer than 75
  ; characters SHOULD be folded according to the folding
  ; procedure described in Section 3.2.

group = 1*(ALPHA / DIGIT / "-")
name  = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
      / "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL"
      / "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE"
      / "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES"
      / "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP"
      / "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
      / "BIRTHPLACE" / "DEATHPLACE" / "DEATHDATE"
      / iana-token / x-name
  ; Parsing of the param and value is based on the "name" as
  ; defined in ABNF sections below.
  ; Group and name are case-insensitive.

iana-token = 1*(ALPHA / DIGIT / "-")
  ; identifier registered with IANA

x-name = "x-" 1*(ALPHA / DIGIT / "-")
  ; Names that begin with "x-" or "X-" are
  ; reserved for experimental use, not intended for released
  ; products, or for use in bilateral agreements.

param = language-param / value-param / pref-param / pid-param
      / type-param / geo-parameter / tz-parameter / sort-as-param
      / calscale-param / any-param
  ; Allowed parameters depend on property name.

param-value = *SAFE-CHAR / ( DQUOTE *QSAFE-CHAR DQUOTE )

any-param  = (iana-token / x-name) "=" param-value *("," param-value)

NON-ASCII = UTF8-2 / UTF8-3 / UTF8-4
  ; UTF8-{2,3,4} are defined in [RFC3629]

QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII
  ; Any character except CTLs, DQUOTE but including HTAB

SAFE-CHAR = WSP / "!" / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
  ; Any character except CTLs, DQUOTE, ",", ";", ":" but
  ; including HTAB
]]></sourcecode></figure>

<t>A line that begins with a white space character is a continuation of
the previous line, as described in <xref target="line-folding"></xref>.  The white space
character and immediately preceeding CRLF should be discarded when
reconstructing the original line.  Note that this line-folding
convention differs from that found in <xref target="RFC5322"/>, in that the sequence
<spanx style="verb">&lt;CRLF&gt;&lt;WSP&gt;</spanx> found anywhere in the content indicates a continued line
and should be removed.</t>

<t>Property names and parameter names are case-insensitive (e.g., the
property name "fn" is the same as "FN" and "Fn").  Parameter values
MAY be case-sensitive or case-insensitive, depending on their
definition.  Parameter values that are not explicitly defined as
being case-sensitive are case-insensitive.  Based on experience with
vCard 3 interoperability, it is RECOMMENDED that property and
parameter names be upper-case on output.</t>

<t>The group construct is used to group related properties together.
The group name is a syntactic convention used to indicate that all
property names prefaced with the same group name SHOULD be grouped
together when displayed by an application.  It has no other
significance.  Implementations that do not understand or support
grouping MAY simply strip off any text before a "." to the left of
the type name and present the types and values as normal.</t>

<t>Property cardinalities are indicated using the following notation,
which is based on ABNF (see <xref target="RFC5234"/>, Section 3.6):</t>

<texttable>
      <ttcol align='center'>Cardinality</ttcol>
      <ttcol align='left'>Meaning</ttcol>
      <c>1</c>
      <c>Exactly one instance per vCard MUST be present.</c>
      <c>*1</c>
      <c>Exactly one instance per vCard MAY be present.</c>
      <c>1*</c>
      <c>One or more instances per vCard MUST be present.</c>
      <c>*</c>
      <c>One or more instances per vCard MAY be present.</c>
</texttable>

<t>Properties defined in a vCard instance may have multiple values
depending on the property cardinality.  The general rule for encoding
multi-valued properties is to simply create a new content line for
each value (including the property name).  However, it should be
noted that some value types support encoding multiple values in a
single content line by separating the values with a comma ",".  This
approach has been taken for several of the content types defined
below (date, time, integer, float).  A property whose value is
structured, such as ADR or ORG, MUST NOT combine multiple instances on a
single content line; each instance is placed on its own line.</t>

</section>
<section anchor="value-escaping"><name>Property Value Escaping</name>

<t>Within a property value, certain characters are escaped using a BACKSLASH
character (U+005C).  A COMMA (U+002C) or a SEMICOLON (U+003B) is escaped by
preceding it with a BACKSLASH, so that it is not taken for a separator; a
literal BACKSLASH is written as two BACKSLASH characters; and a NEWLINE
(U+000A) is encoded as a BACKSLASH followed by an 'n' (U+006E) or an 'N'
(U+004E).  Which of these characters must be escaped depends on the value's
type.</t>

<t>A "text" value MUST escape any COMMA it contains, even for a property that
does not allow multiple values (for consistency), and MUST escape any
BACKSLASH or NEWLINE.  It MAY escape a SEMICOLON but need not, because
within a "text" value a SEMICOLON is ordinary content rather than a
separator.</t>

<t>A "component" value -- the building block of structured properties like
those of N, ADR, and ORG values -- MUST escape any COMMA, SEMICOLON,
BACKSLASH, or NEWLINE it contains, even where the structure does not
allow multiple values (for consistency).</t>

<t>Outside of "text" and "component" values, none of these characters is
escaped.  Most value types cannot contain any of them, and although a
"uri" value may contain a COMMA or a SEMICOLON (<xref target="RFC3986"/>), a URI is
never in a list or component list.  For tolerance of vCards produced
under earlier specifications, a parser MAY accept a backslash-escaped
COMMA or SEMICOLON within a "uri" value as the literal character.</t>

<t>A few properties define a structured value as a fixed sequence of fields
rather than from "component" values; CLIENTPIDMAP and GENDER are
examples in this document.  In each, the field preceding the semicolon
cannot itself contain a semicolon, so the grammar locates the separator
unambiguously; the semicolon is not escaped, and each field is
interpreted according to its own type.</t>

<t>In all other cases, escaping MUST NOT be used.</t>

</section>
<section anchor="param-escaping"><name>Parameter Value Escaping</name>

<t>Except for LABEL line breaks as described below, the BACKSLASH escaping
described in <xref target="value-escaping"></xref> is not used in property parameter values.
This section describes the escaping mechanism originally defined in
<xref target="RFC6868"/>, which uses the CIRCUMFLEX ACCENT character (U+005E), "^",
as the escape character.</t>

<t>The parameter's definition determines which grammar applies, including when
that definition is in an extension.  Caret escaping applies to each value
element whose grammar uses the "param-value" rule, whether the element is
quoted or unquoted.  When the generic "any-param" rule applies, it supplies
"param-value" for each value element.</t>

<t>For example, ALTID, SORT-AS, LABEL, and the "param-value" alternative of TZ
use this escaping.  GEO and the quoted URI alternative of TZ use the URI
grammar and do not use this escaping.</t>

<t>A quoted TZ value matches both alternatives of the TZ grammar, so a parser
cannot always tell from the syntax alone which one applies.  This ambiguity
is harmless.  A valid URI contains no CIRCUMFLEX ACCENT, DQUOTE, or line
break (<xref target="RFC3986"/>), so encoding it under these rules changes nothing, and
decoding a valid URI under these rules leaves it unchanged.  A parser MAY
therefore apply the decoding rules to any TZ parameter value.</t>

<t>When generating a "param-value" element, the following encodings MUST be
applied, subject to the LABEL exception below:</t>

<t><list style="symbols">
  <t>a line break is encoded as ^n (U+005E, U+006E);</t>
  <t>a CIRCUMFLEX ACCENT (U+005E) is encoded as ^^ (U+005E, U+005E); and</t>
  <t>a DQUOTE (U+0022) is encoded as ^' (U+005E, U+0027).</t>
</list></t>

<t>The LABEL parameter of the ADR property (<xref target="prop-adr"></xref>) is an exception:
for compatibility with <xref target="RFC6350"/>, line breaks in its value SHOULD be
encoded as \n rather than ^n.</t>

<t>Before decoding escapes, parsers MUST unfold the content line as
described in <xref target="line-folding"></xref>, identify the individual parameter value
elements, and remove any enclosing DQUOTE delimiters.  Parsers MUST apply
the following rules to each "param-value" element in a single pass from
left to right.  Each recognized escape consumes both of its input
characters.  Characters produced by decoding MUST NOT be scanned again
for escapes.</t>

<t><list style="symbols">
  <t>the sequence ^n (U+005E, U+006E) is decoded into a line break, represented
as appropriate to the system;</t>
  <t>the sequence ^^ (U+005E, U+005E) is decoded into a CIRCUMFLEX ACCENT
(U+005E);</t>
  <t>the sequence ^' (U+005E, U+0027) is decoded into a DQUOTE (U+0022);</t>
  <t>in the LABEL parameter of ADR, the sequences \n (U+005C, U+006E) and \N
(U+005C, U+004E) are also decoded into a line break, as they are in
property values; and</t>
  <t>any character that does not begin a recognized escape is copied unchanged.
Decoding resumes at the next input character, if any.</t>
</list></t>

<t>For example, <spanx style="verb">^^n</spanx> decodes to the two literal characters <spanx style="verb">^n</spanx>.  Caret
escaping is case-sensitive, so <spanx style="verb">^N</spanx> is left in place.  In LABEL, <spanx style="verb">^\n</spanx>
decodes to a literal caret followed by a line break.  Any comparison of
parameter values MUST use the decoded values.</t>

<t>This mechanism defines no other character escapes.  A parameter value
containing a COLON, SEMICOLON, or COMMA is quoted instead, as described in
<xref target="property-parameters"></xref>.</t>

<t>When converting between the text format described in this document and an
alternative representation such as the XML representation of <xref target="RFC6351"/>,
implementations MUST apply the rules in this section when encoding
"param-value" elements in the text format and when decoding them for use
in the alternative representation.</t>

<t>Example: The following GEO property has an "X-ADDRESS" parameter whose value
includes several line breaks.  The parameter value is quoted because it
contains a COMMA.</t>

<figure><artwork><![CDATA[
GEO;X-ADDRESS="Pittsburgh Pirates^n115 Federal St^nPitt
 sburgh, PA 15212":geo:40.446816,-80.00566
]]></artwork></figure>

<t>The unescaped parameter value, where each line is terminated by a line
break, is:</t>

<figure><artwork><![CDATA[
Pittsburgh Pirates
115 Federal St
Pittsburgh, PA 15212
]]></artwork></figure>

</section>
</section>
<section anchor="property-value-data-types"><name>Property Value Data Types</name>

<t>Standard value types are defined below.</t>

<figure><sourcecode type="abnf"><![CDATA[
value = text
      / text-list
      / date-list
      / time-list
      / date-time-list
      / date-and-or-time-list
      / timestamp-list
      / boolean
      / integer-list
      / float-list
      / URI               ; from Section 3 of [RFC3986]
      / utc-offset
      / Language-Tag
      / iana-valuespec
  ; Actual value type depends on property name and VALUE parameter.

text = *TEXT-CHAR

TEXT-CHAR = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
          / %x21-2B / %x2D-5B / %x5D-7E
   ; Backslashes, commas, and newlines must be encoded;
   ; semicolons may be.

COMPONENT-CHAR = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
          / %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E

component = *COMPONENT-CHAR
list-component = component *("," component)

text-list             = text             *("," text)
date-list             = date             *("," date)
time-list             = time             *("," time)
date-time-list        = date-time        *("," date-time)
date-and-or-time-list = date-and-or-time *("," date-and-or-time)
timestamp-list        = timestamp        *("," timestamp)
integer-list          = integer          *("," integer)
float-list            = float            *("," float)

boolean = "TRUE" / "FALSE"
integer = [sign] 1*DIGIT
float   = [sign] 1*DIGIT ["." 1*DIGIT]

sign = "+" / "-"

year   = 4DIGIT  ; 0000-9999
month  = 2DIGIT  ; 01-12
day    = 2DIGIT  ; 01-28/29/30/31 depending on month and leap year
hour   = 2DIGIT  ; 00-23
minute = 2DIGIT  ; 00-59
second = 2DIGIT  ; 00-58/59/60 depending on leap second
zone   = utc-designator / utc-offset
utc-designator = %x5A  ; uppercase "Z"

date          = year    [month  day]
              / year "-" month
              / "--"     month [day]
              / "--"      "-"   day
date-noreduc  = year     month  day
              / "--"     month  day
              / "--"      "-"   day
date-complete = year     month  day

time          = hour [minute [second]] [zone]
              /  "-"  minute [second]
              /  "-"   "-"    second
time-notrunc  = hour [minute [second]] [zone]
time-complete = hour  minute  second   [zone]

time-designator = %x54  ; uppercase "T"
date-time = date-noreduc  time-designator time-notrunc
timestamp = date-complete time-designator time-complete

date-and-or-time = date-time / date / time-designator time

utc-offset = sign hour [minute]

Language-Tag = <Language-Tag, defined in [RFC5646], Section 2.1>

iana-valuespec = <value-spec, see Section 10.2.5>
               ; a publicly defined valuetype format, registered
               ; with IANA, as defined in Section 10.2.5 of this
               ; document.
]]></sourcecode></figure>

<section anchor="text"><name>TEXT</name>

<t>"text": The "text" value type should be used to identify values that
contain human-readable text.  As for the language, it is controlled
by the LANGUAGE property parameter defined in <xref target="param-language"></xref>.</t>

<t>Examples for "text":</t>

<figure><artwork><![CDATA[
    this is a text value
    this is one value,this is another
    this is a single value\, with a comma encoded
]]></artwork></figure>

<t>A formatted text line break in a text value type MUST be represented
as the character sequence backslash (U+005C) followed by a Latin
small letter n (U+006E) or a Latin capital letter N (U+004E), that
is, "\n" or "\N".</t>

<t>For example, a multiple line NOTE value of:</t>

<figure><artwork><![CDATA[
    Mythical Manager
    Hyjinx Software Division
    BabsCo, Inc.
]]></artwork></figure>

<t>could be represented as:</t>

<figure><artwork><![CDATA[
    NOTE:Mythical Manager\nHyjinx Software Division\n
     BabsCo\, Inc.\n
]]></artwork></figure>

<t>demonstrating the \n literal formatted line break technique, the
CRLF-followed-by-space line folding technique, and the backslash
escape technique.</t>

</section>
<section anchor="uri"><name>URI</name>

<t>"uri": The "uri" value type should be used to identify values that
are referenced by a Uniform Resource Identifier (URI) instead of
encoded in-line.  These value references might be used if the value
is too large, or otherwise undesirable to include directly.  The
format for the URI is as defined in Section 3 of <xref target="RFC3986"/>.  Note
that the value of a property of type "uri" is what the URI points to,
not the URI itself.</t>

<t>Examples for "uri":</t>

<figure><artwork><![CDATA[
    http://www.example.com/my/picture.jpg
    ldap://ldap.example.com/cn=babs%20jensen
]]></artwork></figure>

</section>
<section anchor="date-time-date-time-date-and-or-time-and-timestamp"><name>DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP</name>

<t>"date", "time", "date-time", "date-and-or-time", and "timestamp":
Each of these value types is based on the definitions in
<xref target="ISO.8601.2004"/>.  Multiple such values can be specified using the
comma-separated notation.</t>

<t>Only the basic format is supported.</t>

<section anchor="date"><name>DATE</name>

<t>A calendar date as specified in <xref target="ISO.8601.2004"/>, Section 4.1.2.</t>

<t>Reduced accuracy, as specified in <xref target="ISO.8601.2004"/>, Sections 4.1.2.3
a) and b), but not c), is permitted.</t>

<t>Expanded representation, as specified in <xref target="ISO.8601.2004"/>, Section
4.1.4, is forbidden.</t>

<t>Truncated representation, as specified in <xref target="ISO.8601.2000"/>, Sections
5.2.1.3 d), e), and f), is permitted.</t>

<t>Examples for "date":</t>

<figure><artwork><![CDATA[
          19850412
          1985-04
          1985
          --0412
          ---12
]]></artwork></figure>

<t>Note the use of YYYY-MM in the second example above.  YYYYMM is
disallowed to prevent confusion with YYMMDD.  Note also that
YYYY-MM-DD is disallowed since we are using the basic format instead
of the extended format.</t>

</section>
<section anchor="type-time"><name>TIME</name>

<t>A time of day as specified in <xref target="ISO.8601.2004"/>, Section 4.2.</t>

<t>Reduced accuracy, as specified in <xref target="ISO.8601.2004"/>, Section 4.2.2.3,
is permitted.</t>

<t>Representation with decimal fraction, as specified in
<xref target="ISO.8601.2004"/>, Section 4.2.2.4, is forbidden.</t>

<t>The midnight hour is always represented by 00, never 24 (see
<xref target="ISO.8601.2004"/>, Section 4.2.3).</t>

<t>Truncated representation, as specified in <xref target="ISO.8601.2000"/>, Sections
5.3.1.4 a), b), and c), is permitted.</t>

<t>Examples for "time":</t>

<figure><artwork><![CDATA[
          102200
          1022
          10
          -2200
          --00
          102200Z
          102200-0800
]]></artwork></figure>

</section>
<section anchor="date-time"><name>DATE-TIME</name>

<t>A date and time of day combination as specified in <xref target="ISO.8601.2004"/>,
Section 4.3.</t>

<t>Truncation of the date part, as specified in <xref target="ISO.8601.2000"/>, Section
5.4.2 c), is permitted.</t>

<t>Examples for "date-time":</t>

<figure><artwork><![CDATA[
          19961022T140000
          --1022T1400
          ---22T14
]]></artwork></figure>

</section>
<section anchor="date-and-or-time"><name>DATE-AND-OR-TIME</name>

<t>Either a DATE-TIME, a DATE, or a TIME value.  To allow unambiguous
interpretation, a stand-alone TIME value is always preceded by a "T".</t>

<t>Examples for "date-and-or-time":</t>

<figure><artwork><![CDATA[
          19961022T140000
          --1022T1400
          ---22T14
          19850412
          1985-04
          1985
          --0412
          ---12
          T102200
          T1022
          T10
          T-2200
          T--00
          T102200Z
          T102200-0800
]]></artwork></figure>

</section>
<section anchor="timestamp"><name>TIMESTAMP</name>

<t>A complete date and time of day combination as specified in
<xref target="ISO.8601.2004"/>, Section 4.3.2.</t>

<t>Examples for "timestamp":</t>

<figure><artwork><![CDATA[
          19961022T140000
          19961022T140000Z
          19961022T140000-05
          19961022T140000-0500
]]></artwork></figure>

</section>
</section>
<section anchor="boolean"><name>BOOLEAN</name>

<t>"boolean": The "boolean" value type is used to express boolean
values.  These values are case-insensitive.</t>

<t>Examples:</t>

<figure><artwork><![CDATA[
    TRUE
    false
    True
]]></artwork></figure>

</section>
<section anchor="integer"><name>INTEGER</name>

<t>"integer": The "integer" value type is used to express signed
integers in decimal format.  If sign is not specified, the value is
assumed positive "+".  Multiple "integer" values can be specified
using the comma-separated notation.  The maximum value is
9223372036854775807, and the minimum value is -9223372036854775808.
These limits correspond to a signed 64-bit integer using two's-
complement arithmetic.</t>

<t>Examples:</t>

<figure><artwork><![CDATA[
    1234567890
    -1234556790
    +1234556790,432109876
]]></artwork></figure>

</section>
<section anchor="float"><name>FLOAT</name>

<t>"float": The "float" value type is used to express real numbers.  If
sign is not specified, the value is assumed positive "+".  Multiple
"float" values can be specified using the comma-separated notation.
Implementations MUST support a precision equal or better than that of
the IEEE "binary64" format <xref target="IEEE.754.2008"/>.</t>

<t>Note: Scientific notation is disallowed.  Implementers wishing to
use their favorite language's %f formatting should be careful.</t>

<t>Examples:</t>

<figure><artwork><![CDATA[
    20.30
    1000000.0000001
    1.333,3.14
]]></artwork></figure>

</section>
<section anchor="utc-offset"><name>UTC-OFFSET</name>

<t>"utc-offset": The "utc-offset" value type specifies that the property
value is a signed offset from UTC.  This value type can be specified
in the TZ property.</t>

<t>The value type is an offset from Coordinated Universal Time (UTC).
It is specified as a positive or negative difference in units of
hours and minutes (e.g., +hhmm).  The time is specified as a 24-hour
clock.  Hour values are from 00 to 23, and minute values are from 00
to 59.  Hour and minutes are 2 digits with high-order zeroes required
to maintain digit count.  The basic format for ISO 8601 UTC offsets
MUST be used.</t>

</section>
<section anchor="language-tag"><name>LANGUAGE-TAG</name>

<t>"language-tag": A single language tag, as defined in <xref target="RFC5646"/>.</t>

</section>
</section>
<section anchor="property-parameters"><name>Property Parameters</name>

<t>A property can have attributes associated with it.  These "property
parameters" contain meta-information about the property or the
property value.  In some cases, the property parameter can be multi-
valued in which case the property parameter value elements are
separated by a COMMA (U+002C).</t>

<t>Property parameter value elements that contain the COLON (U+003A),
SEMICOLON (U+003B), or COMMA (U+002C) character separators MUST be
specified as quoted-string text values.  The DQUOTE (U+0022) character
is used as a delimiter for parameter values that contain restricted
characters or URI text, and so MUST NOT appear literally within a
parameter value.  Where a parameter's value is defined using the
"param-value" rule, a DQUOTE or a line break can be represented using
the escaping described in <xref target="param-escaping"></xref>.</t>

<t>Applications MUST ignore x-param and iana-param values they don't
recognize.</t>

<section anchor="param-language"><name>LANGUAGE</name>

<t>The LANGUAGE property parameter is used to identify data in multiple
languages.  There is no concept of "default" language, except as
specified by any "Content-Language" MIME header parameter that is
present <xref target="RFC3282"/>.  The value of the LANGUAGE property parameter is a
language tag as defined in Section 2 of <xref target="RFC5646"/>.</t>

<t>Examples:</t>

<figure><artwork><![CDATA[
  ROLE;LANGUAGE=tr:hoca
]]></artwork></figure>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
language-param = "LANGUAGE=" Language-Tag
  ; Language-Tag is defined in section 2.1 of RFC 5646
]]></sourcecode></figure>

</section>
<section anchor="param-value-type"><name>VALUE</name>

<t>The VALUE parameter is OPTIONAL, used to identify the value type
(data type) and format of the value.  The use of these predefined
formats is encouraged even if the value parameter is not explicitly
used.  By defining a standard set of value types and their formats,
existing parsing and processing code can be leveraged.  The
predefined data type values MUST NOT be repeated in COMMA-separated
value lists except within the N, NICKNAME, ADR, and CATEGORIES
properties.</t>

<t>Although the VALUE parameter is OPTIONAL, a property defined outside this
document whose default value type is not "text" SHOULD nonetheless
include it on each instance, stating the type explicitly.  A consumer
that does not recognize a property cannot determine its value type from
the property name alone, and so may mishandle a non-text value -- for
example, treating a COMMA within a URI value as a value separator.  See
<xref target="registering-elements"></xref> for the matching registration guidance.</t>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
value-param = "VALUE=" value-type

value-type = "text"
           / "uri"
           / "date"
           / "time"
           / "date-time"
           / "date-and-or-time"
           / "timestamp"
           / "boolean"
           / "integer"
           / "float"
           / "utc-offset"
           / "language-tag"
           / iana-token  ; registered as described in section 10.2.5
           / x-name
]]></sourcecode></figure>

</section>
<section anchor="pref"><name>PREF</name>

<t>The PREF parameter is OPTIONAL and is used to indicate that the
corresponding instance of a property is preferred by the vCard
author.  Its value MUST be an integer between 1 and 100 that
quantifies the level of preference.  Lower values correspond to a
higher level of preference, with 1 being most preferred.</t>

<t>When the parameter is absent, the default MUST be to interpret the
property instance as being least preferred.</t>

<t>Note that the value of this parameter is to be interpreted only in
relation to values assigned to other instances of the same property
in the same vCard.  A given value, or the absence of a value, MUST
NOT be interpreted on its own.</t>

<t>This parameter MAY be applied to any property that allows multiple
instances.</t>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
pref-param = "PREF=" (1*2DIGIT / "100")
                             ; An integer between 1 and 100.
]]></sourcecode></figure>

</section>
<section anchor="altid"><name>ALTID</name>

<t>The ALTID parameter is used to "tag" property instances as being
alternative representations of the same logical property.  For
example, translations of a property in multiple languages generates
multiple property instances having different LANGUAGE (<xref target="param-language"></xref>)
parameter that are tagged with the same ALTID value.</t>

<t>This parameter's value is treated as an opaque string.  Its sole
purpose is to be compared for equality against other ALTID parameter
values.</t>

<t>Two property instances are considered alternative representations of
the same logical property if and only if their names as well as the
value of their ALTID parameters are identical.  Property instances
without the ALTID parameter MUST NOT be considered an alternative
representation of any other property instance.  Values for the ALTID
parameter are not globally unique: they MAY be reused for different
property names.</t>

<t>Property instances having the same ALTID parameter value count as 1
toward cardinality.  Therefore, since N (<xref target="prop-n"></xref>) has
cardinality *1 and TITLE (<xref target="prop-title"></xref>) has cardinality *, these
three examples would be legal:</t>

<figure><artwork><![CDATA[
  N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
  N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
  (<U+XXXX> denotes a UTF8-encoded Unicode character.)

  TITLE;ALTID=1;LANGUAGE=fr:Patron
  TITLE;ALTID=1;LANGUAGE=en:Boss

  TITLE;ALTID=1;LANGUAGE=fr:Patron
  TITLE;ALTID=1;LANGUAGE=en:Boss
  TITLE;ALTID=2;LANGUAGE=en:Chief vCard Evangelist
]]></artwork></figure>

<t>while this one would not:</t>

<figure><artwork><![CDATA[
  N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
  N:Yamada;Taro;;;
  (Two instances of the N property.)
]]></artwork></figure>

<t>and these three would be legal but questionable:</t>

<figure><artwork><![CDATA[
  TITLE;ALTID=1;LANGUAGE=fr:Patron
  TITLE;ALTID=2;LANGUAGE=en:Boss
  (Should probably have the same ALTID value.)

  TITLE;ALTID=1;LANGUAGE=fr:Patron
  TITLE;LANGUAGE=en:Boss
  (Second line should probably have ALTID=1.)

  N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
  N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
  N;ALTID=1;LANGUAGE=en:Smith;John;;;
  (The last line should probably have ALTID=2.  But that would be
   illegal because N has cardinality *1.)
]]></artwork></figure>

<t>The ALTID property MAY also be used in many contexts other than with
the LANGUAGE parameter.  Here's an example with two representations
of the same photo in different file formats:</t>

<figure><artwork><![CDATA[
  PHOTO;ALTID=1:data:image/jpeg;base64,...
  PHOTO;ALTID=1;data:image/jp2;base64,...
]]></artwork></figure>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
altid-param = "ALTID=" param-value
]]></sourcecode></figure>

</section>
<section anchor="pid"><name>PID</name>

<t>The PID parameter is used to identify a specific property among
multiple instances.  It plays a role analogous to the UID property
(<xref target="prop-uid"></xref>) on a per-property instead of per-vCard basis.  It MAY
appear more than once in a given property.  It MUST NOT appear on
properties that may have only one instance per vCard.  Its value is
either a single small positive integer or a pair of small positive
integers separated by a dot.  Multiple values may be encoded in a
single PID parameter by separating the values with a comma ",".  See
<xref target="synchronization"></xref> for more details on its usage.</t>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
pid-param = "PID=" pid-value *("," pid-value)
pid-value = 1*DIGIT ["." 1*DIGIT]
]]></sourcecode></figure>

</section>
<section anchor="type"><name>TYPE</name>

<t>The TYPE parameter has multiple, different uses.  In general, it is a
way of specifying class characteristics of the associated property.
Most of the time, its value is a comma-separated subset of a
predefined enumeration.  In this document, the following properties
make use of this parameter: FN, NICKNAME, PHOTO, ADR, TEL, EMAIL,
IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES,
NOTE, SOUND, URL, KEY, FBURL, CALADRURI, and CALURI.  The TYPE
parameter MUST NOT be applied on other properties defined in this
document.</t>

<t>The "work" and "home" values act like tags.  The "work" value implies
that the property is related to an individual's work place, while the
"home" value implies that the property is related to an individual's
personal life.  When neither "work" nor "home" is present, it is
implied that the property is related to both an individual's work
place and personal life in the case that the KIND property's value is
"individual", or to none in other cases.</t>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
type-param = "TYPE=" type-value *("," type-value)

type-value = "work" / "home" / type-param-tel
           / type-param-related / iana-token / x-name
  ; This is further defined in individual property sections.
]]></sourcecode></figure>

</section>
<section anchor="mediatype"><name>MEDIATYPE</name>

<t>The MEDIATYPE parameter is used with properties whose value is a URI.
Its use is OPTIONAL.  It provides a hint to the vCard consumer
application about the media type <xref target="RFC2046"/> of the resource identified
by the URI.  Some URI schemes do not need this parameter.  For
example, the "data" scheme allows the media type to be explicitly
indicated as part of the URI <xref target="RFC2397"/>.  Another scheme, "http",
provides the media type as part of the URI resolution process, with
the Content-Type HTTP header <xref target="RFC2616"/>.  The MEDIATYPE parameter is
intended to be used with URI schemes that do not provide such
functionality (e.g., "ftp" <xref target="RFC1738"/>).</t>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
mediatype-param = "MEDIATYPE=" mediatype
mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
  ; "attribute" and "value" are from [RFC2045]
  ; "type-name" and "subtype-name" are from [RFC6838]
]]></sourcecode></figure>

</section>
<section anchor="calscale"><name>CALSCALE</name>

<t>The CALSCALE parameter is identical to the CALSCALE property in
iCalendar (see <xref target="RFC5545"/>, Section 3.7.1).  It is used to define the
calendar system in which a date or date-time value is expressed.  The
only value specified by iCalendar is "gregorian", which stands for
the Gregorian system.  It is the default when the parameter is
absent.  Additional values may be defined in extension documents and
registered with IANA (see <xref target="values-registries"></xref>).  A vCard implementation
MUST ignore properties with a CALSCALE parameter value that it does
not understand.</t>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
calscale-param = "CALSCALE=" calscale-value

calscale-value = "gregorian" / iana-token / x-name
]]></sourcecode></figure>

</section>
<section anchor="sort-as"><name>SORT-AS</name>

<t>The "sort-as" parameter is used to specify the string to be used for
national-language-specific sorting.  Without this information,
sorting algorithms could incorrectly sort this vCard within a
sequence of sorted vCards.  When this property is present in a vCard,
then the given strings are used for sorting the vCard.</t>

<t>This parameter's value is a comma-separated list that MUST have as
many or fewer elements as the corresponding property value has
components.  This parameter's value is case-sensitive.</t>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
sort-as-param = "SORT-AS=" sort-as-value

sort-as-value = param-value *("," param-value)
]]></sourcecode></figure>

<t>Examples: For the case of surname and given name sorting, the
following examples define common sort string usage with the N
property.</t>

<figure><artwork><![CDATA[
        FN:Rene van der Harten
        N;SORT-AS=Harten,Rene:van der Harten;Rene;J.;Sir;R.D.O.N.

        FN:Robert Pau Shou Chang
        N;SORT-AS=Pau Shou Chang,Robert:Shou Chang;Robert;Pau;;

        FN:Osamu Koura
        N;SORT-AS=Koura,Osamu:Koura;Osamu;;;

        FN:Oscar del Pozo
        N;SORT-AS=Pozo,Oscar:del Pozo Triscon;Oscar;;;

        FN:Chistine d'Aboville
        N;SORT-AS=Aboville,Christine:d'Aboville;Christine;;;

        FN:H. James de Mann
        N;SORT-AS=Mann,James:de Mann;Henry;James;;
]]></artwork></figure>

<t>If sorted by surname, the results would be:</t>

<figure><artwork><![CDATA[
        Christine d'Aboville
        Rene van der Harten
        Osamu Koura
        H. James de Mann
        Robert Pau Shou Chang
        Oscar del Pozo
]]></artwork></figure>

<t>If sorted by given name, the results would be:</t>

<figure><artwork><![CDATA[
        Christine d'Aboville
        H. James de Mann
        Osamu Koura
        Oscar del Pozo
        Rene van der Harten
        Robert Pau Shou Chang
]]></artwork></figure>

</section>
<section anchor="geo"><name>GEO</name>

<t>The GEO parameter can be used to indicate global positioning
information that is specific to an address.  Its value is the same as
that of the GEO property (see <xref target="prop-geo"></xref>).</t>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
geo-parameter = "GEO=" DQUOTE URI DQUOTE
]]></sourcecode></figure>

</section>
<section anchor="tz"><name>TZ</name>

<t>The TZ parameter can be used to indicate time zone information that
is specific to an address.  Its value is the same as that of the TZ
property.</t>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)
]]></sourcecode></figure>

</section>
</section>
<section anchor="vcard-properties"><name>vCard Properties</name>

<t>What follows is an enumeration of the standard vCard properties.</t>

<section anchor="general-properties"><name>General Properties</name>

<section anchor="begin"><name>BEGIN</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To denote the beginning of a syntactic entity within a
text/vcard content-type.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>text</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The content entity MUST begin with the BEGIN property
with a value of "VCARD".  The value is case-insensitive.
</t>

    <t>The BEGIN property is used in conjunction with the END property to
delimit an entity containing a related set of properties within a
text/vcard content-type.  This construct can be used instead of
including multiple vCards as body parts inside of a multipart/
alternative MIME message.  It is provided for applications that
wish to define content that can contain multiple entities within
the same text/vcard content-type or to define content that can be
identifiable outside of a MIME environment.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
BEGIN-param = 0" "  ; no parameter allowed
BEGIN-value = "VCARD"
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
      BEGIN:VCARD
]]></artwork></figure>

</section>
<section anchor="end"><name>END</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To denote the end of a syntactic entity within a text/vcard
content-type.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>text</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The content entity MUST end with the END type with a
value of "VCARD".  The value is case-insensitive.
</t>

    <t>The END property is used in conjunction with the BEGIN property to
delimit an entity containing a related set of properties within a
text/vcard content-type.  This construct can be used instead of or
in addition to wrapping separate sets of information inside
additional MIME headers.  It is provided for applications that
wish to define content that can contain multiple entities within
the same text/vcard content-type or to define content that can be
identifiable outside of a MIME environment.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
END-param = 0" "  ; no parameter allowed
END-value = "VCARD"
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
      END:VCARD
]]></artwork></figure>

</section>
<section anchor="prop-source"><name>SOURCE</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To identify the source of directory information contained
in the content type.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>uri</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The SOURCE property is used to provide the means by
which applications knowledgable in the given directory service
protocol can obtain additional or more up-to-date information from
the directory service.  It contains a URI as defined in <xref target="RFC3986"/>
and/or other information referencing the vCard to which the
information pertains.  When directory information is available
from more than one source, the sending entity can pick what it
considers to be the best source, or multiple SOURCE properties can
be included.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
             / mediatype-param / any-param
SOURCE-value = URI
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US

  SOURCE:http://directory.example.com/addressbooks/jdoe/
   Jean%20Dupont.vcf
]]></artwork></figure>

</section>
<section anchor="kind"><name>KIND</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the kind of object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The value may be one of the following:
</t>

    <t>"individual"  for a vCard representing a single person or entity.
   This is the default kind of vCard.</t>

    <t>"group"  for a vCard representing a group of persons or entities.
   The group's member entities can be other vCards or other types
   of entities, such as email addresses or web sites.  A group
   vCard will usually contain MEMBER properties to specify the
   members of the group, but it is not required to.  A group vCard
   without MEMBER properties can be considered an abstract
   grouping, or one whose members are known empirically (perhaps
   "IETF Participants" or "Republican U.S. Senators").</t>

    <t>All properties in a group vCard apply to the group as a whole,
   and not to any particular MEMBER.  For example, an EMAIL
   property might specify the address of a mailing list associated
   with the group, and an IMPP property might refer to a group
   chat room.</t>

    <t>"org"  for a vCard representing an organization.  An organization
   vCard will not (in fact, MUST NOT) contain MEMBER properties,
   and so these are something of a cross between "individual" and
   "group".  An organization is a single entity, but not a person.
   It might represent a business or government, a department or
   division within a business or government, a club, an
   association, or the like.</t>

    <t>All properties in an organization vCard apply to the
   organization as a whole, as is the case with a group vCard.
   For example, an EMAIL property might specify the address of a
   contact point for the organization.</t>

    <t>"location"  for a named geographical place.  A location vCard will
   usually contain a GEO property, but it is not required to.  A
   location vCard without a GEO property can be considered an
   abstract location, or one whose definition is known empirically
   (perhaps "New England" or "The Seashore").</t>

    <t>All properties in a location vCard apply to the location
   itself, and not with any entity that might exist at that
   location.  For example, in a vCard for an office building, an
   ADR property might give the mailing address for the building,
   and a TEL property might specify the telephone number of the
   receptionist.</t>

    <t>An x-name.  vCards MAY include private or experimental values for
   KIND.  Remember that x-name values are not intended for general
   use and are unlikely to interoperate.</t>

    <t>An iana-token.  Additional values may be registered with IANA (see
   <xref target="values-registries"></xref>).  A new value's specification document MUST
   specify which properties make sense for that new kind of vCard
   and which do not.</t>

    <t>Implementations MUST support the specific string values defined
above.  If this property is absent, "individual" MUST be assumed
as the default.  If this property is present but the
implementation does not understand its value (the value is an
x-name or iana-token that the implementation does not support),
the implementation SHOULD act in a neutral way, which usually
means treating the vCard as though its kind were "individual".
The presence of MEMBER properties MAY, however, be taken as an
indication that the unknown kind is an extension of "group".</t>

    <t>Clients often need to visually distinguish contacts based on what
they represent, and the KIND property provides a direct way for
them to do so.  For example, when displaying contacts in a list,
an icon could be displayed next to each one, using distinctive
icons for the different kinds; a client might use an outline of a
single person to represent an "individual", an outline of multiple
people to represent a "group", and so on.  Alternatively, or in
addition, a client might choose to segregate different kinds of
vCards to different panes, tabs, or selections in the user
interface.</t>

    <t>Some clients might also make functional distinctions among the
kinds, ignoring "location" vCards for some purposes and
considering only "location" vCards for others.</t>

    <t>When designing those sorts of visual and functional distinctions,
client implementations have to decide how to fit unsupported kinds
into the scheme.  What icon is used for them?  The one for
"individual"?  A unique one, such as an icon of a question mark?
Which tab do they go into?  It is beyond the scope of this
specification to answer these questions, but these are things
implementers need to consider.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
KIND-param = "VALUE=text" / any-param
KIND-value = "individual" / "group" / "org" / "location"
           / iana-token / x-name
]]></sourcecode></figure>

<t>Example:</t>

<t>This represents someone named Jane Doe working in the marketing
department of the North American division of ABC Inc.</t>

<figure><artwork><![CDATA[
      BEGIN:VCARD
      VERSION:4.0
      KIND:individual
      FN:Jane Doe
      ORG:ABC\, Inc.;North American Division;Marketing
      END:VCARD
]]></artwork></figure>

<t>This represents the department itself, commonly known as ABC
Marketing.</t>

<figure><artwork><![CDATA[
      BEGIN:VCARD
      VERSION:4.0
      KIND:org
      FN:ABC Marketing
      ORG:ABC\, Inc.;North American Division;Marketing
      END:VCARD
]]></artwork></figure>

</section>
<section anchor="xml"><name>XML</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To include extended XML-encoded vCard data in a plain
vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The content of this property is a single XML 1.0
<xref target="W3C.REC-xml-20081126"/> element whose namespace MUST be explicitly
specified using the xmlns attribute and MUST NOT be the vCard 4
namespace ("urn:ietf:params:xml:ns:vcard-4.0").  (This implies
that it cannot duplicate a standard vCard property.)  The element
is to be interpreted as if it was contained in a <spanx style="verb">&lt;vcard&gt;</spanx> element,
as defined in <xref target="RFC6351"/>.
</t>

    <t>The fragment is subject to normal line folding and escaping, i.e.,
replace all backslashes with "\", then replace all newlines with
"\n", then fold long lines.</t>

    <t>Support for this property is OPTIONAL, but implementations of this
specification MUST preserve instances of this property when
propagating vCards.</t>

    <t>See <xref target="RFC6351"/> for more information on the intended use of this
property.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
XML-param = "VALUE=text" / altid-param
XML-value = text
]]></sourcecode></figure>

</section>
</section>
<section anchor="identification-properties"><name>Identification Properties</name>

<t>These types are used to capture information associated with the
identification and naming of the entity associated with the vCard.</t>

<section anchor="fn"><name>FN</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the formatted text corresponding to the name of
the object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>1*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>This property is based on the semantics of the X.520
Common Name attribute <xref target="CCITT.X520.1988"/>.  The property MUST be
present in the vCard object.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
FN-param = "VALUE=text" / type-param / language-param / altid-param
         / pid-param / pref-param / any-param
FN-value = text
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
      FN:Mr. John Q. Public\, Esq.
]]></artwork></figure>

</section>
<section anchor="prop-n"><name>N</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the components of the name of the object the
vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single structured text value.  Each component can have
multiple values.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
  <dt>Special note</dt>
  <dd>
    <t>The structured property value corresponds, in
sequence, to the Family Names (also known as surnames), Given
Names, Additional Names, Honorific Prefixes, and Honorific
Suffixes.  The text components are separated by the SEMICOLON
character (U+003B).  Individual text components can include
multiple text values separated by the COMMA character (U+002C).
This property is based on the semantics of the X.520 individual
name attributes <xref target="CCITT.X520.1988"/>.  The property SHOULD be present
in the vCard object when the name of the object the vCard
represents follows the X.520 model.
</t>

    <t>The SORT-AS parameter MAY be applied to this property.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
N-param = "VALUE=text" / sort-as-param / language-param
        / altid-param / any-param
N-value = list-component 4(";" list-component)
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
          N:Public;John;Quinlan;Mr.;Esq.

          N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
]]></artwork></figure>

</section>
<section anchor="nickname"><name>NICKNAME</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the text corresponding to the nickname of the
object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>One or more text values separated by a COMMA character
(U+002C).</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special note</dt>
  <dd>
    <t>The nickname is the descriptive name given instead of
or in addition to the one belonging to the object the vCard
represents.  It can also be used to specify a familiar form of a
proper name specified by the FN or N properties.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
NICKNAME-param = "VALUE=text" / type-param / language-param
               / altid-param / pid-param / pref-param / any-param
NICKNAME-value = text-list
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
          NICKNAME:Robbie

          NICKNAME:Jim,Jimmie

          NICKNAME;TYPE=work:Boss
]]></artwork></figure>

</section>
<section anchor="photo"><name>PHOTO</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify an image or photograph information that
annotates some aspect of the object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
PHOTO-param = "VALUE=uri" / altid-param / type-param
            / mediatype-param / pref-param / pid-param / any-param
PHOTO-value = URI
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
    PHOTO:http://www.example.com/pub/photos/jqpublic.gif

    PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
     AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
     ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
     <...remainder of base64-encoded data...>
]]></artwork></figure>

</section>
<section anchor="bday"><name>BDAY</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the birth date of the object the vCard
represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>The default is a single date-and-or-time value.  It can
also be reset to a single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
BDAY-param = BDAY-param-date / BDAY-param-text
BDAY-value = date-and-or-time / text
  ; Value and parameter MUST match.

BDAY-param-date = "VALUE=date-and-or-time"
BDAY-param-text = "VALUE=text" / language-param

BDAY-param =/ altid-param / calscale-param / any-param
  ; calscale-param can only be present when BDAY-value is
  ; date-and-or-time and actually contains a date or date-time.
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
          BDAY:19960415
          BDAY:--0415
          BDAY:19531015T231000Z
          BDAY;VALUE=text:circa 1800
]]></artwork></figure>

</section>
<section anchor="prop-anniversary"><name>ANNIVERSARY</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>The date of marriage, or equivalent, of the object the
vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>The default is a single date-and-or-time value.  It can
also be reset to a single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
ANNIVERSARY-param = ANNIVERSARY-param-date / ANNIVERSARY-param-text
ANNIVERSARY-value = date-and-or-time / text
  ; Value and parameter MUST match.

ANNIVERSARY-param-date = "VALUE=date-and-or-time"
ANNIVERSARY-param-text = "VALUE=text" / language-param

ANNIVERSARY-param =/ altid-param / calscale-param / any-param
  ; calscale-param can only be present when ANNIVERSARY-value is
  ; date-and-or-time and actually contains a date or date-time.
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
          ANNIVERSARY:19960415
]]></artwork></figure>

</section>
<section anchor="gender"><name>GENDER</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the components of the sex and gender identity of
the object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single structured value with two components.  Each
component has a single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The components correspond, in sequence, to the sex
(biological), and gender identity.  Each component is optional.
</t>

    <t>Sex component:  A single letter.  M stands for "male", F stands
   for "female", O stands for "other", N stands for "none or not
   applicable", U stands for "unknown".</t>

    <t>Gender identity component:  Free-form text.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
GENDER-param = "VALUE=text" / any-param
GENDER-value = sex [";" text]

sex = "" / "M" / "F" / "O" / "N" / "U"
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  GENDER:M
  GENDER:F
  GENDER:M;Transgender Man
  GENDER:F;Transfeminine
  GENDER:O;Intersex
  GENDER:;Agender
]]></artwork></figure>

</section>
<section anchor="birthplace"><name>BIRTHPLACE</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the place of birth of the object the vCard
represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single text value (default) or a single URI value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The LANGUAGE parameter (<xref target="param-language"></xref>) MUST NOT be present unless
the value is of type "text".</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
BIRTHPLACE-param = BIRTHPLACE-param-text / BIRTHPLACE-param-uri
BIRTHPLACE-value = text / URI
  ; Value and parameter MUST match.

BIRTHPLACE-param-text = "VALUE=text" / language-param
BIRTHPLACE-param-uri  = "VALUE=uri"

BIRTHPLACE-param =/ altid-param / any-param
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  BIRTHPLACE:Babies'R'Us Hospital
  BIRTHPLACE;VALUE=uri:http://example.com/hospitals/babiesrus.vcf
  BIRTHPLACE;VALUE=uri:geo:46.769307,-71.283079
]]></artwork></figure>

</section>
<section anchor="deathplace"><name>DEATHPLACE</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the place of death of the object the vCard
represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single text value (default) or a single URI value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The LANGUAGE parameter (<xref target="param-language"></xref>) MUST NOT be present unless
the value is of type "text".</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
DEATHPLACE-param = DEATHPLACE-param-text / DEATHPLACE-param-uri
DEATHPLACE-value = text / URI
  ; Value and parameter MUST match.

DEATHPLACE-param-text = "VALUE=text" / language-param
DEATHPLACE-param-uri  = "VALUE=uri"

DEATHPLACE-param =/ altid-param / any-param
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  DEATHPLACE:Aboard the Titanic\, near Newfoundland
  DEATHPLACE;VALUE=uri:http://example.com/ships/titanic.vcf
  DEATHPLACE;VALUE=uri:geo:41.731944,-49.945833
]]></artwork></figure>

</section>
<section anchor="deathdate"><name>DEATHDATE</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the date of death of the object the vCard
represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>The default is a single date-and-or-time value.  It can
also be reset to a single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The presence of a DEATHDATE property indicates that the
subject of the vCard is known to be dead.  The absence of this
property makes no statement one way or the other.
</t>

    <t>The LANGUAGE parameter (<xref target="param-language"></xref>) MUST NOT be present unless
the value is of type "text".</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
DEATHDATE-param = DEATHDATE-param-date / DEATHDATE-param-text
DEATHDATE-value = date-and-or-time / text
  ; Value and parameter MUST match.

DEATHDATE-param-date = "VALUE=date-and-or-time"
DEATHDATE-param-text = "VALUE=text" / language-param

DEATHDATE-param =/ altid-param / calscale-param / any-param
  ; calscale-param can only be present when DEATHDATE-value is
  ; date-and-or-time and actually contains a date or date-time.
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  DEATHDATE:19960415
  DEATHDATE:--0415
  DEATHDATE:19531015T231000Z
  DEATHDATE;VALUE=text:circa 1800
]]></artwork></figure>

</section>
</section>
<section anchor="delivery-addressing-properties"><name>Delivery Addressing Properties</name>

<t>These types are concerned with information related to the delivery
addressing or label for the vCard object.</t>

<section anchor="prop-adr"><name>ADR</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the components of the delivery address for the
vCard object.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single structured text value, separated by the
SEMICOLON character (U+003B).</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The structured type value consists of a sequence of
address components.  The component values MUST be specified in
their corresponding position.  The structured type value
corresponds, in sequence, to
   the post office box;
   the extended address (e.g., apartment or suite number);
   the street address;
   the locality (e.g., city);
   the region (e.g., state or province);
   the postal code;
   the country name (full name in the language specified in
   <xref target="param-language"></xref>).
</t>

    <t>When a component value is missing, the associated component
separator MUST still be specified.</t>

    <t>Experience with vCard 3 has shown that the first two components
(post office box and extended address) are plagued with many
interoperability issues.  To ensure maximal interoperability,
their values SHOULD be empty.</t>

    <t>The text components are separated by the SEMICOLON character
(U+003B).  Where it makes semantic sense, individual text
components can include multiple text values (e.g., a "street"
component with multiple lines) separated by the COMMA character
(U+002C).</t>

    <t>The property can include the "PREF" parameter to indicate the
preferred delivery address when more than one address is
specified.</t>

    <t>The GEO and TZ parameters MAY be used with this property.</t>

    <t>The property can also include a "LABEL" parameter to present a
delivery address label for the address.  Its value is a plain-text
string representing the formatted address.  The escaping rules for
this parameter, including the compatibility rules for line breaks,
are described in <xref target="param-escaping"></xref>.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
label-param = "LABEL=" param-value

ADR-param = "VALUE=text" / label-param / language-param
          / geo-parameter / tz-parameter / altid-param / pid-param
          / pref-param / type-param / any-param

ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
            ADR-component-street ";" ADR-component-locality ";"
            ADR-component-region ";" ADR-component-code ";"
            ADR-component-country
ADR-component-pobox    = list-component
ADR-component-ext      = list-component
ADR-component-street   = list-component
ADR-component-locality = list-component
ADR-component-region   = list-component
ADR-component-code     = list-component
ADR-component-country  = list-component
]]></sourcecode></figure>

<t>Example: In this example, the post office box and the extended
address are absent.</t>

<figure><artwork><![CDATA[
  ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n
   Mail Drop: TNE QB\n123 Main Street\nAny Town, CA  91921-1234\n
   U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A.
]]></artwork></figure>

</section>
</section>
<section anchor="communications-properties"><name>Communications Properties</name>

<t>These properties describe information about how to communicate with
the object the vCard represents.</t>

<section anchor="prop-tel"><name>TEL</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the telephone number for telephony communication
with the object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>By default, it is a single free-form text value (for
backward compatibility with vCard 3), but it SHOULD be reset to a
URI value.  It is expected that the URI scheme will be "tel", as
specified in <xref target="RFC3966"/>, but other schemes MAY be used.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>This property is based on the X.520 Telephone Number
attribute <xref target="CCITT.X520.1988"/>.
</t>

    <t>The property can include the "PREF" parameter to indicate a
preferred-use telephone number.</t>

    <t>The property can include the parameter "TYPE" to specify intended
use for the telephone number.  The predefined values for the TYPE
parameter are:</t>

    <texttable>
          <ttcol align='left'>Value</ttcol>
          <ttcol align='left'>Description</ttcol>
          <c>text</c>
          <c>Indicates that the telephone number supports text messages (SMS).</c>
          <c>voice</c>
          <c>Indicates a voice telephone number.</c>
          <c>fax</c>
          <c>Indicates a facsimile telephone number.</c>
          <c>cell</c>
          <c>Indicates a cellular or mobile telephone number.</c>
          <c>video</c>
          <c>Indicates a video conferencing telephone number.</c>
          <c>pager</c>
          <c>Indicates a paging device telephone number.</c>
          <c>textphone</c>
          <c>Indicates a telecommunication device for people with hearing or speech difficulties.</c>
    </texttable>

    <t>The default type is "voice".  These type parameter values can be
specified as a parameter list (e.g., <spanx style="verb">TYPE=text;TYPE=voice</spanx>) or as a
value list (e.g., <spanx style="verb">TYPE=text,voice</spanx>).  The default can be
overridden to another set of values by specifying one or more
alternate values.  For example, the default TYPE of "voice" can be
reset to a VOICE and FAX telephone number by the value list
<spanx style="verb">TYPE=voice,fax.</spanx></t>

    <t>If this property's value is a URI that can also be used for
instant messaging, the IMPP (<xref target="prop-impp"></xref>) property SHOULD be
used in addition to this property.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
TEL-param = TEL-text-param / TEL-uri-param
TEL-value = TEL-text-value / TEL-uri-value
  ; Value and parameter MUST match.

TEL-text-param = "VALUE=text"
TEL-text-value = text

TEL-uri-param = "VALUE=uri" / mediatype-param
TEL-uri-value = URI

TEL-param =/ type-param / pid-param / pref-param / altid-param
           / any-param

type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
               / "pager" / "textphone" / iana-token / x-name
  ; type-param-tel MUST NOT be used with a property other than TEL.
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
  TEL;VALUE=uri;PREF=1;TYPE=voice,home:tel:+1-555-555-5555;ext=5555
  TEL;VALUE=uri;TYPE=home:tel:+33-01-23-45-67
]]></artwork></figure>

</section>
<section anchor="email"><name>EMAIL</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the electronic mail address for communication
with the object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The property can include type "PREF" parameter to
indicate a preferred-use email address when more than one is
specified.
</t>

    <t>Even though the value is free-form UTF-8 text, it is likely to be
interpreted by a Mail User Agent (MUA) as an "addr-spec", as
defined in <xref target="RFC5322"/>, Section 3.4.1.  Readers should also be aware
of the current work toward internationalized email addresses
<xref target="RFC5335bis"/>.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
            / altid-param / any-param
EMAIL-value = text
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        EMAIL;TYPE=work:jqpublic@xyz.example.com

        EMAIL;PREF=1:jane_doe@example.com
]]></artwork></figure>

</section>
<section anchor="prop-impp"><name>IMPP</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the URI for instant messaging and presence
protocol communications with the object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The property may include the "PREF" parameter to
indicate that this is a preferred address and has the same
semantics as the "PREF" parameter in a TEL property.
</t>

    <t>If this property's value is a URI that can be used for voice
and/or video, the TEL property (<xref target="prop-tel"></xref>) SHOULD be used in
addition to this property.</t>

    <t>This property is adapted from <xref target="RFC4770"/>, which is made obsolete by
this document.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
           / mediatype-param / altid-param / any-param
IMPP-value = URI
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
    IMPP;PREF=1:xmpp:alice@example.com
]]></artwork></figure>

</section>
<section anchor="lang"><name>LANG</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the language(s) that may be used for contacting
the entity associated with the vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single language-tag value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
LANG-param = "VALUE=language-tag" / pid-param / pref-param
           / altid-param / type-param / any-param
LANG-value = Language-Tag
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
    LANG;TYPE=work;PREF=1:en
    LANG;TYPE=work;PREF=2:fr
    LANG;TYPE=home:fr
]]></artwork></figure>

</section>
</section>
<section anchor="geographical-properties"><name>Geographical Properties</name>

<t>These properties are concerned with information associated with
geographical positions or regions associated with the object the
vCard represents.</t>

<section anchor="tz-1"><name>TZ</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify information related to the time zone of the
object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>The default is a single text value.  It can also be
reset to a single URI or utc-offset value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>It is expected that names from the public-domain
Olson database <xref target="TZ-DB"/> will be used, but this is not a
restriction.  See also <xref target="IANA-TZ"/>.
</t>

    <t>Efforts are currently being directed at creating a standard URI
scheme for expressing time zone information.  Usage of such a
scheme would ensure a high level of interoperability between
implementations that support it.</t>

    <t>Note that utc-offset values SHOULD NOT be used because the UTC
offset varies with time -- not just because of the usual daylight
saving time shifts that occur in may regions, but often entire
regions will "re-base" their overall offset.  The actual offset
may be +/- 1 hour (or perhaps a little more) than the one given.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
TZ-value = text / URI / utc-offset
  ; Value and parameter MUST match.

TZ-param =/ altid-param / pid-param / pref-param / type-param
          / mediatype-param / any-param
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  TZ:America/New_York

  TZ;VALUE=utc-offset:-0500
    ; Note: utc-offset format is NOT RECOMMENDED.
]]></artwork></figure>

</section>
<section anchor="prop-geo"><name>GEO</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify information related to the global positioning of
the object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The "geo" URI scheme <xref target="RFC5870"/> is particularly well
suited for this property, but other schemes MAY be used.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
          / mediatype-param / altid-param / any-param
GEO-value = URI
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        GEO:geo:37.386013,-122.082932
]]></artwork></figure>

</section>
</section>
<section anchor="organizational-properties"><name>Organizational Properties</name>

<t>These properties are concerned with information associated with
characteristics of the organization or organizational units of the
object that the vCard represents.</t>

<section anchor="prop-title"><name>TITLE</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the position or job of the object the vCard
represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>This property is based on the X.520 Title attribute
<xref target="CCITT.X520.1988"/>.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
TITLE-param = "VALUE=text" / language-param / pid-param
            / pref-param / altid-param / type-param / any-param
TITLE-value = text
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        TITLE:Research Scientist
]]></artwork></figure>

</section>
<section anchor="role"><name>ROLE</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the function or part played in a particular
situation by the object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>This property is based on the X.520 Business Category
explanatory attribute <xref target="CCITT.X520.1988"/>.  This property is
included as an organizational type to avoid confusion with the
semantics of the TITLE property and incorrect usage of that
property when the semantics of this property is intended.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
           / type-param / altid-param / any-param
ROLE-value = text
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        ROLE:Project Leader
]]></artwork></figure>

</section>
<section anchor="logo"><name>LOGO</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify a graphic image of a logo associated with the
object the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
           / type-param / mediatype-param / altid-param / any-param
LOGO-value = URI
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  LOGO:http://www.example.com/pub/logos/abccorp.jpg

  LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc
   AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
   ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
   <...the remainder of base64-encoded data...>
]]></artwork></figure>

</section>
<section anchor="org"><name>ORG</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the organizational name and units associated
with the vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single structured text value consisting of components
separated by the SEMICOLON character (U+003B).</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The property is based on the X.520 Organization Name
and Organization Unit attributes <xref target="CCITT.X520.1988"/>.  The property
value is a structured type consisting of the organization name,
followed by zero or more levels of organizational unit names.
</t>

    <t>The SORT-AS parameter MAY be applied to this property.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
ORG-param = "VALUE=text" / sort-as-param / language-param
          / pid-param / pref-param / altid-param / type-param
          / any-param
ORG-value = component *(";" component)
]]></sourcecode></figure>

<t>Example: A property value consisting of an organizational name,
organizational unit #1 name, and organizational unit #2 name.</t>

<figure><artwork><![CDATA[
        ORG:ABC\, Inc.;North American Division;Marketing
]]></artwork></figure>

</section>
<section anchor="prop-member"><name>MEMBER</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To include a member in the group this vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI value.  It MAY also be reset to free-form text.
A URI value MAY refer to something other than a vCard object;
for example, an email distribution list could employ the
"mailto" URI scheme <xref target="RFC6068"/> for efficiency.  A text value
references a member vCard by its UID, and is used when that
UID is itself a text value (see <xref target="prop-uid"></xref>), as is common
for data originating in vCard 3.0.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>This property MUST NOT be present unless the value of
the KIND property is "group".
</t>

    <t>A MEMBER value that identifies another vCard does so by
matching that vCard's UID.  A MEMBER value and a UID value
identify the same vCard when they are equivalent as described
in <xref target="prop-uid"></xref>; in particular, a text MEMBER value can
reference a vCard whose UID is a text value.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
MEMBER-param = MEMBER-uri-param / MEMBER-text-param
MEMBER-value = MEMBER-uri-value / MEMBER-text-value
  ; Value and parameter MUST match.

MEMBER-uri-param = "VALUE=uri" / mediatype-param
MEMBER-text-param = "VALUE=text"

MEMBER-uri-value = URI
MEMBER-text-value = text

MEMBER-param =/ pid-param / pref-param / altid-param / any-param
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  BEGIN:VCARD
  VERSION:4.0
  KIND:group
  FN:The Doe family
  MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
  MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
  END:VCARD
  BEGIN:VCARD
  VERSION:4.0
  FN:John Doe
  UID:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
  END:VCARD
  BEGIN:VCARD
  VERSION:4.0
  FN:Jane Doe
  UID:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
  END:VCARD

  BEGIN:VCARD
  VERSION:4.0
  KIND:group
  FN:Funky distribution list
  MEMBER:mailto:subscriber1@example.com
  MEMBER:xmpp:subscriber2@example.com
  MEMBER:sip:subscriber3@example.com
  MEMBER:tel:+1-418-555-5555
  END:VCARD
]]></artwork></figure>

</section>
<section anchor="related"><name>RELATED</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify a relationship between another entity and the
entity represented by this vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI.  It can also be reset to a single text
value.  The text value can be used to specify textual information.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The TYPE parameter MAY be used to characterize the
related entity.  It contains a comma-separated list of values that
are registered with IANA as described in <xref target="registering-elements"></xref>.  The
registry is pre-populated with the values defined in <xref target="xfn"/>.  This
document also specifies two additional values:
</t>

    <t>agent:  an entity who may sometimes act on behalf of the entity
   associated with the vCard.</t>

    <t>emergency:  indicates an emergency contact</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
RELATED-param = RELATED-param-uri / RELATED-param-text
RELATED-value = URI / text
  ; Parameter and value MUST match.

RELATED-param-uri = "VALUE=uri" / mediatype-param
RELATED-param-text = "VALUE=text" / language-param

RELATED-param =/ pid-param / pref-param / altid-param / type-param
               / any-param

type-param-related = related-type-value *("," related-type-value)
  ; type-param-related MUST NOT be used with a property other than
  ; RELATED.

related-type-value = "contact" / "acquaintance" / "friend" / "met"
                   / "co-worker" / "colleague" / "co-resident"
                   / "neighbor" / "child" / "parent"
                   / "sibling" / "spouse" / "kin" / "muse"
                   / "crush" / "date" / "sweetheart" / "me"
                   / "agent" / "emergency"
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
RELATED;TYPE=friend:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
RELATED;TYPE=contact:http://example.com/directory/jdoe.vcf
RELATED;TYPE=co-worker;VALUE=text:Please contact my assistant Jane
 Doe for any inquiries.
]]></artwork></figure>

</section>
</section>
<section anchor="explanatory-properties"><name>Explanatory Properties</name>

<t>These properties are concerned with additional explanations, such as
that related to informational notes or revisions specific to the
vCard.</t>

<section anchor="categories"><name>CATEGORIES</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify application category information about the
vCard, also known as "tags".</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>One or more text values separated by a COMMA character
(U+002C).</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
CATEGORIES-param = "VALUE=text" / pid-param / pref-param
                 / type-param / altid-param / any-param
CATEGORIES-value = text-list
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        CATEGORIES:TRAVEL AGENT

        CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
]]></artwork></figure>

</section>
<section anchor="note"><name>NOTE</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify supplemental information or a comment that is
associated with the vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The property is based on the X.520 Description
attribute <xref target="CCITT.X520.1988"/>.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
           / type-param / altid-param / any-param
NOTE-value = text
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        NOTE:This fax number is operational 0800 to 1715
          EST\, Mon-Fri.
]]></artwork></figure>

</section>
<section anchor="prodid"><name>PRODID</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the identifier for the product that created the
vCard object.</t>
  </dd>
  <dt>Type value</dt>
  <dd>
    <t>A single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>Implementations SHOULD use a method such as that
specified for Formal Public Identifiers in <xref target="ISO9070"/> or for
Universal Resource Names in <xref target="RFC3406"/> to ensure that the text
value is unique.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
PRODID-param = "VALUE=text" / any-param
PRODID-value = text
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
]]></artwork></figure>

</section>
<section anchor="prop-rev"><name>REV</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify revision information about the current vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single timestamp value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>The value distinguishes the current revision of the
information in this vCard for other renditions of the information.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
REV-param = "VALUE=timestamp" / any-param
REV-value = timestamp
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        REV:19951031T222710Z
]]></artwork></figure>

</section>
<section anchor="sound"><name>SOUND</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify a digital sound content information that
annotates some aspect of the vCard.  This property is often used
to specify the proper pronunciation of the name property value of
the vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
            / type-param / mediatype-param / altid-param
            / any-param
SOUND-value = URI
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
  SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com

  SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh
   AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
   ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
   <...the remainder of base64-encoded data...>
]]></artwork></figure>

</section>
<section anchor="prop-uid"><name>UID</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify a value that represents a globally unique
identifier corresponding to the entity associated with the vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI value.  It MAY also be reset to free-form
text.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>This property is used to uniquely identify the object
that the vCard represents.  The "uuid" URN namespace defined in
<xref target="RFC4122"/> is particularly well suited to this task, but other URI
schemes MAY be used.  Free-form text MAY also be used.
</t>

    <t>Two identifier values -- each of them either a UID value or a
MEMBER value (<xref target="prop-member"></xref>) -- are compared for equivalence as
follows.  First, the content of each value is determined: for a
text value, this is the value with the escaping described in
<xref target="value-escaping"></xref> removed; for a URI value, it is the value exactly
as written.  If both values are URI values and both are valid URIs,
they are equivalent when they are equivalent under <xref target="RFC3986"/>,
Section 6.  Otherwise, the two values are equivalent when their
content is identical, character for character.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
UID-param = UID-uri-param / UID-text-param
UID-value = UID-uri-value / UID-text-value
  ; Value and parameter MUST match.

UID-uri-param = "VALUE=uri"
UID-uri-value = URI

UID-text-param = "VALUE=text"
UID-text-value = text

UID-param =/ any-param
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
]]></artwork></figure>

</section>
<section anchor="clientpidmap"><name>CLIENTPIDMAP</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To give a global meaning to a local PID source identifier.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single structured text value consisting of components separated by the
SEMICOLON character (U+003B). The first component is a small integer
corresponding to the second component of a PID parameter instance.  The
second component is a URI. The "uuid" URN namespace defined in <xref target="RFC4122"/>
is particularly well suited to this task, but other URI schemes MAY be used.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>PID source identifiers (the source identifier is the
second field in a PID parameter instance) are small integers that
only have significance within the scope of a single vCard
instance.  Each distinct source identifier present in a vCard MUST
have an associated CLIENTPIDMAP.  See <xref target="synchronization"></xref> for more details
on the usage of CLIENTPIDMAP.
</t>

    <t>PID source identifiers MUST be strictly positive.  Zero is not
allowed.</t>

    <t>As a special exception, the PID parameter MUST NOT be applied to
this property.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
CLIENTPIDMAP-param = any-param
CLIENTPIDMAP-value = 1*DIGIT ";" URI
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
  TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555
  EMAIL;PID=4.1,5.2:jdoe@example.com
  CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
  CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
]]></artwork></figure>

</section>
<section anchor="url"><name>URL</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify a uniform resource locator associated with the
object to which the vCard refers.  Examples for individuals
include personal web sites, blogs, and social networking site
identifiers.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single uri value.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
URL-param = "VALUE=uri" / pid-param / pref-param / type-param
          / mediatype-param / altid-param / any-param
URL-value = URI
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        URL:http://example.org/restaurant.french/~chezchic.html
]]></artwork></figure>

</section>
<section anchor="prop-version"><name>VERSION</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the version of the vCard specification used to
format this vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>1</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>This property MUST be present in the vCard object,
and it must appear immediately after BEGIN:VCARD.  The value MUST
be "4.0" if the vCard corresponds to this specification.  Note
that earlier versions of vCard allowed this property to be placed
anywhere in the vCard object, or even to be absent.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
VERSION-param = "VALUE=text" / any-param
VERSION-value = "4.0"
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
        VERSION:4.0
]]></artwork></figure>

</section>
</section>
<section anchor="security-properties"><name>Security Properties</name>

<t>These properties are concerned with the security of communication
pathways or access to the vCard.</t>

<section anchor="prop-key"><name>KEY</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify a public key or authentication certificate
associated with the object that the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI.  It can also be reset to a text value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
KEY-param = KEY-uri-param / KEY-text-param
KEY-value = KEY-uri-value / KEY-text-value
  ; Value and parameter MUST match.

KEY-uri-param = "VALUE=uri" / mediatype-param
KEY-uri-value = URI

KEY-text-param = "VALUE=text"
KEY-text-value = text

KEY-param =/ altid-param / pid-param / pref-param / type-param
           / any-param
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  KEY:http://www.example.com/keys/jdoe.cer

  KEY;MEDIATYPE=application/pgp-keys:ftp://example.com/keys/jdoe

  KEY:data:application/pgp-keys;base64,MIICajCCAdOgAwIBAgICBE
   UwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05l
   <... remainder of base64-encoded data ...>
]]></artwork></figure>

</section>
</section>
<section anchor="calendar-properties"><name>Calendar Properties</name>

<t>These properties are further specified in <xref target="RFC2739"/>.</t>

<section anchor="fburl"><name>FBURL</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the URI for the busy time associated with the
object that the vCard represents.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>Where multiple FBURL properties are specified, the
default FBURL property is indicated with the PREF parameter.  The
FTP <xref target="RFC1738"/> or HTTP <xref target="RFC2616"/> type of URI points to an iCalendar
<xref target="RFC5545"/> object associated with a snapshot of the next few weeks
or months of busy time data.  If the iCalendar object is
represented as a file or document, its file extension should be
".ifb".</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
            / mediatype-param / altid-param / any-param
FBURL-value = URI
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  FBURL;PREF=1:http://www.example.com/busy/janedoe
  FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb
]]></artwork></figure>

</section>
<section anchor="caladruri"><name>CALADRURI</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the calendar user address <xref target="RFC5545"/> to which a
scheduling request <xref target="RFC5546"/> should be sent for the object
represented by the vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>Where multiple CALADRURI properties are specified,
the default CALADRURI property is indicated with the PREF
parameter.</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
                / mediatype-param / altid-param / any-param
CALADRURI-value = URI
]]></sourcecode></figure>

<t>Example:</t>

<figure><artwork><![CDATA[
  CALADRURI;PREF=1:mailto:janedoe@example.com
  CALADRURI:http://example.com/calendar/jdoe
]]></artwork></figure>

</section>
<section anchor="caluri"><name>CALURI</name>

<dl>
  <dt>Purpose</dt>
  <dd>
    <t>To specify the URI for a calendar associated with the
object represented by the vCard.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>A single URI value.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>*</t>
  </dd>
  <dt>Special notes</dt>
  <dd>
    <t>Where multiple CALURI properties are specified, the
default CALURI property is indicated with the PREF parameter.  The
property should contain a URI pointing to an iCalendar <xref target="RFC5545"/>
object associated with a snapshot of the user's calendar store.
If the iCalendar object is represented as a file or document, its
file extension should be ".ics".</t>
  </dd>
</dl>

<t>ABNF:</t>

<figure><sourcecode type="abnf"><![CDATA[
CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
             / mediatype-param / altid-param / any-param
CALURI-value = URI
]]></sourcecode></figure>

<t>Examples:</t>

<figure><artwork><![CDATA[
  CALURI;PREF=1:http://cal.example.com/calA
  CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics
]]></artwork></figure>

</section>
</section>
<section anchor="extended-properties-and-parameters"><name>Extended Properties and Parameters</name>

<t>The properties and parameters defined by this document can be
extended.  Non-standard, private properties and parameters with a
name starting with "X-" may be defined bilaterally between two
cooperating agents without outside registration or standardization.</t>

</section>
</section>
<section anchor="synchronization"><name>Synchronization</name>

<t>vCard data often needs to be synchronized between devices.  In this
context, synchronization is defined as the intelligent merging of two
representations of the same object. vCard 4.0 includes mechanisms to
aid this process.</t>

<section anchor="mechanisms"><name>Mechanisms</name>

<t>Two mechanisms are available: the UID property is used to match
multiple instances of the same vCard, while the PID parameter is used
to match multiple instances of the same property.</t>

<t>The term "matching" is used here to mean recognizing that two
instances are in fact representations of the same object.  For
example, a single vCard that is shared with someone results in two
vCard instances.  After they have evolved separately, they still
represent the same object, and therefore may be matched by a
synchronization engine.</t>

<section anchor="matching-vcard-instances"><name>Matching vCard Instances</name>

<t>vCard instances for which the UID properties (<xref target="prop-uid"></xref>) are
equivalent MUST be matched.  Equivalence of UID values is determined
as described in <xref target="prop-uid"></xref>.</t>

<t>In all other cases, vCard instances MAY be matched at the discretion
of the synchronization engine.</t>

</section>
<section anchor="matching-property-instances"><name>Matching Property Instances</name>

<t>Property instances belonging to unmatched vCards MUST NOT be matched.</t>

<t>Property instances whose name (e.g., EMAIL, TEL, etc.) is not the
same MUST NOT be matched.</t>

<t>Property instances whose name is CLIENTPIDMAP are handled separately
and MUST NOT be matched.  The synchronization MUST ensure that there
is consistency of CLIENTPIDMAPs among matched vCard instances.</t>

<t>Property instances belonging to matched vCards, whose name is the
same, and whose maximum cardinality is 1, MUST be matched.</t>

<t>Property instances belonging to matched vCards, whose name is the
same, and whose PID parameters match, MUST be matched.  See
<xref target="pid-matching"></xref> for details on PID matching.</t>

<t>In all other cases, property instances MAY be matched at the
discretion of the synchronization engine.</t>

</section>
<section anchor="pid-matching"><name>PID Matching</name>

<t>Two PID values for which the first fields are equivalent represent
the same local value.</t>

<t>Two PID values representing the same local value and for which the
second fields point to CLIENTPIDMAP properties whose second field
URIs are equivalent (as specified in <xref target="RFC3986"/>, Section 6) also
represent the same global value.</t>

<t>PID parameters for which at least one pair of their values represent
the same global value MUST be matched.</t>

<t>In all other cases, PID parameters MAY be matched at the discretion
of the synchronization engine.</t>

<t>For example, PID value "5.1", in the first vCard below, and PID value
"5.2", in the second vCard below, represent the same global value.</t>

<figure><artwork><![CDATA[
  BEGIN:VCARD
  VERSION:4.0
  FN:J. Doe
  EMAIL;PID=4.2,5.1:jdoe@example.com
  CLIENTPIDMAP:1;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
  CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc
  END:VCARD

  BEGIN:VCARD
  VERSION:4.0
  FN:J. Doe
  EMAIL;PID=5.1,5.2:john@example.com
  CLIENTPIDMAP:1;urn:uuid:0c75c629-6a8d-4d5e-a07f-1bb35846854d
  CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
  END:VCARD
]]></artwork></figure>

</section>
</section>
<section anchor="example"><name>Example</name>

<section anchor="creation"><name>Creation</name>

<t>The following simple vCard is first created on a given device.</t>

<figure><artwork><![CDATA[
  BEGIN:VCARD
  VERSION:4.0
  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
  FN;PID=1.1:J. Doe
  N:Doe;J.;;;
  EMAIL;PID=1.1:jdoe@example.com
  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
  END:VCARD
]]></artwork></figure>

<t>This new vCard is assigned the UID
"urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1" by the creating
device.  The FN and EMAIL properties are assigned the same local
value of 1, and this value is given global context by associating it
with "urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556", which
represents the creating device.  We are at liberty to reuse the same
local value since instances of different properties will never be
matched.  The N property has no PID because it is forbidden by its
maximum cardinality of 1.</t>

</section>
<section anchor="initial-sharing"><name>Initial Sharing</name>

<t>This vCard is shared with a second device.  Upon inspecting the UID
property, the second device understands that this is a new vCard
(i.e., unmatched) and thus the synchronization results in a simple
copy.</t>

</section>
<section anchor="adding-and-sharing-a-property"><name>Adding and Sharing a Property</name>

<t>A new phone number is created on the first device, then the vCard is
shared with the second device.  This is what the second device
receives:</t>

<figure><artwork><![CDATA[
  BEGIN:VCARD
  VERSION:4.0
  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
  FN;PID=1.1:J. Doe
  N:Doe;J.;;;
  EMAIL;PID=1.1:jdoe@example.com
  TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
  END:VCARD
]]></artwork></figure>

<t>Upon inspecting the UID property, the second device matches the vCard
it received to the vCard that it already has stored.  It then starts
comparing the properties of the two vCards in same-named pairs.</t>

<t>The FN properties are matched because the PID parameters have the
same global value.  Since the property value is the same, no update
takes place.</t>

<t>The N properties are matched automatically because their maximum
cardinality is 1.  Since the property value is the same, no update
takes place.</t>

<t>The EMAIL properties are matched because the PID parameters have the
same global value.  Since the property value is the same, no update
takes place.</t>

<t>The TEL property in the new vCard is not matched to any in the stored
vCard because no property in the stored vCard has the same name.
Therefore, this property is copied from the new vCard to the stored
vCard.</t>

<t>The CLIENTPIDMAP property is handled separately by the
synchronization engine.  It ensures that it is consistent with the
stored one.  If it was not, the results would be up to the
synchronization engine, and thus undefined by this document.</t>

</section>
<section anchor="simultaneous-editing"><name>Simultaneous Editing</name>

<t>A new email address and a new phone number are added to the vCard on
each of the two devices, and then a new synchronization event
happens.  Here are the vCards that are communicated to each other:</t>

<figure><artwork><![CDATA[
  BEGIN:VCARD
  VERSION:4.0
  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
  FN;PID=1.1:J. Doe
  N:Doe;J.;;;
  EMAIL;PID=1.1:jdoe@example.com
  EMAIL;PID=2.1:boss@example.com
  TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
  TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
  END:VCARD

  BEGIN:VCARD
  VERSION:4.0
  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
  FN;PID=1.1:J. Doe
  N:Doe;J.;;;
  EMAIL;PID=1.1:jdoe@example.com
  EMAIL;PID=2.2:ceo@example.com
  TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
  TEL;PID=2.2;VALUE=uri:tel:+1-666-666-6666
  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
  CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
  END:VCARD
]]></artwork></figure>

<t>On the first device, the same PID source identifier (1) is reused for
the new EMAIL and TEL properties.  On the second device, a new source
identifier (2) is generated, and a corresponding CLIENTPIDMAP
property is created.  It contains the second device's identifier,
"urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".</t>

<t>The new EMAIL properties are unmatched on both sides since the PID
global value is new in both cases.  The sync thus results in a copy
on both sides.</t>

<t>Although the situation appears to be the same for the TEL properties,
in this case, the synchronization engine is particularly smart and
matches the two new TEL properties even though their PID global
values are different.  Note that in this case, the rules of
<xref target="matching-property-instances"></xref> state that two properties MAY be matched at the
discretion of the synchronization engine.  Therefore, the two
properties are merged.</t>

<t>All this results in the following vCard, which is stored on both
devices:</t>

<figure><artwork><![CDATA[
  BEGIN:VCARD
  VERSION:4.0
  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
  FN:J. Doe
  N:Doe;J.;;;
  EMAIL;PID=1.1:jdoe@example.com
  EMAIL;PID=2.1:boss@example.com
  EMAIL;PID=2.2:ceo@example.com
  TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
  TEL;PID=2.1,2.2;VALUE=uri:tel:+1-666-666-6666
  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
  CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
  END:VCARD
]]></artwork></figure>

</section>
<section anchor="global-context-simplification"><name>Global Context Simplification</name>

<t>The two devices finish their synchronization procedure by simplifying
their global contexts.  Since they haven't talked to any other
device, the following vCard is for all purposes equivalent to the
above.  It is also shorter.</t>

<figure><artwork><![CDATA[
  BEGIN:VCARD
  VERSION:4.0
  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
  FN:J. Doe
  N:Doe;J.;;;
  EMAIL;PID=1.1:jdoe@example.com
  EMAIL;PID=2.1:boss@example.com
  EMAIL;PID=3.1:ceo@example.com
  TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
  TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
  END:VCARD
]]></artwork></figure>

<t>The details of global context simplification are unspecified by this
document.  They are left up to the synchronization engine.  This
example is merely intended to illustrate the possibility, which
investigating would be, in the author's opinion, worthwhile.</t>

</section>
</section>
</section>
<section anchor="upgrading"><name>Upgrading Considerations</name>

<t>At the time of writing, vCard 3.0, which was obsoleted by vCard 4.0 in 2011, is
still in widespread use.  There are complications related to upgrading from
vCard 3.0 to 4.0, and the following is some guidance on how to cope.</t>

<t>First, avoid upgrading to vCard 4.0 unless it is required.  If the card is
ported to new storage that only supports 4.0, or if information has been added
to the card that can only be represented in 4.0, then upgrading the card is
required.</t>

<t>Next, pay special attention to the UID and MEMBER properties across version
boundaries.  In vCard 3.0, <xref target="RFC2426"/>, the UID property was a text type
value.  In the initial vCard 4.0 specification, <xref target="RFC6350"/>, UID could be
either text or URI, but MEMBER was specified as only URI.  This meant that
there was no way to include a 3.0 card as a member of a 4.0 group.</t>

<t>This document's solution is to introduce VALUE=TEXT for MEMBER, so that a group
may refer to the UID of a vCard 3.0 card unambiguously.</t>

<t>Some existing vCard implementations already behaved this way, putting the
literal, text UID of a card into MEMBER, either with or without setting an
explicit VALUE parameter on the MEMBER property.</t>

<t>Other implementations would form a URI value for MEMBER by prepending
<spanx style="verb">urn:uuid:</spanx> to the target card's UID, whether or not the card's UID was a valid
UUID.  When resolving a MEMBER property that begins with that prefix, if no
matching UID is found by the specified (<xref target="prop-uid"></xref>) equivalence rules, the
target might be found by looking for a card with <spanx style="verb">urn:uuid:</spanx> prefix removed.</t>

</section>
<section anchor="example-authors-vcard"><name>Example: Author's vCard</name>

<figure><artwork><![CDATA[
BEGIN:VCARD
VERSION:4.0
FN:Simon Perreault
N:Perreault;Simon;;;ing. jr,M.Sc.
BDAY:--0203
ANNIVERSARY:20090808T1430-0500
GENDER:M
LANG;PREF=1:fr
LANG;PREF=2:en
ORG;TYPE=work:Viagenie
ADR;TYPE=work:;Suite D2-630;2875 Laurier;
 Quebec;QC;G1V 2M2;Canada
TEL;VALUE=uri;TYPE=work,voice;PREF=1:tel:+1-418-656-9254;ext=102
TEL;VALUE=uri;TYPE=work,cell,voice,video,text:tel:+1-418-262-6501
EMAIL;TYPE=work:simon.perreault@viagenie.ca
GEO;TYPE=work:geo:46.772673,-71.282945
KEY;TYPE=work;VALUE=uri:
 http://www.viagenie.ca/simon.perreault/simon.asc
TZ:America/Toronto
URL;TYPE=home:http://nomis80.org
END:VCARD
]]></artwork></figure>

</section>
<section anchor="security-considerations"><name>Security Considerations</name>

<t><list style="symbols">
  <t>Internet mail is often used to transport vCards and is subject to
many well-known security attacks, including monitoring, replay,
and forgery.  Care should be taken by any directory service in
allowing information to leave the scope of the service itself,
where any access controls or confidentiality can no longer be
guaranteed.  Applications should also take care to display
directory data in a "safe" environment.</t>
  <t>vCards can carry cryptographic keys or certificates, as described
in <xref target="prop-key"></xref>.</t>
  <t>vCards often carry information that can be sensitive (e.g.,
birthday, address, and phone information).  Although vCards have
no inherent authentication or confidentiality provisions, they can
easily be carried by any security mechanism that transfers MIME
objects to address authentication or confidentiality (e.g., S/MIME
<xref target="RFC5751"/>, OpenPGP <xref target="RFC4880"/>).  In cases where the confidentiality
or authenticity of information contained in vCard is a concern,
the vCard SHOULD be transported using one of these secure
mechanisms.  The KEY property (<xref target="prop-key"></xref>) can be used to
transport the public key used by these mechanisms.</t>
  <t>The information in a vCard may become out of date.  In cases where
the vitality of data is important to an originator of a vCard, the
SOURCE property (<xref target="prop-source"></xref>) SHOULD be specified.  In addition,
the "REV" type described in <xref target="prop-rev"></xref> can be specified to
indicate the last time that the vCard data was updated.</t>
  <t>Many vCard properties may be used to transport URIs.  Please refer
to <xref target="RFC3986"/>, Section 7, for considerations related to URIs.</t>
</list></t>

</section>
<section anchor="iana-considerations"><name>IANA Considerations</name>

<section anchor="media-type-reg"><name>Media Type Registration</name>

<t>IANA has registered the following Media Type (in
<eref target="http://www.iana.org/">http://www.iana.org/</eref>) and marked the text/directory Media Type as
DEPRECATED.</t>

<dl>
  <dt>To</dt>
  <dd>
    <t>ietf-types@iana.org</t>
  </dd>
  <dt>Subject</dt>
  <dd>
    <t>Registration of media type text/vcard</t>
  </dd>
  <dt>Type name</dt>
  <dd>
    <t>text</t>
  </dd>
  <dt>Subtype name</dt>
  <dd>
    <t>vcard</t>
  </dd>
  <dt>Required parameters</dt>
  <dd>
    <t>none</t>
  </dd>
  <dt>Optional parameters</dt>
  <dd>
    <t>version
</t>

    <t>The "version" parameter is to be interpreted identically as the
VERSION vCard property.  If this parameter is present, all vCards
in a text/vcard body part MUST have a VERSION property with value
identical to that of this MIME parameter.</t>

    <t>"charset": as defined for text/plain <xref target="RFC2046"/>; encodings other
than UTF-8 <xref target="RFC3629"/> MUST NOT be used.</t>
  </dd>
  <dt>Encoding considerations</dt>
  <dd>
    <t>8bit</t>
  </dd>
  <dt>Security considerations</dt>
  <dd>
    <t>See <xref target="security-considerations"></xref>.</t>
  </dd>
  <dt>Interoperability considerations</dt>
  <dd>
    <t>The text/vcard media type is
intended to identify vCard data of any version.  There are older
specifications of vCard <xref target="RFC2426"/><xref target="vCard21"/> still in common use.
While these formats are similar, they are not strictly compatible.
In general, it is necessary to inspect the value of the VERSION
property (see <xref target="prop-version"></xref>) for identifying the standard to which
a given vCard object conforms.
</t>

    <t>In addition, the following media types are known to have been used
to refer to vCard data.  They should be considered deprecated in
favor of text/vcard.</t>

    <t><list style="symbols">
      <t>text/directory</t>
      <t>text/directory; profile=vcard</t>
      <t>text/x-vcard</t>
    </list></t>
  </dd>
  <dt>Published specification</dt>
  <dd>
    <t>RFC 6350</t>
  </dd>
  <dt>Applications that use this media type</dt>
  <dd>
    <t>They are numerous, diverse,
and include mail user agents, instant messaging clients, address
book applications, directory servers, and customer relationship
management software.</t>
  </dd>
</dl>

<t>Additional information
:</t>

<t>Magic number(s):</t>

<t>File extension(s):  .vcf .vcard</t>

<t>Macintosh file type code(s):</t>

<dl>
  <dt>Person &amp; email address to contact for further information</dt>
  <dd>
    <t>vCard
discussion mailing list <eref target="mailto:vcarddav@ietf.org">vcarddav@ietf.org</eref></t>
  </dd>
  <dt>Intended usage</dt>
  <dd>
    <t>COMMON</t>
  </dd>
  <dt>Restrictions on usage</dt>
  <dd>
    <t>none</t>
  </dd>
  <dt>Author</dt>
  <dd>
    <t>Simon Perreault</t>
  </dd>
  <dt>Change controller</dt>
  <dd>
    <t>IETF</t>
  </dd>
</dl>

</section>
<section anchor="registering-elements"><name>Registering New vCard Elements</name>

<t>This section defines the process for registering new or modified
vCard elements (i.e., properties, parameters, value data types, and
values) with IANA.</t>

<section anchor="registration-procedure"><name>Registration Procedure</name>

<t>The IETF has created a mailing list, vcarddav@ietf.org, which can be
used for public discussion of vCard element proposals prior to
registration.  Use of the mailing list is strongly encouraged.  The
IESG has appointed a designated expert who will monitor the
vcarddav@ietf.org mailing list and review registrations.</t>

<t>Registration of new vCard elements MUST be reviewed by the designated
expert and published in an RFC.  A Standards Track RFC is REQUIRED
for the registration of new value data types that modify existing
properties.  A Standards Track RFC is also REQUIRED for registration
of vCard elements that modify vCard elements previously documented in
a Standards Track RFC.</t>

<t>The registration procedure begins when a completed registration
template, defined in the sections below, is sent to vcarddav@ietf.org
and iana@iana.org.  Within two weeks, the designated expert is
expected to tell IANA and the submitter of the registration whether
the registration is approved, approved with minor changes, or
rejected with cause.  When a registration is rejected with cause, it
can be re-submitted if the concerns listed in the cause are
addressed.  Decisions made by the designated expert can be appealed
to the IESG Applications Area Director, then to the IESG.  They
follow the normal appeals procedure for IESG decisions.</t>

<t>Once the registration procedure concludes successfully, IANA creates
or modifies the corresponding record in the vCard registry.  The
completed registration template is discarded.</t>

<t>An RFC specifying new vCard elements MUST include the completed
registration templates, which MAY be expanded with additional
information.  These completed templates are intended to go in the
body of the document, not in the IANA Considerations section.</t>

<t>Finally, note that there is an XML representation for vCard defined
in <xref target="RFC6351"/>.  An XML representation SHOULD be defined for new vCard
elements.</t>

</section>
<section anchor="vendor-namespace"><name>Vendor Namespace</name>

<t>The vendor namespace is used for vCard elements associated with
commercially available products.  "Vendor" or "producer" are
construed as equivalent and very broadly in this context.</t>

<t>A registration may be placed in the vendor namespace by anyone who
needs to interchange files associated with the particular product.
However, the registration formally belongs to the vendor or
organization handling the vCard elements in the namespace being
registered.  Changes to the specification will be made at their
request, as discussed in subsequent sections.</t>

<t>vCard elements belonging to the vendor namespace will be
distinguished by the "VND-" prefix.  This is followed by an IANA-
registered Private Enterprise Number (PEN), a dash, and a vCard
element designation of the vendor's choosing (e.g., "VND-123456-
MUDPIE").</t>

<t>While public exposure and review of vCard elements to be registered
in the vendor namespace are not required, using the vcarddav@ietf.org
mailing list for review is strongly encouraged to improve the quality
of those specifications.  Registrations in the vendor namespace may
be submitted directly to the IANA.</t>

</section>
<section anchor="registration-template-for-properties"><name>Registration Template for Properties</name>

<t>A property is defined by completing the following template.</t>

<dl>
  <dt>Namespace</dt>
  <dd>
    <t>Empty for the global namespace, "VND-NNNN-" for a vendor-
specific property (where NNNN is replaced by the vendor's PEN).</t>
  </dd>
  <dt>Property name</dt>
  <dd>
    <t>The name of the property.</t>
  </dd>
  <dt>Purpose</dt>
  <dd>
    <t>The purpose of the property.  Give a short but clear
description.</t>
  </dd>
  <dt>Value type</dt>
  <dd>
    <t>Any of the valid value types for the property value
needs to be specified, together with the default value type.  When the
default value type is not "text", the registration SHOULD specify "no
default", which makes the VALUE parameter REQUIRED on every instance of
the property, so that a consumer that does not recognize the property
can still determine its value type.</t>
  </dd>
  <dt>Cardinality</dt>
  <dd>
    <t>See <xref target="vcard-properties"></xref>.</t>
  </dd>
  <dt>Property parameters</dt>
  <dd>
    <t>Any of the valid property parameters for the
property MUST be specified.</t>
  </dd>
  <dt>Description</dt>
  <dd>
    <t>Any special notes about the property, how it is to be
used, etc.</t>
  </dd>
  <dt>Format definition</dt>
  <dd>
    <t>The ABNF for the property definition needs to be
specified.</t>
  </dd>
  <dt>Example(s)</dt>
  <dd>
    <t>One or more examples of instances of the property need
to be specified.</t>
  </dd>
</dl>

</section>
<section anchor="registration-template-for-parameters"><name>Registration Template for Parameters</name>

<t>A parameter is defined by completing the following template.</t>

<dl>
  <dt>Namespace</dt>
  <dd>
    <t>Empty for the global namespace, "VND-NNNN-" for a vendor-
specific property (where NNNN is replaced by the vendor's PEN).</t>
  </dd>
  <dt>Parameter name</dt>
  <dd>
    <t>The name of the parameter.</t>
  </dd>
  <dt>Purpose</dt>
  <dd>
    <t>The purpose of the parameter.  Give a short but clear
description.</t>
  </dd>
  <dt>Description</dt>
  <dd>
    <t>Any special notes about the parameter, how it is to be
used, etc.</t>
  </dd>
  <dt>Format definition</dt>
  <dd>
    <t>The ABNF for the parameter definition needs to be
specified.</t>
  </dd>
  <dt>Example(s)</dt>
  <dd>
    <t>One or more examples of instances of the parameter need
to be specified.</t>
  </dd>
</dl>

</section>
<section anchor="registration-template-for-value-data-types"><name>Registration Template for Value Data Types</name>

<t>A value data type is defined by completing the following template.</t>

<dl>
  <dt>Value name</dt>
  <dd>
    <t>The name of the value type.</t>
  </dd>
  <dt>Purpose</dt>
  <dd>
    <t>The purpose of the value type.  Give a short but clear
description.</t>
  </dd>
  <dt>Description</dt>
  <dd>
    <t>Any special notes about the value type, how it is to be
used, etc.</t>
  </dd>
  <dt>Format definition</dt>
  <dd>
    <t>The ABNF for the value type definition needs to be
specified.</t>
  </dd>
  <dt>Example(s)</dt>
  <dd>
    <t>One or more examples of instances of the value type need
to be specified.</t>
  </dd>
</dl>

</section>
<section anchor="registration-template-for-values"><name>Registration Template for Values</name>

<t>A value is defined by completing the following template.</t>

<dl>
  <dt>Value</dt>
  <dd>
    <t>The value literal.</t>
  </dd>
  <dt>Purpose</dt>
  <dd>
    <t>The purpose of the value.  Give a short but clear
description.</t>
  </dd>
  <dt>Conformance</dt>
  <dd>
    <t>The vCard properties and/or parameters that can take
this value needs to be specified.</t>
  </dd>
  <dt>Example(s)</dt>
  <dd>
    <t>One or more examples of instances of the value need to
be specified.</t>
  </dd>
</dl>

<t>The following is a fictitious example of a registration of a vCard
value:</t>

<dl>
  <dt>Value</dt>
  <dd>
    <t>supervisor</t>
  </dd>
  <dt>Purpose</dt>
  <dd>
    <t>It means that the related entity is the direct hierarchical
superior (i.e., supervisor or manager) of the entity this vCard
represents.</t>
  </dd>
  <dt>Conformance</dt>
  <dd>
    <t>This value can be used with the "TYPE" parameter
applied on the "RELATED" property.</t>
  </dd>
</dl>

<t>Example(s):</t>

<figure><artwork><![CDATA[
RELATED;TYPE=supervisor:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
]]></artwork></figure>

</section>
</section>
<section anchor="initial-vcard-elements-registries"><name>Initial vCard Elements Registries</name>

<t>The IANA has created and will maintain the following registries for
vCard elements with pointers to appropriate reference documents.  The
registries are grouped together under the heading "vCard Elements".</t>

<section anchor="properties-registry"><name>Properties Registry</name>

<t>The following table has been used to initialize the properties
registry.</t>

<texttable>
      <ttcol align='left'>Namespace</ttcol>
      <ttcol align='left'>Property</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>&#160;</c>
      <c>SOURCE</c>
      <c>RFC 6350, Section 6.1.3</c>
      <c>&#160;</c>
      <c>KIND</c>
      <c>RFC 6350, Section 6.1.4</c>
      <c>&#160;</c>
      <c>XML</c>
      <c>RFC 6350, Section 6.1.5</c>
      <c>&#160;</c>
      <c>FN</c>
      <c>RFC 6350, Section 6.2.1</c>
      <c>&#160;</c>
      <c>N</c>
      <c>RFC 6350, Section 6.2.2</c>
      <c>&#160;</c>
      <c>NICKNAME</c>
      <c>RFC 6350, Section 6.2.3</c>
      <c>&#160;</c>
      <c>PHOTO</c>
      <c>RFC 6350, Section 6.2.4</c>
      <c>&#160;</c>
      <c>BDAY</c>
      <c>RFC 6350, Section 6.2.5</c>
      <c>&#160;</c>
      <c>ANNIVERSARY</c>
      <c>RFC 6350, Section 6.2.6</c>
      <c>&#160;</c>
      <c>GENDER</c>
      <c>RFC 6350, Section 6.2.7</c>
      <c>&#160;</c>
      <c>ADR</c>
      <c>RFC 6350, Section 6.3.1</c>
      <c>&#160;</c>
      <c>TEL</c>
      <c>RFC 6350, Section 6.4.1</c>
      <c>&#160;</c>
      <c>EMAIL</c>
      <c>RFC 6350, Section 6.4.2</c>
      <c>&#160;</c>
      <c>IMPP</c>
      <c>RFC 6350, Section 6.4.3</c>
      <c>&#160;</c>
      <c>LANG</c>
      <c>RFC 6350, Section 6.4.4</c>
      <c>&#160;</c>
      <c>TZ</c>
      <c>RFC 6350, Section 6.5.1</c>
      <c>&#160;</c>
      <c>GEO</c>
      <c>RFC 6350, Section 6.5.2</c>
      <c>&#160;</c>
      <c>TITLE</c>
      <c>RFC 6350, Section 6.6.1</c>
      <c>&#160;</c>
      <c>ROLE</c>
      <c>RFC 6350, Section 6.6.2</c>
      <c>&#160;</c>
      <c>LOGO</c>
      <c>RFC 6350, Section 6.6.3</c>
      <c>&#160;</c>
      <c>ORG</c>
      <c>RFC 6350, Section 6.6.4</c>
      <c>&#160;</c>
      <c>MEMBER</c>
      <c>RFC 6350, Section 6.6.5</c>
      <c>&#160;</c>
      <c>RELATED</c>
      <c>RFC 6350, Section 6.6.6</c>
      <c>&#160;</c>
      <c>CATEGORIES</c>
      <c>RFC 6350, Section 6.7.1</c>
      <c>&#160;</c>
      <c>NOTE</c>
      <c>RFC 6350, Section 6.7.2</c>
      <c>&#160;</c>
      <c>PRODID</c>
      <c>RFC 6350, Section 6.7.3</c>
      <c>&#160;</c>
      <c>REV</c>
      <c>RFC 6350, Section 6.7.4</c>
      <c>&#160;</c>
      <c>SOUND</c>
      <c>RFC 6350, Section 6.7.5</c>
      <c>&#160;</c>
      <c>UID</c>
      <c>RFC 6350, Section 6.7.6</c>
      <c>&#160;</c>
      <c>CLIENTPIDMAP</c>
      <c>RFC 6350, Section 6.7.7</c>
      <c>&#160;</c>
      <c>URL</c>
      <c>RFC 6350, Section 6.7.8</c>
      <c>&#160;</c>
      <c>VERSION</c>
      <c>RFC 6350, Section 6.7.9</c>
      <c>&#160;</c>
      <c>KEY</c>
      <c>RFC 6350, Section 6.8.1</c>
      <c>&#160;</c>
      <c>FBURL</c>
      <c>RFC 6350, Section 6.9.1</c>
      <c>&#160;</c>
      <c>CALADRURI</c>
      <c>RFC 6350, Section 6.9.2</c>
      <c>&#160;</c>
      <c>CALURI</c>
      <c>RFC 6350, Section 6.9.3</c>
</texttable>

</section>
<section anchor="parameters-registry"><name>Parameters Registry</name>

<t>The following table has been used to initialize the parameters
registry.</t>

<texttable>
      <ttcol align='left'>Namespace</ttcol>
      <ttcol align='left'>Parameter</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>&#160;</c>
      <c>LANGUAGE</c>
      <c>RFC 6350, Section 5.1</c>
      <c>&#160;</c>
      <c>VALUE</c>
      <c>RFC 6350, Section 5.2</c>
      <c>&#160;</c>
      <c>PREF</c>
      <c>RFC 6350, Section 5.3</c>
      <c>&#160;</c>
      <c>ALTID</c>
      <c>RFC 6350, Section 5.4</c>
      <c>&#160;</c>
      <c>PID</c>
      <c>RFC 6350, Section 5.5</c>
      <c>&#160;</c>
      <c>TYPE</c>
      <c>RFC 6350, Section 5.6</c>
      <c>&#160;</c>
      <c>MEDIATYPE</c>
      <c>RFC 6350, Section 5.7</c>
      <c>&#160;</c>
      <c>CALSCALE</c>
      <c>RFC 6350, Section 5.8</c>
      <c>&#160;</c>
      <c>SORT-AS</c>
      <c>RFC 6350, Section 5.9</c>
      <c>&#160;</c>
      <c>GEO</c>
      <c>RFC 6350, Section 5.10</c>
      <c>&#160;</c>
      <c>TZ</c>
      <c>RFC 6350, Section 5.11</c>
</texttable>

</section>
<section anchor="value-data-types-registry"><name>Value Data Types Registry</name>

<t>The following table has been used to initialize the data types
registry.</t>

<texttable>
      <ttcol align='left'>Value Data Type</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>BOOLEAN</c>
      <c>RFC 6350, Section 4.4</c>
      <c>DATE</c>
      <c>RFC 6350, Section 4.3.1</c>
      <c>DATE-AND-OR-TIME</c>
      <c>RFC 6350, Section 4.3.4</c>
      <c>DATE-TIME</c>
      <c>RFC 6350, Section 4.3.3</c>
      <c>FLOAT</c>
      <c>RFC 6350, Section 4.6</c>
      <c>INTEGER</c>
      <c>RFC 6350, Section 4.5</c>
      <c>LANGUAGE-TAG</c>
      <c>RFC 6350, Section 4.8</c>
      <c>TEXT</c>
      <c>RFC 6350, Section 4.1</c>
      <c>TIME</c>
      <c>RFC 6350, Section 4.3.2</c>
      <c>TIMESTAMP</c>
      <c>RFC 6350, Section 4.3.5</c>
      <c>URI</c>
      <c>RFC 6350, Section 4.2</c>
      <c>UTC-OFFSET</c>
      <c>RFC 6350, Section 4.7</c>
</texttable>

</section>
<section anchor="values-registries"><name>Values Registries</name>

<t>Separate tables are used for property and parameter values.</t>

<t>The following table is to be used to initialize the property values
registry.</t>

<texttable>
      <ttcol align='left'>Property</ttcol>
      <ttcol align='left'>Value</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>BEGIN</c>
      <c>VCARD</c>
      <c>RFC 6350, Section 6.1.1</c>
      <c>END</c>
      <c>VCARD</c>
      <c>RFC 6350, Section 6.1.2</c>
      <c>KIND</c>
      <c>individual</c>
      <c>RFC 6350, Section 6.1.4</c>
      <c>KIND</c>
      <c>group</c>
      <c>RFC 6350, Section 6.1.4</c>
      <c>KIND</c>
      <c>org</c>
      <c>RFC 6350, Section 6.1.4</c>
      <c>KIND</c>
      <c>location</c>
      <c>RFC 6350, Section 6.1.4</c>
      <c>VERSION</c>
      <c>4.0</c>
      <c>RFC 6350, Section 6.7.9</c>
</texttable>

<t>The following table has been used to initialize the parameter values
registry.</t>

<texttable>
      <ttcol align='left'>Property</ttcol>
      <ttcol align='left'>Parameter</ttcol>
      <ttcol align='left'>Value</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>FN, NICKNAME, PHOTO, ADR, TEL, EMAIL, IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES, NOTE, SOUND, URL, KEY, FBURL, CALADRURI, and CALURI</c>
      <c>TYPE</c>
      <c>work</c>
      <c>RFC 6350, Section 5.6</c>
      <c>FN, NICKNAME, PHOTO, ADR, TEL, EMAIL, IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES, NOTE, SOUND, URL, KEY, FBURL, CALADRURI, and CALURI</c>
      <c>TYPE</c>
      <c>home</c>
      <c>RFC 6350, Section 5.6</c>
      <c>TEL</c>
      <c>TYPE</c>
      <c>text</c>
      <c>RFC 6350, Section 6.4.1</c>
      <c>TEL</c>
      <c>TYPE</c>
      <c>voice</c>
      <c>RFC 6350, Section 6.4.1</c>
      <c>TEL</c>
      <c>TYPE</c>
      <c>fax</c>
      <c>RFC 6350, Section 6.4.1</c>
      <c>TEL</c>
      <c>TYPE</c>
      <c>cell</c>
      <c>RFC 6350, Section 6.4.1</c>
      <c>TEL</c>
      <c>TYPE</c>
      <c>video</c>
      <c>RFC 6350, Section 6.4.1</c>
      <c>TEL</c>
      <c>TYPE</c>
      <c>pager</c>
      <c>RFC 6350, Section 6.4.1</c>
      <c>TEL</c>
      <c>TYPE</c>
      <c>textphone</c>
      <c>RFC 6350, Section 6.4.1</c>
      <c>BDAY, ANNIVERSARY</c>
      <c>CALSCALE</c>
      <c>gregorian</c>
      <c>RFC 6350, Section 5.8</c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>contact</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>acquaintance</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>friend</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>met</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>co-worker</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>colleague</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>co-resident</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>neighbor</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>child</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>parent</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>sibling</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>spouse</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>kin</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>muse</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>crush</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>date</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>sweetheart</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>me</c>
      <c>RFC 6350, Section 6.6.6 and <xref target="xfn"/></c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>agent</c>
      <c>RFC 6350, Section 6.6.6</c>
      <c>RELATED</c>
      <c>TYPE</c>
      <c>emergency</c>
      <c>RFC 6350, Section 6.6.6</c>
</texttable>

</section>
</section>
</section>
<section anchor="acknowledgments"><name>Acknowledgments</name>

<t>The authors would like to thank Tim Howes, Mark Smith, and Frank
Dawson, the original authors of <xref target="RFC2425"/> and <xref target="RFC2426"/>, Pete
Resnick, who got this effort started and provided help along the way,
as well as the following individuals who have participated in the
drafting, review, and discussion of this memo:</t>

<t>Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil
Srivastava, Barry Leiba, Ben Fortuna, Bernard Desruisseaux, Bernie
Hoeneisen, Bjoern Hoehrmann, Caleb Richardson, Chris Bryant, Chris
Newman, Cyrus Daboo, Daisuke Miyakawa, Dan Brickley, Dan Mosedale,
Dany Cauchie, Darryl Champagne, Dave Thewlis, Filip Navara, Florian
Zeitz, Helge Hess, Jari Urpalainen, Javier Godoy, Jean-Luc Schellens,
Joe Hildebrand, Jose Luis Gayosso, Joseph Smarr, Julian Reschke,
Kepeng Li, Kevin Marks, Kevin Wu Won, Kurt Zeilenga, Lisa Dusseault,
Marc Blanchet, Mark Paterson, Markus Lorenz, Michael Haardt, Mike
Douglass, Nick Levinson, Peter K. Sheerin, Peter Mogensen, Peter
Saint-Andre, Renato Iannella, Rohit Khare, Sly Gryphon, Stephane
Bortzmeyer, Tantek Celik, and Zoltan Ordogh.</t>

</section>


  </middle>

  <back>


<references title='References' anchor="sec-combined-references">

    <references title='Normative References' anchor="sec-normative-references">



<reference anchor="CCITT.X520.1988">
  <front>
    <title>Information Technology - Open Systems Interconnection - The Directory: Selected Attribute Types</title>
    <author>
      <organization>International Telephone and Telegraph
Consultative Committee</organization>
    </author>
    <date month="November" year="1988"/>
  </front>
  <seriesInfo name="CCITT" value="Recommendation X.520"/>
</reference>

<reference anchor="IEEE.754.2008" >
  <front>
    <title>Standard for Binary Floating-Point Arithmetic</title>
    <author >
      <organization>Institute of Electrical and Electronics Engineers</organization>
    </author>
    <date year="2008" month="August"/>
  </front>
  <seriesInfo name="IEEE Standard" value="754"/>
</reference>
<reference anchor="ISO.8601.2000" >
  <front>
    <title>Data elements and interchange formats - Information interchange - Representation of dates and times</title>
    <author >
      <organization>International Organization for Standardization</organization>
    </author>
    <date year="2000" month="December"/>
  </front>
  <seriesInfo name="ISO Standard" value="8601"/>
</reference>
<reference anchor="ISO.8601.2004" >
  <front>
    <title>Data elements and interchange formats - Information interchange - Representation of dates and times</title>
    <author >
      <organization>International Organization for Standardization</organization>
    </author>
    <date year="2004" month="December"/>
  </front>
  <seriesInfo name="ISO Standard" value="8601"/>
</reference>


<reference anchor="RFC2045">
  <front>
    <title>Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
    <author fullname="N. Freed" initials="N." surname="Freed"/>
    <author fullname="N. Borenstein" initials="N." surname="Borenstein"/>
    <date month="November" year="1996"/>
    <abstract>
      <t>This initial document specifies the various headers used to describe the structure of MIME messages. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2045"/>
  <seriesInfo name="DOI" value="10.17487/RFC2045"/>
</reference>
<reference anchor="RFC6838">
  <front>
    <title>Media Type Specifications and Registration Procedures</title>
    <author fullname="N. Freed" initials="N." surname="Freed"/>
    <author fullname="J. Klensin" initials="J." surname="Klensin"/>
    <author fullname="T. Hansen" initials="T." surname="Hansen"/>
    <date month="January" year="2013"/>
    <abstract>
      <t>This document defines procedures for the specification and registration of media types for use in HTTP, MIME, and other Internet protocols. This memo documents an Internet Best Current Practice.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="13"/>
  <seriesInfo name="RFC" value="6838"/>
  <seriesInfo name="DOI" value="10.17487/RFC6838"/>
</reference>
<reference anchor="W3C.REC-xml-20081126" target="https://www.w3.org/TR/2008/REC-xml-20081126/">
  <front>
    <title>Extensible Markup Language (XML) 1.0 (Fifth Edition)</title>
    <author fullname="Eve Maler" role="editor"/>
    <author fullname="François Yergeau" role="editor"/>
    <author fullname="Jean Paoli" role="editor"/>
    <author fullname="Michael Sperberg-McQueen" role="editor"/>
    <author fullname="Tim Bray" role="editor"/>
    <date day="26" month="November" year="2008"/>
  </front>
  <seriesInfo name="W3C REC" value="REC-xml-20081126"/>
  <seriesInfo name="W3C" value="REC-xml-20081126"/>
</reference>

<reference anchor="xfn" target="http://gmpg.org/xfn/11">
  <front>
    <title>XFN 1.1 profile</title>
    <author initials="T." surname="Celik" fullname="Tantek Celik">
      <organization></organization>
    </author>
    <author initials="M." surname="Mullenweg" fullname="Matt Mullenweg">
      <organization></organization>
    </author>
    <author initials="E." surname="Meyer" fullname="Eric Meyer">
      <organization></organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>


<reference anchor="RFC2119">
  <front>
    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
    <author fullname="S. Bradner" initials="S." surname="Bradner"/>
    <date month="March" year="1997"/>
    <abstract>
      <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="2119"/>
  <seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="RFC3629">
  <front>
    <title>UTF-8, a transformation format of ISO 10646</title>
    <author fullname="F. Yergeau" initials="F." surname="Yergeau"/>
    <date month="November" year="2003"/>
    <abstract>
      <t>ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279.</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="63"/>
  <seriesInfo name="RFC" value="3629"/>
  <seriesInfo name="DOI" value="10.17487/RFC3629"/>
</reference>
<reference anchor="RFC5322">
  <front>
    <title>Internet Message Format</title>
    <author fullname="P. Resnick" initials="P." role="editor" surname="Resnick"/>
    <date month="October" year="2008"/>
    <abstract>
      <t>This document specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. This specification is a revision of Request For Comments (RFC) 2822, which itself superseded Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="5322"/>
  <seriesInfo name="DOI" value="10.17487/RFC5322"/>
</reference>
<reference anchor="RFC5234">
  <front>
    <title>Augmented BNF for Syntax Specifications: ABNF</title>
    <author fullname="D. Crocker" initials="D." role="editor" surname="Crocker"/>
    <author fullname="P. Overell" initials="P." surname="Overell"/>
    <date month="January" year="2008"/>
    <abstract>
      <t>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="68"/>
  <seriesInfo name="RFC" value="5234"/>
  <seriesInfo name="DOI" value="10.17487/RFC5234"/>
</reference>
<reference anchor="RFC3986">
  <front>
    <title>Uniform Resource Identifier (URI): Generic Syntax</title>
    <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
    <author fullname="R. Fielding" initials="R." surname="Fielding"/>
    <author fullname="L. Masinter" initials="L." surname="Masinter"/>
    <date month="January" year="2005"/>
    <abstract>
      <t>A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="66"/>
  <seriesInfo name="RFC" value="3986"/>
  <seriesInfo name="DOI" value="10.17487/RFC3986"/>
</reference>
<reference anchor="RFC5646">
  <front>
    <title>Tags for Identifying Languages</title>
    <author fullname="A. Phillips" initials="A." role="editor" surname="Phillips"/>
    <author fullname="M. Davis" initials="M." role="editor" surname="Davis"/>
    <date month="September" year="2009"/>
    <abstract>
      <t>This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="47"/>
  <seriesInfo name="RFC" value="5646"/>
  <seriesInfo name="DOI" value="10.17487/RFC5646"/>
</reference>
<reference anchor="RFC2046">
  <front>
    <title>Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</title>
    <author fullname="N. Freed" initials="N." surname="Freed"/>
    <author fullname="N. Borenstein" initials="N." surname="Borenstein"/>
    <date month="November" year="1996"/>
    <abstract>
      <t>This second document defines the general structure of the MIME media typing system and defines an initial set of media types. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2046"/>
  <seriesInfo name="DOI" value="10.17487/RFC2046"/>
</reference>
<reference anchor="RFC5545">
  <front>
    <title>Internet Calendaring and Scheduling Core Object Specification (iCalendar)</title>
    <author fullname="B. Desruisseaux" initials="B." role="editor" surname="Desruisseaux"/>
    <date month="September" year="2009"/>
    <abstract>
      <t>This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="5545"/>
  <seriesInfo name="DOI" value="10.17487/RFC5545"/>
</reference>
<reference anchor="RFC6351">
  <front>
    <title>xCard: vCard XML Representation</title>
    <author fullname="S. Perreault" initials="S." surname="Perreault"/>
    <date month="August" year="2011"/>
    <abstract>
      <t>This document defines the XML schema of the vCard data format. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6351"/>
  <seriesInfo name="DOI" value="10.17487/RFC6351"/>
</reference>
<reference anchor="RFC3966">
  <front>
    <title>The tel URI for Telephone Numbers</title>
    <author fullname="H. Schulzrinne" initials="H." surname="Schulzrinne"/>
    <date month="December" year="2004"/>
    <abstract>
      <t>This document specifies the URI (Uniform Resource Identifier) scheme "tel". The "tel" URI describes resources identified by telephone numbers. This document obsoletes RFC 2806. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="3966"/>
  <seriesInfo name="DOI" value="10.17487/RFC3966"/>
</reference>
<reference anchor="RFC5870">
  <front>
    <title>A Uniform Resource Identifier for Geographic Locations ('geo' URI)</title>
    <author fullname="A. Mayrhofer" initials="A." surname="Mayrhofer"/>
    <author fullname="C. Spanring" initials="C." surname="Spanring"/>
    <date month="June" year="2010"/>
    <abstract>
      <t>This document specifies a Uniform Resource Identifier (URI) for geographic locations using the 'geo\' scheme name. A 'geo' URI identifies a physical location in a two- or three-dimensional coordinate reference system in a compact, simple, human-readable, and protocol-independent way. The default coordinate reference system used is the World Geodetic System 1984 (WGS-84). [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="5870"/>
  <seriesInfo name="DOI" value="10.17487/RFC5870"/>
</reference>
<reference anchor="RFC4122">
  <front>
    <title>A Universally Unique IDentifier (UUID) URN Namespace</title>
    <author fullname="P. Leach" initials="P." surname="Leach"/>
    <author fullname="M. Mealling" initials="M." surname="Mealling"/>
    <author fullname="R. Salz" initials="R." surname="Salz"/>
    <date month="July" year="2005"/>
    <abstract>
      <t>This specification defines a Uniform Resource Name namespace for UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier). A UUID is 128 bits long, and can guarantee uniqueness across space and time. UUIDs were originally used in the Apollo Network Computing System and later in the Open Software Foundation\'s (OSF) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms.</t>
      <t>This specification is derived from the DCE specification with the kind permission of the OSF (now known as The Open Group). Information from earlier versions of the DCE specification have been incorporated into this document. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4122"/>
  <seriesInfo name="DOI" value="10.17487/RFC4122"/>
</reference>
<reference anchor="RFC2739">
  <front>
    <title>Calendar Attributes for vCard and LDAP</title>
    <author fullname="T. Small" initials="T." surname="Small"/>
    <author fullname="D. Hennessy" initials="D." surname="Hennessy"/>
    <author fullname="F. Dawson" initials="F." surname="Dawson"/>
    <date month="January" year="2000"/>
    <abstract>
      <t>This memo defines three mechanisms for obtaining a URI to a user's calendar and free/busy time. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2739"/>
  <seriesInfo name="DOI" value="10.17487/RFC2739"/>
</reference>
<reference anchor="RFC5546">
  <front>
    <title>iCalendar Transport-Independent Interoperability Protocol (iTIP)</title>
    <author fullname="C. Daboo" initials="C." role="editor" surname="Daboo"/>
    <date month="December" year="2009"/>
    <abstract>
      <t>This document specifies a protocol that uses the iCalendar object specification to provide scheduling interoperability between different calendaring systems. This is done without reference to a specific transport protocol so as to allow multiple methods of communication between systems. Subsequent documents will define profiles of this protocol that use specific, interoperable methods of communication between systems.</t>
      <t>The iCalendar Transport-Independent Interoperability Protocol (iTIP) complements the iCalendar object specification by adding semantics for group scheduling methods commonly available in current calendaring systems. These scheduling methods permit two or more calendaring systems to perform transactions such as publishing, scheduling, rescheduling, responding to scheduling requests, negotiating changes, or canceling. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="5546"/>
  <seriesInfo name="DOI" value="10.17487/RFC5546"/>
</reference>



    </references>

    <references title='Informative References' anchor="sec-informative-references">

<reference anchor="IANA-TZ" >
  <front>
    <title>IANA Procedures for Maintaining the Timezone Database</title>
    <author initials="E." surname="Lear" fullname="Eliot Lear">
      <organization></organization>
    </author>
    <author initials="P." surname="Eggert" fullname="Paul Eggert">
      <organization></organization>
    </author>
    <date year="2011" month="May"/>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-lear-iana-timezone-database"/>
</reference>
<reference anchor="ISO9070" >
  <front>
    <title>Information Processing - SGML support facilities - Registration Procedures for Public Text Owner Identifiers</title>
    <author >
      <organization>International Organization for Standardization</organization>
    </author>
    <date year="1991" month="April"/>
  </front>
  <seriesInfo name="ISO" value="9070"/>
</reference>


<reference anchor="RFC5335bis">
  <front>
    <title>Internationalized Email Headers</title>
    <author fullname="A. Yang" initials="A." role="editor" surname="Yang"/>
    <date month="September" year="2008"/>
    <abstract>
      <t>Full internationalization of electronic mail requires not only the capabilities to transmit non-ASCII content, to encode selected information in specific header fields, and to use non-ASCII characters in envelope addresses. It also requires being able to express those addresses and the information based on them in mail header fields. This document specifies an experimental variant of Internet mail that permits the use of Unicode encoded in UTF-8, rather than ASCII, as the base form for Internet email header field. This form is permitted in transmission only if authorized by an SMTP extension, as specified in an associated specification. This specification Updates section 6.4 of RFC 2045 to conform with the requirements. This memo defines an Experimental Protocol for the Internet community.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="5335"/>
  <seriesInfo name="DOI" value="10.17487/RFC5335"/>
</reference>

<reference anchor="TZ-DB" target="ftp://elsie.nci.nih.gov/pub/">
  <front>
    <title>Time zone code and data</title>
    <author initials="A. D." surname="Olson" fullname="Arthur David Olson">
      <organization></organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>
<reference anchor="vCard21" >
  <front>
    <title>vCard - The Electronic Business Card Version 2.1</title>
    <author >
      <organization>Internet Mail Consortium</organization>
    </author>
    <date year="1996" month="September"/>
  </front>
</reference>


<reference anchor="RFC6350">
  <front>
    <title>vCard Format Specification</title>
    <author fullname="S. Perreault" initials="S." surname="Perreault"/>
    <date month="August" year="2011"/>
    <abstract>
      <t>This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and updates RFC 2739. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6350"/>
  <seriesInfo name="DOI" value="10.17487/RFC6350"/>
</reference>
<reference anchor="RFC3536">
  <front>
    <title>Terminology Used in Internationalization in the IETF</title>
    <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
    <date month="May" year="2003"/>
    <abstract>
      <t>This document provides a glossary of terms used in the IETF when discussing internationalization. The purpose is to help frame discussions of internationalization in the various areas of the IETF and to help introduce the main concepts to IETF participants. This memo provides information for the Internet community.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="3536"/>
  <seriesInfo name="DOI" value="10.17487/RFC3536"/>
</reference>
<reference anchor="RFC6868">
  <front>
    <title>Parameter Value Encoding in iCalendar and vCard</title>
    <author fullname="C. Daboo" initials="C." surname="Daboo"/>
    <date month="February" year="2013"/>
    <abstract>
      <t>This specification updates the data formats for iCalendar (RFC 5545) and vCard (RFC 6350) to allow parameter values to include certain characters forbidden by the existing specifications.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6868"/>
  <seriesInfo name="DOI" value="10.17487/RFC6868"/>
</reference>
<reference anchor="RFC3282">
  <front>
    <title>Content Language Headers</title>
    <author fullname="H. Alvestrand" initials="H." surname="Alvestrand"/>
    <date month="May" year="2002"/>
    <abstract>
      <t>This document defines a "Content-language:" header, for use in cases where one desires to indicate the language of something that has RFC 822-like headers, like MIME body parts or Web documents, and an "Accept-Language:" header for use in cases where one wishes to indicate one's preferences with regard to language. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="3282"/>
  <seriesInfo name="DOI" value="10.17487/RFC3282"/>
</reference>
<reference anchor="RFC2397">
  <front>
    <title>The "data" URL scheme</title>
    <author fullname="L. Masinter" initials="L." surname="Masinter"/>
    <date month="August" year="1998"/>
    <abstract>
      <t>A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2397"/>
  <seriesInfo name="DOI" value="10.17487/RFC2397"/>
</reference>
<reference anchor="RFC2616">
  <front>
    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
    <author fullname="R. Fielding" initials="R." surname="Fielding"/>
    <author fullname="J. Gettys" initials="J." surname="Gettys"/>
    <author fullname="J. Mogul" initials="J." surname="Mogul"/>
    <author fullname="H. Frystyk" initials="H." surname="Frystyk"/>
    <author fullname="L. Masinter" initials="L." surname="Masinter"/>
    <author fullname="P. Leach" initials="P." surname="Leach"/>
    <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
    <date month="June" year="1999"/>
    <abstract>
      <t>HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1", and is an update to RFC 2068. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2616"/>
  <seriesInfo name="DOI" value="10.17487/RFC2616"/>
</reference>
<reference anchor="RFC1738">
  <front>
    <title>Uniform Resource Locators (URL)</title>
    <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
    <author fullname="L. Masinter" initials="L." surname="Masinter"/>
    <author fullname="M. McCahill" initials="M." surname="McCahill"/>
    <date month="December" year="1994"/>
    <abstract>
      <t>This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="1738"/>
  <seriesInfo name="DOI" value="10.17487/RFC1738"/>
</reference>
<reference anchor="RFC4770">
  <front>
    <title>vCard Extensions for Instant Messaging (IM)</title>
    <author fullname="C. Jennings" initials="C." surname="Jennings"/>
    <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
    <date month="January" year="2007"/>
    <abstract>
      <t>This document describes an extension to vCard to support Instant Messaging (IM) and Presence Protocol (PP) applications. IM and PP are becoming increasingly common ways of communicating, and users want to save this contact information in their address books. It allows a URI that is associated with IM or PP to be specified inside a vCard. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4770"/>
  <seriesInfo name="DOI" value="10.17487/RFC4770"/>
</reference>
<reference anchor="RFC6068">
  <front>
    <title>The 'mailto' URI Scheme</title>
    <author fullname="M. Duerst" initials="M." surname="Duerst"/>
    <author fullname="L. Masinter" initials="L." surname="Masinter"/>
    <author fullname="J. Zawinski" initials="J." surname="Zawinski"/>
    <date month="October" year="2010"/>
    <abstract>
      <t>This document defines the format of Uniform Resource Identifiers (URIs) to identify resources that are reached using Internet mail. It adds better internationalization and compatibility with Internationalized Resource Identifiers (IRIs; RFC 3987) to the previous syntax of 'mailto' URIs (RFC 2368). [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6068"/>
  <seriesInfo name="DOI" value="10.17487/RFC6068"/>
</reference>
<reference anchor="RFC3406">
  <front>
    <title>Uniform Resource Names (URN) Namespace Definition Mechanisms</title>
    <author fullname="L. Daigle" initials="L." surname="Daigle"/>
    <author fullname="D. van Gulik" initials="D." surname="van Gulik"/>
    <author fullname="R. Iannella" initials="R." surname="Iannella"/>
    <author fullname="P. Faltstrom" initials="P." surname="Faltstrom"/>
    <date month="October" year="2002"/>
    <abstract>
      <t>This document lays out general definitions of and mechanisms for establishing Uniform Resource Names (URN) "namespaces". The URN WG has defined a syntax for URNs in RFC 2141, as well as some proposed mechanisms for their resolution and use in Internet applications in RFC 3401 and RFC 3405. The whole rests on the concept of individual "namespaces" within the URN structure. Apart from proof-of-concept namespaces, the use of existing identifiers in URNs has been discussed in RFC 2288. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="3406"/>
  <seriesInfo name="DOI" value="10.17487/RFC3406"/>
</reference>
<reference anchor="RFC2426">
  <front>
    <title>vCard MIME Directory Profile</title>
    <author fullname="F. Dawson" initials="F." surname="Dawson"/>
    <author fullname="T. Howes" initials="T." surname="Howes"/>
    <date month="September" year="1998"/>
    <abstract>
      <t>This memo defines the profile of the MIME Content-Type for directory information for a white-pages person object, based on a vCard electronic business card. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2426"/>
  <seriesInfo name="DOI" value="10.17487/RFC2426"/>
</reference>
<reference anchor="RFC5751">
  <front>
    <title>Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification</title>
    <author fullname="B. Ramsdell" initials="B." surname="Ramsdell"/>
    <author fullname="S. Turner" initials="S." surname="Turner"/>
    <date month="January" year="2010"/>
    <abstract>
      <t>This document defines Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.2. S/MIME provides a consistent way to send and receive secure MIME data. Digital signatures provide authentication, message integrity, and non-repudiation with proof of origin. Encryption provides data confidentiality. Compression can be used to reduce data size. This document obsoletes RFC 3851. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="5751"/>
  <seriesInfo name="DOI" value="10.17487/RFC5751"/>
</reference>
<reference anchor="RFC4880">
  <front>
    <title>OpenPGP Message Format</title>
    <author fullname="J. Callas" initials="J." surname="Callas"/>
    <author fullname="L. Donnerhacke" initials="L." surname="Donnerhacke"/>
    <author fullname="H. Finney" initials="H." surname="Finney"/>
    <author fullname="D. Shaw" initials="D." surname="Shaw"/>
    <author fullname="R. Thayer" initials="R." surname="Thayer"/>
    <date month="November" year="2007"/>
    <abstract>
      <t>This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. It is not a step-by-step cookbook for writing an application. It describes only the format and methods needed to read, check, generate, and write conforming packets crossing any network. It does not deal with storage and implementation questions. It does, however, discuss implementation issues necessary to avoid security flaws.</t>
      <t>OpenPGP software uses a combination of strong public-key and symmetric cryptography to provide security services for electronic communications and data storage. These services include confidentiality, key management, authentication, and digital signatures. This document specifies the message formats used in OpenPGP. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4880"/>
  <seriesInfo name="DOI" value="10.17487/RFC4880"/>
</reference>
<reference anchor="RFC2425">
  <front>
    <title>A MIME Content-Type for Directory Information</title>
    <author fullname="T. Howes" initials="T." surname="Howes"/>
    <author fullname="M. Smith" initials="M." surname="Smith"/>
    <author fullname="F. Dawson" initials="F." surname="Dawson"/>
    <date month="September" year="1998"/>
    <abstract>
      <t>This document defines a MIME Content-Type for holding directory information. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2425"/>
  <seriesInfo name="DOI" value="10.17487/RFC2425"/>
</reference>
<reference anchor="RFC6474">
  <front>
    <title>vCard Format Extensions: Place of Birth, Place and Date of Death</title>
    <author fullname="K. Li" initials="K." surname="Li"/>
    <author fullname="B. Leiba" initials="B." surname="Leiba"/>
    <date month="December" year="2011"/>
    <abstract>
      <t>The base vCard 4.0 specification defines a large number of properties, including date of birth. This specification adds three new properties to vCard 4.0: place of birth, place of death, and date of death. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6474"/>
  <seriesInfo name="DOI" value="10.17487/RFC6474"/>
</reference>



    </references>

</references>


<?line 3716?>

<section anchor="changes-from-2426"><name>Differences from RFCs 2425 and 2426</name>

<t>This appendix contains a high-level overview of the major changes
that have been made in the vCard specification from RFCs 2425 and
2426.  It is incomplete, as it only lists the most important changes.</t>

<section anchor="new-structure"><name>New Structure</name>

<t><list style="symbols">
  <t><xref target="RFC2425"/> and <xref target="RFC2426"/> have been merged.</t>
  <t>vCard is now not only a MIME type but a stand-alone format.</t>
  <t>A proper MIME type registration form has been included.</t>
  <t>UTF-8 is now the only possible character set.</t>
  <t>New vCard elements can be registered from IANA.</t>
</list></t>

</section>
<section anchor="removed-features"><name>Removed Features</name>

<t><list style="symbols">
  <t>The CONTEXT and CHARSET parameters are no more.</t>
  <t>The NAME, MAILER, LABEL, and CLASS properties are no more.</t>
  <t>The "intl", "dom", "postal", and "parcel" TYPE parameter values
for the ADR property have been removed.</t>
  <t>In-line vCards (such as the value of the AGENT property) are no
longer supported.</t>
</list></t>

</section>
<section anchor="new-properties-and-parameters"><name>New Properties and Parameters</name>

<t><list style="symbols">
  <t>The KIND, GENDER, LANG, ANNIVERSARY, XML, and CLIENTPIDMAP
properties have been added.</t>
  <t><xref target="RFC2739"/>, which defines the FBURL, CALADRURI, CAPURI, and CALURI
properties, has been merged in.</t>
  <t><xref target="RFC4770"/>, which defines the IMPP property, has been merged in.</t>
  <t>The "work" and "home" TYPE parameter values are now applicable to
many more properties.</t>
  <t>The "pref" value of the TYPE parameter is now a parameter of its
own, with a positive integer value indicating the level of
preference.</t>
  <t>The ALTID and PID parameters have been added.</t>
  <t>The MEDIATYPE parameter has been added and replaces the TYPE
parameter when it was used for indicating the media type of the
property's content.</t>
</list></t>

</section>
<section anchor="updated-property-value-data-types"><name>Updated Property Value Data Types</name>

<t><list style="symbols">
  <t>The syntax of the UTC-OFFSET property value type has changed from:</t>
</list></t>

<figure><artwork><![CDATA[
"+" / "-" hour ":" minute
]]></artwork></figure>

<t>to</t>

<figure><artwork><![CDATA[
"+" / "-" hour [minute]
]]></artwork></figure>

<t><list style="symbols">
  <t>The default value type for the UID property has changed from TEXT to URI.</t>
  <t>The default value type for the PHOTO, LOGO, SOUND, and KEY properties has
changed from BINARY to URI.</t>
  <t>The default value type for the TZ property has changed from UTC-OFFSET to
TEXT.</t>
  <t>The value type for the GEO property has changed from a structured value of
the form: float ";" float to a URI.</t>
</list></t>

</section>
</section>
<section anchor="changes-from-6350"><name>Changes from RFC 6350</name>

<t>This appendix summarizes the major changes made in this document relative
to <xref target="RFC6350"/>.  It is not exhaustive.</t>

<section anchor="incorporated-extensions"><name>Incorporated Extensions</name>

<t><list style="symbols">
  <t>The parameter value escaping mechanism of <xref target="RFC6868"/>, which uses the
CIRCUMFLEX ACCENT character to encode line breaks and DQUOTE characters in
parameter values, has been incorporated (see <xref target="param-escaping"></xref>).  This
document replaces the provisions of RFC 6868 that apply to vCard; its
provisions for iCalendar are unaffected.</t>
  <t>The BIRTHPLACE, DEATHPLACE, and DEATHDATE properties, defined in
<xref target="RFC6474"/>, have been incorporated.  The LANGUAGE parameter is now
limited to text values on BIRTHPLACE and DEATHPLACE.</t>
</list></t>

</section>
<section anchor="other-changes"><name>Other Changes</name>

<t><list style="symbols">
  <t>The LABEL parameter of the ADR property continues to encode line breaks
as \n, for compatibility with RFC 6350 implementations, but parsers must
also accept the ^n encoding of <xref target="param-escaping"></xref>.  Parsers also accept \N,
which RFC 6350 permitted as an alternative to \n.</t>
  <t>The MEMBER property may now have a text value, which refers to a member
vCard by its UID when that UID is itself a text value, as is common for
vCards converted from vCard 3.0.  A rule for comparing UID and MEMBER
values, including values of differing types, has been added (see
<xref target="prop-uid"></xref> and <xref target="prop-member"></xref>).</t>
  <t>The rules for backslash escaping in property values have been rewritten
(see <xref target="value-escaping"></xref>).  Escaping now applies only to "text" and
"component" values.  In particular, a COMMA or SEMICOLON in a URI value is
not escaped, although parsers may accept such escapes in data produced
under RFC 6350.  The ABNF for "text" now also permits an escaped
SEMICOLON, as the prose of RFC 6350 already did.  This resolves RFC 6350
errata 3845, 3846, and 6864, RFC 6474 errata 4557 and 4559, and RFC 6868
erratum 4383.</t>
  <t>The truncated forms of a "time" value no longer permit a time zone,
consistent with ISO 8601 (see <xref target="type-time"></xref>).</t>
  <t>The ANNIVERSARY property now permits the LANGUAGE parameter when its
value is text, as BDAY does (see <xref target="prop-anniversary"></xref>).</t>
  <t>An unquoted parameter value may no longer contain a COMMA, which
separates the elements of a multi-valued parameter.  The "SAFE-CHAR" ABNF
rule has been changed accordingly.</t>
  <t>A property defined outside this document whose default value type is not
"text" should include the VALUE parameter on every instance, and its
registration should specify no default value type (see
<xref target="param-value-type"></xref> and <xref target="registering-elements"></xref>).</t>
  <t>A section on upgrading vCard 3.0 data to vCard 4.0 has been added (see
<xref target="upgrading"></xref>).</t>
  <t>Examples that wrote a multi-valued parameter as a single quoted string,
such as <spanx style="verb">TYPE="voice,home"</spanx>, have been corrected.  A quoted parameter
value is a single value even if it contains a COMMA; <spanx style="verb">TYPE=voice,home</spanx>
gives two values.</t>
  <t>Many other errata against RFC 6350 have been applied, correcting
typographical errors, examples, cross-references, and details of the
ABNF.</t>
</list></t>

</section>
</section>


  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA+y9aXfbVrIo+h2/Ape9zoqVJikOGql2n0NLlKO0pkh05vQN
SIIUYhJgA6BkJZ3z219NewJASnLcZ3jvOSu2BGzssap2zdVoNLw8yudhz6/d
HwfpxD9N0kWQ+7fLcBxNo3GQR0lc84LRKA3vez618eBpOEvSx56f5RPPS0ZZ
Mg/zMOv5e93dlrdaTgL6zZsk4zhYQOeTNJjmjSjMp41xMA8/5I37MfS00xhF
WaPV9rLVaBFlGYyVPy6h/dlgeOrFq8UoTHse9tbzxkmchXG2gn7zdBV6MJuu
F6RhAFPvL5dzmWvmB/HEvwmDeWMYLcKa95Ck72dpslpCu2MYO54EqT/4kENf
2LzmvQ8foc2k5/l+w6dpeV6wyu+SlB9NV/M5r+ImwreJfxvN4jCDl76fpLMg
jn6loXv+aZDliyCa06sQf+r56S+j7D+ycBEleTRuZo9ZHi742zTBfQ8nUZ6k
nhfTxkf3IY56fHw2HDa/3e20mu3DgwN8dDYYDJr7uzvNTqtFD3xfndxtHuCq
Jv40Sf03URykj/7pPIHe4lnjOoni3O+nUX63CGEKNfrULFBWAd2cxRn0uMpD
P5n6g3k4zlNY8Jw2lH9N4mic+YN4FsVhmGbcFR2Pj7NqtA7oSRamUZhF8TRR
A9Rw9r6aZw0Gg5Xg52e3V82DvVYbV9VyV3US5IEfzsNFGOd8qrCQMB3fBfEs
xKXCdmVwPmcx/wwn4LRoABQs0xCAJueXsCoCTOorB+DINu0FdBTTd7ADV9Yp
0yarlcizwka0Gu3O2o24vXL2ARdf3Iid/7dsxM5HbMTN6XGntbPb4x/3DroE
7N90j5s3g+PGh8W8gaDWbnf28PmHaexu1renl3672faXaTKN5mHVwho+o3Nt
GMDi3vvH4Tx6Xyu+vAjy3L8A3A/jh3BWej0A3PAvwscw5Vd5kM7CvOff5fmy
t709WyxnTdjBbZjgdrvteZE6HEbws/5lvzH83p07PvSv02QcTlZwXrTBFwEc
JfwPqOznd6GPRO3XJA59hIpRkG1e4WAOZMc/D4O0tIDrYDX3B7NZmObuqbXb
jdbumlNjaAjzxgkSdEXX59B/IwrioJHL7BoTmR1D9mFrv4DcNqzSioH4wwob
/u3bi3M/Wy2XSZr702AczaMcJkFAPIuyPLW+Mbt0vRrBBeAP4Wbxrx7iMPXP
JgDucINpMvVpgbt9eAjbtLMBuBGmcd0C07vd7i5cdthi+H3j5I27HXiqPh3r
OJmEhJe4gxvPtp/md6sU4OA+mvhX80xNUEHilAAxnGdR2IzHUTOO7pqz5H57
uRptQ0O6yjttdx7MAzT8IUCaIfn+mxUsD47Ip9dfw57iFnWa7ae2NswRgOf+
Mdy0cKDRalHYxL1G69BrABeCf/nBCA94nHve8C7KfGAfVkj0/Ek4xfEJAXiK
uDtC+uioUkXhEIpg+7zwA1E/+tW/D+CE8kckfJEFeMEoWeXwZBLBFq6CORPE
BEZJPeyKAO9V2Jw16zJWHk6oDUxzNc4B/CZ0GnxgQEbuQ7h6g8kE5pKFWd0j
HkA9qPuL1TyPlvPQz4GcL+/wvJnJgXfwa57M0mB5V/fnySypw7ZOosQbz6Ml
vA7zcXOrCcDjbIxmvRDEiPtq8k4uoslkHnrenxBl02QCs4UVe551qDIrf5Qk
7zP/LrgP/VE4TmA1q1H0jxVwJauMBgyjFDZpDKxWFk483ucxMAmxj0gajOZh
HcA2jqHnELfhPhrj3ZL5D+F8jv/isU1wb7KIDsFbzoMcNxRfwQHKWSHwA60b
53y6wHrM6WwD2G5GRLX+RbhIvDJQ8BnV/Ye7aHznw+fJA78eB0s8LDomPRjM
wwYG4r/m80cYLMFzfQCGKQIYiZ2NAuiGpaSwVOB/vcDwnbDvff8umt0BNbwP
534Cy72PwgeEOV7/dBqmuHFAsdJkgQeW+Z2dzi7NCn7Yg2nG3ghv9BXd8f4P
P736E082a+A3DWyFQNAHCrlYIJsnvUsr6tn77bd/x5sTgOH337FPf2Of2G6r
iZACSHqPYA+4iggY+sAZ+8gaZ3Abvrsd1ur8r395RT/fDL56d3YzOMGfb7/o
n5/rH7iFB79cvTuX9/iT+fL46uJicHnCH8NTv/Doov8d/IOIXLu6Hp5dXfbP
azj93AF/YP/9PMH1Eb8DoEkICi3CbJxGoxCXDPvxf5CpaLcPf/+dFrpe0uF1
53CNbJMk4F+cXQwILHE4lE38V0AdQrj14I55HycPMQ7HdLN2BFdB6OEOL4Cr
h9sQ2jfScLa1xZAdgXSiQNwCvTp2jJw2AN8SrmN12yd+4OGtODeIAdBHsgye
uzwTHNWTRDkJ7skMmyCBAdliAQDtzwlZaAsV0+jPACkRPABRcGMABO6CNAtz
3oYx/+K/glX5DFTd3e4eABViZWTfnerWhEeLKE6Afj1uYSuPtxrO7N3wtHHA
R4NoS7DIB9Pd6+DB0CpgntA2TvyH4BE3ALEojSahh+cOTc5yfB/F9zDkBBtk
dHqPROPnq5CJN1KV2K/RkAI1oVeT5dT4TJdBCoQbT5GWV3VovCXnETJbQNsX
kbpcAHTmE/z5tz/hrjam/Ovvnnem7xLZb6EivA0IrhPuCTZg9EhHwZuw2+10
YGPxIw9E7eC9omKw3MA/vjk/Bdj6x4oI76t3fwYZ4wT2Fykc90SP+kgbzpN4
5sEBkOjGk0AigZyR0IIMiBYCIAKYvpIay7vHDL9p0BxSV2JYZYr/5EHxN1k1
dD2+i+HCCGHwYwFCGtcTpCfyM5+EdGAwYvAhWqwWsDWT/A7ntr/rJ3B15HjL
fRjPVxM1ltkN6PoCJ9qghgSZAPpwofhEkFK8Z2NCgWi20veWnwp4hh5CLNEO
NeslM50l+mgfR92/DeneRFYH/kMSb++sD1QKP6Zx4xUsMGH0inG31YZy0yB+
fED4BgKfP4SAdflDYq8DzhDIA2A/cyx04tGCQBKYhUfnsDVZABDJ8TyDcWj6
AoCmBwQmndYWEg1gz6JfkV7MgT0ceQxBh1tbsk9yPLwm3FAhVz7QCGDus5wo
iR4Bb6D40dMACWdI89VztCeO8/XL8/XMfBGjZzFduq/gJAHnJ1vQFPZoaSSD
3CJxiKIwByDgwOYFiyUyIApeep73n//5n8BkwqUy6BG3QCg0B7SQa2HJpIo5
DyaVsWqBXTSpB08gQ2MC3SzP7Z656qeGOENyvZpDx8C+f9xgHnHvxfXg06oB
8bAV5MOpwV4TJiM/orEDhtZEgSDCpQUefBdgJ3hVPTI5j3gGiR/B4HzWVZ/i
7PGaAy5yFQsiwjm+Uz/T6sbAggKByu4Y1oESowQGL4so4TkosQ4XkD2fP9b9
L4b9N76Ce0SJ2+v+8cBTSLKFVxPAc3SPKsIc1xI7+Ambi/zoq6gZNhnaaD7I
oWxERqT5CqiBgFwmKPjwNbZMALSBe6brlCSHLEJg9unvhdq1DCczC0GohWV7
8I62nkmCwlp9sTPf79MZ8ZW7MHRTYywjDx85svXIgxQHFeLNB6UH8bIVstZ0
Pwc0Mz0dOGjknGkaQG5A9AJqo0dUS3cOe4JkRXHG+fyRL+4CFbYhxCu8A7Si
kXF/M30qdTi7nH7j0zB3VpTDRE4LE2BmDgi0JjAw44Sa0D4S20fsRdMrT38U
ThMSLRAXqj/DFQWqc4/REVmL/pvLU8WGnmg8Yiw1c6ZWq0zWByvTSjzZiU53
B+8qJfUAJRHRyOPN+Ob2uu6ffPUOiEjd//r4i/5N3e+fX3/RJwbbPzl7ezZs
EqkBiTieesT5NkgAfvRf++3PRSnOHPFrv/Zm8Pbssvf1cf/mpEYbLpK/79e+
HtzcArfe22m2Cq/an8sG0K2uPwCOv9DTEYg3zC8lo1/g/uUbCQRQ4AwYumQQ
ZsUuFS0CYb1Jn6vXcpMtQuc+4tO2lgBLt2YG6/uBWexas/YTS/efv6od1Zhj
3PJrvZqcqp7vN3RXAXfJd/fYYoLqLpYuVnCXTqM0y+lDoPiMX0jugfAxoQOk
wlVqEskUG5Vd9JEt22gGpdvsNM1chFpUTYfngfeC4pP3d+lDi9aV+LbS3BQ6
4od6dhtm5vGWIjC9ItDztxnu4N9ao7bl0T4jbN1evbs5HtTw+d/OLk/oh9NL
+kf+Pjv+22X/YqAUmvDo+our4RW9fHMCciP+0L+8PEM46N/w729RsrzhVyf8
73BwbvUxuOifndPzs4vra/rhvH/5llt+L33wIMOz4TnP8Obq3J7H+dVbbnF1
wx9eDC7eyKg3g/P+cMDrOYaf3l7dnA1urY/xjqe31zdXJ2cn8tHX9C9simzF
O3lzfH42uBxen51c9K+tTt7d8Br+NuBln75RT47757Dwdzdn6jf147cX9ja8
ObsZfnF93pcjOBn0S7+ewOzNF6z2Td4D1G37Hxp4jgQV14IOoqAg5CGEFYoI
HC+qkxTHXMMPa3ClCIhrGZGoX8awlClRFdu8JYjCHlkDl6KaJwsbEZkJI1S0
A9xZ01sPfNhdpPXFyHIAFxUqJRDp6j2P14Yg+qFR29jVJbQTzdYIuoq5F/oM
Lt3at/BvILiMzFEKrAGxAOEHIGMRXcFzJPh8jaGcHU+kSRrOWQsniId6PRCb
4A2+hW9wy0bRHEhdipa7WRqy2Qi2go/gtT8P4tkqmIHERw+2+UT0b8CwTc0v
0YR/1udN4rF6PQuThhGk4eWvzq+o8m0EWaEH4AAzNALrXuDq1E2A+AtTpztC
lcEyjAlUNNuJZ6HW1GCQeu1/fts/HTTwgoNeX8mV53/+lXksj7Y8Tw+KVOdV
BRQDpX8tRF8GgGug7jyBbi6vLhv92+OzM+gF+K2DRgc6oB+66ocdWhb9+Fun
3q3v/C6KAA3jP4gW5CfPs+b6Gi9uhKv/g7j3bx863cb+AH7SQ/J2IduiuU2Q
n8Nl7h8PzzN15fsj0nEruRr5YM/bOErnDf900uge0k/d448aue7DfsFfR/gX
3JowEUY1dzIkmPRZ+DRIw6qTtXw9yUEidyt+yCNCk4b3UbLK5Lor6AJJz2Pr
bJQEXC2Zkq3V4h2g83EYGmkkuyPpbYRMbIbcEZIMuIA9aAfkiowESnjVLDHx
fyDTATvM6yU23J4U8iOiiRXuOFMyGpk7KlUVUax6CzXX7f38F5znX/8CZ/zX
n+VLpYlQIoPiD9AOMmazsKXRIG6NTB56rSLOAPpd2+jI1hOD//Ksgi4rmwqq
5RyM9mvTuIZnS4sgsp7x9Y9d107jGp7XtR6CsDDzlBoGhzGDAEEsDlwXUkIX
E60+Sj0jwVb0zXuKi0BaDBR6Ho0jlFQU+sKNNQqxv8LolfeR779Rlx4Te1Kf
IKCLorTLalXckmCEpk+QXCMSFi39OM9JbxyKoMVdR8ZyCa8bOAUcLlnlyxUK
PwjszIxpCMXuVxmr5/gVXDMBqiAMZw3vZiHqVptWD3RkhInZI+mio7Fvga7q
UwGW7OV87h56RlcOIJ5ct/rsrUEMR0oP4QJU82FFEaDfch48ii4ApC3LMENa
47uA1Mps28uiWUwqfxaFz4riNk5zktCJA8IA9uVkF0yVXZq5WTx0hDwS2tFs
lEaol5+SKEj6ViUaoiihOOd5OM0VrSIJUdsPRVPiqzeZYZfImsYGKhvrxqQZ
CcRCHhBK81ZPKjW2Snase1q3rJkw4rNE029LlYaN39vqed4/yQTMgz7Cdf5P
/yIMyFzx7D//hE56DfOnB500XviHOmm73fqDDwCCcBIolQPW5Xi8aFARaZLE
wVGo9rnJM/nx8/aLOmFSY/rgmfz4udPJFdldfLK7qE6yTVPhmfgv66Q4lX9q
0EBwsPiLQL7Q61kEj2zw1QZpoaRF8miojIG1R7kyWcic++lKVFhKa+Kxyom6
dGhIRAojwRe0J+eIHHH44MioZDcKA4BPZrteGX7BmRExaTCXL4BdvA9TIpT6
kvIA1pH6ICpnqALgvhivlHuJVvMUtoH2zDa96akBdclCJLb6WpcvhFkZJ4tF
gGyPWKrRQpwmuBYkQCPS+wfIZeJ+ZTht2EBlw7W02/r4PJJ4/FfoMFEnX606
XREzXPAUffzYHqx35eEuybTaKfOMo0LdZ9Vd5oMciIAFQmrdV/ZcnPkIV6i3
woBcsmY3jnw6JQ1VqNKcEx1HVS+qoR9i32i7NNn6miY3AIZpyUY0FkBCefC7
530jtnezLGpS98dsHnUUs4Ae9KkmeoH/pn/8t9vz/u0XFi9Hmt7dY94uvEv7
YiE5JnVw4N8OLs6Or86vLvl5980Wrkh1PXr0iPtj3V+uDlyPBNubMLjxfU0a
SH3UgQKbJD2CzQQsopPXX+MXD2mUw96SWvUhsd6ZxR7RlRD4l4Nvzs8uRXvd
6vNEEZjZ+m1Ny7Ubxf5n8We8vL0BLxseXX7GHe0McHO+oauBYTIL7Z0m5dXI
7DYTi0yRCjqizzKPrDPI0dfwElTKMgI0/pIuSD6BKNeW8bof3uvd0ueOO+pN
kpA3lFw6Stj6Cr8RszfswuMW6zULI3pmT6C57CAzB0hJVUMLDFBwikN08Uny
OvrGBMDReMovxF2e/R0cBmnL0D9D4QscvTZMAzIpYOB9QosH3Dex7g0uONzR
0SpiBeBonozf45lYfkcWXZ1H79FCjogPbS7riOG8B4Djapegz8ozqJuZ1z0L
nM0mVZwSCxDEqakZ+eqUvGeeEqz9apVn0YRmLbtJfH5xPzLUhMRhJVACjRN4
RBtxAhBqU3pg8RButDkzVh4zC96fYA7btpoBJnu1VRqp/cf7UX8joFqkEeK8
cHiw9/vvCHH+u5sznE2MVJ1v3XmUkcuGXg89UcaXZA40QMyndD9notEh89gE
ZeognaNCKrNdVDIcC5XN8AIBNxiT4B0AKzd+n82D7K4hG+LpiZtpG+i1lisu
WooqGTsvQucUrudlka0gnywNirqXwJ9GH+CBbRmeRuF8knk2ApAsWz7lI9/W
atL5sNqW1GVi6c1KXkCIwzFdRWyXowF9Q6xZIF5E42SexJ5ABFxP4XxqHbJu
IYQcJY0Afax8wD2SirkfQVw4oQAuTHI2mD8euYMo+i/nwKBGdyXPDaDE8Vey
tevq3hQqCitDsyO7taAwhxiobk59eaO4l5FEjveslgVLFy3rrqyLdsBaG0TN
8/6bwblwOehykbm6E+JDeIMNIVU9eSUdi3ulb6kdIZEwsvR4y4K83WTPT1H4
6vF59/XCFyG6sEXZQmtVLImcPL7IA+5g78AYxrQF7fjs5vjdxen54Fu/f3wM
8OYXmYQB4HPt77W6F1jjhg5eDJVOG+f+WWabwSche0EhV0gjK0AioRQP0DC0
pCxiedN0EDEDijoCiVJBzxrAgdzsgPSFEGNYZU+CBIQJVOPqldcs3WWN+Hbc
nFAQM1QxBgif/1gR/4xK5Zh/JtYg5KueWH8Q9mtai8rdWUvMicvGXzx3WJIU
DHcvY5JZFrWI4s7RPx+encDVdHUzbPRv6wydjEjllQAVZ1e0e6I4w+891IQT
kVAbBrN/O7jS38vykGSXPvb54xDfevrs0ME3UTBc6BvJpPQIn6srJB/foSYm
QT7RjJEpdh9aSudEcRRNVwQqmD8Ejxk6Cs+V7i9kNcsHeIe3IQMXGbB5o5V3
LBMmENS8CP160wVQzYzYXnabw1Vrf8Q4KSOEUeDCkRgnLLzz7CsPZq0lqEhU
JXJBIzBk2isV1gOXzoz9ObWRPLCmU/52Hga4WdQv9zNhQUfffKhCSUXDslzO
2ZtO9869oMMZ3Pmw1wVCA2dWtpS6UCWQWS8oUdSSMyXFsxcwC1hssBZVD1NU
VowjXhMJ7Xne58QaKDpb4N3/HisiVPeFTz/iT8p0S1GrYhd/d7uAFiQ4cDdi
FWDZp1P69jP3287+llA7Xo3ZRgFjFCY1NX+FpB9/awSTdIv6JjImO9DzpsIN
wY6zepPlKNtjue7cQRFLkoxTWgvoWTP+MXaY67+jJ/YbBgsNDEzA0cmeoEeO
TlxbbNmbXfWy8n3m2AzqylrIMGcCCIpQpghyxpSLFecEkbCAeULSqpyH8gtN
M9ZCm2kScHsuEGroJkpaCbfMgorYvgwycQ4n/SN8CPfmHbJOA+wAzRWzOPoV
1qvuOmA0VwtFvzBuIsfDWK5yI1LjTI8NJ66YV5Q09c7bLEqGpA0PbQaUh0BB
zqWJkGnbLaqwgBxuQj528V01gFK3Pec8n3hR1Lws04gUz4mQTwy+PCqPVkaY
itFK+AfjKAys6LOMSBV9FpCRuhGzTAW+kVhnj0LQL4oNs1EIaj9e6tnJmx18
g7SSHYTWbiTzPI+iToZeXB1MZkiJY/8TpbkI6mz3DioAC10Ak2WEyhpN12GQ
E023Q4Y7sWSRJy3BnRkL0I+U7EWe4ee//z3+WZaWqTNHVUpJsMmgbfyz4qo8
zVWRf6JtxqFL7ue/X/6Mrwh1kHlFJRdLHcKW/Pz3H+OfPWvkwIxJfJvrqmi2
mz1pmSSmUcZmzCJPLNRKuBJ1dIpf9iQiRnHEKixGWTtsG62gm9yjDqUShkC8
j0kbYCkGkBEQjU2mWB3U+4XBpGRj9dQlgEBj/AGyLXXnkomIHZ21M7REXajA
BIf+FmI+yITp2WxbwctU6Tmx028vzouvyXGOr5s2XDde0fHREF3qgUmtmoYS
TMjqpBXelQRY+2TaC8PZs8VKATwqI5T3hidfrF9cE2U2gvee8tyWKwHZW42q
qG3GEIhvG/2Tk5vB7W3NOnBLReyJW12mldHW5St6/gKkWBAgKjG4GzzNT4q6
hP0JPZjUkZ7D69p1lOfZaJXO7vzrCN1Zs7/H7faufxpOaPDb/O8xtvF8blX3
r/t+e7fT7tR6szDp7bSaOzt7B+29euOg1QTatrdn/JpXsVJMFmZcF3UV3ZW0
PjREkIwW5DZOqsiLSHlel+frudO1Wpi58pRKCm8K4x6iWsrzdMS+rayyvUJU
TI5xyhQfFwQm44yDmRRQp6SfoJ3AfYI2g4o2ax7DtBpJWvGWwsRzgDz38ShJ
gFOPjTsY2ybcRmSncB8h0+/+OWIxR9sbEU9/EHHjJ/3dKh83kukUY5TUo3Pl
zzQMZq5bGpPIZThmf5Vxjiya2XFbge26ISCWft0/f2eFCcFZEB6/9j8fDr4d
kvMMwJ36Ef3CfvyRnOR+rPM/R/xPjP+wj43tP6P+kKdN2/K52eWfdk8a+wOP
9uWNUuwhB0sWJuEn4/DBcitFzTyzxUf8ndZHZaTQHKHQA8h5fXUJzMsnnnW3
rzyFnPl7RvUJG+cO7iFANOwG5md2tdK/b/HmEwg5QMP44DziT/HxlqexofAR
Pq/4CB9veRr2iyNhjHbFSPBYRip9+drgWnmkhvVlEe3Ul9Zz+0vrMc/XYKY7
X3peni893vJsZLVXKs+LK5XHW57BZ3eH6Hl5h9hM6XlCKxDohjfv2KP0tH9+
O6ipmaDzNTpn/OS3Pye3Sk91WXzh/4A+FfLLTx65dGDHf66xJ6bnPYZBSh/u
8AeAEC1MzXEIf7wFXFd3+LJjXrYxWcUkeOS1OC86B9udw+1ua7vbdj2IuB/E
RVjZ0scxvbtklRa7aDU6XQ/uG0yuUnixe+hl6C02Kb042N493N5ruSPSOPyB
RwkDcCSkinCJwx6gbtolk4V3rxE3+zgEOQiRf1Dte9gvFyde+7J//g+yV7Az
P3m+82ebG8F280aUXtca8Ar/cB8/VPahG1FHNBAjBYWErcb2ZHwzmacG29ym
OBYFHYV0OlVjeS7yv/bpkH+QE/2Bz+Onn/wf8EjKS+TRCq3XtJK/1RkTSQCR
KgVx6emBqbW1FoZFaS1d4plya25eBI6dAnAMa4a6Kbqkj6bYgz1dQ5nUZ3pm
lZ+pt16JJjqElDkVxdkUOvE8A/rwFZEFe8tg0Ta/AE3+Yv9eL7rl7u7t7P3k
xIH+VZzKNXOBfbC5A3+rYwy4bt9uNTvN3b8Wjhr2N/CXlLLEsltQH8SXqDwG
xhG93IH2TK8XgqrdoVlNF2XlDrT5TNjVP/nIzHgeG2JZunBM3DQ14wWqvfuU
KsxymFTigH+3WgRxA7jqCaaJoFsZpU9O2kI2R9l85eaIH6YJhQhKfDRGYbzr
vx1U2Yzsw0Khk6Qw1eWWkZV4PFmZCqr0WaIj/0XiIlgisl8gfWURQjeN2YXQ
/Vy0bNT0x7rrDCQ8mXJzNnlEaExbDxw7E+H9Vp5itnpLRFsj12ulkzYBa2+X
gubhHFXdXoaJLuAmyclh1PUH4SaYMSPCMARpJD4xO2gZowOOgAUlLhH39cfL
WlEXYwLLeYkY3aJC9KfWEVw8wi5ikPQF4NRMNvaLx1+i+IN/m0zzBxSKTqL7
KFNBtW+CUXac1P2zeKwCdY1jcmX0rMTPFof6MV43zo8iz/BQP/JY8JBGm4QL
cpw1LmA/xlrbY07XOlgdIM8ez+iR3VDH0hg9Nti3XVzfCjH1xuSlz1b8Hay4
e8JetFaxE4PgrmXgfwnqcsCq5CoRsHkXR7gy/ybMgJbCZE12JQCMm7MtpQxC
9ZXSzUdxQ1zdh2TX4anorkEoQRW0nk80NV5EHnkKJkAdUiQNAFiEdQ9RFpKp
KANhnOhJouMCOSnLXJwTPSs1kJjyCFMrKWXXxFKybUu88z3tT68A1/ZMQsKK
28r7jP5bqjUOtsSse7iIuqdiUWkO5HZQIkx0agZcJYfYw8NDUxCqCbRke/G4
vYzI5aL5y5JF3fkkwJb4j9N0HL8eAfD+W6f1S4j+55rGY/BW3R+eXcDf+HPD
+rF/edK4upEnCHb40+2wf3ENgIV3LsZx4CWL/+r7WP9i3decuoUbEwMAqyND
g/bgsfUexVgwYwrP2Jjv5Maj47lQxIV0fQK+Or0FecvYPtAekeKGeG+wR5dS
p13FouiDOURjpaeLtJeouFXw1iEFH6skksSGAEiZASkoozBbwzzsNNsUC3kT
sp0kGI9XQMEf6y/oJJNeul7Aiv4RUGRyVEM3J7RMkYvwAl0JJwRny4Cix1w1
4kuG9HDEHeoZNmcUTQD3Ue2MLB5t5su6btmr8XabmFqj609g6qE47k2rlmGj
C8GihS/8p314sNvakYSD5pHK0maeWL82GoUvGo2GUuBJgA6RJwTc7+BP4+JC
aXWFmRasw1xiFOCBrbBR5k2iLJC7l8Lk0XGOXNGmK0qfRlwCNj45UeFAZJsh
KiyDNU5OyGpkugKQxpARDjAxTv4u8DIx9sRES24kEkEIrwWcEbn93/5E8XyI
p78jbBODTekhH18G2X8UrqkLAOu6Vzj5QupK2rQJdLnA2xb5nyqQK9OM4kAV
8MzZE2K6lEhkwAuDvTBsxgIuxFar7rObX2eHYiaeGq+79QkRpovo6AeI94Iw
lXjvML5Ik8sI0+pA94UHzq82YhTaAuYUP221vi89abQOoJ3cPn8yVw4CG9NP
SUGqoI790CU/35Pg45ld7potFisP3SU4BlD9/CW7DJsMp/b0tpo7sIIYHe7h
DgzbO6h1cjZOP3fpDj0sbJV1JcPgEdnzAvviDuRGJ9adUJrdW4ALSsRd2vJU
NG6HCvI4tV6DPYrM9xbssyOl4gRrw1r1Nti3/6fbDZdwfyLqbn4fllBgWMCB
oYMEwyIWDAtoMCzjwbASESzWqu9rtchLMWIz3eHMC2VKoDiyZx9S4c3361+p
zLHrXpot8N9cXZ0P+pfAWopeWMkt6ldbdrEiFMMPS5WNkSxPYgd3pIzqsFNr
M6zFoyqafpjC7cvi/xDzi6t5nl0OB28HNzBPUVKreapfn5gnqqBAaJfWZBTW
9xffx75/NmVNlXjJ6iOuW9IHBhNl6BsxwcRBHGRa+3PNZoYLUypzxN7KyqW1
hiNmo69K0qbHPux0ut39Tqu7d7C7s7+/e9DaN7LpAvh1u7XfKDc/oMjRDAXd
BToTjZMU9meJPBQ5TPA++XuYEz7XJgiZ8EPyWdbwGE8k86PKZ159qu1Od2d3
b//gkOG4Qb/DA/n9z+b3+k63024dHuzv6SM/Pb/qoyaMjA/quPmXJw4b5P25
SulK5+o941z9J87Vc8beJOesP1WvGORKiiUVCBcQlSfdBybBwpi0FH0zcuVV
R5KwRK1SKvfaiOJb9nZqiukEUmRnqKdUm5zy6XYcsbZgbLIXOUytHYOLKAJy
/h27w4sjL2agnQb3SYpB+kq/91nm/9tUaVywuVFwoNPNdDWvBo1Oq9llKGi3
6E+T/2nzs2a3260Dj6WvYv/d8LhxdXp6O0CYMOplrWcxTxx1ixxPZsLyle7A
MyevwF401mQCh/GUK6/VXwmXRQ5B31bpV7hYF0SD2On8OOHYJHJ/jikpLxw3
5Z9+BQMDo8rJyQx0UVyHBk0AjDicsWuKyWmLVG0VU+zClAxgHLzMOnedQ/nP
d3eLhcq4QFdceaDOTgO/98YY8kTRnavUJuq0iFYLka7TrVujVDTyoNHuoerE
nhA26sD8ZzhlkikodS9sDUD8r2GKfmwppoNLKdTcX0gWdv4Ek/ZR3MmwKHnh
HYuJ7fFGxnOUrc88pcc1YRpKr90Y9t8CXOmsLHkwA8jqK52yeu7naJ2oyp+K
JgpJbKs9TnQMSIZRH2VfLBL2rNjemMOBAZHSaMQ7lGXJOCIwof2Jcn3F1jQc
mw5rOpQGfg8a5SzbTugua+U817OQPeooWFcCXZxvjNZfMIGjjD0JM8Y0O+QQ
T0arNV86IQcEBZ6hlcTfuoGhdrD92l4IvdXqKcDECiLtb4GMUgostfzpdAyq
rc6XICPjYu4gCXtfNTDhAKmKlcVAOWwVPbx1z566sQjTtMcxQW3J6dBZFub2
SyPM7225/+IiUKmJM2BMzBLj8Bssl2hIFc34/FGHnhX9GzmwhPIk2BE1mkYq
gDfavKo4Fu1LS5KQpX2vSONJPXlORFHJ4dsNlUJIcIrMcE46ylrqf2iY7FZk
GuRf9T6Gj5gp8LPc096wLgXQgVkK139XHvfrLV8W76G1+JQ1HTFQ8Q2qv6yQ
XBlOlcK+MOwSdjeA9jXLEiepfILMAjuKHn70a5Lgt6GMppJN+S4MkHKa+XEk
dOappBaSPrpz0FGpno1S/SkrH15ink0H1+jxO1ZOREUTS/c/pmw7UqO9ztPe
XTIOxDj35vK0Z7ncFRJlveaMcPRdreh1duQ8sMEWJpgZ6zFOEVP14wQ1g8Gu
ZgoK2JaM17fAQcETDTtXOdHrZSjIHQ7Ae0VQgT+yvlguqsSytsh5iJqT9fNw
bioDgSowI4EiqxQWOeEwYNtm407QzZbj0bXn+29UvljyMlZZ/X1kTjAI1vaF
ZMkiSlV9m7pHuW0pHaLKtEhJU3SGYKqcIdg+J29Wjhka0k2jluPr/XC8qyVE
AahEGLBzM9Nnw0sL0zanBLuCIkLScA8u677KTGjFX5tMf56JoUVaouKO86fO
t5hqF3lFiZomu772i2avXkHnAg+IpyG2fImhwXhqGBsjw5QPMFrgk9jN6VDH
Q9KGTurOnCr5kUugSOq5AQCa1NkLkNA2HSBphfaw3wMGqDhXN3tjonJKXzDo
yrgAAQF+nVP6kCRuWFbzRoPzh+i80JhmRHm144WrI6Dx6rIil/lHE5nvA13h
ZP7KDQOraalbf0ubFinQjyMXrPo0s1U0CTjvbZGs2On2gKbQ6b8W0YHQ3vPM
z9iCDs524Nhmi2HhEVlFCs9IHVfRrrH2ha3Hq+iMdUeFF0pjU3istBGFxyzM
FtdjhKjCG4cxdt9ZWfsol6JO21jM+pY5PjFuJ5KzUtHi65vBKZNd/KkaK/mm
z9YkuGJ7o1JuUFiJypDiWpAjznwVpmmoqwFwgT0uqEPJKRSCKAEiiLVuRAVP
tGk+bRSK0HQE8jvb5iWqn8uRTGUsSf98DnK3ZvUKqhgPZSF4W/Gl+La0fc55
tsB8C3oNKr4jvytcBsEo04GUikCp9dD2iVLaFQr0rlHmHByOU9Hb49lJ9ByO
AvfWnkK5Sghljo4wVd88UOnLdbItkcpzFUNjJcPhK48SlGk5SJkE8SGdIJFG
rq4hIQhCLWgrFCTIK9wKTy4gd4YqG4CK8jFLkuRPEnqq4lydtCmqAI5mB/Ui
KoiSlfXzNaagHZwCSXrV/ryjs5sCfFF+0w1/MCfkeug0jmYU3M1IRj9W87U1
RHi/BA6ZhocNMUDuOamaDVpPUqwdkAZxNjcf2jgaW45Mip3W2dgzT7+smCeI
1CRaqPzmhsl9VeGttuUVuGcqbhPMZqW8eLxnKozZBQxbcKKrT6S92E+WwT9W
lK+Fw+GRtGDxKG+5SpfIOmgs4Wi0UJLSojoQA3UpahPzmRBCFM5NaeFhOg9J
5ZmlHFMKfAsR6I0n5609OY78U8g7FRZRMk06Bac8W7yIShOWdHnENMMAGHNb
mjSl+lG6iyKg2lyjvbDYXluxjErCyQF5C0u7BJP4mgmQ4i0YUcygKg/lbJ6M
SKZekQNYj4VMoQlpSBg0pUpVAnqFjIu2XqMErwU4K+o9SPeFm9z28uQB2fdS
ajiOyq+Lr8KlFRYeb21hbJpnfUIZ+NjbaHg+sNpSTTpu77vt6yykAJikYejr
xDAPSv07D2fB3BTPOKKFvG4bse+XZe8v7/68e7zf/iv8u7/bbf31CB8cdvr4
4LB1PPjr0dFR9cdh3PsuWAST4GgYpAk3ewVffQt//gr3G2aey7j8wkFDOcO9
iyOWT3QOkS0PvqM1l4eYpr3rAMu0rW8Cs3iTAPP+STpxG3ScBsd3USgJivzB
PQbsUiAX0fKHu2guyTAoIwUdAKz/E+19xT4jeSldxpeGsm/xxER8JE0gwogL
GuQwBXiTUXWg0dwUjXnhVnaqtvLVLdshYE4j6FwyLVZS75fBQOVY7IVE+q6s
alzpl4f6r0CF6ma3C6ClR18md7E6SHL+zvInp95BvQERYbgT1TkiHxLN5TAl
CvWyRCk+byt4sFgNRfcod5aU3VFpiRa6CMgHZLxynVWCUvS6eiodGOj7XwDF
+0xSXbA3GF/YAKuFy81z2Ees+Ej2YM0hYMlapfHQQEnlDdSu9lB/0YsWwDJs
/7IMZ0foOrm3U282m8WmR07Tjt2yUt8FF5dK945MIPfiJDw3UpLi367XcW9a
HxXo9GVWyuJFotKEOqkmOR0fZvJFAor1sWFTA6yGudIB/e+sQ/TMbQHyNtwV
VGUJ8x47lys7JtNzpmNos8l07j9PVNULrl6DvJKYtALh4S3G8SwvqbgBRe1E
yQinOsEqMSrVuWQd8Q7T2Cn3HrH8sJe+NrwpvprzIwYRZYRw2xgng4JVY5Lk
tp+AiDkcFOobf22T5tM91pdkPVVKk+wxHt9hoVGuDMj6kgVnZcmDaJ4p8WaV
AXxWSSQ2LF4zJMIj3i5Jxa9+3/LMq9drQgR1lMt31wOGXfzJWiVSDwWSdQsn
MX0W26Yk462KVQk8rIKEp8BFCEkJOcdMK/qWR43lWN9Tlk3NmGwpZ6E0kPyu
FlSo3bVs+tlqJArTwNZrhjGq4XTK60LahGIWIwOw3iJ4byl/bWGi5586ak2i
LqLdHGLeCyqaUvewYkqdSCM8/76OqQjqfGfVSd8O767ewiPKOCuFUOqWbrSO
0u8As329u4QX726g678Nvqv7VL4EW0rtEqVUxeIlorWm46xmy5VwjIy3zXEX
siM7alQxodcekvS9ZKO8S7AyiVINjHNKt4mSmbK3SWM5sgUnPSsZ/X2qtcV5
1Ulct/IGfYbMa/qeM4tQwjpiq0LPHlx1XfYn2Ny1B22yhCsPTEOVxi0WciOT
j9E5jAdjtRRrbAjQPR548uTAnOusYmEeLYwV9vZkdAkCttlK71j3Rw9hCbTo
gaU6rrFGJeHEoFFsZ0isICZW1RKMPgaYAXJCD216Yh5gwLl5+1rt0rbaI7sO
SiMP565K0Xqndmd9oRxV1m+6SmkJFmTaiaXUjqtSOEabcjE4OesbqqZ/rbiX
iV5bWOAmi2adODqAZFxKxmg85WJOE5gOCTd3UazznPGdqg0BVu59y/ZPRTRY
zS/1eFtoolOUL1WRRboOjw4AZFy/Rb8AVNln47sQxX3JxkcJel2yVVUaskbl
1OVjuzS0NS/WflhWK5NNP6DuNZ3GebBFs9M93CeLZp8DA2WEOgBKni9rdU/v
WWGwih5xD+Yr2jcxa9UN46kMr5hAxP9iOLxWNleZx157T1tWq0HA05WEcsP0
EkTY22oXP5C5U5CNN13FYyn2i5ne2KOnNoVFyhTa+92D33/fqsA+LqDioKCe
IuChfm0aYvoCbM9FQbZreOmZB5+/wqIyxluFKvUwFHMFppp+JTRcJYpUvkE/
MADu/sTNddfS3B6t8NXeQffAMBNwFd3C/4J66jcX87SSSeGLaWaYVC86VmFF
dhGG3Z1dtwjDfrO9pesgK15bcvKS4UH1wrnOjFtMwM7FSWpFUmvEF/dFbS4l
rlUMYrYLgJkkfFSbpeEsSYGu1VSOVbLokvqKYPataiCz0RO3DQEPVSYDj00G
iFeTScRgV2BbLTqp86RqdocMyF5VIS9T7pm7a4jZDsjhFueGl1oJjr+kZ/t7
2ASUGeCKgxezpiSER7uo59YTqcCTQmWs11SnjToG+NYvWRLz3N+xsTmPNdeN
glrJqiqsjlTpqlXLcarANkmt4nFkyAeetKoBrlXZDS3wYdesbf5Gq1Ipu62p
fe5JG6DJOPn8bpFJTdwoJrsUVePARvwtn472JbIzTWcUrSe5tE26WuJnHJNb
ptMjUts6AqsktiVxj9eZSYiV6FLVPPWNt1H3XmbbKV0KwQPBEvvbIfcdkz/c
NESDnHFNkxhvx47o+suxIlWlyNHZXyun42a1qwA9p1Qb12EkGAHAU68E7pxf
oeUTFdII5rQXjpSdFY4Pz2yV6oxLvPn0q2w2B0xbuVeVqlcoHu4xJnxD6BDg
JHHSGEwuPSNpOfEOp5e9m5DC+9EfP/W/gMs4jPXryyO1Afyijo17buMjfHb0
ZfPoNkqPbponzavmZdNzRkhGMLR/Hax8VApitsx4VjGG26DOn/XMkyN+cgTt
jo6cEa6yYLHy/4ZeORX90vM6tenRz0f081GpkzGGs4Zz/zr5NamaHzyuU6ue
auUPQbgFnu+IHhd7PL4jXx2g0p/1R8BEzOdhRbfqVf34LuX2PdP+SD8sdv5F
0/+SLD7AmlwEcdWh4eM6NepJo6Mvwjh9PKJn0B+X39Y0AzUcDIl1xY7C3WRM
CoVgGT21qvVtAquq41q7nM3QUzi08oIMOv3xNa2dY9WC1oDTpn2pXqq6r94O
rviuohyHRT/gkhcGW8dEK5bEXDba+COLa6JRS7LIHEwmKefJtrVyRlsbiEwv
DLuTblHzFKSKnIXJVhUb7FbLfE0FZYG+it8qMuH8o1FVfS+Kqu+fsWri6H5l
adhdrPcxi/XtxcJELDJaEq5/dZc1/B59B+x7Ybu8yC2VJZEvdKtw1W9/4gLU
hs3CikBc+ZDlNkkrbRRe2tqv0ypSp47LHcKRVKwyg3EwHhWD9rxrNoR7PYyd
ZDsex1ZjMttY1/U2te6kRLZmRnxyhd7mOtmSUrohhRy+Ni6ZPU7i6FmV1OBZ
2/Nu8ZAwgAgtiB6Hl5iS5DSWuM3oqrI4P5q+0Yn7iivVFvAaF9h2/G4VU+DG
x3ELt0PNDUaUuvUXkQPN+ANLXYMxO75yLedTonk76WWVUkTUmAV++omtFDbH
VC+0EcJKQ+JbZRZMLRqus4IeJMmEfIwpTasqQqOy1sDjbejA9lIgN2eggKSt
VnKMCMjMIAa2fzjhnU+RTJaEpkt8kW99EJugCTVB2i6zE7gPCifXbIjowdaN
QLYypVShpCmJKboT8LLC+D5Kk1j0n0X0JmjQjGGr5tdQZo4TiyZJHJc01QIJ
g53DAjqXjlWE3UTGAjStR0UqA7wRCa1tglH+hUiIU3FQgA6DUQ9G/mjkc7Dp
KdQrYOr/FOQDmCT8w3smUs51DylgCMXpiUyEUyDbiH1hMTIi8hnB3woxyP6/
hXsADM/DPGz4bLyDxkWsu716d3M8kGCxButify/goRNiIOpajFGnzEtJ+uic
o+wupa4rFBquQsZVGhVx8cfPq5FRplrCEUqywgpL1rUGWDCe7kPWgNkw8j5O
HubhZEanEtnCv1kOlmaPxniG0G+ejJM5nWoy4pJRBj6VZXO1bORJg/Rs9laQ
WzsDU6lzBmcrezaVpKmI8uPMVIgX8WRbJcRyhlFOuo6SghCPlo+StO98sORi
ilpVUn2QyGzdB9Ecdwo6IEWobSlXoKAqE7CqQlEeaLKMxu85OVaUM0kmZznl
bcgcVpbrbnA3FUq6Zx1x8DN0Qp6yFLVQpUfjr4ou9pSnyyppX6x1b7k/uG6u
235RgW3XrJfBFPJhGjZX56Ewjxv2NqTsesMpu76klF11+CmhR+MEfx6/fnfr
mW4kR5g+M6cvYe9HSfI+2/5lkoTIzfhfAkZARyerJYBb8348NeiPJrcCttuK
v/cR37uJ1LfR0KXdW7IiQusAVhOb0Sxj+Jr7ljdTFL2m8p+xX/dwJ2xzoC+F
IwvTkkAjKYJCpkefKtUidDb5mJUBzlZKqwUrRZ+P2tVktdw8DhesZk+TjFxZ
U32p6MGkhPVnWLMB8wSYa0fuUsZs4VQ1plNYFPcBA6hvTFHXcAE4quS6kD58
CEew9FwKPtCo3IHSoc7nQDlX5EiqLsOLwcWbwY2NcK4OmDvgmWu/Buqa05CZ
4qcqfBo6MONLfAN1orxry0PKRhTcakcYXDOWvO+qAjcnB6RqWGjKVBNDzS2S
eGCBFssoResLLPIVDHAXLGUba2eD4SlGSgMXCSw/wDBns7wJOTUrjPmuedv0
b0NKL5vVtpRyrz+f29NlRyGzPFU8IjGbwyFGMMd5WOc+KH97kmvPfZrGah6k
sh9SJdIk1IzZ24K/1pcf51C0cVVAQMQZAAqKnEDls3E/MQdgnx9X1vDRm6M4
AN0tnKfDgqMxEvU0SRaMIUk624gfiHqzQHkEkc3UeVICTtyfV7C7Uzh2U6p4
az2wWnvLRRwzzpOGQeVUgox3ZZwmmEBGAhQcMoJmI4YOxvfyLJ2Mr0xITAa+
QFBfsB2udrV/yuwQQNsMk/YTis6Se5Aw2UEHI7IRDCiaL+FMqP5EUpIa+Wb9
53AfjvAUZRPktCnPk8q2G70PNwBxYaFlYBb6YzeyABt/FjpK6n1RQ1iYIdtS
CdjPhWkBvYTkP86zqf3lHfgimKTinfCbBkzUh078WZjMQBzhfLCqnk/fV60t
IOThimQycPR/T5A+7qLUN1M/t6dK0ifnKfRPd1QgfW4ByRLx404UBfRrl+GD
PwAYBoBnskesdRhkd8DbbSZ1hZU41E6946853WldEzuGCCp/Ruwh+0rScVN0
L1d9CnJ3x4qk0KpoP+US1sl0Go1NvWSDBE51Oh4IuXwWEIQ2KuBSQKR7McQk
QHe3TQCah/NweYeHwcl/5GbkHjCBGtW/w+K/uK9AUdgi2/TVPY/eyCoOd5lG
92KrDz/AiBGZobX9e6poAzJtTdSrCyNBu8kd28lQqNxtbFJAKjdGBdlsfCNb
Z4wEgg+TAtFwvTATNWljU95kmF9rdecBN5neYwBKeveZ0VgzqOkwZwqWo47U
/rN4YwEpOTSiYiWUMw1y6tlh6szh8vfs8kIr3ZgqiYQcbd9mm6OsXwXM+zoZ
6JnyqLRkVRUM6Vw7OrqTM0F5vjIAC0O6pi91qYzYyQrlO2fuJh7b+B1Y7qWv
tCsvq9ThewEf2DbLgUB75q3rXTZnqy5ibqGdxJwj8SLcjcNVjnr4h+DRVOdd
CZViuV2HbRtZg3aEguZxBXSYD5jTwt7IpijReGNYP1HmLwHZ6v5d8oBJAuok
gwa4zED2QEwq2laEU1jFTFFpWLE/aK8T1PIJu4DwczyPyIafTHNytGTdBNzj
fIdMOI3BCtVTco1ZCZAfmPzlGNCluQaTac3xjbQd8lgQxC0VApFjXTFUTgH/
nhRJKJcgizJ0tefcCTIPXbe8TqoGPxqTLkeiZ+QLTCyGUp2qP0nh+ZyehRc3
Jm90n742hNW4VOMuYiFBYFlwq4SgMilCHRnFhMhl7wpveWLzUi7zVi98rQNf
gV8OkyXnC7c5MTk0nVqAmVKj9J8/0h1LqkCl7qkXZz2+S/D6RTEpRA8cpNyF
lbI5Qig9Hol+DWIHJToCokBDwXWp8jyLUmqVhaxLhVlNgzHTYnKGHAuY8TQo
lIUon3HUM6eBHVLQhZAJmladHZrw2Cw+SabJLi8YpcJKgUxYY8WZcDkaAOfq
T0lozWiyrFuiMh2M0LhdaKYmfo7RglOTVE8cIVF2vFiqjyOrqJwlqv0ApfG3
KRUN1um7ebG8h1IHlHwdSe2FWqkxs0za0wcx59+ZjiSUkz8tKBv+He8qDr1k
2FdCuEIYkjJUgBmcSvr+32kjSA8XjBAnCcFndM8m/6502qPwMRFEz8bJUrvk
e37hOiSpMXvQNZPVWFld3QUi+ZDUk9kXA4rHiiapw6zQoSGhKWrQOIOIrfyi
VlrvbN9o21pjsi2S4bYFKraCbYOvmlFek5LGaJsINIndInb+S0Aj/yQJydmc
My4Ii5e+D3MuUG9EKwkaBOC48/sLLGSOTglK0MI6q2+OubzEGlsVP/l6cHN7
dnXZ22mqXKm4Gz2zCfL09LKn5idPrm7e9mAMKSxxVJiJqkJxdKFnz58V1PbF
LWF2QS9T8d7sIwWIyhcYQCkM7em+P26RcKBmdbhdxbl+miWiavLbi/OiHUL4
ZJ3XHJroQFvmFVQqrACFO6LfSpP3EUrKzTbBpIrHU/1i+dE2bd1vv33TPW7e
DI4bHxbzBmbIbLc76ACvyjWzFEfh2VQPRLGElj+6X5nzE/pD6q6doZGU2mEw
hoPCVMlmgFe1VRr3ojCf9giZsx701IuzHrtfwInXkCt/xfpRCWvxtUurSuaz
YqtKaCd0ctwvHptbTExlpUiMqhJyoPYA60wDD5MZ8xGf4s9/oUn99WddlZ1Z
5JKZhIu6amPqNA1mjA2ZXZ09RuvG3C25gtum0r3BzdgMmzgG4BeHroAcPDJ1
GFmywdqJZPaInXa6LCM57/tUJ0eaUcHxeUIauTjk+/FWJAu+egqQZBJBkYqh
cP+tux7o+IkwpPdWeGUZVpEPZPvWMpgxwy3uszQz7YjO22pi+GwDkVTt0CKm
FUrmGU1lxRWDaLvuhrFsMdhMXTFks9eZmcWyKou2vXqGHPuty6oqAyEcL9ZP
ceZfzHSJHFLkdk36i2AhCkR2RCAFRsW3mtIg8TotuhXZSoNCKSjX11dYFZbG
piJXfWL7S7uathVA0KnNkoULzC5kYhq/be52kL4dsyvuJXmPaVr022/Hx2fD
YfNbaNRsHx4c6BgVE4ctKS592zPbrJCXXAE9p5frgMcx1BWS+K0x820yC2pm
5/SyAg6r7OtwJ16kTR+j3f2vmv41mRPgKhxk/2iai+1SWdvjoqHdBhLj4K12
XECiABDqinsOSLDvxipVkKeyAFKJHlOEVaWFRaHcDR1+2pInl6Q1UsF53UA7
yiFIhJQrf13B/ilgHPAtl+R4+ooEHM3DiLdutlX336LZHr6ndnVbLyVPvkhQ
ykF9zTUcbPQhlPK5+jkR4Sm9UcmJGSH11pMRwY6pxvnpvK6eb2VvVTleKQhX
x+8VOxxTmCTxMfb2Wslcy+Nx/rrCSJSl1v8orPUdVjV2MDd7DuqKXmek9C25
8fWwkdeE+FSDrlbIWcyscvU0k10AezfXF7s4em/MiOVcdRUUZC0BcYMhijTE
M0TDzphgUwpDKAo1jndeYeCa+7AYI1Gsy3DZYwLC2TO+WkUxzOcICMwR0ROn
5W2OeTkz4Kyp8fVdNI+W9etgNT86gQ++TJv1i+ZJs95vHjevbVokMd4bCNGG
Oyoav7dOFib0gnvqKg61/8xa6A+KsA9jWDmaNzPsQor0LLWpHxMELsm5k56z
+4/jQUrKH8eJLRelANZnj2fWJmwEZ/HyoeRQVsYRy7Qe+FOkdlHACU+V8ouh
V2Ji7Eg8oo+XOMFLS7NZBeRysh9xWdpCehW8P+PK1KPbF2fDJBBaD/TyIYbQ
jKLQq3r1ZbSow/+L6tdHFF2KCgFOlqNhnbIYrAF0pMqYLwU3ltKzkJWw7FGP
ulGqZRCyKgKupCUe/xra9pxLmUKvK0C5eKA0/TW+Te75mKN1TrLKnck5vmUl
TeNxn3ZzkiQ0vTVFDJer0TbtbLb9yz/Y0aI5i6ae9eWaDDcXZ2fHwS/Hx/3J
1az/cPamPzs7fjN493Dy1Xdf/i35/uzuXmx+Xw0Gb77qP0x+HZxf9N+/7bff
Dd7cXRx//fXFh/OT/j/ezC6/ftNPhmet3fnki8tfvvv2zfxscHk/+qbdHslW
zeHpzXLU2f0V34zjN/fjxWkr+OZwdXHz8PB29t3J1199dT74cPnlaPE9vGvf
Td7O70fRm2H47aVoSv7SbDZTdMtB0wtCBq9DaypwmdDkrwYy35z0v9tAgUcR
KlE4jPcZd2gR0oaWf5OtoygVW9bZ+HPxtlNECzvOVbWWZzl3lXzJYYUads0v
DanobD0hDpt+VyBXmuc2s+HoE8sLpfwSbioQys4LcyuOpTGnnPS2MIkyySxQ
SWdRRRwshPTaCIXzLrwm91LU1RmWipknayNIqj4q7wYZcYHXtv0Usqqw7+YT
pBfH6mHpptZOe7f4nEpqlZ62D3e77VZ7d9jptgsFovD9kdm/3jhKx4Hfdoph
9S8vz1DR2L/5TslEQF65Nkn66EpHd6HGgEWQplEgBWLR5eIeo9Pz+kcJR/8T
sMPaB40kpWcKV8ovCBvsx58Ec9ZMYAMCVc/saTyqWP6/CJ3Km/QvxyprSINc
GgPeDi5PsMbYC9QAWfiBo6ZDul9YY0V1if+AssiS13lfdCI7J9AcFQVkC1Ry
zV2QPR/sq7XpRjTWMkadc3cX1AKwcGT/R1Ei2WGlCmZhI8r6DMxSuWTVgKg3
P5i3Pd+quUOVrzBjmpXRwq8tALJqdf9UHvLh0ptpKO+unA/ICApPL52nlLEI
yygl4uckgQkj6uGd01bcDtiv4G3hpO25n6Zh2CDJAXe/Qg5gCHvaoiftFOlA
KPsBZVZs+ZPn4e/wNVnzLujvU/r7iv6+pL/f1dbgAvfduzA/nlpPj4aYhllO
8YJIq2rFr2CXMYgpNC+ujs7IoEkQIc+O+tyFxVad3Qy/uD7vH28Sb1l9j1wa
cVkfw2BVqFz9V3KnbHHePsPrvxRByoknq7NIO6YfRfRWMRV6YLqgHX50BXOC
gqrIP71xhmcrPGLSvl1+jgE91kNb/oPmKD48j2+rHO+pq6RqNr4rLZW7Lt82
Biuq4dn00HsTgJSafXbz2bvM/yLJllFOSjXT4kgPrSQjWyq6k0+y7RF1lK4y
CtBY08MsTHo7e839vcNua7/e2G83Owfw06FVPXbQfwHMT8Lg/4d5hnmzcRrm
i48UzJeeI8xbDz8W5qvHewrmq2ZTgvny6l4K86aHXn+UUIQZJggA4I3JxhFj
RtTL8GGarOLJnH2GzDebsSC7i5bZds59CfxXfkvw327ud9uHOzv1xs5h83Bn
96DbLcA/lkbeAP5Kjvh46P/vEBqqEMV2dwzM2u0EY5wlwiSPRIOLGMRVLSjO
e6V8x9lAD3sjScHs0hUF2y75nVFlMawWxO4M5JgeqFJ/7A+mtff/bYhNlbMd
vDZPlGBVfEyiknn4SYSqyqE3iFRVc3paoCot+V8kThU3518mTOmBbP2EeaiV
E3a7kmZCv9yslvBPwjmqIB7RophKjbFNPgZUVS+NdcFMJzRX50hl0wP37AWm
Z1j+PBiFc+0tWzB/k57k5EbrRybpy6zGasxiuINWjeiRXmAzrpeMlChW6XKX
FUbR53pX2cPpWm3sr5jlEtxm5X7zfL2uQkY0ay+cgm9OAWUV7B+lxYxrkkNI
uqqcFQnCjjHbkVlZxiN2izM9c6hK8uHIvNGebGoRkl4zsOLBgFxj9WOOL9my
PoZJhXCHyKfWC/S2tJN1juFn+0MMvwDglLdEusnugU7lMHm7KU4dTggV19ZT
KgWSSpW2V9MV+j6RhY2tvbpkY2Gjfd+vIvbGWTgonhkS+EVEiMJh5pbfjW5K
LgQEjYlQ2yzHKEL7pGmMAQXVEOQQpjL8d0mJkd3R3afc/qdRiln7HP0HKh8K
R8nOY4VD3CKqADz2bKVoAib783wrtmYU0QHB0qR8a+KHcYYeSlSAHba82Lau
IVWg2Rjhw8WS7Nwf48JQNq2yCwNXZo1yueKVIwGH19TtDMVy+VX7OFR7OCgo
92sMwzVHp8Q7posvob/c1pNOEa5huOCvYE8Iv6U6V3beS7eWm/gkSYG2EgGl
q8/NhKBe2S55AnQ4EYz0o0o3Vj6vTDkumHS8Rb+FilUQ+6iWEmBh0jeD88JK
dJyD55cn7941a9KBifdsQ45Wop2coF7Xj830Q/6eqrguVujNdFiKnaOybiVp
UvcWXJmCFvo7q54vhQMEqbLfb67YWyroCou2q7nCphUKXHhwx65Tktmfb7CV
b/tuojfgC391fl1jRXe6cAyyazJP0FwVO4o/a9xpLBOkSqi3c58j8sFTxx7s
tpDbpPypvk02fy+XSvl7Kn+0+Vu5T7yqtfh+yZvGK6/Nf0Y7WeGT7fSCn2gn
K36yP9qAZ8xP3arldo7DoS7x4OQ5r7qYbA5DsZyEQpJkWXHXMI0jSkmI4nW7
0+zu7O7X9w+ah+1W7UiQpezXyG6NP9LFfoE5KE6AUAETdznwv3rzY9zudPFx
7N/Stv8Y9+NHuOYeYizr4PuH7cNOuwGNdrgHzLjQb9Z6R0eFD4/Ud0fH/SPz
1RF/YBJyJ4vFKtZpfsr8ulMDgimIX65WL5FEY91baDKxb7arIJ+OwcLCp+fh
fBOfXoobJoosDx+t8TmkWvsYv8C2wzWXUUWh65Yonn7qGA2U9o7pNDq7c3U3
hyTbDNOWjns3PIjRZ0AfRuWnApwwnnmc26UkTO55zvkwIhGegvmcS9TOhLS3
h0nRcWw7575zkz5T0NjkNMluh0N9Qpd0Qnj7bHRv/mNcR2DzHA10pS+CyNMD
mJ6p0kXN9jNTXvoeR34rBqA0iA6jVREWJvicFX5Yb8K3E5GlISXl+acoP/4J
8rM42MF+/hPfNPiP+ld+o28I/v5JDrOumqqMIRLXl/E3kpEReMnbi1tgWLm7
+wTpn91fIM/KC+UvpsGHQvtpMM6iBRViWfPNGKtNuh/hI0riQi6No01fY+Bu
UpwjPQMp18rktebzZYDFoNzP4RnF4Ib3m5aK+8bP3a+xvUNwVEd45hJAS+h/
FwapqCwArEIMno/wxkFWHaWYfyoIVapRVYa8RmcgqRBFd1JMmZ+ZzHkG9wNe
nWpI2WxEePiZ3PxwTezwR0P8zKaHzMrEWP1NXZo33QnrKWB+lTSaTEIJuRR6
Y9Wrzyh3tCkAlRh/Vs9kENWO84U47NwalAp2YCg575KZhKUj/vrq7HhAl/pp
/9sybqgi0nrF8PXPZlvqAOXNnynFQSEQyE1djzRZJzF0PFanktgRbdQK+bRQ
TomDTEW2aLFcbm1VeIsz7ZmUXWs3u2vDrao5c/yZXEkVV4wPVmkknDH+phhj
3VSlIlZNlfLmGerawnCuZOAVRpDoEM+ZUslVs+CD6TmzEgdLe8kFKeClWewc
ucGtXaRLzKPtXmAPy7QHH+hfJGn8ComTy75TxzUiRdREk5Z1FShwtwuj2yp+
IwNbJZitMoywH65q2BTuHJwb+9AR1a9uWwShjmWbejBc78/txu7urvp/9whm
/Bp/KPVBH5vPut1Gq93odBs7u429fStdLSXlWs/hUUA/1sEb+3aGNiKqn4K9
+yMhrNUcBFlRyjyK51tcSoFHcZLPVSlGKhQig3sKCqGEHo4lx3Cl74anjQNa
mGJdTX4azq1qhY9SmAAJIO8yLFA9Q93Hq4t3/S2JzK/h/Kg2iWIuS9Gju91O
x623s9NsU4odyj2rypQqkhgAg0y3BKvYx6uUkjpQKTepjUwzVBVSol+xTp+b
qM/D0GAaurs7ijJiIEtZYBHG1mkl1lKCte7f6wy+PMzzQtx8BnzLyV55c//H
h8dfbY9vr/AF42bvlyAO/+8kCf/Dbqqxiq6S38w9skmGwttqSpEahVuJKbqY
Rj07i6srJP4htFvntr8R3zBT0hMigY1uwgxzmkoL9zTG4ULvApO/n1ThKuRL
npfGoMBqO69V84WcgcUUMHft6ey0dFcwV+BkzrKqe4dzYA6M4Cgcgedv5Akq
At2CSbBE/KfEtFyJbGd/v4VozKmF0HYQYM7lEZa7h+2knMBOdcwKnEMIfGkG
2WqMq0wfuwYFadR1MRYWAmI7hUkfAD96AHrjNbiExvYN6KP0mK+yLV/XrrWP
VnIDcZIGutKejn2uxhWtMs2D2YarqngUuIDiUdhdrT8TbwPdW6NUpcHUCZyr
UYbBbN1R4AeGDKpDkdomVS87vWlaeElsxlS7LPpv7fSEG3VYTxieC2fkuXkP
xbhJqSRZi5lVnqrlSL9O4/X9GgjbYAU3BUs+Jm5wneuNE9DsBt25opTllgbL
X+XjRjKd4tvn81BVOi2KSmZiRLoYuhMbk2TBaUiu5pjFCkN/UNcE9Gr4fePk
ze+/a+UXop1K4sMEn/KK8tzzNBqLORpzM9C6fvsNE+w1ht+L7mkwnZJ6hCCD
ORJy2eDsXClPFSm4yrBm5e1gFzVRx005/6ByUKisLwMTeUcFt6iU15hLHyh1
HvFKYs7EiqHA6M3De2D5KeV/wQQq2Vi9Ygo7UQWp9HsRp+i7TNS1WDw4bRC1
RQpVIp7YheExsWzySarL+NECGw3a719WWa6/EvaOUtTB0T3OMeEWrjO41xuT
3UXTXBXNGcO+czn5R4VXoq6kjHBIP1OGxpkwIHD2tTRsIEzUxLyLqgfMJsIz
VT5Y5D0jz6AHodV/3m74bR+Y09R/RcoaTvKJmdzyHIAcmfEt5sZzCWClaNcq
Kfv7Iqmt+a+MfChXYM1se20Lvyn7OsLfptEzxezvjbT7zFDTyit3c8L2atei
4fc9SU+0fRk+/N/vsGoxPVYioV5Lr9HabXGM3xEBYs8GQkYNxFsEwJsB2qfR
Mf3EirZGO/BvulbUOt52A+ksV7j6Y2EfL2Fi0TpUs9X2IjodIM/ls3FXUlkD
3XkIKYUu+a5Myiluntbil+MY1gW/fgIYWcOV4ZjPYMrwDzQl79TufrN7sNdq
d+uNdqfTbB10Drsdfb9fWXmKP/ENv6b0vJOzGfPzuTMAaUi7inkagoLNVi4s
8K7tXBHQmU1SmoJVHPyXZPSpnM0/nZ0HF2BMOySWVxl3SvQSd2G9x0Ah+UyV
sb9k7n8Wn8rjPldYp9a9G9jWIIVb+naM6RR1FD6e5s3V+SZfaZWbkRzEsG61
5AHlHGsa4xHVI7iiqKloo/9LlFlPH/AblTf9GJBllqQoBGJutYCy+z8+I2mR
O4anCoyJfSIu4pSqKR6AbExlg6YrncldeWAX87IwTulRKF2vKoMrpU2pJaUg
cLJ4sezv9lfYFGX7q4BiPP2XA/EGWetZdJVGfS4IY+MeUEoCpnNSyFky7tXb
tSkdfJF4VGaHKaUwnyWVib9eJIO8OHcDTnPN7fXHd/n59xlN4+lMDthsUxoH
3MRsOxiNAUCXzV+WM0999NEZHDAV0ydI4PDH0zdg8gb2kX1JAoerm02algJ9
0HWP+fJ1qnM8U6FS6ZStvKQlW53juPocB9CXO2s/QXltbodycrGe0H3+LsaS
dS9JP6VNuyz+F1yz3U0osUBUFtfzJc8U78evIJHqXEQkqWZcy67EKrGU/0mT
UQHorCPAz0xHtTmL3dOZYWwKgbNRBMJ45H5O2avWJK5CsCzleLPPoHxD8iFU
7e+f2lK4GOGkskGHGhSKer8466zGXEkSL9wsF1Qo1b/T/rZScEHVjaMCJ1Z1
+ufdGLaWCuGlFBI2LcR0Y4S6/o4+0WV5rAI3xloaOJEdR54vKh1TeIVtURMq
wgBoh4hBfhKc8D2EdomK6qhh07wo+aG2fa+1dyC5QUN0A0HP+kcq52BoErH1
7NRCviaygTw/QD0kgO/OTvi8VS5uYWuI14GXxMJQUmOp8qkc1pziy6tosrWl
StFw7mNZOOUETtJoFsWs+IpUBZNus/URbOb62DTLnqnFcjdxPzrDWBUD+gr+
+CNOsSspSCnzulUTjKsuIKhQtQRUnbD3NHxDDT6jrWyWeuVCJriR6kjcgo5U
NoRr0wg/+UjCp8mswhl3xe2a+F9334/wiREG6uqcnGlw/KOGBg2lnP9Yzjlw
JYAiseQONb2UX42zxbZ6ZJw21DeKqlnfKMcQ+5sXOIeURn/K1aM0t6JDiVea
HLNppQlqXxN3Q559DzwZ4O7kA3dzgVMecFUM7PSyhxchpmCnPHYImjynHiaZ
XgF09FrdoBXutqeNSTsIGjvdg93GQbDbbYSdw1ZnNxhPDoJpxWejg/29/YP9
/cZoJ2g3dsb7rcZhMB43dlu7k+5B+xC6PPTszOGbp43Z2NF/mbOxA7i9eIIv
GcnkfXdGevGaXngWp6v4/WOZrpvdZWLey1Yjxua07dgOdTuyLZpWnepWWWQ3
6lY3EuebnfaBdr7xKhO+3wzO+8PBunKUUsAY9eZ30VIXcVMkUtkm2e0dRXx+
oK9kxfqqy3qjTFdK21gdrq04UTt5rCZ2VdkescWKgruMJeW5zDa5CZY4TZ3g
Wqv/flUhTEp3rNPiuAVn8Y4MGkYwIAbAeDeqdIfpmsJO9pWgLgTVEHaoIfna
M3GxFKtHhgEOXMCosUyWq3nBjMxjO/45H6ax1sOg744qCEVHo1yLMorVC4ql
qcgzOZhxqhxTFxuuHLKgEPcUoe4ZSxSh5iq8C4DNcHJ9M5O5yegNwAas5gzZ
n57x3uBaQeqFsqZXqGAY7PWN4PxOyRy2C88I9NQj656wI9GvjYN2rHI6ObdX
eZinrq/yJJ6ORC8s7o8JKiVpxXZoVND+WsE9FeqW7QEBpl6reLFVdExUvbzA
OZG6kHXCvlaMDrskp08mtGD8jxXgIKXmZ49LDEqd0I8LDoYs/UF/zKSBvgTi
cTkG+TXECFP5DWaeEVu37vM4jGZ3o0S+vovmPCAse8NHWTTCUnnUMlsmq4yH
ex/FPFt8sG666Sq7o1YY3c89AMXO0Yk8l7Wu+5Ywltpo/KlOLSXbzs4UvI3m
sp0etCc70yBs7E/CcaPdnrQawf7ebqPVClrjw3a4N5ruuT3IKVWlKNH1lqms
MuUoKXwqp2MnF7iGI8pCXbNyQb4zEXurIYvgMeNEtQzR7ofVIymbr7IXDSw9
9UuNRRYxVOpuNkhL0SKPJAfLwGhdSurqYQcRlp5NZT5VFNQueHAMW/H26uZs
cLvu/jZV2P2xaOIrArByk5mg7rup32t5MMtq/zV5pItE2izvZe6YZQB/porc
GtDm+MsplAvacvNdb3jT/3pw7vffDi6HXlWDs8vh4OZyMKxjQeQ6sJJA9G6+
gx9Or24u+lh/xB8Ojr+4vDq/evudlTP8am12HfTWEB8Oh8nhhFDIceDNzWIu
XuYvdyX7I97O1VpKK1zJezrGq5Rm+2r432BAoVGfa0DBxj1SYWCwk0SMUE5E
LPLJ2N46aLUQrdv7TpLXwe3wx7p/kcSN0zSyHBmub65OzjYVjtdKjFRHjsEx
TFbKvExOSOHERneTiGRoUmz8gXryxWqe4h5ExQZ91JolE12/TZhdE3iEkz7l
YkEc7aqLzqA7OPGlZ7dXhy3yfUhSiY95J7lr5/5NmCWrdBxKEQv6AHVm3Z0W
1n7KdboHK97NyBOkCaMycxUQx3u/DuasvN3c7rlQws17je3tq8vzs8uBf3J2
MzgeXt18t719eXV5+/bi3P8aFofY3N7eHlzagtvXSoEKl8U6ZwB1j1QTfe1E
/wT6I7eew/xfmimLt8EqwRlmzrB6dton0Z5mFNtqXl3nEL6KJ8qVkmUGV7Ir
8/pflw5Orcg9PWypj0412WgmHXyNyZF2261ue9jpdPbbre/NEd1evbtcL1lP
ohkmIQR5aBVPdIGzlya/55Or8NRm7zdko1EnWnAP4UIH8E+8iqVsuVPwpmBa
0HrVp4X459zrtC+fzjL7ItNs4UNz9jypJx2PqFnvGJD2y6svLr+6fvfm/Oy4
iWrYgyalyep0DodI2Fut5ofHXzFE5j8K8RncBVltg9UkSrbhfozGzzbb/u82
2qLK+TetxF5HtgJbN28VqgnEGW/+KKTa6NXx1qssmPLRDvQvshohgnAu4GfR
xgKyKoUSLwpW5xgL+I72/A1OYqwLq6EIhkajS6vyoNHrkJsVug/utDHyqtJ9
UDkPKiNqHmTvbb9B22nZ9R4spkV2Nkz8C2GaD4l9YiI3NBpS25ho0MIPIxrM
MqAQM6v1m8oYpQ0ibOLa2sKeWCxboJDN14a2qaABJNN2aIoPxpRTHDpjlZik
uWimYIIanQXuYY/FRjlrlZVNuY4bO5QGMJ2Ux9baeVZZdpNBB/EouQ8nRzyG
gT4VjWe6B3oy5gqVwEU9pFGeU434M0C/JL+zq9HrTjhqiV7jc3gWkQN6Jhmu
SsantVYpqm2uk0McYHIIpGkSw7cH87jCs3uIMom4Rh2hNaWKMSJk4/QFmAl8
jIN53fKToOAY9VvFLf/OYs/wZ9s+hb9bxql3FoemmiqzlG76ApuUO5ybBNbt
XyKN3fkUDVLuFLTVyVrgOltSgTtxrCDPUsxoMn18DtfC8Prs5KJ/XaDR6Muu
CTEVkBdiG3AOPB++8oURN5j+ibxqXpwCkQuTUmI5Jzd94GcLdPhHN71ZyABY
cXlk4TiJrbR37NCGKzSwoCp+ap176SMVzdd8DpV2aLTnfyyV/ug8LZXHl/mv
aDuKz4UwmUXDw7k4qlbvEifqczZfi4KU75TKjFP9cqwIqvIGiveHLtStTULK
kdk6BapEoIqaV8zZKn2p7OGIz9AJjR04ft42JkgkEFLv7DEe32GkOXvKbJlq
rXBdANOX0XIklEU8IZ2u8DJcs9U6ZSZFIMGWsDv3Pa7te3Sb4jglpP/sT8Vu
DQTUcpjhh3FI2hWmwe5R2Hp24zTlqXRx692m7AVo2mWpz+zXini1Pz85e3s2
pBxla7lqTAYA373uNtv1nWbHSj5dkUXA08HN8MUOfLHb7PR+KUY3+85299pH
mhJ2J9OdVne609g97Ow0dkaj/caotb/f6I73gSwehqPuzqj4ecd8Pjk4HB+O
94NGJ2yPGjsH3U7joDMBuhoeHnYmh7vTILBqjby7WZevIEBuj7ilVOktqGI7
5VLZ5CubSKitzQhOAW4Q8kVTLyHaKl2k5T6N4UoZaZ8ewhG6j2N9ztE8mUmZ
ThoYqyrnqro7tnHY7KqCpOuoO5q41vmVwNb8lweX4JjPDC6BpkWbRJLOtjEw
MFilQZw3p+hTc7f9n0Bofx3DkTTv8sXcHL14DShx5571OJvCNqSJmyPcLTYt
kgJ7WS1UpPpHq2+fFE4ULdpQLphyRKInWe4vMJIPSAqmpY8WfCwozgRTpDuW
U4UILMZECn1gMjKsg46Fyc0YVrZffd05W9LkAEUlHsHQc5IseC9JR8Q9CbEs
uOpz5nUqzjChhTw+cBbWioVS6av7UKVr1xn9ipAtJ/+0ulA11CZLXP8moLQ9
UZS9CnhvwJv85cYqYXD4Y2azrAwpyyC/ewgeyRwVjMfkaZc4YjMC+d8GuorY
+/BxvTzPobk+tKH+VtAP8fhsmsI50nmGa+wTz4iS+jjHkidMG8WTheXqU8Wf
bSkDf7ekDPxVnatqqqQM3fQFUoY73FN+A+6IIne4MyzKHe6ktNxhLfmPBYo+
wwUOxloXAwGQk7EZGKDF47ZHF4OTsz6Zgi1L5/ZyRsCY9aYli7LuRXoQNVzF
x5v1cbgsJ5Ti8iUqOaU+e1J35tvKM/8YxeYJkNYnEX26SjnKs5zQsbPfPSSj
GmLv6Zv1/EluZXvBn0er7JHDr58I5fkIFH2BcZFzZOtM1bSC4vL1susyN5W7
wGktYVrsOGTRGswbYZBQS3Wnw2uxJ7X3uwdsgfpiqB929tpkZHpk+QQXtUwi
FFkpl50fqdPTWrjd3Z1d7Ib3rbipwMvHwTK7S7SqP0ZSNQ0fgHML35N8gRJH
nN/RHWeOh5SuklsmNOOqgcgGbHvoUb6/KWZPRL9t8fSqk5c4PaVstsSXSEYm
Su5Qa0bTUVXpD9rjT8LYvYy143GfDrSidipzyBpig5u5jUmTJuROyp8YYoOE
cXss+1pBZejzJUfPNQLcKEuz0j/vn9wQOV5fUEId2QqTa6m8Qw7UaClA5YCY
rOacL/wfK+BQTWMESn1uPvFwCqO1Xrnkr/l81fhHoKzegfVoK+YmhbalLzah
rmclSq2SYVVfnwhEXwqmZvwn5RDdVEGrOBILYBbFXdW6ypNKQRTffTYwboZE
dQEEBiY3Uv//ckjaCEYF6u82fyH5118JMolTr2jqidQrPahF7B2kNdv0NLFH
zP8sM7ue5UkaYlTSerL+TKKOouMaso5EfZxVEXXeuk+FMi/El03IktnYYqGK
4ADsX7OAB33TdjNFh79L3+L+WI6CUoPk2gJAYOC1GzCzZw582vy98blWTvLa
z1rS0apE8iTjxg2VOqgOXUb3mKxufdcMVx6Z8+G7lKCTHta+bdRULhs9gQg9
ElOyrCov//wh8caJOCxh6qIZaeCxD/Qfgf/R+VV5mGuXMzVJ0Ywip+nfutpS
kBgL+lMQHCXeiuLGyHchDkOW+fHe0s0pwRBPkDMmUyENdhXxyIiECSwL3bMZ
j5cqGfpQ9zyfR5S4Ev1dVewqLFrjUeB4mVDMlvhLCXcLYrhSrGXQy/guiKNs
gZP2gshoGlB4Jo7bv9BtADQeEvsbqhFwDxQea9P2mPqenVSaiUkk9DQZVKpv
d6bizglcwjysUAJLd57qzn+iO0stzGEX6QLDFDkgrqZnRwQa+wwDTKQzTmZw
BjpkDnfXdB+wmmUa2BfHhj1H5zDPRFQ6FgDl3wjELNAxE+gvg+mXoGdYHHmE
4Qyk9p6aBwbvkX6KzJ1kAgjvk/k99KKsTfPHOr+lIkcGQIpzrKtYGKCCCdUV
IiyjbRKnWK8ImmEMsBeKQHahIgx5jmdqjl5x0nQrGz2wBSlIC165EZq4055l
eFVKPZkXKo4tEzlKL8rsnrkGcK8qAEWPA2s4QyXLXKxQYxBos7pfnLkYpNSm
iLg4iaDbkDRP6uyftVHXCj/0XgF1UXDZUFDb0MOjisoUalSfjMJ5Es/kAl/F
am409cwxmKg9q+yGwyq5QhdnPydLRR0NHHU/zMfNLZVkDlkTgpyP6Rz6sM0T
hElARyZzB2Y9BMaq7qW+WmF/qWXBQxLghiJ7yRpLITUFOxZgMcigM9/ZMQu3
nt5td6/rhWWqbWLM4ndUrWuFJRI1v4hN2/USYP8rRnfIaMYdlEcmS6FH6AFs
jYJHNhOKhRDtg9iZerkGfZblFVRikGcwyH8OBuHQGot+c6b5O19O14YKuNSG
7elk6i05dWja6GnayG4Bissv9FwqcFX8hLbeGd+zbc0Z8954lg5KWNSQz83+
yEPXl+LMXwVZlcJMnFyMi8sW6ZGrLgHxiVArLUCKWQMcGAapcN3WZRClcmCm
zlzFLtqdVwB6FegUJvCHCa9TTUGfoV/bbbZrdWUxYeCQZAOAag+MPLq5B807
prkci9P+6a19OmIaA4KbEg5sm4s7dZjti8zFYTjt7u+Ejf32/mFjp3241wgO
2zuNzn5392DcDfd2O/sbzMU7ndF4shvsN9p7h/D5Lnx5sD/aabR298LJdO8g
PBxjHp5nRx9Xr2tXmcGTu/iZ62qN93fHe53Dxl5wMGnsTHbDRtDanzbaoxEs
bGfvYHdnsmFdz9yWUsixslGLAoLyogLoEVPJfnlsdMY2pkqyePBIAAP6sHNO
TZEBngURjjvUznQUHhzutxut0bjb2OnsjBuH485eo7sHc2+H0+neqE27Tdvb
BpDRu37Zg3+PvmweHR05Z9B+GVztdkPYv8lho9vdDxs7+539xsFBq9sI2gAS
7Z2wtbu7V95Ass7G4YPZGoxum8Uc1oFr9GovWmRN6WlUilpPtpSZhNNLwl5a
ZVHR4oxsyLannMbxRmZ+OLLymvO5CT6LwEacsehEKFlI7rGo+qLdqkkScs/y
GLZX5uuVfRPyAoAOYxA9m4HTUGWtpazu9hWUYYlWVzDCKjwhRTHYNw3mlo3D
e6wOE3ouu3VpbnLMHh/zLajS3rKPJ1wRIy6Aw2lavCpWBzdW7vCzOMpRP3Z7
R0WCBDw0aNiyUKAord6Ed0sKsqBwAnX5IvyYdKEWfZbqROT9SRK+rhqlEuVr
oPReRc0QWF/NRm8JFKyyyuvFks4CQXwQ5JePqg7zZKLKC8gy0bdMpaXy+jSw
U5gHOVZDKcydxGugZdnG/Sjz7I0qLVpFV0TIScil6TQAeBuHANXPS+Xx30SG
lIsVvH7SverTkqw1cOZvgjOGnMyckhcha0nbPHH8EETwx9QEcOYTRi7Slk7Y
8E+nTRow1A+hW7iahIW4wvmQrzLLfFhYGsgAVdKZEJOWierj9LJICLV8b2W+
LvBepFbQMp/DzYCoQOTFmtKjIZeKHtWRYqyWGNft5VQemHxWZE5rpxSs8gTD
icai2tMTBF5TiItXlKM+yYwqb4z//o1yCmQIC+pcpyibq2mSMl83Y6DyFKfK
K4iTUnfcTnq0C4VIErWhUg/V/VLWUKB7kSqv4U5NOSRbk5AlVYk91FlZI6Cc
ptdw+IQvrAHINF7Z8n9uTD6yyoQ/m2LLB7rWJJxCUfUHZVvArG3JhtHr5pbA
W6ZaMS53wm2E2sogDhNoPcBoQLz8+CpwyyNxHq7SFUG3/2RSpCXAiFpxKEQO
RMmsNXuxdFdaxD1Ka3fo/BajSvELVIQGaWh6ly2V8BRV6pRmwIOi6PY/+Qox
DTrQYJRk2R+4Y1TbTlXbvb099f/ep7yP/ufva6c3DpNPsq0VXtSfdlvXSYbt
6f5eZ9IZNVrd8U5jJzjoNg4D+Hx/F/Zs9yDYC8OwzCVcreHUmHJWesr7r9pb
bPfU5RIVzeTbh8q/D+xbCMOTHL2DGkmQmobw7CE6NMQsjEMKO6kLRXGjRZxw
GYeeMx9ayANVGv+zzFpW3ZLgnrOXNbkHzLoLt67RZ2O2JYwBQ8NdJlKN3MGe
o18SITOS9qRPstTGTKYdxh05ds/pH83Ic6vmnMlVzh7CyranD1mXu3WOrO6p
QHCcRX2DhqoUKpMtMHk6HJhn85NI1XFx7jDi2KunC/wRAh3vimcFsGnBr2lX
RinPMV3NibEkJfAGg8QWMqe67thDYs/pDyp66cAMr0FL94osGeb6oSzlILrS
EmxrmaOUMRZFLvSlWQA6dNEb/CuFoH/dzfWvIcHt+v86MkwVU5gSHItu5hZF
cu1uL+ZfwxkByY6jTOFMERLJ+j1BkxJW7uWesHSvx81dNVBms/hsio0/A5gP
5u8NN05skmffEAUIFUUKqcOX7NiU2Xp+4UKDUXJvaqVzYru7JGWvsf/NENyF
Bp8Mgv/reDNRb4bGPDYtagkzBxLlbjMmGxEWPC0sEP3jCOZ5OM2NCLKJYEIH
snNUzBDo59xUcqeUXfP5ihxeRBKFs4i4rpbSP0bxfZjl0Yy1jkoC0iYPjH5I
0LsLhL2YYvQeMHc2eWqQu8y75SwNmLFAyWsiKYPQsr1Sr34Hii1JbNDpFzYL
I8GpPLTOs6xoNQpmqiAjbZPtveJ3Wu12nbRg6NyATx7w+l6iOgWdOtQ1ogPr
57qYp5XITE+MhFdPzwHf7eBURH6ysDWSjCYzgBcK9ISDuEseKLMm3FFocOLw
fC7qYUbIE2sFkgU6Ehc4TOfGDJfUiRUVHxY045kSowdXF0ZlcgkxDDvVle5p
shg+N3WSsaAgP6Lkpyg2egJHY62BGlPxXdKxOI54sJ3UI4mO1hKsqelJe94l
eS8tg0cdyRlgdL+p0MmqMzLscyYE+zofpwCLKvLJG2FiGSq5xh5SFliIy/pO
hyybRYUcwYuExpC/ps6CwfAbidbZnIETkKW63+vuUmFQ7HqsHMclswP1nVCg
Mscty2oeHBssgi1uKQfxkBIW/Yo4yMAj9wRROsA/j5xOT2WNR9CjDQ6sFOgU
OIwTpvS9TdGXK3rxGcLjfKUcxqi7nBJohT6TweHg2yHdLTzdOmYGZ6Gee/S4
CJ3kiVf7SqMahKBZreJgMYpmq2SVzVHTfYuIEH6QmHe5xwrJtJSGExOm3qtA
Nlg4AMwqV6pVDwgROvLVeY/1+GMpkJzouctRkEYnSbVfXxZyX0HsYQrDaAyY
Rau3nMdEre6CIC6Dcj+UJs4UkGJdrcQW1kYiTQKUWYYkTnk/61vkZ12/MgA2
NadVfCbZ6x/uQhoNehGHGuu1wDAluvDecYr2bxAFMdh2fs9WhML8+ShH4Swy
dYqDnFxaow91JAhx4ukc8JI8fUrpm8SGZkC36IFl5yAhyYCdk2VZCyxyiJRD
9zZPEoq+Vc7XqVgn7K3hianEIXRzmPIQ6o5h7TndrjY7YzMzwJYAj4feKFjo
GF2lvcue/vmI3gGbgi4q/i9p/aJ5O256b0763/UajVan1fX6l5dn2GH/5rte
p9U6bB20DobtnW6Li/e9xZJ8N70LKveqHHSnqfVrB0u4Xt1Y1Vt7X0fobxqF
Xv/kxnp8dIuZD/yTTmOv2zr6f6q72ua2rR39nb+Co87s1rmUGzt+S3L3ThVb
dtzYsmsrvXe73Z3SEm2xpkWXlOy4Sf774gFwXkhRkts4H25mmoYizzsODoAD
PFjf2d4Mj2KSTpKCxKgfp8lFMnj94+7rg7WfwvXj9de78TgexkFDsnnUFnEi
ZdMjDzN7a3Or/XJ9c4MT1q89X59bwSDJMqklkizMDEHq1bS+RT3dfL4W1DN4
l5jV1Vszy9/f6XhXBzFS4HlfIsPdxtbq9vb61vaLqL29trq+s/5yYxOReV66
WyeoBaEX1uLV+12tTX2Oy0HgJWTs5yQXTXKESnv5crXGcX6TljvPEQkd1DUH
F4g6I7WYKNP2oPKGZJhndKggaTs2Aey2FeQy3vxFTCIespGqEVWTVpRTEw4f
IDHDWIAx2gJcaqNa6fSMB9dlpAcDdhQNOaXTnyUlYjkZ8U8NYKa9dpUUAO3e
5TgC6xaPawS+kkUzFpSWWin4skoSaVupxkdwy+Hoc6c2DoNdIeYfLcs5NtAD
CTtGCxptC6m3yDMOwEVCM7EQyTUNpA069eDIJnfNIUlRMaLSExZ+OreelKYD
YRUHQwE7YSfdYVpi/AiRsINiB2y26LTK+DJpkWh8lxJFqPX9mVkG9IDqoRKD
4uF2YjIdI8JXeuxiestoUS4LKrDiVyzLL1XX0fAMxHuJyAUgYqibJaLHUxKh
hzgM1fQvEqdY/b16AI1uzVLaJI5TqmKMA38kl/q1COWGJaDOK0av+gZLro0k
LlORAjEEVUuwqpYmrc+3mnxA4Jfsn3V43LUxIhI3aG4xlvZG3U3Pv9NKRATb
3N5cgwh2Qifr6YEJVdwgRezz5xUR6Ni0p8THR2i1YgkztO2r/4G/LmrVFFHX
eaWYYHMTyyVvXAp6u68TKBnsfW+TU5cal45FcR7yan9ExHlDinuQ0UotBQCa
tuyDdTUXhS6pih+0Oa8VkGJ/VKEZHylGXLoHENc4CuISOyaZmUszakA86qTJ
ziohHVF/YrFEcJ4myZKTF56kaGKXzk/en+12mwYstmoas5tTK35IdwwYtVmC
1ln3p5ZEqDY7cRfJnZ1CJ8rwPJpAKa4og+8iq521aF8eIiQvuX8d8mQeg/rl
vaes+InvK2werpnUf4XxZmE6YATLZnfM7UigwapHjqeYcn04njiDQvVo0piM
YRqHjH975seyfPyGo5QEVL5IoHFzFdAEvewMVZ3Wq+xbOhf+7p3EKckiDCHy
D3GIuUFiLCnP4UeOB3uVxGWw1yUBZVeR7vt58CpMk8kld6v83lRKGoQciPS6
MgoiKR6GZshEQ3cDFgm5flxJUxEJ9acqJt6P+t2ZqqfeLT29HNN2JXn/VrGM
K++MBhooLKE+t6rhJ2L959zkJMmyrmyA3wAZYoClDIxKhYIejIIvJn9XqSre
EVv/hL3LeRN7Yw8vclKjcFUgjrQC+2RbcnpwauD0gtB1TlSSeGLTfoLlVmJO
Q4D9xwXydb+So09us/mCA72gU9cF5D9HjO7rkOP+iYRKtXAynsk4fN/fb+8Y
2t9af/n580yeBGqxq4Vr+4DWYucixcqaw2fmvQW0ahbRJKijlj5+ppL+yCct
n+A0datnPTPIlpV4Lz4hlUwq9qY8G/JcVCwMHqiLb8n4+JF/W19DyLOxZUlW
MrZjBVABNRqqTBRAR2NG05uUk2hNjMEQKqUF4GK/oUl6kUkI5ljvAzODzThO
ILHFhdogBKGX2aJxhcSD0pcfTFpNp6YTsCJhAmamrGO8BtbZ2G9InepO6cPU
8BFOY5OUif45UONVbplkEkR2ptp5P7Cxy+EHW6uGWzdjX3WCsiEMwFfABiYO
DiwfX8Z3csA5OuH+Pasxv4afXmO+ELP6X8KR7Bcf2sqiGC68xBVZhU7AC/d3
QxiigqAiEvP+FQ8kNiqZiRBaVgqYkkaUT0m8GzLCeGKBjtTIxAqLhOhzaGSk
HqIIKCRq4BCTQZbKKxXlIKmSau9nZuAGfJ2C2hLhdTAtJyRoFJUsTKLuUIsc
KFqSuHwfF4yv5XJPeLJLwOl4jqk3A3V++bZc4d/2K1HA+DUMkWMDf/GsotgA
JqNyJCHDmutzmEgVpwwlFv5HzeWGzbeSfANkbLBIKn2ysH24y5yWHIaMSjBl
nBPp79yHYXz3PQ47nHD/EEbEfIQh9agWJJigDUVHlGxV4Q1j+14OKbGFgNfV
rBzBLnHYq8RoWlmCj5CXgeWCM5dYKexZP6yuplgi8aAp89JntSmWKp4I6y+N
zxordpec4MNVDoM0Y3kMWeBS27mpMVR3Wu9G3DttIwOyDj7KW5lJRy+sV1zu
KPWcqsgGp+ZyTi5eMHKWboz3bFxZkyicWRNzwaDhysYNw8jZ3uJahq3D4uHk
JemkiGXGuYiIGtc3+CeXlnNWSINvnkkjvSLGjENzCku+elkHh93zAx4DbTDE
BfEoSNpNr8aSl+sDJpGTUbGztloDWNaYGV61XexIINbTavk9BZutS1zObc+u
oonYkRocPILrW6B9Y7XVMjSILmOwMc4xea5nQBn2i3hwzeyN5uOs++P7w7Pu
XmBcKIqmDtUIRZggU92DNT0HFV+ZuQ2yLcG06hG0tBjUV7vaVu3VLaaE7eDW
Ei+HRtzUujq7VAboXTKr8Vb89PiyiiXLSu8myLVKMx75qKvqkyMsROOQeB+L
njZDGxxcCenbiuCwMCtS6X0uID1RbYkN+fEdI4QEVX4A6SoJ3vSSrJxe3ADX
2USGVcerlu9g5kXKdF/AHBzZfwkPuEnHgqBMDK/EBRdtt9+kB/ye3VmNkTye
qbbhYwg/gWqLRdI2XR4a/D41AJS8e9wki98sIpL1wOC9u0fHtuD13cTDZHZz
mJnT9tiDKHP3cLztKyd8h3hYuKfnqvH5dx+r7BKINCS+tpJ6RKouPaICeXMD
Q9NJ3HQY36k5lIjRCy5AOWV73uU0Qxg5L7Mw2DJwXF8jVSpeZQifL+y8GTwt
yeen7K6ZwkND4Ry9TUyYSoqPD3MSg/Bizp4mTmVkHOmVNhI0NlKaU0C9lWil
Yj6laxmxAj9NB3e/9Op21SkugFMZrnKdg4D1Nt0RDtQEorpOUoOOb3Y1XyeP
Y16EsfXbkkvElPMG/uv4qIZDwEuvAq+wisDqbSRVrnGOxE5jSWeV8bU/FyRj
plvP5Z9otPS+ZwChhcvdya8OJtrALLh+2WWrYcoEnPipwB0ytGkDLGEyAoG7
t6TRFoSPlvyORHfYmhDkJ8VU7mD9nMQI1UxITr0o8niYPTi/N3HRAI1VSVHt
PAKwaWm5Pi6xkcICSCdzYJE/2DggPIsl0JlRilxlff7M6FaDt/k9wrCi2S3K
NCjBEDCfO1RL6RMxxkruenaiNypYbcpN/IAbRoIj1BmHcJUgHNc6nlTQXFkE
YQe/YaLefWkRKIaXWM1FhJKpQ9pXvIPcr0fValAXFyvh7Y2Tra0GfmIeK4+0
furttVt6t+iFPgmjNOZs3mhtb6QkSwoiTVfsOSnt7Z742n972u0hSTiJHuXI
+M9WNoHl8z74LfcaEEijPGf7sJq4uYNr6y82NrfawfH7vdPDbgtWClHtVfIk
HpQzkIEntDUIJYoGagYRzCNPYxAwnhqRmqz54xnJoCI1Xmo2P3jTNgquTOc3
fFRzfb9PxfDO88CB6xXTBy2JL22Wc7cUbbzgwkkSQ1Uyswd7DM7RCvrm8EDX
fajJTiW6xAvRUCZuZsRZGAxPh2eL5Wyvwu7NLdVhZFV18rI91yXu0R8iRLkA
l9G1PUOQZ0ORywt8ryhYwmsM/pghJJChjwihVs6+7mBDeJ43gweLxpcH/DTz
XRgeSEoEdh9kb5ZBljDQ49CluZtBQBvbk0yycdzZt6Wfvs2LcsIVlY+J5OGc
5VeJc+YQyUkwz1ytRrabVDDR3HsT/NRiNNgGxqknmoGHa41zV48JvSWqu1ZZ
pu4zYrUFCZYpHKCFyy/lQgKdYw2OIlhi5HmYJ6VuRcEWqoaDUT2QEMX6Z3Fr
GMvSm4k61JyxgfJWbjsNqEIuFQv3zOrdzn5mVtG391lof3tTEwR+LkSpufRh
77x0bW564CanaWFyuf6FWCAQM4zTAGhw3qGp1gsKBqrbLG25z3zyCsJKJ9Wx
5NtypZb+MzGQ83wtWEOOsm2gYrEj1ga/hPt4SGqdqqH/35b92EHM4z/eRcJi
BuRhFD6SA/0JUjOVPw2t2UF/TWJzM/vXqE348x4MJLgbY5qrGU3+AuVJrXMW
u8KUFq52hZE/+XK72p9kvb1T5SsuuNfKl6y4t85/cXUr6S7V//JR6/n4pdyV
Ox2M37RWv1EnUfc72F7dAWRdZuD1E2h+F+lloyDxhSuBOsVboFZpv+72DWhS
0l8mMPuZmsX5oW64NJoCt/DKzXc5vYUHVUnqmjfPhxN2ELbYFIl1BNAsgBon
LqJwOEpppQqk7oiByc51whatFnfXBs8CX7oUK2bMWqPLvxF4QMplw5LZufed
VKzA1oKvnXdDjrsmzc2j3rYtzX3e8kVUt15N2dndCP5aIjALMFK7+9AdZQDo
Q+sXYW8OAJfG9vU4FZzc6g4qbAUctlnTy3hSxHwvUYJsyiSlEvuWLyLZj9ZY
gNQzKPAqhcLGHtlMkSocS+o6dGSUiBd+qzquloFGc5tKR/pQJ+IJG1NsUIBx
Y1HX+JpYinmyhrsg+OTMPGEYfnIQhiE/ntkBVv98ooJt9yesPNUfK2+oYKUi
41VkHs0lqQdytrq2+qKh4LvD3p732Fxwo6EgLGRLC242FNzvhcsKrq+uNRTs
hY8ouN5U8HD3Xa9z3F1YsGlyTt+e9E+Wtdg0OfClXtrVpsnxHK/nF9xqKCgu
2Uta3G5qce/Mf2wq+KJxORBtu6TgRmNBCWleUrBpHQ+PT0+Xtti0jvBLX1qw
aR37P1cemwpuNo7xoHuyvGDTGPuH/aPu4oJbjS2enbhycws2tXh0cnCytGDT
rJ6cHYRLCzbNqkZpLC7YtDv0KFxcsGl3wNnu4OTssHs+t+B2M8856S+b1e3G
WZVE8EsKNs0q0sAvbbFpVjkL9bKCTbP6/nDPf2wu2DirPk7NvIJNPAc5W5a2
uNNQ0Dj0LSz4sumY6/63/9hUcKeRACTBzMKCLxsLuhQXCwo2UY4mNVjcIihH
JBunHHyhZOMsM4skG6uSLxBsFso1c8WaOXz7feegO28mwHubqIQNlfMnEJy3
cct29xet9CbNetMBetRfuNE3abc2tXa4WO7apL3adD6QFrC42FZTMZsYYW6x
7aZiRIvn9N+CBdhpKnZ+ctZvd84XdPJlUzH/0Jyz3M+XHNJziq2Z7VK3CH3h
pnG+N9VNU2sm/BNawKOE/zcndNp3lgnSkGmk/r2Od4wt+N5Ievi+3enttU/O
2n04Q8/9fsN9Lx8uqV+OvP2jk07/Ef3Z0v4f9uj87p4t/X5TvzeMo93vHCz6
fke/5zDgR/RnzXzvD3XheNft9+f9zvFi8RXfywHtDoDF369rf973d9sn+/vn
3f7i77f5e7cTfMU//CgZ7Mu2U7s/w9FcsOZkRyj+kHULNIpuNc2h1DNjJ5I9
ZQMFFqvYekVW21ieZm12mRnuo7ZXOPehYZMhutZUz3GR86cWyq5sna4vhD2i
lBCIp4Z/8vL8LtHIK6XYOrK4rYZScIpcQDJzSnFeY7xfVsoT2D5xnP7CtkR2
+zLxZRnZ2A5URRmPlhZR03zKeoywM5/gZohvvxdZu0UkhogIurpmntAsFNCI
I+Z29PvPEU7QSFTIiBXCiLW7CKpaZLSnyNOGIlZwItEdIsjlEUTlSMTeyAmx
4uWhoqlKIZ+AcnI9Vwr5txkFwqEXjqJi6VACqcphjMywmLbl8KhSz/KKORL9
a1R8GX/wXz5dxQig/zpTgXD8r1HxLW4BvkbFoAoJV/5TFcN4GFUsgXVB/IqY
W16k8XhexSyXz1RcMZ809tiEeSyYChhYsIs+fvxwOf78+ZEVx4Pfp3xxAJb6
lBVfkphChZ6+x3Q0+C+fruJB3gbfFJJ72oqzLImvpgvI7S/3uEhKjl572orH
SXo1usiLp5/jUZoN3ePTVUxiBs/Ck1dcphfsYvj0Fd/mcM9/+oqv07H/8gl3
nuvvE1NFMS1HX6NihMZ/lR6X9wluOhHX/NTcrfLyCRn9ldsfCyr2/zyu4oRx
TZGw7E9UHHwTdgaIgs2S4RXfCIt2IYB9BscqS68TjQEfX4f99CaEs3kZhccx
ybfnN+lEvZz3C/og2IvvSxN7q1APma0xv3QRzEjrLDPog7Odks6B+MZxOrjm
9GThVa5pN5LLSziNcG4DvXNnUJIh52HMbsMYnuDcMFDCkLwPGDkmA6bnkWE1
SE6WJfG/4lWf3sYudicYFvHlRJFz4NIs46yG+WlE7U3+Kgg612nYS5OblASU
8fCBZujiIplM6ClLPsR8HX8cPxSj/BKOZvgxAfpBNk6v8zuUSbPgHI7lNMa7
OArfMCrMUZJe4IHUu32agOmYH4oxrvL3krKYpmWZxNMP8muaBG/zhM6OMqFV
ePNbTr/RiiUjuGbQL0ikexGepYjYH/JK7Y4KGsKb4iFGdAk/Bb3knj6npwfi
CuFefJHnEf0vLadEDMfpQ3wd38f4ZUwFaamy5EGejnPSQKmJiAhh/ECtTem0
SfCOhpIhPOCGJMox/0KzTuR2n6VETPtplt6GPRp2QfXuZyzABT8n6eSPKHyb
ZFcJ/Q2Umx/iIg3fF7cxMAUwxB/iOyBXH+TDnPrwQxKP20fTQXg+IJrIknEZ
BT/kVJiOvOSCKHRI38Av6YimLTyIH/KyzOWn2xFRM3WTnqYZxEciw8Homoby
DlBtV+ERres7IoQxk35pHv45Df+JeXw3JeqkHlOjVzSGo7SMw70pr002iQIq
MwjfZCTjjZKJ7p5TZKHlRcAjzfRRTicojfgY65Nk4duYVglf0yYM9vLpVRZj
Eno05UQX1DoXPmVF/d1qeD5KEGNrfjnOiScwHfBzcA4hs02kCYDkswQgLOEh
UQVNFHX4LB+lk/AdcsMQ38gewoPiAQI6PUxocuJxErwh+vvjJnkA+faBvnQd
7ibEIGRj/JwjSUF4Ugzzq9FqEEBbv4gH12A0ewojzQi6SPdAe74MwQa4KLZ/
+PEbjddr44s2swSNL+Y8A8P0gwMVj8MRiUftLLmjacrv4PcjQQ8SQPubi/4L
2DvKBflz9EklyqwapTLbvQBdsdi56dhEcXHISqqImgh/EE5zkyNs18LeaDck
Iy4iq88nxXQw4TjkZ4v5od9rA1z9zE/ecc/O4dx+LMAc7B8Ix7pYEBTa4IoG
/YGLm7gG7/uZiCFnUdLIOGlZ0Dm0ZebwaFkgYbMEIy1IQaKqy0Ta6s3G29kQ
ShtLwxNuwzOIMBngL9xPYkxSaRCKdk96bIlmK8XbzhnsuZ73nwStsPeeBTUS
ywrsKECAPOq8gV2Fyx91zs/rwPH10i3aLVkrClvD/Ab/o3FOYvyAGlrUNGnz
LTmIZwxsoXUOhQuJlwrLrKeDMQQmXDuD377ic31bTpE1sZyF1OgcdHt9W9uK
9poaU2Q0RXVVV1Ce/QXJumWUMF1G6iFj7Eyeeh3Bl8lMmgf7H/qz54bFcLGr
QtgM97L94iXOdQmX8OEBZs1Pu53Tmhmq0krkiFI2A9HmqttCG9vbz5tbYs8Y
L5iguRZeceieLVlfGL7mrK7O+72BtQDtO2A+9h/14spt5Qgya1UXtFa97qzY
xx691Cz2+T2QkyW3GVGi4MHBZ/DK9MugVhkPXuWNlzyLxmRruyM3syZXZT0l
UW0xUcDdkrreVWGCNfyMIwJKOz40bwtwqLomz7EXJbV+e3g6Mk1eSMl/auwl
o/OBxt8L9JYzYs+6tT8ziRwm8Qcz8d6dUC23ErfLzp3Mt4U9qbdp62+t8Luw
1W6Fo3xahK1XLQSaT0lkZQ9SooGmz/5Hvvlf+Uh60xCQZBhGBZu43hG5jBOc
r9VHVKZWZTERqwkYq+TByskGBolVGnpz2IN17fFN9X9e0G1vvnmnYBi20obK
cNs9vzacbXqGDu2G0qAqHF+vwsssp0O/9bql/4JXrQ7kGxukak561pXq4gfj
OdfFj3J6QyJi+oeSd0XO8AQLD2VZwWzukoAx3RxStJUncIInH0bxtMRnq+qI
PMgLYuVM2l0DWmNpucaQQhJU41vBODJgi1bV2trZ2nF8cVomBmls9/Bs9/3x
/lH3X2FndxcHizu/kaQJGFvw76eD6aJI4ms5QPZ+fA+vL/tpKXhHdRYZVSQI
NxaHAIUCbdPxlRUDRh/6M+dxEoc/iaHxotHANGqO2PCDBWt6rQzTK8FMBpoP
4DUUSD8mgXQw8fjbm8Oz/tvTo84uiQx73Y79N48az+wn4J9HDk/DQlBubWxv
YLYdE/WHr5iO1nOnzvlxkqekURucjA8Tc+KQXOb657rEj0IygkWtpG3GxCJP
9TSZkUnAT4lBSdD27KrDM78Mfxkb4EGBBhNkND6O7Aaq4WAL0vktgOGQOJzI
m3Fjy5wRX28lYOH/xhYJDp1roAyAI2odfuFfeoIiC6K2PbhFACRH/8YMcRBn
ANvl7YfB/TL2DrMqFjbi9nH0Kjaem3qzcfgAFe98hVen5jU5HicvFRhuCTmN
JwYvWwBvazXGpaSZY6g2BASEFmY2H5MqMzF8zqKoMzgNgLTdIhQGlduh46Me
3X0OANgQkMnhyqesICfVTm/sTaqiAuXNtdtfZOArK3YaJesP+gRFryTtdOSY
UTquuytU5F8kcCDGRi1apsBfVZlC19Rm5a1EYfJpKSR4l1U0gBDStJCuM560
jI8F48E5vARE5QNDq4MAl/Pu8eHuydFJT+ASHU47MyFmymiaoWUMgK4l5vjB
0CHL6vIlB6ez05OiS6BXEoVhKFQZgI0e0wHw2EDcQsBMu9o6QFFNTyOjFFD9
ElplKd+A5Q/ToUExEOh3eLEYULgwTIoC/Xuxs7EZ4e8tYW/ESjci+Y74l/lq
Y3Nzm1/TP17Kh4bvmqqmN+HGi50Xlh7oVB4LCh5D8klIUwvYqUbwdTDOMlZs
DUCr/kErhx1dT754eH4S7mw9X3NEwgClKOPRoX8f6KJwaVbNhE6a2a6Ko6XZ
Oex/w0kpaKY5ToEjsKu4hfF4zAh5cfGgXeiMaZ1/n+aTZMbRRzmLGbTaLwwh
Rhba0GStlK5abZknENkf0zZXN6zEwbJacd7Z77ahELeYrhCXNfV9QozkRASb
Iwz8ijMwODuAiYlG6NV0gpusmgRzz7gMc0PosfWEjBUZ0QfTaUilUI2GF7qS
JaiYIbQyE38/zpt64LMsPjaEg+CdY11NwHVm4SxyXe6nK3HZK8SH0U/AMp9p
2vJaedfEEPKBcF8AhWfeYkreDqBsZMDEYEqCl9n4KuJQPTEI/Mphbi1B4GcF
9Vdf1GA8pYHIGZ2wTo8+jdumVH4EqGbKWU09AxtT6Gtt1LX5K9DXkf9Z8gcb
bzZFPmY0V8NB4itUNXFsytMtJdovMp0GkkyIRTXQ6nGGWnJg/plgTPoYKV/a
VplV4EgvhZKIttgHq8H/A8hmXviBzAEA

-->

</rfc>

