Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard

To: Peter Saint-Andre <stpeter at stpeter.im>
Subject: Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard
From: Cullen Jennings <fluffy at cisco.com>
Date: Fri, 24 Aug 2007 14:44:41 -0700
Authentication-results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: ietf at ietf.org
Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=647; t=1187991963; x=1188855963; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20Last=20Call=3A=20draft-saintandre-jabberid=20(The=20J abber-ID=20Header=09Field)=20to=20Proposed=20Standard |Sender:=20; bh=kpxP6GwRK1pWNhYV0tqqGKjn6M9Yb9i4fnCluQmW/es=; b=tOIeoFuRYoBMrOHh1F3Va5U5mcx/XSPYlrMe8ns73jUWzDX8J4D+Wl9pxVDzOwgPN+Kig2/L a36SOHhByAr5cP79rdOhUfuWs0GvE++C+W+3FRmEVnzxVU7JSQzJkjPyrlFoW7RGZzuJ9z1lvO I1ShjPWZq/zNIF3uzxreHhoKU=;
In-reply-to: <46CF2146.3060704@stpeter.im>
List-help: <mailto:ietf-request@ietf.org?subject=help>
List-id: IETF-Discussion <ietf.ietf.org>
List-post: <mailto:ietf@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
References: <E1IOZZ3-00085A-EY@stiedprstage1.ietf.org> <74CEC9E0-043B-4F3A-AE7C-D03DED5A8DAB@cisco.com> <46CF2146.3060704@stpeter.im>


On Aug 24, 2007, at 11:19 AM, Peter Saint-Andre wrote:

Cullen Jennings wrote:
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.com
Another approach, naturally, would be to define a header field for
including an im: URI and/or one for including a pres: URI. That seems
fairly straightforward.
Peter


Sure - that works for me too.

BTW - I do like the basic idea of the draft - I just prefer the more general form of it.

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

References:
- Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard
  - From: Cullen Jennings
- Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard
  - From: Peter Saint-Andre

Prev by Date: Re: IPv6 addresses really are scarce after all
Next by Date: Re: IPv6 addresses really are scarce after all
Previous by thread: Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard
Next by thread: When will ISP's switch over to IPv6 and how will it affect customers?
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.