text:
Network Working Group
Category: Informational
M. Salter
E. Rescorla
Network Resonance
R. Housley
Vigil Security
Suite B Profile for Transport Layer Security (TLS)
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
The United States government has published guidelines for "NSA Suite B Cryptography", which defines cryptographic algorithm policy for national security applications. This document defines a profile of Transport Layer Security (TLS) version 1.2 that is fully conformant with Suite B. This document also defines a transitional profile for use with TLS version 1.0 and TLS version 1.1 which employs Suite B algorithms to the greatest extent possible.
2. Conventions Used in This Document ...............................3
3. Suite B Requirements ............................................3
4. Suite B Compliance and Interoperability Requirements ............4
4.1. Security Levels ............................................7
4.2. Acceptable Curves ..........................................8
4.3. Certificates ...............................................8
4.4. signature_algorithms Extension .............................9
4.5. CertificateRequest Message .................................9
4.6. CertificateVerify Message .................................10
4.7. ServerKeyExchange Message Signature .......................10
The United States government has posted the Fact Sheet on National Security Agency (NSA) Suite B Cryptography [NSA], and at the time of writing, it states:
To complement the existing policy for the use of the Advanced Encryption Standard (AES) to protect national security systems and information as specified in The National Policy on the use of the Advanced Encryption Standard (AES) to Protect National Security Systems and National Security Information (CNSSP-15), the National Security Agency (NSA) announced Suite B Cryptography at the 2005 RSA Conference. In addition to the AES, Suite B includes cryptographic algorithms for hashing, digital signatures, and key exchange.
Suite B only specifies the cryptographic algorithms to be used. Many other factors need to be addressed in determining whether a particular device implementing a particular set of cryptographic algorithms should be used to satisfy a particular requirement.
Among those factors are "requirements for interoperability both domestically and internationally".
This document does not define any new cipher suites; instead, it defines two profiles:
A Suite B compliant profile for use with TLS version 1.2 [RFC5246] and the cipher suites defined in [RFC5289]. This profile uses only Suite B algorithms.
A transitional profile for use with TLS version 1.0 [RFC2246] or TLS version 1.1 [RFC4346] and the cipher suites defined in [RFC4492]. This profile uses the Suite B cryptographic algorithms to the greatest extent possible and provides backward compatibility. While the transitional profile is not Suite B compliant, it provides a transition path towards the Suite B compliant profile.
2. Conventions Used in This Document
3. Suite B Requirements
The Fact Sheet on Suite B Cryptography requires that key establishment and authentication algorithms be based on Elliptic Curve Cryptography, and that the encryption algorithm be AES [AES]. Suite B defines two security levels, of 128 and 192 bits.
In particular, Suite B includes:
Encryption:         Advanced Encryption Standard (AES) [AES] --
FIPS 197 (with key sizes of 128 and 256 bits)
Digital Signature:  Elliptic Curve Digital Signature Algorithm
(ECDSA) [DSS] - FIPS 186-2 (using the
curves with 256- and 384-bit prime moduli)
Key Exchange:       Elliptic Curve Diffie-Hellman (ECDH) - NIST
Special Publication 800-56A [PWKE] (using the
The 128-bit security level corresponds to an elliptic curve size of 256 bits and AES-128; it also makes use of SHA-256 [SHS]. The 192- bit security level corresponds to an elliptic curve size of 384 bits and AES-256; it also makes use of SHA-384 [SHS].
Note: Some people refer to the two security levels based on the AES key size that is employed instead of the overall security provided by the combination of Suite B algorithms. At the 128-bit security level, an AES key size of 128 bits is used, which does not lead to any confusion. However, at the 192-bit security level, an AES key size of 256 bits is used, which sometimes leads to an expectation of more security than is offered by the combination of Suite B algorithms.
To accommodate backward compatibility, a Suite B compliant client or server can be configured to accept a cipher suite that is not part of Suite B. However, whenever a Suite B compliant client and a Suite B compliant server establish a TLS version 1.2 session, only Suite B algorithms are employed.
4. Suite B Compliance and Interoperability Requirements
TLS version 1.1 [RFC4346] and earlier do not support Galois Counter Mode (GCM) cipher suites [RFC5289]. However, TLS version 1.2 [RFC5246] and later do support GCM. For Suite B TLS compliance, GCM cipher suites are REQUIRED to be used whenever both the client and the server support the necessary cipher suites. Also, for Suite B TLS compliance, Cipher Block Chaining (CBC) cipher suites are employed when GCM cipher suites cannot be employed.
For a client to implement the Suite B compliant profile, it MUST implement TLS version 1.2 or later, and the following cipher suite rules apply:
A Suite B compliant TLS version 1.2 or later client MUST offer at least two cipher suites for each supported security level. For the 128-bit security level, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 MUST be offered in this order in the ClientHello message. For the 192-bit security level, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 and TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 MUST be offered in this order in the ClientHello message. One of these cipher suites MUST be the first (most preferred) cipher suite in the ClientHello message.
A Suite B compliant TLS version 1.2 or later client that offers backward compatibility with TLS version 1.1 or earlier servers MAY offer an additional cipher suite for each supported security level. If these cipher suites are offered, they MUST appear after the ones discussed above. For the 128-bit security level, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA MAY be offered in the ClientHello message. For the 192-bit security level, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA MAY be offered in the ClientHello message.
A Suite B compliant TLS version 1.2 or later client that offers interoperability with non-Suite B compliant servers MAY offer additional cipher suites. If any additional cipher suites are offered, they MUST appear after the ones discussed above in the ClientHello message.
For a client to implement the Suite B transitional profile, it MUST implement TLS version 1.1 or earlier and the following cipher suite rules apply:
A Suite B transitional TLS version 1.1 or earlier client MUST offer the cipher suite for the 128-bit security level, the cipher suite for the 192-bit security level, or both. For the 128-bit security level, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA MUST be offered in the ClientHello message. For the 192-bit security level, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA MUST be offered in the ClientHello message. One of these cipher suites MUST be the first (most preferred) cipher suite in the ClientHello message.
A Suite B transitional TLS version 1.1 or earlier client that offers interoperability with non-Suite B compliant servers MAY offer additional cipher suites. If any additional cipher suites are offered, they MUST appear after the ones discussed above in the ClientHello message.
A Suite B compliant TLS server MUST be configured to support the 128- bit security level, the 192-bit security level, or both security levels. The cipher suite rules for each of these security levels is described below. If a Suite B compliant TLS server is configured to support both security levels, then the configuration MUST prefer one security level over the other. In practice, this means that the cipher suite rules associated with the cipher suites listed in Section 4.1 for the preferred security level are processed before the cipher suite rules for the less preferred security level.
For a server to implement the Suite B conformant profile at the 128- bit security level, the following cipher suite rules apply:
A Suite B compliant TLS version 1.2 or later server MUST accept the TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 cipher suite if it is offered.
If the preceding cipher suite is not offered, then a Suite B compliant TLS version 1.2 or later server MUST accept the TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 cipher suite if it is offered.
If neither of the preceding two cipher suites is offered, then a Suite B compliant TLS version 1.2 or later server that offers backward compatibility with TLS version 1.1 or earlier clients MAY accept the TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA cipher suite if it is offered.
If the server is not offered any of the preceding three cipher suites and interoperability with clients that are not compliant or interoperable with Suite B is desired, then the server MAY accept another offered cipher suite that is considered acceptable by the server administrator.
For a server to implement the Suite B transitional profile at the 128-bit security level, the following cipher suite rules apply:
A Suite B transitional TLS version 1.1 or earlier server MUST accept the TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA cipher suite if it is offered.
If the server is not offered the preceding cipher suite and interoperability with clients that are not Suite B transitional is desired, then the server MAY accept another offered cipher suite that is considered acceptable by the server administrator.
Note that these rules explicitly permit the use of CBC cipher suites in TLS version 1.2 connections in order to permit operation between Suite B compliant and non-Suite B compliant implementations. For instance, a Suite B compliant TLS version 1.2 client might offer TLS version 1.2 with both GCM and CBC cipher suites when communicating with a non-Suite B TLS version 1.2 server, which then selected the CBC cipher suites. This connection would nevertheless meet the requirements of this specification. However, any two Suite B compliant implementations will negotiate a GCM cipher suite when doing TLS version 1.2.
4.1. Security Levels
As described in Section 1, Suite B specifies two security levels: 128-bit and 192-bit. The following table lists the cipher suites for each security level. Within each security level, the cipher suites are listed in their preferred order for selection by a TLS version 1.2 implementation.
+-----------------------------------------+----------------+
| Cipher Suite                            | Security Level |
| TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | 128            |
| TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 | 128            |
| TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA    | 128            |
4.2. Acceptable Curves
RFC 4492 defines a variety of elliptic curves. For cipher suites defined in this specification, only secp256r1(23) or secp384r1(24) may be used. These are the same curves that appear in FIPS 186-2 [DSS] as P-256 and P-384, respectively. For cipher suites at the 128-bit security level, secp256r1 MUST be used. For cipher suites at the 192-bit security level, secp384r1 MUST be used. RFC 4492 requires that the uncompressed(0) form be supported. The ansiX962_compressed_prime(1) point formats MAY also be supported.
Clients desiring to negotiate only a Suite B compliant connection MUST generate a "Supported Elliptic Curves Extension" containing only the allowed curves. These curves MUST match the cipher suite security levels being offered. Clients that are willing to do both Suite B compliant and non-Suite B compliant connections MAY omit the extension or send the extension but offer other curves as well as the appropriate Suite B ones.
Servers desiring to negotiate a Suite B compliant connection SHOULD check for the presence of the extension, but MUST NOT negotiate inappropriate curves even if they are offered by the client. This allows a client that is willing to do either Suite B compliant or non-Suite B compliant modes to interoperate with a server that will only do Suite B compliant modes. If the client does not advertise an acceptable curve, the server MUST generate a fatal "handshake_failure" alert and terminate the connection. Clients MUST check the chosen curve to make sure it is acceptable.
4.3. Certificates
Server and client certificates used to establish a Suite B compliant connection MUST be signed with ECDSA. Digital signatures MUST be calculated using either the P-256 curve along with the SHA-256 hash algorithm or calculated using the P-384 curve along with the SHA-384 hash algorithm. For certificates used at the 128-bit security level, the subject public key MUST use the P-256 curve and be signed with either the P-384 curve or the P-256 curve. For certificates used at the 192-bit security level, the subject public key MUST use the P-384 curve and be signed with the P-384 curve.
In TLS version 1.0 and TLS version 1.1, the key exchange algorithm used in the TLS_ECDHE_ECDSA-collection of cipher suites requires the server's certificate to be signed with a particular signature scheme. TLS version 1.2 offers more flexibility. This specification does not impose any additional restrictions on the server certificate signature or the signature schemes used elsewhere in the certification path. (Often such restrictions will be useful, and it is expected that this will be taken into account in practices of certification authorities. However, such restrictions are not strictly required, even if it is beyond the capabilities of a client to completely validate a given certification path, the client may be able to validate the server's certificate by relying on a trusted certification authority whose certificate appears as one of the intermediate certificates in the certification path.)
Likewise, this specification does not impose restrictions on signature schemes used in the certification path for the client's certificate when mutual authentication is employed.
4.4. signature_algorithms Extension
The signature_algorithms extension is defined in Section 7.4.1.4.1 of TLS version 1.2 [RFC5246]. A Suite B compliant TLS version 1.2 or later client MUST include the signature_algorithms extension. For the 128-bit security level, SHA-256 with ECDSA MUST be offered in the signature_algorithms extension. For the 192-bit security level, SHA- 384 with ECDSA MUST be offered in the signature_algorithms extension. Other offerings MAY be included to indicate the signature algorithms that are acceptable in cipher suites that are offered for interoperability with servers that are not compliant with Suite B and to indicate the signature algorithms that are acceptable for certification path validation.
4.5. CertificateRequest Message
A Suite B compliant TLS version 1.2 or later server MUST include SHA- 256 with ECDSA and/or SHA-384 with ECDSA in the supported_signature_algorithms field of the CertificateRequest message. For the 128-bit security level, SHA-256 with ECDSA MUST appear in the supported_signature_algorithms field. For the 192-bit security level, SHA-384 with ECDSA MUST appear in the supported_signature_algorithms field.
4.6. CertificateVerify Message
A Suite B compliant TLS version 1.2 or later client MUST use SHA-256 with ECDSA or SHA-384 with ECDSA for the signature in the CertificateVerify message. For the 128-bit security level, SHA-256 with ECDSA MUST be used. For the 192-bit security level, SHA-384 with ECDSA MUST be used.
4.7. ServerKeyExchange Message Signature
In the TLS_ECDHE_ECDSA-collection of cipher suites, the server sends its ephemeral ECDH public key and a specification of the corresponding curve in the ServerKeyExchange message. These parameters MUST be signed with ECDSA using the private key corresponding to the public key in the server's certificate.
A TLS version 1.1 or earlier server MUST sign the ServerKeyExchange message using SHA-1 with ECDSA.
A Suite B compliant TLS version 1.2 or later server MUST sign the ServerKeyExchange message using either SHA-256 with ECDSA or SHA-384 with ECDSA. For the 128-bit security level, SHA-256 with ECDSA MUST be used. For the 192-bit security level, SHA-384 with ECDSA MUST be used.
Most of the security considerations for this document are described in "The Transport Layer Security (TLS) Protocol Version 1.2" [RFC5246], "Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS)" [RFC4492], "AES Galois Counter Mode (GCM) Cipher Suites for TLS" [RFC5288], and "TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)" [RFC5289]. Readers should consult those documents.
In order to meet the goal of a consistent security level for the entire cipher suite, in Suite B mode TLS implementations MUST ONLY use the curves defined in Section 4.2. Otherwise, it is possible to have a set of symmetric algorithms with much weaker or stronger security properties than the asymmetric (ECC) algorithms.
Thanks to Pasi Eronen, Steve Hanna, and Paul Hoffman for their review, comments, and insightful suggestions.
This work was supported by the US Department of Defense.
[RFC4492]  Blake-Wilson, S., Bolyard, N., Gupta, V., Hawk, C., and B.
Moeller, "Elliptic Curve Cryptography (ECC) Cipher Suites
for Transport Layer Security (TLS)", RFC 4492, May 2006.
(TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5289]  Rescorla, E., "TLS Elliptic Curve Cipher Suites with SHA-
256/384 and AES Galois Counter Mode (GCM)", RFC 5289,
[AES]      National Institute of Standards and Technology,
"Specification for the Advanced Encryption Standard
(AES)", FIPS 197, November 2001.
[DSS]      National Institute of Standards and Technology, "Digital
Signature Standard", FIPS 186-2, January 2000.
[PWKE]     National Institute of Standards and Technology,
"Recommendation for Pair-Wise Key Establishment Schemes
Using Discrete Logarithm Cryptography (Revised)", NIST
Special Publication 800-56A, March 2007.
[SHS]      National Institute of Standards and Technology, "Secure
Hash Standard", FIPS 180-2, August 2002.
[RFC2246]  Dierks, T. and C. Allen, "The TLS Protocol Version 1.0",
(TLS) Protocol Version 1.1", RFC 4346, April 2006.
[RFC5288]  Salowey, J., Choudhury, A., and D. McGrew, "AES Galois
Counter Mode (GCM) Cipher Suites for TLS", RFC 5288,
[NSA]      National Security Agency, "Fact Sheet NSA Suite B
Cryptography",
<http://www.nsa.gov/ia/Industry/crypto_suite_b.cfm>.
Margaret Salter
9800 Savage Rd.
Fort Meade  20755-6709
EMail: msalter@restarea.ncsc.mil
Eric Rescorla
ekr@rtfm.com
Russ Housley
918 Spring Knoll Drive
Herndon  21070
housley@vigilsec.com
Obsoleted by


