[Capwap] tsv-dir review of draft-ietf-capwap-protocol-specification-13.txt
David Borman <david.borman@windriver.com> Wed, 24 September 2008 20:35 UTC
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E14653A68A4 for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 24 Sep 2008 13:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 gSkWrXQ4wO3D for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 24 Sep 2008 13:35:54 -0700 (PDT)
Received: from hermes.alternate-outgoing.tigertech.net (hermes.alternate-outgoing.tigertech.net [64.71.157.152]) by core3.amsl.com (Postfix) with ESMTP id 0C6203A67F1 for <capwap-archive@lists.ietf.org>; Wed, 24 Sep 2008 13:35:54 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 4B2F4430BD8 for <capwap-archive@lists.ietf.org>; Wed, 24 Sep 2008 13:27:58 -0700 (PDT)
Received: from mx3.tigertech.net (mx3.tigertech.net [64.62.209.33]) by mx2.tigertech.net (Postfix) with ESMTP id 49E9D440023 for <capwap@lists.tigertech.net>; Wed, 24 Sep 2008 13:27:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id 2BC0519FF4C for <capwap@frascone.com>; Wed, 24 Sep 2008 13:27:51 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at morbo.tigertech.net
Received: from mx3.tigertech.net (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id E308719FF59 for <capwap@frascone.com>; Wed, 24 Sep 2008 13:27:49 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Neutral)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11]) by mx3.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Wed, 24 Sep 2008 13:27:49 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8OKRlY2007088; Wed, 24 Sep 2008 13:27:47 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Sep 2008 13:27:47 -0700
Received: from [172.25.34.48] ([172.25.34.48]) by ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Sep 2008 13:27:47 -0700
Message-Id: <3ECAB620-645B-462C-B28E-7DD29119602F@windriver.com>
From: David Borman <david.borman@windriver.com>
To: iesg@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 24 Sep 2008 15:27:45 -0500
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 24 Sep 2008 20:27:47.0196 (UTC) FILETIME=[01D40BC0:01C91E84]
Cc: capwap <capwap@frascone.com>, TSV Dir <tsv-dir@ietf.org>
Subject: [Capwap] tsv-dir review of draft-ietf-capwap-protocol-specification-13.txt
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com
I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. The authors should consider
this review together with any other last-call comments they receive.
Please always CC tsv-dir@… if you reply to or forward this review.
This document was originally reviewed for transport issues in 2007,
and a TSV directorate presentation was made to the CAPWAP WG during
the Chicago IETF meeting. At that time, five main issues were brought
up. While reviewing the current version of the document, I looked
specifically for these five topics. I am satisfied that they have all
been addressed. Specifically:
"3. CAPWAP Transport"
This section addresses 1) UDP checksum and 2) PMTU discovery concerns.
"11. NAT Considerations"
This section addresses the issues of 3) NAT Traversal
"14. Transport Considerations"
This section addresses 4) congestion control, as well as the
5) performance of the lock-step protocol.
I also did not see any new transport related issues in the current
CAPWAP specification, so from the viewpoint of transport
considerations, I believe that this document is ready for publication.
-David Borman, for the Transport Directorate
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap
Archives: http://lists.frascone.com/pipermail/capwap
- [Capwap] tsv-dir review of draft-ietf-capwap-prot… David Borman