IDENTIFYING INFORMATION ####################### APPID: w7. APPID type: OMNA. Owner: Device Management Working Group. Contact: Device Management Working Group . Registration version: 1. Registration timestamp: 2003-06-18. Application description: Device Management (DM). Application reference: OMA Device Management (Based on SyncML DM), Version 1.1.2 specifications, URL:http://www.openmobilealliance.org/documents.asp. "SyncML DM Tree and Description" specification, URL:http:www.openmobilealliance.org/tech/docs/OMA-SyncML-DMTND-V1_1_2-20030508-C.pdf. "SyncML DM Security" specification, URL:http:www.openmobilealliance.org/tech/docs/OMA-SyncML-DMSecurity-V1_1_2-20030508-C.pdf. "SyncML Representation Protocol" specification, URL:http:www.openmobilealliance.org/tech/docs/OMA-SyncML-RepPro-V1_1_2-20030505-C.pdf. WELL-KNOWN PARAMETERS ##################### Characteristic/name: APPLICATION/APPID. Status: Required. Occurs: 1/1. Default value: None. Used values: w7. Interpretation: N/A. ------- Characteristic/name: APPLICATION/PROVIDER-ID. Status: Required. Occurs: 1/1. Default value: None. Used values: Server Identifier specified in "SyncML DM Tree and Description". Interpretation: PROVIDER-ID specifies the server identifier for management server used in the management sessions. ------- Characteristic/name: APPLICATION/NAME. Status: Optional. Occurs: 0/1. Default value: None. Used values: N/A. Interpretation: User displayable name for management server. ------- Characteristic/name: APPLICATION/TO-PROXY. Status: Required if use of Proxy supported. Occurs: 0/*. Default value: None. Used values: N/A. Interpretation: N/A. ------- Characteristic/name: APPLICATION/TO-NAPID. Status: Required if direct use of Network Access Point supported. Occurs: 0/*. Default value: None. Used values: N/A. Interpretation: N/A. ------- Characteristic/name: APPADDR/ADDR. Status: Required. Occurs: 1/1. Default value: None. Used values: Absolute URI. Interpretation: Management server address, which may differ based on the used transport binding. Also APPLICATION/ADDR can be used to specify the address, if the parameter APPADDR/ADDRTYPE is not used. ------- Characteristic/name: APPADDR/ADDRTYPE. Status: Required. Occurs: 0/1. Default value: None. Used values: N/A. Interpretation: N/A. ------- Characteristic/name: PORT/PORTNBR. Status: Required. Occurs: 0/1. Default value: None. Used values: N/A. Interpretation: N/A. ------- Characteristic/name: APPAUTH/AAUTHLEVEL. Status: Required. Occurs: 0/1. Default value: None. Used values: "APPSRV", "CLIENT", "OBEX". Interpretation: When the value is omitted, the characteristic contains client credentials for HTTP or WSP authentication. The used values are described below. ------- Characteristic/name: APPAUTH/AAUTHTYPE. Status: Required. Occurs: 0/1. Default value: None. Used values: "HTTP-BASIC", "HTTP-DIGEST", "BASIC", "DIGEST", "HMAC", "X509", "SECUREID", "SAFEWORD", "DIGIPASS". Interpretation: See descriptions below. The values specific to the SyncML DM protocol are covered in "SyncML DM Security" and "SyncML Representation Protocol". ------- Characteristic/name: APPAUTH/AAUTHNAME. Status: Required. Occurs: 1/1. Default value: None. Used values: N/A. Interpretation: N/A. ------- Characteristic/name: APPAUTH/AAUTHSECRET. Status: Required. Occurs: 1/1. Default value: None. Used values: N/A. Interpretation: N/A. ------- Characteristic/name: APPAUTH/AAUTHDATA. Status: Required. Occurs: 0/1. Default value: None. Used values: Nonce value. Interpretation: Contains the nonce value used in the SyncML DM authentication as specified in "SyncML DM Security". ------- APPLICATION-SPECIFIC PARAMETERS ############################### Characteristic/name: APPLICATION/INIT. Status: Required. Occurs: 0/1. Default value: None. Used values: N/A. Interpretation: Takes no values. When present indicates that the management server wants the client to initiate a management session immediately after settings approval. ------- PARAMETER VALUES ################ Characteristic/name/parameter: APPAUTH/AAUTHLEVEL/APPSRV. Status: Required. Interpretation: Credentials client uses to authenticate itself to the SyncML DM Server at the DM protocol level. -------- Characteristic/name/parameter: APPAUTH/AAUTHLEVEL/CLIENT. Status: Required. Interpretation: Credentials server uses to authenticate itself to the SyncML DM Client at the DM protocol level. -------- Characteristic/name/parameter: APPAUTH/AAUTHLEVEL/OBEX. Status: Optional. Interpretation: Client credentials for OBEX authentication. -------- Characteristic/name/parameter: APPAUTH/AAUTHTYPE/HTTP-BASIC. Status: Optional. Interpretation: HTTP basic authentication done according to RFC 2617. -------- Characteristic/name/parameter: APPAUTH/AAUTHTYPE/HTTP-DIGEST. Status: Optional. Interpretation: HTTP digest authentication done according to RFC 2617. -------- Characteristic/name/parameter: APPAUTH/AAUTHTYPE/BASIC. Status: Required. Interpretation: SyncML DM 'syncml:auth-basic' authentication as specified in "SyncML DM Security". -------- Characteristic/name/parameter: APPAUTH/AAUTHTYPE/DIGEST. Status: Required. Interpretation: SyncML DM 'syncml:auth-md5' authentication as specified in "SyncML DM Security". -------- Characteristic/name/parameter: APPAUTH/AAUTHTYPE/HMAC. Status: Optional. Interpretation: SyncML DM 'syncml:auth-hmac' authentication as specified in "SyncML DM Security". -------- Characteristic/name/parameter: APPAUTH/AAUTHTYPE/X509. Status: Optional. Interpretation: SyncML 'syncml:auth-X509' authentication done according to "SyncML Representation Protocol". -------- Characteristic/name/parameter: APPAUTH/AAUTHTYPE/SECURID. Status: Optional. Interpretation: SyncML 'syncml:auth-securid' authentication done according to "SyncML Representation Protocol". -------- Characteristic/name/parameter: APPAUTH/AAUTHTYPE/SAFEWORD. Status: Optional. Interpretation: SyncML 'syncml:auth-safeword' authentication done according to "SyncML Representation Protocol". -------- Characteristic/name/parameter: APPAUTH/AAUTHTYPE/DIGIPASS. Status: Optional. Interpretation: SyncML 'syncml:auth-digipass' authentication done according to "SyncML Representation Protocol". -------- EXAMPLE ####### ###END###