<?xml version="1.0" encoding="UTF-8" ?> 
<EapPeerDll>
	<!--
This subsection is used to configure rpc server and the eap peer dll 
-->
	<WrapperInfo>

		<!-- 
The author id, should be your company's Enterprise code. To find your companies enterprise code
go to http://www.iana.org/assignments/enterprise-numbers ,  if you company does not have an enterprise code
you can register for one at http://www.iana.org/cgi-bin/enterprise.pl

The Enterprise code of 311, is microsofts.  311 shuold only be used for testing purposes.  When a code of 311
is used,  microsoft will load the PctelEapPeer.dll directly into the EapHost service Process,  instead of loading it up 
in an out of proc com process.  Also, for the ui,  when 311 is specified,  windows will load this dll up into explorer.  
Using a vendor code of 311 makes it relatively easy to Debug the eap peer dlls, because you can attach to explorer.exe
and the svchost process that is hosting eaphost.  

DO NOT USE 311 IN RELEASE,  

Note,  at the time of this comment 9:58 AM 1/15/2007  the last issued id is 27775,  so it might be possible to Borrow someone elses
id if you do not expect them to be creating eap methods.  Do not use the pctel enterprise code for the SDK,  the pctel enterprise code is being used
in the client product.


This value is used as the author id under the EapHost service registry key.

see http://msdn2.microsoft.com/en-us/library/aa813686.aspx for information.  Note that microsoft did not actually implement the 
"HKLM\System\CCS\Services\Eaphost\Methods\<AuthorId>\254\<VendorId>\<EapTypeId>" functionality.  Even on Vista RTM it still causes explorer.exe 
to crash when you attempt to edit the profile using the ms profile page.  They say its supposed to be supported in vista sp1.


So for right now the entries will be created under.  So that it is listed in the EapHost service as an eap type.
HKLM\System\CurrentControlSet\Services\Eaphost\Methods\<AuthorId>\<EapTypeId>
		<AuthorId>311</AuthorId>
-->
<AuthorId>23678</AuthorId>

<!--
The RpcServer value is used to help create a dynamic endpoint for the rpc server name.  Simply just use your company name. All of the pctel clients use Pctel.
It is case sensative.  Do not use "Pctel" for the SDK,  try using PCTELSDK or some other value instead.
-->
		<RpcServer>Pctel</RpcServer>

<!--
This is the root of the registry key that is used to store the actually real,  eap methods.

This key exists under HKLM\Software\.

So for example
PctelEapPeer Authentication

would mean that the registry key is 

HKLM\Software\PctelEapPeer Authentication\


Do not use "PctelEapPeer Authentication" for the SDK,  it is reserved for use w/ the client.
-->
		<RegistryKey>PctelEapPeer Authentication</RegistryKey>
	
	<!--  To see logging informatino set this value to 1 then use the dbgview.exe utility
	      to see logging information -->
	<Logging>0</Logging>
	</WrapperInfo>
	<EapMethods>
		<!--
		These values are used to populate the Eap registry keys under EapHost\AuthorId\
		See the microsoft documentation for these values.
		-->

		<EapMethod>
			<TypeId>13</TypeId>
			<PeerFriendlyName>SmithMicro Eap-TLS Peer</PeerFriendlyName>
			<PeerInvokePasswordDialog>0</PeerInvokePasswordDialog>
			<PeerInvokeUsernameDialog>0</PeerInvokeUsernameDialog>
			<Properties>0x00280000</Properties>
			<TreatAsMsMethod>1</TreatAsMsMethod>
		</EapMethod>


		<EapMethod>
			<TypeId>21</TypeId>
			<PeerFriendlyName>SmithMicro Eap-TTLS Peer</PeerFriendlyName>
			<PeerInvokePasswordDialog>0</PeerInvokePasswordDialog>
			<PeerInvokeUsernameDialog>0</PeerInvokeUsernameDialog>
			<Properties>0x00280000</Properties>
			<TreatAsMsMethod>1</TreatAsMsMethod>
		</EapMethod>

		<EapMethod>
			<TypeId>25</TypeId>
			<PeerFriendlyName>SmithMicro Eap-PEAP Peer</PeerFriendlyName>
			<PeerInvokePasswordDialog>0</PeerInvokePasswordDialog>
			<PeerInvokeUsernameDialog>0</PeerInvokeUsernameDialog>
			<Properties>0x00280000</Properties>
			<TreatAsMsMethod>1</TreatAsMsMethod>
		</EapMethod>

		<EapMethod>
			<TypeId>43</TypeId>
			<PeerFriendlyName>SmithMicro Eap-Fast Peer</PeerFriendlyName>
			<PeerInvokePasswordDialog>0</PeerInvokePasswordDialog>
			<PeerInvokeUsernameDialog>0</PeerInvokeUsernameDialog>
			<Properties>0x00280000</Properties>
			<TreatAsMsMethod>1</TreatAsMsMethod>
		</EapMethod>
	</EapMethods>
</EapPeerDll>