
From dromasca@avaya.com  Thu Aug  4 22:22:28 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0426C21F8A51; Thu,  4 Aug 2011 22:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.431
X-Spam-Level: 
X-Spam-Status: No, score=-103.431 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gset1T2Oge8; Thu,  4 Aug 2011 22:22:27 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id E2DB021F8A4F; Thu,  4 Aug 2011 22:22:26 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAFN9O07GmAcF/2dsb2JhbABChEeiMXd3gUABAQEBAxIGCw0EUQYBCA0IAgMCBgYMCwECAgMBRAcBAQUEAQQBEggarH0Cik+RPIErhAsxXwSYJYtD
X-IronPort-AV: E=Sophos;i="4.67,321,1309752000"; d="scan'208";a="295397196"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 05 Aug 2011 01:22:42 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 05 Aug 2011 01:19:48 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Fri, 5 Aug 2011 07:22:39 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0403774FEB@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for the August 11, 2011 IESG Teleconference 
Thread-Index: AcxS+Km6RbnadWQnSwSsJ6TQqXwHvAANlg1Q
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, <aaa-doctors@ietf.org>, <mib-doctors@ietf.org>, "YANG Doctors" <yang-doctors@ietf.org>, "IETF DNS Directorate" <dns-dir@ietf.org>
Subject: [MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for the August 11, 2011 IESG Teleconference
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 05 Aug 2011 05:22:28 -0000

UGxlYXNlIGZpbmQgYmVsb3cgdGhlIHByZWxpbWluYXJ5IGFnZW5kYSBvZiB0aGUgOC8xNCB0ZWxl
Y2hhdC4gUGxlYXNlIHNlbmQgbWUgeW91ciBxdWVzdGlvbnMsIGNvbW1lbnRzIGFuZCBjb25jZXJu
cyBiZWZvcmUgOC8xMyBDT0IuIA0KDQpUaGFua3MgYW5kIFJlZ2FyZHMsDQoNCkRhbg0KDQoNCg0K
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGllc2ctYm91bmNlc0BpZXRmLm9yZyBb
bWFpbHRvOmllc2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIElFU0cgU2VjcmV0YXJ5
DQpTdWJqZWN0OiBQUkVMSU1JTkFSWSBBZ2VuZGEgYW5kIFBhY2thZ2UgZm9yIHRoZSBBdWd1c3Qg
MTEsIDIwMTEgSUVTRyBUZWxlY29uZmVyZW5jZSANCg0KLi4uDQoNCjIuIFByb3RvY29sIEFjdGlv
bnMNCjIuMSBXRyBTdWJtaXNzaW9ucw0KMi4xLjEgTmV3IEl0ZW1zDQoNCiAgbyBkcmFmdC1pZXRm
LW1wbHMtcDJtcC1sc3AtcGluZy0xNw0KICAgIERldGVjdGluZyBEYXRhIFBsYW5lIEZhaWx1cmVz
IGluIFBvaW50LXRvLU11bHRpcG9pbnQgTXVsdGlwcm90b2NvbA0KICAgIExhYmVsIFN3aXRjaGlu
ZyAoTVBMUykgLSBFeHRlbnNpb25zIHRvIExTUCBQaW5nIChQcm9wb3NlZCBTdGFuZGFyZCkNCiAg
ICBOb3RlOiBSb3NzIENhbGxvbiAocmNhbGxvbkBqdW5pcGVyLm5ldCkgaXMgdGhlIGRvY3VtZW50
IHNoZXBoZXJkLg0KICAgIFRva2VuOiBTdGV3YXJ0IEJyeWFudA0KDQogIG8gZHJhZnQtaWV0Zi1t
cGxzLWxzcC1waW5nLWVuaGFuY2VkLWRzbWFwLTEwDQogICAgTWVjaGFuaXNtIGZvciBwZXJmb3Jt
aW5nIExTUC1QaW5nIG92ZXIgTVBMUyB0dW5uZWxzIChQcm9wb3NlZA0KICAgIFN0YW5kYXJkKQ0K
ICAgIE5vdGU6IFJvc3MgQ2FsbG9uIChyY2FsbG9uQGp1bmlwZXIubmV0KSBpcyB0aGUgZG9jdW1l
bnQgc2hlcGhlcmQuDQogICAgVG9rZW46IFN0ZXdhcnQgQnJ5YW50DQoNCiAgbyBkcmFmdC1pZXRm
LWJlaGF2ZS1mdHA2NC0xMg0KICAgIEFuIEZUUCBBTEcgZm9yIElQdjYtdG8tSVB2NCB0cmFuc2xh
dGlvbiAoUHJvcG9zZWQgU3RhbmRhcmQpDQogICAgTm90ZTogRGFuIFdpbmcgKGR3aW5nQGNpc2Nv
LmNvbSkgaXMgdGhlIGRvY3VtZW50IHNoZXBoZXJkLg0KICAgIFRva2VuOiBEYXZpZCBIYXJyaW5n
dG9uDQoNCiAgbyBkcmFmdC1pZXRmLWNjYW1wLWFzeW1tLWJ3LWJpZGlyLWxzcHMtYmlzLTAyDQog
ICAgR01QTFMgQXN5bW1ldHJpYyBCYW5kd2lkdGggQmlkaXJlY3Rpb25hbCBMYWJlbCBTd2l0Y2hl
ZCBQYXRocyAoTFNQcykNCiAgICAoUHJvcG9zZWQgU3RhbmRhcmQpDQogICAgTm90ZTogRGVib3Jh
aCBCcmluZ2VyIChkYjM1NDZAYXR0LmNvbSkgaXMgdGhlIERvY3VtZW50DQogICAgU2hlcGhlcmQu
DQogICAgVG9rZW46IEFkcmlhbiBGYXJyZWwNCg0KICBvIGRyYWZ0LWlldGYtcm9sbC1vZjAtMTUN
CiAgICBSUEwgT2JqZWN0aXZlIEZ1bmN0aW9uIFplcm8gKFByb3Bvc2VkIFN0YW5kYXJkKQ0KICAg
IE5vdGU6IEpQIFZhc3NldXIgKGpwdkBjaXNjby5jb20pIGlzIHRoZSBkb2N1bWVudCBzaGVwaGVy
ZC4NCiAgICBUb2tlbjogQWRyaWFuIEZhcnJlbA0KDQogIG8gZHJhZnQtaWV0Zi1tcGxzLW1sZHAt
cmVjdXJzLWZlYy0wNA0KICAgIFVzaW5nIE11bHRpcG9pbnQgTERQIHdoZW4gdGhlIEJhY2tib25l
IGhhcyBubyBSb3V0ZSB0byB0aGUgUm9vdA0KICAgIChQcm9wb3NlZCBTdGFuZGFyZCkNCiAgICBO
b3RlOiBMb2EgQW5kZXJzc29uIChsb2FAcGkubnUpIGlzIHRoZSBEb2N1bWVudCBTaGVwaGVyZC4N
CiAgICBUb2tlbjogQWRyaWFuIEZhcnJlbA0KDQogIG8gZHJhZnQtaWV0Zi1zb2Z0d2lyZS1kc2xp
dGUtcmFkaXVzLWV4dC0wNA0KICAgIFJBRElVUyBFeHRlbnNpb25zIGZvciBEdWFsLVN0YWNrIExp
dGUgKFByb3Bvc2VkIFN0YW5kYXJkKQ0KICAgIE5vdGU6IFlvbmcgQ3VpIChjdWl5b25nQHRzaW5n
aHVhLmVkdS5jbikgaXMgdGhlIGRvY3VtZW50IHNoZXBoZXJkLg0KICAgIFRva2VuOiBSYWxwaCBE
cm9tcw0KDQogIG8gZHJhZnQtaWV0Zi1tc2VjLWdkb2ktdXBkYXRlLTA5DQogICAgVGhlIEdyb3Vw
IERvbWFpbiBvZiBJbnRlcnByZXRhdGlvbiAoUHJvcG9zZWQgU3RhbmRhcmQpDQogICAgTm90ZTog
VmluY2VudCBSb2NhICh2aW5jZW50LnJvY2FAaW5yaWEuZnIpIGlzIHRoZSBzaGVwaGVyZC4NCiAg
ICBUb2tlbjogU2VhbiBUdXJuZXINCg0KMi4xLjIgUmV0dXJuaW5nIEl0ZW1zDQoNCiAgTk9ORQ0K
DQoyLjIgSW5kaXZpZHVhbCBTdWJtaXNzaW9ucw0KMi4yLjEgTmV3IEl0ZW1zDQoNCiAgbyBkcmFm
dC1ndXRtYW5uLWNtcy1obWFjLWVuYy0wNQ0KICAgIFVzaW5nIE1BQy1hdXRoZW50aWNhdGVkIEVu
Y3J5cHRpb24gaW4gdGhlIENyeXB0b2dyYXBoaWMgTWVzc2FnZQ0KICAgIFN5bnRheCAoQ01TKSAo
UHJvcG9zZWQgU3RhbmRhcmQpDQogICAgTm90ZTogUGV0ZXIgR3V0bWFubiAocGd1dDAwMUBjcy5h
dWNrbGFuZC5hYy5ueikgaXMgdGhlIERvY3VtZW50DQogICAgU2hlcGhlcmQuDQogICAgVG9rZW46
IFNlYW4gVHVybmVyDQoNCjIuMi4yIFJldHVybmluZyBJdGVtcw0KDQogIE5PTkUNCg0KMy4gRG9j
dW1lbnQgQWN0aW9ucw0KMy4xIFdHIFN1Ym1pc3Npb25zDQozLjEuMSBOZXcgSXRlbXMNCg0KICBv
IGRyYWZ0LWlldGYtdHN2d2ctcnN2cC1zZWN1cml0eS1ncm91cGtleWluZy0xMA0KICAgIEFwcGxp
Y2FiaWxpdHkgb2YgS2V5aW5nIE1ldGhvZHMgZm9yIFJTVlAgU2VjdXJpdHkgKEluZm9ybWF0aW9u
YWwpDQogICAgTm90ZTogSmFtZXMgUG9sayAoam1wb2xrQGNpc2NvLmNvbSkgaXMgdGhlIERvY3Vt
ZW50IFNoZXBoZXJkLg0KICAgIFRva2VuOiBEYXZpZCBIYXJyaW5ndG9uDQoNCiAgbyBkcmFmdC1p
ZXRmLWRlY2FkZS1zdXJ2ZXktMDUNCiAgICBBIFN1cnZleSBvZiBJbi1uZXR3b3JrIFN0b3JhZ2Ug
U3lzdGVtcyAoSW5mb3JtYXRpb25hbCkNCiAgICBOb3RlOiBIYWliaW4gU29uZyAoaGFpYmluLnNv
bmdAaHVhd2VpLmNvbSkgaXMgdGhlIGRvY3VtZW50IHNoZXBoZXJkLg0KICAgIFRva2VuOiBEYXZp
ZCBIYXJyaW5ndG9uDQoNCiAgbyBkcmFmdC1pZXRmLW9wc2F3Zy1vYW0tb3ZlcnZpZXctMDUNCiAg
ICBBbiBPdmVydmlldyBvZiBPcGVyYXRpb25zLCBBZG1pbmlzdHJhdGlvbiwgYW5kIE1haW50ZW5h
bmNlIChPQU0pDQogICAgTWVjaGFuaXNtcyAoSW5mb3JtYXRpb25hbCkNCiAgICBOb3RlOiBTY290
dCBCcmFkbmVyIChzb2JAaGFydmFyZC5lZHUpIGlzIHRoZSBEb2N1bWVudCBTaGVwaGVyZC4NCiAg
ICBUb2tlbjogUm9uIEJvbmljYQ0KDQozLjEuMiBSZXR1cm5pbmcgSXRlbXMNCg0KICBOT05FDQoN
CjMuMiBJbmRpdmlkdWFsIFN1Ym1pc3Npb25zIFZpYSBBRA0KMy4yLjEgTmV3IEl0ZW1zDQoNCiAg
byBkcmFmdC1zaGlvbW90by1jY2FtcC1zd2l0Y2gtcHJvZ3JhbW1pbmctMDUNCiAgICBBZHZpY2Ug
b24gV2hlbiBJdCBpcyBTYWZlIHRvIFN0YXJ0IFNlbmRpbmcgRGF0YSBvbiBMYWJlbCBTd2l0Y2hl
ZA0KICAgIFBhdGhzIEVzdGFibGlzaGVkIFVzaW5nIFJTVlAtVEUgKEluZm9ybWF0aW9uYWwpDQog
ICAgTm90ZTogRGFuaWVsIEtpbmcgKGRhbmllbEBvbGRkb2cuY28udWspIGlzIHRoZSBEb2N1bWVu
dCBTaGVwaGVyZC4NCiAgICBUb2tlbjogU3Rld2FydCBCcnlhbnQNCg0KICBvIGRyYWZ0LWJ1cmdp
bi1pcHNlYy1zdWl0ZWItcHJvZmlsZS0wMQ0KICAgIFN1aXRlIEIgUHJvZmlsZSBmb3IgSW50ZXJu
ZXQgUHJvdG9jb2wgU2VjdXJpdHkgKElQc2VjKQ0KICAgIChJbmZvcm1hdGlvbmFsKQ0KICAgIE5v
dGU6IFBhdWwgSG9mZm1hbiAocGF1bC5ob2ZmbWFuQHZwbmMub3JnKSBpcyB0aGUgZG9jdW1lbnQg
c2hlcGhlcmQuDQogICAgVG9rZW46IFNlYW4gVHVybmVyDQoNCiAgbyBkcmFmdC1sYXctcmZjNDg2
OWJpcy0wMQ0KICAgIFN1aXRlIEIgQ3J5cHRvZ3JhcGhpYyBTdWl0ZXMgZm9yIElQc2VjIChJbmZv
cm1hdGlvbmFsKQ0KICAgIE5vdGU6IFBhdWwgSG9mZm1hbiAocGF1bC5ob2ZmbWFuQHZwbmMub3Jn
KSBpcyB0aGUgZG9jdW1lbnQgc2hlcGhlcmQuDQogICAgVG9rZW46IFNlYW4gVHVybmVyDQoNCiAg
byBkcmFmdC1mb3J0ZS1sb3N0LWV4dGVuc2lvbnMtMDcNCiAgICBMb2NhdGlvbi10by1TZXJ2aWNl
IFRyYW5zbGF0aW9uIChMb1NUKSBQcm90b2NvbCBFeHRlbnNpb25zDQogICAgKEV4cGVyaW1lbnRh
bCkNCiAgICBOb3RlOiBSaWNoYXJkIEJhcm5lcyAocmJhcm5lc0BiYm4uY29tKSBpcyB0aGUgZG9j
dW1lbnQgc2hlcGhlcmQuDQogICAgVG9rZW46IFJvYmVydCBTcGFya3MNCg0KMy4yLjIgUmV0dXJu
aW5nIEl0ZW1zDQoNCiAgTk9ORQ0KDQozLjMgSVJURiBhbmQgSW5kZXBlbmRlbnQgU3VibWlzc2lv
biBTdHJlYW0gRG9jdW1lbnRzDQozLjMuMSBOZXcgSXRlbXMNCg0KICBvIGRyYWZ0LXNpbXBzb24t
aXNpcy1wcHAtdW5pcXVlLTAxDQogICAgR2VuZXJhdGlvbiBvZiBVbmlxdWUgSVMtSVMgU3lzdGVt
IElkZW50aWZpZXJzIChFeHBlcmltZW50YWwpDQogICAgTm90ZTogSVNFIFN1Ym1pc3Npb24NCiAg
ICBUb2tlbjogU3Rld2FydCBCcnlhbnQNCg0KMy4zLjIgUmV0dXJuaW5nIEl0ZW1zDQoNCiAgTk9O
RQ0KDQo0LiBXb3JraW5nIEdyb3VwIEFjdGlvbnMNCjQuMSBXRyBDcmVhdGlvbg0KNC4xLjEgUHJv
cG9zZWQgZm9yIElFVEYgUmV2aWV3DQoNCiAgTk9ORQ0KDQo0LjEuMiBQcm9wb3NlZCBmb3IgQXBw
cm92YWwNCg0KICBOT05FDQoNCjQuMiBXRyBSZWNoYXJ0ZXJpbmcNCjQuMi4xIFVuZGVyIEV2YWx1
YXRpb24gZm9yIElFVEYgUmV2aWV3DQoNCiAgbyBQYXRoIENvbXB1dGF0aW9uIEVsZW1lbnQgKHBj
ZSkNCiAgICBUb2tlbjogQWRyaWFuDQoNCiAgbyB2Q2FyZCBhbmQgQ2FyZERBViAodmNhcmRkYXYp
DQogICAgVG9rZW46IFBldGVyDQoNCg0K

From dromasca@avaya.com  Thu Aug 11 05:26:29 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6383221F86C0 for <mib-doctors@ietfa.amsl.com>; Thu, 11 Aug 2011 05:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.931
X-Spam-Level: 
X-Spam-Status: No, score=-102.931 tagged_above=-999 required=5 tests=[AWL=-0.332, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z-znj3+CsFPe for <mib-doctors@ietfa.amsl.com>; Thu, 11 Aug 2011 05:26:28 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id B94F021F86BF for <mib-doctors@ietf.org>; Thu, 11 Aug 2011 05:26:28 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsgHABDJQ06HCzI1/2dsb2JhbABBmEGPBXeBQgEBAxIeCj8SARUVBgwMB1cBBBsBGYdRoHwCnCKFaF8EmDeLSA
X-IronPort-AV: E=Sophos;i="4.67,355,1309752000"; d="scan'208";a="201341144"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 11 Aug 2011 08:26:56 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 11 Aug 2011 08:18: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: Thu, 11 Aug 2011 14:26:47 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04037E1827@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Volunteer needed to review draft-ietf-trill-rbridge-mib-03
Thread-Index: AcxYIfCLyF4rQLPWRxKLbU+p6t8aXA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <mib-doctors@ietf.org>
Cc: Ralph Droms <rdroms.ietf@gmail.com>
Subject: [MIB-DOCTORS] Volunteer needed to review draft-ietf-trill-rbridge-mib-03
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Aug 2011 12:26:29 -0000

MIB-Doctors,

We need a volunteer to review
http://www.ietf.org/id/draft-ietf-trill-rbridge-mib-03.txt. The document
is co-authored by Anil Rijhsinghani (author of the original Bridge MIB)
and looks in pretty good shape.=20

Thanks and Regards,

Dan





From macfaden@gmail.com  Mon Aug 15 16:06:00 2011
Return-Path: <macfaden@gmail.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A67811E8089 for <mib-doctors@ietfa.amsl.com>; Mon, 15 Aug 2011 16:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JSENMajd5Tj5 for <mib-doctors@ietfa.amsl.com>; Mon, 15 Aug 2011 16:05:59 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 360AB11E8086 for <mib-doctors@ietf.org>; Mon, 15 Aug 2011 16:05:59 -0700 (PDT)
Received: by wwf5 with SMTP id 5so3581438wwf.13 for <mib-doctors@ietf.org>; Mon, 15 Aug 2011 16:06:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=KrwRjpL9Gx0iTMJBdb8ptGgjcS7LI5sCgvg5z9E+eB8=; b=lH9GhJL19hoF3FF3UvCoFVqkPfaLWlPvqBqi2uqjiuEmsPEtbrWiHC04UkK+3BHlOq 9ADWhiMmxtCMO5wns602uU/ATiTzSfHIMmU87I5vCUe1w02K1jVCB4u2OLZBco6aR++C UTGqysu8wMFjq4Wex5awNG92h79V/QBkJTQRI=
MIME-Version: 1.0
Received: by 10.216.67.143 with SMTP id j15mr3681920wed.110.1313449605217; Mon, 15 Aug 2011 16:06:45 -0700 (PDT)
Sender: macfaden@gmail.com
Received: by 10.216.169.82 with HTTP; Mon, 15 Aug 2011 16:06:45 -0700 (PDT)
Date: Mon, 15 Aug 2011 16:06:45 -0700
X-Google-Sender-Auth: Pzx76L9AxzSH68yS-5Jg7vp03jk
Message-ID: <CAD3a8TkBxG+ZgzL1DnMo2ziaSChLKWNNmGT=1hhK7AMVUzaUPg@mail.gmail.com>
From: Michael MacFaden <mrm@macfaden.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: [MIB-DOCTORS] Questions on IEEE published mib modules vs IETF
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Aug 2011 23:07:27 -0000

Hi Dan,

Can you or someone on this list explain what's the equivalent of the
IETF maturity level for
IEEE mib modules?  Specifically those found here:
http://www.ieee802.org/1/files/public/MIBs

For example am looking at  IEEE8023-LAG-MIB which doesn't match the one in this
spec so am curious when it would be updated. The changes appear to be
fixed REFERENCES only.
http://standards.ieee.org/getieee802/download/802.1AX-2008.pdf

Lastly, are these IETF mib modules going to deprecated/moved to IEEE?
EtherLike-MIB/3635 and MAU-MIB/4836.

Thanks
Mike MacFaden

From dromasca@avaya.com  Wed Aug 17 08:36:08 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 786A921F8B9A; Wed, 17 Aug 2011 08:36:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.419
X-Spam-Level: 
X-Spam-Status: No, score=-103.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EeznsMvwhYeG; Wed, 17 Aug 2011 08:36:07 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 3B01D21F8B92; Wed, 17 Aug 2011 08:36:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjoBALXeS06HCzI1/2dsb2JhbABCmRODa4tsd4FAAQEBAQECEh4KPwwEAgEIDQQEAQELBgwLAQYBICUJCAEBBBMIGodSmSACnDyFaV8EmD2ETIcB
X-IronPort-AV: E=Sophos;i="4.68,240,1312171200"; d="scan'208";a="262736143"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 17 Aug 2011 11:36:57 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 17 Aug 2011 11:28:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Aug 2011 17:36:54 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040385FCAA@307622ANEX5.global.avaya.com>
In-Reply-To: <CAD3a8TkBxG+ZgzL1DnMo2ziaSChLKWNNmGT=1hhK7AMVUzaUPg@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Questions on IEEE published mib modules vs IETF
Thread-Index: AcxboAJeFi6hDNAZQ/KJ8ABDeQ7XBQBUEZhg
References: <CAD3a8TkBxG+ZgzL1DnMo2ziaSChLKWNNmGT=1hhK7AMVUzaUPg@mail.gmail.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Michael MacFaden" <mrm@macfaden.com>
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Hubmib <hubmib@ietf.org>
Subject: Re: [MIB-DOCTORS] Questions on IEEE published mib modules vs IETF
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Aug 2011 15:36:08 -0000

Hi Mike,=20

I am copying hubmib as the last question refers to Ethernet MIB
documents.=20

There is no equivalent of the IETF maturity levels in the IEEE. There is
just one level of standards, and there is a re-affirmation process that
needs to happen every five years, unless the standard was updated
sooner.=20

I do not know about the LAG MIB. I think - but I am not sure - that it
is being updated. Best place to ask is the IEEE 802.3 folks - Howard
Frazier(hfrazier@broadcom.com) is a good person to start from. Howard
chairs the IEEE 802.3.1 project which is taking over the Ethernet MIB
work in the IEEE=20

The MIB modules defined in RFC 3635 and RFC 4836 (and a few more) are in
the scope of IEEE 802.3.1 which was approved as an IEEE standard a few
months ago. We entertained a discussion at and around the Quebec meeting
and decided to mark the RFCs as obsolete by the IEEE standards and point
to these, but not transit them to Historic (not yet in any case). Bert
will write when he gets some time a short Informational RFC to document
this transition.=20

I hope this helps.=20

Regards,

Dan




> -----Original Message-----
> From: macfaden@gmail.com [mailto:macfaden@gmail.com] On Behalf Of
> Michael MacFaden
> Sent: Tuesday, August 16, 2011 2:07 AM
> To: Romascanu, Dan (Dan)
> Cc: MIB Doctors (E-mail)
> Subject: Questions on IEEE published mib modules vs IETF
>=20
> Hi Dan,
>=20
> Can you or someone on this list explain what's the equivalent of the
> IETF maturity level for
> IEEE mib modules?  Specifically those found here:
> http://www.ieee802.org/1/files/public/MIBs
>=20
> For example am looking at  IEEE8023-LAG-MIB which doesn't match the
one
> in this
> spec so am curious when it would be updated. The changes appear to be
> fixed REFERENCES only.
> http://standards.ieee.org/getieee802/download/802.1AX-2008.pdf
>=20
> Lastly, are these IETF mib modules going to deprecated/moved to IEEE?
> EtherLike-MIB/3635 and MAU-MIB/4836.
>=20
> Thanks
> Mike MacFaden

From macfaden@gmail.com  Wed Aug 17 10:15:21 2011
Return-Path: <macfaden@gmail.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E847A21F8BCB; Wed, 17 Aug 2011 10:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wp1ekCAXvWR4; Wed, 17 Aug 2011 10:15:21 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8B99221F8BC4; Wed, 17 Aug 2011 10:15:15 -0700 (PDT)
Received: by wwf5 with SMTP id 5so823453wwf.13 for <multiple recipients>; Wed, 17 Aug 2011 10:16:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=1DG5POvxlB7CVAOKDB6Jmj8nbRBYW/claZu19agalIo=; b=ZVoCz/89nWE6wpzfFruN2onHd8N7OP6/AA4B/melMaTKhBVBNC7cuHz/U5vpXDJfjS AlUH26EqG5bR+mE9diHowoS+hvrTUYMQE++ik/OcfzwjISk+X2nWU0TmKOl8el1Gmrzy ickLZq6sNrS8zKujccrGNwSnR8ZlxqmKMKv5Q=
MIME-Version: 1.0
Received: by 10.216.172.69 with SMTP id s47mr4219170wel.95.1313601365038; Wed, 17 Aug 2011 10:16:05 -0700 (PDT)
Sender: macfaden@gmail.com
Received: by 10.216.169.82 with HTTP; Wed, 17 Aug 2011 10:16:04 -0700 (PDT)
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040385FCAA@307622ANEX5.global.avaya.com>
References: <CAD3a8TkBxG+ZgzL1DnMo2ziaSChLKWNNmGT=1hhK7AMVUzaUPg@mail.gmail.com> <EDC652A26FB23C4EB6384A4584434A040385FCAA@307622ANEX5.global.avaya.com>
Date: Wed, 17 Aug 2011 10:16:04 -0700
X-Google-Sender-Auth: eYQ_9Cyb3jWnMnXIhfHY1AFfD3M
Message-ID: <CAD3a8T=HEcLKf6HNmY2WxADVypQFfeQc9+mGt2fJHtYFQ5WhwQ@mail.gmail.com>
From: Michael MacFaden <mrm@macfaden.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, hubmib@ietf.org
Subject: Re: [MIB-DOCTORS] Questions on IEEE published mib modules vs IETF
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Aug 2011 17:15:22 -0000

On Wed, Aug 17, 2011 at 8:36 AM, Romascanu, Dan (Dan)
<dromasca@avaya.com> wrote:
> There is no equivalent of the IETF maturity levels in the IEEE. There is
> just one level of standards, and there is a re-affirmation process that
> needs to happen every five years, unless the standard was updated
> sooner.

Ok, that's good to know. Unfortunately there is no README.txt file at this URL
  http://www.ieee802.org/1/files/public/MIBs
to describe when files are posted here at what part of the standards
process this is/such as being up for reaffirmation. Am
going to the pdf's just to make sure.

> The MIB modules defined in RFC 3635 and RFC 4836 (and a few more) are in
> the scope of IEEE 802.3.1 which was approved as an IEEE standard a few
> months ago. We entertained a discussion at and around the Quebec meeting
> and decided to mark the RFCs as obsolete by the IEEE standards and point
> to these, but not transit them to Historic (not yet in any case). Bert
> will write when he gets some time a short Informational RFC to document
> this transition.

Makes sense to me, have already started using IEEE8021-BRIDGE-MIB,
IEEE8021-Q-BRIDGE, and others in products so would
prefer new to use correct IEEE versions when they become available.

Thanks again,
Mike MacFaden

From dromasca@avaya.com  Thu Aug 18 06:39:26 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2FFA21F8B02 for <mib-doctors@ietfa.amsl.com>; Thu, 18 Aug 2011 06:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.421
X-Spam-Level: 
X-Spam-Status: No, score=-103.421 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tKTNzz1cPnLZ for <mib-doctors@ietfa.amsl.com>; Thu, 18 Aug 2011 06:39:26 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id B20C421F8AF6 for <mib-doctors@ietf.org>; Thu, 18 Aug 2011 06:39:25 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An4CADQUTU6HCzI1/2dsb2JhbAA6CZkfil2EdXeBQAEBAQEDAQEBDx4KNAQHDAQCAQgNBAQBAQsGDAsBBgEmHwkIAQEECgkIARmHU50hApwlgyiCQV8EmD2LTQ
X-IronPort-AV: E=Sophos;i="4.68,245,1312171200"; d="scan'208";a="262945619"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 18 Aug 2011 09:40:07 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 18 Aug 2011 09:31:49 -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, 18 Aug 2011 15:40:03 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040385FE8B@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04037E1827@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] Volunteer needed to reviewdraft-ietf-trill-rbridge-mib-03
Thread-Index: AcxYIfCLyF4rQLPWRxKLbU+p6t8aXAFgDkBA
References: <EDC652A26FB23C4EB6384A4584434A04037E1827@307622ANEX5.global.avaya.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <mib-doctors@ietf.org>
Cc: rbridge@postel.org, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [MIB-DOCTORS] Volunteer needed to reviewdraft-ietf-trill-rbridge-mib-03
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 18 Aug 2011 13:39:26 -0000

Hi,

We did not receive any volunteering offers. The list is still open and
the MIB doctors are invited to step ahead.=20

Bert and me did however a quick review of the I-D. Here are our
findings. Please treat them as review comments, but keep in mind that
the list is not final and more things may accumulate.=20

I would also note that I reviewed a previous version of the MIB module
and document and made a number of comments. Not all were taken into
consideration.=20

1. The relationship with other MIB module sections refer to the IETF
RFCs. However, since 2006 the development of the Bridge MIB modules and
their successors were transferred to IEEE 802.1. I suggest to define the
relationship sections in relation to the IEEE MIB modules

2. There are several tables with read-create objects but no rowStatus
object - rbridgeBaseNicknameTable, rbridgeBasePortTable,
rbridgeVlanPortTable, etc.

3. There are several writeable objects and tables with writeable objects
but no rowStorageType or any indication about persistency

4. In several places SYNTAX of Integer32 is used for range positive
integers. RFC 4181, section 4.6.1.1 says:=20

- If the value range is between 0..4294967295 (inclusive), and values
     greater than 2147483647 are possible, and the value of the
     information being modelled does not increase above the maximum
     value nor decrease below the minimum value, then:

     - Unsigned32 is RECOMMENDED;
     - Gauge32 is acceptable;
     - INTEGER and Integer32 MUST NOT be used.

5. Use of Inter32 (0-65535) for port numbers instead of using
InetPortNumber from RFC4001

6. SMICng strict checking gives:

W: f(trill-rbridge.mi2), (46,17) The first revision should match the
last update for MODULE-IDENTITY rbridgeMIB
W: f(trill-rbridge.mi2), (299,4) Sequence "RBridgeBasePortEntry" and Row
"rbridgeBasePortEntry" should have related names
E: f(trill-rbridge.mi2), (299,4) Row "rbridgeBasePortEntry" may not have
columns with MAX-ACCESS of read-write if any column is read-create
E: f(trill-rbridge.mi2), (608,18) Index item "dot1qFdbId" must be
defined with syntax that includes a range
W: f(trill-rbridge.mi2), (810,20) Item "rbridgeMultiFibPorts" should
have SIZE specified
E: f(trill-rbridge.mi2), (838,18) Index item "dot1qVlanIndex" must be
defined with syntax that includes a range
E: f(trill-rbridge.mi2), (912,18) Index item "dot1qVlanIndex" must be
defined with syntax that includes a range
E: f(trill-rbridge.mi2), (1113,18) Index item "dot1qVlanIndex" must be
defined with syntax that includes a range
E: f(trill-rbridge.mi2), (1272,17) Index item "dot1qVlanIndex" must be
defined with syntax that includes a range
W: f(trill-rbridge.mi2), (1265,4) Row "rbridgeSnoopingAddrEntry" has
indexing that may create variables with more than 128 sub-ids
W: f(trill-rbridge.mi2), (1310,20) Item "rbridgeSnoopingAddrPorts"
should have SIZE specified
W: f(trill-rbridge.mi2), (838,18) Row "rbridgeVlanEntry" does not have a
consistent indexing scheme - index items must be in same order as used
in INDEX cl ause for "base row" dot1qVlanCurrentEntry
W: f(trill-rbridge.mi2), (912,18) Row "rbridgeVlanPortEntry" does not
have a consistent indexing scheme - cannot specify an index item from
additional "bas e row" dot1qVlanCurrentEntry, since can have only one
"base row" which is rbridgeBasePortEntry
W: f(trill-rbridge.mi2), (1113,18) Row "rbridgeEsadiEntry" does not have
a consistent indexing scheme - index items must be in same order as used
in INDEX clause for "base row" dot1qVlanCurrentEntry
W: f(trill-rbridge.mi2), (1272,17) Row "rbridgeSnoopingAddrEntry" does
not have a consistent indexing scheme - index items must be in same
order as used in  INDEX clause for "base row" dot1qVlanCurrentEntry

7. Objects like rbridgeBaseUniMultipathEnable or
rbridgeBaseMultiMultipathEnable could use the TruthValue TC as SYNTAX.

8. UNITS clauses would be useful for counter objects.

9. There is no indication about the behavior of tables that contain
counters wrt. counters discontinuity or any discontinuity indicator
objects defined. (see section 4.6.1.2 in RFC 4181 for this)


Regards,

Dan



> -----Original Message-----
> From: mib-doctors-bounces@ietf.org [mailto:mib-doctors-
> bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
> Sent: Thursday, August 11, 2011 3:27 PM
> To: mib-doctors@ietf.org
> Cc: Ralph Droms
> Subject: [MIB-DOCTORS] Volunteer needed to reviewdraft-ietf-trill-
> rbridge-mib-03
>=20
> MIB-Doctors,
>=20
> We need a volunteer to review
> http://www.ietf.org/id/draft-ietf-trill-rbridge-mib-03.txt. The
> document
> is co-authored by Anil Rijhsinghani (author of the original Bridge
MIB)
> and looks in pretty good shape.
>=20
> Thanks and Regards,
>=20
> Dan
>=20
>=20
>=20
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors

From dromasca@avaya.com  Fri Aug 19 00:48:32 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DFAA21F8581; Fri, 19 Aug 2011 00:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.835
X-Spam-Level: 
X-Spam-Status: No, score=-102.835 tagged_above=-999 required=5 tests=[AWL=-0.436, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ryTxdndqtjPl; Fri, 19 Aug 2011 00:48:31 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 75E8621F8574; Fri, 19 Aug 2011 00:48:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlwHAJwUTk7GmAcF/2dsb2JhbABBhEuXRIpzdneBQAEBAQEDEhENBFEGAQYCDQgFAgYGDAsBAgIDAR8lBwEGBAEEARIIGqRdAopQkUeBLIQMMV8EmD2ETIcB
X-IronPort-AV: E=Sophos;i="4.68,250,1312171200"; d="scan'208";a="298383456"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 19 Aug 2011 03:49:25 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 19 Aug 2011 03:45:43 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Fri, 19 Aug 2011 09:49:23 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040385FFE3@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for the August 25, 2011 IESG Teleconference 
Thread-Index: Acxd8+oZjGs6sf3ESV2HUb+wglzX6gAUEMog
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, <mib-doctors@ietf.org>, "IETF DNS Directorate" <dns-dir@ietf.org>, <ops-dir@ietf.org>, "YANG Doctors" <yang-doctors@ietf.org>
Subject: [MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for the August 25, 2011 IESG Teleconference
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 19 Aug 2011 07:48:32 -0000

UGxlYXNlIGZpbmQgYmVsb3cgdGhlIHByZWxpbWluYXJ5IGFnZW5kYSBvZiB0aGUgOC8yNSBJRVNH
IHRlbGVjaGF0LiBQbGVhc2Ugc2VuZCBtZSB5b3VyIHF1ZXN0aW9ucywgY29tbWVudHMgYW5kIGNv
bmNlcm5zIHJlbGF0ZWQgdG8gdGhlIGRvY3VtZW50cyBhbmQgV0cgY2hhcnRlcnMgb24gdGhlIGFn
ZW5kYSBiZWZvcmUgOC8yNCBDT0IuIA0KDQpUaGFua3MgYW5kIFJlZ2FyZHMsDQoNCkRhbg0KDQoN
Cg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaWVzZy1ib3VuY2VzQGlldGYu
b3JnIFttYWlsdG86aWVzZy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSUVTRyBTZWNy
ZXRhcnkNCg0KDQoNCjIuIFByb3RvY29sIEFjdGlvbnMNCjIuMSBXRyBTdWJtaXNzaW9ucw0KMi4x
LjEgTmV3IEl0ZW1zDQoNCiAgbyBkcmFmdC1pZXRmLXB3ZTMtZmF0LXB3LTA3DQogICAgRmxvdyBB
d2FyZSBUcmFuc3BvcnQgb2YgUHNldWRvd2lyZXMgb3ZlciBhbiBNUExTIFBhY2tldCBTd2l0Y2hl
ZA0KICAgIE5ldHdvcmsgKFByb3Bvc2VkIFN0YW5kYXJkKQ0KICAgIE5vdGU6IE1hdHRoZXcgQm9j
Y2kgKG1hdHRoZXcuYm9jY2lAYWxjYXRlbC1sdWNlbnQuY29tKSBpcyB0aGUNCiAgICBkb2N1bWVu
dCBzaGVwaGVyZA0KICAgIFRva2VuOiBBZHJpYW4gRmFycmVsDQoNCiAgbyBkcmFmdC1pZXRmLXNp
ZHItcmVzY2VydHMtcHJvdmlzaW9uaW5nLTEwDQogICAgQSBQcm90b2NvbCBmb3IgUHJvdmlzaW9u
aW5nIFJlc291cmNlIENlcnRpZmljYXRlcyAoUHJvcG9zZWQNCiAgICBTdGFuZGFyZCkNCiAgICBO
b3RlOiBTYW5kcmEgTXVycGh5IChTYW5kcmEuTXVycGh5QHNwYXJ0YS5jb20pIGlzIHRoZSBkb2N1
bWVudA0KICAgIHNoZXBoZXJkLg0KICAgIFRva2VuOiBTdGV3YXJ0IEJyeWFudA0KDQogIG8gZHJh
ZnQtaWV0Zi1tcGxzLXJzdnAtdGUtbm8tcGhwLW9vYi1tYXBwaW5nLTA5DQogICAgTm9uIFBlbnVs
dGltYXRlIEhvcCBQb3BwaW5nIEJlaGF2aW9yIGFuZCBvdXQtb2YtYmFuZCBtYXBwaW5nIGZvcg0K
ICAgIFJTVlAtVEUgTGFiZWwgU3dpdGNoZWQgUGF0aHMgKFByb3Bvc2VkIFN0YW5kYXJkKQ0KICAg
IE5vdGU6IE1hcnRpbiBWaWdvdXJldXggKG1hcnRpbi52aWdvdXJldXhAYWxjYXRlbC1sdWNlbnQu
Y29tKSBpcyB0aGUNCiAgICBkb2N1bWVudCBzaGVwaGVyZC4NCiAgICBUb2tlbjogQWRyaWFuIEZh
cnJlbA0KDQogIG8gZHJhZnQtaWV0Zi15YW0tcmZjNDQwOWJpcy0wMg0KICAgIE1lc3NhZ2UgU3Vi
bWlzc2lvbiBmb3IgTWFpbCAoU3RhbmRhcmQpDQogICAgTm90ZTogUyBNb29uZXNhbXkgKHNtK2ll
dGZAZWxhbmRzeXMuY29tKSBpcyB0aGUgZG9jdW1lbnQgc2hlcGhlcmQuDQogICAgVG9rZW46IFBl
dGUgUmVzbmljaw0KDQogIG8gZHJhZnQtaWV0Zi1waW0taGVsbG8taW50aWQtMDENCiAgICBBbiBJ
bnRlcmZhY2UgSUQgSGVsbG8gT3B0aW9uIGZvciBQSU0gKFByb3Bvc2VkIFN0YW5kYXJkKQ0KICAg
IE5vdGU6IE1pa2UgTWNCcmlkZSAobW1jYnJpZGVAY2lzY28uY29tKSBpcyB0aGUgZG9jdW1lbnQg
c2hlcGhlcmQuDQogICAgVG9rZW46IEFkcmlhbiBGYXJyZWwNCg0KICBvIGRyYWZ0LWlldGYtbXBs
cy10cC1vbi1kZW1hbmQtY3YtMDYNCiAgICBNUExTIE9uLWRlbWFuZCBDb25uZWN0aXZpdHkgVmVy
aWZpY2F0aW9uIGFuZCBSb3V0ZSBUcmFjaW5nIChQcm9wb3NlZA0KICAgIFN0YW5kYXJkKQ0KICAg
IE5vdGU6IExvYSBBbmRlcnNzb24gKGxvYUBwaS5udSkgaXMgdGhlIERvY3VtZW50IFNoZXBoZXJk
Lg0KICAgIFRva2VuOiBBZHJpYW4gRmFycmVsDQoNCiAgbyBkcmFmdC1pZXRmLWtyYi13Zy1jbGVh
ci10ZXh0LWNyZWQtMDINCiAgICBUaGUgVW5lbmNyeXB0ZWQgRm9ybSBPZiBLZXJiZXJvcyA1IEtS
Qi1DUkVEIE1lc3NhZ2UgKFByb3Bvc2VkDQogICAgU3RhbmRhcmQpDQogICAgTm90ZTogU2FtIEhh
cnRtYW4gKGhhcnRtYW5zLWlldGZAbWl0LmVkdSkgaXMgdGhlIGRvY3VtZW50IHNoZXBoZXJkLg0K
ICAgIFRva2VuOiBTdGVwaGVuIEZhcnJlbGwNCg0KMi4xLjIgUmV0dXJuaW5nIEl0ZW1zDQoNCiAg
byBkcmFmdC1pZXRmLWdyb3ctZ2VvbXJ0LTA1DQogICAgTXVsdGktdGhyZWFkZWQgUm91dGluZyBU
b29sa2l0IChNUlQpIEJvcmRlciBHYXRld2F5IFByb3RvY29sIChCR1ApDQogICAgcm91dGluZyBp
bmZvcm1hdGlvbiBleHBvcnQgZm9ybWF0IHdpdGggZ2VvLWxvY2F0aW9uIGV4dGVuc2lvbnMNCiAg
ICAoUHJvcG9zZWQgU3RhbmRhcmQpDQogICAgTm90ZTogQ2hyaXN0b3BoZXIgTW9ycm93IChjaHJp
c3RvcGhlci5tb3Jyb3dAZ21haWwuY29tKSBpcyB0aGUNCiAgICBkb2N1bWVudCBzaGVwaGVyZC4N
CiAgICBUb2tlbjogUm9uIEJvbmljYQ0KDQoyLjIgSW5kaXZpZHVhbCBTdWJtaXNzaW9ucw0KMi4y
LjEgTmV3IEl0ZW1zDQoNCiAgTk9ORQ0KDQoyLjIuMiBSZXR1cm5pbmcgSXRlbXMNCg0KICBOT05F
DQoNCjMuIERvY3VtZW50IEFjdGlvbnMNCjMuMSBXRyBTdWJtaXNzaW9ucw0KMy4xLjEgTmV3IEl0
ZW1zDQoNCiAgbyBkcmFmdC1pZXRmLXY2b3BzLTNncHAtZXBzLTAzDQogICAgSVB2NiBpbiAzR1BQ
IEV2b2x2ZWQgUGFja2V0IFN5c3RlbSAoSW5mb3JtYXRpb25hbCkNCiAgICBOb3RlOiBKb2VsIEph
ZWdnbGkgKGpvZWxqYUBib2d1cy5jb20pLCB2Nm9wcyBjby1jaGFpciBpcyB0aGUNCiAgICBkb2N1
bWVudCBzaGVwaGVyZC4NCiAgICBUb2tlbjogUm9uIEJvbmljYQ0KDQogIG8gZHJhZnQtaWV0Zi1k
YW5lLXVzZS1jYXNlcy0wNQ0KICAgIFVzZSBDYXNlcyBhbmQgUmVxdWlyZW1lbnRzIGZvciBETlMt
YmFzZWQgQXV0aGVudGljYXRpb24gb2YgTmFtZWQNCiAgICBFbnRpdGllcyAoREFORSkgKEluZm9y
bWF0aW9uYWwpDQogICAgTm90ZTogT25kP2VqIFN1csOvwr/CvSAob25kcmVqLnN1cnlAbmljLmN6
KSBpcyB0aGUgRG9jdW1lbnQgU2hlcGhlcmQuDQogICAgVG9rZW46IFN0ZXBoZW4gRmFycmVsbA0K
DQozLjEuMiBSZXR1cm5pbmcgSXRlbXMNCg0KICBvIGRyYWZ0LWlldGYtYm13Zy1pZ3AtZGF0YXBs
YW5lLWNvbnYtbWV0aC0yMw0KICAgIEJlbmNobWFya2luZyBNZXRob2RvbG9neSBmb3IgTGluay1T
dGF0ZSBJR1AgRGF0YSBQbGFuZSBSb3V0ZQ0KICAgIENvbnZlcmdlbmNlIChJbmZvcm1hdGlvbmFs
KQ0KICAgIE5vdGU6IEFsIE1vcnRvbiAoYWNtb3J0b25AYXR0LmNvbSkgaXMgdGhlIHNoZXBoZXJk
Lg0KICAgIFRva2VuOiBSb24gQm9uaWNhDQoNCiAgbyBkcmFmdC1pZXRmLWJtd2ctaWdwLWRhdGFw
bGFuZS1jb252LXRlcm0tMjMNCiAgICBUZXJtaW5vbG9neSBmb3IgQmVuY2htYXJraW5nIExpbmst
U3RhdGUgSUdQIERhdGEgUGxhbmUgUm91dGUNCiAgICBDb252ZXJnZW5jZSAoSW5mb3JtYXRpb25h
bCkNCiAgICBOb3RlOiBBbCBNb3J0b24gKGFjbW9ydG9uQGF0dC5jb20pIGlzIHRoZSBzaGVwaGVy
ZC4NCiAgICBUb2tlbjogUm9uIEJvbmljYQ0KDQozLjIgSW5kaXZpZHVhbCBTdWJtaXNzaW9ucyBW
aWEgQUQNCjMuMi4xIE5ldyBJdGVtcw0KDQogIG8gZHJhZnQtZG9yaWEtZ2VuYXJ0LWV4cGVyaWVu
Y2UtMDQNCiAgICBHZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW0gKEdlbi1BUlQpIEV4cGVyaWVuY2Vz
IChJbmZvcm1hdGlvbmFsKQ0KICAgIFRva2VuOiBSdXNzIEhvdXNsZXkNCg0KICBvIGRyYWZ0LXll
dnN0aWZleWV2LWlvbi1yZXBvcnQtMDcNCiAgICBNb3ZpbmcgUkZDIDQ2OTMgdG8gSGlzdG9yaWMg
KEluZm9ybWF0aW9uYWwpDQogICAgVG9rZW46IFJ1c3MgSG91c2xleQ0KDQozLjIuMiBSZXR1cm5p
bmcgSXRlbXMNCg0KICBOT05FDQoNCjMuMyBJUlRGIGFuZCBJbmRlcGVuZGVudCBTdWJtaXNzaW9u
IFN0cmVhbSBEb2N1bWVudHMNCjMuMy4xIE5ldyBJdGVtcw0KDQogIG8gZHJhZnQtYm91Y2FkYWly
LXBwcGV4dC1wb3J0cmFuZ2Utb3B0aW9uLTA2DQogICAgSHVhd2VpIFBvcnQgUmFuZ2UgQ29uZmln
dXJhdGlvbiBPcHRpb25zIGZvciBQUFAgSVBDUCAoSW5mb3JtYXRpb25hbCkNCiAgICBOb3RlOiBJ
U0UgU3VibWlzc2lvbg0KICAgIFRva2VuOiBKYXJpIEFya2tvDQoNCjMuMy4yIFJldHVybmluZyBJ
dGVtcw0KDQogIE5PTkUNCg0KMy4zLjMgRm9yIEFjdGlvbg0KDQogIG8gZHJhZnQtd2VlYi1yZXNl
YXJjaC10by1pbnRlcm5ldC1zdGRzLTAyDQogICAgSG93IHRvIENvbnRyaWJ1dGUgUmVzZWFyY2gg
UmVzdWx0cyB0byBJbnRlcm5ldCBTdGFuZGFyZGl6YXRpb24NCiAgICAoSW5mb3JtYXRpb25hbCkN
CiAgICBOb3RlOiBJU0UgU3VibWlzc2lvbg0KICAgIFRva2VuOiBSdXNzIEhvdXNsZXkNCg0KNC4g
V29ya2luZyBHcm91cCBBY3Rpb25zDQo0LjEgV0cgQ3JlYXRpb24NCjQuMS4xIFByb3Bvc2VkIGZv
ciBJRVRGIFJldmlldw0KDQogIG8gSmF2YXNjcmlwdCBPYmplY3QgU2lnbmluZyBhbmQgRW5jcnlw
dGlvbiAoam9zZSkNCiAgICBUb2tlbjogU2Vhbg0KDQo0LjEuMiBQcm9wb3NlZCBmb3IgQXBwcm92
YWwNCg0KICBOT05FDQoNCjQuMiBXRyBSZWNoYXJ0ZXJpbmcNCjQuMi4xIFVuZGVyIEV2YWx1YXRp
b24gZm9yIElFVEYgUmV2aWV3DQoNCiAgbyBMYXllciAyIFZpcnR1YWwgUHJpdmF0ZSBOZXR3b3Jr
cyAobDJ2cG4pDQogICAgVG9rZW46IFN0ZXdhcnQNCg0KICBvIFNUT1JhZ2UgTWFpbnRlbmFuY2Ug
KHN0b3JtKQ0KICAgIFRva2VuOiBEYXZpZA0KDQoNCg==

From dbharrington@comcast.net  Thu Aug 25 05:34:35 2011
Return-Path: <dbharrington@comcast.net>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A07E821F8634 for <mib-doctors@ietfa.amsl.com>; Thu, 25 Aug 2011 05:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WLqqFm4spv-c for <mib-doctors@ietfa.amsl.com>; Thu, 25 Aug 2011 05:34:35 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by ietfa.amsl.com (Postfix) with ESMTP id CF57F21F85EC for <mib-doctors@ietf.org>; Thu, 25 Aug 2011 05:34:34 -0700 (PDT)
Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta02.westchester.pa.mail.comcast.net with comcast id QcMv1h00416LCl052cboVJ; Thu, 25 Aug 2011 12:35:48 +0000
Received: from davidPC ([67.189.235.106]) by omta06.westchester.pa.mail.comcast.net with comcast id Qcbn1h00r2JQnJT3ScboY5; Thu, 25 Aug 2011 12:35:48 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: <mib-doctors@ietf.org>
Date: Thu, 25 Aug 2011 08:35:36 -0400
Message-ID: <6DA2C01C4A604981A04BD3A838870994@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609
Thread-index: Acxiep2tWF1GJoNOS2WdxhLRtjWGMQAqJnAw
Subject: [MIB-DOCTORS] FW: RFC1213 updates
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 25 Aug 2011 12:34:35 -0000

 

-----Original Message-----
From: David Harrington [mailto:ietfdbh@comcast.net] 
Sent: Wednesday, August 24, 2011 12:27 PM
To: ops-ads@ietf.org; 'The IESG'
Cc: 'Romascanu, Dan (Dan)'; 'Ronald Bonica'
Subject: RFC1213 updates

Hi,

the RFC index does not report that 1573/2233/2863 update RFC1213.
RFC2011 updates RFC1213 by extracting the IP group into an IP-MIB.
RFC2012 updates RFC1213 by extracting the TCP group into a TCP-MIB.
RFC2013 updates RFC1213 by extracting the UDP group into a UDP-MIB.
Since RFC1573 extracts the interfaces group into an IF-MIB, shouldn't
RFC1573 update RFC1213 as well?
Since RFC1354 extracts the IP Forwarding Table into an IP Forwarding
Table MIB, shouldn't it update RFC1213 as well?

It appears that sometime after RFC1573 was published, a decision was
made that these extractions should be labeled as updates.

While this may seem unimportant administration upkeep, I have run
across a number of uses of ifIndex in new work that ignore the "minor"
changes wrought to the ifIndex semantics by RFC1573 and RFC2233. 

RFC1573 says "this MIB module
   also re-specifies the 'interfaces' group of MIB-II in a manner
which
   is both compliant to the SNMPv2 SMI and semantically-identical to
the
   existing SNMPv1-based definitions." 
and
"This MIB consists of 5 tables:

   ifTable
        This table is the ifTable from MIB-II."
and 
" The solution adopted in this memo is to delete the requirement that
   the value of ifIndex must be less than the value of ifNumber, and
to
   retain ifNumber with its current definition.  It could be argued
that
   this is a change in the semantics of ifIndex; however, all existing
   implementations conform to this new definition, and in the
interests
   of not requiring changes in existing implementations and in the
many
   existing media-specific MIBs, it is proposed that this change does
   not require ifIndex to be deprecated."
and
"   ifMIB MODULE-IDENTITY
       LAST-UPDATED "9311082155Z"
       ORGANIZATION "IETF Interfaces MIB Working Group"
       [...]
       DESCRIPTION
               "The MIB module to describe generic objects for
               network interface sub-layers.  This MIB is an updated
               version of MIB-II's ifTable, and incorporates the
               extensions defined in RFC 1229."
       ::= { mib-2 31 }
"

Sounds like an official "updates" is appropriate here, given the
re-specification of the interfaces group from MIB-II (RFC1213) to a
separate IF-MIB, and the changes to ifIndex, even if ifIndex is not
deprecated.

Note that RFC2011, which updates RFC1213, explicitly refers to
RFC1573's ifIndex rather than RFC1213's ifIndex.
Note that RFC4293, which obsolete's RFC2011, explicitly refers to
IF-MIB's ifIndex rather than RFC1213's ifIndex.

RFC2233 obsoletes RFC1573. RFC2233 says very clearly about a change to
ifIndex that it makes, "This is a minor change in the semantics of
ifIndex"). 
ifIndex is originally defined in RFC1213, but the RFC database doesn't
reflect this update to RFC1213 definitions either.

These minor changes to the semantics of IfIndex, due to hot-swapping
and other dynamic assignments, impact an application's ability to rely
on the persistence of ifIndex assignments to interfaces, but many new
documents - including MIB modules, YANG modules, and other protocols -
utilize ifIndex as a persistent identifier for an interface. 

Shouldn't the RFC database reflect these updates to RFC1213?
It's only meta-data, so it shouldn't have any impact on
implementations. But new documents that use ifIndex should reference
the updated ifIndex, including the "minor changes" to its semantics,
not the original RFC1213 ifIndex.

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)



From dromasca@avaya.com  Wed Aug 31 01:23:10 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C473821F8AF1; Wed, 31 Aug 2011 01:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.899
X-Spam-Level: 
X-Spam-Status: No, score=-102.899 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YW+zB+FNKy-f; Wed, 31 Aug 2011 01:23:10 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 5AFEC21F8B09; Wed, 31 Aug 2011 01:23:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArkAAHvvXU7GmAcF/2dsb2JhbABCmF2PbXeBOQcBAQEBAwEBAQ8eCi0HFwYBCA0EBAEBCwIEDAsBByYfBwEBBQQBBAESCAEZh1SZcwKcVIV1YASYUYtb
X-IronPort-AV: E=Sophos;i="4.68,306,1312171200"; d="scan'208";a="204918666"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 31 Aug 2011 04:24:31 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 31 Aug 2011 04:20:08 -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, 31 Aug 2011 10:24:27 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04038D6AA2@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [new-work] WG Review: Javascript Object Signing and Encryption(jose)
Thread-Index: AcxnMjrwaMVff4mKSfaUrnzkye64dwAhQiBQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, "IETF DNS Directorate" <dns-dir@ietf.org>, <aaa-doctors@ietf.org>, <mib-doctors@ietf.org>, "YANG Doctors" <yang-doctors@ietf.org>
Subject: [MIB-DOCTORS] FW: [new-work] WG Review: Javascript Object Signing and Encryption(jose)
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 Aug 2011 08:23:10 -0000

-----Original Message-----
From: new-work-bounces@ietf.org [mailto:new-work-bounces@ietf.org] On
Behalf Of IESG Secretary
Sent: Tuesday, August 30, 2011 7:30 PM
To: new-work@ietf.org
Subject: [new-work] WG Review: Javascript Object Signing and
Encryption(jose)

A new IETF working group has been proposed in the Security Area.  The=20
IESG has not made any determination as yet. The following draft charter=20
was submitted, and is provided for informational purposes only. Please=20
send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday,=20
September 6, 2011                           =20

Javascript Object Signing and Encryption (jose)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Status: Proposed Working Group
Last updated: 2011-08-18

Chairs
    TBD

Security Area Directors:
    Stephen Farrell <stephen.farrell@cs.tcd.ie>
    Sean Turner <turners@ieca.com>

Security Area Advisor:
    Sean Turner <turners@ieca.com>

Mailing Lists:
   General Discussion: jose@ietf.org
   To Subscribe: <https://www.ietf.org/mailman/listinfo/jose>
   Archive: <http://www.ietf.org/mail-archive/web/jose/>

Description of Working Group
----------------------------

Javascript Object Notation (JSON) is a text format for the serialization

of structured data described in RFC 4627. The JSON format is often used=20
for serializing and transmitting structured data over a network=20
connection. With the increased usage of JSON in protocols in the IETF=20
and elsewhere, there is now a desire to offer security services such as=20
encryption, digital signatures, and message authentication codes (MACs)=20
for data that is being carried in JSON format.

Different proposals for providing such security services have already=20
been defined and implemented. This Working Group's task is to=20
standardize two security services, integrity protection (signature and=20
MAC) and encryption, in order to increase interoperability of security=20
features between protocols that use JSON.  The Working Group will base=20
its work on well-known message security primitives (e.g., CMS), and will

solicit input from the rest of the IETF Security Area to be sure that=20
the security functionality in the JSON format is correct.

This group is chartered to work on four documents:

1) A Standards Track document specifying how to apply JSON-structured=20
integrity protection to data, including (but not limited to) JSON data=20
structures.  "Integrity protection" includes public-key digital=20
signatures as well as symmetric-key MACs.

2) A Standards Track document specifying how to apply a JSON-structured=20
encryption to data, including (but not limited to) JSON data structures.

3) A Standards Track document specifying how to encode public keys as=20
JSON-structured objects.

