Mail Index

• Thread Index

• Re: DateAndTime TC oversight in RFC 2579
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: DateAndTime TC oversight in RFC 2579
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: DateAndTime TC oversight in RFC 2579
  • From: "C. M. Heard" <heard@pobox.com>
• RE: DateAndTime TC oversight in RFC 2579
  • From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
• RE: Volunteer MIB Dcotor: Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Server MIB' to Proposed Standard
  • From: "Glenn Waters" <gww@nortelnetworks.com>
• RE: DateAndTime TC oversight in RFC 2579
  • From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
• Re: DateAndTime TC oversight in RFC 2579
  • From: "C. M. Heard" <heard@pobox.com>
• Re: DateAndTime TC oversight in RFC 2579
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• DateAndTime TC oversight in RFC 2579
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Volunteer MIB Dcotor: Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Server MIB' to Proposed Standard
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: Last Call: 'Operational Security Requirements for IP Netw ork Infrastructure' to BCP
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: FW: Last Call: 'Operational Security Requirements for IP Network Infrastructure' to BCP
  • From: "C. M. Heard" <heard@pobox.com>
• FW: Last Call: 'Operational Security Requirements for IP Network Infrastructure' to BCP
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: [ipv6mib] Re: MIB topic in draft-ietf-ipv6-node-requirements- 07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: [ipcdn] MIB reviewer comments on draft-ietf-ipcdn-device-mibv2-06.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: [ipcdn] MIB reviewer comments on draft-ietf-ipcdn-device-mibv2-06.txt
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: MIB topic in draft-ietf-ipv6-node-requirements-07.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: MIB topic in draft-ietf-ipv6-node-requirements-07.txt
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: MIB topic in draft-ietf-ipv6-node-requirements-07.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: MIB topic in draft-ietf-ipv6-node-requirements-07.txt
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• MIB topic in draft-ietf-ipv6-node-requirements-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Illegal MODULE-IDENTITY value assignments in draft PWE3 MIB Modules
  • From: "C. M. Heard" <heard@pobox.com>
• RE: MIB Doctor (architectural) review needed
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: MIB Doctor (architectural) review needed
  • From: "C. M. Heard" <heard@pobox.com>
• FW: Agenda and Package for December 18, 2003 Telechat
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Editorial comments on draft-ietf-pwe3-arch-06.txt Section 8 (was: MIB Doctor (architectural) review needed)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Volunteer MIB Dcotor: Dynamic Host Configuration Protocol for IPv 4 (DHCPv4) Server MIB' to Proposed Standard
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Volunteer MIB Dcotor: Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Server MIB' to Proposed Standard
  • From: "Harrington, David" <dbh@enterasys.com>
• Volunteer MIB Dcotor: Dynamic Host Configuration Protocol for IPv 4 (DHCPv4) Server MIB' to Proposed Standard
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: [ifmib] IANAifType-MIB issue
  • From: "C. M. Heard" <heard@pobox.com>
• FW: IANAifType-MIB issue
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• MIB Doctor (architectural) review needed
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Agenda and Package for December 4, 2003 Telechat
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Agenda and Package for December 4, 2003 Telechat
  • From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
• Re: FW: Agenda and Package for December 4, 2003 Telechat
  • From: "C. M. Heard" <heard@pobox.com>
• FW: Agenda and Package for December 4, 2003 Telechat
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• FW: Agenda and Package for November 20, 2003 Telechat
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Returning zero or empty string for unsupported objects
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Returning zero or empty string for unsupported objects
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: Returning zero or empty string for unsupported objects
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Volunteer to be at RADIUSEXT meeting on Friday
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Returning zero or empty string for unsupported objects
  • From: Andy Bierman <abierman@cisco.com>
• RE: Returning zero or empty string for unsupported objects
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Returning zero or empty string for unsupported objects
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Returning zero or empty string for unsupported objects
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: Returning zero or empty string for unsupported objects
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Returning zero or empty string for unsupported objects
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RE: Returning zero or empty string for unsupported objects
  • From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
• Re: Returning zero or empty string for unsupported objects
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Returning zero or empty string for unsupported objects
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• IANA MIB copyright update (WAS: Protocol Action: 'IETF Rights in Contributions' to BCP)
  • From: "C. M. Heard" <heard@pobox.com>
• FW: MIB experts to VRRP WG meeting
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• IESG telechat Agenda and Package for October 30, 2003
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Redundant objects
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Redundant objects
  • From: "Dave Thaler" <dthaler@windows.microsoft.com>
• Re: Redundant objects
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Redundant objects
  • From: "Dave Thaler" <dthaler@windows.microsoft.com>
• Re: FW: Discuss on draft-ietf-adslmib-hc-tc-06.txt
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: draft-ietf-tewg-mib-07.txt
  • From: "Dave Thaler" <dthaler@windows.microsoft.com>
• RE: FW: draft-ietf-tewg-mib-07.txt
  • From: "Dave Thaler" <dthaler@windows.microsoft.com>
• Re: FW: Discuss on draft-ietf-adslmib-hc-tc-06.txt
  • From: "C. M. Heard" <heard@pobox.com>
• FW: The IPSEC MIB documents
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: Discuss on draft-ietf-adslmib-hc-tc-06.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: FW: Discuss on draft-ietf-adslmib-hc-tc-06.txt
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: FW: FW: Discuss on draft-ietf-adslmib-hc-tc-06.txt
  • From: "C. M. Heard" <heard@pobox.com>
• FW: FW: Discuss on draft-ietf-adslmib-hc-tc-06.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: FW: draft-ietf-tewg-mib-07.txt
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• RE: FW: draft-ietf-tewg-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: FW: draft-ietf-tewg-mib-07.txt
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• Re: Volunteers wanted for MIB Doctor reviews
  • From: "C. M. Heard" <heard@pobox.com>
