From hubmib-bounces@ietf.org Fri Aug 05 09:57:19 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E12hK-0006Cc-Us; Fri, 05 Aug 2005 09:57:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E12hJ-0006CX-Dn for hubmib@megatron.ietf.org; Fri, 05 Aug 2005 09:57:17 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11353 for ; Fri, 5 Aug 2005 09:57:15 -0400 (EDT) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E13EO-0008JA-Sw for hubmib@ietf.org; Fri, 05 Aug 2005 10:31:30 -0400 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j75DiTpt016471 for ; Fri, 5 Aug 2005 09:44:30 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j75DiRpt016433 for ; Fri, 5 Aug 2005 09:44:28 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 5 Aug 2005 16:57:07 +0300 Message-ID: Thread-Topic: Mail Delivery (failure dromasca@avaya.com) Thread-Index: AcWZxZFmbeBsKkPQQhGd1jZioRBCSwAAAACc From: "Romascanu, Dan \(Dan\)" To: X-Spam-Score: 0.8 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Subject: [Hubmib] Out of Office AutoReply: Mail Delivery (failure dromasca@avaya.com) X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1374022708==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============1374022708== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C599C5.91689913" This is a multi-part message in MIME format. ------_=_NextPart_001_01C599C5.91689913 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable I am out-of-office, on a business trip, untill August 6, 2005, and I may = be able to read your e-mail only after this date. If you need to contact = me urgently, please call the mobile phone number +972-50-6928065. Regards, Dan ------_=_NextPart_001_01C599C5.91689913 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Out of Office AutoReply: <Possible SPAM> Mail Delivery = (failure dromasca@avaya.com)

I am out-of-office, on a business trip, untill August = 6, 2005, and I may be able to read your e-mail only after this date. If = you need to contact me urgently, please call the mobile phone number = +972-50-6928065.

Regards,

Dan

------_=_NextPart_001_01C599C5.91689913-- --===============1374022708== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============1374022708==-- From hubmib-bounces@ietf.org Tue Aug 23 08:46:58 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7YB7-0004ic-VA; Tue, 23 Aug 2005 08:46:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7YB2-0004iT-UL for hubmib@megatron.ietf.org; Tue, 23 Aug 2005 08:46:56 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01461 for ; Tue, 23 Aug 2005 08:46:50 -0400 (EDT) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E7YB6-0003Mz-Mh for hubmib@ietf.org; Tue, 23 Aug 2005 08:46:59 -0400 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j7NCXjvl008782 for ; Tue, 23 Aug 2005 08:33:45 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j7NCXevl008696 for ; Tue, 23 Aug 2005 08:33:41 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 23 Aug 2005 15:46:37 +0300 Message-ID: Thread-Topic: I-D Publication Request - draft-ietf-hubmib-efm-mib-03.txt Thread-Index: AcWn4LLAJC/SM5s6R2yc4+hc3EN/0Q== From: "Romascanu, Dan \(Dan\)" To: "Wijnen, Bert \(Bert\)" X-Spam-Score: 0.0 (/) X-Scan-Signature: 6379955759c38e2371a49573a0932fc7 Cc: David Kessens , hubmib@ietf.org Subject: [Hubmib] I-D Publication Request - draft-ietf-hubmib-efm-mib-03.txt X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0344891382==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============0344891382== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5A7E0.B3382656" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5A7E0.B3382656 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 [Area] OPS-NM [WG] hubmib [I-D] draft-ietf-hubmib-efm-mib-03.txt [Qver] draft-ietf-proto-wgchair-doc-shepherding-05.txt [Shep] Dan Romascanu 1.a) Yes, the WG Chair has reviewed this version of the document. 1.b) Yes it has had adequate reviews from WG members and members of the = IEEE 802.3 Working Groups; no concerns about the reviews 1.c) No special concerns, a MIB Doctor review would be helpful. 1.d) No special concerns 1.e) The hubmib Working group had a low numbers particpation. The = document was reviewed and discussed, including in two WG Last Call = sessions. It represents the strong consensus of the current active = participants in the work.=20 1.f) No appeals have been threatened. 1.g) Yes, there are some minor nits and boilerplate problems that will = be fixed before RFC publication.=20 --------------------------------------- idnits 1.77=20 tmp/draft-ietf-hubmib-efm-mib-03.txt: tmp/draft-ietf-hubmib-efm-mib-03.txt(305): Line has weird spacing: = '...uration dot...' tmp/draft-ietf-hubmib-efm-mib-03.txt(306): Line has weird spacing: = '...uration dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(340): Line has weird spacing: = '...cificTx dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(341): Line has weird spacing: = '...cificRx dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(343): Line has weird spacing: = '...dConfig dot3O...' tmp/draft-ietf-hubmib-efm-mib-03.txt(346): Line has weird spacing: = '...odEvent dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(354): Line has weird spacing: = '...odEvent dot3O...' tmp/draft-ietf-hubmib-efm-mib-03.txt(362): Line has weird spacing: = '...odEvent dot3O...' tmp/draft-ietf-hubmib-efm-mib-03.txt(2938): Line contains a non-ascii = character (=FB) in position 71. tmp/draft-ietf-hubmib-efm-mib-03.txt(2945): Line contains a non-ascii = character (=FB) in position 39. tmp/draft-ietf-hubmib-efm-mib-03.txt(2949): Line contains a non-ascii = character (=FB) in position 51. Checking nits according to http://www.ietf.org/ID-Checklist.html: Checking conformance with RFC 3978/3979 boilerplate... * The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement.=20 (Expected a match on the following text: "By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.") * The document seems to lack an RFC 3979 Section 5, para 1 IPR = Disclosure Acknowledgement -- however, there's a paragraph with a matching = beginning. Boilerplate error? (Expected a match on the following text: "The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed = to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. = Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79." =20 ... but found this: "The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed = to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. = Information EFM OAM MIB March 2005") ...^ * The document seems to lack an RFC 3979 Section 5, para 3 IPR = Disclosure Invitation -- however, there's a paragraph with a matching = beginning. Boilerplate error? (Expected a match on the following text: "The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org." =20 ... but found this: "The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf .................................................................^ ipr@ietf.org.") Checking nits according to = http://www.ietf.org/ietf/1id-guidelines.txt: * The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a = paragraph with a matching beginning. Boilerplate error? (Expected a match on the following text: "Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as = Internet-Drafts." =20 ... but found this: "Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet = Drafts.") .................................................................^ - It seems as if not all pages are separated by form feeds - found 54 form feeds but 56 pages Miscellaneous warnings: None. ---------------------------------------- 1.h) Yes, references are split. No, there are no references to unpublished documents, 1.j) I-D Submission Summary Technical Summary This document defines objects for managing Operations, Administration, and Maintenance (OAM) capabilities on Ethernet like interfaces conformant to the Ethernet OAM functionality defined in [802.3ah]. The Ethernet OAM functionality is complementary to SNMP management in that it is focused on a small set of link-specific functions for directly connected Ethernet interfaces. This document defines objects for controlling those link OAM functions, and on providing mechanisms to take status and input from Ethernet OAM and feed it into a larger TCP/IP network management system. =20 Working Group Summary There is consensus in the WG to recommend this document as a Proposed = Standard Protocol Quality This document was reviewed by Dan Romascanu, CM Heard, Lior Khermosh and = Edward Beili and found to be at the appropriate level for submission to = the IESG.=20 ------_=_NextPart_001_01C5A7E0.B3382656 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 

