
From nobody Mon Apr  4 08:09:41 2016
Return-Path: <jcucchiara@mindspring.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 B7D2512D78A; Mon,  4 Apr 2016 08:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (384-bit key) header.from=jcucchiara@mindspring.com header.d=mindspring.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rLUpDbdGkD5T; Mon,  4 Apr 2016 08:09:36 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 71CFB12D724; Mon,  4 Apr 2016 08:09:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=MygzPr+zgZb6FBxH1RvETUH8btSmpb5L1ZRY9qD33xPsXlNtbsNElxhQUqQCjFgB; h=Received:From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [72.93.239.57] (helo=JoanTower) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1an67l-0006wp-KB; Mon, 04 Apr 2016 11:09:05 -0400
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>, <draft-ietf-mpls-tp-linear-protection-mib@ietf.org>, <mpls-chairs@ietf.org>
Date: Mon, 4 Apr 2016 11:10:49 -0400
Message-ID: <00a901d18e84$2c19a340$844ce9c0$@mindspring.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdGOgu3jx1rdAtVCTCy7UrFLqFTuiw==
Content-Language: en-us
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e2654dda0a30e53f1c0b99b09c09edee31f90676ae045857c2f36350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 72.93.239.57
Archived-At: <http://mailarchive.ietf.org/arch/msg/mib-doctors/BA1OZM4Ru5BJJ2HEGT61hpVRzFA>
Cc: mib-doctors@ietf.org
Subject: [MIB-DOCTORS] Review of draft-ietf-mpls-tp-linear-protection-mib-07
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Apr 2016 15:09:39 -0000

Comments for draft-ietf-mpls-tp-linear-protection-mib-07.txt

Authors,

Lots of work went into this draft.  The early MIB Doctor review 
comments have been incorporated, so thank you for that.   These 
comments are arranged in 3 sections:  MIB compiler outputs, 
General Comments which are observations that apply to several 
places in the MIB and should be checked for throughout the MIB.  

The last section is for specific comments.

Please take these comments as part of the last call.

Thanks,
-Joan

Compiles cleanly with smilint

smicng flagged some errors
Output from smicng
E: f(MPLS-LSP-MIB.my), (370,4) Row "mplsLpsConfigEntry" may not 
have columns with MAX-ACCESS of read-write if any column is read-create
E: f(MPLS-LSP-MIB.my), (378,15) Index item 
"mplsLpsConfigDomainIndex" must be defined with syntax that 
includes a range
E: f(MPLS-LSP-MIB.my), (907,4) Item "mplsLpsMeConfigDomainIndex" 
has invalid value for MAX-ACCESS


When looking at the MIB, I see that there do appear to be some potential
errors:
   mplsLpsConfigCommand OBJECT-TYPE
      SYNTAX      MplsLpsCommand
      MAX-ACCESS  read-write    <---- should be read-create 

because row created using RowStatus
      STATUS      current

In general, indices should specify a range so this is why it was 
flagged by compiler.  Looking at this specific index would like to 
understand how the value is supposed to be assigned?   If this is 
assigned by an operator, perhaps there should be a mechanism for 
the operator to choose a value (for example, by using a 
IndexIntegerNextFree object)?  Please clarify.

   mplsLpsConfigDomainIndex OBJECT-TYPE
      SYNTAX        Unsigned32

mplsLpsMeConfigDomainIndex <--- name implies that this is an index 
but it is NOT included in the INDEX clause for this table.   

Please clarify what is intended.


General Comments:
=====================

* There are mentions of there being two MIB Modules in this 
document, but there is only one MIB Module. I have tried to note 
these statements under specific comments, but please check for 
such statements.   If the intention is to create two MIB Modules, 
that is fine, but currently, there is only one.

* The relationships of these Tables is not clear.  
MplsLpsConfigTable has an INDEX but how the operator 
is supposed to choose a value for this index is 
not specified.  The MplsLpsMeConfigTable indexing is confusing.  
Although the document states that this table is an extension 
of the MPLSOamIdMeTable, the name of the object, 
mplsLpsMeConfigDomainIndex is confusing because it suggests
this is an INDEX (as does the status of not-accessible).   Please clarify.  

Since the indexing for these Tables is confusing to me, then 
please realize that this MIB may have additional comments
during the next review once the indexing is clarified. 

* In general more REFERENCE Clauses could/should be added throughout MIB.

Objects such as mplsLpsMeConfigDomainIndex, mplsLpsMeStatusCurrent,
mplsLpsConfigMode, mplsLpsConfigProtectionType, etc.   This was also 
mentioned during the early MIB Dr. review.

* Some of the objects use Integer32 but they probably should 
use Unsigned32.   In other words, if the objects can only take on values 0
and above, then 
they should use Unsigned32.

e.g.     mplsLpsConfigSdBadSeconds, mplsLpsConfigSdGoodSeconds,
mplsLpsConfigWaitToRestore, mplsLpsConfigHoldOff, etc.  Please 
check all the Integer32 objects to see if they should be Unsigned32.


*) Date is same a previous version.  This should be updated for 
every revision of the document.  Please update.
      LAST-UPDATED  and REVISION clauses
    "201512060000Z"  -- December 06, 2015


*) Only FullCompliance is done for this MIB Module.  As you 
probably are aware, not all operators want to configure
using SNMP, if there is not a ReadOnly Compliance available, then 
they will not be compliant with the MIB.  I think a ReadOnly Compliance 
for a MIB is useful and would like to understand why this MIB doesn't have
one.
Could the authors please clarify?


Specific Comments:   

Section 1. Introductions

Mentions multiple MIB Modules but there is only one.  Please 
clarify the text:  "However, since the MIB modules ..." <-- plural


Section 4.

As mentioned before there is only 1 MIB module.  Please update.

   "This document specifies a MIB module 
    for the Label Edge Router (LER)
    that supports MPLS TP Linear protection and a MIB 
    module that defines textual conventions....."


Section 5.1 Textual Conventions
 
* I don't see a separate MIB Module for TCs.  Please clarify.

Section 5.4 The Table Structure

 * The mplsLpsConfigTable

