IETF69
======

Calsify Working Group minutes for March 11, 2008
================================================

Chairs:
    
    Eliot Lear <mailto:lear@cisco.com>
    Aki Niemi <mailto:aki.niemi@nokia.com>
    
Agenda:

       #. Topic                presents    time
       -------------------------------------------------
       1. Agenda Bash          chairs      15:20 - 15:21
       2. Administrivia        chairs      15:21 - 15:35
       3. RFC2446bis issues    Cyrus       15:35 - 17:10
       4. All other business   chairs      17:10 - 17:20
       
Documents:

    - RFC2445bis:
    http://tools.ietf.org/html/draft-ietf-calsify-rfc2445bis-08    
    
    - RFC2446bis:
    http://tools.ietf.org/html/draft-ietf-calsify-2446bis-05
    
    - RFC2447bis:
    http://tools.ietf.org/html/draft-ietf-calsify-rfc2447bis-03
    
Resources:

    - Calsify WG Issue Tracker:
    http://www.ofcourseimright.com/cgi-bin/roundup/calsify/
    
    - Calsify WG Status Pages (Jabber logs, etc.)
    http://tools.ietf.org/wg/calsify


Minutes:
========

    
1. Agenda Bash
--------------

Slides:
http://www3.ietf.org/proceedings/08mar/slides/calsify-0.ppt

Going with the proposed agenda.


2. Administrivia (Eliot Lear)
-----------------------------

Working group is finishing up RFC2446bis. Eliot will handle proto 
writeup on RFC2446bis. 

Will move on to RFC2447bis, which will be handled on the mailing list 
only.

Nothing else in the charter; this will be the last meeting of Calsify.

Cyrus Daboo: About VVENUE, since the last meeting, it has become clear 
that VVENUE is really more a vCard issue. So not a Calsify issue after
all.

Cyrus Daboo: The vcarddav working group is doing an XML transform for
vcard, which might play into what calsify is doing.

Eliot: Needs to be taken up with ADs whether XML is something calsify
needs to do.


3. RFC2446bis issues (Cyrus Daboo)
----------------------------------

Slides: 
http://www3.ietf.org/proceedings/08mar/slides/calsify-1.pdf

New version (-05) is now out with text changes, removal of EXRULE,
PROCEDURE alarms, and with fixed examples.

Proposal for issue 85. No disagreements.

Proposal for issue 86. Some push-back received on the list. Some support
for the proposed text, but need to confirm consensus on list.

Issue 90 waiting on RANGE= resolution.

Proposed text for issue 95 to be sent on mailing list. Room seems happy 
with the text if it makes clear that unrecognized codes get ignored and
that new codes should be documented.

Consensus on issue 67 is to go with option a): Remove statement from
RFC2445bis.

4. AOB
------

Discussion of Spam messages with iCalendar objects. No conclusions.

Meeting adjourned at 13:16.