Glenn Parsons (gparsons@nortelnetworks.com)
Fri, 9 Mar 2001 14:08:50 -0500
> Folks,
>
> I've been distracted by my sabbatical for the first two months of this
> year...
>
> Anyway, I requested only one meeting slot for VPIM. And we won the Friday
> slot again (perhaps because we didn't complain loudly last time :-) This
> sufficed with our pre-meeting at IETF 49. Do folks think it would be
> useful to have a another pre-meeting (aka Bar BOF) to discuss any burning
> issues? I doubt I could secure a room like last time...
>
> In any case here are the topics that I think we will want to discuss and
> put on the agenda:
>
>
> VPIM milestones
> I still need to update these :-)
>
> VPIM v2
> Greg & I were distracted from getting a new draft out to discuss -- his
> excuse's name is Stephen and was born on March 3rd. The current draft is
> draft-ietf-vpim-vpimv2r2-01.txt. We will update this after the meeting,
> then likely go for a WG last call on this and the drafts for the other
> VPIM v2 RFCs (2422-4) that need to be elevated to Draft Standard.
> However, the important discussion will be on the status of moving the
> dependencies like DSN and MDNs forward to Draft Standard.
>
> VPIM Directory
> There are two topics here. The first is the global address resolution
> provided by ENUM. Greg did not update the draft on VPIM's use of ENUM
> (draft-ietf-vpim-routing-01.txt). Secondly, we need to close on the VPIM
> schema (Greg & Anne merged their proposals in
> draft-ietf-vpim-vpimdir-00.txt but work is needed to tidy up the syntax).
> I hope to do a WG last call on these after the meeting.
>
> VPIM Addressing
> This draft has not been updated for the last call comments (the last one
> was draft-ietf-vpim-address-00.txt) but I should get time in the next few
> weeks. I plan to send this for IESG last call after the meeting.
>
> IVM
> The goals document will be updated by Emily (it was
> draft-ietf-ivm-goals-01.txt). We should discuss if we want to last call
> this to Informational or just leave it. Stuart & I updated the IVM base
> document for the last meeting (draft-ietf-vpim-ivm-01.txt) but did not get
> a chance to for this meeting. The WAV & MS-GSM are long expired and need
> an update from Microsoft - but there is also G.711 mu-law - stay tuned.
> As well, I think that we are almost closed on the primary/critical content
> hint concept, its requirements and implications. Eric updated critical
> content (draft-ietf-vpim-cc-03.txt), so we will discuss that as well as
> the hotly discussed content hint draft (draft-ietf-vpim-hint-04.txt).
>
> VPIM Addenda
> These may or may not fall under our charter but I still think they are
> relevant and useful to review. We may or may not (depending on time)
> discuss the following:
>
> - IMAP draft on telset playback of voice messages
> - draft on extended headers (for spoken name, subject, etc.)
> - draft on putting CLID info in the headers
> - draft on desired client behaviour when dealing with voice mail
- draft on SIP MWI
> - draft on profiling VPIM et al for 3G wireless
>
>
> How does this sound? Is there anything I am missing?
>
I will create a more 'formal' version of this to send in by Mar 14th next
week...
> Cheers,
> Glenn.
>
>
>
This archive was generated by hypermail 2.0b3 on Fri Mar 09 2001 - 21:16:26 IST