TABLE OF CONTENTS This appendix includes an extract from version 2.2 of the FLAP specification. This documents the FLAP messages and includes the FLAP XML schema.
FLAP uses the Block Extensible Exchange Protocol (BEEP) (see Reference 1) for the session-layer protocol. BEEP provides a secure, asynchronous communication layer that allows for two-way communication between client and server. It also manages message framing and message-response correlation.
The FLAP profile is identified by the URN:
http://sitacs.uow.edu.au/ns/location/flap/beep
Following the guidelines of Reference 1, Table A.1 summarizes the FLAP profile.
| Registration Item | Value |
|---|---|
| Profile Identification | http://sitacs.uow.edu.au/ns/location/flap/beep |
| Messages exchanged during channel creation | ns-prefix |
| Messages starting one-to-one exchanges | ns-prefix, ntfy, aq |
| Messages in positive replies | syncr, aqr |
| Messages in negative replies | error |
| Messages in one-to-many exchanges | sync |
| Message syntax | This appendix |
| Message semantics | Chapter 3 of this book |
| Contact information | The authors of this book |
The TCP [binding for BEEP] is required (see References 1 and 2). In addition, it is recommended that the TLS profile for BEEP be used for FLAP TLS provides a reliable connection with authentication and protection from replay, intercept, and eavesdropping. However, where performance requirements demand it, unsecured TCP may be used, providing that link security is ensured through other means (dedicated media, VPN, and so on).
No specific TLS ciphersuite is required for this protocol, although due to the nature of the relationship between the LIS and ALE, those defined in Reference 3 are recommended. Pre-shared keys provide a degree of...
