PWG Mail Archive: Re: Closing down the Printer MIB

Re: Closing down the Printer MIB

JK Martin (jkm@underscore.com)
Thu, 26 Sep 96 18:36 EDT

Referencing Lloyd's recent posting:

> - Addition of new Channels Group (aka MagicCookie)
> Host Software groups feel that the simple group as proposed by
> David Kellerman would be sufficient for them.
> > My opinion is that this issue should wait until November so Jay and
> > Dave can join in the discussion of this issue.

Please, let's not wait until the November meeting to start resolving
this issue. Let's get this topic rolling on the mailing list.

The PWG has heard quite a bit in favor of this "MagicCookie" MIB object
from the host software side of the PWG, yet not very much against it
(other than the one posting sent third hand from Jeff Dunham).

Would all those _against_ the object please post your concerns so that
we can start resolving this issue before the November meeting?

> - Channel Type TC
> This was closed at the San Diego meeting but Jay Martin raised
> an issue on the mailing list that he still thought the
> definition might be wrong. Bob Setterbo and Bob Pentecost from
> Adobe and HP respectively were asked to respond from their
> companies.
> > My suggestion is to go with the following definitions. This appears
> > to be the best that we have unless we hear differently from Adobe
> > and HP.
> > chPort9100(11), -- Bi-directional printing protocol
> > -- utilizing TCP port 9101 for control
> > -- and TCP port 9100 for data.
> > AppSocket(12), -- a bi-directional, LPD-like
> > -- protocol using 9101 for
> > -- control and 9100 for data
> > -- Adobe Systems, Inc.

You know, I don't know whether to laugh or cry about this topic.

I just got off the phone with Ron Bergman (the original "author"
of the statement that the two definitions were reversed), and he
said he thought the issue was resolved after my last posting, and
that the *original* definitions should stand as is. (Ron should be
posting a statement shortly confirming this.)

This issue is dead. Cross it off the list. It is no more. It is
a non-issue. The original definitions--as authored by the respective
companies--should remain as documented in RFC-1759. (Hey, less work
for Randy!)

...jay