4) A Standards Track document specifying mandatory-to-implement=20
algorithms for the other three documents.

The working group may decide to address one or more of these goals in a=20
single document, in which case the concrete milestones for=20
signing/encryption below will both be satisfied by the single document.

Goals and Milestones
--------------------

Jan 2012    Submit JSON object integrity document as a WG item.

Jan 2012    Submit JSON object encryption document as a WG item.

Jan 2012    Submit JSON key format document as a WG item.

Jan 2012    Submit JSON algorithm document as a WG item.

Jun 2012    Start Working Group Last Call on JSON object integrity=20
            document.

Jun 2012    Start Working Group Last Call on JSON object encryption=20
            document.

Jun 2012    Start Working Group Last Call on JSON key format document.

Jun 2012    Start Working Group Last Call on JSON algorithm document.

Jul 2012    Submit JSON object integrity document to IESG for=20
            consideration as Standards Track document.

Jul 2012    Submit JSON object encryption document to IESG for=20
            consideration as Standards Track document.

Jul 2012    Submit JSON key format document to IESG for consideration
            as Standards Track document.

Jul 2012    Submit JSON algorithm document to IESG for consideration
            as Standards Track document.


_______________________________________________
new-work mailing list
new-work@ietf.org
https://www.ietf.org/mailman/listinfo/new-work

