[TLS] Re: Draft THURDAY minutes are at
Nadim Kobeissi <[email protected]> Thu, 23 Jul 2026 12:12:03 +0200
| Newsgroups | gmane.ietf.tls |
|---|---|
| Message-ID | <[email protected]> |
--===============8679294636588231835==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_1F64BCEA-90A0-4469-AA2B-D6C4C7FB2D00"
--Apple-Mail=_1F64BCEA-90A0-4469-AA2B-D6C4C7FB2D00
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
Hi Rich,
I=E2=80=99m familiar with RFC2418 [1] and I believe that it actually =
validates Fabiana=E2=80=99s queries. Quoting the sections you=E2=80=99re =
mentioning:
Section 3.4 (all-caps emphasis of parts that support Fabiana=E2=80=99s =
queries is added by me):
Disputes are possible at various stages during the IETF process. As
much as possible the process is designed so that compromises can be
made, and genuine consensus achieved; however, there are times when
even the most reasonable and knowledgeable people are unable to
agree. TO ACHIEVE THE GOALS OF OPENNESS AND FAIRNESS,
SUCH CONFLICTS MUST BE RESOLVED BY A PROCESS=20
OF OPEN REVIEW AND DISCUSSION.
Section 6.1 (all-caps emphasis of parts that support Fabiana=E2=80=99s =
queries is added by me):
The Chair has ultimate responsibility for ensuring that a working
group achieves forward progress and meets its milestones. THE
CHAIR IS ALSO RESPONSIBLE TO ENSURE THAT THE
WORKING GROUP OPERATES IN AN OPEN AND FAIR MANNER.
In either case, I would appreciate a substantive response directly from =
the chairs to my original message about Fabiana=E2=80=99s queries [2].
[1] https://www.rfc-editor.org/info/rfc2418
[2] =
https://mailarchive.ietf.org/arch/msg/tls/O5tgVST_oEtwC5-PvoD-xaMEKRk/
Nadim Kobeissi
Symbolic Software =E2=80=A2 https://symbolic.software
> On 23 Jul 2026, at 12:05=E2=80=AFPM, Salz, Rich <[email protected]> =
wrote:
>=20
>=20
>=20
> On 7/23/26, 11:59=E2=80=AFAM, "Nadim Kobeissi" =
<[email protected]> wrote:
> A few days later, we didn=E2=80=99t get any substantive response to =
Fabiana=E2=80=99s reasonable questions,=20
>=20
> Those questions were not not reasonable and rather showed an ignorance =
of how the IETF works, in particular RFC 2418 which describes how IETF =
working groups work. Look at Section 3 and 6.1=20
>=20
>=20
--Apple-Mail=_1F64BCEA-90A0-4469-AA2B-D6C4C7FB2D00
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" =
content=3D"text/html; charset=3Dutf-8"></head><body =
style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;">Hi Rich,<div><br></div><div>I=E2=80=99m =
familiar with RFC2418 [1] and I believe that it actually validates =
Fabiana=E2=80=99s queries. Quoting the sections you=E2=80=99re =
mentioning:</div><div><br></div><div>Section 3.4 (all-caps emphasis of =
parts that support Fabiana=E2=80=99s queries is added by =
me):</div><div><br></div><div><div> Disputes are possible at =
various stages during the IETF process. As</div><div> much =
as possible the process is designed so that compromises can =
be</div><div> made, and genuine consensus achieved; however, =
there are times when</div><div> even the most reasonable and =
knowledgeable people are unable to</div><div> agree. =
TO ACHIEVE THE GOALS OF OPENNESS AND FAIRNESS,</div><div> =
SUCH CONFLICTS MUST BE RESOLVED BY A =
PROCESS </div><div> OF OPEN REVIEW AND =
DISCUSSION.</div><div><br></div><div>Section 6.1 (all-caps emphasis of =
parts that support Fabiana=E2=80=99s queries is added by =
me):</div><div><br></div><div><div> The Chair has =
ultimate responsibility for ensuring that a working</div><div> =
group achieves forward progress and meets its milestones. =
THE</div><div> CHAIR IS ALSO RESPONSIBLE TO =
ENSURE THAT THE</div><div> WORKING GROUP OPERATES IN =
AN OPEN AND FAIR MANNER.</div></div><div><br></div><div>In either case, =
I would appreciate a substantive response directly from the chairs to my =
original message about Fabiana=E2=80=99s queries =
[2].</div><div><br></div><div>[1] =
https://www.rfc-editor.org/info/rfc2418</div><div>[2] =
https://mailarchive.ietf.org/arch/msg/tls/O5tgVST_oEtwC5-PvoD-xaMEKRk/</di=
v><div>
<meta charset=3D"UTF-8"><br>Nadim Kobeissi<br>Symbolic Software =
=E2=80=A2 https://symbolic.software<br>
</div>
<div><br><blockquote type=3D"cite"><div>On 23 Jul 2026, at 12:05=E2=80=AFP=
M, Salz, Rich <[email protected]> wrote:</div><br =
class=3D"Apple-interchange-newline"><div>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
<div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, =
sans-serif; font-size: 12pt;">
<br>
</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, =
sans-serif; font-size: 12pt;">
<br>
</div>
<div id=3D"mail-editor-reference-message-container">
<div class=3D"ms-outlook-mobile-reference-message skipProofing" =
style=3D"direction: ltr;">
</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing">On =
7/23/26, 11:59=E2=80=AFAM, "Nadim Kobeissi" =
<[email protected]> wrote:</div>
<ul =
data-editing-info=3D"{"applyListStyleFromLevel":false,"unor=
deredStyleType":4}" style=3D"direction: ltr; margin-top: 0px; =
margin-bottom: 0px;">
<li style=3D"direction: ltr; margin-top: 0px; margin-bottom: 0px; =
list-style-type: "=E2=9E=A2 ";">
<div class=3D"ms-outlook-mobile-reference-message skipProofing" =
role=3D"presentation" style=3D"direction: ltr;">
A few days later, we didn=E2=80=99t get any substantive response to =
Fabiana=E2=80=99s reasonable questions, </div>
</li></ul>
<div style=3D"direction: ltr;"><br>
</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, =
sans-serif; font-size: 12pt;">
Those questions were not not reasonable and rather showed an ignorance =
of how the IETF works, in particular RFC 2418 which describes how IETF =
working groups work. Look at Section 3 and 6.1 </div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, =
sans-serif; font-size: 12pt;">
<br>
</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, =
sans-serif; font-size: 12pt;">
<br>
</div>
</div>
</div>
</div></blockquote></div><br></div></body></html>=
--Apple-Mail=_1F64BCEA-90A0-4469-AA2B-D6C4C7FB2D00--
--===============8679294636588231835==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVExTIG1haWxp
bmcgbGlzdCAtLSB0bHNAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB0
bHMtbGVhdmVAaWV0Zi5vcmcK
--===============8679294636588231835==--