Hello, All,
Current draft (IDT_r0X.pdf as of July 5, 1999) specifies the SERVICE_ID
parameter as a service name string registered with a global naming
authority (like IANA).
The SERVICE_ID parameter is used in the following two places;
- Destination identifier for the CONNECT request operation, and
- Service descriptor for the SERVICE_DIRECTORY operation response.
By sharing a common name string in both places, the service descriptor
describes destination identifier by itself.
I have a concern with employing the globally registered service name as
a destination identifier for the CONNECT operation. (I.e., the use of
the SERVICE_ID in the former place.)
And, I would like to propose the use of new parameter "DEST_ID" for a
destination identifier that replaces "SERVICE_ID" parameter in the
"connection establishment" part of the draft.
Please find the attached document for more details. (Sorry for the file
attachment.)
If you have any comment and/or suggestion, please feel free to discuss
on this list.
By introducing the "DEST_ID", the service descriptor will also need to
be justified to include the "DEST_ID" as a part of descriptor to
provide a destination location.
I will post a proposal on the syntax of the descriptor (, and service
discovery protocol along with the syntax,) soon.
Regards,
Akihiro Shimura
--
Akihiro Shimura (shimura at pure.cpdc.canon.co.jp)
Office Imaging Products Development Center 3
CANON INC.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DestId0799.pdf
Type: application/octet-stream
Size: 21332 bytes
Desc: not available
Url : http://www.pwg.org/archives/p1394/attachments/19990723/6992a2e9/DestId0799-0001.obj