
From nobody Mon Feb  1 21:56:26 2016
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: dispatch@ietf.org
Delivered-To: dispatch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E24C1A8787; Mon,  1 Feb 2016 21:55:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160202055538.24060.52573.idtracker@ietfa.amsl.com>
Date: Mon, 01 Feb 2016 21:55:38 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/VfjEHjEW8w7x5Lulu_sVs736sOY>
Cc: dispatch@ietf.org, dispatch-chairs@ietf.org
Subject: [dispatch] Spencer Dawkins' Yes on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 05:55:38 -0000

Spencer Dawkins has entered the following ballot position for
charter-ietf-dispatch-02-00: Yes

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-dispatch/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Given this,

"Options for handling new work include:

"- By agreement with ART ADs, processing simple documents."

and this: 

"The DISPATCH WG will not do any
protocol work. Specifically, DISPATCH will always opt to find a location
for technical work; the only work that DISPATCH is not required to
delegate (or defer, or reject) is administrative work such as IANA
actions."

If these are describing the same thing, I'd suggest replacing "simple"
with "administrative", which I'm reading as more restrictive. Having
"simple" being undefined in this context seems vulnerable to mischief
("of course, my document is simple, so it's within charter, right?").

If they aren't describing the same thing, I'd suggest defining "simple".



From nobody Wed Feb  3 13:51:06 2016
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 666EB1B2D6A; Wed,  3 Feb 2016 13:51:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 G-usGmdMWZNu; Wed,  3 Feb 2016 13:51:01 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 2F31D1B2F83; Wed,  3 Feb 2016 13:51:01 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u13LowBo062399 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 3 Feb 2016 15:50:58 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
Date: Wed, 03 Feb 2016 15:50:58 -0600
Message-ID: <6C95A03F-C159-4252-BC57-301D2103D511@nostrum.com>
In-Reply-To: <20160202055538.24060.52573.idtracker@ietfa.amsl.com>
References: <20160202055538.24060.52573.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5213)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/_eEBpMOOj7KpQ8-xYA5vo2VzCe0>
Cc: dispatch@ietf.org, The IESG <iesg@ietf.org>, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Spencer Dawkins' Yes on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 21:51:02 -0000

On 1 Feb 2016, at 23:55, Spencer Dawkins wrote:

>
> Given this,
>
> "Options for handling new work include:
>
> "- By agreement with ART ADs, processing simple documents."
>
> and this:
>
> "The DISPATCH WG will not do any
> protocol work. Specifically, DISPATCH will always opt to find a 
> location
> for technical work; the only work that DISPATCH is not required to
> delegate (or defer, or reject) is administrative work such as IANA
> actions."
>
> If these are describing the same thing,

I believe they are describing the same thing. (Although "simple" may be 
somewhat tainted by SIMPLE. :-)  )

> I'd suggest replacing "simple"
> with "administrative", which I'm reading as more restrictive. Having
> "simple" being undefined in this context seems vulnerable to mischief
> ("of course, my document is simple, so it's within charter, right?").
>

Such mischief would require AD agreement by the current wording :-) But, 
how about "simple administrative documents"?

> If they aren't describing the same thing, I'd suggest defining 
> "simple".

Thanks!

Ben.


From nobody Wed Feb  3 14:02:22 2016
Return-Path: <barryleiba@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B34C1B3599; Wed,  3 Feb 2016 14:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 1fyY-xEyAudp; Wed,  3 Feb 2016 14:02:16 -0800 (PST)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::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 4AAD11B2DBE; Wed,  3 Feb 2016 14:02:16 -0800 (PST)
Received: by mail-ig0-x22a.google.com with SMTP id 5so47447705igt.0; Wed, 03 Feb 2016 14:02:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OqZ+xETHoN12GR4TsYO1fOJE4OSDsuUbnKD8PHNX6gc=; b=Dp5M/AAkIGfk+GWak/1pwIAMI035icQBwHzmyLSXTH9cYuXj4Ibib0RWkeu2XF2CSu WR458nrv4gyUTK5L/eCVAPShLq6kTmZbrNxGm5OSvvySvgfAyfrxEMbdY8UbUnpSklvB IH9kKqi3y5ILH2o1esYA7z6TZcrXcXVNpaN1yEUS1W9eKTs5heoER1JW0PKnyPXj++pF BSuKs99NaA+ycpbo3pt4mdr5O9uiH1ImWGRs7gV8FY4BGc3ZGkABrDkvGTsFnKklVpW5 GLc6U5+pRFBH7Xd9r1UVKiCOjomtmrK11YqutvVw5O8/wGYOyApBFmA0GSalEQ4RH4rs 79Ig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=OqZ+xETHoN12GR4TsYO1fOJE4OSDsuUbnKD8PHNX6gc=; b=jfx8FuBpEdXlq6KrvpZpTwkB2Cc1S+DBzkgvq8hBzZjM7njuaEf75Ko3D2ZVVHD2Zu 4+VI4xqKKPCyQfM4WdN0QxKSDJKxzOivxGrCPeASjv39Z6UqurUHb/AfvyKsqbblodMm p2uSpCFa4wlCqz9uncx7rqy7Y2I+kQD+SEuvkH29Q0Wsnk6tMxOZ+dA9dRIl8UxuhNM/ y0jdW5OXDcB/XbSui95hbK7IzSppXt8DcNhwxzagoc4NDYWsfqF71Oc0HGqy18q+Fgdv bXu/l59hfOXoQq/MXoWE4IdBCaSqEiKGVk0btPuspYSCZzhsKvTgaSQ4Wmddrs4qWtc8 O4/Q==
X-Gm-Message-State: AG10YOTh4PJi0cDy4vsjqqUs8nEZKS3WNcHIgs3+UCxrk1T37t2v4Z1qHmBPxzrukVk6IpmHv3aYNJCAz9qHmQ==
MIME-Version: 1.0
X-Received: by 10.50.138.72 with SMTP id qo8mr5887155igb.81.1454536935709; Wed, 03 Feb 2016 14:02:15 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.36.155.198 with HTTP; Wed, 3 Feb 2016 14:02:15 -0800 (PST)
In-Reply-To: <6C95A03F-C159-4252-BC57-301D2103D511@nostrum.com>
References: <20160202055538.24060.52573.idtracker@ietfa.amsl.com> <6C95A03F-C159-4252-BC57-301D2103D511@nostrum.com>
Date: Wed, 3 Feb 2016 17:02:15 -0500
X-Google-Sender-Auth: Juvr6Gvmzsq9-hUma4kVwWBNhnY
Message-ID: <CALaySJK_h7ghbKtH8Pj30_a++NFTgnxeh1_McPonfv=4r1xyFA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/Nn3X2hEZl04cjfDGGfjZXpHlNcY>
Cc: dispatch@ietf.org, dispatch-chairs@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [dispatch] Spencer Dawkins' Yes on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 22:02:17 -0000

>> I'd suggest replacing "simple"
>> with "administrative", which I'm reading as more restrictive. Having
>> "simple" being undefined in this context seems vulnerable to mischief
>> ("of course, my document is simple, so it's within charter, right?").
>
> Such mischief would require AD agreement by the current wording :-) But, how
> about "simple administrative documents"?

Yes, I prefer keeping "simple" and adding "administrative".  Not *all*
administrative documents will qualify.

I also prefer, with this change, to leave "simple" vague.  See Potter Stewart.

Barry


From nobody Wed Feb  3 22:36:54 2016
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEC291A92B1; Wed,  3 Feb 2016 22:36:51 -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, SPF_PASS=-0.001] autolearn=ham
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 2S9zP9cixE_4; Wed,  3 Feb 2016 22:36:50 -0800 (PST)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (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 57A771A92B0; Wed,  3 Feb 2016 22:36:50 -0800 (PST)
Received: by mail-yw0-x234.google.com with SMTP id h129so20684132ywb.1; Wed, 03 Feb 2016 22:36:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=w30D3F/GZh6c9sZv/UydrjgzftKq3kZUtshtCi9DXio=; b=OVIhC2EnIyhaBULkj5ecip0shOl+rsLxY4jipYDV/Pul6y9nmauZSqL1ZVDGul0lNe fXJg/8+dW+WwPLM4DcLeFcW9ROqBlf6CF8hV9GCUb4IMYgLZubOIxn8KK9S6Mf7TPvFx fvYJwJwgCFianCOaEVWQxdA9sdWO0zsNLH7G1Bd1gZ3cbD1/IyxBplaGbTgY+uSlXBrw MOWTlWgqEbVxJYEgqGJvAz4zgLDOVEzS4SwDOf+SUQ69ugyEcmYxAojk4CHYAxGDpDak AfSwCU4iL+9xvwytUcjNFSYRm3T+Hcfw+wZkx5X16hIiVXOk6D6csZwx0lAEdUNaXkfO NlVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=w30D3F/GZh6c9sZv/UydrjgzftKq3kZUtshtCi9DXio=; b=bXZFgt0pj6bXeMXsYLjCd3ATDgOtd56qveIK3ZbbuBoalwbNFXnGcEBDMmZLwbWGDp JTN/u3DzcrzcZLV+t3vgYyPEdFbb47Q9orb7OR2+Pzfi1KM29vSrW3hZ6F331OR3/q8i kBmmYCjNxEzuVUOPw9xcvaD76OGGNEaT120gHwBPMxhi9MLbfgsWsNAq0MHws3Sltg34 Cfv1hew/YcyI+FyV0D+JCCLahylpmHCLq1Ic4H0J5n6YJ/yiZ1OnL8k0pX+WqzNZ47X+ fyCMDWX6+FBw1yN0MqWtN2Kwp99MOhMmge8ZlB/gX2yj24PY9JJ2cZA1ZMk0+pHoKfMM TkIA==
X-Gm-Message-State: AG10YOTew7XSNyaRRIzGYEnzMKnPeMyYEjbW4q21Tbqj2XB/nISCkL9WdHeFMDICS4O49vkawh+HaHNbCFcQTQ==
MIME-Version: 1.0
X-Received: by 10.13.210.7 with SMTP id u7mr2877985ywd.100.1454567809606; Wed, 03 Feb 2016 22:36:49 -0800 (PST)
Received: by 10.37.99.65 with HTTP; Wed, 3 Feb 2016 22:36:49 -0800 (PST)
In-Reply-To: <CALaySJK_h7ghbKtH8Pj30_a++NFTgnxeh1_McPonfv=4r1xyFA@mail.gmail.com>
References: <20160202055538.24060.52573.idtracker@ietfa.amsl.com> <6C95A03F-C159-4252-BC57-301D2103D511@nostrum.com> <CALaySJK_h7ghbKtH8Pj30_a++NFTgnxeh1_McPonfv=4r1xyFA@mail.gmail.com>
Date: Thu, 4 Feb 2016 00:36:49 -0600
Message-ID: <CAKKJt-drKj7UVpzmGGjWov8zA886Lj=avkCZg_4idjOhLU+JbA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=001a114e7e7897ee4b052aebf502
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/gu4ka0jqrJirnyEA_0lKGG5FHwI>
Cc: Ben Campbell <ben@nostrum.com>, DISPATCH <dispatch@ietf.org>, The IESG <iesg@ietf.org>, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Spencer Dawkins' Yes on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 06:36:51 -0000

--001a114e7e7897ee4b052aebf502
Content-Type: text/plain; charset=UTF-8

On Wed, Feb 3, 2016 at 4:02 PM, Barry Leiba <barryleiba@computer.org> wrote:

> >> I'd suggest replacing "simple"
> >> with "administrative", which I'm reading as more restrictive. Having
> >> "simple" being undefined in this context seems vulnerable to mischief
> >> ("of course, my document is simple, so it's within charter, right?").
> >
> > Such mischief would require AD agreement by the current wording :-) But,
> how
> > about "simple administrative documents"?
>
> Yes, I prefer keeping "simple" and adding "administrative".  Not *all*
> administrative documents will qualify.
>
> I also prefer, with this change, to leave "simple" vague.  See Potter
> Stewart.


This all works for me, and thank you.

Spencer

--001a114e7e7897ee4b052aebf502
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Wed, Feb 3, 2016 at 4:02 PM, Barry Leiba <span dir=3D"ltr">&lt;<a href=
=3D"mailto:barryleiba@computer.org" target=3D"_blank">barryleiba@computer.o=
rg</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""=
>&gt;&gt; I&#39;d suggest replacing &quot;simple&quot;<br>
&gt;&gt; with &quot;administrative&quot;, which I&#39;m reading as more res=
trictive. Having<br>
&gt;&gt; &quot;simple&quot; being undefined in this context seems vulnerabl=
e to mischief<br>
&gt;&gt; (&quot;of course, my document is simple, so it&#39;s within charte=
r, right?&quot;).<br>
&gt;<br>
&gt; Such mischief would require AD agreement by the current wording :-) Bu=
t, how<br>
&gt; about &quot;simple administrative documents&quot;?<br>
<br>
</span>Yes, I prefer keeping &quot;simple&quot; and adding &quot;administra=
tive&quot;.=C2=A0 Not *all*<br>
administrative documents will qualify.<br>
<br>
I also prefer, with this change, to leave &quot;simple&quot; vague.=C2=A0 S=
ee Potter Stewart.</blockquote><div><br></div><div>This all works for me, a=
nd thank you.</div><div><br></div><div>Spencer=C2=A0</div></div></div></div=
>

--001a114e7e7897ee4b052aebf502--


From nobody Thu Feb  4 01:45:16 2016
Return-Path: <a.james.winterbottom@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 102B71A6EE2 for <dispatch@ietfa.amsl.com>; Thu,  4 Feb 2016 01:45:14 -0800 (PST)
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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 KY7U4s_W3yg9 for <dispatch@ietfa.amsl.com>; Thu,  4 Feb 2016 01:45:11 -0800 (PST)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::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 85B111A6EE0 for <dispatch@ietf.org>; Thu,  4 Feb 2016 01:45:11 -0800 (PST)
Received: by mail-pf0-x232.google.com with SMTP id o185so39613272pfb.1 for <dispatch@ietf.org>; Thu, 04 Feb 2016 01:45:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=i5WiTE0ubcN8jTertQ0XvI/EJmUXEozTEjUjdPw5OQ4=; b=pZnMDgO+MtysQvAakjGIg9/PcBdxnHRwg4AUGFtRHxA6EeLds63yAsKDCaq1IWoLzI MguvgQnbAQXcBdtlUjnf/F8LhCLK467zXbtm/s5IJ413q/HlZ288obc+KKr3WNcYUuwy 7gwh/KefNF9zvvMY1YyjZpzNaJciUNnMO0Ul6EO0tUbiyhsZDGkrQ8khQI8pnlm+S5KQ k2UaZq4lyVz/srQstYQGdGkGeAKkvzdHEPyvB5O4/KgWjpqibbnZIZHwOEkDmwsGnSvj 9hz/Eh85AAZRqic/JlZs3UPmT0NRTbbd93uAQmPeuwu05g295QfMRjo08kGup26XvVAN 3tzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=i5WiTE0ubcN8jTertQ0XvI/EJmUXEozTEjUjdPw5OQ4=; b=B5sLKTOVKEsthLlrZQNmoba8gIpRvwAW0jsAOWTGaIDsj6fEB/khrP9KvjRWspThgX bAWuxA/1aw3A+h67YfjXjBlBN15uHwkVPe6V8s0SBmbwYH9kYGlV20v05kZSLVa758na 8RVJvEwneXvrPc1Sx1PFuS0fa73VmBxY5YATp+8qvTRz0QvXqgggpPQzfRVMAzXAUloD DzkeWyZwl9Id5WJSgCg1ZBheY1/7mIl3Jv/ZFpZG+tehRWPPT/4hS683yJdgCsU9MALa +Bs0x7rhP7Zb6Ug1v1eIplzaQVX+G/Mcf2+OTT+VcCFoOoRveMGBH7nEVZNZjSSSbfef ZwRw==
X-Gm-Message-State: AG10YOR7ufQT9KMoNqSYDfo41h5+dG3rf9JT4KGKOU/tG6FmFzJ5mduJq/+keoNZSaiBhA==
X-Received: by 10.98.14.69 with SMTP id w66mr9613798pfi.144.1454579111206; Thu, 04 Feb 2016 01:45:11 -0800 (PST)
Received: from [192.168.1.100] ([1.144.0.29]) by smtp.gmail.com with ESMTPSA id tp3sm15712286pac.16.2016.02.04.01.45.09 for <dispatch@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 04 Feb 2016 01:45:10 -0800 (PST)
From: James Winterbottom <a.james.winterbottom@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <A3A8B6D2-7664-45B3-B740-DA345B5DFF81@gmail.com>
Date: Thu, 4 Feb 2016 20:45:06 +1100
To: DISPATCH list <dispatch@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/wIUkc_zGknCcw7b2AJ9o97w7e3Y>
Subject: [dispatch] draft-winterbottom-dispatch-locparam-01
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 09:45:14 -0000

Hi All,

I was asked to make some updates to this document so that it could be =
dispatched.
I made, what I think were the requested updates back in December and =
posted to the list but I haven=E2=80=99t heard anything back.
ETSI needs this work as part of their M/493 stage-3 document so if there =
are further comments could they please be posted, otherwise can we =
please call for it to be dispatched somewhere?

Cheers
James


From nobody Thu Feb  4 01:59:37 2016
Return-Path: <bclaise@cisco.com>
X-Original-To: dispatch@ietf.org
Delivered-To: dispatch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE531A6EF4; Thu,  4 Feb 2016 01:59:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160204095936.4820.82987.idtracker@ietfa.amsl.com>
Date: Thu, 04 Feb 2016 01:59:36 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/VvVYlt1gTSOOLaq0iPYTgpXGnkc>
Cc: dispatch@ietf.org, dispatch-chairs@ietf.org
Subject: [dispatch] Benoit Claise's No Record on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 09:59:36 -0000

Benoit Claise has entered the following ballot position for
charter-ietf-dispatch-02-00: No Record

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-dispatch/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

(*)  Disclaimer: I've not been following RAI/ART work in the IETF and I
don't know whether the DISPATCH process has been efficient or not. So
I'll mainly make observations.

I understand Harald's point,
https://mailarchive.ietf.org/arch/msg/ietf/-kiAbvZDTCLets4szoXmaCIgrs4,
When I read the charter, it's like an extra procedure, specific to ART.
For example, if I want a BoF, I must first go to DISPATCH to get their
approval? Same thing for AD-sponsored document?

    The Dispatch working group is chartered to consider proposals for
new
    work in the ART area and identify, or help create, an appropriate
venue
    for the work.

Btw, no change here: this sentence is basically unchanged compared to the
previous charter.

In the past, I was told that DISPATCH was similar to the OPSAWG WG.
Let me observe it's not. "The DISPATCH WG will not do any protocol work",
while OPSAWG might.
>From the OPSAWG charter:

    The Operations and Management Area receives occasional proposals for
    the development and publication of RFCs dealing with operational and
    management topics that are not in scope of an existing working group
    and do not justify the formation of a new working group. The OPSAWG
    will serve as the forum for developing such work items in the IETF.

Obviously, redirecting work to existing WGs is also an OPSAWG task.
And when the work is substantial, a new WG can even be created. Ex: EMAN 
in the past

I prefer the OPSAWG approach (*).



From nobody Thu Feb  4 02:37:38 2016
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B171E1A6F81; Thu,  4 Feb 2016 02:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 sx60GSAeEZmm; Thu,  4 Feb 2016 02:37:32 -0800 (PST)
Received: from mail-yk0-x232.google.com (mail-yk0-x232.google.com [IPv6:2607:f8b0:4002:c07::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 175BF1A6F80; Thu,  4 Feb 2016 02:37:32 -0800 (PST)
Received: by mail-yk0-x232.google.com with SMTP id z13so38986056ykd.0; Thu, 04 Feb 2016 02:37:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pVitNin79V2X6uE+PPX5DQgjOFDYAJ5bcBwbOi8M2xw=; b=D/puwJKKx87jw/oHsy6vx3tv27RBnoGjlso04hJgLmPsnDUJ9UUu5asbiQtkPLC0nI O8vQjCu5zK/8cOgrOfZAhh3JV0OifAGwzSeMoNd0xegrePwOEQarKTTEw03P1A25Wryv 6CCayugzS7mTfjO4zJKOuXMBeHgpqOq+7QhlOCvLpwQyGV2WsEoshgQst0Sl3/iuP7v3 +zSL2aBGd/5eWWhHQNqQmkR6W/iGY2uF+JQBaRum6Ej4BydMvNV6SQyuBmPJxAZCiLkQ pIVwUJOYCA9xj2X4sO3jGhxndFndmIfHObSggkFUip2gLfcz2MpDyzpA9geQqEzCqcoN aNRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pVitNin79V2X6uE+PPX5DQgjOFDYAJ5bcBwbOi8M2xw=; b=GseiNNGPygj5HskSPem5ewvVo/zrTlRMiOIpICTmPZ6LvdyKaCgiH/foOJOrInQwLz DrgGwfpBJ3QL5AZTBbMvJb+YIWuxpxKeu4xUPNUF1dm6loqc8bHHOT9NgXqQb4z9yKb0 ijqHv30n8UtW13t2oDAKCjxNFE2GPRIHiEtIJ0+ABSsa/UjdoaPu//S7w5bDFxtXjkna kqTb1MaqLduBGWEpK0UbD/aRygrklYN9kqezUGhHjrbXPbEteZkCbUVxeFcJzYzZp6lx Om/wu1dbvjrkN0kpoIaV/pic7fHUClWIpI9QB4hHW35QlJ166TSKocggRhtBG8PVKzue w9Ug==
X-Gm-Message-State: AG10YOQY5HDJI0K7kJyXFxm+seDmKWGqTPBKrmEYjFiGtBP/zJkY5V7lLtmZwes3Ox+aoiz/OjtGTzqiZXHfPA==
MIME-Version: 1.0
X-Received: by 10.37.231.4 with SMTP id e4mr3377323ybh.143.1454582251354; Thu, 04 Feb 2016 02:37:31 -0800 (PST)
Received: by 10.37.110.196 with HTTP; Thu, 4 Feb 2016 02:37:31 -0800 (PST)
In-Reply-To: <20160204095936.4820.82987.idtracker@ietfa.amsl.com>
References: <20160204095936.4820.82987.idtracker@ietfa.amsl.com>
Date: Thu, 4 Feb 2016 04:37:31 -0600
Message-ID: <CAHBDyN7huHGRkxOwsMPMBpZxzL3t0tWH1g6621_7DD1Y=E3LWg@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=94eb2c0b4eae6386f3052aef52e8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/eEbbJiAepvwCwYeDYU8dE_THv4c>
Cc: DISPATCH <dispatch@ietf.org>, The IESG <iesg@ietf.org>, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Benoit Claise's No Record on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 10:37:34 -0000

--94eb2c0b4eae6386f3052aef52e8
Content-Type: text/plain; charset=UTF-8

A few comments below [MB].

Mary.

On Thu, Feb 4, 2016 at 3:59 AM, Benoit Claise <bclaise@cisco.com> wrote:

> Benoit Claise has entered the following ballot position for
> charter-ietf-dispatch-02-00: No Record
>
> 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-dispatch/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> (*)  Disclaimer: I've not been following RAI/ART work in the IETF and I
> don't know whether the DISPATCH process has been efficient or not. So
> I'll mainly make observations.
>
[MB] You can see the history of all the work we have dispatched since the
WG was chartered:
https://trac.tools.ietf.org/wg/dispatch/trac/wiki/WikiStart
I can understand that folks that weren't involved in RAI prior to the
DISPATCH model might not understand the impact it has had on the area, but
previously we had the SIPPING WG that handled all the work that didn't fit
within existing WGs and it was chaotic and highly inefficient. [/MB]
[/MB]

>
> I understand Harald's point,
> https://mailarchive.ietf.org/arch/msg/ietf/-kiAbvZDTCLets4szoXmaCIgrs4,
>
[MB] You might want to read Alissa's response to that email as those
comments really aren't directly related to the process but rather the
protocols that were developed in the TSV and RAI area.  DISPATCH wasn't
intended to fix the protocols but rather to define a process and procedures
for changing the protocols and defining new protocols.
[/MB]

> When I read the charter, it's like an extra procedure, specific to ART.
> For example, if I want a BoF, I must first go to DISPATCH to get their
> approval? Same thing for AD-sponsored document?
>
[MB] No, it is not required that you go through DISPATCH for a Bof.  If
it's something for which it's clear that there would be wider interest than
the regular ART community, the regular Bof process is followed.  There's a
number of examples of that including RTCWEB and NETVC.  For AD sponsored,
yes, it goes through DISPATCH.
[/MB]

>
>     The Dispatch working group is chartered to consider proposals for
> new
>     work in the ART area and identify, or help create, an appropriate
> venue
>     for the work.
>
> Btw, no change here: this sentence is basically unchanged compared to the
> previous charter.
>
> In the past, I was told that DISPATCH was similar to the OPSAWG WG.
> Let me observe it's not. "The DISPATCH WG will not do any protocol work",
> while OPSAWG might.
>
[MB] I'm not sure who made that observation, but from what you've posted
below since the objective of DISPATCH was to not have any deliverables, I
don't see the similarity except at the highest level. [/MB]

> >From the OPSAWG charter:
>
>     The Operations and Management Area receives occasional proposals for
>     the development and publication of RFCs dealing with operational and
>     management topics that are not in scope of an existing working group
>     and do not justify the formation of a new working group. The OPSAWG
>     will serve as the forum for developing such work items in the IETF.
>
> Obviously, redirecting work to existing WGs is also an OPSAWG task.
> And when the work is substantial, a new WG can even be created. Ex: EMAN
> in the past
>
> I prefer the OPSAWG approach (*).
>
[MB] In one sense the RAI area had a WG similar to OPSAWG and that was the
SIPPING WG and it was a disaster - there was way too much coming into the
WG and work was very slow to complete. The model of chartering what we
sometimes call mini-WGs has proven to be significantly superior.  And, I
will note that I chaired SIPPING and have chaired DISPATCH since it was
chartered, so it wasn't how we managed the SIPPING WG, it was the fact that
there was just too much disparate work that was of interest to subsets of
individuals that made it quite chaotic. We also had a huge issue with WG
shopping in the RAI area prior to DISPATCH WG chartering.  We had one
document that was discussed in 3 separate WGs at a single meeting. [/MB]

--94eb2c0b4eae6386f3052aef52e8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">A few comments below [MB].=C2=A0<div><br></div><div>Mary.<=
/div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Feb =
4, 2016 at 3:59 AM, Benoit Claise <span dir=3D"ltr">&lt;<a href=3D"mailto:b=
claise@cisco.com" target=3D"_blank">bclaise@cisco.com</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:sol=
id;padding-left:1ex">Benoit Claise has entered the following ballot positio=
n for<br>
charter-ietf-dispatch-02-00: No Record<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://datatracker.ietf.org/doc/charter-ietf-dispatch/" rel=3D"=
noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/charter-ietf=
-dispatch/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
(*)=C2=A0 Disclaimer: I&#39;ve not been following RAI/ART work in the IETF =
and I<br>
don&#39;t know whether the DISPATCH process has been efficient or not. So<b=
r>
I&#39;ll mainly make observations.<br></blockquote><div>[MB] You can see th=
e history of all the work we have dispatched since the WG was chartered:</d=
iv><div><a href=3D"https://trac.tools.ietf.org/wg/dispatch/trac/wiki/WikiSt=
art">https://trac.tools.ietf.org/wg/dispatch/trac/wiki/WikiStart</a><br></d=
iv><div>I can understand that folks that weren&#39;t involved in RAI prior =
to the DISPATCH model might not understand the impact it has had on the are=
a, but previously we had the SIPPING WG that handled all the work that didn=
&#39;t fit within existing WGs and it was chaotic and highly inefficient. [=
/MB]=C2=A0</div><div>[/MB]</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex">
<br>
I understand Harald&#39;s point,<br>
<a href=3D"https://mailarchive.ietf.org/arch/msg/ietf/-kiAbvZDTCLets4szoXma=
CIgrs4" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.org/a=
rch/msg/ietf/-kiAbvZDTCLets4szoXmaCIgrs4</a>,<br></blockquote><div>[MB] You=
 might want to read Alissa&#39;s response to that email as those comments r=
eally aren&#39;t directly related to the process but rather the protocols t=
hat were developed in the TSV and RAI area.=C2=A0 DISPATCH wasn&#39;t inten=
ded to fix the protocols but rather to define a process and procedures for =
changing the protocols and defining new protocols.=C2=A0</div><div>[/MB]=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-styl=
e:solid;padding-left:1ex">
When I read the charter, it&#39;s like an extra procedure, specific to ART.=
<br>
For example, if I want a BoF, I must first go to DISPATCH to get their<br>
approval? Same thing for AD-sponsored document?<br></blockquote><div>[MB] N=
o, it is not required that you go through DISPATCH for a Bof.=C2=A0 If it&#=
39;s something for which it&#39;s clear that there would be wider interest =
than the regular ART community, the regular Bof process is followed.=C2=A0 =
There&#39;s a number of examples of that including RTCWEB and NETVC.=C2=A0 =
For AD sponsored, yes, it goes through DISPATCH. =C2=A0=C2=A0</div><div>[/M=
B]</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style=
:solid;padding-left:1ex">
<br>
=C2=A0 =C2=A0 The Dispatch working group is chartered to consider proposals=
 for<br>
new<br>
=C2=A0 =C2=A0 work in the ART area and identify, or help create, an appropr=
iate<br>
venue<br>
=C2=A0 =C2=A0 for the work.<br>
<br>
Btw, no change here: this sentence is basically unchanged compared to the<b=
r>
previous charter.<br>
<br>
In the past, I was told that DISPATCH was similar to the OPSAWG WG.<br>
Let me observe it&#39;s not. &quot;The DISPATCH WG will not do any protocol=
 work&quot;,<br>
while OPSAWG might.<br></blockquote><div>[MB] I&#39;m not sure who made tha=
t observation, but from what you&#39;ve posted below since the objective of=
 DISPATCH was to not have any deliverables, I don&#39;t see the similarity =
except at the highest level. [/MB]=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-co=
lor:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
&gt;From the OPSAWG charter:<br>
<br>
=C2=A0 =C2=A0 The Operations and Management Area receives occasional propos=
als for<br>
=C2=A0 =C2=A0 the development and publication of RFCs dealing with operatio=
nal and<br>
=C2=A0 =C2=A0 management topics that are not in scope of an existing workin=
g group<br>
=C2=A0 =C2=A0 and do not justify the formation of a new working group. The =
OPSAWG<br>
=C2=A0 =C2=A0 will serve as the forum for developing such work items in the=
 IETF.<br>
<br>
Obviously, redirecting work to existing WGs is also an OPSAWG task.<br>
And when the work is substantial, a new WG can even be created. Ex: EMAN<br=
>
in the past<br>
<br>
I prefer the OPSAWG approach (*).<br></blockquote><div>[MB] In one sense th=
e RAI area had a WG similar to OPSAWG and that was the SIPPING WG and it wa=
s a disaster - there was way too much coming into the WG and work was very =
slow to complete. The model of chartering what we sometimes call mini-WGs h=
as proven to be significantly superior.=C2=A0 And, I will note that I chair=
ed SIPPING and have chaired DISPATCH since it was chartered, so it wasn&#39=
;t how we managed the SIPPING WG, it was the fact that there was just too m=
uch disparate work that was of interest to subsets of individuals that made=
 it quite chaotic. We also had a huge issue with WG shopping in the RAI are=
a prior to DISPATCH WG chartering.=C2=A0 We had one document that was discu=
ssed in 3 separate WGs at a single meeting. [/MB]=C2=A0</div></div><br></di=
v></div>

--94eb2c0b4eae6386f3052aef52e8--


From nobody Thu Feb  4 05:49:10 2016
Return-Path: <barryleiba@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25A361B2F94; Thu,  4 Feb 2016 05:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 MWTs4tAI6yR8; Thu,  4 Feb 2016 05:49:08 -0800 (PST)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (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 1C9601B2F99; Thu,  4 Feb 2016 05:49:08 -0800 (PST)
Received: by mail-ig0-x230.google.com with SMTP id 5so60747005igt.0; Thu, 04 Feb 2016 05:49:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=UcLcB2hDC8E8O1ei6wOAyYbcWYEFjnqb7Vv5iknOvmY=; b=wED4/KSbxDY23tZGsZwnvKhtkYp36aJ5ubvxMoyVmX7c851Gy/Y423rBZ3o6CxZ91Q 62DRNLV26jq0bbUb43DMBU/ganZ2RcolR+8tAB6E3ibpdN1pT044YIY6mDNYFNvlXisR 0rT2uSI22tahotNKpIDxo8OvtBbCfyktHH/veSKAhxh7riXX2/hb1mhhIH7NzRk7cGxM gz7C72f/eclzkkvjQdF79ITVOAvWCESPC1T5RdQk13yTDEi0dkeoRKEpvyTFTGI3ezJB jo4e7zzus7e58F6WWYlns9NXqG3DBLVqzXapCfSoq+n6aQdi6J8I/bqFHNy8m3kMTvre soGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=UcLcB2hDC8E8O1ei6wOAyYbcWYEFjnqb7Vv5iknOvmY=; b=liyQc72CBZwht/dBE0OWpf6qvKohbUe+ZI7X6cgxY93lbt9obvwqcWrig3uSlcCgKg bQUq2o4Q9HaXoQD8DbA1ampMjLE/1OHQL0f/CMy/MDHPVf44WsXYu79YFKH3V6JW1SSb WZX8IL9wukBh21ZUFs/LQJN1YHlxjzEPZjl1UsFr4ALkDN0WcYu+N9lez7r5MQyrcSn0 Aqd20DoiRcNwdSr7nPmEemtwtq+ZbM5BsEP5NypWwK9tR+LLV5+Uyu3268PqznALomz3 xsAlrSe+1VU5Okeiz0HXwZmEK5HHtTCOz9eecy5GmBpP6ID3G+5G71DAE59P9QRoDQZQ lHFA==
X-Gm-Message-State: AG10YORiydLrtzTT3oc5LnX66ki5ve461kB0zTxHdIOdVMY3z/lDd39lDvlkFbRs5VET4obG/bQIxFWllIESjQ==
MIME-Version: 1.0
X-Received: by 10.50.142.68 with SMTP id ru4mr10213846igb.54.1454593747537; Thu, 04 Feb 2016 05:49:07 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.36.156.5 with HTTP; Thu, 4 Feb 2016 05:49:07 -0800 (PST)
In-Reply-To: <CAHBDyN7huHGRkxOwsMPMBpZxzL3t0tWH1g6621_7DD1Y=E3LWg@mail.gmail.com>
References: <20160204095936.4820.82987.idtracker@ietfa.amsl.com> <CAHBDyN7huHGRkxOwsMPMBpZxzL3t0tWH1g6621_7DD1Y=E3LWg@mail.gmail.com>
Date: Thu, 4 Feb 2016 08:49:07 -0500
X-Google-Sender-Auth: kcsDzg1OMOKoY2IxtTYw8aTiTto
Message-ID: <CALaySJ+o-67H46q8OW5y074T3hQDysD92hq8zm8PbLmU-EUd-Q@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/gCqTHzz54RwBYNOGxBtg0AeQoMQ>
Cc: Benoit Claise <bclaise@cisco.com>, DISPATCH <dispatch@ietf.org>, The IESG <iesg@ietf.org>, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Benoit Claise's No Record on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 13:49:09 -0000

Adding briefly to what Mary said:

>> When I read the charter, it's like an extra procedure, specific to ART.
>> For example, if I want a BoF, I must first go to DISPATCH to get their
>> approval? Same thing for AD-sponsored document?
>
> [MB] No, it is not required that you go through DISPATCH for a Bof.  If it's
> something for which it's clear that there would be wider interest than the
> regular ART community, the regular Bof process is followed.

And I don't see anything in the charter text that implies that BoF
requests must go through DISPATCH.  DISPATCH is there to help if it's
needed/wanted.

> [MB] In one sense the RAI area had a WG similar to OPSAWG and that was the
> SIPPING WG and it was a disaster - there was way too much coming into the WG
> and work was very slow to complete. The model of chartering what we
> sometimes call mini-WGs has proven to be significantly superior.  And, I
> will note that I chaired SIPPING and have chaired DISPATCH since it was
> chartered, so it wasn't how we managed the SIPPING WG, it was the fact that
> there was just too much disparate work that was of interest to subsets of
> individuals that made it quite chaotic. We also had a huge issue with WG
> shopping in the RAI area prior to DISPATCH WG chartering.  We had one
> document that was discussed in 3 separate WGs at a single meeting. [/MB]

APPSAWG has also been similar to OPSAWG, and it worked well for some
documents... and failed badly for some others.  It has turned out that
having no clear structure for the work -- remember that there are a
lot of disparate topics handled by the former APP and RAI areas, and
now ART -- has meant that such a working group can have a lot of
trouble getting meaningful review for arbitrary protocol documents,
which often have a few proponents and lack broad interest.

Because of that, we think it's better to let DISPATCH form a home for
the work, and not try to manage the work directly.

Barry


From nobody Thu Feb  4 06:19:19 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: dispatch@ietf.org
Delivered-To: dispatch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2ED1B300D; Thu,  4 Feb 2016 06:19:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160204141918.18497.50701.idtracker@ietfa.amsl.com>
Date: Thu, 04 Feb 2016 06:19:18 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/n_0YLrhJcDuDYB7m63Aas4eLd6Y>
Cc: dispatch@ietf.org, dispatch-chairs@ietf.org
Subject: [dispatch] Stephen Farrell's No Objection on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 14:19:18 -0000

Stephen Farrell has entered the following ballot position for
charter-ietf-dispatch-02-00: No Objection

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-dispatch/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


A friendly amendment, if you're up for accepting it: I think a
change along these lines would better reflect what we hope
folks will be doing:

OLD:

5. Ensuring that the new work considers security and privacy.

NEW:

5. Ensuring that the new work considers and aims to improve
security and privacy.

My reason is that while we definitely do want to consider
security and privacy, I think we do have consensus to try to
make those better whenever we can, and to never just say
"yeah, we thought about it, but we're doing nothing." I think
it may be better if we can say that the DISPATCH charter
calls for improvement to handle cases where folks are a
bit reluctant to change a piece of work they bring to the
IETF that hasn't done such a good job on security or 
privacy.



From nobody Thu Feb  4 06:57:25 2016
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 906441B30CD; Thu,  4 Feb 2016 06:57:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 NJ1iQ6nfcr28; Thu,  4 Feb 2016 06:57:22 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 A44011B30CC; Thu,  4 Feb 2016 06:57:22 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u14EvKi9074609 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 4 Feb 2016 08:57:20 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: "Barry Leiba" <barryleiba@computer.org>
Date: Thu, 04 Feb 2016 08:57:20 -0600
Message-ID: <86008F04-2E37-450B-A644-444254565609@nostrum.com>
In-Reply-To: <CALaySJK_h7ghbKtH8Pj30_a++NFTgnxeh1_McPonfv=4r1xyFA@mail.gmail.com>
References: <20160202055538.24060.52573.idtracker@ietfa.amsl.com> <6C95A03F-C159-4252-BC57-301D2103D511@nostrum.com> <CALaySJK_h7ghbKtH8Pj30_a++NFTgnxeh1_McPonfv=4r1xyFA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5213)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/Ci8fizwPsSKmfUcP8wZLlTmEiRU>
Cc: The IESG <iesg@ietf.org>, dispatch@ietf.org, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Spencer Dawkins' Yes on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 14:57:23 -0000

On 3 Feb 2016, at 16:02, Barry Leiba wrote:

>>> I'd suggest replacing "simple"
>>> with "administrative", which I'm reading as more restrictive. Having
>>> "simple" being undefined in this context seems vulnerable to 
>>> mischief
>>> ("of course, my document is simple, so it's within charter, 
>>> right?").
>>
>> Such mischief would require AD agreement by the current wording :-) 
>> But, how
>> about "simple administrative documents"?
>
> Yes, I prefer keeping "simple" and adding "administrative".  Not *all*
> administrative documents will qualify.
>
> I also prefer, with this change, to leave "simple" vague.  See Potter 
> Stewart.
>

Done.

Thanks!

Ben.


From nobody Thu Feb  4 06:58:42 2016
Return-Path: <barryleiba@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2A221B30D6; Thu,  4 Feb 2016 06:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 liCgZwZlRDGs; Thu,  4 Feb 2016 06:58:39 -0800 (PST)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (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 D7A8A1B30C6; Thu,  4 Feb 2016 06:58:35 -0800 (PST)
Received: by mail-ig0-x22c.google.com with SMTP id mw1so60856035igb.1; Thu, 04 Feb 2016 06:58:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=UabOZcNhD4eFdNG4ZEigGHauNQn67OnnjPWKGD6w0Qk=; b=IM1wxjZ1x5DxO9EVecGT7CcC5HUhvPhm9Vjb+np40czlQKM7UknGQHBLaNzBE9xytE z24h1zKBC3t5JssUtieIxvYaSPNO9Vt9bnJ2popdp6EdCXFHPVmkM3GgvXGjJCQ4GSsq Fzvqvartiv+zbHuLP6BFqrHYBfqnbs0qAv4dUlvkTQC9awE+fTQ02T1E1twtciQe6zSd nlXHSLwmCrOyPFuKkBzTsD+YTWJAbn/Aa+hsTDB1Ed4XcrQYdwnwhg+A6wOqRJ1+R7rk jHS/lY81z6af1P025nqtkhvoOncNIjMi7QaXt/AondAaoijkw8egCAZ3KghKVGeDVHi+ 4ZZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=UabOZcNhD4eFdNG4ZEigGHauNQn67OnnjPWKGD6w0Qk=; b=eoiovitU8IukSWdg3oSEBZ317b8oEF6LtvJf842ejVDVolNUdHOLFVqkGoeY65fUn3 zoqt/HEvtSIXkpdvHI3Y9DA2kknvzRjLDQD7ljuj2rjxgrJm+TagBYphYyPvJpj/P+Sb fbYan4mDkGNly7SMmUOsZFLj3oA3/SwDE88KBU5bgp3MmU+YZuKNARX2d8jnqw8x4zAI MydfaPg/9nfpnXpXUjJdcT9Ou6cUlWl/Xppx+zPe65tqhcR8BjQ2/dENzIHveQUNauN1 cB/c4Aoku+xV/x7tNn72SJs2ZGa2n+3QeH0acLUn+qilxdr3VfxJFBv9R02kf6mJA/du xE/w==
X-Gm-Message-State: AG10YOSmCOl9MVElfgEGLwEgdCGHnzBPHDeGlAj3Luz0Vtgl3rVXoKVPvA+mjasfEZfMEiVEfuKKIwag7UcrTg==
MIME-Version: 1.0
X-Received: by 10.50.138.72 with SMTP id qo8mr9700739igb.81.1454597915261; Thu, 04 Feb 2016 06:58:35 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.36.156.5 with HTTP; Thu, 4 Feb 2016 06:58:35 -0800 (PST)
In-Reply-To: <20160204141918.18497.50701.idtracker@ietfa.amsl.com>
References: <20160204141918.18497.50701.idtracker@ietfa.amsl.com>
Date: Thu, 4 Feb 2016 09:58:35 -0500
X-Google-Sender-Auth: pH-unS2Nj7tVx0aLn0TXZfqhJRo
Message-ID: <CALaySJJpz35QWjreF5GuWp8Qcu3cchqiM_0hOT9Sb3ApTZHCdg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/mK5h-9ADAfzgqk_FaGyX9fD9gbw>
Cc: DISPATCH <dispatch@ietf.org>, The IESG <iesg@ietf.org>, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Stephen Farrell's No Objection on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 14:58:41 -0000

I'm happy with that.

b

On Thu, Feb 4, 2016 at 9:19 AM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
> Stephen Farrell has entered the following ballot position for
> charter-ietf-dispatch-02-00: No Objection
>
> 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-dispatch/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
>
> A friendly amendment, if you're up for accepting it: I think a
> change along these lines would better reflect what we hope
> folks will be doing:
>
> OLD:
>
> 5. Ensuring that the new work considers security and privacy.
>
> NEW:
>
> 5. Ensuring that the new work considers and aims to improve
> security and privacy.
>
> My reason is that while we definitely do want to consider
> security and privacy, I think we do have consensus to try to
> make those better whenever we can, and to never just say
> "yeah, we thought about it, but we're doing nothing." I think
> it may be better if we can say that the DISPATCH charter
> calls for improvement to handle cases where folks are a
> bit reluctant to change a piece of work they bring to the
> IETF that hasn't done such a good job on security or
> privacy.
>
>


From nobody Thu Feb  4 07:39:36 2016
Return-Path: <bclaise@cisco.com>
X-Original-To: dispatch@ietf.org
Delivered-To: dispatch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D22481B318E; Thu,  4 Feb 2016 07:39:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160204153934.14557.85409.idtracker@ietfa.amsl.com>
Date: Thu, 04 Feb 2016 07:39:34 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/VkAYmFMAI617PU7q6oPD6ouk0ik>
Cc: dispatch@ietf.org, dispatch-chairs@ietf.org
Subject: [dispatch] Benoit Claise's No Objection on charter-ietf-dispatch-02-01: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 15:39:35 -0000

Benoit Claise has entered the following ballot position for
charter-ietf-dispatch-02-01: No Objection

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-dispatch/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I received the necessary clarifications from both Barry and Ben during
the IESG telechat. Thanks, Benoit
=============================================================================


(*)  Disclaimer: I've not been following RAI/ART work in the IETF and I
don't know whether the DISPATCH process has been efficient or not. So
I'll mainly make observations.

I understand Harald's point,
https://mailarchive.ietf.org/arch/msg/ietf/-kiAbvZDTCLets4szoXmaCIgrs4,
When I read the charter, it's like an extra procedure, specific to ART.
For example, if I want a BoF, I must first go to DISPATCH to get their
approval? Same thing for AD-sponsored document?

    The Dispatch working group is chartered to consider proposals for
new
    work in the ART area and identify, or help create, an appropriate
venue
    for the work.

Btw, no change here: this sentence is basically unchanged compared to the
previous charter.

In the past, I was told that DISPATCH was similar to the OPSAWG WG.
Let me observe it's not. "The DISPATCH WG will not do any protocol work",
while OPSAWG might.
>From the OPSAWG charter:

    The Operations and Management Area receives occasional proposals for
    the development and publication of RFCs dealing with operational and
    management topics that are not in scope of an existing working group
    and do not justify the formation of a new working group. The OPSAWG
    will serve as the forum for developing such work items in the IETF.

Obviously, redirecting work to existing WGs is also an OPSAWG task.
And when the work is substantial, a new WG can even be created. Ex: EMAN 
in the past

I prefer the OPSAWG approach (*).



From nobody Thu Feb  4 08:40:55 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4190D1B328F for <dispatch@ietfa.amsl.com>; Thu,  4 Feb 2016 08:40:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 xOqU8hmclM_G for <dispatch@ietfa.amsl.com>; Thu,  4 Feb 2016 08:40:53 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF1C31A1A70 for <dispatch@ietf.org>; Thu,  4 Feb 2016 08:40:52 -0800 (PST)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-06v.sys.comcast.net with comcast id EGeo1s0032TL4Rh01GgsDN; Thu, 04 Feb 2016 16:40:52 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-17v.sys.comcast.net with comcast id EGgr1s00a3KdFy101GgrjD; Thu, 04 Feb 2016 16:40:52 +0000
To: dispatch@ietf.org
References: <A3A8B6D2-7664-45B3-B740-DA345B5DFF81@gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <56B37F12.2040802@alum.mit.edu>
Date: Thu, 4 Feb 2016 11:40:50 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <A3A8B6D2-7664-45B3-B740-DA345B5DFF81@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1454604052; bh=x6EihsMxsn4ggFK2oaj7oidd5BPju/g9ejyOitJCwLs=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=t9H8rizhYMezR+RanU4jArRxlMsWJ4h4NHjnGo2cTMI3i1eRf4EL4eFaZBwOzMSU7 S0mfef2g3a4OnO/D9Vlpe5KMVT2uWDJE2gQ6OKeHUNEN0zgA6shREBVyXvE9W7S8SS uyT9W5FYxYfhSYizKfEECY65fJ1Up1rFkDHetepelNguEWsdEnjrHK3BAT10DzJRlC VD5c1dnkHd/G5lzbvdUP1V79w5j2vGVQDOYBDKg0kdBfQ69pn+r8B+gTFfsAzUozdn 4eSICkD+bd53mNcTByzlmXdDGgMwQPrVGlDOwB8s0ifGTGri1jjMlnB5JR1U7G0T0C BANXXRbZVJ/Qg==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/pqxQL9sik_Nj-hxr7M2mXTsmsj4>
Subject: Re: [dispatch] draft-winterbottom-dispatch-locparam-01
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 16:40:54 -0000

The updates were intended to address my comments. And indeed they do. 
I'm ok with this now.

	Thanks,
	Paul

On 2/4/16 4:45 AM, James Winterbottom wrote:
> Hi All,
>
> I was asked to make some updates to this document so that it could be dispatched.
> I made, what I think were the requested updates back in December and posted to the list but I haven’t heard anything back.
> ETSI needs this work as part of their M/493 stage-3 document so if there are further comments could they please be posted, otherwise can we please call for it to be dispatched somewhere?
>
> Cheers
> James
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>


From nobody Fri Feb  5 00:31:16 2016
Return-Path: <ogud@ogud.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 402461B3406 for <dispatch@ietfa.amsl.com>; Thu,  4 Feb 2016 15:31:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.801
X-Spam-Level: 
X-Spam-Status: No, score=0.801 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_EXTRA_CLOSE=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
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 qJBaAlLSjyi8 for <dispatch@ietfa.amsl.com>; Thu,  4 Feb 2016 15:31:25 -0800 (PST)
Received: from smtp80.iad3a.emailsrvr.com (smtp80.iad3a.emailsrvr.com [173.203.187.80]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EE801B3405 for <dispatch@ietf.org>; Thu,  4 Feb 2016 15:31:23 -0800 (PST)
Received: from smtp3.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp3.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 309FB3005D5; Thu,  4 Feb 2016 18:31:23 -0500 (EST)
Received: from app41.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by smtp3.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 24B1F300223; Thu,  4 Feb 2016 18:31:23 -0500 (EST)
X-Sender-Id: ogud@ogud.com
Received: from app41.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by 0.0.0.0:25 (trex/5.5.4); Thu, 04 Feb 2016 18:31:23 -0500
Received: from ogud.com (localhost.localdomain [127.0.0.1]) by app41.wa-webapps.iad3a (Postfix) with ESMTP id 129A0280041; Thu,  4 Feb 2016 18:31:23 -0500 (EST)
Received: by apps.rackspace.com (Authenticated sender: ogud@ogud.com, from: ogud@ogud.com)  with HTTP; Thu, 4 Feb 2016 18:31:23 -0500 (EST)
Date: Thu, 4 Feb 2016 18:31:23 -0500 (EST)
From: "Olafur Gudmundsson" <ogud@ogud.com>
To: secdir@ietf.org, "IETF DNSOP WG" <dnsop@ietf.org>, dispatch@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_20160204183123000000_67968"
Importance: Normal
X-Priority: 3 (Normal)
X-Type: html
X-Auth-ID: ogud@ogud.com
Message-ID: <1454628683.073614898@apps.rackspace.com>
X-Mailer: webmail/12.0.0-RC
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/H71S7UX7hkGrELLooWkRRiZWYvA>
X-Mailman-Approved-At: Fri, 05 Feb 2016 00:31:14 -0800
Subject: [dispatch] SecDIr review:  draft-holmberg-dispatch-pani-abnf-02
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 23:31:26 -0000

------=_20160204183123000000_67968
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=0AI have reviewed this document as part of the security directorate's ongo=
ing effort to review all IETF documents being processed by the IESG.  These=
 comments were written primarily for the benefit of the security area direc=
tors.  Document editors and WG chairs should treat these comments just like=
 any other last call comments.=0A=0AThe document is short and to the point,=
 it has no security issues and is ready for publication. =0A=0AOlafur=0A=0A
------=_20160204183123000000_67968
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<font face=3D"arial" size=3D"2"><p class=3D"wiki" style=3D"margin:0;padding=
:0;background-color: #f7f7f7; border: 1px solid #d7d7d7; margin-right: 1.75=
em; margin-left: 1.75em; padding: 0.25em; overflow: auto; font-size: 15px;"=
>I have reviewed this document as part of the security directorate's =0Aong=
oing effort to review all IETF documents being processed by the =0AIESG.  T=
hese comments were written primarily for the benefit of the =0Asecurity are=
a directors.  Document editors and WG chairs should treat =0Athese comments=
 just like any other last call comments.<br /><br />The document is short a=
nd to the point, it has no security issues and is ready for publication. <b=
r /><br />Olafur<br /><br /></pre></font>
------=_20160204183123000000_67968--


From nobody Fri Feb  5 18:08:42 2016
Return-Path: <a.james.winterbottom@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DBB61A00C3 for <dispatch@ietfa.amsl.com>; Fri,  5 Feb 2016 18:08:42 -0800 (PST)
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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 FnFtdxnW2oib for <dispatch@ietfa.amsl.com>; Fri,  5 Feb 2016 18:08:40 -0800 (PST)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (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 951E11A005A for <dispatch@ietf.org>; Fri,  5 Feb 2016 18:08:40 -0800 (PST)
Received: by mail-pf0-x22f.google.com with SMTP id o185so77967623pfb.1 for <dispatch@ietf.org>; Fri, 05 Feb 2016 18:08:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FOWEnRdMZutYbY5Mi+c/EE1m5/auVTdALRhGNN/FUag=; b=vsQKjAoxgiciHlxf4fnqz15HAZICp7jDfAd8W9gOP3CDATgJFQWyXpCw9jYkjW+7mh T1Jvxg2jyKHOUHfybeVV+48/NE20CNk3F7r9iKbaCcKM+3GfZKsX9Mr0pMWdSCvpwlog +GrRJp510R33KOGFpaaTnR4ca5kVhA6oMu99bRmdpzECmeJjILa2ephQVYqGE99q9jzP T7bmQs2CEXuZFU05HX82YuruprxVlGoSCVeDIWzWCpcyqsjsbFfcch7RT3lLf9QPDFDe iIPuFkYR9cZkz90flTy5U6XIgStBnQ09nm8Q7wC6GhgIsx04X634yRsTCOtL9W///Xjl MB6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=FOWEnRdMZutYbY5Mi+c/EE1m5/auVTdALRhGNN/FUag=; b=QS/UxEZWJrJWLAO7e8KjWrd4Y/FNgtu0U9zmQX26EZlAXnYPYS8D5wgvm4LjDGd2l6 Ko9Omuy4Drc37WOWyUVZCi6WFOKPv6UsF35BQSj19bOOTf7yk81f38jHZ5PHnIfbQ9NB ycBd08JaA0cydnqofMjE6inw3Q5N5p3/r3O4UKNVVnCwWKuKihHMKDiPLIPYcT0hVA/8 rX4qHzMjloSHU9KJOsGXg1QS07yFPTkyIVbhKhNg3+t5OlbQHUK3Cak4y5qN8iCZB8BV Kw5QHbBS98Ow+LRy9h0xFxShsarr9yvrzqnxeXkL11ULko/cf7AGZctm1Z6ZLie90ej7 OxWw==
X-Gm-Message-State: AG10YOS1dd039wUGs5I6FZo+D0T2vlaajArc9fH2Z8mEM2t5XMX+UCMtoRhHohUVob7NQw==
X-Received: by 10.98.66.157 with SMTP id h29mr24381084pfd.91.1454724520239; Fri, 05 Feb 2016 18:08:40 -0800 (PST)
Received: from [192.168.1.4] (124-171-30-137.dyn.iinet.net.au. [124.171.30.137]) by smtp.gmail.com with ESMTPSA id h89sm22854911pfj.52.2016.02.05.18.08.37 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Feb 2016 18:08:39 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: James Winterbottom <a.james.winterbottom@gmail.com>
In-Reply-To: <56B37F12.2040802@alum.mit.edu>
Date: Sat, 6 Feb 2016 13:08:35 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DCA7565-D04B-4209-93F1-A9F2991B27BB@gmail.com>
References: <A3A8B6D2-7664-45B3-B740-DA345B5DFF81@gmail.com> <56B37F12.2040802@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/ZTIxy2rhLYrTv2h0Ie1jKOtDrDk>
Cc: dispatch@ietf.org
Subject: Re: [dispatch] draft-winterbottom-dispatch-locparam-01
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Feb 2016 02:08:42 -0000

Thanks Paul.

What next is required to dispatch it?

Cheers
James


> On 5 Feb 2016, at 3:40 am, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> The updates were intended to address my comments. And indeed they do. =
I'm ok with this now.
>=20
> 	Thanks,
> 	Paul
>=20
> On 2/4/16 4:45 AM, James Winterbottom wrote:
>> Hi All,
>>=20
>> I was asked to make some updates to this document so that it could be =
dispatched.
>> I made, what I think were the requested updates back in December and =
posted to the list but I haven=E2=80=99t heard anything back.
>> ETSI needs this work as part of their M/493 stage-3 document so if =
there are further comments could they please be posted, otherwise can we =
please call for it to be dispatched somewhere?
>>=20
>> Cheers
>> James
>>=20
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>>=20
>=20
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


From nobody Sat Feb  6 07:58:10 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA0F1A1B1D for <dispatch@ietfa.amsl.com>; Sat,  6 Feb 2016 07:58:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 CFRAYez9bvky for <dispatch@ietfa.amsl.com>; Sat,  6 Feb 2016 07:58:07 -0800 (PST)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14F2F1A1AFF for <dispatch@ietf.org>; Sat,  6 Feb 2016 07:58:06 -0800 (PST)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-05v.sys.comcast.net with comcast id F3xR1s0022LrikM013y66G; Sat, 06 Feb 2016 15:58:06 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-12v.sys.comcast.net with comcast id F3y51s00D3KdFy1013y5bk; Sat, 06 Feb 2016 15:58:06 +0000
To: James Winterbottom <a.james.winterbottom@gmail.com>
References: <A3A8B6D2-7664-45B3-B740-DA345B5DFF81@gmail.com> <56B37F12.2040802@alum.mit.edu> <7DCA7565-D04B-4209-93F1-A9F2991B27BB@gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <56B6180D.5020409@alum.mit.edu>
Date: Sat, 6 Feb 2016 10:58:05 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <7DCA7565-D04B-4209-93F1-A9F2991B27BB@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1454774286; bh=/zP7dj92aWMSFo93xTqiaVknFjokies6cLfW/Kpu+SA=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=gR4gOwatb4rEC16cRCy+IOtZSE3iwk8AawTPbOmoXakuvgIVOSONS95cQa4i0NAqJ BnIPYyjDjr/DyzzNa9B+Y6FUgrc4fU4qkrNCTyn1L3dC4QcY52hygkjCdRtgTu/OrC /8LSf6/r6PPg3kEeCMX4Vw/ihFMjkOsXXPeDvAmyZf6UvcrxTq26B495yvWQQddwcG 0IxNgPF9AoFNsK5wePnzgTeFiyshVO2ivJyfMl9wVb/Y/9cBMZ2sEqbMZVLNKbv0s+ 4SQmZo8dy3U9BY2yI2WDG6n9FCjy+87CidGsaeeun7HeQ6wZZ0bmkODVi2+DdrZ/i+ GwpyCoxtgkUig==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/g4f3e7ObuIBopryQIjXz5_NCqg0>
Cc: dispatch@ietf.org
Subject: Re: [dispatch] draft-winterbottom-dispatch-locparam-01
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Feb 2016 15:58:09 -0000

On 2/5/16 9:08 PM, James Winterbottom wrote:
> Thanks Paul.
>
> What next is required to dispatch it?

That is a question for the chairs.

	Thanks,
	Paul

> Cheers
> James
>
>
>> On 5 Feb 2016, at 3:40 am, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>
>> The updates were intended to address my comments. And indeed they do. I'm ok with this now.
>>
>> 	Thanks,
>> 	Paul
>>
>> On 2/4/16 4:45 AM, James Winterbottom wrote:
>>> Hi All,
>>>
>>> I was asked to make some updates to this document so that it could be dispatched.
>>> I made, what I think were the requested updates back in December and posted to the list but I haven’t heard anything back.
>>> ETSI needs this work as part of their M/493 stage-3 document so if there are further comments could they please be posted, otherwise can we please call for it to be dispatched somewhere?
>>>
>>> Cheers
>>> James
>>>
>>> _______________________________________________
>>> dispatch mailing list
>>> dispatch@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dispatch
>>>
>>
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>
>


From nobody Mon Feb  8 13:57:19 2016
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8DC11B33CD for <dispatch@ietfa.amsl.com>; Mon,  8 Feb 2016 13:57:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, RP_MATCHES_RCVD=-0.001] autolearn=no
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 ISKcjSEmLMaO for <dispatch@ietfa.amsl.com>; Mon,  8 Feb 2016 13:57:14 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 E4ABE1B33D6 for <dispatch@ietf.org>; Mon,  8 Feb 2016 13:56:50 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u18LukuK019481 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 8 Feb 2016 15:56:47 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: "Nigel Weinronk" <Nigel.Weinronk@gamma.co.uk>, "dispatch@ietf.org" <dispatch@ietf.org>
Date: Mon, 08 Feb 2016 15:56:45 -0600
Message-ID: <3F4D2A04-2743-4EF1-80BC-8FDBD15723AC@nostrum.com>
In-Reply-To: <2FA3A1EB67D00349B9871E2A3841072D0117CA6E29@INF-EXCH-MB-02.gammatelecom.com>
References: <20150915120520.28650.89731.idtracker@ietfa.amsl.com> <2FA3A1EB67D00349B9871E2A3841072D0117CA6E29@INF-EXCH-MB-02.gammatelecom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.4r5213)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/__xwVQ4bpl7TmyqWcy2271I5PYE>
Subject: Re: [dispatch] New Version Notification for draft-weinronk-last-diverting-line-identity-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 21:57:16 -0000

Hi Everyone,

I'd like people to comment on the IANA registrations requested in this =

draft. I think it's likely this would have been an independent stream =

submission, but the privacy header field registration requires IETF =

review. The header field registration might require that as well, =

depending on the opinion of the expert reviewer.

Thanks!

Ben.

On 23 Jan 2016, at 6:21, Nigel Weinronk wrote:

> I have been advised to submit this draft =

> (draft-weinronk-last-diverting-line-identity-00.txt) to the DISPATCH =

> WG as it proposes a new SIP header - see below.
>
> This draft defines a new SIP header "Last-Diverting-Line-Identity" for =

> use where a Network Asserted Identity of the last diverted user is =

> needed by applications / services provided by a network that is not =

> the originating network.
>
> Your comments are welcome,
>
> Thanks,
> Nigel Weinronk
>
>
>
>
>      Nigel Weinronk
>      Design Engineer
>
> T:      0333 240 3421
> M:      07436 070 002
> E:      Nigel.Weinronk@gamma.co.uk
> W:      www.gamma.co.uk
>
> This is an email from Gamma Telecom Ltd, trading as =E2=80=9CGamma=E2=80=
=9D. The =

> contents of this email are confidential to the ordinary user of the =

> email address to which it was addressed. This email is not intended to =

> create any legal relationship. No one else may place any reliance upon =

> it, or copy or forward all or any of it in any form (unless otherwise =

> notified). If you receive this email in error, please accept our =

> apologies, we would be obliged if you would telephone our postmaster =

> on +44 (0) 808 178 9652 or email postmaster@gamma.co.uk
>
> Gamma Telecom Limited, a company incorporated in England and Wales, =

> with limited liability, with registered number 04340834, and whose =

> registered office is at 5 Fleet Place London EC4M 7RD and whose =

> principal place of business is at Kings House, Kings Road West, =

> Newbury, Berkshire, RG14 5BY.
>
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: 15 September 2015 13:05
> To: Nigel Weinronk <Nigel.Weinronk@gamma.co.uk>; Nigel Weinronk =

> <Nigel.Weinronk@gamma.co.uk>
> Subject: New Version Notification for =

> draft-weinronk-last-diverting-line-identity-00.txt
>
>
> A new version of I-D, =

> draft-weinronk-last-diverting-line-identity-00.txt
> has been successfully submitted by Nigel Weinronk and posted to the =

> IETF repository.
>
> Name:           draft-weinronk-last-diverting-line-identity
> Revision:       00
> Title:          Last Diverting Line Identity
> Document date:  2015-09-15
> Group:          Individual Submission
> Pages:          9
> URL:            =

> https://www.ietf.org/internet-drafts/draft-weinronk-last-diverting-line=
-identity-00.txt
> Status:         =

> https://datatracker.ietf.org/doc/draft-weinronk-last-diverting-line-ide=
ntity/
> Htmlized:       =

> https://tools.ietf.org/html/draft-weinronk-last-diverting-line-identity=
-00
>
>
> Abstract:
> This document proposes an extension to the Session Initiation
> Protocol (SIP).
>
> In cases where applications/services (for example verification /
> billing) are provided by a network that is not the originating
> network the Network Asserted Identity is needed to provide these
> services.
>
> This extension provides the ability for a 'diversion service' to
> provide a Network Asserted Identity of the last diverting user to
> these applications/services.
>
> This extension defines a new general header, Last Diverting Line
> Identity which conveys the Network Asserted Identity of the
> diverting party to these applications/services.
>
>
>
>
> Please note that it may take a couple of minutes from the time of =

> submission until the htmlized version and diff are available at =

> tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


From nobody Mon Feb  8 15:56:48 2016
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46EBF1B3DAB for <dispatch@ietfa.amsl.com>; Mon,  8 Feb 2016 15:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 wBgUyGOOF5hU for <dispatch@ietfa.amsl.com>; Mon,  8 Feb 2016 15:56:44 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 BECE61B3DA4 for <dispatch@ietf.org>; Mon,  8 Feb 2016 15:56:44 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u18NuhL5030104 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <dispatch@ietf.org>; Mon, 8 Feb 2016 17:56:44 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: DISPATCH <dispatch@ietf.org>
Date: Mon, 08 Feb 2016 17:56:43 -0600
Message-ID: <F967E6E0-E292-454F-BCBA-05646E10E506@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5213)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/bGMvFXLToNDJSsW0ro49VdMMVLY>
Subject: [dispatch] Updated to Proposed New DISPATCH Charter
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 23:56:46 -0000

Hi,

I made a couple of edits to the proposed new charter[1], due to AD 
comments made during the internal review. Please take a look. If anyone 
has substantial objections to the changes, please say so ASAP. 
Otherwise, this will shortly go to external review. (And of course 
people can continue to send feedback during the external review.)

Thanks!

Ben.

[1] 
https://www.ietf.org/rfcdiff?url1=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-01.txt&url2=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-02.txt.


From nobody Mon Feb  8 15:58:28 2016
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C97D21B3DAB; Mon,  8 Feb 2016 15:58:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 eSWStBmUipT4; Mon,  8 Feb 2016 15:58:23 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 461AD1B3DAA; Mon,  8 Feb 2016 15:58:23 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u18NwJwv030230 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 8 Feb 2016 17:58:20 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: "Benoit Claise" <bclaise@cisco.com>
Date: Mon, 08 Feb 2016 17:58:19 -0600
Message-ID: <C9FEC1BB-4CAD-4FDF-AC40-B9DE882D51AC@nostrum.com>
In-Reply-To: <20160204153934.14557.85409.idtracker@ietfa.amsl.com>
References: <20160204153934.14557.85409.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.4r5213)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/g3Xz-8kaHRrIK3cyyL8hY46xU5Y>
Cc: dispatch@ietf.org, The IESG <iesg@ietf.org>, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Benoit Claise's No Objection on charter-ietf-dispatch-02-01: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 23:58:25 -0000

