IETF Logo Mail Archive

Re: [regext] draft-ietf-regext-unhandled-namespaces and draft-ietf-regext-secure-authinfo-transfer Document Track

"Gould, James" <jgould@verisign.com> Wed, 16 September 2020 16:43 UTC

Return-Path: <jgould@verisign.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19E863A0F68 for <regext@ietfa.amsl.com>; Wed, 16 Sep 2020 09:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.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 8fmjHUqe0M9K for <regext@ietfa.amsl.com>; Wed, 16 Sep 2020 09:43:38 -0700 (PDT)
Received: from mail3.verisign.com (mail3.verisign.com [72.13.63.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 773CF3A12D1 for <regext@ietf.org>; Wed, 16 Sep 2020 09:43:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=4098; q=dns/txt; s=VRSN; t=1600274588; h=from:to:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version:subject; bh=PfGct2thA9S5Lo7fiTkRDsjTeL1egUd3vpobXKt0zd0=; b=cyiD6z12c/2bMcLBAx2gDHT9XYjHqdq5rgalrZT21lt0W1OrDa+/hjYz c0KIN0sn4hrCM6MEk1r/w2upG7EXJwwoSmXk4/LUmRRV+7VjzV9Wn3o6d 2KjsCQNPR2UQV23tDZlnO/qfM3m3cW44MlTu6HqRoXmsISXEfbbNbTpr0 v94KptqCtUGkWb3NsqZAQXYrZGlcH0Xfl9cIv5fQgPTIqszBXMl4NHNVs hGc0wK8BQvA1wUSHgibpMWEz1ChBqojD79nP2BryFQprGldtDLrGV81+d 0SfcfbYb4GY2tXm2tNOf67f6VtitAXugrJ4OyqS1iSky8OoYXvVK2quTs w==;
IronPort-SDR: jJ70VfNn00icaUYGRkv7oVfbc2sZ5O0zDa9cW+IWALDCF4PhYe+SmtmPDcZDyBcO5o9Gg9wcIJ EtTzZqbBTvraAeKPdIdZBUVg+n+AvmRJdvOVTJ34vQtN484HAdn1qKtulTDzew4mvNG0Hs/e3Z L7HU14FqHtTflVVYykjg4kGr9tkw5KrYhNuXY7cnNqrNNwvI8Hm1kyDdck48GoaDNBwR3Sd41E NK7CbWWIiB9aAa+FL1cGInw7P7oU2FGgmyQQkuPltRwUAa/R4XKjcjfK915rs641ddT5DTA/pE OpM=
X-IronPort-AV: E=Sophos;i="5.76,433,1592870400"; d="scan'208";a="3025727"
IronPort-PHdr: 9a23:2Si1NhdTeowz1wVWZR+oIIdglGMj4u6mDksu8pMizoh2WeGdxc24YRON2/xhgRfzUJnB7Loc0qyK6v+mATZLsMrJ8ChbNsAVCVld0YRetjdjKfbNMVf8Iv/uYn5yN+V5f3ghwUuGN1NIEt31fVzYry76xzcTHhLiKVg9fbytScbdgMutyu+95YDYbRlWizqhe7NyKwi9oRnMusUMjoZuN6Q8xgHVrndWdOhbwWxlLk+Xkxrg+8u85pFu/zlRtv4768JMTaD2dLkkQLJFCzgrL3o779DxuxnZSguP6HocUmEInRdNHgPI8hL0UIrvvyXjruZy1zWUMsPwTbAvRDSt9LxrRwPyiCcGLDE27mfagdFtga1BoRKhoxt/w5PIYIyQKfFzcL/Rcc8cSGFcWMtaSi5PDZ6mb4YXD+QPI/tWr5XzqVUNoxuxBwejBOLzxTFHiXD7xrE63P8kEQ3awAAtBdADvXLJp9v1LqcSVuW1wbHGwTvCaPNWxDP955XQfhs8pf+DR7dwftTKyUUhCgjIiVeQqYPiPzOI0uQCrnOW7/R+WuK1im4nsABxojepxss2lobJgYcVx0nC+C5kz4k7Oce2R1RnYd64DpRQrSeaOpN0T84tXmxkpjo3xLIHtJO7fyUHzJspywPRZfGIc4WE/hzuWPueLzp3mX9od6yzihms/EW+1+DxVse63lZWoiZblNTHq34D1xvW6sedS/t9+F+s2SiR2ADJ6+FEOkE0laXdK54gxL4/ioAfvljEHi/zgEn5kK6Wdl449eiv8ejofrLmppqEO491lA7+Lqoulta4AeQiPQgDWXWQ9+ek1LD74EH1XK9GguA0n6TXqpzWOMQWq6CjDwJa1osv8wuzAyu83NgFn3QLMEhJdA+IgoXqIV3CPfP1APGiiFq2ijhr3erJPrj5D5XIKXjMjanucK5m605Z1Aoz1ddf549ICr0ZIPL8REvxtNvAAxIkLwK62/vrB9Vl2I0RWG2DHrGVPLnMsVCU4eIvOfGMaJUPtzngMfQl+eTujWQ/mVMHYaap2p4XZGi5HvRgPUqZfWLhjsodHWsQowYzTuLnhEefXTNTaXu+Ra0x6zUjBIKjF4jDR4StgLKb3Ce8G51bfmJGCl+LEXf1c4WLRuwBaDyMLc97kzwETrmhS4An1R20qAD6zL9nIvLO+iIErZLjyMR15+rLmBEp9Tx0CMCd02WTQGFyhWwHWSM53KNnrEFy1luDz7Z3g+ZZFdxI5vNJXQE6OYTAwOx9DtD/QR/OftKTR1a8XtqqGzAxQcwtw98AeUp9HM+ijh/b1SqwH7AVj6CLBIAz8q/Ex3jxIt1wxGvB1Kk9lVYmRNZAOnGhhqJl6wfTAIvJmV2Dl6m2baQcwDLN9GCbwGqUok5YXxB/UKrZXX0EZ0vZs8j55k3YQ7+pE7QnPVgJ9cnXYLBKbdntgFNMSfzgbYiGfW+rmnyxChDOzbSJRIbvcn8WmiTQFEZClBoctz7SLgg5AiOspWjTBz87SQrxblnt6uhxrjWwSUocwwSDdUYn1rep9FgSn/PKD7tZxrcstCA9ojN4F1H71NXTQZLUvw9JcKJAaNUx61AB3mXc4Ug1dIatIK1ymnYffhh5+UT02F8/Xp9NnsU6sFsrwRZ8b6WC3wUSWSmf2MW6FbrKLmW2tDKmbqPNkBmK0tmR56MDwOo1sVT4vQ6vUEEl9iM0gJFuz3KA68CSX0IpWpXrXxNv+g==
X-IPAS-Result: A2GpBABLP2Jf/zGZrQpcAx4BAQsSDECBRAuDGoE0CoQvkRImg3qXZz0LAQEBAQEBAQEBCAEfEAQBAQKESQIXgXwRJTcGDgIDAQELAQEBBQEBAQEBBgMBAQEChkUMgjciez0JPQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQUCCAdNB0cBHgEBAQEDIxE6FwQCAQgRBAEBAQICHwcCAgIwFQgIAgQBCQkUgxIBt1F2gTKKSoEOKoZahm2BQj6BOAwQgk0+glwEgV0XCiaCUDOCCyIEkAyDGqN0AweCZYhzkVQegwmBJ4hRk3iNcoN4DHmIbxKBXZUTAgQCBAUCFYFqgXxwFTsqAYI+CUcXAg2OVoM6ilZ0AgwmAwIGAQkBAQMJjU6BEQEB
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) by BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Wed, 16 Sep 2020 12:43:04 -0400
Received: from BRN1WNEX01.vcorp.ad.vrsn.com ([fe80::a89b:32d6:b967:337d]) by BRN1WNEX01.vcorp.ad.vrsn.com ([fe80::a89b:32d6:b967:337d%4]) with mapi id 15.01.1979.003; Wed, 16 Sep 2020 12:43:03 -0400
From: "Gould, James" <jgould@verisign.com>
To: "shollenbeck=40verisign.com@dmarc.ietf.org" <shollenbeck=40verisign.com@dmarc.ietf.org>, "pm@dotandco.com" <pm@dotandco.com>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: [regext] draft-ietf-regext-unhandled-namespaces and draft-ietf-regext-secure-authinfo-transfer Document Track
Thread-Index: AQHWheOcT0BFC5DLTU+UPg/snTMjhalg3yQAgArPnwD//9ZZgA==
Date: Wed, 16 Sep 2020 16:43:03 +0000
Message-ID: <903E1D6F-9AF4-4FFB-9154-70FFAB36F3C8@verisign.com>
References: <086BAABE-36EB-449A-86B1-E68012BEBC2C@verisign.com> <13ab636f-1630-4173-b359-ef182145520b@www.fastmail.com> <7fdcbf728f5f42c69988c2c146f4d85b@verisign.com>
In-Reply-To: <7fdcbf728f5f42c69988c2c146f4d85b@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.16.200509
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0FA26EDC25FACD4BB355539521646F25@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/FPxPrbkPklEouIoBv-jxOHLeRwM>
Subject: Re: [regext] draft-ietf-regext-unhandled-namespaces and draft-ietf-regext-secure-authinfo-transfer Document Track
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2020 16:43:40 -0000

Scott,

Thanks, I agree that there is supporting language in RFC 2026 to support draft-ietf-regext-unhandled-namespaces and draft-ietf-regext-secure-authinfo-transfer as standards track technical specifications.  We would change the track of both drafts from BCP to standards track.  Are there additional thoughts from the working group?    

Thanks,

-- 
 
JG



James Gould
Fellow Engineer
jgould@Verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com <http://verisigninc.com/>

On 9/16/20, 11:12 AM, "regext on behalf of Hollenbeck, Scott" <regext-bounces@ietf.org on behalf of shollenbeck=40verisign.com@dmarc.ietf.org> wrote:

    > -----Original Message-----
    > From: regext <regext-bounces@ietf.org> On Behalf Of Patrick Mevzek
    > Sent: Wednesday, September 9, 2020 2:06 PM
    > To: regext@ietf.org
    > Subject: [EXTERNAL] Re: [regext] draft-ietf-regext-unhandled-namespaces
    > and draft-ietf-regext-secure-authinfo-transfer Document Track
    > 
    > 
    > 
    > On Tue, Sep 8, 2020, at 08:26, Gould, James wrote:
    > >
    > > Both draft-ietf-regext-unhandled-namespaces and
    > > draft-ietf-regext-secure-authinfo-transfer are BCP drafts.  We have
    > > discussed the status of these drafts informally at prior REGEXT
    > > meetings and more formally at the IETF-108 REGEXT meeting.  Both
    > > drafts don’t define protocol, but define operational practices of
    > > using the existing EPP RFCs in a more secure or more compliant way.  I
    > > believe the drafts best match the purpose of a BCP.  Please respond on
    > > the list with your support for the BCP track or if you believe a
    > > different track should be used for one or both drafts.
    > 
    > I believe they both should be "Experimental" instead.
    > 
    > They are not long term widespread "current practices" at all.
    > 
    > As for "best" ones, I am still reserved.
    
    Patrick's reservations have merit. If we as a community can't agree that the documents describe best current practices, then it might not be appropriate for them to be published as BCPs. I'd feel more comfortable with publication on the standards track as technical specifications ("A Technical Specification is any description of a protocol, service, procedure, convention, or format") as described in Section 3.1 of RFC 2026.
    
    Scott
    _______________________________________________
    regext mailing list
    regext@ietf.org
    https://secure-web.cisco.com/1-5xcnRGPSR_FMxlp_u9DCtCkDAP63ET4arcK3x2U08H8dv4pIt0hJyhUEafMW4xCbmfjodXmDB2NeFwNE9cQLzXH-RTaht8knEDRnuu3S-muvpcYvTN6r7VL4l60rMi5I7uBtnsH7QjMy3LT6Lowp_ARN0wqKvRyDdUpc7JLyj-iv4ri64uM16Dsq-4sY6hSoaLEYlIVPEo2f484NABmZ2RqqcFyfaHkIZOKhe03_KGeprRN6ZE0jfY31KV9m-uUWsEL9NDd0NTA44QOSzp3o2wwG0iNzDtjFkBwcfkUdlA/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext

v2.29.0 | Report a Bug | By Email | System Status