[Ieprep] RE: WG Review: Recharter of Internet Emergency Preparedness (ieprep)

"Dolly, Martin C, ALABS" <mdolly@att.com> Thu, 16 November 2006 12:01 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkfvX-0004UR-Sy; Thu, 16 Nov 2006 07:01:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkfvW-0004UD-B2; Thu, 16 Nov 2006 07:01:06 -0500
Received: from mail146.messagelabs.com ([216.82.245.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GkfvU-0007c1-2W; Thu, 16 Nov 2006 07:01:06 -0500
X-VirusChecked: Checked
X-Env-Sender: mdolly@att.com
X-Msg-Ref: server-9.tower-146.messagelabs.com!1163678463!9337589!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 11703 invoked from network); 16 Nov 2006 12:01:03 -0000
Received: from unknown (HELO attrh9i.attrh.att.com) (134.24.146.4) by server-9.tower-146.messagelabs.com with SMTP; 16 Nov 2006 12:01:03 -0000
Received: from attrh.att.com (localhost [127.0.0.1]) by attrh9i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kAGBsFmi003663; Thu, 16 Nov 2006 06:54:16 -0500 (EST)
Received: from OCCLUST04EVS1.ugd.att.com (ocst07.ugd.att.com [135.38.164.12]) by attrh9i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kAGBs7j5003623; Thu, 16 Nov 2006 06:54:08 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 16 Nov 2006 06:00:53 -0600
Message-ID: <28F05913385EAC43AF019413F674A017101B71F6@OCCLUST04EVS1.ugd.att.com>
In-Reply-To: <Pine.LNX.4.64.0611160919090.5636@netcore.fi>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: WG Review: Recharter of Internet Emergency Preparedness (ieprep)
Thread-Index: AccJU0n7xxk44BK3SP2Hzmvj8WrOAgAI3FZA
From: "Dolly, Martin C, ALABS" <mdolly@att.com>
To: "Pekka Savola" <pekkas@netcore.fi>, "Fred Baker" <fred@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org, ieprep@ietf.org, Scott Bradner <sob@harvard.edu>
Subject: [Ieprep] RE: WG Review: Recharter of Internet Emergency Preparedness (ieprep)
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
Errors-To: ieprep-bounces@ietf.org

Pekka,

At least two carriers, AT&T and Verizon support, "An EF DSCP for
Capacity-Admitted Traffic", Fred Baker, 6-Oct-06

Martin  

-----Original Message-----
From: Pekka Savola [mailto:pekkas@netcore.fi] 
Sent: Thursday, November 16, 2006 2:32 AM
To: Fred Baker
Cc: Sam Hartman; ietf@ietf.org; ieprep@ietf.org; Scott Bradner
Subject: Re: WG Review: Recharter of Internet Emergency Preparedness
(ieprep)

On Wed, 15 Nov 2006, Fred Baker wrote:
> We also specifically addressed their requirements (in tsvwg)
operationally:
> 
> >http://www.ietf.org/rfc/rfc4594.txt
> >4594 Configuration Guidelines for DiffServ Service Classes. J.
> >     Babiarz, K. Chan, F. Baker. August 2006. (Format: TXT=144044
bytes)
> >     (Status: INFORMATIONAL)
> >
> >http://tools.ietf.org/html/draft-ietf-tsvwg-diffserv-class-aggr
> >  "Aggregation of DiffServ Service Classes", Kwok Ho Chan, 22-Oct-06
> >and
> >http://tools.ietf.org/html/draft-baker-tsvwg-admitted-voice-dscp
> >  "An EF DSCP for Capacity-Admitted Traffic", Fred Baker, 6-Oct-06
> 
> The last two are in last call and in discussion in tsvwg respectively.

All of these documents are, or are aimed at Informational.  I do not 
see how those could define DSCP codepoints or behaviour -- doing so 
requires Standards Action and certain codepoint pools are reserved for 
local/private use (which specifying them is not).  I wonder how wide 
IETF or operator consensus is behind this work.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep