Re: [recipe] And another new draft revision: Green Networking Metrics

"Schooler, Eve M" <eve.m.schooler@intel.com> Wed, 30 November 2022 07:54 UTC

Return-Path: <eve.m.schooler@intel.com>
X-Original-To: recipe@ietfa.amsl.com
Delivered-To: recipe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB3AC14CF1F for <recipe@ietfa.amsl.com>; Tue, 29 Nov 2022 23:54:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.394
X-Spam-Level:
X-Spam-Status: No, score=-4.394 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 (2048-bit key) header.d=intel.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 o3CTScuhwrqR for <recipe@ietfa.amsl.com>; Tue, 29 Nov 2022 23:54:10 -0800 (PST)
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (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 DEB87C14CF0C for <recipe@ietf.org>; Tue, 29 Nov 2022 23:54:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1669794849; x=1701330849; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=4gf4Fy7Bzka4vSryDtLBuncoixCy4fpV4JRnS3WqWjI=; b=MNT/IFyw8mTc4aglGt+83eEC1UeOJpCDWnz2nISttE7kQjVg8YKTC1V3 mVyHzyPnK9jr3Qh6meiI16Rcmi/6ejj5r4gYQ2B9XHuL0/Ws1JF7T12IG lsf1Dca29E4o3jSQWSDuDIICI6orku3pn5910siVUSHW8msoEJX/SaAiS S/iP3qTzBDcgmiprn46rxMD+9vw5JUjvmkmRICV4XKrETesdjsL+behbD tIuINNLKn0/Yl//uLtq3vGgaiL1oFQBKkI1EVleIV64wVSl3Kit8zR3Hl hOPfU87124xiY8P70W0ljlShthDN7422cq3xpq0vE9A15YeIA0USR/wIs Q==;
X-IronPort-AV: E=McAfee;i="6500,9779,10546"; a="316484542"
X-IronPort-AV: E=Sophos;i="5.96,205,1665471600"; d="scan'208";a="316484542"
Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Nov 2022 23:54:02 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=McAfee;i="6500,9779,10546"; a="818535989"
X-IronPort-AV: E=Sophos;i="5.96,205,1665471600"; d="scan'208";a="818535989"
Received: from orsmsx601.amr.corp.intel.com ([10.22.229.14]) by orsmga005.jf.intel.com with ESMTP; 29 Nov 2022 23:54:02 -0800
Received: from orsmsx610.amr.corp.intel.com (10.22.229.23) by ORSMSX601.amr.corp.intel.com (10.22.229.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.16; Tue, 29 Nov 2022 23:54:01 -0800
Received: from orsmsx610.amr.corp.intel.com (10.22.229.23) by ORSMSX610.amr.corp.intel.com (10.22.229.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.16; Tue, 29 Nov 2022 23:54:01 -0800
Received: from orsedg603.ED.cps.intel.com (10.7.248.4) by orsmsx610.amr.corp.intel.com (10.22.229.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.16 via Frontend Transport; Tue, 29 Nov 2022 23:54:01 -0800
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (104.47.59.177) by edgegateway.intel.com (134.134.137.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.16; Tue, 29 Nov 2022 23:54:01 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Oc/TDYLAAODqJFIQDc/oyy3dr42qLQZSQy0Y6iCjpBCWuQEuG2e0y2CPB3+hKXTLDZex2lqEf+dKsvcatZyV/rZyOlbnQy9cdqqNAupfCH+k5MTJPdMAEeJtziIBm66qBEsmj0uYeZhlB/aZiazFzZjQyUp75w2C7Z5mLD3OnJYSS0voBq4D5+Gh4Rci/2qycf63KcrfwCsAb6SRz+ZiU68FnNfdxnoe59LJSl/NosFLBpbnHgtM2y9qYSkQof6JsrwTznKFdwbnGh0buFwIFmYeaDCFXmYvn9rz/7xZFhczL6Ib/iFMVQIH7hqHRbJRL00wwvoASp8a3LXc9XapXw==
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=06YynNVcr7YB4LF4GxC7PDpuuNOL57PFbZJGxW6/B5o=; b=P5+Ry025PAYLLE0ZhOjnPH79eZvTvpFFT4u1GEAxNXtylPkly/TsIiS/xgoMcVK9h1uuFujrMyMeew43eL5FZKXG15nw5c5FjqmSJ9e3I2Ubt0KIG6KwvW0djytKixMPESkzsvtphubTyhm3GBzNE8OYE9oRs1OxMGq8+yUFMAFb0gOXjzfIHFTl/o3io3d1xoCc/98kYH+DPHAuXPBVmnVdHdWpMXg/WSw1bLfaVW2ff8Mv5py4OMNS9XR9V1BrZArPuGuxKhImKUUm3or4L03gcvF9ysBQZPoB74xgjwDRtsbHH7eB+whqc3WZan9KFGIq+byLadG4XMEXQU8sVw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none
Received: from SN6PR11MB3150.namprd11.prod.outlook.com (2603:10b6:805:d1::25) by IA1PR11MB7680.namprd11.prod.outlook.com (2603:10b6:208:3fb::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5857.23; Wed, 30 Nov 2022 07:53:54 +0000
Received: from SN6PR11MB3150.namprd11.prod.outlook.com ([fe80::50c:ffc4:3e5a:e4df]) by SN6PR11MB3150.namprd11.prod.outlook.com ([fe80::50c:ffc4:3e5a:e4df%7]) with mapi id 15.20.5857.023; Wed, 30 Nov 2022 07:53:54 +0000
From: "Schooler, Eve M" <eve.m.schooler@intel.com>
To: "recipe@ietf.org" <recipe@ietf.org>
CC: "Schooler, Eve M" <eve.m.schooler@intel.com>
Thread-Topic: [recipe] And another new draft revision: Green Networking Metrics
Thread-Index: AQHZBJDkeOanDOmY/UqNW2LWr3Cpog==
Date: Wed, 30 Nov 2022 07:53:54 +0000
Message-ID: <SN6PR11MB31504BE5143C6045A1567781D7159@SN6PR11MB3150.namprd11.prod.outlook.com>
References: <mailman.127.1666378803.33896.recipe@ietf.org>
In-Reply-To: <mailman.127.1666378803.33896.recipe@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=intel.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: SN6PR11MB3150:EE_|IA1PR11MB7680:EE_
x-ms-office365-filtering-correlation-id: 5a2c35bf-fad5-429c-c93d-08dad2a80713
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 2LMYU69rJ7jQtn5k+cCdo+JBbNvwNHOoT+8aesCMK/Et+AAeHhTy7jhnn90i9RSdkGWG9mo96wZP5vmv1HXowZv/cNVViB3dr/9CSIQWaHZhxSzH7u6f1+3E55HZ4zCsgvSrGZpOKbhDatDh6aCQzPyw+xiw0rBIeov1gvTIgpnibuJD4Jl2gN7rO+/CjlgMqwzucpY6IEgCheKPIf1OmTmWHzYU3C2zdLq+u+M0fE/5YhrJdsL9CXtlJhMLYNn+b/ECFakN47ghuVaS6qQi6iKqGajEK8bCqVGjLAUm3nH6QHhs7ciQg8ZKILYtLVoohuOkbgYWfYWwl9e0gKpnz7DadnXjfkfj5Q77CZfVsvQlBhpz20fKM24XJuRJdntruqFZSeRkyM8AxVGtSDpArKxZ5XMWJEwfZbq3VJEWQzKSGqTjMX/u8a7mwBACXZh4lajV0lw73Fg11n5qMiKgrFAks1qucyacnY7cQHmIOIIe9Bu/lNpM8BOpRu+vC7Z/AuQvTtsmNu3HPXsySZGCYQ7wgT4qFj+kW2NazETApsnzF6s0wG0ZcBqKgzp66CdTQxflQ9GFCF1aJD7IqI9Xc3VlTo3sdunhzQCg8lHjap/UsuOYIlY5uVrrZCWUFnqkAbgZxCaYyBlGsXMvQ76iavJAoUqIKUcndKW5BkT6HC98n7YbnObnbl02HmDYHhpjpQWA0Z7vIirbHf7WalwdoFowqIcVOEx62lZo67alvhE=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:SN6PR11MB3150.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230022)(376002)(39860400002)(366004)(346002)(396003)(136003)(451199015)(8936002)(66556008)(66476007)(76116006)(66946007)(64756008)(66446008)(40140700001)(8676002)(33656002)(5660300002)(41300700001)(52536014)(86362001)(107886003)(122000001)(71200400001)(26005)(6506007)(7696005)(83380400001)(9686003)(66574015)(53546011)(186003)(6916009)(316002)(55016003)(38100700002)(38070700005)(966005)(478600001)(4326008)(2906002)(66899015)(82960400001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: hsg3WFARc6O9VURrYxd+HuC6dHZHSrD9g2WSvnktiL+8uKcMJMRoMDPY4hYiovlLSJmwFaD158OrJaMnxLw2/6zJZNnCzeQligJnU9sDck6qaJ7u502v4rC6e0OAIgpfWAdV+uWP1NzRVKrmEN7JnBHLlRyXXioOlnxA5qHFEOkwONThIcwT/GHC4AKO9KcDBcWuIe6stMlszZ/d5UWpd5QXOxXXZTXzj1mLPvfeyhvhSLK6G07OMNd9URSFeKkMxD/zDxpsoE0XZpdPvQTggWJlfyDnRDsjHDHDC3Rl9zSNuF9TyQ/t91615kcODKT1WAYV4QMaEFJwb55WLnVMalXZZEgVyOjzSu4zQrR9huJtLt19Bc/tHJ+LuzXZk4LKEsf5u9fGt8yYCKUPiT8tIWW9k2ELCNL2ZvC8bhzXuHi0BtyPPWY9chgSMbGHIBJz14Hze7l6MpgiilpR/TjBh5tOPiGtZ406ukCUGSom7N6vyOZr7C1qkvXc1sIlUBipxFuFkljoufNjuM2kokpgAVB7AEClhKj/MZH5fhP8bjLRQwyW+CkPYc+n+fUXjYbgOul9/48hHHJHNe4O1HjQRK1PyY+gT0EjDoqdpco+cay2R9ttaZW2GlBsr9sDcUn7y73iGcVgZD2QwPBMCmn5rcgubMEoHJwR4u1Mkm1B1cwMS6Q6pA2emnZO52YgeVfc4hS4QMEowr3Gb5I5ciOo5aRwwFHAE6DteTlm2Q05PqGXTQf+HZX5YDu7wEWfAje0692zfUoR35jxNKtrpty7XXJFpM/qZZbNAEYNZ8Ruh9ajRTefzb7N/I5XpPj0poVJHeFhU5MTotKF/E5sGrgrEzSU+06EwYyBXmSfelau6GVDAODrna4bGgFrxtesrwL4jU3Dy4dIDvT/iwXKoZx1+/oDmDWj3OytzGHnK5HAB/BvuK6TJ7S+R2j5HxQweXbZYET30odSFCqicLTL4yAKT92o34rlLvNRvoPoPCtwiOsrzLgsM+T7xj5ogzv1sqi7aBjj4TgCHAsFAd4ulh5EFZkF6R1axFDfFCs61MOUxmO9lozN7gVob3pLVt+iVAT4h3SNcl/MCtneYaiUHiE6KEJbqD+PJCKWi1V85vdDT61w06QsNicqs330OvhJjxwhTjmQ2TgW4Zd+d2hCM+m4/Shj73mS58W6SYYnazLtMi0CEhvluVf8Fbi1Th2V/G7UitwJzPjHiHRzmVBpx6wcg9ZS7UCyczWjmsyGTBrqKwIcQ3yBka8p+oHV0J4tYTAMsKvJekXrqH0B1dUVK7s+/zRINukbHvi9upFv0wR6NQEAPerWN3Bv8kqHr7ysU8sWWr/dVBckEYmW4MhrYSYwFRL9K9E0P/3ZMXOJwIrWOdSNrE5t8ZB/scuV9vKADN4wTPPWogWU9mauDVlUknwuLNlJdAJnZT0xGacA9mPlsI9KckQ+fXpwxlnzh6Yb0Ce4KBc7ExfB19HuBioFW5qj+e54XZzkzKbBRLX8xq/oSNsqsvaQ/tlosIlVcaY0joa6HllcPplN3QXnca7XMDVZC9SQuLNGDw7FpJPTpn9XQCDRzxf5EJBn9m8Iwgv09+px
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SN6PR11MB3150.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5a2c35bf-fad5-429c-c93d-08dad2a80713
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Nov 2022 07:53:54.0953 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: FgxdCDcEqSjrgnAGjADUfKBOMypvna1cdAf2C3HeCH/FVmqYLHz6kPl5WmOJfbgYi6xwj1N2X14wg1rekNDnnZ2QIrhlmhX2NDLwKH09oZs=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: IA1PR11MB7680
X-OriginatorOrg: intel.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/recipe/FdeWB_zjTwvX7sXP1GHCGWd9onI>
Subject: Re: [recipe] And another new draft revision: Green Networking Metrics
X-BeenThere: recipe@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RECIPE \(Reducing Energy Consumption with Internet Protocols Exploration\)" <recipe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/recipe>, <mailto:recipe-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/recipe/>
List-Post: <mailto:recipe@ietf.org>
List-Help: <mailto:recipe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/recipe>, <mailto:recipe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2022 07:54:14 -0000

Hi Alex and co-authors, 
Thanks for a very interesting read (https://datatracker.ietf.org/doc/draft-cx-green-metrics/)!
Here is some informal feedback on the latest version of the draft document.
Best regards, 
Eve

Eve M. Schooler, PhD
Principal Engineer & Director
Intel | CSO & NEX | Emerging IoT Networks
2200 Mission College Blvd., Santa Clara, CA, USA  95054
+1 650.868.7369
-----

Abstract:
In the abstract there is reference to "power consumption, energy efficiency and carbon footprint", for both network equipment and services provided over it - would be great to describe the relationship between these three attributes somewhere. In the Intro, language is also used re "environmental sustainability of networks", which may go beyond energy-related metrics.

Section 1. Intro
- Why cite the Telefonica Consolidated annual report vs Sustainability report?

Section 2. Definitions and Acronyms
- Include kWh

Section 3. Energy Metrics
- For each bullet, give examples of existing metrics.
- 3rd bullet references energy intensity. Is this a term commonly used? Does it need specific definition
- Either way, contrast this with carbon intensity.

3.1.1 Energy consumption Metrics
- Any thoughts/precedent on how to separate the carbon footprint of a device from the networking aspects of the device?
- Are we only gaging router power consumption, or other network HW elements? What about SW? Different parts of the stack?
- Love the reference to ATIS, which makes me wonder about certification of the numbers associated with the various device elements and the devices overall?
- Re "The second set of metrics reflects the actual power being drawn during operation." What about embodied carbon, which for smaller devices such as phones is a dominating factor?
- Odd to see the terms "kilooctet" and "gigaoctet"; why not simply kB or gB? Yes to pico Joules.

3.1.2 Other Metrics
- A common sustainability rating of the power source is carbon intensity. A good publication to read, where carbon intensity is considered, but so is a waste metric to capture environmental impact beyond energy and carbon: 
    + Hossain, Md. Mohaimenul, Georges, Jean-Phillippe, Rondeau, Eric, Divoux, Thierry. Energy, carbon and renewable energy: Candidate metrics for green-aware routing? Sensors, 19(13), Feb 2019.
- "It may be possible to obtain such a rating from the energy operation...."
    + I really like that the document includes such a statement. It would be helpful for each of the metrics discussions to include: from whom the measurements for the metric might originate
- If deployment of the device is outside a Data Center (DC) and actually is in the wild, e.g., an RSU (road side unit), should the device be charged an energy tax for releasing its heat into the atmosphere?

3.1.3 Virtualization Considerations
- 2nd paragraph seems to imply that DCs because they are more energy efficient should be the target environment of choice. However, in Edge IoT contexts, there may be too much data to be able to migrate a container to a back-end cloud, thus the cloud must stay local. In other words, the choice to process a container locally may have other constraints (data volume, privacy, latency, that prohibit it from being placed in a more PUE-optimal setting).
- Orchestration SW, Developers, run-time systems, are all going to want to have insight into how to untangle virtualization and CFP. Perhaps the demand is to insist that HW manufacturers support SW APIs that can extract and export this data upon request. IETF may or may not be the place to define those APIs, but we should help critique them and ensure they support the metadata we need to properly calculate and to properly attribute impact of the network elements (HW/FW/SW).

3.2 Energy Metrics related to Flows
- "In its basic incarnation, those metrics reflect the energy consumption at a given device."
    + There are many hidden devices that are like supporting cast members for each Layer 3 device, making this seem nearly impossible, unless the owners/operators are involved in assessing the supporting infrastructure that enables that device. This is similar to saying services reside in DCs and they consume x% of the overall energy, therefore there is a fair share of a carbon tax that all services must contribute towards cooling.
- "Amortized energy consumed over the duration of the flow"
    + Expecting this to help us compute the aforementioned carbon tax that goes unaccounted when we only consider the router itself. Basically, compute a percentage of the total unaccounted for energy usage, to tax the app or flow.
- "A second set of energy metrics related to flow might aggregate the flow's energy consumption over the entire flow path". 
    + This should be do-able at least if thought of as an approximation or a bound/threshold of some sort
    + Also, it begs the question if we can/should reserve resources along that path to use lowest carbon-intensity

3.3 Energy Metrics related to Paths
- Need to articulate somewhere how energy usage and carbon footprint relate to each other. It would then be more clear that carbon-intensity is a useful attribute for consideration in these steering decisions, as the carbon-intensity of electricity in Poland is 80x the carbon intensity of electricity in Sweden.

4.1 User perspective
- A discussion of incentivization could be fruitful here (or at least a discussion of stick vs carrot, tax vs tax break). For instance, have reduce rates for users who have time-elastic data transmissions. 

4.2 Holistic perspective
- See reference cited above for an example of other metrics outside energy/carbon

4.3 Sustainable equipment production - really enjoyed reading this section
- With which other organizations should IETF partner to affect change in the lifecycle of networking devices and systems?
- What should the IETF as a community demand from HW/FW/SW manufacturers?
    + For real-time instrumentation
    + For data sheets on expected energy usages
    + APIs to access/modify/disseminate carbon-footprint-related data
    + Published embodied carbon in the manufacturing of networking equipment - i.e., product carbon footprints
    + Ramp up of Circularity programs - which might look categorically different in developed vs developing nations

-----Original Message-----
Date: Thu, 20 Oct 2022 20:53:30 -0700
From: Alexander Clemm <alex@clemm.org>
To: recipe@ietf.org
Subject: [recipe] And another new draft revision: Green Networking Metrics
Message-ID: <d90dc815-5de2-32ca-cab6-84f53fc29451@clemm.org>
Content-Type: text/plain; charset=UTF-8; format=flowed

As subject line:  FYI, we have just posted a new revision of draft-cx-green-metrics, "Green Networking Metrics", here: 
https://datatracker.ietf.org/doc/draft-cx-green-metrics/

The updates are mostly of a relatively minor nature to provide further editorial quality.

--- Alex (on behalf of coauthors)



------------------------------

End of recipe Digest, Vol 12, Issue 1
*************************************