From dromasca@avaya.com  Wed Aug 31 01:23:55 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D95F921F8B2B; Wed, 31 Aug 2011 01:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.618
X-Spam-Level: 
X-Spam-Status: No, score=-102.618 tagged_above=-999 required=5 tests=[AWL=-0.579, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_MLB_Stock6=1.56, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7sop+xYWDtKO; Wed, 31 Aug 2011 01:23:55 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id AA28421F8B1C; Wed, 31 Aug 2011 01:23:54 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArkAAHvvXU6HCzI1/2dsb2JhbAA4Cphdj213gUABAQEBAwEBAQ8eCjQXBgEIDQQBAwEBCwIEDAsBByYfAwQBAQUEAQQBEggBEgeHVJlzApxUgzCCRWAEmFGLWw
X-IronPort-AV: E=Sophos;i="4.68,306,1312171200"; d="scan'208";a="300823327"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 31 Aug 2011 04:25:23 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 31 Aug 2011 04:16:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 31 Aug 2011 10:25:21 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04038D6AA5@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [new-work] WG Review: Recharter of Layer 2 Virtual Private Networks(l2vpn)
Thread-Index: AcxnM125mid25wOTQ+emQJ3+knEbugAhBpAw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, "IETF DNS Directorate" <dns-dir@ietf.org>, <aaa-doctors@ietf.org>, <mib-doctors@ietf.org>, "YANG Doctors" <yang-doctors@ietf.org>
Subject: [MIB-DOCTORS] FW: [new-work] WG Review: Recharter of Layer 2 Virtual Private Networks(l2vpn)
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 Aug 2011 08:23:56 -0000

-----Original Message-----
From: new-work-bounces@ietf.org [mailto:new-work-bounces@ietf.org] On
Behalf Of IESG Secretary
Sent: Tuesday, August 30, 2011 7:37 PM
To: new-work@ietf.org
Subject: [new-work] WG Review: Recharter of Layer 2 Virtual Private
Networks(l2vpn)

A modified charter has been submitted for the Layer 2 Virtual Private=20
Networks (l2vpn) working group in the Routing Area of the IETF.  The=20
IESG has not made any determination as yet.  The modified charter is=20
provided below for informational purposes only.  Please send your=20
comments to the IESG mailing list (iesg@ietf.org) by Tuesday, September=20
6, 2011.

Layer 2 Virtual Private Networks (l2vpn)
----------------------------------------
Last updated: 2011-08-30

  Current Status: Active

 Chairs:
     Nabil Bitar <nabil.n.bitar@verizon.com>
     Giles Heron <giheron@cisco.com>

 Routing Area Directors:
     Stewart Bryant <stbryant@cisco.com>
     Adrian Farrel <adrian@olddog.co.uk>

 Routing Area Advisor:
     Stewart Bryant <stbryant@cisco.com>

 Mailing Lists:
     General Discussion: l2vpn@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/l2vpn
     Archive:=20
http://www.ietf.org/mail-archive/web/l2vpn/current/maillist.html

Description of Working Group:

The L2VPN working group is responsible for defining and specifying a
limited number of solutions for supporting provider-provisioned Layer-2
Virtual Private Networks (L2VPNs). It will also address requirements=20
driven by cloud computing services and data centers as they apply to=20
Layer-2 VPN services.

Layer-2 VPNs defined by L2VPN operate over pseudowires (PWs) as
defined by the PWE3 WG or over IP or MPLS PSN tunnels. A L2VPN
emulates a "native" service over a PSN that is adequately faithful
to, but may not be entirely indistinguishable from the native
service itself. Further, following in the "edge-to-edge" nature
of the  service, the L2VPN WG will not define any mechanisms
which exert control over the underlying PSN. When necessary it
may, however, recommend or require the use of existing PSN QoS
and path control mechanisms between the PEs which provide the
L2VPN connectivity.

Layer-2 VPNs comprise the following:

1. Virtual Private LAN Service (VPLS) -- A Layer-2 service
that emulates a switched Ethernet (V)LAN across a PSN.

2. Virtual Private Wire Service (VPWS) -- A Layer-2 service that
provides point-to-point connectivity for a variety of link layers,
including Frame Relay, ATM, Ethernet, PPP, etc., across a PSN.

3. Virtual Private Multicast Service (VPMS) -- A Layer-2 service that
provides point-to-multipoint connectivity for a variety of link
layers across a PSN.

4. IP-only L2VPN, an IP-only service over a PSN.  The WG will address
two specific types of IP-only L2VPN:

a) Point-to-point Layer-2 VPN.  This service is similar to VPWS, but=20
also supports heterogenous Attachment Circuits at either end
of a single point-to-point service.

