Re: [Last-Call] Last Call: <draft-ietf-alto-oam-yang-12.txt> (YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol) to Proposed Standard
tom petch <daedulus@btconnect.com> Mon, 25 September 2023 11:57 UTC
Return-Path: <daedulus@btconnect.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB26CC151999; Mon, 25 Sep 2023 04:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uj_q_8ZRGmaM; Mon, 25 Sep 2023 04:57:43 -0700 (PDT)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-db3eur04on2119.outbound.protection.outlook.com [40.107.6.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA257C151993; Mon, 25 Sep 2023 04:57:38 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F8einAAr/NOP93bBL37C0GebMkmFZ2cYlYJyidWA3+mg1ilv7Glwkl8UwCrLS7PNQb4p6ugksg799Nv9CIXI80MjEsG7JZHQ3O5apF7VUWruIVv+7RgiRUNx/99y/smrMcdB0PVThi8pyrjnA6QSSxvFH0F0zCqLZcR3ObtkVeqEDaC/GBLYbHntKaoKfqlaI+dPaxaIyTxsTGfWFetL2c6cQDqF9Hr4cVhwDXuB1gbM3LmmKcD+JoRd+BT9XUJnO/Q8VshePlxGvWj5xDeBB8DyLOOGxP4LZA7iWhILVb+qtTKtCyf0klDwbGSzPiNam8a4URY2tZzFTqtKro6JkA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=AR+cyxLik9rj+SMJC7BRsrgGTNS5eXmkaCtrf8sWeng=; b=LPYXtOHj2JzZuZSDT9l6mZ31yb/84tuzXFB2GiBvzPyCLD2pfUbvch0FEzVDhEJ/59XZi79EPq/tsIndngPVihwTgi2PiklXl2eQdhngdEao79IBrHUSZxaXKg3iDt6u/ESJSeEcVCvmTmOcFcm4GaUOzNvdvbH3F4/cOhWsvwj0BrHOhnsDU8pIhMh64l5XiS0/onudYxJL3VebHEpSMlTLHJXVv6hQN2zjpnWWiflR8copSG8NOC4oTpFu7UuF/CCscmNGP9teExHhZRetNT+q/7OPX/Rn8gKZ1dQWWBmHDCT5FtQ1iW9jEAaVSuNOJCIfQmUWXl6tup4iv8jRaQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AR+cyxLik9rj+SMJC7BRsrgGTNS5eXmkaCtrf8sWeng=; b=YrhtMwH0DOmBD9UtpXABLvSsjGeIc/2s+FujHVZf5fj7Kl33e38DJ2W9gNK5VyAgBUV+kFHM0rwF9yNIEh7KTv7/k7eY05g/4e/GNJvBSyJLhte3wFEknJmBM24J4RvdD/PzVxXvSqBUcd1aZVMXLNpZ9MpsA6XUGiEwN2FeuCM=
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by DB9PR07MB9246.eurprd07.prod.outlook.com (2603:10a6:10:45b::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6813.28; Mon, 25 Sep 2023 11:57:35 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::981:77a3:1d89:dbae]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::981:77a3:1d89:dbae%6]) with mapi id 15.20.6813.027; Mon, 25 Sep 2023 11:57:35 +0000
From: tom petch <daedulus@btconnect.com>
To: "last-call@ietf.org" <last-call@ietf.org>
CC: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "alto-chairs@ietf.org" <alto-chairs@ietf.org>, "alto@ietf.org" <alto@ietf.org>, "draft-ietf-alto-oam-yang@ietf.org" <draft-ietf-alto-oam-yang@ietf.org>
Thread-Topic: Last Call: <draft-ietf-alto-oam-yang-12.txt> (YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol) to Proposed Standard
Thread-Index: AQHZ7W76ecu0vef2mEKRLKcn8PJZB7Arc00L
Date: Mon, 25 Sep 2023 11:57:34 +0000
Message-ID: <VI1PR07MB6704AAED540AA4A2431498A2C6FCA@VI1PR07MB6704.eurprd07.prod.outlook.com>
References: <169539880679.14638.14603557957902222631@ietfa.amsl.com>
In-Reply-To: <169539880679.14638.14603557957902222631@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=btconnect.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: VI1PR07MB6704:EE_|DB9PR07MB9246:EE_
x-ms-office365-filtering-correlation-id: 5f0eb2af-3de5-4e00-895e-08dbbdbe9b52
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: jun9VeRRtmsVtvdj4/9PhRU3RWmnYiwh1EDVXt0VNvk6VAL7g08BhowRoeu2EYyKlw4OzLgg4lEpikaQ+nnYT3IAprosiz9hOI/64plhfaNJUeBF1iPOOUquYbUXQzAQ4/zXeAiixdm8eDBi6HB91AVsYVX6e/w16mcwnW0exsZfL6XAM0SZac+msmNuv40KUoFj4Wgh310jngT+RfjwqhcjkouLlTGuo+5M/cGpjKgG1d9Ph3pFolah684yhorXTklC2ggyow+XGMkxueT/kccwISFmIKQn2vKHXzjBc+oP//T2dn2fBClQMraaidHVdyY0SkYGKT24gODxp7JcHuh5VcNawu3owx+3VKU/v9ntcXt2R0FDdm0YxaVC1wgfWu3Y/hV6pniu+TcDMt7qp283jwIeCoZDF/0UsuOEllhcEntykabaWQQB5lEgqO1bTg9K/UIRoUcolH3jXcjgn9QblWTSLJudZOSMxDYq8/uYEMhrw9R3tr7aHrghMzJxmlzs4e8iSVsn0YcL4jip1oXmFlYmPk7YQGjXrzmVroXhj0i4wrESPU2U1kxq0yphB9/MGD/fNzna78aSsfp3eCr130eXl7R/LoUDrbgqY4jOSF8wgN7gzTSiuMmfxFsgSGKvTSvhRoOO4j98pPo5gQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230031)(346002)(39860400002)(396003)(136003)(366004)(376002)(230922051799003)(186009)(1800799009)(451199024)(2906002)(55016003)(33656002)(86362001)(71200400001)(53546011)(26005)(66574015)(6506007)(9686003)(7696005)(82960400001)(83380400001)(38100700002)(122000001)(38070700005)(966005)(478600001)(91956017)(5660300002)(76116006)(54906003)(64756008)(66446008)(66476007)(66556008)(66946007)(52536014)(6916009)(8936002)(316002)(8676002)(4326008)(41300700001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: PIDzz33UKLH7Z+XWy/QVnjE7lmUXGQ05lC94ub+6KzNm4chaZxjiS4oycnPIBJDEwmv7rklHBYaHNgEbqJ63L3IoevLI7br0pIGgLDrRS/pBZoQ2tCsyXp/0YrKW3KFD2HxM6MLzuLESj0Dkn+UUZv3Ivyyt1Q6Ox9LJ7xpASB0QRF8LzpOd5DTHXW6843dkL9JkUjV5yJh6WUrJcjluP5vGsoI4r8Lj5TBj7ZRYcMm8OJ9Wltulf6Zv8+7mSJ6eZvKoAxoI3YmkSowhyzmMlPP/QaWBWJAZ7RUpwscXKilEACuhtcvq0BP+sCTcubNuMF/3UraKmrU+INqGXKle6FrhzUPYnI+luL0BTOsPobYEDAAqN2O2cqYtz1/EVipC34EupxMY9XJtS+GgRneowjZSNYFCCyvAUX8hyH9GTCHudxuZwTlKgOusKmh0RnauvKGbuGTsRS7p5IBzKDJ1UV75JCHNJUokIQZlrRkqyMN3dJBurTmtaMqltqxDxi5Lg2pG9jxjkFPUI9oaFR4yiCy4J9A7cCydymDcIcXY89+qNSw6lC898vLSbeiGwXatJWIPbPFoRhL2LgB/n+7SS21cODe0WjgiMxoOYBNDEI/ynqrs3NkB/uvd3YqakeeXCE0aIl6lOHqC6eznTkLPyQS97i9inMJysHZ0UqdN+Qewl0reGCGcP6b9ufpDbY1PkZRZbldsDLHjTMRkx7EyCOsG5Erbxk5HKX4JAmtsg/q4yKU7jjTBeo/cVcnux7M95UX+ttQCLeJDMqKH3EIzSlDE05VpJ84uAGPFAH5PrDA95MAsnU9P9IO0azwSszlpj3188oJzCqzysG831FnjvhHdN7EugkvNefzb1+cg4HUjh98RSO4DvbmCnHNzVnz9G3TT9gnjUlxuNvbXIFaJPK5dOCHUzIgDfOfjLj8hsAFeFW+w48oB10glJLQEKSng/054bYtdRFkP3kH68l7m1ZBGZV1Z2SIjKmsa/zmnfv7TGNvfr9RqI1dwiaTxDlKqjOckE/lCRkdiAyRUanZ1govPbhZaTGaUl+2Af5/5v5rYfddzvT0QjCmD20HgZEWvRKO6F8VS85GFrzaW4MiTD4uat8X15qpeQ2X9JL3HAyBH/v6vY5SaT3sLvenx2+s0nUHDmCSRwoKEsPM11dAEtbexYjUJHTDZaAn0TJhEhrak+cZ7mTcQSYRwN97KxBpjyTTX/thMQD41S9ipgEyUY8ooi1eIDw0YASam4BDeTzEWyGJa9cwr9dCGdOpNECh7SxBiQ2TleqXt6vstY/PYEdMmGRVIO8vsZq31oQ57oRSne7lj5H0LqqkvsnBmcUeKSdY3i5d1Uk75ikLPkE6mDZgD6CMHLlInyLa9WUJO8ZqrHUJxq/wJBDuV+n2RNNA8B6ssYAgi00s4vgvc6FkaPD5XLcsCBys7VG8Hpnhzer3A/zdBe1C0TKFg9kgBMsU58VdcsFWgTdEEZ5+zcjflTXLbnzTBTw3XmoV+f9i6Dtcd9DEIylKX/gNo64si2okhR46lcpiaO7jGn3JPXva3M7wPaXqt4H0dDBFe3y3amTW7t+XW7XGmgacp4G6rYZ22
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5f0eb2af-3de5-4e00-895e-08dbbdbe9b52
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Sep 2023 11:57:34.9876 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jw62/0B8UCwdAw3TxCYFldFwEkMNsJQGJHwqJXprTOJjjN25YWK95UaojwRmKAEt3+o+wcD5rk61VdLl2d3LYw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB9PR07MB9246
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/ug0A3t5A3u7BBuHfePgaOgofKzc>
Subject: Re: [Last-Call] Last Call: <draft-ietf-alto-oam-yang-12.txt> (YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol) to Proposed Standard
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Sep 2023 11:57:44 -0000
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@ietf.org> To: <i-d-announce@ietf.org> Cc: <alto@ietf.org> 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@ietf.org> on behalf of The IESG <iesg-secretary@ietf.org> Sent: 22 September 2023 16:06 To: IETF-Announce Cc: mohamed.boucadair@orange.com; alto-chairs@ietf.org; alto@ietf.org; draft-ietf-alto-oam-yang@ietf.org 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@ietf.org mailing lists by 2023-10-06. Exceptionally, comments may be sent to iesg@ietf.org 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@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
- Re: [Last-Call] Last Call: <draft-ietf-alto-oam-y… tom petch
- Re: [Last-Call] Last Call: <draft-ietf-alto-oam-y… mohamed.boucadair
- Re: [Last-Call] Last Call: <draft-ietf-alto-oam-y… tom petch