Benoit,

Does the update at [1] address your original concern?

Thanks!

Ben.

[1] =

https://www.ietf.org/rfcdiff?url1=3Dhttps%3A%2F%2Fdatatracker.ietf.org%2F=
doc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-01.txt&url2=3Dhttps%3A%2F=
%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02=
-02.txt.

On 4 Feb 2016, at 9:39, Benoit Claise wrote:

> Benoit Claise has entered the following ballot position for
> charter-ietf-dispatch-02-01: No Objection
>
> 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-dispatch/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I received the necessary clarifications from both Barry and Ben during
> the IESG telechat. Thanks, Benoit
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
>
>
> (*)  Disclaimer: I've not been following RAI/ART work in the IETF and =

> I
> don't know whether the DISPATCH process has been efficient or not. So
> I'll mainly make observations.
>
> I understand Harald's point,
> https://mailarchive.ietf.org/arch/msg/ietf/-kiAbvZDTCLets4szoXmaCIgrs4,=

> When I read the charter, it's like an extra procedure, specific to =

> ART.
> For example, if I want a BoF, I must first go to DISPATCH to get their
> approval? Same thing for AD-sponsored document?
>
>  The Dispatch working group is chartered to consider proposals for
> new
>  work in the ART area and identify, or help create, an appropriate
> venue
>  for the work.
>
> Btw, no change here: this sentence is basically unchanged compared to =

