text: STATEMENT OF DANIEL N. WENK, DEPUTY DIRECTOR, NATIONAL PARK SERVICE, DEPARTMENT OF THE INTERIOR, BEFORE THE SUBCOMMITTEE ON NATIONAL PARKS, SENATE COMMITTEE ON ENERGY AND NATURAL RESOURCES, CONCERNING S. 148, TO ESTABLISH THE PATERSON GREAT FALLS NATIONAL PARK IN THE STATE OF NEW JERSEY. September 27, 2007 Mr. Chairman, thank you for the opportunity to appear before your committee to present the views of the Department of the Interior on S. 148, a bill to establish the Paterson Great Falls National Park in the State of New Jersey. The Department opposes S. 148. The Department has three main objections to the bill. First, the Special Resource Study authorized by P.L. 107-59 and still under final Departmental review, has preliminarily concluded that the resources of the Great Falls Historic District do not meet congressionally required criteria for designation as a unit of the National Park System. Second, the bill includes within the boundary of the proposed unit, a resource with no relationship to the documented period of historic significance of the Great Falls Historic District or of any determined national significance under established National Historic Landmark criteria. And third, the bill also contains a number of sections that raise crucially important concerns as to how the proposed unit would be effectively and efficiently managed by the National Park Service. The history of the Great Falls Historic District is rich in the nation's late 18th and early 19th century movement into the industrial revolution. Conceived by Alexander Hamilton as the demonstration of his Report on Manufactures to Congress, the venture was of clear historic significance. While the Hamilton-inspired Society for the Establishment of Useful Manufactures (S.U.M.) did not achieve the early success envisioned by its architect, largely due to diversion of funds by its initial governor, William Duer, it became a very successful real estate leasing and water power purveyor into the mid 20th century. The S.U.M. water power system at the Great Falls, designed by Pierre C. L'Enfant, and constructed between 1794 and 1827, was an engineering achievement of major importance. Over time, industries at the Great Falls produced cotton and wool textiles, spun flax, hemp, jute, paper, and other products. The site was the location of Samuel Colt's unsuccessful first arms factory, and a major center for locomotive manufacturing and the production of silk fabrics. The latter activity of silk weaving and dyeing, which during its heyday produced half of the nation's silk products, earned Paterson the label of "Silk City." The District was also an important place in labor history, with the unsuccessful Silk Strike of 1913 involving an estimated 24,000 workers spurred on by the labor organization, the Industrial Workers of the World, often referred to as the "Wobblies." John Holland's first submarine, "The Fenian Ram," built in New York, was fitted with its engine at the Great Falls and made its maiden voyage on the Passaic River. While the District was plagued by arson impacting or destroying many of its earliest and most important mills, the remaining structures have integrity and have been and continue to be rehabilitated for housing and other public and private adaptive reuses. During the course of the Special Resource Study and the public comment period for the report which ended on January 30, 2007, a number of Alexander Hamilton biographers, knowledgeable historians, and interested individuals have urged the designation of the District as a unit of the National Park System because of its seminal role in the industrial revolution and its association with Alexander Hamilton. The Department concurs that the history of the Great Falls Historic District and its remaining resources are of national significance. Its designations as a National Historic Landmark and National Natural Landmark attest to that significance. National significance, although the first criterion analyzed in any Special Resource Study, does not alone result in a recommendation to Congress for unit designation. The resource being studied must also be judged suitable and feasible for designation, and a determination must be made that there is a need for National Park Service (NPS) management of the resource. The National Park Service does not believe that the Great Falls Historic District meets these critical criteria nor is there a need for NPS management of, or presence at, the site. Suitability is the determination of whether comparable resources to those being studied are already adequately represented in the National Park System or protected by other public agencies including state and local governments or private organizations. The extant resources of the District primarily comprise the S.U.M. water power system and the remaining elements of a collection of 19th century mills used for the manufactures noted above. We believe that within the National Park System and among numerous other protected sites, there are similar resources adequate to interpret the major theme categories also associated with the Great Falls Historic District, whether they represent comparable manufacturing enterprises, early water power, labor unrest of the same period, or sites associated with Alexander Hamilton's contributions to our nation. In the National Park System, itself, Lowell National Historical Park contains comparable mill resources and tells the stories associated with our nation's industrial revolution, including those of immigrant workers and labor unrest. The John H. Chafee Blackstone River Valley National Heritage Area contains Slater's Mill, the first successful textile manufacturing enterprise in the nation. The Special Resource Study documents many examples of similar resources and themes within and outside of the National Park System. NPS sites associated with Alexander Hamilton include his home, Hamilton Grange, in New York City and, of course, Independence National Historical Park in Philadelphia. The feasibility analysis conducted by the National Park Service estimates the costs for planning, developing and operating a unit at the Great Falls to range from $20 to $34 million dollars over a ten-year period. This estimate assumes a small staffing contingent and no major NPS ownership of resources at the site. In the difficult budget climate facing federal agencies, we believe these costs would negatively impact finite resources available to other units of the National Park System in the Northeast Region and that lesser and equally effective cost alternatives are available through a partnership between the NPS and the State of New Jersey. We believe the costs to implement the provisions of S. 148 would far exceed this estimate. In late 2004 the State of New Jersey established the Great Falls State Park in the Historic District. The boundaries of the park contain the primary resources related to the S.U.M. water power system and the earliest mill sites. The State has recently completed a design competition for phase 1 of the park and has pledged $10,000,000 for park improvements. The Department believes that the Division of Parks and Forestry of the New Jersey State Department of Environmental Protection, which manages both natural and cultural resources of national significance throughout the State, is fully capable of providing the stewardship necessary to protect the critical resources associated with Alexander Hamilton and the S.U.M. Therefore, we believe there is no need for NPS management of these resources. We understand that many state park systems are encountering necessary budgetary constraints similar to those of the National Park Service. We do not believe this constitutes a reason to supplant any state's management of resources. The Department also has strong concerns with a number of provisions of S. 148 that go beyond the fact that the Great Falls Historic District fails to meet congressionally required criteria for designation. The bill includes Hinchliffe Stadium within the proposed boundary of the unit. Hinchliffe Stadium, built during the 1930s, has important associations with the Negro Baseball Leagues, serving during periods as the home field for the New York Black Yankees. It is also the site where Larry Doby, the second African American to play in the previously all white major leagues, played high school baseball. The site is listed on the National Register of Historic Places, but currently is listed as "locally," rather than "nationally" significant. To be considered as a unit of the National Park System, resources must be determined to meet the criteria for National Historic Landmark (NHL) designation. This resource is far from being considered for NHL status and no nomination for such a designation has been presented to the Department. Hinchliffe Stadium also has no connection to the NHL determined period of historical significance of the Great Falls Historic District, and we believe it should not be considered for unit designation. Costs associated with maintaining and improving the site would also be significant due to its present deteriorated condition. S. 148 contains other provisions that cause the Department concern. In section 6(d), for example, the bill provides a process for approval of the park's management plan more common to Affiliated Areas of the National Park System or national heritage areas. In section 7, the bill creates a federal commission to coordinate management of the park. In section 8, an advisory council is provided, also appointed by the Secretary, to advise the group created in section 7. In section 10(c), the bill appears to provide for authority to the Secretary to condemn property for Federal ownership under certain circumstances. Congress has been reluctant to extend this authority in recent park legislation. Section 11(b) provides a matching requirement that for every one federal dollar the value in cash or in-kind of three non-federal dollars must be available. In effect, annual funding to operate the national park unit would be contingent upon the availability of non-federal donations. The Department has concerns with taking on this permanent funding obligation under the assumption that some of the costs would be covered through private fundraising since appropriations would be required if private funds proved to be insufficient. While philanthropic donations can and do help to enhance park activities, facilities and resources, they should not be relied upon to support core operations, including the salaries for permanent staff. We have specific concerns about the viability of raising funds for this purpose based on our past experience working in Paterson. While during the study period, advocates for unit designation have stated (as does section 2 (a)(10) of the bill) that significant funding for the park will be available from private donors if the unit is established, attempts to verify any tangible evidence of private funding interests were met with the simple explanation that "They will not identify themselves unless and until the park is created." In 1996, Congress authorized $3.3 million through the Omnibus Parks and Public Lands Management Act (section 510) in technical assistance, grants, and infrastructure improvements. All funding required a 50 percent local match, yet over the past 11 years, no local matching funds have been made available under this authority. S. 148 contains other technical and substantive provisions of concern that are incompatible with current unit designation and park management practices. In conclusion, Mr. Chairman, the Special Resource Study of the Great Falls Historic District does suggest a pathway to an effective partnership with the State of New Jersey to protect and interpret the nationally significant resources of the District. It provides for possible congressional consideration of a Great Falls National Historic Site, as an Affiliated Area of the National Park System, with technical and financial assistance provided by the Secretary of the Interior to the State of New Jersey. We believe that time spent exploring this alternative could enhance the protection of the District's resources by establishing a strong partnership between the NPS and the New Jersey Department of Environmental Protection, one not dissimilar to the very productive partnership we have enjoyed with the State of New Jersey in its 25 years of management of the congressionally designated 1.1 million acre New Jersey Pinelands National Reserve. Thank you for the opportunity to present the Department's position on this bill. This concludes my prepared remarks and I would be glad to answer any questions that you or the members of the committee may have.

subset: commoncrawl


