Real-Time Public Reporting of Swap Transaction Data

Federal RegisterDec 7, 2010

Ask Donna

What actually matters in this document.

Text

COMMODITY FUTURES TRADING COMMISSION

17 CFR Part 43

RIN 3038-AD08

Real-Time Public Reporting of Swap Transaction Data

AGENCY:

Commodity Futures Trading Commission.

ACTION:

Notice of proposed rulemaking.

SUMMARY:

The Commodity Futures Trading Commission (“Commission”) is proposing rules to implement new statutory provisions enacted by Title VII of the Dodd-Frank Wall Street Reform and Consumer Protection Act (the “Dodd-Frank Act”). Specifically, in accordance with Section 727 of the Dodd-Frank Act, the Commission is proposing rules to implement a new framework for the real-time public reporting of swap transaction and pricing data for all swap transactions. Additionally, the Commission is proposing rules to address the appropriate minimum size and time delay relating to block trades on swaps and large notional swap transactions.

DATES:

Comments must be received by February 7, 2011.

ADDRESSES:

You may submit comments, identified by RIN number 3038-AD08, by any of the following methods:

• Federal eRulemaking Portal at

http://www.regulations.gov

. Follow the instructions for submitting comments.

•

Agency Internet Web site, via Its Comments Online Process: http://comments.cftc.gov

. Follow the instructions for submitting comments through the Internet Web site.

•

Mail:

David A. Stawick, Secretary of the Commission, Commodity Futures Trading Commission, Three Lafayette Centre, 1155 21st Street, NW., Washington, DC 20581.

•

Hand Delivery/Courier:

Same as mail above.

All comments must be submitted in English, or if not, accompanied by an English translation. Comments will be posted as received on

http://www.cftc.gov

. You should submit only information that you wish to make publicly available. If you wish the Commission to consider information that is exempt from disclosure under the Freedom of Information Act, a petition for confidential treatment of the exempt information may be submitted according to the established procedures in Commission Regulation § 145.9.

17 CFR 145.9.

The Commission reserves the right, but shall not have the obligation, to review, pre-screen, filter, redact, refuse, or remove any or all of your submission from www.cftc.gov that it may deem to be inappropriate for publication, such as obscene language. All submissions that have been redacted or removed from the Commission's Internet Web site, but that contain comments on the merits of the rulemaking, will be retained in the public comment file and will be considered as required under the Administrative Procedure Act, 5 U.S.C. 551

et seq.,

and other applicable laws, and may be accessible under the Freedom of Information Act, 5 U.S.C. 552.

FOR FURTHER INFORMATION CONTACT:

Thomas Leahy, Associate Director, Division of Market Oversight, 202-418-5278,

tleahy@cftc.gov;

or Jeffrey L. Steiner, Special Counsel, Division of Market Oversight, 202-418-5482,

jsteiner@cftc.gov

; Commodity Futures Trading Commission, Three Lafayette Center, 1155 21st Street, NW., Washington, DC 20581.

SUPPLEMENTARY INFORMATION:

Table of Contents

I. Background

II. Explanation of the Proposed Rules

A. Overview

1. Introduction

2. Parties Responsible for Reporting Swap Transaction and Pricing Data to a Registered Entity

3. Parties Responsible for Publicly Disseminating Swap Transaction and Pricing Data in Real-Time

4. Proposed Effective Date and Implementation Schedule

B. Section-by-Section Analysis

1. Proposed Section 43.1—Purpose, Scope and Rules of Construction

2. Proposed Section 43.2—Definitions

3. Proposed Section 43.3—Method and Timing for Real-Time Public Reporting

i. Responsibilities of the Reporting Party To Report Data

ii. Responsibilities of Swap Markets To Publicly Disseminate Swap Transaction and Pricing Data in Real-Time

iii. Requirements for Registered SDRs

iv. Requirements for Third-Party Service Providers

v. Availability of Real-Time Swap Transaction and Pricing Data

vi. Errors or Omissions

vii. Hours of Operation

viii. Recordkeeping Requirements

ix. Fees Charged by Registered SDRs

x. Consolidated Public Dissemination of Swap Data

4. Proposed Section 43.4 and Appendix A to Proposed Part 43—Swap Transaction and Pricing Data to be Publicly Disseminated in Real-Time

i. Ensuring the Anonymity of the Parties to a Swap

ii. Unique Product Identifiers

iii. Price-Forming Continuation Data

iv. Reporting and Public Dissemination of Notional or Principal Amount

v. Appendix A to Proposed Part 43

vi. Examples to Illustrate the Public Reporting of Real-Time Swap Transaction and Pricing Data

5. Proposed Section 43.5—Block Trades and Large Notional Swaps

i. Parties to a Block Trade or Large Notional Swap

ii. Block Trades on Swaps

iii. Large Notional Swaps

iv. Time-Stamp and Reporting Requirements for Block Trades and Large Notional Swaps

v. Responsibilities of Registered SDRs in Determining the Appropriate Minimum Block Size

vi. Formula to Calculate the Appropriate Minimum Block Size

vii. Distribution Test

viii. Multiple Test

ix. Responsibilities of Swap Markets in Determining Minimum Block Trade Sizes

x. Responsibilities of the Parties to a Swap in Determining the Appropriate Minimum Large Notional Swap Size

xi. Time Delay in the Real-Time Public Reporting of Block Trades and Large Notional Swaps

xii. Prohibition of Aggregation of Trades

III. Related Matters

A. Cost-Benefit Analysis

1. Introduction

2. Summary of Proposed Requirements

3. Costs

4. Benefits

B. Paperwork Reduction Act

1. Introduction

2. Information Provided by Reporting Entities/Persons

i. Reporting Requirement

ii. Public Dissemination Requirement

iii. Recordkeeping Requirement

iv. Determination of Appropriate Minimum Block Size

3. Information Collection Comments

C. Regulatory Flex Act

I. Background

On July 21, 2010, President Obama signed the Dodd-Frank Wall Street Reform and Consumer Protection Act (“Dodd-Frank Act”).

Title VII of the Dodd-Frank Act

amended the Commodity Exchange Act (“CEA”)

to establish a comprehensive, new regulatory framework for swaps and security-based swaps.

The legislation was enacted to reduce risk, increase transparency and promote market integrity within the financial system by, among other things: (1) Providing for the

registration and comprehensive regulation of swap dealers and major swap participants (“MSPs”); (2) imposing mandatory clearing and trade execution requirements on standardized derivative products; (3) creating robust recordkeeping and real-time reporting regimes; and (4) enhancing the Commodity Futures Trading Commission's (“Commission” or “CFTC”) rulemaking and enforcement authorities with respect to, among others, all registered entities and intermediaries subject to the Commission's oversight.

See

Dodd-Frank Wall Street Reform and Consumer Protection Act, Public Law 111-203, 124 Stat. 1376 (2010). The text of the Dodd-Frank Act may be accessed at

http://www.cftc.gov./LawRegulation/OTCDERIVATIVES/index.htm

Pursuant to Section 701 of the Dodd-Frank Act, Title VII may be cited as the “Wall Street Transparency and Accountability Act of 2010.”

7 U.S.C. 1

et seq.

Rules governing the reporting and dissemination of security-based swaps are the subject of a separate and forthcoming rulemaking by the Securities and Exchange Commission (“SEC”).

Accordingly, in order to ensure the proper implementation of the new regulatory framework, Section 727 of the Dodd-Frank Act created Section 2(a)(13) of the CEA, which requires the Commission to promulgate rules that provide for the public availability of swap transaction and pricing data in real-time in such form and at such times as the Commission determines appropriate to enhance price discovery.

Under new Section 2(a)(13)(A) of the CEA, the definition of “real-time public reporting” means reporting “data relating to a swap transaction, including price and volume, as soon as technologically practicable after the time at which the swap transaction has been executed.”

Section 2(a)(13)(B) of the CEA states that “[t]he purpose of this section is to authorize the Commission to make swap transaction and pricing data available to the public in such form and at such times as the Commission determines appropriate to enhance price discovery.”

It is notable that the CEA is silent as to the appropriate method through which real-time public reporting must occur.

Sections 2(a)(13)(C)(i) through (iv) of the CEA set out the four types of swaps for which transaction and pricing data must be reported to the public in real-time: (i) Swaps that are subject to the mandatory clearing requirement

(including those swaps that may qualify for a non-financial end-user exception from the mandatory clearing requirement);

(ii) swaps that are not subject to the mandatory clearing requirement but are cleared at a registered derivatives clearing organization (“DCO”); (iii) swaps that are not cleared at a registered DCO and which are reported to a registered swap data repository (“SDR”) or to the Commission pursuant to Section 2(h)(6) of the CEA; and (iv) swaps that are “determined to be required to be cleared” under Section 2(h)(2) of the CEA but are not cleared. The four categories described in Section 2(a)(13)(C) of the CEA cover all swaps and, therefore, the real-time reporting requirements apply to all swaps, including those swaps executed on a registered swap execution facility (“SEF”) or a registered designated contract market (“DCM,” together with a SEF, a “swap market”) and those swaps executed bilaterally between counterparties and not pursuant to the rules of a SEF or DCM (“off-facility swaps”).

The mandatory clearing requirement is found in Section 2(h)(1) of the CEA, as added by Section 723(a)(3) of the Dodd-Frank Act.

Section 2(h)(7) of the CEA provides the non-financial end-user exception from the mandatory clearing requirement.

The legislative history of the Dodd-Frank Act also suggests that the real-time reporting requirements of Section 2(a)(13) apply to all swaps. Senate Agriculture Committee Chairwoman Blanche Lincoln stated during Senate deliberations that “[t]he major components of the derivatives title include: 100 percent reporting of swaps and security-based swaps, mandatory trading and clearing of standardized swaps and security-based swaps and real-time price reporting for all swap transactions—those subject to mandatory trading and clearing as well as those subject to the end-user clearing exemption and customized swaps.” 156 Cong. Rec. S5,920 (daily ed. July 15, 2010) (statement of Sen. Blanche Lincoln).

With regard to swaps described in Sections 2(a)(13)(C)(i) and (ii) of the CEA, Section 2(a)(13)(E) of the CEA provides that the Commission shall prescribe rules that: (i) Ensure such information does not identify the participants; (ii) specify the criteria for determining what constitutes a large notional swap transaction (block trade) for particular markets and contracts; (iii) specify the appropriate time delay for reporting large notional swap transactions (block trades) to the public; and (iv) take into account whether public disclosure will materially reduce market liquidity. CEA Section 2(a)(13)(E) does not state explicitly that the proposed rules must contain similar provisions for those swaps described in Sections 2(a)(13)(C)(iii) and (iv). However, in applying its authority under Section 2(a)(13)(B) to “make swap transaction and pricing data available to the public in such form and at such times as the Commission determines appropriate to enhance price discovery,” the Commission is authorized to prescribe similar rules to those provisions in Section 2(a)(13)(E) for off-facility swap transactions described in Sections 2(a)(13)(C)(iii) and (iv).

In addition, the Commission is required by Section 2(a)(13)(C)(iii) of the CEA to prescribe real-time public reporting requirements for off-facility swaps “in a manner that does not disclose the business transactions and market positions of any person.”

II. Explanation of the Proposed Rules

A. Overview

1. Introduction

The Commission proposes to create a new part 43 of its regulations, implementing the provisions of Section 2(a)(13) of the CEA. The proposed rules in part 43 set out: (1) The entities or persons that shall be responsible for reporting swap transaction and pricing data; (2) the entities or persons that shall be responsible for publicly disseminating such data; (3) the data fields and guidance on the appropriate order and format for data to be reported to the public in real-time; (4) the appropriate minimum size and time delay for block trades and large notional swaps; and (5) the proposed effective date and implementation schedule for the proposed rules.

The proposed rules reflect consultation with staff of the Securities and Exchange Commission (the “SEC”)

and staff of the Board of Governors of the Federal Reserve.

Staff from each of these agencies has provided verbal and/or written comments and the proposed rules incorporate elements of the comments provided. The proposed rules have been further informed by (i) the joint roundtable conducted by CFTC staff and staff of the SEC on September 14, 2010 (the “Roundtable”);

(ii) public comments posted on the Commission's Internet Web site;

and (iii) CFTC staff meetings with market participants.

Section 763 of the Dodd-Frank Act authorizes the SEC to promulgate rules “to provide for the public availability of security-based swap transaction, volume, and pricing data * * *.”

See

Section 712(a)(1) of the Dodd-Frank Act requires staff to consult with the SEC and other prudential regulators.

The transcript from the Roundtable (the “Roundtable Tr.) is available at:

http://www.cftc.gov/ucm/groups/public/@swaps/documents/file/derivative18sub091410.pdf

Such comments are available at:

http://www.cftc.gov/LawRegulation/DoddFrankAct/OTC_18_RealTimeReporting.html.

A list and description of such meetings is available at:

http://www.cftc.gov/LawRegulation/DoddFrankAct/ExternalMeetings/index.htm

The SEC is adopting rules related to the real-time reporting of security based swaps as required under Section 763 of the Dodd-Frank Act. Understanding that the Commission and the SEC regulate different products and markets and, as such may be proposing alternative regulatory requirements, the Commission requests comments on the impact of any differences between the Commission's and the SEC's approach to the regulation and reporting of swaps and security-based swaps and the public dissemination of swap transaction and

pricing data in real-time. In addition, the Commission requests specific comment on the following issues:

• Would the regulatory approach of the Commission in this proposed rulemaking, pursuant to Section 727 of the Dodd-Frank Act, and the SEC's proposed rulemaking, pursuant to Section 763 and 766 of the Dodd-Frank Act, result in duplicative or inconsistent requirements on the part of market participants to both regulatory regimes or result in gaps between those regimes? If so, in what way should these duplications, inconsistencies or gaps be minimized?

• Do commenters believe that the proposed approaches by the Commission and the SEC for the real-time reporting and public dissemination of swap transaction and pricing data are comparable? If not, why? Are there approaches that could make the real-time reporting and public dissemination of swap transaction and pricing data more comparable? If so, what?

• Do commenters believe that it would be appropriate for the Commission to adopt an approach proposed by the SEC that differs from the Commission's proposal? If so, which one(s)? The Commission requests that commenters provide data, to the extent possible, to support any suggested approaches.

2. Parties Responsible for Reporting Swap Transaction and Pricing Data to a Registered Entity

Section 2(a)(13)(F) of the CEA provides that the parties to a swap (including agents of the parties to a swap) shall be responsible for reporting swap transaction information to the appropriate registered entity

in a timely manner as may be prescribed by the Commission.

For off-facility swaps, the Commission's proposal places the requirement to report the swap transaction and pricing data in real-time to a registered entity (

i.e.,

a registered SDR that accepts and publicly disseminates real-time swap transaction and pricing data in real-time) in a manner similar to that in which all swap transaction information for uncleared swaps would be reported to a registered SDR pursuant to Section 4r(a)(3) of the CEA.

With respect to swaps that are executed on a swap market, the Commission's proposal provides that if the parties to a swap execute a transaction on a swap market, then the transacting parties' reporting requirements under Section 2(a)(13)(F) of the CEA are satisfied. The Commission views the real-time swap transaction and pricing data that is sent to a real-time disseminator and the swap information that is sent to a registered SDR as two separate and distinct data streams.

