Some stray thoughts
'source-type' I do not understand. The module defines it but it is not
used except as a base in the vendor example. I would suggest more
explanation ( and I confuse sourve-id with 'resource-id')
RFC9274 is in the YANG module - needs adding to the I-D references
RFC GGGG in the YANG module has a title which is not quite the same as
that current I-D; mind that I-D has changed so much that it could change
again before reaching the RFC Editor!
5.4.1. Data Source Configuration Management
To satisfy R5-1 in Section 4.2, the ALTO server instance contains a
list of 'data-source' entries to subscribe the data sources from...'
Not quite English - not sure what it is saying (even if it has been
there since -00)
5.4.3
IRD needs expanding on first use - perhaps add it to the definitions as
well
1..max can be a Very Long string - that said, that is what many models
have with the implementors expected not to fail when given a string
terabytes in length
"Type for a data source ID that are used to reference a data
source.";
Perhaps
"Type for a data source ID that is used to reference a data
source.";
list meta {
the identifier 'meta' has been appropriated by an internet giant that you may
or may not want to be associated with. 'metadata'? meta-key I think
fine
"ALTO information resources to be defined";
to be defined has overtones of we do not know yet - perhaps use a
different formulation. And I am unsure what it means
leaf is-default {
type boolean;
description
"Sets whether this is the default network map.";
I like my booleans to be clear about what they mean when true. Perhaps
"When true, this entry is the default network map"
except that I do not think I understand this leaf - often the default is
the entry in a list to be used when nothing is specified but I do not
see the list here.
And is there a default, such as false, for this boolean?
Appendix A
examples should use the values reserved for documentation use
prefix vendor-alto-disc;
two problems; it is looooong for a prefix, the difference between e.g
type leafref {
path '/alto:alto/alto:alto-server/alto:data-source'
+ '[alto:source-id'
+ ' = current()/../source-datastore]'
+ '/alto-ds:yang-datastore-source-params'
+ '/alto-ds:target-paths/alto-ds:name';
type leafref {
path
'/vendor-alto-disc:alto/vendor-alto-disc:alto-server/vendor-alto-disc:da
ta-source'
+ '[vendor-alto-disc:source-id'
+ ' = current()/../source-datastore]'
+ '/vendor-alto-disc:yang-datastore-source-params'
+
'/vendor-alto-disc:target-paths/vendor-alto-disc:name';
and there is nothing there to say that this is an example. We need a
prefix for prefixes to say that this is an example, like we have
addresses reserved for documentation. Some vendors will think that all
vendor prefixes must be 'prefix vendor-alto-disc', a good recipe for
confusion. I would use eg-
prefix vendor-alto-ds;
ditto
module example-vendor-alto-data-source {
yang-version 1.1;
namespace "https://example.com/ns/vendor-alto-data-source";;
prefix vendor-alto-ds;
but
import example-vendor-alto-data-source {
prefix alto-ds;
consistency is good but only having sorted out what the prefix should
be.
eg-alto-ds?
I hope to look some more but will probably not find the tome.
Tom Petch
----- Original Message -----
From: <internet-drafts@xxxxxxxx>
To: <i-d-announce@xxxxxxxx>
Cc: <alto@xxxxxxxx>
Sent: Friday, September 22, 2023 4:38 PM
Subject: I-D Action: draft-ietf-alto-oam-yang-12.txt
> Internet-Draft draft-ietf-alto-oam-yang-12.txt is now available. It is
a work
> item of the Application-Layer Traffic Optimization (ALTO) WG of the
IETF.
>
> Title: YANG Data Models for the Application-Layer Traffic
Optimization (ALTO) Protocol
> Authors: Jingxuan Jensen Zhang
> Dhruv Dhody
> Kai Gao
> Roland Schott
> Qiufang Ma
> Name: draft-ietf-alto-oam-yang-12.txt
> Pages: 79
> Dates: 2023-09-22
>
> Abstract:
>
> This document defines a YANG data model for Operations,
> Administration, and Maintenance (OAM) & Management of the
> Application-Layer Traffic Optimization (ALTO) Protocol. The
operator
> of an ALTO server can use this data model to (1) set up the ALTO
> server, (2) configure server discovery, (3) create, update and
remove
> ALTO information resources, (4) manage the access control of each
> ALTO information resource, and (5) collect statistical data from
the
> ALTO server. The application provider can also use this data model
> to configure ALTO clients to communicate with known ALTO servers.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-12.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-12
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> =
________________________________________
From: IETF-Announce <ietf-announce-bounces@xxxxxxxx> on behalf of The IESG <iesg-secretary@xxxxxxxx>
Sent: 22 September 2023 16:06
To: IETF-Announce
Cc: mohamed.boucadair@xxxxxxxxxx; alto-chairs@xxxxxxxx; alto@xxxxxxxx; draft-ietf-alto-oam-yang@xxxxxxxx
Subject: Last Call: <draft-ietf-alto-oam-yang-12.txt> (YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol) to Proposed Standard
The IESG has received a request from the Application-Layer Traffic
Optimization WG (alto) to consider the following document: - 'YANG Data
Models for the Application-Layer Traffic Optimization (ALTO)
Protocol'
<draft-ietf-alto-oam-yang-12.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
last-call@xxxxxxxx mailing lists by 2023-10-06. Exceptionally, comments may
be sent to iesg@xxxxxxxx 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 Operations,
Administration, and Maintenance (OAM) & Management of the
Application-Layer Traffic Optimization (ALTO) Protocol. The operator
of an ALTO server can use this data model to (1) set up the ALTO
server, (2) configure server discovery, (3) create, update and remove
ALTO information resources, (4) manage the access control of each
ALTO information resource, and (5) collect statistical data from the
ALTO server. The application provider can also use this data model
to configure ALTO clients to communicate with known ALTO servers.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/
No IPR declarations have been submitted directly on this I-D.
The document contains these normative downward references.
See RFC 3967 for additional information:
rfc9275: An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector (Experimental - Internet Engineering Task Force (IETF))
_______________________________________________
IETF-Announce mailing list
IETF-Announce@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf-announce
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
