IETF Logo Mail Archive

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

Takuya Miyasaka <ta-miyasaka@kddi-research.jp> Thu, 17 May 2018 04:20 UTC

Return-Path: <ta-miyasaka@kddi-research.jp>
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 7D5AE12E8A8 for <spring@ietfa.amsl.com>; Wed, 16 May 2018 21:20:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 T9cLmMi1rO84 for <spring@ietfa.amsl.com>; Wed, 16 May 2018 21:20:19 -0700 (PDT)
Received: from mandala.kddilabs.jp (mandala.kddilabs.jp [192.26.91.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9A581120726 for <spring@ietf.org>; Wed, 16 May 2018 21:20:17 -0700 (PDT)
Received: from localhost (mandala.kddilabs.jp [127.0.0.1]) by mandala.kddilabs.jp (Postfix) with ESMTP id 023C5C0EF655; Thu, 17 May 2018 13:20:14 +0900 (JST)
X-Virus-Scanned: amavisd-new at kddi-research.jp
Received: from mandala.kddilabs.jp ([127.0.0.1]) by localhost (mandala.kddilabs.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8FcwRdLtU17S; Thu, 17 May 2018 13:20:09 +0900 (JST)
Received: from safeattach.localdomain (unknown [IPv6:2001:200:601:1a00:20c:29ff:fe79:2280]) by mandala.kddilabs.jp (Postfix) with ESMTP id D66CEC0EF643; Thu, 17 May 2018 13:20:09 +0900 (JST)
Received: from [172.19.124.101] (dhcp101.west-4f.cn.kddilabs.jp [172.19.124.101]) by safeattach.localdomain with ESMTP id w4H4K9Rn019528; Thu, 17 May 2018 13:20:09 +0900
To: Rob Shakir <robjs@google.com>, SPRING WG List <spring@ietf.org>
References: <CAHd-QWsZrcdJZnnJvDCpS_RqQ1e068FTUo0Rvh8s+C2zoiuy_A@mail.gmail.com>
From: Takuya Miyasaka <ta-miyasaka@kddi-research.jp>
Message-ID: <1a5ab986-812f-f2f4-9865-30b52b09f2c2@kddi-research.jp>
Date: Thu, 17 May 2018 13:20:09 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CAHd-QWsZrcdJZnnJvDCpS_RqQ1e068FTUo0Rvh8s+C2zoiuy_A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------C46FED562C02798012B8F9DB"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/_Y6X7mkWcUzKwe0ANvIgGgARJf4>
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: Thu, 17 May 2018 04:20:22 -0000

I support the adoption of this draft. This kind of feature is very 
useful from operator's point of view.

Thanks,
Takuya

On 2018/05/17 0:20, Rob Shakir wrote:
> 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.
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring

v2.23.0 | Report a Bug | By Email