Section 1a(40) of the CEA, as amended by Section 721(a) of the Dodd-Frank Act, defines “registered entity” to include SEFs, DCMs and SDRs, but does not include swap dealers and MSPs. Section 1a(40) also defines registered entity to include DCOs. The Commission has determined not to apply this requirement to DCOs because it believes that the value of timely public dissemination outweighs the benefit of waiting until a swap is presented to a clearing organization.

Sections 4s(f)(1)(A) and 4s(f)(2) of the CEA, provide the Commission with broad authority to adopt rules governing the reporting of all swap transaction information for swap dealers and MSPs. Specifically, Section 4s(f)(1)(A) of the CEA provides that “[e]ach registered swap dealer and major swap participant shall make such reports as are required by the Commission by rule or regulation regarding the transactions and positions and financial condition of the registered swap dealer or major swap participant * * *” Section 4s(f)(2) of the CEA provides that “[t]he Commission shall adopt rules governing reporting and recordkeeping for swap dealers and major swap participants.” Additionally, Sections 4s(h)(1)(D) and 4s(h)(3)(D) of the CEA provide the Commission with rulemaking authority to establish business conduct standards and requirements relating to the real-time reporting requirements on swap dealers and major swap participants.

Section 4r(a)(3) of the CEA provides that for swaps in which only one counterparty is a swap dealer or MSP, the swap dealer or MSP is required to report the swap to a registered SDR. For swaps in which only one counterparty is a swap dealer and the other is an MSP, the swap dealer is required to report to a registered SDR. For all other swaps, Section 4r(a)(3) provides that the counterparties to the swap shall select a counterparty to report to a registered SDR.

The real-time reporting requirements pursuant to Section 2(a)(13) of the CEA are separate and apart from the requirements to report swap transaction information to a registered SDR. The reporting requirements for all swap transaction information to an SDR are found in Sections 2(a)(13)(G) and 4r(a)(1) of the CEA. Specifically, Section 2(a)(13)(G) of the CEA provides that [e]ach swap, (whether cleared or uncleared) shall be reported to a registered swap data repository.” In addition, Section 4r(a)(1) provides that “[e]ach swap that is not accepted for clearing by any [DCO] shall be reported to [an SDR] described in section 21 [of the CEA];” or if no SDR exists, to the Commission.

3. Parties Responsible for Publicly Disseminating Swap Transaction and Pricing Data in Real-Time

Section 2(a)(13)(D) of the CEA authorizes the Commission to require registered entities “to publicly disseminate the swap transaction and pricing data.” With respect to all off-facility swaps, the Commission's proposal requires that reporting parties send swap transaction and pricing data to registered SDRs to publicly disseminate such data in real-time. With respect to swaps that are executed on a swap market, the Commission's proposal requires that swap markets publicly disseminate swap transaction and pricing data either through a registered SDR or a third-party service provider. Under the proposal, if a swap market sends the swap transaction and pricing data to a registered SDR, the swap market is responsible for ensuring that such data is sent in a timely manner for public dissemination. Alternatively, if a swap market sends the swap transaction and pricing data to a third-party service provider for the public dissemination of such data, the swap market does not absolve itself from or satisfy the requirement to publicly disseminate swap transaction and pricing data until such time as the third-party service provider actually disseminates such data. Indeed, under the alternative, a swap market must ensure that the third-party service provider publicly disseminates the data in the manner set forth in the proposal.

In considering different schemes of real-time public reporting requirements, the Commission also considered a “first touch” method of reporting whereby the swap dealer, MSP or swap market where a swap transaction occurred would have been required to real-time report the transaction by posting the transaction on its Internet Web site or through other electronic means. The Commission chose not to pursue a “first touch” method because it would likely lead to greater fragmentation of market data, increased search costs for market participants and potential concerns with the quality of the data that would be publicly disseminated.

The Commission requests comment on all aspects of the proposed rules, as well as comment on the specific provisions, issues and questions highlighted in the discussion in Section B below.

4. Proposed Effective Date and Implementation Schedule

The Dodd-Frank Act requires the Commission to promulgate rules to implement these provisions by July 15, 2011.

Proposed part 43 is designed to provide clarity as to the real-time reporting and public dissemination requirements with respect to all swap transaction and pricing data. The Commission acknowledges that the systems for reporting and public dissemination described in proposed part 43 may take a significant amount of time and resources to implement effectively. While the Commission is fully committed to implementing Congress' directive to require real-time public reporting of all swaps and will adopt final rules by July 15, 2011, participants will need a reasonable amount of time in which to acquire or configure the necessary systems, engage

and train the necessary staff and develop and implement the necessary policies and procedures to implement the proposed rules. The Commission's proposed rules provide that appropriate minimum block sizes will be published by registered SDRs beginning in January 2012.

Accordingly, it is anticipated that registered entities and registrants will have begun their compliance by that time.

See

Section 754 of the Dodd-Frank Act which states: “Unless otherwise provided in this title, the provisions of this subtitle shall take effect on the later of 360 days after the date of enactment of this subtitle or, to the extent a provision of this subtitle requires a rulemaking, not less than 60 days after publication of the final rule or regulation implementing such provision of this subtitle.”

See

discussion relating to proposed § 43.5(g)(4) below.

The Commission requests comment on what would be an appropriate implementation schedule (

i.e.,

effective date) for the final rules. In addition, the Commission requests specific comment on the following issues:

• How do commenters believe that an appropriate implementation schedule should be structured? Should there be a phased-in approach? Please provide specific examples.

• Do commenters believe that different types of reporting parties (

e.g.,

swap dealers, MSPs and end-users) should have different implementation timeframes? If so, why and what timeframes? If not, why and what timeframe?

• Do commenters believe that different types of execution (

e.g.,

SEF, DCM and off-facility) should have different implementation timeframes? If so, why and what timeframes? If not, why and what timeframe?

• How long would swap dealers, MSPs and end-users need to establish the appropriate connections to report off-facility swaps to registered SDRs? Please explain.

• How long after registration would registered SDRs need to accept and publicly disseminate swap transaction and pricing data in real-time? Please explain.

• Should there be different implementation timeframes for particular asset classes, markets or contracts? If so, what criteria should be used to select those asset classes, markets or contracts?

• Should the implementation timeframes for real-time reporting and public dissemination requirements for swaps and security-based swaps be coordinated?

• Should there be different implementation timeframes for the block trade and large notional swap rules explained in the discussion relating to proposed § 43.5 below?

B. Section-by-Section Analysis

1. Proposed Section 43.1—Purpose, Scope and Rules of Construction

The proposed rules apply to all swaps as defined in Section 1a(47) of the CEA and as may be further defined by Commission regulations. The categories of swaps described in Section 2(a)(13)(C) of the CEA account for all swaps, whether cleared or uncleared, and regardless of whether a swap is executed on a SEF, DCM or off-facility. The proposed rules apply real-time reporting requirements to SEFs, DCMs, SDRs and the parties of a swap, including registered or exempt swap dealers, registered or exempt MSPs and U.S.-based end-users.

The Commission requests comment generally on the scope of transactions covered by this part. In addition, the Commission requests specific comment on which parties to a swap should be covered by the reporting requirements in this part in order to enhance price discovery?

2. Proposed Section 43.2—Definitions

Proposed § 43.2 contains definitions for, inter alia, the following terms: “Affirmation”; “As Soon As Technologically Practicable”; “Asset Class”; “Confirmation”; “Execution”; “Public Dissemination” or “Publicly Disseminate”; “Real-Time Disseminator”; “Reportable Swap Transaction”; “Swap Instrument”; and “Third-Party Service Provider”.

Affirmation

Proposed § 43.2(b) defines “affirmation” as the process (electronically, orally, in writing or otherwise) in which the parties to a swap verify that they agree on the primary economic terms of a swap, but not necessarily all terms of the swap. The affirmation of the swap is only the agreement to the primary economic terms of the swap, as distinguished from the confirmation of a swap in which all of the terms of the swap are agreed to in writing to memorialize the agreement of all parties to the swap. Such confirmation legally supersedes any previous agreement of the parties.

Affirmation and execution can, but do not necessarily, occur at the same time. In either case, affirmation and execution always occur prior to the confirmation of a swap. One further distinction is that “affirmation”, as defined in the proposed rules, differs from “confirmation by affirmation”. Some confirmation service vendors (

e.g.,

Deriv/SERV, MarkitSERV) have used the term “affirmation” to describe the process by which one party to a swap (usually an end-user) electronically acknowledges its assent to complete swap terms submitted to the vendor by its counterparty (usually a dealer). This process allows for electronic confirmation even when one party to the swap does not have the systems necessary to submit swap terms to the vendor electronically. Upon such assent to complete swap terms, a swap is legally confirmed (

i.e.,

“confirmation by affirmation”). Parties that use a confirmation by affirmation process previously will have affirmed the primary economic terms of the trade and therefore executed the trade pursuant to the definitions in the proposed rules.

As Soon as Technologically Practicable

Section 2(a)(13)(A) of the CEA defines “real-time public reporting” to mean “to report data relating to a swap transaction, including price and volume, as soon as technologically practicable after the time at which the swap transaction has been executed.” “As soon as technologically practicable” and “executed” are not defined in the Dodd-Frank Act.

The terms “execution” and “executed” are discussed below.

The proposed rules provide definitions for “as soon as technologically practicable” and “executed”. Proposed § 43.2(d) defines the term “as soon as technologically practicable” to mean as soon as possible, taking into consideration the prevalence of technology, implementation and use of technology by comparable market participants. In defining “as soon as technologically practicable”, the Commission has considered that this term may have different interpretations for different parties to a swap (

i.e.,

swap dealers, MSPs and end-users), for different types of swaps (

e.g.,

energy swaps, credit default swaps, interest rate swaps, etc.) and for different methods of execution (

i.e.,

SEFs, DCMs and off-facility). Staff considered real-time reporting regimes that are currently in place, comments by market participants at external meetings, the discussions at the Roundtable and the potential costs to market participants, among other things. Cost, access to the latest technology and other factors may prevent some of the fastest, most efficient technology from being available to all market participants. Because of these factors, the Commission recognizes that what is “technologically practicable” for one party to a swap may not be the same as what is “technologically practicable” for another party to a swap.

The Commission requests comment on whether the term should account for other considerations not presently identified in the definition.

Asset Class

Proposed § 43.2(e) defines the term “asset class” to mean the broad category of goods, services or commodities underlying a swap. The asset classes include, but are not limited to, the following five major categories: interest rate, currency, credit, equity and other commodity.

In proposing these five major categories, the Commission considered market statistics that distinguish between those general types of underlying instruments, as well as market infrastructures that have been established for these five types of instruments. The interest rate asset class would encompass the underlying of any swap which is primarily based on one or more reference rates, such as swaps of payments determined by fixed and floating rates. The currency asset class would encompass the underlying of any swap that is primarily based on rates of exchange between different currencies, changes in such rates or other aspects of such rates including any swap that is a foreign exchange option. This category includes foreign exchange swaps defined in Section 1a(25) of the CEA. The credit asset class would encompass the underlying of any swap that is primarily based on one instruments of indebtedness, including without limitation any swap primarily based on one or more broad-based indices related to instruments of indebtedness and any swap that is an index credit default swap or a total return swap on one or more indices of debt instruments. The equity asset class would encompass the underlying of any swap that is primarily based on equity securities, including, without limitation, any swap primarily based on one or more broad-based indices of equity securities and any total return swap on one or more equity indices. The other commodity asset class would encompass the underlying of any swap not included in the credit, currency, equity or interest rate asset class categories, including, without limitation, any swap for which the primary underlying notional item is a physical commodity or the price or any other aspect of a physical commodity.

Proposed § 43.2(e) also provides that the Commission may determine other asset classes.

Proposed § 43.2(q) defines “other commodity” to mean any commodity that cannot be grouped in one of the other four asset classes (

i.e.,

interest rate, currency, credit, equity). Other commodities may include physical commodities (

e.g.,

natural gas, oil) but may also include non-physical commodities (

e.g.,

weather and property).

The Commission requests comment on the following issues related to the definition of asset class:

• Do commenters agree with the proposed asset class categories? If not, why? Should there be any additional categories of asset classes? Should any categories of asset classes in the proposed definition be changed or removed?

• Do commenters agree on the proposed method of allocating swaps among asset class categories? If not, why?

• Should the Commission classify cross-currency rate swaps as belonging to the interest rate asset class or to the currency asset class? Please explain.

• Should the asset class for other commodity be divided further (

e.g.,

agricultural commodity, energy commodity,

etc.

)? If so, how should it be divided?

Confirmation

Proposed § 43.2(g) defines the term “confirmation” to mean the consummation (electronically or otherwise) of legally binding documentation (electronic or otherwise) that memorializes the agreement of the parties to all terms of a swap. A confirmation must be in writing (whether electronic or otherwise) and must legally supersede any previous agreement (electronic or otherwise). A confirmation between parties to a swap may occur in various ways including via facsimile, via “confirmation by affirmation” and via electronic matching. A confirmation will contain all of the terms to a swap that have been agreed to between two parties, whereas an affirmation contains a subset of the terms of the confirmation.

Execution

As noted above, swap counterparties and reporting entities must report “as soon as technologically practicable after the time at which the swap transaction has been executed.”

Proposed § 43.2(k) defines “execution” as the agreement between parties to the terms of a swap that legally binds the parties to such terms under applicable law. An agreement may be in electronic form (

e.g.,

on a swap market or via instant message), oral (

e.g.,

over the phone), in writing (

e.g.,

a bespoke, structured transaction where documents are exchanged) or in some other format not contemplated at this time. Execution immediately follows or is simultaneous with the pre-execution affirmation of the swap. The Commission notes that the proposed definition of execution does not attempt to define what constitutes a legally enforceable contract, only that execution occurs if and when the parties have formed a legally enforceable contract (which is a matter to be decided by applicable law).

If pre-execution affirmation of the primary economic terms creates a legally enforceable contract under applicable law, then it would also constitute execution. If pre-execution affirmation does not create a legally enforceable contract, then execution would not have occurred at that stage.

Section 2(a)(13)(A) of the CEA.

Because contract law varies by jurisdiction, the time at which a legally enforceable contract is formed may differ based on the applicable state or local law.

Public Dissemination and Publicly Disseminate

Proposed § 43.2(r) defines “public dissemination” and “publicly disseminate” to mean publishing and making available swap transaction and pricing data in a non-discriminatory manner, through the Internet or other electronic data feed that is widely published and in a machine-readable format. The definition encompasses the non-delayed provision of such data to the public, including market participants, end-users, data vendors and news media.

Real-Time Disseminator

Proposed § 43.2(s) defines “real-time disseminator” to mean any registered SDR or third-party service provider that is responsible for accepting and publicly disseminating swap transaction and pricing data in real-time from multiple sources, in accordance with proposed part 43.

Reportable Swap Transaction