• FW: draft-ietf-tewg-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Volunteers wanted for MIB Doctor reviews
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• IESG Agenda and Package for October 16, 2003 Telechat
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• offline for 3 days
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Anotehr doc for this Thrusday's IESG call
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Anotehr doc for this Thrusday's IESG call
  • From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
• Anotehr doc for this Thrusday's IESG call
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Agenda and Package for October 2, 2003 Telechat
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Agenda and Package for October 2, 2003 Telechat
  • From: "Glenn Waters" <gww@nortelnetworks.com>
• FW: Agenda and Package for October 2, 2003 Telechat
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• New MIB Doctor added
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: MIB module root assignment
  • From: Frank Strauß <strauss@ibr.cs.tu-bs.de>
• Re: MIB module root assignment
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• RE: MIB module root assignment
  • From: Andy Bierman <abierman@cisco.com>
• RE: MIB module root assignment
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RE: MIB module root assignment
  • From: "C. M. Heard" <heard@pobox.com>
• RE: MIB module root assignment
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: MIB module root assignment
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: MIB module root assignment
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: MIB module root assignment
  • From: "C. M. Heard" <heard@pobox.com>
• Re: MIB module root assignment
  • From: Harrie Hazewinkel <harrie@lisanza.net>
• RE: MIB module root assignment
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: MIB module root assignment
  • From: "Glenn Waters" <gww@nortelnetworks.com>
• RE: MIB module root assignment
  • From: "Harrington, David" <dbh@enterasys.com>
• Re: MIB module root assignment
  • From: Andy Bierman <abierman@cisco.com>
• Re: MIB module root assignment
  • From: "C. M. Heard" <heard@pobox.com>
• Re: MIB module root assignment
  • From: Andy Bierman <abierman@cisco.com>
• Re: MIB module root assignment
  • From: "C. M. Heard" <heard@pobox.com>
• RE: MIB module root assignment
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• MIB module root assignment
  • From: Andy Bierman <abierman@cisco.com>
• Re: Sanity check on StorageType
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• RE: Sanity check on StorageType
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Sanity check on StorageType
  • From: Harrie Hazewinkel <harrie@lisanza.net>
• Sanity check on StorageType
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Advancing RFC 2864 (IF-INVERTED-STACK-MIB)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: 484 octet limit (was: new feature in smilint?)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: 484 octet limit (was: new feature in smilint?)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: 484 octet limit (was: new feature in smilint?)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: new feature in smilint?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: new feature in smilint?
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• new feature in smilint?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: New MIB review guidelines draft now available
  • From: "C. M. Heard" <heard@pobox.com>
• RE: New MIB review guidelines draft now available
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• New MIB review guidelines draft now available
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Personal Invitation to comment on IEEE 802.17 Working Group Ballot
  • From: Mike Takefman <tak@cisco.com>
• RE: Personal Invitation to comment on IEEE 802.17 Working Group Ballo t
  • From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
• FW: Personal Invitation to comment on IEEE 802.17 Working Group Ballo t
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: MIB doctor reviews and common format for RFC Editor Notes
  • From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
• RE: MIB doctor reviews and common format for RFC Editor Notes
  • From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
• RE: MIB doctor reviews and common format for RFC Editor Notes
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: MIB doctor reviews and common format for RFC Editor Notes
  • From: "C. M. Heard" <heard@pobox.com>
• RE: draft-ietf-ops-mib-review-guidelines-02a.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• draft-ietf-ops-mib-review-guidelines-02a.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Proposed wordsmithing to notification throttling guideline
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Proposed wordsmithing to notification throttling guideline
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Proposed changes to MIB review guidelines checklist (Appendix A)
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: Proposed wordsmithing to notification throttling guideline
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• FW: Working group Last Call on MPLS base MIBs
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Proposed wordsmithing to notification throttling guideline
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Proposed changes to MIB review guidelines checklist (Appendix A)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Proposed OID layout update text in guidelines doc
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Proposed change to guidelines 4.6.1.10 ("Other Data Types")
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Eliminating Appendices B and C
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Eliminating Appendices B and C
  • From: Andy Bierman <abierman@cisco.com>
• Proposed change to guidelines 4.6.1.10 ("Other Data Types")
  • From: "C. M. Heard" <heard@pobox.com>
• Eliminating Appendices B and C
  • From: "C. M. Heard" <heard@pobox.com>
• Proposed changes to MIB review guidelines checklist (Appendix A)
  • From: "C. M. Heard" <heard@pobox.com>
• Proposed wordsmithing to notification throttling guideline
  • From: "C. M. Heard" <heard@pobox.com>
• Proposed OID layout update text in guidelines doc
  • From: "C. M. Heard" <heard@pobox.com>
• Example for OID layout appendix in MIB review guidelines
  • From: "C. M. Heard" <heard@pobox.com>
• Re: How to specify InetAddressType COMPLIANCE requirements
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• Pls check if there are any showstoppers in draft-ietf-mpls-ftn-mib-08.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Thomas D. Nadeau" <tnadeau@cisco.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Cheenu Srinivasan" <cheenu_srinivasan@hotmail.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Cheenu Srinivasan" <cheenu_srinivasan@hotmail.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Cheenu Srinivasan" <cheenu_srinivasan@hotmail.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Thomas D. Nadeau" <tnadeau@cisco.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Thomas D. Nadeau" <tnadeau@cisco.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• MIB review guidelines ptr added to: http://www.ietf.org/IESG/wgchairs.html
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Thomas D. Nadeau" <tnadeau@cisco.com>
• Re: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Cheenu Srinivasan" <cheenu_srinivasan@hotmail.com>
• Re: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Cheenu Srinivasan" <cheenu_srinivasan@hotmail.com>
• Re: How to specify InetAddressType COMPLIANCE requirements
  • From: "C. M. Heard" <heard@pobox.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Cheenu Srinivasan" <cheenu_srinivasan@hotmail.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• FW: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: How to specify InetAddressType COMPLIANCE requirements
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "Cheenu Srinivasan" <cheenu_srinivasan@hotmail.com>
• RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• Re: How to specify InetAddressType COMPLIANCE requirements
  • From: "C. M. Heard" <heard@pobox.com>