text:
It's a chapter of history mostly forgotten, not just across Canada but even in the Maritime provinces themselves. Shipbuilding – like fishing – is an obvious fact of life on the Atlantic coast, but few people today know just how extensive the industry once was. There was a time not that long ago when men built ships in sheltered harbours, on open beaches and up narrow rivers – ships that went on to carry cargoes and passengers all over the world.
From the first boats built by the earliest settlers, to the golden Age of Sail in the 1800s, and from the Grand Bank fishing schooners to the high tech naval frigates of today – the thousands of vessels built in Atlantic Canada during the past 250 years have shaped the region like no other industry.
Maritime Shipbuilding is a half hour documentary that explores this seafaring history and the proud tradition that lives on to this day. The film travels to once-thriving shipbuilding centres in the Maritimes to rediscover the story of one of the world's most vibrant, productive, and profitable shipbuilding regions.
Although no longer the economic driving force it once was, the shipbuilding industry in Atlantic Canada continues to prosper. The thousands of people who recently attended the re-launch of the Bluenose II in Lunenburg, Nova Scotia are a testament to that enduring legacy.
Maritime Shipbuilding was written and directed by award-winning Halifax documentary-maker Geoff D'Eon, (Blood On The Coal/Facebook Follies) and produced by Edward Peill from Halifax-based Tell Tale Productions Inc.
"This was an interesting piece to work on. More than 28,000 ships built in the Maritimes? Who knew?" says D'Eon "It's not only the numbers that are surprising, but the locations where these ships were built, places that today show no trace of the industry that once was."
Maritime Shipbuilding will have its world broadcast premiere on CBC Television's Land & Sea on Sunday, December 9, 2012 at 12 Noon. Following the broadcast, the documentary can be watched on the CBC TV website at: www.cbc.ca/landandsea. Land & Sea is CBC's 2nd longest running TV series and can be followed on Twitter: @cbclandandsea
Maritime Shipbuilding was produced in association with CBC TV with funding from Film NS, and Provincial and Federal tax credits.


text:
System requirements
Headset and headphones
- About the VIVE Cosmos headset
- Putting on the VIVE Cosmos headset
- Can I wear prescription glasses while using the headset?
- Adjusting the IPD on the headset
- Flipping up the visor
- Connecting a USB device to VIVE Cosmos
- Removing or reattaching the face cushions
- Removing the front and back pads
- Reattaching the front and back pads to the headset
- Reattaching the headset cable strip to the back pad
- Detaching the top strap from the headset band
- Attaching the top strap to the headset band
- Replacing the front cover
- What does the status light on the headset mean?
Product care and maintenance
Link box
Play area
- What is the play area?
- Planning your play area
- Choosing the play area
- Setting up VIVE Cosmos for the first time
- Setting up the play area
- What is the recommended space for the play area?
- Can I include space occupied by furniture for the play area?
- Does VIVE Cosmos store my room or environment image?
- Can stationary experiences work at room scale?
- How do I fix download errors during VIVE Setup installation?
- I can't complete the room setup. What should I do?
- Why are the headset and controllers not tracked properly?
VIVE Reality System
- Disabling Volume limit
- Capturing screenshots in VR
- Seeing real surroundings
- Enabling motion compensation
- What is motion compensation?
- Updating the firmware
- Troubleshooting VIVE Cosmos
- Joining the VIVE Cosmos beta program
- Setting the power supply frequency
- What do the error codes and messages mean? What can I do?
What is Lens?
Lens is your starting point in VR—just press the VIVE button on the right controller to bring it up.
Lens, you can:
- View, sort, and launch titles.
- Browse the VIVEPORT store.
- Go to Origin. To learn more about Origin, see What is Origin?.
- View and change system settings such as the default Lens height and distance, boundary color, and system volume.
If Lens is too far or close, you can reposition it in the Lens settings. See Changing Lens settings.
Why am I seeing a "Sign In Required" message, what should I do?
You need to be signed in to your
VIVEPORT™ account to use
Lens. Go to the computer where
VIVE Cosmos is connected to and sign in to your
VIVEPORT account.
Launching titles from Lens
Quickly sort, find, and launch titles from
Important: Sign in to your
VIVEPORT account on the computer where
VIVE Cosmos is connected to before opening
- Press the VIVE button on the right controller to open Lens.
- Use the joystick to scroll up or down to see recently-used as well as featured titles.
To browse your entire collection, select
Go to Library.
Tip: To filter currently installed titles, select an option from the drop-down menus.
- Select a title, and then select Play or Download to launch or download the title.
Changing Lens settings
Adjust the audio volume, change the boundary color and transparency, choose a night-time display mode, choose headset camera settings, and more from the
Lens settings.
- Press the VIVE button on the right controller to open Lens.
- On the right side of Lens, select .
- Use the joystick to scroll up or down the available settings.
- Select an option pulling the trigger on a particular setting.
- After selecting your preferences, select .
Was this helpful?
Thank you! Your feedback helps others to see the most helpful information.


