IETF Logo Mail Archive

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

Shraddha Hegde <shraddha@juniper.net> Mon, 11 June 2018 15:02 UTC

Return-Path: <shraddha@juniper.net>
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 39DD6130E64 for <spring@ietfa.amsl.com>; Mon, 11 Jun 2018 08:02:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 hrJFyyOKZInO for <spring@ietfa.amsl.com>; Mon, 11 Jun 2018 08:02:35 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 4B206130F3A for <spring@ietf.org>; Mon, 11 Jun 2018 08:02:35 -0700 (PDT)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w5BErmRi018054; Mon, 11 Jun 2018 08:02:24 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=ICRL5MVpobjWfyypfjBIOTwubClpGcvAm+RL3aZQPtw=; b=y6Dzp9kAG0oU2Vaw+bcuYMH/uqYBbqqEyuaYVbQGQeOxviXS6wpm3L3bJ3mNHkt1Rc2z Xz5Zx/9FUvoEZXzm18uP2ZLU82jK2QzhBrxvOLnGLsEVUWytLm3VrKqyCeJ9+2boCXFk bICobA1hNVX9zPMxFNfAEpdBvaypTjlJiH9UjXKlGlfDHzbpyscIIukRLw1m+3xZx1LD XVpVZBMge5MQNoTH4gwAs++OdsjcexJ+6TF6HYIXVDOvoP2VhnHjfNXxmatUGq72mob8 cYArY+9Kwaej+opsa863BzQTC3J4q5xCkELYVwKXDdI6nb797a6AuYmUxtHnQ2Ll4nez Gg==
Received: from nam04-co1-obe.outbound.protection.outlook.com (mail-co1nam04lp0048.outbound.protection.outlook.com [216.32.181.48]) by mx0a-00273201.pphosted.com with ESMTP id 2jhgg6h42a-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 11 Jun 2018 08:02:24 -0700
Received: from BN3PR05MB2706.namprd05.prod.outlook.com (10.167.2.135) by BN3PR05MB2739.namprd05.prod.outlook.com (10.167.2.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.863.6; Mon, 11 Jun 2018 15:02:22 +0000
Received: from BN3PR05MB2706.namprd05.prod.outlook.com ([fe80::59df:5cb1:4d42:7950]) by BN3PR05MB2706.namprd05.prod.outlook.com ([fe80::59df:5cb1:4d42:7950%8]) with mapi id 15.20.0863.010; Mon, 11 Jun 2018 15:02:22 +0000
From: Shraddha Hegde <shraddha@juniper.net>
To: "Voyer, Daniel" <daniel.voyer@bell.ca>, 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: AQHT7Sl+ia2e66Lujka/OsSrCowqjaRIXcQAgBLyOBA=
Date: Mon, 11 Jun 2018 15:02:22 +0000
Message-ID: <BN3PR05MB270651AA8A5537766B80ABEDD5780@BN3PR05MB2706.namprd05.prod.outlook.com>
References: <CAHd-QWsZrcdJZnnJvDCpS_RqQ1e068FTUo0Rvh8s+C2zoiuy_A@mail.gmail.com> <303E6805-2445-4226-AA00-13E154B79D22@bell.ca>
In-Reply-To: <303E6805-2445-4226-AA00-13E154B79D22@bell.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.0.300.84
dlp-reaction: no-action
x-originating-ip: [116.197.184.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR05MB2739; 7:Azcl8Yk1gGZdTK3lLQEwwLaEtgoXtRm8WfoOvgsj9Y+b3Pdgb5ztSi9hnf5n6Ui2oQadShYkvUP9LUCspxFDZjN+XRvjgHboiJzfeo1cgtXJ4ZXeoXoZxRgHpWBcRVHPxHtNBwCWkAJ502dqRgq4URKYRgGJUfLq3xQo83ZCLlmgDF1e8usoAO2dRrBAL36FJclZnF6AGO/6xCqEY5f6m+EyW5zw6ciRDRMCig4/lNR6yeiZCLPE7neQteViK0Kt
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BN3PR05MB2739;
x-ms-traffictypediagnostic: BN3PR05MB2739:
x-microsoft-antispam-prvs: <BN3PR05MB2739339F03A37BE431F65AC4D5780@BN3PR05MB2739.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(211936372134217)(153496737603132)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123562045)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:BN3PR05MB2739; BCL:0; PCL:0; RULEID:; SRVR:BN3PR05MB2739;
x-forefront-prvs: 070092A9D3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39380400002)(39860400002)(376002)(346002)(396003)(199004)(189003)(86362001)(81166006)(6436002)(8936002)(5660300001)(59450400001)(8676002)(26005)(186003)(53546011)(2900100001)(74316002)(9686003)(102836004)(229853002)(68736007)(6506007)(33656002)(81156014)(790700001)(5250100002)(66066001)(6116002)(3846002)(25786009)(6246003)(2906002)(53936002)(316002)(11346002)(3660700001)(476003)(97736004)(55016002)(76176011)(54896002)(6306002)(110136005)(7696005)(478600001)(446003)(3280700002)(106356001)(486006)(236005)(7736002)(99286004)(105586002)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR05MB2739; H:BN3PR05MB2706.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: jQ7IflBIGBmNo3hbSZs9fO1MrzknHuwatNzhIuw3T71ZR+PGv5X0rnSncJVOnyEOVq9jqb1utV4OHm8XZRcXIyXpSbLzzauPaUsYcw3TUP7F3D57NHtv0hVkDZXvVMTo9w8bOyXr4bg7at15p8C1uGfWj7H0bHv7fGR/1Si10M0h2lqLcxvjYDtSz6k2u+oc
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN3PR05MB270651AA8A5537766B80ABEDD5780BN3PR05MB2706namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 4a887c8a-8a32-43f6-c336-08d5cfac55ba
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 4a887c8a-8a32-43f6-c336-08d5cfac55ba
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jun 2018 15:02:22.1639 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR05MB2739
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-06-11_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1806110173
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/Lp1YHuUlshCHFoXbV8Aurk0_1fA>
Subject: Re: [spring] Working Group Adoption Call for draft-filsfils-spring-segment-routing-policy
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.26
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, 11 Jun 2018 15:02:40 -0000

Not aware of any IPR related to the draft.

Rgds
Shraddha

From: spring <spring-bounces@ietf.org> On Behalf Of Voyer, Daniel
Sent: Wednesday, May 30, 2018 7:12 PM
To: Rob Shakir <robjs@google.com>; SPRING WG List <spring@ietf.org>
Subject: Re: [spring] Working Group Adoption Call for draft-filsfils-spring-segment-routing-policy

Support

Not aware of any IPR

dan

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:20 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