• How to specify InetAddressType COMPLIANCE requirements
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Volunteers needed for IPCDN wg: prioritized list of IDs for MIB doctor review
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Volunteers needed for IPCDN wg: prioritized list of IDs for MIBdoctor review
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Adding PhysicalIndex/PhysicalIndexOrZero to guidelines Append ix D
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• FW: WG Last Call: a batch of draft-ietf-v6ops-ipv4survey-*01 documents (fwd)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: making a display hint RECOMMENDED in non-enum TCs
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: making a display hint RECOMMENDED in non-enum TCs
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• Re: Adding PhysicalIndex/PhysicalIndexOrZero to guidelines Append ix D
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• Re: making a display hint RECOMMENDED in non-enum TCs
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Adding PhysicalIndex/PhysicalIndexOrZero to guidelines Appendix D
  • From: "C. M. Heard" <heard@pobox.com>
• Re: adding suggested naming conventions for extension modules
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• Re: Adding PhysicalIndex/PhysicalIndexOrZero to guidelines Appendix D
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• Re: making a display hint RECOMMENDED in non-enum TCs
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• RE: Adding PhysicalIndex/PhysicalIndexOrZero to guidelines Appendix D
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: allowing revisions of labels to correct typos
  • From: "C. M. Heard" <heard@pobox.com>
• text for removal of reduntant size/range constraints
  • From: "C. M. Heard" <heard@pobox.com>
• allowing revisions of labels to correct typos
  • From: "C. M. Heard" <heard@pobox.com>
• adding suggested naming conventions for extension modules
  • From: "C. M. Heard" <heard@pobox.com>
• making a display hint RECOMMENDED in non-enum TCs
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines changes to date (WAS: comments on mib review guidelines01)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Apendices B and C (Was: RE: comments on mib review guidelines01)
  • From: "C. M. Heard" <heard@pobox.com>
• Adding PhysicalIndex/PhysicalIndexOrZero to guidelines Appendix D
  • From: "C. M. Heard" <heard@pobox.com>
• guidelines sec. 3.8 proposed text
  • From: "C. M. Heard" <heard@pobox.com>
• Volunteers needed for IPCDN wg: prioritized list of IDs for MIB doctor review
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• guidelines changes to date (WAS: comments on mib review guidelines01)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: comments on mib review guidelines 01 - draft-ietf-ops-mib-review-guidelines-XX-20030707.txt
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• Re: comments on mib review guidelines 01 -draft-ietf-ops-mib-review-guidelines-XX-20030707.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: comments on mib review guidelines 01 - draft-ietf-ops-mib-review-guidelines-XX-20030707.txt
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: comments on mib review guidelines 01 - draft-ietf-ops-mib-review-guidelines-XX-20030707.txt
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: comments on mib review guidelines 01 - draft-ietf-ops-mib-review-guidelines-XX-20030707.txt
  • From: Juergen Schoenwaelder - International University Bremen <j.schoenwaelder@merkur.iu-bremen.de>
• Re: comments on mib review guidelines 01 - draft-ietf-ops-mib-rev iew-guidelines-XX-20030707.txt
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: comments on mib review guidelines 01 - draft-ietf-ops-mib-review-guidelines-XX-20030707.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Problematic revisions in RFC 2515 (ATM-MIB rev. 9810191200Z) (fwd)
  • From: "C. M. Heard" <heard@pobox.com>
• Volunteers for MIB Doctor review
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• guidelines changes to date (WAS: comments on mib review guidelines01)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: comments on mib review guidelines 01
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Apendices B and C (Was: RE: comments on mib review guidelines 01)
  • From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
• Re: comments on mib review guidelines 01
  • From: "C. M. Heard" <heard@pobox.com>
• RE: comments on mib review guidelines 01
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• comments on mib review guidelines 01
  • From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
• Re: indexing scheme in draft-ietf-rohc-mib-rtp-06.txt
  • From: Andy Bierman <abierman@cisco.com>
• indexing scheme in draft-ietf-rohc-mib-rtp-06.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Guidelines Document and Optional Groups
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: Guidelines Document and Optional Groups
  • From: "Sharon Chisholm" <schishol@nortelnetworks.com>
• FW: MIB doctor assignments
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: MIB Doctor review
  • From: Allison Mankin <mankin@psg.com>
• Re: FW: prequeal to WG lat call om the LSR mib module
  • From: "C. M. Heard" <heard@pobox.com>
• Re: MIB Doctor review
  • From: "C. M. Heard" <heard@pobox.com>
• MIB Doctor review
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Design pattern (fwd)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Design pattern
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: Design pattern
  • From: "C. M. Heard" <heard@pobox.com>
• FW: prequeal to WG lat call om the LSR mib module
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Request For MIB Review (WAS: Design pattern)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Design pattern
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Design pattern
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• I will be on vacation till June 30th
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Design pattern
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10e included
  • From: "Maria-Carmen Belinchon-Vergara (ECE)" <maria-carmen.belinchon-vergara@ece.ericsson.se>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10e included
  • From: "Peterson, Jon" <jon.peterson@neustar.biz>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10e included
  • From: "C. M. Heard" <heard@pobox.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10e included
  • From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10d included
  • From: "C. M. Heard" <heard@pobox.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10d included
  • From: "Maria-Carmen Belinchon-Vergara (ECE)" <maria-carmen.belinchon-vergara@ece.ericsson.se>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10c included
  • From: "Maria-Carmen Belinchon-Vergara (ECE)" <maria-carmen.belinchon-vergara@ece.ericsson.se>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10c included
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10b included
  • From: "Maria-Carmen Belinchon-Vergara (ECE)" <maria-carmen.belinchon-vergara@ece.ericsson.se>
