Re: draft-ietf-httpbis-legally-restricted-status-02, example on 3. 451 Unavailable For Legal Reasons

On Thu, Oct 1, 2015 at 10:53 AM, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
wrote:

> > Yeah, good catch.  If someone wants to propose a URL for the entity
> > blocking the People’s Front of Judea, I’ll wire that in.
> >
>
> Link: <http://example.com/murus-incendii.html>; rel=blocked-by
>
> (from Laura Kataja)
>
> / Kari Hurtta
>
>
​I think you're aiming for "firewall" rendered in Latin.  You might try
"vallum" (rampart) or "fossa" (moat).  Or, given that the Romans had
censors, "magister morum".

​regards,

Ted​




> > On Tue, Sep 29, 2015 at 8:54 PM, Kari Hurtta <khurtta@welho.com> wrote:
> >
> >>
> >>
> >> An HTTP Status Code to Report Legal Obstacles
> >> draft-ietf-httpbis-legally-restricted-status-02
> >> August 31, 2015
> >>
> >>
> https://tools.ietf.org/html/draft-ietf-httpbis-legally-restricted-status-02
> >>
> >> On
> >>
> >> 3. 451 Unavailable For Legal Reasons
> >>
> >>
> https://tools.ietf.org/html/draft-ietf-httpbis-legally-restricted-status-02#section-3
> >>
> >> there is an example.
> >>
> >> Next chapter
> >>
> >> 4. Identifying Blocking Entities
> >>
> >>
> https://tools.ietf.org/html/draft-ietf-httpbis-legally-restricted-status-02#section-4
> >>
> >> introduces "Link" HTTP header field for that.
> >>
> >> Should previous example also include that "Link" header field or is it
> >> too early?
> >>
> >> Otherwise the example do not fulfill that "SHOULD" -requirement.
> >>
> >>
> >> / Kari Hurtta
> >> ( not member of the mailing list)
> >>
> >>
> >
> >
> > --
> > - Tim Bray (If you’d like to send me a private message, see
> > https://keybase.io/timbray)
>
>
>
>