> the
> previous charter.
>
> In the past, I was told that DISPATCH was similar to the OPSAWG WG.
> Let me observe it's not. "The DISPATCH WG will not do any protocol =

> work",
> while OPSAWG might.
>> From the OPSAWG charter:
>
>  The Operations and Management Area receives occasional proposals for
>  the development and publication of RFCs dealing with operational and
>  management topics that are not in scope of an existing working group
>  and do not justify the formation of a new working group. The OPSAWG
>  will serve as the forum for developing such work items in the IETF.
>
> Obviously, redirecting work to existing WGs is also an OPSAWG task.
> And when the work is substantial, a new WG can even be created. Ex: =

> EMAN
> in the past
>
> I prefer the OPSAWG approach (*).


From nobody Mon Feb  8 15:59:36 2016
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33D821B3DB4; Mon,  8 Feb 2016 15:59:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 AFXdrrKX20Zy; Mon,  8 Feb 2016 15:59:33 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 7E82C1B3DAE; Mon,  8 Feb 2016 15:59:33 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u18NxTLD030344 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 8 Feb 2016 17:59:30 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
Date: Mon, 08 Feb 2016 17:59:28 -0600
Message-ID: <97DB39B8-6AB1-4218-B72B-569822B49242@nostrum.com>
In-Reply-To: <20160204141918.18497.50701.idtracker@ietfa.amsl.com>
References: <20160204141918.18497.50701.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.4r5213)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/eswjNI93w6dMXe0Jtc-NAEduEOg>
Cc: dispatch@ietf.org, The IESG <iesg@ietf.org>, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Stephen Farrell's No Objection on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 23:59:35 -0000

Hi Stephen,

Does the update at [1] address your comment?

Thanks!

Ben.

[1] =

https://www.ietf.org/rfcdiff?url1=3Dhttps%3A%2F%2Fdatatracker.ietf.org%2F=
doc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-01.txt&url2=3Dhttps%3A%2F=
%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02=
-02.txt

On 4 Feb 2016, at 8:19, Stephen Farrell wrote:

> Stephen Farrell has entered the following ballot position for
> charter-ietf-dispatch-02-00: No Objection
>
> 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-dispatch/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
>
> A friendly amendment, if you're up for accepting it: I think a
> change along these lines would better reflect what we hope
> folks will be doing:
>
> OLD:
>
> 5. Ensuring that the new work considers security and privacy.
>
> NEW:
>
> 5. Ensuring that the new work considers and aims to improve
> security and privacy.
>
> My reason is that while we definitely do want to consider
> security and privacy, I think we do have consensus to try to
> make those better whenever we can, and to never just say
> "yeah, we thought about it, but we're doing nothing." I think
> it may be better if we can say that the DISPATCH charter
> calls for improvement to handle cases where folks are a
> bit reluctant to change a piece of work they bring to the
> IETF that hasn't done such a good job on security or
> privacy.


From nobody Mon Feb  8 16:01:55 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 194A51B3DC8; Mon,  8 Feb 2016 16:01:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
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 JyA_V2CBNp_4; Mon,  8 Feb 2016 16:01:49 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF9001B3DC0; Mon,  8 Feb 2016 16:01:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C4A4EBE50; Tue,  9 Feb 2016 00:01:47 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2rnHWYXJXp6l; Tue,  9 Feb 2016 00:01:46 +0000 (GMT)
Received: from [10.87.48.75] (unknown [86.46.17.89]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id DE323BE4C; Tue,  9 Feb 2016 00:01:45 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1454976106; bh=NZdS/FTo1YNmMqwoxTQvzD7IXuejE/Z1UXq9Mi3npAc=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=i7hvRXpTuPiSRx89IhwxLypAF1J0rLEGMCJhsC4jXGFWZ5CcWofNLyVbbPbvM+q2f c9dB3L/wtHNnpyWxhxfm1ztMqQ9vT3zGlr4SemASiw0fDsQfm6s3uSYjfetZ5NiuvO Y6y442yzReHu1U7sMF+HUgkVKhlu6SvI6jTR6oT0=
To: Ben Campbell <ben@nostrum.com>
References: <20160204141918.18497.50701.idtracker@ietfa.amsl.com> <97DB39B8-6AB1-4218-B72B-569822B49242@nostrum.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <56B92C69.5080709@cs.tcd.ie>
Date: Tue, 9 Feb 2016 00:01:45 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <97DB39B8-6AB1-4218-B72B-569822B49242@nostrum.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/BmHjxYLZWY3E1zvahuJKrFWzH20>
Cc: dispatch@ietf.org, The IESG <iesg@ietf.org>, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Stephen Farrell's No Objection on charter-ietf-dispatch-02-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 00:01:52 -0000

On 08/02/16 23:59, Ben Campbell wrote:
> Hi Stephen,
> 
> Does the update at [1] address your comment?

Yep, thanks,
S

> 
> Thanks!
> 
> Ben.
> 
> [1]
> https://www.ietf.org/rfcdiff?url1=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-01.txt&url2=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-02.txt
> 
> 
> On 4 Feb 2016, at 8:19, Stephen Farrell wrote:
> 
>> Stephen Farrell has entered the following ballot position for
>> charter-ietf-dispatch-02-00: No Objection
>>
>> 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-dispatch/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>>
>> A friendly amendment, if you're up for accepting it: I think a
>> change along these lines would better reflect what we hope
>> folks will be doing:
>>
>> OLD:
>>
>> 5. Ensuring that the new work considers security and privacy.
>>
>> NEW:
>>
>> 5. Ensuring that the new work considers and aims to improve
>> security and privacy.
>>
>> My reason is that while we definitely do want to consider
>> security and privacy, I think we do have consensus to try to
>> make those better whenever we can, and to never just say
>> "yeah, we thought about it, but we're doing nothing." I think
>> it may be better if we can say that the DISPATCH charter
>> calls for improvement to handle cases where folks are a
>> bit reluctant to change a piece of work they bring to the
>> IETF that hasn't done such a good job on security or
>> privacy.
> 


From nobody Tue Feb  9 05:51:33 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83EBC1A903B for <dispatch@ietfa.amsl.com>; Tue,  9 Feb 2016 05:51:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 6Q20G8n67XK2 for <dispatch@ietfa.amsl.com>; Tue,  9 Feb 2016 05:51:28 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3282F1A902F for <dispatch@ietf.org>; Tue,  9 Feb 2016 05:51:28 -0800 (PST)
X-AuditID: c1b4fb25-f797e6d000007600-5b-56b9eede0a8b
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.183.30]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id B9.D2.30208.EDEE9B65; Tue,  9 Feb 2016 14:51:26 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.151]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.03.0248.002; Tue, 9 Feb 2016 14:51:25 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: Draft new: draft-holmberg-dispatch-mcptt-rp-namespace-00.txt
Thread-Index: AdFjQJjkKlzfMs/1QfqDRnL1Vu370w==
Date: Tue, 9 Feb 2016 13:51:24 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37DC6FE8@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37DC6FE8ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42KZGbFdTvfeu51hBhtWyFtsfbGaxWLppAWs DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAldG86prTAVbFSoapy1hbGDcL9PFyMkhIWAi 8eP+KRYIW0ziwr31bCC2kMBhRonNG326GLmA7MWMErsXPwMq4uBgE7CQ6P6nDVIjIqAtcXRV FzOIzSzgKnFq/zF2EFsYyH507A4bRI2XxJN7TxghbD2JT7MPsoLYLAIqEo1TesB6eQV8JV68 u8kEYjMC3fD91BomiJniEreezGeCuE1AYsme88wQtqjEy8f/WEHOkRBQlFjeLwdRni8x+9N9 NoiRghInZz5hmcAoPAvJpFlIymYhKYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGEWL U4uTctONjPVSizKTi4vz8/TyUks2MQJj5+CW36o7GC+/cTzEKMDBqMTD+0F2Z5gQa2JZcWXu IUYJDmYlEV65N0Ah3pTEyqrUovz4otKc1OJDjNIcLErivGuc14cJCaQnlqRmp6YWpBbBZJk4 OKUaGFkO7nZ05IrcqClY2+ymcWbXUqtdfGtf/Tp61cvYhlF+mXr2s9WfPxX/Nk/Xd37hX1Dz PrRaa9ZR1oqwLcv3Pl7+YEpLz2P9mz/c7Z+fOB00795arofzT95Me5v3zm7teYEp6YWCBh4m 93cv5ShcyBwp9FD3b7Xh1aP/fQSD+5VVZC8bztW6UqXEUpyRaKjFXFScCAA0mGvkmQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/vqFYftOx-tBPE0AfAotkpgAWWs4>
Cc: "dispatch-chairs@tools.ietf.org" <dispatch-chairs@tools.ietf.org>
Subject: [dispatch] Draft new: draft-holmberg-dispatch-mcptt-rp-namespace-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 13:51:30 -0000

--_000_7594FB04B1934943A5C02806D1A2204B37DC6FE8ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

We've submitted a new draft, draft-holmberg-dispatch-mcptt-rp-namespace-00.=
txt.

The purpose of the draft is to register a new SIP Resource-Priority header =
field namespace. 3GPP is in the process of defining Mission Critical Push t=
o Talk (MCPTT) over LTE. The service is an enhanced PTT service intended fo=
r mission critical public service use. It is based on the 3GPP Evolved Pack=
et System services.

As this service is over the radio network and needs to function even when r=
esources are scarce in various disaster scenarios a priority mechanism is n=
eeded to ensure that the highest priority traffic gets the resources it nee=
ds.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B37DC6FE8ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FI" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We&#8217;ve submitted a new dra=
ft, draft-holmberg-dispatch-mcptt-rp-namespace-00.txt.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">The purpose of the draft is to =
register a new SIP Resource-Priority header field namespace. 3GPP is in the=
 process of defining Mission Critical Push to Talk (MCPTT) over LTE. The se=
rvice is an enhanced PTT service intended
 for mission critical public service use. It is based on the 3GPP Evolved P=
acket System services.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">As this service is over the rad=
io network and needs to function even when resources are scarce in various =
disaster scenarios a priority mechanism is needed to ensure that the highes=
t priority traffic gets the resources
 it needs.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Christer<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B37DC6FE8ESESSMB209erics_--


