vCard Extensions for Instant Messaging (IM)
draft-jennings-impp-vcard-08

[Ballot comment]
User question: how do I express that the URI is appropriate for both personal and business communication? If it should be TYPE=BUSINESS,PERSONAL maybe it should be mentioned that types are not exclusive.

[Ballot discuss]
(built from Gen-ART review by Spencer Dawkins)

Something is wrong with either the text description, or the ABNF, or my brain.

  Type special notes: The type can include the type parameter "TYPE" to
  specify an intended use for the URI.

As far as I can parse the ABNF this should be "MUST include".

  The TYPE parameter values can
  include:

  o  An indication of the type of communication for which this URI is
      appropriate.  This can be a value of PERSONAL or BUSINESS.
  o  An indication of the location of a device associated with this
      URI.  Values can be HOME, WORK, or MOBILE.

As I read the ABNF there MUST be at least one impp-type, so 'can include' is inaccurate, and the set of impp-types listed is exclusive, so both 'can be's are slightly misleading. (The language in RFC 2426 for the EMAIL type
is equally confusing to me.)

[Ballot discuss]
This document apparently imports the definition of uri from 2425, which in turn
says that URI is "as defined in 1738".  1738's description of URIs has long been
superseded, and its formal description of genericurl (the closest thing to this)
is in RFC822's BNF-like grammar, not ABNF.  May I suggest this document cite
RFC 3986 directly? It's a full standard.  I believe citing the ABNF RFC as normative
is also required.

[Ballot comment]
Might want to mention that some vendors have already extended the
  vcard format to include IM addresses. For example, my Apple
  AddressBook vcard has .

Section 1., paragraph 4:

>      "sip"[5] indicates to use SIP/SIMPLE,
>      "xmpp"[6] indicates to use XMPP,
>      "irc"[4] indicates to use IRC,
>      "ymsgr" indicates to use yahoo,
>      "msn" might indicate to use Microsoft messenger,
>      "aim" indicates to use AOL, and
>      "im"[8] or "pres"[7] indicates to use a CPIM or CPP gateway.

  Nit: Insert a space before the reference.


Section 2., paragraph 8:

>    o  An indication of the type of communication for which this URI is
>      appropriate.  This can be a value of PERSONAL or BUSINESS.
>    o  An indication of the location of a device associated with this
>      URI.  Values can be HOME, WORK, or MOBILE.

  This set of options only encodes a very limited set of usage
  scenarios.  Is there any rationale that these are sufficient or
  useful? (Since they cannot be omitted according to the ABNF.) Is there
  any definition of the semantics of the tags?

[Ballot comment]
Might want to mention that some vendors have already extended the
  vcard format to include IM addresses. For example, my Apple
  AddressBook vcard has
  "X

[Ballot comment]
Might want to mention that some vendors have already extended the
  vcard format to include IM addresses. For example, my Apple
  AddressBook vcard has
  "X

[Ballot comment]
Might want to mention that some vendors have already extended the
  vcard format to include IM addresses. For example, my Apple
  AddressBook vcard has
  "X

[Ballot comment]
Might want to mention that some vendors have already extended the
  vcard format to include IM addresses. For example, my Apple
  AddressBook vcard has:

X

[Ballot discuss]
(built from Gen-ART review by Spencer Dawkins)

Something is wrong with either the text description, or the ABNF, or my brain.

  Type special notes: The type can include the type parameter "TYPE" to
  specify an intended use for the URI.

As far as I can parse the ABNF this should be "MUST include".

  The TYPE parameter values can
  include:

  o  An indication of the type of communication for which this URI is
      appropriate.  This can be a value of PERSONAL or BUSINESS.
  o  An indication of the location of a device associated with this
      URI.  Values can be HOME, WORK, or MOBILE.

As I read the ABNF there MUST be at least one impp-type, so 'can include' is inaccurate, and the set of impp-types listed is exclusive, so both 'can be's are slightly misleading. (The language in RFC 2426 for the EMAIL type
is equally confusing to me.)

User question: how do I express that the URI is appropriate for both personal and business communication?

IANA Last Call Comments:

Upon approval of this document, IANA understands that there is a single IANA action to be taken.

IANA will add a new registration to the text/directory MIME types subregistry in the text/directory MIME registry located at:
http://www.iana.org/assignments/text-directory-registrations.

The text of that registration will be:

Type name: IMPP

Type purpose: To specify the URI for instant messaging and presence
protocol communications with the object the vCard represents.

Type encoding: 8bit

Type value: A single URI. The type of the URI indicates the protocol
that can be used for this contact.

Type special notes: The type can include the type parameter "TYPE" to
specify an intended use for the URI. The TYPE parameter values can
include:

o An indication of the type of communication for which this URI is
appropriate. This can be a value of PERSONAL or BUSINESS.
o An indication of the location of a device associated with this
URI. Values can be HOME, WORK, or MOBILE.
o The value PREF indicates this is a preferred address and has the
same semantics as the PREF value in a TEL type.

Additional information can be found in RFCtbd.

Intended usage: COMMON

IANA will substitute the proper RFC number at the time of publication (in place of RFCtbd).

IANA understands that this is the only IANA action required for this document.