• FW: Recruitment of Experimental SIRs
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10b included
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10b included
  • From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10b included
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt
  • From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
• Re: FW: Request For MIB Review
  • From: "C. M. Heard" <heard@pobox.com>
• FW: Request For MIB Review
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt
  • From: "Maria-Carmen Belinchon-Vergara (ECE)" <maria-carmen.belinchon-vergara@ece.ericsson.se>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Guidelines Document and Optional Groups
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Guidelines Document and Optional Groups
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Guidelines Document and Optional Groups
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Guidelines Document and Optional Groups
  • From: "C. M. Heard" <heard@pobox.com>
• Re: FW: FlowId and FlowIdOrAny
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: Guidelines Document and Optional Groups
  • From: Andy Bierman <abierman@cisco.com>
• Re: Guidelines Document and Optional Groups
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• Re: Guidelines Document and Optional Groups
  • From: Andy Bierman <abierman@cisco.com>
• Guidelines Document and Optional Groups
  • From: "Sharon Chisholm" <schishol@nortelnetworks.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt
  • From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
• FW: FW: FlowId and FlowIdOrAny
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Question on RowStatus
  • From: "Thomas D. Nadeau" <tnadeau@cisco.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt
  • From: "C. M. Heard" <heard@pobox.com>
• RE: FW: draft-ietf-sigtran-sctp-mib-09.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Question on RowStatus
  • From: John Flick <johnf@rose.hp.com>
• Re: Question on RowStatus (StorageType)
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RE: Question on RowStatus
  • From: "Thomas D. Nadeau" <tnadeau@cisco.com>
• Re: FW: draft-ietf-sigtran-sctp-mib-09.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Question on RowStatus
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: Question on RowStatus
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Question on RowStatus
  • From: "Harrington, David" <dbh@enterasys.com>
• Re: Question on RowStatus
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: Question on RowStatus
  • From: Harrie Hazewinkel <harrie@lisanza.net>
• Question on RowStatus
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• FW: draft-ietf-sigtran-sctp-mib-09.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Question on InetAddressType
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Question on InetAddressType
  • From: Andy Bierman <abierman@cisco.com>
• Question on InetAddressType
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Last Call: Stream Control Transmission Protocol Management In formation Base to Proposed Standard
  • From: "C. M. Heard" <heard@pobox.com>
• Re: host-resources
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• host-resources
  • From: "Harrington, David" <dbh@enterasys.com>
• draft-ietf-sigtran-sctp-mib-09.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Last Call: Stream Control Transmission Protocol Management In formation Base to Proposed Standard
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Last Call: Stream Control Transmission Protocol Management Information Base to Proposed Standard
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Last Call: Stream Control Transmission Protocol Management In formation Base to Proposed Standard
  • From: Harrie Hazewinkel <harrie@lisanza.net>
• RE: Last Call: Stream Control Transmission Protocol Management Information Base to Proposed Standard
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: ipsp-policy-pib
  • From: "C. M. Heard" <heard@pobox.com>
• Re: ipsp-policy-pib
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• RE: ipsp-policy-pib
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: ipsp-policy-pib
  • From: "Harrington, David" <dbh@enterasys.com>
• ipsp-policy-pib
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: OID value assigned to MODULE-IDENTITY invocation
  • From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
• RE: MIB module terminology
  • From: Andy Bierman <abierman@cisco.com>
• RE: MIB module terminology
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RE: MIB module terminology
  • From: "Harrington, David" <dbh@enterasys.com>
• Re: MIB module terminology
  • From: Harrie Hazewinkel <harrie@lisanza.net>
• RE: MIB module terminology
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: MIB module terminology
  • From: Andy Bierman <abierman@cisco.com>
• Re: MIB module terminology
  • From: "C. M. Heard" <heard@pobox.com>
• MIB module terminology
  • From: Andy Bierman <abierman@cisco.com>
• Re: Important question about draft-ietf-ipsec-doi-tc-mib-07.txt(fwd)
  • From: "C. M. Heard" <heard@pobox.com>
• FW: FW: OID value assigned to MODULE-IDENTITY invocation
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• FW: OID value assigned to MODULE-IDENTITY invocation
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: augmenting std MIBs to use TransportAddress
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• augmenting std MIBs to use TransportAddress
  • From: Andy Bierman <abierman@cisco.com>
• Re: Last Call: Stream Control Transmission Protocol ManagementInformation Base to Proposed Standard
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Last Call: Stream Control Transmission Protocol Management Information Base to Proposed Standard
  • From: Harrie Hazewinkel <harrie@lisanza.net>
• Re: Fwd: Last Call: Stream Control Transmission Protocol Management Information Base to Proposed Standard
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: Fwd: Last Call: Stream Control Transmission Protocol Management Information Base to Proposed Standard
  • From: "C. M. Heard" <heard@pobox.com>
• Fwd: Last Call: Stream Control Transmission Protocol Management Information Base to Proposed Standard
  • From: Harrie Hazewinkel <harrie@lisanza.net>
• Re: OID value assigned to MODULE-IDENTITY invocation
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• OID value assigned to MODULE-IDENTITY invocation
  • From: "C. M. Heard" <heard@pobox.com>
• Fwd: Last Call: Stream Control Transmission Protocol Management Information Base to Proposed Standard
  • From: Harrie Hazewinkel <harrie@jumpy.it>