Proposed § 43.2(v) defines “reportable swap transaction” to mean any executed swap, novation, swap unwind, partial novation, partial swap unwind or such post-execution event that affects the price of a swap. A reportable swap transaction includes not only the execution of a swap contract, but also certain price-affecting events that occur over the “life” of a swap. The Commission believes novations and swap unwinds are events that clearly affect the price of the swap and, therefore, should be publicly disseminated in real-time. In addition to novations and swap unwinds, other price-affecting events over the life of a swap may be considered reportable swap transactions. For example, certain amendments that change the price terms of a swap may be subject to the real-time public reporting requirements. Further, the Commission recognizes that certain

market participants may enter into a swap and then immediately enter into an amendment to the swap that alters the price terms, thus reducing transparency and price discovery. The Commission believes that including such post-execution price-affecting events to be reportable for the purposes of real-time public reporting will enhance the transparency and price discovery attributes of swaps trading.

The Commission requests comments on other post-execution events that could affect price and that should be considered reportable swap transactions.

Swap Instrument

Proposed § 43.2(y) defines “swap instrument” to mean each swap in the same asset class with the same or similar characteristics. Under proposed § 43.5, discussed below, registered SDRs would determine the appropriate minimum block size based on the type of swap instrument. After a registered SDR sets the appropriate minimum block size for a swap instrument and groups a specific swap contract that is listed on a swap market into a category of swap instrument, a swap market that lists such swap contract would then reference such appropriate minimum block size when adopting the minimum block trade size for such swap. The Commission believes that it is appropriate to group particular swap contracts into various broad categories of swap instruments in determining the appropriate minimum block size.

The Commission is requesting general and specific comments on swap instruments, as described in the discussion of appendix A to proposed part 43 below.

Third-Party Service Provider

Proposed § 43.2(bb) defines “third-party service provider” to mean an entity, other than a registered SDR, that publicly disseminates swap transaction and pricing data in real-time on behalf of a swap market or, in the case of an off-facility swap where there is no registered SDR available to publicly disseminate the data in real-time, on behalf of a reporting party.

3. Proposed Section 43.3—Method and Timing for Real-Time Public Reporting

Section 2(a)(13) of the CEA does not provide an explicit method or timeframe in which swap transaction and pricing data must be reported to the public in real-time. Instead, Section 2(a)(13) of the CEA provides the Commission with authority to prescribe rules requiring: (1) The parties to a swap transaction (including agents of the parties) to report swap transaction and pricing data to the appropriate registered entity in a timely manner;

and (2) registered entities to publicly disseminate swap transaction and pricing data.

In addition, Section 2(a)(13)(B) of the CEA provides that the Commission is authorized to make swap transaction and pricing data available to the public in such form and at such times as the Commission determines appropriate to enhance price discovery. Accordingly, the Commission's proposal in § 43.3 sets out both the manner in which parties to a swap must report the swap transaction and pricing data to the appropriate registered entity, as well as the manner in which registered entities must publicly disseminate such data. In addition, proposed § 43.3 sets out requirements for: (1) The acceptable forms of media through which swap transaction and pricing data must be made available to the public; (2) the appropriate methods to cancel or correct erroneous or omitted data that has been publicly disseminated; (3) the hours of operation that swap markets and registered SDRs must maintain for the public dissemination of swap transaction and pricing data; and (4) the recordkeeping of data by swap markets and registered SDRs.

See

Section 2(a)(13)(F) of the CEA.

See

Section 2(a)(13)(D) of the CEA. As discussed below, the Commission's proposal requires registered entities to publicly disseminate swap transaction and pricing data “as soon as technologically practicable”.

See

Section 2(a)(13)(A).

i. Responsibilities of the Reporting Party To Report Data

As discussed above, Section 2(a)(13)(F) of the CEA provides that the parties to a swap (including agents of the parties to a swap) shall be responsible for reporting swap transaction information to the appropriate registered entity. In general, proposed § 43.3(a) provides that the “reporting party” to each swap transaction shall be responsible for reporting any reportable swap transaction to a registered entity as soon as technologically practicable.

Proposed § 43.2(w) defines “reporting party” to mean a party to a swap with the duty to report a reportable swap transaction to a registered entity. Under this proposal, the determination of who has this duty depends on whether the reportable swap transaction is executed on a swap market. For reportable swap transactions that are executed on a swap market, proposed § 43.3(a)(2)(i) provides that the requirement for parties to report the swap transaction and pricing data is itself satisfied by the act of execution on the swap market. The Commission believes that this approach should result in the timeliest and most efficient method of reporting swap transaction and pricing data, since swap markets by definition would have immediate access to the most accurate execution information related to each swap transaction (

e.g.,

information on the counterparties to the swap, date and time of execution, bid-offer information, final pricing information, whether the swap should be deemed a block trade,

etc.

). Proposed § 43.3(a)(2)(ii) recognizes that block trades may not be executed on a swap market, but would be effective pursuant to the rules of the swap market. For that reason, this section would require the reporting party to the block trade to report such trades to the swap market in accordance with the rules of the swap market and proposed § 43.5.

The Commission proposes to define “timely manner” to mean “as soon as technologically practicable”.

For off-facility swaps, proposed § 43.3(a)(3) provides that, except otherwise provided in proposed § 43.5, the reporting party must report (

i.e.,

transmit or otherwise electronically transfer) swap transaction and pricing data to a registered SDR as soon as technologically practicable. Once a reporting party has reported its swap transaction and pricing data to a registered SDR, the reporting party has satisfied its requirement to report pursuant to Section 2(a)(13)(F) of the CEA and this proposed part 43.

The Commission believes that advanced technologies presently exist through which a reporting party to an off-facility swap can send swap transaction and pricing data to a registered SDR as soon as technologically practicable. Through discussions with market participants, the Commission understands that many swaps are executed over the telephone and then inputted manually into electronic recording systems. The Commission believes that reporting parties should remain current with changes in technology and regularly update their technology infrastructure to decrease the time of transmission of swap transaction and pricing data to real-time disseminators.

Two examples of how reporting technology can improve over time are seen in the evolution of (1) the Financial Industry Regulatory Authority's (“FINRA”) Trade Reporting and Compliance Engine (“TRACE”), and (2) the reporting of over-the-counter (“OTC”) equity securities. Under the reporting rules for TRACE, the current maximum reporting time requirement for publicly reporting transaction and pricing data for corporate bonds is 15 minutes. FINRA staff has noted in meetings with

Commission staff that over 90% of its trades are reported within five minutes.

See

FINRA Rule 6730 (“Transaction Reporting”). Available at:

http://finra.complinet.com/en/display/display_main.html?rbid=2403&element_id=4402.

With respect to the OTC securities market, FINRA has recently reduced the reporting requirements for these securities to within 30 seconds of execution.

See

Securities Exchange Act Release No. 61819 (March 31, 2010), 75 FR 17806 (April 7, 2010 (Notice of Filing of Amendment No. 2 and Order Granting Accelerated Approval of File No. SR-FINRA-2009-061));

See also,

FINRA Rules 6282(a); 6380A(a) and (g); 6380B(a) and (f); 6622(a) and (f); 7130(b); 7230A(b); 7230B(b); and 7330(b).

The determination of which party to a swap will be deemed the reporting party for the purposes of proposed § 43.3(a) chiefly depends on the types of entities that are parties to the swap.

Specifically, proposed § 43.3(a)(3) provides that for off-facility swaps:

• If only one party is a swap dealer or MSP, the swap dealer or MSP shall be the reporting party.

• If one party is a swap dealer and the other party is an MSP, the swap dealer shall be the reporting party.

• If both parties are swap dealers, the swap dealers shall designate which party shall be the reporting party.

• If both parties are MSPs, the MSPs shall designate which party shall be the reporting party.

• If neither party is a swap dealer or an MSP, the parties shall designate which party (or its agent) shall be the reporting party.

Through discussions with market participants at the Roundtable and external meetings, the Commission believes that swap dealers and MSPs are more likely to have the infrastructure and resources available to report their swap transaction information to a registered SDR in a quicker period of time than parties to an end-user-to-end-user, off-facility swap. Indeed, the Commission recognizes that non-financial end-users do not frequently enter into swap transactions and may not have the technology readily available to report swap transaction and pricing data for the purposes of the real-time reporting requirements under Section 2(a)(13)(F) of the CEA, and therefore, may lead to longer reporting time periods from execution for such reporting parties.

The Commission understands that the requirement to report swap transaction and pricing data as soon as technologically practicable may increase costs for reporting parties as a result of such parties having to upgrade their technology infrastructures. Based on discussions with market participants, however, the Commission believes that technology solutions may develop, such as web portals and other Internet-based interfaces, which will aide reporting parties in complying with the requirements proposed in § 43.3(a) and reduce the cost burden associated with their compliance. In addition, the Commission believes that the total number of end-user to end-user swaps will be small and thus the costs imposed on end-users will likely be lower relative to the total number of swaps.

In addition, the Commission believes that increased transparency may lead to more robust price competition, thus decreasing bid-offer spreads in certain swap contracts and benefiting end-users.

The Commission's proposal with respect to off-facility swaps is consistent with the reporting requirements for the reporting of uncleared swaps to a registered SDR under Section 4r(a) of the CEA.

After consulting with market participants at the Roundtable and in meetings with market participants, the Commission believes that this consistency may reduce technology infrastructure costs for swap dealers and MSPs, particularly since swap dealers and MSPs will likely establish direct connectivity to registered SDRs to satisfy the reporting requirements for the reporting of uncleared swaps under Section 4r(a) of the CEA.

The requirements of Section 4r(a)(3) of the CEA are discussed in footnote 18 above.

In the event that no registered SDR exists or is available to accept and publicly disseminate swap transaction and pricing data, proposed § 43.3(a)(4) establishes a special rule for the real-time reporting of these swaps. Specifically, proposed § 43.3(a)(4) provides that the reporting party may report such data to a third-party service provider, which provides public dissemination services. Similar to the requirements placed on swap markets when such markets choose to publicly disseminate through a third-party service provider, the reporting party will be required to ensure that the swap transaction and pricing data is publicly disseminated in real-time.

The Commission requests comment related to the responsibilities of the parties to a swap to report swap transaction and pricing data. In addition, the Commission requests specific comment on the following issues:

• Should the Commission establish maximum timeframes in which reporting parties must report to a registered SDR that accepts and publicly disseminates swap transaction and pricing data in real-time (

e.g.,

as soon as technologically practicable but no later than five minutes)? If so, what should the maximum timeframes be and how should they be determined?

• Do commenters believe that the rules should require that any additional parties to a swap be the reporting party for a swap? If so, which parties and in which circumstances?

• Should the Commission's final rules address the reporting and public dissemination of swap transaction and pricing data for swaps, which are transacted between two non-U.S. persons? If so, how should the Commission's final rules address these situations?

• In off-facility swap transactions where a non-U.S. swap dealer or non-U.S. MSP transacts with a U.S.-based end-user, which party to the swap should have the obligation to report to a real-time disseminator? Are there other situations involving non-U.S. parties where this issue may arise? How should the Commission address these situations in its final rules?

• Should there be an alternative method of reporting and subsequently disseminating swap transaction and pricing data in real-time when no registered SDR is available to accept and publicly disseminate such data? If there is no registered SDR available and there is no third-party service provider available to accept and publicly disseminate data for a swap transaction, what should the real-time reporting requirement be for such transaction?

• Is there a better or more efficient alternative to have swap transaction and pricing data reported by a reporting party to a registered SDR for public dissemination in real-time? If so, what would that be?

ii. Responsibilities of Swap Markets To Publicly Disseminate Swap Transaction and Pricing Data in Real-Time

Section 2(a)(13)(D) of the CEA gives the Commission the authority to require registered entities to publicly disseminate swap transaction and pricing data.

Proposed § 43.3(b) provides the method and timeliness of public dissemination of swap transaction and pricing data. Proposed § 43.3(b) distinguishes the public dissemination requirement for swaps that are executed on a swap market versus those swaps that are executed off-facility.

Irrespective of the mode of

execution, the Commission sought to provide market participants with reasonable guidelines to report and publicly disseminate swap transaction and pricing data in real-time.

As noted above, Section 1a(40) of the CEA, as amended by Section 721(a) of the Dodd-Frank Act, defines “registered entity” to include SEFs, DCOs, DCMs and SDRs. The Commission has determined, however, not to apply the Section 2(a)(13)(D) requirement to DCOs because it believes that the value of timely public dissemination outweighs the benefit of waiting until a swap is presented to a clearing organization.

Block trades that are transmitted pursuant to a swap market's rules are addressed in proposed § 43.5.

With respect to reportable swap transactions that are executed on a swap market, proposed § 43.3(b)(1)(i) provides that a swap market shall satisfy its requirement to publicly disseminate swap transaction and pricing data by: (1) Sending, or otherwise electronically transmitting, swap transaction and pricing data to a registered SDR that accepts swaps for the particular asset class of reportable swap transactions; or (2) disseminating such data to the public through a third-party service provider operating on behalf of the swap market.

The Commission notes that a swap market that relies on a third-party service provider to disseminate swap transaction and pricing data, for example through a contractual agreement, remains responsible for compliance with the rules of proposed part 43.

As discussed immediately below, proposed§ 43.3(b)(2) prohibits a swap market or reporting parties from disclosing swap transaction and pricing data prior to sending such data to a real-time disseminator.

If a swap market sends swap transaction and pricing data to a registered SDR, proposed § 43.3(b)(1)(i) provides that such data must be sent as soon as technologically practicable after the swap has been executed. As a result of industry comments made during staff meetings and at the Roundtable, the Commission believes that technologies presently exist through which a swap market can send swap transaction and pricing data to a registered SDR almost instantaneously after execution of a reportable swap transaction.

Under the proposal, once the swap market has sent the swap transaction and pricing data to a registered SDR, the swap market will have satisfied its dissemination requirement.

See, e.g.,

Comments by Steve Joachim, Executive Vice President, Transparency Services, FINRA (“[T]he technology for collecting, aggregating, and disseminating [swap] data, assuming [the] use [of] current infrastructures * * * can allow [real-time public reporting] to work pretty efficiently.”) Roundtable Tr. at 277-78.

In contrast, proposed § 43.3(b)(1)(ii) provides that if a swap market sends swap transaction and pricing data to a third-party service provider, the swap market does not satisfy its requirement to publicly disseminate swap transaction and pricing data until such data is actually disseminated to the public. The Commission's proposal distinguishes between a registered SDR and a third-party service provider because the Commission would have oversight authority over a registered SDR, but not over a third-party service provider. This distinction would be especially important if, for example, a third-party service provider failed to publish swap transaction and pricing data in real-time. Under those circumstances, the Commission may have no authority over the third-party service provider to remedy the failure. Since the swap market is still obligated to publicly disseminate, the Commission may require the swap market to resolve the failure and publicly disseminate the swap transaction and pricing data through another third-party service provider or a registered SDR. Accordingly, the Commission would expect that a swap market that uses a third-party service provider to meet its public dissemination obligation should be vigilant in monitoring the timeliness and accuracy of the provider's publication of the swap market's swap transaction and pricing data.

Proposed § 43.3(b)(2)(i) prohibits swap markets or any reporting party to a swap from disclosing the swap transaction and pricing data before the real-time disseminator has publicly disseminated such data. The Commission believes that this prohibition will ensure that swap transaction and pricing data is disseminated uniformly and is not published in a manner that creates unfair advantages for any segment of market participants.

