
From dromasca@avaya.com  Wed Sep  9 08:01:10 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE9CA28C217; Wed,  9 Sep 2009 08:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QvYyr0GOKyFn; Wed,  9 Sep 2009 08:01:09 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 85B9128C212; Wed,  9 Sep 2009 08:01:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,358,1249272000"; d="scan'208";a="182723104"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 09 Sep 2009 11:01:41 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by co300216-co-erhwest-out.avaya.com with ESMTP; 09 Sep 2009 11:01:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 9 Sep 2009 17:01:39 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A0C05C@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Nomcom 2009-10: Important Reminder: Call for Nominations, Local Office hours, Nominee Questionnaires available 
thread-index: AcoxW3x0itr054ovT3Oh2zchhv74PgAALA6gAACI9JA=
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, <ops-dir@ietf.org>, <dns-dir@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
Subject: [OPS-AREA] FW: Nomcom 2009-10: Important Reminder: Call for Nominations, Local Office hours, Nominee Questionnaires available
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2009 15:01:10 -0000

=20

-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
Mary Barnes
Sent: Wednesday, September 09, 2009 5:47 PM
To: Working Group Chairs
Subject: FW: Nomcom 2009-10: Important Reminder: Call for
Nominations,Local Office hours, Nominee Questionnaires available=20

Hi all,

Thanks to the ADs and chairs that forwarded the previous reminder to
their mailing lists. I would appreciate it if other chairs and ADs could
do so, since we are really in need of more nominations.

Thanks,
Mary.=20

-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of Barnes, Mary
(RICH2:AR00)
Sent: Wednesday, September 09, 2009 9:38 AM
To: IETF Announcement list
Cc: ietf@ietf.org
Subject: Nomcom 2009-10: Important Reminder: Call for Nominations, Local
Office hours, Nominee Questionnaires available=20

Hi all,

This is a 2nd reminder of the Call for Nominations that is underway.  We
*really* need more nominations in order to properly execute the task of
selecting candidates for the open positions. At this time, the number of
nominations for all the positions is about 1/2 of what is necessary for
the Nomcom to do a conscientious job of evaluating the nominees and we
are over 2/3 of the way through the nominations period. Nomcom cannot do
their job without this important input from the community.=20

So, please consider making nominations for the open positions - it takes
just a few minutes of your time - the details are below.  Right now, we
just need the names/email addresses for the nominees - we'll be
soliciting feedback later. Also, consider that over 1/2 the nominees are
not able to accept the nominations for a variety of reasons - e.g., lack
of funding, lack of sponsor support, etc. Thus, please consider
nominating more than one individual for each of the positions. =20

As well as the reminder for the call for nominations, this email also
serves as a reminder for:
2) Local Office Hours
3) Questionnaires available for nominees=20

Best Regards,
Mary Barnes
nomcom-chair@ietf.org
mary.h.barnes@gmail.com
mary.barnes@nortel.com


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D

1) Call for Nominations
------------------------
The nomination period ends in less than 2 weeks on Sept. 18th, 2009. We
appreciate the folks that have taken the time to make nominations thus
far. But, we do need more nominations. Please use the online tool to
nominate - it's fast, easy and secure:
https://wiki.tools.ietf.org/group/nomcom/09/nominate

Details on the open positions, as well as other details and options for
making nominations are available on the Nomcom homepage:
https://wiki.tools.ietf.org/group/nomcom/09/

Please consider that the sooner you make the nominations, the more time
your nominee(s) will have to complete the necessary questionnaire (item
3
below).  As well, please consider nominating more than one person for a
particular position. You will have the opportunity to provide additional
feedback later and it's important to consider that not all nominees will
be able to accept the nomination.=20


2) Local office hours
-----------------------

In order facilitate additional feedback, the Nomcom has decided to make
themselves available for office areas at various geographic locations
for
3 weeks in September, starting on the 8th.=20

Below please find the list of locations where Nomcom members will be
available for these f2f meetings . Unless dates are identified below,
the Nomcom member is generally available for part of the day during the
weeks of Sept 8-11, Sept 14-18 and Sept 21-25. Also, languages other
than English in which the Nomcom member is fluent are identfied. =20

Please contact a Nomcom member in a specific geographic location to
arrange a convenient meeting time and place. Most Nomcom members are
flexible as to meeting locations - i.e., we can travel to your office,
meet at our offices or somewhere in between. =20

As a reminder folks can always contact any Nomcom member to provide
feedback at anytime - i.e., you don't need to participate in these f2f
sessions to provide feedback.=20


Belgium:=20
     Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be
(Sept
21-25) (Languages: French)=20

Boston, Mass, USA: =20
     Stephen Kent - kent@bbn.com  (Sept 16-18)=20

Boulder, CO, USA:=20
     Wassim Haddad - wmhaddad@gmail.com (Sept 14-18)

Dallas/Ft. Worth, TX, USA: =20
     Mary Barnes  - mary.h.barnes@gmail.com=20
     Lucy Yong - lucyyong@huawei.com  (Languages: Chinese)=20

Helsinki, Finland:=20
      Simo Veikkolainen - simo.veikkolainen@nokia.com (Languages:
Finnish)
=20

Ithaca, NY, USA:=20
      Scott Brim - scott.brim@gmail.com

Montevideo, Uruguay:=20
      Roque Gagliano - roque@lacnic.net (Sept 14-18, 21-25) (Languages:
Spanish, Portuguese)=20

Montreal, Quebec, Canada=20
     Wassim Haddad - wmhaddad@gmail.com (Sept 8-11)
     -- Can also be available in Ottawa if folks are interested=20

Paris, France:=20
      Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be
(Sept 15-18)  (Languages: French)

San Diego, CA, USA:=20
      Randall Gellens - rg+ietf@qualcomm.com  =20
      Dave Crocker - dcrocker@bbiw.net  (Sept 16-18)

Silicon Valley/SF Bay,  CA, USA:=20
      Dave Crocker - dcrocker@bbiw.net  (Sept 8-11, Sept 14-15, Sept
21-25)  =20
      Dorothy Gellert - Dorothy.gellert@gmail.com

3) Questionnaires available for nominees:=20

For folks that have been notified that they have been nominated for any
of the positions, the questionnaires are now available on the Nomcom09
tools website:
https://wiki.tools.ietf.org/group/nomcom/09/iab-questionnaire
https://wiki.tools.ietf.org/group/nomcom/09/iaoc-questionnaire
https://wiki.tools.ietf.org/group/nomcom/09/iesg-questionnaire

If you have any questions, please let me know. I will be contacting
everyone individually, as well as sending reminders.=20


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From dromasca@avaya.com  Thu Sep 17 01:38:38 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC9653A67E3; Thu, 17 Sep 2009 01:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Frjxq+VyaOWV; Thu, 17 Sep 2009 01:38:38 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id AC59928C12F; Thu, 17 Sep 2009 01:38:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,402,1249272000"; d="scan'208";a="183607540"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 17 Sep 2009 04:39:28 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 Sep 2009 04:39:27 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Sep 2009 10:39:04 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A45B0B@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Nomcom 2009-10: FINAL Call for Nominations, Local Office hours, Nominee Questionnaires 
thread-index: Aco3RBVohLPLHLLKTMmfTZpXjGQXMAALh7lA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, <ops-area@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <aaa-doctors@ietf.org>, <dns-dir@ietf.org>
Subject: [OPS-AREA] FW: Nomcom 2009-10: FINAL Call for Nominations, Local Office hours, Nominee Questionnaires
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2009 08:38:39 -0000

=20

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Mary Barnes
Sent: Thursday, September 17, 2009 6:07 AM
To: IETF Announcement list
Cc: ietf@ietf.org
Subject: Nomcom 2009-10: FINAL Call for Nominations, Local Office hours,
Nominee Questionnaires=20

Hi all,

This is the Final Call for Nominations - the nominations period ends in
two days on Sept 18, 2009. =20

We do not have a sufficient number of nominations for the following AD
positions:
APP, OPS, RAI and SEC

In addition, we have not received responses from almost half of the
nominees. I will be sending reminders for all the outstanding
nominations.
=20

We need Community input and participation!!! We cannot properly execute
the task of selecting the best candidates for these positions with so
few accepted nominations.  So, please consider making nominations for
the open positions, in particular those for which we have so few
nominations - it takes just a few minutes of your time. Right now, we
just need the names/email addresses - we'll be soliciting feedback
later.=20

Also, please note that although draft-dawkins-nomcom-openlist-06 has
been approved, the 2009-10 Nomcom is NOT operating under these new
guidelines.

As well as the reminder for the call for nominations, this email also
serves as a reminder for:
2) Local Office Hours through Sept. 25, 2009.=20
3) Questionnaires due from Nominees on Sept. 25, 2009.

Best Regards,
Mary Barnes
nomcom-chair@ietf.org
mary.h.barnes@gmail.com
mary.barnes@nortel.com


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D

1) Call for Nominations
------------------------
The nomination period ends in less than 2 days on Sept. 18th, 2009. We
appreciate the folks that have taken the time to make nominations thus
far. But, we do need more nominations. Please use the online tool to
nominate - it's fast, easy and secure:
https://wiki.tools.ietf.org/group/nomcom/09/nominate

Details on the open positions, as well as other details and options for
making nominations are available on the Nomcom homepage:
https://wiki.tools.ietf.org/group/nomcom/09/

You will have the opportunity to provide additional feedback later and
it's important to consider that not all nominees will be able to accept
the nomination.=20


2) Local office hours
-----------------------

In order facilitate additional feedback, the Nomcom has decided to make
themselves available for office areas at various geographic locations
from
September 8th through Sept. 25th.=20

Below please find the list of locations where Nomcom members will be
available for these f2f meetings . Unless dates are identified below,
the
Nomcom member is generally available for part of the day during the
weeks
of Sept 8-11, Sept 14-18 and Sept 21-25. Also, languages other than
English in which the Nomcom member is fluent are identfied. =20

Please contact a Nomcom member in a specific geographic location to
arrange a convenient meeting time and place. Most Nomcom members are
flexible as to meeting locations - i.e., we can travel to your office,
meet at our offices or somewhere in between. =20

As a reminder folks can always contact any Nomcom member to provide
feedback at anytime - i.e., you don't need to participate in these f2f
sessions to provide feedback.=20


Belgium:=20
     Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be
(Sept
21-25) (Languages: French)=20

Boston, Mass, USA: =20
     Stephen Kent - kent@bbn.com  (Sept 16-18)=20

Boulder, CO, USA:=20
     Wassim Haddad - wmhaddad@gmail.com (Sept 14-18)

Dallas/Ft. Worth, TX, USA: =20
     Mary Barnes  - mary.h.barnes@gmail.com=20
     Lucy Yong - lucyyong@huawei.com  (Languages: Chinese)=20

Helsinki, Finland:=20
      Simo Veikkolainen - simo.veikkolainen@nokia.com (Languages:
Finnish)
=20

Ithaca, NY, USA:=20
      Scott Brim - scott.brim@gmail.com

Montevideo, Uruguay:=20
      Roque Gagliano - roque@lacnic.net (Sept 14-18, 21-25) (Languages:
Spanish, Portuguese)=20

Montreal, Quebec, Canada=20
     Wassim Haddad - wmhaddad@gmail.com (Sept 8-11)
     -- Can also be available in Ottawa if folks are interested=20

Paris, France:=20
      Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be
(Sept 15-18)  (Languages: French)

San Diego, CA, USA:=20
      Randall Gellens - rg+ietf@qualcomm.com  =20
      Dave Crocker - dcrocker@bbiw.net  (Sept 16-18)

Silicon Valley/SF Bay,  CA, USA:=20
      Dave Crocker - dcrocker@bbiw.net  (Sept 8-11, Sept 14-15, Sept
21-25)  =20
      Dorothy Gellert - Dorothy.gellert@gmail.com


3) Questionnaires available for nominees:=20

For folks that have been notified that they have been nominated for any
of the positions, the questionnaires are available on the Nomcom09 tools
website:
https://wiki.tools.ietf.org/group/nomcom/09/iab-questionnaire
https://wiki.tools.ietf.org/group/nomcom/09/iaoc-questionnaire
https://wiki.tools.ietf.org/group/nomcom/09/iesg-questionnaire

