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

[Pablo Camarillo (pcamaril)]

Hi,

I support the adoption of this document.

Cheers,
Pablo.

From: spring  on behalf of Rob Shakir 

Date: Wednesday, 16 May 2018 at 17:21
To: SPRING WG List 
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.
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] IPR Poll for draft-filsfils-spring-segment-routing-policy

[Francois Clad (fclad)]

I’m not aware of any IPR other than already disclosed at 
https://datatracker.ietf.org/ipr/search/?submit=draft=draft-filsfils-spring-segment-routing-policy

Francois

On 16 May 2018, at 18:15, 
bruno.decra...@orange.com wrote:

[+ authors]

I'm not aware of any IPR that applies to this draft

--Bruno

From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Rob Shakir
Sent: Wednesday, May 16, 2018 5:20 PM
To: SPRING WG List
Subject: [spring] IPR Poll for draft-filsfils-spring-segment-routing-policy

Hi SPRING WG,

In parallel to the call for adoption for 
draft-filsfils-spring-segment-routing-policy, we would like to poll for IPR.

If you are aware of IPR that applies to 
draft-filsfils-spring-segment-routing-policy please respond to this email. If 
you are aware of IPR, please indicate whether it has been disclosed in 
accordance with IETF IPR rules (RFCs 3979, 4879, 3669 and 5378 provide more 
details).

If you are an author or contributor please respond to this email regardless of 
whether or not you're aware of any IPR. If you are not an author or 
contributor, please explicitly respond only if you are aware of IPR that has 
not yet been disclosed.

This document will not advance into the working group until IPR confirmations 
have been received from all authors and contributors.

Thanks,
Bruno & Rob.

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring