Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Requirements for a Protocol to Replace the AppleTalk Name Binding Protocol (NBP) (RFC6760)

IP.com Disclosure Number: IPCOM000225615D
Original Publication Date: 2013-Feb-01
Included in the Prior Art Database: 2013-Feb-21
Document File: 32 page(s) / 38K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Cheshire: AUTHOR [+2]

Abstract

An important goal of the participants working on Zeroconf, Multicast DNS, and DNS-Based Service Discovery was to provide a viable IP-based replacement for AppleTalk and the AppleTalk Name Binding Protocol (NBP).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Internet Engineering Task Force (IETF)                       S. Cheshire Request for Comments: 6760                                   M. Krochmal Category: Informational                                       Apple Inc. ISSN: 2070-1721                                            February 2013

                  Requirements for a Protocol to Replace                the AppleTalk Name Binding Protocol (NBP)

Abstract

   One of the goals of the authors of Multicast DNS (mDNS) and DNS-Based    Service Discovery (DNS-SD) was to retire AppleTalk and the AppleTalk    Name Binding Protocol (NBP) and to replace them with an IP-based    solution.  This document presents a brief overview of the    capabilities of AppleTalk NBP and outlines the properties required of    an IP-based replacement.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6760.

 Cheshire & Krochmal           Informational                     [Page 1]
 RFC 6760              Replacement of AppleTalk NBP         February 2013

 Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................3

   2. Zero Configuration Networking ...................................4

   3. Requirements ....................................................4

      3.1. Name-to-Address Mapping ....................................5

      3.2. Name Services, Not Hardware ...........