From nobody Wed Feb 10 03:33:13 2016
Return-Path: <Peter.Dawes@vodafone.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF511A1B87 for <dispatch@ietfa.amsl.com>; Wed, 10 Feb 2016 03:33:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 Aps3lsMTqQez for <dispatch@ietfa.amsl.com>; Wed, 10 Feb 2016 03:33:09 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A181F1A1B86 for <dispatch@ietf.org>; Wed, 10 Feb 2016 03:33:08 -0800 (PST)
Received: from [195.245.230.51] by server-6.bemta-3.messagelabs.com id CD/F2-08479-CEF1BB65; Wed, 10 Feb 2016 11:33:00 +0000
X-Env-Sender: Peter.Dawes@vodafone.com
X-Msg-Ref: server-2.tower-33.messagelabs.com!1455103980!15433979!1
X-Originating-IP: [195.232.244.134]
X-StarScan-Received: 
X-StarScan-Version: 7.35.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31458 invoked from network); 10 Feb 2016 11:33:00 -0000
Received: from mailout02.vodafone.com (HELO mailout02.vodafone.com) (195.232.244.134) by server-2.tower-33.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2016 11:33:00 -0000
Received: from mailint01.vodafone.com (mailint01.vodafone.com [195.232.244.198]) by mailout02.vodafone.com (Postfix) with ESMTP id 3q0f8r0lNzzbdFb; Wed, 10 Feb 2016 12:33:00 +0100 (CET)
Received: from mailint01.vodafone.com (localhost [127.0.0.1]) by mailint01.vodafone.com (Postfix) with ESMTP id 3q0f8q6xLWzxQDv; Wed, 10 Feb 2016 12:32:59 +0100 (CET)
Received: from VOEXC05W.internal.vodafone.com (voexc05w.dc-ratingen.de [145.230.101.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailint01.vodafone.com (Postfix) with ESMTPS id 3q0f8q6rhKzxQB4; Wed, 10 Feb 2016 12:32:59 +0100 (CET)
Received: from VOEXC30W.internal.vodafone.com (145.230.103.202) by VOEXC05W.internal.vodafone.com (145.230.101.25) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 10 Feb 2016 12:32:59 +0100
Received: from VOEXM31W.internal.vodafone.com ([169.254.7.89]) by voexc30w ([145.230.103.202]) with mapi id 14.03.0224.002; Wed, 10 Feb 2016 12:32:59 +0100
From: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>
To: "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: [dispatch] https://www.ietf.org/id/draft-dawes-sipcore-mediasec-parameter-03.txt
Thread-Index: AdFj9n/RDdNgtOUcTdeo4doxMUAK5Q==
Date: Wed, 10 Feb 2016 11:32:58 +0000
Message-ID: <4A4F136CBD0E0D44AE1EDE36C4CD9D99C89EE030@VOEXM31W.internal.vodafone.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/uYfPcbTjP5yBl6N5hT3RDiQCXuA>
Cc: "dispatch-chairs@tools.ietf.org" <dispatch-chairs@tools.ietf.org>
Subject: [dispatch] https://www.ietf.org/id/draft-dawes-sipcore-mediasec-parameter-03.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 11:33:12 -0000

Hello All,
I would like to ask dispatch to (re-)consider the proposals in https://data=
tracker.ietf.org/doc/draft-dawes-sipcore-mediasec-parameter/ and how it mig=
ht be progressed. One of the sipcore chairs has indicated that this draft p=
robably does not belong in sipcore and dispatch did not make a detailed eva=
luation the first time it was brought to the group.=20

The most recent comments on the sipcore mailing list are https://mailarchiv=
e.ietf.org/arch/msg/sipcore/mD1Qedh93ep9oVOxttIxKN7lIcg and it might help t=
o repeat part of what I said there about the new header field parameter tha=
t is the reason for the draft:=20

"...the header field parameter introduced by this draft originates from 3GP=
P specifications and related procedures and header field values are also de=
scribed in 3GPP specifications. The purpose of this draft is to name the he=
ader field parameter, give several illustrative examples to make it clear h=
ow it is used, and set up an IANA registry for existing and future values. =
The draft does not propose that IETF defines any new security setup procedu=
res, ciphering, integrity protection etc."

Thanks and regards,
Peter


From nobody Wed Feb 10 05:54:29 2016
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 987EC1A8A9B for <dispatch@ietfa.amsl.com>; Wed, 10 Feb 2016 05:54:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 OHKTcQMzRijV for <dispatch@ietfa.amsl.com>; Wed, 10 Feb 2016 05:54:27 -0800 (PST)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (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 08AEB1A8AB3 for <dispatch@ietf.org>; Wed, 10 Feb 2016 05:54:27 -0800 (PST)
Received: by mail-yw0-x236.google.com with SMTP id q190so14231176ywd.3 for <dispatch@ietf.org>; Wed, 10 Feb 2016 05:54:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=4RXs38ftx9Q3ICsPaFJNhI3tJ/e3Q8O21QhvSuddMQ8=; b=eAU+j/I6DQXXpOb2wsRx904uQq8/2to4YZBIO1LQkM1MQkkeB4vo99F1ZSC++gIsPp 7w/Dh0rlyvizdjAAhlmZqeKy7kwdxkpJHD8eld/zMY8Zj+KWzMBchYIRAwBgPdLcwNWg oczzkDU4kUzxxNMgAA8aLZtnjj8k/9sUmUxeDlweELtjIXq2C9gsfJElyPo0nIfdwoGE rA9+ha10s6vHjBCgbM7y1KE0VSHXiH1e4BjwQN9sntE6PuA5l3yQT9AcKxOSqdfVM4Yb R3JrWlnToXNoExPVfHoVguNju23taE4OwxAvHcpFXs3S0lC6qPBL2fMo2AwS+CnXJ41o 64gA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=4RXs38ftx9Q3ICsPaFJNhI3tJ/e3Q8O21QhvSuddMQ8=; b=ileKGWTK/SUSCxEOXFJ+aUL+lK3fyyVIUXwGLtDbcAxJD15I8CKedzCNYOWO9qIwKf Fm5vLDQuib3N7waKj64qF+WwAnNHhfngI91mdyXDdBaSL/cBp0klLDNOcvGXsl6Krt0d QjZvty0hZ1fQGAnYS8YHrieREEkqMz1yQauzpAAuH4F1jTiqIyzYkdRv0ReYjXNJPEOb b2QZ/Eg2tVysYC1B9wrLZyLDykbaxA1B15M3sNNZeIJMJ7TWbG7t/d0r94urxMfV3BJQ qpq+ccxCyrqU5xK4V0pGV3Nr3CFLdVOHnJffKn6V2Ej7eQIs9sWlANRGOZ72oy0krY94 HNTw==
X-Gm-Message-State: AG10YOQELy0uSZrNgoK/0lScAx07p6ILefWMg4FTHhxatQyk9OxmRx+VySIxciJVIRRkQl4xYTkdbJ8r9iRPJA==
MIME-Version: 1.0
X-Received: by 10.129.34.133 with SMTP id i127mr21699674ywi.153.1455112466404;  Wed, 10 Feb 2016 05:54:26 -0800 (PST)
Received: by 10.37.101.68 with HTTP; Wed, 10 Feb 2016 05:54:26 -0800 (PST)
Date: Wed, 10 Feb 2016 07:54:26 -0600
Message-ID: <CAHBDyN4hgTg1o4On39C6sKwO9y=yy+46SEJB1DJrAfaUfhir=Q@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: DISPATCH <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary=001a114091bcab296e052b6ac583
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/K5q4sOMBqgRtpHu4073BKtTFbPU>
Subject: [dispatch] Reminder: Deadlines for IETF-95
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 13:54:28 -0000

--001a114091bcab296e052b6ac583
Content-Type: text/plain; charset=UTF-8

Hi all,

Just a reminder of the DISPATCH WG deadlines for IETF-95:
https://trac.tools.ietf.org/wg/dispatch/trac/wiki


   - February 22, 2016. Cutoff date to notify the chairs/DISPATCH WG of
   plans to submit a proposal.


   - February 29, 2016. Cutoff for charter proposals for topics.


   - March 7, 2016. Announcement of topics that have been dispatched for
   IETF-95.


   - March 21, 2016. Draft deadline.


Regards,
Mary

--001a114091bcab296e052b6ac583
Content-Type: text/html; charset=UTF-8

<div dir="ltr">Hi all,<div><br></div><div>Just a reminder of the DISPATCH WG deadlines for IETF-95:</div><div><a href="https://trac.tools.ietf.org/wg/dispatch/trac/wiki">https://trac.tools.ietf.org/wg/dispatch/trac/wiki</a><br></div><div><br></div><div>







<ul class="">
<li class=""><span class=""></span><span class="">February 22, 2016. Cutoff date to notify the chairs/DISPATCH WG of plans to submit a proposal.</span></li>
</ul>
<ul class="">
<li class=""><span class="">February 29, 2016. Cutoff for charter proposals for topics.</span></li>
</ul>
<ul class="">
<li class=""><span class="">March 7, 2016. Announcement of topics that have been dispatched for IETF-95.</span></li>
</ul>
<ul class="">
<li class=""><span class="">March 21, 2016. Draft deadline.</span></li>
</ul><div><br></div></div><div>Regards,</div><div>Mary</div></div>

--001a114091bcab296e052b6ac583--


From nobody Thu Feb 11 17:56:36 2016
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB181B3DBC for <dispatch@ietfa.amsl.com>; Thu, 11 Feb 2016 17:56:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 k7iDmMdkHCAu for <dispatch@ietfa.amsl.com>; Thu, 11 Feb 2016 17:56:33 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 D2F2F1B3DC0 for <dispatch@ietf.org>; Thu, 11 Feb 2016 17:56:33 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u1C1uVNP068072 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 11 Feb 2016 19:56:31 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: "Mary Barnes" <mary.ietf.barnes@gmail.com>
Date: Thu, 11 Feb 2016 19:56:30 -0600
Message-ID: <8119825D-F91F-4494-AE59-39E3956B02F1@nostrum.com>
In-Reply-To: <CAHBDyN4hgTg1o4On39C6sKwO9y=yy+46SEJB1DJrAfaUfhir=Q@mail.gmail.com>
References: <CAHBDyN4hgTg1o4On39C6sKwO9y=yy+46SEJB1DJrAfaUfhir=Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5213)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/w104A7cpMZ5TXikN1XqtOkklrH4>
Cc: DISPATCH <dispatch@ietf.org>
Subject: Re: [dispatch] Reminder: Deadlines for IETF-95
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2016 01:56:35 -0000

Hi,

I understand that Jon, Ekr, Richard, and Russ plan to submit a draft on 
security recommendations for point-to-point, SIP-signaled RTP in time 
for Buenos Aires. While I would be pleasantly surprised if the 
discussion is far enough along by then for a charter proposal, I think 
discussion in DISPATCH would be worthwhile.

So, please consider this notice of their intent to propose a discussion 
topic, on their behalf.

Thanks!

Ben.

On 10 Feb 2016, at 7:54, Mary Barnes wrote:

> Hi all,
>
> Just a reminder of the DISPATCH WG deadlines for IETF-95:
> https://trac.tools.ietf.org/wg/dispatch/trac/wiki
>
>
>  - February 22, 2016. Cutoff date to notify the chairs/DISPATCH WG of
>  plans to submit a proposal.
>
>
>  - February 29, 2016. Cutoff for charter proposals for topics.
>
>
>  - March 7, 2016. Announcement of topics that have been dispatched for
>  IETF-95.
>
>
>  - March 21, 2016. Draft deadline.
>
>
> Regards,
> Mary
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


From nobody Fri Feb 12 13:59:02 2016
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 401A31A9091; Fri, 12 Feb 2016 13:59:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 RuqgOKBuZLdb; Fri, 12 Feb 2016 13:58:59 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 717331A9088; Fri, 12 Feb 2016 13:58:59 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u1CLwwVx092834 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 12 Feb 2016 15:58:58 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: IESG <iesg@ietf.org>, DISPATCH <dispatch@ietf.org>, dispatch-chairs@tools.ietf.org
Date: Fri, 12 Feb 2016 15:58:57 -0600
Message-ID: <3E9F04A5-8982-47C9-9BD3-7AFB8CF52823@nostrum.com>
MIME-Version: 1.0
X-Mailer: MailMate (1.9.4r5213)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/k03-H0mRLSV5bwJRR2sytAMPTrI>
Subject: [dispatch] Approved: DISPATCH charter update for external review
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2016 21:59:00 -0000

Hi Secretariat (bcc'd)

The updated DISPATCH charter is ready for external review.

Thanks!

Ben.


From nobody Fri Feb 12 14:10:33 2016
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dispatch@ietf.org
Delivered-To: dispatch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B5E1A90DC; Fri, 12 Feb 2016 14:10:30 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160212221030.18260.11945.idtracker@ietfa.amsl.com>
Date: Fri, 12 Feb 2016 14:10:30 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/G_6Ohpm39K9fJeV0b1fiJHHvOno>
Cc: dispatch@ietf.org
Subject: [dispatch] WG Review: Dispatch (dispatch)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2016 22:10:30 -0000

The Dispatch (dispatch) WG in the Applications and Real-Time Area of the
IETF is undergoing rechartering. The IESG has not made any determination
yet. The following draft charter was submitted, and is provided for
informational purposes only. Please send your comments to the IESG
mailing list (iesg@ietf.org) by 2016-02-22.

Dispatch (dispatch)
-----------------------------------------------------------------------
Current status: Active WG

Chairs:
  Mary Barnes <mary.ietf.barnes@gmail.com>
  Cullen Jennings <fluffy@iii.ca>
  Murray Kucherawy <superuser@gmail.com>

Assigned Area Director:
  Ben Campbell <ben@nostrum.com>

Applications and Real-Time Area Directors:
  Barry Leiba <barryleiba@computer.org>
  Ben Campbell <ben@nostrum.com>
  Alissa Cooper <alissa@cooperw.in>
 
Mailing list:
  Address: dispatch@ietf.org
  To subscribe: https://www.ietf.org/mailman/listinfo/dispatch
  Archive: https://mailarchive.ietf.org/arch/browse/dispatch/

Charter: https://datatracker.ietf.org/doc/charter-ietf-dispatch/

The Dispatch working group is chartered to consider proposals for new
work in the ART area and identify, or help create, an appropriate venue
for the work.

Guiding principles for the proposed new work include:

1. Providing a clear problem statement, motivation and deliverables for
   the proposed new work.

2. Ensuring there has been adequate mailing list discussion reflecting
   sufficient interest, individuals have expressed a willingness to
   contribute and there is WG consensus before new work is dispatched.

3. Looking for and identifying commonalities and overlap amongst
   published or ongoing protocol work. Such commonalities may indicate
   the possibility of reusing existing protocols or elements thereof
   published by other WGs, or expanding and/or refactoring the scope of
   deliverables in an active WG.

4. Protecting the architectural integrity of IETF protocols and ensuring
   that new work has general applicability.

5. Ensuring that the new work considers and seeks to improve security 
    and privacy.

Options for handling new work include:

- Directing the work to an existing WG. 
- Developing a proposal for a BOF.
- Developing a charter for a new WG. 
- Making recommendations that documents be AD-sponsored 
  (which ADs may or may not choose to follow).
- By agreement with ART ADs, processing simple administrative documents. 
- Deferring the decision for the new work. 
- Rejecting the new work.

If the group decides that a particular topic needs to be addressed by a
new WG, the normal IETF chartering process will be followed, including,
for instance, IETF-wide review of the proposed charter. Proposals for
large work efforts SHOULD lead to a BOF where the topic can be discussed
in front of the entire IETF community. The DISPATCH WG will not do any
protocol work. Specifically, DISPATCH will always opt to find a location
for technical work; the only work that DISPATCH is not required to
delegate (or defer, or reject) is administrative work such as IANA
actions. Documents progressed as AD-sponsored would typically include
those that do not have general applicability to IETF protocols, but
rather are only applicable to specific use cases and network
deployments, for which the scope must be clearly specified.

Proposed new work may be deferred in cases where the WG does not have
enough information for the chairs to determine consensus. New work may
be rejected in cases where there is not sufficient WG interest or the
proposal has been considered and rejected in the past, unless a
substantially revised proposal is put forth, including compelling new
reasons for accepting the work.

A major objective of the DISPATCH WG is to provide timely, clear
dispositions of new efforts. Thus, where there is consensus to take on
new work, the WG will strive to quickly find a home for it. While most
new work in the ART area is expected to be considered in the DISPATCH
working group, there may be times where that is not appropriate. At the
discretion of the area directors, new efforts may follow other paths. 
For example work may go directly to BoFs, may be initiated in other 
working groups when it clearly belongs in that group, or may be directly 
AD sponsored.




From nobody Thu Feb 18 07:54:36 2016
Return-Path: <nweinronk@btinternet.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40AD71B29E6 for <dispatch@ietfa.amsl.com>; Thu, 18 Feb 2016 07:54:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.599
X-Spam-Level: 
X-Spam-Status: No, score=0.599 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 ElP9BxGCglcv for <dispatch@ietfa.amsl.com>; Thu, 18 Feb 2016 07:54:32 -0800 (PST)
Received: from rgout0103.bt.lon5.cpcloud.co.uk (rgout0103.bt.lon5.cpcloud.co.uk [65.20.0.123]) by ietfa.amsl.com (Postfix) with ESMTP id 211671B29D6 for <dispatch@ietf.org>; Thu, 18 Feb 2016 07:54:31 -0800 (PST)
X-OWM-Source-IP: 10.110.13.1 ()
X-OWM-Env-Sender: nweinronk@btinternet.com
X-CTCH-RefID: str=0001.0A090201.56C5E92D.004A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-Spam: Unknown
X-RazorGate-Suspect: true
Received: from webmail38.bt.ext.cpcloud.co.uk (10.110.13.1) by rgout01.bt.lon5.cpcloud.co.uk (8.6.122.06) (authenticated as nweinronk@btinternet.com) id 56B9DEA20100F081; Thu, 18 Feb 2016 15:54:21 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btcpcloud; t=1455810872;  bh=OIzgz01ZeNJquMXFGQ7JgJXgjqobenfB6d1PuEHNc5o=; h=Date:From:Reply-To:To:Message-ID:In-Reply-To:References:Subject:MIME-Version; b=Uqv9co2vRprhOvJPmGSm8wA3JPuPdSYCr8NLmOqcqJQYD8oDC2wJo1MWIEjsST7k2T5MNsF2QI5bknYKSbuQdz/MbNCEANxwPOaGqObk5mCTbIPt1gGYL10E2xmfIHm/Dw7hkCtfYnxt7g3H9udpXaH+Zeala3uyhwKJKK7lHjc=
Date: Thu, 18 Feb 2016 15:54:21 +0000 (GMT)
From: N WEINRONK <nweinronk@btinternet.com>
To: ben@nostrum.com, dispatch@ietf.org, Nigel.Weinronk@gamma.co.uk
Message-ID: <30488691.40732.1455810861085.JavaMail.defaultUser@defaultHost>
In-Reply-To: <3F4D2A04-2743-4EF1-80BC-8FDBD15723AC@nostrum.com>
References: <20150915120520.28650.89731.idtracker@ietfa.amsl.com> <2FA3A1EB67D00349B9871E2A3841072D0117CA6E29@INF-EXCH-MB-02.gammatelecom.com> <3F4D2A04-2743-4EF1-80BC-8FDBD15723AC@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-CP-REPLY-ALL-UID: 24201
X-CP-REPLY-ALL-PATH: INBOX
Importance: 3 (Normal)
X-Priority: 3 (Normal)
X-Client-IP: IPv4[31.53.69.176] Epoch[1455810861060]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/VHOqjky-9czrF_9JI-0DxgHRPwk>
Subject: Re: [dispatch] New Version Notification for draft-weinronk-last-diverting-line-identity-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: nweinronk@btinternet.com
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2016 15:54:35 -0000

I have resubmitted this draft under the dispatch working group as:

https://datatracker.ietf.org/doc/draft-weinronk-dispatch-last-diverting-lin=
e-id/=20

This draft defines a new SIP header "Last-Diverting-Line-Identity" for=20
use where a Network Asserted Identity of the last diverted user is=20
needed by applications / services provided by a network that is not=20
the originating network.

Your comments are welcome,

 Thanks,
Nigel Weinronk


----Original message----
>From : ben@nostrum.com
Date : 08/02/2016 - 21:56 (GMTST)
To : Nigel.Weinronk@gamma.co.uk, dispatch@ietf.org
Subject : Re: [dispatch] New Version Notification for draft-weinronk-last-d=
iverting-line-identity-00.txt

Hi Everyone,

I'd like people to comment on the IANA registrations requested in this=20
draft. I think it's likely this would have been an independent stream=20
submission, but the privacy header field registration requires IETF=20
review. The header field registration might require that as well,=20
depending on the opinion of the expert reviewer.

Thanks!

Ben.

On 23 Jan 2016, at 6:21, Nigel Weinronk wrote:

> I have been advised to submit this draft=20
> (draft-weinronk-last-diverting-line-identity-00.txt) to the DISPATCH=20
> WG as it proposes a new SIP header - see below.
>
> This draft defines a new SIP header "Last-Diverting-Line-Identity" for=20
> use where a Network Asserted Identity of the last diverted user is=20
> needed by applications / services provided by a network that is not=20
> the originating network.
>
> Your comments are welcome,
>
> Thanks,
> Nigel Weinronk
>
>
>
>
>      Nigel Weinronk
>      Design Engineer
>
> T:      0333 240 3421
> M:      07436 070 002
> E:      Nigel.Weinronk@gamma.co.uk
> W:      www.gamma.co.uk
>
> This is an email from Gamma Telecom Ltd, trading as =E2=80=9CGamma=E2=80=
=9D. The=20
> contents of this email are confidential to the ordinary user of the=20
> email address to which it was addressed. This email is not intended to=20
> create any legal relationship. No one else may place any reliance upon=20
> it, or copy or forward all or any of it in any form (unless otherwise=20
> notified). If you receive this email in error, please accept our=20
> apologies, we would be obliged if you would telephone our postmaster=20
> on +44 (0) 808 178 9652 or email postmaster@gamma.co.uk
>
> Gamma Telecom Limited, a company incorporated in England and Wales,=20
> with limited liability, with registered number 04340834, and whose=20
> registered office is at 5 Fleet Place London EC4M 7RD and whose=20
> principal place of business is at Kings House, Kings Road West,=20
> Newbury, Berkshire, RG14 5BY.
>
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: 15 September 2015 13:05
> To: Nigel Weinronk <Nigel.Weinronk@gamma.co.uk>; Nigel Weinronk=20
> <Nigel.Weinronk@gamma.co.uk>
> Subject: New Version Notification for=20
> draft-weinronk-last-diverting-line-identity-00.txt
>
>
> A new version of I-D,=20
> draft-weinronk-last-diverting-line-identity-00.txt
> has been successfully submitted by Nigel Weinronk and posted to the=20
> IETF repository.
>
> Name:           draft-weinronk-last-diverting-line-identity
> Revision:       00
> Title:          Last Diverting Line Identity
> Document date:  2015-09-15
> Group:          Individual Submission
> Pages:          9
> URL:           =20
> https://www.ietf.org/internet-drafts/draft-weinronk-last-diverting-line-i=
dentity-00.txt
> Status:        =20
> https://datatracker.ietf.org/doc/draft-weinronk-last-diverting-line-ident=
ity/
> Htmlized:      =20
> https://tools.ietf.org/html/draft-weinronk-last-diverting-line-identity-0=
0
>
>
> Abstract:
> This document proposes an extension to the Session Initiation
> Protocol (SIP).
>
> In cases where applications/services (for example verification /
> billing) are provided by a network that is not the originating
> network the Network Asserted Identity is needed to provide these
> services.
>
> This extension provides the ability for a 'diversion service' to
> provide a Network Asserted Identity of the last diverting user to
> these applications/services.
>
> This extension defines a new general header, Last Diverting Line
> Identity which conveys the Network Asserted Identity of the
> diverting party to these applications/services.
>
>
>
>
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at=20
> tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch


From nobody Sat Feb 20 23:07:01 2016
Return-Path: <a.james.winterbottom@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8951B2E18 for <dispatch@ietfa.amsl.com>; Sat, 20 Feb 2016 23:07:00 -0800 (PST)
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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 caymqFD9QpNf for <dispatch@ietfa.amsl.com>; Sat, 20 Feb 2016 23:06:59 -0800 (PST)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (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 EDF811B2D0C for <dispatch@ietf.org>; Sat, 20 Feb 2016 23:06:58 -0800 (PST)
Received: by mail-pa0-x22d.google.com with SMTP id ho8so75472901pac.2 for <dispatch@ietf.org>; Sat, 20 Feb 2016 23:06:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=AnMl2QGLl6VBkLLtX4kx3ATlQl9sxlgneApl1gI5EN4=; b=Ln/Hs2vz6o4Tyxg/lvnWsFq5G81croi9xWIbKFsk32s3TASP2OCua9Xq1lt690L+sK NAIryt2DVPBseNbr7FESl4Gp+FNyLVTxYTUnondEutxw/FfZ6CHx016w7/1DvKt+h3u8 naE5DNZ2Sya5EPkTen87zs8zWswyNkw51fACsdqIxDZUEiMAm2uuYjpl08d5xyNikSFY ElKfa/jNwOMRKI/3F3EYFGayxTDw9o/AL++TdgWOMszEZ8r7AIpXf4qrpKnk92vvzFjH htjZ4lTTgQtsl+VrGmYLm4gs7gAWkPqGuz5Xuke48aBHFY+Oh0eOWkqKyCeMyiMTIrwt tMWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=AnMl2QGLl6VBkLLtX4kx3ATlQl9sxlgneApl1gI5EN4=; b=Zo+gNsR+vRRAgLMARHpl2thb7Hd3aoNDInYMZewaWskUdVXN5s5MGAGQ2Ic2LzrJVf SJKnlSteO2ssOV3/6xqWjJ5853N2sx4mrgYAXcJB4CDMX1SyNoR6B6B7+qun8lQbsA7G PVOSiRuodnJzWhI8ixoGNBkqeryFgEi4J9UOVfzEOxQF0XbtOpklmPuQfGb5BPjJIEc0 CG0ybrfz/kArNUjaBiSRxpvJD6foHbyzC7ziTHfltnAZ3xP7uqPJ+flnol+wKohRA9jy Tbw3VRoBxT7x9LANApKJm9U9kRDp/NIFCDuj9SkWaqh2S+MnzVthtDxCpyHs4u3xvWqu e3kA==
X-Gm-Message-State: AG10YOTdNOJxhHiS3sr60Lt9uMIyij2IQXXxaRxUQvqR2xOtmqfOL1H2OLImteMbI/JNRQ==
X-Received: by 10.66.119.202 with SMTP id kw10mr24590326pab.110.1456038418112;  Sat, 20 Feb 2016 23:06:58 -0800 (PST)
Received: from [192.168.1.100] ([1.144.41.236]) by smtp.gmail.com with ESMTPSA id u5sm1948135par.37.2016.02.20.23.06.55 for <dispatch@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sat, 20 Feb 2016 23:06:56 -0800 (PST)
From: James Winterbottom <a.james.winterbottom@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <CCDF6314-688E-49FE-B501-1448815E6CC4@gmail.com>
Date: Sun, 21 Feb 2016 18:06:53 +1100
To: DISPATCH list <dispatch@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/6OMEKvCovaRZJp6vG-trvKMk6gg>
Subject: [dispatch] Please can we dispatch draft-winterbottom-dispatch-locparam-01?
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Feb 2016 07:07:00 -0000

Hi Dispatch Chairs,

This document has been updated for some time with the changes requested =
by WG participants so that it can be dispatched.
This work is required for ongoing ETSI work.

Please can you let me know if there is anything more that I need to do =
to help this document on this way?

Cheers
James


From nobody Sun Feb 21 14:13:45 2016
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AFA91B29BC for <dispatch@ietfa.amsl.com>; Sun, 21 Feb 2016 14:13:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 N7ax8Lgr_w_l for <dispatch@ietfa.amsl.com>; Sun, 21 Feb 2016 14:13:42 -0800 (PST)
Received: from mail-yk0-x232.google.com (mail-yk0-x232.google.com [IPv6:2607:f8b0:4002:c07::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 725AE1AD087 for <dispatch@ietf.org>; Sun, 21 Feb 2016 14:13:42 -0800 (PST)
Received: by mail-yk0-x232.google.com with SMTP id u9so54804876ykd.1 for <dispatch@ietf.org>; Sun, 21 Feb 2016 14:13:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9iA+DlE2Sm+bwjIOjpmCU2D13AniZO5kSdQcemMg528=; b=o8VeWEXrjOYSPNE5ur7UdjNmDTPn8eLmpycb1vAb8ymQKmK78o7/bNSk/cfT2aKmHP 9XF3tAbAYozlCHXOpzY5zDrDGIk/+AhN3quGSxJmFxRpoOgYnPA/VFGnIbJDZ5PcpTtg Suu5dZzLD14RdJaBKkVFcA4VPHCulpPkfXkmlog084XDgrXtJAPVBXMi/QeVCMc1GGaL 3lWRUiFdZu4PlPTFtA42h0js2WTdyVmUjC/IhcYJ98vTCT8iQxFaJ2zay2Bneq7Ib6/3 dCJNkxPSLwSZz40j/aa2G5aGRV32Qv740rE2V2e62j8fYa4GVPAITwX1EFL0EYn+IZLU pYYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=9iA+DlE2Sm+bwjIOjpmCU2D13AniZO5kSdQcemMg528=; b=LkI+GADtNNqaSF711n0SplpOOPrbRydAgGDtK9MEtOjdCexAQL4oaEwjNMRbaYm28P SXNlPUGpEMtEbUfItuug0GRmM7Fmh9EFsD4hnVNt6k0qHLRhd9gEr7gcw+arMostByxD dndUf9ZBe90MCEzGT2kiiGWNgSjAmYoR3GeI+HANQN04/m3cahl2dDFxFIXON9pU0U03 /DXJMEN3RPWPlofkzhCYODVOi6NOVlq0+lHhHFAYH2y7gTE7aBQNE6YOnbcL4Edxf8ZU ZqbjlyjDsk+LWfFOU7Zi4XW2W8KPNjpXxnqaKhfVhHTp9fTZDwaadM4hqJsRisMyy28b EobA==
X-Gm-Message-State: AG10YOS5xAy6Z194qCHhavxZuOEZW3BqiVhz/sqxRAuw1ksABVmkFws16B2OakTo7odML0Xjm9B5yR2jO7FbYQ==
MIME-Version: 1.0
X-Received: by 10.37.36.136 with SMTP id k130mr12913858ybk.102.1456092821628;  Sun, 21 Feb 2016 14:13:41 -0800 (PST)
Received: by 10.37.89.195 with HTTP; Sun, 21 Feb 2016 14:13:41 -0800 (PST)
In-Reply-To: <CCDF6314-688E-49FE-B501-1448815E6CC4@gmail.com>
References: <CCDF6314-688E-49FE-B501-1448815E6CC4@gmail.com>
Date: Sun, 21 Feb 2016 16:13:41 -0600
Message-ID: <CAHBDyN6A+OX9GKOZVXJqrw+71ZsLX=tSPueC-NVvLUfoOr0HKw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: James Winterbottom <a.james.winterbottom@gmail.com>
Content-Type: multipart/alternative; boundary=001a113ce16a64b313052c4f0796
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/zhuXDtdy4VFsYsTIkCpJA4T9uOw>
Cc: DISPATCH list <dispatch@ietf.org>
Subject: Re: [dispatch] Please can we dispatch draft-winterbottom-dispatch-locparam-01?
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Feb 2016 22:13:44 -0000

--001a113ce16a64b313052c4f0796
Content-Type: text/plain; charset=UTF-8

At this point, there's nothing more for you do unless someone makes
comments on the document on the mailing list.  The chairs and ADs are
currently discussing how best to progress the work item.

Regards,
Mary.

On Sun, Feb 21, 2016 at 1:06 AM, James Winterbottom <
a.james.winterbottom@gmail.com> wrote:

> Hi Dispatch Chairs,
>
> This document has been updated for some time with the changes requested by
> WG participants so that it can be dispatched.
> This work is required for ongoing ETSI work.
>
> Please can you let me know if there is anything more that I need to do to
> help this document on this way?
>
> Cheers
> James
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>

--001a113ce16a64b313052c4f0796
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">At this point, there&#39;s nothing more for you do unless =
someone makes comments on the document on the mailing list.=C2=A0 The chair=
s and ADs are currently discussing how best to progress the work item.<div>=
<br></div><div>Regards,</div><div>Mary.=C2=A0</div></div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Sun, Feb 21, 2016 at 1:06 AM, Ja=
mes Winterbottom <span dir=3D"ltr">&lt;<a href=3D"mailto:a.james.winterbott=
om@gmail.com" target=3D"_blank">a.james.winterbottom@gmail.com</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">Hi Dispatch Chairs,<br>
<br>
This document has been updated for some time with the changes requested by =
WG participants so that it can be dispatched.<br>
This work is required for ongoing ETSI work.<br>
<br>
Please can you let me know if there is anything more that I need to do to h=
elp this document on this way?<br>
<br>
Cheers<br>
James<br>
<br>
_______________________________________________<br>
dispatch mailing list<br>
<a href=3D"mailto:dispatch@ietf.org">dispatch@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dispatch</a><br>
</blockquote></div><br></div>

--001a113ce16a64b313052c4f0796--


From nobody Sun Feb 21 14:26:56 2016
Return-Path: <a.james.winterbottom@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 944A71A8AA4 for <dispatch@ietfa.amsl.com>; Sun, 21 Feb 2016 14:26:54 -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, SPF_PASS=-0.001] autolearn=ham
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 TInbDcB2EBcF for <dispatch@ietfa.amsl.com>; Sun, 21 Feb 2016 14:26:53 -0800 (PST)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 E18441A6FC0 for <dispatch@ietf.org>; Sun, 21 Feb 2016 14:26:52 -0800 (PST)
Received: by mail-pf0-x234.google.com with SMTP id x65so81578662pfb.1 for <dispatch@ietf.org>; Sun, 21 Feb 2016 14:26:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=HbuI3BCW/B/gwy3Kk7Zn3fb8Z9p5vGbMK3ew+TTslek=; b=cUziyJq6FBoEPKW5WSijzABhHrvrof2c/ZOnMbqoLX+WKZDA58yTHsrTUm3TVxMyAR 1cb/GSeP/QmiVmOR/0dvDpGr2nROnIdpqzgzTqQLeM+8jBYRdLn/nm516Ceme8nfr9nH kA15aFSPdqAhzs+bKRIp/Kw2e7zhEJGr0fh9aSN1NCTLljR/e678nAe9vVxoY38tmV0t wuvjH7dF37PHfbCkLzUmiA+tGehVLxtSfdGuIN8c4i2gM+1Xb/lSBzLstSTu87MA1FLn VV9WiNlEkjv0/BXO1C3ulL/ITjg7KjOH5gsah0BlpEDOA8mGZ02EH32ZQyfkZ0UVP8vj XfcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=HbuI3BCW/B/gwy3Kk7Zn3fb8Z9p5vGbMK3ew+TTslek=; b=fhAIjESBt8vEZdBjV96jsPKRzxveF0FBS0xOol/XCIDsnUfUItaxNqeDdp1ypF9MW/ YKoRatPJGvvYjkFi3L626BsPWCJ+tZ8JrSYcWCGN/gyjJyehnO7ICa29U0Z7r+nqSA7Z CwSfQUF04aW1n8PUL35JrALOjtwNW/bHJefXfotdG4FVNpNSlF9ehOO5mCU5LDdJwFKn DyG0U6RclyNoHzRFjN7R/TOoqlAA3omo9BgqUojHkbcbC0OVWioF49UE55eep5T7qAOV PCPSy1B6MSmFWklVnPJnjrfwhxT3JvMkLIAne4MV8L75m1eh6D+ov3iq/6aitQilSHdj J5pA==
X-Gm-Message-State: AG10YOTsOhUNpbwWOcGFDxsFOHMsJGuRFszxyk6Cb0CfIKzSAC9CfKWSQXkiEoZAjVqRNQ==
X-Received: by 10.98.70.28 with SMTP id t28mr33812574pfa.110.1456093612562; Sun, 21 Feb 2016 14:26:52 -0800 (PST)
Received: from [10.172.51.119] ([1.129.17.41]) by smtp.gmail.com with ESMTPSA id d65sm31805446pfb.74.2016.02.21.14.26.50 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 21 Feb 2016 14:26:51 -0800 (PST)
References: <CCDF6314-688E-49FE-B501-1448815E6CC4@gmail.com> <CAHBDyN6A+OX9GKOZVXJqrw+71ZsLX=tSPueC-NVvLUfoOr0HKw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAHBDyN6A+OX9GKOZVXJqrw+71ZsLX=tSPueC-NVvLUfoOr0HKw@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-8D7B103B-F19B-4DE3-A15B-396625F68032
Content-Transfer-Encoding: 7bit
Message-Id: <1FD8C7E4-C9A7-4F95-870D-8F705D85C1A1@gmail.com>
X-Mailer: iPhone Mail (11D201)
From: James Winterbottom <a.james.winterbottom@gmail.com>
Date: Mon, 22 Feb 2016 09:26:45 +1100
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/Zl8qf8668iG71pUw36EoqIT-t0k>
Cc: DISPATCH list <dispatch@ietf.org>
Subject: Re: [dispatch] Please can we dispatch draft-winterbottom-dispatch-locparam-01?
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Feb 2016 22:26:54 -0000

--Apple-Mail-8D7B103B-F19B-4DE3-A15B-396625F68032
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Thanks Mary.

Sent from my iPhone

> On 22 Feb 2016, at 9:13 am, Mary Barnes <mary.ietf.barnes@gmail.com> wrote=
:
>=20
> At this point, there's nothing more for you do unless someone makes commen=
ts on the document on the mailing list.  The chairs and ADs are currently di=
scussing how best to progress the work item.
>=20
> Regards,
> Mary.=20
>=20
>> On Sun, Feb 21, 2016 at 1:06 AM, James Winterbottom <a.james.winterbottom=
@gmail.com> wrote:
>> Hi Dispatch Chairs,
>>=20
>> This document has been updated for some time with the changes requested b=
y WG participants so that it can be dispatched.
>> This work is required for ongoing ETSI work.
>>=20
>> Please can you let me know if there is anything more that I need to do to=
 help this document on this way?
>>=20
>> Cheers
>> James
>>=20
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>=20

--Apple-Mail-8D7B103B-F19B-4DE3-A15B-396625F68032
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Thanks Mary.<br><br>Sent from my iPhone</div><div><br>On 22 Feb 2016, at 9:13 am, Mary Barnes &lt;<a href="mailto:mary.ietf.barnes@gmail.com">mary.ietf.barnes@gmail.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">At this point, there's nothing more for you do unless someone makes comments on the document on the mailing list.&nbsp; The chairs and ADs are currently discussing how best to progress the work item.<div><br></div><div>Regards,</div><div>Mary.&nbsp;</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 21, 2016 at 1:06 AM, James Winterbottom <span dir="ltr">&lt;<a href="mailto:a.james.winterbottom@gmail.com" target="_blank">a.james.winterbottom@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Dispatch Chairs,<br>
<br>
This document has been updated for some time with the changes requested by WG participants so that it can be dispatched.<br>
This work is required for ongoing ETSI work.<br>
<br>
Please can you let me know if there is anything more that I need to do to help this document on this way?<br>
<br>
Cheers<br>
James<br>
<br>
_______________________________________________<br>
dispatch mailing list<br>
<a href="mailto:dispatch@ietf.org">dispatch@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/dispatch" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/dispatch</a><br>
</blockquote></div><br></div>
</div></blockquote></body></html>
--Apple-Mail-8D7B103B-F19B-4DE3-A15B-396625F68032--


From nobody Mon Feb 22 00:16:14 2016
Return-Path: <bruno.chatras@orange.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 559FC1ACCF0 for <dispatch@ietfa.amsl.com>; Mon, 22 Feb 2016 00:16:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.904
X-Spam-Level: 
X-Spam-Status: No, score=-0.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
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 5_hXxswPpyo0 for <dispatch@ietfa.amsl.com>; Mon, 22 Feb 2016 00:16:11 -0800 (PST)
Received: from relais-inet.orange.com (relais-nor35.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9279E1ACCE0 for <dispatch@ietf.org>; Mon, 22 Feb 2016 00:16:11 -0800 (PST)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id E482B400F2; Mon, 22 Feb 2016 09:16:09 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.75]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 9EAF41A006E; Mon, 22 Feb 2016 09:16:09 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([fe80::787e:db0c:23c4:71b3]) by OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe%19]) with mapi id 14.03.0279.002; Mon, 22 Feb 2016 09:16:09 +0100
From: <bruno.chatras@orange.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, James Winterbottom <a.james.winterbottom@gmail.com>
Thread-Topic: [dispatch] Please can we dispatch draft-winterbottom-dispatch-locparam-01?
Thread-Index: AQHRbPUkv0vWjz9UnU6aJ0Yfn7NunJ83tfAQ
Date: Mon, 22 Feb 2016 08:16:08 +0000
Message-ID: <15061_1456128969_56CAC3C9_15061_3198_6_88CAD1D4E8773F42858B58CAA28272A015DD33AE@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <CCDF6314-688E-49FE-B501-1448815E6CC4@gmail.com> <CAHBDyN6A+OX9GKOZVXJqrw+71ZsLX=tSPueC-NVvLUfoOr0HKw@mail.gmail.com>
In-Reply-To: <CAHBDyN6A+OX9GKOZVXJqrw+71ZsLX=tSPueC-NVvLUfoOr0HKw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_88CAD1D4E8773F42858B58CAA28272A015DD33AEOPEXCLILM23corp_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/BwkPwrdbDjlJX65fsYXNd00PYe4>
Cc: DISPATCH list <dispatch@ietf.org>
Subject: Re: [dispatch] Please can we dispatch draft-winterbottom-dispatch-locparam-01?
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2016 08:16:13 -0000

--_000_88CAD1D4E8773F42858B58CAA28272A015DD33AEOPEXCLILM23corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhpcyBuZXcgcGFyYW1ldGVyIHJlc3BvbmRzIHRvIGFuIEVDIHJlcXVpcmVtZW50IGFuZCBFVFNJ
ICBpbnRlbmRzIHRvIHJlZmVyZW5jZSB0aGlzIGRvY3VtZW50IGluIGEgc3BlY2lmaWNhdGlvbiBj
dXJyZW50bHkgdW5kZXIgZGV2ZWxvcG1lbnQuIFNvLCB1bmxlc3MgdGhlcmUgYXJlIHRlY2huaWNh
bCBjb21tZW50cyB0byBiZSByZXNvbHZlZCwgSSBob3BlIHRoaXMgd29yayBpdGVtIHdpbGwgcHJv
Z3Jlc3MgcXVpY2tseS4NCkJydW5vDQoNCg0KRGUgOiBkaXNwYXRjaCBbbWFpbHRvOmRpc3BhdGNo
LWJvdW5jZXNAaWV0Zi5vcmddIERlIGxhIHBhcnQgZGUgTWFyeSBCYXJuZXMNCkVudm95w6kgOiBk
aW1hbmNoZSAyMSBmw6l2cmllciAyMDE2IDIzOjE0DQrDgCA6IEphbWVzIFdpbnRlcmJvdHRvbQ0K
Q2MgOiBESVNQQVRDSCBsaXN0DQpPYmpldCA6IFJlOiBbZGlzcGF0Y2hdIFBsZWFzZSBjYW4gd2Ug
ZGlzcGF0Y2ggZHJhZnQtd2ludGVyYm90dG9tLWRpc3BhdGNoLWxvY3BhcmFtLTAxPw0KDQpBdCB0
aGlzIHBvaW50LCB0aGVyZSdzIG5vdGhpbmcgbW9yZSBmb3IgeW91IGRvIHVubGVzcyBzb21lb25l
IG1ha2VzIGNvbW1lbnRzIG9uIHRoZSBkb2N1bWVudCBvbiB0aGUgbWFpbGluZyBsaXN0LiAgVGhl
IGNoYWlycyBhbmQgQURzIGFyZSBjdXJyZW50bHkgZGlzY3Vzc2luZyBob3cgYmVzdCB0byBwcm9n
cmVzcyB0aGUgd29yayBpdGVtLg0KDQpSZWdhcmRzLA0KTWFyeS4NCg0KT24gU3VuLCBGZWIgMjEs
IDIwMTYgYXQgMTowNiBBTSwgSmFtZXMgV2ludGVyYm90dG9tIDxhLmphbWVzLndpbnRlcmJvdHRv
bUBnbWFpbC5jb208bWFpbHRvOmEuamFtZXMud2ludGVyYm90dG9tQGdtYWlsLmNvbT4+IHdyb3Rl
Og0KSGkgRGlzcGF0Y2ggQ2hhaXJzLA0KDQpUaGlzIGRvY3VtZW50IGhhcyBiZWVuIHVwZGF0ZWQg
Zm9yIHNvbWUgdGltZSB3aXRoIHRoZSBjaGFuZ2VzIHJlcXVlc3RlZCBieSBXRyBwYXJ0aWNpcGFu
dHMgc28gdGhhdCBpdCBjYW4gYmUgZGlzcGF0Y2hlZC4NClRoaXMgd29yayBpcyByZXF1aXJlZCBm
b3Igb25nb2luZyBFVFNJIHdvcmsuDQoNClBsZWFzZSBjYW4geW91IGxldCBtZSBrbm93IGlmIHRo
ZXJlIGlzIGFueXRoaW5nIG1vcmUgdGhhdCBJIG5lZWQgdG8gZG8gdG8gaGVscCB0aGlzIGRvY3Vt
ZW50IG9uIHRoaXMgd2F5Pw0KDQpDaGVlcnMNCkphbWVzDQoNCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQpkaXNwYXRjaCBtYWlsaW5nIGxpc3QNCmRpc3Bh
dGNoQGlldGYub3JnPG1haWx0bzpkaXNwYXRjaEBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vZGlzcGF0Y2gNCg0KCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KCkNlIG1lc3NhZ2UgZXQg
c2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQgY29udGVuaXIgZGVzIGluZm9ybWF0aW9ucyBjb25m
aWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRvaXZlbnQgZG9uYwpwYXMgZXRyZSBk
aWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5zIGF1dG9yaXNhdGlvbi4gU2kgdm91cyBh
dmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlcgphIGwn
ZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBM
ZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9u
LApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRl
IGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVyY2kuCgpUaGlzIG1lc3NhZ2UgYW5kIGl0
cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgb3IgcHJpdmlsZWdlZCBpbmZv
cm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkgbGF3Owp0aGV5IHNob3VsZCBub3QgYmUg
ZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4KSWYgeW91
IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2Vu
ZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMuCkFzIGVtYWls
cyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQg
aGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNpZmllZC4KVGhhbmsgeW91LgoK

--_000_88CAD1D4E8773F42858B58CAA28272A015DD33AEOPEXCLILM23corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1z
ZXJpZiI7DQoJY29sb3I6YmxhY2s7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6
bm9ybWFsO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0K
CW1hcmdpbjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3JkU2VjdGlv
bjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+
PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8
L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0
IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNo
YXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRlIiIGxp
bms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOmJsYWNrIj5UaGlzIG5ldyBwYXJhbWV0ZXIgcmVzcG9uZHMgdG8gYW4gRUMgcmVxdWly
ZW1lbnQgYW5kIEVUU0kgJm5ic3A7aW50ZW5kcyB0byByZWZlcmVuY2UgdGhpcyBkb2N1bWVudCBp
biBhIHNwZWNpZmljYXRpb24gY3VycmVudGx5IHVuZGVyIGRldmVsb3BtZW50LiBTbywgdW5sZXNz
DQogdGhlcmUgYXJlIHRlY2huaWNhbCBjb21tZW50cyB0byBiZSByZXNvbHZlZCwgSSBob3BlIHRo
aXMgd29yayBpdGVtIHdpbGwgcHJvZ3Jlc3MgcXVpY2tseS4NCjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOmJsYWNrIj5CcnVubzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDsiPkRlJm5ic3A7Ojwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPiBkaXNwYXRjaCBbbWFpbHRvOmRpc3BhdGNoLWJvdW5jZXNAaWV0Zi5vcmdd
DQo8Yj5EZSBsYSBwYXJ0IGRlPC9iPiBNYXJ5IEJhcm5lczxicj4NCjxiPkVudm95w6kmbmJzcDs6
PC9iPiBkaW1hbmNoZSAyMSBmw6l2cmllciAyMDE2IDIzOjE0PGJyPg0KPGI+w4AmbmJzcDs6PC9i
PiBKYW1lcyBXaW50ZXJib3R0b208YnI+DQo8Yj5DYyZuYnNwOzo8L2I+IERJU1BBVENIIGxpc3Q8
YnI+DQo8Yj5PYmpldCZuYnNwOzo8L2I+IFJlOiBbZGlzcGF0Y2hdIFBsZWFzZSBjYW4gd2UgZGlz
cGF0Y2ggZHJhZnQtd2ludGVyYm90dG9tLWRpc3BhdGNoLWxvY3BhcmFtLTAxPzxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkF0IHRoaXMgcG9pbnQsIHRoZXJlJ3Mgbm90aGlu
ZyBtb3JlIGZvciB5b3UgZG8gdW5sZXNzIHNvbWVvbmUgbWFrZXMgY29tbWVudHMgb24gdGhlIGRv
Y3VtZW50IG9uIHRoZSBtYWlsaW5nIGxpc3QuJm5ic3A7IFRoZSBjaGFpcnMgYW5kIEFEcyBhcmUg
Y3VycmVudGx5IGRpc2N1c3NpbmcgaG93IGJlc3QgdG8gcHJvZ3Jlc3MgdGhlIHdvcmsgaXRlbS48
bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlJlZ2FyZHMsPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5NYXJ5LiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5PbiBTdW4sIEZlYiAyMSwgMjAxNiBhdCAxOjA2IEFNLCBKYW1lcyBXaW50ZXJib3R0b20gJmx0
OzxhIGhyZWY9Im1haWx0bzphLmphbWVzLndpbnRlcmJvdHRvbUBnbWFpbC5jb20iIHRhcmdldD0i
X2JsYW5rIj5hLmphbWVzLndpbnRlcmJvdHRvbUBnbWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIERpc3BhdGNoIENoYWlycyw8YnI+
DQo8YnI+DQpUaGlzIGRvY3VtZW50IGhhcyBiZWVuIHVwZGF0ZWQgZm9yIHNvbWUgdGltZSB3aXRo
IHRoZSBjaGFuZ2VzIHJlcXVlc3RlZCBieSBXRyBwYXJ0aWNpcGFudHMgc28gdGhhdCBpdCBjYW4g
YmUgZGlzcGF0Y2hlZC48YnI+DQpUaGlzIHdvcmsgaXMgcmVxdWlyZWQgZm9yIG9uZ29pbmcgRVRT
SSB3b3JrLjxicj4NCjxicj4NClBsZWFzZSBjYW4geW91IGxldCBtZSBrbm93IGlmIHRoZXJlIGlz
IGFueXRoaW5nIG1vcmUgdGhhdCBJIG5lZWQgdG8gZG8gdG8gaGVscCB0aGlzIGRvY3VtZW50IG9u
IHRoaXMgd2F5Pzxicj4NCjxicj4NCkNoZWVyczxicj4NCkphbWVzPGJyPg0KPGJyPg0KX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpkaXNwYXRjaCBt
YWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86ZGlzcGF0Y2hAaWV0Zi5vcmciPmRpc3Bh
dGNoQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vZGlzcGF0Y2giIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2Rpc3BhdGNoPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8UFJFPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18KCkNlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQg
Y29udGVuaXIgZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVz
IGV0IG5lIGRvaXZlbnQgZG9uYwpwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGll
cyBzYW5zIGF1dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJy
ZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlcgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBh
aW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBl
dGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNw
b25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZp
ZS4gTWVyY2kuCgpUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBj
b25maWRlbnRpYWwgb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0
ZWQgYnkgbGF3Owp0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVk
IHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBp
biBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdl
IGFuZCBpdHMgYXR0YWNobWVudHMuCkFzIGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlz
IG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2Vk
IG9yIGZhbHNpZmllZC4KVGhhbmsgeW91Lgo8L1BSRT48L2JvZHk+DQo8L2h0bWw+DQo=

--_000_88CAD1D4E8773F42858B58CAA28272A015DD33AEOPEXCLILM23corp_--


From nobody Mon Feb 22 09:49:48 2016
Return-Path: <bclaise@cisco.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC4821B2FDF; Mon, 22 Feb 2016 09:49:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.507
X-Spam-Level: 
X-Spam-Status: No, score=-14.507 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 lrj5e82H6ly2; Mon, 22 Feb 2016 09:49:43 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64C511B2E54; Mon, 22 Feb 2016 09:49:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2893; q=dns/txt; s=iport; t=1456163382; x=1457372982; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=ej2Y6phuPpA4QzNaWdZIIoVWInNcR3EwHFI6/wU8yeI=; b=OdsrTVfwRXmae+Wum/PqvpSYWkea/V9pt3cwMtgzg9xehqgr3YqcuK5y dQ8WxfCRNhnBH96edFDhuS4yyMPGMGPRy6bzV4NgqcBaKr8PWsHB/KM3O fNzIVBMGsv9dMvsDdlk360iLcRgJoLMagaOs9C94QAA79YfA2Cwmbo2Z1 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CsBADeSMtW/xbLJq1UCoQMbbhBhAceh?= =?us-ascii?q?W8Cgg0BAQEBAQFlJ4RBAQEBAwE4QRALGAklDwJGBg0IAQGIDwgOuSIBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBEwSGEoQ6hAUGCwGEWAEEh1aPMYVXiAeBXIRDgwIjhS+Fc?= =?us-ascii?q?ohXYoNlOy4BAQEBhnuBMQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.22,485,1449532800"; d="scan'208";a="625622599"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Feb 2016 17:49:40 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u1MHndBs002051; Mon, 22 Feb 2016 17:49:40 GMT
To: Ben Campbell <ben@nostrum.com>
References: <20160204153934.14557.85409.idtracker@ietfa.amsl.com> <C9FEC1BB-4CAD-4FDF-AC40-B9DE882D51AC@nostrum.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <56CB4A33.80904@cisco.com>
Date: Mon, 22 Feb 2016 18:49:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <C9FEC1BB-4CAD-4FDF-AC40-B9DE882D51AC@nostrum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/auIB_xKV-rsuJlw28RumxYgS524>
Cc: dispatch@ietf.org, The IESG <iesg@ietf.org>, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Benoit Claise's No Objection on charter-ietf-dispatch-02-01: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2016 17:49:44 -0000

On 2/9/2016 12:58 AM, Ben Campbell wrote:
> Benoit,
>
> Does the update at [1] address your original concern?
Yes, thank you.

Regards, B.
>
> Thanks!
>
> Ben.
>
> [1] 
> https://www.ietf.org/rfcdiff?url1=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-01.txt&url2=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-02.txt.
>
> On 4 Feb 2016, at 9:39, Benoit Claise wrote:
>
>> Benoit Claise has entered the following ballot position for
>> charter-ietf-dispatch-02-01: No Objection
>>
>> 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-dispatch/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> I received the necessary clarifications from both Barry and Ben during
>> the IESG telechat. Thanks, Benoit
>> ============================================================================= 
>>
>>
>>
>> (*)  Disclaimer: I've not been following RAI/ART work in the IETF and I
>> don't know whether the DISPATCH process has been efficient or not. So
>> I'll mainly make observations.
>>
>> I understand Harald's point,
>> https://mailarchive.ietf.org/arch/msg/ietf/-kiAbvZDTCLets4szoXmaCIgrs4,
>> When I read the charter, it's like an extra procedure, specific to ART.
>> For example, if I want a BoF, I must first go to DISPATCH to get their
>> approval? Same thing for AD-sponsored document?
>>
>>  The Dispatch working group is chartered to consider proposals for
>> new
>>  work in the ART area and identify, or help create, an appropriate
>> venue
>>  for the work.
>>
>> Btw, no change here: this sentence is basically unchanged compared to 
>> the
>> previous charter.
>>
>> In the past, I was told that DISPATCH was similar to the OPSAWG WG.
>> Let me observe it's not. "The DISPATCH WG will not do any protocol 
>> work",
>> while OPSAWG might.
>>> From the OPSAWG charter:
>>
>>  The Operations and Management Area receives occasional proposals for
>>  the development and publication of RFCs dealing with operational and
>>  management topics that are not in scope of an existing working group
>>  and do not justify the formation of a new working group. The OPSAWG
>>  will serve as the forum for developing such work items in the IETF.
>>
>> Obviously, redirecting work to existing WGs is also an OPSAWG task.
>> And when the work is substantial, a new WG can even be created. Ex: EMAN
>> in the past
>>
>> I prefer the OPSAWG approach (*).
> .
>


From nobody Mon Feb 22 11:08:12 2016
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72BD01B3811 for <dispatch@ietfa.amsl.com>; Mon, 22 Feb 2016 11:08:11 -0800 (PST)
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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
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 wPrK3QmB9YdP for <dispatch@ietfa.amsl.com>; Mon, 22 Feb 2016 11:08:10 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F15601B3826 for <dispatch@ietf.org>; Mon, 22 Feb 2016 11:08:09 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id CAE1920A86 for <dispatch@ietf.org>; Mon, 22 Feb 2016 14:02:48 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 22 Feb 2016 14:02:48 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=/9PLUrDN251ipNo7WEfMI5jiu5Y=; b=EmKVUk DhSiMS9oFODdeYGR3JqyQBICVxYX9AHQBP6o5n2HyO4Ldu5xwMmQ2bzf5gcr1Jgf n2Z8WHbWVlZAyBxm8xbD0G/BszORwgA4cfCbct/hls1/6VExUqBDoBR7ogO64U2b KOlb40SdBBvaXmrgnMOk0c232L5LPucI6oPUU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=/9PLUrDN251ipNo 7WEfMI5jiu5Y=; b=Yy5S+h5QvU3pcIAASG9qn09WmvlW2VbhhsjlfGeky5IEyHL n0r8XHBQZZ/vvYLsELzTHWQEoR8xQcUloqCWJD+D9SvYPHCyYz6U+sHbmLzPC7qA mj4K48vVI9NO48ix65spVrxCUs+jQEZXjEcYDMH6PPsySapH9Aet9JGasHV4=
X-Sasl-enc: pP4AEbofCCERPg+KpQRKkJJnaIWCx7tpTkWeTxn7s0lu 1456167767
Received: from [172.22.50.50] (unknown [62.232.206.186]) by mail.messagingengine.com (Postfix) with ESMTPA id 2478CC00022; Mon, 22 Feb 2016 14:02:47 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13D15)
In-Reply-To: <C9FEC1BB-4CAD-4FDF-AC40-B9DE882D51AC@nostrum.com>
Date: Mon, 22 Feb 2016 19:03:44 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <12B6528D-71C9-44E2-B1E2-4CE8767108A4@fastmail.fm>
References: <20160204153934.14557.85409.idtracker@ietfa.amsl.com> <C9FEC1BB-4CAD-4FDF-AC40-B9DE882D51AC@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/7GZRFNIeLpliC8PKuD25tmEZWhE>
Cc: Benoit Claise <bclaise@cisco.com>, dispatch@ietf.org, The IESG <iesg@ietf.org>, dispatch-chairs@ietf.org
Subject: Re: [dispatch] Benoit Claise's No Objection on charter-ietf-dispatch-02-01: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2016 19:08:11 -0000

Hi Ben,

> On 8 Feb 2016, at 23:58, Ben Campbell <ben@nostrum.com> wrote:
>=20
> Benoit,
>=20
> Does the update at [1] address your original concern?
>=20
> Thanks!
>=20
> Ben.
>=20
> [1] https://www.ietf.org/rfcdiff?url1=3Dhttps%3A%2F%2Fdatatracker.ietf.org=
%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-01.txt&url2=3Dhttps%3A%2F%=
2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-02.=
txt.

I think this is an improvement!
>=20
>> On 4 Feb 2016, at 9:39, Benoit Claise wrote:
>>=20
>> Benoit Claise has entered the following ballot position for
>> charter-ietf-dispatch-02-01: No Objection
>>=20
>> 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.)
>>=20
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/charter-ietf-dispatch/
>>=20
>>=20
>>=20
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>=20
>> I received the necessary clarifications from both Barry and Ben during
>> the IESG telechat. Thanks, Benoit
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

>>=20
>>=20
>> (*)  Disclaimer: I've not been following RAI/ART work in the IETF and I
>> don't know whether the DISPATCH process has been efficient or not. So
>> I'll mainly make observations.
>>=20
>> I understand Harald's point,
>> https://mailarchive.ietf.org/arch/msg/ietf/-kiAbvZDTCLets4szoXmaCIgrs4,
>> When I read the charter, it's like an extra procedure, specific to ART.
>> For example, if I want a BoF, I must first go to DISPATCH to get their
>> approval? Same thing for AD-sponsored document?
>>=20
>> The Dispatch working group is chartered to consider proposals for
>> new
>> work in the ART area and identify, or help create, an appropriate
>> venue
>> for the work.
>>=20
>> Btw, no change here: this sentence is basically unchanged compared to the=

>> previous charter.
>>=20
>> In the past, I was told that DISPATCH was similar to the OPSAWG WG.
>> Let me observe it's not. "The DISPATCH WG will not do any protocol work",=

>> while OPSAWG might.
>>> =46rom the OPSAWG charter:
>>=20
>> The Operations and Management Area receives occasional proposals for
>> the development and publication of RFCs dealing with operational and
>> management topics that are not in scope of an existing working group
>> and do not justify the formation of a new working group. The OPSAWG
>> will serve as the forum for developing such work items in the IETF.
>>=20
>> Obviously, redirecting work to existing WGs is also an OPSAWG task.
>> And when the work is substantial, a new WG can even be created. Ex: EMAN
>> in the past
>>=20
>> I prefer the OPSAWG approach (*).
>=20


From nobody Fri Feb 26 10:47:13 2016
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 868BA1B2E66 for <dispatch@ietfa.amsl.com>; Fri, 26 Feb 2016 10:47:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 in-UFhPAW7w3 for <dispatch@ietfa.amsl.com>; Fri, 26 Feb 2016 10:47:09 -0800 (PST)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 AC8751B2E52 for <dispatch@ietf.org>; Fri, 26 Feb 2016 10:47:09 -0800 (PST)
Received: by mail-yw0-x22b.google.com with SMTP id e63so75884836ywc.3 for <dispatch@ietf.org>; Fri, 26 Feb 2016 10:47:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=ZcsHGSUhnsoUT2ZL9rYO/vL0YPD2Lh7cUmi6ROtFX2M=; b=q2tyqZy/KLbChUGbJ67Lr/2U6aCYDfU/nFd5peqAsEjUk+AZrYkXw4AS48fyq5sNxZ NfERHCuXDUo9/cXG9Qb8LeVkMjYgxR7uoHUYJqH94DzkIPhcOIffnI8loMAzI52J63Hv 9CJE4EieS9hwxg695bDWSCqAZH93kyV4ITYhq7Tbff8ROD2tMNCo3g1eaa1vQAcua3mc +5+CijfYnkk7c1+jc5A0AysBWuMq1WkJHChvVy0Nvrg+EsSVzBRMcR/b21und+f+thwQ A++KCvktTrtlhTg3p5CNkgYSjRUX+QYrB6LD4+ie0LfMj2vfDkm2iFbMjRon1/rsqq2V 2vsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ZcsHGSUhnsoUT2ZL9rYO/vL0YPD2Lh7cUmi6ROtFX2M=; b=ZcH02dcmb+PjZlzmOffJbIXwKZcWCNBBDcfOlwusRTTGdShi/1NKaOggSzVsr/swLX uEXROsX4GrfjwJDCLU9jFWduYCD7YOxd618frcJr4Vab7QArfG04eWelrJypmupYtQ0T TRIM4yBWhlOOuReM5dgYL3D4II92APQosip6svGVW3mCvMWxWqwRiwGesgTAb6d8YC5A EQmH0HD19KpeaqpmUnoj+biiaVpDRWif0kYkvIK+TQw0yw73OcjHFAJQJPc1LzTXoz/7 YNbc8asJbMgjY2s+h03cY1zQNSQgJ+Mj77nlN0rncjxFJMOIbPN8A9X13cmmvxQmPT7X GiMg==
X-Gm-Message-State: AD7BkJL0Teyf4dv32px656bBaqO3piPztWytLk9mNtAVXUxuLmxY/M9B1yZCOu8BMQK+TjOesdjG0MS+6MyUzg==
MIME-Version: 1.0
X-Received: by 10.129.34.133 with SMTP id i127mr1848415ywi.153.1456512429006;  Fri, 26 Feb 2016 10:47:09 -0800 (PST)
Received: by 10.37.89.195 with HTTP; Fri, 26 Feb 2016 10:47:08 -0800 (PST)
In-Reply-To: <A3A8B6D2-7664-45B3-B740-DA345B5DFF81@gmail.com>
References: <A3A8B6D2-7664-45B3-B740-DA345B5DFF81@gmail.com>
Date: Fri, 26 Feb 2016 12:47:08 -0600
Message-ID: <CAHBDyN469G3DRTWgFR8t8gN1wym_PrGNAV+6ur3sr20fCL_8Qw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: James Winterbottom <a.james.winterbottom@gmail.com>
Content-Type: multipart/alternative; boundary=001a114091bcf12abb052cb0b9c8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/wgGalkYWVHmJnky7yC39v-4CRnk>
Cc: DISPATCH list <dispatch@ietf.org>
Subject: Re: [dispatch] draft-winterbottom-dispatch-locparam-01
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2016 18:47:11 -0000

--001a114091bcf12abb052cb0b9c8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

James - thanks for updating the document and Paul thanks for reviewing the
updates.

The chairs and ADs have had some offline discussions about how to move this
forward.  The current proposal is to AD sponsor the document.  However, we
would also like feedback from the WG, in particular folks that have been
active in ECRIT and GEOPRIV WGs, as to whether this seems reasonable or
whether we might need to consider a "mini" WG.    We do think that
additional text is necessary to further emphasize that this is only
recommended to be used in the context of a trusted network.

Please respond no later than Friday, March 11 , 2016.

Regards,
Mary


On Thu, Feb 4, 2016 at 3:45 AM, James Winterbottom <
a.james.winterbottom@gmail.com> wrote:

> Hi All,
>
> I was asked to make some updates to this document so that it could be
> dispatched.
> I made, what I think were the requested updates back in December and
> posted to the list but I haven=E2=80=99t heard anything back.
> ETSI needs this work as part of their M/493 stage-3 document so if there
> are further comments could they please be posted, otherwise can we please
> call for it to be dispatched somewhere?
>
> Cheers
> James
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>

--001a114091bcf12abb052cb0b9c8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>James - thanks for updating the document and Paul tha=
nks for reviewing the updates. =C2=A0<br></div><div><br></div><div>The chai=
rs and ADs have had some offline discussions about how to move this forward=
.=C2=A0 The current proposal is to AD sponsor the document.=C2=A0 However, =
we would also like feedback from the WG, in particular folks that have been=
 active in ECRIT and GEOPRIV WGs, as to whether this seems reasonable or wh=
ether we might need to consider a &quot;mini&quot; WG. =C2=A0 =C2=A0We do t=
hink that additional text is necessary to further emphasize that this is on=
ly recommended to be used in the context of a trusted network.</div><div><b=
r></div><div>Please respond no later than Friday, March 11 , 2016.</div><di=
v><br></div><div>Regards,</div><div>Mary</div><div><br></div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Thu, Feb 4, 2016 at 3:45 AM,=
 James Winterbottom <span dir=3D"ltr">&lt;<a href=3D"mailto:a.james.winterb=
ottom@gmail.com" target=3D"_blank">a.james.winterbottom@gmail.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">Hi All,<br>
<br>
I was asked to make some updates to this document so that it could be dispa=
tched.<br>
I made, what I think were the requested updates back in December and posted=
 to the list but I haven=E2=80=99t heard anything back.<br>
ETSI needs this work as part of their M/493 stage-3 document so if there ar=
e further comments could they please be posted, otherwise can we please cal=
l for it to be dispatched somewhere?<br>
<br>
Cheers<br>
James<br>
<br>
_______________________________________________<br>
dispatch mailing list<br>
<a href=3D"mailto:dispatch@ietf.org">dispatch@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dispatch</a><br>
</blockquote></div><br></div></div>

--001a114091bcf12abb052cb0b9c8--


From nobody Fri Feb 26 13:12:37 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B121B307D for <dispatch@ietfa.amsl.com>; Fri, 26 Feb 2016 13:12:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.307
X-Spam-Level: 
X-Spam-Status: No, score=-4.307 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=ham
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 4VuEMzBFD6LD for <dispatch@ietfa.amsl.com>; Fri, 26 Feb 2016 13:12:34 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 380D21B307A for <dispatch@ietf.org>; Fri, 26 Feb 2016 13:12:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4C0EFBE7B; Fri, 26 Feb 2016 21:12:32 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9NqQ51yNjmc9; Fri, 26 Feb 2016 21:12:31 +0000 (GMT)
Received: from [10.87.48.75] (unknown [86.46.31.86]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 9BB88BE73; Fri, 26 Feb 2016 21:12:30 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1456521151; bh=OePusRgknq4tTniW3lfi7XSlTJWTScC76zJXTWFxPdI=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=nBeHOjq6XvcF1V3Q58Si0h7BF35ZTKJXezndXTNYRUX/iphmI6CVjqNdEOnjCFis2 74MQdb72Eo5dSFAJiW4q9AjKwJ2nwcmEaBsVWT4c45fT5u7B2H3tPZQwaZLpDzlTQF fGthWerY5cfoGyYBMpXvTpG984P2Af0wJwvgTta4=
To: Mary Barnes <mary.ietf.barnes@gmail.com>, James Winterbottom <a.james.winterbottom@gmail.com>
References: <A3A8B6D2-7664-45B3-B740-DA345B5DFF81@gmail.com> <CAHBDyN469G3DRTWgFR8t8gN1wym_PrGNAV+6ur3sr20fCL_8Qw@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <56D0BFBD.8080000@cs.tcd.ie>
Date: Fri, 26 Feb 2016 21:12:29 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <CAHBDyN469G3DRTWgFR8t8gN1wym_PrGNAV+6ur3sr20fCL_8Qw@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms020400070907090803020308"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/lGgV_56mgNRvM3AWSW8Vinar-hM>
Cc: DISPATCH list <dispatch@ietf.org>
Subject: Re: [dispatch] draft-winterbottom-dispatch-locparam-01
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2016 21:12:36 -0000

This is a cryptographically signed message in MIME format.

--------------ms020400070907090803020308
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi Mary,

On 26/02/16 18:47, Mary Barnes wrote:
> only
> recommended to be used in the context of a trusted network.

What does that mean?

Ta,
S.


--------------ms020400070907090803020308
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjAyMjYy
MTEyMjlaMC8GCSqGSIb3DQEJBDEiBCD0MU3YMnNQfA9jP6Hbd2071RJKy4MGmIO1HN669vUz
BzBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQAoAR1VPOkbWbT8iTettJIitwhjxM66jozbBXhwLlpULlKWh2BavcfS
r3AqKJCpuPgv9CbKQwXZluEpiZZ0nS4QRT4/lQ/Dwmu0/i2BVSzGxzjbnQtOojurN7xUfJ/0
X5giccdp3glLwxEMePbaYcKgQWvFvai1cHnJP6CjABIaK2is29teZdImhu5URt9nJaMbGrDb
baFZniVcYj0jQTGOYtolNEbZrq2XC4suWobMpezAIX322JdCygB8QWDhV/FfTBMk2pky7+Zc
dJ/+kRGlKFYjn9wy+zSTRq45tgqtiw5ltcttP9QKtTu9sp7PWgQmacW/sO3OpGyEUBi7kzAj
AAAAAAAA
--------------ms020400070907090803020308--


From nobody Fri Feb 26 14:52:32 2016
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C84FB1B322B for <dispatch@ietfa.amsl.com>; Fri, 26 Feb 2016 14:52:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level: 
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006] autolearn=ham
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 NxO-hOHd2Ccs for <dispatch@ietfa.amsl.com>; Fri, 26 Feb 2016 14:52:29 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 9697C1B3227 for <dispatch@ietf.org>; Fri, 26 Feb 2016 14:52:29 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u1QMqLmK089653 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 26 Feb 2016 16:52:22 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
Date: Fri, 26 Feb 2016 16:52:21 -0600
Message-ID: <6ED851DB-7951-4CE0-8674-A49120881DD4@nostrum.com>
In-Reply-To: <56D0BFBD.8080000@cs.tcd.ie>
References: <A3A8B6D2-7664-45B3-B740-DA345B5DFF81@gmail.com> <CAHBDyN469G3DRTWgFR8t8gN1wym_PrGNAV+6ur3sr20fCL_8Qw@mail.gmail.com> <56D0BFBD.8080000@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5226)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/t2qYRbCBnIQ0xbOavIM-MHJs510>
Cc: DISPATCH list <dispatch@ietf.org>
Subject: Re: [dispatch] draft-winterbottom-dispatch-locparam-01
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2016 22:52:30 -0000

