RE: MTF meeting invitation - Friday 11 am / 3 pm

To: <mtf@xxxxxxxx>

Subject: RE: MTF meeting invitation - Friday 11 am / 3 pm

From: "Irina Yermakova" <IYermakova@xxxxxxxx>

Date: Fri, 14 Mar 2008 11:09:15 -0400

Importance: normal

In-reply-to: <021c01c884fa$f0641380$d12c3a80$@lynn@global-emarkets.com>

References: <021c01c884fa$f0641380$d12c3a80$@lynn@global-emarkets.com>

Reply-to: mtf@xxxxxxxx

Sender: mtf@xxxxxxxx

Thread-index: AchkDl7HoqZK+uw5TA+vZyiPWZpuXAFv/aswAUtTuaABYCJy8AFh2LbAAV4YyqABXmjdsAA75Xfw

Thread-topic: MTF meeting invitation - Friday 11 am / 3 pm

Attached the breakdown issue summary.

From: mtf@xxxxxxxx [mailto:mtf@xxxxxxxx] On Behalf Of Brian Lynn
Sent: Thursday, March 13, 2008 7:11 AM
To: mtf@xxxxxxxx
Subject: MTF meeting invitation - Friday 11 am / 3 pm

Reminder ...

Next meeting will be this Friday (tomorrow) at 11 am (NY)/3pm (London). (Note UK time change. Sorry for those people in the UK who have trouble with the new time.)

US: 888 481 3032

Intl: 617 801 9600

UK: 0800 904 7961

Participant Code: 28413758

Agenda:

- Review/discuss overall implementation status report (see attached draft).

- Discuss request from CDWG for advice on how to model eliminate optionality from credit events where the content model isn’t empty. See attached diagram for a proposal, e.g FailureToPay.

- Discuss comparison with other standards, determine whether we can move ahead with proposed FpML messaging changes. (see attached).

- Discuss Matthew’s proposal that unique trade identification be supported via validation rules, as described in the attached document (these are the validation rules that have been added for contract notification). (I am particularly interested how this approach might work in a central service provider context when there are multiple trade IDs on a message).

- AOB

************************************************************************************************************************** The information contained in either this email and, if applicable, the attachment, are confidential and are intended only for the recipient. The contents of either the email or the attachment may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, or distribution is prohibited and may be unlawful. If you have received this communication in error, please notify us by e-mail at isda@xxxxxxxx then delete the e-mail and all attachments and any copies thereof. This communication is part of an ISDA process and is not intended for unauthorized use or distribution. **************************************************************************************************************************

Attachment: IssueUpdatedSummary.doc
Description: IssueUpdatedSummary.doc