Re: [Editorial Errata Reported] RFC5865 (3194)

Fred Baker <fred@cisco.com> Tue, 17 April 2012 07:45 UTC

Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55DA521F8589 for <tsvwg@ietfa.amsl.com>; Tue, 17 Apr 2012 00:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1c3RvjFhcfQ8 for <tsvwg@ietfa.amsl.com>; Tue, 17 Apr 2012 00:45:42 -0700 (PDT)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id 43C7021F8587 for <tsvwg@ietf.org>; Tue, 17 Apr 2012 00:45:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2330; q=dns/txt; s=iport; t=1334648742; x=1335858342; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=dW3Hvwu6dpJ6qgyuDH+ZHda5LshFP0M2HMEDcsMrRYk=; b=BKRB/uDJ4d3//gUpigC10ZcBFE5uUDc73lyf4n/2QpBaT57tph5gK63T 4pjYQMnkcPPIpB6AoW5wNiaiabaozLfnXCpe2/Ty0Y7o/MZFt5CWbl5MP mDduP4cNGkd2ng2XRrcAFQPeftBtP5ESYFsIe16BkLYs+AVm15pARLJZj c=;
X-IronPort-AV: E=Sophos;i="4.75,433,1330905600"; d="scan'208";a="10240440"
Received: from vla196-nat.cisco.com (HELO bgl-core-1.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 17 Apr 2012 07:45:40 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by bgl-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q3H7jarX010152; Tue, 17 Apr 2012 07:45:37 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Tue, 17 Apr 2012 00:45:39 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Tue, 17 Apr 2012 00:45:39 -0700
Subject: Re: [Editorial Errata Reported] RFC5865 (3194)
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <20120417072440.B3CDB62199@rfc-editor.org>
Date: Tue, 17 Apr 2012 00:44:48 -0700
Message-Id: <47D41F4E-BDFD-4210-A1D0-DC60DB91C77B@cisco.com>
References: <20120417072440.B3CDB62199@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org, mdolly@att.com, jmpolk@cisco.com, sergey.antipov@nsn.com
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 17 Apr 2012 07:45:47 -0000

I am not opposed to the erratum.

On Apr 17, 2012, at 12:24 AM, RFC Errata System wrote:

> 
> The following errata report has been submitted for RFC5865,
> "A Differentiated Services Code Point (DSCP) for Capacity-Admitted Traffic".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5865&eid=3194
> 
> --------------------------------------
> Type: Editorial
> Reported by: Sergey Antipov <sergey.antipov@nsn.com>
> 
> Section: 2.2
> 
> Original Text
> -------------
>   There are at least six major ways that capacity admission is done or
> 
>   has been proposed to be done for real-time applications.  Each will
> 
>   be described below, and Section 3 will judge which ones are likely to
> 
>   meet the requirements of the Admitted Telephony service class.  These
> 
>   include:
> 
> 
> 
> Corrected Text
> --------------
>   There are at least six major ways that capacity admission is done or
> 
>   has been proposed to be done for real-time applications.  Each will
> 
>   be described below, and Section 2.3 will judge which ones are likely to
> 
>   meet the requirements of the Admitted Telephony service class.  These
> 
>   include:
> 
> 
> 
> Notes
> -----
> Section 2.3 is the one, which recommends capacity admission procedures, while Section 3 summarizes proposed changes.
> 
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC5865 (draft-ietf-tsvwg-admitted-realtime-dscp-07)
> --------------------------------------
> Title               : A Differentiated Services Code Point (DSCP) for Capacity-Admitted Traffic
> Publication Date    : May 2010
> Author(s)           : F. Baker, J. Polk, M. Dolly
> Category            : PROPOSED STANDARD
> Source              : Transport Area Working Group
> Area                : Transport
> Stream              : IETF
> Verifying Party     : IESG