I think a much better design would be one that supported many
protocols and took advantage of the flexibility or URIs instead of
just jabber - for example a header that looked like
IMPP: xmpp:juliet(_at_)example(_dot_)com
The way we did vcard might be a good thing to look at, or heck, just
attach a vcard.
(sorry for few of you that got duplicate on this - sent to wrong list
first time)
On Aug 24, 2007, at 6:51 AM, The IESG wrote:
The IESG has received a request from an individual submitter to
consider
the following document:
- 'The Jabber-ID Header Field '
<draft-saintandre-jabberid-05.txt> as a Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to
the
ietf(_at_)ietf(_dot_)org mailing lists by 2007-09-21. Exceptionally,
comments may be sent to iesg(_at_)ietf(_dot_)org instead. In either case, please
retain the beginning of the Subject line to allow automated sorting.
The file can be obtained via
http://www.ietf.org/internet-drafts/draft-saintandre-jabberid-05.txt
IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?
command=view_id&dTag=14260&rfc_flag=0
_______________________________________________
IETF-Announce mailing list
IETF-Announce(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf