[secdir] Review of draft-ietf-pcn-baseline-encoding-05

Magnus Nyström <magnusn@gmail.com> Tue, 01 September 2009 23:45 UTC

Return-Path: <magnusn@gmail.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 04C5C3A70CE; Tue, 1 Sep 2009 16:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 jsbQD2Hgnexb; Tue, 1 Sep 2009 16:45:20 -0700 (PDT)
Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com [209.85.219.207]) by core3.amsl.com (Postfix) with ESMTP id D9B673A6995; Tue, 1 Sep 2009 16:45:19 -0700 (PDT)
Received: by ewy3 with SMTP id 3so317598ewy.42 for <multiple recipients>; Tue, 01 Sep 2009 16:45:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=fhYPqmPKRljGZkTWhFX5qsw15BqA0OyD92nGb5uWVyg=; b=MOXKdEOyb0F2AGsE4NklWjQD9Q4OIEFRrt0HuLHuPro1oxXlTNoIyYktI5TkwdNyLH VPHrMeFggXG0/2S+FrmrT6Qg62TO7WLS+w8eZHGS127nFKAaVoTI7Y6zg8QctfuVtI06 dPSWRNhoSFjcfFEo3F3YiKfe783Su4ykDA41Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=FVKjd55+UuOuzDaBTi2+WsmpRDV9xhStcrN+ax/wysI/X6oA7eLogyKroQhXL7zG/V hUvOuBvVf/NPD3Zg3nrPWsWFeWOLDaJjbspIMDHhfcysAR1cCv1BRWgjFy6/IFlT2X4t hfJ12hq/N3I9zyByN6C7ug/+5TPGbbC/pxZF0=
MIME-Version: 1.0
Received: by 10.211.159.19 with SMTP id l19mr7966185ebo.83.1251848730061; Tue, 01 Sep 2009 16:45:30 -0700 (PDT)
Date: Tue, 1 Sep 2009 16:45:30 -0700
Message-ID: <2f57b9e60909011645w3d23f4d9m23bdbc278d84efd0@mail.gmail.com>
From: =?ISO-8859-1?Q?Magnus_Nystr=F6m?= <magnusn@gmail.com>
To: iesg@ietf.org, secdir@ietf.org, toby.moncaster@bt.com, bob.briscoe@bt.com, menth@informatik.uni-wuerzburg.de, sob@harvard.edu, slblake@petri-meat.com
Content-Type: text/plain; charset=ISO-8859-1
Subject: [secdir] Review of draft-ietf-pcn-baseline-encoding-05
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2009 23:45:21 -0000

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

Overview:

Loosely, this document describes a way of pre-congestion notification
marking of packets that builds on the Explicit Congestion Notification
(RFC 3168). The marking is only carrying meaning within a given PCN
domain.

Comments:

With the caveat of not being an expert in the field this draft is
about, I find the document relatively straightforward to understand
and the Security Considerations section reasonably complete (although
it perhaps would have been useful to describe what problems that
possibly could occur should a party inject PCN-marked packets inside a
network?).

Editorial:

Maybe useful to add a brief early section providing definitions of
abbreviations?

-- Magnus