13.07.2015 Views

PROCEEDINGS May 15, 16, 17, 18, 2005 - Casualty Actuarial Society

PROCEEDINGS May 15, 16, 17, 18, 2005 - Casualty Actuarial Society

PROCEEDINGS May 15, 16, 17, 18, 2005 - Casualty Actuarial Society

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

APPLICATION OF THE OPTION MARKET PARADIGM 729SummaryMy main aim in this response to Mildenhall’s review of mypaper has been to acknowledge that my Formula (1.3) does nothave the generality I originally claimed for it, but then to presson with my contention that, even if the pricing formulas are notidentical, call options and excess insurance are still governed bythe same pricing paradigm; in particular, one that rests on optimalasset-liability matching.There is another point I hope I have made clear. The dynamicasset-liability matching regimen that underlies the Black-ScholesFormula (1.1) imposes a different burden on the seller of a calloption than the more passive asset-liability matching seen in CaseB and in insurance applications. As we saw in our discussion ofCase A, it is foolhardy to sell a hedgable call for the Black-Scholes price and then fail to dynamically hedge it. There areother situations where hedging is not possible, because the assetis either not traded or extremely illiquid. In such cases, itis also a mistake to sell the call option for the Black-Scholesprice, since it cannot be dynamically hedged. In the case of liquidtradable assets, arbitrageurs will drive the option price to theBlack-Scholes level. In illiquid or non-traded markets, there willbe no such arbitrage activity and in these markets, the pricingformulas used in Case B are applicable.In closing, I would like to thank Stephen Mildenhall for hisexcellent discussion, which not only corrected shortcomings inmy paper but also added greatly to the understanding (includingmy own) of option concepts among actuaries.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!