text:
Designing for Cisco Internetwork Solutions (DESGN) Foundation Learning Guide: (CCDA DESGN 640-864), 3rd Edition
- By Sean Wilkins
- Published Jul 31, 2011 by Cisco Press.
- Sorry, this book is no longer in print.
eBook (Watermarked)
- Your Price: $53.59
- List Price: $66.99
- Includes EPUB and PDF
- About eBook Formats
This eBook includes the following formats, accessible from your Account page after purchase:
EPUB The open industry format known for its reflowable content and usability on supported mobile devices.
PDF The popular standard, used most often with the free Acrobat® Reader® software.
This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.
- Copyright 2011
- Edition: 3rd
- Book
Designing for Cisco Internetwork Solutions (DESGN)
Foundation Learning Guide
Third Edition
Sean Wilkins
Foundation learning for the CCDA DESGN 640-864 exam
Designing for Cisco Internetwork Solutions (DESGN) Foundation Learning Guide, Third Edition, is a Cisco®-authorized, self-paced learning tool for CCDA® foundation learning. This book provides you with the knowledge needed to design enterprise networks. By reading this book, you will gain a thorough understanding of designing routed and switched network infrastructures and services involving LAN, WAN, and broadband access for businesses and organizations.
Designing for Cisco Internetwork Solutions (DESGN) Foundation Learning Guide, Third Edition teaches you how to gather internetworking requirements, identify solutions, and design the network infrastructure and services to ensure basic functionality using the principles of hierarchical network design to structure and modularize a converged enterprise network design. Specific topics include understanding the design methodology; structuring and modularizing the network design; designing the Enterprise Campus, Enterprise Data Center, Enterprise Edge, and remote modules as needed; designing an addressing plan and selecting suitable routing protocols; designing basic voice transport across the network; designing a basic wireless solution; and evaluating security solutions. Chapter-ending review questions illustrate and help solidify the concepts presented in the book.
Whether you are preparing for CCDA certification or simply want to gain a better understanding of network design principles, you will benefit from the foundation information presented in this book.
Designing for Cisco Internetwork Solutions (DESGN) Foundation Learning Guide, Third Edition, is part of a recommended learning path from Cisco that includes simulation and hands-on training from authorized Cisco Learning Partners and self-study products from Cisco Press. To find out more about instructor-led training, e-learning, and hands-on instruction offered by authorized Cisco Learning Partners worldwide, please visit www.cisco.com/go/authorizedtraining.
· Understand network design methodologies and the lifecycle of a network
· Learn how to structure and modularize network designs within the Cisco Network Architectures for the Enterprise
· Design basic campus and data center networks
· Build designs for remote connectivity with WAN technologies
· Examine IPv4 and IPv6 addressing schemes
· Select the appropriate routing protocols for various modules in the enterprise architecture
· Evaluate security solutions for the network
· Identify voice and video networking considerations
· Understand design technologies and considerations when implementing a controller-based wireless network
This book is in the Foundation Learning Guide Series. These guides are developed together with Cisco® as the only authorized, self-paced learning tools that help networking professionals build their understanding of networking concepts and prepare for Cisco certification exams.
Related Articles
(Video) Exam Profile: Cisco CCDA Design
An Overview of Cisco IOS Versions and Naming
Cisco ASA Access Lists Concepts and Configuration
Cisco ASA Basic Internet Protocol Inspection
Cisco IOS Image Concepts and Configuration
IPv6 Translation and Tunneling Technologies
Online Sample Chapter
CCDA DESGN 640-864: Designing Remote Connectivity
Table of Contents
Introduction xxiii
Chapter 1 Network Fundamentals Review 1
Introduction to Networks 2
Protocols and the OSI Model 2
OSI Model 3
Protocols 3
OSI Layers 4
Physical Layer: Layer 1 4
Data Link Layer: Layer 2 4
Network Layer: Layer 3 5
Transport Layer: Layer 4 5
Upper Layers: Layers 5 Through 7 6
Communication Among OSI Layers 6
LANs and WANs 8
Network Devices 10
Terminology: Domains, Bandwidth, Unicast, Broadcast, and Multicast 10
Hubs 11
Physical Interfaces and Ports 11
Switches 11
Switches Versus Bridges 12
Routers 12
Introduction to the TCP/IP Suite 13
TCP/IP Transport Layer Protocols 15
Port Numbers 17
TCP Sequencing, Acknowledgment, and Windowing 18
TCP/IP Internet Layer Protocols 22
Protocols 22
IPv4 Datagrams 22
IPv6 Datagrams 24
Routing 25
Routers Work at the Lower Three OSI Layers 26
Routing Tables 27
Routing Protocols 28
Addressing 29
Physical Addresses 29
Logical Addresses 30
Routing and Network Layer Addresses 31
IPv4 Addresses 31
IPv4 Address Classes 31
Private and Public IPv4 Addresses 32
IPv4 Subnets 33
IPv6 Addresses 34
IPv6 Address Types 36
Switching Types 36
Layer 2 Switching 37
Layer 3 Switching 39
Spanning Tree Protocol 40
Redundancy in Layer 2 Switched Networks 40
STP Terminology and Operation 41
STP Terminology 41
STP States 43
Rapid STP 44
Virtual LANs 45
VLAN Membership 45
Trunks 46
STP and VLANs 46
Inter-VLAN Routing 47
Comprehensive Example 49
Summary 52
Review Questions 52
Chapter 2 Network Design Methodology 53
Understanding the Network Architectures for the Enterprise 53
Business Drivers for a New Network Framework 54
Business Forces 54
Technology-Related Forces 54
IT Challenges 55
Cisco Network Architectures for the Enterprise 55
Borderless Networks Architecture 56
Borderless Networks Architecture Approach 57
Collaboration Architecture Approach 58
Data Center/Virtualization Architecture Approach 59
Identifying Design Requirements 61
Using the PPDIOO Approach for Networks 61
Benefits of the Lifecycle Approach 63
Design Methodology 64
Identifying Customer Design Requirements 65
Identifying Network Applications and Network Services 65
Defining Organizational Goals 67
Identifying Organizational Constraints 69
Identifying Technical Goals 71
Assessing Technical Constraints 73
Characterizing the Existing Network and Sites 74
Identifying Major Features of the Network 74
Sample Site Contact Information 75
Sample High-Level Network Diagram 76
Auditing the Existing Network 77
Using Tools for Auditing the Network 79
RSPAN with VACLs for Granular Traffic Analysis 81
Analyzing Network Traffic and Applications 83
Using Tools for Analyzing Network Traffic 84
Reviewing Network Traffic Information 85
Analyzing Network Health 85
Creating a Draft Design Document 86
Time Estimates for Performing Network Characterization 88
Using the Top-Down Approach to Network Design 89
Top-Down Approach to Network Design 90
Top-Down Design Example 91
Decision Tables in Network Design 91
Assessing the Scope of the Network Design Project 93
Using Structured Design Principles 93
Logical Structure 94
Physical Structure 95
Network Design Tools 95
Testing the Design 96
Planning an Implementation 97
Documenting the Design 98
Summary 100
References 100
Review Questions 101
Chapter 3 Structuring and Modularizing the Network 103
Designing the Network Hierarchy 103
Introducing the Hierarchical Network Model 104
Describing Access Layer Functionality 106
Campus Access Layer Connectivity 107
Describing Distribution Layer Functionality 108
Virtual Switches 110
Describing Core Layer Functionality 111
Using a Modular Approach in Network Design 114
Describing the Enterprise Campus Functional Area 117
Enterprise Campus Infrastructure Module 117
Data Center Module 117
Describing the Enterprise Edge Area 119
E-Commerce Module 121
Internet Connectivity Module 121
WAN and MAN and Site-to-Site VPN Module 122
Remote Access and VPN Module 122
Describing the Service Provider Area 122
ISP Module 123
Public Switched Telephone Network Module 123
Frame Relay and ATM Module 123
Describing the Remote Area 124
Enterprise Branch Module 124
Enterprise Data Center Module 125
Enterprise Teleworker Module 125
Supporting Services on Borderless Networks 126
Explaining the Role of Borderless Network Services 126
Mobility Considerations 128
Security Infrastructure Services 129
Designing Security to Protect Against External Threats 132
Application Performance Considerations 134
Resolving Application Issues with Cisco Application Network Services 135
Cisco ANS Components 135
IP Communications 136
Voice Transport 137
High-Availability Network Services 141
Full-Mesh Versus Partial-Mesh Redundancy 142
Identifying Network Management Protocols and Features 145
Network Management Overview 145
SNMP Message Types 147
SNMP Version 2 148
SNMP Version 3 149
MIB Characteristics 150
MIB Variable Retrieval 152
Using RMON 153
NetFlow Characteristics 155
NetFlow Versus RMON Information Gathering 157
Applications Using NetFlow 158
Cisco Discovery Protocol Features 159
Syslog Features 160
Summary 164
References 164
Review Questions 164
Chapter 4 Designing Basic Campus and Data Center Networks 167
Describing Campus Design Considerations 167
Campus Design Factors 168
Network Application Characteristics and Considerations 168
Peer-Peer Applications 169
Client—Local Server Applications 170
Client—Data Center Applications 170
Client—Enterprise Edge Applications 172
Application Requirements 173
Environmental Characteristics and Considerations 174
Intrabuilding Structure 174
Interbuilding Structure 175
Distant Remote Building Structure 175
Transmission Media Considerations 176
Copper 176
Optical Fiber 177
Wireless 177
Campus Transmission Media Comparison 178
Transmission Media Cabling Example 179
Infrastructure Device Characteristics and Considerations 179
Quality of Service (QoS) 180
Designing the Campus Infrastructure Module 181
Design Considerations for the Campus Network 181
Design Considerations for the Building Access Layer 182
Managing VLANs and STP 183
Managing Trunks Between Switches 186
Managing Default PAgP Settings 186
Consider Implementing Routing in the Building Access Layer 186
Design Considerations for the Building Distribution Layer 187
Best Practices in the Distribution Layer 187
Using First-Hop Redundancy Protocols 188
Deploying Layer 3 Routing Protocols 189
Using the Virtual Switching System at the Distribution Layer 191
Campus Core Design Considerations 192
Small and Medium Campus Design Options 195
Edge Distribution at the Campus Core 196
Describing Enterprise Data Center Considerations 197
Describing the Enterprise Data Center Architectures 197
Cisco Enterprise Data Center Architecture Framework 198
Server Challenges 200
Data Center Facility Aspects 200
Enterprise Data Center Infrastructure 205
Data Center Access Layer 206
Data Center Aggregation Layer 207
Data Center Core Layer 207
Describing Enterprise Network Virtualization Tools 208
Virtualization Challenges 208
What Is Virtualization? 209
Types of Virtualization 209
Virtualization Technologies 210
Network Virtualization Design Considerations 211
Summary 212
References 212
Review Questions 213
Chapter 5 Designing Remote Connectivity 215
Identifying WAN Technology Considerations 215
Review of WAN Features 216
Comparison of WAN Transport Technologies 217
Time-Division Multiplexing 218
ISDN Connectivity 218
Frame Relay 219
Multiprotocol Label Switching 219
Metro Ethernet 219
DSL Technology 220
Cable Technology 221
Wireless Technology 221
SONET and SDH Technology 222
DWDM Technology 223
Dark Fiber 224
WAN Link Categories 224
WAN Transport Technology Pricing and Contract Considerations 225
WAN Design Requirements 226
Response Time 227
Throughput 227
Packet Loss 228
Reliability 228
QoS Considerations for Bandwidth Constraints 228
Classification 229
Congestion Management 230
Traffic Shaping and Policing 231
Link Efficiency 232
Window Size 233
Designing the Enterprise WAN 233
Traditional WAN Designs 234
Star Topology 234
Fully Meshed Topology 235
Partially Meshed Topology 235
Remote-Access Network Design 235
VPN Design 236
Enterprise Versus Service Provider—Managed VPNs 237
Enterprise Managed VPN: IPsec 237
Service Provider—Managed VPNs: MPLS 242
Service Provider—Managed VPNs: Metro Ethernet 242
Service Provider—Managed VPNs: VPLS 243
WAN Backup Strategy Design 244
Using the Internet as a WAN Backup 245
Selecting the Enterprise WAN Architecture 246
Cisco Enterprise MAN and WAN Architecture 247
Selecting Enterprise WAN Components 249
Hardware Selection 249
Designing the Enterprise Branch 251
Enterprise Branch Architecture 251
Enterprise Branch Design 252
New Features on the ISR G2 Routers 253
Small Branch Office Design 254
Medium Branch Office Design 255
Large Branch Office Design 256
Enterprise Teleworker (Cisco Virtual Office Solution) Design 256
New ISRs for Small Offices and Teleworkers 257
Summary 259
References 259
Review Questions 260
Chapter 6 Designing IP Addressing 261
Designing IPv4 Addressing 261
IPv4 Addressing 261
Private and Public Addressing Guidelines 262
Recommended Practices for NAT 262
Developing an Addressing Plan 263
Planning the IP Addressing Hierarchy 266
Design Consideration: Route Summarization Groups 266
Address Blocks by Location 267
Hierarchical IP Addressing Plan 268
Recommended Practices for Name Resolution 270
Locating DHCP and DNS Servers in the Network 272
IP Address Space Planning Road Map 272
Designing IPv6 Addressing 272
IPv6 Addressing 273
Benefits of IPv6 Addressing 273
IPv6 Address Types 274
IPv6 Address Assignment Strategies 277
Identifying IPv6 Name Resolution 277
Making the Transition from IPv4 to IPv6 278
Strategies for IPv6 Deployment 279
Dual-Stack Model 280
Hybrid Model 281
Service Block Model 284
Summary 285
References 286
Review Questions 287
Chapter 7 Designing and Selecting Routing Protocols 289
Reviewing Enterprise Routing Protocols 289
Reviewing Routing Protocol Fundamentals 289
Differentiating Between Distance Vector and Link-State Routing Protocols 289
Differentiating Between Interior and Exterior Routing Protocols 292
Differentiating Between Hierarchical and Flat Routing Protocols 293
Routing Protocol Convergence 294
Routing Protocols for the Enterprise 295
Open Shortest Path First 296
Border Gateway Protocol 298
IPv6 Routing 300
Selecting an Enterprise Routing Protocol 301
When to Choose EIGRP 301
When to Choose OSPF 301
Designing a Routing Protocol Deployment 301
Applying Routing Protocols to a Hierarchical Network Structure 301
Routing in the Campus Core 302
Routing in the Building Distribution Layer 302
Routing in the Enterprise Edge Functional Area 302
Route Redistribution 303
Route Redistribution Planning 304
Remote-Access and VPN and Internet Connectivity Module Route Redistribution 305
Route Filtering 306
Route Filtering and Internet Connectivity 306
Route Summarization 306
Recommended Practice: Summarize at the Distribution Layer 307
Recommended Practice: Passive Interfaces for IGP at the Access Layer 308
IPv6 Route Summarization 308
Summary 309
Review Questions 310
Chapter 8 Evaluating Security Solutions for the Network 311
Defining Network Security 311
Network Security Background 312
Security Legislation 312
Threats and Risks 313
Reconnaissance Attacks 314
Vulnerability Assessment 315
Example Threat: Gaining Unauthorized Access to Systems 316
Example Risk: Loss of Availability 318
Everything Is a Potential Target 319
Understanding Network Security Policy and Processes 319
Definition of a Security Policy 319
Risk Assessment and Management 320
Example: Security Policy 322
Network Security Is a Continuous Process 323
Integrating Security Design and Network Design 324
Understanding the Cisco SAFE Approach 325
Cisco SAFE Architecture 325
The Network as a Platform for Security 326
Cisco Security Control Framework 327
Trust and Identity Management 328
Trust 329
Identity 330
Access Control 331
Trust and Identity Management Technologies 331
Example: Cisco IBNS 332
Example: Firewall Filtering Using ACLs 332
Example: Cisco NAC Appliance 333
Identity and Access Control Deployment Locations 333
Threat Defense 335
Incorporating Physical Security 335
Infrastructure Protection 336
Threat Detection and Mitigation 338
Threat Detection and Mitigation Solutions 339
Example: Cisco IronPort ESA 341
Example: Cisco IronPort WSA 341
Secure Connectivity 342
Encryption Fundamentals 343
VPN Protocols 344
Ensuring Privacy 345
Example: Providing Confidentiality over the Internet 347
Example: Protecting Communication over the Public Infrastructure 347
Example: Network Authentication over a VPN 347
Maintaining Data Integrity 347
Example: VPN Tunneling for Data Integrity 348
Example: Implementation of Digital Signatures 349
Security Management 349
Selecting Network Security Solutions 352
Security Integration in Network Devices 352
Cisco IOS Security 352
Security Appliances 354
Intrusion Prevention System 355
Cisco Catalyst Services Modules 356
Endpoint Security Solutions 357
Securing the Enterprise Network 358
Example: Deploying Identity and Access Control in the Enterprise Campus 358
Example: Deploying Threat Detection and Mitigation in the Enterprise Campus 359
Example: Deploying Infrastructure Protection in the Enterprise Campus 359
Example: Deploying Security in the Enterprise Campus 359
Example: Deploying Identity and Access Control in the Enterprise Data Center 361
Example: Deploying Threat Detection and Mitigation in the Enterprise Data Center 361
Example: Deploying Infrastructure Protection in the Enterprise Data Center 361
Example: Deploying Security in the Data Center 361
Example: Deploying Identity and Access Control in the Enterprise Edge 364
Example: Deploying Threat Detection and Mitigation in the Enterprise Edge 364
Example: Deploying Infrastructure Protection in the Enterprise Edge 364
Example: Deploying Security in the Enterprise Edge 366
Summary 367
References 368
Review Questions 369
Chapter 9 Identifying Voice and Video Networking Considerations 371
Integrating Voice and Video Architectures 371
Differentiating Between Analog and Digital Signaling 372
Introducing Voice and Video over IP 373
Voice and Video Standards 376
Terminals 376
Gateways 377
Gatekeepers 377
Multipoint Control Units 378
Introducing VoIP 379
IP Telephony Design Models 381
Introducing Video Considerations 385
Media Application Models 386
Delivery of Media Application 386
Architectural Framework for Media Services 387
Call Control and Transport Protocols 388
Call Control Functions with H.323 388
Voice Conversation with RTP 389
Call Control Functions with SSCP 389
Call Control Functions with SIP 390
Call Control Functions with MGCP 392
Identifying the Requirements of Voice and Video Technologies 393
Minimizing Delay, Jitter, and Loss 394
One-Way Network Delay Recommendations 394
Propagation Delay 394
Serialization Delay 395
Processing Delay 395
Queuing Delay 395
Dejitter Buffers 396
Packet Loss 397
Preventing Echo 398
Echo Canceller Example 399
Echo Cancellation Guidelines 399
Voice Coding and Compression 399
Codec Complexity, DSPs, and Voice Calls 402
Bandwidth Considerations 402
Reducing Voice Traffic with cRTP 403
Reducing Voice Traffic with VAD 403
Voice Bandwidth Calculation 404
Typical Video Resolution and Bandwidth 406
Using QoS for Voice and Video 407
QoS Considerations for Voice and Video in the WAN 413
Call Rerouting Alternatives 414
Call Admission Control Examples 414
Implementing CAC with RSVP 415
Voice Traffic Engineering Overview 416
Summary 418
References 419
Review Questions 420
Chapter 10 Identifying Design Considerations for Basic Wireless Networking 421
Cisco Unified Wireless Network Review 421
Cisco Unified Wireless Network Architecture 421
Cisco Unified Wireless Network Elements 422
CAPWAP and LWAPP Fundamentals 423
Split Media Access Control 425
Local Media Access Control 426
Access Point Modes 427
Wireless Infrastructure 428
Wireless Authentication 430
Overview of WLAN Controllers 432
Access Point Support and Scaling 435
Access Point Scalability Considerations 437
Multiple AP Manager Interface Example 437
Link Aggregation (LAG) with a Single AP Manager Interface Example 439
Wireless Network Controller Technology 440
Lightweight Access Point Connectivity to a WLC 440
WLC Selection 440
Lightweight Access Point Operations 442
Mobility in the Cisco Unified Wireless Network 442
Intracontroller Roaming 443
Intercontroller Roaming–Layer 2 444
Intercontroller Roaming–Layer 3 444
Mobility Groups 446
Mobility Group Requirement Example 447
Recommended Practices for Supporting Roaming 448
Controller Redundancy Design 449
Deterministic Controller Redundancy 449
Dynamic Controller Redundancy 451
N + 1 Redundancy Design 452
N + N Redundancy Design 453
N + N + 1 Redundancy Design 454
Radio Resource Management (RRM) and RF Groups 455
RF Grouping 456
Access Point Self-Healing 458
Designing Wireless Networks Using Controllers 458
RF Site Survey 458
RF Site Survey Process 459
Design Considerations for Campus Wireless Networks 466
CAPWAP Access Point Feature Summary 466
Controller Placement Design 467
Campus Cisco Wireless LAN Controller Options 469
Design Considerations for Branch Wireless Networks 470
Hybrid REAP 470
Branch Office Cisco Wireless LAN Controller Options 472
Design Considerations for Guest Services in Wireless Networks 474
Design Considerations for Outdoor Wireless Networks 474
Wireless Mesh Components 476
Mesh Design Recommendations 477
Summary 478
References 478
Review Questions 479
Appendix A Answers to Review Questions 481
Appendix B Acronyms and Abbreviations 489
Other Things You Might Like
- Designing Real-World Multi-domain Networks
- eBook (Watermarked) $46.39
- Designing Real-World Multi-domain Networks
- Book $47.99
- Cisco Certified Design Expert (CCDE 400-007) Official Cert Guide Premium Edition and Practice Test
- Premium Edition eBook $71.99