The questionnaires are due no later than Sept. 25th, 2009.  If you have
any questions or concerns with meeting the deadline, please let me know.



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From dromasca@avaya.com  Thu Sep 17 03:38:17 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 92E253A6A77; Thu, 17 Sep 2009 03:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.451
X-Spam-Level: 
X-Spam-Status: No, score=-2.451 tagged_above=-999 required=5 tests=[AWL=0.148,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bqndWvcfeEZf; Thu, 17 Sep 2009 03:38:16 -0700 (PDT)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 6700B3A69DD; Thu, 17 Sep 2009 03:38:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,403,1249272000"; d="scan'208";a="173672007"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 17 Sep 2009 06:39:07 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 17 Sep 2009 06:39:07 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Sep 2009 12:38:57 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IESG Statement on Copyright 
thread-index: AcoxhiUZg8zOETXZTmqnTSdu8xpXLAF/OI0A
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <ops-area@ietf.org>
Subject: [OPS-AREA] FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2009 10:38:17 -0000

=20

-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
IESG Secretary
Sent: Wednesday, September 09, 2009 10:45 PM
To: ietf-announce@ietf.org
Cc: wgchairs@ietf.org; ietf@ietf.org
Subject: IESG Statement on Copyright=20

This IESG Statement obsoletes all earlier IESG Statements regarding
Copyright statements in MIB and PIB Modules.

The IESG is providing this guidance to align current practice with RFC
5377, RFC 5378, and the resulting IETF Trust Legal Provisions (TLP)
(http://trustee.ietf.org/license-info).

IETF Contributions and IETF Documents often include code components that
are intended to be directly processed by a computer. Examples of such
code components include ABNF definitions, XML Schemas, XML DTDs, XML
RelaxNG definitions, tables of values, MIBs, PIBs, ASN.1, and classical
programming source code. The IETF Trust maintains a list of code
component types. A link to this list can be found on this web
page: http://trustee.ietf.org/license-info.

In addition to the code component types listed, any text found between
the markers &lt;CODE BEGINS&gt; and &lt;CODE ENDS&gt; shall be
considered a code component. Authors may wish to use these markers as
clear delimiters of code components.

Authors are encouraged to collect code into a separate section or
appendix.

The TLP requires copyright notice in IETF Documents, but not necessarily
in each code component within an IETF Document. Authors may choose to
include a copyright notice as a comment when a significant amount of
code is collected together. For example, authors may include a copyright
notice in a comment as part of an ASN.1 module or a representation of a
classical programming language file. If IETF Document authors choose to
include a code component copyright notice comment, they must follow the
guidance in Section 6.d of the TLP.
Implementors that extract any code component from the IETF Document must
include the BSD license text as described in Section 4.e of the TLP.

From dromasca@avaya.com  Tue Sep 22 05:47:22 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5985C3A6828; Tue, 22 Sep 2009 05:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GucvP4lbkrLR; Tue, 22 Sep 2009 05:47:21 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id C8B2C3A6887; Tue, 22 Sep 2009 05:47:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,431,1249272000"; d="scan'208";a="157572372"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 22 Sep 2009 08:48:22 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 22 Sep 2009 08:48:21 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 Sep 2009 14:48:03 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com>
In-Reply-To: <Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] FW: IESG Statement on Copyright
thread-index: Aco7BTMu+4VYqCc6RieKrILgnGPzVQAfYmJw
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com> <Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "C. M. Heard" <heard@pobox.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
Cc: "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS] FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2009 12:47:22 -0000

There are a number of issues that gathered around 4181 that would
deserve attention if a willing editor is found.=20

Dan
=20

> -----Original Message-----
> From: mib-doctors-bounces@ietf.org=20
> [mailto:mib-doctors-bounces@ietf.org] On Behalf Of C. M. Heard
> Sent: Tuesday, September 22, 2009 12:48 AM
> To: MIB Doctors (E-mail)
> Cc: OPS Area (E-mail)
> Subject: Re: [MIB-DOCTORS] FW: IESG Statement on Copyright
>=20
> Greetings,
>=20
> It seems to me that the new IESG statement on MIB and PIB=20
> module copyrights obsoletes Section 3.7 of RFC 4181=20
> (Guidelines for Authors and Reviewers of MIB Documents) and=20
> all of RFC 4841 (RFC 4181 Update to Recognize the IETF=20
> Trust).  If the cycles exist to do it, someone should write a=20
> short RFC to update RFC 4181 and to obsolete RFC 4841, or=20
> even better, issue an upated version of the mib guidelines=20
> that obsoletes both 4181 and 4841.
>=20
> Just in case anyone should ask, I'm stil retired from MIB=20
> work, and I don't have the cycles to do it myself.
>=20
> Best regards,
>=20
> Mike Heard
>=20
> On Thu, 17 Sep 2009, Romascanu, Dan (Dan) wrote:
> > -----Original Message-----
> > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]=20
> On Behalf=20
> > Of IESG Secretary
> > Sent: Wednesday, September 09, 2009 10:45 PM
> > To: ietf-announce@ietf.org
> > Cc: wgchairs@ietf.org; ietf@ietf.org
> > Subject: IESG Statement on Copyright
> >=20
> > This IESG Statement obsoletes all earlier IESG Statements regarding=20
> > Copyright statements in MIB and PIB Modules.
> >=20
> > The IESG is providing this guidance to align current=20
> practice with RFC=20
> > 5377, RFC 5378, and the resulting IETF Trust Legal Provisions (TLP)=20
> > (http://trustee.ietf.org/license-info).
> >=20
> > IETF Contributions and IETF Documents often include code components=20
> > that are intended to be directly processed by a computer.=20
> Examples of=20
> > such code components include ABNF definitions, XML Schemas,=20
> XML DTDs,=20
> > XML RelaxNG definitions, tables of values, MIBs, PIBs, ASN.1, and=20
> > classical programming source code. The IETF Trust maintains=20
> a list of=20
> > code component types. A link to this list can be found on this web
> > page: http://trustee.ietf.org/license-info.
> >=20
> > In addition to the code component types listed, any text=20
> found between=20
> > the markers &lt;CODE BEGINS&gt; and &lt;CODE ENDS&gt; shall be=20
> > considered a code component. Authors may wish to use these=20
> markers as=20
> > clear delimiters of code components.
> >=20
> > Authors are encouraged to collect code into a separate section or=20
> > appendix.
> >=20
> > The TLP requires copyright notice in IETF Documents, but not=20
> > necessarily in each code component within an IETF Document. Authors=20
> > may choose to include a copyright notice as a comment when a=20
> > significant amount of code is collected together. For=20
> example, authors=20
> > may include a copyright notice in a comment as part of an=20
> ASN.1 module=20
> > or a representation of a classical programming language=20
> file. If IETF=20
> > Document authors choose to include a code component=20
> copyright notice=20
> > comment, they must follow the guidance in Section 6.d of the TLP.
> > Implementors that extract any code component from the IETF Document=20
> > must include the BSD license text as described in Section=20
> 4.e of the TLP.
> >=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20

From j.schoenwaelder@jacobs-university.de  Tue Sep 22 05:53:51 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E782E3A6A2E; Tue, 22 Sep 2009 05:53:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.376
X-Spam-Level: 
X-Spam-Status: No, score=-1.376 tagged_above=-999 required=5 tests=[AWL=-0.616, BAYES_05=-1.11, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m9W2DFQe7FQ3; Tue, 22 Sep 2009 05:53:51 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 03CF63A6A40; Tue, 22 Sep 2009 05:53:51 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4C3B9C0007; Tue, 22 Sep 2009 14:54:54 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id bQ2RuFy+2IYX; Tue, 22 Sep 2009 14:54:51 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3B81EC005D; Tue, 22 Sep 2009 14:54:51 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 2AD40CFA973; Tue, 22 Sep 2009 14:54:50 +0200 (CEST)
Date: Tue, 22 Sep 2009 14:54:50 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-ID: <20090922125450.GB12736@elstar.local>
Mail-Followup-To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "C. M. Heard" <heard@pobox.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, "OPS Area (E-mail)" <ops-area@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com> <Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net> <EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "C. M. Heard" <heard@pobox.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS] FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2009 12:53:52 -0000

On Tue, Sep 22, 2009 at 02:48:03PM +0200, Romascanu, Dan (Dan) wrote:

> There are a number of issues that gathered around 4181 that would
> deserve attention if a willing editor is found. 

Do we have a list of those issues somewhere?

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From dromasca@avaya.com  Tue Sep 22 05:59:37 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B088E3A6A37; Tue, 22 Sep 2009 05:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.451
X-Spam-Level: 
X-Spam-Status: No, score=-2.451 tagged_above=-999 required=5 tests=[AWL=0.148,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bfJnn2a2WTb7; Tue, 22 Sep 2009 05:59:36 -0700 (PDT)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 7E7693A659A; Tue, 22 Sep 2009 05:59:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,431,1249272000"; d="scan'208";a="174204245"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 22 Sep 2009 09:00:39 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 22 Sep 2009 09:00:38 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 Sep 2009 15:00:27 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com>
In-Reply-To: <20090922125450.GB12736@elstar.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] [MIB-DOCTORS] FW: IESG Statement on Copyright
thread-index: Aco7g+NmquLjqHllQbO/zfQjDcQEvQAAICTQ
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com> <Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net> <EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com> <20090922125450.GB12736@elstar.local>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
Cc: "C. M. Heard" <heard@pobox.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS] FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2009 12:59:37 -0000

Nothing as ordered as we would it to be. I remember discussions having
started a few times but we need to go back into the MIB Doctors
archives. There are also three verified errata (editorial stuff).=20

Dan
=20

> -----Original Message-----
> From: Juergen Schoenwaelder=20
> [mailto:j.schoenwaelder@jacobs-university.de]=20
> Sent: Tuesday, September 22, 2009 3:55 PM
> To: Romascanu, Dan (Dan)
> Cc: C. M. Heard; MIB Doctors (E-mail); OPS Area (E-mail)
> Subject: Re: [OPS-AREA] [MIB-DOCTORS] FW: IESG Statement on Copyright
>=20
> On Tue, Sep 22, 2009 at 02:48:03PM +0200, Romascanu, Dan (Dan) wrote:
>=20
> > There are a number of issues that gathered around 4181 that would=20
> > deserve attention if a willing editor is found.
>=20
> Do we have a list of those issues somewhere?
>=20
> --=20
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>=20

From heard@pobox.com  Mon Sep 21 14:46:59 2009
Return-Path: <heard@pobox.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A3933A693B for <ops-area@core3.amsl.com>; Mon, 21 Sep 2009 14:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FGgHnSHgKo0H for <ops-area@core3.amsl.com>; Mon, 21 Sep 2009 14:46:59 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by core3.amsl.com (Postfix) with ESMTP id 714DC3A683F for <ops-area@ietf.org>; Mon, 21 Sep 2009 14:46:58 -0700 (PDT)
Received: (qmail 18502 invoked from network); 21 Sep 2009 14:47:57 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 21 Sep 2009 14:47:55 -0700
Date: Mon, 21 Sep 2009 14:47:54 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com>
Message-ID: <Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net>
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 22 Sep 2009 08:11:00 -0700
Cc: "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS] FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2009 21:46:59 -0000

Greetings,

It seems to me that the new IESG statement on MIB and PIB module 
copyrights obsoletes Section 3.7 of RFC 4181 (Guidelines for Authors 
and Reviewers of MIB Documents) and all of RFC 4841 (RFC 4181 Update 
to Recognize the IETF Trust).  If the cycles exist to do it, someone 
should write a short RFC to update RFC 4181 and to obsolete RFC 
4841, or even better, issue an upated version of the mib guidelines 
that obsoletes both 4181 and 4841.

Just in case anyone should ask, I'm stil retired from MIB work, and 
I don't have the cycles to do it myself.

Best regards,

Mike Heard

On Thu, 17 Sep 2009, Romascanu, Dan (Dan) wrote:
> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
> IESG Secretary
> Sent: Wednesday, September 09, 2009 10:45 PM
> To: ietf-announce@ietf.org
> Cc: wgchairs@ietf.org; ietf@ietf.org
> Subject: IESG Statement on Copyright 
> 
> This IESG Statement obsoletes all earlier IESG Statements regarding
> Copyright statements in MIB and PIB Modules.
> 
> The IESG is providing this guidance to align current practice with RFC
> 5377, RFC 5378, and the resulting IETF Trust Legal Provisions (TLP)
> (http://trustee.ietf.org/license-info).
> 
> IETF Contributions and IETF Documents often include code components that
> are intended to be directly processed by a computer. Examples of such
> code components include ABNF definitions, XML Schemas, XML DTDs, XML
> RelaxNG definitions, tables of values, MIBs, PIBs, ASN.1, and classical
> programming source code. The IETF Trust maintains a list of code
> component types. A link to this list can be found on this web
> page: http://trustee.ietf.org/license-info.
> 
> In addition to the code component types listed, any text found between
> the markers &lt;CODE BEGINS&gt; and &lt;CODE ENDS&gt; shall be
> considered a code component. Authors may wish to use these markers as
> clear delimiters of code components.
> 
> Authors are encouraged to collect code into a separate section or
> appendix.
> 
> The TLP requires copyright notice in IETF Documents, but not necessarily
> in each code component within an IETF Document. Authors may choose to
> include a copyright notice as a comment when a significant amount of
> code is collected together. For example, authors may include a copyright
> notice in a comment as part of an ASN.1 module or a representation of a
> classical programming language file. If IETF Document authors choose to
> include a code component copyright notice comment, they must follow the
> guidance in Section 6.d of the TLP.
> Implementors that extract any code component from the IETF Document must
> include the BSD license text as described in Section 4.e of the TLP.
> 

From heard@pobox.com  Tue Sep 22 14:29:46 2009
Return-Path: <heard@pobox.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3E243A6996 for <ops-area@core3.amsl.com>; Tue, 22 Sep 2009 14:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Id3O7b6jmXrA for <ops-area@core3.amsl.com>; Tue, 22 Sep 2009 14:29:45 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by core3.amsl.com (Postfix) with ESMTP id F0CB03A6452 for <ops-area@ietf.org>; Tue, 22 Sep 2009 14:29:44 -0700 (PDT)
Received: (qmail 3464 invoked from network); 22 Sep 2009 14:30:47 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 22 Sep 2009 14:30:46 -0700
Date: Tue, 22 Sep 2009 14:30:46 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com>
Message-ID: <Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net>
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com> <Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net> <EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com> <20090922125450.GB12736@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-2133786286-2036955929-1253651838=:13053"
Content-ID: <Pine.LNX.4.64.0909221342120.13053@shell4.bayarea.net>
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS]   FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2009 21:29:46 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---2133786286-2036955929-1253651838=:13053
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.64.0909221342121.13053@shell4.bayarea.net>

Other than the copyright text that goes in MIB modules, the only 
issues that I know of that we all agreed were actually issues are 
the errata now on the RFC Editor site.  Attached is an e-mail 
message on this subject sent to David Harrington and Bert Wijnen 
earlier this year.

In my archives I found a discussion that tooks place between 16 Oct 
2005 and 4 Jan 2006 as to whether RFC 4181 should be listed as 
updating STD 58 (RFCs 2578, 2579, and 2580), as suggested by Alfred 
Hoenes.  We decided that the answer was NO, but in the process there 
was an inconclusive discussion as to whether the MUSTs in 4181 that 
go beyond the requirements of STD 58 (there are some in sec. 4.6.4) 
ought to be SHOULDs instead.  The subject lines in the relevant 
threads are "RFC 4181 indeed updates RFC 2578..2580" and "Erratum 
for RFC 4181".  If it's too much of a pain to search the mib-doctors 
archive, I can make the 28 messages that I saved from those threads 
available as a Unix mbox file.

Mike Heard

On Tue, 22 Sep 2009, Romascanu, Dan (Dan) wrote:
> Nothing as ordered as we would it to be. I remember discussions having
> started a few times but we need to go back into the MIB Doctors
> archives. There are also three verified errata (editorial stuff). 
> 
> Dan
>  
> 
> > -----Original Message-----
> > From: Juergen Schoenwaelder 
> > [mailto:j.schoenwaelder@jacobs-university.de] 
> > Sent: Tuesday, September 22, 2009 3:55 PM
> > To: Romascanu, Dan (Dan)
> > Cc: C. M. Heard; MIB Doctors (E-mail); OPS Area (E-mail)
> > Subject: Re: [OPS-AREA] [MIB-DOCTORS] FW: IESG Statement on Copyright
> > 
> > On Tue, Sep 22, 2009 at 02:48:03PM +0200, Romascanu, Dan (Dan) wrote:
> > 
> > > There are a number of issues that gathered around 4181 that would 
> > > deserve attention if a willing editor is found.
> > 
> > Do we have a list of those issues somewhere?
> > 
> > -- 
> > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> > Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> > 
> 
---2133786286-2036955929-1253651838=:13053
Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.64.0909221337170.13053@shell4.bayarea.net>
Content-Description: RE: Does another RFC4181 update need to be done? (fwd)

Return-Path: <heard@pobox.com>
Delivered-To: 2-heard@mail4.bayarea.net
Received: (qmail 11732 invoked from network); 3 Mar 2009 12:28:32 -0800
Received: from shell4.bayarea.net (209.128.82.1)
  by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 3 Mar 2009 12:28:31 -0800
