[Tsvwg] Fw: New Version Notification for draft-ietf-tsvwg-rsvp-user-error-spec-08
"Adrian Farrel" <adrian@olddog.co.uk> Sat, 31 May 2008 10:49 UTC
Return-Path: <tsvwg-bounces@ietf.org>
X-Original-To: tsvwg-archive@optimus.ietf.org
Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FD2F3A6A72; Sat, 31 May 2008 03:49:18 -0700 (PDT)
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2977D3A6A72 for <tsvwg@core3.amsl.com>; Sat, 31 May 2008 03:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.622
X-Spam-Level:
X-Spam-Status: No, score=-0.622 tagged_above=-999 required=5 tests=[AWL=1.976, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mFHk8RzFNoYs for <tsvwg@core3.amsl.com>; Sat, 31 May 2008 03:49:16 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by core3.amsl.com (Postfix) with ESMTP id E0DDA3A69CB for <tsvwg@ietf.org>; Sat, 31 May 2008 03:49:15 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id m4VAn3gr012947; Sat, 31 May 2008 11:49:03 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id m4VAn1D0012939; Sat, 31 May 2008 11:49:02 +0100
Message-ID: <001401c8c30b$ecf847d0$0200a8c0@your029b8cecfe>
From: Adrian Farrel <adrian@olddog.co.uk>
To: Chris Newman <chris.newman@sun.com>, tsvwg <tsvwg@ietf.org>
Date: Sat, 31 May 2008 11:48:51 +0100
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="UTF-8"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Cc: George Swallow <swallow@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, jari.arkko@piuha.net
Subject: [Tsvwg] Fw: New Version Notification for draft-ietf-tsvwg-rsvp-user-error-spec-08
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
Hi Chris, The new revision of this I-D is intended to address your concerns. I have moved over to UTF-8 with references and a recommendation to limit to US-ASCII. I have also commented on how to handle UTF-8 in an ASCII system, and briefly noted the security risk of character strings in a protocol. Having discussed language codes, we have decided not to include them. The only reason for not including them is that no-one in the WG expressed any support. Let me know what you think. Hoping you will clear. Cheers, Adrian ----- Original Message ----- From: "IETF I-D Submission Tool" <idsubmission@ietf.org> To: <adrian@olddog.co.uk> Cc: <swallow@cisco.com> Sent: Saturday, May 31, 2008 11:44 AM Subject: New Version Notification for draft-ietf-tsvwg-rsvp-user-error-spec-08 > > A new version of I-D, draft-ietf-tsvwg-rsvp-user-error-spec-08.txt has > been successfuly submitted by Adrian Farrel and posted to the IETF > repository. > > Filename: draft-ietf-tsvwg-rsvp-user-error-spec > Revision: 08 > Title: User-Defined Errors for RSVP > Creation_date: 2008-05-31 > WG ID: tsvwg > Number_of_pages: 9 > > Abstract: > 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. > > > > The IETF Secretariat. > > >
- [Tsvwg] Fw: New Version Notification for draft-ie… Adrian Farrel
- Re: [Tsvwg] Fw: New Version Notification for draf… Magnus Westerlund