[Area] OPS-NM

[WG] hubmib

[I-D]=20 draft-ietf-hubmib-efm-mib-03.txt

[Qver]=20 draft-ietf-proto-wgchair-doc-shepherding-05.txt

[Shep] Dan=20 Romascanu

1.a) Yes, the WG Chair has reviewed this = version of=20 the document.

1.b) Yes it has had adequate = reviews from WG members and members of the IEEE = 802.3 Working=20 Groups; no concerns about the=20 reviews

1.c) No special concerns, a MIB Doctor = review would=20 be helpful.

1.d) No special=20 concerns

1.e) The=20 hubmib Working group had a low numbers particpation. The document was = reviewed=20 and discussed, including in two WG Last Call sessions. It represents the = strong=20 consensus of the current active participants in the work.=20

1.f) No appeals have been = threatened.

1.g) Yes, there are some minor = nits and boilerplate problems that will be=20 fixed

before RFC publication.

---------------------------------------

idnits 1.77=20

tmp/draft-ietf-hubmib-efm-mib-03.txt:

tmp/draft-ietf-hubmib-efm-mib-03.txt(305): Line has weird spacing: =
'...uration    dot...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(306): Line has weird spacing: =
'...uration   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(340): Line has weird spacing: =
'...cificTx   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(341): Line has weird spacing: =
'...cificRx   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(343): Line has weird spacing: =
'...dConfig  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(346): Line has weird spacing: =
'...odEvent   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(354): Line has weird spacing: =
'...odEvent  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(362): Line has weird spacing: =
'...odEvent  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(2938): Line contains a non-ascii =
character (=FB) in position 71.
tmp/draft-ietf-hubmib-efm-mib-03.txt(2945): Line contains a non-ascii =
character (=FB) in position 39.
tmp/draft-ietf-hubmib-efm-mib-03.txt(2949): Line contains a non-ascii =
character (=FB) in position 51.


  Checking nits according to http://www.ietf.org/ID-Checklist.html:
    Checking conformance with RFC 3978/3979 boilerplate...
  * The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure
    Acknowledgement.=20

  (Expected a match on the following text:
    "By submitting this Internet-Draft, each author represents that any
    applicable patent or other IPR claims of which he or she is aware
    have been or will be disclosed, and any of which he or she becomes
    aware will be disclosed, in accordance with Section 6 of BCP 79.")

  * The document seems to lack an RFC 3979 Section 5, para 1 IPR =
Disclosure
    Acknowledgement -- however, there's a paragraph with a matching =
beginning.
    Boilerplate error?

  (Expected a match on the following text:
    "The IETF takes no position regarding the validity or scope of any
    Intellectual Property Rights or other rights that might be claimed =
to
    pertain to the implementation or use of the technology described in
    this document or the extent to which any license under such rights
    might or might not be available; nor does it represent that it has
    made any independent effort to identify any such rights.  =
Information
    on the procedures with respect to rights in RFC documents can be
    found in BCP 78 and BCP 79."
 =20
   ... but found this:
    "The IETF takes no position regarding the validity or scope of any
    Intellectual Property Rights or other rights that might be claimed =
to
    pertain to the implementation or use of the technology described in
    this document or the extent to which any license under such rights
    might or might not be available; nor does it represent that it has
    made any independent effort to identify any such rights.  =
Information
    EFM OAM MIB                March 2005")
...^


  * The document seems to lack an RFC 3979 Section 5, para 3 IPR =
Disclosure
    Invitation -- however, there's a paragraph with a matching =
beginning.
    Boilerplate error?

  (Expected a match on the following text:
    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at
    ietf-ipr@ietf.org."
 =20
   ... but found this:
    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at ietf
.................................................................^
    ipr@ietf.org.")



  Checking nits according to =
http://www.ietf.org/ietf/1id-guidelines.txt:
  * The document seems to lack a 1id_guidelines paragraph about
    Internet-Drafts being working documents -- however, there's a =
paragraph with
    a matching beginning. Boilerplate error?

  (Expected a match on the following text:
    "Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as =
Internet-Drafts."
 =20
   ... but found this:
    "Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet =
Drafts.")
.................................................................^


  - It seems as if not all pages are separated by form feeds - found 54
    form feeds but 56 pages

  Miscellaneous warnings:
    None.

----------------------------------------

1.h) Yes, references are = split.

No, there are no references to unpublished=20 documents,

1.j) I-D Submission Summary

Technical Summary

This document defines objects for = managing=20 Operations,
  Administration, and Maintenance (OAM) capabilities = on=20 Ethernet like
  interfaces conformant to the Ethernet OAM = functionality=20 defined in
  [802.3ah].   The Ethernet OAM = functionality is=20 complementary to SNMP
  management in that it is focused on a = small set=20 of link-specific
  functions for directly connected Ethernet=20 interfaces.  This document
  defines objects for = controlling those=20 link OAM functions, and on
  providing mechanisms to take status = and=20 input from Ethernet OAM and
  feed it into a larger TCP/IP = network=20 management system.  

Working = Group=20 Summary

There is = consensus in=20 the WG to recommend this document as a Proposed = Standard

Protocol Quality

This document was reviewed by Dan Romascanu, CM Heard, Lior Khermosh and = Edward Beili=20 and found to be at the appropriate level for submission to the IESG.=20

------_=_NextPart_001_01C5A7E0.B3382656-- --===============0344891382== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============0344891382==-- From hubmib-bounces@ietf.org Tue Aug 23 08:49:09 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7YDF-0004q1-Ft; Tue, 23 Aug 2005 08:49:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7YDD-0004pu-EQ for hubmib@megatron.ietf.org; Tue, 23 Aug 2005 08:49:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01503; Tue, 23 Aug 2005 08:49:06 -0400 (EDT) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E7YDK-0003P4-78; Tue, 23 Aug 2005 08:49:15 -0400 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j7NCa7vl011946; Tue, 23 Aug 2005 08:36:07 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j7NCZmvl011552; Tue, 23 Aug 2005 08:35:49 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 23 Aug 2005 15:48:45 +0300 Message-ID: Thread-Topic: I-D Publication Request - draft-ietf-hubmib-efm-mib-03.txt Thread-Index: AcWn4LLAJC/SM5s6R2yc4+hc3EN/0Q== From: "Romascanu, Dan \(Dan\)" To: "Wijnen, Bert \(Bert\)" X-Spam-Score: 0.0 (/) X-Scan-Signature: 6379955759c38e2371a49573a0932fc7 Cc: David Kessens , iesg-secretary@ietf.org, hubmib@ietf.org Subject: [Hubmib] I-D Publication Request - draft-ietf-hubmib-efm-mib-03.txt X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0660614109==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============0660614109== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5A7E0.FFFFA106" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5A7E0.FFFFA106 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 [Area] OPS-NM [WG] hubmib [I-D] draft-ietf-hubmib-efm-mib-03.txt [Qver] draft-ietf-proto-wgchair-doc-shepherding-05.txt [Shep] Dan Romascanu 1.a) Yes, the WG Chair has reviewed this version of the document. 1.b) Yes it has had adequate reviews from WG members and members of the = IEEE 802.3 Working Groups; no concerns about the reviews 1.c) No special concerns, a MIB Doctor review would be helpful. 1.d) No special concerns 1.e) The hubmib Working group had a low numbers particpation. The = document was reviewed and discussed, including in two WG Last Call = sessions. It represents the strong consensus of the current active = participants in the work.=20 1.f) No appeals have been threatened. 1.g) Yes, there are some minor nits and boilerplate problems that will = be fixed before RFC publication.=20 --------------------------------------- idnits 1.77=20 tmp/draft-ietf-hubmib-efm-mib-03.txt: tmp/draft-ietf-hubmib-efm-mib-03.txt(305): Line has weird spacing: = '...uration dot...' tmp/draft-ietf-hubmib-efm-mib-03.txt(306): Line has weird spacing: = '...uration dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(340): Line has weird spacing: = '...cificTx dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(341): Line has weird spacing: = '...cificRx dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(343): Line has weird spacing: = '...dConfig dot3O...' tmp/draft-ietf-hubmib-efm-mib-03.txt(346): Line has weird spacing: = '...odEvent dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(354): Line has weird spacing: = '...odEvent dot3O...' tmp/draft-ietf-hubmib-efm-mib-03.txt(362): Line has weird spacing: = '...odEvent dot3O...' tmp/draft-ietf-hubmib-efm-mib-03.txt(2938): Line contains a non-ascii = character (=FB) in position 71. tmp/draft-ietf-hubmib-efm-mib-03.txt(2945): Line contains a non-ascii = character (=FB) in position 39. tmp/draft-ietf-hubmib-efm-mib-03.txt(2949): Line contains a non-ascii = character (=FB) in position 51. Checking nits according to http://www.ietf.org/ID-Checklist.html: Checking conformance with RFC 3978/3979 boilerplate... * The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement.=20 (Expected a match on the following text: "By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.") * The document seems to lack an RFC 3979 Section 5, para 1 IPR = Disclosure Acknowledgement -- however, there's a paragraph with a matching = beginning. Boilerplate error? (Expected a match on the following text: "The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed = to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. = Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79." =20 ... but found this: "The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed = to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. = Information EFM OAM MIB March 2005") ...^ * The document seems to lack an RFC 3979 Section 5, para 3 IPR = Disclosure Invitation -- however, there's a paragraph with a matching = beginning. Boilerplate error? (Expected a match on the following text: "The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org." =20 ... but found this: "The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf .................................................................^ ipr@ietf.org.") Checking nits according to = http://www.ietf.org/ietf/1id-guidelines.txt: * The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a = paragraph with a matching beginning. Boilerplate error? (Expected a match on the following text: "Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as = Internet-Drafts." =20 ... but found this: "Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet = Drafts.") .................................................................^ - It seems as if not all pages are separated by form feeds - found 54 form feeds but 56 pages Miscellaneous warnings: None. ---------------------------------------- 1.h) Yes, references are split. No, there are no references to unpublished documents, 1.j) I-D Submission Summary Technical Summary This document defines objects for managing Operations, Administration, and Maintenance (OAM) capabilities on Ethernet like interfaces conformant to the Ethernet OAM functionality defined in [802.3ah]. The Ethernet OAM functionality is complementary to SNMP management in that it is focused on a small set of link-specific functions for directly connected Ethernet interfaces. This document defines objects for controlling those link OAM functions, and on providing mechanisms to take status and input from Ethernet OAM and feed it into a larger TCP/IP network management system. =20 Working Group Summary There is consensus in the WG to recommend this document as a Proposed = Standard Protocol Quality This document was reviewed by Dan Romascanu, CM Heard, Lior Khermosh and = Edward Beili and found to be at the appropriate level for submission to = the IESG.=20 ------_=_NextPart_001_01C5A7E0.FFFFA106 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 

[Area] OPS-NM

[WG] hubmib

[I-D]=20 draft-ietf-hubmib-efm-mib-03.txt

[Qver]=20 draft-ietf-proto-wgchair-doc-shepherding-05.txt

[Shep] Dan=20 Romascanu

1.a) Yes, the WG Chair has reviewed this = version of=20 the document.

1.b) Yes it has had adequate = reviews from WG members and members of the IEEE = 802.3 Working=20 Groups; no concerns about the=20 reviews

