[VCARDDAV] IETF79 vcarddav wg meeting notes

Marc Blanchet <marc.blanchet@viagenie.ca> Mon, 15 November 2010 18:46 UTC

Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: vcarddav@core3.amsl.com
Delivered-To: vcarddav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6193B3A6AAB for <vcarddav@core3.amsl.com>; Mon, 15 Nov 2010 10:46:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.277
X-Spam-Level:
X-Spam-Status: No, score=-102.277 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, J_CHICKENPOX_45=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JB-1FHvyr5rE for <vcarddav@core3.amsl.com>; Mon, 15 Nov 2010 10:46:10 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id F2E213A6B7F for <vcarddav@ietf.org>; Mon, 15 Nov 2010 10:46:09 -0800 (PST)
Received: from h109.viagenie.ca (unknown [IPv6:2620:0:230:c000:5ab0:35ff:fef4:6fa]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 0A36820E59 for <vcarddav@ietf.org>; Mon, 15 Nov 2010 13:46:50 -0500 (EST)
Message-ID: <4CE1801A.70100@viagenie.ca>
Date: Mon, 15 Nov 2010 13:46:50 -0500
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: CardDAV <vcarddav@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [VCARDDAV] IETF79 vcarddav wg meeting notes
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Nov 2010 18:46:19 -0000

Hello,
  please find the minutes of our meeting. Please send any modifications 
to me directly.

Marc, co-chair.

--------------------

IETF Vcarddav working group
IETF 79 meeting, Beijing, China
November 10th 2010, 15h10-16h10

1. Administrativia

2. vcard4 and vcardxml wglc comments (Perreault, Resnick)
  draft-ietf-vcarddav-vcardrev
  draft-ietf-vcarddav-vcardxml

- i18n email
   - Problem: How to allow Unicode characters in EMAIL. Choose eai? 
utf-8? ...
   - Resolution: None. Chairs will discuss with area directors about.

- Restoring N format
   - Problem: Current format for N is not backward compatible.
   - Resolution: Go back to vCard 3's format and allow multiple items in
each component.

- DDAY, BIRTH, DEAH
   - Problem: New properties which are not widely implemented.
   - Resolution: Remove them from base vCard 4. (Could be defined as an
extension.)

- Remove fields from ADR
   - Problem: PO box and extended address fields are misunderstood and
not interoperable.
   - Resolution: Keep fields, but indicate that they SHOULD be empty.

- Link LABEL to ADR
   - Problem: No way to know which LABEL is associated with which ADR.
   - Resolution: Remove LABEL property and make it a parameter of ADR.

- Remove BINARY
   - Problem: BINARY value type is redundant with data: URI scheme.
   - Resolution: Remove BINARY property, remove FMTTYPE and ENCODING
parameters.

- SEX
   - Problem: Biological vs psychological semantics are unclear. Allowed
values are un-intuitive and restrictive.
   - Resolution: Rename SEX to GENDER. Change values to (male, female,
<free-form text>). IANA registry for additional values that could be 
reserved.

- TEL property
   - Problem: Previous parsers of TEL property values cannot parse tel: 
URIs.
   - Resolution: Default to free-form text, but SHOULD reset to a URI.

- CALSCALE parameter
   - Problem: Having only a single pre-defined value makes this parameter
useless.
   - Resolution: Refer to iCalendar and create an IANA registry for 
calendar types.

- Calendar properties
   - Problem: FBURL, CALADRURI, and CALURI are new for vCard 4. Maybe
better suited for an extension.
   - Resolution: Keep them.

- Date ranges
   - Problem: Proposal to add a new parameter for identifying validity
ranges for properties.
   - Resolution: Do not add.

- KIND property
   - Problem:
     - KIND property is new for vCard 4.
     - Maybe BEGIN:VGROUP would be better.
     - Semantics for KIND:thing are vague.
   - Resolution:
     - Reduce the list to the ones we think we understand well right now.
     - If you want new ones registered, you have to write a draft that
profiles the fields that make sense for that kind.

- RELATED property
   - Problem: Property is new for vCard 4. Allowed values do not make
consensus. Multiple types are impossible.
   - Resolution:
     - Use the XFN 1.1 taxonomy.
     - Allow a list of types.

- Synchronization
   - Problem: Synchronization is new for vCard 4.
   - Resolution: Keep it.

- CATEGORIES property
   - Problem: Would be nice to use URIs as tags.
   - Resolution: Do not do this. (Could be specified in an extension.)

- VERSION parameter
   - Problem: VERSION parameter is useless, violates DRY.
   - Resolution: None. ("Take it to the list.")
     - Proposal: Drop it. Specify 1.0 in text.

- CLASS parameter
   - Problem: Not used in practice. Interoperability is bad.
   - Resolution: Drop it.

- Case sensitivity
   - Problem: Case causes interoperability issues in practice.
   - Resolution: Output SHOULD be upper-case. Accept both.

- New ACCOUNT property
   - Problem: Proposal for a new ACCOUNT property.
   - Resolution: Reject proposal. (Could be added in an extension.)

- REV property
   - Problem: Proposal for allowing date resolution.
   - Resolution: Reject proposal.

- Cardinality notation
   - Problem: Notation is new, people are unfamiliar with it.
   - Resolution: Adopt ABNF notation.

3. Charter discussion
  Concensus was that there are possible additional work items. Next IETF 
should have a vcarddav meeting to discuss these.


-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN Implementation: http://postellation.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca