RFC 3091 (rfc3091) - Page 1 of 6

Pi Digit Generation Protocol

Network Working Group                                         H. Kennedy
Request for Comments: 3091                        University of Michigan
Category: Informational                                     1 April 2001


                      Pi Digit Generation Protocol

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 (2001).  All Rights Reserved.

Abstract

   This memo defines a protocol to provide the Pi digit generation
   service (PIgen) used between clients and servers on host computers.

Introduction

   This protocol is intended to provide the Pi digit generation service
   (PIgen), and be used between clients and servers on host computers.
   Typically the clients are on workstation hosts lacking local Pi
   support, and the servers are more capable machines with greater Pi
   calculation capabilities.  The essential tradeoff is the use of
   network resources and time instead of local computational cycles.

   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 [RFC 2119].

Note

   All digits supplied by implementations of this service are ASCII
   [US-ASCII] representations of decimal (base 10) numbers following the
   decimal point in values or approximations of Pi.  There MUST be an
   implied decimal value of 3 (three) preceding the values provided by
   the service defined by this protocol.

1.     TCP Based Digit Generator Service

   One REQUIRED PIgen service is defined as a stateless TCP service.  A
   server listens on TCP port 314159.  Once a connection is established
   the server sends a stream of data, one digit of Pi at at time,



Kennedy                      Informational