The proposed rules do allow for swap markets and swap dealers to provide their market participants and customers, respectively, with swap transaction and pricing data for swaps that they execute. In particular, proposed § 43.3(b)(2)(ii) provides that notwithstanding the non-disclosure provision in proposed § 43.3(b)(2)(i), a swap market may make swap transaction and pricing data available to participants on its market prior to the public dissemination of such data; however, the swap market must send such swap transaction and pricing data to a real-time disseminator at the same time as or earlier than it makes such data available to its market participants. Similarly, proposed § 43.3(b)(2)(iii) provides that notwithstanding the non-disclosure provision in proposed § 43.3(b)(2)(i), a swap dealer may make swap transaction and pricing data for off-facility swaps available to its customer base prior to the public dissemination of such data; however, such swap dealer must send such swap transaction and pricing data to a registered SDR at the same time as or earlier than it makes such data available to its customer base. In both cases, the data may only be made available to the particular market (

e.g.,

data for a swap executed on a particular SEF or DCM may only be shared with market participants on that SEF or DCM). The Commission believes that granting swap markets and swap dealers the flexibility to provide swap transaction and pricing data to its market participants or customer base, respectively, concurrent with reporting to the real-time disseminator may incentivize a rapid transmittal of data to the real-time disseminator.

The Commission requests comment generally on the responsibilities of swap markets to publicly disseminate real-time swap transaction and pricing data. In addition, the Commission requests comment on the following issues:

• Should the Commission establish a maximum timeframe in which swap markets must report swap transaction and pricing data to a real-time disseminator? If so, what is an appropriate maximum timeframe and why?

• Do commenters agree with the Commission's proposal that swap markets satisfy their public dissemination requirement by either sending to a registered SDR that accepts and disseminates swap transaction and pricing data or by publicly disseminating through a third-party service provider? If not, why? Should there be any other means by which a swap market can satisfy its public dissemination requirement? If yes, by what other means?

iii. Requirements for Registered SDRs

Sections 2(a)(13)(D) and 21(c)(4)(B) of the CEA provide the Commission with the authority to require registered SDRs to publicly disseminate swap transaction and pricing data in real-time. In particular, Section 2(a)(13)(D) provides that the Commission may require registered entities to publicly disseminate swap transaction and pricing data. Registered SDRs are registered entities as defined in Section 1(a)(40)(E) of the CEA. Section 21(c)(4)(B) of the CEA provides that an SDR must provide swap transaction information in such form and at such frequency as the Commission may require to comply with the real-time reporting requirements under Section 2(a)(13).

Pursuant to these authorities, the Commission is proposing § 43.3(c)(1) to require that registered SDRs that accept and publicly disseminate such data in real-time to comply with proposed part

49 of the Commission's regulations.

Under proposed part 49, a registered SDR may choose, but would not be required, to publicly disseminate swap transaction and pricing data in real-time for an asset class of swaps. Further, a registered SDR that accepts swap transaction and pricing data for public dissemination must publicly disseminate such data as soon as technologically practicable upon receipt of such data. Proposed § 43.3(c)(2) provides that if a registered SDR chooses to publicly disseminate swap transaction and pricing data in real-time for its specified asset class,

the registered SDR must accept and publicly disseminate swap transaction and pricing data for all swaps within such asset class. This requirement is intended to minimize the number of swaps that are not accepted by a registered SDR for public dissemination by enabling market participants to easily identify the SDR that accepts particular asset classes. In addition, proposed § 43.3(c)(3) provides that any registered SDR that accepts and publicly disseminates swap transaction and pricing data in real-time shall perform, on an annual basis, an independent review of its security and other system controls, in accordance with established audit procedures and standards, for the purposes of ensuring that the requirements of proposed part 43 are met.

In a forthcoming release, the Commission will propose part 49 of the Commission's regulations, which will set out the requirements that a registered SDR must satisfy in connection with its receipt and public dissemination of swap transaction and pricing data in real-time. Proposed part 49 of the Commission's regulations also will identify the necessary systems that registered SDRs must develop and maintain in order to receive and publicly disseminate such data.

In the forthcoming proposed part 49 of the Commission's regulations, registered swap data repositories will select the asset class(es) for which they accept swaps.

The Commission requests comment generally on the requirements for registered SDRs under proposed part 43. In addition, the Commission requests comment on whether it should require registered SDRs to publicly disseminate all real-time swap transaction and pricing data.

iv. Requirements for Third-Party Service Providers

If a swap market chooses to publicly disseminate swap transaction and pricing data through a third-party service provider, proposed § 43.3(d) provides that the swap market must ensure that the provider maintains standards that are, at a minimum, equal to those standards for registered SDRs described in proposed part 43 and the relevant provisions relating to real-time public reporting that will be proposed in part 49 of the Commission's regulations. In addition, this section provides that the swap market must ensure that the Commission has access to any swap transaction and pricing data, either through the swap market or directly through the third-party service provider.

v. Availability of Real-Time Swap Transaction and Pricing Data

Under proposed § 43.3(e), registered SDRs that report swap transaction and pricing data to the public in real-time, must make the data available and accessible in an electronic format that is capable of being downloaded, saved and/or analyzed. The Commission is proposing this provision to address the concern that a registered SDR may flash real-time swap transaction and pricing data to selected market participants with the technology to view such data without making such information available to the public and all market participants. Requiring registered SDRs to allow market participants and the public to download, save and/or analyze the real-time swap transaction and pricing data upon public dissemination, ensures equal access to real-time swap transaction and pricing data.

vi. Errors or Omissions

Proposed § 43.3(f)(1) sets out the process through which any errors or omissions in swap transaction and pricing data that were publicly disseminated in real-time shall be corrected or cancelled. Section 43.3(f)(1) sets out different processes depending on whether the data error or omission was discovered by the reporting party to the swap or the non-reporting party. Proposed paragraph (f)(1)(i) provides that if the non-reporting party becomes aware of an error or omission in the data reported for its swap, it shall promptly notify the reporting party of the correction. Proposed paragraph (f)(1)(ii) provides that if the reporting party becomes aware of an error or omission in the reported data, it is required to promptly submit the corrected data to the swap market or real-time disseminator. Proposed paragraph (f)(1)(iii) provides that if the swap market becomes aware of an error or omission in the swap transaction and pricing data reported for a swap, whether or not it received notification from the reporting party, the swap market shall promptly submit corrected data to the real-time disseminator. Proposed paragraph (f)(1)(iv) provides that a registered SDR that accepts and publicly disseminates swap transaction and pricing data in real-time must publicly disseminate any cancellations or corrections to such data as soon as technologically practicable after receipt or discovery of such cancellation or correction.

The proposal also seeks to prevent fraudulent dissemination for the purpose of distorting market pricing. Specifically, proposed paragraph (f)(2) of this section provides that reporting parties, swap markets and registered SDRs that accept and publicly disseminate swap transaction and pricing data in real-time are prohibited from submitting or agreeing to submit a cancellation or correction for the purpose of re-reporting swap transaction and pricing data in order to gain or extend a delay in publication or to otherwise evade the reporting requirements of proposed part 43.

Proposed paragraph (f)(3) of this section sets forth the appropriate method of canceling incorrectly published swap transaction and pricing data. Specifically, this paragraph provides that a real-time disseminator must cancel incorrect data that has been disseminated to the public by publishing a cancellation of the incorrect data in the format and manner described in appendix A to proposed part 43.

Proposed paragraph (f)(4) of this section sets forth the appropriate method of correcting erroneous or omitted swap transaction and pricing data. Specifically, this paragraph provides that a real-time disseminator must correct any erroneous or omitted data that has been disseminated to the public by first publicly disseminating a cancellation of the incorrect data and then publicly disseminating the correct data pursuant to the format described in appendix A to proposed part 43.

Depending on the situation, a cancellation may or not be followed by a correction. For example, a cancellation may occur in a situation where a clearinghouse does not accept a particular swap for clearing and, therefore, the swap may be busted and not require a correction. In another situation, one or more terms to a swap may be incorrectly reported by the party responsible for reporting the swap, and upon confirmation of the swap the error in the terms would be realized. Under the proposed rules, such a situation would require a cancellation of the original incorrectly reported data, followed by a correction with the correct swap transaction and pricing data. Whenever reporting a cancellation or correction, the real-time disseminator must report the data in the same form

and manner in which it was originally reported and include a date stamp reflecting the time of the original transaction, so that market participants and the public are aware of exactly which swap has been canceled or corrected.

vii. Hours of Operation

Since Section 2(a)(13) of the CEA requires that swap transaction and pricing data be reported and subsequently disseminated to the public in real-time, the Commission proposes that registered SDRs maintain certain hours of operation in order to comply with this legislative requirement. Proposed § 43.3(g)(1) requires registered SDRs that accept and publicly disseminate swap transaction and pricing data in real-time to be able to receive and publicly disseminate such data at all times, twenty-four hours a day.

Because the Commission recognizes that a registered SDR periodically may need to conduct maintenance on its electronic systems, proposed § 43.3(g)(2) would permit a registered SDR to declare special closing hours to perform such maintenance on an ad hoc basis. In addition, this section would require a registered SDR to provide advance notice of its special closing hours to market participants and the public. Further, proposed § 43.3(g)(3) provides that registered SDRs should avoid scheduling special closing hours during those periods when the U.S. markets and major foreign swap markets are most active. Proposed § 43.3(h) provides that during special closing hours, a registered SDR that accepts and publicly disseminates swap transaction and pricing data in real-time shall have the capability to receive and hold in queue information regarding reportable swap transactions pursuant to proposed part 43.

The Commission requests comment on the following questions regarding hours of operation:

• Should swap markets have requirements regarding hours of operation for the purposes of the real-time reporting requirements?

• Do the proposed requirements regarding hours of operation provide registered SDRs with sufficient flexibility to conduct the necessary maintenance on their electronic systems?

• Do commenters agree that registered SDRs that accept and publicly disseminate swap transaction and pricing data should have the capability to receive and hold such data in queue during special closing hours? If not, why and are there any alternatives?

viii. Recordkeeping Requirements

Proposed § 43.3(i) requires reporting parties, swap markets and registered SDRs to retain all data related to a reportable swap transaction (including large notional swaps and block trades) for a period of not less than five years following the time at which such reportable swap transaction is publicly disseminated. The Commission believes that it is necessary to retain such records in order to recreate transaction profiles for the purposes of trade practice surveillance and compliance. This requirement is separate and distinct from any other recordkeeping requirements under the Commission's regulations, including § 1.31.

Section 1.31 of the Commission's regulations generally provides, inter alia, all books and records required to be kept by the CEA or the Commission's regulations shall be kept for a period of five years from the date such records come into existence. In addition, § 1.31 provides that the records shall be readily accessible during the first two years of the five year period.

The Commission requests comment on the following questions regarding recordkeeping requirements:

• Do commenters believe that the proposed retention period for data related to reportable swap transactions is an appropriate period of time?

• Should the recordkeeping requirement be the same as § 1.31 of the Commission's regulations?

• What are the anticipated costs associated with storing such real-time swap transaction and pricing data for a longer period of time?

ix. Fees Charged by Registered SDRs

The Commission believes that the intent and purpose of Sections 2(a)(13) and 21 of the CEA is for registered SDRs to provide open and equal access to their data collection services for the purposes of real-time public reporting.

Consistent with open and equal access to registered SDR services, the Commission further believes that fees or charges adopted by a registered SDR for its data collection services for the purposes of real-time public reporting must be equitable and non-discriminatory. Proposed § 43.3(j) ensures that any fees or charges assessed on a reporting party or a swap market are consistent with the intent and purpose of Sections 2(a)(13) and 21. Proposed § 43.3(j) also prohibits a registered SDR from offering a discount based on the volume of swap transaction and pricing data reported to the registered SDR for public dissemination, unless such discount is offered to all reporting parties and swap markets.

Section 21 of the CEA sets forth the rules with respect to the business conduct standards and regulation of SDRs.

x. Consolidated Public Dissemination of Swap Data

The Commission recognizes the benefits of consolidating the public dissemination of swap transaction and pricing data in real-time.

During the Roundtable and in Commission external meetings, several market participants commented on their desire for the Commission to establish a consolidator in order to avoid fragmentation of the publication of swap transaction and pricing data. The Commission believes that a real-time reporting consolidator of swap transaction and pricing data could provide a comprehensive record of all swaps executed in chronological order. Additionally, a real-time reporting consolidator would create greater anonymity for the parties to transactions, particularly for swap dealers and MSPs.

The Commission considered the experience of the European Union under the Markets in Financial Instruments Directive (“MiFID”) and its Financial Services Action Plan, which went into effect on November 1, 2007 for OTC equity securities. Under this plan, the European Union broadened post-trade transparency requirements in European OTC equity securities markets. While MiFID required transparency, many market participants expressed concerns about the fragmentation of post-trade transparency under the MiFID regime, especially in OTC trading. The quality, disparate timing of publication and other barriers to consolidation of post-trade data were all highlighted as problems by the Committee of European Securities Regulators (“CESR”) in its Technical Advice report.

See

“CESR Technical Advice to the European Commission in the Context of the MiFID Review and Responses to the European Commission Request for Additional Information” (CESR/10-802, CESR/10-799, CESR/10-808, CESR/10-859), July 29, 2010. Available at:

http://www.cesr-eu.org/popup2.php?id=7003

Unlike the federal securities laws,

however, neither the CEA nor the Dodd-Frank Act grants the Commission explicit statutory authority to establish a real-time reporting consolidator.

The Commission requests comment on methods to encourage the consolidation of publicly disseminated swap transaction and pricing data.

See, e.g.,

15 U.S.C. 78k-1.

As mentioned above, FINRA oversees TRACE, which is a mechanism through which post-trade data regarding OTC secondary market securities in fixed income is reported. FINRA requires its broker-dealer member firms to report transactions to TRACE under an SEC-approved set of rules. Beginning in 2002, TRACE published transaction data on a consolidated tape. TRACE first published data on very liquid transactions and later phased-in additional products. More information on TRACE can be accessed at:

http://www.finra.org/Industry/Compliance/MarketTransparency/TRACE/index.htm

4. Proposed Section 43.4 and Appendix A to Proposed Part 43—Swap Transaction and Pricing Data To Be Publicly Disseminated in Real-Time

As noted above, Section 2(a)(13)(B) authorizes the Commission to prescribe regulations to make swap transaction and pricing data available in real-time in such form as the Commission determines appropriate to enhance price discovery. Proposed § 43.4 establishes the format in which such data will be publicly disseminated.

Proposed § 43.4(a) provides that swap transaction information shall be reported to a real-time disseminator so that the real-time disseminator can publicly disseminate swap transaction and pricing data in real-time in accordance with proposed part 43, including the manner and format described in appendix A to proposed part 43.

Appendix A to proposed part 43 provides a list of data fields for which a registered SDR must publicly disseminate swap transaction and pricing data. The descriptions and examples in appendix A to proposed part 43 are intended to provide guidance on an acceptable public reporting format and order for the data fields that are listed.