• offline for a few days
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Important question about draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Important question about draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• Re: Important question about draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Important question about draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: Important question about draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: Andy Bierman <abierman@cisco.com>
• Re: Important question about draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Important question about draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: Important question about draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• FW: Important question about draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "C. M. Heard" <heard@pobox.com>
• FW: [IPORPR] RPR MIB question
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Telechat agenda topic: IANA MIB Copyright
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Telechat agenda topic: IANA MIB Copyright
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Volunteer for MIB Doctor review draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Volunteer for MIB Doctor review draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: FW: Question regarding address specs for IPv4-only protocol MIBs
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Volunteer for MIB Doctor review draft-ietf-ipsec-doi-tc-mib-07.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: FW: Question regarding address specs for IPv4-only protocolM IBs
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: FW: Question regarding address specs for IPv4-only protocol MIBs
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: FW: Question regarding address specs for IPv4-only protocol MIBs
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: the MIB review document
  • From: "C. M. Heard" <heard@pobox.com>
• the MIB review document
  • From: Harrie Hazewinkel <harrie@lisanza.net>
• Re: AD Review of draft-ietf-disman-alarm-mib-09.txt
  • From: Harrie Hazewinkel <harrie@lisanza.net>
• AD Review of draft-ietf-disman-alarm-mib-09.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: PerfHist counters
  • From: "C. M. Heard" <heard@pobox.com>
• RE: PerfHist counters
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• PerfHist counters
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: SNMP/MIB advisor for IDR WG
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: InetAddress
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• FW: Last Call: Instructions to Request for Comments (RFC) Authorsto BCP
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Possible Addition to MIB Doctors description page
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Possible Addition to MIB Doctors description page
  • From: "C. M. Heard" <heard@pobox.com>
• Re: InetAddress
  • From: "C. M. Heard" <heard@pobox.com>
• Re: FW: Question regarding address specs for IPv4-only protocol MIBs
  • From: "C. M. Heard" <heard@pobox.com>
• InetAddress
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: Question regarding address specs for IPv4-only protocol MIBs
  • From: "Glenn Waters" <gww@nortelnetworks.com>
• FW: Question regarding address specs for IPv4-only protocol MIBs
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: diverging views on adding range constraints in MIB module rev isions
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: diverging views on adding range constraints in MIB module rev isions
  • From: Andy Bierman <abierman@cisco.com>
• RE: diverging views on adding range constraints in MIB module revisions
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: diverging views on adding range constraints in MIB modulerevisions
  • From: "C. M. Heard" <heard@pobox.com>
• Re: diverging views on adding range constraints in MIB module revisions
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: registration OIDs: standardization
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• draft-ietf-ops-mib-review-guidelines-01.txt (fwd)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: registration OIDs: standardization
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: registration OIDs: standardization
  • From: "C. M. Heard" <heard@pobox.com>
• RE: registration OIDs: standardization
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: registration OIDs: standardization
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: registration OIDs: standardization
  • From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
• RE: registration OIDs: standardization
  • From: Andy Bierman <abierman@cisco.com>
• RE: registration OIDs: standardization
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: registration OIDs: do the values matter?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: registration OIDs: do the values matter?
  • From: "C. M. Heard" <heard@pobox.com>
• RE: diverging views on adding range constraints in MIB modulerevisions
  • From: "C. M. Heard" <heard@pobox.com>
• RE: registration OIDs: standardization
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: registration OIDs: do the values matter?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: diverging views on adding range constraints in MIB module revisions
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: registration OIDs: standardization
  • From: Harrie Hazewinkel <harrie@lisanza.net>
• registration OIDs: standardization
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: registration OIDs: do the values matter?
  • From: "C. M. Heard" <heard@pobox.com>
• diverging views on adding range constraints in MIB module revisions
  • From: "C. M. Heard" <heard@pobox.com>
• RE: registration OIDs: do the values matter?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: registration OIDs: do the values matter?
  • From: Andy Bierman <abierman@cisco.com>
• RE: registration OIDs: do the values matter?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: registration OIDs: do the values matter?
  • From: Andy Bierman <abierman@cisco.com>
• Re: registration OIDs: do the values matter?
  • From: "C. M. Heard" <heard@pobox.com>
• registration OIDs: do the values matter?
  • From: Andy Bierman <abierman@cisco.com>
• RE: Telechat agenda topic: IANA MIB Copyright
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Telechat agenda topic: Does an IANA maintained MIB require an RFC ?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Naming Conventions for Descriptors (was: comments/review<draft-ietf-ops-mib-review-guidelines-00.txt>)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Naming Conventions for Descriptors (was: comments/review<draft-ietf-ops-mib-review-guidelines-00.txt>)
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: Telechat agenda topic: Does an IANA maintained MIB require anRFC ?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Telechat agenda topic: IANA MIB Copyright
  • From: "C. M. Heard" <heard@pobox.com>
• Telechat agenda topic: IANA MIB Copyright
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Telechat agenda topic: Does an IANA maintained MIB require an RFC?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Naming Conventions for Descriptors (was: comments/review<draft-ietf-ops-mib-review-guidelines-00.txt>)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Naming Conventions for Descriptors (was: comments/review<draft-ietf-ops-mib-review-guidelines-00.txt>)
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• RE: Naming Conventions for Descriptors (was: comments/review <draft-ietf-ops-mib-review-guidelines-00.txt>)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Naming Conventions for Descriptors (was: comments/review<draft-ietf-ops-mib-review-guidelines-00.txt>)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: ID-nits
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: ID-nits
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• RE: time to say "good enough"?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: ID-nits
  • From: "C. M. Heard" <heard@pobox.com>
• Re: ID-nits
  • From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
