IETF Logo Mail Archive

Re: [Taps] Éric Vyncke's Discuss on draft-ietf-taps-transport-security-11: (with DISCUSS and COMMENT)

Kyle Rose <krose@krose.org> Thu, 09 April 2020 14:01 UTC

Return-Path: <krose@krose.org>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE1E3A0BBC for <taps@ietfa.amsl.com>; Thu, 9 Apr 2020 07:01:15 -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_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 (1024-bit key) header.d=krose.org
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 1ZpYF271--dy for <taps@ietfa.amsl.com>; Thu, 9 Apr 2020 07:01:11 -0700 (PDT)
Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (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 C55733A0747 for <taps@ietf.org>; Thu, 9 Apr 2020 07:01:05 -0700 (PDT)
Received: by mail-yb1-xb2e.google.com with SMTP id l84so5781532ybb.1 for <taps@ietf.org>; Thu, 09 Apr 2020 07:01:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zOVghcbg02tswPxPappPWcfQOHWa5zVejgzsFGbeXmE=; b=C7xU3AIvRzgkRgcM3KGFAqreo4hmtizUnjVCg0W/wl/4Zjpjs0eDnnSm4fRy/E8UHQ 2bgHANWY+bzP0eC3KJpwm2sNlhEE5h2oYVJD9wwK/kzJj57HhV2khfzFZBTESUtaBvaG gDcJO6fRqjSm8b53y6ctLLddTvf+PPzSOj1mU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zOVghcbg02tswPxPappPWcfQOHWa5zVejgzsFGbeXmE=; b=c/ALoHxRFr3bfjA32oIRhSss9SphAUfPE18dXHwsD+g02P5arkgotRiX8BGuGKNqUt 2+l2PxMCVPR2CLdcyEhN2J06CajFCB7wNOi2KG+rEEvmkFHpXBAFo8FUiX2v/uJX6Fi9 2COyN+UwDaP9D6DWKufr7RtmwupZY6wKMnq9zBwC0mpoV0K4GE4SIgAtdVThv5DiYQIc HKYwLEodJEVK5neW2ydrcJ+Qud+r117h2L9qvgIV0UhYbwXhC5n0pVvot344PxkbKcpp YCOrxluJtbRJSRWEwvmkBHBok+bPQCY5OdDrMRZyCoWaup3tZodtaxmgG2TOrtjrDZO9 oUdQ==
X-Gm-Message-State: AGi0PuZb0oe7gWF5hJZfk04F1Ev0lP3xVL3Hmq3+Wv1U4jnl6t2OCl/x aLPv1YG6Mbc7lkyMtFgLo0VO7YmKa+z7xy314tXxkQ==
X-Google-Smtp-Source: APiQypKy/W4KMO7agURkxwJ4n0puY4EbSMj8dypOf/IeVuXji3gYwT4bCY121QrYqMkkjJooRMcuDHahEgYBYTaRz3A=
X-Received: by 2002:a25:6757:: with SMTP id b84mr21466245ybc.396.1586440864304; Thu, 09 Apr 2020 07:01:04 -0700 (PDT)
MIME-Version: 1.0
References: <158642650492.8627.16111048765603393250@ietfa.amsl.com> <33e2fe4c9f68ee3fea18ed7109f210ea9374e1d8.camel@ericsson.com> <894AC91E-8128-42F0-8E6B-1A66EF84CF43@cisco.com> <HE1PR0702MB37723EFD59A730E22EE3D8FF95C10@HE1PR0702MB3772.eurprd07.prod.outlook.com> <EA85FA19-A337-49E7-95C8-FC0D39ABA63E@cisco.com> <CALaySJLn4N13CdHhwg695_uBOm22FsX3WE_yuzQDeZP0HnB3cQ@mail.gmail.com>
In-Reply-To: <CALaySJLn4N13CdHhwg695_uBOm22FsX3WE_yuzQDeZP0HnB3cQ@mail.gmail.com>
From: Kyle Rose <krose@krose.org>
Date: Thu, 09 Apr 2020 10:00:52 -0400
Message-ID: <CAJU8_nUy0ga6F--W6S9UK_V=WC18LrFRDtDpsk3heNdbdFsZqQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "brian@innovationslab.net" <brian@innovationslab.net>, "philipp@tiesel.net" <philipp@tiesel.net>, Mohit Sethi M <mohit.m.sethi@ericsson.com>, "taps-chairs@ietf.org" <taps-chairs@ietf.org>, "draft-ietf-taps-transport-security@ietf.org" <draft-ietf-taps-transport-security@ietf.org>, "int-dir@ietf.org" <int-dir@ietf.org>, "caw@heapingbits.net" <caw@heapingbits.net>, "taps@ietf.org" <taps@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002ca4c405a2dc0c19"
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/dUrL3Zp56lsI-pGcUpV-_CgCSNU>
Subject: Re: [Taps] Éric Vyncke's Discuss on draft-ietf-taps-transport-security-11: (with DISCUSS and COMMENT)
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2020 14:01:16 -0000

Agreed. This document is not an endorsement of any of the protocols
mentioned, merely an analysis from a security perspective. Mentioning IPv6
here would be a non-sequitur.


On Thu, Apr 9, 2020 at 9:46 AM Barry Leiba <barryleiba@computer.org> wrote:

> I have to agree with Magnus here: I think this is really a stretch.
>
> Barry
>
> On Thu, Apr 9, 2020 at 9:40 AM Eric Vyncke (evyncke)
> <evyncke=40cisco.com@dmarc.ietf.org> wrote:
> >
> > Magnus,
> >
> > While my comment is not directed to the core of the document, I believe
> that when one IETF document refers in the section 3, ' Transport Security
> Protocol Descriptions', to non-IETF protocols, then in order to avoid any
> 'IETF blessing' of this protocol, it should clearly state the important
> protocol limitations when describing this protocol.
> >
> > Regards
> >
> > -éric
> >
> > -----Original Message-----
> > From: iesg <iesg-bounces@ietf.org> on behalf of Magnus Westerlund
> <magnus.westerlund=40ericsson.com@dmarc.ietf.org>
> > Date: Thursday, 9 April 2020 at 14:41
> > To: "evyncke=40cisco.com@dmarc.ietf.org" <evyncke=
> 40cisco.com@dmarc.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
> > Cc: "brian@innovationslab.net" <brian@innovationslab.net>, "
> int-dir@ietf.org" <int-dir@ietf.org>, Mohit Sethi M <
> mohit.m.sethi@ericsson.com>, "taps-chairs@ietf.org" <taps-chairs@ietf.org>,
> "draft-ietf-taps-transport-security@ietf.org" <
> draft-ietf-taps-transport-security@ietf.org>, "philipp@tiesel.net" <
> philipp@tiesel.net>, "caw@heapingbits.net" <caw@heapingbits.net>, "
> taps@ietf.org" <taps@ietf.org>
> > Subject: RE: Éric Vyncke's Discuss on
> draft-ietf-taps-transport-security-11: (with DISCUSS and COMMENT)
> >
> >     >
> >     > A simple mention of the lack of IPv6 in section 3 of the
> description would
> >     > be
> >     > more than enough for me.
> >
> >     Yes, but why do you consider that relevant for this document?
> >
> >     Cheers
> >
> >     Magnus
> >
> >
> >
> >
>

v2.23.0 | Report a Bug | By Email