Re: [Standards] jabber-id email header
+1 from Japan as well :-) Yusuke (2013-09-21 07:22), Joachim Lindborg wrote: +1 from sweden as well. 2013/9/20 Alexey Melnikov alexey.melni...@isode.com mailto:alexey.melni...@isode.com On 20/09/2013 03:44, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/__draft-saintandre-jabberid-08.__txt http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Can you do an Independent submission to RFC Editor? You already have a draft... Is there still interest in registering this header? Yes yes yes :-). -- Regards Joachim Lindborg CTO, systems architect Sustainable Innovation AB Adress: Box 55998 102 16 Stockholm Besöksadress: Storgatan 31 (Malmgården) Email: joachim.lindb...@sust.se mailto:joachim.lindb...@sust.se, www.sust.se http://www.sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270
Re: [Standards] jabber-id email header
On 20 Sep 2013, at 16:12, Peter Saint-Andre stpe...@stpeter.im wrote: On 9/20/13 8:25 AM, Alexey Melnikov wrote: On 20/09/2013 03:44, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Can you do an Independent submission to RFC Editor? You already have a draft... Now that I think about it, I might resurrect this as an I-D and get it published as an RFC. I last pursued this back in 2007 when everyone (well, some influential people at the IETF) thought that the world would switch to using 'im:' and 'pres:' URIs. That hasn't exactly happened. :-) Indeed. And I remember some people who didn't like the idea.
Re: [Standards] jabber-id email header
Mike Taylor wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/19/2013 10:44 PM, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Is there still interest in registering this header? I'm +1 for this because it will make sense when we start using our JID as an identity marker. Oh, I'd forgotten this was only an I-D, I'd thought it was a proper spec. So yes, +1 for sorting this. I might even implement it. Sent with [inky: http://inky.com?kme=signature]
Re: [Standards] jabber-id email header
On 20 September 2013 03:44, Peter Saint-Andre stpe...@stpeter.im wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Is there still interest in registering this header? A very big +1. Regards, Matthew Sent without blotting paper
Re: [Standards] jabber-id email header
On 20/09/2013 03:44, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Can you do an Independent submission to RFC Editor? You already have a draft... Is there still interest in registering this header? Yes yes yes :-).
Re: [Standards] jabber-id email header
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/20/13 8:25 AM, Alexey Melnikov wrote: On 20/09/2013 03:44, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Can you do an Independent submission to RFC Editor? You already have a draft... Now that I think about it, I might resurrect this as an I-D and get it published as an RFC. I last pursued this back in 2007 when everyone (well, some influential people at the IETF) thought that the world would switch to using 'im:' and 'pres:' URIs. That hasn't exactly happened. :-) Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSPGXmAAoJEOoGpJErxa2pSXcQAJ8AXKNfP9fxRv6Yi7Ohr9r0 g805cRvlAvd+ehdIhuqodr8B6MCLZFHzmZqRWpJtmvf+ZKGD1+Ja7xc8PcqYALez vX/HV1RrUEpzmr97lslXufDXtKzP3DLfU8G7/psF4IpeCaDdWCukOVXzP99VNGw+ +4QwTGvri9UVvlwnUOf+CX2qegxMdFFQ/pImYrm0fI82zs28+ebgx5G4/AsldsEN HZgqIZXyzrBfECFnosvwagc+vEsLGCp1mWm9Yoys/EdCOK+X+bokecquiDanwnvo PIl8JA4PQHRvzTQcu3F/a68iHajqsBspdbzZ5E5SSJddEySDNG0ZYaXaRuidDHbF 6BeHyxvTwtVH/g/7sS9e3A7r7mVSU+glohF3nNmcgU9N6p9JlCmI/ipZ7CBqU0x2 kT+h3YvnoMHJAanU6plNmVoZohWlIa6fO/bJZXYDNxf82fLCP+3ECuW24V9jfUc6 dwR7ghfyD4CNK6HRA+TyWjibgOqRFqifhYTP2UvBwHg/RZBodbNN9uYIc3DzZr6K k+qeqP729n6Z7Anv02bOkR6tmWFPNWx22/+89+1t8oQrt1/vy4Jc/n2jslegmJvA U2JhjweYJxd7dz/phQHIGBs+Pe2HLCF3UsxxKl00YpDy1+wsLWiYHGSVHpObMlRd JomTihLmN6QuPiH94Zuj =Dn5j -END PGP SIGNATURE-
Re: [Standards] jabber-id email header
Not sure what this JabberID thing is Has anyone thought of putting your XMPP-ID into an email header? Now that would be awesome! S. On 20 September 2013 17:12, Peter Saint-Andre stpe...@stpeter.im wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/20/13 8:25 AM, Alexey Melnikov wrote: On 20/09/2013 03:44, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Can you do an Independent submission to RFC Editor? You already have a draft... Now that I think about it, I might resurrect this as an I-D and get it published as an RFC. I last pursued this back in 2007 when everyone (well, some influential people at the IETF) thought that the world would switch to using 'im:' and 'pres:' URIs. That hasn't exactly happened. :-) Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSPGXmAAoJEOoGpJErxa2pSXcQAJ8AXKNfP9fxRv6Yi7Ohr9r0 g805cRvlAvd+ehdIhuqodr8B6MCLZFHzmZqRWpJtmvf+ZKGD1+Ja7xc8PcqYALez vX/HV1RrUEpzmr97lslXufDXtKzP3DLfU8G7/psF4IpeCaDdWCukOVXzP99VNGw+ +4QwTGvri9UVvlwnUOf+CX2qegxMdFFQ/pImYrm0fI82zs28+ebgx5G4/AsldsEN HZgqIZXyzrBfECFnosvwagc+vEsLGCp1mWm9Yoys/EdCOK+X+bokecquiDanwnvo PIl8JA4PQHRvzTQcu3F/a68iHajqsBspdbzZ5E5SSJddEySDNG0ZYaXaRuidDHbF 6BeHyxvTwtVH/g/7sS9e3A7r7mVSU+glohF3nNmcgU9N6p9JlCmI/ipZ7CBqU0x2 kT+h3YvnoMHJAanU6plNmVoZohWlIa6fO/bJZXYDNxf82fLCP+3ECuW24V9jfUc6 dwR7ghfyD4CNK6HRA+TyWjibgOqRFqifhYTP2UvBwHg/RZBodbNN9uYIc3DzZr6K k+qeqP729n6Z7Anv02bOkR6tmWFPNWx22/+89+1t8oQrt1/vy4Jc/n2jslegmJvA U2JhjweYJxd7dz/phQHIGBs+Pe2HLCF3UsxxKl00YpDy1+wsLWiYHGSVHpObMlRd JomTihLmN6QuPiH94Zuj =Dn5j -END PGP SIGNATURE- -- Simon Tennant | buddycloud.com | +49 17 8545 0880 | office hours: goo.gl/tQgxP
Re: [Standards] jabber-id email header
Simon Tennant si...@buddycloud.com schrieb: Not sure what this JabberID thing is Has anyone thought of putting your XMPP-ID into an email header? Now that would be awesome! S. On 20 September 2013 17:12, Peter Saint-Andre stpe...@stpeter.im wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/20/13 8:25 AM, Alexey Melnikov wrote: On 20/09/2013 03:44, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Can you do an Independent submission to RFC Editor? You already have a draft... Now that I think about it, I might resurrect this as an I-D and get it published as an RFC. I last pursued this back in 2007 when everyone (well, some influential people at the IETF) thought that the world would switch to using 'im:' and 'pres:' URIs. That hasn't exactly happened. :-) Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSPGXmAAoJEOoGpJErxa2pSXcQAJ8AXKNfP9fxRv6Yi7Ohr9r0 g805cRvlAvd+ehdIhuqodr8B6MCLZFHzmZqRWpJtmvf+ZKGD1+Ja7xc8PcqYALez vX/HV1RrUEpzmr97lslXufDXtKzP3DLfU8G7/psF4IpeCaDdWCukOVXzP99VNGw+ +4QwTGvri9UVvlwnUOf+CX2qegxMdFFQ/pImYrm0fI82zs28+ebgx5G4/AsldsEN HZgqIZXyzrBfECFnosvwagc+vEsLGCp1mWm9Yoys/EdCOK+X+bokecquiDanwnvo PIl8JA4PQHRvzTQcu3F/a68iHajqsBspdbzZ5E5SSJddEySDNG0ZYaXaRuidDHbF 6BeHyxvTwtVH/g/7sS9e3A7r7mVSU+glohF3nNmcgU9N6p9JlCmI/ipZ7CBqU0x2 kT+h3YvnoMHJAanU6plNmVoZohWlIa6fO/bJZXYDNxf82fLCP+3ECuW24V9jfUc6 dwR7ghfyD4CNK6HRA+TyWjibgOqRFqifhYTP2UvBwHg/RZBodbNN9uYIc3DzZr6K k+qeqP729n6Z7Anv02bOkR6tmWFPNWx22/+89+1t8oQrt1/vy4Jc/n2jslegmJvA U2JhjweYJxd7dz/phQHIGBs+Pe2HLCF3UsxxKl00YpDy1+wsLWiYHGSVHpObMlRd JomTihLmN6QuPiH94Zuj =Dn5j -END PGP SIGNATURE- No, it is a Jabber-ID. The user handle has been called JID forever, and it makes sense, because it identifies you in the network of federated XMPP-capable servers. The Jabber-ID carries an xmpp protocol schema. On a side note, +1 for the header!
Re: [Standards] jabber-id email header
On Fri, 20 Sep 2013 17:56:41 +0200 Dominik George n...@naturalnet.de wrote: Simon Tennant si...@buddycloud.com schrieb: Not sure what this JabberID thing is Has anyone thought of putting your XMPP-ID into an email header? Now that would be awesome! S. On 20 September 2013 17:12, Peter Saint-Andre stpe...@stpeter.im wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/20/13 8:25 AM, Alexey Melnikov wrote: On 20/09/2013 03:44, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Can you do an Independent submission to RFC Editor? You already have a draft... Now that I think about it, I might resurrect this as an I-D and get it published as an RFC. I last pursued this back in 2007 when everyone (well, some influential people at the IETF) thought that the world would switch to using 'im:' and 'pres:' URIs. That hasn't exactly happened. :-) Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSPGXmAAoJEOoGpJErxa2pSXcQAJ8AXKNfP9fxRv6Yi7Ohr9r0 g805cRvlAvd+ehdIhuqodr8B6MCLZFHzmZqRWpJtmvf+ZKGD1+Ja7xc8PcqYALez vX/HV1RrUEpzmr97lslXufDXtKzP3DLfU8G7/psF4IpeCaDdWCukOVXzP99VNGw+ +4QwTGvri9UVvlwnUOf+CX2qegxMdFFQ/pImYrm0fI82zs28+ebgx5G4/AsldsEN HZgqIZXyzrBfECFnosvwagc+vEsLGCp1mWm9Yoys/EdCOK+X+bokecquiDanwnvo PIl8JA4PQHRvzTQcu3F/a68iHajqsBspdbzZ5E5SSJddEySDNG0ZYaXaRuidDHbF 6BeHyxvTwtVH/g/7sS9e3A7r7mVSU+glohF3nNmcgU9N6p9JlCmI/ipZ7CBqU0x2 kT+h3YvnoMHJAanU6plNmVoZohWlIa6fO/bJZXYDNxf82fLCP+3ECuW24V9jfUc6 dwR7ghfyD4CNK6HRA+TyWjibgOqRFqifhYTP2UvBwHg/RZBodbNN9uYIc3DzZr6K k+qeqP729n6Z7Anv02bOkR6tmWFPNWx22/+89+1t8oQrt1/vy4Jc/n2jslegmJvA U2JhjweYJxd7dz/phQHIGBs+Pe2HLCF3UsxxKl00YpDy1+wsLWiYHGSVHpObMlRd JomTihLmN6QuPiH94Zuj =Dn5j -END PGP SIGNATURE- No, it is a Jabber-ID. The user handle has been called JID forever, and it makes sense, because it identifies you in the network of federated XMPP-capable servers. The Jabber-ID carries an xmpp protocol schema. On a side note, +1 for the header! Agreed. -- Proper English www.reddit.com/r/proper 4 teh lulz... http://email.is-not-s.ms can i haz... http://jabber.is-not-s.ms
Re: [Standards] jabber-id email header
+1 from sweden as well. 2013/9/20 Alexey Melnikov alexey.melni...@isode.com On 20/09/2013 03:44, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/**draft-saintandre-jabberid-08.**txthttp://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Can you do an Independent submission to RFC Editor? You already have a draft... Is there still interest in registering this header? Yes yes yes :-). -- Regards Joachim Lindborg CTO, systems architect Sustainable Innovation AB Adress: Box 55998 102 16 Stockholm Besöksadress: Storgatan 31 (Malmgården) Email: joachim.lindb...@sust.se, www.sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270
[Standards] jabber-id email header
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Is there still interest in registering this header? Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSO7Z/AAoJEOoGpJErxa2ppZwP/Am8BLYtfV66ilG73VcF4C+L G1Hepp+zHOQTpdXo3Mmr0HkNXPsaLywzjHsNx8eqLkaD2VKvCvpptgF07EvKyzPJ JKLws5Mif8UJtsUhlnLD3kqx80SnQStKcmqZLKxz20qfD0OZA4Nc16o6QmvAVXjc 1Vnja5t34eIOUJbjgeMXZzMkeservCRo5CAqNZceN2KjIc6oHYUYUGC2Qfl1FlNP kaLikEEmCmomVyVHmix/sDLOg6+p5OdyL0JlNm2gInuoNhp3pQ3XG5XcjzMWXkRG WC8175u6Dh05Lxl7uMYFhp7AvZHzV/FF3KWKBLNHONzro4aubaI95d7Z5vgYl3Kr T/8RsoPCXyg76Zdhd+Wnhxd3vE72NwX2qx+15jAL8/NAis6IDPCmpuH12kH4WXLG ZR+8GRrWIJ0bJflW+9Sxnpze0PZsBuNtgsp6MEfqC1Z+xRlqIABJPtBLQbM2KM8J slCRizf15ovK44/lcc4NfxtzB4MybRDu/ZuQIwZROk489s77sJLlPmJ4/8CQnKUV xctk6iDwYw0PtwudyyDu1FbtgYSn55A53nbISaBLD/dMjiwfwWgGr1czNgMYDlie baPmnKRpyP260OPK0zcukX/XpeWZL+VhxpJ0aX055T+hevz82iOedkIc54cbgsEG FIUzWgwWfNNmzy8hCUb5 =Ma0/ -END PGP SIGNATURE-
Re: [Standards] jabber-id email header
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/19/2013 10:44 PM, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Is there still interest in registering this header? I'm +1 for this because it will make sense when we start using our JID as an identity marker. Peter - -- bear xmpp agitator; ops curmudgeon; generalist http://bear.im/about http://bear.im/pubkey.txt 0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSO8n3AAoJEJ0eBmGO5bTYPcAP/3iRndy23n5F3wffuyBui3N+ fhATlKplUWInsXJkNtZYVilckLy4QfdLJXo3wE2SeQfjM/6U92kZvXFPahxMnOEm Whv6vq2pf2LVYaXsHkdc2+I4bNpOsenWMrp99uyneQ7hdU58q/5PdbFu5o8IVezb 0Y33c6iEa3qw2jAYCUFvOBUeBe4UXIcgZh4AU9D/48h3tV5aQXEcQV7sMZA44eXO EhuphezJoPLBMq0DpqwyJhd63kVGtdXpMlI6g4z8q0C4FrqBCT0xkKbT444PBWdc qUWg4eAumb3CIs3/wxVF9SKfuUKkq7bFOphydbISWhGxuKexqyuD6RBwRb9MnACJ +gwMbA27FCIRPGX5VGVAhbGuNIXb3EGsuLRg06k5vxAWhTJ5o4S3kDGQPpqyJ812 Xajb+ptUft1l6o/gUhnroHCSMGvksStyeSq2kkMyg6PJoudBicpImoYb3+8aKT0k KF9U46oupwiqny4Irt3jcRT1R8HbGGT2EauuiM1hGgzEYIFw/TPOutlBT1XL3WSt BZz0IpUMmOsvRYY12PmXEfomMHCKHNJdN5o1mxQnv1QgP/S7GoaVIwx5YKdBGjox cYtBncChVtfg6O24fzsmU1dcYKdtF2vmjcFg65DStUpc22ZSjuzzqw0M1/KY1sb8 slsGrvQfUxYmPKygzSaJ =+cc6 -END PGP SIGNATURE-
