Re: [spring] SPRING WG Implementation Information Policy

2022-10-14 Thread Joel Halpern
al Message- From: Joel Halpern Sent: 14 October 2022 13:56 To: adr...@olddog.co.uk; 'SPRING WG List' Subject: Re: [spring] SPRING WG Implementation Information Policy We removed all references to retaining the material in the published RFC. And emphasized that we are following

Re: [spring] SPRING WG Implementation Information Policy

2022-10-14 Thread Adrian Farrel
carried in RFCs. I think you could safely change both occurrences to "the draft" and I would then shut up and go and do some real work. Cheers, Adrian -Original Message- From: Joel Halpern Sent: 14 October 2022 13:56 To: adr...@olddog.co.uk; 'SPRING WG List' S

Re: [spring] SPRING WG Implementation Information Policy

2022-10-14 Thread Joel Halpern
We removed all references to retaining the material in the published RFC.  And emphasized that we are following RFC 7942, being explicit about where we are varying from it.  This is to align with the rough consensus of the WG not to retain the material in RFCs. If we put in text about not reta

Re: [spring] SPRING WG Implementation Information Policy

2022-10-14 Thread Adrian Farrel
Hi Joel, chairs. Thanks for working on this. Can I ask, just for clarification, what the conclusion is on whether this section is going to remain in the document when it becomes an RFC. I find the text a little confusing because it talks about "an I-D [that] is ready for WG last call", but lat