Date: Tue, 3 Mar 2009 12:28:31 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: David Harrington <ietfdbh@comcast.net>
cc: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Subject: RE: Does another RFC4181 update need to be done?
In-Reply-To: <13cc01c99c2a$4c588940$0600a8c0@china.huawei.com>
Message-ID: <Pine.LNX.4.64.0903031142010.12325@shell4.bayarea.net>
References: <129c01c99bb0$f65e3bd0$0600a8c0@china.huawei.com>
 <Pine.LNX.4.64.0903022233340.5098@shell4.bayarea.net>
 <132d01c99c06$8d767fa0$0600a8c0@china.huawei.com>
 <Pine.LNX.4.64.0903030658290.15205@shell4.bayarea.net>
 <13cc01c99c2a$4c588940$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-2133786286-1532398083-1236104214=:32533"
Content-ID: <Pine.LNX.4.64.0903031208120.12325@shell4.bayarea.net>


  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---2133786286-1532398083-1236104214=:32533
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.64.0903031208121.12325@shell4.bayarea.net>

Hello David,

I looked in my mail archive and the only RFC 4181 errata that I 
found were in the attached message from 1 Nov 2005.  These, as it 
happens, have been posted by the RFC Editor, contrary to what I said 
below.  After so long away from the subject my memory of it is 
failing :-(

I do have some vague recollections of some other stuff that came up 
when we discussed the RFC 4181 update to recognize the IETF Trust 
(which became RFC 4841), but I can't find anything in my records.  
Bert once volunteered to convert the doucment in to xml2rfc format, 
and I sent him some errata that **may** have contained more than 
those in the attached message -- but I'm not sure.

Bert, if you have anything lying around that might help please 
forward it to David.

Thanks,

Mike

On Tue, 3 Mar 2009, David Harrington wrote:
> OK. If you send me the errata list, I will try to update the document
> (and convert source to xml2rfc format in the process).
> 
> Thanks,
> dbh
> 
> > -----Original Message-----
> > From: C. M. Heard [mailto:heard@pobox.com] 
> > Sent: Tuesday, March 03, 2009 10:42 AM
> > To: David Harrington
> > Cc: Bert Wijnen (IETF)
> > Subject: RE: Does another RFC4181 update need to be done?
> > 
> > I have the nroff source for the draft that was approved for 
> > publication.  That source does not include the changes made by the 
> > RFC, nor any subsequently reported errata (and not all of the ones 
> > reported by me and Alfred Hoenes were posted on the RFC Editor 
> > site).  There is no xml2rfc source.
> > 
> > Let me know if you want what I have.  Probably the most accurate way
> 
> > to do the update would be to start from the RFC text and the errata.
> 
> > I kept a list of errata that I could dig out for you.  I did that 
> > once for Bert.
> > 
> > Mike
> > 
> > 
> > On Tue, 3 Mar 2009, David Harrington wrote:
> > > Do you have the sources?
> > > I might find time to do a quick update.
> > > 
> > > dbh 
> > > 
> > > > -----Original Message-----
> > > > From: C. M. Heard [mailto:heard@pobox.com] 
> > > > Sent: Tuesday, March 03, 2009 1:51 AM
> > > > To: David Harrington
> > > > Cc: Dan Romascanu; Ron Bonica; Bert Wijnen (IETF)
> > > > Subject: Re: Does another RFC4181 update need to be done?
> > > > 
> > > > Yes it does -- but I don't have the time to do it.
> > > > 
> > > > It was a mistake (IMHO) to ever put any IPR stuff into 4181.  It
> > > > delayed the document by 1.5 years, waiting for the IPR WG to get
> > > > done with RFCs 3978 and 3979, and those docs have now been updated 
> > > > twice now.  If 4181 is ever rewritten and reissued, it should point 
> > > > to the legend instruction URLs -- which, one hopes, will be more
> > > > stable than the actual copyright text.
> > > > 
> > > > Mike Heard
> > > > 
> > > > On Mon, 2 Mar 2009, David Harrington wrote:
> > > > > Hi,
> > > > > 
> > > > > Does another RFC4181 update need to be done?
> > > > > See attached.
> > > > > 
> > > > > dbh
> > > > > 
> > > > > -----Original Message-----
> > > > > From: RFC Editor [mailto:rfc-editor@rfc-editor.org] 
> > > > > Sent: Monday, March 02, 2009 8:12 PM
> > > > > To: Glenn M. Keeni; Pasi Eronen; Tim Polk; Russ Housley
> > > > > Cc: Stacy Burns; Chris Lonvick; David Harrington; RFC Editor
> > > > > Subject: [ADs] Re: AUTH48 [SB]: RFC 5427
> > > > > <draft-ietf-syslog-tc-mib-08.txt> NOW AVAILABLE
> > > > > 
> > > > > Glenn, Pasi, and Tim,
> > > > > 
> > > > > Does the copyright in the MIB need to be updated?  The text currently
> > > > > reads:
> > > > > 
> > > > >     DESCRIPTION
> > > > >         "The MIB module containing textual conventions for syslog
> > > > >          messages.
> > > > > 
> > > > >          Copyright (C) The IETF Trust (2009).  This version of
> > > > >          this MIB module is part of RFC 5427; see the RFC itself for
> > > > >          full legal notices.
> > > > >         "
> > > > > 
> > > > > The BSD license in the IETF-Trust-License-Policy document states:
> > > > > 
> > > > >    Copyright (c) <insert year> IETF Trust and the persons identified as
> > > > >    authors of the code.  All rights reserved.   
> > > > > 
> > > > > Thanks!
> > > > > 
> > > > > RFC Editor
> > > > > 
> > > > > 
> > > > > 
> > > > > On Sat, Jan 10, 2009 at 11:17:30AM +0900, Glenn M. Keeni wrote:
> > > > > > 
> > > > > > Hi,
> > > > > >  I, an author of RFC 5427, am aware of the new copyright notice
> > > > > >  and I do approve this document (RFC 5427) for publication under
> > > > > >  the RFC 5378 copyright notice and legends.
> > > > > > 
> > > > > >  Thanks and cheers
> > > > > > 
> > > > > > Glenn
> > > > > > 
> > > > > > Stacy Burns wrote:
> > > > > > > Correction, inline.
> > > > > > > 
> > > > > > > RFC Editor/sb
> > > > > > > 
> > > > > > >> On Jan 9, 2009, at 11:02 AM, Stacy Burns wrote:
> > > > > > >> Glenn,
> > > > > > >>
> > > > > > >> As of 10 November 2008, the RFC Editor has been instructed to publish
> > > > > > >> documents with the copyright notice and legends adopted by the IETF
> > > > > > >> by the publication of BCP 78 / RFC 5378.  Please review the new 
> > > > > > >> copyright notice and legends and the text located at 
> > > > > > >> http://trustee.ietf.org/license-info/.
> > > > > > >>
> > > > > > >> If you, as an author of RFC 5410, agree with the copyright and
> > > > > > > If you, as an author of RFC 5427 ...
> > > > > > >> legends as defined in RFC 5378, please send us an explicit
> > > > > > >> acknowledgment that you are aware of the new copyright notice and
> > > > > > >> legends and that you approve this document for publication under the
> > > > > > >> RFC 5378 copyright notice and legends.  If all of the authors agree, 
> > > > > > >> we will update RFC 5410 to reflect the new copyright notice as it
> > > > > > >> appears in Item 6b of 
> > > > > > >> http://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf, and 
> > > > > > >> continue with the publication process.
> > > > > > >>
> > > > > > >> However, if you are unable to agree to publish the document with the
> > > > > > >> new copyright notice and legends, please let us know, and we will
> > > > > > >> delay publication until the issue has been resolved.  The appropriate
> > > > > > >> parties are working to resolve this issue as quickly as possible.  We 
> > > > > > >> plan to update you on the situation and provide an email address
> > > > > > >> (once it is available) where you can send your questions and/or 
> > > > > > >> concerns regarding the new copyright notice and legends.
> > > > > > >>
> > > > > > >> Please note that document currently available at 
> > > > > > >> http://www.rfc-editor.org/authors/rfc5427.txt doesn't reflect the 5378 
> > > > > > >> copyright. You must review it at http://trustee.ietf.org/license-info/.
> > > > > > >>
> > > > > > >> RFC Editor/sb
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > > 
> > 
> 
---2133786286-1532398083-1236104214=:32533
Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.64.0903031016520.32533@shell4.bayarea.net>
Content-Description: Re: Erratum for RFC 4181 (fwd)

Return-Path: <heard@pobox.com>
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id jA25CoYx024153;
	Tue, 1 Nov 2005 21:12:50 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id jA25CnH6024150;
	Tue, 1 Nov 2005 21:12:50 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 1 Nov 2005 21:12:49 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: RFC Editor <rfc-editor@rfc-editor.org>
cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        David Kessens <david.kessens@nokia.com>
Subject: Re: Erratum for RFC 4181
In-Reply-To: <Pine.LNX.4.10.10510231842180.17333-100000@shell4.bayarea.net>
Message-ID: <Pine.LNX.4.10.10511012100280.20281-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by shell4.bayarea.net id jA25CoYx024153

On Sun, 23 Oct 2005, C. M. Heard wrote:
> On Sun, 16 Oct 2005, Alfred HÎnes wrote:
> > I've [...] observed two minor typos in the text of RFC 4181
> > that migth be worth noting for consideration in the case of
> > any future update to this RFC:
> > 
> > *  The bottom text line of page 29 says:
> > 
> >       " ... .  Two point are worth reiterating:"
> >                        ^^
> >    It should say:
> > 
> >       " ... .  Two points are worth reiterating:"
> > 
> > *  The first line of item 8 in Appendix A, on page 34, says:
> > 
> >       "... -- if the draft does not contains a verbatim copy ..."
> >                                            ^
> >    It should say:
> > 
> >       "... -- if the draft does not contain a verbatim copy ..."
> 
> RFC Editor:
> 
> As document editor, I would like to request than an RFC Erratum be
> created for RFC 4181 listing these errors.  Thanks to Alfred HÎnes
> for pointing them out.

In addition to the above, I have noticed the following formatting
error in the first bullet in Section 4.6.1.1 on p. 14.  The text
in the RFC looks like this:

   - For integer-valued enumerations:

     - INTEGER is REQUIRED; - Integer32, Unsigned32, and Gauge32 MUST
     NOT be used.

and it should look like this:

   - For integer-valued enumerations:

     - INTEGER is REQUIRED;
     - Integer32, Unsigned32, and Gauge32 MUST NOT be used.

I would appreciate it if you would include this item when you create
the erratum for RFC 4181.


Regards,

Mike Heard

---2133786286-1532398083-1236104214=:32533--

---2133786286-2036955929-1253651838=:13053--

From dromasca@avaya.com  Wed Sep 23 01:13:53 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F313C3A689C; Wed, 23 Sep 2009 01:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level: 
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BlHiYRfZEyNe; Wed, 23 Sep 2009 01:13:52 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 6760A3A6851; Wed, 23 Sep 2009 01:13:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,437,1249272000"; d="scan'208";a="157677309"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 Sep 2009 04:14:54 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Sep 2009 04:14:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 23 Sep 2009 10:14:46 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A465FE@307622ANEX5.global.avaya.com>
In-Reply-To: <Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] [OPS-AREA]  FW: IESG Statement on Copyright
thread-index: Aco7zAO+hs+BOtyiT8eofmAt4Jem8wAWM0Fg
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com> <Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net> <EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com> <20090922125450.GB12736@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com> <Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "C. M. Heard" <heard@pobox.com>
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS]   FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 08:13:53 -0000

I have some good news to share. Randy Presuhn stepped ahead and accepted
to be the editor of 4181bis. Thanks, Randy!

I have two questions:=20

1. OPSAWG (which did not exist by the time 4181 was edited and
published) seems to me to be the natural home for 4181bis. Does anybody
see any problem with this? If all agree we shall move discussions to
opsawg@ietf.org

2.  What should be the scope of 4181bis?=20

Thanks and Regards,

Dan


> -----Original Message-----
> From: C. M. Heard [mailto:heard@pobox.com]=20
> Sent: Wednesday, September 23, 2009 12:31 AM
> To: Romascanu, Dan (Dan)
> Cc: Juergen Schoenwaelder; MIB Doctors (E-mail); OPS Area (E-mail)
> Subject: Re: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on Copyright
>=20
> Other than the copyright text that goes in MIB modules, the=20
> only issues that I know of that we all agreed were actually=20
> issues are the errata now on the RFC Editor site.  Attached=20
> is an e-mail message on this subject sent to David Harrington=20
> and Bert Wijnen earlier this year.
>=20
> In my archives I found a discussion that tooks place between 16 Oct
> 2005 and 4 Jan 2006 as to whether RFC 4181 should be listed=20
> as updating STD 58 (RFCs 2578, 2579, and 2580), as suggested=20
> by Alfred Hoenes.  We decided that the answer was NO, but in=20
> the process there was an inconclusive discussion as to=20
> whether the MUSTs in 4181 that go beyond the requirements of=20
> STD 58 (there are some in sec. 4.6.4) ought to be SHOULDs=20
> instead.  The subject lines in the relevant threads are "RFC=20
> 4181 indeed updates RFC 2578..2580" and "Erratum for RFC=20
> 4181".  If it's too much of a pain to search the mib-doctors=20
> archive, I can make the 28 messages that I saved from those=20
> threads available as a Unix mbox file.
>=20
> Mike Heard
>=20
> On Tue, 22 Sep 2009, Romascanu, Dan (Dan) wrote:
> > Nothing as ordered as we would it to be. I remember=20
> discussions having=20
> > started a few times but we need to go back into the MIB Doctors=20
> > archives. There are also three verified errata (editorial stuff).
> >=20
> > Dan
> > =20
> >=20
> > > -----Original Message-----
> > > From: Juergen Schoenwaelder
> > > [mailto:j.schoenwaelder@jacobs-university.de]
> > > Sent: Tuesday, September 22, 2009 3:55 PM
> > > To: Romascanu, Dan (Dan)
> > > Cc: C. M. Heard; MIB Doctors (E-mail); OPS Area (E-mail)
> > > Subject: Re: [OPS-AREA] [MIB-DOCTORS] FW: IESG Statement on=20
> > > Copyright
> > >=20
> > > On Tue, Sep 22, 2009 at 02:48:03PM +0200, Romascanu, Dan=20
> (Dan) wrote:
> > >=20
> > > > There are a number of issues that gathered around 4181=20
> that would=20
> > > > deserve attention if a willing editor is found.
> > >=20
> > > Do we have a list of those issues somewhere?
> > >=20
> > > --=20
> > > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > > Phone: +49 421 200 3587         Campus Ring 1, 28759=20
> Bremen, Germany
> > > Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> > >=20
> >=20
>=20

