< draft-hallambaker-web-service-discovery-01.txt   draft-hallambaker-web-service-discovery-02.txt >
Network Working Group P. Hallam-Baker Network Working Group P. Hallam-Baker
Internet-Draft February 25, 2019 Internet-Draft April 4, 2019
Intended status: Informational Intended status: Informational
Expires: August 29, 2019 Expires: October 6, 2019
DNS Web Service Discovery DNS Web Service Discovery
draft-hallambaker-web-service-discovery-01 draft-hallambaker-web-service-discovery-02
Abstract Abstract
This document describes a standardized approach to discovering Web This document describes a standardized approach to discovering Web
Service Endpoints from a DNS name. Services are advertised using the Service Endpoints from a DNS name. Services are advertised using the
DNS SRV and TXT records and the HTTP Well Known Service conventions. DNS SRV and TXT records and the HTTP Well Known Service conventions.
This document is also available online at This document is also available online at
http://mathmesh.com/Documents/draft-hallambaker- web-service- http://mathmesh.com/Documents/draft-hallambaker-web-service-
discovery.html [1] . discovery.html [1] .
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 29, 2019. This Internet-Draft will expire on October 6, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 27 skipping to change at page 2, line 27
3.2.1. TXT Service and Host Description . . . . . . . . . . 5 3.2.1. TXT Service and Host Description . . . . . . . . . . 5
3.3. Service Selection . . . . . . . . . . . . . . . . . . . . 5 3.3. Service Selection . . . . . . . . . . . . . . . . . . . . 5
3.4. Web Service Endpoint Determination . . . . . . . . . . . 5 3.4. Web Service Endpoint Determination . . . . . . . . . . . 5
3.5. DNS Fallback . . . . . . . . . . . . . . . . . . . . . . 6 3.5. DNS Fallback . . . . . . . . . . . . . . . . . . . . . . 6
3.6. Example . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.6. Example . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Further Work . . . . . . . . . . . . . . . . . . . . . . . . 8 4. Further Work . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Additional Description Keys . . . . . . . . . . . . . . . 8 4.1. Additional Description Keys . . . . . . . . . . . . . . . 8
4.2. Service Scaling . . . . . . . . . . . . . . . . . . . . . 8 4.2. Service Scaling . . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6.1. Well-Known URIs . . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 9 7.1. Normative References . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . 9 7.2. Informative References . . . . . . . . . . . . . . . . . 9
7.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
Web services are traditionally identified by means of a URI Web services are traditionally identified by means of a URI
specifying a Web Service Endpoint (WSE). This is approach is specifying a Web Service Endpoint (WSE). This is approach is
unsatisfactory in many situations: unsatisfactory in many situations:
o Specification of the Web Service requires the transport and o Specification of the Web Service requires the transport and
presentation protocols to be fixed. presentation protocols to be fixed.
skipping to change at page 8, line 50 skipping to change at page 9, line 5
the present work. the present work.
5. Security Considerations 5. Security Considerations
A treatment of the security considerations will follow. A treatment of the security considerations will follow.
6. IANA Considerations 6. IANA Considerations
The following registrations are required: The following registrations are required:
Well-Known URIs /.well-known/srv/ 6.1. Well-Known URIs
[Or change registry to FCFS] The following registration is requested in the well-known URI
registry in accordance with [RFC5785]
URI suffix
srv
Change controller
Phillip Hallam-Baker, phill@hallambaker.com
Specification document(s):
[This document]
Related information
[draft-hallambaker-web-service-discovery]
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for [RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", RFC 2782, specifying the location of services (DNS SRV)", RFC 2782,
DOI 10.17487/RFC2782, February 2000. DOI 10.17487/RFC2782, February 2000.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
skipping to change at page 9, line 28 skipping to change at page 9, line 47
[RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known [RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known
Uniform Resource Identifiers (URIs)", RFC 5785, Uniform Resource Identifiers (URIs)", RFC 5785,
DOI 10.17487/RFC5785, April 2010. DOI 10.17487/RFC5785, April 2010.
[RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service [RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service
Discovery", RFC 6763, DOI 10.17487/RFC6763, February 2013. Discovery", RFC 6763, DOI 10.17487/RFC6763, February 2013.
7.2. Informative References 7.2. Informative References
[draft-hallambaker-web-service-discovery]
Hallam-Baker, P., "DNS Web Service Discovery", draft-
hallambaker-web-service-discovery-01 (work in progress),
February 2019.
[RFC5322] Resnick, P., "Internet Message Format", RFC 5322, [RFC5322] Resnick, P., "Internet Message Format", RFC 5322,
DOI 10.17487/RFC5322, October 2008. DOI 10.17487/RFC5322, October 2008.
[RFC6698] Hoffman, P. and J. Schlyter, "The DNS-Based Authentication [RFC6698] Hoffman, P. and J. Schlyter, "The DNS-Based Authentication
of Named Entities (DANE) Transport Layer Security (TLS) of Named Entities (DANE) Transport Layer Security (TLS)
Protocol: TLSA", RFC 6698, DOI 10.17487/RFC6698, August Protocol: TLSA", RFC 6698, DOI 10.17487/RFC6698, August
2012. 2012.
7.3. URIs 7.3. URIs
[1] http://mathmesh.com/Documents/draft-hallambaker- web-service- [1] http://mathmesh.com/Documents/draft-hallambaker-web-service-
discovery.html discovery.html
Author's Address Author's Address
Phillip Hallam-Baker Phillip Hallam-Baker
Email: phill@hallambaker.com Email: phill@hallambaker.com
 End of changes. 11 change blocks. 
10 lines changed or deleted 33 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/