Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-23.txt> (The OAuth 2.0 Authorization Protocol) to Proposed StandardRe: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-23.txt> (The OAuth 2.0 Authorization Protocol) to Proposed Standard
Barry Leiba
2012-01-23
oauth
/arch/msg/oauth/OrBhbOoqIqzvrY2yQjqIqwTrUUA/
1084324
1527775
Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed StandardRe: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard
Julian Reschke
2012-01-23
oauth
/arch/msg/oauth/NgtTFJ3TaAxuJ9yi4VKV9k6ZCXA/
1084323
1527774
Re: [OAUTH-WG] OAuth specs in IETF last callRe: [OAUTH-WG] OAuth specs in IETF last call
Mike Jones
2012-01-23
oauth
/arch/msg/oauth/-rFcy7ataRjA8x9VSyPBosnmgdE/
1084322
1527773
Re: [OAUTH-WG] OAuth specs in IETF last callRe: [OAUTH-WG] OAuth specs in IETF last call
Peter Saint-Andre
2012-01-23
oauth
/arch/msg/oauth/juJR3G_DmETiuPAKUt2ivg3d41k/
1084321
1527773
Re: [OAUTH-WG] OAuth specs in IETF last callRe: [OAUTH-WG] OAuth specs in IETF last call
Stephen Farrell
2012-01-23
oauth
/arch/msg/oauth/CjMywlZf8i08fY4b4W-KVI62MeA/
1084320
1527773
Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed StandardRe: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard
Mike Jones
2012-01-23
oauth
/arch/msg/oauth/CGWaNTvPYeQp-sYlV_Zl1LognN8/
1084319
1527774
[OAUTH-WG] OAuth specs in IETF last call[OAUTH-WG] OAuth specs in IETF last call
Mike Jones
2012-01-23
oauth
/arch/msg/oauth/37HWfjCLvwd2_V2Fq4724uj_i3g/
1084318
1527773
Re: [OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client requestRe: [OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client request
Justin Richer
2012-01-23
oauth
/arch/msg/oauth/okscK1yjNCXrjw7tREg32ORP_xQ/
1084317
1527781
Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed StandardRe: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard
Julian Reschke
2012-01-23
oauth
/arch/msg/oauth/n05dhtGRltEF5AIrAfmdnJ2-UYc/
1084316
1527774
[OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard[OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard
The IESG
2012-01-23
oauth
/arch/msg/oauth/7ISVr43hjT3gpVxFomsgtKnWFCc/
1084315
1527774
[OAUTH-WG] Last Call: <draft-ietf-oauth-v2-23.txt> (The OAuth 2.0 Authorization Protocol) to Proposed Standard[OAUTH-WG] Last Call: <draft-ietf-oauth-v2-23.txt> (The OAuth 2.0 Authorization Protocol) to Proposed Standard
The IESG
2012-01-23
oauth
/arch/msg/oauth/w4_WulHyq2kVsmTI2QRVV6G3Ioc/
1084314
1527775
Re: [OAUTH-WG] Seeking Clarification: Potential Ambiguity in SpecificationRe: [OAUTH-WG] Seeking Clarification: Potential Ambiguity in Specification
Eran Hammer
2012-01-23
oauth
/arch/msg/oauth/TGtxyPPocQ9oe5owuSCypP9Ggb4/
1084313
1527786
Re: [OAUTH-WG] Seeking Clarification: Potential Ambiguity in SpecificationRe: [OAUTH-WG] Seeking Clarification: Potential Ambiguity in Specification
Andreas Åkre Solberg
2012-01-23
oauth
/arch/msg/oauth/s78XtMOMlKb5kC2E88xqmvLm_pI/
1084312
1527786
Re: [OAUTH-WG] AD Review of -22 (part III)Re: [OAUTH-WG] AD Review of -22 (part III)
Stephen Farrell
2012-01-21
oauth
/arch/msg/oauth/dDXAgizVDarOD_PbY9WixtHR_DQ/
1084311
1527777
Re: [OAUTH-WG] Seeking Clarification: Potential Ambiguity in SpecificationRe: [OAUTH-WG] Seeking Clarification: Potential Ambiguity in Specification
William Mills
2012-01-21
oauth
/arch/msg/oauth/AR_ocUcjydldhVmNkFhAW4IcRVM/
1084310
1527786
Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-23.txtRe: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-23.txt
Eran Hammer
2012-01-21
oauth
/arch/msg/oauth/ZowoNFIbV8mjicWK0TTqvZPTREQ/
1084309
1527776
[OAUTH-WG] I-D Action: draft-ietf-oauth-v2-23.txt[OAUTH-WG] I-D Action: draft-ietf-oauth-v2-23.txt
internet-drafts
2012-01-21
oauth
/arch/msg/oauth/UM_2POkJ1mJd05n00Kskq60aDxA/
1084308
1527776
Re: [OAUTH-WG] AD Review of -22 (part III)Re: [OAUTH-WG] AD Review of -22 (part III)
Eran Hammer
2012-01-21
oauth
/arch/msg/oauth/YIJrtVIhH2jeVM5ZP53UkNfgSso/
1084307
1527777
Re: [OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client requestRe: [OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client request
John Bradley
2012-01-21
oauth
/arch/msg/oauth/mgF1MRKpyjCKANIEhatmp5r-RBA/
1084306
1527781
Re: [OAUTH-WG] AD Review of -22 (part II)Re: [OAUTH-WG] AD Review of -22 (part II)
Stephen Farrell
2012-01-21
oauth
/arch/msg/oauth/aw2_aNTSASbAwtiK6F3AtHCqd0w/
1084305
1527778
Re: [OAUTH-WG] AD Review of -22 (part II)Re: [OAUTH-WG] AD Review of -22 (part II)
Eran Hammer
2012-01-21
oauth
/arch/msg/oauth/E9cSDwQy2WfSI5r0CTUwLzN8bwU/
1084304
1527778
Re: [OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client requestRe: [OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client request
Igor Faynberg
2012-01-21
oauth
/arch/msg/oauth/xOUZdt4m3dekavt-57zoQ769BzQ/
1084303
1527781
Re: [OAUTH-WG] AD Review of -22 (part I)Re: [OAUTH-WG] AD Review of -22 (part I)
Stephen Farrell
2012-01-21
oauth
/arch/msg/oauth/QceJUYkwIJCiLfBeLMGWLb-CYEw/
1084302
1527779
Re: [OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client requestRe: [OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client request
Dick Hardt
2012-01-20
oauth
/arch/msg/oauth/zvivsfGeSHbKNDq5sJhD3QRiBaY/
1084301
1527781
Re: [OAUTH-WG] AD Review of -22 (part I)Re: [OAUTH-WG] AD Review of -22 (part I)
Eran Hammer
2012-01-20
oauth
/arch/msg/oauth/VfG5ItcL8n6Imyf5eWL4i3ytKXo/
1084300
1527779
[OAUTH-WG] Server cret verification in 10.9[OAUTH-WG] Server cret verification in 10.9
Eran Hammer
2012-01-20
oauth
/arch/msg/oauth/L81Tvm_p4II_YqN-_Xi7k11vUoU/
1084299
1527780
Re: [OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client requestRe: [OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client request
Torsten Lodderstedt
2012-01-20
oauth
/arch/msg/oauth/l0wtutcU6OVN_Rq8VGcs93JYIbk/
1084298
1527781
[OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client request[OAUTH-WG] SHOULD vs MUST for indicating scope on response when different from client request
Eran Hammer
2012-01-20
oauth
/arch/msg/oauth/m3qFzPi1ALpnf1sA8D5PT9nOWW4/
1084297
1527781
Re: [OAUTH-WG] TLS version requirements in OAuth 2.0 baseRe: [OAUTH-WG] TLS version requirements in OAuth 2.0 base
Igor Faynberg
2012-01-20
oauth
/arch/msg/oauth/wkxwMq-pKCQpt8u1hlCL3ofl7AE/
1084296
1527818
Re: [OAUTH-WG] Seeking Clarification: Potential Ambiguity in SpecificationRe: [OAUTH-WG] Seeking Clarification: Potential Ambiguity in Specification
Igor Faynberg
2012-01-20
oauth
/arch/msg/oauth/j4K05B87V3CnN272PU2_tiql_wA/
1084295
1527786
Re: [OAUTH-WG] TLS version requirements in OAuth 2.0 baseRe: [OAUTH-WG] TLS version requirements in OAuth 2.0 base
Barry Leiba
2012-01-20
oauth
/arch/msg/oauth/INxf79mCPtPEAqNe-rLdRoqRLFI/
1084294
1527818
Re: [OAUTH-WG] Seeking Clarification: Potential Ambiguity in SpecificationRe: [OAUTH-WG] Seeking Clarification: Potential Ambiguity in Specification
Eran Hammer
2012-01-20
oauth
/arch/msg/oauth/yChnHFAU733qeIuCvOSsrI_7H1s/
1084293
1527786
Re: [OAUTH-WG] TLS version requirements in OAuth 2.0 baseRe: [OAUTH-WG] TLS version requirements in OAuth 2.0 base
Eran Hammer
2012-01-20
oauth
/arch/msg/oauth/2-Em2rt1nudc4T-eQdbaniag5As/
1084292
1527818
Re: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1 and extension response types (8.4)Re: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1 and extension response types (8.4)
Eran Hammer
2012-01-20
oauth
/arch/msg/oauth/72VBOVGRW4H7kOrjkWdrjWC7BJ8/
1084291
1527827
Re: [OAUTH-WG] Error code for access token requestRe: [OAUTH-WG] Error code for access token request
Eran Hammer
2012-01-19
oauth
/arch/msg/oauth/n71w1LCkS_WKSuEH6fSdTNBTro0/
1084290
1527792
Re: [OAUTH-WG] Access Token Response without expires_inRe: [OAUTH-WG] Access Token Response without expires_in
Justin Richer
2012-01-19
oauth
/arch/msg/oauth/uLtOiRuGQtS5f2rs8ksvhmCvQAI/
1084289
1527783
Re: [OAUTH-WG] Error code for access token requestRe: [OAUTH-WG] Error code for access token request
Antonio Sanso
2012-01-19
oauth
/arch/msg/oauth/fljJMOZDVkxcOtgkrSJrhljrDy4/
1084288
1527792
[OAUTH-WG] Fwd: Smart Object Security Workshop Announcement[OAUTH-WG] Fwd: Smart Object Security Workshop Announcement
Hannes Tschofenig
2012-01-19
oauth
/arch/msg/oauth/-f5V1IR3D6lGcOW7lEDO7WnKiTQ/
1084287
1527782
Re: [OAUTH-WG] Access Token Response without expires_inRe: [OAUTH-WG] Access Token Response without expires_in
Paul Madsen
2012-01-18
oauth
/arch/msg/oauth/Ciy4-zt_S69JfEDBLtDKZvcN4tk/
1084286
1527783
Re: [OAUTH-WG] Access Token Response without expires_inRe: [OAUTH-WG] Access Token Response without expires_in
Torsten Lodderstedt
2012-01-18
oauth
/arch/msg/oauth/ychfRfgz9FrBa6jkAXcOzs4wMGo/
1084285
1527783
40 Messages