From dromasca@avaya.com  Wed Sep 23 01:25:03 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E80B33A682F; Wed, 23 Sep 2009 01:25:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level: 
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64d0IfnHDch9; Wed, 23 Sep 2009 01:25:03 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 0F0633A6783; Wed, 23 Sep 2009 01:25:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,437,1249272000"; d="scan'208";a="184284364"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 23 Sep 2009 04:26:08 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 23 Sep 2009 04:26:07 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 23 Sep 2009 10:26:02 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A46607@307622ANEX5.global.avaya.com>
In-Reply-To: <Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] [OPS-AREA]  FW: IESG Statement on Copyright
thread-index: Aco7zAO+hs+BOtyiT8eofmAt4Jem8wAW1H7g
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com> <Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net> <EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com> <20090922125450.GB12736@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com> <Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "C. M. Heard" <heard@pobox.com>
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS]   FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 08:25:04 -0000

=20

> -----Original Message-----
> From: C. M. Heard [mailto:heard@pobox.com]=20

>=20
> In my archives I found a discussion that tooks place between 16 Oct
> 2005 and 4 Jan 2006 as to whether RFC 4181 should be listed=20
> as updating STD 58 (RFCs 2578, 2579, and 2580), as suggested=20
> by Alfred Hoenes.  We decided that the answer was NO, but in=20
> the process there was an inconclusive discussion as to=20
> whether the MUSTs in 4181 that go beyond the requirements of=20
> STD 58 (there are some in sec. 4.6.4) ought to be SHOULDs=20
> instead.  The subject lines in the relevant threads are "RFC=20
> 4181 indeed updates RFC 2578..2580" and "Erratum for RFC=20
> 4181".  If it's too much of a pain to search the mib-doctors=20
> archive, I can make the 28 messages that I saved from those=20
> threads available as a Unix mbox file.
>=20
> Mike Heard
>=20

This was the conversation that I also had in mind, although for some
reasons I remembered it being more dramatic than it looks to me now.=20

Dan

From j.schoenwaelder@jacobs-university.de  Wed Sep 23 02:20:46 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C9B03A67B3; Wed, 23 Sep 2009 02:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[AWL=0.130,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H00E2PwA3tB5; Wed, 23 Sep 2009 02:20:45 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 86FE33A6985; Wed, 23 Sep 2009 02:20:45 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id B686EC000A; Wed, 23 Sep 2009 11:21:50 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id nxGWmqFkzqnY; Wed, 23 Sep 2009 11:21:49 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id F07CBC0007; Wed, 23 Sep 2009 11:21:48 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id D98E9CFBCB8; Wed, 23 Sep 2009 11:21:47 +0200 (CEST)
Date: Wed, 23 Sep 2009 11:21:47 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-ID: <20090923092147.GB14118@elstar.local>
Mail-Followup-To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "C. M. Heard" <heard@pobox.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, "OPS Area (E-mail)" <ops-area@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com> <Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net> <EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com> <20090922125450.GB12736@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com> <Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net> <EDC652A26FB23C4EB6384A4584434A0401A465FE@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401A465FE@307622ANEX5.global.avaya.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "C. M. Heard" <heard@pobox.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS]   FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 09:20:46 -0000

On Wed, Sep 23, 2009 at 10:14:46AM +0200, Romascanu, Dan (Dan) wrote:
> I have some good news to share. Randy Presuhn stepped ahead and accepted
> to be the editor of 4181bis. Thanks, Randy!
> 
> I have two questions: 
> 
> 1. OPSAWG (which did not exist by the time 4181 was edited and
> published) seems to me to be the natural home for 4181bis. Does anybody
> see any problem with this? If all agree we shall move discussions to
> opsawg@ietf.org
> 
> 2.  What should be the scope of 4181bis? 

Bug fixes and alignment to current IETF procedures and rules (although
the last thing might be an endless undertaking ;-). As little rewrite
as possible if you ask me.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From dbharrington@comcast.net  Wed Sep 23 07:06:14 2009
Return-Path: <dbharrington@comcast.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B1973A69EB for <ops-area@core3.amsl.com>; Wed, 23 Sep 2009 07:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level: 
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gh4auNEmvEBb for <ops-area@core3.amsl.com>; Wed, 23 Sep 2009 07:06:13 -0700 (PDT)
Received: from QMTA07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by core3.amsl.com (Postfix) with ESMTP id 2581B3A68A0 for <ops-area@ietf.org>; Wed, 23 Sep 2009 07:06:13 -0700 (PDT)
Received: from OMTA22.westchester.pa.mail.comcast.net ([76.96.62.73]) by QMTA07.westchester.pa.mail.comcast.net with comcast id kBgh1c0061ap0As57E7LxU; Wed, 23 Sep 2009 14:07:20 +0000
Received: from Harrington73653 ([24.147.240.98]) by OMTA22.westchester.pa.mail.comcast.net with comcast id kEBH1c002284sdk3iEBHC3; Wed, 23 Sep 2009 14:11:17 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>, "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com><Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net><EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com><20090922125450.GB12736@elstar.local><EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com><Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net><EDC652A26FB23C4EB6384A4584434A0401A465FE@307622ANEX5.global.avaya.com> <20090923092147.GB14118@elstar.local>
Date: Wed, 23 Sep 2009 10:07:16 -0400
Message-ID: <0a3801ca3c57$28d37b10$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20090923092147.GB14118@elstar.local>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aco8L0tsIugKjBB6Q9Sm+mYeVa/UvwAJ9fIg
Cc: "'C. M. Heard'" <heard@pobox.com>, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>, "'OPS Area \(E-mail\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS]   FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 14:06:14 -0000

+1 
dbh 