text:
Tetrix serrifemoroides är en insektsart som beskrevs av Zheng, Z. och G. Jiang 2002. Tetrix serrifemoroides ingår i släktet Tetrix och familjen torngräshoppor. Inga underarter finns listade i Catalogue of Life.

Källor

Torngräshoppor
serrifemoroides

redpajama_set_name: RedPajamaWikipedia


text:
Q: jvisualvm do not monitor local JBoss application on Windows 7 / Windows 2008 When I start JVisualVM on Windows 7 or Windows 2008 there is no way to find JBoss instances running on the same machine

A: Run the JBoss command line using the "Run as administrator" feature of Windows 7 or Windows 2008.
This probably could solve also problems in other profilers for the Java VM when you run them in the same operating systems.

redpajama_set_name: RedPajamaStackExchange


On July 24, 2018 from 3:00-4:00 Eastern, we will hear from two fantastic authors and thinkers in EE as part of NAAEE's monthly webinar series. Dr. Marc Stern (link is external)(Virginia Tech) and Dr. Bill Scott (link is external) (University of Bath) have both recently published books that are both inspirational and practical. We'll learn about the new thinking and ideas they're exploring for how we can use social theories to shape our work, understand the challenges and apply new strategies for working toward sustainability, and more.
It is now clear that human activity has influenced how the biosphere supports life on Earth, and given rise to a set of connected environmental and social problems. In response to the challenge that these problems present, a series of international conferences and summits led to discussions of sustainable development and the core dilemma of our time: How can we all live well, now and in the future, without compromising the ability of the planet to enable us all to live well.


