Re: [Teas] WG adoption - draft-nsdt-teas-transport-slice-definition

RFC 7297 is an Independent Submission Informational RFC.
Looking at it, building from it, and where agreed copying the text would 
seem sensible.
Referencing it normatively would be a major problem, as it is not an 
IETF consensus document.

Yours,
Joel

On 8/27/2020 8:26 AM, mohamed.boucadair@orange.com wrote:
> Hi all,
> 
> I support this effort.
> 
> That’s said, I do think the document should leverage existing documents, 
> e.g., use https://tools.ietf.org/html/rfc7297 to define the SLOs:
> 
> 3  <https://tools.ietf.org/html/rfc7297#section-3>.  Connectivity Provisioning Profile (CPP) . . . . . . . . . . . 9  <https://tools.ietf.org/html/rfc7297#page-9>
> 
> 3.1  <https://tools.ietf.org/html/rfc7297#section-3.1>.  Customer Nodes Map  . . . . . . . . . . . . . . . . . . . 9  <https://tools.ietf.org/html/rfc7297#page-9>
> 
> 3.2  <https://tools.ietf.org/html/rfc7297#section-3.2>.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 10  <https://tools.ietf.org/html/rfc7297#page-10>
> 
> 3.3  <https://tools.ietf.org/html/rfc7297#section-3.3>.  QoS Guarantees  . . . . . . . . . . . . . . . . . . . . . 11  <https://tools.ietf.org/html/rfc7297#page-11>
> 
> 3.4  <https://tools.ietf.org/html/rfc7297#section-3.4>.  Availability  . . . . . . . . . . . . . . . . . . . . . . 11  <https://tools.ietf.org/html/rfc7297#page-11>
> 
> 3.5  <https://tools.ietf.org/html/rfc7297#section-3.5>.  Capacity  . . . . . . . . . . . . . . . . . . . . . . . . 12  <https://tools.ietf.org/html/rfc7297#page-12>
> 
> 3.6  <https://tools.ietf.org/html/rfc7297#section-3.6>.  Conformance Traffic . . . . . . . . . . . . . . . . . . . 13  <https://tools.ietf.org/html/rfc7297#page-13>
> 
> 3.7  <https://tools.ietf.org/html/rfc7297#section-3.7>.  Overall Traffic Guarantees  . . . . . . . . . . . . . . . 13  <https://tools.ietf.org/html/rfc7297#page-13>
> 
> 3.8  <https://tools.ietf.org/html/rfc7297#section-3.8>.  Traffic Isolation . . . . . . . . . . . . . . . . . . . . 13  <https://tools.ietf.org/html/rfc7297#page-13>
> 
> 3.9  <https://tools.ietf.org/html/rfc7297#section-3.9>.  Flow Identification . . . . . . . . . . . . . . . . . . . 13  <https://tools.ietf.org/html/rfc7297#page-13>
> 
> 3.10  <https://tools.ietf.org/html/rfc7297#section-3.10>. Routing and Forwarding  . . . . . . . . . . . . . . . . . 14  <https://tools.ietf.org/html/rfc7297#page-14>
> 
> 3.11  <https://tools.ietf.org/html/rfc7297#section-3.11>. Activation Means  . . . . . . . . . . . . . . . . . . . . 15  <https://tools.ietf.org/html/rfc7297#page-15>
> 
> 3.12  <https://tools.ietf.org/html/rfc7297#section-3.12>. Invocation Means  . . . . . . . . . . . . . . . . . . . . 15  <https://tools.ietf.org/html/rfc7297#page-15>
> 
>       3.13  <https://tools.ietf.org/html/rfc7297#section-3.13>. Notifications . . . . . . . . . . . . . . . . . . . . . .16  <https://tools.ietf.org/html/rfc7297#page-16>
> 
> Cheers,
> 
> Med
> 
> *De :*Teas [mailto:teas-bounces@ietf.org] *De la part de* Vishnu Pavan 
> Beeram
> *Envoyé :* mercredi 19 août 2020 17:50
> *À :* TEAS WG <teas@ietf.org>
> *Cc :* TEAS WG Chairs <teas-chairs@ietf.org>
> *Objet :* [Teas] WG adoption - draft-nsdt-teas-transport-slice-definition
> 
> All,
> 
> This is start of a *three* week poll on making
> draft-nsdt-teas-transport-slice-definition-03 a TEAS working group document.
> Please send email to the list indicating "yes/support" or "no/do not
> support". If indicating no, please state your reservations with the
> document. If yes, please also feel free to provide comments you'd
> like to see addressed once the document is a WG document.
> 
> The poll ends September 9th (extra week to account for vacation season).
> 
> Thanks,
> Pavan and Lou
> 
> _________________________________________________________________________________________________________________________
> 
> 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.
> 
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
> 