Subject: [Pce] FW: New Version Notification for draft-ietf-pce-pcep-mib-03.txt

From: Jonathan Hardwick <[email-masked]>
Date: Tue, 10 Jul 2012 16:20:33 +0000

Hi all

A new version of the PCEP MIB draft is now available.

The overall motivation for the changes in this version is to improve the structure and (hopefully) bring the content up to the minimum level required by RFC 5440.  There is potentially a lot more content that we might want to put into this MIB, and I would welcome any feedback that the working group has on this.

There have been some structural changes and several fields from the previous version have been removed.  A summary and brief rationale is below.

Cheers
Jon

Structural changes
==================

-  Session MIB now stands alone instead of augmenting Peer MIB, because the lifetimes of objects in these different MIBs are logically distinct.  Both MIBs are read-only.

-  pcePcepClientTable renamed to pcePcepEntityTable.

-  Various new timer configuration and limit configuration fields in the pcePcepEntityTable.  These are supposed to reflect recommendations made in RFC 5440.

-  Various new reporting and statistics fields in the Peer and Session MIBs.

Deleted fields
==============

The following fields from version -02 have not been included in the new version -03.

-  pcePcepClientSessionAuth

This was incomplete as specified and might best be left to the implementation.  For example, the setting onlyAuthorizedPeers is not meaningful without some way to configure the authorized peers.

-  pcePcepClientStorageType

Again this is probably best left to the implementation.

-  pcePcepClientInitSession

This was incomplete as specified and might best be left to the implementation.  It only allows “automatically connect to everyone” and “do not connect to anyone”.  There are many different policies that you might wish to apply between those two extremes.

-  pcePcepClientPoliciesAllowed

This was incomplete as specified and might best be left to the implementation.  Has an exhaustive list of path computation policies been standardized anywhere?

-  pcePcepPeerLastChange

This is covered adequately by the new time values within the peer and session MIBs.

-  pcePcepSessionDiscontinuityTime

This is covered adequately by the new time values within the peer MIB.

-  pcePcepSessionSpeakerRole

This was structurally wrong.  A role is a property of an individual request, not an entire session.

-  pcePcepSessionCorruptedMsgs

We need a tighter definition in the MIB of what is “corrupted” versus “unsupported” and it might be better to count them separately.  For example, if an object type is not recognized, how do you know whether the message was corrupted?

-  pcePcepSessionFailedComps

There are different categories of failure and it might be better to split them out: NO-PATH; undecipherable request; policy rejects request; and so on.

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: 10 July 2012 16:44
To: Jonathan Hardwick
Cc: [email-masked]; [email-masked]; [email-masked]; [email-masked]
Subject: New Version Notification for draft-ietf-pce-pcep-mib-03.txt

A new version of I-D, draft-ietf-pce-pcep-mib-03.txt
has been successfully submitted by Jonathan Hardwick and posted to the
IETF repository.

Filename:	 draft-ietf-pce-pcep-mib
Revision:	 03
Title:		 PCE communication protocol (PCEP) Management Information Base
Creation date:	 2012-07-10
WG ID:		 pce
Number of pages: 27
URL:             http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-mib-03.txt
Status:          http://datatracker.ietf.org/doc/draft-ietf-pce-pcep-mib
Htmlized:        http://tools.ietf.org/html/draft-ietf-pce-pcep-mib-03
Diff:            http://tools.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-mib-03

Abstract:
   This memo defines an experimental portion of the Management
   Information Base for use with network management protocols in the
   Internet community.  In particular, it describes managed objects for
   modeling of Path Computation Element communication Protocol (PCEP)
   for communications between a Path Computation Client (PCC) and a Path
   Computation Element (PCE), or between two PCEs.

The IETF Secretariat