Hi all

here is a question that probably does not have an easy answer.

But I am curious about what happens when a new protocol is being
invented at some hardware manufacturer. How do the people who work on
these actually go about inventing a new protocol?

What steps do they go through?

Hi all

here is a question that probably does not have an easy answer.

But I am curious about what happens when a new protocol is being
invented at some hardware manufacturer. How do the people who work on
these actually go about inventing a new protocol?

What steps do they go through?

Any good books / websites that deal with this subject? (preferably
books)

Hi all

here is a question that probably does not have an easy answer.

But I am curious about what happens when a new protocol is being
invented at some hardware manufacturer. How do the people who work on
these actually go about inventing a new protocol?

What steps do they go through?

Any good books / websites that deal with this subject? (preferably
books)

Thanks in advance,

here is a question that probably does not have an easy answer.

But I am curious about what happens when a new protocol is being
invented at some hardware manufacturer. How do the people who work on
these actually go about inventing a new protocol?

What steps do they go through?

Any good books / websites that deal with this subject? (preferably
books)

But I am curious about what happens when a new protocol is being
invented at some hardware manufacturer. How do the people who work on
these actually go about inventing a new protocol?

Any good books / websites that deal with this subject? (preferably
books)

Hi all

here is a question that probably does not have an easy answer.

But I am curious about what happens when a new protocol is being
invented at some hardware manufacturer. How do the people who work on
these actually go about inventing a new protocol?

What steps do they go through?

Any good books / websites that deal with this subject? (preferably
books)

Thanks in advance,

Recently came across the term toolkits. These are used as standards and
they include "hard coded" data sets, but offer the option for
modification.
These toolkits are used to manipulate data, and probably could resemble an
ADT (abstract data type). But ifd there is a version for networking, then
you have a network protocol.

My subject of inquiry is based on the problem of the ten flower shoppes,
where clerks share the designs and market information and special
promotion
opportunities as partners. It means they have an extra day off. And
those
of them who are learning more slowly can bind useful help from the network
of clerks in their design repository. You want to be a repository
subscriber? Then you can have the keys to the tools. Can we call a
doctor!!!??

"S Claus" <santa at (no spam) temporaryinbox.com> wrote in message
news:7324c39b-b5e6-4aff-a6a6-6d0f86a7bd3a at (no spam) v23g2000pro.googlegroups.com...
Hi all

here is a question that probably does not have an easy answer.

But I am curious about what happens when a new protocol is being
invented at some hardware manufacturer. How do the people who work on
these actually go about inventing a new protocol?

What steps do they go through?

Any good books / websites that deal with this subject? (preferably
books)

Thanks in advance,

S Claus <santa at (no spam) temporaryinbox.com> writes:

here is a question that probably does not have an easy answer.

But I am curious about what happens when a new protocol is being
invented at some hardware manufacturer. How do the people who work on
these actually go about inventing a new protocol?

What steps do they go through?

Any good books / websites that deal with this subject? (preferably
books)

More than no easy answer, it doesn't even have a unique answer. When
you write a client/server application, you will develop a new protocol,
which may be as simple as "send me a packet with a sensor number, and
I'll answer with a packet with a sensor setting", or may be a particular
AJAX request/response pair.

It's really the same as how anything is developed: you figure out what
the requirements are, and you meet them. What's involved in doing that
is entirely situation-dependant.

--
As we enjoy great advantages from the inventions of others, we should
be glad of an opportunity to serve others by any invention of ours;
and this we should do freely and generously. (Benjamin Franklin)

"Joe Pfeiffer" <pfeif... at (no spam) cs.nmsu.edu> wrote in message
[snip]
we all know that all other options are meaningless when compared against the
incredible greatness of SOAP...

after all, SOAP is the one true protocol and is necessarily implemented,
even if it just so happens that both ends are incompatible due to being
implemented using different versions of the schema, this is merely an
"implementation detail" (in much the same way as that it is such low-level
details that software runs on computers, or that humans need food and air to
survive...).

(and in a condescending voice) the truely intellectual would not concern
themselves with such low-level details, and instead focus on the "bigger
picture", a world where software is not constrained to running on computers,
and humans can propel themselves into space and explore alien worlds via
little more than the immense powers of their own flatulence...

nevermind the ignorant masses and all their naysayers...

ok, not really, just a sort of an unrelated semi-rant in the above...

but, yes, how one will design a protocol, ... will depend highly on the type
of system being implemented, operating requirements, ...

so, it is not so much about any one-true-strategy, but the careful
consideration and weighting of the various factors involved (much as in many
complex systems). and, often, it may well make sense to allow the use of
multiple "competing" possibilities, serving as such to allow some level of
experimentation and weeding out options which do not work as well as ideal.

so, rather than pursue the ideal of genericness, one can pursue the ideal of
openness...

These days, though, if you want to achieve good interoperability, the
way to go is to propose the new protocol in an appropriate IETF
working group (go to www.ietf.org), hopefully get people interested in
that idea, and write it up in an Internet Draft. And go on from there.
If the I-D gathers followers, it would eventually become a Request for
Comments (RFC), and maybe eventually even a standard.

IPv6 could have been a lot more usable "right now" had a better means been
devised to embed it into IPv4 (among other issues...).

one such idea would be not using explicit tunnels and tunnel-brokering, and
instead using implicit tunnels.

for example:
routing information could be partially embedded into DNS (for example, via
name mangling, ...);

IPv6 network interfaces would export a public IPv4 address,

and otherwise behave in a manner similar to that of servers;

by IP. Or Windows LAN Manager, which was an internal Microsoft product
derived from a previous IBM protocol.

What I was referring to with this was a case similar to what happened
at Ericsson (nowadays part of SonyEricsson) when they started, in
1994, to work on finding a way to transmit data at a short range
without wires. This eventually lead to the creation of the Bluetooth
protocol.