IETF Logo Mail Archive

Re: [mile] Spencer Dawkins' Block on charter-ietf-mile-03-03: (with BLOCK)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 21 November 2018 03:08 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9181012896A; Tue, 20 Nov 2018 19:08:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 atYnjJeerRGO; Tue, 20 Nov 2018 19:08:03 -0800 (PST)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 6447A126DBF; Tue, 20 Nov 2018 19:08:03 -0800 (PST)
Received: by mail-lf1-x136.google.com with SMTP id f23so2851059lfc.13; Tue, 20 Nov 2018 19:08:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gf3nthRLeeJlxsSO4kwiS2W1AOLsqLQdkeT5wIeI6z4=; b=j32X7AxII+iyMK2zaIoDNjxTgcCx6Nyl9rbQGA532K7DkC7n58qYUwRzW0k3/ax1YD v6H+wiVPLbxNPTU6QJ3SPCatL3u2bfVCGI5hW7Xy3XAT2ZeY/6RoVYGfwmgAYx80mqtk 6QyiqQVGsCxjmQtTclitrMgU2lMovROot1BsLjMDWzVHS4QU3+900j8ZDCZYllqlWWZw rQVbFdn4yzQOX43oiPHcbhUP1vWOlYkoRuXHvG1J4AtGYrrO0QRpqrwBFtHKby12TuQi MPaBtwiL5Nyx9k90/7iqHEkKm/VzPHxdc47CYQ7G2h7IyMlqw3oB7YxUX2PKQqMO08md ToKQ==
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=gf3nthRLeeJlxsSO4kwiS2W1AOLsqLQdkeT5wIeI6z4=; b=H0zxfmEVktm9Fw5ovPCacBLSZ4JufLDW+B4R/nbI3ZwsshSWRd58yYX8JRZfw+zpmx xqkRI58D5AhmthMd1yIziBoRMFie/ETYLgwzKvq4qP2si4Bo3FIpY484cOZ6EX/16r7k 4Ey2GV/dKK/qVK60tiMvagWuUTWSo7YpCZiXMaEDQGH3Ju42q2aBmaeWGOPbId/trtHQ JiWOtWOQNz+JaAzne5Xi2VPAzFBgdP37iXxCEGDZSZqywNRx9L4bbPj/9rtEtAqYPVqu khiuDmxVunpd+7BXvc2H/r9dUZoWKYR0gxCNl5SpWn5lQwvTfd+V0zmrfogbqRQBKjkj Egog==
X-Gm-Message-State: AGRZ1gLprFo5ocQ0VYwtCGrk1uhbTMJ9KcCba4p7sjEx2PvP7MqTAgmQ MnJRGGXGugiRC5gvApBJBh/jGNTxzINuAJkGKLPh7w==
X-Google-Smtp-Source: AJdET5e5+qdAYSlULIusru1eFLybUy62e8CWZU8NdlRjpyOcJDTtGdtuiSbQiNI0TH1VKV06+8npE/32/RGx6D6MjFY=
X-Received: by 2002:a19:d145:: with SMTP id i66mr2675713lfg.97.1542769681207; Tue, 20 Nov 2018 19:08:01 -0800 (PST)
MIME-Version: 1.0
References: <154274395688.29937.12557512339611908452.idtracker@ietfa.amsl.com> <34339FA8-9644-48A7-81D0-D1CF99E73381@cisco.com>
In-Reply-To: <34339FA8-9644-48A7-81D0-D1CF99E73381@cisco.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 20 Nov 2018 21:07:47 -0600
Message-ID: <CAKKJt-fAdv0Sc4QsHtjwQUjV2dVzKM41r8-+=VCKtDKb1W6t_A@mail.gmail.com>
To: ncamwing@cisco.com
Cc: IESG <iesg@ietf.org>, mile@ietf.org, mile-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d1968d057b240e16"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/DVpznuz0VDZ4FkzinXC1kaLjqfM>
Subject: Re: [mile] Spencer Dawkins' Block on charter-ietf-mile-03-03: (with BLOCK)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2018 03:08:06 -0000

Hi, Nancy,

On Tue, Nov 20, 2018 at 4:50 PM Nancy Cam-Winget (ncamwing) <
ncamwing@cisco.com> wrote:

> Hi Spencer,
> My apologies if I didn't capture things properly.  I updated the text to
> read:
> "and standardizing mappings into
> application substrate protocols, such as HTTP and XMPP,"
>
> So, while we are not defining transport protocols we are demonstrating how
> they are used to transport the incident reports/data.
> Would the following sentence be more appropriate:
>
> "....and standardizing how transports such as HTTP(s) and XMPP become
> substrates for MILE data."
>

That sounds much better. Based on this e-mail exchange, I'll clear.

(And for your amusement, I stopped being a WG chair about five minutes
before they deployed the WG chair's tooling for the datatracker, so I have
a very vague understanding of what WG chairs can actually update, beyond
what my chairs have updated - I didn't know you could make these changes!)

Thanks,

Spencer


> Warm regards, Nancy
>
> On 11/20/18, 11:59, "mile on behalf of Spencer Dawkins" <
> mile-bounces@ietf.org on behalf of spencerdawkins.ietf@gmail.com> wrote:
>
>     Spencer Dawkins has entered the following ballot position for
>     charter-ietf-mile-03-03: Block
>
>     When responding, please keep the subject line intact and reply to all
>     email addresses included in the To and CC lines. (Feel free to cut this
>     introductory paragraph, however.)
>
>
>
>     The document, along with other ballot positions, can be found here:
>     https://datatracker.ietf.org/doc/charter-ietf-mile/
>
>
>
>     ----------------------------------------------------------------------
>     BLOCK:
>     ----------------------------------------------------------------------
>
>     It doesn't look like the conversation Nancy Cam-Winget and I had about
> my
>     comments on our previous ballot have been reflected yet - this version
> of the
>     charter still describes work on transport protocols, and Nancy said it
>     shouldn't be, because they're already based on HTTP and XMPP.
>
>     The correct term is something like "substrate for application
> protocol", if I'm
>     understanding https://tools.ietf.org/html/rfc3205 (BCP 56).
>
>     I'm happy to clear when the edit happens, but not happy to charter
> work on
>     transport protocols outside TSV by accident.
>
>     My position on the previous ballot is at
>     https://datatracker.ietf.org/doc/charter-ietf-mile/ballot/630408/.
>
>
>
>
>     _______________________________________________
>     mile mailing list
>     mile@ietf.org
>     https://www.ietf.org/mailman/listinfo/mile
>
>
>

v2.23.0 | Report a Bug | By Email