Proposed § 43.4 would not require that a reporting party or swap market provide swap transaction and pricing data in a particular format or that such data be anonymized prior to being sent to a real-time disseminator. Reporting parties and swap markets must, however, provide real-time disseminators with the information required to publicly disseminate the required data fields.

Proposed § 43.4(b) provides that any registered SDR that accepts and publicly disseminates swap transaction and pricing data in real-time shall publicly disseminate the information in the data fields described in appendix A to proposed part 43.

Proposed § 43.4(c) provides that a registered SDR that accepts and publicly disseminates swap transaction and pricing data in real-time may, as necessary, require reporting parties and swap markets to report such information in addition to the data described in appendix A to proposed part 43, in order to match the swap transaction and pricing data that was publicly disseminated in real-time to the data reported to a registered SDR or confirm that parties to a swap have reported in a timely manner pursuant to § 43.3. Such additional information shall not be publicly disseminated, on either a transactional or aggregate basis, by the registered SDR that accepts and publicly disseminates swap transaction and pricing data in real-time.

Proposed § 43.4(d) provides that the Commission may determine from time to time to amend the data fields described in appendix A. This section gives the Commission flexibility to add, modify or delete data fields as the Commission may deem appropriate and necessary to enhance price discovery and prevent the disclosure of the identities of the parties to any swap.

The Commission requests comment generally on the real-time reporting and public dissemination of the data described in appendix A to proposed part 43. In addition, the Commission requests comment on the following issues:

• Should the Commission specify the format and/or manner in which swap transaction and pricing data must be reported to a real-time disseminator?

• Should the Commission require that registered SDRs follow a specified order and format for the public dissemination of swap transaction and pricing data instead of providing examples and guidance?

i. Ensuring the Anonymity of the Parties to a Swap

Sections 2(a)(13)(C)(iii) and 2(a)(13)(E)(i) of the CEA emphasize the importance of maintaining the anonymity of the parties to a swap.

Proposed § 43.4(e)(1) prohibits the disclosure of swap transaction and pricing data that is publicly disseminated in real-time, which identifies or otherwise facilitates the identification of a party to a swap. This section further provides that a registered SDR may not report such data in a manner that discloses or otherwise facilitates the identification of a party to a swap.

The legislative history of the Dodd-Frank Act states that “regulators are to ensure that the public reporting of swap transactions and pricing data does not disclose the names or identities of the parties to the transactions.” 156 Cong. Rec. S5,921 (daily ed. July 15, 2010) (statement of Sen. Blanche Lincoln).

The Commission understands that this latter prohibition may lead to a loss of clarity with respect to the precise characteristics of swaps in certain circumstances.

Proposed § 43.4(e)(2) provides that a reporting party or a swap market must provide a real-time disseminator with a specific description of the underlying asset and tenor of a swap. The description must be general enough to provide anonymity, but specific enough to provide for a meaningful understanding of the swap. The Commission recognizes that it is conceivable that in situations where few parties trade a particular type of underlying asset, the description of that asset may inadvertently reveal the identity of one or more party(ies) to the swap.

See, e.g.,

comments from Steve Joachim, Executive Vice President, Transparency Services, FINRA (“I think we have to recognize that when we're talking about transparen[cy] in marketplaces that if we want to pursue the goal of transparency, that trading in transparent markets is different than trading in opaque markets and that you lose some anonymity no matter what happens. There will not be total confidentiality.”), Roundtable Tr. at 258.

For off-facility swaps, particularly other commodity swaps with very specific underlying assets, market participants may be able to infer the identity of a party or parties to a swap based on the description of the underlying asset.

For example, if the underlying asset to an off-facility swap is an energy commodity contract that has a specific delivery point at Lake Charles, Louisiana and such contract is only traded by two companies, then disclosing the underlying asset to the public would effectively disclose that one of those companies was entering into the trade. Proposed § 43.4(e)(2) allows reporting parties of off-facility swaps to publicly disseminate a description an underlying asset or tenor that by virtue of its real-time reporting would enable market participants to infer the identity of a party to the swap, in a way that does not disclose a party to a swap, but provides a meaningful understanding of the swap for the purpose of price discovery.

In the example, instead of saying a specific delivery point of Lake Charles, Louisiana, the reporting party may use a broader geographic region (

e.g.,

Louisiana, Gulf coast,

etc.

) under the Commission's proposal. The Commission believes that the issue of the description being too specific as to divulge the identity of a party to a swap

is more likely to arise when the underlying asset is a commodity. The Commission, however, believes that other asset classes and markets may have similar issues. In contrast, for those swaps that are executed on a swap market, the Commission believes that, since such contracts will be listed on a particular trading platform or facility, it will be unlikely that a party to a swap could be inferred based on the reporting of the underlying asset and therefore parties to swaps executed on swap markets must report the specific underlying assets and tenor of the swap.

See, e.g.,

comments from Peter Axilrod, Managing Director, New Business Development, The Depository Trust & Clearing Corporation (“I guess I'd like to make a plea for people to be careful with commodities. It's a little bit of a different market than what most people have been talking about. There are delivery points all over the country, there are load-serving entities, many of them all over the country, there are producers all over the country, and if you force people to specify a particular delivery point all the time, people are pretty much going to know who's making those trades. So, whatever you do in terms of what commodities data is reported publicly, you have to leave room for some flexibility in terms of anonymization [sic]. So, if the delivery points are too specific, you may never get much anonymizing [sic] of trades, but if you allow the geographic area to be expanded or to have some anonymity criteria and perhaps pick the set of the delivery points that meets the anonymity criteria, something like that needs to be done.”), Roundtable Tr. at 252-253.

It is important to note that the reporting requirement in this section is separate from the requirement to report swap transaction information to a registered SDR pursuant to Section 2(a)(13)(G) of the CEA. The CEA does not require swap transaction information be reported in a manner that protects anonymity since such information will not be publicly disseminated.

The Commission recognizes that swap markets may differ and that new types of swaps may emerge; therefore, the Commission is not proposing specific guidelines at this time for how an underlying asset should be described for the purposes of proposed § 43.4(e)(2). The specificity of the description will vary based on particular markets and contracts, but the proposed rules provide reporting parties with discretion on how to report swap transaction and pricing data. Proposed § 43.3(e)(2) and proposed part 23 of the Commission's regulations require that swap dealers and MSPs who do not disclose a specific description of an underlying asset and/or tenor because such disclosure would facilitate the identity of a party to a swap, must document why the specific information regarding the underlying asset and/or tenor was not publicly disseminated.

Further, swap dealers and MSPs must retain and provide such written justifications to the Commission pursuant to proposed part 23 of the Commission's regulations.

In a forthcoming release, the Commission will propose part 23 of the Commission's regulations, which will set out the internal business conduct standards for swap dealers and MSPs, including recordkeeping requirements in connection with real-time public reporting.

See id.

The Commission notes that the language found in Section 2(a)(13)(C)(iii) of the CEA, requiring that real-time public reporting be done “in a manner that does not disclose the business transactions and market positions of any person” is similar to the language found in Section 8(a) of the CEA. Section 8(a)(1) of the CEA provides, in relevant part, that “the Commission may not publish data and information that would separately disclose the business transactions or market positions of any person and trade secrets of or names of customers * * *.”

For the purposes of protecting the confidentiality of participants' business transactions or market positions as required under Section 8(a)(1) of the CEA, the Commission has historically created guidelines for various market information reports (

e.g.,

Bank Participation Reports (“BPRs”) and Commitments of Traders (“COT”) reports) that prevent market participants and the public from reverse-engineering aggregate data to determine the participants that submitted the data.

The Commission believes that the approach in the proposed rules regarding protecting the identities of parties to a swap under Sections 2(a)(13)(C)(iii) and 2(a)(13)(E)(i) of the CEA is consistent with the approach to confidentiality under Section 8(a)(1).

7 U.S.C. 12(a)(1).

The BPRs, which provide large-trader positions of banks participating in various financial and non-financial commodity futures, collect data for every market where five or more banks hold reportable positions. The BPRs break the banks' positions into two categories—U.S. Banks and Non-U.S. Banks—and show their aggregate gross long and short market positions for each type. However, in those markets where the number of banks in either category (U.S. Banks or Non-U.S. Banks) is less than five, the number of banks in each of the two categories is omitted and only the total number of banks is shown for that market. Available at:

http://www.cftc.gov/MarketReports/BankParticipationReports/ExplanatoryNotes/index.htm

. Similarly, the COT reports provide a breakdown of each Tuesday's open interest for markets in which 20 or more traders hold positions equal to or above the reporting levels established by the Commission. Available at:

http://www.cftc.gov/MarketReports/CommitmentsofTraders/AbouttheCOTReports/index.htm

The Commission requests comment generally on the protection of identities of the parties to the swap relating to real-time public reporting. In addition, the Commission requests comment on the following issues:

• Do commenters agree with the proposed method for real-time reporting of less specific information with regard to the underlying asset and tenor data fields in order to protect the anonymity of parties to a swap? If not, why?

• Should any additional data fields be allowed to have less specificity to ensure the anonymity of the parties to a swap? Should this proposed provision apply to all asset classes? If so, why?

• In what situations, if any, would it be appropriate for a reporting party to report, for the purposes of public dissemination, less specificity in the underlying asset(s) of a swap and how should such underlying asset(s) be reported? Please provide specific examples.

• Do commenters believe that it is appropriate to allow for less specificity than the month and year (as described in appendix A to proposed part 43) for the tenor of the swap? If not, why? If so, in what situations would it be appropriate for a reporting party to report, for the purposes of public dissemination, less specificity in the tenor of a swap and how should the tenor be reported? Please provide specific examples.

• What specific parameters for reporting less specificity in the underlying asset(s) and tenor of a swap should be applied to swaps in order to protect the identities of the counterparties?

• Should there be an indication to the public that a description of the underlying asset or tenor lacks specificity in order to protect the identities of the parties to the swap?

ii. Unique Product Identifiers

The Commission anticipates that unique product identifiers may develop for various swap products in various markets. Proposed § 43.4(f) provides that if a unique product identifier is developed and it sufficiently describes the information in one or more of the data fields for public dissemination in real-time, as described in appendix A, then such unique product identifier may be used in lieu of such data fields. If a swap does not have a unique product identifier, the swap transaction and pricing data must contain all of the appropriate product identification fields in appendix A to proposed part 43.

The Commission is considering the issue of unique product identifiers in two forthcoming rulemakings under proposed parts 45 and 49.

iii. Price-Forming Continuation Data

Proposed § 43.4(g) requires any swap-specific event (including, but not limited to, novations, swap unwinds, partial novations and partial swap unwinds) that occurs during the life of a swap and affects the price of such swap to be publicly disseminated (a “price forming continuation event”). The Commission does not believe that a price-forming continuation event includes the scheduled expiration of a swap, any anticipated interest rate adjustments, or any other event that does not result in a change to the price that would otherwise not have been known at the point of execution.

v. Reporting and Public Dissemination of Notional or Principal Amount

Proposed § 43.4(h) and (i) provide rules for the public reporting of the notional or principal amount for all swaps. Proposed § 43.4(h)(1) would require the reporting party to report the actual notional size of any swap, including large notional swaps, to the registered SDR that accepts and publicly disseminates such data. Proposed § 43.4(h)(2) would require a reporting party to transmit the actual notional size

of any block trade to a swap market. Further, a swap market must transmit the actual notional size for all swaps executed on or pursuant to its rules to a real-time disseminator. The Commission believes that the application of the rounding convention for notional or principal size, described in proposed § 43.4(i) should be done at the point of public dissemination (as opposed to the point at which it is reported to real-time disseminator) since this timing would provide for a more efficient audit trail of the swap.

Proposed § 43.4(i) provides that for all swaps the notional or principal amount that must be reported pursuant to proposed § 43.4 and appendix A to proposed part 43 should be rounded pursuant a specific rounding convention. Specifically, proposed § 43.4(i) provides that if the notional or principal amount of a swap is:

• Less than one million, round to the nearest 100 thousand;

• Less than 50 million, but greater than one million, round to the nearest million;

• Less than 100 million, but greater than 50 million, round to the nearest 5 million;

• Less than 250 million, but greater than 100 million, round to the nearest 10 million; and

• Greater than 250 million, use “250+”.

For example, if the notional size of a swap is $575 million, the notional size that would be reported by a reporting party to a swap market (assuming such swap is a block trade) would be $575 million. The swap market would then report the notional amount of $575 million to a real-time disseminator and the real-time disseminator would publicly disseminate the notional amount for such block trade as “$250+”. By reporting the notional or principal transaction amount pursuant to the rounding convention set forth in proposed § 43.4(i), parties to swaps, particularly those swaps that are of a large notional size, would be given a greater amount of anonymity.

The Commission requests comment generally on all aspects of the proposed rules relating to the reporting and public dissemination of notional or principal amount. In addition, the Commission requests specific comment on the following issues:

• Do commenters agree with the proposed rounding convention for public dissemination of large notional or principal amount provided in proposed § 43.4(i)? If not, why and provide alternatives?

• Would this rounding convention be appropriate for all swaps? For example, would this apply to swaps with an underlying asset that is a physical commodity with a specific delivery point? If not, why and what additional rounding convention may be needed?

• Does the rounding convention for reporting notional and principal transaction amounts in proposed § 43.4(i) help to protect the anonymity of the parties to a swap?

• Should the actual notional or principal amount be publicly disseminated at a later time?

• Should registered SDRs publish the aggregate volume for each category of swap instrument on a daily basis? If so, why? If not, why not?

• Would the daily publication of aggregate volume of swap instruments be useful to market participants and the public?

v. Appendix A to Proposed Part 43

The Commission anticipates that real-time swap transaction and pricing data may be publicly disseminated by multiple real-time disseminators in the same asset class. In order to reduce the effects of fragmentation and increase consistency both within an asset class and between asset classes, the Commission is proposing that the information in the data fields in appendix A to proposed part 43 be publicly disseminated. In addition, the Commission is providing proposed guidance on the order and format of reporting swap transaction and pricing data.

Additionally, the Commission believes that the public dissemination of standardized data should reduce the search costs to the public and market participants, increase consolidation of real-time swap transaction and pricing data and promote post-trade transparency and price discovery.

While appendix A to proposed part 43 attempts to provide consistency in describing which real-time data fields must be publicly disseminated, the Commission anticipates that certain fields will be easier to standardize than other fields. For example, it should be easy to standardize the format for an execution time-stamp across all swap transactions; whereas it may be more difficult to achieve standardization when describing an underlying asset. The Commission anticipates that, as markets develop over time, real-time disseminators and market participants may develop a form of standardization for certain data fields in certain asset classes.

In developing the Commission's proposal, Commission staff considered technical advice reports from CESR in the context of MiFID. In those reports, CESR concluded that market participants in the equities markets are not delivering consolidated data to the market in a standard format as a result of the “inadequate quality and consistency of the raw data itself, the inconsistencies in the way in which firms report it for publication, and the lack of any formal requirements to publish data through bodies with responsibilities for monitoring the publication process.” Committee for European Securities Regulators, “CESR Technical Advice to the European Commission in the Context of the MiFID Review—Equity Markets,” CESR/10-802, July 29, 2010. Available at:

http://www.cesr-eu.org/popup2.php?id=7004

See also,

http://www.cesr-eu.org/popup2.php?id=7003

See id.

While real-time disseminators must disseminate swap transaction and pricing data to the public, the reporting parties and swap markets must provide the real-time disseminators with, at a minimum, the relevant information needed to report the data fields described in appendix A to proposed part 43. As discussed above, a real-time disseminator that is a registered SDR may require a reporting party or a swap market to report additional information to the information necessary for public dissemination. Since all swap data must be sent to a registered SDR pursuant to Section 2(a)(13)(G) of the CEA and forthcoming Commission proposals, and an SDR may be a real-time disseminator, as previously discussed, the proposed rules provide that a registered SDR that is a real-time disseminator may require additional information to match the real-time swap transaction and pricing data to data reported to the registered SDR or confirm that parties to a swap have reported in a timely manner pursuant to Section 2(a)(13)(F) of the CEA. Such additional information requested by a registered SDR may include a transaction identification code, the names of the parties to the swap, or such other information as may be necessary.

As mentioned above, proposed § 43.4(b) would require that the information in any data field listed in appendix A to proposed part 43 to be publicly disseminated by a registered SDR or swap market through a third-party service provider to the extent that such data field captures a term of the reportable swap transaction. In many cases, several data fields listed in appendix A to proposed part 43 will not be applicable to a particular reportable swap transaction. To the extent that a data field is not a term of the swap, such field need not be reported and should be left blank. Appendix A to proposed part 43 also provides specific examples of how the reporting of a particular field should look (both in form and in order) when disseminated to the public.

Table A1 of appendix A to proposed part 43 provides that the following data fields be reported to the public in real-time.

Cancellation.

This data field reports the swap transaction and pricing data that was incorrectly or erroneously reported and is therefore being canceled. Any cancellations must also contain a date stamp of the original swap, even if such date stamp was not originally reported, followed by the full swap transaction and pricing data that is being canceled (including the original time-stamp of execution). It must be made clear to the public exactly which transaction is being reported so that the public can easily disregard such swap transaction and pricing data. A cancellation does not have to be corrected; however, any corrections must first be canceled. Any such cancellation must be done in accordance with proposed § 43.3(f).

Correction.

This data field reports the swap transaction and pricing data that is being reported is a correction to real-time swap transaction and pricing data that has been incorrectly publicly disseminated. Any corrections must also contain a date stamp to indicate the date of the initial swap that is being corrected, even if such date stamp was not originally reported, and the time-stamp must indicate the time of execution of the swap, not the time of the correction. Providing the date and original time-stamp of the swap will allow the public to easily replace the incorrect data. Any reportable swap transaction for which there are corrections to real-time swap transaction and pricing data must first be canceled prior to the correction, so that the public is aware of which data is being corrected. Any such correction must be done in accordance with proposed § 43.3(f).

Date stamp.

This data field reports the date of execution of the swap (if not the same day or a correction). This data field need only be publicly disseminated if the swap that is being reported was executed on a day other than the current day or if the swap transaction or pricing data is a cancellation or correction to previously real-time reported swap transaction and pricing data.

Execution time-stamp.

This data field reports the time of execution of the swap. The reporting party provides the execution time-stamp of the swap. The execution time-stamp is the only time-stamp that will be publicly disseminated.

Cleared or uncleared.

This data field reports whether a swap is cleared through a DCO, which may affect the price of the swap. For cleared swaps, the specific DCO that clears the swap will not be listed. In consideration of protecting the identities of the parties to the swap, the Commission does not believe that the specific DCO through which a swap is cleared must be reported to the public.

Indication of other price-affecting term (non-standardized swaps).

This data field reports whether there are other non-standard terms to the swap that materially affect the price of the swap. This indicator signals to market participants that there may be unreported terms of the contract that affect the price. Any reporting of bespoke swap transactions must include this indicator, since in these transactions there are other terms or factors that materially affect the price of the swap and are otherwise not included in the required fields for real-time public reporting found elsewhere in appendix A to proposed part 43.

Block trades and large notional swaps.

This data field reports whether the swap is a block trade or large notional swap. This data field does not, however, make a distinction between block trades and large notional swaps, since the execution venue data field will reveal that information.

Execution venue.

This data field reports where the swap was executed. The reporting party must indicate whether the swap was executed on a swap market or whether such swap is an off-facility swap. This data field assists the public in understanding the other data fields that are being reported. In consideration of protecting the identities of the parties, the Commission does not believe that the specific swap market on which the swap was executed need be publicly disseminated. Similarly, the Commission does not believe that a distinction need be made between those swaps executed on a SEF and those executed on a DCM.

Swap instrument.

This data field must be reported only if a trade is a block trade or a large notional swap. Large notional swaps must refer to an existing swap instrument that is posted by a registered SDR and has an appropriate minimum block size associated with such instrument. The parties to a swap must use the appropriate minimum block size of the swap instrument when determining if a swap constitutes a large notional swap. Swap markets, in setting the minimum block trade size for a particular listed swap, must reference the appropriate minimum block size for the category of swap instrument within which the particular listed swap is included. A swap market will set a minimum block trade size for a listed swap based on the appropriate minimum block size for the relevant category of swap instrument as calculated by the SDR. Proposed § 43.5 provides rules on block trades and large notional swaps, including the determination of minimum block trade sizes. The reporting of the swap instrument data field provides market participants and the public with an understanding of the type of swap instrument for which a block trade is occurring.

The Commission believes that within each asset class there should be certain criteria that are used to determine a category of swap instrument. For example, swaps in the interest rate asset class may be considered the same swap instrument if they are denominated in the same major currency (or denominated in any non-major currency considered in the aggregate) and if they have the same general tenor.

With regard to tenor, the Commission believes that tenors may be grouped into ranges based on maturity date (

e.g.,

short, intermediate and long). For example, a single category of swap instrument may be “U.S. dollar interest rate swaps in a short maturity bucket, including swaps, swaptions, inflation-linked swaps, etc. and all underlying reference rates.” Similarly, swaps in the “other commodity” asset class may be considered the same swap instrument if they have the same underlying asset, which generally would include all swaps whose economic terms relate to the same underlying product (

e.g.,

oil, natural gas, heating oil, gold,

etc.

). In contrast, the Commission believes that for swaps under the Commission's jurisdiction in the credit or equity asset classes all swaps within each asset class can be considered to be the same swap instrument. The swaps in the credit and equity asset class will be broad-based or on indexes and such swaps can likely be grouped together for purposes of determining the appropriate minimum block size. In the currency asset class, swap instruments may be defined by major currency pair, not by whether a major currency is one of the currencies involved in the swap.

Major currencies are those of the United States, Japan, the United Kingdom, Canada, Australia, Switzerland, Sweden and the European Monetary Union.

See

§ 15.03 of the Commissions regulations.

The Commission requests comment generally about swap instruments. In addition the Commission requests comment on the following specific issues:

• What criteria for each asset class should a registered SDR consider in determining if a swap falls within a

particular grouping of swap instrument? Specifically, what criteria should be used to classify a swap instrument and how do those criteria differ by asset class? What particular considerations should apply to swaps in interest rate, equity, credit, currency and other commodity classes? Who should determine the categories of swap instrument?

• How broad or narrow should the categories of swap instruments be for each asset class? Do commenters believe that the appropriate minimum block size should be determined based on particular types of swap contracts and not on categories of swap instruments? If so, why?

• Should certain asset classes have additional or fewer criteria in determining a swap instrument? If so, what asset classes and what criteria?

• Should a registered SDR apply any other criteria to the other commodity asset class to decide whether a swap falls within a particular type of swap instrument? How should the underlying asset be grouped for the other commodity asset class?

• Is it an appropriate approach to group tenors for swaps in the interest rate asset class into ranges (

e.g.,

short-term, intermediate-term and long-term)? What should be the appropriate ranges of tenor or maturity date for each of these ranges? Should there be tenor ranges for other asset classes?

• Are there any other currencies other than those described in § 15.03 of the Commissions regulations that the Commission should consider as a major currency? If so, which currencies and why?

10.

Start date.

This data field reports the day on which the contractual provisions of a swap commence or become effective. The Commission recognizes that the start date may be different than the execution date. The Commission also recognizes that the markets may develop such that swaps traded on swap markets become standardized to the point where the start date is embedded or understood by a unique product identifier. For example, the start date for a particular swap may always be the day following execution (

i.e.,

T+1), and such information could be captured by simply identifying the product through a unique product identifier. If the markets evolve in such a manner, then this data field may not be necessary to report for these swaps. Nonetheless, the start date must always be provided in a manner that is apparent to the public.

11.

Asset class.

This data field provides a general description of the asset class for a swap, as defined in proposed § 43.2(e). This data field will allow the public to easily compare swaps within an asset class and to easily identify the type of swap that is being reported. Swaps within an asset class would have broadly similar characteristics.

12.

Sub-asset class for other commodity.

This data field provides greater detail as to the type of other commodity that is being reported. The Commission realizes that there may be vast differences in the types of products that fall under a particular asset class. For this reason, a sub-asset class should be reported for other commodities so that the public can easily understand similar types of swaps. Such sub-asset classes may include, but are not limited to, specific energy, weather, precious metals, other metals, agricultural commodities, etc.

13.

Contract type.

This data field reports the specific type of swap that has been executed. This data field provides greater transparency and price discovery to market participants and the public, as knowledge of the contract type will allow the public to understand the swap transaction and pricing data that is being reported. The Commission has identified four broad categories of contracts that may be entered into: swaps, swaptions, forwards and stand-alone options. These categories may be further defined by the contract sub-type data field discussed immediately below.

14.

Contract sub-type.

This data field provides more detail on the type of contract specified in the contract type data field. The Commission envisions that there will be many contract sub-types. Such contract sub-types may include, for example, basis swaps, index swaps, broad-based security swaps and basket swaps. Specific option types and other information about options are covered by the options fields found in Table A2 to appendix A to proposed part 43.

15.

Price-forming continuation data.

This data field describes whether the information that is being reported is a price-affecting event to an existing swap. Such events may include novations, partial novations, swap unwinds and partial swap unwinds as well as other price-forming events that may occur following the execution of the swap. Such other events may also include amendments to the swap that have a specific affect on the price of the swap.

16.

Underlying asset 1 and underlying asset 2.

These data fields describe the specifics of the swap and help the public evaluate the price of the swap transaction. It is likely that each leg of a swap (

i.e.,

the fixed and the variable) will have an underlying asset that should be reported as a separate field. If there are more than two underlying assets, all underlying assets should be real-time reported and publicly disseminated. The Commission is not providing a specific format for all underlying asset fields, but the description of each underlying asset should be in a format that is commonly used by market participants. The Commission encourages reporting parties and real-time reporting disseminators to consult with one another to determine consistent ways of reporting similar underlying assets. If a standardized industry abbreviation exists for a particular underlying asset, such abbreviation should be used to describe the underlying asset. Whenever possible, alphabetical abbreviations should be used, including roman numerals; provided, however the underlying asset must be reasonably apparent to the public (

e.g.,

six-month LIBOR could be represented as VIL, 10-year Treasury could be represented as TX, etc.). Further, if a unique product identifier adequately captures the underlying asset, the underlying asset field may not need to be reported.

17.

Price notation and additional price notation.

These data fields report the price of the swap. These fields should include the total or net of any premium that is associated with a party's requirements under the swap. For example, if Party A's contractual requirements are linked to a 10-year Treasury note and Party B's requirements are linked to three-month LIBOR, the price notation should be the rate of 10-year Treasury note compared to three-month LIBOR (

e.g.,

2.5).