> -----Original Message-----
> From: mib-doctors-bounces@ietf.org 
> [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Juergen 
> Schoenwaelder
> Sent: Wednesday, September 23, 2009 5:22 AM
> To: Romascanu, Dan (Dan)
> Cc: C. M. Heard; MIB Doctors (E-mail); OPS Area (E-mail)
> Subject: Re: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on
Copyright
> 
> On Wed, Sep 23, 2009 at 10:14:46AM +0200, Romascanu, Dan (Dan)
wrote:
> > I have some good news to share. Randy Presuhn stepped ahead 
> and accepted
> > to be the editor of 4181bis. Thanks, Randy!
> > 
> > I have two questions: 
> > 
> > 1. OPSAWG (which did not exist by the time 4181 was edited and
> > published) seems to me to be the natural home for 4181bis. 
> Does anybody
> > see any problem with this? If all agree we shall move discussions
to
> > opsawg@ietf.org
> > 
> > 2.  What should be the scope of 4181bis? 
> 
> Bug fixes and alignment to current IETF procedures and rules
(although
> the last thing might be an endless undertaking ;-). As little
rewrite
> as possible if you ask me.
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
> 


From heard@pobox.com  Wed Sep 23 09:33:34 2009
Return-Path: <heard@pobox.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8440428C11A for <ops-area@core3.amsl.com>; Wed, 23 Sep 2009 09:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vZQrSZt+qHsM for <ops-area@core3.amsl.com>; Wed, 23 Sep 2009 09:33:34 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by core3.amsl.com (Postfix) with ESMTP id 5C7D03A69DE for <ops-area@ietf.org>; Wed, 23 Sep 2009 09:33:34 -0700 (PDT)
Received: (qmail 23104 invoked from network); 23 Sep 2009 09:27:19 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 23 Sep 2009 09:27:18 -0700
Date: Wed, 23 Sep 2009 09:27:18 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: David B Harrington <dbharrington@comcast.net>
In-Reply-To: <0a3801ca3c57$28d37b10$0600a8c0@china.huawei.com>
Message-ID: <Pine.LNX.4.64.0909230737180.24719@shell4.bayarea.net>
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com><Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net><EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com><20090922125450.GB12736@elstar.local><EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com><Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net><EDC652A26FB23C4EB6384A4584434A0401A465FE@307622ANEX5.global.avaya.com> <20090923092147.GB14118@elstar.local> <0a3801ca3c57$28d37b10$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-2133786286-2045072633-1253718822=:7169"
Content-ID: <Pine.LNX.4.64.0909230840500.29394@shell4.bayarea.net>
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>, "'OPS Area \(E-mail\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS]   FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 16:33:34 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---2133786286-2045072633-1253718822=:7169
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.64.0909230840501.29394@shell4.bayarea.net>

+1 also (though I really don't have a stake in the outcome).

One of the things that should probably be discussed is whether the 
issues brought up in the attached e-mail (downgrading some of the 
MUSTSs to SHOULDs) should be addressed under the head of bug fixes.

//cmh

On Wed, 23 Sep 2009, David B Harrington wrote:
> +1 
> dbh 
> 
> > -----Original Message-----
> > From: mib-doctors-bounces@ietf.org 
> > [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Juergen 
> > Schoenwaelder
> > Sent: Wednesday, September 23, 2009 5:22 AM
> > To: Romascanu, Dan (Dan)
> > Cc: C. M. Heard; MIB Doctors (E-mail); OPS Area (E-mail)
> > Subject: Re: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on Copyright
> > 
> > On Wed, Sep 23, 2009 at 10:14:46AM +0200, Romascanu, Dan (Dan) wrote:
> > > I have some good news to share. Randy Presuhn stepped ahead and accepted
> > > to be the editor of 4181bis. Thanks, Randy!
> > > 
> > > I have two questions: 
> > > 
> > > 1. OPSAWG (which did not exist by the time 4181 was edited and
> > > published) seems to me to be the natural home for 4181bis.  Does anybody
> > > see any problem with this? If all agree we shall move discussions to
> > > opsawg@ietf.org
> > > 
> > > 2.  What should be the scope of 4181bis? 
> > 
> > Bug fixes and alignment to current IETF procedures and rules (although
> > the last thing might be an endless undertaking ;-). As little rewrite
> > as possible if you ask me.
> > 
> > /js
> > 
> > -- 
> > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> > Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> > _______________________________________________
> > MIB-DOCTORS mailing list
> > MIB-DOCTORS@ietf.org
> > https://www.ietf.org/mailman/listinfo/mib-doctors
> > 
> 
---2133786286-2045072633-1253718822=:7169
Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.64.0909230813400.7169@shell4.bayarea.net>
Content-Description: Re: RFC 4181 indeed updates RFC 2578..2580 (fwd)

Return-Path: <SRS0=/nxR=YY=ops.ietf.org=owner-mreview@bounce2.pobox.com>
Received: from psmtp.com (exprod6mx146.postini.com [64.18.1.118])
	by shell4.bayarea.net (8.12.11/8.12.11) with SMTP id j9OK5ZJt010679
	for <heard@mail4.bayarea.net>; Mon, 24 Oct 2005 13:05:35 -0700
Received: from source ([209.128.95.9]) (using TLSv1) by exprod6mx146.postini.com ([64.18.5.10]) with SMTP;
	Mon, 24 Oct 2005 15:05:35 CDT
Received: from snug.pobox.com (snug.pobox.com [208.210.124.72])
	by mx1.bayarea.net (8.12.8/8.12.8) with ESMTP id j9OK5ZDI027146
	for <heard@bayarea.net>; Mon, 24 Oct 2005 13:05:35 -0700
Received: from psg.com (psg.com [147.28.0.62])
	by snug.pobox.com (Postfix) with ESMTP id B16C515B01
	for <heard@pobox.com>; Mon, 24 Oct 2005 16:05:54 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.52 (FreeBSD))
	id 1EU8ZY-00010r-Mz
	for mreview-data@psg.com; Mon, 24 Oct 2005 20:05:32 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.0
Received: from [205.178.146.50] (helo=mail.networksolutionsemail.com)
	by psg.com with smtp (Exim 4.52 (FreeBSD))
	id 1EU8ZX-00010U-Gq
	for mreview@ops.ietf.org; Mon, 24 Oct 2005 20:05:31 +0000
Received: (qmail 8055 invoked by uid 78); 24 Oct 2005 20:05:29 -0000
Received: from unknown (HELO ?127.0.0.1?) (24.24.133.237)
  by 10.49.34.55 with SMTP; 24 Oct 2005 20:05:29 -0000
Message-ID: <435D3E75.6040308@andybierman.com>
Date: Mon, 24 Oct 2005 13:05:09 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dbharrington@comcast.net
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Mreview (E-mail)'" <mreview@ops.ietf.org>,
        =?ISO-8859-1?Q?=27Alfred_H=CEnes=27?= <ah@tr-sys.de>
Subject: Re: RFC 4181 indeed updates RFC 2578..2580 (fwd)
References: <001b01c5d8ca$e5a7f3f0$0400a8c0@DJYXPY41>
In-Reply-To: <001b01c5d8ca$e5a7f3f0$0400a8c0@DJYXPY41>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-mreview@ops.ietf.org
Precedence: bulk
X-pstn-levels: (S:99.90000/99.90000 R:95.9108 P:95.9108 M:97.0232 C:98.7678 )
X-pstn-settings: 4 (1.5000:1.5000) s gt3 gt2 gt1 r p m c 
X-pstn-addresses: from <ietf@andybierman.com> [1360/57] 


David B Harrington wrote:

>Hi,
>
>As I contributed to the development of the mib guidelines, I thought
>we were producing guidelines to help people, not new rules to hit them
>over the head with.
>
>RFCs 2578-2580 were developed by a working group, following
>appropriate IETF procedures for developing new standards-track RFCs,
>notably those procedures documented in RFC2026, section 6.2. 
>
>The mib guidelines were developed by the MIB Doctors, a closed group,
>following a process that was consistent with BCP procedures, but not
>consistent with IETF procedures for developing new standards-track
>RFCs.
>
>Therefore, I object to the mib guidelines, a BCP document, being
>considered an official update to the SMIv2 STD rules, and I object to
>enforcement of the new MUST requirements in the mib guidelines, since
>those requirements can have a serious impact on implementers, who have
>not had the opportunity to debate the proposals in an open working
>group, and test the proposed and draft standards, as afforded by the
>three-phase standards-development process. 
>
>Is that a solid-enough opinion on the topic?
>

I agree with you.  I don't care as much about SNMP as I used to,
but from a process POV, it is better to make these guidelines SHOULD
instead of MUST, especially en masse.  IMO, MUST should be reserved
for when it would cause "obvious harm to interoperability" to do otherwise.
MIB style guidelines have a minimal impact (at best) on interoperability.
(Perhaps SHOULD is even too strong for some guidelines, but MAY is
too weak. Oh well.)

>David Harrington
>dbharrington@comcast.net
>

Andy

>
>>-----Original Message-----
>>From: owner-mreview@ops.ietf.org 
>>[mailto:owner-mreview@ops.ietf.org] On Behalf Of C. M. Heard
>>Sent: Monday, October 24, 2005 11:04 AM
>>To: Mreview (E-mail)
>>Cc: Alfred HÎnes
>>Subject: RE: RFC 4181 indeed updates RFC 2578..2580 (fwd)
>>
>>On Sat, 22 Oct 2005, Wijnen, Bert (Bert) wrote:
>>> If we want to do anything we should create the exact and complete list
>>> of what we are altering. Note that if something that is OK in STD58
>>> and is still OK/ACCEPTABLE (although maybe not recommended or prefered
>>> by RFC4181), then we (MIB doctors) can strongly advise a WG to follow
>>> the recommendations of 4181, but I doubt we can block a document for
>>> that. So I am somewhat hesitant to tag 4181 with a "Updates STD58"
>>> because it makes the "guidelines" a "hard rules" as opposed to
>>> guidelines. I think we intended the last (namely guidelines). I do
>>> see that at a few places we may be saying that we are in fact 
>>> changing a rule.
>>
>>Obviously, the "General Documentation Guidelines" in Section 3 don't
>>have anything to do with RFCs 2578/2579/2580 so we can focus attention
>>on Section 4, which says:
>>
>>   The guidelines in this section are intended to supplement the SMIv2
>>   documents in the following ways:
>>
>>    o to document the current generally accepted interpretation when
>>      those documents contain ambiguities or contradictions;
>>
>>    o to update recommendations in those documents that have been shown
>>      by practical experience to be out-of-date or otherwise suboptimal;
>>
>>    o to provide guidance in selection of SMIv2 options in cases where
>>      there is a consensus on a preferred approach.
>>
>>The first two bullets are clearly things that could be considered as
>>updating the SMIv2 RFCs, although there is precedent for not
>>considering ambiguity resolution as a specification update (for
>>instance RFC 1122 is not listed as updating RFCs 791 and 792, even
>>though it has text to clear up many ambiguities in those
>>specifications).  The last bullet covers usage guidelines, and I
>>tend to agree with Bert that since those are guidelines and not
>>hard-and-fast requirements they need not be considered updating to
>>the SMIv2 RFCs.
>>
>>Here is a list of things I've found in RFC 4181 that either update a
>>recommendation or document and resolve a contradiction in the SMIv2
>>RFCs.  The list seems pretty short;  it is possible that I've
>>overlooked something.
>>
>>- Section 4.2 abolishes the recommendation in RFCs 2579 and 2579
>>that names be limited to 32 characters.  It does not alter the
>>requirement that names be limited to 64 characters, so the critera
>>for syntactic validity remain unchanged.
>>
>>- Section 4.6.1.2 abolishes the requirement that RFC 2578 imposes on
>>"standard" MIB modules that the Counter64 type may be used only if
>>the information being modelled would wrap in less than one hour if
>>the Counter32 type was used instead.
>>
>>- Section 4.9 resolves contradictions between the general rule that
>>MIB moudule revisions shall not make semantic changes to existing
>>definitions and the specific lists of changes that RFC 2580 allows
>>to be made to compliance statements and capabilities statements.
>>
>>HOWEVER, this is not the whole story.
>>
>>After re-reading the document it becomes clear that RFC 4181 Section
>>4 supplements the SMIv2 documents in at least one other way that
>>those stated:  in some cases content requirements are imposed on
>>IETF MIB modules that go beyond the minimal requirements of correct
>>syntax specified in the STD 58 documents.  One example is Section
>>4.5 on the usage of the MODULE-IDENTITY macro.  It says:
>>
>>   RFC 2578 Section 5 describes how the various clauses are used.  The
>>   following additional guidelines apply to all MIB modules over which
>>   the IETF has change control:
>>
>>Another example is the following from Section 4.6.4:
>>
>>   - If dynamic row creation and/or deletion by management applications
>>     is supported, then:
>>   [ ... ]
>>     - There either MUST be one columnar object with a SYNTAX value of
>>       StorageType [RFC2579] and a MAX-ACCESS value of read-create, or
>>       else the row object (table entry) DESCRIPTION clause MUST specify
>>       what happens to dynamically-created rows after an agent restart.
>>
>>     - If the agent itself may also create and/or delete rows, then the
>>       conditions under which this can occur MUST be clearly documented
>>       in the row object DESCRIPTION clause.
>>
>>Should these things be considered as updating the STD 58 RFCs?  Or is
>>the situation something like the Host Requirements documents (RFCs
>>1122/1123, STD 3), which specify requirements for hosts that are in
>>addition to the basic requirements of the underlying protocols?
>>
>>Mike
>>
>

---2133786286-2045072633-1253718822=:7169--

From dromasca@avaya.com  Fri Sep 25 08:16:53 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1BE5F3A695D; Fri, 25 Sep 2009 08:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.46
X-Spam-Level: 
X-Spam-Status: No, score=-2.46 tagged_above=-999 required=5 tests=[AWL=0.139,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yLFC4hBNsoeJ; Fri, 25 Sep 2009 08:16:52 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 6541A3A6961; Fri, 25 Sep 2009 08:16:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,452,1249272000"; d="scan'208";a="157973826"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 25 Sep 2009 11:18:00 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Sep 2009 11:17:58 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 Sep 2009 17:17:49 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A84CEC@307622ANEX5.global.avaya.com>
In-Reply-To: <Pine.LNX.4.64.0909230737180.24719@shell4.bayarea.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] [OPS-AREA]  FW: IESG Statement on Copyright
thread-index: Aco8aslj/dPJqnEzRoOTg8Cl6AxC1wBh3hXA
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com><Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net><EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com><20090922125450.GB12736@elstar.local><EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com><Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net><EDC652A26FB23C4EB6384A4584434A0401A465FE@307622ANEX5.global.avaya.com><20090923092147.GB14118@elstar.local><0a3801ca3c57$28d37b10$0600a8c0@china.huawei.com> <Pine.LNX.4.64.0909230737180.24719@shell4.bayarea.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "C. M. Heard" <heard@pobox.com>, "David B Harrington" <dbharrington@comcast.net>
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS]   FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 15:16:53 -0000

I think that we should consider also the following:=20

1. Update the tools information. We refer now
http://www.ops.ietf.org/mib-review-tools.html but is the information
there accurate, with smicng support aparently discontinued?=20

2. information about templates - refer to RFC 5249 ?=20

Also - is it time to move this discussion to OPSAWG?=20

Dan
(speaking as contributor)

> -----Original Message-----
> From: mib-doctors-bounces@ietf.org=20
> [mailto:mib-doctors-bounces@ietf.org] On Behalf Of C. M. Heard
> Sent: Wednesday, September 23, 2009 7:27 PM
> To: David B Harrington
> Cc: 'MIB Doctors (E-mail)'; 'OPS Area (E-mail)'
> Subject: Re: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on Copyright
>=20
> +1 also (though I really don't have a stake in the outcome).
>=20
> One of the things that should probably be discussed is=20
> whether the issues brought up in the attached e-mail=20
> (downgrading some of the MUSTSs to SHOULDs) should be=20
> addressed under the head of bug fixes.
>=20
> //cmh
>=20
> On Wed, 23 Sep 2009, David B Harrington wrote:
> > +1
> > dbh
> >=20
> > > -----Original Message-----
> > > From: mib-doctors-bounces@ietf.org
> > > [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Juergen=20
> > > Schoenwaelder
> > > Sent: Wednesday, September 23, 2009 5:22 AM
> > > To: Romascanu, Dan (Dan)
> > > Cc: C. M. Heard; MIB Doctors (E-mail); OPS Area (E-mail)
> > > Subject: Re: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on=20
> > > Copyright
> > >=20
> > > On Wed, Sep 23, 2009 at 10:14:46AM +0200, Romascanu, Dan=20
> (Dan) wrote:
> > > > I have some good news to share. Randy Presuhn stepped ahead and=20
> > > > accepted to be the editor of 4181bis. Thanks, Randy!
> > > >=20
> > > > I have two questions:=20
> > > >=20
> > > > 1. OPSAWG (which did not exist by the time 4181 was edited and
> > > > published) seems to me to be the natural home for=20
> 4181bis.  Does=20
> > > > anybody see any problem with this? If all agree we shall move=20
> > > > discussions to opsawg@ietf.org
> > > >=20
> > > > 2.  What should be the scope of 4181bis?=20
> > >=20
> > > Bug fixes and alignment to current IETF procedures and rules=20
> > > (although the last thing might be an endless undertaking ;-). As=20
> > > little rewrite as possible if you ask me.
> > >=20
> > > /js
> > >=20
> > > --=20
> > > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > > Phone: +49 421 200 3587         Campus Ring 1, 28759=20
> Bremen, Germany
> > > Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> > > _______________________________________________
> > > MIB-DOCTORS mailing list
> > > MIB-DOCTORS@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mib-doctors
> > >=20
> >=20
>=20

From paduffy@cisco.com  Fri Sep 25 08:43:28 2009
Return-Path: <paduffy@cisco.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A74AE3A6842 for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 08:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aTuZf3b-sk9U for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 08:43:27 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 7DD763A65A6 for <ops-area@ietf.org>; Fri, 25 Sep 2009 08:43:27 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAOeBvEqrR7PD/2dsb2JhbAC+XIEYCAGHMgGPfgWEHg
X-IronPort-AV: E=Sophos;i="4.44,452,1249257600"; d="scan'208";a="247007707"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 25 Sep 2009 15:44:37 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n8PFibcA031864 for <ops-area@ietf.org>; Fri, 25 Sep 2009 08:44:37 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n8PFiXad023444 for <ops-area@ietf.org>; Fri, 25 Sep 2009 15:44:37 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 25 Sep 2009 11:44:36 -0400
Received: from [161.44.65.120] ([161.44.65.120]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 25 Sep 2009 11:44:36 -0400
Message-ID: <4ABCE564.20101@cisco.com>
Date: Fri, 25 Sep 2009 11:44:36 -0400
From: Paul Duffy <paduffy@cisco.com>
Organization: Cisco Systems
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "OPS Area (E-mail)" <ops-area@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Sep 2009 15:44:36.0535 (UTC) FILETIME=[15CB6C70:01CA3DF7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=798; t=1253893477; x=1254757477; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paduffy@cisco.com; z=From:=20Paul=20Duffy=20<paduffy@cisco.com> |Subject:=20Present=20day=20reality=20of=20COPS-PR |Sender:=20; bh=7+kY72J09TFQ4QlulRpelRSJaM4ldK0bdI+nngxlVhM=; b=qowmVuvzBKZXxuDucCeMArO2aN0ssoivIA3uCyA6l2SczPR8x0EtZexO8h kFmYlhWlfnhzeRNzXUZPxkZ1fjOlR4YDNeuDv7Oyb/nq5ZSjSFPMKfalr+qG Fd0pxiYr3R;
Authentication-Results: sj-dkim-3; header.From=paduffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: [OPS-AREA] Present day reality of COPS-PR
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: paduffy@cisco.com
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 15:43:28 -0000

Folks,

I recently had to do a quick eval re: COPS-PR viability.  Please correct 
as needed, and thanks for your input.

-----------

COPS-PR seems a solution that was looking for a problem.  It never 
really took off, for the following reasons....

- most, if not all, of what could be done with COPS-PR/PIBs can be done
with SNMP/MIBs. To do both is significant duplicated effort.

- operators don't want binary PIBs, prefer ASCII based CLI-type interfaces.

- key players (who?) withdrew from COPS-PR and PIB approach, claiming
there was no market.

- IETF has since gone down the path of Netconf and started discussion to
make COPS-PR historical.

- there are few, if any, significant deployments.

AFAIK, there is minimal commercial or open source support.


Cheers




From rbonica@juniper.net  Fri Sep 25 08:57:28 2009
Return-Path: <rbonica@juniper.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DFB6B3A6948 for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 08:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.493
X-Spam-Level: 
X-Spam-Status: No, score=-6.493 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kZlRqge3Ythv for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 08:57:28 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by core3.amsl.com (Postfix) with ESMTP id A79F73A6937 for <ops-area@ietf.org>; Fri, 25 Sep 2009 08:57:26 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKSrzorHTA1LO9A1dsQPyHfWlvFoOJrNt9@postini.com; Fri, 25 Sep 2009 08:58:39 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 25 Sep 2009 08:54:48 -0700
Received: from [172.28.134.53] (172.28.134.53) by p-emfe02-wf.jnpr.net (172.28.145.22) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 25 Sep 2009 11:54:47 -0400
Message-ID: <4ABCE7C6.5050807@juniper.net>
Date: Fri, 25 Sep 2009 11:54:46 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "paduffy@cisco.com" <paduffy@cisco.com>
References: <4ABCE564.20101@cisco.com>
In-Reply-To: <4ABCE564.20101@cisco.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] Present day reality of COPS-PR
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 15:57:29 -0000

Paul,

Speaking as an individual contributor, I think that your analysis is on
target. Speaking as AD, I would support a motion to move the COPS
documents to HISTORIC.

                                Ron


Paul Duffy wrote:
> Folks,
> 
> I recently had to do a quick eval re: COPS-PR viability.  Please correct 
> as needed, and thanks for your input.
> 
> -----------
> 
> COPS-PR seems a solution that was looking for a problem.  It never 
> really took off, for the following reasons....
> 
> - most, if not all, of what could be done with COPS-PR/PIBs can be done
> with SNMP/MIBs. To do both is significant duplicated effort.
> 
> - operators don't want binary PIBs, prefer ASCII based CLI-type interfaces.
> 
> - key players (who?) withdrew from COPS-PR and PIB approach, claiming
> there was no market.
> 
> - IETF has since gone down the path of Netconf and started discussion to
> make COPS-PR historical.
> 
> - there are few, if any, significant deployments.
> 
> AFAIK, there is minimal commercial or open source support.
> 
> 
> Cheers
> 
> 
> 
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 

From dromasca@avaya.com  Fri Sep 25 08:59:17 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FFD03A62C1 for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 08:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.462
X-Spam-Level: 
X-Spam-Status: No, score=-2.462 tagged_above=-999 required=5 tests=[AWL=0.137,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qlwaSvOM5ewy for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 08:59:16 -0700 (PDT)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 0A3053A67A7 for <ops-area@ietf.org>; Fri, 25 Sep 2009 08:59:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,452,1249272000"; d="scan'208";a="174650769"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 25 Sep 2009 12:00:26 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 25 Sep 2009 12:00:26 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 Sep 2009 18:00:24 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A84CF2@307622ANEX5.global.avaya.com>
In-Reply-To: <4ABCE7C6.5050807@juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] Present day reality of COPS-PR
thread-index: Aco9+Q/FYcyoCc//Ssu1wmBIuIJ8KwAAB+qg
References: <4ABCE564.20101@cisco.com> <4ABCE7C6.5050807@juniper.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Ron Bonica" <rbonica@juniper.net>, <paduffy@cisco.com>
Cc: "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] Present day reality of COPS-PR
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 15:59:17 -0000

Let us move this discussion to OPSAWG where a proposal was made in
Stockholm on this respect. We need a volunteer to write the RFC.=20

Dan
=20

> -----Original Message-----
> From: ops-area-bounces@ietf.org=20
> [mailto:ops-area-bounces@ietf.org] On Behalf Of Ron Bonica
> Sent: Friday, September 25, 2009 6:55 PM
> To: paduffy@cisco.com
> Cc: OPS Area (E-mail)
> Subject: Re: [OPS-AREA] Present day reality of COPS-PR
>=20
> Paul,
>=20
> Speaking as an individual contributor, I think that your=20
> analysis is on target. Speaking as AD, I would support a=20
> motion to move the COPS documents to HISTORIC.
>=20
>                                 Ron
>=20
>=20
> Paul Duffy wrote:
> > Folks,
> >=20
> > I recently had to do a quick eval re: COPS-PR viability.  Please=20
> > correct as needed, and thanks for your input.
> >=20
> > -----------
> >=20
> > COPS-PR seems a solution that was looking for a problem.  It never=20
> > really took off, for the following reasons....
> >=20
> > - most, if not all, of what could be done with COPS-PR/PIBs can be=20
> > done with SNMP/MIBs. To do both is significant duplicated effort.
> >=20
> > - operators don't want binary PIBs, prefer ASCII based=20
> CLI-type interfaces.
> >=20
> > - key players (who?) withdrew from COPS-PR and PIB=20
> approach, claiming=20
> > there was no market.
> >=20
> > - IETF has since gone down the path of Netconf and started=20
> discussion=20
> > to make COPS-PR historical.
> >=20
> > - there are few, if any, significant deployments.
> >=20
> > AFAIK, there is minimal commercial or open source support.
> >=20
> >=20
> > Cheers
> >=20
> >=20
> >=20
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >=20
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
>=20

From rbonica@juniper.net  Fri Sep 25 09:13:05 2009
Return-Path: <rbonica@juniper.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD9683A69D7 for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 09:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.496
X-Spam-Level: 
X-Spam-Status: No, score=-6.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWWrDZ1PbS2x for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 09:13:05 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by core3.amsl.com (Postfix) with ESMTP id E15A33A6944 for <ops-area@ietf.org>; Fri, 25 Sep 2009 09:13:04 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKSrzsVhdVEb5jlhRTOos08y8PzlT8DD3u@postini.com; Fri, 25 Sep 2009 09:14:16 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 25 Sep 2009 09:11:09 -0700
Received: from [172.28.134.53] (172.28.134.53) by p-emfe02-wf.jnpr.net (172.28.145.22) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 25 Sep 2009 12:11:09 -0400
Message-ID: <4ABCEB9C.2000505@juniper.net>
Date: Fri, 25 Sep 2009 12:11:08 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
References: <4ABCE564.20101@cisco.com> <4ABCE7C6.5050807@juniper.net> <EDC652A26FB23C4EB6384A4584434A0401A84CF2@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401A84CF2@307622ANEX5.global.avaya.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] Present day reality of COPS-PR
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 16:13:06 -0000

Sorry. I confused the two mailing lists....

                         Ron


Romascanu, Dan (Dan) wrote:
> Let us move this discussion to OPSAWG where a proposal was made in
> Stockholm on this respect. We need a volunteer to write the RFC. 
> 
> Dan
>  
> 
>> -----Original Message-----
>> From: ops-area-bounces@ietf.org 
>> [mailto:ops-area-bounces@ietf.org] On Behalf Of Ron Bonica
>> Sent: Friday, September 25, 2009 6:55 PM
>> To: paduffy@cisco.com
>> Cc: OPS Area (E-mail)
>> Subject: Re: [OPS-AREA] Present day reality of COPS-PR
>>
>> Paul,
>>
>> Speaking as an individual contributor, I think that your 
>> analysis is on target. Speaking as AD, I would support a 
>> motion to move the COPS documents to HISTORIC.
>>
>>                                 Ron
>>
>>
>> Paul Duffy wrote:
>>> Folks,
>>>
>>> I recently had to do a quick eval re: COPS-PR viability.  Please 
>>> correct as needed, and thanks for your input.
>>>
>>> -----------
>>>
>>> COPS-PR seems a solution that was looking for a problem.  It never 
>>> really took off, for the following reasons....
>>>
>>> - most, if not all, of what could be done with COPS-PR/PIBs can be 
>>> done with SNMP/MIBs. To do both is significant duplicated effort.
>>>
>>> - operators don't want binary PIBs, prefer ASCII based 
>> CLI-type interfaces.
>>> - key players (who?) withdrew from COPS-PR and PIB 
>> approach, claiming 
>>> there was no market.
>>>
>>> - IETF has since gone down the path of Netconf and started 
>> discussion 
>>> to make COPS-PR historical.
>>>
>>> - there are few, if any, significant deployments.
>>>
>>> AFAIK, there is minimal commercial or open source support.
>>>
>>>
>>> Cheers
>>>
>>>
>>>
>>> _______________________________________________
>>> OPS-AREA mailing list
>>> OPS-AREA@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ops-area
>>>
>> _______________________________________________
>> OPS-AREA mailing list
>> OPS-AREA@ietf.org
>> https://www.ietf.org/mailman/listinfo/ops-area
>>
> .
> 

From dbharrington@comcast.net  Fri Sep 25 09:27:09 2009
Return-Path: <dbharrington@comcast.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0DFC3A69E2 for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 09:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zpdsLQ85+fDP for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 09:27:08 -0700 (PDT)
Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by core3.amsl.com (Postfix) with ESMTP id 3E7A73A68DE for <ops-area@ietf.org>; Fri, 25 Sep 2009 09:27:08 -0700 (PDT)
Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA10.westchester.pa.mail.comcast.net with comcast id l2x11c0081HzFnQ5A4ULZo; Fri, 25 Sep 2009 16:28:20 +0000
Received: from Harrington73653 ([24.147.240.98]) by OMTA14.westchester.pa.mail.comcast.net with comcast id l4UL1c001284sdk3a4ULcb; Fri, 25 Sep 2009 16:28:20 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, "'C. M. Heard'" <heard@pobox.com>
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com><Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net><EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com><20090922125450.GB12736@elstar.local><EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com><Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net><EDC652A26FB23C4EB6384A4584434A0401A465FE@307622ANEX5.global.avaya.com><20090923092147.GB14118@elstar.local><0a3801ca3c57$28d37b10$0600a8c0@china.huawei.com> <Pine.LNX.4.64.0909230737180.24719@shell4.bayarea.net> <EDC652A26FB23C4EB6384A4584434A0401A84CEC@307622ANEX5.global.avaya.com>
Date: Fri, 25 Sep 2009 12:28:18 -0400
Message-ID: <0bd301ca3dfd$31191cb0$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401A84CEC@307622ANEX5.global.avaya.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aco8aslj/dPJqnEzRoOTg8Cl6AxC1wBh3hXAAAK0LPA=
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>, "'OPS Area \(E-mail\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS]   FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 16:27:09 -0000

The MIB templates should be updated to match the updated copyright as
well.
I think should also be done in OPSAWG.

dbh 

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
> Sent: Friday, September 25, 2009 11:18 AM
> To: C. M. Heard; David B Harrington
> Cc: MIB Doctors (E-mail); OPS Area (E-mail)
> Subject: RE: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on
Copyright
> 
> I think that we should consider also the following: 
> 
> 1. Update the tools information. We refer now
> http://www.ops.ietf.org/mib-review-tools.html but is the information
> there accurate, with smicng support aparently discontinued? 
> 
> 2. information about templates - refer to RFC 5249 ? 
> 
> Also - is it time to move this discussion to OPSAWG? 
> 
> Dan
> (speaking as contributor)
> 
> > -----Original Message-----
> > From: mib-doctors-bounces@ietf.org 
> > [mailto:mib-doctors-bounces@ietf.org] On Behalf Of C. M. Heard
> > Sent: Wednesday, September 23, 2009 7:27 PM
> > To: David B Harrington
> > Cc: 'MIB Doctors (E-mail)'; 'OPS Area (E-mail)'
> > Subject: Re: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on 
> Copyright
> > 
> > +1 also (though I really don't have a stake in the outcome).
> > 
> > One of the things that should probably be discussed is 
> > whether the issues brought up in the attached e-mail 
> > (downgrading some of the MUSTSs to SHOULDs) should be 
> > addressed under the head of bug fixes.
> > 
> > //cmh
> > 
> > On Wed, 23 Sep 2009, David B Harrington wrote:
> > > +1
> > > dbh
> > > 
> > > > -----Original Message-----
> > > > From: mib-doctors-bounces@ietf.org
> > > > [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Juergen 
> > > > Schoenwaelder
> > > > Sent: Wednesday, September 23, 2009 5:22 AM
> > > > To: Romascanu, Dan (Dan)
> > > > Cc: C. M. Heard; MIB Doctors (E-mail); OPS Area (E-mail)
> > > > Subject: Re: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on 
> > > > Copyright
> > > > 
> > > > On Wed, Sep 23, 2009 at 10:14:46AM +0200, Romascanu, Dan 
> > (Dan) wrote:
> > > > > I have some good news to share. Randy Presuhn stepped 
> ahead and 
> > > > > accepted to be the editor of 4181bis. Thanks, Randy!
> > > > > 
> > > > > I have two questions: 
> > > > > 
> > > > > 1. OPSAWG (which did not exist by the time 4181 was edited
and
> > > > > published) seems to me to be the natural home for 
> > 4181bis.  Does 
> > > > > anybody see any problem with this? If all agree we shall
move 
> > > > > discussions to opsawg@ietf.org
> > > > > 
> > > > > 2.  What should be the scope of 4181bis? 
> > > > 
> > > > Bug fixes and alignment to current IETF procedures and rules 
> > > > (although the last thing might be an endless 
> undertaking ;-). As 
> > > > little rewrite as possible if you ask me.
> > > > 
> > > > /js
> > > > 
> > > > -- 
> > > > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > > > Phone: +49 421 200 3587         Campus Ring 1, 28759 
> > Bremen, Germany
> > > > Fax:   +49 421 200 3103         
> <http://www.jacobs-university.de/>
> > > > _______________________________________________
> > > > MIB-DOCTORS mailing list
> > > > MIB-DOCTORS@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/mib-doctors
> > > > 
> > > 
> > 
> 


From dromasca@avaya.com  Fri Sep 25 09:35:23 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3F633A68D4; Fri, 25 Sep 2009 09:35:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.463
X-Spam-Level: 
X-Spam-Status: No, score=-2.463 tagged_above=-999 required=5 tests=[AWL=0.136,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrgcdzH423xY; Fri, 25 Sep 2009 09:35:21 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 2DA7B3A67D8; Fri, 25 Sep 2009 09:35:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,452,1249272000"; d="scan'208";a="157982764"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 25 Sep 2009 12:36:20 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Sep 2009 12:36:18 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 Sep 2009 18:36:08 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A84CF6@307622ANEX5.global.avaya.com>
In-Reply-To: <0bd301ca3dfd$31191cb0$0600a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] [OPS-AREA]  FW: IESG Statement on Copyright
thread-index: Aco8aslj/dPJqnEzRoOTg8Cl6AxC1wBh3hXAAAK0LPAAAEnFYA==
References: <EDC652A26FB23C4EB6384A4584434A0401A45B79@307622ANEX5.global.avaya.com><Pine.LNX.4.64.0909211433360.11502@shell4.bayarea.net><EDC652A26FB23C4EB6384A4584434A0401A46408@307622ANEX5.global.avaya.com><20090922125450.GB12736@elstar.local><EDC652A26FB23C4EB6384A4584434A0401A4641D@307622ANEX5.global.avaya.com><Pine.LNX.4.64.0909221338320.13053@shell4.bayarea.net><EDC652A26FB23C4EB6384A4584434A0401A465FE@307622ANEX5.global.avaya.com><20090923092147.GB14118@elstar.local><0a3801ca3c57$28d37b10$0600a8c0@china.huawei.com> <Pine.LNX.4.64.0909230737180.24719@shell4.bayarea.net> <EDC652A26FB23C4EB6384A4584434A0401A84CEC@307622ANEX5.global.avaya.com> <0bd301ca3dfd$31191cb0$0600a8c0@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David B Harrington" <dbharrington@comcast.net>, "C. M. Heard" <heard@pobox.com>
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [MIB-DOCTORS]   FW: IESG Statement on Copyright
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 16:35:23 -0000

Good point.=20

Dan
=20

> -----Original Message-----
> From: David B Harrington [mailto:dbharrington@comcast.net]=20
> Sent: Friday, September 25, 2009 7:28 PM
> To: Romascanu, Dan (Dan); 'C. M. Heard'
> Cc: 'MIB Doctors (E-mail)'; 'OPS Area (E-mail)'
> Subject: RE: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on Copyright
>=20
> The MIB templates should be updated to match the updated=20
> copyright as well.
> I think should also be done in OPSAWG.
>=20
> dbh=20
>=20
> > -----Original Message-----
> > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > Sent: Friday, September 25, 2009 11:18 AM
> > To: C. M. Heard; David B Harrington
> > Cc: MIB Doctors (E-mail); OPS Area (E-mail)
> > Subject: RE: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on
> Copyright
> >=20
> > I think that we should consider also the following:=20
> >=20
> > 1. Update the tools information. We refer now=20
> > http://www.ops.ietf.org/mib-review-tools.html but is the=20
> information=20
> > there accurate, with smicng support aparently discontinued?
> >=20
> > 2. information about templates - refer to RFC 5249 ?=20
> >=20
> > Also - is it time to move this discussion to OPSAWG?=20
> >=20
> > Dan
> > (speaking as contributor)
> >=20
> > > -----Original Message-----
> > > From: mib-doctors-bounces@ietf.org
> > > [mailto:mib-doctors-bounces@ietf.org] On Behalf Of C. M. Heard
> > > Sent: Wednesday, September 23, 2009 7:27 PM
> > > To: David B Harrington
> > > Cc: 'MIB Doctors (E-mail)'; 'OPS Area (E-mail)'
> > > Subject: Re: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on
> > Copyright
> > >=20
> > > +1 also (though I really don't have a stake in the outcome).
> > >=20
> > > One of the things that should probably be discussed is=20
> whether the=20
> > > issues brought up in the attached e-mail (downgrading some of the=20
> > > MUSTSs to SHOULDs) should be addressed under the head of=20
> bug fixes.
> > >=20
> > > //cmh
> > >=20
> > > On Wed, 23 Sep 2009, David B Harrington wrote:
> > > > +1
> > > > dbh
> > > >=20
> > > > > -----Original Message-----
> > > > > From: mib-doctors-bounces@ietf.org=20
> > > > > [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Juergen=20
> > > > > Schoenwaelder
> > > > > Sent: Wednesday, September 23, 2009 5:22 AM
> > > > > To: Romascanu, Dan (Dan)
> > > > > Cc: C. M. Heard; MIB Doctors (E-mail); OPS Area (E-mail)
> > > > > Subject: Re: [MIB-DOCTORS] [OPS-AREA] FW: IESG Statement on=20
> > > > > Copyright
> > > > >=20
> > > > > On Wed, Sep 23, 2009 at 10:14:46AM +0200, Romascanu, Dan
> > > (Dan) wrote:
> > > > > > I have some good news to share. Randy Presuhn stepped
> > ahead and
> > > > > > accepted to be the editor of 4181bis. Thanks, Randy!
> > > > > >=20
> > > > > > I have two questions:=20
> > > > > >=20
> > > > > > 1. OPSAWG (which did not exist by the time 4181 was edited
> and
> > > > > > published) seems to me to be the natural home for
> > > 4181bis.  Does
> > > > > > anybody see any problem with this? If all agree we shall
> move=20
> > > > > > discussions to opsawg@ietf.org
> > > > > >=20
> > > > > > 2.  What should be the scope of 4181bis?=20
> > > > >=20
> > > > > Bug fixes and alignment to current IETF procedures and rules=20
> > > > > (although the last thing might be an endless
> > undertaking ;-). As
> > > > > little rewrite as possible if you ask me.
> > > > >=20
> > > > > /js
> > > > >=20
> > > > > --=20
> > > > > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > > > > Phone: +49 421 200 3587         Campus Ring 1, 28759=20
> > > Bremen, Germany
> > > > > Fax:   +49 421 200 3103        =20
> > <http://www.jacobs-university.de/>
> > > > > _______________________________________________
> > > > > MIB-DOCTORS mailing list
> > > > > MIB-DOCTORS@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/mib-doctors
> > > > >=20
> > > >=20
> > >=20
> >=20
>=20
>=20

From ietfdbh@comcast.net  Fri Sep 25 15:15:48 2009
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D90123A6925 for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 15:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.061
X-Spam-Level: 
X-Spam-Status: No, score=-2.061 tagged_above=-999 required=5 tests=[AWL=0.538,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dULSkT4593Rh for <ops-area@core3.amsl.com>; Fri, 25 Sep 2009 15:15:47 -0700 (PDT)
Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by core3.amsl.com (Postfix) with ESMTP id 2A9013A6882 for <ops-area@ietf.org>; Fri, 25 Sep 2009 15:15:47 -0700 (PDT)
Received: from OMTA03.westchester.pa.mail.comcast.net ([76.96.62.27]) by QMTA08.westchester.pa.mail.comcast.net with comcast id kzDA1c0040bG4ec58AGa1k; Fri, 25 Sep 2009 22:16:34 +0000
Received: from Harrington73653 ([24.147.240.98]) by OMTA03.westchester.pa.mail.comcast.net with comcast id lAGy1c009284sdk3PAGzU8; Fri, 25 Sep 2009 22:16:59 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <paduffy@cisco.com>, "'OPS Area \(E-mail\)'" <ops-area@ietf.org>
References: <4ABCE564.20101@cisco.com>
Date: Fri, 25 Sep 2009 18:16:57 -0400
Message-ID: <0c0801ca3e2d$e5bf7260$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4ABCE564.20101@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aco99xo+4wb6yTDwQUCcZShQ/i6fFAABhpuA
Subject: Re: [OPS-AREA] Present day reality of COPS-PR
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 22:15:48 -0000

Hi,

comments inline. I can help with the RFC. here's a start ... ;-)

> COPS-PR seems a solution that was looking for a problem.  

I disagree. The problem - how to standardize configuration - had been
talked about in the OPS area for years. COPS-PR was designed to solve
that problem. 

COPS-PR also addressed some related issues:
	1. how to do policy-based configuration
	2. how to do policy-server discovery
	3. how to separate policy distribution from policy
enforcement.
	4. how to do vendor-specific enforcement behind standardized
policies

> It never 
> really took off, for the following reasons....
> 
> - most, if not all, of what could be done with COPS-PR/PIBs 
> can be done
> with SNMP/MIBs. To do both is significant duplicated effort.

That is true, and that is what really killed it in IETF, where there
was a policy that all WGs were expected to "write a MIB" to make their
protoocls manageable. The IESG decided that they could not insist that
WGs duplicate effort by writing both a MIB and a PIB, but SNMP could
work with PIBs (and it would not have been easy to make that work), so
just "write a PIB" for both COPS-PR and SNMP usage was not a viable
option either.

Most of what can be done with PIBs could be done with MIBs, but
wildcarding and other policy specification cannot be done easily with
MIBs. SPPI added extensions to SMI to address those limitations. 

Much of what can be done with COPS-PR can be done with SNMP, but only
in an assembly language (or peek/poke) style, and only when the SNMP
agent actually supports both the SET command and secure
communications. To a large degree, since we are considering reality,
SNMP cannot do what COPS-PR was designed to do because SET is not
supported consistently, and SNMPv3 security is still not supported
consistently. COPS-PR added functionality that knew how to work with
the SPPI extensions (such as wildcard evaluation/expansion); SNMP does
not have that functionality. 

The SNMPCONF WG tried to do something similar to what COPS-PR did,
using scripting, and failed to catch anybody's interest. Operators
have made it clear that a standardized scripting language (ala
SNMPCONF) and or a standardized approach to support scripting in a
variety of languages (ala SCRIPT-MIB) is not of much interest. 

Architecturally, the IETF had an established framework (RFC1052) for
doing all network management using MIBs, and mostly using SNMP as the
protocol. COPS-PR was not consistent with the prevailing IETF
architecture.

Operationally, A policy-driven approach demands a single decision
point to ensure consistent policy. The COPS-PR global lock and
modification overwrites prevented operators from easily modifying the
policy-driven devices using other NM interfaces, such as SNMP and the
CLI. This was extremely unpopular with operators.

Operators made it very clear that the COPS-PR approach of using
standardized polices with vendor-specific enforcement mechanisms made
the enforcement non-deterministic, and allowing enforcement procedures
to be changed by vendors during software updates, was totally
unacceptable.

Politically, the SNMP community had gone through the SNMPv2 wars and
were not allowed to address anything other than security for a number
of years. The SNMP community was not allowed to address configuration
and policy-based management, but the COPS-PR WG did so in the
background (in a different IETF area, if I recall correctly). Some
COPS-PR advocates were very vocal that their intention was to replace
SNMP, totally. In response, many in the SNMP community fought hard to
ensure that COPS-PR did not get accepted.

> 
> - operators don't want binary PIBs, prefer ASCII based 
> CLI-type interfaces.

Involved operators made it clear they preferred an ASCII protocol so
they could see the commands on-the-wire, and an ASCII (or XML) data
modeling language rather than SMI, with its OID labeling and
two-dimension tables and no nesting.

I think they made it less clear that operators seem to prefer a
task-oriented interface, like a CLI, rather than a database-driven
approach like MIBs and PIBs. YANG will be an interesting test of
whether an XML-database approach can work to replace an ASCII
task-oriented CLI for configuration.

> 
> - key players (who?) withdrew from COPS-PR and PIB approach,
claiming
> there was no market.

Probably the most important were Cisco, Intel.
Probably the most important SDO that suppoprted COPS-PR and then
withdrew support (they would use it if it was available, but if it
wasn't available they'd find another solution) was 3GPP (or was it
3GPP2?)

> 
> - IETF has since gone down the path of Netconf and started 
> discussion to
> make COPS-PR historical.

Following long discussions with operators, in many venues, netconf was
specifically designed to match what the operators told us they wanted.

Venues included the IAB Workshop (RFC3535), the Dilbert mailing list,
the "world Tour" meetings at NANOG, RIPE, APRICOT, etc.

> 
> - there are few, if any, significant deployments.
> 
> AFAIK, there is minimal commercial or open source support.

I have not been able to research these claims, but I am told that
COPS-PR is actually in use in a number of places. Here are some of the
claims I have heard:

1) Juniper uses COPS-PR for their resource allocation, using both push
and pull methods, at least in the access and aggregation network. 
2) COPS-PR may be deployed in the Verizon FIOS (FTTH) access network
in the US.
3) COPS-PR may be deployed in the FT-Orange IPTV access network in UK.
4) Comcast uses a mix of COPS and COPS-PR in cable TV video QoS
control. 
5) COPS-PR is in DOCSIS 1.0 QoS, which may still be used in cable
deployments
6) Huawei uses both COPS and COPS-PR in their Quidway RM9000 Resource
Manager and their Multi-Service Control Gateway solution (public
documents show COPS, but I have not found explicit mention of COPS-PR;
I am checking further)
7) ITU-T has a proposal being considered that is based on COPS-PR

Searching the Web I found some additional information that might bear
further research (many items have no associated dates):
8) MultiService Forum has an Implementation Agreement for Dynamic
Policy Control Using COPS-PR (2005)
http://www.msforum.org/techinfo/approved/MSF-IA-COPS-PR.001-FINAL.pdf
9) IEEE Xplore has a paper that apparently was presented at ICT 2008
comparing the performance of COPS-PR and Netconf. The paper might
identify some equipment that has COPS-PR support.
10) A 2006 paper was published in the Proceedings of the IEEE
International Workshop on Policies for Distributed Systems and
Networks. The paper considers substituting Netconf and/or SOAP for
COPS-PR
11) I found discussion of COPS-PR in JUNOSe and the SAE on the web,
apparently for the SDX line (dated 2008). Was this from the Juniper
acquisition of netscreen and neoteris?
12) Sejong University apparently has developed a COPS-PR lite
http://ietcom.oxfordjournals.org/cgi/content/abstract/E90-B/11/3024
13) EION has an implementation
http://www.eion.com/protocols/protocols_traffic_cops.html
14) Cisco Catalyst has an implementation
15) Wireshark apparently implements it
16) ACSE Networks implements COPS-PR in their NeuTrans product line
17) ZNYX Networks implements COPS-PR in the ZX4900
18) libsmi implemented it
19) Operax AB implemented it
20) MIB Smithy implemented it
21) GridNet has implemented it in its products for managing utility
(power) grids
22) GE apparently embeds the GridNet implementation in its WiMax
SmartMeter and SmartGrid Router family of products
23) COPS-PR has been the subject of a tremendous number of academic
papers

