Re: [spring] Working Group Adoption Call for draft-filsfils-spring-segment-routing-policy

Rob Shakir <robjs@google.com> Wed, 30 May 2018 14:56 UTC

Return-Path: <robjs@google.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B99AD12DA24 for <spring@ietfa.amsl.com>; Wed, 30 May 2018 07:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.21
X-Spam-Level:
X-Spam-Status: No, score=-18.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ciLcC80I2EPk for <spring@ietfa.amsl.com>; Wed, 30 May 2018 07:56:16 -0700 (PDT)
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 A1A7212EA24 for <spring@ietf.org>; Wed, 30 May 2018 07:56:16 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id v197-v6so4789118ywc.13 for <spring@ietf.org>; Wed, 30 May 2018 07:56:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Y9J1shtnomUAz9PXLQFEK2UGOQiG4Z53p9cy6bmHd9s=; b=lZ9gr0lNZrD70F2fBp4b1hes+AQM8VnmhGIjLjHUdaCg1dZ32OXOWRUTlEY729QgZd dycX3rnim2BD6+8NsfUO6vtPDXdhrXeajxGJUytyssvKBsMc5osS4t0Pk/n6DtjYDWNu nLNBmmLpbP0MrpiPuXKaCfbmwK5RtC8ovUcmoL8Mvaho6TRoQxDlLvK5bTKDuG0aEdgF fdxDrXq7jyg7ZfXjp3g6wG5txpk475Nk0Z/+5rxz9LJtSHDWYBCsYCIxnI/lND0kvKBM T5Q3LIj2Gc3JtM5/2v5yCQnG5ylZxNd7OQ5AULgqYoumi3OYz/rtTUghSkdL/X1sz4XO a3TA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Y9J1shtnomUAz9PXLQFEK2UGOQiG4Z53p9cy6bmHd9s=; b=EoVTqXS1Y7OJJHaEx1v6WRPtefZWLxigVdPiODnkUIu7F/5FtfbEDv7CbEAiM+lWSu l4Qe9ymjPs0JW6p6eD/r+bnEyh9qscHIfgHLKull1vidZc33WvAJJEuY/5gicUlbfywL txsFEMqYkSlCV1Gv6qX4DB3TaAEikt0pnwE8fQOe4rlf0rQsYOMIjZog1RpbCDnUAQLW q98WzAJk61QhfszIDvhKrNrJWMv8b6PTemyc3vKk5rB06cob0aR0oSvfLkpmGkT4eio3 S8wJ6DkC4AhalWQzy7J5znLBNwP04nMSTYiCILC27LkQ0myQawq3FWEIIqmjqaP732V4 OTCQ==
X-Gm-Message-State: ALKqPwc1bwXu1mpiSITpSftpzDtfp+e2/rjSbTI4/Ozowvis4nK42uAy iYlEGeJfM/j0hzKod3PHvvdvNgYi0HB+6TsX/wmBGQ==
X-Google-Smtp-Source: ADUXVKIhTbpP2X8aPI/9XrIlJlCcOeWIuy4kgiConpgc25QBKjPxt5cYswhpIY4/vWohgqKohsQBHhzTt0L34BOIKnk=
X-Received: by 2002:a0d:ed06:: with SMTP id w6-v6mr1526087ywe.467.1527692175322; Wed, 30 May 2018 07:56:15 -0700 (PDT)
MIME-Version: 1.0
References: <CAHd-QWsZrcdJZnnJvDCpS_RqQ1e068FTUo0Rvh8s+C2zoiuy_A@mail.gmail.com> <18c1bf48f8eb4a1396c7a26e22a41f0c@XCH-ALN-008.cisco.com> <CAHd-QWunQFKV-4SGUATGXwLbKQ1jAS6u0AOZhwADfpRyW9TM0w@mail.gmail.com> <a916629f516c4aac8cea247a032882eb@XCH-ALN-008.cisco.com>
In-Reply-To: <a916629f516c4aac8cea247a032882eb@XCH-ALN-008.cisco.com>
From: Rob Shakir <robjs@google.com>
Date: Wed, 30 May 2018 07:56:02 -0700
Message-ID: <CAHd-QWt+VdWKVto9D5SFimcHw2_cL7r0fXMWmqrs4yK6a8ZBtw@mail.gmail.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, SPRING WG List <spring@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000704078056d6d8d05"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/589zJQV30f2cbNrp5v1001mPVJ4>
Subject: Re: [spring] Working Group Adoption Call for draft-filsfils-spring-segment-routing-policy
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2018 14:56:20 -0000

Thanks Ketan.

We're also pending one IPR statement from Steven Lin -- I've dropped him a
note to follow up on this.

If we have Steven's email by when you're ready to submit this draft, then
based on the support on the list please submit it with the revised
(adopted) name.

I look forward to seeing the edits and the WG iterating on this document.

Thanks,
r.

On Wed, May 30, 2018 at 7:32 AM Ketan Talaulikar (ketant) <ketant@cisco.com>
wrote:

> Hi Rob,
>
>
>
> We are working on posting the updated drafts with the trimmed author list
> by this weekend.
>
>
>
> Thanks,
>
> Ketan
>
>
>
> *From:* Rob Shakir <robjs@google.com>
> *Sent:* 21 May 2018 20:42
> *To:* Ketan Talaulikar (ketant) <ketant@cisco.com>
> *Cc:* SPRING WG List <spring@ietf.org>
> *Subject:* Re: [spring] Working Group Adoption Call for
> draft-filsfils-spring-segment-routing-policy
>
>
>
> Ketan,
>
>
>
> Thanks for the work on this -- this is definitely a good step to moving
> towards these documents being clearer and more addressable.
>
>
>
> Just FYI, there is still an outstanding point around the authors for the
> document under review here (draft-filsfils-spring-segment-routing-policy).
>
>
>
> Kind regards,
>
> r.
>
>
>
> On Mon, May 21, 2018 at 1:44 AM Ketan Talaulikar (ketant) <
> ketant@cisco.com> wrote:
>
> Hello Chairs/All,
>
>
>
> At the IETF London and afterwards over the mailing list, the chairs have
> asked us to split the SR Policy draft into sub-documents to allow for
> faster proceeding of the core concepts. As asked and discussed, the authors
> have proceeded to split draft-filsfils-spring-segment-routing-policy-05 as
> follows:
>
>
>
> 1)     The core architecture of SR Policy has been published
> <https://tools.ietf.org/html/draft-filsfils-spring-segment-routing-policy-06>
> as draft-filsfils-spring-segment-routing-policy-06.
>
> 2)     The section 13 on traffic counters has been moved to an existing
> draft and a new version of draft-ali-spring-sr-traffic-accounting-01 has
> been posted
> <https://tools.ietf.org/html/draft-ali-spring-sr-traffic-accounting-01>,
> accordingly.
>
> 3)     The contents of section 14, the Appendix, and a few other sections
> have been published
> <https://tools.ietf.org/html/draft-filsfils-spring-sr-policy-considerations-00>
> as a new informational draft,
> draft-filsfils-spring-sr-policy-considerations-00.
>
>
>
> Please let know if you have any questions or feedback.
>
>
>
> Thanks,
>
> Ketan (on behalf of authors of
> draft-filsfils-spring-segment-routing-policy)
>
>
>
> *From:* spring <spring-bounces@ietf.org> *On Behalf Of *Rob Shakir
> *Sent:* 16 May 2018 20:50
> *To:* SPRING WG List <spring@ietf.org>
> *Subject:* [spring] Working Group Adoption Call for
> draft-filsfils-spring-segment-routing-policy
>
>
>
> Hi SPRING WG,
>
>
>
> This email initiates a two week call for working group adoption
> for draft-filsfils-spring-segment-routing-policy. Please indicate your
> support, or otherwise, for adopting this draft as a working group item by *30th
> May 2018*. We are particularly interested in hearing from working group
> members that are not co-authors of this draft.
>
>
>
> As part of the discussions of adopting this draft into SPRING with the ADs
> and chairs of other WGs, there are a number of requests to the authors.
>
>
>
> 1. Please clarify in the text traffic steering with "SR policy" and its
> relationship to other traffic engineering functions. It seems to me that
> this work is generally describing how one selects and steers traffic into
> policies, rather than path calculation. Additional clarification of whether
> this is the case (or not), would be welcome to ensure that the relationship
> with other work is clear. We would ask the authors to consider whether
> sections 14.1-14.4 are required scope of this document.
>
>
>
> 2.. Consider what the core content of this document is, and how it can be
> make as concise and clear as possible. There are some specific suggestions
> that can be made here, but we would like to see this discussed with the
> working group.
>
>
>
> Additionally, there are currently 17 authors listed on this document.
> Please trim this to <= 5 front-page authors, utilising a "Contributors"
> section if required for the others.. An approach to achieving this would be
> to list ~2 editors as the front-page authors.
>
>
>
> In parallel to this adoption call, I will send an IPR call for this
> document. We will need all 17 authors to confirm their IPR position on this
> document.
>
>
>
> Thanks,
>
> Bruno & Rob.
>
>