What it is: A skin-improving, 24-hour, breathable, matte liquid foundation with Mineral Lock technology to blend pigments with lipids and lock-in full coverage.
- Bamboo Extract: Provides a blurring, soft-focus effect.
- Papaya Enzymes: Gently even the look of skin's texture, both immediately and over time.
- Mineral Lock Long Wear: Adheres to skin for long-lasting wear.
What Else You Need to Know: This high-performance formula blurs pores and imperfections while evening the look of skin's texture. This self-setting foundation is lightweight, oil-free, transfer-resistant, and photo-friendly. It provides skin-improving long-wear without unnatural cakiness.
-For best results, apply with the Luxe Performance Brush, which is specially developed for the creamy texture of BAREPRO Liquid Foundation.
-Pump foundation onto back of hand. Start with one pump, or add more to build more coverage.
-Pick up foundation with brush.
-Starting in center of face and working outward, blend onto skin using short downward strokes.
-Blend well into jawline and hairline to ensure an even appearance.


text:
MHI Vestas launched the world's most powerful wind turbine
The launch of the V164-9.5 MW turbine showcases the proven V164 platform with increased energy output from minimal design changes. (Photo: MHI Vestas)
MHI Vestas launched the V164-9.5 MW wind turbine, signaling the company's drive to lower the cost of energy for offshore wind.
The announcement came as the offshore wind industry met in London at Offshore Wind Energy 2017 to reaffirm its commitment to reduce the cost of energy, to urge policy-makers to set clear offshore wind volume targets, and to define a clear path forward as the sector eyes global expansion. The V164 platform's massive 80-meter blades are already capturing wind energy off the coast of the UK, giving the company volumes of real-time data and valuable experience that is already paying dividends.
Jens Tommerup, CEO of MHI Vestas, said: "As a leader in the offshore wind industry, we are committed to lowering the cost of energy through innovative turbine technology. The launch of our V164-9.5 MW turbine is a testament to that leadership and to the ingenuity of our engineers and technicians."
Torben Hvid Larsen, Chief Technology Officer at MHI Vestas, commented: "I'm very proud of our team for their hard work in launching our next generation turbine, the V164-9.5 MW. With only minimal design changes, including a redesigned gearbox and cooling system upgrades, this turbine continues the legacy of the proven V164 platform and is available now to all MHI Vestas customers."
MHI Vestas / SIlke Funke
ZF's first wind turbine gearboxes equipped with a Schaeffler cloud connection go into operation
ZF Friedrichshafen and Schaeffler are collaborating to develop new solutions for predicting the operating life of wind turbine gearbox components based on the actual loads that occur during operation. Since September, the first wind turbine gearboxes equipped with sensors and condition monitoring systems have been supplying operating data to a cloud-to-cloud solution to enable this to happen.
German offshore wind contracts and new defence activities emphasize the significance of Den Helder Airport
Den Helder Airport (DHA) will facilitate helicopter flights for the maintenance of the Deutsche Bucht offshore wind farm for Vestas in the coming years. At the same time, offshore wind farm constructor Van Oord has finalized a call-off contract for the same German wind farm.
Home > News > MHI Vestas launched the world's most powerful wind turbine

redpajama_set_name: RedPajamaCommonCrawl


text:
Arts and Entertainment >
Entertainment Biographies >
Lana Turner Biography
(Julia Jean Mildred Frances Turner)
Born: 2/8/1921
Birthplace: Wallace, Idaho
The legendary Turner was "discovered" while sipping soda at Schwab's Drugstore on Sunset Boulevard and, after numerous bit parts, was transformed into the film goddess known as "The Sweater Girl." A star role in Dancing Co-Ed (1939) was followed by a long string of credits, including Weekend at the Waldorf (1945), The Postman Always Rings Twice (1946), Peyton Place (1957, which gained her an Oscar nomination), and Bittersweet Love (1976). Turner appeared on TV's Falcon Crest (1982–83) late in her career.
Died: 6/29/1995
Kathleen Turner T Tina Turner
Kathleen Turner Biography T Tina Turner Biography
Tina Turner Biography


For City water and sewer customers that sign up, the City has offered automatic bank account deductions to pay utility bills for years — and it works great for many residents.
But we also knew that it was important to offer online payment of utility bills with credit cards.
As simple as that sounds, it turned out to be a rather complicated service to add as it required a seamless connection with our financial billing technology — and getting software to talk to each other and share the right information was a bigger challenge than we anticipated.
At long last, we started offering online payment of utility bills with credit cards in February 2018.
This week the Finance Department reported that since February's introduction of the new online payment option, we've had 700 customer transactions — and their payments represent about 7% of our total utility receipts.
In this era of ubiquitous online shopping, we're glad that our credit card payment service is gaining traction too.
Here's a link to the register for online payment of City utilities.


text:
"calendar 357" Nominations 114 (2015-2016)
Sort by Sort by: RelevancyLatest Action - Newest to OldestLatest Action - Oldest to NewestDate Received - Newest to OldestDate Received - Oldest to NewestNumber - AscendingNumber - Descending
1. PN575 — 114th Congress (2015-2016) — Brian R. Martinotti — The Judiciary Brian R. Martinotti, of New Jersey, to be United States District Judge for the District of New Jersey, vice Stanley R. Chesler, retiring. Date Received from President: 06/11/2015 Committee: Judiciary Latest Action: 07/06/2016 - Confirmed by the Senate by Yea-Nay Vote. 92 - 5. Record Vote Number: 118. (All Actions)
1. PN575 — 114th Congress (2015-2016) — Brian R. Martinotti — The Judiciary Brian R. Martinotti, of New Jersey, to be United States District Judge for the District of New Jersey, vice Stanley R. Chesler, retiring. Date Received: 06/11/2015 Referred: Judiciary Latest Action: 07/06/2016 - Confirmed by the Senate by Yea-Nay Vote. 92 - 5. Record Vote Number: 118. (All Actions)
Nominations [1]
Civilian [1]
Status of Nomination
Referred to committee [1]
Calendars [1]
Considered by Senate [1]
Confirmed by Senate [1]
Nominees with US State or Territory Indicated
New Jersey [1]


text:
Biosafety Information Centre
Biosafety Science
Genomics/Genetics
General Biosafety Issues
Emerging Trends/Techniques
Research Gaps
Horizontal Gene Transfer
Agriculture / Organisms
Staple Food Crops
Other Food Crops
Industrial Crops
Animals/Fish
Insects/Microorganisms
Horticulture/trees
Traits in Agriculture
Pest Resistance
Enhanced Nutrition
Biomedical Applications
Pharmaceutical Crops
Cloning & Stem Cell Research
Biological Weapons/Biodefence
GE Pharmaceuticals
Assessment & Impacts
Trends in Industry
Global Agreements and Fora
International Standard Setting
Other UN Agencies
Key Regulatory Issues
Contained Use
Post-Release Monitoring
Traceability & Labelling
Liability & Redress
Sustainable Systems
Indigenous Peoples' Perspective
Local Community Perspective
Independent Science
Ecological Agriculture & Food Security
Energy linkages
Biosafety Assessment Tool (BAT)
Biosafety Information Service —
NGO/CSO
Biosafety Briefings
Biotechnology & Biosafety Series
« Cartagena Protocol Online Forum on Public Awareness, Education and Participation
US Groups Call On Florida Governor To Stop Release GE Mosquitoes »
US Groups Call On Florida Governor To Stop Release GE Mosquitoes
THIRD WORLD NETWORK BIOSAFETY INFORMATION SERVICE
Groups Call On Governor To Protect Floridians And Block Release Of Unregulated, Risky GE Mosquitoes
Food & Water Watch, Friends of the Earth, Florida Chapter of the Sierra Club, Florida Keys Environme
Press Release, 19 April 2012
http://www.foodandwaterwatch.org/pressreleases/groups-call-on-governor-to-protect-floridians-and-block-release-of-unregulated-risky-ge-mosquitoes/
Washington, D.C.: Today consumer and environmental groups sent a letter to Florida Governor Rick Scott to encourage him to prevent the experimental release of British biotechnology company Oxitec's genetically engineered
(GE) mosquitoes in the Florida Keys. The letter, also sent to Florida Commissioner of Agriculture Adam Putnam and the entire Florida congressional delegation, was signed by Food & Water Watch, Friends of the Earth, the Florida Chapter of the Sierra Club, the Florida Keys Environmental Coalition and GMO Free Florida.
"South Florida's environmentally sensitive landscape already endures many exotic and invasive species," said Food & Water Watch Executive Director Wenonah Hauter. "The proposed open-air release of millions of unregulated, experimental insects into the Florida Keys opens a Pandora's box that cannot easily be sealed."
The experiment raises serious concerns around the impact releasing genetically engineered mosquitoes could have on public health and the environment. This is the first genetically engineered insect to be introduced in the United States with the intent to wipe out a wild population in the name of disease control.
"The risks genetically engineered mosquitoes pose to the local ecology and to human health have yet to be properly studied by independent experts, nor has this technology been proven to even work in limiting the spread of disease," said Eric Hoffman, food and technology policy campaigner for Friends of the Earth. "Right now, the residents are left having to take Oxitec's word that its technology is safe. Citizens in the Keys deserve better science and deserve to be protected from this unproven and risky technology by their elected officials."
Oxitec claims the purpose of the experiment is to determine if the Aedes aegypti mosquito population will be reduced, as genetically engineered males mate with wild females, passing on a genetic defect that kills their offspring before they reach adulthood. The company claims this would theoretically reduce the mosquito population and the prevalence of dengue fever despite the fact that the Florida Keys had no reported cases of dengue fever in 2011.
"Communities near the proposed test areas should not become Oxitec's laboratory for the field release of genetically engineered mosquitoes,"
said Marian Ryan, Sierra Club Florida's Conservation Chair. "Since the federal government is not regulating these insects, Florida's government should step up to protect Floridians and prohibit the release of these unregulated and uncontrolled mosquitoes in South Florida."
Despite the grave and growing public concerns that have been raised about the mosquitoes, there is no indication that the U.S. Food and Drug Administration or any other federal or state agency has evaluated the safety of the company's release. Nor does any agency seem to know who is actively responsible for considering it. Regardless of this lack of clarity about which federal agency will have oversight of Oxitec's transgenic mosquitoes, the Florida Keys Mosquito Control District is still interested in moving ahead with a field trial in 2012.
On April 3, 2012, the Key West City Commission voted 5-2 to pass a resolution objecting to the release of Oxitec's mosquitoes. "We urge Governor Rick Scott to stand with Key West residents and our elected officials and oppose the release of these genetically engineered mosquitoes," said Meagan Morrison, board member of the Florida Keys Environmental Coalition.
The letter to Governor Scott can be viewed here:
http://documents.foodandwaterwatch.org/doc/GovernorScottLetter.pdf (or Item 2)
Food & Water Watch works to ensure the food, water and fish we consume is safe, accessible and sustainable. So we can all enjoy and trust in what we eat and drink, we help people take charge of where their food comes from, keep clean, affordable, public tap water flowing freely to our homes, protect the environmental quality of oceans, force government to do its job protecting citizens, and educate about the importance of keeping shared resources under public control.
Office of Governor Rick Scott
400 S. Monroe St.
Tallahassee, FL 32399-0001
Dear Governor Scott,
The undersigned consumer and environmental groups urge you to prevent the experimental release of British biotechnology company Oxitec's genetically engineered mosquitoes in the Florida Keys.
This experiment would be a first in the United States. The supposed purpose of this experiment is to determine if the Aedes aegypti mosquito population will be reduced, as genetically engineered males mate with wild females, passing on a genetic defect that kills their offspring before they reach adulthood. The company claims this would theoretically reduce the mosquito population and the prevalence of dengue fever.
While mosquitoes that breed themselves out of existence may seem like a new option for dealing with the threat of disease and an irritating daily fact of life for Floridians, it has yet to be proven that this engineered mosquito is safe for people or the environment – or that it can effectively reduce the spread of dengue fever.
This would be the first genetically engineered insect to be introduced in the United States with the intent to wipe out a wild population in the name of disease control. Oxitec has already released millions of GE insects into the wild in South America and the Caribbean without studying potential environmental or health risks. Now Floridians are set to be Oxitec's next guinea pigs, despite the fact that the Florida Keys had no reported cases of dengue fever in 2011.
The release of the company's transgenic mosquitoes by the Florida Keys Mosquito Control District was planned to occur as early as spring 2012.
According to the Associated Press, during a two-month trial, between 5,000 and 10,000 of these transgenic mosquitoes would be released into an undisclosed 36-square-acre block near the Key West Cemetery.
The experiment raises serious concerns around the impact releasing genetically engineered mosquitoes could have on public health and the environment. For example, biting female mosquitoes could inject an engineered protein into humans along with other proteins from the mosquitos' salivary gland. Oxitec has yet to conduct or publish any study showing that this protein is not expressed in the salivary gland and therefore cannot be passed on to humans. This is a real concern, even though officials only plan to release non-biting males, as genetically engineered females can also be accidentally released.
The company expects each batch to contain less than one percent females.
This is because mosquito pupae are tiny and sorting them for a large-scale release leaves plenty of room for error. Additionally, 3.5 percent of the insects in an Oxitec lab test survived to adulthood despite presumably carrying the lethal gene. These two facts combined mean that there will be a significant number of genetically engineered female mosquitoes in the environment that bite humans and spread disease. Since Aedes aegypti females bite many people in one feeding, it is able to spread disease even at low population levels. This means Oxitec's technology might not even work in limiting the spread of disease while still exposing Keys residents to possible risks.
Despite the grave and growing public concerns that have been raised about the genetically engineered mosquitoes, there is no indication that the U.S. Food & Drug Administration or any other federal or state agency has evaluated the safety of the company's planned release. Nor has there been an independent analysis to examine the public health or environmental impacts of this release. While it does appear Oxitec has a pending application, no agency seems to know who is actively responsible for considering it. Recent reports claim that despite a lack of clarity on which federal agency will have oversight over Oxitec's transgenic mosquitoes, the Florida Keys Mosquito Control District is still interested in moving ahead with their field trial in 2012.
Communities near the proposed test areas should not become Oxitec's laboratory for the field release of genetically engineered mosquitoes.
Since the federal government is not actively regulating these insects, Florida's government should step up to protect Floridians and prohibit the release of these unregulated and uncontrolled mosquitoes in South Florida.
On April 3, 2012, the Key West City Commission voted 5 to 2 to pass a resolution objecting to the release of Oxitec's genetically engineered mosquitoes. Please stand with Key West residents and their elected officials and oppose the release of these genetically engineered mosquitoes.
If you have questions or need more information, please contact Meagan Morrison at morrisonmeagan@yahoo.com or at (305) 879-3042.
Florida Keys Environmental Coalition
GMO Free Florida
Sierra Club Florida
Florida Commissioner of Agriculture Adam Putnam Florida congressional delegation
131 Jalan Macalister,
10400 Penang,
Email: twnet@po.jaring.my
Websites: www.biosafety-info.net, www.twnside.org.sg, www.twnshop.com To subscribe to other TWN information services, go to: www.twnnews.net
May 24th, 2012 | Category: Insects/Microorganisms
« US Groups Call On Florida Governor To Stop Release GE Mosquitoes
Hazardous Harvest: Genetically Modified Crops in South Africa: 2008-2012 »
May 24th, 2012 | Category: Agriculture / Organisms
Why Genome Edited Organisms are not Excluded from the Cartagena Protocol on Biosafety
US rDNA Committee Disbanded, Exacerbating Poor Oversight of GE Research
Risk Assessment Challenges of Synthetic Gene Drive Organisms
Peru extends GMO moratorium, Mexico phases out glyphosate and GM maize in food, disallows GM maize releases
How Corporations Forced GE Dicamba-Tolerant Crops onto US Farmers
Agroecological Principles to Guide Transition Pathways Towards Food Security
New Democratic Governance Imperatives to Enhance Agricultural Biodiversity
A Feminist Ethics of Care Framework for Risk Assessment of GM Crops
Archives Select Month January 2021 December 2020 November 2020 October 2020 September 2020 August 2020 July 2020 June 2020 May 2020 April 2020 March 2020 February 2020 January 2020 December 2019 November 2019 October 2019 September 2019 August 2019 July 2019 June 2019 May 2019 April 2019 March 2019 February 2019 January 2019 December 2018 November 2018 October 2018 September 2018 August 2018 July 2018 June 2018 May 2018 April 2018 March 2018 February 2018 January 2018 December 2017 November 2017 October 2017 September 2017 August 2017 July 2017 June 2017 May 2017 April 2017 March 2017 February 2017 January 2017 December 2016 November 2016 October 2016 September 2016 August 2016 July 2016 June 2016 May 2016 April 2016 March 2016 February 2016 January 2016 December 2015 November 2015 October 2015 September 2015 August 2015 July 2015 June 2015 May 2015 April 2015 March 2015 February 2015 January 2015 December 2014 November 2014 October 2014 September 2014 August 2014 July 2014 June 2014 May 2014 April 2014 March 2014 February 2014 January 2014 December 2013 November 2013 October 2013 September 2013 August 2013 July 2013 June 2013 May 2013 April 2013 March 2013 February 2013 January 2013 December 2012 November 2012 October 2012 September 2012 August 2012 July 2012 June 2012 May 2012 April 2012 March 2012 February 2012 January 2012 December 2011 November 2011 October 2011 September 2011 August 2011 July 2011 June 2011 May 2011 April 2011 March 2011 February 2011 January 2011 December 2010 November 2010 October 2010 September 2010 August 2010 July 2010 June 2010 May 2010 April 2010 March 2010 February 2010 January 2010 December 2009 November 2009 October 2009 September 2009 August 2009 July 2009 June 2009 May 2009 April 2009 March 2009 February 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008 July 2008 June 2008 May 2008 April 2008 March 2008 February 2008 January 2008 December 2007 November 2007 October 2007 September 2007 August 2007 July 2007 June 2007 May 2007 April 2007 March 2007 February 2007 January 2007 December 2006 November 2006 October 2006 September 2006 August 2006 July 2006 June 2006 May 2006 April 2006 March 2006 February 2006 January 2006 December 2005 November 2005 October 2005 September 2005 August 2005 July 2005 June 2005 May 2005 April 2005 March 2005 February 2005 January 2005 December 2004 November 2004 October 2004 September 2004 August 2004 July 2004 June 2004 May 2004 April 2004 March 2004 February 2004 January 2004 December 2003 November 2003 October 2003 September 2003 August 2003 July 2003 June 2003 May 2003 April 2003 February 2003 November 2002 October 2002 September 2002 August 2002 July 2002 June 2002 April 2002 January 2002 September 2001 June 2001 May 2001 April 2001 March 2001 February 2001 January 2001 December 2000 November 2000 October 2000 0
All our content may be republished or reused for free, except where otherwise noted.
articles post


