Skip to main content

The 'leaptofrogans' URI Scheme
draft-op3ft-leaptofrogans-uri-scheme-07

Yes

(Alexey Melnikov)

No Objection

(Alvaro Retana)
(Deborah Brungard)
(Martin Vigoureux)
(Spencer Dawkins)
(Suresh Krishnan)

Abstain


Note: This ballot was opened for revision 04 and is now closed.

Warren Kumari
No Objection
Comment (2019-02-06 for -06) Not sent
I personally have some concerns about some of the frogans technologies (mainly around the International Frogans Address Pattern (IFAP) bits), but that has nothing to do with this document. 
No objections, no comments.
Alexey Melnikov Former IESG member
Yes
Yes (for -04) Unknown

                            
Adam Roach Former IESG member
(was Discuss) No Objection
No Objection (2019-02-05 for -06) Sent for earlier
Thank you for the explanation regarding my DISCUSS question.
Alissa Cooper Former IESG member
(was Discuss) No Objection
No Objection (2019-02-22) Sent
Thanks for addressing my DISCUSS.
Alvaro Retana Former IESG member
No Objection
No Objection (for -05) Not sent

                            
Ben Campbell Former IESG member
No Objection
No Objection (2019-02-05 for -06) Sent
I'm surprised to find §5 in an IETF stream document. I wonder if this is too close to the case of including additional licensing information in a draft, which we generally try to avoid. (This is mostly to make sure it's on Alexey's radar; if he thinks it's okay to include this, I can live with it.)

Otherwise, I have just a few mostly editorial comments:

 §1.1: "This is just like instant messaging, which was
not intended to and did not replace E-mail."

"just like" seems overstated. I suggest "is analogous to", or something to that effect.

 §1.2: This document is being published by the IETF, isn't it? (that is, in the IETF stream?) If so, it seems a little odd to find the "About the OP3FT" text.

§2:
- "enabling end users to easily go from one layer to another, in both directions."
I'm not sure what that means. I suspect it means going from one reader/browser application to another. But I think a lot of people familiar with IETF protocols will think it means going from one network layer to another. (e.g. application to transport).

- "As regards Frogans as a medium, in the outgoing direction, FSDL
enables Frogans site publishers to include in their Frogans sites
way-out buttons enabling end users to launch their usual Web browser
on a given Web page, or to launch their usual E-mail client with a
given E-mail address."

That's hard to parse.
Deborah Brungard Former IESG member
No Objection
No Objection (for -06) Not sent

                            
Martin Vigoureux Former IESG member
No Objection
No Objection (for -06) Not sent

                            
Spencer Dawkins Former IESG member
No Objection
No Objection (for -05) Not sent

                            
Suresh Krishnan Former IESG member
No Objection
No Objection (for -06) Not sent

                            
Benjamin Kaduk Former IESG member
Abstain
Abstain (2019-02-07 for -06) Not sent
I haven't really seen a compelling argument to publish this in the IETF stream
Mirja Kühlewind Former IESG member
Abstain
Abstain (2019-02-06 for -06) Sent
I don't think publication of this document in the IETF series is appropriate (as registration policy is Expert Review only). I'm not apposed to the publication of this doc in there RFC series in general if a stable reference is appreciated by the Experts, however, I don't think IETF-wide and IESG reviews are needed for this doc.