[451] Follow-up HTTP Status Code 451

[Mark Nottingham]

Individual to start with, we can figure out a home later.

As an implementation report -- worth a try.


> On 20 Aug 2017, at 4:38 am, Niels ten Oever <niels at article19.org> wrote:
> 
> Hi Mark,
> 
> That sounds like a fruitful way to go. Where do you think we should bring up such a draft? Individual or otherwise?
> 
> We already have a draft implementation report: https://tools.ietf.org/html/draft-451-imp-report-00
> 
> Do you think it wuold make sense to (in a later version) publish it as official implementation report [0] ?
> 
> Best,
> 
> Niels
> 
> [0] https://www.ietf.org/iesg/implementation-report.html
> 
> 
> On Fri, Aug 18, 2017 at 02:07:07PM -0700, Mark Nottingham wrote:
>> I've given this feedback individually, but I don't think this needs to be a bis document -- AIUI we're trying to add to RFC7725, not update what's already there. You probably want to have a new draft that defines any new protocol elements, and a separate document (draft?) that is the implementation report.
>> 
>> Cheers,
>> 
>> 
>>> On 18 Aug 2017, at 2:36 am, Niels ten Oever <niels at article19.org> wrote:
>>> 
>>> 0. Update to RFC7725 (RFC7725bis)
>>> 	- Logan already made version a new for this (attached)
>>> 	- Might consist of integration of implementation report and human
>>> rights considerations
>> 
>> --
>> Mark Nottingham   https://www.mnot.net/
>> 
> 
> -- 
> 
> Niels ten Oever
> Head of Digital
> 
> Article 19
> www.article19.org
> 
> PGP fingerprint	   2458 0B70 5C4A FD8A 9488  
>                   643A 0ED8 3F3A 468A C8B3
> 

--
Mark Nottingham   https://www.mnot.net/