2 SOLID ORANGE FOOD CHOICES Carbohydrates, Fruit and Every meal and snack should contain carbohydrates. Approximately one half of the food on your plate should consist of carbohydrates. Two thirds of your plate should consist of carbohydrates and vegetables. Immediately after training or playing, eat a high carbohydrate snack that is easy to digest. This will ensure that your energy stores are rapidly replaced. Drink an energy drink during training/playing to maintain energy levels. Remember that many fruits and vegetables are good sources of carbohydrate. Beans and legumes such as black beans and split peas are excellent protein sources while providing a good source of carbohydrate. Solid Orange Carbohydrates: choices for everyday diet. These foods supply the body with a longlasting, consistent source of energy. Whole Wheat- Pasta Rice Bread Pita Tortillas English muffins Bagels Unsweetened cereals Cucumbers Broccoli Spinach / collard greens Mushrooms Romaine lettuce Tomatoes Special Carbohydrates Beans/Peas Dried beans and peas Black beans Kidney beans Garbanzo beans (chickpeas) Lentils Fruit Apples Bananas Grapes Nectarines / peaches Oranges / grapefruit Peaches Plums Starchy Squash and zucchini Eggplant Corn Carrots Green beans and peas Potatoes with skin Typically, high glycemic carbohydrates (i.e. those that are absorbed into the blood very rapidly) should be avoided. This is because they do not provide lasting energy. They should especially be avoided right before activity / training / match since they may cause a rapid depletion in blood sugar levels due to the response of insulin. However, in situations where it is essential to quickly increase blood sugar levels for the purpose of re-stocking muscle energy stores, these carbohydrate sources can be particularly useful. As soon after training / playing as possible, and certainly within 30 minutes, consumption of these foods may help recovery by restoring used energy levels.
5 Hydration All athletes, especially those training/playing during the summer months need to pay special attention to remaining hydrated. Dehydration negatively affects athletic performance, but worse, during hot and humid conditions, it can be life threatening. Athletes need to drink water consistently throughout the day. Lost weight from a competition or practice should be replaced with water and sports drinks. Athletes should take the time during breaks in play to sip on water or a sports drink. The color of an athlete s urine is indicative of their hydration level it should be colorless. If an athlete becomes thirsty, they are already dehydrated to the level that cannot be overcome during that particular practice / match.
Fueling the Athlete. Questions? Food Guide Pyramid. What is the best way to prepare for competition? How do you maximize results naturally?
Food Calories List. The food calories list is broken down into sections based on the 5 basic food groups of a balanced diet.
Getting Started. So, how much weight is the appropriate amount?


