Thanks for your quick feedback. My replies inline below.
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:firstname.lastname@example.org]
> Sent: Tuesday, July 19, 2005 9:08 AM
> To: McDonald, Ira; 'email@example.com'
> Subject: RE: PMP> Restructured Port MIB (18 July 2005)
> Only did a very very quick scan.
> - ppmPortProtocolTargetPort OBJECT-TYPE
> SYNTAX Integer32 (0..65535)
> I propose that you use InetPortNumber TC from RFC4001
Won't work, because this port is not limited to Internet Suite
protocols. The 'service:' URI in ppmPortServiceNameOrURI may
also be for non-Internet suites (AppleTalk, NetWare, etc.).
I'll correct the DESCRIPTION in the MIB and make clear that
(as with the Printer MIB) ports/channels may be from multiple
> - ppmPortProtocolType OBJECT-TYPE
> SYNTAX Integer32 (0..2147483647)
> WHy not use TC PrtChannelTypeTC as the SYNTAX?
> I do see that you want to use zero (meaning not supported).
> But maybe better is to use none(1) in that case, or maybe
> adding an enumeration to the TC of notSupported(xx) ??
> It is now an IANA-maintained TC, so it should not be that
> difficult to get a label added.
Won't work. PrtChannelTypeTC currently only defines 'other(1)'
and (foolishly) does NOT define 'unknown(2)' (unlike every other
textual convention in the Printer MIB). Because the Printer MIB
v2 still doesn't define DEFVAL clauses for most objects, this
oversight has not surfaced before. We could register 'unknown(2)'
with IANA, but _not_ fast enough (because this MIB's going into OS
and printer vendor products right now).
> - ppmPortPrtChannelIndex has a reference to RFC1213, while I
> think I would reather reference RFC2863 (the current IF-MIB)
Agreed. My mistake from the old Printer MIB (RFC 1759).
I'll correct the references in the MIB.
This archive was generated by hypermail 2b29 : Tue Jul 19 2005 - 12:46:38 EDT