Re: [Acme] Question about the "expired" status

[Daniel McCarney]

Merged & resolved.

Thanks again,

On Wed, Mar 21, 2018 at 2:26 PM, Daniel McCarney 
wrote:

> Hi again Ning,
>
> I opened https://github.com/ietf-wg-acme/acme/pull/416 just now to
> resolve these. Since this is strictly editorial it should be possible to
> merge by EOD.
>
> In the future it would save some time if you were able to provide PRs to
> address these small changes yourself :-)
>
> Thanks!
>
> - Daniel / cpu
>
> On Wed, Mar 21, 2018 at 1:12 PM, Zhang, Ning 
> wrote:
>
>> Should section 7.1.4 list "expired" as a possible status value? Section
>> 7.1.6 specifies that an Authorization object may end up in the "expired"
>> status.
>>
>>
>>
>> By the way, the example in Section 7.1.2.1 has a typo:
>>
>>
>>
>>Link: , rel="next"
>>
>> =>
>>
>>Link: ;rel="next"
>>
>>
>>
>> Thanks,
>>
>> -Ning
>>
>> ___
>> Acme mailing list
>> Acme@ietf.org
>> https://www.ietf.org/mailman/listinfo/acme
>>
>>
>
___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

Re: [Acme] Question about the "expired" status

[Daniel McCarney]

Hi again Ning,

I opened https://github.com/ietf-wg-acme/acme/pull/416 just now to resolve
these. Since this is strictly editorial it should be possible to merge by
EOD.

In the future it would save some time if you were able to provide PRs to
address these small changes yourself :-)

Thanks!

- Daniel / cpu

On Wed, Mar 21, 2018 at 1:12 PM, Zhang, Ning 
wrote:

> Should section 7.1.4 list "expired" as a possible status value? Section
> 7.1.6 specifies that an Authorization object may end up in the "expired"
> status.
>
>
>
> By the way, the example in Section 7.1.2.1 has a typo:
>
>
>
>Link: , rel="next"
>
> =>
>
>Link: ;rel="next"
>
>
>
> Thanks,
>
> -Ning
>
> ___
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>
>
___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme