Re: [apps-discuss] AppsDir review of draft-farrresnickel-ipr-sanctions

"Murray S. Kucherawy" <superuser@gmail.com> Tue, 05 June 2012 05:23 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C06121F8731; Mon, 4 Jun 2012 22:23:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dSMjSfh97S8F; Mon, 4 Jun 2012 22:23:43 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2310621F8726; Mon, 4 Jun 2012 22:23:42 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so3940698lbb.31 for <multiple recipients>; Mon, 04 Jun 2012 22:23:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pVr4SzkPJgPZuAkTVXxEfIv4+e4RGpDEwFbFVnIUcF0=; b=n8ZMfOJEdhq87Zj/C5OT+PpsqrrWelgjOc2v7vWccyJ+vZ19waaSxoSCP/G+PPQ9mO AdjpTpgQXT+awFXk0o+Bln+1P1Ov/M5mnFubbZbFcunicSLBSFvv20GLIZuWKTXMpocb AzAhpD94BRkZ+1dX0SkwDIGnRwzzaMsudhMOd+l2pmXj8s7TSxBiuZU99ZUxUKuhJyPx NCW6y3FEzgoJxNC7pyAk/cc45ah1UeHm9BWCdKjNfW/Gxixa+7lCw0JGT7LeyldQo020 5yUjxPsfYqn/GeiqESijLRRGp5FYoDVORmbAO/P3hTpd0+DNtOeyq7XmcahMnhjKkhit uBzg==
MIME-Version: 1.0
Received: by 10.112.49.100 with SMTP id t4mr7331511lbn.10.1338873821906; Mon, 04 Jun 2012 22:23:41 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Mon, 4 Jun 2012 22:23:41 -0700 (PDT)
In-Reply-To: <014901cd4294$e6ba1440$b42e3cc0$@olddog.co.uk>
References: <9452079D1A51524AA5749AD23E00392812C442@exch-mbx901.corp.cloudmark.com> <014901cd4294$e6ba1440$b42e3cc0$@olddog.co.uk>
Date: Mon, 04 Jun 2012 22:23:41 -0700
Message-ID: <CAL0qLwZnARZUeo7xU5xnTQRBMCbpJ_+ZgsJRck7jigHvOjfmwQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: adrian@olddog.co.uk
Content-Type: multipart/alternative; boundary="bcaec554d63c8dc77404c1b2da9a"
Cc: draft-farrresnickel-ipr-sanctions.all@tools.ietf.org, The IESG <iesg@ietf.org>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] AppsDir review of draft-farrresnickel-ipr-sanctions
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 05:23:44 -0000

On Mon, Jun 4, 2012 at 1:59 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> > 1. Should this not be a BCP?  The polk draft describes ways to encourage
> > compliance, while this one talks about penalties for non-compliance.
> That
> > seems too severe for Informational status, while the polk draft can
> > probably get away with it.
>
> My thinking was that this does not define any new process and doesn't even
> recommend their use. It just makes sure people remember the options exist.
>
> Barry seems to think "not a BCP" as well.
>
> Maybe we leave this to the IESG?
>

Sure.  PSA's suggestion is also reasonable to me.


>
> > Minor Issues:
> >
> > 1. Are all the URL references in here permanent?  I’m not sure about
> things
> > like [URLIESGIPR], for example, since it points to a wiki.
>
> I am not sure the URLs must be permanent. Sure we would like them to be
> "stable"
> but the RFC Editor seems to say that a URL is acceptable where no better
> reference can be found. Additionally, this is "only" an Informative
> reference.
>
> Can we leave this, and fix it if the RFC Editor complains?
>

Yep.  I was just trying to anticipate what the Editor might want.  Whatever
satisfies their requirements works for me.


>
> > Nits:
>
> Useful and accepted, except...
>
> > 3. Section 2.4: s/to be clearly understood/to be understood clearly/
>
> This is largely stylistic and a lot of stuff is said about split
> infinitives.
> Here I intended to stress clarity not understanding.
> I am sure the RFC Editor will apply house style.
>

Same here.

Cheers,
-MSK