text:
British Drift Championships Event Information
Commentators slagging too...
18-06-15, 18:16
Drift Allstars Europe Event Information
London Livestream?
13-06-15, 10:42
Round 5 - Throwdown - July...
19-07-15, 22:16
IDC Series Event Information
IDC round 1 2018 aftermath
23-04-18, 08:10
N1 Drift Series Event Information
2016 ni drift AMA series
13-11-15, 12:02
Aftermath: Ultimate Drift...
06-10-15, 21:32
There are no posts in this forum.
Use this control to limit the display of threads to those newer than the specified time frame.
Allows you to choose the data by which the thread list will be sorted.
Order threads in...
Note: when sorting by date, 'descending order' will show the newest results first.
Forum Rules


text: Aperaham, from our Instinct Collection is printed on a vintage dictionary book bringing a gift of art together with a piece of the past. Connecting with artists from around the world and printing their work on the pages of dictionaries from the early 1900's. Each page being it's own unique & one of a kind piece of art. The world is filled with beautiful art that is never exposed to the public. Lost in the creative minds, journals, and shelves of those given a gift to turn a blank canvas into a visual experience. We want to make it available for everyone to enjoy. These PRINTS DO NOT COME FRAMED but will fit a standard 8 x 10 frame, as well as a larger frame with an 8 x 10 matte. We hope you enjoy this truly one of a kind piece due to each page of the dictionary being unique with the print thats on it and take a moment to view our complete collection of art on our Artisan profile page.


text: Paul Maroof founded the Royal Chain Group in 1978. Under his meticulous leadership, he developed his family owned business bringing in his son and daughter as they work diligently together to run, develop, and grow the Royal Chain Group. Mr. Maroof maintains a personal involvement in everything that the Royal Chain Group represents. This commitment has made him the pre-eminent importer of quality jewelry.


text:
On November 5, 1940, Franklin Delano Roosevelt is re-elected for an unprecedented third term as president of the United States.
Roosevelt was elected to a third term with the promise of maintaining American neutrality as far as foreign wars were concerned: "Let no man or woman thoughtlessly or falsely talk of American people sending its armies to European fields." But as Hitler's war spread, and the desperation of Britain grew, the president fought for passage of the Lend-Lease Act in Congress, in March 1941, which would commit financial aid to Great Britain and other allies. In August, Roosevelt met with British Prime Minister Winston Churchill to proclaim the Atlantic Charter, which would become the basis of the United Nations; they also drafted a statement to the effect that the United States "would be compelled to take countermeasures" should Japan further encroach in the southwest Pacific.
Despite ongoing negotiations with Japan, that "further encroachment" took the form of the Japanese bombing of Pearl Harbor—"a day that would live in infamy." The next day Roosevelt requested, and received, a declaration of war against Japan. On December 11, Germany and Italy declared war on the United States.
Certain wartime decisions by Roosevelt proved controversial, such as the demand of unconditional surrender of the Axis powers, which some claim prolonged the war. Another was the acquiescence to Joseph Stalin of certain territories in the Far East in exchange for his support in the war against Japan. Roosevelt is often accused of being too naive where Stalin was concerned, especially in regard to "Uncle Joe's" own imperial desires.


