Re: [webrtc-pc] OAUTH-POP-KEY-DISTRIBUTION IETF draft has been replaced by ACE-CWT-PROOF-OF-POSSESSION

https://datatracker.ietf.org/doc/draft-ietf-oauth-pop-architecture/history/
shows the draft was ready from the WG and was sent to ISEG review (Security
AD had approved the spec).
You may want to contact Hannes Tschofenig (OAuth WG) chair to figure out
the actual reason.

Cheers,
-Tiru

On 22 March 2018 at 14:38, Mészáros Mihály <notifications@github.com> wrote:

> I think decision has made. => PR needed.
> @alvestrand <https://github.com/alvestrand> will you make it, or shall I
> make it?
>
> @tireddy2 <https://github.com/tireddy2>
> From WebRTC + RFC7635 point of view I still miss an RFC that describes the
> OAuth PoP key distribution over HTTP. As it was mentioned
> draft-ietf-oauth-pop-key-distribution-03 draft is no longer active.
> I understand that OAuth PoP key distribution interest is moved to COAP,
> but I don't know why the HTTP OAuth PoP isn't it finished => dead.
> I know HTTP in a constrained env is to expensive, but for a system that
> encodes media http shouldn't be a problem.
> Correct me if I am wrong, but according RFC7635 Appendix example, and
> because WebRTC is strongly related to browsers, so I feel that we are still
> interested in OAuth PoP key distribution over HTTP.
>
> OAuth Client<=>AS communication over HTTP
>
> On the wire:
>
>    - either RFC7635 or CWT token
>    - kid
>    - session key
>
> IMHO Key distribution over COAP does not fit perfectly, complicates more
> the communication, and so I prefer to use HTTP.
>
> Could you shade on it light, or point me where I could find more
> information about why OAuth PoP over HTTP idea is not finished and totally
> dropped?
>
> Thanks in advance!
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webrtc-pc/issues/1642#issuecomment-375329541>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AddeEmXfUnoFhZxZDKMnaCWvHKs0_hp0ks5tg7dzgaJpZM4QDBTz>
> .
>


-- 
GitHub Notification of comment by tireddy2
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1642#issuecomment-375849540 using your GitHub account

Received on Saturday, 24 March 2018 05:59:52 UTC