1. Requirements for Generic Rights Trading Ko Fujimura fujimura@isl.ntt.co.jp 49th IETF Meeting – San Diego draft-ietf-trade-drt-requirements-01.txt

2. Contents What is RTS? Proposed specification structure Proposed actions Changes from "-00"

3. An infrastructure that enables to circulate diverse types of "digitally represented rights" Provide copy prevention functionality Can be shared among several issuers What is RTS? Rights Trading System (provided by RTS provider) User CollectorIssuer

4. Requirements & Approaches Preventing alternation Non-repudiation One and only one (idempotency) Preventing duplicate- redemption Preventing reproduction (copy prevention) Digital Signature IOTP messaging RTS

5. Proposed specification structure HTTP Messaging (One & only one) Signature (Preventing alternation) RTS (Preventing reproduction) Vendor- specific Protocols Order Comp. Paymnt Receipt Comp. Delivery Note Comp. XML Components Layer Common Protocol Layer Ticket Comp. IOTP v2 (Branding, Trading sequence control) Loyalty Comp.... IOTP v1 scope Transport Layer RMIIIOP... Independent control

6. Proposed Action  Publish the requirement document as an informational RFC as scheduled  Next step?  Rights Component 1.Loyalty Point Component  Gift certificate Component  Ticket Component  Coupon Component Can be specified in IOTP/ECML v2 or separate document?

7. Changes from "-00" Naming for "digitally represented rights" Use "electronic-rights" instead of "digital-rights" The title is changed to "Generic Rights Trading" To avoid confusion with "Digital Property Rights" Application examples are added (Section 6) To clarify the objectives and benefits of rights trading Improvement of readability A several editorial changes are made Requirements are now clarified!