IETF Logo Mail Archive

Re: Kathleen Moriarty's Discuss on draft-ietf-rtgwg-yang-key-chain-20: (with DISCUSS and COMMENT)

Alia Atlas <akatlas@gmail.com> Thu, 27 April 2017 14:21 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A38461294EE; Thu, 27 Apr 2017 07:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=0.001] autolearn=ham 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 DI9AzLD84_ur; Thu, 27 Apr 2017 07:21:19 -0700 (PDT)
Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (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 56E2C126CC7; Thu, 27 Apr 2017 07:21:19 -0700 (PDT)
Received: by mail-wr0-x234.google.com with SMTP id l50so18086097wrc.3; Thu, 27 Apr 2017 07:21:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2D27RQoOLz/E5PtYK8GmdZfqsUbWkoW0OJBZtOogBgI=; b=VHCuvTN+T7Zkr9kSYpeFN7Qnc0g+jTdrsrrEfA0ZeEhCBIACcZ7jmikdW0VyG5y504 o5ob1qI8rdgzR2dFusY/+uS0rSgfJqUZ9ms2J2OalXsOGVt9K0Es9tt8AbXwGllsjqeR Vld0IDsntlna0ONGMz4dJajST3Y1pwJ+a9gmx73yH3Yo/EKq4FpCbbNKTBA3n7D5438X 1BIAiBYfauC3goEnwtBIgchqOF+DkSh8idBm97TxewKLLLNtH3SprLeKlMWVajeyg1ux jlpcZNEQlgr7W7WIs+sId+ZqAHLOguFqOQ2ugsP4KMyII/avEdYcD9Y2n8qDrVTsxDtV hTng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2D27RQoOLz/E5PtYK8GmdZfqsUbWkoW0OJBZtOogBgI=; b=NjM1hM7COg3M/qu5UTSHEjpjs/+BQPC+gQSKroDEFD1dKjeBiBMwbPLckmzvF9G2zn 9ealYUzLZrDJjcNOda30N91LugJh6VmjomWi1DrHzpkqjyqIHG8Qed56sXXEsK2AUs0r 8KIwdeqAWIkTp7cptU7hr4Mp0iWh1BUT75ez31Q7kevTC6EXhHsnhw+U2fCXeCApPHrA PMtEVTdRvdVg0ZcGwmZEAWLMU3amNyqQQDdmAI3a3I6eMHWZLcz3NDo1mlMBljP8A7/h j9Wh54BNb327a8BGwD1AvQzBuEhXCDiQuVq+ER8cOT8xaqPtrU1EUKy0V4MuywGgkdiB oGUg==
X-Gm-Message-State: AN3rC/5FEdr5DVU4gKV4+DWY4P8y8h0wOmSogkLVDXa16g2muBzhvV3r G/xSOhhbAosT4c+yyAHyZFm3dL8wrA==
X-Received: by 10.223.148.5 with SMTP id 5mr847674wrq.44.1493302877658; Thu, 27 Apr 2017 07:21:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.135.120 with HTTP; Thu, 27 Apr 2017 07:21:16 -0700 (PDT)
In-Reply-To: <CABcZeBNQ=kwZZf6gUa_r1hJEscn+T11=mu3P1ACjjggMhkivHA@mail.gmail.com>
References: <149322447211.30122.5870367500760951821.idtracker@ietfa.amsl.com> <f366eb05-b82c-123e-d0ca-8701fe16a469@nostrum.com> <CAHbuEH5vDjZ5tSt=314Dquju7N26XSOqQPNjV=jO6D8Xn7QVdQ@mail.gmail.com> <89d1c702-7830-1f5a-1176-0b894e2d99e9@nostrum.com> <CAHbuEH5OX-GiwF7zqWmks5k6yLj5SXvXwYVFjCChrsa_ckokwQ@mail.gmail.com> <f6ac64b0-1e50-b02f-7043-8cae2cd56020@nostrum.com> <CAHbuEH7B=bzknZnfF_qsE435peOOd8XYjd=YKREeXw0RW18aGA@mail.gmail.com> <0c744357-0d94-62a8-c16b-81a02ef5db45@nostrum.com> <CAG4d1reMAu0YmTfPnStYFx1DotDpwnuGP3BM8ks5-YA1XxrKtA@mail.gmail.com> <d4fa3596-8ff5-5d31-41c3-10e189d553b0@nostrum.com> <CAG4d1recAczYUczXSw9w8=RT6ijE2fkc1FoRVF5_s-g1EaDe=w@mail.gmail.com> <CABcZeBNQ=kwZZf6gUa_r1hJEscn+T11=mu3P1ACjjggMhkivHA@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Thu, 27 Apr 2017 10:21:16 -0400
Message-ID: <CAG4d1rfOQBVUcnrjG7C=gmTdg3PZrJkzLcujW-D8GHtebDOfKQ@mail.gmail.com>
Subject: Re: Kathleen Moriarty's Discuss on draft-ietf-rtgwg-yang-key-chain-20: (with DISCUSS and COMMENT)
To: Eric Rescorla <ekr@rtfm.com>
Cc: Adam Roach <adam@nostrum.com>, "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, draft-ietf-rtgwg-yang-key-chain@ietf.org, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, The IESG <iesg@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0d22ee90a535054e26abac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/ujwAORTrIfOZ3Lme7We5d-AlA9o>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 14:21:20 -0000

On Thu, Apr 27, 2017 at 10:17 AM, Eric Rescorla <ekr@rtfm.com> wrote:

>
>
> On Thu, Apr 27, 2017 at 7:15 AM, Alia Atlas <akatlas@gmail.com> wrote:
>
>> On Thu, Apr 27, 2017 at 10:05 AM, Adam Roach <adam@nostrum.com> wrote:
>>
>>> On 4/26/17 23:02, Alia Atlas wrote:
>>>
>>>> First, the YANG model is primarily for information in motion - either
>>>> for configuration to the device
>>>> or to read from the device.   It is much less likely to represent the
>>>> data structure and storage in the device.
>>>> I believe that this draft's context is strictly for information in
>>>> motion.
>>>>
>>>
>>>
>>> Thanks; I understand all that. I'm trying to focus on the final
>>> paragraph of section 5, though, which appears to be an exception to what
>>> you say above.
>>
>>
>> I don't understand why - IMHO, that paragraph is simply saying  - this
>> model passes keys around (in motion).  Of course, a system shouldn't store
>> such keys unencrypted.  From what Acee says, this "motherhood and apple
>> pie" additional advice was added due to secdir review.
>>
>
> I thought Adam's point was that storing keys encrypted with a key that's
> adjacent to them was not useful.
>

This is not at all in scope for this document.  It isn't giving
implementation-specific advice on how to manage and store keys.
It is providing a model to configure and read keys.

Alia



> -Ekr
>
>
>>
>> Regards,
>> Alia
>>
>>
>>
>>> /a
>>>
>>>
>>
>

v2.23.0 | Report a Bug | By Email