On 26 Feb 2016, at 15:12, Stephen Farrell wrote:

> Hi Mary,
>
> On 26/02/16 18:47, Mary Barnes wrote:
>> only
>> recommended to be used in the context of a trusted network.
>
> What does that mean?

I think the point is, the draft needs to say what it means :-).

And actually, the current version does have a Spec(T) [RFC 3325] 
reference. But I think the request here is for clarification of 
application scope assumptions. For example, it mentions 3GPP and ETSI 
architectures; do we expect its use to be limited to those 
architectures?

This probably goes beyond just trust issues.  For example, what happens 
when a recipient that does not understand this extension tries to 
interpret a location value that uses it.

Ben. (Who is answering off the top of his head, and apologizes in 
advance if he forgot something in the draft that answers all this).


From nobody Mon Feb 29 15:53:50 2016
Return-Path: <jon.peterson@neustar.biz>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0591C1A1A06 for <dispatch@ietfa.amsl.com>; Mon, 29 Feb 2016 15:53:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.266
X-Spam-Level: 
X-Spam-Status: No, score=-102.266 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, USER_IN_WHITELIST=-100] autolearn=ham
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 hjx9hxkUNkD8 for <dispatch@ietfa.amsl.com>; Mon, 29 Feb 2016 15:53:47 -0800 (PST)
Received: from mx0b-0018ba01.pphosted.com (mx0a-0018ba01.pphosted.com [67.231.149.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B997F1A03F9 for <dispatch@ietf.org>; Mon, 29 Feb 2016 15:53:47 -0800 (PST)
Received: from pps.filterd (m0078666.ppops.net [127.0.0.1]) by mx0a-0018ba01.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id u1TNr0Fu003036; Mon, 29 Feb 2016 18:53:46 -0500
Received: from stntexhc12.cis.neustar.com ([156.154.17.216]) by mx0a-0018ba01.pphosted.com with ESMTP id 21b8su8brg-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 29 Feb 2016 18:53:46 -0500
Received: from STNTEXMB10.cis.neustar.com ([169.254.5.140]) by stntexhc12.cis.neustar.com ([::1]) with mapi id 14.03.0279.002; Mon, 29 Feb 2016 18:53:44 -0500
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: Ben Campbell <ben@nostrum.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Thread-Topic: [dispatch] Reminder: Deadlines for IETF-95
Thread-Index: AQHRZAqTJ+2zqOwoS02MQXPireE1/p8n/OoAgBuhi4A=
Date: Mon, 29 Feb 2016 23:53:44 +0000
Message-ID: <D2F9BF7A.17C6C3%jon.peterson@neustar.biz>
References: <CAHBDyN4hgTg1o4On39C6sKwO9y=yy+46SEJB1DJrAfaUfhir=Q@mail.gmail.com> <8119825D-F91F-4494-AE59-39E3956B02F1@nostrum.com>
In-Reply-To: <8119825D-F91F-4494-AE59-39E3956B02F1@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.7.151005
x-originating-ip: [192.168.129.117]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EEDD5AAC05FDE64D9AABA32CBCE62929@neustar.biz>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-02-29_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1601100000 definitions=main-1602290454
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/oo07CgmvMHQ3qBGbzDCDCJ3T3Q4>
Cc: DISPATCH <dispatch@ietf.org>
Subject: Re: [dispatch] Reminder: Deadlines for IETF-95
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Feb 2016 23:53:49 -0000

I just wanted to confirm that Ben here is correct. This idea came out of a
discussion in Yokohama about identifying the best practices for media
security when setting up sessions with SIP, and in particular the glue
that binds security in SIP to SDP and to RTP. This would invoke things
like STIR, and would also potentially nod to more opportunistic approaches
like those outlined in Alan's draft, as media confidentiality is one of
the more important security properties in this post-PERPASS world of ours.

So, we expect to have a draft before the deadline - happy to discuss the
general topic here in the meantime if there's interest.

Jon Peterson
Neustar, Inc.

On 2/11/16, 5:56 PM, "dispatch on behalf of Ben Campbell"
<dispatch-bounces@ietf.org on behalf of ben@nostrum.com> wrote:

>Hi,
>
>I understand that Jon, Ekr, Richard, and Russ plan to submit a draft on
>security recommendations for point-to-point, SIP-signaled RTP in time
>for Buenos Aires. While I would be pleasantly surprised if the
>discussion is far enough along by then for a charter proposal, I think
>discussion in DISPATCH would be worthwhile.
>
>So, please consider this notice of their intent to propose a discussion
>topic, on their behalf.
>
>Thanks!
>
>Ben.
>
>On 10 Feb 2016, at 7:54, Mary Barnes wrote:
>
>> Hi all,
>>
>> Just a reminder of the DISPATCH WG deadlines for IETF-95:
>> https://trac.tools.ietf.org/wg/dispatch/trac/wiki
>>
>>
>>  - February 22, 2016. Cutoff date to notify the chairs/DISPATCH WG of
>>  plans to submit a proposal.
>>
>>
>>  - February 29, 2016. Cutoff for charter proposals for topics.
>>
>>
>>  - March 7, 2016. Announcement of topics that have been dispatched for
>>  IETF-95.
>>
>>
>>  - March 21, 2016. Draft deadline.
>>
>>
>> Regards,
>> Mary
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>
>_______________________________________________
>dispatch mailing list
>dispatch@ietf.org
>https://www.ietf.org/mailman/listinfo/dispatch


From nobody Mon Feb 29 23:05:04 2016
Return-Path: <oej@edvina.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42EB51B29CF for <dispatch@ietfa.amsl.com>; Mon, 29 Feb 2016 23:05:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, SPF_PASS=-0.001] autolearn=no
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 ApRdz1wfPwOO for <dispatch@ietfa.amsl.com>; Mon, 29 Feb 2016 23:05:01 -0800 (PST)
Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) by ietfa.amsl.com (Postfix) with ESMTP id E3A561B29CA for <dispatch@ietf.org>; Mon, 29 Feb 2016 23:04:59 -0800 (PST)
Received: from 68_1e_mfp.printers.eeghlan.net (h87-96-134-129.dynamic.se.alltele.net [87.96.134.129]) by smtp7.webway.se (Postfix) with ESMTPA id 236CA93DE55; Tue,  1 Mar 2016 07:03:36 +0000 (UTC)
Content-Type: multipart/signed; boundary="Apple-Mail=_FF2A794D-044E-4DC3-AC88-F7FD32B509F4"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <D2F9BF7A.17C6C3%jon.peterson@neustar.biz>
Date: Tue, 1 Mar 2016 08:04:43 +0100
Message-Id: <83BE167B-15C3-4727-9E9B-1BF2EC82D105@edvina.net>
References: <CAHBDyN4hgTg1o4On39C6sKwO9y=yy+46SEJB1DJrAfaUfhir=Q@mail.gmail.com> <8119825D-F91F-4494-AE59-39E3956B02F1@nostrum.com> <D2F9BF7A.17C6C3%jon.peterson@neustar.biz>
To: "Peterson, Jon" <jon.peterson@neustar.biz>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/f8lNJ9r-30I7UeFt5_YcCI-23wA>
Cc: DISPATCH <dispatch@ietf.org>, Ben Campbell <ben@nostrum.com>
Subject: Re: [dispatch] Reminder: Deadlines for IETF-95
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2016 07:05:03 -0000