text:
Well, kids, today's the day! The official launch date of Trophy Cupcakes & Party! by Jennifer Shea! It seems oh-so-fitting to celebrate the day with Pink Champagne Cupcakes and so, as promised, here is the recipe to Jennifer's scrumptiously celebratory cupcakes! Enjoy!
makes 2 dozen
Pink Champagne Cupcakes
2 cups cake flour (not self-rising)
1 1/2 cups all-purpose flour
1 tablespoon plus 1/2 teaspoon baking powder
1 teaspoon salt
2/3 cup champagne
2/3 cup half-and-half
1/4 teaspoon red food coloring
1 1/2 cups (3 sticks) unsalted butter, at room temperature
2 1/2 cups sugar
3 eggs
- Preheat the oven to 350ºF. Line two 12-cup muffin pans with cupcake liners and set aside.
- In a large bowl, sift together the cake flour, all-purpose flour, baking powder, and salt. Set aside.
- Combine the champagne, half-and-half, and food coloring in a large measuring cup with a spout. Set aside.
- Combine the butter and sugar in the bowl of a stand mixer fitted with the paddle attachment and beat them at low speed until the mixture is smooth and creamy, about 1 minute if the butter is soft. If the butter is cool, it will take longer. Add the eggs one at a time, mixing well and scraping the bowl after each addition, and waiting until all traces of each egg have disappeared before adding next one.
- Add the dry ingredients in 3 parts, alternating with adding the wet ingredients in 2 parts. Keep the mixer at the lowest speed and mix each time just until the ingredients are combined. When everything has been added, scrape the bowl and paddle one more time, and stir the batter just until it's smooth. Let the batter rest for 15 minutes and stir gently before using.
- Fill the cupcake liners three-quarters full and bake until the tops of the cupcakes are firm and a cake tester inserted into the center of a middle cupcake comes our with just a few crumbs, about 20 minutes. Let the cupcakes cool for 5 minutes in the pans before removing to a rack to cool completely.
Pink Champagne Buttercream
3 cups (6 sticks) unsalted butter, at room temperature
6 cups confectioners' sugar, sifted*
1/4 cup plus 1 tablespoon champagne
2 teaspoons vanilla extract
1/4 teaspoon salt
Red food coloring
- In a stand mixer fitted with the paddle attachment, cream the butter. Start with the mixer at the lowest speed, then gradually increase the speed, using a rubber spatula to scrape the bowl as needed, until the butter is light in color, perfectly smooth, and makes a slapping sound as it hits the sides of the bowl. If the butter is soft, this should only take 30 seconds, but if the butter is cool, it can take a couple of minutes.
- Add the sugar, 1 cup at a time, and mix at the lowest speed until it's fully incorporated before adding the next cup. When all the sugar has been added, scrape the paddle and the bottom and sides of the bowl. Add the champagne, vanilla, salt, and a drop or two of food coloring (or add more for a darker, deeper pink shade), and beat them at low speed for 15 seconds. Increase the speed to as high as you can without making a mess and whip the buttercream until the mixutre is perfectly smooth, creamy, and light, about 5 minutes. Stop the mixer once or twice to scrape the bowl and paddle, then continue beating. At first the buttercream will appear to soften, then it will stiffen and increase in volume.
- Use right away, or store in an airtight container for up to a week in the refrigerator. When you're ready to use it, let the buttercream come to room temperature, then put it back in the stand mixer and use the paddle attachment to beat it until it's creamy and stiff again.


text: Home / Yorkshire Dales/Hawes Product Description A4 Clip Frame of Yorkshire Dales Pubs. An official boxed framed picture. Customer reviews No reviews left yet Write A Review Most RecentTop Rated Delivery & Returns Cancellations, returns and refunds1.18 All customers have the right to cancel their order under the Consumer Contracts (Information, Cancellation & Additional Charges) Regulations.1.19 Your right to cancel an order for goods starts the moment you place your order and ends 14 days from the day you receive your goods.1.20 To meet the cancellation deadline, please notify us via email or phone about cancelling the order before the cancellation period has expired.1.21 If you are in possession of the goods you are under the duty to retain them and take reasonable care of them. You must send the goods back to us to our contact address at your own cost (unless we delivered the item to you in error or the item is damaged or defective) as soon as possible once you have cancelled the order.1.22 We reserve the right to make a charge not exceeding our direct costs of recovering the goods if you do not return the goods or return them at our expense.1.23 Once you have notified us that you wish to cancel the order, any sum debited to us will be refunded to you as soon as possible and in any event within 14 days of your cancellation.1.24 You will not have any right to cancel an order for the supply of any of the following goods:(a) medicinal products or services that are either dispensed on prescription or are available free under an NHS arrangement.(b) a contract for passenger transport services - such as bus, rail or flight tickets.(c) the supply of goods or services where prices are dependent upon fluctuations in the financial markets, which are beyond the control of the retailer.(d) the supply of goods that are made to the customer's specification or are clearly personalised.(e) the supply of goods that are liable to deteriorate or expire rapidly - such as a delivery of fresh flowers or meat.(f) the supply of newspapers, periodicals or magazines.(g) the supply of accommodation, transport of goods, vehicle rental services, catering or services related to leisure activities if the contract provides for a specific date or period of performance - for example, hotel bookings, courier services, car hire, restaurant bookings and theatre tickets for specific dates.1.25 In addition you will lose your right to cancel if you:(a) unseal goods that are not suitable for return if they are unsealed, due to health protection or hygiene reasons.(b) unseal audio, video recordings or computer software that were sealed at the time of delivery.(c) combine goods with other goods after delivery so that they become inseparable. Customer Reviews A4 Pubstops Yorkshire Dales Picture Item in Stock (9 Available) £18.95 Login to add this product to your wishlist. You Will Earn 18 points which is the equivalent of £0.18


text:
seems Artless | ||||||||||||
Edwards vines 1 :: June 18, 2007 | |||||||||||||
Back to Doors Open for a bit, and to vines on rough hewn stone. | |||||||||||||
Processed with Map this photo location | Filed under: Architecture :: Doors Open |
Today's Historic Toronto photos: I've geotagged and dated a bunch of historic photos from around Toronto. Click here to see photos from today's date in history. Or you can also see the set of historic photos by Toronto neighbourhoods here. | |||||||||||||
blog comments powered by Disqus | |||||||||||||
This work is licensed under a Creative Commons License by David Sky, 2004-2024.
(This photo Edwards vines 1 was taken at Edwards Gardens in Toronto, Ontario on 2007-05-27 ) ( Photo taken at 43.733460646925046, -79.35965538024902) Toronto map | wallpaper | photography guides |


text:
The Secret Life of Pets
Max (Louis C.K.) is a spoiled terrier who enjoys a comfortable life in a New York building until his owner adopts Duke, a giant and unruly canine. During their walk outside, they encounter a group of ferocious alley cats and wind up in a truck that's bound for the pound. Luckily, a rebellious bunny named Snowball swoops in to save the doggy duo from captivity. In exchange, Snowball demands that Max and Duke join his gang of abandoned pets on a mission against the humans who've done them wrong.
Louis C.K., Eric Stonestreet, Kevin Hart
Chris Renaud, Yarrow Cheney


text:
This dynamic Fish Planting Schedule is updated in real time, directly by CDFW Hatchery staff. Although it contains current information, all fish plants are subject to change depending on road, water, weather and operational conditions. Conditions permitting, the waters listed here will be restocked with catchable-size fish from CDFW hatcheries, according to this schedule. More specific dates are not given to avoid focusing excess fishing activity immediately after a plant.
If you have questions about Fish Planting activities, please call the Regional Office that covers the area in question.
See Fish Plants on a Map in our Fishing Guide
NOTE: The "Map It" links and resulting map markers do not indicate the exact or only planting locations, but rather the general location of the waters being planted.
Range of dates available for viewing: the current week, one week in the future, and six months in the past.


text:
Page tools: Print Page Print All | ||
This re-issue contains amended data for state and territory government expenditure on nature parks and reserves for the periods 2002-03 and 2003-04. Subsequent totals have also been amended, the updated figures are in Tables 1, 2 and 5. There are no amendments for the 2004-05 period.
Cultural Funding, By level of government - 2002-03 to 2004-05 The increase in funding by the Australian Government was primarily for Broadcasting and film, which received $1,096.5m in 2004-05 compared to $1,012.8m in 2003-04, an increase of $83.7m or 8.3%. Conversely, funding allocated to Other museums fell by $20.3m (10.0%) to $182.1m in 2004-05 from $202.4m in 2003-04.
STATE AND TERRITORY GOVERNMENT CULTURAL FUNDING, By value of funding - 2004-05 STATE AND TERRITORY GOVERNMENT CULTURAL FUNDING, By $ per person - 2004-05 RECURRENT AND CAPITAL EXPENDITURE Recurrent expenditure refers mainly to expenditure on wages and salaries, purchases of goods and services, and current grants and subsidies. In 2004-05, recurrent expenditure was $4,533.6m or 90.4% of total cultural funding. The Australian Government allocated $1,736.3m (98.6%) of its cultural funding towards recurrent activity, whereas state and territory governments provided $2,050.1m (87.0%) and local governments contributed $747.2m (83.2%).
Document Selection These documents will be presented in a new window. |


text:
Title: Waiting For My Queen
A Dark Mafia Romance
Author: Georgia Cates
Genre: Adult Dark Romance
Release Date: March 3, 2020
All I've
ever wanted was to marry for love.
But girls
like me don't have that luxury.
We are used
as pawns in a game we can't control.
The game?
It's called Mafia.
I was
foolish enough to try to change the rules… and I lost.
She was
promised to me years ago.
And he
dared to take her from me.
Dared to
touch what was mine.
I put an
end to that.
I hope he's
enjoying the view from his dirt room.
beloved's killer placed a ruby ring on my finger and called me his queen.
But that
red gem symbolizes something different for me.
represents the blood shed by those I love most.
Hell was
empty the day we wed.
Because the
devil was standing before me and said "I do."
I saw her
as a possession.
A shiny toy
I didn't want other boys to play with.
But she's
so much more.
and brave and strong and broken all at once.
She tastes
like everything I've ever wanted.
Hidden and
I wait for
the perfect time to seek my revenge.
But slowly,
I feel him possessing me.
His heart
is full of darkness… and I still want every inch of him.
Hard as I
try, I can't escape loving this beautiful monster.
I'm waiting
patiently because I already know that she's mine.
Mine in a
way that no one will ever understand.
Even if she
hasn't yet realized it.
For love,
I'd do anything.
For her,
I'd do everything.
Purchase Links
I focus my attention on the girl sitting to Sofia's left. The more
beautiful one. The older-looking one. The more frightened-looking one with
tears pooling in her lower lids.
Dark brown hair cascading over her shoulders and down her arms, the ends
nuzzling against her bare skin like a frightened child clinging to its mother.
Almond-shaped deep-caramel eyes surrounded by lush dark lashes. A few scattered
freckles across the bridge of her perfectly shaped nose. Plump, glossy coral
In my wildest dreams, my betrothed didn't grow up to be this beautiful.
And it annoys the hell out of me because I don't want to be attracted to her.
I want to make her suffer.
Sofia Bellini grips the hand of the girl in question. "Please, Marco.
Swear to me on your honor that my daughter will be safe with you."
My father chuckles. "Emilia is going to give us babies, heirs to the
Rossini empire. There is no safer place for her than with our family. You know
Sofia and the girl beside her, my Emilia, embrace one another and sob.
Her grandmother and sisters cluster around her doing the same. It's pathetic. I
would have expected less of a display from Bellinis. Certainly not this
My betrothed has weaknesses. Those will need to be eliminated before she
influences our sons with that nonsense.
"That's more than enough of that," I tell them.
She lifts her chin and her eyes meet mine for the first time. Inside
those deep-caramel orbs, I see something I like very much: rage. There during
one heartbeat and gone the next, it was only a fleeting flash. But I saw it and
I don't mistake it for what it is.
This girl is going to be so much fun to break.
"Come, Emilia. I'm ready to take you home."
Author Bio
resides in rural Mississippi with her wonderful husband, Jeff, and their two
beautiful daughters. She spent fourteen years as a labor and delivery nurse
before she decided to pursue her dream of becoming an author and hasn't looked
back yet.
When she's
not writing, she's thinking about writing. When she's being domestic, she's
listening to her music and visualizing scenes for her current work in progress.
Every story coming from her always has a song to inspire it.
Author Links


