The Mother of All Windows 98 Books, 1st edition
Authors: Woody Leonhard, Barry Simon
Venue:  (1998)

From the Book:ISBN: 0201485583 TITLE: The Java Tutorial Continued SUBTITLE: The Rest of the JDK AUTHOR: Campione, Mary AUTHOR: Walrath, Kathy AUTHOR: Huml, Alison AUTHOR: Tutorial Team TABLE OF CONTENTS: Preface Overview of JDK Features LESSON 1 A Day in the Life LESSON 2 All Things New with JDK 1.2 LESSON 3 Features Roadmap Collections LESSON 4 Introduction LESSON 5 Interfaces LESSON 6 Implementations LESSON 7 Algorithms LESSON 8 Custom Implementations LESSON 9 Interoperability Working with Java 2D Graphics LESSON 10 Overview of the Java 2D API LESSON 11 Displaying Graphics with Graphics2D LESSON 12 Manipulating and Displaying Images LESSON 13 Printing Java Sound LESSON 14 Playing Sounds LESSON 15 Java Sound Engine Integration LESSON 16 Common Problems (and Their Solutions JavaBeans: Java Platform Components LESSON 17 JavaBeans Concepts and Development Kit LESSON 18 Using the BeanBox LESSON 19 Writing a SimpleBean LESSON 20 Properties LESSON 21 Manipulating Events in the BeanBox LESSON 22 The BeanInfo Interface LESSON 23 Bean Customization LESSON 24 Bean Persistence JDBC Database Access LESSON 25 JDBC LESSON 26 New Features in the JDBC 2.0 API Programming with Java IDL LESSON 27 Introducing Java IDL LESSON 28 The Hello Client-Server Example LESSON 29 Java IDL Summary Using Java RMI LESSON 30 An Overview of RMI Applications LESSON 31 Writing an RMI Server LESSON 32 Creating A Client Program LESSON 33 Compiling and Running the Example Servlets LESSON 34 Overview of Servlets LESSON 35 Interacting with Clients LESSON 36 The Life Cycle of a Servlet LESSON 37 Saving Client State LESSON 38 The servletrunner Utility LESSON 39 Running Servlets Security LESSON 40 Security Features Overview LESSON 41 Quick Tour of Controlling LESSON 42 Quick Tour of Controlling Applications LESSON 43 Secure Code and File LESSON 44 Tools to Sign Code and Grant Permissions LESSON 45 Tools for Exchanging LESSON 46 Generating and Verifying Signatures LESSON 47 Implementing Your Own Permission The Java Archive (JAR) File Format LESSON 48 Using JAR Files: The Basics LESSON 49 Signing and Verifying JAR LESSON 50 Using JAR-Related APIs Introduced in 1.2 The Java Extension Mechanism LESSON 51 Creating and Using LESSON 52 Setting Extension Security Privileges Using the Java Native Interface LESSON 53 Overview of the LESSON 54 Writing a Java Program with Native Methods LESSON 55 Integrating Java and Native Programs LESSON 56 Interacting with Java from the Native Side LESSON 57 Invoking the Java Virtual Machine LESSON 58 Summary of the JNI The Reflection API LESSON 59 Examining Classes LESSON 60 Manipulating Objects LESSON 61 Working with Arrays LESSON 62 Summary of Classes Reference Objects LESSON 63 Understanding Garbage Collection LESSON 64 All About Reference Objects Appendixes Appendix A: Code Examples Appendix B: Reference Index END ISBN: 0201309505 TITLE: Network Application Frameworks SUBTITLE: Design and Architecture AUTHOR: Greenberg, Eric TABLE OF CONTENTS: Preface Can Really Cover All That? Book Organization Acknowledgments and Reflections Chapter 1 What a Network Application Framework? 1.1 Introduction 1.2 Object Technology and Distributed Objects 1.2.1 The Study Object-Oriented Concepts and Component Models 1.2.2 Categories Object Technology 1.2.3 Object Terminology and Concepts 1.3 Directory Services 1.3.1 Characteristics Directory Services 1.3.2 Directory Services and the Network 1.4 Transaction Services 1.5 Security Services 1.6 Networking Services 1.6.1 Retransmission and Flow Control 1.6.2 Byte Overhead 1.6.3 Character Echo 1.6.4 Packet Size and Queuing 1.7 Application Programming Interfaces (APIs) and Development Platform Services 1.8 File- and Printer-Sharing Services 1.9 Conclusions Chapter 2 Core Network Application Framework Technologies 2.1 Introduction 2.2 Core Security Technologies 2.2.1 Public Key Cryptography 2.2.2 Secure Sockets Layer (SSL) and Transport Layer Security (TLS) Protocols 2.2.3 -Level Security (IPSEC) 2.2.4 Kerberos 2.3 Remote Procedure Call (RPC) 2.3.1 Application Development Concerns 2.3.2 Standard RPC Implementations 2.3.3 Data Representation 2.3.4 Transactional RPC (TxRPC) 2.3.5 Security 2.3.6 API Programming 2.4 Common Object Request Broker Architecture (CORBA): Awakening the Object Web 2.4.1 Introduction CORBA 2.4.2 Interfaces: Standardizing Information Passing Between Objects 2.4.3 Hop the Object Bus: The Object Request Broker (ORB) 2.4.4 Static Versus Dynamic Object Discovery 2.4.5 Distributed Object Communication: Inter-ORB Standards and IIOP 2.4.6 CORBA Value-Added Services 2.4.7 CORBA Versus RPC 2.5 X.500 and Lightweight Directory Access Protocol Version 3 (LDAPv3) 2.5.1 X.500 2.5.2 LDAPv3 2.6 Conclusions Chapter 3 The TCP/ Protocol Suite 3.1 Introduction 3.2 TCP, and UDP 3.2.1 Detail 3.2.2 TCP Detail 3.2.3 UDP Detail 3.3 Application Design 3.4 TCP and UDP Security and WAN Efficiency 3.5 Protocol Security: A Closer Look 3.5.1 Tapping and Sniffing 3.5.2 TFTP and Security 3.5.3 BOOTP/DHCP and Security 3.5.4 DNS and Security 3.5.5 SNMP and Security 3.6 Efficiency: A Closer Look 3.6.1 TELNET and Efficiency 3.6.2 X-Terminal and Efficiency 3.6.3 TFTP and Efficiency 3.6.4 SNMP and Efficiency 3.7 The World Internet Addressing 3.7.1 Subnet Masks: Organizing Your Network Address Space 3.7.2 Variable-Length Subnet Masks (VLSM): Conserving Your Address Space 3.8 Conclusions Chapter 4 Routing 4.1 Introduction 4.2 The Autonomous System (): Keeping Things Separate 4.3 Fundamental Routing Characteristics 4.4 Address Resolution Protocol (ARP) 4.4.1 ARP Example 4.5 Internet Control Message Protocol (ICMP) for IPv4 4.6 Routing Protocols 4.6.1 Routing Information Protocol Version 1 (RIPv1) 4.6.2 Routing Information Protocol Version 2 (RIPv2) 4.6.3 Open Shortest Path First (OSPF) Protocol 4.6.4 Interior Gateway Routing Protocol (IGRP) and Enhanced Gateway Routing Protocol (EIGRP) 4.6.5 Border Gateway Protocol 4 (BGP-4) 4.7 Conclusions Chapter 5 Internet Protocol Version 6 (IPv6) 5.1 Introduction 5.2 Datagram Header Format and Options 5.2.1 The Minimum IPv6 Header 5.2.2 Extension Headers 5.3 Addressing 5.3.1 Hexadecimal Representation 5.3.2 Structure and Assignment 5.4 Autoconfiguration 5.5 Address Resolution 5.6 Impact Applications 5.7 IPv4/IPv6 Migration and Interoperability 5.8 Conclusions Chapter 6 The Open Group Distributed Computing Environment (DCE) 6.1 Introduction 6.2 DCE: Not Necessarily Operating System 6.3 DCE Security Service 6.3.1 Tickets and PACs 6.3.2 Security Database 6.3.3 Security API 6.4 DCE Directory Service 6.5 DCE File Service (DFS) 6.6 DCE Time Service (DTS) 6.7 DCE Threads 6.7.1 A Platform-Independent API 6.7.2 Threads Application Development 6.8 DCE and CORBA 6.9 DCE Interoperability 6. Conclusions Chapter 7 Microsoft and WOSA 7.1 Introduction 7.1.1 Vision 7.1.2 Components the Microsoft Network Application Framework 7.2 Service Provider Interface (SPI) Architecture 7.3 Multitasking, Synchronization, and Threads 7.4 Local Interprocess Communication 7.5 Networking 7.5.1 Transports 7.5.2 Remote Interprocess Communication 7.5.3 WNet( ) APIs 7.5.4 NetBIOS 7.5.5 Berkeley (BSD) Sockets and Windows Sockets Specification (WinSock) 7.6 Open Database Connectivity (ODBC) 7.7 Messaging API (MAPI) 7.7.1 Simple Microsoft Messaging API (MAPI) 7.7.2 Common Messaging Call (CMC) 7.7.3 Extended MAPI 7.8 Telephony API (TAPI) 7.9 Microsoft Distributed Object Framework 7.9.1 Evolution COM: The Art All That "X" 7.9.2 COM Wrapping: Microsoft Interface Definition Language (MIDL) 7.9.3 COM: A Binary Standard 7.9.4 ActiveX Security 7.9.5 Containers 7.9.6 COM, Clustering, and Middleware 7.9.7 Microsoft Message Queue Server (MSMQ) 7.9.8 Distributed COM (DCOM): COM with a Longer Wire 7.9.9 COM+ 7.10 Microsoft Transaction Server (MTS): Managing Objects the Enterprise 7.10.1 MTS Services and Architecture 7.10.2 MTS and Object Pooling 7.10.3 MTS and Object Creationism 7.10.4 MTS and Object Security7 7.11 COM Transaction Integrator for CICS and IMS (Cedar): Integrating with SNA/Mainframe Technology 7.12 COM, CORBA, and JavaBeans: Friendly Fire and Interoperability 7.12.1 COM Versus Java RMI Versus CORBA 7.12.2 COM/CORBA Interoperability 7.13 Universal Data Architecture (UDA), ActiveX Data Objects (ADO), and OLE- 7.14 Internationalization 7.15 Conclusions Chapter 8 The 4 Directory Service 8.1 Introduction 8.2 Directory Structure 8.3 The Application Groups Within Domains 8.4 Domains More Detail 8.5 Domains and Groups 8.6 Access Control Lists 8.7 Trust Management 8.8 Directionality Trust and Human Relationships 8.9 Summary Design Rules 8.10 Directory Service Topologies 8.10.1 Single Domain 8.10.2 Single Master Domain 8.10.3 Multiple Master Domain 8.10.4 Complete Trust 8.11 Interoperability and Migration 8.12 Conclusions Chapter 9 5 Active Directory Services 9.1 Introduction 9.2 Standards Supported 9.2.1 DNS 9.2.2 Kerberos and SSPI 9.2.3 X.500 9.2.4 ADSI, LDAP, and MAPI 9.3 Directory Structure 9.4 Objects, Users, Groups, Resources, and OUs 9.5 Naming, Domains, and Trees 9.6 Kerberos: Guarding the "Forest" 9.7 The Global Catalogue: Make Snappy 9.7 Domain Controllers 9.9 Name Interference 9.10 Trust Management 9.11 Interoperability and Migration 9.12 Conclusions Chapter 10 Novell NetWare 10.1 Introduction 10.2 NetWare 3.x 10.2.1 Core Protocols and Functions 10.2.2 Internetwork Packet Exchange (IPX) 10.2.3 Sequenced Packet Exchange (SPX) 10.2.4 Service Advertisement Protocol (SAP) and the Bindery: Precursor a Directory 10.2.5 Routing Protocols: RIP, NLSP, and EIGRP 10.2.6 NetWare Core Protocol (NCP) 10.2.7 Application Development 10.3 NetWare 4.x/IntraNetWare 10.4 NetWare Directory Services (NDS) 10.4.1 Containers and Leaf Objects: Organizing People, Resources, and Services 10.4.2 Trust Management and Inherited Rights Filter (IRF) 10.4.3 Security: Authentication and Authorization 10.4.4 Partitions and Replicas: Designing for Reliability and Performance 10.4.5 NDS for : Integrating with Microsoft Domains 10.4.6 LDAP Services for NDS 10.5 NetWare 3.x/4.x Integration with TCP/ 10.6 NetWare and IBM SNA Integration 10.7 NetWare 5: The Dawn Native TCP/ over NetWare 10.8 Modern Novell Application Development: Java, CORBA, and the Directory Service 10.9 Conclusions Chapter 11 IBM 11.1 Introduction 11.2 IBM Time Line and Computer Systems Overview 11.2.1 The Time Line 11.2.2 Processors and Architectures 11.2.3 Mainframe Operating Systems and Applications 11.2.4 Mainframe Access with Terminals 11.3 SNA Components: Physical Units and Logical Units 11.4 The Systems Network Architecture (SNA) Layered Model 11.5 IBM Networking 11.5.1 The First Networking Intelligence Assumption: The Desktop Has None 11.5.2 Making Dynamic: APPN 11.5.3 Networking Media and Methods 11.6 IBM Transaction Series Systems: The Customer Information Control System (CICS) 11.7 11.7 Integrating CICS with the Web 11.7.1 CICS Gateway for Java 11.7.2 CICS Internet Gateway 11.8 The IBM 3270 Java Emulator 11.9 Conclusions Chapter 12 Design Rule Summary 12.1 Introduction 12.2 Tables Index EXCERPT: PREFACE: Writing a book is an adventure. To begin with, it is a toy and an amusement; then it becomes a mistress, and then it becomes a master, and then a tyrant. The last phase is that, just as you are about to be reconciled with your servitude, you kill the monster, and fling him out to the public.Winston Churchill This book provides a comprehensive road map for understanding the design, architecture, and inherent integrated nature of modern and legacy networking and application technologies. The audience for this book includes IS managers, systems engineers, software designers, network engineers, system administrators, network managers, systems architects, senior technologists, and senior management. By reading this book, you will be introduced to a wide range of highly relevant enterprise networking and application technologies. Armed with this knowledge, you will be able to design new systems that better meet functional, performance, and operational objectives. For existing deployments, your ability to isolate poor performance to either the network, the application, or both will be improved. In addition, you will be able to design networks and applications that more seamlessly and efficiently integrate legacy technologies with modern ones. To understand the purpose of this book, let's consider the following scenario: The company's sales staff has called a meeting with the Information Systems (IS) department to discuss the increasingly poor performance of their worldwide sales processing application. The IS group has brought the folks responsible for the network to the meeting as well. The networking people blame the application developer arguing the application must be at fault and vice versa, the developer claims the network is slow. Furthermore, there's a desire to integrate the sales processing application with other corporate systems, and there's confusion and disagreement on exactly how to achieve that. The networking people claim the systems cannot be integrated due to differing incompatible protocols, and the application folks want to rewrite everything but don't have the time or resources for that approach. Problems like these have existed for years, but we are now entering a new era in which less and less tolerance exists for this isolated approach to network and application design. Distributed object technology, directory services information embedded within the network, vast connectivity, a huge base of older legacy technology that must be further integrated, and a host of other technologies we'll discuss in this book are producing a tighter coupling between the network and its applications. This means that our old habits of separating network and application design, which never worked well anyway, will no longer work at all. The functionality, efficiency, performance, reliability, and security of the network and its applications are so inter-twined, that designing them in isolation will repeatedly result in networks and applications that miss the mark in too many ways-- over budget, underperforming, poorly integrated, and too expensive to maintain. As a result, there's a growing need for technical professionals to understand how both networks and applications behave together, as one. Like those systems-level hardware designers that are more concerned with how chips and boards work together than they are transistors and capacitors, there's a need to look at the design problem from a higher level of abstraction. In this new tightly coupled era, one of the greatest challenges is the integration of existing (legacy) technologies with open multiplatform standards-based ones. To ignore what is installed across the enterprise today and just speak of what's new is to be unrealistic. This book places heavy emphasis on the understanding of legacy technologies and their role as part of an integrated heterogeneous open standards-based networking and application environment. Can We Really Cover All That? It's fair to ask ourselves this question. With all the information explored in this book, and its associated sea of endless details, is it practical to address all the subject matter here, or is it necessary to decompose it analytically, step by step, detail by detail, topic by topic, and span thousands of pages? Covering this many topics is a formidable challenge for both the author and the reader. I've discussed this problem with many people over the years and have found that there are three general classes of responses: (1) The Nay-Sayers These people argue it can't be done. They look at me, from within their safe insulated and, in my opinion, overly simplistic world, and state it's not practical to expect one person to understand enough about both applications and networking technologies. They argue human beings aren't mentally capable of such things. They are separate areas of study and require individuals who solely focus on one or the other. That's the way it has been, and that's the way it will always be. And they add, that there are 'detailed people' and 'architectural people' and the two don't mix. (2) The Curious This group is usually very receptive. They start-off the discussion by giving me the benefit of the doubt. Their questions generally take the following form: What is the perspective, viewpoint, mental discipline- the magic if you will- involved in cultivating a deeper understanding of both? (3) The Burned These people have experienced first-hand the scenarios I described earlier. They've been in the meetings where the network engineers and the application developers clashed and the system didn't work. These people demand a copy of the book and usually our discussions last three to four times longer than we anticipated. They also ask me about viewpoint and discipline- how do you get to the bottom of problems in such complex systems, given that we agree it must be done. Relative to the Nay-Sayers, I perhaps have more confidence than they do in the capabilities of technical professionals and management. I think they can indeed grasp this. I also believe that detailed and architectural people do mix. I rebel against the belief that systems and architectural folks don't need to be bothered with details, despite the fact that I've had titles in my career such as Systems Architect. I believe in having such people and positions, but the moment they think they are the only ones who worry about architecture, and that they don't need to worry about details, then the project is guaranteed to be in for some serious trouble. People responsible for the system need to have a good understanding of concepts, architectures and yes, indeed, details. Details keep them honest. If you can't worry yourself with details such as the bytes of overhead for a packet or configured maximum packet and retransmission values for your applications and protocols, then you can't architect well, in my opinion. For those that ask about the magic, the secrets of a mental discipline that will help one cut-across such a wide range of topics, in search of the key details, but not all the details, I offer more of a psychological argument. I often refer them to such abstract perspectives as those from a famous Chinese philosopher, Lao Tzu. Lao Tzu, an acquaintance of Confucius and historically accepted by many as the author of an approximately 2500 year old famous text entitled the Tao Te Ching, wrote with great eloquence about Tao, or the Way. In his book he infers that the nature of everything in our universe escapes extreme rationalization and overly analytic definition. All that exists reflects a certain flexibility, or softness and, free from a desire to know each and every detail in our world, but instead to know its concepts (its flow) as well as the select details that guide it, we are then free to realize its mystery. The Tao is hidden but always present and is filled with infinite possibilities. Keeping Lao Tzu's perspective in mind, let's consider again the aspirations of this book. Given that any single topic explored here can alone justify hundreds and occasionally even thousands of pages of explanation, how can its goals be met? I believe the answer is rooted in perspective. For everyone I've come to know who takes true ownership for the quality of a given network and its applications together, I have observed that their problem solving approach and psychology consistently includes a virtually undescribable freeness while brainstorming, coupled with a willingness to dive deeply, looking for that one detail that when brought to the surface reveals the fundamental insight they are after. They seem instinctively to know which details to pursue, and which to leave alone. Their instincts tell them where to dive. Their thought process isn't purely top-down, nor is it entirely bottom-up. Both techniques are applied at different times. The best problem solvers I've met don't fashion themselves purely as architects nor simply as programmers or network engineers. Instead, they see themselves as thinkers. They are willing to own the entire problem, not just a piece of it and, at the same time, they have the sense and fluidity about them to know when and where to focus. They know how to maintain their buoyancy, regardless of the infinite number of details involved, because they only focus on those details that matter. I believe, consciously or not, these people have a sense of what Lao Tzu was writing about-- they have found a Way. And while I may not grasp or proclaim with great certainty that this book successfully shows this Way, I will admit to you that in writing it, I envisioned harmonizing with it, and I envisioned sharing it with you. We will dive together, and select which details are relevant for our design and architecture study, and which we will choose to leave alone. And, in doing so, we will explore a great expanse of networking and applications technologies and prepare ourselves for the new connectivity paradigm of our era- the design and architecture of Network Application Frameworks. Book Organization Our study of network application frameworks will be organized by technology provider and open standards, with emphasis on solutions offered by Netscape, Microsoft, Novell, and IBM as well as important open standards from organizations including the IETF, OMG, IEEE, ISO, and others. You'll notice that every chapter in this book begins with a mind map. Mind maps are used to summarize the technical concepts presented and their relationships to one another. In addition, every chapter except the first and last contains a table summarizing the benefits of the technology addressed within it along with industry experience and observations which support why this technology is worth looking at. Acknowledgements and Reflections The writing of this book was a soulful endeavor, one not easily explained in terms of professional career goals or a desire for material gain. It expresses my strong passion for technology and for writing. I can confidently say that to complete this book I put forth every ounce of effort I had. Books like this one don't get completed in months. They demand years of ongoing sacrifice, in every aspect of your life. I was not alone in this effort. First and foremost, I would like to thank Mary Treseler O'Brien of Addison Wesley Longman. The connection and work chemistry that Mary and I share is anything but common. From the first time we spoke and through every last painful, happy, and manic phase associated with completion of this project, Mary supported me and guided this book as if she and I had been preparing for its completion all our lives. Working alongside of Mary was Elizabeth Spainhour, who put-up with my incessant nagging and worry about every detail of the process. Elizabeth and Mary make a great team. "Two on one" was the minimum requirement to keep me under control at times. Thank goodness Elizabeth was there to keep me in my cage. Addison Wesley assembled a powerful and diverse team of reviewers for this book. Each one offered a unique perspective and style, and as a whole, they complimented each other wonderfully. Clem Cole brought deep insight, character, maturity, and a great sense of humor and understanding to the review process. He provided seasoned input into the history and content of the technologies presented in this book. Peter J. Welcher reviewed the manuscript with the utmost in tenacity, completeness, and precision. We disagreed often, right to the end. And there are a few holes in the walls of my office with Peter's name underneath them ;-) At the same time, this book is orders of magnitude better because of his involvement. Thomas R. Amlicke, Jr. provided memorable kindness and understanding through his comments and guidance. And then we have Lou Breit, Rich Sherman, Roger Snowden, and Ed Wax. While they acted independently, together they were great motivators. Rich, with the project from its beginning, was like a steady beacon, always reinforcing the premise of the book and encouraging me to move forward. Roger provided the greatest sound bytes- if I hadn't slept in what seemed like days, and needed more energy, I'd just pickup one of Roger's reviews and I'd instantly be motivated once again. And likewise, Ed provided great input and memorable words. And rounding out the group was Lou Breit, who also lent his expertise to the review of this book. Now for my friends and colleagues. I'd like to thank Judy Peck for noticing that the single guy living in the apartment below her didn't know how to keep anything but Diet Coke in his refrigerator. Judy brought me fruit salad every week and became a great friend. And thanks to Tom McKnight, a friend of mine for years. He also happens to be the most brilliant person I know. Also thanks to Colleen, Tom's daughter, for putting up without her daddy while he helped me build a strategic consulting practice. To my friends and former colleagues at Netscape, the Litronic crew, the Global SprintLink team, Simson Garfinkel, Susan Fitzgerald, Steve Petri, Cam, Leslie Aimone, Grace Adams, Chandra Shah, Eric Vaughn, Jeff Treuhaft, Jack Schiff, Sarah Gottlieb-Hecht, Jack Ziros, Larry Elfes, Vab Goel, Don Williams, Ian Little, and Sami Mousa. Thanks to Katie, Rachie, and Robbie Greenberg for putting up with Uncle Eric's writing over the holidays. Thanks to my brother James and sister-in-law Lisa. In memory of the late Phil Karlton and his wife Jan. I hope that this book is helpful and I wish you great success in your professional endeavors. Please feel free to contact me directly with any comments, corrections, complaints, or kind words. My email address is eric@seinedynamics.com. END ISBN: 0201379511 TITLE: BGP4 SUBTITLE: Inter-Domain Routing in the Internet AUTHOR: Stewart, John W. III TABLE OF CONTENTS: Preface Chapter 1: Introduction 1.1 A Brief IP Primer 1.2 Notes on Terminology 1.3 IP Addressing and the Need for Routing 1.4 Autonomous Systems and the Distinction Between IGPs and EGPs 1.5 Distance Vector Versus Link State Routing Protocols 1.5.1 Distance Vector Protocols 1.5.2 Link State Protocols 1.6 Classless Inter-Domain Routing 1.7 Setting the Tone for Understanding BGP Chapter 2: The BGP Protocol 2.1 Bringing Up a BGP Session 2.2 The BGP Message Types 2.2.1 Common Header 2.2.2 OPEN 2.2.3 UPDATE 2.2.4 NOTIFICATION 2.2.5 KEEPALIVE 2.3 Conceptual Model of Operation 2.4 Base Standard Path Attributes 2.4.1 ORIGIN 2.4.2 AS-PATH 2.4.3 NEXT-HOP 2.4.4 MULTI-EXIT-DISCRIMINATOR 2.4.5 LOCAL-PREF 2.4.6 ATOMIC-AGGREGATE 2.4.7 AGGREGATOR 2.5 Internal Versus External BGP 2.6 BGP Route Selection Process Chapter 3: BGP Operations 3.1 IGP Interacti