Re: [homenet] Comments requested for draft CER-ID

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 28 October 2014 19:37 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8AAA1A6F99 for <homenet@ietfa.amsl.com>; Tue, 28 Oct 2014 12:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] 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 adjc509jWu46 for <homenet@ietfa.amsl.com>; Tue, 28 Oct 2014 12:37:13 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BA541AC43A for <homenet@ietf.org>; Tue, 28 Oct 2014 12:37:13 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id CC9A9203AA; Tue, 28 Oct 2014 15:38:27 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 1A3C363A84; Tue, 28 Oct 2014 15:37:12 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 02E4A63A21; Tue, 28 Oct 2014 15:37:12 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Michael Kloberdans <M.Kloberdans@cablelabs.com>
In-Reply-To: <D073AA38.D326%m.kloberdans@cablelabs.com>
References: <D0739ED2.D31D%m.kloberdans@cablelabs.com> <A06B0EA0-5817-4584-9010-776FC1CE1C90@iki.fi> <D073AA38.D326%m.kloberdans@cablelabs.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Tue, 28 Oct 2014 15:37:11 -0400
Message-ID: <32647.1414525031@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/987eKlSwbChqTwfyBTbsjInfqt4
Cc: "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Comments requested for draft CER-ID
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Oct 2014 19:37:17 -0000

Michael Kloberdans <M.Kloberdans@cablelabs.com> wrote:
    > All home routers should know their role; CER or IR.  The status of CER

80% of the innovation of the Homenet working group is really to find a way to
avoid having to *tell* the routers this role.  Yes, they wind up deriving it,
and I agree that it's useful for the routers to emit their conclusion in
the form of CER-ID.

> The status of CER places the burden of providing the firewall and NAPT as
> it was determined to be the edge router.  The interior routers need to
> understand their role and disable their firewall and NAPT abilities.  This
> is why the CER-ID is a numeric value (indicating CER status) or a double
> colon (indicating IR status).

I think that your document needs a 2-3 page explanation of reasons why
an router should believe the CER-ID it says.  It's a very clear attack vector
on a home router if you can get it to turn off it's firewall.

I don't think your security considerations is adequate; you likely did not
understand Markus' reference to the "evil bit", which a Steve Bellovin April
1 "RFC": rfc3514.txt.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-