DOCSLIB.ORG

Zero Configuration and the Future Home Network

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Zero Configuration and the Future Home Network ZERO CONFIGURATION AND THE FUTURE HOME NETWORK William Garrison Motorola, Inc., Broadband Communications Sector Abstract of Windows PCs. However, these protocols were completely separate from any WAN This paper will review the state-of-the-art (Wide Area Network) Protocol and served a in Zero Configuration initiatives as it applies limited range of devices. They did not allow to an in-home network. The IETF Zeroconf, a wide variety of appliances, PCs and Macs to UPnP (Universal Plug-and-Play), Apple interoperate. Rendezvous and IPv6 Stateless Address Autoconfiguration initiatives will be covered. An additional Zero Configuration In addition, from a MSO’s perspective, does networking benefit will be the creation of new Zero Configuration represent a lost revenue kinds of networked products. These products opportunity or a lost headache opportunity? will become commercially viable only when How will the Zero Configuration home the inconvenience and support costs of network connect to the internet? traditional networking technologies are removed. INTRODUCTION This paper will cover the Zero Consumers do not want to own a home Configuration of IP (Internet Protocol) based network. Instead, they want applications and networks. IP was selected because it is the services to simply work, as if by magic. If native protocol for the ubiquitous Internet. this magic requires a network, then it should be easily invoked with, at most, a simple COVERAGE incantation. This is how the consumer sees it. This is how we need to see it to get consumers A whole home network should be to deploy applications that rely on home comprised of all of the data paths available networks. between devices. These data paths include wired and wireless technologies. Wired The purpose of a home network is to technologies include power line, phone line, enable new services by combining the coax and dedicated CAT5 wiring. Wireless capabilities of both new and existing includes 802.11a/b/g, Zigbee and UWB (Ultra elements. Why can’t I view a program that Wide Band). These technologies have happens to be stored on my PVR downstairs significantly different data rate, delay and on my TV upstairs? Why can’t I listen to the jitter characteristics. However, we need them music stored on my iPod on my home theater to interoperate seamlessly and with zero user without hooking anything up? Well, with a intervention. Zero Configuration home network, you will be able to do all these things and more! REQUIREMENTS Zero Configuration is not a new idea. In As described in the internet draft entitled the past, AppleTalk handled Zero “Requirements for Automatic Configuration Configuration for Macs and NETBIOS of IP Hosts” by Aidan Williams [1], Zero provided similar features for small networks Configuration requires that we: • Distribute IP addresses without a to interact with a corresponding entity at the DHCP (Dynamic Host Configuration same layer in a remote host. Zero Protocol) server Configuration applies to the Application and • Provide name resolution without a Network layers, as outlined in Figure 1. DNS (Domain Name System) server • Find and list services SECURITY • Distribute multicast addresses Security is also a Zero Configuration In addition, while the system must operate requirement. In the wired world, there is in the absence of DHCP and DNS, it also some physical security in a local network. In must operate properly in their presence. Zero the wireless world, it is a challenge to tell the Configuration must not thwart their normal difference between your wireless device and function. your neighbor’s. Zero Configuration may bring tighter security requirements. You cannot depend on the user noticing an Application intrusion because the user is further removed Name Resolution / Find Services from what is actually going on. At the very least, the protocols used on a Zero Configuration network must be as secure as a Presentation non-Zero Configuration network. Does Zero Configuration degrade security? Not really, a cracker can find out the same Session network information as offered by Zero Configuration using standard tools. There are plenty of tools floating around that let the unsophisticated “script kiddies” get into Transport lightly protected networks. Zero Configuration’s most likely security effect is to increase the number of networks that Network someone might try to intercept and increase IP unicast/multicast addresses the number of devices connected to those networks. Data Link ZERO CONFIGURATION APPROACHES Many people are currently trying to solve the Zero Configuration problem. Current Physical initiatives include: • Apple Rendezvous • IETF Zeroconf Figure 1 – The OSI Reference Model • UPnP™ (Universal Plug-and-Play) The OSI Basic Reference Model divides a • IPv6 Stateless Address networking system into seven layers. This Autoconfiguration layering system enables an entity in one host Each of these will be covered in its own Vulnerability to denial of service attacks is section. probably unavoidable. Even a simple ploy, such as a rogue device responding to every IETF ZEROCONF ARP (Address Resolution Protocol) so as to claim all available IP addresses, could shut The Zeroconf Working Group of the IETF down a Zeroconf network. However, is this (Internet Engineering Task Force) was any worse than being unable to speak to the chartered in September, 1999. Its goal is to person next to you on the train due to an “enable networking in the absence of unruly child? Given local nature of a configuration and administration.” Their goal Zeroconf network, the universe of people who is so inclusive that it goes as far as to include could interfere with your network is small. allowing “impromptu networks as between Given the local nature of the network, in the the devices of strangers on a train.” [2] case of a network interruption you could simply search for the scoundrel. Zeroconf is a link-local technology. This means that the link-local addressing and Industry Support naming are only meaningful to devices directly connected to the local network. A standard needs industry support to have Because these addresses and names are not real-world relevance. Support for Zeroconf unique globally, Zeroconf only applies to has been announced by: small wired or wireless networks. Zeroconf is • Apple appropriate for: • Canon • Home and small office networks • Epson • Ad hoc networks at meetings and • HP conferences • Lexmark • Two devices needed to share • Philips information • Sybase Inappropriate applications of Zeroconf would • Xerox potentially result in serious networking • World-Book problems. Working Group Status Security The Zeroconf Working Group could not Zeroconf security is primarily based on the reach a consensus on security and service requirement that all included devices must be discovery issues. Therefore, it is not going to connected to a single link. Therefore, a produce a specification on those issues. The Zeroconf connection can only be hacked by a Working Group is producing a protocol device that is close by and easier to detect. specification, describing automatic generation However, if you are indeed going to and assignment of link-local IPv4 addresses in wirelessly network with the stranger on the environments lacking host configuration train, you will want some way to prevent (static or using DHCP). This document is in networking with the stranger in the next train draft form and will be submitted in the spring compartment. of 2004 for consideration as a Standards Track RFC. A Zeroconf network is relatively vulnerable to some fairly standard attacks. Further information on the IETF Zeroconf Working group can be found at http://www.zeroconf.org/. APPLE RENDEZVOUS Rendezvous is Apple’s name for IETF’s Zeroconf. You might want to think of it like Rendezvous is to Zeroconf as Firewire is to 1394. Rendezvous is an open protocol, which Apple has submitted back to the IETF as a part Figure 2 – A Rendezvous Assigned IP Address of the ongoing standards creation process. Apple is using Rendezvous to transition from In the above figure, you can tell the IP AppleTalk to an all-IP network. address came from Rendezvous both by the 164.256/16 address and the annotation “Self- Rendezvous matches the Apple customer’s assigned”. expectations of a friendly, easy to use system. Apple added Rendezvous services in the Apple then uses mDNS (multicast DNS) to Jaguar release of the Mac OS X Operating handle DNS requests. In mDNS, each device System and is using those services in its own runs their own mDNS responder. The mDNS applications. responder provides traditional domain name services by having every device respond to Rendezvous uses three technologies the name queries that they know how to • Automatic IP addresses (IPv4) answer. Traditionally, devices contact a single • Name to Address Translation (DNS known DNS server for name lookups. In queries via IP Multicast) mDNS, when a host needs to look up a name, • Service Discovery it sends the query out to a local multicast group that includes all of devices that have A Rendezvous device first tries to obtain locally registered Rendezvous services. an IP address by a standard DHCP request. If there is no DHCP response, it: Rendezvous also uses a DNS-based • picks an address at random in the Service Discovery called mDNS-SD. 169.254/16 range Essentially, services are resolved to devices • Checks to see if this IP address is used similar to the way host names are resolved via an ARP (tries another IP if it is) using mDNS. • Periodically checks for DHCP server Rendezvous Applications The device periodically checks for a DHCP server because it wants to participate in the Apple uses Rendezvous in its iChat instant network with the widest possible reach. messaging application. Besides working with AOL Instant Messenger, it also works with Rendezvous-enabled Macs. So, if the stranger on the train has a Mac, you can easily chat.
Load more

