RFC 6145 has been obsoleted by RFC 7915 #221

Open
toreanderson opened this Issue Aug 8, 2016 · 1 comment

Projects

None yet

2 participants

@toreanderson
Contributor

You're probably already aware of this, but in case you're not and considering that the compliance page says to let you know if there's anything missing, I'd just like to point out that RFC 6145 has been obsoleted by RFC 7915.

Looking at the changelog I think the most significant change is that you can now in good conscience purge the atomic fragment support from Jool. However, maybe it's best to do so in v3.5 in case anyone actually depends on it (for the record, I don't).

@ydahhrk ydahhrk added a commit that referenced this issue Aug 9, 2016
@ydahhrk ydahhrk More misc review and testing
Also fixes the atomic fragments part of #221.
b06e244
@ydahhrk ydahhrk added this to the 3.5.0 milestone Sep 14, 2016
@ydahhrk
Member
ydahhrk commented Sep 26, 2016

I'd like to leave this open to remind me that I should read the new RFC more thoroughly. (Though atomic fragments were indeed already purged.)

@ydahhrk ydahhrk modified the milestone: 3.5.1, 3.5.0 Sep 26, 2016
@ydahhrk ydahhrk modified the milestone: 3.5.2, 3.5.1 Oct 8, 2016
@ydahhrk ydahhrk removed this from the 3.5.2 milestone Dec 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment