RFC 3958:Domain-Based Application Service Location...
RFC-Ref

Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)


1. Introduction
2. Straightforward-NAPTR (S-NAPTR) Specification
2.1. Key Terms
2.2. S-NAPTR DDDS Application Usage
2.2.1. Ordering and Preference
2.2.2. Matching and Non-Matching NAPTR Records
2.2.3. Terminal and Non-terminal NAPTR Records
2.2.4. S-NAPTR and Successive Resolution
2.2.5. Clients Supporting Multiple Protocols
3. Guidelines
3.1. Guidelines for Application Protocol Developers
3.1.1. Registration of Application Service and Protocol Tags
3.1.2. Definition of Conditions for Retry/Failure
3.1.3. Server Identification and Handshake
3.2. Guidelines for Domain Administrators
3.3. Guidelines for Client Software Writers
4. Illustrations
4.1. Use Cases
4.2. Service Discovery within a Domain
4.3. Multiple Protocols
4.4. Remote Hosting
4.5. Sets of NAPTR RRs
4.6. Sample sequence diagram
5. Motivation and Discussion
5.1. So Why Not Just SRV Records?
5.2. So Why Not Just NAPTR Records?
6. Formal Definition of <Application Service Location> Application of
6.1. Application-Unique String
6.2. First Well-Known Rule
6.3. Expected Output
6.4. Flags
6.5. Service Parameters
6.5.1. Application Services
6.5.2. Application Protocols
6.6. Valid Rules
6.7. Valid Databases
7. IANA Considerations
7.1. Application Service Tag IANA Registry
7.2. Application Protocol Tag IANA Registry
7.3. Registration Process
8. Security Considerations
9. Acknowledgements
10. References
10.1. Normative References
10.2. Informative References
11. Appendix A. Pseudo-Pseudocode for S-NAPTR
12. Appendix B. Availability of Sample Code
13. Authors' Addresses
14. Full Copyright Statement
15. Intellectual Property
16. Acknowledgement

Google
Web
RFC-Ref
RFC-Ref.org
Frontpage
Global Index
RFC
Sister Sites
Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org