"The protection domain is identified by mplsLpsConfigGroupName."   
This statement does not seem to be entirely accurate given the MIB 
design for 2 reasons, 1.  there doesn't seem to be an object
mplsLpsConfigGroupName 
and 2. the INDEX is mplsLpsConfigDomainIndex Unsigned32 (which also appears
in the 
mplsLpsMeConfigEntry with a status of not-accessible 
(and I think you intend for it to be an object)?

As a reviewer, this is confusing because the relationship with 
these tables is unclear and so it is very difficult to 
review the MIB Module.  Please clarify the relationship with 
these tables and to the mplsOamIdMeTable in the 
MPLS-OAM-ID-STD-MIB.


"The other attributes in this table", do you mean objects?

* The  mplsLpsStatusTable

There is no mention that the mplsLpsStatusTable's Entries have an 
AUGMENTS relationship with the mplsLpsConfigTable Entries.  Please add.

6.1  Relationship to the MPLS OAM maintenance identifier MIB Module

The title needs to be capitalized correctly, Relationship to the 
MPLS OAM Maintenance Identifier MIB Module

Please update this section to use RFC7697 (and in Informative References
also) 
instead of draft-ietf-mpls-tp-oam-id-mib.   

As mentioned above, the mplsLpsMeConfigTable has an object 
mplsLpsMeConfigDomainIndex which is (not-accessible).
Is this supposed to be an INDEX, or is this an object?   I am 
confused by what is intended.  

7.  Example of Protection switching configuration for 

MPLS-TP TE tunnel (Please change title:  Example of Protection Switching
Configuration)

* I am unclear how mplsLspConfigEntry is actually configured for 
use in this example.   Is an operator supposed to randomly choose an INDEX
value?

Would an IndexNext object be useful to use in conjunction with this INDEX?

MIB Module
------------

(general comment:  the DESCRIPTION clauses could be more readable 
if consistency was used.  Sometimes the
value is listed on the side and the description follows on the 
same line and sometimes the value is listed
on a single line and the description follows a couple of lines 
after.   Please be consistent.)

* mplsLpsConfigDomainName  -- Is there a DEFAULT value for this 
object?   The string size is 1..32 with no
option of 0 length string, so wanted to check about a default 
value?  Under what circumstances can this value
be modified?   Please give a REFERENCE.

* mplsLpsConfigMode - Needs REFERENCE (and please try to be 
specific).  Under what circumstances can this be modified?

* mplsLpsConfigWaitToRestore
Why is this not in minutes?  If someone configures this to be 30 
seconds is that valid?  Doesn't seem so based on the DESCRIPTION.  Please
clarify.

* mplsLpsConfigHoldOff What is meant by "Can be configured in 
steps of 100?"   Is this 100 milliseconds?  If so then maybe a better unit
choice would be 
centiseconds.   Please clarify.

*mplsLpsConfigCommand is read-write.  Is this supposed to be 
read-create?

*mplsLpsConfigRowStatus --  I think there is some conflicting 
advice given to the operator.  Several objects say that it is fine to change
the 
value of the object when RowStatus is active, but this is not specified
consistently.  Limiting the 
values of RowStatus in the Conformance Section
may be the way to go.  Please clarify.

*mplsLpsMeConfigState is a read-create. This is probably okay, but 
again, that depends on if mplsLpsMeConfigDomainIndex
is an INDEX for this table given that it has a status of not-accessible,
etc.


*mplsLpsMeStatusSwitchoverSeconds
Needs a units clause for Seconds


Notifications

There are a couple Notifications that are send when values of certain 
counters increment.  Maybe this is valid, but it seems suspect.  
If a management stations needs information on counters,
why can't it just retrieve them at that point?   I don't see any 
counter discontinuity objects, so was wondering about that too.  

* mplsLpsEventFopTimOut Notification

Please rename this to mplsLpsEventFopTimeout

* Compliance/Conformance Section of the MIB Module

Currently, there is only FullCompliance.   Why is there no
ReadOnlyCompliance?

--- end of comments ---



From nobody Wed Apr  6 06:15:00 2016
Return-Path: <ryoo@etri.re.kr>
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 5C8E012D1AB; Wed,  6 Apr 2016 06:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.911
X-Spam-Level: 
X-Spam-Status: No, score=-101.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i_GYubn8bO52; Wed,  6 Apr 2016 06:14:53 -0700 (PDT)
Received: from smtpeg.etri.re.kr (smtpeg2.etri.re.kr [129.254.27.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA81A12D0C7; Wed,  6 Apr 2016 06:14:29 -0700 (PDT)
Received: from SMTP1.etri.info (129.254.28.71) by SMTPEG2.etri.info (129.254.27.142) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 6 Apr 2016 22:14:29 +0900
Received: from SMTP2.etri.info ([169.254.2.162]) by SMTP1.etri.info ([10.2.6.30]) with mapi id 14.01.0355.002; Wed, 6 Apr 2016 22:14:25 +0900
From: =?ks_c_5601-1987?B?t/nBpLW/?= <ryoo@etri.re.kr>
To: Joan Cucchiara <jcucchiara@mindspring.com>, Loa Andersson <loa@pi.nu>, "draft-ietf-mpls-tp-linear-protection-mib@ietf.org" <draft-ietf-mpls-tp-linear-protection-mib@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Thread-Topic: Review of draft-ietf-mpls-tp-linear-protection-mib-07 
Thread-Index: AdGOgu3jx1rdAtVCTCy7UrFLqFTuiwBgwY4U
Date: Wed, 6 Apr 2016 13:14:24 +0000
Message-ID: <5B4A6CBE3924BB41A3BEE462A8E0B75A291BF031@SMTP2.etri.info>
References: <00a901d18e84$2c19a340$844ce9c0$@mindspring.com>
In-Reply-To: <00a901d18e84$2c19a340$844ce9c0$@mindspring.com>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.254.26.37]
Content-Type: text/plain; charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mib-doctors/lzJLaaYgyOP67pnGmWTokz1nw28>
Cc: "mib-doctors@ietf.org" <mib-doctors@ietf.org>
Subject: [MIB-DOCTORS] =?euc-kr?q?=C8=B8=BD=C5=3A_Review_of_draft-ietf-mpl?= =?euc-kr?q?s-tp-linear-protection-mib-07?=
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 06 Apr 2016 13:14:56 -0000

Sm9hbiwgdGhhbmsgeW91IHNvIG11Y2ggZm9yIHlvdXIgdGltZSBhbmQgdmFsdWFibGUgY29tbWVu
dHMuDQoNCldlIHdpbGwgcmVzb2x2ZSB0aGUgY29tbWVudHMgaW4gdGhlIG5leHQgdmVyc2lvbi4N
Cg0KQmVzdCByZWdhcmRzLA0KDQpKZW9uZy1kb25nDQoNCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCrq4s70gu+e29zogSm9hbiBDdWNjaGlhcmEgW2pjdWNjaGlhcmFA
bWluZHNwcmluZy5jb21dDQq6uLO9ILOvwqU6IDIwMTaz4iA0v/kgNcDPIMitv+TAzyC/wMD8IDEy
OjEwDQq53rTCILvntvc6IExvYSBBbmRlcnNzb247IG1wbHNAaWV0Zi5vcmc7IGRyYWZ0LWlldGYt
bXBscy10cC1saW5lYXItcHJvdGVjdGlvbi1taWJAaWV0Zi5vcmc7IG1wbHMtY2hhaXJzQGlldGYu
b3JnDQrC/MG2OiBtaWItZG9jdG9yc0BpZXRmLm9yZw0Kwaa48TogUmV2aWV3IG9mIGRyYWZ0LWll
dGYtbXBscy10cC1saW5lYXItcHJvdGVjdGlvbi1taWItMDcNCg0KQ29tbWVudHMgZm9yIGRyYWZ0
LWlldGYtbXBscy10cC1saW5lYXItcHJvdGVjdGlvbi1taWItMDcudHh0DQoNCkF1dGhvcnMsDQoN
CkxvdHMgb2Ygd29yayB3ZW50IGludG8gdGhpcyBkcmFmdC4gIFRoZSBlYXJseSBNSUIgRG9jdG9y
IHJldmlldw0KY29tbWVudHMgaGF2ZSBiZWVuIGluY29ycG9yYXRlZCwgc28gdGhhbmsgeW91IGZv
ciB0aGF0LiAgIFRoZXNlDQpjb21tZW50cyBhcmUgYXJyYW5nZWQgaW4gMyBzZWN0aW9uczogIE1J
QiBjb21waWxlciBvdXRwdXRzLA0KR2VuZXJhbCBDb21tZW50cyB3aGljaCBhcmUgb2JzZXJ2YXRp
b25zIHRoYXQgYXBwbHkgdG8gc2V2ZXJhbA0KcGxhY2VzIGluIHRoZSBNSUIgYW5kIHNob3VsZCBi
ZSBjaGVja2VkIGZvciB0aHJvdWdob3V0IHRoZSBNSUIuDQoNClRoZSBsYXN0IHNlY3Rpb24gaXMg
Zm9yIHNwZWNpZmljIGNvbW1lbnRzLg0KDQpQbGVhc2UgdGFrZSB0aGVzZSBjb21tZW50cyBhcyBw
YXJ0IG9mIHRoZSBsYXN0IGNhbGwuDQoNClRoYW5rcywNCi1Kb2FuDQoNCkNvbXBpbGVzIGNsZWFu
bHkgd2l0aCBzbWlsaW50DQoNCnNtaWNuZyBmbGFnZ2VkIHNvbWUgZXJyb3JzDQpPdXRwdXQgZnJv
bSBzbWljbmcNCkU6IGYoTVBMUy1MU1AtTUlCLm15KSwgKDM3MCw0KSBSb3cgIm1wbHNMcHNDb25m
aWdFbnRyeSIgbWF5IG5vdA0KaGF2ZSBjb2x1bW5zIHdpdGggTUFYLUFDQ0VTUyBvZiByZWFkLXdy
aXRlIGlmIGFueSBjb2x1bW4gaXMgcmVhZC1jcmVhdGUNCkU6IGYoTVBMUy1MU1AtTUlCLm15KSwg
KDM3OCwxNSkgSW5kZXggaXRlbQ0KIm1wbHNMcHNDb25maWdEb21haW5JbmRleCIgbXVzdCBiZSBk
ZWZpbmVkIHdpdGggc3ludGF4IHRoYXQNCmluY2x1ZGVzIGEgcmFuZ2UNCkU6IGYoTVBMUy1MU1At
TUlCLm15KSwgKDkwNyw0KSBJdGVtICJtcGxzTHBzTWVDb25maWdEb21haW5JbmRleCINCmhhcyBp
bnZhbGlkIHZhbHVlIGZvciBNQVgtQUNDRVNTDQoNCg0KV2hlbiBsb29raW5nIGF0IHRoZSBNSUIs
IEkgc2VlIHRoYXQgdGhlcmUgZG8gYXBwZWFyIHRvIGJlIHNvbWUgcG90ZW50aWFsDQplcnJvcnM6
DQogICBtcGxzTHBzQ29uZmlnQ29tbWFuZCBPQkpFQ1QtVFlQRQ0KICAgICAgU1lOVEFYICAgICAg
TXBsc0xwc0NvbW1hbmQNCiAgICAgIE1BWC1BQ0NFU1MgIHJlYWQtd3JpdGUgICAgPC0tLS0gc2hv
dWxkIGJlIHJlYWQtY3JlYXRlDQoNCmJlY2F1c2Ugcm93IGNyZWF0ZWQgdXNpbmcgUm93U3RhdHVz
DQogICAgICBTVEFUVVMgICAgICBjdXJyZW50DQoNCkluIGdlbmVyYWwsIGluZGljZXMgc2hvdWxk
IHNwZWNpZnkgYSByYW5nZSBzbyB0aGlzIGlzIHdoeSBpdCB3YXMNCmZsYWdnZWQgYnkgY29tcGls
ZXIuICBMb29raW5nIGF0IHRoaXMgc3BlY2lmaWMgaW5kZXggd291bGQgbGlrZSB0bw0KdW5kZXJz
dGFuZCBob3cgdGhlIHZhbHVlIGlzIHN1cHBvc2VkIHRvIGJlIGFzc2lnbmVkPyAgIElmIHRoaXMg
aXMNCmFzc2lnbmVkIGJ5IGFuIG9wZXJhdG9yLCBwZXJoYXBzIHRoZXJlIHNob3VsZCBiZSBhIG1l
Y2hhbmlzbSBmb3INCnRoZSBvcGVyYXRvciB0byBjaG9vc2UgYSB2YWx1ZSAoZm9yIGV4YW1wbGUs
IGJ5IHVzaW5nIGENCkluZGV4SW50ZWdlck5leHRGcmVlIG9iamVjdCk/ICBQbGVhc2UgY2xhcmlm
eS4NCg0KICAgbXBsc0xwc0NvbmZpZ0RvbWFpbkluZGV4IE9CSkVDVC1UWVBFDQogICAgICBTWU5U
QVggICAgICAgIFVuc2lnbmVkMzINCg0KbXBsc0xwc01lQ29uZmlnRG9tYWluSW5kZXggPC0tLSBu
YW1lIGltcGxpZXMgdGhhdCB0aGlzIGlzIGFuIGluZGV4DQpidXQgaXQgaXMgTk9UIGluY2x1ZGVk
IGluIHRoZSBJTkRFWCBjbGF1c2UgZm9yIHRoaXMgdGFibGUuDQoNClBsZWFzZSBjbGFyaWZ5IHdo
YXQgaXMgaW50ZW5kZWQuDQoNCg0KR2VuZXJhbCBDb21tZW50czoNCj09PT09PT09PT09PT09PT09
PT09PQ0KDQoqIFRoZXJlIGFyZSBtZW50aW9ucyBvZiB0aGVyZSBiZWluZyB0d28gTUlCIE1vZHVs
ZXMgaW4gdGhpcw0KZG9jdW1lbnQsIGJ1dCB0aGVyZSBpcyBvbmx5IG9uZSBNSUIgTW9kdWxlLiBJ
IGhhdmUgdHJpZWQgdG8gbm90ZQ0KdGhlc2Ugc3RhdGVtZW50cyB1bmRlciBzcGVjaWZpYyBjb21t
ZW50cywgYnV0IHBsZWFzZSBjaGVjayBmb3INCnN1Y2ggc3RhdGVtZW50cy4gICBJZiB0aGUgaW50
ZW50aW9uIGlzIHRvIGNyZWF0ZSB0d28gTUlCIE1vZHVsZXMsDQp0aGF0IGlzIGZpbmUsIGJ1dCBj
dXJyZW50bHksIHRoZXJlIGlzIG9ubHkgb25lLg0KDQoqIFRoZSByZWxhdGlvbnNoaXBzIG9mIHRo
ZXNlIFRhYmxlcyBpcyBub3QgY2xlYXIuDQpNcGxzTHBzQ29uZmlnVGFibGUgaGFzIGFuIElOREVY
IGJ1dCBob3cgdGhlIG9wZXJhdG9yDQppcyBzdXBwb3NlZCB0byBjaG9vc2UgYSB2YWx1ZSBmb3Ig
dGhpcyBpbmRleCBpcw0Kbm90IHNwZWNpZmllZC4gIFRoZSBNcGxzTHBzTWVDb25maWdUYWJsZSBp
bmRleGluZyBpcyBjb25mdXNpbmcuDQpBbHRob3VnaCB0aGUgZG9jdW1lbnQgc3RhdGVzIHRoYXQg
dGhpcyB0YWJsZSBpcyBhbiBleHRlbnNpb24NCm9mIHRoZSBNUExTT2FtSWRNZVRhYmxlLCB0aGUg
bmFtZSBvZiB0aGUgb2JqZWN0LA0KbXBsc0xwc01lQ29uZmlnRG9tYWluSW5kZXggaXMgY29uZnVz
aW5nIGJlY2F1c2UgaXQgc3VnZ2VzdHMNCnRoaXMgaXMgYW4gSU5ERVggKGFzIGRvZXMgdGhlIHN0
YXR1cyBvZiBub3QtYWNjZXNzaWJsZSkuICAgUGxlYXNlIGNsYXJpZnkuDQoNClNpbmNlIHRoZSBp
bmRleGluZyBmb3IgdGhlc2UgVGFibGVzIGlzIGNvbmZ1c2luZyB0byBtZSwgdGhlbg0KcGxlYXNl
IHJlYWxpemUgdGhhdCB0aGlzIE1JQiBtYXkgaGF2ZSBhZGRpdGlvbmFsIGNvbW1lbnRzDQpkdXJp
bmcgdGhlIG5leHQgcmV2aWV3IG9uY2UgdGhlIGluZGV4aW5nIGlzIGNsYXJpZmllZC4NCg0KKiBJ
biBnZW5lcmFsIG1vcmUgUkVGRVJFTkNFIENsYXVzZXMgY291bGQvc2hvdWxkIGJlIGFkZGVkIHRo
cm91Z2hvdXQgTUlCLg0KDQpPYmplY3RzIHN1Y2ggYXMgbXBsc0xwc01lQ29uZmlnRG9tYWluSW5k
ZXgsIG1wbHNMcHNNZVN0YXR1c0N1cnJlbnQsDQptcGxzTHBzQ29uZmlnTW9kZSwgbXBsc0xwc0Nv
bmZpZ1Byb3RlY3Rpb25UeXBlLCBldGMuICAgVGhpcyB3YXMgYWxzbw0KbWVudGlvbmVkIGR1cmlu
ZyB0aGUgZWFybHkgTUlCIERyLiByZXZpZXcuDQoNCiogU29tZSBvZiB0aGUgb2JqZWN0cyB1c2Ug
SW50ZWdlcjMyIGJ1dCB0aGV5IHByb2JhYmx5IHNob3VsZA0KdXNlIFVuc2lnbmVkMzIuICAgSW4g
b3RoZXIgd29yZHMsIGlmIHRoZSBvYmplY3RzIGNhbiBvbmx5IHRha2Ugb24gdmFsdWVzIDANCmFu
ZCBhYm92ZSwgdGhlbg0KdGhleSBzaG91bGQgdXNlIFVuc2lnbmVkMzIuDQoNCmUuZy4gICAgIG1w
bHNMcHNDb25maWdTZEJhZFNlY29uZHMsIG1wbHNMcHNDb25maWdTZEdvb2RTZWNvbmRzLA0KbXBs
c0xwc0NvbmZpZ1dhaXRUb1Jlc3RvcmUsIG1wbHNMcHNDb25maWdIb2xkT2ZmLCBldGMuICBQbGVh
c2UNCmNoZWNrIGFsbCB0aGUgSW50ZWdlcjMyIG9iamVjdHMgdG8gc2VlIGlmIHRoZXkgc2hvdWxk
IGJlIFVuc2lnbmVkMzIuDQoNCg0KKikgRGF0ZSBpcyBzYW1lIGEgcHJldmlvdXMgdmVyc2lvbi4g
IFRoaXMgc2hvdWxkIGJlIHVwZGF0ZWQgZm9yDQpldmVyeSByZXZpc2lvbiBvZiB0aGUgZG9jdW1l
bnQuICBQbGVhc2UgdXBkYXRlLg0KICAgICAgTEFTVC1VUERBVEVEICBhbmQgUkVWSVNJT04gY2xh
dXNlcw0KICAgICIyMDE1MTIwNjAwMDBaIiAgLS0gRGVjZW1iZXIgMDYsIDIwMTUNCg0KDQoqKSBP
bmx5IEZ1bGxDb21wbGlhbmNlIGlzIGRvbmUgZm9yIHRoaXMgTUlCIE1vZHVsZS4gIEFzIHlvdQ0K
cHJvYmFibHkgYXJlIGF3YXJlLCBub3QgYWxsIG9wZXJhdG9ycyB3YW50IHRvIGNvbmZpZ3VyZQ0K
dXNpbmcgU05NUCwgaWYgdGhlcmUgaXMgbm90IGEgUmVhZE9ubHkgQ29tcGxpYW5jZSBhdmFpbGFi
bGUsIHRoZW4NCnRoZXkgd2lsbCBub3QgYmUgY29tcGxpYW50IHdpdGggdGhlIE1JQi4gIEkgdGhp
bmsgYSBSZWFkT25seSBDb21wbGlhbmNlDQpmb3IgYSBNSUIgaXMgdXNlZnVsIGFuZCB3b3VsZCBs
aWtlIHRvIHVuZGVyc3RhbmQgd2h5IHRoaXMgTUlCIGRvZXNuJ3QgaGF2ZQ0Kb25lLg0KQ291bGQg
dGhlIGF1dGhvcnMgcGxlYXNlIGNsYXJpZnk/DQoNCg0KU3BlY2lmaWMgQ29tbWVudHM6DQoNClNl
Y3Rpb24gMS4gSW50cm9kdWN0aW9ucw0KDQpNZW50aW9ucyBtdWx0aXBsZSBNSUIgTW9kdWxlcyBi
dXQgdGhlcmUgaXMgb25seSBvbmUuICBQbGVhc2UNCmNsYXJpZnkgdGhlIHRleHQ6ICAiSG93ZXZl
ciwgc2luY2UgdGhlIE1JQiBtb2R1bGVzIC4uLiIgPC0tIHBsdXJhbA0KDQoNClNlY3Rpb24gNC4N
Cg0KQXMgbWVudGlvbmVkIGJlZm9yZSB0aGVyZSBpcyBvbmx5IDEgTUlCIG1vZHVsZS4gIFBsZWFz
ZSB1cGRhdGUuDQoNCiAgICJUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBhIE1JQiBtb2R1bGUNCiAg
ICBmb3IgdGhlIExhYmVsIEVkZ2UgUm91dGVyIChMRVIpDQogICAgdGhhdCBzdXBwb3J0cyBNUExT
IFRQIExpbmVhciBwcm90ZWN0aW9uIGFuZCBhIE1JQg0KICAgIG1vZHVsZSB0aGF0IGRlZmluZXMg
dGV4dHVhbCBjb252ZW50aW9ucy4uLi4uIg0KDQoNClNlY3Rpb24gNS4xIFRleHR1YWwgQ29udmVu
dGlvbnMNCg0KKiBJIGRvbid0IHNlZSBhIHNlcGFyYXRlIE1JQiBNb2R1bGUgZm9yIFRDcy4gIFBs
ZWFzZSBjbGFyaWZ5Lg0KDQpTZWN0aW9uIDUuNCBUaGUgVGFibGUgU3RydWN0dXJlDQoNCiAqIFRo
ZSBtcGxzTHBzQ29uZmlnVGFibGUNCg0KIlRoZSBwcm90ZWN0aW9uIGRvbWFpbiBpcyBpZGVudGlm
aWVkIGJ5IG1wbHNMcHNDb25maWdHcm91cE5hbWUuIg0KVGhpcyBzdGF0ZW1lbnQgZG9lcyBub3Qg
c2VlbSB0byBiZSBlbnRpcmVseSBhY2N1cmF0ZSBnaXZlbiB0aGUgTUlCDQpkZXNpZ24gZm9yIDIg
cmVhc29ucywgMS4gIHRoZXJlIGRvZXNuJ3Qgc2VlbSB0byBiZSBhbiBvYmplY3QNCm1wbHNMcHND
b25maWdHcm91cE5hbWUNCmFuZCAyLiB0aGUgSU5ERVggaXMgbXBsc0xwc0NvbmZpZ0RvbWFpbklu
ZGV4IFVuc2lnbmVkMzIgKHdoaWNoIGFsc28gYXBwZWFycw0KaW4gdGhlDQptcGxzTHBzTWVDb25m
aWdFbnRyeSB3aXRoIGEgc3RhdHVzIG9mIG5vdC1hY2Nlc3NpYmxlDQooYW5kIEkgdGhpbmsgeW91
IGludGVuZCBmb3IgaXQgdG8gYmUgYW4gb2JqZWN0KT8NCg0KQXMgYSByZXZpZXdlciwgdGhpcyBp
cyBjb25mdXNpbmcgYmVjYXVzZSB0aGUgcmVsYXRpb25zaGlwIHdpdGgNCnRoZXNlIHRhYmxlcyBp
cyB1bmNsZWFyIGFuZCBzbyBpdCBpcyB2ZXJ5IGRpZmZpY3VsdCB0bw0KcmV2aWV3IHRoZSBNSUIg
TW9kdWxlLiAgUGxlYXNlIGNsYXJpZnkgdGhlIHJlbGF0aW9uc2hpcCB3aXRoDQp0aGVzZSB0YWJs
ZXMgYW5kIHRvIHRoZSBtcGxzT2FtSWRNZVRhYmxlIGluIHRoZQ0KTVBMUy1PQU0tSUQtU1RELU1J
Qi4NCg0KDQoiVGhlIG90aGVyIGF0dHJpYnV0ZXMgaW4gdGhpcyB0YWJsZSIsIGRvIHlvdSBtZWFu
IG9iamVjdHM/DQoNCiogVGhlICBtcGxzTHBzU3RhdHVzVGFibGUNCg0KVGhlcmUgaXMgbm8gbWVu
dGlvbiB0aGF0IHRoZSBtcGxzTHBzU3RhdHVzVGFibGUncyBFbnRyaWVzIGhhdmUgYW4NCkFVR01F
TlRTIHJlbGF0aW9uc2hpcCB3aXRoIHRoZSBtcGxzTHBzQ29uZmlnVGFibGUgRW50cmllcy4gIFBs
ZWFzZSBhZGQuDQoNCjYuMSAgUmVsYXRpb25zaGlwIHRvIHRoZSBNUExTIE9BTSBtYWludGVuYW5j
ZSBpZGVudGlmaWVyIE1JQiBNb2R1bGUNCg0KVGhlIHRpdGxlIG5lZWRzIHRvIGJlIGNhcGl0YWxp
emVkIGNvcnJlY3RseSwgUmVsYXRpb25zaGlwIHRvIHRoZQ0KTVBMUyBPQU0gTWFpbnRlbmFuY2Ug
SWRlbnRpZmllciBNSUIgTW9kdWxlDQoNClBsZWFzZSB1cGRhdGUgdGhpcyBzZWN0aW9uIHRvIHVz
ZSBSRkM3Njk3IChhbmQgaW4gSW5mb3JtYXRpdmUgUmVmZXJlbmNlcw0KYWxzbykNCmluc3RlYWQg
b2YgZHJhZnQtaWV0Zi1tcGxzLXRwLW9hbS1pZC1taWIuDQoNCkFzIG1lbnRpb25lZCBhYm92ZSwg
dGhlIG1wbHNMcHNNZUNvbmZpZ1RhYmxlIGhhcyBhbiBvYmplY3QNCm1wbHNMcHNNZUNvbmZpZ0Rv
bWFpbkluZGV4IHdoaWNoIGlzIChub3QtYWNjZXNzaWJsZSkuDQpJcyB0aGlzIHN1cHBvc2VkIHRv
IGJlIGFuIElOREVYLCBvciBpcyB0aGlzIGFuIG9iamVjdD8gICBJIGFtDQpjb25mdXNlZCBieSB3
aGF0IGlzIGludGVuZGVkLg0KDQo3LiAgRXhhbXBsZSBvZiBQcm90ZWN0aW9uIHN3aXRjaGluZyBj
b25maWd1cmF0aW9uIGZvcg0KDQpNUExTLVRQIFRFIHR1bm5lbCAoUGxlYXNlIGNoYW5nZSB0aXRs
ZTogIEV4YW1wbGUgb2YgUHJvdGVjdGlvbiBTd2l0Y2hpbmcNCkNvbmZpZ3VyYXRpb24pDQoNCiog
SSBhbSB1bmNsZWFyIGhvdyBtcGxzTHNwQ29uZmlnRW50cnkgaXMgYWN0dWFsbHkgY29uZmlndXJl
ZCBmb3INCnVzZSBpbiB0aGlzIGV4YW1wbGUuICAgSXMgYW4gb3BlcmF0b3Igc3VwcG9zZWQgdG8g
cmFuZG9tbHkgY2hvb3NlIGFuIElOREVYDQp2YWx1ZT8NCg0KV291bGQgYW4gSW5kZXhOZXh0IG9i
amVjdCBiZSB1c2VmdWwgdG8gdXNlIGluIGNvbmp1bmN0aW9uIHdpdGggdGhpcyBJTkRFWD8NCg0K
TUlCIE1vZHVsZQ0KLS0tLS0tLS0tLS0tDQoNCihnZW5lcmFsIGNvbW1lbnQ6ICB0aGUgREVTQ1JJ
UFRJT04gY2xhdXNlcyBjb3VsZCBiZSBtb3JlIHJlYWRhYmxlDQppZiBjb25zaXN0ZW5jeSB3YXMg
dXNlZC4gIFNvbWV0aW1lcyB0aGUNCnZhbHVlIGlzIGxpc3RlZCBvbiB0aGUgc2lkZSBhbmQgdGhl
IGRlc2NyaXB0aW9uIGZvbGxvd3Mgb24gdGhlDQpzYW1lIGxpbmUgYW5kIHNvbWV0aW1lcyB0aGUg
dmFsdWUgaXMgbGlzdGVkDQpvbiBhIHNpbmdsZSBsaW5lIGFuZCB0aGUgZGVzY3JpcHRpb24gZm9s
bG93cyBhIGNvdXBsZSBvZiBsaW5lcw0KYWZ0ZXIuICAgUGxlYXNlIGJlIGNvbnNpc3RlbnQuKQ0K
DQoqIG1wbHNMcHNDb25maWdEb21haW5OYW1lICAtLSBJcyB0aGVyZSBhIERFRkFVTFQgdmFsdWUg
Zm9yIHRoaXMNCm9iamVjdD8gICBUaGUgc3RyaW5nIHNpemUgaXMgMS4uMzIgd2l0aCBubw0Kb3B0
aW9uIG9mIDAgbGVuZ3RoIHN0cmluZywgc28gd2FudGVkIHRvIGNoZWNrIGFib3V0IGEgZGVmYXVs
dA0KdmFsdWU/ICBVbmRlciB3aGF0IGNpcmN1bXN0YW5jZXMgY2FuIHRoaXMgdmFsdWUNCmJlIG1v
ZGlmaWVkPyAgIFBsZWFzZSBnaXZlIGEgUkVGRVJFTkNFLg0KDQoqIG1wbHNMcHNDb25maWdNb2Rl
IC0gTmVlZHMgUkVGRVJFTkNFIChhbmQgcGxlYXNlIHRyeSB0byBiZQ0Kc3BlY2lmaWMpLiAgVW5k
ZXIgd2hhdCBjaXJjdW1zdGFuY2VzIGNhbiB0aGlzIGJlIG1vZGlmaWVkPw0KDQoqIG1wbHNMcHND
b25maWdXYWl0VG9SZXN0b3JlDQpXaHkgaXMgdGhpcyBub3QgaW4gbWludXRlcz8gIElmIHNvbWVv
bmUgY29uZmlndXJlcyB0aGlzIHRvIGJlIDMwDQpzZWNvbmRzIGlzIHRoYXQgdmFsaWQ/ICBEb2Vz
bid0IHNlZW0gc28gYmFzZWQgb24gdGhlIERFU0NSSVBUSU9OLiAgUGxlYXNlDQpjbGFyaWZ5Lg0K
DQoqIG1wbHNMcHNDb25maWdIb2xkT2ZmIFdoYXQgaXMgbWVhbnQgYnkgIkNhbiBiZSBjb25maWd1
cmVkIGluDQpzdGVwcyBvZiAxMDA/IiAgIElzIHRoaXMgMTAwIG1pbGxpc2Vjb25kcz8gIElmIHNv
IHRoZW4gbWF5YmUgYSBiZXR0ZXIgdW5pdA0KY2hvaWNlIHdvdWxkIGJlDQpjZW50aXNlY29uZHMu
ICAgUGxlYXNlIGNsYXJpZnkuDQoNCiptcGxzTHBzQ29uZmlnQ29tbWFuZCBpcyByZWFkLXdyaXRl
LiAgSXMgdGhpcyBzdXBwb3NlZCB0byBiZQ0KcmVhZC1jcmVhdGU/DQoNCiptcGxzTHBzQ29uZmln
Um93U3RhdHVzIC0tICBJIHRoaW5rIHRoZXJlIGlzIHNvbWUgY29uZmxpY3RpbmcNCmFkdmljZSBn
aXZlbiB0byB0aGUgb3BlcmF0b3IuICBTZXZlcmFsIG9iamVjdHMgc2F5IHRoYXQgaXQgaXMgZmlu
ZSB0byBjaGFuZ2UNCnRoZQ0KdmFsdWUgb2YgdGhlIG9iamVjdCB3aGVuIFJvd1N0YXR1cyBpcyBh
Y3RpdmUsIGJ1dCB0aGlzIGlzIG5vdCBzcGVjaWZpZWQNCmNvbnNpc3RlbnRseS4gIExpbWl0aW5n
IHRoZQ0KdmFsdWVzIG9mIFJvd1N0YXR1cyBpbiB0aGUgQ29uZm9ybWFuY2UgU2VjdGlvbg0KbWF5
IGJlIHRoZSB3YXkgdG8gZ28uICBQbGVhc2UgY2xhcmlmeS4NCg0KKm1wbHNMcHNNZUNvbmZpZ1N0
YXRlIGlzIGEgcmVhZC1jcmVhdGUuIFRoaXMgaXMgcHJvYmFibHkgb2theSwgYnV0DQphZ2Fpbiwg
dGhhdCBkZXBlbmRzIG9uIGlmIG1wbHNMcHNNZUNvbmZpZ0RvbWFpbkluZGV4DQppcyBhbiBJTkRF
WCBmb3IgdGhpcyB0YWJsZSBnaXZlbiB0aGF0IGl0IGhhcyBhIHN0YXR1cyBvZiBub3QtYWNjZXNz
aWJsZSwNCmV0Yy4NCg0KDQoqbXBsc0xwc01lU3RhdHVzU3dpdGNob3ZlclNlY29uZHMNCk5lZWRz
IGEgdW5pdHMgY2xhdXNlIGZvciBTZWNvbmRzDQoNCg0KTm90aWZpY2F0aW9ucw0KDQpUaGVyZSBh
cmUgYSBjb3VwbGUgTm90aWZpY2F0aW9ucyB0aGF0IGFyZSBzZW5kIHdoZW4gdmFsdWVzIG9mIGNl
cnRhaW4NCmNvdW50ZXJzIGluY3JlbWVudC4gIE1heWJlIHRoaXMgaXMgdmFsaWQsIGJ1dCBpdCBz
ZWVtcyBzdXNwZWN0Lg0KSWYgYSBtYW5hZ2VtZW50IHN0YXRpb25zIG5lZWRzIGluZm9ybWF0aW9u
IG9uIGNvdW50ZXJzLA0Kd2h5IGNhbid0IGl0IGp1c3QgcmV0cmlldmUgdGhlbSBhdCB0aGF0IHBv
aW50PyAgIEkgZG9uJ3Qgc2VlIGFueQ0KY291bnRlciBkaXNjb250aW51aXR5IG9iamVjdHMsIHNv
IHdhcyB3b25kZXJpbmcgYWJvdXQgdGhhdCB0b28uDQoNCiogbXBsc0xwc0V2ZW50Rm9wVGltT3V0
IE5vdGlmaWNhdGlvbg0KDQpQbGVhc2UgcmVuYW1lIHRoaXMgdG8gbXBsc0xwc0V2ZW50Rm9wVGlt
ZW91dA0KDQoqIENvbXBsaWFuY2UvQ29uZm9ybWFuY2UgU2VjdGlvbiBvZiB0aGUgTUlCIE1vZHVs
ZQ0KDQpDdXJyZW50bHksIHRoZXJlIGlzIG9ubHkgRnVsbENvbXBsaWFuY2UuICAgV2h5IGlzIHRo
ZXJlIG5vDQpSZWFkT25seUNvbXBsaWFuY2U/DQoNCi0tLSBlbmQgb2YgY29tbWVudHMgLS0tDQoN
Cg0K


From nobody Wed Apr 20 09:25:39 2016
Return-Path: <vinays@cisco.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 C4B2A12E975 for <mib-doctors@ietfa.amsl.com>; Wed, 20 Apr 2016 09:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.806
X-Spam-Level: 
X-Spam-Status: No, score=-7.806 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2uIFxVh56M3U for <mib-doctors@ietfa.amsl.com>; Wed, 20 Apr 2016 09:25:35 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A52512E8F9 for <mib-doctors@ietf.org>; Wed, 20 Apr 2016 09:25:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=41662; q=dns/txt; s=iport; t=1461169534; x=1462379134; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=EcfcKeK1UlGhLF+cgMO4+bCfJfrJklLlXVL2D6ydoUQ=; b=fXy59HMIZqu++3mK2HNejDQlZVj2eDJBnim8g555WID/+yphp9iHmQP3 eBAaEwjrjz9KHzRcRwKDkSil0C9gPS79SH6+mPRR+qNGEa6WrvIt5j2T4 7py3r62jvvwJ3zW3hKQWSWAH8VqM6ummtuqIqeexWXeAN0ozc3tYCMrkX 0=;
X-IronPort-AV: E=Sophos; i="5.24,510,1454976000"; d="scan'208,217"; a="93981866"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Apr 2016 16:25:34 +0000
Received: from [10.150.29.67] (dhcp-10-150-29-67.cisco.com [10.150.29.67]) (authenticated bits=0) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u3KGPXCa002259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 20 Apr 2016 16:25:33 GMT
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA7519FBEB@AZ-FFEXMB04.global.avaya.com>
From: vinays <vinays@cisco.com>
Message-ID: <5717AD7D.2080609@cisco.com>
Date: Wed, 20 Apr 2016 12:25:33 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA7519FBEB@AZ-FFEXMB04.global.avaya.com>
Content-Type: multipart/alternative; boundary="------------090101060405020604000802"
X-Authenticated-User: vinays
Archived-At: <http://mailarchive.ietf.org/arch/msg/mib-doctors/1tjOLy88jw8-y3ZFs7sszPj7Ggc>
Cc: Vinay Shankarkumar <vinays@cisco.com>, Tim Frost <tim.frost@calnexsol.com>, Greg Dowd <greg.dowd@microsemi.com>, Laurent Montini <lmontini@cisco.com>, "draft-ietf-tictoc-ptp-mib.all@tools.ietf.org" <draft-ietf-tictoc-ptp-mib.all@tools.ietf.org>
Subject: Re: [MIB-DOCTORS] MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 20 Apr 2016 16:25:38 -0000

This is a multi-part message in MIME format.
--------------090101060405020604000802
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit


Thanks Dan for the valuable review and comments.

Please see below for what I have addressed in the MIB module. We will 
make the few changes
needed in the draft also as mentioned.

1. The current compile line lists only 2 errors, which are ok since they 
need the IANA number:

smilint -s -e -l 5 ./PTPBASE-MIB

./PTPBASE-MIB:417: [2] {bad-identifier-case} `XXX' should start with a 
lower case letter
./PTPBASE-MIB:417: [2] {object-identifier-not-prefix} Object identifier 
element `XXX' name only allowed as first element


2.  Have replaced the TEXTUAL CONVENTIONS as you suggested to add 'Ptp' 
prefix.

3. Have changed PtpClockIdentity to a SYNTAX OCTET STRING (SIZE(8))

4. Will replace with SMIv2 and SMIv1.

5. Yes, Intention is to refer to PTPv2 when using PTP. We will clarify this.

6. Have replaced with 'MIB module'.

7. We will address in the draft.

8.  If it is ok, we would prefer to leave this as is. Thanks.

9.  Same for this as well, Thanks

10. Its not an enumeration since there are ranges in the types.

11. Its not an enumeration since there are ranges in the types.

12. Am not sure what we need to change here, Please let us know. Will 
add as you need.

13. Would prefer to leave this as is, Thanks.

14. It can change following any configuration changes, hence would leave 
it as is. Thanks

15. Please help what should be mentioned here? Thanks

16. Same applies here as well since it can change per configuration.

17.  Will clarify in the draft.

18. This is the normal method used to extend for new types and hence 
have used it. Please suggest what needs to be done. Thanks.

19. we will make changes in the draft,

Thanks,
-Vinay.




On 3/23/16 1:58 PM, Romascanu, Dan (Dan) wrote:
> This is the MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt.
> Note that this document has a long history. A MIB Doctor review was 
> performed already by Bert Wijnen back in 2011.
> I do not believe that this document is ready for approval in its 
> current form.
> Here are my findings.
> 1.PARSING
> Using smilint:
> smistrip -d mibs docs/draft-ietf-tictoc-ptp-mib-08.txt
> timeout 10 smilint -s -e -l 5 mibs/PTPBASE-MIB 2>report.txt
>
> You can access any intermediately created files, the processing report 
> (which might be empty if no errors or warnings have been found), and 
> output files (in case of a conversion request) for reading and 
> download from a temporary serverdirectory 
> <http://www.ibr.cs.tu-bs.de/projects/libsmi/tools/tmp/691tQ1/>for 
> approx. 24 hours.
>
> While processing your request the following errors and/or warnings 
> have been found:
>
> mibs/PTPBASE-MIB:426: [2] {bad-identifier-case} `XXX' should start 
> with a lower case letter
> mibs/PTPBASE-MIB:426: [2] {object-identifier-not-prefix} Object 
> identifier element `XXX' name only allowed as first element
> mibs/PTPBASE-MIB:26: [2] {module-identity-registration} illegal module 
> identity registration
> Using smicng (thanks to Bert Wijnen):
>
> C:\bw\smicng\work>smicng ptpbase.inc
>
> Successful parsing
>
> C:\bw\smicng\work>
>
> **** now setup for STRICT checking:
>
> C:\bw\smicng\work>smicstrict
>
> C:\bw\smicng\work>smicng ptpbase.inc
>
> W: f(rfc2863.mi2), (274,17) Item "ifPhysAddress" should have SIZE 
> specified
>
> E: f(rfc2863.mi2), (1092,23) Index item "ifRcvAddressAddress" must be 
> defined with syntax that includes a SIZE
>
> W: f(rfc2863.mi2), (1084,1) Row "ifRcvAddressEntry" has indexing that 
> may create variables with more than 128 sub-ids
>
> W: f(rfc2863.mi2), (1103,17) Item "ifRcvAddressAddress" should have 
> SIZE specified
>
> W: f(rfc2863.mi2), (1146,15) Variable "ifIndex" in notification 
> "linkDown" is an index for a table
>
> W: f(rfc2863.mi2), (1158,15) Variable "ifIndex" in notification 
> "linkUp" is an index for a table
>
> W: f(rfc2863.mi2), (1691,1) OBJECT-GROUP "ifOldObjectsGroup" is not 
> used in a MODULE-COMPLIANCE in current module
>
> E: f(ptpbase.mi2), (413,19) Sub-Id for item "ptpbaseMIB" must be 
> "number" or "name(number)" format
>
> *** 2 errors and 6 warnings in parsing
>
> C:\bw\smicng\work>
>
> As the two errors refer to the RFC 2863 module rather than to the 
> PTBASE-MIB: the compilation seems clean.
> 2.TEXTUAL CONVENTIONS are prefixed differently than the MIB objects. 
> This is not forbidden, but it creates inconsistency. Also the prefix 
> ‘Clock’ for the TCs hints to a more generic functionality, although 
> the TCs seem to be PTP-related. I would suggest prefixing the TCs also 
> with PTP or Ptp
> 3.The following TC
>
> ClockIdentity ::= TEXTUAL-CONVENTION
>
> STATUS          current
>
> DESCRIPTION
>
>         "The clock Identity is an 8-octet array...
>
> REFERENCE       "Section 7.5.2.2.1 from [IEEE
>
> SYNTAX          OCTET STRING (SIZE (1..255))
>
> If this is 8-Octet why is the OCTET STRING size 255?
> 4.I see in the Abstract:
>
>    This memo specifies a MIB module in a manner that is both compliant
>    to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
>    definitions.
>
> Do you actually mean SMIv2 rather than SNMPv2 SMI? I am not sure why 
> this is important, but if this is important, please provide a 
> reference to the document that includes the ‘peer SNMPv1’ definitions 
> (probably SMIv1)
>
> 5.Most of the document speaks about PTP, but in the DESCRIPTION clause 
> at page 7 it mentions:
>
>         [IEEE 1588-2008] defines a protocol enabling precise
>         synchronization of clocks in measurement and control systems
>         implemented with packet-based networks, the Precision Time
>         Protocol Version 2 (PTPv2).  This MIB does not address the
>         earlier version IEEE Std. 1588(TM)-2002 (PTPv1).
>
> So, when it says ‘PTP’ does it mean PTPv2 or any version of PTP? It 
> would be good to clarify.
>
> 6. The document uses the improper terminology ‘MIB’ when it means MIB 
> module. For example ‘Relationship to other Profiles and MIBs’ or ‘This 
> MIB is intended to be used …’ etc., etc.,
>
> 7.Idnits complains about an obsolete reference to RFC 1906:
> -- Obsolete informational reference (is this intentional?): RFC 1906
>      (Obsoleted by RFC 3417)
> 8.I do not believe that Section 3 includes any useful information.
> 9.The DESCRIPTION clause is unusually long and includes a lot of 
> abbreviations, terminology, architectural details and other pieces of 
> information which is not clear why they need to be hardcoded in the 
> MIB module. Maybe the place for all these is in the currently 
> empty-content section 3?
> 10.I do not understand how the ClockPortTransportTypeAddress TC works. 
> If this TC defines an address type why is it not an enumeration? What 
> is the string that for example indicates IPv6? Is it ‘IPv6’? who 
> guarantees that a manager and an agent spell the same? Or is the 
> intention to use the list of identifiers for ‘Well Known transport 
> types for PTP communication’at page 64? If yes, how is this extended? 
> Probably an IANA maintained enumerated TC would be a better solution.
> 11.Why is not the SYNTAX of ClockQualityClassType an enumeration, when 
> the DESCRIPTION indicates clearly that this is an enumeration.
>
> 12.I do not understand how ClockTimeIntervalworks. The example does 
> not help either. It says ‘For example, 2.5 ns is expressed as 0000 
> 0000 0002 8000 in Base16.’ and than the SYNTAX is
>
> SYNTAX          OCTET STRING (SIZE (1..255))
>
> What is the STRING for the object in this example?
> 13.For objects like ptpDomainIndex there is no need to copy again the 
> possible values in the DESCRIPTION clause, because these are already 
> listed in the TC.
> 14.Why is ptpDomainClockPortsTotal of SYNTAX Gauge32? Does this value 
> change all the time? Does it latch at a max value?
> 15.There is no indication of behavior for counter discontinuity, or 
> object for counter discontinuity – see section 4.6.1.2 in RFC 4181
> 16.Why is the SYNATX of ptpbaseClockTransDefaultDSNumOfPorts 
> Counter32? This does not seem to be a counter, but an unsigned integer.
>
> 17.The DESCRIPTION clause of the ptpbaseClockPortDSPTPVersion objects 
> reads: "This object specifies the PTP version being used.” However, 
> the DESCRIPTION clause of the MIB module says that this module refers 
> only to PTPv2. So what does this object stand for? And in any case, 
> how is this coded? (1) for v1 and (2) for v2? Then why is it not an 
> enumerated value?
>
> 18.How does ptpbaseClockPortAssociateAddressType work? What would be 
> included under the AutonomousType SYNTAX to make possible 
> interoperability?
>
> 19.The Security Considerations section does not follow the template 
> defined at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security.
>
> I hope this helps.
>
> Regards,
>
> Dan
>


--------------090101060405020604000802
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    Thanks Dan for the valuable review and comments.<br>
    <br>
    Please see below for what I have addressed in the MIB module. We
    will make the few changes<br>
    needed in the draft also as mentioned.<br>
    <br>
    1. The current compile line lists only 2 errors, which are ok since
    they need the IANA number:<br>
    <br>
    smilint -s -e -l 5 ./PTPBASE-MIB<br>
    <br>
    ./PTPBASE-MIB:417: [2] {bad-identifier-case} `XXX' should start with
    a lower case letter<br>
    ./PTPBASE-MIB:417: [2] {object-identifier-not-prefix} Object
    identifier element `XXX' name only allowed as first element<br>
    <br>
    <br>
    2.  Have replaced the TEXTUAL CONVENTIONS as you suggested to add
    'Ptp' prefix.<br>
    <br>
    3. Have changed PtpClockIdentity to a SYNTAX OCTET STRING (SIZE(8))<br>
    <br>
    4. Will replace with SMIv2 and SMIv1.<br>
    <br>
    5. Yes, Intention is to refer to PTPv2 when using PTP. We will
    clarify this.<br>
    <br>
    6. Have replaced with 'MIB module'.<br>
    <br>
    7. We will address in the draft.<br>
    <br>
    8.  If it is ok, we would prefer to leave this as is. Thanks.<br>
    <br>
    9.  Same for this as well, Thanks<br>
    <br>
    10. Its not an enumeration since there are ranges in the types.<br>
    <br>
    11. Its not an enumeration since there are ranges in the types.<br>
    <br>
    12. Am not sure what we need to change here, Please let us know.
    Will add as you need.<br>
    <br>
    13. Would prefer to leave this as is, Thanks.<br>
    <br>
    14. It can change following any configuration changes, hence would
    leave it as is. Thanks<br>
    <br>
    15. Please help what should be mentioned here? Thanks<br>
    <br>
    16. Same applies here as well since it can change per configuration.<br>
    <br>
    17.  Will clarify in the draft.<br>
    <br>
    18. This is the normal method used to extend for new types and hence
    have used it. Please suggest what needs to be done. Thanks.<br>
    <br>
    19. we will make changes in the draft,<br>
    <br>
    Thanks,<br>
    -Vinay.<br>
    <br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 3/23/16 1:58 PM, Romascanu, Dan
      (Dan) wrote:<br>
    </div>
    <blockquote
cite="mid:9904FB1B0159DA42B0B887B7FA8119CA7519FBEB@AZ-FFEXMB04.global.avaya.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2099474858;
	mso-list-type:hybrid;
	mso-list-template-ids:-1068084126 -1890702922 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:25.5pt;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:61.5pt;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:97.5pt;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:133.5pt;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:169.5pt;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:205.5pt;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:241.5pt;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:277.5pt;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:313.5pt;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">This is the MIB Doctor Review for <span style="color:black">draft-ietf-tictoc-ptp-mib-08.txt. <o:p></o:p></span></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Note that this document has a long history. A MIB Doctor review was performed already by Bert Wijnen back in 2011. <o:p></o:p></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">I do not believe that this document is ready for approval in its current form. <o:p></o:p></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Here are my findings. <o:p></o:p></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p> </o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">1.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">PARSING<o:p></o:p></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Using smilint:<o:p></o:p></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">smistrip -d mibs docs/draft-ietf-tictoc-ptp-mib-08.txt<o:p></o:p></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">timeout 10 smilint -s -e -l 5 mibs/PTPBASE-MIB 2&gt;report.txt<o:p></o:p></span></pre>
        <p
          style="margin:7.5pt;text-align:justify;background:white;orphans:
          auto;widows: 1;-webkit-text-stroke-width:
          0px;word-spacing:0px">
          <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">You
            can access any intermediately created files, the processing
            report (which might be empty if no errors or warnings have
            been found), and output files (in case of a conversion
            request) for reading and download from a temporary server<span
              class="apple-converted-space"> </span><a
              moz-do-not-send="true"
              href="http://www.ibr.cs.tu-bs.de/projects/libsmi/tools/tmp/691tQ1/"><span
                style="color:#990000">directory</span></a><span
              class="apple-converted-space"> </span>for approx. 24
            hours.<o:p></o:p></span></p>
        <p
          style="margin:7.5pt;text-align:justify;background:white;orphans:
          auto;widows: 1;-webkit-text-stroke-width:
          0px;word-spacing:0px">
          <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">While
            processing your request the following errors and/or warnings
            have been found:<o:p></o:p></span></p>
        <pre style="margin:7.5pt;text-align:justify;background:white;orphans: auto;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">mibs/PTPBASE-MIB:426: [2] {bad-identifier-case} `XXX' should start with a lower case letter<o:p></o:p></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">mibs/PTPBASE-MIB:426: [2] {object-identifier-not-prefix} Object identifier element `XXX' name only allowed as first element<o:p></o:p></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">mibs/PTPBASE-MIB:26: [2] {module-identity-registration} illegal module identity registration<o:p></o:p></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Using smicng (thanks to Bert Wijnen):<o:p></o:p></span></pre>
        <p class="MsoPlainText">C:\bw\smicng\work&gt;smicng ptpbase.inc<o:p></o:p></p>
        <p class="MsoPlainText">Successful parsing<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">C:\bw\smicng\work&gt;<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">**** now setup for STRICT checking:<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">C:\bw\smicng\work&gt;smicstrict<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">C:\bw\smicng\work&gt;smicng ptpbase.inc<o:p></o:p></p>
        <p class="MsoPlainText">W: f(rfc2863.mi2), (274,17) Item
          "ifPhysAddress" should have SIZE specified<o:p></o:p></p>
        <p class="MsoPlainText">E: f(rfc2863.mi2), (1092,23) Index item
          "ifRcvAddressAddress" must be defined with syntax that
          includes a SIZE<o:p></o:p></p>
        <p class="MsoPlainText">W: f(rfc2863.mi2), (1084,1) Row
          "ifRcvAddressEntry" has indexing that may create variables
          with more than 128 sub-ids<o:p></o:p></p>
        <p class="MsoPlainText">W: f(rfc2863.mi2), (1103,17) Item
          "ifRcvAddressAddress" should have SIZE specified<o:p></o:p></p>
        <p class="MsoPlainText">W: f(rfc2863.mi2), (1146,15) Variable
          "ifIndex" in notification "linkDown" is an index for a table<o:p></o:p></p>
        <p class="MsoPlainText">W: f(rfc2863.mi2), (1158,15) Variable
          "ifIndex" in notification "linkUp" is an index for a table<o:p></o:p></p>
        <p class="MsoPlainText">W: f(rfc2863.mi2), (1691,1) OBJECT-GROUP
          "ifOldObjectsGroup" is not used in a MODULE-COMPLIANCE in
          current module<o:p></o:p></p>
        <p class="MsoPlainText">E: f(ptpbase.mi2), (413,19) Sub-Id for
          item "ptpbaseMIB" must be "number" or "name(number)" format<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">*** 2 errors and 6 warnings in parsing<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">C:\bw\smicng\work&gt;<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:0cm;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">As the two errors refer to the RFC 2863 module rather than to the PTBASE-MIB: the compilation seems clean. <o:p></o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">2.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">TEXTUAL CONVENTIONS are prefixed differently than the MIB objects. This is not forbidden, but it creates inconsistency. Also the prefix ‘Clock’ for the TCs hints to a more generic functionality, although the TCs seem to be PTP-related. I would suggest prefixing the TCs also with PTP or Ptp<o:p></o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">3.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">The following TC<o:p></o:p></span></pre>
        <p class="MsoPlainText" style="margin-left:7.5pt">ClockIdentity
          ::= TEXTUAL-CONVENTION<o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:7.5pt">   
          STATUS          current<o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:7.5pt">   
          DESCRIPTION<o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:7.5pt">        "The
          clock Identity is an 8-octet array...<o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:7.5pt">   
          REFERENCE       "Section 7.5.2.2.1 from [IEEE<o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:7.5pt">   
          SYNTAX          OCTET STRING (SIZE (1..255))<o:p></o:p></p>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:0cm;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">If this is 8-Octet why is the OCTET STRING size 255?<o:p></o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">4.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">I see in the Abstract: <o:p></o:p></span></pre>
        <p class="MsoPlainText" style="margin-left:7.5pt">   This memo
          specifies a MIB module in a manner that is both compliant<br>
             to the SNMPv2 SMI, and semantically identical to the peer
          SNMPv1<br>
             definitions.<o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:7.5pt"><o:p> </o:p></p>
        <p class="MsoPlainText" style="margin-left:7.5pt">Do you
          actually mean SMIv2 rather than SNMPv2 SMI? I am not sure why
          this is important, but if this is important, please provide a
          reference to the document that includes the ‘peer SNMPv1’
          definitions (probably SMIv1)<o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:7.5pt"><o:p> </o:p></p>
        <p class="MsoPlainText"
          style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo2">
          <!--[if !supportLists]--><span style="mso-list:Ignore">5.<span
              style="font:7.0pt &quot;Times New Roman&quot;">      
            </span></span><!--[endif]--><span dir="LTR"></span>Most of
          the document speaks about PTP, but in the DESCRIPTION clause
          at page 7 it mentions:<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">        [IEEE 1588-2008] defines a
          protocol enabling precise<br>
                  synchronization of clocks in measurement and control
          systems<br>
                  implemented with packet-based networks, the Precision
          Time<br>
                  Protocol Version 2 (PTPv2).  This MIB does not address
          the<br>
                  earlier version IEEE Std. 1588(TM)-2002 (PTPv1).  <o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">So, when it says ‘PTP’ does it mean
          PTPv2 or any version of PTP? It would be good to clarify.<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText"
          style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo2">
          <!--[if !supportLists]--><span style="mso-list:Ignore">6.<span
              style="font:7.0pt &quot;Times New Roman&quot;">      
            </span></span><!--[endif]--><span dir="LTR"></span> The
          document uses the improper terminology ‘MIB’ when it means MIB
          module. For example ‘Relationship to other Profiles and MIBs’
          or ‘This MIB is intended to be used …’ etc., etc.,
          <o:p></o:p></p>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">7.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Idnits complains about an obsolete reference to RFC 1906: <o:p></o:p></span></pre>
        <pre style="margin-left:7.5pt"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">-- Obsolete informational reference (is this intentional?): RFC 1906<o:p></o:p></span></pre>
        <pre style="margin-left:7.5pt"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">     (Obsoleted by RFC 3417)<o:p></o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">8.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">I do not believe that Section 3 includes any useful information. <o:p></o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">9.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">The DESCRIPTION clause is unusually long and includes a lot of abbreviations, terminology, architectural details and other pieces of information which is not clear why they need to be hardcoded in the MIB module. Maybe the place for all these is in the currently empty-content section 3? <o:p></o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">10.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">I do not understand how the </span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">ClockPortTransportTypeAddress TC works. If this TC defines an address type why is it not an enumeration? What is the string that for example indicates IPv6? Is it ‘IPv6’? who guarantees that a manager and an agent spell the same? Or is the intention to use the list of identifiers for ‘Well Known transport types for PTP comm
 u
nication’at page 64? If yes, how is this extended? Probably an IANA maintained enumerated TC would be a better solution.  <span style="color:black"><o:p></o:p></span></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">11.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Why is not the SYNTAX of </span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">ClockQualityClassType an enumeration, when the DESCRIPTION indicates clearly that this is an enumeration. <span style="color:black"><o:p></o:p></span></span></pre>
        <p class="MsoPlainText"
          style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo2">
          <!--[if !supportLists]--><span style="mso-list:Ignore">12.<span
              style="font:7.0pt &quot;Times New Roman&quot;">  
            </span></span><!--[endif]--><span dir="LTR"></span>I do not
          understand how <span
            style="font-size:10.5pt;font-family:&quot;Courier New&quot;">
            ClockTimeInterval</span><span style="font-size:10.5pt">
            works. The example does not help either. It says ‘</span><span
            style="font-family:&quot;Courier New&quot;">For example, 2.5
            ns is expressed as 0000 0000 0002 8000 in Base16.’ and than
            the SYNTAX is
          </span><o:p></o:p></p>
        <p class="MsoPlainText"><span style="font-family:&quot;Courier
            New&quot;">SYNTAX          OCTET STRING (SIZE (1..255))</span><o:p></o:p></p>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:0cm;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">What is the STRING for the object in this example? <o:p></o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">13.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">For objects like ptpDomainIndex there is no need to copy again the possible values in the DESCRIPTION clause, because these are already listed in the TC.<o:p></o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">14.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Why is </span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">ptpDomainClockPortsTotal of SYNTAX Gauge32? Does this value change all the time? Does it latch at a max value? <span style="color:black"><o:p></o:p></span></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">15.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">There is no indication of behavior for counter discontinuity, or object for counter discontinuity – see section 4.6.1.2 in RFC 4181<o:p></o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">16.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Why is the SYNATX of </span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">ptpbaseClockTransDefaultDSNumOfPorts Counter32? This does not seem to be a counter, but an unsigned integer.<span style="color:black"><o:p></o:p></span></span></pre>
        <p class="MsoPlainText"
          style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo2">
          <!--[if !supportLists]--><span style="mso-list:Ignore">17.<span
              style="font:7.0pt &quot;Times New Roman&quot;">  
            </span></span><!--[endif]--><span dir="LTR"></span><span
            style="color:black">The DESCRIPTION clause of the
          </span>ptpbaseClockPortDSPTPVersion objects reads: "This
          object specifies the PTP version being used.” However, the
          DESCRIPTION clause of the MIB module says that this module
          refers only to PTPv2. So what does this object stand for? And
          in any case, how is this coded? (1) for v1 and (2) for v2?
          Then why is it not an enumerated value? <o:p>
          </o:p></p>
        <p class="MsoPlainText"
          style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo2">
          <!--[if !supportLists]--><span style="mso-list:Ignore">18.<span
              style="font:7.0pt &quot;Times New Roman&quot;">  
            </span></span><!--[endif]--><span dir="LTR"></span>How does
          ptpbaseClockPortAssociateAddressType work? What would be
          included under the AutonomousType SYNTAX to make possible
          interoperability?
          <o:p></o:p></p>
        <p class="MsoPlainText"
          style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo2">
          <!--[if !supportLists]--><span style="mso-list:Ignore">19.<span
              style="font:7.0pt &quot;Times New Roman&quot;">  
            </span></span><!--[endif]--><span dir="LTR"></span>The
          Security Considerations section does not follow the template
          defined at
          <a moz-do-not-send="true"
            href="http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security">http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security</a>.
          <o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:25.5pt"><o:p> </o:p></p>
        <p class="MsoPlainText" style="margin-left:25.5pt">I hope this
          helps. <o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:25.5pt"><o:p> </o:p></p>
        <p class="MsoPlainText" style="margin-left:25.5pt">Regards,<o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:25.5pt"><o:p> </o:p></p>
        <p class="MsoPlainText" style="margin-left:25.5pt">Dan<o:p></o:p></p>
        <p class="MsoPlainText" style="margin-left:25.5pt"><o:p> </o:p></p>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:0cm;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p> </o:p></span></pre>
        <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:0cm;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p> </o:p></span></pre>
        <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p> </o:p></span></pre>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------090101060405020604000802--


From nobody Wed Apr 20 19:41:51 2016
Return-Path: <vinays@cisco.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 CCF2B12E8E8 for <mib-doctors@ietfa.amsl.com>; Wed, 20 Apr 2016 19:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.806
X-Spam-Level: 
X-Spam-Status: No, score=-7.806 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6nBuulrPqfpC for <mib-doctors@ietfa.amsl.com>; Wed, 20 Apr 2016 19:41:46 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5ED412E8EC for <mib-doctors@ietf.org>; Wed, 20 Apr 2016 19:41:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=44032; q=dns/txt; s=iport; t=1461206505; x=1462416105; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=qdH35I//JCp+L7W4AgewREsEagk/7csYHvGbuBSGkZE=; b=ZHw3up+jmt6+pAZwMszAEYlWXoOLa1dZD5w7wqIPwfi5UUvN839fgRDR o39UzD+Vf77o0hNpEScj47zj9uDcgAeIjseGIG4EZlr+MBq+LML6WHcqr 4JyLv9Xow7ZMtEr7IYJgEP6ctoi2Qu/fI+E638uPtC3ZItB9i4ZColfc3 s=;
X-IronPort-AV: E=Sophos;i="5.24,512,1454976000";  d="scan'208,217";a="264214686"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Apr 2016 02:41:45 +0000
Received: from [10.82.241.140] (rtp-vpn2-396.cisco.com [10.82.241.140]) (authenticated bits=0) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u3L2fhAU005810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 21 Apr 2016 02:41:44 GMT
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Benoit Claise <bclaise@cisco.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA7519FBEB@AZ-FFEXMB04.global.avaya.com> <5717AD7D.2080609@cisco.com>
From: vinays <vinays@cisco.com>
Message-ID: <57183DE7.3060507@cisco.com>
Date: Wed, 20 Apr 2016 22:41:43 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <5717AD7D.2080609@cisco.com>
Content-Type: multipart/alternative; boundary="------------040007010809010207060802"
X-Authenticated-User: vinays
Archived-At: <http://mailarchive.ietf.org/arch/msg/mib-doctors/uutdnVjdUS6pGRaY6qEtvLliQy0>
Cc: Tim Frost <tim.frost@calnexsol.com>, Greg Dowd <greg.dowd@microsemi.com>, Karen O'Donoghue <odonoghue@isoc.org>, Vinay Shankarkumar <vinays@cisco.com>, Laurent Montini <lmontini@cisco.com>, "draft-ietf-tictoc-ptp-mib.all@tools.ietf.org" <draft-ietf-tictoc-ptp-mib.all@tools.ietf.org>
Subject: Re: [MIB-DOCTORS] MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Apr 2016 02:41:50 -0000

This is a multi-part message in MIME format.
--------------040007010809010207060802
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit


(Adding Benoit; Dan is on vacation)

We have addressed the MIB doctor review comments as described. We have 
addressed the Gen-ART reviewer comments from Peter Yee also.

Tim will be addressing the editorial comments in the draft and submit a 
new version tomorrow 4/21 (early morning UK time), so as to make it 
before the telechat. Appreciate all the valuable feedback and comments 
to see this through,


Thanks,
-Vinay.


On 4/20/16 12:25 PM, vinays wrote:
>
> Thanks Dan for the valuable review and comments.
>
> Please see below for what I have addressed in the MIB module. We will 
> make the few changes
> needed in the draft also as mentioned.
>
> 1. The current compile line lists only 2 errors, which are ok since 
> they need the IANA number:
>
> smilint -s -e -l 5 ./PTPBASE-MIB
>
> ./PTPBASE-MIB:417: [2] {bad-identifier-case} `XXX' should start with a 
> lower case letter
> ./PTPBASE-MIB:417: [2] {object-identifier-not-prefix} Object 
> identifier element `XXX' name only allowed as first element
>
>
> 2.  Have replaced the TEXTUAL CONVENTIONS as you suggested to add 
> 'Ptp' prefix.
>
> 3. Have changed PtpClockIdentity to a SYNTAX OCTET STRING (SIZE(8))
>
> 4. Will replace with SMIv2 and SMIv1.
>
> 5. Yes, Intention is to refer to PTPv2 when using PTP. We will clarify 
> this.
>
> 6. Have replaced with 'MIB module'.
>
> 7. We will address in the draft.
>
> 8.  If it is ok, we would prefer to leave this as is. Thanks.
>
> 9.  Same for this as well, Thanks
>
> 10. Its not an enumeration since there are ranges in the types.
>
> 11. Its not an enumeration since there are ranges in the types.
>
> 12. Am not sure what we need to change here, Please let us know. Will 
> add as you need.
>
> 13. Would prefer to leave this as is, Thanks.
>
> 14. It can change following any configuration changes, hence would 
> leave it as is. Thanks
>
> 15. Please help what should be mentioned here? Thanks
>
> 16. Same applies here as well since it can change per configuration.
>
> 17.  Will clarify in the draft.
>
> 18. This is the normal method used to extend for new types and hence 
> have used it. Please suggest what needs to be done. Thanks.
>
> 19. we will make changes in the draft,
>
> Thanks,
> -Vinay.
>
>
>
>
> On 3/23/16 1:58 PM, Romascanu, Dan (Dan) wrote:
>> This is the MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt.
>> Note that this document has a long history. A MIB Doctor review was 
>> performed already by Bert Wijnen back in 2011.
>> I do not believe that this document is ready for approval in its 
>> current form.
>> Here are my findings.
>> 1.PARSING
>> Using smilint:
>> smistrip -d mibs docs/draft-ietf-tictoc-ptp-mib-08.txt
>> timeout 10 smilint -s -e -l 5 mibs/PTPBASE-MIB 2>report.txt
>>
>> You can access any intermediately created files, the processing 
>> report (which might be empty if no errors or warnings have been 
>> found), and output files (in case of a conversion request) for 
>> reading and download from a temporary serverdirectory 
>> <http://www.ibr.cs.tu-bs.de/projects/libsmi/tools/tmp/691tQ1/>for 
>> approx. 24 hours.
>>
>> While processing your request the following errors and/or warnings 
>> have been found:
>>
>> mibs/PTPBASE-MIB:426: [2] {bad-identifier-case} `XXX' should start 
>> with a lower case letter
>> mibs/PTPBASE-MIB:426: [2] {object-identifier-not-prefix} Object 
>> identifier element `XXX' name only allowed as first element
>> mibs/PTPBASE-MIB:26: [2] {module-identity-registration} illegal 
>> module identity registration
>> Using smicng (thanks to Bert Wijnen):
>>
>> C:\bw\smicng\work>smicng ptpbase.inc
>>
>> Successful parsing
>>
>> C:\bw\smicng\work>
>>
>> **** now setup for STRICT checking:
>>
>> C:\bw\smicng\work>smicstrict
>>
>> C:\bw\smicng\work>smicng ptpbase.inc
>>
>> W: f(rfc2863.mi2), (274,17) Item "ifPhysAddress" should have SIZE 
>> specified
>>
>> E: f(rfc2863.mi2), (1092,23) Index item "ifRcvAddressAddress" must be 
>> defined with syntax that includes a SIZE
>>
>> W: f(rfc2863.mi2), (1084,1) Row "ifRcvAddressEntry" has indexing that 
>> may create variables with more than 128 sub-ids
>>
>> W: f(rfc2863.mi2), (1103,17) Item "ifRcvAddressAddress" should have 
>> SIZE specified
>>
>> W: f(rfc2863.mi2), (1146,15) Variable "ifIndex" in notification 
>> "linkDown" is an index for a table
>>
>> W: f(rfc2863.mi2), (1158,15) Variable "ifIndex" in notification 
>> "linkUp" is an index for a table
>>
>> W: f(rfc2863.mi2), (1691,1) OBJECT-GROUP "ifOldObjectsGroup" is not 
>> used in a MODULE-COMPLIANCE in current module
>>
>> E: f(ptpbase.mi2), (413,19) Sub-Id for item "ptpbaseMIB" must be 
>> "number" or "name(number)" format
>>
>> *** 2 errors and 6 warnings in parsing
>>
>> C:\bw\smicng\work>
>>
>> As the two errors refer to the RFC 2863 module rather than to the 
>> PTBASE-MIB: the compilation seems clean.
>> 2.TEXTUAL CONVENTIONS are prefixed differently than the MIB objects. 
>> This is not forbidden, but it creates inconsistency. Also the prefix 
>> ‘Clock’ for the TCs hints to a more generic functionality, although 
>> the TCs seem to be PTP-related. I would suggest prefixing the TCs 
>> also with PTP or Ptp
>> 3.The following TC
>>
>> ClockIdentity ::= TEXTUAL-CONVENTION
>>
>> STATUS          current
>>
>> DESCRIPTION
>>
>>         "The clock Identity is an 8-octet array...
>>
>> REFERENCE       "Section 7.5.2.2.1 from [IEEE
>>
>> SYNTAX          OCTET STRING (SIZE (1..255))
>>
>> If this is 8-Octet why is the OCTET STRING size 255?
>> 4.I see in the Abstract:
>>
>>    This memo specifies a MIB module in a manner that is both compliant
>>    to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
>>    definitions.
>>
>> Do you actually mean SMIv2 rather than SNMPv2 SMI? I am not sure why 
>> this is important, but if this is important, please provide a 
>> reference to the document that includes the ‘peer SNMPv1’ definitions 
>> (probably SMIv1)
>>
>> 5.Most of the document speaks about PTP, but in the DESCRIPTION 
>> clause at page 7 it mentions:
>>
>>         [IEEE 1588-2008] defines a protocol enabling precise
>>         synchronization of clocks in measurement and control systems
>>         implemented with packet-based networks, the Precision Time
>>         Protocol Version 2 (PTPv2).  This MIB does not address the
>>         earlier version IEEE Std. 1588(TM)-2002 (PTPv1).
>>
>> So, when it says ‘PTP’ does it mean PTPv2 or any version of PTP? It 
>> would be good to clarify.
>>
>> 6. The document uses the improper terminology ‘MIB’ when it means MIB 
>> module. For example ‘Relationship to other Profiles and MIBs’ or 
>> ‘This MIB is intended to be used …’ etc., etc.,
>>
>> 7.Idnits complains about an obsolete reference to RFC 1906:
>> -- Obsolete informational reference (is this intentional?): RFC 1906
>>      (Obsoleted by RFC 3417)
>> 8.I do not believe that Section 3 includes any useful information.
>> 9.The DESCRIPTION clause is unusually long and includes a lot of 
>> abbreviations, terminology, architectural details and other pieces of 
>> information which is not clear why they need to be hardcoded in the 
>> MIB module. Maybe the place for all these is in the currently 
>> empty-content section 3?
>> 10.I do not understand how the ClockPortTransportTypeAddress TC 
>> works. If this TC defines an address type why is it not an 
>> enumeration? What is the string that for example indicates IPv6? Is 
>> it ‘IPv6’? who guarantees that a manager and an agent spell the same? 
>> Or is the intention to use the list of identifiers for ‘Well Known 
>> transport types for PTP commu nication’at page 64? If yes, how is 
>> this extended? Probably an IANA maintained enumerated TC would be a 
>> better solution.
>> 11.Why is not the SYNTAX of ClockQualityClassType an enumeration, 
>> when the DESCRIPTION indicates clearly that this is an enumeration.
>>
>> 12.I do not understand how ClockTimeIntervalworks. The example does 
>> not help either. It says ‘For example, 2.5 ns is expressed as 0000 
>> 0000 0002 8000 in Base16.’ and than the SYNTAX is
>>
>> SYNTAX          OCTET STRING (SIZE (1..255))
>>
>> What is the STRING for the object in this example?
>> 13.For objects like ptpDomainIndex there is no need to copy again the 
>> possible values in the DESCRIPTION clause, because these are already 
>> listed in the TC.
>> 14.Why is ptpDomainClockPortsTotal of SYNTAX Gauge32? Does this value 
>> change all the time? Does it latch at a max value?
>> 15.There is no indication of behavior for counter discontinuity, or 
>> object for counter discontinuity – see section 4.6.1.2 in RFC 4181
>> 16.Why is the SYNATX of ptpbaseClockTransDefaultDSNumOfPorts 
>> Counter32? This does not seem to be a counter, but an unsigned integer.
>>
>> 17.The DESCRIPTION clause of the ptpbaseClockPortDSPTPVersion objects 
>> reads: "This object specifies the PTP version being used.” However, 
>> the DESCRIPTION clause of the MIB module says that this module refers 
>> only to PTPv2. So what does this object stand for? And in any case, 
>> how is this coded? (1) for v1 and (2) for v2? Then why is it not an 
>> enumerated value?
>>
>> 18.How does ptpbaseClockPortAssociateAddressType work? What would be 
>> included under the AutonomousType SYNTAX to make possible 
>> interoperability?
>>
>> 19.The Security Considerations section does not follow the template 
>> defined at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security.
>>
>> I hope this helps.
>>
>> Regards,
>>
>> Dan
>>
>


--------------040007010809010207060802
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <big><font face="Times New Roman">(Adding Benoit; Dan is on
        vacation)<br>
        <br>
        We have addressed the MIB doctor review comments as described.
        We have addressed the </font></big>Gen-ART reviewer comments
    from Peter Yee also.<br>
    <pre wrap=""><big><font face="Times New Roman">
Tim will be addressing the editorial comments in the draft and submit a new version tomorrow 4/21 (early morning UK time), so as to make it before the telechat.

Appreciate all the valuable feedback and comments to see this through,
</font></big></pre>
    <big><font face="Times New Roman"><br>
        Thanks,<br>
        -Vinay.<br>
      </font></big><br>
    <br>
    <div class="moz-cite-prefix">On 4/20/16 12:25 PM, vinays wrote:<br>
    </div>
    <blockquote cite="mid:5717AD7D.2080609@cisco.com" type="cite">
      <meta content="text/html; charset=windows-1252"
        http-equiv="Content-Type">
      <br>
      Thanks Dan for the valuable review and comments.<br>
      <br>
      Please see below for what I have addressed in the MIB module. We
      will make the few changes<br>
      needed in the draft also as mentioned.<br>
      <br>
      1. The current compile line lists only 2 errors, which are ok
      since they need the IANA number:<br>
      <br>
      smilint -s -e -l 5 ./PTPBASE-MIB<br>
      <br>
      ./PTPBASE-MIB:417: [2] {bad-identifier-case} `XXX' should start
      with a lower case letter<br>
      ./PTPBASE-MIB:417: [2] {object-identifier-not-prefix} Object
      identifier element `XXX' name only allowed as first element<br>
      <br>
      <br>
      2.  Have replaced the TEXTUAL CONVENTIONS as you suggested to add
      'Ptp' prefix.<br>
      <br>
      3. Have changed PtpClockIdentity to a SYNTAX OCTET STRING
      (SIZE(8))<br>
      <br>
      4. Will replace with SMIv2 and SMIv1.<br>
      <br>
      5. Yes, Intention is to refer to PTPv2 when using PTP. We will
      clarify this.<br>
      <br>
      6. Have replaced with 'MIB module'.<br>
      <br>
      7. We will address in the draft.<br>
      <br>
      8.  If it is ok, we would prefer to leave this as is. Thanks.<br>
      <br>
      9.  Same for this as well, Thanks<br>
      <br>
      10. Its not an enumeration since there are ranges in the types.<br>
      <br>
      11. Its not an enumeration since there are ranges in the types.<br>
      <br>
      12. Am not sure what we need to change here, Please let us know.
      Will add as you need.<br>
      <br>
      13. Would prefer to leave this as is, Thanks.<br>
      <br>
      14. It can change following any configuration changes, hence would
      leave it as is. Thanks<br>
      <br>
      15. Please help what should be mentioned here? Thanks<br>
      <br>
      16. Same applies here as well since it can change per
      configuration.<br>
      <br>
      17.  Will clarify in the draft.<br>
      <br>
      18. This is the normal method used to extend for new types and
      hence have used it. Please suggest what needs to be done. Thanks.<br>
      <br>
      19. we will make changes in the draft,<br>
      <br>
      Thanks,<br>
      -Vinay.<br>
      <br>
      <br>
      <br>
      <br>
      <div class="moz-cite-prefix">On 3/23/16 1:58 PM, Romascanu, Dan
        (Dan) wrote:<br>
      </div>
      <blockquote
cite="mid:9904FB1B0159DA42B0B887B7FA8119CA7519FBEB@AZ-FFEXMB04.global.avaya.com"
        type="cite">
        <meta http-equiv="Content-Type" content="text/html;
          charset=windows-1252">
        <meta name="Generator" content="Microsoft Word 14 (filtered
          medium)">
        <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2099474858;
	mso-list-type:hybrid;
	mso-list-template-ids:-1068084126 -1890702922 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:25.5pt;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:61.5pt;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:97.5pt;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:133.5pt;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:169.5pt;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:205.5pt;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:241.5pt;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:277.5pt;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:313.5pt;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
        <div class="WordSection1">
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">This is the MIB Doctor Review for <span style="color:black">draft-ietf-tictoc-ptp-mib-08.txt. <o:p></o:p></span></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Note that this document has a long history. A MIB Doctor review was performed already by Bert Wijnen back in 2011. <o:p></o:p></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">I do not believe that this document is ready for approval in its current form. <o:p></o:p></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Here are my findings. <o:p></o:p></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p> </o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">1.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">PARSING<o:p></o:p></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Using smilint:<o:p></o:p></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">smistrip -d mibs docs/draft-ietf-tictoc-ptp-mib-08.txt<o:p></o:p></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">timeout 10 smilint -s -e -l 5 mibs/PTPBASE-MIB 2&gt;report.txt<o:p></o:p></span></pre>
          <p
            style="margin:7.5pt;text-align:justify;background:white;orphans:
            auto;widows: 1;-webkit-text-stroke-width:
            0px;word-spacing:0px"> <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">You

              can access any intermediately created files, the
              processing report (which might be empty if no errors or
              warnings have been found), and output files (in case of a
              conversion request) for reading and download from a
              temporary server<span class="apple-converted-space"> </span><a
                moz-do-not-send="true"
                href="http://www.ibr.cs.tu-bs.de/projects/libsmi/tools/tmp/691tQ1/"><span
                  style="color:#990000">directory</span></a><span
                class="apple-converted-space"> </span>for approx. 24
              hours.<o:p></o:p></span></p>
          <p
            style="margin:7.5pt;text-align:justify;background:white;orphans:
            auto;widows: 1;-webkit-text-stroke-width:
            0px;word-spacing:0px"> <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">While

              processing your request the following errors and/or
              warnings have been found:<o:p></o:p></span></p>
          <pre style="margin:7.5pt;text-align:justify;background:white;orphans: auto;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">mibs/PTPBASE-MIB:426: [2] {bad-identifier-case} `XXX' should start with a lower case letter<o:p></o:p></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">mibs/PTPBASE-MIB:426: [2] {object-identifier-not-prefix} Object identifier element `XXX' name only allowed as first element<o:p></o:p></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">mibs/PTPBASE-MIB:26: [2] {module-identity-registration} illegal module identity registration<o:p></o:p></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Using smicng (thanks to Bert Wijnen):<o:p></o:p></span></pre>
          <p class="MsoPlainText">C:\bw\smicng\work&gt;smicng
            ptpbase.inc<o:p></o:p></p>
          <p class="MsoPlainText">Successful parsing<o:p></o:p></p>
          <p class="MsoPlainText"><o:p> </o:p></p>
          <p class="MsoPlainText">C:\bw\smicng\work&gt;<o:p></o:p></p>
          <p class="MsoPlainText"><o:p> </o:p></p>
          <p class="MsoPlainText">**** now setup for STRICT checking:<o:p></o:p></p>
          <p class="MsoPlainText"><o:p> </o:p></p>
          <p class="MsoPlainText">C:\bw\smicng\work&gt;smicstrict<o:p></o:p></p>
          <p class="MsoPlainText"><o:p> </o:p></p>
          <p class="MsoPlainText">C:\bw\smicng\work&gt;smicng
            ptpbase.inc<o:p></o:p></p>
          <p class="MsoPlainText">W: f(rfc2863.mi2), (274,17) Item
            "ifPhysAddress" should have SIZE specified<o:p></o:p></p>
          <p class="MsoPlainText">E: f(rfc2863.mi2), (1092,23) Index
            item "ifRcvAddressAddress" must be defined with syntax that
            includes a SIZE<o:p></o:p></p>
          <p class="MsoPlainText">W: f(rfc2863.mi2), (1084,1) Row
            "ifRcvAddressEntry" has indexing that may create variables
            with more than 128 sub-ids<o:p></o:p></p>
          <p class="MsoPlainText">W: f(rfc2863.mi2), (1103,17) Item
            "ifRcvAddressAddress" should have SIZE specified<o:p></o:p></p>
          <p class="MsoPlainText">W: f(rfc2863.mi2), (1146,15) Variable
            "ifIndex" in notification "linkDown" is an index for a table<o:p></o:p></p>
          <p class="MsoPlainText">W: f(rfc2863.mi2), (1158,15) Variable
            "ifIndex" in notification "linkUp" is an index for a table<o:p></o:p></p>
          <p class="MsoPlainText">W: f(rfc2863.mi2), (1691,1)
            OBJECT-GROUP "ifOldObjectsGroup" is not used in a
            MODULE-COMPLIANCE in current module<o:p></o:p></p>
          <p class="MsoPlainText">E: f(ptpbase.mi2), (413,19) Sub-Id for
            item "ptpbaseMIB" must be "number" or "name(number)" format<o:p></o:p></p>
          <p class="MsoPlainText"><o:p> </o:p></p>
          <p class="MsoPlainText">*** 2 errors and 6 warnings in parsing<o:p></o:p></p>
          <p class="MsoPlainText"><o:p> </o:p></p>
          <p class="MsoPlainText">C:\bw\smicng\work&gt;<o:p></o:p></p>
          <p class="MsoPlainText"><o:p> </o:p></p>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:0cm;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">As the two errors refer to the RFC 2863 module rather than to the PTBASE-MIB: the compilation seems clean. <o:p></o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">2.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">TEXTUAL CONVENTIONS are prefixed differently than the MIB objects. This is not forbidden, but it creates inconsistency. Also the prefix ‘Clock’ for the TCs hints to a more generic functionality, although the TCs seem to be PTP-related. I would suggest prefixing the TCs also with PTP or Ptp<o:p></o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">3.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">The following TC<o:p></o:p></span></pre>
          <p class="MsoPlainText" style="margin-left:7.5pt">ClockIdentity

            ::= TEXTUAL-CONVENTION<o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:7.5pt">   
            STATUS          current<o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:7.5pt">   
            DESCRIPTION<o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:7.5pt">        "The
            clock Identity is an 8-octet array...<o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:7.5pt">   
            REFERENCE       "Section 7.5.2.2.1 from [IEEE<o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:7.5pt">   
            SYNTAX          OCTET STRING (SIZE (1..255))<o:p></o:p></p>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:0cm;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">If this is 8-Octet why is the OCTET STRING size 255?<o:p></o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">4.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">I see in the Abstract: <o:p></o:p></span></pre>
          <p class="MsoPlainText" style="margin-left:7.5pt">   This memo
            specifies a MIB module in a manner that is both compliant<br>
               to the SNMPv2 SMI, and semantically identical to the peer
            SNMPv1<br>
               definitions.<o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:7.5pt"><o:p> </o:p></p>
          <p class="MsoPlainText" style="margin-left:7.5pt">Do you
            actually mean SMIv2 rather than SNMPv2 SMI? I am not sure
            why this is important, but if this is important, please
            provide a reference to the document that includes the ‘peer
            SNMPv1’ definitions (probably SMIv1)<o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:7.5pt"><o:p> </o:p></p>
          <p class="MsoPlainText"
            style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
            level1 lfo2">
            <!--[if !supportLists]--><span style="mso-list:Ignore">5.<span
                style="font:7.0pt &quot;Times New Roman&quot;">       </span></span><!--[endif]--><span
              dir="LTR"></span>Most of the document speaks about PTP,
            but in the DESCRIPTION clause at page 7 it mentions:<o:p></o:p></p>
          <p class="MsoPlainText"><o:p> </o:p></p>
          <p class="MsoPlainText">        [IEEE 1588-2008] defines a
            protocol enabling precise<br>
                    synchronization of clocks in measurement and control
            systems<br>
                    implemented with packet-based networks, the
            Precision Time<br>
                    Protocol Version 2 (PTPv2).  This MIB does not
            address the<br>
                    earlier version IEEE Std. 1588(TM)-2002 (PTPv1).  <o:p></o:p></p>
          <p class="MsoPlainText"><o:p> </o:p></p>
          <p class="MsoPlainText">So, when it says ‘PTP’ does it mean
            PTPv2 or any version of PTP? It would be good to clarify.<o:p></o:p></p>
          <p class="MsoPlainText"><o:p> </o:p></p>
          <p class="MsoPlainText"
            style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
            level1 lfo2">
            <!--[if !supportLists]--><span style="mso-list:Ignore">6.<span
                style="font:7.0pt &quot;Times New Roman&quot;">       </span></span><!--[endif]--><span
              dir="LTR"></span> The document uses the improper
            terminology ‘MIB’ when it means MIB module. For example
            ‘Relationship to other Profiles and MIBs’ or ‘This MIB is
            intended to be used …’ etc., etc., <o:p></o:p></p>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">7.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Idnits complains about an obsolete reference to RFC 1906: <o:p></o:p></span></pre>
          <pre style="margin-left:7.5pt"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">-- Obsolete informational reference (is this intentional?): RFC 1906<o:p></o:p></span></pre>
          <pre style="margin-left:7.5pt"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">     (Obsoleted by RFC 3417)<o:p></o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">8.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">I do not believe that Section 3 includes any useful information. <o:p></o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">9.<span style="font:7.0pt &quot;Times New Roman&quot;">       </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">The DESCRIPTION clause is unusually long and includes a lot of abbreviations, terminology, architectural details and other pieces of information which is not clear why they need to be hardcoded in the MIB module. Maybe the place for all these is in the currently empty-content section 3? <o:p></o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">10.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">I do not understand how the </span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">ClockPortTransportTypeAddress TC works. If this TC defines an address type why is it not an enumeration? What is the string that for example indicates IPv6? Is it ‘IPv6’? who guarantees that a manager and an agent spell the same? Or is the intention to use the list of identifiers for ‘Well Known transport types for PTP co
 m
mu
nication’at page 64? If yes, how is this extended? Probably an IANA maintained enumerated TC would be a better solution.  <span style="color:black"><o:p></o:p></span></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">11.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Why is not the SYNTAX of </span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">ClockQualityClassType an enumeration, when the DESCRIPTION indicates clearly that this is an enumeration. <span style="color:black"><o:p></o:p></span></span></pre>
          <p class="MsoPlainText"
            style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
            level1 lfo2">
            <!--[if !supportLists]--><span style="mso-list:Ignore">12.<span
                style="font:7.0pt &quot;Times New Roman&quot;">   </span></span><!--[endif]--><span
              dir="LTR"></span>I do not understand how <span
              style="font-size:10.5pt;font-family:&quot;Courier
              New&quot;"> ClockTimeInterval</span><span
              style="font-size:10.5pt"> works. The example does not help
              either. It says ‘</span><span
              style="font-family:&quot;Courier New&quot;">For example,
              2.5 ns is expressed as 0000 0000 0002 8000 in Base16.’ and
              than the SYNTAX is </span><o:p></o:p></p>
          <p class="MsoPlainText"><span style="font-family:&quot;Courier
              New&quot;">SYNTAX          OCTET STRING (SIZE (1..255))</span><o:p></o:p></p>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:0cm;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">What is the STRING for the object in this example? <o:p></o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">13.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">For objects like ptpDomainIndex there is no need to copy again the possible values in the DESCRIPTION clause, because these are already listed in the TC.<o:p></o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">14.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Why is </span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">ptpDomainClockPortsTotal of SYNTAX Gauge32? Does this value change all the time? Does it latch at a max value? <span style="color:black"><o:p></o:p></span></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">15.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">There is no indication of behavior for counter discontinuity, or object for counter discontinuity – see section 4.6.1.2 in RFC 4181<o:p></o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 level1 lfo2;background:white"><!--[if !supportLists]--><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><span style="mso-list:Ignore">16.<span style="font:7.0pt &quot;Times New Roman&quot;">   </span></span></span><!--[endif]--><span dir="LTR"></span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Why is the SYNATX of </span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">ptpbaseClockTransDefaultDSNumOfPorts Counter32? This does not seem to be a counter, but an unsigned integer.<span style="color:black"><o:p></o:p></span></span></pre>
          <p class="MsoPlainText"
            style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
            level1 lfo2">
            <!--[if !supportLists]--><span style="mso-list:Ignore">17.<span
                style="font:7.0pt &quot;Times New Roman&quot;">   </span></span><!--[endif]--><span
              dir="LTR"></span><span style="color:black">The DESCRIPTION
              clause of the </span>ptpbaseClockPortDSPTPVersion objects
            reads: "This object specifies the PTP version being used.”
            However, the DESCRIPTION clause of the MIB module says that
            this module refers only to PTPv2. So what does this object
            stand for? And in any case, how is this coded? (1) for v1
            and (2) for v2? Then why is it not an enumerated value? <o:p>
            </o:p></p>
          <p class="MsoPlainText"
            style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
            level1 lfo2">
            <!--[if !supportLists]--><span style="mso-list:Ignore">18.<span
                style="font:7.0pt &quot;Times New Roman&quot;">   </span></span><!--[endif]--><span
              dir="LTR"></span>How does
            ptpbaseClockPortAssociateAddressType work? What would be
            included under the AutonomousType SYNTAX to make possible
            interoperability? <o:p></o:p></p>
          <p class="MsoPlainText"
            style="margin-left:25.5pt;text-indent:-18.0pt;mso-list:l0
            level1 lfo2">
            <!--[if !supportLists]--><span style="mso-list:Ignore">19.<span
                style="font:7.0pt &quot;Times New Roman&quot;">   </span></span><!--[endif]--><span
              dir="LTR"></span>The Security Considerations section does
            not follow the template defined at <a
              moz-do-not-send="true"
              href="http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security"><a class="moz-txt-link-freetext" href="http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security">http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security</a></a>.
            <o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:25.5pt"><o:p> </o:p></p>
          <p class="MsoPlainText" style="margin-left:25.5pt">I hope this
            helps. <o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:25.5pt"><o:p> </o:p></p>
          <p class="MsoPlainText" style="margin-left:25.5pt">Regards,<o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:25.5pt"><o:p> </o:p></p>
          <p class="MsoPlainText" style="margin-left:25.5pt">Dan<o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left:25.5pt"><o:p> </o:p></p>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:0cm;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p> </o:p></span></pre>
          <pre style="mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt;margin-left:0cm;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p> </o:p></span></pre>
          <pre style="margin:7.5pt;text-align:justify;background:white"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p> </o:p></span></pre>
        </div>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------040007010809010207060802--


From nobody Thu Apr 21 04:14:00 2016
Return-Path: <tim.frost@calnexsol.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 47A8212E90F for <mib-doctors@ietfa.amsl.com>; Thu, 21 Apr 2016 04:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.891
X-Spam-Level: 
X-Spam-Status: No, score=-1.891 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=calnexsolutions.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RJbO_0u9hgOj for <mib-doctors@ietfa.amsl.com>; Thu, 21 Apr 2016 04:13:54 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0788.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::788]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A12C112E8BE for <mib-doctors@ietf.org>; Thu, 21 Apr 2016 04:13:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=calnexsolutions.onmicrosoft.com; s=selector1-calnexsol-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=+q3IoLilJoLbvaKMYBSfD1wPJzxGeMCaNEru0lFvkL8=; b=EDohLhn/KR5akNkcfm3RXhf2rE9bLfnO6InTBDf63HZg3rH8o8qXvFQgcV8OkaPHk/d9RtB1VBdRDSvSZJ0R8SRuMfCf4Qq787XMn2Q8aizo3j/giiBKPjVkxBaA4UFqHc9n8OsGfu/DEJt0BXpSlGSiTpRMJBkI5pKZ68bmqf0=
Received: from DB5PR05MB1382.eurprd05.prod.outlook.com (10.162.157.28) by DB5PR05MB1381.eurprd05.prod.outlook.com (10.162.157.27) with Microsoft SMTP Server (TLS) id 15.1.466.19; Thu, 21 Apr 2016 11:13:36 +0000
Received: from DB5PR05MB1382.eurprd05.prod.outlook.com ([10.162.157.28]) by DB5PR05MB1382.eurprd05.prod.outlook.com ([10.162.157.28]) with mapi id 15.01.0466.023; Thu, 21 Apr 2016 11:13:36 +0000
From: Tim Frost <tim.frost@calnexsol.com>
To: vinays <vinays@cisco.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>,  Benoit Claise <bclaise@cisco.com>
Thread-Topic: MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt
Thread-Index: AdGFLY74bIUdlz37SrKXjSHlfwmBygV87P+AABWE9YAAEdMg4A==
Date: Thu, 21 Apr 2016 11:13:36 +0000
Message-ID: <DB5PR05MB1382583E0298EB054A357AD9FA6E0@DB5PR05MB1382.eurprd05.prod.outlook.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA7519FBEB@AZ-FFEXMB04.global.avaya.com> <5717AD7D.2080609@cisco.com> <57183DE7.3060507@cisco.com>
In-Reply-To: <57183DE7.3060507@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=calnexsol.com;
x-originating-ip: [31.216.7.58]
x-ms-office365-filtering-correlation-id: d075e6b7-7e08-40ac-ec65-08d369d5fc05
x-microsoft-exchange-diagnostics: 1; DB5PR05MB1381; 5:9OvqrLLT5pZktg+EmfOTiks4RxmgoDAuNseNBRvh+IFZqzLq976VC6dzMI4Jo5s1ovaLwp/hSJGZeOWw4e5ZFm8l95Ou6aFsXFAkHtVOAPwfnPSgTpA6iOWxil3HVwiBvdBpRt7ot3n3kQoSL8iSWQBWLidLVOmEbof5qrHKVsNq18Z30O//lizF274xg+he; 24:XXwkskfwsF4ZbP1zFt09kCHMfGPDZ3RVY9oEB84/YMLFKgv0LC0fqkXQ6/M4o2E94MBpoPG2jxx/a4RUkgRSv8W4afHIswG6Qn14xiAguUY=; 7:Y1Zpelt7Cpn/zcPTY5xvA2bhiZCO50DKiNLTBxWlxSEVOKqWmYZSpAE5TvYW/2Wg8YJNKeCRn5qh73lkcYm//gwpM5pMMkRL+mXtf9EsLrmdE+iNdNc/acdun5tEEjUT5D2FmYdLDjVejgcAWbI7MMuoGK/aekq/nKF3OmafK3xdNcFqrDkD++tbmIqzagszpeesR4+EBh292Zsqt1l7uVOAB9Yc7rfaCClPMBlo7sk=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR05MB1381;
x-microsoft-antispam-prvs: <DB5PR05MB138194D231C8EDF7128EA3FAFA6E0@DB5PR05MB1381.eurprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(95692535739014);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521026)(6040130)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041072)(6043046); SRVR:DB5PR05MB1381; BCL:0; PCL:0; RULEID:; SRVR:DB5PR05MB1381; 
x-forefront-prvs: 091949432C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(24454002)(377454003)(122556002)(5002640100001)(4326007)(10400500002)(5008740100001)(230783001)(5003600100002)(189998001)(19617315012)(1096002)(3846002)(6116002)(102836003)(19300405004)(790700001)(1220700001)(11100500001)(66066001)(86362001)(9686002)(5004730100002)(2900100001)(87936001)(5001770100001)(92566002)(54356999)(586003)(76176999)(50986999)(3660700001)(74316001)(2950100001)(3280700002)(76576001)(16236675004)(19580395003)(19580405001)(15975445007)(19625215002)(81166005)(33656002)(77096005)(2906002)(7059030)(21314002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR05MB1381; H:DB5PR05MB1382.eurprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB5PR05MB1382583E0298EB054A357AD9FA6E0DB5PR05MB1382eurp_"
MIME-Version: 1.0
X-OriginatorOrg: calnexsol.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Apr 2016 11:13:36.4850 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: fbb4e2fb-f802-4d55-beca-b7149551e928
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR05MB1381
Archived-At: <http://mailarchive.ietf.org/arch/msg/mib-doctors/lmGcMU5htDKTHnwNb5j8Boto5ww>
Cc: Karen O'Donoghue <odonoghue@isoc.org>, Greg Dowd <greg.dowd@microsemi.com>, Laurent Montini <lmontini@cisco.com>, "draft-ietf-tictoc-ptp-mib.all@tools.ietf.org" <draft-ietf-tictoc-ptp-mib.all@tools.ietf.org>
Subject: Re: [MIB-DOCTORS] MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Apr 2016 11:13:58 -0000

--_000_DB5PR05MB1382583E0298EB054A357AD9FA6E0DB5PR05MB1382eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have now submitted the -09 version of the draft. Hopefully this answers D=
an Romascanu's comments, as reviewed by Vinay below.  I updated the securit=
y section to match the newer template, and made a few typographical correct=
ions, mainly for line length.

Best regards,
Tim



Tim Frost   |   Calnex Solutions Ltd.   |   +44 (0) 7825 706 952   |   www.=
calnexsol.com<http://www.calnexsol.com/>

From: vinays [mailto:vinays@cisco.com]
Sent: 21 April 2016 03:42
To: MIB Doctors (E-mail) <mib-doctors@ietf.org>; Benoit Claise <bclaise@cis=
co.com>
Cc: Romascanu, Dan (Dan) <dromasca@avaya.com>; draft-ietf-tictoc-ptp-mib.al=
l@tools.ietf.org; Tim Frost <tim.frost@calnexsol.com>; Laurent Montini <lmo=
ntini@cisco.com>; Greg Dowd <greg.dowd@microsemi.com>; Karen O'Donoghue <od=
onoghue@isoc.org>; Vinay Shankarkumar <vinays@cisco.com>
Subject: Re: MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt


(Adding Benoit; Dan is on vacation)

We have addressed the MIB doctor review comments as described. We have addr=
essed the Gen-ART reviewer comments from Peter Yee also.




Tim will be addressing the editorial comments in the draft and submit a new=
 version tomorrow 4/21 (early morning UK time), so as to make it before the=
 telechat.



Appreciate all the valuable feedback and comments to see this through,

Thanks,
-Vinay.

On 4/20/16 12:25 PM, vinays wrote:

Thanks Dan for the valuable review and comments.

Please see below for what I have addressed in the MIB module. We will make =
the few changes
needed in the draft also as mentioned.

1. The current compile line lists only 2 errors, which are ok since they ne=
ed the IANA number:

smilint -s -e -l 5 ./PTPBASE-MIB

./PTPBASE-MIB:417: [2] {bad-identifier-case} `XXX' should start with a lowe=
r case letter
./PTPBASE-MIB:417: [2] {object-identifier-not-prefix} Object identifier ele=
ment `XXX' name only allowed as first element


2.  Have replaced the TEXTUAL CONVENTIONS as you suggested to add 'Ptp' pre=
fix.

3. Have changed PtpClockIdentity to a SYNTAX OCTET STRING (SIZE(8))

4. Will replace with SMIv2 and SMIv1.

5. Yes, Intention is to refer to PTPv2 when using PTP. We will clarify this=
.

6. Have replaced with 'MIB module'.

7. We will address in the draft.

8.  If it is ok, we would prefer to leave this as is. Thanks.

9.  Same for this as well, Thanks

10. Its not an enumeration since there are ranges in the types.

11. Its not an enumeration since there are ranges in the types.

12. Am not sure what we need to change here, Please let us know. Will add a=
s you need.

13. Would prefer to leave this as is, Thanks.

14. It can change following any configuration changes, hence would leave it=
 as is. Thanks

15. Please help what should be mentioned here? Thanks

16. Same applies here as well since it can change per configuration.

17.  Will clarify in the draft.

18. This is the normal method used to extend for new types and hence have u=
sed it. Please suggest what needs to be done. Thanks.

19. we will make changes in the draft,

Thanks,
-Vinay.



On 3/23/16 1:58 PM, Romascanu, Dan (Dan) wrote:

This is the MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt.

Note that this document has a long history. A MIB Doctor review was perform=
ed already by Bert Wijnen back in 2011.

I do not believe that this document is ready for approval in its current fo=
rm.

Here are my findings.



1.PARSING

Using smilint:

smistrip -d mibs docs/draft-ietf-tictoc-ptp-mib-08.txt

timeout 10 smilint -s -e -l 5 mibs/PTPBASE-MIB 2>report.txt

You can access any intermediately created files, the processing report (whi=
ch might be empty if no errors or warnings have been found), and output fil=
es (in case of a conversion request) for reading and download from a tempor=
ary server directory<http://www.ibr.cs.tu-bs.de/projects/libsmi/tools/tmp/6=
91tQ1/> for approx. 24 hours.

While processing your request the following errors and/or warnings have bee=
n found:

mibs/PTPBASE-MIB:426: [2] {bad-identifier-case} `XXX' should start with a l=
ower case letter

mibs/PTPBASE-MIB:426: [2] {object-identifier-not-prefix} Object identifier =
element `XXX' name only allowed as first element

mibs/PTPBASE-MIB:26: [2] {module-identity-registration} illegal module iden=
tity registration

Using smicng (thanks to Bert Wijnen):

C:\bw\smicng\work>smicng ptpbase.inc

Successful parsing



C:\bw\smicng\work>



**** now setup for STRICT checking:



C:\bw\smicng\work>smicstrict



C:\bw\smicng\work>smicng ptpbase.inc

W: f(rfc2863.mi2), (274,17) Item "ifPhysAddress" should have SIZE specified

E: f(rfc2863.mi2), (1092,23) Index item "ifRcvAddressAddress" must be defin=
ed with syntax that includes a SIZE

W: f(rfc2863.mi2), (1084,1) Row "ifRcvAddressEntry" has indexing that may c=
reate variables with more than 128 sub-ids

W: f(rfc2863.mi2), (1103,17) Item "ifRcvAddressAddress" should have SIZE sp=
ecified

W: f(rfc2863.mi2), (1146,15) Variable "ifIndex" in notification "linkDown" =
is an index for a table

W: f(rfc2863.mi2), (1158,15) Variable "ifIndex" in notification "linkUp" is=
 an index for a table

W: f(rfc2863.mi2), (1691,1) OBJECT-GROUP "ifOldObjectsGroup" is not used in=
 a MODULE-COMPLIANCE in current module

E: f(ptpbase.mi2), (413,19) Sub-Id for item "ptpbaseMIB" must be "number" o=
r "name(number)" format



*** 2 errors and 6 warnings in parsing



C:\bw\smicng\work>



As the two errors refer to the RFC 2863 module rather than to the PTBASE-MI=
B: the compilation seems clean.

2.TEXTUAL CONVENTIONS are prefixed differently than the MIB objects. This i=
s not forbidden, but it creates inconsistency. Also the prefix 'Clock' for =
the TCs hints to a more generic functionality, although the TCs seem to be =
PTP-related. I would suggest prefixing the TCs also with PTP or Ptp

3.The following TC

ClockIdentity ::=3D TEXTUAL-CONVENTION

    STATUS          current

    DESCRIPTION

        "The clock Identity is an 8-octet array...

    REFERENCE       "Section 7.5.2.2.1 from [IEEE

    SYNTAX          OCTET STRING (SIZE (1..255))

If this is 8-Octet why is the OCTET STRING size 255?

4.I see in the Abstract:

   This memo specifies a MIB module in a manner that is both compliant
   to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
   definitions.



Do you actually mean SMIv2 rather than SNMPv2 SMI? I am not sure why this i=
s important, but if this is important, please provide a reference to the do=
cument that includes the 'peer SNMPv1' definitions (probably SMIv1)



5.       Most of the document speaks about PTP, but in the DESCRIPTION clau=
se at page 7 it mentions:



        [IEEE 1588-2008] defines a protocol enabling precise
        synchronization of clocks in measurement and control systems
        implemented with packet-based networks, the Precision Time
        Protocol Version 2 (PTPv2).  This MIB does not address the
        earlier version IEEE Std. 1588(TM)-2002 (PTPv1).



So, when it says 'PTP' does it mean PTPv2 or any version of PTP? It would b=
e good to clarify.



6.        The document uses the improper terminology 'MIB' when it means MI=
B module. For example 'Relationship to other Profiles and MIBs' or 'This MI=
B is intended to be used ...' etc., etc.,

7.Idnits complains about an obsolete reference to RFC 1906:

-- Obsolete informational reference (is this intentional?): RFC 1906

     (Obsoleted by RFC 3417)

8.I do not believe that Section 3 includes any useful information.

9.The DESCRIPTION clause is unusually long and includes a lot of abbreviati=
ons, terminology, architectural details and other pieces of information whi=
ch is not clear why they need to be hardcoded in the MIB module. Maybe the =
place for all these is in the currently empty-content section 3?

10.   I do not understand how the ClockPortTransportTypeAddress TC works. I=
f this TC defines an address type why is it not an enumeration? What is the=
 string that for example indicates IPv6? Is it 'IPv6'? who guarantees that =
a manager and an agent spell the same? Or is the intention to use the list =
of identifiers for 'Well Known transport types for PTP com

11.   mu

12.nication'at page 64? If yes, how is this extended? Probably an IANA main=
tained enumerated TC would be a better solution.

13.Why is not the SYNTAX of ClockQualityClassType an enumeration, when the =
DESCRIPTION indicates clearly that this is an enumeration.

14.   I do not understand how ClockTimeInterval works. The example does not=
 help either. It says 'For example, 2.5 ns is expressed as 0000 0000 0002 8=
000 in Base16.' and than the SYNTAX is

SYNTAX          OCTET STRING (SIZE (1..255))

What is the STRING for the object in this example?

15.For objects like ptpDomainIndex there is no need to copy again the possi=
ble values in the DESCRIPTION clause, because these are already listed in t=
he TC.

16.Why is ptpDomainClockPortsTotal of SYNTAX Gauge32? Does this value chang=
e all the time? Does it latch at a max value?

17.There is no indication of behavior for counter discontinuity, or object =
for counter discontinuity - see section 4.6.1.2 in RFC 4181

18.Why is the SYNATX of ptpbaseClockTransDefaultDSNumOfPorts Counter32? Thi=
s does not seem to be a counter, but an unsigned integer.

19.   The DESCRIPTION clause of the ptpbaseClockPortDSPTPVersion objects re=
ads: "This object specifies the PTP version being used." However, the DESCR=
IPTION clause of the MIB module says that this module refers only to PTPv2.=
 So what does this object stand for? And in any case, how is this coded? (1=
) for v1 and (2) for v2? Then why is it not an enumerated value?

20.   How does ptpbaseClockPortAssociateAddressType work? What would be inc=
luded under the AutonomousType SYNTAX to make possible interoperability?

21.   The Security Considerations section does not follow the template defi=
ned at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security.



I hope this helps.



Regards,



Dan











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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New",serif;
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New",serif;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2099474858;
	mso-list-type:hybrid;
	mso-list-template-ids:-1068084126 -1890702922 67698713 67698715 67698703 6=
7698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:25.5pt;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:61.5pt;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:97.5pt;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:133.5pt;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:169.5pt;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:205.5pt;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:241.5pt;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:277.5pt;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:313.5pt;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US">I have now submitted the -09 version of the draft. Hopefully this answ=
ers Dan Romascanu&#8217;s comments, as reviewed by Vinay below.&nbsp; I upd=
ated the security section to match the newer template,
 and made a few typographical corrections, mainly for line length.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US">Best regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US">Tim<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:&quot;Ari=
al&quot;,sans-serif;color:#7F7F7F"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:&quot;Ari=
al&quot;,sans-serif;color:#7F7F7F">Tim Frost&nbsp;&nbsp;
</span><span style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,sans-se=
rif;color:red">| </span>
<span style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,sans-serif;col=
or:#7F7F7F">&nbsp;&nbsp;<b>Calnex Solutions Ltd.</b>&nbsp;&nbsp;
</span><span style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,sans-se=
rif;color:red">|</span><span style=3D"font-size:9.0pt;font-family:&quot;Ari=
al&quot;,sans-serif;color:#7F7F7F">&nbsp;&nbsp; &#43;44 (0) 7825 706 952&nb=
sp; &nbsp;</span><span style=3D"font-size:9.0pt;font-family:&quot;Arial&quo=
t;,sans-serif;color:red">|</span><span style=3D"font-size:9.0pt;font-family=
:&quot;Arial&quot;,sans-serif;color:#7F7F7F">&nbsp;&nbsp;
</span><span style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,sans-se=
rif;color:gray"><a href=3D"http://www.calnexsol.com/"><span style=3D"color:=
gray;text-decoration:none">www.calnexsol.com</span></a></span><span style=
=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#7F7F7F"=
><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:windowtext">F=
rom:</span></b><span lang=3D"EN-US" style=3D"color:windowtext"> vinays [mai=
lto:vinays@cisco.com]
<br>
<b>Sent:</b> 21 April 2016 03:42<br>
<b>To:</b> MIB Doctors (E-mail) &lt;mib-doctors@ietf.org&gt;; Benoit Claise=
 &lt;bclaise@cisco.com&gt;<br>
<b>Cc:</b> Romascanu, Dan (Dan) &lt;dromasca@avaya.com&gt;; draft-ietf-tict=
oc-ptp-mib.all@tools.ietf.org; Tim Frost &lt;tim.frost@calnexsol.com&gt;; L=
aurent Montini &lt;lmontini@cisco.com&gt;; Greg Dowd &lt;greg.dowd@microsem=
i.com&gt;; Karen O'Donoghue &lt;odonoghue@isoc.org&gt;; Vinay
 Shankarkumar &lt;vinays@cisco.com&gt;<br>
<b>Subject:</b> Re: MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt<=
o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><br>
<span style=3D"font-size:13.5pt">(Adding Benoit; Dan is on vacation)<br>
<br>
We have addressed the MIB doctor review comments as described. We have addr=
essed the
</span>Gen-ART reviewer comments from Peter Yee also.<br>
<br>
<span style=3D"font-size:12.0pt"><o:p></o:p></span></p>
<pre><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,serif"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,serif">Tim will be addressing the editorial comments in the draft and sub=
mit a new version tomorrow 4/21 (early morning UK time), so as to make it b=
efore the telechat.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,serif"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,serif">Appreciate all the valuable feedback and comments to see this thro=
ugh,<o:p></o:p></span></pre>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:13.5pt"><br>
Thanks,<br>
-Vinay.<br>
<br>
</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On 4/20/16 12:25 PM, vinays wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
Thanks Dan for the valuable review and comments.<br>
<br>
Please see below for what I have addressed in the MIB module. We will make =
the few changes<br>
needed in the draft also as mentioned.<br>
<br>
1. The current compile line lists only 2 errors, which are ok since they ne=
ed the IANA number:<br>
<br>
smilint -s -e -l 5 ./PTPBASE-MIB<br>
<br>
./PTPBASE-MIB:417: [2] {bad-identifier-case} `XXX' should start with a lowe=
r case letter<br>
./PTPBASE-MIB:417: [2] {object-identifier-not-prefix} Object identifier ele=
ment `XXX' name only allowed as first element<br>
<br>
<br>
2.&nbsp; Have replaced the TEXTUAL CONVENTIONS as you suggested to add 'Ptp=
' prefix.<br>
<br>
3. Have changed PtpClockIdentity to a SYNTAX OCTET STRING (SIZE(8))<br>
<br>
4. Will replace with SMIv2 and SMIv1.<br>
<br>
5. Yes, Intention is to refer to PTPv2 when using PTP. We will clarify this=
.<br>
<br>
6. Have replaced with 'MIB module'.<br>
<br>
7. We will address in the draft.<br>
<br>
8.&nbsp; If it is ok, we would prefer to leave this as is. Thanks.<br>
<br>
9.&nbsp; Same for this as well, Thanks<br>
<br>
10. Its not an enumeration since there are ranges in the types.<br>
<br>
11. Its not an enumeration since there are ranges in the types.<br>
<br>
12. Am not sure what we need to change here, Please let us know. Will add a=
s you need.<br>
<br>
13. Would prefer to leave this as is, Thanks.<br>
<br>
14. It can change following any configuration changes, hence would leave it=
 as is. Thanks<br>
<br>
15. Please help what should be mentioned here? Thanks<br>
<br>
16. Same applies here as well since it can change per configuration.<br>
<br>
17.&nbsp; Will clarify in the draft.<br>
<br>
18. This is the normal method used to extend for new types and hence have u=
sed it. Please suggest what needs to be done. Thanks.<br>
<br>
19. we will make changes in the draft,<br>
<br>
Thanks,<br>
-Vinay.<br>
<br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On 3/23/16 1:58 PM, Romascanu, Dan (Dan) wrote:<o:p>=
</o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">This is th=
e MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt. </span><o:p></o:p=
></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">Note that =
this document has a long history. A MIB Doctor review was performed already=
 by Bert Wijnen back in 2011. </span><o:p></o:p></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">I do not b=
elieve that this document is ready for approval in its current form. </span=
><o:p></o:p></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">Here are m=
y findings. </span><o:p></o:p></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</sp=
an><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">1.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">PARSING</span><o:p></o:p></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">Using smil=
int:</span><o:p></o:p></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">smistrip -=
d mibs docs/draft-ietf-tictoc-ptp-mib-08.txt</span><o:p></o:p></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">timeout 10=
 smilint -s -e -l 5 mibs/PTPBASE-MIB 2&gt;report.txt</span><o:p></o:p></pre=
>
<p style=3D"margin:7.5pt;text-align:justify;background:white;orphans:
            auto;widows: 1;-webkit-text-stroke-width:
            0px;word-spacing:0px">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"=
>You can access any intermediately created files, the processing report (wh=
ich might be empty if no errors or warnings have been found), and output fi=
les (in case of a conversion request) for reading
 and download from a temporary server<span class=3D"apple-converted-space">=
&nbsp;</span><a href=3D"http://www.ibr.cs.tu-bs.de/projects/libsmi/tools/tm=
p/691tQ1/"><span style=3D"color:#990000">directory</span></a><span class=3D=
"apple-converted-space">&nbsp;</span>for approx. 24
 hours.</span><o:p></o:p></p>
<p style=3D"margin:7.5pt;text-align:justify;background:white;orphans:
            auto;widows: 1;-webkit-text-stroke-width:
            0px;word-spacing:0px">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"=
>While processing your request the following errors and/or warnings have be=
en found:</span><o:p></o:p></p>
<pre style=3D"margin:7.5pt;text-align:justify;background:white;orphans: aut=
o;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px"><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">mibs/PTPBASE-=
MIB:426: [2] {bad-identifier-case} `XXX' should start with a lower case let=
ter</span><o:p></o:p></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">mibs/PTPBA=
SE-MIB:426: [2] {object-identifier-not-prefix} Object identifier element `X=
XX' name only allowed as first element</span><o:p></o:p></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">mibs/PTPBA=
SE-MIB:26: [2] {module-identity-registration} illegal module identity regis=
tration</span><o:p></o:p></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">Using smic=
ng (thanks to Bert Wijnen):</span><o:p></o:p></pre>
<p class=3D"MsoPlainText">C:\bw\smicng\work&gt;smicng ptpbase.inc<o:p></o:p=
></p>
<p class=3D"MsoPlainText">Successful parsing<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">C:\bw\smicng\work&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">**** now setup for STRICT checking:<o:p></o:p></p=
>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">C:\bw\smicng\work&gt;smicstrict<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">C:\bw\smicng\work&gt;smicng ptpbase.inc<o:p></o:p=
></p>
<p class=3D"MsoPlainText">W: f(rfc2863.mi2), (274,17) Item &quot;ifPhysAddr=
ess&quot; should have SIZE specified<o:p></o:p></p>
<p class=3D"MsoPlainText">E: f(rfc2863.mi2), (1092,23) Index item &quot;ifR=
cvAddressAddress&quot; must be defined with syntax that includes a SIZE<o:p=
></o:p></p>
<p class=3D"MsoPlainText">W: f(rfc2863.mi2), (1084,1) Row &quot;ifRcvAddres=
sEntry&quot; has indexing that may create variables with more than 128 sub-=
ids<o:p></o:p></p>
<p class=3D"MsoPlainText">W: f(rfc2863.mi2), (1103,17) Item &quot;ifRcvAddr=
essAddress&quot; should have SIZE specified<o:p></o:p></p>
<p class=3D"MsoPlainText">W: f(rfc2863.mi2), (1146,15) Variable &quot;ifInd=
ex&quot; in notification &quot;linkDown&quot; is an index for a table<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">W: f(rfc2863.mi2), (1158,15) Variable &quot;ifInd=
ex&quot; in notification &quot;linkUp&quot; is an index for a table<o:p></o=
:p></p>
<p class=3D"MsoPlainText">W: f(rfc2863.mi2), (1691,1) OBJECT-GROUP &quot;if=
OldObjectsGroup&quot; is not used in a MODULE-COMPLIANCE in current module<=
o:p></o:p></p>
<p class=3D"MsoPlainText">E: f(ptpbase.mi2), (413,19) Sub-Id for item &quot=
;ptpbaseMIB&quot; must be &quot;number&quot; or &quot;name(number)&quot; fo=
rmat<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">*** 2 errors and 6 warnings in parsing<o:p></o:p>=
</p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">C:\bw\smicng\work&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:0cm;text-align:justify;background:white"><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">As the two errors =
refer to the RFC 2863 module rather than to the PTBASE-MIB: the compilation=
 seems clean. </span><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">2.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">TEXTUAL CONVENTIONS are prefixed differently than=
 the MIB objects. This is not forbidden, but it creates inconsistency. Also=
 the prefix &#8216;Clock&#8217; for the TCs hints to a more generic functio=
nality, although the TCs seem to be PTP-related. I would suggest prefixing =
the TCs also with PTP or Ptp</span><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">3.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">The following TC</span><o:p></o:p></pre>
<p class=3D"MsoPlainText" style=3D"margin-left:7.5pt">ClockIdentity ::=3D T=
EXTUAL-CONVENTION<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:7.5pt">&nbsp;&nbsp;&nbsp; ST=
ATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current<o:p></o:=
p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:7.5pt">&nbsp;&nbsp;&nbsp; DE=
SCRIPTION<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:7.5pt">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; &quot;The clock Identity is an 8-octet array...<o:p><=
/o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:7.5pt">&nbsp;&nbsp;&nbsp; RE=
FERENCE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;Section 7.5.2.2.1 from [I=
EEE<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:7.5pt">&nbsp;&nbsp;&nbsp; SY=
NTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OCTET STRING (SI=
ZE (1..255))<o:p></o:p></p>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:0cm;text-align:justify;background:white"><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">If this is 8-Octet=
 why is the OCTET STRING size 255?</span><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">4.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">I see in the Abstract: </span><o:p></o:p></pre>
<p class=3D"MsoPlainText" style=3D"margin-left:7.5pt">&nbsp;&nbsp;&nbsp;Thi=
s memo specifies a MIB module in a manner that is both compliant<br>
&nbsp;&nbsp; to the SNMPv2 SMI, and semantically identical to the peer SNMP=
v1<br>
&nbsp;&nbsp; definitions.<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:7.5pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:7.5pt">Do you actually mean =
SMIv2 rather than SNMPv2 SMI? I am not sure why this is important, but if t=
his is important, please provide a reference to the document that includes =
the &#8216;peer SNMPv1&#8217; definitions (probably
 SMIv1)<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:7.5pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">5.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Most of the document speaks about PTP, but in the D=
ESCRIPTION clause at page 7 it mentions:<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [IEEE =
1588-2008] defines a protocol enabling precise<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; synchronization of clocks in mea=
surement and control systems<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; implemented with packet-based ne=
tworks, the Precision Time<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Protocol Version 2 (PTPv2).&nbsp=
; This MIB does not address the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; earlier version IEEE Std. 1588(T=
M)-2002 (PTPv1).&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">So, when it says &#8216;PTP&#8217; does it mean P=
TPv2 or any version of PTP? It would be good to clarify.<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">6.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>&nbsp;The document uses the improper terminology &#=
8216;MIB&#8217; when it means MIB module. For example &#8216;Relationship t=
o other Profiles and MIBs&#8217; or &#8216;This MIB is intended to be used =
&#8230;&#8217; etc., etc.,
<o:p></o:p></p>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">7.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">Idnits complains about an obsolete reference to R=
FC 1906: </span><o:p></o:p></pre>
<pre style=3D"margin-left:7.5pt"><span style=3D"font-size:11.0pt;font-famil=
y:&quot;Calibri&quot;,sans-serif">-- Obsolete informational reference (is t=
his intentional?): RFC 1906</span><o:p></o:p></pre>
<pre style=3D"margin-left:7.5pt"><span style=3D"font-size:11.0pt;font-famil=
y:&quot;Calibri&quot;,sans-serif">&nbsp;&nbsp;&nbsp;&nbsp; (Obsoleted by RF=
C 3417)</span><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">8.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">I do not believe that Section 3 includes any usef=
ul information. </span><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">9.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">The DESCRIPTION clause is unusually long and incl=
udes a lot of abbreviations, terminology, architectural details and other p=
ieces of information which is not clear why they need to be hardcoded in th=
e MIB module. Maybe the place for all these is in the currently empty-conte=
nt section 3? </span><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"font-size:1=
1.0pt;font-family:&quot;Calibri&quot;,sans-serif"><span style=3D"mso-list:I=
gnore">10.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p; </span></span></span><![endif]><span style=3D"font-size:11.0pt;font-fami=
ly:&quot;Calibri&quot;,sans-serif">I do not understand how the ClockPortTra=
nsportTypeAddress TC works. If this TC defines an address type why is it no=
t an enumeration? What is the string that for example indicates IPv6? Is it=
 &#8216;IPv6&#8217;? who guarantees that a manager and an agent spell the s=
