[rfc-i] SVG document - stray text
rjsparks at nostrum.com
Wed Jul 27 15:23:18 PDT 2016
We are to the point of approving for publication as an RFC and issuing
RFPs for implementation.
I missed that glitch in my reading of the diffs, focusing on what was
going to matter to the implementers. I'm glad you caught it.
IMHO, that's an easy RFC editor note or auth48 fix.
On 7/27/16 4:51 PM, Heather Flanagan (RFC Series Editor) wrote:
> Hi Lee,
> Not as such. We did last call/community comment several months ago. It's
> just taken a while to incorporate the comments. The question before the
> IAB now is whether we captured the comments sufficiently such that the
> IAB is willing to approve these for publication (noting that all the
> documents will be going through a -bis cycle after we finish coding and
> incorporating what we've learned from real-life implementation).
> On 7/27/16 2:42 PM, Howard, Lee L wrote:
>> I think right now it looks like nobody on the IAB read it. So I think it'd be embarrassing to send it for last call as is. That's where we are now, right?
>> Sent from my iPhone
>>> On Jul 27, 2016, at 4:37 PM, Heather Flanagan (RFC Series Editor) <rse at rfc-editor.org> wrote:
>>>> On 7/27/16 7:32 AM, Howard, Lee L wrote:
>>>> Before we send for further comment, the Abstract in draft-iab-rfc-02 has
>>>> stray text in the opening words:
>>>> . Maybe the text in section
>>>> I wouldn't want to announce without cleaning that up.
>>> Hi Lee,
>>> Is this something we can clean up during AUTH48, or do you want it fixed
>>> before the IAB does it's final approval for publication?
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
More information about the rfc-interest