IP over Cable Data Network (ipcdn)

Sumanth Channabasappa | 18 Aug 2008 15:42

draft-ietf-ipcdn-pktc-eventmess (-v14)

Folks,

We have posted version -14 of draft-ietf-ipcdn-pktc-eventmess,
(http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-eventmess-14.
txt). 

This version incorporates the comments received from Pasi and Lars,
based on the resolutions proposed by Rich Woundy and the co-authors. The
changes are summarized at the end of this email. I have also included
the results from IDNits verification and MIB compilation.

- S

Summary of changes:
-------------------

#1:
"The SYSLOG WG is obtaining a port number for SYSLOG over TLS that we
will use as the DEFVAL for pktcEventSyslogPort."

Specifically, the following change is suggested: 

	DEFVAL     { syslogs }

-- RFC Editor - replace syslogs with the IANA-assigned 
-- SYSLOG over TLS port in [RFCCCC ] and remove this note  

#2:

We also need to delete the following sentence from

(Continue reading)

headers

Jean-Francois Mule | 21 Jan 2005 19:24

RE: draft-ietf-ipcdn-pktc-mtamib-05 - why 1024?

A question was posed w.r.t. the choice of the max number of errors in the MTA ErrorOID table, currently set as
1024 in the object definition. I just wanted to close the loop on the comment and the suggestions to not
limit the error OID table to 1024 but instead, put a max in MODULE-COMPLIANCE.

After talking to some folks here and some vendors, here's a summary of our discussions:
- we think that a limit of 1024 errors in a config file that is usually 20-100(say even 300) lines or OID
assignments is sufficient, even for future extensions,
- the cable operators do control this config file very strictly and run lab tests before rolling out a new
config file and this table is a pre-deployment tool to check config file errors and 1024 is ok.

=> So, the authors are recommending we keep the object as-is. We have had many discussions and valuable
refinements to state what happens beyond the 1024th error.

We will add the following text in the object description clause to explain the rationale:
"The maximum number of errors or warnings that can be recorded in the pktcMtaDevErrorOidsTable is set to
1024 as a configuration file is usually validated by operators before deployment. Given the possible
number of configuration parameter assignments in the MTA configuration file, 1024 is perceived as a
sufficient limit even with future extensions."

Feel free to propose better text.

Let me know if this is ok.
Jean-François
PS: The alternative to get rid of the limit in the object definition, add it to the module compliance, which
also provides strong guidance to vendors for their implementations. Let me know if this is a better route,
I really think that this is a minor comment given how this table is used. And we're all used to SMICng barking
after a certain number of errors when compiling a MIB module and that pretty much means: too many errors,
fix those first, then come back and try again...

(Continue reading)

headers

Jean-Francois Mule | 21 Jan 2005 18:12

RE: draft-ietf-ipcdn-pktc-mtamib-05 - SMI questionforpktcMtaDevErrorsTooManyErrors

Hi Randy,
As usual, thanks for your good comments. See inline.
Jean-François 

Randy wrote:
> >           file was interpreted by the MTA as being .1.2.3.4.5, and
> 
> Please get rid of the leading "."
Corrected, sorry. My global search on leading zeros for OIDs missed that one.

> ...
> > |         If the numbers of errors in the configuration file exceeds
> > |         1024, then for all subsequent errors, the
> > |         pktcMtaDevErrorOid of 1024th table's entry MUST contain
> 
> you mean "of the table's 1024th entry"
Yes. Grammar corrected everywhere, thanks for catching this.

> > |         a human readable representation of the
> > |         pktcMtaDevErrorsTooManyErrors object, i.e. the string
> > |          '1.3.6.1.2.1.XXX.1.1.4.1.0'.
> 
> ...
> > |         pktcMtaDevErrorValue of 1024th table's entry MUST contain
> 
> again "of the table's 1024th entry"
Yes. Corrected.

> > |         pktcMtaDevErrorReason of 1024th table's entry must contain
>

(Continue reading)

headers

Wijnen, Bert (Bert | 21 Jan 2005 14:54

RE: draft-ietf-ipcdn-pktc-mtamib-05 - SMI question for pk tcMtaDevErrorsTooManyErrors

I agree with Randy's answer.

Bert

> -----Original Message-----
> From: ipcdn-bounces <at> ietf.org 
> [mailto:ipcdn-bounces <at> ietf.org]On Behalf Of
> Jean-Francois Mule
> Sent: Friday, January 21, 2005 01:11
> To: Eugene Nechamkin; ipcdn <at> ietf.org
> Subject: [ipcdn] draft-ietf-ipcdn-pktc-mtamib-05 - SMI question for
> pktcMtaDevErrorsTooManyErrors
> 
> 
> 
>   I like Bert's proposal to create an OID to deal with the 
> internationalization issue raised by Dave and Randy. See 
> below, a quick SMI question.
> 
> Eugene integrated the comments and proposed the following text:
> pktcMtaDevErrorOid  OBJECT-TYPE  
>     SYNTAX      SnmpAdminString
>     MAX-ACCESS  read-only
>     STATUS      current
>     DESCRIPTION 
>         " This object contains a human readable representation
>           (character string) of the OID corresponding to the
>           configuration file parameter that caused the particular
>           error.
>           For example, if the value of the pktcMtaDevEnabled object

(Continue reading)