1.c) No special concerns, a MIB Doctor = review would=20 be helpful.

1.d) No special=20 concerns

1.e) The=20 hubmib Working group had a low numbers particpation. The document was = reviewed=20 and discussed, including in two WG Last Call sessions. It represents the = strong=20 consensus of the current active participants in the work.=20

1.f) No appeals have been = threatened.

1.g) Yes, there are some minor = nits and boilerplate problems that will be=20 fixed

before RFC publication.

---------------------------------------

idnits 1.77=20

tmp/draft-ietf-hubmib-efm-mib-03.txt:

tmp/draft-ietf-hubmib-efm-mib-03.txt(305): Line has weird spacing: =
'...uration    dot...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(306): Line has weird spacing: =
'...uration   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(340): Line has weird spacing: =
'...cificTx   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(341): Line has weird spacing: =
'...cificRx   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(343): Line has weird spacing: =
'...dConfig  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(346): Line has weird spacing: =
'...odEvent   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(354): Line has weird spacing: =
'...odEvent  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(362): Line has weird spacing: =
'...odEvent  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(2938): Line contains a non-ascii =
character (=FB) in position 71.
tmp/draft-ietf-hubmib-efm-mib-03.txt(2945): Line contains a non-ascii =
character (=FB) in position 39.
tmp/draft-ietf-hubmib-efm-mib-03.txt(2949): Line contains a non-ascii =
character (=FB) in position 51.


  Checking nits according to http://www.ietf.org/ID-Checklist.html:
    Checking conformance with RFC 3978/3979 boilerplate...
  * The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure
    Acknowledgement.=20

  (Expected a match on the following text:
    "By submitting this Internet-Draft, each author represents that any
    applicable patent or other IPR claims of which he or she is aware
    have been or will be disclosed, and any of which he or she becomes
    aware will be disclosed, in accordance with Section 6 of BCP 79.")

  * The document seems to lack an RFC 3979 Section 5, para 1 IPR =
Disclosure
    Acknowledgement -- however, there's a paragraph with a matching =
beginning.
    Boilerplate error?

  (Expected a match on the following text:
    "The IETF takes no position regarding the validity or scope of any
    Intellectual Property Rights or other rights that might be claimed =
to
    pertain to the implementation or use of the technology described in
    this document or the extent to which any license under such rights
    might or might not be available; nor does it represent that it has
    made any independent effort to identify any such rights.  =
Information
    on the procedures with respect to rights in RFC documents can be
    found in BCP 78 and BCP 79."
 =20
   ... but found this:
    "The IETF takes no position regarding the validity or scope of any
    Intellectual Property Rights or other rights that might be claimed =
to
    pertain to the implementation or use of the technology described in
    this document or the extent to which any license under such rights
    might or might not be available; nor does it represent that it has
    made any independent effort to identify any such rights.  =
Information
    EFM OAM MIB                March 2005")
...^


  * The document seems to lack an RFC 3979 Section 5, para 3 IPR =
Disclosure
    Invitation -- however, there's a paragraph with a matching =
beginning.
    Boilerplate error?

  (Expected a match on the following text:
    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at
    ietf-ipr@ietf.org."
 =20
   ... but found this:
    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at ietf
.................................................................^
    ipr@ietf.org.")



  Checking nits according to =
http://www.ietf.org/ietf/1id-guidelines.txt:
  * The document seems to lack a 1id_guidelines paragraph about
    Internet-Drafts being working documents -- however, there's a =
paragraph with
    a matching beginning. Boilerplate error?

  (Expected a match on the following text:
    "Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as =
Internet-Drafts."
 =20
   ... but found this:
    "Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet =
Drafts.")
.................................................................^


  - It seems as if not all pages are separated by form feeds - found 54
    form feeds but 56 pages

  Miscellaneous warnings:
    None.

----------------------------------------

1.h) Yes, references are = split.

No, there are no references to unpublished=20 documents,

1.j) I-D Submission Summary

Technical Summary

This document defines objects for = managing=20 Operations,
  Administration, and Maintenance (OAM) capabilities = on=20 Ethernet like
  interfaces conformant to the Ethernet OAM = functionality=20 defined in
  [802.3ah].   The Ethernet OAM = functionality is=20 complementary to SNMP
  management in that it is focused on a = small set=20 of link-specific
  functions for directly connected Ethernet=20 interfaces.  This document
  defines objects for = controlling those=20 link OAM functions, and on
  providing mechanisms to take status = and=20 input from Ethernet OAM and
  feed it into a larger TCP/IP = network=20 management system.  

Working = Group=20 Summary

There is = consensus in=20 the WG to recommend this document as a Proposed = Standard

Protocol Quality

This document was reviewed by Dan Romascanu, CM Heard, Lior Khermosh and = Edward Beili=20 and found to be at the appropriate level for submission to the IESG.=20

------_=_NextPart_001_01C5A7E0.FFFFA106-- --===============0660614109== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============0660614109==-- From hubmib-bounces@ietf.org Tue Aug 23 08:55:32 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7YJQ-0006lS-5U; Tue, 23 Aug 2005 08:55:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7YJM-0006kW-G9 for hubmib@megatron.ietf.org; Tue, 23 Aug 2005 08:55:30 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01702; Tue, 23 Aug 2005 08:55:26 -0400 (EDT) Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E7YJQ-0003Y3-Sx; Tue, 23 Aug 2005 08:55:35 -0400 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j7NCqg8V010557; Tue, 23 Aug 2005 08:52:42 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j7NCqX8V010277; Tue, 23 Aug 2005 08:52:34 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 23 Aug 2005 15:55:10 +0300 Message-ID: Thread-Topic: I-D Publication Request - draft-ietf-hubmib-efm-mib-03.txt Thread-Index: AcWn4LLAJC/SM5s6R2yc4+hc3EN/0Q== From: "Romascanu, Dan \(Dan\)" To: "Wijnen, Bert \(Bert\)" X-Spam-Score: 0.0 (/) X-Scan-Signature: 054490fec19f6a94c68e63428d06db69 Cc: David Kessens , iesg-secretary@ietf.org, hubmib@ietf.org Subject: [Hubmib] I-D Publication Request - draft-ietf-hubmib-efm-mib-03.txt X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1649506758==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============1649506758== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5A7E1.E4F533E6" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5A7E1.E4F533E6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable One more important note at the Protocol Quality section. Sorry for the = repeated sending. =20 Regards, =20 Dan =20 [Area] OPS-NM [WG] hubmib [I-D] draft-ietf-hubmib-efm-mib-03.txt [Qver] draft-ietf-proto-wgchair-doc-shepherding-05.txt [Shep] Dan Romascanu 1.a) Yes, the WG Chair has reviewed this version of the document. 1.b) Yes it has had adequate reviews from WG members and members of the = IEEE 802.3 Working Groups; no concerns about the reviews 1.c) No special concerns, a MIB Doctor review would be helpful. 1.d) No special concerns 1.e) The hubmib Working group had a low numbers particpation. The = document was reviewed and discussed, including in two WG Last Call = sessions. It represents the strong consensus of the current active = participants in the work.=20 1.f) No appeals have been threatened. 1.g) Yes, there are some minor nits and boilerplate problems that will = be fixed before RFC publication.=20 --------------------------------------- idnits 1.77=20 tmp/draft-ietf-hubmib-efm-mib-03.txt: tmp/draft-ietf-hubmib-efm-mib-03.txt(305): Line has weird spacing: = '...uration dot...' tmp/draft-ietf-hubmib-efm-mib-03.txt(306): Line has weird spacing: = '...uration dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(340): Line has weird spacing: = '...cificTx dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(341): Line has weird spacing: = '...cificRx dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(343): Line has weird spacing: = '...dConfig dot3O...' tmp/draft-ietf-hubmib-efm-mib-03.txt(346): Line has weird spacing: = '...odEvent dot3...' tmp/draft-ietf-hubmib-efm-mib-03.txt(354): Line has weird spacing: = '...odEvent dot3O...' tmp/draft-ietf-hubmib-efm-mib-03.txt(362): Line has weird spacing: = '...odEvent dot3O...' tmp/draft-ietf-hubmib-efm-mib-03.txt(2938): Line contains a non-ascii = character (=FB) in position 71. tmp/draft-ietf-hubmib-efm-mib-03.txt(2945): Line contains a non-ascii = character (=FB) in position 39. tmp/draft-ietf-hubmib-efm-mib-03.txt(2949): Line contains a non-ascii = character (=FB) in position 51. Checking nits according to http://www.ietf.org/ID-Checklist.html: Checking conformance with RFC 3978/3979 boilerplate... * The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement.=20 (Expected a match on the following text: "By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.") * The document seems to lack an RFC 3979 Section 5, para 1 IPR = Disclosure Acknowledgement -- however, there's a paragraph with a matching = beginning. Boilerplate error? (Expected a match on the following text: "The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed = to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. = Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79." =20 ... but found this: "The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed = to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. = Information EFM OAM MIB March 2005") ...^ * The document seems to lack an RFC 3979 Section 5, para 3 IPR = Disclosure Invitation -- however, there's a paragraph with a matching = beginning. Boilerplate error? (Expected a match on the following text: "The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org." =20 ... but found this: "The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf .................................................................^ ipr@ietf.org.") Checking nits according to = http://www.ietf.org/ietf/1id-guidelines.txt: * The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a = paragraph with a matching beginning. Boilerplate error? (Expected a match on the following text: "Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as = Internet-Drafts." =20 ... but found this: "Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet = Drafts.") .................................................................^ - It seems as if not all pages are separated by form feeds - found 54 form feeds but 56 pages Miscellaneous warnings: None. ---------------------------------------- 1.h) Yes, references are split. No, there are no references to unpublished documents, 1.j) I-D Submission Summary Technical Summary This document defines objects for managing Operations, Administration, and Maintenance (OAM) capabilities on Ethernet like interfaces conformant to the Ethernet OAM functionality defined in [802.3ah]. The Ethernet OAM functionality is complementary to SNMP management in that it is focused on a small set of link-specific functions for directly connected Ethernet interfaces. This document defines objects for controlling those link OAM functions, and on providing mechanisms to take status and input from Ethernet OAM and feed it into a larger TCP/IP network management system. =20 Working Group Summary There is consensus in the WG to recommend this document as a Proposed = Standard Protocol Quality This document was reviewed by Dan Romascanu, CM Heard, Lior Khermosh and = Edward Beili and found to be at the appropriate level for submission to = the IESG. There is information about a number of implementations = (between three and seven) based on previous and the current = Internet-Draft version.=20 ------_=_NextPart_001_01C5A7E1.E4F533E6 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
One more important = note at the=20 Protocol Quality section. Sorry for the repeated = sending.
 
Regards,
 
Dan
 

[Area] OPS-NM

[WG] hubmib

[I-D]=20 draft-ietf-hubmib-efm-mib-03.txt

[Qver]=20 draft-ietf-proto-wgchair-doc-shepherding-05.txt

[Shep] Dan=20 Romascanu

1.a) Yes, the WG Chair has reviewed this = version of=20 the document.

1.b) Yes it has had adequate = reviews from WG members and members of the IEEE = 802.3 Working=20 Groups; no concerns about the=20 reviews

