Re: [Secret] Éric Vyncke's No Objection on charter-ietf-tigress-00-01: (with COMMENT)

Qin Wu <bill.wu@huawei.com> Thu, 30 June 2022 10:09 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: secret@ietfa.amsl.com
Delivered-To: secret@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8580C14CF10 for <secret@ietfa.amsl.com>; Thu, 30 Jun 2022 03:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J2zXrR30G0wg for <secret@ietfa.amsl.com>; Thu, 30 Jun 2022 03:09:24 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C65BC14F606 for <secret@ietf.org>; Thu, 30 Jun 2022 03:09:23 -0700 (PDT)
Received: from fraeml739-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4LYYsD1WZhz67n3l for <secret@ietf.org>; Thu, 30 Jun 2022 18:06:56 +0800 (CST)
Received: from canpemm500007.china.huawei.com (7.192.104.62) by fraeml739-chm.china.huawei.com (10.206.15.220) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 30 Jun 2022 12:09:18 +0200
Received: from canpemm500005.china.huawei.com (7.192.104.229) by canpemm500007.china.huawei.com (7.192.104.62) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 30 Jun 2022 18:09:17 +0800
Received: from canpemm500005.china.huawei.com ([7.192.104.229]) by canpemm500005.china.huawei.com ([7.192.104.229]) with mapi id 15.01.2375.024; Thu, 30 Jun 2022 18:09:17 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "secret@ietf.org" <secret@ietf.org>
CC: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, Roman Danyliw <rdd@cert.org>
Thread-Topic: Re: [Secret] Éric Vyncke's No Objection on charter-ietf-tigress-00-01: (with COMMENT)
Thread-Index: AdiMZ2gebfr/CBpLTbKYH6dUJwcELw==
Date: Thu, 30 Jun 2022 10:09:17 +0000
Message-ID: <fea08e5a56534432be6b314595af03ea@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.100.16]
Content-Type: multipart/alternative; boundary="_000_fea08e5a56534432be6b314595af03eahuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/secret/8whJFK47YwYk5B3APifk1zvDC7s>
Subject: Re: [Secret] Éric Vyncke's No Objection on charter-ietf-tigress-00-01: (with COMMENT)
X-BeenThere: secret@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Secure Credential Transfer <secret.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secret>, <mailto:secret-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secret/>
List-Post: <mailto:secret@ietf.org>
List-Help: <mailto:secret-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secret>, <mailto:secret-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2022 10:09:26 -0000

Agree with Eric to use 3rd person, fixing this is easy, here is the proposed change:

OLD TEXT:

“

There are many situations in which it is desirable to transfer a copy of a

digital credential to another person. For example, you may want to provide

access to your vehicle to a friend or a family member. You may also want to

provide access to your home to your cat sitter. Or, you may want to transfer a

copy of a hotel key to your spouse. Today, no such standardized method exists

in a cross-platform, credential type-agnostic capacity.

”

NEW TEXT:

“

There are many situations in which it is desirable to transfer a copy of a

digital credential to another person. For example, Private car owners may want to provide

access to their vehicle to a friend or a family member. Private Home owners may want to

provide access to their home to their cat sitter. Or, Rental hotel room owners may want to transfer a

copy of a hotel key to their spouse. Today, no such standardized method exists

in a cross-platform, credential type-agnostic capacity.

”



Also I want to make sure I understand the meaning of ‘cross-platform’ word? Two understandings we can have:

1.        OS independent: Sender uses its mobile device with OS A to send credential, receiver uses its mobile device with OS B to receive credential from relay server.

2.        Platform independent: Separate credential provision from credential transfer, relay server is deployed in one platform, while credential authority is deployed in another platform.

I am wondering which one is correct?



-Qin

Re: [Secret] Éric Vyncke's No Objection on charter-ietf-tigress-00-01: (with COMMENT)

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Wed, 29 June 2022 21:13 UTCShow header<https://mailarchive.ietf.org/arch/msg/secret/0WWCaN8O4YYyAi_11w_boJFJcmw/>

Hello Roman,



Thank you for your reply and actions.



I agree that the 2nd person use in the charter is a matter of style, it is not mine but I do not mind at all as long as the secretive feline agrees with this wording.



Regards



-éric





On 29/06/2022, 19:47, "Roman Danyliw" <rdd@cert.org><mailto:&lt;rdd@cert.org&gt;> wrote:



    Hi Éric!



    Thank you for the feedback.  It has been folded into 00-02.  More inline ...



    > -----Original Message-----

    > From: iesg <iesg-bounces@ietf.org><mailto:&lt;iesg-bounces@ietf.org&gt;> On Behalf Of Éric Vyncke via Datatracker

    > Sent: Tuesday, June 28, 2022 2:07 AM

    > To: The IESG <iesg@ietf.org><mailto:&lt;iesg@ietf.org&gt;>

    > Cc: tigress-chairs@ietf.org<mailto:tigress-chairs@ietf.org>; secret@ietf.org<mailto:secret@ietf.org>

    > Subject: Éric Vyncke's No Objection on charter-ietf-tigress-00-01: (with

    > COMMENT)

    >

    > Éric Vyncke has entered the following ballot position for

    > charter-ietf-tigress-00-01: 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.)

    >

    >

    >

    > The document, along with other ballot positions, can be found here:

    > https://datatracker.ietf.org/doc/charter-ietf-tigress/

    >

    >

    >

    > ----------------------------------------------------------------------

    > COMMENT:

    > ----------------------------------------------------------------------

    >

    > Interesting pieces of work that will be quite useful. Here are some quick

    > comments:

    >

    > The 1st paragraph is written using "you", I would prefer to read it as the 3rd

    > person.



    I can see that, but I think this might be a matter of style.  Let's see what the community review returns.



    > 2nd paragraph, in "Note that neither private keys", the "note that" looks

    > strange in a charter, suggest to replace it by "Note: neither private keys".



    Changed.



    > The MD format (bullet list) is broken in a couple of places.



    I did my best by inserting too many CR to get bullets to break across lines.  I'm having issues with MD rendering the text to be bullets without line breaks.



    > It is unclear what "sensitive details of the share" are.

    >

    > The charter has privacy & security "goals" and "considerations", while I am not

    > a native English speaker, I wonder those 2 words are synonyms. Should

    > 'requirements' be used ?



    In this case, I would consider "goals", "considerations" and "requirements" synonyms.  However, there is no reason to use all three.  The text now only uses "goals"



    Roman