--Apple-Mail=_FF2A794D-044E-4DC3-AC88-F7FD32B509F4
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


> On 01 Mar 2016, at 00:53, Peterson, Jon <jon.peterson@neustar.biz> wrote:
> 
> 
> I just wanted to confirm that Ben here is correct. This idea came out of a
> discussion in Yokohama about identifying the best practices for media
> security when setting up sessions with SIP, and in particular the glue
> that binds security in SIP to SDP and to RTP. This would invoke things
> like STIR, and would also potentially nod to more opportunistic approaches
> like those outlined in Alan's draft, as media confidentiality is one of
> the more important security properties in this post-PERPASS world of ours.
> 
> So, we expect to have a draft before the deadline - happy to discuss the
> general topic here in the meantime if there's interest.
I really look forward to this work. Thank you for starting it!

/Olle
> 
> Jon Peterson
> Neustar, Inc.
> 
> On 2/11/16, 5:56 PM, "dispatch on behalf of Ben Campbell"
> <dispatch-bounces@ietf.org on behalf of ben@nostrum.com> wrote:
> 
>> Hi,
>> 
>> I understand that Jon, Ekr, Richard, and Russ plan to submit a draft on
>> security recommendations for point-to-point, SIP-signaled RTP in time
>> for Buenos Aires. While I would be pleasantly surprised if the
>> discussion is far enough along by then for a charter proposal, I think
>> discussion in DISPATCH would be worthwhile.
>> 
>> So, please consider this notice of their intent to propose a discussion
>> topic, on their behalf.
>> 
>> Thanks!
>> 
>> Ben.
>> 
>> On 10 Feb 2016, at 7:54, Mary Barnes wrote:
>> 
>>> Hi all,
>>> 
>>> Just a reminder of the DISPATCH WG deadlines for IETF-95:
>>> https://trac.tools.ietf.org/wg/dispatch/trac/wiki
>>> 
>>> 
>>> - February 22, 2016. Cutoff date to notify the chairs/DISPATCH WG of
>>> plans to submit a proposal.
>>> 
>>> 
>>> - February 29, 2016. Cutoff for charter proposals for topics.
>>> 
>>> 
>>> - March 7, 2016. Announcement of topics that have been dispatched for
>>> IETF-95.
>>> 
>>> 
>>> - March 21, 2016. Draft deadline.
>>> 
>>> 
>>> Regards,
>>> Mary
>>> _______________________________________________
>>> dispatch mailing list
>>> dispatch@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dispatch
>> 
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


