[saag] TCPINC report

Kyle Rose <krose@krose.org> Wed, 18 July 2018 17:58 UTC

Return-Path: <krose@krose.org>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99B28130DDE for <saag@ietfa.amsl.com>; Wed, 18 Jul 2018 10:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 A0B5UFYlWLRs for <saag@ietfa.amsl.com>; Wed, 18 Jul 2018 10:57:59 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 9759F1292F1 for <saag@ietf.org>; Wed, 18 Jul 2018 10:57:59 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id d189-v6so10442400oib.6 for <saag@ietf.org>; Wed, 18 Jul 2018 10:57:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=oMXyH8NAsIhosew+N/GlpRXPFfbK7yPRqaC2qshdAZg=; b=Nn1GC/Q9MbcINUeuM5WOnjBUgwOABuScBquw+p2AVfZ35Mm6ta8n/jsca+qe1qk45Z aODHZSNX5fVjh4xDNPhGEJk1zeeOsx4Bg8VtJOMEe8sqcUn2H7lUecy1Mq8mE4fFzv0o Pl4AtU6U+5CJ8wdtTj6BxW5jW9gjVYqzTXnx8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oMXyH8NAsIhosew+N/GlpRXPFfbK7yPRqaC2qshdAZg=; b=ltPp89M70+SQ08hlBW4cbwtyt+Kolf4C4NLew5b12/mjoeOjrPaTh8RmuIM7L1Q7VU lxaIKGbDJhXLVIM4PlN6zE4OTvMVh8IHsQXI9HN/7ruTck1tjvpKBf6KqzA9TVVoNtWM qLO+FJIxjncN/j92yeVDvh/3gimQS2gYGCPP4pWbGqkOcdM0wQGI0HNaaDo/A5aTjhPM POSdM5T1OPL3tVk+AoyprbaK+fPbdBtOqucHvQi1oLh3goW0aKTj424VVAvIVzw1z2f4 tmno+Djw9SO1zytm2GKqd9et1Sy1a7t7IxSqm9U43ZkKuUYtYpA8+6vEFhg1M5BSS/XX BPtA==
X-Gm-Message-State: AOUpUlHr8GjteZFlyIJQf42iPZXaj3/LP7v4QZmxofAOdImkFgWjP3Vh ruQBuyp5HJiBUhhOOX+qFvUHXn8Y6fMDom8o+eu/sFk8tus=
X-Google-Smtp-Source: AAOMgpeSUTwECSPVGnyL4of3Og0IPt6Wt+YrGhiKZhWXuOKhAWQ7Ppmn/n5y2h9p6zd5N12T0OXHSLk3ItvZ3aUOuxg=
X-Received: by 2002:aca:4288:: with SMTP id p130-v6mr2044254oia.265.1531936678492; Wed, 18 Jul 2018 10:57:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:204a:0:0:0:0:0 with HTTP; Wed, 18 Jul 2018 10:57:57 -0700 (PDT)
X-Originating-IP: [2001:67c:370:128:99fd:af81:3a80:2e8f]
From: Kyle Rose <krose@krose.org>
Date: Wed, 18 Jul 2018 13:57:57 -0400
Message-ID: <CAJU8_nV23xffdwrhte6e+mnR=-BW3fH388FFOkbjJr4bp+Uqkg@mail.gmail.com>
To: saag@ietf.org, tcpinc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008a4daa057149cde9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/sFmEuwKdAr2gKo1N5kcSyDyGT_8>
Subject: [saag] TCPINC report
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2018 17:58:02 -0000

TCPINC did not meet at IETF 102.

Of the two main drafts, TCP-ENO has been approved for publication and is
pending a writeup (presumably waiting on approval of the other draft).
Tcpcrypt has an open discuss point with a resolution pending review by the
security AD. The remaining milestone is to complete and request publication
of an informational abstract API draft.