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

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Sat, 06 October 2007 14:03 UTC

Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IeAFf-00031h-AN; Sat, 06 Oct 2007 10:03:31 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1IeAFd-00030l-UG for tsvwg-confirm+ok@megatron.ietf.org; Sat, 06 Oct 2007 10:03:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IeAFd-0002wM-Kc for tsvwg@ietf.org; Sat, 06 Oct 2007 10:03:29 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IeAFP-0005wx-36 for tsvwg@ietf.org; Sat, 06 Oct 2007 10:03:21 -0400
Received: (qmail invoked by alias); 06 Oct 2007 14:02:51 -0000
Received: from p5498668F.dip.t-dialin.net (EHLO [192.168.1.4]) [84.152.102.143] by mail.gmx.net (mp057) with SMTP; 06 Oct 2007 16:02:51 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18RktckJvcR9pIzO+yNYDhXzLQSzI6ZAOzv9kGV43 h7pM6x7YKh15AZ
Message-ID: <4707958D.3000704@gmx.net>
Date: Sat, 06 Oct 2007 16:02:53 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: [Tsvwg] I-D Action:draft-ietf-tsvwg-rsvp-user-error-spec-02.txt
References: <E1Ie8Tq-0007X6-B5@stiedprstage1.ietf.org>
In-Reply-To: <E1Ie8Tq-0007X6-B5@stiedprstage1.ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

If I understood this document correctly then it essentially suggests 
vendor-specific error codes.

Typically, you use three octets to denote the vendor-specific Object 
Identifier (OID) that points to the IANA assigned "SMI Network 
Management Private Enterprise Codes" value (see [RFC3232]). Then, you 
need to provide a field for the error code. Often 3 bytes are 
sufficient. You seem to split these 3 bytes into 1 byte for a "Sub Org " 
and another 2 bytes for the actual error code value. I believe it is 
more common to just merge the 1+2 bytes together since a vendor will 
hopefully be able to manage the allocation of unique values.

I further suspect that you wrote this draft not really for vendors but 
rather for other SDOs, since they are also listed as vendors.

If my reading of the draft is correct then I wonder why you call the 
document "user-defined" errors instead of vendor-specific error codes 
for RSVP.
Do you think that it is so common that vendors or other SDOs will define 
their own error messages? Could that lead to interoperability problems?

Ciao
Hannes

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Transport Area Working Group Working Group of the IETF.
>
>
> 	Title           : User-Defined Errors for RSVP
> 	Author(s)       : G. Swallow, et al.
> 	Filename        : draft-ietf-tsvwg-rsvp-user-error-spec-02.txt
> 	Pages           : 8
> 	Date            : 2007-10-06
>
> 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.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-user-error-spec-02.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of 
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the 
> username "anonymous" and a password of your e-mail address. After 
> logging in, type "cd internet-drafts" and then
> 	"get draft-ietf-tsvwg-rsvp-user-error-spec-02.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-tsvwg-rsvp-user-error-spec-02.txt".
>
> NOTE:   The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>