IETF Logo Mail Archive

Re: [precis] Review of current document draft-ietf-precis-framework-20

Patrik Fältström <paf@frobbit.se> Thu, 04 December 2014 08:00 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC261A8934 for <precis@ietfa.amsl.com>; Thu, 4 Dec 2014 00:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.961
X-Spam-Level:
X-Spam-Status: No, score=-1.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8px-9TJoEEbI for <precis@ietfa.amsl.com>; Thu, 4 Dec 2014 00:00:25 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA1AC1A8935 for <precis@ietf.org>; Thu, 4 Dec 2014 00:00:25 -0800 (PST)
Received: from vpn-client-208.netnod.se (vpn-client-208.netnod.se [192.71.80.208]) by mail.frobbit.se (Postfix) with ESMTPSA id F1CB023071; Thu, 4 Dec 2014 09:00:23 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Content-Type: multipart/signed; boundary="Apple-Mail=_F1C95371-A6BD-4DE2-8586-BD258F0EB251"; protocol="application/pgp-signature"; micalg="pgp-sha1"
X-Pgp-Agent: GPGMail 2.5b3
From: Patrik Fältström <paf@frobbit.se>
In-Reply-To: <547FCFA6.7000908@andyet.net>
Date: Thu, 04 Dec 2014 09:00:23 +0100
Message-Id: <F49F03E5-FB1E-4B81-B13F-F14E3DF350D5@frobbit.se>
References: <13AD33F4-1741-472E-8423-1B0302734325@frobbit.se> <547695F3.3030106@andyet.net> <47327B22-0591-43C9-A4E5-89F6222F7E82@frobbit.se> <547E7DD0.1090306@andyet.net> <636EC582-BA21-44B5-B202-DDB4E51FD138@frobbit.se> <547FCFA6.7000908@andyet.net>
To: Peter Saint-Andre - &yet <peter@andyet.net>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/precis/2YdaAFmw7itSHAm__UQJsoEth7U
Cc: precis@ietf.org
Subject: Re: [precis] Review of current document draft-ietf-precis-framework-20
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 08:00:27 -0000

> On 4 Dec 2014, at 04:06, Peter Saint-Andre - &yet <peter@andyet.net> wrote:
> 
> Is that kind of text specific enough for you?

Yes.

> I think we need to define this at the level of the application protocol because that's where the rubber meets the road and where we can legitimately talk about the various entities involved (at the level of the PRECIS framework we don't know what the entities are and what their responsibilities are).

I would say "ok" to the precis document if there is text added that say explicitly that that kind of text MUST be in an application specific document that reference the precis doc.

I.e. without text like that, it is very dangerous what is specified.

   Patrik

v2.46.0 | Report a Bug | By Email | System Status