--Apple-Mail=_FF2A794D-044E-4DC3-AC88-F7FD32B509F4
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIF1TCCBdEw
ggO5oAMCAQICAw/zvTANBgkqhkiG9w0BAQ0FADB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQL
ExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3Jp
dHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0xNDEyMTIxODA1NTZaFw0x
NjEyMTExODA1NTZaMHExFzAVBgNVBAMTDk9sbGUgSm9oYW5zc29uMR0wGwYJKoZIhvcNAQkBFg5v
ZWpAZWR2aW5hLm5ldDE3MDUGCSqGSIb3DQEJARYoMDc2ZGY1NDBkZGJiMmJkNTliNTUxYTRjZWY5
MjE4NmQzNjNkYmIyNTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOmqasMHgkaLk5k0
wLfHa8L3ICewso+Sf8NWodzRroWD3GGT94T70v5qTYlXMs7K3H0kFGvKmk4JGPa+TbDptfcjicqY
9PGGB9ILQQ02jP8lvm1QJuDKrXoZ70C5ApW8dy4fjVmy4iDWugDeEYXRzvuSS3H7ygFzPFAOX80q
r2pUzn/uRw4ui7EPp0g3nv1wfpVQ65zKYiy28Xzuvut8S3o9BsWPq9zCzfes2jJrKoMnyKDodmBD
3QZaCxPplmLKoW/7QylznhdI5H1xBWoMRvUAvdxY7bucwcDzChxGXzhrbtov2qz/CHV4UqBxdLmJ
4absg9wIk09IaWgThoe3d5MCAwEAAaOCAWgwggFkMAwGA1UdEwEB/wQCMAAwVgYJYIZIAYb4QgEN
BEkWR1RvIGdldCB5b3VyIG93biBjZXJ0aWZpY2F0ZSBmb3IgRlJFRSBoZWFkIG92ZXIgdG8gaHR0
cDovL3d3dy5DQWNlcnQub3JnMA4GA1UdDwEB/wQEAwIDqDBABgNVHSUEOTA3BggrBgEFBQcDBAYI
KwYBBQUHAwIGCisGAQQBgjcKAwQGCisGAQQBgjcKAwMGCWCGSAGG+EIEATAyBggrBgEFBQcBAQQm
MCQwIgYIKwYBBQUHMAGGFmh0dHA6Ly9vY3NwLmNhY2VydC5vcmcwMQYDVR0fBCowKDAmoCSgIoYg
aHR0cDovL2NybC5jYWNlcnQub3JnL3Jldm9rZS5jcmwwQwYDVR0RBDwwOoEOb2VqQGVkdmluYS5u
ZXSBKDA3NmRmNTQwZGRiYjJiZDU5YjU1MWE0Y2VmOTIxODZkMzYzZGJiMjUwDQYJKoZIhvcNAQEN
BQADggIBAHxgZcQ5PWVh9S+4jVooejp71WhkpFOLJl9T7cYQ5jjHYJK4A5QXcByNhN42oL8grx7a
nIsOxDQf93zEx4y+t2QQpvh4LssrbUpDg5UVCtDWPKRxnnAGIJ+uHx+zUUleQ3rdzGGkk4lOVw1o
oeIoFt83a4a32iTP8RODaS1O2K38npQPX0Ggy1bpcVUXn19w+mCMueMg6yfvkv0n7URJ7jNzANvE
5OAtzWJt/eVn3czf0KJSvzN74pS/+3K0hPw8Wl/TrdBUtpul2x5gVH34djA/kW3uWfW18bC82hxc
OerzO/XOE1VBRlqFns0OmSDL9MA7BgJ7Qx5dgjElbIcojo1v9Uk/bNF04qMDwTrbWCKvxaRx3crY
R4LTzFfpnZVrqmXBGUXZBsbQHxeSBxAev0A7D1krDU57sIKnKdkW4n16dZMEnqQL3YcwYlUHmrWK
KZO8M295MQ8V6e7Q5h+iRvX00TtWt0c0UBpAKeZbpOw0nTwtsjp+7SEVxefzcOXSxxlrGLuipEU9
rKPNFBDUpqmipi+x6Dfb4Jv0bEn1rLXidlj9x2sY0IJbU38qDCjL2IVSMiV5E7p8tlIExJ7JKuKk
6sgNGFDxvc6VqHxQh9g8FgpDE0XF+4PEcn6Lq5VL603KhEc/aJw+mtXrhFEWXulwYphnsxU9/rih
gG8S7EXjMYIDMzCCAy8CAQEwgYAweTEQMA4GA1UEChMHUm9vdCBDQTEeMBwGA1UECxMVaHR0cDov
L3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25pbmcgQXV0aG9yaXR5MSEwHwYJ
KoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcCAw/zvTAJBgUrDgMCGgUAoIIBhzAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjAzMDEwNzA0NDNaMCMGCSqGSIb3
DQEJBDEWBBSwnr9wbaJ8AIidXydg2BZ4asQE/TCBkQYJKwYBBAGCNxAEMYGDMIGAMHkxEDAOBgNV
BAoTB1Jvb3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0Eg
Q2VydCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3Jn
AgMP870wgZMGCyqGSIb3DQEJEAILMYGDoIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsT
FWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0
eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMP870wDQYJKoZIhvcNAQEBBQAE
ggEA521NUC6u8PPQkydvAYLszvzE5RJ/M8pcFNZyAMsWWNL4wPCYJIkNKHHwZJodSQzhSeYhBAoI
KOMqEqRwhQ26EeKmPw8tFRrDPpulRiyIkiHwgTij1DInrJPwl4bkvgCXOdVwRiwPt/CFLNBd+vnZ
vOhrTO5xvZZpOh9SQCjJNzJMNFgPxl9sU+LRnALl2YL0Z9Lq1hX+f5htyUI0aqrzog/xj8mL5GBD
B62CebujeBHHztcDJOhglb77l7EnptIwLW1SLy8pRk5G5OyzsqpC3EPTchXaJupmsVJhVIdAaFSA
CRF4fIOabk5ddgs+WZmFvtyU0+lhxI/Fk/7V7SspswAAAAAAAA==
--Apple-Mail=_FF2A794D-044E-4DC3-AC88-F7FD32B509F4--


From nobody Mon Feb 29 23:30:54 2016
Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CBA21A8BAF for <dispatch@ietfa.amsl.com>; Mon, 29 Feb 2016 23:30:53 -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, SPF_PASS=-0.001] autolearn=ham
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 oG64ZZ3l9Q5K for <dispatch@ietfa.amsl.com>; Mon, 29 Feb 2016 23:30:51 -0800 (PST)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::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 15C1F1A8AFE for <dispatch@ietf.org>; Mon, 29 Feb 2016 23:30:51 -0800 (PST)
Received: by mail-ig0-x233.google.com with SMTP id y8so14147634igp.0 for <dispatch@ietf.org>; Mon, 29 Feb 2016 23:30:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=etNuJ3TmD3a4LvOkHnyvkZaBQhVvmwTcdvMG8hLR88c=; b=SiXCA/FV0i8wgj3Ypm7BYGBV5dbZHdUVG7tmKc/aZCxZHUJ6zoY3oC1RWsuVEP+Fnk +2GfGXgj3ZIPyasxYaYQXVvG0jjaCTW3e7ToUYwuBokATM0nCTvGI/dMz+QBCITSr8Vn A/Yz5qrrxjQnPcGMrA+PUuixBKZLhryRJMTj6GjKCOlUPuu2mmgnUc5zQGZrHgRpKPhF +Jjew5Ns/OBt2CpAnRrwksaG52s4tKqUk4vdD/0nFFb/CiUEZLuGS4EjNLbbVG1QXKq1 F3y9aKlYYX8Pt3Turu2rf/HJOdcclNu5FfV6v4G6xdQ6BopkEopR7e3FtY5okuE0xFYR rOWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=etNuJ3TmD3a4LvOkHnyvkZaBQhVvmwTcdvMG8hLR88c=; b=b8Y+5FBemcUhYdMb0Cq7D/qpTnndM9vkbQbNlFerF4O25Qi5su7VAXo05GPftOylY1 H9UHUoxtNVnY5AIn7MYugcSBJC4cQ/45IYgc4ERiFF7gmbKPv3IkLyFjm1Kt8YnOHHt2 epDiAf8GBofYSNxi97tJj/JSXowTBbmTh8JCFk3CjRBnG9IwwRZtq8yHnWW7wj4/U5dR +5rs2fIf6wvghukAb8TD+eCUoddWEKOs85vtWpQ2fjgG1NMU4/7cAazh+N0dNA/rE+dG uDd//gvqckCYkdvi/8OCf11Q7iTXucr57HIPyDj6HmmkswScoimlK7UFAaKawj7D9bgC k/Xw==
X-Gm-Message-State: AD7BkJJiqEpE8rWsLEW1Z0bJ/uIk2WaWHBT0nNah31P5Z8jdruJ1twYylcmTuy2/OIUDTEFsZdbbj1KkjW16+Q==
MIME-Version: 1.0
X-Received: by 10.50.98.74 with SMTP id eg10mr2168915igb.26.1456817450504; Mon, 29 Feb 2016 23:30:50 -0800 (PST)
Received: by 10.79.117.220 with HTTP; Mon, 29 Feb 2016 23:30:50 -0800 (PST)
In-Reply-To: <D2F9BF7A.17C6C3%jon.peterson@neustar.biz>
References: <CAHBDyN4hgTg1o4On39C6sKwO9y=yy+46SEJB1DJrAfaUfhir=Q@mail.gmail.com> <8119825D-F91F-4494-AE59-39E3956B02F1@nostrum.com> <D2F9BF7A.17C6C3%jon.peterson@neustar.biz>
Date: Mon, 29 Feb 2016 23:30:50 -0800
Message-ID: <CAKhHsXGi0sJRA44uwajYdJZ26jhjvfPwAnsAJhfmFd+mzw_TOg@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: "Peterson, Jon" <jon.peterson@neustar.biz>
Content-Type: multipart/alternative; boundary=047d7b3a8ab0a3da3a052cf7be88
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/NCc3viAdmOjnpVnfbX2f-_s6euY>
Cc: DISPATCH <dispatch@ietf.org>, Ben Campbell <ben@nostrum.com>
Subject: Re: [dispatch] Reminder: Deadlines for IETF-95
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2016 07:30:53 -0000

--047d7b3a8ab0a3da3a052cf7be88
Content-Type: text/plain; charset=UTF-8

Hi Jon,

The draft sounds interesting.

We have revised the OSRTP draft as well based on feedback from Yokohama.

     https://tools.ietf.org/html/draft-johnston-dispatch-osrtp

- Alan -

On Mon, Feb 29, 2016 at 3:53 PM, Peterson, Jon <jon.peterson@neustar.biz>
wrote:

>
> I just wanted to confirm that Ben here is correct. This idea came out of a
> discussion in Yokohama about identifying the best practices for media
> security when setting up sessions with SIP, and in particular the glue
> that binds security in SIP to SDP and to RTP. This would invoke things
> like STIR, and would also potentially nod to more opportunistic approaches
> like those outlined in Alan's draft, as media confidentiality is one of
> the more important security properties in this post-PERPASS world of ours.
>
> So, we expect to have a draft before the deadline - happy to discuss the
> general topic here in the meantime if there's interest.
>
> Jon Peterson
> Neustar, Inc.
>
> On 2/11/16, 5:56 PM, "dispatch on behalf of Ben Campbell"
> <dispatch-bounces@ietf.org on behalf of ben@nostrum.com> wrote:
>
> >Hi,
> >
> >I understand that Jon, Ekr, Richard, and Russ plan to submit a draft on
> >security recommendations for point-to-point, SIP-signaled RTP in time
> >for Buenos Aires. While I would be pleasantly surprised if the
> >discussion is far enough along by then for a charter proposal, I think
> >discussion in DISPATCH would be worthwhile.
> >
> >So, please consider this notice of their intent to propose a discussion
> >topic, on their behalf.
> >
> >Thanks!
> >
> >Ben.
> >
> >On 10 Feb 2016, at 7:54, Mary Barnes wrote:
> >
> >> Hi all,
> >>
> >> Just a reminder of the DISPATCH WG deadlines for IETF-95:
> >> https://trac.tools.ietf.org/wg/dispatch/trac/wiki
> >>
> >>
> >>  - February 22, 2016. Cutoff date to notify the chairs/DISPATCH WG of
> >>  plans to submit a proposal.
> >>
> >>
> >>  - February 29, 2016. Cutoff for charter proposals for topics.
> >>
> >>
> >>  - March 7, 2016. Announcement of topics that have been dispatched for
> >>  IETF-95.
> >>
> >>
> >>  - March 21, 2016. Draft deadline.
> >>
> >>
> >> Regards,
> >> Mary
> >> _______________________________________________
> >> dispatch mailing list
> >> dispatch@ietf.org
> >> https://www.ietf.org/mailman/listinfo/dispatch
> >
> >_______________________________________________
> >dispatch mailing list
> >dispatch@ietf.org
> >https://www.ietf.org/mailman/listinfo/dispatch
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>

--047d7b3a8ab0a3da3a052cf7be88
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Jon,<div><br></div><div>The draft sounds interesting.</=
div><div><br></div><div>We have revised the OSRTP draft as well based on fe=
edback from Yokohama.</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0<a href=
=3D"https://tools.ietf.org/html/draft-johnston-dispatch-osrtp">https://tool=
s.ietf.org/html/draft-johnston-dispatch-osrtp</a></div><div><br></div><div>=
- Alan -</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On Mon, Feb 29, 2016 at 3:53 PM, Peterson, Jon <span dir=3D"ltr">&lt;<a =
href=3D"mailto:jon.peterson@neustar.biz" target=3D"_blank">jon.peterson@neu=
star.biz</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I just wanted to confirm that Ben here is correct. This idea came out of a<=
br>
discussion in Yokohama about identifying the best practices for media<br>
security when setting up sessions with SIP, and in particular the glue<br>
that binds security in SIP to SDP and to RTP. This would invoke things<br>
like STIR, and would also potentially nod to more opportunistic approaches<=
br>
like those outlined in Alan&#39;s draft, as media confidentiality is one of=
<br>
the more important security properties in this post-PERPASS world of ours.<=
br>
<br>
So, we expect to have a draft before the deadline - happy to discuss the<br=
>
general topic here in the meantime if there&#39;s interest.<br>
<br>
Jon Peterson<br>
Neustar, Inc.<br>
<br>
On 2/11/16, 5:56 PM, &quot;dispatch on behalf of Ben Campbell&quot;<br>
&lt;<a href=3D"mailto:dispatch-bounces@ietf.org">dispatch-bounces@ietf.org<=
/a> on behalf of <a href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a>&gt;=
 wrote:<br>
<br>
&gt;Hi,<br>
&gt;<br>
&gt;I understand that Jon, Ekr, Richard, and Russ plan to submit a draft on=
<br>
&gt;security recommendations for point-to-point, SIP-signaled RTP in time<b=
r>
&gt;for Buenos Aires. While I would be pleasantly surprised if the<br>
&gt;discussion is far enough along by then for a charter proposal, I think<=
br>
&gt;discussion in DISPATCH would be worthwhile.<br>
&gt;<br>
&gt;So, please consider this notice of their intent to propose a discussion=
<br>
&gt;topic, on their behalf.<br>
&gt;<br>
&gt;Thanks!<br>
&gt;<br>
&gt;Ben.<br>
&gt;<br>
&gt;On 10 Feb 2016, at 7:54, Mary Barnes wrote:<br>
&gt;<br>
&gt;&gt; Hi all,<br>
&gt;&gt;<br>
&gt;&gt; Just a reminder of the DISPATCH WG deadlines for IETF-95:<br>
&gt;&gt; <a href=3D"https://trac.tools.ietf.org/wg/dispatch/trac/wiki" rel=
=3D"noreferrer" target=3D"_blank">https://trac.tools.ietf.org/wg/dispatch/t=
rac/wiki</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 - February 22, 2016. Cutoff date to notify the chairs/DISPAT=
CH WG of<br>
&gt;&gt;=C2=A0 plans to submit a proposal.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 - February 29, 2016. Cutoff for charter proposals for topics=
.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 - March 7, 2016. Announcement of topics that have been dispa=
tched for<br>
&gt;&gt;=C2=A0 IETF-95.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 - March 21, 2016. Draft deadline.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Regards,<br>
&gt;&gt; Mary<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; dispatch mailing list<br>
&gt;&gt; <a href=3D"mailto:dispatch@ietf.org">dispatch@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"=
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dispatc=
h</a><br>
&gt;<br>
&gt;_______________________________________________<br>
&gt;dispatch mailing list<br>
&gt;<a href=3D"mailto:dispatch@ietf.org">dispatch@ietf.org</a><br>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dispatch</a>=
<br>
<br>
_______________________________________________<br>
dispatch mailing list<br>
<a href=3D"mailto:dispatch@ietf.org">dispatch@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dispatch</a><br>
</blockquote></div><br></div>

--047d7b3a8ab0a3da3a052cf7be88--

