Opened 8 years ago

Closed 8 years ago

#2 closed defect (fixed)

Section: Timezone Service SRV Service Labels

Reported by: mglt.ietf@… Owned by: cyrus@…
Priority: major Milestone:
Component: caldav-timezone-ref Version:
Severity: Candidate WG Document Keywords:


Draft: draft-douglass-timezone-service-11

_timezones._tcp shouldn't it be: _timezones._sub._http._tcp

Change History (2)

comment:1 Changed 8 years ago by mglt.ietf@…

  • Component set to caldav-timezone-ref

the correct syntax is _timezones_tcp . _timezones._sub._http._tcp is incorrect in our case.

RFC6763 Scetion 7 provides the description below:


However, it is common to "borrow" an existing protocol and repurpose
it for a new task. This is entirely sensible and sound engineering
practice, but that doesn't mean that the new protocol is providing
the same semantic service as the old one, even if it borrows the same
message formats. For example, the network music sharing protocol
implemented by iTunes on Macintosh and Windows is built upon "HTTP
GET" commands. However, that does *not* mean that it is sensible or
useful to try to access one of these music servers by connecting to
it with a standard web browser. Consequently, the DNS-SD service
advertised (and browsed for) by iTunes is "_daap._tcp" (Digital Audio
Access Protocol), not "_http._tcp".

If iTunes were to advertise that it offered "_http._tcp" service,
that would cause iTunes servers to appear in conventional web
browsers (Safari, Camino, OmniWeb?, Internet Explorer, Firefox,
Chrome, etc.), which is of little use since an iTunes music library
offers no HTML pages containing human-readable content that a web
browser could display.

Equally, if iTunes were to browse for "_http._tcp" service, that
would cause it to discover generic web servers, such as the embedded
web servers in devices like printers, which is of little use since
printers generally don't have much music to offer.

comment:2 Changed 8 years ago by mglt.ietf@…

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.