Bob, Joe,
Given this viewpoint, what guidance would you give, then, to protocol
designers who are writing specifications?
Eliot
On 3/30/11 8:09 PM, Bob Braden wrote:
+1
Bpb Braden
On 3/30/2011 1:11 AM, Joe Touch wrote:
Hi, all,
Perhaps we're not talking about an API, or even an abstract API, but
just the "application interface" (or just "upper layer service"
specification).
RFC793 is a great example that a protocol provides a service, and
that service needs to be explained - and that explaining it does NOT
need to be done in a specific language.
Joe
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf