IETF Logo Mail Archive

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

Lizhenbin <lizhenbin@huawei.com> Mon, 21 May 2018 01:22 UTC

Return-Path: <lizhenbin@huawei.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 6A93312E043 for <spring@ietfa.amsl.com>; Sun, 20 May 2018 18:22:16 -0700 (PDT)
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 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 eCIPc66-besa for <spring@ietfa.amsl.com>; Sun, 20 May 2018 18:22:14 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 1981B1200C1 for <spring@ietf.org>; Sun, 20 May 2018 18:22:14 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id E05A352F98ACC for <spring@ietf.org>; Mon, 21 May 2018 02:22:09 +0100 (IST)
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.382.0; Mon, 21 May 2018 02:22:10 +0100
Received: from DGGEMM512-MBX.china.huawei.com ([169.254.3.72]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0382.000; Mon, 21 May 2018 09:22:02 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Rob Shakir <robjs@google.com>, SPRING WG List <spring@ietf.org>
Thread-Topic: [spring] Working Group Adoption Call for draft-filsfils-spring-segment-routing-policy
Thread-Index: AQHT7SmPxhMrMkXMQUustfU6hGdSY6Q2x42AgAKiG4A=
Date: Mon, 21 May 2018 01:22:02 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F41BE95@dggemm512-mbx.china.huawei.com>
References: <CAHd-QWsZrcdJZnnJvDCpS_RqQ1e068FTUo0Rvh8s+C2zoiuy_A@mail.gmail.com> <9F3F4EEC-9F4C-4266-8C04-DC340DBC3CCA@cisco.com>
In-Reply-To: <9F3F4EEC-9F4C-4266-8C04-DC340DBC3CCA@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.206.84]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D8F41BE95dggemm512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/puRoOrdSc2EHVq10ilofactxjvY>
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: Mon, 21 May 2018 01:22:16 -0000

Support.

Best Regards,
Zhenbin (Robin)


From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Zafar Ali (zali)
Sent: Sunday, May 20, 2018 1:08 AM
To: Rob Shakir <robjs@google.com>; SPRING WG List <spring@ietf.org>
Cc: Zafar Ali (zali) <zali@cisco.com>
Subject: Re: [spring] Working Group Adoption Call for draft-filsfils-spring-segment-routing-policy

Dear WG and chairs,

Support (as a co-author).

Thanks

Regards … Zafar

From: spring <spring-bounces@ietf.org<mailto:spring-bounces@ietf.org>> on behalf of Rob Shakir <robjs@google.com<mailto:robjs@google.com>>
Date: Wednesday, May 16, 2018 at 11:21 AM
To: SPRING WG List <spring@ietf.org<mailto: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.

v2.23.0 | Report a Bug | By Email