Re: [Teas] Last Call: <draft-ietf-teas-yang-te-topo-15.txt> (YANG Data Model for Traffic Engineering (TE) Topologies) to Proposed Standard

[Xufeng Liu <[e-mail]>]

Hi Tom,

Thanks for pointing out these. We have posted

We have posted an undated version
*https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-17
<https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-17>* to include
the fixes for these.

Best regards,
- Xufeng

On Tue, Jun 5, 2018 at 1:01 PM, tom p. <[e-mail]> wrote:

> Lou et al
>
> I note that the YANG module in this I-D has Reference statements to 20
> other RFC, which is good, but only one of the twenty appear in the
> References for the I-D, which I think is not good, and needs to be
> fixed.
>
> Also, some of the RFC which appear in Reference clauses of the YANG
> module appear in [square brackets] e.g. [RFC6001] which I think should
> not be there.
>
> In the same vein, there are imports of four other YANG modules but no
> indication as to which RFC they can be found in - again, I think that
> that needs fixing with a Reference statement.
>
> A quick pass suggests the missing references are to
> 1195 missing
> 3209 missing
> 3272 missing
> 3471 missing
> 3630 missing
> 3785 missing
> 4201 4202 4203 4206 all missing
> 4872 missing
> 5152 missing
> 5212 missing
> 5305 missing
> 6001 missing
> 6241 ok Norm
> 7471 missing
> 7752 missing
> 7579 missing
>
[Xufeng]: Fixed.

>
> Russ's comment about Section 1.1 does not seem to have been addressed.
>
[Xufeng]: Fixed.

>
> Tom Petch
>
>
> ----- Original Message -----
> From: "The IESG" <[e-mail]>
> To: "IETF-Announce" <[e-mail]>
> Cc: <[e-mail]>; <[e-mail]>;
> <[e-mail]>; <[e-mail]>
> Sent: Wednesday, May 16, 2018 3:40 PM
>
> > The IESG has received a request from the Traffic Engineering
> Architecture and
> > Signaling WG (teas) to consider the following document: - 'YANG Data
> Model
> > for Traffic Engineering (TE) Topologies'
> >   <draft-ietf-teas-yang-te-topo-15.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> final
> > comments on this action. Please send substantive comments to the
> > [e-mail] mailing lists by 2018-05-30. Exceptionally, comments may
> be
> > sent to [e-mail] instead. In either case, please retain the
> beginning of
> > the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    This document defines a YANG data model for representing,
> retrieving
> >    and manipulating Traffic Engineering (TE) Topologies. The model
> >    serves as a base model that other technology specific TE Topology
> >    models can augment.
> >
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/
> >
> > IESG discussion can be tracked via
> > https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > The document contains these normative downward references.
> > See RFC 3967 for additional information:
> >     rfc5212: Requirements for GMPLS-Based Multi-Region and Multi-Layer
> Networks (MRN/MLN) (Informational - IETF stream)
> >
> >
> >
>
>