• Re: ID-nits
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: Section 4.6.5 [was: 4.5] OID size limits
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RE: time to say "good enough"?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Section 4.6.5 [was: 4.5] OID size limits
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: should guidelines say something about NOT using IMPLIED?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: time to say "good enough"?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Section 4.6.5 [was: 4.5] OID size limits
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: FW: I-D ACTION:draft-ietf-ops-mib-review-guidelines-00.txt
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Section 4.6.5 [was: 4.5] OID size limits
  • From: "C. M. Heard" <heard@pobox.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: Extensible TCs (WAS: Compliance Statements)
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: Extensible TCs (WAS: Compliance Statements)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Guidelines Section 4.6.4 (OID Values Assigned to Objects)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Guidelines Section 4.6.4 (OID Values Assigned to Objects)
  • From: Michael Kirkham <mikek@muonics.com>
• RE: Guidelines Section 4.6.4 (OID Values Assigned to Objects)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Extensible TCs (WAS: Compliance Statements)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Extensible TCs (WAS: Compliance Statements)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Guidelines Section 4.6.4 (OID Values Assigned to Objects)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Compliance Statements
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Guidelines Section 4.6.1.6 (BITS construct)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Guidelines Section 4.6.1.6 (BITS construct)
  • From: Michael Kirkham <mikek@muonics.com>
• Re: Guidelines Section 4.6.1.6 (BITS construct)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Compliance Statements
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Compliance Statements
  • From: Andy Bierman <abierman@cisco.com>
• Re: Compliance Statements
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Compliance Statements
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• Re: Compliance Statements
  • From: "C. M. Heard" <heard@pobox.com>
• ID-nits
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: comments/review <draft-ietf-ops-mib-review-guidelines-00.txt>
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Compliance Statements
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: printermib - problems other than compliances
  • From: "C. M. Heard" <heard@pobox.com>
• Re: IANA MIBs and copyrights ... some ideas (was: printermib - problems other than compliances)
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• IANA MIBs and copyrights ... some ideas (was: printermib - problemsother than compliances)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: printermib - problems other than compliances
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: guidelines 4.8 (read-only + full compliances)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: guidelines 4.6.2/4.6.3 (persistence of values of read-write objects)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: printermib - problems other than compliances
  • From: "C. M. Heard" <heard@pobox.com>
• Re: comments/review <draft-ietf-ops-mib-review-guidelines-00.txt>
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines 4.8 (read-only + full compliances)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines 4.6.2/4.6.3 (persistence of values of read-writeobjects)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: "C. M. Heard" <heard@pobox.com>
• RE: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: "C. M. Heard" <heard@pobox.com>
• RE: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: Andy Bierman <abierman@cisco.com>
• RE: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: guidelines and SMIv1 -> SMIv2 conversions
  • From: Andy Bierman <abierman@cisco.com>
• Re: guidelines and SMIv1 -> SMIv2 conversions
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines section 4.5 (WG-assigned OIDs vs IANA-assigned OIDs)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: Andy Bierman <abierman@cisco.com>
• Re: guidelines section 4.5 (WG-assigned OIDs vs IANA-assigned OIDs)
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: DisplayString in guidelines 4.6.1.4 and Appendix D
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines section 4.5 (WG-assigned OIDs vs IANA-assigned OIDs)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines section 4.5 (WG-assigned OIDs vs IANA-assigned OIDs)
  • From: Andy Bierman <abierman@cisco.com>
• Re: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: guidelines section 3.7 (copyright notices in IANA MIB modules)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: printermib - problems other than compliances
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: clarify that MIB review requirements are targeted at standards-track documents but are useful for other documents
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: clarify that MIB review requirements are targeted at standards-trackdocuments but are useful for other documents
  • From: "C. M. Heard" <heard@pobox.com>
• RE: guidelines section 4.5 (WG-assigned OIDs vs IANA-assigned OIDs)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: guidelines section 4.5 (WG-assigned OIDs vs IANA-assigned OIDs)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: clarify that MIB review requirements are targeted at standard s-track documents
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: printermib - problems other than compliances
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines section 3.7 (disposition of IANA MIB modules)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: clarify that MIB review requirements are targeted at standards-track documents
  • From: "C. M. Heard" <heard@pobox.com>
• RE: printermib - problems other than compliances
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: clarify that MIB review requirements are targeted at standards-track documents
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: clarify that MIB review requirements are targeted at standards-trackdocuments
  • From: "C. M. Heard" <heard@pobox.com>
• Re: printermib - problems other than compliances
  • From: "C. M. Heard" <heard@pobox.com>
• RE: clarify that MIB review requirements are targeted at standards-track documents
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: clarifying the term "standard"
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: printermib - problems other than compliances
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: clarify that MIB review requirements are targeted at standards-trackdocuments
  • From: "C. M. Heard" <heard@pobox.com>
• Re: clarifying the term "standard"
  • From: "C. M. Heard" <heard@pobox.com>
• RE: guidelines sec. 4.6.1.2 and discontinuity indicator
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Ipcdn - draft agenda for interim meeting for your review
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: guidelines sec. 4.6.1.2 and discontinuity indicator
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: guidelines sec. 4.6.1.2 and discontinuity indicator
  • From: "C. M. Heard" <heard@pobox.com>
• SNMP/MIB advisor for IDR WG
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: ACTION REQUESTED: please review draft-ietf-ops-mib-review-guidelines-00.txt
  • From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
• Re: ifNumber and its ilk considered harmful
  • From: Mike MacFaden <mrm@riverstonenet.com>
• Re: ifNumber and its ilk considered harmful
  • From: Andy Bierman <abierman@cisco.com>
• Re: ifNumber and its ilk considered harmful
  • From: Mike MacFaden <mrm@riverstonenet.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: Andy Bierman <abierman@cisco.com>
• RE: Naming Conventions for Descriptors (was: comments/review <draft-ietf-ops-mib-review-guidelines-00.txt>)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Naming Conventions for Descriptors (was: comments/review<draft-ietf-ops-mib-review-guidelines-00.txt>)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: ifNumber and its ilk considered harmful
  • From: "C. M. Heard" <heard@pobox.com>
