Review of draft-ietf-behave-dccp-04

Christian Vogt <christian.vogt@ericsson.com> Thu, 06 November 2008 12:08 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC7593A69E7; Thu, 6 Nov 2008 04:08:34 -0800 (PST)
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 2264B3A69F1 for <ietf@core3.amsl.com>; Thu, 6 Nov 2008 04:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.147
X-Spam-Level:
X-Spam-Status: No, score=-6.147 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 cWXsI22mxXh0 for <ietf@core3.amsl.com>; Thu, 6 Nov 2008 04:08:32 -0800 (PST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 1CFEA3A69A7 for <ietf@ietf.org>; Thu, 6 Nov 2008 04:08:31 -0800 (PST)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id C6AFC20E9C; Thu, 6 Nov 2008 13:07:50 +0100 (CET)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-61-4912de164d9e
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 8268B20F0C; Thu, 6 Nov 2008 13:07:50 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 6 Nov 2008 13:07:48 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 6 Nov 2008 13:07:45 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 98CE926A4; Thu, 6 Nov 2008 14:07:45 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 6836F4DABE; Thu, 6 Nov 2008 14:07:45 +0200 (EET)
Message-Id: <3873DF72-B768-427B-A6F5-99778DF5DC02@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Review of draft-ietf-behave-dccp-04
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 06 Nov 2008 14:07:41 +0200
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 06 Nov 2008 12:07:46.0044 (UTC) FILETIME=[4782CBC0:01C94008]
X-Brightmail-Tracker: AAAAAA==
Cc: Behave Chairs <behave-chairs@tools.ietf.org>, rem@videolan.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-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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Folks,

I was asked to review draft-ietf-behave-dccp-04 as input for IESG
evaluation, and I got three comments:

(1) On the abstract:

         Developing NATs that meet this set of requirements will greatly
         increase the likelihood that applications using DCCP will
         function properly.

     Sounds a bit like DCCP would work well only if we develop NATs. ;-)
     Better reword to:

         Ensuring that NATs meet this set of requirements will greatly
         increase the likelihood that applications using DCCP will
         function properly.

(2) On requirements 1 and 3:

         REQ-1: A NAT MUST have an "Endpoint-Independent Mapping"
         behavior for DCCP.

         REQ-3: If application transparency is most important, it is
         RECOMMENDED that a NAT have an "Endpoint-independent filtering"
         behavior for DCCP.  If a more stringent filtering behavior is
         most important, it is RECOMMENDED that a NAT have an
         "Address-dependent filtering" behavior.

     These requirements are general and not specific to DCCP.  Would it
     make sense to specify them in a separate RFC for NATs in general,
     independent of any specific transport protocol?

(3) On requirement 6:

         REQ-6: If a NAT includes ALGs, it MUST NOT affect DCCP.

     This requirement is not 100% clear.  I am assuming it means:  "If a
     NAT includes ALGs, the NAT MUST NOT affect DCCP packets that are
     processed by one of those ALGs."  Suggest to reword the requirement
     in this way.

- Christian


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