Compatibility issue

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 01 April 2017 22:51 UTC

Return-Path: <brian.e.carpenter@gmail.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 9D27B127337 for <ietf@ietfa.amsl.com>; Sat, 1 Apr 2017 15:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 c2AmvhwsFfUF for <ietf@ietfa.amsl.com>; Sat, 1 Apr 2017 15:51:34 -0700 (PDT)
Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::241]) (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 4F4F5127BA3 for <ietf@ietf.org>; Sat, 1 Apr 2017 15:51:34 -0700 (PDT)
Received: by mail-it0-x241.google.com with SMTP id w11so5202211itb.0 for <ietf@ietf.org>; Sat, 01 Apr 2017 15:51:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:organization:to:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=RW5Fc5RnDWQfwRlOe1E3yFbWZEKllg3iED4puXCofBg=; b=rtc49o7NktVMk7hPHkUx7sVgUpW/mCie7j5Tl0m0wBQIY8nDW8OMTf8XWVj0CAStii 32FtUPsfy+LIN/UjUPinzPrIbwjp+W9JrL4gqnFQcwbQdO99Soz+qsN03pX7Y6MHC+gW JJctdTsh54BZTCCVbhuK8v6iPdYgWjhryLLIyUdFxwdKTxHKqRNOI9RIdxQ1mHL9sVAH n9NkG0Vvi+WkBFU4z8xqACOp72eFoQhZbpkOpAEFKcgFXdcLlmZqOUgmt2WFQRSzTkIr 3qmCVviuwHU+6KIATXybKJhwdMa7xDwMO448LI3pTgKXxrsQvStA7lDbHz7gQqNI7Uuj edkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:organization:to:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=RW5Fc5RnDWQfwRlOe1E3yFbWZEKllg3iED4puXCofBg=; b=BnK1hWIcFfoWyOtS//IF8XsDAQCtUFYko5lAj7PAyr1YUqIbHqrHhzbd0/Hmi0E9aO 7MalXe1YhTAB6VYO3NdLS+ttPwFIg2DmPC7/+ZQUGFwmD8sHrKVPF4B54ytbllL24WW+ znWI3qPY7pgrApFfWabh6dzZwG8HKulJLaQkA6xcw0iYmFTkHpmD+rMJh5Rhe1R71IE2 Xl4omeFFtQuvSkBmmOFSQq/nhBbkUADyvYpfx7wGKHNPKopfNjZJm/3uruc+qCov1/n+ gu22H6cRDqrh38QDDXE1FA2wVZPdpcH4KeCGD/PX3yeeudEgE2vgk/YQaNJqxAE4i9Bh eoxg==
X-Gm-Message-State: AFeK/H2AXiCU7HAQ34fJ2sB3qN7hHFS7Pt9R5zvNiIoFpd8xjDUe63bw 190hJLFhqHwyAkwq
X-Received: by 10.36.160.195 with SMTP id o186mr4217102ite.102.1491087093592; Sat, 01 Apr 2017 15:51:33 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id p140sm3517440itc.27.2017.04.01.15.51.32 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 01 Apr 2017 15:51:32 -0700 (PDT)
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Compatibility issue
Organization: University of Auckland
To: IETF discussion list <ietf@ietf.org>
Message-ID: <79a279e1-85a5-865d-e427-1aa61427e100@gmail.com>
Date: Sun, 2 Apr 2017 10:51:32 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K_gzBA2F5mBdlpScpez9H_270v0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 01 Apr 2017 22:51:35 -0000

Many people have been asking whether RFC8136 is compatible with the earlier RFC8135. As far as we can tell, there is indeed no incompatibility; they are complementary mechanisms. We will produce a more detailed analysis soon (see section 7.1 of [I-D.farrel-soon]).

Regards
   Brian