Return-Path: X-Original-To: kitten@ietfa.amsl.com Delivered-To: kitten@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD9E71A02EB for ; Mon, 24 Mar 2014 13:06:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.508 X-Spam-Level: X-Spam-Status: No, score=-1.508 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO_END_DIGIT=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QjLAw_DaEbhv for ; Mon, 24 Mar 2014 13:06:54 -0700 (PDT) Received: from nm19-vm0.bullet.mail.bf1.yahoo.com (nm19-vm0.bullet.mail.bf1.yahoo.com [98.139.213.162]) by ietfa.amsl.com (Postfix) with ESMTP id 5898B1A02EA for ; Mon, 24 Mar 2014 13:06:54 -0700 (PDT) Received: from [98.139.215.140] by nm19.bullet.mail.bf1.yahoo.com with NNFMP; 24 Mar 2014 20:06:53 -0000 Received: from [98.139.212.242] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 24 Mar 2014 20:06:53 -0000 Received: from [127.0.0.1] by omp1051.mail.bf1.yahoo.com with NNFMP; 24 Mar 2014 20:06:53 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 379288.51803.bm@omp1051.mail.bf1.yahoo.com Received: (qmail 12795 invoked by uid 60001); 24 Mar 2014 20:06:53 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1395691613; bh=jXaF9w7ON79g3GEpLfW+kBt6jteUmI5bTL0+CdlyavU=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=PRgKNzoX7O+ak6EiXTVYJ3XNxSgIsSw1RC/OSmaq6j2V5SiRlrBTRS8JVCNa7KY+LWrPONEwdWSDvbHL9yZ3aAxf5kSwM7RBPdNpHY4qyevD+YXewM841Nbsg53y35gn/ZoiTU5u7Mpg0c9a4qj4I9rHNEKigXjm6ERd7oUxSOU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=sV2vnKKr9gCcLRZnNYFxuZdtP9powyC/kaP4b+gFZxIjzLmZq4jM1R4gGB9IuDDIuoaBvlpzialgVQYww+hTJ6CF0jI623XB1tn6LMFIiOTGG037taQAU8q87N1VePEGeRPbiu5N+/5B6MroihTW0LbCfX/MNslj6csB+/J5c40=; X-YMail-OSG: NXKbMRQVM1kJEUv1xVM1fhlVgv93HHmIaNE7e1OOxaoaYcB ywtr3oRyD0X8e.deEZvtK4g34Wpv3m.zgE8QiF3m21SDGDnvqHAMtonqkR8O 3VHyzKQym75L2hdUDHsNT_ngTUgnUM5RPbzUndhxd.jL5oKSsj8xY81731pd TEOwtS2M1yiJRd4Kv9qOABP2EjjJSD3J36WR0rTOJ6UKLRjwupsWtX2KIGzK UhFRgm36_OXbIrnmr4HiLQ0tPrOrPwsuFaltMfuoZUOpEFDqmYKGxdL0N149 FSDCBa0bjRpdFO5DMzwGEUfgq0SWKBXz4nybLMkBmX5sefYvHVvYJeieR0G6 eZAE.TPNh8Bvh_bgfTQLLv_UCx6AkC2VBvVo7QIFSRqbW8HoLj_C8S2Gf5QY WwneuWI6S2tHU_DEtMcSRjWmLS7Ix82VzqMrocG.x3nv9meh8HkbCpwKCpFB fLjTl8arA0pl4MNfj_LMIp8QcEPLUdogiCvkvYzxpzCx2TQPuH6c2ofulrga JbnM2djAJGwI6VtG.nEVH.zEO0yOq41TWn_lMakBgDsvdGU_Ig59X4yOKWrz wkmfPP1DvUANNK6OSjHn4r_mZK3vwbMVZF9QQugTZaqt5Yl2GcSXu2t8jLNU czh4_PzvtElqumBkfpuU- Received: from [66.228.162.52] by web142803.mail.bf1.yahoo.com via HTTP; Mon, 24 Mar 2014 13:06:53 PDT X-Rocket-MIMEInfo: 002.001, R29vZ2xlIHVzZWQgWE9BVVRIIGZvciBpdCdzIG9yaWdpbmFsIE9BdXRoIDEuMGEgYmFzZWQgbWVjaGFuaXNtLiDCoFRoZXkgdXNlZCBYT0FVVEgyIHRvIHNwZWNpZmljYWxseSBub3QgY29uZmxpY3Qgd2l0aCB3aGF0ZXZlciBuYW1lIHdlIHN0YW5kYXJkaXplZCBvbiBmb3IgdGhlIG1lY2hhbmlzbSBhcyBzdGFuZGFyZGl6ZWQuCgpUaGV5IHBsYW4sIGFjY29yZGluZyB0byBSeWFuIHdobydzIGJlZW4gcGFydGljaXBhdGluZyBvbiBsaXN0LCB0byBpbXBsZW1lbnQgdGhlIHN0YW5kYXJkaXplZCBtZWNoYW5pc20BMAEBAQE- X-Mailer: YahooMailWebService/0.8.181.645 References: <53308872.9030305@cs.tcd.ie> <533088AB.203@cs.tcd.ie> Message-ID: <1395691613.66133.YahooMailNeo@web142803.mail.bf1.yahoo.com> Date: Mon, 24 Mar 2014 13:06:53 -0700 (PDT) From: Bill Mills To: Stephen Farrell , "oauth@ietf.org" , "kitten@ietf.org" , "iana-questions@ietf.corg" In-Reply-To: <533088AB.203@cs.tcd.ie> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="905790552-1643390876-1395691613=:66133" Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/jeQTR2rJOLzUHuwLPxYgAF5HvEk Subject: Re: [kitten] [OAUTH-WG] Fwd: [IANA #731918] SASL mechanism not listed X-BeenThere: kitten@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Bill Mills List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Mar 2014 20:06:56 -0000 --905790552-1643390876-1395691613=:66133 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Google used XOAUTH for it's original OAuth 1.0a based mechanism. =A0They us= ed XOAUTH2 to specifically not conflict with whatever name we standardized = on for the mechanism as standardized.=0A=0AThey plan, according to Ryan who= 's been participating on list, to implement the standardized mechanism defi= nition under the OAUTHBEARER mechanism name so there should be no conflict.= =0A=0ARegards,=0A=0A-bill=0A=0A=0A=0AOn Monday, March 24, 2014 12:34 PM, St= ephen Farrell wrote:=0A =0A=0ASee below. I thin= k (not quite sure) that this is better=0Adiscussed on the kitten list.=0A= =0ATa,=0AS.=0A=0A=0A=0A-------- Original Message --------=0ASubject: [kitte= n] [IANA #731918] SASL mechanism not listed=0ADate: Mon, 24 Mar 2014 19:33:= 06 +0000=0AFrom: Stephen Farrell =0ATo: kitten@i= etf.org =0ACC: iana-questions@iana.org =0A=0A=0AHiya,=0A=0AIANA were asked the following question a while ba= ck, but I=0Adropped the ball;-)=0A=0AI'd appreciate your thoughts on the ma= tter. I'm not quite=0Asure which registries are meant exactly though.=0A=0A= (I'll also forward to the oauth WG, but not cross-post)=0A=0AThanks,=0AS.= =0A=0A=0A=0AThe following draft describes a SASL mechanism that is i= n use on=0AGMail and should not therefore be allocated to another scheme un= less=0Awe want bad things to happen.=0A=0Ahttp://tools.ietf.org/id/draft-mu= rchison-sasl-login-00.txt=0A=0AThe strings XOAUTH and XOAUTH2 are also bein= g used for a preliminary=0Aversion of the OAUTH spec as well.=0A=0AThe reas= on Google is using this particular mechanism rather than=0APLAIN is that it= is the one that has the widest client support:=0A=0Ahttp://www.fehcom.de/q= mail/smtpauth.html=0A=0ASo it would be a real disaster if this particular c= ode point was re-issued.=0A=0AIt would probably be a good idea if every reg= istry had a list of 'dirty'=0Acode points that must not be reused because t= here are existing applications.=0A=0A=0A=0A___________________________= ____________________=0AKitten mailing list=0AKitten@ietf.org=0Ahttps://www.= ietf.org/mailman/listinfo/kitten=0A=0A=0A=0A=0A____________________________= ___________________=0AOAuth mailing list=0AOAuth@ietf.org=0Ahttps://www.iet= f.org/mailman/listinfo/oauth --905790552-1643390876-1395691613=:66133 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Google used XOAUTH for it's original OAuth 1.0a ba= sed mechanism.  They used XOAUTH2 to specifically not conflict with wh= atever name we standardized on for the mechanism as standardized.

They plan, according to Ryan w= ho's been participating on list, to implement the standardized mechanism de= finition under the OAUTHBEARER mechanism name so there should be no conflict.

Regards,

-bill


On Monday, March 24, 2014 12:34 PM, Stephen Farrell <= stephen.farrell@cs.tcd.ie> wrote:

See below. I think (not quite sure) that th= is is better
discussed on the kitten list.

Ta,
S.


-------- Original Message --------
Subject: [kitten] [IA= NA #731918] SASL mechanism not listed
Date: Mon, 24 Mar 2= 014 19:33:06 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>= ;
To: kitten@ietf.org <kitten@= ietf.org>
CC: iana-quest= ions@iana.org <iana-questions@iana.org= >


Hiya,

IANA were asked the following question a while= back, but I
dropped the ball;-)

I'd appreciate your thoughts on the matter. I'm not quite
sure which registries are meant exactly though.

(I'll also forward to the oauth WG, but not cross-post)

Tha= nks,
S.

<start>= ;

The following draft describes a SASL= mechanism that is in use on
GMail and should not therefo= re be allocated to another scheme unless
we want bad thin= gs to happen.

http://tools.ietf.org/id/draft-murchison-sasl-login-00.txt

The strings XOAUTH and XOAUTH2 are also bei= ng used for a preliminary
version of the OAUTH spec as we= ll.

The reason Google is using this pa= rticular mechanism rather than
PLAIN is that it is the on= e that has the widest client support:

= http:/= /www.fehcom.de/qmail/smtpauth.html

So it would be a real disaster if this particular code point was re-issued= .

It would probably be a good idea if = every registry had a list of 'dirty'
code points that mus= t not be reused because there are existing applications.
=
<end>

_______= ________________________________________
Kitten mailing l= ist
Kitten@ietf.org
https://www.ietf.org/mailman/listinfo/kitten





_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth=


--905790552-1643390876-1395691613=:66133--