Subject: [Teas] FW: New Version Notification for draft-ietf-teas-yang-path-computation-18.txt

From: "Belotti, Sergio (Nokia - IT/Vimercate)" <[email-masked]>
Date: Tue, 22 Mar 2022 13:56:45 +0000

Hello chairs, all,

As stated in our notes contained in the "status" of the draft (attached) , we have just uploaded the new version -18, we think should be ready for WG LC.

Thanks

Italo and Sergio (on-behalf of authors/contributors)

> -----Original Message-----
> From: [email-masked] <[email-masked]>
> Sent: Tuesday, March 22, 2022 1:11 PM
> To: Anurag Sharma <[email-masked]>; Daniele Ceccarelli
> <[email-masked]>; italo.busi <[email-masked]>;
> Oscar Gonzalez de Dios <[email-masked]>; Oscar de
> Dios <[email-masked]>; Belotti, Sergio (Nokia -
> IT/Vimercate) <[email-masked]>
> Subject: New Version Notification for draft-ietf-teas-yang-path-computation-
> 18.txt
> 
> 
> A new version of I-D, draft-ietf-teas-yang-path-computation-18.txt
> has been successfully submitted by Italo Busi and posted to the IETF
> repository.
> 
> Name:		draft-ietf-teas-yang-path-computation
> Revision:	18
> Title:		A YANG Data Model for requesting path computation
> Document date:	2022-03-21
> Group:		teas
> Pages:		84
> URL:            https://www.ietf.org/archive/id/draft-ietf-teas-yang-path-
> computation-18.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-teas-yang-path-
> computation/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-
> computation
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-yang-path-
> computation-18
> 
> Abstract:
>    There are scenarios, typically in a hierarchical Software-Defined
>    Networking (SDN) context, where the topology information provided by
>    a Traffic Engineering (TE) network provider may be insufficient for
>    its client to perform multi-domain path computation.  In these cases
>    the client would need to request the TE network provider to compute
>    some intra-domain paths.
> 
>    This document defines a YANG data model which contains Remote
>    Procedure Calls (RPCs) to request path computation.  This model
>    complements the solution, defined in RFC YYYY, to configure a TE
>    tunnel path in "compute-only" mode.
> 
>    [RFC EDITOR NOTE: Please replace RFC YYYY with the RFC number of
>    draft-ietf-teas-yang-te once it has been published.
> 
>    Moreover, this document describes some use cases where the path
>    computation request, via YANG-based protocols (e.g., NETCONF or
>    RESTCONF), can be needed.
> 
> 
> 
> 
> The IETF Secretariat
> 

Subject: Status update on draft-ietf-teas-yang-path-computation (IETF 113)
From: italo.busi <[email-masked]>
To: 'TEAS WG' <[email-masked]>
Cc: TEAS WG Chairs <[email-masked]>, "[email-masked]" <[email-masked]>, "Belotti, Sergio (Nokia - IT/Vimercate)" <[email-masked]>
Date: Wed, 16 Mar 2022 18:33:18 +0000

Dear TEAS WG,

Please find below the status update for draft-ietf-teas-yang-path-computation

Current Status:

******* Revision -17 submitted on March 7

******* addressed Tom's comments on July 13 (as reported to the list)

******* aligned with the latest changes in draft-ietf-teas-yang-te-29

******* added security considerations

******* removed appendix A (as discussed on the list)

******* added examples (aligned with the examples in draft-ietf-teas-yang-te-29)

******* Revision -18 ready to be submitted

******* just fixing few nits

******* available on github

******* to be submitted as soon as I-D submission reopens

Next steps:

******* the authors believe the draft is ready for WG LC

Git Repo: https://github.com/rvilalta/ietf-te-path-computation

Thanks

Sergio and Italo (on behalf of co-authors/contributors)