The Commission recognizes that a number of different pricing conventions currently exist across swap transactions and even among market participants for similar swap transactions. Nevertheless, the Commission believes that standardizing of pricing conventions will result in greater price transparency. In order to promote such standardization, it becomes important to define what “pricing” means for swaps. Notional or principal amount is the amount on which payment rates are calculated and is not the actual amount or units exchanged in most cases. Payments under the swap are based on what the market refers to as “legs” and what the Commission refers to as “underlying assets” in this proposed rulemaking. The additional price notation would be necessary in such instances where there are multiple premiums yields, spreads or rates are characteristics of the swap. It is for this reason that the proposed rules require

the additional price notation to include, inter alia, front-end payments, back-end payments, mid-cycle flat payments, collateral and margin. All of the elements to additional price notation must be represented in this field as a single number, relative to the difference in payments between the underlying assets of the swap.

In the example above, if Party A's requirement is tied to the 10-year Treasury note yield and Party B's requirement is linked to three-month LIBOR and Party B is also required to post a back-end payment of $100,000, then the price notation would be the rate of 10-year Treasury note compared to three-month LIBOR (

e.g.,

2.5). The additional price notation might be calculated to be +0.05, because in this example, the net present value of the back-end payment of $100,000, as applied to the exchange of payments within the swap, would be equal to +0.05. These two data fields provide the public and market participants with an easily accessible and uniform means of understanding the price at which the parties to a swap have reached an agreement regarding the swap's payment streams.

18.

Unique product identifier.

This data field, if available, describes a standardized swap. If a unique product identifier is available for a particular product, it may be reported in lieu of reporting other identifying fields including, but not limited to, the underlying asset, asset class, contract type, contract sub-type and start date, so long as such fields are adequately described and apparent to the public. The Commission believes that the markets will evolve to a point where the use of such unique product identifiers will increase transparency and promote price discovery across real-time disseminators. The Commission envisions unique product identifiers will be uniform across different swap markets.

19.

Notional currency 1 and notional currency 2.

This data field is needed if the notional or principal amounts are referenced in terms of a currency. The currency field may be reported in a commonly-accepted code. For example, U.S. dollars may be reported with the ISO 4217 currency code “USD”.

The notional currency 1 field should refer to the notional or principal amount 1 field, while the notional currency 2 field, if applicable, should refer to the notional or principal amount 2 field. If there are more than two notional or principal amounts that require a notional currency field, then these fields should be reported in a similar manner.

The International Organization for Standardization (“ISO”) provides a list of currency and funds names that are represented by both a three-letter alphabetical and a three-number numerical code (the “ISO 4217” code list), which is available at:

http://www.iso.org/iso/support/currency_codes_list-1.htm.

20.

Notional or principal amount 1 and notional or principal amount 2.

This data field is needed to identify the size or amount of the swap transaction. The notional amount may be reported in a currency and if so, the currency must be disclosed and made easily identifiable to the public. Such disclosure can be done by reporting the notional currency field with respect to the notional amount that requires such information. If a principal amount is in units, then a currency description does not need to be reported. Appendix A to proposed part 43 contemplates the potential for two or more notional or principal amounts. When a swap has more than two notional or principal amounts, then all such amounts must be reported and made easily identifiable by reporting parties and real-time reporting disseminators. The notional or principal amount for swaps should be reported pursuant to proposed § 43.4(h) and (i). Each notional or principal amount (if there is more than one) should be labeled with a number (

e.g.,

1, 2, 3, etc.), such that the number corresponds to the underlying asset for which the notional or principal amount is applicable.

21.

Payment frequency 1 and payment frequency 2.