David Harrington
dbharrington@comcast.net
ietfdbh@comcast.net
dharrington@huawei.com



From bertietf@bwijnen.net  Sun Sep 27 13:09:59 2009
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 600833A68A0; Sun, 27 Sep 2009 13:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.929
X-Spam-Level: *
X-Spam-Status: No, score=1.929 tagged_above=-999 required=5 tests=[AWL=-0.229,  BAYES_50=0.001, HELO_MISMATCH_NET=0.611, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ASJ0Ml6PItX; Sun, 27 Sep 2009 13:09:58 -0700 (PDT)
Received: from relay.versatel.net (relay55.tele2.vuurwerk.nl [62.250.3.55]) by core3.amsl.com (Postfix) with ESMTP id 492943A6850; Sun, 27 Sep 2009 13:09:58 -0700 (PDT)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1Ms05O-0000E2-9O; Sun, 27 Sep 2009 22:11:10 +0200
Message-ID: <60C0A9FD33634335B84450589BEFB172@BertLaptop>
From: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
To: "David Harrington" <ietfdbh@comcast.net>, <paduffy@cisco.com>, "'OPS Area \(E-mail\)'" <ops-area@ietf.org>
References: <4ABCE564.20101@cisco.com> <0c0801ca3e2d$e5bf7260$0600a8c0@china.huawei.com>
In-Reply-To: <0c0801ca3e2d$e5bf7260$0600a8c0@china.huawei.com>
Date: Sun, 27 Sep 2009 22:06:17 +0200
Organization: Consultant
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_1FC6_01CA3FBE.BC6D8270"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
Cc: opsawg@ietf.org
Subject: Re: [OPS-AREA] Present day reality of COPS-PR
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Sep 2009 20:09:59 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_1FC6_01CA3FBE.BC6D8270
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I am not really interested to get involved too deeply in this =
discussion,
certainly not at the level of detail that David does in his repsonse to =
Paul.

But I would like to comment on one statement from David Harrington,
namely:

  ----- Original Message -----=20
  From: David Harrington=20
  To: paduffy@cisco.com ; 'OPS Area (E-mail)'=20
  Sent: Saturday, September 26, 2009 12:16 AM
  Subject: Re: [OPS-AREA] Present day reality of COPS-PR


  Hi,

  comments inline. I can help with the RFC. here's a start ... ;-)

  > It never=20
  > really took off, for the following reasons....
  >=20
  > - most, if not all, of what could be done with COPS-PR/PIBs=20
  > can be done
  > with SNMP/MIBs. To do both is significant duplicated effort.

  That is true, and that is what really killed it in IETF, where there
  was a policy that all WGs were expected to "write a MIB" to make their
  protoocls manageable. The IESG decided that they could not insist that
  WGs duplicate effort by writing both a MIB and a PIB, but SNMP could
  work with PIBs (and it would not have been easy to make that work), so
  just "write a PIB" for both COPS-PR and SNMP usage was not a viable
  option either.

This gives the impression that the IESG decided this on her own. The =
IESG did collect
IETF input in various ways (BOF, info-gathering meetings, plenary =
discussion etc)
and based on the input concluded that there was (albeit very rough) =
consensus to not=20
support PIB Modules on the standards track.

Bert
------=_NextPart_000_1FC6_01CA3FBE.BC6D8270
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18813">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>I am not really interested to get involved too =
deeply in this=20
discussion,</FONT></DIV>
<DIV><FONT size=3D2>certainly not at the level of detail that David does =
in his=20
repsonse to Paul.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>But I would like to comment on one statement from =
David=20
Harrington,</FONT></DIV>
<DIV><FONT size=3D2>namely:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px" dir=3Dltr>
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Dietfdbh@comcast.net href=3D"">David Harrington</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dpaduffy@cisco.com=20
  href=3D"">paduffy@cisco.com</A> ; <A title=3Dops-area@ietf.org =
href=3D"">'OPS Area=20
  (E-mail)'</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Saturday, September 26, =
2009 12:16=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [OPS-AREA] Present =
day=20
  reality of COPS-PR</DIV>
  <DIV><FONT size=3D2></FONT><FONT size=3D2></FONT><FONT =
size=3D2></FONT><FONT=20
  size=3D2></FONT><BR></DIV>
  <DIV>Hi,<BR><BR>comments inline. I can help with the RFC. here's a =
start ...=20
  ;-)<BR><BR>&gt; It never <BR>&gt; really took off, for the following=20
  reasons....<BR>&gt; <BR>&gt; - most, if not all, of what could be done =
