attachment-0001
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<TITLE>OID Registrations</TITLE>
<META content="MSHTML 6.00.2900.2523" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff
size=2>Ira,</FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff size=2>Note
that Don's proposal was constructed primarily of examples. The only real
assignment at that time</FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff size=2>was
2699.1.1 to the Job MIB. His example of 2699.1.1.1 and 2699.1.1.2 were
just examples as to how</FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff size=2>the
Job MIB could use the assignment. As I explained in the "actual current
assignments", the usage</FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff size=2>in the
MIB was somewhat different.</FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff size=2>The
Protocols arc was reserved in case an OID was ever needed for PWG protocols,
such as IPP. As</FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff size=2>you
pointed out, this has not been used. It may be a good idea to add IPP to
the Protocols registration</FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff
size=2>section. I don't recall if this was ever a formal proposal or just
another example. So the assignment</FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff size=2>tree
would then be:</FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff size=2><FONT
color=#000000>......2699.1........ MIBS<BR>..... 2699.1.1....... Job Monitoring
MIB (jobMonMIB, RFC 2707)<BR>..... 2699.1.2....... Port Monitor MIB
(ppmMIB, TBA)<BR>..... 2699.1.3....... (TBA)<BR>......2699.2........
PROTOCOLS<BR>..... 2699.2.1....... Internet Printing Protocol (IPP, RFC 2910,
2911)</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT color=#0000ff size=2><FONT
face=Arial><FONT color=#000000>..... 2699.2.1.1 ..... IPP Operations<BR>.....
2699.2.1.2 ..... IPP Attributes<BR>..... 2699.2.2....... (TBA)<BR>.....
2699.3....... (TBA)</FONT><BR><BR>I am sure that Jerry will take the initiative,
when he returns from Japan, to make this information
available</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff size=2>in an
obvious place on the PWG FTP site. (He indicated in the call that it was
part of his task as secretary.)</FONT></SPAN></DIV>
<DIV><SPAN class=154253015-15042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=154253015-15042005> <FONT face=Arial
color=#0000ff size=2>Ron</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> McDonald, Ira
[mailto:imcdonald@sharplabs.com]<BR><B>Sent:</B> Friday, April 15, 2005 8:20
AM<BR><B>To:</B> Bergman, Ron; thrasher@lexmark.com<BR><B>Cc:</B> Harry Lewis
(E-mail); McDonald, Ira; pmp@pwg.org<BR><B>Subject:</B> RE: OID
Registrations<BR><BR></FONT></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff size=4>Hi
Ron,</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff size=4>Glad
you could find Don's email. I spent a long time searching the PWG
server</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff size=4>in
HTTP and FTP without finding anything yesterday.</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff size=4>By
the way, Don's original proposal that put Job MIB down two-levels was
formally</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff
size=4>invalid. When the IETF designates an arc for an enterprise (e.g.,
'pwg(2699)),</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff size=4>an
immediate subordinate arc must contains MIB module registrations
(remember</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff size=4>the
parent arc belongs to the IETF, who get to make the MIB
rules).</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff size=4>NONE
of the other uses (Protocols, IPP, etc.) have ever
materialized.</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff size=4>The
eventual OID registrations document SHOULD be in plaintext and
stored</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff size=4>in
'pub/pwg/general/registrations' (or some similarly obvious sub-directory
of</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff
size=4>'pub/pwg/general'.</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff
size=4>Cheers,</FONT></SPAN></DIV>
<DIV><SPAN class=496541515-15042005><FONT face=Arial color=#0000ff size=4>-
Ira</FONT></SPAN></DIV>
<DIV> </DIV>
<P><FONT size=2>Ira McDonald (Musician / Software Architect)<BR>Blue Roof
Music / High North Inc<BR>PO Box 221 Grand Marais, MI
49839<BR>phone: +1-906-494-2434<BR>email: imcdonald@sharplabs.com</FONT> </P>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Bergman, Ron
[mailto:Ron.Bergman@rpsa.ricoh.com]<BR><B>Sent:</B> Thursday, April 14, 2005
2:25 PM<BR><B>To:</B> thrasher@lexmark.com<BR><B>Cc:</B> Harry Lewis
(E-mail); Ira McDonald (E-mail 3); pmp@pwg.org<BR><B>Subject:</B> OID
Registrations<BR><BR></FONT></DIV><!-- Converted from text/rtf format -->
<P><FONT face=Arial size=2>Jerry,</FONT> </P>
<P><FONT face=Arial size=2>I found the Email from Don with the OID
allocation proposal but I cannot</FONT> <BR><FONT face=Arial size=2>find in
any of the minutes where it was approved and who was to create
</FONT><BR><FONT face=Arial size=2>the registration document. I recall
it being discussed in a meeting but</FONT> <BR><FONT face=Arial size=2>do
not remember if anyone was assigned to followup.</FONT> </P>
<P><FONT face=Arial size=2>From Don's email in the JMP archives dated 14 Nov
1997, subject:</FONT> <BR><FONT face=Arial size=2>"Job MIB - trials and
tribulations"</FONT> </P>
<P><FONT face="Courier New" size=2>To be consistant, we might even want to
do something like:</FONT> <BR><FONT face="Courier New"
size=2>......2699.1........ MIBS<BR>..... 2699.1.1.1...... Job Mib<BR>.....
2699.1.1.2 ..... Future Job Mib extensions<BR>..... 2699.1.2.1 .....
Finisher Mib<BR>..... 2699.1.2.2 ..... Finisher Mib extensions<BR>.....
2699.1.3.1 ..... Hey, how about... Printer Mib<BR>..... 2699.1.3.2 .....
Printer MIB extensions<BR>..... 2699.1.3.2 ..... Printer MIB
extensions<BR>......2699.2........ PROTOCOLS<BR>......2699.2.1......
IPP<BR>..... 2699.2.1.1 ..... IPP Operations (as suggested by someone,
below)<BR>..... 2699.2.1.2 ..... IPP Attributes<BR>......2699.2.2.......
Some Other Protocol<BR>......2699.3........
SOMETHING_ELSE_BESIDES_MIBS_AND_PROTOCOLS</FONT> <BR><FONT face=Arial
size=2>The actual current official assignments are:</FONT> <BR><FONT
face=Arial size=2>......2699.1........ MIBS<BR>..... 2699.1.1.......
jobMonMIB<BR>..... 2699.1.1.1...... jobmonMIBObjects<BR>..... 2699.1.1.2
..... jobmonMIBNotifications<BR>..... 2699.1.1.2 .....
jobmonMIBConformance<BR>..... 2699.1.2....... Port Monitor
MIB<BR>......2699.2........ PROTOCOLS<BR></FONT><BR><FONT face=Arial
size=2>where the third level is assigned by the project, not the PWG.</FONT>
</P>
<P><FONT face=Arial size=2>So the present PWG OID assignment tree is:</FONT>
</P>
<P><FONT face=Arial size=2>......2699.1........ MIBS<BR>.....
2699.1.1....... Job Monitoring MIB (jobMonMIB, RFC 2707)<BR>.....
2699.1.2....... Port Monitor MIB (ppmMIB, TBA)<BR>.....
2699.1.3....... (TBA)<BR>......2699.2........ PROTOCOLS<BR>.....
2699.2.2....... (TBA)<BR>..... 2699.3....... (TBA)<BR></FONT><BR><FONT
face=Arial size=2>Now, all we need is a home for this information.</FONT>
</P>
<P> <FONT face=Arial
size=2>Ron</FONT> </P><BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>