[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Pls review Agenda and Package for July 22, 2004 IESG Telechat

To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, "Mreview (E-mail)" <mreview@ops.ietf.org>
Subject: RE: Pls review Agenda and Package for July 22, 2004 IESG Telechat
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Date: Tue, 20 Jul 2004 14:48:32 +0300
I am getting the following errors by applying smilint on the BGP-4 MIB:

This command (smilint 0.4.3-pre1, as of Fri Jul 09 15:59:34 2004)
has been processed to get the following results:
smilint -m -s -m -s -l 6 -i namelength-32 bgp4-mib.txt

bgp4-mib.txt:56: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
bgp4-mib.txt:76: [5] {} warning: flushing recent incorrect declaration, see previous error(s)
bgp4-mib.txt:1213: [2] {module-identity-missing} missing MODULE-IDENTITY clause in SMIv2 MIB
bgp4-mib.txt:96: [1] {} unknown object identifier label `bgp'
bgp4-mib.txt:123: [5] {index-element-accessible} warning: index element `bgpPeerRemoteAddr' of row `bgpPeerEntry' should be not-accessible in SMIv2 MIB
bgp4-mib.txt:564: [5] {row-name-table-name} warning: row identifier `bgpPathAttrEntry' should have the same prefix as table identifier `bgpRcvdPathAttrTable'
bgp4-mib.txt:564: [5] {index-element-accessible} warning: index element `bgpPathAttrDestNetwork' of row `bgpPathAttrEntry' should be not-accessible in SMIv2 MIB
bgp4-mib.txt:564: [5] {index-element-accessible} warning: index element `bgpPathAttrPeer' of row `bgpPathAttrEntry' should be not-accessible in SMIv2 MIB
bgp4-mib.txt:680: [5] {index-element-accessible} warning: index element `bgp4PathAttrIpAddrPrefix' of row `bgp4PathAttrEntry' should be not-accessible in SMIv2 MIB
bgp4-mib.txt:680: [5] {index-element-accessible} warning: index element `bgp4PathAttrIpAddrPrefixLen' of row `bgp4PathAttrEntry' should be not-accessible in SMIv2 MIB
bgp4-mib.txt:680: [5] {index-element-accessible} warning: index element `bgp4PathAttrPeer' of row `bgp4PathAttrEntry' should be not-accessible in SMIv2 MIB
bgp4-mib.txt:1022: [5] {notification-not-reversible} warning: notification `bgpEstablished' is not reverse mappable
bgp4-mib.txt:1035: [5] {notification-not-reversible} warning: notification `bgpBackwardTransition' is not reverse mappable
bgp4-mib.txt:6: [5] {import-unused} warning: identifier `mib-2' imported from module `SNMPv2-SMI' is never used

The first 4 and the last seem to be caused by the use of " in the DESCRIPTION Clause of one of the REVISION clauses


Regards,

Dan



> -----Original Message-----
> From: owner-mreview@ops.ietf.org 
> [mailto:owner-mreview@ops.ietf.org]On Behalf Of Wijnen, Bert (Bert)
> Sent: 16 July, 2004 12:52 PM
> To: Mreview (E-mail)
> Subject: Pls review Agenda and Package for July 22, 2004 IESG Telechat
> 
> 
> MIB Doctors,
> 
> I would appreciate if you can review from an NM and SNMP/MIB
> perspective. Specific documents I like you to focus on are:
> 
>      - draft-ietf-idr-bgp4-mib-14.txt
>        Definitions of Managed Objects for the Fourth Version 
> of Border Gateway 
>        Protocol (BGP-4) (Proposed Standard) 
> 
>      - draft-ietf-idr-bgp-mibagent-survey-01.txt
>        BGP MIB V1 implementation survey (Informational) 
> 
> But of course checking any other documents will be 
> appreciated as well.
> Comments asap, but certainly before Thursday July 22nd at 4pm 
> European time.
> 
> Thanks, Bert
> ------------
> 2.1 WG Submissions
> 2.1.1 New Item
>   o Eight-document ballot:  - 1 of 4
>      - draft-ietf-idr-bgp-implementation-01.txt
>        BGP 4 Implementation Report (Informational) 
>      - draft-ietf-idr-bgp4-24.txt
>        A Border Gateway Protocol 4 (BGP-4) (Draft Standard) 
>      - draft-ietf-idr-bgp4-mib-14.txt
>        Definitions of Managed Objects for the Fourth Version 
> of Border Gateway 
>        Protocol (BGP-4) (Proposed Standard) 
>      - draft-ietf-idr-bgp-vuln-00.txt
>        BGP Security Vulnerabilities Analysis (Informational) 
>      - draft-ietf-idr-bgp-analysis-05.txt
>        BGP-4 Protocol Analysis (Informational) 
>      - draft-ietf-idr-bgp4-experience-protocol-04.txt
>        Experience with the BGP-4 Protocol (Informational) 
>      - draft-ietf-idr-bgp-mibagent-survey-01.txt
>        BGP MIB V1 implementation survey (Informational) 
>      - draft-iesg-tcpmd5app-00.txt
>        Standards Maturity Variance Regarding the TCP MD5 
> Signature Option (RFC 
>        2385) and the BGP-4 Specification (Informational) 
>     Token: Alex Zinin
>   o draft-ietf-opes-http-02.txt
>     HTTP adaptation with OPES (Proposed Standard) - 2 of 4 
>     Token: Ted Hardie
>   o draft-ietf-mmusic-anat-01.txt
>     The Alternative Network Address Types Semantics for the 
> Session Description 
>     Protocol Grouping Framework (Proposed Standard) - 3 of 4 
>     Token: Jon Peterson
>   o draft-ietf-sip-anat-usage-00.txt
>     Usage of the Session Description Protocol (SDP) 
> Alternative Network Address 
>     Types (ANAT) Semantics in the Session Initiation Protocol 
> (SIP) (Proposed 
>     Standard) - 4 of 4 
>     Note: RFC Editor Note: ANAT to be expanded in Abstract and Intro 
>     Token: Allison Mankin
> 
> 2.1.2 Returning Item
>   o draft-ietf-pkix-pi-10.txt
>     Internet X.509 Public Key Infrastructure Permanent 
> Identifier (Proposed 
>     Standard) - 1 of 3 
>     Note: The draft includes significant revisions.&nbsp; On 
> the agenda to see 
>     if the revisions resolve the discuss positions.&nbsp; 
> Also, given the 
>     significant changes, all of the ADs may want to take a 
> fresh look. 
>     Token: Russ Housley
>   o Two-document ballot:  - 2 of 3
>      - draft-ietf-sipping-early-media-02.txt
>        Early Media and Ringing Tone Generation in the Session 
> Initiation 
>        Protocol (SIP) (Informational) 
>      - draft-ietf-sipping-early-disposition-03.txt
>        The Early Session Disposition Type for the Session 
> Initiation Protocol 
>        (SIP) (Proposed Standard) 
>        Note: For re-review by Discussants please. 
>     Token: Allison Mankin
>   o Three-document ballot:  - 3 of 3
>      - draft-ietf-crisp-iris-core-07.txt
>        IRIS - The Internet Registry Information Service 
> (IRIS) Core Protocol 
>        (Proposed Standard) 
>        Note: Returning to resolve outstanding DISCUSS; please 
> be sure to review 
>        the -07 versions. 
>      - draft-ietf-crisp-iris-dreg-07.txt
>        IRIS - A Domain Registry (dreg) Type for the Internet Registry 
>        Information Service (Proposed Standard) 
>      - draft-ietf-crisp-iris-beep-07.txt
>        IRIS - Using the Internet Registry Information Service 
> (IRIS) over the 
>        Blocks Extensible Exchange Protocol (BEEP) (Proposed Standard) 
>        Note: Needs to add a normative reference to 
> draft-daigle-snaptr-00.txt, 
>        which sets up the registry populated here. 
>     Token: Ted Hardie
> 
> 
> 2.2 Individual Submissions
> 2.2.1 New Item
>   o draft-wasserman-rfc2418-ml-update-01.txt
>     Update to RFC 2418 Regarding the Management of IETF 
> Mailing Lists (BCP) - 1 
>     of 2 
>     Token: Harald Alvestrand
>   o draft-hansen-lemonade-msgctxt-videomsg-01.txt
>     Video Message Message Context (Proposed Standard) - 2 of 2 
>     Token: Ted Hardie
> 
> 2.2.2 Returning Item
> NONE
> 
> 3. Document Actions
> 
> 3.1 WG Submissions
> 	Reviews should focus on these questions: "Is this 
> document a reasonable
> 	contribution to the area of Internet engineering which 
> it covers? If
> 	not, what changes would make it so?"
> 
> 3.1.1 New Item
>   o draft-ietf-msec-gkmarch-08.txt
>     MSEC Group Key Management Architecture (Informational) - 1 of 2 
>     Note: Blue Team. 
>     Token: Russ Housley
>   o draft-ietf-v6ops-renumbering-procedure-01.txt
>     Procedures for Renumbering an IPv6 Network without a Flag Day 
>     (Informational) - 2 of 2 
>     Note: Note: red team 
>     Token: David Kessens
> 
> 3.1.2 Returning Item
> NONE
> 
> 3.2 Individual Submissions Via AD
> 	Reviews should focus on these questions: "Is this 
> document a reasonable
> 	contribution to the area of Internet engineering which 
> it covers? If
> 	not, what changes would make it so?"
> 
> 3.2.1 New Item
>   o draft-torvinen-http-digest-aka-v2-01.txt
>     Hypertext Transfer Protocol (HTTP) Digest Authentication Using 
>     Authentication and Key Agreement (AKA) Version-2 
> (Informational) - 1 of 1 
>     Token: Allison Mankin
> 
> 3.2.2 Returning Item
> NONE
> 3.3 Individual Submissions Via RFC Editor
> 	Reviews should focus on these questions: "Does this document
> 	represent an end run around the IETF's working groups
> 	or its procedures? Does this document present an incompatible
> 	change to IETF technologies as if it were compatible?" Other
> 	matters may be sent to the RFC Editor in private review.
> 
> 3.3.1 New Item
>   o draft-richardson-ipsec-opportunistic-15.txt
>     Opportunistic Encryption using The Internet Key Exchange (IKE) 
>     (Informational) - 1 of 1 
>     Token: Steve Bellovin
> 
> 3.3.2 Returning Item
> NONE
> 
> 
>
Prev by Date: Pls review Agenda and Package for July 22, 2004 IESG Telechat
Next by Date: Volunteer for MIB Doctor review: draft-ietf-mip6-mipv6-mib-02.txt
Previous by thread: Pls review Agenda and Package for July 22, 2004 IESG Telechat
Next by thread: RE: Pls review Agenda and Package for July 22, 2004 IESG Telechat
Index(es):
- Date
- Thread