[salud] Finishing up

worley@ariadne.com (Dale R. Worley) Wed, 16 July 2014 18:35 UTC

Return-Path: <worley@ariadne.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 7B78D1A0180 for <salud@ietfa.amsl.com>; Wed, 16 Jul 2014 11:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 8BdPJkvSi6JS for <salud@ietfa.amsl.com>; Wed, 16 Jul 2014 11:35:24 -0700 (PDT)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:56]) by ietfa.amsl.com (Postfix) with ESMTP id 90D0F1A017A for <salud@ietf.org>; Wed, 16 Jul 2014 11:35:24 -0700 (PDT)
Received: from omta02.westchester.pa.mail.comcast.net ([]) by qmta06.westchester.pa.mail.comcast.net with comcast id T3Gp1o0060QuhwU566bQg8; Wed, 16 Jul 2014 18:35:24 +0000
Received: from hobgoblin.ariadne.com ([]) by omta02.westchester.pa.mail.comcast.net with comcast id T6bP1o00n1KKtkw3N6bP4i; Wed, 16 Jul 2014 18:35:24 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com []) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s6GIZMZZ021613; Wed, 16 Jul 2014 14:35:22 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s6GIZMlT021612; Wed, 16 Jul 2014 14:35:22 -0400
Date: Wed, 16 Jul 2014 14:35:22 -0400
Message-Id: <201407161835.s6GIZMlT021612@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: rlb@ipv.sx, salud@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1405535724; bh=/cJ2Igpdy3cMrXFMpOMIpXUMyrCHLVSvd3JQAiqfWzk=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=WxNUCPg6Q39g4ixt3HUK6N8aKKP61lEAI5nly1wQE6DcNQ+CCYTD1tLd/Z7Oh0w+1 i3Vn/G2udgiOQ+eWBH2qEYtWyNX65NplQCGWF7tYZ4YWFwzedv+yvXGyKOcV69zp+3 JQde1uOGv5imuDL0sRXB2q69TZxR6M1qm/WMgtjdiZmymORb2jj3yFgRiKWx5Z1uys unJVIqTH/aoh6YGC2KVvmFKM7ikKFOBfkNf3Hf9Z8tWdoFSvdiMtrvwBQoIs1kPKoY wGC3j0t7Kn3jKdzT/1NnOULsEOvF+IloU0Ncj/W08NE81oiluaqgvoMx5nCuKRHmMM WYmL4MFn5LeIQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/WzLaECuKMd_eLpUhP4lbaOjbubs
Cc: Atle Monrad <atle.monrad@ericsson.com>
Subject: [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 18:35:26 -0000

[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.


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

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

   - 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.