<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE permissionrequestfile PUBLIC "-//OCAP//DTD Permission Request File 1.0//EN"
"http://www.opencable.com/ocap/dtd/ocappermissionrequestfile-1-0.dtd">

<permissionrequestfile orgid="0x21" appid="0x2468">
     <file value="true"></file>
     <applifecyclecontrol value="true"></applifecyclecontrol>
     <returnchannel>
          <defaultisp></defaultisp>
          <phonenumber></phonenumber>
     </returnchannel>
     <tuning value="true"></tuning>
     <servicesel value="true"></servicesel>
     <userpreferences read="true" write="true"></userpreferences>
     <network>
          <host action="all">nethostname</host>
     </network>
     <dripfeed value="true"></dripfeed>

     <ocap:monitorapplication name="registrar" value="true"></ocap:monitorapplication>
     <ocap:monitorapplication name="service" value="true"></ocap:monitorapplication>

</permissionrequestfile>

Notes:

  1. See OCAP specification Section 14.2.2.1 and MHP 12.6.2 and for more details.

  2. <persistentfilecredential> sections omitted. OCAP SFG allows you to generate and insert a Persistent File Credential into either someone else's Permission Request File or another person's Persistent File Credential into your own Permission Request File.

  3. <userpreferences> are User Language, Parental Rating, DefaultFontSize and Country Code.

  4. <tuning>, <returnchannel>, <servicesel> are required for allowing tuning to another channel frequency, allowing use of the return channel and service selection (changing to another channel) respectively.

  5. <network> provides network access via the return channel.

  6. The ocap:monitorapplication tags (text in red) are only required for Monitor Applications and require the application to be dual signed. As with a number of the tags included in this example, they can be omitted depending on the priviledges the application requires.