Recommended publications
  • Ipv6-Ipsec And
    IPSec and SSL Virtual Private Networks ITU/APNIC/MICT IPv6 Security Workshop 23rd – 27th May 2016 Bangkok Last updated 29 June 2014 1 Acknowledgment p Content sourced from n Merike Kaeo of Double Shot Security n Contact: [email protected] Virtual Private Networks p Creates a secure tunnel over a public network p Any VPN is not automagically secure n You need to add security functionality to create secure VPNs n That means using firewalls for access control n And probably IPsec or SSL/TLS for confidentiality and data origin authentication 3 VPN Protocols p IPsec (Internet Protocol Security) n Open standard for VPN implementation n Operates on the network layer Other VPN Implementations p MPLS VPN n Used for large and small enterprises n Pseudowire, VPLS, VPRN p GRE Tunnel n Packet encapsulation protocol developed by Cisco n Not encrypted n Implemented with IPsec p L2TP IPsec n Uses L2TP protocol n Usually implemented along with IPsec n IPsec provides the secure channel, while L2TP provides the tunnel What is IPSec? Internet IPSec p IETF standard that enables encrypted communication between peers: n Consists of open standards for securing private communications n Network layer encryption ensuring data confidentiality, integrity, and authentication n Scales from small to very large networks What Does IPsec Provide ? p Confidentiality….many algorithms to choose from p Data integrity and source authentication n Data “signed” by sender and “signature” verified by the recipient n Modification of data can be detected by signature “verification”
    [Show full text]
  • 1. Ipv4 Sites Reaching Global Ipv4 Internet
    1. IPv4 Sites Reaching Global IPv4 Internet Private IPv4 Internet IPv4 NAT • Keep IPv4 service as unchanged as possible, even without enough addresses • Single global IPv4 address shared across more than one subscriber SP IPv6 Network Private Tunnel for IPv4 (public, private, port-limited, etc....) IPv4 Internet IPv4 • Scenario #2 - Service Providers Running out of Private IPv4 space • IPv4 / IPv6 encapsulations/tunnels • Tunnels setup by DHCP, Routing, etc. between a GW and Router • Wherever the NAT lands, it is important that the user keeps control of it • Provides a path to delivering IPv6 SP IPv6 Network Tunnel for IPv4 (public, private, port-limited, etc....) IPv4 Internet • Scenario #3a “Wireless Greenfield” • IPv4 / IPv6 encapsulations/tunnels • Tunnels setup between a host and a Router • IPv4 binding for host applications, transport over IPv6 • Wherever the NAT lands, it is important that the user keeps control of it 3 - 5 Translation Options IPv6 Internet IPv4 Internet IPv6 IPv4 My IPv6 Network IPv6 Internet IPv4 Internet • “Scenario #3” • NAT64/DNS64.... - Stateful, DNSSEC Challenges, DNS64 location, etc. My IPv6 Network IPv6 Internet IPv4 Internet • “Scenario #5” • IVI - NAT-PT..... Expose only certain IPv6 servers, etc. MY IPv4 Network IPv6 Internet IPv4 Internet • “Scenario #4” • NAT64 - 1:1, Stateless, DNSSEC OK, no DNS64 MY IPv4 Network IPv6 Internet IPv4 Internet • Already solved by existing transition mechanisms?? (teredo, etc). Scenarios 1 - 5 1. IPv4 Sites Reaching Global IPv4 Internet Private IPv4 Internet IPv4 NAT • Keep IPv4 service as unchanged as possible, even without enough addresses • Single global IPv4 address shared across more than one subscriber 2. Service Providers Running out of Private IPv4 space ISP Private IPv4 Private Network IPv4 IPv4 Internet • Service Providers with large, privately addressed, IPv4 networks • Organic growth plus pressure to free global addresses for customer use contribute to the problem • The SP Private networks in question generally do not need to reach the Internet at large 3.
    [Show full text]
  • Internet Protocol Suite
    InternetInternet ProtocolProtocol SuiteSuite Srinidhi Varadarajan InternetInternet ProtocolProtocol Suite:Suite: TransportTransport • TCP: Transmission Control Protocol • Byte stream transfer • Reliable, connection-oriented service • Point-to-point (one-to-one) service only • UDP: User Datagram Protocol • Unreliable (“best effort”) datagram service • Point-to-point, multicast (one-to-many), and • broadcast (one-to-all) InternetInternet ProtocolProtocol Suite:Suite: NetworkNetwork z IP: Internet Protocol – Unreliable service – Performs routing – Supported by routing protocols, • e.g. RIP, IS-IS, • OSPF, IGP, and BGP z ICMP: Internet Control Message Protocol – Used by IP (primarily) to exchange error and control messages with other nodes z IGMP: Internet Group Management Protocol – Used for controlling multicast (one-to-many transmission) for UDP datagrams InternetInternet ProtocolProtocol Suite:Suite: DataData LinkLink z ARP: Address Resolution Protocol – Translates from an IP (network) address to a network interface (hardware) address, e.g. IP address-to-Ethernet address or IP address-to- FDDI address z RARP: Reverse Address Resolution Protocol – Translates from a network interface (hardware) address to an IP (network) address AddressAddress ResolutionResolution ProtocolProtocol (ARP)(ARP) ARP Query What is the Ethernet Address of 130.245.20.2 Ethernet ARP Response IP Source 0A:03:23:65:09:FB IP Destination IP: 130.245.20.1 IP: 130.245.20.2 Ethernet: 0A:03:21:60:09:FA Ethernet: 0A:03:23:65:09:FB z Maps IP addresses to Ethernet Addresses
    [Show full text]
  • The Internet Protocol, Version 4 (Ipv4)
    Today’s Lecture I. IPv4 Overview The Internet Protocol, II. IP Fragmentation and Reassembly Version 4 (IPv4) III. IP and Routing IV. IPv4 Options Internet Protocols CSC / ECE 573 Fall, 2005 N.C. State University copyright 2005 Douglas S. Reeves 1 copyright 2005 Douglas S. Reeves 2 Internet Protocol v4 (RFC791) Functions • A universal intermediate layer • Routing IPv4 Overview • Fragmentation and reassembly copyright 2005 Douglas S. Reeves 3 copyright 2005 Douglas S. Reeves 4 “IP over Everything, Everything Over IP” IP = Basic Delivery Service • Everything over IP • IP over everything • Connectionless delivery simplifies router design – TCP, UDP – Dialup and operation – Appletalk – ISDN – Netbios • Unreliable, best-effort delivery. Packets may be… – SCSI – X.25 – ATM – Ethernet – lost (discarded) – X.25 – Wi-Fi – duplicated – SNA – FDDI – reordered – Sonet – ATM – Fibre Channel – Sonet – and/or corrupted – Frame Relay… – … – Remote Direct Memory Access – Ethernet • Even IP over IP! copyright 2005 Douglas S. Reeves 5 copyright 2005 Douglas S. Reeves 6 1 IPv4 Datagram Format IPv4 Header Contents 0 4 8 16 31 •Version (4 bits) header type of service • Functions version total length (in bytes) length (x4) prec | D T R C 0 •Header Length x4 (4) flags identification fragment offset (x8) 1. universal 0 DF MF s •Type of Service (8) e time-to-live (next) protocol t intermediate layer header checksum y b (hop count) identifier •Total Length (16) 0 2 2. routing source IP address •Identification (16) 3. fragmentation and destination IP address reassembly •Flags (3) s •Fragment Offset ×8 (13) e t 4. Options y IP options (if any) b •Time-to-Live (8) 0 4 ≤ •Protocol Identifier (8) s e t •Header Checksum (16) y b payload 5 •Source IP Address (32) 1 5 5 6 •Destination IP Address (32) ≤ •IP Options (≤ 320) copyright 2005 Douglas S.
    [Show full text]
  • SOCKS Protocol Version 6
    SOCKS Protocol Version 6 draft-olteanu-intarea-socks-6-08 Vladimir Olteanu IETF 106 What’s new ● DNS provided by SOCKS ● Options for Happy Eyeballs at the proxy Clients need DNS-like features ● A and AAAA – LD_PRELOAD for non-SOCKS-aware apps: gedaddrinfo() separate from connect() – Happy Eyeballs: need to do queries separately ● TXT – ESNI ● MX, Service Binding, etc. – <Insert future use case here> Providing DNS-like features ● Individual SOCKS options (removed in -08) – Have to keep up with use cases – Duplicate DNS functionality – Until -07: A, AAAA, PTR ● Having the client use DNS – Hard to convey policies: resolver IPs, plaintext / over TLS / over HTTPS etc., maybe credentials, etc. – Provide a DNS proxy Why not separate DNS from SOCKS? Client Proxy Server HTTP/SOCKS :1080 HTTP :80 DNS :53 Why not separate DNS from SOCKS? Client Proxy Server HTTP/SOCKS :1080 HTTP :80 DNS :53 WHICH TOR CIRCUIT? ● Need context for DNS query – Otherwise: privacy leaks, suboptimal CDN use DNS provided by SOCKS ● Clients make CONNECT request to 0.0.0.0:53 – Proxy needn’t provide a valid bind address ● Plaintext DNS over SOCKS (opt. over TLS) – TCP by default: SOCKS + UDP more cumbersome to use ● Implementation in Sixtysocks – Run separate DNS proxy locally – Translate 0.0.0.0:53 to 127.0.0.1:53 Happy Eyeballs ● RFC 8305: resolve and connect to a server using both IPv4 and IPv6, keep only one connection – Failover from IPv6 to IPv4 – Better responsiveness if one is faster ● Clients can implement Happy Eyeballs locally – Have DNS + CONNECT Happy Eyeballs:
    [Show full text]
  • 61A Lecture 35 Distributed Computing Internet Protocol Transmission
    Announcements • Homework 9 (6 pts) due Wednesday 11/26 @ 11:59pm ! Homework Party Monday 6pm-8pm in 2050 VLSB • Guest in live lecture, TA Soumya Basu, on Monday 11/24 • Optional Scheme recursive art contest due Monday 12/1 @ 11:59pm 61A Lecture 35 • No lecture on Wednesday 11/26 (turkey) • No lab on Tuesday 11/25 & Wednesday 11/26 • The week of 12/1: Homework 10 due Wednesday 12/3 & Quiz 3 due Thursday 12/4 on SQL Monday, November 24 ! The lab on SQL (12/2 & 12/3) will be an excellent place to get homework help 2 Distributed Computing A distributed computing application consists of multiple programs running on multiple computers that together coordinate to perform some task. • Computation is performed in parallel by many computers. • Information can be restricted to certain computers. • Redundancy and geographic diversity improve reliability. Distributed Computing Characteristics of distributed computing: • Computers are independent — they do not share memory. • Coordination is enabled by messages passed across a network. • Individual programs have differentiating roles. Distributed computing for large-scale data processing: • Databases respond to queries over a network. • Data sets can be partitioned across multiple machines (next lecture). 4 Network Messages Computers communicate via messages: sequences of bytes transmitted over a network. Messages can serve many purposes: • Send data to another computer • Request data from another computer • Instruct a program to call a function on some arguments. Internet Protocol • Transfer a program to be executed by another computer. Messages conform to a message protocol adopted by both the sender (to encode the message) & receiver (to interpret the message).
    [Show full text]
  • Ipv6 – What Is It, Why Is It Important, and Who Is in Charge? … Answers to Common Questions from Policy Makers, Executives and Other Non­Technical Readers
    IPv6 – What is it, why is it important, and who is in charge? … answers to common questions from policy makers, executives and other non­technical readers. A factual paper prepared for and endorsed by the Chief Executive Officers of ICANN and all the Regional Internet Registries, October 2009. 1. What is IPv6? “IP” is the Internet Protocol, the set of digital communication codes which underlies the Internet infrastructure. IP allows the flow of packets of data between any pair of points on the network, providing the basic service upon which the entire Internet is built. Without IP, the Internet as we know it would not exist. Currently the Internet makes use of IP version 4, or IPv4, which is now reaching the limits of its capacity to address additional devices. IPv6 is the “next generation” of IP, which provides a vastly expanded address space. Using IPv6, the Internet will be able to grow to millions of times its current size, in terms of the numbers of people, devices and objects connected to it1. 2. Just how big is IPv6? To answer this question, we must compare the IPv6 address architecture with that of IPv4. The IPv4 address has 32 bits, allowing today’s Internet to connect up to around four billion devices. By contrast, IPv6 has an address of 128 bits. Because each additional bit doubles the size of the address space, an extra 96 bits increases the theoretical size of the address space by many trillions of times. For comparison, if IPv4 were represented as a golf ball, then IPv6 would be approaching the size of the Sun.2 IPv6 is certainly not infinite, but it is not going to run out any time soon.
    [Show full text]
  • Domain Name System 1 Domain Name System
    Domain Name System 1 Domain Name System The Domain Name System (DNS) is a hierarchical distributed naming system for computers, services, or any resource connected to the Internet or a private network. It associates various information with domain names assigned to each of the participating entities. A Domain Name Service translates queries for domain names (which are easier to understand and utilize when accessing the internet) into IP addresses for the purpose of locating computer services and devices worldwide. An often-used analogy to explain the Domain Name System is that it serves as the phone book for the Internet by translating human-friendly computer hostnames into IP addresses. For example, the domain name www.example.com translates to the addresses 192.0.43.10 (IPv4) and 2620:0:2d0:200::10 (IPv6). The Domain Name System makes it possible to assign domain names to groups of Internet resources and users in a meaningful way, independent of each entity's physical location. Because of this, World Wide Web (WWW) hyperlinks and Internet contact information can remain consistent and constant even if the current Internet routing arrangements change or the participant uses a mobile device. Internet domain names are easier to remember than IP addresses such as 208.77.188.166 (IPv4) or 2001:db8:1f70::999:de8:7648:6e8 (IPv6). Users take advantage of this when they recite meaningful Uniform Resource Locators (URLs) and e-mail addresses without having to know how the computer actually locates them. The Domain Name System distributes the responsibility of assigning domain names and mapping those names to IP addresses by designating authoritative name servers for each domain.
    [Show full text]
  • WIRELESS BLUETOOTH 2.0 USB Adapter
    ENABLE BLUETOOTH® CONNECTIVITY ON YOUR COMPUTER Wireless Bluetooth 2.0 USB ADapter BLUETOOTH CONNECTIVITY NETWORK PROTECTION WIRELESS INTEGRATION Sync data between your Bluetooth Protect your personal information with Experience the convenience of PDA, mobile phone, and PC 128-bit encryption Bluetooth headphones, cameras, mice, and keyboards BLUETOOTH CONNECTIVITY Experience the world of Bluetooth technology with the D-Link Wireless Bluetooth 2.0 USB Adapter (DBT-120). Sync your PDA and download images from your Bluetooth camera from across the room or transfer music from your PC to your mobile phone from down the hall. Connect headphones, mice, keyboards, and other Bluetooth devices to your computer with the convenience of Bluetooth wireless technology1. COMPACT AND PORTABLE The Wireless Bluetooth 2.0 USB Adapter was designed and engineered with mobile users in mind, making it a perfect solution for use with notebook computers. Ultra-compact and portable, utilize the device on trips, at work, school, coffee shops, or anywhere around the house for an instant, untethered connection. SIMPLE SETUP The DBT-120 is compatible with Windows® XP/2000 and Mac OS® X2 and works with desktop or notebook computers with an available USB 2.0/1.1 port3. To keep your data safe and secure, the DBT-120 utilizes 128-bit encryption and Frequency-Hopping Spread Spectrum (FHSS). The DBT-120 features Plug and Play and Universal Plug and Play (UPnP) for easy installation and detection of compatible devices. The included software enables you to identify and manage Bluetooth devices on your network. SEAMLESS CONNECTION Both notebook and desktop computer users will experience seamless connectivity with the D-Link Wireless Bluetooth 2.0 USB Adapter (DBT-120).
    [Show full text]
  • Guidelines for the Secure Deployment of Ipv6
    Special Publication 800-119 Guidelines for the Secure Deployment of IPv6 Recommendations of the National Institute of Standards and Technology Sheila Frankel Richard Graveman John Pearce Mark Rooks NIST Special Publication 800-119 Guidelines for the Secure Deployment of IPv6 Recommendations of the National Institute of Standards and Technology Sheila Frankel Richard Graveman John Pearce Mark Rooks C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 December 2010 U.S. Department of Commerce Gary Locke, Secretary National Institute of Standards and Technology Dr. Patrick D. Gallagher, Director GUIDELINES FOR THE SECURE DEPLOYMENT OF IPV6 Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL’s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-119 Natl. Inst. Stand. Technol. Spec. Publ. 800-119, 188 pages (Dec. 2010) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately.
    [Show full text]
  • DOD Memorandum: Department of Defense Implementation of Internet
    DEPUTY SECRETARY OF DEFENSE 1010 DEFENSE PENTAGON WASHINGTON DC 20301-1010 June 29, 2021 MEMORANDUM FOR SENIOR PENTAGON LEADERSHIP DEFENSE AGENCY AND DOD FIELD ACTIVITY DIRECTORS SUBJECT: Directive-type Memorandum 21-004 – “Department of Defense Implementation of Internet Protocol Version 6” References: See Attachment 1 Purpose. Pursuant to the Federal requirements in Office of Management and Budget (OMB) Memorandum M-21-07, this directive-type memorandum (DTM): • Establishes policy, assigns responsibilities, and prescribes procedures for deploying and using Internet Protocol version 6 (IPv6) in DoD information systems. • Is effective June 29, 2021; it will be converted to a new DoD instruction. This DTM will expire effective 12 months from the date issuance is published on the DoD Issuances Website, June 29, 2022. Applicability. This DTM: • Applies to OSD, the Military Departments (including the Coast Guard at all times, including when it is a Service in the Department of Homeland Security by agreement with that Department), the Office of the Chairman of the Joint Chiefs of Staff and the Joint Staff, the Combatant Commands, the Office of Inspector General of the Department of Defense, the Defense Agencies, the DoD Field Activities, and all other organizational entities within DoD (referred to collectively in this issuance as the “DoD Components”). • Does not apply to National Security Systems, as defined by Committee on National Security Systems Instruction 4009. Definitions. See Glossary. Policy. Pursuant to OMB Memorandum M-21-07, all new networked DoD information systems that use internet protocol (IP) technologies will be IPv6-enabled before implementation and operational use by the end of fiscal year (FY) 2023.
    [Show full text]
  • Universal Plug and Play Device Architecture
    UPnP Device Architecture 1.0 Document Revision Date 15 October 2008 Note: This document consolidates the several separate documents that make up the entirety of UPnP Device Architecture Version 1.0, including the previously separate specifications for AutoIP, SSDP, HTTPU/MU, FXPP, and GENA, and clarifications made in the UPnP Vendor Implementation Guide. It does not introduce any new technical requirements, but constitutes an editorial clarification only. Contributors Allegro Software Development Corporation Conexant Systems, Inc. Intel Corporation Microsoft Corporation Motorola Nokia Corporation Philips Electronics Pioneer Sony Electronics © 2008 Contributing Members of the UPnP™ Forum. All rights reserved. See http://www.upnp.org/info/cpyright.asp for more information. Table of Contents Introduction ........................................................................................ 1 What is UPnP™ Technology? .................................................................... 1 UPnP™ Forum ..................................................................................... 1 In this document ................................................................................. 2 Audience .......................................................................................... 4 Required vs. recommended .................................................................... 4 Acronyms .......................................................................................... 5 References and resources .....................................................................
    [Show full text]