On 10/21/11 10:01 AM, Ole Troan wrote:
Tassos,
I noticed [I-D.ymbk-aplusp] on the list, which recently became RFC 6346. Besides updating the list, do you find it appropriate to include RFCs with experimental status?
I think we should apply reasonable judgement.
with regards to A+P, that's an architecture document. I don't understand how an implementation could support that. there are a number of A+P-ish solutions being worked on in the softwire wg. 4rd, dIVI and ds-lite + A+P. plus a general stateless address mapping document and DHCP option. these are the A+P solutions, but way too early to include any of this work. I do not think 6346 belongs in RIPE-501.
hey, it's optional and covers everything you just said. Cool, is it? :)
Also 3484bis is still in draft.
3484bis fixes some real problems. hopefully it will be RFC before 501 is out.
early november?
If we include drafts, then 6204 should also be changed to 6204bis. Although i would prefer to have the final RFCs in.
I have suggested to just shelf 6204bis until we have something to put in it. 501 already has the references to 6rd and ds-lite that 6204bis adds. so not needed.
+1 /jan