On 3/20/17 4:23 PM, Dave Cridland wrote:
> On 20 March 2017 at 22:04, Florian Schmaus <[email protected]> wrote:
>> On 20.03.2017 22:32, Dave Cridland wrote:
>>> Loosely, this is OK, but, in order:
>>>
>>> 1) Section 6 must go. I don't believe that the XSF has the required
>>> expertise to adequately review a SASL mechanism. I'm saying this
>>> without commenting on the mechanism described in Section 6. This needs
>>> to go through the IETF (this document can reference any particular
>>> SASL mechanism for MTI it likes, including this one). The right
>>> working group is - probably - Kitten, though traditionally XMPP itself
>>> works through the ART area, and we might want to give an ART AD or two
>>> a heads-up. This issue is a blocker for me.
>>
>> Section 6. was written in mind being probably factored out. So I'm happy
>> to bring this to the IETF. Anyone who wants to shepherd me?
>>
> 
> I'm confident we can find a shepherd, but I can do that if we need
> one. (Assuming you actually do mean a Document Shepherd).

I doubt that Florian knows all about the special lingo of the IETF. ;-)

But yes, it's important to have someone who can guide you through the
labyrinth.

> Incidentally, I think a token-based SASL mechanism might be generally
> useful; 

We already have a token-based authentication mechanism for OAuth 2
<https://datatracker.ietf.org/doc/rfc7628/> but perhaps that's not what
you had in mind...

> Surevine could use one if it existed, certainly. It's useful
> to have a device-specific token which can then be managed and/or
> revoked, independent of ISR - this implies a multiple-use token rather
> than a single-use one, however. I have a vague feeling that something
> based around a fusion of HOTP and YAP might yield something that
> satisfies this. If you're open to the idea, I'll outline a quick
> design.

Do tell. :-)

Peter

_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to