ame? Or is the intention to use the list of identifiers for &#8216;Well Kno=
wn transport types for PTP com<o:p></o:p></span></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"font-size:1=
1.0pt;font-family:&quot;Calibri&quot;,sans-serif"><span style=3D"mso-list:I=
gnore">11.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p; </span></span></span><![endif]><span style=3D"font-size:11.0pt;font-fami=
ly:&quot;Calibri&quot;,sans-serif">mu<o:p></o:p></span></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">12.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">nication&#8217;at page 64? If yes, how is this e=
xtended? Probably an IANA maintained enumerated TC would be a better soluti=
on.&nbsp; </span><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">13.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">Why is not the SYNTAX of ClockQualityClassType a=
n enumeration, when the DESCRIPTION indicates clearly that this is an enume=
ration. </span><o:p></o:p></pre>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">14.<span style=3D"font=
:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><![endif]>I do not understand how <span style=3D"font-size:10=
.5pt;font-family:&quot;Courier New&quot;,serif">
ClockTimeInterval</span><span style=3D"font-size:10.5pt"> works. The exampl=
e does not help either. It says &#8216;</span><span style=3D"font-family:&q=
uot;Courier New&quot;,serif">For example, 2.5 ns is expressed as 0000 0000 =
0002 8000 in Base16.&#8217; and than the SYNTAX is
</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Courier New&quot=
;,serif">SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OCTET=
 STRING (SIZE (1..255))</span><o:p></o:p></p>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:0cm;text-align:justify;background:white"><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">What is the STRING=
 for the object in this example? </span><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">15.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">For objects like ptpDomainIndex there is no need=
 to copy again the possible values in the DESCRIPTION clause, because these=
 are already listed in the TC.</span><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">16.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">Why is ptpDomainClockPortsTotal of SYNTAX Gauge3=
