IETF Logo Mail Archive

Re: Alexey Melnikov's No Objection on draft-ietf-rtgwg-yang-key-chain-24: (with COMMENT)

"Acee Lindem (acee)" <acee@cisco.com> Wed, 03 May 2017 18:16 UTC

Return-Path: <acee@cisco.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 731D3126BF0; Wed, 3 May 2017 11:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 dnZU9PUJVkOA; Wed, 3 May 2017 11:16:24 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1B3D129B40; Wed, 3 May 2017 11:14:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2308; q=dns/txt; s=iport; t=1493835276; x=1495044876; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Ron/KhQ3RK01GF+UqkArGQJl3jUT0B2l9heafIhw1Zs=; b=RA72xx3X7bNft8/IB+jKTHSwRGpF0R+csdUnv7fMjRDHWHdUc6B/50Dh 6wb8UH7JkMX351yYBV+LkVS3f7FuDe56T5af+AABB//wRQB8UFA2Xho3x 5Wvs/P4gvSO9CNSpeXaa9aVOa9TeeoEIJSGi8aEha2gpT7/V+7dhal+uu k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AsAQDRHQpZ/49dJa1cGQEBAQEBAQEBAQEBBwEBAQEBg1VigQwHg2GKGKdAgg8hC4V4AhqEJj8YAQIBAQEBAQEBayiFFgIBAwEBIRE6CxACAQgODAImAgICJQsVEAIEAQ0FiiEOsSKCJopsAQEBAQEBAQEBAQEBAQEBAQEBAQEZBYELik2ENBIBHIMGgl8FiUCUHAGHGot5ggKFOYollDMBHzh/C28VRYUmgUp2AYYvgSGBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.38,284,1491264000"; d="scan'208";a="420731453"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 May 2017 18:14:15 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v43IEFVt021676 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 3 May 2017 18:14:15 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 3 May 2017 14:14:14 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Wed, 3 May 2017 14:14:14 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
CC: "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "draft-ietf-rtgwg-yang-key-chain@ietf.org" <draft-ietf-rtgwg-yang-key-chain@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: Alexey Melnikov's No Objection on draft-ietf-rtgwg-yang-key-chain-24: (with COMMENT)
Thread-Topic: Alexey Melnikov's No Objection on draft-ietf-rtgwg-yang-key-chain-24: (with COMMENT)
Thread-Index: AQHSxCUmTFYIG/K/pEGacNZogiEiVKHi6c6A
Date: Wed, 03 May 2017 18:14:14 +0000
Message-ID: <D52F94B4.AC97C%acee@cisco.com>
References: <149382668546.21423.308568120805096987.idtracker@ietfa.amsl.com>
In-Reply-To: <149382668546.21423.308568120805096987.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.197]
Content-Type: text/plain; charset="utf-8"
Content-ID: <AFACAAE8F12B04499D4C12069A4D5A2D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/31NGrO8f4a1MNow064qG1inquh4>
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: Wed, 03 May 2017 18:16:25 -0000

Hi Alexey, 

See below. 

On 5/3/17, 11:51 AM, "rtgwg on behalf of Alexey Melnikov"
<rtgwg-bounces@ietf.org on behalf of aamelnikov@fastmail.fm> wrote:

>Alexey Melnikov has entered the following ballot position for
>draft-ietf-rtgwg-yang-key-chain-24: No Objection
>
>When responding, please keep the subject line intact and reply to all
>email addresses included in the To and CC lines. (Feel free to cut this
>introductory paragraph, however.)
>
>
>Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>for more information about IESG DISCUSS and COMMENT positions.
>
>
>The document, along with other ballot positions, can be found here:
>https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-key-chain/
>
>
>
>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>Thank you for addressing my DISCUSS.
>
>Maybe it is just me, but it would have helped to say that "key string in
>ASCII" is a passphrase. I was not sure whether "key string" was a term
>used in Routing and/or YANG circles. The best place to clarify this is in
>Section 2   (Problem Statement)

Typically, authentication keys using for applications such as routing
protocols have been configured in ASCII or hexadecimal and still referred
to as keys. For example, refer to RFC 7474. I believe the term
“passphrase” would be wrong as this seems to imply something like an SSH
paraphrase. 

Thanks,
Acee 
>
>
>_______________________________________________
>rtgwg mailing list
>rtgwg@ietf.org
>https://www.ietf.org/mailman/listinfo/rtgwg

v2.23.0 | Report a Bug | By Email