
From dromasca@avaya.com  Wed Apr  1 07:44:07 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC98628C22B; Wed,  1 Apr 2009 07:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 JbOjeq2+zpfV; Wed,  1 Apr 2009 07:44:07 -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 452ED3A6B62; Wed,  1 Apr 2009 07:42:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.39,306,1235970000"; d="scan'208";a="166617773"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 01 Apr 2009 10:43:46 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 01 Apr 2009 10:43:45 -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, 1 Apr 2009 16:43:34 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04015502F5@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: draft-ietf-isms-tmsm (Transport Subsystem for the Simple Network Management Protocol (SNMP)) to Proposed Standard
Thread-Index: Acmy1/sOOLPH5mroSAKG4wA0jg1bewAACTyg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
Subject: [MIB-DOCTORS] FW: Last Call: draft-ietf-isms-tmsm (Transport Subsystem for the Simple Network Management Protocol (SNMP)) to Proposed Standard
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2009 14:44:07 -0000

=20

-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG
Sent: Wednesday, April 01, 2009 5:40 PM
To: IETF-Announce
Cc: isms@ietf.org
Subject: Last Call: draft-ietf-isms-tmsm (Transport Subsystem for the
Simple Network Management Protocol (SNMP)) to Proposed Standard=20

The IESG has received a request from the Integrated Security Model for
SNMP WG (isms) to consider the following document:

- 'Transport Subsystem for the Simple Network Management Protocol (SNMP)
'
   <draft-ietf-isms-tmsm-16.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-04-15. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-isms-tmsm-16.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag=
=3D
13828&rfc_flag=3D0

The following IPR Declarations may be related to this I-D:



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

From dromasca@avaya.com  Wed Apr  1 07:51:39 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2E993A68BC; Wed,  1 Apr 2009 07:51:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 3EHHL6GD-iJM; Wed,  1 Apr 2009 07:51:38 -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 1B4633A67DF; Wed,  1 Apr 2009 07:51:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.39,306,1235970000"; d="scan'208";a="141972335"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 Apr 2009 10:52:36 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 01 Apr 2009 10:52:35 -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, 1 Apr 2009 16:52:18 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401550307@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isms] Last Call: draft-ietf-isms-transport-security-model (Transport Security Model for SNMP) to Proposed Standard
Thread-Index: Acmy2A+xmZ7Ls6AwRDeWGZFrxJdboQAAVvEw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <ops-dir@ietf.org>
Subject: [MIB-DOCTORS] FW: [Isms] Last Call: draft-ietf-isms-transport-security-model (Transport Security Model for SNMP) to Proposed Standard
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2009 14:51:39 -0000

=20

-----Original Message-----
From: isms-bounces@ietf.org [mailto:isms-bounces@ietf.org] On Behalf Of
The IESG
Sent: Wednesday, April 01, 2009 5:41 PM
To: IETF-Announce
Cc: isms@ietf.org
Subject: [Isms] Last Call: draft-ietf-isms-transport-security-model
(Transport Security Model for SNMP) to Proposed Standard

The IESG has received a request from the Integrated Security Model for
SNMP WG (isms) to consider the following document:

- 'Transport Security Model for SNMP '
   <draft-ietf-isms-transport-security-model-12.txt> as a Proposed
Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-04-15. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-isms-transport-security-m
odel-12.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag=
=3D
15419&rfc_flag=3D0

The following IPR Declarations may be related to this I-D:



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

From dromasca@avaya.com  Fri Apr  3 02:04:22 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD94A3A6968; Fri,  3 Apr 2009 02:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 eGwB7aZWSH85; Fri,  3 Apr 2009 02:04:21 -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 9CAC23A69DB; Fri,  3 Apr 2009 02:04:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.39,318,1235970000"; d="scan'208";a="166838090"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 03 Apr 2009 05:05:23 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 03 Apr 2009 05:05:22 -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, 3 Apr 2009 11:05:20 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040158B055@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for April 9, 2009 Telechat 
Thread-Index: Acmz3y3SSoSLlC+ORC+4RbrHrPD4QwAW3lGw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <ops-dir@ietf.org>, <dns-dir@ietf.org>
Cc: Ronald Bonica <rbonica@juniper.net>
Subject: [MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for April 9, 2009 Telechat
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2009 09:04:22 -0000

Please find below the preliminary agenda of the 4/9 telechat. Please
send your comments and concerns until Wednesday 4/8 the latest. Also
note that several Working Groups are on the agenda of the telechat for
discussions and approval.=20

Please copy Ron on your mails. I will be missing this telechat because
of a short vacation (4/7 to 4/12).=20

Dan




2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-nsis-ntlp-19.txt
    GIST: General Internet Signalling Transport (Proposed Standard) - 1
of
9=20
    Note: Please check your comment field so that it doesn't contain old
text!=20
    RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN please

    indicate in the comment field that you have performed this
re-evaluation.=20
    Pleas also include some motivation behind your decision.=20
    Token: Magnus Westerlund
  o draft-ietf-behave-turn-13.txt
    Traversal Using Relays around NAT (TURN): Relay Extensions to
Session

    Traversal Utilities for NAT (STUN) (Proposed Standard) - 2 of 9=20
    Token: Magnus Westerlund
  o draft-ietf-mpls-ldp-capabilities-03.txt
    LDP Capabilities (Proposed Standard) - 3 of 9=20
    Token: Ross Callon
  o draft-ietf-kitten-gssapi-channel-bindings-06.txt
    Clarifications and Extensions to the GSS-API for the Use of Channel=20
    Bindings (Proposed Standard) - 4 of 9=20
    Note: proto writeup received...=20
    Token: Tim Polk
  o draft-ietf-softwire-security-requirements-07.txt
    Softwire Security Analysis and Requirements (Proposed Standard) - 5
of
9=20
    Token: ?
  o draft-ietf-ntp-ntpv4-proto-11.txt
    Network Time Protocol Version 4 Protocol And Algorithms
Specification

    (Proposed Standard) - 6 of 9=20
    Token: ?
  o draft-ietf-ntp-ntpv4-mib-05.txt
    Definitions of Managed Objects for Network Time Protocol Version 4
(NTPv4)=20
    (Proposed Standard) - 7 of 9=20
    Token: ?
  o draft-ietf-ccamp-path-key-ero-04.txt
    RSVP Extensions for Path Key Support (Proposed Standard) - 8 of 9=20
    Token: Ross Callon
  o draft-ietf-pce-global-concurrent-optimization-10.txt
    Path Computation Element Communication Protocol (PCEP) Requirements
and=20
    Protocol Extensions In Support of Global Concurrent Optimization
(Proposed=20
    Standard) - 9 of 9=20
    Token: Ross Callon

2.1.2 Returning Item
  o draft-ietf-ippm-duplicate-07.txt
    A One-Way Packet Duplication Metric (Proposed Standard) - 1 of 1=20
    Token: Lars Eggert


2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
NONE

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.1.1 New Item
  o draft-ietf-lemonade-streaming-10.txt
    Streaming Internet Messaging Attachments (Informational) - 1 of 1=20
    Note: Glenn Parsons is document shepherd=20
    Token: Alexey Melnikov

3.1.2 Returning Item
NONE

3.2 Individual Submissions Via AD
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.2.1 New Item
NONE
3.2.2 Returning Item
NONE
3.3 Independent Submissions Via RFC Editor
	The IESG will use RFC 3932 responses: 1) The IESG has not
	found any conflict between this document and IETF work; 2) The
	IESG thinks that this work is related to IETF work done in WG
	<X>, but this does not prevent publishing; 3) The IESG thinks
	that publication is harmful to work in WG <X> and recommends
	not publishing at this time; 4) The IESG thinks that this
	document violates the IETF procedures for <X> and should
	therefore not be published without IETF review and IESG
	approval; 5) The IESG thinks that this document extends an
	IETF protocol in a way that requires IETF review and should
	therefore not be published without IETF review and IESG
approval.

	The document shepherd must propose one of these responses in
	the Data Tracker note and supply complete text in the IESG
	Note portion of the write-up. The Area Director ballot positions
	indicate consensus with the response proposed by the
	document shepherd.

	Other matters may be recorded in comments, and the comments will
	be passed on to the RFC Editor as community review of the
document.


3.3.1 New Item
  o draft-despres-6rd-02.txt
    IPv6 Rapid Deployment on IPv4 infrastructures (6rd) (Informational)
-
1 of=20
    1=20
    Token: Jari Arkko

3.3.2 Returning Item
NONE

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
  o Multiple Interfaces (mif) - 1 of 1
    Token: Jari Arkko
4.1.2 Proposed for Approval
  o Locator/ID Separation Protocol (lisp) - 1 of 3
    Token: Jari Arkko
  o Session Initiation Protocol Core (sipcore) - 2 of 3
    Token: Cullen Jennings
  o Dispatch (dispatch) - 3 of 3
    Token: Cullen Jennings

