Opened 10 years ago

Closed 10 years ago

#179 closed enhancement (fixed)

draft-iab-dns-applications-05 is a bit short on alternatives

Reported by: bortzmeyer+ietf@… Owned by: jon.peterson@…
Priority: minor Milestone: milestone1
Component: draft-iab-dns-applications Version: 1.0
Severity: Active WG Document Keywords:
Cc:

Description

draft-iab-dns-applications-05 repeats several times that the DNS is not the ideal solution for every problem requiring a distributed database but it mentions no alternatives besides HTTP. Saying "Ultimately, this document concludes that efforts to retrofit these capabilities into the DNS would be better invested in selecting, or if necessary inventing, other Internet services with broader powers than the DNS" does not help since it is obviously a lot of work to invent something new.

If the DNS is used, it is because it works and works well. When the IAB writes "The overhead of
using HTTP may not be appropriate for all environments, but even in environments where a more lightweight protocol is appropriate, DNS is not the only alternative", it would be more convincing if at least one such alternative were mentioned. (LDAP ? whois ? HTTP-over-UDP, like Call of Duty does?)

Change History (3)

comment:1 Changed 10 years ago by bernard_aboba@…

  • Component changed from /home/ietf/id/draft-iab-dns-applications-05.txt to draft-iab-dns-applications
  • Milestone set to milestone1
  • Owner changed from draft-iab-dns-applications@… to jon.peterson@…
  • Severity changed from - to Active WG Document
  • Version set to 1.0

comment:2 Changed 10 years ago by jon.peterson@…

Added some text in -07 to clarify that there are trade-offs to the use of application layer protocols, and tried to remove any connotation that this advocates for weird tunneling or exclusive use of HTTP.

comment:3 Changed 10 years ago by jon.peterson@…

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