Subject: [Teas] FW: Manual Post Requested for draft-ietf-teas-yang-path-computation

From: "Belotti, Sergio (Nokia - IT/Vimercate)" <[email-masked]>
Date: Thu, 31 Oct 2019 13:53:44 +0000

Dear TEAS WG,

We have just submitted an updated version of draft-ietf-teas-yang-path-computation.

One of the issue we have tried to address is the support for requesting protected paths:
https://github.com/rvilalta/ietf-te-path-computation/issues/49

We have taken into account feedback received in a previous IETF meeting (i.e., using two path requests with some association).

Since the changes are quite substantive, we have not updated the YANG model yet but just described how we are planning/thinking the model should be updated in section 5.3 and provided some information about the expected tree changes in Appendix B. 
The proposed modification has also the benefit, in our view, to better highlight relationship between requested paths and related tunnel, and the mapping with specific attribute of the tunnel.

We will present the proposal during Singapore meeting and would appreciate any initial feedbacks and comments at the meeting as well as on the list.

Sergio (on-behalf of co-author/contributors)

-----Original Message-----
From: IETF I-D Submission Tool <[email-masked]> 
Sent: Thursday, October 31, 2019 2:21 PM
To: [email-masked]
Cc: Daniele Ceccarelli <[email-masked]>; Oscar González de Dios <[email-masked]>; Michael Scharf <[email-masked]>; [email-masked]; Yan Shi <[email-masked]>; Ricard Vilalta <[email-masked]>; Belotti, Sergio (Nokia - IT/Vimercate) <[email-masked]>; Victor Lopez <[email-masked]>; Italo Busi <[email-masked]>; Anurag Sharma <[email-masked]>; Karthik Sethuraman <[email-masked]>
Subject: Manual Post Requested for draft-ietf-teas-yang-path-computation

Hi,

Manual posting has been requested for the following Internet-Draft.

Full idnits results are available at the end of this message.

I-D Submission Tool URL: 
  https://datatracker.ietf.org/submit/status/107455/

  File name       : draft-ietf-teas-yang-path-computation
  Revision        : 07
  Submission date : 2019-10-31
  Group           : Traffic Engineering Architecture and Signaling 

  Title           : Yang model for requesting Path Computation
  Document date   : 2019-10-30
  Pages           : 78
  File size       : 149.9 KB

  Submitter       : Italo Busi <[email-masked]>

  Abstract        : 
   There are scenarios, typically in a hierarchical SDN context, where
   the topology information provided by a TE network provider may not
   be sufficient for its client to perform end-to-end path computation.
   In these cases the client would need to request the provider to
   calculate some (partial) feasible paths.

   This document defines a YANG data model for a stateless RPC to
   request path computation. This model complements the stateful
   solution defined in [TE-TUNNEL].

   Moreover this document describes some use cases where a path
   computation request, via YANG-based protocols (e.g., NETCONF or
   RESTCONF), can be needed.

  Authors:
    Italo Busi <[email-masked]>
    Sergio Belotti <[email-masked]>
    Victor Lopez <[email-masked]>
    Oscar Gonzalez de Dios <[email-masked]>
    Anurag Sharma <[email-masked]>
    Yan Shi <[email-masked]>
    Ricard Vilalta <[email-masked]>
    Karthik Sethuraman <[email-masked]>
    Michael Scharf <[email-masked]>
    Daniele Ceccarelli <[email-masked]>

  Comment to the secretariat:

  Idnits result:

idnits 2.16.02 

/a/www/www6s/staging/draft-ietf-teas-yang-path-computation-07.txt:

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/checklist :
  ----------------------------------------------------------------------------

  ** The abstract seems to contain references ([TE-TUNNEL]), which it
     shouldn't.  Please replace those with straight textual mentions of the
     documents in question.

  Miscellaneous warnings:
  ----------------------------------------------------------------------------

  == Line 1347 has weird spacing: '...tion-id    uin...'

  == Line 1354 has weird spacing: '...ic-type    ide...'

  == Line 1363 has weird spacing: '...-- name    str...'

  == Line 1370 has weird spacing: '...ic-type    ide...'

  == Line 1439 has weird spacing: '...o usage    ide...'

  == (36 more instances...)

  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

  ** Downref: Normative reference to an Informational RFC: RFC 7491

  ** Downref: Normative reference to an Informational RFC: RFC 8453

  ** Downref: Normative reference to an Informational RFC: RFC 8454

     Summary: 4 errors (**), 0 flaws (~~), 6 warnings (==), 0 comments (--).

     Run idnits with the --verbose option for more detailed information about
     the items above.