This data field is needed to assist in understanding the price of a swap. It represents the frequency at which payments will be made for a party's contractual requirements under a swap. It is possible that the payment frequency may be the same for both parties to a swap; however, the payment frequency also may be different. If there is a difference, the payment frequencies must be reported for each requirement under the swap. The format for payment frequency should be consistent and may be reported as a numerical character followed by a letter.

For example, if payments are to be made every two weeks, then “2W” may be reported in this field; if payments are to be made every year, then “1Y” may be reported, etc. Each payment frequency (if there is more than one) should be labeled with a number (

e.g.,

1, 2, 3,

etc.

), such that the number corresponds to the underlying asset for which the payment frequency is applicable.

Such period descriptions may be described as follows: daily (D), weekly (W), monthly (M) and yearly (Y).

22.

Reset frequency 1 and reset frequency 2.

This data field is needed to assist in understanding the price of a swap. It represents the frequency that a price for an underlying asset may be adjusted. It is possible that there is no reset frequency, that the reset frequency is the same for both underlying assets or that the reset is different for both underlying assets. If different, the reset frequencies must be reported for each underlying asset. The format for reset frequency must be consistent and may be a numerical character followed by a letter.

For example, if adjustments are to be made every two weeks, then “2W” may be reported in this field, if adjustments are to be made every year, then “1Y” may be reported, etc. Each reset frequency (if there is more than one) should be labeled with a number (

e.g.,

1, 2, 3,

etc.

), such that the number corresponds to the underlying asset for which the reset frequency is applicable.

See id.

23.

Tenor.

This data field is needed to describe the duration of a swap and when a swap will terminate, mature or end. To protect the anonymity of the parties to a swap, the tenor field should only be reported as the month and year that the swap terminates, matures or ends. Such description may use the three character alpha-numerical format that is used in describing futures contracts.

For example, if a swap ends on March 15, 2020, the tenor may be reported as “H20”.

Futures month symbols are as follows: January (F), February (G), March (H), April (J), May (K), June (M), July (N), August (Q), September (U), October (V), November (X) and December (Z).

Table A2 of appendix A to proposed part 43 provides the following data fields to be publicly disseminated in real-time for options, swaptions and swaps with embedded options, if applicable to a swap. If a swap has more than one embedded option or swaption provision, then all such embedded options or swaptions should be real-time reported to the public in the same manner.

Embedded option on swap.

This data field is needed to describe whether the data listed in the option fields is an option that is embedded in the price of the swap. Proposed § 43.2(i) defines “embedded option” as any right, but not an obligation, provided to one party of a swap by the other party to the same swap that provides the party in possession of the option with the ability to change any one or more of the economic terms of the swap as they were previously established at confirmation (or were in effect on the start date). By requiring a separate field for embedded options on swaps, market participants and the public will be able to compare prices across the same or

similar swaps. The Commission believes that requiring this field will increase transparency and price discovery across the swap markets, as it will allow for the easy comparison of price by market participants and the public. Further, the Commission does not wish to see market participants wasting resources to try to avoid transparency by adding embedded options to otherwise standardized swap contracts. If the Commission did not require separate reporting of the embedded option field, it would be possible for market participants to attach worthless options to a swap in order to avoid real-time public reporting the swap in the same format as a standardized swap that does not have an embedded option.

Option strike price.

This data field reports the level or price at which a party to a swap may exercise an option. The Commission recognizes that for some option types, such as collars, strangles and condors, it will be necessary to report two or more prices in this field. This data field is the first field that would be reported for options and real-time disseminators may choose to place an “O” prior to the strike price. After the “O”, the level or price should follow immediately thereafter. For example, an option or swaption with a strike price of $25 should be real-time publicly reported as “O25”.

Option type.

This data field reports the type of option. The option type is important because it clarifies how the buying or selling of the asset is to be transacted between two parties. To promote standardization, this data field should be reported from the perspective of the party to the swap associated with underlying asset 1. The Commission recognizes that there are several different types of options, and has tried to identify some of the more common option types and their suggested two-character alphabetical descriptors in Table A2 of appendix A to proposed part 43. The Commission intends for the list of options in Table A2 to promote consistency and transparency across reporting parties and real-time disseminators. Some examples of option types include caps, collars, floors, puts, calls, pay fixed versus floating, receive fixed versus floating, straddles, strangles and knock-outs.

Option family.

This data field reports the family associated with the option. The option family is important because it identifies the period of time over which an option may be executed. The Commission recognizes that there are several different types of option families, and has tried to identify some of the more common option families and provided suggested two-character alphabetical descriptors in Table A2 of appendix A to proposed part 43. The Commission intends for the list in Table A2 to promote consistency and transparency across reporting parties and real-time disseminators. Some examples of option families include American, Bermudan, European and Asian.

Option currency.

This data field is needed to explain the currency for the option that is being reported. If applicable, the option currency field shall refer to both the option premium field and the option strike price.

Option premium.

This data field reports the purchase price for the option at the time of execution of the swap. This number represents the total additional cost of the option as a numerical value and is broken out separately from the price notation and additional price notation fields to allow for an easier comparison of a swap with an option to similar swaps that do not include an option.

Option lockout period.

This data field reports the time at which an option first can be exercised and thus, assist them in evaluating the price of an option. The option lockout date should be reported in the year and month format used in futures markets.

This field most often will be needed for European style options and other options where the start date for the requirements to a swap with an embedded option may be different than the date that an embedded option is available for execution. The option lockout period should be reported in the year and month format used in futures.

See id.

Option expiration.

This data field reports when an option can no longer be exercised. This data field will assist the public and market participants in evaluating the price of an option. In most cases, this data field can be omitted, as a standard option would expire at the same time as the swap contract to which it is linked. The option expiration should be reported in the year and month format used in futures markets.

v. Examples To Illustrate the Public Reporting of Real-Time Swap Transaction and Pricing Data

The Commission envisions that the reporting of the data fields in appendix A to proposed part 43 may eventually be reported in the form of a consolidated ticker, particularly for the more standardized swaps that are traded on swap markets. Additionally, the Commission believes that when unique product identifiers emerge they will be publicly disseminated, increase uniformity and transparency across real-time disseminators and ultimately lead to greater transparency and price discovery. Below, the Commission has set out two examples of how real-time public reporting of swap transaction and pricing data may evolve as consolidation and standardization develops in particular asset classes and markets.

Example 1

On Friday, February 4, 2011, Bank X enters into a new plain vanilla 10-year fixed versus floating interest rate swap with Bank Y, for a notional amount of $10 million U.S. dollars. The swap is scheduled to start on Tuesday, February 8, 2011 (note: start dates are usually 2 business days later for interest rate swaps). Bank X is the payer of the fixed leg of the swap and is obligated to pay a fixed rate of 2.53% on the notional amount for the ten-year tenor of the swap. Bank Y is the payer of the floating leg of the swap and is obligated to pay the prevailing three-month LIBOR on the $10 million notional amount. The first LIBOR payment will be based upon the three-month LIBOR rate for February 4, 2011 with the rate reset on a quarterly basis going forward. This interest rate swap is plain vanilla with both banks using the same day count convention, payment currency and notional value for both of the underlying assets to the swap.

Bank X and Bank Y have no additional premiums or payments under the terms of the swap. In this example, the reset and payment frequency for the fixed-rate are semi-annual. The reset and payment frequency for the floating rate (

i.e.,

three-month LIBOR) are quarterly. The parties' requirements under the swap for both the fixed leg and floating leg are scheduled to mature on Monday, February 8, 2021. Bank X and Bank Y are both members in good standing with a SEF named “Xeqution Co.” and use a DCO named “ClearitAll”.

Field

Description

Execution time-stamp

16:20:47

Cleared or uncleared

C (

note:

the name of DCO is not reported)

Execution Venue

SWM (

note:

the name of SEF is not reported)

Start date

08-02-11

Asset class

Contract type

S-

Underlying asset 1

TX (

note:

TX represents the reference rate of Treasury 10 year, which is the fixed rate)

Underlying asset 2

IIIL (

note:

IIIL represents 3 month LIBOR, which is the floating rate)

Notional currency 1

USD

Notional or principal amount 1

10M (

note:

this may be reported as “10,000,000”)

Pricing Notation

2.53

Payment frequency 1

Payment frequency 2

Reset frequency 1

Reset frequency 2

Tenor

G21 (

note:

actual day is not reported)

The Commission believes that as swaps become more standardized, market participants and real-time disseminators may develop a nomenclature that combines data fields in an easy-to-follow manner, ensuring that all the relevant information in appendix A to this proposed part 43 is publicly disseminated. For example, the swap in the above example may be displayed as follows:

16:20:47 IRS 10 TXIIIL 2.53 @0 G21.

In the illustration above, the symbol “C” is not included, because as the markets develop, the majority of standardized swaps will be cleared through DCOs and an indication of “U” would only be necessary for the reporting of uncleared swaps. The term “SWM” is also omitted since it could be assumed by market participants and the public that the swap has taken place on a swap market. Such an indication would only be needed if the swap was done off-facility pursuant to the non-financial end-user exception from the mandatory clearing requirement under Section 2(h)(7) of the CEA. The start date is not reported because in this illustration it is assumed for a swap of “TXIIIL” the start date is always two business days after the date of execution (

i.e.,

T+2). The term “IRS” would replace the separate data fields for asset class “IR” and contract type “S-” as the standard format once market participants have become accustomed to reading data on a consolidated tape for swaps. The terms “USD” and “M” in 10,000,000 are also dropped because in this illustration the market would have developed in such a manner as to understand that the standard trade is done in U.S. dollars and in round lots of one million or in this case “10”. Payment frequency and reset frequency would also be excluded for both of the underlying assets because the symbol “TXIIIL” now represents a plain vanilla interest rate swap where payment frequency and reset frequency are standardized terms of the swap transaction. The number “2.53” for price notation remains but in some cases, such as a basis swap, this field may be omitted as the market develops. The symbol “@0” is used because in some cases front-end, back-end, margin, collateral or other payments that are not included in the terms of the swap must be reported as an additional price notation characteristic. In this example, there is no additional price notation that must be reported. The symbol “G21” is still reported to indicate that the swap matures (

i.e.,

terminates) in February 2016.

Example 2:

On Friday, February 4, 2011, Bank X, once again enters into a plain vanilla 10-year fixed versus floating interest rate swap with Bank Y for a notional amount of $10 million U.S. dollars. The swap is scheduled to start on Tuesday, February 8, 2011 (

Note:

start dates are usually 2 business days later). Bank X is payer of the fixed leg of the swap and is obligated to pay a fixed rate of 2.53% on the notional amount for the ten-year tenor of the swap. Bank Y is the payer of the floating leg of the swap and is obligated to pay the prevailing three-month LIBOR on the $10 million notional amount. To illustrate an exception from the plain vanilla swap, the first LIBOR payment in this example is based on the three-month LIBOR rate for February 4, 2011 with a weekly rate reset, instead of the normal quarterly rate reset. Both parties have agreed to use the same day count convention, payment currency and notional amount for both of the underlying assets to the swap.

Bank X and Bank Y have additional payments to be made between the two parties under the terms of the swap. Bank X is required to deliver a front-end payment of $500,000 U.S. dollars to Bank Y, which is represented by an increase to the fixed-rate payer's requirement of “+0.07” and reported in the additional price notation data field. For the sake of clarity, this additional price notation data field should be in the same format as the price notation field and be displayed as an addition or subtraction to the fixed-rate payer's rate under the swap.

In order for the parties to protect themselves from a possible increase in interest rates, Bank Y purchases a one-year pay fixed versus floating swaption with a strike rate of 2.53% to pay fixed for 9-years to Bank X (

i.e.,

through the maturity of the swap). This swaption effectively will terminate the original swap with Bank X, and in this example, we can assume that the cost of the swaption is $100,000. This swaption might also be listed as an adjustment to the fixed rate that Bank Y would receive from Bank X in the initial swap if the payments were not made outright, but were blended into the initial fixed rate. In this example, this might be represented by subtracting four basis points or “-0.04”.

The reset and payment frequency for the fixed rate is semi-annual (every six months), while the reset and payment frequency for the three-month LIBOR is weekly, upon the request of the variable rate payer. The parties' requirements under the swap are scheduled to mature on Monday, February 8, 2021. Bank X and Bank Y are both members in good standing with a SEF named “Xeqution Co.” and use a DCO named “ClearitAll”.

Field

Description

Execution time-stamp

16:20:47

Cleared or uncleared

C (

note:

the name of DCO is not reported)

Execution Venue

SWM (

note:

the name of SEF is not reported)

Start date

08-02-11

Asset class

Contract type

S-

Underlying asset 1

TX (

note:

TX represents Treasury 10 year)

Underlying asset 2

IIIL (

note:

IIIL represents 3 month LIBOR)

Price Notation

2.53

Additional price notation

+0.07

Notional currency 1

USD

Notional or principal amount 1

10M (

note:

this may be reported as “10,000,000”)

Payment frequency 1

Payment frequency 2

Reset frequency 1

Reset frequency 2

Tenor

G21 (

note:

actual day is not reported)

Embedded option on swap

EMBED1

Option Strike Price

O2.53

Option Type

PF (

note:

this is always reported from the point of view of the variable leg)

Option Family

EU (

note:

this is a European style option)

Option currency

USD

Option premium

-.04 (

note:

this may be reported as “$100,000” depending on market conventions)

Option lockout period

G12 (

note:

actual day is not reported)

Option expiration

G21 (

note:

actual day is not reported)

The Commission believes that as swaps become more standardized, market participants or real-time disseminators may develop a nomenclature that combines data fields in an easy-to-follow manner, while ensuring that all the relevant information in appendix A to this proposed part 43 is publicly disseminated. Even swaps with one or more non-standard terms may still be reported in a consolidated format. For example, the swap in the example above may be displayed as follows:

16:20:47 IRS 10 TXIIIL S/1W 2.53 @0.07 G21 EMBED1 EU 2.53PF@-.04 LOG12

In the illustration above, the symbol “C” is not included because as the markets develop the majority of standardized swaps will be cleared through DCOs, and an indication (

e.g.,

the symbol “U”) would only be necessary for the reporting of uncleared swaps. The term “SWM” is also omitted since, it could be assumed by market participants and the public that the swap has taken place on a swap market. Such indication would only be necessary if the swap was done off-facility, pursuant to the non-financial end-user exception from the mandatory clearing requirement under Section 2(h)(7) of the CEA. The start date not reported for this swap because in this illustration, it is assumed that for a swap of “TXIIIL” the start date is always two business days after the date of execution (

i.e.,

T+2). The term “IRS” would replace the separate data fields for asset class “IR” and contract type “S-” as the standard format once market participants have come accustomed reading data on a consolidated tape for swaps. The terms “USD” and “M” in 10,000,000 are also dropped because in this illustration the market has developed in such manner as to understand that the standard trade is done in U.S. dollars and in round lots of one million or in this case “10”.

The Commission anticipates that in order for the price notation and additional price notation data fields to be of the greatest value to market participants and the public, some form of standardization likely will develop for the purposes of real-time public reporting and market participants consistently use these data fields.

