on 1.2

The low incidence of coronary heart disease (CHD) in premenopausal women is partly ascribed to protection by endogenous estrogen production. As a consequence, we hypothesized that premenopausal women with low endogenous estrogen production or high androgen production might be at increased risk for CHD. We studied the relationship between urinary sex hormone excretions and CHD risk by means of a nested case-referent study within a cohort of premenopausal (ages 40—49 yrs) women (n = 11,284). This cohort was formed at a breast cancer screening project in 1982-1986 (The Diagnostisch Onderzoek Mammacarcinoom [DOM] Project). Baseline data included self-administered questionnaires and anthropometric measurements. At the time of screening the women were instructed to collect an overnight urine sample on day 22 of three separate cycles. These urine samples were stored at —20°C. Up to June 1991, 45 subjects were admitted to local hospitals on diagnosis of CHD (29 with myocardial infarction, and 16 with angiographically confirmed coronary disease). Referents were sampled from the cohort, matched for age and year of screening in a 1:3 ratio. In a follow-up study, menopausal state of the subjects was assessed yearly by mailed questionnaires. Urinary excretions of estrone-glucuronide, pregnanediol-glucuronide, and testosterone-glucuronide adjusted by creatinine were similar for cases and referents. Cases had no earlier menopause than referents, although cases had more anovulatory cycles. The occurrence of CHD in middle-aged women is not preceded by a low premenopausal endogenous estrogen production or high androgen production. Anovulatory cycles appear more frequently in women who develop CHD many years later, j c l in e p id e m io l 5013:275-281, 1997© 1997 Elsevier Science Inc. KEY WORDS* Sex hormones, women, coronary disease, urine, risk factor


comments
• In General, we believe that discussion on this topic has identified multiple stakeholders that have not been sufficiently consulted or involved in the development of the PAR/CSD.
• An EC Study Group should be created to allow multiple Stakeholders, across all 802 WGs, to participate in the development of a PAR/CSD. Timing conflicts need to be addressed to allow for an inclusive opportunity of the stakeholders. 802.11 5.2b continued 1. The RAC does not allocate local addresses and should not begin doing so. "A CID has the X bit (U/L bit) equal to one and consequently that places any address with the CID as its first three octets in the local address space (U/L = 1). Local addresses are not globally unique, but a network administrator is responsible for assuring that any local addresses assigned are unique within the span of use." from IEEE RAC document "Guidelines for Use Organizationally Unique Identifier (OUI) and Company ID (CID)" The scope statement should not imply a change to the current RAC policy. 802.11 on 5.5 need 1.The sentences "This project will enable protocols that automatically configure addresses from a portion of the local address space. Such protocols will allow virtual machines and IoT devices to obtain a local address without local administration." do not state a need. Delete the 2 cited sentences or reword to describe a need.
2."Organizations will be able to use a CID address block as a default address space for their protocol without conflicting with other protocols following the guideline." •Organizations are already able to use the local address space. A local administrator can allocate local addresses without a CID. A local administrator can use a CID to allocate addresses from the local address space as an alternative.
802.11 CSD coexistance Include specifically in the scope that the project will develop guidelines, techniques and strategies which may be applied to management of local address spaces, and rules to apply when the specific guidelines, techniques and strategies recommended are adopted.
• 802.15 Also, the opening premise in the "need for the project" appears based on the assumption virtual machines and IoT devices use EUI-48 addresses and ignores the far deeper EUI-64 address space used by many (now approaching one billion and growing rapidly) 15.4 based IoT devices. From explanations given in the ad-hoc discussion, it appears the intent of the project is to address ONLY locally administered EUI-48 address space. If this is the intent it should be clearly stated in the project scope.
• IEEE 802c 802.15 Need comments • The sentence "Such protocols will allow virtual machines and IoT devices to obtain a local address without local administration." is self contradictory and technically invalid: "This project will enable protocols that automatically configure addresses from a portion of the local address space" would be a method of local administration. Suggest deleting this sentence.
802.16 on 5.2b Scope of project • PAR 5.2.b. "Scope of the project" should include allocation of some address space for use by 802 protocols, not only for use by other parties. IEEE 802 protocols should not be limited to operation under a single CID.
• 5.2.b: This will allocate a portion of the address space for protocols using an IEEE Registration Authority assigned Company ID. Another portion of the local address space will be allocated for assignment by local administrators. A portion will be allocated for use by IEEE 802 protocols using a partitioned local address.

on Need
• PAR 5.5 "Need for the Project" mentions configuring addresses but nothing about how addresses can be used • 5.5: This project will enable protocols that automatically configure and use addresses from a portion of the local address space..

on 6.1b Registration activity
• If yes please explain: This will allocate a portion of the address space for protocols using an IEEE Registration Authority assigned Company ID and one or more blocks of CID space to be agreed with the Registration Authority.
Geoff Thompson on Need • I have a problem with the following text which is currently in the draft PAR: • 5.5 Need for the Project: Currently, global addresses are assigned to most IEEE 802 end stations and bridge ports. Increasing use of virtual machines and Internet of Things (IoT) devices could exhaust the global address space if global addresses are assigned. This project will enable protocols that automatically configure addresses from a portion of the local address space. Such protocols will allow virtual machines and IoT devices to obtain a local address without local administration.
• • Geoff Thompson on Need (cont) • I believe that following would be more accurate depiction of appropriate goals for the project: • 5.5 Need for the Project: Currently, globally unique addresses are assigned to most IEEE 802 end stations and bridge ports. Increasing use of virtual machines (wherein a networked (virtual) machine is instantiated as a software file or record) and Internet of Things (IoT) devices could exhaust the global address space if global addresses are assigned. This project will provide conventions and provide for protocols that will allow multiple stations or servers to automatically configure addresses from a portion of the local address space. Such protocols will allow virtual machines and IoT devices to obtain a local address without centralized local address administration.
• • (I admit that this text is more directed at the virtual machine problem that the IoT problem. I am not convinced that the IoT problem is nearly as serious and I further believe that many IoT devices (e.g those in automobiles) may well end up with fixed addresses because it is obvious that there will be only a single instance of one device per routed network. A well know MAC address for a conventional automotive alternator would be an example. It is a one per car device (yes, there COULD be exceptions but they are not relevant.)) Geoff Thompson on coexistence • 1.1.2 Coexistence • The response "A CA document is not applicable because this is not a wireless project" is, I believe incorrect. First, the 802 O&A applies equally to wired and wireless projects so the response is misleading or incorrect. Second, I do not believe that the coexistence criteria should be limited to wireless projects when coexistence is an issue with the project. Please reconsider your response.
Privacy and 802c PAR • Long lived identifiers associated with a user, such as MAC addresses, have been identified as privacy risks in 802 protocols • The potential 802c recommendations and rules for the use of the local address space would have direct implications on privacy issues and possible solutions being considered in the group