RFC 3117:On the Design of Application Protocols
RFC-Ref

framework


Click on the red underlined text to get to the source

... To begin, we figured that our requirements, while a little more stringent than most, could fit inside a framework suitable for a large number of future application protocols. The trick is to avoid ...


... file transfer, remote shell, and the world-wide web. So, the bet we are placing in going forward is that there will continue to be reasons for defining protocols that fit within our framework. ...


... 17] (the Simple Authentication and Security Layer) was developed to provide a framework for authenticating protocol peers. SASL let's you describe how an authentication mechanism ...


... extensibility. For example, although SMTP initially didn't have an extension framework, it was only after ten years of experience that its excellent design was altered. In contrast, a poorly-designed protocol such as Telnet ...


... The BXXP Framework ...
... We defined an application protocol framework called BXXP (the Blocks eXtensible eXchange Protocol). The reason it's a "framework" instead ...
... application protocol framework called BXXP (the Blocks eXtensible eXchange Protocol). The reason it's a "framework" instead of an application protocol is that we provide all the mechanisms ...
... intra-application streams is worth it. (Besides, our belief is that few application implementors will actually code the BXXP framework directly -- rather, we expect them to use third-party packages that ...
... authorization. Naming was excluded from the framework because, outside of URIs, there isn't a commonly accepted framework ...
... framework because, outside of URIs, there isn't a commonly accepted framework for naming things. To our view, this remains a domain-specific problem for each application protocol ...
... Similarly, authorization was explicitly excluded from the framework. Every approach to authorization we've seen uses names to identify ...
... principals (i.e., targets and subjects), so if a framework doesn't include naming, it can't very well include authorization. ...
... From Framework to Protocol ...



Google
Web
RFC-Ref