Re: [salud] Finishing up

Richard Barnes <rlb@ipv.sx> Wed, 16 July 2014 19:41 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 183771A01EF for <salud@ietfa.amsl.com>; Wed, 16 Jul 2014 12:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 FD-KR6Ls17e7 for <salud@ietfa.amsl.com>; Wed, 16 Jul 2014 12:41:57 -0700 (PDT)
Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A3B61A01F1 for <salud@ietf.org>; Wed, 16 Jul 2014 12:41:57 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id tp5so1344784ieb.37 for <salud@ietf.org>; Wed, 16 Jul 2014 12:41:56 -0700 (PDT)
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=11tHPYzyLA7w823yt6pRY+Ga9x8rxZDyVT8vlZmFnb0=; b=Sh+FH7YKr24nkaVUkgvVlwy9cLYy6RTdRnj2yHZi5yiKqTrkK22PTCu4tjMXnKfua1 nbISHcnWKmszAVF/4vQlJMYMGrvja4DRZHF8+nwRhvulTOfWXFFarDEnqzZFniweCa46 ktlvioRcwlUaGlHe8SAXpo2fOBK2xM0SG9B2AHWNdG39UvTWA7GbCs1eAQKl9JJeBszP Q1Xapzjry9uNrvigNQqmfgp4mkSozQ8Cmjwnq8j/jJc7/f4hC55Pj6HHq5kN8VvWtOtC 5/5Tsg6ZAYuimHeRLDbp/ly0EHvu7i2D6fkXJOUTUtjP/FDQrB7sCf9K+FCF0bREgKE9 IS7g==
X-Gm-Message-State: ALoCoQkeOinY2hfRsICBj6wE6ofazX3eexKXiPTAPRWmiCvk3qs5lgaVv5RCXokNpWiXKg+TNH1z
MIME-Version: 1.0
X-Received: by 10.182.126.40 with SMTP id mv8mr39303605obb.36.1405539716291; Wed, 16 Jul 2014 12:41:56 -0700 (PDT)
Received: by 10.76.106.202 with HTTP; Wed, 16 Jul 2014 12:41:56 -0700 (PDT)
In-Reply-To: <201407161835.s6GIZMlT021612@hobgoblin.ariadne.com>
References: <201407161835.s6GIZMlT021612@hobgoblin.ariadne.com>
Date: Wed, 16 Jul 2014 15:41:56 -0400
Message-ID: <CAL02cgTBoaEJ8QBEp52eA-N-TcRBm3awunzY_XXnH-V0D+t-WA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary=e89a8fb1f76481f44804fe54b760
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/7WDKsp0Eu2DAYnD2ty72Nxr23I4
Cc: Atle Monrad <atle.monrad@ericsson.com>, salud@ietf.org
Subject: Re: [salud] Finishing up
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud/>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jul 2014 19:41:59 -0000

Hey Dale,

Thanks for keeping this moving.  Glad it sounds like you've got some
resolutions to IESG issues.

I think it's OK to run the WGLC in parallel with the meeting next week,
especially if you extend it to run a little bit before and/or after the
meeting.

You don't need to be quite so formal about steps 4, 5, and 6.  You really
just need to talk to the individual ADs holding DISCUSSes, and once they
clear, I can approve the document.

Thanks again,
--Richard



On Wed, Jul 16, 2014 at 2:35 PM, Dale R. Worley <worley@ariadne.com>; wrote:

> [as chair of Salud]
>
> I am currently planning how to bring the draft to a rapid conclusion.
> There are a number of steps to be followed, and by IETF procedures,
> they need to be followed in order, and that will take some time.
>
> However, I believe that with proper planning we can advance quickly to
> the point where we know that the current Salud draft will be accepted,
> even though finishing the procedures will take a few weeks further.
>
> The purpose of this message is to ask our AD, Richard Barnes, if he
> considers this a reasonable way to proceed, and to notify all
> concerned that this is the proposed plan and request feedback on any
> needed modifications.
>
> First,
>
> 1. Establish a -13 draft, so we have a definitive revision of the
>    draft.  I believe that the authors are in consensus about a -13
>    draft.
>
> After that, we can proceed in parallel with,
>
> 2. Obtain approval of Christer Holmberg, who is the Document Shepherd
>    and outside technical reviewer.
>
> 3. Obtain approval of the working group via a WGLC.  We need to allow
>    for at least two weeks for WGLC.  In my opinion, this time should
>    be disjoint of the Toronto IETF meeting, which means that it spans
>    Monday 28 July to Monday 11 August.  Given the recent history of
>    the working group and the fact that all recently active members
>    have been active authors of the draft, I do not expect any
>    objections to be raised.
>
> 4. Informally verify that the changes in the -13 draft satisfy the
>    IESG objections that have design import or are in some way
>    controversial:
>
>    - replacing the domain name-based <provider> value with a
>      first-com, first-served registry (Alissa Cooper, Barry Leiba,
>      Brian Haberman, Pete Resnick, Stephen Farrell)
>
>    - using a uniform policy of Specification Required (which includes
>      Expert Review) for defining additional standard URNs, including
>      providing detailed guidelines for the expert review (Barry Leiba,
>      Brian Haberman, Pete Resnick)
>
>    - revision of section 13 and its requirement that a UA "MUST
>      produce a reasonable rending" (Gen-Art review, Jari Arkko)
>
>    - additional security considerations and reorganizing their
>      presentation, including that a "source" indication will almost
>      certainly only be accepted when it is provided by a proxy acting
>      on behalf of the recipient UA (section 16, 8.2.2) (Secdir review,
>      Alissa Cooper, Kathleen Moriarty, Stephen Farrell, Ted Lemon)
>
> After 1, 2, and 4 are finished, I believe that we can safely predict
> the draft will proceed to an RFC.
>
> After the second stage, we can proceed with,
>
> 5. Formally file responses to the IESG's discuss points.
>
> 6. Get the IESG's approval.
>
> After that there is,
>
> 7. Editorial consultation with the RFC Editor.
>
> Dale
>