• RE: comments/review <draft-ietf-ops-mib-review-guidelines-00.txt>
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• ACTION REQUESTED: please review draft-ietf-ops-mib-review-guidelines-00.txt
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: ifNumber and its ilk considered harmful
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: guidelines section 3.6 (security considerations)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Section 4.6.5 [was: 4.5] OID size limits
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines sec. 4.6.1.2 and discontinuity indicator
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines sec. 4.6.1.2 and discontinuity indicator
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: ifNumber and its ilk considered harmful
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: guidelines section 3.6 (security considerations)
  • From: "Harrington, David" <dbh@enterasys.com>
• ifNumber and its ilk considered harmful
  • From: Mike MacFaden <mrm@riverstonenet.com>
• RE: guidelines sec. 4.6.1.2 and discontinuity indicator
  • From: "C. M. Heard" <heard@pobox.com>
• comments/review <draft-ietf-ops-mib-review-guidelines-00.txt>
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Section 4.5 OID size limits
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Section 4.5 OID size limits
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: guidelines sec. 4.6.1.2 and discontinuity indicator
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: guidelines section 3.6 (security considerations)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: guidelines section 4.7 (index objects in notifications)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: guidelines section 4.6.1.2 (one hour rule)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: Andy Bierman <abierman@cisco.com>
• MIB review guidelines open issues list
  • From: "C. M. Heard" <heard@pobox.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: guidelines section 3.6 (security considerations)
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: guidelines section 3.6 (security considerations)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Gauge32 as an index (guidelines Section 4.6.1.1)
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: guidelines section 4.6.1.2 (one hour rule)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: guidelines section 3.6 (security considerations)
  • From: "Harrington, David" <dbh@enterasys.com>
• Re: guidelines section 4.7 (index objects in notifications)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Gauge32 as an index (guidelines Section 4.6.1.1)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: printermib - problems other than compliances
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: guidelines section 3.6 (security considerations)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Gauge32 as an index (guidelines Section 4.6.1.1)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: printermib - problems other than compliances
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Gauge32 as an index (guidelines Section 4.6.1.1)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines section 3.6 (security considerations)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: should guidelines say something about NOT using IMPLIED?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: guidelines sec. 4.6.1.2 and discontinuity indicator
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Guidelines Section 4.6.1.6 (BITS construct)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Disappointment with guidelines doc (was: Re: consensus call sect 4.4)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Guidelines Section 4.6.1.6 (BITS construct)
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: Guidelines Section 4.6.5 (OID Length Limitations and TableIndexing)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Guidelines Section 4.6.4 (OID Values Assigned to Objects)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Guidelines Section 4.6.1.6 (BITS construct)
  • From: "C. M. Heard" <heard@pobox.com>
• Disappointment with guidelines doc (was: Re: consensus call sect4.4)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: consensus call sect 4.4
  • From: "C. M. Heard" <heard@pobox.com>
• Re: consensus call sect 4.4
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• RE: consensus call sect 4.4
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Typos in sec. 4.9 of <draft-ietf-ops-mib-review-guidelines-00.txt>
  • From: "C. M. Heard" <heard@pobox.com>
• Re: consensus call sect 4.4
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• consensus call sect 4.4
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Submission of <draft-ietf-ops-mib-review-guidelines-00.txt>
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Submission of <draft-ietf-ops-mib-review-guidelines-00.txt>
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: printermib - compliance statement(s)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: printermib - compliance statement(s)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Omission from reviewer's guide: one hour rule
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Omission from reviewer's guide: one hour rule
  • From: "C. M. Heard" <heard@pobox.com>
• RE: printermib - compliance statement(s)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: printermib - compliance statement(s)
  • From: "Harrington, David" <dbh@enterasys.com>
• Re: Submission of <draft-ietf-ops-mib-review-guidelines-00.txt>
  • From: "C. M. Heard" <heard@pobox.com>
• Submission of <draft-ietf-ops-mib-review-guidelines-00.txt>
  • From: "C. M. Heard" <heard@pobox.com>
• Re: printermib - compliance statement(s)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: printermib - compliance statement(s)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: printermib - compliance statement(s)
  • From: "C. M. Heard" <heard@pobox.com>
• printermib - compliance statement(s)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: INET-Addresses not used in MPLS MIB Modules
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: INET-Addresses not used in MPLS MIB Modules
  • From: Mike MacFaden <mrm@riverstonenet.com>
• FW: Ipcdn - draft agenda for interim meeting for your review
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: INET-Addresses not used in MPLS MIB Modules
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: INET-Addresses not used in MPLS MIB Modules
  • From: "C. M. Heard" <heard@pobox.com>
• Re: INET-Addresses not used in MPLS MIB Modules
  • From: Mike MacFaden <mrm@riverstonenet.com>
• RE: INET-Addresses not used in MPLS MIB Modules
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: INET-Addresses not used in MPLS MIB Modules
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• RE: INET-Addresses not used in MPLS MIB Modules
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: INET-Addresses not used in MPLS MIB Modules
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• RE: INET-Addresses not used in MPLS MIB Modules
  • From: "C. M. Heard" <heard@pobox.com>
• RE: INET-Addresses not used in MPLS MIB Modules
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: INET-Addresses not used in MPLS MIB Modules
  • From: "C. M. Heard" <heard@pobox.com>
• INET-Addresses not used in MPLS MIB Modules
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Status of MIB reviewers Guidelines
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Missing normative references to modules containing importeditems (was: FW: Malloc MIB)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: RFC 2011 bugs
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Missing normative references to modules containing imported items (was: FW: Malloc MIB)
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RFC 2011 bugs
  • From: Andy Bierman <abierman@cisco.com>
