PWG> RE: Posted draft Printer Port Monitor MIB (10 Dec 2004)

PWG> RE: Posted draft Printer Port Monitor MIB (10 Dec 2004)

PWG> RE: Posted draft Printer Port Monitor MIB (10 Dec 2004)

McDonald, Ira imcdonald at sharplabs.com
Mon Dec 13 17:29:45 EST 2004


Hi Ron,

Replies inline below.

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald at sharplabs.com

-----Original Message-----
From: Bergman, Ron [mailto:Ron.Bergman at rpsa.ricoh.com]
Sent: Monday, December 13, 2004 4:28 PM
To: McDonald, Ira; pwg at pwg.org; Mike Fenelon; Ivan Pavicevic; Harry
Lewis
Subject: RE: Posted draft Printer Port Monitor MIB (10 Dec 2004)


Ira,

Its much better!  Some minor comments:

1. ppmGeneralNaturalLanguage SIZE(0..63):
   The actual max is currently 3. If a null string, this value
   must be at least 4.  I suggest 6 or 8.

<ira> This is NOT equivalent to 'prtLocalizationLanguage'
    Per IPP and Semantic Model, all new PWG std interfaces MUST
      support a full RFC 3066 'language tag' as follows:

   "The syntax of this tag in ABNF [RFC 2234] is:
    Language-Tag = Primary-subtag *( "-" Subtag )
    Primary-subtag = 1*8ALPHA
    Subtag = 1*8(ALPHA / DIGIT)"

    For example, "en-US"
</ira>


2. ppmGeneralNumberOfPorts:  Can't the DEFVAL be omitted without
   an explanation?

<ira>
I really dislike the theory that explanations should be deleted
</ira>


3. ppmPortProtocolType:  If the value is other(1), then it is
   specified as a protocol other than a defined type.  The note
   should be removed.

<ira>
There is no defined value for 'unknown' in 'PrtChannelTypeTC'.
There is an actual requirement in well-written MIBs to include
DEFVALs for all possible objects (part of SMIv2 standards).
</ira>


4. ppmPortProtocoPortNumber:  chIpp(42) should be removed since
   the target protocols are only LPR and RAW TCP.

<ira> No - this is a PWG standard MIB that can use ANY of the
    defined channel types, not just LPR or RAW.  The IPP example
    is appropriate (Harry Lewis suggested it!).
</ira>


5. ppmPortQueueName:  The LPR queue name cannot be unknown. The
   MS document originally defined the default as "LPR".

<ira>
The point is that it's unspecified, if empty.  The default queue
name in RFC 1179 is certainly not "LPR".
</ira>


6. ppmPortLprByteCountEnabled:  Add:  "Ignored if 
   'ppmPortProtocolType' is not 'chLPDServer(8)."

<ira>
OK!
</ira>

Some of the notes should be moved into the future introductory
text and others should just be merged into the DESCRIPTION
clause.  The 'notes:' should only be used only for information
that is not obvious to a well-informed reader and should be
used sparingly. 

<ira>
No - delete the word 'Note:', but these explanations belong in
the MIB - customers and users who have compiled this MIB ONLY
see the DESCRIPTION and REFERENCE clauses in their management
tools - the outside text is lost forever - and not available, 
since PWG standards are never published in plaintext.
</ira>


	Ron


-----Original Message-----
From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
Sent: Friday, December 10, 2004 12:29 PM
To: 'pwg at pwg.org'; 'Mike Fenelon'; Ivan Pavicevic; Bergman, Ron;
McDonald, Ira; Harry Lewis
Subject: Posted draft Printer Port Monitor MIB (10 Dec 2004)


Hi folks,                                      Friday (10 December 2004)

Based on comments from Mike, Ivan, Ron, and Harry, I have just posted a
second draft of the PWG Printer Port Monitor MIB at:

    ftp://ftp.pwg.org/pub/pwg/BOFs/port/tb-portmib10-20041210.mib

(Enclosing IEEE/ISTO PWG boilerplate will written after email comments
and our review on January 12 at the PWG face-to-face in Camas, WA.)

Comments?

Cheers,
- Ira

----------------------------------------
[change log included in MIB]

    REVISION        "0412100000Z" -- 10 December 2004 (v0.20)
    DESCRIPTION     "Second draft of PWG Printer Port Monitor MIB.
                    - added Ivan to editors (oversight in v0.10),
                      per request of Mike and Ivan;
                    - added IMPORT of 'PrtChannelTypeTC' from
                      IANA-PRINTER-MIB (first published in RFC 3805)
                      and changed SYNTAX of 'ppmPortProtocolType',
                      per request of Ron Bergman;
                    - renamed 'PpmTextStringTC' textual convention to
                      'PpmLocalizedStringTC' (for clarity);
                    - added 'ppmGeneralNumberOfPorts' to General group,
                      to align with Mike and Ivan's original draft;
                    - revised 'ppmPortProtocolType' to specify the IANA
                      Printer MIB as the authoritative source of values,
                      per request of Ron Bergman;
                    - revised 'ppmPortProtocolPortNumber' to specify
                      that, if zero, then the default port for the
                      current value of 'ppmPortProtocolType' is used,
                      per request of Harry Lewis;
                    - revised 'ppmPortIEEE1284DeviceId' to clarify more
                      format details and restricted characters,
                      per request of Mike and Ivan;
                    - moved 'ppmGeneralCommunityName' and renamed to
                      'ppmPortSnmpCommunityName' (for clarity),
                      to align with Mike and Ivan's original draft;
                    - renamed 'ppmPortStatusQueryEnabled' to
                      'ppmPortSnmpStatusQueryEnabled' (for clarity),
                      to align with Mike and Ivan's original draft;
                    - deleted 'ppmPortDescription' (redundant),
                      per request of Mike and Ivan;
                    - deleted 'ppmPortPrtChannelIndex' and
                      'ppmPortInterfaceIndex' (not necessary),
                      per request of Mike and Ivan."

    REVISION        "0411180000Z" -- 18 November 2004 (v0.10)
    DESCRIPTION     "First draft of PWG Printer Port Monitor MIB.
                    - content from Mike and Ivan's original draft and
                      a few proposed extensions."
----------------------------------------



More information about the Pwg mailing list