b) Multipoint-to-multipoint Layer-2 VPN.  This service is similar
to VPLS, but learns IP and MAC address bindings from ARPs and
broadcast/multicast IP packets.

5. Ethernet VPN (E-VPN) - An enhanced Layer-2 service that
emulates an Ethernet (V)LAN across a PSN. E-VPN supports
load-sharing across multiple connections from a Layer-2 site
to an L2VPN service. E-VPN is primarily targeted to support
large-scale L2VPNs with resiliency requirements not satisfied
by other L2VPN solutions.

6. E-Tree, a Layer-2 service defined by the MEF, which provides
connectivity between one or more root nodes and one or more leaf
nodes, with the restriction that leaf nodes may only communicate
with root node(s) (and not with each other).

L2VPNs will make use of existing IETF specified mechanisms
unless there are technical reasons why the existing mechanisms
are insufficient or unnecessary.

The L2VPN WG is responsible for specification of the
discovery and membership of PEs participating in a Layer-2
VPN as well as the membership of CE devices for a specific
instance of an L2VPN.

The L2VPN WG will provide extensions of existing protocols
that will be discussed in protocol-specific WGs. In
particular, the L2VPN WG may define extensions to pseudowire
management mechanisms for VPLS. Those extensions will
be reviewed by the PWE3 WG to ensure they are aligned
with the overall design/architecture of PWE3.

