IETF Logo Mail Archive

Re: [IAB] IAB report to the community for IETF 103

Eric Rescorla <ekr@rtfm.com> Thu, 24 January 2019 17:07 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59529131212 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2019 09:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.04
X-Spam-Level:
X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 iqq1VlpbygmR for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2019 09:07:38 -0800 (PST)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 D1FE1130EB9 for <ietf@ietf.org>; Thu, 24 Jan 2019 09:07:37 -0800 (PST)
Received: by mail-lj1-x233.google.com with SMTP id x85-v6so5923817ljb.2 for <ietf@ietf.org>; Thu, 24 Jan 2019 09:07:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BYiKA+UlwODUtLQFXRQ/VB0aCbVpN91noAOoScw1+sE=; b=XM/5C7FDSXKeAc/yvxrDVaziy+ubJsDkRJDMKate9ZcSV/lyUlV+TKR2Hf6g+mUW6n KqIp8B7TMNbLEYhSUNUuRKsltkqFr3GjLv3PliG4YfLeHylxsNdlN6r6wP/riCaePL4Z lN6MXzw9gLKfEWCPPSOp6fBw0HZ7Jha3ctrTLEP+37PDSRCKwiDini1nSJs3DXNPj+C2 Q4/vxexYOZ60gT/51oNEydnXqeuC8I0xRYqe1FuEETSCDrkGfSNdrvwZvUBCTpcXjOwH qVP6T/bVWAKCIxOwKzpr1mCf73R9YQGgG/WBxzeniNfcyBArj6jmUVVWhvSpDUe3iFzA vqlw==
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=BYiKA+UlwODUtLQFXRQ/VB0aCbVpN91noAOoScw1+sE=; b=rru2vBH/HLTd8gBt6ghgmx75TYmXT4cJ4u6p/Sli2TsZ0yT5gOujvS5mzUjX117J5D 2TD4TIVx5Z+iuB2j99T+TsTf7/AL0xYZ1Yq3QlKTNKxQGs+ODYpMju9uy/UA3oYtxTGm jL26YHs8xzYVttCJbiLqRJ6/f0ADTsnxtQepS9XKREzSY6VzlDuFgmHNKETVDAvHumAO 4vwEzqrJFTZnXiSoB2PfMuFkuvXQngKDeljq4v5xa63se6WZMxf27NJzZLtMcBM1Z9pd YzY+CNVcpCRYCmmaAUEux8GsOPc90UEPs0AQvB9gv+rtHHBwM7ucdXFiuBWOS6ep00Qk +Q8Q==
X-Gm-Message-State: AJcUukf9GiG4NIYp2xr+gP0sf/CbpXZZDTX57TeZa55CafBY9Ka2AM9d igkYUT+ex2ToaTHSF+bzdT8RBeMLDN9jGwg+SCEhJg==
X-Google-Smtp-Source: ALg8bN4JT0Y4gX1uvt2KQbcHQAPmn1EawTIG1dFM6nnjAlnYITvKxU6WCeB2cd6qg8C6QPP5CuKWeJYUrx2ldTctl74=
X-Received: by 2002:a2e:2909:: with SMTP id u9-v6mr6220171lje.28.1548349655854; Thu, 24 Jan 2019 09:07:35 -0800 (PST)
MIME-Version: 1.0
References: <CA+9kkMDEP-JKDwcwRMT7QUs-yQi+PsuKo22mFZxB6yKTEqTuSQ@mail.gmail.com> <6.2.5.6.2.20181111093128.0bd80f60@elandnews.com> <CA+9kkMAcJSixn2-S-OwK0tojyJLQZ=mrhr4NT7OM9+ji0vb=GA@mail.gmail.com> <CABcZeBPSGzmtG-w5cGYDrYmRxhp7Z48uuFXQ4Abn3J-71YWX2A@mail.gmail.com>
In-Reply-To: <CABcZeBPSGzmtG-w5cGYDrYmRxhp7Z48uuFXQ4Abn3J-71YWX2A@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 24 Jan 2019 09:06:59 -0800
Message-ID: <CABcZeBPgSKkiwy8Qe984Q9VRbtjR96w5Tq0eqwyM_0_g1YxEag@mail.gmail.com>
Subject: Re: [IAB] IAB report to the community for IETF 103
To: Ted Hardie <ted.ietf@gmail.com>
Cc: S Moonesamy <sm+ietf@elandsys.com>, IESG <iesg@ietf.org>, "iab@iab.org IAB" <iab@iab.org>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000039c7e70580373f0c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kR-8yzUK0cfeOVK9C3s_RN14MTY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2019 17:07:40 -0000

And here is ETSI's response:
https://datatracker.ietf.org/liaison/1624/

On Thu, Dec 6, 2018 at 2:41 PM Eric Rescorla <ekr@rtfm.com> wrote:

> Yesterday, we sent the following liaison statement to ETSI on this topic:
> https://datatracker.ietf.org/liaison/1616/
>
> On Mon, Nov 12, 2018 at 2:08 AM Ted Hardie <ted.ietf@gmail.com> wrote:
>
>> On Sun, Nov 11, 2018 at 6:57 PM S Moonesamy <sm+ietf@elandsys.com> wrote:
>>
>>>
>>> ETSI TS 103 523-3 V1.1.1 specifies some changes to RFC 8446.  Does
>>> the IAB have an opinion on its potential impact on the Internet trust
>>> model and the risk of fragmentation if multiple jurisdictions
>>> required it through regulation?
>>>
>>>
>> The IETF security ADs provided feedback to ETSI
>> <https://datatracker.ietf.org/liaison/1538/> on this ETSI work last year
>> and ETSI responded in liaison statement CYBER(17)011006r1.  The IAB
>> generally agreed with the IETF security Area Directors' analysis.
>>
>> regards,
>>
>> Ted Hardie
>>
>

v2.23.0 | Report a Bug | By Email