没有合适的资源?快使用搜索试试~ 我知道了~
The Simple Service Discovery Protocol (SSDP) provides a mechanism where by network clients, with little or no static configuration, can discover network services. SSDP accomplishes this by providing for multicast discovery support as well as server based notification and discovery routing.
资源推荐
资源详情
资源评论
Internet Engineering Task Force Yaron Y. Goland
INTERNET DRAFT Ting Cai
Paul Leach
Ye Gu
Microsoft Corporation
Shivaun Albright
Hewlett-Packard Company
October 28, 1999
Expires April 2000
Simple Service Discovery Protocol/1.0
Operating without an Arbiter
<draft-cai-ssdp-v1-03.txt>
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Please send comments to the SSDP mailing list. Subscription
information for the SSDP mailing list is available at
http://www.upnp.org/resources/ssdpmail.htm.
Abstract
The Simple Service Discovery Protocol (SSDP) provides a mechanism
where by network clients, with little or no static configuration,
can discover network services. SSDP accomplishes this by providing
for multicast discovery support as well as server based notification
and discovery routing.
Table of Contents
Status of this Memo................................................1
Abstract...........................................................1
Goland et al. [Page 1]
INTERNET-DRAFT SSDP/V1 October 28, 1999
Table of Contents..................................................1
1. Changes Since 02.............................................3
2. Introduction.................................................3
2.1. Problem Statement.........................................3
2.2. Proposed Solution.........................................4
2.2.1. Message Flow on the SSDP Multicast Channel...........4
2.2.2. SSDP Discovery Information Caching Model.............4
2.3. Design Rationale..........................................5
2.3.1. Message Flow on the SSDP Multicast Channel...........5
2.3.2. SSDP Discovery Information Caching Model.............7
3. Terminology..................................................8
4. SSDP Discovery Requests......................................8
4.1. Problem Statement.........................................8
4.2. Proposed Solution.........................................8
4.3. Design Rationale.........................................10
4.3.1. Why is the ST header so limited? Why doesn't it support
at least and/or/not? Why not name/value pair searching?.....10
4.3.2. If we are using the SEARCH method why aren't you using
the DASL search syntax?.....................................10
4.3.3. Why can we only specify one search type in the ST
header of a ssdp:discover request?..........................10
4.3.4. Why do we only provide support for multicast UDP, not
TCP, ssdp:discover requests?................................10
4.3.5. Why do we require that responses without caching
information not be cached at all?...........................11
5. SSDP Presence Announcements.................................11
5.1. Problem Statement........................................11
5.2. Proposed Solution........................................11
5.2.1. ssdp:alive..........................................11
5.2.2. ssdp:byebye.........................................12
5.3. Design Rationale.........................................13
5.3.1. Why are we using GENA NOTIFY requests?..............13
5.3.2. Why is there no response to the ssdp:alive/ssdp:byebye
requests sent to the SSDP multicast channel/port?...........13
5.3.3. Could NTS values other than ssdp:alive/ssdp:byebye be
sent to the SSDP multicast channel/port?....................13
5.3.4. Why do we include the NT header on ssdp:byebye
requests?...................................................13
5.3.5. Shouldn't the NT and NTS values be switched?........13
6. SSDP Auto-Shut-Off Algorithm................................13
6.1. Problem Statement........................................13
6.2. Proposed Solution........................................13
6.3. Design Rationale.........................................14
6.3.1. Why do we need an auto-shut-off algorithm?..........14
6.3.2. Why not just require everyone to support directories
and thus get around the scaling issue?......................15
7. ssdp:all....................................................15
7.1. Problem Statement........................................15
INTERNET-DRAFT SSDP/V1 October 28, 1999
8.1. Problem Statement........................................16
8.2. Proposed Solution........................................16
8.3. Design Rationale.........................................16
8.3.1. Why didn't SSDP just get a static local administrative
scope address rather than a relative address?...............16
8.3.2. Why does SSDP need to use a port other than 80?.....16
9. HTTP Headers................................................17
9.1. USN Header...............................................17
9.2. ST Header................................................17
10. Security Considerations.....................................17
11. IANA Considerations.........................................17
12. Appendix - Constants........................................17
13. Acknowledgements............................................17
14. References..................................................17
15. Author's Addresses..........................................18
1. Changes Since 02
The entire specification has been extensively re-written. As such
the reader is advised to re-read the entire specification rather
than to just look for particular changes.
Removed the arbiter and related functionality.
Spec used to contain both ssdp:discover and ssdp:discovery, settled
on ssdp:discover.
Changed SSDP multicast message examples to use the reserved relative
multicast address "5" provided by IANA. In the local administrative
scope, the only scope currently used by SSDP, this address
translates to 239.255.255.250.
An application has been made for a reserved port for SSDP but no
response from IANA has been received.
2. Introduction
[Ed. Note: In my experience, one of the best ways to enable a
specification to be quickly and successfully developed is to provide
a problem statement, a proposed solution and a design rationale. I
came across this three-part design structure when Larry Masinter
proposed it to the WebDAV WG. To that end, I have divided this spec
in a similar manner. Once the specification is sufficiently mature,
the problem statement and design rationale sections will be placed
in a separate document and the proposed solutions will be presented
for standardization.]
This document assumes the reader is very familiar with [RFC2616],
[HTTPUDP], [GENA], [MAN] and [RFC2365].
剩余35页未读,继续阅读
资源评论
Coding人生
- 粉丝: 31
- 资源: 10
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- YOLO-yolo资源
- 适用于 Java 项目的 Squash 客户端库 .zip
- 适用于 Java 的 Chef 食谱.zip
- Simulink仿真快速入门与实践基础教程
- js-leetcode题解之179-largest-number.js
- js-leetcode题解之174-dungeon-game.js
- Matlab工具箱使用与实践基础教程
- js-leetcode题解之173-binary-search-tree-iterator.js
- js-leetcode题解之172-factorial-trailing-zeroes.js
- js-leetcode题解之171-excel-sheet-column-number.js
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功