+1 to Tim - tell the reader explicitly that they will only ever get PQC w/
TLS 1.3 or higher.
Cheers,
- Ira
On Thu, Dec 21, 2023, 12:34 PM Tim Hollebeek wrote:
> I personally think this point is important enough to be made explicitly
> instead of implicitly.
>
>
>
> If we want to communicate
Hi,
Approve.
Cheers,
- Ira
On Wed, Nov 29, 2023 at 10:51 AM Joseph Salowey wrote:
> RFC 8773 (TLS 1.3 Extension for Certificate-Based Authentication with an
> External Pre-Shared Key) was originally published as experimental due to
> lack of implementations. As part of implementation work
Hi,
Yes - I support deprecating all FFDHE cipher suites including well-known
groups.
Cheers,
- Ira
On Tue, Dec 13, 2022 at 9:46 AM Sean Turner wrote:
> During the tls@IETF 115 session topic covering
> draft-ietd-tls-deprecate-obsolete-kex, the sense of the room was that there
> was support
Hi Ned,
No - Henk meant IETF 113 - this is not a BoF at IETF 114 in July - this is
a BoF on next Thursday, that was dispatched as such at IETF 113.
Henk - that's lunch hour at ESCAR USA next week - I'll try to join.
Cheers,
- Ira
*Ira McDonald (Musician / Software Architect)*
*Chair - SAE
Hi Ashley,
Bear in mind that DTLS 1.3 languished in the RFC Editor's queue for over a
year.
The major TLS libraries have had implementations and have been doing
interop testing
for a long time. Simply doing software update to current library versions
would make
DTLS 1.3 available in civil
would be: let's get consensus on the *semantics* we want for
> the various categories without worrying about the names (call them A, B, C,
> etc.) and then we can name them after.
>
> -Ekr
>
>
> On Fri, Oct 29, 2021 at 2:14 PM Ira McDonald
> wrote:
>
>> Hi Eric,
>>
Hi,
I agree that the "Recommended" column in the IANA registry (which is
frequently misunderstood)
should just be renamed to "IETF Consensus". Obvious and self-explanatory.
Cheers,
- Ira
On Tue, Oct 26, 2021 at 10:45 AM Hannes Tschofenig <
hannes.tschofe...@arm.com> wrote:
> Rich, this makes
Hi,
I agree with Bill. Keeping confidentiality in all TLS/1.3 connections is
future proofing.
Supposedly analyzing and then leaving confidentiality out invites future
attacks.
Cheers,
- Ira
On Thu, Feb 11, 2021 at 9:56 AM Bill Frantz wrote:
> On 2/11/21 at 9:01 PM,
I support Stephen and Uri and oppose adoption.
On Mon, Jul 27, 2020 at 8:20 AM Blumenthal, Uri - 0553 - MITLL <
u...@ll.mit.edu> wrote:
> I support Stephen and oppose adoption. IMHO, this is not a technology that
> IETF should standardize.
>
>
> On 7/25/20, 10:07, "TLS on behalf of Stephen
I support Stephen and Uri and oppose adoption.
On Mon, Jul 27, 2020 at 8:20 AM Blumenthal, Uri - 0553 - MITLL <
u...@ll.mit.edu> wrote:
> I support Stephen and oppose adoption. IMHO, this is not a technology that
> IETF should standardize.
>
>
> On 7/25/20, 10:07, "TLS on behalf of Stephen
+1 for TLS WG adoption.
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Co-Chair - TCG Metadata Access Protocol SG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
Hi,
I strongly prefer option 3. The future-proofing and avoidance of a
proliferation of new columns in the IANA registries is paramount.
The points about QUIC highlight the near-term need to clean up
this this issue.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG
I support adoption.
- Ira
On Fri, Aug 17, 2018 at 1:32 PM, Sean Turner wrote:
> At the TLS@IETF102 session, there seemed to be some interest in adopting
> draft-moriarty-tls-oldversions-diediedie as a WG item. This email is to
> determine whether there is WG consensus to adopt this draft as a
community goes right on conflating SSL
with TLS on web sites.
I change my two cents to "TLS 4" but am unsure about "4" or "4.0" because
the tech community has been trained to care about major.minor.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Co-Chair
in automotive.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Hi,
This survey of TLS in 1 million web servers shows that 93% support 3DES -
oof!
https://jve.linuxwall.info/blog/index.php?post/TLS_Survey
3DES hasn't quite disappeared on the Internet.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
objects to keeping ippusbxd in a separate package,
please speak up now.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet
Hi Pete and Robert,
My mistake - agreed - (c) should go - and no need for the note about PWG
IPP/2.0.
(which will get updated anyway to reference the IETF IPPS spec next year).
Cheers,
- Ira (wearing PWG IPP co-chair and IPP/2.0 co-editor hats)
Ira McDonald (Musician / Software Architect)
Co
soon to your other comments.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert
Hi Bjoern,
Thanks for your excellent comments.
I propose some fixes inline in your note below.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP Printer
: for years and users expect to be
able to use ANY valid https: URI for a target Printer object.
Mike - can we constrain ipps: to use UTF-8?
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
21 matches
Mail list logo