RFC462 Responding to user needs

0462 Responding to user needs. J. Iseli, D. Crocker. February 1973. (Format: TXT=2808 bytes) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                                 Jean Iseli (MITRE)
RFC # 462                                        Dave Crocker (UCLA-NMC)
NIC # 14434                                            February 22, 1973


                        Responding to User Needs


INTRODUCTION

The ARPANET is currently undergoing a transition to an environment in
which network resources will be made available to a larger user base.
This emergent user base already contains a significant number of
terminal users not associated with a server site.  Information relative
to network host services and access characteristics is needed to
encourage and assist new users.

To date, the Resources Notebook has been the primary outlet for efforts
to provide users with Network-wide information. A separate RFC, from the
NIC, discusses the past and current history more completely. In this
RFC, we would like to second the NIC's suggestion for the formation of a
Working Group concerned with User Information and Services, and we would
like to offer a specific suggestion for consideration at the NIC's
proposed meeting.


PROPOSAL

Many of the problems associated with the lack of adequate Network
information are caused by the many compilation steps. Too many resources
(most of them human) are required. In addition to delay, errors are
introduced. Part of the solution is to place the acquisition of basic
information closer to the source and make the source responsible for the
acquisition and maintenance.

    The "source" is distributed around the Network and, therefore, the
    proposal is to develop and implement a distributed and extensible
    network data-base which contains the desired information.  This
    would require each server site to create and maintain an information
    file locally and/or at the NIC. As a further (more down stream)
    step, a mechanism to access these files could be specified and
    implemented.

        People at different sites would thereby be able to use the tools
        most comfortable and accessible to them.






Iseli & D. Crocker                                              [Page 1]

RFC 462                 Responding to User Needs           February 1973


        An interesting technical issue involves making the disparate
        files accessible by an automaton.  The NIC is currently
        attempting to smooth out the interface between NLS and non-NLS
        files, and this seems like a reasonable object for such efforts.










       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by Alex McKenzie with    ]
       [ support from GTE, formerly BBN Corp.             9/99 ]


































Iseli & D. Crocker                                              [Page 2]

一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

画像を読み込まない設定下では背景画像と背景色の指定が無効になる

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る