Messages in one-to-many exchanges: none
Message Syntax: IRIS XML instances as defined by IRIS [6]
Message Semantics: request/response exchanges as defined by IRIS [6]
Contact Information: Andrew Newton and Marcos Sanz
8.2. URI Scheme Registration
URL scheme name: iris.beep
URL scheme syntax: defined in Section 7.1 and [6]
Character encoding considerations: as defined in RFC 2396 [7]
Intended usage: identifies an IRIS entity made available using the
BEEP profile for IRIS
Applications using this scheme: defined in IRIS [6]
Interoperability considerations: n/a
Security Considerations: defined in Section 12.
Relevant Publications: BEEP [2] and IRIS [6]
Contact Information: Andrew Newton and Marcos Sanz
Author/Change controller: the IESG
8.3. Well-Known TCP Port Registration
Protocol Number: TCP
Message Formats, Types, Opcodes, and Sequences: defined in Sections
3, 4, and 5.
Functions: defined in IRIS [6]
Use of Broadcast/Multicast: none
Proposed Name: IRIS over BEEP
Short name: iris.beep
Contact Information: Andrew Newton and Marcos Sanz
8.4. S-NAPTR Registration
Application Protocol Label: iris.beep
Intended usage: identifies an IRIS server using BEEP
Interoperability considerations: n/a
Security Considerations: defined in Section 12
Relevant Publications: BEEP [2] and IRIS [6]
Contact Information: Andrew Newton and Marcos Sanz
Author/Change controller: the IESG
9. Registry Definition Checklist
Specifications of registry types MUST include the following explicit
definitions:
o message pattern -- a definition of the message pattern for use
with BEEP, or a declaration to use the default message pattern in
Section 5.2.
o server authentication method -- a definition of the method to use
for server authentication with TLS, a declaration to use the basic
server authentication method in Section 6.2, or a declaration to
use no server authentication at all.
10. Internationalization Considerations
See Section 4.
11. IANA Considerations
Registrations with the IANA are described in Section 8.
12. Security Considerations
Implementers should be fully aware of the security considerations
given by IRIS [6], BEEP [2], and TLS [4]. With respect to server