An example of the evolution of standardization is shown in the illustration above where price notation is displayed as the number “2.53”, which is equal to the rates associated with payments on each leg at execution. Each leg of the swap's present value of future payments would be equal to zero (

i.e.,

a par swap's value). The symbol “@0.07” is listed in the illustration above because the present value of the front-end payment is the equivalent of a higher interest payment of 0.07 over the life of the swap for the party that is paying the fixed rate at execution. Payment frequency and reset frequency have been represented with an “S/1W” for the underlying assets because the symbol “TXIIIL” represents a plain vanilla interest rate swap where payment frequency and reset frequency are standardized terms of the swap transaction. In the illustration above, however, only the Treasury leg is standard, while the floating LIBOR leg is set to weekly versus its standard quarterly format. The symbol “G21” is reported to indicate that the requirements under the swap terminate in February 2021. In this illustration, “TXIIIL” is still used as a symbol that lets participants know several of the previously required data fields are standardized and combined and therefore do not need to be displayed separately for real-time public reporting, while those fields that are non-standard are simply broken out and reported separately in a more traditional long format.

It is important to note that such standards are not intended to change the form in which market participants use to quote or construct swaps.

The interest rate swap in this illustration contains an embedded option that is broken out so that data fields can be easily comparable across a wider variety of similar, but not identical swaps, thus promoting post-trade price transparency. The term “EMBED1” indicates that this interest rate swap has an embedded option and the pricing information for such embedded option follows on the real-time public reporting consolidated tape. The symbol “2.53PF” replaces the separate data fields for option strike price “O2.53” and option type “PF”. Option family “EU” is included in the consolidated tape to indicate the family of the embedded option. The option currency “USD” is left off of this transaction because it is assumed for a “TXIIIL” swap, the option currency for any embedded options would be “USD”, unless broken out and reported individually. The symbol “LOG12” is used instead of “G12” to indicate the lock out period to provide clarity. The option expiration of “G21” is omitted because the embedded option is assumed to be in a standard form and as such would be set to expire at the same time as the swap itself. If such embedded option was not in standard form, then the option expiration field would have been reported as an additional data field.

The Commission requests comment on all aspects of the data fields in appendix A to proposed part 43 that would be required to be reported in real-time under this proposal. In addition, the Commission requests specific comment on the following issues:

• Do commenters agree with the proposed data fields that would be required to be reported in real-time? If not, what additional data fields should be reported and why? How would public dissemination of these data fields enhance transparency and price discovery?

• Which data fields, if any, should not be required to be publicly disseminated in real-time and why?

• Would public dissemination of certain data fields reduce market liquidity?

If so, why?

Section 2(a)(13)(E)(iv) requires that the Commission “take into account whether the public disclosure will materially reduce market liquidity.”

• Should the portion of the amount reported in the additional price notation data field that relates to the creditworthiness of a counterparty be extracted and reported as a separate data field? If so, why? Should the creditworthiness of a counterparty be reported in some other way?

• Do commenters agree that tenure should only be reported with month and year? Is this a useful method for protecting the anonymity of the counterparties? Does this provide an adequate level of transparency?

• Do commenters agree with the proposed method for real-time reporting and public dissemination of non-standardized swaps? Should the “indication of other price affecting term” data field contain more specificity as to what type of term is affecting the price? If so, what additional information should be included and how should it be reported?

• Would public dissemination of information concerning non-standardized swaps materially reduce market liquidity? If so, why?

See

Section 2(a)(13)(E)(iv).

• Under the proposal, the swap instrument data field would only be required for block trades and large notional swaps, should this data field be reported for all swaps? If so, why?

• Would information concerning the type of counterparties that enter into a swap enhance transparency and price discovery (

e.g.,

whether the counterparty is a swap dealer, MSP, or not)? If so, why?

• Would separately reporting embedded option information enhance price discovery and transparency? If not, why?

• Do proposed § 43.4 and appendix A to proposed part 43 provide adequate guidance with respect to the information that must be reported? If not, what additional guidance do commenters believe is necessary?

• Do commenters agree with the reporting of price-affecting continuation events? Should data relating to these events be publicly disseminated in real-time in the same way as new swap transactions? What additional types of transactions, if any, would be price-affecting continuation events that should be reported and publicly disseminated in real-time?

• What would be the costs of reporting and publicly disseminating the proposed data fields? What would be the benefits? Please provide examples, if possible.

5. Proposed Section 43.5—Block Trades and Large Notional Swaps

Sections 2(a)(13)(E)(ii) and (iii) of the CEA authorize the Commission to prescribe rules “to specify the criteria for determining what constitutes a large notional swap transaction (block trade) for particular markets and contracts” and “to specify the appropriate time delay for reporting large notional swap transactions (block trades) to the public.” As discussed in the Background Section above, while Section 2(a)(13)(E) of the CEA specifically refers to the swaps described only in Sections 2(a)(13)(C)(i) and 2(a)(13)(C)(ii) of the CEA (

i.e.,

clearable swaps, including swaps that are exempt from clearing), the Commission believes that it is appropriate to consider the four criteria in Section 2(a)(13)(E) of the CEA for all four categories of swaps described in Section 2(a)(13)(C) of the CEA.

Therefore, proposed § 43.5 establishes: (1) the procedures for determining the appropriate minimum sizes for block trades and large notional swaps; and (2) the appropriate time delays for the reporting of block trades and large notional swaps.

Pursuant to the Commission's authority under Sections 2(a)(13)(B) and 2(a)(13)(E)(iii) of the CEA.

In developing the proposed rules with respect to block trades and large notional swaps, the Commission considered its guidance with respect to block trades in the futures markets. Additionally, the Commission considered the treatment of block trades in other markets (both foreign and domestic), such as those for equities, options and corporate bonds. Further, the Commission considered the treatment and effects of swaps with large notional or principal amounts in the current OTC swap markets. The Commission is not aware of any academic literature that offers empirical evidence to support the claim of impaired liquidity given greater transparency or how block trades on swaps or large notional swaps are affected by a post-trade transparency regime.

The Commission will continue to analyze and study the effects of increased transparency on post-trade liquidity, particularly in the context of block trades on swaps and large notional swaps. The Commission expects that, as post-trade transparency is implemented in the context of the Dodd-Frank Act, new data will come to light that will inform the discussion and could cause subsequent revision of the proposed rules.

The Commission recognizes that the term “block trade” has different meanings in different markets. For example, in the futures markets, a block trade is a permissible, privately negotiated transaction that equals or exceeds a DCM's specified minimum quantity of futures or options contracts and is executed away from the DCM's centralized market but pursuant to its rules.

Block trades are large-sized transactions that would cause a significant price impact if required to be executed on the DCM's centralized market. In contrast, the Commission understands, through discussions with market participants, that in the swaps markets, asset managers that execute OTC swaps and then later distribute or allocate the swap to various clients or funds may refer to such bunched transactions as block trades. To clarify the Commission's view of block trades on swaps, the proposed rules include definitions for both “block trade” and “large notional swap”.

See, e.g.,

CME Rulebook, Rule 526 (“Block Trades”). Available at:

http://www.cmegroup.com/rulebook/CME/index.html;

ICE Futures U.S. Rulebook, Rule 4.31 (“Block Trading”). Available at:

https://www.theice.com/Rulebook.shtml?futuresUSRulebook=.

The legislative history to the Dodd-Frank Act provides the following statement by Senate Agriculture Committee Chairwoman Blanche Lincoln regarding block trades and large notional swaps: “I would like to specifically note the treatment of `block trades' or `large notional' swap transactions. Block trades, which are transactions involving a very large number of shares or dollar amount of a particular security or commodity and which transactions could move the market price for the security or contract, are very common in the securities and futures markets. Block trades, which are normally arranged privately, off exchange, are subject to certain minimum size requirements and time delayed reporting * * *.” 156 Cong. Rec. S5921 (daily ed. July 15, 2010) (statement of Sen. Blanche Lincoln).

i. Parties to a Block Trade or Large Notional Swap

Proposed § 43.5(b)(1) provides that any party to a block trade or large notional swap is required to be an eligible contract participant (“ECP”) as that term is defined in Section 1(a)(18) of the CEA. The ECP requirement relies on Section 2(e) of the CEA, which provides that “[i]t shall be unlawful for any person, other than an eligible contract participant, to enter into a swap unless the swap is entered into on, or subject to the rules of, a board of trade designated as a contract market under section 5.” The parties to any block trade, pursuant to a swap market's rules, and any large notional swap executed off-facility, must be ECPs. However, the proposed rule makes clear that a registered DCM may allow commodity trading advisors acting in an asset managerial capacity and investment advisors that have over $25 million in assets under management, including foreign persons performing equivalent roles, to carry out block trades on a registered DCM for non-ECP customers. Any such person may not conduct a trade on behalf of a customer unless the person receives instruction or prior consent to do so.

Proposed § 43.5(b)(2) requires that parties to a swap that is equal to or greater than the minimum block trade size must elect to be treated as a block trade and that the swap market must provide the real-time disseminator with such election. The block trade election allows parties to a swap to calculate the impact of executing the transaction bilaterally and delaying public dissemination versus executing the transaction on a swap market's trading system or platform where there would be no delay in the dissemination of the swap's transaction and pricing data. Proposed § 45.5(b)(2) also requires that the parties to a swap that qualifies as a large notional swap must elect to be treated as a large notional swap and the reporting party must provide the real-time disseminator with such election.

By way of comparison, a party to a futures contract may elect not to treat the transaction as a block trade. By not electing to treat the transaction as a block trade, the party is choosing to place its order on the DCM's centralized market. The party who makes such an election may believe that it will receive a better price in settling its trade immediately, on the DCM's centralized market, rather than bilaterally negotiating the transaction and delaying the reporting of the trade.

ii. Block Trades on Swaps

Proposed § 43.2(f) and (l) define “block trade” and “large notional swap”

as separate concepts to distinguish the difference between large notional or principal sized trades executed pursuant to a swap market's rules (block trades) and off-facility swaps that are not subject to a swap market's rules but have very large notional or principal sizes (large notional swaps). Proposed § 43.2(f) defines a block trade as a swap transaction that: (1) Involves a swap that is made available for trading or execution on a swap market; (2) occurs off the swap market's trading system or platform pursuant to the swap market's rules and procedures; (3) is consistent with the minimum block trade size requirements set forth in proposed § 43.5; and (4) is reported in accordance with the swap market's rules and procedures and subject to the appropriate time delay set forth in proposed § 43.5.

Both block trades and large notional swaps would only apply to new events (

i.e.,

not price affecting continuation events).

Proposed § 43.5(c)(2) provides that a reporting party for any block trade must report the block trade transaction and pricing data pursuant to the rules of the swap market that makes that swap available for trading. Such reporting must occur as soon as technologically practicable after execution of the block trade and pursuant to the rules of the swap market.

Proposed § 43.5(c)(3) would require the swap market that accepts the block trade to immediately send the block trade transaction and pricing data to a real-time disseminator, which shall not publicly disseminate the swap transaction and pricing data before the expiration of the appropriate time delay described in proposed § 43.5(k) discussed below.

The Commission requests comment generally on all aspects of the proposed rules regarding block trades. In addition, the Commission requests specific comment on the following issues:

• Do commenters agree with the proposed definition of “block trade”? If not, why?

• Do commenters believe that the Commission should set a maximum time frame in which a reporting party must report a block trade to a swap market, or should such time period be defined pursuant to the rules of the respective swap markets?

iii. Large Notional Swaps

Proposed § 43.2(l) defines a large notional swap as a swap that (1) is not available for trading or execution on a swap market; (2) is consistent with the appropriate size requirements for large notional swaps set forth in proposed § 43.5; and (3) is reported in accordance with the appropriate time delay requirements set forth in proposed § 43.5. Similar to the proposed reporting requirements for block trades, the reporting party to a large notional swap must report to a real-time disseminator as soon as technologically practicable. Such large notional swaps may include: (1) Swaps that would have been subject to mandatory clearing, and for which an end-user relies on the exception from the mandatory clearing requirement in Section 2(h)(7) of the CEA;

or (2) other off-facility swaps that are not subject to mandatory clearing but have large notional amounts (which would include non-standardized swaps). The proposed rules provide that if a swap is sufficiently large in notional or principal amount, such swap could be considered a large notional swap and therefore may be eligible for the same time delay in real-time public reporting as block trades.

As described below, swaps that rely on the exception in Section 2(h)(7) of the CEA, although large notional swaps, are subject to the same time delay as block trades.

Proposed § 43.5(d) requires the registered SDR that has received the swap transaction and pricing data for a large notional swap not to publicly disseminate such data before the expiration of the appropriate time delay described in proposed § 43.5(k).

Proposed § 43.5(e) provides that an off-facility swap where neither counterparty is a swap dealer or an MSP (

e.g.,

a swap between two end-users) may be eligible to be a large notional swap. Although the parties to these swaps will not be registrants with the Commission, this provision specifies that such swaps (

i.e.,

end-user to end-user transactions) will be treated the same as swaps in which a swap dealer or MSP is a party.

The Commission requests comment generally on all aspects of the proposed rules regarding large notional swaps. In addition, the Commission requests specific comment on the following issues:

• Do commenters agree with the proposed definition of “large notional swap”? If not, why?

• Do commenters agree that off-facility swaps in which neither party is a swap dealer or an MSP be eligible to be treated as large notional swaps? If not, why?

iv. Time-Stamp and Reporting Requirements for Block Trades and Large Notional Swaps

In addition to the execution time-stamp requirement under proposed § 43.4 and appendix A to proposed part 43, proposed § 43.5(f) would require a swap market and registered SDR that accepts and publicly disseminates swap transaction and pricing data in real-time to have additional time-stamp requirements with respect to block trades and large notional swaps. Proposed § 43.5(f)(1) would require swap markets to time-stamp swap transaction and pricing data with the date and time to the nearest second (1) when such swap market receives the data from a reporting party and (2) when a swap market transmits such data to a real-time disseminator. Proposed § 45.5(f)(2) would require registered SDRs that accept and publicly disseminate swap transaction and pricing data in real-time to time-stamp such data with the date and time to the nearest second when (1) such registered SDR receives such swap transaction and pricing data from a swap market or reporting party and (2) when such data is publicly disseminated.

Proposed § 43.5(f)(3) would require that records of these additional time-stamps be maintained for a period of at least five years from the execution of the block trade or large notional swap. The Commission believes that requiring a swap market and a registered SDR to time-stamp these actions for block trades and/or large notional swaps is essential in providing an audit trail for block trade and large notional swap transactions from execution through public dissemination. Additionally, such time-stamps would provide the Commission ability to monitor whether reporting parties, swap markets and registered SDRs are reporting the block trades and large notional swaps in the manner described in proposed part 43.

Proposed § 43.5(f) would require five distinct time-stamps for block trades and three distinct time-stamps for large notional swaps. Block trades would receive a time-stamp by: (1) The parties at execution; (2) the swap market upon receipt of the data; (3) the swap market when it sends the data to a real-time disseminator; (4) the real-time disseminator upon receipt of the d

This text is long and has been trimmed here. Open the source document for the complete record.

This is a copy of a public record, reproduced as it was published. It is not legal advice, and it may not be the version a court would rely on. Check the official source before you cite it.