Re: [OPSAWG] Secdir last call review of draft-ietf-opsawg-model-automation-framework-06 Mon, 05 October 2020 08:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 954993A0E3F; Mon, 5 Oct 2020 01:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dDFqwN_hQ6Oi; Mon, 5 Oct 2020 01:02:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 903DD3A0E10; Mon, 5 Oct 2020 01:02:15 -0700 (PDT)
Received: from (unknown [xx.xx.xx.69]) by (ESMTP service) with ESMTP id 4C4Y3V0r7fz5wBH; Mon, 5 Oct 2020 10:02:14 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1601884934; bh=8r2GI4/MGJ9PTxR6r0RWEew3mJsvylAEpPP3AigQ2/o=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=sX5k9DRvjwCJ3GwUD44UXnbl7Z8u/fnG612fXstD3qinQODPULV15EsbHBuKV4jTZ jT5JKSjpbF8PRvupogAdv0K4DAXqkIht9eZM0LJqlhLNng66j8rGsHCMVQgXT1smR/ 2Z0vi31zP21GNvu+fi9prifnPv0mTSH/7Qw8I7L3QWn8TG/0mpwZhMBbNO8qaG0MOR RVhzUce740yrmClQHuoJHA+cwt66kLjOC7kYd+bKTpouybMTOtuspRp4X3LETqTR3i oIyeZtdPfFNXI/crq0PybdemUmkXCZFMq1GOpHRlOyPdBcYt1ycM4afKdpS1Awc6Iq 7xmiIC5GiBp+A==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.60]) by (ESMTP service) with ESMTP id 4C4Y3T6g64zyQY; Mon, 5 Oct 2020 10:02:13 +0200 (CEST)
From: <>
To: Christian Huitema <>, "" <>
CC: "" <>, "" <>, "" <>
Thread-Topic: Secdir last call review of draft-ietf-opsawg-model-automation-framework-06
Thread-Index: AQHWmdu2f0CAI4IxOUWO20psGbaR5amIjiTA
Date: Mon, 5 Oct 2020 08:02:13 +0000
Message-ID: <6471_1601884933_5F7AD305_6471_296_1_787AE7BB302AE849A7480A190F8B93303154CFFA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [OPSAWG] Secdir last call review of draft-ietf-opsawg-model-automation-framework-06
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 05 Oct 2020 08:02:22 -0000

Hi Christian, 

Thank you for the review. 

Please see inline.


> -----Message d'origine-----
> De : Christian Huitema via Datatracker []
> Envoyé : dimanche 4 octobre 2020 01:20
> À :
> Cc :;; draft-ietf-opsawg-model-
> Objet : Secdir last call review of draft-ietf-opsawg-model-
> automation-framework-06
> Reviewer: Christian Huitema
> Review result: Has Issues
> The document proposes an architecture for describing and
> provisioning services such as L3VPN or L2VPN. This is an ambitious
> architecture, aiming at providing end-to-end services over
> concatenations of network services provided by independent
> providers.

[Med] There is no such assumption in the draft but we can accommodate that case. 

 I am concerned that the model does not expose trust
> boundaries during these providers, and that the security section
> does not discuss what happens when some providers try to game the
> system or otherwise fail to cooperate.

[Med] The various blocks discussed in the document are within the scope of the ** same provider **. 

That's said, if a provider relies upon other providers to deliver a given service, the model will apply in a recursive manner: That is, a network can act as a "customer" and request services from other networks. The peer network will then follow the various levels depicted in the architecture to deliver the service.

Any failure of a peer provider to deliver an agreed service is a violation of the service level agreement. Such violation is detected by means of the service fulfilment/assurance and appropriate counter-measures will be followed. These counter-measures may be technical (switch to another provider) and/or contractual (penalties). 

We can add the following: 

   A provider may rely upon services offered by other providers.
   Appropriate mechanisms should be enabled by the provider to monitor
   and detect a service disruption from these providers.  The
   characterization of a service disruption (including, mean time
   between failures, mean time to repair), the escalation procedure, and
   penalties are usually documented in contractual agreements.
   Misbehaving peer providers will thus be identified and appropriate
   countermeasures will be applied.

> The architecture organizes functions in three levels, service,
> network and device. Creation of services will trigger requirements
> on the networks, and then configuration of devices. Performance
> monitoring at the device level will inform service assurance and
> service optimizatio at the network level, and service assurance,
> optimization and diagnostic at the service level. The configurations
> and the performance measurements are described using Yang models.
> The Yang modules are designed to be accessed through secrure
> protocols, such as NETCONF over SSH or RESTCONF over HTTPS. This
> provides authentication of the servers and protection of the data,
> and allows implementation of access control. That's a good basis,
> but these processes only secure "point to point"
> interfaces between functions in the system. This presupposes honest
> cooperation between all actors, despite the fact that those actors
> often are in competition.
> The security considerations consider misconfiguration attacks such
> as the creation of forwarding loops, leakage of sensitive
> information, and traffic isolation issues. These are all interesting
> issues, but they are only mentioned in the architecture document as
> guidelines for the future development of actual services. I think
> issues such as the protection of sensitive information should be
> developed in the model itself, because they are generic.

[Med] It is up to each individual model to call out those, not this document. 

> document articulates a hierarchy of Yang modules. Why does it not
> articulate the trust boundaries between the different actors?

[Med] Because the focus is on what happens within  ** a single provider **. The interaction with other providers is no more than a provider acting as a "customer" for a service offered by another provider. 

The customer-facing interface is out of scope. We think this this now clarified with the review from Brian. 

> In addition to three classes of issues listed in the security
> considerations, I am also concerned with possibilities of retaining
> or falsifying data. What if an actor hides or fakes performance
> monitoring data, either out of malice or due to faulty equipement?

[Med] All the levels are under the responsibility of the same provider. An underlying level can report performance data but the above level can also proceed with OAM checks as per Section 4.1.4. Anomalies can thus be detected locally.   

> Will that disrupt the provision of the services? What tools are
> available to detect such behavior? What if a network provide
> overpromises, in order to attract contracts? I understand that the
> ultimate remedies lies in contract obligations and contract
> enforcement, but that enforcement has to be based on data. How is
> the architectur organizing the collection of the data?

[Med] This is the role of the assurance functions. See also the NEW text suggested above.  

> On a side note, I find that this architecture cites a large number
> of other drafts such as evpn, l2vpn, l3vpn, etc. These drafts in
> turn presumably cite the architecture, thus forcing the RFC
> production to organize all of them in a large publication cluster.
> Is it really required for the architecture document to cite all the
> documents that will later use it?

[Med] None of these drafts is normative. There is not risk to create a publication cluster. 


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.