with=20
  COPS-PR/PIBs <BR>&gt; can be done<BR>&gt; with SNMP/MIBs. To do both =
is=20
  significant duplicated effort.<BR><BR>That is true, and that is what =
really=20
  killed it in IETF, where there<BR>was a policy that all WGs were =
expected to=20
  "write a MIB" to make their<BR>protoocls manageable. The IESG decided =
that=20
  they could not insist that<BR>WGs duplicate effort by writing both a =
MIB and a=20
  PIB, but SNMP could<BR>work with PIBs (and it would not have been easy =
to make=20
  that work), so<BR>just "write a PIB" for both COPS-PR and SNMP usage =
was not a=20
  viable<BR>option either.<BR></DIV></BLOCKQUOTE>
<DIV dir=3Dltr><FONT size=3D2>This gives the impression that the IESG =
decided this=20
on her own. The IESG did collect</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2>IETF input in various ways (BOF, =
info-gathering=20
meetings, plenary discussion etc)</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2>and based on the input concluded that =
there was=20
(albeit very rough) consensus to not </FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2>support PIB Modules on the standards=20
track.</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>Bert</FONT></DIV></BODY></HTML>

------=_NextPart_000_1FC6_01CA3FBE.BC6D8270--


From brian.e.carpenter@gmail.com  Sun Sep 27 13:52:25 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41A183A68AA; Sun, 27 Sep 2009 13:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3F0Aq0CZblvO; Sun, 27 Sep 2009 13:52:24 -0700 (PDT)
Received: from mail-pz0-f174.google.com (mail-pz0-f174.google.com [209.85.222.174]) by core3.amsl.com (Postfix) with ESMTP id 6C3913A685E; Sun, 27 Sep 2009 13:52:24 -0700 (PDT)
Received: by pzk4 with SMTP id 4so2104756pzk.32 for <multiple recipients>; Sun, 27 Sep 2009 13:53:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=IG4VpR1AvdQPVI2gkyiMq4tEouOGvJMq8p58nW5ISlE=; b=bqQXzBudlxHqucbmK859FM1U2Di3nZA6+nplxMokeQDRzzrYPFzBPTw2Osz+BwKBMq liqMOuYLjEpbqUz8DkQB6GoiQ9NDyygYQou810DFz6fLtZyKXXggMLJXyBS4ZvXgebsX skOWlC/q4H9qbVzMtcK2ApxSbh3B1c3GB2tMY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=EtzFWUgprQmKPavgwjViwGK4FYmFeTUq87EEFTJ537OdODOyoiTN20Q81lrn1wyzbM StPtCiCY9+JmoUek0U6rinkF55E4CT7HcdizhF3/zpgydOIi/1p5OQRjFwjyf+/u4Aqv q6SLsCojK3Vo/wp0Wgy+xI6czoBbiEQZJmvTI=
Received: by 10.114.9.16 with SMTP id 16mr4365432wai.114.1254084815551; Sun, 27 Sep 2009 13:53:35 -0700 (PDT)
Received: from ?10.1.1.4? (118-93-94-219.dsl.dyn.ihug.co.nz [118.93.94.219]) by mx.google.com with ESMTPS id 20sm1946791pzk.13.2009.09.27.13.53.32 (version=SSLv3 cipher=RC4-MD5); Sun, 27 Sep 2009 13:53:34 -0700 (PDT)
Message-ID: <4ABFD0C5.2080504@gmail.com>
Date: Mon, 28 Sep 2009 09:53:25 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <4ABCE564.20101@cisco.com>	<0c0801ca3e2d$e5bf7260$0600a8c0@china.huawei.com> <60C0A9FD33634335B84450589BEFB172@BertLaptop>
In-Reply-To: <60C0A9FD33634335B84450589BEFB172@BertLaptop>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: opsawg@ietf.org, "'OPS Area \(E-mail\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] Present day reality of COPS-PR
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Sep 2009 20:52:25 -0000

