From nobody Tue Dec 13 18:11:40 2016 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9C6F129841; Tue, 13 Dec 2016 18:11:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -107.098 X-Spam-Level: X-Spam-Status: No, score=-107.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nQmXYPfDk8Q4; Tue, 13 Dec 2016 18:11:32 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63D91129421; Tue, 13 Dec 2016 18:11:30 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 5A806B817C8; Tue, 13 Dec 2016 18:11:30 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161214021130.5A806B817C8@rfc-editor.org> Date: Tue, 13 Dec 2016 18:11:30 -0800 (PST) Archived-At: Cc: drafts-update-ref@iana.org, cdni@ietf.org, rfc-editor@rfc-editor.org Subject: [CDNi] RFC 8006 on Content Delivery Network Interconnection (CDNI) Metadata X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 02:11:35 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8006 Title: Content Delivery Network Interconnection (CDNI) Metadata Author: B. Niven-Jenkins, R. Murray, M. Caulfield, K. Ma Status: Standards Track Stream: IETF Date: December 2016 Mailbox: ben.niven-jenkins@nokia.com, rob.murray@nokia.com, mcaulfie@cisco.com, kevin.j.ma@ericsson.com Pages: 66 Characters: 126524 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-cdni-metadata-21.txt URL: https://www.rfc-editor.org/info/rfc8006 DOI: 10.17487/RFC8006 The Content Delivery Network Interconnection (CDNI) Metadata interface enables interconnected Content Delivery Networks (CDNs) to exchange content distribution metadata in order to enable content acquisition and delivery. The CDNI Metadata associated with a piece of content provides a downstream CDN with sufficient information for the downstream CDN to service content requests on behalf of an upstream CDN. This document describes both a base set of CDNI Metadata and the protocol for exchanging that metadata. This document is a product of the Content Delivery Networks Interconnection Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Tue Dec 13 18:11:59 2016 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 770EB129BA1; Tue, 13 Dec 2016 18:11:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -107.098 X-Spam-Level: X-Spam-Status: No, score=-107.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MN0KwW9lCt4P; Tue, 13 Dec 2016 18:11:44 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEE75129801; Tue, 13 Dec 2016 18:11:40 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id B86E3B817CF; Tue, 13 Dec 2016 18:11:40 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161214021140.B86E3B817CF@rfc-editor.org> Date: Tue, 13 Dec 2016 18:11:40 -0800 (PST) Archived-At: Cc: drafts-update-ref@iana.org, cdni@ietf.org, rfc-editor@rfc-editor.org Subject: [CDNi] RFC 8007 on Content Delivery Network Interconnection (CDNI) Control Interface / Triggers X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 02:11:52 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8007 Title: Content Delivery Network Interconnection (CDNI) Control Interface / Triggers Author: R. Murray, B. Niven-Jenkins Status: Standards Track Stream: IETF Date: December 2016 Mailbox: rob.murray@nokia.com, ben.niven-jenkins@nokia.com Pages: 49 Characters: 90108 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-cdni-control-triggers-15.txt URL: https://www.rfc-editor.org/info/rfc8007 DOI: 10.17487/RFC8007 This document describes the part of the Content Delivery Network Interconnection (CDNI) Control interface that allows a CDN to trigger activity in an interconnected CDN that is configured to deliver content on its behalf. The upstream CDN can use this mechanism to request that the downstream CDN pre-position metadata or content or to request that it invalidate or purge metadata or content. The upstream CDN can monitor the status of activity that it has triggered in the downstream CDN. This document is a product of the Content Delivery Networks Interconnection Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Tue Dec 13 18:12:19 2016 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 600491297EE; Tue, 13 Dec 2016 18:12:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -107.098 X-Spam-Level: X-Spam-Status: No, score=-107.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qha7YX1Hr6vu; Tue, 13 Dec 2016 18:12:08 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52525129801; Tue, 13 Dec 2016 18:11:55 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 4693DB817D8; Tue, 13 Dec 2016 18:11:55 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161214021155.4693DB817D8@rfc-editor.org> Date: Tue, 13 Dec 2016 18:11:55 -0800 (PST) Archived-At: Cc: drafts-update-ref@iana.org, cdni@ietf.org, rfc-editor@rfc-editor.org Subject: [CDNi] RFC 8008 on Content Delivery Network Interconnection (CDNI) Request Routing: Footprint and Capabilities Semantics X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 02:12:10 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8008 Title: Content Delivery Network Interconnection (CDNI) Request Routing: Footprint and Capabilities Semantics Author: J. Seedorf, J. Peterson, S. Previdi, R. van Brandenburg, K. Ma Status: Standards Track Stream: IETF Date: December 2016 Mailbox: jan.seedorf@hft-stuttgart.de, jon.peterson@neustar.biz, sprevidi@cisco.com, ray.vanbrandenburg@tno.nl, kevin.j.ma@ericsson.com Pages: 31 Characters: 61956 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-cdni-footprint-capabilities-semantics-20.txt URL: https://www.rfc-editor.org/info/rfc8008 DOI: 10.17487/RFC8008 This document captures the semantics of the "Footprint and Capabilities Advertisement" part of the Content Delivery Network Interconnection (CDNI) Request Routing interface, i.e., the desired meaning of "Footprint" and "Capabilities" in the CDNI context and what the "Footprint & Capabilities Advertisement interface (FCI)" offers within CDNI. The document also provides guidelines for the CDNI FCI protocol. It further defines a Base Advertisement Object, the necessary registries for capabilities and footprints, and guidelines on how these registries can be extended in the future. This document is a product of the Content Delivery Networks Interconnection Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Mon Dec 19 11:39:50 2016 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E21171295FC for ; Mon, 19 Dec 2016 11:39:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.202 X-Spam-Level: X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5BfLdMAxbX4R for ; Mon, 19 Dec 2016 11:39:45 -0800 (PST) Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (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 006091295F6 for ; Mon, 19 Dec 2016 11:39:44 -0800 (PST) X-AuditID: c618062d-aa3ff70000007359-18-58583d1124ef Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by (Symantec Mail Security) with SMTP id AB.B5.29529.11D38585; Mon, 19 Dec 2016 21:03:32 +0100 (CET) Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0319.002; Mon, 19 Dec 2016 14:39:40 -0500 From: Kevin Ma J To: "cdni@ietf.org" Thread-Topic: IETF 98 f2f meeting? Thread-Index: AdJaL8KKt3pnkA3qSZ20y5DHW4GulA== Date: Mon, 19 Dec 2016 19:39:40 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHLMWRmVeSWpSXmKPExsUyuXRPrK6IbUSEwYpGE4uns/+wOjB6LFny kymAMYrLJiU1J7MstUjfLoEr4/2a+cwFfWwVFy8+Zm5gvMjSxcjJISFgIvHhyyYwW0hgPaPE wdOcXYxcQPZyRomb89YwgSTYBLQkHn/9C2RzcIgIKEv8POQIEhYWkJX4uvwBM0RYSWLLLweQ sIiAnsT+h9tZQWwWAVWJNZN7wEp4BXwljl3kAgkzCohJfD8FMZxZQFzi1pP5TBDXCEgs2XOe GcIWlXj5+B8rhK0kMWnpOVaIeh2JBbs/sUHY2hLLFr4Gq+cVEJQ4OfMJywRGoVlIxs5C0jIL ScssJC0LGFlWMXKUFhfk5KYbGWxiBIbqMQk23R2M96d7HmIU4GBU4uH9IBIeIcSaWFZcmXuI UYKDWUmEV1Q/IkKINyWxsiq1KD++qDQntfgQozQHi5I4b9zq++FCAumJJanZqakFqUUwWSYO TqkGxvYPUqmfArUPSdzZ4bM2lmO31/dDstv5jP9vydH7aLFZnI+xVy6+NbLsmkGItu4f5+Nu Sww2n1NM7mg8/bHoYU5u2bxi+/3qnQLXDTn757AvC3ykz5XQnc/5I7vgaqX+pRx588gtNZ7f jVhO3o6Qf+n+2tw2ecoa3W4v0xMu8tz619KuGNxSYinOSDTUYi4qTgQAMeJG0VECAAA= Archived-At: Subject: [CDNi] IETF 98 f2f meeting? X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2016 19:39:47 -0000 Hi All, (as chair) Congratulations to the authors and the entire working group on= getting RFCs 8006, 8007, and 8008 out! A lot of folks put in a lot of har= d work over the past 6 years and it is great to have the core specs finally= published. With that, the only charter item still outstanding is the URI Signing dra= ft, and I'm sure the authors are eager to have completed as well. The chairs wanted to take a poll to see if folks think we need a face-to-= face meeting in Chicago. If the only topic is URI Signing, then we could t= ry to finish that up on the list. If folks want to propose other agenda it= ems (HTTPS, VR, etc.), please send mail to the list. Happy Holidays and Merry New Year to all! thanx! -- Kevin and Francois From nobody Mon Dec 19 13:22:23 2016 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50E6A127078 for ; Mon, 19 Dec 2016 13:22:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.7 X-Spam-Level: X-Spam-Status: No, score=-5.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LGlPflMVX1u0 for ; Mon, 19 Dec 2016 13:22:21 -0800 (PST) Received: from relais-inet.orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B307712965F for ; Mon, 19 Dec 2016 13:22:21 -0800 (PST) Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 72081C05B6 for ; Mon, 19 Dec 2016 22:22:19 +0100 (CET) Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.42]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 4CF9B1A0065 for ; Mon, 19 Dec 2016 22:22:19 +0100 (CET) Received: from OPEXCLILMA1.corporate.adroot.infra.ftgroup ([fe80::95e2:eb4b:3053:fabf]) by OPEXCLILM41.corporate.adroot.infra.ftgroup ([fe80::c845:f762:8997:ec86%19]) with mapi id 14.03.0319.002; Mon, 19 Dec 2016 22:22:16 +0100 From: To: "cdni@ietf.org" Thread-Topic: IETF 98 f2f meeting? Thread-Index: AdJaL8KKt3pnkA3qSZ20y5DHW4GulAADVwZA Date: Mon, 19 Dec 2016 21:22:15 +0000 Message-ID: <9597_1482182539_58584F8B_9597_7417_1_9bb5a393-ceb0-40c0-8004-2cc784f69d15@OPEXCLILM41.corporate.adroot.infra.ftgroup> References: In-Reply-To: Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.1] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [CDNi] IETF 98 f2f meeting? X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2016 21:22:23 -0000 Hi Kevin, Fran=E7ois and all, As far as we are concerned, we would like to propose an item on HTTPS deleg= ation for the meeting in Chicago. Thank you, Best regards, Fr=E9d=E9ric -----Message d'origine----- De=A0: CDNi [mailto:cdni-bounces@ietf.org] De la part de Kevin Ma J Envoy=E9=A0: lundi 19 d=E9cembre 2016 20:40 =C0=A0: cdni@ietf.org Objet=A0: [CDNi] IETF 98 f2f meeting? Hi All, (as chair) Congratulations to the authors and the entire working group on= getting RFCs 8006, 8007, and 8008 out! A lot of folks put in a lot of har= d work over the past 6 years and it is great to have the core specs finally= published. With that, the only charter item still outstanding is the URI Signing dra= ft, and I'm sure the authors are eager to have completed as well. The chairs wanted to take a poll to see if folks think we need a face-to-= face meeting in Chicago. If the only topic is URI Signing, then we could t= ry to finish that up on the list. If folks want to propose other agenda it= ems (HTTPS, VR, etc.), please send mail to the list. Happy Holidays and Merry New Year to all! thanx! -- Kevin and Francois _______________________________________________ CDNi mailing list CDNi@ietf.org https://www.ietf.org/mailman/listinfo/cdni ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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.