2? Does this value change all the time? Does it latch at a max value? </spa=
n><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">17.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">There is no indication of behavior for counter d=
iscontinuity, or object for counter discontinuity &#8211; see section 4.6.1=
.2 in RFC 4181</span><o:p></o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:25.5pt;text-align:justify;text-indent:-18.0pt;mso-list:l0 le=
vel1 lfo2;background:white"><![if !supportLists]><span style=3D"mso-list:Ig=
nore">18.</span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">Why is the SYNATX of ptpbaseClockTransDefaultDSN=
umOfPorts Counter32? This does not seem to be a counter, but an unsigned in=
teger.</span><o:p></o:p></pre>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">19.<span style=3D"font=
:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><![endif]>The DESCRIPTION clause of the ptpbaseClockPortDSPTP=
Version objects reads: &quot;This object specifies the PTP version being us=
ed.&#8221; However, the DESCRIPTION clause of the MIB module says that this=
 module refers only to PTPv2. So what does
 this object stand for? And in any case, how is this coded? (1) for v1 and =
(2) for v2? Then why is it not an enumerated value?
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">20.<span style=3D"font=
:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><![endif]>How does ptpbaseClockPortAssociateAddressType work?=
 What would be included under the AutonomousType SYNTAX to make possible in=
teroperability?
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">21.<span style=3D"font=
:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><![endif]>The Security Considerations section does not follow=
 the template defined at
<a href=3D"http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security">http=
://trac.tools.ietf.org/area/ops/trac/wiki/mib-security</a>.
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt">&nbsp;<o:p></o:p></p=
>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt">I hope this helps. <=
o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt">&nbsp;<o:p></o:p></p=
>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt">Regards,<o:p></o:p><=
/p>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt">&nbsp;<o:p></o:p></p=
>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt">Dan<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:25.5pt">&nbsp;<o:p></o:p></p=
>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:0cm;text-align:justify;background:white"><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span><o:p>=
</o:p></pre>
<pre style=3D"mso-margin-top-alt:7.5pt;margin-right:7.5pt;margin-bottom:7.5=
pt;margin-left:0cm;text-align:justify;background:white"><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span><o:p>=
</o:p></pre>
<pre style=3D"margin:7.5pt;text-align:justify;background:white"><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</sp=
an><o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,serif"><o:p>&nbsp;</o:p></span></p>
</blockquote>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,serif"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_DB5PR05MB1382583E0298EB054A357AD9FA6E0DB5PR05MB1382eurp_--