On 2009-09-28 09:06, Bert Wijnen (IETF) wrote:
> I am not really interested to get involved too deeply in this discussion,
> certainly not at the level of detail that David does in his repsonse to Paul.

Ditto, however:

...
> This gives the impression that the IESG decided this on her own. The IESG did collect
> IETF input in various ways (BOF, info-gathering meetings, plenary discussion etc)
> and based on the input concluded that there was (albeit very rough) consensus to not 
> support PIB Modules on the standards track.

I'd like to say, as a case in point, that the diffserv WG produced both a MIB
(because Bert said we had to ;-) and a PIB. The latter (RFC3317) took almost a
year after we'd finished all the core work of the WG, but I've really never heard
of it being used extensively and it was only somewhat supported even while under
active development (see below). What Bert says fits that picture.

    Brian

-------- Original Message --------
Subject: Updated summary Re: diffserv PIB: a question to the WG
Date: Wed, 12 Dec 2001 22:47:35 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
To: Diff Serv <diffserv@ietf.org>
CC: Bert Wijnen <bwijnen@lucent.com>, Randy Bush <randy@psg.com>
References: <3C14DCBD.EFBE5EDA@hursley.ibm.com>

Summary so far:

Plan to use the PIB: 1
May use and implement the PIB: 1
Implemented/now implementing the draft PIB: 3

Also, the PIB is currently a normative reference in 3GPP.

More replies welcome; anonymity guaranteed if requested.

   Brian

Brian E Carpenter wrote:
>
> Diffservers,
>
> As you know the Diffserv PIB recently passed WG last call, and will be forwarded
> to the IESG as soon as the draft is updated.
>
> Now I have a question, at the request of the Ops and Management Area Directors:
>
> Can anyone who plans to implement the diffserv PIB (or has already done so)
> please let us know? If you don't want to answer on the list, please send
> me a private response.
>
> Thanks
>    Brian Carpenter
>    diffserv co-chair

From ietfdbh@comcast.net  Sun Sep 27 15:42:32 2009
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2F323A6944 for <ops-area@core3.amsl.com>; Sun, 27 Sep 2009 15:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.134
X-Spam-Level: 
X-Spam-Status: No, score=-1.134 tagged_above=-999 required=5 tests=[AWL=-0.395, BAYES_20=-0.74, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bYozoiN2xDya for <ops-area@core3.amsl.com>; Sun, 27 Sep 2009 15:42:31 -0700 (PDT)
Received: from QMTA06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by core3.amsl.com (Postfix) with ESMTP id 561963A693E for <ops-area@ietf.org>; Sun, 27 Sep 2009 15:42:30 -0700 (PDT)
Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA06.westchester.pa.mail.comcast.net with comcast id lyBp1c0040QuhwU56yjGEH; Sun, 27 Sep 2009 22:43:16 +0000
Received: from Harrington73653 ([24.147.240.98]) by OMTA02.westchester.pa.mail.comcast.net with comcast id lyjn1c00F284sdk3NyjnQG; Sun, 27 Sep 2009 22:43:48 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Bert Wijnen \(IETF\)'" <bertietf@bwijnen.net>, <paduffy@cisco.com>, "'OPS Area \(E-mail\)'" <ops-area@ietf.org>
References: <4ABCE564.20101@cisco.com> <0c0801ca3e2d$e5bf7260$0600a8c0@china.huawei.com> <60C0A9FD33634335B84450589BEFB172@BertLaptop>
Date: Sun, 27 Sep 2009 18:43:46 -0400
Message-ID: <0c6501ca3fc3$f9862090$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0C66_01CA3FA2.72748090"
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <60C0A9FD33634335B84450589BEFB172@BertLaptop>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aco/rqpy26CqxdZTRRqgkXHVk3VPiwAFOhOQ
Cc: opsawg@ietf.org
Subject: Re: [OPS-AREA] Present day reality of COPS-PR
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Sep 2009 22:42:32 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0C66_01CA3FA2.72748090
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,
 
I did not mean to imply that the IESG did this without following the
normal IETF review process.
I agree it was IETF rough consensus.
 
and I have a typo in that paragraph. 
s/SNMP could work with PIBs/SNMP could not work with PIBs/
 
dbh


  _____  

From: Bert Wijnen (IETF) [mailto:bertietf@bwijnen.net] 
Sent: Sunday, September 27, 2009 4:06 PM
To: David Harrington; paduffy@cisco.com; 'OPS Area (E-mail)'
Cc: opsawg@ietf.org
Subject: Re: [OPS-AREA] Present day reality of COPS-PR


I am not really interested to get involved too deeply in this
discussion,
certainly not at the level of detail that David does in his repsonse
to Paul.
 
But I would like to comment on one statement from David Harrington,
namely:
 

----- Original Message ----- 
From: David Harrington 
To: paduffy@cisco.com ; 'OPS Area (E-mail)' 
Sent: Saturday, September 26, 2009 12:16 AM
Subject: Re: [OPS-AREA] Present day reality of COPS-PR


Hi,

comments inline. I can help with the RFC. here's a start ... ;-)

> It never 
> really took off, for the following reasons....
> 
> - most, if not all, of what could be done with COPS-PR/PIBs 
> can be done
> with SNMP/MIBs. To do both is significant duplicated effort.

That is true, and that is what really killed it in IETF, where there
was a policy that all WGs were expected to "write a MIB" to make their
protoocls manageable. The IESG decided that they could not insist that
WGs duplicate effort by writing both a MIB and a PIB, but SNMP could
work with PIBs (and it would not have been easy to make that work), so
just "write a PIB" for both COPS-PR and SNMP usage was not a viable
option either.


This gives the impression that the IESG decided this on her own. The
IESG did collect
IETF input in various ways (BOF, info-gathering meetings, plenary
discussion etc)
and based on the input concluded that there was (albeit very rough)
consensus to not 
support PIB Modules on the standards track.
 
Bert


------=_NextPart_000_0C66_01CA3FA2.72748090
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D684544022-27092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D684544022-27092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D684544022-27092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I did not mean to imply that the IESG did this =
without=20
following the normal IETF review process.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D684544022-27092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I agree it was IETF rough =
consensus.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D684544022-27092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D684544022-27092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>and I have a typo in that paragraph. =
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D684544022-27092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>s/SNMP could work with PIBs/SNMP could not work =
with=20
PIBs/</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D684544022-27092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D684544022-27092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>dbh</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Bert Wijnen (IETF)=20
  [mailto:bertietf@bwijnen.net] <BR><B>Sent:</B> Sunday, September 27, =
2009 4:06=20
  PM<BR><B>To:</B> David Harrington; paduffy@cisco.com; 'OPS Area=20
  (E-mail)'<BR><B>Cc:</B> opsawg@ietf.org<BR><B>Subject:</B> Re: =
[OPS-AREA]=20
  Present day reality of COPS-PR<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT size=3D2>I am not really interested to get involved too =
deeply in=20
  this discussion,</FONT></DIV>
  <DIV><FONT size=3D2>certainly not at the level of detail that David =
does in his=20
  repsonse to Paul.</FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2>But I would like to comment on one statement from =
David=20
  Harrington,</FONT></DIV>
  <DIV><FONT size=3D2>namely:</FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
    <A title=3Dietfdbh@comcast.net href=3D"">David Harrington</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dpaduffy@cisco.com=20
    href=3D"">paduffy@cisco.com</A> ; <A title=3Dops-area@ietf.org =
href=3D"">'OPS Area=20
    (E-mail)'</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Saturday, September 26, =
2009=20
    12:16 AM</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [OPS-AREA] =
Present day=20
    reality of COPS-PR</DIV>
    <DIV><FONT size=3D2></FONT><FONT size=3D2></FONT><FONT =
size=3D2></FONT><FONT=20
    size=3D2></FONT><BR></DIV>
    <DIV>Hi,<BR><BR>comments inline. I can help with the RFC. here's a =
start ...=20
    ;-)<BR><BR>&gt; It never <BR>&gt; really took off, for the following =

    reasons....<BR>&gt; <BR>&gt; - most, if not all, of what could be =
done with=20
    COPS-PR/PIBs <BR>&gt; can be done<BR>&gt; with SNMP/MIBs. To do both =
is=20
    significant duplicated effort.<BR><BR>That is true, and that is what =
really=20
    killed it in IETF, where there<BR>was a policy that all WGs were =
expected to=20
    "write a MIB" to make their<BR>protoocls manageable. The IESG =
decided that=20
    they could not insist that<BR>WGs duplicate effort by writing both a =
MIB and=20
    a PIB, but SNMP could<BR>work with PIBs (and it would not have been =
easy to=20
    make that work), so<BR>just "write a PIB" for both COPS-PR and SNMP =
usage=20
    was not a viable<BR>option either.<BR></DIV></BLOCKQUOTE>
  <DIV dir=3Dltr><FONT size=3D2>This gives the impression that the IESG =
decided this=20
  on her own. The IESG did collect</FONT></DIV>
  <DIV dir=3Dltr><FONT size=3D2>IETF input in various ways (BOF, =
info-gathering=20
  meetings, plenary discussion etc)</FONT></DIV>
  <DIV dir=3Dltr><FONT size=3D2>and based on the input concluded that =
there was=20
  (albeit very rough) consensus to not </FONT></DIV>
  <DIV dir=3Dltr><FONT size=3D2>support PIB Modules on the standards=20
  track.</FONT></DIV>
  <DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT =
size=3D2>Bert</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0C66_01CA3FA2.72748090--


From j.schoenwaelder@jacobs-university.de  Tue Sep 29 00:21:48 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C182028C121 for <ops-area@core3.amsl.com>; Tue, 29 Sep 2009 00:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.367
X-Spam-Level: 
X-Spam-Status: No, score=-1.367 tagged_above=-999 required=5 tests=[AWL=-0.607, BAYES_05=-1.11, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VwrOJahm1cSj for <ops-area@core3.amsl.com>; Tue, 29 Sep 2009 00:21:48 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 0CDA83A6A33 for <ops-area@ietf.org>; Tue, 29 Sep 2009 00:21:48 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id C1873C0008; Tue, 29 Sep 2009 09:23:07 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id FkV261ASYXky; Tue, 29 Sep 2009 09:23:07 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id D5CEDC0007; Tue, 29 Sep 2009 09:23:06 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id AB044D06AED; Tue, 29 Sep 2009 09:23:05 +0200 (CEST)
Date: Tue, 29 Sep 2009 09:23:05 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-ID: <20090929072305.GB24719@elstar.local>
References: <4ABCE564.20101@cisco.com> <4ABCE7C6.5050807@juniper.net> <EDC652A26FB23C4EB6384A4584434A0401A84CF2@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401A84CF2@307622ANEX5.global.avaya.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "OPS Area \(E-mail\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] Present day reality of COPS-PR
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2009 07:21:48 -0000

On Fri, Sep 25, 2009 at 06:00:24PM +0200, Romascanu, Dan (Dan) wrote:

> Let us move this discussion to OPSAWG where a proposal was made in
> Stockholm on this respect. We need a volunteer to write the RFC. 

I have posted <draft-schoenw-opsawg-copspr-historic-00.txt> and all
followup discussion should take place on the OPSAWG mailing, as
suggested by Dan.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