The L2VPN WG will not define new encapsulations, control,
or resiliency mechanisms specifically related to pseudowires.=20
Furthermore, when the L2VPN solution is based on PWs, the
L2VPN WG will not define protocol inter-working between
an L2VPN and native service Layer-2 OAM or resiliency
mechanisms. The L2VPN WG may define how to operate native
service-layer control, OAM or resiliency mechanisms on
top of an L2VPN. In addition, it may define native data
plane and/or control plane interworking between an
L2VPN and an associated native Layer-2 service.


The L2VPN WG scope includes the following:

1. Discovery of PEs participating in a Layer-2 VPN and the
associated topology required for connectivity of the VPLS,
VPWS, VPMS or E-VPN service.

2. Signaling of information related to the discovery and
membership of PEs within a L2VPN. These procedures must
use PWE3 control and management procedures, or define
requirements for extensions of PWE3 protocols to suit
the needs of an L2VPN, when the L2VPN operates over PWs.
Once those requirements have been reviewed by the L2VPN WG,
they should be provided to the PWE3 WG to derive solutions.

3. MIBs for Layer-2 VPN solutions.

4. Specification of requirements, framework and solutions
that facilitate Operations Administration and Management
(OAM) of any type of L2VPN within the scope of the L2VPN
Working Group.

