J D Falk wrote: > Jim Fenton wrote: > > >>> At best, the benefit of having s= defined now depends on whether >>> people are setting s=email now. Are they? Should they? How will >>> they know? >>> >> Are they: I haven't seen a key with s=email yet, although I'll have >> to admit that I don't look at a lot of selectors. >> > > I have. Also s=mail, s=mx, s=mta23, s=domainkeys, and other strings > that our more-or-less human brains might want to interpret as carrying > additional meaning. > > I haven't, however, seen any indication that those strings were chosen > with the intention of also having s=usenet, s=rss, s=sip, > s=antidisestablishmentarianism, or other indicators that a specific > selector would be used solely for non-email purposes. >
Are you perhaps confusing s= in the signature (selector name) with s= in the key record (service type)? It's the latter that we're discussing. -Jim _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
