IETF 96 - include Implementation section

[jjones425]

Recommendation to include Implementation section

[mrisher]

I think the comment was simply to include the "current implementation status" that we had from the slide. Sounds like it'll be a weird addition to the doc, though; does anyone have examples of how this has been done before?

[abrotman]

Do we know who asked for that? Could we get more context?

Sent from Yahoo Mail on Android

On Tue, Jul 26, 2016 at 6:24, Mark Rishernotifications@github.com wrote:
I think the comment was simply to include the "current implementation status" that we had from the slide. Sounds like it'll be a weird addition to the doc, though; does anyone have examples of how this has been done before?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jjones425]

I am going to research what others have done with respect to implementation sections. Stephen was one of the folks that mentioned, so, I will connect with him to get his feedback.

[jjones425]

Reaching out to Barry Leiba to get more feedback as the UTA notes mentioned he had feedback on this.

[jjones425]

Barry responded, referenced RFC 7942 (BCP 205).

[jjones425]

I read through RFC 7942 (BCP 205). Here are a few things to note. Please comment on recommendation and I will update the draft.

• Implementation sections are optional, but, encouraged.
• Implementation sections should only be used in the drafts, removed before RFC is published
• Since this information is necessarily time dependent, it is inappropriate for inclusion in a published RFC. The authors should include a note to the RFC Editor requesting that the section be removed before publication.
• We can host the implementation section outside of the draft if we want (ex. Via wiki) and only include a link within the draft as long as it does not require authentication for consumers to see.

Here is what I recommend – please comment @mrisher @abrotman @danmarg @prbinu

• Create an implementation section within the draft.
• Populate according to suggested content in RFC 7942 (BCP 205) and use the existing GitHub page wiki to host if we are able to allow consumers to see without requiring a login. This will allow us to be able to update as we have new information and share learnings as we pilot and put in production.