Re: [secdir] SECDIR review of draft-ietf-lisp-crypto-07

"Brian Weis (bew)" <> Mon, 26 September 2016 03:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A5AE912B064; Sun, 25 Sep 2016 20:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -16.838
X-Spam-Status: No, score=-16.838 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hilbgC7U0OgR; Sun, 25 Sep 2016 20:11:58 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9D7C31288B8; Sun, 25 Sep 2016 20:11:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=3829; q=dns/txt; s=iport; t=1474859518; x=1476069118; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=4LDDTJNm3MqY9ki7QBtdVjMa65uRHjrlcEJxka7Zf6k=; b=NeHnnt2dzl3p9MBV1cO9DYczeN/tZnNz2DBDA2bFGSfDeMym8t5gZzu5 Y7Nnxj75yJfi9nQ1JPz1lypJfCLNxd5tWtaGgxYYC5YPKob7PopPtnMdy 8jmZEtJvoJ3jA3gACx+0lMLMDOt2klJBIJKeIUH5LHpHDKu3CWAKls+po A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.30,397,1470700800"; d="scan'208";a="328096644"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 26 Sep 2016 03:11:57 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u8Q3BvYj002237 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 26 Sep 2016 03:11:57 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 25 Sep 2016 23:11:56 -0400
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Sun, 25 Sep 2016 23:11:56 -0400
From: "Brian Weis (bew)" <>
To: Chris Lonvick <>
Thread-Topic: SECDIR review of draft-ietf-lisp-crypto-07
Date: Mon, 26 Sep 2016 03:11:56 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>, "" <>, Dino Farinacci <>, "" <>
Subject: Re: [secdir] SECDIR review of draft-ietf-lisp-crypto-07
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Security Area Directorate <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 26 Sep 2016 03:12:00 -0000

Hi Chris, 

Thanks for the review. I’ve added one comment below.

> On Sep 25, 2016, at 6:27 PM, Chris Lonvick <> wrote:
> Hi Dino,
> On 9/25/16 4:37 PM, Dino Farinacci wrote:
>>>> I don't follow LISP so I'm not sure if there is an actual mechanism for a device receiving a map request packet to decline an offered cipher suite. If there is, I didn't see it explained in the
>> Yes, there is. If the Map-Reply this is returned contains no Security LCAF that means to the ITR that it either needs to go unencrypted encapsulating packets to the ETR or try another cipher text.
>>>> >>draft. You should address this in a future draft. This will be needed for when new cipher suites are
>> Understand the need. We intentionally wanted to support this.
>>>> >>added and a receiving device does not have the capability to handle the new cipher suite, or the case where an old cipher suite has been administratively disabled; like if it's been compromised and shouldn't be used. There are several ways to do this.
>> We have this in section x of the draft. Is it not sufficient?
>>    If an ITR, PITR, or RTR sends a Map-Request with the Security Type
>>    LCAF included and the ETR or RTR does not want to have encapsulated
>>    traffic encrypted, they will return a Map-Reply with no RLOC records
>>    encoded with the Security Type LCAF.  This signals to the ITR, PITR
>>    or RTR not to encrypt traffic (it cannot encrypt traffic anyways
>>    since no ETR public-key was returned).
> That text just says that if the cipher suite is declined then there will be no encryption. I was interpreting that to mean that the receiver just isn't going to accept any attempt at encryption. If it's just meant to be for that particular cipher suit then you'll need to add a line to that paragraph to say that the ITR, PITR, or RTR can attempt a different cipher suite if it is administratively configured to do so. However, that could get to be very inefficient if the ITR has to make 6 attempts before understanding that the ETR just isn't going to accept any encryption request - if it's so configured, or if it just doesn't support the feature whatsoever. So even if you allow the sender to make offer after offer, it would still be a good idea to have a way for the receiver to entirely decline encrypting packets from the sender.
> But, with all that being said, I'm figuring that we're getting outside the intent of your experimental specification. When you do get around to getting this onto a standards track, then you should make some decisions around how to convey capabilities between the sender and receiver so they can quickly and efficiently figure out what's going to work, or if it's just not, rather than making one offer after another. TLS and SSH have ways for a sender to offer a list from which the receiver can choose, if you're looking for examples. Another way is for the sender to proffer a version number which is associated with a select group of capabilities. From that, the receiver can make a choice, or efficiently decline all.

Thanks for the suggestions. In this effort we were intentionally avoiding the complexities and added security analysis requirements of a multiple round-trip method capabilities negotiation such as TLS. But maybe a capabilities declaration more along the lines of the version number you suggest might be appropriate.  I agree that at such time as the protocol was prepared for standards-track that this would be important to add.


> Best regards,
> Chris

Brian Weis
Security, CSG, Cisco Systems
Telephone: +1 408 526 4796