text: Home The Best Of Lake Norman is all about Lake Norman NC. We have pages for each town around the lake with links to websites of interest. There are pages of information about Lake Norman and live lake water temperature (updated ever 15 minutes). Our Fishing section has lots of information for beginners and experts alike. Our Birds / Waterfowl section has photos and information about various birds and waterfowl that is common (and some not so common) to Lake Norman, with more coming. We have sections for Clubs & Groups and a listing of Historical sites. We will be adding many items to each section as time allows. If there is something you would like to see added, E-mail Us.. Lake Norman on a cold winter day We also provide website hosting and website design services. Our servers run with a light load by design to enable your website to run fast. Our designers can develop the website you want. From basic to advanced sites. We have several options for advertising an existing website and advertising if you don't have a website. If you have any website need, CALL US! 704-660-7052 or E-mail Us. Lake Norman on a beautiful Fall Day


text: Assessment and Control at Parkview School: Qualitative Case Study of Accommodating Assessment (Chang Quantity in Basket:noneCode: 1-57273-035-8 Price:$22.95 Title: Assessment and Control at Parkview School Sub-title: A Qualitative Case Study of Accommodating Assessment Author(s): Chang Publish Date: 1996 Pages: 240 Format: Paper Quantity: This book investigates the process of implementation of externally imposed educational change. It's central core is a finely detailed empirical case study that offers insights into the meaning of educational change by coming to an understanding of the ideologies, values, and attitudes of key participants—a group of teachers who reveal why they act the way they do when faced with management directives to makes changes to their professional working practices. The theme of the book is articulated by the question that weaves through the study: How do individuals manage to retain a sense of freedom with constraints imposed on them? The approach adopted in this study shares the perspective known as policy ethnography which stresses the problematic nature of implementation, viewing it as an active process whereby individuals engaged in the act of implementation interpret, reinterpret, reform, and reconstruct the policy ideas when actively putting them into practice or into use.


text:
Description of Art, Floral Painting, Abstract Flower, Navy Blue Wall Art
An original modern abstract flower presents in shades of navy blue and gold yellow in this floral art painting.
All artwork © 2015 Catherine Jeltes, Gallery Zoo Art. All Rights Reserved.
PHOTOGRAPHS DO NOT DO THIS PAINTING JUSTICE. Colors are more vivid and more nuance of detail is visible in person. You will not be disappointed.
~TITLE: Abstract Flower Navy Blue Yellow 2
~MEDIUM: Acrylic
~GROUND: Archival Cotton Ragg Paper
~SIZE: 6 inches x 5 inches
~DEPTH: n/a
~READY TO HANG: NO. Frame and mat not included.
~SIGNATURE: YES. Signed and dated on the verso (back.)
* Painting is sprayed with a light matte varnish to protect from dust and UV light.
* SHIPPING: $7.00 included in price (Continental United States only.) Ships via USPS Priority Mail or USPS First Class International Package. Painting is protected in a plastic archival sleeve. Ships flat.
* INTERNATIONAL COLLECTORS: Please contact me for shipping charges to your country. Or if you wish to proceed with making a purchase as listed, I will send you a separate shipping invoice via PayPal for your approval prior to shipping your order. Your purchases ship USPS First Class International Package, unless Priority Mail is requested. Additional charges apply for this upgrade.
Each painting is an original, authentic piece of art created and signed by me.
Only professional grade acrylic paints, papers, and canvases are used.
Paintings are professionally packaged when shipped. Painting presents in a plastic archival sleeve.


text:
RFC 2772 - 6Bone Backbone Routing Guidelines
Network Working Group R. Rockell Request for Comments: 2772 Sprint Obsoletes: 2546 R. Fink Category: Informational ESnet February 2000 6Bone Backbone Routing Guidelines Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. Abstract The 6Bone is an Ipv6 testbed to assist in the evolution and deployment of IPv6. Because of this, it is important that the core backbone of the IPv6 network maintain stability, and that all operators have a common set of rules and guidelines by which to deploy IPv6 routing equipment. This document provides a set of guidelines for all 6bone routing equipment operators to use as a reference for efficient and stable deployment of 6bone routing systems. As the complexity of the 6Bone grows,the adherence to a common set of rules becomes increasingly important in order for an efficient, scalable backbone to exist. Table of Contents 1. Introduction.................................................. 2 2. Scope of this document........................................ 3 3. Common Rules for the 6bone.................................... 3 3.1 Link-local prefixes...................................... 3 3.2 Site-local prefixes...................................... 4 3.3 Loopback and unspecified prefixes........................ 5 3.4 Multicast prefixes....................................... 5 3.5 IPv4 compatible prefixes................................. 5 3.6 IPv4-mapped prefixes..................................... 6 3.7 Default routes........................................... 6 3.8 Yet undefined unicast prefixes........................... 6 3.9 Inter-site links......................................... 6 3.10 6to4 Prefixes........................................... 7 3.11 Aggregation & advertisement issues...................... 7 4. Routing Policies for the 6bone................................ 7 5. The 6Bone Registry............................................ 8 6. Guidelines for new sites joining the 6Bone.................... 9 7. Guidelines for 6Bone pTLA sites............................... 9 8. 6Bone Operations group........................................ 11 9. Common rules enforcement for the 6bone........................ 11 10. Security Considerations...................................... 12 11. References................................................... 12 12. Authors' Addresses........................................... 13 13. Full Copyright Statement..................................... 14 1. Introduction The 6Bone is an IPv6 testbed to assist in the evolution and deployment of IPv6. Because of this, it is important that the core backbone of the IPv6 network maintain stability, and that all operators have a common set of rules and guidelines by which to deploy IPv6 routing equipment. This document provides a set of guidelines for all 6bone routing equipment operators to use as a reference for efficient and stable deployment of 6bone routing systems. As the complexity of the 6Bone grows,the adherence to a common set of rules becomes increasingly important in order for an efficient, scalable backbone to exist. This document uses BGP-4 with Multiprotocol Extensions for BGP-4 as defined [RFC 2283], commonly referred to as BGP4+, as the currently accepted EGP. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119]. 2. Scope of this document This document is a best-practices Informational document aimed at IPv6 entities which operate under the 6Bone IPv6 testbed TLA allocation. 3. Common Rules for the 6bone This section details common rules governing the routing of the 6Bone. They are derived from the issues encountered on the 6Bone, with respect to the routes advertised, handling of special addresses, and aggregation: 1) link local prefixes 2) site local prefixes 3) loopback and unspecified prefixes 4) multicast prefixes 5) IPv4-compatible prefixes 6) IPv4-mapped prefixes 7) default routes 8) yet undefined unicast prefixes (from a different /3 prefix) 9) inter-site links issues 10) 6to4 prefixes 11) aggregation & advertisement issues 3.1 Link-local prefixes This link-local prefix (FE80::/10) MUST NOT be advertised through either an IGP or an EGP. Under no circumstance should this prefix be seen in the 6Bone backbone routing table. By definition, the link-local prefix has a scope limited to a specific link. Since the prefix is the same on all IPv6 links, advertising it in any routing protocol does not make sense and, worse, may introduce nasty error conditions. Well known cases where link-local prefixes could be advertised by mistake include, but are not limited to: - a router advertising all directly connected network prefixes including the link-local one - subnetting of the link-local prefix In such cases, vendors should be urged to correct their code. While vendors should be encouraged to fix the problem, the ultimate responsibility lies on the operator of that IPv6 site to correct the problem through whatever means necessary. Should a pTLA discover link-local prefixes coming from another pTLA, it is the responsibility of the pTLA leaking the routes to filter these, and correct the problem in a timely fashion. Should a pTLA discover that a downstream of that pTLA is leaking link-local prefixes, it is the pTLA's responsibility to ensure that these prefixes are not leaked to other pTLA's, or to other downstreams of that pTLA. Failure to filter such routes in a timely fashion may result in the manual shutting down of BGP4+ sessions to that pTLA, from other pTLA's. (Also, it is each pTLA, pNLA, and end-site's responsibility to not only filter their own BGP4+ sessions appropriately to peers, but to filter routes coming from peers as well, and to only allow those routes that fit the aggregation model, and do not cause operational problems). 3.2 Site-local prefixes Site local prefixes (in the FEC0::/10 range) MAY be advertised by IGP's or EGP's within a site. The precise definition of a site is ongoing work of the IPng working group, but should generally include a group of nodes that are operating under one administrator or group of administrators, or a group of nodes which are used for a common purpose. Site-local prefixes MUST NOT be advertised across transit pNLAs, pTLAs, or leaf-sites. Again, should site-local prefixes be leaked outside of a given site, it is the responsibility of the site to fix the problem in a timely manner, either through filters, or via other means which remove the operational impact that those prefixes had on the peering sites involved. However, every site SHOULD filter not only outbound on their EGP, but also inbound, in order to ensure proper routing announcements are not only sent, but also received. 3.3 Loopback and unspecified prefixes The loopback prefix (::1/128) and the unspecified prefix (::0/128) MUST NOT be advertised by any routing protocol. The same responsibility lies with the party guilty of advertising the loopback or unspecified prefix as in Section 3.1 and 3.2. 3.4 Multicast prefixes Multicast prefixes MUST NOT be advertised by any unicast routing protocol. Multicast routing protocols are designed to respect the semantics of multicast and MUST therefore be used to route packets with multicast destination addresses (in the range of FF00::/8). Multicast address scopes MUST be respected on the 6Bone. Only global scope multicast addresses MAY be routed across transit pNLAs and pTLAs. There is no requirement on a pTLA to route multicast packets at the time of the writing of this memo. Organization-local multicasts (in the FF08::/16 or FF18::/16 ranges) MAY be routed across a pNLA to its leaf sites. Site-local multicasts MUST NOT be routed toward transit pNLAs or pTLAs. Link-local multicasts and node-local multicasts MUST NOT be routed at all. 3.5 IPv4 compatible prefixes Sites may choose to use IPv4 compatible addresses (::a.b.c.d where a.b.c.d represents the octets of an IPv4 address) internally. As there is no real rationale today for doing so, these address SHOULD NOT be used or routed in the 6Bone. The ::/96 IPv4-compatible prefixes MAY be advertised by IGPs. IPv4 compatible prefixes MUST NOT be advertised by EGPs to transit pNLAs or pTLAs. Should ::/96 IPv4-compatible prefixes be leaked into an EGP, it is the responsibility of the party who is advertising the route to fix the problem, either through proper filters, or through other means, while it remains in the best interest of all particiapants of the 6Bone to filter both outbound and inbound at their IGP borders. 3.6 IPv4-mapped prefixes IPv4-mapped prefixes (::FFFF:a.b.c.d where a.b.c.d represents the octets of an IPv4 address) MAY be advertised by IGPs within a site. It may be useful for some IPv6 only nodes within a site to have such a route pointing to a translation device, to aid in deployment of IPv6. IPv4-mapped prefixes MUST NOT be advertised by EGPs. 3.7 Default routes 6Bone core pTLA routers MUST be default-free. pTLAs MAY advertise a default route to any downstream peer (non-pTLA site). Transit pNLAs MAY advertise a default route to any of their downstreams (other transit pNLA or leaf site). Should a default route be redistributed into an EGP and found on any pTLA EGP sessions, it is the responsibility of the pTLA to fix this problem immediately upon realization of the route's existence, and the responsibility of the guilty pTLA to push the entity from which the default route was originated, should the default route have originated from downstream of a pTLA. 3.8 Yet undefined unicast prefixes Yet undefined unicast prefixes from a format prefix other than 2000::/3 MUST NOT be advertised by any routing protocol in the 6Bone. In particular, RFC 2471 test addresses MUST NOT be advertised on the 6Bone. Routing of global unicast prefixes outside the 6Bone range (3ffe::/16), and routing of global unicast prefixes yet undelegated in the range (3ffe::/16) are discussed in section 4, Routing policies, below. 3.9 Inter-site links Global IPv6 addresses must be used for the end points of inter-site links. In particular, IPv4 compatible addresses MUST NOT be used for tunnels. Sites MAY use Other addressing schemes for Inter-site links, but these addresses MUST NOT be advertised into the IPv6 global routing table. Prefixes for inter-site links MUST NOT be injected in the global routing tables. 3.10 6to4 Prefixes The 6to4 prefix, or some portion thereof, MAY be announced by any pTLA which has a current implementation of 6to4 in their IPv6 network. However, as 6to4 implementors gain more operational experience, it MAY be necessary to change this in some way. At the time of the writing of this docuement, any pTLA MAY announce the 6to4 prefix into global EBGP. However, in order to announce this block, the pTLA MUST have a 6to4 router active, sourcing this prefix announcement. This section subject to change, and MAY vary, depending on 6to4 progress within the NGTRANS working group. 3.11 Aggregation & advertisement issues Route aggregation MUST be performed by any border router talking EGP with any other IPv6 sites. More-specifics MUST NOT be leaked into or across the IPv6 6Bone backbone. 4. Routing Policies for the 6bone Leaf sites or pNLAs MUST only advertise to an upstream provider the prefixes assigned by that provider. Advertising a prefix assigned by another provider to a provider is not acceptable, and breaks the aggregation model. A site MUST NOT advertise a prefix from another provider to a provider as a way around the multi-homing problem. However, in the interest of testing new solutions, one may break this policy, so long as ALL affected parties are aware of this test, and all agree to support this testing. These policy breaks MUST NOT affect the 6bone routing table globally. To clarify, if one has two upstream pNLA or pTLA providers, (A and B for this example), one MUST only announce the prefix delegated to one by provider A to provider A, and one MUST only announce the prefeix delegated by one from provider B upstream to provider B. There exists no circumstance where this should be violated, as it breaks the aggregation model, and could globally affect routing decisions if downstreams are able to leak other providers' more specific delegations up to a pTLA. As the IPNG working group works through the multi-homing problem, there may be a need to alter this rule slightly, to test new strategies for deployment. However, in the case of current specifications at the time of this writing, there is no reason to advertise more specifics, and pTLA's MUST adhere to the current aggregation model. Site border routers for pNLA or leaf sites MUST NOT advertise prefixes more specific (longer) than the prefix that was allocated by their upstream provider. All 6bone pTLAs MUST NOT advertise prefixes longer than a given pTLA delegation (currently /24 or /28) to other 6bone pTLAs unless special peering arrangements are implemented. When such special peering aggreements are in place between any two or more 6bone pTLAs, care MUST be taken not to leak the more specifics to other 6bone pTLAs not participating in the peering aggreement. 6bone pTLAs which have such agreements in place MUST NOT advertise other 6bone pTLA more specifics to downstream 6bone pNLAs or leaf sites, as this will break the best-path routing decision. The peering agreements across the 6Bone may be by nature non- commercial, and therefore MAY allow transit traffic, if peering agreements of this nature are made. However, no pTLA is REQUIRED to give or receive transit service from another pTLA. Eventually, the Internet registries will assign prefixes under other than the 6Bone TLA (3FFE::/16). As of the time this document was written in 1999, the Internet registries were starting to assign /35 sub-TLA (sTLA) blocks from the 2001::/16 TLA. Others will certainly be used in the future. The organizations receiving prefixes under these newer TLAs would be expected to want to establish peering and connectivity relationships with other IPv6 networks, both in the newer TLA space and in the 6bone pTLA space. Peering between new TLA's and the current 6Bone pTLA's MAY occur, and details such as transit, and what routes are received by each, are outside of general peering rules as stated in this memo, and are left up to the members of those TLA's and pTLA's that are establishing said peerings. However, it is expected that most of the rules discussed here are equally applicable to new TLAs. 5. The 6Bone Registry The 6Bone registry is a RIPE-181 database with IPv6 extensions used to store information about the 6Bone, and its sites. The 6bone is accessible at: <http://www.6bone.net/whois.html>) Each 6Bone site MUST maintain the relevant entries in the 6Bone registry. In particular, the following object MUST be present for all 6Bone leaf sites, pNLAs and pTLAs: - IPv6-site: site description - Inet6num: prefix delegation (one record MUST exist for each delegation) - Mntner: contact info for site maintance/administration staff. Other object MAY be maintained at the discretion of the sites such as routing policy descriptors, person, or role objects. The Mntner object MUST make reference to a role or person object, but those MAY NOT necessarily reside in the 6Bone registry. They can be stored within any of the Internet registry databases (ARIN, APNIC, RIPE-NCC, etc.) 6. Guidelines for new sites joining the 6Bone New sites joining the 6Bone should seek to connect to a transit pNLA or a pTLA within their region, and preferably as close as possible to their existing IPv4 physical and routing path for Internet service. The 6Bone web site at <http://www.6bone.net> has various information and tools to help find candidate 6bone networks. Any site connected to the 6Bone MUST maintain a DNS server for forward name lookups and reverse address lookups. The joining site MUST maintain the 6Bone objects relative to its site, as describe in section 5. The upstream provider MUST delegate the reverse address translation zone in DNS to the joining site, or have an agreement in place to perform primary DNS for that downstream. The provider MUST also create the 6Bone registry inet6num object reflecting the delegated address space. Up to date informatino about how to join the 6Bone is available on the 6Bone Web site at <http://www.6bone.net>. 7. Guidelines for 6Bone pTLA sites The following rules apply to qualify for a 6Bone pTLA allocation. It should be recognized that holders of 6Bone pTLA allocations are expected to provide production quality backbone network services for the 6Bone. 1. The pTLA Applicant must have a minimum of three (3) months qualifying experience as a 6Bone end-site or pNLA transit. During the entire qualifying period the Applicant must be operationally providing the following: a. Fully maintained, up to date, 6Bone Registry entries for their ipv6-site inet6num, mntner, and person objects, including each tunnel that the Applicant has. b. Fully maintained, and reliable, BGP4+ peering and connectivity between the Applicant's boundary router and the appropriate connection point into the 6Bone. This router must be IPv6 pingable. This criteria is judged by members of the 6Bone Operations Group at the time of the Applicant's pTLA request. c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) entries for the Applicant's router(s) and at least one host system. d. A fully maintained, and reliable, IPv6-accessible system providing, at a mimimum, one or more web pages, describing the Applicant's IPv6 services. This server must be IPv6 pingable. 2. The pTLA Applicant MUST have the ability and intent to provide "production-quality" 6Bone backbone service. Applicants must provide a statement and information in support of this claim. This MUST include the following: a. A support staff of two persons minimum, three preferable, with person attributes registered for each in the ipv6-site object for the pTLA applicant. b. A common mailbox for support contact purposes that all support staff have acess to, pointed to with a notify attribute in the ipv6-site object for the pTLA Applicant. 3. The pTLA Applicant MUST have a potential "user community" that would be served by its becoming a pTLA, e.g., the Applicant is a major provider of Internet service in a region, country, or focus of interest. Applicant must provide a statement and information in support this claim. 4. The pTLA Applicant MUST commit to abide by the current 6Bone operational rules and policies as they exist at time of its application, and agree to abide by future 6Bone backbone operational rules and policies as they evolve by consensus of the 6Bone backbone and user community. When an Applicant seeks to receive a pTLA allocation, it will apply to the 6Bone Operations Group (see section 8 below) by providing to the Group information in support of its claims that it meets the criteria above. 8. 6Bone Operations Group The 6Bone Operations Group is the group in charge of monitoring and policing adherence to the current rules. Membership in the 6Bone Operations Group is mandatory for, and restricted to, sites connected to the 6Bone. The 6Bone Operations Group is currently defined by those members of the existing 6Bone mailing list who represent sites participating in the 6Bone. Therefore it is incumbent on relevant site contacts to join the 6Bone mailing list. Instructions on how to join the list are maintained on the 6Bone web site at < http://www.6bone.net>. 9. Common rules enforcement for the 6bone Participation in the 6Bone is a voluntary and benevolent undertaking. However, participating sites are expected to adhere to the rules and policies described in this document in order to maintain the 6Bone as a quality tool for the deployment of, and transition to, IPv6 protocols and the products implementing them. The following is in support of policing adherence to 6Bone rules and policies: 1. Each pTLA site has committed to implement the 6Bone's rules and policies, and SHOULD try to ensure they are adhered to by sites within their administrative control, i.e. those to who prefixes under their respective pTLA prefix have been delegated. 2. When a site detects an issue, it SHOULD first use the 6Bone registry to contact the site maintainer and work the issue. 3. If nothing happens, or there is disagreement on what the right solution is, the issue SHOULD be brought to the 6Bone Operations Group. 4. When the problem is related to a product issue, the site(s) involved SHOULD be responsible for contacting the product vendor and work toward its resolution. 5. When an issue causes major operational problems, backbone sites SHOULD decide to temporarily set filters in order to restore service. 10. Security Considerations The result of incorrect entries in routing tables is usually unreachable sites. Having guidelines to aggregate or reject routes will clean up the routing tables. It is expected that using these rules and policies, routing on the 6Bone will be less sensitive to denial of service attacks due to misleading routes. The 6Bone is an IPv6 testbed to assist in the evolution and deployment of IPv6. Therefore, denial of service or packet disclosure are to be expected. However, it is the pTLA from where the attack originated who has ultimate responsibility for isolating and fixing problems of this nature. It is also every 6Bone site's responsibility to safely introduce new test systems into the 6Bone, by placing them at a strategically safe places which will have minimal impact on other 6Bone sites, should bugs or misconfigurations occur. 11. References [RFC 2373] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 2373, July 1998. [RFC 2471] Hinden, R., Fink, R. and J. Postel, "IPv6 Testing Address Allocation", RFC 2471, December 1998. [RFC 2546] Durand, A. and B. Buclin, "6Bone Routing Practice", RFC 2546, March 1999 [RFC 2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080, January 1997. [RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC 2283] Bates, T., Chandra, R., Katz, D. and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 2283, March 1998. [RIPE-181] Bates, T., Gerich, E., Joncheray, L., Jouanigot, J., Karrenberg, D., Terpstra, M. and J. Yu, Representation of IP Routing Policies in a Routing Registry. Technical Report ripe-181, RIPE, RIPE NCC, Amsterdam, Netherlands, October 1994. 12. Authors' Addresses Rob Rockell EMail: email@example.com Bob Fink EMail: firstname.lastname@example.com 13. Full Copyright Statement Copyright (C) The Internet Society (2000). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. User Contributions:Comment about this RFC, ask questions, or add new information about this topic: |


text:
What's New in Datamarts – August 2022
Hear about the latest updates to Datamart in Power BI since the //Build announcement
» Devamını okuyunHear about the latest updates to Datamart in Power BI since the //Build announcement
» Devamını okuyunToday, we are excited to announce the public preview of Multiple Audiences in the Power BI Apps, one of the highly requested features from the community. With multiple audiences for an App, now Power BI App author can create multiple audience groups within the same App and assign different permissions to each group.
» Devamını okuyunThis month's Power BI Dev Camp session provides a quick primer on modern React-JS development and demonstrates how to create an SPA application with React-JS which calls the Power BI REST API and implements User-Owns-Data embedding.
» Devamını okuyunData loss prevention (DLP) policies help you govern the sensitive information managed in your Power BI tenant and comply with governmental or industry regulations, such as GDPR (the European Union's General Data Protection Regulation). Earlier this year, we announced the release of DLP policies for Power BI to public preview. We're happy to share with you two significant enhancements to DLP policies in Power BI: CPU metering for DLP policy evaluation, ability to override DLP policy tips and option to report of a false positive detection.
» Devamını okuyunWe are committed to helping our Azure Analysis Services customers unlock the enormous capabilities of Power BI as a superset of Azure Analysis Services through a smooth migration path to Power BI. As part of this effort, we are happy to announce today that Power BI has reached yet another compatibility milestone with the introduction of explicit Dataset Write permissions.
» Devamını okuyunPostgreSQL connector now available through the virtual network data gateway!
» Devamını okuyunWelcome to the August 2022 update. Can you imagine it's the last month of summer already? We are excited to announce a variety of new features such as the conditional formatting for data labels, new "Select sensitivity label" dialog, data loss prevention policy update and DAX editor improvements. There is more to explore, please continue to read on.
» Devamını okuyunThis post is an overview of the improvements made to Datamart's Visual and SQL Query editor, which is currently in Public Preview.
» Devamını okuyunThe first annual Power Platform Conference sponsored by Microsoft and Power Platform Conference is coming to Orlando for an amazing in-person event this September, with keynotes, sessions, breakouts and more! All dedicated to Microsoft Power Platform products: Power BI, Power Automate, Power Apps, Power Pages, and Power Virtual Agents.
» Devamını okuyunThe Power BI app for Microsoft Teams is coming to Teams mobile. This helps users stay up to date and never miss activity in their Power BI reports and scorecards.
» Devamını okuyun


text:
Shell announces the completion of the transaction to separate Motiva assets
May 1, 2017 – Royal Dutch Shell plc ("Shell") announces today the completion of the transaction for the separation of assets, liabilities and businesses of Motiva Enterprises LLC ("Motiva").
As announced when the definitive agreements were signed, the separation is as follows:
- Saudi Aramco (through its wholly owned Saudi Refining, Inc. subsidiary) assumes full ownership of the Motiva Enterprises LLC name and legal entity, including the refinery at Port Arthur, Texas and 24 distribution terminals. Additionally, Motiva has the right to exclusively sell Shell-branded gasoline and diesel in Georgia, North Carolina, South Carolina, Virginia, Maryland and Washington, D.C., as well as the eastern half of Texas and the majority of Florida.
- Shell (through various affiliated companies) assumes sole ownership of the Norco, LA., refinery (where Shell operates a chemicals plant), the Convent, La., refinery, 11 distribution terminals, and Shell-branded markets in Alabama, Mississippi, Tennessee, Louisiana, a portion of the Florida panhandle, and the North-eastern region of the U.S. These assets are now fully integrated with Shell's downstream business in North America.
About Shell
Royal Dutch Shell plc, a global group of energy and petrochemical companies with operations in more than 70 countries. In the U.S., Shell operates in 50 states and employs more than 20,000 people.
Cautionary note
The companies in which Royal Dutch Shell plc directly and indirectly owns investments are separate legal entities. In this announcement "Shell", "Shell group" and "Royal Dutch Shell" are sometimes used for convenience where references are made to Royal Dutch Shell plc and its subsidiaries in general. Likewise, the words "we", "us" and "our" are also used to refer to subsidiaries in general or to those who work for them. These expressions are also used where no useful purpose is served by identifying the particular company or companies.''Subsidiaries'', "Shell subsidiaries" and "Shell companies" as used in this announcement refer to companies over which Royal Dutch Shell plc either directly or indirectly has control. Entities and unincorporated arrangements over which Shell has joint control are generally referred to as "joint ventures" and "joint operations" respectively. Entities over which Shell has significant influence but neither control nor joint control are referred to as "associates". The term "Shell interest" is used for convenience to indicate the direct and/or indirect ownership interest held by Shell in a venture, partnership or company, after exclusion of all third-party interest.
This announcement contains forward-looking statements concerning the financial condition, results of operations and businesses of Royal Dutch Shell. All statements other than statements of historical fact are, or may be deemed to be, forward-looking statements. Forward-looking statements are statements of future expectations that are based on management's current expectations and assumptions and involve known and unknown risks and uncertainties that could cause actual results, performance or events to differ materially from those expressed or implied in these statements. Forward-looking statements include, among other things, statements concerning the potential exposure of Royal Dutch Shell to market risks and statements expressing management's expectations, beliefs, estimates, forecasts, projections and assumptions. These forward-looking statements are identified by their use of terms and phrases such as ''anticipate'', ''believe'', ''could'', ''estimate'', ''expect'', ''goals'', ''intend'', ''may'', ''objectives'', ''outlook'', ''plan'', ''probably'', ''project'', ''risks'', "schedule", ''seek'', ''should'', ''target'', ''will'' and similar terms and phrases. There are a number of factors that could affect the future operations of Royal Dutch Shell and could cause those results to differ materially from those expressed in the forward-looking statements included in this announcement, including (without limitation): (a) price fluctuations in crude oil and natural gas; (b) changes in demand for Shell's products; (c) currency fluctuations; (d) drilling and production results; (e) reserves estimates; (f) loss of market share and industry competition; (g) environmental and physical risks; (h) risks associated with the identification of suitable potential acquisition properties and targets, and successful negotiation and completion of such transactions; (i) the risk of doing business in developing countries and countries subject to international sanctions; (j) legislative, fiscal and regulatory developments including regulatory measures addressing climate change; (k) economic and financial market conditions in various countries and regions; (l) political risks, including the risks of expropriation and renegotiation of the terms of contracts with governmental entities, delays or advancements in the approval of projects and delays in the reimbursement for shared costs; and (m) changes in trading conditions. No assurance is provided that future dividend payments will match or exceed previous dividend payments. All forward-looking statements contained in this announcement are expressly qualified in their entirety by the cautionary statements contained or referred to in this announcement. Readers should not place undue reliance on forward-looking statements. Additional risk factors that may affect future results are contained in Royal Dutch Shell's 20-F for the year ended December 31, 2016 (available at www.shell.com/investor and www.sec.gov). These risk factors also expressly qualify all forward looking statements contained in this announcement and should be considered by the reader. Each forward-looking statement speaks only as of the date of this announcement, May 1, 2017. Neither Royal Dutch Shell plc nor any of its subsidiaries undertake any obligation to publicly update or revise any forward-looking statement as a result of new information, future events or other information. In light of these risks, results could differ materially from those stated, implied or inferred from the forward-looking statements contained in this announcement.
We may have used certain terms, such as resources, in this announcement that United States Securities and Exchange Commission (SEC) strictly prohibits us from including in our filings with the SEC. U.S. Investors are urged to consider closely the disclosure in our Form 20-F, File No 1-32575, available on the SEC website www.sec.gov
SOURCE: Shell