Re: [Perc] Benjamin Kaduk's Discuss on draft-ietf-perc-dtls-tunnel-09: (with DISCUSS and COMMENT)

Cullen Jennings <fluffy@iii.ca> Tue, 07 September 2021 20:57 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: perc@ietfa.amsl.com
Delivered-To: perc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07B153A1754; Tue, 7 Sep 2021 13:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 mL9YRuXtVLzb; Tue, 7 Sep 2021 13:57:36 -0700 (PDT)
Received: from smtp71.iad3b.emailsrvr.com (smtp71.iad3b.emailsrvr.com [146.20.161.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3D9C3A1751; Tue, 7 Sep 2021 13:57:35 -0700 (PDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp9.relay.iad3b.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 7067B200E8; Tue, 7 Sep 2021 16:57:32 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_D12AC4C4-4C2E-475F-9F05-58F5099568BB"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CAL0qLwb12yh6p6cK21bD8PWM7F_co8NYyy+oqsmg80VT6CZZwg@mail.gmail.com>
Date: Tue, 07 Sep 2021 14:57:31 -0600
Cc: Paul Jones <paulej@packetizer.com>, Suhas Nandakumar <suhasietf@gmail.com>, perc@ietf.org, perc-chairs@ietf.org, draft-ietf-perc-dtls-tunnel@ietf.org, The IESG <iesg@ietf.org>
Message-Id: <235FA332-7A68-4189-B74E-52D7276AE8AD@iii.ca>
References: <162510321507.13724.12968550804927630403@ietfa.amsl.com> <emf2164c70-5bda-4e41-aa5e-08eb27232cef@sydney> <CAL0qLwb12yh6p6cK21bD8PWM7F_co8NYyy+oqsmg80VT6CZZwg@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, Benjamin Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-Classification-ID: 80fdbd06-8105-4208-9a42-590f5ef4a2d3-1-1
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/fcjBfnwDqM_q5toPGvAz7kf4y2Q>
Subject: Re: [Perc] Benjamin Kaduk's Discuss on draft-ietf-perc-dtls-tunnel-09: (with DISCUSS and COMMENT)
X-BeenThere: perc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Enhanced RTP Conferencing <perc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perc>, <mailto:perc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perc/>
List-Post: <mailto:perc@ietf.org>
List-Help: <mailto:perc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perc>, <mailto:perc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2021 20:57:41 -0000


> On Aug 20, 2021, at 10:39 PM, Murray S. Kucherawy <superuser@gmail.com> wrote:
> 
> On Thu, Aug 5, 2021 at 6:17 PM Paul E. Jones <paulej=40packetizer.com@dmarc.ietf.org <mailto:40packetizer.com@dmarc.ietf.org>> wrote:
> 
>> (2) I'll also mention here so that the IESG can talk about it during our
>> telechat (but with no intent to insist on a change): this document
>> specifies a versioned protocol and creates a registry. Are we happy
>> with the current Informational status, as opposed to Proposed Standard?
>> I do see that the topic was touched on in the shepherd writeup, but the
>> treatment there did not feel especially compelling to me.
> 
> Hopefully that got resolved.  I'll await instructions on any requested changes here.
> 
> I'm not aware of a resolution.  I never got a reply after my message of July 1, where I suggested some possible paths by the working group.
> 
> -MSK
> 

I’m having a hard time understanding the problem here. As far as I know there is no requirement for a document to be standards track to create an IANA registry - am I missing something? I was under the belief that a document does not even need to be part of the IETF stream for inclusion into IANA.  

I would rather see this document published than go back to WGLC.