Re: My comments to the press about RFC 2474
Russ Housley <housley@vigilsec.com> Tue, 07 September 2010 22:51 UTC
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AAD03A69A2 for <ietf@core3.amsl.com>; Tue, 7 Sep 2010 15:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.596
X-Spam-Level:
X-Spam-Status: No, score=-103.596 tagged_above=-999 required=5 tests=[AWL=1.003, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
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 Y7OsU64zj7DW for <ietf@core3.amsl.com>; Tue, 7 Sep 2010 15:51:35 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id CBFF83A699A for <ietf@ietf.org>; Tue, 7 Sep 2010 15:51:34 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D5B439A4749; Tue, 7 Sep 2010 18:52:14 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id oBr2wFlEE3nd; Tue, 7 Sep 2010 18:52:01 -0400 (EDT)
Received: from [192.168.2.101] (pool-96-231-149-87.washdc.fios.verizon.net [96.231.149.87]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 350239A472B; Tue, 7 Sep 2010 18:52:14 -0400 (EDT)
Message-ID: <4C86C215.9080209@vigilsec.com>
Date: Tue, 07 Sep 2010 18:52:05 -0400
From: Russ Housley <housley@vigilsec.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Richard Bennett <richard@bennett.com>
Subject: Re: My comments to the press about RFC 2474
References: <4C815335.4050209@bennett.com> <4C81554D.5060000@gmail.com> <4C8169DF.7010202@bennett.com> <4C8172AC.9060202@gmail.com> <4C817866.7040400@bennett.com>
In-Reply-To: <4C817866.7040400@bennett.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 22:51:36 -0000
Richard: > Russ said to the press that he considers AT&T's belief that the RFCs > envisioned payment for premium services implemented over DiffServ or > MPLS to be "invalid." This is not what I said. I said 'misleading.' The letter from AT&T jumbles some things together. AT&T makes many correct points, but in my opinion, a reader will get a distorted impression from the parts of the letter where things get jumbled. Adding to this situation, it is clear to me that the term "paid prioritization" does not have the same meaning to all readers. If you read the AT&T letter with one definition in your head, then you get one overall message, and if you read the letter with the other in your head, then you get a different overall message. I tried to make this point. This was captured pretty clearly in the article by Eliza Krigman: | The feud boiled down to what it means to have "paid | prioritization," ... As I said on Friday, I made the point that DiffServ can be used to make sure that traffic associated with applications that require timely delivery, like voice and video, to give preference over traffic associated with applications without those demands, like email. Unfortunately, it is not simple, and I said so. I used an example in my discussion with Declan McCullagh. I think that Declan captured this point in his article, except that he said 'high priority', when I actually said 'requiring timely delivery': | The disagreement arises from what happens if Video Site No. 1 and | Video Site No. 2 both mark their streams as high priority. "If two | sources of video are marking their stuff the same, then that's where | the ugliness of this debate begins," Housley says. "The RFC doesn't | talk about that...If they put the same tags, they'd expect the same | service from the same provider." Clearly, if the two video sources have purchased different amounts of bandwidth, then the example breaks down. However, that is not the point in this debate. Russ
- Re: My comments to the press about RFC 2474 Brian E Carpenter
- RE: My comments to the press about RFC 2474 Richard Shockey
- My comments to the press about RFC 2474 Russ Housley
- Re: My comments to the press about RFC 2474 Brian E Carpenter
- Re: My comments to the press about RFC 2474 Phillip Hallam-Baker
- Re: My comments to the press about RFC 2474 Marshall Eubanks
- Re: My comments to the press about RFC 2474 David Morris
- Re: My comments to the press about RFC 2474 Russ Housley
- Re: My comments to the press about RFC 2474 John C Klensin
- Re: My comments to the press about RFC 2474 Ofer Inbar
- RE: My comments to the press about RFC 2474 Worley, Dale R (Dale)
- RE: My comments to the press about RFC 2474 Richard Shockey
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Brian E Carpenter
- Re: My comments to the press about RFC 2474 Brian E Carpenter
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Brian E Carpenter
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Randall Gellens
- Re: My comments to the press about RFC 2474 Livingood, Jason
- Re: My comments to the press about RFC 2474 Livingood, Jason
- Re: My comments to the press about RFC 2474 Richard Bennett
- RE: My comments to the press about RFC 2474 Richard Shockey
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Matthew Ford
- Re: My comments to the press about RFC 2474 DOLLY, MARTIN C (ATTLABS)
- RE: My comments to the press about RFC 2474 Chris Fenton (Iridescent)
- Re: My comments to the press about RFC 2474 Patrik Faltstrom (pfaltstr)
- Re: My comments to the press about RFC 2474 Ben Niven-Jenkins
- RE: My comments to the press about RFC 2474 Worley, Dale R (Dale)
- Re: My comments to the press about RFC 2474 Russ Housley
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Brian E Carpenter
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Marshall Eubanks
- Re: My comments to the press about RFC 2474 Marshall Eubanks
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Marshall Eubanks
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Brian E Carpenter
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Randall Gellens
- Re: My comments to the press about RFC 2474 Mans Nilsson
- Re: My comments to the press about RFC 2474 Theodore Tso
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: My comments to the press about RFC 2474 Theodore Tso
- The Evils of Informational RFC's Eric Burger
- Re: The Evils of Informational RFC's Paul Hoffman
- Re: The Evils of Informational RFC's Iljitsch van Beijnum
- Re: My comments to the press about RFC 2474 Phillip Hallam-Baker
- Re: My comments to the press about RFC 2474 Phillip Hallam-Baker
- Re: The Evils of Informational RFC's Jorge Amodio
- Re: My comments to the press about RFC 2474 Gene Gaines
- Re: My comments to the press about RFC 2474 Eric Burger
- Re: The Evils of Informational RFC's Bob Hinden
- Re: The Evils of Informational RFC's Eric Burger
- Re: My comments to the press about RFC 2474 Richard Bennett
- RE: The Evils of Informational RFC's Ronald Bonica
- Re: The Evils of Informational RFC's Richard L. Barnes
- Re: The Evils of Informational RFC's Bob Hinden
- Re: The Evils of Informational RFC's Jorge Amodio
- Re: The Evils of Informational RFC's Brian E Carpenter
- Re: My comments to the press about RFC 2474 Richard Bennett
- Re: The Evils of Informational RFC's Richard Bennett
- Re: The Evils of Informational RFC's Richard L. Barnes
- Re: The Evils of Informational RFC's Andrew G. Malis
- Re: The Evils of Informational RFC's Brian E Carpenter
- Re: The Evils of Informational RFC's Stephen Farrell
- Re: The Evils of Informational RFC's David Morris
- Re: The Evils of Informational RFC's Fred Baker
- Re: The Evils of Informational RFC's Olaf Kolkman
- Re: The Evils of Informational RFC's Richard Bennett
- RE: The Evils of Informational RFC's Richard Shockey
- Re: The Evils of Informational RFC's Phillip Hallam-Baker
- Re: My comments to the press about RFC 2474 Phillip Hallam-Baker
- Re: The Evils of Informational RFC's Dave CROCKER
- Re: My comments to the press about RFC 2474 Phillip Hallam-Baker
- Re: The Evils of Informational RFC's Kevin Fall
- Re: The Evils of Informational RFC's Phillip Hallam-Baker
- Re: The Evils of Informational RFC's Bob Braden
- Re: The Evils of Informational RFC's Sam Hartman
- Re: The Evils of Informational RFC's Russ Housley
- Re: My comments to the press about RFC 2474 Yoav Nir
- Re: The Evils of Informational RFC's Jari Arkko
- Re: The Evils of Informational RFC's Dave CROCKER
- Re: My comments to the press about RFC 2474 Randall Gellens