1.c) No special concerns, a MIB Doctor = review would=20 be helpful.

1.d) No special=20 concerns

1.e) The=20 hubmib Working group had a low numbers particpation. The document was = reviewed=20 and discussed, including in two WG Last Call sessions. It represents the = strong=20 consensus of the current active participants in the work.=20

1.f) No appeals have been = threatened.

1.g) Yes, there are some minor = nits and boilerplate problems that will be=20 fixed

before RFC publication.

---------------------------------------

idnits 1.77=20

tmp/draft-ietf-hubmib-efm-mib-03.txt:

tmp/draft-ietf-hubmib-efm-mib-03.txt(305): Line has weird spacing: =
'...uration    dot...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(306): Line has weird spacing: =
'...uration   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(340): Line has weird spacing: =
'...cificTx   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(341): Line has weird spacing: =
'...cificRx   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(343): Line has weird spacing: =
'...dConfig  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(346): Line has weird spacing: =
'...odEvent   dot3...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(354): Line has weird spacing: =
'...odEvent  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(362): Line has weird spacing: =
'...odEvent  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-03.txt(2938): Line contains a non-ascii =
character (=FB) in position 71.
tmp/draft-ietf-hubmib-efm-mib-03.txt(2945): Line contains a non-ascii =
character (=FB) in position 39.
tmp/draft-ietf-hubmib-efm-mib-03.txt(2949): Line contains a non-ascii =
character (=FB) in position 51.


  Checking nits according to http://www.ietf.org/ID-Checklist.html:
    Checking conformance with RFC 3978/3979 boilerplate...
  * The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure
    Acknowledgement.=20

  (Expected a match on the following text:
    "By submitting this Internet-Draft, each author represents that any
    applicable patent or other IPR claims of which he or she is aware
    have been or will be disclosed, and any of which he or she becomes
    aware will be disclosed, in accordance with Section 6 of BCP 79.")

  * The document seems to lack an RFC 3979 Section 5, para 1 IPR =
Disclosure
    Acknowledgement -- however, there's a paragraph with a matching =
beginning.
    Boilerplate error?

  (Expected a match on the following text:
    "The IETF takes no position regarding the validity or scope of any
    Intellectual Property Rights or other rights that might be claimed =
to
    pertain to the implementation or use of the technology described in
    this document or the extent to which any license under such rights
    might or might not be available; nor does it represent that it has
    made any independent effort to identify any such rights.  =
Information
    on the procedures with respect to rights in RFC documents can be
    found in BCP 78 and BCP 79."
 =20
   ... but found this:
    "The IETF takes no position regarding the validity or scope of any
    Intellectual Property Rights or other rights that might be claimed =
to
    pertain to the implementation or use of the technology described in
    this document or the extent to which any license under such rights
    might or might not be available; nor does it represent that it has
    made any independent effort to identify any such rights.  =
Information
    EFM OAM MIB                March 2005")
...^


  * The document seems to lack an RFC 3979 Section 5, para 3 IPR =
Disclosure
    Invitation -- however, there's a paragraph with a matching =
beginning.
    Boilerplate error?

  (Expected a match on the following text:
    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at
    ietf-ipr@ietf.org."
 =20
   ... but found this:
    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at ietf
.................................................................^
    ipr@ietf.org.")



  Checking nits according to =
http://www.ietf.org/ietf/1id-guidelines.txt:
  * The document seems to lack a 1id_guidelines paragraph about
    Internet-Drafts being working documents -- however, there's a =
paragraph with
    a matching beginning. Boilerplate error?

  (Expected a match on the following text:
    "Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as =
Internet-Drafts."
 =20
   ... but found this:
    "Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet =
Drafts.")
.................................................................^


  - It seems as if not all pages are separated by form feeds - found 54
    form feeds but 56 pages

  Miscellaneous warnings:
    None.

----------------------------------------

1.h) Yes, references are = split.

No, there are no references to unpublished=20 documents,

1.j) I-D Submission Summary

Technical Summary

This document defines objects for = managing=20 Operations,
  Administration, and Maintenance (OAM) capabilities = on=20 Ethernet like
  interfaces conformant to the Ethernet OAM = functionality=20 defined in
  [802.3ah].   The Ethernet OAM = functionality is=20 complementary to SNMP
  management in that it is focused on a = small set=20 of link-specific
  functions for directly connected Ethernet=20 interfaces.  This document
  defines objects for = controlling those=20 link OAM functions, and on
  providing mechanisms to take status = and=20 input from Ethernet OAM and
  feed it into a larger TCP/IP = network=20 management system.  

Working = Group=20 Summary

There is = consensus in=20 the WG to recommend this document as a Proposed = Standard

Protocol Quality

This document was reviewed by Dan Romascanu, CM Heard, Lior Khermosh and = Edward Beili=20 and found to be at the appropriate level for submission to the IESG. = There is=20 information about a number of implementations (between three and seven) = based on=20 previous and the current Internet-Draft version.=20

------_=_NextPart_001_01C5A7E1.E4F533E6-- --===============1649506758== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============1649506758==-- From hubmib-bounces@ietf.org Tue Aug 23 09:03:31 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7YR9-0007lj-IW; Tue, 23 Aug 2005 09:03:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7YR6-0007lE-FI for hubmib@megatron.ietf.org; Tue, 23 Aug 2005 09:03:28 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02107; Tue, 23 Aug 2005 09:03:26 -0400 (EDT) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E7YRC-0003nI-RZ; Tue, 23 Aug 2005 09:03:35 -0400 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j7NCoLvl001966; Tue, 23 Aug 2005 08:50:21 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j7NCnLvl000581; Tue, 23 Aug 2005 08:49:22 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 23 Aug 2005 16:02:11 +0300 Message-ID: Thread-Topic: I-D Publication Request - draft-ietf-hubmib-efm-epon-mib-03.txt Thread-Index: AcWn4uALliXEnTXRTxeglAg0LBDhRQ== From: "Romascanu, Dan \(Dan\)" To: "Wijnen, Bert \(Bert\)" X-Spam-Score: 0.5 (/) X-Scan-Signature: ed68cc91cc637fea89623888898579ba Cc: David Kessens , iesg-secretary@ietf.org, hubmib@ietf.org Subject: [Hubmib] I-D Publication Request - draft-ietf-hubmib-efm-epon-mib-03.txt X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0476690990==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============0476690990== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5A7E2.E050D112" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5A7E2.E050D112 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 =20 =20 [Area] OPS-NM [WG] hubmib [I-D] draft-ietf-hubmib-efm-epon-mib-03.txt [Qver] draft-ietf-proto-wgchair-doc-shepherding-05.txt [Shep] Dan Romascanu 1.a) Yes, the WG Chair has reviewed this version of the document. 1.b) Yes it has had adequate reviews from WG members and members of the IEEE 802.3 Working Groups; no concerns about the reviews 1.c) No special concerns, a MIB Doctor review would be helpful. 1.d) No special concerns 1.e) The hubmib Working group had a low numbers particpation. The document was reviewed and discussed, including in two WG Last Call sessions. It represents the strong consensus of the current active participants in the work.=20 1.f) No appeals have been threatened. 1.g) Yes, idnits complains about the lack of an IPR Disclosure section. That will be fixed before RFC publication.=20 --------------------------------------- idnits 1.77=20 tmp/draft-ietf-hubmib-efm-epon-mib-03.txt: Checking nits according to http://www.ietf.org/ID-Checklist.html: Checking conformance with RFC 3978/3979 boilerplate... * The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement.=20 (Expected a match on the following text: "By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.") (The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted.) Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt: Nothing found here (but these checks do not cover all of 1id-guidelines.txt yet). Miscellaneous warnings: None. ---------------------------------------- 1.h) Yes, references are split. No, there are no references to unpublished documents, 1.j) I-D Submission Summary Technical Summary This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based Internets. In particular, it defines objects for managing devices and interfaces that conform to the Ethernet Passive Optical Networks (EPON) standards as defined in IEEE 802.3-2004.=20 Working Group Summary There is consensus in the WG to recommend this document as a Proposed Standard Protocol Quality This document was reviewed by Dan Romascanu, CM Heard, Matt Squire and Edward Beili and found to be at the appropriate level for submission to the IESG.=20 =20 ------_=_NextPart_001_01C5A7E2.E050D112 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
 
 
 

[Area] OPS-NM

[WG] hubmib

[I-D]=20 draft-ietf-hubmib-efm-epon-mib-03.txt

[Qver]=20 draft-ietf-proto-wgchair-doc-shepherding-05.txt

[Shep] Dan=20 Romascanu

1.a) Yes, the WG Chair has reviewed this = version of=20 the document.

1.b) Yes it has had adequate = reviews from WG members and members of the IEEE = 802.3 Working=20 Groups; no concerns about the=20 reviews

1.c) No special concerns, a MIB Doctor = review would=20 be helpful.

1.d) No special=20 concerns

1.e) The=20 hubmib Working group had a low numbers particpation. The document was = reviewed=20 and discussed, including in two WG Last Call sessions. It represents the = strong=20 consensus of the current active participants in the work.=20

1.f) No appeals have been = threatened.

1.g) Yes, idnits=20 complains about the lack of an IPR Disclosure section. That will = be=20 fixed

before RFC publication.

---------------------------------------

idnits 1.77=20

tmp/draft-ietf-hubmib-efm-epon-mib-03.txt:


  Checking nits according to http://www.ietf.org/ID-Checklist.html:
    Checking conformance with RFC 3978/3979 boilerplate...
  * The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure
    Acknowledgement.=20

  (Expected a match on the following text:
    "By submitting this Internet-Draft, each author represents that any
    applicable patent or other IPR claims of which he or she is aware
    have been or will be disclosed, and any of which he or she becomes
    aware will be disclosed, in accordance with Section 6 of BCP 79.")

    (The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate
    instead of verbatim RFC 3978 boilerplate.  After 6 May 2005, =
submission of
    drafts without verbatim RFC 3978 boilerplate is not accepted.)

  Checking nits according to =
http://www.ietf.org/ietf/1id-guidelines.txt:
    Nothing found here (but these checks do not cover all of
    1id-guidelines.txt yet).

  Miscellaneous warnings:
    None.

----------------------------------------

1.h) Yes, references are = split.

