Re: [eppext] Stephen Farrell's Discuss on draft-ietf-eppext-tmch-smd-04: (with DISCUSS and COMMENT)

Gustavo Lozano <gustavo.lozano@icann.org> Thu, 18 February 2016 19:01 UTC

Return-Path: <gustavo.lozano@icann.org>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBA001A0405; Thu, 18 Feb 2016 11:01:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level:
X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] 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 E7h0xrV_XfBz; Thu, 18 Feb 2016 11:01:20 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE2F81A002C; Thu, 18 Feb 2016 11:01:20 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Thu, 18 Feb 2016 11:01:18 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1130.005; Thu, 18 Feb 2016 11:01:18 -0800
From: Gustavo Lozano <gustavo.lozano@icann.org>
To: Barry Leiba <barryleiba@computer.org>
Thread-Topic: Stephen Farrell's Discuss on draft-ietf-eppext-tmch-smd-04: (with DISCUSS and COMMENT)
Thread-Index: AQHRan6/WIIEdQbNnUW9UsPRNxu5iw==
Date: Thu, 18 Feb 2016 19:01:18 +0000
Message-ID: <D2EB53EE.F510B%gustavo.lozano@icann.org>
References: <20160215191046.25962.24626.idtracker@ietfa.amsl.com> <CALaySJL=nkxm7Hy-=02uzhYT4+VtaNJrEbep9FO+KPzraR_BZg@mail.gmail.com>
In-Reply-To: <CALaySJL=nkxm7Hy-=02uzhYT4+VtaNJrEbep9FO+KPzraR_BZg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.1.160122
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.35.2]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3538638069_916877"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/fWvgZCH-lwPF1KRd8MmMYCupSeY>
Cc: "nkong@cnnic.cn" <nkong@cnnic.cn>, "draft-ietf-eppext-tmch-smd@ietf.org" <draft-ietf-eppext-tmch-smd@ietf.org>, "eppext-chairs@ietf.org" <eppext-chairs@ietf.org>, eppext <eppext@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
Subject: Re: [eppext] Stephen Farrell's Discuss on draft-ietf-eppext-tmch-smd-04: (with DISCUSS and COMMENT)
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2016 19:01:23 -0000

Thank you for the follow-up Barry,

I replied today to Stephen┬╣s comments, see
https://mailarchive.ietf.org/arch/msg/eppext/cNizylFVKdWXu20OKKlq5gIA1KM

Hopefully my response clarifies the intention of the reference to the
[ICANN-TMCH] document.

Regards,
Gustavo

On 2/18/16, 07:17, "barryleiba@gmail.com on behalf of Barry Leiba"
<barryleiba@gmail.com on behalf of barryleiba@computer.org>; wrote:

>Gustavo, we need some discussion here to resolve Stephen's issues
>(which other ADs are agreeing with), and also Ben's comments and any
>others that are out there.  Can you please respond soon?
>
>Barry
>
>On Mon, Feb 15, 2016 at 11:10 AM, Stephen Farrell
><stephen.farrell@cs.tcd.ie>; wrote:
>> Stephen Farrell has entered the following ballot position for
>> draft-ietf-eppext-tmch-smd-04: Discuss
>>
>> 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-eppext-tmch-smd/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>>
>> Section 7 points to [ICANN-TMCH] for signature validation policy
>> (I think, not quite sure). I did a quick scan (so I might have
>> missed it) of that document and did not find any mention of
>> security or signature validation, so what is an implementer
>> supposed to do, over and above just checking the cryptographic
>> correctness of the XMLDSIG? Note1: I'm not asking that all of
>> the details of how to construct a PKI for this functionality be
>> documented here, somewhere else is fine, but it doesn't seem to
>> be in [ICANN-TMCH] that I can see, so I don't know what I'd have
>> to implement, that'd get interop. Note2: I'm also not asking for
>> a US-DoD-scale super-huge PKI or RPKI to be specified here,
>> something simpler should work.
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>>
>> - Please see the secdir review [1] which raises a number of
>> significant points (including the DISCUSS above) and which
>> hasn't as far as I've seen gotten a response (apologies if I
>> missed that).
>>
>>    [1]
>> https://www.ietf.org/mail-archive/web/secdir/current/msg06248.html
>>
>> - "precudle" nice:-)
>>
>>