Re: [secdir] SECDIR review of draft-freytag-lager-variant-rules-03

Chris Lonvick <lonvick.ietf@gmail.com> Tue, 31 January 2017 13:40 UTC

Return-Path: <lonvick.ietf@gmail.com>
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 745B2129473; Tue, 31 Jan 2017 05:40:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HHsf344sF7OV; Tue, 31 Jan 2017 05:40:16 -0800 (PST)
Received: from mail-ot0-x243.google.com (mail-ot0-x243.google.com [IPv6:2607:f8b0:4003:c0f::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FBE3129EE5; Tue, 31 Jan 2017 05:34:39 -0800 (PST)
Received: by mail-ot0-x243.google.com with SMTP id 73so41803188otj.1; Tue, 31 Jan 2017 05:34:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=3/txZ6hHARkHyr+KnfhMoGyiRpqfh1WSBoMzUoZOQaQ=; b=BvZxdZEoJYMu7IL0xe0YiFJGLhUHiw8qrVWt0xKYfdO93l8LLkuV7QxdDJ5MgJvP2S 0UsfHDmyQGy2FNP5nalJ4s4uHnq2PXqF25irglaVBOVLe8xwY4jELMS3FBXT7yN54Az+ u1qPNgx/KvWMmAQ4KjUJ0+ique8pQjORVH7jM2UvAnNOCN4A6yiDE5ezyF2grLOhvvlE L3nZUb20hv7cvoA0MVBmRePwdo3tAknWN11o6B5anBywuhu0vJkzj4ayqwxJ9AjhQ6JQ IP0lo8+98CKUE9NsL7ltfCXqXA6BGkOcb213fF5OVasMddySDJnI0CjeL4B2BSJNSeiy Fm+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=3/txZ6hHARkHyr+KnfhMoGyiRpqfh1WSBoMzUoZOQaQ=; b=hAKxG+MFKmaXWfj4scvt6fSORT9SrRsjTbM32fvJrS1uYHpV7IM/Op1Id2rYDJIRXx q4WW9dOgxryl+C8bHQ4Hz5ayPQvvbqDIGRvElQFa+GUqbqDRarjHjL5Mxk7qbjgcF2oK XMM7asXBYlDzTQQDo2tQVvmTqOZ8/XsWNy6aAfLOeX2g53qOxdL3IXBACXEoIdWloAIA uvj/VPDaGB80xc41Cs/0BHyvI0Y1P7lLm1HDDD8pXsGv25gItu2yf65JtTVtstYdtUcN XgibxeYKqNkOwuLKasWDa5QluljizCo+byqmRQeB3x4+5+k8ZrHTaUdGEPkCtQL9ZS0e whUA==
X-Gm-Message-State: AIkVDXJhlxMzrdbg0MkDQd5+zTwOPg2lK2FfWkSbpH3Fov2nR0bx31JiDLOHBsNj9gyOTg==
X-Received: by 10.157.21.19 with SMTP id u19mr12281929otf.229.1485869678412; Tue, 31 Jan 2017 05:34:38 -0800 (PST)
Received: from Chriss-MacBook-Air.local ([216.201.230.154]) by smtp.googlemail.com with ESMTPSA id r41sm8756129otc.40.2017.01.31.05.34.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2017 05:34:38 -0800 (PST)
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "iesg@ietf.org" <iesg@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>, "draft-freytag-lager-variant-rules.all@ietf.org" <draft-freytag-lager-variant-rules.all@ietf.org>
References: <588EA8FF.5030105@gmail.com> <831693C2CDA2E849A7D7A712B24E257F4A52AA1D@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
From: Chris Lonvick <lonvick.ietf@gmail.com>
Message-ID: <5890926D.1020903@gmail.com>
Date: Tue, 31 Jan 2017 07:34:37 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A52AA1D@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Content-Type: multipart/alternative; boundary="------------000309030202080809080105"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/-PLDqCkJaif2aIb8Ks3c-Rl2aGQ>
Subject: Re: [secdir] SECDIR review of draft-freytag-lager-variant-rules-03
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 31 Jan 2017 13:40:17 -0000

Hi Scott,

Oops. :-) The assignment I got on the 19th was for -02 which was what I 
reviewed. I got a reminder on the 26th which was for -03 so I just put 
that in. And yes, I did mean 7940.

The Security Considerations section is much better in -03. However, if 
it is possible, I would still like to see something more in there. RFC 
7940 has a short section in its Security Considerations section, noted 
below, about how LGRs are only a partial remedy to the problem. The new 
Security Considerations section in -03 seems to indicate that the 
problem space may be constrained by properly utilizing certain optional 
features of 7940. If that is correct, then perhaps the author would 
consider revising the last part of the second paragraph to more clearly 
state that?

Current:

    By including
    certain declarations that are optional under the schema and may not
    alter the results of processing a label, such an LGR supports the
    task of review and verification by more clearly expressing the
    intent.


Proposed:
    Utilizing certain optional declarations under the schema provides a 
clear expression
    of the label. When properly used, the label becomes unalterable and 
observably
    verifiable.

 From there, I would also like to see a quick statement about any other 
areas that implementers should be aware of that are not addressed in 
this document. I'm not familiar enough with this technology to know if 
there is or isn't. If there are no other issues, or they are far outside 
the scope of this document, then don't worry about it.

Regards,
Chris


On 1/30/17 12:48 PM, Hollenbeck, Scott wrote:
> Thanks for the review, Chris. I should note that my document shepherd 
> review of the -02 version of this draft also produced feedback about 
> the need to add Security Considerations text. The author added text 
> and published the -03 version on 23 January. Chris, could you please 
> look at -03 and see how well the text addresses your comments modulo 
> what you’ve shared below? I assume that you meant RFC 7940 
> (Representing Label Generation Rulesets Using XML) when you wrote RFC 
> 7948 (Internet Exchange BGP Route Server Operations).
>
> Scott
>
> *From:*Chris Lonvick [mailto:lonvick.ietf@gmail.com]
> *Sent:* Sunday, January 29, 2017 9:46 PM
> *To:* iesg@ietf.org; secdir@ietf.org; 
> draft-freytag-lager-variant-rules.all@ietf.org
> *Subject:* [EXTERNAL] SECDIR review of 
> draft-freytag-lager-variant-rules-03
>
> 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.
>
> I consider this draft to be ready with issues.
>
> The document is well written and thorough but has no content in the 
> Security Considerations section. The guidance provided in this 
> INFORMATIONAL document appears to be sound but it should still provide 
> a statement of how this work attempts to address the security concerns 
> of RFC 7948. For perspective, the title of section 12.1 of the 
> Security Considerations section is "LGRs Are Only a Partial Remedy for 
> Problem Space".
>
> My recommendation is that a Security Considerations section for this 
> document incorporate the Security Considerations section of RFC 7948, 
> along with statements of how the document addresses the obtainable 
> remediations, and what implementers should continue to be concerned 
> about.
>
> Thanks,
> Chris
>