5. Mechanisms to permit optimization of multicast data
traffic within an L2VPN.

6. If transport does not involve PWs, mechanisms that
support load-balancing/multi-pathing between PEs
interconnecting a Layer-2 service using an L2VPN across
the PSN.

7. requirements for the multi-homing of CEs to several
VPLS or E-VPN PEs, inclusive of active/backup and active/
active (load-sharing) configurations. Based on these
requirements define VPLS or E-VPN control plane
solutions for achieving fast convergence after failure
of an active path in the PSN or on the AC side.

8. Enhancements to increase the scalability of the Control
Plane and Data Plane of L2VPN PE nodes, and of core nodes
that provide transport services for L2VPN.

9. Requirements and solutions for Auto-Discovery and
Signaling of Inter-AS L2VPNs, in addition to Inter-AS
solutions for multicast-optimized L2VPNs.

10. Requirements and solutions for supporting "E-Tree"
services using VPLS.

Milestones:

Done        Submit an I-D describing MIB for VPLS
Done        Submit an I-D describing MIB for VPWS
Done        Submit an I-D on OAM requirements for VPLS
Done        Submit an I-D on OAM requirements for VPWS
Done        Submit L2 requirements to IESG for publication
            as Informational RFC
Done        Submit L2 framework to IESG for publication
            as Informational RFC