• Re: Missing normative references to modules containing importeditems (was: FW: Malloc MIB)
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Status of MIB reviewers Guidelines
  • From: "C. M. Heard" <heard@pobox.com>
• Status of MIB reviewers Guidelines
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• FW: Malloc MIB
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Anyone wants to do a double check on an IPCDN mib?
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Anyone wants to do a double check on an IPCDN mib?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: Anyone wants to do a double check on an IPCDN mib?
  • From: Andy Bierman <abierman@cisco.com>
• Re: Anyone wants to do a double check on an IPCDN mib?
  • From: "C. M. Heard" <heard@pobox.com>
• Anyone wants to do a double check on an IPCDN mib?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Index values of zero (was: Index values of zero)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: reviewer guidelines
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Gauge32 as an INDEX (was: Index values of zero)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: reviewer guidelines
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: reviewer guidelines
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Gauge32 as an INDEX (was: Index values of zero)
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Enumerated INTEGER - start with zero or one (0 or 1) ?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: reviewer guidelines
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• RE: Gauge32 as an INDEX (was: Index values of zero)
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Enumerated INTEGER - start with zero or one (0 or 1) ?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: reviewer guidelines
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: reviewer guidelines
  • From: "C. M. Heard" <heard@pobox.com>
• RE: reviewer guidelines
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: reviewer guidelines
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Integer32 vs. INTEGER
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• Re: Integer32 vs. INTEGER
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: Integer32 vs. INTEGER
  • From: "Randy Presuhn" <randy_presuhn@mindspring.com>
• Re: Integer32 vs. INTEGER
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• Re: Integer32 vs. INTEGER
  • From: "C. M. Heard" <heard@pobox.com>
• Integer32 vs. INTEGER
  • From: Andy Bierman <abierman@cisco.com>
• RE: reviewer guidelines
  • From: "Harrington, David" <dbh@enterasys.com>
• Re: reviewer guidelines
  • From: "C. M. Heard" <heard@pobox.com>
• reviewer guidelines
  • From: "Harrington, David" <dbh@enterasys.com>
• Re: Importing items used in MODULE-COMPLIANCE and AGENT-CAPABILITIES
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Enumerated INTEGER - start with zero or one (0 or 1) ?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Gauge32 as an INDEX (was: Index values of zero)
  • From: "C. M. Heard" <heard@pobox.com>
• Is enumeration syntax refinement legal with a TC?
  • From: "C. M. Heard" <heard@pobox.com>, "C. M. Heard" <heard@pobox.com>
• Re: Changing enum labels considered harmful
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RE: Changing enum labels considered harmful
  • From: "Presuhn, Randy" <Randy_Presuhn@bmc.com>
• RE: Changing enum labels considered harmful
  • From: "C. M. Heard" <heard@pobox.com>
• RE: Changing enum labels considered harmful
  • From: "Harrington, David" <dbh@enterasys.com>
• Re: Changing enum labels considered harmful
  • From: "C. M. Heard" <heard@pobox.com>
• Re: Changing enum labels considered harmful
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Changing enum labels considered harmful
  • From: "C. M. Heard" <heard@pobox.com>
• RE: docsis subscriber mib
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RE: docsis subscriber mib
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: docsis subscriber mib
  • From: "Presuhn, Randy" <Randy_Presuhn@bmc.com>
• Re: docsis subscriber mib
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: docsis subscriber mib
  • From: "Presuhn, Randy" <Randy_Presuhn@bmc.com>
• Re: docsis subscriber mib
  • From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
• RE: docsis subscriber mib
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RE: docsis subscriber mib
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: docsis subscriber mib
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• docsis subscriber mib
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: MODULE COMPLIANCE
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• RE: Is unconstrained INTEGER illegal in SMIv2?
  • From: Andy Bierman <abierman@cisco.com>
• RE: Is unconstrained INTEGER illegal in SMIv2?
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: Is unconstrained INTEGER illegal in SMIv2?
  • From: "Presuhn, Randy" <Randy_Presuhn@bmc.com>
• Re: Is unconstrained INTEGER illegal in SMIv2?
  • From: Andy Bierman <abierman@cisco.com>
• Re: MODULE COMPLIANCE
  • From: "C. M. Heard" <heard@pobox.com>
• Re: MODULE COMPLIANCE
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• Is unconstrained INTEGER illegal in SMIv2?
  • From: "C. M. Heard" <heard@pobox.com>
• Re: MODULE COMPLIANCE
  • From: Andy Bierman <abierman@cisco.com>
• Re: MODULE COMPLIANCE
  • From: "C. M. Heard" <heard@pobox.com>
• Re: MODULE COMPLIANCE
  • From: "David T. Perkins" <dperkins@dsperkins.com>
• MODULE COMPLIANCE
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• Re: FW: 64 bit counters in MPLS MIBs
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: "C. M. Heard" <heard@pobox.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: Andy Bierman <abierman@cisco.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: "Harrington, David" <dbh@enterasys.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: Andy Bierman <abierman@cisco.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: "Glenn Waters" <gww@nortelnetworks.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: "C. M. Heard" <heard@pobox.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: Andy Bierman <abierman@cisco.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: "C. M. Heard" <heard@pobox.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
• RE: FW: 64 bit counters in MPLS MIBs
  • From: "Glenn Waters" <gww@nortelnetworks.com>
• Re: FW: 64 bit counters in MPLS MIBs
  • From: Andy Bierman <abierman@cisco.com>
• Re: 64 bit counters in MPLS MIBs
  • From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
• Re: FW: 64 bit counters in MPLS MIBs
  • From: "C. M. Heard" <heard@pobox.com>
• RE: 64 bit counters in MPLS MIBs
  • From: "Harrington, David" <dbh@enterasys.com>
• FW: 64 bit counters in MPLS MIBs
  • From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>