[Search] [txt|pdfized|bibtex] [Tracker] [WG] [Email] [Nits]

Versions: 00                                                            
Service Location Working Group                             Jonathan Wood
INTERNET DRAFT                                               Roberto Tam
                                                  Sun Microsystems, Inc.
                                                        22 December 1998

                          The NIS+ Service Type

Status of This Memo

   This document is a submission by the Service Location Working Group
   of the Internet Engineering Task Force (IETF).  Comments should be
   submitted to the srvloc@srvloc.org mailing list.

   This document is an Internet-Draft.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at
   any time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as ``work in progress.''

   To view the entire list of current Internet-Drafts, please check
   the ``1id-abstracts.txt'' listing contained in the Internet-Drafts
   Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
   Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
   Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).

   Distribution of this memo is unlimited.


   This document describes the NIS+ service type. NIS+ is a naming
   service which serves as a repository for UNIX-style system
   information. This service type can be used to dynamically discover
   NIS+ servers.

1. Introduction

   NIS+ is the succeeding iteration of NIS (also known as YP). It
   stands for "Network Information Service+," and uses ONC RPC [1]
   as its transport mechanism. This document describes a template
   providing a service: URL and attributes useful for dynamically
   discovering NIS+ servers; this type can be used with SLP [2].
   Service templates and service: schemes are defined in [3].

Wood, Tam                  expires June 1999                    [Page 1]

INTERNET DRAFT                                             December 1998

   This type is intended to be used as a concrete portion of the
   abstract naming-directory type defined in [4]. The NIS+ type
   includes all attributes from the naming-directory abstract type,
   and defines two new attributes specific to NIS+ security.

   For usage examples, refer to [4].

2. The NIS+ Service Type

Names of submitters: Jonathan Wood <jonathan.wood@eng.sun.com>
                     Roberto Tam <roberto.tam@eng.sun.com>
Language of service template: en
Security Considerations:
   The nisplus service type inherits the security considerations from
   the naming-directory service type [3]. Additionally, if SLP is
   used to transport public keys, measures should be taken to insure
   the integrity of these public keys across the network. One possible
   measure is to use SLP security, which protects the integrity of
   SLP payloads.

Template text:
-------------------------template begins here-----------------------


  This is a concrete type; the abstract type for this service
  is naming-directory (described in [4]). This type is used by
  NIS+ servers to advertise their services and NIS+ clients
  which wish to discover NIS+ servers.

  url-path      = "nisplus://" addr "/" directory
  addr          = ipv4-addr
  directory     = string "."  / string "." directory
  ipv4-addr     = 1*3DIGIT 3( "." 1*3DIGIT )
  string        = ISO Latin 1 character set except the
                  character '/' (slash). The initial character
                  may not be a terminal character or the
                  characters '@' (at), '+' (plus), or (`-')

security= string M
  # security mechanisms supported by this server

key= string M

Wood, Tam                  expires June 1999                    [Page 2]

INTERNET DRAFT                                             December 1998

  # the stringified public key(s) and other keying material for
  # this server.

--------------------------template ends here------------------------


  [1] Sun Microsystems, Inc., RPC: Remote Procedure Call: Protocol
      Specification Version 2, RFC 1057 June 1988.

  [2] E. Guttman, C. Perkins, J. Veizades, M. Day.  Service Location
      Protocol. draft-ietf-svrloc-protocol-v2-10.txt, July 1998 (work in

  [3] E. Guttman, C. Perkins, J. Kempf, Service Templates and service:
      Schemes. draft-ietf-svrloc-service-scheme-12.txt
      March, 1998 (work in progress).

  [4] J. Wood, R. Tam, The Naming and Directory Service Abstract Type.
      draft-ietf-svrloc-naming-directory-00.txt, November 1998 (work in

Wood, Tam                  expires June 1999                    [Page 3]