Re: [Tsvwg] I-D Action:draft-ietf-tsvwg-rsvp-user-error-spec-05.txt

["tom.petch" <[e-mail]>]

And updated again:-) comments on -06

Two areas in which this I-D might be more helpful.

Enterprise number; RFC2578 is sort of the reference for this but unhelpful when
it comes to doing anything about it.  For example, in the ietf-syslog-protocol
I-D, Reiner Gerhards included

"7.2.2.  enterpriseId

   The "enterpriseId" parameter MUST be a 'SMI Network Management
   Private Enterprise Code', maintained by IANA, whose prefix is
   iso.org.dod.internet.private.enterprise (1.3.6.1.4.1).  The number
   that follows is unique and may be registered by an on-line form at
   <http://www.iana.org/cgi-bin/mod_ent.pl>.  An enterprise is only
   authorized to assign values within the
   iso.org.dod.internet.private.enterprise.<enterprise ID> subtree
   assigned by IANA to that enterprise.  The enterpriseId MUST contain
   only a value from the
   iso.org.dod.internet.private.enterprise.<enterprise ID> subtree.  In
   general, only the IANA-assigned enterpriseID is needed (a single
   number).  An enterprise might decide to use sub-identifiers below its
   enterpriseID.  If sub-identifiers are used, they MUST be separated by
   periods and be represented as decimal numbers.  An example for that
   would be "0.1.2".  Please note that the id "0.1.2" is just an example
   and MUST NOT be used.  The complete up-to-date list of Enterprise
   Numbers is maintained by IANA at
   <http://www.iana.org/assignments/enterprise-numbers>.

   By specifying an enterpriseId, the vendor allows more specific
   processing of the message."

which, with a few changes from enterpriseId to Enterprise Number and some
elision, could help implementers more.

Likewise 'US-ASCII' is a bit vague; 7 bit, printable ???  Again the syslog I-D
is more specific and includes an ANSI reference, to whit

[ANSI.X3-4.1968] American National Standards Institute, "USA Code for
Information Interchange", ANSI X3.4, 1968.


Tom Petch



----- Original Message -----
From: "Adrian Farrel" <[e-mail]>
To: "tsvwg" <[e-mail]>
Sent: Tuesday, April 01, 2008 11:46 AM
Subject: Re: [Tsvwg] I-D Action:draft-ietf-tsvwg-rsvp-user-error-spec-05.txt


> Updated after discussion with Jukka.
> Adrian
>
> >A New Internet-Draft is available from the on-line Internet-Drafts
> >directories.
> >
> > Title           : User-Defined Errors for RSVP
> > Author(s)       : G. Swallow, A. Farrel
> > Filename        : draft-ietf-tsvwg-rsvp-user-error-spec-05.txt
> > Pages           : 8
> > Date            : 2008-04-01
> >
> > The Resource ReserVation Protocol (RSVP) defines an ERROR_SPEC object
> > for communicating errors.  That object has a defined format that
> > permits the definition of 256 error codes.  As RSVP has been
> > developed and extended, the convention has been to be conservative in
> > defining new error codes.  Further, no provision for user-defined
> > errors exists in RSVP.
> >
> > This document defines a USER_ERROR_SPEC to be used in addition to the
> > ERROR_SPEC to carry additional user information related to errors.
> >
> > A URL for this Internet-Draft is:
> >
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-user-error-spec-05.txt
>
>