[secdir] SECDIR review of draft-ietf-straw-b2bua-loop-detection-04

Chris Lonvick <lonvick.ietf@gmail.com> Fri, 18 April 2014 22:58 UTC

Return-Path: <lonvick.ietf@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3CC51A01F0; Fri, 18 Apr 2014 15:58:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5NrQtgizffqX; Fri, 18 Apr 2014 15:58:42 -0700 (PDT)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 756771A01B5; Fri, 18 Apr 2014 15:58:42 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id md12so1869032pbc.35 for <multiple recipients>; Fri, 18 Apr 2014 15:58:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=L73IoCi4E7GQ+MunKwnpH9COx+Zn3CgE/RKvnx7UtW8=; b=qC7BFRHalJ7M5Rf+eA+kjrYtrMy8WGpeofyWdiIQ4uFucIcxvgrCWWROXRNGh1pZ5c a+kVYJYPO1AuFIaCZamGOC62RJlWbHLyIVDpFSotgnCgOztjtG3QVCgLN1vsmnFy775K JuYrIxY+nhahgXb3fxynM18ld2g32enOCQe112wB/ymeH/mBmsQmGsjtaGnpzegWGAGj wxLXFunJ/vzliG7PmZyrxG0tFNjeTcWHeHQWJRQoIAKMNIOibMu5N7sFVQvVReV16NMd 9ZFeLXPaW6fbHi1FIdHWXMIIoHRC+caAEAjndTDG75O70C0nlq0uGhvWvEod5oPDRRqb C11A==
X-Received: by 10.66.252.135 with SMTP id zs7mr24532699pac.13.1397861918525; Fri, 18 Apr 2014 15:58:38 -0700 (PDT)
Received: from [10.19.75.99] (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPSA id ba5sm62090748pbc.61.2014.04.18.15.58.36 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Apr 2014 15:58:37 -0700 (PDT)
Message-ID: <5351AE1C.1000603@gmail.com>
Date: Fri, 18 Apr 2014 15:58:36 -0700
From: Chris Lonvick <lonvick.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: draft-ietf-straw-b2bua-loop-detection@tools.ietf.org, iesg@ietf.org, secdir@ietf.org
Content-Type: multipart/alternative; boundary="------------090606000707040406090204"
Archived-At: http://mailarchive.ietf.org/arch/msg/secdir/MQnsdzhs-qGNHQbrG7sgmtjSJRw
X-Mailman-Approved-At: Fri, 18 Apr 2014 16:02:31 -0700
Subject: [secdir] SECDIR review of draft-ietf-straw-b2bua-loop-detection-04
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 18 Apr 2014 22:58:43 -0000

Hi,

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.

The document is well written and I agree that the Security Considerations
section of RFC 5393 pretty much covers everything in this document.

I don't feel strongly about this\, but the authors may wish to describe
what could happen if one B2BUA adheres to the specifications described in
this document (adds appropriate header information when it finds none)
and an old B2BUA that has not implemented these specifications (may strip
out Via header information) causing a loop to encourage everyone to
implement the recommendations in this specification.

Regards,
Chris