From nobody Tue Sep 7 13:57:43 2021 Return-Path: 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 In-Reply-To: Date: Tue, 7 Sep 2021 14:57:31 -0600 Cc: Paul Jones , Suhas Nandakumar , perc@ietf.org, perc-chairs@ietf.org, draft-ietf-perc-dtls-tunnel@ietf.org, The IESG Message-Id: <235FA332-7A68-4189-B74E-52D7276AE8AD@iii.ca> References: <162510321507.13724.12968550804927630403@ietfa.amsl.com> To: "Murray S. Kucherawy" , Benjamin Kaduk X-Mailer: Apple Mail (2.3654.120.0.1.13) X-Classification-ID: 80fdbd06-8105-4208-9a42-590f5ef4a2d3-1-1 Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2021 20:57:41 -0000 --Apple-Mail=_D12AC4C4-4C2E-475F-9F05-58F5099568BB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Aug 20, 2021, at 10:39 PM, Murray S. Kucherawy = wrote: >=20 > On Thu, Aug 5, 2021 at 6:17 PM Paul E. Jones = > wrote: >=20 >> (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. >=20 > Hopefully that got resolved. I'll await instructions on any requested = changes here. >=20 > 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. >=20 > -MSK >=20 I=E2=80=99m 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. =20 I would rather see this document published than go back to WGLC.=20 =20= --Apple-Mail=_D12AC4C4-4C2E-475F-9F05-58F5099568BB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

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=3D40packetizer.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=E2=80=99m = 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. 



 
= --Apple-Mail=_D12AC4C4-4C2E-475F-9F05-58F5099568BB-- From nobody Wed Sep 22 22:30:09 2021 Return-Path: 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 6F4A33A20AB; Wed, 22 Sep 2021 22:29:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 4UH2DXNypwey; Wed, 22 Sep 2021 22:29:45 -0700 (PDT) Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 998843A20A9; Wed, 22 Sep 2021 22:29:45 -0700 (PDT) Received: by mail-vs1-xe2f.google.com with SMTP id y141so5358015vsy.5; Wed, 22 Sep 2021 22:29:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pTh6c+prQoRxuEMoxO1L9/jaodO9tMAv8qt+zFDQn/U=; b=EzSNxxN/SzNhXD108pVXOnRH1F89Y3icL8G5Ur82UW2g5PPcZTw2FNGh6rfT85JjwR XYfPaiUzPHBetm6xTyegKnguuigbLFech/eqOZ46acbBagblD2m7vbWiJxd4OBL7wGF3 xJeT631fUBVUhTIlMQrQPdmtcrkFRhm0bSph0tzys08yGqg7SPNJRd1Gbvyys+YLvkO/ d/Pg4se+zRqPoNIEexuT1vrd62Ni+tvyQpGImyPnEey0QGvFfHwnUqOD932Pel+fl5Qy EX9XXJzVFi0Js+PSxlGCZeVtVmW232jMTsy45enWmJkYgcvySykdJkuyP1Zyf6qCGgwO 3qhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pTh6c+prQoRxuEMoxO1L9/jaodO9tMAv8qt+zFDQn/U=; b=6xnkbVhhYk8JuqavekSgW18qidsAqq4jpASFKZQ13gbLo9PPplxDphCk8/X8OjJy94 jbStVrt6eM8dNdxxauojJlZl37IIJ3lEGrdKLTJd4oROKXKunjpOi/P147DqGssKPmXR FlMdoOZmA1taEdoFDk904a/xHiIb54CmwrcssCq2VjJ2qNj08KasdtR/vDmpveVpqe4i PcvDD8h7rVRrapgyCmXt/HWeUaqr62tRRSgoZvnHszD3+xdHG9osbXCDYSVSYckPxnFQ IlQC/QYcS7C5tHD2Rtj4vsKAKS+7OH0Yn77hrfO939cawY2HpjqFciLe2QDtmYITdZfJ geVg== X-Gm-Message-State: AOAM5339/BY79AiNSBsxM6WmQXBVunnTGibqr1FhI/forhJlz9+4z1TF dhrFOl3PNKA3OXmsnoM4XBaCiaxLxXFhUkMvmaY= X-Google-Smtp-Source: ABdhPJyEbgfid9W69ZgsGOmDHEEj9S09cvjcnPoucujMc3IQxTt5bv0xCM/4UOdGjwZ0Y9qDJsnGHTByjkSrrrtHvjw= X-Received: by 2002:a67:c989:: with SMTP id y9mr2852506vsk.12.1632374984501; Wed, 22 Sep 2021 22:29:44 -0700 (PDT) MIME-Version: 1.0 References: <162510321507.13724.12968550804927630403@ietfa.amsl.com> <235FA332-7A68-4189-B74E-52D7276AE8AD@iii.ca> In-Reply-To: <235FA332-7A68-4189-B74E-52D7276AE8AD@iii.ca> From: "Murray S. Kucherawy" Date: Wed, 22 Sep 2021 22:29:33 -0700 Message-ID: To: Cullen Jennings Cc: Benjamin Kaduk , Paul Jones , Suhas Nandakumar , perc@ietf.org, perc-chairs@ietf.org, draft-ietf-perc-dtls-tunnel@ietf.org, The IESG Content-Type: multipart/alternative; boundary="000000000000176c0505cca2eb5b" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2021 05:29:52 -0000 --000000000000176c0505cca2eb5b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Sep 7, 2021 at 1:57 PM Cullen Jennings wrote: > On Thu, Aug 5, 2021 at 6:17 PM Paul E. Jones 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=E2=80=99m 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. > I'll follow up with Ben and the others during the next IESG telechat (in about nine hours). In any event, it looks like Paul needs to post a new version before this can go forward. -MSK --000000000000176c0505cca2eb5b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Sep 7, 2021 at 1:57 PM Cullen Jen= nings <fluffy@iii.ca> wrote:
=
On Thu, Aug 5, 2021 at 6:= 17 PM Paul E. Jones <paulej=3D40packetizer.com@dmarc.ietf.org> wrote:

(2) I'll also m= ention 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 th= e
treatment there did not feel especially compelling to me.

Hopefully that got r= esolved.=C2=A0 I'll await instructions on any requested changes here.

I'm not aware o= f a resolution.=C2=A0 I never got a reply after my message of July 1, where= I suggested some possible paths by the working group.

=
-MSK


I=E2=80=99= 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 r= egistry - am I missing something? I was under the belief that a document do= es not even need to be part of the IETF stream for inclusion into IANA. =C2= =A0

I would rather see this document published tha= n go back to WGLC.

I'l= l follow up with Ben and the others during the next IESG telechat (in about= nine hours).

In any event, it looks like Paul needs to post a new = version before this can go forward.

-MSK
=
--000000000000176c0505cca2eb5b-- From nobody Wed Sep 22 23:57:09 2021 Return-Path: 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 948D53A23DC; Wed, 22 Sep 2021 23:56:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 zxhPLSuR0ixi; Wed, 22 Sep 2021 23:56:39 -0700 (PDT) Received: from mail-vk1-xa33.google.com (mail-vk1-xa33.google.com [IPv6:2607:f8b0:4864:20::a33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9DCA3A23DA; Wed, 22 Sep 2021 23:56:39 -0700 (PDT) Received: by mail-vk1-xa33.google.com with SMTP id h132so2177723vke.8; Wed, 22 Sep 2021 23:56:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=deg2MHiZNqT9TQ6x7wt3fQh0qlpFwzIN2uJZF6PxgBk=; b=Y2RT5uOfLT2ato3yx97gIc+3eP+9bJgqO9r4rWYUfFjp42HLapmpiaR9f8NLFVtUYK wrzmk9bPQEBzwo/zrrCXDU/cMuFYIfLSv3lHJ6ef5rI0wFi+V3z+lZmmyjAY6KdoShCx 2WxJFc3lFGTCvql7aVaobSM5cg5AmoMIuyqRdWaOeDDIGHksFjrk5zWUeb7/21l5gZIR ggOcl/taULM8nGbvJLLl769SxO7ofzbBmdtcJSaIlsp+w03/IzHqO5yeqqG2eX9fWBjt L7b3Daf/8SFCXro/8kvC3YkenFhEJQVU7VMKSeflmHDCmM3JveBY9gc8W3tSkopDrgQL FqbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=deg2MHiZNqT9TQ6x7wt3fQh0qlpFwzIN2uJZF6PxgBk=; b=hwzay0B1yFE+L3ibFpMmPkUwH2JTAaLyJtF8sKn0kU3qJW8rN2pCFgtpSpvrAxmBHG bA48Iu5uggJEGRs7q84UDsZN09ZFJX5M4ncgP7Fdh7iX5pVLY5bpm2RTbgAy4eRfE84J +/xfO/QrnCAOZiaPg1S/r1+PgE3RUaaBjVSPw5AK5znJiA4KNyAxbWePrIvQUisg35Jd ZXbBzIXu0MttJyR/LnP62CBXsXQSc8QnSDaiAKR7EmqpZ1e2xnKYr1Z/ZaxxNplXGpGu YDo0h/9b1pLSmZzBQARi8QKdCvpu+8KoQ2mKNb0aiU/FSEyt4lf6rFSfB3KtW4n6dgAb jcEQ== X-Gm-Message-State: AOAM531P5WPI0hbXY1vJFsCzX1XCFu4LdGgkCaYV+UcEaN6dRpVgdpUa 4vp9W4GoYmrLYe11499D6a3vpixCviupcOmDJFE= X-Google-Smtp-Source: ABdhPJzKceY2OvLaeQuP7UzzBGTwlfVjYmJy6fY3V3AiZARQpnEM4y+T50nM0r16hn67nZOjJFw1sveWywbFgzALZXk= X-Received: by 2002:a1f:ad46:: with SMTP id w67mr2357593vke.16.1632380198466; Wed, 22 Sep 2021 23:56:38 -0700 (PDT) MIME-Version: 1.0 References: <162510321507.13724.12968550804927630403@ietfa.amsl.com> <235FA332-7A68-4189-B74E-52D7276AE8AD@iii.ca> In-Reply-To: From: "Murray S. Kucherawy" Date: Wed, 22 Sep 2021 23:56:27 -0700 Message-ID: To: Cullen Jennings Cc: Benjamin Kaduk , Paul Jones , Suhas Nandakumar , perc@ietf.org, perc-chairs@ietf.org, draft-ietf-perc-dtls-tunnel@ietf.org, The IESG Content-Type: multipart/alternative; boundary="000000000000de3a4805cca4217b" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2021 06:56:42 -0000 --000000000000de3a4805cca4217b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Sep 22, 2021 at 10:29 PM Murray S. Kucherawy wrote: > > I=E2=80=99m 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 a= n >> 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. >> > > I'll follow up with Ben and the others during the next IESG telechat (in > about nine hours) > I did this just now, and he reminds me that the IESG on review of this document found that it actually meets the bar for Proposed Standard, since it specifies a protocol with interoperable implementations, and we were wondering if the Working Group really wanted to stick with Informational. The IANA question was secondary. So I'm happy to send it through as-is, but I wanted to get that point covered first. Unfortunately I have had very little success getting anyone to answer my inquiries. -MSK --000000000000de3a4805cca4217b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


--000000000000de3a4805cca4217b-- From nobody Thu Sep 23 12:01:02 2021 Return-Path: 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 C39B63A1831; Thu, 23 Sep 2021 12:00:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetizer.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 f62OU4w87rAZ; Thu, 23 Sep 2021 12:00:28 -0700 (PDT) Received: from dublin.packetizer.com (dublin.packetizer.com [IPv6:2600:1f18:24d6:2e01:e842:9b2b:72a2:d2c6]) (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 994B93A1801; Thu, 23 Sep 2021 12:00:25 -0700 (PDT) Received: from authuser (localhost [127.0.0.1]) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1632423620; bh=wi004PuCR/lGnSsYGj2o+QFYjWXIP1jGUrLmUCOkw7s=; h=Date:From:To:CC:Subject:In-Reply-To:References; b=SfllQR65NJ+OcHji13JwZ1R3GRRBzYL2mEn96UYjmsqsBAa9Q9ByHgYNHf/q4+qLK xsJmWHqku9NLw54n/6Et59Y6hHUfr3eNmXhFjzofYor2ePexC0lrQY18gF4IsKq91H 6ZHcB672jdRdHsc/B8JzT3APQk54o/eL6C+Ty6lI= Date: Thu, 23 Sep 2021 15:00:18 -0400 From: "Paul E. Jones" To: "Murray S. Kucherawy" , Cullen Jennings CC: Benjamin Kaduk , Suhas Nandakumar , perc@ietf.org, perc-chairs@ietf.org, draft-ietf-perc-dtls-tunnel@ietf.org, The IESG In-Reply-To: References: <162510321507.13724.12968550804927630403@ietfa.amsl.com> <235FA332-7A68-4189-B74E-52D7276AE8AD@iii.ca> Message-ID: <516943E6-640C-463E-98C1-6C87487B5C53@packetizer.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----ZK3M5CEVZGI1INL94G3TQTW5BZXN2R Content-Transfer-Encoding: 7bit Autocrypt: addr=paulej@packetizer.com; keydata= mQQNBFHlwHIBIADPBuXxiC7IP3Acolod+D4BWYKBDGgyX90mexkDt6Wi6D2LJlpadGp99NgG9Oc4 m9QDEPPuhRHKvgexNAxAeILUZlOX6m/30n83VuwGNZagxjawN9/Kv4WrLlDI+HSZeKwfVf8GBus/ jB6c5WQtV6/L7LYCQLU08dWng8NlBi6dupyWC1rhtNWnPCqS4C3nINWJRx4grfIvkI5PbDMPca/B iluZxy0XntHuNWf51Gj4IIIAK2QNWQwDLaDnZ774Q1HfMTt4u4UwivsOt9Z49w92Q6FuN7/3sve7 DwrEVtp0xCKqaBQOX2354VVOTMh0bhHGLprQ1BL3QAWlyg/ZkTs+kopd3h+mJ0Mkg3Es66umcG8U YbH+edmZ7mHWqHuWmNieEycZgmah6kfrb7lUZeJnkkLfZ6SS3fhJIhJq3RwTKfvyF9LNvnZ7XXsO VSBKvVFPHWuDe3tbglTZCEYIcdFotgMcpZatdJF0ZPdLPGECc/XCZOgQpICGZ6b0dt/uJKOPC1OY RlFfIWc9bDgRCQY0MCqTsYiGevMNdQTlZHgTactm4h886bETFdbSoDniPls7LuI3cAr++iHmF56o hwh9Hl8KVzsv+uSL1mmrfE/X+lEaJnPUrQopByFQySE4D+hvOFLNh2iv7BHyXX9G0Dv9jDB6hW+6 1RYBf23GRZWSEVMyoYfbbU7Tg5JNrVRLU7nUMVbla2fGIKz9K3ejtCy/35QAjt7DIrVVe9k9J54r Z1yD8ZXfQXv869/q/mHGVzxdtgO+PcrIXJYck8R7jSDB2wIo3g5z+2P3Lt2gvB4w9UUSNZ4deE95 MNc6FvqqTMlBzoxzBf2E+SoUZKTl4i48XJhKI+Bk71NnMug2ER2NbyQIg6aH7l4t4t38mK6yt/cd 00f8UtKxp7z2EnqXJ+/kx0pq9zECp76oAPv9JlInntbcl89jRS4qMAMgZFEy6sYOMftfhVgDkci/ JR+2s4V65aUxcR6PLtXRHg3ZZ2F4hEBkBxJQt4LZ6lWzMXuWkCfjca032WOq/Zl+RMrs18dywVoh DXqSaYoSCzkfeCbzTE4cCuE8o9FUx7B/nS6g+h0wvrGDcLeGIwVWYO+Q0gf+vbLq2ZfykWjS5Fa3 ZKLdEOWaNas/8UlW33lU3u9nj84dJgMcP/VAugd8N9QWJ9NKszL8689NmwQnzoIU43+ucRd0WgCA WgXtV6MmG2WUpKN6y/ARqis6NvKTpl/t7SMznBxZGg2ZUC7pBpT/cq6vi18+tWP1ghRGJgJJ4t6v D64fBQTAaaN9MxU46OIlcWtjvf5zzL0pwebYOdInN/wA7YOOK3Q/wQsPaD5dvY+6H9yrCLMBwGyR l3TB/bsaYqtFABEBAAG0JVBhdWwgRS4gSm9uZXMgPHBhdWxlakBwYWNrZXRpemVyLmNvbT6JBDgE EwECACIFAlOH4kACGy8GCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEHropU4WcvKlpF4gAI34 iWlJY84nB8y12sqLldU0d9rSnk6euOYf7HIIJ8yHGCHVkQJUksjcwPOAr/zw4XjftSEv8JN3PDLp khvQ2snEIZ7UPFafUmbq3BQLPkN0Mpamx7br7vpLwpRMwbPyWYc4Z0+Ag4t6p/01troi++v3DLDN AjAov/Q526pL7qFkIJpadMcVcTEgr5XEsVVxw5TbGrqyDwam+aNIVcxDNxzOG4nFJ1bjUGAeoRcV Jnz0X0CQUFzxgMceyjuqI3Qyj5kp3gZkoibJyfZ6/6FFVV5dGAlHluL52H6KiUAkWPf0qbGo6ELu xsnSX9JPVUtr14B6HfZP8kWX740Hu2yBQTAxhsfhhsR4LNUxKcdNFSJ/Ozpo3i7fvek3CF+ash7l 25JAkI+1TH4kh7dYpndwTWwXDNqTMQR+I+JtsKgATpx/pBWaNK0zvWKuxjoM/CVn4NPWf9aqfdF3 wvTq5EMDarQ8Leou0LsKLKZsJHYYxFlMlD37/+q4UsIy5iPatNl8qm4YM4LykjvB+Ozsd3OZ3z+b uSdJ+6QwOnje21tPLhSI8dEIw8S+DKl+80I/2bEd3+wKptHcB0NU3OF9B3N1ClOp7wFIrgsQ0pTH A2pchxWyC9pngYhErJS6nZaQeWwrN7VH9RkS2SPPkAzf5N27ayky2rF8nDZrkO1OuXCaH9gyi2CQ fJEtbAPMXfAJo5Ls0trEMqQGDAW3/GxCo5NoX70bXjPd+NXBIYBaC9dc6Iyqei3xQJNsE2vtPEo3 glJaE3mFMpUOILqQkU8hjs3+J1rNkpkmaoenlvbDVUqM0TVGzHFJlPtLXR/DsDjgjk1uaS+xIlD0 exwLp3/Bgs4nXAQ1UYlPOLC/BokUPwAuSuUrCAYHfAzwsynIgI8j/EHeKgyjyuQ4f1uIlzy63rVd 8QVvGt6qV2hO0Bj4FzIMG9xG4KZ7cPziHmAh5tR0PbV35vJLww3HbmL6LzC5CaB2cYkLuOL4BuhU D+b20GiThhtYaPBQr49NBNViCB+RlhojKIS4Ou9+ngg2L4EWe6rY0yzR+BWPBvNtZNantozb49Pu IcYhfxzWFjK7Gt6zlQeUfsBGtdjR1p4emdH4c/VFdzj4bNPtKv56mkUrcFQpE1vym/PPYyvG3wBz UXF/d/W5NqojZmuQLO+GfMPo2sbT3V0LTELlfRfzOstA7SpdQgYpMoRQwErxIwn2lUVjt6DjXeaR oOkQgYAgQqHYLrWef6gYLy05xHEN6Ow6t7VDxuZOtjrJqQ3oyfcyR9EsyAET8CvSSaHABOaqWOiw E+TzU9/42ei0Qph08xL8BQMQVsnOJZLM8DMNWzWB3wVxCaVil+unNTnmw7mjClcPFuBjFyc= Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2021 19:00:43 -0000 ------ZK3M5CEVZGI1INL94G3TQTW5BZXN2R Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I have a draft prepared already=2E I'll publish it later today and wait for= further input=2E Paul -------- Original Message -------- From: "Murray S=2E Kucherawy" Sent: September 23, 2021 1:29:33 AM EDT To: Cullen Jennings Cc: Benjamin Kaduk , Paul Jones = , Suhas Nandakumar , perc@ietf=2Eorg, perc-chairs@ie= tf=2Eorg, draft-ietf-perc-dtls-tunnel@ietf=2Eorg, The IESG Subject: Re: [Perc] Benjamin Kaduk's Discuss on draft-ietf-perc-dtls-tunne= l-09: (with DISCUSS and COMMENT) On Tue, Sep 7, 2021 at 1:57 PM Cullen Jennings wrote: > On Thu, Aug 5, 2021 at 6:17 PM Paul E=2E Jones 40packetizer=2Ecom@dmarc=2Eietf=2Eorg> wrote: > > >> (2) I'll also mention here so that the IESG can talk about it during ou= r >> telechat (but with no intent to insist on a change): this document >> specifies a versioned protocol and creates a registry=2E 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=2E >> >> >> Hopefully that got resolved=2E I'll await instructions on any requeste= d >> changes here=2E >> > > I'm not aware of a resolution=2E I never got a reply after my message o= f > July 1, where I suggested some possible paths by the working group=2E > > -MSK > > > I=E2=80=99m having a hard time understanding the problem here=2E As far = as I know > there is no requirement for a document to be standards track to create a= n > 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=2E > > I would rather see this document published than go back to WGLC=2E > I'll follow up with Ben and the others during the next IESG telechat (in about nine hours)=2E In any event, it looks like Paul needs to post a new version before this can go forward=2E -MSK ------ZK3M5CEVZGI1INL94G3TQTW5BZXN2R Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable I have a draft prepared already=2E I'll publish it= later today and wait for further input=2E

Paul


From: "Murray S=2E Kucherawy" <superuser@gmail=2Ecom>
Sent: September 23, 2021 1:29:33 AM EDT
To: Cullen Jennings <fluffy@iii=2Eca>
Cc: Benjamin Kaduk <kaduk@mit=2Eedu>, Paul Jones <paulej@p= acketizer=2Ecom>, Suhas Nandakumar <suhasietf@gmail=2Ecom>, perc@i= etf=2Eorg, perc-chairs@ietf=2Eorg, draft-ietf-perc-dtls-tunnel@ietf=2Eorg, = The IESG <iesg@ietf=2Eorg>
Subject: Re: [Perc] Benjamin Kaduk's Discuss on draft-ietf-perc-dtl= s-tunnel-09: (with DISCUSS and COMMENT)

On Thu, Aug 5, 202= 1 at 6:17 PM Paul E=2E Jones <paulej=3D40packetizer=2Ecom@dmarc=2Eietf= =2Eorg> wrote:

(2) I'll also ment= ion 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=2E Are we happ= y
with the current Informational status, as opposed to Proposed Standar= d?
I do see that the topic was touched on in the shepherd writeup, but t= he
treatment there did not feel especially compelling to me=2E

Hopefully that go= t resolved=2E  I'll await instructions on any requested changes here= =2E

I'm not aware = of a resolution=2E  I never got a reply after my message of July 1, wh= ere I suggested some possible paths by the working group=2E

<= /div>
-MSK


I=E2= =80=99m having a hard time understanding the problem here=2E As far as I kn= ow there is no requirement for a document to be standards track to create a= n IANA registry - am I missing something? I was under the belief that a doc= ument does not even need to be part of the IETF stream for inclusion into I= ANA=2E  

I would rather see this document pub= lished than go back to WGLC=2E

=
I'll follow up with Ben and the others during the next IESG telechat (= in about nine hours)=2E

In any event, it looks like Paul needs to p= ost a new version before this can go forward=2E

-M= SK
------ZK3M5CEVZGI1INL94G3TQTW5BZXN2R-- From nobody Thu Sep 23 18:10:52 2021 Return-Path: X-Original-To: perc@ietf.org Delivered-To: perc@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ECF173A0E48; Thu, 23 Sep 2021 18:10:28 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: perc@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.38.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: perc@ietf.org Message-ID: <163244582886.7547.18223340215815386839@ietfa.amsl.com> Date: Thu, 23 Sep 2021 18:10:28 -0700 Archived-At: Subject: [Perc] I-D Action: draft-ietf-perc-dtls-tunnel-10.txt X-BeenThere: perc@ietf.org X-Mailman-Version: 2.1.29 List-Id: Privacy Enhanced RTP Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2021 01:10:29 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Privacy Enhanced RTP Conferencing WG of the IETF. Title : DTLS Tunnel between a Media Distributor and Key Distributor to Facilitate Key Exchange Authors : Paul E. Jones Paul M. Ellenbogen Nils H. Ohlmeier Filename : draft-ietf-perc-dtls-tunnel-10.txt Pages : 18 Date : 2021-09-23 Abstract: This document defines a protocol for tunneling DTLS traffic in multimedia conferences that enables a Media Distributor to facilitate key exchange between an endpoint in a conference and the Key Distributor. The protocol is designed to ensure that the keying material used for hop-by-hop encryption and authentication is accessible to the Media Distributor, while the keying material used for end-to-end encryption and authentication is inaccessible to the Media Distributor. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-perc-dtls-tunnel/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-perc-dtls-tunnel-10.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-perc-dtls-tunnel-10 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Sep 23 18:15:18 2021 Return-Path: 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 B34F43A0E84; Thu, 23 Sep 2021 18:15:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetizer.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 ImEoFdtLfzJ9; Thu, 23 Sep 2021 18:15:02 -0700 (PDT) Received: from dublin.packetizer.com (dublin.packetizer.com [IPv6:2600:1f18:24d6:2e01:e842:9b2b:72a2:d2c6]) (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 44A1A3A0E7D; Thu, 23 Sep 2021 18:15:01 -0700 (PDT) Received: from authuser (localhost [127.0.0.1]) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1632446098; bh=DfJf84gNDam1APfV1P/ajKLPByOEqWTjqKcodjHEV3Y=; h=From:To:Subject:Cc:Date:In-Reply-To:References:Reply-To; b=CWumVPq6Uex8F4UpaYiAVEWjjKRdO6Mhxjec2EQcUxVwsujv63uCx40gCO4pAdzNt LOrVp8E75fnCYFX1lz3txWo6QtZXmsAKMdk0gVTEqtVxw2Grm7/cjbi+JYPiy7N0f0 y8cmr9M3b4G7WkCZmmNtfNQGwrc+gvBel5ihxpvw= From: "Paul E. Jones" To: "Paul E. Jones" , "Murray S. Kucherawy" , "Cullen Jennings" Cc: "Benjamin Kaduk" , "Suhas Nandakumar" , perc@ietf.org, perc-chairs@ietf.org, draft-ietf-perc-dtls-tunnel@ietf.org, "The IESG" Date: Fri, 24 Sep 2021 01:14:54 +0000 Message-Id: In-Reply-To: <516943E6-640C-463E-98C1-6C87487B5C53@packetizer.com> References: <162510321507.13724.12968550804927630403@ietfa.amsl.com> <235FA332-7A68-4189-B74E-52D7276AE8AD@iii.ca> <516943E6-640C-463E-98C1-6C87487B5C53@packetizer.com> Reply-To: "Paul E. Jones" User-Agent: eM_Client/8.2.1473.0 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------=_MB89B89E0B-A684-4F3D-ACE5-EE401F6F31DB" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2021 01:15:08 -0000 --------=_MB89B89E0B-A684-4F3D-ACE5-EE401F6F31DB Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable I've published -10:=20 https://datatracker.ietf.org/doc/html/draft-ietf-perc-dtls-tunnel-10 ------ Original Message ------ From: "Paul E. Jones" To: "Murray S. Kucherawy" ; "Cullen Jennings"=20 Cc: "Benjamin Kaduk" ; "Suhas Nandakumar"=20 ; perc@ietf.org; perc-chairs@ietf.org;=20 draft-ietf-perc-dtls-tunnel@ietf.org; "The IESG" Sent: 9/23/2021 3:00:18 PM Subject: Re: [Perc] Benjamin Kaduk's Discuss on=20 draft-ietf-perc-dtls-tunnel-09: (with DISCUSS and COMMENT) >I have a draft prepared already. I'll publish it later today and wait=20 >for further input. > >Paul > >--------------------------------------------------------------------------= ------ >From: "Murray S. Kucherawy" >Sent: September 23, 2021 1:29:33 AM EDT >To: Cullen Jennings >Cc: Benjamin Kaduk , Paul Jones ,=20 >Suhas Nandakumar , perc@ietf.org,=20 >perc-chairs@ietf.org, draft-ietf-perc-dtls-tunnel@ietf.org, The IESG=20 > >Subject: Re: [Perc] Benjamin Kaduk's Discuss on=20 >draft-ietf-perc-dtls-tunnel-09: (with DISCUSS and COMMENT) > >On Tue, Sep 7, 2021 at 1:57 PM Cullen Jennings wrote: >>On Thu, Aug 5, 2021 at 6:17 PM Paul E. Jones=20 >> wrote: >>>> >>>>>(2) I'll also mention here so that the IESG can talk about it=20 >>>>>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=20 >>>>>Standard? >>>>>I do see that the topic was touched on in the shepherd writeup, but=20 >>>>>the >>>>>treatment there did not feel especially compelling to me. >>>> >>>>Hopefully that got resolved. I'll await instructions on any=20 >>>>requested changes here. >>> >>>I'm not aware of a resolution. I never got a reply after my message=20 >>>of July 1, where I suggested some possible paths by the working=20 >>>group. >>> >>>-MSK >>> >> >>I=E2=80=99m having a hard time understanding the problem here. As far as= I=20 >>know there is no requirement for a document to be standards track to=20 >>create an IANA registry - am I missing something? I was under the=20 >>belief that a document does not even need to be part of the IETF=20 >>stream for inclusion into IANA. >> >>I would rather see this document published than go back to WGLC. > >I'll follow up with Ben and the others during the next IESG telechat=20 >(in about nine hours). > >In any event, it looks like Paul needs to post a new version before=20 >this can go forward. > >-MSK --------=_MB89B89E0B-A684-4F3D-ACE5-EE401F6F31DB Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

------ Original Message ------
From: "Paul E. Jones" <pau= lej@packetizer.com>
To: "Murray S. Kucherawy" <s= uperuser@gmail.com>; "Cullen Jennings" <fluffy@iii.ca>
Sent: 9/23/2021 3:00:18 PM
Subject: Re: [Perc] Benjamin Kaduk's Discuss on draft-ietf-perc-dtls-t= unnel-09: (with DISCUSS and COMMENT)

I have a draft prepared already. I'll publish it later today and wait for f= urther input.

Paul


From: "Murray S. Kucherawy" <superuser@gmail.com>
Sent: September 23, 2021 1:29:33 AM EDT
To: Cullen Jennings <fluffy@iii.= ca>
Cc: Benjamin Kaduk <kaduk@mit.ed= u>, Paul Jones <paulej@p= acketizer.com>, Suhas Nandakumar <suhasietf@gmail.com>, perc@= ietf.org, perc-chairs@ietf.org<= /a>, draft-ietf-per= c-dtls-tunnel@ietf.org, The IESG <i= esg@ietf.org>
Subject: Re: [Perc] Benjamin Kaduk's Discuss on draft-ietf-perc-dtls= -tunnel-09: (with DISCUSS and COMMENT)

On Tue, Sep 7, 2021 at 1:57 PM Cullen Jen= nings <fluffy@iii.ca> wrote:
On Thu, Aug 5, 2021 at = 6:17 PM Paul E. Jones <paulej=3D40packetizer.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 th= e
treatment there did not feel especially compelling to me.

Hopefully that got = resolved.=C2=A0 I'll await instructions on any requested changes here.

I'm not aware of a= resolution.=C2=A0 I never got a reply after my message of July 1, where I s= uggested some possible paths by the working group.

-MSK


I=E2=80= =99m having a hard time understanding the problem here. As far as I know th= ere is no requirement for a document to be standards track to create an IAN= A 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. = =C2=A0

I would rather see this document publish= ed than go back to WGLC.

I'll follow up with Ben and the others during the next IESG telechat (in = about nine hours).

In any event, it looks like Paul needs to p= ost a new version before this can go forward.

-M= SK
--------=_MB89B89E0B-A684-4F3D-ACE5-EE401F6F31DB-- From nobody Mon Sep 27 21:05:26 2021 Return-Path: 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 92B243A1A71; Mon, 27 Sep 2021 21:05:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 iVI0_v6FWKGQ; Mon, 27 Sep 2021 21:05:04 -0700 (PDT) Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 479AB3A1A2F; Mon, 27 Sep 2021 21:05:02 -0700 (PDT) Received: by mail-ua1-x92a.google.com with SMTP id i8so11620206uae.7; Mon, 27 Sep 2021 21:05:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lTLogfYs9KDD816DYVMN313IU1CMM7AH4bEceI3V/xM=; b=J8MBKVxUgZREo8K4teuVRl5yOX24zm1hp2lZZ3RANOb+Y81WzG4V32guB9H9Zpaahc zabzzrgtJEO4jiIdi3yI7ychbjG9WSmhjqq+sTIOwzt3Uw7tBYmGElH6asAuDuCnBzYm eDuq9H2zRL2ZquoLHdyY3KopQyvMDq+wJk0k94nvGFJ2cSyCK2vCLuT4Ou93vA6YCRGp hrT5+go0Ldj/99J648Mg0zS1MUt3pZZJN57nkLtFm9qM5llzU2IOL5MOJvgw1j40dVKj 4A7MF6W+VYa3DPYgWp4hp8nxedkC/UK3RCZTV6CdT1KJ6htkUw80Ln9pD3AjNkj4kOcs 7vLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lTLogfYs9KDD816DYVMN313IU1CMM7AH4bEceI3V/xM=; b=ISKsREZCDR82DNdKVxt88JWdE9C6MiOO2mVoKvbtNc+mB3aik/jEvflZgNKKPARLbO ujvDYBewThO1sCw7bZNc6fr9N4ooavFUkgZJAUH5jgFvFEeLtl2+yEJsOyHXn02WYhBY iwVVO15HlqXK0I3BXi+jNMYrJ9PDHrgNFTpdZuXwqI6Gi/zb+MVuLLjjsTqmT5jdYTeU N+etuUu5++iJ8q91BIgKpGzNxmi22UIKnaTCodpxyMgYIeE3EJ0BWuvC6pCt3/J6++DX bovwedkVY0cFthaBPtyX8kR9BlMTXEvAO4j0y5tmQSMfdGuGmhHqFfu0E/zX/Cawapem ed3Q== X-Gm-Message-State: AOAM533+QVH+gzCSVIHEnUhR8x7tRAog72vV3mzAAtUzxhmj+DXFCiAq F3ER4Z66zp0FRGBNJjPh88wsJcImKAcvRM63bvo= X-Google-Smtp-Source: ABdhPJwkKPQMawU+dFc5tbj9PObsYrG7aKDY/YkSpqNi8iiC8zxr+YH2KEy6koGr70rCvLQ4WxVtwVYK2RO/pzWrjFw= X-Received: by 2002:a9f:234a:: with SMTP id 68mr3253237uae.13.1632801901296; Mon, 27 Sep 2021 21:05:01 -0700 (PDT) MIME-Version: 1.0 References: <162510321507.13724.12968550804927630403@ietfa.amsl.com> <235FA332-7A68-4189-B74E-52D7276AE8AD@iii.ca> In-Reply-To: From: Suhas Nandakumar Date: Mon, 27 Sep 2021 21:04:50 -0700 Message-ID: To: "Murray S. Kucherawy" Cc: Cullen Jennings , Benjamin Kaduk , Paul Jones , perc@ietf.org, perc-chairs@ietf.org, draft-ietf-perc-dtls-tunnel@ietf.org, The IESG Content-Type: multipart/alternative; boundary="00000000000050be1005cd065128" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Sep 2021 04:05:18 -0000 --00000000000050be1005cd065128 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Sep 22, 2021 at 11:56 PM Murray S. Kucherawy wrote: > On Wed, Sep 22, 2021 at 10:29 PM Murray S. Kucherawy > wrote: > >> >> I=E2=80=99m 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. >>> >> >> I'll follow up with Ben and the others during the next IESG telechat (in >> about nine hours) >> > > I did this just now, and he reminds me that the IESG on review of this > document found that it actually meets the bar for Proposed Standard, sinc= e > it specifies a protocol with interoperable implementations, and we were > wondering if the Working Group really wanted to stick with Informational. > The IANA question was secondary. > > So I'm happy to send it through as-is, but I wanted to get that point > covered first. Unfortunately I have had very little success getting anyo= ne > to answer my inquiries. > [Suhas] From what I understand, authors are fine with either Standards track or an Informational reference. Informational was chosen with the intent of helping have a standard reference to enable interop and if IESG experts recommend the spec could be a Standards track one, we should be ok with it . Hope this helps > > -MSK > --00000000000050be1005cd065128 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Sep 22, 2021 at 11:56 PM Murr= ay S. Kucherawy <superuser@gmail.com> wrote:
On Wed, Sep 22, 2021= at 10:29 PM Murray S. Kucherawy <superuser@gmail.com> wrote:

I=E2=80=99m having a hard time understanding the p= roblem 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. =C2=A0

I would rat= her see this document published than go back to WGLC.

I'll follow up with Ben and the others duri= ng the next IESG telechat (in about nine hours)

I did this just now, and he reminds me that the IESG= on review of this document found that it actually meets the bar for Propos= ed Standard, since it specifies a protocol with interoperable implementatio= ns, and we were wondering if the Working Group really wanted to stick with = Informational.=C2=A0 The IANA question was secondary.

<= div>So I'm happy to send it through as-is, but I wanted to get that poi= nt covered first.=C2=A0 Unfortunately I have had very little success gettin= g anyone to answer my inquiries.
[Suhas]=C2=A0 From what I understand, authors are fine with eit= her Standards track or an Informational reference. Informational was chosen= with the intent of helping have a standard reference to enable interop and= if IESG experts recommend the spec could be a Standards track one, we shou= ld be ok with it . Hope this helps
=
-MSK
--00000000000050be1005cd065128--