JAddress
Japan NLIA System NLIA
JAddress
NLIA
JAddress
Test Operation Sunrise
Operation
Native Language Internet Address NLIA
Native Language Internet Address NLIA
Domain Name System
a
b
c
a b
d
d
a
b
Uniform Resource Locator
c
d
http://directory.net/NUMBER
http://
ftp gopher
schemes
e
a
b
c
URL 2 URL
NLIA
NLIA
NLIA
a
a
b
b
c
c
d
providing a descriptor at the client
providing a descriptor comprising a telephone
number at the client
a
a
b
b
c
c
d
d
e
e
a
a
b
b
c
c
4 5
NLIA Name Server NLIA
NLIA Name Server
NLIA Name Server
NLIA Name Server NLIA
4 5
NLIA
NLIA Name
Server
NLIA
NLIA Name Server
NLIA Name Server NLIA
NLIA
a
b
a
b
a b
a b
a b
a 2
b
NLIA
NLIA
a
b
a
b
a a
b b
a a
b b
Computer Communication Review Volume 17, Number 5 Special Issue
A Yellow-Pages Service for a Local-Area Network Larry L. Peterson
a
b
descriptor
a
b
a X
b
c
a
b 5.2
b
a
Uniform Resource Locators
Uniform Resource Locators
b
a
b
a
Map
/a/b/* /a/b/
/X/Y/Z/*
Redirect
Redirect
http:// /
Redirect /a/b/* URL
b
c
b a
speed res arch
a b c
a b
a a
b
a a b c
b
a Redirect
/a/b
c
a
b
a
b
b
Test Operation Sunrise Operation
NLIA
NLIA Name Server
NLIA
JAddress
NLIA NLIA
Name Server
a
b
NLIA
JAddress
Sunrise Operation 3
Commercial Operation
COMPUTER COMMUNICATION REVIEW
Volume17, Number5 Special Issue Part 8. RESOURCE SHARING IN
DISTRIBUTED SYSTEMS Larry L. Peterson A Yellow-Pages Service
for a Local-Area Network
In addition to describing the implementation of the yellow-pages service within alocal-area network, we show how the service can be integrated with the available internetcommunication protocols to enable clients from throughout the internet to access localservers.
This paper describes a yellow-pages service that maps the name of a service intothe address of a server willing to provide the service
A client that wishes to engage a service queries the yellow-pages service for theaddress of a server, specifying the name of the service and any attributes the server shouldpossess.The yellow-pages service returns the address of one or more servers that satisfy theclient's requirements.
Clients connect to the flagship host as though the server is available on that host.A forwarding mechanism running on the flagship host then "patches" the client through to anactual server that provides the service.
A set of servers implement the yellow-pages service. Each server maintains adatabase of information about the available services and servers.
An attribute is a syntactic object that denotes a property or characteristic of aserver.
Clients submit a set of attributes when querying the yellow-pages for a server thatprovides a particular service.
Associated with each yellow-pages server is a database of information about theservices available in the system. The database contains bindings of each service to a set ofservers that provide the service.
Clients query the yellow-pages service for the address of one or more servers thatprovide a given service with the operation
As another example, suppose the client wishes to retrieve the address of theprinter based on its location: e.g., " the printer in Rick's office". In this case, the client invokesthe lookup operation with the mandatory attribute loc=rick. Any number of optionalattributes are ignored because the mandatory attribute loc=rick selects a single server.Rick
loc=rick lookup loc=rick
This section describes how the yellow-pages service is integrated with the internettransport protocols, therby allowing clients from throughout the internet to access serverswithin an autonomous system.
A single host in the local system is designated as the flagship host;
The system advertizes the flagship as offering a set of services to Internet clients byregistering a set of resource records potentially one for each service with the domainnaming system.
A client consults the domain name server to learn the address of a host at thesystem that offers a particular service and the address of the flagship host is returned. Theclient then contacts the server by sending one or more packets addressed to the well-knownport on the flagship host. The flagship host, in turn, forwards the packets to a server within thesystem. Thus, the forwarding mechanism is analogous to the strategy of accessing a server atwell-known port: The flagship serves as the "well-known host" for the system.Consider how the forwarding mechanism is implemented within TCP in more detail. TheTCP module running on the flagship host is modified to include the forwarding mechanism.Associated with the forwarding mechanism is a table that binds well-known ports to theaddresses of servers.
When a packet arrives at the TCP module addressed for some port, the forwardingmechanism is consulted to see if forwarding is to take place for that port; i.e., if there is anentry in the table. If the packet is from a new client, the forward server randomly selects oneof the available servers and forwards the packet on to it. That is, the forwarding mechanismsets the packet's destination address to the server's address and resends packet.Subsequent packets sent on the same connection are forwarded to the sameserver.
by engaging the selection algorithm at the server rather than the client, theyellow-pages service effectively moves the "function to the data" rather than the " data to thefunction". That is, the selection algorithm executes on the same host as the database and arelatively small answer a server address is returned.
The forwarding mechanism acts as an intermediary between the client and server.This has the advantage of not requiring any changes to the transport protocol because theclient is shielded from the indirection. In contrast, the protocol could be modified such that theflagship host informs the client that it should redirect its packets to the server host.While thismight be reasonable in the case of a connection oriented protocol e.g., TCPforwarding mechanism
patch
ftp telnet
ftp telnet
World Wide Web
http
HTML
http HyperText Transfer Protocol
World Wide Web
CGI
Location
Location
Redirect
Redirect
http:// /
httpd httpd.conf
Japan NLIA Native Language Internet Address System
JAddress
JAddress 1
2 2
NLIA Name Server 2 2
NLIA Name Server
3 4
NLIA Name Server NLIA
NLIA
NLIA
C NLIA
D NLIA
9 10
Japan NLIA Native Language Internet System JAddress
2 2
4 9
2 NLIA
NLIA
NLIA
NLIA
NLIA
9 10
出典：裁判所ウェブサイト「裁判例検索」（https://www.courts.go.jp/hanrei/36953/detail7/index.html）。本文は同サイト掲載の判決書PDFからTaiLexi AIがテキスト化・整形したもの（正確な文言は原本PDFを参照）。判示事項・裁判要旨・参照法条は裁判所の公表どおり。