Re: [secdir] secdir review of draft-ietf-slim-negotiating-human-language-22

Randall Gellens <rg+ietf@randy.pensive.org> Thu, 11 January 2018 15:10 UTC

Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC45912420B; Thu, 11 Jan 2018 07:10:47 -0800 (PST)
X-Quarantine-ID: <leBp9rThIXgR>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 leBp9rThIXgR; Thu, 11 Jan 2018 07:10:46 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5A4751204DA; Thu, 11 Jan 2018 07:10:46 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 11 Jan 2018 07:11:19 -0800
Mime-Version: 1.0
Message-Id: <p06240600d67d2e5fcbb7@[99.111.97.136]>
In-Reply-To: <ldv8td55b41.fsf@ubuntu-1gb-nyc1-01.localdomain>
References: <ldv8td55b41.fsf@ubuntu-1gb-nyc1-01.localdomain>
X-Mailer: Eudora for Mac OS X
Date: Thu, 11 Jan 2018 07:10:43 -0800
To: Taylor Yu <tlyu@mit.edu>, iesg@ietf.org, secdir@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/F3Y3L0IKtRP0sygmr8Ylkw_yc7I>
Subject: Re: [secdir] secdir review of draft-ietf-slim-negotiating-human-language-22
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 11 Jan 2018 15:10:48 -0000

At 3:26 AM +0000 1/11/18, Taylor Yu wrote:

>  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.
>
>  Summary: ready with minor issues
>
>  The security considerations section seems mostly reasonable.  The
>  emergency services use case vaguely bothered me in ways I couldn't quite
>  articulate at first, but I think Alissa Cooper's ballot comment about
>  denying emergency services by manipulating these attributes captures
>  most of the essence.
>
>  I would add for that these new language tags, integrity seems to be a
>  stronger requirement than confidentiality, at least in the emergency
>  calling use case.

Hi Taylor,

Thanks for your review.  In response to Alissa's comments, I reworded 
the Security Considerations section to read:

    The Security Considerations of BCP 47 [RFC5646] apply here.  An
    attacker with the ability to modify signaling could prevent a call
    from succeeding by altering any of several crucial elements,
    including the 'hlang-send' or 'hlang-recv' values.  RFC 5069
    [RFC5069] discusses such threats.  Use of TLS or IPSec can protect
    against such threats.  Emergency calls are of particular concern; RFC
    6881 [RFC6881], which is specific to emergency calls, mandates use of
    TLS or IPSec (in ED-57/SP-30).

I think this also addresses your concern regarding integrity, as it 
specifically calls out "modification" as a principal threat.

--Randall



-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Substitute "damn" every time you're inclined to write "very"; your
editor will delete it and the writing will be just as it should be.
              --William Allen White (famed Kansas newspaper editor)