Re: [saag] metadata insertion draft question

Yoav Nir <ynir.ietf@gmail.com> Sat, 15 October 2016 07:50 UTC

Return-Path: <ynir.ietf@gmail.com>
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 755DA1295D9 for <saag@ietfa.amsl.com>; Sat, 15 Oct 2016 00:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=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 pExtgW4dwIKj for <saag@ietfa.amsl.com>; Sat, 15 Oct 2016 00:50:52 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 31D611295BC for <saag@ietf.org>; Sat, 15 Oct 2016 00:50:52 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id d128so19669328wmf.1 for <saag@ietf.org>; Sat, 15 Oct 2016 00:50:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=fy1YMA9GIeo0Ue+3rv8e9L9CEv6fa3ULAi9qP3KNDLs=; b=hTrWh6qMUcEUOVQ/yF0RiFYRYT1yfJ6hDlk1dRROmz58Q58/8brFjIOlx4FArXINIo lEQNhfYPIRaL0ykQxngEPNPhr6RT5Z88ardf5tpYfJGH0dLbt51C/DL4Pe+oJ/H+x9aq 0pUV4eYWYkJnXmMptWAUafUt1/PFpYaCZtQ6euumWmyPeUcjJanN4CN+Ci3rKih5Zz6g V2xy+41IBOj3WfkRZmezVX7+7+Wt/Jd4zgr6KWRKaKAxCakrkhVhEaaXBXeq0LLRvflK VaoQm9jPXllIQIQA61ZDvru6ZijxLm3xlkfqFHRaVrckhBBynWPRYVpyXtoS1KmU814p NsUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=fy1YMA9GIeo0Ue+3rv8e9L9CEv6fa3ULAi9qP3KNDLs=; b=W3L0IgL5CyHsJ1VpuSXVtt3x2x+Zp9ov6mRnadT+wT1wZ/52Cdar5pPJtxMlWe46Jz ff7KU6qmGkg5PI0Hd7mUkQhgb7EXlFpWY3FJv89cruFJ1MWeshrklHE8u8CFB7qAKL8T PaA8Ra1PEclsyhYT5tYbubwIkJnpPxxl5jF9fZrYb60Y9YyzFnT7uG+qHrayk1XWOJiX Srzmz7jqkexn4zDfZWvFMjtTi/8VWT5Ud6odEbgdDe0vjW3/ylOOn9z4bYMEpdA18zwH CpKvkIqx9XKYAtI+/gLCsmkFoVXQWZ3vD8blLOR5eWu5i23/IwroT5aHmt2H0XRP4VkW IapQ==
X-Gm-Message-State: AA6/9RnNXh4fS/f/ci/fQCQcCp10IizzTtwhqItPiyPPNy3CzccOWpEgzXrkjtdVODzfPw==
X-Received: by 10.194.192.197 with SMTP id hi5mr4666321wjc.71.1476517850704; Sat, 15 Oct 2016 00:50:50 -0700 (PDT)
Received: from [192.168.1.13] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id af4sm26228055wjc.17.2016.10.15.00.50.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Oct 2016 00:50:49 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <BE9B4C4E-6B25-445D-9F4A-31982FCB62A5@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_019D189E-603C-4E2B-A15E-C2571D107D31"
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
Date: Sat, 15 Oct 2016 10:50:47 +0300
In-Reply-To: <86bbe523-972b-772c-b002-dbdbbedc00c8@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <86bbe523-972b-772c-b002-dbdbbedc00c8@cs.tcd.ie>
X-Mailer: Apple Mail (2.3226)
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/VeFmHemDJBMmTEldQWGk74iUwPQ>
Cc: Security Area Advisory Group <saag@ietf.org>
Subject: Re: [saag] metadata insertion draft question
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 15 Oct 2016 07:50:54 -0000

> On 14 Oct 2016, at 18:59, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> 
> Hiya,
> 
> Ted has written a draft [1] on this topic.
> 
> Earlier, we wondered whether it'd be good to include
> the meat of this into the work on 3552bis. [2]
> 
> Ted's now at the point of thinking his draft is near
> done so would like to know the plan.
> 
> If we seem to have consensus to include this in 3552bis
> then that's straightforward.
> 
> If we think that's not the best plan, then I'd likely
> look at AD sponsoring this separately to see if it has
> IETF consensus.
> 
> So, what do you think, should we:
> 
> a) incorporate the meat of [1] into [2]
> b) look at AD sponsoring [1] separately
> c) something else…

Plan (a) is tempting. However, since we published version -00 of 3552bis there have been zero comments on the list. We are going to try to revive the discussion, but there’s a real risk that 3552bis will either expire and go away or take a long, long time to reach publication.  I hope this isn’t the case, but it’s a real possibility.

The content in draft-hardie is worth publishing, so I don’t think it’s a good idea to tie it to 3552bis.  Of course we would link to it from 3552bis if it gets published on its own.

But if people prefer (a), just post a PR on [3] and I can merge it into a -01 version before Seoul.

Yoav

[3] https://github.com/IETF-SAAG/RFC3552bis <https://github.com/IETF-SAAG/RFC3552bis>