Done        Identify VPLS and VPWS solutions for the WG
Done        Submit VPLS solution documents to IESG
Done        Submit VPWS solution documents to IESG
Done        Submit Auto-Discovery and Signaling for Intra-AS
            and Inter-AS VPLS and VPWS Layer-2 VPNs
Oct 2011    Submit IP-only L2VPN solution documents to IESG
Nov 2011    Submit OAM solutions for VPWS to IESG
Nov 2011    Submit OAM solutions for VPLS to IESG
Nov 2011    Submit signaling solution for multicast-optimized
            VPLS to IESG
Nov 2011    Submit I-D on Virtual Private Multicast Service (VPMS)
            requirements to IESG
Nov 2011    Submit MIB for VPLS to IESG
Nov 2011    Submit MIB for VPWS to IESG
Mar 2012    Submit scalability solutions for VPLS Data-Plane to IESG
Mar 2012    Submit scalability solutions for VPLS Control-Plane to
            IESG
Mar 2012    Submit E-Tree requirements/framework to IESG
Jul 2012    Submit MIB for IP-only L2VPN to IESG
Jul 2012    Submit OAM solutions for IP-only L2VPN to IESG
Jul 2012    Submit Auto-Discovery solution for VPMS to IESG
Jul 2012    Submit VPLS service convergence improvement solutions
            to IESG
Jul 2012    Submit VPLS multi-homing solutions to IESG
Jul 2012    Submit E-Tree solution to IESG
Jul 2012    Submit E-VPN requirements/framework to IESG
Nov 2012    Submit E-Tree OAM to IESG
Dec 2012    Submit E-Tree MIB to IESG
Nov 2012    Submit E-VPN solution to IESG
Mar 2013    Submit E-VPN OAM to IESG
Apr 2013    Submit E-VPN MIB to IESG



_______________________________________________
new-work mailing list
new-work@ietf.org
https://www.ietf.org/mailman/listinfo/new-work