From housley@vigilsec.com  Sun Apr  5 13:07:37 2009
Return-Path: <housley@vigilsec.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1490D3A6B5D; Sun,  5 Apr 2009 13:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.943
X-Spam-Level: 
X-Spam-Status: No, score=-100.943 tagged_above=-999 required=5 tests=[AWL=-1.291, BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, USER_IN_WHITELIST=-100]
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 izC-Ju1G9Ioi; Sun,  5 Apr 2009 13:07:31 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 9A1913A6B34; Sun,  5 Apr 2009 13:07:23 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id AA5769A4721; Sun,  5 Apr 2009 16:08:45 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id XoTPUPmehi8b; Sun,  5 Apr 2009 16:08:22 -0400 (EDT)
Received: from THINKPADR52.vigilsec.com (pool-71-191-197-15.washdc.fios.verizon.net [71.191.197.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id BB7AB9A477D; Sun,  5 Apr 2009 16:08:39 -0400 (EDT)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 05 Apr 2009 16:08:19 -0400
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,<iesg@ietf.org>
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040153187D@307622ANEX5.globa l.avaya.com>
References: <20090325055429.63BEC9A471B@odin.smetech.net> <EDC652A26FB23C4EB6384A4584434A040153187D@307622ANEX5.global.avaya.com>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Message-Id: <20090405200839.BB7AB9A477D@odin.smetech.net>
Cc: trustees@ietf.org, mib-doctors@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: [MIB-DOCTORS] Copyright notice in "code"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2009 20:07:37 -0000

<html>
<body>
Dan:<br><br>
I do not see PIB modules as code in the Trustee list.<br>
<a href="http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt" eudora="autourl">
http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt</a><br><br>
Russ<br><br>
At 09:09 AM 3/25/2009, Romascanu, Dan (Dan) wrote:<br><br>
<blockquote type=cite class=cite cite=""><font size=2>Russ,<br><br>
I thought that we already knew this from the previous conversations. The
clarification that I thought that we were expecting from Jorge was
whether we are allowed to replace 'the code' in the first paragraph by
'the MIB module' for MIB modules and 'the PIB module' for PIB modules. Or
we must use exactly the copyright text below?<br><br>
Dan<br><br>
<br><br>
-----Original Message-----<br>
From: iesg-bounces@ietf.org on behalf of Russ Housley<br>
Sent: Wed 3/25/2009 7:54 AM<br>
To: iesg@ietf.org<br>
Cc: trustees@ietf.org; rfc-editor@rfc-editor.org<br>
Subject: Copyright notice in &quot;code&quot;<br><br>
I spoke with Jorge today, and he confirmed that the entire legend below
needs to appear in comments in any code, such as MIB, PIB, ASN.1, XML
Schema, and so on.&nbsp; This is needed to comply with the BSD open
source license.<br><br>
Russ<br><br>
<br><br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Copyright (c) &lt;insert year&gt; IETF Trust and the persons identified
as<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
authors of the code. All rights reserved.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Redistribution and use in source and binary forms, with or without<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
modification, are permitted provided that the following conditions<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; are
met:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
Redistributions of source code must retain the above copyright<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
notice, this list of conditions and the following disclaimer.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
Redistributions in binary form must reproduce the above copyright<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
notice, this list of conditions and the following disclaimer in the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
documentation and/or other materials provided with the distribution.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
Neither the name of Internet Society, IETF or IETF Trust, nor the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
names of specific contributors, may be used to endorse or promote<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
products derived from this software without specific prior written<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
permission.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; THIS
SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;AS IS&quot; AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OWNER
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DATA,
OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.<br><br>
</font></blockquote></body>
</html>


From dromasca@avaya.com  Mon Apr  6 09:05:33 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51F473A698C; Mon,  6 Apr 2009 09:05:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.579
X-Spam-Level: 
X-Spam-Status: No, score=-1.579 tagged_above=-999 required=5 tests=[AWL=-0.840, 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 PHJ65zpYYpJJ; Mon,  6 Apr 2009 09:05:26 -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 2F8023A6CC6; Mon,  6 Apr 2009 09:05:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.39,331,1235970000";  d="scan'208,217";a="167084252"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 06 Apr 2009 12:06:31 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 06 Apr 2009 12:06:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9B6D1.A5EDD606"
Date: Mon, 6 Apr 2009 18:06:29 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040158B4D2@307622ANEX5.global.avaya.com>
In-Reply-To: <20090405200839.BB7AB9A477D@odin.smetech.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Copyright notice in "code"
Thread-Index: Acm2KkpanUantJcaRxeJk5Fl7SuCvQApyEsQ
References: <20090325055429.63BEC9A471B@odin.smetech.net> <EDC652A26FB23C4EB6384A4584434A040153187D@307622ANEX5.global.avaya.com> <20090405200839.BB7AB9A477D@odin.smetech.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Russ Housley" <housley@vigilsec.com>, <iesg@ietf.org>
Cc: trustees@ietf.org, mib-doctors@ietf.org, David Partain <david.partain@ericsson.com>, rfc-editor@rfc-editor.org
Subject: Re: [MIB-DOCTORS] Copyright notice in "code"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 16:05:33 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9B6D1.A5EDD606
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Neither are YANG modules which result from the NETMOD WG.=20
=20
What is the process of adding new items to this list?=20
=20
Dan
=20


________________________________

	From: Russ Housley [mailto:housley@vigilsec.com]=20
	Sent: Sunday, April 05, 2009 11:08 PM
	To: Romascanu, Dan (Dan); iesg@ietf.org
	Cc: trustees@ietf.org; rfc-editor@rfc-editor.org;
mib-doctors@ietf.org
	Subject: RE: Copyright notice in "code"
=09
=09
	Dan:
=09
	I do not see PIB modules as code in the Trustee list.
	http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt
=09
	Russ
=09
	At 09:09 AM 3/25/2009, Romascanu, Dan (Dan) wrote:
=09
=09

		Russ,
	=09
		I thought that we already knew this from the previous
conversations. The clarification that I thought that we were expecting
from Jorge was whether we are allowed to replace 'the code' in the first
paragraph by 'the MIB module' for MIB modules and 'the PIB module' for
PIB modules. Or we must use exactly the copyright text below?
	=09
		Dan
	=09
	=09
	=09
		-----Original Message-----
		From: iesg-bounces@ietf.org on behalf of Russ Housley
		Sent: Wed 3/25/2009 7:54 AM
		To: iesg@ietf.org
		Cc: trustees@ietf.org; rfc-editor@rfc-editor.org
		Subject: Copyright notice in "code"
	=09
		I spoke with Jorge today, and he confirmed that the
entire legend below needs to appear in comments in any code, such as
MIB, PIB, ASN.1, XML Schema, and so on.  This is needed to comply with
the BSD open source license.
	=09
		Russ
	=09
	=09
	=09
	=09
		            Copyright (c) <insert year> IETF Trust and
the persons identified as
		            authors of the code. All rights reserved.
		      =20
		            Redistribution and use in source and binary
forms, with or without
		            modification, are permitted provided that
the following conditions
		            are met:
		      =20
		            - Redistributions of source code must retain
the above copyright
		              notice, this list of conditions and the
following disclaimer.
		      =20
		            - Redistributions in binary form must
reproduce the above copyright
		              notice, this list of conditions and the
following disclaimer in the
		              documentation and/or other materials
provided with the distribution.
		      =20
		            - Neither the name of Internet Society, IETF
or IETF Trust, nor the
		              names of specific contributors, may be
used to endorse or promote
		              products derived from this software
without specific prior written
		              permission.
		      =20
		            THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT
HOLDERS AND CONTRIBUTORS
		            "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT
		            LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR
		            A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE COPYRIGHT
		            OWNER OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL,
		            SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT
		            LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE,
		            DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY
		            THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT
		            (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE
		            OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
	=09
	=09


------_=_NextPart_001_01C9B6D1.A5EDD606
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.2900.3492" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D553520416-06042009><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>Neither are&nbsp;YANG modules which result from the =
NETMOD=20
WG. </EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D553520416-06042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D553520416-06042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>What is the process of adding new items to this list?=20
</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D553520416-06042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D553520416-06042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D553520416-06042009></SPAN>&nbsp;</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> Russ Housley=20
  [mailto:housley@vigilsec.com] <BR><B>Sent:</B> Sunday, April 05, 2009 =
11:08=20
  PM<BR><B>To:</B> Romascanu, Dan (Dan); iesg@ietf.org<BR><B>Cc:</B>=20
  trustees@ietf.org; rfc-editor@rfc-editor.org;=20
  mib-doctors@ietf.org<BR><B>Subject:</B> RE: Copyright notice in=20
  "code"<BR></FONT><BR></DIV>
  <DIV></DIV>Dan:<BR><BR>I do not see PIB modules as code in the Trustee =

  list.<BR><A=20
  =
href=3D"http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt"=20
  =
eudora=3D"autourl">http://trustee.ietf.org/docs/Code-Components-List-11-1=
0-08.txt</A><BR><BR>Russ<BR><BR>At=20
  09:09 AM 3/25/2009, Romascanu, Dan (Dan) wrote:<BR><BR>
  <BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite"><FONT =
size=3D2>Russ,<BR><BR>I=20
    thought that we already knew this from the previous conversations. =
The=20
    clarification that I thought that we were expecting from Jorge was =
whether=20
    we are allowed to replace 'the code' in the first paragraph by 'the =
MIB=20
    module' for MIB modules and 'the PIB module' for PIB modules. Or we =
must use=20
    exactly the copyright text =
below?<BR><BR>Dan<BR><BR><BR><BR>-----Original=20
    Message-----<BR>From: iesg-bounces@ietf.org on behalf of Russ=20
    Housley<BR>Sent: Wed 3/25/2009 7:54 AM<BR>To: iesg@ietf.org<BR>Cc:=20
    trustees@ietf.org; rfc-editor@rfc-editor.org<BR>Subject: Copyright =
notice in=20
    "code"<BR><BR>I spoke with Jorge today, and he confirmed that the =
entire=20
    legend below needs to appear in comments in any code, such as MIB, =
PIB,=20
    ASN.1, XML Schema, and so on.&nbsp; This is needed to comply with =
the BSD=20
    open source=20
    =
license.<BR><BR>Russ<BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Copyright (c) &lt;insert year&gt; IETF Trust and the persons =
identified=20
    =
as<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

    authors of the code. All rights=20
    reserved.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Redistribution and use in source and binary forms, with or=20
    =
without<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    modification, are permitted provided that the following=20
    =
conditions<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
    are met:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =

    Redistributions of source code must retain the above=20
    =
copyright<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;=20
    notice, this list of conditions and the following=20
    disclaimer.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =

    Redistributions in binary form must reproduce the above=20
    =
copyright<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;=20
    notice, this list of conditions and the following disclaimer in=20
    =
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;=20
    documentation and/or other materials provided with the=20
    distribution.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =

    Neither the name of Internet Society, IETF or IETF Trust, nor=20
    =
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;=20
    names of specific contributors, may be used to endorse or=20
    =
promote<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
    products derived from this software without specific prior=20
    =
written<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
    permission.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
THIS=20
    SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND=20
    =
CONTRIBUTORS<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT=20
    =
NOT<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS=20
    =
FOR<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 A=20
    PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE=20
    =
COPYRIGHT<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,=20
    =
INCIDENTAL,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT=20
    =
NOT<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF=20
    =
USE,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON=20
    =
ANY<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR=20
    =
TORT<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE=20
    =
USE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 OF=20
    THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH=20
    DAMAGE.<BR><BR></FONT></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C9B6D1.A5EDD606--

From dromasca@avaya.com  Mon Apr  6 09:27:52 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C29D53A6C18; Mon,  6 Apr 2009 09:27:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093,  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 zXqov9YZrtmp; Mon,  6 Apr 2009 09:27:52 -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 D63CD3A6BEB; Mon,  6 Apr 2009 09:27:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.39,331,1235970000"; d="scan'208";a="167087169"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 06 Apr 2009 12:28:57 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 06 Apr 2009 12:28:57 -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: Mon, 6 Apr 2009 18:28:41 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040158B4E0@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: draft-ietf-mpls-p2mp-te-mib (Point-to-Multipoint Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB) module) to Proposed Standard 
Thread-Index: Acm0ajhJPtSbLvv5S9+1cyx5azOFdQCaoJ2A
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <mib-doctors@ietf.org>, <ops-dir@ietf.org>
Subject: [MIB-DOCTORS] FW: Last Call: draft-ietf-mpls-p2mp-te-mib (Point-to-Multipoint Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB) module) to Proposed Standard
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 16:27:52 -0000

=20

-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG
Sent: Friday, April 03, 2009 5:39 PM
To: IETF-Announce
Cc: mpls@lists.ietf.org
Subject: Last Call: draft-ietf-mpls-p2mp-te-mib (Point-to-Multipoint
Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management
Information Base (MIB) module) to Proposed Standard=20

The IESG has received a request from the Multiprotocol Label Switching
WG (mpls) to consider the following document:

- 'Point-to-Multipoint Multiprotocol Label Switching (MPLS) Traffic=20
   Engineering (TE) Management Information Base (MIB) module '
   <draft-ietf-mpls-p2mp-te-mib-08.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-04-17. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-te-mib-08.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag=
=3D
15176&rfc_flag=3D0

The following IPR Declarations may be related to this I-D:



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

From housley@vigilsec.com  Mon Apr  6 11:17:15 2009
Return-Path: <housley@vigilsec.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9006428C24E; Mon,  6 Apr 2009 11:17:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.674
X-Spam-Level: 
X-Spam-Status: No, score=-101.674 tagged_above=-999 required=5 tests=[AWL=-0.533, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, USER_IN_WHITELIST=-100]
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 O8Qb6GQBNdX7; Mon,  6 Apr 2009 11:17:14 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 8BA8728C18A; Mon,  6 Apr 2009 11:17:14 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id B9E329A4749; Mon,  6 Apr 2009 14:18:22 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 3YwBUzBDYIHU; Mon,  6 Apr 2009 14:18:16 -0400 (EDT)
Received: from THINKPADR52.vigilsec.com (pool-71-191-197-15.washdc.fios.verizon.net [71.191.197.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 449929A477A; Mon,  6 Apr 2009 14:18:18 -0400 (EDT)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 06 Apr 2009 14:08:04 -0400
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,<iesg@ietf.org>
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040158B4D2@307622ANEX5.globa l.avaya.com>
References: <20090325055429.63BEC9A471B@odin.smetech.net> <EDC652A26FB23C4EB6384A4584434A040153187D@307622ANEX5.global.avaya.com> <20090405200839.BB7AB9A477D@odin.smetech.net> <EDC652A26FB23C4EB6384A4584434A040158B4D2@307622ANEX5.global.avaya.com>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Message-Id: <20090406181818.449929A477A@odin.smetech.net>
Cc: trustees@ietf.org, mib-doctors@ietf.org, David Partain <david.partain@ericsson.com>, rfc-editor@rfc-editor.org
Subject: Re: [MIB-DOCTORS] Copyright notice in "code"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 18:17:15 -0000

<html>
<body>
Send email to trustees@ietf.org and ask.<br><br>
Russ<br><br>
<br>
At 12:06 PM 4/6/2009, Romascanu, Dan (Dan) wrote:<br>
<blockquote type=cite class=cite cite=""><font size=2 color="#0000FF"><b>
<i>Neither are YANG modules which result from the NETMOD WG. <br>
</i></b></font>&nbsp;<br>
<font size=2 color="#0000FF"><b><i>What is the process of adding new
items to this list? <br>
</i></b></font>&nbsp;<br>
<font size=2 color="#0000FF"><b><i>Dan<br>
</i></b></font>&nbsp;<br><br>

<dl><hr>

<dd><font face="Tahoma" size=2>From:</b> Russ Housley
[<a href="mailto:housley@vigilsec.com" eudora="autourl">
mailto:housley@vigilsec.com</a>] <br>

<dd>Sent:</b> Sunday, April 05, 2009 11:08 PM<br>

<dd>To:</b> Romascanu, Dan (Dan); iesg@ietf.org<br>

<dd>Cc:</b> trustees@ietf.org; rfc-editor@rfc-editor.org;
mib-doctors@ietf.org<br>

<dd>Subject:</b> RE: Copyright notice in &quot;code&quot;<br>
</font><br>

<dd>Dan:<br><br>

<dd>I do not see PIB modules as code in the Trustee list.<br>

<dd>
<a href="http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt" eudora="autourl">
http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt</a><br><br>

<dd>Russ<br><br>

<dd>At 09:09 AM 3/25/2009, Romascanu, Dan (Dan) wrote:<br><br>
<blockquote type=cite class=cite cite="">
<dd><font size=2>Russ,<br><br>

<dd>I thought that we already knew this from the previous conversations.
The clarification that I thought that we were expecting from Jorge was
whether we are allowed to replace 'the code' in the first paragraph by
'the MIB module' for MIB modules and 'the PIB module' for PIB modules. Or
we must use exactly the copyright text below?<br><br>

<dd>Dan<br><br>
<br><br>

<dd>-----Original Message-----<br>

<dd>From: iesg-bounces@ietf.org on behalf of Russ Housley<br>

<dd>Sent: Wed 3/25/2009 7:54 AM<br>

<dd>To: iesg@ietf.org<br>

<dd>Cc: trustees@ietf.org; rfc-editor@rfc-editor.org<br>

<dd>Subject: Copyright notice in &quot;code&quot;<br><br>

<dd>I spoke with Jorge today, and he confirmed that the entire legend
below needs to appear in comments in any code, such as MIB, PIB, ASN.1,
XML Schema, and so on.&nbsp; This is needed to comply with the BSD open
source license.<br><br>

<dd>Russ<br><br>
<br><br>
<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Copyright (c) &lt;insert year&gt; IETF Trust and the persons identified
as<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
authors of the code. All rights reserved.<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Redistribution and use in source and binary forms, with or without<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
modification, are permitted provided that the following conditions<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
are met:<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
Redistributions of source code must retain the above copyright<br>

<dd>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
notice, this list of conditions and the following disclaimer.<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
Redistributions in binary form must reproduce the above copyright<br>

<dd>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
notice, this list of conditions and the following disclaimer in the<br>

<dd>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
documentation and/or other materials provided with the distribution.<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
Neither the name of Internet Society, IETF or IETF Trust, nor the<br>

<dd>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
names of specific contributors, may be used to endorse or promote<br>

<dd>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
products derived from this software without specific prior written<br>

<dd>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
permission.<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;AS IS&quot; AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL,<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE,<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE<br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.<br>
</font>
</dl></blockquote></blockquote></body>
</html>


From henk@ripe.net  Tue Apr  7 01:06:55 2009
Return-Path: <henk@ripe.net>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF9773A6D94; Tue,  7 Apr 2009 01:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.377
X-Spam-Level: 
X-Spam-Status: No, score=-8.377 tagged_above=-999 required=5 tests=[AWL=2.222,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 l9TUt4A-o07J; Tue,  7 Apr 2009 01:06:48 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ripe.net [193.0.19.66]) by core3.amsl.com (Postfix) with ESMTP id BC37D28C112; Tue,  7 Apr 2009 01:06:47 -0700 (PDT)
Received: from herring.ripe.net ([193.0.1.203]) by postgirl.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1Lr6LU-00021i-Oh; Tue, 07 Apr 2009 10:07:51 +0200
Received: from geir.local (gw.office.nsrp.ripe.net [193.0.1.126]) by herring.ripe.net (Postfix) with ESMTP id 8B4492F583; Tue,  7 Apr 2009 10:07:48 +0200 (CEST)
Message-ID: <49DB09D4.6040805@ripe.net>
Date: Tue, 07 Apr 2009 10:07:48 +0200
From: Henk Uijterwaal <henk@ripe.net>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
References: <20090325055429.63BEC9A471B@odin.smetech.net>	<EDC652A26FB23C4EB6384A4584434A040153187D@307622ANEX5.global.avaya.com>	<20090405200839.BB7AB9A477D@odin.smetech.net>	<EDC652A26FB23C4EB6384A4584434A040158B4D2@307622ANEX5.global.avaya.com> <20090406181818.449929A477A@odin.smetech.net>
In-Reply-To: <20090406181818.449929A477A@odin.smetech.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: ----
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5dde138c14eb574fdf93729574d35c48a
X-Mailman-Approved-At: Tue, 07 Apr 2009 01:11:08 -0700
Cc: trustees@ietf.org, mib-doctors@ietf.org, David Partain <david.partain@ericsson.com>, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: [MIB-DOCTORS] [Trustees] Copyright notice in "code"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2009 08:06:56 -0000

Russ Housley wrote:
> Send email to trustees@ietf.org and ask.

I like the process but is the process known?

If somebody puts something into a RFC tomorrow that can reasonably be
seen as "code" but isn't included in the list, does anybody in the
publication process know that the list should be extended and the
copyright statement be put in the file?

Henk





> 
> Russ
> 
> 
> At 12:06 PM 4/6/2009, Romascanu, Dan (Dan) wrote:
>> * /Neither are YANG modules which result from the NETMOD WG.
>> /* 
>> */What is the process of adding new items to this list?
>> /* 
>> */Dan
>> /* 
>>
>> ------------------------------------------------------------------------
>>     From: Russ Housley [ mailto:housley@vigilsec.com]
>>     Sent: Sunday, April 05, 2009 11:08 PM
>>     To: Romascanu, Dan (Dan); iesg@ietf.org
>>     Cc: trustees@ietf.org; rfc-editor@rfc-editor.org; mib-doctors@ietf.org
>>     Subject: RE: Copyright notice in "code"
>>
>>     Dan:
>>
>>     I do not see PIB modules as code in the Trustee list.
>>     http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt
>>
>>     Russ
>>
>>     At 09:09 AM 3/25/2009, Romascanu, Dan (Dan) wrote:
>>
>>>         Russ,
>>>
>>>         I thought that we already knew this from the previous
>>>         conversations. The clarification that I thought that we were
>>>         expecting from Jorge was whether we are allowed to replace
>>>         'the code' in the first paragraph by 'the MIB module' for MIB
>>>         modules and 'the PIB module' for PIB modules. Or we must use
>>>         exactly the copyright text below?
>>>
>>>         Dan
>>>
>>>
>>>
>>>         -----Original Message-----
>>>         From: iesg-bounces@ietf.org on behalf of Russ Housley
>>>         Sent: Wed 3/25/2009 7:54 AM
>>>         To: iesg@ietf.org
>>>         Cc: trustees@ietf.org; rfc-editor@rfc-editor.org
>>>         Subject: Copyright notice in "code"
>>>
>>>         I spoke with Jorge today, and he confirmed that the entire
>>>         legend below needs to appear in comments in any code, such as
>>>         MIB, PIB, ASN.1, XML Schema, and so on.  This is needed to
>>>         comply with the BSD open source license.
>>>
>>>         Russ
>>>
>>>
>>>
>>>
>>>                     Copyright (c) <insert year> IETF Trust and the
>>>         persons identified as
>>>                     authors of the code. All rights reserved.
>>>               
>>>                     Redistribution and use in source and binary
>>>         forms, with or without
>>>                     modification, are permitted provided that the
>>>         following conditions
>>>                     are met:
>>>               
>>>                     - Redistributions of source code must retain the
>>>         above copyright
>>>                       notice, this list of conditions and the
>>>         following disclaimer.
>>>               
>>>                     - Redistributions in binary form must reproduce
>>>         the above copyright
>>>                       notice, this list of conditions and the
>>>         following disclaimer in the
>>>                       documentation and/or other materials provided
>>>         with the distribution.
>>>               
>>>                     - Neither the name of Internet Society, IETF or
>>>         IETF Trust, nor the
>>>                       names of specific contributors, may be used to
>>>         endorse or promote
>>>                       products derived from this software without
>>>         specific prior written
>>>                       permission.
>>>               
>>>                     THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT
>>>         HOLDERS AND CONTRIBUTORS
>>>                     "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
>>>         INCLUDING, BUT NOT
>>>                     LIMITED TO, THE IMPLIED WARRANTIES OF
>>>         MERCHANTABILITY AND FITNESS FOR
>>>                     A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
>>>         SHALL THE COPYRIGHT
>>>                     OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
>>>         INDIRECT, INCIDENTAL,
>>>                     SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
>>>         (INCLUDING, BUT NOT
>>>                     LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
>>>         SERVICES; LOSS OF USE,
>>>                     DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
>>>         HOWEVER CAUSED AND ON ANY
>>>                     THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
>>>         LIABILITY, OR TORT
>>>                     (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
>>>         ANY WAY OUT OF THE USE
>>>                     OF THIS SOFTWARE, EVEN IF ADVISED OF THE
>>>         POSSIBILITY OF SUCH DAMAGE.
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Trustees mailing list
> Trustees@ietf.org
> https://www.ietf.org/mailman/listinfo/trustees


-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.amsterdamned.org/~henk
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

Belgium: an unsolvable problem, discussed in endless meetings, with no
          hope for a solution, where everybody still lives happily.

From dromasca@avaya.com  Tue Apr  7 02:04:40 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B26C128C167; Tue,  7 Apr 2009 02:04:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, 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 a6W9fLsMfv+r; Tue,  7 Apr 2009 02:04:35 -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 0CDB23A67A5; Tue,  7 Apr 2009 02:04:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.39,336,1235970000";  d="scan'208,217";a="167169437"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Apr 2009 05:05:40 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 07 Apr 2009 05:05:39 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9B760.05174B01"
Date: Tue, 7 Apr 2009 11:05:37 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040158B5DA@307622ANEX5.global.avaya.com>
In-Reply-To: <20090406181818.449929A477A@odin.smetech.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Copyright notice in "code"
Thread-Index: Acm25BLnPnbfZYw3RlGwNvPhHqxZOQAe7aaw
References: <20090325055429.63BEC9A471B@odin.smetech.net> <EDC652A26FB23C4EB6384A4584434A040153187D@307622ANEX5.global.avaya.com> <20090405200839.BB7AB9A477D@odin.smetech.net> <EDC652A26FB23C4EB6384A4584434A040158B4D2@307622ANEX5.global.avaya.com> <20090406181818.449929A477A@odin.smetech.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Russ Housley" <housley@vigilsec.com>, <iesg@ietf.org>
Cc: trustees@ietf.org, mib-doctors@ietf.org, David Partain <david.partain@ericsson.com>, rfc-editor@rfc-editor.org
Subject: Re: [MIB-DOCTORS] Copyright notice in "code"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2009 09:04:40 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9B760.05174B01
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Trustees are copied to the mails, so the question is asked.=20
=20
What is the process of adding new types of 'code' to the list?=20
=20
Thanks,=20
=20
Dan
=20


________________________________

	From: Russ Housley [mailto:housley@vigilsec.com]=20
	Sent: Monday, April 06, 2009 9:08 PM
	To: Romascanu, Dan (Dan); iesg@ietf.org
	Cc: trustees@ietf.org; rfc-editor@rfc-editor.org;
mib-doctors@ietf.org; David Kessens; David Partain
	Subject: RE: Copyright notice in "code"
=09
=09
	Send email to trustees@ietf.org and ask.
=09
	Russ
=09
=09
	At 12:06 PM 4/6/2009, Romascanu, Dan (Dan) wrote:
=09

		Neither are YANG modules which result from the NETMOD
WG.=20
		=20
		What is the process of adding new items to this list?=20
		=20
		Dan
		=20
	=09
	=09

________________________________

			From: Russ Housley [ mailto:housley@vigilsec.com
<mailto:housley@vigilsec.com> ]=20
		=09
			Sent: Sunday, April 05, 2009 11:08 PM
		=09
			To: Romascanu, Dan (Dan); iesg@ietf.org
		=09
			Cc: trustees@ietf.org;
rfc-editor@rfc-editor.org; mib-doctors@ietf.org
		=09
			Subject: RE: Copyright notice in "code"
		=09
		=09
			Dan:
		=09
		=09
			I do not see PIB modules as code in the Trustee
list.
		=09
=09
http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt
		=09
		=09
			Russ
		=09
		=09
			At 09:09 AM 3/25/2009, Romascanu, Dan (Dan)
wrote:
		=09
		=09

				Russ,
			=09
			=09
				I thought that we already knew this from
the previous conversations. The clarification that I thought that we
were expecting from Jorge was whether we are allowed to replace 'the
code' in the first paragraph by 'the MIB module' for MIB modules and
'the PIB module' for PIB modules. Or we must use exactly the copyright
text below?
			=09
			=09
				Dan
			=09
			=09
			=09
			=09
				-----Original Message-----
			=09
				From: iesg-bounces@ietf.org on behalf of
Russ Housley
			=09
				Sent: Wed 3/25/2009 7:54 AM
			=09
				To: iesg@ietf.org
			=09
				Cc: trustees@ietf.org;
rfc-editor@rfc-editor.org
			=09
				Subject: Copyright notice in "code"
			=09
			=09
				I spoke with Jorge today, and he
confirmed that the entire legend below needs to appear in comments in
any code, such as MIB, PIB, ASN.1, XML Schema, and so on.  This is
needed to comply with the BSD open source license.
			=09
			=09
				Russ
			=09
			=09
			=09
			=09
			=09
				            Copyright (c) <insert year>
IETF Trust and the persons identified as
			=09
				            authors of the code. All
rights reserved.
			=09
				      =20
			=09
				            Redistribution and use in
source and binary forms, with or without
			=09
				            modification, are permitted
provided that the following conditions
			=09
				            are met:
			=09
				      =20
			=09
				            - Redistributions of source
code must retain the above copyright
			=09
				              notice, this list of
conditions and the following disclaimer.
			=09
				      =20
			=09
				            - Redistributions in binary
form must reproduce the above copyright
			=09
				              notice, this list of
conditions and the following disclaimer in the
			=09
				              documentation and/or other
materials provided with the distribution.
			=09
				      =20
			=09
				            - Neither the name of
Internet Society, IETF or IETF Trust, nor the
			=09
				              names of specific
contributors, may be used to endorse or promote
			=09
				              products derived from this
software without specific prior written
			=09
				              permission.
			=09
				      =20
			=09
				            THIS SOFTWARE IS PROVIDED BY
THE COPYRIGHT HOLDERS AND CONTRIBUTORS
			=09
				            "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT
			=09
				            LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
			=09
				            A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
			=09
				            OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
			=09
				            SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
			=09
				            LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
			=09
				            DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
			=09
				            THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT
			=09
				            (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
			=09
				            OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
			=09


------_=_NextPart_001_01C9B760.05174B01
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.2900.3492" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D739580309-07042009><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>Trustees are copied to the mails, so the question =
is asked.=20
</EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D739580309-07042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D739580309-07042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>What is the process of adding new types of 'code' to the list?=20
</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D739580309-07042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D739580309-07042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Thanks, </FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D739580309-07042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D739580309-07042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D739580309-07042009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</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> Russ Housley=20
  [mailto:housley@vigilsec.com] <BR><B>Sent:</B> Monday, April 06, 2009 =
9:08=20
  PM<BR><B>To:</B> Romascanu, Dan (Dan); iesg@ietf.org<BR><B>Cc:</B>=20
  trustees@ietf.org; rfc-editor@rfc-editor.org; mib-doctors@ietf.org; =
David=20
  Kessens; David Partain<BR><B>Subject:</B> RE: Copyright notice in=20
  "code"<BR></FONT><BR></DIV>
  <DIV></DIV>Send email to trustees@ietf.org and =
ask.<BR><BR>Russ<BR><BR><BR>At=20
  12:06 PM 4/6/2009, Romascanu, Dan (Dan) wrote:<BR>
  <BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite"><FONT color=3D#0000ff =

    size=3D2><B><I>Neither are YANG modules which result from the NETMOD =
WG.=20
    <BR></I></B></FONT>&nbsp;<BR><FONT color=3D#0000ff =
size=3D2><B><I>What is the=20
    process of adding new items to this list? =
<BR></I></B></FONT>&nbsp;<BR><FONT=20
    color=3D#0000ff size=3D2><B><I>Dan<BR></I></B></FONT>&nbsp;<BR><BR>
    <DL>
      <HR>

      <DD><FONT face=3DTahoma size=3D2>From:</B> Russ Housley [<A=20
      href=3D"mailto:housley@vigilsec.com" eudora=3D"autourl">=20
      mailto:housley@vigilsec.com</A>] <BR>
      <DD>Sent:</B> Sunday, April 05, 2009 11:08 PM<BR>
      <DD>To:</B> Romascanu, Dan (Dan); iesg@ietf.org<BR>
      <DD>Cc:</B> trustees@ietf.org; rfc-editor@rfc-editor.org;=20
      mib-doctors@ietf.org<BR>
      <DD>Subject:</B> RE: Copyright notice in "code"<BR></FONT><BR>
      <DD>Dan:<BR><BR>
      <DD>I do not see PIB modules as code in the Trustee list.<BR>
      <DD><A=20
      =
href=3D"http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt"=20
      =
eudora=3D"autourl">http://trustee.ietf.org/docs/Code-Components-List-11-1=
0-08.txt</A><BR><BR>
      <DD>Russ<BR><BR>
      <DD>At 09:09 AM 3/25/2009, Romascanu, Dan (Dan) wrote:<BR><BR>
      <BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">
        <DD><FONT size=3D2>Russ,<BR><BR>
        <DD>I thought that we already knew this from the previous =
conversations.=20
        The clarification that I thought that we were expecting from =
Jorge was=20
        whether we are allowed to replace 'the code' in the first =
paragraph by=20
        'the MIB module' for MIB modules and 'the PIB module' for PIB =
modules.=20
        Or we must use exactly the copyright text below?<BR><BR>
        <DD>Dan<BR><BR><BR><BR>
        <DD>-----Original Message-----<BR>
        <DD>From: iesg-bounces@ietf.org on behalf of Russ Housley<BR>
        <DD>Sent: Wed 3/25/2009 7:54 AM<BR>
        <DD>To: iesg@ietf.org<BR>
        <DD>Cc: trustees@ietf.org; rfc-editor@rfc-editor.org<BR>
        <DD>Subject: Copyright notice in "code"<BR><BR>
        <DD>I spoke with Jorge today, and he confirmed that the entire =
legend=20
        below needs to appear in comments in any code, such as MIB, PIB, =
ASN.1,=20
        XML Schema, and so on.&nbsp; This is needed to comply with the =
BSD open=20
        source license.<BR><BR>
        <DD>Russ<BR><BR><BR><BR><BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Copyright (c) &lt;insert year&gt; IETF Trust and the persons =
identified=20
        as<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        authors of the code. All rights reserved.<BR>
        <DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Redistribution and use in source and binary forms, with or =
without<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        modification, are permitted provided that the following =
conditions<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        are met:<BR>
        <DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =

        Redistributions of source code must retain the above =
copyright<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        notice, this list of conditions and the following =
disclaimer.<BR>
        <DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =

        Redistributions in binary form must reproduce the above =
copyright<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        notice, this list of conditions and the following disclaimer in =
the<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        documentation and/or other materials provided with the =
distribution.<BR>
        <DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - =

        Neither the name of Internet Society, IETF or IETF Trust, nor =
the<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        names of specific contributors, may be used to endorse or =
promote<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        products derived from this software without specific prior =
written<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        permission.<BR>
        <DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND =
CONTRIBUTORS<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT =
NOT<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND =
FITNESS=20
FOR<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A =

        PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE =
COPYRIGHT<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,=20
INCIDENTAL,<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT =
NOT<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF =

USE,<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND =
ON=20
ANY<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR =
TORT<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF =
THE=20
USE<BR>
        =
<DD>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH=20
        DAMAGE.<BR></FONT></DD></BLOCKQUOTE></DD></DL></BLOCKQUOTE>
  <BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C9B760.05174B01--

From rpelletier@isoc.org  Tue Apr  7 06:31:40 2009
Return-Path: <rpelletier@isoc.org>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50FC73A6941 for <mib-doctors@core3.amsl.com>; Tue,  7 Apr 2009 06:31:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.579
X-Spam-Level: 
X-Spam-Status: No, score=-103.579 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ne6B2YhdS5KM for <mib-doctors@core3.amsl.com>; Tue,  7 Apr 2009 06:31:39 -0700 (PDT)
Received: from smtp115.iad.emailsrvr.com (smtp115.iad.emailsrvr.com [207.97.245.115]) by core3.amsl.com (Postfix) with ESMTP id C039F3A6978 for <mib-doctors@ietf.org>; Tue,  7 Apr 2009 06:31:38 -0700 (PDT)
Received: from relay1.r1.iad.emailsrvr.com (localhost [127.0.0.1]) by relay1.r1.iad.emailsrvr.com (SMTP Server) with ESMTP id CF0BF44C17B;  Tue,  7 Apr 2009 09:32:43 -0400 (EDT)
Received: by relay1.r1.iad.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 7AB0344C182;  Tue,  7 Apr 2009 09:32:43 -0400 (EDT)
Message-Id: <DFE6FFE0-50EE-49D8-AC6A-CB7FBB9815FD@isoc.org>
From: Ray Pelletier <rpelletier@isoc.org>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040158B5DA@307622ANEX5.global.avaya.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-102-958441297
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 7 Apr 2009 09:32:42 -0400
References: <20090325055429.63BEC9A471B@odin.smetech.net> <EDC652A26FB23C4EB6384A4584434A040153187D@307622ANEX5.global.avaya.com> <20090405200839.BB7AB9A477D@odin.smetech.net> <EDC652A26FB23C4EB6384A4584434A040158B4D2@307622ANEX5.global.avaya.com> <20090406181818.449929A477A@odin.smetech.net> <EDC652A26FB23C4EB6384A4584434A040158B5DA@307622ANEX5.global.avaya.com>
X-Mailer: Apple Mail (2.930.3)
X-Mailman-Approved-At: Mon, 13 Apr 2009 08:04:38 -0700
Cc: trustees@ietf.org, mib-doctors@ietf.org, Russ Housley <housley@vigilsec.com>, David Partain <david.partain@ericsson.com>, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: [MIB-DOCTORS] [Trustees] Copyright notice in "code"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2009 13:31:40 -0000

--Apple-Mail-102-958441297
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Dan,

Your request to have PIB modules considered 'code' and placed on the  
Code Components list at
http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt  is  
accepted for Trustee consideration.

I anticipate the Trust will review the matter in April.

Ray


On Apr 7, 2009, at 5:05 AM, Romascanu, Dan (Dan) wrote:

> Trustees are copied to the mails, so the question is asked.
>
> What is the process of adding new types of 'code' to the list?
>
> Thanks,
>
> Dan
>
>
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: Monday, April 06, 2009 9:08 PM
> To: Romascanu, Dan (Dan); iesg@ietf.org
> Cc: trustees@ietf.org; rfc-editor@rfc-editor.org; mib- 
> doctors@ietf.org; David Kessens; David Partain
> Subject: RE: Copyright notice in "code"
>
> Send email to trustees@ietf.org and ask.
>
> Russ
>
>
> At 12:06 PM 4/6/2009, Romascanu, Dan (Dan) wrote:
>> Neither are YANG modules which result from the NETMOD WG.
>>
>> What is the process of adding new items to this list?
>>
>> Dan
>>
>>
>> From: Russ Housley [ mailto:housley@vigilsec.com]
>> Sent: Sunday, April 05, 2009 11:08 PM
>> To: Romascanu, Dan (Dan); iesg@ietf.org
>> Cc: trustees@ietf.org; rfc-editor@rfc-editor.org; mib- 
>> doctors@ietf.org
>> Subject: RE: Copyright notice in "code"
>>
>> Dan:
>>
>> I do not see PIB modules as code in the Trustee list.
>> http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt
>>
>> Russ
>>
>> At 09:09 AM 3/25/2009, Romascanu, Dan (Dan) wrote:
>>
>>> Russ,
>>>
>>> I thought that we already knew this from the previous  
>>> conversations. The clarification that I thought that we were  
>>> expecting from Jorge was whether we are allowed to replace 'the  
>>> code' in the first paragraph by 'the MIB module' for MIB modules  
>>> and 'the PIB module' for PIB modules. Or we must use exactly the  
>>> copyright text below?
>>>
>>> Dan
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: iesg-bounces@ietf.org on behalf of Russ Housley
>>> Sent: Wed 3/25/2009 7:54 AM
>>> To: iesg@ietf.org
>>> Cc: trustees@ietf.org; rfc-editor@rfc-editor.org
>>> Subject: Copyright notice in "code"
>>>
>>> I spoke with Jorge today, and he confirmed that the entire legend  
>>> below needs to appear in comments in any code, such as MIB, PIB,  
>>> ASN.1, XML Schema, and so on.  This is needed to comply with the  
>>> BSD open source license.
>>>
>>> Russ
>>>
>>>
>>>
>>>
>>>             Copyright (c) <insert year> IETF Trust and the persons  
>>> identified as
>>>             authors of the code. All rights reserved.
>>>
>>>             Redistribution and use in source and binary forms,  
>>> with or without
>>>             modification, are permitted provided that the  
>>> following conditions
>>>             are met:
>>>
>>>             - Redistributions of source code must retain the above  
>>> copyright
>>>               notice, this list of conditions and the following  
>>> disclaimer.
>>>
>>>             - Redistributions in binary form must reproduce the  
>>> above copyright
>>>               notice, this list of conditions and the following  
>>> disclaimer in the
>>>               documentation and/or other materials provided with  
>>> the distribution.
>>>
>>>             - Neither the name of Internet Society, IETF or IETF  
>>> Trust, nor the
>>>               names of specific contributors, may be used to  
>>> endorse or promote
>>>               products derived from this software without specific  
>>> prior written
>>>               permission.
>>>
>>>             THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND  
>>> CONTRIBUTORS
>>>             "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,  
>>> INCLUDING, BUT NOT
>>>             LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY  
>>> AND FITNESS FOR
>>>             A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL  
>>> THE COPYRIGHT
>>>             OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,  
>>> INDIRECT, INCIDENTAL,
>>>             SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES  
>>> (INCLUDING, BUT NOT
>>>             LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR  
>>> SERVICES; LOSS OF USE,
>>>             DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER  
>>> CAUSED AND ON ANY
>>>             THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT  
>>> LIABILITY, OR TORT
>>>             (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY  
>>> OUT OF THE USE
>>>             OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY  
>>> OF SUCH DAMAGE.
>
> _______________________________________________
> Trustees mailing list
> Trustees@ietf.org
> https://www.ietf.org/mailman/listinfo/trustees


--Apple-Mail-102-958441297
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Dan,<div><br></div><div>Your =
request to have PIB modules considered 'code' and placed on the Code =
Components list at&nbsp;</div><div><a =
href=3D"http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt">ht=
tp://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt</a> =
&nbsp;is accepted for Trustee consideration.</div><div><br></div><div>I =
anticipate the Trust will review the matter in =
April.</div><div><br></div><div>Ray</div><div><br></div><div><br><div><div=
>On Apr 7, 2009, at 5:05 AM, Romascanu, Dan (Dan) wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"> <div> =
<div><span class=3D"739580309-07042009"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"><strong><em>Trustees are copied to the =
mails, so the question is asked. </em></strong></font></span></div> =
<div><span class=3D"739580309-07042009"><strong><em><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></em></strong></span>&nbsp;</div> =
<div><span class=3D"739580309-07042009"><strong><em><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">What is the process of adding new types of =
'code' to the list? </font></em></strong></span></div> <div><span =
class=3D"739580309-07042009"><strong><em><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></em></strong></span>&nbsp;</div> =
<div><span class=3D"739580309-07042009"><strong><em><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">Thanks, </font></em></strong></span></div> =
<div><span class=3D"739580309-07042009"><strong><em><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></em></strong></span>&nbsp;</div> =
<div><span class=3D"739580309-07042009"><strong><em><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">Dan</font></em></strong></span></div> =
<div><span class=3D"739580309-07042009"><strong><em><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></em></strong></span>&nbsp;</div><br> =
<blockquote dir=3D"ltr" style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">  <div =
class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"> =
 <hr tabindex=3D"-1">  <font face=3D"Tahoma" size=3D"2"><b>From:</b> =
Russ Housley   [<a =
href=3D"mailto:housley@vigilsec.com">mailto:housley@vigilsec.com</a>] =
<br><b>Sent:</b> Monday, April 06, 2009 9:08   PM<br><b>To:</b> =
Romascanu, Dan (Dan); <a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a><br><b>Cc:</b>   <a =
href=3D"mailto:trustees@ietf.org">trustees@ietf.org</a>; <a =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>; =
<a href=3D"mailto:mib-doctors@ietf.org">mib-doctors@ietf.org</a>; David  =
 Kessens; David Partain<br><b>Subject:</b> RE: Copyright notice in   =
"code"<br></font><br></div>  <div></div>Send email to <a =
href=3D"mailto:trustees@ietf.org">trustees@ietf.org</a> and =
ask.<br><br>Russ<br><br><br>At   12:06 PM 4/6/2009, Romascanu, Dan (Dan) =
wrote:<br>  <blockquote class=3D"cite" cite=3D"" type=3D"cite"><font =
color=3D"#0000ff" size=3D"2"><b><i>Neither are YANG modules which result =
from the NETMOD WG.     <br></i></b></font>&nbsp;<br><font =
color=3D"#0000ff" size=3D"2"><b><i>What is the     process of adding new =
items to this list? <br></i></b></font>&nbsp;<br><font color=3D"#0000ff" =
size=3D"2"><b><i>Dan<br></i></b></font>&nbsp;<br><br>    <dl>      <hr>  =
     <dd><font face=3D"Tahoma" size=3D"2">From: Russ Housley [<a =
href=3D"mailto:housley@vigilsec.com" eudora=3D"autourl">       =
mailto:housley@vigilsec.com</a>] <br>      </font></dd><font =
face=3D"Tahoma" size=3D"2"><dd>Sent: Sunday, April 05, 2009 11:08 PM<br> =
     </dd><dd>To: Romascanu, Dan (Dan); <a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a><br>      </dd><dd>Cc: <a =
href=3D"mailto:trustees@ietf.org">trustees@ietf.org</a>; <a =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>; =
      <a href=3D"mailto:mib-doctors@ietf.org">mib-doctors@ietf.org</a><br>=
      </dd></font><dd><font face=3D"Tahoma" size=3D"2">Subject: RE: =
Copyright notice in "code"<br></font><br>      </dd><dd>Dan:<br><br>     =
 </dd><dd>I do not see PIB modules as code in the Trustee list.<br>      =
</dd><dd><a =
href=3D"http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt" =
eudora=3D"autourl">http://trustee.ietf.org/docs/Code-Components-List-11-10=
-08.txt</a><br><br>      </dd><dd>Russ<br><br>      </dd><dd>At 09:09 AM =
3/25/2009, Romascanu, Dan (Dan) wrote:<br><br>      <blockquote =
class=3D"cite" cite=3D"" type=3D"cite">        <dd><font =
size=3D"2">Russ,<br><br>        </font></dd><font size=3D"2"><dd>I =
thought that we already knew this from the previous conversations.       =
  The clarification that I thought that we were expecting from Jorge was =
        whether we are allowed to replace 'the code' in the first =
paragraph by         'the MIB module' for MIB modules and 'the PIB =
module' for PIB modules.         Or we must use exactly the copyright =
text below?<br><br>        </dd><dd>Dan<br><br><br><br>        =
</dd><dd>-----Original Message-----<br>        </dd><dd>From: <a =
href=3D"mailto:iesg-bounces@ietf.org">iesg-bounces@ietf.org</a> on =
behalf of Russ Housley<br>        </dd><dd>Sent: Wed 3/25/2009 7:54 =
AM<br>        </dd><dd>To: <a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a><br>        </dd><dd>Cc: =
<a href=3D"mailto:trustees@ietf.org">trustees@ietf.org</a>; <a =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br=
>        </dd><dd>Subject: Copyright notice in "code"<br><br>        =
</dd><dd>I spoke with Jorge today, and he confirmed that the entire =
legend         below needs to appear in comments in any code, such as =
MIB, PIB, ASN.1,         XML Schema, and so on.&nbsp; This is needed to =
comply with the BSD open         source license.<br><br>        =
</dd><dd>Russ<br><br><br><br><br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         Copyright (c) &lt;insert year> IETF Trust and the persons =
identified         as<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         authors of the code. All rights reserved.<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         Redistribution and use in source and binary forms, with or =
without<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         modification, are permitted provided that the following =
conditions<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         are met:<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; -         Redistributions of source code must retain the above =
copyright<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;         notice, this list of conditions and the following =
disclaimer.<br>        </dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; -         Redistributions in binary form must reproduce the above =
copyright<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;         notice, this list of conditions and the following =
disclaimer in the<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;         documentation and/or other materials provided with =
the distribution.<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; -         Neither the name of Internet Society, IETF or IETF Trust, =
nor the<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;         names of specific contributors, may be used to =
endorse or promote<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;         products derived from this software without =
specific prior written<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;         permission.<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND =
CONTRIBUTORS<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT =
NOT<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND =
FITNESS FOR<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; A         PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE =
COPYRIGHT<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, =
INCIDENTAL,<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT =
NOT<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS =
OF USE,<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND =
ON ANY<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR =
TORT<br>        =
</dd><dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;         (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF =
THE USE<br>        </dd></font><dd><font =
size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;         OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH =
        DAMAGE.<br></font></dd></blockquote></dd></dl></blockquote>  =
<blockquote></blockquote></blockquote></div> =
_______________________________________________<br>Trustees mailing =
list<br><a =
href=3D"mailto:Trustees@ietf.org">Trustees@ietf.org</a><br>https://www.iet=
f.org/mailman/listinfo/trustees<br></blockquote></div><br></div></body></h=
tml>=

--Apple-Mail-102-958441297--

From dromasca@avaya.com  Thu Apr 16 00:37:35 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E315D28C0F1; Thu, 16 Apr 2009 00:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level: 
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.082,  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 QU5LK0KXeYfI; Thu, 16 Apr 2009 00:37:35 -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 DD1DC3A6D05; Thu, 16 Apr 2009 00:37:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,197,1238990400"; d="scan'208";a="168048181"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 16 Apr 2009 03:38:47 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 16 Apr 2009 03:38:46 -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, 16 Apr 2009 09:38:30 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04015DA6AC@307622ANEX5.global.avaya.com>
In-reply-to: <EDC652A26FB23C4EB6384A4584434A0401514435@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] [IPFIX] AD review of draft-ietf-ipfix-mib-05.txt
Thread-index: AcmRHJmf24PVuTAzTrOZoe2H0CfpvQPihcJAAcqLQMAFpQf5IA==
References: <EDC652A26FB23C4EB6384A4584434A04013E05ED@307622ANEX5.global.avaya.com><547F018265F92642B577B986577D671C7009CF@VENUS.office> <EDC652A26FB23C4EB6384A4584434A0401514435@307622ANEX5.global.avaya.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "Thomas Dietz" <Thomas.Dietz@nw.neclab.eu>, "IETF IPFIX Working Group" <ipfix@ietf.org>
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [IPFIX] AD review of draft-ietf-ipfix-mib-05.txt
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2009 07:37:36 -0000

Thomas,

I do not think that the pending issues T19 and T21 were addressed
properly in  draft-ietf-ipfix-mib-06.txt

See in-line my concerns.=20

Thanks and Regards,

Dan



> -----Original Message-----
> From: mib-doctors-bounces@ietf.org=20
> [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Romascanu,=20
> Dan (Dan)
> Sent: Wednesday, March 18, 2009 3:57 PM
> To: Thomas Dietz; IETF IPFIX Working Group
> Cc: MIB Doctors (E-mail)
> Subject: Re: [MIB-DOCTORS] [IPFIX] AD review of=20
> draft-ietf-ipfix-mib-05.txt
>=20
> Thank you for addressing my comments. Most of the issues were=20
> acknowledged and fixed accordingly. T19 and T21 still need=20
> discussion, while T23 needs to be acknowledged by the other editors.=20
>=20
> My question to the WG chairs is whether we should send the=20
> document to IETF Last Call, considering the open issues as=20
> Last Call issues, to be answered and resolved together with=20
> other Last Call comments we receive.
>=20
>=20
> Dan
> =20
>=20
> > -----Original Message-----
> > From: Thomas Dietz [mailto:Thomas.Dietz@nw.neclab.eu]
> > Sent: Monday, March 09, 2009 1:26 PM
> > To: Romascanu, Dan (Dan); IETF IPFIX Working Group
> > Cc: MIB Doctors (E-mail)
> > Subject: RE: [IPFIX] AD review of draft-ietf-ipfix-mib-05.txt
> >=20
> > Dear Dan, all,
> >=20
> > find my comments inline...
> >=20
> >=20
> > > T19. I cannot understand what useful information carries=20
> > > ipfixmeteringProcessId - it is not an index and its value is=20
> > > implementation dependent.
> >=20
> > We wanted to give a kind of ID to make it possible to identify the=20
> > process that creates the Flow Records. This may be a process id or=20
> > something similar. Maybe we should specify it as process id. This=20
> > needs further discussion.
> >=20

This does not seem to be addressed. The object with the current
DESCRIPTION clause would not help an implementer understand what is the
information to be placed in or a manager to know what to do with it.=20

> >=20
> > > T21. I assume that selection functions will be added in the
> > future. If
> > > I am wrong please delete all mention of extensibility and
> > take out the
> > > ipfixSelectorFunctions group. If I am right, I suggest to put=20
> > > ipfixSelectorFunctions in a separate MIB module that will be IANA=20
> > > maintained, so that new functions can be added in the
> > future without
> > > the need to revise the MIB module and the RFC. The separate
> > MIB module
> > > will become the initial version of the IANA maintained
> > module, and new
> > > selector functions will be added using for example Expert Review=20
> > > policy.
> > >=20
> > >=20
> >=20
> > I personally think this makes sense to put it in a separate=20
> MIB module=20
> > which is maintained by IANA but this needs further=20
> discussion on the=20
> > list which I will start soon.

This does not seem to be addressed  From your response it looked like
you agreed that moving ipfixSelectorFunctions to a separate
IANA-maintained module would be a good idea. Yet, I see that the group
is still present in the current MIB, and although it includes only one
object ipfixFuncSelectAllAvail - you would need to deprecate it when the
IANA-maintained MIB module shows up. This is cumbersome, I suggest to
take it out as the object does not provide any useful information any
way, from the DESCRIPTION clause it is always at value true.=20


From Thomas.Dietz@nw.neclab.eu  Thu Apr 16 00:42:32 2009
Return-Path: <Thomas.Dietz@nw.neclab.eu>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D711D28C159; Thu, 16 Apr 2009 00:42:32 -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 P2BDsugy+0a2; Thu, 16 Apr 2009 00:42:31 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id 29DB63A6CBC; Thu, 16 Apr 2009 00:42:31 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id ADB9B2C0008EB; Thu, 16 Apr 2009 09:43:43 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MhKktVLNpwVG; Thu, 16 Apr 2009 09:43:43 +0200 (CEST)
Received: from VENUS.office (mx2.office [192.168.24.15]) by smtp0.neclab.eu (Postfix) with ESMTP id 79ED12C000305; Thu, 16 Apr 2009 09:43:28 +0200 (CEST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 16 Apr 2009 09:43:26 +0200
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_0036_01C9BE77.CA4401D0"; micalg=SHA1
Message-ID: <547F018265F92642B577B986577D671C7FE79E@VENUS.office>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04015DA6AC@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] [IPFIX] AD review of draft-ietf-ipfix-mib-05.txt
Thread-Index: AcmRHJmf24PVuTAzTrOZoe2H0CfpvQPihcJAAcqLQMAFpQf5IAAAc1IQ
References: <EDC652A26FB23C4EB6384A4584434A04013E05ED@307622ANEX5.global.avaya.com><547F018265F92642B577B986577D671C7009CF@VENUS.office> <EDC652A26FB23C4EB6384A4584434A0401514435@307622ANEX5.global.avaya.com> <EDC652A26FB23C4EB6384A4584434A04015DA6AC@307622ANEX5.global.avaya.com>
From: "Thomas Dietz" <Thomas.Dietz@nw.neclab.eu>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, "IETF IPFIX Working Group" <ipfix@ietf.org>
X-Mailman-Approved-At: Thu, 16 Apr 2009 01:10:52 -0700
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [IPFIX] AD review of draft-ietf-ipfix-mib-05.txt
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2009 07:42:32 -0000

This is a multi-part message in MIME format.

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

Dear Dan,

you are right we need a revised version of the draft. Meanwhile we agreed
that for T19 the object will be deleted. For T21 we need to put up the text
and the extra MIB module in the draft. I will do that asap.

Best Regards,

Thomas

-- 
Thomas Dietz                 E-mail: Thomas.Dietz@nw.neclab.eu
NEC Europe Ltd.              Phone:  +49 6221 4342-128
NEC Laboratories Europe      Fax:    +49 6221 4342-155
Network Research Division
Kurfuersten-Anlage 36
69115 Heidelberg, Germany    http://www.nw.neclab.eu

NEC Europe Limited           Registered in England 2832014
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Donnerstag, 16. April 2009 09:38
> To: Romascanu, Dan (Dan); Thomas Dietz; IETF IPFIX Working Group
> Cc: MIB Doctors (E-mail)
> Subject: RE: [MIB-DOCTORS] [IPFIX] AD review of draft-ietf-ipfix-mib-
> 05.txt
> 
> Thomas,
> 
> I do not think that the pending issues T19 and T21 were addressed
> properly in  draft-ietf-ipfix-mib-06.txt
> 
> See in-line my concerns.
> 
> Thanks and Regards,
> 
> Dan
> 
> 
> 
> > -----Original Message-----
> > From: mib-doctors-bounces@ietf.org
> > [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Romascanu,
> > Dan (Dan)
> > Sent: Wednesday, March 18, 2009 3:57 PM
> > To: Thomas Dietz; IETF IPFIX Working Group
> > Cc: MIB Doctors (E-mail)
> > Subject: Re: [MIB-DOCTORS] [IPFIX] AD review of
> > draft-ietf-ipfix-mib-05.txt
> >
> > Thank you for addressing my comments. Most of the issues were
> > acknowledged and fixed accordingly. T19 and T21 still need
> > discussion, while T23 needs to be acknowledged by the other editors.
> >
> > My question to the WG chairs is whether we should send the
> > document to IETF Last Call, considering the open issues as
> > Last Call issues, to be answered and resolved together with
> > other Last Call comments we receive.
> >
> >
> > Dan
> >
> >
> > > -----Original Message-----
> > > From: Thomas Dietz [mailto:Thomas.Dietz@nw.neclab.eu]
> > > Sent: Monday, March 09, 2009 1:26 PM
> > > To: Romascanu, Dan (Dan); IETF IPFIX Working Group
> > > Cc: MIB Doctors (E-mail)
> > > Subject: RE: [IPFIX] AD review of draft-ietf-ipfix-mib-05.txt
> > >
> > > Dear Dan, all,
> > >
> > > find my comments inline...
> > >
> > >
> > > > T19. I cannot understand what useful information carries
> > > > ipfixmeteringProcessId - it is not an index and its value is
> > > > implementation dependent.
> > >
> > > We wanted to give a kind of ID to make it possible to identify the
> > > process that creates the Flow Records. This may be a process id or
> > > something similar. Maybe we should specify it as process id. This
> > > needs further discussion.
> > >
> 
> This does not seem to be addressed. The object with the current
> DESCRIPTION clause would not help an implementer understand what is the
> information to be placed in or a manager to know what to do with it.
> 
> > >
> > > > T21. I assume that selection functions will be added in the
> > > future. If
> > > > I am wrong please delete all mention of extensibility and
> > > take out the
> > > > ipfixSelectorFunctions group. If I am right, I suggest to put
> > > > ipfixSelectorFunctions in a separate MIB module that will be IANA
> > > > maintained, so that new functions can be added in the
> > > future without
> > > > the need to revise the MIB module and the RFC. The separate
> > > MIB module
> > > > will become the initial version of the IANA maintained
> > > module, and new
> > > > selector functions will be added using for example Expert Review
> > > > policy.
> > > >
> > > >
> > >
> > > I personally think this makes sense to put it in a separate
> > MIB module
> > > which is maintained by IANA but this needs further
> > discussion on the
> > > list which I will start soon.
> 
> This does not seem to be addressed  From your response it looked like
> you agreed that moving ipfixSelectorFunctions to a separate
> IANA-maintained module would be a good idea. Yet, I see that the group
> is still present in the current MIB, and although it includes only one
> object ipfixFuncSelectAllAvail - you would need to deprecate it when
> the
> IANA-maintained MIB module shows up. This is cumbersome, I suggest to
> take it out as the object does not provide any useful information any
> way, from the DESCRIPTION clause it is always at value true.


------=_NextPart_000_0036_01C9BE77.CA4401D0
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIISNzCCA58w
ggKHoAMCAQICASYwDQYJKoZIhvcNAQEFBQAwcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRz
Y2hlIFRlbGVrb20gQUcxHzAdBgNVBAsTFlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMT
GkRldXRzY2hlIFRlbGVrb20gUm9vdCBDQSAyMB4XDTk5MDcwOTEyMTEwMFoXDTE5MDcwOTIzNTkw
MFowcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRzY2hlIFRlbGVrb20gQUcxHzAdBgNVBAsT
FlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMTGkRldXRzY2hlIFRlbGVrb20gUm9vdCBD
QSAyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqwujNeCLKRSxFIWvPBDkOW81XUqu
3ephjZVJ9G9koxpgZqSpQCKE2dSl5XiTDmgBrblNXDrO07ioQkDfz6O6gllqkhusHJraCCslJ/lp
I0fx4Ossepv1EwLQfjR8wp48AFmr9doM9TI8K6xQ2tbD3oOUyqgMmTIOCEhWW2r72uFYWAFJX3JB
PBUGAY5draq4k7TNnuun6GotUjTbOu9cdVHa2/Mx+e5xmDLEVBVEDPmbVe2t3xgIoKOGiknuUwWP
GUzV3lh5m9JqHEKrxdWnz2gPluThYZh2YciRfNY+AOKRUIfhnQrmrZfSHcY6fcu82gM01Y5bAfVq
B7cWtm5KfwIDAQABo0IwQDAdBgNVHQ4EFgQUMcN5G7r1U9cX4Il6LRdsCrMrnTMwDwYDVR0TBAgw
BgEB/wIBBTAOBgNVHQ8BAf8EBAMCAQYwDQYJKoZIhvcNAQEFBQADggEBAJRkWa05ZOcp6xP+WsOL
E1fIBCTwdHfAYONn++mJpoO/loJ8btTDPe+egG67KbSYerE7VOs5F0d+Go4L/B8xWTEEss4X8yzH
YjZV4iLYiVW0mEiqZPrWHDbYRHhaWiM6V5f1ejBPrp9qTEsrjqAD4z7gqdTSe9KzqOJyPK2e/4BZ
5JtFtPY7sM05GZgy5eohYZDkMSGONLH3LzVKhRDa54o3Ib5ZY+DyhYgxU9RUFIVwefQuBncndS8f
uIr5/sW62Dbkg+znZbe/Y1rzRq+BlDfUQYzWI9Yez/VoG0Rjolq6pzVZoeVwBZsOI1eZlAptujlj
KIaS8xiE2PvRzwVWZFcwggQhMIIDCaADAgECAgIAxzANBgkqhkiG9w0BAQUFADBxMQswCQYDVQQG
EwJERTEcMBoGA1UEChMTRGV1dHNjaGUgVGVsZWtvbSBBRzEfMB0GA1UECxMWVC1UZWxlU2VjIFRy
dXN0IENlbnRlcjEjMCEGA1UEAxMaRGV1dHNjaGUgVGVsZWtvbSBSb290IENBIDIwHhcNMDYxMjE5
MTAyOTAwWhcNMTkwNjMwMjM1OTAwWjBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVp
bjEQMA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAx
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6ZvDZ4X5Da71jVTDllA1PWLpbkztlNcA
W5UidNQg6zSP1uzAMQQLmYHiphTSUqAoI4SLdIkEXlvg4njBeMsWyyg1OXstkEXQ7aAAeny/Sg4b
AMOG6VwrMRF7DPOCJEOMHDiLamgAmu7cT3ir0sYTm3at7t4m6O8Br3QPwQmi9mvOvdPNFDBP9eXj
pMhim4IaAycwDQJlYE3t0QkjKpY1WCfTdsZxtpAdxO3/NYZ9bzOz2w/FEcKKg6GUXUFr2NIQ9Uz9
ylGs2b3vkoO72uuLFlZWQ8/h1RM9ph8nMM1JVNvJEzSacXXFbOqnC5j5IZ0nrz6jOTlIaoytyZn7
wxLyvQIDAQABo4HZMIHWMHAGA1UdHwRpMGcwZaBjoGGGX2h0dHA6Ly9wa2kudGVsZXNlYy5kZS9j
Z2ktYmluL3NlcnZpY2UvYWZfRG93bmxvYWRBUkwuY3JsPy1jcmxfZm9ybWF0PVhfNTA5Ji1pc3N1
ZXI9RFRfUk9PVF9DQV8yMB0GA1UdDgQWBBRJt8bP6D0ff+pEexMp9/EKcD7eZDAfBgNVHSMEGDAW
gBQxw3kbuvVT1xfgiXotF2wKsyudMzAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIB
AjANBgkqhkiG9w0BAQUFAAOCAQEAO+Fad8BIF9ypGOyBr1qJ8L0okqbKWRgScOwo8ueuf5Ys5/Jd
GTH2Eyt0vb2Asrn3Z8k5onk74RER7mt4kTN+O18mJ3VTZY4zY+7Pc8OwkiNJIVB1I6EfGOKUhT0/
M+l3II2iveahhSlA9j9zMlgNCWum2oVswD+7jWZkViROrg0/MjUBW+mMgtlyWU+xhoXxdIVW5cP4
XPON7kezUwVw5+VNimmDKOETCYaeXsjqWB4MH/mk1FoEaP0oPosCtli19qEsN1cAZ6sjaI1jpe+Z
a1z9S1b2q0CHNNQRkmzsh8UKCwczcrRvDB1ULNhRx8y/MNNDcvEyv4zOSWOoAPfyHDCCBS8wggQX
oAMCAQICBA0hCkcwDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCREUxEzARBgNVBAoTCkRGTi1W
ZXJlaW4xEDAOBgNVBAsTB0RGTi1QS0kxJDAiBgNVBAMTG0RGTi1WZXJlaW4gUENBIEdsb2JhbCAt
IEcwMTAeFw0wODEwMjQwODUyMDhaFw0xOTA2MzAwMDAwMDBaMIGQMQswCQYDVQQGEwJERTEYMBYG
A1UEChMPTkVDIEV1cm9wZSBMdGQuMSAwHgYDVQQLExdORUMgTGFib3JhdG9yaWVzIEV1cm9wZTES
MBAGA1UEAxMJTkVDTEFCLUNBMTEwLwYJKoZIhvcNAQkBFiJ6ZXJ0aWZpemllcnVuZ3NzdGVsbGVA
bncubmVjbGFiLmV1MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnvIVsbURqjIOcbnf
ruYkRceWOZpyvM2ebnYpbd1cP+zdWm6yR7HSO9ppOe1ZZFIasArqQpedPEFvcncSG94FRuW3ND4r
Rcq08mbpUTmpWmXfdYlJpQezbsOHCWR74NXoEEbK6TPZIMFpJr6dzQDAxnRc7UOgO6JQ1V42Z39B
PhIbPIWz64t8svafxbORmxulJn7F5zDLDcR1AEGyn+L9b645AGwapoKNh7cSQFTqdb6kGyPQjLWf
tv09dvmBDKesrcyLZXuDWJ1LMeizSjUEygdSszNXD3gePgJaVaZDS3o923W5gAyPCTSxpAFj8XJ+
/7Ap5jJwYhjJgJ8khFR7JQIDAQABo4IBxDCCAcAwEgYDVR0TAQH/BAgwBgEB/wIBATALBgNVHQ8E
BAMCAQYwHQYDVR0OBBYEFE8ch3od4C+Z9r4VqtE1nQ5K5ro2MB8GA1UdIwQYMBaAFEm3xs/oPR9/
6kR7Eyn38QpwPt5kMC0GA1UdEQQmMCSBInplcnRpZml6aWVydW5nc3N0ZWxsZUBudy5uZWNsYWIu
ZXUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290
LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2Jh
bC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggrBgEFBQcBAQSBlTCBkjBHBggrBgEFBQcw
AoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2Vy
dC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2Ev
cHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQBsMQ+dD0mmi48dgDU4R6Q/
eXcY0zQcHNp1Vu1s3kwO0WahWB0tiqVBodvfTAWG44xuw0I7NXSTwQ68FU5P0GIQnvRFZyVJlDjr
SNlLYxjqfmgb+KVm67o383cZIuDakEE0f29kULIEn2fg/HsDiBAXTsb4I19XaN0TXLI+PMhU+GDp
sGCJrydeugEV7qi15q8yymjSAsYgnrc2wJuXpyQ9r3qCtP6aedAPSHqOT8ga1dLT2YRZFs3vNm7T
HSr5JJymWMbfpD6OcbRTnNAjSMDHwJxgRBAflA6WzDVm7fk4jiWyLvJwWTMk19t8QLiKG7D0nYvj
cEUYyiOSE+SFUTEdMIIFODCCBCCgAwIBAgIEDTI0WzANBgkqhkiG9w0BAQUFADCBkDELMAkGA1UE
BhMCREUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExhYm9yYXRvcmll
cyBFdXJvcGUxEjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVydGlmaXppZXJ1
bmdzc3RlbGxlQG53Lm5lY2xhYi5ldTAeFw0wODExMDYwOTIwMTFaFw0xMTExMDYwOTIwMTFaMGAx
CzAJBgNVBAYTAkRFMRgwFgYDVQQKEw9ORUMgRXVyb3BlIEx0ZC4xIDAeBgNVBAsTF05FQyBMYWJv
cmF0b3JpZXMgRXVyb3BlMRUwEwYDVQQDEwxUaG9tYXMgRGlldHowggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQCniLuqlMflMs7ag3idESVRwfZ9nrdIyUmq5Tget4k9APGSPo2GZ1f1hr8y
MuJIGowc/HzS1laVSICclOXju1xW93Tm+Vco5gwkRqHXY3Rmda0r2jlb8niVie4qXQgXPzunFRqk
yNmbwYep3oD5Kq0GfB6EuZ7X6cYH5A7erAMeeQPhoDQDIfR79lRHlcMtanJZyORYNQONPEa+L4AF
v5f3nAsmY7ZLJ72wX7X8BtcF6Vdkr0T2b1YrPl8Qir7e0TKY9Rf0q5DKu3QdLnXk0Rb+63V/4vLS
PZ3XQVdwHzLiOhIZJVVMJE7TmJI0DFeDFn99O/F/Le/sJOJjNO4n6KMLAgMBAAGjggHHMIIBwzAJ
BgNVHRMEAjAAMAsGA1UdDwQEAwIF4DApBgNVHSUEIjAgBggrBgEFBQcDAgYIKwYBBQUHAwQGCisG
AQQBgjcUAgIwHQYDVR0OBBYEFLkbmpJJpIXhIR9JFttGC+KHW5g5MB8GA1UdIwQYMBaAFE8ch3od
4C+Z9r4VqtE1nQ5K5ro2MCQGA1UdEQQdMBuBGVRob21hcy5EaWV0ekBudy5uZWNsYWIuZXUwfQYD
VR0fBHYwdDA4oDagNIYyaHR0cDovL2NkcDEucGNhLmRmbi5kZS9uZWNsYWItY2EvcHViL2NybC9j
YWNybC5jcmwwOKA2oDSGMmh0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvbmVjbGFiLWNhL3B1Yi9jcmwv
Y2FjcmwuY3JsMIGYBggrBgEFBQcBAQSBizCBiDBCBggrBgEFBQcwAoY2aHR0cDovL2NkcDEucGNh
LmRmbi5kZS9uZWNsYWItY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MEIGCCsGAQUFBzAChjZodHRw
Oi8vY2RwMi5wY2EuZGZuLmRlL25lY2xhYi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZI
hvcNAQEFBQADggEBAEbKwRBhNxAzsH6kAYRBoIziyI2IY2QnZGeiGitOfkLKcFNIBH3ZfQXH4j20
4BP34Vzzob17EgsbLbNkMlxh2M7tenXH9vA4MiN5yPPBKoR7SfI6mIaIr+7kewOizJ8D5dvpdfP5
HbAUTZVSYHqixgBWJyNp7sXWVQtOo+eOv8qKUeiodClanKuCnGD42Bl6EQR486dlXvOronEikRYX
Xg6gFrhO+DonUYluMZpNdabnybKozchSdHcceOKd0JFMmyiSNG944ystXbR7QZqfNSh/Pbyc5QRp
Z1vdFZLFh907iS3KxueDYKDPWmlsPt/QnmXmF4A9/5OrmVS1C45k5rcxggQ4MIIENAIBATCBmTCB
kDELMAkGA1UEBhMCREUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExh
Ym9yYXRvcmllcyBFdXJvcGUxEjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVy
dGlmaXppZXJ1bmdzc3RlbGxlQG53Lm5lY2xhYi5ldQIEDTI0WzAJBgUrDgMCGgUAoIICczAYBgkq
hkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTA0MTYwNzQzMjZaMCMGCSqG
SIb3DQEJBDEWBBQakHnrHUOZfAb2EIGPDWdBLvW7uzCBqgYJKwYBBAGCNxAEMYGcMIGZMIGQMQsw
CQYDVQQGEwJERTEYMBYGA1UEChMPTkVDIEV1cm9wZSBMdGQuMSAwHgYDVQQLExdORUMgTGFib3Jh
dG9yaWVzIEV1cm9wZTESMBAGA1UEAxMJTkVDTEFCLUNBMTEwLwYJKoZIhvcNAQkBFiJ6ZXJ0aWZp
emllcnVuZ3NzdGVsbGVAbncubmVjbGFiLmV1AgQNMjRbMIGsBgsqhkiG9w0BCRACCzGBnKCBmTCB
kDELMAkGA1UEBhMCREUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExh
Ym9yYXRvcmllcyBFdXJvcGUxEjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVy
dGlmaXppZXJ1bmdzc3RlbGxlQG53Lm5lY2xhYi5ldQIEDTI0WzCBtwYJKoZIhvcNAQkPMYGpMIGm
MAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCgYIKoZIhvcNAwcwCwYJYIZIAWUDBAECMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMC
GjALBglghkgBZQMEAgMwCwYJYIZIAWUDBAICMAsGCWCGSAFlAwQCATAKBggqhkiG9w0CBTANBgkq
hkiG9w0BAQEFAASCAQA1M+gMnl3fFTC4c1Gtypr16q/9w8Mx4Qypj1KKXXQkzqOVfq7eUPXqW5KP
aAhx7DDRcRohxv3KvVsCnuK62PX04DY1YDRaz0eloxYXNbVZv1QY97nE/pAMQTcWPTJCYBpKO8y7
VapqDqjk8ErClM0HBwRq662xBg95RCMazzGILoHc1CZHBpUVJbnBxkiYGTtV2DSgi2WczNgg8KG5
9wvJuyzIAMTcZHS9fFWNx/mTaiHBo0/gCJX3R4nRg79LWYWXD47HkpLDW1yqbi8qDdWtwf5aCEM3
OxpmAhl1o/POzeDo9kncsxrDD4bthfJtQgiC+HQoZd+rPZCn1idZU+XDAAAAAAAA

------=_NextPart_000_0036_01C9BE77.CA4401D0--

From dromasca@avaya.com  Thu Apr 16 02:09:54 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 824743A6CBC; Thu, 16 Apr 2009 02:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081,  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 g6AaroOLCgvN; Thu, 16 Apr 2009 02:09:53 -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 690B628C184; Thu, 16 Apr 2009 02:09:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,197,1238990400"; d="scan'208";a="168055034"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 16 Apr 2009 05:11:05 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 16 Apr 2009 05:11:05 -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, 16 Apr 2009 11:10:42 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04015DA705@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Evaluation: draft-ietf-isms-secshell-15.txt to Proposed Standard
Thread-index: Acm+cvorKxEYO0H0RFu9Se9RX1pDhAAABvFA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <ops-dir@ietf.org>, <aaa-doctors@ietf.org>
Subject: [MIB-DOCTORS] FW: Evaluation: draft-ietf-isms-secshell-15.txt to Proposed Standard
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2009 09:09:54 -0000

=20

I believe that this document requires special attention from MIB-Doctors
and OPS-DIR.=20

Dan



A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isms-secshell-15.txt

Technical Summary

   The document defines a Transport Model for the Simple Network
   Management Protocol (SNMP), using the Secure Shell protocol (SSH).
   The document also defines a portion of the Management Information
   Base (MIB) for monitoring and managing the Secure Shell Transport
   Model for SNMP.

Working Group Summary

   The document has mainly been updated recently to track
   clarifications and to improve the readability. There has been WG
   consensus on revision 15 of this document and there are no
   controversies on the technical solution.

Document Quality

   There are two known implementations in progress of the Secure Shell
   Transport Model. There are no further vendor commitments at the
   moment to implement this specification.

Personnel

   The document shepherd is Juergen Schoenwaelder, and the responsible
   area director is Pasi Eronen.

RFC Editor Note

   Replace all occurrences of "SSHTM-MIB" with
   "SNMP-SSH-TM-MIB" (also in the MIB module in Section 7)

   Section 10:
   OLD:
   1.  two TCP registered port numbers in the
       http://www.iana.org/assignments/port-numbers registry which will
       be the default ports for SNMP over an SSH Transport Model (SSHTM)
       as defined in this document, and SNMP over an SSH Transport Model
       for notifications (SSHTM-TRAP) as defined in this document.  It
       would be good if the assigned numbers were x161 and x162.
   NEW:
   1.  two TCP registered port numbers in the
       http://www.iana.org/assignments/port-numbers registry which will
       be the default ports for SNMP over an SSH Transport Model
(snmpssh)


       as defined in this document, and SNMP over an SSH Transport Model
       for notifications (snmpssh-trap) as defined in this document.  It
       would be good if the assigned numbers were x161 (snmpssh) and
x162
       (snmpssh-trap).







From dromasca@avaya.com  Thu Apr 16 02:10:24 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EE563A6CC1; Thu, 16 Apr 2009 02:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081,  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 htSfEKK4c8zH; Thu, 16 Apr 2009 02:10:23 -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 369CB3A6B59; Thu, 16 Apr 2009 02:10:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,197,1238990400"; d="scan'208";a="158567477"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 16 Apr 2009 05:11:35 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 16 Apr 2009 05:11:35 -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, 16 Apr 2009 11:11:33 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04015DA708@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Evaluation: draft-ietf-isms-tmsm-16.txt to Proposed Standard 
Thread-index: Acm+cw7ftL4feU8YSX2+KfWzJkTCHAAADSlQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <ops-dir@ietf.org>, <aaa-doctors@ietf.org>
Subject: [MIB-DOCTORS] FW: Evaluation: draft-ietf-isms-tmsm-16.txt to Proposed Standard
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2009 09:10:24 -0000

=20

I believe that this document requires special attention from MIB-Doctors
and OPS-DIR.=20

Dan

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isms-tmsm-16.txt

Technical Summary

   The document defines a Transport Subsystem, extending the Simple
   Network Management Protocol (SNMP) architecture defined in RFC
   3411. The subsystem can contain Transport Models comparable to
   other subsystems in the RFC 3411 architecture.  The Transport
   Subsystem can be used to expand the transports to include secure
   transports such as SSH or TLS.

Working Group Summary

   The working group went over several revisions of this document
   while developing a Transport Model for SSH. The document did
   stabilize several revisions ago and has mainly been kept back to
   track clarifications and to ensure the new subsystem works with the
   SSH transport defined in a companion document. There has been
   strong WG consensus on revision 16 of this document.

Document Quality

   There are two known implementations in progress of secure transport
   models. A concrete SSH subsystem has been worked out by the ISMS
   working group and a DTLS subsystem is in progress as an individual
   draft and it seems the Transport Subsystem defined in this document
   is capable to supports both secure transports.

Personnel

   The document shepherd is Juergen Schoenwaelder, and the responsible
   area director is Pasi Eronen. The IANA Expert for the registries in
   this document is David Harrington (ietfdbh@comcast.net).







From dromasca@avaya.com  Thu Apr 16 02:11:06 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B87BC28C227; Thu, 16 Apr 2009 02:11:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.519
X-Spam-Level: 
X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=0.080,  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 PeVByWbqMBfI; Thu, 16 Apr 2009 02:11:05 -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 E6E3E28C1FE; Thu, 16 Apr 2009 02:10:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,197,1238990400"; d="scan'208";a="158567503"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 16 Apr 2009 05:12:00 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 16 Apr 2009 05:11:59 -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, 16 Apr 2009 11:11:57 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04015DA709@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Evaluation: draft-ietf-isms-transport-security-model-12.txt to Proposed Standard 
Thread-index: Acm+cx756bzJiBzsSJmAgdmYpkhcAwAADrTA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <ops-dir@ietf.org>, <aaa-doctors@ietf.org>
Subject: [MIB-DOCTORS] FW: Evaluation: draft-ietf-isms-transport-security-model-12.txt to Proposed Standard
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2009 09:11:06 -0000

=20

I believe that this document requires special attention from MIB-Doctors
and OPS-DIR.=20

Dan

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isms-transport-security-m
odel-12.txt

Technical Summary

   The document defines a Transport Security Model for the Simple
   Network Management Protocol (SNMP) for use with secure Transport
   Models in the Transport Subsystem. The document also defines a
   portion of the Management Information Base (MIB) for monitoring and
   managing the Transport Security Model for SNMP.

Working Group Summary

   The document did stabilize several revisions ago and has mainly
   been updated recently to track clarifications. There has been WG
   consensus on revision 12 of this document and there were no
   controversies on the technical solution since the IETF meeting in
   Dublin.

Document Quality

   There are two known implementations in progress of the Transport
   Security Model. A concrete SSH subsystem has been worked out by the
   ISMS working group and a DTLS subsystem is in progress as an
   individual draft and it seems the Transport Security Model defined
   in this document is capable to support both secure transports.

Personnel

   The document shepherd is Juergen Schoenwaelder, and the responsible
   area director is Pasi Eronen.

RFC Editor Note

   Replace all occurrences of "SNMP-TSM-MIB" with
   "SNMP-TRANSPORT-SM-MIB" (also in the MIB module in Section 7)







From dromasca@avaya.com  Fri Apr 17 00:34:20 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47BFB3A6A4C; Fri, 17 Apr 2009 00:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.52
X-Spam-Level: 
X-Spam-Status: No, score=-2.52 tagged_above=-999 required=5 tests=[AWL=0.079,  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 X5M7zI-rRqmx; Fri, 17 Apr 2009 00:34:19 -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 03F5C3A6A26; Fri, 17 Apr 2009 00:34:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,203,1238990400"; d="scan'208";a="168185022"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 17 Apr 2009 03:35:31 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 Apr 2009 03:35:31 -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, 17 Apr 2009 09:35:15 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04015DA94B@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for April 23, 2009 Telechat 
Thread-index: Acm+22A4Hv2nJ1qcToGAcYR2BmAbgQAUljkg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <dns-dir@ietf.org>
Subject: [MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for April 23, 2009 Telechat
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2009 07:34:20 -0000

Please find below the preliminary agenda of the 4/23 telechat. Please
read and review the relevant documents, as well as the charters of the
WGs that are being brought for approval by the IESG. Comments, concerns
and questions should be sent before 4/22 COB.=20

Thanks and Regards,

Dan
=20

2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-tcpm-tcpsecure-11.txt
    Improving TCP's Robustness to Blind In-Window Attacks (Proposed
Standard) -=20
    1 of 10=20
    Note: IESG: Please read the Document Shepherd Writeup, we need to
discuss=20
    the "Updates: 793" issue.=20
    Token: Lars Eggert
  o draft-ietf-radext-design-07.txt
    RADIUS Design Guidelines (BCP) - 2 of 10=20
    Token: Dan Romascanu
  o draft-ietf-ipfix-exporting-type-03.txt
    Exporting Type Information for IPFIX Information Elements (Proposed=20
    Standard) - 3 of 10=20
    Token: Dan Romascanu
  o draft-ietf-ipfix-file-03.txt
    Specification of the IPFIX File Format (Proposed Standard) - 4 of 10

    Token: Dan Romascanu
  o draft-ietf-dime-mip6-split-16.txt
    Diameter Mobile IPv6: Support for Home Agent to Diameter Server
Interaction=20
    (Proposed Standard) - 5 of 10=20
    Token: Dan Romascanu
  o draft-ietf-netlmm-grekey-option-06.txt
    GRE Key Option for Proxy Mobile IPv6 (Proposed Standard) - 6 of 10=20
    Token: Jari Arkko
  o draft-ietf-dhc-container-opt-05.txt
    Container Option for Server Configuration (Proposed Standard) - 7 of
10=20
    Token: Jari Arkko
  o draft-ietf-pkix-3281update-04.txt
    An Internet Attribute Certificate Profile for Authorization
(Proposed

    Standard) - 8 of 10=20
    Token: Tim Polk
  o draft-ietf-dccp-serv-codes-08.txt
    The DCCP Service Code (Proposed Standard) - 9 of 10=20
    Token: Lars Eggert
  o rfc3852.txt
    Cryptographic Message Syntax (CMS) (Draft Standard) - 10 of 10=20
    Token: Tim Polk

2.1.2 Returning Item
  o draft-ietf-geopriv-radius-lo-23.txt
    Carrying Location Objects in RADIUS and Diameter (Proposed Standard)
-
1 of=20
    1=20
    Note: Did new LC because previous one did not mention DOWNREF.=20
    Token: Cullen Jennings


2.2 Individual Submissions
2.2.1 New Item
  o draft-atlas-icmp-unnumbered-06.txt
    Extending ICMP for Interface and Next-hop Identification (Proposed=20
    Standard) - 1 of 1=20
    Token: Jari Arkko

2.2.2 Returning Item
NONE

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.1.1 New Item
  o draft-ietf-tcpm-ecnsyn-08.txt
    Adding Explicit Congestion Notification (ECN) Capability to TCP's
SYN/ACK=20
    Packets (Experimental) - 1 of 3=20
    Token: Lars Eggert
  o draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt
    OSPFv2 Routing Protocols Extensions for ASON Routing (Experimental)
-
2 of=20
    3=20
    Token: Adrian Farrel
  o draft-ietf-pana-statemachine-10.txt
    State Machines for Protocol for Carrying Authentication for Network
Access=20
    (PANA) (Informational) - 3 of 3=20
    Token: Jari Arkko

3.1.2 Returning Item
NONE

3.2 Individual Submissions Via AD
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.2.1 New Item
NONE
3.2.2 Returning Item
NONE
3.3 Independent Submissions Via RFC Editor
	The IESG will use RFC 3932 responses: 1) The IESG has not
	found any conflict between this document and IETF work; 2) The
	IESG thinks that this work is related to IETF work done in WG
	<X>, but this does not prevent publishing; 3) The IESG thinks
	that publication is harmful to work in WG <X> and recommends
	not publishing at this time; 4) The IESG thinks that this
	document violates the IETF procedures for <X> and should
	therefore not be published without IETF review and IESG
	approval; 5) The IESG thinks that this document extends an
	IETF protocol in a way that requires IETF review and should
	therefore not be published without IETF review and IESG
approval.

	The document shepherd must propose one of these responses in
	the Data Tracker note and supply complete text in the IESG
	Note portion of the write-up. The Area Director ballot positions
	indicate consensus with the response proposed by the
	document shepherd.

	Other matters may be recorded in comments, and the comments will
	be passed on to the RFC Editor as community review of the
document.


3.3.1 New Item
NONE
3.3.2 Returning Item
  o draft-lochter-pkix-brainpool-ecc-03.txt
    ECC Brainpool Standard Curves and Curve Generation (Informational) -
1
of 2=20
    Note: waiting for confirmation that no IPR disclosure is needed.=20
    Token: Tim Polk
  o draft-bberry-rfc4938bis-00.txt
    PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link
Metrics

    (Informational) - 2 of 2=20
    Token: Jari Arkko


4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
  o Open Web authentication (oauth) - 1 of 1
    Token: Lisa Dusseault
4.1.2 Proposed for Approval
  o Multiple Interfaces (mif) - 1 of 3
    Token: Jari Arkko
  o Locator/ID Separation Protocol (lisp) - 2 of 3
    Token: Jari Arkko
  o Network-Based Mobility Extensions (netext) - 3 of 3
    Token: Jari Arkko
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
    NONE
4.2.2 Proposed for Approval
    NONE



From dromasca@avaya.com  Mon Apr 20 09:37:46 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09E7E3A6A34 for <mib-doctors@core3.amsl.com>; Mon, 20 Apr 2009 09:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  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 QeD8vyPz1b-5 for <mib-doctors@core3.amsl.com>; Mon, 20 Apr 2009 09:37:45 -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 2033E3A6D01 for <mib-doctors@ietf.org>; Mon, 20 Apr 2009 09:37:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,218,1238990400"; d="scan'208";a="168427582"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 20 Apr 2009 12:39:00 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 20 Apr 2009 12:39:00 -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: Mon, 20 Apr 2009 18:38:43 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04015DAF66@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Evaluation: draft-ietf-mpls-p2mp-te-mib-09.txt to Proposed Standard 
Thread-Index: AcnB1SrZeHDtTBgHQOKUXwkCzKAUhgAAK0Hw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Joan Cucchiara" <jcucchiara@mindspring.com>
Cc: mib-doctors@ietf.org
Subject: [MIB-DOCTORS] FW: Evaluation: draft-ietf-mpls-p2mp-te-mib-09.txt to Proposed Standard
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Apr 2009 16:37:46 -0000

 Joan,

This document will be on the agenda of the IESG telechat on 5/7. You
already performed an early MIB Doctor review on this document. Can you
check that your comments were considered and whether the last versions
did not introduce any new problems?=20

Thanks and Regards,

Dan



A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-te-mib-09.txt

Technical Summary

   This memo describes managed objects for point-to-multipoint (P2MP)
   Multiprotocol Label Switching (MPLS) based traffic engineering (TE).

   The MIB module defined in this document is applicable to P2MP MPLS-TE
   by extensions to the MPLS-TE MIB module defined in RFC 3812. It is
   equally applicable to P2MP Generalized MPLS (GMPLS) in association
   with the GMPLS TE MIB module defined in RFC 4802.

Working Group Summary

   No dissent reported (see PROTO writeup by Loa Andersson in the
   tracker).=20

Document Quality

   No existing implementations of this MIB. The document has
   been updated based on early MIB doctor review by Joan Cucchiara
   as well as WG and IETF Last call comments. Several key reviewers
   work at companies where implementation of such a MIB module is=20
   on the roadmap.

Personnel

   Loa Andersson is the Document Shepherd for this document. =20
   Ross Callon is the Responsible Area Director. Adrian=20
   Farrel is document editor.=20

RFC Editor Note

  (Insert RFC Editor Note here or remove section)

IRTF Note

  (Insert IRTF Note here or remove section)

IESG Note

  (Insert IESG Note here or remove section)

IANA Note

  (Insert IANA Note here or remove section)







From jcucchiara@mindspring.com  Tue Apr 21 09:21:54 2009
Return-Path: <jcucchiara@mindspring.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB63F3A6B8F for <mib-doctors@core3.amsl.com>; Tue, 21 Apr 2009 09:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.494
X-Spam-Level: 
X-Spam-Status: No, score=-1.494 tagged_above=-999 required=5 tests=[AWL=1.104,  BAYES_00=-2.599, STOX_REPLY_TYPE=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 kw14CuEHeNQr for <mib-doctors@core3.amsl.com>; Tue, 21 Apr 2009 09:21:54 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by core3.amsl.com (Postfix) with ESMTP id F19DE28C28C for <mib-doctors@ietf.org>; Tue, 21 Apr 2009 09:21:53 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=LeiTEwXNepCjntKYZ3o1tOtbG7aeV7FlREgqk9QGfaw6bHQCHJy9fDlKQKrUa4u6; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [141.154.114.79] (helo=JoanPC) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1LwIkY-0006DL-65; Tue, 21 Apr 2009 12:23:10 -0400
Message-ID: <02e101c9c29d$77961bb0$6401a8c0@JoanPC>
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A04015DAF66@307622ANEX5.global.avaya.com>
Date: Tue, 21 Apr 2009 12:23:12 -0400
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e26545988e05e688f108d5984b74c6a30d05019c9e15d1c7c699c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 141.154.114.79
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] Evaluation: draft-ietf-mpls-p2mp-te-mib-09.txt to Proposed Standard
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2009 16:21:54 -0000

Hi Dan,

Yes, I can check.

When do you want comments by?  (I assume sometime before
the telechat, but how soon before?)

Thanks,
  -Joan

----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Joan Cucchiara" <jcucchiara@mindspring.com>
Cc: <mib-doctors@ietf.org>
Sent: Monday, April 20, 2009 12:38 PM
Subject: FW: Evaluation: draft-ietf-mpls-p2mp-te-mib-09.txt to Proposed 
Standard


Joan,

This document will be on the agenda of the IESG telechat on 5/7. You
already performed an early MIB Doctor review on this document. Can you
check that your comments were considered and whether the last versions
did not introduce any new problems?

Thanks and Regards,

Dan



A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-te-mib-09.txt

Technical Summary

   This memo describes managed objects for point-to-multipoint (P2MP)
   Multiprotocol Label Switching (MPLS) based traffic engineering (TE).

   The MIB module defined in this document is applicable to P2MP MPLS-TE
   by extensions to the MPLS-TE MIB module defined in RFC 3812. It is
   equally applicable to P2MP Generalized MPLS (GMPLS) in association
   with the GMPLS TE MIB module defined in RFC 4802.

Working Group Summary

   No dissent reported (see PROTO writeup by Loa Andersson in the
   tracker).

Document Quality

   No existing implementations of this MIB. The document has
   been updated based on early MIB doctor review by Joan Cucchiara
   as well as WG and IETF Last call comments. Several key reviewers
   work at companies where implementation of such a MIB module is
   on the roadmap.

Personnel

   Loa Andersson is the Document Shepherd for this document.
   Ross Callon is the Responsible Area Director. Adrian
   Farrel is document editor.

RFC Editor Note

  (Insert RFC Editor Note here or remove section)

IRTF Note

  (Insert IRTF Note here or remove section)

IESG Note

  (Insert IESG Note here or remove section)

IANA Note

  (Insert IANA Note here or remove section)







From dromasca@avaya.com  Tue Apr 21 09:24:56 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A41328C2A6 for <mib-doctors@core3.amsl.com>; Tue, 21 Apr 2009 09:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081,  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 XYOQF-Lw9kFJ for <mib-doctors@core3.amsl.com>; Tue, 21 Apr 2009 09:24:55 -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 9BF503A6E04 for <mib-doctors@ietf.org>; Tue, 21 Apr 2009 09:24:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,225,1238990400"; d="scan'208";a="168564925"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 21 Apr 2009 12:25:54 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 21 Apr 2009 12:25: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: Tue, 21 Apr 2009 18:25:32 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04015DB30C@307622ANEX5.global.avaya.com>
In-Reply-To: <02e101c9c29d$77961bb0$6401a8c0@JoanPC>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Evaluation: draft-ietf-mpls-p2mp-te-mib-09.txt to Proposed Standard 
Thread-Index: AcnCnXl1LH6j7WmtRLmXgq3PrqE67QAAEW4g
References: <EDC652A26FB23C4EB6384A4584434A04015DAF66@307622ANEX5.global.avaya.com> <02e101c9c29d$77961bb0$6401a8c0@JoanPC>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Joan Cucchiara" <jcucchiara@mindspring.com>
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] Evaluation: draft-ietf-mpls-p2mp-te-mib-09.txt to Proposed Standard
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2009 16:24:56 -0000

Thank you. Two or three days before the telechat would be fine - so to
allow the authors the time to consider and responds to your comments if
any.=20

 Regards,

Dan
=20

> -----Original Message-----
> From: Joan Cucchiara [mailto:jcucchiara@mindspring.com]=20
> Sent: Tuesday, April 21, 2009 7:23 PM
> To: Romascanu, Dan (Dan)
> Cc: mib-doctors@ietf.org
> Subject: Re: Evaluation: draft-ietf-mpls-p2mp-te-mib-09.txt=20
> to Proposed Standard=20
>=20
>=20
> Hi Dan,
>=20
> Yes, I can check.
>=20
> When do you want comments by?  (I assume sometime before the=20
> telechat, but how soon before?)
>=20
> Thanks,
>   -Joan
>=20
> ----- Original Message -----
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: "Joan Cucchiara" <jcucchiara@mindspring.com>
> Cc: <mib-doctors@ietf.org>
> Sent: Monday, April 20, 2009 12:38 PM
> Subject: FW: Evaluation: draft-ietf-mpls-p2mp-te-mib-09.txt=20
> to Proposed Standard
>=20
>=20
> Joan,
>=20
> This document will be on the agenda of the IESG telechat on=20
> 5/7. You already performed an early MIB Doctor review on this=20
> document. Can you check that your comments were considered=20
> and whether the last versions did not introduce any new problems?
>=20
> Thanks and Regards,
>=20
> Dan
>=20
>=20
>=20
> A URL of this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-te-mib-09.txt
>=20
> Technical Summary
>=20
>    This memo describes managed objects for point-to-multipoint (P2MP)
>    Multiprotocol Label Switching (MPLS) based traffic=20
> engineering (TE).
>=20
>    The MIB module defined in this document is applicable to=20
> P2MP MPLS-TE
>    by extensions to the MPLS-TE MIB module defined in RFC 3812. It is
>    equally applicable to P2MP Generalized MPLS (GMPLS) in association
>    with the GMPLS TE MIB module defined in RFC 4802.
>=20
> Working Group Summary
>=20
>    No dissent reported (see PROTO writeup by Loa Andersson in the
>    tracker).
>=20
> Document Quality
>=20
>    No existing implementations of this MIB. The document has
>    been updated based on early MIB doctor review by Joan Cucchiara
>    as well as WG and IETF Last call comments. Several key reviewers
>    work at companies where implementation of such a MIB module is
>    on the roadmap.
>=20
> Personnel
>=20
>    Loa Andersson is the Document Shepherd for this document.
>    Ross Callon is the Responsible Area Director. Adrian
>    Farrel is document editor.
>=20
> RFC Editor Note
>=20
>   (Insert RFC Editor Note here or remove section)
>=20
> IRTF Note
>=20
>   (Insert IRTF Note here or remove section)
>=20
> IESG Note
>=20
>   (Insert IESG Note here or remove section)
>=20
> IANA Note
>=20
>   (Insert IANA Note here or remove section)
>=20
>=20
>=20
>=20
>=20
>=20
>=20