Near Kudlu Gate, Hosur Road, Bangalore.
The main aim of this special session is to introduce state-of-the-art and advanced techniques for developing software systems dealing with the machine and deep learning. The objective of this special session is to resolve the difficult task for effort estimation and reusability prediction.
The several techniques proposed by the different authors but required more intelligent techniques to predict the reusability estimation from the software code. Predicting the reusability metrics is one of the challenging tasks in software engineering domain.
According to recent studies, soft computing has become an important issue in the development of the software engineering field.
Machines, Evolutionary computation to minimize the execution periods of functional tasks. The aim of this special issue is to highlight the utility of different soft computing methodologies on software engineering problems.
area which has attracted the attention of several researchers.
Please submit your paper (in word/pdf format) at email: dr.neelamadhab@gmail.com / neela.mbamtech@gmail.com with 'AMLiM (Application of Machine Learning: Multidisciplinary Domains: ' mentioned in the subject line.
Click here for the brochure and for full details about the conference, click here.


VULCAN — Rose Ann Wenzel, 89, of Vulcan, passed away Saturday, Sept. 1, 2018, at ManorCare in Kingsford.
She was born on May 9, 1929, in Vulcan the daughter of the late Michael and Rose Opolka.
Rose married Thadeus "Keppo" Baranski of June 30, 1951, at St. Barbara Church in Vulcan. He preceded her in death on May 4, 1968.
She then married Roy Wenzel on March 29, 1969. He preceded her in death on January 19, 1974.
Rose worked in housekeeping at the First National Bank in Norway, and for 13 years at ManorCare in Kingsford.
She loved playing bingo and cards, watching westerns and the Green Bay Packers. She loved to make Polish dishes for her family.
Rose is survived by her daughter, Roseann DeMarse; three sons, Albert (Molly) Baranski, John Baranski and Michael (Danielle) Baranski; grandson, Tyler Baranski; great-grandson, Kamden Baranski; step-son, David (Mary) Wenzel and his family of Gaylord; sister, Marilyn Steeno of Niagara, Wis.; many nieces and nephews; and special neighbors, Vicky and Butch Pipp.
She was preceded in death by her six sisters, Nora, Ann, Stella, Catherine, Julia and Helen; three brothers, Adam, Johnny and Mike Opolka; and her son-in-law, Richard DeMarse.
Per Rose's request, there will be a private graveside service at the Norway Township Cemetery.
Condolences to the family of Rose may be expressed online at www.ortmanfuneralhome.com.
Arrangements announced by the Ortman Funeral Home in Norway.


text:
Mellersta Västmanlands kontrakt var ett kontrakt i Västerås stift. Kontraktet bildades 1995. Kontraktet upphörde den 31 december 2006 och dess församlingar överfördes till Norra Västmanlands kontrakt och Södra Västmanlands kontrakt.

Administrativ historik
Kontraktet bildades av
hela Västanfors kontrakt där församlingarna vid upplösningen överfördes till Norra Västmanlands kontrakt
Skinnskattebergs församling som 2006 uppgick i Skinnskatteberg med Hed och Gunnilbo församling
Gunnilbo församling som 2006 uppgick i Skinnskatteberg med Hed och Gunnilbo församling
Heds församling som 2006 uppgick i Skinnskatteberg med Hed och Gunnilbo församling
Norbergs församling
Västanfors församling som 2006 uppgick i Västanfors-Västervåla församling
Västervåla församling som 2006 uppgick i Västanfors-Västervåla församling
del av Sala kontrakt där församlingen vid upplösningen överfördes till Norra Västmanlands kontrakt
Karbennings församling
delar av Munktorps kontrakt där församlingarna vid upplösningen överfördes till Södra Västmanlands kontrakt
Hallstahammars församling som 2006 uppgick i Hallstahammar-Bergs församling
Bergs församling som 2006 uppgick i Hallstahammar-Bergs församling
Kolbäcks församling som 2006 uppgick i Kolbäck-Säby församling
Säby församling som 2006 uppgick i Kolbäck-Säby församling
Ramnäs församling
Sura församling

Referenser
För allmänna uppgifter enligt respektive församlingsartikel
Historiska kontrakt i Västerås stift
Bildanden 1995
Upplösningar 2006


Deu 28:1 And it will be, if you shall listen carefully to the voice of Jehovah your God, to observe and to do all His commandments which I command you today, Jehovah your God will set you on high above all nations of the earth.
Deu 28:2 And all these blessings shall come on you and overtake you, if you will listen to the voice of Jehovah your God.
Deu 28:3 You shall be blessed in the city, and be blessed in the field.
Deu 28:4 The fruit of your body shall be blessed, and the fruit of your ground, and the fruit of your cattle, the increase of your cows, and the flocks of your sheep.
Deu 28:5 Your basket and your store shall be blessed.
Deu 28:6 You shall be blessed when you come in, and blessed when you go out.
Deu 28:7 Jehovah shall cause your enemies that rise up against you to be stricken before your face. They shall come out against you one way, and flee before you seven ways.
Deu 28:8 Jehovah shall command the blessing on you in your storehouses, and all that you set your hand to. And He shall bless you in the land which Jehovah your God gives you.
Deu 28:9 Jehovah shall establish you a holy people to Himself, as He has sworn to you, if you shall keep the commandments of Jehovah your God and walk in His ways.
Deu 28:10 And all the peoples of the earth shall see that you are called by the name of Jehovah, and they shall be afraid of you.
Deu 28:11 And Jehovah shall prosper you in goods, in the fruit of your body, and in the fruit of your cattle, and in the fruit of your ground, in the land which Jehovah swore to your fathers to give you.
Deu 28:12 Jehovah shall open to you His good treasure, the heaven to give the rain to your land in its season, and to bless all the work of your hand. And you shall loan to many nations, and you shall not borrow.
Deu 28:13 And Jehovah shall make you the head, and not the tail. And you shall be always above, and you shall not be beneath, if you listen to the commandments of Jehovah your God, which I command you today, to observe and to do them.
Deu 28:14 And you shall not go aside from any of the words which I command you today, to the right hand or the left, to go after other gods to serve them.