No, there are no references to unpublished=20 documents,

1.j) I-D Submission Summary

Technical Summary

   This = document=20 defines a portion of the Management Information Base
   = (MIB) for=20 use with network management protocols in TCP/IP based
  =20 Internets.  In particular, it defines objects for managing=20 devices
   and interfaces that conform to the Ethernet = Passive=20 Optical Networks
   (EPON) standards as defined in IEEE = 802.3-2004.=20

Working = Group=20 Summary

There is = consensus in=20 the WG to recommend this document as a Proposed = Standard

Protocol Quality

This document was reviewed by Dan Romascanu, CM Heard, Matt Squire and Edward Beili and = found to=20 be at the appropriate level for submission to the IESG.=20

 
------_=_NextPart_001_01C5A7E2.E050D112-- --===============0476690990== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============0476690990==-- From hubmib-bounces@ietf.org Fri Aug 26 07:41:18 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8caE-00088M-Il; Fri, 26 Aug 2005 07:41:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8caC-00088E-3b for hubmib@megatron.ietf.org; Fri, 26 Aug 2005 07:41:16 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12839 for ; Fri, 26 Aug 2005 07:41:15 -0400 (EDT) Received: from web32703.mail.mud.yahoo.com ([68.142.207.247]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1E8caq-0002tk-O1 for hubmib@ietf.org; Fri, 26 Aug 2005 07:42:01 -0400 Received: (qmail 67284 invoked by uid 60001); 26 Aug 2005 11:41:00 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=QCajYGCNilAfUMsYiKh0MObhd8PRCF6R0bocN7AC2igc1S/eZ5iMlRqJ6Ln+9TSOrPQuQXkUCjV9k8fboUf9GYZHKYEBG/B9rJA9vPGlc75lghBYM/YcTym/KUreBfY+2xpkGh/8tCXO47KlR8AxMUW22Gf8nr+j2rUwAYrfMq4= ; Message-ID: <20050826114100.67282.qmail@web32703.mail.mud.yahoo.com> Received: from [67.71.182.33] by web32703.mail.mud.yahoo.com via HTTP; Fri, 26 Aug 2005 07:41:00 EDT Date: Fri, 26 Aug 2005 07:41:00 -0400 (EDT) From: Dominique bastien To: hubmib@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.5 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 8bit Subject: [Hubmib] looking for OAMPDU trace X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org Hi, I'm presently validate a dissector with Ethereal to analyze OAMPDU. But to validate the efficiency of the analyzer I need some traces for many vendor. I heard that some people like Exfo and ADC create private extensions. If someone can capture some traffic and forward to me, with a mention of the product used I will improve the dissector according to them. Thanks, Dominique __________________________________________________________ Find your next car at http://autos.yahoo.ca _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-bounces@ietf.org Sun Aug 28 03:27:44 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E9HZw-00084r-Ec; Sun, 28 Aug 2005 03:27:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E9HZt-00084d-Mo for hubmib@megatron.ietf.org; Sun, 28 Aug 2005 03:27:42 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03175 for ; Sun, 28 Aug 2005 03:27:40 -0400 (EDT) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E9Haw-0007Ma-Gm for hubmib@ietf.org; Sun, 28 Aug 2005 03:28:49 -0400 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j7S7EQE9007166 for ; Sun, 28 Aug 2005 03:14:26 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j7S7ENE9007132 for ; Sun, 28 Aug 2005 03:14:24 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Hubmib] looking for OAMPDU trace X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Date: Sun, 28 Aug 2005 10:27:26 +0300 Message-ID: Thread-Topic: [Hubmib] looking for OAMPDU trace Thread-Index: AcWqMzfeFaCN39ZWRO+oMZnSJaSQ7QBbkfOA From: "Romascanu, Dan \(Dan\)" To: "Dominique bastien" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org Dominique, I believe that the IEEE 802.3 reflectors may be a better place to ask this question. OAMPDUs are not in the scope of the current IETF Ethernet Interfaces and Hub MIB Charter, although they are somehow related.=20 Thank you, Dan=20 Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG =20 =20 > -----Original Message----- > From: hubmib-bounces@ietf.org=20 > [mailto:hubmib-bounces@ietf.org] On Behalf Of Dominique bastien > Sent: Friday, August 26, 2005 2:41 PM > To: hubmib@ietf.org > Subject: [Hubmib] looking for OAMPDU trace >=20 >=20 > Hi, >=20 > I'm presently validate a dissector with Ethereal to analyze=20 > OAMPDU. But to validate the efficiency of the analyzer I need=20 > some traces for many vendor. I heard that some people like=20 > Exfo and ADC create private extensions. If someone can=20 > capture some traffic and forward to me, with a mention of the=20 > product used I will improve the dissector according to them. >=20 > Thanks, >=20 > Dominique >=20 >=20 > =09 >=20 > =09 > =09 > __________________________________________________________ > Find your next car at http://autos.yahoo.ca >=20 > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib