
From daedulus@btconnect.com  Fri Jun  1 01:10:05 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D17521F8480 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 01:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_66=0.6, RCVD_IN_DNSWL_MED=-4]
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 BLkIW9pzWCVy for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 01:10:04 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id 7739021F84A2 for <ietf@ietf.org>; Fri,  1 Jun 2012 01:10:04 -0700 (PDT)
Received: from mail140-tx2-R.bigfish.com (10.9.14.247) by TX2EHSOBE007.bigfish.com (10.9.40.27) with Microsoft SMTP Server id 14.1.225.23; Fri, 1 Jun 2012 08:09:33 +0000
Received: from mail140-tx2 (localhost [127.0.0.1])	by mail140-tx2-R.bigfish.com (Postfix) with ESMTP id 003D81201CC; Fri,  1 Jun 2012 08:09:33 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT008.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(z3b49sz9371I542M98dKzz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah304l)
Received: from mail140-tx2 (localhost.localdomain [127.0.0.1]) by mail140-tx2 (MessageSwitch) id 1338538171567572_28971; Fri,  1 Jun 2012 08:09:31 +0000 (UTC)
Received: from TX2EHSMHS005.bigfish.com (unknown [10.9.14.250])	by mail140-tx2.bigfish.com (Postfix) with ESMTP id 87441E0047; Fri,  1 Jun 2012 08:09:31 +0000 (UTC)
Received: from DB3PRD0702HT008.eurprd07.prod.outlook.com (157.55.224.141) by TX2EHSMHS005.bigfish.com (10.9.99.105) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 1 Jun 2012 08:10:25 +0000
Received: from BY2PRD0610HT002.namprd06.prod.outlook.com (157.56.236.117) by pod51017.outlook.com (10.3.4.173) with Microsoft SMTP Server (TLS) id 14.15.74.2; Fri, 1 Jun 2012 08:09:45 +0000
Message-ID: <003f01cd3fcd$7d3b5b60$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com><4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com><alpine.OSX.2.01.1205310108380.82586@sjc-vpn7-992.cisco.com> <47983FE3-D3C5-4AC6-BAC3-F8DC96CAF854@niven-jenkins.co.uk>
Subject: Re: Colloquial language [Re: Last Call:<draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice'sGuide to the Internet Engineering Task Force) to Informational RFC]
Date: Fri, 1 Jun 2012 09:06:36 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.236.117]
X-OriginatorOrg: btconnect.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 08:10:05 -0000

---- Original Message -----
From: "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk>
To: "Ole Jacobsen" <ole@cisco.com>
Cc: <ietf@ietf.org>
Sent: Thursday, May 31, 2012 11:36 PM
On 31 May 2012, at 09:16, Ole Jacobsen wrote:
> Sounds like a difficult thing to do with any kind of predictable or
> measurable outcome, although it might be fun to ask the Brits if they
> understand everything the Americans are saying and vice versa :-)

I don't really have any issues understanding American English but I'm
regularly gobsmacked by how many North Americans struggle to understand
some things that I say :-)

<tp>
It's called irony; it got left behind on the beach, when the Pilgrim
Fathers crossed the pond.

On the other hand, it could just be that what you say <>is<> cricket.
Which would also be perfectly comprehensible to the Indian audience,
alluded to earlier (and to the remainder of the English speaking
world:-)

Tom Petch
</tp>

Ben




From randy@psg.com  Fri Jun  1 01:13:29 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4412021F861E for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 01:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.204
X-Spam-Level: 
X-Spam-Status: No, score=-2.204 tagged_above=-999 required=5 tests=[AWL=-0.205, BAYES_00=-2.599, J_CHICKENPOX_66=0.6]
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 pB6z-GLTqBlE for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 01:13:28 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6A621F854B for <ietf@ietf.org>; Fri,  1 Jun 2012 01:13:28 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SaMz6-000Kfy-EM; Fri, 01 Jun 2012 08:13:24 +0000
Date: Fri, 01 Jun 2012 17:13:23 +0900
Message-ID: <m2zk8nphzw.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: t.p. <daedulus@btconnect.com>
Subject: Re: Colloquial language [Re: Last	Call:<draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice'sGuide to the Internet Engineering Task Force) to	Informational RFC]
In-Reply-To: <003f01cd3fcd$7d3b5b60$4001a8c0@gateway.2wire.net>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com> <alpine.OSX.2.01.1205310108380.82586@sjc-vpn7-992.cisco.com> <47983FE3-D3C5-4AC6-BAC3-F8DC96CAF854@niven-jenkins.co.uk> <003f01cd3fcd$7d3b5b60$4001a8c0@gateway.2wire.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 08:13:29 -0000

if i have to delete through much more about this bikeshed, i will give
you some colloquial american to read.

randy

From ynir@checkpoint.com  Fri Jun  1 01:16:20 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 141EB21F863D for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 01:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.266
X-Spam-Level: 
X-Spam-Status: No, score=-10.266 tagged_above=-999 required=5 tests=[AWL=-0.267, BAYES_00=-2.599, J_CHICKENPOX_66=0.6, RCVD_IN_DNSWL_HI=-8]
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 aNNJGv1Fvwoe for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 01:16:19 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id E31EA21F863E for <ietf@ietf.org>; Fri,  1 Jun 2012 01:16:18 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (dlpgw.checkpoint.com [194.29.34.27]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q518GB6u011844; Fri, 1 Jun 2012 11:16:11 +0300
X-CheckPoint: {4FC88684-2-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Fri, 1 Jun 2012 11:16:09 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Randy Bush <randy@psg.com>
Date: Fri, 1 Jun 2012 11:16:08 +0300
Subject: Re: Colloquial language [Re:	Last Call:<draft-hoffman-tao4677bis-15.txt> (The Tao of IETF:	A	Novice'sGuide to the Internet Engineering Task Force)	to	Informational RFC]
Thread-Topic: Colloquial language [Re:	Last Call:<draft-hoffman-tao4677bis-15.txt> (The Tao of IETF:	A	Novice'sGuide to the Internet Engineering Task Force)	to	Informational RFC]
Thread-Index: Ac0/zsxZKjTDkaBxQlWyaKXRJS85PQ==
Message-ID: <814D1F9A-66E5-4F57-A4F4-BCA5E636787E@checkpoint.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com> <alpine.OSX.2.01.1205310108380.82586@sjc-vpn7-992.cisco.com> <47983FE3-D3C5-4AC6-BAC3-F8DC96CAF854@niven-jenkins.co.uk> <003f01cd3fcd$7d3b5b60$4001a8c0@gateway.2wire.net> <m2zk8nphzw.wl%randy@psg.com>
In-Reply-To: <m2zk8nphzw.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11a1842c656b4862e454557ab1ae340b3c5a10752d
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 08:16:20 -0000

On Jun 1, 2012, at 11:13 AM, Randy Bush wrote:

> if i have to delete through much more about this bikeshed, i will give
> you some colloquial american to read.


"bikeshed" ?

:-)

Yoav

From mrex@sap.com  Fri Jun  1 03:46:21 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80A9D21F85D2 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 03:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.178
X-Spam-Level: 
X-Spam-Status: No, score=-10.178 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 WZTQ6eQBeIf2 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 03:46:21 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id D5E3921F85C9 for <ietf@ietf.org>; Fri,  1 Jun 2012 03:46:20 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q51AkIJv006285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 1 Jun 2012 12:46:18 +0200 (MEST)
Subject: Re: Colloquial language
In-Reply-To: <4FC78FC2.9030800@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
Date: Fri, 1 Jun 2012 12:46:18 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20120601104618.7BD181A094@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 10:46:21 -0000

Peter Saint-Andre wrote:
> 
> So the way we introduce some people to the IETF is to expect that they
> will look up fifty unfamiliar words and phrases? Having taught English
> as a second language, I can attest that some of the idioms and
> colloquialisms included in this document would have caused puzzlement in
> my students.

How about an appendix for draft-hoffman-tao4677bis describing the
terms you find exceedingly colloquial? (to support offline consumption
of the document)?

-Martin

From tnadeau@lucidvision.com  Fri Jun  1 04:41:13 2012
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B783521F85E5 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 04:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
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 rNiJmrKUUqqx for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 04:41:13 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 20A7821F85E4 for <ietf@ietf.org>; Fri,  1 Jun 2012 04:41:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by lucidvision.com (Postfix) with ESMTP id 9153621487B5; Fri,  1 Jun 2012 07:41:12 -0400 (EDT)
X-Virus-Scanned: amavisd-new at www.lucidvision.com
Received: from lucidvision.com ([127.0.0.1]) by localhost (static-72-71-250-34.cncdnh.fios.verizon.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mEsx5syczD0C; Fri,  1 Jun 2012 07:41:12 -0400 (EDT)
Received: from sa-nc-ipg-172-23-0-29.static.jnpr.net (natint3.juniper.net [66.129.224.36]) by lucidvision.com (Postfix) with ESMTP id 9893921487B2; Fri,  1 Jun 2012 07:41:11 -0400 (EDT)
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <47983FE3-D3C5-4AC6-BAC3-F8DC96CAF854@niven-jenkins.co.uk>
Date: Fri, 1 Jun 2012 07:41:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6DCC8518-8477-496E-BEB2-641D0BE3542C@lucidvision.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com> <alpine.OSX.2.01.1205310108380.82586@sjc-vpn7-992.cisco.com> <47983FE3-D3C5-4AC6-BAC3-F8DC96CAF854@niven-jenkins.co.uk>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
X-Mailer: Apple Mail (2.1278)
Cc: Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 11:41:13 -0000

On May 31, 2012:6:36 PM, at 6:36 PM, Ben Niven-Jenkins wrote:

>=20
> On 31 May 2012, at 09:16, Ole Jacobsen wrote:
>> Sounds like a difficult thing to do with any kind of predictable or=20=

>> measurable outcome, although it might be fun to ask the Brits if they
>> understand everything the Americans are saying and vice versa :-)
>=20
> I don't really have any issues understanding American English but I'm =
regularly gobsmacked by how many North Americans struggle to understand =
some things that I say :-)

	I can personally attest to that. *)

	--Tom


From nick@inex.ie  Fri Jun  1 05:03:59 2012
Return-Path: <nick@inex.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A57A021F8752 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 05:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 nUG7ijm-0f13 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 05:03:58 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 983CF21F8705 for <ietf@ietf.org>; Fri,  1 Jun 2012 05:03:57 -0700 (PDT)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.local ([IPv6:2001:1bb8:2004:100:f0f2:ab4f:abfc:e662]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q51C3hL0006025 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 1 Jun 2012 13:03:43 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4FC8AFA9.1020200@inex.ie>
Date: Fri, 01 Jun 2012 13:03:53 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Making the Tao a web page
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org>
In-Reply-To: <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org>
X-Enigmail-Version: 1.4.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 12:03:59 -0000

On 01/06/2012 00:50, Paul Hoffman wrote:
> Thank you for that most colorful analogy. :-) What I proposed is exactly
> what we are doing now, except that the changes would appear on the web
> page instead of an Internet-Draft and, five years later, an RFC. Are you
> saying that the current system (which you have not commented on until
> now) is sclerotic (a word that I have wanted to use since I learned it
> in high school)?

It depends on what you're trying to do.  For prescriptive documents which
aren't expected to change much, the I-D system works well.  But as it's
been suggested that this document falls into a category which is expected
to change from time to time, wikis offer a lot more flexibility.  Wikipedia
editing and document management policy suggests that you can end up with
quality material.  It's a bit of a departure from the I-D system, but its
lack of formality is quite appealing for documents which are not formally
prescriptive.

Nick

From mellon@fugue.com  Thu May 31 13:43:17 2012
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F392D21F85AF for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 13:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 LryQ2WxEPMVl for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 13:43:15 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 2A8A521F85AD for <ietf@ietf.org>; Thu, 31 May 2012 13:43:15 -0700 (PDT)
Received: from [64.89.226.6] (unknown [64.89.226.6]) by toccata.fugue.com (Postfix) with ESMTPSA id 0E263238152B; Thu, 31 May 2012 16:43:12 -0400 (EDT)
Subject: Re: Last Call: <draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt> (Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI)) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <20120531184851.30358.8816.idtracker@ietfa.amsl.com>
Date: Thu, 31 May 2012 13:43:11 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <ADE21D06-F6A4-4018-A999-6B50EC94F3C7@fugue.com>
References: <20120531184851.30358.8816.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Fri, 01 Jun 2012 08:15:25 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 20:43:17 -0000

There are still a few problems with this draft.   The first is that it =
uses a nonstandard and somewhat odd encoding to deliver the URI and =
Lifetime values.   These should simply be delivered as separate options, =
leaving out the whole Luritype complication.    The argument might be =
raised that the Luritype field provides some sort of future-proofing, =
but this future-proofing can as easily be attained with another DHCP =
option code, so it's unnecessary.

Secondly, this text ought to be expanded:

>  The choice of the Valid-For value is a policy decision for the=20
>  operator of the DHCP server.  Like location URIs themselves, it can=20=

>  be statically configured on the DHCP server or provisioned=20
>  dynamically (via an out-of-band exchange with a Location Information
>  Server) as requests for location URIs are received.

To:

> The choice of the Valid-For value is a policy decision for the=20
>  operator of the DHCP server.  Like location URIs themselves, it can=20=

>  be statically configured on the DHCP server or provisioned=20
>  dynamically (via an out-of-band exchange with a Location Information
>  Server) as requests for location URIs are received.   DHCP server
>  operators are advised not to configure a valid-for lifetime that is
>  greater than half the minimum configured lifetime for DHCP leases,
>  since this could result in stale configuration information on the
>  DHCP client and potential loss of service.


Thirdly, this text is simply wrong, and indeed specifically contradicted =
by RFC3396:

>    Per [RFC2131], subsequent LocationURI Options, which are=20
>    non-concatenated, overwrite the previous value.

I don't think this is a huge problem, but I think the text should say =
this:

> It is not meaningful to configure multiple LocationURI options.   =
DHCPv4 servers and clients conforming to RFC3396 will not permit this; =
DHCPv6 servers and clients can be configured this way, but the behavior =
when so configured is undefined.   Therefore, DHCPv6 server operators =
are cautioned not to configure more than one such option.

Section 3.2 suggests that options shouldn't contain certain potentially =
harmful values, but this is a toothless restriction, since an attacker =
can simply ignore it.   In order for it to be effective, Section 3.2 =
should insist that DHCP clients reject forbidden URI formats.   Of =
course, this too is somewhat toothless, since any list of forbidden URI =
formats will necessarily fail to mention any future potentially harmful =
URIs that could arise.   It would be better to list which URIs _are_ =
permitted, and require the client to reject any URI that is not =
permitted.   The document is already set up to do this, but doesn't =
_actually_ do it, so fixing this should be quite easy.

Sorry for not catching all of this sooner=97the previous review of the =
document was rudely interrupted by the Paris IETF meeting... :)

Aside from these objections, which I think are easy to address, I have =
no problem with the document proceeding.=

From drc@virtualized.org  Fri Jun  1 08:41:35 2012
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B752421F8A53 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 08:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 kc6kBLnQosbZ for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 08:41:35 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id F109621F8A52 for <ietf@ietf.org>; Fri,  1 Jun 2012 08:41:34 -0700 (PDT)
Received: from [192.168.2.168] (unknown [173.245.57.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id A9C831705A; Fri,  1 Jun 2012 15:41:33 +0000 (UTC)
Subject: Re: IANA [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of	IETF: A Novice's Guide to the Internet Engineering Task Force)	to	Informational RFC]
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: David Conrad <drc@virtualized.org>
In-Reply-To: <E583EE89-5772-4E85-AFDF-49E2C3ADEAC2@cisco.com>
Date: Fri, 1 Jun 2012 08:12:39 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <355F9FFB-74B0-48A4-98BB-E0FBEB142195@virtualized.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20120530214914.094ac8d0@resistor.net> <4FC79FF0.9010001@gmail.com> <4FC82EA2.4000406@connotech.com> <E583EE89-5772-4E85-AFDF-49E2C3ADEAC2@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1278)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 15:41:35 -0000

On May 31, 2012, at 9:38 PM, Fred Baker wrote:
>>> The IAB decides who acts as the IETF's IANA. RFC 2860 again.
>> http://ntia.doc.gov/page/iana-functions-purchase-order
> You're correct that NTIA wants to pay someone to do the "protocol =
parameter" job.

Err, "pay" isn't the right word here: it's a zero dollar contract =
(although this doesn't preclude the contract assignee from charging to =
recover costs (as long as NTIA agrees)).

> The IAB can decide to not use that office.

Yep. Of course, what happens after that is left to the reader as an =
exercise.  Fortunately, I believe (hope?) everybody wants the same thing =
wrt administrative oversight of "the IANA" so that exercise won't need =
to be handed in to the teacher.

Regards,
-drc


From d3e3e3@gmail.com  Fri Jun  1 08:46:21 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6ADE21F8B38; Fri,  1 Jun 2012 08:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.233
X-Spam-Level: 
X-Spam-Status: No, score=-102.233 tagged_above=-999 required=5 tests=[AWL=-0.934, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 NgXkeR9PrKWL; Fri,  1 Jun 2012 08:46:20 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5A88421F8B3A; Fri,  1 Jun 2012 08:46:20 -0700 (PDT)
Received: by yhq56 with SMTP id 56so1978691yhq.31 for <multiple recipients>; Fri, 01 Jun 2012 08:46:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=3SrWxgz4JzCQG0DAWAHWabO2CemWwugsLuYlXUsDRcE=; b=bumQNY8oJv5Pe7UPZozUcSlW5O1zXvDkoegjh9XQxlDCWr0jk6sqBeG26vYykNr981 Mf2TpVrG3gP+tL4vHgj8ak8r5eg07dOWt6i4pI5P6wDurlPnujr8aLF9VspKvN+jPIoK RLL2J0Fst0kERy2E7V+gQrImS4kfVdYVfzskp16cyU2nVPZyHBHF8A5AVNF+FhmbSTUH 9t4nVsAvy/bN4Vjn/UyX4Y8yADuhrvu2cuPZg4IO88klN/KDdBE0wDvHTyZ/i37YFy+E HzzuTQJeLceMcO5+tliN7DZxR4DlCSNefmhZqtEgBbKavbTXewXdoBverluzufP2fopj n5Xg==
Received: by 10.50.212.98 with SMTP id nj2mr2038781igc.35.1338565578568; Fri, 01 Jun 2012 08:46:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.99.228 with HTTP; Fri, 1 Jun 2012 08:45:57 -0700 (PDT)
In-Reply-To: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com>
References: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 1 Jun 2012 11:45:57 -0400
Message-ID: <CAF4+nEESCSkUgM2Wzr5MXfW5su5Og_XA0dyO+gksfN2LAzCCWw@mail.gmail.com>
Subject: Re: Gen-ART LC/Telechat review of draft-ietf-trill-rbridge-extension-04
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-ietf-trill-rbridge-extension.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 15:46:21 -0000

Hi Ben,

Thanks for your review. See responses below.

On Thu, May 31, 2012 at 6:08 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document: draft-ietf-trill-rbridge-extension-04
> Reviewer: Ben Campbell
> Review Date: 2012-05-31
> IETF LC End Date: 2012-06-07
> IESG Telechat date: 2012-06-07
>
> Note: Since this draft is on the agenda of the IESG Telechat on the
> same day that the IETF last call expires, this review is intended
> for both purposes.
>
> Summary:
>
> This draft is almost ready for publication as a proposed standard,
> but I have some clarification questions and comments that should be
> considered prior to publication.
>
> Major issues:
>
> None
>
> Minor issues:
>
> -- section 2, general:
>
> Do the authors assume that all TRILL extensions will follow this
> spec? Since RFC6325 already specifies an extension mechanism, what
> stops an extension from ignoring this spec and doing something
> different? Does it hurt if they do?

I am not aware of any conflicts between this draft and RFC 6325. RFC
6325 provides the broadest header option framework, for example
specifying the field for the length of the options area and the
initial two critical summary bits. This document fills in the
structure and allocation mechanism of the remaining bits in the first
4-byte word of the options area, consistent with and repeating some
material from RFC 6325, but leaving specification of the remainder of
the options area for future documents, which should be consistent with
both RFC 6325 and this document. (For example, some future version of
draft-ietf-trill-rbridge-options.)

However, neither RFC 6325 nor this document can actually actually bind
the IETF against adopting future standards describing extensions that
do not conform. If future changes do not follow RFC 6325 or this
document, for example changing the location or interpretation of the
option length field in the TRILL Header or changing the interpretation
of the critical summary bits in the first word of the options area,
then this would break hardware and software implementations that
depend on RFC 6325 and/or this document. But I trust the IETF to
adhere to its usually high standards for backwards compatibility.

Perhaps this draft should, in the first page header, say "Updates:
6325", not in the sense that it makes a change but in the sense that
it fills in more details.

> -- section 2, 3rd paragraph from end: "Non-critical extensions can
>    be safely ignored."
>
> Is that intended to be normative? (Seems like it should be, since
> behavior for critical extensions is normative).

I think of it as more like the definition of "non-critical".

> -- section 2.1, 1st paragraph, last sentence:
>
> Redundant with normative language in previous section.

? There is a normative requirement to discard frames with any
unimplemented critical hop-by-hop options present, which might be
thought to require examination of all options (something manifestly
impossible since the format of options beyond the first word of the
options area is not yet normatively specified). The sentence to which
you refer just clarifies that testing the appropriate crtical summary
bit(s) in the first word of the options area, if that word is present,
is all that is required.

> -- section 2.3, first paragraph:
>
> Is the first sentence intended as normative?

Yes. When one is describing part of a protocol and you say that some
particular contiguous block of bits is some particular field (and then
possibly describe the sub-structure of that field) isn't that always
normative?

> -- section 6, last paragraph:
>
> No security implications of this are mentioned. Is it really a
> security consideration?
>
> Also, is this more likely to be set incorrectly than all the other
> things that some implementation might screw up, so that it warrants
> special treatment?

I tend to think that a discussion of what happens if bits are
corrupted or incorrectly set is something reasonable for the Security
Considerations section, although it could be elsewhere. The second
paragraph/sentence of this section says that security considerations
for any bits in the first word of the options area will be in the
document specifying those bits. This document specifies the critical
summary bits and the RBridge Channel Alert bits so there is text on
both of those in its Security Considerations Section.

> Nits/editorial comments:
>
> -- section 1:
>
> Please expand TRILL on first mention in the body of the document
> (i.e. not just in the Abstract.)

Sure. And all the other acronym expansions requested below are fine so
I won't respond individually to them below although I agree with them.

> -- section 2:
>
> Please expand RBridge and IS-IS on first mention.
>
> -- section 2, bullet list, 2nd bullet: " ... which would only
>    necessarily affect the RBridge(s) where a TRILL frame is
>    decapsulated"
>
> Does that mean it always affects the decapsulating RBridge but might
> effect transit RBridges as well?

Yes.

> -- section 2, first paragraph after bullet list: "critical
>    hop-by-hop extension"
>
> I assume this means an extension with the critical flag set? If so,
> it would be more precise to say that.

This draft was split out of a more general draft that covered
extensions in general. The three paragraphs after the bullet list on
critical / non-critical extensions apply to all extensions as well as
the flag bits in the first word of the options area. So this means
critical header extensions flags and any other types of critical
options specified in the future.

> -- section 2.1, 1st paragraph:
>
> I'm a little confused by a citation for "future documents". Do you
> mean the cited document as an example of something that might do
> this (in which case a "for example" would help), or do you mean to
> say that document will do this?

Yes, the cited work-in-progress references are examples. I'm fine with
adding "for example".

> -- section 2.2, 1st paragraph:
>
> Please expand PDU on first mention.
>
> -- section 2.3, first paragraph:
>
> s/modifictions/modifications

OK. Thanks.

> -- section 5:
>
> Since section 3 is entirely composed of the referenced table, and
> seems to exist mostly if not entirely for the purpose of this
> reference, why not just move the table to the IANA considerations
> section.

(Looking at Section 3, I believe the reference there to the IANA
Considerations Section should be to Section 5 rather than Section 6.)

I guess I don't actually see any problem with the current document
structure that I think flows better for someone reading it from the
start. I suppose it imposes a tiny burden on someone who is just
looking at the IANA Considerations Section. I don't see why it would
be better to make it a tiny bit easier for someone just looking at the
IANA Considerations Section while imposing a tiny burdne on those
reading through the document from the start.

Hope the above responses help with the clarification,
Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

From ben@nostrum.com  Fri Jun  1 12:18:10 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3788E11E80AD; Fri,  1 Jun 2012 12:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.08
X-Spam-Level: 
X-Spam-Status: No, score=-101.08 tagged_above=-999 required=5 tests=[AWL=-0.780, BAYES_00=-2.599, MANGLED_LIST=2.3, SPF_PASS=-0.001,  USER_IN_WHITELIST=-100]
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 td9g-XnJUZz3; Fri,  1 Jun 2012 12:18:09 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 313EB11E80A4; Fri,  1 Jun 2012 12:18:08 -0700 (PDT)
Received: from frankenstein.test.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q51JI3ZX082589 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 1 Jun 2012 14:18:05 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Re: Gen-ART LC/Telechat review of draft-ietf-trill-rbridge-extension-04
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <CAF4+nEESCSkUgM2Wzr5MXfW5su5Og_XA0dyO+gksfN2LAzCCWw@mail.gmail.com>
Date: Fri, 1 Jun 2012 14:18:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <69241DCD-C349-4D15-8B92-58D05F216BF5@nostrum.com>
References: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com> <CAF4+nEESCSkUgM2Wzr5MXfW5su5Og_XA0dyO+gksfN2LAzCCWw@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1278)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: draft-ietf-trill-rbridge-extension.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 19:18:10 -0000

Thanks for the quick response. Further comments inline. I deleted =
sections that do not appear to need further discussion.

Thanks!

Ben.

On Jun 1, 2012, at 10:45 AM, Donald Eastlake wrote:

> Hi Ben,
>=20
> Thanks for your review. See responses below.
>=20
> On Thu, May 31, 2012 at 6:08 PM, Ben Campbell <ben@nostrum.com> wrote:
>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please wait for direction from your document shepherd
>> or AD before posting a new version of the draft.
>>=20
>> Document: draft-ietf-trill-rbridge-extension-04
>> Reviewer: Ben Campbell
>> Review Date: 2012-05-31
>> IETF LC End Date: 2012-06-07
>> IESG Telechat date: 2012-06-07
>>=20
>> Note: Since this draft is on the agenda of the IESG Telechat on the
>> same day that the IETF last call expires, this review is intended
>> for both purposes.
>>=20
>> Summary:
>>=20
>> This draft is almost ready for publication as a proposed standard,
>> but I have some clarification questions and comments that should be
>> considered prior to publication.
>>=20
>> Major issues:
>>=20
>> None
>>=20
>> Minor issues:
>>=20
>> -- section 2, general:
>>=20
>> Do the authors assume that all TRILL extensions will follow this
>> spec? Since RFC6325 already specifies an extension mechanism, what
>> stops an extension from ignoring this spec and doing something
>> different? Does it hurt if they do?
>=20
> I am not aware of any conflicts between this draft and RFC 6325. RFC
> 6325 provides the broadest header option framework, for example
> specifying the field for the length of the options area and the
> initial two critical summary bits. This document fills in the
> structure and allocation mechanism of the remaining bits in the first
> 4-byte word of the options area, consistent with and repeating some
> material from RFC 6325, but leaving specification of the remainder of
> the options area for future documents, which should be consistent with
> both RFC 6325 and this document. (For example, some future version of
> draft-ietf-trill-rbridge-options.)

I agree there is no conflict--this draft adds details, but doesn't seem =
to contradict anything in the RFC.

>=20
> However, neither RFC 6325 nor this document can actually actually bind
> the IETF against adopting future standards describing extensions that
> do not conform.

Certainly. Nothing can do that. The IETF can always update a protocol to =
change normative language, no matter how strongly it was stated =
originally :-)

> If future changes do not follow RFC 6325 or this
> document, for example changing the location or interpretation of the
> option length field in the TRILL Header or changing the interpretation
> of the critical summary bits in the first word of the options area,
> then this would break hardware and software implementations that
> depend on RFC 6325 and/or this document. But I trust the IETF to
> adhere to its usually high standards for backwards compatibility.
>=20
> Perhaps this draft should, in the first page header, say "Updates:
> 6325", not in the sense that it makes a change but in the sense that
> it fills in more details.
>=20

Assuming the additional details in this draft comprise preferred =
extension mechanism, then I think it makes sense to say that somewhere =
(perhaps a SHOULD strength), and also mark it as updating 6325. Adding =
details is still an update.


>> -- section 2, 3rd paragraph from end: "Non-critical extensions can
>>   be safely ignored."
>>=20
>> Is that intended to be normative? (Seems like it should be, since
>> behavior for critical extensions is normative).
>=20
> I think of it as more like the definition of "non-critical".

Sure--I mainly mention it to be consistent with the text for "critical" =
extensions, since it did use normative language about dropping frames.

>=20
>> -- section 2.1, 1st paragraph, last sentence:
>>=20
>> Redundant with normative language in previous section.
>=20
> ? There is a normative requirement to discard frames with any
> unimplemented critical hop-by-hop options present, which might be
> thought to require examination of all options (something manifestly
> impossible since the format of options beyond the first word of the
> options area is not yet normatively specified). The sentence to which
> you refer just clarifies that testing the appropriate crtical summary
> bit(s) in the first word of the options area, if that word is present,
> is all that is required.

section 2 says "Any RBridge receiving a frame with a critical hop-by-hop =
extension  that it does not implement MUST discard the frame...". =
Section 2.1 says "If an RBridge does not implement all critical flags in =
a TRILL Data frame, it MUST discard the frame..." These really seem like =
the same MUST (i.e, if you updated one but not the other, you would have =
an ambiguous state). The same is true for the egress bit.

I understand that you want to draw the connection between a "critical =
extension" and "critical flags", but it's better to avoid having =
multiple bits of authoritative text for the same normative requirement. =
Perhaps it might be better to say something like "If the RBridge does =
not implement all critical flags... it MUST treat the frame as having an =
unimplemented critical extension as described in section 2"



>=20
>> -- section 2.3, first paragraph:
>>=20
>> Is the first sentence intended as normative?
>=20
> Yes. When one is describing part of a protocol and you say that some
> particular contiguous block of bits is some particular field (and then
> possibly describe the sub-structure of that field) isn't that always
> normative?

Never mind, I misread the sentence. Sorry for the confusion.

>=20
>> -- section 6, last paragraph:
>>=20
>> No security implications of this are mentioned. Is it really a
>> security consideration?
>>=20
>> Also, is this more likely to be set incorrectly than all the other
>> things that some implementation might screw up, so that it warrants
>> special treatment?
>=20
> I tend to think that a discussion of what happens if bits are
> corrupted or incorrectly set is something reasonable for the Security
> Considerations section, although it could be elsewhere. The second
> paragraph/sentence of this section says that security considerations
> for any bits in the first word of the options area will be in the
> document specifying those bits. This document specifies the critical
> summary bits and the RBridge Channel Alert bits so there is text on
> both of those in its Security Considerations Section.

On re-reading the paragraph, I can see interpreting it to mean that =
incorrectly set flags explicitly do not cause a security problem, which =
I agree is reasonable to say in the security considerations. So, never =
mind :-)

[...]


>>=20
>> -- section 2, bullet list, 2nd bullet: " ... which would only
>>   necessarily affect the RBridge(s) where a TRILL frame is
>>   decapsulated"
>>=20
>> Does that mean it always affects the decapsulating RBridge but might
>> effect transit RBridges as well?
>=20
> Yes.
>=20

Okay, no problem.

>> -- section 2, first paragraph after bullet list: "critical
>>   hop-by-hop extension"
>>=20
>> I assume this means an extension with the critical flag set? If so,
>> it would be more precise to say that.
>=20
> This draft was split out of a more general draft that covered
> extensions in general. The three paragraphs after the bullet list on
> critical / non-critical extensions apply to all extensions as well as
> the flag bits in the first word of the options area. So this means
> critical header extensions flags and any other types of critical
> options specified in the future.

Okay

[...]


>=20
>> -- section 5:
>>=20
>> Since section 3 is entirely composed of the referenced table, and
>> seems to exist mostly if not entirely for the purpose of this
>> reference, why not just move the table to the IANA considerations
>> section.
>=20
> (Looking at Section 3, I believe the reference there to the IANA
> Considerations Section should be to Section 5 rather than Section 6.)
>=20
> I guess I don't actually see any problem with the current document
> structure that I think flows better for someone reading it from the
> start. I suppose it imposes a tiny burden on someone who is just
> looking at the IANA Considerations Section. I don't see why it would
> be better to make it a tiny bit easier for someone just looking at the
> IANA Considerations Section while imposing a tiny burdne on those
> reading through the document from the start.
>=20

Okay. I was interpreting it as existing entirely for the IANA =
registration--but if you believe it adds value to the "body" of the =
text, I am okay with it.

[...]


From sm@resistor.net  Fri Jun  1 13:34:06 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3842B11E80B0 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 13:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.485
X-Spam-Level: 
X-Spam-Status: No, score=-102.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 IUARcTuMYgZ7 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 13:34:05 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B9C11E80B4 for <ietf@ietf.org>; Fri,  1 Jun 2012 13:34:05 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q51KXxlL009086 for <ietf@ietf.org>; Fri, 1 Jun 2012 13:34:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338582843; i=@resistor.net; bh=iUvWxT8/AN9JvUzKjHeTz1QqtTXReeK5PEZNUZ+3Qzs=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=agHel+/l2vWRr/DRFrCms3pvHwH9kIjKUqOVdrGPh7RhdDkmH3SPIaKYQ0fvgVOau LjA9nliGZKzUzFD9Iv7YsXEKAhTimROgQoYMe2GYPil/HlEpF3MMr1m/aeIVgw5aIY ahveIQydYTJ2jludzoNzjRuyQc4Sm7E1Fevyzlt8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1338582843; i=@resistor.net; bh=iUvWxT8/AN9JvUzKjHeTz1QqtTXReeK5PEZNUZ+3Qzs=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=icxyqPGaJVQ3kELxdSCjZxoyZUUw/EsOkve9u8CppsZVVAzigMBBgsZgjW7vUzN9P pLL3X0bPUraqfY4jfJSaem/XUqHaFi2CKCKrmaRl5kVWsSsraqyUQTqasxTvFDObUL RtivzVqvd3gyfxbU8OVRlkjqo5Pmu5HkUMx4jTbY=
Message-Id: <6.2.5.6.2.20120601123737.0acca170@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 01 Jun 2012 13:23:32 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: RFC 2818 (HTTP Over TLS) to Proposed Standard
In-Reply-To: <20120601164205.25357.54620.idtracker@ietfa.amsl.com>
References: <20120601164205.25357.54620.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 20:34:06 -0000

At 09:42 01-06-2012, IESG Secretary wrote:
>The IESG has received a request from the TLS Working Group to 
>reclassify RFC 2818 (HTTP Over TLS) to Proposed Standard.
>
>The IESG plans to make a decision in the next few weeks, and 
>solicits final comments on this action. Please send substantive 
>comments to the ietf at ietf.org mailing lists by

Could the IESG please use ietf@ietf.org instead of obfuscating the 
email address?  Some of us are lazy especially on Fridays.

Erratum #1077 has been classified as "Held for Document 
Update".  Will there ever be a document update?  Implementing this 
specification requires HTTP/1.1 and TLS 1.0.  I suggest updating the 
reference to RFC 4346 at least and waiting for the updated HTTP specifications.

St. Andre and Mr. Hodges authored a Proposed Standard called 
"Representation and Verification of Domain-Based Application Service 
Identity within Internet Public Key Infrastructure Using X.509 (PKIX) 
Certificates in the Context of Transport Layer Security 
(TLS)".  Quoting from Section 1.4:

   "the procedures described here can be referenced by future
    specifications, including updates to specifications for
    existing application protocols if the relevant technology
    communities agree to do so."

May I suggest taking the above into consideration and at least put 
some minimal effort into a 2818bis?

Regards,
-sm 


From housley@vigilsec.com  Fri Jun  1 14:33:46 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F79B11E80E0 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 14:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.396
X-Spam-Level: 
X-Spam-Status: No, score=-102.396 tagged_above=-999 required=5 tests=[AWL=0.203, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8syd20r138Ra for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 14:33:46 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id A0A0D11E80BC for <ietf@ietf.org>; Fri,  1 Jun 2012 14:33:45 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id AE3039A470F for <ietf@ietf.org>; Fri,  1 Jun 2012 17:33:55 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 125aZ64KCYyL for <ietf@ietf.org>; Fri,  1 Jun 2012 17:33:36 -0400 (EDT)
Received: from [10.73.40.255] (unknown [70.42.157.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 4BC16F2402F for <ietf@ietf.org>; Fri,  1 Jun 2012 17:33:52 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Making the Tao a web page
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4FC8AFA9.1020200@inex.ie>
Date: Fri, 1 Jun 2012 17:33:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <4FC8AFA9.1020200@inex.ie>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 21:33:46 -0000

I have a concern here.  When I did the AD review for this document, I =
was quite surprised how stale it had become.  For example, the document =
told people to send I-Ds to the Secretariat for posting instead of =
pointing to the online I-D submission tool.  If we put it in a wiki, =
there will be more people that can make update, but the publication =
process ensure that an end-to-end read takes place when an update =
published as an RFC.

So, I am left with a few questions:
- What is the similar forcing function if we use a wiki?
- Will the number of people that can make updates eliminate the need for =
such a forcing function?
- Who designates the editor-in-chief of the wiki?

Russ=

From mohta@necom830.hpcl.titech.ac.jp  Fri Jun  1 17:04:48 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4B7D11E807F for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 17:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 spO0TQoSdEGt for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 17:04:48 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 89F5921F8760 for <ietf@ietf.org>; Fri,  1 Jun 2012 17:04:47 -0700 (PDT)
Received: (qmail 97267 invoked from network); 2 Jun 2012 00:05:11 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 2 Jun 2012 00:05:11 -0000
Message-ID: <4FC9585E.6010205@necom830.hpcl.titech.ac.jp>
Date: Sat, 02 Jun 2012 09:03:42 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net>
In-Reply-To: <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jun 2012 00:04:48 -0000

C. M. Heard wrote:

> My one reservation is that I do not think it is strictly necessary
> to ban re-use of the IPv4 ID value in retransmitted non-atomic IPv4
> datagrams.

Do you mean

 >> Sources of non-atomic IPv4 datagrams MUST rate-limit their output
   to comply with the ID uniqueness requirements.

is too strict?

If so, I agree with you.

> On the other hand, the evidence available to me suggests
> that existing implementations overwhelmingly comply with this ban
> anyway, so it does not seem to do any harm.

I think most NAT boxes do not care ID uniqueness.

But, it is a lot worse than that.

Existing routers, which was relying on ID uniqueness of atomic
packets, are now broken when they fragment the atomic packets.

So, the requirement may be:

 >> Sources of non-atomic IPv4 datagrams SHOULD rate-limit their output
   to comply with the ID uniqueness requirements.

or:

 >> Sources of non-atomic IPv4 datagrams is encouraged to rate-limit
their output
   to comply with the ID uniqueness requirements.

In addition, I have one question:

 Is there some document provided to obsolete the following:

   The IPv6 fragment header is present

   when the source has received
   a "packet too big" ICMPv6 error message when the path cannot support
   the required minimum 1280-byte IPv6 MTU and is thus subject to
   translation

 which is meaningless from the beginning, because length of
 IPv6 ID is 32 bit, from which it is impossible to generate
 unique IPv4 ID.

and one comment:

 As expired IDs are referenced, may I suggest to add

   draft-ohta-e2e-nat-00.txt

 along with [Bo11] and [De11].

						Masataka Ohta

From touch@isi.edu  Fri Jun  1 18:22:45 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 637AD11E8094 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 18:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4c1oTy7+3yxl for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 18:22:44 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id D3F6311E8087 for <ietf@ietf.org>; Fri,  1 Jun 2012 18:22:44 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q521MIqB004562 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 1 Jun 2012 18:22:18 -0700 (PDT)
Message-ID: <4FC96ACA.9040800@isi.edu>
Date: Fri, 01 Jun 2012 18:22:18 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4FC9585E.6010205@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jun 2012 01:22:45 -0000

On 6/1/2012 5:03 PM, Masataka Ohta wrote:
> C. M. Heard wrote:
> 
>> My one reservation is that I do not think it is strictly necessary
>> to ban re-use of the IPv4 ID value in retransmitted non-atomic IPv4
>> datagrams.
> 
> Do you mean
> 
>   >>  Sources of non-atomic IPv4 datagrams MUST rate-limit their output
>     to comply with the ID uniqueness requirements.
> 
> is too strict?
> 
> If so, I agree with you.
> 
>> On the other hand, the evidence available to me suggests
>> that existing implementations overwhelmingly comply with this ban
>> anyway, so it does not seem to do any harm.
> 
> I think most NAT boxes do not care ID uniqueness.
> 
> But, it is a lot worse than that.
> 
> Existing routers, which was relying on ID uniqueness of atomic
> packets, are now broken when they fragment the atomic packets.
> 
> So, the requirement may be:
> 
>   >>  Sources of non-atomic IPv4 datagrams SHOULD rate-limit their output
>     to comply with the ID uniqueness requirements.
> 
> or:
> 
>   >>  Sources of non-atomic IPv4 datagrams is encouraged to rate-limit
> their output
>     to comply with the ID uniqueness requirements.

The recommendation in this doc - that such sources MUST rate-limit - is
to comply with the ID uniqueness requirements already in RFC791 that
this doc does not deprecate - e.g., its use to support fragmentation.
It's not that they SHOULD do this in order to comply; if they don't,
they're not in compliance.

We all recognize that there are plenty of non-compliant NAT boxes
(actually, I'd be surprised if there were any compliant ones). Declaring
that non-compliance acceptable is not the purpose of this document.

> In addition, I have one question:
> 
>   Is there some document provided to obsolete the following:
> 
>     The IPv6 fragment header is present
> 
>     when the source has received
>     a "packet too big" ICMPv6 error message when the path cannot support
>     the required minimum 1280-byte IPv6 MTU and is thus subject to
>     translation
> 
>   which is meaningless from the beginning, because length of
>   IPv6 ID is 32 bit, from which it is impossible to generate
>   unique IPv4 ID.

None of which I am aware.

> and one comment:
> 
>   As expired IDs are referenced, may I suggest to add
> 
>     draft-ohta-e2e-nat-00.txt
> 
>   along with [Bo11] and [De11].

The current references - although currently expired - are under current
discussion in INTAREA, and updated versions are expected to be posted by
the time this document is published.

This document is not intended to provide a complete history of A+P
approaches, which would take more than adding a single long expired
reference.

Joe

From mohta@necom830.hpcl.titech.ac.jp  Fri Jun  1 19:47:03 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3EC511E8110 for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 19:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 AhEB-b21faDa for <ietf@ietfa.amsl.com>; Fri,  1 Jun 2012 19:47:03 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id ED11711E808C for <ietf@ietf.org>; Fri,  1 Jun 2012 19:47:02 -0700 (PDT)
Received: (qmail 98108 invoked from network); 2 Jun 2012 02:47:21 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 2 Jun 2012 02:47:21 -0000
Message-ID: <4FC97E57.6070505@necom830.hpcl.titech.ac.jp>
Date: Sat, 02 Jun 2012 11:45:43 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu>
In-Reply-To: <4FC96ACA.9040800@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jun 2012 02:47:04 -0000

Joe Touch wrote:

>> Existing routers, which was relying on ID uniqueness of atomic
>> packets, are now broken when they fragment the atomic packets.

> The recommendation in this doc - that such sources MUST rate-limit - is
> to comply with the ID uniqueness requirements already in RFC791 that
> this doc does not deprecate - e.g., its use to support fragmentation.

It means that the uniqueness requirements must be loosened.

Another example is that, when route changes, routers
fragmenting atomic packets may change, which means rate
limiting does not guarantee ID uniqueness.

> We all recognize that there are plenty of non-compliant NAT boxes

Rest of my examples are plain routers, which has been fully
compliant.

>>    Is there some document provided to obsolete the following:
>>
>>      The IPv6 fragment header is present
>>
>>      when the source has received
>>      a "packet too big" ICMPv6 error message when the path cannot support
>>      the required minimum 1280-byte IPv6 MTU and is thus subject to
>>      translation
>>
>>    which is meaningless from the beginning, because length of
>>    IPv6 ID is 32 bit, from which it is impossible to generate
>>    unique IPv4 ID.
> 
> None of which I am aware.

There should be. May I volunteer?

						Masataka Ohta

From lear@cisco.com  Sat Jun  2 06:00:51 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E65821F8665; Sat,  2 Jun 2012 06:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 yL8b4D4QqjZ5; Sat,  2 Jun 2012 06:00:50 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id E16E221F865A; Sat,  2 Jun 2012 06:00:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=4616; q=dns/txt; s=iport; t=1338642050; x=1339851650; h=message-id:date:from:mime-version:to:cc:subject; bh=pOhlmC+eumfcB67KHpASchgU1L+bBCW8LzySfz2x8hQ=; b=MssU/AE/GnLbWt1c2cvdQ7+AoI8GMfJgEVV5jgYKO5bq6HyQSIvb21wQ ZliqoiIRbPPa5ukZCrC1/3wx4i0/8OSwy2SjU4sXdxCvFB+I26T+sLBGx /mIbJJvUInGwCjcSvDfSmg+8CugrGxL2zKcO6RPIIJsY7g1AzM6JeZx10 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAIcNyk+Q/khL/2dsb2JhbABFhU6uT4EHghgBAQEDEwEQVQEFGhANFgsCCwMCAQIBSwEMAQcBAR6HZAWXUY0Wkg2LEYR+gRIDlRuOEIFmgmI
X-IronPort-AV: E=Sophos;i="4.75,701,1330905600"; d="scan'208,217";a="5291680"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-3.cisco.com with ESMTP; 02 Jun 2012 13:00:48 +0000
Received: from dhcp-10-61-99-222.cisco.com (dhcp-10-61-99-222.cisco.com [10.61.99.222]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q52D0lu1024078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 2 Jun 2012 13:00:48 GMT
Message-ID: <4FCA0E7F.7020109@cisco.com>
Date: Sat, 02 Jun 2012 15:00:47 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: draft-ietf-intarea-ipv4-update.all@tools.ietf.org, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Apps Directorate Review of draft-ietf-intarea-ipv4-id-update-05
X-Enigmail-Version: 1.4.1
Content-Type: multipart/alternative; boundary="------------060505010801040403010400"
Cc: Internet Area <int-area@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jun 2012 13:00:51 -0000

This is a multi-part message in MIME format.
--------------060505010801040403010400
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


Document: draft-ietf-intarea-ipv4-id-update-05
Title: Updated Specification of the IPv4 ID Field
Reviewer: Eliot Lear
Review Date: 2 June 2012
IETF Last Call Date: 31 May  2012


Summary: This draft is quite well written, and is *very* nearly ready
for publication.

This draft is well written, and from the applications perspective
represents an important step to improving performance and error
reduction.  It uses a new requirements call-out style that I would class
as experimental, but not bad.  It is worth people reading this draft and
deciding if they agree with Joe's approach.

Major issues:

None (Yay!).

Minor issues:

Section 4 needs to be reconciled a bit with Section 6.1.  Specifically:

>  The IPv4 ID field can be useful for other purposes. 


And

  >> IPv4 ID field MUST NOT be used for purposes other than
   fragmentation and reassembly.


My suggestion is to drop the above sentence from Section 4.

In Section 6.1:


>    Datagram de-duplication can be accomplished using hash-based
>    duplicate detection for cases where the ID field is absent.

Under what circumstances would the ID field be absent?

>    >> Sources of non-atomic IPv4 datagrams using strong integrity checks
>    MAY reuse the ID within MSL values smaller than is typical.

Is the issue really the source using strong integrity checks or the
destination in this context?  What is typical?

Nit:

Shouldn't Sections 3, 4, and 5, really be Sections 2.1, 2.2, and 2.3?


Eliot



--------------060505010801040403010400
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <br>
    Document: draft-ietf-intarea-ipv4-id-update-05<br>
    Title:
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    Updated Specification of the IPv4 ID Field<br>
    Reviewer: Eliot Lear<br>
    Review Date: 2 June 2012<br>
    IETF Last Call Date: 31 MayÂ  2012<br>
    <br>
    <br>
    Summary: This draft is quite well written, and is <b>very</b>
    nearly ready for publication.<br>
    <br>
    This draft is well written, and from the applications perspective
    represents an important step to improving performance and error
    reduction.Â  It uses a new requirements call-out style that I would
    class as experimental, but not bad.Â  It is worth people reading this
    draft and deciding if they agree with Joe's approach.<br>
    <br>
    Major issues:<br>
    <br>
    None (Yay!).<br>
    <br>
    Minor issues:<br>
    <br>
    Section 4 needs to be reconciled a bit with Section 6.1.Â 
    Specifically:<br>
    <br>
    <blockquote type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <pre> The IPv4 ID field can be useful for other purposes. </pre>
    </blockquote>
    <br>
    <br>
    And<br>
    <br>
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <pre>  &gt;&gt; IPv4 ID field MUST NOT be used for purposes other than
   fragmentation and reassembly.</pre>
    <br>
    My suggestion is to drop the above sentence from Section 4.<br>
    <br>
    In Section 6.1:<br>
    <br>
    <br>
    <blockquote type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <pre>   Datagram de-duplication can be accomplished using hash-based
   duplicate detection for cases where the ID field is absent.
</pre>
    </blockquote>
    <br>
    Under what circumstances would the ID field be absent?<br>
    <br>
    <blockquote type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <pre>   &gt;&gt; Sources of non-atomic IPv4 datagrams using strong integrity checks
   MAY reuse the ID within MSL values smaller than is typical.
</pre>
    </blockquote>
    <br>
    Is the issue really the source using strong integrity checks or the
    destination in this context?Â  What is typical?<br>
    <br>
    Nit:<br>
    <br>
    Shouldn't Sections 3, 4, and 5, really be Sections 2.1, 2.2, and
    2.3?<br>
    <br>
    <br>
    Eliot<br>
    <br>
    <br>
  </body>
</html>

--------------060505010801040403010400--

From touch@isi.edu  Sat Jun  2 07:50:30 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C95321F8535; Sat,  2 Jun 2012 07:50:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hdACuNWqRnzV; Sat,  2 Jun 2012 07:50:29 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDFA21F8531; Sat,  2 Jun 2012 07:50:29 -0700 (PDT)
Received: from [192.168.1.95] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q52Eo1WA022182 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 2 Jun 2012 07:50:06 -0700 (PDT)
Subject: Re: [Int-area] Apps Directorate Review of draft-ietf-intarea-ipv4-id-update-05
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Joe Touch <touch@isi.edu>
In-Reply-To: <4FCA0E7F.7020109@cisco.com>
Date: Sat, 2 Jun 2012 07:50:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <ACEDFEC8-1525-47B0-92D8-FB7CB1D22A0C@isi.edu>
References: <4FCA0E7F.7020109@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1278)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Internet Area <int-area@ietf.org>, draft-ietf-intarea-ipv4-update.all@tools.ietf.org, IETF Discussion <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jun 2012 14:50:30 -0000

Hi, Eliot,

On Jun 2, 2012, at 6:00 AM, Eliot Lear wrote:

>=20
> Document: draft-ietf-intarea-ipv4-id-update-05
> Title: Updated Specification of the IPv4 ID Field
> Reviewer: Eliot Lear
> Review Date: 2 June 2012
> IETF Last Call Date: 31 May  2012
>=20
>=20
> Summary: This draft is quite well written, and is very nearly ready =
for publication.
>=20
> This draft is well written, and from the applications perspective =
represents an important step to improving performance and error =
reduction.  It uses a new requirements call-out style that I would class =
as experimental, but not bad.  It is worth people reading this draft and =
deciding if they agree with Joe's approach.
>=20
> Major issues:
>=20
> None (Yay!).
>=20
> Minor issues:
>=20
> Section 4 needs to be reconciled a bit with Section 6.1.  =
Specifically:
>=20
>>  The IPv4 ID field can be useful for other purposes.=20
>=20
>=20
> And
>=20
>   >> IPv4 ID field MUST NOT be used for purposes other than
>    fragmentation and reassembly.
>=20
>=20
> My suggestion is to drop the above sentence from Section 4.

The two are not contradictory - the ID can be useful, but generating it =
correctly is prohibitive and typically not done.

> In Section 6.1:
>=20
>=20
>>    Datagram de-duplication can be accomplished using hash-based
>>    duplicate detection for cases where the ID field is absent.
>>=20
>=20
> Under what circumstances would the ID field be absent?

Replace "absent" with "known not unique".

>>    >> Sources of non-atomic IPv4 datagrams using strong integrity =
checks
>>    MAY reuse the ID within MSL values smaller than is typical.
>>=20
>=20
> Is the issue really the source using strong integrity checks or the =
destination in this context?  What is typical?

The onus is on the source (of non-atomic datagrams) - if it includes =
strong integrity checks (that are presumably validated by the receiver), =
it then has more flexibility in its generation of the iD values.

> Nit:
>=20
> Shouldn't Sections 3, 4, and 5, really be Sections 2.1, 2.2, and 2.3?

Not subsections of 2, but perhaps "3, 3.1, 3.2"?=20

Joe=

From joelja@bogus.com  Sat Jun  2 20:50:48 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFE9D21F84D6 for <ietf@ietfa.amsl.com>; Sat,  2 Jun 2012 20:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 noCPkCBJLN+l for <ietf@ietfa.amsl.com>; Sat,  2 Jun 2012 20:50:48 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE7921F84D5 for <ietf@ietf.org>; Sat,  2 Jun 2012 20:50:48 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (50-0-150-57.dsl.static.sonic.net [50.0.150.57]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q533ojM1064834 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 3 Jun 2012 03:50:46 GMT (envelope-from joelja@bogus.com)
Message-ID: <4FCADF15.3070401@bogus.com>
Date: Sat, 02 Jun 2012 20:50:45 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Klaas Wierenga <klaas@cisco.com>
Subject: Re: Colloquial language [Re: Last Call:	<draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task	Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>	<4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com>	<4FC716B8.2090208@dcrocker.net> <4FC71CC9.2000604@gmail.com>	<4FC72213.8060800@bbiw.net> <4FC732D3.7090904@cs.tcd.ie> <4FC7345E.807@cisco.com>
In-Reply-To: <4FC7345E.807@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 03 Jun 2012 03:50:46 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 03:50:49 -0000

On 5/31/12 02:05 , Klaas Wierenga wrote:
> On 5/31/12 10:58 AM, Stephen Farrell wrote:
>>
>> I'm with Brian and Yoav on this. I don't see a need
>> to change here. And I do think we might lose something
>> if we become too PC. If a bunch of non-native speakers
>> did say "yes, I found that made the document less
>> useful" then I'd be more convinced that all these
>> changes were worth it.
> 
> As a non-native speaker I agree. I think colloquial is fine. The one
> thing causes me some trouble is all the references that Americans make
> to sports that nobody in the civilized world cares about ;-) ("left
> field", "Hail Mary passes"

If the Congregatio a Sancta Cruce hadn't come to North America from Le
Mans France and specifically to South Bend Indiana there would be no
Hail Mary.


From heard@pobox.com  Sat Jun  2 21:21:42 2012
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9792811E8093 for <ietf@ietfa.amsl.com>; Sat,  2 Jun 2012 21:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599]
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 JLVTS3j6JRNq for <ietf@ietfa.amsl.com>; Sat,  2 Jun 2012 21:21:41 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87EDD11E8091 for <ietf@ietf.org>; Sat,  2 Jun 2012 21:21:39 -0700 (PDT)
Received: (qmail 19638 invoked from network); 2 Jun 2012 21:21:39 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Jun 2012 21:21:39 -0700
Date: Sat, 2 Jun 2012 21:21:38 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: IETF Discussion <ietf@ietf.org>
Subject: Re: [Int-area] Apps Directorate Review of draft-ietf-intarea-ipv4-id-update-05
In-Reply-To: <ACEDFEC8-1525-47B0-92D8-FB7CB1D22A0C@isi.edu>
Message-ID: <Pine.LNX.4.64.1206022113110.17026@shell4.bayarea.net>
References: <4FCA0E7F.7020109@cisco.com> <ACEDFEC8-1525-47B0-92D8-FB7CB1D22A0C@isi.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Internet Area <int-area@ietf.org>, Apps Discussion <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 04:21:42 -0000

On Sat, 2 Jun 2012, Joe Touch wrote:
> Hi, Eliot,
> 
> On Jun 2, 2012, at 6:00 AM, Eliot Lear wrote:
> 
> > 
> > Document: draft-ietf-intarea-ipv4-id-update-05
> > Title: Updated Specification of the IPv4 ID Field
> > Reviewer: Eliot Lear
> > Review Date: 2 June 2012
> > IETF Last Call Date: 31 May  2012
> > 
> > 
> > Summary: This draft is quite well written, and is very nearly ready for publication.
> > 
> > This draft is well written, and from the applications 
> > perspective represents an important step to improving 
> > performance and error reduction.  It uses a new requirements 
> > call-out style that I would class as experimental, but not bad.  
> > It is worth people reading this draft and deciding if they agree 
> > with Joe's approach.

FWIW, I thought it was helpful.

> > Major issues:
> > 
> > None (Yay!).
> > 
> > Minor issues:
> > 
> > Section 4 needs to be reconciled a bit with Section 6.1.  Specifically:
> > 
> >>  The IPv4 ID field can be useful for other purposes. 
> > 
> > 
> > And
> > 
> >   >> IPv4 ID field MUST NOT be used for purposes other than
> >    fragmentation and reassembly.
> > 
> > 
> > My suggestion is to drop the above sentence from Section 4.
> 
> The two are not contradictory - the ID can be useful, but 
> generating it correctly is prohibitive and typically not done.

After re-reading the text I agree with Eliot that it is confusing.  
Dropping the sentence in Section 4 would be fine.  Another 
possibility would be to reword it along the following lines:

  Other uses have been envisioned for the IPv4 ID field.

> > In Section 6.1:
> > 
> > 
> >>    Datagram de-duplication can be accomplished using hash-based
> >>    duplicate detection for cases where the ID field is absent.
> >> 
> > 
> > Under what circumstances would the ID field be absent?
> 
> Replace "absent" with "known not unique".

Better, I think, would be "not known to be unique".

> >>    >> Sources of non-atomic IPv4 datagrams using strong integrity checks
> >>    MAY reuse the ID within MSL values smaller than is typical.
> >> 
> > 
> > Is the issue really the source using strong integrity checks or 
> > the destination in this context?  What is typical?
> 
> The onus is on the source (of non-atomic datagrams) - if it 
> includes strong integrity checks (that are presumably validated by 
> the receiver), it then has more flexibility in its generation of 
> the iD values.
> 
> > Nit:
> > 
> > Shouldn't Sections 3, 4, and 5, really be Sections 2.1, 2.2, and 2.3?
> 
> Not subsections of 2, but perhaps "3, 3.1, 3.2"?

That would be fine but I'm also OK with leaving the document the way 
it is (especially if it would get it into the publication queue 
faster).

//cmh

From heard@pobox.com  Sat Jun  2 21:34:18 2012
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF48B11E808E for <ietf@ietfa.amsl.com>; Sat,  2 Jun 2012 21:34:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
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 fWl+HwWzL9IN for <ietf@ietfa.amsl.com>; Sat,  2 Jun 2012 21:34:17 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7767A11E8089 for <ietf@ietf.org>; Sat,  2 Jun 2012 21:34:17 -0700 (PDT)
Received: (qmail 23688 invoked from network); 2 Jun 2012 21:34:16 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Jun 2012 21:34:16 -0700
Date: Sat, 2 Jun 2012 21:34:16 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: IETF <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
In-Reply-To: <4FC9585E.6010205@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.LNX.4.64.1206022127550.17026@shell4.bayarea.net>
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 04:34:18 -0000

On Sat, 2 Jun 2012, Masataka Ohta wrote:
> Existing routers, which was relying on ID uniqueness of atomic
> packets, are now broken when they fragment the atomic packets.

Such routers were always broken.  An atomic packet has DF=0 and any 
router fragmenting such a packet was and is non-compliant with 
the relevant specifications (RFCs 791, 1122, 1812).

//cmh

From glenzorn@gmail.com  Sat Jun  2 21:54:02 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C24C21F848A; Sat,  2 Jun 2012 21:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 oc0xjAjGOSAI; Sat,  2 Jun 2012 21:54:01 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 944BE21F8466; Sat,  2 Jun 2012 21:54:01 -0700 (PDT)
Received: by dacx6 with SMTP id x6so4350273dac.31 for <multiple recipients>; Sat, 02 Jun 2012 21:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:cc:date:in-reply-to:references :organization:content-type:x-mailer:content-transfer-encoding :mime-version; bh=SW8hKCbAQgq3FmuGaCh+kPbttGlsBCtrkCRMo3sbY+Q=; b=rfh+j1fhkn/UQjPKIUGY4adFK/7MyusW7H68QgCgrqR7q+mc1hhhy8DBYHs68vm15E 1riNaXtM3F4DzWshYzO5oUCBdlN6MOlAFnPzho6QhLJ3S4Vzn2aSbfBJkc9HXE0dECUP /CDc2Bbg71aBfT/yn4sdiKg4DkO6wevXuepTFgiQRAgjz3dNFoAzEqX0AlO3tVVdrWSr FlcNdMUQyiktlDJdvkamyvqxxq5KBkVsbfvVdzzbcmnEBN/v94TNOXtmFSnpZXkGK+FH UOIZ5J6raVNcvqf98+KHvXp+Az0bN3QgiCqUkNFoyI+UwvI2FzoARxwFRZLOym+lBTYO u/cQ==
Received: by 10.68.219.162 with SMTP id pp2mr25898071pbc.85.1338699241397; Sat, 02 Jun 2012 21:54:01 -0700 (PDT)
Received: from [192.168.1.99] (ppp-58-11-241-69.revip2.asianet.co.th. [58.11.241.69]) by mx.google.com with ESMTPS id iv8sm326444pbc.53.2012.06.02.21.53.59 (version=SSLv3 cipher=OTHER); Sat, 02 Jun 2012 21:54:00 -0700 (PDT)
Message-ID: <1338699237.5620.3.camel@gwz-laptop>
Subject: Re: [Int-area] Apps Directorate Review of draft-ietf-intarea-ipv4-id-update-05
From: Glen Zorn <glenzorn@gmail.com>
To: "C. M. Heard" <heard@pobox.com>
Date: Sun, 03 Jun 2012 11:53:57 +0700
In-Reply-To: <Pine.LNX.4.64.1206022113110.17026@shell4.bayarea.net>
References: <4FCA0E7F.7020109@cisco.com> <ACEDFEC8-1525-47B0-92D8-FB7CB1D22A0C@isi.edu> <Pine.LNX.4.64.1206022113110.17026@shell4.bayarea.net>
Organization: Network Zen
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.2- 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
Cc: Internet Area <int-area@ietf.org>, IETF Discussion <ietf@ietf.org>, Apps Discussion <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 04:54:02 -0000

On Sat, 2012-06-02 at 21:21 -0700, C. M. Heard wrote:

...

> > > In Section 6.1:
> > > 
> > > 
> > >>    Datagram de-duplication can be accomplished using hash-based
> > >>    duplicate detection for cases where the ID field is absent.
> > >> 
> > > 
> > > Under what circumstances would the ID field be absent?
> > 
> > Replace "absent" with "known not unique".
> 
> Better, I think, would be "not known to be unique".

Except that the two are not semantically equivalent.

...


From heard@pobox.com  Sat Jun  2 22:26:44 2012
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B35021F8484 for <ietf@ietfa.amsl.com>; Sat,  2 Jun 2012 22:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level: 
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599]
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 UHb9vFd--oNf for <ietf@ietfa.amsl.com>; Sat,  2 Jun 2012 22:26:44 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CCC921F8483 for <ietf@ietf.org>; Sat,  2 Jun 2012 22:26:44 -0700 (PDT)
Received: (qmail 31369 invoked from network); 2 Jun 2012 22:00:02 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Jun 2012 22:00:02 -0700
Date: Sat, 2 Jun 2012 22:00:01 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: IETF Discussion <ietf@ietf.org>
Subject: Re: [Int-area] Apps Directorate Review of draft-ietf-intarea-ipv4-id-update-05
In-Reply-To: <1338699237.5620.3.camel@gwz-laptop>
Message-ID: <Pine.LNX.4.64.1206022157100.17026@shell4.bayarea.net>
References: <4FCA0E7F.7020109@cisco.com> <ACEDFEC8-1525-47B0-92D8-FB7CB1D22A0C@isi.edu> <Pine.LNX.4.64.1206022113110.17026@shell4.bayarea.net> <1338699237.5620.3.camel@gwz-laptop>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Internet Area <int-area@ietf.org>, Apps Discussion <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 05:26:44 -0000

On Sun, 3 Jun 2012, Glen Zorn wrote:
> On Sat, 2012-06-02 at 21:21 -0700, C. M. Heard wrote:
> 
> ...
> 
> > > > In Section 6.1:
> > > > 
> > > > 
> > > >>    Datagram de-duplication can be accomplished using hash-based
> > > >>    duplicate detection for cases where the ID field is absent.
> > > >> 
> > > > 
> > > > Under what circumstances would the ID field be absent?
> > > 
> > > Replace "absent" with "known not unique".
> > 
> > Better, I think, would be "not known to be unique".
> 
> Except that the two are not semantically equivalent.

Indeed.  That was why I suggested the change.

//cmh

From d3e3e3@gmail.com  Sun Jun  3 06:44:01 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6DB21F8570; Sun,  3 Jun 2012 06:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.17
X-Spam-Level: 
X-Spam-Status: No, score=-102.17 tagged_above=-999 required=5 tests=[AWL=-0.871, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 50b8S2+YvV9I; Sun,  3 Jun 2012 06:44:00 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3D71821F856D; Sun,  3 Jun 2012 06:44:00 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so3187714ghb.31 for <multiple recipients>; Sun, 03 Jun 2012 06:43:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=kGeZky1e46ToxtZmAoTyz83ypNSEXm4SsuMZC4tpVhk=; b=s5+KB5GcFWGD178RlZTswLZrynRF/o0gvLwbSFE5RfvVSEqvuf7oUpg6t/WRuZ6X04 VTRi2TXRyTfg1TegaKMSTETdsTyizC2Kpjskz442PBmEvSXuLs3swcBOS51NeE1tyZ43 c4Ic+p9ox9Jl8WCGso65sWTGT5XH4rJ9qx8+qeJvMUAkGkDen5MuRZaUoGPjdc12MKvX AoIByiIyUCVQw/Alr7/QfIkhwCtQSSQPpC8trYPXx7ye33nqlGgO32nrBs1TCZRAqZlG 1j8Kw/N33ru5u921tyNBZYVC0gbmBYNWiHKCgZ/1UI4iEQcku1ROCPmYf0DrhrkWa2Jx PLmw==
Received: by 10.50.196.201 with SMTP id io9mr5636621igc.58.1338731039264; Sun, 03 Jun 2012 06:43:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.99.228 with HTTP; Sun, 3 Jun 2012 06:43:39 -0700 (PDT)
In-Reply-To: <69241DCD-C349-4D15-8B92-58D05F216BF5@nostrum.com>
References: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com> <CAF4+nEESCSkUgM2Wzr5MXfW5su5Og_XA0dyO+gksfN2LAzCCWw@mail.gmail.com> <69241DCD-C349-4D15-8B92-58D05F216BF5@nostrum.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 3 Jun 2012 09:43:39 -0400
Message-ID: <CAF4+nEH0G-8JD5XuSBRp2xcWtdFUmh0x0nw=Q-9gV4Jtkp74iw@mail.gmail.com>
Subject: Re: Gen-ART LC/Telechat review of draft-ietf-trill-rbridge-extension-04
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: draft-ietf-trill-rbridge-extension.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 13:44:01 -0000

Hi Ben,

On Fri, Jun 1, 2012 at 3:18 PM, Ben Campbell <ben@nostrum.com> wrote:
> Thanks for the quick response. Further comments inline. I deleted section=
s that do not appear to need further discussion.
>
> Thanks!
>
> Ben.
>
> On Jun 1, 2012, at 10:45 AM, Donald Eastlake wrote:
>
>> Hi Ben,
>>
>> Thanks for your review. See responses below.
>>
>> On Thu, May 31, 2012 at 6:08 PM, Ben Campbell <ben@nostrum.com> wrote:
>>
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>> Please wait for direction from your document shepherd
>>> or AD before posting a new version of the draft.
>>>
>>> Document: draft-ietf-trill-rbridge-extension-04
>>> Reviewer: Ben Campbell
>>> Review Date: 2012-05-31
>>> IETF LC End Date: 2012-06-07
>>> IESG Telechat date: 2012-06-07
>>>
>>> Note: Since this draft is on the agenda of the IESG Telechat on the
>>> same day that the IETF last call expires, this review is intended
>>> for both purposes.
>>>
>>> Summary:
>>>
>>> This draft is almost ready for publication as a proposed standard,
>>> but I have some clarification questions and comments that should be
>>> considered prior to publication.
>>>
>>> Major issues:
>>>
>>> None
>>>
>>> Minor issues:
>>>
>>> -- section 2, general:
>>>
>>> Do the authors assume that all TRILL extensions will follow this
>>> spec? Since RFC6325 already specifies an extension mechanism, what
>>> stops an extension from ignoring this spec and doing something
>>> different? Does it hurt if they do?
>>
>> I am not aware of any conflicts between this draft and RFC 6325. RFC
>> 6325 provides the broadest header option framework, for example
>> specifying the field for the length of the options area and the
>> initial two critical summary bits. This document fills in the
>> structure and allocation mechanism of the remaining bits in the first
>> 4-byte word of the options area, consistent with and repeating some
>> material from RFC 6325, but leaving specification of the remainder of
>> the options area for future documents, which should be consistent with
>> both RFC 6325 and this document. (For example, some future version of
>> draft-ietf-trill-rbridge-options.)
>
> I agree there is no conflict--this draft adds details, but doesn't seem t=
o contradict anything in the RFC.
>
>>
>> However, neither RFC 6325 nor this document can actually actually bind
>> the IETF against adopting future standards describing extensions that
>> do not conform.
>
> Certainly. Nothing can do that. The IETF can always update a protocol to =
change normative language, no matter how strongly it was stated originally =
:-)
>
>> If future changes do not follow RFC 6325 or this
>> document, for example changing the location or interpretation of the
>> option length field in the TRILL Header or changing the interpretation
>> of the critical summary bits in the first word of the options area,
>> then this would break hardware and software implementations that
>> depend on RFC 6325 and/or this document. But I trust the IETF to
>> adhere to its usually high standards for backwards compatibility.
>>
>> Perhaps this draft should, in the first page header, say "Updates:
>> 6325", not in the sense that it makes a change but in the sense that
>> it fills in more details.
>>
>
> Assuming the additional details in this draft comprise preferred extensio=
n mechanism, then I think it makes sense to say that somewhere (perhaps a S=
HOULD strength), and also mark it as updating 6325. Adding details is still=
 an update.

OK.

>>> -- section 2, 3rd paragraph from end: "Non-critical extensions can
>>> =A0 be safely ignored."
>>>
>>> Is that intended to be normative? (Seems like it should be, since
>>> behavior for critical extensions is normative).
>>
>> I think of it as more like the definition of "non-critical".
>
> Sure--I mainly mention it to be consistent with the text for "critical" e=
xtensions, since it did use normative language about dropping frames.
>
>>
>>> -- section 2.1, 1st paragraph, last sentence:
>>>
>>> Redundant with normative language in previous section.
>>
>> ? There is a normative requirement to discard frames with any
>> unimplemented critical hop-by-hop options present, which might be
>> thought to require examination of all options (something manifestly
>> impossible since the format of options beyond the first word of the
>> options area is not yet normatively specified). The sentence to which
>> you refer just clarifies that testing the appropriate crtical summary
>> bit(s) in the first word of the options area, if that word is present,
>> is all that is required.
>
> section 2 says "Any RBridge receiving a frame with a critical hop-by-hop =
extension =A0that it does not implement MUST discard the frame...". Section=
 2.1 says "If an RBridge does not implement all critical flags in a TRILL D=
ata frame, it MUST discard the frame..." These really seem like the same MU=
ST (i.e, if you updated one but not the other, you would have an ambiguous =
state). The same is true for the egress bit.
>
> I understand that you want to draw the connection between a "critical ext=
ension" and "critical flags", but it's better to avoid having multiple bits=
 of authoritative text for the same normative requirement. Perhaps it might=
 be better to say something like "If the RBridge does not implement all cri=
tical flags... it MUST treat the frame as having an unimplemented critical =
extension as described in section 2"

I'm OK with your suggested wording.

>>
>>> -- section 2.3, first paragraph:
>>>
>>> Is the first sentence intended as normative?
>>
>> Yes. When one is describing part of a protocol and you say that some
>> particular contiguous block of bits is some particular field (and then
>> possibly describe the sub-structure of that field) isn't that always
>> normative?
>
> Never mind, I misread the sentence. Sorry for the confusion.
>
>>
>>> -- section 6, last paragraph:
>>>
>>> No security implications of this are mentioned. Is it really a
>>> security consideration?
>>>
>>> Also, is this more likely to be set incorrectly than all the other
>>> things that some implementation might screw up, so that it warrants
>>> special treatment?
>>
>> I tend to think that a discussion of what happens if bits are
>> corrupted or incorrectly set is something reasonable for the Security
>> Considerations section, although it could be elsewhere. The second
>> paragraph/sentence of this section says that security considerations
>> for any bits in the first word of the options area will be in the
>> document specifying those bits. This document specifies the critical
>> summary bits and the RBridge Channel Alert bits so there is text on
>> both of those in its Security Considerations Section.
>
> On re-reading the paragraph, I can see interpreting it to mean that incor=
rectly set flags explicitly do not cause a security problem, which I agree =
is reasonable to say in the security considerations. So, never mind :-)
>
> [...]
>
>
>>>
>>> -- section 2, bullet list, 2nd bullet: " ... which would only
>>> =A0 necessarily affect the RBridge(s) where a TRILL frame is
>>> =A0 decapsulated"
>>>
>>> Does that mean it always affects the decapsulating RBridge but might
>>> effect transit RBridges as well?
>>
>> Yes.
>>
>
> Okay, no problem.
>
>>> -- section 2, first paragraph after bullet list: "critical
>>> =A0 hop-by-hop extension"
>>>
>>> I assume this means an extension with the critical flag set? If so,
>>> it would be more precise to say that.
>>
>> This draft was split out of a more general draft that covered
>> extensions in general. The three paragraphs after the bullet list on
>> critical / non-critical extensions apply to all extensions as well as
>> the flag bits in the first word of the options area. So this means
>> critical header extensions flags and any other types of critical
>> options specified in the future.
>
> Okay
>
> [...]
>
>
>>
>>> -- section 5:
>>>
>>> Since section 3 is entirely composed of the referenced table, and
>>> seems to exist mostly if not entirely for the purpose of this
>>> reference, why not just move the table to the IANA considerations
>>> section.
>>
>> (Looking at Section 3, I believe the reference there to the IANA
>> Considerations Section should be to Section 5 rather than Section 6.)
>>
>> I guess I don't actually see any problem with the current document
>> structure that I think flows better for someone reading it from the
>> start. I suppose it imposes a tiny burden on someone who is just
>> looking at the IANA Considerations Section. I don't see why it would
>> be better to make it a tiny bit easier for someone just looking at the
>> IANA Considerations Section while imposing a tiny burdne on those
>> reading through the document from the start.
>>
>
> Okay. I was interpreting it as existing entirely for the IANA registratio=
n--but if you believe it adds value to the "body" of the text, I am okay wi=
th it.
>
> [...]

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

From warren@kumari.net  Sun Jun  3 08:21:47 2012
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17AC421F8570 for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 08:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level: 
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 zXIevjbPqWfG for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 08:21:46 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 7A60321F8518 for <ietf@ietf.org>; Sun,  3 Jun 2012 08:21:46 -0700 (PDT)
Received: from [192.168.100.40] (unknown [207.34.158.233]) by vimes.kumari.net (Postfix) with ESMTPSA id 53A3C1B402FF; Sun,  3 Jun 2012 11:21:45 -0400 (EDT)
Subject: Re: [IETF] Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <Pine.LNX.4.64.1206022127550.17026@shell4.bayarea.net>
Date: Sun, 3 Jun 2012 11:21:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <35224171-BE58-4875-BE3A-7EAE7BB8B18D@kumari.net>
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <Pine.LNX.4.64.1206022127550.17026@shell4.bayarea.net>
To: "C. M. Heard" <heard@pobox.com>
X-Mailer: Apple Mail (2.1278)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 15:21:47 -0000

--=20
No man is an island, But if you take a bunch of dead guys and tie them =
together, they make a pretty good raft.
                --Anon.


On Jun 3, 2012, at 12:34 AM, C. M. Heard wrote:

> On Sat, 2 Jun 2012, Masataka Ohta wrote:
>> Existing routers, which was relying on ID uniqueness of atomic
>> packets, are now broken when they fragment the atomic packets.
>=20
> Such routers were always broken.  An atomic packet has DF=3D0 and any=20=

> router fragmenting such a packet was and is non-compliant with=20
> the relevant specifications (RFCs 791, 1122, 1812).

Sorry, but no=85.

Not following the RFC !=3D broken. Not following the RFC =3D=3D =
non-compliant.

There are numerous places where implementations do not follow the specs =
for various reasons, ranging from simply not bothering, through =
philosophical differences to customers paying for non-compliant feature =
X.

Sorry, I'm in a somewhat pedantic mood, and I saw a soapbox, so I =
climbed up on it=85

W

>=20
> //cmh
>=20


From dhc@dcrocker.net  Sun Jun  3 11:13:30 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F54B21F8460 for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 11:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.74
X-Spam-Level: 
X-Spam-Status: No, score=-4.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
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 J1mtVSORXp-X for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 11:13:29 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3ED8B21F845E for <ietf@ietf.org>; Sun,  3 Jun 2012 11:13:29 -0700 (PDT)
Received: from [192.168.2.101] (g231207152.adsl.alicedsl.de [92.231.207.152]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q53IDQHt029632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 3 Jun 2012 11:13:28 -0700
Message-ID: <4FCBA944.8060201@dcrocker.net>
Date: Sun, 03 Jun 2012 20:13:24 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: maybe it's getting real
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 03 Jun 2012 11:13:28 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 18:13:30 -0000

Sitting in a pub in the Tiergarten metro station, in Berlin, today, I 
checked whether there were any open-access wireless points around.

There weren't.

But one of the nets had an SSID of IPV6...

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From paul@cypherpunks.ca  Sun Jun  3 11:52:33 2012
Return-Path: <paul@cypherpunks.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6018921F85A4 for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 11:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 qz9v8oqC6aXD for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 11:52:33 -0700 (PDT)
Received: from letoams.cypherpunks.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id E844E21F85A3 for <ietf@ietf.org>; Sun,  3 Jun 2012 11:52:32 -0700 (PDT)
Received: by letoams.cypherpunks.ca (Postfix, from userid 500) id CCC16853FD; Sun,  3 Jun 2012 14:52:28 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by letoams.cypherpunks.ca (Postfix) with ESMTP id BEF788244F; Sun,  3 Jun 2012 14:52:28 -0400 (EDT)
Date: Sun, 3 Jun 2012 14:52:28 -0400 (EDT)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: dcrocker@bbiw.net
Subject: Re: maybe it's getting real
In-Reply-To: <4FCBA944.8060201@dcrocker.net>
Message-ID: <alpine.LFD.2.02.1206031451320.22782@bofh.nohats.ca>
References: <4FCBA944.8060201@dcrocker.net>
User-Agent: Alpine 2.02 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 18:52:33 -0000

On Sun, 3 Jun 2012, Dave Crocker wrote:

> Subject: maybe it's getting real
> 
> Sitting in a pub in the Tiergarten metro station, in Berlin, today, I checked 
> whether there were any open-access wireless points around.
>
> There weren't.

It's very unfortunate "not sharing bandwidth" is getting real.

Paul

From mohta@necom830.hpcl.titech.ac.jp  Sun Jun  3 12:13:27 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 250F521F85FD for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 12:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 IUWHRnkxSabR for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 12:13:26 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 568D621F85FC for <ietf@ietf.org>; Sun,  3 Jun 2012 12:13:26 -0700 (PDT)
Received: (qmail 15355 invoked from network); 3 Jun 2012 19:14:21 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 3 Jun 2012 19:14:21 -0000
Message-ID: <4FCBB71E.9080209@necom830.hpcl.titech.ac.jp>
Date: Mon, 04 Jun 2012 04:12:30 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <Pine.LNX.4.64.1206022127550.17026@shell4.bayarea.net>
In-Reply-To: <Pine.LNX.4.64.1206022127550.17026@shell4.bayarea.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 19:13:27 -0000

C. M. Heard wrote:

>> Existing routers, which was relying on ID uniqueness of atomic
>> packets, are now broken when they fragment the atomic packets.
> 
> Such routers were always broken.  An atomic packet has DF=0 and any
> router fragmenting such a packet was and is non-compliant with
> the relevant specifications (RFCs 791, 1122, 1812).

Thank you. I have overlooked that atomic implied DF=1.

But, then,

   >> Sources emitting non-atomic datagrams MUST NOT repeat IPv4 ID
   values within one MSL for a given source address/destination
   address/protocol triple.

makes most, if not all, IPv4 hosts non compliant if MSL=2min.

Worse, without hard value of MSL, it is a meaningless
requirement. Note that MSL=2min derived from RFC793 breaks
150Mbps TCP.

The proper solution, IMHO, to the ID uniqueness is to request
a destination host drop fragments from a source host after
it receives tens (or hundreds) of packets with different IDs
from the same source host.

A source host, then, is only required to remember the
previous ID used for each destination.

						Masataka Ohta

From joelja@bogus.com  Sun Jun  3 12:35:04 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 788A421F84A5 for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 12:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 BHk8KVD+wtcz for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 12:35:04 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1C3C221F844C for <ietf@ietf.org>; Sun,  3 Jun 2012 12:35:04 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q53JYsR2081034 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 3 Jun 2012 19:34:56 GMT (envelope-from joelja@bogus.com)
Message-ID: <4FCBBC5D.7050805@bogus.com>
Date: Sun, 03 Jun 2012 12:34:53 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: maybe it's getting real
References: <4FCBA944.8060201@dcrocker.net>
In-Reply-To: <4FCBA944.8060201@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 03 Jun 2012 19:34:56 +0000 (UTC)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 19:35:04 -0000

On 6/3/12 11:13 , Dave Crocker wrote:
> Sitting in a pub in the Tiergarten metro station, in Berlin, today, I
> checked whether there were any open-access wireless points around.

http://www.msnbc.msn.com/id/37107291/ns/technology_and_science-security/

> There weren't.
> 
> But one of the nets had an SSID of IPV6...
> 
> d/


From eburger-l@standardstrack.com  Sun Jun  3 14:40:30 2012
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D809021F86C9 for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 14:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 UFb-v4qPaYpc for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 14:40:29 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id 3943221F86C8 for <ietf@ietf.org>; Sun,  3 Jun 2012 14:40:28 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:53225 helo=[192.168.15.135]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1SbIX9-0006NB-Qo; Sun, 03 Jun 2012 14:40:24 -0700
Subject: Re: Making the Tao a web page
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org>
Date: Sun, 3 Jun 2012 17:40:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDB80324-3064-4282-8502-A26C8BFB08AF@standardstrack.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 21:40:30 -0000

What we have now *is* sclerotic. See Russ' email above yours.

Can we PLEASE eat our own dog food? Wikipedia managed not to melt down =
when they decided NOT TO BUILD WALLS so there were no gates for the =
barbarians to crush.

Let's just turn on a wiki. Wiki's have a lot of technical measures to =
deal with problem edits as well as social measures to ensure quality. =
Unlike a protocol that needs one editor, I do not think we will run into =
interoperability problems by having an open Wiki. Yes, you and I and =
others can think of exactly four individuals who will try to crash the =
party. There are technical measures to keep them out without burdening =
one or even four people with keeping up the wiki.


On Jun 1, 2012, at 5:33 PM, Russ Housley wrote:
> I have a concern here.  When I did the AD review for this document, I =
was quite surprised how stale it had become.  For example, the document =
told people to send I-Ds to the Secretariat for posting instead of =
pointing to the online I-D submission tool.  If we put it in a wiki, =
there will be more people that can make update, but the publication =
process ensure that an end-to-end read takes place when an update =
published as an RFC.
>=20
> So, I am left with a few questions:
> - What is the similar forcing function if we use a wiki?
> - Will the number of people that can make updates eliminate the need =
for such a forcing function?
> - Who designates the editor-in-chief of the wiki?
>=20
> Russ


On May 31, 2012, at 7:50 PM, Paul Hoffman wrote:

> On May 31, 2012, at 4:30 PM, Nick Hilliard wrote:
>=20
>> On 01/06/2012 00:04, Paul Hoffman wrote:
>>> Works for me, other than it should not be a "wiki". It should have =
one
>>> editor who takes proposed changes from the community the same way we =
do
>>> it now. Not all suggestions from this community, even from =
individuals
>>> in the leadership, are ones that should appear in such a document.
>>=20
>> In practice, if this is to be a living document then it should be =
open for
>> inspection and poking rather than preserved in formaldehyde and put =
in a
>> display case, only to be opened occasionally when the curator decides =
the
>> glass needs some dusting.  That way leads to sclerosis.
>=20
> Thank you for that most colorful analogy. :-) What I proposed is =
exactly what we are doing now, except that the changes would appear on =
the web page instead of an Internet-Draft and, five years later, an RFC. =
Are you saying that the current system (which you have not commented on =
until now) is sclerotic (a word that I have wanted to use since I =
learned it in high school)?
>=20
>> Please put it on a wiki and put all changes through a lightweight =
review
>> system.  If someone makes a change which doesn't work, then it can be
>> reverted quickly and easily.  This approach is much more in line with =
the
>> ietf approach of informality / asking for forgiveness rather than
>> permission / rough consensus + running code / etc.
>=20
>=20
> In the IETF approach, only the authors of an Internet-Draft can change =
the contents of that draft. I hope you are not proposing a change to =
that as well.
>=20
> --Paul Hoffman
>=20


From john-ietf@jck.com  Sun Jun  3 15:46:59 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CCBD21F8753 for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 15:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.608
X-Spam-Level: 
X-Spam-Status: No, score=-101.608 tagged_above=-999 required=5 tests=[AWL=-0.868, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
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 vTi5cow2A8fr for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 15:46:58 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4D37B21F8752 for <ietf@ietf.org>; Sun,  3 Jun 2012 15:46:58 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SbJTW-000PKz-MW; Sun, 03 Jun 2012 18:40:42 -0400
Date: Sun, 03 Jun 2012 18:46:44 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eric Burger <eburger-l@standardstrack.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Making the Tao a web page
Message-ID: <EA537FE44DD2C0CD3FA67A3F@PST.JCK.COM>
In-Reply-To: <CDB80324-3064-4282-8502-A26C8BFB08AF@standardstrack.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <CDB80324-3064-4282-8502-A26C8BFB08AF@standardstrack.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 22:46:59 -0000

--On Sunday, June 03, 2012 17:40 -0400 Eric Burger
<eburger-l@standardstrack.com> wrote:

> What we have now *is* sclerotic. See Russ' email above yours.
> 
> Can we PLEASE eat our own dog food? Wikipedia managed not to
> melt down when they decided NOT TO BUILD WALLS so there were
> no gates for the barbarians to crush.
> 
> Let's just turn on a wiki. Wiki's have a lot of technical
> measures to deal with problem edits as well as social measures
> to ensure quality. Unlike a protocol that needs one editor, I
> do not think we will run into interoperability problems by
> having an open Wiki. Yes, you and I and others can think of
> exactly four individuals who will try to crash the party.
> There are technical measures to keep them out without
> burdening one or even four people with keeping up the wiki.

Eric,

FWIW, I think Paul is completely correct.  First of all, what is
sclerotic is RFC 4677.  Paul has been updating the I-D which is
much less of a problem.   Most of those "in the know" point
people to the I-D.  I think that having 4677 be the official
copy that some people consult as authoritative is a problem, but
it is another problem.

Those wiki technical measures depend on someone actively
watching for changes and having the time to step in.  I don't
think we can count on that, at least without a greater level of
effort that is required for an editor to receive comments and
integrate them.  I might change my mind if you, personally,
agreed to monitor the wiki in real time and alert the IETF list
to any possibly-questionable postings _and_ there was consensus
that those on the list wanted that additional traffic.

FWIW, I had a need on Friday to look up some details and
information that are fairly directly related to the IETF and its
relationships to some other bodies and decided to check the
Wikipedia pages that showed up in the search.  I'd give what I
found a score on accuracy and completeness of "joke" -- a few
identifiable falsehoods and a lot of convenient omissions (I
don't know or care whether those are the result of carelessness,
ignorance, or malice).  The most relevant of those pages wasn't
even flagged with "may be incomplete", "insufficient
references", or "may be biased", etc.  If you want to
demonstrate how well the Wiki system works, drop me a note
volunteering to fix the primary page involved and I'll tell you
what it is and, if you can't figure it out on your own in under
two minutes, where to get authoritative information.   In
principle, I could do it myself, but I just don't have time...
and that, and the fact that no one with the facts and time has
spotted those pages, is a large part of the problem with doing
something like the Tao by Wiki.

Also, perhaps because I have a more vivid (or paranoid)
imagination than you do, I can think of a lot more than four
individuals who would be inclined to wreck the party.  Some of
the individuals I can think of also have multiple personalities
or collections of sympathetic fellow-travelers (not just
multiple email addresses).  And, while I would hope they
wouldn't engage in such thing, if only because of the risk of
getting caught, I can think of a large and well-endowed
organization or three who might have incentives to put highly
distorted information onto an IETF Wiki that described how the
IETF worked, copy that material before it were taken down, and
then quote it in other sources.

Finally, as far as "our dogfood" is concerned, I just made a
careful search through the RFC index and a few other sources and
couldn't find an IETF Standards Track document describing the
Wiki technology and approach.  I couldn't even find an
Informational document.  So, unless I've missed something, this
particular food belongs to some other dog.  _Our_ dog food would
be to follow the precedent set with RFC 5000.  And I think that
is exactly what Paul and several others, including myself, have
been suggesting.

  best,
    john



From melinda.shore@gmail.com  Sun Jun  3 15:58:08 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6675821F86E5 for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 15:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 DC46W50qpPUB for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 15:58:07 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id DB87D21F84FE for <ietf@ietf.org>; Sun,  3 Jun 2012 15:58:07 -0700 (PDT)
Received: by dacx6 with SMTP id x6so4904429dac.31 for <ietf@ietf.org>; Sun, 03 Jun 2012 15:58:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=b4nAgRf5XACYjPt6VwobEzCLNACkRD4FBORHc86g6LY=; b=d3lCOLkL3LBlHf/g6pME1NmT1p8fEX59g+EMpN3mWdDBwxxxgZ2gq3KVyFfGVaUAgs 8BNfrRSQbato+E+2LQzinoUSF0fCG7HPvaYi/UUzYTUQdXs7T/Bai8u3QuUZeInpfiFb uvANvKQKWEVnl+Cj4Nugkq0h7lyEaZpH6/OTb97J218SPq/5JUdUj8OrqE/ECpkNLo9s mnr8FGeGeCShIrGYRqq5+7GBMKofNFYj50/Ma6aR/aEC/8foexss78HxGmXOqIV+XUNa iFaJJPa62P4pYVWYdrNEnsoyzZwc4t/OyEGOF5MGADwZpvd3K7e8IICJ06ttux3O2Euc ElHQ==
Received: by 10.68.136.68 with SMTP id py4mr33173739pbb.151.1338764287682; Sun, 03 Jun 2012 15:58:07 -0700 (PDT)
Received: from spandex.local (66-230-85-178-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.85.178]) by mx.google.com with ESMTPS id rs3sm11016323pbc.47.2012.06.03.15.58.06 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 03 Jun 2012 15:58:07 -0700 (PDT)
Message-ID: <4FCBEBFC.9010306@gmail.com>
Date: Sun, 03 Jun 2012 14:58:04 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Making the Tao a web page
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <CDB80324-3064-4282-8502-A26C8BFB08AF@standardstrack.com> <EA537FE44DD2C0CD3FA67A3F@PST.JCK.COM>
In-Reply-To: <EA537FE44DD2C0CD3FA67A3F@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 22:58:08 -0000

On 6/3/12 2:46 PM, John C Klensin wrote:
> Also, perhaps because I have a more vivid (or paranoid)
> imagination than you do, I can think of a lot more than four
> individuals who would be inclined to wreck the party.

This, I think, is the show-stopper.  Back when the internet started
to become popular a well-known open access advocate put his system,
which had a passwordless root account, online, and it was basically
vandalized immediately, then vandalized again, and again, and again,
until he finally surrendered.  I really prefer to keep things as
open as possible and I would love it if the Tao were a wiki article,
but transitioning to that model would essentially mean making a
commitment for the life of the page to keeping a very close eye on
it with a quick response to vandalism.

I also think that enough of our process is actually disputed to make
a living document hard to handle.  At least with an RFC we can say
"this is what we thought it was on a given date, with considerable
review prior to publication."

Melinda

From sm@resistor.net  Sun Jun  3 16:15:10 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C822021F875B for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 16:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 rJuaUHKoN9pY for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 16:15:07 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 57BFE21F8733 for <ietf@ietf.org>; Sun,  3 Jun 2012 16:15:07 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q53NF1gr000473 for <ietf@ietf.org>; Sun, 3 Jun 2012 16:15:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338765305; i=@resistor.net; bh=LWzyeaFLR7ptS7NHOp+zeI3VbSeGkEHUs1qeSTws5rs=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=pqxBfOXqDlZD4PiGCLD09wQsawfilKrFBJ+cKQWi17QQ7Vk0iIugiQheQ3CdJ/elZ 7hPC985ZuatqIC1jmn1iH4/Z+1f0X4nF5fr9GHQE8ZEOq+gIG83rZCRIv2UQZbMyg1 5aNwIGCr29McEKo/zOl5kPv38q+QGprwgMVyjjHs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1338765305; i=@resistor.net; bh=LWzyeaFLR7ptS7NHOp+zeI3VbSeGkEHUs1qeSTws5rs=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=LNfKNFBLoGLX4+aPUKBia8qXllyra246M8hjBEvTuLTTI4ToyPjyegvIqV1ZjptNC aI5iumUD6IWwdcsWtXjYIqt89h1wBUHarhtX5wsxMt0ma404bKleGV1xsduGFse+Oo Y9DpRPhc7RB8ReD7KXQbGOx75VVt5jzVbHuKVeQE=
Message-Id: <6.2.5.6.2.20120603145115.09cfc558@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 03 Jun 2012 15:36:31 -0700
To: IETF <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: Making the Tao a web page
In-Reply-To: <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <4FC8AFA9.1020200@inex.ie> <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 23:15:11 -0000

At 14:33 01-06-2012, Russ Housley wrote:
>it in a wiki, there will be more people that can make update, but 
>the publication process ensure that an end-to-end read takes place 
>when an update published as an RFC.

Seven individuals (approximate) submitted comments during the Last 
Call.  That's not much in terms of end-to-end read of the draft.

>So, I am left with a few questions:
>- What is the similar forcing function if we use a wiki?
>- Will the number of people that can make updates eliminate the need 
>for such a forcing function?
>- Who designates the editor-in-chief of the wiki?

HTTPbis has a good Wiki due to the efforts of two persons.  The rest 
of the IETF, excluding the IESG, do not believe that it is worth the 
effort updating a Wiki.  Instead of discussing the above questions it 
is easier to create an Wiki page and leave it to anyone with a tools 
login who cares to update it.

Regards,
-sm


From john-ietf@jck.com  Sun Jun  3 18:14:12 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 859D221F87ED for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 18:14:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level: 
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 N6NeA274BAag for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 18:14:12 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E49C521F87EA for <ietf@ietf.org>; Sun,  3 Jun 2012 18:14:11 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SbLm7-000PU1-JL; Sun, 03 Jun 2012 21:08:03 -0400
Date: Sun, 03 Jun 2012 21:14:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Making the Tao a web page
Message-ID: <71AE4608EF35D8250EB7508E@PST.JCK.COM>
In-Reply-To: <4FCBEBFC.9010306@gmail.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <CDB80324-3064-4282-8502-A26C8BFB08AF@standardstrack.com> <EA537FE44DD2C0CD3FA67A3F@PST.JCK.COM> <4FCBEBFC.9010306@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 01:14:12 -0000

--On Sunday, June 03, 2012 14:58 -0800 Melinda Shore
<melinda.shore@gmail.com> wrote:

> On 6/3/12 2:46 PM, John C Klensin wrote:
>> Also, perhaps because I have a more vivid (or paranoid)
>> imagination than you do, I can think of a lot more than four
>> individuals who would be inclined to wreck the party.
> 
> This, I think, is the show-stopper.  Back when the internet
> started
> to become popular a well-known open access advocate put his
> system,
> which had a passwordless root account, online, and it was
> basically
> vandalized immediately, then vandalized again, and again, and
> again,
> until he finally surrendered.  I really prefer to keep things
> as
> open as possible and I would love it if the Tao were a wiki
> article,
> but transitioning to that model would essentially mean making a
> commitment for the life of the page to keeping a very close
> eye on
> it with a quick response to vandalism.

Indeed.

> I also think that enough of our process is actually disputed
> to make
> a living document hard to handle.  At least with an RFC we can
> say
> "this is what we thought it was on a given date, with
> considerable review prior to publication."

Well, as long as the document is informational and an overview,
I think that can be accomplished as easily with a web page, an
editor who can be trusted to exercise a certain amount of good
sense (and whose intentions are trusted) and a process for
forcing a review if needed.   The thing that bothers me about
trying to do this by RFC is that the entire community then
wastes a huge amount of time debating the choice and style of
words and relatively minor details, after which everyone runs
out of energy to make further changes for years (other than
posting I-Ds on which there are no real controls, even an appeal
process (not that I'd expect Paul to ignore input)).   If we go
the web page and editor route, expect revisions only when real
problems are identified and otherwise do a review every year or
so, I think we can get a pretty good balance between the
slowness of the RFC-and-community-consensus process and the
difficulties of the Wiki one.

best,
   john






From john-ietf@jck.com  Sun Jun  3 18:34:40 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB03C21F87D4 for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 18:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.497
X-Spam-Level: 
X-Spam-Status: No, score=-102.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4ysPxY2D+dae for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 18:34:40 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 603EE21F87D1 for <ietf@ietf.org>; Sun,  3 Jun 2012 18:34:40 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SbM5v-000PVm-3b; Sun, 03 Jun 2012 21:28:31 -0400
Date: Sun, 03 Jun 2012 21:34:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>, IETF <ietf@ietf.org>
Subject: Re: Making the Tao a web page
Message-ID: <35398D42C139212863F6D771@PST.JCK.COM>
In-Reply-To: <6.2.5.6.2.20120603145115.09cfc558@resistor.net>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <4FC8AFA9.1020200@inex.ie> <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com> <6.2.5.6.2.20120603145115.09cfc558@resistor.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 01:34:41 -0000

--On Sunday, June 03, 2012 15:36 -0700 SM <sm@resistor.net>
wrote:

> At 14:33 01-06-2012, Russ Housley wrote:
>> it in a wiki, there will be more people that can make update,
>> but  the publication process ensure that an end-to-end read
>> takes place  when an update published as an RFC.
> 
> Seven individuals (approximate) submitted comments during the
> Last Call.  That's not much in terms of end-to-end read of the
> draft.

Subramanian,

I don't think that is a fair comparison.  First of all, the Last
Call spawned the whole thread about colloquial language.  I
don't have any way to know how many of those who participated in
that thread read all the way through the document and even less
way to guess how many people were enough turned off by it to
lose interest in the Last Call, maybe after having read the
document.  Second and more important, my suggestion that we go
in the direction of a web page or wiki spawned a separate thread
that is more about the philosophy of how to handle the document
rather than about the detailed content of the document itself.
Again, I have no idea how many people other than myself looked
through the document, decided that "publish as RFC?" was the
wrong question, and as the result of that decision, concluded
that my time was better spent on medium and editorial process
than on reporting specific document comments.  So you don't know
to what extent I, or anyone else in the "making it a web page"
threads read the document through either.

My guess is that more people have volunteered to help with the
web page approach on an ongoing basis than have read the
document carefully in the last week or so.  I further guess that
"on an ongoing basis" will be better for the document than
getting a new snapshot out as an RFC and seeing how long it
takes to get stale and how long after that it takes the
community to notice.  But those are just guesses and my opinion.
YMMD.

>...
> HTTPbis has a good Wiki due to the efforts of two persons.
> The rest of the IETF, excluding the IESG, do not believe that
> it is worth the effort updating a Wiki.  Instead of discussing
> the above questions it is easier to create an Wiki page and
> leave it to anyone with a tools login who cares to update it.

See my responses to Eric and Melinda.

   john




From lixia@cs.ucla.edu  Sun Jun  3 20:49:20 2012
Return-Path: <lixia@cs.ucla.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D84C221F881C for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 20:49:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 t-pLaApXfU3r for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 20:49:20 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 6AFD321F87A9 for <ietf@ietf.org>; Sun,  3 Jun 2012 20:49:20 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 1E693A60003; Sun,  3 Jun 2012 20:49:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zdp709f6u3gu; Sun,  3 Jun 2012 20:49:19 -0700 (PDT)
Received: from [192.168.6.75] (ip-64-134-67-225.public.wayport.net [64.134.67.225]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 7086339E8006; Sun,  3 Jun 2012 20:49:19 -0700 (PDT)
Subject: Re: Making the Tao a web page
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <35398D42C139212863F6D771@PST.JCK.COM>
Date: Sun, 3 Jun 2012 20:49:19 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <4D72EB63-90AB-4A01-989C-6C40B2453619@cs.ucla.edu>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <4FC8AFA9.1020200@inex.ie> <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com> <6.2.5.6.2.20120603145115.09cfc558@resistor.net> <35398D42C139212863F6D771@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1278)
Cc: SM <sm@resistor.net>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 03:49:20 -0000

On Jun 3, 2012, at 6:34 PM, John C Klensin wrote:

> ... I further guess that
> "on an ongoing basis" will be better for the document than
> getting a new snapshot out as an RFC and seeing how long it
> takes to get stale and how long after that it takes the
> community to notice. ...

I second the above statement
(my apology to John for quoting this single sentence out of his whole msg)

Lixia


From sm@resistor.net  Sun Jun  3 22:49:24 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D93B21F8873 for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 22:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.473
X-Spam-Level: 
X-Spam-Status: No, score=-102.473 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 7EdubJOTbpnL for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 22:49:22 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B8EDC21F8869 for <ietf@ietf.org>; Sun,  3 Jun 2012 22:49:15 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q545n9l7010166; Sun, 3 Jun 2012 22:49:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338788953; i=@resistor.net; bh=11a4NCqLyLPtCfnAEvUWmkUH/C+qt0H+XlSf409JuNg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KygaP0U4bttwFEOxz874SNKwj1vEgF/qG0NfgynwOD+9xX4E7UcBGBZvp5x3r+Ryg MLY8QtkCs+4qpQG9//NZffH7X2GQe4xSbSDP2hSRXWk4ZHVvdJSCQ7yEg6Cag5QZZO slHt96QDhm261z7tmgU4bVcF3IfMR+v8AoSZTuFs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1338788953; i=@resistor.net; bh=11a4NCqLyLPtCfnAEvUWmkUH/C+qt0H+XlSf409JuNg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2RLoGpCVpQe6P3aS8fbAQgbCPEWDo+ntBUcYIyDywWv18tdu5HddRIictsP+kV/Hm Jll06Hp6uzOrfi3PetLqrxu6rC5YXHMw+UivKVHyLHIlnIgY6sIUQ7JgOSrcSvQzA9 SBmc9DHKFODsu80MnYUQsxBNozOVmS6SHcPG9o2s=
Message-Id: <6.2.5.6.2.20120603195759.0a1a9528@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 03 Jun 2012 22:18:54 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Making the Tao a web page
In-Reply-To: <35398D42C139212863F6D771@PST.JCK.COM>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <4FC8AFA9.1020200@inex.ie> <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com> <6.2.5.6.2.20120603145115.09cfc558@resistor.net> <35398D42C139212863F6D771@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 05:49:24 -0000

Hi John,
At 18:34 03-06-2012, John C Klensin wrote:
>I don't think that is a fair comparison.  First of all, the Last
>Call spawned the whole thread about colloquial language.  I
>don't have any way to know how many of those who participated in
>that thread read all the way through the document and even less
>way to guess how many people were enough turned off by it to
>lose interest in the Last Call, maybe after having read the
>document.  Second and more important, my suggestion that we go

Fair enough.  My guess was that the Last Call was not really a Last Call. :-)

>in the direction of a web page or wiki spawned a separate thread
>that is more about the philosophy of how to handle the document
>rather than about the detailed content of the document itself.
>Again, I have no idea how many people other than myself looked
>through the document, decided that "publish as RFC?" was the
>wrong question, and as the result of that decision, concluded
>that my time was better spent on medium and editorial process
>than on reporting specific document comments.  So you don't know
>to what extent I, or anyone else in the "making it a web page"
>threads read the document through either.

Yes.

At 18:14 03-06-2012, John C Klensin wrote:
>Well, as long as the document is informational and an overview,
>I think that can be accomplished as easily with a web page, an
>editor who can be trusted to exercise a certain amount of good
>sense (and whose intentions are trusted) and a process for
>forcing a review if needed.   The thing that bothers me about
>trying to do this by RFC is that the entire community then
>wastes a huge amount of time debating the choice and style of
>words and relatively minor details, after which everyone runs
>out of energy to make further changes for years (other than
>posting I-Ds on which there are no real controls, even an appeal
>process (not that I'd expect Paul to ignore input)).   If we go
>the web page and editor route, expect revisions only when real
>problems are identified and otherwise do a review every year or
>so, I think we can get a pretty good balance between the
>slowness of the RFC-and-community-consensus process and the
>difficulties of the Wiki one.

In 1994 it was mentioned that due to the nature of the document it 
can become outdated quite quickly.  The web page approach was 
recommended.  The EDU Team ( 
http://wiki.tools.ietf.org/group/edu/wiki/EduCharter ) could be an 
alternative to take on the task.

Regards,
-sm




From dhc@dcrocker.net  Sun Jun  3 23:03:01 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9FC921F8547 for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 23:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level: 
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 31X05xNQi8zt for <ietf@ietfa.amsl.com>; Sun,  3 Jun 2012 23:03:01 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1B84021F8542 for <ietf@ietf.org>; Sun,  3 Jun 2012 23:03:01 -0700 (PDT)
Received: from [192.168.2.101] (g231207152.adsl.alicedsl.de [92.231.207.152]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q5462wFP007236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 3 Jun 2012 23:02:59 -0700
Message-ID: <4FCC4F8F.1060800@dcrocker.net>
Date: Mon, 04 Jun 2012 08:02:55 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: Making the Tao a web page
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <4FC8AFA9.1020200@inex.ie> <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com> <6.2.5.6.2.20120603145115.09cfc558@resistor.net>
In-Reply-To: <6.2.5.6.2.20120603145115.09cfc558@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 03 Jun 2012 23:03:00 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 06:03:01 -0000

On 6/4/2012 12:36 AM, SM wrote:
> At 14:33 01-06-2012, Russ Housley wrote:
>> So, I am left with a few questions:
>> - What is the similar forcing function if we use a wiki?
>> - Will the number of people that can make updates eliminate the need
>> for such a forcing function?
>> - Who designates the editor-in-chief of the wiki?
...
>   ...  Instead of discussing the above questions it is easier
> to create an Wiki page and leave it to anyone with a tools login who
> cares to update it.


In effect, the wiki construct becomes a form of incrementally-updatable 
internet draft.  For documents involving procedures rather than 
products, this well might be a better working base than I-Ds...

But with the I-D model superimposed.

That is, perhaps what makes this workable is imposing an editor role 
onto the wiki and assign responsibility for monitoring changes to the 
editors?  (It might even be worth integrating it into the rest of the 
I-D administration environment?)

Note that this still leaves a place for published snapshots as RFCs.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From rbarnes@bbn.com  Mon Jun  4 05:33:43 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 484D121F8724; Mon,  4 Jun 2012 05:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 UoveCkfK1DfS; Mon,  4 Jun 2012 05:33:41 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id B089321F871C; Mon,  4 Jun 2012 05:33:41 -0700 (PDT)
Received: from ros-dhcp192-1-51-6.bbn.com ([192.1.51.6]:59859) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1SbWT4-0003ZQ-Qa; Mon, 04 Jun 2012 08:33:06 -0400
From: Richard L. Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART Telechat review of draft-ietf-appsawg-about-uri-scheme-05
Date: Mon, 4 Jun 2012 08:33:40 -0400
Message-Id: <196B9066-2934-443D-B642-997BDF57948E@bbn.com>
To: ietf@ietf.org, IESG <iesg@ietf.org>, gen-art@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 12:33:43 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-appsawg-about-uri-scheme-05
Reviewer: Richard Barnes
Review Date: Jun-04-2012
IETF LC End Date: Not known
IESG Telechat date: Jun-07-2012

Summary: Almost ready, couple of questions

MAJOR:=20

*.
I wonder how useful this document is, given that the use of "about:" =
URIs is currently very inconsistent across browsers. (See, for example, =
<http://en.wikipedia.org/wiki/About_URI_scheme>)  Some browsers also use =
alternative URI schemes for essentially the same function ("opera:", =
"chrome:").  Has there been input from the browser vendor community on =
this document? =20


4.
The document correctly notes that "about:" URIs sometimes point to =
sensitive data, and that browsers need to protect them.  However, the =
document fails to specify what the threats are and how to mitigate them. =
 It seems to me that the major risk is cross-site scripting, in the =
sense that a remote web page might include an "about:" URI (e.g., via an =
XMLHttpRequest) in order to access sensitive data.  At a high level, =
then, the mitigation would be to ensure that such URIs are accessible =
only as a result of direct user action (e.g., typing in a URI) or =
trusted browser code (e.g., extensions).


From abdussalambaryun@gmail.com  Mon Jun  4 00:17:52 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD3C311E8072; Mon,  4 Jun 2012 00:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.18
X-Spam-Level: 
X-Spam-Status: No, score=-3.18 tagged_above=-999 required=5 tests=[AWL=-0.181,  BAYES_00=-2.599, J_CHICKENPOX_12=0.6, 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 j2-Sab99fdjJ; Mon,  4 Jun 2012 00:17:51 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0CF8F21F85A4; Mon,  4 Jun 2012 00:17:50 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2587694vbb.31 for <multiple recipients>; Mon, 04 Jun 2012 00:17:50 -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:content-transfer-encoding; bh=8aqhCUAkQkiahAlngyxsmMnxYd3VH1Sp2KqZgtlqKw8=; b=CXz0+2OEJz39Yypk1b/L4wjbCvSMKGVrjxvMCiKLB9f5IIoS+quc8OhE1J9dRraycD 6gUngRBNrzPRcJnPH8W4qmWSyDaxVQUUvh5q3oHusfKXErxq8vlSsKsH+wAWBU1YjkIZ hH31vI565Z43fSyy5Q4ocGgUey2WPFlSTuhqLN/8WXuBBbaYy5TDoPI+jO/Qfl/U+CUb TpfPgmFzDQ043Dg2pLkvRYBHoiNq9+bK1/bSFr90jnRpPlxayAXv/NxXG2pZaEpOoss9 NC7uvmbcF4rBQjs/NMzjdhM1n7OBwZG9cYuITVn0hjHWQsu5KBkze4n2eFUk/9eF+Kx2 Zasg==
MIME-Version: 1.0
Received: by 10.52.36.116 with SMTP id p20mr9688983vdj.129.1338794270279; Mon, 04 Jun 2012 00:17:50 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Mon, 4 Jun 2012 00:17:50 -0700 (PDT)
In-Reply-To: <CBF0BEC2.168B4%d.sturek@att.net>
References: <4FCB0261.9020405@computer.org> <CBF0BEC2.168B4%d.sturek@att.net>
Date: Mon, 4 Jun 2012 09:17:50 +0200
Message-ID: <CADnDZ889mGxHsCcXsr=SgJHqzHKZ8t9AKCpgsUETYNm9vJuW6g@mail.gmail.com>
Subject: Re: [manet] Defining subnet models used by our protocols
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Don Sturek <d.sturek@att.net>, manet <manet@ietf.org>, autoconf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 04 Jun 2012 08:23:19 -0700
Cc: "robert.g.cole" <robert.g.cole@us.army.mil>, ietf <ietf@ietf.org>, "Charles E. Perkins" <charliep@computer.org>, "Emmanuel.Baccelli" <Emmanuel.Baccelli@inria.fr>, Ulrich Herberg <ulrich@herberg.name>, Stan Ratliff <sratliff@cisco.com>, "ian.chakeres" <ian.chakeres@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 07:17:52 -0000

Hi Don, and All,

I would like to know your opinion about why we don't define subnets for MAN=
ET?

On 6/3/12, Don Sturek <d.sturek@att.net> wrote:
> +1
>
> On 6/2/12 11:21 PM, "Charles E. Perkins" <charliep@computer.org> wrote:

Could we discuss why we don't define subnets models? I don't
understand adding (+1). I hope the chair does not ask me to close this
thread too :)

The ad hoc autoconfig was proposed in 2005 and proposed-ended in 2011
so living for about 6 years only. What was the reason for the proposed
close of it? please read the DA Jari's reasons below.

IMO it because it had low/no useful discussions and only produced one
RFC which is RFC5889, why only one? what happend within 6 years?  IMO
any WG should have more discussions, discussions are mandatory
activity for WG. Not discussing issues is like ignoring the value
input to group progress. Healthy discussions are more important than
producing more documents produced, because discussions are really the
source of correct documents (don't mean it has to be perfect, but
should not be misleading). WGs should be compared in terms of the
amount of discussions not in amount of documents forwarded/submitted.

According to Chakeres and Maker (2006) [1] quoated below:

[The autoconf WG is chartered to initially develop
two documents. The first document is a document
defining the MANET architecture and how MANET
relates to IP networks and the Internet. The second
document is to define the terminology, problem statement
and goals for autoconf. These autoconf documents
will be discussed on the autoconf mailing list.]

That WG did not produce the definition of MANET architecture. Which I
think is related to the subnet-model definition importance for MANET.
So i understand the authors see the importance of defining something
for MANET in 2006. Now, Do we have a network architecture definition
of MANET in one RFC?

> On 6/2/12 11:21 PM, "Charles E. Perkins" <charliep@computer.org> wrote:
>>Hello folks,
>>
>>I would be opposed to requiring the subnet model as a mandatory
>>component of any current [manet] working group charter item.
>>
>>We have had at least ten years of experience showing that requiring
>>subnets can derail practically any wireless network discussion within
>>the sphere of applicability of manet protocols.  The reasons are many
>>and varied -- and, I must admit, really very interesting.
>>
>>It was the death of another working group which really should have
>>been allowed to go forward except for disagreements about certain
>>subnet-related constructs.  Let's not consign ourselves to the same
>>fate.

In future the death of the WG will be because they don't discuss
things on the list, or don't have what to discuss, please read the
reasons mentioned by Jari Arkko below. IMO for the future, some day
any WGs possibly will close and other days new WGs comes.

>>
>>Regards,
>>Charlie P.

References:
[1] Chakers, I., and Maker, J., 'Mobile Ad Hoc Networking and the
IETF', Mobile Computing and communication review, volume 1, Number 2,
2006.

Best regards

Abdussalam Baryun
University of Glamorgan, UK
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
To: "autoconf at ietf.org" <autoconf at ietf.org>
Subject: [Autoconf] closing the working group?
From: Jari Arkko <jari.arkko at piuha.net>
Date: Tue, 29 Mar 2011 08:48:47 +0200

---------------------------------------------------------------------------=
-----
I have looked at the discussions on the list (or lack thereof). I also
cannot see too many internet drafts on the topics belonging to the
group's charter. I am very happy with the RFC that has been produced
by the working group, but we also seem to have some actual protocol
work happening elsewhere (e.g., in the context of the ROLL WG).

I discussed this matter with the chairs and my co-AD, and we are
wondering if it would be time to close the working group. I do know
that there is at least one implementation team that is still in the
process of describing their DHCP-based solution, maybe there are
similar efforts on the distributed solution space. My proposal is that
we close the working group and I'be VERY happy to AD sponsor all such
solutions to Experimental RFCs as soon as we have those proposals in
some reasonable shape.
Thoughts?

Jari
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
To: IETF-Announce at ietf.org
Subject: WG Review: Ad Hoc Network configuration (autoconf)
From: The IESG <iesg-secretary at ietf.org>
Date: Wed, 27 Jul 2005 14:28:49 -0400
Cc: manetautoconf at ml.free.fr
List-help: <mailto:ietf-announce-request@ietf.org?subject=3Dhelp>
List-id: ietf-announce.ietf.org
List-post: <mailto:ietf-announce@ietf.org>
List-subscribe:
<https://www1.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request@ietf.org?subject=3Dsubscribe>
List-unsubscribe:
<https://www1.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request@ietf.org?subject=3Dunsubscribe>
Reply-to: iesg at ietf.org
Sender: ietf-announce-bounces at ietf.org

---------------------------------------------------------------------------=
-----
A new IETF working group has been proposed in the Internet Area. The
IESG has not
made any determination as yet. The following draft charter was
submitted, and is
provided for informational purposes only. Please send your comments to the =
IESG
mailing list (iesg at ietf.org) by August 3rd.

+++++++++++++

Ad Hoc Network configuration (autoconf)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Current Status: Proposed Working Group

Chairs:
TBD

Internet Area Director(s):
Mark Townsley <townsley at cisco.com>
Margaret Wasserman <margaret at thingmagic.com>

Internet Area Advisor:
Margaret Wasserman <margaret at thingmagic.com>

Mailing Lists:
General Discussion: manetautoconf at ml.free.fr
To Subscribe: manetautoconf-request at ml.free.fr

Description of the WG:

In order to communicate among themselves, ad hoc nodes (refer to RFC
2501) may need to configure their network interface(s) with local
addresses that are valid within an ad hoc network. Ad hoc nodes may
also need to configure globally routable addresses, in order to
communicate with devices on the Internet.

Ad hoc networks present several new challenges. Unlike in traditional
IP networks, each ad hoc node, besides being a traffic end-point,
should be capable of forwarding traffic destined for other hosts.
Additionally, nodes constituting an ad-hoc network do not share access
to a single multicast-capable link for signaling. Many protocol
specifications used in traditional IP networks e.g. RFCs 2462, 2463
etc. do, however, assume that subnet-local signals (e.g. link-local
multicast signal) are received by each of the hosts on the particular
subnet without being forwarded by the routers defining the subnet
boundary.

The main purpose of the AUTOCONF WG is to standardize mechanisms to be
used by ad hoc nodes for configuring unique local and/or globally
routable IPv6 addresses. The ad hoc nodes under consideration are
expected to support multi-hop communication by running a MANET routing
protocol, e.g. those developed by the IETF MANET WG. However, this may
or may not mean that an AUTOCONF mechanism will be dependent on any
specific MANET routing protocol. With this in mind, the goals of
AUTOCONF WG are to:

- Produce a "terminology and problem statement" document, defining the
problem statement and goals for AUTOCONF.

- Develop an IPv6 stateless autoconfiguration mechanism to be used by
ad hoc nodes for configuring unique local addresses as well as, in
cases where Internet connectivity exists, globally routable unique
addresses.

- Develop a stateful address autoconfiguration mechanism to be used by
ad hoc nodes for configuring globally routable unique addresses, if an
address providing entity such as DHCPv6 server is available.

- Develop a mechanism to promote configured address uniqueness in the
situation where different ad hoc networks merge.

Issues and requirements related to prefix and/or address providing
entities, such as an Internet gateway, will be addressed within the
group to the extent that they are directly related to the AUTOCONF
mechanisms. Security concerns related to AUTOCONF mechanisms will also
be discussed within the group.

The working group will reuse existing specifications whenever
reasonable and possible.

Goals and Milestones:

Oct 05 : Submit "terminology and problem statement" document for WG
review
Oct 05: Submit initial I-D(s) of candidate proposed AUTOCONF mechanisms
and design frameworks
Feb 06: Submit "terminology and problem statement" document to IESG for
publication as an informational RFC
Apr 06: Submit initial I-D of "stateless autoconfiguration mechanism"
for WG review
Apr 06: Submit initial I-D of "stateful autoconfiguration mechanism"
for WG review
Apr 06: Submit initial -ID of "configured address uniqueness
maintenance" for WG review
Aug 06: Revise WG documents and review
Dec 06 Revise documents based upon implementation experience
Apr 07: Submit "stateless autoconfiguration mechanism" specification
and supporting documentation to IESG for publications as Proposed
Standard
Apr 07: Submit "stateful autoconfiguration mechanism" specification and
supporting documentation to IESG for publications as Proposed Standard
Apr 07: Submit "configured address uniqueness maintenance"
specification and supporting documentation to IESG for publications as
Proposed Standard
Oct 07: Close or recharter the WG


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce





=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
>>
>>
>>
>>On 6/2/2012 1:12 AM, Abdussalam Baryun wrote:
>>> Hi All
>>>
>>> I want to discuss this subnet definition issue that was raised in the
>>> 82 meeting, could we discuss about it please. Will we need to put it
>>> in a draft or include it in our active draft working in progress,
>>> please advise,
>>>
>>> Abdussalam Baryun,
>>> University of Glamorgan, UK
>>> ++++++++++++++++++++++++++++++
>>>
>>> In WG 82 meeting it was mentioned (Bob Cole and Teco discussions):
>>> BC>  that subnet-models are not defined But in DLEP it looks at two
>>> subnet-models (different models; e.g. radio subnet-models,
>>> sat-subnet-models). We are defining IP over a subnet, but the subnet
>>> is not defined. Then we don=B9t know how to define control protocols,
>>> data-packet-formats, and managements-models without having a subnet
>>> model in mind.
>>> TB>  In sat-comms the up-link and down-link can be very different. So
>>> for different nodes on same carrier can be different data rates, SNR,
>>> etc. so it is important that DLEP include the link metrics, even if it
>>> is a full connected subnet.
>>> BC>  the subnet depends on the link of the subnet-underlying model,
>>> The semantics of link up and down are determined by the underlying.
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>> ********************************************************************
>>> This email and any attachments are confidential to the intended
>>> recipient and may also be privileged. If you are not the intended
>>> recipient please delete it from your system and notify the sender.
>>> You should not copy it or use it for any purpose nor disclose or
>>> distribute its contents to any other person.
>>> ********************************************************************
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>>
>>>
>>
>>
>>--
>>Regards,
>>Charlie P.
>>
>>_______________________________________________
>>manet mailing list
>>manet@ietf.org
>>https://www.ietf.org/mailman/listinfo/manet
>
>
>

From sm@elandsys.com  Sun Jun  3 03:36:28 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53CB621F864E; Sun,  3 Jun 2012 03:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.48
X-Spam-Level: 
X-Spam-Status: No, score=-102.48 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
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 Lq7Woxy0P-zn; Sun,  3 Jun 2012 03:36:26 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8760021F864C; Sun,  3 Jun 2012 03:36:26 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.232.102]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q53AaABq014765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 3 Jun 2012 03:36:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338719782; i=@elandsys.com; bh=y9PVa/WtjvsS3hSnTEaXN+g8/pjUlEFRkSATR57t5T4=; h=Date:To:From:Subject:Cc; b=l0AV58x7rFeX5jP+R4hr8C5DJXK8iV7Ji7jwop+OTvONezJB0fzEr30NvBtV6wlge TOPWo01aqsf20xPmscuwNMfARchmdlpAmQGvLd617ZX3OWCzsKRSjyD5Q+3NWGAbh1 pXtnqn8Dkp8iwiwegYK0NzW2h/P8SdVxowElMxdE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1338719782; i=@elandsys.com; bh=y9PVa/WtjvsS3hSnTEaXN+g8/pjUlEFRkSATR57t5T4=; h=Date:To:From:Subject:Cc; b=V5Y2kbRlB3w1jrLWmFAJ7sWm6S7aHeemcjqcd5uz0pfGB8cbkmvKoSX8+bVWVFEau Zi1bhBcFiYdUFIIvjXpxbiM6+jSg23F5gsaydbpKtVUmyfHIGey9TBjvfptIiN3ABO vsm8d9wfGPF7isQJ1CvpeVj1iZc7jatF1DMaTPQ0=
Message-Id: <6.2.5.6.2.20120603010308.0be0d8e8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 03 Jun 2012 03:18:10 -0700
To: apps-discuss@ietf.org, draft-vegoda-cotton-rfc5735bis.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: APPSDIR review of draft-vegoda-cotton-rfc5735bis-02
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Mon, 04 Jun 2012 08:23:35 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 10:36:28 -0000

I have been selected as the Applications Area Directorate reviewer 
for this draft (for background on APPSDIR, please see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft.  The review 
is not copied to the IESG as the Last Call has not been announced yet.

Document: draft-vegoda-cotton-rfc5735bis-02
Title: Special Use IPv4 Addresses
Reviewer: S. Moonesamy
Review Date: June 3, 2012

Summary: This document is almost ready for publication as a BCP.

The draft describes the global and other specialized IPv4 address 
blocks that have been assigned by IANA.  It is an update of RFC 5735 
to include the Shared IPv4 address space which was assigned about the 
publication of RFC 5735.  The proposal does not have any impact on 
Application-related protocols.

Major issues: None

Minor issues:

In Section 1:

   "Section 4 of this document describes that assignment process."

Section 4 contains a summary table without any assignment process 
description.  Where is the assignment process described?

In Section 5:

   "The domain name and IP address spaces involve policy issues (in
    addition to technical issues) so that the requirements of [RFC2860]
    do not apply generally to those spaces."

The wording is different from what is in RFC 2860.

   "Immediately before the RFC is published, the IANA will, in
    consultation with the Regional Internet Registries, make the
    necessary assignment and notify the RFC Editor of the particulars
    for inclusion in the RFC as published."

There is no mention of "Regional Internet Registries" in RFC 2860.

I suggest dropping Section 5 as according to Abstract this draft is 
about documenting Special Use IPv4 addresses.

In Section 7:

   "Security policy SHOULD NOT blindly filter all of these address spaces
    without due consideration, and network operators are encouraged to
    review this document, and references contained therein, and determine
    what security policies should be associated with each of these address
    blocks within their specific operating environments."

The recommendation is not clear.  The recommendation seems more 
appropriate for network operators instead of "Security policy" as 
they have the awareness to make such decisions.

Given the recommendation about due consideration and reviewing all 
the references, these references would have to be normative.  It is 
easier to remove the RFC 2119 boilerplate and use a "should not" to 
reduce the amount of required reading.

Nits:

Why does this draft update RFC 6441?

Regards,
S. Moonesamy


From abdussalambaryun@gmail.com  Mon Jun  4 00:44:26 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EDF121F877B; Mon,  4 Jun 2012 00:44:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.477
X-Spam-Level: 
X-Spam-Status: No, score=-3.477 tagged_above=-999 required=5 tests=[AWL=0.122,  BAYES_00=-2.599, 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 I5cCIMSPKCLI; Mon,  4 Jun 2012 00:44:26 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E096D21F8779; Mon,  4 Jun 2012 00:44:25 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2603236vcq.31 for <multiple recipients>; Mon, 04 Jun 2012 00:44:25 -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 :content-type; bh=k4fJPrs3Rgmz1tj68QgZhVI8DEpI9ty4U1/OKs7MoaU=; b=E9rQtSHC30VQNaYPDeTJFJ5C86o7YL9roaW3UCg7f9aYWJ7HPYQ4epUx9xFQGjsXcZ FAmKEH1WIr4hsf9VS7IBzducWqMAZsiZSBWNH9/H6NI6u+SIOOU12YZilE6ZO3EDI1g1 SLr5d0w642eN3PUG/G0cnUWgyAEZTPteyC0x3bvPAWIGTDYuHVOXsrIHcVLO6qbgSba/ vVS6KDokE9vLbxOcj++wohpy5xKAJYdfWBPFTb+shRK0mdCKN3/tdcGbzEYErqnIqZZc Y9eEAfj4mpCmjIVOc0+zRlKQy/eP6wk3i+gtH8sOAowGYUwvAfhah66vEeTgY+uRvi5I QJ+A==
MIME-Version: 1.0
Received: by 10.220.150.134 with SMTP id y6mr11275185vcv.43.1338795865091; Mon, 04 Jun 2012 00:44:25 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Mon, 4 Jun 2012 00:44:25 -0700 (PDT)
In-Reply-To: <CADnDZ8-52f3Tzu4T3gjfJirmPhAGY+4uBBN0jxV03wcY6E5YVQ@mail.gmail.com>
References: <CADnDZ8-52f3Tzu4T3gjfJirmPhAGY+4uBBN0jxV03wcY6E5YVQ@mail.gmail.com>
Date: Mon, 4 Jun 2012 09:44:25 +0200
Message-ID: <CADnDZ88OjX0NRyE0-fO7ErXMR6BZoEsM-+gnZ1_Qe+dor+7cMw@mail.gmail.com>
Subject: draft-ietf-roll-terminology-06.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: JP Vasseur <jpv@cisco.com>, 6lowpan <6lowpan@ietf.org>, ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Mon, 04 Jun 2012 08:23:35 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 07:44:26 -0000

Hi Vasseur,

I want to ask about the draft of ROLL terminology, when will it be
re-activated? because expired, and if it is completed should we make
it go forward, or is it better to wait for other drafts to come in,
not sure, please advise, thanking you,

Abdussalam Baryun,
University of Glamorgan, UK
+++++++++++++++++++++++++++++++++++++++++++++++++++

From abdussalambaryun@gmail.com  Mon Jun  4 02:30:48 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2B421F870E for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 02:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.308
X-Spam-Level: 
X-Spam-Status: No, score=-3.308 tagged_above=-999 required=5 tests=[AWL=-0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_UNSUB30=0.351]
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 mLigYXTbFmyV for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 02:30:47 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC3921F847D for <ietf@ietf.org>; Mon,  4 Jun 2012 02:30:47 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2641653vbb.31 for <ietf@ietf.org>; Mon, 04 Jun 2012 02:30:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=R7Fo2XYttFM9j8mLhWcHAxy70MJioCH4K0gzdhDrUx0=; b=RFxeT/+6tqx2W38o9yku9k09paDEafch3oDMQlhEHW6zw6j3W8jkNgZbnLTlSCgxir jA27BhOTLHVLMdgZ4GMOygOfFYi0owz+hjEVP6aSsluo7WiPX+YqdVxkPQX4b1kQhB1/ 8rA5jPXXgdvoypcxgiuiLkAz39Defsn42ZDhQ9Gtcyl6YwtRxeo+DHZHFqG1M2D5B4cS S+xZCesGEYqdlKwypybhwH2utqKs/MV+V7Yy0S5RJ2eF1JJwy5seu45PxwVNemD8yDyZ 2WOKETZ7oGbRvMAD0pKWBB/unHzDDKqgRb1j82zbrLNxj3duDf82p26HCFapMdAu9kg3 mOyQ==
MIME-Version: 1.0
Received: by 10.52.94.36 with SMTP id cz4mr10273911vdb.10.1338802247158; Mon, 04 Jun 2012 02:30:47 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Mon, 4 Jun 2012 02:30:46 -0700 (PDT)
Date: Mon, 4 Jun 2012 11:30:46 +0200
Message-ID: <CADnDZ89sKYO5Ao7tKZ=V=7z4dJA1D8fb8Vbo5JFJpuQKajCfDw@mail.gmail.com>
Subject: Re: Making the Tao a web page
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: paul.hoffman@vpnc.org, ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Mon, 04 Jun 2012 08:23:35 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 09:30:48 -0000

Dear Paul Hoffman

>Simpler than the above: make it a web page
> (as Brian points out, we already have a good URL),
> have one editor, have one leadership person who
> approves non-trivial changes (I think "IETF Chair" fits here well),
> have a "last modified" date on it, and update it as needed. If there
> is consensus in the community to do this, I'm happy to take on
> the HTMLizing and skip the RFCizing for this round.


I thank you for this opportunity. I think we need both the webpage and
the RFCs to make it more understood to all volunteer members around
the world. As a new comer to IETF my volunteer process experience was
started not good so far (see below attached), as I feel lost some
times by group-practice-policy, I think list leaders/holders should
help in such situations. I am reviewing the draft
<draft-hoffman-tao4677bis-15> and will comment on the changes and
future updates. Please note that practice may not always be perfect
like documents/webs procedures.

In conclusion, All policy procedures of IETF SHOULD be perfect, hope
we do our best together for this. I will write my comments on
some-points of overall procedures and for your draft, I also will try
to include New-Comers consideration by chairs and memebrs, so
procedure consider their experience and that do not be blocked by
informal directions a group takes over.

Abdussalam Baryun
University of glamorgan, UK
+++++++++++++++++++++++++++++++++++++++++++++++
To: manet <manet at ietf.org>
Subject: Re: [manet] I-D Action: draft-ietf-manet-olsrv2-15.txt
From: Abdussalam Baryun <abdussalambaryun at gmail.com>
Date: Sat, 19 May 2012 09:41:33 +0200

Dear All,

I beleive that we are all informally equal in terms of rights and
responsibilities, but in organisations we have formal responsibilities
and rights to make work-processes progress to the direction of the aim
and objectives of the organisation, not in the direction of some
individuals decisions. I beleive the best practice for IETF groups is
in RFC2418 and RFC3934.

On 5/18/12, Stan Ratliff <sratliff at cisco.com> wrote:
> It has never been the process (at least in the MANET working group) to
> formally track each and every comment coming in on a draft and actively
> notify/dispose of said items. This is rooted in the notion that the IETF is
> a volunteer organization; as such, we've all got "day jobs", and do the best
> we can. Another reason for this (slightly informal) process model is to keep
> the group from spinning ad-nauseum, generating vast amounts of email on
> trivial topics. This discussion is a reasonably good example of that very
> thing.

The process for MANET WG SHOULD follow the RFC2418. IMHO the IETF is a
formal organisation, and yes it is structured of volunteering members,
but it is not informal organisation. Please note that number of emails
SHOULD not be restricted, but the content of messages MAY be
restricted. Yes our relationships are RECOMMENDED to be friendly and
informally social to inhance the group activities.

All informal models give chances of more power to organisation
managers. I don't agree with the informal-process model, but agree
with RFC2418-process model.

>
> You made some comments/suggestions on OLSRv2. They were considered by the
> authors, and by the working group members. The authors didn't agree with you
> in all cases, and the working group, via its silence, indicated *they*
> didn't agree with you either. And now, apparently, you want to re-litigate
> all or part of that. I for one am not interested.
>

Silence is not a reaction (e.g. not an indication), because as you
mentioned we are volunteers and we have jobs, therefore, silence most
possibility means I am bussy, not meaning I agree nor disagree.

> My opinion is that OSLRv2-15 has cleared WGLC, and will be forwarded to the
> AD's/IESG for review and publication. If the working group members *DO NOT*
> agree with me, then let the fire-storm of emails commence.
>

I reply to this call that I *DO NOT* agree to give forward to
OLSRv2-14 or OLSRv2-15 until I comment on it, or only after concensus
collected for the decision (i.e. it is easy to collect electronically,
as in RFC2418 does not have to be face-to-face collecting). Regarding
the OLSRv2-15 draft it is better than OLSRv2-14 because it reduced my
confusions, but I will need some time to review OLSRv2-15 and comment
on it as well. Regarding fire-storm emails, it seems it will not be
happening in MANET WG, maybe active memebrs are about 60, not sure.

In conclusion, from the group chair last message, I understand that
there was no concensus collected for OLSRv2 to go forward, so the
MANET-WG still didn't make last decision yet.

I am sorry if I made any disturbing to any. In the end of all
processes I am interested in understanding and participating in IETF.
If the group or group chairs decides that I stop emailing in MANET, I
will stop without any complains to higher levels, and go to another
IETF group. Thanking you,

Best Regards,
Abdussalam
+++++++++++++++++++++++++++++++++++++++++++++++++++++

From abdussalambaryun@gmail.com  Mon Jun  4 02:45:17 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 268AD21F86E8 for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 02:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.482
X-Spam-Level: 
X-Spam-Status: No, score=-3.482 tagged_above=-999 required=5 tests=[AWL=0.117,  BAYES_00=-2.599, 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 zQfufxhxdlCu for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 02:45:16 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 90CB821F8603 for <ietf@ietf.org>; Mon,  4 Jun 2012 02:45:16 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2651417vcq.31 for <ietf@ietf.org>; Mon, 04 Jun 2012 02:45:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=RhCzhFJW0ndfyut3rOeYJLm01ShyNICYTM2D5BA6eYg=; b=0G9n91r1VRMyMS+vnwiYjf2+PVcxKsniLXgMm2/rZP3CQizQXi7witMUqgZRcIPzS1 81yMx6Yz8+4eWCHmYJL1ibaBul8pNNIzGooubKMIEL6kB2bYtRIyfKb8dqTKKnWO8VZ5 UKb4nM17nyu4ntFeaY5DefJfVQmnWix8EXDJ202n0XTkHjFuOFcIhrQj3aX/o7HF6v53 HLZTv+oaQC60kohi3W9j1I1VtII0uZl/Xj+um0yKnCxSpxiqiDhHzw1rbGW+wSfLm3Ao hFo9CfZBIJ9RWSuGuTGekwTihw+wwcWgyuzbKL//hNE6X/1rdMK9RgvPUxEheh67qSA8 F5+A==
MIME-Version: 1.0
Received: by 10.52.65.145 with SMTP id x17mr9900759vds.117.1338803116133; Mon, 04 Jun 2012 02:45:16 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Mon, 4 Jun 2012 02:45:16 -0700 (PDT)
Date: Mon, 4 Jun 2012 11:45:16 +0200
Message-ID: <CADnDZ8-GiVPK2i00zYEdHtnkoD+AmX7CRx0gwxbWcyggH4GU2g@mail.gmail.com>
Subject: Re: Making the Tao a web page
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: lixia@cs.ucla.edu, ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Mon, 04 Jun 2012 08:23:35 -0700
Cc: john-ietf@jck.com, sm@resistor.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 09:45:17 -0000

Hi

I agree with you, and would add we need the web and RFC so that we get
things right. However, to make quick progress in RFC is not to wait
for discussions to end, but to open a restricted period/window for
discussion which MUST end some date and make the changes/updates, then
take the final consensus,

Best regards
AB

+++++++++++++++++++++++++++++++++++++++++++++++++++++
On Jun 3, 2012, at 6:34 PM, John C Klensin wrote:

> ... I further guess that
> "on an ongoing basis" will be better for the document than
> getting a new snapshot out as an RFC and seeing how long it
> takes to get stale and how long after that it takes the
> community to notice. ...

I second the above statement
(my apology to John for quoting this single sentence out of his whole msg)

Lixia

From d.sturek@att.net  Mon Jun  4 06:36:38 2012
Return-Path: <d.sturek@att.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04E9A21F87E7 for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 06:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[AWL=-0.599, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, MIME_QP_LONG_LINE=1.396]
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 HbgO5a7UbtsP for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 06:36:36 -0700 (PDT)
Received: from nm35-vm5.bullet.mail.ne1.yahoo.com (nm35-vm5.bullet.mail.ne1.yahoo.com [98.138.229.101]) by ietfa.amsl.com (Postfix) with SMTP id 8C30721F85EA for <ietf@ietf.org>; Mon,  4 Jun 2012 06:36:36 -0700 (PDT)
Received: from [98.138.90.49] by nm35.bullet.mail.ne1.yahoo.com with NNFMP; 04 Jun 2012 13:36:32 -0000
Received: from [68.142.200.224] by tm2.bullet.mail.ne1.yahoo.com with NNFMP; 04 Jun 2012 13:36:32 -0000
Received: from [66.94.237.98] by t5.bullet.mud.yahoo.com with NNFMP; 04 Jun 2012 13:36:32 -0000
Received: from [127.0.0.1] by omp1003.access.mail.mud.yahoo.com with NNFMP; 04 Jun 2012 13:36:32 -0000
X-Yahoo-Newman-Id: 574756.28889.bm@omp1003.access.mail.mud.yahoo.com
Received: (qmail 13053 invoked from network); 4 Jun 2012 13:36:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1338816992; bh=WvEwzBLd9rAPlnRWwvVEbpizpqCsOSrW3QXdzGN5UsU=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:User-Agent:Date:Subject:From:To:CC:Message-ID:Thread-Topic:In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; b=xf0lf2u3GEuHk+GjTGN9GOJO8p39DeLEv9wbN1y+mLd/+F5u42rrKIcmh3w8YpobguBo1Z2XoQe/9pjFSE3npqOc6dRyXflXY1GOWeBQ8CHRPeWhyEm8RbTYQCEt3i0ypLIHA/AzH+yVuce4d0ukyjajDUHssG3NEcnn+k5zgFY=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: EJf.M74VM1mOdW7E5sUUmTsXzWdbp3eCkwJtmIz9tclADR. C0gvS9Jg3dyMD15ifaivKqHed5FMxp9IXepCIIe.GWO.3V78PrUKfm0VrXCX josimu_fRga7Q_dtSWLoiOz7GIuIu0eGz5pMK7qGz5Kq.L3MTUR3sKs0UzAf BJx.pVnTmEVl3p3nAWaA96rcOJJDiWlfAWGSN6.qgxO5Jk3f_ACcweMfwOP0 yTyoBIfDWY6.SEBqk5fFgMIoeBTAsdjB2bAEM0KXGSweG5KsE8VaHLcZXbCt q_59l9nKvvE0GM48wf.i4cAvdy5Co01imWQVcm8QtGIfHEMat5ZoftoRW9TX uw_e85OFjkStkjKtqKI_SHGIbHBwQFKgzskp2bp5_vYNbcfXBr7fuUk4vwRq wa_k0C8MaFeqk.niUaGefyTJOAqf2nScGB83YpiRfhZrVYslkFsvUnuRvJf4 9a7kHP_RrCvmjWd8oNGpp0uXjrToA3XEYGTsEd_41sBVCo7oy9PfMwbct3aS DAADF7_ev8HyP5csVebrQAzNo64X3Zguaqwo3yYxyAHZPDtSjoBcQt9hHKgl C_8vy.37piigeCKYLha_SRT9eHPvSoIcqHfaoiuy9ap6TNb7GkHPNEUba0wr LZiQ-
X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo-
Received: from [192.168.0.198] (d.sturek@69.105.139.102 with login) by smtp111.sbc.mail.mud.yahoo.com with SMTP; 04 Jun 2012 06:36:31 -0700 PDT
User-Agent: Microsoft-MacOutlook/14.2.2.120421
Date: Mon, 04 Jun 2012 06:35:11 -0700
Subject: Re: [manet] Defining subnet models used by our protocols
From: Don Sturek <d.sturek@att.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, manet <manet@ietf.org>, <autoconf@ietf.org>
Message-ID: <CBF2059A.16905%d.sturek@att.net>
Thread-Topic: [manet] Defining subnet models used by our protocols
In-Reply-To: <CADnDZ889mGxHsCcXsr=SgJHqzHKZ8t9AKCpgsUETYNm9vJuW6g@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="EUC-KR"
Content-transfer-encoding: quoted-printable
X-Mailman-Approved-At: Mon, 04 Jun 2012 08:23:35 -0700
Cc: "robert.g.cole" <robert.g.cole@us.army.mil>, ietf <ietf@ietf.org>, "Charles E. Perkins" <charliep@computer.org>, "Emmanuel.Baccelli" <Emmanuel.Baccelli@inria.fr>, Ulrich Herberg <ulrich@herberg.name>, Stan Ratliff <sratliff@cisco.com>, "ian.chakeres" <ian.chakeres@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 13:36:38 -0000

Hi Abdullalam,

I think basing a routing protocol (like those in MANET and also ROLL) on
some standard definition of subnets is:
1)  not needed in my experience with virtually every deployment scenario I
have seen
2)  conflates the network topology with the pratical issue of providing
peer to peer route discovery and establishment

Don



On 6/4/12 12:17 AM, "Abdussalam Baryun" <abdussalambaryun@gmail.com> wrote:

>Hi Don, and All,
>
>I would like to know your opinion about why we don't define subnets for
>MANET?
>
>On 6/3/12, Don Sturek <d.sturek@att.net> wrote:
>> +1
>>
>> On 6/2/12 11:21 PM, "Charles E. Perkins" <charliep@computer.org> wrote:
>
>Could we discuss why we don't define subnets models? I don't
>understand adding (+1). I hope the chair does not ask me to close this
>thread too :)
>
>The ad hoc autoconfig was proposed in 2005 and proposed-ended in 2011
>so living for about 6 years only. What was the reason for the proposed
>close of it? please read the DA Jari's reasons below.
>
>IMO it because it had low/no useful discussions and only produced one
>RFC which is RFC5889, why only one? what happend within 6 years?  IMO
>any WG should have more discussions, discussions are mandatory
>activity for WG. Not discussing issues is like ignoring the value
>input to group progress. Healthy discussions are more important than
>producing more documents produced, because discussions are really the
>source of correct documents (don't mean it has to be perfect, but
>should not be misleading). WGs should be compared in terms of the
>amount of discussions not in amount of documents forwarded/submitted.
>
>According to Chakeres and Maker (2006) [1] quoated below:
>
>[The autoconf WG is chartered to initially develop
>two documents. The first document is a document
>defining the MANET architecture and how MANET
>relates to IP networks and the Internet. The second
>document is to define the terminology, problem statement
>and goals for autoconf. These autoconf documents
>will be discussed on the autoconf mailing list.]
>
>That WG did not produce the definition of MANET architecture. Which I
>think is related to the subnet-model definition importance for MANET.
>So i understand the authors see the importance of defining something
>for MANET in 2006. Now, Do we have a network architecture definition
>of MANET in one RFC?
>
>> On 6/2/12 11:21 PM, "Charles E. Perkins" <charliep@computer.org> wrote:
>>>Hello folks,
>>>
>>>I would be opposed to requiring the subnet model as a mandatory
>>>component of any current [manet] working group charter item.
>>>
>>>We have had at least ten years of experience showing that requiring
>>>subnets can derail practically any wireless network discussion within
>>>the sphere of applicability of manet protocols.  The reasons are many
>>>and varied -- and, I must admit, really very interesting.
>>>
>>>It was the death of another working group which really should have
>>>been allowed to go forward except for disagreements about certain
>>>subnet-related constructs.  Let's not consign ourselves to the same
>>>fate.
>
>In future the death of the WG will be because they don't discuss
>things on the list, or don't have what to discuss, please read the
>reasons mentioned by Jari Arkko below. IMO for the future, some day
>any WGs possibly will close and other days new WGs comes.
>
>>>
>>>Regards,
>>>Charlie P.
>
>References:
>[1] Chakers, I., and Maker, J., 'Mobile Ad Hoc Networking and the
>IETF', Mobile Computing and communication review, volume 1, Number 2,
>2006.
>
>Best regards
>
>Abdussalam Baryun
>University of Glamorgan, UK
>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>To: "autoconf at ietf.org" <autoconf at ietf.org>
>Subject: [Autoconf] closing the working group?
>From: Jari Arkko <jari.arkko at piuha.net>
>Date: Tue, 29 Mar 2011 08:48:47 +0200
>
>--------------------------------------------------------------------------
>------
>I have looked at the discussions on the list (or lack thereof). I also
>cannot see too many internet drafts on the topics belonging to the
>group's charter. I am very happy with the RFC that has been produced
>by the working group, but we also seem to have some actual protocol
>work happening elsewhere (e.g., in the context of the ROLL WG).
>
>I discussed this matter with the chairs and my co-AD, and we are
>wondering if it would be time to close the working group. I do know
>that there is at least one implementation team that is still in the
>process of describing their DHCP-based solution, maybe there are
>similar efforts on the distributed solution space. My proposal is that
>we close the working group and I'be VERY happy to AD sponsor all such
>solutions to Experimental RFCs as soon as we have those proposals in
>some reasonable shape.
>Thoughts?
>
>Jari
>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>To: IETF-Announce at ietf.org
>Subject: WG Review: Ad Hoc Network configuration (autoconf)
>From: The IESG <iesg-secretary at ietf.org>
>Date: Wed, 27 Jul 2005 14:28:49 -0400
>Cc: manetautoconf at ml.free.fr
>List-help: <mailto:ietf-announce-request@ietf.org?subject=3Dhelp>
>List-id: ietf-announce.ietf.org
>List-post: <mailto:ietf-announce@ietf.org>
>List-subscribe:
><https://www1.ietf.org/mailman/listinfo/ietf-announce>,
><mailto:ietf-announce-request@ietf.org?subject=3Dsubscribe>
>List-unsubscribe:
><https://www1.ietf.org/mailman/listinfo/ietf-announce>,
><mailto:ietf-announce-request@ietf.org?subject=3Dunsubscribe>
>Reply-to: iesg at ietf.org
>Sender: ietf-announce-bounces at ietf.org
>
>--------------------------------------------------------------------------
>------
>A new IETF working group has been proposed in the Internet Area. The
>IESG has not
>made any determination as yet. The following draft charter was
>submitted, and is
>provided for informational purposes only. Please send your comments to
>the IESG
>mailing list (iesg at ietf.org) by August 3rd.
>
>+++++++++++++
>
>Ad Hoc Network configuration (autoconf)
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>Current Status: Proposed Working Group
>
>Chairs:
>TBD
>
>Internet Area Director(s):
>Mark Townsley <townsley at cisco.com>
>Margaret Wasserman <margaret at thingmagic.com>
>
>Internet Area Advisor:
>Margaret Wasserman <margaret at thingmagic.com>
>
>Mailing Lists:
>General Discussion: manetautoconf at ml.free.fr
>To Subscribe: manetautoconf-request at ml.free.fr
>
>Description of the WG:
>
>In order to communicate among themselves, ad hoc nodes (refer to RFC
>2501) may need to configure their network interface(s) with local
>addresses that are valid within an ad hoc network. Ad hoc nodes may
>also need to configure globally routable addresses, in order to
>communicate with devices on the Internet.
>
>Ad hoc networks present several new challenges. Unlike in traditional
>IP networks, each ad hoc node, besides being a traffic end-point,
>should be capable of forwarding traffic destined for other hosts.
>Additionally, nodes constituting an ad-hoc network do not share access
>to a single multicast-capable link for signaling. Many protocol
>specifications used in traditional IP networks e.g. RFCs 2462, 2463
>etc. do, however, assume that subnet-local signals (e.g. link-local
>multicast signal) are received by each of the hosts on the particular
>subnet without being forwarded by the routers defining the subnet
>boundary.
>
>The main purpose of the AUTOCONF WG is to standardize mechanisms to be
>used by ad hoc nodes for configuring unique local and/or globally
>routable IPv6 addresses. The ad hoc nodes under consideration are
>expected to support multi-hop communication by running a MANET routing
>protocol, e.g. those developed by the IETF MANET WG. However, this may
>or may not mean that an AUTOCONF mechanism will be dependent on any
>specific MANET routing protocol. With this in mind, the goals of
>AUTOCONF WG are to:
>
>- Produce a "terminology and problem statement" document, defining the
>problem statement and goals for AUTOCONF.
>
>- Develop an IPv6 stateless autoconfiguration mechanism to be used by
>ad hoc nodes for configuring unique local addresses as well as, in
>cases where Internet connectivity exists, globally routable unique
>addresses.
>
>- Develop a stateful address autoconfiguration mechanism to be used by
>ad hoc nodes for configuring globally routable unique addresses, if an
>address providing entity such as DHCPv6 server is available.
>
>- Develop a mechanism to promote configured address uniqueness in the
>situation where different ad hoc networks merge.
>
>Issues and requirements related to prefix and/or address providing
>entities, such as an Internet gateway, will be addressed within the
>group to the extent that they are directly related to the AUTOCONF
>mechanisms. Security concerns related to AUTOCONF mechanisms will also
>be discussed within the group.
>
>The working group will reuse existing specifications whenever
>reasonable and possible.
>
>Goals and Milestones:
>
>Oct 05 : Submit "terminology and problem statement" document for WG
>review
>Oct 05: Submit initial I-D(s) of candidate proposed AUTOCONF mechanisms
>and design frameworks
>Feb 06: Submit "terminology and problem statement" document to IESG for
>publication as an informational RFC
>Apr 06: Submit initial I-D of "stateless autoconfiguration mechanism"
>for WG review
>Apr 06: Submit initial I-D of "stateful autoconfiguration mechanism"
>for WG review
>Apr 06: Submit initial -ID of "configured address uniqueness
>maintenance" for WG review
>Aug 06: Revise WG documents and review
>Dec 06 Revise documents based upon implementation experience
>Apr 07: Submit "stateless autoconfiguration mechanism" specification
>and supporting documentation to IESG for publications as Proposed
>Standard
>Apr 07: Submit "stateful autoconfiguration mechanism" specification and
>supporting documentation to IESG for publications as Proposed Standard
>Apr 07: Submit "configured address uniqueness maintenance"
>specification and supporting documentation to IESG for publications as
>Proposed Standard
>Oct 07: Close or recharter the WG
>
>
>_______________________________________________
>IETF-Announce mailing list
>IETF-Announce at ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf-announce
>
>
>
>
>
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>
>>>
>>>
>>>On 6/2/2012 1:12 AM, Abdussalam Baryun wrote:
>>>> Hi All
>>>>
>>>> I want to discuss this subnet definition issue that was raised in the
>>>> 82 meeting, could we discuss about it please. Will we need to put it
>>>> in a draft or include it in our active draft working in progress,
>>>> please advise,
>>>>
>>>> Abdussalam Baryun,
>>>> University of Glamorgan, UK
>>>> ++++++++++++++++++++++++++++++
>>>>
>>>> In WG 82 meeting it was mentioned (Bob Cole and Teco discussions):
>>>> BC>  that subnet-models are not defined But in DLEP it looks at two
>>>> subnet-models (different models; e.g. radio subnet-models,
>>>> sat-subnet-models). We are defining IP over a subnet, but the subnet
>>>> is not defined. Then we don=A9=F6t know how to define control protocols,
>>>> data-packet-formats, and managements-models without having a subnet
>>>> model in mind.
>>>> TB>  In sat-comms the up-link and down-link can be very different. So
>>>> for different nodes on same carrier can be different data rates, SNR,
>>>> etc. so it is important that DLEP include the link metrics, even if it
>>>> is a full connected subnet.
>>>> BC>  the subnet depends on the link of the subnet-underlying model,
>>>> The semantics of link up and down are determined by the underlying.
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>>> ********************************************************************
>>>> This email and any attachments are confidential to the intended
>>>> recipient and may also be privileged. If you are not the intended
>>>> recipient please delete it from your system and notify the sender.
>>>> You should not copy it or use it for any purpose nor disclose or
>>>> distribute its contents to any other person.
>>>> ********************************************************************
>>>> _______________________________________________
>>>> manet mailing list
>>>> manet@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/manet
>>>>
>>>>
>>>
>>>
>>>--
>>>Regards,
>>>Charlie P.
>>>
>>>_______________________________________________
>>>manet mailing list
>>>manet@ietf.org
>>>https://www.ietf.org/mailman/listinfo/manet
>>
>>
>>



From alexey.melnikov@isode.com  Mon Jun  4 12:01:49 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57D0221F84A7; Mon,  4 Jun 2012 12:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.396
X-Spam-Level: 
X-Spam-Status: No, score=-102.396 tagged_above=-999 required=5 tests=[AWL=0.203, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 jlaSY1KxXsgv; Mon,  4 Jun 2012 12:01:48 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC8111E80BC; Mon,  4 Jun 2012 12:01:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1338836507; d=isode.com; s=selector; i=@isode.com; bh=vxo9UNRHNXKosweE/7BBzhB8IVZ0Ll8Zii4qOOSGJOI=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=DXUlY8hlueWQ6af40iOP9KQgx8xRYhMglblOtCsSfTEVgIH/5XQ9vNCIi+Q3t0jST+zzz1 IZRrs48uXe9Saf2mZOTMIJMu4nBhjJ4iOWoknM8eyz7fJjbc8qfXd4DGj+KUW12F2N9478 U4LUNjEBo0gs6MJIx8BuWWC0PjxDN6Y=;
Received: from [172.20.10.2] ((unknown) [212.183.128.204])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T80GFgAE43EA@rufus.isode.com>; Mon, 4 Jun 2012 20:01:44 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4FCD0614.5050902@isode.com>
Date: Mon, 04 Jun 2012 20:01:40 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: apps-discuss@ietf.org, draft-ietf-nea-pt-tls.all@tools.ietf.org
Subject: APPSDIR review of draft-ietf-nea-pt-tls-04
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 19:01:49 -0000

I have been selected as the Applications Area Directorate reviewer for 
this draft (for background on APPSDIR, please see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document shepherd 
or AD before posting a new version of the draft.  The review is not 
copied to the IESG as the Last Call has not been announced yet.

Document: draft-ietf-nea-pt-tls-04
Title: PT-TLS: A TCP-based Posture Transport (PT) Protocol
Reviewer: Alexey Melnikov
Review Date: June 4, 2012

Summary: This document is almost ready for publication as a Proposed 
Standard, although some [mostly] SASL related issues remain.

This document specifies PT-TLS, a TCP-based Posture Transport (PT)
protocol.  The PT-TLS protocol carries the Network Endpoint
Assessment (NEA) message exchange under the protection of a Transport
Layer Security (TLS) secured tunnel.

(Note, I've reviewed -04, but I think all of this still applies to -05.)


Major:

In 3.4.2.1: RFC 6125 use details are missing. You need to describe 
whether CN-IDs and SRV-IDs are allowed, whether wildcards are allowed, 
etc. I can suggest some details.


Minor:

In Section 3.2: This document is not yet Internet Standard, it will be 
Proposed Standard. Suggest saying "Publication on Standards Track" 
instead instead of "Internet Standard". The same issue in the IANA 
consideration section.

In 3.8.1: I think one instance of "SASL authentication messages" --> 
"SASL authentication mechanisms". Otherwise this sentence is out of 
place, as you are not talking about SASL messages.

In 3.8.4: in SASL the server doesn't return abort as an error code, it 
just fails the authentication exchange. I suggest removing it as a choice.

In 3.8.7: you define the Reserved field which I assume is used for 
padding? If yes, then you will not get proper alignment for the next 
field, as SASL mechanism names are variable length. (If you intended 
that they are always sent as 20 bytes, then this is missing from the 
document.)

In 3.8.10:

The Abort choice is really not needed (as per above).

Also, can you give me an example of when the Mechanism Failure will be 
returned instead of just Failure?

In 3.9: Failed Authentication error code - how does this differ from 
SASL Authentication result with Failure code?

In 4.1.2, second block, the first bullet: I think you meant "client" 
instead of the "server".


Question (might not be an issue):

In 6.2: is it possible to register a vendor specific value without a 
specification?

The same question for 6.3.


Nits: None


From ajs@anvilwalrusden.com  Mon Jun  4 12:14:15 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 786E911E80D1 for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 12:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level: 
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599]
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 c24d7NaDUeV9 for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 12:14:15 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 06E6F11E80C0 for <ietf@ietf.org>; Mon,  4 Jun 2012 12:14:14 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 160351ECB41D for <ietf@ietf.org>; Mon,  4 Jun 2012 19:14:14 +0000 (UTC)
Date: Mon, 4 Jun 2012 15:14:12 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Friday scheduling in YVR?
Message-ID: <20120604191412.GH614@mail.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 19:14:15 -0000

Dear colleagues,

At the last meeting in Paris, the Friday sessions ended by 13:30.

I haven't seen (but might have missed) follow-up about that trial, and
it isn't clear to me what the conclusion is about that approach.  Does
anyone know?  (It's time for me to buy a plane ticket, is why I'm
asking.)

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@resistor.net  Mon Jun  4 12:27:05 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B1421F8589 for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 12:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hU-21dQvZnhX for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 12:27:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D2FF321F857F for <ietf@ietf.org>; Mon,  4 Jun 2012 12:27:01 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q54JQocA005316; Mon, 4 Jun 2012 12:26:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338838015; i=@resistor.net; bh=dKMhU+rvU8pYOjVUf9o5vShz5mGXrQnIGtet81sFwXw=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=iqTy0br0YQmJ4U2tyOCdO2AbG4s0vjQuKIOJ7/bkwbgw81beEXh45+G8jHuzLA3Qv P7gpWmzWgsaonY7CJmQ2qZi7lMmhltlkfOWRd+5m74l7ECnaJj7En8HAw9XfU3Drkh 2OFN7NEnHW7m6de8qgjhftQN2ceFm0KN7S9nQhcA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1338838015; i=@resistor.net; bh=dKMhU+rvU8pYOjVUf9o5vShz5mGXrQnIGtet81sFwXw=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=gs6jpjliJQE1PrnW+0f9opl9EDiQvCuYuR93bEwZIeNWDuhglVqH+NX/mb+mMxdjJ CtjkBvkhq0lYNwTX4SK77n/QGiz1VnLo/d4vAaybE+UMWH11c778EvmA0e2WpXnqax D4id3IMHnwo+R9qwpHOvkuYjzmMZZRtZkku8+Dus=
Message-Id: <6.2.5.6.2.20120604012929.09cbc410@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 04 Jun 2012 12:18:23 -0700
To: dcrocker@bbiw.net, IETF <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: Making the Tao a web page
In-Reply-To: <4FCC4F8F.1060800@dcrocker.net>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <4FC8AFA9.1020200@inex.ie> <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com> <6.2.5.6.2.20120603145115.09cfc558@resistor.net> <4FCC4F8F.1060800@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 19:27:05 -0000

Hi Dave,
At 23:02 03-06-2012, Dave Crocker wrote:
>In effect, the wiki construct becomes a form of 
>incrementally-updatable internet draft.  For documents involving 
>procedures rather than products, this well might be a better working 
>base than I-Ds...

It's more of an experiment.  If it is a success someone gets all the 
glory by turning it into an I-D.  If the experiment fails the people 
who have put in the effort will have wasted their time.

I would look at this in terms of the tool used for a collaborative 
effort.  It is left to the community to decide whether further 
changes are needed for the output to reflect consensus.

>That is, perhaps what makes this workable is imposing an editor role 
>onto the wiki and assign responsibility for monitoring changes to 
>the editors?  (It might even be worth integrating it into the rest 
>of the I-D administration environment?)

There is a Trac plugin for email notifications.

I am not thinking of the integration part as it requires more than a 
lightweight effort.  Eliot pointed out that there is a socialization 
problem.  Who knows, may be the collaborative effort might help.

Regards,
-sm 


From housley@vigilsec.com  Mon Jun  4 12:40:42 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 313D321F867D for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 12:40:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 UBl2tvWIa9nn for <ietf@ietfa.amsl.com>; Mon,  4 Jun 2012 12:40:41 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id A2F5121F867C for <ietf@ietf.org>; Mon,  4 Jun 2012 12:40:41 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 7EBB39A471B; Mon,  4 Jun 2012 15:40:51 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id E9QbX2-yY6nQ; Mon,  4 Jun 2012 15:40:33 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 7F4A99A470F; Mon,  4 Jun 2012 15:40:50 -0400 (EDT)
Subject: Re: Friday scheduling in YVR?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20120604191412.GH614@mail.yitter.info>
Date: Mon, 4 Jun 2012 15:40:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <02BA7D9A-B1C6-4124-9B1F-8D2DE141E55F@vigilsec.com>
References: <20120604191412.GH614@mail.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 19:40:42 -0000

Andrew:

That is the current plan, but we have not seen all of the WG requests =
yet, so it is subject to change.

Russ


On Jun 4, 2012, at 3:14 PM, Andrew Sullivan wrote:

> Dear colleagues,
>=20
> At the last meeting in Paris, the Friday sessions ended by 13:30.
>=20
> I haven't seen (but might have missed) follow-up about that trial, and
> it isn't clear to me what the conclusion is about that approach.  Does
> anyone know?  (It's time for me to buy a plane ticket, is why I'm
> asking.)
>=20
> Best regards,
>=20
> A
>=20
> --=20
> Andrew Sullivan
> ajs@anvilwalrusden.com


From ron.even.tlv@gmail.com  Mon Jun  4 14:23:02 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3C4411E80DF; Mon,  4 Jun 2012 14:23:01 -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 fhDgSf814vHC; Mon,  4 Jun 2012 14:22:59 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 23D2D11E80EC; Mon,  4 Jun 2012 14:22:58 -0700 (PDT)
Received: by werb13 with SMTP id b13so3605459wer.31 for <multiple recipients>; Mon, 04 Jun 2012 14:22:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=5FGk1VhOrYtA3rMsj8vOwLC415uw9sXew8WnrWZhFik=; b=01L3UtUaaqsaa85rMRGi7Guw9qAGO6QRMo08QzcJ6DaurUFcFyxqDH6roIeiP1l9Px sX4j5JrEScMFfOA8Y0nTAfdca9+Oy2J1t5Htj6dZvEWUyJ+bHhPAkIy+iYS4Hv6Q3pHr +qbKOW5XfAy2PRR/JoXTBZa6UOuiS7QkFXrvd0/+pwgBpnIIO4cg2H3DZa0fuZ6UOf2i Z639Pv4Hul4C89Q6fWyNSG1LoUGSA4YfKHrl4TDHyLnrt9NQLO6EhKnnmvOmLuFjzfV7 2KSjsAQ4JtMH7DC/v7ujI3zfVFHXqzjx1LxNPAA/9KdPvlNhxQeE3yw+8Wj8Cy95lfos Pl1g==
Received: by 10.216.50.80 with SMTP id y58mr6011977web.106.1338844975531; Mon, 04 Jun 2012 14:22:55 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-182-224-219.red.bezeqint.net. [79.182.224.219]) by mx.google.com with ESMTPS id gb9sm22526945wib.8.2012.06.04.14.22.53 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jun 2012 14:22:54 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-nea-pt-tls.all@tools.ietf.org>
Subject: GenART LC review of draft-ietf-nea-pt-tls-05
Date: Tue, 5 Jun 2012 00:20:26 +0300
Message-ID: <4fcd272e.2968b40a.55d4.ffff9de3@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005B_01CD42B1.032B5AF0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1Cl9xExNAkih6WSYeHA9SkXDOg7g==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 21:23:02 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_005B_01CD42B1.032B5AF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-ietf-nea-pt-tls-05

Reviewer: Roni Even

Review Date:2012-6-4

IETF LC End Date: 2012-6-13

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

Major issues:

 

Minor issues:

1.       In section 3.2 "Therefore, this specification requests the IANA
reserve a TCP port number for use with the PT-TLS protocol upon publication
of this specification as an Internet standard RFC." I think it will  be
better to have here the assigned port number and instruct the RFC editor to
put the correct value.

2.       In section 3.4.2.2 last paragraph you summarize the text from
section 3.8 while in the paragraph above you provide the reference. Why do
you need the last paragraph if 3.8 is referenced.

3.       In various places you refer to SMI 0 as IETF SMI number while
according to the table it is IANA SMI number.

4.       I assume that all implementations MUST support message type vendor
ID 0. Is this mentioned?

5.       In section 3.5 and 6.1 you propose a policy of "Expert Review with
Specification Required ". I think that according to RFC5226 expert review is
implied if you select a specification required policy.

6.       In section 3.6 on 9+ "Recipients of messages   of type 9 or higher
that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message
Type of a received PT-TLS message MUST respond with a Type Not Supported
PT-TLS error code in a PT-TLS Error message." I think this is true only for
Message Type Vendor ID 0.

7.       In 3.7.1 for Max vers and prefs ver you say that they MUST be set
to 1. I think it will be more correct here to say SHOULD since you explain
afterwards that they may have other values.

8.       In section 3.7.2 "the recipient SHOULD send". Why not make it a
MUST here.

9.       In section 3.7.2 "The version selected MUST be within the Min Vers
to Max Vers inclusive range sent in the Version Request   Message" I was
expecting to see pref ver here.

10.   In section 3.8.3 " The SASL client authentication starts when the NEA
Server  enters the PT-TLS Negotiation phase and its policy indicates  that
an authentication of the NEA Client is necessary but was not performed
during the TLS handshake protocol " my read of  section 3.8 second paragraph
is that it can be done even if was done in the TLS handshake so the last
part of the sentence is not correct, if there is a policy you do it anyhow.
This comment is also for the third paragraph.

11.   In section 3.9 I noticed that you propose to send the entire original
message. Isn't it enough to send only the message identifier. This is based
on the last sentence of this section.

12.   Most of the text in section 6.1 repeats RFC5226 but in your words. Are
you trying to change some of RFC5226 text if not why write it in different
words?

 

 

 

Nits/editorial comments:

 


------=_NextPart_000_005B_01CD42B1.032B5AF0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2023900102;
	mso-list-type:hybrid;
	mso-list-template-ids:-625979886 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-=
nea-pt-tls-05<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;6&#8211;4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;6&#8211;13<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as a standard track =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC</span><=
span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.2 </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&#8220;Ther=
efore, this specification requests the IANA reserve a TCP port number =
for use with the PT-TLS protocol upon publication of this specification =
as an Internet standard RFC.&#8221; I think it will&nbsp; be better to =
have here the assigned port number and instruct the RFC editor to put =
the correct value.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.4.2.2 last paragraph you summarize the text from section 3.8 while in =
the paragraph above you provide the reference. Why do you need the last =
paragraph if 3.8 is referenced.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In various =
places you refer to SMI 0 as IETF SMI number while according to the =
table it is IANA SMI number.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I assume =
that all implementations MUST support message type vendor ID 0. Is this =
mentioned?<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.5 and 6.1 you propose a policy of &#8220;Expert Review with =
Specification Required &#8220;. I think that according to RFC5226 expert =
review is implied if you select a specification required =
policy.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.6 on 9+ &#8220;Recipients of messages&nbsp;&nbsp; of type 9 or higher =
that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message =
Type of a received PT-TLS message MUST respond with a Type Not Supported =
PT-TLS error code in a PT-TLS Error message.&#8221; I think this is true =
only for Message Type Vendor ID 0.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In 3.7.1 =
for Max vers and prefs ver you say that they MUST be set to 1. I think =
it will be more correct here to say SHOULD since you explain afterwards =
that they may have other values.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.7.2 &#8220;the recipient SHOULD send&#8221;. Why not make it a MUST =
here.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.7.2 &#8220;The version selected MUST be within the Min Vers to Max =
Vers inclusive range sent in the Version Request&nbsp;&nbsp; =
Message&#8221; I was expecting to see pref ver =
here.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>10.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.8.3 &#8220; The SASL client authentication starts when the NEA =
Server&nbsp; enters the PT-TLS Negotiation phase and its policy =
indicates&nbsp; that an authentication of the NEA Client is necessary =
but was not performed during the TLS handshake protocol &#8220; my read =
of&nbsp; s</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>ection 3.8 =
second paragraph is that it can be done even if was done in the TLS =
handshake so the last part of the sentence is not correct, if there is a =
policy you do it anyhow. This comment is also for the third =
paragraph.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>11.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.9 I noticed that you propose to send the entire original message. =
Isn&#8217;t it enough to send only the message identifier. This is based =
on the last sentence of this section.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>12.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Most of =
the text in section 6.1 repeats RFC5226 but in your words. Are you =
trying to change some of RFC5226 text if not why write it in different =
words?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_005B_01CD42B1.032B5AF0--


From adrian@olddog.co.uk  Mon Jun  4 14:25:25 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74FD611E8111; Mon,  4 Jun 2012 14:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.513
X-Spam-Level: 
X-Spam-Status: No, score=-2.513 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599]
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 N2eYLW1AsAQD; Mon,  4 Jun 2012 14:25:24 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 901F711E810D; Mon,  4 Jun 2012 14:25:24 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q54LPGDs002370;  Mon, 4 Jun 2012 22:25:16 +0100
Received: from 950129200 (ns-visitor-nsrp.juniper.net [208.223.208.242]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q54LPDsR002359 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 4 Jun 2012 22:25:15 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: Last Call updates to draft-farrresnickel-ipr-sanctions
Date: Mon, 4 Jun 2012 22:25:13 +0100
Message-ID: <014f01cd4298$888bd4e0$99a37ea0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1CmA0bSNQkdzonQfWjJkhEr7THMw==
Content-Language: en-gb
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 21:25:25 -0000

Hi,

I posted an update with changes as follows:

Abstract and Introduction:
Clarify applicability to IPR

Introduction:
Add note to clarify this I-D does not address or limit other legal sanctions.

2.2
Fix places where Note Well shows up

3
Clarify first step in sanctions

Throughout
Typos and style 

I believe I replied to all last call comments and have made updates consistent
with those replies. Please shout if you think I missed something.

Thanks,
Adrian

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]
> On Behalf Of internet-drafts@ietf.org
> Sent: 04 June 2012 22:00
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-farrresnickel-ipr-sanctions-06.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> 
> 	Title           : Sanctions Available for Application to Violators of
IETF IPR
> Policy
> 	Author(s)       : Adrian Farrel
>                           Pete Resnick
> 	Filename        : draft-farrresnickel-ipr-sanctions-06.txt
> 	Pages           : 11
> 	Date            : 2012-06-04
> 
>    The IETF has developed and documented policies that govern the
>    behavior of all IETF participants with respect to Intellectual
>    Property Rights (IPR) about which they might reasonably be aware.
> 
>    The IETF takes conformance to these IPR policies very seriously.
>    However, there has been some ambiguity as to what the appropriate
>    sanctions are for the violation of these policies, and how and by
>    whom those sanctions are to be applied.
> 
>    This document discusses these issues and provides a suite of
>    potential actions that can be taken within the IETF community in
>    cases related to patents.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-farrresnickel-ipr-sanctions-06.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-farrresnickel-ipr-sanctions-06.txt
> 
> The IETF datatracker page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From duerst@it.aoyama.ac.jp  Tue Jun  5 02:43:08 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB87321F86D5 for <ietf@ietfa.amsl.com>; Tue,  5 Jun 2012 02:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.68
X-Spam-Level: 
X-Spam-Status: No, score=-98.68 tagged_above=-999 required=5 tests=[AWL=-0.690, BAYES_50=0.001, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_35=0.6, J_CHICKENPOX_37=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 BJeyH9I7EUTp for <ietf@ietfa.amsl.com>; Tue,  5 Jun 2012 02:43:06 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 4174F21F86B3 for <ietf@ietf.org>; Tue,  5 Jun 2012 02:43:05 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q559gqHe026517 for <ietf@ietf.org>; Tue, 5 Jun 2012 18:42:52 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 4a87_35b8_d19f44d4_aef2_11e1_ab9e_001d096c5782; Tue, 05 Jun 2012 18:42:51 +0900
Received: from [IPv6:::1] ([133.2.210.1]:52147) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15CE4E6> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 5 Jun 2012 18:42:56 +0900
Message-ID: <4FCDD499.7060206@it.aoyama.ac.jp>
Date: Tue, 05 Jun 2012 18:42:49 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: draft-farrell-decade-ni.all@tools.ietf.org
Subject: APPSDIR review of draft-farrell-decade-ni-07
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 09:43:08 -0000

Hello everybody,

[For replies, please trim the cc list, thanks!]


I have been selected as the Applications Area Directorate reviewer for 
this draft (for background on appsdir, please see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).


Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document shepherd 
or AD before posting a new version of the draft.


Document: draft-farrell-decade-ni-07
Title: Naming Things with Hashes
Reviewer: Martin DÃ¼rst
Review Date: 2012-06-03, 2012 (written up 2012-06-04/05)
IETF Last Call Date: started 2012-06-04, ends 2012-07-02


Summary: This draft addresses a real generic need, but the current form 
of the draft is the result of adding more and more special cases without 
a clear overall view and a firm hand to separate the wheat from the 
chaff. This shows both in the technical issues as well as in many of the 
editorial issues below. This draft is not ready for publication without 
some serious additional work, but that work is mostly straightforward 
and should be easy to complete quickly.



Major design issue:

The draft defines two schemes, which differ only slightly, and mostly 
just gratuitously (see also editorial issues).
These are the ni: and the nih: scheme. As far as I understand, they 
differ as follows:
                                     ni:                nih:
authority:                          optional           disallowed
ascii-compatible encoding:          base64url          base16
check digit:                        disallowed         optional
query part:                         optional           disallowed
decimal presentation of algorithm:  disallowed         possible

The usability of URIs is strongly influenced by the number of different 
schemes, with the smaller a number, the better. As a somewhat made-up 
example, if the original URIs had been separated into httph: for HTML 
pages and httpi: for images, or any other arbitrary subdivision that one 
can envision, that would have hurt the growth and extensibility of the 
Web. Creating new URI schemes is occasionally necessary, and the ideas 
that lead to this draft definitely seem to warrant a new scheme (*), but 
there's no reason for two schemes.
[(*) I know people who would claim the the .well-formed http/https thing 
is completely sufficient, no new scheme needed at all.]

More specifically, if the original URIs had been separated into httpm: 
(for machines) and httph: (for humans), the Web for sure wouldn't have 
grown at the speed it did (and does) grow. In practice, there are huge 
differences in human 'speakability' for URIs (and IRIs, for that 
matter); compare e.g. http://google.com with 
http://www.google.co.jp/#sclient=psy-ab&hl=en&site=&source=hp&q=hash&oq=hash&aq=f&aqi=g4&aql=
(which I have significantly shortened to hopefully eliminate potential 
privacy issues), or compare the average mailto: URI with the average 
data: URI. However, what's important is that there never has been a 
strong dividing line between machine-only and human-only URIs or 
schemes, the division has always been very gradual. Short and mainly 
human-oriented URIs have of course been handled by machines, and on the 
other hand, very long URIs have been spoken when really necessary. 
"Speakability" has been maintained to some extent by scheme designers, 
and to some extent by "survival of the fittest" (URIs that weren't very 
speakable (or spellable/memorizable/guessable/...), and their Web sites, 
might just die out slowly).

It should also be noted that the resistance against multiple URI schemes 
may have been low because there are so many different ways to express 
hashes in the draft anyway, and one more (the nih: section is the last 
one before the examples section) didn't seem like much of a deal 
anymore. But when it comes to URIs, one less is a lot better than one more.

In the above ni:/nih: distinction, nih: seems to have been added as an 
afterthought after realizing that reading an ni: URI aloud over the 
phone may be somewhat suboptimal because there is a need for repeated 
"upper case" - "lower case" (sure very quickly shortened to "upper" - 
"lower" and then to "up" - "low" or something similar). It is not a bad 
idea to try to make sure that IETF technology, and URIs in particular, 
are accessible to people with certain kinds of dislexya. (There are 
indeed people who have tremendous difficulties with distinguishing 
upper- and lower-case letters, and this may or may not be connected with 
other aspects of dislexya.) It is however totally unclear to this 
reviewer why this has to lead to two different URI schemes with other 
gratuitous differences.

Finding a solution is rather easy (of course, other solutions may also 
be possible): Merge the schemes, so that authority, check digit, and 
query part are all optional (an authority part and/or a query part may 
very well be very useful in human communication, and a check digit won't 
hurt when transmitted electronically) and the decimal presentation of 
the algorithm is always allowed, and use base32 
(http://tools.ietf.org/html/rfc4648) as the encoding. This leads to a 
16.6% less efficient encoding of the value part of the ni: URI, but 
given that other URI-related encodings, e.g. the %-encoding resulting 
when converting an IRI to an URI, are much less efficient, and that URI 
infrastructure these days can handle URIs with more than 1000 bytes, 
this should not be a serious problem. Also, there's a separate binary 
format (section 6) that is more compact already.



(relatively) Minor technical issues:

Section 2, "When the input to the hash algorithm is a public key value": 
Is it absolutely clear that this will work for any and all public key 
values, existing and future, and not only for what's currently around? 
After all, as far as I understand, the concept of a public key is a 
fairly general one.

"Other than in the above special case where public keys are used, we do 
not specify the hash function input here.  Other specifications are 
expected to define this.": Do you really expect that to happen? Wouldn't 
it be better limit variability here as much as possible, and to use 
media types to identify different kinds of data? This would also work 
for public keys: If there's a MIME media type for a 
SubjectPublicKeyInfo, then the fact that this media type is the 
preferred way to transfer a public key becomes an application convention 
rather than a special case in the spec. If a better way (or just another 
way) to encode/transfer public keys became popular at a later date, 
there would be no need to change the spec.

Related, in Section 3:
    The "val" field MUST contain the output of base64url encoding the
    result of applying the hash function ("alg") to its defined input,
    which defaults to the object bytes that are expected to be returned
    when the URI is dereferenced.
How do I know whether the default applies or not? The URI doesn't tell 
you. Deducing from context is a bad idea.

Section 3: "Thus to ensure interoperability, implementations SHOULD NOT 
generate URIs that employ URI character escaping": This is wrong and 
needs to be fixed. Characters such as "&", "=", "#", and "%", as well as 
ASCII characters not allowed in URIs and non-ASCII characters MUST be 
%-encoded if they appear in query parameter values in URIs (or in query 
parameter tags, which is however less likely). It would be better if the 
spec here deferred to the URI spec rather than trying to come up with 
its own rules.

Section 3: "The Named Information URI adapts the URI definition from the 
URI Generic Syntax [RFC3986].": This sounds as if this were a voluntary 
decision (and the text should be changed to avoid such an impression), 
but if you don't conform to RFC 3986 syntax, you're not an URI. This is 
the first time I have seen an URI scheme definition starting explicitly 
with the top ABNF rule from RFC 3986 
(http://tools.ietf.org/html/rfc3986#appendix-A). This is completely 
unnecessary. Just make sure your production conforms to the generic URI 
syntax, and mention all the ABNF rules from RFC3986 that you use.

Also, using the "URI" production from RFC 3986, and then silently 
dropping the #fragment part, is technically wrong. Scheme definitions 
have nothing to do with the fragment (including the question of whether 
there's a fragment or not; the semantics of fragments are defined by the 
MIME media type that you get when you resolve). This may not be 
completely clear in RFC 4395, but the IRI WG is working on an update of 
RFC 4395 where this will be made clearer (see also 
http://trac.tools.ietf.org/wg/iri/trac/ticket/126; thanks for giving me 
a chance to remember that I had to create a new issue in the tracker for 
this :-).

Section 3, ABNF:
             ni-hier-part   = "//" authority path-algval
                              / path-algval
This gives you ni://example.com/sha-256;f4OxZX_x_FO5... (//authority/) 
and ni:/sha-256;f4OxZX_x_FO5... (one slash only), but the examples show 
ni:///sha-256;f4OxZX_x_FO5... (three slashes). It looks like the ABNF 
you want is:
             ni-hier-part   = "//" authority path-algval
                            / "//" path-algval
(aligning "=" and "/" helps!)
or more simply:
             ni-hier-part   = "//" [authority] path-algval
or even more simply:
             ni-hier-part   = "//" authority path-algval
because authority can be empty; let's show this:
    authority     = [ userinfo "@" ] host [ ":" port ]
If we can show that host can be empty, we're done:
    host          = IP-literal / IPv4address / reg-name
If we can show that any one of these can be empty, we're done, let's 
pick reg-name:
    reg-name      = *( unreserved / pct-encoded / sub-delims )
* means "zero or more", thus reg-name can be empty. QED.

Section 4:
    The HTTP(S) mapping MAY be used in any context where clients without
    support for ni URIs are needed without loss of interoperability or
    functionality.
What is meant by "support for ni"? There's nowhere in the spec where 
this is explained clearly. If I were a browser maker, or writing an URI 
library,..., what would I do to support the ni scheme? The only thing I 
have come up with is to covert ni to the .well-known format, then use 
HTTP(S). In that case, the above text seems wrong, as it says that 
.well-known is used when there's no support for ni, not in order to 
support ni.

Section 5: This defines an "URL segment format". It seems to be limited 
to path componest in HTTP URIs. What if I want to use this in a query 
part, or maybe even as a fragment identifier? What if I want to use this 
as a path component in an FTP URI? Or in some other schem? It would be 
better to define the alg-val (see next point) part as such (before the 
other things), with an explanation along the following lines: "This is 
defined here both for use in other sections of this document as well as 
for use in other places where it may be helpful, such as HTTP URI path 
segments,..."

Section 5 (and Section 3): "To do this one simply uses the "alg;val" 
production": There is no "alg;val" production. Please change to "To do 
this one simply uses the <alg-val> production" and fix the ABNF in 
section 3 to
             path-algval = "/" alg-val
             alg-val     = alg ";" val
It's probably even better to fold this in with the changes to 
ni-hier-part, resulting e.g. in:
             ni-hier-part   = "//" authority "/" alg-val
             alg-val     = alg ";" val

Section 9.4: Status can be 'empty' or 'deprecated'. I suggest to replace 
'empty' with something positive, such as 'valid' or 'active'. This will 
help people who go to the IANA page and start to ask "well, it doesn't 
have a status, what does that mean". Also, I strongly suggest to add an 
additional status 'reserved', and remove the current "Reserved" hash 
name string from the entries with IDs 0 and 32.

Section 9.4: "The Suite ID value 32 is reserved for compatibility with 
ORCHIDs [RFC4843].": How will compatibility be kept for future 
changes/additions in ORCHID?



Major editorial issues:

Title and abstract (and the spec itself) use the wording "Naming 
Things". While in a security context, it may be that there is an 
implicitly assumption that there are only digital things, in a wider 
context, this is of course not true. Research on the Internet of Things 
and efforts such as the Semantic Web/Linked Data try to deal with things 
in the real world. People in these areas it will be confused by title, 
abstract, and text, unless you can show (me and) them an ni: hash for a 
person, an apple, a building, or an elephant. Therefore, while it may be 
possible to keep the catchy title, the abstract has to be fixed to avoid 
such misunderstandings, e.g. by changing "to identify a thing" to "to 
identify a digital object" or some such in the abstract, and likewise in 
the main text of the spec.

"Human-speakable" (e.g. ), "human-readable" (e.g. section title of 
section 7), and "for humans" (e.g. section title of section 9.2): These 
terms are used throughout the spec, but are imprecise and confusing. 
First, there's the problem of interpreting "for humans" in the sense of 
the previous paragraph, which of course has to be fixed. But the main 
problem is that none of the "ni:" URIs are "non-human-readable" or 
"non-human-speakable". Reading them aloud is only somewhat more tedious, 
but not at all impossible. And because the value part of the nih: form 
is 50% longer, and people quickly develop conventions for shortening 
things such as "upper case" and "lower case", it's not even clear that 
reading aloud the nih: form will necessarily take that much time. 
Therefore, I strongly recommend to change all occurrences of 
"Human-speakable", "human-readable", "for humans", and the like, to the 
more precise "more easily read out aloud by humans" or something equivalent.

Abstract and further on: "specifying URI, URL": By all URx theories (see 
e.g. http://www.w3.org/TR/uri-clarification/), URLs are a subset of 
URIs, and therefore saying that the spec specifies an URI and an URL is 
somewhat confusing. I'd propose using wording along the following lines: 
"specifying an URI scheme and a way to map these URIs to http".

Section 2, "When the input to the hash algorithm is a public key value", 
and example section: It took me a while to understand that the "public 
key" stuff was not yet another way to present a hash, and also not a way 
to mix in a public key to the hash in order to obtain some specific 
security property (I wasn't able to figure out how that would work, but 
draft-hallambaker-decade-ni-params contains something similar involving 
digital signatures and a public key). The document would be much easier 
to understand if there was a section e.g. entitled "Forms of input to 
hash", with subsections e.g. "general data", "public keys", "other stuff 
(not defined in this document)". As it is written, the relevant 
paragraphs in section 2 look like an afterthought, and it's not clear to 
what.
Also, the example section should be fixed as follows: 1) say upfront 
that there will be two examples, one for a short string and another for 
a public key. 2) Make sure both examples exercise all forms (the public 
key example seems to be pretty complete, but the "Hello World!" example 
seems to be incomplete). 3) Use the same form of presentation (either a 
table in both cases or short paragaphs in both cases.
The caption on Figure 7 is also way too unspecific.

Section 9.4: "Hash Name Algorithm Registry", and later "a new registry 
for hash algorithms as used in the name formats specified here": IANA 
will be helped tremendously if your draft comes with an 
easy-to-understand and unambiguous name for the new registry. "Hash Name 
Algorithm Registry" may be okay, but is probably not specific enough. 
The circumscription at the start of the section is definitely not good 
enough because you're not registering hash algorithms, but names of hash 
algorithms and their truncations.



Minor editorial issues:

Introduction: It would be good to have a general reference to hashing 
(for security purposes) for people not utterly familiar with the subject.

Intro: After reading the whole document, the structure of the Intro 
seems to make some sense, but it didn't on first reading (where it's 
actually more important). The main problem I was able to identify was 
that after a general outlook in paragraph 1, the Intro drops into a list 
of examples without saying what they are good for. I suggest to, after 
the sentence "This document specifies standard ways to do that to aid 
interoperability.", add a sentence along the lines: "The next few 
paragraphs give usage examples for the various ways to include a hash in 
a name or identifier as they are defined later in this document.". It 
may also make sense to further streamline the following paragraphs, so 
that it is clearer which pieces of text refer each to one of the 
"standard ways".

There are two instances of the term "binary presentation". Looking 
around, it seems that they are supposed to mean the same as "binary 
format". Please replace all instances of "binary presentation" with 
"binary format" to avoid misunderstandings and useless seach time.

Section 3: "A Named Information (ni) URI consists of the following 
components:": It would be good to know exactly where the list ended. One 
way to do this would be to say "consists of the following nine components".

Section 3: "Note that while the ni names with and without an authority 
differ syntactically, both names refer to the same object if the digest 
algorithm and value are the same.": What about cases with different 
authority? The text seems to apply by transitivity, but this may be easy 
to miss for an implementer. I suggest changing to: "Note that while ni 
names with and without an authority, and ni names with different 
authorities, differ syntactically, they all refer to the same object if 
the digest algorithm and value are the same.".

Section 3: "Consequently no special escaping mechanism is required for 
the query parameter portion of ni URIs.": Does this mean "no escaping 
mechanism at all"? Or "nothing besides %-encoding"? Or something else? 
Please clarify.

Figure 3: the "=" characters of the various rules should be aligned as 
much as possible to make it easier to scan the productions (see 
http://tools.ietf.org/html/rfc3986#appendix-A for an example).

Section 3:
             unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"
                 ;  directly from RFC 3986, section 2.3
                 ; "authority" and "pct-encoded" are also from RFC 3986
Please don't copy productions. Please don't copy half (or one-third, 
actually) of the productions you use, and reference the rest. Please 
don't say what productions you copy from where in a comment, and even 
less in a comment for an unrelated production. Please before the ABNF, 
say which productions are used from another spec.

Section 4:
    The HTTP(S) mapping MAY be used in any context where clients without
    support for ni URIs are needed without loss of interoperability or
    functionality.
This is difficult to understand. If some new functionality is proposed, 
it's usually a client *with* the new functionality that's needed, not 
one without. Also, the "without loss of interoperability or 
functionality" is unclear: Sure if ni isn't supported, there's a loss in 
interoperability. So I suggest to rewrite this as:
    The HTTP(S) mapping MAY be used in any context where clients with
    support for ni URIs are not available.
(but see also the comment in minor technical issues)

Section 6: "binary format name": Why 'name'? Why not just "binary 
format"? The later is completely clear in the context of the document or 
together with an indication of the document; for something that can be 
used independently, even "binary format name" isn't enough.

Section 6: "suite ID": The word "suite" seems out of place here. In the 
general use of the term, it refers to "a group of things forming a unit 
or constituting a collection" (see 
http://www.merriam-webster.com/dictionary/suite). A good definition that 
works for the uses I'm familiar with in digital security would be "An 
algorithm suite is a coherent collection of cryptographic algorithms for 
performing operations such as signing, encryption, generating message 
digests, and so on." 
(http://fusesource.com/docs/framework/2.4/security/MsgProtect-SOAP-SpecifyAlgorithmSuite.html; 
disclaimer: I'm in no way a SOAP fan). The use here is not for a 
collection, but for a single truncated-length variant of a single hash 
algorithm. I seriously hope you can find a better name.

Section 6: "Note that a hash value that is truncated to 120 bits will 
result in the overall name being a 128-bit value which may be useful 
with certain use-cases.": This left me really wondering: Is there 
something magic to 128 bits in computer/internet security? What are the 
"certain use cases"? Or is this just an example to make sure the reader 
got the relationships, and it could have been as well "Note that a hash 
value that is truncated to 64 bits will result in the overall name being 
a 72-bit value which may be useful with certain use-cases." (or whatever 
other value that's registered in section 9)?

Section 7: Just for the highly unfortunate case that this doesn't 
disappear, it would be very helpful if the presentation of this section 
paralleled section 3.

Section 7: "contain the ID value as a UTF-8 encoded decimal number": I'm 
an internationalization expert with a strong affection for UTF-8, but 
even for me, this should be "contain the ID value as an ASCII encoded 
decimal number".

Section 9: The registration templates refer to sections. This is fine 
for readers of the draft, but not if the template is standalone. I 
suggest using a format such as that at 
http://tools.ietf.org/html/rfc6068#section-8.1, which in draft stage may 
look e.g. like 
http://tools.ietf.org/html/draft-duerst-eai-mailto-03#section-8.1.

Section 9.3: "Assignment of Well Known URI prefix ni" and later (and 
elsewhere in the draft) "URI suffix": Are we dealing with a prefix or a 
suffix here?

Section 9.4: "This registry has five fields, the binary suite ID,...":
Better to remove the word "binary", because the actual number is decimal.

Section 9.4: "The expert SHOULD seek IETF review before approving a 
request to mark an entry as "deprecated."  Such requests may simply take 
the form of a mail to the designated expert (an RFC is not required). 
IETF review can be achieved if the designated expert sends a mail to the 
IETF discussion list.  At least two weeks for comments MUST be allowed 
thereafter before the request is approved and actioned.": I'm at a loss 
to see why asking the IETF at large is a SHOULD, but if it's done, then 
the two weeks period is a MUST.

Section 9.4: The registry initialization in Fig. 8 refers to RFC4055 
many times. But RFC 4055 does in no way define SHA-256. It looks like 
the actual spec is http://tools.ietf.org/html/rfc4055#ref-SHA2 (National 
Institute of Standards and Technology (NIST), FIPS 180-2: Secure Hash 
Standard, 1 August 2002.) I think this should be cited, in particular 
because there is a "Specification Required" requirement, and this sure 
should mean that there is a Specification for the actual algorithm, and 
not just a specification that mentions some labels. So using RFC4055 as 
a reference could be taken as creating bad precedent.

Section 9.4: "The designated expert is responsible for ensuring that the 
document referenced for the hash algorithm is such that it would be 
acceptable were the "specification required" rule applied.": Why all 
this circumscription? Why not just say something like: "The designated 
expert is responsible for ensuring that the document referenced for the 
hash algorithm meets the "specification required" rule."



Nits:

Author's list: Last time I heard about this, there was a general limit 
of 5 authors per RFC. I'm not sure whether this still exists, and what'd 
be needed to get around it, but I just wanted to point out that this may 
be a potential problem or additional work (hoops to get through).

Intro: "Since, there is no standard" -> "Since there is no standard"

Intro: "for these various purposes" -> "for these purposes" or "for 
various purposes" (the indefinite 'various' is incompatible with the 
definite 'these').

"2.  Hashes are what Count" -> "2.  Hashes are what Counts" (the former 
may look logically correct, but 'what' requires a singular verb form.

Section 2: "the left-most or most significant in network byte order N 
bits from the binary representation of the hash value" -> "the left-most 
(or most significant in network byte order) N bits from the binary 
representation of the hash value" or "the left-most N bits, or the N 
most significant bits in network byte order, from the binary 
representation of the hash value" (the current text is virtually 
unparsable).

Figure 1: The 0x notation is never explained. A short clause or pharse 
is all that would be needed, but it would be better if this were spelled 
out.

Section 3, Query Parameter separator: "The query parameter separator 
acts a separator between" -> "The query parameter separator acts *as* a 
separator between".

Section 3, Query Parameters: "A tag=value list of optional query 
parameters as are used with HTTP URLs" ->  "A tag=value list of optional 
query parameters as used with HTTP URLs" (or "A tag=value list of 
optional query parameters as they are used with HTTP URLs").

Section 4: "the object named by the ni URI will be available at the 
corresponding HTTP(S) URL" -> "the object named by the ni URI will be 
available via the corresponding HTTP(S) URL" (via stresses the point 
that this should be done via (sic) redirection)

Section 4: "so there may still be reasons to use" -> "so there can still 
be reasons to use" (better to use can because non-normative; the 
document otherwise does a good job on this)

Section 10: "Note that fact that" -> "Note the fact that", or much 
better: "Note that".


Regards,     Martin.


From stephen.farrell@cs.tcd.ie  Tue Jun  5 04:11:52 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6397221F868A; Tue,  5 Jun 2012 04:11:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.649
X-Spam-Level: 
X-Spam-Status: No, score=-102.649 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_35=0.6, J_CHICKENPOX_37=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 sqt8Pg-a9tKJ; Tue,  5 Jun 2012 04:11:49 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id D490521F8685; Tue,  5 Jun 2012 04:11:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 1F2F01714E8; Tue,  5 Jun 2012 12:11:48 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1338894705; bh=iH5g6Si9BZVv7M /ksHWD/H6cxopNpufd7jbeTUh5nUA=; b=Km9QiHWzH78ziZNpOvQtJNchRdz87D c3a/U8PbTbPiBowYGOQQy/SJk6zdqDis5v1GZeBSNsgVHl1Bl8xj8F0ZWeko1gJw gDXNpGR1dP+onxOKiCIQI+fXVjXXnVtK03dpmHGPd5mBkkdAN0WBpvl0Ql3SMGoT DbfrU0UqjhfQ8HalteXEeVyMV5YhI4R5l8SPzPL4rjMKNECgPHBOiZiCyUSuumj3 0AxjvqvAw1QRboKFx+EfSkiNSUHgWvMH3rpOKb2k4VifFrSoYmW4pWkRHPj86CGw 4tsiVjvTGkPOGscDFqZjDQiZQ/v7B+iXr9/QCHmesKNs0/oAGhg3pLXA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 21CULiXHWsKW; Tue,  5 Jun 2012 12:11:45 +0100 (IST)
Received: from [IPv6:2001:770:10:203:cc4b:866f:6fec:abaf] (unknown [IPv6:2001:770:10:203:cc4b:866f:6fec:abaf]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 568451718D8; Tue,  5 Jun 2012 12:11:42 +0100 (IST)
Message-ID: <4FCDE96E.5000109@cs.tcd.ie>
Date: Tue, 05 Jun 2012 12:11:42 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: APPSDIR review of draft-farrell-decade-ni-07
References: <4FCDD499.7060206@it.aoyama.ac.jp>
In-Reply-To: <4FCDD499.7060206@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Apps Discuss <apps-discuss@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 11:11:52 -0000

Hi Martin,

First, thanks for the speedy and thorough review. Some
good points made, some with which I strongly disagree,
but thrashing stuff like that out is part of the point
of the reviews.

On 06/05/2012 10:42 AM, "Martin J. Dürst" wrote:
> Hello everybody,
> 
> [For replies, please trim the cc list, thanks!]

Not sure what trimming you mean. I've reduced it
to ietf-discuss and apps-discuss and authors.

> 
> 
> I have been selected as the Applications Area Directorate reviewer for
> this draft (for background on appsdir, please see
> http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).
> 
> 
> 
> Please resolve these comments along with any other Last Call comments
> you may receive. Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
> 
> 
> Document: draft-farrell-decade-ni-07
> Title: Naming Things with Hashes
> Reviewer: Martin Dürst
> Review Date: 2012-06-03, 2012 (written up 2012-06-04/05)
> IETF Last Call Date: started 2012-06-04, ends 2012-07-02
> 
> 
> Summary: This draft addresses a real generic need, but the current form
> of the draft is the result of adding more and more special cases without
> a clear overall view and a firm hand to separate the wheat from the
> chaff. This shows both in the technical issues as well as in many of the
> editorial issues below. This draft is not ready for publication without
> some serious additional work, but that work is mostly straightforward
> and should be easy to complete quickly.

Wheat? Chaff? Firm hand? Hmm. Are those useful phrases here?
I disagree about 'em in any case, and you're wrong as to how
we got here and IMO quite wrong in your main technical comment.
See below for that.

> 
> Major design issue:
> 
> The draft defines two schemes, which differ only slightly, and mostly
> just gratuitously (see also editorial issues).
> These are the ni: and the nih: scheme. As far as I understand, they
> differ as follows:
>                                     ni:                nih:
> authority:                          optional           disallowed
> ascii-compatible encoding:          base64url          base16
> check digit:                        disallowed         optional
> query part:                         optional           disallowed
> decimal presentation of algorithm:  disallowed         possible
> 
> The usability of URIs is strongly influenced by the number of different
> schemes, with the smaller a number, the better. As a somewhat made-up
> example, if the original URIs had been separated into httph: for HTML
> pages and httpi: for images, or any other arbitrary subdivision that one
> can envision, that would have hurt the growth and extensibility of the
> Web. Creating new URI schemes is occasionally necessary, and the ideas
> that lead to this draft definitely seem to warrant a new scheme (*), but
> there's no reason for two schemes.
> [(*) I know people who would claim the the .well-formed http/https thing
> is completely sufficient, no new scheme needed at all.]
> 
> More specifically, if the original URIs had been separated into httpm:
> (for machines) and httph: (for humans), the Web for sure wouldn't have
> grown at the speed it did (and does) grow. In practice, there are huge
> differences in human 'speakability' for URIs (and IRIs, for that
> matter); compare e.g. http://google.com with
> http://www.google.co.jp/#sclient=psy-ab&hl=en&site=&source=hp&q=hash&oq=hash&aq=f&aqi=g4&aql=
> 
> (which I have significantly shortened to hopefully eliminate potential
> privacy issues), or compare the average mailto: URI with the average
> data: URI. However, what's important is that there never has been a
> strong dividing line between machine-only and human-only URIs or
> schemes, the division has always been very gradual. Short and mainly
> human-oriented URIs have of course been handled by machines, and on the
> other hand, very long URIs have been spoken when really necessary.
> "Speakability" has been maintained to some extent by scheme designers,
> and to some extent by "survival of the fittest" (URIs that weren't very
> speakable (or spellable/memorizable/guessable/...), and their Web sites,
> might just die out slowly).
> 
> It should also be noted that the resistance against multiple URI schemes
> may have been low because there are so many different ways to express
> hashes in the draft anyway, and one more (the nih: section is the last
> one before the examples section) didn't seem like much of a deal
> anymore. But when it comes to URIs, one less is a lot better than one more.
> 
> In the above ni:/nih: distinction, nih: seems to have been added as an
> afterthought after realizing that reading an ni: URI aloud over the
> phone may be somewhat suboptimal because there is a need for repeated
> "upper case" - "lower case" (sure very quickly shortened to "upper" -
> "lower" and then to "up" - "low" or something similar). It is not a bad
> idea to try to make sure that IETF technology, and URIs in particular,
> are accessible to people with certain kinds of dislexya. (There are
> indeed people who have tremendous difficulties with distinguishing
> upper- and lower-case letters, and this may or may not be connected with
> other aspects of dislexya.) It is however totally unclear to this
> reviewer why this has to lead to two different URI schemes with other
> gratuitous differences.
> 
> Finding a solution is rather easy (of course, other solutions may also
> be possible): Merge the schemes, so that authority, check digit, and
> query part are all optional (an authority part and/or a query part may
> very well be very useful in human communication, and a check digit won't
> hurt when transmitted electronically) and the decimal presentation of
> the algorithm is always allowed, and use base32
> (http://tools.ietf.org/html/rfc4648) as the encoding. This leads to a
> 16.6% less efficient encoding of the value part of the ni: URI, but
> given that other URI-related encodings, e.g. the %-encoding resulting
> when converting an IRI to an URI, are much less efficient, and that URI
> infrastructure these days can handle URIs with more than 1000 bytes,
> this should not be a serious problem. Also, there's a separate binary
> format (section 6) that is more compact already.

I strongly disagree with merging ni & nih. Though that clearly
could be done, it would be an error.

There was no such comment on the uri-review list and the designated
expert was happy. That review was IMO the time for such comments
and second-guessing the designated expert at this stage seems
contrary to the registration requirements. So process-wise I
think your main comment is late.

But in any case, I also think you're wrong technically in this
case.

nih *is* intended for a corner case, where humans need to speak these
URIs and was added as a direct result of requirements from the core
WG and not as an afterthought. ni URIs are not intended for that
and so there really are IMO different requirements, (esp. e.g.
checkdigit) that are best met with different schemes.

Merging ni/nih would also add more complexity for no benefit,
which would be a bad idea.

Your analogy about httpm/h may appear reasonable, but it is always
unreasonable to draw conclusions from analogies. It is also unwise
to reason from counterfactuals, which we'd also be doing if we
accepted your argument. So I find that speculation utterly useless
to be honest.

In this case, we are dealing with different requirements so this
should stay as-is.

Finally, we have (some, early,) running code that matches the
current draft and that ought also count for something when compared
to a change that would be a gratuitous dis-improvement based it
seems upon dubious argument that is also offered at the wrong
point in the process. (I'd say that gets over the level of my
disagreement here with a firm hand:-)

> (relatively) Minor technical issues:
> 
> Section 2, "When the input to the hash algorithm is a public key value":
> Is it absolutely clear that this will work for any and all public key
> values, existing and future, and not only for what's currently around?
> After all, as far as I understand, the concept of a public key is a
> fairly general one.

Yes. SPKI is good for this and is what's used elsewhere, e.g. in
dane and websec. Its the right choice and will be so long as folks
still need to map public key formats to X.509 which I expect will
be the case for many years to come. (Not that we get new public
key formats very often in any case.)

> "Other than in the above special case where public keys are used, we do
> not specify the hash function input here.  Other specifications are
> expected to define this.": Do you really expect that to happen? 

I do, yes, assuming that ni URIs get adopted. If they don't, then
its not a problem:-)

> Wouldn't
> it be better limit variability here as much as possible, and to use
> media types to identify different kinds of data? 

To be honest, I think that's another day's work. I don't know that
there's a generic solution that'd work for enough protocols. If there
were, then that could, and I think, should, be done in another RFC.

> This would also work
> for public keys: If there's a MIME media type for a
> SubjectPublicKeyInfo, then the fact that this media type is the
> preferred way to transfer a public key becomes an application convention
> rather than a special case in the spec. If a better way (or just another
> way) to encode/transfer public keys became popular at a later date,
> there would be no need to change the spec.

See above.

> 
> Related, in Section 3:
>    The "val" field MUST contain the output of base64url encoding the
>    result of applying the hash function ("alg") to its defined input,
>    which defaults to the object bytes that are expected to be returned
>    when the URI is dereferenced.
> How do I know whether the default applies or not? The URI doesn't tell
> you. Deducing from context is a bad idea.

I agree that deducing the input from context alone could be
difficult, though you would know when you got the right answer.
I think the way to handle this is for other specifications that
use ni URIs to specify the inputs.

> 
> Section 3: "Thus to ensure interoperability, implementations SHOULD NOT
> generate URIs that employ URI character escaping": This is wrong and
> needs to be fixed. Characters such as "&", "=", "#", and "%", as well as
> ASCII characters not allowed in URIs and non-ASCII characters MUST be
> %-encoded if they appear in query parameter values in URIs (or in query
> parameter tags, which is however less likely). It would be better if the
> spec here deferred to the URI spec rather than trying to come up with
> its own rules.

Can you suggest text to include? I'm always uncertain about this
kind of thing and would be very happy to take your suggestion.

> 
> Section 3: "The Named Information URI adapts the URI definition from the
> URI Generic Syntax [RFC3986].": This sounds as if this were a voluntary
> decision (and the text should be changed to avoid such an impression),

Huh? I don't get what change you'd like.

> but if you don't conform to RFC 3986 syntax, you're not an URI. This is
> the first time I have seen an URI scheme definition starting explicitly
> with the top ABNF rule from RFC 3986
> (http://tools.ietf.org/html/rfc3986#appendix-A). This is completely
> unnecessary. Just make sure your production conforms to the generic URI
> syntax, and mention all the ABNF rules from RFC3986 that you use.
> 
> Also, using the "URI" production from RFC 3986, and then silently
> dropping the #fragment part, is technically wrong. Scheme definitions
> have nothing to do with the fragment (including the question of whether
> there's a fragment or not; the semantics of fragments are defined by the
> MIME media type that you get when you resolve). This may not be
> completely clear in RFC 4395, but the IRI WG is working on an update of
> RFC 4395 where this will be made clearer (see also
> http://trac.tools.ietf.org/wg/iri/trac/ticket/126; thanks for giving me
> a chance to remember that I had to create a new issue in the tracker for
> this :-).

Again, I'm not clear what change is suggested.

> 
> Section 3, ABNF:
>             ni-hier-part   = "//" authority path-algval
>                              / path-algval
> This gives you ni://example.com/sha-256;f4OxZX_x_FO5... (//authority/)
> and ni:/sha-256;f4OxZX_x_FO5... (one slash only), but the examples show
> ni:///sha-256;f4OxZX_x_FO5... (three slashes). It looks like the ABNF
> you want is:
>             ni-hier-part   = "//" authority path-algval
>                            / "//" path-algval
> (aligning "=" and "/" helps!)
> or more simply:
>             ni-hier-part   = "//" [authority] path-algval
> or even more simply:
>             ni-hier-part   = "//" authority path-algval
> because authority can be empty; let's show this:
>    authority     = [ userinfo "@" ] host [ ":" port ]
> If we can show that host can be empty, we're done:
>    host          = IP-literal / IPv4address / reg-name
> If we can show that any one of these can be empty, we're done, let's
> pick reg-name:
>    reg-name      = *( unreserved / pct-encoded / sub-delims )
> * means "zero or more", thus reg-name can be empty. QED.

Good catch. Will craft a fix that disallows "ni:/sha-s56;..."
and forces "ni:///sha-256;..." when the authority is empty.

> 
> Section 4:
>    The HTTP(S) mapping MAY be used in any context where clients without
>    support for ni URIs are needed without loss of interoperability or
>    functionality.
> What is meant by "support for ni"? There's nowhere in the spec where
> this is explained clearly. If I were a browser maker, or writing an URI
> library,..., what would I do to support the ni scheme? The only thing I
> have come up with is to covert ni to the .well-known format, then use
> HTTP(S). In that case, the above text seems wrong, as it says that
> .well-known is used when there's no support for ni, not in order to
> support ni.

We can re-word, but personally I think its clear now. A suggestion
would be welcome.

> 
> Section 5: This defines an "URL segment format". It seems to be limited
> to path componest in HTTP URIs. What if I want to use this in a query
> part, or maybe even as a fragment identifier? What if I want to use this
> as a path component in an FTP URI? Or in some other schem? It would be
> better to define the alg-val (see next point) part as such (before the
> other things), with an explanation along the following lines: "This is
> defined here both for use in other sections of this document as well as
> for use in other places where it may be helpful, such as HTTP URI path
> segments,..."

Can do that. Good suggestion.

> 
> Section 5 (and Section 3): "To do this one simply uses the "alg;val"
> production": There is no "alg;val" production. Please change to "To do
> this one simply uses the <alg-val> production" and fix the ABNF in
> section 3 to
>             path-algval = "/" alg-val
>             alg-val     = alg ";" val
> It's probably even better to fold this in with the changes to
> ni-hier-part, resulting e.g. in:
>             ni-hier-part   = "//" authority "/" alg-val
>             alg-val     = alg ";" val

Ok.

> 
> Section 9.4: Status can be 'empty' or 'deprecated'. I suggest to replace
> 'empty' with something positive, such as 'valid' or 'active'. This will
> help people who go to the IANA page and start to ask "well, it doesn't
> have a status, what does that mean". 

Can do.

> Also, I strongly suggest to add an
> additional status 'reserved', and remove the current "Reserved" hash
> name string from the entries with IDs 0 and 32.

Huh? Wouldn't that confuse things more? IANA handles Reserved
values all the time.

> Section 9.4: "The Suite ID value 32 is reserved for compatibility with
> ORCHIDs [RFC4843].": How will compatibility be kept for future
> changes/additions in ORCHID?

Dunno actually:-) Ari might. But we can change it to just say "reserved
for compatibility with 4843"

> 
> Major editorial issues:
> 
> Title and abstract (and the spec itself) use the wording "Naming
> Things". While in a security context, it may be that there is an
> implicitly assumption that there are only digital things, in a wider
> context, this is of course not true. Research on the Internet of Things
> and efforts such as the Semantic Web/Linked Data try to deal with things
> in the real world. People in these areas it will be confused by title,
> abstract, and text, unless you can show (me and) them an ni: hash for a
> person, an apple, a building, or an elephant. Therefore, while it may be
> possible to keep the catchy title, the abstract has to be fixed to avoid
> such misunderstandings, e.g. by changing "to identify a thing" to "to
> identify a digital object" or some such in the abstract, and likewise in
> the main text of the spec.

First, I disagree that people will really be confused. I think this
is both a nit and a gratuitous one. However, I've no problem with
making that (tiny, inconsequential and by no means major:-) change to
the abstract.

> 
> "Human-speakable" (e.g. ), "human-readable" (e.g. section title of
> section 7), and "for humans" (e.g. section title of section 9.2): These
> terms are used throughout the spec, but are imprecise and confusing.

Imprecise: sure. Confusing: really? Were you really confused?

> First, there's the problem of interpreting "for humans" in the sense of
> the previous paragraph, which of course has to be fixed. But the main
> problem is that none of the "ni:" URIs are "non-human-readable" or
> "non-human-speakable". Reading them aloud is only somewhat more tedious,
> but not at all impossible. And because the value part of the nih: form
> is 50% longer, and people quickly develop conventions for shortening
> things such as "upper case" and "lower case", it's not even clear that
> reading aloud the nih: form will necessarily take that much time.
> Therefore, I strongly recommend to change all occurrences of
> "Human-speakable", "human-readable", "for humans", and the like, to the
> more precise "more easily read out aloud by humans" or something
> equivalent.

Happy to take a look. But I suspect we'll still disagree on
whether or not there's real confusion here.

> 
> Abstract and further on: "specifying URI, URL": By all URx theories (see
> e.g. http://www.w3.org/TR/uri-clarification/), URLs are a subset of
> URIs, and therefore saying that the spec specifies an URI and an URL is
> somewhat confusing. I'd propose using wording along the following lines:
> "specifying an URI scheme and a way to map these URIs to http".

Sure. Happy to make this *minor* change:-)

> 
> Section 2, "When the input to the hash algorithm is a public key value",
> and example section: It took me a while to understand that the "public
> key" stuff was not yet another way to present a hash, and also not a way
> to mix in a public key to the hash in order to obtain some specific
> security property (I wasn't able to figure out how that would work, but
> draft-hallambaker-decade-ni-params contains something similar involving
> digital signatures and a public key). The document would be much easier
> to understand if there was a section e.g. entitled "Forms of input to
> hash", with subsections e.g. "general data", "public keys", "other stuff
> (not defined in this document)". As it is written, the relevant
> paragraphs in section 2 look like an afterthought, and it's not clear to
> what.

I really don't get what's not clear there and I suspect I don't like
the suggested re-structuring but I'll take a look. Be good if you can
make a suggestion for text to add to the current structure that would
have avoided your confusion.

> Also, the example section should be fixed as follows: 1) say upfront
> that there will be two examples, one for a short string and another for
> a public key. 2) Make sure both examples exercise all forms (the public
> key example seems to be pretty complete, but the "Hello World!" example
> seems to be incomplete). 3) Use the same form of presentation (either a
> table in both cases or short paragaphs in both cases.
> The caption on Figure 7 is also way too unspecific.

I'll take a look. I entirely disagree that these are *major*
editorial changes.

> 
> Section 9.4: "Hash Name Algorithm Registry", and later "a new registry
> for hash algorithms as used in the name formats specified here": IANA
> will be helped tremendously if your draft comes with an
> easy-to-understand and unambiguous name for the new registry. "Hash Name
> Algorithm Registry" may be okay, but is probably not specific enough.
> The circumscription at the start of the section is definitely not good
> enough because you're not registering hash algorithms, but names of hash
> algorithms and their truncations.

I'll take a look.

> Minor editorial issues:
> 
> Introduction: It would be good to have a general reference to hashing
> (for security purposes) for people not utterly familiar with the subject.

Disagree. If I added that I could reasonably be asked to introduce
URIs for the security folks. Serious and pointless ratholes would ensue.

> Intro: After reading the whole document, the structure of the Intro
> seems to make some sense, but it didn't on first reading (where it's
> actually more important). The main problem I was able to identify was
> that after a general outlook in paragraph 1, the Intro drops into a list
> of examples without saying what they are good for. I suggest to, after
> the sentence "This document specifies standard ways to do that to aid
> interoperability.", add a sentence along the lines: "The next few
> paragraphs give usage examples for the various ways to include a hash in
> a name or identifier as they are defined later in this document.". It
> may also make sense to further streamline the following paragraphs, so
> that it is clearer which pieces of text refer each to one of the
> "standard ways".
> 
> There are two instances of the term "binary presentation". Looking
> around, it seems that they are supposed to mean the same as "binary
> format". Please replace all instances of "binary presentation" with
> "binary format" to avoid misunderstandings and useless seach time.
> 
> Section 3: "A Named Information (ni) URI consists of the following
> components:": It would be good to know exactly where the list ended. One
> way to do this would be to say "consists of the following nine components".

Those look reasonable. Will see if the changes work out.

> Section 3: "Note that while the ni names with and without an authority
> differ syntactically, both names refer to the same object if the digest
> algorithm and value are the same.": What about cases with different
> authority? The text seems to apply by transitivity, but this may be easy
> to miss for an implementer. I suggest changing to: "Note that while ni
> names with and without an authority, and ni names with different
> authorities, differ syntactically, they all refer to the same object if
> the digest algorithm and value are the same.".

Sure.

> Section 3: "Consequently no special escaping mechanism is required for
> the query parameter portion of ni URIs.": Does this mean "no escaping
> mechanism at all"? Or "nothing besides %-encoding"? Or something else?
> Please clarify.

I wish I knew:-) What do you think is right here? (Honestly,
input on this would be appreciated.)

> 
> Figure 3: the "=" characters of the various rules should be aligned as
> much as possible to make it easier to scan the productions (see
> http://tools.ietf.org/html/rfc3986#appendix-A for an example).

Ack.

> 
> Section 3:
>             unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"
>                 ;  directly from RFC 3986, section 2.3
>                 ; "authority" and "pct-encoded" are also from RFC 3986
> Please don't copy productions. Please don't copy half (or one-third,
> actually) of the productions you use, and reference the rest. Please
> don't say what productions you copy from where in a comment, and even
> less in a comment for an unrelated production. Please before the ABNF,
> say which productions are used from another spec.

We got contrary advice from elsewhere (can't recall where right now;-).
I'll let Barry (as sponsoring AD) just tell us his preference and go
with that if that's ok.

> Section 4:
>    The HTTP(S) mapping MAY be used in any context where clients without
>    support for ni URIs are needed without loss of interoperability or
>    functionality.
> This is difficult to understand. If some new functionality is proposed,
> it's usually a client *with* the new functionality that's needed, not
> one without. Also, the "without loss of interoperability or
> functionality" is unclear: Sure if ni isn't supported, there's a loss in
> interoperability. So I suggest to rewrite this as:
>    The HTTP(S) mapping MAY be used in any context where clients with
>    support for ni URIs are not available.

Sure.

> (but see also the comment in minor technical issues)
> 
> Section 6: "binary format name": Why 'name'? Why not just "binary
> format"? The later is completely clear in the context of the document or
> together with an indication of the document; for something that can be
> used independently, even "binary format name" isn't enough.

I don't get the problem with that.

> Section 6: "suite ID": The word "suite" seems out of place here. In the
> general use of the term, it refers to "a group of things forming a unit
> or constituting a collection" (see
> http://www.merriam-webster.com/dictionary/suite). A good definition that
> works for the uses I'm familiar with in digital security would be "An
> algorithm suite is a coherent collection of cryptographic algorithms for
> performing operations such as signing, encryption, generating message
> digests, and so on."
> (http://fusesource.com/docs/framework/2.4/security/MsgProtect-SOAP-SpecifyAlgorithmSuite.html;
> disclaimer: I'm in no way a SOAP fan). The use here is not for a
> collection, but for a single truncated-length variant of a single hash
> algorithm. I seriously hope you can find a better name.

That's a don't-care for me. I think suite is fine, but could
take other terms (so long as its not "algorithm"). Suite could
be justified since we have alg+truncation here, but like I
said I'd be fine to change, if a good suggestion is made.

> 
> Section 6: "Note that a hash value that is truncated to 120 bits will
> result in the overall name being a 128-bit value which may be useful
> with certain use-cases.": This left me really wondering: Is there
> something magic to 128 bits in computer/internet security? What are the
> "certain use cases"? Or is this just an example to make sure the reader
> got the relationships, and it could have been as well "Note that a hash
> value that is truncated to 64 bits will result in the overall name being
> a 72-bit value which may be useful with certain use-cases." (or whatever
> other value that's registered in section 9)?

Bit of both. I believe the core WG are keen to end up with a 128 bit
binary value as their preferred option.

> 
> Section 7: Just for the highly unfortunate case that this doesn't
> disappear, it would be very helpful if the presentation of this section
> paralleled section 3.

Disagree. Different requirements, different URIs, different
presentation. I don't think there's a real problem here.

> 
> Section 7: "contain the ID value as a UTF-8 encoded decimal number": I'm
> an internationalization expert with a strong affection for UTF-8, but
> even for me, this should be "contain the ID value as an ASCII encoded
> decimal number".

Fine.

> 
> Section 9: The registration templates refer to sections. This is fine
> for readers of the draft, but not if the template is standalone. I
> suggest using a format such as that at
> http://tools.ietf.org/html/rfc6068#section-8.1, which in draft stage may
> look e.g. like
> http://tools.ietf.org/html/draft-duerst-eai-mailto-03#section-8.1.

Will take a peek. Not sure I agree. (Nor disagree:-)

> Section 9.3: "Assignment of Well Known URI prefix ni" and later (and
> elsewhere in the draft) "URI suffix": Are we dealing with a prefix or a
> suffix here?

Will take a peek.

> Section 9.4: "This registry has five fields, the binary suite ID,...":
> Better to remove the word "binary", because the actual number is decimal.

Ack.

> 
> Section 9.4: "The expert SHOULD seek IETF review before approving a
> request to mark an entry as "deprecated."  Such requests may simply take
> the form of a mail to the designated expert (an RFC is not required).
> IETF review can be achieved if the designated expert sends a mail to the
> IETF discussion list.  At least two weeks for comments MUST be allowed
> thereafter before the request is approved and actioned.": I'm at a loss
> to see why asking the IETF at large is a SHOULD, but if it's done, then
> the two weeks period is a MUST.

I don't get your comment. The two weeks is a MUST already.

> 
> Section 9.4: The registry initialization in Fig. 8 refers to RFC4055
> many times. But RFC 4055 does in no way define SHA-256. It looks like
> the actual spec is http://tools.ietf.org/html/rfc4055#ref-SHA2 (National
> Institute of Standards and Technology (NIST), FIPS 180-2: Secure Hash
> Standard, 1 August 2002.) I think this should be cited, in particular
> because there is a "Specification Required" requirement, and this sure
> should mean that there is a Specification for the actual algorithm, and
> not just a specification that mentions some labels. So using RFC4055 as
> a reference could be taken as creating bad precedent.

I guess so. Good catch.

> Section 9.4: "The designated expert is responsible for ensuring that the
> document referenced for the hash algorithm is such that it would be
> acceptable were the "specification required" rule applied.": Why all
> this circumscription? Why not just say something like: "The designated
> expert is responsible for ensuring that the document referenced for the
> hash algorithm meets the "specification required" rule."

Honestly? I can't recall:-) Will change unless I do remember.

> Nits:
> 
> Author's list: Last time I heard about this, there was a general limit
> of 5 authors per RFC. I'm not sure whether this still exists, and what'd
> be needed to get around it, but I just wanted to point out that this may
> be a potential problem or additional work (hoops to get through).
> 
> Intro: "Since, there is no standard" -> "Since there is no standard"
> 
> Intro: "for these various purposes" -> "for these purposes" or "for
> various purposes" (the indefinite 'various' is incompatible with the
> definite 'these').
> 
> "2.  Hashes are what Count" -> "2.  Hashes are what Counts" (the former
> may look logically correct, but 'what' requires a singular verb form.
> 
> Section 2: "the left-most or most significant in network byte order N
> bits from the binary representation of the hash value" -> "the left-most
> (or most significant in network byte order) N bits from the binary
> representation of the hash value" or "the left-most N bits, or the N
> most significant bits in network byte order, from the binary
> representation of the hash value" (the current text is virtually
> unparsable).
> 
> Figure 1: The 0x notation is never explained. A short clause or pharse
> is all that would be needed, but it would be better if this were spelled
> out.
> 
> Section 3, Query Parameter separator: "The query parameter separator
> acts a separator between" -> "The query parameter separator acts *as* a
> separator between".
> 
> Section 3, Query Parameters: "A tag=value list of optional query
> parameters as are used with HTTP URLs" ->  "A tag=value list of optional
> query parameters as used with HTTP URLs" (or "A tag=value list of
> optional query parameters as they are used with HTTP URLs").
> 
> Section 4: "the object named by the ni URI will be available at the
> corresponding HTTP(S) URL" -> "the object named by the ni URI will be
> available via the corresponding HTTP(S) URL" (via stresses the point
> that this should be done via (sic) redirection)
> 
> Section 4: "so there may still be reasons to use" -> "so there can still
> be reasons to use" (better to use can because non-normative; the
> document otherwise does a good job on this)
> 
> Section 10: "Note that fact that" -> "Note the fact that", or much
> better: "Note that".

Those look ok or are nits in any case.

Thanks again for the thorough review even though we disagree as
to the main point.

Cheers,
Stephen.


> 
> 
> Regards,     Martin.
> 
> 
> 

From sm@elandsys.com  Mon Jun  4 10:22:08 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E519C11E8088; Mon,  4 Jun 2012 10:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2Pi4OkpL9Fpn; Mon,  4 Jun 2012 10:22:05 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C1C1121F845F; Mon,  4 Jun 2012 10:22:05 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.236.146]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q54HLkDh027717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2012 10:21:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338830521; i=@elandsys.com; bh=ZICT4SsNKoebjID3Jr4J6G6YKzLiu7w9knpVKol53QA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GftnKy+PrvXqCGP4WfDH5JM8fuYuDIXOehj3FyhecmcoqZf19MNvmb7t8GQYntb02 tPw3WrNsf/M1DlzmNhQ76ydkZ+cPOJ/QLn7IOyzfkwWQWKVa7tinvX2BMXtOhr0I/Z onhp34NwPij92ni3xE5CXsWmtKwFhapWmHxllP4A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1338830521; i=@elandsys.com; bh=ZICT4SsNKoebjID3Jr4J6G6YKzLiu7w9knpVKol53QA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1NySZBjGptjCil2uTxP6wdxAF/Uz5oJysiyReUANhxGAGVUbiscpraV77SycgwYjQ lEl+hzRcw7HwonMsLsdwWUFLvGpjgjGxCwSOIXFkmczL+xSRHK54HLORx0ExDdvlTq g7Ai5Wz2KjPlpoa9SEvjD2mV4EgaRJR5Mddr9viw=
Message-Id: <6.2.5.6.2.20120604072443.098cdc28@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 04 Jun 2012 10:00:38 -0700
To: "Richard L. Barnes" <rbarnes@bbn.com>, IESG <iesg@ietf.org>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Gen-ART Telechat review of draft-ietf-appsawg-about-uri-scheme-05
In-Reply-To: <196B9066-2934-443D-B642-997BDF57948E@bbn.com>
References: <196B9066-2934-443D-B642-997BDF57948E@bbn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Tue, 05 Jun 2012 09:29:28 -0700
Cc: gen-art@ietf.org, ietf@ietf.org, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 17:22:08 -0000

Hi Richard,

Thanks for the review.  This is an individual comment.

At 05:33 04-06-2012, Richard L. Barnes wrote:
>I wonder how useful this document is, given that the use of "about:" 
>URIs is currently very inconsistent across browsers. (See, for 
>example, <http://en.wikipedia.org/wiki/About_URI_scheme>)  Some 
>browsers also use alternative URI schemes for essentially the same 
>function ("opera:", "chrome:").  Has there been input from the 
>browser vendor community on this document?

One of the editors of draft-ietf-appsawg-about-uri-scheme-04 
affiliated with Opera Software ASA provided input about the draft.

The Wikipedia article mentions that it needs additional citations for 
verification.  Although the "about" URI scheme is well-known, it has 
never been registered.  The document describes the URI scheme and 
registers it in the "URI Schemes".  The document does not seek to 
impose any requirement.  It leaves it to browser vendors to decide 
what to do.

>4.
>The document correctly notes that "about:" URIs sometimes point to 
>sensitive data, and that browsers need to protect them.  However, 
>the document fails to specify what the threats are and how to 
>mitigate them.  It seems to me that the major risk is cross-site 
>scripting, in the sense that a remote web page might include an 
>"about:" URI (e.g., via an XMLHttpRequest) in order to access 
>sensitive data.  At a high level, then, the mitigation would be to 
>ensure that such URIs are accessible only as a result of direct user 
>action (e.g., typing in a URI) or trusted browser code (e.g., extensions).

Section 4 of draft-ietf-appsawg-about-uri-scheme-06 mentions that 
"about" URIs may be used to reference, for example, user passwords 
stored in a cache.  The document does not register such a token 
though. It leaves it to person with expertise to write the 
specification about that token to consider the security 
implications.  Adding text to discuss about cross-site scripting 
might be misconstrued as a recommendation.

Regards,
S. Moonesamy 


From sm@elandsys.com  Mon Jun  4 13:03:18 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4232621F8863; Mon,  4 Jun 2012 13:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 NSOb5R+Ft89f; Mon,  4 Jun 2012 13:03:15 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D60321F885D; Mon,  4 Jun 2012 13:03:15 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.233.69]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q54K300r028294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2012 13:03:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338840192; i=@elandsys.com; bh=jgJ4GK3RifTXHUyRTpXoKIUeVVMsZLkOutPbx2LraFI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1moC9XRmXWQTvE1mFV8KJf3y2Asihbv6cAILxHCs1fUpneGOC9B/QepKCQ5k++1ee 77O/V4dQELuMh0Ff/kZUHumnEtKgZNkdf65E8PwvhiIyoiF3hqx/Fp5E5MqnsVWeji r88T7oCuQxGkepuHazewFgd0XczJkir17Qb0DUek=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1338840192; i=@elandsys.com; bh=jgJ4GK3RifTXHUyRTpXoKIUeVVMsZLkOutPbx2LraFI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uVvSDxqOBb6gNnpXa5TwebcWH1ors65C+UmedGsmN4yqWJAEi+a1iDvyqX86BAM8k /k3tv6EoI0a0RVgimerWPXBytTPp72/LiV46RrtOjuGlmBh/udHY/vBICehBM4zwK9 xJRH6459PC5LUCwJCCoPDvME1zQJmwRuB+bYgknY=
Message-Id: <6.2.5.6.2.20120604122117.0a484fd0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 04 Jun 2012 12:59:58 -0700
To: Arthur Thisell <agthisell@yahoo.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-experiment-09.txt> (Resolution of The SPF and Sender ID Experiments) to Informational RFC
In-Reply-To: <1338836169.30418.YahooMailClassic@web125404.mail.ne1.yahoo .com>
References: <1338836169.30418.YahooMailClassic@web125404.mail.ne1.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Tue, 05 Jun 2012 09:29:43 -0700
Cc: spfbis@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 20:03:18 -0000

Hi Arthur,
At 11:56 04-06-2012, Arthur Thisell wrote:
>I have reviewed the last call draft and find it quite acceptable for 
>publication.

Thanks for the review.

>I realize I've been quite lax in following this WG lately and I 
>should posted comments earlier.  In hind sight, I doubt any comments 
>I would have made would have made any significant improvements to 
>the draft, it turned out just fine without me.
>
>That said, here are a few comments...
>
>1) It was never clear to me why the IESG declared these MARID drafts 
>as being experimental.   Besides the possible confusion between 
>interpreting records as both SPF and Sender ID, I was under the 
>impression that the IESG wasn't sure if these proposals would help 
>or hurt email in general, whether they would damage the function of 
>the DNS, and whether it was appropriate to let individual 
>submissions (the WG concluded without any approved IDs) to be other 
>than experimental or informational.  I'm not sure that there is much 
>point in speculating what the IESG thought, but this draft seems to 
>concentrate on only the SPF v Sender ID conflicts.

The second paragraph of Section 1 of draft-ietf-spfbis-experiment-09 
discusses about the publication status.

>2) I always thought that the type 99 transition plan was faulty, but 
>I could not think of anything better.   This draft glosses over some 
>key points about why it ended up with the transition plan that it did.
>
>* First, no one could come up with an example of a successful 
>transition where the original had significant deployment (like the 
>TXT records did) and the new version had no significant advantages 
>(the type 99 was exactly the same as TXT, other than theoretical 
>elegance.)  Even MX records still fall back to A records.
>
>* Jim and Harry from Microsoft expressed very strong objections to 
>any requirement that type 99 records MUST be checked.   Their 
>explanation was that apparently some MS applications used an API to 
>ask about DNS records, my impression was that this API worked 
>transparently on things like netware and their active directory and 
>such too.   No port 53 communication was done via this API, indeed, 
>port 53 was often explicitly blocked at the firewall so clients 
>couldn't even get around using this API if the wanted to.  This API 
>supported a very limited set of DNS records, TXT being one of them, 
>but had zero support for new/unknown record types.   Not only did 
>the then current version of that API have no way of querying type 99 
>records, the next version had been put into feature freeze, and the 
>version after that had no plans on adding such support.
>
>In short, if the RFCs required checking type 99 records, MS could 
>not produce implementations that could be standard compliant.  They 
>were willing to compromise on many things, but this wasn't one of them.
>
>On the other hand, people in the MARID WG objected to any 
>requirement to check TXT records, arguing that doing so would hinder 
>the transition to type 99 records since people could just publish 
>TXT records and know that they would always work.

According to the SPFBIS Charter the following is out-of-scope:

     "Revisiting past technical arguments where consensus was reached in
      the MARID working group, except where review is reasonably
      warranted based on operational experience."

The working group followed what was in the charter.

>So, the result was:
>
>* the RFC MUST NOT require checking type 99 records, or it would 
>lose support of MS.
>
>* the RFC MUST allow the checking of type 99 records, otherwise no 
>migration would be possible.
>
>* the RFC MUST NOT require checking of TXT records, or it would lose 
>support of IETF players and hinder migration.
>
>* the RFC MUST allow the checking of TXT records, otherwise you 
>would lose a large install base.
>
>I, and others, were quite aware at the time that the language put 
>into the RFC would make it so compliant implementations might not be 
>able to communicate with compliant publishers.  No one came forward 
>with better language.  I felt that as long as TXT could be used, 
>noting else was likely to matter.
>
>Hindsight is 20/20 and positions appear to have softened over the 
>years.  Things like DKIM managed to get by with much less 
>handwringing and I suspect if SPF was done today, known-bogus 
>language like this wouldn't have made it into the draft.


There were discussions about this issue on the WG mailing list and 
during last IETF meeting ( 
http://www.ietf.org/proceedings/83/minutes/minutes-83-spfbis.txt ).

The matter was noted in the Write-up:

   The discussions about the RRTYPE 99 DNS Resource Record were controversial.
   The issue was resolved.

Regards,
S. Moonesamy (as document shepherd) 


From vincent.roca@inria.fr  Tue Jun  5 07:30:46 2012
Return-Path: <vincent.roca@inria.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C885921F85EA; Tue,  5 Jun 2012 07:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.993
X-Spam-Level: 
X-Spam-Status: No, score=-109.993 tagged_above=-999 required=5 tests=[AWL=0.255, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 e3CqPBxiDtVv; Tue,  5 Jun 2012 07:30:45 -0700 (PDT)
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by ietfa.amsl.com (Postfix) with ESMTP id 7396E21F85E3; Tue,  5 Jun 2012 07:30:43 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.75,718,1330902000";  d="scan'208,217";a="146645325"
Received: from geve.inrialpes.fr ([194.199.24.116]) by mail4-relais-sop.national.inria.fr with ESMTP/TLS/AES128-SHA; 05 Jun 2012 16:30:42 +0200
Subject: Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-8--177810415
From: Vincent Roca <vincent.roca@inria.fr>
In-Reply-To: <4F4E961C.7080302@gmx.de>
Date: Tue, 5 Jun 2012 16:30:42 +0200
Message-Id: <FAA9F411-3643-48AA-A726-9EFA960E4A41@inria.fr>
References: <CB72DAA8.19D17%ietfdbh@comcast.net> <767A8227-173E-4C87-B597-E93D1882FDEF@inria.fr> <4F4E961C.7080302@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Tue, 05 Jun 2012 09:29:53 -0700
Cc: rmt-chairs@tools.ietf.org, draft-ietf-rmt-flute-revised@tools.ietf.org, rmt-ads@tools.ietf.org, ietf@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 14:30:46 -0000

--Apple-Mail-8--177810415
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hello Julian,

First of all, I need to apologize for this very late answer.

Many of your comments have already been addressed end of Feb. However
here are the few remaining open points. I wanted to let you know before =
updating
the document.


>>>> Section 3:
>>>>=20
>>>> "File name (usually, this can be concluded from the URI). In the =
above
>>>> example: "file.txt"."
>>>>=20
>>>> ...or the Content-Disposition header field (RFC 6266).
>>=20
>> VR: The sender can freely choose a solution to convey the filename. =
We
>> suggest to use the URI to that purpose. What you suggest =
(Content-Disposition)
>> is an alternative. Current text seems to be appropriate in the sense =
that:
>> 1- it only suggests one solution;
>> 2- it does not close the door, and using another solution remains =
valid;
>> I'm also a little bit confused by what RFC6266 / RFC2616 say, namely =
that
>> Content-Disposition is not part of HTTP/1.1.
>=20
> RFC 6266 has registered Content-Disposition as header field for HTTP. =
As such, it overrides anything that 2616 said about it.
>=20
> That being said; it's advisory only, but I thought it might be =
worthwhile to mention.

[VR] I've been through your RFC and agree it can be used. However I'd
prefer not to change current text since it would suggest another =
mechanism
for carrying the filename that is not part of the current FDT Schema.


>>>> XML-Schema: I believe the spec should state what to do with invalid
>>>> input. Are there extension points (like ignoring unknown elements =
in
>>>> extension namespaces)?
>>=20
>> VR: it seems reasonable, indeed. I'd like to hear other opinions.
>> What about the following text (last sentence is added)?
>>=20
>> NEW:
>>          Any valid FDT Instance MUST use the above XML Schema. This =
way
>>           FDT provides extensibility to support private attributes =
within the
>>           file description entries. Those could be, for example, the
>>           attributes related to the delivery of the file (timing, =
packet
>>           transmission rate, etc.). Unsupported private attributes =
SHOULD be
>>           silently ignored by a FLUTE receiver.
>>=20
>> =3D>  Co-authors, do you agree?
>=20
> So any undefined attributes should be ignored. What about undefined =
elements?

[VR] The XML Schema already clarifies how to behave in front of an =
undefined
element:

 <xs:any namespace=3D"##other" processContents=3D"skip"
                 minOccurs=3D"0" maxOccurs=3D"unbounded"/>

Basically, this is authorized and an XML validator will not try to check =
it.
However I have extended the text as follows:

NEW:=20

   This way FDT
   provides extensibility to support private elements and private
   attributes within the file description entries.  Those could be, for
   example, the attributes related to the delivery of the file (timing,
   packet transmission rate, etc.).  Unsupported private elements and
   attributes SHOULD be silently ignored by a FLUTE receiver.


>>>> "It is RECOMMENDED that the new attributes applied in the FDT are =
in the
>>>> format of MIME fields and are either defined in the HTTP/1.1
>>>> specification [RFC2616] or another well-known specification."
>>>>=20
>>>> As this is a normative requirement it needs to be clarified what =
header
>>>> fields are used? HTTP? MIME?
>>=20
>> VR: Sorry, I don't understand the point (my HTTP/MIME understanding
>> is probably too limited).
>=20
> HTTP header fields and MIME header fields are not the same thing. Pick =
one.

[VR] As I understand, "message header field" is the appropriate term.
See below for new text.


>>>> Also, well-known is irrelevant, we have a registry for header =
fields.
>>=20
>> VR: Right. I've added a pointer to the IANA Internet Media Type =
registry
>> and an informative reference. However I prefer to keep the "or =
another
>> well-known specification" part of the sentence, since removing it =
might
>> create issues.
>=20
> Such as?

[VR] We do not want to limit FLUTE extensibility. Removing "or another =
well-known
specification" would limit the RECOMMENDED places to define attributes =
to those
listed. Other SDOs (3GPP, ETSI, etc.) are not in the list.=20


>> NEW:
>>    It is RECOMMENDED that the new attributes applied in the FDT are =
in the
>>    format of MIME fields and are either defined in the HTTP/1.1
>>    specification [RFC2616], or another well-known specification, or =
in
>>    IANA registry[IANAmediatypes].
>=20
> "MIME fields" isn't a term used in the IETF. (see above).

[VR] Above all, I have the feeling that adding the [IANAmediatypes] =
reference to:
		http://www.iana.org/assignments/media-types/
was a big mistake. I've removed it since we are not concerned here by =
media types
but by the message header fields. So new text is:

NEW:

   It is RECOMMENDED that the new attributes applied in the FDT are in =
the
   format of message header fields and are either defined in the
   HTTP/1.1 specification [RFC2616], or another well-known
   specification, or in an IANA registry [IANAheaderfield].

with:

   [IANAheaderfields]
              IANA, "Permanent and Provisional Message Header Field
              Names registries", URL: http://www.iana.org/assignments/
              message-headers/perm-headers.html, URL: http://
              www.iana.org/assignments/message-headers/
              prov-headers.html.


>>>> 8.1:
>>>>=20
>>>> Actually, what's requested is a URN for the XML namespace
>>>> ("urn:ietf:params:xml:ns:fdt"). That's fine; I don't think the XML
>>>> schema needs to be registered. Otherwise, see
>>>> <http://tools.ietf.org/html/rfc3688#section-3.2>.
>>=20
>> VR: So we keep it as it is. That's what you mean?
>=20
> No, you need to rephrase the request. You're asking for a namespace =
name, not a schema URI.

[VR] done. We are now requesting the registry of 6 items, including:
   1. Registration of the FDT Instance XML Namespace.
   2. Registration of the FDT Instance XML Schema.
   3. Registration of the application/fdt+xml Media-Type.


>>>> 8.2:
>>>>=20
>>>> Has the media type registration been reviewed on ietf-types?
>>=20
>> VR: I cannot answer.
>> =3D>  Co-authors, can you say what has been done (or not)?

[VR] this has been done a few weeks ago. Thanks for the suggestion.


Thanks a lot for your feedback.
Cheers,

   Vincent=

--Apple-Mail-8--177810415
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello =
Julian,<div><br></div><div>First of all, I need to apologize for this =
very late answer.<br><br></div><div>Many of your comments have already =
been addressed end of Feb. However</div><div>here are&nbsp;the few =
remaining open points. I wanted to let you know before =
updating</div><div>the =
document.</div><div><br></div><div><br></div><div><div><blockquote =
type=3D"cite"><div><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Section =
3:</blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">"File =
name (usually, this can be concluded from the URI). In the =
above<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">example:=
 "file.txt"."<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">...or =
the Content-Disposition header field (RFC =
6266).<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">VR: The sender =
can freely choose a solution to convey the filename. =
We<br></blockquote><blockquote type=3D"cite">suggest to use the URI to =
that purpose. What you suggest =
(Content-Disposition)<br></blockquote><blockquote type=3D"cite">is an =
alternative. Current text seems to be appropriate in the sense =
that:<br></blockquote><blockquote type=3D"cite">1- it only suggests one =
solution;<br></blockquote><blockquote type=3D"cite">2- it does not close =
the door, and using another solution remains =
valid;<br></blockquote><blockquote type=3D"cite">I'm also a little bit =
confused by what RFC6266 / RFC2616 say, namely =
that<br></blockquote><blockquote type=3D"cite">Content-Disposition is =
not part of HTTP/1.1.<br></blockquote><br>RFC 6266 has registered =
Content-Disposition as header field for HTTP. As such, it overrides =
anything that 2616 said about it.<br><br>That being said; it's advisory =
only, but I thought it might be worthwhile to =
mention.<br></div></blockquote><div><br></div><div>[VR] I've been =
through your RFC and agree it can be used. However =
I'd</div><div>prefer&nbsp;not to change current text since it would =
suggest another mechanism</div><div>for&nbsp;carrying the filename that =
is not part of the current FDT =
Schema.</div><div><br></div><br><blockquote type=3D"cite"><div><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">XML-Schema: I believe the spec should state what to do =
with invalid<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">input. =
Are there extension points (like ignoring unknown elements =
in<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">extension =
namespaces)?<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">VR: it seems =
reasonable, indeed. I'd like to hear other =
opinions.<br></blockquote><blockquote type=3D"cite">What about the =
following text (last sentence is added)?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">NEW:<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Any valid FDT =
Instance MUST use the above XML Schema. This =
way<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FDT provides =
extensibility to support private attributes within =
the<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;file =
description entries. Those could be, for example, =
the<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;attributes =
related to the delivery of the file (timing, =
packet<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;transmission =
rate, etc.). Unsupported private attributes SHOULD =
be<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;silently =
ignored by a FLUTE receiver.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">=3D&gt; =
&nbsp;Co-authors, do you agree?<br></blockquote><br>So any undefined =
attributes should be ignored. What about undefined =
elements?<br></div></blockquote><div><br></div><div>[VR] The XML Schema =
already clarifies how to behave in front of an =
undefined</div><div>element:</div><div><br></div>&nbsp;&lt;xs:any =
namespace=3D"##other" processContents=3D"skip"<br>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;minOccurs=3D"0" =
maxOccurs=3D"unbounded"/&gt;<br><br></div><div>Basically, this is =
authorized and an XML validator will not try to check =
it.</div><div>However I have extended the text as =
follows:</div><div><br></div><div>NEW:&nbsp;</div><div><br></div><div>&nbs=
p; &nbsp;This way FDT<div>&nbsp; &nbsp;provides extensibility to support =
<b>private elements and</b> private</div>&nbsp; &nbsp;attributes within =
the file description entries.&nbsp;&nbsp;Those could be, =
for</div><div>&nbsp; &nbsp;example, the attributes related to =
the&nbsp;delivery of the file (timing,</div><div>&nbsp; &nbsp;packet =
transmission rate, etc.). &nbsp;Unsupported <b>private elements =
and</b></div><div><b>&nbsp; &nbsp;</b>attributes SHOULD be =
silently&nbsp;ignored by a FLUTE =
receiver.<div><br></div></div><div><div><br></div><blockquote =
type=3D"cite"><div><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">"It is RECOMMENDED that the new =
attributes applied in the FDT are in =
the<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">format =
of MIME fields and are either defined in the =
HTTP/1.1<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">specification [RFC2616] or another well-known =
specification."<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">As =
this is a normative requirement it needs to be clarified what =
header<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">fields =
are used? HTTP? =
MIME?<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">VR: Sorry, I =
don't understand the point (my HTTP/MIME =
understanding<br></blockquote><blockquote type=3D"cite">is probably too =
limited).<br></blockquote><br>HTTP header fields and MIME header fields =
are not the same thing. Pick =
one.<br></div></blockquote><div><br></div><div>[VR] As I understand, =
"message header field" is the appropriate term.</div><div>See =
below&nbsp;for new text.</div><div><br></div><br><blockquote =
type=3D"cite"><div><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Also, well-known is irrelevant, =
we have a registry for header =
fields.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">VR: Right. I've =
added a pointer to the IANA Internet Media Type =
registry<br></blockquote><blockquote type=3D"cite">and an informative =
reference. However I prefer to keep the "or =
another<br></blockquote><blockquote type=3D"cite">well-known =
specification" part of the sentence, since removing it =
might<br></blockquote><blockquote type=3D"cite">create =
issues.<br></blockquote><br>Such =
as?<br></div></blockquote><div><br></div><div>[VR] We do not want to =
limit FLUTE extensibility.&nbsp;Removing "or another =
well-known</div><div>specification" would limit&nbsp;the RECOMMENDED =
places to define attributes to those</div><div>listed. Other&nbsp;SDOs =
(3GPP, ETSI, etc.) are not in the =
list.&nbsp;</div><div><br></div><div><br></div><blockquote =
type=3D"cite"><div><blockquote =
type=3D"cite">NEW:<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;It is RECOMMENDED that the new attributes applied in =
the FDT are in the<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;format of MIME fields and are either defined in the =
HTTP/1.1<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;specification [RFC2616], or another well-known =
specification, or in<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;IANA =
registry[IANAmediatypes].</blockquote></div></blockquote><blockquote =
type=3D"cite"><div><br>"MIME fields" isn't a term used in the IETF. (see =
above).<br></div></blockquote><div><br></div><div>[VR] Above all, I have =
the feeling that adding the&nbsp;[IANAmediatypes] =
reference&nbsp;to:</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span><a =
href=3D"http://www.iana.org/assignments/media-types/">http://www.iana.org/=
assignments/media-types/</a></div><div>was a <b>big mistake</b>. I've =
removed it since we are not concerned here by media types</div><div>but =
by the message header fields. So new text =
is:</div><div><br></div><div>NEW:</div><div><br></div><div><div><div>&nbsp=
; &nbsp;It&nbsp;is RECOMMENDED that the new attributes applied in the =
FDT are in the</div><div>&nbsp; &nbsp;format of <b>message header =
fields</b> and are either defined in the</div><div>&nbsp; &nbsp;HTTP/1.1 =
specification [RFC2616], or another well-known</div><div>&nbsp; =
&nbsp;specification, or in an IANA registry =
<b>[IANAheaderfield]</b>.</div></div></div><div><br></div><div>with:</div>=
<div><br></div><div><div><div><div>&nbsp; =
&nbsp;[IANAheaderfields]</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; IANA, "Permanent and Provisional Message Header =
Field</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Names =
registries", URL: <a =
href=3D"http://www.iana.org/assignments/">http://www.iana.org/assignments/=
</a></div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
message-headers/perm-headers.html, URL: http://</div><div>&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a =
href=3D"http://www.iana.org/assignments/message-headers/">www.iana.org/ass=
ignments/message-headers/</a></div><div>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; =
prov-headers.html.</div><div><br></div></div><div><br></div></div></div><b=
lockquote type=3D"cite"><div><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">8.1:<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Actually, what's requested is a URN for the XML =
namespace<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">("urn:ietf:params:xml:ns:fdt"). That's fine; I don't think =
the XML<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">schema =
needs to be registered. Otherwise, =
see<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">&lt;<a =
href=3D"http://tools.ietf.org/html/rfc3688#section-3.2">http://tools.ietf.=
org/html/rfc3688#section-3.2</a>&gt;.<br></blockquote></blockquote></block=
quote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">VR: So we keep it as it is. That's what you =
mean?<br></blockquote><br>No, you need to rephrase the request. You're =
asking for a namespace name, not a schema =
URI.<br></div></blockquote><div><br></div><div>[VR] done. We are now =
requesting the registry of 6 items, including:</div><div><div>&nbsp; =
&nbsp;1. Registration of the FDT Instance XML =
Namespace.</div><div>&nbsp; &nbsp;2. Registration of the FDT Instance =
XML Schema.</div><div>&nbsp; &nbsp;3. Registration of the =
application/fdt+xml =
Media-Type.</div><div><br></div></div><br><blockquote =
type=3D"cite"><div><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">8.2:<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Has =
the media type registration been reviewed on =
ietf-types?<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">VR: I cannot =
answer.<br></blockquote><blockquote type=3D"cite">=3D&gt; =
&nbsp;Co-authors, can you say what has been done (or =
not)?</blockquote></div></blockquote><br></div><div>[VR] this has been =
done a few weeks ago. Thanks for the =
suggestion.</div><div><br></div><div><br></div><div>Thanks a lot for =
your feedback.</div><div>Cheers,</div><div><br></div><div>&nbsp; =
&nbsp;Vincent</div></div></body></html>=

--Apple-Mail-8--177810415--

From llynch@civil-tongue.net  Tue Jun  5 09:39:48 2012
Return-Path: <llynch@civil-tongue.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F283521F85A0 for <ietf@ietfa.amsl.com>; Tue,  5 Jun 2012 09:39:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 uNs1sQjiiwEq for <ietf@ietfa.amsl.com>; Tue,  5 Jun 2012 09:39:47 -0700 (PDT)
Received: from hiroshima.bogus.com (hiroshima.bogus.com [IPv6:2001:418:1::80]) by ietfa.amsl.com (Postfix) with ESMTP id 4D57721F8726 for <ietf@ietf.org>; Tue,  5 Jun 2012 09:39:47 -0700 (PDT)
Received: from hiroshima.bogus.com (localhost [127.0.0.1]) by hiroshima.bogus.com (8.14.3/8.14.3) with ESMTP id q55Gdf9C048025 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Jun 2012 09:39:42 -0700 (PDT) (envelope-from llynch@civil-tongue.net)
Received: from localhost (llynch@localhost) by hiroshima.bogus.com (8.14.3/8.14.3/Submit) with ESMTP id q55GdfAV048022; Tue, 5 Jun 2012 09:39:41 -0700 (PDT) (envelope-from llynch@civil-tongue.net)
Date: Tue, 5 Jun 2012 09:39:41 -0700 (PDT)
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hiroshima.bogus.com
To: dcrocker@bbiw.net
Subject: Re: Making the Tao a web page
In-Reply-To: <4FCC4F8F.1060800@dcrocker.net>
Message-ID: <alpine.BSF.2.00.1206050931000.33395@hiroshima.bogus.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <4FC8AFA9.1020200@inex.ie> <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com> <6.2.5.6.2.20120603145115.09cfc558@resistor.net> <4FCC4F8F.1060800@dcrocker.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 16:39:48 -0000

On Mon, 4 Jun 2012, Dave Crocker wrote:

>
>
> On 6/4/2012 12:36 AM, SM wrote:
>> At 14:33 01-06-2012, Russ Housley wrote:
>>> So, I am left with a few questions:
>>> - What is the similar forcing function if we use a wiki?
>>> - Will the number of people that can make updates eliminate the need
>>> for such a forcing function?
>>> - Who designates the editor-in-chief of the wiki?
> ...
>>   ...  Instead of discussing the above questions it is easier
>> to create an Wiki page and leave it to anyone with a tools login who
>> cares to update it.
>
>
> In effect, the wiki construct becomes a form of incrementally-updatable 
> internet draft.  For documents involving procedures rather than products, 
> this well might be a better working base than I-Ds...
>
> But with the I-D model superimposed.
>
> That is, perhaps what makes this workable is imposing an editor role onto the 
> wiki and assign responsibility for monitoring changes to the editors?  (It 
> might even be worth integrating it into the rest of the I-D administration 
> environment?)
>
> Note that this still leaves a place for published snapshots as RFCs.

I like the idea of moving towards a more lively version of the Tao and I 
agree with all those who've voiced concerns about using to open of a 
process for group editing.

I have an alternate suggestion which tries to walk the "middle way". What 
is we create the Tao as a web page with one lead editor (an a possible 
second author as needed) who is responsible for regular review and updates 
and then spin up an etherpad version of the text which can be edited by 
anyone with a tools login? The editor could then track and incorporate 
suggested changes into the canonical web page and notify the list when 
major updates occur. This would use some familiar elements of our current 
document production process and tools we already have in place and would
give the editor a way to contact those with suggested changes if further
dialogue was needed.

One question for the Tools team - can etherpad handle a long lived 
document?

- Lucy

> d/
>

From touch@isi.edu  Tue Jun  5 17:42:35 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87C5B21F85DB; Tue,  5 Jun 2012 17:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.705
X-Spam-Level: 
X-Spam-Status: No, score=-102.705 tagged_above=-999 required=5 tests=[AWL=-0.106, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 D3R-xKWdhNX0; Tue,  5 Jun 2012 17:42:34 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id DB3FB21F8602; Tue,  5 Jun 2012 17:42:34 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q560gFO9026508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Jun 2012 17:42:15 -0700 (PDT)
Message-ID: <4FCEA767.30404@isi.edu>
Date: Tue, 05 Jun 2012 17:42:15 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "C. M. Heard" <heard@pobox.com>
Subject: Re: [Int-area] Apps Directorate Review of draft-ietf-intarea-ipv4-id-update-05
References: <4FCA0E7F.7020109@cisco.com> <ACEDFEC8-1525-47B0-92D8-FB7CB1D22A0C@isi.edu> <Pine.LNX.4.64.1206022113110.17026@shell4.bayarea.net>
In-Reply-To: <Pine.LNX.4.64.1206022113110.17026@shell4.bayarea.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Apps Discussion <apps-discuss@ietf.org>, Internet Area <int-area@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 00:42:35 -0000

Hi, all,

On 6/2/2012 9:21 PM, C. M. Heard wrote:
> On Sat, 2 Jun 2012, Joe Touch wrote:
>> Hi, Eliot,
>>
>> On Jun 2, 2012, at 6:00 AM, Eliot Lear wrote:
>>
>>>
>>> Document: draft-ietf-intarea-ipv4-id-update-05
>>> Title: Updated Specification of the IPv4 ID Field
>>> Reviewer: Eliot Lear
>>> Review Date: 2 June 2012
>>> IETF Last Call Date: 31 May  2012
>>>
>>>
>>> Summary: This draft is quite well written, and is very nearly ready for publication.
>>>
>>> This draft is well written, and from the applications
>>> perspective represents an important step to improving
>>> performance and error reduction.  It uses a new requirements
>>> call-out style that I would class as experimental, but not bad.
>>> It is worth people reading this draft and deciding if they agree
>>> with Joe's approach.
>
> FWIW, I thought it was helpful.
>
>>> Major issues:
>>>
>>> None (Yay!).
>>>
>>> Minor issues:
>>>
>>> Section 4 needs to be reconciled a bit with Section 6.1.  Specifically:
>>>
>>>>   The IPv4 ID field can be useful for other purposes.
>>>
>>>
>>> And
>>>
>>>    >>  IPv4 ID field MUST NOT be used for purposes other than
>>>     fragmentation and reassembly.
>>>
>>>
>>> My suggestion is to drop the above sentence from Section 4.
>>
>> The two are not contradictory - the ID can be useful, but
>> generating it correctly is prohibitive and typically not done.
>
> After re-reading the text I agree with Eliot that it is confusing.
> Dropping the sentence in Section 4 would be fine.  Another
> possibility would be to reword it along the following lines:
>
>    Other uses have been envisioned for the IPv4 ID field.

That's much better, IMO.

>>> In Section 6.1:
>>>
>>>
>>>>     Datagram de-duplication can be accomplished using hash-based
>>>>     duplicate detection for cases where the ID field is absent.
>>>>
>>>
>>> Under what circumstances would the ID field be absent?
>>
>> Replace "absent" with "known not unique".
>
> Better, I think, would be "not known to be unique".

Sure.

>>>>     >>  Sources of non-atomic IPv4 datagrams using strong integrity checks
>>>>     MAY reuse the ID within MSL values smaller than is typical.
>>>>
>>>
>>> Is the issue really the source using strong integrity checks or
>>> the destination in this context?  What is typical?
>>
>> The onus is on the source (of non-atomic datagrams) - if it
>> includes strong integrity checks (that are presumably validated by
>> the receiver), it then has more flexibility in its generation of
>> the iD values.
>>
>>> Nit:
>>>
>>> Shouldn't Sections 3, 4, and 5, really be Sections 2.1, 2.2, and 2.3?
>>
>> Not subsections of 2, but perhaps "3, 3.1, 3.2"?
>
> That would be fine but I'm also OK with leaving the document the way
> it is (especially if it would get it into the publication queue
> faster).

I'll check. I'm not sure if it matters whether I do a rev inbetween IETF 
LC and final RFC Editor processing. If so, I'll check on this to see if 
it can be done with minimal content impact (maybe some fluff to explain 
the flow, but no semantic changes).

Joe

From touch@isi.edu  Tue Jun  5 17:46:11 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB1FB21F86B7; Tue,  5 Jun 2012 17:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level: 
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8hEsg8yX+SFg; Tue,  5 Jun 2012 17:46:10 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 4C2C921F86AA; Tue,  5 Jun 2012 17:46:10 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q560jqv7027613 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Jun 2012 17:45:52 -0700 (PDT)
Message-ID: <4FCEA840.9030204@isi.edu>
Date: Tue, 05 Jun 2012 17:45:52 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "C. M. Heard" <heard@pobox.com>
Subject: Re: [Int-area] Apps Directorate Review of draft-ietf-intarea-ipv4-id-update-05
References: <4FCA0E7F.7020109@cisco.com> <ACEDFEC8-1525-47B0-92D8-FB7CB1D22A0C@isi.edu> <Pine.LNX.4.64.1206022113110.17026@shell4.bayarea.net> <1338699237.5620.3.camel@gwz-laptop> <Pine.LNX.4.64.1206022157100.17026@shell4.bayarea.net>
In-Reply-To: <Pine.LNX.4.64.1206022157100.17026@shell4.bayarea.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Internet Area <int-area@ietf.org>, IETF Discussion <ietf@ietf.org>, Apps Discussion <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 00:46:11 -0000

On 6/2/2012 10:00 PM, C. M. Heard wrote:
> On Sun, 3 Jun 2012, Glen Zorn wrote:
>> On Sat, 2012-06-02 at 21:21 -0700, C. M. Heard wrote:
>>
>> ...
>>
>>>>> In Section 6.1:
>>>>>
>>>>>
>>>>>>     Datagram de-duplication can be accomplished using hash-based
>>>>>>     duplicate detection for cases where the ID field is absent.
>>>>>>
>>>>>
>>>>> Under what circumstances would the ID field be absent?
>>>>
>>>> Replace "absent" with "known not unique".
>>>
>>> Better, I think, would be "not known to be unique".
>>
>> Except that the two are not semantically equivalent.

Sorry - I didn't catch that. When the datagram is atomic, under the new 
rules, we would *assume* that the ID field was not unique for a 
src/dst/protocol triple within the expected time (120 seconds).

I.e., the ID field is "assumed to not be useful for such purposes", 
which might be more accurate.

Joe

>
> Indeed.  That was why I suggested the change.
>
> //cmh
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

From touch@isi.edu  Tue Jun  5 17:51:16 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AC8921F8803 for <ietf@ietfa.amsl.com>; Tue,  5 Jun 2012 17:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.693
X-Spam-Level: 
X-Spam-Status: No, score=-102.693 tagged_above=-999 required=5 tests=[AWL=-0.094, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 tPL7nyrgnlTY for <ietf@ietfa.amsl.com>; Tue,  5 Jun 2012 17:51:15 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id A961521F87FF for <ietf@ietf.org>; Tue,  5 Jun 2012 17:51:15 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q560ofGO029056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Jun 2012 17:50:41 -0700 (PDT)
Message-ID: <4FCEA961.6040508@isi.edu>
Date: Tue, 05 Jun 2012 17:50:41 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <Pine.LNX.4.64.1206022127550.17026@shell4.bayarea.net> <35224171-BE58-4875-BE3A-7EAE7BB8B18D@kumari.net>
In-Reply-To: <35224171-BE58-4875-BE3A-7EAE7BB8B18D@kumari.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "C. M. Heard" <heard@pobox.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 00:51:16 -0000

Kuari wrote:
> On Jun 3, 2012, at 12:34 AM, C. M. Heard wrote:
>> On Sat, 2 Jun 2012, Masataka Ohta wrote:
>>> Existing routers, which was relying on ID uniqueness of atomic
>>> packets, are now broken when they fragment the atomic packets.
 >>
>> Such routers were always broken.  An atomic packet has DF=0 and any
>> router fragmenting such a packet was and is non-compliant with
>> the relevant specifications (RFCs 791, 1122, 1812).
 >
> Sorry, but no….
>
> Not following the RFC != broken. Not following the RFC == non-compliant.
>
> There are numerous places where implementations do not follow the
> specs for various reasons, ranging from simply not bothering, through
> philosophical differences to customers paying for non-compliant feature X.

Vendors that "choose to ignore" (IMO, that's "violates") the specs 
rarely make clear their rationale or the consequences to users.

Regardless, as has been noted, the routers were already non-compliant 
when they ignored the flags of an atomic datagram.

Joe

From touch@isi.edu  Tue Jun  5 17:55:22 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C354C11E80AE for <ietf@ietfa.amsl.com>; Tue,  5 Jun 2012 17:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.688
X-Spam-Level: 
X-Spam-Status: No, score=-102.688 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 l8JE4lTD87u4 for <ietf@ietfa.amsl.com>; Tue,  5 Jun 2012 17:55:20 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 9373D11E80AB for <ietf@ietf.org>; Tue,  5 Jun 2012 17:55:20 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q560t7rl000553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Jun 2012 17:55:07 -0700 (PDT)
Message-ID: <4FCEAA6B.20204@isi.edu>
Date: Tue, 05 Jun 2012 17:55:07 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <Pine.LNX.4.64.1206022127550.17026@shell4.bayarea.net> <4FCBB71E.9080209@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4FCBB71E.9080209@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 00:55:22 -0000

Hi,

On 6/3/2012 12:12 PM, Masataka Ohta wrote:
> C. M. Heard wrote:
> 
>>> Existing routers, which was relying on ID uniqueness of atomic
>>> packets, are now broken when they fragment the atomic packets.
>>
>> Such routers were always broken.  An atomic packet has DF=0 and any
>> router fragmenting such a packet was and is non-compliant with
>> the relevant specifications (RFCs 791, 1122, 1812).
> 
> Thank you. I have overlooked that atomic implied DF=1.
> 
> But, then,
> 
>     >>  Sources emitting non-atomic datagrams MUST NOT repeat IPv4 ID
>     values within one MSL for a given source address/destination
>     address/protocol triple.
> 
> makes most, if not all, IPv4 hosts non compliant if MSL=2min.

This is already noted throughout this document, however there is little
impact to such non-compliance if datagrams don't persist that long.

> Worse, without hard value of MSL, it is a meaningless
> requirement. Note that MSL=2min derived from RFC793 breaks
> 150Mbps TCP.

It breaks at 6.4 Mbps for 1500 byte packets, as is already noted in the doc.

> The proper solution, IMHO, to the ID uniqueness is to request
> a destination host drop fragments from a source host after
> it receives tens (or hundreds) of packets with different IDs
> from the same source host.

That doesn't help ID uniqueness; it helps avoid fragmentation overload.
FWIW, such issues were discussed at length in the INTAREA WG when this
doc was developed.

> A source host, then, is only required to remember the
> previous ID used for each destination.

They don't do anywhere near that right now, but even if they did it
would still be prohibitive in speed (as per above).

Joe

From touch@isi.edu  Tue Jun  5 17:59:14 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFE2C21F85DB for <ietf@ietfa.amsl.com>; Tue,  5 Jun 2012 17:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.684
X-Spam-Level: 
X-Spam-Status: No, score=-102.684 tagged_above=-999 required=5 tests=[AWL=-0.085, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lX4+7CZ4qEVc for <ietf@ietfa.amsl.com>; Tue,  5 Jun 2012 17:59:14 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 774E421F85D9 for <ietf@ietf.org>; Tue,  5 Jun 2012 17:59:14 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q560wxpr001657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Jun 2012 17:58:59 -0700 (PDT)
Message-ID: <4FCEAB53.2020504@isi.edu>
Date: Tue, 05 Jun 2012 17:58:59 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4FC97E57.6070505@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 00:59:15 -0000

Some further points...

On 6/1/2012 7:45 PM, Masataka Ohta wrote:
> Joe Touch wrote:
> 
>>> Existing routers, which was relying on ID uniqueness of atomic
>>> packets, are now broken when they fragment the atomic packets.
> 
>> The recommendation in this doc - that such sources MUST rate-limit - is
>> to comply with the ID uniqueness requirements already in RFC791 that
>> this doc does not deprecate - e.g., its use to support fragmentation.
> 
> It means that the uniqueness requirements must be loosened.

This document does that for atomic datagrams. We discussed whether it
was realistic to change the requirements for non-atomic datagrams in
INTAREA, and decided it wasn't.

> Another example is that, when route changes, routers
> fragmenting atomic packets may change, which means rate
> limiting does not guarantee ID uniqueness.

Rate limiting (of non-atomic datagrams) is at the source, which ensures
ID uniqueness regardless of where they are fragmented.

Routers already should not be fragmenting atomic datagrams, as has been
noted.

Joe

From lars@netapp.com  Wed Jun  6 00:14:01 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 359BC11E808C; Wed,  6 Jun 2012 00:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.673
X-Spam-Level: 
X-Spam-Status: No, score=-9.673 tagged_above=-999 required=5 tests=[AWL=-0.473, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
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 sDV93pqV3fWn; Wed,  6 Jun 2012 00:14:00 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 52E1511E8094; Wed,  6 Jun 2012 00:14:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.75,722,1330934400";  d="p7s'?scan'208";a="653552724"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 06 Jun 2012 00:13:45 -0700
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q567Diun013934; Wed, 6 Jun 2012 00:13:45 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.15]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0298.004; Wed, 6 Jun 2012 00:13:44 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: IETF-Discussion list <ietf@ietf.org>, "84attendees@ietf.org" <84attendees@ietf.org>
Subject: Fwd: [IRTF-Announce] Applied Networking Research Prize 2012 presentation	at IETF-84
Thread-Topic: [IRTF-Announce] Applied Networking Research Prize 2012 presentation	at IETF-84
Thread-Index: AQHNQ7PnpWmQ7NxxXUiKOskh5IpvCA==
Date: Wed, 6 Jun 2012 07:13:43 +0000
Message-ID: <B8834A3E-66DF-4E3C-B30B-6D2C2A8FFD7F@netapp.com>
References: <414D17CA-4547-4884-AB40-7F977D1A476E@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_EFC619D0-2075-4113-994D-C68C6CF4B685"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 07:14:01 -0000

--Apple-Mail=_EFC619D0-2075-4113-994D-C68C6CF4B685
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1



Begin forwarded message:

> From: "Eggert, Lars" <lars@netapp.com>
> Subject: [IRTF-Announce] Applied Networking Research Prize 2012 =
presentation at IETF-84
> Date: June 5, 2012 16:10:58 GMT+02:00
> To: "irtf-announce@irtf.org" <irtf-announce@irtf.org>, =
"irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
> Reply-To: "anrp@irtf.org" <anrp@irtf.org>
>=20
>=20
> Hi,
>=20
> we are extremely pleased to report that for the 2012 award period of
> the Applied Networking Research Prize (ANRP), 20 eligible nominations
> were received. Each submission was reviewed by 5-7 members of the
> selection committee according to a diverse set of criteria, including
> scientific excellence and substance, timeliness, relevance, and
> potential impact on the Internet.
>=20
> Based on this review, three submissions were awarded an Applied
> Networking Research Prize in 2012. One of these submissions will be
> presented at IETF-84 in Vancouver, Canada, and two of them will be
> presented at IETF-85 in Atlanta, USA. The award for IETF-84 goes to:
>=20
> *** Alberto Dainotti *** for his research into Internet communication
> disruptions due to filtering:
>=20
>  Alberto Dainotti, Claudio Squarcella, Emile Aben, K.C.  Claffy,
>  Marco Chiesa, Michele Russo and Antonio Pescap=E9.  Analysis of
>  Country-wide Internet Outages Caused by Censorship. Proc. ACM
>  SIGCOMM/SIGMETRICS Internet Measurement Conference (IMC), November
>  2011, Berlin, Germany.
>=20
> Alberto has been invited to present his findings in the IRTF Open
> Meeting during IETF-84, July 29 - August 3, 2012 in Vancouver, Canada.
> Join him there!
>=20
> The other two prize winners of the 2012 ANRP will be announced before
> IETF-85 in Atlanta, USA.
>=20
> The call for ANRP nominations for the 2013 awards cycle will open in
> the fall of 2012. Read more about the ANRP at http://irtf.org/anrp.
> Please subscribe to the IRTF-Announce mailing list in order to receive
> future calls for ANRP nominations and join ISOC to stay informed of
> other networking research initiatives:
>=20
>  http://irtf.org/mailman/listinfo/irtf-announce
>  http://isoc.org/join
>=20
> Regards,
>=20
> Lars Eggert, IRTF Chair            http://irtf.org/anrp
> Mat Ford, Internet Society         http://isoc.org/research
>=20
> --
>=20
> 2012 ANRP Selection Committee
>=20
> Mark Allman, ICIR
> Marcelo Bagnulo, UC3M
> Lou Berger, LabN
> Olivier Bonaventure, UCL Louvain
> Ross Callon, Juniper
> Lars Eggert, NetApp
> Olivier Festor, INRIA
> Mat Ford, ISOC
> Lisandro Granville, UFRGS
> Andrei Gurtov, HIIT
> Dan Massey, Colorado State
> Al Morton, AT&T Laboratories
> J=F6rg Ott, Aalto University
> Colin Perkins, University of Glasgow
> Stefano Previdi, Cisco
> J=FCrgen Sch=F6nw=E4lder, Jacobs University Bremen
> Lixia Zhang, UCLA


--Apple-Mail=_EFC619D0-2075-4113-994D-C68C6CF4B685
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDYwNjA3MTM0NlowIwYJKoZIhvcNAQkEMRYEFNDY
PZySGpdUaN1x8iK4ClLa4QQOMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAAqRSs6j
iKLtpxy4Wh0WBWRih3LfQcKxOPkUQuS+jObM6aSI5vo+pwx6jq8wN6fAnvaZ40xUsNDtQr2h0Ip4
CzslS4j65yk4jmyb8YTor20KMkx/q2VLX1xPygqCHMk/j0zgT9/qSmkkKyN4azWnu9WqCXruCXaQ
y91nxVhByUwVsa81L0zEttZIf69ou7ety+elGjhxrQvnarwe54LiAC/KsYzXdnhSGHUgVN5uS9IF
9NgFNIXUA18+Pl/BZt6Pa7S8UMb0T35P3q8W7Yl521HGV3KjoONkXv5eEt9ZvR/wa5EUrsf9T8nL
m+M5+mZ2Mk3yA9v1PvZqa4TxaOxUU7AAAAAAAAA=

--Apple-Mail=_EFC619D0-2075-4113-994D-C68C6CF4B685--

From mohamed.boucadair@orange.com  Wed Jun  6 05:05:00 2012
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4EF421F85A3; Wed,  6 Jun 2012 05:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 deaR80vFPz6J; Wed,  6 Jun 2012 05:05:00 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id AAA0221F85A1; Wed,  6 Jun 2012 05:04:59 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id C088132458A; Wed,  6 Jun 2012 14:04:58 +0200 (CEST)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id A451A4C017; Wed,  6 Jun 2012 14:04:58 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Wed, 6 Jun 2012 14:04:57 +0200
From: <mohamed.boucadair@orange.com>
To: "ietf@ietf.org" <ietf@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Date: Wed, 6 Jun 2012 14:04:55 +0200
Subject: RE: Last Call: <draft-ietf-6man-lineid-05.txt> (The Line Identification	Destination Option) to Experimental RFC
Thread-Topic: Last Call: <draft-ietf-6man-lineid-05.txt> (The Line Identification	Destination Option) to Experimental RFC
Thread-Index: Ac1CXRFC6OkRFF7HRc+8+F8rviRB6ABegtJQ
Message-ID: <94C682931C08B048B7A8645303FDC9F36E32ED1AC0@PUEXCB1B.nanterre.francetelecom.fr>
References: <20120604141855.24802.66473.idtracker@ietfa.amsl.com>
In-Reply-To: <20120604141855.24802.66473.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.6.6.110315
X-Mailman-Approved-At: Wed, 06 Jun 2012 08:53:32 -0700
Cc: DUREL Sophie OLNC/NAD/TIP <sophie.durel@orange.com>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 12:05:01 -0000

Dear Suresh, all,

Even if the document includes several warnings about the unreliability of a=
n RS-based mechanism, I suggest to add a pointer to the following document:
http://tools.ietf.org/html/draft-dec-6man-rs-access-harmful-00.=20

The document can be cited as an informative reference.

Thanks.=20

Cheers,
Med
=20

>-----Message d'origine-----
>De : ietf-announce-bounces@ietf.org=20
>[mailto:ietf-announce-bounces@ietf.org] De la part de The IESG
>Envoy=E9 : lundi 4 juin 2012 16:19
>=C0 : IETF-Announce
>Cc : ipv6@ietf.org
>Objet : Last Call: <draft-ietf-6man-lineid-05.txt> (The Line=20
>Identification Destination Option) to Experimental RFC
>
>
>The IESG has received a request from the IPv6 Maintenance WG (6man) to
>consider the following document:
>- 'The Line Identification Destination Option'
>  <draft-ietf-6man-lineid-05.txt> as Experimental RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2012-06-18. Exceptionally,=20
>comments may be
>sent to iesg@ietf.org instead. In either case, please retain the
>beginning of the Subject line to allow automated sorting.
>
>Abstract
>
>
>   In Ethernet based aggregation networks, several subscriber premises
>   may be logically connected to the same interface of an edge router.
>   This document proposes a method for the edge router to identify the
>   subscriber premises using the contents of the received Router
>   Solicitation messages.  The applicability is limited to broadband
>   network deployment scenarios where multiple user ports are mapped to
>   the same virtual interface on the Edge Router.
>
>
>
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-ietf-6man-lineid/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-ietf-6man-lineid/ballot/
>
>
>No IPR declarations have been submitted directly on this I-D.
>
>
>=

From sm@resistor.net  Wed Jun  6 14:47:34 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBF311E80AC for <ietf@ietfa.amsl.com>; Wed,  6 Jun 2012 14:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level: 
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 UfXMZe4tvrnT for <ietf@ietfa.amsl.com>; Wed,  6 Jun 2012 14:47:32 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BACD11E80A1 for <ietf@ietf.org>; Wed,  6 Jun 2012 14:47:31 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q56LlQmd010512; Wed, 6 Jun 2012 14:47:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1339019251; i=@resistor.net; bh=v+dH7rssrDKFf8wCSmgkeTcpxnb+5q+jaBiNOMxEZuk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UgHKSWqJyX3hXg8cjo1f7hrVxQYo6fnb4Dz5/6DDduRPOeuKY+yjXsUfijG3WSskM vclWnkq3Dwcr1tuH/GVKXbN4YrE5d2tforuGTDAD+iUG9bs4dSLswwftz7Uy47evag BAxyTjo1sjd/RW7qgcYGQfYFbYvzCVvNHBZAfhq8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1339019251; i=@resistor.net; bh=v+dH7rssrDKFf8wCSmgkeTcpxnb+5q+jaBiNOMxEZuk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=r4qXHJu+QHOlOabGM3iwz4saL53x1G7vJdRwPwGzAMG+AzPakXRXYu/9cn6QRYpZS HawdfjFWwxlby/8qWZq0+yFNd0ofabttcjxA170H3AMirrmmDns1SYmiWhWQ4GJK6A HDy568zbJ4pT+UizjfGqV7DBsE9lC4SFCbGAgq7U=
Message-Id: <6.2.5.6.2.20120605113303.0aa1b028@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 06 Jun 2012 14:39:36 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-tunneling-02.txt> (Tunneling of SMTP Message Transfer Priorities) to Experimental RFC
In-Reply-To: <20120604200531.8859.1367.idtracker@ietfa.amsl.com>
References: <20120604200531.8859.1367.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-melnikov-smtp-priority-tunneling@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 21:47:34 -0000

At 13:05 04-06-2012, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Tunneling of SMTP Message Transfer Priorities'
>   <draft-melnikov-smtp-priority-tunneling-02.txt> as Experimental RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the

In the Introduction section:

Typo: scenarious.

In Section 3.1:

   "This specification inserts the following between steps 3 and 4 in
    Section 4.1 of [SMTP-PRIORITY]:"

The specification would be updating draft-melnikov-smtp-priority 
according to the above.

  "3b.  In absence of both the MT-PRIORITY MAIL FROM parameter and the
         MT-Priority header field, other message header fields, such as
         Priority [RFC2156] and X-Priority, MAY be used for determining
         the priority under this "Priority Message Handling" SMTP
         extension.  But note that the Importance [RFC2156] header field
         MUST NOT be used for determining the priority under this
         "Priority Message Handling" SMTP extension, as it has different
         semantics: the Importance header field is aimed at the user
         recipient and not at the nodes responsible for transferring the
         message."

X-Priority, for example, is undocumented.  If I understood the above 
correctly, the MTA chooses some higher priority when it sees any of 
these header fields.

In Section 7:

   "Thus it is important to ensure that an MTA receiving a message
    containing the MT-Priority header field can trust that it
    was set by an authorized agent.  Such trust can be realized, for
    example, by using DKIM Section 7.1 to sign the MT-Priority header
    field value, S/MIME, or by keeping a list of trusted senders (e.g.
    within a close environment)."

I don't see how DKIM can be used to ensure that the header field was 
set by an authorized agent.  I assume that any SMTP client within the 
(DKIM) signing domain could generate a MT-Priority header field as I 
don't know the DKIM signing policy.  As an example, I consider that 
msg-id 3D9B1776-6DFD-4B80-97C6-FA8774DB7BA9@ietf.org as was generated 
by an authorized agent on behalf of the IETF Chair but I would not 
describe it as trusted.

   "Message Submission Agents MUST implement a policy that only allows"

I suggest using the same text as in draft-melnikov-smtp-priority.

   "To protect MT-Priority header field from modification or insertion,
    MUAs, MSAs and MTAs inserting it into messages SHOULD use message
    header protection mechanism such as DKIM [RFC6376]."

I read Section 7.1 as a case for not following the above 
recommendation.  Any attempt to change priority means breaking the 
DKIM signature.

I am not proposing text to avoid a significant rewrite of the proposal.

Regards,
-sm  


From jonathan.rees@gmail.com  Wed Jun  6 13:33:42 2012
Return-Path: <jonathan.rees@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DF4021F8673 for <ietf@ietfa.amsl.com>; Wed,  6 Jun 2012 13:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 vct0Dy2GRPdX for <ietf@ietfa.amsl.com>; Wed,  6 Jun 2012 13:33:40 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id E40CB21F8589 for <ietf@ietf.org>; Wed,  6 Jun 2012 13:33:37 -0700 (PDT)
Received: by dacx6 with SMTP id x6so9164308dac.31 for <ietf@ietf.org>; Wed, 06 Jun 2012 13:33:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=cmawBQPPg2p2HLTCFl0N7BdsXX6V12ONx8I1a/fiJWk=; b=bupL4+YWADyNwCedhB2pZNRn7j4QF0INL72rIWEBf/nSRCoaGHWZ/lXvL42lOaisT/ I6/VFfMZ7YTX1U0BHeMY36b/QemUUkh/Bh9n1y/vEwIY0HikJwCQPwWZcw8/yGiKQTzM YHJBvja7sphIQoqlQzQiah/1NhcAHa/jStiuq7LizIvCH7rO0A9yEwfo4krfiuMY2jQ1 6Jle7qxxiCQ40zOY1iuznO/OhqeOLE9YwugAdv10TAc10tSZcS+wxhe6wFyz6NPiGYw/ QPrSPboRpY1Ty4xcdAGD9+ja6fTlb4ZbWd8WyopRGSjtjEARceJDOB7GCOXS3tr2+sd3 Pdyw==
MIME-Version: 1.0
Received: by 10.68.216.2 with SMTP id om2mr776781pbc.26.1339014816795; Wed, 06 Jun 2012 13:33:36 -0700 (PDT)
Sender: jonathan.rees@gmail.com
Received: by 10.143.5.7 with HTTP; Wed, 6 Jun 2012 13:33:36 -0700 (PDT)
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com>
Date: Wed, 6 Jun 2012 16:33:36 -0400
X-Google-Sender-Auth: kKalcCONY0IoUFYr8ZxfQActrvw
Message-ID: <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
From: Jonathan A Rees <rees@mumble.net>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 07 Jun 2012 08:39:27 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 20:33:42 -0000

As requested I am sending comments on this last call draft to
ietf@ietf.org. I sent them to the authors on 6 May but received no
reply.

Jonathan Rees


---------- Forwarded message ----------
From: Jonathan A Rees <rees@mumble.net>
Date: Sun, May 6, 2012 at 7:57 PM
Subject: comments on http://tools.ietf.org/html/draft-farrell-decade-ni-06
To: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba
<barryleiba@computer.org>, "S. Farrell" <stephen.farrell@cs.tcd.ie>,
"P. Hallam-Baker" <pbaker@verisign.com>

Here are some opinions on
http://tools.ietf.org/html/draft-farrell-decade-ni-06 :

I think this URI scheme would be a welcome addition to web
architecture. Wide review should be sought, because this might become
quite important and if there are problems they will be very difficult
to fix later.

I think using .well-known is a good idea.

I think integration into the ecosystem, such as browser support,
should be anticipated; for this reason I think content type should be
elevated from an 'optional feature' to a 'required feature'.

[i.e. conformant implementations must support it, even if providing
the content type in the URI is itself optional.]

If you
don't do this, you are just encouraging sniffing and privilege
escalation attacks. Sniffing would be a big step backwards. Better to
do what the data: scheme does and say that there is a default content
type of, say, text/plain, and that otherwise the content type ought to
be specified in the URI.

Content-type privilege escalation risk (and incorrect sniffing risk)
should be mentioned in the security considerations section in any
case.

Maybe the risk that the host used for retrieval might be spoofing the
content-type (by providing a bogus content-type in an HTTP response)
should also be mentioned. (A possible design would be to put the
content-type (and maybe other headers like Expires:?) in the hashed
content, to be pulled out into the HTTP response when the content is
served by an http server and then checked by the client, but I
understand that this would be a tooling headache.)

(I don't understand why you want to separate the 'optional' features
into a separate spec. This made me miss the ct=3D feature entirely at
first.)

I think the documentation should say that the hash and content type
together identify the resource, and that because the content can be
verified, the resource can be sought (using the .well-known path, or
any other path for that matter) from any source that the client thinks
might have it. The primary and alternate domain name(s), and 'wrapped'
URLs, are only provided as hints.

I agree with other commenters on the peculiarity of using // to
provide the location hint since the named host is not being trusted as
an authority. I don't understand why the 'primary' location isn't just
encoded in the query, just like the alternate domain(s) and "wrapped
URL(s)". =A0This would have the nice property that you can put the
identifying parts (i.e. hash and content type) first, and the less importan=
t
location hints parts all together after the identification. The various
location hints (whether primary or secondary) would go together and
their similarity would be clearer.

(Unless I'm misunderstanding something and the part after the //
actually has status other than a hint?  That would seem to defeat
the purpose.)

Jonathan

From stephen.farrell@cs.tcd.ie  Thu Jun  7 08:43:12 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B2A21F8894 for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 08:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 1WIQAcNp7HPM for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 08:43:10 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 3B88921F8882 for <ietf@ietf.org>; Thu,  7 Jun 2012 08:43:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 7D7951714E6; Thu,  7 Jun 2012 16:43:09 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339083789; bh=GlDl/E9LkoEIuT dI5xf3E6zy7mK1dfFe7dr1rtNTy8E=; b=NrJ51XpZ9SVFsOfZk7kIn/FUYp6SU0 PoGT8cNBKmObniDXggRWXTZDhmG3F3RxqNf4fZNjw9i+wv/aZfVub5mhB3eu3RuN ff70qSB9y3geaorAYaZdjZLg2tup5b1i/+VZZW13BkGmUGr1P6p0KRlziQqiOOy8 c7+xzMlx4Pw6E1HtgrlNT9Omdp5QENp8FmW6G6z6vdTlD1UJvOsP/KdDxsLQUqUR UKZyZb4QT63T+tJcS3aHv0Dr0TiIlO/r+1A9WqBPZDMzeJDyv5k3xRM8YuVoJc6g KINBat5FSIx0OOd7sKMZGm2OjKbP6kixks1Vek+DOwGbFkwsHQAKcF6w==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id iehKQcucwrXY; Thu,  7 Jun 2012 16:43:09 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.41.12.146]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id DCE4F1714E1; Thu,  7 Jun 2012 16:43:08 +0100 (IST)
Message-ID: <4FD0CC0C.5030305@cs.tcd.ie>
Date: Thu, 07 Jun 2012 16:43:08 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Jonathan A Rees <rees@mumble.net>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>
In-Reply-To: <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 15:43:12 -0000

On 06/06/2012 09:33 PM, Jonathan A Rees wrote:
> As requested I am sending comments on this last call draft to
> ietf@ietf.org. I sent them to the authors on 6 May but received no
> reply.

Oh crap - so you did. Apologies for missing that. In the
middle of something now but will get back soon,

Cheers,
S

> 
> Jonathan Rees
> 
> 
> ---------- Forwarded message ----------
> From: Jonathan A Rees <rees@mumble.net>
> Date: Sun, May 6, 2012 at 7:57 PM
> Subject: comments on http://tools.ietf.org/html/draft-farrell-decade-ni-06
> To: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba
> <barryleiba@computer.org>, "S. Farrell" <stephen.farrell@cs.tcd.ie>,
> "P. Hallam-Baker" <pbaker@verisign.com>
> 
> Here are some opinions on
> http://tools.ietf.org/html/draft-farrell-decade-ni-06 :
> 
> I think this URI scheme would be a welcome addition to web
> architecture. Wide review should be sought, because this might become
> quite important and if there are problems they will be very difficult
> to fix later.
> 
> I think using .well-known is a good idea.
> 
> I think integration into the ecosystem, such as browser support,
> should be anticipated; for this reason I think content type should be
> elevated from an 'optional feature' to a 'required feature'.
> 
> [i.e. conformant implementations must support it, even if providing
> the content type in the URI is itself optional.]
> 
> If you
> don't do this, you are just encouraging sniffing and privilege
> escalation attacks. Sniffing would be a big step backwards. Better to
> do what the data: scheme does and say that there is a default content
> type of, say, text/plain, and that otherwise the content type ought to
> be specified in the URI.
> 
> Content-type privilege escalation risk (and incorrect sniffing risk)
> should be mentioned in the security considerations section in any
> case.
> 
> Maybe the risk that the host used for retrieval might be spoofing the
> content-type (by providing a bogus content-type in an HTTP response)
> should also be mentioned. (A possible design would be to put the
> content-type (and maybe other headers like Expires:?) in the hashed
> content, to be pulled out into the HTTP response when the content is
> served by an http server and then checked by the client, but I
> understand that this would be a tooling headache.)
> 
> (I don't understand why you want to separate the 'optional' features
> into a separate spec. This made me miss the ct= feature entirely at
> first.)
> 
> I think the documentation should say that the hash and content type
> together identify the resource, and that because the content can be
> verified, the resource can be sought (using the .well-known path, or
> any other path for that matter) from any source that the client thinks
> might have it. The primary and alternate domain name(s), and 'wrapped'
> URLs, are only provided as hints.
> 
> I agree with other commenters on the peculiarity of using // to
> provide the location hint since the named host is not being trusted as
> an authority. I don't understand why the 'primary' location isn't just
> encoded in the query, just like the alternate domain(s) and "wrapped
> URL(s)".  This would have the nice property that you can put the
> identifying parts (i.e. hash and content type) first, and the less important
> location hints parts all together after the identification. The various
> location hints (whether primary or secondary) would go together and
> their similarity would be clearer.
> 
> (Unless I'm misunderstanding something and the part after the //
> actually has status other than a hint?  That would seem to defeat
> the purpose.)
> 
> Jonathan
> 
> 

From stephen.farrell@cs.tcd.ie  Thu Jun  7 12:15:17 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D990511E80A3 for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 12:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 n4kvyIMwzKud for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 12:15:17 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 9D05311E809D for <ietf@ietf.org>; Thu,  7 Jun 2012 12:15:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id DA05C1714E2; Thu,  7 Jun 2012 20:15:15 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339096515; bh=EDt0KwCPXitGxe DC0jOO2XVChZVeJ9c4iqmK0EIFdZs=; b=t0j003sJEMpeGg8nC36og98uTfQcmt 6Suf9Mc1hGmC7f3kLK5nYokqb+D2nNZwfe16HqbEba98Rq/r8qRbUMc1cm9l/lkL 97e83xymO5ZyOLbgpPk3k5IZCMinsP0QqHJhWovIKAG6e8AQZU8OWbe7o01oFTZG mMtvl0E8WIk6rCHNhJlJhaRZtQ9sCSSrDtiu2uixaqE2f8zmg6zMdxX63I58bCdr rFdZ33hHxgoEstjzeTFXGuMe1CG1/HrA6WKB1tdOeHlMAup4e1irOwC7WsYae89J gMzGldMlQQmZv2btkDSld5bvBspliXVp35vlZD3JP6DVGPb9j7fRQhdg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id Kg-AO03m77q3; Thu,  7 Jun 2012 20:15:15 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.41.12.146]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 2C9AB1714E1; Thu,  7 Jun 2012 20:15:14 +0100 (IST)
Message-ID: <4FD0FDC2.2090802@cs.tcd.ie>
Date: Thu, 07 Jun 2012 20:15:14 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Jonathan A Rees <rees@mumble.net>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>
In-Reply-To: <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 19:15:18 -0000

On 06/06/2012 09:33 PM, Jonathan A Rees wrote:
> As requested I am sending comments on this last call draft to
> ietf@ietf.org. I sent them to the authors on 6 May but received no
> reply.

Once again, sorry about that. No idea why I missed responding,
your mail is in my client even. Ah well.

> 
> Jonathan Rees
> 
> 
> ---------- Forwarded message ----------
> From: Jonathan A Rees <rees@mumble.net>
> Date: Sun, May 6, 2012 at 7:57 PM
> Subject: comments on http://tools.ietf.org/html/draft-farrell-decade-ni-06
> To: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba
> <barryleiba@computer.org>, "S. Farrell" <stephen.farrell@cs.tcd.ie>,
> "P. Hallam-Baker" <pbaker@verisign.com>
> 
> Here are some opinions on
> http://tools.ietf.org/html/draft-farrell-decade-ni-06 :
> 
> I think this URI scheme would be a welcome addition to web
> architecture. Wide review should be sought, because this might become
> quite important and if there are problems they will be very difficult
> to fix later.
> 
> I think using .well-known is a good idea.
> 
> I think integration into the ecosystem, such as browser support,
> should be anticipated; for this reason I think content type should be
> elevated from an 'optional feature' to a 'required feature'.
> 
> [i.e. conformant implementations must support it, even if providing
> the content type in the URI is itself optional.]

I could certainly live with that, and I suspect my co-authors too,
but I'd need to ask 'em. However, we'd like to see more support for
it before doing that. If we only hear from you on this, then I
think leaving it in the other draft would be right. (See below
for why we want to keep that draft.) I guess others have a few
weeks to chime in on this.

> If you
> don't do this, you are just encouraging sniffing and privilege
> escalation attacks. Sniffing would be a big step backwards. Better to
> do what the data: scheme does and say that there is a default content
> type of, say, text/plain, and that otherwise the content type ought to
> be specified in the URI.
> 
> Content-type privilege escalation risk (and incorrect sniffing risk)
> should be mentioned in the security considerations section in any
> case.

Would appreciate text if you can offer some. (Always happy to
make the sec. cons. bit better.)

> Maybe the risk that the host used for retrieval might be spoofing the
> content-type (by providing a bogus content-type in an HTTP response)
> should also be mentioned. 

Good one. Yep, we should mention this whereever ct= is described.

> (A possible design would be to put the
> content-type (and maybe other headers like Expires:?) in the hashed
> content, to be pulled out into the HTTP response when the content is
> served by an http server and then checked by the client, but I
> understand that this would be a tooling headache.)

Yep. We thought about it but agree that it gets too complex too
quickly. Maybe with a bit of experience...

> (I don't understand why you want to separate the 'optional' features
> into a separate spec. This made me miss the ct= feature entirely at
> first.)

The intent is to put stuff there if we're not sure if its
ready or needed everywhere. ct= is definitely the main
candidate feature for moving to the "base" spec though.
Some other things (e.g. handling dynamic content) are
way more experimental and should definitely not move
and maybe need more time before we want them in an RFC.

If all this does get popular then the RFCs can be revised later
based on experience in any case. (If nobody cares, then it
won't be a problem:-) So I don't think where things are
documented now is hugely important in the long term.

> I think the documentation should say that the hash and content type
> together identify the resource, 

Well, IMO the hash identifies the resource (if name-data integrity
is verified) so I don't think I agree that the content type is
key for identification. It is for interpretation (or whatever
the right term there is, maybe rendering?) and probably other
things.

> and that because the content can be
> verified, the resource can be sought (using the .well-known path, or
> any other path for that matter) from any source that the client thinks
> might have it. 

Absolutely. That's our primary motivation for all this.

> The primary and alternate domain name(s), and 'wrapped'
> URLs, are only provided as hints.

Yes.

> I agree with other commenters on the peculiarity of using // to
> provide the location hint since the named host is not being trusted as
> an authority. I don't understand why the 'primary' location isn't just
> encoded in the query, just like the alternate domain(s) and "wrapped
> URL(s)".  This would have the nice property that you can put the
> identifying parts (i.e. hash and content type) first, and the less important
> location hints parts all together after the identification. The various
> location hints (whether primary or secondary) would go together and
> their similarity would be clearer.
> 
> (Unless I'm misunderstanding something and the part after the //
> actually has status other than a hint?  That would seem to defeat
> the purpose.)

I think we could argue this (and we did already between the authors;-)
and it'd come down to "pick a way." We did already and wrote code
for that, so we'd prefer to stick with it as-is, especially if there's
no compelling reason to change. I think its likely we can agree that
there's no compelling differences here in whether we use "//" or
a "?loc=" or whatever.

Cheers,
Stephen.


> 
> Jonathan
> 
> 

From paul.hoffman@vpnc.org  Thu Jun  7 16:09:43 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BED821F85ED for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 16:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 QHsaCZk4cRvr for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 16:09:42 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB0F21F84A0 for <ietf@ietf.org>; Thu,  7 Jun 2012 16:09:42 -0700 (PDT)
Received: from [10.20.30.101] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q57N9dFF059053 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 7 Jun 2012 16:09:40 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4FC70E09.30002@cisco.com>
Date: Thu, 7 Jun 2012 16:09:39 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1278)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 23:09:43 -0000

On May 30, 2012, at 11:22 PM, Eliot Lear wrote:

> 	=95 I've been told by some that the Mission of the IETF is in =
some way out of date.  I don't know whether this is true, but if it is, =
the reference should be removed.

As others pointed out, it is a BCP, it is the only BCP we have that =
covers the mission, so it should probably stay.

> 	=95 It's probably worth adding a word or two about the fact that =
the ISOC Board is the final appellate avenue in the standardization =
process.  In this way it may also make sense to move Section 3.2.1 =
further back behind the IAB.

I have heard that as well, but cannot find it in RFC 2026 or any of the =
RFCs that update 2026 (3667 3668 3932 3978 3979 5378 5657 5742 6410). It =
should only be in the Tao if we can point to where the rule comes from.

> 	=95 I don't know about anyone else, but my experience has =
changed with regard to there being a "fair amount of time for =
socializing".  I would say there is a modest amount of time for =
socializing.

I have met with many first-timers at IETF meetings, and they have a fair =
amount of time for socializing. The more meetings you go to, the less =
time you have to socialize. I have added "for many participants" to the =
sentence.

> 	=95 The Tao mentions that we meet once a year in each region.  I =
don't think that's true for Asia at this point.  The text might call out =
that we meet where there are participants, or words that the IAOC might =
provide.

It doesn't say that. It says "approximately once a year in each region". =
That is still true.

> 	=95 The last paragraph in Section 4 is outdated.  Everyone uses =
wireless these days=96 everywhere at nearly every meeting.

Good catch.

> 	=95 4.12 really should be a top level section (moved further =
back).

This was a conscious decision made for the last Tao: put it in the =
middle to give the reader a sense of what the can do.

> 	=95 Section 5 (Working Groups) really should be moved forward =
(after Section 3 but before what is now Section 4).

The Tao is still normally read by people coming to their first meeting, =
not by someone participating for the first time on a WG mailing list.

> 	=95 Move acknowledgments to the back.  As it stands that text =
forms a disconnect between the Intro and later sections.

Done.

--Paul Hoffman


From sob@harvard.edu  Thu Jun  7 18:13:21 2012
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D6E211E8099 for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 18:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 DKZldBcxO79H for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 18:13:20 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id BD6B611E8095 for <ietf@ietf.org>; Thu,  7 Jun 2012 18:13:20 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000001.university.harvard.edu [10.35.2.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 0F4B1E8B72; Thu,  7 Jun 2012 21:13:19 -0400 (EDT)
Received: from ENTWHUBT0000003.university.harvard.edu (192.168.36.24) by ENTWEDGE0000001.university.harvard.edu (10.35.2.152) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 7 Jun 2012 21:12:49 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.61]) by entwhubt0000003.university.harvard.edu ([192.168.36.24]) with mapi id 14.01.0355.002; Thu, 7 Jun 2012 21:12:44 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Thread-Topic: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Thread-Index: AQHNRRPjzeDlNmma+0yP4HiwzJMosQ==
Date: Fri, 8 Jun 2012 01:13:18 +0000
Message-ID: <52CB44AB-006B-407F-AA44-976271B3E27E@harvard.edu>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org>
In-Reply-To: <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.248.127.162]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <3853E324EEAD2A45A946B68CFB2D9B61@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 01:13:21 -0000

On Jun 7, 2012, at 7:09 PM, Paul Hoffman wrote:

> On May 30, 2012, at 11:22 PM, Eliot Lear wrote:
>=20
>> 	=95 It's probably worth adding a word or two about the fact that the IS=
OC Board is the final appellate avenue in the standardization process.  In =
this way it may also make sense to move Section 3.2.1 further back behind t=
he IAB.
>=20
> I have heard that as well, but cannot find it in RFC 2026 or any of the R=
FCs that update 2026 (3667 3668 3932 3978 3979 5378 5657 5742 6410). It sho=
uld only be in the Tao if we can point to where the rule comes from.


see RFC 2026 section 6.5.3

6.5.3 Questions of Applicable Procedure

   Further recourse is available only in cases in which the procedures
   themselves (i.e., the procedures described in this document) are
   claimed to be inadequate or insufficient to the protection of the
   rights of all parties in a fair and open Internet Standards Process.
   Claims on this basis may be made to the Internet Society Board of
   Trustees.  The President of the Internet Society shall acknowledge
   such an appeal within two weeks, and shall at the time of
   acknowledgment advise the petitioner of the expected duration of the
   Trustees' review of the appeal.  The Trustees shall review the
   situation in a manner of its own choosing and report to the IETF on
   the outcome of its review.

   The Trustees' decision upon completion of their review shall be final
   with respect to all aspects of the dispute.

note that the appeal to the ISOC BopT is only if the claim is that the rule=
s are broken=20
not the application of the rules

there has never been such an appeal

Scott


From derhoermi@gmx.net  Thu Jun  7 19:16:37 2012
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBE011E80B7 for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 19:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level: 
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599]
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 jxKn6zuYYRkp for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 19:16:36 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 096E911E80B3 for <ietf@ietf.org>; Thu,  7 Jun 2012 19:16:35 -0700 (PDT)
Received: (qmail invoked by alias); 08 Jun 2012 02:16:34 -0000
Received: from dslb-094-223-208-167.pools.arcor-ip.net (EHLO HIVE) [94.223.208.167] by mail.gmx.net (mp012) with SMTP; 08 Jun 2012 04:16:34 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19mOJxhydtm+HPs0wRjOwUNvD5XM94k+XFKsaf76X 0yhzzrbqiV5ADq
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: ietf@ietf.org
Subject: Comments on draft-farrell-decade-ni-06
Date: Fri, 08 Jun 2012 04:16:35 +0200
Message-ID: <6kk2t71ghjalf43tqu14pvcnisoarv924g@hive.bjoern.hoehrmann.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 02:16:37 -0000

Hi,

  In http://tools.ietf.org/html/draft-farrell-decade-ni-06 the RFC 2119
boilerplate does not belong in an Introduction section, it should be in
a Terminology or Conformance or similarily named section.

For a URI scheme specification having no example of what the syntax is
prior to section 8 (or 4 if you spot it there) is a bad idea, there
should be one much earlier so you can get an idea what this is about
without a lot of reading.

The terms CoAP and DECADE require references in section 9.x since they
are not introduced or used anywhere else, if the terms are kept. I do
not think "General applicability with initial use cases provided by CoAP
and DECADE" is a useful description for the kind of application that may
make use of this scheme, even if there were references.

The Contact field should identify a Person, there should be a name at
least.

Section 7 references a Wikipedia article by bare address. That should be
a proper reference, called [Wikipedia] for instance, or it should at
least be on an indended paragraph of its own. It's very distracting when
flowing text is mixed with formal syntax, especially when using URLs in
a URL scheme specification (the preceding address was an example, not a
link.)

In section 4,

  Note that since the .well-known name-space is not intended for
  general information retrieval, if an application de-references a
  .well-known/ni URL via HTTP(S), then it SHOULD expect to receive a
  30x HTTP re-direction response and it MUST be able to handle this.
  Put another way, a server SHOULD return a 30x response when a .well-
  known/ni URL is de-referenced.

This is a confusing use of RFC 2119 keywords ("put another way" would
generally suggest the two formulations mean the same thing, but they
do not). I would say something like "servers SHOULD and clients MUST",
which would also remove the confusing "SHOULD expect".

It's not immediately clear whether the schemes define a default value
for the authority component. Some definition using the word "default"
would help, including saying there is "no default". See RFC 3986 section
3.2.2. for why this matters.

In section 3 the "MUST" in "decoders MUST recognize" is incorrect, that
re-states RFC 3986 requirements and should not be rendered as a new con-
formance requirement. Say that "RFC 3986 requires ..." or something like
that.

I think the requirement in RFC 4395 section 2.6 applies here, there are
text fields in 'ni' and 'nih' addresses, so there needs to be some dis-
cussion about I18N and IRI issues, or a statement that there are none,
or something along those lines. What if I want a non-ASCII host name in
them, for instance?

I may have missed it, but I did not see much error handling defined, say
how you might handle `ni:///sha-256;%F6...` or perhaps more importantly
`ni:///sha-256;f4Ox%20...` given that some Base64 implementations might
simply silently strip white space characters and perhaps ignore or mis-
treat non-base64 characters. The Security Considerations should mention
such parsing issues.

It's not clear to me that it is a good idea to use `http://h-authority/`
as example. It would seem better to use, say, `http://example.org/`.

regards,
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From paul.hoffman@vpnc.org  Thu Jun  7 19:20:39 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23B2311E808A for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 19:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2Aicp0s0FeEP for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 19:20:38 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD0411E8080 for <ietf@ietf.org>; Thu,  7 Jun 2012 19:20:37 -0700 (PDT)
Received: from [10.20.30.101] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q582KURY064219 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 7 Jun 2012 19:20:32 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <52CB44AB-006B-407F-AA44-976271B3E27E@harvard.edu>
Date: Thu, 7 Jun 2012 19:20:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <03EE51C5-CDAB-471B-8DE2-DFB40CE1E93D@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org> <52CB44AB-006B-407F-AA44-976271B3E27E@harvard.edu>
To: "Bradner, Scott" <sob@harvard.edu>
X-Mailer: Apple Mail (2.1278)
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 02:20:39 -0000

On Jun 7, 2012, at 6:13 PM, Bradner, Scott wrote:

> On Jun 7, 2012, at 7:09 PM, Paul Hoffman wrote:
>=20
>> On May 30, 2012, at 11:22 PM, Eliot Lear wrote:
>>=20
>>> 	=95 It's probably worth adding a word or two about the fact that =
the ISOC Board is the final appellate avenue in the standardization =
process.  In this way it may also make sense to move Section 3.2.1 =
further back behind the IAB.
>>=20
>> I have heard that as well, but cannot find it in RFC 2026 or any of =
the RFCs that update 2026 (3667 3668 3932 3978 3979 5378 5657 5742 =
6410). It should only be in the Tao if we can point to where the rule =
comes from.
>=20
>=20
> see RFC 2026 section 6.5.3
>=20
> 6.5.3 Questions of Applicable Procedure
>=20
>   Further recourse is available only in cases in which the procedures
>   themselves (i.e., the procedures described in this document) are
>   claimed to be inadequate or insufficient to the protection of the
>   rights of all parties in a fair and open Internet Standards Process.
>   Claims on this basis may be made to the Internet Society Board of
>   Trustees.  The President of the Internet Society shall acknowledge
>   such an appeal within two weeks, and shall at the time of
>   acknowledgment advise the petitioner of the expected duration of the
>   Trustees' review of the appeal.  The Trustees shall review the
>   situation in a manner of its own choosing and report to the IETF on
>   the outcome of its review.
>=20
>   The Trustees' decision upon completion of their review shall be =
final
>   with respect to all aspects of the dispute.
>=20
> note that the appeal to the ISOC BopT is only if the claim is that the =
rules are broken=20
> not the application of the rules

Exactly right. What Eliot said, and others have said, is that the ISOC =
board is the "final appellate avenue in the standardization process". =
That's quite different than "the rules are broken".

> there has never been such an appeal


Happily noted.

--Paul Hoffman


From narten@us.ibm.com  Thu Jun  7 21:53:10 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5561921F8602 for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 21:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.024
X-Spam-Level: 
X-Spam-Status: No, score=-110.024 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 tk+jj4P5sK1S for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 21:53:09 -0700 (PDT)
Received: from e5.ny.us.ibm.com (e5.ny.us.ibm.com [32.97.182.145]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE1221F85F6 for <ietf@ietf.org>; Thu,  7 Jun 2012 21:53:08 -0700 (PDT)
Received: from /spool/local by e5.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 8 Jun 2012 00:53:08 -0400
Received: from d01dlp02.pok.ibm.com (9.56.224.85) by e5.ny.us.ibm.com (192.168.1.105) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 8 Jun 2012 00:53:05 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 4C3C46E8049 for <ietf@ietf.org>; Fri,  8 Jun 2012 00:53:05 -0400 (EDT)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q584r4WQ193806 for <ietf@ietf.org>; Fri, 8 Jun 2012 00:53:05 -0400
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q584r4VU005247 for <ietf@ietf.org>; Thu, 7 Jun 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q584r3ZR005182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 7 Jun 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q584r3KU001300 for <ietf@ietf.org>; Fri, 8 Jun 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q584r2pk001286 for ietf@ietf.org; Fri, 8 Jun 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201206080453.q584r2pk001286@rotala.raleigh.ibm.com>
Date: Fri, 08 Jun 2012 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12060804-5930-0000-0000-000008A466BC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 04:53:10 -0000

Total of 73 messages in the last 7 days.
 
script run at: Fri Jun  8 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.59% |    7 |  7.32% |    47136 | touch@isi.edu
  4.11% |    3 |  9.22% |    59420 | stephen.farrell@cs.tcd.ie
  6.85% |    5 |  5.61% |    36144 | sm@resistor.net
  5.48% |    4 |  6.06% |    39055 | abdussalambaryun@gmail.com
  4.11% |    3 |  3.99% |    25726 | sm+ietf@elandsys.com
  4.11% |    3 |  3.53% |    22734 | john-ietf@jck.com
  2.74% |    2 |  4.25% |    27390 | d3e3e3@gmail.com
  4.11% |    3 |  2.84% |    18305 | mohta@necom830.hpcl.titech.ac.jp
  4.11% |    3 |  2.72% |    17519 | heard@pobox.com
  1.37% |    1 |  4.89% |    31480 | duerst@it.aoyama.ac.jp
  1.37% |    1 |  3.92% |    25256 | vincent.roca@inria.fr
  1.37% |    1 |  3.61% |    23258 | ron.even.tlv@gmail.com
  2.74% |    2 |  2.20% |    14159 | paul.hoffman@vpnc.org
  2.74% |    2 |  1.81% |    11632 | housley@vigilsec.com
  2.74% |    2 |  1.74% |    11206 | dhc@dcrocker.net
  2.74% |    2 |  1.71% |    11041 | joelja@bogus.com
  1.37% |    1 |  3.02% |    19471 | d.sturek@att.net
  1.37% |    1 |  2.22% |    14291 | lars@netapp.com
  1.37% |    1 |  2.14% |    13814 | ben@nostrum.com
  1.37% |    1 |  1.53% |     9865 | lear@cisco.com
  1.37% |    1 |  1.38% |     8884 | rees@mumble.net
  1.37% |    1 |  1.38% |     8880 | narten@us.ibm.com
  1.37% |    1 |  1.30% |     8345 | eburger-l@standardstrack.com
  1.37% |    1 |  1.22% |     7876 | derhoermi@gmx.net
  1.37% |    1 |  1.20% |     7702 | mellon@fugue.com
  1.37% |    1 |  1.18% |     7604 | alexey.melnikov@isode.com
  1.37% |    1 |  1.17% |     7532 | mohamed.boucadair@orange.com
  1.37% |    1 |  1.14% |     7356 | sob@harvard.edu
  1.37% |    1 |  1.11% |     7173 | llynch@civil-tongue.net
  1.37% |    1 |  1.10% |     7082 | adrian@olddog.co.uk
  1.37% |    1 |  1.09% |     7049 | daedulus@btconnect.com
  1.37% |    1 |  1.04% |     6712 | melinda.shore@gmail.com
  1.37% |    1 |  1.00% |     6465 | fred@cisco.com
  1.37% |    1 |  0.95% |     6135 | nick@inex.ie
  1.37% |    1 |  0.94% |     6036 | glenzorn@gmail.com
  1.37% |    1 |  0.93% |     5965 | tnadeau@lucidvision.com
  1.37% |    1 |  0.91% |     5893 | rbarnes@bbn.com
  1.37% |    1 |  0.91% |     5864 | warren@kumari.net
  1.37% |    1 |  0.91% |     5849 | ynir@checkpoint.com
  1.37% |    1 |  0.89% |     5738 | drc@virtualized.org
  1.37% |    1 |  0.88% |     5652 | lixia@cs.ucla.edu
  1.37% |    1 |  0.78% |     5010 | mrex@sap.com
  1.37% |    1 |  0.77% |     4984 | randy@psg.com
  1.37% |    1 |  0.75% |     4803 | paul@cypherpunks.ca
  1.37% |    1 |  0.73% |     4712 | ajs@anvilwalrusden.com
--------+------+--------+----------+------------------------
100.00% |   73 |100.00% |   644203 | Total


From daedulus@btconnect.com  Fri Jun  8 03:41:16 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2784E21F8517; Fri,  8 Jun 2012 03:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.909
X-Spam-Level: 
X-Spam-Status: No, score=-4.909 tagged_above=-999 required=5 tests=[AWL=-1.090, BAYES_05=-1.11, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4]
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 FQ74aMi2uo6h; Fri,  8 Jun 2012 03:41:15 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id 7DA4A21F850F; Fri,  8 Jun 2012 03:41:15 -0700 (PDT)
Received: from mail11-tx2-R.bigfish.com (10.9.14.242) by TX2EHSOBE004.bigfish.com (10.9.40.24) with Microsoft SMTP Server id 14.1.225.23; Fri, 8 Jun 2012 10:40:24 +0000
Received: from mail11-tx2 (localhost [127.0.0.1])	by mail11-tx2-R.bigfish.com (Postfix) with ESMTP id 8589532053E; Fri,  8 Jun 2012 10:40:24 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT011.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: PS-23(zz9371I542M1418Izz1202hzz1033IL8275dhz2dh2a8h5a9h668h839h93fhd24hf0ah304l)
Received: from mail11-tx2 (localhost.localdomain [127.0.0.1]) by mail11-tx2 (MessageSwitch) id 1339152022770248_2063; Fri,  8 Jun 2012 10:40:22 +0000 (UTC)
Received: from TX2EHSMHS009.bigfish.com (unknown [10.9.14.248])	by mail11-tx2.bigfish.com (Postfix) with ESMTP id B5784200046; Fri,  8 Jun 2012 10:40:22 +0000 (UTC)
Received: from DB3PRD0702HT011.eurprd07.prod.outlook.com (157.55.224.141) by TX2EHSMHS009.bigfish.com (10.9.99.109) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 8 Jun 2012 10:40:20 +0000
Received: from DBXPRD0610HT004.eurprd06.prod.outlook.com (157.56.252.181) by pod51017.outlook.com (10.3.48.170) with Microsoft SMTP Server (TLS) id 14.15.74.2; Fri, 8 Jun 2012 10:40:42 +0000
Message-ID: <004a01cd4562$b7b338e0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
References: <21762_1337814743_q4NNCMPh008981_alpine.BSF.2.00.1205231837020.9762@fledge.watson.org> <1337881837.3279.45.camel@destiny.pc.cs.cmu.edu>
Subject: Re: [secdir] secdir review of draft-sakane-dhc-dhcpv6-kdc-option
Date: Fri, 8 Jun 2012 11:37:27 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.181]
X-OriginatorOrg: btconnect.com
Cc: draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org, ietf <ietf@ietf.org>, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 10:41:16 -0000

Just to make public what I have hinted at privately, I think that steps
in section 4.1 may be somewhat underspecified.

They give the logic a client, one which supports both DHCP and DNS,
should
follow in order to find a KDC, with DNS information being preferred.
One scenario outlined in section 1 is of a user having entered userid
and
passphrase and waiting to be authenticated.  The steps imply a number of
timeouts in succession without specifying what balance to take of how
long
to wait for a server to respond versus how long to keep the user
waiting.
I would find it difficult to know what balance to strike without
guidance.

A related issue is that section 4.1 prefers DNS to DHCP for Kerberos
information but the Security Considerations stress the weakness of
DHCP and recommend authenticating DHCP.  What if DHCP is secure
and DNS is not?  Should DNS still be preferred?

Tom Petch

----- Original Message -----
From: "Jeffrey Hutzelman" <jhutz@cmu.edu>
To: "Samuel Weiler" <weiler+secdir@watson.org>
Cc: <draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org>;
<secdir@ietf.org>; <ietf@ietf.org>; <jhutz@cmu.edu>
Sent: Thursday, May 24, 2012 6:50 PM
Subject: Re: [secdir] secdir review of
draft-sakane-dhc-dhcpv6-kdc-option




From stephen.farrell@cs.tcd.ie  Fri Jun  8 04:21:49 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FC5E21F889D for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 04:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 vSU0RcMgRVH5 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 04:21:48 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5B121F8877 for <ietf@ietf.org>; Fri,  8 Jun 2012 04:21:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id EAEC717180B; Fri,  8 Jun 2012 12:21:44 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339154504; bh=Z/oLIgw1KsRLc9 pDXCUKTiJI2AbbOF1uuj26LZN2n1g=; b=ziwC+DSz/QV2Fl1tTRE16cYC4SEzP8 Cn8FYRlW457vt3pHHZpuLBR8j6p6PNLRG0IM9srpJntVwfNZxXewzuE5RQXHGRLt eSlmIZ0Al+QGLN4SvkPJri2DX2ssyEAzs46gqg3X9eEpR6JKluah2EXUmZUU5hrn 3nKFgnUi97CM/drOwt+9CS5aH5KOn8GVcTDWoECtSAyG2i5TY8JaCNFcaKHQ/w8O cKI7eBTn368Ox/oHSWnmPOtMNqq8Pl75iSGELkOsqrU3QS5O+nk/GWK2v/I5Vagt /jCKYQq9C0JwIqFf7CPuN5MYGdhwNv0VdmVF9YISJCWwhHg8/g8Ph+wQ==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id B2eliOPIsCj0; Fri,  8 Jun 2012 12:21:44 +0100 (IST)
Received: from [IPv6:2001:770:10:203:ccd0:6c1c:533b:ca48] (unknown [IPv6:2001:770:10:203:ccd0:6c1c:533b:ca48]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 3FD25171809; Fri,  8 Jun 2012 12:21:44 +0100 (IST)
Message-ID: <4FD1E048.8080507@cs.tcd.ie>
Date: Fri, 08 Jun 2012 12:21:44 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Jonathan A Rees <rees@mumble.net>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com> <4FD0FDC2.2090802@cs.tcd.ie> <CAGnGFMLc15-ZkD_Of7k0zK7ef-i6HN2LsPCfbW3pkwFkpSiOfA@mail.gmail.com>
In-Reply-To: <CAGnGFMLc15-ZkD_Of7k0zK7ef-i6HN2LsPCfbW3pkwFkpSiOfA@mail.gmail.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 11:21:49 -0000

Hiya,

On 06/08/2012 01:35 AM, Jonathan A Rees wrote:
> On Thu, Jun 7, 2012 at 3:15 PM, Stephen Farrell
> <stephen.farrell@cs.tcd.ie> wrote:
>>
>> On 06/06/2012 09:33 PM, Jonathan A Rees wrote:
>>> As requested I am sending comments on this last call draft to
>>> ietf@ietf.org. I sent them to the authors on 6 May but received no
>>> reply.
>>
>> Once again, sorry about that. No idea why I missed responding,
>> your mail is in my client even. Ah well.
>>
>>>
>>> Jonathan Rees
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Jonathan A Rees <rees@mumble.net>
>>> Date: Sun, May 6, 2012 at 7:57 PM
>>> Subject: comments on http://tools.ietf.org/html/draft-farrell-decade-ni-06
>>> To: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba
>>> <barryleiba@computer.org>, "S. Farrell" <stephen.farrell@cs.tcd.ie>,
>>> "P. Hallam-Baker" <pbaker@verisign.com>
>>>
>>> Here are some opinions on
>>> http://tools.ietf.org/html/draft-farrell-decade-ni-06 :
>>>
>>> I think this URI scheme would be a welcome addition to web
>>> architecture. Wide review should be sought, because this might become
>>> quite important and if there are problems they will be very difficult
>>> to fix later.
>>>
>>> I think using .well-known is a good idea.
>>>
>>> I think integration into the ecosystem, such as browser support,
>>> should be anticipated; for this reason I think content type should be
>>> elevated from an 'optional feature' to a 'required feature'.
>>>
>>> [i.e. conformant implementations must support it, even if providing
>>> the content type in the URI is itself optional.]
>>
>> I could certainly live with that, and I suspect my co-authors too,
>> but I'd need to ask 'em. However, we'd like to see more support for
>> it before doing that. If we only hear from you on this, then I
>> think leaving it in the other draft would be right. (See below
>> for why we want to keep that draft.) I guess others have a few
>> weeks to chime in on this.
> 
> OK, I suspect I can find other W3C TAG members who would agree; will circulate.

Great. Just note though that in figuring rough consensus its
not really useful for a bunch of (esp. previously unknown)
people to just say "+1" to something. A note like yours that
shows they've read the draft and have their own comment is
much more useful. (Its happened in the past that quite
well-meaning folks have jumped in like that and with no
context it makes it hard for anyone to figure what to make
of things.)

> 
> It is certainly strongly promoted by the W3C web architecture document, see
> http://www.w3.org/TR/webarch/#internet-media-type
> so I think I have W3C consensus (as of 2005) behind my claim.

Well I could argue that that says that protocols SHOULD
do stuff and we're just defining the URI here and not a
protocol. But let's see if we get more input on this.

> 
>>> If you
>>> don't do this, you are just encouraging sniffing and privilege
>>> escalation attacks. Sniffing would be a big step backwards. Better to
>>> do what the data: scheme does and say that there is a default content
>>> type of, say, text/plain, and that otherwise the content type ought to
>>> be specified in the URI.
>>>
>>> Content-type privilege escalation risk (and incorrect sniffing risk)
>>> should be mentioned in the security considerations section in any
>>> case.
>>
>> Would appreciate text if you can offer some. (Always happy to
>> make the sec. cons. bit better.)
> 
> Hmm. Hot potato.
> Maybe something can be derived from Adam's draft
> http://tools.ietf.org/html/draft-abarth-mime-sniff-06
> which I assume you've seen...  obviously I'd prefer you do the
> drafting, but will consider myself pressured.

I look forward to seeing that text then:-)

> 
>>> Maybe the risk that the host used for retrieval might be spoofing the
>>> content-type (by providing a bogus content-type in an HTTP response)
>>> should also be mentioned.
>>
>> Good one. Yep, we should mention this whereever ct= is described
> 
> No, this is a threat even if ct= isn't used. Suppose that the document
> is intended as an unscriptable media type, but the (malicious) server
> sets the content-type: header in the response to a scriptable type.
> Not good. I think this threat is described in Adam's draft.

Ta.

> 
>>> (A possible design would be to put the
>>> content-type (and maybe other headers like Expires:?) in the hashed
>>> content, to be pulled out into the HTTP response when the content is
>>> served by an http server and then checked by the client, but I
>>> understand that this would be a tooling headache.)
>>
>> Yep. We thought about it but agree that it gets too complex too
>> quickly. Maybe with a bit of experience...
>>
>>> (I don't understand why you want to separate the 'optional' features
>>> into a separate spec. This made me miss the ct= feature entirely at
>>> first.)
>>
>> The intent is to put stuff there if we're not sure if its
>> ready or needed everywhere. ct= is definitely the main
>> candidate feature for moving to the "base" spec though.
>> Some other things (e.g. handling dynamic content) are
>> way more experimental and should definitely not move
>> and maybe need more time before we want them in an RFC.
>>
>> If all this does get popular then the RFCs can be revised later
>> based on experience in any case. (If nobody cares, then it
>> won't be a problem:-) So I don't think where things are
>> documented now is hugely important in the long term.
> 
> Hmm... if this spec takes off like I hope it will, you will have more
> influence than you think now, so the implicit messages will be
> important... by putting ct= in a separate document you're saying that
> it's not important, and you'll encourage implementations that use
> sniffing instead of some rational way to convey the media type.

Maybe, maybe not. What's more important is what gets used
IMO. Again, let's see if we get more input.

> 
>>> I think the documentation should say that the hash and content type
>>> together identify the resource,
>>
>> Well, IMO the hash identifies the resource (if name-data integrity
>> is verified) so I don't think I agree that the content type is
>> key for identification. It is for interpretation (or whatever
>> the right term there is, maybe rendering?) and probably other
>> things.
> 
> Well maybe we're quibbling over terminology, but in the HTTP spec and
> in all the W3C documents, the media type is part of the resource (or
> "representation" in HTTPbis; the distinction is immaterial for your
> URI scheme), and therefore part of its identity. 

Immaterial for this scheme is the bit that I like:-) So yes
we don't need to solve any philosophical problems now.

> It would be
> unfortunate to introduce an incompatible world view into the RFC
> corpus.

The RFC corpus has lots of good and lots of dodgy stuff and is
not a bible.

> 
>>> and that because the content can be
>>> verified, the resource can be sought (using the .well-known path, or
>>> any other path for that matter) from any source that the client thinks
>>> might have it.
>>
>> Absolutely. That's our primary motivation for all this.
>>
>>> The primary and alternate domain name(s), and 'wrapped'
>>> URLs, are only provided as hints.
>>
>> Yes.
>>
>>> I agree with other commenters on the peculiarity of using // to
>>> provide the location hint since the named host is not being trusted as
>>> an authority. I don't understand why the 'primary' location isn't just
>>> encoded in the query, just like the alternate domain(s) and "wrapped
>>> URL(s)".  This would have the nice property that you can put the
>>> identifying parts (i.e. hash and content type) first, and the less important
>>> location hints parts all together after the identification. The various
>>> location hints (whether primary or secondary) would go together and
>>> their similarity would be clearer.
>>>
>>> (Unless I'm misunderstanding something and the part after the //
>>> actually has status other than a hint?  That would seem to defeat
>>> the purpose.)
>>
>> I think we could argue this (and we did already between the authors;-)
>> and it'd come down to "pick a way." We did already and wrote code
>> for that, so we'd prefer to stick with it as-is, especially if there's
>> no compelling reason to change. I think its likely we can agree that
>> there's no compelling differences here in whether we use "//" or
>> a "?loc=" or whatever.
> 
> Well, you have a chance to fix this now, and it will be impossible to
> fix later. 

Its true we won't be able to change this later but not true
IMO that any fix is needed, now or later.

> Using // is contrary to RFC 3986, which very clearly says
> "governance of the name space defined by the remainder of the URI is
> delegated to that authority". This is certainly not what this URI
> scheme does, so use of // is contrary to the appicable normative spec.

I disagree. The full quote there is:

  "Many URI schemes include a hierarchical element for a naming
   authority so that governance of the name space defined by the
   remainder of the URI is delegated to that authority (which may, in
   turn, delegate it further)."

There are no SHOULDs nor MUSTs there with which we're not
complying, and "many" != "all." Yes, ni URIs differ in some
respects from HTTP URLs, but if they didn't then this draft
wouldn't be needed, so that's ok.

Cheers,
S.


> 
> Best
> Jonathan
> 
>> Cheers,
>> Stephen.
>>
>>
>>>
>>> Jonathan
>>>
>>>

From stephen.farrell@cs.tcd.ie  Fri Jun  8 06:35:57 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78CCA21F873C for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 06:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ikw5mGyiHrYE for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 06:35:56 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB4921F873A for <ietf@ietf.org>; Fri,  8 Jun 2012 06:35:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id B5D431714E4; Fri,  8 Jun 2012 14:35:42 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339162541; bh=1uVypHRiKNCWXp 0XUhY7+a8fVFwM2mkUy/MFWdTioXY=; b=MWnhSKFKjujT4MQL/Qvcv+O7/9X1ny X8X5iQEkVNHMqxnIOCd8DAySPhCNLD3TEsfzxmOYLVFU6ZMgBHY8YSeOoDmVIbGO 0BvlmJ+Xgh/7aPbK5j488hs/Cf9fNm+L+SGzgSZFJ2D5KmT5RrB7M2e+e0q4mip9 hWmcDIbcbRKyPephJ2bNh+GEwQiW5nGn+CPpGWHPMXkGix0r6MofQoviDGMR+JUU 09+or28yvNg9Mk8mkm9zPKJV6+Eis70nGsK10Ut+RRFCUYWfKXTaTYuCUKtQEhix ojdyewZi97Da50+uwbExdIohLCVquk6/mg1UIMCmAL73o0NZpwIjdkpg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id ubixJu7P67GC; Fri,  8 Jun 2012 14:35:41 +0100 (IST)
Received: from [IPv6:2001:770:10:203:ccd0:6c1c:533b:ca48] (unknown [IPv6:2001:770:10:203:ccd0:6c1c:533b:ca48]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 581FD17180C; Fri,  8 Jun 2012 14:35:37 +0100 (IST)
Message-ID: <4FD1FFA5.4000704@cs.tcd.ie>
Date: Fri, 08 Jun 2012 14:35:33 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: Comments on draft-farrell-decade-ni-06
References: <6kk2t71ghjalf43tqu14pvcnisoarv924g@hive.bjoern.hoehrmann.de>
In-Reply-To: <6kk2t71ghjalf43tqu14pvcnisoarv924g@hive.bjoern.hoehrmann.de>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 13:35:57 -0000

Hi Bjoern,

Thanks for the feedback!

On 06/08/2012 03:16 AM, Bjoern Hoehrmann wrote:
> Hi,
> 
>   In http://tools.ietf.org/html/draft-farrell-decade-ni-06 the RFC 2119

Just to note that -07 is the version for IETF LC. But your
comments apply as well to that, so that's fine.

If its useful, I've a working copy of this at [1] that has
the changes below as well as a bunch based on other
comments received so far.

   [1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-decade-ni.txt

> boilerplate does not belong in an Introduction section, it should be in
> a Terminology or Conformance or similarily named section.

What we have is very common in RFCs.

> For a URI scheme specification having no example of what the syntax is
> prior to section 8 (or 4 if you spot it there) is a bad idea, there
> should be one much earlier so you can get an idea what this is about
> without a lot of reading.

Fair enough, added one to the intro.

> The terms CoAP and DECADE require references in section 9.x since they
> are not introduced or used anywhere else, if the terms are kept. I do
> not think "General applicability with initial use cases provided by CoAP
> and DECADE" is a useful description for the kind of application that may
> make use of this scheme, even if there were references.

Suggestions for text that'd work welcome. I agree that the CoAP and
DECADE mentions should probably go, so for now it just says "General
Applicability."

> The Contact field should identify a Person, there should be a name at
> least.

Sure. That'd be me I guess:-)

> Section 7 references a Wikipedia article by bare address. That should be
> a proper reference, called [Wikipedia] for instance, or it should at
> least be on an indended paragraph of its own. It's very distracting when
> flowing text is mixed with formal syntax, especially when using URLs in
> a URL scheme specification (the preceding address was an example, not a
> link.)

I've no idea what change to section 7 you mean. I'd welcome a better
reference for magnet if someone can offer one but we looked and didn't
find one.

> 
> In section 4,
> 
>   Note that since the .well-known name-space is not intended for
>   general information retrieval, if an application de-references a
>   .well-known/ni URL via HTTP(S), then it SHOULD expect to receive a
>   30x HTTP re-direction response and it MUST be able to handle this.
>   Put another way, a server SHOULD return a 30x response when a .well-
>   known/ni URL is de-referenced.
> 
> This is a confusing use of RFC 2119 keywords ("put another way" would
> generally suggest the two formulations mean the same thing, but they
> do not). I would say something like "servers SHOULD and clients MUST",
> which would also remove the confusing "SHOULD expect".

While I think its ok, I guess "SHOULD expect" is a bit dodgy, so
I've tweaked it to say:

  "Note that since the .well-known name-space is not intended for
   general information retrieval, if an application de-references a
   .well-known/ni URL via HTTP(S), then it will often receive a 30x
   HTTP re-direction response.  A server responding to a request for
   a .well-known/ni URL SHOULD therefore return a 30x response and
   a client sending such a request MUST be able to handle that."

> It's not immediately clear whether the schemes define a default value
> for the authority component. Some definition using the word "default"
> would help, including saying there is "no default". See RFC 3986 section
> 3.2.2. for why this matters.

Good catch. I've added a statement that there is no default.

> In section 3 the "MUST" in "decoders MUST recognize" is incorrect, that
> re-states RFC 3986 requirements and should not be rendered as a new con-
> formance requirement. Say that "RFC 3986 requires ..." or something like
> that.

Ok.

> I think the requirement in RFC 4395 section 2.6 applies here, there are
> text fields in 'ni' and 'nih' addresses, so there needs to be some dis-
> cussion about I18N and IRI issues, or a statement that there are none,
> or something along those lines. What if I want a non-ASCII host name in
> them, for instance?

Hmm. So what are the reasonable options for that? I guess I'd prefer
to just copy from (or reference) something else that's deployed
and works, and not invent anything here.

I've put in a placeholder in my working copy.

> I may have missed it, but I did not see much error handling defined, say
> how you might handle `ni:///sha-256;%F6...` or perhaps more importantly
> `ni:///sha-256;f4Ox%20...` given that some Base64 implementations might
> simply silently strip white space characters and perhaps ignore or mis-
> treat non-base64 characters. The Security Considerations should mention
> such parsing issues.

Good point. I'd welcome suggestions for what to say there.

I've put in a placeholder in my working copy.

> 
> It's not clear to me that it is a good idea to use `http://h-authority/`
> as example. It would seem better to use, say, `http://example.org/`.

Not sure how to use that there, since h-authority isn't an example
authority but really a placeholder. I've left this as-is for now.

Thanks again for the good comments,
Cheers,
S.

> 
> regards,

From john-ietf@jck.com  Fri Jun  8 07:16:09 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D74A21F8754 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 07:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.506
X-Spam-Level: 
X-Spam-Status: No, score=-102.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 SbVDEjhlN+oG for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 07:16:08 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7054221F873D for <ietf@ietf.org>; Fri,  8 Jun 2012 07:16:08 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Sczst-000A3U-Ah; Fri, 08 Jun 2012 10:09:51 -0400
Date: Fri, 08 Jun 2012 10:16:01 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF:	A	Novice's Guide to the Internet Engineering Task Force)	to	Informational RFC
Message-ID: <21AE1D21DA46D4100067071A@JcK-HP8200.jck.com>
In-Reply-To: <03EE51C5-CDAB-471B-8DE2-DFB40CE1E93D@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org> <52CB44AB-006B-407F-AA44-976271B3E27E@harvard.edu> <03EE51C5-CDAB-471B-8DE2-DFB40CE1E93D@vpnc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 14:16:09 -0000

Sigh.

These multiple threads are, IMO, a wonderful exposition of how
the IETF can waste a tremendous amount of collective time and
energy fine-tuning a document and/or procedures by a very large
committee.  If nothing else, the process often leads to victory
by exhaustion as people just give up, leaving the discussion who
have the energy (or, as a colleague would put it, "too much time
on their hands".  I plead somewhat guilty for getting sucked
back in, but I want to make a few suggestions:

(1) Can we figure out a way to converge on whether we are
editing an RFC-to-be by committee or planning something web-ish
(not distinguishing between "web page" and "wiki" for the
moment?   If the former, then there are several irrelevant
threads.  If the latter, then there are a lot of useful comments
that should be handled in a different way.

(2) At one time, one of the key differences between the IETF and
other bodies in more or less the same business was that we
allowed ourselves considerable flexibility to match how we did
things to the situation and our needs while those other bodies
had to spend huge amounts of energy getting agreement on the
exact way that something should be done before attempting to do
it.  If we are going down the "web-ish" path and haven't lost
that sense of flexibility entirely, I would like to recommend
that we perform a "let's try this, see how it works, and then
work out specific procedures for the future" experimental
engineering process rather than trying to get the details right
by committee.  In particular, I suggest that, for the initial
round of turning the current I-D into something web-ish and
establishing a model for handling suggestions and changes, we:

Ii) We appoint an Editor (or Editor-in-chief).  

(ii) Based on precedent, history, a much-better-than-decent job,
authorship of the I-D, and an orderly transition from one
publication model to the other, we should appoint Paul by
acclamation.  By that I mean that someone, ideally Russ, gets on
the list and says "is there really any objection to appointing
Paul... if not, done".  That skips, for the present, wasting
more time figuring out who makes the appointment, whose approval
is needed, whether we need a whole process (e.g., of volunteers,
lists and comments) similar to how we handle IAOC and ISOC BoT
appointments, and a whole series of other ways in which we could
waste a lot of time and then get the same result.

(iii) Let's give the Editor six or nine months of discretion and
experimental time about formats (let's at least start with a
controlled list of people who can make changes until we have a
document in place and a bit of experience -- I see no
substantive difference between a controlled-authorship Wiki and
a controlled-authorship web page other than the tools used
although we could spend lots of time debating the
non-substantive differences), editorial board composition, how
to solicit and receive input, etc.  We encourage the editor to
consult with the IESG to the extent to which the IESG (or some
IESG-chosen subcommittee) is inclined to be involved.

(iv) At the end of that period, we see if we can find an
efficient way to examine the experience, draw ideas together,
and figure out what we really want to do for the long term and
what procedures are needed to do it.  I think I just said "BOF
in Atlanta or Orlando" rather than "mail storm on the IETF
list", but, if we need to do a mail storm, let's at least have
some experience and a web-based document on which to focus,
rather than trying to have editorial, procedural,
organizational, and format suggestions all mixed up with each
other.

If we all really have this many spare cycles, perhaps many of
them would be better spent getting the document (page, wiki,...)
right rather than tuning procedures.  Perhaps some of them might
even be better invested in protocol specification.   And, on
that note, I'm going to go try to spend a little time on a
neglected WG.

    best,
    john


From tglassey@earthlink.net  Fri Jun  8 07:23:48 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E28821F8803; Fri,  8 Jun 2012 07:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 xfyrMR9EzgUt; Fri,  8 Jun 2012 07:23:47 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 81FA621F8759; Fri,  8 Jun 2012 07:23:46 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=g+9RJjk8v1WshDBWR/RmEL7fB0h3k7wKbDSLXkt3k4fMsECeXPtJjpnRGebJ2jxP; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1Sd06E-0007lj-GJ; Fri, 08 Jun 2012 10:23:38 -0400
Message-ID: <4FD20AE5.5060503@earthlink.net>
Date: Fri, 08 Jun 2012 07:23:33 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>
Subject: Re: [secdir] secdir review of draft-sakane-dhc-dhcpv6-kdc-option
References: <21762_1337814743_q4NNCMPh008981_alpine.BSF.2.00.1205231837020.9762@fledge.watson.org> <1337881837.3279.45.camel@destiny.pc.cs.cmu.edu> <004a01cd4562$b7b338e0$4001a8c0@gateway.2wire.net>
In-Reply-To: <004a01cd4562$b7b338e0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec790ed8a6a3d1ea84abb910e2a94da62c8d350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
Cc: draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org, ietf <ietf@ietf.org>, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 14:23:48 -0000

On 6/8/2012 3:37 AM, t.p. wrote:
> Just to make public what I have hinted at privately, I think that steps
> in section 4.1 may be somewhat underspecified.
>
> They give the logic a client, one which supports both DHCP and DNS,
> should
> follow in order to find a KDC, with DNS information being preferred.
Yes, this is because the DNS auth models are better than DHCP today AFAIK.
> One scenario outlined in section 1 is of a user having entered userid
> and
> passphrase and waiting to be authenticated.  The steps imply a number of
> timeouts in succession without specifying what balance to take of how
> long
> to wait for a server to respond versus how long to keep the user
> waiting.
True but this is likely to be set in the client as a flat config value 
one would think.

And if so this is actually a good thing you bring up Tom. My take is 
that from a policy management standpoint the  timeout period should be a 
"policy level" control IMHO and should have both a default value and a 
method of overriding it to allow people when they need to  to create a 
more "synchronous" expectation from a responder.
> I would find it difficult to know what balance to strike without
> guidance.
>
> A related issue is that section 4.1 prefers DNS to DHCP for Kerberos
> information but the Security Considerations stress the weakness of
> DHCP and recommend authenticating DHCP.  What if DHCP is secure
> and DNS is not?  Should DNS still be preferred?
DNSSEC is clearly beyond DHCP security models so perhaps for a working 
system this makes sense unless you want to create an autonomous DNS 
client which can exist in a pre-boot model.

Pardon my restating the obvious but "Still the issue is that DNS 
services dont work until they are loaded and DHCP is designed to work 
from a firmware boot (as we all know)".

How does this fit into what NEA is supposed to provide as a baseline?
>
> Tom Petch
>
> ----- Original Message -----
> From: "Jeffrey Hutzelman"<jhutz@cmu.edu>
> To: "Samuel Weiler"<weiler+secdir@watson.org>
> Cc:<draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org>;
> <secdir@ietf.org>;<ietf@ietf.org>;<jhutz@cmu.edu>
> Sent: Thursday, May 24, 2012 6:50 PM
> Subject: Re: [secdir] secdir review of
> draft-sakane-dhc-dhcpv6-kdc-option
>
>
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2178 / Virus Database: 2433/5055 - Release Date: 06/07/12
>
>


From daedulus@btconnect.com  Fri Jun  8 07:27:32 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5AF021F8920; Fri,  8 Jun 2012 07:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.254
X-Spam-Level: 
X-Spam-Status: No, score=-4.254 tagged_above=-999 required=5 tests=[AWL=-0.655, BAYES_00=-2.599, 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 TI7n1J8qt9aW; Fri,  8 Jun 2012 07:27:32 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe001.messaging.microsoft.com [213.199.154.204]) by ietfa.amsl.com (Postfix) with ESMTP id E7AFA21F8800; Fri,  8 Jun 2012 07:27:31 -0700 (PDT)
Received: from mail26-am1-R.bigfish.com (10.3.201.239) by AM1EHSOBE001.bigfish.com (10.3.204.21) with Microsoft SMTP Server id 14.1.225.23; Fri, 8 Jun 2012 14:26:39 +0000
Received: from mail26-am1 (localhost [127.0.0.1])	by mail26-am1-R.bigfish.com (Postfix) with ESMTP id BFAD64003F8; Fri,  8 Jun 2012 14:26:39 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT009.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -28
X-BigFish: PS-28(zzbb2dI98dI9371I542M1dbaI1432I1418I4015Izz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah304l)
Received: from mail26-am1 (localhost.localdomain [127.0.0.1]) by mail26-am1 (MessageSwitch) id 1339165597980755_20655; Fri,  8 Jun 2012 14:26:37 +0000 (UTC)
Received: from AM1EHSMHS015.bigfish.com (unknown [10.3.201.252])	by mail26-am1.bigfish.com (Postfix) with ESMTP id E33F8220049; Fri,  8 Jun 2012 14:26:37 +0000 (UTC)
Received: from DB3PRD0702HT009.eurprd07.prod.outlook.com (157.55.224.141) by AM1EHSMHS015.bigfish.com (10.3.207.153) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 8 Jun 2012 14:26:36 +0000
Received: from DBXPRD0610HT005.eurprd06.prod.outlook.com (157.56.252.181) by pod51017.outlook.com (10.3.4.174) with Microsoft SMTP Server (TLS) id 14.15.74.2; Fri, 8 Jun 2012 14:27:26 +0000
Message-ID: <020601cd4582$63db64c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: ssakane <ssakane@cisco.com>
References: <CBF82D46.6AB4%ssakane@cisco.com>
Subject: Re: [secdir] secdir review of draft-sakane-dhc-dhcpv6-kdc-option
Date: Fri, 8 Jun 2012 15:24:10 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.181]
X-OriginatorOrg: btconnect.com
Cc: draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org, ietf <ietf@ietf.org>, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 14:27:33 -0000

----- Original Message -----
From: "ssakane" <ssakane@cisco.com>
To: "t.p." <daedulus@btconnect.com>
Cc: <draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org>;
<secdir@ietf.org>; "ietf" <ietf@ietf.org>
Sent: Friday, June 08, 2012 2:29 PM
> Hi Tom,
>
> Some reviewers suggested me to just remove the figure and its
description in
> 4.1 because it has ambiguity.  I think it would be better to leave the
1st
> paragraph in section 4.1, and I should remove the rest.  What do you
think
> about this idea ?

I would leave it in.

The first paragraph on its own I would think underspecified and the rest
of the section does cover a number of issues, issues that only occurred
to me when I read the section carefully.  As I said in my last post, I
then found I had further issues - how long to wait, should a secure DHCP
trump an insecure DNS? - which may be worth exploring in addition.

I do think that this kind of pseudocode helps a lot of developers to
understand the issues and would want a good reason to remove it; at the
same time, others see it as an impurity that has no part in a Standards
Track RFC.  One option would be to remove it to an Appendix which
implicitly makes it Informative and not Normative so it is there for
those who would benefit from it but will not upset those who consider it
out of place.  But I would bounce this off the krb list to see what
reaction you get.

Tom Petch

> Thanks,
> Shoichi
>
> On 6/8/12 7:37 PM, "t.p." <daedulus@btconnect.com> wrote:
>
> > Just to make public what I have hinted at privately, I think that
steps
> > in section 4.1 may be somewhat underspecified.
> >
> > They give the logic a client, one which supports both DHCP and DNS,
> > should
> > follow in order to find a KDC, with DNS information being preferred.
> > One scenario outlined in section 1 is of a user having entered
userid
> > and
> > passphrase and waiting to be authenticated.  The steps imply a
number of
> > timeouts in succession without specifying what balance to take of
how
> > long
> > to wait for a server to respond versus how long to keep the user
> > waiting.
> > I would find it difficult to know what balance to strike without
> > guidance.
> >
> > A related issue is that section 4.1 prefers DNS to DHCP for Kerberos
> > information but the Security Considerations stress the weakness of
> > DHCP and recommend authenticating DHCP.  What if DHCP is secure
> > and DNS is not?  Should DNS still be preferred?
> >
> > Tom Petch
> >
> > ----- Original Message -----
> > From: "Jeffrey Hutzelman" <jhutz@cmu.edu>
> > To: "Samuel Weiler" <weiler+secdir@watson.org>
> > Cc: <draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org>;
> > <secdir@ietf.org>; <ietf@ietf.org>; <jhutz@cmu.edu>
> > Sent: Thursday, May 24, 2012 6:50 PM
> > Subject: Re: [secdir] secdir review of
> > draft-sakane-dhc-dhcpv6-kdc-option
> >
> >
> >
>
>



From sob@harvard.edu  Fri Jun  8 12:46:33 2012
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AAC821F8716 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 12:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 2NUYgI2gKOk0 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 12:46:32 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id D2DC221F871D for <ietf@ietf.org>; Fri,  8 Jun 2012 12:46:30 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000004.university.harvard.edu [10.35.202.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 4A41EE8C48; Fri,  8 Jun 2012 15:46:30 -0400 (EDT)
Received: from ENTWHUBT0000006.university.harvard.edu (192.168.236.26) by entwedge0000004.university.harvard.edu (10.35.202.51) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 8 Jun 2012 15:46:23 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.61]) by ENTWHUBT0000006.university.harvard.edu ([192.168.236.28]) with mapi id 14.01.0355.002; Fri, 8 Jun 2012 15:46:29 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Thread-Topic: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Thread-Index: AQHNRRPjzeDlNmma+0yP4HiwzJMosQ==
Date: Fri, 8 Jun 2012 19:46:29 +0000
Message-ID: <09A09092-51D1-4406-9387-5F988552BF8A@harvard.edu>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org> <52CB44AB-006B-407F-AA44-976271B3E27E@harvard.edu> <03EE51C5-CDAB-471B-8DE2-DFB40CE1E93D@vpnc.org>
In-Reply-To: <03EE51C5-CDAB-471B-8DE2-DFB40CE1E93D@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.248.127.162]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <C5B4FB593B706E448E128C7D8BDDB794@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 19:46:33 -0000

On Jun 7, 2012, at 10:20 PM, Paul Hoffman wrote:

> On Jun 7, 2012, at 6:13 PM, Bradner, Scott wrote:
>=20
>> On Jun 7, 2012, at 7:09 PM, Paul Hoffman wrote:
>>=20
>>> On May 30, 2012, at 11:22 PM, Eliot Lear wrote:
>>>=20
>>>> 	=95 It's probably worth adding a word or two about the fact that the =
ISOC Board is the final appellate avenue in the standardization process.  I=
n this way it may also make sense to move Section 3.2.1 further back behind=
 the IAB.
>>>=20
>>> I have heard that as well, but cannot find it in RFC 2026 or any of the=
 RFCs that update 2026 (3667 3668 3932 3978 3979 5378 5657 5742 6410). It s=
hould only be in the Tao if we can point to where the rule comes from.
>>=20
>>=20
>> see RFC 2026 section 6.5.3
>>=20
>> 6.5.3 Questions of Applicable Procedure
>>=20
>>  Further recourse is available only in cases in which the procedures
>>  themselves (i.e., the procedures described in this document) are
>>  claimed to be inadequate or insufficient to the protection of the
>>  rights of all parties in a fair and open Internet Standards Process.
>>  Claims on this basis may be made to the Internet Society Board of
>>  Trustees.  The President of the Internet Society shall acknowledge
>>  such an appeal within two weeks, and shall at the time of
>>  acknowledgment advise the petitioner of the expected duration of the
>>  Trustees' review of the appeal.  The Trustees shall review the
>>  situation in a manner of its own choosing and report to the IETF on
>>  the outcome of its review.
>>=20
>>  The Trustees' decision upon completion of their review shall be final
>>  with respect to all aspects of the dispute.
>>=20
>> note that the appeal to the ISOC BopT is only if the claim is that the r=
ules are broken=20
>> not the application of the rules
>=20
> Exactly right. What Eliot said, and others have said, is that the ISOC bo=
ard is the "final appellate avenue in the standardization process". That's =
quite different than "the rules are broken".

just to be clear - saying "final appellate avenue in the standardization pr=
ocess". could be read as meaning
that a appeal of a technical decision could be made to the ISOC Board and t=
hat is not the case -=20
this is why I used different language

not sure which you were supporting

Scott

>=20
>> there has never been such an appeal
>=20
>=20
> Happily noted.
>=20
> --Paul Hoffman
>=20


From paul.hoffman@vpnc.org  Fri Jun  8 12:49:08 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68F8511E8120 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 12:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 uqw3hethiXFT for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 12:49:08 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id E1A5A11E811C for <ietf@ietf.org>; Fri,  8 Jun 2012 12:49:07 -0700 (PDT)
Received: from sn87.proper.com (sn87.proper.com [75.101.18.87]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q58Jn4Bk036203 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 8 Jun 2012 12:49:05 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <09A09092-51D1-4406-9387-5F988552BF8A@harvard.edu>
Date: Fri, 8 Jun 2012 12:49:04 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <81AC4AD6-1EFC-405A-AD8F-B5AB03F2976D@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org> <52CB44AB-006B-407F-AA44-976271B3E27E@harvard.edu> <03EE51C5-CDAB-471B-8DE2-DFB40CE1E93D@vpnc.org> <09A09092-51D1-4406-9387-5F988552BF8A@harvard.edu>
To: "Bradner, Scott" <sob@harvard.edu>
X-Mailer: Apple Mail (2.1278)
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 19:49:08 -0000

On Jun 8, 2012, at 12:46 PM, Bradner, Scott wrote:

> just to be clear - saying "final appellate avenue in the =
standardization process". could be read as meaning
> that a appeal of a technical decision could be made to the ISOC Board =
and that is not the case -=20
> this is why I used different language
>=20
> not sure which you were supporting


I am supporting not putting anything about appeals to the ISOC Board in =
the Tao. They do not apply to novices.

--Paul Hoffman


From suresh.krishnan@ericsson.com  Fri Jun  8 13:14:38 2012
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC82011E815B; Fri,  8 Jun 2012 13:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 YoLru9adnSTS; Fri,  8 Jun 2012 13:14:38 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB7F11E8152; Fri,  8 Jun 2012 13:14:38 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q58KED9u009848; Fri, 8 Jun 2012 15:14:37 -0500
Received: from [142.133.112.108] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.264.0; Fri, 8 Jun 2012 16:14:13 -0400
Message-ID: <4FD25D14.7000207@ericsson.com>
Date: Fri, 8 Jun 2012 16:14:12 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Subject: Re: Last Call: <draft-ietf-6man-lineid-05.txt> (The Line Identification Destination Option) to Experimental RFC
References: <20120604141855.24802.66473.idtracker@ietfa.amsl.com> <94C682931C08B048B7A8645303FDC9F36E32ED1AC0@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E32ED1AC0@PUEXCB1B.nanterre.francetelecom.fr>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: DUREL Sophie OLNC/NAD/TIP <sophie.durel@orange.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 20:14:38 -0000

Hi Med,

On 06/06/2012 08:04 AM, mohamed.boucadair@orange.com wrote:
> Dear Suresh, all,
> 
> Even if the document includes several warnings about the unreliability of an RS-based mechanism, I suggest to add a pointer to the following document:
> http://tools.ietf.org/html/draft-dec-6man-rs-access-harmful-00. 

Is there something in particular that you think is missing from the
lineid draft? The current warning text in lineid (and the
reclassification to experimental) was arrived at after consultations
with the the 6man chairs and the author of draft-dec.

Thanks
Suresh

From lear@cisco.com  Fri Jun  8 14:06:22 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 939B121F8692 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 14:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 7g8YXIxJ4DhC for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 14:06:21 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6E39511E80E9 for <ietf@ietf.org>; Fri,  8 Jun 2012 14:06:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=2557; q=dns/txt; s=iport; t=1339189579; x=1340399179; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=o/lgBLj9DJV6zdpoW8cfVQnqe2hyuO+oKGsij4/+VFE=; b=RdUU5L21id8x6zTR0NysjGxzFHI8tIOx//cpO2jOexg+fnFxl2IcgRHk iLwmuvyaj/LGOnWfdk6CGTohrDGfgN6IqgNBQ/vvc2WPbbrATkMi4gaJq hCkNX//dhsTaE73NW9E9spKfLkP/nRpk/Xwvw9golrS/kh1wguMSbOYZ4 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApQFAO1o0k+rRDoH/2dsb2JhbABFDoVGqy2DVoEHghgBAQEEEgEQDwFFARALGAICBRYEBwICCQMCAQIBRQYNAQcBAR6HaJkjjRaSRoEjigOEboESA5UejhWBZoInOw
X-IronPort-AV: E=Sophos;i="4.75,738,1330905600"; d="scan'208";a="48240296"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 08 Jun 2012 21:06:19 +0000
Received: from rtp-vpn4-672.cisco.com (rtp-vpn4-672.cisco.com [10.82.210.160]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q58L6FmP003701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);  Fri, 8 Jun 2012 21:06:17 GMT
Message-ID: <4FD26946.7070209@cisco.com>
Date: Fri, 08 Jun 2012 23:06:14 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org> <52CB44AB-006B-407F-AA44-976271B3E27E@harvard.edu> <03EE51C5-CDAB-471B-8DE2-DFB40CE1E93D@vpnc.org> <09A09092-51D1-4406-9387-5F988552BF8A@harvard.edu>
In-Reply-To: <09A09092-51D1-4406-9387-5F988552BF8A@harvard.edu>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 21:06:22 -0000

All,

Based on this explanation from Scott I withdraw my suggestion.  Text can
stay as it is.

Eliot

On 6/8/12 9:46 PM, Bradner, Scott wrote:
> On Jun 7, 2012, at 10:20 PM, Paul Hoffman wrote:
>
>> On Jun 7, 2012, at 6:13 PM, Bradner, Scott wrote:
>>
>>> On Jun 7, 2012, at 7:09 PM, Paul Hoffman wrote:
>>>
>>>> On May 30, 2012, at 11:22 PM, Eliot Lear wrote:
>>>>
>>>>> 	â€¢ It's probably worth adding a word or two about the fact that the ISOC Board is the final appellate avenue in the standardization process.  In this way it may also make sense to move Section 3.2.1 further back behind the IAB.
>>>> I have heard that as well, but cannot find it in RFC 2026 or any of the RFCs that update 2026 (3667 3668 3932 3978 3979 5378 5657 5742 6410). It should only be in the Tao if we can point to where the rule comes from.
>>>
>>> see RFC 2026 section 6.5.3
>>>
>>> 6.5.3 Questions of Applicable Procedure
>>>
>>>  Further recourse is available only in cases in which the procedures
>>>  themselves (i.e., the procedures described in this document) are
>>>  claimed to be inadequate or insufficient to the protection of the
>>>  rights of all parties in a fair and open Internet Standards Process.
>>>  Claims on this basis may be made to the Internet Society Board of
>>>  Trustees.  The President of the Internet Society shall acknowledge
>>>  such an appeal within two weeks, and shall at the time of
>>>  acknowledgment advise the petitioner of the expected duration of the
>>>  Trustees' review of the appeal.  The Trustees shall review the
>>>  situation in a manner of its own choosing and report to the IETF on
>>>  the outcome of its review.
>>>
>>>  The Trustees' decision upon completion of their review shall be final
>>>  with respect to all aspects of the dispute.
>>>
>>> note that the appeal to the ISOC BopT is only if the claim is that the rules are broken 
>>> not the application of the rules
>> Exactly right. What Eliot said, and others have said, is that the ISOC board is the "final appellate avenue in the standardization process". That's quite different than "the rules are broken".
> just to be clear - saying "final appellate avenue in the standardization process". could be read as meaning
> that a appeal of a technical decision could be made to the ISOC Board and that is not the case - 
> this is why I used different language
>
> not sure which you were supporting
>
> Scott
>
>>> there has never been such an appeal
>>
>> Happily noted.
>>
>> --Paul Hoffman
>>
>
>

From sob@harvard.edu  Fri Jun  8 14:07:00 2012
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 299AB11E8194 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 14:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.289
X-Spam-Level: 
X-Spam-Status: No, score=-103.289 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 CYiheEzKlKRE for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 14:06:59 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 72F2E11E8192 for <ietf@ietf.org>; Fri,  8 Jun 2012 14:06:59 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000001.university.harvard.edu [10.35.2.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 13A93E8C03; Fri,  8 Jun 2012 17:06:59 -0400 (EDT)
Received: from ENTWHUBT0000006.university.harvard.edu (192.168.236.26) by ENTWEDGE0000001.university.harvard.edu (10.35.2.152) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 8 Jun 2012 17:06:01 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.61]) by ENTWHUBT0000006.university.harvard.edu ([192.168.236.28]) with mapi id 14.01.0355.002; Fri, 8 Jun 2012 17:06:33 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Thread-Topic: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Thread-Index: AQHNRRPjzeDlNmma+0yP4HiwzJMosQ==
Date: Fri, 8 Jun 2012 21:06:32 +0000
Message-ID: <C14F6D09-F395-4C57-98F3-EF07BDDA6112@harvard.edu>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org> <52CB44AB-006B-407F-AA44-976271B3E27E@harvard.edu> <03EE51C5-CDAB-471B-8DE2-DFB40CE1E93D@vpnc.org> <09A09092-51D1-4406-9387-5F988552BF8A@harvard.edu> <81AC4AD6-1EFC-405A-AD8F-B5AB03F2976D@vpnc.org>
In-Reply-To: <81AC4AD6-1EFC-405A-AD8F-B5AB03F2976D@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [173.166.5.69]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <DD1DFEFB1CEC82409EB6FC81185F54A1@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 21:07:00 -0000

wfm

On Jun 8, 2012, at 3:49 PM, Paul Hoffman wrote:

> On Jun 8, 2012, at 12:46 PM, Bradner, Scott wrote:
>=20
>> just to be clear - saying "final appellate avenue in the standardization=
 process". could be read as meaning
>> that a appeal of a technical decision could be made to the ISOC Board an=
d that is not the case -=20
>> this is why I used different language
>>=20
>> not sure which you were supporting
>=20
>=20
> I am supporting not putting anything about appeals to the ISOC Board in t=
he Tao. They do not apply to novices.
>=20
> --Paul Hoffman
>=20


From martin.thomson@gmail.com  Fri Jun  8 14:54:19 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3BC821F86E4 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 14:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.28
X-Spam-Level: 
X-Spam-Status: No, score=-4.28 tagged_above=-999 required=5 tests=[AWL=-0.681,  BAYES_00=-2.599, 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 VSPTUxPlMHAQ for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 14:54:19 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 25B2721F86E0 for <ietf@ietf.org>; Fri,  8 Jun 2012 14:54:18 -0700 (PDT)
Received: by bkty8 with SMTP id y8so2508338bkt.31 for <ietf@ietf.org>; Fri, 08 Jun 2012 14:54:18 -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=VqnJFSev2i4kvK/KZJmCFMm+GQmC70DjMaksu/yIi7U=; b=bXSfY5cA0mRGESxCAokNMh7gRt7NdU7g4Dy7wUbN5zkXqtyq/SZ9e+Mnj4++aglB78 busxFvll2Dz2M/czDOxm1Hg0TdgF6I+9JH9xiaxAWbWu20Lx5GRzG9BnAUlzTM82Sydp QQJiLtNgLhesjjQvGR5huuAD6v4a5aHfFTSXoLayw9sJ8g3nBk0zMWbBXwf4qXNKTy3M /6ZLIJFJDSY0M8iKiGaHQ2KMiyP+sS5sdEPGWtLhfucdpLXYf5usn7OkMqkKfx8pVbir orNmaN7o+J4EbcnzFn4jXycHD1NTc6k7LbGN3y0pBpVLWYdYvs+/ocIJbcWqaFL/WJPv YBIA==
MIME-Version: 1.0
Received: by 10.204.150.84 with SMTP id x20mr6848079bkv.26.1339192458229; Fri, 08 Jun 2012 14:54:18 -0700 (PDT)
Received: by 10.204.66.4 with HTTP; Fri, 8 Jun 2012 14:54:18 -0700 (PDT)
In-Reply-To: <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>
Date: Fri, 8 Jun 2012 14:54:18 -0700
Message-ID: <CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
From: Martin Thomson <martin.thomson@gmail.com>
To: Jonathan A Rees <rees@mumble.net>
Content-Type: text/plain; charset=UTF-8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 21:54:19 -0000

One small comment, that I know the authors are aware of...

On 6 June 2012 13:33, Jonathan A Rees <rees@mumble.net> wrote:
> I think using .well-known is a good idea.

I think that using .well-known is a bad idea.

This imposes an unnecessary restriction on the deployment of
resources.  /.well-known/ is a space that can only be deployed to by
an administrator of the system.  By identifying specifically where the
resource might live (potentially with more than one URL), this avoids
the deployment issue.

Yes, I am aware of the "extensions".

And:
> (a lot of other things)

I agree with all of this, the authority thing, the content-type thing.
 All of it.  (And none of the rebuttal.)

Nit:
The draft makes some strange statements about redirects.

   Put another way, a server SHOULD return a 30x response when a .well-
   known/ni URL is de-referenced.

Requiring a compliant HTTP implementation that follows redirects is
sufficient.  What the server does to serve this request is the
server's business.  Redirects seem likely, but 2119 language for the
server is not necessary for interoperation.

From stephen.farrell@cs.tcd.ie  Fri Jun  8 17:06:45 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13E0411E80E2 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 17:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.491
X-Spam-Level: 
X-Spam-Status: No, score=-102.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ckZYGlN8EO4o for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 17:06:36 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 4E90311E80DF for <ietf@ietf.org>; Fri,  8 Jun 2012 17:06:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id E7DBF154252; Sat,  9 Jun 2012 01:06:34 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339200394; bh=jFkZqGUUg7TmLb mZZjFseAcMyxxnOgYrhxyxNlVR+P8=; b=2cts98cWV7hfv4TGVOOaXPVyTapJuA tFgmC9wOYRC3PMH0+MH+1VZvIHW1Pwg1HqcUhoKyvkRzv2MpRx664IBJmG2B48wE SJ6nQhyDVZ9DXhJZ0QRVzPqpTPqeD20NIh1k9hnrQ2VnVbmQ/McXeNHcCNSTwWxj y0T3Zgg8gTA7SwHX3EA4z0Xe9FpfN+pup4XQ/li5q8q7ZuaTBBjPhjeobpceSOBD zOhozd9B5zAEuwAkb3LMP4YEjQPVlHbqp8qaZmTjom8EjMYw5JYFcJgK9eoBW6wb 0wUU/01qYkPxGDHs++d2c3gAHTbOdDnceTHx4DKAWdlsvpsrGUVVOS9A==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id wAr1sTen3K33; Sat,  9 Jun 2012 01:06:34 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.46.22.45]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id CDDD8154251; Sat,  9 Jun 2012 01:06:33 +0100 (IST)
Message-ID: <4FD29389.5060900@cs.tcd.ie>
Date: Sat, 09 Jun 2012 01:06:33 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com> <CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com>
In-Reply-To: <CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Jonathan A Rees <rees@mumble.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 00:06:45 -0000

Hi Martin,

On 06/08/2012 10:54 PM, Martin Thomson wrote:
> One small comment, that I know the authors are aware of...
> 
> On 6 June 2012 13:33, Jonathan A Rees <rees@mumble.net> wrote:
>> I think using .well-known is a good idea.
> 
> I think that using .well-known is a bad idea.

Ok. Opinions vary.

> This imposes an unnecessary restriction on the deployment of
> resources.  /.well-known/ is a space that can only be deployed to by
> an administrator of the system.  By identifying specifically where the
> resource might live (potentially with more than one URL), this avoids
> the deployment issue.
> 
> Yes, I am aware of the "extensions".

I don't get what you mean above. If its something that
implies a change, I don't know what change.

> And:
>> (a lot of other things)
> 
> I agree with all of this, the authority thing, the content-type thing.
>  All of it.  (And none of the rebuttal.)

So the probability of us being completely correct in all this is
probably infinitesimally small, but equal to the probability
of us being completely wrong. That would imply that our rebuttals
are not completely wrong and hence you are equally wrong in
saying "all" and "none" above. (Isn't sophistry great:-)

Anyway, I take that as another +1 for adding ct= to this draft
which is fine. I'm starting to think that might be a good plan.
Let's see if others (dis)agree during the rest of IETF LC.

I also take that as another claim that our use of the
authority field is somehow "wrong" for what seem to me to
be near-mystical reasons, with no compelling argument offered
as to any bad effects at all ensuing. I'm still entirely happy
that our current design is good enough as-is. For me, running
code is a winner in that part of the argument.

> Nit:
> The draft makes some strange statements about redirects.
> 
>    Put another way, a server SHOULD return a 30x response when a .well-
>    known/ni URL is de-referenced.
> 
> Requiring a compliant HTTP implementation that follows redirects is
> sufficient.  What the server does to serve this request is the
> server's business.  Redirects seem likely, but 2119 language for the
> server is not necessary for interoperation.

Good point. I've tweaked that a bit in response to Bjoern's
comments, but your suggestion above is better than what I
have now so I'll work that in. (Actually, is client support
for 3xx mandatory according to 2616? Not sure myself.)

Thanks,
S.


> 

From hartmans@mit.edu  Fri Jun  8 17:43:52 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5645E11E81B4 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 17:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.258
X-Spam-Level: 
X-Spam-Status: No, score=-103.258 tagged_above=-999 required=5 tests=[AWL=-0.993, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 TUgY+W7GQWAU for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 17:43:52 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id E1A8411E816E for <ietf@ietf.org>; Fri,  8 Jun 2012 17:43:51 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 7825C20424; Fri,  8 Jun 2012 20:43:38 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id C0D444151; Fri,  8 Jun 2012 20:43:48 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com> <CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com> <4FD29389.5060900@cs.tcd.ie>
Date: Fri, 08 Jun 2012 20:43:48 -0400
In-Reply-To: <4FD29389.5060900@cs.tcd.ie> (Stephen Farrell's message of "Sat,  09 Jun 2012 01:06:33 +0100")
Message-ID: <tslboktwbzv.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Jonathan A Rees <rees@mumble.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 00:43:52 -0000

Add me as a +1 for the idea that content-type is important for this.
I tend to agree with the arguments given so far. Namely, for some
important use cases you're going to want to know the content type and
guessing is  really a bad idea.

That said, there are security considerations associated with specifying
a content type too.  I'm particularly imagining a situation where some
sort of deep inspection security appliance uses a different procedure
for deciding what kind of foo it is than the ultimate application. One
guesses based on byte stream another looks at a content type.  This is
well known; it's not new; it's probably even so documented that any
reasonably current set of MIME security considerations already includes
a reference.


I agree that your draft does not use the authority portion of a URI
consistent with section 3.2 of RFC 3986. The authority separates the
namespace exactly the way it doesn't in your scheme. It's a naming
hierarchy.  My main concern is whether the relative reference algorithm
described in section 5/4.2 of RFC 3986. In particular take a look at the
last part of section 1.2 of RFC 3986 regarding the disallowing of
/. Consider how you want relative references in an HTML document
resolved through a ni: URI to work.  I don't think your use of authority
provides good results. However I'm not sure that better results would be
achieved without hierarchy.  I hope though that these comments will help
inject some ways of reasoning about authority that are less mystical and
that lead to more practical discussion.

From stewe@stewe.org  Fri Jun  8 17:52:30 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78BFD11E81B4 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 17:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.027
X-Spam-Level: 
X-Spam-Status: No, score=-4.027 tagged_above=-999 required=5 tests=[AWL=-0.428, BAYES_00=-2.599, 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 mhVoImQe9x9g for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 17:52:28 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe001.messaging.microsoft.com [213.199.154.139]) by ietfa.amsl.com (Postfix) with ESMTP id D212F11E8163 for <ietf@ietf.org>; Fri,  8 Jun 2012 17:52:27 -0700 (PDT)
Received: from mail62-db3-R.bigfish.com (10.3.81.237) by DB3EHSOBE003.bigfish.com (10.3.84.23) with Microsoft SMTP Server id 14.1.225.23; Sat, 9 Jun 2012 00:51:35 +0000
Received: from mail62-db3 (localhost [127.0.0.1])	by mail62-db3-R.bigfish.com (Postfix) with ESMTP id B257830059A; Sat,  9 Jun 2012 00:51:34 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT001.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zz98dI1432I853kzz1202h1082kzz1033IL8275dhz2fh2a8h668h839h944he5bhf0ah)
Received-SPF: pass (mail62-db3: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT001.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail62-db3 (localhost.localdomain [127.0.0.1]) by mail62-db3 (MessageSwitch) id 1339203091170130_9207; Sat,  9 Jun 2012 00:51:31 +0000 (UTC)
Received: from DB3EHSMHS004.bigfish.com (unknown [10.3.81.237])	by mail62-db3.bigfish.com (Postfix) with ESMTP id 1D7AF2A0048; Sat,  9 Jun 2012 00:51:31 +0000 (UTC)
Received: from BL2PRD0710HT001.namprd07.prod.outlook.com (157.56.240.133) by DB3EHSMHS004.bigfish.com (10.3.87.104) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sat, 9 Jun 2012 00:51:30 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.169]) by BL2PRD0710HT001.namprd07.prod.outlook.com ([10.255.102.36]) with mapi id 14.16.0164.004; Sat, 9 Jun 2012 00:52:20 +0000
From: Stephan Wenger <stewe@stewe.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
Thread-Topic: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
Thread-Index: AQHNJvVjc3gJqOC7qk+8cEdjIpewVJbxh9+A
Date: Sat, 9 Jun 2012 00:52:20 +0000
Message-ID: <CBF86A27.87CA2%stewe@stewe.org>
In-Reply-To: <CBC48C89.8671C%stewe@stewe.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B8DECACA24E925429AE236DEB3EB49E8@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "psaintan@cisco.com" <psaintan@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 00:52:30 -0000

Hi,
I want to thank Peter and Tim to take my comments into account in version
4 of this document.  I'm happy with version this version.
Regards,
Stephan


On 4.30.2012 19:19 , "Stephan Wenger" <stewe@stewe.org> wrote:

>Hi,
>Here are a few comments to this draft.
>Stephan
>
>(1) Section 3.1, final paragraph.  An IETF disclosure has to be made
>against a Contribution.  In the case described in this paragraph, the
>Contribution may not have been made at the time of the Disclosure request,
>and, therefore, it would be impossible to make a Disclosure.  For example,
>if someone wants to discuss a technology verbally, you cannot make an IPR
>disclosure before the words have been uttered.  I would remove this
>paragraph.  Alternatively, limit it to "materials you plan to make
>available at the meeting" in the sprit it of section 4.1.
>
>(2) Section 3.2, "silence may be interpreted as a weak "No".".  This
>statement is IMO not supported by the IETF patent policy, and should
>therefore be removed.  Generally speaking, any additional burden to
>non-Contributors beyond making them aware of the voluntary disclosure
>opportunity IMP constitutes a policy change and must be avoided.
>
>(3) Section 3.3.  I would replace "author" with "authors and other
>Contributors".  Or "known Contributors", "prominent Contributors", or
>something like this.  It is entirely possible, and in fact not uncommon,
>that non-author Contributors influence the technology choices of I-Ds.
>One possible metric for identifying some of these Contributors would be a
>review of the Acknowledgement section many I-Ds include.  I see this
>mentioned in section 3.4; I would shift (or duplicate?) the burden of
>double-checking with Contributors to the WG chairs as WGLC.
>
>(4) Section 4.2.  Suggest to include Contributors in the spirit of comment
>(3) above.
>
>(5) Section A.1.  The email has a logical structure, but sometimes a
>logical structure may not have the best effect.  As written, people will
>probably not read it in its entirety, but will give up once its clear that
>it includes legalese.  Suggest to move the final paragraph "As FOO WG
>chairs" to the top, and put the formal justification stuff at the end.
>
>(6) Section A.2: I would substitute "Dear FOO WG" with "Dear FOO WG and
>especially authors and Contributors:"
>
>(7) Section A.2, third paragraph, sentence "We will not be able to advance
>this document to the next stage until we have received a reply from each
>author and listed contributor."  If this sentence starts appearing with
>some consistency in IETF WGs, then we have a de-facto policy change
>(requiring affirmative negative declarations).  Suggest to soften the
>language: "we may not be able to advance" or "it does not appear to be
>sensible to us to advance"
>
>(8) Section A.2, fourth paragraph: I would express this along the
>following: "you are reminded of your opportunity for a voluntary IPR
>disclosure under BCP79 section xxx.  Unless you want to make such a
>voluntary disclosure, please do not reply."
>
>(9) Section A.3, see previous comments (7) and (8).
>=20
>(10) Section A.4, see previous comment (7)
>
>(11) Section A.5, see previous comment (7)
>
>=20
>
>On 4.30.2012 18:27 , "The IESG" <iesg-secretary@ietf.org> wrote:
>
>>
>>The IESG has received a request from an individual submitter to consider
>>the following document:
>>- 'Promoting Compliance with Intellectual Property Rights (IPR)
>>   Disclosure Rules'
>>  <draft-polk-ipr-disclosure-03.txt> as Informational RFC
>>
>>The IESG plans to make a decision in the next few weeks, and solicits
>>final comments on this action. Please send substantive comments to the
>>ietf@ietf.org mailing lists by 2012-05-28. Exceptionally, comments may be
>>sent to iesg@ietf.org instead. In either case, please retain the
>>beginning of the Subject line to allow automated sorting.
>>
>>Abstract
>>
>>
>>   The disclosure process for intellectual property rights (IPR) in
>>   documents produced within the IETF stream is essential to the
>>   accurate development of community consensus.  However, this process
>>   is not always followed by participants during IETF standardization.
>>   Regardless of the cause or motivation, noncompliance with IPR
>>   disclosure rules can derail or delay completion of standards
>>   documents.  This document describes strategies for promoting
>>   compliance with the IPR disclosure rules.  The strategies are
>>   primarily intended for area directors, working group chairs, and
>>   working group secretaries.
>>
>>
>>
>>
>>The file can be obtained via
>>http://datatracker.ietf.org/doc/draft-polk-ipr-disclosure/
>>
>>IESG discussion can be tracked via
>>http://datatracker.ietf.org/doc/draft-polk-ipr-disclosure/ballot/
>>
>>
>>No IPR declarations have been submitted directly on this I-D.
>>
>>
>>
>



From glenzorn@gmail.com  Fri Jun  8 18:03:19 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15F9011E816E for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 18:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 C7MBUHa-OI+9 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 18:03:18 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9039A11E812B for <ietf@ietf.org>; Fri,  8 Jun 2012 18:03:18 -0700 (PDT)
Received: by dacx6 with SMTP id x6so3033489dac.31 for <ietf@ietf.org>; Fri, 08 Jun 2012 18:03:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=KfEQ6FvfG/u2zBTKLAf10kYT3sgxHrpNrnlF2UnEzNY=; b=SDwI8V46+YcLVgitKgKlQsi6qZgFvCuYUSlAztDXGf3gBuBtJJ/MEKUXpdrFcarqc4 /qO9jwpeVAaZOvuvysULE2nI0AYEUm1kuYyApwyLqXxAbOCde8D1MiXOZAm+U5p1jxpx at5j8NFzwk2OQ5xhLQMOKm5cllBpr5vtfGk7Kps9OmLE9OtxddVVUQ/T7Q+wnoKI0EzZ a9h+6HQq9KX1ch9o6H97AhRZm0LVoLBDGBbYdkSt8luXpklEtcsV2UoCDaZsQnOaaJhX p4gI99BObMK7fcwTfFXoZY5wHXo1s9tQOYFhUEcpoNEPllr4OY6ig8x69yCJTGC4Gwgy WHow==
Received: by 10.68.223.129 with SMTP id qu1mr554235pbc.165.1339203798414; Fri, 08 Jun 2012 18:03:18 -0700 (PDT)
Received: from [192.168.1.99] (ppp-124-120-25-74.revip2.asianet.co.th. [124.120.25.74]) by mx.google.com with ESMTPS id ku7sm9580425pbc.31.2012.06.08.18.03.16 (version=SSLv3 cipher=OTHER); Fri, 08 Jun 2012 18:03:17 -0700 (PDT)
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org>
Content-Type: text/plain; charset="UTF-8"
Organization: Network Zen
Date: Sat, 09 Jun 2012 08:03:14 +0700
Message-ID: <1339203794.6353.8.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
Content-Transfer-Encoding: 8bit
Cc: glenzorn@cmail.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 01:03:19 -0000

On Thu, 2012-06-07 at 16:09 -0700, Paul Hoffman wrote:


...

> > 	â€¢ The Tao mentions that we meet once a year in each region.  I don't think that's true for Asia at this point.  The text might call out that we meet where there are participants, or words that the IAOC might provide.
> 
> It doesn't say that. It says "approximately once a year in each region". That is still true.

A quick check of the "Upcoming IETF Meetings" calendar
(http://www.ietf.org/meeting/upcoming.html) shows that the next meeting
in Asia is scheduled for November 2015, while the last was November
2011.  How does a 4 year gap map to "approximately once a year"?

...


From stephen.farrell@cs.tcd.ie  Fri Jun  8 18:45:29 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD08211E809C for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 18:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level: 
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 VeW8b6CgT70C for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 18:45:29 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id DE6CF11E8079 for <ietf@ietf.org>; Fri,  8 Jun 2012 18:45:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 2B0AB154252; Sat,  9 Jun 2012 02:45:28 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339206327; bh=IR2XYEwxzS7qVo Scn1kyqc7/Icn8OJqjtJaUzHdK2j8=; b=o+W5eMki1AKOwHbQdxbIHHa1r766EA Hfue6ytm8vUxL9PfydTi6uAHZWezKWsoEL0I5NQ8xOdyLwrmkKkkFZUPpfYyPkaE 4JPhl462zXLdokH6lCHX9R8Z8SHY+u8SDZg15NgL4xPLW0quo0kZCCROL45N6Vy8 zOKWgwkVZLC1TtB1agHDEGgUJcH0+9VXc1Qp81d0NG2qBdygABwQNwyGtsHQqBiw llolsgqbV/EwL+enImC4sShe3JHE6As6aHqFTySwwE9vvq7kpcGD+KELojypMrXm PqXZW0WCfHR1zLalEtajtPxJ7NS8fU/5mDa6zCzC7E88H7KL7Pl5XjbA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id XMYz8auwxIaE; Sat,  9 Jun 2012 02:45:27 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.46.22.45]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id A8E4B154251; Sat,  9 Jun 2012 02:45:23 +0100 (IST)
Message-ID: <4FD2AAB3.4010305@cs.tcd.ie>
Date: Sat, 09 Jun 2012 02:45:23 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com> <CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com> <4FD29389.5060900@cs.tcd.ie> <tslboktwbzv.fsf@mit.edu>
In-Reply-To: <tslboktwbzv.fsf@mit.edu>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Jonathan A Rees <rees@mumble.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 01:45:30 -0000

Hi Sam,

On 06/09/2012 01:43 AM, Sam Hartman wrote:
> Add me as a +1 for the idea that content-type is important for this.
> I tend to agree with the arguments given so far. Namely, for some
> important use cases you're going to want to know the content type and
> guessing is  really a bad idea.

Thusly counted:-)

> 
> That said, there are security considerations associated with specifying
> a content type too.  I'm particularly imagining a situation where some
> sort of deep inspection security appliance uses a different procedure
> for deciding what kind of foo it is than the ultimate application. One
> guesses based on byte stream another looks at a content type.  This is
> well known; it's not new; it's probably even so documented that any
> reasonably current set of MIME security considerations already includes
> a reference.

My only real concern with adding this is the issue of complexity
related to c14n of input to the hash function. While CMS does (I
think) define that well, imposing that burden on anyone that might
want to write code that validates name-data integrity is an issue.
Anyway, if we want to add it we'll look that over and figure how
it might best be done.

> I agree that your draft does not use the authority portion of a URI
> consistent with section 3.2 of RFC 3986. 

I honestly don't get that. I think we are "consistent" with 3986
(there being no MUST/SHOULD with which we're in conflict afaik)
but the authority field here is not identical to that for HTTP
URLs. And that's ok.

> The authority separates the
> namespace exactly the way it doesn't in your scheme. 

Yes there are differences and maybe we ought try describe that
somehow.

> It's a naming
> hierarchy.  My main concern is whether the relative reference algorithm
> described in section 5/4.2 of RFC 3986. In particular take a look at the
> last part of section 1.2 of RFC 3986 regarding the disallowing of
> /. Consider how you want relative references in an HTML document
> resolved through a ni: URI to work.  I don't think your use of authority
> provides good results. However I'm not sure that better results would be
> achieved without hierarchy.  I hope though that these comments will help
> inject some ways of reasoning about authority that are less mystical and
> that lead to more practical discussion.

Thanks.

I think your comment about relative URIs is fair and we maybe ought
say there are no such things for ni URIs. (Or however that kind of
thing is stated best).

I guess a sentence or two about relative URIs would be worthwhile
and I'll ponder that.

S.


> 
> 

From hartmans@mit.edu  Fri Jun  8 19:11:44 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4DD111E8099 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 19:11:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.264
X-Spam-Level: 
X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
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 gEC16wpupJg7 for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 19:11:44 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 17C7E11E8095 for <ietf@ietf.org>; Fri,  8 Jun 2012 19:11:44 -0700 (PDT)
Received: from [100.248.163.15] (ma02436d0.tmodns.net [208.54.36.160]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id 2A00120424; Fri,  8 Jun 2012 22:11:28 -0400 (EDT)
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com> <CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com> <4FD29389.5060900@cs.tcd.ie> <tslboktwbzv.fsf@mit.edu> <4FD2AAB3.4010305@cs.tcd.ie>
User-Agent: K-9 Mail for Android
In-Reply-To: <4FD2AAB3.4010305@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----6PEQHQDHU7B1CXSRIRM9CZATQTU99R"
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
From: hartmans@mit.edu
Date: Fri, 08 Jun 2012 22:11:00 -0400
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Sam Hartman <hartmans-ietf@mit.edu>
Message-ID: <bf122efe-782b-4363-a380-f23439400df1@email.android.com>
Cc: Jonathan A Rees <rees@mumble.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 02:11:45 -0000

------6PEQHQDHU7B1CXSRIRM9CZATQTU99R
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit



Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:


Hi Sam,

On 06/09/2012 01:43 AM, Sam Hartman wrote:
> Add me as a +1 for the idea that content-type is important for this.
> I tend to agree with the arguments given so far. Namely, for some
> important use cases you're going to want to know the content type and
> guessing is really a bad idea.

Thusly counted:-)

> 
> That said, there are security considerations associated with specifying
> a content type too. I'm particularly imagining a situation where some
> sort of deep inspection security appliance uses a different procedure
> for deciding what kind of foo it is than the ultimate application. One
> guesses based on byte stream another looks at a content type. This is
> well known; it's not new; it's probably even so documented that any
> reasonably current set of MIME security considerations already includes
> a reference.

My only real concern with adding this is the issue of complexity
related to c14n of input to the hash function. While CMS does (I
think) define that well, imposing that burden on anyone that might
want to write code that validates name-data integrity is an issue.
Anyway, if we want to add it we'll look that over and figure how
it might best be done.

> I agree that your draft does not use the authority portion of a URI
> consistent with section 3.2 of RFC 3986. 

I honestly don't get that. I think we are "consistent" with 3986
(there being no MUST/SHOULD with which we're in conflict afaik)
but the authority field here is not identical to that for HTTP
URLs. And that's ok.

> The authority separates the
> namespace exactly the way it doesn't in your scheme. 

Yes there are differences and maybe we ought try describe that
somehow.

> It's a naming
> hierarchy. My main concern is whether the relative reference algorithm
> described in section 5/4.2 of RFC 3986. In particular take a look at the
> last part of section 1.2 of RFC 3986 regarding the disallowing of
> /. Consider how you want relative references in an HTML document
> resolved through a ni: URI to work. I don't think your use of authority
> provides good results. However I'm not sure that better results would be
> achieved without hierarchy. I hope though that these comments will help
> inject some ways of reasoning about authority that are less mystical and
> that lead to more practical discussion.

Thanks.

I think your comment about relative URIs is fair and we maybe ought
say there are no such things for ni URIs. (Or however that kind of
thing is stated best).

I guess a sentence or two about relative URIs would be worthwhile
and I'll ponder that.

S.


> 
> 


------6PEQHQDHU7B1CXSRIRM9CZATQTU99R
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<html><head></head><body><br><br><div class="gmail_quote">Stephen Farrell &lt;stephen.farrell@cs.tcd.ie&gt; wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif"><br />Hi Sam,<br /><br />On 06/09/2012 01:43 AM, Sam Hartman wrote:<br />&gt; Add me as a +1 for the idea that content-type is important for this.<br />&gt; I tend to agree with the arguments given so far. Namely, for some<br />&gt; important use cases you're going to want to know the content type and<br />&gt; guessing is  really a bad idea.<br /><br />Thusly counted:-)<br /><br />&gt; <br />&gt; That said, there are security considerations associated with specifying<br />&gt; a content type too.  I'm particularly imagining a situation where some<br />&gt; sort of deep inspection security appliance uses a different procedure<br />&gt; for deciding what kind of foo it is than the ultimate application. One<br />&gt; guesses based on byte stream another looks at a content type.  This is<br />&gt; well known; it's not new; it's probably even so documented that any<br />&gt; reasonably current set o
 f MIME
security considerations already includes<br />&gt; a reference.<br /><br />My only real concern with adding this is the issue of complexity<br />related to c14n of input to the hash function. While CMS does (I<br />think) define that well, imposing that burden on anyone that might<br />want to write code that validates name-data integrity is an issue.<br />Anyway, if we want to add it we'll look that over and figure how<br />it might best be done.<br /><br />&gt; I agree that your draft does not use the authority portion of a URI<br />&gt; consistent with section 3.2 of RFC 3986. <br /><br />I honestly don't get that. I think we are "consistent" with 3986<br />(there being no MUST/SHOULD with which we're in conflict afaik)<br />but the authority field here is not identical to that for HTTP<br />URLs. And that's ok.<br /><br />&gt; The authority separates the<br />&gt; namespace exactly the way it doesn't in your scheme. <br /><br />Yes there are differences and maybe we ought
  try
describe that<br />somehow.<br /><br />&gt; It's a naming<br />&gt; hierarchy.  My main concern is whether the relative reference algorithm<br />&gt; described in section 5/4.2 of RFC 3986. In particular take a look at the<br />&gt; last part of section 1.2 of RFC 3986 regarding the disallowing of<br />&gt; /. Consider how you want relative references in an HTML document<br />&gt; resolved through a ni: URI to work.  I don't think your use of authority<br />&gt; provides good results. However I'm not sure that better results would be<br />&gt; achieved without hierarchy.  I hope though that these comments will help<br />&gt; inject some ways of reasoning about authority that are less mystical and<br />&gt; that lead to more practical discussion.<br /><br />Thanks.<br /><br />I think your comment about relative URIs is fair and we maybe ought<br />say there are no such things for ni URIs. (Or however that kind of<br />thing is stated best).<br /><br />I guess a sentence or two
  about
relative URIs would be worthwhile<br />and I'll ponder that.<br /><br />S.<br /><br /><br />&gt; <br />&gt; <br /><br /></pre></blockquote></div></body></html>
------6PEQHQDHU7B1CXSRIRM9CZATQTU99R--


From stephen.farrell@cs.tcd.ie  Sat Jun  9 06:24:53 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76ED821F84A1 for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 06:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kAt8vpBRgMSC for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 06:24:52 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 9834821F84A0 for <ietf@ietf.org>; Sat,  9 Jun 2012 06:24:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id A5629171802; Sat,  9 Jun 2012 14:24:48 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339248288; bh=ZYYEsvovb5uXNo BCtdsspLd3My7+0SRCh7M9vcKCTT4=; b=cdkSfrbasnrgTA0wU4MhqpgL/JnJiv Rmqtw/V+zra9V2CT76E0J3uaemWTEqQiipHa0tff6w0zgN/e7F3kni3WK/5EaqOU pus1g/SE7WyPHSRcyN5YKHqZwl69sRiIbWXXsPvj3Z8S/kshK/Gip5fqqPCgA7rd Fam0143gK27o1NtcmQmU+WJF4wBZ4ll/cn7hXLW1K93h0raAE/8+MjjRisg281CQ PGLlGfRmMGWeKhR8WMdqicGpYPSrVs1acwph9qV8xIUt92JIwNxlYHrbDSijMED+ BdyBYYt5yf7n8eQCmi2Jctol0zq3gt0HbE/Ta7ZsG6/XYfcapR1GrFyw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id OQ3xmB7Y0B0k; Sat,  9 Jun 2012 14:24:48 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.41.9.170]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id CA7DE1714DD; Sat,  9 Jun 2012 14:24:47 +0100 (IST)
Message-ID: <4FD34E9F.4060904@cs.tcd.ie>
Date: Sat, 09 Jun 2012 14:24:47 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: Comments on draft-farrell-decade-ni-06
References: <6kk2t71ghjalf43tqu14pvcnisoarv924g@hive.bjoern.hoehrmann.de>
In-Reply-To: <6kk2t71ghjalf43tqu14pvcnisoarv924g@hive.bjoern.hoehrmann.de>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 13:24:53 -0000

Hi Björn,

On 06/08/2012 03:16 AM, Bjoern Hoehrmann wrote:
> I think the requirement in RFC 4395 section 2.6 applies here, there are
> text fields in 'ni' and 'nih' addresses, so there needs to be some dis-
> cussion about I18N and IRI issues, or a statement that there are none,
> or something along those lines. What if I want a non-ASCII host name in
> them, for instance?

So what's reasonable here?

We're inheriting some definitions (authority, unreserved &
pct-encoded) from 3986 and I'd not like to break that, nor
would I like something that doesn't work with most libraries.

Any suggestions?

Thanks,
S.


From paul.hoffman@vpnc.org  Sat Jun  9 15:19:58 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84DE421F85E3 for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 15:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 xNgS6NLeme6g for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 15:19:58 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id A3B7E21F8589 for <ietf@ietf.org>; Sat,  9 Jun 2012 15:19:57 -0700 (PDT)
Received: from [10.20.30.101] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q59MJsfd007021 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 9 Jun 2012 15:19:55 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Publishing the Tao as a web page
Date: Sat, 9 Jun 2012 15:19:53 -0700
Message-Id: <CC1638DA-817E-4F2C-BD29-5EFED6CFCAEF@vpnc.org>
To: "<ietf@ietf.org> list" <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 22:19:59 -0000

See draft-hoffman-tao-as-web-page-00, just published. I am the editor of =
that draft, but the ideas in it come from the IESG. The IESG didn't =
pre-review the draft, but it is based on what I was told was agreed to =
during the IESG telechat on Thursday.

--Paul Hoffman


From glenzorn@gmail.com  Sat Jun  9 17:13:15 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7996821F8648 for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 17:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 37YzZdIBYCpF for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 17:13:15 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0C7CC21F8647 for <ietf@ietf.org>; Sat,  9 Jun 2012 17:13:14 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so4023635pbc.31 for <ietf@ietf.org>; Sat, 09 Jun 2012 17:13:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:content-type:organization:date:message-id :mime-version:x-mailer:content-transfer-encoding; bh=5Zlfgrnu9gTEN2PXT5EFLG3gsd+7c6bit+RH18Gyayw=; b=0DV0rzX+ThTA7933n5xJMBcBl3zSQRQ+Vn9OQJwNJNjiQLuRATT01UxBpO1QX9R99J LiA4VAEYWwM+oCmfru545do2gihxOr4rF8g4bindBMhCmtlznbIUbgcKqKpO89hu25KD rRkgx+oZ7K3W+tAPul+xOpvMC29yPOYURtWpCjK0ekUPsya+1HI3xLwYWZ0VVGCZyhSF Lq+YMld/xyIVUdNYufv182BKNYqguh8Vp6eKvlXA2rLbNBZZwkoZUJlj/dFhemHDi9bP W4OdxfRMmlShiYdoQDgPFpg4WJOI0ZTRU96YMw0LT5Gt4MIWJhxbBpUwTBY2uqBMgJmY qTXg==
Received: by 10.68.224.70 with SMTP id ra6mr11080761pbc.11.1339287194465; Sat, 09 Jun 2012 17:13:14 -0700 (PDT)
Received: from [192.168.1.99] (ppp-115-87-100-230.revip4.asianet.co.th. [115.87.100.230]) by mx.google.com with ESMTPS id tj4sm12951601pbc.33.2012.06.09.17.13.12 (version=SSLv3 cipher=OTHER); Sat, 09 Jun 2012 17:13:13 -0700 (PDT)
Subject: [Fwd: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Organization: Network Zen
Date: Sun, 10 Jun 2012 07:13:10 +0700
Message-ID: <1339287190.6353.11.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 00:13:15 -0000

Looks like this didn't get through the first time.

> From: Glen Zorn <glenzorn@gmail.com>
> To: ietf@ietf.org
> Cc: glenzorn@cmail.com
> Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of
> IETF: A Novice's Guide to the Internet Engineering Task Force) to
> Informational RFC
> Date: Sat, 09 Jun 2012 08:03:14 +0700
> 
> On Thu, 2012-06-07 at 16:09 -0700, Paul Hoffman wrote:
> 
> 
> ...
> 
> > > 	â€¢ The Tao mentions that we meet once a year in each region.  I don't think that's true for Asia at this point.  The text might call out that we meet where there are participants, or words that the IAOC might provide.
> > 
> > It doesn't say that. It says "approximately once a year in each region". That is still true.
> 
> A quick check of the "Upcoming IETF Meetings" calendar
> (http://www.ietf.org/meeting/upcoming.html) shows that the next meeting
> in Asia is scheduled for November 2015, while the last was November
> 2011.  How does a 4 year gap map to "approximately once a year"?
> 
> ...
> 



From randy@psg.com  Sat Jun  9 17:33:04 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF7B521F8630 for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 17:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level: 
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=0.097,  BAYES_00=-2.599]
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 mkGNLLncGrjR for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 17:33:04 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 81C6521F860B for <ietf@ietf.org>; Sat,  9 Jun 2012 17:33:04 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SdW5X-000OG4-Cg; Sun, 10 Jun 2012 00:33:03 +0000
Date: Sat, 09 Jun 2012 17:33:02 -0700
Message-ID: <m2r4togg5d.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Glen Zorn <glenzorn@gmail.com>
Subject: Re: [Fwd: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of	IETF: A Novice's Guide to the Internet Engineering Task Force) to	Informational RFC]
In-Reply-To: <1339287190.6353.11.camel@gwz-laptop>
References: <1339287190.6353.11.camel@gwz-laptop>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 00:33:05 -0000

> A quick check of the "Upcoming IETF Meetings" calendar
> (http://www.ietf.org/meeting/upcoming.html) shows that the next
> meeting in Asia is scheduled for November 2015, while the last was
> November 2011.  How does a 4 year gap map to "approximately once a
> year"?

this winter we are meeting in georgia (not the one in the caucasus) and
florida.  what more diversity do you want?  canada?

randy

From ole@cisco.com  Sat Jun  9 18:10:01 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 243D121F8543 for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 18:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.799
X-Spam-Level: 
X-Spam-Status: No, score=-110.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 jnCoRs4nwUm4 for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 18:10:00 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 530A921F853F for <ietf@ietf.org>; Sat,  9 Jun 2012 18:10:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=818; q=dns/txt; s=iport; t=1339290600; x=1340500200; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=LZeGbjrNZh/g6tcIfw+LSZucBrE8FqwZud7KEpmNgoQ=; b=Pc4EJRc5YAE7qVC1W/bzA/qpPqoSCAA1BtAgNfUa83SKctZvvjcsjjgw X42EpMVFhy31A1WqiuLiTynJ7KBuqeCXNcIiDDY61S+Wd9bFh4nAv8jnP 314A9QVhklD5IUcYbzeSo1B+Egj1f7dUV8TghmL6uuriySY9xcLGl5JU2 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIzz00+rRDoG/2dsb2JhbABBA7RagQeCGQEBBBIBAiU/EAs7C1cGEwkZh2gMmFODRxCbKosnGoIvgyADiECXX4MUgQRigwCBPw
X-IronPort-AV: E=Sophos;i="4.75,744,1330905600"; d="scan'208";a="45231333"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 10 Jun 2012 01:10:00 +0000
Received: from sjc-vpn6-829.cisco.com (sjc-vpn6-829.cisco.com [10.21.123.61]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q5A19xam005283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);  Sun, 10 Jun 2012 01:09:59 GMT
Date: Sat, 9 Jun 2012 18:09:58 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Glen Zorn <glenzorn@gmail.com>
Subject: Re: [Fwd: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
In-Reply-To: <1339287190.6353.11.camel@gwz-laptop>
Message-ID: <alpine.OSX.2.01.1206091807030.38431@sjc-vpn6-829.cisco.com>
References: <1339287190.6353.11.camel@gwz-laptop>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 01:10:01 -0000

The intended rotation cycle is still 1-1-1 for NA-EU-AP regions, but 
it's all dependent on finding suitable and available venues and 
willing hosts and sponsors. Changing the text of the document would
imply a change in "policy" or "normal state of things" which there
hasn't been.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Sun, 10 Jun 2012, Glen Zorn wrote:

 A quick check of the "Upcoming IETF Meetings" calendar
 (http://www.ietf.org/meeting/upcoming.html) shows that the next meeting
 in Asia is scheduled for November 2015, while the last was November
 2011.  How does a 4 year gap map to "approximately once a year"?

From glenzorn@gmail.com  Sat Jun  9 22:05:18 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D02521F8685 for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 22:05:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[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 sYaRTX761Boa for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 22:05:17 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id CD3F921F866A for <ietf@ietf.org>; Sat,  9 Jun 2012 22:05:14 -0700 (PDT)
Received: by dacx6 with SMTP id x6so3982147dac.31 for <ietf@ietf.org>; Sat, 09 Jun 2012 22:05:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=sWnJ9uhHx31RoJOfOrmQXNwQhdwqVmy9aZ/Ylz/jHmo=; b=D8ud6oUIOQhgUvOZHqHgxdTuGYOBcizj9wj524MSieQD6gTQJsuLnaH2tCm1TG73td t36F0XWOuyAHYktcSU4cPkTx6BAbHQf/2ZtPvc+DEw32ad6EzejpfNy/kDqy9n+TvAjE PkMPRb+2LzSha5pvdzaEZwVLKtpw/QLb3PNndMbJiLnUcoBjPBwAX4nr7+0+Kq9VGjgJ n1U95PStafZnNVxqQds0fdtq1D/N2RgF/Q5yL7Kv4SLNZz9f48dfyy7PoILp1gVgA14f gAGYtLLmJAOMaUvEzzuZZtPz2HTdogtDqvi4fSa/sCFpUyBieINcIj6uU4rTBpeeBIRh o4VQ==
Received: by 10.68.200.197 with SMTP id ju5mr12684180pbc.19.1339304714582; Sat, 09 Jun 2012 22:05:14 -0700 (PDT)
Received: from [192.168.1.99] (ppp-124-122-245-196.revip2.asianet.co.th. [124.122.245.196]) by mx.google.com with ESMTPS id ru4sm13663207pbc.66.2012.06.09.22.05.12 (version=SSLv3 cipher=OTHER); Sat, 09 Jun 2012 22:05:13 -0700 (PDT)
Subject: Re: [Fwd: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
From: Glen Zorn <glenzorn@gmail.com>
To: Ole Jacobsen <ole@cisco.com>
In-Reply-To: <alpine.OSX.2.01.1206091807030.38431@sjc-vpn6-829.cisco.com>
References: <1339287190.6353.11.camel@gwz-laptop> <alpine.OSX.2.01.1206091807030.38431@sjc-vpn6-829.cisco.com>
Content-Type: multipart/alternative; boundary="=-WeFtK2gIwwStOjA1Ibye"
Organization: Network Zen
Date: Sun, 10 Jun 2012 12:05:10 +0700
Message-ID: <1339304710.6353.19.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 05:05:18 -0000

--=-WeFtK2gIwwStOjA1Ibye
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Sat, 2012-06-09 at 18:09 -0700, Ole Jacobsen wrote:


> The intended rotation cycle is still 1-1-1 for NA-EU-AP regions, but 
> it's all dependent on finding suitable and available venues and 
> willing hosts and sponsors. Changing the text of the document would
> imply a change in "policy" or "normal state of things" which there
> hasn't been.


Hmm.  So a dream world is the normal state of things...I guess really
should read this thing, if only to discover what other fantasies have
been made "real" through the magic of rough consensus.  However, since
this is a guide for the novice, I might remind folks that there is
chance that, lacking real experience, the novices in question might
actually believe what's in it  -- a dangerous prospect it seems.


> 
> Ole
> 
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
> 
> 
> On Sun, 10 Jun 2012, Glen Zorn wrote:
> 
>  A quick check of the "Upcoming IETF Meetings" calendar
>  (http://www.ietf.org/meeting/upcoming.html) shows that the next meeting
>  in Asia is scheduled for November 2015, while the last was November
>  2011.  How does a 4 year gap map to "approximately once a year"?



--=-WeFtK2gIwwStOjA1Ibye
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Sat, 2012-06-09 at 18:09 -0700, Ole Jacobsen wrote:<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
The intended rotation cycle is still 1-1-1 for NA-EU-AP regions, but 
it's all dependent on finding suitable and available venues and 
willing hosts and sponsors. Changing the text of the document would
imply a change in &quot;policy&quot; or &quot;normal state of things&quot; which there
hasn't been.
</PRE>
</BLOCKQUOTE>
<BR>
Hmm.&nbsp; So a dream world is the normal state of things...I guess really should read this thing, if only to discover what other fantasies have been made &quot;real&quot; through the magic of rough consensus.&nbsp; However, since this is a guide for the novice, I might remind folks that there is chance that, lacking real experience, the novices in question might actually believe what's in it&nbsp; -- a dangerous prospect it seems.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: <A HREF="mailto:ole@cisco.com">ole@cisco.com</A>  URL: <A HREF="http://www.cisco.com/ipj">http://www.cisco.com/ipj</A>
Skype: organdemo


On Sun, 10 Jun 2012, Glen Zorn wrote:

 A quick check of the &quot;Upcoming IETF Meetings&quot; calendar
 (<A HREF="http://www.ietf.org/meeting/upcoming.html">http://www.ietf.org/meeting/upcoming.html</A>) shows that the next meeting
 in Asia is scheduled for November 2015, while the last was November
 2011.  How does a 4 year gap map to &quot;approximately once a year&quot;?
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-WeFtK2gIwwStOjA1Ibye--


From ynir@checkpoint.com  Sat Jun  9 23:31:29 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86F8721F86A4 for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 23:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level: 
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8]
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 QWRQQ6OmUXza for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 23:31:29 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id A256C21F8698 for <ietf@ietf.org>; Sat,  9 Jun 2012 23:31:27 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (dlpgw.checkpoint.com [194.29.34.27]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q5A6VK4K017047; Sun, 10 Jun 2012 09:31:20 +0300
X-CheckPoint: {4FD43F10-10004-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sun, 10 Jun 2012 09:31:14 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "'Randy Bush'" <randy@psg.com>, Glen Zorn <glenzorn@gmail.com>
Date: Sun, 10 Jun 2012 09:31:06 +0300
Subject: RE: [Fwd: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of	IETF: A Novice's Guide to the Internet Engineering Task	Force) to Informational RFC]
Thread-Topic: [Fwd: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao	of	IETF: A Novice's Guide to the Internet Engineering Task	Force) to Informational RFC]
Thread-Index: Ac1GoKIWzcjtwAheTxKNb5fEtjK/TgAMc/DQ
Message-ID: <006FEB08D9C6444AB014105C9AEB133F017A7C056C84@il-ex01.ad.checkpoint.com>
References: <1339287190.6353.11.camel@gwz-laptop> <m2r4togg5d.wl%randy@psg.com>
In-Reply-To: <m2r4togg5d.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11dab0bfe07cb63999936f11e08304120017230232
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 06:31:29 -0000

To be fair, nearly half the attendees come from that continent. Even when t=
he meetings are held in Taipei or Paris.=20

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ran=
dy Bush
Sent: 10 June 2012 03:33
To: Glen Zorn
Cc: IETF Disgust
Subject: Re: [Fwd: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Ta=
o of IETF: A Novice's Guide to the Internet Engineering Task Force) to Info=
rmational RFC]

> A quick check of the "Upcoming IETF Meetings" calendar
> (http://www.ietf.org/meeting/upcoming.html) shows that the next=20
> meeting in Asia is scheduled for November 2015, while the last was=20
> November 2011.  How does a 4 year gap map to "approximately once a=20
> year"?

this winter we are meeting in georgia (not the one in the caucasus) and flo=
rida.  what more diversity do you want?  canada?

randy


From daedulus@btconnect.com  Sun Jun 10 00:20:36 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B01A21F8627; Sun, 10 Jun 2012 00:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level: 
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-4]
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 v2KO6Rc6vH-i; Sun, 10 Jun 2012 00:20:34 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe002.messaging.microsoft.com [65.55.88.12]) by ietfa.amsl.com (Postfix) with ESMTP id 8F57C21F8621; Sun, 10 Jun 2012 00:20:31 -0700 (PDT)
Received: from mail176-tx2-R.bigfish.com (10.9.14.248) by TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id 14.1.225.23; Sun, 10 Jun 2012 07:19:35 +0000
Received: from mail176-tx2 (localhost [127.0.0.1])	by mail176-tx2-R.bigfish.com (Postfix) with ESMTP id 5535B40132; Sun, 10 Jun 2012 07:19:35 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT008.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -27
X-BigFish: PS-27(zzbb2dI98dI9371I542M1432I1418I4015Izz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah304l)
Received: from mail176-tx2 (localhost.localdomain [127.0.0.1]) by mail176-tx2 (MessageSwitch) id 1339312773294535_4105; Sun, 10 Jun 2012 07:19:33 +0000 (UTC)
Received: from TX2EHSMHS018.bigfish.com (unknown [10.9.14.240])	by mail176-tx2.bigfish.com (Postfix) with ESMTP id 44E7D100047; Sun, 10 Jun 2012 07:19:33 +0000 (UTC)
Received: from DB3PRD0702HT008.eurprd07.prod.outlook.com (157.55.224.141) by TX2EHSMHS018.bigfish.com (10.9.99.118) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sun, 10 Jun 2012 07:19:31 +0000
Received: from BL2PRD0710HT002.namprd07.prod.outlook.com (157.56.240.133) by pod51017.outlook.com (10.3.4.173) with Microsoft SMTP Server (TLS) id 14.15.74.2; Sun, 10 Jun 2012 07:20:25 +0000
Message-ID: <005001cd46d9$10928de0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: ssakane <ssakane@cisco.com>
References: <CBF8CDF4.6AEF%ssakane@cisco.com>
Subject: Re: [secdir] secdir review of draft-sakane-dhc-dhcpv6-kdc-option
Date: Sun, 10 Jun 2012 08:17:02 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.240.133]
X-OriginatorOrg: btconnect.com
Cc: draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org, ietf <ietf@ietf.org>, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 07:20:36 -0000

---- Original Message -----
From: "ssakane" <ssakane@cisco.com>
To: "t.p." <daedulus@btconnect.com>
Cc: <draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org>;
<secdir@ietf.org>; "ietf" <ietf@ietf.org>
Sent: Saturday, June 09, 2012 1:55 AM
> Removing the section 4.1 to an Appendix is nicer idea rather than just
> deleting it.

Yes, but for me it is definitely second best.

Arguably, following the steps in s 4.1 is necessary for
interoperability.

If DNS and DHCP produce the same KDC information, who cares what
procedure is followed?  It is only when they produce different results
that the procedure matters.

The dictum is that DNS information is preferred to DHCP information, but
as the procedure shows, it is not quite that simple.  It specifies that
DNS is accessed via DHCP, ie DNS is only accessed if DHCP provides
information about it.  Without this guidance, an implementer might
assume that eg preconfigured DNS information should be used to access
DNS for KDC information rather than first asking DHCP for what it knows,
in which case such an implementer would follow a different path to,
potentially, a different KDC.  So the client uses one KDC, the
application server a different KDC; result, protocol failure.

So you could see s 4.1 as necessary for the protocol to work.

And again, as I said before, s 4.1 says that DNS SHOULD be used, while
the Security Considerations say DHCP SHOULD be secured so given secure
DHCP and insecure DNS giving different results, which SHOULD wins?

Tom Petch
>
> Shoichi
>
>
> On 6/8/12 11:24 PM, "t.p." <daedulus@btconnect.com> wrote:
>
> > ----- Original Message -----
> > From: "ssakane" <ssakane@cisco.com>
> > To: "t.p." <daedulus@btconnect.com>
> > Cc: <draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org>;
> > <secdir@ietf.org>; "ietf" <ietf@ietf.org>
> > Sent: Friday, June 08, 2012 2:29 PM
> >> Hi Tom,
> >>
> >> Some reviewers suggested me to just remove the figure and its
> > description in
> >> 4.1 because it has ambiguity.  I think it would be better to leave
the
> > 1st
> >> paragraph in section 4.1, and I should remove the rest.  What do
you
> > think
> >> about this idea ?
> >
> > I would leave it in.
> >
> > The first paragraph on its own I would think underspecified and the
rest
> > of the section does cover a number of issues, issues that only
occurred
> > to me when I read the section carefully.  As I said in my last post,
I
> > then found I had further issues - how long to wait, should a secure
DHCP
> > trump an insecure DNS? - which may be worth exploring in addition.
> >
> > I do think that this kind of pseudocode helps a lot of developers to
> > understand the issues and would want a good reason to remove it; at
the
> > same time, others see it as an impurity that has no part in a
Standards
> > Track RFC.  One option would be to remove it to an Appendix which
> > implicitly makes it Informative and not Normative so it is there for
> > those who would benefit from it but will not upset those who
consider it
> > out of place.  But I would bounce this off the krb list to see what
> > reaction you get.
> >
> > Tom Petch
> >
> >> Thanks,
> >> Shoichi
> >>
> >> On 6/8/12 7:37 PM, "t.p." <daedulus@btconnect.com> wrote:
> >>
> >>> Just to make public what I have hinted at privately, I think that
> > steps
> >>> in section 4.1 may be somewhat underspecified.
> >>>
> >>> They give the logic a client, one which supports both DHCP and
DNS,
> >>> should
> >>> follow in order to find a KDC, with DNS information being
preferred.
> >>> One scenario outlined in section 1 is of a user having entered
> > userid
> >>> and
> >>> passphrase and waiting to be authenticated.  The steps imply a
> > number of
> >>> timeouts in succession without specifying what balance to take of
> > how
> >>> long
> >>> to wait for a server to respond versus how long to keep the user
> >>> waiting.
> >>> I would find it difficult to know what balance to strike without
> >>> guidance.
> >>>
> >>> A related issue is that section 4.1 prefers DNS to DHCP for
Kerberos
> >>> information but the Security Considerations stress the weakness of
> >>> DHCP and recommend authenticating DHCP.  What if DHCP is secure
> >>> and DNS is not?  Should DNS still be preferred?
> >>>
> >>> Tom Petch
> >>>
> >>> ----- Original Message -----
> >>> From: "Jeffrey Hutzelman" <jhutz@cmu.edu>
> >>> To: "Samuel Weiler" <weiler+secdir@watson.org>
> >>> Cc: <draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org>;
> >>> <secdir@ietf.org>; <ietf@ietf.org>; <jhutz@cmu.edu>
> >>> Sent: Thursday, May 24, 2012 6:50 PM
> >>> Subject: Re: [secdir] secdir review of
> >>> draft-sakane-dhc-dhcpv6-kdc-option
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>



From brian.e.carpenter@gmail.com  Sun Jun 10 03:54:47 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72CD021F85BE for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 03:54:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.748
X-Spam-Level: 
X-Spam-Status: No, score=-99.748 tagged_above=-999 required=5 tests=[AWL=1.944, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 2Ry+ag3XbEJY for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 03:54:47 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id C71E221F85BD for <ietf@ietf.org>; Sun, 10 Jun 2012 03:54:46 -0700 (PDT)
Received: by eekd4 with SMTP id d4so2280849eek.31 for <ietf@ietf.org>; Sun, 10 Jun 2012 03:54:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=pT9l/FAtn7Mjt4BpP5dZ+Y4WoES6K3FEGwTycCm/xnQ=; b=YLGdgcsenh8Sn17Dhew53V7GbapQEEuWB4bOOslbDQwzMUPP2rpMW8XDbykiIaQXbX p8YrY1EVCpRDd+5BL/OO4eL/7fv8xa//R0Q1oTbMYqHw5tZdqLkVKyWjHlNea70eCm6a Cwsdh/CcgpuLHQOyETcixdDYcNF9dg0iJY+AWAfgwqZQvza9fPY0twCJ+odEC90UiHQX 1rhq8GlCdS+/HpBHgTSCE2BQtnibARw8gPkJQtuoM1VFCFtAmbX4O38E1uui1GCAIVVY 27MztkeRlyHMe/VNf8kR6d47Q3JUsUuwA0kuobqCLUn0WNV6TWom10c+HlEZHxRC2yJp zO/Q==
Received: by 10.14.127.203 with SMTP id d51mr5197239eei.201.1339325685817; Sun, 10 Jun 2012 03:54:45 -0700 (PDT)
Received: from [192.168.1.66] (host-2-102-218-37.as13285.net. [2.102.218.37]) by mx.google.com with ESMTPS id q53sm40835897eef.8.2012.06.10.03.54.43 (version=SSLv3 cipher=OTHER); Sun, 10 Jun 2012 03:54:45 -0700 (PDT)
Message-ID: <4FD47CF1.4080107@gmail.com>
Date: Sun, 10 Jun 2012 11:54:41 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-hoffman-tao-as-web-page-00.txt
References: <20120609221936.12063.68465.idtracker@ietfa.amsl.com>
In-Reply-To: <20120609221936.12063.68465.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 10:54:47 -0000

This draft should formally obsolete RFC 4677. Otherwise, I think it's fine.

This doesn't need to be in the document, but having a fixed location for
the pending version might be good, e.g. http://www.ietf.org/draft-tao.html .

Regards
   Brian Carpenter

From chair@ietf.org  Sun Jun 10 07:15:07 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CF7421F85F3 for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 07:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100]
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 NJj+XbedT32m for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 07:15:07 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 26B0A21F85EF for <ietf@ietf.org>; Sun, 10 Jun 2012 07:15:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 074E512C8C0 for <ietf@ietf.org>; Sun, 10 Jun 2012 07:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05QQjtZbFp63 for <ietf@ietf.org>; Sun, 10 Jun 2012 07:15:06 -0700 (PDT)
Received: from [192.168.2.110] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) by c8a.amsl.com (Postfix) with ESMTPSA id B996812C8BA for <ietf@ietf.org>; Sun, 10 Jun 2012 07:15:06 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Host needed for Berlin meeting in July 2013
Date: Sun, 10 Jun 2012 10:15:05 -0400
Message-Id: <AB262C63-98EE-4DA0-9826-262AF8205410@ietf.org>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 14:15:07 -0000

In July 2013, the IETF will hold a meeting in Berlin.  We are a only =
little over a year away from that meeting, and we do not yet have a =
host.

We have had some conversations with potentially interested parties, we =
do not at this point have a host for the meeting.  We want sign up a =
host as soon as possible.  As you know Drew Dvorshak <dvorshak@isoc.org> =
coordinates hosting and sponsorship.  As usual, Drew will be in =
Vancouver all week, and he will be available for meetings and =
conversations.  Please consider the value that hosting, co-hosting, or =
sponsoring the first IETF meeting in Berlin.  Feel free to contact Drew =
now to set up time to speak in Vancouver about various opportunities, =
benefits, and other details.

Your organization's support of our meetings is very important, and we =
appreciate your consideration.

Russ=

From johnl@iecc.com  Sun Jun 10 08:47:49 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B8921F85C7 for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 08:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 k9YaaBwm6a0b for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 08:47:48 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 491A621F85BD for <ietf@ietf.org>; Sun, 10 Jun 2012 08:47:47 -0700 (PDT)
Received: (qmail 11103 invoked from network); 10 Jun 2012 15:47:46 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 10 Jun 2012 15:47:46 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4fd4c1a1.xn--30v786c.k1206; i=johnl@user.iecc.com; bh=rs+pKZvKBSnt59PDP64GOuoCD/1odsd29EowpyHX+hk=; b=F3OatIE5NWSdSTYHLTVavQkcvGzju53+fuH1Kz0n7w427hREk8LLZ2CNMNcT4O+0oHmcJvmV5q6qqEzWixHzGIKbULc2enCtx0tXrNYjpxmFXPFMGattrg0C/QPCONWh+wiHT+equljus4PbtVyV4JgrM2Rs1gf+QboPW1c/U8E=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 10 Jun 2012 15:47:23 -0000
Message-ID: <20120610154723.52312.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: [Fwd: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
In-Reply-To: <1339304710.6353.19.camel@gwz-laptop>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 15:47:49 -0000

>> The intended rotation cycle is still 1-1-1 for NA-EU-AP regions, but 
>> it's all dependent on finding suitable and available venues and 
>> willing hosts and sponsors. Changing the text of the document would
>> imply a change in "policy" or "normal state of things" which there
>> hasn't been.
>
>
>Hmm.  So a dream world is the normal state of things...I guess really
>should read this thing, if only to discover what other fantasies have
>been made "real" through the magic of rough consensus. 

Gee, while we're at it, perhaps we should remind novices that the
best way to make progress is to send snarky comments rather than
revised text.

Old:

   Currently, the IETF meets in North America, Europe, and Asia,
   approximately once a year in each region.

New:

   Currently, the IETF meets in North America, Europe, and Asia.  The
   intention is to meet once a year in each region, although due to scheduling
   issues there are often more meetings in North America and fewer in Asia.

R's,
John



From ole@cisco.com  Sun Jun 10 08:56:29 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4A1721F85EF for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 08:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 zya4MQ6+rXH5 for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 08:56:29 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id E0CD021F85E3 for <ietf@ietf.org>; Sun, 10 Jun 2012 08:56:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1187; q=dns/txt; s=iport; t=1339343788; x=1340553388; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=06v7syK4J3zaaovfj1VXOyxpPeoTiky0tYhXCOAdxxc=; b=DCkfig1bNf+4PjSd3mVzhxc+poLan+z/a3ZFxaYIqtK031AJhBFLawq1 Gi7y/u0pc+p8fbzlzGGfSi8WmwoW7htQBJgQD+F/xkbubdUI7RPLrXaDl C+/pyvWaljPJ1SH59+YDRH8qeL2Ncoxhkk0FezAE5nxfHBC5njP2k6rgb U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAG/D1E+rRDoI/2dsb2JhbABCA7RagQeCGAEBAQMBEgECJT8FCws7C1cGEyKHZASYQINHEJsqiycKEIIvgyADiECXX4MUgQRigwCBPw
X-IronPort-AV: E=Sophos;i="4.75,745,1330905600"; d="scan'208";a="48304290"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 10 Jun 2012 15:56:28 +0000
Received: from sjc-vpn6-829.cisco.com (sjc-vpn6-829.cisco.com [10.21.123.61]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q5AFuROp021476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);  Sun, 10 Jun 2012 15:56:28 GMT
Date: Sun, 10 Jun 2012 08:56:27 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: John Levine <johnl@iecc.com>
Subject: Re: [Fwd: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
In-Reply-To: <20120610154723.52312.qmail@joyce.lan>
Message-ID: <alpine.OSX.2.01.1206100853190.52462@sjc-vpn6-829.cisco.com>
References: <20120610154723.52312.qmail@joyce.lan>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 15:56:29 -0000

On Sun, 10 Jun 2012, John Levine wrote:


> Old:
> 
>    Currently, the IETF meets in North America, Europe, and Asia,
>    approximately once a year in each region.
> 
> New:
> 
>    Currently, the IETF meets in North America, Europe, and Asia.  The
>    intention is to meet once a year in each region, although due to scheduling
>    issues there are often more meetings in North America and fewer in Asia.
> 
> R's,
> John
> 

Friendly amendment:

Currently, the IETF meets in North America, Europe, and Asia. The 
intention is to meet once a year in each region, although due to 
scheduling issues there are often more meetings in North America and 
fewer in Asia and Europe.

<eofa>
----

There are many reasons for the current situation, but this is probably 
not the forum/context to discuss this. Let me just draw everyones 
attention to the message sent out today by the IETF Chair regarding
hosting of the upcoming Berlin meeting.


Ole J. Jacobsen 
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


From brian.e.carpenter@gmail.com  Sun Jun 10 09:00:37 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9617721F85BE for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 09:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.395
X-Spam-Level: 
X-Spam-Status: No, score=-100.395 tagged_above=-999 required=5 tests=[AWL=1.296, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 Kz9JNRfMaLMR for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 09:00:37 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id E685021F8471 for <ietf@ietf.org>; Sun, 10 Jun 2012 09:00:36 -0700 (PDT)
Received: by eaaq13 with SMTP id q13so2302234eaa.31 for <ietf@ietf.org>; Sun, 10 Jun 2012 09:00:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=b1RlpsrUFcT8dp8x9Y+EZ/vlufR63PhTDPIgnhbiECQ=; b=O7ihaKPnoY4ZPQb7ntBwpTVbp/mFIzYgOSBJq9P04VhVhUxEcUDy4z1UC/yQyXsufE B9cLHfg3/973Jn2BaPiH3z3aAP5ab2jVSSp7usBKg8+8NxpC53sKIuRNTgfLH7y12SSt 4WXttMRhCw5zRCP4BH2WMjetPdUrOUbstz5vTq7yJr1HqSyi6ogdWb3/TdC0gtOt3rFz qYpQ0cxmECsGd/4Fx+Yfo8lbe90hw4YvkBD4P7fpBSn2U7QU/RwcNRaqTJuSKIweF752 JDfHLCBVcD6y5LQV9LwqX//HV/iebYFPJbE0h5jz2BOTewuFGhK6+WlGPtmqrCWWS5aU pvRg==
Received: by 10.14.99.11 with SMTP id w11mr5424737eef.67.1339344035834; Sun, 10 Jun 2012 09:00:35 -0700 (PDT)
Received: from [192.168.1.66] (host-2-102-218-37.as13285.net. [2.102.218.37]) by mx.google.com with ESMTPS id h53sm42978836eea.1.2012.06.10.09.00.34 (version=SSLv3 cipher=OTHER); Sun, 10 Jun 2012 09:00:34 -0700 (PDT)
Message-ID: <4FD4C49F.8080508@gmail.com>
Date: Sun, 10 Jun 2012 17:00:31 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-hoffman-tao-as-web-page-00.txt
References: <20120609221936.12063.68465.idtracker@ietfa.amsl.com> <4FD47CF1.4080107@gmail.com>
In-Reply-To: <4FD47CF1.4080107@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 16:00:37 -0000

Oh, one thing I now realise is that the draft doesn't state that
the editor (in deciding what changes to adopt) and the IESG
(in approving an update) will of course do so by a normal IETF
consensus process (presumably ad hoc last calls) and subject
to appeal like anything else. This is so obvious in the IETF
context that I didn't even notice that it wasn't stated.

The sentence that should state it belongs about here:
  "The Tao
   has traditionally been an IETF consensus document, which means that
   the IESG has had the final say about what the Tao contained before it
   was sent to the RFC Editor.  Thus, the IESG should have final say for
   what the Tao says when it is a web page."

The IESG's "final say" is of course always in the context of determining
IETF consensus.

Regards
   Brian Carpenter

On 2012-06-10 11:54, Brian E Carpenter wrote:
> This draft should formally obsolete RFC 4677. Otherwise, I think it's fine.
> 
> This doesn't need to be in the document, but having a fixed location for
> the pending version might be good, e.g. http://www.ietf.org/draft-tao.html .
> 
> Regards
>    Brian Carpenter
> 

From randy@psg.com  Sun Jun 10 09:04:45 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A95F21F85B9 for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 09:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 tagged_above=-999 required=5 tests=[AWL=0.402,  BAYES_00=-2.599]
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 KdEwnLvWoIcI for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 09:04:44 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id CD68F21F8593 for <ietf@ietf.org>; Sun, 10 Jun 2012 09:04:44 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Sdkd9-000PwV-H5; Sun, 10 Jun 2012 16:04:43 +0000
Date: Sun, 10 Jun 2012 09:04:42 -0700
Message-ID: <m2r4tnf90l.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "John Levine" <johnl@iecc.com>
Subject: Re: [Fwd: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao	of IETF: A Novice's Guide to the Internet Engineering Task	Force) to Informational RFC]
In-Reply-To: <20120610154723.52312.qmail@joyce.lan>
References: <1339304710.6353.19.camel@gwz-laptop> <20120610154723.52312.qmail@joyce.lan>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 16:04:45 -0000

>    Currently, the IETF meets in North America, Europe, and Asia.  The
>    intention is to meet once a year in each region, although due to
>    scheduling issues there are often more meetings in North America
>    and fewer in Asia.

s/intention/intent/

From paul.hoffman@vpnc.org  Sun Jun 10 09:23:54 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45AF821F85F6 for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 09:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 opTId6pgXPUh for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 09:23:53 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id A5D3B21F8470 for <ietf@ietf.org>; Sun, 10 Jun 2012 09:23:53 -0700 (PDT)
Received: from [10.20.30.101] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q5AGNee0015643 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 10 Jun 2012 09:23:41 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: I-D Action: draft-hoffman-tao-as-web-page-00.txt
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4FD4C49F.8080508@gmail.com>
Date: Sun, 10 Jun 2012 09:23:40 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E95A8C1-08F1-4519-95AF-1E99FA205B28@vpnc.org>
References: <20120609221936.12063.68465.idtracker@ietfa.amsl.com> <4FD47CF1.4080107@gmail.com> <4FD4C49F.8080508@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 16:23:54 -0000

On Jun 10, 2012, at 9:00 AM, Brian E Carpenter wrote:

> Oh, one thing I now realise is that the draft doesn't state that
> the editor (in deciding what changes to adopt) and the IESG
> (in approving an update) will of course do so by a normal IETF
> consensus process (presumably ad hoc last calls) and subject
> to appeal like anything else. This is so obvious in the IETF
> context that I didn't even notice that it wasn't stated.

It is not what was intended.

- There was no mention to me of "ad hoc last calls", so I did not =
include them in the draft.=20

- Is there an appeals process for the content of the various web pages =
created by the IESG?

--Paul Hoffman=

From alexey.melnikov@isode.com  Sun Jun 10 10:39:11 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C328321F85A3 for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 10:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.159
X-Spam-Level: 
X-Spam-Status: No, score=-103.159 tagged_above=-999 required=5 tests=[AWL=-3.444, BAYES_05=-1.11, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
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 fqZ9LVQfo-4b for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 10:39:11 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id D35A321F858E for <ietf@ietf.org>; Sun, 10 Jun 2012 10:39:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1339349949; d=isode.com; s=selector; i=@isode.com; bh=O/xZwHVglml6piyTcChuGI4oBaNed444RmEDrqJh548=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Jkav8NO+MNgtLphbb0bhdqktU406CLXLAgjonnRVE7Edks/7TB/u/Dx9hzm9FPXRU7p8wd XdZfIwm1H2i9Gn+SLrV45AhxKxl/kUGAAdvbxu/vDllg19gCOB9bQyreSGW2QyZcQP+ByE QkKVvSLv7mXMZMAVM8Z8tKiSBCnWY3w=;
Received: from [188.28.164.227] (188.28.164.227.threembb.co.uk [188.28.164.227])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T9TbuwAE42SX@rufus.isode.com>; Sun, 10 Jun 2012 18:39:08 +0100
Subject: Re: Last Call: RFC 2818 (HTTP Over TLS) to Proposed Standard
References: <20120601164205.25357.54620.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120601123737.0acca170@resistor.net>
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (9B206)
In-Reply-To: <6.2.5.6.2.20120601123737.0acca170@resistor.net>
Message-Id: <A33D3784-6B07-46FA-9600-50CADF6EE4DF@isode.com>
Date: Sun, 10 Jun 2012 18:39:05 +0100
To: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 17:39:11 -0000

Adding to what SM already wrote (and yes, I've reread the whole document):

On 1 Jun 2012, at 21:23, SM <sm@resistor.net> wrote:

> At 09:42 01-06-2012, IESG Secretary wrote:
>> The IESG has received a request from the TLS Working Group to reclassify R=
FC 2818 (HTTP Over TLS) to Proposed Standard.
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits fin=
al comments on this action. Please send substantive comments to the ietf at i=
etf.org mailing lists by
>=20
> Could the IESG please use ietf@ietf.org instead of obfuscating the email a=
ddress?  Some of us are lazy especially on Fridays.
>=20
> Erratum #1077 has been classified as "Held for Document Update".  Will the=
re ever be a document update?  Implementing this specification requires HTTP=
/1.1 and TLS 1.0.  I suggest updating the reference to RFC 4346 at least and=
 waiting for the updated HTTP specifications.
>=20

Yes, it would be worth doing that if the document is reopened.

> St. Andre and Mr. Hodges authored a Proposed Standard called "Representati=
on and Verification of Domain-Based Application Service Identity within Inte=
rnet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Contex=
t of Transport Layer Security (TLS)".  Quoting from Section 1.4:
>=20
>  "the procedures described here can be referenced by future
>   specifications, including updates to specifications for
>   existing application protocols if the relevant technology
>   communities agree to do so."
>=20
> May I suggest taking the above into consideration and at least put some mi=
nimal effort into a 2818bis?
>=20

Not surprisingly I agree with you.

Also note that HTTPBis WG has folded the updated definition of https:// URI s=
chemes (Section 2.4 of RFC 2818) into one of its documents. I think it would=
 be good to make it clear to readers which document defines the URI scheme.

As far as reopening the document is concerned: I slightly prefer to do rfc28=
18bis although I understand that doing a -bis always takes longer than origi=
nally anticipated.


From brian.e.carpenter@gmail.com  Sun Jun 10 23:53:43 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00C6C11E8088 for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 23:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.719
X-Spam-Level: 
X-Spam-Status: No, score=-100.719 tagged_above=-999 required=5 tests=[AWL=0.972, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 VyXOv6OpRnt8 for <ietf@ietfa.amsl.com>; Sun, 10 Jun 2012 23:53:42 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 23DF211E8086 for <ietf@ietf.org>; Sun, 10 Jun 2012 23:53:41 -0700 (PDT)
Received: by eaaq13 with SMTP id q13so2434271eaa.31 for <ietf@ietf.org>; Sun, 10 Jun 2012 23:53:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ow8sh0CqOVPfM3SEFOQJwRfqBqvhRoohw4UXo4uJ/Sg=; b=MRvIKRSyrXWpce6jBARXYY0nVrPY3+CbIOKltGbLYj4wQdOaeObNvZcNkJIezTZrt7 efyaroJ/O2pZ2HHODn/EHfacxz71eq1Tc9GodH2f8W4Cm8HOmokiSlAL9LHrvDo4MqB2 7t86VCeG17yU+rcaI7P7kyjl7fkuw0k3CPuTzqQdptkoZtyxvyrzFri+xPI6i2ryVgZE 0tHSAQvC0PsZYFx8Uprc4bRHZ2Sixa8GDrM4YC/XBhnZ2xshH+CAfUZAHgsGGys5tdjx WhJyxd9mJaeoPAHi7TRkp/pbAtjU7ds9R+8u7IYyB64qNnVn8vylvRaR73K6GX5rS820 u41w==
Received: by 10.14.127.130 with SMTP id d2mr5992431eei.82.1339397621207; Sun, 10 Jun 2012 23:53:41 -0700 (PDT)
Received: from [192.168.1.66] (host-2-102-217-26.as13285.net. [2.102.217.26]) by mx.google.com with ESMTPS id e45sm48960395eeb.6.2012.06.10.23.53.38 (version=SSLv3 cipher=OTHER); Sun, 10 Jun 2012 23:53:40 -0700 (PDT)
Message-ID: <4FD595EB.7020401@gmail.com>
Date: Mon, 11 Jun 2012 07:53:31 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: I-D Action: draft-hoffman-tao-as-web-page-00.txt
References: <20120609221936.12063.68465.idtracker@ietfa.amsl.com> <4FD47CF1.4080107@gmail.com> <4FD4C49F.8080508@gmail.com> <3E95A8C1-08F1-4519-95AF-1E99FA205B28@vpnc.org>
In-Reply-To: <3E95A8C1-08F1-4519-95AF-1E99FA205B28@vpnc.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 06:53:43 -0000

On 2012-06-10 17:23, Paul Hoffman wrote:
> On Jun 10, 2012, at 9:00 AM, Brian E Carpenter wrote:
> 
>> Oh, one thing I now realise is that the draft doesn't state that
>> the editor (in deciding what changes to adopt) and the IESG
>> (in approving an update) will of course do so by a normal IETF
>> consensus process (presumably ad hoc last calls) and subject
>> to appeal like anything else. This is so obvious in the IETF
>> context that I didn't even notice that it wasn't stated.
> 
> It is not what was intended.
> 
> - There was no mention to me of "ad hoc last calls", so I did not include them in the draft. 

Well, that was presumably an oversight. The IETF always works by
a consensus process, afaik.

> 
> - Is there an appeals process for the content of the various web pages created by the IESG?

Yes. For many years there has been a presumption that the appeals
process in section 6.5 of RFC 2026 can be applied to *any* IESG action.
That being so, I suppose it isn't vital to write it down in every
document, but it makes things clearer.

Look, I'm not suggesting that either the editor or the IESG will
unilaterally put nonsense in the Tao. But the Tao can't be an exception
to the general principles of IETF process; that would be ironic, indeed.

  Brian

From duerst@it.aoyama.ac.jp  Mon Jun 11 04:04:37 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FAFB21F8570 for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 04:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.59
X-Spam-Level: 
X-Spam-Status: No, score=-96.59 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_35=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 8X5CobopLdTK for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 04:04:36 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id BA09421F856F for <ietf@ietf.org>; Mon, 11 Jun 2012 04:04:34 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5BB4OFI029934 for <ietf@ietf.org>; Mon, 11 Jun 2012 20:04:26 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 3a0e_4317_33b7a154_b3b5_11e1_9403_001d096c5782; Mon, 11 Jun 2012 20:04:23 +0900
Received: from [IPv6:::1] ([133.2.210.1]:34655) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D0EAF> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 11 Jun 2012 20:04:24 +0900
Message-ID: <4FD5D0B5.5000608@it.aoyama.ac.jp>
Date: Mon, 11 Jun 2012 20:04:21 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: APPSDIR review of draft-farrell-decade-ni-07 (minor editorial)
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie>
In-Reply-To: <4FCDE96E.5000109@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 11:04:37 -0000

Hello Stephen,

As Barry has suggested, I'm removing apps-discuss@ietf.org to reduced 
cross-posting. I'm going to split my response into several installments, 
hopefully separating the less contentious issues from the more 
contentious ones, and starting with the former ones.

Also, I want to apologize for the delays here, related to "day job" duties.

On 2012/06/05 20:11, Stephen Farrell wrote:
>
> Hi Martin,
>
> First, thanks for the speedy and thorough review. Some
> good points made, some with which I strongly disagree,
> but thrashing stuff like that out is part of the point
> of the reviews.
>
> On 06/05/2012 10:42 AM, "Martin J. DÃ¼rst" wrote:

>> Minor editorial issues:
>>
>> Introduction: It would be good to have a general reference to hashing
>> (for security purposes) for people not utterly familiar with the subject.
>
> Disagree. If I added that I could reasonably be asked to introduce
> URIs for the security folks. Serious and pointless ratholes would ensue.

Okay.

>> Intro: After reading the whole document, the structure of the Intro
>> seems to make some sense, but it didn't on first reading (where it's
>> actually more important). The main problem I was able to identify was
>> that after a general outlook in paragraph 1, the Intro drops into a list
>> of examples without saying what they are good for. I suggest to, after
>> the sentence "This document specifies standard ways to do that to aid
>> interoperability.", add a sentence along the lines: "The next few
>> paragraphs give usage examples for the various ways to include a hash in
>> a name or identifier as they are defined later in this document.". It
>> may also make sense to further streamline the following paragraphs, so
>> that it is clearer which pieces of text refer each to one of the
>> "standard ways".
>>
>> There are two instances of the term "binary presentation". Looking
>> around, it seems that they are supposed to mean the same as "binary
>> format". Please replace all instances of "binary presentation" with
>> "binary format" to avoid misunderstandings and useless seach time.
>>
>> Section 3: "A Named Information (ni) URI consists of the following
>> components:": It would be good to know exactly where the list ended. One
>> way to do this would be to say "consists of the following nine components".
>
> Those look reasonable. Will see if the changes work out.

The change that I have seen in your pre-draft for the above three items 
look good.


>> Section 3: "Note that while the ni names with and without an authority
>> differ syntactically, both names refer to the same object if the digest
>> algorithm and value are the same.": What about cases with different
>> authority? The text seems to apply by transitivity, but this may be easy
>> to miss for an implementer. I suggest changing to: "Note that while ni
>> names with and without an authority, and ni names with different
>> authorities, differ syntactically, they all refer to the same object if
>> the digest algorithm and value are the same.".
>
> Sure.

Okay.

>> Section 3: "Consequently no special escaping mechanism is required for
>> the query parameter portion of ni URIs.": Does this mean "no escaping
>> mechanism at all"? Or "nothing besides %-encoding"? Or something else?
>> Please clarify.
>
> I wish I knew:-) What do you think is right here? (Honestly,
> input on this would be appreciated.)

(In your internal draft, you removed the paragraph just before this one, 
and now the "Consequently" doesn't make any sense anymore.)

One possibility here is to remove anything about encoding, and have 
people check in RFC 3986, but I guess you wanted to help the reader 
here, so I'd propose something along the following lines (replacing the 
"Consequently" paragraph, and also in some sense the paragraph before 
that you already removed):

<<<<
Escaping of characters follows the rules in RFC 3986. This means that 
%-encoding is used to distinguish between reserved and unreserved 
functions of the same character in the same URI component. As an 
example, an ampersand ('&') is used in the query part to separate 
attribute-value pairs; an ampersand in a value therefore has to be 
escaped as '%26'. Note that the set of reserved characters differs for 
each component, as an example, a slash ('/') does not have any reserved 
function in a query part and therefore does not have to be escaped. 
However, it can still appear escaped as '%2f' or '%2F', and 
implementations have to be able to understand such escaped forms.
Also note that any characters outside those allowed in the respective 
URI component have to be escaped.
<<<<



>> Figure 3: the "=" characters of the various rules should be aligned as
>> much as possible to make it easier to scan the productions (see
>> http://tools.ietf.org/html/rfc3986#appendix-A for an example).
>
> Ack.

Great.

>> Section 3:
>>              unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"
>>                  ;  directly from RFC 3986, section 2.3
>>                  ; "authority" and "pct-encoded" are also from RFC 3986
>> Please don't copy productions. Please don't copy half (or one-third,
>> actually) of the productions you use, and reference the rest. Please
>> don't say what productions you copy from where in a comment, and even
>> less in a comment for an unrelated production. Please before the ABNF,
>> say which productions are used from another spec.
>
> We got contrary advice from elsewhere (can't recall where right now;-).
> I'll let Barry (as sponsoring AD) just tell us his preference and go
> with that if that's ok.

If you want to do it in a different way, you should at least be 
consistent. That would mean to also copy "authority" and "pct-encoded". 
The later is easy, but the former would really be too much. That's why 
I'd kick out "unreserved", too.


>> Section 4:
>>     The HTTP(S) mapping MAY be used in any context where clients without
>>     support for ni URIs are needed without loss of interoperability or
>>     functionality.
>> This is difficult to understand. If some new functionality is proposed,
>> it's usually a client *with* the new functionality that's needed, not
>> one without. Also, the "without loss of interoperability or
>> functionality" is unclear: Sure if ni isn't supported, there's a loss in
>> interoperability. So I suggest to rewrite this as:
>>     The HTTP(S) mapping MAY be used in any context where clients with
>>     support for ni URIs are not available.
>
> Sure.

Great. But in your internal draft, the period at the end of the sentence 
is now missing. (unless there's a bug in the diff)


>> (but see also the comment in minor technical issues)
>>
>> Section 6: "binary format name": Why 'name'? Why not just "binary
>> format"? The later is completely clear in the context of the document or
>> together with an indication of the document; for something that can be
>> used independently, even "binary format name" isn't enough.
>
> I don't get the problem with that.

You had "binary presentation", and changed that to "binary format" as 
per my suggestion. This is a very similar suggestion to align 
terminology. In the later half of the above comment, I was just trying 
to speculate about reasons for the difference, an the only reason I came 
up with was that it would be good to have a longer term that could be 
used independently outside the document.


>> Section 6: "suite ID": The word "suite" seems out of place here. In the
>> general use of the term, it refers to "a group of things forming a unit
>> or constituting a collection" (see
>> http://www.merriam-webster.com/dictionary/suite). A good definition that
>> works for the uses I'm familiar with in digital security would be "An
>> algorithm suite is a coherent collection of cryptographic algorithms for
>> performing operations such as signing, encryption, generating message
>> digests, and so on."
>> (http://fusesource.com/docs/framework/2.4/security/MsgProtect-SOAP-SpecifyAlgorithmSuite.html;
>> disclaimer: I'm in no way a SOAP fan). The use here is not for a
>> collection, but for a single truncated-length variant of a single hash
>> algorithm. I seriously hope you can find a better name.
>
> That's a don't-care for me. I think suite is fine, but could
> take other terms (so long as its not "algorithm"). Suite could
> be justified since we have alg+truncation here, but like I
> said I'd be fine to change, if a good suggestion is made.

What about "Truncated Hash ID" or "Hash Truncation ID" or some such? I'm 
open to other ideas, too.


>> Section 6: "Note that a hash value that is truncated to 120 bits will
>> result in the overall name being a 128-bit value which may be useful
>> with certain use-cases.": This left me really wondering: Is there
>> something magic to 128 bits in computer/internet security? What are the
>> "certain use cases"? Or is this just an example to make sure the reader
>> got the relationships, and it could have been as well "Note that a hash
>> value that is truncated to 64 bits will result in the overall name being
>> a 72-bit value which may be useful with certain use-cases." (or whatever
>> other value that's registered in section 9)?
>
> Bit of both. I believe the core WG are keen to end up with a 128 bit
> binary value as their preferred option.

Is there a way to word this that doesn't leave the reader wondering how 
she is supposed to understand this?

>> Section 7: Just for the highly unfortunate case that this doesn't
>> disappear, it would be very helpful if the presentation of this section
>> paralleled section 3.
>
> Disagree. Different requirements, different URIs, different
> presentation. I don't think there's a real problem here.

I'll address the "Different requirement" in a separate thread. In 
general, I'd expect that if a draft defines 2 of the same thing (e.g. 
two mime types,...), that it streamlines the presentation as far as 
possible. That this hadn't been done was part of the reason for my 
impression that this draft got patched together. But I think we should 
put of streamlining, because I hope that section 7 will disappear anyway 
:-).


>> Section 7: "contain the ID value as a UTF-8 encoded decimal number": I'm
>> an internationalization expert with a strong affection for UTF-8, but
>> even for me, this should be "contain the ID value as an ASCII encoded
>> decimal number".
>
> Fine.
>
>>
>> Section 9: The registration templates refer to sections. This is fine
>> for readers of the draft, but not if the template is standalone. I
>> suggest using a format such as that at
>> http://tools.ietf.org/html/rfc6068#section-8.1, which in draft stage may
>> look e.g. like
>> http://tools.ietf.org/html/draft-duerst-eai-mailto-03#section-8.1.
>
> Will take a peek. Not sure I agree. (Nor disagree:-)

Okay, let me know when you have made up your mind.

>> Section 9.3: "Assignment of Well Known URI prefix ni" and later (and
>> elsewhere in the draft) "URI suffix": Are we dealing with a prefix or a
>> suffix here?
>
> Will take a peek.

For your information, the registry is just named "Well-Known URIs" 
(http://www.iana.org/assignments/well-known-uris/well-known-uris.xml). 
Other drafts 
(http://tools.ietf.org/html/draft-daboo-srv-caldav-10#section-9.1, 
http://tools.ietf.org/html/draft-daboo-srv-caldav-10#section-9.2, 
http://tools.ietf.org/html/draft-ietf-core-link-format-14#section-7.1, 
http://tools.ietf.org/html/rfc6415#section-6.1, 
http://tools.ietf.org/html/rfc6415#section-6.2) have neither "prefix" 
nor "suffix" in the section title. I suggest to follow these, it will be 
less confusing.


>> Section 9.4: "This registry has five fields, the binary suite ID,...":
>> Better to remove the word "binary", because the actual number is decimal.
>
> Ack.
>
>>
>> Section 9.4: "The expert SHOULD seek IETF review before approving a
>> request to mark an entry as "deprecated."  Such requests may simply take
>> the form of a mail to the designated expert (an RFC is not required).
>> IETF review can be achieved if the designated expert sends a mail to the
>> IETF discussion list.  At least two weeks for comments MUST be allowed
>> thereafter before the request is approved and actioned.": I'm at a loss
>> to see why asking the IETF at large is a SHOULD, but if it's done, then
>> the two weeks period is a MUST.
>
> I don't get your comment. The two weeks is a MUST already.

This combination of SHOULD and MUST just doesn't feel right to me. Let 
me try with a different subject area which may make it easier to get my 
point.

What would you think if a document said something: "The expert SHOULD 
donate money to the IETF. If the expert donates money, s/he MUST donate 
at least $200."

As this example hopefully shows, MUSTs conditioned by SHOULDs don't 
really make sense. Or is this really just me ?-)

And let me give another try. Let's assume the expert wants to make a 
decision after one week, but still inform the IETF discussion list. She 
can just send a mail to that list saying "This is not a formal review 
according to Section 9.4 of RFC YYYY, but I'm planning to deprecate this 
entry in a week unless I hear good reasons to do otherwise." Logically 
speaking, that would be following the RFC, and shows that the MUST 
doesn't make sense, because it can't force anything.


>> Section 9.4: The registry initialization in Fig. 8 refers to RFC4055
>> many times. But RFC 4055 does in no way define SHA-256. It looks like
>> the actual spec is http://tools.ietf.org/html/rfc4055#ref-SHA2 (National
>> Institute of Standards and Technology (NIST), FIPS 180-2: Secure Hash
>> Standard, 1 August 2002.) I think this should be cited, in particular
>> because there is a "Specification Required" requirement, and this sure
>> should mean that there is a Specification for the actual algorithm, and
>> not just a specification that mentions some labels. So using RFC4055 as
>> a reference could be taken as creating bad precedent.
>
> I guess so. Good catch.

Great.

>> Section 9.4: "The designated expert is responsible for ensuring that the
>> document referenced for the hash algorithm is such that it would be
>> acceptable were the "specification required" rule applied.": Why all
>> this circumscription? Why not just say something like: "The designated
>> expert is responsible for ensuring that the document referenced for the
>> hash algorithm meets the "specification required" rule."
>
> Honestly? I can't recall:-) Will change unless I do remember.

Okay.

>> Nits:
>>
>> Author's list: Last time I heard about this, there was a general limit
>> of 5 authors per RFC. I'm not sure whether this still exists, and what'd
>> be needed to get around it, but I just wanted to point out that this may
>> be a potential problem or additional work (hoops to get through).
>>
>> Intro: "Since, there is no standard" ->  "Since there is no standard"
>>
>> Intro: "for these various purposes" ->  "for these purposes" or "for
>> various purposes" (the indefinite 'various' is incompatible with the
>> definite 'these').
>>
>> "2.  Hashes are what Count" ->  "2.  Hashes are what Counts" (the former
>> may look logically correct, but 'what' requires a singular verb form.
>>
>> Section 2: "the left-most or most significant in network byte order N
>> bits from the binary representation of the hash value" ->  "the left-most
>> (or most significant in network byte order) N bits from the binary
>> representation of the hash value" or "the left-most N bits, or the N
>> most significant bits in network byte order, from the binary
>> representation of the hash value" (the current text is virtually
>> unparsable).

You seem to disagree with this, but every time I try to read the above 
sentence, I have to take two or three attempts. And given my long-time 
training in German and Japanese, I have to admit that I'm quite used to 
long and convoluted sentences :-).


>> Figure 1: The 0x notation is never explained. A short clause or pharse
>> is all that would be needed, but it would be better if this were spelled
>> out.
>>
>> Section 3, Query Parameter separator: "The query parameter separator
>> acts a separator between" ->  "The query parameter separator acts *as* a
>> separator between".
>>
>> Section 3, Query Parameters: "A tag=value list of optional query
>> parameters as are used with HTTP URLs" ->   "A tag=value list of optional
>> query parameters as used with HTTP URLs" (or "A tag=value list of
>> optional query parameters as they are used with HTTP URLs").
>>
>> Section 4: "the object named by the ni URI will be available at the
>> corresponding HTTP(S) URL" ->  "the object named by the ni URI will be
>> available via the corresponding HTTP(S) URL" (via stresses the point
>> that this should be done via (sic) redirection)
>>
>> Section 4: "so there may still be reasons to use" ->  "so there can still
>> be reasons to use" (better to use can because non-normative; the
>> document otherwise does a good job on this)
>>
>> Section 10: "Note that fact that" ->  "Note the fact that", or much
>> better: "Note that".
>
> Those look ok or are nits in any case.

Other than indicated above, I'm fine with the changes for these 
issues/nits that you have made (or not made) in your internal copy.


Regards,    Martin.

(more replies tomorrow)

> Thanks again for the thorough review even though we disagree as
> to the main point.
>
> Cheers,
> Stephen.
>
>
>>
>>
>> Regards,     Martin.
>>
>>
>>
>

From sm@resistor.net  Mon Jun 11 05:38:59 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF6121F84FF for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 05:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.227
X-Spam-Level: 
X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 mg6rnhQ9r+Jk for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 05:38:58 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A2B121F8497 for <ietf@ietf.org>; Mon, 11 Jun 2012 05:38:58 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5BCcp1g013969; Mon, 11 Jun 2012 05:38:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1339418336; i=@resistor.net; bh=5U44D0RL/91HtlBW3aGg9Mbm2Cx6LeKlQWkOUfzwzr0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xAcMs2VbesPLLc8YNg5vnmxpugPVdw9Y/PXML0C+t9eeuFRn/TpQa/ClLyi+3X/df IxhmMIUlwH1Skv1UuyPvjHaQPbJWMLeRbluG6g1AW4YBYIg0Y2AX9mvWK0V3OSTzGq uOPKmYDUDBR8huvnK8rzXLb7j/+/cuu7m4FPoVkA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1339418336; i=@resistor.net; bh=5U44D0RL/91HtlBW3aGg9Mbm2Cx6LeKlQWkOUfzwzr0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pTeKKT/UuQtP8/0zkWn/1aBwgqX0cZRiMFrWrQMVRN7LhT7YqG9rOoXATGbwUL9GQ KHcbToYS/SoFScfl0QmrzUKHcziSNI9fu5dKRLLFZzq/xqCcb5lQ/2n2ZmNKUxfxDt 2nyXecUoJlVX00ox/nDejQuCa0QfU9S0/x4Mo//4=
Message-Id: <6.2.5.6.2.20120611042706.095ba210@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 11 Jun 2012 05:30:38 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
In-Reply-To: <20120604141804.23098.42455.idtracker@ietfa.amsl.com>
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-farrell-decade-ni@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 12:38:59 -0000

At 07:18 04-06-2012, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Naming Things with Hashes'
>   <draft-farrell-decade-ni-07.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2012-07-02. Exceptionally, comments may be

Here's an editorial comment about Section 9.4 and Section 10.

Move the following to the first paragraph or a separate paragraph as 
it is not related to the second paragraph:

   'Note that if the status is not "deprecated" (it is empty), then that
    does not necessarily mean that the algorithm is "good" for any
    particular purpose, since the cryptographic strength requirements
    will be set by other applications or protocols.'

And for:

   'The expert SHOULD seek IETF review before approving a request to
    mark an entry as "deprecated."  Such requests may simply take the
    form of a mail to the designated expert (an RFC is not required).
    IETF review can be achieved if the designated expert sends a mail
    to the IETF discussion list.  At least two weeks for comments MUST
    be allowed thereafter before the request is approved and actioned.'

Suggested text with pointers to comments:

   A request to mark an entry as "deprecated" can be done by sending
   a mail to the designated expert.  Before approving the request,
   the community should be consulted via a "call for comments" of
   at least two weeks by sending a mail to the IETF discussion list.

Near the end of Page 14:

  "The expert MAY request IETF review before allocating a
   suite ID."

Suggested:

  The designated expert may consult the community via a "call for
  comments" by sending a mail to the IETF discussion list before
  allocating a suite ID.

I avoided using the term "IETF review" because it is used policy 
definition in the BCP.  I leave it to the authors to apply RFC 2119 
casing as appropriate.

In Section 10:

   "While a name-data integrity service can be provided using ni URIs,
    that does not in any sense validate the authority part of the name,
    for example, there is nothing to stop anyone creating an ni URI
    containing a hash of someone else's content so application developers
    MUST NOT assume any relationship between the owner of a domain name
    that is part of an ni URI and some matching content just because the
    ni URI matches that content."

Suggested text:

    While a name-data integrity service can be provided using ni URIs,
    that does not in any sense validate the authority part of the name.
    For example, there is nothing to stop anyone creating an ni URI
    containing a hash of someone else's content.  Application developers
    MUST NOT assume any relationship between the registrant of the domain
    name that is part of an ni URI and some matching content just because
    the ni URI matches that content.

I don't understand why the last sentence is phrased as a 
requirement.  The first two sentences has a clear explanation about 
the authority part of the name.  I would remove the third sentence.

Regards,
-sm 


From stephen.farrell@cs.tcd.ie  Mon Jun 11 05:39:25 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FDFC21F855B for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 05:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.699
X-Spam-Level: 
X-Spam-Status: No, score=-101.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_35=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 uPaAX3107Kzo for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 05:39:24 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 7D93D21F84E1 for <ietf@ietf.org>; Mon, 11 Jun 2012 05:39:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 990AE157557; Mon, 11 Jun 2012 13:39:20 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339418359; bh=xevK6nCRsGihtP dbhK8XJa9HzGIWPUEh2Dcx5dsMRpc=; b=qZEujOOmqAw1HMmcf3HuInYX9EhPJI IVc1lIUQl0xPNaS4fIZEZQyL08YUG/uHq4rWOHEpluaoHyhwlqLE24mfHBALjHWQ XjgsjVz8QN7I0DdoW6kPb9iBA9EzDdGrakzgY2A8nrbRzzLAsBXKqzVc3kg6/204 PwCUwFL+zIeZ0Q8ETryRDjv6EOGn077NbjOX8JkYcL4Lua26OAO83sZuPJOtesMj /kZaZsqD9CJGnWToRPZ7d4t3F73l0pV2PnilRDf3wD5EOUJW40Xj8EPfPdYkPqc7 xBiOuxxqMJJcx12Hs/UluNq7t9AG02EKpTG67lEC9aUxpa9oDUxeCRSg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id aWpVyWtDCo7D; Mon, 11 Jun 2012 13:39:19 +0100 (IST)
Received: from [IPv6:2001:770:10:203:d29:9f2:c54f:4963] (unknown [IPv6:2001:770:10:203:d29:9f2:c54f:4963]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id B5445157554; Mon, 11 Jun 2012 13:39:10 +0100 (IST)
Message-ID: <4FD5E6E8.90201@cs.tcd.ie>
Date: Mon, 11 Jun 2012 13:39:04 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: APPSDIR review of draft-farrell-decade-ni-07 (minor editorial)
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD5D0B5.5000608@it.aoyama.ac.jp>
In-Reply-To: <4FD5D0B5.5000608@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 12:39:25 -0000

Hi Martin,

On 06/11/2012 12:04 PM, "Martin J. Dürst" wrote:
> Hello Stephen,
> 
> As Barry has suggested, I'm removing apps-discuss@ietf.org to reduced
> cross-posting. I'm going to split my response into several installments,
> hopefully separating the less contentious issues from the more
> contentious ones, and starting with the former ones.
> 
> Also, I want to apologize for the delays here, related to "day job" duties.

No probs.

> 
> On 2012/06/05 20:11, Stephen Farrell wrote:
>>
>> Hi Martin,
>>
>> First, thanks for the speedy and thorough review. Some
>> good points made, some with which I strongly disagree,
>> but thrashing stuff like that out is part of the point
>> of the reviews.
>>
>> On 06/05/2012 10:42 AM, "Martin J. Dürst" wrote:
> 
>>> Minor editorial issues:
>>>
>>> Introduction: It would be good to have a general reference to hashing
>>> (for security purposes) for people not utterly familiar with the
>>> subject.
>>
>> Disagree. If I added that I could reasonably be asked to introduce
>> URIs for the security folks. Serious and pointless ratholes would ensue.
> 
> Okay.
> 
>>> Intro: After reading the whole document, the structure of the Intro
>>> seems to make some sense, but it didn't on first reading (where it's
>>> actually more important). The main problem I was able to identify was
>>> that after a general outlook in paragraph 1, the Intro drops into a list
>>> of examples without saying what they are good for. I suggest to, after
>>> the sentence "This document specifies standard ways to do that to aid
>>> interoperability.", add a sentence along the lines: "The next few
>>> paragraphs give usage examples for the various ways to include a hash in
>>> a name or identifier as they are defined later in this document.". It
>>> may also make sense to further streamline the following paragraphs, so
>>> that it is clearer which pieces of text refer each to one of the
>>> "standard ways".
>>>
>>> There are two instances of the term "binary presentation". Looking
>>> around, it seems that they are supposed to mean the same as "binary
>>> format". Please replace all instances of "binary presentation" with
>>> "binary format" to avoid misunderstandings and useless seach time.
>>>
>>> Section 3: "A Named Information (ni) URI consists of the following
>>> components:": It would be good to know exactly where the list ended. One
>>> way to do this would be to say "consists of the following nine
>>> components".
>>
>> Those look reasonable. Will see if the changes work out.
> 
> The change that I have seen in your pre-draft for the above three items
> look good.
> 
> 
>>> Section 3: "Note that while the ni names with and without an authority
>>> differ syntactically, both names refer to the same object if the digest
>>> algorithm and value are the same.": What about cases with different
>>> authority? The text seems to apply by transitivity, but this may be easy
>>> to miss for an implementer. I suggest changing to: "Note that while ni
>>> names with and without an authority, and ni names with different
>>> authorities, differ syntactically, they all refer to the same object if
>>> the digest algorithm and value are the same.".
>>
>> Sure.
> 
> Okay.
> 
>>> Section 3: "Consequently no special escaping mechanism is required for
>>> the query parameter portion of ni URIs.": Does this mean "no escaping
>>> mechanism at all"? Or "nothing besides %-encoding"? Or something else?
>>> Please clarify.
>>
>> I wish I knew:-) What do you think is right here? (Honestly,
>> input on this would be appreciated.)
> 
> (In your internal draft, you removed the paragraph just before this one,
> and now the "Consequently" doesn't make any sense anymore.)
> 
> One possibility here is to remove anything about encoding, and have
> people check in RFC 3986, but I guess you wanted to help the reader
> here, so I'd propose something along the following lines (replacing the
> "Consequently" paragraph, and also in some sense the paragraph before
> that you already removed):
> 
> <<<<
> Escaping of characters follows the rules in RFC 3986. This means that
> %-encoding is used to distinguish between reserved and unreserved
> functions of the same character in the same URI component. As an
> example, an ampersand ('&') is used in the query part to separate
> attribute-value pairs; an ampersand in a value therefore has to be
> escaped as '%26'. Note that the set of reserved characters differs for
> each component, as an example, a slash ('/') does not have any reserved
> function in a query part and therefore does not have to be escaped.
> However, it can still appear escaped as '%2f' or '%2F', and
> implementations have to be able to understand such escaped forms.
> Also note that any characters outside those allowed in the respective
> URI component have to be escaped.
> <<<<

That looks good to me, ta. I've put it in.

>>> Figure 3: the "=" characters of the various rules should be aligned as
>>> much as possible to make it easier to scan the productions (see
>>> http://tools.ietf.org/html/rfc3986#appendix-A for an example).
>>
>> Ack.
> 
> Great.
> 
>>> Section 3:
>>>              unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"
>>>                  ;  directly from RFC 3986, section 2.3
>>>                  ; "authority" and "pct-encoded" are also from RFC 3986
>>> Please don't copy productions. Please don't copy half (or one-third,
>>> actually) of the productions you use, and reference the rest. Please
>>> don't say what productions you copy from where in a comment, and even
>>> less in a comment for an unrelated production. Please before the ABNF,
>>> say which productions are used from another spec.
>>
>> We got contrary advice from elsewhere (can't recall where right now;-).
>> I'll let Barry (as sponsoring AD) just tell us his preference and go
>> with that if that's ok.
> 
> If you want to do it in a different way, you should at least be
> consistent. That would mean to also copy "authority" and "pct-encoded".
> The later is easy, but the former would really be too much. That's why
> I'd kick out "unreserved", too.

Ok, I've now done a version that tries to copy as much
as possible unmodified from 3986. Let me know if its
right this time:-)

> 
> 
>>> Section 4:
>>>     The HTTP(S) mapping MAY be used in any context where clients without
>>>     support for ni URIs are needed without loss of interoperability or
>>>     functionality.
>>> This is difficult to understand. If some new functionality is proposed,
>>> it's usually a client *with* the new functionality that's needed, not
>>> one without. Also, the "without loss of interoperability or
>>> functionality" is unclear: Sure if ni isn't supported, there's a loss in
>>> interoperability. So I suggest to rewrite this as:
>>>     The HTTP(S) mapping MAY be used in any context where clients with
>>>     support for ni URIs are not available.
>>
>> Sure.
> 
> Great. But in your internal draft, the period at the end of the sentence
> is now missing. (unless there's a bug in the diff)

Now full stopped:-)

>>> (but see also the comment in minor technical issues)
>>>
>>> Section 6: "binary format name": Why 'name'? Why not just "binary
>>> format"? The later is completely clear in the context of the document or
>>> together with an indication of the document; for something that can be
>>> used independently, even "binary format name" isn't enough.
>>
>> I don't get the problem with that.
> 
> You had "binary presentation", and changed that to "binary format" as
> per my suggestion. This is a very similar suggestion to align
> terminology. In the later half of the above comment, I was just trying
> to speculate about reasons for the difference, an the only reason I came
> up with was that it would be good to have a longer term that could be
> used independently outside the document.
> 
> 
>>> Section 6: "suite ID": The word "suite" seems out of place here. In the
>>> general use of the term, it refers to "a group of things forming a unit
>>> or constituting a collection" (see
>>> http://www.merriam-webster.com/dictionary/suite). A good definition that
>>> works for the uses I'm familiar with in digital security would be "An
>>> algorithm suite is a coherent collection of cryptographic algorithms for
>>> performing operations such as signing, encryption, generating message
>>> digests, and so on."
>>> (http://fusesource.com/docs/framework/2.4/security/MsgProtect-SOAP-SpecifyAlgorithmSuite.html;
>>>
>>> disclaimer: I'm in no way a SOAP fan). The use here is not for a
>>> collection, but for a single truncated-length variant of a single hash
>>> algorithm. I seriously hope you can find a better name.
>>
>> That's a don't-care for me. I think suite is fine, but could
>> take other terms (so long as its not "algorithm"). Suite could
>> be justified since we have alg+truncation here, but like I
>> said I'd be fine to change, if a good suggestion is made.
> 
> What about "Truncated Hash ID" or "Hash Truncation ID" or some such? I'm
> open to other ideas, too.

Well, the suite IDs don't have to related to a truncated
hash, but can also be full length. Sticking with suite ID
for now.

>>> Section 6: "Note that a hash value that is truncated to 120 bits will
>>> result in the overall name being a 128-bit value which may be useful
>>> with certain use-cases.": This left me really wondering: Is there
>>> something magic to 128 bits in computer/internet security? What are the
>>> "certain use cases"? Or is this just an example to make sure the reader
>>> got the relationships, and it could have been as well "Note that a hash
>>> value that is truncated to 64 bits will result in the overall name being
>>> a 72-bit value which may be useful with certain use-cases." (or whatever
>>> other value that's registered in section 9)?
>>
>> Bit of both. I believe the core WG are keen to end up with a 128 bit
>> binary value as their preferred option.
> 
> Is there a way to word this that doesn't leave the reader wondering how
> she is supposed to understand this?

Tweaked. Though I still don't think its at all unclear.

> 
>>> Section 7: Just for the highly unfortunate case that this doesn't
>>> disappear, it would be very helpful if the presentation of this section
>>> paralleled section 3.
>>
>> Disagree. Different requirements, different URIs, different
>> presentation. I don't think there's a real problem here.
> 
> I'll address the "Different requirement" in a separate thread. In
> general, I'd expect that if a draft defines 2 of the same thing (e.g.
> two mime types,...), that it streamlines the presentation as far as
> possible. That this hadn't been done was part of the reason for my
> impression that this draft got patched together. But I think we should
> put of streamlining, because I hope that section 7 will disappear anyway
> :-).

Still disagree:-)

> 
> 
>>> Section 7: "contain the ID value as a UTF-8 encoded decimal number": I'm
>>> an internationalization expert with a strong affection for UTF-8, but
>>> even for me, this should be "contain the ID value as an ASCII encoded
>>> decimal number".
>>
>> Fine.
>>
>>>
>>> Section 9: The registration templates refer to sections. This is fine
>>> for readers of the draft, but not if the template is standalone. I
>>> suggest using a format such as that at
>>> http://tools.ietf.org/html/rfc6068#section-8.1, which in draft stage may
>>> look e.g. like
>>> http://tools.ietf.org/html/draft-duerst-eai-mailto-03#section-8.1.
>>
>> Will take a peek. Not sure I agree. (Nor disagree:-)
> 
> Okay, let me know when you have made up your mind.

Turns out I disagree.

> 
>>> Section 9.3: "Assignment of Well Known URI prefix ni" and later (and
>>> elsewhere in the draft) "URI suffix": Are we dealing with a prefix or a
>>> suffix here?
>>
>> Will take a peek.
> 
> For your information, the registry is just named "Well-Known URIs"
> (http://www.iana.org/assignments/well-known-uris/well-known-uris.xml).
> Other drafts
> (http://tools.ietf.org/html/draft-daboo-srv-caldav-10#section-9.1,
> http://tools.ietf.org/html/draft-daboo-srv-caldav-10#section-9.2,
> http://tools.ietf.org/html/draft-ietf-core-link-format-14#section-7.1,
> http://tools.ietf.org/html/rfc6415#section-6.1,
> http://tools.ietf.org/html/rfc6415#section-6.2) have neither "prefix"
> nor "suffix" in the section title. I suggest to follow these, it will be
> less confusing.

Ok, I copied from the core link format.

>>> Section 9.4: "This registry has five fields, the binary suite ID,...":
>>> Better to remove the word "binary", because the actual number is
>>> decimal.
>>
>> Ack.
>>
>>>
>>> Section 9.4: "The expert SHOULD seek IETF review before approving a
>>> request to mark an entry as "deprecated."  Such requests may simply take
>>> the form of a mail to the designated expert (an RFC is not required).
>>> IETF review can be achieved if the designated expert sends a mail to the
>>> IETF discussion list.  At least two weeks for comments MUST be allowed
>>> thereafter before the request is approved and actioned.": I'm at a loss
>>> to see why asking the IETF at large is a SHOULD, but if it's done, then
>>> the two weeks period is a MUST.
>>
>> I don't get your comment. The two weeks is a MUST already.
> 
> This combination of SHOULD and MUST just doesn't feel right to me. Let
> me try with a different subject area which may make it easier to get my
> point.
> 
> What would you think if a document said something: "The expert SHOULD
> donate money to the IETF. If the expert donates money, s/he MUST donate
> at least $200."
> 
> As this example hopefully shows, MUSTs conditioned by SHOULDs don't
> really make sense. Or is this really just me ?-)
> 
> And let me give another try. Let's assume the expert wants to make a
> decision after one week, but still inform the IETF discussion list. She
> can just send a mail to that list saying "This is not a formal review
> according to Section 9.4 of RFC YYYY, but I'm planning to deprecate this
> entry in a week unless I hear good reasons to do otherwise." Logically
> speaking, that would be following the RFC, and shows that the MUST
> doesn't make sense, because it can't force anything.

I've changed the SHOULD seek IETF review to a MUST. I guess that
makes sense.

> 
> 
>>> Section 9.4: The registry initialization in Fig. 8 refers to RFC4055
>>> many times. But RFC 4055 does in no way define SHA-256. It looks like
>>> the actual spec is http://tools.ietf.org/html/rfc4055#ref-SHA2 (National
>>> Institute of Standards and Technology (NIST), FIPS 180-2: Secure Hash
>>> Standard, 1 August 2002.) I think this should be cited, in particular
>>> because there is a "Specification Required" requirement, and this sure
>>> should mean that there is a Specification for the actual algorithm, and
>>> not just a specification that mentions some labels. So using RFC4055 as
>>> a reference could be taken as creating bad precedent.
>>
>> I guess so. Good catch.
> 
> Great.
> 
>>> Section 9.4: "The designated expert is responsible for ensuring that the
>>> document referenced for the hash algorithm is such that it would be
>>> acceptable were the "specification required" rule applied.": Why all
>>> this circumscription? Why not just say something like: "The designated
>>> expert is responsible for ensuring that the document referenced for the
>>> hash algorithm meets the "specification required" rule."
>>
>> Honestly? I can't recall:-) Will change unless I do remember.
> 
> Okay.
> 
>>> Nits:
>>>
>>> Author's list: Last time I heard about this, there was a general limit
>>> of 5 authors per RFC. I'm not sure whether this still exists, and what'd
>>> be needed to get around it, but I just wanted to point out that this may
>>> be a potential problem or additional work (hoops to get through).
>>>
>>> Intro: "Since, there is no standard" ->  "Since there is no standard"
>>>
>>> Intro: "for these various purposes" ->  "for these purposes" or "for
>>> various purposes" (the indefinite 'various' is incompatible with the
>>> definite 'these').
>>>
>>> "2.  Hashes are what Count" ->  "2.  Hashes are what Counts" (the former
>>> may look logically correct, but 'what' requires a singular verb form.
>>>
>>> Section 2: "the left-most or most significant in network byte order N
>>> bits from the binary representation of the hash value" ->  "the
>>> left-most
>>> (or most significant in network byte order) N bits from the binary
>>> representation of the hash value" or "the left-most N bits, or the N
>>> most significant bits in network byte order, from the binary
>>> representation of the hash value" (the current text is virtually
>>> unparsable).
> 
> You seem to disagree with this, but every time I try to read the above
> sentence, I have to take two or three attempts. And given my long-time
> training in German and Japanese, I have to admit that I'm quite used to
> long and convoluted sentences :-).

Tweaked.

> 
> 
>>> Figure 1: The 0x notation is never explained. A short clause or pharse
>>> is all that would be needed, but it would be better if this were spelled
>>> out.
>>>
>>> Section 3, Query Parameter separator: "The query parameter separator
>>> acts a separator between" ->  "The query parameter separator acts *as* a
>>> separator between".
>>>
>>> Section 3, Query Parameters: "A tag=value list of optional query
>>> parameters as are used with HTTP URLs" ->   "A tag=value list of
>>> optional
>>> query parameters as used with HTTP URLs" (or "A tag=value list of
>>> optional query parameters as they are used with HTTP URLs").
>>>
>>> Section 4: "the object named by the ni URI will be available at the
>>> corresponding HTTP(S) URL" ->  "the object named by the ni URI will be
>>> available via the corresponding HTTP(S) URL" (via stresses the point
>>> that this should be done via (sic) redirection)
>>>
>>> Section 4: "so there may still be reasons to use" ->  "so there can
>>> still
>>> be reasons to use" (better to use can because non-normative; the
>>> document otherwise does a good job on this)
>>>
>>> Section 10: "Note that fact that" ->  "Note the fact that", or much
>>> better: "Note that".
>>
>> Those look ok or are nits in any case.
> 
> Other than indicated above, I'm fine with the changes for these
> issues/nits that you have made (or not made) in your internal copy.
> 
> 
> Regards,    Martin.
> 
> (more replies tomorrow)

Grand. I've updated the working copy at [1] with those changes.

Thanks,
S.

[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-decade-ni.txt

> 
>> Thanks again for the thorough review even though we disagree as
>> to the main point.
>>
>> Cheers,
>> Stephen.
>>
>>
>>>
>>>
>>> Regards,     Martin.
>>>
>>>
>>>
>>
> 
> 

From stephen.farrell@cs.tcd.ie  Mon Jun 11 05:51:30 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC9121F85AA for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 05:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 62I+TYAerXYD for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 05:51:29 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id A9A5B21F8566 for <ietf@ietf.org>; Mon, 11 Jun 2012 05:51:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id ABDDC157557; Mon, 11 Jun 2012 13:51:24 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339419084; bh=Hezzpi88W9vePs tEnA1wKnOd15R06W9ihOK2oxdRl48=; b=X7n8TuLhNZEeC5O5mX5CTEcOoExc7R Ce5N1jwdW6B9GXCaaY9O1+h6T8qawkthhzHpwZqiYI5CwW6fGkPSNIjzmxF0H1Fx aLKK4ryhCCyXkOwz9+GDWXiY85yn4m7TAIjqIozBE9xQtqI3KfXGI81QpWtKlQGJ 9k59dSjUF57UD+pyAXO0OAZ++J0NY+8v745crgUHyVsNE0cmtw4HsrxOjdx9LF6w Cl5fg5UBMNA9jjk4sPDYsw2H1RLrOrpHa1/z5r5TgnSmyITQDK5+oNV5FAs9PIgB 4fUFnGsNFJsyanRowjdhENbsq6f49mwczRph9PkvJTiX4epHsMLzYsZw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id knD0OGUnKxAg; Mon, 11 Jun 2012 13:51:24 +0100 (IST)
Received: from [IPv6:2001:770:10:203:d29:9f2:c54f:4963] (unknown [IPv6:2001:770:10:203:d29:9f2:c54f:4963]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 01C27157554; Mon, 11 Jun 2012 13:51:23 +0100 (IST)
Message-ID: <4FD5E9CB.4040906@cs.tcd.ie>
Date: Mon, 11 Jun 2012 13:51:23 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120611042706.095ba210@resistor.net>
In-Reply-To: <6.2.5.6.2.20120611042706.095ba210@resistor.net>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, draft-farrell-decade-ni@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 12:51:30 -0000

On 06/11/2012 01:30 PM, SM wrote:
> At 07:18 04-06-2012, The IESG wrote:
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Naming Things with Hashes'
>>   <draft-farrell-decade-ni-07.txt> as Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2012-07-02. Exceptionally, comments may be
> 
> Here's an editorial comment about Section 9.4 and Section 10.
> 
> Move the following to the first paragraph or a separate paragraph as it
> is not related to the second paragraph:
> 
>   'Note that if the status is not "deprecated" (it is empty), then that
>    does not necessarily mean that the algorithm is "good" for any
>    particular purpose, since the cryptographic strength requirements
>    will be set by other applications or protocols.'

Ok.

> 
> And for:
> 
>   'The expert SHOULD seek IETF review before approving a request to
>    mark an entry as "deprecated."  Such requests may simply take the
>    form of a mail to the designated expert (an RFC is not required).
>    IETF review can be achieved if the designated expert sends a mail
>    to the IETF discussion list.  At least two weeks for comments MUST
>    be allowed thereafter before the request is approved and actioned.'
> 
> Suggested text with pointers to comments:
> 
>   A request to mark an entry as "deprecated" can be done by sending
>   a mail to the designated expert.  Before approving the request,
>   the community should be consulted via a "call for comments" of
>   at least two weeks by sending a mail to the IETF discussion list.
> 
> Near the end of Page 14:
> 
>  "The expert MAY request IETF review before allocating a
>   suite ID."
> 
> Suggested:
> 
>  The designated expert may consult the community via a "call for
>  comments" by sending a mail to the IETF discussion list before
>  allocating a suite ID.
> 
> I avoided using the term "IETF review" because it is used policy
> definition in the BCP.  I leave it to the authors to apply RFC 2119
> casing as appropriate.

That looks better all right, thanks.

> 
> In Section 10:
> 
>   "While a name-data integrity service can be provided using ni URIs,
>    that does not in any sense validate the authority part of the name,
>    for example, there is nothing to stop anyone creating an ni URI
>    containing a hash of someone else's content so application developers
>    MUST NOT assume any relationship between the owner of a domain name
>    that is part of an ni URI and some matching content just because the
>    ni URI matches that content."
> 
> Suggested text:
> 
>    While a name-data integrity service can be provided using ni URIs,
>    that does not in any sense validate the authority part of the name.
>    For example, there is nothing to stop anyone creating an ni URI
>    containing a hash of someone else's content.  Application developers
>    MUST NOT assume any relationship between the registrant of the domain
>    name that is part of an ni URI and some matching content just because
>    the ni URI matches that content.
> 
> I don't understand why the last sentence is phrased as a requirement. 
> The first two sentences has a clear explanation about the authority part
> of the name.  I would remove the third sentence.

Looks better all right, thanks.

Updated at [1] again.

S.

[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-decade-ni.txt

> 
> Regards,
> -sm
> 

From jonathan.rees@gmail.com  Thu Jun  7 17:35:44 2012
Return-Path: <jonathan.rees@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88F2411E8157 for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 17:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 V8JBXHoRIKLi for <ietf@ietfa.amsl.com>; Thu,  7 Jun 2012 17:35:43 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6EA3811E809A for <ietf@ietf.org>; Thu,  7 Jun 2012 17:35:43 -0700 (PDT)
Received: by dacx6 with SMTP id x6so1606933dac.31 for <ietf@ietf.org>; Thu, 07 Jun 2012 17:35:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Q/IluWru5J3LWcG4SzmUAqOcPzUgEhaM+QCzqn4LtqA=; b=Wj/ODT4AuMuMwJduSmYp2FSRMwXjnsKj+InYDza5KLp0hKYS27ZsMwq3eLmugL3xOz Cu0stexgSh/aTFCp9KtfsePMn3iR4xZMkfnIkpLFF+4gJOqCIfBc8c7xWvzd4ASjczr7 HY5bG2YkorBtNp3ID3H6XeTSNrZ5Tvv6xzOOCDbbD1BzYdZLczwtHYmYr3e1KH+XCt/s aZl+HhvD683eJtxp11G8xm2qU3ZFmR6FfnJuCT7lKtGNlikdpsya6X7cXTYH29L9lbC2 ADE7grGKsh/xgE6KwNCf80RePslsBQuIcGfDFRp7eG0amxED2rDAlyQ6QCwmCsCaKjG8 75dg==
MIME-Version: 1.0
Received: by 10.68.216.2 with SMTP id om2mr15309212pbc.26.1339115743068; Thu, 07 Jun 2012 17:35:43 -0700 (PDT)
Sender: jonathan.rees@gmail.com
Received: by 10.143.5.7 with HTTP; Thu, 7 Jun 2012 17:35:43 -0700 (PDT)
In-Reply-To: <4FD0FDC2.2090802@cs.tcd.ie>
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com> <4FD0FDC2.2090802@cs.tcd.ie>
Date: Thu, 7 Jun 2012 20:35:43 -0400
X-Google-Sender-Auth: sryjDKvUVfGY_ReNIplStaxtDDE
Message-ID: <CAGnGFMLc15-ZkD_Of7k0zK7ef-i6HN2LsPCfbW3pkwFkpSiOfA@mail.gmail.com>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
From: Jonathan A Rees <rees@mumble.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 11 Jun 2012 07:33:25 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 00:35:44 -0000

On Thu, Jun 7, 2012 at 3:15 PM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
>
> On 06/06/2012 09:33 PM, Jonathan A Rees wrote:
>> As requested I am sending comments on this last call draft to
>> ietf@ietf.org. I sent them to the authors on 6 May but received no
>> reply.
>
> Once again, sorry about that. No idea why I missed responding,
> your mail is in my client even. Ah well.
>
>>
>> Jonathan Rees
>>
>>
>> ---------- Forwarded message ----------
>> From: Jonathan A Rees <rees@mumble.net>
>> Date: Sun, May 6, 2012 at 7:57 PM
>> Subject: comments on http://tools.ietf.org/html/draft-farrell-decade-ni-=
06
>> To: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba
>> <barryleiba@computer.org>, "S. Farrell" <stephen.farrell@cs.tcd.ie>,
>> "P. Hallam-Baker" <pbaker@verisign.com>
>>
>> Here are some opinions on
>> http://tools.ietf.org/html/draft-farrell-decade-ni-06 :
>>
>> I think this URI scheme would be a welcome addition to web
>> architecture. Wide review should be sought, because this might become
>> quite important and if there are problems they will be very difficult
>> to fix later.
>>
>> I think using .well-known is a good idea.
>>
>> I think integration into the ecosystem, such as browser support,
>> should be anticipated; for this reason I think content type should be
>> elevated from an 'optional feature' to a 'required feature'.
>>
>> [i.e. conformant implementations must support it, even if providing
>> the content type in the URI is itself optional.]
>
> I could certainly live with that, and I suspect my co-authors too,
> but I'd need to ask 'em. However, we'd like to see more support for
> it before doing that. If we only hear from you on this, then I
> think leaving it in the other draft would be right. (See below
> for why we want to keep that draft.) I guess others have a few
> weeks to chime in on this.

OK, I suspect I can find other W3C TAG members who would agree; will circul=
ate.

It is certainly strongly promoted by the W3C web architecture document, see
http://www.w3.org/TR/webarch/#internet-media-type
so I think I have W3C consensus (as of 2005) behind my claim.

>> If you
>> don't do this, you are just encouraging sniffing and privilege
>> escalation attacks. Sniffing would be a big step backwards. Better to
>> do what the data: scheme does and say that there is a default content
>> type of, say, text/plain, and that otherwise the content type ought to
>> be specified in the URI.
>>
>> Content-type privilege escalation risk (and incorrect sniffing risk)
>> should be mentioned in the security considerations section in any
>> case.
>
> Would appreciate text if you can offer some. (Always happy to
> make the sec. cons. bit better.)

Hmm. Hot potato.
Maybe something can be derived from Adam's draft
http://tools.ietf.org/html/draft-abarth-mime-sniff-06
which I assume you've seen...  obviously I'd prefer you do the
drafting, but will consider myself pressured.

>> Maybe the risk that the host used for retrieval might be spoofing the
>> content-type (by providing a bogus content-type in an HTTP response)
>> should also be mentioned.
>
> Good one. Yep, we should mention this whereever ct=3D is described

No, this is a threat even if ct=3D isn't used. Suppose that the document
is intended as an unscriptable media type, but the (malicious) server
sets the content-type: header in the response to a scriptable type.
Not good. I think this threat is described in Adam's draft.

>> (A possible design would be to put the
>> content-type (and maybe other headers like Expires:?) in the hashed
>> content, to be pulled out into the HTTP response when the content is
>> served by an http server and then checked by the client, but I
>> understand that this would be a tooling headache.)
>
> Yep. We thought about it but agree that it gets too complex too
> quickly. Maybe with a bit of experience...
>
>> (I don't understand why you want to separate the 'optional' features
>> into a separate spec. This made me miss the ct=3D feature entirely at
>> first.)
>
> The intent is to put stuff there if we're not sure if its
> ready or needed everywhere. ct=3D is definitely the main
> candidate feature for moving to the "base" spec though.
> Some other things (e.g. handling dynamic content) are
> way more experimental and should definitely not move
> and maybe need more time before we want them in an RFC.
>
> If all this does get popular then the RFCs can be revised later
> based on experience in any case. (If nobody cares, then it
> won't be a problem:-) So I don't think where things are
> documented now is hugely important in the long term.

Hmm... if this spec takes off like I hope it will, you will have more
influence than you think now, so the implicit messages will be
important... by putting ct=3D in a separate document you're saying that
it's not important, and you'll encourage implementations that use
sniffing instead of some rational way to convey the media type.

>> I think the documentation should say that the hash and content type
>> together identify the resource,
>
> Well, IMO the hash identifies the resource (if name-data integrity
> is verified) so I don't think I agree that the content type is
> key for identification. It is for interpretation (or whatever
> the right term there is, maybe rendering?) and probably other
> things.

Well maybe we're quibbling over terminology, but in the HTTP spec and
in all the W3C documents, the media type is part of the resource (or
"representation" in HTTPbis; the distinction is immaterial for your
URI scheme), and therefore part of its identity. It would be
unfortunate to introduce an incompatible world view into the RFC
corpus.

>> and that because the content can be
>> verified, the resource can be sought (using the .well-known path, or
>> any other path for that matter) from any source that the client thinks
>> might have it.
>
> Absolutely. That's our primary motivation for all this.
>
>> The primary and alternate domain name(s), and 'wrapped'
>> URLs, are only provided as hints.
>
> Yes.
>
>> I agree with other commenters on the peculiarity of using // to
>> provide the location hint since the named host is not being trusted as
>> an authority. I don't understand why the 'primary' location isn't just
>> encoded in the query, just like the alternate domain(s) and "wrapped
>> URL(s)". =A0This would have the nice property that you can put the
>> identifying parts (i.e. hash and content type) first, and the less impor=
tant
>> location hints parts all together after the identification. The various
>> location hints (whether primary or secondary) would go together and
>> their similarity would be clearer.
>>
>> (Unless I'm misunderstanding something and the part after the //
>> actually has status other than a hint? =A0That would seem to defeat
>> the purpose.)
>
> I think we could argue this (and we did already between the authors;-)
> and it'd come down to "pick a way." We did already and wrote code
> for that, so we'd prefer to stick with it as-is, especially if there's
> no compelling reason to change. I think its likely we can agree that
> there's no compelling differences here in whether we use "//" or
> a "?loc=3D" or whatever.

Well, you have a chance to fix this now, and it will be impossible to
fix later. Using // is contrary to RFC 3986, which very clearly says
"governance of the name space defined by the remainder of the URI is
delegated to that authority". This is certainly not what this URI
scheme does, so use of // is contrary to the appicable normative spec.

Best
Jonathan

> Cheers,
> Stephen.
>
>
>>
>> Jonathan
>>
>>

From dan.pitt@opennetworking.org  Wed Jun  6 16:12:31 2012
Return-Path: <dan.pitt@opennetworking.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A38811E80F0 for <ietf@ietfa.amsl.com>; Wed,  6 Jun 2012 16:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.844
X-Spam-Level: 
X-Spam-Status: No, score=-3.844 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, SARE_GIF_ATTACH=1.42]
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 Qu-JzEMRXdCo for <ietf@ietfa.amsl.com>; Wed,  6 Jun 2012 16:12:30 -0700 (PDT)
Received: from smtp207.dfw.emailsrvr.com (smtp207.dfw.emailsrvr.com [67.192.241.207]) by ietfa.amsl.com (Postfix) with ESMTP id 6960411E808F for <ietf@ietf.org>; Wed,  6 Jun 2012 16:12:21 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp20.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id E15DC2599D7; Wed,  6 Jun 2012 19:12:20 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp20.relay.dfw1a.emailsrvr.com (Authenticated sender: dan.pitt-AT-opennetworking.org) with ESMTPSA id 804D8259947;  Wed,  6 Jun 2012 19:11:58 -0400 (EDT)
From: Dan Pitt <dan.pitt@opennetworking.org>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-1--60163670
Date: Wed, 6 Jun 2012 16:11:29 -0700
Subject: Liaison letter from ONF to IETF
To: ietf@ietf.org, iesg@ietf.org
Message-Id: <316729C3-4C8C-4F75-813B-A4CFB2275480@opennetworking.org>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Mon, 11 Jun 2012 07:33:25 -0700
Cc: Dan Pitt <dan.pitt@opennetworking.org>, iab@iab.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 04:59:16 -0000

--Apple-Mail-1--60163670
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

To: IETF
From: Dan Pitt, executive director, ONF
Subject: Liaison between ONF and IETF

ONF (www.opennetworking.org) was established to promote Software Defined =
Networking (SDN) by creating a forum for users and vendors to discuss =
all aspects of SDNs, to create technical specifications and standards, =
and to evangelize SDNs to the networking industry and its customers. =
ONF=92s scope spans data planes, control planes, and management planes, =
enabling programmability and management of the SDN.=20

ONF's first task has been to standardize the OpenFlow protocol, the =
lowest level building block upon which SDN networks can be built. =
OpenFlow conveys flow-based forwarding information from a logical entity =
called a controller (or network operating system), which embodies the =
control-plane intelligence, to the network switches, which actually =
forward the packets based on directions received from the controller. =
The OpenFlow protocol therefore represents the controller=92s southbound =
interface, and a protocol is indeed necessary because the switches and =
controller are assumed to be physically and geographically separate.

The controller=92s conceptual northbound interface permits other =
software entities representing such factors as policy, security, traffic =
engineering, and energy management to influence the controller=92s =
determination of flow paths. ONF has not yet standardized the =
controller=92s northbound interface, or determined its nature, and so it =
is too early to standardize orchestration of SDNs controlled via ONF =
standards.=20

We in ONF are very interested to discuss potential SDN use cases =
developed by the IETF with a view to demonstrating how these can be =
expressed with ONF constructs, possibly as direct functions of the =
controller. ONF is further interested in the IETF=92s orchestration of =
existing, stable non-SDN data and control planes that already have =
stable northbound interfaces (e.g., SNMP MIB, Netconf/Netmod).

We recommend that ONF and IETF work together on SDN specifications, =
under the ONF framework of chartered ONF Working Groups (via mailing =
lists, wikis, and conference calls), ONF discussion groups (via mailing =
lists, wikis, and conference calls), and the ONF Technical Advisory =
Group (for oversight).=20

ONF specifications will use and interact with IETF standards, such as =
Netconf and BFD. As ONF develops SDN specifications, ONF will work with =
IETF to bring requests for additions and changes to existing IETF =
specifications, and for new code points, as the need arises.

ONF further believes there would be considerable benefit if code points =
defined in ONF specifications are assigned from registries managed by =
the IANA (Internet Assigned Numbers Authority). We would like to discuss =
with you the best way to achieve this.

Finally, ONF is interested in discussing cross-publishing future =
specifications at the IETF, and would welcome a discussion on how best =
to accomplish this as well.


Dan Pitt
Executive Director
Open Networking Foundation
Palo Alto, California
m. 617-803-5938
dan.pitt@opennetworking.org
www.opennetworking.org



--Apple-Mail-1--60163670
Content-Type: multipart/related;
	type="text/html";
	boundary=Apple-Mail-2--60163669


--Apple-Mail-2--60163669
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">To: =
IETF<div>From: Dan Pitt, executive director, ONF</div><div>Subject: =
Liaison between ONF and IETF</div><div><br></div><div><p style=3D"margin: =
0.0px 0.0px 10.0px 0.0px; font: 13.0px Arial"><span =
style=3D"letter-spacing: 0.0px"><font class=3D"Apple-style-span" =
face=3D"Helvetica" size=3D"3">ONF (<a =
href=3D"http://www.opennetworking.org)"><span style=3D"text-decoration: =
underline ; letter-spacing: 0.0px color: =
#0225a3">www.opennetworking.org)</span></a>&nbsp;was established to =
promote Software Defined Networking (SDN) by creating a forum for users =
and vendors to discuss all aspects of SDNs, to create technical =
specifications and standards, and to evangelize SDNs to the networking =
industry and its customers.&nbsp;ONF=92s scope spans data planes, =
control planes, and management planes, enabling programmability and =
management of the SDN.&nbsp;</font></span></p><p style=3D"margin: 0.0px =
0.0px 10.0px 0.0px; font: 13.0px Arial"><span style=3D"letter-spacing: =
0.0px"><font class=3D"Apple-style-span" face=3D"Helvetica" =
size=3D"3">ONF's first task has been to standardize the OpenFlow =
protocol, the lowest level building block upon which SDN networks can be =
built. OpenFlow conveys flow-based forwarding information from a logical =
entity called a controller (or network operating system), which embodies =
the control-plane intelligence, to the network switches, which actually =
forward the packets based on directions received from the controller. =
The OpenFlow protocol therefore represents the controller=92s southbound =
interface, and a protocol is indeed necessary because the switches and =
controller are assumed to be physically and geographically =
separate.</font></span></p><p style=3D"margin: 0.0px 0.0px 10.0px 0.0px; =
font: 13.0px Arial"><span style=3D"letter-spacing: 0.0px"><font =
class=3D"Apple-style-span" face=3D"Helvetica" size=3D"3">The =
controller=92s conceptual northbound interface permits other software =
entities representing such factors as policy, security, traffic =
engineering, and energy management to influence the controller=92s =
determination of flow paths. ONF has not yet standardized the =
controller=92s northbound interface, or determined its nature, and so it =
is too early to standardize orchestration of SDNs controlled via ONF =
standards.&nbsp;</font></span></p><p style=3D"margin: 0.0px 0.0px 10.0px =
0.0px; font: 13.0px Arial"><span style=3D"letter-spacing: 0.0px"><font =
class=3D"Apple-style-span" face=3D"Helvetica" size=3D"3">We in ONF are =
very interested to discuss potential SDN use cases developed by the IETF =
with a view to demonstrating how these can be expressed with ONF =
constructs, possibly as direct functions of the controller. ONF is =
further interested in the IETF=92s orchestration of existing, stable =
non-SDN data and control planes that already have stable northbound =
interfaces (e.g., SNMP MIB, Netconf/Netmod).</font></span></p><p =
style=3D"margin: 0.0px 0.0px 10.0px 0.0px; font: 13.0px Arial"><span =
style=3D"letter-spacing: 0.0px"><font class=3D"Apple-style-span" =
face=3D"Helvetica" size=3D"3">We recommend that ONF and IETF work =
together on SDN specifications, under the ONF framework of chartered ONF =
Working Groups (via mailing lists, wikis, and conference calls), ONF =
discussion groups (via mailing lists, wikis, and conference calls), and =
the ONF Technical Advisory Group (for =
oversight).&nbsp;</font></span></p><p style=3D"margin: 0.0px 0.0px =
10.0px 0.0px; font: 13.0px Arial"><span style=3D"letter-spacing: =
0.0px"><font class=3D"Apple-style-span" face=3D"Helvetica" size=3D"3">ONF =
specifications will use and interact with IETF standards, such as =
Netconf and BFD. As ONF develops SDN specifications, ONF will work with =
IETF to bring requests for additions and changes to existing IETF =
specifications, and for new code points, as the need =
arises.</font></span></p><p style=3D"margin: 0.0px 0.0px 10.0px 0.0px; =
font: 13.0px Arial"><span style=3D"letter-spacing: 0.0px"><font =
class=3D"Apple-style-span" face=3D"Helvetica" size=3D"3">ONF further =
believes there would be considerable benefit if code points defined in =
ONF specifications are assigned from registries managed by the IANA =
(Internet Assigned Numbers Authority). We would like to discuss with you =
the best way to achieve this.</font></span></p><p style=3D"margin: 0.0px =
0.0px 10.0px 0.0px; font: 13.0px Arial"><span style=3D"letter-spacing: =
0.0px"><font class=3D"Apple-style-span" face=3D"Helvetica" =
size=3D"3">Finally, ONF is interested in discussing cross-publishing =
future specifications at the IETF, and would welcome a discussion on how =
best to accomplish this as well.</font></span></p></div><div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Dan Pitt<br>Executive =
Director<br>Open Networking Foundation<br>Palo Alto, California<br>m. =
617-803-5938<br><a =
href=3D"mailto:dan.pitt@opennetworking.org">dan.pitt@opennetworking.org</a=
><br>www.opennetworking.org<br></div></span></span></span></span></span></=
span><span><img height=3D"60" width=3D"244" =
id=3D"a8cf3336-0a68-4af2-bac2-be54cd81110d" apple-width=3D"yes" =
apple-height=3D"yes" =
src=3D"cid:F70E8F22-82C9-400E-B7D8-B85F373B6C7A@wp.comcast.net"></span>
</div>
<br></div></body></html>=

--Apple-Mail-2--60163669
Content-Transfer-Encoding: base64
Content-Disposition: inline;
	filename=onf-email-sig.gif
Content-Type: image/gif;
	name="onf-email-sig.gif"
Content-Id: <F70E8F22-82C9-400E-B7D8-B85F373B6C7A@wp.comcast.net>

R0lGODlh9AA8AOYAADBuczCSjVlWV+TvmW1qa1DHkrjYOGuyaXumUABmnWuVVfHx8Ry9vnykxKrY
R4u3TXnY6AdSib3r8gKnyUWNswB1qPP3ytXy8b7Y5pHL0QCWvnHNd0evizCmmsbdLlTFzy22qABc
lrPSsdbs1KK6OXu/ZN7oVhx2je/5+5OyuLHN0XXQrQ66yhyFl0OuzRxog0eMciySu5/LR7vjs43L
WX+91ZHUmEebfbnSdA5ymDczNHG3qluds22blA6Do1iMl5zfzmWfZFWte+357kF7p5He5KLYZTfH
2IfYrFWUaqPEgCh1phyiqzCuzZGPj8jHxwBKigBsoo3UXwCBsACdw+Pj45vWUznCpgCx0dbV1QCP
uqyrq4SBgirAsgCItbm5uOLkF3/QamPLgp6dnUd6ZlWEX9ThIyp8g0DI30eBbBxdfFWfcg5gjFWL
ZA6XsTmGfNTaHhC82arjxWHAfY21wuTmJs/f64auiD2dwc3f3R6BohCFskjIqb/jdQC41v///yH/
C1hNUCBEYXRhWE1QPD94cGFja2V0IGJlZ2luPSLvu78iIGlkPSJXNU0wTXBDZWhpSHpyZVN6TlRj
emtjOWQiPz4gPHg6eG1wbWV0YSB4bWxuczp4PSJhZG9iZTpuczptZXRhLyIgeDp4bXB0az0iQWRv
YmUgWE1QIENvcmUgNS4wLWMwNjAgNjEuMTM0Nzc3LCAyMDEwLzAyLzEyLTE3OjMyOjAwICAgICAg
ICAiPiA8cmRmOlJERiB4bWxuczpyZGY9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkvMDIvMjItcmRm
LXN5bnRheC1ucyMiPiA8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0iIiB4bWxuczp4bXBSaWdo
dHM9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9yaWdodHMvIiB4bWxuczp4bXBNTT0iaHR0
cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9i
ZS5jb20veGFwLzEuMC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtbG5zOnhtcD0iaHR0cDovL25zLmFk
b2JlLmNvbS94YXAvMS4wLyIgeG1wUmlnaHRzOk1hcmtlZD0iRmFsc2UiIHhtcE1NOk9yaWdpbmFs
RG9jdW1lbnRJRD0idXVpZDoyMDMyM0RBRjM4MzNERDExQjg0REIxNTNGRkNCMkIyNSIgeG1wTU06
RG9jdW1lbnRJRD0ieG1wLmRpZDpEQzY5RThFMEQ2NDkxMUUwQURFNUFDMDlEM0I2NjlBOCIgeG1w
TU06SW5zdGFuY2VJRD0ieG1wLmlpZDpEQzY5RThERkQ2NDkxMUUwQURFNUFDMDlEM0I2NjlBOCIg
eG1wOkNyZWF0b3JUb29sPSJBZG9iZSBQaG90b3Nob3AgQ1M1IE1hY2ludG9zaCI+IDx4bXBNTTpE
ZXJpdmVkRnJvbSBzdFJlZjppbnN0YW5jZUlEPSJ4bXAuaWlkOjA0ODAxMTc0MDcyMDY4MTE5N0E1
RDQ2NEQzRTk3REQ4IiBzdFJlZjpkb2N1bWVudElEPSJ1dWlkOjIwMzIzREFGMzgzM0REMTFCODRE
QjE1M0ZGQ0IyQjI1Ii8+IDwvcmRmOkRlc2NyaXB0aW9uPiA8L3JkZjpSREY+IDwveDp4bXBtZXRh
PiA8P3hwYWNrZXQgZW5kPSJyIj8+Af/+/fz7+vn49/b19PPy8fDv7u3s6+rp6Ofm5eTj4uHg397d
3Nva2djX1tXU09LR0M/OzczLysnIx8bFxMPCwcC/vr28u7q5uLe2tbSzsrGwr66trKuqqainpqWk
o6KhoJ+enZybmpmYl5aVlJOSkZCPjo2Mi4qJiIeGhYSDgoGAf359fHt6eXh3dnV0c3JxcG9ubWxr
amloZ2ZlZGNiYWBfXl1cW1pZWFdWVVRTUlFQT05NTEtKSUhHRkVEQ0JBQD8+PTw7Ojk4NzY1NDMy
MTAvLi0sKyopKCcmJSQjIiEgHx4dHBsaGRgXFhUUExIREA8ODQwLCgkIBwYFBAMCAQAAIfkEAAAA
AAAsAAAAAPQAPAAAB/+Af4KDhIWGh4iJiouMjY6PkJGSk5SVlpeYmZqbnJ2en6ChoqOkpaanqKmq
q6ytrq+wsbKztLW2t7i5uru8vb6/wMHCw8TFxsfIycrLzM3Oz9DR0qB2GCMWFiMYedkXEhgS4RcX
GODgEiPThgtPVcJPWaHs7pFDIx8xAVBQJGBSDvzMpPGjRYOfg1fEQNGQoIIYGggaqSjDhoSDM3MQ
KOhCgsyJClMaOPpw8CANLRVAtungRoqfDQWmRDBYwAofMyxkTMnx5pETAU4IEFggSIeAowLiIT3K
5Y+AMYOeOCn0NOrUn0v/cDlqVMAWLvH+fNExiIC7L0C3hl3qVZCAQQv/kjr980QHUbeDfjrZepeR
BSRmzLwpwCRCAgZiqAAwUMbACT85WJRkcSBEFDYAACA44OjLizcVJryAEcGBAg9SxOQQ2agPiwle
KpwwSDCBnwphJEt5sw+LHwNiPFxxiaVno6+DvkydK2gBAeaEjtKTSlXA9KtPEL0V9AWqVi70nlcR
cLfKc+h/zDLPMhTvEwFN8Ypd/idLfEUSKFyxsuFBgA2aRUYFGXDQEIBGc6RxwBpvlFGGGmr4cAUL
FRz0SA8AJADFCSGEoEACOF2xmiM8pOEDFVdsUNIZPtxWQAEHHQBFCBUwsUEYHmygoh8OONJeWfLh
tV10WWxHHZFGYqcd/1znEZAFVFU05UR2eSlFiBNWFtnXW1IR8IV8PwqyxSIQ+OHFBH6IQeBmAHRU
hhlSwIFABC8AkEYLQlgRBgiG+XYbmo8s8IMDD+QwoxonkCCGH1jU4AgaVjjAgo4HiXGCbWdacdAU
JeSARQ4d+CGFDEL4toGPhWAJ3RPPAeXEq9m9NcZURw4iK61XEfCqE2PaSoh4Uz23xZfnRQWVAE8k
u8V2Senwpa9SxUXUdsUygkIMKYHkBxUwwEEGAknsAYUCb5ygwAEgQMGGGR6EcVAUUNh20AQOQWJH
CQ4IMUUI+0BhwEGONuICT1IYwIcfDNCgLWwbdIFFBQy0gUUBZZypxv+MZ6SB6pXxdAXftMkm6w6z
WdQqX1LUOTFGyGEF+ceUY8TzXJOFPHHsrnu5xUVc9MxFHavMnVekAGQdckEcB2FBRUM0ZgahAkzY
JoUUVngQBBlXpGlFByGcEUVJBbRxRSQS+OGDgfu8AAaMATNCwT4+GFDAFQ500EELc2xwwj8nyCDF
DQ8YAAYC/f7XYyNhpufy4syNpxxVgjiu5CFD1heUmEC/TKUgqlbu5HpDcrkcF8sKkni1g1xgBKNU
TFFBhxUkkcYJEQDQRgA+vOGBFS5pEYEQUxcAwAsOTOFHAQ4U4EUIkkBQwQYUvRDBDQZckYEjSoSQ
wAPklrHGCSAwwUT/FxWWUKEfE8AABhgk7IOAA3544Ahy3C1XOeNDokVfkPprvuSv5xmPd8ZTnvNU
bkrQ2YIB6UIfoonpPlkoGiFQsAevTUEDaNJCCIQHgjbtQwEIIEMUKnADKuRgCl9jwQ0iUAYwwCB5
KJnRJCiQBAWUQQFqWAMAFECHRx1kA2ZgABi4FoUEeAELU6AXCEoShTCIoQsIcMPapAAGnwBFKHe5
n1OW0hTP7Q89unoZW6JTCAL06g86aJn+1OKyLYzJc29k4CAimJe0hLEQTfDCR9B0EA2c4AEVYIMC
aLCPCRjAAY85gBdmRCMqRCAEATADDGDwghZEQQNumAQKiEAGALgh/wJq0AIAnsUINBzkHw6gW4Um
MMIRJkBTB3meFArQBQd4QAwUg8Q83tEyT+zSEDWgwktgkxIN8AQzZJAUbJKQtQ68IQw32AfT1MAG
MrwhAm5I0APCIAVKjEAPAJgJG3g3Ax+KygH/ogICusCHFhwEClHQnheoUIE3TCEJUwiAAmAQggio
oxVVsKYM2qWjDSgAAGpo0xkcoKMwkIEJV7jCGRhzgARMYAJQuAEbKtABfYTAXEI43CRGMAeQsOEE
DhiAIygQBR+cAQBvaIFlYIDDAMArCm44ABW8kIAIhMYBXQCD9071z1VA4GEt+MgUbkCDNKxBDTmw
TABAwAcDSOEFEf8FwQta6AEzkCECGb0RTMPgABoEQQGWaEAIpvAGDaXgUVEowD604IAc+IEFZtjI
6+AJSz+UoXU5OAMZWqCAHBRVFUPogh/iyrsCMAQKEfBaaLyA0ABwwIIo3OFB4WmZ173AMlOYQgta
cAkKoLMEUHhrI9CgmH1ooAuPOV4aQIBCIjQgBRmAAARqoFsIZCAFty3nYVGxg8y8YJ+h7SkAorCv
CmgIAAHQAGWhkJIcDM8NAJBBGIqYACxswHg/ZMAlUHAEMUihAqxhhA0cQAY2PGADQgiCAyKVBgXo
KL2Z2ALO6PEFAlRFEO0YRBWykyxCjKkKu9pCX/6wgOVIBWdjOmP/f/9Ll8394YyocIAYGNDEDUgh
DCFAwAmwgIUlhEMCeSgHBiygYhXHYA8fZkNb/WCF89G4Api4QB0cMAH8KgINFQgAEzyVKT+EYQo+
SOX1NoGskBGFCzv7wxjOg0AAX8Uu0CJAstDSMgVmZ8DvSZaVvkOUKXMOy4wjRdk2paIJcOgGa5BC
AHbgiB8EYAJngIEYFOCFMNhYAVrIhAXAcAUgOAIPCJhbBxLwtRdJIQFUYIED5MCJ+43nStmpshxf
VSzRwWVIZqlW5d5y6bxk+nJpHkUD/MQpxfD5a4tFgiOIEAGwBkAGIpJBi8zkU02kwAcicMQdpMCA
uU0gBAdxQEWF/8kC4Wrifl8gJYOltLmUScU7nh4EeCyXni2RMdqEWAC1VZZqUeBBCwehggLS4IAR
ClMLWkBDnaHwMHp2qE60m60fNoGDJTNiBS7ZwGtSElQydAC8EKg0UqgNOU1b2ykjk6Op0+MON/rK
V5rGCwKtgx5TxAHWXiCDGdzguoPYRt6NUALX0A2bHKShX/bUwCZQgIFD0+AlBKECFc5AAgXEBIl4
qIEc5FADEcyAt3IYwAwgQIciOALa0ha3/6zsvyL5bH/gWYDHQvftqDPc6lokhR+SWAGNXCEKUfAN
FdDdB0eYwM9oT+JLThAFLaRhhKvgARs0AL8KdSEIEdgADSwjzP8KYOEGJyDrA25ghUmpe2yNsPQB
szOs5HypyrPKNoPfYnHTrYWMpeZcpqmUeVWgLwII0JsWQvuuKxjABo7owRvU8IICGCCIHMBM3lgQ
hFX0YEYvqEAUmOAANyQgATmILUFCS7X1PeYK26UBURmhRSiX+Tw8+wMBp75Fumj5CVxGT+ZGLQjr
S5nKmzuKKj4FgC5YwWsJKMAGmKCAqaGcES4gwZnOsL4DnMGeAEBd+6YKJmA+L5AAJ2BT/EIjZ8AA
B8EvxkNFF4FXUbQBIrUIGJYc/uUdkeNf6kEXPVMFB5ZgRLEAGegdGCZhGxgVIZiBpcAGJeAGCMAC
GUIF69MGLND/ePe3CBTwBmjiBUJwADkAAhxgQlAAANOHCjawH51iGCHgBRvQOlAAA0G2D8bjegXg
A3DgLWJgAA8wXKfgLn6GBRHwNQbgARUgBYq1gz8GBYq1WN3VBTpVGWRQB6tAAQXAAt5yfFCgBS5x
GwhAAppRBmdAQgcABg/QcxahAGgFhqUQBwUgBimhBnwUBRywI2yYCGjABsaDBWinWIoUBhiFA6tA
BGtQQ4sRAFOQAACAJlPQSYfEAMNBAgiQBi8FAEKQA0HAB45YCgC3LY8kTFhwAlaABShBAYfmBmRA
BVEAAgiAACAQBGdwA/vCA46AASqwCRQQATIgAy0gBUjIAGvw/4QaEAI54AYlwQAO4AAFI2MAkGdl
0IukMABhIIRQ0AHCNAVpkAMVYBCZiAhEMAUKQF0V0ElRcANt4Aa+4W+LgAFScAGasAMRQAIkEATw
VgCBsQH64AW3gW53tQFWcAUPAAVl0HgqIo+jUDb7EAFt8AJ1skQl8Y+HQAGioYoIAwI5EAZvcBAs
MASOIAFSwIuZsAP1pABW8AI8mSMnQAOGQU9uAJJZ4weY0QFT810oOQpxsJI0cgJk8CFv4DV4cA5i
iQ1k+Q1NUAEHIAVRwEcaEASxZQSPYAEFEAZHkAkuEAJsQF0LFVFzwAYHwAAt8EmYEQBJE2IPwJEl
QDtXKQo8AP8FbJUAbOApB9EFgjeNDphEnkhWBuBhY8dRwYEF8gIZZ3A8KuUIFhAGmuJslQBkg5cA
GjAFJ3AGF8MGUnACG2AEFEAERLADH0ABP2ADfUABPNADP4CMiwkKKFAhUqABfVgSjGJR0GcFB9AC
PqAFfCBwYRAGDBACQbA+QfSaBzEHL/APKPAIF2B7++F0loAGGqAAa5U0bHAG8fIGABAEDHmcRkVj
cuWcGpB2zkmDEUAD8yUqEjUFYgAGHuABQLWWonIGClCaP/lEG+ABBWAB64kF8ZIAXdAFbCADQdAP
VtCKwYafrXA0UvAAIXBRXlByzmlyX1MwBdMCACBM++EBYOD/AKAZP28AA+X5CEB5PAnqAQsWCSsQ
ogcQAGvwAkxgBW8AAiwgBTDAAglHoq1QBAZwQjIhgC26LU8oKhvgBm4QAGcwNWJgBbcHIxrQAqYh
AZGAAQhgBjBxEaRICUSgARFwEL8zXzbmAzJgaFTaCkowBVTQT825pSM0BV0gifFCA22gWInqDwXg
gFFQAnMKCRYQBJDWBTJQIff5CGigLowGU+mTAK4jfBHgY3+KCgvwAYNaSFsKbyP0RDd1Ax2wKKcU
USDpAD8wCRZQpmJKBomZBtkoCXgASgRpGa1YmGygmqmaCkPQAxcTAXxUEp5ITMSxBljgA13wh36w
rSVhAj4p/wkWIAUbIAM4NCNREAR2IAkUkFDyYkJswFyv4wYKQGnNygrXkgNzYAVPVBKCGhpacAPh
ZZvc6gdgIBkrEK6SgAEoBFYECQU5sAQ9eiFqgAAMChmMVoY50AZR0Db3qgoo4ALolqh6AgIV8jW0
NZkHoAVWMDclwR8QMLGSUDYTkJdtIAWvAQUtUJeQQAHEeAMhYIwdUndXIANR5bEfqwoZgDQ8eQIl
cKQMsAF2dRBtMAF7IgRUcHBBAKGUIAEFyQRUABM0AGkHEAWoqggUIEwdwAYRoAVREAFUUAAWOwFT
MKVJi69lsi0VQE/c455R8H/xCQNvsAY69wEySwkYEACwFKBRFVACMHEFVDCsjUABWBAbCYA7AOBH
ZOCRFaCed1uiDXBcCNAm/YAAcVYCG0FjRgAEh1sJGGAAIdmtaYBuyOMuDmChjUAEUVB4r4MAMoUm
BSAFaXC2n6sKIwABPBAGMFEAaSBnJWACM4C7m7AAXwAEAzAAIsBbumW9RTAAbNoIuaVbNTC+tyUC
KqB0ENAANVe8tOANGACR7Bu/8ju/lRAIADs=

--Apple-Mail-2--60163669--

--Apple-Mail-1--60163670--

From john@jck.com  Fri Jun  8 15:57:57 2012
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74DA711E80AA for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 15:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 HET3F-h3h-lj for <ietf@ietfa.amsl.com>; Fri,  8 Jun 2012 15:57:57 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 007C411E8091 for <ietf@ietf.org>; Fri,  8 Jun 2012 15:57:57 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1Sd81q-000AdI-P2; Fri, 08 Jun 2012 18:51:38 -0400
Date: Fri, 08 Jun 2012 18:57:27 -0400
From: John C Klensin <john@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "Bradner, Scott" <sob@harvard.edu>
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF:	A	Novice's Guide to the Internet Engineering Task Force)	to	Informational RFC
Message-ID: <EF3FA76E11F79DA4B45230B8@JcK-HP8200.jck.com>
In-Reply-To: <81AC4AD6-1EFC-405A-AD8F-B5AB03F2976D@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <91BA408B-60F6-4451-910A-7D5C33F48038@vpnc.org> <52CB44AB-006B-407F-AA44-976271B3E27E@harvard.edu> <03EE51C5-CDAB-471B-8DE2-DFB40CE1E93D@vpnc.org> <09A09092-51D1-4406-9387-5F988552BF8A@harvard.edu> <81AC4AD6-1EFC-405A-AD8F-B5AB03F2976D@vpnc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Mon, 11 Jun 2012 07:33:25 -0700
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 22:57:57 -0000

--On Friday, June 08, 2012 12:49 -0700 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

> I am supporting not putting anything about appeals to the ISOC
> Board in the Tao. They do not apply to novices.

Paul, that suggests something else which the Tao does sort of
say but maybe not clearly enough in context.  A novice really
shouldn't attempt to exercise any of our processes, especially
the more advanced/complex ones like appeals, without either a
lot of observation or seeking out advice and guidance.   It is
too easy to get tangled up in things or have an
almost-reasonable request or suggestion rejected because it is
badly presented.   Fortunately the community is ultimately
pretty friendly to newcomers/novices.  While that friendliness
may not express itself proactively, I've encountered very few
people who would not try to help get a novice pointed in the
right direction if asked for advice.  

IMO, the more clearly and broadly that can be said the better.

    john




From abdussalambaryun@gmail.com  Sat Jun  9 03:12:28 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABAC621F8A0B for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 03:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.528
X-Spam-Level: 
X-Spam-Status: No, score=-3.528 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, 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 wHo7rdmXTX2E for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 03:12:28 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E42AD21F8A07 for <ietf@ietf.org>; Sat,  9 Jun 2012 03:12:27 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1737929vbb.31 for <ietf@ietf.org>; Sat, 09 Jun 2012 03:12:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=40eRSDnaAmdgjBNKRL7tPrwS+ZCCsho7Za3OGQVuS9A=; b=mkqDJloWLZLhVC0qhQ0lIWOvrCMHag0blVXpPcFhCvqUO0lC+o2USxS+yunOrFy9K6 7GjKcbOHO2GWwG0JO+GbprGRhS6UflxX9uzQYWEWxT0HyAOJ4eFTdIUxQNWbHytpl89S 559DsY1dN73WWZyp6CrTObMTAQLBPxZ2RQutDUwyxzk+lAJnyCfcqU4E2DhXCDLg22MU 9xLBwSdo3ZEJZbVzFPP7+Z7Ooxu1xArRyJqeZTuH8dsdaJglT2I+FpmMdh0OIl8R3iSx LdE0i5IM6zAxLG+hl92T1K0RBoHfROq/aUgvfIv+C33BoMTJRkPi9bX49sSn0jiADsAd t/qA==
MIME-Version: 1.0
Received: by 10.52.90.196 with SMTP id by4mr7475797vdb.103.1339236747487; Sat, 09 Jun 2012 03:12:27 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Sat, 9 Jun 2012 03:12:27 -0700 (PDT)
Date: Sat, 9 Jun 2012 12:12:27 +0200
Message-ID: <CADnDZ8_PoshoJu61hm=qmhCAwViKBS_7gXf8M_zAfeE8Q=0ONw@mail.gmail.com>
Subject: Discussions in IETF WGs
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 11 Jun 2012 07:33:26 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 10:12:28 -0000

++++++++++++++++   Possible Duplication  +++++++++++++++

Hi Folks,

IMHO, there are difference between discussion that MAY become
argumentable and/or debatable. In a healthy-discussion you produce new
ideas and educate yourself and others, but in unproductive-discussion
you MAY block any progress and waste time.  I define productive
discussion as the posting/speaking of a point of view referenced by
scientific facts or RFCs. I define debates as the posting/speaking of
points without good-referencing or without good-reasoning. IMHO these
debating inputs with no good reference will not provide progress in
discussions, even though it may (in low probability) start indirectly
an interest/input to a work-in-progress.

For example, in one of the WG discussion on list, two members of WG
have referenced a history-discussion and informed me to read them
regarding some subject, I did do that but was *lost in translation*. I
now think that the memebrs' advise was to a wrong direction. We SHOULD
NOT refer in our current discussions to any other
history-subjected-discussions (thoes discussion had no approve by WG
consensus nor IESG review) in any WGs.  Also referring to old
discussions in the list result to waste time and MAY make current
arguments long (i.e. long means more than 5 working days), or even
makes the current argument unproductive.Old-discussions MAY be
misleading/incorrect/invalid, even if they are helpful to gain some
knowledge.

We should *reference* mostly RFCs in our discussion, because RFCs are
correct resource. The reason is because only RFCs are productions of
healthy discussions and reviewed by experts in IESG. IMHO the IETF
sees that RFCs are the correct-progress-reference. All Discussions are
important for the IETF processes and to produce RFCs. Memebers of the
WG should try to direct their discussions in the direction of progress
without discouraging debate-input. Discussions that produce I-D that
in the end submits <I-Ds are work-in-progress> are the most productive
discussions. IMO it is accepted in discussions to reference scientific
research papers, reviewed publications, industry experience, or RFCs,
but please don=92t accept in discussion the validity of ; a) a reference
to a specific historic discussion that possibly were with wrong
arguments, or b) a reference to unproductive discussions.

In conclusion, we should try with the help of the WGs chairs to direct
our discussions to become more productive, and within a reasonable
time, and if we see any good-correct ideas, we SHOULD react quickly
and input in a informational I-D and submit to WG for approval so we
don't repeat refering to wrong-argumental-discussion.

If you feel differently please advise, thanking you :)

Best regards

Abdussalam Baryun
University of Glamorgan, UK.

+++++++++++++++++++++++++++++++++++++++++++++++++++++
< In discussions one may be wrong, or may be right, but it does not
matter if we work together as a group to progress and resolve all
issues. IETF WGs are always right >
***************************************************************************=
*************

From abdussalambaryun@gmail.com  Sat Jun  9 13:34:59 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8916621F855A for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 13:34:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.529
X-Spam-Level: 
X-Spam-Status: No, score=-3.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, 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 W4dOEbLiztUJ for <ietf@ietfa.amsl.com>; Sat,  9 Jun 2012 13:34:59 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id CA05021F853F for <ietf@ietf.org>; Sat,  9 Jun 2012 13:34:58 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1907252vbb.31 for <ietf@ietf.org>; Sat, 09 Jun 2012 13:34:56 -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 :content-type:content-transfer-encoding; bh=40eRSDnaAmdgjBNKRL7tPrwS+ZCCsho7Za3OGQVuS9A=; b=stb6jr27OHVYVt9RbVyqK2llXAAeTbjVhJP4vlLoj9aJX19osDXYPkEDKwxbaal0Ie nezW6QKXaARcc/Ld6u4bDGxL5AHbVlzDYKFLrB13eqiapGl8PQ840CdreQg9NLwK8TG3 M82jjB9r9Zk2aZX/sbZ5e9oGB8yIj4zfyvXVYi1smzhNNbICWEnU4C6DnVwfLCZ5mMPI iWhwHuTXDfby7bm13eqWZicvBsZmbxPeIKN1wRSSnT9hWd6vCeKpjEY3TIAHuERgvGf4 9mlqm8fXyTisqbWB+BXRemiHgIQbX/0NmXLg68tAdxWDOs1XuaUUf/uIXfMbwSmVcsdq fVhw==
MIME-Version: 1.0
Received: by 10.52.100.4 with SMTP id eu4mr8119273vdb.66.1339274096788; Sat, 09 Jun 2012 13:34:56 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Sat, 9 Jun 2012 13:34:56 -0700 (PDT)
In-Reply-To: <CADnDZ8_PoshoJu61hm=qmhCAwViKBS_7gXf8M_zAfeE8Q=0ONw@mail.gmail.com>
References: <CADnDZ8_PoshoJu61hm=qmhCAwViKBS_7gXf8M_zAfeE8Q=0ONw@mail.gmail.com>
Date: Sat, 9 Jun 2012 22:34:56 +0200
Message-ID: <CADnDZ8_V9vHc9yWPEwbk=Fa5dQ60s4Vkm0yiknUQWKkDoWspbQ@mail.gmail.com>
Subject: Re: Discussions in IETF WGs
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 11 Jun 2012 07:33:26 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 20:34:59 -0000

++++++++++++++++   Possible Duplication  +++++++++++++++

Hi Folks,

IMHO, there are difference between discussion that MAY become
argumentable and/or debatable. In a healthy-discussion you produce new
ideas and educate yourself and others, but in unproductive-discussion
you MAY block any progress and waste time.  I define productive
discussion as the posting/speaking of a point of view referenced by
scientific facts or RFCs. I define debates as the posting/speaking of
points without good-referencing or without good-reasoning. IMHO these
debating inputs with no good reference will not provide progress in
discussions, even though it may (in low probability) start indirectly
an interest/input to a work-in-progress.

For example, in one of the WG discussion on list, two members of WG
have referenced a history-discussion and informed me to read them
regarding some subject, I did do that but was *lost in translation*. I
now think that the memebrs' advise was to a wrong direction. We SHOULD
NOT refer in our current discussions to any other
history-subjected-discussions (thoes discussion had no approve by WG
consensus nor IESG review) in any WGs.  Also referring to old
discussions in the list result to waste time and MAY make current
arguments long (i.e. long means more than 5 working days), or even
makes the current argument unproductive.Old-discussions MAY be
misleading/incorrect/invalid, even if they are helpful to gain some
knowledge.

We should *reference* mostly RFCs in our discussion, because RFCs are
correct resource. The reason is because only RFCs are productions of
healthy discussions and reviewed by experts in IESG. IMHO the IETF
sees that RFCs are the correct-progress-reference. All Discussions are
important for the IETF processes and to produce RFCs. Memebers of the
WG should try to direct their discussions in the direction of progress
without discouraging debate-input. Discussions that produce I-D that
in the end submits <I-Ds are work-in-progress> are the most productive
discussions. IMO it is accepted in discussions to reference scientific
research papers, reviewed publications, industry experience, or RFCs,
but please don=92t accept in discussion the validity of ; a) a reference
to a specific historic discussion that possibly were with wrong
arguments, or b) a reference to unproductive discussions.

In conclusion, we should try with the help of the WGs chairs to direct
our discussions to become more productive, and within a reasonable
time, and if we see any good-correct ideas, we SHOULD react quickly
and input in a informational I-D and submit to WG for approval so we
don't repeat refering to wrong-argumental-discussion.

If you feel differently please advise, thanking you :)

Best regards

Abdussalam Baryun
University of Glamorgan, UK.

+++++++++++++++++++++++++++++++++++++++++++++++++++++
< In discussions one may be wrong, or may be right, but it does not
matter if we work together as a group to progress and resolve all
issues. IETF WGs are always right >
***************************************************************************=
*************

From housley@vigilsec.com  Mon Jun 11 08:43:23 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABC2921F8620 for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 08:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 uohJPR6uFlJx for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 08:43:22 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 0C96221F860E for <ietf@ietf.org>; Mon, 11 Jun 2012 08:43:22 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id C6B60F24014; Mon, 11 Jun 2012 11:43:33 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id g21TvgMpVgFJ; Mon, 11 Jun 2012 11:43:08 -0400 (EDT)
Received: from [192.168.2.110] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id EB487F2402B; Mon, 11 Jun 2012 11:43:32 -0400 (EDT)
Subject: Re: I-D Action: draft-hoffman-tao-as-web-page-00.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4FD595EB.7020401@gmail.com>
Date: Mon, 11 Jun 2012 11:43:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <981B0927-EC49-4AB0-985D-C80951487D89@vigilsec.com>
References: <20120609221936.12063.68465.idtracker@ietfa.amsl.com> <4FD47CF1.4080107@gmail.com> <4FD4C49F.8080508@gmail.com> <3E95A8C1-08F1-4519-95AF-1E99FA205B28@vpnc.org> <4FD595EB.7020401@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>, Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 15:43:23 -0000

Paul and Brian:

>>> Oh, one thing I now realise is that the draft doesn't state that
>>> the editor (in deciding what changes to adopt) and the IESG
>>> (in approving an update) will of course do so by a normal IETF
>>> consensus process (presumably ad hoc last calls) and subject
>>> to appeal like anything else. This is so obvious in the IETF
>>> context that I didn't even notice that it wasn't stated.
>>=20
>> It is not what was intended.
>>=20
>> - There was no mention to me of "ad hoc last calls", so I did not =
include them in the draft.=20
>=20
> Well, that was presumably an oversight. The IETF always works by
> a consensus process, afaik.

The IESG thinking on this is in line with Brian's thinking.  In the =
past, the Tao has been published as an informational RFC.  The approval =
process included community comment and IESG evaluation.  A parallel =
approval process ought to be used here.

Let's use of a well-known URL for the current approved Tao and a =
well-known URL for the draft of the Tao that is under consideration.  =
This will facilitate review of updates.

>> - Is there an appeals process for the content of the various web =
pages created by the IESG?
>=20
> Yes. For many years there has been a presumption that the appeals
> process in section 6.5 of RFC 2026 can be applied to *any* IESG =
action.
> That being so, I suppose it isn't vital to write it down in every
> document, but it makes things clearer.

Indeed.  Any decision by the IESG is subject to the existing appeals =
process.

Russ


From tony@att.com  Mon Jun 11 09:05:19 2012
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB33921F8648 for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 09:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 55NzAc8fQnLq for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 09:05:19 -0700 (PDT)
Received: from nbfkord-smmo03.seg.att.com (nbfkord-smmo03.seg.att.com [209.65.160.84]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE5B21F863C for <ietf@ietf.org>; Mon, 11 Jun 2012 09:05:19 -0700 (PDT)
Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo03.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id e3716df4.0.223945.00-418.599822.nbfkord-smmo03.seg.att.com (envelope-from <tony@att.com>);  Mon, 11 Jun 2012 16:05:19 +0000 (UTC)
X-MXL-Hash: 4fd6173f0618e833-c3b6ed9c4fa71412bb04d433c1948879132e944b
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q5BG5HQ2015293 for <ietf@ietf.org>; Mon, 11 Jun 2012 09:05:17 -0700
Received: from fflint03.pst.cso.att.com (fflint03.pst.cso.att.com [150.234.39.63]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q5BG59ft015212 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 11 Jun 2012 09:05:13 -0700
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by fflint03.pst.cso.att.com (RSA Interceptor) for <ietf@ietf.org>; Mon, 11 Jun 2012 09:04:43 -0700
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q5BG4g14019903 for <ietf@ietf.org>; Mon, 11 Jun 2012 12:04:42 -0400
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q5BG4ZhM019721 for <ietf@ietf.org>; Mon, 11 Jun 2012 12:04:37 -0400
Received: from [135.91.35.200] (dn135-91-35-200.dhcpn.ugn.att.com[135.91.35.200]) by maillennium.att.com (mailgw1) with ESMTP id <20120611160045gw10060l91e> (Authid: tony); Mon, 11 Jun 2012 16:00:45 +0000
X-Originating-IP: [135.91.35.200]
Message-ID: <4FD61713.9060804@att.com>
Date: Mon, 11 Jun 2012 12:04:35 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: I-D Action: draft-hoffman-tao-as-web-page-00.txt
References: <20120609221936.12063.68465.idtracker@ietfa.amsl.com> <4FD47CF1.4080107@gmail.com> <4FD4C49F.8080508@gmail.com> <3E95A8C1-08F1-4519-95AF-1E99FA205B28@vpnc.org> <4FD595EB.7020401@gmail.com> <981B0927-EC49-4AB0-985D-C80951487D89@vigilsec.com>
In-Reply-To: <981B0927-EC49-4AB0-985D-C80951487D89@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.128.153]
X-AnalysisOut: [v=1.0 c=1 a=QWrpuJ_xb_AA:10 a=4JAii899aesA:10 a=amGdIZ_B7J]
X-AnalysisOut: [AA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:1]
X-AnalysisOut: [0 a=xwOvzTHDVLE4u4nGvK72ag==:17 a=9GY94KUMPlJXnqtxdHUA:9 a]
X-AnalysisOut: [=wPNLvfGTeEIA:10]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 16:05:20 -0000

I'm wondering if there needs to be a distinction between "minor updates" 
and "major updates". Minor updates would be the typo variety or a URL 
change and wouldn't require much review at all. Major updates would 
require non-trivial review.

     Tony Hansen

On 6/11/2012 11:43 AM, Russ Housley wrote:
> Paul and Brian:
>
>>>> Oh, one thing I now realise is that the draft doesn't state that
>>>> the editor (in deciding what changes to adopt) and the IESG
>>>> (in approving an update) will of course do so by a normal IETF
>>>> consensus process (presumably ad hoc last calls) and subject
>>>> to appeal like anything else. This is so obvious in the IETF
>>>> context that I didn't even notice that it wasn't stated.
>>> It is not what was intended.
>>>
>>> - There was no mention to me of "ad hoc last calls", so I did not include them in the draft.
>> Well, that was presumably an oversight. The IETF always works by
>> a consensus process, afaik.
> The IESG thinking on this is in line with Brian's thinking.  In the past, the Tao has been published as an informational RFC.  The approval process included community comment and IESG evaluation.  A parallel approval process ought to be used here.
>
> Let's use of a well-known URL for the current approved Tao and a well-known URL for the draft of the Tao that is under consideration.  This will facilitate review of updates.
>
>>> - Is there an appeals process for the content of the various web pages created by the IESG?
>> Yes. For many years there has been a presumption that the appeals
>> process in section 6.5 of RFC 2026 can be applied to *any* IESG action.
>> That being so, I suppose it isn't vital to write it down in every
>> document, but it makes things clearer.
> Indeed.  Any decision by the IESG is subject to the existing appeals process.
>
> Russ
>

From adrian@olddog.co.uk  Mon Jun 11 09:11:01 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A30721F859A for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 09:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.484
X-Spam-Level: 
X-Spam-Status: No, score=-1.484 tagged_above=-999 required=5 tests=[AWL=1.115,  BAYES_00=-2.599]
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 tSmRXWdoNY75 for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 09:10:55 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 462C821F854C for <ietf@ietf.org>; Mon, 11 Jun 2012 09:10:55 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id q5BGAo1w019255;  Mon, 11 Jun 2012 17:10:51 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id q5BGAnjd019241 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 11 Jun 2012 17:10:50 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Tony Hansen'" <tony@att.com>, "'IETF'" <ietf@ietf.org>
References: <20120609221936.12063.68465.idtracker@ietfa.amsl.com>	<4FD47CF1.4080107@gmail.com> <4FD4C49F.8080508@gmail.com>	<3E95A8C1-08F1-4519-95AF-1E99FA205B28@vpnc.org>	<4FD595EB.7020401@gmail.com>	<981B0927-EC49-4AB0-985D-C80951487D89@vigilsec.com> <4FD61713.9060804@att.com>
In-Reply-To: <4FD61713.9060804@att.com>
Subject: RE: I-D Action: draft-hoffman-tao-as-web-page-00.txt
Date: Mon, 11 Jun 2012 17:10:48 +0100
Message-ID: <02ce01cd47ec$c4403a90$4cc0afb0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJeRmh79RQ8dEhgFQ6HkrGHIFFyzAEXYR1wAZGF/sQBFN89MQFJ0jsmAq4yBH4C8ID9QJV+GfQg
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 16:11:01 -0000

Tony,

Is there a need to draw a line (over which we will, no doubt, manage to fight in
the future)?

Can we not just say that updates will be batched and approved "in a timely
fashion", and know that updates will receive as much review and discussion as
the community thinks they merit?

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Tony
> Hansen
> Sent: 11 June 2012 17:05
> To: IETF
> Subject: Re: I-D Action: draft-hoffman-tao-as-web-page-00.txt
> 
> I'm wondering if there needs to be a distinction between "minor updates"
> and "major updates". Minor updates would be the typo variety or a URL
> change and wouldn't require much review at all. Major updates would
> require non-trivial review.
> 
>      Tony Hansen
> 
> On 6/11/2012 11:43 AM, Russ Housley wrote:
> > Paul and Brian:
> >
> >>>> Oh, one thing I now realise is that the draft doesn't state that
> >>>> the editor (in deciding what changes to adopt) and the IESG
> >>>> (in approving an update) will of course do so by a normal IETF
> >>>> consensus process (presumably ad hoc last calls) and subject
> >>>> to appeal like anything else. This is so obvious in the IETF
> >>>> context that I didn't even notice that it wasn't stated.
> >>> It is not what was intended.
> >>>
> >>> - There was no mention to me of "ad hoc last calls", so I did not include
them
> in the draft.
> >> Well, that was presumably an oversight. The IETF always works by
> >> a consensus process, afaik.
> > The IESG thinking on this is in line with Brian's thinking.  In the past,
the Tao has
> been published as an informational RFC.  The approval process included
> community comment and IESG evaluation.  A parallel approval process ought to
> be used here.
> >
> > Let's use of a well-known URL for the current approved Tao and a well-known
> URL for the draft of the Tao that is under consideration.  This will
facilitate review
> of updates.
> >
> >>> - Is there an appeals process for the content of the various web pages
> created by the IESG?
> >> Yes. For many years there has been a presumption that the appeals
> >> process in section 6.5 of RFC 2026 can be applied to *any* IESG action.
> >> That being so, I suppose it isn't vital to write it down in every
> >> document, but it makes things clearer.
> > Indeed.  Any decision by the IESG is subject to the existing appeals
process.
> >
> > Russ
> >


From sm@resistor.net  Mon Jun 11 10:04:44 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BADAC21F8582 for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 10:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.351
X-Spam-Level: 
X-Spam-Status: No, score=-102.351 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8g1ZNjtfRR90 for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 10:04:44 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 169FA21F84D8 for <ietf@ietf.org>; Mon, 11 Jun 2012 10:04:43 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5BH4ZJ3001910; Mon, 11 Jun 2012 10:04:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1339434280; i=@resistor.net; bh=g1xKYQMMIMJx9Nb3zafUKatmmH9zQpL+xkAb+9tEtwo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cEV11Qjq6l1xb3wcZHbyNwpsmefyIwqIbhYQ87G+UUICPz+CDhPqisFPK+RBfL4F3 Z7bMIFFEQavnmWK/GRJyrWKweNrZEUVer6L4EsEDHpszL2B5DrD9Oxe1DIUVSmr6tN Pa2D/PgWmffTuEzpUkBmS5OvurlCOi+IPiQIqnc0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1339434280; i=@resistor.net; bh=g1xKYQMMIMJx9Nb3zafUKatmmH9zQpL+xkAb+9tEtwo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OAEonGBJAzGy6tTgLIkJfSZyKyhmOCKYy/GvuxalwE2hkIMYrpw/rQj9AQU4c5n0N 6uD6gP4PkeNoC/lVotGdTIk4/mP3+LEKm2xpmtLkeUh85RI3+2yebYiH3eesNZC9XK Gqr4xzRxyWeSPxKidiXl1DnERhbSeYhNI73l7qKE=
Message-Id: <6.2.5.6.2.20120611093423.08d238b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 11 Jun 2012 09:54:27 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Discussions in IETF WGs
In-Reply-To: <CADnDZ8_PoshoJu61hm=qmhCAwViKBS_7gXf8M_zAfeE8Q=0ONw@mail.g mail.com>
References: <CADnDZ8_PoshoJu61hm=qmhCAwViKBS_7gXf8M_zAfeE8Q=0ONw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 17:04:44 -0000

Hi Abdussalam,
At 03:12 09-06-2012, Abdussalam Baryun wrote:
>For example, in one of the WG discussion on list, two members of WG
>have referenced a history-discussion and informed me to read them
>regarding some subject, I did do that but was *lost in translation*. I
>now think that the memebrs' advise was to a wrong direction. We SHOULD
>NOT refer in our current discussions to any other
>history-subjected-discussions (thoes discussion had no approve by WG
>consensus nor IESG review) in any WGs.  Also referring to old
>discussions in the list result to waste time and MAY make current
>arguments long (i.e. long means more than 5 working days), or even
>makes the current argument unproductive.Old-discussions MAY be
>misleading/incorrect/invalid, even if they are helpful to gain some
>knowledge.

If someone is not aware of the old discussions about an issue it can 
be a problem.  The issue may have to be discussed again when there 
isn't any new input available.

Is the above related to discussions in the MANET WG?

Regards,
-sm 


From dworley@avaya.com  Mon Jun 11 11:36:04 2012
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8665021F8570; Mon, 11 Jun 2012 11:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
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 1-UBkwKKWPxr; Mon, 11 Jun 2012 11:36:04 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id F03FC21F856F; Mon, 11 Jun 2012 11:36:03 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAFI51k/GmAcF/2dsb2JhbABFtRiBB4IYAQEBAQIBEig/BQsCAQgNCAIfEDIdCAEBBAENDQEZh2QFC5tXnGeQLWADmxOKBoJ8
X-IronPort-AV: E=Sophos;i="4.77,390,1336363200"; d="scan'208";a="13285767"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 11 Jun 2012 14:33:49 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 11 Jun 2012 14:34:27 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Mon, 11 Jun 2012 14:36:00 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Dan Pitt <dan.pitt@opennetworking.org>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Date: Mon, 11 Jun 2012 14:33:24 -0400
Subject: RE: Liaison letter from ONF to IETF
Thread-Topic: Liaison letter from ONF to IETF
Thread-Index: Ac1H31CGK2fg/5xESMWhMpkTiN/pIwAIV81Q
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0B71@DC-US1MBEX4.global.avaya.com>
References: <316729C3-4C8C-4F75-813B-A4CFB2275480@opennetworking.org>
In-Reply-To: <316729C3-4C8C-4F75-813B-A4CFB2275480@opennetworking.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "iab@iab.org" <iab@iab.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 18:36:04 -0000

> To: IETF
> From: Dan Pitt, executive director, ONF
> Subject: Liaison between ONF and IETF
>=20
> [...] Finally, ONF is interested in discussing cross-publishing future
> specifications at the IETF, and would welcome a discussion on how best
> to accomplish this as well.

Who will ONF be sending to the next IETF meeting in Vancouver?
(http://www.ietf.org/meeting/84/index.html) That is where you will
have productive discussions about coordinating activities.

Dale

From mrex@sap.com  Mon Jun 11 13:09:12 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9D1921F8567 for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 13:09:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 U1YTwmv7qwHp for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 13:09:12 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id F41E721F8550 for <ietf@ietf.org>; Mon, 11 Jun 2012 13:09:11 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q5BK93Rj018729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 11 Jun 2012 22:09:08 +0200 (MEST)
Subject: Re: Discussions in IETF WGs
In-Reply-To: <CADnDZ8_PoshoJu61hm=qmhCAwViKBS_7gXf8M_zAfeE8Q=0ONw@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Mon, 11 Jun 2012 22:09:03 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20120611200903.460881A0A5@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 20:09:13 -0000

Abdussalam Baryun wrote:
> 
> For example, in one of the WG discussion on list, two members of WG
> have referenced a history-discussion and informed me to read them
> regarding some subject, I did do that but was *lost in translation*. I
> now think that the memebrs' advise was to a wrong direction. We SHOULD
> NOT refer in our current discussions to any other
> history-subjected-discussions (thoes discussion had no approve by WG
> consensus nor IESG review) in any WGs.  Also referring to old
> discussions in the list result to waste time and MAY make current
> arguments long (i.e. long means more than 5 working days), or even
> makes the current argument unproductive. Old-discussions MAY be
> misleading/incorrect/invalid, even if they are helpful to gain some
> knowledge.

There is no substiantial difference between old discussions and recent
discussions.  Referencing an argument from an earlier discussion rather
than repeating it is often an improvement with a significant potential to
actually save time, and zero risk to waste time (compared to repeating
the exact same previous arguments in a new message).


> 
> We should *reference* mostly RFCs in our discussion, because RFCs are
> correct resource.

If RFCs were correct, we would neither need an Errata process, nor
maturity levels, nor -bis documents.

"RFCs are correct" is a bold and dangerous presumption.  Many RFCs
are vague or even ambigous, and they may contain numerous implications
that are non-obvious to a number of readers, and sometimes non-obvious
to implementors and document authors).

All that can be said about standard track RFCs, is that they're the result
of the IETF consensus process.  And the primary focus of the IETF consensus
process is to resolve dissent (technical or procedural objections),
_not_ correctness.  Some level of confidence about correctness can be obtained
by creating independent implementations and demonstrate that they interop
on the implemented features, but results are mixed, and most interop
tests are lacking (test only a fraction of the features and only a fraction
of the implementations in the installed base, and rarely "border cases"
of unusual encodings).


-Martin

From stpeter@stpeter.im  Mon Jun 11 13:31:25 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EFAA21F8629 for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 13:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lUg-dzjCBvBz for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 13:31:24 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 228F721F85CD for <ietf@ietf.org>; Mon, 11 Jun 2012 13:31:24 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9F3B640081; Mon, 11 Jun 2012 14:48:29 -0600 (MDT)
Message-ID: <4FD65599.8020807@stpeter.im>
Date: Mon, 11 Jun 2012 14:31:21 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Last Call: RFC 2818 (HTTP Over TLS) to Proposed Standard
References: <20120601164205.25357.54620.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120601123737.0acca170@resistor.net> <A33D3784-6B07-46FA-9600-50CADF6EE4DF@isode.com>
In-Reply-To: <A33D3784-6B07-46FA-9600-50CADF6EE4DF@isode.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, Mark Nottingham <mnot@mnot.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 20:31:25 -0000

On 6/10/12 11:39 AM, Alexey Melnikov wrote:
> Adding to what SM already wrote (and yes, I've reread the whole
> document):
> 
> On 1 Jun 2012, at 21:23, SM <sm@resistor.net> wrote:
> 
>> At 09:42 01-06-2012, IESG Secretary wrote:
>>> The IESG has received a request from the TLS Working Group to
>>> reclassify RFC 2818 (HTTP Over TLS) to Proposed Standard.
>>> 
>>> The IESG plans to make a decision in the next few weeks, and
>>> solicits final comments on this action. Please send substantive
>>> comments to the ietf at ietf.org mailing lists by
>> 
>> Could the IESG please use ietf@ietf.org instead of obfuscating the
>> email address?  Some of us are lazy especially on Fridays.
>> 
>> Erratum #1077 has been classified as "Held for Document Update".
>> Will there ever be a document update?  Implementing this
>> specification requires HTTP/1.1 and TLS 1.0.  I suggest updating
>> the reference to RFC 4346 at least and waiting for the updated HTTP
>> specifications.
>> 
> 
> Yes, it would be worth doing that if the document is reopened.
> 
>> St. Andre and Mr. Hodges authored a Proposed Standard called
>> "Representation and Verification of Domain-Based Application
>> Service Identity within Internet Public Key Infrastructure Using
>> X.509 (PKIX) Certificates in the Context of Transport Layer
>> Security (TLS)".  Quoting from Section 1.4:
>> 
>> "the procedures described here can be referenced by future 
>> specifications, including updates to specifications for existing
>> application protocols if the relevant technology communities agree
>> to do so."
>> 
>> May I suggest taking the above into consideration and at least put
>> some minimal effort into a 2818bis?
>> 
> 
> Not surprisingly I agree with you.
> 
> Also note that HTTPBis WG has folded the updated definition of
> https:// URI schemes (Section 2.4 of RFC 2818) into one of its
> documents. I think it would be good to make it clear to readers which
> document defines the URI scheme.

RFC 2818 is extremely minimal in its description of the 'https' URI
scheme. At least draft-ietf-httpbis-p1-messaging is a bit more complete.
However, the IANA Considerations of the latter document need to be
modified so that they instruct the IANA to change the data in the URI
schemes registry.

> As far as reopening the document is concerned: I slightly prefer to
> do rfc2818bis although I understand that doing a -bis always takes
> longer than originally anticipated.

Agreed.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/





From julian.reschke@gmx.de  Mon Jun 11 14:42:35 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3791B21F847E for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 14:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 BvG225Qjd+jT for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 14:42:34 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 99C7721F8471 for <ietf@ietf.org>; Mon, 11 Jun 2012 14:42:33 -0700 (PDT)
Received: (qmail invoked by alias); 11 Jun 2012 21:42:31 -0000
Received: from p54BB3983.dip.t-dialin.net (EHLO [192.168.178.36]) [84.187.57.131] by mail.gmx.net (mp071) with SMTP; 11 Jun 2012 23:42:31 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19hAd01Epxh/Rjhn0k50ElhuPVTEeu18+rG3IfAVb Ka510wox7O5yA8
Message-ID: <4FD66644.1060201@gmx.de>
Date: Mon, 11 Jun 2012 23:42:28 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120604 Thunderbird/13.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Last Call: RFC 2818 (HTTP Over TLS) to Proposed Standard
References: <20120601164205.25357.54620.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120601123737.0acca170@resistor.net> <A33D3784-6B07-46FA-9600-50CADF6EE4DF@isode.com> <4FD65599.8020807@stpeter.im>
In-Reply-To: <4FD65599.8020807@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Mark Nottingham <mnot@mnot.net>, "ietf@ietf.org" <ietf@ietf.org>, SM <sm@resistor.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 21:42:35 -0000

On 2012-06-11 22:31, Peter Saint-Andre wrote:
> ...
> RFC 2818 is extremely minimal in its description of the 'https' URI
> scheme. At least draft-ietf-httpbis-p1-messaging is a bit more complete.
> However, the IANA Considerations of the latter document need to be
> modified so that they instruct the IANA to change the data in the URI
> schemes registry.
> ...

Not so: 
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-19.html#rfc.section.7.2>

Best regards, Julian

From stpeter@stpeter.im  Mon Jun 11 14:43:26 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E53CE11E8087 for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 14:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ITubR1zkxdbi for <ietf@ietfa.amsl.com>; Mon, 11 Jun 2012 14:43:26 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 88D5811E8083 for <ietf@ietf.org>; Mon, 11 Jun 2012 14:43:26 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C92AF40081; Mon, 11 Jun 2012 16:00:32 -0600 (MDT)
Message-ID: <4FD6667D.5050901@stpeter.im>
Date: Mon, 11 Jun 2012 15:43:25 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call: RFC 2818 (HTTP Over TLS) to Proposed Standard
References: <20120601164205.25357.54620.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120601123737.0acca170@resistor.net> <A33D3784-6B07-46FA-9600-50CADF6EE4DF@isode.com> <4FD65599.8020807@stpeter.im> <4FD66644.1060201@gmx.de>
In-Reply-To: <4FD66644.1060201@gmx.de>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Mark Nottingham <mnot@mnot.net>, "ietf@ietf.org" <ietf@ietf.org>, SM <sm@resistor.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 21:43:27 -0000

On 6/11/12 3:42 PM, Julian Reschke wrote:
> On 2012-06-11 22:31, Peter Saint-Andre wrote:
>> ...
>> RFC 2818 is extremely minimal in its description of the 'https' URI
>> scheme. At least draft-ietf-httpbis-p1-messaging is a bit more complete.
>> However, the IANA Considerations of the latter document need to be
>> modified so that they instruct the IANA to change the data in the URI
>> schemes registry.
>> ...
> 
> Not so:
> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-19.html#rfc.section.7.2>

Right you are!



From shimshamshimmy@gmail.com  Tue Jun 12 01:04:59 2012
Return-Path: <shimshamshimmy@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85AD621F8617 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 01:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.377
X-Spam-Level: 
X-Spam-Status: No, score=-0.377 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, 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 oDRWQyOeLuGj for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 01:04:59 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id C84D421F8616 for <ietf@ietf.org>; Tue, 12 Jun 2012 01:04:58 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so3733578ggn.31 for <ietf@ietf.org>; Tue, 12 Jun 2012 01:04:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=wa04opbXog1q/qEiiHmNgoqF8v13ayaIckmmyfTdYS8=; b=SB9Tp6stm9Up6fZQD1GMv8hc5yqqBg4kcl6fUwdaCDGGD0ZZKrr19+5dr3zyFdPS8J ppFaOy1f3n9dRQxx/MGNeaogMExGZPQJyuCSakMX9Inz5naW21AbvUXJ91Iwm6bVkgYw STQ03C0l6X6IfUMq+97qd6Te8CVJ8wA2Rm+qMxNPpcbI0Fz4lgbHUAzFI8k+bf30ul95 oZsb/yEddcyzVaPITLnyieawVyDSiemj/8q3d4CpMIshCJA/7N3YfDJ2HcVlEDVc+EmD 6pKtPiQk2WPTa1B1DHznGb+bxCb49L95NRCjBKiWb4TEP69Hd2FIS2OAjT5wuJbldxT2 +2hg==
Received: by 10.236.78.105 with SMTP id f69mr25290909yhe.15.1339488298369; Tue, 12 Jun 2012 01:04:58 -0700 (PDT)
MIME-Version: 1.0
Sender: shimshamshimmy@gmail.com
Received: by 10.236.114.170 with HTTP; Tue, 12 Jun 2012 01:04:38 -0700 (PDT)
From: Jun Murai <jun@wide.ad.jp>
Date: Tue, 12 Jun 2012 17:04:38 +0900
X-Google-Sender-Auth: 3upNbUP9gw02fYXgoZ7WbjV66Qw
Message-ID: <CA+k18nWeCCjaPDkfbYQ2k6kAyshu+VQnC9VEeEKTUU+jKmJ-kA@mail.gmail.com>
Subject: Reminder of CFC FOR ITOJUN SERVICE AWARD
To: "ietf@ietf. org" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 08:04:59 -0000

Dear IETFers,
Here is a reminder of CFC on  Itojun Service Award.
We have less than a month for this call.

Thanks,
Jun Murai

==
ANNOUNCING: CALL FOR CANDIDATES FOR ITOJUN SERVICE AWARD

The Itojun Service Award is presented every year to an individual or a
group who has made outstanding contributions in service to the IPv6
community.   The deadline for nominations for this year's award is 13
July 2012.  The award will be presented at the 85th meeting of the
IETF to be held in November 2012 in Atlanta, USA.

About the Award

The Itojun Service Award was established by the friends of Itojun and
administered by the Internet Society (ISOC), recognises and
commemorates the extraordinary dedication exercised by Itojun over the
course of IPv6 development.  The award includes a presentation
crystal, a US$3,000 honorarium, and a travel grant.

The award is focused on pragmatic technical contributions, especially
through development or operation, with the spirit of servicing the
Internet.  With respect to the spirit, the selection committee seeks
contributors to the Internet as a whole; open source developers are a
common example of such contributors, although this is not a
requirement for expected nominees.  While the committee primarily
consider practical contributions such as software development or
network operation, higher level efforts that help those direct
contributions will also be appreciated in this regard.  The
contribution should be substantial, but could be immature or ongoing;
this award aims to encourage the contributor to keep their efforts,
rather than just recognizing well established work.  Finally,
contributions of a group of individuals will be accepted as deployment
work is often done by a large project, not just a single outstanding
individual.

The award is named after Dr. Jun-ichiro "Itojun" Hagino, who passed
away in 2007, aged just 37.  Itojun worked as a Senior Researcher at
Internet Initiative Japan Inc. (IIJ), was a member of the board of the
Widely Integrated Distributed Environment (WIDE) project, and from
1998 to 2006 served on the groundbreaking KAME project in Japan as the

From duerst@it.aoyama.ac.jp  Tue Jun 12 02:13:46 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B0B21F853C for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 02:13:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.468
X-Spam-Level: 
X-Spam-Status: No, score=-99.468 tagged_above=-999 required=5 tests=[AWL=-0.092, BAYES_40=-0.185, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 bwMznvEyUpeA for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 02:13:45 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id EF77C21F85DF for <ietf@ietf.org>; Tue, 12 Jun 2012 02:13:44 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5C9DXMx004973 for <ietf@ietf.org>; Tue, 12 Jun 2012 18:13:34 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 7682_ec23_e287e040_b46e_11e1_96d0_001d096c5782; Tue, 12 Jun 2012 18:13:33 +0900
Received: from [IPv6:::1] ([133.2.210.1]:38052) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D1671> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 12 Jun 2012 18:13:37 +0900
Message-ID: <4FD7083A.6080502@it.aoyama.ac.jp>
Date: Tue, 12 Jun 2012 18:13:30 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: APPSDIR review of draft-farrell-decade-ni-07, major design issue (one or two URI schemes)
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie>
In-Reply-To: <4FCDE96E.5000109@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Graham Klyne <GK@ninebynine.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 09:13:46 -0000

Hello Stephen,

This mail responds to your points on the main technical issue that I 
have identified.

On 2012/06/05 20:11, Stephen Farrell wrote:

> On 06/05/2012 10:42 AM, "Martin J. DÃ¼rst" wrote:
>> Hello everybody,
>>
>> [For replies, please trim the cc list, thanks!]

Done, removed apps-discuss@ietf.org for the moment.


>> Major design issue:
>>
>> The draft defines two schemes, which differ only slightly, and mostly
>> just gratuitously (see also editorial issues).
>> These are the ni: and the nih: scheme. As far as I understand, they
>> differ as follows:
>>                                      ni:                nih:
>> authority:                          optional           disallowed
>> ascii-compatible encoding:          base64url          base16
>> check digit:                        disallowed         optional
>> query part:                         optional           disallowed
>> decimal presentation of algorithm:  disallowed         possible
>>
>> The usability of URIs is strongly influenced by the number of different
>> schemes, with the smaller a number, the better. As a somewhat made-up
>> example, if the original URIs had been separated into httph: for HTML
>> pages and httpi: for images, or any other arbitrary subdivision that one
>> can envision, that would have hurt the growth and extensibility of the
>> Web. Creating new URI schemes is occasionally necessary, and the ideas
>> that lead to this draft definitely seem to warrant a new scheme (*), but
>> there's no reason for two schemes.
>> [(*) I know people who would claim the the .well-formed http/https thing
>> is completely sufficient, no new scheme needed at all.]
>>
>> More specifically, if the original URIs had been separated into httpm:
>> (for machines) and httph: (for humans), the Web for sure wouldn't have
>> grown at the speed it did (and does) grow. In practice, there are huge
>> differences in human 'speakability' for URIs (and IRIs, for that
>> matter); compare e.g. http://google.com with
>> http://www.google.co.jp/#sclient=psy-ab&hl=en&site=&source=hp&q=hash&oq=hash&aq=f&aqi=g4&aql=
>>
>> (which I have significantly shortened to hopefully eliminate potential
>> privacy issues), or compare the average mailto: URI with the average
>> data: URI. However, what's important is that there never has been a
>> strong dividing line between machine-only and human-only URIs or
>> schemes, the division has always been very gradual. Short and mainly
>> human-oriented URIs have of course been handled by machines, and on the
>> other hand, very long URIs have been spoken when really necessary.
>> "Speakability" has been maintained to some extent by scheme designers,
>> and to some extent by "survival of the fittest" (URIs that weren't very
>> speakable (or spellable/memorizable/guessable/...), and their Web sites,
>> might just die out slowly).
>>
>> It should also be noted that the resistance against multiple URI schemes
>> may have been low because there are so many different ways to express
>> hashes in the draft anyway, and one more (the nih: section is the last
>> one before the examples section) didn't seem like much of a deal
>> anymore. But when it comes to URIs, one less is a lot better than one more.
>>
>> In the above ni:/nih: distinction, nih: seems to have been added as an
>> afterthought after realizing that reading an ni: URI aloud over the
>> phone may be somewhat suboptimal because there is a need for repeated
>> "upper case" - "lower case" (sure very quickly shortened to "upper" -
>> "lower" and then to "up" - "low" or something similar). It is not a bad
>> idea to try to make sure that IETF technology, and URIs in particular,
>> are accessible to people with certain kinds of dislexya. (There are
>> indeed people who have tremendous difficulties with distinguishing
>> upper- and lower-case letters, and this may or may not be connected with
>> other aspects of dislexya.) It is however totally unclear to this
>> reviewer why this has to lead to two different URI schemes with other
>> gratuitous differences.
>>
>> Finding a solution is rather easy (of course, other solutions may also
>> be possible): Merge the schemes, so that authority, check digit, and
>> query part are all optional (an authority part and/or a query part may
>> very well be very useful in human communication, and a check digit won't
>> hurt when transmitted electronically) and the decimal presentation of
>> the algorithm is always allowed, and use base32
>> (http://tools.ietf.org/html/rfc4648) as the encoding. This leads to a
>> 16.6% less efficient encoding of the value part of the ni: URI, but
>> given that other URI-related encodings, e.g. the %-encoding resulting
>> when converting an IRI to an URI, are much less efficient, and that URI
>> infrastructure these days can handle URIs with more than 1000 bytes,
>> this should not be a serious problem. Also, there's a separate binary
>> format (section 6) that is more compact already.
>
> I strongly disagree with merging ni&  nih. Though that clearly
> could be done, it would be an error.
>
> There was no such comment on the uri-review list and the designated
> expert was happy. That review was IMO the time for such comments
> and second-guessing the designated expert at this stage seems
> contrary to the registration requirements. So process-wise I
> think your main comment is late.

First, if IETF Last Call is too late to make serious technical comments 
on drafts, then I think we have to rename it to IETF Too-Late Call.

Second, designated experts are there to check for minimum requirements 
for a registration, and to give advice as they see fit (and have time). 
I'm myself a designated expert on "Character Sets", and I have 
definitely in the past approved, and would again in the future approve, 
registrations for stuff on which I would complain strongly if the 
question was "is this a good technical solution".

Graham Klyne, the designated expert for URI scheme registrations, has 
confirmed offline that he does not see his role as "expert reviewer" as 
judging the technical merit of a URI scheme proposal.


> But in any case, I also think you're wrong technically in this
> case.

Let's see. I hope we agree that we should come to a conclusion on this 
issue on technical merits, rather than on process details.


> nih *is* intended for a corner case, where humans need to speak these
> URIs and was added as a direct result of requirements from the core
> WG and not as an afterthought. ni URIs are not intended for that
> and so there really are IMO different requirements, (esp. e.g.
> checkdigit) that are best met with different schemes.

I agree that the value of a checkdigit is very limited for communication 
among machines (and for communication among humans with the help of 
machines, such as in the case of email).

On the other hand, I can't understand why (even assuming we needed a 
separate scheme) there is no authority and no query part on nih.

For the authority, I'd assume that it would be as useful when the URI is 
transmitted e.g. over the phone as when it is transmitted e.g. over email.

For the query part, there are already various ideas and proposals 
floating around, and at least some of them would be of interest for when 
the URI is transmitted e.g. over the phone. Also, even if we currently 
didn't have any actual proposals for query parameters, I think it would 
be a very bad idea to exclude them a priori for transmission e.g. over 
the phone.


> Merging ni/nih would also add more complexity for no benefit,
> which would be a bad idea.

Can you please explain what kind of complexity would have to be added? 
In terms of specification, merging the two schemes doesn't seem to be 
difficult or complex at all. Also, in terms of implementation, the only 
additions to the ni: scheme that become necessary are the check digit 
and the expression of the "suite id" as a decimal. It's very difficult 
for me to imagine that this would add significant complexity to an 
implementation; if code for nih: exists, that can mostly just be moved over.


> Your analogy about httpm/h may appear reasonable, but it is always
> unreasonable to draw conclusions from analogies. It is also unwise
> to reason from counterfactuals, which we'd also be doing if we
> accepted your argument. So I find that speculation utterly useless
> to be honest.

It is definitely unreasonable to draw conclusions from analogies *only*. 
But if you think that the httpm/h analogy is wrong, and that ni/nih is 
different, could you please explain *what* is different?


> In this case, we are dealing with different requirements so this
> should stay as-is.

If "different requirements" is your main (or only) real argument, could 
you at least explain exactly how they are different? Just that one 
requirement came from the core WG and others from other WGs or other 
parties doesn't help me to understand how the actual requirements 
differ. (Please note that even if the requirements differ, that doesn't 
mean that we need different technology to address them.)

Why do you say that ni: URIs are not intended for humans to speak? What 
am I supposed to do if I got an ni: URI in a mail message and call you 
on the phone to tell you about that? If I want to send somebody the 
information in an ni: URI by mail, should I use only the ni: version or 
only the nih: version, or both, if I can't exclude that the recipient 
may want to relay this information via voice?


> Finally, we have (some, early,) running code that matches the
> current draft and that ought also count for something

How much? The boiler plate on every ID is pretty clear that they are not 
set in stone. Also, the changes needed to merge the two schemes are not 
rocket science, quite to the contrary. (I herewith volunteer to fix the 
Ruby version, just to show)


> when compared
> to a change that would be a gratuitous dis-improvement

In what sense would merging the two schemes be a dis-improvement? Can 
you please explain?


> based it
> seems upon dubious argument

If you think that my arguments are dubious, please explain exactly why.


> that is also offered at the wrong
> point in the process.

See above. If there's something wrong with IETF Last Call, or with the 
fact that the Apps Area Directorate does reviews (which I don't think), 
then that should be addressed separately. For this discussion, I hope we 
can concentrate on technical issues.


Regards,   Martin.

From duerst@it.aoyama.ac.jp  Tue Jun 12 02:49:43 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 810F721F8619 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 02:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.652
X-Spam-Level: 
X-Spam-Status: No, score=-99.652 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 iaPqDZN9gxOh for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 02:49:42 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 6B35D21F85CD for <ietf@ietf.org>; Tue, 12 Jun 2012 02:49:42 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5C9nbY8000722 for <ietf@ietf.org>; Tue, 12 Jun 2012 18:49:37 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 7680_3a9c_ec1ba358_b473_11e1_9745_001d096c5782; Tue, 12 Jun 2012 18:49:37 +0900
Received: from [IPv6:::1] ([133.2.210.1]:58138) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D16AD> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 12 Jun 2012 18:49:41 +0900
Message-ID: <4FD710AD.9030505@it.aoyama.ac.jp>
Date: Tue, 12 Jun 2012 18:49:33 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com>	<CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>	<4FD0FDC2.2090802@cs.tcd.ie>	<CAGnGFMLc15-ZkD_Of7k0zK7ef-i6HN2LsPCfbW3pkwFkpSiOfA@mail.gmail.com> <4FD1E048.8080507@cs.tcd.ie>
In-Reply-To: <4FD1E048.8080507@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jonathan A Rees <rees@mumble.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 09:49:43 -0000

Hello Stephen, others,

On 2012/06/08 20:21, Stephen Farrell wrote:
>
> Hiya,
>
> On 06/08/2012 01:35 AM, Jonathan A Rees wrote:
>> On Thu, Jun 7, 2012 at 3:15 PM, Stephen Farrell
>> <stephen.farrell@cs.tcd.ie>  wrote:
>>>
>>> On 06/06/2012 09:33 PM, Jonathan A Rees wrote:

>>>> ---------- Forwarded message ----------
>>>> From: Jonathan A Rees<rees@mumble.net>
>>>> Date: Sun, May 6, 2012 at 7:57 PM
>>>> Subject: comments on http://tools.ietf.org/html/draft-farrell-decade-ni-06
>>>> To: Alexey Melnikov<alexey.melnikov@isode.com>, Barry Leiba
>>>> <barryleiba@computer.org>, "S. Farrell"<stephen.farrell@cs.tcd.ie>,
>>>> "P. Hallam-Baker"<pbaker@verisign.com>
>>>>
>>>> Here are some opinions on
>>>> http://tools.ietf.org/html/draft-farrell-decade-ni-06 :
>>>>
>>>> I think this URI scheme would be a welcome addition to web
>>>> architecture. Wide review should be sought, because this might become
>>>> quite important and if there are problems they will be very difficult
>>>> to fix later.
>>>>
>>>> I think using .well-known is a good idea.
>>>>
>>>> I think integration into the ecosystem, such as browser support,
>>>> should be anticipated; for this reason I think content type should be
>>>> elevated from an 'optional feature' to a 'required feature'.
>>>>
>>>> [i.e. conformant implementations must support it, even if providing
>>>> the content type in the URI is itself optional.]
>>>
>>> I could certainly live with that, and I suspect my co-authors too,
>>> but I'd need to ask 'em. However, we'd like to see more support for
>>> it before doing that. If we only hear from you on this, then I
>>> think leaving it in the other draft would be right. (See below
>>> for why we want to keep that draft.) I guess others have a few
>>> weeks to chime in on this.


>> It is certainly strongly promoted by the W3C web architecture document, see
>> http://www.w3.org/TR/webarch/#internet-media-type
>> so I think I have W3C consensus (as of 2005) behind my claim.
>
> Well I could argue that that says that protocols SHOULD
> do stuff and we're just defining the URI here and not a
> protocol. But let's see if we get more input on this.

Sophistry is great, but security is better :-).

Seriously, (1) URIs can be seen as (extremely small) protocols, (2) they 
are used in many protocols and formats, which might be better served 
with having the content type being taken care off rather than having to 
do it on their own, and (3) in order for the protocols to do the right 
stuff, they need the right information.



>>>> I agree with other commenters on the peculiarity of using // to
>>>> provide the location hint since the named host is not being trusted as
>>>> an authority. I don't understand why the 'primary' location isn't just
>>>> encoded in the query, just like the alternate domain(s) and "wrapped
>>>> URL(s)".  This would have the nice property that you can put the
>>>> identifying parts (i.e. hash and content type) first, and the less important
>>>> location hints parts all together after the identification. The various
>>>> location hints (whether primary or secondary) would go together and
>>>> their similarity would be clearer.
>>>>
>>>> (Unless I'm misunderstanding something and the part after the //
>>>> actually has status other than a hint?  That would seem to defeat
>>>> the purpose.)
>>>
>>> I think we could argue this (and we did already between the authors;-)
>>> and it'd come down to "pick a way." We did already and wrote code
>>> for that, so we'd prefer to stick with it as-is, especially if there's
>>> no compelling reason to change. I think its likely we can agree that
>>> there's no compelling differences here in whether we use "//" or
>>> a "?loc=" or whatever.
>>
>> Well, you have a chance to fix this now, and it will be impossible to
>> fix later.
>
> Its true we won't be able to change this later but not true
> IMO that any fix is needed, now or later.
>
>> Using // is contrary to RFC 3986, which very clearly says
>> "governance of the name space defined by the remainder of the URI is
>> delegated to that authority". This is certainly not what this URI
>> scheme does, so use of // is contrary to the appicable normative spec.
>
> I disagree. The full quote there is:
>
>    "Many URI schemes include a hierarchical element for a naming
>     authority so that governance of the name space defined by the
>     remainder of the URI is delegated to that authority (which may, in
>     turn, delegate it further)."
>
> There are no SHOULDs nor MUSTs there with which we're not
> complying, and "many" != "all." Yes, ni URIs differ in some
> respects from HTTP URLs, but if they didn't then this draft
> wouldn't be needed, so that's ok.

In my opinion, the decision on whether to use the authority part or not 
is probably more a theoretical one than a practical one. Either way 
seems to be fine. Strictly speaking on abstract "authority" grounds, the 
mailto: URI could have used // because mumble.net is the authority for 
mail to rees@mumble.net.

But I agree with Jonathan that once we start putting other information 
such as full URIs from which the resource can be retrieved, alternate 
'authorities' where it may be available, and so on, after the hash, then 
putting all that stuff there seems cleaner.

Regards,   Martin.

From stephen.farrell@cs.tcd.ie  Tue Jun 12 02:59:10 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 574B721F8620 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 02:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.066
X-Spam-Level: 
X-Spam-Status: No, score=-102.066 tagged_above=-999 required=5 tests=[AWL=2.233, BAYES_00=-2.599, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 O8rsnYFwm36F for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 02:59:08 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 764B221F862F for <ietf@ietf.org>; Tue, 12 Jun 2012 02:59:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id DA4031717FE; Tue, 12 Jun 2012 10:59:07 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339495146; bh=w2YVXWGikof+Pr buKBwiU2IgfQx9TOr9ZNmsH3o6Uhk=; b=WJnxHIrJRWseV3Db5/Om8QJAVXV+gZ wTER7+VPaTJk7BQK8fy51e8VjsfoKasTvbw7b2XbTTdqM2yWLZEGi2f50yrBoir7 42wBtb6/A7fJob+RZYczHWwLq/bNvknW/QT7lI5llmUzeDB6rvLK/mGD5Ree+md7 3TUALh0YYVPMTfNQ1abMllB0envAFjZvEs7T9i4yNGXQS6mKMBlIfM8jUBXPGRIE FewzLvgzUVASXMb4AqgYYFA42qrlELBPkuQr3xkEB+UlZHZBMHXH0+Sv77ufy9Hi zubclL/Q8lTaO6/s4P8iyXyPN1OLVcYQVRK3vwoIigT5JUZTSwImk/ug==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id qsiC9mUVnLLP; Tue, 12 Jun 2012 10:59:06 +0100 (IST)
Received: from [IPv6:2001:770:10:203:f0bb:fb89:d865:2639] (unknown [IPv6:2001:770:10:203:f0bb:fb89:d865:2639]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 0EFCC1714DE; Tue, 12 Jun 2012 10:59:04 +0100 (IST)
Message-ID: <4FD712E8.7010506@cs.tcd.ie>
Date: Tue, 12 Jun 2012 10:59:04 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: APPSDIR review of draft-farrell-decade-ni-07, major design issue (one or two URI schemes)
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp>
In-Reply-To: <4FD7083A.6080502@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Graham Klyne <GK@ninebynine.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 09:59:10 -0000

Hi Martin,

On 06/12/2012 10:13 AM, "Martin J. Dürst" wrote:
> Hello Stephen,
> 
> This mail responds to your points on the main technical issue that I
> have identified.
> 
> On 2012/06/05 20:11, Stephen Farrell wrote:
> 
>> On 06/05/2012 10:42 AM, "Martin J. Dürst" wrote:
>>> Hello everybody,
>>>
>>> [For replies, please trim the cc list, thanks!]
> 
> Done, removed apps-discuss@ietf.org for the moment.
> 
> 
>>> Major design issue:
>>>
>>> The draft defines two schemes, which differ only slightly, and mostly
>>> just gratuitously (see also editorial issues).
>>> These are the ni: and the nih: scheme. As far as I understand, they
>>> differ as follows:
>>>                                      ni:                nih:
>>> authority:                          optional           disallowed
>>> ascii-compatible encoding:          base64url          base16
>>> check digit:                        disallowed         optional
>>> query part:                         optional           disallowed
>>> decimal presentation of algorithm:  disallowed         possible

I'll note in passing that the two schemes differ in all those
respects. You may disagree with our design, but basically you're
showing that the two differ in pretty much all possible ways
other than that both include a hash value.

>>>
>>> The usability of URIs is strongly influenced by the number of different
>>> schemes, with the smaller a number, the better. As a somewhat made-up
>>> example, if the original URIs had been separated into httph: for HTML
>>> pages and httpi: for images, or any other arbitrary subdivision that one
>>> can envision, that would have hurt the growth and extensibility of the
>>> Web. Creating new URI schemes is occasionally necessary, and the ideas
>>> that lead to this draft definitely seem to warrant a new scheme (*), but
>>> there's no reason for two schemes.
>>> [(*) I know people who would claim the the .well-formed http/https thing
>>> is completely sufficient, no new scheme needed at all.]
>>>
>>> More specifically, if the original URIs had been separated into httpm:
>>> (for machines) and httph: (for humans), the Web for sure wouldn't have
>>> grown at the speed it did (and does) grow. In practice, there are huge
>>> differences in human 'speakability' for URIs (and IRIs, for that
>>> matter); compare e.g. http://google.com with
>>> http://www.google.co.jp/#sclient=psy-ab&hl=en&site=&source=hp&q=hash&oq=hash&aq=f&aqi=g4&aql=
>>>
>>>
>>> (which I have significantly shortened to hopefully eliminate potential
>>> privacy issues), or compare the average mailto: URI with the average
>>> data: URI. However, what's important is that there never has been a
>>> strong dividing line between machine-only and human-only URIs or
>>> schemes, the division has always been very gradual. Short and mainly
>>> human-oriented URIs have of course been handled by machines, and on the
>>> other hand, very long URIs have been spoken when really necessary.
>>> "Speakability" has been maintained to some extent by scheme designers,
>>> and to some extent by "survival of the fittest" (URIs that weren't very
>>> speakable (or spellable/memorizable/guessable/...), and their Web sites,
>>> might just die out slowly).
>>>
>>> It should also be noted that the resistance against multiple URI schemes
>>> may have been low because there are so many different ways to express
>>> hashes in the draft anyway, and one more (the nih: section is the last
>>> one before the examples section) didn't seem like much of a deal
>>> anymore. But when it comes to URIs, one less is a lot better than one
>>> more.
>>>
>>> In the above ni:/nih: distinction, nih: seems to have been added as an
>>> afterthought after realizing that reading an ni: URI aloud over the
>>> phone may be somewhat suboptimal because there is a need for repeated
>>> "upper case" - "lower case" (sure very quickly shortened to "upper" -
>>> "lower" and then to "up" - "low" or something similar). It is not a bad
>>> idea to try to make sure that IETF technology, and URIs in particular,
>>> are accessible to people with certain kinds of dislexya. (There are
>>> indeed people who have tremendous difficulties with distinguishing
>>> upper- and lower-case letters, and this may or may not be connected with
>>> other aspects of dislexya.) It is however totally unclear to this
>>> reviewer why this has to lead to two different URI schemes with other
>>> gratuitous differences.
>>>
>>> Finding a solution is rather easy (of course, other solutions may also
>>> be possible): Merge the schemes, so that authority, check digit, and
>>> query part are all optional (an authority part and/or a query part may
>>> very well be very useful in human communication, and a check digit won't
>>> hurt when transmitted electronically) and the decimal presentation of
>>> the algorithm is always allowed, and use base32
>>> (http://tools.ietf.org/html/rfc4648) as the encoding. This leads to a
>>> 16.6% less efficient encoding of the value part of the ni: URI, but
>>> given that other URI-related encodings, e.g. the %-encoding resulting
>>> when converting an IRI to an URI, are much less efficient, and that URI
>>> infrastructure these days can handle URIs with more than 1000 bytes,
>>> this should not be a serious problem. Also, there's a separate binary
>>> format (section 6) that is more compact already.
>>
>> I strongly disagree with merging ni&  nih. Though that clearly
>> could be done, it would be an error.
>>
>> There was no such comment on the uri-review list and the designated
>> expert was happy. That review was IMO the time for such comments
>> and second-guessing the designated expert at this stage seems
>> contrary to the registration requirements. So process-wise I
>> think your main comment is late.
> 
> First, if IETF Last Call is too late to make serious technical comments
> on drafts, then I think we have to rename it to IETF Too-Late Call.
> 
> Second, designated experts are there to check for minimum requirements
> for a registration, and to give advice as they see fit (and have time).
> I'm myself a designated expert on "Character Sets", and I have
> definitely in the past approved, and would again in the future approve,
> registrations for stuff on which I would complain strongly if the
> question was "is this a good technical solution".
> 
> Graham Klyne, the designated expert for URI scheme registrations, has
> confirmed offline that he does not see his role as "expert reviewer" as
> judging the technical merit of a URI scheme proposal.

While that's fair enough. Its also fair to note that there was
discussion of the this document on the uri-review list but this
aspect was not raised at all. That list is called "uri-review"
and from its archives it does seem to frequently do more than
just check the paperwork (including quite a few mails from you:-).

>> But in any case, I also think you're wrong technically in this>> case.
> 
> Let's see. I hope we agree that we should come to a conclusion on this
> issue on technical merits, rather than on process details.

Sure.

>> nih *is* intended for a corner case, 

Let me emphasise the above. nih is not intended to be used
broadly, nor often. If you want a hash-based URI scheme for
users to speak that is for broad frequent use then I think
you are free to try design one. But nih is not that and is
not intended to be that. (And I'm not sure such a beast
could really be done well.)

>> where humans need to speak these
>> URIs and was added as a direct result of requirements from the core
>> WG and not as an afterthought. ni URIs are not intended for that
>> and so there really are IMO different requirements, (esp. e.g.
>> checkdigit) that are best met with different schemes.
> 
> I agree that the value of a checkdigit is very limited for communication

s/very limited/useless/

> among machines (and for communication among humans with the help of
> machines, such as in the case of email).
> 
> On the other hand, I can't understand why (even assuming we needed a
> separate scheme) there is no authority and no query part on nih.

The main intent of nih is to allow entry of something that
confirms something else (e.g. a public key) that is already
present. There is no need for an authority for that, for
the use-cases we have. We could speculate about other potential
use-cases but we'd rather not speculate like that when there's
no need to.

> For the authority, I'd assume that it would be as useful when the URI is
> transmitted e.g. over the phone as when it is transmitted e.g. over email.

We don't have a use for that that I know about. I agree
it could be done, but then I think it'd also impact on
usability, which will be pretty crap no matter what's
done. But making usability worse also seems wrong. Not
having an authority also seems to work fine for PGP keys
and the lack of an authority does get rid of some threats,
if the nih URI is used for something security-sensitive.

> For the query part, there are already various ideas and proposals
> floating around, 

Where? If you mean draft-hallambaker-decade-params then
we (the authors of that) don't think those are useful for
nih names.

> and at least some of them would be of interest for when
> the URI is transmitted e.g. over the phone. Also, even if we currently
> didn't have any actual proposals for query parameters, I think it would
> be a very bad idea to exclude them a priori for transmission e.g. over
> the phone.

I disagree that there is any "very bad idea" here.

>> Merging ni/nih would also add more complexity for no benefit,
>> which would be a bad idea.
> 
> Can you please explain what kind of complexity would have to be added?

I think its obvious actually. In your table above you highlighted
5 ways in which ni and nih differ. Merging all those yields loads
of combinations, which makes for complexity.

> In terms of specification, merging the two schemes doesn't seem to be
> difficult or complex at all. Also, in terms of implementation, the only
> additions to the ni: scheme that become necessary are the check digit
> and the expression of the "suite id" as a decimal. It's very difficult
> for me to imagine that this would add significant complexity to an
> implementation; if code for nih: exists, that can mostly just be moved
> over.

Feel free to look at our code. (With the caveat that I'm a crap
programmer so close your eyes a bit when you look at the 'C' code:-)

>> Your analogy about httpm/h may appear reasonable, but it is always
>> unreasonable to draw conclusions from analogies. It is also unwise
>> to reason from counterfactuals, which we'd also be doing if we
>> accepted your argument. So I find that speculation utterly useless
>> to be honest.
> 
> It is definitely unreasonable to draw conclusions from analogies *only*.

I only saw the analogy. What in your httpm/h argument is not
couterfactual analogy?

> But if you think that the httpm/h analogy is wrong, and that ni/nih is
> different, could you please explain *what* is different?

We have real use cases for ni and nih and we think they differ.
I'd be repeating myself to say why again.

>> In this case, we are dealing with different requirements so this
>> should stay as-is.
> 
> If "different requirements" is your main (or only) real argument, 

That would be a valid argument.

> could
> you at least explain exactly how they are different? 

I did that above. Asking for an "exact" explanation seems
like asking the same thing again.

> Just that one
> requirement came from the core WG and others from other WGs or other
> parties doesn't help me to understand how the actual requirements
> differ. (Please note that even if the requirements differ, that doesn't
> mean that we need different technology to address them.)

Perhaps not. But that was the design choice we made and its
a valid one.

> Why do you say that ni: URIs are not intended for humans to speak? 

So phone me up and say this:

  ni:///sha-256;UyaQV-Ev4rdLoHyJJWCi11OHfrYv9E1aGQAlMO2X_-Q

> What
> am I supposed to do if I got an ni: URI in a mail message and call you
> on the phone to tell you about that? 

Not my problem actually, but I guess most people might
say "remember that mail you sent me with all that gobbledygook
nonsense - what the hell was that about?" :-)

>  If I want to send somebody the
> information in an ni: URI by mail, should I use only the ni: version or
> only the nih: version, or both, if I can't exclude that the recipient
> may want to relay this information via voice?

You can try either and let me know what works. This seems like
a very artificial use-case for ni.

>> Finally, we have (some, early,) running code that matches the
>> current draft and that ought also count for something
> 
> How much? 

Feel free to go look and see. [1] I've not counted lines of
code, but we have c, python, ruby and clojure library
implementations and some apps and other bits and pieces.

   [1] http://sourceforge.net/projects/netinf/

> The boiler plate on every ID is pretty clear that they are not
> set in stone. Also, the changes needed to merge the two schemes are not
> rocket science, quite to the contrary. (I herewith volunteer to fix the
> Ruby version, just to show)

I didn't say our code is set in stone. I said that running code
counts.

I didn't say a merge would require rocket science. I said it'd be
a bad idea and would produce a worse result.

>> when compared
>> to a change that would be a gratuitous dis-improvement
> 
> In what sense would merging the two schemes be a dis-improvement? Can
> you please explain?

I believe I did that above.

>> based it
>> seems upon dubious argument
> 
> If you think that my arguments are dubious, please explain exactly why.

I believe I did that above. (To be clear: not all your argument is
dubious but the httph/m part is IMO.)

>> that is also offered at the wrong
>> point in the process.
> 
> See above. If there's something wrong with IETF Last Call, or with the
> fact that the Apps Area Directorate does reviews (which I don't think),
> then that should be addressed separately. For this discussion, I hope we
> can concentrate on technical issues.

Right. But let's not ignore the fact that the uri-review
list had sight of this at the end of April.

Bottom line - we have use-cases and a valid design and running
code that as far as we know works and I see no reason to make
the change you'd like, which would make thing worse IMO.

Cheers,
S.


> 
> 
> Regards,   Martin.
> 
> 

From stephen.farrell@cs.tcd.ie  Tue Jun 12 03:09:40 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A61221F862F for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 03:09:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.183
X-Spam-Level: 
X-Spam-Status: No, score=-102.183 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 KEltMWU3IlXp for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 03:09:39 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 0B53C21F8628 for <ietf@ietf.org>; Tue, 12 Jun 2012 03:09:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 73976154274; Tue, 12 Jun 2012 11:09:38 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339495777; bh=krJj6WILypVlFm 9wG+Ng4LaetpBheW6YWEAPBn4lFwE=; b=CyUo+PzPLlZr9VGhlvX+aCdoJD6xAx A+Io+/dA1OLMpAo6FHzPnKFMailwK+SlK35CB8gMJiXLxtG7p7DygaiZa3r0A+xp xeQARE+CWGXG4W2tOPkbyOh2zrwUrV+/X8krWclqTDxGyxBpsAfJvlJkyecwiIIf STUkUuNWcWwKnsGVAEqCD4DWSsHfiYbOJak9Wd80VrfRePooO8B+wplk5fyTft1i 1k/njx1Qtzw6+qKg07LtFwl6/HeRUThvM6JjOe/KJmVh+9oIZSYUlZbI/Apfb2Pf XSzlEJ/V2+pZFgWbMqmGpbXR0JCG+ZOqafRn5VuKasGMJKUSFxQ0xpQA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id ZLPpStZeziyg; Tue, 12 Jun 2012 11:09:37 +0100 (IST)
Received: from [IPv6:2001:770:10:203:f0bb:fb89:d865:2639] (unknown [IPv6:2001:770:10:203:f0bb:fb89:d865:2639]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 21453171803; Tue, 12 Jun 2012 11:09:33 +0100 (IST)
Message-ID: <4FD7155D.6080407@cs.tcd.ie>
Date: Tue, 12 Jun 2012 11:09:33 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com>	<CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>	<4FD0FDC2.2090802@cs.tcd.ie>	<CAGnGFMLc15-ZkD_Of7k0zK7ef-i6HN2LsPCfbW3pkwFkpSiOfA@mail.gmail.com> <4FD1E048.8080507@cs.tcd.ie> <4FD710AD.9030505@it.aoyama.ac.jp>
In-Reply-To: <4FD710AD.9030505@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Jonathan A Rees <rees@mumble.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 10:09:40 -0000

Hi Martin,

On 06/12/2012 10:49 AM, "Martin J. Dürst" wrote:
> Hello Stephen, others,
> 
> On 2012/06/08 20:21, Stephen Farrell wrote:
>>
>> Hiya,
>>
>> On 06/08/2012 01:35 AM, Jonathan A Rees wrote:
>>> On Thu, Jun 7, 2012 at 3:15 PM, Stephen Farrell
>>> <stephen.farrell@cs.tcd.ie>  wrote:
>>>>
>>>> On 06/06/2012 09:33 PM, Jonathan A Rees wrote:
> 
>>>>> ---------- Forwarded message ----------
>>>>> From: Jonathan A Rees<rees@mumble.net>
>>>>> Date: Sun, May 6, 2012 at 7:57 PM
>>>>> Subject: comments on
>>>>> http://tools.ietf.org/html/draft-farrell-decade-ni-06
>>>>> To: Alexey Melnikov<alexey.melnikov@isode.com>, Barry Leiba
>>>>> <barryleiba@computer.org>, "S. Farrell"<stephen.farrell@cs.tcd.ie>,
>>>>> "P. Hallam-Baker"<pbaker@verisign.com>
>>>>>
>>>>> Here are some opinions on
>>>>> http://tools.ietf.org/html/draft-farrell-decade-ni-06 :
>>>>>
>>>>> I think this URI scheme would be a welcome addition to web
>>>>> architecture. Wide review should be sought, because this might become
>>>>> quite important and if there are problems they will be very difficult
>>>>> to fix later.
>>>>>
>>>>> I think using .well-known is a good idea.
>>>>>
>>>>> I think integration into the ecosystem, such as browser support,
>>>>> should be anticipated; for this reason I think content type should be
>>>>> elevated from an 'optional feature' to a 'required feature'.
>>>>>
>>>>> [i.e. conformant implementations must support it, even if providing
>>>>> the content type in the URI is itself optional.]
>>>>
>>>> I could certainly live with that, and I suspect my co-authors too,
>>>> but I'd need to ask 'em. However, we'd like to see more support for
>>>> it before doing that. If we only hear from you on this, then I
>>>> think leaving it in the other draft would be right. (See below
>>>> for why we want to keep that draft.) I guess others have a few
>>>> weeks to chime in on this.
> 
> 
>>> It is certainly strongly promoted by the W3C web architecture
>>> document, see
>>> http://www.w3.org/TR/webarch/#internet-media-type
>>> so I think I have W3C consensus (as of 2005) behind my claim.
>>
>> Well I could argue that that says that protocols SHOULD
>> do stuff and we're just defining the URI here and not a
>> protocol. But let's see if we get more input on this.
> 
> Sophistry is great, but security is better :-).

:-)

> Seriously, (1) URIs can be seen as (extremely small) protocols, (2) they
> are used in many protocols and formats, which might be better served
> with having the content type being taken care off rather than having to
> do it on their own, and (3) in order for the protocols to do the right
> stuff, they need the right information.

I'm looking into this since a number of people seem to
want it and it does have some real value.

My main concern is with adding it is to see if it can be
done without over-complicating a basic implementation. The
danger would be that we'd say "you MUST be able to verify
name-data integrity for any MIME Content Type" which'd get
hard quickly.

I expect we'll shoot out a proposal for how ct could be
included at the end of IETF LC. (We may still argue
against, but we'll likely float a version including it
in any case.)

>>>>> I agree with other commenters on the peculiarity of using // to
>>>>> provide the location hint since the named host is not being trusted as
>>>>> an authority. I don't understand why the 'primary' location isn't just
>>>>> encoded in the query, just like the alternate domain(s) and "wrapped
>>>>> URL(s)".  This would have the nice property that you can put the
>>>>> identifying parts (i.e. hash and content type) first, and the less
>>>>> important
>>>>> location hints parts all together after the identification. The
>>>>> various
>>>>> location hints (whether primary or secondary) would go together and
>>>>> their similarity would be clearer.
>>>>>
>>>>> (Unless I'm misunderstanding something and the part after the //
>>>>> actually has status other than a hint?  That would seem to defeat
>>>>> the purpose.)
>>>>
>>>> I think we could argue this (and we did already between the authors;-)
>>>> and it'd come down to "pick a way." We did already and wrote code
>>>> for that, so we'd prefer to stick with it as-is, especially if there's
>>>> no compelling reason to change. I think its likely we can agree that
>>>> there's no compelling differences here in whether we use "//" or
>>>> a "?loc=" or whatever.
>>>
>>> Well, you have a chance to fix this now, and it will be impossible to
>>> fix later.
>>
>> Its true we won't be able to change this later but not true
>> IMO that any fix is needed, now or later.
>>
>>> Using // is contrary to RFC 3986, which very clearly says
>>> "governance of the name space defined by the remainder of the URI is
>>> delegated to that authority". This is certainly not what this URI
>>> scheme does, so use of // is contrary to the appicable normative spec.
>>
>> I disagree. The full quote there is:
>>
>>    "Many URI schemes include a hierarchical element for a naming
>>     authority so that governance of the name space defined by the
>>     remainder of the URI is delegated to that authority (which may, in
>>     turn, delegate it further)."
>>
>> There are no SHOULDs nor MUSTs there with which we're not
>> complying, and "many" != "all." Yes, ni URIs differ in some
>> respects from HTTP URLs, but if they didn't then this draft
>> wouldn't be needed, so that's ok.
> 
> In my opinion, the decision on whether to use the authority part or not
> is probably more a theoretical one than a practical one. Either way
> seems to be fine. Strictly speaking on abstract "authority" grounds, the
> mailto: URI could have used // because mumble.net is the authority for
> mail to rees@mumble.net.
> 
> But I agree with Jonathan that once we start putting other information
> such as full URIs from which the resource can be retrieved, alternate
> 'authorities' where it may be available, and so on, after the hash, then
> putting all that stuff there seems cleaner.

Right. A few people seem to prefer it like that. We prefer it
as is. I agree with you that this isn't significant so I'd
really rather go with the running code here.

Cheers,
S.


> 
> Regards,   Martin.
> 
> 

From duerst@it.aoyama.ac.jp  Tue Jun 12 03:44:07 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F96721F861A for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 03:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.38
X-Spam-Level: 
X-Spam-Status: No, score=-99.38 tagged_above=-999 required=5 tests=[AWL=-0.190, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_55=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 oEyR3oMG8mIc for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 03:44:06 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 905DF21F8619 for <ietf@ietf.org>; Tue, 12 Jun 2012 03:44:05 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5CAhwZK011380 for <ietf@ietf.org>; Tue, 12 Jun 2012 19:43:58 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 7682_047d_83a05c44_b47b_11e1_96d0_001d096c5782; Tue, 12 Jun 2012 19:43:57 +0900
Received: from [IPv6:::1] ([133.2.210.1]:37047) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D1705> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 12 Jun 2012 19:44:01 +0900
Message-ID: <4FD71D6A.9070101@it.aoyama.ac.jp>
Date: Tue, 12 Jun 2012 19:43:54 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com>	<CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>	<CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com>	<4FD29389.5060900@cs.tcd.ie> <tslboktwbzv.fsf@mit.edu> <4FD2AAB3.4010305@cs.tcd.ie>
In-Reply-To: <4FD2AAB3.4010305@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jonathan A Rees <rees@mumble.net>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 10:44:07 -0000

Hello Stephen,

On 2012/06/09 10:45, Stephen Farrell wrote:

> On 06/09/2012 01:43 AM, Sam Hartman wrote:

>> It's a naming
>> hierarchy.  My main concern is whether the relative reference algorithm
>> described in section 5/4.2 of RFC 3986. In particular take a look at the
>> last part of section 1.2 of RFC 3986 regarding the disallowing of
>> /. Consider how you want relative references in an HTML document
>> resolved through a ni: URI to work.  I don't think your use of authority
>> provides good results. However I'm not sure that better results would be
>> achieved without hierarchy.  I hope though that these comments will help
>> inject some ways of reasoning about authority that are less mystical and
>> that lead to more practical discussion.
>
> Thanks.
>
> I think your comment about relative URIs is fair and we maybe ought
> say there are no such things for ni URIs. (Or however that kind of
> thing is stated best).

You can't say that. It's perfectly okay to have an HTML document like this:

<html>
  <head>
    <title>ni: relative URI test</title>
    <base href="ni://example.com">
  </head>

  <body>
    <p>Please check <a href="sha-256;f4OxZX...">this document</a>.
      And <a href="sha-256;UyaQV...">this other document</a>.
      And <a href="sha-256-128;...">this third document</a>.
    </p>
  </body>
</html>

("..." used for brevity). What the browser will try to interpret when 
the links are activated is:
ni://example.com/sha-256;f4OxZX...
ni://example.com/sha-256;UyaQV...
ni://example.com/sha-256-128;...

If you don't think that makes sense, then you might just leave it to 
users to not use it that way. On the other hand, if you think that's 
actively harmful (I couldn't come up with a reason for that), then you 
have to change to the form without //.

[Well, actual browser behavior is a bit more mixed:

IE does what's explained above, and tries to go to the address, but says 
that this page can't be displayed.

Safari uses the above resolved URIs when asked to copy the link, and 
also tries to follow the link saying that the page can't be opened.

Mozilla doesn't even show the link texts as links, nor allows to 
activate them, probably because it decides that it doesn't want to 
disappoint the user when she clicks.

Chrome shows the underlined links, but doesn't want to show any 
destination when hoovering. When activating, it goes to about:blank.

Opera shows and tries to go to ni://sha-256;f4OxZX... and similar, i.e. 
it seems to drop the authority, possibly because it doesn't have ni: 
registered as a hierarchical scheme. But that would be fixed when the 
scheme is getting implemented.]

> I guess a sentence or two about relative URIs would be worthwhile
> and I'll ponder that.

Yes, please do. I'm willing to check it.

Regards,    Martin.

From duerst@it.aoyama.ac.jp  Tue Jun 12 03:56:59 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0685221F8557 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 03:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.648
X-Spam-Level: 
X-Spam-Status: No, score=-99.648 tagged_above=-999 required=5 tests=[AWL=0.142, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 xUKRDUjGf+ds for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 03:56:58 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 34FB321F851C for <ietf@ietf.org>; Tue, 12 Jun 2012 03:56:58 -0700 (PDT)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5CAuv9Q021421 for <ietf@ietf.org>; Tue, 12 Jun 2012 19:56:57 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 05ee_e0ee_5430c37a_b47d_11e1_a138_001d096c566a; Tue, 12 Jun 2012 19:56:56 +0900
Received: from [IPv6:::1] ([133.2.210.1]:39493) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D1710> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 12 Jun 2012 19:57:01 +0900
Message-ID: <4FD72075.6060200@it.aoyama.ac.jp>
Date: Tue, 12 Jun 2012 19:56:53 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Comments on draft-farrell-decade-ni-06
References: <6kk2t71ghjalf43tqu14pvcnisoarv924g@hive.bjoern.hoehrmann.de> <4FD34E9F.4060904@cs.tcd.ie>
In-Reply-To: <4FD34E9F.4060904@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 10:56:59 -0000

Hello Stephen,

On 2012/06/09 22:24, Stephen Farrell wrote:
>
> Hi BjÃ¶rn,
>
> On 06/08/2012 03:16 AM, Bjoern Hoehrmann wrote:
>> I think the requirement in RFC 4395 section 2.6 applies here, there are
>> text fields in 'ni' and 'nih' addresses, so there needs to be some dis-
>> cussion about I18N and IRI issues, or a statement that there are none,
>> or something along those lines. What if I want a non-ASCII host name in
>> them, for instance?
>
> So what's reasonable here?
>
> We're inheriting some definitions (authority, unreserved&
> pct-encoded) from 3986 and I'd not like to break that, nor
> would I like something that doesn't work with most libraries.
>
> Any suggestions?

I shouldn't have missed I18N and IRI issues in my apps review.

For IDNs in the authority part, you are essentially safe because RFC 
3986 says exactly how to handle this (%-encoding based on UTF-8; 
alternatively punycode (A-Labels), for which library suppor may be 
better than for the former). You don't have to say anything about this, 
but you can say something if you think it's useful for implementers and 
if it's limited to a non-normative pointer (to the last paragraph of 
http://tools.ietf.org/html/rfc3986#section-3.2.2).

For the query part, you should put in the following text (or an equivalent):

For compatibility with IRIs, non-ASCII characters in the query part MUST 
be encoded as UTF-8, and the resulting octets MUST be %-encoded (see 
http://tools.ietf.org/html/rfc3986#section-2.1).

My understanding is that there's no danger for getting non-ASCII 
characters in the path part, and that fragments are separate anyway.

Regards,   Martin.

From stephen.farrell@cs.tcd.ie  Tue Jun 12 04:00:24 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F7DA21F8628 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 04:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.921
X-Spam-Level: 
X-Spam-Status: No, score=-101.921 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 ykrmpYdxog52 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 04:00:24 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id AB91B21F8627 for <ietf@ietf.org>; Tue, 12 Jun 2012 04:00:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id BE34F171803; Tue, 12 Jun 2012 12:00:22 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339498822; bh=Nvi6yzA5ZhHeW0 dzNHc1KVG5T7PK4z1cioOAce9YiVY=; b=2EndkiqzdJsTUzBe6KqhK0mkMsGnIF 8iQl50mjlY+EZs0Jx6d3GWWyHT8CDGzujVelGqpQIqTKlOALfVTRcXjS1SmBtbiQ pUJHpm+3MJdPgfEkygf3RRLypaGDtHBrYdSggRS7lMCSioQeH/EzHhkPHcEPvcU3 3vi/678ZtjlYZmmQzQ3drMNPMO+8dIdmc7MEn7FhhfYpVdKK3lHcVfsQdiSxVxA4 rbXqsVh9egwU6SiHKp/80QwJ1DU71l11IUBsmlVKF/EF+PTX7KTRB1LLf5lo5T7n bUrCav6LeycG9tQQiVd3Vq01gpYTv1Ut1TdCVa4DDZS5CZayTMGNsOvg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id ijoAdaldU+Ko; Tue, 12 Jun 2012 12:00:22 +0100 (IST)
Received: from [IPv6:2001:770:10:203:f0bb:fb89:d865:2639] (unknown [IPv6:2001:770:10:203:f0bb:fb89:d865:2639]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id A81DB171800; Tue, 12 Jun 2012 12:00:17 +0100 (IST)
Message-ID: <4FD72141.9010201@cs.tcd.ie>
Date: Tue, 12 Jun 2012 12:00:17 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com>	<CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>	<CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com>	<4FD29389.5060900@cs.tcd.ie> <tslboktwbzv.fsf@mit.edu> <4FD2AAB3.4010305@cs.tcd.ie> <4FD71D6A.9070101@it.aoyama.ac.jp>
In-Reply-To: <4FD71D6A.9070101@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Jonathan A Rees <rees@mumble.net>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 11:00:24 -0000

Hiya,

Ah, ok I get it now. I'll look back at that again,

Ta,
S

On 06/12/2012 11:43 AM, "Martin J. Dürst" wrote:
> Hello Stephen,
> 
> On 2012/06/09 10:45, Stephen Farrell wrote:
> 
>> On 06/09/2012 01:43 AM, Sam Hartman wrote:
> 
>>> It's a naming
>>> hierarchy.  My main concern is whether the relative reference algorithm
>>> described in section 5/4.2 of RFC 3986. In particular take a look at the
>>> last part of section 1.2 of RFC 3986 regarding the disallowing of
>>> /. Consider how you want relative references in an HTML document
>>> resolved through a ni: URI to work.  I don't think your use of authority
>>> provides good results. However I'm not sure that better results would be
>>> achieved without hierarchy.  I hope though that these comments will help
>>> inject some ways of reasoning about authority that are less mystical and
>>> that lead to more practical discussion.
>>
>> Thanks.
>>
>> I think your comment about relative URIs is fair and we maybe ought
>> say there are no such things for ni URIs. (Or however that kind of
>> thing is stated best).
> 
> You can't say that. It's perfectly okay to have an HTML document like this:
> 
> <html>
>  <head>
>    <title>ni: relative URI test</title>
>    <base href="ni://example.com">
>  </head>
> 
>  <body>
>    <p>Please check <a href="sha-256;f4OxZX...">this document</a>.
>      And <a href="sha-256;UyaQV...">this other document</a>.
>      And <a href="sha-256-128;...">this third document</a>.
>    </p>
>  </body>
> </html>
> 
> ("..." used for brevity). What the browser will try to interpret when
> the links are activated is:
> ni://example.com/sha-256;f4OxZX...
> ni://example.com/sha-256;UyaQV...
> ni://example.com/sha-256-128;...
> 
> If you don't think that makes sense, then you might just leave it to
> users to not use it that way. On the other hand, if you think that's
> actively harmful (I couldn't come up with a reason for that), then you
> have to change to the form without //.
> 
> [Well, actual browser behavior is a bit more mixed:
> 
> IE does what's explained above, and tries to go to the address, but says
> that this page can't be displayed.
> 
> Safari uses the above resolved URIs when asked to copy the link, and
> also tries to follow the link saying that the page can't be opened.
> 
> Mozilla doesn't even show the link texts as links, nor allows to
> activate them, probably because it decides that it doesn't want to
> disappoint the user when she clicks.
> 
> Chrome shows the underlined links, but doesn't want to show any
> destination when hoovering. When activating, it goes to about:blank.
> 
> Opera shows and tries to go to ni://sha-256;f4OxZX... and similar, i.e.
> it seems to drop the authority, possibly because it doesn't have ni:
> registered as a hierarchical scheme. But that would be fixed when the
> scheme is getting implemented.]
> 
>> I guess a sentence or two about relative URIs would be worthwhile
>> and I'll ponder that.
> 
> Yes, please do. I'm willing to check it.
> 
> Regards,    Martin.
> 
> 

From stephen.farrell@cs.tcd.ie  Tue Jun 12 04:08:26 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3637121F864C for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 04:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.866
X-Spam-Level: 
X-Spam-Status: No, score=-101.866 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 i+y9EbAq5yqm for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 04:08:24 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 2066421F84DF for <ietf@ietf.org>; Tue, 12 Jun 2012 04:08:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 864A9171805; Tue, 12 Jun 2012 12:08:17 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339499297; bh=tyCCdiptUrmUaj hwG1NzOHu9K9Sx2nVTVUAaDNwxfrI=; b=pftNW977sRo1l0PsCTcVxFcrAn3uo0 mfAy0WCD9sifGwJB9oVYZUPESio6m133rkgUZWgP2A/okxdzi56x/VLg75CLDGQj HFfb5oNRdcXyq+y33FzB4+FkVLaUAq2pjTfGwiwTcfgOkB9+xakatOk9M8QKb9/e 3zAE2KMAq0yEvXnmNcBtr1VcbvHTVDpHJ3An7fkdjvoiYMTpYgB/BJdyNToaO0sd OYcGDHyJ/WUgWQD9qFJWfoe2fi2vJ37g5DXnKMSJXh7/MZU9WSgYeWbfekhJLhFH LJwJLavzrKEwoAo0osMnFQYV2zI0ZNYtRaxVNVU6Ei5Tu5J09+5JQdsg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id c+xBy2vCeafQ; Tue, 12 Jun 2012 12:08:17 +0100 (IST)
Received: from [IPv6:2001:770:10:203:f0bb:fb89:d865:2639] (unknown [IPv6:2001:770:10:203:f0bb:fb89:d865:2639]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 4C60C171803; Tue, 12 Jun 2012 12:08:15 +0100 (IST)
Message-ID: <4FD7231F.1050903@cs.tcd.ie>
Date: Tue, 12 Jun 2012 12:08:15 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com>	<CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>	<CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com>	<4FD29389.5060900@cs.tcd.ie> <tslboktwbzv.fsf@mit.edu> <4FD2AAB3.4010305@cs.tcd.ie> <4FD71D6A.9070101@it.aoyama.ac.jp>
In-Reply-To: <4FD71D6A.9070101@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Jonathan A Rees <rees@mumble.net>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 11:08:26 -0000

So would it work to add this:

"
   Note that relative ni URIs can occur, for example as shown in
   Figure 5.  In such cases, user agents MUST construct the absolute URI
   as they would in the case of an HTTP URL, that is, in the example
   shown the absolute URI for "this third document" would be
   "ni://example.com/sha-256-128;...".


     <html>
      <head>
        <title>ni: relative URI test</title>
        <base href="ni://example.com">
      </head>

      <body>
        <p>Please check <a href="sha-256;f4OxZX...">this document</a>.
          And <a href="sha-256;UyaQV...">this other document</a>.
          And <a href="sha-256-128;...">this third document</a>.
        </p>
      </body>
     </html>

                Figure 5: Example HTML with relative ni URI

"

Better suggestions welcome.
Ta,
S.


On 06/12/2012 11:43 AM, "Martin J. Dürst" wrote:
> Hello Stephen,
> 
> On 2012/06/09 10:45, Stephen Farrell wrote:
> 
>> On 06/09/2012 01:43 AM, Sam Hartman wrote:
> 
>>> It's a naming
>>> hierarchy.  My main concern is whether the relative reference algorithm
>>> described in section 5/4.2 of RFC 3986. In particular take a look at the
>>> last part of section 1.2 of RFC 3986 regarding the disallowing of
>>> /. Consider how you want relative references in an HTML document
>>> resolved through a ni: URI to work.  I don't think your use of authority
>>> provides good results. However I'm not sure that better results would be
>>> achieved without hierarchy.  I hope though that these comments will help
>>> inject some ways of reasoning about authority that are less mystical and
>>> that lead to more practical discussion.
>>
>> Thanks.
>>
>> I think your comment about relative URIs is fair and we maybe ought
>> say there are no such things for ni URIs. (Or however that kind of
>> thing is stated best).
> 
> You can't say that. It's perfectly okay to have an HTML document like this:
> 
> <html>
>  <head>
>    <title>ni: relative URI test</title>
>    <base href="ni://example.com">
>  </head>
> 
>  <body>
>    <p>Please check <a href="sha-256;f4OxZX...">this document</a>.
>      And <a href="sha-256;UyaQV...">this other document</a>.
>      And <a href="sha-256-128;...">this third document</a>.
>    </p>
>  </body>
> </html>
> 
> ("..." used for brevity). What the browser will try to interpret when
> the links are activated is:
> ni://example.com/sha-256;f4OxZX...
> ni://example.com/sha-256;UyaQV...
> ni://example.com/sha-256-128;...
> 
> If you don't think that makes sense, then you might just leave it to
> users to not use it that way. On the other hand, if you think that's
> actively harmful (I couldn't come up with a reason for that), then you
> have to change to the form without //.
> 
> [Well, actual browser behavior is a bit more mixed:
> 
> IE does what's explained above, and tries to go to the address, but says
> that this page can't be displayed.
> 
> Safari uses the above resolved URIs when asked to copy the link, and
> also tries to follow the link saying that the page can't be opened.
> 
> Mozilla doesn't even show the link texts as links, nor allows to
> activate them, probably because it decides that it doesn't want to
> disappoint the user when she clicks.
> 
> Chrome shows the underlined links, but doesn't want to show any
> destination when hoovering. When activating, it goes to about:blank.
> 
> Opera shows and tries to go to ni://sha-256;f4OxZX... and similar, i.e.
> it seems to drop the authority, possibly because it doesn't have ni:
> registered as a hierarchical scheme. But that would be fixed when the
> scheme is getting implemented.]
> 
>> I guess a sentence or two about relative URIs would be worthwhile
>> and I'll ponder that.
> 
> Yes, please do. I'm willing to check it.
> 
> Regards,    Martin.
> 
> 

From stephen.farrell@cs.tcd.ie  Tue Jun 12 04:11:46 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9CC921F865E for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 04:11:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.132
X-Spam-Level: 
X-Spam-Status: No, score=-102.132 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 MJ+t-rgqODoJ for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 04:11:46 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 07F9721F864C for <ietf@ietf.org>; Tue, 12 Jun 2012 04:11:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 620B7171803; Tue, 12 Jun 2012 12:11:45 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339499504; bh=z0P/0mWxIsUs4Y 9BxudrmVgsFjjLqjNTCZxGGMxJQGA=; b=VWI0aLHrucRu/joNfvr30CtuSlzo6v wQMmvzARs4Xc3UITy1R8K03qGXLylCfSF44D8ZwGOYXsls9txxbdp9Es5B9lo4Bo 6nDUbhpR6St+6ZzIp1Ucjor1GXgOrIsf/Vw/buMIJGr+GsPf/hueCNXAoWLQwaDs 9J9SUn0hUPe/nC1li7r+mxUoQyb7l0LJlFsvH6eF6LsIw1tjDFLoPAgl2pFrsBaV hkLLquGkgqo5RI85HGVLrkLElomBvD4q4hMMFk4JxwtD04P3J8NjmM5JwY+Gi9hw Ct5lG07Hz9tFKboFj9QRpcEte/qfKkCtyEdQiegG6FjDwvFycfCN8vdg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id lrrMLgA-5zjr; Tue, 12 Jun 2012 12:11:44 +0100 (IST)
Received: from [IPv6:2001:770:10:203:f0bb:fb89:d865:2639] (unknown [IPv6:2001:770:10:203:f0bb:fb89:d865:2639]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id DEE7F171800; Tue, 12 Jun 2012 12:11:43 +0100 (IST)
Message-ID: <4FD723F0.1080607@cs.tcd.ie>
Date: Tue, 12 Jun 2012 12:11:44 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: Comments on draft-farrell-decade-ni-06
References: <6kk2t71ghjalf43tqu14pvcnisoarv924g@hive.bjoern.hoehrmann.de> <4FD34E9F.4060904@cs.tcd.ie> <4FD72075.6060200@it.aoyama.ac.jp>
In-Reply-To: <4FD72075.6060200@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 11:11:46 -0000

On 06/12/2012 11:56 AM, "Martin J. Dürst" wrote:
> Hello Stephen,
> 
> On 2012/06/09 22:24, Stephen Farrell wrote:
>>
>> Hi Björn,
>>
>> On 06/08/2012 03:16 AM, Bjoern Hoehrmann wrote:
>>> I think the requirement in RFC 4395 section 2.6 applies here, there are
>>> text fields in 'ni' and 'nih' addresses, so there needs to be some dis-
>>> cussion about I18N and IRI issues, or a statement that there are none,
>>> or something along those lines. What if I want a non-ASCII host name in
>>> them, for instance?
>>
>> So what's reasonable here?
>>
>> We're inheriting some definitions (authority, unreserved&
>> pct-encoded) from 3986 and I'd not like to break that, nor
>> would I like something that doesn't work with most libraries.
>>
>> Any suggestions?
> 
> I shouldn't have missed I18N and IRI issues in my apps review.
> 
> For IDNs in the authority part, you are essentially safe because RFC
> 3986 says exactly how to handle this (%-encoding based on UTF-8;
> alternatively punycode (A-Labels), for which library suppor may be
> better than for the former). You don't have to say anything about this,
> but you can say something if you think it's useful for implementers and
> if it's limited to a non-normative pointer (to the last paragraph of
> http://tools.ietf.org/html/rfc3986#section-3.2.2).

I'll leave it out unless a bunch of folks thing it better in.

> For the query part, you should put in the following text (or an
> equivalent):
> 
> For compatibility with IRIs, non-ASCII characters in the query part MUST
> be encoded as UTF-8, and the resulting octets MUST be %-encoded (see
> http://tools.ietf.org/html/rfc3986#section-2.1).

Added that,
Thanks,
S

> 
> My understanding is that there's no danger for getting non-ASCII
> characters in the path part, and that fragments are separate anyway.
> 
> Regards,   Martin.
> 
> 

From duerst@it.aoyama.ac.jp  Tue Jun 12 06:05:12 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAA2721F8597 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 06:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.668
X-Spam-Level: 
X-Spam-Status: No, score=-100.668 tagged_above=-999 required=5 tests=[AWL=1.122, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 KBkh32sDJKkl for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 06:05:11 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 8A6AA21F8592 for <ietf@ietf.org>; Tue, 12 Jun 2012 06:05:09 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5CD4xLe024984 for <ietf@ietf.org>; Tue, 12 Jun 2012 22:04:59 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 7682_2b93_36910a48_b48f_11e1_96d0_001d096c5782; Tue, 12 Jun 2012 22:04:58 +0900
Received: from [IPv6:::1] ([133.2.210.1]:52423) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D17C9> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 12 Jun 2012 22:05:02 +0900
Message-ID: <4FD73E76.7050105@it.aoyama.ac.jp>
Date: Tue, 12 Jun 2012 22:04:54 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: APPSDIR review of draft-farrell-decade-ni-07, major design issue (one or two URI schemes)
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD712E8.7010506@cs.tcd.ie>
In-Reply-To: <4FD712E8.7010506@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Graham Klyne <GK@ninebynine.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 13:05:12 -0000

Hello Stephen,

On 2012/06/12 18:59, Stephen Farrell wrote:
>
> Hi Martin,
>
> On 06/12/2012 10:13 AM, "Martin J. DÃ¼rst" wrote:
>> Hello Stephen,
>>
>> This mail responds to your points on the main technical issue that I
>> have identified.
>>
>> On 2012/06/05 20:11, Stephen Farrell wrote:
>>
>>> On 06/05/2012 10:42 AM, "Martin J. DÃ¼rst" wrote:
>>>> Hello everybody,

>>> Major design issue:
>>>>
>>>> The draft defines two schemes, which differ only slightly, and mostly
>>>> just gratuitously (see also editorial issues).
>>>> These are the ni: and the nih: scheme. As far as I understand, they
>>>> differ as follows:
>>>>                                       ni:                nih:
>>>> authority:                          optional           disallowed
>>>> ascii-compatible encoding:          base64url          base16
>>>> check digit:                        disallowed         optional
>>>> query part:                         optional           disallowed
>>>> decimal presentation of algorithm:  disallowed         possible
>
> I'll note in passing that the two schemes differ in all those
> respects. You may disagree with our design, but basically you're
> showing that the two differ in pretty much all possible ways
> other than that both include a hash value.
>
>>>>
>>>> The usability of URIs is strongly influenced by the number of different
>>>> schemes, with the smaller a number, the better. As a somewhat made-up
>>>> example, if the original URIs had been separated into httph: for HTML
>>>> pages and httpi: for images, or any other arbitrary subdivision that one
>>>> can envision, that would have hurt the growth and extensibility of the
>>>> Web. Creating new URI schemes is occasionally necessary, and the ideas
>>>> that lead to this draft definitely seem to warrant a new scheme (*), but
>>>> there's no reason for two schemes.
>>>> [(*) I know people who would claim the the .well-formed http/https thing
>>>> is completely sufficient, no new scheme needed at all.]
>>>>
>>>> More specifically, if the original URIs had been separated into httpm:
>>>> (for machines) and httph: (for humans), the Web for sure wouldn't have
>>>> grown at the speed it did (and does) grow. In practice, there are huge
>>>> differences in human 'speakability' for URIs (and IRIs, for that
>>>> matter); compare e.g. http://google.com with
>>>> http://www.google.co.jp/#sclient=psy-ab&hl=en&site=&source=hp&q=hash&oq=hash&aq=f&aqi=g4&aql=
>>>>
>>>>
>>>> (which I have significantly shortened to hopefully eliminate potential
>>>> privacy issues), or compare the average mailto: URI with the average
>>>> data: URI. However, what's important is that there never has been a
>>>> strong dividing line between machine-only and human-only URIs or
>>>> schemes, the division has always been very gradual. Short and mainly
>>>> human-oriented URIs have of course been handled by machines, and on the
>>>> other hand, very long URIs have been spoken when really necessary.
>>>> "Speakability" has been maintained to some extent by scheme designers,
>>>> and to some extent by "survival of the fittest" (URIs that weren't very
>>>> speakable (or spellable/memorizable/guessable/...), and their Web sites,
>>>> might just die out slowly).
>>>>
>>>> It should also be noted that the resistance against multiple URI schemes
>>>> may have been low because there are so many different ways to express
>>>> hashes in the draft anyway, and one more (the nih: section is the last
>>>> one before the examples section) didn't seem like much of a deal
>>>> anymore. But when it comes to URIs, one less is a lot better than one
>>>> more.
>>>>
>>>> In the above ni:/nih: distinction, nih: seems to have been added as an
>>>> afterthought after realizing that reading an ni: URI aloud over the
>>>> phone may be somewhat suboptimal because there is a need for repeated
>>>> "upper case" - "lower case" (sure very quickly shortened to "upper" -
>>>> "lower" and then to "up" - "low" or something similar). It is not a bad
>>>> idea to try to make sure that IETF technology, and URIs in particular,
>>>> are accessible to people with certain kinds of dislexya. (There are
>>>> indeed people who have tremendous difficulties with distinguishing
>>>> upper- and lower-case letters, and this may or may not be connected with
>>>> other aspects of dislexya.) It is however totally unclear to this
>>>> reviewer why this has to lead to two different URI schemes with other
>>>> gratuitous differences.
>>>>
>>>> Finding a solution is rather easy (of course, other solutions may also
>>>> be possible): Merge the schemes, so that authority, check digit, and
>>>> query part are all optional (an authority part and/or a query part may
>>>> very well be very useful in human communication, and a check digit won't
>>>> hurt when transmitted electronically) and the decimal presentation of
>>>> the algorithm is always allowed, and use base32
>>>> (http://tools.ietf.org/html/rfc4648) as the encoding. This leads to a
>>>> 16.6% less efficient encoding of the value part of the ni: URI, but
>>>> given that other URI-related encodings, e.g. the %-encoding resulting
>>>> when converting an IRI to an URI, are much less efficient, and that URI
>>>> infrastructure these days can handle URIs with more than 1000 bytes,
>>>> this should not be a serious problem. Also, there's a separate binary
>>>> format (section 6) that is more compact already.
>>>
>>> I strongly disagree with merging ni&   nih. Though that clearly
>>> could be done, it would be an error.
>>>
>>> There was no such comment on the uri-review list and the designated
>>> expert was happy. That review was IMO the time for such comments
>>> and second-guessing the designated expert at this stage seems
>>> contrary to the registration requirements. So process-wise I
>>> think your main comment is late.
>>
>> First, if IETF Last Call is too late to make serious technical comments
>> on drafts, then I think we have to rename it to IETF Too-Late Call.
>>
>> Second, designated experts are there to check for minimum requirements
>> for a registration, and to give advice as they see fit (and have time).
>> I'm myself a designated expert on "Character Sets", and I have
>> definitely in the past approved, and would again in the future approve,
>> registrations for stuff on which I would complain strongly if the
>> question was "is this a good technical solution".
>>
>> Graham Klyne, the designated expert for URI scheme registrations, has
>> confirmed offline that he does not see his role as "expert reviewer" as
>> judging the technical merit of a URI scheme proposal.
>
> While that's fair enough. Its also fair to note that there was
> discussion of the this document on the uri-review list but this
> aspect was not raised at all. That list is called "uri-review"
> and from its archives it does seem to frequently do more than
> just check the paperwork (including quite a few mails from you:-).

Oh well. I'm not sure how familiar you are with the IETF :-), but it's 
basically all a volunteer organization. So even more than in an 
organization where people are getting paid, some things happen to get a 
lot of attention and other things happen to get less attention than 
maybe they would deserve. And most people have their day jobs, and 
occasionally miss a mail or two, or even a few more. And many people are 
on many lists and just skim them until something catches their eye, and 
ignore many threads. If you don't do anything like this and survive, I'd 
like to know how :-).

So the uri-review list, like any other IETF (or other) list, can get 
excited about stuff, sometimes for good reasons, or can just ignore some 
aspects of some proposal. It's unfortunate, but it's something we have 
to live with. You can't ask everybody on that list to take the same 
amount of time to look at all the proposals that e.g. a Security 
Directorate or Apps Area Directorate reviewer is using.


>>> But in any case, I also think you're wrong technically in this>>  case.
>>
>> Let's see. I hope we agree that we should come to a conclusion on this
>> issue on technical merits, rather than on process details.
>
> Sure.

Good.

>>> nih *is* intended for a corner case,
>
> Let me emphasise the above. nih is not intended to be used
> broadly, nor often. If you want a hash-based URI scheme for
> users to speak that is for broad frequent use then I think
> you are free to try design one. But nih is not that and is
> not intended to be that.

Then, at the barest minimum, don't sell it as that. The only thing the 
draft essentially says is "use this if you want to read/speak it". Now 
you are saying "don't use that for users to speak, unless in specific 
corner cases", but you still haven't told me or the readers of the draft 
what these corner cases are, and why the SHOULD/MUST not use it 
otherwise even if they might think it makes sense.

The second, more general advice is of course to not design URIs for 
corner cases, because URIs work best if they are used widely. (There may 
be a very tiny chance that your case is different, but even after 
reading all your mail, I haven't understood that.)


> (And I'm not sure such a beast
> could really be done well.)

Speaking 256 or so bits of random data aloud is in no way going to be 
terribly easy :-).


>>> where humans need to speak these
>>> URIs and was added as a direct result of requirements from the core
>>> WG and not as an afterthought. ni URIs are not intended for that
>>> and so there really are IMO different requirements, (esp. e.g.
>>> checkdigit) that are best met with different schemes.
>>
>> I agree that the value of a checkdigit is very limited for communication
>
> s/very limited/useless/
>
>> among machines (and for communication among humans with the help of
>> machines, such as in the case of email).
>>
>> On the other hand, I can't understand why (even assuming we needed a
>> separate scheme) there is no authority and no query part on nih.
>
> The main intent of nih is to allow entry of something that
> confirms something else (e.g. a public key) that is already
> present.

At least a little bit of information about the "use case", but this just 
leads to more questions:

Do you need an URI for that? (Isn't that what people are supposed to do 
with fingerprints these days?)

How/where would a user input that URI e.g. in a browser?

Would copy/paste from an email or a Web page be fine?

Would entry be needed, or could it just be checked? (I understand that 
forcing a user to enter the data is way safer than believing her that a 
check was made, but then it's also way more tedious, and many users will 
just switch to different software.)

Can ni: URIs also be used for the same purpose? If not, why not (they 
essentially contain the same information)?

What about other URIs, starting e.g. with http:?

I won't claim that this list of questions is exhaustive, but I hope it's 
a good start.


> There is no need for an authority for that, for
> the use-cases we have. We could speculate about other potential
> use-cases but we'd rather not speculate like that when there's
> no need to.

There was a lot of stuff that we take for granted today that Tim 
Berners-Lee didn't speculate when he designed the first URI schemes. But 
if he had designed these schemes with only corner cases in mind, he 
wouldn't have invented the Web :-). (sorry about an analogy again)


>> For the authority, I'd assume that it would be as useful when the URI is
>> transmitted e.g. over the phone as when it is transmitted e.g. over email.
>
> We don't have a use for that that I know about.

Do you mean the "over the phone" part or the authority part? (assuming 
the later below)

> I agree
> it could be done, but then I think it'd also impact on
> usability, which will be pretty crap no matter what's
> done.

Reading "example.com" or some equivalent domain name in addition to a 
long hex string shouldn't really make matters much worse.

> But making usability worse also seems wrong.

My understanding is that there are some cases where things will be found 
with authority, but not without. If that's right, then I'm sure users 
will prefer to find what they are looking for, after aurally 
transmitting 256 or thereabout bits, even at the cost of an additional 
domain name (and a few slashes), which are the easiest parts to get 
across the line quickly and correctly.


> Not
> having an authority also seems to work fine for PGP keys

That the lack of authority works in some cases is perfectly okay. But 
it's not an argument for not allowing authority for cases (even those 
that maybe you're not seeing yet) where it is or will be useful.


> and the lack of an authority does get rid of some threats,
> if the nih URI is used for something security-sensitive.

Which would mean that ni: has these threats, yes? Where are they 
described? I don't remember seeing them in the security section.


>> For the query part, there are already various ideas and proposals
>> floating around,
>
> Where? If you mean draft-hallambaker-decade-params

Correct.

> then
> we (the authors of that) don't think those are useful for
> nih names.

Why not? And what if others think they would be useful?


>> and at least some of them would be of interest for when
>> the URI is transmitted e.g. over the phone. Also, even if we currently
>> didn't have any actual proposals for query parameters, I think it would
>> be a very bad idea to exclude them a priori for transmission e.g. over
>> the phone.
>
> I disagree that there is any "very bad idea" here.
>
>>> Merging ni/nih would also add more complexity for no benefit,
>>> which would be a bad idea.
>>
>> Can you please explain what kind of complexity would have to be added?
>
> I think its obvious actually. In your table above you highlighted
> 5 ways in which ni and nih differ. Merging all those yields loads
> of combinations, which makes for complexity.

Well, if your implementation is a big switch with 32 cases, one for each 
combination, with no code sharing, then indeed you get complexity. But I 
hope we agree that that's very bad design, and totally unnecessary. It's 
very straightforward to go through the components one-by-one and deal 
with them (hint: I'd start with the check digit).

On the other hand, the complexity you get from query parameters is 
potentially huge, because, contrary to the basic syntax, we don't know 
for sure what combinations of parameters people will dream up, and how 
these will interact.


>> In terms of specification, merging the two schemes doesn't seem to be
>> difficult or complex at all. Also, in terms of implementation, the only
>> additions to the ni: scheme that become necessary are the check digit
>> and the expression of the "suite id" as a decimal. It's very difficult
>> for me to imagine that this would add significant complexity to an
>> implementation; if code for nih: exists, that can mostly just be moved
>> over.
>
> Feel free to look at our code. (With the caveat that I'm a crap
> programmer so close your eyes a bit when you look at the 'C' code:-)
>
>>> Your analogy about httpm/h may appear reasonable, but it is always
>>> unreasonable to draw conclusions from analogies. It is also unwise
>>> to reason from counterfactuals, which we'd also be doing if we
>>> accepted your argument. So I find that speculation utterly useless
>>> to be honest.
>>
>> It is definitely unreasonable to draw conclusions from analogies *only*.
>
> I only saw the analogy. What in your httpm/h argument is not
> couterfactual analogy?

Do you claim that it's not true that URIs are often transferred 
electronically, often transferred on paper, and often spoken, and that 
these sets for which these activities happen overlap? If you think that 
has to be different for ni:/nih:, you have to convince me, not the other 
way round.


>> But if you think that the httpm/h analogy is wrong, and that ni/nih is
>> different, could you please explain *what* is different?
>
> We have real use cases for ni and nih and we think they differ.
> I'd be repeating myself to say why again.

You're still very vague on these "real use cases". Confirmation of PGP 
keys by speaking the URI aloud seems to be your main/only use case for 
nih:. But I'm only guessing, because you haven't really explained this yet.

>>> In this case, we are dealing with different requirements so this
>>> should stay as-is.
>>
>> If "different requirements" is your main (or only) real argument,
>
> That would be a valid argument.

It would only be a valid argument if these are requirements that can't 
be consolidated.


>> could
>> you at least explain exactly how they are different?
>
> I did that above. Asking for an "exact" explanation seems
> like asking the same thing again.

Here are the pieces of text from above that I can at least in some way 
link to actual requirements:
"nih is not intended to be used broadly, nor often."
"The main intent of nih is to allow entry of something that
confirms something else (e.g. a public key) that is already
present."

Is that all there is? Or did I miss something? Maybe it would help this 
discussion if you wrote a few paragraphs of free-standing text 
explaining the use cases (and restrictions, and reasons for these) for 
both schemes. It may turn out to be a valid addition to the document at 
the very minimum. (I'm not asking for an independent "use cases and 
requirements" draft :-)


>> Just that one
>> requirement came from the core WG and others from other WGs or other
>> parties doesn't help me to understand how the actual requirements
>> differ. (Please note that even if the requirements differ, that doesn't
>> mean that we need different technology to address them.)
>
> Perhaps not. But that was the design choice we made and its
> a valid one.

Given the more than 20 years of experience we have of how URIs are 
handled on the Web and around it, I have very good reasons to strongly 
doubt that this is a good design choice.


>> Why do you say that ni: URIs are not intended for humans to speak?
>
> So phone me up and say this:
>
>    ni:///sha-256;UyaQV-Ev4rdLoHyJJWCi11OHfrYv9E1aGQAlMO2X_-Q

So apart from the upper/lower problem, would the equivalent nih: URI be 
any better?

>> What
>> am I supposed to do if I got an ni: URI in a mail message and call you
>> on the phone to tell you about that?
>
> Not my problem actually, but I guess most people might
> say "remember that mail you sent me with all that gobbledygook
> nonsense - what the hell was that about?" :-)

I think "tell you about it" should have been "speak it out to you".


>>   If I want to send somebody the
>> information in an ni: URI by mail, should I use only the ni: version or
>> only the nih: version, or both, if I can't exclude that the recipient
>> may want to relay this information via voice?
>
> You can try either and let me know what works. This seems like
> a very artificial use-case for ni.

Why artificial? Long URIs get spoken over the phone once in a while. And 
I really don't understand why this is "very artificial" for ni:, but 
"indispensable" for nih:.


>>> Finally, we have (some, early,) running code that matches the
>>> current draft and that ought also count for something
>>
>> How much?
>
> Feel free to go look and see. [1] I've not counted lines of
> code, but we have c, python, ruby and clojure library
> implementations and some apps and other bits and pieces.
>
>     [1] http://sourceforge.net/projects/netinf/
>
>> The boiler plate on every ID is pretty clear that they are not
>> set in stone. Also, the changes needed to merge the two schemes are not
>> rocket science, quite to the contrary. (I herewith volunteer to fix the
>> Ruby version, just to show)
>
> I didn't say our code is set in stone. I said that running code
> counts.
>
> I didn't say a merge would require rocket science.

It somehow sounded like this.

> I said it'd be
> a bad idea and would produce a worse result.

Can you substantiate that? The discussion on use cases is still open, 
and the argument with all the 32 combinations also didn't fly.

>>> when compared
>>> to a change that would be a gratuitous dis-improvement
>>
>> In what sense would merging the two schemes be a dis-improvement? Can
>> you please explain?
>
> I believe I did that above.

Very marginally, perhaps. More information would definitely help.

>>> based it
>>> seems upon dubious argument
>>
>> If you think that my arguments are dubious, please explain exactly why.
>
> I believe I did that above. (To be clear: not all your argument is
> dubious

Thanks for some encouragement :-).


> but the httph/m part is IMO.)

I'm sorry that I started out with that analogy, but I thought it would 
be easy to understand. You seem to be caught in the specific use/corner 
cases, but I'm trying to look at the long term big picture.


>>> that is also offered at the wrong
>>> point in the process.
>>
>> See above. If there's something wrong with IETF Last Call, or with the
>> fact that the Apps Area Directorate does reviews (which I don't think),
>> then that should be addressed separately. For this discussion, I hope we
>> can concentrate on technical issues.
>
> Right. But let's not ignore the fact that the uri-review
> list had sight of this at the end of April.

[If you keep insisting, why don't you check your MUA and look at all the 
messages I sent on the draft. You may be surprised, but I seriously hope 
you will stop bringing up "uri-review" again.]


> Bottom line - we have use-cases and a valid design and running
> code that as far as we know works and I see no reason to make
> the change you'd like, which would make thing worse IMO.

It may look like some more work in the short time, but it will make 
things more general and create more potential for the future.


Regards,    Martin.

From dworley@avaya.com  Tue Jun 12 07:04:25 2012
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1120F21F85B8 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 07:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.099
X-Spam-Level: 
X-Spam-Status: No, score=-104.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 X8XZ+Rzs08NI for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 07:04:24 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 0F41621F85AE for <ietf@ietf.org>; Tue, 12 Jun 2012 07:04:24 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAJJL10/GmAcF/2dsb2JhbABFEwEBtSKBB4IfEihRAQgNKUInBBsah2kLl3qEIpx4kFhgA5YxhGOKBoJ8
X-IronPort-AV: E=Sophos;i="4.77,397,1336363200"; d="scan'208";a="352308869"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 12 Jun 2012 10:01:49 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 12 Jun 2012 10:02:46 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 12 Jun 2012 10:04:19 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 12 Jun 2012 10:04:18 -0400
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
Thread-Topic: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
Thread-Index: AQHNSKGW//NxWPLhvkiovEghRhUVLQ==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0B76@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 14:04:25 -0000

Having never heard of this proposal before, I found the concept
interesting, but the exposition in the draft was difficult to grasp in
certain places.  I believe that it is because the text assumes that
the reader already knows the underlying theory of what the process is
intended to accomplish.

For example, in section 3, the syntax of the "ni" URI scheme is
spelled out with admirable clarity and exactness, including:

   Digest Value [Required]  The digest value MUST be encoded using the
      base64url [RFC4648] encoding.

Hmmm, "the digest value"...  The digest value *of what*?

Considering the previous section 2, it seems that there is some
implicit string, which when hashed by the algorithm specified in the
"Digest Algorithm" part, produces the "Digest Value".  And given the
discussion, it seems that this string is an *input* to the process of
generating an ni URI, and that the ni URI is really a way of encoding
this string.  The string itself is specified by some external reality,
and seems to be expected to represent or specify some object in some
way, and thus the ni URI is a "name" for that object.

So far, so good, although it would have been better if this was
spelled out explicitly.

Going back to section 2 for a moment, there is:

   When the input to the hash algorithm is a public key value, as may be
   used by various security protocols, the hash SHOULD be calculated
   over the public key in an X.509 SubjectPublicKeyInfo structure
   (Section 4.1 of [RFC5280]).

I can see what this means, but it's not very clear.  A better way to
write it would be:

    When the input is intended to be a public key value, as may be
    used by various security protocols, the input to the hash SHOULD
    be an X.509 SubjectPublicKeyInfo structure (Section 4.1 of
    [RFC5280]) containing the public key rather than the public key
    value itself.

In section 8 is:

   The following ni URI references the text "Hello World!" (without the
   quotes, being 12 characters), [...]

But the term "references" seems not to have been used in this sense
before in the draft.  More clear would be:

   The following ni URI is generated from the string "Hello World!"
   (without the quotes, being 12 characters), [...]

Unfortunately, the example is somewhat incongruous, as "Hello World!"
is not obviously a name or reference to any object.  Thus while it
still is clear how it can be input to the processes that are described
in the draft, it doesn't seem to be a conceptually typical example.

Then we get to:

   Given the SubjectPublicKeyInfo in Figure 6 we derive the names shown
   in Figure 7 for this value.

I can't tell what this means. What is "this value"?  Is it the
immediately preceding URI
(http://example.com/.well-known/ni/sha-256/f4OxZX_x_FO5LcGBSKHWXfwtSx-j1nco=
St3SABJtkGk)?
In what manner does the "given" SubjectPublicKeyInfo affect the names?

If the input value was meant to be the SubjectPublicKeyInfo itself,
the sentence would not add "this value", which strongly suggests a
*different* value than the one mentioned just before in the same
sentence.  Rather, one would say:

   We derive the names shown in Figure 7 from the SubjectPublicKeyInfo
   in Figure 6.

Dale

From stephen.farrell@cs.tcd.ie  Tue Jun 12 07:09:36 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 567C021F852E for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 07:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.232
X-Spam-Level: 
X-Spam-Status: No, score=-103.232 tagged_above=-999 required=5 tests=[AWL=1.067, BAYES_00=-2.599, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 MzBIg+8eNTkh for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 07:09:34 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 0136821F8597 for <ietf@ietf.org>; Tue, 12 Jun 2012 07:09:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 3A361171800; Tue, 12 Jun 2012 15:09:33 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339510171; bh=e055XXCxMEpuDa R8G7IPt05SRfV61y0WgseRSErZdO8=; b=4hGPolLheCPB6XApxrNakJPsL+rEC4 MhroePS1FXig/cfnrjI0YPuNxnqYispjwWh2tLrcUlRKzGc34WUScfOOwxkapKcp KB8Erv+MICWLv5fj4AiK8+s3qgX+OP+/aPawkyLXfYXOgjlOiVFSlhsuVPY0Yl4R fqc+sDALNQ0zj6bRQLS3nfSbnAhyty+L1gBOlqwWAMz0V0NOnylgZniBZWX8KF7l 9ZgZJMKMNGtnDlAByKweIirytWBhE5TKSIdfBAme0XPFJvi+93GlE4GMb469pqAa /ygPYPrHJrWz+s6th5thzIY4c5WUhFRy/gb0E8DSoA235DsywAhuNE3Q==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 777T-9r-ElAD; Tue, 12 Jun 2012 15:09:31 +0100 (IST)
Received: from [IPv6:2001:770:10:203:f0bb:fb89:d865:2639] (unknown [IPv6:2001:770:10:203:f0bb:fb89:d865:2639]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id D00281714E5; Tue, 12 Jun 2012 15:09:23 +0100 (IST)
Message-ID: <4FD74D94.4020408@cs.tcd.ie>
Date: Tue, 12 Jun 2012 15:09:24 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: APPSDIR review of draft-farrell-decade-ni-07, major design issue (one or two URI schemes)
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD712E8.7010506@cs.tcd.ie> <4FD73E76.7050105@it.aoyama.ac.jp>
In-Reply-To: <4FD73E76.7050105@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Graham Klyne <GK@ninebynine.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 14:09:36 -0000

Martin,

I honestly don't think this exchange is going
anywhere new so I've not provided blow-by-blow
answers below.

We (the authors) think ni and nih are better
kept separate because the use-cases and
requirements differ. And that's what the
limited amount of running code does.

I think I've explained that, and I have no
intention whatsoever of getting into the "write
up the use-cases and requirements" game that
too-often happens in the IETF when its neither
needed nor productive. (Regardless of whether
the game is played with I-Ds or email.)
Sometimes that is useful, but not here IMO.

You disagree, which is fine. You think ni and nih
should be merged because they don't differ
sufficiently, (I think), and (I guess) because
you think that new URI schemes are more expensive
than what you see as the differences between
these two proposed schemes warrant.

I suggest we see if anyone else chimes in on
this aspect (so far nobody has, despite a quite
active IETF LC:-) and if not leave it to the
sponsoring AD to figure out what, if anything,
needs doing at the end of IETF LC.

Cheers,
S.

PS: Many thanks for all the other good comments,
though we disagree on this one, you've helped
make the draft better for sure.


On 06/12/2012 02:04 PM, "Martin J. Dürst" wrote:
> Hello Stephen,
> 
> On 2012/06/12 18:59, Stephen Farrell wrote:
>>
>> Hi Martin,
>>
>> On 06/12/2012 10:13 AM, "Martin J. Dürst" wrote:
>>> Hello Stephen,
>>>
>>> This mail responds to your points on the main technical issue that I
>>> have identified.
>>>
>>> On 2012/06/05 20:11, Stephen Farrell wrote:
>>>
>>>> On 06/05/2012 10:42 AM, "Martin J. Dürst" wrote:
>>>>> Hello everybody,
> 
>>>> Major design issue:
>>>>>
>>>>> The draft defines two schemes, which differ only slightly, and mostly
>>>>> just gratuitously (see also editorial issues).
>>>>> These are the ni: and the nih: scheme. As far as I understand, they
>>>>> differ as follows:
>>>>>                                       ni:                nih:
>>>>> authority:                          optional           disallowed
>>>>> ascii-compatible encoding:          base64url          base16
>>>>> check digit:                        disallowed         optional
>>>>> query part:                         optional           disallowed
>>>>> decimal presentation of algorithm:  disallowed         possible
>>
>> I'll note in passing that the two schemes differ in all those
>> respects. You may disagree with our design, but basically you're
>> showing that the two differ in pretty much all possible ways
>> other than that both include a hash value.
>>
>>>>>
>>>>> The usability of URIs is strongly influenced by the number of
>>>>> different
>>>>> schemes, with the smaller a number, the better. As a somewhat made-up
>>>>> example, if the original URIs had been separated into httph: for HTML
>>>>> pages and httpi: for images, or any other arbitrary subdivision
>>>>> that one
>>>>> can envision, that would have hurt the growth and extensibility of the
>>>>> Web. Creating new URI schemes is occasionally necessary, and the ideas
>>>>> that lead to this draft definitely seem to warrant a new scheme
>>>>> (*), but
>>>>> there's no reason for two schemes.
>>>>> [(*) I know people who would claim the the .well-formed http/https
>>>>> thing
>>>>> is completely sufficient, no new scheme needed at all.]
>>>>>
>>>>> More specifically, if the original URIs had been separated into httpm:
>>>>> (for machines) and httph: (for humans), the Web for sure wouldn't have
>>>>> grown at the speed it did (and does) grow. In practice, there are huge
>>>>> differences in human 'speakability' for URIs (and IRIs, for that
>>>>> matter); compare e.g. http://google.com with
>>>>> http://www.google.co.jp/#sclient=psy-ab&hl=en&site=&source=hp&q=hash&oq=hash&aq=f&aqi=g4&aql=
>>>>>
>>>>>
>>>>>
>>>>> (which I have significantly shortened to hopefully eliminate potential
>>>>> privacy issues), or compare the average mailto: URI with the average
>>>>> data: URI. However, what's important is that there never has been a
>>>>> strong dividing line between machine-only and human-only URIs or
>>>>> schemes, the division has always been very gradual. Short and mainly
>>>>> human-oriented URIs have of course been handled by machines, and on
>>>>> the
>>>>> other hand, very long URIs have been spoken when really necessary.
>>>>> "Speakability" has been maintained to some extent by scheme designers,
>>>>> and to some extent by "survival of the fittest" (URIs that weren't
>>>>> very
>>>>> speakable (or spellable/memorizable/guessable/...), and their Web
>>>>> sites,
>>>>> might just die out slowly).
>>>>>
>>>>> It should also be noted that the resistance against multiple URI
>>>>> schemes
>>>>> may have been low because there are so many different ways to express
>>>>> hashes in the draft anyway, and one more (the nih: section is the last
>>>>> one before the examples section) didn't seem like much of a deal
>>>>> anymore. But when it comes to URIs, one less is a lot better than one
>>>>> more.
>>>>>
>>>>> In the above ni:/nih: distinction, nih: seems to have been added as an
>>>>> afterthought after realizing that reading an ni: URI aloud over the
>>>>> phone may be somewhat suboptimal because there is a need for repeated
>>>>> "upper case" - "lower case" (sure very quickly shortened to "upper" -
>>>>> "lower" and then to "up" - "low" or something similar). It is not a
>>>>> bad
>>>>> idea to try to make sure that IETF technology, and URIs in particular,
>>>>> are accessible to people with certain kinds of dislexya. (There are
>>>>> indeed people who have tremendous difficulties with distinguishing
>>>>> upper- and lower-case letters, and this may or may not be connected
>>>>> with
>>>>> other aspects of dislexya.) It is however totally unclear to this
>>>>> reviewer why this has to lead to two different URI schemes with other
>>>>> gratuitous differences.
>>>>>
>>>>> Finding a solution is rather easy (of course, other solutions may also
>>>>> be possible): Merge the schemes, so that authority, check digit, and
>>>>> query part are all optional (an authority part and/or a query part may
>>>>> very well be very useful in human communication, and a check digit
>>>>> won't
>>>>> hurt when transmitted electronically) and the decimal presentation of
>>>>> the algorithm is always allowed, and use base32
>>>>> (http://tools.ietf.org/html/rfc4648) as the encoding. This leads to a
>>>>> 16.6% less efficient encoding of the value part of the ni: URI, but
>>>>> given that other URI-related encodings, e.g. the %-encoding resulting
>>>>> when converting an IRI to an URI, are much less efficient, and that
>>>>> URI
>>>>> infrastructure these days can handle URIs with more than 1000 bytes,
>>>>> this should not be a serious problem. Also, there's a separate binary
>>>>> format (section 6) that is more compact already.
>>>>
>>>> I strongly disagree with merging ni&   nih. Though that clearly
>>>> could be done, it would be an error.
>>>>
>>>> There was no such comment on the uri-review list and the designated
>>>> expert was happy. That review was IMO the time for such comments
>>>> and second-guessing the designated expert at this stage seems
>>>> contrary to the registration requirements. So process-wise I
>>>> think your main comment is late.
>>>
>>> First, if IETF Last Call is too late to make serious technical comments
>>> on drafts, then I think we have to rename it to IETF Too-Late Call.
>>>
>>> Second, designated experts are there to check for minimum requirements
>>> for a registration, and to give advice as they see fit (and have time).
>>> I'm myself a designated expert on "Character Sets", and I have
>>> definitely in the past approved, and would again in the future approve,
>>> registrations for stuff on which I would complain strongly if the
>>> question was "is this a good technical solution".
>>>
>>> Graham Klyne, the designated expert for URI scheme registrations, has
>>> confirmed offline that he does not see his role as "expert reviewer" as
>>> judging the technical merit of a URI scheme proposal.
>>
>> While that's fair enough. Its also fair to note that there was
>> discussion of the this document on the uri-review list but this
>> aspect was not raised at all. That list is called "uri-review"
>> and from its archives it does seem to frequently do more than
>> just check the paperwork (including quite a few mails from you:-).
> 
> Oh well. I'm not sure how familiar you are with the IETF :-), but it's
> basically all a volunteer organization. So even more than in an
> organization where people are getting paid, some things happen to get a
> lot of attention and other things happen to get less attention than
> maybe they would deserve. And most people have their day jobs, and
> occasionally miss a mail or two, or even a few more. And many people are
> on many lists and just skim them until something catches their eye, and
> ignore many threads. If you don't do anything like this and survive, I'd
> like to know how :-).
> 
> So the uri-review list, like any other IETF (or other) list, can get
> excited about stuff, sometimes for good reasons, or can just ignore some
> aspects of some proposal. It's unfortunate, but it's something we have
> to live with. You can't ask everybody on that list to take the same
> amount of time to look at all the proposals that e.g. a Security
> Directorate or Apps Area Directorate reviewer is using.
> 
> 
>>>> But in any case, I also think you're wrong technically in this>>  case.
>>>
>>> Let's see. I hope we agree that we should come to a conclusion on this
>>> issue on technical merits, rather than on process details.
>>
>> Sure.
> 
> Good.
> 
>>>> nih *is* intended for a corner case,
>>
>> Let me emphasise the above. nih is not intended to be used
>> broadly, nor often. If you want a hash-based URI scheme for
>> users to speak that is for broad frequent use then I think
>> you are free to try design one. But nih is not that and is
>> not intended to be that.
> 
> Then, at the barest minimum, don't sell it as that. The only thing the
> draft essentially says is "use this if you want to read/speak it". Now
> you are saying "don't use that for users to speak, unless in specific
> corner cases", but you still haven't told me or the readers of the draft
> what these corner cases are, and why the SHOULD/MUST not use it
> otherwise even if they might think it makes sense.
> 
> The second, more general advice is of course to not design URIs for
> corner cases, because URIs work best if they are used widely. (There may
> be a very tiny chance that your case is different, but even after
> reading all your mail, I haven't understood that.)
> 
> 
>> (And I'm not sure such a beast
>> could really be done well.)
> 
> Speaking 256 or so bits of random data aloud is in no way going to be
> terribly easy :-).
> 
> 
>>>> where humans need to speak these
>>>> URIs and was added as a direct result of requirements from the core
>>>> WG and not as an afterthought. ni URIs are not intended for that
>>>> and so there really are IMO different requirements, (esp. e.g.
>>>> checkdigit) that are best met with different schemes.
>>>
>>> I agree that the value of a checkdigit is very limited for communication
>>
>> s/very limited/useless/
>>
>>> among machines (and for communication among humans with the help of
>>> machines, such as in the case of email).
>>>
>>> On the other hand, I can't understand why (even assuming we needed a
>>> separate scheme) there is no authority and no query part on nih.
>>
>> The main intent of nih is to allow entry of something that
>> confirms something else (e.g. a public key) that is already
>> present.
> 
> At least a little bit of information about the "use case", but this just
> leads to more questions:
> 
> Do you need an URI for that? (Isn't that what people are supposed to do
> with fingerprints these days?)
> 
> How/where would a user input that URI e.g. in a browser?
> 
> Would copy/paste from an email or a Web page be fine?
> 
> Would entry be needed, or could it just be checked? (I understand that
> forcing a user to enter the data is way safer than believing her that a
> check was made, but then it's also way more tedious, and many users will
> just switch to different software.)
> 
> Can ni: URIs also be used for the same purpose? If not, why not (they
> essentially contain the same information)?
> 
> What about other URIs, starting e.g. with http:?
> 
> I won't claim that this list of questions is exhaustive, but I hope it's
> a good start.
> 
> 
>> There is no need for an authority for that, for
>> the use-cases we have. We could speculate about other potential
>> use-cases but we'd rather not speculate like that when there's
>> no need to.
> 
> There was a lot of stuff that we take for granted today that Tim
> Berners-Lee didn't speculate when he designed the first URI schemes. But
> if he had designed these schemes with only corner cases in mind, he
> wouldn't have invented the Web :-). (sorry about an analogy again)
> 
> 
>>> For the authority, I'd assume that it would be as useful when the URI is
>>> transmitted e.g. over the phone as when it is transmitted e.g. over
>>> email.
>>
>> We don't have a use for that that I know about.
> 
> Do you mean the "over the phone" part or the authority part? (assuming
> the later below)
> 
>> I agree
>> it could be done, but then I think it'd also impact on
>> usability, which will be pretty crap no matter what's
>> done.
> 
> Reading "example.com" or some equivalent domain name in addition to a
> long hex string shouldn't really make matters much worse.
> 
>> But making usability worse also seems wrong.
> 
> My understanding is that there are some cases where things will be found
> with authority, but not without. If that's right, then I'm sure users
> will prefer to find what they are looking for, after aurally
> transmitting 256 or thereabout bits, even at the cost of an additional
> domain name (and a few slashes), which are the easiest parts to get
> across the line quickly and correctly.
> 
> 
>> Not
>> having an authority also seems to work fine for PGP keys
> 
> That the lack of authority works in some cases is perfectly okay. But
> it's not an argument for not allowing authority for cases (even those
> that maybe you're not seeing yet) where it is or will be useful.
> 
> 
>> and the lack of an authority does get rid of some threats,
>> if the nih URI is used for something security-sensitive.
> 
> Which would mean that ni: has these threats, yes? Where are they
> described? I don't remember seeing them in the security section.
> 
> 
>>> For the query part, there are already various ideas and proposals
>>> floating around,
>>
>> Where? If you mean draft-hallambaker-decade-params
> 
> Correct.
> 
>> then
>> we (the authors of that) don't think those are useful for
>> nih names.
> 
> Why not? And what if others think they would be useful?
> 
> 
>>> and at least some of them would be of interest for when
>>> the URI is transmitted e.g. over the phone. Also, even if we currently
>>> didn't have any actual proposals for query parameters, I think it would
>>> be a very bad idea to exclude them a priori for transmission e.g. over
>>> the phone.
>>
>> I disagree that there is any "very bad idea" here.
>>
>>>> Merging ni/nih would also add more complexity for no benefit,
>>>> which would be a bad idea.
>>>
>>> Can you please explain what kind of complexity would have to be added?
>>
>> I think its obvious actually. In your table above you highlighted
>> 5 ways in which ni and nih differ. Merging all those yields loads
>> of combinations, which makes for complexity.
> 
> Well, if your implementation is a big switch with 32 cases, one for each
> combination, with no code sharing, then indeed you get complexity. But I
> hope we agree that that's very bad design, and totally unnecessary. It's
> very straightforward to go through the components one-by-one and deal
> with them (hint: I'd start with the check digit).
> 
> On the other hand, the complexity you get from query parameters is
> potentially huge, because, contrary to the basic syntax, we don't know
> for sure what combinations of parameters people will dream up, and how
> these will interact.
> 
> 
>>> In terms of specification, merging the two schemes doesn't seem to be
>>> difficult or complex at all. Also, in terms of implementation, the only
>>> additions to the ni: scheme that become necessary are the check digit
>>> and the expression of the "suite id" as a decimal. It's very difficult
>>> for me to imagine that this would add significant complexity to an
>>> implementation; if code for nih: exists, that can mostly just be moved
>>> over.
>>
>> Feel free to look at our code. (With the caveat that I'm a crap
>> programmer so close your eyes a bit when you look at the 'C' code:-)
>>
>>>> Your analogy about httpm/h may appear reasonable, but it is always
>>>> unreasonable to draw conclusions from analogies. It is also unwise
>>>> to reason from counterfactuals, which we'd also be doing if we
>>>> accepted your argument. So I find that speculation utterly useless
>>>> to be honest.
>>>
>>> It is definitely unreasonable to draw conclusions from analogies *only*.
>>
>> I only saw the analogy. What in your httpm/h argument is not
>> couterfactual analogy?
> 
> Do you claim that it's not true that URIs are often transferred
> electronically, often transferred on paper, and often spoken, and that
> these sets for which these activities happen overlap? If you think that
> has to be different for ni:/nih:, you have to convince me, not the other
> way round.
> 
> 
>>> But if you think that the httpm/h analogy is wrong, and that ni/nih is
>>> different, could you please explain *what* is different?
>>
>> We have real use cases for ni and nih and we think they differ.
>> I'd be repeating myself to say why again.
> 
> You're still very vague on these "real use cases". Confirmation of PGP
> keys by speaking the URI aloud seems to be your main/only use case for
> nih:. But I'm only guessing, because you haven't really explained this yet.
> 
>>>> In this case, we are dealing with different requirements so this
>>>> should stay as-is.
>>>
>>> If "different requirements" is your main (or only) real argument,
>>
>> That would be a valid argument.
> 
> It would only be a valid argument if these are requirements that can't
> be consolidated.
> 
> 
>>> could
>>> you at least explain exactly how they are different?
>>
>> I did that above. Asking for an "exact" explanation seems
>> like asking the same thing again.
> 
> Here are the pieces of text from above that I can at least in some way
> link to actual requirements:
> "nih is not intended to be used broadly, nor often."
> "The main intent of nih is to allow entry of something that
> confirms something else (e.g. a public key) that is already
> present."
> 
> Is that all there is? Or did I miss something? Maybe it would help this
> discussion if you wrote a few paragraphs of free-standing text
> explaining the use cases (and restrictions, and reasons for these) for
> both schemes. It may turn out to be a valid addition to the document at
> the very minimum. (I'm not asking for an independent "use cases and
> requirements" draft :-)
> 
> 
>>> Just that one
>>> requirement came from the core WG and others from other WGs or other
>>> parties doesn't help me to understand how the actual requirements
>>> differ. (Please note that even if the requirements differ, that doesn't
>>> mean that we need different technology to address them.)
>>
>> Perhaps not. But that was the design choice we made and its
>> a valid one.
> 
> Given the more than 20 years of experience we have of how URIs are
> handled on the Web and around it, I have very good reasons to strongly
> doubt that this is a good design choice.
> 
> 
>>> Why do you say that ni: URIs are not intended for humans to speak?
>>
>> So phone me up and say this:
>>
>>    ni:///sha-256;UyaQV-Ev4rdLoHyJJWCi11OHfrYv9E1aGQAlMO2X_-Q
> 
> So apart from the upper/lower problem, would the equivalent nih: URI be
> any better?
> 
>>> What
>>> am I supposed to do if I got an ni: URI in a mail message and call you
>>> on the phone to tell you about that?
>>
>> Not my problem actually, but I guess most people might
>> say "remember that mail you sent me with all that gobbledygook
>> nonsense - what the hell was that about?" :-)
> 
> I think "tell you about it" should have been "speak it out to you".
> 
> 
>>>   If I want to send somebody the
>>> information in an ni: URI by mail, should I use only the ni: version or
>>> only the nih: version, or both, if I can't exclude that the recipient
>>> may want to relay this information via voice?
>>
>> You can try either and let me know what works. This seems like
>> a very artificial use-case for ni.
> 
> Why artificial? Long URIs get spoken over the phone once in a while. And
> I really don't understand why this is "very artificial" for ni:, but
> "indispensable" for nih:.
> 
> 
>>>> Finally, we have (some, early,) running code that matches the
>>>> current draft and that ought also count for something
>>>
>>> How much?
>>
>> Feel free to go look and see. [1] I've not counted lines of
>> code, but we have c, python, ruby and clojure library
>> implementations and some apps and other bits and pieces.
>>
>>     [1] http://sourceforge.net/projects/netinf/
>>
>>> The boiler plate on every ID is pretty clear that they are not
>>> set in stone. Also, the changes needed to merge the two schemes are not
>>> rocket science, quite to the contrary. (I herewith volunteer to fix the
>>> Ruby version, just to show)
>>
>> I didn't say our code is set in stone. I said that running code
>> counts.
>>
>> I didn't say a merge would require rocket science.
> 
> It somehow sounded like this.
> 
>> I said it'd be
>> a bad idea and would produce a worse result.
> 
> Can you substantiate that? The discussion on use cases is still open,
> and the argument with all the 32 combinations also didn't fly.
> 
>>>> when compared
>>>> to a change that would be a gratuitous dis-improvement
>>>
>>> In what sense would merging the two schemes be a dis-improvement? Can
>>> you please explain?
>>
>> I believe I did that above.
> 
> Very marginally, perhaps. More information would definitely help.
> 
>>>> based it
>>>> seems upon dubious argument
>>>
>>> If you think that my arguments are dubious, please explain exactly why.
>>
>> I believe I did that above. (To be clear: not all your argument is
>> dubious
> 
> Thanks for some encouragement :-).
> 
> 
>> but the httph/m part is IMO.)
> 
> I'm sorry that I started out with that analogy, but I thought it would
> be easy to understand. You seem to be caught in the specific use/corner
> cases, but I'm trying to look at the long term big picture.
> 
> 
>>>> that is also offered at the wrong
>>>> point in the process.
>>>
>>> See above. If there's something wrong with IETF Last Call, or with the
>>> fact that the Apps Area Directorate does reviews (which I don't think),
>>> then that should be addressed separately. For this discussion, I hope we
>>> can concentrate on technical issues.
>>
>> Right. But let's not ignore the fact that the uri-review
>> list had sight of this at the end of April.
> 
> [If you keep insisting, why don't you check your MUA and look at all the
> messages I sent on the draft. You may be surprised, but I seriously hope
> you will stop bringing up "uri-review" again.]
> 
> 
>> Bottom line - we have use-cases and a valid design and running
>> code that as far as we know works and I see no reason to make
>> the change you'd like, which would make thing worse IMO.
> 
> It may look like some more work in the short time, but it will make
> things more general and create more potential for the future.
> 
> 
> Regards,    Martin.
> 
> 

From stpeter@stpeter.im  Tue Jun 12 07:19:41 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 942F021F860F for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 07:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 c+YnO77SzO2H for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 07:19:41 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 102C821F85CD for <ietf@ietf.org>; Tue, 12 Jun 2012 07:19:41 -0700 (PDT)
Received: from [192.168.0.7] (unknown [216.17.179.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 515654005A; Tue, 12 Jun 2012 08:36:49 -0600 (MDT)
Message-ID: <4FD74FFC.3050905@stpeter.im>
Date: Tue, 12 Jun 2012 08:19:40 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Subject: registries and designated experts (was: Re: APPSDIR review of draft-farrell-decade-ni-07,  major design issue (one or two URI schemes))
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp>
In-Reply-To: <4FD7083A.6080502@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: Graham Klyne <GK@ninebynine.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 14:19:41 -0000

[change of subject]

On 6/12/12 3:13 AM, "Martin J. DÃ¼rst" wrote:
> 
> On 2012/06/05 20:11, Stephen Farrell wrote:

<snip/>

>> I strongly disagree with merging ni&  nih. Though that clearly
>> could be done, it would be an error.
>>
>> There was no such comment on the uri-review list and the designated
>> expert was happy. That review was IMO the time for such comments
>> and second-guessing the designated expert at this stage seems
>> contrary to the registration requirements. So process-wise I
>> think your main comment is late.
> 
> First, if IETF Last Call is too late to make serious technical comments
> on drafts, then I think we have to rename it to IETF Too-Late Call.
> 
> Second, designated experts are there to check for minimum requirements
> for a registration, and to give advice as they see fit (and have time).
> I'm myself a designated expert on "Character Sets", and I have
> definitely in the past approved, and would again in the future approve,
> registrations for stuff on which I would complain strongly if the
> question was "is this a good technical solution".
> 
> Graham Klyne, the designated expert for URI scheme registrations, has
> confirmed offline that he does not see his role as "expert reviewer" as
> judging the technical merit of a URI scheme proposal.

By my reading, the "happiana" discussions [1] over the 12+ months have
led most participants to the conclusion that registration does not imply
standardization, and that it's not the role of the designated expert to
act as a gatekeeper with respect to the technical merits of the
technologies that trigger registration requests. It might be good to
have a wider discussion about the purpose of registries and the role of
designated experts, but IMHO it's not correct to conclude that a
technology is acceptable just because the designated expert didn't
object to the registrations related to that technology.

Peter

[1] https://www.ietf.org/mailman/listinfo/happiana





From stephen.farrell@cs.tcd.ie  Tue Jun 12 07:21:08 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76C7F21F865A for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 07:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 qBjmLdAeiIPZ for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 07:21:07 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 0259821F8658 for <ietf@ietf.org>; Tue, 12 Jun 2012 07:21:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 5C6C8171805; Tue, 12 Jun 2012 15:21:06 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339510865; bh=hRu9zfv3b99hzs iLcyBiT4eOu+YjyoiVomFWjtYE8hs=; b=hPi7zgl5Wx7lWyZszt8bRItPjzs0pb m8hvpPzhvJ76t8xd+JEyZPDwIvdEdWD9g3aZ0Z3xmF0wgJmZckqYZqSfA/9MxVnW NX6vyQymhiqhBqNtpHjtw7ra1jPluzujHPzaKQQ59HOZcTdkDTe8nUlFPl5mO3r3 VpoDPSBD3YRtjo0CowonT3GTNsQ2jV05Y+VbJ6rqAfatgVSYVrY+ynqC5O+Q+SPT 9C0QLt4I4ivCpO3++eN0fSqd79hQEcZA6kyfaDA98Wzsdek4xvXrLOsTWqm8Oir3 N8RgN4cRRqvNakXqIsu/Sj/C2fi4g9x48gr4V9u9n33h3RcRffnpes/A==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id nuAoFvgbG9Qr; Tue, 12 Jun 2012 15:21:05 +0100 (IST)
Received: from [IPv6:2001:770:10:203:f0bb:fb89:d865:2639] (unknown [IPv6:2001:770:10:203:f0bb:fb89:d865:2639]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id C6A6A171800; Tue, 12 Jun 2012 15:21:05 +0100 (IST)
Message-ID: <4FD75051.10702@cs.tcd.ie>
Date: Tue, 12 Jun 2012 15:21:05 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <CD5674C3CD99574EBA7432465FC13C1B22726A0B76@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0B76@DC-US1MBEX4.global.avaya.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 14:21:08 -0000

Hi Dale,

On 06/12/2012 03:04 PM, Worley, Dale R (Dale) wrote:
> Having never heard of this proposal before, I found the concept
> interesting, but the exposition in the draft was difficult to grasp in
> certain places.  I believe that it is because the text assumes that
> the reader already knows the underlying theory of what the process is
> intended to accomplish.

I'm not sure there's a theory:-)

> For example, in section 3, the syntax of the "ni" URI scheme is
> spelled out with admirable clarity and exactness, including:
> 
>    Digest Value [Required]  The digest value MUST be encoded using the
>       base64url [RFC4648] encoding.
> 
> Hmmm, "the digest value"...  The digest value *of what*?

The input to the digest is not defined by this draft, except
in the case of public keys. (See other comments wrt MIME &
Content Type as well.)

  "Other than in the above special case where public keys are used, we
   do not specify the hash function input here.  Other specifications
   are expected to define this."

> Considering the previous section 2, it seems that there is some
> implicit string, which when hashed by the algorithm specified in the
> "Digest Algorithm" part, produces the "Digest Value".  And given the
> discussion, it seems that this string is an *input* to the process of
> generating an ni URI, and that the ni URI is really a way of encoding
> this string.  The string itself is specified by some external reality,
> and seems to be expected to represent or specify some object in some
> way, and thus the ni URI is a "name" for that object.
> 
> So far, so good, although it would have been better if this was
> spelled out explicitly.
> 
> Going back to section 2 for a moment, there is:
> 
>    When the input to the hash algorithm is a public key value, as may be
>    used by various security protocols, the hash SHOULD be calculated
>    over the public key in an X.509 SubjectPublicKeyInfo structure
>    (Section 4.1 of [RFC5280]).
> 
> I can see what this means, but it's not very clear.  A better way to
> write it would be:
> 
>     When the input is intended to be a public key value, as may be
>     used by various security protocols, the input to the hash SHOULD
>     be an X.509 SubjectPublicKeyInfo structure (Section 4.1 of
>     [RFC5280]) containing the public key rather than the public key
>     value itself.

Have to say I prefer the existing text.

> 
> In section 8 is:
> 
>    The following ni URI references the text "Hello World!" (without the
>    quotes, being 12 characters), [...]
> 
> But the term "references" seems not to have been used in this sense
> before in the draft.  More clear would be:
> 
>    The following ni URI is generated from the string "Hello World!"
>    (without the quotes, being 12 characters), [...]

Ack. Thanks.

> 
> Unfortunately, the example is somewhat incongruous, as "Hello World!"
> is not obviously a name or reference to any object.  

In this case the object named is just those 12 characters.

> Thus while it
> still is clear how it can be input to the processes that are described
> in the draft, it doesn't seem to be a conceptually typical example.

Well, I could have said a file that contains "Hello World!" (12 chars:-)

But I don't think its much clearer, maybe less.

> Then we get to:
> 
>    Given the SubjectPublicKeyInfo in Figure 6 we derive the names shown
>    in Figure 7 for this value.
> 
> I can't tell what this means. What is "this value"?  Is it the
> immediately preceding URI
> (http://example.com/.well-known/ni/sha-256/f4OxZX_x_FO5LcGBSKHWXfwtSx-j1ncoSt3SABJtkGk)?
> In what manner does the "given" SubjectPublicKeyInfo affect the names?

No, the input value is the DER encoding of the SPKI as stated earlier.
I guess the following is a little more correct so I've changed it to:

   Given the DER-encoded SubjectPublicKeyInfo in Figure 6 we derive
   the names shown in Figure 7 for this value.

> If the input value was meant to be the SubjectPublicKeyInfo itself,
> the sentence would not add "this value", which strongly suggests a
> *different* value than the one mentioned just before in the same
> sentence.  Rather, one would say:
> 
>    We derive the names shown in Figure 7 from the SubjectPublicKeyInfo
>    in Figure 6.

I don't get the difference to be honest.

Cheers,
S.

> 
> Dale
> 
> 

From stbryant@cisco.com  Tue Jun 12 07:25:38 2012
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C331F21F85C7; Tue, 12 Jun 2012 07:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 2Sc7O9l0O+Am; Tue, 12 Jun 2012 07:25:36 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 0BEFC21F85AE; Tue, 12 Jun 2012 07:25:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=3140; q=dns/txt; s=iport; t=1339511136; x=1340720736; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=WOGT0lESNND4R+zquSAfl5kfhD9AHxG7YiFg/doMqKU=; b=Tzn8RXdQqdCc6RTjtN03PfVft/t/CKHxKwUjkJ+YiHUbazMgmcl+ZqAu lZa+zr4iFU75QxtFtf0BueSpvvItmNLd/SXKVHT+Hmk+iw4za2XOk1mqQ gH6PkbqWx8aHIXe9oaVaTmgg2iFb5i80nhS5M88l4KJx94cXSVebCpaVr U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EACxQ10+Q/khM/2dsb2JhbABFtTiBB4IYAQEBBBIBAiMvBwoBDAQcAwECAQkWBAsJAwIBAgE7AggGDQEFAgEBHodpmTKDRxCcGIsnhhEDlR+OFYEEYoJh
X-IronPort-AV: E=Sophos;i="4.75,758,1330905600";  d="scan'208";a="5694672"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 12 Jun 2012 14:25:34 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q5CEPYZw026352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Jun 2012 14:25:34 GMT
Received: from dhcp-bdlk10-data-vlan300-64-103-106-111.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q5CEPYkH020306; Tue, 12 Jun 2012 15:25:34 +0100 (BST)
Message-ID: <4FD7515E.3000101@cisco.com>
Date: Tue, 12 Jun 2012 15:25:34 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: "Ietf@ietf.org" <Ietf@ietf.org>
Subject: Fwd: Re: [Idr] Last Call: <draft-ietf-idr-rfc4893bis-06.txt> (BGP Support for	Four-octet AS Number Space) to Proposed Standard
References: <20120612135455.GC18025@diehard.n-r-g.com>
In-Reply-To: <20120612135455.GC18025@diehard.n-r-g.com>
X-Forwarded-Message-Id: <20120612135455.GC18025@diehard.n-r-g.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: idr mailing list <idr@ietf.org>, "idr-chairs@tools.ietf.org" <idr-chairs@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 14:25:38 -0000

FYI

Copying to IETF list as this is an IETF LC

Stewart

-------- Original Message --------
Subject: 	Re: [Idr] Last Call: (BGP Support for Four-octet AS Number 
Space) to Proposed Standard
Date: 	Tue, 12 Jun 2012 15:54:55 +0200
From: 	Claudio Jeker <cjeker@diehard.n-r-g.com>
To: 	Stewart Bryant <stbryant@cisco.com>
CC: 	<idr@ietf.org>



On Tue, Jun 12, 2012 at 11:30:11AM +0100, Stewart Bryant wrote:
> On 01/06/2012 23:00, Claudio Jeker wrote:
> >On Fri, Jun 01, 2012 at 11:54:44AM -0700, The IESG wrote:
> >>The IESG has received a request from the Inter-Domain Routing WG (idr) to
> >>consider the following document:
> >>- 'BGP Support for Four-octet AS Number Space'
> >>   <draft-ietf-idr-rfc4893bis-06.txt> as Proposed Standard
> >>
> >>The IESG plans to make a decision in the next few weeks, and solicits
> >>final comments on this action. Please send substantive comments to the
> >>ietf@ietf.org mailing lists by 2012-06-15. Exceptionally, comments may be
> >>sent to iesg@ietf.org instead. In either case, please retain the
> >>beginning of the Subject line to allow automated sorting.
> >>
> >>Abstract
> >>
> >>
> >>    The Autonomous System (AS) number is encoded as a two-octet entity in
> >>    the base BGP specification. This document describes extensions to BGP
> >>    to carry the Autonomous System numbers as four-octet entities.  This
> >>    document obsoletes RFC 4893.
> >>
> >Just for the sake of clarity, OpenBGPD will not do the following:
> >
> >    In addition, the path segment types AS_CONFED_SEQUENCE and
> >    AS_CONFED_SET [RFC5065] MUST NOT be carried in the AS4_PATH attribute
> >    of an UPDATE message.  A NEW BGP speaker that receives these path
> >    segment types in the AS4_PATH attribute of an UPDATE message from an
> >    OLD BGP speaker MUST discard these path segments, adjust the relevant
> >    attribute fields accordingly, and continue processing the UPDATE
> >    message.  This case SHOULD be logged locally for analysis.
> >
> >There is no point to do this fiddeling instead we will treat this like any
> >other parse error of AS4_PATH.
> >
> Claudio
>
> Since this is in last call, I have to ask whether you have objection
> to the publication
> of the above text, or have any proposed text changes?

I see no reason to enforce AS_CONFED_SEQUENCE and AS_CONFED_SET stripping
on all AS4 implementations. It forces bgp implementations that don't have
confederation support to strip out something that will cause an error in
the regular path and for those systems ignoring the AS4_PATH attribute
is perfectly fine. I do not understand how a workaround needs to be a
MUST for something that is a MUST NOT at the same time? Why MUST we
workaround something that MUST NOT appear? Why do we need to add extra
code that is hard to test and maybe cause for further errors because it
modifies attributes in very uncommon way?

I propose to remove that paragraph entierly since it does only add
complexity to the protocol for no reason and therefor is only a source of
errors without any benefit.
-- 
:wq Claudio





From dhc@dcrocker.net  Tue Jun 12 07:56:04 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C11321F86FA for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 07:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Rw4d6zjZE-MB for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 07:56:03 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CF32421F86F9 for <ietf@ietf.org>; Tue, 12 Jun 2012 07:56:03 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q5CEu2u2022757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 12 Jun 2012 07:56:02 -0700
Message-ID: <4FD75881.3080102@dcrocker.net>
Date: Tue, 12 Jun 2012 07:56:01 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: registries and designated experts
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im>
In-Reply-To: <4FD74FFC.3050905@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 12 Jun 2012 07:56:03 -0700 (PDT)
Cc: Graham Klyne <GK@ninebynine.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 14:56:04 -0000

On 6/12/2012 7:19 AM, Peter Saint-Andre wrote:
> it's not the role of the designated expert to
> act as a gatekeeper with respect to the technical merits of the
> technologies that trigger registration requests. It might be good to
> have a wider discussion about the purpose of registries and the role of
> designated experts, but IMHO it's not correct to conclude that a
> technology is acceptable just because the designated expert didn't
> object to the registrations related to that technology.


It's almost inevitable that many designated experts will, in fact, act 
as gatekeepers.  For example the distinction between "won't do damage" 
vs. "looks like excellent engineering" is more subtle in practice than 
one might think.  Especially absent very precise specification of review 
criteria and absent actual training of the reviewers.

While, yes, protocol specs that define the registry and review of its 
entries are supposed to provide the necessary details that do the 
distinction, I believe such texts do not get deep review for 
interpretive robustness.  That is, I doubt they are bullet-proofed 
against the vagaries of differerent readers who might be doing the 
reviews or writing text for them.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From abdussalambaryun@gmail.com  Tue Jun 12 04:09:29 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7291821F8670 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 04:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 siFaBM2buEQV for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 04:09:28 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id DFCE521F866C for <ietf@ietf.org>; Tue, 12 Jun 2012 04:09:27 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so3236166vcq.31 for <ietf@ietf.org>; Tue, 12 Jun 2012 04:09:27 -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=P4xD3BcGwpIQ+q0xDwA+Lisz9IvAl21f3OJFAJFkUzI=; b=H3JHF2eKSHyqxXmKJ02zvvLtQu1GgcPNTlFpFkQE1VVSrMK3pA56aMeOjrkBv43myn ZMFFlxFm0EMt3R5IgBrwHqOb7gsbBGwDesmuv+QWvMGG6oiQxVxxSWil1743dZpUckNW ugpEsubDYrw4rIDFWnfYaet/CNGToTA7D+cE/Gjr/5NdpF/Bk8QIKQu4lXlxgzys9sTk qRO12edcMZVYfZuimJ2m6zeNWuveH5+evYvv183rF/R+sc+jsov1R6Udd+NU4OwvPJei 9eBCUk2+Xlm9uMVcm6D3oHAl/jgdcQU/2aYgRPOJy0G959OxCkIRYxP7EFOW1i6dfKP2 NW9Q==
MIME-Version: 1.0
Received: by 10.52.65.145 with SMTP id x17mr11913057vds.117.1339499367329; Tue, 12 Jun 2012 04:09:27 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Tue, 12 Jun 2012 04:09:26 -0700 (PDT)
In-Reply-To: <20120611200903.460881A0A5@ld9781.wdf.sap.corp>
References: <CADnDZ8_PoshoJu61hm=qmhCAwViKBS_7gXf8M_zAfeE8Q=0ONw@mail.gmail.com> <20120611200903.460881A0A5@ld9781.wdf.sap.corp>
Date: Tue, 12 Jun 2012 13:09:26 +0200
Message-ID: <CADnDZ8_JdNMzDoK6tdExVeweik35Q4HcR3FNcUZL+tZ0an0UTA@mail.gmail.com>
Subject: Re: Discussions in IETF WGs
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: mrex@sap.com
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Tue, 12 Jun 2012 08:07:10 -0700
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 11:09:29 -0000

Hi Martin,

I thank you for your help and comments, it will help me for future.

comments in line:

On 6/11/12, Martin Rex <mrex@sap.com> wrote:
>
> There is no substiantial difference between old discussions and recent
> discussions.  Referencing an argument from an earlier discussion rather
> than repeating it is often an improvement with a significant potential to
> actually save time, and zero risk to waste time (compared to repeating
> the exact same previous arguments in a new message).
>

I agree with you, but only if the reference was pointed by date or
subject, so the all readers can follow the current discussion and
reference. also if the it was copied from the history (if short
discussion) forward to the current it will be useful, but overall
mentioning the subject/date of discussion is important.

>>
>> We should *reference* mostly RFCs in our discussion, because RFCs are
>> correct resource.
>
> If RFCs were correct, we would neither need an Errata process, nor
> maturity levels, nor -bis documents.
>
> "RFCs are correct" is a bold and dangerous presumption.  Many RFCs
> are vague or even ambigous, and they may contain numerous implications
> that are non-obvious to a number of readers, and sometimes non-obvious
> to implementors and document authors).

I just mentioned that to compare RFC with discussion list. In your
refering if the RFC maybe vague and it is the product of the
discussions, so what about the discussion as a reference.

>
> All that can be said about standard track RFCs, is that they're the result
> of the IETF consensus process.  And the primary focus of the IETF consensus
> process is to resolve dissent (technical or procedural objections),
> _not_ correctness.  Some level of confidence about correctness can be
> obtained
> by creating independent implementations and demonstrate that they interop
> on the implemented features, but results are mixed, and most interop
> tests are lacking (test only a fraction of the features and only a fraction
> of the implementations in the installed base, and rarely "border cases"
> of unusual encodings).
>

IMO the RFC is result of both; WG discussions first, and then
consensus process. Regarding confidence issue I agree with you,

>
> -Martin
>

Best regards
Abdussalam
==========

From barryleiba.mailing.lists@gmail.com  Tue Jun 12 08:07:56 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9661C21F8690 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 08:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level: 
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 TqHMByMFbNGQ for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 08:07:56 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id B27B821F8681 for <ietf@ietf.org>; Tue, 12 Jun 2012 08:07:55 -0700 (PDT)
Received: by lagv3 with SMTP id v3so5339602lag.31 for <ietf@ietf.org>; Tue, 12 Jun 2012 08:07:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=cWdz+RJjxmkVQADk42OStpNuxOpJQUeGMbggr84gMAM=; b=M89Tn0n9ToP50k+hEMiKG4Z/W/IKPu7nW56ZPZ6QqtcpyyRO5BxsetkAUH83BDhR7h pnDI7HegA9oQvEZEXkkcYGDMU9vXZ/jFuNs2Xwbea+N1nQZh4405J1k/BQHAhiVK7JZb PdJRanEaWsL9nq77GBXrmsa/9i2dZG4mVdbji3102HbxpJQrZSRjfZp11L2TLBIPM/1X RfqjSjDOgOlysHuSMU2APSsj09D9XGiMa6fCN8usstZ4SGxzSbIpZZuCYNKphX7wzLP0 YGlmOXxyidL0v69/G+5/1/9OhjwNV3/hYRpB9Gud9FAVs/Rb/SQrDMZNCC6qTRHjq2eZ rZYA==
MIME-Version: 1.0
Received: by 10.112.36.130 with SMTP id q2mr4682233lbj.44.1339513674660; Tue, 12 Jun 2012 08:07:54 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.48.104 with HTTP; Tue, 12 Jun 2012 08:07:54 -0700 (PDT)
In-Reply-To: <4FD74FFC.3050905@stpeter.im>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im>
Date: Tue, 12 Jun 2012 17:07:54 +0200
X-Google-Sender-Auth: GAwItS6Y_7XriqUS4cNyMb1Bg8g
Message-ID: <CAC4RtVA9Nd7cO=a=f9U0H-3cFnEhqdhXVeWNcw=xjW3cinTUYA@mail.gmail.com>
Subject: Re: registries and designated experts (was: Re: APPSDIR review of draft-farrell-decade-ni-07, major design issue (one or two URI schemes))
From: Barry Leiba <barryleiba@computer.org>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=e0cb4efe32a2bff9f204c247d4c7
Cc: Graham Klyne <GK@ninebynine.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 15:07:56 -0000

--e0cb4efe32a2bff9f204c247d4c7
Content-Type: text/plain; charset=ISO-8859-1

Martin said:
> Second, designated experts are there to check for minimum requirements
> for a registration, and to give advice as they see fit (and have time).
> I'm myself a designated expert on "Character Sets", and I have
> definitely in the past approved, and would again in the future approve,
> registrations for stuff on which I would complain strongly if the
> question was "is this a good technical solution".

There's no one correct statement about what designated experts do, or are
supposed to do.  Some specs that create designated experts give more or
fewer instructions to the expert than others do.  Some give none at all.
 The desognated expert should be doing what the specification that defined
the registry said the expert should do, to the best of the expert's
interpretation.  That might involve more gatekeeping in some cases, and
less in others, and there's always an appeal path available.

It's my opinion that more specifications that create Expert Review or
Specification Required registries should be specifying what they expect
from the designated experts.

Barry

--e0cb4efe32a2bff9f204c247d4c7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Martin said:<br><span class=3D"Apple-style-span" style>&gt; Second, designa=
ted experts are there to check for minimum requirements<br>&gt; for a regis=
tration, and to give advice as they see fit (and have time).<br>&gt; I&#39;=
m myself a designated expert on &quot;Character Sets&quot;, and I have<br>
&gt; definitely in the past approved, and would again in the future approve=
,<br>&gt; registrations for stuff on which I would complain strongly if the=
<br>&gt; question was &quot;is this a good technical solution&quot;.</span>=
<div>
<span class=3D"Apple-style-span" style><br></span></div><div><span class=3D=
"Apple-style-span" style>There&#39;s no one correct statement about what de=
signated experts do, or are supposed to do. =A0Some specs that create desig=
nated experts give more or fewer instructions to the expert than others do.=
 =A0Some give none at all. =A0The desognated expert should be doing what th=
e specification that defined the registry said the expert should do, to the=
 best of the expert&#39;s interpretation. =A0That might involve more gateke=
eping in some cases, and less in others, and there&#39;s always an appeal p=
ath available.</span></div>
<div><span class=3D"Apple-style-span" style><br></span></div><div><span cla=
ss=3D"Apple-style-span" style>It&#39;s my opinion that more specifications =
that create Expert Review or Specification Required registries should be sp=
ecifying what they expect from the designated experts.</span></div>
<div><span class=3D"Apple-style-span" style><br></span></div><div><span cla=
ss=3D"Apple-style-span" style>Barry<span></span></span></div>

--e0cb4efe32a2bff9f204c247d4c7--

From dworley@avaya.com  Tue Jun 12 08:42:24 2012
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB6D221F848A for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 08:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.849
X-Spam-Level: 
X-Spam-Status: No, score=-103.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 DALw3fGJYSY7 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 08:42:24 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 4426E21F86AB for <ietf@ietf.org>; Tue, 12 Jun 2012 08:42:23 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAD1i10+HCzI1/2dsb2JhbABFEwEBtSOBB4IYAQEBAQIBEig/BQsCAQgNCCEQMiUBAQQOBQgah2QFC5wtnH2QWGADljGEY4oGgnw
X-IronPort-AV: E=Sophos;i="4.77,397,1336363200"; d="scan'208";a="310643978"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 12 Jun 2012 11:40:49 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 12 Jun 2012 11:24:08 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Tue, 12 Jun 2012 11:42:10 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Tue, 12 Jun 2012 11:42:08 -0400
Subject: RE: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
Thread-Topic: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
Thread-Index: Ac1Ipp6c5UvoY7mlQ/usnwWx1+yIigACK6Ui
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0B7A@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B22726A0B76@DC-US1MBEX4.global.avaya.com>, <4FD75051.10702@cs.tcd.ie>
In-Reply-To: <4FD75051.10702@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 15:42:24 -0000

> From: Stephen Farrell [stephen.farrell@cs.tcd.ie]
>=20
> > For example, in section 3, the syntax of the "ni" URI scheme is
> > spelled out with admirable clarity and exactness, including:
> >
> >    Digest Value [Required]  The digest value MUST be encoded using the
> >       base64url [RFC4648] encoding.
> >
> > Hmmm, "the digest value"...  The digest value *of what*?
>=20
> The input to the digest is not defined by this draft, except
> in the case of public keys. (See other comments wrt MIME &
> Content Type as well.)

True... But what I am looking for is an explicit statement that the
process described in the draft *takes as input a string* which is not
defined in this draft.  Ideally, that fact should be stated separately
before the first description of any operation which is applied to the
string.  ("When defining a function, you must first state its
signature...")

> > Going back to section 2 for a moment, there is:
> >
> >    When the input to the hash algorithm is a public key value, as may b=
e
> >    used by various security protocols, the hash SHOULD be calculated
> >    over the public key in an X.509 SubjectPublicKeyInfo structure
> >    (Section 4.1 of [RFC5280]).
> >
> > I can see what this means, but it's not very clear.  A better way to
> > write it would be:
> >
> >     When the input is intended to be a public key value, as may be
> >     used by various security protocols, the input to the hash SHOULD
> >     be an X.509 SubjectPublicKeyInfo structure (Section 4.1 of
> >     [RFC5280]) containing the public key rather than the public key
> >     value itself.
>=20
> Have to say I prefer the existing text.

OK...  But I dislike the phrase "hash calculated over" -- a hash is a
function, it has an input, and it has an output.

> > Unfortunately, the example is somewhat incongruous, as "Hello World!"
> > is not obviously a name or reference to any object.
>=20
> In this case the object named is just those 12 characters.
>=20
> > Thus while it
> > still is clear how it can be input to the processes that are described
> > in the draft, it doesn't seem to be a conceptually typical example.
>=20
> Well, I could have said a file that contains "Hello World!" (12 chars:-)
>=20
> But I don't think its much clearer, maybe less.

It all depends on how one creates the input string from the object,
and there are a lot of ways of doing that (object contents, object
locator, etc.).  Properly speaking, that is out of scope of this
draft.  But the explanatory talks a great deal about "refering to an
object" without providing any details, which leads me assume that the
input strings are the locators of the objects in question, else they
would be references to the objects.

> > Then we get to:
> >
> >    Given the SubjectPublicKeyInfo in Figure 6 we derive the names shown
> >    in Figure 7 for this value.
> >
> > I can't tell what this means. What is "this value"?  Is it the
> > immediately preceding URI
> > (http://example.com/.well-known/ni/sha-256/f4OxZX_x_FO5LcGBSKHWXfwtSx-j=
1ncoSt3SABJtkGk)?
> > In what manner does the "given" SubjectPublicKeyInfo affect the names?
>=20
> No, the input value is the DER encoding of the SPKI as stated earlier.
> I guess the following is a little more correct so I've changed it to:
>=20
>    Given the DER-encoded SubjectPublicKeyInfo in Figure 6 we derive
>    the names shown in Figure 7 for this value.
>=20
> > If the input value was meant to be the SubjectPublicKeyInfo itself,
> > the sentence would not add "this value", which strongly suggests a
> > *different* value than the one mentioned just before in the same
> > sentence.  Rather, one would say:
> >
> >    We derive the names shown in Figure 7 from the SubjectPublicKeyInfo
> >    in Figure 6.
>=20
> I don't get the difference to be honest.

To my ear, the phrase "this value" in the sentence is strongly implied
*not* to be "the SubjectPublicKeyInfo".  It's hard to explain why, of
course, but it has something to do with the fact that if they were the
same, a separate noun phrase would not be needed, a simpler sentence
could be used to express the same meaning.

To avoid that effect, I would say:

    We derive the names shown in Figure 7 from the SubjectPublicKeyInfo
    in Figure 6.

or

    From the SubjectPublicKeyInfo in Figure 6, we derive the names
    shown in Figure 7.

Dale

From sm@resistor.net  Tue Jun 12 09:41:26 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C87821F859A for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 09:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lCkiO62df2-O for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 09:41:24 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9851221F8630 for <ietf@ietf.org>; Tue, 12 Jun 2012 09:41:24 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5CGfJUR001883; Tue, 12 Jun 2012 09:41:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1339519284; i=@resistor.net; bh=+3apbgsKNvTuPsVqa/7E+GNRpm9CY4CTVlX9qpz6I8w=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gTY7C3BmoUa5D/BDLiDPLfS3ozJyk/3mcfrlMuArLGmzkDV6RVM5P8FW7Ex1nwDeE TZNm1BR6nxz6q1dWvBeEbAkmRWEVXZEy/+FWtcYAasQI7jibRdxQtN7eBVYsBgJx4m gyl1eFfipmMcrVGmn2uenNA1QzTrliGZoeTHFjRQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1339519284; i=@resistor.net; bh=+3apbgsKNvTuPsVqa/7E+GNRpm9CY4CTVlX9qpz6I8w=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rEV89Cq4ygZrkBOwT6IzNAHwOLnXAJgZMoTCug0kC5x4fHtUmF3oEJ291Co4+HN1x 7vCry9n3u0GfMjN6GZ5BUAH4QhDFdweuICcrRO3Wk/YYlSgw/MvhOfkfCn5TZOQ8QU E/Vrrg2fSorRaKC5JspLHoPg2TaoRxYw6z6SPWt4=
Message-Id: <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 12 Jun 2012 09:31:16 -0700
To: Peter Saint-Andre <stpeter@stpeter.im>
From: SM <sm@resistor.net>
Subject: Re: registries and designated experts (was: Re: APPSDIR review of draft-farrell-decade-ni-07,  major design issue (one or two URI schemes))
In-Reply-To: <4FD74FFC.3050905@stpeter.im>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 16:41:26 -0000

Hi Peter,
At 07:19 12-06-2012, Peter Saint-Andre wrote:
>By my reading, the "happiana" discussions [1] over the 12+ months have
>led most participants to the conclusion that registration does not imply
>standardization, and that it's not the role of the designated expert to
>act as a gatekeeper with respect to the technical merits of the
>technologies that trigger registration requests. It might be good to
>have a wider discussion about the purpose of registries and the role of
>designated experts, but IMHO it's not correct to conclude that a
>technology is acceptable just because the designated expert didn't
>object to the registrations related to that technology.

I'll +1 the above.

In a recent review the path followed by the draft is Standards Action 
whereas the assignment policy is Expert Review.  Explaining to the 
authors that they should not use the assigned value isn't a 
worthwhile effort given that they have already been through the gate 
to get the value.  The Designated Expert did his job; that is to see 
that the requirements were met instead of acting as gatekeeper.  If 
you reject assignment requests people will find it simpler not to 
register the values.  If you accept the request people might consider 
that the specification is fine.

The reasons provided for managing a namespace are:

   - prevent the hoarding of or unnecessary wasting of values

   - provide a sanity check that the request actually makes sense

   - interoperability issues

The above is at odds with standardization.  The last reason does not 
apply for Expert review.

Regards,
-sm   


From brian.e.carpenter@gmail.com  Tue Jun 12 11:13:55 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF3B21F858A for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 11:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.252
X-Spam-Level: 
X-Spam-Status: No, score=-101.252 tagged_above=-999 required=5 tests=[AWL=0.439, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 GR1C47bFK523 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 11:13:55 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id D7E4621F8535 for <ietf@ietf.org>; Tue, 12 Jun 2012 11:13:54 -0700 (PDT)
Received: by eaaq13 with SMTP id q13so3184603eaa.31 for <ietf@ietf.org>; Tue, 12 Jun 2012 11:13:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/5lgSOI0puNECqdsYRcRd0l/AIE/q2D9jyEltkm5Z74=; b=LJmWbH74Qjt2CcVFtulNDw4C3h2GC+sEro/wh3PJW7CZCFThJjCcgU4kQpDIQzzHOd W7b07Yj8D/vnDdnmq2yAbR3Y0W/NDHUNz2Uga19cPUESYKTINa89+UAU5ch9WUC1+1UW 8knR+TvX5bE1PEtJEoQZiJxuteUultGHBfSxilQVVq5nDM7Ok1Cyy8eAQbrQHDPRofu1 QoD2lzkCoVKP/jKJjHX9DceBJNpj8VsqQShEwK26n/5WhT0YjKIjrpwTzYG/xupWS3xg jnGITBSST6rGI66koPeRgKcR9tgqpQ6Ndqf0MFOlgAtCt28OYJkBNTa5OGL8f1SVI+TG 8ghA==
Received: by 10.14.98.204 with SMTP id v52mr6901986eef.198.1339524833848; Tue, 12 Jun 2012 11:13:53 -0700 (PDT)
Received: from [192.168.1.67] (host-2-102-219-50.as13285.net. [2.102.219.50]) by mx.google.com with ESMTPS id h53sm67071459eea.1.2012.06.12.11.13.51 (version=SSLv3 cipher=OTHER); Tue, 12 Jun 2012 11:13:52 -0700 (PDT)
Message-ID: <4FD786DC.4090403@gmail.com>
Date: Tue, 12 Jun 2012 19:13:48 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: registries and designated experts
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie>	<4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net>
In-Reply-To: <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 18:13:55 -0000

On 2012-06-12 17:31, SM wrote:
> Hi Peter,
> At 07:19 12-06-2012, Peter Saint-Andre wrote:
>> By my reading, the "happiana" discussions [1] over the 12+ months have
>> led most participants to the conclusion that registration does not imply
>> standardization, and that it's not the role of the designated expert to
>> act as a gatekeeper with respect to the technical merits of the
>> technologies that trigger registration requests. It might be good to
>> have a wider discussion about the purpose of registries and the role of
>> designated experts, but IMHO it's not correct to conclude that a
>> technology is acceptable just because the designated expert didn't
>> object to the registrations related to that technology.
> 
> I'll +1 the above.
> 
> In a recent review the path followed by the draft is Standards Action
> whereas the assignment policy is Expert Review.  Explaining to the
> authors that they should not use the assigned value isn't a worthwhile
> effort given that they have already been through the gate to get the
> value.  The Designated Expert did his job; that is to see that the
> requirements were met instead of acting as gatekeeper.  If you reject
> assignment requests people will find it simpler not to register the
> values.  If you accept the request people might consider that the
> specification is fine.
> 
> The reasons provided for managing a namespace are:
> 
>   - prevent the hoarding of or unnecessary wasting of values
> 
>   - provide a sanity check that the request actually makes sense
> 
>   - interoperability issues
> 
> The above is at odds with standardization.  The last reason does not
> apply for Expert review.

I don't understand that statement. RFC 5226 says, in Section 2 about
"Why Management of a Namespace May Be Necessary":

"  A third, and perhaps most important, consideration concerns potential
   impact on the interoperability of unreviewed extensions."

One of the specific considerations for designated experts in section 3.3
is

"      - the extension would cause problems with existing deployed
        systems."

It seems clear that interoperability is a primary concern for any
expert review.

    Brian

From john-ietf@jck.com  Tue Jun 12 11:38:40 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EECF21F861F for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 11:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 abxdpJIjt5-m for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 11:38:39 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE6C21F85E7 for <ietf@ietf.org>; Tue, 12 Jun 2012 11:38:39 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SeVt0-000IXv-9s; Tue, 12 Jun 2012 14:32:14 -0400
Date: Tue, 12 Jun 2012 14:38:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, SM <sm@resistor.net>
Subject: Re: registries and designated experts
Message-ID: <B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com>
In-Reply-To: <4FD786DC.4090403@gmail.com>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie>	<4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net> <4FD786DC.4090403@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 18:38:40 -0000

--On Tuesday, June 12, 2012 19:13 +0100 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> The above is at odds with standardization.  The last reason
>> does not apply for Expert review.
> 
> I don't understand that statement. RFC 5226 says, in Section 2
> about "Why Management of a Namespace May Be Necessary":
> 
> "  A third, and perhaps most important, consideration concerns
> potential    impact on the interoperability of unreviewed
> extensions."
> 
> One of the specific considerations for designated experts in
> section 3.3 is
> 
> "      - the extension would cause problems with existing
> deployed         systems."
> 
> It seems clear that interoperability is a primary concern for
> any expert review.

Brian, Subramanian,

I've with Barry on this.  The details of the expectations of an
expert reviewer, including the thresholds for approval, should
be specified in whatever document sets up the particular
registry.  One size does not fit all; "Expert Review" is a
designation of a mechanism and not a set of criteria.

We should, IMO, do two things in this area:

(1) When a document specifies "Expert Review" for a registry, it
should be required to spell out the criteria the Expert is
supposed to use, at least to the degree that isn't obvious.  If
it doesn't, that should be grounds for "DISCUSS until fixed".

(2) If it turns out that an Expert for a particular registry is
not behaving as people expect, part of the process for getting
that fixed (or even complaining about it), should be to see if
the registry-creating documents are clear about procedures and
criteria.  If they are not, an effort to update those criteria
would be a useful way to discuss the issues and not the
individual expert.   Of course, Experts who knowingly violate
clear criteria should be summarily fired -- but I think we can
trust that to the IESG and note that it has almost never been
necessary.

     john



From sm@resistor.net  Tue Jun 12 13:19:03 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5CA321F861F for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 13:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level: 
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 fZ4iMcqkNuaE for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 13:19:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EDFB821F861D for <ietf@ietf.org>; Tue, 12 Jun 2012 13:19:00 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5CKIojL012163; Tue, 12 Jun 2012 13:18:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1339532336; i=@resistor.net; bh=s+3vNaALEozH3G6O1ANAM33E/K6+XMWeEsrZLLMfQM0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sIXV4agjeUUZNWIWQ2sj65+Hygdwj3MY16dRw+jZSHtYDshhvX9bLTxgMHrDZAY7g N3LGTkF+PBURlJu2Gcmhne5wGnA3AJa/j54qpO0McFJVN96GWPREm4I/5CQGW9pvaX Adg8UdFRezhbE6MnIB+1iciqsK7Fj6zrL+lpTgjk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1339532336; i=@resistor.net; bh=s+3vNaALEozH3G6O1ANAM33E/K6+XMWeEsrZLLMfQM0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=25KVUScRxGohS9JIDhg/kDRBldLzTgLZJTuR4qo8Fex0NJWTbHNxfv221G+tXs6SW IZpcnKjnCg3zPRidP4zztdruzE5xB6+nhsgH1a2vlAwp8ORs0Vjx2boYJZxsz8I7Ca Vueq2ccghnEVmsC4qR/sAclVe4PCVy75GyY0GPi4=
Message-Id: <6.2.5.6.2.20120612114107.091f2a80@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 12 Jun 2012 12:48:48 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: registries and designated experts
In-Reply-To: <4FD786DC.4090403@gmail.com>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net> <4FD786DC.4090403@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john-ietf@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 20:19:03 -0000

At 11:13 12-06-2012, Brian E Carpenter wrote:
>I don't understand that statement. RFC 5226 says, in Section 2 about
>"Why Management of a Namespace May Be Necessary":
>
>"  A third, and perhaps most important, consideration concerns potential
>    impact on the interoperability of unreviewed extensions."
>
>One of the specific considerations for designated experts in section 3.3
>is
>
>"      - the extension would cause problems with existing deployed
>         systems."
>
>It seems clear that interoperability is a primary concern for any
>expert review.

This gets you into the level of review (see Barry's comment).

The easiest policy is FSFC.  The next step is Expert Review which is 
supposed to have clear guidelines.  If you want interoperability, 
there's Specification Required.  It seems from the above that the 
argument is about avoiding problems with deployed systems.

At 11:38 12-06-2012, John C Klensin wrote:
>I've with Barry on this.  The details of the expectations of an
>expert reviewer, including the thresholds for approval, should
>be specified in whatever document sets up the particular
>registry.  One size does not fit all; "Expert Review" is a
>designation of a mechanism and not a set of criteria.

Agreed.

>We should, IMO, do two things in this area:
>
>(1) When a document specifies "Expert Review" for a registry, it
>should be required to spell out the criteria the Expert is
>supposed to use, at least to the degree that isn't obvious.  If
>it doesn't, that should be grounds for "DISCUSS until fixed".

I like the idea of spelling up the criteria.

>(2) If it turns out that an Expert for a particular registry is
>not behaving as people expect, part of the process for getting
>that fixed (or even complaining about it), should be to see if
>the registry-creating documents are clear about procedures and
>criteria.  If they are not, an effort to update those criteria
>would be a useful way to discuss the issues and not the
>individual expert.   Of course, Experts who knowingly violate
>clear criteria should be summarily fired -- but I think we can
>trust that to the IESG and note that it has almost never been
>necessary.

The people who come to the registry may not know much about the 
process.  I wonder if they are aware that there is a path to complain 
if there are not satisfied.  Even then, they may find it easier to 
walk away.  I don't think that the individual expert is the 
issue.  The better path is to have clear documentation (what you 
mentioned above) about the criteria so that the registrant can tell 
what the expectations are.  I'll add publication of the median time 
to process a request as information for the registrant.

Regards,
-sm 


From paul.hoffman@vpnc.org  Tue Jun 12 16:01:19 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B98C21F86D0 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 16:01:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 nFaBXlnjlPko for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 16:01:19 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id C52CF21F862F for <ietf@ietf.org>; Tue, 12 Jun 2012 16:01:18 -0700 (PDT)
Received: from [10.20.30.101] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q5CN1C9Z043541 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 12 Jun 2012 16:01:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: Publishing the Tao as a web page
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CC1638DA-817E-4F2C-BD29-5EFED6CFCAEF@vpnc.org>
Date: Tue, 12 Jun 2012 16:01:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <867BD23C-3581-4EDC-B4FF-973FEEBC253C@vpnc.org>
References: <CC1638DA-817E-4F2C-BD29-5EFED6CFCAEF@vpnc.org>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 23:01:19 -0000

Based on the earlier comments, I have revised the proposal. See =
draft-hoffman-tao-as-web-page-01, diffs at =
<tools.ietf.org/rfcdiff?url2=3Ddraft-hoffman-tao-as-web-page-01>.

--Paul Hoffman=

From randy@psg.com  Tue Jun 12 17:29:14 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4006D11E80AB for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 17:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[AWL=0.201,  BAYES_00=-2.599]
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 O9wl0ZIb0IH1 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 17:29:13 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id D63B811E80A5 for <ietf@ietf.org>; Tue, 12 Jun 2012 17:29:13 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SebST-000868-15; Wed, 13 Jun 2012 00:29:13 +0000
Date: Wed, 13 Jun 2012 09:29:11 +0900
Message-ID: <m2ipewdpgo.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: registries and designated experts
In-Reply-To: <B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net> <4FD786DC.4090403@gmail.com> <B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 00:29:14 -0000

> (1) When a document specifies "Expert Review" for a registry, it
> should be required to spell out the criteria the Expert is supposed to
> use, at least to the degree that isn't obvious.  If it doesn't, that
> should be grounds for "DISCUSS until fixed".

given our reknown abilities to predict and understand the future, this
is going to work out really well. </dripping sarcasm>

of course, any known non-obvious gotchas are worth passing along.  but
if they are non-obvious to the expert, then i suspect they will also
have been non-obvious to the doc author(s).

there may be a reason we have not automated this.

randy

From john-ietf@jck.com  Tue Jun 12 17:43:18 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0331611E809C for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 17:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 sprn+e5BXHWH for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 17:43:17 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0177B11E8098 for <ietf@ietf.org>; Tue, 12 Jun 2012 17:43:16 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SebZt-000Iwf-68; Tue, 12 Jun 2012 20:36:53 -0400
Date: Tue, 12 Jun 2012 20:43:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>
Subject: Re: registries and designated experts
Message-ID: <4F370B3BC882A87C8DE601A1@JcK-HP8200.jck.com>
In-Reply-To: <m2ipewdpgo.wl%randy@psg.com>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie>	<4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net> <4FD786DC.4090403@gmail.com> <B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com> <m2ipewdpgo.wl%randy@psg.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 00:43:18 -0000

--On Wednesday, June 13, 2012 09:29 +0900 Randy Bush
<randy@psg.com> wrote:

>> (1) When a document specifies "Expert Review" for a registry,
>> it should be required to spell out the criteria the Expert is
>> supposed to use, at least to the degree that isn't obvious.
>> If it doesn't, that should be grounds for "DISCUSS until
>> fixed".
> 
> given our reknown abilities to predict and understand the
> future, this is going to work out really well. </dripping
> sarcasm>
> 
> of course, any known non-obvious gotchas are worth passing
> along.  but if they are non-obvious to the expert, then i
> suspect they will also have been non-obvious to the doc
> author(s).
> 
> there may be a reason we have not automated this.

I agree with your basic point, but I wasn't suggesting
automation nor predicting the future.  I was suggesting that
giving the expert some guidance about what she is supposed to
look for (if that isn't obvious) and, e.g., whether the default
action on a marginal application is to accept or deny would be
of some help, at least to the expert's sanity.

Taking that comment as an example, I am _not_ suggesting that we
try to define the boundaries of "marginal application".  I also
trust the IESG to make reasonable appointments in at least the
vast majority of cases and assume that these will continue to be
"Expert Reviewers" rather than, e.g., "Robot Reviewers" or
"Moron Reviewers".

Contrary to some other comments, it is not at all clear to me
that having clear guidance will be of a lot of help to
applicants in predicting outcomes.  It would be nice if it
happened, but my main aspiration would be to reduce confusion on
the part of the expert about the expectations of the community.

Put differently, I don't much like oral traditions, especially
secret ones, in bodies like the IETF.  But I'm also in favor of
good sense as a primary guideline here.

    john


From derhoermi@gmx.net  Tue Jun 12 18:01:46 2012
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6909121F86DA for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 18:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 hykDTDw87inU for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 18:01:45 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 0CFDB21F8627 for <ietf@ietf.org>; Tue, 12 Jun 2012 18:01:44 -0700 (PDT)
Received: (qmail invoked by alias); 13 Jun 2012 01:01:43 -0000
Received: from dslb-094-223-202-247.pools.arcor-ip.net (EHLO HIVE) [94.223.202.247] by mail.gmx.net (mp033) with SMTP; 13 Jun 2012 03:01:43 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18EbPViAn4EsAIkVIuSAaaVwDu2wFfAN/F73JTqSi Sc8NASyGc0wToX
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: registries and designated experts (was: Re: APPSDIR review of draft-farrell-decade-ni-07, major design issue (one or two URI schemes))
Date: Wed, 13 Jun 2012 03:01:42 +0200
Message-ID: <ocoft7ho6dlqfuj2g96rccuht7ec2v1rlc@hive.bjoern.hoehrmann.de>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im>
In-Reply-To: <4FD74FFC.3050905@stpeter.im>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: Graham Klyne <GK@ninebynine.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 01:01:46 -0000

* Peter Saint-Andre wrote:
>By my reading, the "happiana" discussions [1] over the 12+ months have
>led most participants to the conclusion that registration does not imply
>standardization, and that it's not the role of the designated expert to
>act as a gatekeeper with respect to the technical merits of the
>technologies that trigger registration requests.

My impression is the same (though I do not agree with "led").

>It might be good to have a wider discussion about the purpose of
>registries and the role of designated experts, but IMHO it's not correct
>to conclude that a technology is acceptable just because the designated
>expert didn't object to the registrations related to that technology.

I would say that decisions by designated experts have no implications
outside the confines of their role and their discretion. We could give
experts the power to decide over "is acceptable", but when we do not,
then they do not have that power, and nobody should argue otherwise.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From derhoermi@gmx.net  Tue Jun 12 18:15:52 2012
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D849521F86EC for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 18:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 QOY8cFNAsrib for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 18:15:52 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 93B6721F86C8 for <ietf@ietf.org>; Tue, 12 Jun 2012 18:15:51 -0700 (PDT)
Received: (qmail invoked by alias); 13 Jun 2012 01:15:49 -0000
Received: from dslb-094-223-202-247.pools.arcor-ip.net (EHLO HIVE) [94.223.202.247] by mail.gmx.net (mp029) with SMTP; 13 Jun 2012 03:15:49 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+K12o4KByKTwFfic6HjrJ85eLZ9Ak/8SyYTmdrge OQZHRY0vkpEXtx
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: dcrocker@bbiw.net
Subject: Re: registries and designated experts
Date: Wed, 13 Jun 2012 03:15:54 +0200
Message-ID: <40qft756nm9l1g4q5asm5voc0jg2ng0pgl@hive.bjoern.hoehrmann.de>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <4FD75881.3080102@dcrocker.net>
In-Reply-To: <4FD75881.3080102@dcrocker.net>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>, Graham Klyne <GK@ninebynine.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 01:15:53 -0000

* Dave Crocker wrote:
>It's almost inevitable that many designated experts will, in fact, act 
>as gatekeepers.  For example the distinction between "won't do damage" 
>vs. "looks like excellent engineering" is more subtle in practice than 
>one might think.  Especially absent very precise specification of review 
>criteria and absent actual training of the reviewers.

It seems to me that if an expert reviewer thinks that something will do
notable harm, they should decline to make a decision and defer it to the
IETF at large; and any registration procedure that does not allow that
is broken. (Similarily, let's assume that something will do harm, but an
expert reviewer fails to see it, but others do: they should have the a-
bility to appeal expert reviewer decisions, so the matter can be brought
to the attention of more and possibly better qualified people; if that
is not an option, the process is broken; if, on the other hand, nobody
cares to use available procedures, including making a big fuss over it
in the regular press, or whatever, then it probably was not important e-
nough.)
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From randy@psg.com  Tue Jun 12 22:53:10 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ACA821F871D for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 22:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level: 
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599]
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 wiuHAdcmaPsR for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 22:53:10 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0670221F871C for <ietf@ietf.org>; Tue, 12 Jun 2012 22:53:09 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SegVw-0008mE-Ax; Wed, 13 Jun 2012 05:53:08 +0000
Date: Wed, 13 Jun 2012 14:53:07 +0900
Message-ID: <m21uljep18.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: registries and designated experts
In-Reply-To: <40qft756nm9l1g4q5asm5voc0jg2ng0pgl@hive.bjoern.hoehrmann.de>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <4FD75881.3080102@dcrocker.net> <40qft756nm9l1g4q5asm5voc0jg2ng0pgl@hive.bjoern.hoehrmann.de>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 05:53:10 -0000

> It seems to me that if an expert reviewer thinks that something will do
> notable harm, they should decline to make a decision and defer it to the
> IETF at large

so they are not an expert, they are a rubber stamp?  bs.

From duerst@it.aoyama.ac.jp  Tue Jun 12 23:29:05 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEBB221F8716 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 23:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.208
X-Spam-Level: 
X-Spam-Status: No, score=-99.208 tagged_above=-999 required=5 tests=[AWL=-0.618, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_31=0.6, J_CHICKENPOX_51=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 eT8aTgjUPo7V for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 23:29:05 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 313C621F8497 for <ietf@ietf.org>; Tue, 12 Jun 2012 23:29:04 -0700 (PDT)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5D6StTv002860 for <ietf@ietf.org>; Wed, 13 Jun 2012 15:28:55 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 432f_9d76_0d0ae7ce_b521_11e1_9956_001d096c566a; Wed, 13 Jun 2012 15:28:55 +0900
Received: from [IPv6:::1] ([133.2.210.1]:50545) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D1DD4> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 13 Jun 2012 15:28:59 +0900
Message-ID: <4FD83322.70203@it.aoyama.ac.jp>
Date: Wed, 13 Jun 2012 15:28:50 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com>	<CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>	<CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com>	<4FD29389.5060900@cs.tcd.ie> <tslboktwbzv.fsf@mit.edu> <4FD2AAB3.4010305@cs.tcd.ie> <4FD71D6A.9070101@it.aoyama.ac.jp> <4FD7231F.1050903@cs.tcd.ie>
In-Reply-To: <4FD7231F.1050903@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jonathan A Rees <rees@mumble.net>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 06:29:06 -0000

Hello Stephen,

On 2012/06/12 20:08, Stephen Farrell wrote:
>
> So would it work to add this:
>
> "
>     Note that relative ni URIs can occur, for example as shown in
>     Figure 5.  In such cases, user agents MUST construct the absolute URI
>     as they would in the case of an HTTP URL, that is, in the example
>     shown the absolute URI for "this third document" would be
>     "ni://example.com/sha-256-128;...".

This looks fine, except that it contains a MUST when it can just refer 
to RFC 3986. So I would suggest the following text:

    Note that relative ni URIs can occur. In such cases, the algorithm
    in Section 5 of RFC 3986 applies. As an example, in Figure 5, the
    absolute URI for "this third document" is
    "ni://example.com/sha-256-128;...".



>       <html>
>        <head>
>          <title>ni: relative URI test</title>
>          <base href="ni://example.com">
>        </head>
>
>        <body>
>          <p>Please check<a href="sha-256;f4OxZX...">this document</a>.
>            And<a href="sha-256;UyaQV...">this other document</a>.
>            And<a href="sha-256-128;...">this third document</a>.
>          </p>
>        </body>
>       </html>
>
>                  Figure 5: Example HTML with relative ni URI
>
> "
>
> Better suggestions welcome.
> Ta,

I tried to look "Ta" up on the Web, but there were just too many 
potential explanations. What are you using it for?


Regards,   Martin.

> S.

From brian.e.carpenter@gmail.com  Wed Jun 13 00:48:03 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D07B21F8642 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 00:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.292
X-Spam-Level: 
X-Spam-Status: No, score=-101.292 tagged_above=-999 required=5 tests=[AWL=0.399, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 e+RbO-y0M0WR for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 00:48:02 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4546821F8679 for <ietf@ietf.org>; Wed, 13 Jun 2012 00:48:02 -0700 (PDT)
Received: by eekd4 with SMTP id d4so80889eek.31 for <ietf@ietf.org>; Wed, 13 Jun 2012 00:48:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=/CVWIrFgLchXfgDhKLw8mYlxj1KCszQJGpqCDLysVGM=; b=fHy3gOiYDeQgkhJBtOl63pa+GxQmIJoqPIbzN8h8JTlWxLj+zjZeIICzIkIKgfHPE5 +lcVvjaNJIfHjwWWpUyd2PlHEQG2isRdWB59+CmYOOQWH9ysDHXGzS6r1VSrelHADOc0 V3eguehx1fBkSVChqevp7K4lUPGiALWpAjeoxkrZupBZvsFPOpIJsJzHMlMz1RYFOfs6 px3HW/npoQbl2o5zaB48MozunT2YYu6BkNOUaBZuU5sGAInZzAfFP+PVwmTVzWt41wTw QvSoqFGY/HRn860DIlYW4sQC3rRHWM/HLLyzpBvHZcPmT0gWBuoO8yruNoYPN8vFl1CJ QfsA==
Received: by 10.14.28.11 with SMTP id f11mr7705207eea.136.1339573681376; Wed, 13 Jun 2012 00:48:01 -0700 (PDT)
Received: from [192.168.1.66] (host-2-102-216-85.as13285.net. [2.102.216.85]) by mx.google.com with ESMTPS id h53sm4351072eea.1.2012.06.13.00.48.00 (version=SSLv3 cipher=OTHER); Wed, 13 Jun 2012 00:48:00 -0700 (PDT)
Message-ID: <4FD845AB.9020505@gmail.com>
Date: Wed, 13 Jun 2012 08:47:55 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Change in I-D announcement format
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 07:48:03 -0000

Did I miss an announcement of the change in format of
I-D announcement messages?

There's no longer a URL for the standard .txt format. That's
mildly annoying for me (extra time and extra mouse clicks)
and must be a nuisance for anyone who processes these messages
automatically.

At least, I would have expected a warning message about the change.

-- 
Regards
   Brian Carpenter



From ynir@checkpoint.com  Wed Jun 13 00:59:05 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0068521F85C4 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 00:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.819
X-Spam-Level: 
X-Spam-Status: No, score=-9.819 tagged_above=-999 required=5 tests=[AWL=0.780,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 g2EJcqNaKXRh for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 00:59:04 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 9B60D21F853F for <ietf@ietf.org>; Wed, 13 Jun 2012 00:59:03 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q5D7wxGd001114;  Wed, 13 Jun 2012 10:58:59 +0300
X-CheckPoint: {4FD84843-10000-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 13 Jun 2012 10:58:57 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
Date: Wed, 13 Jun 2012 10:58:56 +0300
Subject: RE: Change in I-D announcement format
Thread-Topic: Change in I-D announcement format
Thread-Index: Ac1JOOYJBwmygTWUTO+WLqt0/eFI0AAAUawA
Message-ID: <006FEB08D9C6444AB014105C9AEB133F017A7C056C98@il-ex01.ad.checkpoint.com>
References: <4FD845AB.9020505@gmail.com>
In-Reply-To: <4FD845AB.9020505@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 07:59:05 -0000

This line is not too hot either:

There's also a htmlized version available at:
http://tools.ietf.org/html/submission.filename }}-01=20

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Bri=
an E Carpenter
Sent: 13 June 2012 10:48
To: IETF discussion list
Subject: Change in I-D announcement format

Did I miss an announcement of the change in format of I-D announcement mess=
ages?

There's no longer a URL for the standard .txt format. That's mildly annoyin=
g for me (extra time and extra mouse clicks) and must be a nuisance for any=
one who processes these messages automatically.

At least, I would have expected a warning message about the change.

--
Regards
   Brian Carpenter



Scanned by Check Point Total Security Gateway.

From brian.e.carpenter@gmail.com  Wed Jun 13 01:05:05 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15F1121F86AD for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 01:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.325
X-Spam-Level: 
X-Spam-Status: No, score=-101.325 tagged_above=-999 required=5 tests=[AWL=0.366, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 9LjZ+sv-eqi4 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 01:05:04 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5685B21F846A for <ietf@ietf.org>; Wed, 13 Jun 2012 01:05:04 -0700 (PDT)
Received: by eaaq13 with SMTP id q13so87793eaa.31 for <ietf@ietf.org>; Wed, 13 Jun 2012 01:05:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4tYPCmyH68tRk9PHkIjK70GfFso7XfGrdqKDn461LFg=; b=c0qvWfXGZTW5s/Xc5GMlcLKy91R3m2mQmDDt/7Rvai5daWMCgDshncMr8s77rkfFGV sN+dAYCayyXUuqxgTg4o4fcUnN/WF4JkSMzYg3I0K7WzDrQQpsS83K8Dl79HAoOsC6kc Nkw5xt22FIASnuuvr8vIGow6UvjWVqduvSxSeJa+3XSe5gzi10pWRpyPtiwqDETH+ZWh ZmFcXr5VYsZsD+ffxxqZj0SU6Ng3eenZiK1WqQq7ef2JeET/vRRPQa1SMtnTPH1izP+y /rhPU08JpbEocNLMIFbMz288WqrrpyMeZuPtihs9FwGcx7vJfu1t2FYnVqjU5KiRDtMk MUcg==
Received: by 10.14.188.4 with SMTP id z4mr7883482eem.228.1339574703423; Wed, 13 Jun 2012 01:05:03 -0700 (PDT)
Received: from [192.168.1.66] (host-2-102-216-85.as13285.net. [2.102.216.85]) by mx.google.com with ESMTPS id c51sm4458072eei.12.2012.06.13.01.05.01 (version=SSLv3 cipher=OTHER); Wed, 13 Jun 2012 01:05:02 -0700 (PDT)
Message-ID: <4FD849A9.7000708@gmail.com>
Date: Wed, 13 Jun 2012 09:04:57 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: registries and designated experts
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie>	<4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net> <4FD786DC.4090403@gmail.com> <B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com>
In-Reply-To: <B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 08:05:05 -0000

John,

On 2012-06-12 19:38, John C Klensin wrote:
> 
> --On Tuesday, June 12, 2012 19:13 +0100 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>>> The above is at odds with standardization.  The last reason
>>> does not apply for Expert review.
>> I don't understand that statement. RFC 5226 says, in Section 2
>> about "Why Management of a Namespace May Be Necessary":
>>
>> "  A third, and perhaps most important, consideration concerns
>> potential    impact on the interoperability of unreviewed
>> extensions."
>>
>> One of the specific considerations for designated experts in
>> section 3.3 is
>>
>> "      - the extension would cause problems with existing
>> deployed         systems."
>>
>> It seems clear that interoperability is a primary concern for
>> any expert review.
> 
> Brian, Subramanian,
> 
> I've with Barry on this.  The details of the expectations of an
> expert reviewer, including the thresholds for approval, should
> be specified in whatever document sets up the particular
> registry.  One size does not fit all; "Expert Review" is a
> designation of a mechanism and not a set of criteria.

I completely agree. My point was only that the baseline set by
RFC 5226 is clear that interoperability is a criterion. The
details vary case by case and should be written down.

I also agree with what I think Randy meant - the designated
expert shouldn't be afraid to say no (or yes) in dubious
cases; that's why we designate an expert...

    Brian
> 
> We should, IMO, do two things in this area:
> 
> (1) When a document specifies "Expert Review" for a registry, it
> should be required to spell out the criteria the Expert is
> supposed to use, at least to the degree that isn't obvious.  If
> it doesn't, that should be grounds for "DISCUSS until fixed".
> 
> (2) If it turns out that an Expert for a particular registry is
> not behaving as people expect, part of the process for getting
> that fixed (or even complaining about it), should be to see if
> the registry-creating documents are clear about procedures and
> criteria.  If they are not, an effort to update those criteria
> would be a useful way to discuss the issues and not the
> individual expert.   Of course, Experts who knowingly violate
> clear criteria should be summarily fired -- but I think we can
> trust that to the IESG and note that it has almost never been
> necessary.
> 
>      john
> 
> 
> .
> 

From dromasca@avaya.com  Wed Jun 13 02:08:45 2012
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7467C21F857D for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 02:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.619
X-Spam-Level: 
X-Spam-Status: No, score=-103.619 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 0k4PS1SqAN69 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 02:08:45 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id D20E421F854C for <ietf@ietf.org>; Wed, 13 Jun 2012 02:08:44 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAN1X2E+HCzI1/2dsb2JhbABFhVeuPoElgQeCGAEBAQEDEhENBDcODAQCAQgNBAQBAQECAgYGDAsBAgICAQEfJQkIAQEEARIIGodbAwudAYociR4NiU6BIIklYoR/MmADk1KHRYUJhH2CYg
X-IronPort-AV: E=Sophos;i="4.77,402,1336363200"; d="scan'208";a="352465869"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 13 Jun 2012 05:06:09 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 13 Jun 2012 04:50:38 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: registries and designated experts
Date: Wed, 13 Jun 2012 11:08:41 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407B53CA1@307622ANEX5.global.avaya.com>
In-Reply-To: <4FD849A9.7000708@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: registries and designated experts
Thread-Index: Ac1JO0pwVDBb9DVcR8aP4Ju8hIx3cgAB8dbg
References: <4FCDD499.7060206@it.aoyama.ac.jp><4FCDE96E.5000109@cs.tcd.ie>	<4FD7083A.6080502@it.aoyama.ac.jp><4FD74FFC.3050905@stpeter.im><6.2.5.6.2.20120612073602.09c8cbb8@resistor.net><4FD786DC.4090403@gmail.com><B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com> <4FD849A9.7000708@gmail.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "John C Klensin" <john-ietf@jck.com>
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 09:08:45 -0000

DQoNCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGlldGYtYm91bmNl
c0BpZXRmLm9yZyBbbWFpbHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mDQo+
IEJyaWFuIEUgQ2FycGVudGVyDQo+IFNlbnQ6IFdlZG5lc2RheSwgSnVuZSAxMywgMjAxMiAxMTow
NSBBTQ0KPiBUbzogSm9obiBDIEtsZW5zaW4NCj4gQ2M6IFNNOyBpZXRmQGlldGYub3JnDQo+IFN1
YmplY3Q6IFJlOiByZWdpc3RyaWVzIGFuZCBkZXNpZ25hdGVkIGV4cGVydHMNCj4gDQo+IEpvaG4s
DQo+IA0KPiBPbiAyMDEyLTA2LTEyIDE5OjM4LCBKb2huIEMgS2xlbnNpbiB3cm90ZToNCj4gPg0K
PiA+IC0tT24gVHVlc2RheSwgSnVuZSAxMiwgMjAxMiAxOToxMyArMDEwMCBCcmlhbiBFIENhcnBl
bnRlcg0KPiA+IDxicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb20+IHdyb3RlOg0KPiA+DQo+ID4+
PiBUaGUgYWJvdmUgaXMgYXQgb2RkcyB3aXRoIHN0YW5kYXJkaXphdGlvbi4gIFRoZSBsYXN0IHJl
YXNvbg0KPiA+Pj4gZG9lcyBub3QgYXBwbHkgZm9yIEV4cGVydCByZXZpZXcuDQo+ID4+IEkgZG9u
J3QgdW5kZXJzdGFuZCB0aGF0IHN0YXRlbWVudC4gUkZDIDUyMjYgc2F5cywgaW4gU2VjdGlvbiAy
DQo+ID4+IGFib3V0ICJXaHkgTWFuYWdlbWVudCBvZiBhIE5hbWVzcGFjZSBNYXkgQmUgTmVjZXNz
YXJ5IjoNCj4gPj4NCj4gPj4gIiAgQSB0aGlyZCwgYW5kIHBlcmhhcHMgbW9zdCBpbXBvcnRhbnQs
IGNvbnNpZGVyYXRpb24gY29uY2VybnMNCj4gPj4gcG90ZW50aWFsICAgIGltcGFjdCBvbiB0aGUg
aW50ZXJvcGVyYWJpbGl0eSBvZiB1bnJldmlld2VkDQo+ID4+IGV4dGVuc2lvbnMuIg0KPiA+Pg0K
PiA+PiBPbmUgb2YgdGhlIHNwZWNpZmljIGNvbnNpZGVyYXRpb25zIGZvciBkZXNpZ25hdGVkIGV4
cGVydHMgaW4NCj4gPj4gc2VjdGlvbiAzLjMgaXMNCj4gPj4NCj4gPj4gIiAgICAgIC0gdGhlIGV4
dGVuc2lvbiB3b3VsZCBjYXVzZSBwcm9ibGVtcyB3aXRoIGV4aXN0aW5nDQo+ID4+IGRlcGxveWVk
ICAgICAgICAgc3lzdGVtcy4iDQo+ID4+DQo+ID4+IEl0IHNlZW1zIGNsZWFyIHRoYXQgaW50ZXJv
cGVyYWJpbGl0eSBpcyBhIHByaW1hcnkgY29uY2VybiBmb3INCj4gPj4gYW55IGV4cGVydCByZXZp
ZXcuDQo+ID4NCj4gPiBCcmlhbiwgU3VicmFtYW5pYW4sDQo+ID4NCj4gPiBJJ3ZlIHdpdGggQmFy
cnkgb24gdGhpcy4gIFRoZSBkZXRhaWxzIG9mIHRoZSBleHBlY3RhdGlvbnMgb2YgYW4NCj4gPiBl
eHBlcnQgcmV2aWV3ZXIsIGluY2x1ZGluZyB0aGUgdGhyZXNob2xkcyBmb3IgYXBwcm92YWwsIHNo
b3VsZA0KPiA+IGJlIHNwZWNpZmllZCBpbiB3aGF0ZXZlciBkb2N1bWVudCBzZXRzIHVwIHRoZSBw
YXJ0aWN1bGFyDQo+ID4gcmVnaXN0cnkuICBPbmUgc2l6ZSBkb2VzIG5vdCBmaXQgYWxsOyAiRXhw
ZXJ0IFJldmlldyIgaXMgYQ0KPiA+IGRlc2lnbmF0aW9uIG9mIGEgbWVjaGFuaXNtIGFuZCBub3Qg
YSBzZXQgb2YgY3JpdGVyaWEuDQo+IA0KPiBJIGNvbXBsZXRlbHkgYWdyZWUuIE15IHBvaW50IHdh
cyBvbmx5IHRoYXQgdGhlIGJhc2VsaW5lIHNldCBieQ0KPiBSRkMgNTIyNiBpcyBjbGVhciB0aGF0
IGludGVyb3BlcmFiaWxpdHkgaXMgYSBjcml0ZXJpb24uIFRoZQ0KPiBkZXRhaWxzIHZhcnkgY2Fz
ZSBieSBjYXNlIGFuZCBzaG91bGQgYmUgd3JpdHRlbiBkb3duLg0KPiANCj4gSSBhbHNvIGFncmVl
IHdpdGggd2hhdCBJIHRoaW5rIFJhbmR5IG1lYW50IC0gdGhlIGRlc2lnbmF0ZWQNCj4gZXhwZXJ0
IHNob3VsZG4ndCBiZSBhZnJhaWQgdG8gc2F5IG5vIChvciB5ZXMpIGluIGR1YmlvdXMNCj4gY2Fz
ZXM7IHRoYXQncyB3aHkgd2UgZGVzaWduYXRlIGFuIGV4cGVydC4uLg0KPiANCg0KW1tEUl1dICsx
LiANCg0KSSB0aGluayB0aGF0IGl0J3MgYSBnb29kIHRoaW5nIHRvIHByb3ZpZGUgZ3VpZGVsaW5l
cyBpbiB0aGUgUkZDcyBmb3IgRXhwZXJ0IFJldmlld3MgY3JpdGVyaWEsIGl0J3MgYmV0dGVyIHRo
YW4gb3JhbCB0cmFkaXRpb24sIHRoZXkgc2V0IGFuZCBkb2N1bWVudCB0aGUgZXhwZWN0YXRpb25z
IGF0IHRoZSB0aW1lIHRoZSBkb2N1bWVudCBpcyBhcHByb3ZlZC4gSG93ZXZlciBndWlkZWxpbmVz
IGFyZSBqdXN0IGd1aWRlbGluZXMsIG90aGVyd2lzZSB0aGUgcHJvY2VzcyBjb3VsZCBoYXZlIGJl
ZW4gY29tcGxldGVseSBhdXRvbWF0ZWQsIGFuZCB0aGUgZXhwZXJ0IGlzIHRoZSBvbmUgY2FsbGVk
IHRvIG1ha2UgdGhlIGZpcm0geWVzL25vIHJlY29tbWVuZGF0aW9uIHRvIElBTkEuIElmIGF0IHNv
bWUgcG9pbnQgaW4gdGltZSB0aGUgZ3VpZGVsaW5lcyBhcmUgaW4gY29uZmxpY3Qgd2l0aCB0aGUg
cmVhbGl0eSwgdGhlIFJGQyBzaG91bGQgYmUgdXBkYXRlZCwgc29tZXRpbWVzIHRoZSBwb2xpY3kg
Y2hhbmdlZC4NCg0KTWF5YmUgYW4gSUVTRyBzdGF0ZW1lbnQgb24gdGhpcyByZXNwZWN0IGNhbiBo
ZWxwIGhlcmUuIA0KDQpEYW4NCg0K

From stephen.farrell@cs.tcd.ie  Wed Jun 13 02:47:22 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6215A21F867B for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 02:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.099
X-Spam-Level: 
X-Spam-Status: No, score=-101.099 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_31=0.6, J_CHICKENPOX_51=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 etwpocos5SlD for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 02:47:21 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id A34F421F8668 for <ietf@ietf.org>; Wed, 13 Jun 2012 02:47:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id BC5CC1717F2; Wed, 13 Jun 2012 10:47:18 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339580838; bh=sH6Rs8QEGX+uLv 4a3EsIIuiSNx5a/7OBGVi5iazlVdE=; b=GESqOYvrHvPfesIRVoaKj73399um/X 9ngV/gjc+yzNe6kaUbaAB3dadqATc3/M5NR+ov13m/PJqg2/4sNXwo+hzWKWAQyF SoPZvO6Gjl3sWb/58ICnJ+eK8iHGx8uWta9qMzf6Y1aq7Tfa6nRWh9bIPtUk/+WZ KaQwiZzOQklr9KFKEvXNMOS8+TKnGzGYIqILG97p5yMBfJyiEKWSKGgYsNBgGeUj EFMP3RL3p+9Dm1l3K+aqj34fnrPmhkLiG8Z5/8g/a2+/BxcYH7TSv3t2E/r5mIH8 9Yl8Pp+6z7nyB7aHjnwcsHZUptMDR9fyRnrX4cA0p5N1Zvmf6JyL55MQ==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id Y64X-KarQ7g5; Wed, 13 Jun 2012 10:47:18 +0100 (IST)
Received: from [IPv6:2001:770:10:203:353a:5c1f:6277:879a] (unknown [IPv6:2001:770:10:203:353a:5c1f:6277:879a]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 5664D1717F1; Wed, 13 Jun 2012 10:47:10 +0100 (IST)
Message-ID: <4FD8619F.4000102@cs.tcd.ie>
Date: Wed, 13 Jun 2012 10:47:11 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com>	<CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com>	<CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com>	<4FD29389.5060900@cs.tcd.ie> <tslboktwbzv.fsf@mit.edu> <4FD2AAB3.4010305@cs.tcd.ie> <4FD71D6A.9070101@it.aoyama.ac.jp> <4FD7231F.1050903@cs.tcd.ie> <4FD83322.70203@it.aoyama.ac.jp>
In-Reply-To: <4FD83322.70203@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Jonathan A Rees <rees@mumble.net>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 09:47:22 -0000

On 06/13/2012 07:28 AM, "Martin J. Dürst" wrote:
> Hello Stephen,
> 
> On 2012/06/12 20:08, Stephen Farrell wrote:
>>
>> So would it work to add this:
>>
>> "
>>     Note that relative ni URIs can occur, for example as shown in
>>     Figure 5.  In such cases, user agents MUST construct the absolute URI
>>     as they would in the case of an HTTP URL, that is, in the example
>>     shown the absolute URI for "this third document" would be
>>     "ni://example.com/sha-256-128;...".
> 
> This looks fine, except that it contains a MUST when it can just refer
> to RFC 3986. So I would suggest the following text:
> 
>    Note that relative ni URIs can occur. In such cases, the algorithm
>    in Section 5 of RFC 3986 applies. As an example, in Figure 5, the
>    absolute URI for "this third document" is
>    "ni://example.com/sha-256-128;...".

works for me

> 
> 
> 
>>       <html>
>>        <head>
>>          <title>ni: relative URI test</title>
>>          <base href="ni://example.com">
>>        </head>
>>
>>        <body>
>>          <p>Please check<a href="sha-256;f4OxZX...">this document</a>.
>>            And<a href="sha-256;UyaQV...">this other document</a>.
>>            And<a href="sha-256-128;...">this third document</a>.
>>          </p>
>>        </body>
>>       </html>
>>
>>                  Figure 5: Example HTML with relative ni URI
>>
>> "
>>
>> Better suggestions welcome.
>> Ta,
> 
> I tried to look "Ta" up on the Web, but there were just too many
> potential explanations. What are you using it for?

Ta == Thanks :-)

Ta,
S.


> 
> 
> Regards,   Martin.
> 
>> S.
> 
> 

From mrex@sap.com  Wed Jun 13 02:51:11 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E723421F8427 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 02:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 b7YPlXZQ9CL3 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 02:51:11 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 83F4421F8470 for <ietf@ietf.org>; Wed, 13 Jun 2012 02:51:10 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q5D9oxPs019114 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 13 Jun 2012 11:50:59 +0200 (MEST)
Subject: Re: Change in I-D announcement format
In-Reply-To: <006FEB08D9C6444AB014105C9AEB133F017A7C056C98@il-ex01.ad.checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
Date: Wed, 13 Jun 2012 11:50:59 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20120613095059.8707A1A065@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 09:51:12 -0000

> Brian E Carpenter wrote:
>> 
>> Did I miss an announcement of the change in format of
>> I-D announcement messages?
>> 
>> There's no longer a URL for the standard .txt format.
>> That's mildly annoying for me (extra time and extra mouse clicks)
>> and must be a nuisance for anyone who processes these
>> messages automatically.

I did not see an announcement either.

I don't mind addition of URLs.  But I strongly dislike removal of URLs!
I would also appreciate if that URL was put back in.

After noticing download failures due to the lack of the URL to the TXT,
I changed my I-D download perl-script on 11-Jun-2012 to accomodate for that
unexpected change.  Since the URL is gone, I have resorted to synthesize
the URL to the TXT document myself from the unqualified filename.

   if ( $_ =~ m/^\s+Filename\s+:\s+(draft-.*\d\d\.txt)/ ) {
        push(@link, "http://tools.ietf.org/id/$1");
   }


Additionally, for some time now, I'm seeing errors trying to download
I-D TXT documents which have been superseded by a successor version
_before_ I feed the announcement EMail to my download script.

What is the purpose of the change to deny previous TXT versions of I-Ds?


Yoav Nir wrote:
> This line is not too hot either:
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/submission.filename }}-01 

This puzzles me too.

How about adding a mailto: URL into I-D announcements to
report bugs for the software that creates them?

-Martin

From narten@us.ibm.com  Wed Jun 13 05:49:53 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D5F521F8642 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 05:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 BqinBcJs9r2l for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 05:49:52 -0700 (PDT)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id 7D23F21F8637 for <ietf@ietf.org>; Wed, 13 Jun 2012 05:49:52 -0700 (PDT)
Received: from /spool/local by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Wed, 13 Jun 2012 06:49:51 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 13 Jun 2012 06:49:50 -0600
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id BE2563E40072 for <ietf@ietf.org>; Wed, 13 Jun 2012 12:49:23 +0000 (WET)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q5DCmpo5055328 for <ietf@ietf.org>; Wed, 13 Jun 2012 06:49:07 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q5DCmZKN025704 for <ietf@ietf.org>; Wed, 13 Jun 2012 06:48:35 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-76-134-249.mts.ibm.com [9.76.134.249]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q5DCmVoR025269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Jun 2012 06:48:33 -0600
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q5DCmSL6028424; Wed, 13 Jun 2012 08:48:29 -0400
Message-Id: <201206131248.q5DCmSL6028424@cichlid.raleigh.ibm.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: registries and designated experts
In-reply-to: <EDC652A26FB23C4EB6384A4584434A0407B53CA1@307622ANEX5.global.avaya.com>
References: <4FCDD499.7060206@it.aoyama.ac.jp><4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp><4FD74FFC.3050905@stpeter.im><6.2.5.6.2.20120612073602.09c8cbb8@resistor.net><4FD786DC.4090403@gmail.com><B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com> <4FD849A9.7000708@gmail.com> <EDC652A26FB23C4EB6384A4584434A0407B53CA1@307622ANEX5.global.avaya.com>
Comments: In-reply-to "Romascanu, Dan (Dan)" <dromasca@avaya.com> message dated "Wed, 13 Jun 2012 11:08:41 +0200."
Date: Wed, 13 Jun 2012 08:48:28 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12061312-1780-0000-0000-0000066681FB
X-IBM-ISS-SpamDetectors: 
X-IBM-ISS-DetailInfo: BY=3.00000281; HX=3.00000190; KW=3.00000007; PH=3.00000001; SC=3.00000002; SDB=6.00147686; UDB=6.00033703; UTC=2012-06-13 12:49:51
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 12:49:53 -0000

> Maybe an IESG statement on this respect can help here.

Is the existing text in RFC 5226 not sufficient? It contains extensive
text about the purpose and role of designated experts, and was revised
substantially the last time around to try and find a good middle
ground between being overly prescriptive and giving experts a "blank
check" to do what they want.

Nothing in the discussion I've seen so far in this thread seems at
odds with or beyond what is already in RFC 5226 (but I may be biased).

Thomas


From alexey.melnikov@isode.com  Wed Jun 13 05:58:27 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA02721F857A; Wed, 13 Jun 2012 05:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 s67ev3iRP2Xl; Wed, 13 Jun 2012 05:58:27 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0658F21F8554; Wed, 13 Jun 2012 05:58:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1339584399; d=isode.com; s=selector; i=@isode.com; bh=uWLgdw/EuKzNiCteJBgvfOWbbfJipLb2UCZKGzAMfNs=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=UFBO2g2pqLIL5iazrGOrjJdjXpHb5xhcMdct3QpCE5xKGAnlNyXEInlyxj/RgyCiO6EVsc iDfTF+e5ItswSGBa0A2UI4ckx1NuC1IW5E6EXfRdwPc+u5MX7f7lLOhm/SykLnCpPEKxk6 so3+IyLDM7OVNwU6JTucrTupESOLA3c=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T9hvjgAE413e@rufus.isode.com>; Wed, 13 Jun 2012 11:46:38 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4FD86FB2.2050002@isode.com>
Date: Wed, 13 Jun 2012 11:47:14 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: apps-discuss@ietf.org, draft-ietf-nea-pt-tls.all@tools.ietf.org
Subject: Re: [apps-discuss] APPSDIR review of draft-ietf-nea-pt-tls-04
References: <4FCD0614.5050902@isode.com>
In-Reply-To: <4FCD0614.5050902@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 12:58:28 -0000

On 04/06/2012 20:01, Alexey Melnikov wrote:
> I have been selected as the Applications Area Directorate reviewer for 
> this draft (for background on APPSDIR, please see 
> http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate 
> ).
>
> Please resolve these comments along with any other Last Call comments 
> you may receive. Please wait for direction from your document shepherd 
> or AD before posting a new version of the draft.  The review is not 
> copied to the IESG as the Last Call has not been announced yet.
>
> Document: draft-ietf-nea-pt-tls-04
> Title: PT-TLS: A TCP-based Posture Transport (PT) Protocol
> Reviewer: Alexey Melnikov
> Review Date: June 4, 2012
>
> Summary: This document is almost ready for publication as a Proposed 
> Standard, although some [mostly] SASL related issues remain.
>
> This document specifies PT-TLS, a TCP-based Posture Transport (PT)
> protocol.  The PT-TLS protocol carries the Network Endpoint
> Assessment (NEA) message exchange under the protection of a Transport
> Layer Security (TLS) secured tunnel.
>
> (Note, I've reviewed -04, but I think all of this still applies to -05.)
Additional issues in -05:

1) I didn't find the updated text prohibiting TLS renegotiation to be 
any clearer in -05? Can you maybe try to explain what is allowed and 
what is not?

2) In the IANA Considerations:

The PEN 0 (IETF) PT-TLS Message Type values between 9 and 2^32-2
inclusive are allocated for future assignment by the IANA.  The value
2^32-1 is permanently reserved and is not to be allocated.

Whom does the last sentence apply to? This registry? Or the IANA PEN 
registry being documented by draft-liang-iana-pen?

From housley@vigilsec.com  Wed Jun 13 06:06:57 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECA8521F85D1 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 06:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ZuYDrwxxKGY8 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 06:06:57 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 66CAF21F85A8 for <ietf@ietf.org>; Wed, 13 Jun 2012 06:06:57 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id E5B7D9A4724; Wed, 13 Jun 2012 09:07:11 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 10Q21d+EGr6K; Wed, 13 Jun 2012 09:06:55 -0400 (EDT)
Received: from [192.168.2.110] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 098969A471B; Wed, 13 Jun 2012 09:07:11 -0400 (EDT)
Subject: Re: Change in I-D announcement format
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4FD845AB.9020505@gmail.com>
Date: Wed, 13 Jun 2012 09:06:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D903BF63-043C-400A-90AF-DF962B246540@vigilsec.com>
References: <4FD845AB.9020505@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 13:06:58 -0000

Brian:

There was no announcement that this change was about to be deployed; =
however, there was a long discussion of the change.  It started with a =
request for the HTML version of the I-D instead of the plain text =
version.  At the end of the discussion the decision was to use the =
Datatracker URL as it allows anyone to get the plaintext or a diff with =
just one more click.

Russ


On Jun 13, 2012, at 3:47 AM, Brian E Carpenter wrote:

> Did I miss an announcement of the change in format of
> I-D announcement messages?
>=20
> There's no longer a URL for the standard .txt format. That's
> mildly annoying for me (extra time and extra mouse clicks)
> and must be a nuisance for anyone who processes these messages
> automatically.
>=20
> At least, I would have expected a warning message about the change.
>=20
> --=20
> Regards
>   Brian Carpenter
>=20
>=20


From mrex@sap.com  Wed Jun 13 06:28:43 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A214C21F863E for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 06:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 gkps2brVfCNt for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 06:28:43 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id F2B5A21F85AF for <ietf@ietf.org>; Wed, 13 Jun 2012 06:28:42 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q5DDSe7u001005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 13 Jun 2012 15:28:40 +0200 (MEST)
Subject: Re: Change in I-D announcement format
In-Reply-To: <D903BF63-043C-400A-90AF-DF962B246540@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
Date: Wed, 13 Jun 2012 15:28:40 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20120613132840.660C11A067@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 13:28:43 -0000

Russ Housley wrote:
> Brian:
> 
> There was no announcement that this change was about to be deployed;
> however, there was a long discussion of the change.  It started with
> a request for the HTML version of the I-D instead of the plain
> text version.  At the end of the discussion the decision was to use
> the Datatracker URL as it allows anyone to get the plaintext or a
> diff with just one more click.

I recall a different outcome, because this reasoning looks flawed to me.

Tools that process the announce-Emails automatically
will be unable to "perform another mouse-click" in order to
get to a page where there is an URL to the TXT document, 
so that option does not exist.

Those who use a graphical frontend that is sensitive to follow
URLs on mouse-click, will probably prefer the HTML variant
over the TXT variant.

The two changes that I would appreciate:
Put the direct TXT URL back into the announcement.
Fix the new URL to the HTML version in the announcment.

-Martin


From ned+ietf@mauve.mrochek.com  Wed Jun 13 09:18:24 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B41521F852C for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 09:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 IJz7FTtoxrxt for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 09:18:24 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id F354821F850C for <ietf@ietf.org>; Wed, 13 Jun 2012 09:18:23 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OGMRAJZEQO0035EU@mauve.mrochek.com> for ietf@ietf.org; Wed, 13 Jun 2012 09:13:22 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OGIRBMUA6O0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 13 Jun 2012 09:13:20 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OGMRAIUL7I0006TF@mauve.mrochek.com>
Date: Wed, 13 Jun 2012 07:49:29 -0700 (PDT)
Subject: Re: registries and designated experts
In-reply-to: "Your message dated Wed, 13 Jun 2012 14:53:07 +0900" <m21uljep18.wl%randy@psg.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <4FD75881.3080102@dcrocker.net> <40qft756nm9l1g4q5asm5voc0jg2ng0pgl@hive.bjoern.hoehrmann.de> <m21uljep18.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 16:18:24 -0000

> > It seems to me that if an expert reviewer thinks that something will do
> > notable harm, they should decline to make a decision and defer it to the
> > IETF at large

> so they are not an expert, they are a rubber stamp?  bs.

+1

More generally, the notion of appealing to the "IETF at large", whatever that
is supposed to consist of, isn't part of the written policy of any registry I'm
aware of. There's supposed to be an appeals process (usually to the IESG), and
that's the obvious process to invoke should an issue come up that a reviewer
feels uncomfortable resolving directly.

Additionally, given the widespread use of IANA registries by people and
organizations not connected to the IETF in any way - and this usage is
something we want to encourage - appealing registrations to the IETF at large
is a really bad idea.

				Ned

From enkechen@cisco.com  Tue Jun 12 11:19:17 2012
Return-Path: <enkechen@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CEC421F84A6; Tue, 12 Jun 2012 11:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 44mTvJOKbgBt; Tue, 12 Jun 2012 11:19:16 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 86A7521F84A0; Tue, 12 Jun 2012 11:19:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=enkechen@cisco.com; l=4069; q=dns/txt; s=iport; t=1339525156; x=1340734756; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Lw1sIdHAZPtBu0WJOGAVELpx4paMKByDJbGPpOwoqKE=; b=jvV6cTJAlsi5i4A988NlbLRCjGc2V1zfXeS1I8bTTzq4NohjLKLa5dHP DjEJJlvHgvP4MdgyrPzI7rYBaoorMeUJf2iQystvTuAGt+I3kBY/z3n4j xYZZxVjT4oPYdolosSRh8551SmvoZ1B1OZdQrqH38K2RFzhF2NUA7oYYW U=;
X-IronPort-AV: E=Sophos;i="4.75,759,1330905600"; d="scan'208";a="48566393"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 12 Jun 2012 18:19:16 +0000
Received: from dhcp-171-71-139-24.cisco.com (dhcp-171-71-139-24.cisco.com [171.71.139.24]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q5CIJGi4021678; Tue, 12 Jun 2012 18:19:16 GMT
Message-ID: <4FD7886F.5090508@cisco.com>
Date: Tue, 12 Jun 2012 11:20:31 -0700
From: Enke Chen <enkechen@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: stbryant@cisco.com
Subject: Re: [Idr] Fwd: Re: Last Call: <draft-ietf-idr-rfc4893bis-06.txt> (BGP Support for	Four-octet AS Number Space) to Proposed Standard
References: <20120612135455.GC18025@diehard.n-r-g.com> <4FD7515E.3000101@cisco.com>
In-Reply-To: <4FD7515E.3000101@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 13 Jun 2012 09:30:18 -0700
Cc: idr mailing list <idr@ietf.org>, "idr-chairs@tools.ietf.org" <idr-chairs@tools.ietf.org>, Enke Chen <enkechen@cisco.com>, "Ietf@ietf.org" <Ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 18:19:17 -0000

Here is my reply to Claudio on the IDR list.  Copying the IETF list.

------------------------------------------------------
Hi, Claudio:

Not sure if you are aware of the large scale outage that occurred a few 
years ago from the leak of the confed related segments by one 
implementation. At the time quite a few implementations were resetting 
the sessions when receiving such updates.

While discarding the whole AS4_PATH would be simpler and less disruptive 
(than session resetting), it would still lose the vital as-path info 
contained in the AS4_PATH which can otherwise be recovered by 
"repairing" the attribute.  That is why the approach specified in the 
rfc4893bis is adopted, and it has been implemented widely.

-- Enke


On 6/12/12 7:25 AM, Stewart Bryant wrote:
> FYI
>
> Copying to IETF list as this is an IETF LC
>
> Stewart
>
> -------- Original Message --------
> Subject:     Re: [Idr] Last Call: (BGP Support for Four-octet AS 
> Number Space) to Proposed Standard
> Date:     Tue, 12 Jun 2012 15:54:55 +0200
> From:     Claudio Jeker <cjeker@diehard.n-r-g.com>
> To:     Stewart Bryant <stbryant@cisco.com>
> CC: <idr@ietf.org>
>
>
>
> On Tue, Jun 12, 2012 at 11:30:11AM +0100, Stewart Bryant wrote:
>> On 01/06/2012 23:00, Claudio Jeker wrote:
>> >On Fri, Jun 01, 2012 at 11:54:44AM -0700, The IESG wrote:
>> >>The IESG has received a request from the Inter-Domain Routing WG 
>> (idr) to
>> >>consider the following document:
>> >>- 'BGP Support for Four-octet AS Number Space'
>> >> <draft-ietf-idr-rfc4893bis-06.txt> as Proposed Standard
>> >>
>> >>The IESG plans to make a decision in the next few weeks, and solicits
>> >>final comments on this action. Please send substantive comments to the
>> >>ietf@ietf.org mailing lists by 2012-06-15. Exceptionally, comments 
>> may be
>> >>sent to iesg@ietf.org instead. In either case, please retain the
>> >>beginning of the Subject line to allow automated sorting.
>> >>
>> >>Abstract
>> >>
>> >>
>> >>    The Autonomous System (AS) number is encoded as a two-octet 
>> entity in
>> >>    the base BGP specification. This document describes extensions 
>> to BGP
>> >>    to carry the Autonomous System numbers as four-octet entities.  
>> This
>> >>    document obsoletes RFC 4893.
>> >>
>> >Just for the sake of clarity, OpenBGPD will not do the following:
>> >
>> >    In addition, the path segment types AS_CONFED_SEQUENCE and
>> >    AS_CONFED_SET [RFC5065] MUST NOT be carried in the AS4_PATH 
>> attribute
>> >    of an UPDATE message.  A NEW BGP speaker that receives these path
>> >    segment types in the AS4_PATH attribute of an UPDATE message 
>> from an
>> >    OLD BGP speaker MUST discard these path segments, adjust the 
>> relevant
>> >    attribute fields accordingly, and continue processing the UPDATE
>> >    message.  This case SHOULD be logged locally for analysis.
>> >
>> >There is no point to do this fiddeling instead we will treat this 
>> like any
>> >other parse error of AS4_PATH.
>> >
>> Claudio
>>
>> Since this is in last call, I have to ask whether you have objection
>> to the publication
>> of the above text, or have any proposed text changes?
>
> I see no reason to enforce AS_CONFED_SEQUENCE and AS_CONFED_SET stripping
> on all AS4 implementations. It forces bgp implementations that don't have
> confederation support to strip out something that will cause an error in
> the regular path and for those systems ignoring the AS4_PATH attribute
> is perfectly fine. I do not understand how a workaround needs to be a
> MUST for something that is a MUST NOT at the same time? Why MUST we
> workaround something that MUST NOT appear? Why do we need to add extra
> code that is hard to test and maybe cause for further errors because it
> modifies attributes in very uncommon way?
>
> I propose to remove that paragraph entierly since it does only add
> complexity to the protocol for no reason and therefor is only a source of
> errors without any benefit.


From mohamed.boucadair@orange.com  Wed Jun 13 00:17:34 2012
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 841FB21F85A5; Wed, 13 Jun 2012 00:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.152
X-Spam-Level: 
X-Spam-Status: No, score=-3.152 tagged_above=-999 required=5 tests=[AWL=1.096,  BAYES_00=-2.599, GB_I_INVITATION=-2, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 IrAmN4PGyjhW; Wed, 13 Jun 2012 00:17:34 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id A827021F85A4; Wed, 13 Jun 2012 00:17:33 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id E1AE92DC34A; Wed, 13 Jun 2012 09:17:32 +0200 (CEST)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id A533A23804B; Wed, 13 Jun 2012 09:17:32 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Wed, 13 Jun 2012 09:17:32 +0200
From: <mohamed.boucadair@orange.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Date: Wed, 13 Jun 2012 09:17:31 +0200
Subject: RE: Last Call: <draft-ietf-6man-lineid-05.txt> (The Line Identification Destination Option) to Experimental RFC
Thread-Topic: Last Call: <draft-ietf-6man-lineid-05.txt> (The Line Identification Destination Option) to Experimental RFC
Thread-Index: Ac1Fs1XkNY8C44NgQnKZ7H347pCyswDf3WXg
Message-ID: <94C682931C08B048B7A8645303FDC9F36E331FF0B4@PUEXCB1B.nanterre.francetelecom.fr>
References: <20120604141855.24802.66473.idtracker@ietfa.amsl.com> <94C682931C08B048B7A8645303FDC9F36E32ED1AC0@PUEXCB1B.nanterre.francetelecom.fr> <4FD25D14.7000207@ericsson.com>
In-Reply-To: <4FD25D14.7000207@ericsson.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.24.112414
X-Mailman-Approved-At: Wed, 13 Jun 2012 09:30:18 -0700
Cc: DUREL Sophie OLNC/NAD/TIP <sophie.durel@orange.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 07:17:34 -0000

Dear Suresh,

Having the warnings in the draft is good but having a pointer to a document=
 including a fair and detailed risk analysis is also valuable and worth to =
be acknowledged.

Having that pointer is an "invitation" to people who will deploy this mecha=
nism (I know some of them who are planning to) to assess the validity of th=
e claimed threats (and also to consider the alternatives listed in Section =
3 of draft-dec-*). This is even encouraged given the intended track: "exper=
imental".=20

Thanks.

Cheers,
Med=20

>-----Message d'origine-----
>De : Suresh Krishnan [mailto:suresh.krishnan@ericsson.com]=20
>Envoy=E9 : vendredi 8 juin 2012 22:14
>=C0 : BOUCADAIR Mohamed OLNC/NAD/TIP
>Cc : ietf@ietf.org; ipv6@ietf.org; DUREL Sophie OLNC/NAD/TIP
>Objet : Re: Last Call: <draft-ietf-6man-lineid-05.txt> (The=20
>Line Identification Destination Option) to Experimental RFC
>
>Hi Med,
>
>On 06/06/2012 08:04 AM, mohamed.boucadair@orange.com wrote:
>> Dear Suresh, all,
>>=20
>> Even if the document includes several warnings about the=20
>unreliability of an RS-based mechanism, I suggest to add a=20
>pointer to the following document:
>> http://tools.ietf.org/html/draft-dec-6man-rs-access-harmful-00.=20
>
>Is there something in particular that you think is missing from the
>lineid draft? The current warning text in lineid (and the
>reclassification to experimental) was arrived at after consultations
>with the the 6man chairs and the author of draft-dec.
>
>Thanks
>Suresh
>=

From jonathan.rees@gmail.com  Tue Jun 12 08:23:21 2012
Return-Path: <jonathan.rees@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5517C21F86A4 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 08:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 KgkBN1QsKRG5 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 08:23:20 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id D66C821F8513 for <ietf@ietf.org>; Tue, 12 Jun 2012 08:23:19 -0700 (PDT)
Received: by dacx6 with SMTP id x6so7016439dac.31 for <ietf@ietf.org>; Tue, 12 Jun 2012 08:23:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OdvBhWF178b7JqQpA255DMlpRMUHC2XwzN9q6gPFMH8=; b=Jqns7GjNJQN9OTskyvGTswea+HQos6TvDrOJXKkaM9B4JvoCQtWd69TMD2hQcEAUAN op6AcyWKq/I+JNYYgNEQdAPVaElKrcKL+/J1VjnF8tySKz/4f/C4tYuIOQAHYsgWchAq j16USBhNgfDJP4NJ28KGvGGiGuexLPOlKs5v8u1TM9gyVqSCSCf3fs3zN/k+LmnzTnbz bGPFSrW1FcdImSAcF+uw+snoV3XU40QKkAsYBnc4BPUUCXi0MZFEygXcklP36pGnz5mV jHXg/aiGSzaPnj9Q7wwp1T2/q43YhrF9kNl3V/82OB/ww44zVbXekWbxMIWc59IF2j4v VVyA==
MIME-Version: 1.0
Received: by 10.68.229.2 with SMTP id sm2mr39304733pbc.57.1339514599382; Tue, 12 Jun 2012 08:23:19 -0700 (PDT)
Sender: jonathan.rees@gmail.com
Received: by 10.143.5.7 with HTTP; Tue, 12 Jun 2012 08:23:19 -0700 (PDT)
In-Reply-To: <4FD7155D.6080407@cs.tcd.ie>
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com> <4FD0FDC2.2090802@cs.tcd.ie> <CAGnGFMLc15-ZkD_Of7k0zK7ef-i6HN2LsPCfbW3pkwFkpSiOfA@mail.gmail.com> <4FD1E048.8080507@cs.tcd.ie> <4FD710AD.9030505@it.aoyama.ac.jp> <4FD7155D.6080407@cs.tcd.ie>
Date: Tue, 12 Jun 2012 11:23:19 -0400
X-Google-Sender-Auth: FJy4gIrq2K79r-H0fJzV3PwqEXI
Message-ID: <CAGnGFM+41AFr+jtobgoyHwhLPe4rmhc-YzuOigw8Bs+zrhJoHA@mail.gmail.com>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
From: Jonathan A Rees <rees@mumble.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 13 Jun 2012 09:30:54 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 15:23:21 -0000

On Fri, Jun 8, 2012 at 9:45 PM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
>
> Hi Sam,
>
> On 06/09/2012 01:43 AM, Sam Hartman wrote:
>> Add me as a +1 for the idea that content-type is important for this.
>> I tend to agree with the arguments given so far. Namely, for some
>> important use cases you're going to want to know the content type and
>> guessing is =A0really a bad idea.
>
> Thusly counted:-)
>
>>
>> That said, there are security considerations associated with specifying
>> a content type too. =A0I'm particularly imagining a situation where some
>> sort of deep inspection security appliance uses a different procedure
>> for deciding what kind of foo it is than the ultimate application. One
>> guesses based on byte stream another looks at a content type. =A0This is
>> well known; it's not new; it's probably even so documented that any
>> reasonably current set of MIME security considerations already includes
>> a reference.
>
> My only real concern with adding this is the issue of complexity
> related to c14n of input to the hash function. While CMS does (I
> think) define that well, imposing that burden on anyone that might
> want to write code that validates name-data integrity is an issue.
> Anyway, if we want to add it we'll look that over and figure how
> it might best be done.

OK, I agree that's an issue. My feeling is that it's not much of a
burden, and to the extent it is a burden it's important to take on.
I'm not sure but wouldn't the burden just be: If (1) the client is
sensitive to media type, and (2) it gets a media type from the server,
and (3) ct=3D is provided, and (4) they don't match, you either ignore
the type from the server, or treat it as spoofing.  Otherwise - you
just do what you would have done, had ct=3D not been mentioned in the
spec. Clients or protocols for which either (1) or (2) doesn't apply
are unaffected; if (1-2-3) apply then the situation is important.

(Come to think of it the  same consideration applies to data: ... of
course it's not common to use a data: URI as the request URI in an
HTTP request.)

From housley@vigilsec.com  Wed Jun 13 09:39:16 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2242F11E8079 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 09:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 WkkvSqZeYs42 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 09:39:15 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id F3B8F11E8072 for <ietf@ietf.org>; Wed, 13 Jun 2012 09:39:12 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 51FD5F24014 for <ietf@ietf.org>; Wed, 13 Jun 2012 12:39:22 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id TXIAP5UkIqkN for <ietf@ietf.org>; Wed, 13 Jun 2012 12:39:04 -0400 (EDT)
Received: from [192.168.2.110] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 1F5309A4725 for <ietf@ietf.org>; Wed, 13 Jun 2012 12:39:21 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Last Call: <draft-krishnan-nomcom-tools-01.txt> (Requirements for IETF Nominations Committee tools) to Informational RFC
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20120613160444.22853.1522.idtracker@ietfa.amsl.com>
Date: Wed, 13 Jun 2012 12:39:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3ED7694B-47FE-4741-B0FE-4989BFDF68A0@vigilsec.com>
References: <20120613160444.22853.1522.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 16:39:16 -0000

I want to highlight one think in this document.  The document says:

   There is an existing tool for supporting Nomcom work.  The set of
   requirements specified in this document are mainly enhancement
   requirements or behavior changes to the existing tool.  Unless
   otherwise stated all of the current functions of the existing Nomcom
   tool need to be supported in the new tool as well.

If you have not served on a NomCom since the existing tool was deployed, =
then it will be difficult to understand the proposed tool requirements.  =
Is this acceptable?

Russ


On Jun 13, 2012, at 12:04 PM, The IESG wrote:

> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'Requirements for IETF Nominations Committee tools'
>  <draft-krishnan-nomcom-tools-01.txt> as Informational RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-07-11. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>   This document defines the requirements for a set of tools for use by
>   the IETF Nominations Committee.
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-krishnan-nomcom-tools/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-krishnan-nomcom-tools/ballot/
>=20
> No IPR declarations have been submitted directly on this I-D.


From iad@ietf.org  Wed Jun 13 09:42:45 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B172221F8491; Wed, 13 Jun 2012 09:42:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Upvcc4kr7VGm; Wed, 13 Jun 2012 09:42:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC2621F847D; Wed, 13 Jun 2012 09:42:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: RFP: IETF Mail List Archiving, Web-Browsing & Search Tool
X-Test-IDTracker: no
X-IETF-IDTracker: 4.20
Message-ID: <20120613164244.7679.2968.idtracker@ietfa.amsl.com>
Date: Wed, 13 Jun 2012 09:42:44 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 16:42:45 -0000

The Internet Engineering Task Force (IETF) desires an IETF Mail List Archiv=
ing, Web-Browsing & Search
Tool that will improve email list archiving and searching. =


The IETF makes heavy use of electronic mail lists to conduct its work.  IET=
F Participants frequently need to
search the archives of these mail lists, and have asked for improved search=
 capabilities, particularly when the
search needs to cover a large period of time, or cross several lists.  For =
instance, document editors, shepherds,
working group chairs, and area directors may need to review all discussion =
of a particular Internet-Draft.  That
discussion may be spread across the working group list, one or more directo=
rate lists, and the IETF general =

list.  Occasionally, work impacts multiple groups, possibly in different ar=
eas, and the search must cover =

additional working group lists.  The current tools for performing these sea=
rches require several manually
coordinated steps, which are error prone.  It is difficult to obtain a comp=
lete local copy of the archive.  Without
such a local copy, searching most working group lists requires brute force =
effort, possibly aided by web search =

engines.  More advanced search capabilities have been constructed for a lim=
ited subset of the available lists and =

are exposed in the "Email Archives Quick Search" section of the main IETF w=
ebsite.  While these tools are of =

great assistance, there is still significant need for improvement.  The cur=
rent archive mechanism could also be
made more efficient.  The current practices involve duplicate stores for th=
e web and ftp interfaces, which =

impacts storage.  Also, replication is subject to inconsistency.

Bidders may propose customization of an existing product(s), and/or develop=
ment of the solution.

The RFP can be found at: http://iaoc.ietf.org/rfpsrfis.html =


Proposals must be received via email at agenda-tool@ietf-bids.org no later =
than July 9, 2012.  All questions/
inquiries must be submitted in writing and must be received no later than J=
une 25, 2012.  Responses to =

questions and inquiries shall be posted online at:  http://iaoc.ietf.org/rf=
psrfis.html by June 29, 2012. =


The point of contact regarding this RFP is the IETF Administrative Director=
, Ray Pelletier, iad@ietf.org.

Ray Pelletier

From housley@vigilsec.com  Wed Jun 13 13:07:02 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1CB221F8474 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 13:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 sVNhozqZRWcH for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 13:07:02 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id DACEA21F846C for <ietf@ietf.org>; Wed, 13 Jun 2012 13:07:01 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id DC386F24036; Wed, 13 Jun 2012 16:07:19 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id QRQJvGyXyumG; Wed, 13 Jun 2012 16:06:44 -0400 (EDT)
Received: from [192.168.2.110] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 48733F24014; Wed, 13 Jun 2012 16:07:18 -0400 (EDT)
Subject: Re: Publishing the Tao as a web page
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <867BD23C-3581-4EDC-B4FF-973FEEBC253C@vpnc.org>
Date: Wed, 13 Jun 2012 16:06:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0C00137-E868-4017-AF5D-932848AEF6A2@vigilsec.com>
References: <CC1638DA-817E-4F2C-BD29-5EFED6CFCAEF@vpnc.org> <867BD23C-3581-4EDC-B4FF-973FEEBC253C@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 20:07:02 -0000

Paul:

It implies that the current RFC will become the initial web page =
content.  I think that is not the case.  Rather, the initial content =
will come from draft-hoffman-tao4677bis.

Do you want draft-hoffman-tao4677bis to be published as the final RFC =
version in the Tao series?

Russ


On Jun 12, 2012, at 7:01 PM, Paul Hoffman wrote:

> Based on the earlier comments, I have revised the proposal. See =
draft-hoffman-tao-as-web-page-01, diffs at =
<tools.ietf.org/rfcdiff?url2=3Ddraft-hoffman-tao-as-web-page-01>.
>=20
> --Paul Hoffman


From john-ietf@jck.com  Wed Jun 13 13:17:37 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6DB221F8467 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 13:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 jxbwXpMMfRbX for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 13:17:37 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4608821F845F for <ietf@ietf.org>; Wed, 13 Jun 2012 13:17:37 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SetuG-000KOu-P2; Wed, 13 Jun 2012 16:11:08 -0400
Date: Wed, 13 Jun 2012 16:17:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: Russ Housley <housley@vigilsec.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Publishing the Tao as a web page
Message-ID: <55DD186626302C4F0AB644C4@JcK-HP8200.jck.com>
In-Reply-To: <B0C00137-E868-4017-AF5D-932848AEF6A2@vigilsec.com>
References: <CC1638DA-817E-4F2C-BD29-5EFED6CFCAEF@vpnc.org> <867BD23C-3581-4EDC-B4FF-973FEEBC253C@vpnc.org> <B0C00137-E868-4017-AF5D-932848AEF6A2@vigilsec.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 20:17:37 -0000

--On Wednesday, June 13, 2012 16:06 -0400 Russ Housley
<housley@vigilsec.com> wrote:

> Paul:
> 
> It implies that the current RFC will become the initial web
> page content.  I think that is not the case.  Rather, the
> initial content will come from draft-hoffman-tao4677bis.
> 
> Do you want draft-hoffman-tao4677bis to be published as the
> final RFC version in the Tao series?

Russ,

If the community cares about developing and maintaining a clear
history of changes, it might be slightly advantageous to:

	(i) Make the current RFC the initial web page content
	
	(ii) Immediately replace it with a (possibly further
	revised) version of draft-hoffman-tao4677bis.
	
	(iii) Put the Tao aside until we are ready for another
	update.

I have trouble convincing myself that is worth even the marginal
extra effort it would take, but I can see the advantages if
others disagree.  On the other hand, publishing
draft-hoffman-tao4677bis in the RFC series seems to me to have
no value at all.  There should be an RFC 4677bis but it should
probably say little more than "Tao is now a web page at .... and
it is not being maintained in the RFC Series".

best,
    john




From paul.hoffman@vpnc.org  Wed Jun 13 13:44:49 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBD0C11E809B for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 13:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Z5riujQI3tTY for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 13:44:48 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0156811E8099 for <ietf@ietf.org>; Wed, 13 Jun 2012 13:44:46 -0700 (PDT)
Received: from [10.20.30.101] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q5DKiipM065167 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Wed, 13 Jun 2012 13:44:46 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: Publishing the Tao as a web page
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <B0C00137-E868-4017-AF5D-932848AEF6A2@vigilsec.com>
Date: Wed, 13 Jun 2012 13:44:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D41FAFE-6B15-4CD5-AB00-59DE8E93AC7B@vpnc.org>
References: <CC1638DA-817E-4F2C-BD29-5EFED6CFCAEF@vpnc.org> <867BD23C-3581-4EDC-B4FF-973FEEBC253C@vpnc.org> <B0C00137-E868-4017-AF5D-932848AEF6A2@vigilsec.com>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 20:44:49 -0000

On Jun 13, 2012, at 1:06 PM, Russ Housley wrote:

> Paul:
>=20
> It implies that the current RFC will become the initial web page =
content.  I think that is not the case.  Rather, the initial content =
will come from draft-hoffman-tao4677bis.

Good catch. I'll add explicit text in -02 that says that the initial =
text will come from the most recent proposed revision (and I will *not* =
put in a draft name).

> Do you want draft-hoffman-tao4677bis to be published as the final RFC =
version in the Tao series?

No. That seems silly, given that the web page will be done before the =
RFC.

On Jun 13, 2012, at 1:17 PM, John C Klensin wrote:

> If the community cares about developing and maintaining a clear
> history of changes, it might be slightly advantageous to:
>=20
> 	(i) Make the current RFC the initial web page content
> =09
> 	(ii) Immediately replace it with a (possibly further
> 	revised) version of draft-hoffman-tao4677bis.
> =09
> 	(iii) Put the Tao aside until we are ready for another
> 	update.

Yuck. The slight advantage there is hugely overwhelmed by the process =
hassles. Instead, the first web page should have a section talking about =
where it came from.

> I have trouble convincing myself that is worth even the marginal
> extra effort it would take,

Good. :-)

> but I can see the advantages if
> others disagree.  On the other hand, publishing
> draft-hoffman-tao4677bis in the RFC series seems to me to have
> no value at all.  There should be an RFC 4677bis but it should
> probably say little more than "Tao is now a web page at .... and
> it is not being maintained in the RFC Series".

That's the purpose of this document.

--Paul Hoffman


From john-ietf@jck.com  Wed Jun 13 14:50:44 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8F9821F84D6 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 14:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 K4cysAyyfaB9 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 14:50:43 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 38AAF21F84D5 for <ietf@ietf.org>; Wed, 13 Jun 2012 14:50:43 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SevMK-000KUX-KG; Wed, 13 Jun 2012 17:44:12 -0400
Date: Wed, 13 Jun 2012 17:50:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: registries and designated experts
Message-ID: <21E957EA9B7C80B51E88AE22@JcK-HP8200.jck.com>
In-Reply-To: <201206131248.q5DCmSL6028424@cichlid.raleigh.ibm.com>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp><4FD74FFC.3050905@stpeter.im> <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net> <4FD786DC.4090403@gmail.com> <B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com> <4FD849A9.7000708@gmail.com> <EDC652A26FB23C4EB6384A4584434A0407B53CA1@307622ANEX5.global.avaya.com> <201206131248.q5DCmSL6028424@cichlid.raleigh.ibm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 21:50:44 -0000

--On Wednesday, June 13, 2012 08:48 -0400 Thomas Narten
<narten@us.ibm.com> wrote:

>> Maybe an IESG statement on this respect can help here.
> 
> Is the existing text in RFC 5226 not sufficient? It contains
> extensive text about the purpose and role of designated
> experts, and was revised substantially the last time around to
> try and find a good middle ground between being overly
> prescriptive and giving experts a "blank check" to do what
> they want.
> 
> Nothing in the discussion I've seen so far in this thread
> seems at odds with or beyond what is already in RFC 5226 (but
> I may be biased).

Thomas,

FWIW, I think 5226 is ok, but that the community, especially the
community who write "Designated Experts" need to pay a little
more attention to a few phrases there than has sometimes been
the case.  For example, 5226 says:

	"Ideally, the designated expert follows specific review
	criteria as documented with the protocol that creates or
	uses the namespace."

and 

	"Experts are expected to apply applicable documented
	review or vetting procedures, or in the absence of
	documented criteria, follow generally accepted norms,
	e.g., those in Section 3.3."

My impression is that people have perhaps too often skipped
specifying specific guidelines or criteria in their definitions,
leaving the experts to fall back on good sense and the last half
of Section 3.3.  That isn't necessarily bad but can easily lead
to misunderstandings if there is actually controversy about a
proposed registration.  So I'd recommend that  the community pay
a bit more attention during Last Call to whether enough (or too
much) guidance is specified than has often been the case in the
past where we argue protocol details and do a lot of nit-picking
but mostly ignore IANA Considerations sections.

That doesn't require changes to 5226.  But, if 5226 is every
revised, it might be well to check to see if the emphasis in
what it says about this issue is in line with what we want.

    john


From derhoermi@gmx.net  Wed Jun 13 19:12:36 2012
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA5411E80D2 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 19:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 PHn2PtQprE20 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 19:12:35 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 3547E11E80CE for <ietf@ietf.org>; Wed, 13 Jun 2012 19:12:34 -0700 (PDT)
Received: (qmail invoked by alias); 14 Jun 2012 02:12:32 -0000
Received: from dslb-094-223-180-172.pools.arcor-ip.net (EHLO HIVE) [94.223.180.172] by mail.gmx.net (mp004) with SMTP; 14 Jun 2012 04:12:32 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18+B/MvrzU+G7JOlDs0K+HKSen7hwnlXlnswSlLg3 8G8LBRvFAjyOFc
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Randy Bush <randy@psg.com>
Subject: Re: registries and designated experts
Date: Thu, 14 Jun 2012 04:12:32 +0200
Message-ID: <l8bit7h15gu6go57e5o82jgkf22mj5ki69@hive.bjoern.hoehrmann.de>
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <4FD75881.3080102@dcrocker.net> <40qft756nm9l1g4q5asm5voc0jg2ng0pgl@hive.bjoern.hoehrmann.de> <m21uljep18.wl%randy@psg.com>
In-Reply-To: <m21uljep18.wl%randy@psg.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 02:12:36 -0000

* Randy Bush wrote:
>> It seems to me that if an expert reviewer thinks that something will do
>> notable harm, they should decline to make a decision and defer it to the
>> IETF at large
>
>so they are not an expert, they are a rubber stamp?  bs.

Expert reviewers should use their judgement, but that includes whether
their judgement is the right way to resolve some controversy or doubt.

I was thinking the above more in terms of something about an application
that had not been considered or forseen when the registry was created,
in which case an expert reviewer might want to say they think making
a decision is outside the confines of their role and expectations and
assumptions that have been made when the registry was set up and they
were appointed as reviewer, and reviewers should be expected to do that
as appropriate, in principle.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From stpeter@stpeter.im  Wed Jun 13 20:13:59 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D481211E80F4; Wed, 13 Jun 2012 20:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 yw8Erd64EsVp; Wed, 13 Jun 2012 20:13:59 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 57CE111E80F1; Wed, 13 Jun 2012 20:13:55 -0700 (PDT)
Received: from [192.168.0.7] (unknown [216.17.179.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 99B6840081; Wed, 13 Jun 2012 21:31:08 -0600 (MDT)
Message-ID: <4FD956F2.6070609@stpeter.im>
Date: Wed, 13 Jun 2012 21:13:54 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
References: <20120430162717.27050.41652.idtracker@ietfa.amsl.com>
In-Reply-To: <20120430162717.27050.41652.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 03:14:00 -0000

On 4/30/12 10:27 AM, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Promoting Compliance with Intellectual Property Rights (IPR)
>    Disclosure Rules'
>   <draft-polk-ipr-disclosure-03.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-05-28. 

Tim and I received actionable feedback on this list from Stephan Wenger
and Subramanian Moonesamy during the Last Call [1] [2], and Stephan has
publicly verified that his concerns were addressed [3] (SM contacted me
offlist to the same effect). A full diff is at [4], but in brief the
main changes were as follows:

1. Tightened some terminology (e.g., changed "limitations" to "licensing
requirements" and, in several places, "IETF participants" to "IETF
contributors" and "authors" to "authors and listed contributors") and
explicitly defined the terms "formal disclosure" and "informal disclosure".

2. Clarified that this document does *not* define best current practices
but instead suggests some strategies that ADs, WG chairs, and WG
secretaries might want to use.

3. Mentioned that, if informal disclosure is allowed in a meeting,
chairs ought to capture such statements in the meeting minutes.

4. Removed a misleading statement that silence could be interpreted as
as a weak "no".

5. Removed any suggestion that non-receipt of IPR disclosures could be
interpreted by ADs or WG chairs as necessarily blocking any advancement
of an I-D.

6. Tweaked the sample email messages to improve their readability and
better align with the body of the document.

Peter

[1]
https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=63103&tid=1339642625

[2]
https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=63414&tid=1339642383

[3]
https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=63596&tid=1339642383

[4] http://tools.ietf.org/rfcdiff?url2=draft-polk-ipr-disclosure-04.txt

From john@jlc.net  Wed Jun 13 23:26:12 2012
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99D3811E8088; Wed, 13 Jun 2012 23:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 gN3GIrbP+aXK; Wed, 13 Jun 2012 23:26:12 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id A904611E8087; Wed, 13 Jun 2012 23:26:11 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id CE9D933C22; Thu, 14 Jun 2012 02:26:10 -0400 (EDT)
Date: Thu, 14 Jun 2012 02:26:10 -0400
From: John Leslie <john@jlc.net>
To: Claudio Jeker <cjeker@diehard.n-r-g.com>, idr@ietf.org, ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-idr-rfc4893bis-06.txt> (BGP Support for	Four-octet AS Number Space) to Proposed Standard
Message-ID: <20120614062610.GR21341@verdi>
References: <20120612135455.GC18025@diehard.n-r-g.com> <4FD7515E.3000101@cisco.com> <4FD7886F.5090508@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4FD7886F.5090508@cisco.com>
User-Agent: Mutt/1.4.1i
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 06:26:12 -0000

Enke Chen <enkechen@cisco.com> wrote:
> On 6/12/12 7:25 AM, Stewart Bryant wrote:
> From:     Claudio Jeker <cjeker@diehard.n-r-g.com>
>> On Tue, Jun 12, 2012 at 11:30:11AM +0100, Stewart Bryant wrote:
>>> On 01/06/2012 23:00, Claudio Jeker wrote:
>>>> On Fri, Jun 01, 2012 at 11:54:44AM -0700, The IESG wrote:
>>>>> 
>>>>> The IESG has received a request from the Inter-Domain Routing WG
>>>>> (idr) to consider the following document:
>>>>> - 'BGP Support for Four-octet AS Number Space'
>>>>> <draft-ietf-idr-rfc4893bis-06.txt> as Proposed Standard
>>>>>
>>>>> Abstract
>>>>>
>>>>>  The Autonomous System (AS) number is encoded as a two-octet 
>>>>>  entity in the base BGP specification. This document describes
>>>>>  extensions to BGP to carry the Autonomous System numbers as
>>>>>  four-octet entities. This document obsoletes RFC 4893.
>>>>
>>>> Just for the sake of clarity, OpenBGPD will not do the following:
>>>>
>>>>  In addition, the path segment types AS_CONFED_SEQUENCE and
>>>>  AS_CONFED_SET [RFC5065] MUST NOT be carried in the AS4_PATH 
>>>>  attribute of an UPDATE message. A NEW BGP speaker that receives
>>>>  these path segment types in the AS4_PATH attribute of an UPDATE
>>>>  message from an OLD BGP speaker MUST discard these path segments,
>>>>  adjust the relevant attribute fields accordingly, and continue
>>>>  processing the UPDATE message. This case SHOULD be logged locally
>>>>  for analysis.
>>>>
>>>> There is no point to do this fiddeling instead we will treat this 
>>>> like any other parse error of AS4_PATH.
>>>>
>>>> Claudio

   That would make the OpenBSD implementation non-compliant with 4893bis.

>>> Since this is in last call, I have to ask whether you have objection
>>> to the publication of the above text, or have any proposed text
>>> changes?
>>
>> I see no reason to enforce AS_CONFED_SEQUENCE and AS_CONFED_SET stripping
>> on all AS4 implementations. It forces bgp implementations that don't have
>> confederation support to strip out something that will cause an error in
>> the regular path and for those systems ignoring the AS4_PATH attribute
>> is perfectly fine. I do not understand how a workaround needs to be a
>> MUST for something that is a MUST NOT at the same time? Why MUST we
>> workaround something that MUST NOT appear? Why do we need to add extra
>> code that is hard to test and maybe cause for further errors because it
>> modifies attributes in very uncommon way?

   Enke explains why this is called for in 4893bis.

   It may help to recall the IETF mantra: "We believe in rough consensus
and running code."

   At the time 4893 was designed, it was a strict requirement in IDR
that nothing could get to Proposed Standard without demonstrating
multiple implementations. In practice, this meant we only documented
something after multiple vendors had it deployed.

   Thus, 4893 went out with bugs (though I was in the rough, explaining
in general terms some weaknesses).

   One bug in particular turned out to be _very_ serious. Patching in
the AS4_PATH produced some AS_CONFED stuff very much out of context.
A fix was desperately needed, and several vendors quickly patched it.
4893bis, as I understood it, documented this fix. I'm still in the rough,
but I saw no point in objecting to documenting actual practice.

   If in fact, OpenBSD has no intention of patching for this bug, _they_
need to be considered "in the rough" (as well as non-compliant).

   If, OTOH, they wish to propose a different fix, it's possible the
IESG might ask IDR to consider it. (I can certainly imagine better ways
to resolve the problem.)

   But any fix (IMHO) _must_ dispose of out-of-context AS_CONFED stuff
that still may be in the wild.

>> I propose to remove that paragraph entierly since it does only add
>> complexity to the protocol for no reason and therefor is only a source
>> of errors without any benefit.

   (I cannot endorse that proposal. It's too likely there's legacy
equipment that allows AS_CONFED stuff to be placed in AS4_PATH.)

> Hi, Claudio:
> 
> Not sure if you are aware of the large scale outage that occurred a few 
> years ago from the leak of the confed related segments by one 
> implementation. At the time quite a few implementations were resetting 
> the sessions when receiving such updates.
> 
> While discarding the whole AS4_PATH would be simpler and less disruptive 
> (than session resetting), it would still lose the vital as-path info 
> contained in the AS4_PATH which can otherwise be recovered by 
> "repairing" the attribute.  That is why the approach specified in the 
> rfc4893bis is adopted, and it has been implemented widely.
> 
> -- Enke

--
John Leslie <john@jlc.net>

From Paul_Sangster@symantec.com  Wed Jun 13 09:53:57 2012
Return-Path: <Paul_Sangster@symantec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56E3521F8539; Wed, 13 Jun 2012 09:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 V+rP1tMCVig4; Wed, 13 Jun 2012 09:53:53 -0700 (PDT)
Received: from ecl1mtaoutpex02.symantec.com (ecl1mtaoutpex02.symantec.com [166.98.1.210]) by ietfa.amsl.com (Postfix) with ESMTP id CA19421F858A; Wed, 13 Jun 2012 09:53:50 -0700 (PDT)
X-AuditID: a66201d2-b7f6b6d000005fd4-11-4fd8c599508c
Received: from ecl1mtahubpin02.ges.symantec.com (ECL1MTAHUBPIN02.ges.symantec.com [10.48.69.202]) by ecl1mtaoutpex02.symantec.com (Symantec Messaging Gateway) with SMTP id 76.B9.24532.995C8DF4; Wed, 13 Jun 2012 16:53:45 +0000 (GMT)
Received: from [155.64.220.139] (helo=TUS1XCHHUBPIN03.SYMC.SYMANTEC.COM) by ecl1mtahubpin02.ges.symantec.com with esmtp (Exim 4.76) (envelope-from <Paul_Sangster@symantec.com>) id 1SeqpF-0000L1-7p; Wed, 13 Jun 2012 16:53:45 +0000
Received: from TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM ([155.64.220.150]) by TUS1XCHHUBPIN03.SYMC.SYMANTEC.COM ([155.64.220.139]) with mapi; Wed, 13 Jun 2012 09:53:44 -0700
From: Paul Sangster <Paul_Sangster@symantec.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-nea-pt-tls.all@tools.ietf.org" <draft-ietf-nea-pt-tls.all@tools.ietf.org>
Date: Wed, 13 Jun 2012 09:55:55 -0700
Subject: RE: GenART LC review of draft-ietf-nea-pt-tls-05
Thread-Topic: GenART LC review of draft-ietf-nea-pt-tls-05
Thread-Index: Ac1Cl9xExNAkih6WSYeHA9SkXDOg7gG388dg
Message-ID: <6E79D623502C70419A9EAB18E4D274252B8B06102F@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
References: <4fcd272e.2968b40a.55d4.ffff9de3@mx.google.com>
In-Reply-To: <4fcd272e.2968b40a.55d4.ffff9de3@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_6E79D623502C70419A9EAB18E4D274252B8B06102FTUS1XCHEVSPIN_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKIsWRmVeSWpSXmKPExsXCZeB6Snfm0Rv+BofWaFjMvTiB3eLqq88s Fs82zmex+Py2wuJvO7MDq8fOWXfZPZYs+cnk8eXyZ7YA5igum5TUnMyy1CJ9uwSujOtPlQom vGCsWPL+InsD4/vTjF2MHBwSAiYSjbequxg5gUwxiQv31rN1MXJxCAm8ZJSYvH4FM0hCSOA1 o8SanekQiVWMEp+2zmUESbAJGEjsPHKKHSQhItDIKPF1yRywDmaBJInjMzawgNgsAqoSV483 sYPYwgKWElO+TwKLiwhYSSz9MJEJwjaSaL73EizOKxAl0f1rJyvEZmuJ/ZeWgi3jFLCR2Hfl OFicEejU76fWMEHsEpe49WQ+E8QLAhJL9pxnhrBFJV4+/gdVLypxp3092MfMAvkSU85aQqwS lDg58wnLBEaxWUgmzUKomoWkCqJER2LB7k9sELa2xLKFr5lh7DMHHjMhiy9gZF/FKJOanGOY W5KYX1pSkFphYKRXXJmbCIzaZL3k/NxNjMDIXZbEeGkH4/3DuocYBTgYlXh42ffd8BdiTSwD qjzEKMHBrCTCu3olUIg3JbGyKrUoP76oNCe1+BCjNAeLkjjvhV1b/YUE0hNLUrNTUwtSi2Cy TBycUg2M2aFnX/Mf7DSawXywW6Zo0ZxzPLenH77Ad0BTKyv6wv4NaWs6zktHSFusELd6Pkd2 XSlbpnqYynnXP/1eVf32k39oZxeuflK9d3vastca5gl3n81o+yyyT2+FRHbNz+r1psmyK9KW rMnTUWc69eWVVIeOswBX4xTe7s+rOphNbugp5BlKLL6pxFKckWioxVxUnAgAH0ARXtgCAAA=
X-Mailman-Approved-At: Thu, 14 Jun 2012 09:11:48 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "nea@ietf.org" <nea@ietf.org>, 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 16:53:57 -0000

--_000_6E79D623502C70419A9EAB18E4D274252B8B06102FTUS1XCHEVSPIN_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for the detailed review, comments are in-lined...

From: Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: Monday, June 04, 2012 2:20 PM
To: draft-ietf-nea-pt-tls.all@tools.ietf.org
Cc: 'IETF'; gen-art@ietf.org
Subject: GenART LC review of draft-ietf-nea-pt-tls-05

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.



Document: draft-ietf-nea-pt-tls-05

Reviewer: Roni Even

Review Date:2012-6-4

IETF LC End Date: 2012-6-13

IESG Telechat date:



Summary: This draft is almost ready for publication as a standard track RFC=
.



Major issues:



Minor issues:

1.       In section 3.2 "Therefore, this specification requests the IANA re=
serve a TCP port number for use with the PT-TLS protocol upon publication o=
f this specification as an Internet standard RFC." I think it will  be bett=
er to have here the assigned port number and instruct the RFC editor to put=
 the correct value.



[PS:] Ok, we can reword this in hopes of getting a particular value (race c=
ondition with other upcoming RFCs).



2.       In section 3.4.2.2 last paragraph you summarize the text from sect=
ion 3.8 while in the paragraph above you provide the reference. Why do you =
need the last paragraph if 3.8 is referenced.



[PS:] The goal of this section is to introduce and summarize the different =
phases of PT-TLS.  We felt a brief discussion of the general message flow w=
as helpful to the reader to understand what occurs during this phase (simil=
ar to what we did in the other sub-sections).  Your correct that this infor=
mation is covered later in more detail.



3.       In various places you refer to SMI 0 as IETF SMI number while acco=
rding to the table it is IANA SMI number.



[PS:] I presume this is about the PEN 0 being for the IETF.  Correct, it's =
the IETF's name space that administered by the IANA.  What text would you l=
ike to see to make this more clear?  Can we do it in one place, for example=
 stating that the IETF name space is administered by the IANA?



4.       I assume that all implementations MUST support message type vendor=
 ID 0. Is this mentioned?



[PS:] The purpose of this section was just to summarize and enumerate the m=
essage types for vendor id 0.   I don't think it's a general rule that any =
message type defined in the IETF (IANA :)) name space must (or should be) s=
upported by all implementations.  It will vary depending on the purpose of =
the message so that normative language is included in the descriptions of t=
he message.



5.       In section 3.5 and 6.1 you propose a policy of "Expert Review with=
 Specification Required ". I think that according to RFC5226 expert review =
is implied if you select a specification required policy.



[PS:] I agree, it says "Specification Required also implies use of a Design=
ated Expert".  The policy is just "Specification Required" so we could remo=
ve the "Expert Review with" and make it clear it's the Specification Requir=
ed IANA policy.



6.       In section 3.6 on 9+ "Recipients of messages   of type 9 or higher=
 that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message T=
ype of a received PT-TLS message MUST respond with a Type Not Supported PT-=
TLS error code in a PT-TLS Error message." I think this is true only for Me=
ssage Type Vendor ID 0.



[PS:] Thanks will reword this section to make it more clear.



7.       In 3.7.1 for Max vers and prefs ver you say that they MUST be set =
to 1. I think it will be more correct here to say SHOULD since you explain =
afterwards that they may have other values.



[PS:] I think this is a MUST.  The next sentence just points out that this =
normative text might change in a future revision (which is not currently pl=
anned).



8.       In section 3.7.2 "the recipient SHOULD send". Why not make it a MU=
ST here.



[PS:] I ok with making this change, let's see what others think ...



9.       In section 3.7.2 "The version selected MUST be within the Min Vers=
 to Max Vers inclusive range sent in the Version Request   Message" I was e=
xpecting to see pref ver here.



[PS:] Perf is just an informational (hint) preference.



10.   In section 3.8.3 " The SASL client authentication starts when the NEA=
 Server  enters the PT-TLS Negotiation phase and its policy indicates  that=
 an authentication of the NEA Client is necessary but was not performed dur=
ing the TLS handshake protocol " my read of  section 3.8 second paragraph i=
s that it can be done even if was done in the TLS handshake so the last par=
t of the sentence is not correct, if there is a policy you do it anyhow. Th=
is comment is also for the third paragraph.



[PS:] Thanks, this was supposed to be an example.  Will fix these.



11.   In section 3.9 I noticed that you propose to send the entire original=
 message. Isn't it enough to send only the message identifier. This is base=
d on the last sentence of this section.



[PS:] Not "the entire original message" as its at most the first 1024 bytes=
 of the offending message.  This allows the recipient to either caches rece=
ntly sent messages and/or message identifiers when determining what caused =
the error.  We thought this flexibility was useful and had very little cost=
.



12.   Most of the text in section 6.1 repeats RFC5226 but in your words. Ar=
e you trying to change some of RFC5226 text if not why write it in differen=
t words?



[PS:] We were hoping to emphasize the aspects of 5226 that are most importa=
nt to this specification.  We weren't trying to change how the IANA policy =
was interpreted.  Did you think we did so?  Is there a portion of this text=
 that is most troubling or was this just a question?









Nits/editorial comments:


--_000_6E79D623502C70419A9EAB18E4D274252B8B06102FTUS1XCHEVSPIN_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2023900102;
	mso-list-type:hybrid;
	mso-list-template-ids:-625979886 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Thanks for the detailed review, comments are in-lined&#8230;<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:=
p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:solid blue 1=
.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:s=
olid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D=
'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><sp=
an style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even =
[mailto:ron.even.tlv@gmail.com] <br><b>Sent:</b> Monday, June 04, 2012 2:20=
 PM<br><b>To:</b> draft-ietf-nea-pt-tls.all@tools.ietf.org<br><b>Cc:</b> 'I=
ETF'; gen-art@ietf.org<br><b>Subject:</b> GenART LC review of draft-ietf-ne=
a-pt-tls-05<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p><p class=3DMsoNormal>I am the assigned Gen-ART reviewer for thi=
s draft. For background on Gen-ART, please see the FAQ at &lt;<a href=3D"ht=
tp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank">ht=
tp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Please res=
olve these comments along with any other Last Call comments you may receive=
.<o:p></o:p></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
PlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif=
"'>Document: draft-ietf-nea-pt-tls-05<o:p></o:p></span></p><p class=3DMsoPl=
ainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'=
>Reviewer: Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review Date:2012=
&#8211;6&#8211;4<o:p></o:p></span></p><p class=3DMsoPlainText><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC End Date: =
2012&#8211;6&#8211;13<o:p></o:p></span></p><p class=3DMsoPlainText><span st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG Telechat d=
ate:<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:=
11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p c=
lass=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","=
sans-serif"'>Summary: This draft is almost ready for publication as a stand=
ard track RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'=
font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"=
Calibri","sans-serif"'>Major issues:<o:p></o:p></span></p><p class=3DMsoPla=
inText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif"'>Minor issues:<o:p></o:p></span=
></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;m=
so-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>1.<sp=
an style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; </span></span></span><![endif]><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif"'>In section 3.2 &#8220;Therefore, this specifica=
tion requests the IANA reserve a TCP port number for use with the PT-TLS pr=
otocol upon publication of this specification as an Internet standard RFC.&=
#8221; I think it will&nbsp; be better to have here the assigned port numbe=
r and instruct the RFC editor to put the correct value.<o:p></o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
PlainText><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>[PS:] Ok, we can reword this in hopes of getting a p=
articular value (race condition with other upcoming RFCs).<o:p></o:p></span=
></i></b></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:=
l0 level1 lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>2.<span style=
=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </sp=
an></span></span><![endif]><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif"'>In section 3.4.2.2 last paragraph you summarize the tex=
t from section 3.8 while in the paragraph above you provide the reference. =
Why do you need the last paragraph if 3.8 is referenced.<o:p></o:p></span><=
/p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oPlainText><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'>[PS:] The goal of this section is to introduce and =
summarize the different phases of PT-TLS.&nbsp; We felt a brief discussion =
of the general message flow was helpful to the reader to understand what oc=
curs during this phase (similar to what we did in the other sub-sections).&=
nbsp; Your correct that this information is covered later in more detail.<o=
:p></o:p></span></i></b></p><p class=3DMsoPlainText><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-=
.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore=
'>3.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; </span></span></span><![endif]><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif"'>In various places you refer to SMI 0 as =
IETF SMI number while according to the table it is IANA SMI number.<o:p></o=
:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'>[PS:] I presume this is about the PEN 0 =
being for the IETF.&nbsp; Correct, it&#8217;s the IETF&#8217;s name space t=
hat administered by the IANA. &nbsp;What text would you like to see to make=
 this more clear?&nbsp; Can we do it in one place, for example stating that=
 the IETF name space is administered by the IANA?<o:p></o:p></span></i></b>=
</p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DM=
soPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1=
 lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif"'><span style=3D'mso-list:Ignore'>4.<span style=3D'font:=
7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span=
></span><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif"'>I assume that all implementations MUST support message type vend=
or ID 0. Is this mentioned?<o:p></o:p></span></p><p class=3DMsoPlainText><s=
pan style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F4=
97D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:=
] The purpose of this section was just to summarize and enumerate the messa=
ge types for vendor id 0.&nbsp; &nbsp;I don&#8217;t think it&#8217;s a gene=
ral rule that any message type defined in the IETF (IANA </span></i></b><b>=
<i><span style=3D'font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</=
span></i></b><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>) name space must (or should be) supported by all=
 implementations.&nbsp; It will vary depending on the purpose of the messag=
e so that normative language is included in the descriptions of the message=
.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-inden=
t:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ign=
ore'>5.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; </span></span></span><![endif]><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif"'>In section 3.5 and 6.1 you propose a =
policy of &#8220;Expert Review with Specification Required &#8220;. I think=
 that according to RFC5226 expert review is implied if you select a specifi=
cation required policy.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] I a=
gree, it says &#8220;Specification Required also implies use of a Designate=
d Expert&#8221;.&nbsp; The policy is just &#8220;Specification Required&#82=
21; so we could remove the &#8220;Expert Review with&#8221; and make it cle=
ar it&#8217;s the Specification Required IANA policy. <o:p></o:p></span></i=
></b></p><p class=3DMsoPlainText style=3D'margin-left:10.5pt'><b><i><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>=
<o:p>&nbsp;</o:p></span></i></b></p><p class=3DMsoPlainText style=3D'margin=
-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New Roman"'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 3.6 o=
n 9+ &#8220;Recipients of messages&nbsp;&nbsp; of type 9 or higher that do =
not support the PT-TLS Message Type Vendor ID and PT-TLS Message Type of a =
received PT-TLS message MUST respond with a Type Not Supported PT-TLS error=
 code in a PT-TLS Error message.&#8221; I think this is true only for Messa=
ge Type Vendor ID 0.<o:p></o:p></span></p><p class=3DMsoPlainText><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] Thanks=
 will reword this section to make it more clear.<o:p></o:p></span></i></b><=
/p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif"'><span style=3D'mso-list:Ignore'>7.<span style=3D'font:7=
.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>=
</span><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif"'>In 3.7.1 for Max vers and prefs ver you say that they MUST be set=
 to 1. I think it will be more correct here to say SHOULD since you explain=
 afterwards that they may have other values.<o:p></o:p></span></p><p class=
=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText>=
<b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";co=
lor:#1F497D'>[PS:] I think this is a MUST.&nbsp; The next sentence just poi=
nts out that this normative text might change in a future revision (which i=
s not currently planned).<o:p></o:p></span></i></b></p><p class=3DMsoPlainT=
ext><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";colo=
r:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=3D'mar=
gin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLis=
ts]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><sp=
an style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New Roman"'=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 3.=
7.2 &#8220;the recipient SHOULD send&#8221;. Why not make it a MUST here.<o=
:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>[PS:] I ok with making this change=
, let&#8217;s see what others think &#8230;<o:p></o:p></span></i></b></p><p=
 class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlai=
nText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'=
><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif"'><span style=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt =
"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></spa=
n><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-ser=
if"'>In section 3.7.2 &#8220;The version selected MUST be within the Min Ve=
rs to Max Vers inclusive range sent in the Version Request&nbsp;&nbsp; Mess=
age&#8221; I was expecting to see pref ver here.<o:p></o:p></span></p><p cl=
ass=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainTe=
xt><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"=
;color:#1F497D'>[PS:] Perf is just an informational (hint) preference.<o:p>=
</o:p></span></i></b></p><p class=3DMsoPlainText><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25=
in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>1=
0.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span><=
/span><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif"'>In section 3.8.3 &#8220; The SASL client authentication starts whe=
n the NEA Server&nbsp; enters the PT-TLS Negotiation phase and its policy i=
ndicates&nbsp; that an authentication of the NEA Client is necessary but wa=
s not performed during the TLS handshake protocol &#8220; my read of&nbsp; =
section 3.8 second paragraph is that it can be done even if was done in the=
 TLS handshake so the last part of the sentence is not correct, if there is=
 a policy you do it anyhow. This comment is also for the third paragraph.<o=
:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>[PS:] Thanks, this was supposed to=
 be an example.&nbsp; Will fix these.<o:p></o:p></span></i></b></p><p class=
=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if=
 !supportLists]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif"'><span style=3D'mso-list:Ignore'>11.<span style=3D'font:7.0pt "Time=
s New Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 3.9 I noticed=
 that you propose to send the entire original message. Isn&#8217;t it enoug=
h to send only the message identifier. This is based on the last sentence o=
f this section.<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&n=
bsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] Not &#8220;=
the entire original message&#8221; as its at most the first 1024 bytes of t=
he offending message.&nbsp; This allows the recipient to either caches rece=
ntly sent messages and/or message identifiers when determining what caused =
the error. &nbsp;We thought this flexibility was useful and had very little=
 cost.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span style=3D'=
font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-=
indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'=
font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-lis=
t:Ignore'>12.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </sp=
an></span></span><![endif]><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif"'>Most of the text in section 6.1 repeats RFC5226 but in =
your words. Are you trying to change some of RFC5226 text if not why write =
it in different words?<o:p></o:p></span></p><p class=3DMsoPlainText><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] We w=
ere hoping to emphasize the aspects of 5226 that are most important to this=
 specification.&nbsp; We weren&#8217;t trying to change how the IANA policy=
 was interpreted.&nbsp; Did you think we did so?&nbsp; Is there a portion o=
f this text that is most troubling or was this just a question?<o:p></o:p><=
/span></i></b></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f"'>Nits/editorial comments:<o:p></o:p></span></p><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p></div></div></body></html>=

--_000_6E79D623502C70419A9EAB18E4D274252B8B06102FTUS1XCHEVSPIN_--

From Paul_Sangster@symantec.com  Wed Jun 13 21:00:21 2012
Return-Path: <Paul_Sangster@symantec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A75A11E80F6; Wed, 13 Jun 2012 21:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 gnuNO5KNDGsO; Wed, 13 Jun 2012 21:00:16 -0700 (PDT)
Received: from ecl1mtaoutpex02.symantec.com (ecl1mtaoutpex02.symantec.com [166.98.1.210]) by ietfa.amsl.com (Postfix) with ESMTP id 8425111E80EB; Wed, 13 Jun 2012 21:00:16 -0700 (PDT)
X-AuditID: a66201d2-b7f756d000004ee0-14-4fd961cf045d
Received: from tus1opsmtapin02.ges.symantec.com (tus1opsmtapin02.ges.symantec.com [192.168.214.44]) by ecl1mtaoutpex02.symantec.com (Symantec Messaging Gateway) with SMTP id 65.F2.20192.FC169DF4; Thu, 14 Jun 2012 04:00:15 +0000 (GMT)
Received: from [155.64.220.138] (helo=TUS1XCHHUBPIN02.SYMC.SYMANTEC.COM) by tus1opsmtapin02.ges.symantec.com with esmtp (Exim 4.76) (envelope-from <Paul_Sangster@symantec.com>) id 1Sf1EE-0004Cu-Uu; Thu, 14 Jun 2012 04:00:14 +0000
Received: from TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM ([155.64.220.150]) by TUS1XCHHUBPIN02.SYMC.SYMANTEC.COM ([172.24.185.246]) with mapi; Wed, 13 Jun 2012 21:00:15 -0700
From: Paul Sangster <Paul_Sangster@symantec.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, "draft-ietf-nea-pt-tls.all@tools.ietf.org" <draft-ietf-nea-pt-tls.all@tools.ietf.org>, "nea@ietf.org" <nea@ietf.org>
Date: Wed, 13 Jun 2012 21:02:31 -0700
Subject: RE: APPSDIR review of draft-ietf-nea-pt-tls-04
Thread-Topic: APPSDIR review of draft-ietf-nea-pt-tls-04
Thread-Index: Ac1ChIONzSZhkDZ1SQ2GmKWHIfcYdgHWLbtQ
Message-ID: <6E79D623502C70419A9EAB18E4D274252B8B061618@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
References: <4FCD0614.5050902@isode.com>
In-Reply-To: <4FCD0614.5050902@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOIsWRmVeSWpSXmKPExsVyYMU1Hd3ziTf9Df5NULaYsbrIYu7FCewW zzbOZ7H4/LbCgcVjyZKfTB6nmg09vlz+zBbAHMVlk5Kak1mWWqRvl8CVMfvdecaCPr2Knztn sjUwvlLpYuTgkBAwkXi6sryLkRPIFJO4cG89WxcjF4eQwGtGiX235jDBOWuXrGMHqRISWMUo cXmOIojNJmAgsfPIKbC4iMBKRom9f7NAbGYBZYmnm0CaOTlYBFQlDvfdZgSxhQXMJdqmXmaB qLeQOHygjRXCNpJ43beGDcTmFYiSODD7HdQuDYmjc1cyg9icApoS2482gs1kBLr0+6k1TBC7 xCVuPZnPBPGBgMSSPeeZIWxRiZeP/7FC1ItK3GlfzwhRryOxYPcnNghbW2LZwtfMEHsFJU7O fMIygVF8FpKxs5C0zELSMgtJywJGllWMMqnJOYa5JYn5pSUFqRUGRnrFlbmJwMhL1kvOz93E CIy+ZUmMl3Yw3j+se4hRgINRiYd3YthNfyHWxDKgykOMEhzMSiK8zxSAQrwpiZVVqUX58UWl OanFhxilOViUxHkv7NrqLySQnliSmp2aWpBaBJNl4uCUamDMuL/A5LPQLkcH2dOXds5ffmv7 4wlvPGdnMDufdDj8W6vdYQGfg+1LS/MJ/2/cKe1UvpY3vYEr03nihgc7Dktrf5zJaNOxTj7P QKd247mCqMknCx5Zdnr6b567dh6j15r3HitqC9fePcf6+FGjvnYI27Ovi+Iv5Km8Cah49fto +PsjqeIL+r5nKbEUZyQaajEXFScCAAyyTZ26AgAA
X-Mailman-Approved-At: Thu, 14 Jun 2012 09:11:48 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 04:00:21 -0000

> -----Original Message-----
> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]
> Sent: Monday, June 04, 2012 12:02 PM
> To: apps-discuss@ietf.org; draft-ietf-nea-pt-tls.all@tools.ietf.org
> Cc: ietf@ietf.org
> Subject: APPSDIR review of draft-ietf-nea-pt-tls-04
>=20
> I have been selected as the Applications Area Directorate reviewer for
> this draft (for background on APPSDIR, please see
> http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectora
> te ).
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive. Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.  The review is not
> copied to the IESG as the Last Call has not been announced yet.
>=20
> Document: draft-ietf-nea-pt-tls-04
> Title: PT-TLS: A TCP-based Posture Transport (PT) Protocol
> Reviewer: Alexey Melnikov
> Review Date: June 4, 2012
>=20
> Summary: This document is almost ready for publication as a Proposed
> Standard, although some [mostly] SASL related issues remain.
>=20
> This document specifies PT-TLS, a TCP-based Posture Transport (PT)
> protocol.  The PT-TLS protocol carries the Network Endpoint
> Assessment (NEA) message exchange under the protection of a Transport
> Layer Security (TLS) secured tunnel.
>=20
> (Note, I've reviewed -04, but I think all of this still applies to -
> 05.)
>=20
>=20
> Major:
>=20
> In 3.4.2.1: RFC 6125 use details are missing. You need to describe
> whether CN-IDs and SRV-IDs are allowed, whether wildcards are allowed,
> etc. I can suggest some details.

[PS:] Since you weren't happy with our first attempt to address this commen=
t, we would like to take you up on your kind offer to provide suggestions. =
 Maybe we could do this off-line and included the text in -06?

>=20
>=20
> Minor:
>=20
> In Section 3.2: This document is not yet Internet Standard, it will be
> Proposed Standard. Suggest saying "Publication on Standards Track"
> instead instead of "Internet Standard". The same issue in the IANA
> consideration section.

[PS:] This sentence will be re-written to address the gen-art comment so th=
e new text won't have this issue.

>=20
> In 3.8.1: I think one instance of "SASL authentication messages" -->
> "SASL authentication mechanisms". Otherwise this sentence is out of
> place, as you are not talking about SASL messages.

[PS:] Will make it more clear the relationship between SASL messages in PT-=
TLS and the SASL mechanism exchanges inside the messages.  The sentence men=
tioned is about the PT-TLS client authentication messages.

>=20
> In 3.8.4: in SASL the server doesn't return abort as an error code, it
> just fails the authentication exchange. I suggest removing it as a
> choice.

[PS:] This text was attempting to support the abort as described in RFC4422=
 which says:

3.5.  Aborting Authentication Exchanges

   A client or server may desire to abort an authentication exchange if
   it is unwilling or unable to continue (or enter into).

   A client may abort the authentication exchange by sending a message,
   the particulars of which are protocol specific, to the server,
   indicating that the exchange is aborted.  The server may be required
   by the protocol to return a message in response to the client's abort
   message.

   Likewise, a server may abort the authentication exchange by sending a
   message, the particulars of which are protocol specific, to the
   client, indicating that the exchange is aborted.

[PS]: Is this an unacceptable way to do this? =20

>=20
> In 3.8.7: you define the Reserved field which I assume is used for
> padding? If yes, then you will not get proper alignment for the next
> field, as SASL mechanism names are variable length. (If you intended
> that they are always sent as 20 bytes, then this is missing from the
> document.)

[PS:] Sure, word alignment would have been a good reason for doing this but=
 we thought more about byte alignment.  We also thought having these bits a=
vailable could be useful later (e.g. for indicating preference or some othe=
r semantic that could impact the mechanism selection).   Since we didn't ne=
ed an entire byte for the Mech Len we thought it made sense to at least byt=
e align the Mechanism Name and the cost of 3 bits for some future purpose m=
ade sense.

>=20
> In 3.8.10:
>=20
> The Abort choice is really not needed (as per above).
>=20
> Also, can you give me an example of when the Mechanism Failure will be
> returned instead of just Failure?

[PS:] The document gives the example of authentication failure (incorrect c=
redential) where mechanism failure is when the mechanism logic detects a fa=
ilure in processing the authentication request that isn't related to the us=
er's input (e.g. malloc error).

>=20
> In 3.9: Failed Authentication error code - how does this differ from
> SASL Authentication result with Failure code?

[PS:] Hmm, I'm going to have to look into this more.  One way they are diff=
erent is the fact that the NEA Client is not allowed to send the SASL Resul=
t TLV so can't use the Failure code but it could send a Failed Authenticati=
on error code in the PT-TLS Error Message.

>=20
> In 4.1.2, second block, the first bullet: I think you meant "client"
> instead of the "server".

[PS:] Thanks, good catch

>=20
>=20
> Question (might not be an issue):
>=20
> In 6.2: is it possible to register a vendor specific value without a
> specification?

[PS:] In order to be placed in the IANA registry a permanent specification =
is required (as mentioned in section 6.1).   Of course vendors are free to =
use values in their name space without registering them with the IANA.

>=20
> The same question for 6.3.
>=20
>=20
> Nits: None


From Paul_Sangster@symantec.com  Wed Jun 13 21:09:02 2012
Return-Path: <Paul_Sangster@symantec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E238311E80B3; Wed, 13 Jun 2012 21:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 FJ-ofcgXiI6F; Wed, 13 Jun 2012 21:09:01 -0700 (PDT)
Received: from tus1smtoutpex02.symantec.com (tus1smtoutpex02.symantec.com [216.10.195.242]) by ietfa.amsl.com (Postfix) with ESMTP id D95D811E8073; Wed, 13 Jun 2012 21:09:00 -0700 (PDT)
X-AuditID: d80ac3f2-b7fb36d000006edb-f9-4fd963dbb8a3
Received: from ecl1mtahubpin02.ges.symantec.com (ECL1MTAHUBPIN02.ges.symantec.com [10.48.69.202]) by tus1smtoutpex02.symantec.com (Symantec Brightmail Gateway out) with SMTP id 98.82.28379.CD369DF4; Thu, 14 Jun 2012 04:09:00 +0000 (GMT)
Received: from [155.64.220.137] (helo=TUS1XCHHUBPIN01.SYMC.SYMANTEC.COM) by ecl1mtahubpin02.ges.symantec.com with esmtp (Exim 4.76) (envelope-from <Paul_Sangster@symantec.com>) id 1Sf1Mh-0002dD-JI; Thu, 14 Jun 2012 04:08:59 +0000
Received: from TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM ([155.64.220.150]) by TUS1XCHHUBPIN01.SYMC.SYMANTEC.COM ([155.64.220.137]) with mapi; Wed, 13 Jun 2012 21:08:59 -0700
From: Paul Sangster <Paul_Sangster@symantec.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "draft-ietf-nea-pt-tls.all@tools.ietf.org" <draft-ietf-nea-pt-tls.all@tools.ietf.org>
Date: Wed, 13 Jun 2012 21:11:17 -0700
Subject: RE: [apps-discuss] APPSDIR review of draft-ietf-nea-pt-tls-04
Thread-Topic: [apps-discuss] APPSDIR review of draft-ietf-nea-pt-tls-04
Thread-Index: Ac1JUdVFSXL4cIl6SCmIW/z3GYOE9QAkS6rw
Message-ID: <6E79D623502C70419A9EAB18E4D274252B8B06161A@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
References: <4FCD0614.5050902@isode.com> <4FD86FB2.2050002@isode.com>
In-Reply-To: <4FD86FB2.2050002@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNIsWRmVeSWpSXmKPExsXCZeB6SvdO8k1/g019ohYzVhdZrH65gs1i 7sUJ7BbPNs5ncWDxWLLkJ5PHqWZDjy+XP7MFMEdx2aSk5mSWpRbp2yVwZexdu4ytYLJwxddD 61kbGHfydzFyckgImEicm3WLCcIWk7hwbz1bFyMXh5DAO0aJ/SveMEE4rxklzh7awgzhrGKU WDz7EDtIC5uAgcTOI6fYQRIiArsZJR6c/8gGkmAWUJZ4umkO2FwWAVWJlYfvg8WFBdwkvi/p ZQGxRQTcJW683s8MYRtJvL71D8zmFYiS+LW8GaxXSMBV4sXctWBxTgFNiV1bvoPNYQS69fup NUwQu8Qlbj2ZD/WDgMSSPeeZIWxRiZeP/7FC1ItK3GlfzwhRryOxYPcnqDu1JZYtfA21V1Di 5MwnLBMYxWchGTsLScssJC2zkLQsYGRZxShTUlpsWJxbkl9aUpBaYWCkV1yZmwiMwGS95Pzc TYzAKLzBdfjTDsYbSxUPMQpwMCrx8KoAo1OINbEMqPIQowQHs5II7zMFoBBvSmJlVWpRfnxR aU5q8SFGaQ4WJXHeD7u3+gsJpCeWpGanphakFsFkmTg4pRoYPc+5vN0kvo73V1Bg617vIKN1 rExtXKdks7/o3Q9J2XS2Zs7+fkFx7fWG1XnvZjp/MbgidMsrYd1vGZWtV44a65UvmmJc9+Od ZKbmm1DT16yXHa6lWz2+9jBD4fvR7as+/9nz7NWE1+Kf5jNccFq5fOLj+eVN6hq/uRR+Xw4r vv3+Fav3ykrBr0osxRmJhlrMRcWJANJEHki+AgAA
X-Mailman-Approved-At: Thu, 14 Jun 2012 09:11:48 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 04:09:02 -0000

> -----Original Message-----
> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]
> Sent: Wednesday, June 13, 2012 3:47 AM
> To: apps-discuss@ietf.org; draft-ietf-nea-pt-tls.all@tools.ietf.org
> Cc: ietf@ietf.org
> Subject: Re: [apps-discuss] APPSDIR review of draft-ietf-nea-pt-tls-04
>=20
> On 04/06/2012 20:01, Alexey Melnikov wrote:
> > I have been selected as the Applications Area Directorate reviewer
> for
> > this draft (for background on APPSDIR, please see
> >
> http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectora
> te
> > ).
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive. Please wait for direction from your document
> shepherd
> > or AD before posting a new version of the draft.  The review is not
> > copied to the IESG as the Last Call has not been announced yet.
> >
> > Document: draft-ietf-nea-pt-tls-04
> > Title: PT-TLS: A TCP-based Posture Transport (PT) Protocol
> > Reviewer: Alexey Melnikov
> > Review Date: June 4, 2012
> >
> > Summary: This document is almost ready for publication as a Proposed
> > Standard, although some [mostly] SASL related issues remain.
> >
> > This document specifies PT-TLS, a TCP-based Posture Transport (PT)
> > protocol.  The PT-TLS protocol carries the Network Endpoint
> > Assessment (NEA) message exchange under the protection of a Transport
> > Layer Security (TLS) secured tunnel.
> >
> > (Note, I've reviewed -04, but I think all of this still applies to -
> 05.)
> Additional issues in -05:
>=20
> 1) I didn't find the updated text prohibiting TLS renegotiation to be
> any clearer in -05? Can you maybe try to explain what is allowed and
> what is not?

[PS:] The editors will discuss this more and provide a response.

>=20
> 2) In the IANA Considerations:
>=20
> The PEN 0 (IETF) PT-TLS Message Type values between 9 and 2^32-2
> inclusive are allocated for future assignment by the IANA.  The value
> 2^32-1 is permanently reserved and is not to be allocated.
>=20
> Whom does the last sentence apply to? This registry? Or the IANA PEN
> registry being documented by draft-liang-iana-pen?

[PS:] I'm assuming your asking about the text at the bottom of section 6.2.=
 Registry for PT-TLS Message Types immediately below the table that defines=
 registry values 0 thru 8 for PEN=3D0.  It refers to this specific registry=
 not the PEN registry.


From anandmadhab@gmail.com  Thu Jun 14 10:23:17 2012
Return-Path: <anandmadhab@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49A0321F86DB for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 10:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.403
X-Spam-Level: 
X-Spam-Status: No, score=-0.403 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_16=0.6, J_CHICKENPOX_22=0.6, J_CHICKENPOX_52=0.6, MIME_QP_LONG_LINE=1.396, 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 A24Mt3huV4WQ for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 10:23:15 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3571B21F86D4 for <ietf@ietf.org>; Thu, 14 Jun 2012 10:23:15 -0700 (PDT)
Received: by dacx6 with SMTP id x6so2854842dac.31 for <ietf@ietf.org>; Thu, 14 Jun 2012 10:23:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; bh=qnz3ESJLlS92AUKIxGtzb8DAFMDCkEsIK4J0SC3k8ks=; b=eiortYvcpxymWdcmC5vH5ni7vOpY8Hqc/aPX7ZHlMXJM0yMdIFAEx9YfPuqIcsYaiH 2iOOn4QuXZ3IARsD73SxBnb/dqQZYhjvsJHW9E66l9DP87QeRoDaW0OwL4E4XLfp8IRa j158noeOF+0Th5SKQrUQ/s8j3ZW4U8HqABu2pTnVJ3f1QHld1E6LQ5KTfy6MdH363nGG MJNgejO4R+PyqTVaonndOF3W7MGeRgPFXUVAeY+JRZfyWWoNqnCd4HGVOCaqfHOZoBiG IIbFo6N968YLWgBbOLkyV8yeEohlobz15Dpeul2rszFwpnyKNth4GYZk5vdki29MTisA 13vw==
Received: by 10.68.197.136 with SMTP id iu8mr10134678pbc.111.1339694593937; Thu, 14 Jun 2012 10:23:13 -0700 (PDT)
Received: from [192.168.1.2] ([122.167.8.184]) by mx.google.com with ESMTPS id pq1sm10147550pbb.5.2012.06.14.10.23.11 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Jun 2012 10:23:13 -0700 (PDT)
Subject: Re: Ietf Digest, Vol 49, Issue 40
References: <mailman.946.1339690308.3336.ietf@ietf.org>
From: anandmadhab@gmail.com
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (8L1)
In-Reply-To: <mailman.946.1339690308.3336.ietf@ietf.org>
Message-Id: <8B147500-8995-45F4-8DE2-476DB216DB1E@gmail.com>
Date: Thu, 14 Jun 2012 22:53:47 +0530
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (iPad Mail 8L1)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 17:23:17 -0000

Hey bro how are you I don't know what to now I am totally free so just hangi=
ng around nothing to everything is just fine I am watching yaadein movie on s=
ome channel I don't even know the name of the channel.. Ha ha...=20


Sent from my iPad

On 14-Jun-2012, at 21:41, ietf-request@ietf.org wrote:

> If you have received this digest without all the individual message
> attachments you will need to update your digest options in your list
> subscription.  To do so, go to=20
>=20
> https://www.ietf.org/mailman/listinfo/ietf
>=20
> Click the 'Unsubscribe or edit options' button, log in, and set "Get
> MIME or Plain Text Digests?" to MIME.  You can set this option
> globally for all the list digests you receive at this point.
>=20
>=20
>=20
> Send Ietf mailing list submissions to
>    ietf@ietf.org
>=20
> To subscribe or unsubscribe via the World Wide Web, visit
>    https://www.ietf.org/mailman/listinfo/ietf
> or, via email, send a message with subject or body 'help' to
>    ietf-request@ietf.org
>=20
> You can reach the person managing the list at
>    ietf-owner@ietf.org
>=20
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ietf digest..."
>=20
>=20
> Today's Topics:
>=20
>   1. Re: Publishing the Tao as a web page (Russ Housley)
>   2. Re: Publishing the Tao as a web page (John C Klensin)
>   3. Re: Publishing the Tao as a web page (Paul Hoffman)
>   4. Re: registries and designated experts (John C Klensin)
>   5. Re: registries and designated experts (Bjoern Hoehrmann)
>   6. Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting
>      Compliance    with Intellectual Property Rights (IPR) Disclosure
>      Rules) to    Informational RFC (Peter Saint-Andre)
>   7. Re: Last Call: <draft-ietf-idr-rfc4893bis-06.txt> (BGP
>      Support    for    Four-octet AS Number Space) to Proposed Standard
>      (John Leslie)
>   8. RE: GenART LC review of draft-ietf-nea-pt-tls-05 (Paul Sangster)
>=20
>=20
> ----------------------------------------------------------------------
>=20
> Message: 1
> Date: Wed, 13 Jun 2012 16:06:59 -0400
> From: Russ Housley <housley@vigilsec.com>
> To: Paul Hoffman <paul.hoffman@vpnc.org>
> Cc: IETF discussion list <ietf@ietf.org>
> Subject: Re: Publishing the Tao as a web page
> Message-ID: <B0C00137-E868-4017-AF5D-932848AEF6A2@vigilsec.com>
> Content-Type: text/plain; charset=3Dus-ascii
>=20
> Paul:
>=20
> It implies that the current RFC will become the initial web page content. =
 I think that is not the case.  Rather, the initial content will come from d=
raft-hoffman-tao4677bis.
>=20
> Do you want draft-hoffman-tao4677bis to be published as the final RFC vers=
ion in the Tao series?
>=20
> Russ
>=20
>=20
> On Jun 12, 2012, at 7:01 PM, Paul Hoffman wrote:
>=20
>> Based on the earlier comments, I have revised the proposal. See draft-hof=
fman-tao-as-web-page-01, diffs at <tools.ietf.org/rfcdiff?url2=3Ddraft-hoffm=
an-tao-as-web-page-01>.
>>=20
>> --Paul Hoffman
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 2
> Date: Wed, 13 Jun 2012 16:17:26 -0400
> From: John C Klensin <john-ietf@jck.com>
> To: Russ Housley <housley@vigilsec.com>, Paul Hoffman
>    <paul.hoffman@vpnc.org>
> Cc: IETF discussion list <ietf@ietf.org>
> Subject: Re: Publishing the Tao as a web page
> Message-ID: <55DD186626302C4F0AB644C4@JcK-HP8200.jck.com>
> Content-Type: text/plain; charset=3Dus-ascii
>=20
>=20
>=20
> --On Wednesday, June 13, 2012 16:06 -0400 Russ Housley
> <housley@vigilsec.com> wrote:
>=20
>> Paul:
>>=20
>> It implies that the current RFC will become the initial web
>> page content.  I think that is not the case.  Rather, the
>> initial content will come from draft-hoffman-tao4677bis.
>>=20
>> Do you want draft-hoffman-tao4677bis to be published as the
>> final RFC version in the Tao series?
>=20
> Russ,
>=20
> If the community cares about developing and maintaining a clear
> history of changes, it might be slightly advantageous to:
>=20
>    (i) Make the current RFC the initial web page content
>   =20
>    (ii) Immediately replace it with a (possibly further
>    revised) version of draft-hoffman-tao4677bis.
>   =20
>    (iii) Put the Tao aside until we are ready for another
>    update.
>=20
> I have trouble convincing myself that is worth even the marginal
> extra effort it would take, but I can see the advantages if
> others disagree.  On the other hand, publishing
> draft-hoffman-tao4677bis in the RFC series seems to me to have
> no value at all.  There should be an RFC 4677bis but it should
> probably say little more than "Tao is now a web page at .... and
> it is not being maintained in the RFC Series".
>=20
> best,
>    john
>=20
>=20
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 3
> Date: Wed, 13 Jun 2012 13:44:44 -0700
> From: Paul Hoffman <paul.hoffman@vpnc.org>
> To: IETF discussion list <ietf@ietf.org>
> Subject: Re: Publishing the Tao as a web page
> Message-ID: <6D41FAFE-6B15-4CD5-AB00-59DE8E93AC7B@vpnc.org>
> Content-Type: text/plain; charset=3Dus-ascii
>=20
> On Jun 13, 2012, at 1:06 PM, Russ Housley wrote:
>=20
>> Paul:
>>=20
>> It implies that the current RFC will become the initial web page content.=
  I think that is not the case.  Rather, the initial content will come from d=
raft-hoffman-tao4677bis.
>=20
> Good catch. I'll add explicit text in -02 that says that the initial text w=
ill come from the most recent proposed revision (and I will *not* put in a d=
raft name).
>=20
>> Do you want draft-hoffman-tao4677bis to be published as the final RFC ver=
sion in the Tao series?
>=20
> No. That seems silly, given that the web page will be done before the RFC.=

>=20
> On Jun 13, 2012, at 1:17 PM, John C Klensin wrote:
>=20
>> If the community cares about developing and maintaining a clear
>> history of changes, it might be slightly advantageous to:
>>=20
>>    (i) Make the current RFC the initial web page content
>>   =20
>>    (ii) Immediately replace it with a (possibly further
>>    revised) version of draft-hoffman-tao4677bis.
>>   =20
>>    (iii) Put the Tao aside until we are ready for another
>>    update.
>=20
> Yuck. The slight advantage there is hugely overwhelmed by the process hass=
les. Instead, the first web page should have a section talking about where i=
t came from.
>=20
>> I have trouble convincing myself that is worth even the marginal
>> extra effort it would take,
>=20
> Good. :-)
>=20
>> but I can see the advantages if
>> others disagree.  On the other hand, publishing
>> draft-hoffman-tao4677bis in the RFC series seems to me to have
>> no value at all.  There should be an RFC 4677bis but it should
>> probably say little more than "Tao is now a web page at .... and
>> it is not being maintained in the RFC Series".
>=20
> That's the purpose of this document.
>=20
> --Paul Hoffman
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 4
> Date: Wed, 13 Jun 2012 17:50:30 -0400
> From: John C Klensin <john-ietf@jck.com>
> To: Thomas Narten <narten@us.ibm.com>,    "Romascanu, Dan (Dan)"
>    <dromasca@avaya.com>
> Cc: SM <sm@resistor.net>, ietf@ietf.org
> Subject: Re: registries and designated experts
> Message-ID: <21E957EA9B7C80B51E88AE22@JcK-HP8200.jck.com>
> Content-Type: text/plain; charset=3Dus-ascii
>=20
>=20
>=20
> --On Wednesday, June 13, 2012 08:48 -0400 Thomas Narten
> <narten@us.ibm.com> wrote:
>=20
>>> Maybe an IESG statement on this respect can help here.
>>=20
>> Is the existing text in RFC 5226 not sufficient? It contains
>> extensive text about the purpose and role of designated
>> experts, and was revised substantially the last time around to
>> try and find a good middle ground between being overly
>> prescriptive and giving experts a "blank check" to do what
>> they want.
>>=20
>> Nothing in the discussion I've seen so far in this thread
>> seems at odds with or beyond what is already in RFC 5226 (but
>> I may be biased).
>=20
> Thomas,
>=20
> FWIW, I think 5226 is ok, but that the community, especially the
> community who write "Designated Experts" need to pay a little
> more attention to a few phrases there than has sometimes been
> the case.  For example, 5226 says:
>=20
>    "Ideally, the designated expert follows specific review
>    criteria as documented with the protocol that creates or
>    uses the namespace."
>=20
> and=20
>=20
>    "Experts are expected to apply applicable documented
>    review or vetting procedures, or in the absence of
>    documented criteria, follow generally accepted norms,
>    e.g., those in Section 3.3."
>=20
> My impression is that people have perhaps too often skipped
> specifying specific guidelines or criteria in their definitions,
> leaving the experts to fall back on good sense and the last half
> of Section 3.3.  That isn't necessarily bad but can easily lead
> to misunderstandings if there is actually controversy about a
> proposed registration.  So I'd recommend that  the community pay
> a bit more attention during Last Call to whether enough (or too
> much) guidance is specified than has often been the case in the
> past where we argue protocol details and do a lot of nit-picking
> but mostly ignore IANA Considerations sections.
>=20
> That doesn't require changes to 5226.  But, if 5226 is every
> revised, it might be well to check to see if the emphasis in
> what it says about this issue is in line with what we want.
>=20
>    john
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 5
> Date: Thu, 14 Jun 2012 04:12:32 +0200
> From: Bjoern Hoehrmann <derhoermi@gmx.net>
> To: Randy Bush <randy@psg.com>
> Cc: IETF discussion list <ietf@ietf.org>
> Subject: Re: registries and designated experts
> Message-ID:
>    <l8bit7h15gu6go57e5o82jgkf22mj5ki69@hive.bjoern.hoehrmann.de>
> Content-Type: text/plain; charset=3DISO-8859-1
>=20
> * Randy Bush wrote:
>>> It seems to me that if an expert reviewer thinks that something will do
>>> notable harm, they should decline to make a decision and defer it to the=

>>> IETF at large
>>=20
>> so they are not an expert, they are a rubber stamp?  bs.
>=20
> Expert reviewers should use their judgement, but that includes whether
> their judgement is the right way to resolve some controversy or doubt.
>=20
> I was thinking the above more in terms of something about an application
> that had not been considered or forseen when the registry was created,
> in which case an expert reviewer might want to say they think making
> a decision is outside the confines of their role and expectations and
> assumptions that have been made when the registry was set up and they
> were appointed as reviewer, and reviewers should be expected to do that
> as appropriate, in principle.
> --=20
> Bj?rn H?hrmann ? mailto:bjoern@hoehrmann.de ? http://bjoern.hoehrmann.de
> Am Badedeich 7 ? Telefon: +49(0)160/4415681 ? http://www.bjoernsworld.de
> 25899 Dageb?ll ? PGP Pub. KeyID: 0xA4357E78 ? http://www.websitedev.de/=20=

>=20
>=20
> ------------------------------
>=20
> Message: 6
> Date: Wed, 13 Jun 2012 21:13:54 -0600
> From: Peter Saint-Andre <stpeter@stpeter.im>
> To: ietf@ietf.org
> Cc: The IESG <iesg@ietf.org>
> Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting
>    Compliance    with Intellectual Property Rights (IPR) Disclosure Rules)=

>    to    Informational RFC
> Message-ID: <4FD956F2.6070609@stpeter.im>
> Content-Type: text/plain; charset=3DUTF-8
>=20
> On 4/30/12 10:27 AM, The IESG wrote:
>>=20
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Promoting Compliance with Intellectual Property Rights (IPR)
>>   Disclosure Rules'
>>  <draft-polk-ipr-disclosure-03.txt> as Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2012-05-28.=20
>=20
> Tim and I received actionable feedback on this list from Stephan Wenger
> and Subramanian Moonesamy during the Last Call [1] [2], and Stephan has
> publicly verified that his concerns were addressed [3] (SM contacted me
> offlist to the same effect). A full diff is at [4], but in brief the
> main changes were as follows:
>=20
> 1. Tightened some terminology (e.g., changed "limitations" to "licensing
> requirements" and, in several places, "IETF participants" to "IETF
> contributors" and "authors" to "authors and listed contributors") and
> explicitly defined the terms "formal disclosure" and "informal disclosure"=
.
>=20
> 2. Clarified that this document does *not* define best current practices
> but instead suggests some strategies that ADs, WG chairs, and WG
> secretaries might want to use.
>=20
> 3. Mentioned that, if informal disclosure is allowed in a meeting,
> chairs ought to capture such statements in the meeting minutes.
>=20
> 4. Removed a misleading statement that silence could be interpreted as
> as a weak "no".
>=20
> 5. Removed any suggestion that non-receipt of IPR disclosures could be
> interpreted by ADs or WG chairs as necessarily blocking any advancement
> of an I-D.
>=20
> 6. Tweaked the sample email messages to improve their readability and
> better align with the body of the document.
>=20
> Peter
>=20
> [1]
> https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D63103=
&tid=3D1339642625
>=20
> [2]
> https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D63414=
&tid=3D1339642383
>=20
> [3]
> https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D63596=
&tid=3D1339642383
>=20
> [4] http://tools.ietf.org/rfcdiff?url2=3Ddraft-polk-ipr-disclosure-04.txt
>=20
>=20
> ------------------------------
>=20
> Message: 7
> Date: Thu, 14 Jun 2012 02:26:10 -0400
> From: John Leslie <john@jlc.net>
> To: Claudio Jeker <cjeker@diehard.n-r-g.com>, idr@ietf.org,
>    ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-idr-rfc4893bis-06.txt> (BGP
>    Support    for    Four-octet AS Number Space) to Proposed Standard
> Message-ID: <20120614062610.GR21341@verdi>
> Content-Type: text/plain; charset=3Dus-ascii
>=20
> Enke Chen <enkechen@cisco.com> wrote:
>> On 6/12/12 7:25 AM, Stewart Bryant wrote:
>> From:     Claudio Jeker <cjeker@diehard.n-r-g.com>
>>> On Tue, Jun 12, 2012 at 11:30:11AM +0100, Stewart Bryant wrote:
>>>> On 01/06/2012 23:00, Claudio Jeker wrote:
>>>>> On Fri, Jun 01, 2012 at 11:54:44AM -0700, The IESG wrote:
>>>>>>=20
>>>>>> The IESG has received a request from the Inter-Domain Routing WG
>>>>>> (idr) to consider the following document:
>>>>>> - 'BGP Support for Four-octet AS Number Space'
>>>>>> <draft-ietf-idr-rfc4893bis-06.txt> as Proposed Standard
>>>>>>=20
>>>>>> Abstract
>>>>>>=20
>>>>>> The Autonomous System (AS) number is encoded as a two-octet=20
>>>>>> entity in the base BGP specification. This document describes
>>>>>> extensions to BGP to carry the Autonomous System numbers as
>>>>>> four-octet entities. This document obsoletes RFC 4893.
>>>>>=20
>>>>> Just for the sake of clarity, OpenBGPD will not do the following:
>>>>>=20
>>>>> In addition, the path segment types AS_CONFED_SEQUENCE and
>>>>> AS_CONFED_SET [RFC5065] MUST NOT be carried in the AS4_PATH=20
>>>>> attribute of an UPDATE message. A NEW BGP speaker that receives
>>>>> these path segment types in the AS4_PATH attribute of an UPDATE
>>>>> message from an OLD BGP speaker MUST discard these path segments,
>>>>> adjust the relevant attribute fields accordingly, and continue
>>>>> processing the UPDATE message. This case SHOULD be logged locally
>>>>> for analysis.
>>>>>=20
>>>>> There is no point to do this fiddeling instead we will treat this=20
>>>>> like any other parse error of AS4_PATH.
>>>>>=20
>>>>> Claudio
>=20
>   That would make the OpenBSD implementation non-compliant with 4893bis.
>=20
>>>> Since this is in last call, I have to ask whether you have objection
>>>> to the publication of the above text, or have any proposed text
>>>> changes?
>>>=20
>>> I see no reason to enforce AS_CONFED_SEQUENCE and AS_CONFED_SET strippin=
g
>>> on all AS4 implementations. It forces bgp implementations that don't hav=
e
>>> confederation support to strip out something that will cause an error in=

>>> the regular path and for those systems ignoring the AS4_PATH attribute
>>> is perfectly fine. I do not understand how a workaround needs to be a
>>> MUST for something that is a MUST NOT at the same time? Why MUST we
>>> workaround something that MUST NOT appear? Why do we need to add extra
>>> code that is hard to test and maybe cause for further errors because it
>>> modifies attributes in very uncommon way?
>=20
>   Enke explains why this is called for in 4893bis.
>=20
>   It may help to recall the IETF mantra: "We believe in rough consensus
> and running code."
>=20
>   At the time 4893 was designed, it was a strict requirement in IDR
> that nothing could get to Proposed Standard without demonstrating
> multiple implementations. In practice, this meant we only documented
> something after multiple vendors had it deployed.
>=20
>   Thus, 4893 went out with bugs (though I was in the rough, explaining
> in general terms some weaknesses).
>=20
>   One bug in particular turned out to be _very_ serious. Patching in
> the AS4_PATH produced some AS_CONFED stuff very much out of context.
> A fix was desperately needed, and several vendors quickly patched it.
> 4893bis, as I understood it, documented this fix. I'm still in the rough,
> but I saw no point in objecting to documenting actual practice.
>=20
>   If in fact, OpenBSD has no intention of patching for this bug, _they_
> need to be considered "in the rough" (as well as non-compliant).
>=20
>   If, OTOH, they wish to propose a different fix, it's possible the
> IESG might ask IDR to consider it. (I can certainly imagine better ways
> to resolve the problem.)
>=20
>   But any fix (IMHO) _must_ dispose of out-of-context AS_CONFED stuff
> that still may be in the wild.
>=20
>>> I propose to remove that paragraph entierly since it does only add
>>> complexity to the protocol for no reason and therefor is only a source
>>> of errors without any benefit.
>=20
>   (I cannot endorse that proposal. It's too likely there's legacy
> equipment that allows AS_CONFED stuff to be placed in AS4_PATH.)
>=20
>> Hi, Claudio:
>>=20
>> Not sure if you are aware of the large scale outage that occurred a few=20=

>> years ago from the leak of the confed related segments by one=20
>> implementation. At the time quite a few implementations were resetting=20=

>> the sessions when receiving such updates.
>>=20
>> While discarding the whole AS4_PATH would be simpler and less disruptive=20=

>> (than session resetting), it would still lose the vital as-path info=20
>> contained in the AS4_PATH which can otherwise be recovered by=20
>> "repairing" the attribute.  That is why the approach specified in the=20
>> rfc4893bis is adopted, and it has been implemented widely.
>>=20
>> -- Enke
>=20
> --
> John Leslie <john@jlc.net>
>=20
>=20
> ------------------------------
>=20
> Message: 8
> Date: Wed, 13 Jun 2012 09:55:55 -0700
> From: Paul Sangster <Paul_Sangster@symantec.com>
> To: Roni Even <ron.even.tlv@gmail.com>,
>    "draft-ietf-nea-pt-tls.all@tools.ietf.org"
>    <draft-ietf-nea-pt-tls.all@tools.ietf.org>
> Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "nea@ietf.org"
>    <nea@ietf.org>,    'IETF' <ietf@ietf.org>
> Subject: RE: GenART LC review of draft-ietf-nea-pt-tls-05
> Message-ID:
>    <6E79D623502C70419A9EAB18E4D274252B8B06102F@TUS1XCHEVSPIN35.SYMC.SYMANT=
EC.COM>
>   =20
> Content-Type: text/plain; charset=3D"us-ascii"
>=20
> Thanks for the detailed review, comments are in-lined...
>=20
> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> Sent: Monday, June 04, 2012 2:20 PM
> To: draft-ietf-nea-pt-tls.all@tools.ietf.org
> Cc: 'IETF'; gen-art@ietf.org
> Subject: GenART LC review of draft-ietf-nea-pt-tls-05
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-A=
RT, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.
>=20
> Please resolve these comments along with any other Last Call comments you m=
ay receive.
>=20
>=20
>=20
> Document: draft-ietf-nea-pt-tls-05
>=20
> Reviewer: Roni Even
>=20
> Review Date:2012-6-4
>=20
> IETF LC End Date: 2012-6-13
>=20
> IESG Telechat date:
>=20
>=20
>=20
> Summary: This draft is almost ready for publication as a standard track RFC=
.
>=20
>=20
>=20
> Major issues:
>=20
>=20
>=20
> Minor issues:
>=20
> 1.       In section 3.2 "Therefore, this specification requests the IANA r=
eserve a TCP port number for use with the PT-TLS protocol upon publication o=
f this specification as an Internet standard RFC." I think it will  be bette=
r to have here the assigned port number and instruct the RFC editor to put t=
he correct value.
>=20
>=20
>=20
> [PS:] Ok, we can reword this in hopes of getting a particular value (race c=
ondition with other upcoming RFCs).
>=20
>=20
>=20
> 2.       In section 3.4.2.2 last paragraph you summarize the text from sec=
tion 3.8 while in the paragraph above you provide the reference. Why do you n=
eed the last paragraph if 3.8 is referenced.
>=20
>=20
>=20
> [PS:] The goal of this section is to introduce and summarize the different=
 phases of PT-TLS.  We felt a brief discussion of the general message flow w=
as helpful to the reader to understand what occurs during this phase (simila=
r to what we did in the other sub-sections).  Your correct that this informa=
tion is covered later in more detail.
>=20
>=20
>=20
> 3.       In various places you refer to SMI 0 as IETF SMI number while acc=
ording to the table it is IANA SMI number.
>=20
>=20
>=20
> [PS:] I presume this is about the PEN 0 being for the IETF.  Correct, it's=
 the IETF's name space that administered by the IANA.  What text would you l=
ike to see to make this more clear?  Can we do it in one place, for example s=
tating that the IETF name space is administered by the IANA?
>=20
>=20
>=20
> 4.       I assume that all implementations MUST support message type vendo=
r ID 0. Is this mentioned?
>=20
>=20
>=20
> [PS:] The purpose of this section was just to summarize and enumerate the m=
essage types for vendor id 0.   I don't think it's a general rule that any m=
essage type defined in the IETF (IANA :)) name space must (or should be) sup=
ported by all implementations.  It will vary depending on the purpose of the=
 message so that normative language is included in the descriptions of the m=
essage.
>=20
>=20
>=20
> 5.       In section 3.5 and 6.1 you propose a policy of "Expert Review wit=
h Specification Required ". I think that according to RFC5226 expert review i=
s implied if you select a specification required policy.
>=20
>=20
>=20
> [PS:] I agree, it says "Specification Required also implies use of a Desig=
nated Expert".  The policy is just "Specification Required" so we could remo=
ve the "Expert Review with" and make it clear it's the Specification Require=
d IANA policy.
>=20
>=20
>=20
> 6.       In section 3.6 on 9+ "Recipients of messages   of type 9 or highe=
r that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message T=
ype of a received PT-TLS message MUST respond with a Type Not Supported PT-T=
LS error code in a PT-TLS Error message." I think this is true only for Mess=
age Type Vendor ID 0.
>=20
>=20
>=20
> [PS:] Thanks will reword this section to make it more clear.
>=20
>=20
>=20
> 7.       In 3.7.1 for Max vers and prefs ver you say that they MUST be set=
 to 1. I think it will be more correct here to say SHOULD since you explain a=
fterwards that they may have other values.
>=20
>=20
>=20
> [PS:] I think this is a MUST.  The next sentence just points out that this=
 normative text might change in a future revision (which is not currently pl=
anned).
>=20
>=20
>=20
> 8.       In section 3.7.2 "the recipient SHOULD send". Why not make it a M=
UST here.
>=20
>=20
>=20
> [PS:] I ok with making this change, let's see what others think ...
>=20
>=20
>=20
> 9.       In section 3.7.2 "The version selected MUST be within the Min Ver=
s to Max Vers inclusive range sent in the Version Request   Message" I was e=
xpecting to see pref ver here.
>=20
>=20
>=20
> [PS:] Perf is just an informational (hint) preference.
>=20
>=20
>=20
> 10.   In section 3.8.3 " The SASL client authentication starts when the NE=
A Server  enters the PT-TLS Negotiation phase and its policy indicates  that=
 an authentication of the NEA Client is necessary but was not performed duri=
ng the TLS handshake protocol " my read of  section 3.8 second paragraph is t=
hat it can be done even if was done in the TLS handshake so the last part of=
 the sentence is not correct, if there is a policy you do it anyhow. This co=
mment is also for the third paragraph.
>=20
>=20
>=20
> [PS:] Thanks, this was supposed to be an example.  Will fix these.
>=20
>=20
>=20
> 11.   In section 3.9 I noticed that you propose to send the entire origina=
l message. Isn't it enough to send only the message identifier. This is base=
d on the last sentence of this section.
>=20
>=20
>=20
> [PS:] Not "the entire original message" as its at most the first 1024 byte=
s of the offending message.  This allows the recipient to either caches rece=
ntly sent messages and/or message identifiers when determining what caused t=
he error.  We thought this flexibility was useful and had very little cost.
>=20
>=20
>=20
> 12.   Most of the text in section 6.1 repeats RFC5226 but in your words. A=
re you trying to change some of RFC5226 text if not why write it in differen=
t words?
>=20
>=20
>=20
> [PS:] We were hoping to emphasize the aspects of 5226 that are most import=
ant to this specification.  We weren't trying to change how the IANA policy w=
as interpreted.  Did you think we did so?  Is there a portion of this text t=
hat is most troubling or was this just a question?
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> Nits/editorial comments:
>=20
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.ietf.org/mail-archive/web/ietf/attachments/20120613/c733c=
f1b/attachment.htm>
>=20
> ------------------------------
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20
>=20
> End of Ietf Digest, Vol 49, Issue 40
> ************************************

From alexey.melnikov@isode.com  Thu Jun 14 14:01:13 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99B0921F85AD; Thu, 14 Jun 2012 14:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
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 cZfqMLYjE+Mu; Thu, 14 Jun 2012 14:01:12 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 725DB21F85A5; Thu, 14 Jun 2012 14:01:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1339707671; d=isode.com; s=selector; i=@isode.com; bh=Ih7jSg2aiSNcRKQWzAQPbbzQ5PN8yA8mUSNR074eHes=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=RlZqrq596aepScf9cAUNvnZ7xakXoSXYLzTry9gKS4eMrKI+sWSl0m1H3HMtqpI7MmcaDt X1Mo7sQe5175nkK+U0r2U4bIR3AgLemO4ww6gtXl2B5DxdN/XOMDH1k9l0dEiAR/vwEfQ0 +4gsUBoAbsyMCWlnIAs4um3A8dBZr6w=;
Received: from [188.29.2.53] (188.29.2.53.threembb.co.uk [188.29.2.53])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <T9pRFgBjLKYP@statler.isode.com>; Thu, 14 Jun 2012 22:01:11 +0100
References: <4FCD0614.5050902@isode.com> <6E79D623502C70419A9EAB18E4D274252B8B061618@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
In-Reply-To: <6E79D623502C70419A9EAB18E4D274252B8B061618@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
Message-Id: <BBFCA866-ECF1-4F2F-9CE4-4BD3EB081B42@isode.com>
X-Mailer: iPad Mail (9B206)
From: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: APPSDIR review of draft-ietf-nea-pt-tls-04
Date: Thu, 14 Jun 2012 22:01:05 +0100
To: Paul Sangster <Paul_Sangster@symantec.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Cc: "draft-ietf-nea-pt-tls.all@tools.ietf.org" <draft-ietf-nea-pt-tls.all@tools.ietf.org>, "nea@ietf.org" <nea@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 21:01:13 -0000

Hi Paul,

On 14 Jun 2012, at 05:02, Paul Sangster <Paul_Sangster@symantec.com> wrote:

>> -----Original Message-----
>> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]
>> Sent: Monday, June 04, 2012 12:02 PM
>> To: apps-discuss@ietf.org; draft-ietf-nea-pt-tls.all@tools.ietf.org
>> Cc: ietf@ietf.org
>> Subject: APPSDIR review of draft-ietf-nea-pt-tls-04
>>=20
>> I have been selected as the Applications Area Directorate reviewer for
>> this draft (for background on APPSDIR, please see
>> http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectora
>> te ).
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive. Please wait for direction from your document shepherd
>> or AD before posting a new version of the draft.  The review is not
>> copied to the IESG as the Last Call has not been announced yet.
>>=20
>> Document: draft-ietf-nea-pt-tls-04
>> Title: PT-TLS: A TCP-based Posture Transport (PT) Protocol
>> Reviewer: Alexey Melnikov
>> Review Date: June 4, 2012
>>=20
>> Summary: This document is almost ready for publication as a Proposed
>> Standard, although some [mostly] SASL related issues remain.
>>=20
>> This document specifies PT-TLS, a TCP-based Posture Transport (PT)
>> protocol.  The PT-TLS protocol carries the Network Endpoint
>> Assessment (NEA) message exchange under the protection of a Transport
>> Layer Security (TLS) secured tunnel.
>>=20
>> (Note, I've reviewed -04, but I think all of this still applies to -
>> 05.)
>>=20
>>=20
>> Major:
>>=20
>> In 3.4.2.1: RFC 6125 use details are missing. You need to describe
>> whether CN-IDs and SRV-IDs are allowed, whether wildcards are allowed,
>> etc. I can suggest some details.
>=20
> [PS:] Since you weren't happy with our first attempt to address this comme=
nt, we would like to take you up on your kind offer to provide suggestions. =
 Maybe we could do this off-line and included the text in -06?
>=20

Yes.

>> Minor:
>>=20
>> In Section 3.2: This document is not yet Internet Standard, it will be
>> Proposed Standard. Suggest saying "Publication on Standards Track"
>> instead instead of "Internet Standard". The same issue in the IANA
>> consideration section.
>=20
> [PS:] This sentence will be re-written to address the gen-art comment so t=
he new text won't have this issue.
>=20
>>=20
>> In 3.8.1: I think one instance of "SASL authentication messages" -->
>> "SASL authentication mechanisms". Otherwise this sentence is out of
>> place, as you are not talking about SASL messages.
>=20
> [PS:] Will make it more clear the relationship between SASL messages in PT=
-TLS and the SASL mechanism exchanges inside the messages.  The sentence men=
tioned is about the PT-TLS client authentication messages.
>=20
>>=20
>> In 3.8.4: in SASL the server doesn't return abort as an error code, it
>> just fails the authentication exchange. I suggest removing it as a
>> choice.
>=20
> [PS:] This text was attempting to support the abort as described in RFC442=
2 which says:
>=20
> 3.5.  Aborting Authentication Exchanges
>=20
>   A client or server may desire to abort an authentication exchange if
>   it is unwilling or unable to continue (or enter into).
>=20
>   A client may abort the authentication exchange by sending a message,
>   the particulars of which are protocol specific, to the server,
>   indicating that the exchange is aborted.  The server may be required
>   by the protocol to return a message in response to the client's abort
>   message.
>=20
>   Likewise, a server may abort the authentication exchange by sending a
>   message, the particulars of which are protocol specific, to the
>   client, indicating that the exchange is aborted.
>=20
> [PS]: Is this an unacceptable way to do this? =20
>=20

Well, Ok, but nobody is sending a special message when a SASL server wants t=
o abort the exchange. Existing open source API don't seem to support this ei=
ther.
I suppose the client can just treat this as an authentication failure, as it=
 can't know what caused the abort.

>>=20
>> In 3.8.7: you define the Reserved field which I assume is used for
>> padding? If yes, then you will not get proper alignment for the next
>> field, as SASL mechanism names are variable length. (If you intended
>> that they are always sent as 20 bytes, then this is missing from the
>> document.)
>=20
> [PS:] Sure, word alignment would have been a good reason for doing this bu=
t we thought more about byte alignment.  We also thought having these bits a=
vailable could be useful later (e.g. for indicating preference or some other=
 semantic that could impact the mechanism selection).   Since we didn't need=
 an entire byte for the Mech Len we thought it made sense to at least byte a=
lign the Mechanism Name and the cost of 3 bits for some future purpose made s=
ense.

Ok. Never mind.

Just to confirm: SASL mechanism names are not padded with spaces or NULs?

>=20
>>=20
>> In 3.8.10:
>>=20
>> The Abort choice is really not needed (as per above).
>>=20
>> Also, can you give me an example of when the Mechanism Failure will be
>> returned instead of just Failure?
>=20
> [PS:] The document gives the example of authentication failure (incorrect c=
redential) where mechanism failure is when the mechanism logic detects a fai=
lure in processing the authentication request that isn't related to the user=
's input (e.g. malloc error).
>=20

Ok. Having malloc failure as an example would help.

>> In 3.9: Failed Authentication error code - how does this differ from
>> SASL Authentication result with Failure code?
>=20
> [PS:] Hmm, I'm going to have to look into this more.  One way they are dif=
ferent is the fact that the NEA Client is not allowed to send the SASL Resul=
t TLV so can't use the Failure code but it could send a Failed Authenticatio=
n error code in the PT-TLS Error Message.

Wouldn't the client just send Abort in this case? (Abort makes sense for cli=
ents)
>=20
>>=20
>> In 4.1.2, second block, the first bullet: I think you meant "client"
>> instead of the "server".
>=20
> [PS:] Thanks, good catch
>=20
>>=20
>>=20
>> Question (might not be an issue):
>>=20
>> In 6.2: is it possible to register a vendor specific value without a
>> specification?
>=20
> [PS:] In order to be placed in the IANA registry a permanent specification=
 is required (as mentioned in section 6.1).   Of course vendors are free to u=
se values in their name space without registering them with the IANA.

This might be a bit heavyweight and might discourage registrations. But if t=
hat is what you want...
>=20
>>=20
>> The same question for 6.3.
>>=20
>>=20
>> Nits: None
>=20

From alexey.melnikov@isode.com  Thu Jun 14 14:25:15 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F52521F84A5; Thu, 14 Jun 2012 14:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 35yTTfI-HbCM; Thu, 14 Jun 2012 14:25:14 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 77BFC21F8498; Thu, 14 Jun 2012 14:25:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1339709113; d=isode.com; s=selector; i=@isode.com; bh=81mR9i2F7RG42oI6bOpLQGMiTVTv8elqSyGxOuZDM+Y=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=cMMq/gHwhstEPBOJXtyxyq1jneZmbO6joY/ITXEWx5I6GA73qNHl0qCoUQQGPV+SNKJsCf CYPhwSmmKoUcp8GZQfxojj3SuMTUY8TW+sacyemqe0iLcOnzgGE3gD8TIejaT/pwHsIuaZ JuCrHmjjQw20+dPM+/pr9cTemfGSeMo=;
Received: from [172.20.10.2] ((unknown) [212.183.128.139])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <T9pWtwBjLJuC@statler.isode.com>; Thu, 14 Jun 2012 22:25:13 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4FDA4CFA.7000507@isode.com>
Date: Thu, 14 Jun 2012 21:43:38 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Paul Sangster <Paul_Sangster@symantec.com>
Subject: Re: [apps-discuss] APPSDIR review of draft-ietf-nea-pt-tls-04
References: <4FCD0614.5050902@isode.com> <4FD86FB2.2050002@isode.com> <6E79D623502C70419A9EAB18E4D274252B8B06161A@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
In-Reply-To: <6E79D623502C70419A9EAB18E4D274252B8B06161A@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-nea-pt-tls.all@tools.ietf.org" <draft-ietf-nea-pt-tls.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 21:25:15 -0000

Hi Paul,

On 14/06/2012 05:11, Paul Sangster wrote:
>> -----Original Message-----
>> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]
>> Sent: Wednesday, June 13, 2012 3:47 AM
>> To: apps-discuss@ietf.org; draft-ietf-nea-pt-tls.all@tools.ietf.org
>> Cc: ietf@ietf.org
>> Subject: Re: [apps-discuss] APPSDIR review of draft-ietf-nea-pt-tls-04
>>
>> On 04/06/2012 20:01, Alexey Melnikov wrote:
>>> I have been selected as the Applications Area Directorate reviewer
>> for
>>> this draft (for background on APPSDIR, please see
>>>
>> http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectora
>> te
>>> ).
>>>
>>> Please resolve these comments along with any other Last Call comments
>>> you may receive. Please wait for direction from your document
>> shepherd
>>> or AD before posting a new version of the draft.  The review is not
>>> copied to the IESG as the Last Call has not been announced yet.
>>>
>>> Document: draft-ietf-nea-pt-tls-04
>>> Title: PT-TLS: A TCP-based Posture Transport (PT) Protocol
>>> Reviewer: Alexey Melnikov
>>> Review Date: June 4, 2012
>>>
>>> Summary: This document is almost ready for publication as a Proposed
>>> Standard, although some [mostly] SASL related issues remain.
>>>
>>> This document specifies PT-TLS, a TCP-based Posture Transport (PT)
>>> protocol.  The PT-TLS protocol carries the Network Endpoint
>>> Assessment (NEA) message exchange under the protection of a Transport
>>> Layer Security (TLS) secured tunnel.
>>>
>>> (Note, I've reviewed -04, but I think all of this still applies to -
>> 05.)
>> Additional issues in -05:
>>
>> 1) I didn't find the updated text prohibiting TLS renegotiation to be
>> any clearer in -05? Can you maybe try to explain what is allowed and
>> what is not?
> [PS:] The editors will discuss this more and provide a response.

Thanks.

>> 2) In the IANA Considerations:
>>
>> The PEN 0 (IETF) PT-TLS Message Type values between 9 and 2^32-2
>> inclusive are allocated for future assignment by the IANA.  The value
>> 2^32-1 is permanently reserved and is not to be allocated.
>>
>> Whom does the last sentence apply to? This registry? Or the IANA PEN
>> registry being documented by draft-liang-iana-pen?
> [PS:] I'm assuming your asking about the text at the bottom of section 6.2. Registry for PT-TLS Message Types immediately below the table that defines registry values 0 thru 8 for PEN=0.  It refers to this specific registry not the PEN registry.
Please make this clear in your document. If you want to reserve the 
value 2^32-1 in the PEN registry, then you need to make this clear in 
your document as well.


From chair@ietf.org  Thu Jun 14 14:26:59 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9739121F846C for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 14:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.699
X-Spam-Level: 
X-Spam-Status: No, score=-101.699 tagged_above=-999 required=5 tests=[AWL=0.900, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 RZcbqm7WwDhW for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 14:26:59 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id F2FC921F8469 for <ietf@ietf.org>; Thu, 14 Jun 2012 14:26:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 4958112BBBD for <ietf@ietf.org>; Thu, 14 Jun 2012 14:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fisR2CvjzBDN for <ietf@ietf.org>; Thu, 14 Jun 2012 14:26:59 -0700 (PDT)
Received: from [192.168.2.110] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) by c8a.amsl.com (Postfix) with ESMTPSA id D864912BBAC for <ietf@ietf.org>; Thu, 14 Jun 2012 14:26:58 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Future Handling of Blue Sheets
From: IETF Chair <chair@ietf.org>
In-Reply-To: <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org>
Date: Thu, 14 Jun 2012 17:26:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 21:26:59 -0000

Two things have occurred since the message below as sent to the IETF =
mail list.  First, we got a lawyer in Europe to do some investigation, =
and the inclusion of the email address on the blue sheet will lead to =
trouble with the European privacy laws.  Second, Ted Hardie suggested =
that we could require a password to access the scanned blue sheet.

Based on the European privacy law information, the use of email will =
result in a major burden.  If the email address is used, then we must =
provide a way for people to ask for their email address to be remove at =
any time in the future, even if we got prior approval to include it.  =
Therefore, I suggest that we collect organization affiliation to =
discriminate between multiple people with the same name instead of email =
address.

Based on Ted's suggestion, I checked with the Secretariat about using a =
datatracker login to download the scanned blue sheet.  This is fairly =
easy to do, once the community tracking tools are deployed.  However, =
with the removal of the email addresses from the blue sheets, it is =
unclear that there is any further need for password protection of these =
images.  Therefore, I suggest that we proceed without password =
protection for the blue sheet images.

Here is a summary of the suggested way forward:

- Stop collecting email addresses on blue sheets;

- Collect organization affiliation to discriminate between multiple =
people with the same name;

- Scan the blue sheets and include the images in the proceedings for the =
WG session;

- Add indication to top of the blue sheet so people know it will be part =
of the proceedings; and

- Discard paper blue sheets after scanning.

Russ


On May 6, 2012, at 12:46 PM, IETF Chair wrote:

> We have heard from many community participants, and consensus is quite =
rough on this topic.  The IESG discussed this thread and reached two =
conclusions:
>=20
> (1) Rough consensus: an open and transparent standards process is more =
important to the IETF than privacy of blue sheet information.
>=20
> (2) Rough consensus: inclusion of email addresses is a good way to =
distinguish participants with the same or similar names.
>=20
>=20
> Based on these conclusions, the plan is to handle blue sheets as =
follows:
>=20
> - Continue to collect email addresses on blue sheets;
>=20
> - Scan the blue sheet and include the image in the proceedings for the =
WG session;
>=20
> - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and
>=20
> - Discard paper blue sheets after scanning.
>=20
>=20
> On behalf of the IESG,
> Russ
>=20


From stpeter@stpeter.im  Thu Jun 14 14:44:04 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E85611E8097 for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 14:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
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 2NIZ24ly6A+A for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 14:44:03 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 5A24811E8079 for <ietf@ietf.org>; Thu, 14 Jun 2012 14:44:03 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 5B1694005A for <ietf@ietf.org>; Thu, 14 Jun 2012 16:01:19 -0600 (MDT)
Message-ID: <4FDA5B22.4040507@stpeter.im>
Date: Thu, 14 Jun 2012 15:44:02 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: New Non-WG Mailing List: IETF-822
References: <20120614213751.1985.262.idtracker@ietfa.amsl.com>
In-Reply-To: <20120614213751.1985.262.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 21:44:04 -0000

On 6/14/12 3:37 PM, IETF Secretariat wrote:

> List address: ietf-822@ietf.org

Is no one thinking ahead to the 822nd meeting of the IETF in the year
2258?!?

/psa




From warren@kumari.net  Thu Jun 14 14:55:17 2012
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B650121F85D0 for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 14:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 6rSxHBRMGhMv for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 14:55:16 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 02CA921F85C7 for <ietf@ietf.org>; Thu, 14 Jun 2012 14:55:15 -0700 (PDT)
Received: from dhcp-172-19-118-235.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id E8A581B411DF; Thu, 14 Jun 2012 17:55:14 -0400 (EDT)
Subject: Re: [IETF] Re: New Non-WG Mailing List: IETF-822
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4FDA5B22.4040507@stpeter.im>
Date: Thu, 14 Jun 2012 17:55:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4FAEA770-E0CF-450E-8056-40C72A4843F5@kumari.net>
References: <20120614213751.1985.262.idtracker@ietfa.amsl.com> <4FDA5B22.4040507@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1278)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 21:55:17 -0000

On Jun 14, 2012, at 5:44 PM, Peter Saint-Andre wrote:

> On 6/14/12 3:37 PM, IETF Secretariat wrote:
>=20
>> List address: ietf-822@ietf.org
>=20
> Is no one thinking ahead to the 822nd meeting of the IETF in the year
> 2258?!?

Who cares about that? I think that it is *vital* that we discuss RFC 85 =
and fully explore all of the implications therein.

For example, *where* at the Illini Union will it be? What do we do if =
Phyllis doesn't reply in time? Who will bring the bluesheets?  How do I =
get from the airport to the Illini Union? And who fixes the clock in my =
room if the chambermaid doesn't?

I therefore propose that we create a ietf-822@ietf.org list to fully =
(and finally) get to the bottom of these important questions, once and =
for all=85.

W

>=20
> /psa
>=20
>=20
>=20

---
Schizophrenia beats being alone.



From warren@kumari.net  Thu Jun 14 14:57:35 2012
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5997E11E807F for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 14:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 EB8yYz6tBgec for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 14:57:34 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id C756B11E8079 for <ietf@ietf.org>; Thu, 14 Jun 2012 14:57:34 -0700 (PDT)
Received: from dhcp-172-19-118-235.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 463BD1B4062E; Thu, 14 Jun 2012 17:57:34 -0400 (EDT)
Subject: Re: [IETF] Re: [IETF] Re: New Non-WG Mailing List: IETF-822
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4FAEA770-E0CF-450E-8056-40C72A4843F5@kumari.net>
Date: Thu, 14 Jun 2012 17:57:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9CD362B5-EE3D-4FAC-9B2F-F97B1AF09504@kumari.net>
References: <20120614213751.1985.262.idtracker@ietfa.amsl.com> <4FDA5B22.4040507@stpeter.im> <4FAEA770-E0CF-450E-8056-40C72A4843F5@kumari.net>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1278)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 21:57:35 -0000

On Jun 14, 2012, at 5:55 PM, Warren Kumari wrote:

>=20
> On Jun 14, 2012, at 5:44 PM, Peter Saint-Andre wrote:
>=20
>> On 6/14/12 3:37 PM, IETF Secretariat wrote:
>>=20
>>> List address: ietf-822@ietf.org
>>=20
>> Is no one thinking ahead to the 822nd meeting of the IETF in the year
>> 2258?!?
>=20
> Who cares about that? I think that it is *vital* that we discuss RFC =
85 and fully explore all of the implications therein.
>=20
> For example, *where* at the Illini Union will it be? What do we do if =
Phyllis doesn't reply in time? Who will bring the bluesheets?  How do I =
get from the airport to the Illini Union? And who fixes the clock in my =
room if the chambermaid doesn't?
>=20
> I therefore propose that we create a ietf-822@ietf.org list to fully =
(and finally) get to the bottom of these important questions, once and =
for all=85.

=85. and wouldn't this have been awesome if I actually had =
ietf-85@ietf.org in my paste buffer (like I thought  I did) and not =
ietf-822@ietf.org. That way I would have sounded super-awesomely funny =
and not like I had miscalculated my meds=85.

W
>=20
> W
>=20
>>=20
>> /psa
>>=20
>>=20
>>=20
>=20
> ---
> Schizophrenia beats being alone.
>=20
>=20

--
It is impossible to sharpen a pencil with a blunt axe.  It is equally =
vain
to try to do it with ten blunt axes instead=20
    --  E.W Dijkstra, 1930-2002



From ben@nostrum.com  Thu Jun 14 14:58:48 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9200F11E8080; Thu, 14 Jun 2012 14:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 QsveMV+FzJQ1; Thu, 14 Jun 2012 14:58:47 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id B930F21F84AC; Thu, 14 Jun 2012 14:58:47 -0700 (PDT)
Received: from frankenstein.test.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q5ELwk8X082296 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 14 Jun 2012 16:58:47 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-ietf-6man-rfc3484bis-05 
Date: Thu, 14 Jun 2012 16:58:46 -0500
Message-Id: <C8476C40-FE78-4712-B76A-88C324715579@nostrum.com>
To: draft-ietf-6man-rfc3484bis.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 21:58:48 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-6man-rfc3484bis-05
Reviewer: Ben Campbell=09
Review Date: 2012-06-14
IETF LC End Date: 2012-06-15

Summary: This draft is almost ready for publication as a proposed =
standard. I have one security consideration question that should be =
addressed first. I also have some editorial comments that might be worth =
addressing if there is a revision prior to publication.

Note: As always, reviewing a "bis" draft is difficult for someone who =
has not been involved in its creation, as one may comment on issues =
inherited from the original RFC that were not in scope to be fixed in a =
particular "bis" draft. Apologies in advance if I run afoul of such =
things.

Major issues:

None


Minor issues:

-- security considerations, 1st paragraph: "This document has no direct =
impact on Internet infrastructure security."

Can source and/or destination address selection could influence whether =
data is sent over and encrypted path? In particularly true since section =
7 allows the address selection to influence interface selection? If so, =
it's worth mentioning the fact, and considering whether an encrypted =
path vs unencrypted path should be considered in the selection rules. =
Perhaps such decisions should be made prior to following the rules in =
this draft--but if so it would be helpful to explicitly say that.

Nits/editorial comments:

-- section 3/5, last paragraph: "Whether or not an address is designated =
a home address or care-of address is outside the scope of this =
document."

This sentence is confusing since the previous sentence indicated that =
"... it is sufficient to know whether or not one=92s own addresses are =
designated as home addresses or care-of addresses." Is the point that =
the _mechanism_ for making that designation is out of scope, even though =
one needs to know the _results_? Or is this a question about talking =
about one's own addresses vs the destination addresses?

-- section 4, third paragraph: (starting with "Discussion: ..."

I tend to expect indented paragraphs like this to be parenthetical =
notes. The "discussion" label reinforces this. It seems like normative =
statements don't belong in such paragraphs. Can this be promoted to a =
normal paragraph? (Note that this occurs in several other "discussion" =
paragraphs as well.)

-- section 4. last paragraph:

Please expand SIIT on first mention.

-- section 5, general:

It would be helpful to define SA, SB prior to use. ( I note that the =
destination section does this for DA and DB.)

-- section 5, last paragraph:

Since this talks about Rule 2, perhaps it should be moved to immediately =
after rule 2?

-- section 6, discussion paragraph after Rule 7:

Please expand 6RD and ISATAP on first mention.

-- section 10.6, first paragraph:

Please expand ULAs on first mention.



--=20





From narten@us.ibm.com  Thu Jun 14 21:53:11 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 273DC21F8535 for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 21:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 i8H3adJSWN2P for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 21:53:10 -0700 (PDT)
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.143]) by ietfa.amsl.com (Postfix) with ESMTP id 0937421F8533 for <ietf@ietf.org>; Thu, 14 Jun 2012 21:53:09 -0700 (PDT)
Received: from /spool/local by e3.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 15 Jun 2012 00:53:08 -0400
Received: from d01dlp02.pok.ibm.com (9.56.224.85) by e3.ny.us.ibm.com (192.168.1.103) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 15 Jun 2012 00:53:06 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 826C66E8049 for <ietf@ietf.org>; Fri, 15 Jun 2012 00:53:05 -0400 (EDT)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q5F4r5rO221484 for <ietf@ietf.org>; Fri, 15 Jun 2012 00:53:05 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q5F4r50I014254 for <ietf@ietf.org>; Fri, 15 Jun 2012 01:53:05 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q5F4r47I014234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 15 Jun 2012 01:53:04 -0300
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q5F4r39o012681 for <ietf@ietf.org>; Fri, 15 Jun 2012 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q5F4r3Ih012667 for ietf@ietf.org; Fri, 15 Jun 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201206150453.q5F4r3Ih012667@rotala.raleigh.ibm.com>
Date: Fri, 15 Jun 2012 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12061504-8974-0000-0000-00000A181A45
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 04:53:11 -0000

Total of 119 messages in the last 7 days.
 
script run at: Fri Jun 15 00:53:03 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 12.61% |   15 | 18.08% |   190700 | stephen.farrell@cs.tcd.ie
  5.88% |    7 |  9.35% |    98669 | duerst@it.aoyama.ac.jp
  5.04% |    6 |  3.88% |    40902 | brian.e.carpenter@gmail.com
  2.52% |    3 |  5.34% |    56277 | paul_sangster@symantec.com
  4.20% |    5 |  3.31% |    34932 | john-ietf@jck.com
  4.20% |    5 |  2.94% |    30959 | stpeter@stpeter.im
  4.20% |    5 |  2.61% |    27534 | paul.hoffman@vpnc.org
  3.36% |    4 |  3.20% |    33801 | alexey.melnikov@isode.com
  3.36% |    4 |  2.85% |    30072 | sm@resistor.net
  3.36% |    4 |  2.40% |    25278 | housley@vigilsec.com
  3.36% |    4 |  1.90% |    20072 | randy@psg.com
  2.52% |    3 |  2.49% |    26228 | daedulus@btconnect.com
  2.52% |    3 |  2.31% |    24379 | dworley@avaya.com
  2.52% |    3 |  2.30% |    24235 | abdussalambaryun@gmail.com
  2.52% |    3 |  2.03% |    21453 | glenzorn@gmail.com
  2.52% |    3 |  1.73% |    18277 | derhoermi@gmx.net
  2.52% |    3 |  1.72% |    18167 | mrex@sap.com
  0.84% |    1 |  2.96% |    31181 | anandmadhab@gmail.com
  1.68% |    2 |  2.00% |    21114 | rees@mumble.net
  0.84% |    1 |  2.37% |    25010 | dan.pitt@opennetworking.org
  1.68% |    2 |  1.46% |    15418 | narten@us.ibm.com
  1.68% |    2 |  1.39% |    14631 | sob@harvard.edu
  1.68% |    2 |  1.27% |    13432 | chair@ietf.org
  1.68% |    2 |  1.23% |    12973 | ole@cisco.com
  1.68% |    2 |  1.15% |    12089 | ynir@checkpoint.com
  1.68% |    2 |  1.10% |    11599 | warren@kumari.net
  0.84% |    1 |  1.07% |    11279 | hartmans@mit.edu
  0.84% |    1 |  1.07% |    11265 | stewe@stewe.org
  0.84% |    1 |  0.89% |     9396 | enkechen@cisco.com
  0.84% |    1 |  0.86% |     9101 | john@jlc.net
  0.84% |    1 |  0.85% |     8940 | stbryant@cisco.com
  0.84% |    1 |  0.80% |     8486 | tony@att.com
  0.84% |    1 |  0.80% |     8484 | barryleiba@computer.org
  0.84% |    1 |  0.80% |     8412 | lear@cisco.com
  0.84% |    1 |  0.76% |     7992 | dromasca@avaya.com
  0.84% |    1 |  0.74% |     7780 | ben@nostrum.com
  0.84% |    1 |  0.73% |     7708 | tglassey@earthlink.net
  0.84% |    1 |  0.72% |     7545 | adrian@olddog.co.uk
  0.84% |    1 |  0.68% |     7143 | mohamed.boucadair@orange.com
  0.84% |    1 |  0.68% |     7131 | jun@wide.ad.jp
  0.84% |    1 |  0.63% |     6654 | hartmans-ietf@mit.edu
  0.84% |    1 |  0.62% |     6569 | iad@ietf.org
  0.84% |    1 |  0.61% |     6415 | martin.thomson@gmail.com
  0.84% |    1 |  0.60% |     6369 | dhc@dcrocker.net
  0.84% |    1 |  0.57% |     6020 | johnl@iecc.com
  0.84% |    1 |  0.57% |     5968 | john@jck.com
  0.84% |    1 |  0.54% |     5669 | ned+ietf@mauve.mrochek.com
  0.84% |    1 |  0.53% |     5571 | suresh.krishnan@ericsson.com
  0.84% |    1 |  0.52% |     5489 | julian.reschke@gmx.de
--------+------+--------+----------+------------------------
100.00% |  119 |100.00% |  1054768 | Total


From ynir@checkpoint.com  Thu Jun 14 23:47:09 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7867321F867A for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 23:47:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.032
X-Spam-Level: 
X-Spam-Status: No, score=-10.032 tagged_above=-999 required=5 tests=[AWL=0.567, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 2yGn-RefZF38 for <ietf@ietfa.amsl.com>; Thu, 14 Jun 2012 23:47:09 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC5321F86E0 for <ietf@ietf.org>; Thu, 14 Jun 2012 23:47:08 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q5F6l1qq010015; Fri, 15 Jun 2012 09:47:05 +0300
X-CheckPoint: {4FDADA4D-0-1B221DC2-4FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 15 Jun 2012 09:47:01 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Fri, 15 Jun 2012 09:46:59 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Date: Fri, 15 Jun 2012 09:46:59 +0300
Subject: Re: New Non-WG Mailing List: IETF-822
Thread-Topic: New Non-WG Mailing List: IETF-822
Thread-Index: Ac1KwqmLKJHnH8VeS6ylUVF/A91JUg==
Message-ID: <DE6911BA-1AF0-45FC-8A0A-34BBB4C3BEA5@checkpoint.com>
References: <20120614213751.1985.262.idtracker@ietfa.amsl.com> <4FDA5B22.4040507@stpeter.im>
In-Reply-To: <4FDA5B22.4040507@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 06:47:09 -0000

On Jun 15, 2012, at 12:44 AM, Peter Saint-Andre wrote:

> On 6/14/12 3:37 PM, IETF Secretariat wrote:
>=20
>> List address: ietf-822@ietf.org
>=20
> Is no one thinking ahead to the 822nd meeting of the IETF in the year
> 2258?!?

Well, I've started working on draft-nir-ipv6-were-finally-deploying-it but =
I'm not sure what format would be an appropriate submission format in the 2=
3rd century.

Doesn't it coincide with the 1st season of Babylon 5?

Yoav=

From harald@alvestrand.no  Fri Jun 15 02:24:56 2012
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69C9521F85BD for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 02:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.449
X-Spam-Level: 
X-Spam-Status: No, score=-110.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 LYLKlSP0CoRg for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 02:24:55 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 4B64121F85A5 for <ietf@ietf.org>; Fri, 15 Jun 2012 02:24:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id AD44439E179 for <ietf@ietf.org>; Fri, 15 Jun 2012 11:25:20 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3NHqrBuGDCbs for <ietf@ietf.org>; Fri, 15 Jun 2012 11:25:18 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:be30:5bff:fede:bcdc]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 89CCD39E020 for <ietf@ietf.org>; Fri, 15 Jun 2012 11:25:18 +0200 (CEST)
Message-ID: <4FDAFF60.3070509@alvestrand.no>
Date: Fri, 15 Jun 2012 11:24:48 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: New Non-WG Mailing List: IETF-822
References: <20120614213751.1985.262.idtracker@ietfa.amsl.com> <4FDA5B22.4040507@stpeter.im> <DE6911BA-1AF0-45FC-8A0A-34BBB4C3BEA5@checkpoint.com>
In-Reply-To: <DE6911BA-1AF0-45FC-8A0A-34BBB4C3BEA5@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 09:24:56 -0000

On 06/15/2012 08:46 AM, Yoav Nir wrote:
> On Jun 15, 2012, at 12:44 AM, Peter Saint-Andre wrote:
>
>> On 6/14/12 3:37 PM, IETF Secretariat wrote:
>>
>>> List address: ietf-822@ietf.org
>> Is no one thinking ahead to the 822nd meeting of the IETF in the year
>> 2258?!?
> Well, I've started working on draft-nir-ipv6-were-finally-deploying-it but I'm not sure what format would be an appropriate submission format in the 23rd century.
ASCII, of course. But the boilerplate will have changed.
>
> Doesn't it coincide with the 1st season of Babylon 5?
>
> Yoav


From mohta@necom830.hpcl.titech.ac.jp  Fri Jun 15 03:49:32 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B56321F854D for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 03:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.399
X-Spam-Level: *
X-Spam-Status: No, score=1.399 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 KfWrtDSj4IuD for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 03:49:31 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id F224221F853D for <ietf@ietf.org>; Fri, 15 Jun 2012 03:49:30 -0700 (PDT)
Received: (qmail 80776 invoked from network); 15 Jun 2012 10:53:50 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 15 Jun 2012 10:53:50 -0000
Message-ID: <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp>
Date: Fri, 15 Jun 2012 19:48:18 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu>
In-Reply-To: <4FCEAB53.2020504@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 10:49:32 -0000

After thinking more about the draft, I think it is
purposelessly hostile against innocent operators and
end users who are suffering between people filtering
ICMP and people insisting on PMTUD.

Today, innocent operators often clear DF bit and
end users are happy with it, because, today, probability
of accidental ID match is small enough.

However, as the ID specifies:

   >> Originating sources MAY set the IPv4 ID field of atomic datagrams
   to any value.

   >> IPv4 datagram transit devices MUST NOT clear the DF bit.

people insisting on PMTUD are now authorized to set ID always
zero, trying to discourage ICMP filtering and DF bit clearing.

But, as people filtering ICMP won't stop doing so and if
operators can do nothing other than clearing DF, it is
end users who suffers.

Then, end users may actively act against PMTUD and/or IETF.

					Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Fri Jun 15 05:03:27 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F07E21F85DD for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 05:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.655
X-Spam-Level: 
X-Spam-Status: No, score=0.655 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 Gci-GEh9vbMX for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 05:03:26 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id C9F3421F85D8 for <ietf@ietf.org>; Fri, 15 Jun 2012 05:03:21 -0700 (PDT)
Received: (qmail 81772 invoked from network); 15 Jun 2012 12:07:34 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 15 Jun 2012 12:07:34 -0000
Message-ID: <4FDB2436.2060805@necom830.hpcl.titech.ac.jp>
Date: Fri, 15 Jun 2012 21:01:58 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <Pine.LNX.4.64.1206022127550.17026@shell4.bayarea.net> <4FCBB71E.9080209@necom830.hpcl.titech.ac.jp> <4FCEAA6B.20204@isi.edu>
In-Reply-To: <4FCEAA6B.20204@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 12:03:27 -0000

Joe Touch wrote:

> Hi,

Hi,

>> But, then,
>>
>>      >>   Sources emitting non-atomic datagrams MUST NOT repeat IPv4 ID
>>      values within one MSL for a given source address/destination
>>      address/protocol triple.
>>
>> makes most, if not all, IPv4 hosts non compliant if MSL=2min.
> 
> This is already noted throughout this document, however there is little
> impact to such non-compliance if datagrams don't persist that long.

So, the question to be asked is how long datagrams persist.

As you now say MSL may be smaller than 2min, the draft is
useless to promote implementers implement rate limiting.

If you can't define hard value of MSL, implementors can
assume anything.

>> Worse, without hard value of MSL, it is a meaningless
>> requirement. Note that MSL=2min derived from RFC793 breaks
>> 150Mbps TCP.
> 
> It breaks at 6.4 Mbps for 1500 byte packets, as is already noted in the doc.

With practically very low probability.

>> The proper solution, IMHO, to the ID uniqueness is to request
>> a destination host drop fragments from a source host after
>> it receives tens (or hundreds) of packets with different IDs
>> from the same source host.
> 
> That doesn't help ID uniqueness; it helps avoid fragmentation
> overload.

It does help ID uniqueness, because fragments with accidental
matches are quickly discarded.

> FWIW, such issues were discussed at length in the INTAREA WG when this
> doc was developed.

I appreciate that the draft is terse not including so lengthy
discussions in the WG.

However, at the same time, don't expect me to read all the log
of the discussions in the WG, especially because you and
the discussions misunderstand the problem as:

> That doesn't help ID uniqueness; it helps avoid fragmentation
> overload.

That does help ID uniqueness.

						Masataka Ohta

From smb@cs.columbia.edu  Fri Jun 15 08:13:24 2012
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E5D21F8887 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 08:13:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 WmEAXH+0BE5z for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 08:13:23 -0700 (PDT)
Received: from salak.cc.columbia.edu (salak.cc.columbia.edu [128.59.29.6]) by ietfa.amsl.com (Postfix) with ESMTP id 0707821F8885 for <ietf@ietf.org>; Fri, 15 Jun 2012 08:13:22 -0700 (PDT)
Received: from [192.168.2.11] (74-92-112-54-Philadelphia.hfc.comcastbusiness.net [74.92.112.54]) (user=smb2132 mech=PLAIN bits=0) by salak.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q5FFDKnH002071 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 15 Jun 2012 11:13:20 -0400 (EDT)
Subject: Re: New Non-WG Mailing List: IETF-822
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <4FDAFF60.3070509@alvestrand.no>
Date: Fri, 15 Jun 2012 11:13:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A768CD1A-8C03-473B-8DC1-5C956C2521F3@cs.columbia.edu>
References: <20120614213751.1985.262.idtracker@ietfa.amsl.com> <4FDA5B22.4040507@stpeter.im> <DE6911BA-1AF0-45FC-8A0A-34BBB4C3BEA5@checkpoint.com> <4FDAFF60.3070509@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.1278)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 15:13:24 -0000

On Jun 15, 2012, at 5:24 48AM, Harald Alvestrand wrote:

> On 06/15/2012 08:46 AM, Yoav Nir wrote:
>> On Jun 15, 2012, at 12:44 AM, Peter Saint-Andre wrote:
>>=20
>>> On 6/14/12 3:37 PM, IETF Secretariat wrote:
>>>=20
>>>> List address: ietf-822@ietf.org
>>> Is no one thinking ahead to the 822nd meeting of the IETF in the =
year
>>> 2258?!?
>> Well, I've started working on =
draft-nir-ipv6-were-finally-deploying-it but I'm not sure what format =
would be an appropriate submission format in the 23rd century.
> ASCII, of course. But the boilerplate will have changed.

Yes, but upgraded from US-ASCII to Federation of Planets-ASCII.


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From john-ietf@jck.com  Fri Jun 15 09:26:55 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2C6021F846C for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 09:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 dPl2vrj-KuJc for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 09:26:55 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 427BE21F8467 for <ietf@ietf.org>; Fri, 15 Jun 2012 09:26:55 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SfZG3-000Ncd-UB; Fri, 15 Jun 2012 12:20:23 -0400
Date: Fri, 15 Jun 2012 12:26:44 -0400
From: John C Klensin <john-ietf@jck.com>
To: Steven Bellovin <smb@cs.columbia.edu>, Harald Alvestrand <harald@alvestrand.no>
Subject: Re: New Non-WG Mailing List: IETF-822
Message-ID: <593D9F44CB30965E44DF97C1@JcK-HP8200.jck.com>
In-Reply-To: <A768CD1A-8C03-473B-8DC1-5C956C2521F3@cs.columbia.edu>
References: <20120614213751.1985.262.idtracker@ietfa.amsl.com> <4FDA5B22.4040507@stpeter.im> <DE6911BA-1AF0-45FC-8A0A-34BBB4C3BEA5@checkpoint.com> <4FDAFF60.3070509@alvestrand.no> <A768CD1A-8C03-473B-8DC1-5C956C2521F3@cs.columbia.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 16:26:55 -0000

--On Friday, June 15, 2012 11:13 -0400 Steven Bellovin
<smb@cs.columbia.edu> wrote:

>>> Well, I've started working on
>>> draft-nir-ipv6-were-finally-deploying-it but I'm not sure
>>> what format would be an appropriate submission format in the
>>> 23rd century.
>> ASCII, of course. But the boilerplate will have changed.
> 
> Yes, but upgraded from US-ASCII to Federation of Planets-ASCII.

Can't be anything-ASCII unless there is an ANSI on Mars or
further out.

FoPSCII ?

Maybe, in the interest of interplanetaryization (i19n ?) and
multigalacticism (m13m ?) we should start using FoPSCII and
Galicode references in our documents and noting that ASCII and
Unicode are temporary substitutes.

    john


   john




From touch@isi.edu  Fri Jun 15 09:52:33 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F14B21F8592 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 09:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 SPlbhkz2aIAR for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 09:52:32 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 93A1921F856F for <ietf@ietf.org>; Fri, 15 Jun 2012 09:52:31 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q5FGqJuO014349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Jun 2012 09:52:19 -0700 (PDT)
Message-ID: <4FDB6843.6090107@isi.edu>
Date: Fri, 15 Jun 2012 09:52:19 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 16:52:33 -0000

Masataka,

On 6/15/2012 3:48 AM, Masataka Ohta wrote:
> After thinking more about the draft, I think it is
> purposelessly hostile against innocent operators and
> end users who are suffering between people filtering
> ICMP and people insisting on PMTUD.
> 
> Today, innocent operators often clear DF bit and
> end users are happy with it, because, today, probability
> of accidental ID match is small enough.

That is not an innocent action. It defeats PMTUD, which is a draft
standard. It also violates RFC 791 and 1121.

> However, as the ID specifies:
> 
>     >>  Originating sources MAY set the IPv4 ID field of atomic datagrams
>     to any value.
> 
>     >>  IPv4 datagram transit devices MUST NOT clear the DF bit.
> 
> people insisting on PMTUD are now authorized to set ID always
> zero, trying to discourage ICMP filtering and DF bit clearing.
> 
> But, as people filtering ICMP won't stop doing so and if
> operators can do nothing other than clearing DF, it is
> end users who suffers.

This document only restates existing requirements in this regard,
stating them in 2119-language. It does not create any new requirement.
Operates that clear the DF bit are already in violation of three
standards-track RFCs.

> Then, end users may actively act against PMTUD and/or IETF.

I disagree; if they wanted to do so, they already would have acted since
the requirements already exist, albeit in pre-RFC2199 language.

Joe

> 
> 					Masataka Ohta

From touch@isi.edu  Fri Jun 15 10:03:15 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C944B21F85F0 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 10:03:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 gXDNLK+L47R7 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 10:03:15 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3674B21F85E1 for <ietf@ietf.org>; Fri, 15 Jun 2012 10:03:15 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q5FH2X9C016006 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Jun 2012 10:02:34 -0700 (PDT)
Message-ID: <4FDB6AA9.4090008@isi.edu>
Date: Fri, 15 Jun 2012 10:02:33 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <Pine.LNX.4.64.1206022127550.17026@shell4.bayarea.net> <4FCBB71E.9080209@necom830.hpcl.titech.ac.jp> <4FCEAA6B.20204@isi.edu> <4FDB2436.2060805@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4FDB2436.2060805@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 17:03:16 -0000

Hi, Masataka,

On 6/15/2012 5:01 AM, Masataka Ohta wrote:
> Joe Touch wrote:
> 
>> Hi,
> 
> Hi,
> 
>>> But, then,
>>>
>>>       >>    Sources emitting non-atomic datagrams MUST NOT repeat IPv4 ID
>>>       values within one MSL for a given source address/destination
>>>       address/protocol triple.
>>>
>>> makes most, if not all, IPv4 hosts non compliant if MSL=2min.
>>
>> This is already noted throughout this document, however there is little
>> impact to such non-compliance if datagrams don't persist that long.
> 
> So, the question to be asked is how long datagrams persist.
> 
> As you now say MSL may be smaller than 2min, the draft is
> useless to promote implementers implement rate limiting.
> 
> If you can't define hard value of MSL, implementors can
> assume anything.

MSL is not defined on a network unless it is enforced throughout the
network. The only MSL that matters is how long segments persist between
a pair of endpoints, which is why the draft states the requirement this way.

This was discussed at length in the WG and led to the language used
throughout this document.

The section you quote above later already states:

   Because there is no strict definition of the MSL, reassembly hazards
   exist regardless of the IPv4 ID reuse interval or the reassembly
   timeout. As a result:
...

Perhaps we should change "is no strict definition" to "can be no strict
definition"?

>>> Worse, without hard value of MSL, it is a meaningless
>>> requirement. Note that MSL=2min derived from RFC793 breaks
>>> 150Mbps TCP.
>>
>> It breaks at 6.4 Mbps for 1500 byte packets, as is already noted in the doc.
> 
> With practically very low probability.

"Breaks" means 'breaks the requirement'. The probability of doing this
for 1500-byte packets at 6.4 Mbps is 100%.

If you mean "and this causes problems", it generally doesn't because:

	a) most packets aren't fragmented
and
	b) fragments aren't reordered over the full 120-second delay

The problem is that you can't know the max fragment delay variability on
a path.

>>> The proper solution, IMHO, to the ID uniqueness is to request
>>> a destination host drop fragments from a source host after
>>> it receives tens (or hundreds) of packets with different IDs
>>> from the same source host.
>>
>> That doesn't help ID uniqueness; it helps avoid fragmentation
>> overload.
> 
> It does help ID uniqueness, because fragments with accidental
> matches are quickly discarded.
> 
>> FWIW, such issues were discussed at length in the INTAREA WG when this
>> doc was developed.
> 
> I appreciate that the draft is terse not including so lengthy
> discussions in the WG.
> 
> However, at the same time, don't expect me to read all the log
> of the discussions in the WG, especially because you and
> the discussions misunderstand the problem as:
> 
>> That doesn't help ID uniqueness; it helps avoid fragmentation
>> overload.
> 
> That does help ID uniqueness.

Again this was discussed in the WG and the conclusion of the group was
that it did not help. The document does not include the full text of the
discussions of the WG, nor does it include all alternatives that were
not selected.

If you can point to a specific thing we need to include, please let us know.

Joe

From dcrocker@bbiw.net  Fri Jun 15 10:47:54 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4081621F850B for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 10:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.351
X-Spam-Level: 
X-Spam-Status: No, score=-6.351 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 yWlV5lxYVlgA for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 10:47:53 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6028221F84D6 for <ietf@ietf.org>; Fri, 15 Jun 2012 10:47:52 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q5FHlpgN025405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Jun 2012 10:47:51 -0700
Message-ID: <4FDB7541.5040404@bbiw.net>
Date: Fri, 15 Jun 2012 10:47:45 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Graham Klyne <GK@ninebynine.org>
Subject: Re: registries and designated experts
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <4FD75881.3080102@dcrocker.net> <4FDB1510.40702@ninebynine.org>
In-Reply-To: <4FDB1510.40702@ninebynine.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 15 Jun 2012 10:47:52 -0700 (PDT)
Cc: "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 17:47:54 -0000

oh boy...

On 6/15/2012 3:57 AM, Graham Klyne wrote:
> On 12/06/2012 15:56, Dave Crocker wrote:
>> It's almost inevitable that many designated experts will, in fact,
>> act as gatekeepers.
...
> The effect may sometimes be similar to being a gatekeeper but,
> speaking for myself, that's not how I see my role.

Herein lies the core problem with these types of discussions:  Most 
participants use themselves as the metric.

Designing human processes requires consideration of other folk, not 
ourselves.  Other folk display widely varying behaviors.  They have less 
information and education on the topic than current participants.  They 
have moods.  They have distractions. They have biases.

In other words, real-world, human processes are "noisier" than we tend 
to design for.

When looking for factors to consider, a posting with "here's how I 
behave" can be extremely helpful.  When looking for what can go wrong, 
it actually tends to undermine the exercise, IMO.

Note that this is not about diligence.  It is about typical human vagaries.


> My experience is that no amount of review completely bullet-proofs a
>  spec against misinterpretation. So we do the best we can.

The second sentence is such a natural choice, given the first.  What it 
misses is that "the best" often means excessive hassle.  That is, very 
poor cost/benefit tradeoff analysis.

Quality control processes can and do help.  Carried to excess, they make 
the activity more effort than it is worth.

In the face of being unable to ensure perfect bullet-proofing, we often 
think that we need to put in more effort.  In fact what is often 
appropriate is /less/ formal bullet-proofing and trusting market forces 
to do the rest, since they will anyhow.

d/


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From jmpolk@cisco.com  Fri Jun 15 10:49:54 2012
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E5121F864E for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 10:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.901
X-Spam-Level: 
X-Spam-Status: No, score=-109.901 tagged_above=-999 required=5 tests=[AWL=0.698, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 yKCauZD0JvNl for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 10:49:53 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 4FDDF21F850B for <ietf@ietf.org>; Fri, 15 Jun 2012 10:49:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=632; q=dns/txt; s=iport; t=1339782593; x=1340992193; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=kZDrS3tv9qeHFtAnyTjn9FrXqlDCNiY0DwJsOv+HSx8=; b=dbQsyiXtZTqkcPeL8OsBtlakzq2JgXGO/HYogK/C4Cbu7Z9fsOv5jp1h BfQGNctbhSKBMB5RcYW2rJpdnn287dzF5CLIyL16xyX4f8Ts3fuXYvBFo n5blZ7n/Nc7gMzfSskZJAa5nwOsZahO01sxX2KDZrLHACx93dMMixtnjw Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAMx020+rRDoG/2dsb2JhbABFtVSBB4IYAQEBBBIBJQI0CxAHBA4KHhAZPgYBEiKHaJlhoCWLNoYRA4hCmnmBZoJ+
X-IronPort-AV: E=Sophos;i="4.75,779,1330905600"; d="scan'208";a="49109002"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 15 Jun 2012 17:49:52 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8714.cisco.com [10.99.80.21]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q5FHnpRL003924; Fri, 15 Jun 2012 17:49:51 GMT
Message-Id: <201206151749.q5FHnpRL003924@mtv-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 15 Jun 2012 12:49:30 -0500
To: Yoav Nir <ynir@checkpoint.com>, Peter Saint-Andre <stpeter@stpeter.im>
From: James Polk <jmpolk@cisco.com>
Subject: Re: New Non-WG Mailing List: IETF-822
In-Reply-To: <DE6911BA-1AF0-45FC-8A0A-34BBB4C3BEA5@checkpoint.com>
References: <20120614213751.1985.262.idtracker@ietfa.amsl.com> <4FDA5B22.4040507@stpeter.im> <DE6911BA-1AF0-45FC-8A0A-34BBB4C3BEA5@checkpoint.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 17:49:54 -0000

At 01:46 AM 6/15/2012, Yoav Nir wrote:

>On Jun 15, 2012, at 12:44 AM, Peter Saint-Andre wrote:
>
> > On 6/14/12 3:37 PM, IETF Secretariat wrote:
> >
> >> List address: ietf-822@ietf.org
> >
> > Is no one thinking ahead to the 822nd meeting of the IETF in the year
> > 2258?!?
>
>Well, I've started working on 
>draft-nir-ipv6-were-finally-deploying-it but I'm not sure what 
>format would be an appropriate submission format in the 23rd century.
>
>Doesn't it coincide with the 1st season of Babylon 5?

a B5 reference... this doesn't happen often enough IMO

BTW - 2258 was the second season of B5.


>Yoav


From john-ietf@jck.com  Fri Jun 15 11:17:29 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 149A421F84AC for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 11:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 fFtaKzlKwVcA for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 11:17:28 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7C84B21F8484 for <ietf@ietf.org>; Fri, 15 Jun 2012 11:17:28 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Sfaz5-000NjR-91; Fri, 15 Jun 2012 14:10:59 -0400
Date: Fri, 15 Jun 2012 14:17:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: Publishing the Tao as a web page
Message-ID: <8749BCD449F070AA5E9AFCE5@JcK-HP8200.jck.com>
In-Reply-To: <6D41FAFE-6B15-4CD5-AB00-59DE8E93AC7B@vpnc.org>
References: <CC1638DA-817E-4F2C-BD29-5EFED6CFCAEF@vpnc.org> <867BD23C-3581-4EDC-B4FF-973FEEBC253C@vpnc.org> <B0C00137-E868-4017-AF5D-932848AEF6A2@vigilsec.com> <6D41FAFE-6B15-4CD5-AB00-59DE8E93AC7B@vpnc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 18:17:29 -0000

--On Wednesday, June 13, 2012 13:44 -0700 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

>> but I can see the advantages if
>> others disagree.  On the other hand, publishing
>> draft-hoffman-tao4677bis in the RFC series seems to me to have
>> no value at all.  There should be an RFC 4677bis but it should
>> probably say little more than "Tao is now a web page at ....
>> and it is not being maintained in the RFC Series".
> 
> That's the purpose of this document.

Paul,

Having taken a quick look at -02 in the above context, let me
make an observation and small procedural suggestion:

The information in this I-D is exactly what the title and
abstract suggest (A Good Thing), namely an explanation of the
change from RFC publication and the new procedure.  But that
sets a bit of a trap because, if the procedural model changes
--as it inevitably will over time-- the RFC will need to be
revised.

So, I suggest that, after sufficient agreement on this document
and procedure are reached, you take the bulk of this document
and simply make it an appendix to the Tao.  Since the IESG has
to approve any changes to the Tao anyway, no control is lost,
but we avoid having to obsolete 4677bis, a document whose
purpose was the get the Tao out of the RFC Series.  Then we
produce a very short and focused 4677bis for the RFC Series that
says as little more than "out of the RFC Series, 4677 is
obsolete, doc is located at stable URI ..."

    john


From stephen.farrell@cs.tcd.ie  Fri Jun 15 12:18:24 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BAAE11E80C8 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 12:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
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 V9zSqcey41tl for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 12:18:21 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 8519011E8088 for <ietf@ietf.org>; Fri, 15 Jun 2012 12:18:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id EF695171829; Fri, 15 Jun 2012 20:18:17 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339787896; bh=AwjuG/52rk5gg2 9Bh3MVIPG/zOQ4fLJ3LFR3PusqBXs=; b=izGxUHuFlgM1WYUNGiGT098LF74VbE AfaAjHzKvPv+Cv+ysX/PFgsAMm6F9cbk+B+Sfi7qUmQVM/qo8bEIDrPSDbcRDLMt w81m3RXi68/kFzOP7U35Qj5i9iN7v9EFA+OT94mrEir11Wcrv05tgn1xAOGLq9q6 YKESB7GYcbpiwO5hKILt3DnC0gyD7Uw7lqJ/uDOLjj+2hLzafZtYdDmlNC/BMi3Y leo5VEOKfkBUOtuGT4ZdkNo3gzM6qYsPeX0UV7Q3qHMz2LmbWq7ymDWLAGAit0Q9 YcfOG+BjbrTbnrdMMv2sea1PyLEdwohLFfP++KETMM2jvPTNOf+VR+Ew==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id QgtzeIPCaF+W; Fri, 15 Jun 2012 20:18:16 +0100 (IST)
Received: from [10.87.48.7] (unknown [86.44.66.178]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 23CB3171471; Fri, 15 Jun 2012 20:18:11 +0100 (IST)
Message-ID: <4FDB8A73.4090707@cs.tcd.ie>
Date: Fri, 15 Jun 2012 20:18:11 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Graham Klyne <GK@ninebynine.org>
Subject: Re: APPSDIR review of draft-farrell-decade-ni-07, major design issue (one or two URI schemes)
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD712E8.7010506@cs.tcd.ie> <4FD73E76.7050105@it.aoyama.ac.jp> <4FD74D94.4020408@cs.tcd.ie> <4FDB1319.7040501@ninebynine.org>
In-Reply-To: <4FDB1319.7040501@ninebynine.org>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 19:18:24 -0000

Hi Graham,

On 06/15/2012 11:48 AM, Graham Klyne wrote:
> Stephen,
> 
> (Personal hat on)
> 
> I've followed elements of this exchange.  I must confess that when I
> read through the draft previously, I didn't really pay attention to the
> nih: parts.

I guess part of my reaction to Martin's comments was based on
an assumption that such a comment (make your two registrations
into one) was something one could expect to have gotten from
the uri-review list. But anyway...

> I can see that there are distinct use-cases here, and I think you have
> reasonable grounds for not wanting to combine them.

Right.

> What I can't see is why the speakable form (nih:) needs to be a URI
> scheme - what are the envisaged contexts of use where the information
> provided by an nih: URI actually needs to be a URI, as opposed to just,
> say, a simple string?
> 
> In all the uses I can think of for ni:, I don't see a corresponding use
> for a speakable form.  

I agree that there's little overlap for sure.

> I think you said somewhere in this exchange, nih:
> is intended to be used to confirm some information that you already
> have.  As such, I'm not seeing how it can be said to identify a resource.

I'm checking with others since I'm not entirely familiar with
all that they want from nih, (so you might be right, or maybe
not;-)

As far as I do know now, the idea is that nih could be useful
when values are to be read over the phone. I agree the listener
wouldn't need the scheme, but I think the argument is that it'd
help the speaker (or speaker's UA) to highlight the right thing.
I'd agree if you argued that that's not the most compelling
reason, but maybe there's more.

In terms of identifying a resource, I don't get the
comment, since the information is similar to that in an ni,
so it does identify whatever it is matches that hash.

Cheers,
S.

> 
> #g
> -- 
> 
> On 12/06/2012 15:09, Stephen Farrell wrote:
>>
>> Martin,
>>
>> I honestly don't think this exchange is going
>> anywhere new so I've not provided blow-by-blow
>> answers below.
>>
>> We (the authors) think ni and nih are better
>> kept separate because the use-cases and
>> requirements differ. And that's what the
>> limited amount of running code does.
>>
>> I think I've explained that, and I have no
>> intention whatsoever of getting into the "write
>> up the use-cases and requirements" game that
>> too-often happens in the IETF when its neither
>> needed nor productive. (Regardless of whether
>> the game is played with I-Ds or email.)
>> Sometimes that is useful, but not here IMO.
>>
>> You disagree, which is fine. You think ni and nih
>> should be merged because they don't differ
>> sufficiently, (I think), and (I guess) because
>> you think that new URI schemes are more expensive
>> than what you see as the differences between
>> these two proposed schemes warrant.
>>
>> I suggest we see if anyone else chimes in on
>> this aspect (so far nobody has, despite a quite
>> active IETF LC:-) and if not leave it to the
>> sponsoring AD to figure out what, if anything,
>> needs doing at the end of IETF LC.
>>
>> Cheers,
>> S.
>>
>> PS: Many thanks for all the other good comments,
>> though we disagree on this one, you've helped
>> make the draft better for sure.
>>
>>
>> On 06/12/2012 02:04 PM, "Martin J. Dürst" wrote:
>>> Hello Stephen,
>>>
>>> On 2012/06/12 18:59, Stephen Farrell wrote:
>>>>
>>>> Hi Martin,
>>>>
>>>> On 06/12/2012 10:13 AM, "Martin J. Dürst" wrote:
>>>>> Hello Stephen,
>>>>>
>>>>> This mail responds to your points on the main technical issue that I
>>>>> have identified.
>>>>>
>>>>> On 2012/06/05 20:11, Stephen Farrell wrote:
>>>>>
>>>>>> On 06/05/2012 10:42 AM, "Martin J. Dürst" wrote:
>>>>>>> Hello everybody,
>>>
>>>>>> Major design issue:
>>>>>>>
>>>>>>> The draft defines two schemes, which differ only slightly, and
>>>>>>> mostly
>>>>>>> just gratuitously (see also editorial issues).
>>>>>>> These are the ni: and the nih: scheme. As far as I understand, they
>>>>>>> differ as follows:
>>>>>>>                                        ni:                nih:
>>>>>>> authority:                          optional           disallowed
>>>>>>> ascii-compatible encoding:          base64url          base16
>>>>>>> check digit:                        disallowed         optional
>>>>>>> query part:                         optional           disallowed
>>>>>>> decimal presentation of algorithm:  disallowed         possible
>>>>
>>>> I'll note in passing that the two schemes differ in all those
>>>> respects. You may disagree with our design, but basically you're
>>>> showing that the two differ in pretty much all possible ways
>>>> other than that both include a hash value.
>>>>
>>>>>>>
>>>>>>> The usability of URIs is strongly influenced by the number of
>>>>>>> different
>>>>>>> schemes, with the smaller a number, the better. As a somewhat
>>>>>>> made-up
>>>>>>> example, if the original URIs had been separated into httph: for
>>>>>>> HTML
>>>>>>> pages and httpi: for images, or any other arbitrary subdivision
>>>>>>> that one
>>>>>>> can envision, that would have hurt the growth and extensibility
>>>>>>> of the
>>>>>>> Web. Creating new URI schemes is occasionally necessary, and the
>>>>>>> ideas
>>>>>>> that lead to this draft definitely seem to warrant a new scheme
>>>>>>> (*), but
>>>>>>> there's no reason for two schemes.
>>>>>>> [(*) I know people who would claim the the .well-formed http/https
>>>>>>> thing
>>>>>>> is completely sufficient, no new scheme needed at all.]
>>>>>>>
>>>>>>> More specifically, if the original URIs had been separated into
>>>>>>> httpm:
>>>>>>> (for machines) and httph: (for humans), the Web for sure wouldn't
>>>>>>> have
>>>>>>> grown at the speed it did (and does) grow. In practice, there are
>>>>>>> huge
>>>>>>> differences in human 'speakability' for URIs (and IRIs, for that
>>>>>>> matter); compare e.g. http://google.com with
>>>>>>> http://www.google.co.jp/#sclient=psy-ab&hl=en&site=&source=hp&q=hash&oq=hash&aq=f&aqi=g4&aql=
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> (which I have significantly shortened to hopefully eliminate
>>>>>>> potential
>>>>>>> privacy issues), or compare the average mailto: URI with the average
>>>>>>> data: URI. However, what's important is that there never has been a
>>>>>>> strong dividing line between machine-only and human-only URIs or
>>>>>>> schemes, the division has always been very gradual. Short and mainly
>>>>>>> human-oriented URIs have of course been handled by machines, and on
>>>>>>> the
>>>>>>> other hand, very long URIs have been spoken when really necessary.
>>>>>>> "Speakability" has been maintained to some extent by scheme
>>>>>>> designers,
>>>>>>> and to some extent by "survival of the fittest" (URIs that weren't
>>>>>>> very
>>>>>>> speakable (or spellable/memorizable/guessable/...), and their Web
>>>>>>> sites,
>>>>>>> might just die out slowly).
>>>>>>>
>>>>>>> It should also be noted that the resistance against multiple URI
>>>>>>> schemes
>>>>>>> may have been low because there are so many different ways to
>>>>>>> express
>>>>>>> hashes in the draft anyway, and one more (the nih: section is the
>>>>>>> last
>>>>>>> one before the examples section) didn't seem like much of a deal
>>>>>>> anymore. But when it comes to URIs, one less is a lot better than
>>>>>>> one
>>>>>>> more.
>>>>>>>
>>>>>>> In the above ni:/nih: distinction, nih: seems to have been added
>>>>>>> as an
>>>>>>> afterthought after realizing that reading an ni: URI aloud over the
>>>>>>> phone may be somewhat suboptimal because there is a need for
>>>>>>> repeated
>>>>>>> "upper case" - "lower case" (sure very quickly shortened to
>>>>>>> "upper" -
>>>>>>> "lower" and then to "up" - "low" or something similar). It is not a
>>>>>>> bad
>>>>>>> idea to try to make sure that IETF technology, and URIs in
>>>>>>> particular,
>>>>>>> are accessible to people with certain kinds of dislexya. (There are
>>>>>>> indeed people who have tremendous difficulties with distinguishing
>>>>>>> upper- and lower-case letters, and this may or may not be connected
>>>>>>> with
>>>>>>> other aspects of dislexya.) It is however totally unclear to this
>>>>>>> reviewer why this has to lead to two different URI schemes with
>>>>>>> other
>>>>>>> gratuitous differences.
>>>>>>>
>>>>>>> Finding a solution is rather easy (of course, other solutions may
>>>>>>> also
>>>>>>> be possible): Merge the schemes, so that authority, check digit, and
>>>>>>> query part are all optional (an authority part and/or a query
>>>>>>> part may
>>>>>>> very well be very useful in human communication, and a check digit
>>>>>>> won't
>>>>>>> hurt when transmitted electronically) and the decimal
>>>>>>> presentation of
>>>>>>> the algorithm is always allowed, and use base32
>>>>>>> (http://tools.ietf.org/html/rfc4648) as the encoding. This leads
>>>>>>> to a
>>>>>>> 16.6% less efficient encoding of the value part of the ni: URI, but
>>>>>>> given that other URI-related encodings, e.g. the %-encoding
>>>>>>> resulting
>>>>>>> when converting an IRI to an URI, are much less efficient, and that
>>>>>>> URI
>>>>>>> infrastructure these days can handle URIs with more than 1000 bytes,
>>>>>>> this should not be a serious problem. Also, there's a separate
>>>>>>> binary
>>>>>>> format (section 6) that is more compact already.
>>>>>>
>>>>>> I strongly disagree with merging ni&    nih. Though that clearly
>>>>>> could be done, it would be an error.
>>>>>>
>>>>>> There was no such comment on the uri-review list and the designated
>>>>>> expert was happy. That review was IMO the time for such comments
>>>>>> and second-guessing the designated expert at this stage seems
>>>>>> contrary to the registration requirements. So process-wise I
>>>>>> think your main comment is late.
>>>>>
>>>>> First, if IETF Last Call is too late to make serious technical
>>>>> comments
>>>>> on drafts, then I think we have to rename it to IETF Too-Late Call.
>>>>>
>>>>> Second, designated experts are there to check for minimum requirements
>>>>> for a registration, and to give advice as they see fit (and have
>>>>> time).
>>>>> I'm myself a designated expert on "Character Sets", and I have
>>>>> definitely in the past approved, and would again in the future
>>>>> approve,
>>>>> registrations for stuff on which I would complain strongly if the
>>>>> question was "is this a good technical solution".
>>>>>
>>>>> Graham Klyne, the designated expert for URI scheme registrations, has
>>>>> confirmed offline that he does not see his role as "expert
>>>>> reviewer" as
>>>>> judging the technical merit of a URI scheme proposal.
>>>>
>>>> While that's fair enough. Its also fair to note that there was
>>>> discussion of the this document on the uri-review list but this
>>>> aspect was not raised at all. That list is called "uri-review"
>>>> and from its archives it does seem to frequently do more than
>>>> just check the paperwork (including quite a few mails from you:-).
>>>
>>> Oh well. I'm not sure how familiar you are with the IETF :-), but it's
>>> basically all a volunteer organization. So even more than in an
>>> organization where people are getting paid, some things happen to get a
>>> lot of attention and other things happen to get less attention than
>>> maybe they would deserve. And most people have their day jobs, and
>>> occasionally miss a mail or two, or even a few more. And many people are
>>> on many lists and just skim them until something catches their eye, and
>>> ignore many threads. If you don't do anything like this and survive, I'd
>>> like to know how :-).
>>>
>>> So the uri-review list, like any other IETF (or other) list, can get
>>> excited about stuff, sometimes for good reasons, or can just ignore some
>>> aspects of some proposal. It's unfortunate, but it's something we have
>>> to live with. You can't ask everybody on that list to take the same
>>> amount of time to look at all the proposals that e.g. a Security
>>> Directorate or Apps Area Directorate reviewer is using.
>>>
>>>
>>>>>> But in any case, I also think you're wrong technically in this>>  
>>>>>> case.
>>>>>
>>>>> Let's see. I hope we agree that we should come to a conclusion on this
>>>>> issue on technical merits, rather than on process details.
>>>>
>>>> Sure.
>>>
>>> Good.
>>>
>>>>>> nih *is* intended for a corner case,
>>>>
>>>> Let me emphasise the above. nih is not intended to be used
>>>> broadly, nor often. If you want a hash-based URI scheme for
>>>> users to speak that is for broad frequent use then I think
>>>> you are free to try design one. But nih is not that and is
>>>> not intended to be that.
>>>
>>> Then, at the barest minimum, don't sell it as that. The only thing the
>>> draft essentially says is "use this if you want to read/speak it". Now
>>> you are saying "don't use that for users to speak, unless in specific
>>> corner cases", but you still haven't told me or the readers of the draft
>>> what these corner cases are, and why the SHOULD/MUST not use it
>>> otherwise even if they might think it makes sense.
>>>
>>> The second, more general advice is of course to not design URIs for
>>> corner cases, because URIs work best if they are used widely. (There may
>>> be a very tiny chance that your case is different, but even after
>>> reading all your mail, I haven't understood that.)
>>>
>>>
>>>> (And I'm not sure such a beast
>>>> could really be done well.)
>>>
>>> Speaking 256 or so bits of random data aloud is in no way going to be
>>> terribly easy :-).
>>>
>>>
>>>>>> where humans need to speak these
>>>>>> URIs and was added as a direct result of requirements from the core
>>>>>> WG and not as an afterthought. ni URIs are not intended for that
>>>>>> and so there really are IMO different requirements, (esp. e.g.
>>>>>> checkdigit) that are best met with different schemes.
>>>>>
>>>>> I agree that the value of a checkdigit is very limited for
>>>>> communication
>>>>
>>>> s/very limited/useless/
>>>>
>>>>> among machines (and for communication among humans with the help of
>>>>> machines, such as in the case of email).
>>>>>
>>>>> On the other hand, I can't understand why (even assuming we needed a
>>>>> separate scheme) there is no authority and no query part on nih.
>>>>
>>>> The main intent of nih is to allow entry of something that
>>>> confirms something else (e.g. a public key) that is already
>>>> present.
>>>
>>> At least a little bit of information about the "use case", but this just
>>> leads to more questions:
>>>
>>> Do you need an URI for that? (Isn't that what people are supposed to do
>>> with fingerprints these days?)
>>>
>>> How/where would a user input that URI e.g. in a browser?
>>>
>>> Would copy/paste from an email or a Web page be fine?
>>>
>>> Would entry be needed, or could it just be checked? (I understand that
>>> forcing a user to enter the data is way safer than believing her that a
>>> check was made, but then it's also way more tedious, and many users will
>>> just switch to different software.)
>>>
>>> Can ni: URIs also be used for the same purpose? If not, why not (they
>>> essentially contain the same information)?
>>>
>>> What about other URIs, starting e.g. with http:?
>>>
>>> I won't claim that this list of questions is exhaustive, but I hope it's
>>> a good start.
>>>
>>>
>>>> There is no need for an authority for that, for
>>>> the use-cases we have. We could speculate about other potential
>>>> use-cases but we'd rather not speculate like that when there's
>>>> no need to.
>>>
>>> There was a lot of stuff that we take for granted today that Tim
>>> Berners-Lee didn't speculate when he designed the first URI schemes. But
>>> if he had designed these schemes with only corner cases in mind, he
>>> wouldn't have invented the Web :-). (sorry about an analogy again)
>>>
>>>
>>>>> For the authority, I'd assume that it would be as useful when the
>>>>> URI is
>>>>> transmitted e.g. over the phone as when it is transmitted e.g. over
>>>>> email.
>>>>
>>>> We don't have a use for that that I know about.
>>>
>>> Do you mean the "over the phone" part or the authority part? (assuming
>>> the later below)
>>>
>>>> I agree
>>>> it could be done, but then I think it'd also impact on
>>>> usability, which will be pretty crap no matter what's
>>>> done.
>>>
>>> Reading "example.com" or some equivalent domain name in addition to a
>>> long hex string shouldn't really make matters much worse.
>>>
>>>> But making usability worse also seems wrong.
>>>
>>> My understanding is that there are some cases where things will be found
>>> with authority, but not without. If that's right, then I'm sure users
>>> will prefer to find what they are looking for, after aurally
>>> transmitting 256 or thereabout bits, even at the cost of an additional
>>> domain name (and a few slashes), which are the easiest parts to get
>>> across the line quickly and correctly.
>>>
>>>
>>>> Not
>>>> having an authority also seems to work fine for PGP keys
>>>
>>> That the lack of authority works in some cases is perfectly okay. But
>>> it's not an argument for not allowing authority for cases (even those
>>> that maybe you're not seeing yet) where it is or will be useful.
>>>
>>>
>>>> and the lack of an authority does get rid of some threats,
>>>> if the nih URI is used for something security-sensitive.
>>>
>>> Which would mean that ni: has these threats, yes? Where are they
>>> described? I don't remember seeing them in the security section.
>>>
>>>
>>>>> For the query part, there are already various ideas and proposals
>>>>> floating around,
>>>>
>>>> Where? If you mean draft-hallambaker-decade-params
>>>
>>> Correct.
>>>
>>>> then
>>>> we (the authors of that) don't think those are useful for
>>>> nih names.
>>>
>>> Why not? And what if others think they would be useful?
>>>
>>>
>>>>> and at least some of them would be of interest for when
>>>>> the URI is transmitted e.g. over the phone. Also, even if we currently
>>>>> didn't have any actual proposals for query parameters, I think it
>>>>> would
>>>>> be a very bad idea to exclude them a priori for transmission e.g. over
>>>>> the phone.
>>>>
>>>> I disagree that there is any "very bad idea" here.
>>>>
>>>>>> Merging ni/nih would also add more complexity for no benefit,
>>>>>> which would be a bad idea.
>>>>>
>>>>> Can you please explain what kind of complexity would have to be added?
>>>>
>>>> I think its obvious actually. In your table above you highlighted
>>>> 5 ways in which ni and nih differ. Merging all those yields loads
>>>> of combinations, which makes for complexity.
>>>
>>> Well, if your implementation is a big switch with 32 cases, one for each
>>> combination, with no code sharing, then indeed you get complexity. But I
>>> hope we agree that that's very bad design, and totally unnecessary. It's
>>> very straightforward to go through the components one-by-one and deal
>>> with them (hint: I'd start with the check digit).
>>>
>>> On the other hand, the complexity you get from query parameters is
>>> potentially huge, because, contrary to the basic syntax, we don't know
>>> for sure what combinations of parameters people will dream up, and how
>>> these will interact.
>>>
>>>
>>>>> In terms of specification, merging the two schemes doesn't seem to be
>>>>> difficult or complex at all. Also, in terms of implementation, the
>>>>> only
>>>>> additions to the ni: scheme that become necessary are the check digit
>>>>> and the expression of the "suite id" as a decimal. It's very difficult
>>>>> for me to imagine that this would add significant complexity to an
>>>>> implementation; if code for nih: exists, that can mostly just be moved
>>>>> over.
>>>>
>>>> Feel free to look at our code. (With the caveat that I'm a crap
>>>> programmer so close your eyes a bit when you look at the 'C' code:-)
>>>>
>>>>>> Your analogy about httpm/h may appear reasonable, but it is always
>>>>>> unreasonable to draw conclusions from analogies. It is also unwise
>>>>>> to reason from counterfactuals, which we'd also be doing if we
>>>>>> accepted your argument. So I find that speculation utterly useless
>>>>>> to be honest.
>>>>>
>>>>> It is definitely unreasonable to draw conclusions from analogies
>>>>> *only*.
>>>>
>>>> I only saw the analogy. What in your httpm/h argument is not
>>>> couterfactual analogy?
>>>
>>> Do you claim that it's not true that URIs are often transferred
>>> electronically, often transferred on paper, and often spoken, and that
>>> these sets for which these activities happen overlap? If you think that
>>> has to be different for ni:/nih:, you have to convince me, not the other
>>> way round.
>>>
>>>
>>>>> But if you think that the httpm/h analogy is wrong, and that ni/nih is
>>>>> different, could you please explain *what* is different?
>>>>
>>>> We have real use cases for ni and nih and we think they differ.
>>>> I'd be repeating myself to say why again.
>>>
>>> You're still very vague on these "real use cases". Confirmation of PGP
>>> keys by speaking the URI aloud seems to be your main/only use case for
>>> nih:. But I'm only guessing, because you haven't really explained
>>> this yet.
>>>
>>>>>> In this case, we are dealing with different requirements so this
>>>>>> should stay as-is.
>>>>>
>>>>> If "different requirements" is your main (or only) real argument,
>>>>
>>>> That would be a valid argument.
>>>
>>> It would only be a valid argument if these are requirements that can't
>>> be consolidated.
>>>
>>>
>>>>> could
>>>>> you at least explain exactly how they are different?
>>>>
>>>> I did that above. Asking for an "exact" explanation seems
>>>> like asking the same thing again.
>>>
>>> Here are the pieces of text from above that I can at least in some way
>>> link to actual requirements:
>>> "nih is not intended to be used broadly, nor often."
>>> "The main intent of nih is to allow entry of something that
>>> confirms something else (e.g. a public key) that is already
>>> present."
>>>
>>> Is that all there is? Or did I miss something? Maybe it would help this
>>> discussion if you wrote a few paragraphs of free-standing text
>>> explaining the use cases (and restrictions, and reasons for these) for
>>> both schemes. It may turn out to be a valid addition to the document at
>>> the very minimum. (I'm not asking for an independent "use cases and
>>> requirements" draft :-)
>>>
>>>
>>>>> Just that one
>>>>> requirement came from the core WG and others from other WGs or other
>>>>> parties doesn't help me to understand how the actual requirements
>>>>> differ. (Please note that even if the requirements differ, that
>>>>> doesn't
>>>>> mean that we need different technology to address them.)
>>>>
>>>> Perhaps not. But that was the design choice we made and its
>>>> a valid one.
>>>
>>> Given the more than 20 years of experience we have of how URIs are
>>> handled on the Web and around it, I have very good reasons to strongly
>>> doubt that this is a good design choice.
>>>
>>>
>>>>> Why do you say that ni: URIs are not intended for humans to speak?
>>>>
>>>> So phone me up and say this:
>>>>
>>>>     ni:///sha-256;UyaQV-Ev4rdLoHyJJWCi11OHfrYv9E1aGQAlMO2X_-Q
>>>
>>> So apart from the upper/lower problem, would the equivalent nih: URI be
>>> any better?
>>>
>>>>> What
>>>>> am I supposed to do if I got an ni: URI in a mail message and call you
>>>>> on the phone to tell you about that?
>>>>
>>>> Not my problem actually, but I guess most people might
>>>> say "remember that mail you sent me with all that gobbledygook
>>>> nonsense - what the hell was that about?" :-)
>>>
>>> I think "tell you about it" should have been "speak it out to you".
>>>
>>>
>>>>>    If I want to send somebody the
>>>>> information in an ni: URI by mail, should I use only the ni:
>>>>> version or
>>>>> only the nih: version, or both, if I can't exclude that the recipient
>>>>> may want to relay this information via voice?
>>>>
>>>> You can try either and let me know what works. This seems like
>>>> a very artificial use-case for ni.
>>>
>>> Why artificial? Long URIs get spoken over the phone once in a while. And
>>> I really don't understand why this is "very artificial" for ni:, but
>>> "indispensable" for nih:.
>>>
>>>
>>>>>> Finally, we have (some, early,) running code that matches the
>>>>>> current draft and that ought also count for something
>>>>>
>>>>> How much?
>>>>
>>>> Feel free to go look and see. [1] I've not counted lines of
>>>> code, but we have c, python, ruby and clojure library
>>>> implementations and some apps and other bits and pieces.
>>>>
>>>>      [1] http://sourceforge.net/projects/netinf/
>>>>
>>>>> The boiler plate on every ID is pretty clear that they are not
>>>>> set in stone. Also, the changes needed to merge the two schemes are
>>>>> not
>>>>> rocket science, quite to the contrary. (I herewith volunteer to fix
>>>>> the
>>>>> Ruby version, just to show)
>>>>
>>>> I didn't say our code is set in stone. I said that running code
>>>> counts.
>>>>
>>>> I didn't say a merge would require rocket science.
>>>
>>> It somehow sounded like this.
>>>
>>>> I said it'd be
>>>> a bad idea and would produce a worse result.
>>>
>>> Can you substantiate that? The discussion on use cases is still open,
>>> and the argument with all the 32 combinations also didn't fly.
>>>
>>>>>> when compared
>>>>>> to a change that would be a gratuitous dis-improvement
>>>>>
>>>>> In what sense would merging the two schemes be a dis-improvement? Can
>>>>> you please explain?
>>>>
>>>> I believe I did that above.
>>>
>>> Very marginally, perhaps. More information would definitely help.
>>>
>>>>>> based it
>>>>>> seems upon dubious argument
>>>>>
>>>>> If you think that my arguments are dubious, please explain exactly
>>>>> why.
>>>>
>>>> I believe I did that above. (To be clear: not all your argument is
>>>> dubious
>>>
>>> Thanks for some encouragement :-).
>>>
>>>
>>>> but the httph/m part is IMO.)
>>>
>>> I'm sorry that I started out with that analogy, but I thought it would
>>> be easy to understand. You seem to be caught in the specific use/corner
>>> cases, but I'm trying to look at the long term big picture.
>>>
>>>
>>>>>> that is also offered at the wrong
>>>>>> point in the process.
>>>>>
>>>>> See above. If there's something wrong with IETF Last Call, or with the
>>>>> fact that the Apps Area Directorate does reviews (which I don't
>>>>> think),
>>>>> then that should be addressed separately. For this discussion, I
>>>>> hope we
>>>>> can concentrate on technical issues.
>>>>
>>>> Right. But let's not ignore the fact that the uri-review
>>>> list had sight of this at the end of April.
>>>
>>> [If you keep insisting, why don't you check your MUA and look at all the
>>> messages I sent on the draft. You may be surprised, but I seriously hope
>>> you will stop bringing up "uri-review" again.]
>>>
>>>
>>>> Bottom line - we have use-cases and a valid design and running
>>>> code that as far as we know works and I see no reason to make
>>>> the change you'd like, which would make thing worse IMO.
>>>
>>> It may look like some more work in the short time, but it will make
>>> things more general and create more potential for the future.
>>>
>>>
>>> Regards,    Martin.
>>>
>>>
>>
> 

From jnc@mercury.lcs.mit.edu  Fri Jun 15 12:57:30 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8BB911E808A for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 12:57:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 KPBiTyDqbZ9k for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 12:57:30 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 465E521F8440 for <ietf@ietf.org>; Fri, 15 Jun 2012 12:57:30 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1132E18C18D; Fri, 15 Jun 2012 15:57:29 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: New Non-WG Mailing List: IETF-822
Message-Id: <20120615195729.1132E18C18D@mercury.lcs.mit.edu>
Date: Fri, 15 Jun 2012 15:57:29 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 19:57:30 -0000

    > From: Yoav Nir <ynir@checkpoint.com>

    > I've started working on draft-nir-ipv6-were-finally-deploying-it but
    > I'm not sure what format would be an appropriate submission format in
    > the 23rd century.

The Emperor finds your lack of faith... disturbing.

	Noel

From johnl@iecc.com  Fri Jun 15 12:59:18 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EE1711E809C for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 12:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 N-p-EhXQokiX for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 12:59:17 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id BB59911E808A for <ietf@ietf.org>; Fri, 15 Jun 2012 12:59:16 -0700 (PDT)
Received: (qmail 95666 invoked from network); 15 Jun 2012 19:59:16 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 15 Jun 2012 19:59:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4fdb9414.xn--hew.k1206; i=johnl@user.iecc.com; bh=z86a5e1uX8gPgvyo6wqOzIFlYHrgvTjtAXR77sH0dEQ=; b=R7Kkp78V1IuLQvs8/i8tKAHEorECakDkEtErg8W5xZe2HvSVrmVkXlh7jXPW8LNOIdH2uGbt+2fm3t3NU4Ytreq2R0/wFNsuHmuLdEdYrJn226MXeg7r7pQOcNb6DoJ2OIYdmeh/S1LulKSDcTcc/tINAviN6wqsrOD1Jk2arwE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 15 Jun 2012 19:58:54 -0000
Message-ID: <20120615195854.71801.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: New Non-WG Mailing List: IETF-822
In-Reply-To: <593D9F44CB30965E44DF97C1@JcK-HP8200.jck.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: john-ietf@jck.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 19:59:18 -0000

>Maybe, in the interest of interplanetaryization (i19n ?) and
>multigalacticism (m13m ?) we should start using FoPSCII and
>Galicode references in our documents and noting that ASCII and
>Unicode are temporary substitutes.

It hardly seems worth the effort, since the only difference between
ASCII and FoPSCII is that the ASCII # is replaced by the modern
currency symbol, and, of course, they put the little gap back in the
vertical bar to resolve the concerns about religious and cultural
insensitivty.

R's,
John

From dhc@dcrocker.net  Fri Jun 15 13:08:18 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 489FE21F8510 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 13:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ariT3CoXikTo for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 13:08:17 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 728AB21F84FC for <ietf@ietf.org>; Fri, 15 Jun 2012 13:08:17 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q5FK8GaF028076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 15 Jun 2012 13:08:17 -0700
Message-ID: <4FDB962B.2030101@dcrocker.net>
Date: Fri, 15 Jun 2012 13:08:11 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: New Non-WG Mailing List: IETF-822
References: <20120615195854.71801.qmail@joyce.lan>
In-Reply-To: <20120615195854.71801.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 15 Jun 2012 13:08:17 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 20:08:18 -0000

On 6/15/2012 12:58 PM, John Levine wrote:
> It hardly seems worth the effort, since the only difference between
> ASCII and FoPSCII is that the ASCII # is replaced by the modern
> currency symbol, and, of course, they put the little gap back in the
> vertical bar to resolve the concerns about religious and cultural
> insensitivty.


The more important questions are: who invented FoPSCII and how old were 
they?

d/

ps. the less important question is how many folk don't get the reference?

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From stpeter@stpeter.im  Fri Jun 15 14:03:21 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CDB611E80D0 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 dWaoe3Y+eDnO for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:03:20 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id D668011E8088 for <ietf@ietf.org>; Fri, 15 Jun 2012 14:03:20 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id DC476400EE for <ietf@ietf.org>; Fri, 15 Jun 2012 15:20:39 -0600 (MDT)
Message-ID: <4FDBA317.4010001@stpeter.im>
Date: Fri, 15 Jun 2012 15:03:19 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com>
In-Reply-To: <20120615202915.11032.53296.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 21:03:21 -0000

On 6/15/12 2:29 PM, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Publishing the "Tao of the IETF" as a Web Page'
>   <draft-hoffman-tao-as-web-page-02.txt> as Informational RFC

Looks good to me. I'd prefer a slightly different model (e.g., group
wiki with a limited number of contributors), but this model is also
workable.

One possible oversight is that this I-D does not describe how the editor
will work on the tao-possible-revision.html file (e.g., will only the
editor have permissions to work on that, might there be multiple
committers, will it be under source control?). Are such details
intentionally out of scope?

Peter

P.S. Two typos:

s/lead/led/
s/propsed/proposed/


From john-ietf@jck.com  Fri Jun 15 14:21:09 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D0A311E80E1 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:21:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.855
X-Spam-Level: 
X-Spam-Status: No, score=-101.855 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, USER_IN_WHITELIST=-100]
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 9IlK-EHTzpEd for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:21:09 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C613B11E8088 for <ietf@ietf.org>; Fri, 15 Jun 2012 14:21:08 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Sfdqn-000Ntn-Eu; Fri, 15 Jun 2012 17:14:37 -0400
Date: Fri, 15 Jun 2012 17:20:57 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@iecc.com>, ietf@ietf.org
Subject: Re: New Non-WG Mailing List: IETF-822
Message-ID: <60F818CB9BBA86B709B1E1D2@JcK-HP8200.jck.com>
In-Reply-To: <20120615195854.71801.qmail@joyce.lan>
References: <20120615195854.71801.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 21:21:10 -0000

--On Friday, June 15, 2012 19:58 +0000 John Levine
<johnl@iecc.com> wrote:

>> Maybe, in the interest of interplanetaryization (i19n ?) and
>> multigalacticism (m13m ?) we should start using FoPSCII and
>> Galicode references in our documents and noting that ASCII =
and
>> Unicode are temporary substitutes.
>=20
> It hardly seems worth the effort, since the only difference
> between ASCII and FoPSCII is that the ASCII # is replaced by
> the modern currency symbol, and, of course, they put the
> little gap back in the vertical bar to resolve the concerns
> about religious and cultural insensitivty.

Huh?   ISO/IEC 646 IRV (another candidate for a FoPSCII
precursor) replaces the ASCII $, not #, with that universal
currency symbol.  As for that vertical bar, sufficiently elderly
practitioners of the art of Character Confusion and Coding (CCS)
will recall that the ancient Earthling-Based Convention for
Difficult Information Coding included two peculiar characters: a
mathematical "not" sign that closely resembled Unicode's =
"=E2=8C=90"
(U+2310) and that broken vertical bar.  Those characters spawned
multiple wars over how they should be mapped into "ASCII" and
"ISO/IEC 646" with one group arguing for caret and (solid)
vertical bar, another for tilde and exclamation mark, and a
third for exclamation mark and [solid] vertical bar.  After much
bloodshed, 16 and 32 bit character sets were invented so that
almost everyone could contemplate their cakes while eating them
and continued dissenters were tortured until they repented.

Those battles were repeated in the development of FoPSCII when
it was noticed that the 5th character of the Klingon alphabet
was confusable with both the not-sign, Greek upper case Gamma,
and  Latin "r".  In addition, the Klingon numeral 8 was easily
confused with Cyrillic "=D0=96".  This created a variant problem
that the Intergalactic Consortium for Arbitrary Names and
Numbers could not dismiss because of some of the advocates had a
more effective means of persuasion than merely hiring lawyers.

:-(

   john



From paul.hoffman@vpnc.org  Fri Jun 15 14:27:12 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9390811E80D0 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lMnIsWybMxLE for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:27:12 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0F7D611E8088 for <ietf@ietf.org>; Fri, 15 Jun 2012 14:27:11 -0700 (PDT)
Received: from [10.20.30.101] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q5FLR9G3031018 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 15 Jun 2012 14:27:10 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4FDBA317.4010001@stpeter.im>
Date: Fri, 15 Jun 2012 14:27:08 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E550DD2D-D21E-44D0-A987-0DE391ABD7DB@vpnc.org>
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <4FDBA317.4010001@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1278)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 21:27:12 -0000

On Jun 15, 2012, at 2:03 PM, Peter Saint-Andre wrote:

> One possible oversight is that this I-D does not describe how the =
editor
> will work on the tao-possible-revision.html file (e.g., will only the
> editor have permissions to work on that, might there be multiple
> committers, will it be under source control?). Are such details
> intentionally out of scope?


I would imagine that that would be determined by the IESG when they pick =
a Tao editor.

--Paul Hoffman


From stpeter@stpeter.im  Fri Jun 15 14:28:39 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF8811E80D9 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 CNm1Y7Is4R4J for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:28:39 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E78CD11E8088 for <ietf@ietf.org>; Fri, 15 Jun 2012 14:28:38 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0A613400A4; Fri, 15 Jun 2012 15:45:57 -0600 (MDT)
Message-ID: <4FDBA905.4060502@stpeter.im>
Date: Fri, 15 Jun 2012 15:28:37 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <4FDBA317.4010001@stpeter.im> <E550DD2D-D21E-44D0-A987-0DE391ABD7DB@vpnc.org>
In-Reply-To: <E550DD2D-D21E-44D0-A987-0DE391ABD7DB@vpnc.org>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 21:28:39 -0000

On 6/15/12 3:27 PM, Paul Hoffman wrote:
> On Jun 15, 2012, at 2:03 PM, Peter Saint-Andre wrote:
> 
>> One possible oversight is that this I-D does not describe how the editor
>> will work on the tao-possible-revision.html file (e.g., will only the
>> editor have permissions to work on that, might there be multiple
>> committers, will it be under source control?). Are such details
>> intentionally out of scope?
> 
> 
> I would imagine that that would be determined by the IESG when they pick a Tao editor.

Fine with me. I'm not even saying this I-D needs to say it's out of
scope, I merely curious.

/psa




From eburger-l@standardstrack.com  Fri Jun 15 14:37:55 2012
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26F8111E80DF; Fri, 15 Jun 2012 14:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 TxHAvcShsReA; Fri, 15 Jun 2012 14:37:54 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id 77B5B11E8088; Fri, 15 Jun 2012 14:37:54 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:55294 helo=[192.168.15.135]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1SfeDI-00010s-Bf; Fri, 15 Jun 2012 14:37:52 -0700
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org>
Date: Fri, 15 Jun 2012 17:37:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org>
To: IETF Chair <chair@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 21:37:55 -0000

Do we have guidelines as to what is an "organization affiliation"?

On Jun 14, 2012, at 5:26 PM, IETF Chair wrote:

> Two things have occurred since the message below as sent to the IETF =
mail list.  First, we got a lawyer in Europe to do some investigation, =
and the inclusion of the email address on the blue sheet will lead to =
trouble with the European privacy laws.  Second, Ted Hardie suggested =
that we could require a password to access the scanned blue sheet.
>=20
> Based on the European privacy law information, the use of email will =
result in a major burden.  If the email address is used, then we must =
provide a way for people to ask for their email address to be remove at =
any time in the future, even if we got prior approval to include it.  =
Therefore, I suggest that we collect organization affiliation to =
discriminate between multiple people with the same name instead of email =
address.
>=20
> Based on Ted's suggestion, I checked with the Secretariat about using =
a datatracker login to download the scanned blue sheet.  This is fairly =
easy to do, once the community tracking tools are deployed.  However, =
with the removal of the email addresses from the blue sheets, it is =
unclear that there is any further need for password protection of these =
images.  Therefore, I suggest that we proceed without password =
protection for the blue sheet images.
>=20
> Here is a summary of the suggested way forward:
>=20
> - Stop collecting email addresses on blue sheets;
>=20
> - Collect organization affiliation to discriminate between multiple =
people with the same name;
>=20
> - Scan the blue sheets and include the images in the proceedings for =
the WG session;
>=20
> - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and
>=20
> - Discard paper blue sheets after scanning.
>=20
> Russ
>=20
>=20
> On May 6, 2012, at 12:46 PM, IETF Chair wrote:
>=20
>> We have heard from many community participants, and consensus is =
quite rough on this topic.  The IESG discussed this thread and reached =
two conclusions:
>>=20
>> (1) Rough consensus: an open and transparent standards process is =
more important to the IETF than privacy of blue sheet information.
>>=20
>> (2) Rough consensus: inclusion of email addresses is a good way to =
distinguish participants with the same or similar names.
>>=20
>>=20
>> Based on these conclusions, the plan is to handle blue sheets as =
follows:
>>=20
>> - Continue to collect email addresses on blue sheets;
>>=20
>> - Scan the blue sheet and include the image in the proceedings for =
the WG session;
>>=20
>> - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and
>>=20
>> - Discard paper blue sheets after scanning.
>>=20
>>=20
>> On behalf of the IESG,
>> Russ
>>=20
>=20


From edj.etc@gmail.com  Fri Jun 15 14:42:40 2012
Return-Path: <edj.etc@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C52ED11E80D0; Fri, 15 Jun 2012 14:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.846
X-Spam-Level: 
X-Spam-Status: No, score=-101.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 77B5F3RdIa6R; Fri, 15 Jun 2012 14:42:40 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 080B111E80CE; Fri, 15 Jun 2012 14:42:39 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so3022479ggn.31 for <multiple recipients>; Fri, 15 Jun 2012 14:42:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-rim-org-msg-ref-id:message-id:content-transfer-encoding:reply-to :x-priority:references:in-reply-to:sensitivity:importance:subject:to :cc:from:date:content-type:mime-version; bh=My3c6LzIUHnPX6W6NR/ToXH8bagNnuIz89JItyd8Y3I=; b=nKCUlAk5l8in+li0q49eQNg8j0jUNmTyT+McSDjcIBOPG114hCMSwYMm+2vUuYWg5/ eOg+jnjnRpK19QqTMeLpGMsZJR79bC4H9c4Zn/yXSK5h/4w2yxVI4nSaH9e2VgYLR20T 7yRMRT47dNTgwLHLn1Zq4A0yulHn1MWqlBMYwUlWFeJKW9HK+T6nyc+64XgOHdltnh3y q4nrVVsAhGoR/OlhARPkH681wfs42Bnd8LgDauQDp1X5l341KyTBBiRww66squzBWlNb +NsuQUleEwEplOs7vrTscgbGqmoeC5UdxpULJvVEU2sVLpEx7TbQkYCaFFHXLAKHqM/D TIBg==
Received: by 10.50.159.227 with SMTP id xf3mr3378538igb.24.1339796559270; Fri, 15 Jun 2012 14:42:39 -0700 (PDT)
Received: from 172.29.195.211 (bda-74-82-80-108.bis6.us.blackberry.com. [74.82.80.108]) by mx.google.com with ESMTPS id v17sm3720700igv.7.2012.06.15.14.42.37 (version=SSLv3 cipher=OTHER); Fri, 15 Jun 2012 14:42:38 -0700 (PDT)
X-rim-org-msg-ref-id: 616737881
Message-ID: <616737881-1339796556-cardhu_decombobulator_blackberry.rim.net-133583724-@b2.c2.bise6.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org> <F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com>
In-Reply-To: <F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com>
Sensitivity: Normal
Importance: Normal
Subject: Re: Future Handling of Blue Sheets
To: "Eric Burger" <eburger-l@standardstrack.com>, ietf-bounces@ietf.org, "IETF Chair" <chair@ietf.org>
From: edj.etc@gmail.com
Date: Fri, 15 Jun 2012 21:42:34 +0000
Content-Type: text/plain
MIME-Version: 1.0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: edj.etc@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 21:42:40 -0000

SSBwcmVzdW1lIGl0IGlzIHRoZSBzYW1lIGRhdGEgdGhhdCBwZW9wbGUgaW5wdXQgaW50byB0aGUg
Ik9yZ2FuaXphdGlvbiIgZmllbGQgd2hlbiB0aGV5IHJlZ2lzdGVyIGZvciB0aGUgbWVldGluZy4N
Cg0KUmVnYXJkcywNCg0KRWQgIEouDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9t
OiBFcmljIEJ1cmdlciA8ZWJ1cmdlci1sQHN0YW5kYXJkc3RyYWNrLmNvbT4NClNlbmRlcjogaWV0
Zi1ib3VuY2VzQGlldGYub3JnDQpEYXRlOiBGcmksIDE1IEp1biAyMDEyIDE3OjM3OjUwIA0KVG86
IElFVEYgQ2hhaXI8Y2hhaXJAaWV0Zi5vcmc+DQpDYzogSUVURjxpZXRmQGlldGYub3JnPg0KU3Vi
amVjdDogUmU6IEZ1dHVyZSBIYW5kbGluZyBvZiBCbHVlIFNoZWV0cw0KDQpEbyB3ZSBoYXZlIGd1
aWRlbGluZXMgYXMgdG8gd2hhdCBpcyBhbiAib3JnYW5pemF0aW9uIGFmZmlsaWF0aW9uIj8NCg0K
T24gSnVuIDE0LCAyMDEyLCBhdCA1OjI2IFBNLCBJRVRGIENoYWlyIHdyb3RlOg0KDQo+IFR3byB0
aGluZ3MgaGF2ZSBvY2N1cnJlZCBzaW5jZSB0aGUgbWVzc2FnZSBiZWxvdyBhcyBzZW50IHRvIHRo
ZSBJRVRGIG1haWwgbGlzdC4gIEZpcnN0LCB3ZSBnb3QgYSBsYXd5ZXIgaW4gRXVyb3BlIHRvIGRv
IHNvbWUgaW52ZXN0aWdhdGlvbiwgYW5kIHRoZSBpbmNsdXNpb24gb2YgdGhlIGVtYWlsIGFkZHJl
c3Mgb24gdGhlIGJsdWUgc2hlZXQgd2lsbCBsZWFkIHRvIHRyb3VibGUgd2l0aCB0aGUgRXVyb3Bl
YW4gcHJpdmFjeSBsYXdzLiAgU2Vjb25kLCBUZWQgSGFyZGllIHN1Z2dlc3RlZCB0aGF0IHdlIGNv
dWxkIHJlcXVpcmUgYSBwYXNzd29yZCB0byBhY2Nlc3MgdGhlIHNjYW5uZWQgYmx1ZSBzaGVldC4N
Cj4gDQo+IEJhc2VkIG9uIHRoZSBFdXJvcGVhbiBwcml2YWN5IGxhdyBpbmZvcm1hdGlvbiwgdGhl
IHVzZSBvZiBlbWFpbCB3aWxsIHJlc3VsdCBpbiBhIG1ham9yIGJ1cmRlbi4gIElmIHRoZSBlbWFp
bCBhZGRyZXNzIGlzIHVzZWQsIHRoZW4gd2UgbXVzdCBwcm92aWRlIGEgd2F5IGZvciBwZW9wbGUg
dG8gYXNrIGZvciB0aGVpciBlbWFpbCBhZGRyZXNzIHRvIGJlIHJlbW92ZSBhdCBhbnkgdGltZSBp
biB0aGUgZnV0dXJlLCBldmVuIGlmIHdlIGdvdCBwcmlvciBhcHByb3ZhbCB0byBpbmNsdWRlIGl0
LiAgVGhlcmVmb3JlLCBJIHN1Z2dlc3QgdGhhdCB3ZSBjb2xsZWN0IG9yZ2FuaXphdGlvbiBhZmZp
bGlhdGlvbiB0byBkaXNjcmltaW5hdGUgYmV0d2VlbiBtdWx0aXBsZSBwZW9wbGUgd2l0aCB0aGUg
c2FtZSBuYW1lIGluc3RlYWQgb2YgZW1haWwgYWRkcmVzcy4NCj4gDQo+IEJhc2VkIG9uIFRlZCdz
IHN1Z2dlc3Rpb24sIEkgY2hlY2tlZCB3aXRoIHRoZSBTZWNyZXRhcmlhdCBhYm91dCB1c2luZyBh
IGRhdGF0cmFja2VyIGxvZ2luIHRvIGRvd25sb2FkIHRoZSBzY2FubmVkIGJsdWUgc2hlZXQuICBU
aGlzIGlzIGZhaXJseSBlYXN5IHRvIGRvLCBvbmNlIHRoZSBjb21tdW5pdHkgdHJhY2tpbmcgdG9v
bHMgYXJlIGRlcGxveWVkLiAgSG93ZXZlciwgd2l0aCB0aGUgcmVtb3ZhbCBvZiB0aGUgZW1haWwg
YWRkcmVzc2VzIGZyb20gdGhlIGJsdWUgc2hlZXRzLCBpdCBpcyB1bmNsZWFyIHRoYXQgdGhlcmUg
aXMgYW55IGZ1cnRoZXIgbmVlZCBmb3IgcGFzc3dvcmQgcHJvdGVjdGlvbiBvZiB0aGVzZSBpbWFn
ZXMuICBUaGVyZWZvcmUsIEkgc3VnZ2VzdCB0aGF0IHdlIHByb2NlZWQgd2l0aG91dCBwYXNzd29y
ZCBwcm90ZWN0aW9uIGZvciB0aGUgYmx1ZSBzaGVldCBpbWFnZXMuDQo+IA0KPiBIZXJlIGlzIGEg
c3VtbWFyeSBvZiB0aGUgc3VnZ2VzdGVkIHdheSBmb3J3YXJkOg0KPiANCj4gLSBTdG9wIGNvbGxl
Y3RpbmcgZW1haWwgYWRkcmVzc2VzIG9uIGJsdWUgc2hlZXRzOw0KPiANCj4gLSBDb2xsZWN0IG9y
Z2FuaXphdGlvbiBhZmZpbGlhdGlvbiB0byBkaXNjcmltaW5hdGUgYmV0d2VlbiBtdWx0aXBsZSBw
ZW9wbGUgd2l0aCB0aGUgc2FtZSBuYW1lOw0KPiANCj4gLSBTY2FuIHRoZSBibHVlIHNoZWV0cyBh
bmQgaW5jbHVkZSB0aGUgaW1hZ2VzIGluIHRoZSBwcm9jZWVkaW5ncyBmb3IgdGhlIFdHIHNlc3Np
b247DQo+IA0KPiAtIEFkZCBpbmRpY2F0aW9uIHRvIHRvcCBvZiB0aGUgYmx1ZSBzaGVldCBzbyBw
ZW9wbGUga25vdyBpdCB3aWxsIGJlIHBhcnQgb2YgdGhlIHByb2NlZWRpbmdzOyBhbmQNCj4gDQo+
IC0gRGlzY2FyZCBwYXBlciBibHVlIHNoZWV0cyBhZnRlciBzY2FubmluZy4NCj4gDQo+IFJ1c3MN
Cj4gDQo+IA0KPiBPbiBNYXkgNiwgMjAxMiwgYXQgMTI6NDYgUE0sIElFVEYgQ2hhaXIgd3JvdGU6
DQo+IA0KPj4gV2UgaGF2ZSBoZWFyZCBmcm9tIG1hbnkgY29tbXVuaXR5IHBhcnRpY2lwYW50cywg
YW5kIGNvbnNlbnN1cyBpcyBxdWl0ZSByb3VnaCBvbiB0aGlzIHRvcGljLiAgVGhlIElFU0cgZGlz
Y3Vzc2VkIHRoaXMgdGhyZWFkIGFuZCByZWFjaGVkIHR3byBjb25jbHVzaW9uczoNCj4+IA0KPj4g
KDEpIFJvdWdoIGNvbnNlbnN1czogYW4gb3BlbiBhbmQgdHJhbnNwYXJlbnQgc3RhbmRhcmRzIHBy
b2Nlc3MgaXMgbW9yZSBpbXBvcnRhbnQgdG8gdGhlIElFVEYgdGhhbiBwcml2YWN5IG9mIGJsdWUg
c2hlZXQgaW5mb3JtYXRpb24uDQo+PiANCj4+ICgyKSBSb3VnaCBjb25zZW5zdXM6IGluY2x1c2lv
biBvZiBlbWFpbCBhZGRyZXNzZXMgaXMgYSBnb29kIHdheSB0byBkaXN0aW5ndWlzaCBwYXJ0aWNp
cGFudHMgd2l0aCB0aGUgc2FtZSBvciBzaW1pbGFyIG5hbWVzLg0KPj4gDQo+PiANCj4+IEJhc2Vk
IG9uIHRoZXNlIGNvbmNsdXNpb25zLCB0aGUgcGxhbiBpcyB0byBoYW5kbGUgYmx1ZSBzaGVldHMg
YXMgZm9sbG93czoNCj4+IA0KPj4gLSBDb250aW51ZSB0byBjb2xsZWN0IGVtYWlsIGFkZHJlc3Nl
cyBvbiBibHVlIHNoZWV0czsNCj4+IA0KPj4gLSBTY2FuIHRoZSBibHVlIHNoZWV0IGFuZCBpbmNs
dWRlIHRoZSBpbWFnZSBpbiB0aGUgcHJvY2VlZGluZ3MgZm9yIHRoZSBXRyBzZXNzaW9uOw0KPj4g
DQo+PiAtIEFkZCBpbmRpY2F0aW9uIHRvIHRvcCBvZiB0aGUgYmx1ZSBzaGVldCBzbyBwZW9wbGUg
a25vdyBpdCB3aWxsIGJlIHBhcnQgb2YgdGhlIHByb2NlZWRpbmdzOyBhbmQNCj4+IA0KPj4gLSBE
aXNjYXJkIHBhcGVyIGJsdWUgc2hlZXRzIGFmdGVyIHNjYW5uaW5nLg0KPj4gDQo+PiANCj4+IE9u
IGJlaGFsZiBvZiB0aGUgSUVTRywNCj4+IFJ1c3MNCj4+IA0KPiANCg0K


From johnl@iecc.com  Fri Jun 15 14:44:16 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7564F11E80DF for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 rBclForlk0j6 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 14:44:15 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9C12811E80CE for <ietf@ietf.org>; Fri, 15 Jun 2012 14:44:15 -0700 (PDT)
Received: (qmail 10211 invoked from network); 15 Jun 2012 21:44:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=27e2.4fdbacaf.k1206; bh=BROG70rRLQDkRYYuOwlRlh4vBVXnJBvdyMvsfQBq7js=; b=mTaNZkMOlSJUH6gKqNjgcwWLe2q+YGLK8Aw1UfjTcrJbcKTzHPDiw6OCxu7gGvk+wIyD3zCJ1oCG0/dQqpOIPhL8PRnJBBxUIU+FavUIMOPF8PKC29GYPSNTpwWHkq5HNBiuGjBmmaD1cFsMd0061BNTt8IZlFEhbuRbu2yOuFQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 15 Jun 2012 21:43:52 -0000
Date: 15 Jun 2012 17:44:14 -0400
Message-ID: <alpine.BSF.2.00.1206151743480.97707@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "John C Klensin" <john-ietf@jck.com>
Subject: Re: New Non-WG Mailing List: IETF-822
In-Reply-To: <60F818CB9BBA86B709B1E1D2@JcK-HP8200.jck.com>
References: <20120615195854.71801.qmail@joyce.lan> <60F818CB9BBA86B709B1E1D2@JcK-HP8200.jck.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="3825401791-1873958699-1339796654=:97707"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 21:44:16 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1873958699-1339796654=:97707
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

Do we have to rehash all of this stuff AGAIN?

R's,
John

> Huh?   ISO/IEC 646 IRV (another candidate for a FoPSCII
> precursor) replaces the ASCII $, not #, with that universal
> currency symbol.  As for that vertical bar, sufficiently elderly
> practitioners of the art of Character Confusion and Coding (CCS)
> will recall that the ancient Earthling-Based Convention for
> Difficult Information Coding included two peculiar characters: a
> mathematical "not" sign that closely resembled Unicode's "=E2=8C=90"
> (U+2310) and that broken vertical bar.  Those characters spawned
> multiple wars over how they should be mapped into "ASCII" and
> "ISO/IEC 646" with one group arguing for caret and (solid)
> vertical bar, another for tilde and exclamation mark, and a
> third for exclamation mark and [solid] vertical bar.  After much
> bloodshed, 16 and 32 bit character sets were invented so that
> almost everyone could contemplate their cakes while eating them
> and continued dissenters were tortured until they repented.
>
> Those battles were repeated in the development of FoPSCII when
> it was noticed that the 5th character of the Klingon alphabet
> was confusable with both the not-sign, Greek upper case Gamma,
> and  Latin "r".  In addition, the Klingon numeral 8 was easily
> confused with Cyrillic "=D0=96".  This created a variant problem
> that the Intergalactic Consortium for Arbitrary Names and
> Numbers could not dismiss because of some of the advocates had a
> more effective means of persuasion than merely hiring lawyers.
>
> :-(
>
--3825401791-1873958699-1339796654=:97707--

From barryleiba@gmail.com  Fri Jun 15 18:07:17 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 039D211E808C for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 18:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.882
X-Spam-Level: 
X-Spam-Status: No, score=-102.882 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 o3OK38s-YGcI for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 18:07:16 -0700 (PDT)
Received: from mail-qa0-f42.google.com (mail-qa0-f42.google.com [209.85.216.42]) by ietfa.amsl.com (Postfix) with ESMTP id A4D7211E807F for <ietf@ietf.org>; Fri, 15 Jun 2012 18:07:16 -0700 (PDT)
Received: by qafi31 with SMTP id i31so33850qaf.15 for <ietf@ietf.org>; Fri, 15 Jun 2012 18:07:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=M7DCGYOhAOYHQdCogdUFbG/G4FfRA4yqa0xh0KIZbV0=; b=CBiczKyoSwrAp047FO23rbgLPQdYFkhEfnZRM8u48OjcS+aVqBJ3cw6fggWT07BGC0 p7lFO2G4oe0p/8RbbRzLzF+c+998s3rAM3M0U2wIFtlgyr6qRIBYsWMhbYqJH8//Vokk aWvKJ4lH4H+ejyI/Tn5D70LEPMig5u++sgW+FExpGCbVyqLVoBIV9fZ70kXI7azEXV5w T4raz2O7kcpANDU80dgQs0smE4a05YvjMWcbMF3CqokjOA7zHk+nXoC8/KF19CtCkuOG UYIY4hytxT69jRbp4WYD3JXiTzBmPF8jW6TjWFeKXsXTmjkljfBUpUrJBUB63KkJozJi ICGw==
MIME-Version: 1.0
Received: by 10.224.40.2 with SMTP id i2mr14719896qae.62.1339808836108; Fri, 15 Jun 2012 18:07:16 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.229.245.85 with HTTP; Fri, 15 Jun 2012 18:07:16 -0700 (PDT)
Date: Fri, 15 Jun 2012 21:07:16 -0400
X-Google-Sender-Auth: evKKaaB6pJQeK0oCiWkDCVvWVzo
Message-ID: <CALaySJKga+AZTTeBy4kk0LuHJevzSSV2i2_0ng8XyHNGrk6N1A@mail.gmail.com>
Subject: Some mailing lists moved from imc.org to ietf.org
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 01:07:17 -0000

A number of IETF-related mailing lists in the Applications Area have
for some years been hosted by Paul Hoffman at imc.org.  Most of them
belonged to working groups at one time, and have remained active since
the working groups closed, holding discussions of related activities
and technology.  Because of that history and current activity, it
makes sense to keep the lists, and it also makes sense to re-host them
at ietf.org.  I discussed this with Paul, and he was also interested
in making the switch.

The Secretariat has, therefore, moved the lists to ietf.org.  By
"moved", I mean that the subscribers to the old lists were subscribed
to the new ones, *and* the archives were copied over as well -- many
thanks to Steve Young for doing his best to clean out the spam and
only archive the real stuff.

The new lists have the same purpose as the old ones, and Paul has set
things up to point people to the new ones when they try to access the
old.  This should look, to all the users, like a pretty seamless
transition, requiring only an update of any email filters to use the
new list designations (see below).

In addition to thanking Steve for handling the move, I thank Paul
Hoffman for having set these up quickly when they were needed, and for
hosting them for many years.

The lists that were moved are these:

imapext@ietf.org, List-ID: <imapext.ietf.org>  (was ietf-imapext@imc.org)
  Discussion of IMAP extensions

ietf-822@ietf.org, List-ID: <ietf-822.ietf.org>  (was ietf-822@imc.org)
  Discussion of issues related to Internet Message Format [RFC 822,
  RFC 2822, RFC 5322]

ietf-smtp@ietf.org, List-ID: <ietf-smtp.ietf.org>  (was ietf-smtp@imc.org)
  Discussion of issues related to Simple Mail Transfer Protocol
  (SMTP) [RFC 821, RFC 2821, RFC 5321]

pop3ext@ietf.org, List-ID: <pop3ext.ietf.org>  (was ietf-pop3ext@imc.org)
  Discussion of extensions and updates to Post Office Protocol (POP3)

xml-mime@ietf.org, List-ID: <xml-mime.ietf.org>  (was ietf-xml-mime@imc.org)
  Discussion of XML media types and issues relating to their use in MIME.

openpgp@ietf.org, List-ID: <openpgp.ietf.org>  (was ietf-openpgp@imc.org)
  Ongoing discussion of OpenPGP issues.

usefor@ietf.org, List-ID: <usefor.ietf.org>  (was ietf-usefor@imc.org)
  Ongoing discussion of usefor issues.

The mailman page for any list is at
https://www.ietf.org/mailman/listinfo/LISTNAME

---
Barry, Applications AD

From mohta@necom830.hpcl.titech.ac.jp  Fri Jun 15 18:56:39 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83B1311E8083 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 18:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.282
X-Spam-Level: 
X-Spam-Status: No, score=0.282 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 6IHeTneI-RWK for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 18:56:39 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id BEA0421F8449 for <ietf@ietf.org>; Fri, 15 Jun 2012 18:56:38 -0700 (PDT)
Received: (qmail 88906 invoked from network); 16 Jun 2012 02:01:01 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 16 Jun 2012 02:01:01 -0000
Message-ID: <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp>
Date: Sat, 16 Jun 2012 10:54:34 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu>
In-Reply-To: <4FDB6843.6090107@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 01:56:39 -0000

Joe Touch wrote:

>> After thinking more about the draft, I think it is
>> purposelessly hostile against innocent operators and
>> end users who are suffering between people filtering
>> ICMP and people insisting on PMTUD.
>>
>> Today, innocent operators often clear DF bit and
>> end users are happy with it, because, today, probability
>> of accidental ID match is small enough.

> That is not an innocent action.

It is a fair action by innocent providers.

> It defeats PMTUD, which is a draft
> standard.

So, the proper thing for IETF to do is to obsolete RFC1191.

There is no reason for IETF to ignore operational feedback
from the real world that RFC1191 is a bad idea.

> It also violates RFC 791 and 1121.

To stop the fair violation, obsolete RFC1191.

> This document only restates existing requirements in this regard,

   >>   Originating sources MAY set the IPv4 ID field of atomic datagrams
   to any value.

is not a restatement of existing requirements.

> stating them in 2119-language. It does not create any new requirement.
> Operates that clear the DF bit are already in violation of three
> standards-track RFCs.

That many operators are actively violating the standard track
RFCs means the standard track RFCs are defective.

>> Then, end users may actively act against PMTUD and/or IETF.
> 
> I disagree; if they wanted to do so, they already would have acted since
> the requirements already exist, albeit in pre-RFC2199 language.

As your draft actively tries to change the current situation
that:

>> Today, innocent operators often clear DF bit and
>> end users are happy with it, because, today, probability
>> of accidental ID match is small enough.

it is not surprising if end users think you are guilty.

						Masataka Ohta

From adrian@olddog.co.uk  Fri Jun 15 18:59:38 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64B0221F854B for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 18:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[AWL=0.160,  BAYES_00=-2.599]
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 q2gWMT-tKFSZ for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 18:59:37 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC2421F8549 for <ietf@ietf.org>; Fri, 15 Jun 2012 18:59:37 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q5G1xWBk024211 for <ietf@ietf.org>; Sat, 16 Jun 2012 02:59:32 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q5G1xVwc024201 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 16 Jun 2012 02:59:32 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'IETF'" <ietf@ietf.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com>	<360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com>	<64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu>	<BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org>	<D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org>	<F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com> <616737881-1339796556-cardhu_decombobulator_blackberry.rim.net-133583724-@b2.c2.bise6.blackberry>
In-Reply-To: <616737881-1339796556-cardhu_decombobulator_blackberry.rim.net-133583724-@b2.c2.bise6.blackberry>
Subject: RE: Future Handling of Blue Sheets
Date: Sat, 16 Jun 2012 02:59:29 +0100
Message-ID: <0c1e01cd4b63$ab0f6210$012e2630$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHY9tDIdSVp+arZNGQzvi7tw/09QgLe/LnYAn76fjYDMzbM3QJTH6vMAumV0ikCKMeXEpZlI+jQ
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 01:59:38 -0000

I've always found that term in that context highly presumptuous and slightly
offensive.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> edj.etc@gmail.com
> Sent: 15 June 2012 22:43
> To: Eric Burger; ietf-bounces@ietf.org; IETF Chair
> Cc: IETF
> Subject: Re: Future Handling of Blue Sheets
> 
> I presume it is the same data that people input into the "Organization" field
when
> they register for the meeting.
> 
> Regards,
> 
> Ed  J.
> 
> -----Original Message-----
> From: Eric Burger <eburger-l@standardstrack.com>
> Sender: ietf-bounces@ietf.org
> Date: Fri, 15 Jun 2012 17:37:50
> To: IETF Chair<chair@ietf.org>
> Cc: IETF<ietf@ietf.org>
> Subject: Re: Future Handling of Blue Sheets
> 
> Do we have guidelines as to what is an "organization affiliation"?
> 
> On Jun 14, 2012, at 5:26 PM, IETF Chair wrote:
> 
> > Two things have occurred since the message below as sent to the IETF mail
list.
> First, we got a lawyer in Europe to do some investigation, and the inclusion
of the
> email address on the blue sheet will lead to trouble with the European privacy
> laws.  Second, Ted Hardie suggested that we could require a password to access
> the scanned blue sheet.
> >
> > Based on the European privacy law information, the use of email will result
in a
> major burden.  If the email address is used, then we must provide a way for
> people to ask for their email address to be remove at any time in the future,
> even if we got prior approval to include it.  Therefore, I suggest that we
collect
> organization affiliation to discriminate between multiple people with the same
> name instead of email address.
> >
> > Based on Ted's suggestion, I checked with the Secretariat about using a
> datatracker login to download the scanned blue sheet.  This is fairly easy to
do,
> once the community tracking tools are deployed.  However, with the removal of
> the email addresses from the blue sheets, it is unclear that there is any
further
> need for password protection of these images.  Therefore, I suggest that we
> proceed without password protection for the blue sheet images.
> >
> > Here is a summary of the suggested way forward:
> >
> > - Stop collecting email addresses on blue sheets;
> >
> > - Collect organization affiliation to discriminate between multiple people
with
> the same name;
> >
> > - Scan the blue sheets and include the images in the proceedings for the WG
> session;
> >
> > - Add indication to top of the blue sheet so people know it will be part of
the
> proceedings; and
> >
> > - Discard paper blue sheets after scanning.
> >
> > Russ
> >
> >
> > On May 6, 2012, at 12:46 PM, IETF Chair wrote:
> >
> >> We have heard from many community participants, and consensus is quite
> rough on this topic.  The IESG discussed this thread and reached two
conclusions:
> >>
> >> (1) Rough consensus: an open and transparent standards process is more
> important to the IETF than privacy of blue sheet information.
> >>
> >> (2) Rough consensus: inclusion of email addresses is a good way to
distinguish
> participants with the same or similar names.
> >>
> >>
> >> Based on these conclusions, the plan is to handle blue sheets as follows:
> >>
> >> - Continue to collect email addresses on blue sheets;
> >>
> >> - Scan the blue sheet and include the image in the proceedings for the WG
> session;
> >>
> >> - Add indication to top of the blue sheet so people know it will be part of
the
> proceedings; and
> >>
> >> - Discard paper blue sheets after scanning.
> >>
> >>
> >> On behalf of the IESG,
> >> Russ
> >>
> >



From touch@isi.edu  Fri Jun 15 19:10:03 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D91811E8083 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 19:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 e84FMwfxdxLb for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 19:10:02 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 236FA11E8072 for <ietf@ietf.org>; Fri, 15 Jun 2012 19:10:02 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q5G29EOh001475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Jun 2012 19:09:14 -0700 (PDT)
Message-ID: <4FDBEACA.4030701@isi.edu>
Date: Fri, 15 Jun 2012 19:09:14 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120604 Thunderbird/13.0
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu> <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 02:10:03 -0000

Masataka,

On 6/15/2012 6:54 PM, Masataka Ohta wrote:
> Joe Touch wrote:
> 
>>> After thinking more about the draft, I think it is
>>> purposelessly hostile against innocent operators and
>>> end users who are suffering between people filtering
>>> ICMP and people insisting on PMTUD.
>>>
>>> Today, innocent operators often clear DF bit and
>>> end users are happy with it, because, today, probability
>>> of accidental ID match is small enough.
> 
>> That is not an innocent action.
> 
> It is a fair action by innocent providers.

It is a violation of standards. They may do it innocently, but it's
still a violation. This document doesn't make it more of a violation; it
just explains the existing violation.

>> It defeats PMTUD, which is a draft
>> standard.
> 
> So, the proper thing for IETF to do is to obsolete RFC1191.
>
> There is no reason for IETF to ignore operational feedback
> from the real world that RFC1191 is a bad idea.

That is not the focus of this document. Again, we don't create a new
requirement.  If you feel there is consensus to raise this change, that
would be a separate issue.

>> It also violates RFC 791 and 1121.
> 
> To stop the fair violation, obsolete RFC1191.

The steps needed to allow DF clearing need to be determined; I don't
know what they are, but that's outside the scope of this doc.

>> This document only restates existing requirements in this regard,
> 
>     >>   Originating sources MAY set the IPv4 ID field of atomic datagrams
>     to any value.
> 
> is not a restatement of existing requirements.

I will be more clear:

- regarding clearing the DF bit, this document only restates existing
requirements

Yes, there are other, new requirements that this document introduces.
But the rules about not clearing the DF bit are not new.

>> stating them in 2119-language. It does not create any new requirement.
>> Operates that clear the DF bit are already in violation of three
>> standards-track RFCs.
> 
> That many operators are actively violating the standard track
> RFCs means the standard track RFCs are defective.

Or that they have defective equipment, or that their logic in deciding
to run their equipment this way is defective. Just because "everyone
does it" doesn't make it correct or warrant changing the specs (see RFC
2525 for treatment of TCP implementation errors, e.g.).

>>> Then, end users may actively act against PMTUD and/or IETF.
>>
>> I disagree; if they wanted to do so, they already would have acted since
>> the requirements already exist, albeit in pre-RFC2199 language.
> 
> As your draft actively tries to change the current situation
> that:
> 
>>> Today, innocent operators often clear DF bit and
>>> end users are happy with it, because, today, probability
>>> of accidental ID match is small enough.
> 
> it is not surprising if end users think you are guilty.

Again, this document doesn't change the current situation. Operators who
clear the DF bit are not innocent - they need to override a default
setting. They are active participants. They ARE guilty of violating
existing standards.

You seem to think that this is OK because they have good reasons. That
may make their actions acceptable, but it will not make them compliant
*until* someone updates the standards that require the DF not be
cleared. This is not that document.

Joe

From joelja@bogus.com  Fri Jun 15 20:50:27 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9179011E808C; Fri, 15 Jun 2012 20:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 BqxYUQ0oPolB; Fri, 15 Jun 2012 20:50:27 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A87EB11E8089; Fri, 15 Jun 2012 20:50:26 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q5G3oOTf058237 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 16 Jun 2012 03:50:24 GMT (envelope-from joelja@bogus.com)
Message-ID: <4FDC0280.8060505@bogus.com>
Date: Fri, 15 Jun 2012 20:50:24 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: edj.etc@gmail.com
Subject: Re: Future Handling of Blue Sheets
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org> <F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com> <616737881-1339796556-cardhu_decombobulator_blackberry.rim.net-133583724-@b2.c2.bise6.blackberry>
In-Reply-To: <616737881-1339796556-cardhu_decombobulator_blackberry.rim.net-133583724-@b2.c2.bise6.blackberry>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 16 Jun 2012 03:50:25 +0000 (UTC)
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, ietf-bounces@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 03:50:27 -0000

On 6/15/12 14:42 , edj.etc@gmail.com wrote:
> I presume it is the same data that people input into the "Organization" field when they register for the meeting.

I do change mine based on what capacity I'm attending a particular
meeting in. That goes for email address on existing blue sheets as well...

The nice people who send me a check every two weeks don't generally fund
my attendance.

> Regards,
> 
> Ed  J.
> 
> -----Original Message-----
> From: Eric Burger <eburger-l@standardstrack.com>
> Sender: ietf-bounces@ietf.org
> Date: Fri, 15 Jun 2012 17:37:50 
> To: IETF Chair<chair@ietf.org>
> Cc: IETF<ietf@ietf.org>
> Subject: Re: Future Handling of Blue Sheets
> 
> Do we have guidelines as to what is an "organization affiliation"?
> 
> On Jun 14, 2012, at 5:26 PM, IETF Chair wrote:
> 
>> Two things have occurred since the message below as sent to the IETF mail list.  First, we got a lawyer in Europe to do some investigation, and the inclusion of the email address on the blue sheet will lead to trouble with the European privacy laws.  Second, Ted Hardie suggested that we could require a password to access the scanned blue sheet.
>>
>> Based on the European privacy law information, the use of email will result in a major burden.  If the email address is used, then we must provide a way for people to ask for their email address to be remove at any time in the future, even if we got prior approval to include it.  Therefore, I suggest that we collect organization affiliation to discriminate between multiple people with the same name instead of email address.
>>
>> Based on Ted's suggestion, I checked with the Secretariat about using a datatracker login to download the scanned blue sheet.  This is fairly easy to do, once the community tracking tools are deployed.  However, with the removal of the email addresses from the blue sheets, it is unclear that there is any further need for password protection of these images.  Therefore, I suggest that we proceed without password protection for the blue sheet images.
>>
>> Here is a summary of the suggested way forward:
>>
>> - Stop collecting email addresses on blue sheets;
>>
>> - Collect organization affiliation to discriminate between multiple people with the same name;
>>
>> - Scan the blue sheets and include the images in the proceedings for the WG session;
>>
>> - Add indication to top of the blue sheet so people know it will be part of the proceedings; and
>>
>> - Discard paper blue sheets after scanning.
>>
>> Russ
>>
>>
>> On May 6, 2012, at 12:46 PM, IETF Chair wrote:
>>
>>> We have heard from many community participants, and consensus is quite rough on this topic.  The IESG discussed this thread and reached two conclusions:
>>>
>>> (1) Rough consensus: an open and transparent standards process is more important to the IETF than privacy of blue sheet information.
>>>
>>> (2) Rough consensus: inclusion of email addresses is a good way to distinguish participants with the same or similar names.
>>>
>>>
>>> Based on these conclusions, the plan is to handle blue sheets as follows:
>>>
>>> - Continue to collect email addresses on blue sheets;
>>>
>>> - Scan the blue sheet and include the image in the proceedings for the WG session;
>>>
>>> - Add indication to top of the blue sheet so people know it will be part of the proceedings; and
>>>
>>> - Discard paper blue sheets after scanning.
>>>
>>>
>>> On behalf of the IESG,
>>> Russ
>>>
>>
> 
> 



From mohta@necom830.hpcl.titech.ac.jp  Fri Jun 15 22:55:54 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 636A321F85B1 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 22:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.158
X-Spam-Level: 
X-Spam-Status: No, score=0.158 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 qxi1s-0i9TYR for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 22:55:53 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 5596B21F85AF for <ietf@ietf.org>; Fri, 15 Jun 2012 22:55:52 -0700 (PDT)
Received: (qmail 90230 invoked from network); 16 Jun 2012 06:00:18 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 16 Jun 2012 06:00:18 -0000
Message-ID: <4FDC1F9C.2060808@necom830.hpcl.titech.ac.jp>
Date: Sat, 16 Jun 2012 14:54:36 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu> <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp> <4FDBEACA.4030701@isi.edu>
In-Reply-To: <4FDBEACA.4030701@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 05:55:54 -0000

Joe Touch wrote:

>>> That is not an innocent action.

>> It is a fair action by innocent providers.

> It is a violation of standards. They may do it innocently, but it's
> still a violation.

You misunderstand standardization processes.

That innocent operators must violate some standard means
the standard must be changed.

Moreover, there already is a change, RFC4821-stype PMTUD.

> This document doesn't make it more of a violation; it
> just explains the existing violation.

There is no point just to explain standards when the real
world recognizes that the standards can not be followed
and must be changed.

>> So, the proper thing for IETF to do is to obsolete RFC1191.
>>
>> There is no reason for IETF to ignore operational feedback
>> from the real world that RFC1191 is a bad idea.
> 
> That is not the focus of this document. Again, we don't create a new
> requirement.

Your draft reduces existing requirements to make RFC1191-style
PMTUD more harmful.

> If you feel there is consensus to raise this change, that
> would be a separate issue.

Do you think there is explicit consensus on your draft that
we should make RFC1191-stype PMTUD more harmful?

>>> It also violates RFC 791 and 1121.
>>
>> To stop the fair violation, obsolete RFC1191.
> 
> The steps needed to allow DF clearing need to be determined; I don't
> know what they are, but that's outside the scope of this doc.

Your draft has too much to do with RFC1191-stype PMTUD and
is narrowly scoped to make RFC1191-stype PMTUD more harmful,
which means it is in scope.

> - regarding clearing the DF bit, this document only restates existing
> requirements
> 
> Yes, there are other, new requirements that this document introduces.
> But the rules about not clearing the DF bit are not new.

The problem is that the real world requires standards must change.

We can obsolete RFC1191. Or, we must permit DF clearing.

So, there is no point to say DF clearing forbidden without
obsoleting RFC1191.

>> That many operators are actively violating the standard track
>> RFCs means the standard track RFCs are defective.
> 
> Or that they have defective equipment,

Yes, they often have equipments with RFC1191-style PMTUD.

> or that their logic in deciding
> to run their equipment this way is defective.

Don't ignore the logic in the real world to filter ICMP,
which requires standard changes.

> Just because "everyone
> does it" doesn't make it correct or warrant changing the specs (see RFC
> 2525 for treatment of TCP implementation errors, e.g.).

That is a completely different example from your draft.

>> it is not surprising if end users think you are guilty.
> 
> Again, this document doesn't change the current situation.

That's not a excuse not to change the current situation.

Worse, your draft will, by loosening a requirement, changes
the current operational situation worse.

> Operators who
> clear the DF bit are not innocent - they need to override a default
> setting. They are active participants. They ARE guilty of violating
> existing standards.

Comments are Requested For by IETF to them, the active participants.

Their comments are that they can't follow the standard, because
*SOMEONE ELSE* filters ICMP. They are not guilty.

Now, it's time for IETF to modify RFCs.

> You seem to think that this is OK because they have good reasons. That
> may make their actions acceptable, but it will not make them compliant
> *until* someone updates the standards that require the DF not be
> cleared. This is not that document.

Once RFC1191 is obsoleted, your draft becomes almost useless
because no one will follow the rate limitation requirement of
your draft.

						Masataka Ohta


From mohta@necom830.hpcl.titech.ac.jp  Fri Jun 15 23:51:54 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECB0421F8522 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 23:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.096
X-Spam-Level: 
X-Spam-Status: No, score=0.096 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 mP2aLKA4UWZH for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 23:51:54 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 15A5A21F851C for <ietf@ietf.org>; Fri, 15 Jun 2012 23:51:53 -0700 (PDT)
Received: (qmail 90586 invoked from network); 16 Jun 2012 06:56:37 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 16 Jun 2012 06:56:37 -0000
Message-ID: <4FDC2CCB.70904@necom830.hpcl.titech.ac.jp>
Date: Sat, 16 Jun 2012 15:50:51 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu> <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp> <4FDBEACA.4030701@isi.edu>
In-Reply-To: <4FDBEACA.4030701@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 06:51:55 -0000

Joe Touch wrote:

> Again, this document doesn't change the current situation. Operators who
> clear the DF bit are not innocent - they need to override a default
> setting. They are active participants. They ARE guilty of violating
> existing standards.

While IETF is not a protocol police and clearing DF is not
considered guilty by operators community, the following
draft:

	draft-generic-v6ops-tunmtu-03.txt

to fragment IPv6 packets by intermediate routers should be
very interesting to you.

						Masataka Ohta

From tjc@ecs.soton.ac.uk  Sat Jun 16 03:53:53 2012
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EF1321F8592; Sat, 16 Jun 2012 03:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 eiZV4rQAiyGc; Sat, 16 Jun 2012 03:53:52 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 3061D21F858F; Sat, 16 Jun 2012 03:53:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q5GAre76020238; Sat, 16 Jun 2012 11:53:40 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q5GAre76020238
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1339844021; bh=npVrjUJ7V4sTK/90/VvBx4ti0hQ=; h=Subject:Mime-Version:From:In-Reply-To:Date:Cc:References:To; b=zx0n3GjsDapTSGgxiNtRzfeHwyJEIFEGN8ETv9T5nSk1mYEzz8uouo27d6krL7RqG wfJURCVjsUwmDps0/TkOV6Tv8x2WOcp8eElct1B4/aQFb1Kv+IXCF8FQ7Wh+engnG2 S5EwMzETTVs6CznBONUCs3Ryif6r2QzM0oiNBSrY=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id o5FBre0544129124Hx ret-id none; Sat, 16 Jun 2012 11:53:40 +0100
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q5GArZRt008462 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 16 Jun 2012 11:53:36 +0100
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <4FDC0280.8060505@bogus.com>
Date: Sat, 16 Jun 2012 11:53:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|71e7e6f840161bab9e911f1161b36a93o5FBre03tjc|ecs.soton.ac.uk|E01DF13C-F351-4F3E-B82E-DBFFDB252500@ecs.soton.ac.uk>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org> <F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com> <616737881-1339796556-cardhu_decombobulator_blackberry.rim.net-133583724-@b2.c2.bise6.blackberry> <4FDC0280.8060505@bogus.com> <E01DF13C-F351-4F3E-B82E-DBFFDB252500@ecs.soton.ac.uk>
To: Joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1278)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o5FBre054412912400; tid=o5FBre0544129124Hx; client=relay,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: q5GAre76020238
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, ietf-bounces@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 10:53:53 -0000

If the purpose is simply differentiation of people with the same names, =
could we not ask people to enter the last four digits of their IETF =
registration number, which would presumably be unique, while being easy =
to remember?  The number could even be on your badge to always be easy =
to look up.

Unless there's some reason to keep registration numbers private?

That would also allow poorly handwritten names to more readily be =
checked/corrected by OCR when the sheets are scanned.

Tim

On 16 Jun 2012, at 04:50, Joel jaeggli wrote:

> On 6/15/12 14:42 , edj.etc@gmail.com wrote:
>> I presume it is the same data that people input into the =
"Organization" field when they register for the meeting.
>=20
> I do change mine based on what capacity I'm attending a particular
> meeting in. That goes for email address on existing blue sheets as =
well...
>=20
> The nice people who send me a check every two weeks don't generally =
fund
> my attendance.
>=20
>> Regards,
>>=20
>> Ed  J.
>>=20
>> -----Original Message-----
>> From: Eric Burger <eburger-l@standardstrack.com>
>> Sender: ietf-bounces@ietf.org
>> Date: Fri, 15 Jun 2012 17:37:50=20
>> To: IETF Chair<chair@ietf.org>
>> Cc: IETF<ietf@ietf.org>
>> Subject: Re: Future Handling of Blue Sheets
>>=20
>> Do we have guidelines as to what is an "organization affiliation"?
>>=20
>> On Jun 14, 2012, at 5:26 PM, IETF Chair wrote:
>>=20
>>> Two things have occurred since the message below as sent to the IETF =
mail list.  First, we got a lawyer in Europe to do some investigation, =
and the inclusion of the email address on the blue sheet will lead to =
trouble with the European privacy laws.  Second, Ted Hardie suggested =
that we could require a password to access the scanned blue sheet.
>>>=20
>>> Based on the European privacy law information, the use of email will =
result in a major burden.  If the email address is used, then we must =
provide a way for people to ask for their email address to be remove at =
any time in the future, even if we got prior approval to include it.  =
Therefore, I suggest that we collect organization affiliation to =
discriminate between multiple people with the same name instead of email =
address.
>>>=20
>>> Based on Ted's suggestion, I checked with the Secretariat about =
using a datatracker login to download the scanned blue sheet.  This is =
fairly easy to do, once the community tracking tools are deployed.  =
However, with the removal of the email addresses from the blue sheets, =
it is unclear that there is any further need for password protection of =
these images.  Therefore, I suggest that we proceed without password =
protection for the blue sheet images.
>>>=20
>>> Here is a summary of the suggested way forward:
>>>=20
>>> - Stop collecting email addresses on blue sheets;
>>>=20
>>> - Collect organization affiliation to discriminate between multiple =
people with the same name;
>>>=20
>>> - Scan the blue sheets and include the images in the proceedings for =
the WG session;
>>>=20
>>> - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and
>>>=20
>>> - Discard paper blue sheets after scanning.
>>>=20
>>> Russ
>>>=20
>>>=20
>>> On May 6, 2012, at 12:46 PM, IETF Chair wrote:
>>>=20
>>>> We have heard from many community participants, and consensus is =
quite rough on this topic.  The IESG discussed this thread and reached =
two conclusions:
>>>>=20
>>>> (1) Rough consensus: an open and transparent standards process is =
more important to the IETF than privacy of blue sheet information.
>>>>=20
>>>> (2) Rough consensus: inclusion of email addresses is a good way to =
distinguish participants with the same or similar names.
>>>>=20
>>>>=20
>>>> Based on these conclusions, the plan is to handle blue sheets as =
follows:
>>>>=20
>>>> - Continue to collect email addresses on blue sheets;
>>>>=20
>>>> - Scan the blue sheet and include the image in the proceedings for =
the WG session;
>>>>=20
>>>> - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and
>>>>=20
>>>> - Discard paper blue sheets after scanning.
>>>>=20
>>>>=20
>>>> On behalf of the IESG,
>>>> Russ
>>>>=20
>>>=20
>>=20
>>=20
>=20
>=20


From touch@isi.edu  Sat Jun 16 10:09:33 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C2E921F852A for <ietf@ietfa.amsl.com>; Sat, 16 Jun 2012 10:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Prq708WTACq5 for <ietf@ietfa.amsl.com>; Sat, 16 Jun 2012 10:09:32 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id D4AA621F8525 for <ietf@ietf.org>; Sat, 16 Jun 2012 10:09:32 -0700 (PDT)
Received: from [192.168.1.95] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q5GH9Aa6020254 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 16 Jun 2012 10:09:17 -0700 (PDT)
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-2022-jp
From: Joe Touch <touch@isi.edu>
In-Reply-To: <4FDC2CCB.70904@necom830.hpcl.titech.ac.jp>
Date: Sat, 16 Jun 2012 10:10:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <603619C7-D09E-4779-8C0A-3EC29C7972A9@isi.edu>
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu> <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp> <4FDBEACA.4030701@isi.edu> <4FDC2CCB.70904@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.1278)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 17:09:33 -0000

On Jun 15, 2012, at 11:50 PM, Masataka Ohta wrote:

> Joe Touch wrote:
>=20
>> Again, this document doesn't change the current situation. Operators =
who
>> clear the DF bit are not innocent - they need to override a default
>> setting. They are active participants. They ARE guilty of violating
>> existing standards.
>=20
> While IETF is not a protocol police and clearing DF is not
> considered guilty by operators community, the following
> draft:
>=20
> 	draft-generic-v6ops-tunmtu-03.txt
>=20
> to fragment IPv6 packets by intermediate routers should be
> very interesting to you.

It is aware of our IPv4-ID doc, and consistent with it.

When the DF is "ignored", the ID field is rewritten - i.e., turning the =
packet from atomic to compliant non-atomic within the tunnel. This is =
consistent with the notion that the ID field must be unique, and that =
atomic packets need not have unique IDs. The rewriting is hidden - =
happens only inside the tunnel, is controlled uniquely by the source, =
and does not need coordination by other sources.

Joe=

From touch@isi.edu  Sat Jun 16 10:18:42 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D192121F84FE for <ietf@ietfa.amsl.com>; Sat, 16 Jun 2012 10:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 R8qH00-YEw8Y for <ietf@ietfa.amsl.com>; Sat, 16 Jun 2012 10:18:42 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5A60921F84EC for <ietf@ietf.org>; Sat, 16 Jun 2012 10:18:42 -0700 (PDT)
Received: from [192.168.1.95] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q5GHHmR1022326 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 16 Jun 2012 10:18:02 -0700 (PDT)
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-2022-jp
From: Joe Touch <touch@isi.edu>
In-Reply-To: <4FDC1F9C.2060808@necom830.hpcl.titech.ac.jp>
Date: Sat, 16 Jun 2012 10:18:39 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <79E3C9F8-3A0F-4BD7-B018-A508D439ED57@isi.edu>
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu> <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp> <4FDBEACA.4030701@isi.edu> <4FDC1F9C.2060808@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.1278)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 17:18:43 -0000

On Jun 15, 2012, at 10:54 PM, Masataka Ohta wrote:

> Joe Touch wrote:
>=20
>>>> That is not an innocent action.
>=20
>>> It is a fair action by innocent providers.
>=20
>> It is a violation of standards. They may do it innocently, but it's
>> still a violation.
>=20
> You misunderstand standardization processes.

Standards remain so until revoked explicitly. Common use does not itself =
revoke a standard - it can also represent either operator error or =
ignorance. That decision has not yet been made for ignoring the DF bit - =
if you want to make that case, you need to take it through the IETF =
process to obsolete the existing standards.

> Moreover, there already is a change, RFC4821-stype PMTUD.

4821 neither updates nor obsoletes 1191. It provides an alternative, =
which is (AFAIK) not widely used either.

>>> So, the proper thing for IETF to do is to obsolete RFC1191.
>>>=20
>>> There is no reason for IETF to ignore operational feedback
>>> from the real world that RFC1191 is a bad idea.
>>=20
>> That is not the focus of this document. Again, we don't create a new
>> requirement.
>=20
> Your draft reduces existing requirements to make RFC1191-style
> PMTUD more harmful.

It does not change existing requirements that the DF bit should not be =
ignored.

>> If you feel there is consensus to raise this change, that
>> would be a separate issue.
>=20
> Do you think there is explicit consensus on your draft that
> we should make RFC1191-stype PMTUD more harmful?

If you have a specific example of how this draft makes 1191 PMTUD more =
harmful, please explain. Merely restating existing requirements on =
preservation of the DF bit does not.

>>>> It also violates RFC 791 and 1121.
>>>=20
>>> To stop the fair violation, obsolete RFC1191.
>>=20
>> The steps needed to allow DF clearing need to be determined; I don't
>> know what they are, but that's outside the scope of this doc.
>=20
> Your draft has too much to do with RFC1191-stype PMTUD and
> is narrowly scoped to make RFC1191-stype PMTUD more harmful,
> which means it is in scope.

The draft neither mentions nor discusses 1191. If you want to update =
existing standards regarding PMTUD, you should write that doc.

>> You seem to think that this is OK because they have good reasons. =
That
>> may make their actions acceptable, but it will not make them =
compliant
>> *until* someone updates the standards that require the DF not be
>> cleared. This is not that document.
>=20
> Once RFC1191 is obsoleted, your draft becomes almost useless
> because no one will follow the rate limitation requirement of
> your draft.

You can make that case in the doc that obsoletes 1191 if you like.=20

This entire issue is out of scope of this document, though.

Joe=

From harald@alvestrand.no  Sat Jun 16 14:43:52 2012
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E295821F85C2 for <ietf@ietfa.amsl.com>; Sat, 16 Jun 2012 14:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 nwmtT2hCRFgI for <ietf@ietfa.amsl.com>; Sat, 16 Jun 2012 14:43:52 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 4CE3221F85B4 for <ietf@ietf.org>; Sat, 16 Jun 2012 14:43:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2FC8E39E07C for <ietf@ietf.org>; Sat, 16 Jun 2012 23:43:50 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UjcoTdwfueG6 for <ietf@ietf.org>; Sat, 16 Jun 2012 23:43:49 +0200 (CEST)
Received: from [192.168.11.193] (c213-89-143-9.bredband.comhem.se [213.89.143.9]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 5805C39E04C for <ietf@ietf.org>; Sat, 16 Jun 2012 23:43:49 +0200 (CEST)
Message-ID: <4FDCFE14.7040200@alvestrand.no>
Date: Sat, 16 Jun 2012 23:43:48 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <4FDBA317.4010001@stpeter.im> <E550DD2D-D21E-44D0-A987-0DE391ABD7DB@vpnc.org>
In-Reply-To: <E550DD2D-D21E-44D0-A987-0DE391ABD7DB@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 21:43:53 -0000

On 06/15/2012 11:27 PM, Paul Hoffman wrote:
> On Jun 15, 2012, at 2:03 PM, Peter Saint-Andre wrote:
>
>> One possible oversight is that this I-D does not describe how the editor
>> will work on the tao-possible-revision.html file (e.g., will only the
>> editor have permissions to work on that, might there be multiple
>> committers, will it be under source control?). Are such details
>> intentionally out of scope?
>
> I would imagine that that would be determined by the IESG when they pick a Tao editor.
>
>
Adhering to the principles of oversight rather than control, I would 
imagine that the IESG would tell the editor to use his best judgment, 
and if they don't like his judgment, they'll replace him.
But then I'm an optimist :-)

ObDraftComment: I support the draft.
ObMinorTweak: I think the URL structure for the dated versions is not 
the best one, because it requires all Tao versions to be in the root 
namespace of the IETF web service.

I would prefer that they be named 
www.ietf.org/tao/archive/YYYY-MM-DD.html, which would also give rise to 
a presumption that one could list all versions by going to 
www.ietf.org/tao/archive.
I'd even support the reference to the archive being in the Tao itself, 
making another layer of indirection possible. But the ability to say 
"the Tao said THIS on Feb 16, 2013" is important.

Yours for more nits in the Last Call process :-)

                   Harald


From ynir@checkpoint.com  Sun Jun 17 00:37:12 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5A6B21F8587; Sun, 17 Jun 2012 00:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.135
X-Spam-Level: 
X-Spam-Status: No, score=-10.135 tagged_above=-999 required=5 tests=[AWL=0.464, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 DTUtG4pEBzLV; Sun, 17 Jun 2012 00:37:12 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7732721F857F; Sun, 17 Jun 2012 00:37:11 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q5H7ax1T020611; Sun, 17 Jun 2012 10:36:59 +0300
X-CheckPoint: {4FDD88E9-0-1B221DC2-4FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 17 Jun 2012 10:36:58 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Sun, 17 Jun 2012 10:36:56 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "'Tim Chown'" <tjc@ecs.soton.ac.uk>, Joel jaeggli <joelja@bogus.com>
Date: Sun, 17 Jun 2012 10:36:56 +0300
Subject: RE: Future Handling of Blue Sheets
Thread-Topic: Future Handling of Blue Sheets
Thread-Index: Ac1LrmMVxyLZSDIlS62PkFUYROl/IgArFYZQ
Message-ID: <006FEB08D9C6444AB014105C9AEB133F017A7C056CA6@il-ex01.ad.checkpoint.com>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org> <F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com> <616737881-1339796556-cardhu_decombobulator_blackberry.rim.net-133583724-@b2.c2.bise6.blackberry> <4FDC0280.8060505@bogus.com> <E01DF13C-F351-4F3E-B82E-DBFFDB252500@ecs.soton.ac.uk> <EMEW3|71e7e6f840161bab9e911f1161b36a93o5FBre03tjc|ecs.soton.ac.uk|E01DF13C-F351-4F3E-B82E-DBFFDB252500@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|71e7e6f840161bab9e911f1161b36a93o5FBre03tjc|ecs.soton.ac.uk|E01DF13C-F351-4F3E-B82E-DBFFDB252500@ecs.soton.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: "ietf-bounces@ietf.org" <ietf-bounces@ietf.org>, IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 07:37:12 -0000

This creates a distinguished identity, so if two "Fei Zhang"s attended in P=
aris (only case I found in the attendee list), this would distinguish which=
 of them attended a particular meeting. It would not, however, tie them to =
an identity on the mailing list, or to the "Fei Zhang" who attends the Vanc=
ouver meeting, so I'm not sure what purpose it serves.

Yoav

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Tim=
 Chown
Sent: 16 June 2012 13:54
To: Joel jaeggli
Cc: IETF Chair; IETF; ietf-bounces@ietf.org
Subject: Re: Future Handling of Blue Sheets

If the purpose is simply differentiation of people with the same names, cou=
ld we not ask people to enter the last four digits of their IETF registrati=
on number, which would presumably be unique, while being easy to remember? =
 The number could even be on your badge to always be easy to look up.

Unless there's some reason to keep registration numbers private?

That would also allow poorly handwritten names to more readily be checked/c=
orrected by OCR when the sheets are scanned.

Tim

On 16 Jun 2012, at 04:50, Joel jaeggli wrote:

> On 6/15/12 14:42 , edj.etc@gmail.com wrote:
>> I presume it is the same data that people input into the "Organization" =
field when they register for the meeting.
>=20
> I do change mine based on what capacity I'm attending a particular=20
> meeting in. That goes for email address on existing blue sheets as well..=
.
>=20
> The nice people who send me a check every two weeks don't generally=20
> fund my attendance.
>=20
>> Regards,
>>=20
>> Ed  J.
>>=20
>> -----Original Message-----
>> From: Eric Burger <eburger-l@standardstrack.com>
>> Sender: ietf-bounces@ietf.org
>> Date: Fri, 15 Jun 2012 17:37:50
>> To: IETF Chair<chair@ietf.org>
>> Cc: IETF<ietf@ietf.org>
>> Subject: Re: Future Handling of Blue Sheets
>>=20
>> Do we have guidelines as to what is an "organization affiliation"?
>>=20
>> On Jun 14, 2012, at 5:26 PM, IETF Chair wrote:
>>=20
>>> Two things have occurred since the message below as sent to the IETF ma=
il list.  First, we got a lawyer in Europe to do some investigation, and th=
e inclusion of the email address on the blue sheet will lead to trouble wit=
h the European privacy laws.  Second, Ted Hardie suggested that we could re=
quire a password to access the scanned blue sheet.
>>>=20
>>> Based on the European privacy law information, the use of email will re=
sult in a major burden.  If the email address is used, then we must provide=
 a way for people to ask for their email address to be remove at any time i=
n the future, even if we got prior approval to include it.  Therefore, I su=
ggest that we collect organization affiliation to discriminate between mult=
iple people with the same name instead of email address.
>>>=20
>>> Based on Ted's suggestion, I checked with the Secretariat about using a=
 datatracker login to download the scanned blue sheet.  This is fairly easy=
 to do, once the community tracking tools are deployed.  However, with the =
removal of the email addresses from the blue sheets, it is unclear that the=
re is any further need for password protection of these images.  Therefore,=
 I suggest that we proceed without password protection for the blue sheet i=
mages.
>>>=20
>>> Here is a summary of the suggested way forward:
>>>=20
>>> - Stop collecting email addresses on blue sheets;
>>>=20
>>> - Collect organization affiliation to discriminate between multiple=20
>>> people with the same name;
>>>=20
>>> - Scan the blue sheets and include the images in the proceedings for=20
>>> the WG session;
>>>=20
>>> - Add indication to top of the blue sheet so people know it will be=20
>>> part of the proceedings; and
>>>=20
>>> - Discard paper blue sheets after scanning.
>>>=20
>>> Russ
>>>=20
>>>=20
>>> On May 6, 2012, at 12:46 PM, IETF Chair wrote:
>>>=20
>>>> We have heard from many community participants, and consensus is quite=
 rough on this topic.  The IESG discussed this thread and reached two concl=
usions:
>>>>=20
>>>> (1) Rough consensus: an open and transparent standards process is more=
 important to the IETF than privacy of blue sheet information.
>>>>=20
>>>> (2) Rough consensus: inclusion of email addresses is a good way to dis=
tinguish participants with the same or similar names.
>>>>=20
>>>>=20
>>>> Based on these conclusions, the plan is to handle blue sheets as follo=
ws:
>>>>=20
>>>> - Continue to collect email addresses on blue sheets;
>>>>=20
>>>> - Scan the blue sheet and include the image in the proceedings for=20
>>>> the WG session;
>>>>=20
>>>> - Add indication to top of the blue sheet so people know it will be=20
>>>> part of the proceedings; and
>>>>=20
>>>> - Discard paper blue sheets after scanning.
>>>>=20
>>>>=20
>>>> On behalf of the IESG,
>>>> Russ
>>>>=20
>>>=20
>>=20
>>=20
>=20
>=20


Scanned by Check Point Total Security Gateway.

From tjc@ecs.soton.ac.uk  Sun Jun 17 05:39:54 2012
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 110C621F8610; Sun, 17 Jun 2012 05:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 JPlSFEBTXkht; Sun, 17 Jun 2012 05:39:53 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id C3B7521F8602; Sun, 17 Jun 2012 05:39:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q5HCdaAo013215; Sun, 17 Jun 2012 13:39:36 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q5HCdaAo013215
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1339936776; bh=9z+/MbbalsC8KuXJLzCHLGJsy9s=; h=Subject:Mime-Version:From:In-Reply-To:Date:Cc:References:To; b=ue2dzfu4W4xvFyn9s7zzwBAHT05qs3/DUqpDWT1gscftkK9U6x2vfHRiGEGRZCReW HA24hs3DyOz2lJCAhiA452WoA7s+KV/VXiapCiHY1KW2v0VBJRXZHJq5YFdZsbnYOj RIRHc1KmQnGBijIYvmwLw8A4MdRIQRnx80qmkTyg=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id o5GDdZ0544132751Fw ret-id none; Sun, 17 Jun 2012 13:39:36 +0100
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q5HCcEKD016567 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 17 Jun 2012 13:38:17 +0100
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <006FEB08D9C6444AB014105C9AEB133F017A7C056CA6@il-ex01.ad.checkpoint.com>
Date: Sun, 17 Jun 2012 13:38:13 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|6b1bc7fb740b086f9e9016821e20f316o5GDdZ03tjc|ecs.soton.ac.uk|4DC36834-60DD-40A8-9C4F-A5BE295D4081@ecs.soton.ac.uk>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org> <F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com> <616737881-1339796556-cardhu_decombobulator_blackberry.rim.net-133583724-@b2.c2.bise6.blackberry> <4FDC0280.8060505@bogus.com> <E01DF13C-F351-4F3E-B82E-DBFFDB252500@ecs.soton.ac.uk> <EMEW3|71e7e6f840161bab9e911f1161b36a93o5FBre03tjc|ecs.soton.ac.uk|E01DF13C-F351-4F3E-B82E-DBFFDB252500@ecs.soton.ac.uk> <006FEB08D9C6444AB014105C9AEB133F017A7C056CA6@il-ex01.ad.checkpoint.com> <4DC36834-60DD-40A8-9C4F-A5BE295D4081@ecs.soton.ac.uk>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1278)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o5GDdZ054413275100; tid=o5GDdZ0544132751Fw; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: q5HCdaAo013215
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "ietf-bounces@ietf.org" <ietf-bounces@ietf.org>, IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 12:39:54 -0000

The registration number links to a registration that includes an email =
address, should that need to be looked up for some reason later.

Holding minimal information for the purpose, and keeping that =
information as non-identifiable to the holder as possible, would be nice =
properties?

Tim

On 17 Jun 2012, at 08:36, Yoav Nir wrote:

> This creates a distinguished identity, so if two "Fei Zhang"s attended =
in Paris (only case I found in the attendee list), this would =
distinguish which of them attended a particular meeting. It would not, =
however, tie them to an identity on the mailing list, or to the "Fei =
Zhang" who attends the Vancouver meeting, so I'm not sure what purpose =
it serves.
>=20
> Yoav
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Tim Chown
> Sent: 16 June 2012 13:54
> To: Joel jaeggli
> Cc: IETF Chair; IETF; ietf-bounces@ietf.org
> Subject: Re: Future Handling of Blue Sheets
>=20
> If the purpose is simply differentiation of people with the same =
names, could we not ask people to enter the last four digits of their =
IETF registration number, which would presumably be unique, while being =
easy to remember?  The number could even be on your badge to always be =
easy to look up.
>=20
> Unless there's some reason to keep registration numbers private?
>=20
> That would also allow poorly handwritten names to more readily be =
checked/corrected by OCR when the sheets are scanned.
>=20
> Tim
>=20
> On 16 Jun 2012, at 04:50, Joel jaeggli wrote:
>=20
>> On 6/15/12 14:42 , edj.etc@gmail.com wrote:
>>> I presume it is the same data that people input into the =
"Organization" field when they register for the meeting.
>>=20
>> I do change mine based on what capacity I'm attending a particular=20
>> meeting in. That goes for email address on existing blue sheets as =
well...
>>=20
>> The nice people who send me a check every two weeks don't generally=20=

>> fund my attendance.
>>=20
>>> Regards,
>>>=20
>>> Ed  J.
>>>=20
>>> -----Original Message-----
>>> From: Eric Burger <eburger-l@standardstrack.com>
>>> Sender: ietf-bounces@ietf.org
>>> Date: Fri, 15 Jun 2012 17:37:50
>>> To: IETF Chair<chair@ietf.org>
>>> Cc: IETF<ietf@ietf.org>
>>> Subject: Re: Future Handling of Blue Sheets
>>>=20
>>> Do we have guidelines as to what is an "organization affiliation"?
>>>=20
>>> On Jun 14, 2012, at 5:26 PM, IETF Chair wrote:
>>>=20
>>>> Two things have occurred since the message below as sent to the =
IETF mail list.  First, we got a lawyer in Europe to do some =
investigation, and the inclusion of the email address on the blue sheet =
will lead to trouble with the European privacy laws.  Second, Ted Hardie =
suggested that we could require a password to access the scanned blue =
sheet.
>>>>=20
>>>> Based on the European privacy law information, the use of email =
will result in a major burden.  If the email address is used, then we =
must provide a way for people to ask for their email address to be =
remove at any time in the future, even if we got prior approval to =
include it.  Therefore, I suggest that we collect organization =
affiliation to discriminate between multiple people with the same name =
instead of email address.
>>>>=20
>>>> Based on Ted's suggestion, I checked with the Secretariat about =
using a datatracker login to download the scanned blue sheet.  This is =
fairly easy to do, once the community tracking tools are deployed.  =
However, with the removal of the email addresses from the blue sheets, =
it is unclear that there is any further need for password protection of =
these images.  Therefore, I suggest that we proceed without password =
protection for the blue sheet images.
>>>>=20
>>>> Here is a summary of the suggested way forward:
>>>>=20
>>>> - Stop collecting email addresses on blue sheets;
>>>>=20
>>>> - Collect organization affiliation to discriminate between multiple=20=

>>>> people with the same name;
>>>>=20
>>>> - Scan the blue sheets and include the images in the proceedings =
for=20
>>>> the WG session;
>>>>=20
>>>> - Add indication to top of the blue sheet so people know it will be=20=

>>>> part of the proceedings; and
>>>>=20
>>>> - Discard paper blue sheets after scanning.
>>>>=20
>>>> Russ
>>>>=20
>>>>=20
>>>> On May 6, 2012, at 12:46 PM, IETF Chair wrote:
>>>>=20
>>>>> We have heard from many community participants, and consensus is =
quite rough on this topic.  The IESG discussed this thread and reached =
two conclusions:
>>>>>=20
>>>>> (1) Rough consensus: an open and transparent standards process is =
more important to the IETF than privacy of blue sheet information.
>>>>>=20
>>>>> (2) Rough consensus: inclusion of email addresses is a good way to =
distinguish participants with the same or similar names.
>>>>>=20
>>>>>=20
>>>>> Based on these conclusions, the plan is to handle blue sheets as =
follows:
>>>>>=20
>>>>> - Continue to collect email addresses on blue sheets;
>>>>>=20
>>>>> - Scan the blue sheet and include the image in the proceedings for=20=

>>>>> the WG session;
>>>>>=20
>>>>> - Add indication to top of the blue sheet so people know it will =
be=20
>>>>> part of the proceedings; and
>>>>>=20
>>>>> - Discard paper blue sheets after scanning.
>>>>>=20
>>>>>=20
>>>>> On behalf of the IESG,
>>>>> Russ
>>>>>=20
>>>>=20
>>>=20
>>>=20
>>=20
>>=20
>=20
>=20
> Scanned by Check Point Total Security Gateway.


From duerst@it.aoyama.ac.jp  Sun Jun 17 05:55:39 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C94D621F85D4 for <ietf@ietfa.amsl.com>; Sun, 17 Jun 2012 05:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.445
X-Spam-Level: 
X-Spam-Status: No, score=-98.445 tagged_above=-999 required=5 tests=[AWL=-1.069, BAYES_40=-0.185, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 1AskZJCZyJG2 for <ietf@ietfa.amsl.com>; Sun, 17 Jun 2012 05:55:39 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id EEEC621F85C2 for <ietf@ietf.org>; Sun, 17 Jun 2012 05:55:38 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5HCtUuj008260 for <ietf@ietf.org>; Sun, 17 Jun 2012 21:55:30 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 2a49_0eb2_b7cba7ae_b87b_11e1_9371_001d096c5782; Sun, 17 Jun 2012 21:55:29 +0900
Received: from [IPv6:::1] ([133.2.210.1]:37951) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D3CE8> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Sun, 17 Jun 2012 21:55:30 +0900
Message-ID: <4FDDD3B7.20507@it.aoyama.ac.jp>
Date: Sun, 17 Jun 2012 21:55:19 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: registries and designated experts
References: <4FCDD499.7060206@it.aoyama.ac.jp><4FCDE96E.5000109@cs.tcd.ie>	<4FD7083A.6080502@it.aoyama.ac.jp><4FD74FFC.3050905@stpeter.im><6.2.5.6.2.20120612073602.09c8cbb8@resistor.net><4FD786DC.4090403@gmail.com><B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com>	<4FD849A9.7000708@gmail.com>	<EDC652A26FB23C4EB6384A4584434A0407B53CA1@307622ANEX5.global.avaya.com> <201206131248.q5DCmSL6028424@cichlid.raleigh.ibm.com>
In-Reply-To: <201206131248.q5DCmSL6028424@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, ietf@ietf.org, SM <sm@resistor.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 12:55:39 -0000

Hello Thomas, others,

On 2012/06/13 21:48, Thomas Narten wrote:
>> Maybe an IESG statement on this respect can help here.
>
> Is the existing text in RFC 5226 not sufficient? It contains extensive
> text about the purpose and role of designated experts, and was revised
> substantially the last time around to try and find a good middle
> ground between being overly prescriptive and giving experts a "blank
> check" to do what they want.
>
> Nothing in the discussion I've seen so far in this thread seems at
> odds with or beyond what is already in RFC 5226 (but I may be biased).

I have quickly looked through RFC 5226, and found Section 5.3
(http://tools.ietf.org/html/rfc5226#section-5.3) which answers in part 
the specific issue that this thread started with, but not in the 
direction that we would need this time.

What that section says is that if the IETF/IESG thinks they need to 
register something in a registry, but the procedures for that registry 
are written too restrictive, then the procedures can be bypassed (but 
they should be fixed as soon as possible).

This time, the situation was somewhat reversed: The expert approved the 
registration, and this fact was then used as a claim that IETF Last Call 
comments on the item registered were no longer appropriate.

I'm with Ned in that I don't think that IETF consensus should be 
involved in any but the most important registrations and most blatant 
registration mistakes, because there are many registrations that don't 
need standardization.

But I really hope that we all agree that registrations can't preempt 
IETF Last Call comments or consensus. I didn't find anything about this 
aspect of registrations and expert reviews in RFC 5226, but maybe I 
didn't look hard enough?

Regards,    Martin.



From abdussalambaryun@gmail.com  Sun Jun 17 06:13:54 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 711EC21F863E; Sun, 17 Jun 2012 06:13:54 -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=[AWL=-0.000, 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 zg8-wFzQLyxG; Sun, 17 Jun 2012 06:13:53 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6A29021F863B; Sun, 17 Jun 2012 06:13:53 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2570486vcq.31 for <multiple recipients>; Sun, 17 Jun 2012 06:13:53 -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 :content-type; bh=LDrnpE9EYTS/rmMZg8ASeNUcnKZSTIUNE+4L4d5F2S4=; b=PiB0f+T1FjU226QELpbLKI/uuDqFxnYbqJXpWoqv+iG+kgpJZY4IEbj7zlHLJCxL16 UU7a8MaaMQMSzvf3c2K6c7nRyJ0UEpXY0+PBU6juQES82WOEK/WO3byop8Q2GgsSGCIC Xq4nf6siiuKn2d+GQqWJ+fgOMDcVQ6d0QOpL1sjewc6Jb8D2Qx5GxfmIimpPccUXfGmY o4zLi/RmOiqLuqsbh8ONbTFGDNts0JrHEkptmud0R7BdxRVDTMp7hCIj7AgJtg5bLxRz b59FE7hG6SxFNTXMnKf8+3wzFLPrk42FuGBByMTGFX7R6Mfar4gHr0Z562otX5CRSw0G 3Tqw==
MIME-Version: 1.0
Received: by 10.52.33.37 with SMTP id o5mr5094681vdi.86.1339938832872; Sun, 17 Jun 2012 06:13:52 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Sun, 17 Jun 2012 06:13:52 -0700 (PDT)
In-Reply-To: <CADnDZ8-pNW6bcCOOBhYCepmLuexHq9EpJq1h4mJQ=qy+7cMyHQ@mail.gmail.com>
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <CADnDZ8-pNW6bcCOOBhYCepmLuexHq9EpJq1h4mJQ=qy+7cMyHQ@mail.gmail.com>
Date: Sun, 17 Jun 2012 14:13:52 +0100
Message-ID: <CADnDZ88Gh2vf4wBqgKySm0SYsTE4SzqD1BHT7jr2oOg37+QG9w@mail.gmail.com>
Subject: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: iesg@ietf.org, ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf307ac16327745804c2aad2d8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 13:13:54 -0000

--20cf307ac16327745804c2aad2d8
Content-Type: text/plain; charset=ISO-8859-1

I suggest to have both webpage and RFC

AB

On Fri, Jun 15, 2012 at 9:29 PM, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Publishing the "Tao of the IETF" as a Web Page'
>  <draft-hoffman-tao-as-web-page-02.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-07-13. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>   Discussion of the "Tao of the IETF" during 2012 made it clear that
>   many people want the document published only as a web page, not as an
>   RFC that needs to be periodically updated.  This document specifies
>   how the Tao will be published as a web page.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

--20cf307ac16327745804c2aad2d8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><br><div>I suggest to have both webpage and RFC<=
/div><span class=3D"HOEnZb"><font color=3D"#888888">
<div>=A0</div>
<div>AB<br><br></div></font></span><div class=3D"HOEnZb"><div class=3D"h5">
<div class=3D"gmail_quote">On Fri, Jun 15, 2012 at 9:29 PM, The IESG <span =
dir=3D"ltr">&lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank=
">iesg-secretary@ietf.org</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote"><br>The IESG has received a request f=
rom an individual submitter to consider<br>the following document:<br>- &#3=
9;Publishing the &quot;Tao of the IETF&quot; as a Web Page&#39;<br>

=A0&lt;draft-hoffman-tao-as-web-page-02.txt&gt; as Informational RFC<br><br=
>The IESG plans to make a decision in the next few weeks, and solicits<br>f=
inal comments on this action. Please send substantive comments to the<br>

<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a> mailin=
g lists by 2012-07-13. Exceptionally, comments may be<br>sent to <a href=3D=
"mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a> instead. In eith=
er case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>Abstract<br><br><br>=A0 Discussion of the &quot;Tao of the IETF&quot; d=
uring 2012 made it clear that<br>=A0 many people want the document publishe=
d only as a web page, not as an<br>=A0 RFC that needs to be periodically up=
dated. =A0This document specifies<br>

=A0 how the Tao will be published as a web page.<br><br><br><br><br>The fil=
e can be obtained via<br><a href=3D"http://datatracker.ietf.org/doc/draft-h=
offman-tao-as-web-page/" target=3D"_blank">http://datatracker.ietf.org/doc/=
draft-hoffman-tao-as-web-page/</a><br>

<br>IESG discussion can be tracked via<br><a href=3D"http://datatracker.iet=
f.org/doc/draft-hoffman-tao-as-web-page/ballot/" target=3D"_blank">http://d=
atatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/ballot/</a><br><br><b=
r>

No IPR declarations have been submitted directly on this I-D.<br><br><br></=
blockquote></div><br>
</div></div></div><br>

--20cf307ac16327745804c2aad2d8--

From stephen.farrell@cs.tcd.ie  Sun Jun 17 06:33:16 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57E8221F8639 for <ietf@ietfa.amsl.com>; Sun, 17 Jun 2012 06:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 okBbICJapTCP for <ietf@ietfa.amsl.com>; Sun, 17 Jun 2012 06:33:15 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 4D74A21F8629 for <ietf@ietf.org>; Sun, 17 Jun 2012 06:33:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id B0225153718; Sun, 17 Jun 2012 14:33:13 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1339939993; bh=Psr3IjjYbBBQS3 GtyCLfrrfKYUbUzvrLbfbwN4r/zVI=; b=fwH3Dfiy/BJGeeq9Z9Vu5v4H9lOx91 37+C9170NVIKbtgMsjPGjBtHd+V0WUJHT3/ac4XlhlnSQ8J5FmQqhlaqa11A5O4/ uYfrh1Asfp6iv//nFAxRrIuylgqesh9AfDhDgga5IoooiywH9ty6KOTGVQrB5g3w 8wHLUND3CC7GskHbFu1bVEgK3bIB5nhuqM4RW9xLPrJ8j0UnAoQbZvNOX/cEovQs UiW4wI3cdCHSfILMzplmYSv85I1VjtkHlb2FdG+QI8PtlQrcc5GfOy3OrLgY4YWn CFSDbx+2Lkwj3TApTt/jv2czayz5Ux33cJvP06cofz4wJgbEDiPhqtuw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id HHSz9z3QpsoQ; Sun, 17 Jun 2012 14:33:13 +0100 (IST)
Received: from [10.87.48.10] (unknown [86.46.29.139]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 8E9E1153717; Sun, 17 Jun 2012 14:33:03 +0100 (IST)
Message-ID: <4FDDDC8E.2060001@cs.tcd.ie>
Date: Sun, 17 Jun 2012 14:33:02 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: registries and designated experts
References: <4FCDD499.7060206@it.aoyama.ac.jp><4FCDE96E.5000109@cs.tcd.ie>	<4FD7083A.6080502@it.aoyama.ac.jp><4FD74FFC.3050905@stpeter.im><6.2.5.6.2.20120612073602.09c8cbb8@resistor.net><4FD786DC.4090403@gmail.com><B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com>	<4FD849A9.7000708@gmail.com>	<EDC652A26FB23C4EB6384A4584434A0407B53CA1@307622ANEX5.global.avaya.com> <201206131248.q5DCmSL6028424@cichlid.raleigh.ibm.com> <4FDDD3B7.20507@it.aoyama.ac.jp>
In-Reply-To: <4FDDD3B7.20507@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Thomas Narten <narten@us.ibm.com>, John C Klensin <john-ietf@jck.com>, ietf@ietf.org, SM <sm@resistor.net>, "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 13:33:16 -0000

Martin,

On 06/17/2012 01:55 PM, "Martin J. Dürst" wrote:
> This time, the situation was somewhat reversed: The expert approved the
> registration, and this fact was then used as a claim that IETF Last Call
> comments on the item registered were no longer appropriate.

I'm sorry, but that's just not accurate. The specific comment (of
yours) was to the effect that two registrations should become
one. I believe its fair to say that that is something one
could have expected to be raised on the uri-review list, given
the comments typically sent to that list, and the comments we
got there on our I-D, and so I brought that up when you (who
often comment on that list), only raised this during IETF LC.

At no point did I claim that IETF LC comments were no longer
appropriate, and indeed I've been responding al all IETF LC
comments on their merits, including this one of yours. But,
yes, I do think that your specific issue (essentially, not doing
one of the registrations) would have been better raised
earlier on uri-review, and as the one asking for the registrations
it does feel like having to jump through the same bureaucratic
hoops a second time.

However, perhaps there is a generic issue in that its not clear
whether one is doing paperwork or getting substantive technical
review when one requests a registration, at least to the
uri-review list. I'm not sure how many other *-review lists
might have the same situation.

That could be clarified I guess. If that list is just to check
the paperwork, then I'd guess that pretty much all technical
comment ought be re-directed elsewhere. If that list is for
substantive technical review, then seeing frequent contributors
to that list first bringing up issues at IETF LC would seem
noteworthy. (I'm not saying such issues ought be ignored, but
they maybe ought be treated as we would the case of a WG
participant making comments on a topic only after WGLC.)

S

From abdussalambaryun@gmail.com  Sun Jun 17 08:06:50 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E18321F851C; Sun, 17 Jun 2012 08:06:50 -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=[AWL=-0.000, 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 LiYI-UBktjWX; Sun, 17 Jun 2012 08:06:49 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1F9A321F851A; Sun, 17 Jun 2012 08:06:49 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2594223vcq.31 for <multiple recipients>; Sun, 17 Jun 2012 08:06:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=I3giR7wI9paIfpQfS+BZ2IcEpO6aOpN1KeJ5gEqmRv0=; b=IW0rer3waEeSg2E0UT+B5tvvOdTXXWJ7G36ZWVvyXpD+XQg+o1E5ZiiiNrizndAHiZ ugmzi5zRzo9zNwUA/ZoA0IE/cP4WJ+UhoCN5FAn5WLiAhkyGRfevTlfzdCve5OBKpJjQ W8KaUgO3gmRnxLng0tBUP265HcX9cAjCxP+V3T5URoS2WrjmH7XebdrJ8NrU+hbQYKgZ WK3BXECAOBlUBwavSXUgXVnIZIS70VUN6oVQPl1xCHhXlkdN/Icai6WuAkfq4Law6RzF MuM0IaN5ID4AsDnpVQUi370BkQDh0ntOnC0dNDC4PIi48bGbZv5JsRFzna8APQhMicXA 4Ulw==
MIME-Version: 1.0
Received: by 10.52.65.145 with SMTP id x17mr5133026vds.117.1339945608484; Sun, 17 Jun 2012 08:06:48 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Sun, 17 Jun 2012 08:06:48 -0700 (PDT)
Date: Sun, 17 Jun 2012 16:06:48 +0100
Message-ID: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com>
Subject: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=bcaec5015d5d0317a704c2ac66aa
Cc: iesg@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 15:06:50 -0000

--bcaec5015d5d0317a704c2ac66aa
Content-Type: text/plain; charset=ISO-8859-1

The abstract mentions 'many people',  because many people may mean 4 to 10
people. The annonced I-D lacks the method of discussion in the community
(discussing such change), the draft mentions the input from any community
individual to be accepted by editor and then approved by IESG, but does not
mention the methodology of discussion between community members nor between
editor and members, also no announcements of such updates mentioned in
draft.

suggest> amend in abstract the word 'many' to the word  'some', or mention
like in the introduction the desire of community.

suggest> to add> to the draft that a discussion group to discuss
inputs/suggestions before the editors undertakes changes. The draft to
specify the discussion ( may be either on-List or during the IETF
meetings). I prefer to mention; the face-to-face IETF meeting discussion in
this procedure issue.

suggest> to add>  the announcement for last call of Tao changes by the
IESG,

suggest> replace in section2> line 7> The editor of the Tao decides which
proposed changes should be submitted to the IESG for the next version of
the Tao.

     replace with> The editor of the Tao decides which proposed changes
should be
                          submitted to the IESG for the next version of the
Tao after
                          the community discussed the changes.

suggest> A time period of updates to be made, and input from the community
to be collected, and editor to submit to IESG. It will be helpful also to


AB
==============

On Fri, Jun 15, 2012 at 9:29 PM, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Publishing the "Tao of the IETF" as a Web Page'
>  <draft-hoffman-tao-as-web-page-02.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-07-13. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>   Discussion of the "Tao of the IETF" during 2012 made it clear that
>   many people want the document published only as a web page, not as an
>   RFC that needs to be periodically updated.  This document specifies
>   how the Tao will be published as a web page.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

--bcaec5015d5d0317a704c2ac66aa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The abstract mentions &#39;many people&#39;, =A0because many people may mea=
n 4 to 10 people. The annonced I-D lacks the method of discussion in the co=
mmunity (discussing such change), the draft mentions the input from any com=
munity individual to be accepted by editor and then approved by IESG, but d=
oes not mention the methodology of discussion between community members nor=
 between editor and members, also no announcements of such updates mentione=
d in draft.<div>
<br></div><div>suggest&gt; amend in abstract the word &#39;many&#39; to the=
 word =A0&#39;some&#39;, or mention like in the introduction the desire of =
community.</div><div><br></div><div>suggest&gt; to add&gt; to the draft tha=
t a discussion group to discuss inputs/suggestions before the editors under=
takes changes. The draft to specify the discussion ( may be either on-List =
or during the IETF meetings). I prefer to mention; the face-to-face IETF me=
eting discussion in this procedure issue.</div>
<div><br></div><div>suggest&gt; to add&gt; =A0the announcement for last cal=
l of Tao changes by the IESG,=A0</div><div><br></div><div>suggest&gt; repla=
ce in section2&gt; line 7&gt; The editor of the Tao decides which proposed =
changes should be submitted to the IESG for the next version of the Tao.</d=
iv>
<div><br></div><div>=A0 =A0 =A0replace with&gt; The editor of the Tao decid=
es which proposed changes should be</div><div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 submitted to the IESG for the next version of the T=
ao after</div><div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 the =
community discussed the changes.=A0</div>
<div><div><br></div><div>suggest&gt; A time period of updates to be made, a=
nd input from the community to be collected, and editor to submit to IESG. =
It will be helpful also to=A0</div><div><br></div><div><br></div><div>AB</d=
iv>
<div><div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br><div class=3D"g=
mail_quote">On Fri, Jun 15, 2012 at 9:29 PM, The IESG <span dir=3D"ltr">&lt=
;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-secretar=
y@ietf.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
The IESG has received a request from an individual submitter to consider<br=
>
the following document:<br>
- &#39;Publishing the &quot;Tao of the IETF&quot; as a Web Page&#39;<br>
 =A0&lt;draft-hoffman-tao-as-web-page-02.txt&gt; as Informational RFC<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2012-07=
-13. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In eith=
er case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
 =A0 Discussion of the &quot;Tao of the IETF&quot; during 2012 made it clea=
r that<br>
 =A0 many people want the document published only as a web page, not as an<=
br>
 =A0 RFC that needs to be periodically updated. =A0This document specifies<=
br>
 =A0 how the Tao will be published as a web page.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/" =
target=3D"_blank">http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-=
page/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/ba=
llot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-hoffman-tao-=
as-web-page/ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
</blockquote></div><br></div></div></div>

--bcaec5015d5d0317a704c2ac66aa--

From barryleiba@gmail.com  Sun Jun 17 08:54:35 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE6A21F8592; Sun, 17 Jun 2012 08:54:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.897
X-Spam-Level: 
X-Spam-Status: No, score=-102.897 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 V15ctJ7BkMXz; Sun, 17 Jun 2012 08:54:35 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7562D21F857D; Sun, 17 Jun 2012 08:54:28 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so2944500qcs.31 for <multiple recipients>; Sun, 17 Jun 2012 08:54:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Agmpf3vi3lS8+7s25hForKE0mVkRiw3m/5TdDUhhJuU=; b=TP7nJiOmV0YP98OhTS+MuIBaDqZoEDasCNMlwc4qdU1ND66jhE1YiqdOwASiPgV7ry s/IZSURx0P4YB0IYEr9LM3NaFlwrxmCB0BzAK+HFxOok7Cx4CB5DsDhjy9zQ6cRoYzTV vsyE93pPLk1NvCpH5Vtibp1QH61gkeyvqorWmwJYmXpgrFMaBWXaxPeLEXSr/2lyJiI/ mTdb4+v/eNGE+H9/pVbkyCXewcT8rGoM/1cNmJ9bE6r07hswpGX8h7ZXOAIBG2pfBPAF s1UNtDSFp0LtwfthQFfGA6gR0OUyIAtoxlFcqnxkh5DN3+nNZOfYnqure1acanOu9D0B /vug==
MIME-Version: 1.0
Received: by 10.229.137.144 with SMTP id w16mr6424221qct.154.1339948467951; Sun, 17 Jun 2012 08:54:27 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.229.245.85 with HTTP; Sun, 17 Jun 2012 08:54:27 -0700 (PDT)
In-Reply-To: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com>
Date: Sun, 17 Jun 2012 11:54:27 -0400
X-Google-Sender-Auth: 8lBd74yV5_cUbMgS1GMI1kUQ3e8
Message-ID: <CALaySJ+t2sYzFgeN_32E8u+Rw5kNPtwrNoxf0M-ZU63GYW_zDw@mail.gmail.com>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
From: Barry Leiba <barryleiba@computer.org>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=00235452f2d073180e04c2ad10d6
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 15:54:35 -0000

--00235452f2d073180e04c2ad10d6
Content-Type: text/plain; charset=ISO-8859-1

> The abstract mentions 'many people',  because many people may mean 4 to 10
> people. The annonced I-D lacks the method of discussion in the community
> (discussing such change), the draft mentions the input from any community
> individual to be accepted by editor and then approved by IESG, but does
not
> mention the methodology of discussion between community members nor
> between editor and members, also no announcements of such updates
> mentioned in draft.

On this, as well as on the rest of the comments in the same message:
The IETF already has a process for discussion, review, and consensus, and
this document neither changes any of it nor, I think, needs to repeat it.

Barry

--00235452f2d073180e04c2ad10d6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<span class=3D"Apple-style-span" style>&gt; The abstract mentions &#39;many=
 people&#39;, =A0because many people may mean 4 to 10</span><div><span clas=
s=3D"Apple-style-span" style>&gt; people. The annonced I-D lacks the method=
 of discussion in the community</span></div>
<div><span class=3D"Apple-style-span" style>&gt; (discussing such change), =
the draft mentions the input from any community</span></div><div><span clas=
s=3D"Apple-style-span" style>&gt; individual to be accepted by editor and t=
hen approved by IESG, but does not</span></div>
<div><span class=3D"Apple-style-span" style>&gt; mention the methodology of=
 discussion between community members nor</span></div><div><span class=3D"A=
pple-style-span" style>&gt; between editor and members, also no announcemen=
ts of such updates</span></div>
<div><span class=3D"Apple-style-span" style>&gt; mentioned in draft.</span>=
</div><div><span class=3D"Apple-style-span" style><br></span></div><div><sp=
an class=3D"Apple-style-span" style>On this, as well as on the rest of the =
comments in the same message:</span></div>
<div><span class=3D"Apple-style-span" style>The IETF already has a process =
for discussion, review, and consensus, and this document neither changes an=
y of it nor, I think, needs to repeat it.</span></div><div><span class=3D"A=
pple-style-span" style><br>
</span></div><div><span class=3D"Apple-style-span" style>Barry</span></div>=
<div><span class=3D"Apple-style-span" style><br></span><span></span></div>

--00235452f2d073180e04c2ad10d6--

From vesely@tana.it  Mon Jun 18 03:31:08 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 228DA21F8539 for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 03:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.375
X-Spam-Level: 
X-Spam-Status: No, score=-4.375 tagged_above=-999 required=5 tests=[AWL=0.344,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 wV7O54yS19vR for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 03:31:07 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id B268521F8525 for <ietf@ietf.org>; Mon, 18 Jun 2012 03:31:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1340015458; bh=4IFyxYTLae7Z1lGhb6t0qRT+5IDNrqe0TasyUolCtls=; l=1764; h=Message-ID:Date:From:MIME-Version:To:Content-Transfer-Encoding; b=ded4mMU1loYAPMjoPnFriP/1IsvxJv0e7B3BZ4Ol6uq/zXOxvYjTlo8qXkrtcVivH XRqTTrjz9R22nOvfkhFoFXWe3ahAExBfgwgs8coH9apRJR6FfmbKQJTj24QljvOGTb vLEEEUti8bS6S1UW4wnkbbp36OsU3k0LGtNnJpkY=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Mon, 18 Jun 2012 12:30:58 +0200 id 00000000005DC045.000000004FDF0362.000040B7
Message-ID: <4FDF0362.3050101@tana.it>
Date: Mon, 18 Jun 2012 12:30:58 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Protocol Definition
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 10:31:08 -0000

On 5 Jan 2012, todd glassey <tglassey@earthlink.net> wrote
> On 1/5/2012 6:48 AM, Dave CROCKER wrote: 
>>  
>> (One can quibble about the difference between algorithm and
>> program. An algorithm is a component of a program.
>  
> The program is the code-based implementation of the alg? 
>  
>> The distinction is relevant here because a protocol is typically
>> a complete mechanism rather than being a component of the
>> mechanisms.
>  
> I.e. "A complete method of doing something"... 

I noticed no disagreement between "method" and "mechanism", at the
time.  In retrospect, those two terms might seem to allude to a
different depth of semantic explanations.  Rereading that thread, I
find that the same ambiguity holds for algorithm descriptions:  one
can give a full description (or coding) of, say, sqrt, without
actually saying that the square of the result will match its argument
up to some rounding error.  The specification does not have to relate
the underlying mathematical abstraction.

Protocol specifications, especially when dealing with policies, do not
have to describe the exact meaning of the relevant tokens.  To do that
would often look like mandating a state or a reaction, neither of
which is needed to ensure interoperability.  In fact, the protocol
just has to ensure that a policy can be transmitted correctly.  Many
would rather leave a policy token underspecified than get involved in
its details.

In that respect, a protocol is not a complete method.  The "upper
layer", where policies and politics are dealt with, seems to be too
fuzzy to be specified.  I think this limitation is consistent with the
etymological meaning of the term, that refers to forms of conduct that
don't betray intentions.  Is that right?

From abdussalambaryun@gmail.com  Mon Jun 18 04:11:52 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2958121F8542; Mon, 18 Jun 2012 04:11:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 dlxb+jU9ASHZ; Mon, 18 Jun 2012 04:11:51 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6265A21F84E7; Mon, 18 Jun 2012 04:11:51 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2925390vcq.31 for <multiple recipients>; Mon, 18 Jun 2012 04:11:50 -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=s+rw670rqaRXVfMSXz68YyD0VTG168gUljAg3UttoYU=; b=QkhWucCMc47HZyO+zrAPnqM9nE030mkFgnLdzLYlH/GjkSq4Al/8eix00JnUtJNdTU Pkwh1Zc+n8ICQvAZ4WoQ9HIILTH86jlJU7wUgUX+3RccaBqiKHjU3Q1UK1jYapDiqcRm 9XE8Slz4WtwWSvo7P0REqVHDiSOt5g1Y+xJbGCR+42IUw2ZypBivHBxLBSISrtEcBePW y+HkMD8+/pLAr+0fO6Qj6rvIbTmpkZ/rxiwY1gyGmtUIITc4FdBrXahrfSjgUi9f2jvO GDd0WZw+ZEdgyGVEi67+jqi3SDxjtgl7MtoA2agWjivmK6AQ2YMedqO7kBmhIG/TLtth H8SA==
MIME-Version: 1.0
Received: by 10.220.157.14 with SMTP id z14mr7574479vcw.73.1340017910786; Mon, 18 Jun 2012 04:11:50 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Mon, 18 Jun 2012 04:11:50 -0700 (PDT)
In-Reply-To: <CALaySJ+t2sYzFgeN_32E8u+Rw5kNPtwrNoxf0M-ZU63GYW_zDw@mail.gmail.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CALaySJ+t2sYzFgeN_32E8u+Rw5kNPtwrNoxf0M-ZU63GYW_zDw@mail.gmail.com>
Date: Mon, 18 Jun 2012 13:11:50 +0200
Message-ID: <CADnDZ88=yj+-zNXpJy92YfBg+8xq8=fumCJ061YGDRjUMS8yoQ@mail.gmail.com>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 11:11:52 -0000

Hi Barry,

I think from your message, you agree that discussion is important in
the decision of updates, which I share. I agree to not repeat any
unnecessary info, but if contradictions appear to procedure, it then
needs a reference or repeat.

The problem is that the I-D does not mention in the
publish-procedure-section-2 *discussion* as an important procedure
factor for submission nor even refers to what you call
process-of-discussion. I think mentioning that editor decides to
submit and accept input is a new thing that is not in the procedure
you refer to. Therefore, to be clear in the I-D it MUST clarify, is
there community consensus with editor decision, OR is their only
decision of editor.

It is clear from the draft if you read it, that the decision *is not*
for the internet-community in two issues: a) editor decision of
accepting a propose change, b) editor decision of change-updates to
submit to IESG. The discussion in the I-D is mentioned as just for
information not as decision making of submission.

Please note that this I-D informs:

1) The Tao will be published at <http://www.ietf.org/tao.html> and
<https://www.ietf.org/tao.html>. The initial content for the Tao web
page will come from the last Internet-Draft that was meant to replace
RFC 4677.

2) RFC4677 is not a formal IETF process document but instead an
informational overview. Therefore, the proposed Tao-webpage is the
same.

Abdussalam
========================================

On 6/17/12, Barry Leiba <barryleiba@computer.org> wrote:
>> The abstract mentions 'many people',  because many people may mean 4 to
>> 10
>> people. The annonced I-D lacks the method of discussion in the community
>> (discussing such change), the draft mentions the input from any community
>> individual to be accepted by editor and then approved by IESG, but does
> not
>> mention the methodology of discussion between community members nor
>> between editor and members, also no announcements of such updates
>> mentioned in draft.
>
> On this, as well as on the rest of the comments in the same message:
> The IETF already has a process for discussion, review, and consensus, and
> this document neither changes any of it nor, I think, needs to repeat it.
>
> Barry
>

From duerst@it.aoyama.ac.jp  Mon Jun 18 04:43:57 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4558321F8507 for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 04:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.555
X-Spam-Level: 
X-Spam-Status: No, score=-99.555 tagged_above=-999 required=5 tests=[AWL=0.235, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 44ddsMyqkPzt for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 04:43:56 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 5332C21F84DD for <ietf@ietf.org>; Mon, 18 Jun 2012 04:43:47 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5IBhXr2007349 for <ietf@ietf.org>; Mon, 18 Jun 2012 20:43:33 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 65e6_0845_d4f990b0_b93a_11e1_bfbd_001d096c5782; Mon, 18 Jun 2012 20:43:32 +0900
Received: from [IPv6:::1] ([133.2.210.1]:52111) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D427B> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 18 Jun 2012 20:43:33 +0900
Message-ID: <4FDF1462.5000506@it.aoyama.ac.jp>
Date: Mon, 18 Jun 2012 20:43:30 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: registries and designated experts
References: <4FCDD499.7060206@it.aoyama.ac.jp><4FCDE96E.5000109@cs.tcd.ie>	<4FD7083A.6080502@it.aoyama.ac.jp><4FD74FFC.3050905@stpeter.im><6.2.5.6.2.20120612073602.09c8cbb8@resistor.net><4FD786DC.4090403@gmail.com><B416CA36462A3CA8C721BDF5@JcK-HP8200.jck.com>	<4FD849A9.7000708@gmail.com>	<EDC652A26FB23C4EB6384A4584434A0407B53CA1@307622ANEX5.global.avaya.com> <201206131248.q5DCmSL6028424@cichlid.raleigh.ibm.com> <4FDDD3B7.20507@it.aoyama.ac.jp> <4FDDDC8E.2060001@cs.tcd.ie>
In-Reply-To: <4FDDDC8E.2060001@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Thomas Narten <narten@us.ibm.com>, John C Klensin <john-ietf@jck.com>, ietf@ietf.org, SM <sm@resistor.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 11:43:57 -0000

Hello Stephen,

On 2012/06/17 22:33, Stephen Farrell wrote:
>
> Martin,
>
> On 06/17/2012 01:55 PM, "Martin J. DÃ¼rst" wrote:
>> This time, the situation was somewhat reversed: The expert approved the
>> registration, and this fact was then used as a claim that IETF Last Call
>> comments on the item registered were no longer appropriate.
>
> I'm sorry, but that's just not accurate. The specific comment (of
> yours) was to the effect that two registrations should become
> one.

[Minor detail: It was about merging two schemes. Merging the 
registrations is a consequence of merging the schemes, but not the core 
issue.]


> I believe its fair to say that that is something one
> could have expected to be raised on the uri-review list, given
> the comments typically sent to that list, and the comments we
> got there on our I-D,

I agree that, as you say below, it would have been better if the issue 
had been raised earlier. But that's the same all over the place; it 
would often have been better if an issue got raised earlier during WG 
discussion rather than later, during WG discussion rather than in WGLC, 
during WGLC rather than in IETF LC, during IETF LC rather than in IESG 
review, and so on. I also agree that nobody would have been surprised if 
such an issue had been brought up on the uri-review list.

But that's different from expecting a specific issue to be brought up in 
a specific place, and only there.

> and so I brought that up when you (who
> often comment on that list), only raised this during IETF LC.

[Minor detail: I don't consider myself a "frequent" contributor to that 
list. But of course frequency is relative.]

First: I mentioned the issue that having two different encodings (base64 
and base16) of the same data was a non-starter *way* earlier. If you 
didn't read that, or don't remember that anymore, it's not my fault.

Second: As explained earlier, my comments were part of an Apps 
Directorate review. When I'm doing an Apps Directorate review, I'm 
setting away time for that explicitly, and try to do a really thorough 
job, with a wide perspective. I can do that because I'm only doing one 
of these every few months. This is quite different from a registration 
mailing list where I'm not the Designated Expert, and can't devote that 
much time to each and every registration that comes by.

The Apps Directorate review is also intended to help the Apps ADs. I'd 
expect that they want to know everything that a reviewer thinks is 
relevant, rather than the reviewer suppressing stuff because he happens 
to be on a registration mailing list on that specific topic and didn't 
have time to look at the draft when it was passing by on that list.


> At no point did I claim that IETF LC comments were no longer
> appropriate, and indeed I've been responding al all IETF LC
> comments on their merits, including this one of yours.

You didn't explicitly claim that IETF LC comments were no longer 
appropriate. And you were indeed quite responsive to many of the issues 
brought up, including many other issues that one could reasonably expect 
to be brought up on the uri-review@ietf.org mailing list (scheme syntax 
issues, escaping/encoding issues,...), and where you didn't say that 
these should have been brought up earlier.

But for that one specific issue, you kept telling me things like 
"second-guessing the designated expert at this stage seems contrary to 
the registration requirements", "process-wise ... your main comment is 
late", "let's not ignore the fact that the uri-review list had sight of 
this at the end of April", and so on.

On my side, this definitely felt very much like "your comment is 
inappropriate at this time" rather than just "would have been great if 
we got this earlier".


> But,
> yes, I do think that your specific issue (essentially, not doing
> one of the registrations) would have been better raised
> earlier on uri-review, and as the one asking for the registrations
> it does feel like having to jump through the same bureaucratic
> hoops a second time.

There are a lot of hoops at the IETF. WG discussion, WG LC, registration 
reviews where applicable, IETF LC, IESG review,.... It would be good if 
we could do with less, but I guess they are all there for a reason.


> However, perhaps there is a generic issue in that its not clear
> whether one is doing paperwork or getting substantive technical
> review when one requests a registration, at least to the
> uri-review list. I'm not sure how many other *-review lists
> might have the same situation.

Quite a few, I guess. I see three main reasons for this:

1) The description of what the Designated Expert should check and what 
not is not clear enough. [For URI/IRI schemes, the IRI WG is working on 
an update to RFC 4395, and yours as well as everybody else's comments 
are highly appreciated.]

2) Many registries have been criticized for being too strict, leading to 
situations where labels are being used without being registered. As a 
result of that, the review has shifted from "is this really absolutely 
needed" in the direction of "make sure this isn't explicitly harmful". 
[This is in particular the case for quite a few registries in the Apps 
Area; it may be quite different in the Security Area, in particular for 
things such as cryptographic algorithms.]

3) The Designated Expert, and even more the other people on these 
mailing lists, are all volunteers, and most have a day job.

While 1) and 2) may eventually be addressed by updating the registry 
guidelines, 3) is difficult to fix.


> That could be clarified I guess.

As said above, the IRI WG is working on an update of RFC 4395, and 
everybody's comments, including yours, are highly appreciated


> If that list is just to check
> the paperwork, then I'd guess that pretty much all technical
> comment ought be re-directed elsewhere.

I'd describe the purpose of the list more as "make sure the basic 
paperwork is okay, make sure this is not overly harmful, and provide a 
place for technical input". There are many people on that list that can 
give technical advice, and quite a bit of it is usually appreciated, so 
I don't see why we should exclude it.


> If that list is for
> substantive technical review, then seeing frequent contributors
> to that list first bringing up issues at IETF LC would seem
> noteworthy. (I'm not saying such issues ought be ignored, but
> they maybe ought be treated as we would the case of a WG
> participant making comments on a topic only after WGLC.)

I strongly disagree here. The purpose of registration is not the same as 
the purpose of IETF standardization. There are many registries that 
contain stuff that "just happened" outside the IETF and would never have 
a chance in the IETF, but nevertheless a label is in use and it is 
better to get it registered than to deny registration. This may be (just 
guessing) different for security stuff such as cryptographic algorithms. 
But it definitely applies to many Apps Area related registries (MIME 
media types, charsets, URI/IRI schemes, and so on).

Also, a mailing list associated with a registry is not the same as a WG 
mailing list. A WG is chartered with creating something new. The main 
motivation for WG participants is to shape that "something new", and 
most aspects of a proposal will be discussed explicitly on the WG list. 
Lurking or occasional participation should indeed not be specially rewarded.

On the other hand, registration mailing lists are essentially "pro bono" 
efforts, both for the Designated Expert(s) as well as for every other 
participant. It would be highly inappropriate to disadvantage these 
volunteer participants in the same way as WG lurkers.

Regards,    Martin.

From mohta@necom830.hpcl.titech.ac.jp  Mon Jun 18 05:10:24 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1078A21F85CD for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 05:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.059
X-Spam-Level: 
X-Spam-Status: No, score=0.059 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 12AmD9YBAswf for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 05:10:23 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id B2AFA21F85C9 for <ietf@ietf.org>; Mon, 18 Jun 2012 05:10:22 -0700 (PDT)
Received: (qmail 15476 invoked from network); 18 Jun 2012 12:15:43 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 18 Jun 2012 12:15:43 -0000
Message-ID: <4FDF1A93.2060304@necom830.hpcl.titech.ac.jp>
Date: Mon, 18 Jun 2012 21:09:55 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu> <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp> <4FDBEACA.4030701@isi.edu> <4FDC2CCB.70904@necom830.hpcl.titech.ac.jp> <603619C7-D09E-4779-8C0A-3EC29C7972A9@isi.edu>
In-Reply-To: <603619C7-D09E-4779-8C0A-3EC29C7972A9@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 12:10:24 -0000

Joe Touch wrote:

>> 	draft-generic-v6ops-tunmtu-03.txt
>>
>> to fragment IPv6 packets by intermediate routers should be
>> very interesting to you.
> 
> It is aware of our IPv4-ID doc, and consistent with it.

What?

> When the DF is "ignored", the ID field is rewritten - i.e.,

If the ID field could be rewritten by intermediate entities,
it is fine for intermediate routers to clear DF.

> The
> rewriting is hidden - happens only inside the tunnel, is
> controlled uniquely by the source, and does not need coordination
> by other sources.

The tunnels are often controlled uniquely only by the destinations.

						Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Mon Jun 18 05:40:21 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C47B21F8610 for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 05:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.034
X-Spam-Level: 
X-Spam-Status: No, score=0.034 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 2T-DDyopNVKI for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 05:40:20 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 54A1F21F860F for <ietf@ietf.org>; Mon, 18 Jun 2012 05:40:20 -0700 (PDT)
Received: (qmail 15712 invoked from network); 18 Jun 2012 12:45:46 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 18 Jun 2012 12:45:46 -0000
Message-ID: <4FDF219D.5020201@necom830.hpcl.titech.ac.jp>
Date: Mon, 18 Jun 2012 21:39:57 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu> <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp> <4FDBEACA.4030701@isi.edu> <4FDC1F9C.2060808@necom830.hpcl.titech.ac.jp> <79E3C9F8-3A0F-4BD7-B018-A508D439ED57@isi.edu>
In-Reply-To: <79E3C9F8-3A0F-4BD7-B018-A508D439ED57@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 12:40:21 -0000

Joe Touch wrote:>

>>>> It is a fair action by innocent providers.
>>
>>> It is a violation of standards. They may do it innocently, but it's
>>> still a violation.
>>
>> You misunderstand standardization processes.
> 
> Standards remain so until revoked explicitly. Common use does
> not itself revoke a standard - it can also represent either
> operator error or ignorance. That decision has not yet been
> made for ignoring the DF bit - if you want to make that case,
> you need to take it through the IETF process to obsolete the
> existing standards.

Urrrr, I'm afraid standards can be ignored a lot more easily.

That operators think it fine to clear DF means IETF must
admit it especially because there is RFC 4821.

>> Your draft reduces existing requirements to make RFC1191-style
>> PMTUD more harmful.
> 
> It does not change existing requirements that the DF bit should
> not be ignored.

So what?

That it does change existing requirements is the problem.

> If you have a specific example of how this draft makes 1191 PMTUD
> more harmful, please explain.

As I already wrote, your draft enables people insisting on 1191
PMUTD can, now, set ID always zero, which is harmful to people,
IN THE REAL WORLD, to clear DF.

> Merely restating existing requirements on preservation of the
> DF bitn

The reality is that you merely loosening existing requirements
to make IPv4 PMTUD more harmful.

>> Your draft has too much to do with RFC1191-stype PMTUD and
>> is narrowly scoped to make RFC1191-stype PMTUD more harmful,
>> which means it is in scope.
> 
> The draft neither mentions nor discusses 1191. If you want to
> update existing standards regarding PMTUD, you should write
> that doc.

That you maliciously do not mention 1191 dose not mean your
draft is strongly tied to 1191.

>> Once RFC1191 is obsoleted, your draft becomes almost useless
>> because no one will follow the rate limitation requirement of
>> your draft.
> 
> You can make that case in the doc that obsoletes 1191 if you like.

My point is that that's what IETF must do.

						Masataka Ohta

PS

While your draft is rather harmful than useless, I'm fine
if the following point of the draft:

   >> Originating sources MAY set the IPv4 ID field of atomic
   datagrams to any value.

is changed to:

   >> Originating sources MUST set the IPv4 ID field of atomic
   datagrams to values as unique as possible.

which is what the current BSD implementations do.

From abdussalambaryun@gmail.com  Sat Jun 16 02:17:16 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8670221F85E5; Sat, 16 Jun 2012 02:17:16 -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=[AWL=-0.000, 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 V5aCFtNeoEKF; Sat, 16 Jun 2012 02:17:16 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB8821F85DF; Sat, 16 Jun 2012 02:17:15 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2261951vcq.31 for <multiple recipients>; Sat, 16 Jun 2012 02:17:15 -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=9LTN6vEQMoY7tpUpgMZHvu/TT1RsMypw8XpNB52/jAY=; b=GsLA9cI0yUzfWMgoWs/H+ZlmtDfnsuuAmboE+chsaHxM964etfhW7zGP3JAzZXcE3d xO904gy6vhgNX/kf/uAd2kohTLo8tYwaP2UClLwr9Tk8/A0hEuGty3HY5+4PX+ieVZDC 7/61DgfES5ExjDqapRhl6jqgExtDvZPQy+G2ZeK+jcVVI7516WVuB/XO02DAEoqRmKaT eG97xlgSFFI/G3FHNnw0TvScSNCzYJhV1QBs8arkobr2ADOxRCSG5YvNfJBtljRUWJ3p QJ4/KYpgsAbNu6eAsf4cUFgmK/A3tON1W1H0ahi6j7UMgrkWjTRbKZaMBNVJxch2p9wq wODw==
MIME-Version: 1.0
Received: by 10.220.157.14 with SMTP id z14mr4426042vcw.73.1339838234870; Sat, 16 Jun 2012 02:17:14 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Sat, 16 Jun 2012 02:17:14 -0700 (PDT)
In-Reply-To: <20120615202915.11032.53296.idtracker@ietfa.amsl.com>
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com>
Date: Sat, 16 Jun 2012 10:17:14 +0100
Message-ID: <CADnDZ8-pNW6bcCOOBhYCepmLuexHq9EpJq1h4mJQ=qy+7cMyHQ@mail.gmail.com>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=f46d043890570bc3ec04c2936620
X-Mailman-Approved-At: Mon, 18 Jun 2012 05:40:39 -0700
Cc: iesg@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 09:17:16 -0000

--f46d043890570bc3ec04c2936620
Content-Type: text/plain; charset=ISO-8859-1

It will be better to have both webpage and RFC

AB

On Fri, Jun 15, 2012 at 9:29 PM, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Publishing the "Tao of the IETF" as a Web Page'
>  <draft-hoffman-tao-as-web-page-02.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-07-13. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>   Discussion of the "Tao of the IETF" during 2012 made it clear that
>   many people want the document published only as a web page, not as an
>   RFC that needs to be periodically updated.  This document specifies
>   how the Tao will be published as a web page.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

--f46d043890570bc3ec04c2936620
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>It will be better to have both webpage and RFC</div>
<div>=A0</div>
<div>AB<br><br></div>
<div class=3D"gmail_quote">On Fri, Jun 15, 2012 at 9:29 PM, The IESG <span =
dir=3D"ltr">&lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank=
">iesg-secretary@ietf.org</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote"><br>The IESG has received a request f=
rom an individual submitter to consider<br>the following document:<br>- &#3=
9;Publishing the &quot;Tao of the IETF&quot; as a Web Page&#39;<br>
=A0&lt;draft-hoffman-tao-as-web-page-02.txt&gt; as Informational RFC<br><br=
>The IESG plans to make a decision in the next few weeks, and solicits<br>f=
inal comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2012-07=
-13. Exceptionally, comments may be<br>sent to <a href=3D"mailto:iesg@ietf.=
org">iesg@ietf.org</a> instead. In either case, please retain the<br>beginn=
ing of the Subject line to allow automated sorting.<br>
<br>Abstract<br><br><br>=A0 Discussion of the &quot;Tao of the IETF&quot; d=
uring 2012 made it clear that<br>=A0 many people want the document publishe=
d only as a web page, not as an<br>=A0 RFC that needs to be periodically up=
dated. =A0This document specifies<br>
=A0 how the Tao will be published as a web page.<br><br><br><br><br>The fil=
e can be obtained via<br><a href=3D"http://datatracker.ietf.org/doc/draft-h=
offman-tao-as-web-page/" target=3D"_blank">http://datatracker.ietf.org/doc/=
draft-hoffman-tao-as-web-page/</a><br>
<br>IESG discussion can be tracked via<br><a href=3D"http://datatracker.iet=
f.org/doc/draft-hoffman-tao-as-web-page/ballot/" target=3D"_blank">http://d=
atatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/ballot/</a><br><br><b=
r>
No IPR declarations have been submitted directly on this I-D.<br><br><br></=
blockquote></div><br>

--f46d043890570bc3ec04c2936620--

From GK@ninebynine.org  Fri Jun 15 10:37:21 2012
Return-Path: <GK@ninebynine.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD2E321F8673 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 10:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.116
X-Spam-Level: 
X-Spam-Status: No, score=-5.116 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, DATE_IN_PAST_06_12=1.069, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
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 3Xos4gohsZpd for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 10:37:19 -0700 (PDT)
Received: from relay9.mail.ox.ac.uk (relay9.mail.ox.ac.uk [163.1.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 2BC6F21F8672 for <ietf@ietf.org>; Fri, 15 Jun 2012 10:37:18 -0700 (PDT)
Received: from smtp1.mail.ox.ac.uk ([129.67.1.207]) by relay9.mail.ox.ac.uk with esmtp (Exim 4.75) (envelope-from <GK@ninebynine.org>) id 1SfaSN-0003Aj-T5; Fri, 15 Jun 2012 18:37:11 +0100
Received: from arl-d-234.arl.org ([192.100.21.234] helo=Eskarina.local) by smtp1.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1SfaSM-0005jP-4E; Fri, 15 Jun 2012 18:37:10 +0100
Message-ID: <4FDB1319.7040501@ninebynine.org>
Date: Fri, 15 Jun 2012 11:48:57 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: APPSDIR review of draft-farrell-decade-ni-07, major design issue (one or two URI schemes)
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD712E8.7010506@cs.tcd.ie> <4FD73E76.7050105@it.aoyama.ac.jp> <4FD74D94.4020408@cs.tcd.ie>
In-Reply-To: <4FD74D94.4020408@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Oxford-Username: zool0635
X-Mailman-Approved-At: Mon, 18 Jun 2012 05:41:05 -0700
Cc: IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 17:37:22 -0000

Stephen,

(Personal hat on)

I've followed elements of this exchange.  I must confess that when I read 
through the draft previously, I didn't really pay attention to the nih: parts.

I can see that there are distinct use-cases here, and I think you have 
reasonable grounds for not wanting to combine them.

What I can't see is why the speakable form (nih:) needs to be a URI scheme - 
what are the envisaged contexts of use where the information provided by an nih: 
URI actually needs to be a URI, as opposed to just, say, a simple string?

In all the uses I can think of for ni:, I don't see a corresponding use for a 
speakable form.  I think you said somewhere in this exchange, nih: is intended 
to be used to confirm some information that you already have.  As such, I'm not 
seeing how it can be said to identify a resource.

#g
--

On 12/06/2012 15:09, Stephen Farrell wrote:
>
> Martin,
>
> I honestly don't think this exchange is going
> anywhere new so I've not provided blow-by-blow
> answers below.
>
> We (the authors) think ni and nih are better
> kept separate because the use-cases and
> requirements differ. And that's what the
> limited amount of running code does.
>
> I think I've explained that, and I have no
> intention whatsoever of getting into the "write
> up the use-cases and requirements" game that
> too-often happens in the IETF when its neither
> needed nor productive. (Regardless of whether
> the game is played with I-Ds or email.)
> Sometimes that is useful, but not here IMO.
>
> You disagree, which is fine. You think ni and nih
> should be merged because they don't differ
> sufficiently, (I think), and (I guess) because
> you think that new URI schemes are more expensive
> than what you see as the differences between
> these two proposed schemes warrant.
>
> I suggest we see if anyone else chimes in on
> this aspect (so far nobody has, despite a quite
> active IETF LC:-) and if not leave it to the
> sponsoring AD to figure out what, if anything,
> needs doing at the end of IETF LC.
>
> Cheers,
> S.
>
> PS: Many thanks for all the other good comments,
> though we disagree on this one, you've helped
> make the draft better for sure.
>
>
> On 06/12/2012 02:04 PM, "Martin J. Dürst" wrote:
>> Hello Stephen,
>>
>> On 2012/06/12 18:59, Stephen Farrell wrote:
>>>
>>> Hi Martin,
>>>
>>> On 06/12/2012 10:13 AM, "Martin J. Dürst" wrote:
>>>> Hello Stephen,
>>>>
>>>> This mail responds to your points on the main technical issue that I
>>>> have identified.
>>>>
>>>> On 2012/06/05 20:11, Stephen Farrell wrote:
>>>>
>>>>> On 06/05/2012 10:42 AM, "Martin J. Dürst" wrote:
>>>>>> Hello everybody,
>>
>>>>> Major design issue:
>>>>>>
>>>>>> The draft defines two schemes, which differ only slightly, and mostly
>>>>>> just gratuitously (see also editorial issues).
>>>>>> These are the ni: and the nih: scheme. As far as I understand, they
>>>>>> differ as follows:
>>>>>>                                        ni:                nih:
>>>>>> authority:                          optional           disallowed
>>>>>> ascii-compatible encoding:          base64url          base16
>>>>>> check digit:                        disallowed         optional
>>>>>> query part:                         optional           disallowed
>>>>>> decimal presentation of algorithm:  disallowed         possible
>>>
>>> I'll note in passing that the two schemes differ in all those
>>> respects. You may disagree with our design, but basically you're
>>> showing that the two differ in pretty much all possible ways
>>> other than that both include a hash value.
>>>
>>>>>>
>>>>>> The usability of URIs is strongly influenced by the number of
>>>>>> different
>>>>>> schemes, with the smaller a number, the better. As a somewhat made-up
>>>>>> example, if the original URIs had been separated into httph: for HTML
>>>>>> pages and httpi: for images, or any other arbitrary subdivision
>>>>>> that one
>>>>>> can envision, that would have hurt the growth and extensibility of the
>>>>>> Web. Creating new URI schemes is occasionally necessary, and the ideas
>>>>>> that lead to this draft definitely seem to warrant a new scheme
>>>>>> (*), but
>>>>>> there's no reason for two schemes.
>>>>>> [(*) I know people who would claim the the .well-formed http/https
>>>>>> thing
>>>>>> is completely sufficient, no new scheme needed at all.]
>>>>>>
>>>>>> More specifically, if the original URIs had been separated into httpm:
>>>>>> (for machines) and httph: (for humans), the Web for sure wouldn't have
>>>>>> grown at the speed it did (and does) grow. In practice, there are huge
>>>>>> differences in human 'speakability' for URIs (and IRIs, for that
>>>>>> matter); compare e.g. http://google.com with
>>>>>> http://www.google.co.jp/#sclient=psy-ab&hl=en&site=&source=hp&q=hash&oq=hash&aq=f&aqi=g4&aql=
>>>>>>
>>>>>>
>>>>>>
>>>>>> (which I have significantly shortened to hopefully eliminate potential
>>>>>> privacy issues), or compare the average mailto: URI with the average
>>>>>> data: URI. However, what's important is that there never has been a
>>>>>> strong dividing line between machine-only and human-only URIs or
>>>>>> schemes, the division has always been very gradual. Short and mainly
>>>>>> human-oriented URIs have of course been handled by machines, and on
>>>>>> the
>>>>>> other hand, very long URIs have been spoken when really necessary.
>>>>>> "Speakability" has been maintained to some extent by scheme designers,
>>>>>> and to some extent by "survival of the fittest" (URIs that weren't
>>>>>> very
>>>>>> speakable (or spellable/memorizable/guessable/...), and their Web
>>>>>> sites,
>>>>>> might just die out slowly).
>>>>>>
>>>>>> It should also be noted that the resistance against multiple URI
>>>>>> schemes
>>>>>> may have been low because there are so many different ways to express
>>>>>> hashes in the draft anyway, and one more (the nih: section is the last
>>>>>> one before the examples section) didn't seem like much of a deal
>>>>>> anymore. But when it comes to URIs, one less is a lot better than one
>>>>>> more.
>>>>>>
>>>>>> In the above ni:/nih: distinction, nih: seems to have been added as an
>>>>>> afterthought after realizing that reading an ni: URI aloud over the
>>>>>> phone may be somewhat suboptimal because there is a need for repeated
>>>>>> "upper case" - "lower case" (sure very quickly shortened to "upper" -
>>>>>> "lower" and then to "up" - "low" or something similar). It is not a
>>>>>> bad
>>>>>> idea to try to make sure that IETF technology, and URIs in particular,
>>>>>> are accessible to people with certain kinds of dislexya. (There are
>>>>>> indeed people who have tremendous difficulties with distinguishing
>>>>>> upper- and lower-case letters, and this may or may not be connected
>>>>>> with
>>>>>> other aspects of dislexya.) It is however totally unclear to this
>>>>>> reviewer why this has to lead to two different URI schemes with other
>>>>>> gratuitous differences.
>>>>>>
>>>>>> Finding a solution is rather easy (of course, other solutions may also
>>>>>> be possible): Merge the schemes, so that authority, check digit, and
>>>>>> query part are all optional (an authority part and/or a query part may
>>>>>> very well be very useful in human communication, and a check digit
>>>>>> won't
>>>>>> hurt when transmitted electronically) and the decimal presentation of
>>>>>> the algorithm is always allowed, and use base32
>>>>>> (http://tools.ietf.org/html/rfc4648) as the encoding. This leads to a
>>>>>> 16.6% less efficient encoding of the value part of the ni: URI, but
>>>>>> given that other URI-related encodings, e.g. the %-encoding resulting
>>>>>> when converting an IRI to an URI, are much less efficient, and that
>>>>>> URI
>>>>>> infrastructure these days can handle URIs with more than 1000 bytes,
>>>>>> this should not be a serious problem. Also, there's a separate binary
>>>>>> format (section 6) that is more compact already.
>>>>>
>>>>> I strongly disagree with merging ni&    nih. Though that clearly
>>>>> could be done, it would be an error.
>>>>>
>>>>> There was no such comment on the uri-review list and the designated
>>>>> expert was happy. That review was IMO the time for such comments
>>>>> and second-guessing the designated expert at this stage seems
>>>>> contrary to the registration requirements. So process-wise I
>>>>> think your main comment is late.
>>>>
>>>> First, if IETF Last Call is too late to make serious technical comments
>>>> on drafts, then I think we have to rename it to IETF Too-Late Call.
>>>>
>>>> Second, designated experts are there to check for minimum requirements
>>>> for a registration, and to give advice as they see fit (and have time).
>>>> I'm myself a designated expert on "Character Sets", and I have
>>>> definitely in the past approved, and would again in the future approve,
>>>> registrations for stuff on which I would complain strongly if the
>>>> question was "is this a good technical solution".
>>>>
>>>> Graham Klyne, the designated expert for URI scheme registrations, has
>>>> confirmed offline that he does not see his role as "expert reviewer" as
>>>> judging the technical merit of a URI scheme proposal.
>>>
>>> While that's fair enough. Its also fair to note that there was
>>> discussion of the this document on the uri-review list but this
>>> aspect was not raised at all. That list is called "uri-review"
>>> and from its archives it does seem to frequently do more than
>>> just check the paperwork (including quite a few mails from you:-).
>>
>> Oh well. I'm not sure how familiar you are with the IETF :-), but it's
>> basically all a volunteer organization. So even more than in an
>> organization where people are getting paid, some things happen to get a
>> lot of attention and other things happen to get less attention than
>> maybe they would deserve. And most people have their day jobs, and
>> occasionally miss a mail or two, or even a few more. And many people are
>> on many lists and just skim them until something catches their eye, and
>> ignore many threads. If you don't do anything like this and survive, I'd
>> like to know how :-).
>>
>> So the uri-review list, like any other IETF (or other) list, can get
>> excited about stuff, sometimes for good reasons, or can just ignore some
>> aspects of some proposal. It's unfortunate, but it's something we have
>> to live with. You can't ask everybody on that list to take the same
>> amount of time to look at all the proposals that e.g. a Security
>> Directorate or Apps Area Directorate reviewer is using.
>>
>>
>>>>> But in any case, I also think you're wrong technically in this>>   case.
>>>>
>>>> Let's see. I hope we agree that we should come to a conclusion on this
>>>> issue on technical merits, rather than on process details.
>>>
>>> Sure.
>>
>> Good.
>>
>>>>> nih *is* intended for a corner case,
>>>
>>> Let me emphasise the above. nih is not intended to be used
>>> broadly, nor often. If you want a hash-based URI scheme for
>>> users to speak that is for broad frequent use then I think
>>> you are free to try design one. But nih is not that and is
>>> not intended to be that.
>>
>> Then, at the barest minimum, don't sell it as that. The only thing the
>> draft essentially says is "use this if you want to read/speak it". Now
>> you are saying "don't use that for users to speak, unless in specific
>> corner cases", but you still haven't told me or the readers of the draft
>> what these corner cases are, and why the SHOULD/MUST not use it
>> otherwise even if they might think it makes sense.
>>
>> The second, more general advice is of course to not design URIs for
>> corner cases, because URIs work best if they are used widely. (There may
>> be a very tiny chance that your case is different, but even after
>> reading all your mail, I haven't understood that.)
>>
>>
>>> (And I'm not sure such a beast
>>> could really be done well.)
>>
>> Speaking 256 or so bits of random data aloud is in no way going to be
>> terribly easy :-).
>>
>>
>>>>> where humans need to speak these
>>>>> URIs and was added as a direct result of requirements from the core
>>>>> WG and not as an afterthought. ni URIs are not intended for that
>>>>> and so there really are IMO different requirements, (esp. e.g.
>>>>> checkdigit) that are best met with different schemes.
>>>>
>>>> I agree that the value of a checkdigit is very limited for communication
>>>
>>> s/very limited/useless/
>>>
>>>> among machines (and for communication among humans with the help of
>>>> machines, such as in the case of email).
>>>>
>>>> On the other hand, I can't understand why (even assuming we needed a
>>>> separate scheme) there is no authority and no query part on nih.
>>>
>>> The main intent of nih is to allow entry of something that
>>> confirms something else (e.g. a public key) that is already
>>> present.
>>
>> At least a little bit of information about the "use case", but this just
>> leads to more questions:
>>
>> Do you need an URI for that? (Isn't that what people are supposed to do
>> with fingerprints these days?)
>>
>> How/where would a user input that URI e.g. in a browser?
>>
>> Would copy/paste from an email or a Web page be fine?
>>
>> Would entry be needed, or could it just be checked? (I understand that
>> forcing a user to enter the data is way safer than believing her that a
>> check was made, but then it's also way more tedious, and many users will
>> just switch to different software.)
>>
>> Can ni: URIs also be used for the same purpose? If not, why not (they
>> essentially contain the same information)?
>>
>> What about other URIs, starting e.g. with http:?
>>
>> I won't claim that this list of questions is exhaustive, but I hope it's
>> a good start.
>>
>>
>>> There is no need for an authority for that, for
>>> the use-cases we have. We could speculate about other potential
>>> use-cases but we'd rather not speculate like that when there's
>>> no need to.
>>
>> There was a lot of stuff that we take for granted today that Tim
>> Berners-Lee didn't speculate when he designed the first URI schemes. But
>> if he had designed these schemes with only corner cases in mind, he
>> wouldn't have invented the Web :-). (sorry about an analogy again)
>>
>>
>>>> For the authority, I'd assume that it would be as useful when the URI is
>>>> transmitted e.g. over the phone as when it is transmitted e.g. over
>>>> email.
>>>
>>> We don't have a use for that that I know about.
>>
>> Do you mean the "over the phone" part or the authority part? (assuming
>> the later below)
>>
>>> I agree
>>> it could be done, but then I think it'd also impact on
>>> usability, which will be pretty crap no matter what's
>>> done.
>>
>> Reading "example.com" or some equivalent domain name in addition to a
>> long hex string shouldn't really make matters much worse.
>>
>>> But making usability worse also seems wrong.
>>
>> My understanding is that there are some cases where things will be found
>> with authority, but not without. If that's right, then I'm sure users
>> will prefer to find what they are looking for, after aurally
>> transmitting 256 or thereabout bits, even at the cost of an additional
>> domain name (and a few slashes), which are the easiest parts to get
>> across the line quickly and correctly.
>>
>>
>>> Not
>>> having an authority also seems to work fine for PGP keys
>>
>> That the lack of authority works in some cases is perfectly okay. But
>> it's not an argument for not allowing authority for cases (even those
>> that maybe you're not seeing yet) where it is or will be useful.
>>
>>
>>> and the lack of an authority does get rid of some threats,
>>> if the nih URI is used for something security-sensitive.
>>
>> Which would mean that ni: has these threats, yes? Where are they
>> described? I don't remember seeing them in the security section.
>>
>>
>>>> For the query part, there are already various ideas and proposals
>>>> floating around,
>>>
>>> Where? If you mean draft-hallambaker-decade-params
>>
>> Correct.
>>
>>> then
>>> we (the authors of that) don't think those are useful for
>>> nih names.
>>
>> Why not? And what if others think they would be useful?
>>
>>
>>>> and at least some of them would be of interest for when
>>>> the URI is transmitted e.g. over the phone. Also, even if we currently
>>>> didn't have any actual proposals for query parameters, I think it would
>>>> be a very bad idea to exclude them a priori for transmission e.g. over
>>>> the phone.
>>>
>>> I disagree that there is any "very bad idea" here.
>>>
>>>>> Merging ni/nih would also add more complexity for no benefit,
>>>>> which would be a bad idea.
>>>>
>>>> Can you please explain what kind of complexity would have to be added?
>>>
>>> I think its obvious actually. In your table above you highlighted
>>> 5 ways in which ni and nih differ. Merging all those yields loads
>>> of combinations, which makes for complexity.
>>
>> Well, if your implementation is a big switch with 32 cases, one for each
>> combination, with no code sharing, then indeed you get complexity. But I
>> hope we agree that that's very bad design, and totally unnecessary. It's
>> very straightforward to go through the components one-by-one and deal
>> with them (hint: I'd start with the check digit).
>>
>> On the other hand, the complexity you get from query parameters is
>> potentially huge, because, contrary to the basic syntax, we don't know
>> for sure what combinations of parameters people will dream up, and how
>> these will interact.
>>
>>
>>>> In terms of specification, merging the two schemes doesn't seem to be
>>>> difficult or complex at all. Also, in terms of implementation, the only
>>>> additions to the ni: scheme that become necessary are the check digit
>>>> and the expression of the "suite id" as a decimal. It's very difficult
>>>> for me to imagine that this would add significant complexity to an
>>>> implementation; if code for nih: exists, that can mostly just be moved
>>>> over.
>>>
>>> Feel free to look at our code. (With the caveat that I'm a crap
>>> programmer so close your eyes a bit when you look at the 'C' code:-)
>>>
>>>>> Your analogy about httpm/h may appear reasonable, but it is always
>>>>> unreasonable to draw conclusions from analogies. It is also unwise
>>>>> to reason from counterfactuals, which we'd also be doing if we
>>>>> accepted your argument. So I find that speculation utterly useless
>>>>> to be honest.
>>>>
>>>> It is definitely unreasonable to draw conclusions from analogies *only*.
>>>
>>> I only saw the analogy. What in your httpm/h argument is not
>>> couterfactual analogy?
>>
>> Do you claim that it's not true that URIs are often transferred
>> electronically, often transferred on paper, and often spoken, and that
>> these sets for which these activities happen overlap? If you think that
>> has to be different for ni:/nih:, you have to convince me, not the other
>> way round.
>>
>>
>>>> But if you think that the httpm/h analogy is wrong, and that ni/nih is
>>>> different, could you please explain *what* is different?
>>>
>>> We have real use cases for ni and nih and we think they differ.
>>> I'd be repeating myself to say why again.
>>
>> You're still very vague on these "real use cases". Confirmation of PGP
>> keys by speaking the URI aloud seems to be your main/only use case for
>> nih:. But I'm only guessing, because you haven't really explained this yet.
>>
>>>>> In this case, we are dealing with different requirements so this
>>>>> should stay as-is.
>>>>
>>>> If "different requirements" is your main (or only) real argument,
>>>
>>> That would be a valid argument.
>>
>> It would only be a valid argument if these are requirements that can't
>> be consolidated.
>>
>>
>>>> could
>>>> you at least explain exactly how they are different?
>>>
>>> I did that above. Asking for an "exact" explanation seems
>>> like asking the same thing again.
>>
>> Here are the pieces of text from above that I can at least in some way
>> link to actual requirements:
>> "nih is not intended to be used broadly, nor often."
>> "The main intent of nih is to allow entry of something that
>> confirms something else (e.g. a public key) that is already
>> present."
>>
>> Is that all there is? Or did I miss something? Maybe it would help this
>> discussion if you wrote a few paragraphs of free-standing text
>> explaining the use cases (and restrictions, and reasons for these) for
>> both schemes. It may turn out to be a valid addition to the document at
>> the very minimum. (I'm not asking for an independent "use cases and
>> requirements" draft :-)
>>
>>
>>>> Just that one
>>>> requirement came from the core WG and others from other WGs or other
>>>> parties doesn't help me to understand how the actual requirements
>>>> differ. (Please note that even if the requirements differ, that doesn't
>>>> mean that we need different technology to address them.)
>>>
>>> Perhaps not. But that was the design choice we made and its
>>> a valid one.
>>
>> Given the more than 20 years of experience we have of how URIs are
>> handled on the Web and around it, I have very good reasons to strongly
>> doubt that this is a good design choice.
>>
>>
>>>> Why do you say that ni: URIs are not intended for humans to speak?
>>>
>>> So phone me up and say this:
>>>
>>>     ni:///sha-256;UyaQV-Ev4rdLoHyJJWCi11OHfrYv9E1aGQAlMO2X_-Q
>>
>> So apart from the upper/lower problem, would the equivalent nih: URI be
>> any better?
>>
>>>> What
>>>> am I supposed to do if I got an ni: URI in a mail message and call you
>>>> on the phone to tell you about that?
>>>
>>> Not my problem actually, but I guess most people might
>>> say "remember that mail you sent me with all that gobbledygook
>>> nonsense - what the hell was that about?" :-)
>>
>> I think "tell you about it" should have been "speak it out to you".
>>
>>
>>>>    If I want to send somebody the
>>>> information in an ni: URI by mail, should I use only the ni: version or
>>>> only the nih: version, or both, if I can't exclude that the recipient
>>>> may want to relay this information via voice?
>>>
>>> You can try either and let me know what works. This seems like
>>> a very artificial use-case for ni.
>>
>> Why artificial? Long URIs get spoken over the phone once in a while. And
>> I really don't understand why this is "very artificial" for ni:, but
>> "indispensable" for nih:.
>>
>>
>>>>> Finally, we have (some, early,) running code that matches the
>>>>> current draft and that ought also count for something
>>>>
>>>> How much?
>>>
>>> Feel free to go look and see. [1] I've not counted lines of
>>> code, but we have c, python, ruby and clojure library
>>> implementations and some apps and other bits and pieces.
>>>
>>>      [1] http://sourceforge.net/projects/netinf/
>>>
>>>> The boiler plate on every ID is pretty clear that they are not
>>>> set in stone. Also, the changes needed to merge the two schemes are not
>>>> rocket science, quite to the contrary. (I herewith volunteer to fix the
>>>> Ruby version, just to show)
>>>
>>> I didn't say our code is set in stone. I said that running code
>>> counts.
>>>
>>> I didn't say a merge would require rocket science.
>>
>> It somehow sounded like this.
>>
>>> I said it'd be
>>> a bad idea and would produce a worse result.
>>
>> Can you substantiate that? The discussion on use cases is still open,
>> and the argument with all the 32 combinations also didn't fly.
>>
>>>>> when compared
>>>>> to a change that would be a gratuitous dis-improvement
>>>>
>>>> In what sense would merging the two schemes be a dis-improvement? Can
>>>> you please explain?
>>>
>>> I believe I did that above.
>>
>> Very marginally, perhaps. More information would definitely help.
>>
>>>>> based it
>>>>> seems upon dubious argument
>>>>
>>>> If you think that my arguments are dubious, please explain exactly why.
>>>
>>> I believe I did that above. (To be clear: not all your argument is
>>> dubious
>>
>> Thanks for some encouragement :-).
>>
>>
>>> but the httph/m part is IMO.)
>>
>> I'm sorry that I started out with that analogy, but I thought it would
>> be easy to understand. You seem to be caught in the specific use/corner
>> cases, but I'm trying to look at the long term big picture.
>>
>>
>>>>> that is also offered at the wrong
>>>>> point in the process.
>>>>
>>>> See above. If there's something wrong with IETF Last Call, or with the
>>>> fact that the Apps Area Directorate does reviews (which I don't think),
>>>> then that should be addressed separately. For this discussion, I hope we
>>>> can concentrate on technical issues.
>>>
>>> Right. But let's not ignore the fact that the uri-review
>>> list had sight of this at the end of April.
>>
>> [If you keep insisting, why don't you check your MUA and look at all the
>> messages I sent on the draft. You may be surprised, but I seriously hope
>> you will stop bringing up "uri-review" again.]
>>
>>
>>> Bottom line - we have use-cases and a valid design and running
>>> code that as far as we know works and I see no reason to make
>>> the change you'd like, which would make thing worse IMO.
>>
>> It may look like some more work in the short time, but it will make
>> things more general and create more potential for the future.
>>
>>
>> Regards,    Martin.
>>
>>
>

From GK@ninebynine.org  Fri Jun 15 10:37:25 2012
Return-Path: <GK@ninebynine.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA40B21F8673 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 10:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.323
X-Spam-Level: 
X-Spam-Status: No, score=-5.323 tagged_above=-999 required=5 tests=[AWL=0.207,  BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, RCVD_IN_DNSWL_MED=-4]
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 rhdSkOkSm44F for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 10:37:25 -0700 (PDT)
Received: from relay3.mail.ox.ac.uk (relay3.mail.ox.ac.uk [163.1.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id DB6BF21F8672 for <ietf@ietf.org>; Fri, 15 Jun 2012 10:37:24 -0700 (PDT)
Received: from smtp1.mail.ox.ac.uk ([129.67.1.207]) by relay3.mail.ox.ac.uk with esmtp (Exim 4.75) (envelope-from <GK@ninebynine.org>) id 1SfaSQ-0006fp-CB; Fri, 15 Jun 2012 18:37:14 +0100
Received: from arl-d-234.arl.org ([192.100.21.234] helo=Eskarina.local) by smtp1.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1SfaSQ-0005jV-4E; Fri, 15 Jun 2012 18:37:14 +0100
Message-ID: <4FDB1510.40702@ninebynine.org>
Date: Fri, 15 Jun 2012 11:57:20 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: registries and designated experts
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <4FD75881.3080102@dcrocker.net>
In-Reply-To: <4FD75881.3080102@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
X-Mailman-Approved-At: Mon, 18 Jun 2012 05:41:05 -0700
Cc: "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 17:37:25 -0000

On 12/06/2012 15:56, Dave Crocker wrote:
>
> On 6/12/2012 7:19 AM, Peter Saint-Andre wrote:
>> it's not the role of the designated expert to
>> act as a gatekeeper with respect to the technical merits of the
>> technologies that trigger registration requests. It might be good to
>> have a wider discussion about the purpose of registries and the role of
>> designated experts, but IMHO it's not correct to conclude that a
>> technology is acceptable just because the designated expert didn't
>> object to the registrations related to that technology.
>
>
> It's almost inevitable that many designated experts will, in fact, act as
> gatekeepers. For example the distinction between "won't do damage" vs. "looks
> like excellent engineering" is more subtle in practice than one might think.
> Especially absent very precise specification of review criteria and absent
> actual training of the reviewers.

The effect may sometimes be similar to being a gatekeeper but, speaking for 
myself, that's not how I see my role.  When responding to IANA review requests, 
I may often have and express technical opinions about a proposal, but I try to 
be clear that these are separate from my view of whether or not the registry 
requirements are satisfied.  And where I feel that registration requirements are 
not satisfied, I try to provide indicators as to what the submitter might do to 
create satisfaction.  So it doesn't *feel* like being a gatekeeper.

> While, yes, protocol specs that define the registry and review of its entries
> are supposed to provide the necessary details that do the distinction, I believe
> such texts do not get deep review for interpretive robustness. That is, I doubt
> they are bullet-proofed against the vagaries of differerent readers who might be
> doing the reviews or writing text for them.

My experience is that no amount of review completely bullet-proofs a spec 
against misinterpretation.  So we do the best we can.

#g
--

From GK@ninebynine.org  Fri Jun 15 17:30:27 2012
Return-Path: <GK@ninebynine.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E43A611E807F for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 17:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
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 33VkAzr72Zun for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2012 17:30:25 -0700 (PDT)
Received: from relay2.mail.ox.ac.uk (relay2.mail.ox.ac.uk [163.1.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 4687A11E808C for <ietf@ietf.org>; Fri, 15 Jun 2012 17:30:25 -0700 (PDT)
Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay2.mail.ox.ac.uk with esmtp (Exim 4.75) (envelope-from <GK@ninebynine.org>) id 1Sfgu7-0002cT-8v; Sat, 16 Jun 2012 01:30:15 +0100
Received: from client0997.vpn.ox.ac.uk ([129.67.119.229] helo=Eskarina.local) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1Sfgu1-0004Bb-7d; Sat, 16 Jun 2012 01:30:15 +0100
Message-ID: <4FDBCE2C.1080702@ninebynine.org>
Date: Sat, 16 Jun 2012 01:07:08 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: APPSDIR review of draft-farrell-decade-ni-07, major design issue (one or two URI schemes)
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD712E8.7010506@cs.tcd.ie> <4FD73E76.7050105@it.aoyama.ac.jp> <4FD74D94.4020408@cs.tcd.ie> <4FDB1319.7040501@ninebynine.org> <4FDB8A73.4090707@cs.tcd.ie>
In-Reply-To: <4FDB8A73.4090707@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Oxford-Username: zool0635
X-Mailman-Approved-At: Mon, 18 Jun 2012 05:41:05 -0700
Cc: IETF discussion list <ietf@ietf.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 00:30:28 -0000

On 15/06/2012 20:18, Stephen Farrell wrote:
>> I think you said somewhere in this exchange, nih:
>> is intended to be used to confirm some information that you already
>> have.  As such, I'm not seeing how it can be said to identify a resource.
>
> I'm checking with others since I'm not entirely familiar with
> all that they want from nih, (so you might be right, or maybe
> not;-)
>
> As far as I do know now, the idea is that nih could be useful
> when values are to be read over the phone. I agree the listener
> wouldn't need the scheme, but I think the argument is that it'd
> help the speaker (or speaker's UA) to highlight the right thing.
> I'd agree if you argued that that's not the most compelling
> reason, but maybe there's more.
>
> In terms of identifying a resource, I don't get the
> comment, since the information is similar to that in an ni,
> so it does identify whatever it is matches that hash.

I meant to say that I don't see how it is being *used* to identify a resource - 
as you point out, it clearly *can* so identify, as much as ni: can.

What I'm trying to get to is why one might need a URI, rather than just a 
string, in situations where nih: might be used.  One of the useful features of 
URIs is that they provide a uniform way of referencing things that may be 
accessed or "baptized" by a variety of different mechanisms or structures, 
decoupling the identification mechanism from the details of what is done with 
the thing identified.  The particular use of confirming information one already 
has doesn't seem to fit this model of separating use of some value from the form 
of identification and/or access mechanism.

#g
--








>> On 12/06/2012 15:09, Stephen Farrell wrote:
>>>
>>> Martin,
>>>
>>> I honestly don't think this exchange is going
>>> anywhere new so I've not provided blow-by-blow
>>> answers below.
>>>
>>> We (the authors) think ni and nih are better
>>> kept separate because the use-cases and
>>> requirements differ. And that's what the
>>> limited amount of running code does.
>>>
>>> I think I've explained that, and I have no
>>> intention whatsoever of getting into the "write
>>> up the use-cases and requirements" game that
>>> too-often happens in the IETF when its neither
>>> needed nor productive. (Regardless of whether
>>> the game is played with I-Ds or email.)
>>> Sometimes that is useful, but not here IMO.
>>>
>>> You disagree, which is fine. You think ni and nih
>>> should be merged because they don't differ
>>> sufficiently, (I think), and (I guess) because
>>> you think that new URI schemes are more expensive
>>> than what you see as the differences between
>>> these two proposed schemes warrant.
>>>
>>> I suggest we see if anyone else chimes in on
>>> this aspect (so far nobody has, despite a quite
>>> active IETF LC:-) and if not leave it to the
>>> sponsoring AD to figure out what, if anything,
>>> needs doing at the end of IETF LC.
>>>
>>> Cheers,
>>> S.
>>>
>>> PS: Many thanks for all the other good comments,
>>> though we disagree on this one, you've helped
>>> make the draft better for sure.
>>>
>>>
>>> On 06/12/2012 02:04 PM, "Martin J. Dürst" wrote:
>>>> Hello Stephen,
>>>>
>>>> On 2012/06/12 18:59, Stephen Farrell wrote:
>>>>>
>>>>> Hi Martin,
>>>>>
>>>>> On 06/12/2012 10:13 AM, "Martin J. Dürst" wrote:
>>>>>> Hello Stephen,
>>>>>>
>>>>>> This mail responds to your points on the main technical issue that I
>>>>>> have identified.
>>>>>>
>>>>>> On 2012/06/05 20:11, Stephen Farrell wrote:
>>>>>>
>>>>>>> On 06/05/2012 10:42 AM, "Martin J. Dürst" wrote:
>>>>>>>> Hello everybody,
>>>>
>>>>>>> Major design issue:
>>>>>>>>
>>>>>>>> The draft defines two schemes, which differ only slightly, and
>>>>>>>> mostly
>>>>>>>> just gratuitously (see also editorial issues).
>>>>>>>> These are the ni: and the nih: scheme. As far as I understand, they
>>>>>>>> differ as follows:
>>>>>>>>                                         ni:                nih:
>>>>>>>> authority:                          optional           disallowed
>>>>>>>> ascii-compatible encoding:          base64url          base16
>>>>>>>> check digit:                        disallowed         optional
>>>>>>>> query part:                         optional           disallowed
>>>>>>>> decimal presentation of algorithm:  disallowed         possible
>>>>>
>>>>> I'll note in passing that the two schemes differ in all those
>>>>> respects. You may disagree with our design, but basically you're
>>>>> showing that the two differ in pretty much all possible ways
>>>>> other than that both include a hash value.
>>>>>
>>>>>>>>
>>>>>>>> The usability of URIs is strongly influenced by the number of
>>>>>>>> different
>>>>>>>> schemes, with the smaller a number, the better. As a somewhat
>>>>>>>> made-up
>>>>>>>> example, if the original URIs had been separated into httph: for
>>>>>>>> HTML
>>>>>>>> pages and httpi: for images, or any other arbitrary subdivision
>>>>>>>> that one
>>>>>>>> can envision, that would have hurt the growth and extensibility
>>>>>>>> of the
>>>>>>>> Web. Creating new URI schemes is occasionally necessary, and the
>>>>>>>> ideas
>>>>>>>> that lead to this draft definitely seem to warrant a new scheme
>>>>>>>> (*), but
>>>>>>>> there's no reason for two schemes.
>>>>>>>> [(*) I know people who would claim the the .well-formed http/https
>>>>>>>> thing
>>>>>>>> is completely sufficient, no new scheme needed at all.]
>>>>>>>>
>>>>>>>> More specifically, if the original URIs had been separated into
>>>>>>>> httpm:
>>>>>>>> (for machines) and httph: (for humans), the Web for sure wouldn't
>>>>>>>> have
>>>>>>>> grown at the speed it did (and does) grow. In practice, there are
>>>>>>>> huge
>>>>>>>> differences in human 'speakability' for URIs (and IRIs, for that
>>>>>>>> matter); compare e.g. http://google.com with
>>>>>>>> http://www.google.co.jp/#sclient=psy-ab&hl=en&site=&source=hp&q=hash&oq=hash&aq=f&aqi=g4&aql=
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> (which I have significantly shortened to hopefully eliminate
>>>>>>>> potential
>>>>>>>> privacy issues), or compare the average mailto: URI with the average
>>>>>>>> data: URI. However, what's important is that there never has been a
>>>>>>>> strong dividing line between machine-only and human-only URIs or
>>>>>>>> schemes, the division has always been very gradual. Short and mainly
>>>>>>>> human-oriented URIs have of course been handled by machines, and on
>>>>>>>> the
>>>>>>>> other hand, very long URIs have been spoken when really necessary.
>>>>>>>> "Speakability" has been maintained to some extent by scheme
>>>>>>>> designers,
>>>>>>>> and to some extent by "survival of the fittest" (URIs that weren't
>>>>>>>> very
>>>>>>>> speakable (or spellable/memorizable/guessable/...), and their Web
>>>>>>>> sites,
>>>>>>>> might just die out slowly).
>>>>>>>>
>>>>>>>> It should also be noted that the resistance against multiple URI
>>>>>>>> schemes
>>>>>>>> may have been low because there are so many different ways to
>>>>>>>> express
>>>>>>>> hashes in the draft anyway, and one more (the nih: section is the
>>>>>>>> last
>>>>>>>> one before the examples section) didn't seem like much of a deal
>>>>>>>> anymore. But when it comes to URIs, one less is a lot better than
>>>>>>>> one
>>>>>>>> more.
>>>>>>>>
>>>>>>>> In the above ni:/nih: distinction, nih: seems to have been added
>>>>>>>> as an
>>>>>>>> afterthought after realizing that reading an ni: URI aloud over the
>>>>>>>> phone may be somewhat suboptimal because there is a need for
>>>>>>>> repeated
>>>>>>>> "upper case" - "lower case" (sure very quickly shortened to
>>>>>>>> "upper" -
>>>>>>>> "lower" and then to "up" - "low" or something similar). It is not a
>>>>>>>> bad
>>>>>>>> idea to try to make sure that IETF technology, and URIs in
>>>>>>>> particular,
>>>>>>>> are accessible to people with certain kinds of dislexya. (There are
>>>>>>>> indeed people who have tremendous difficulties with distinguishing
>>>>>>>> upper- and lower-case letters, and this may or may not be connected
>>>>>>>> with
>>>>>>>> other aspects of dislexya.) It is however totally unclear to this
>>>>>>>> reviewer why this has to lead to two different URI schemes with
>>>>>>>> other
>>>>>>>> gratuitous differences.
>>>>>>>>
>>>>>>>> Finding a solution is rather easy (of course, other solutions may
>>>>>>>> also
>>>>>>>> be possible): Merge the schemes, so that authority, check digit, and
>>>>>>>> query part are all optional (an authority part and/or a query
>>>>>>>> part may
>>>>>>>> very well be very useful in human communication, and a check digit
>>>>>>>> won't
>>>>>>>> hurt when transmitted electronically) and the decimal
>>>>>>>> presentation of
>>>>>>>> the algorithm is always allowed, and use base32
>>>>>>>> (http://tools.ietf.org/html/rfc4648) as the encoding. This leads
>>>>>>>> to a
>>>>>>>> 16.6% less efficient encoding of the value part of the ni: URI, but
>>>>>>>> given that other URI-related encodings, e.g. the %-encoding
>>>>>>>> resulting
>>>>>>>> when converting an IRI to an URI, are much less efficient, and that
>>>>>>>> URI
>>>>>>>> infrastructure these days can handle URIs with more than 1000 bytes,
>>>>>>>> this should not be a serious problem. Also, there's a separate
>>>>>>>> binary
>>>>>>>> format (section 6) that is more compact already.
>>>>>>>
>>>>>>> I strongly disagree with merging ni&     nih. Though that clearly
>>>>>>> could be done, it would be an error.
>>>>>>>
>>>>>>> There was no such comment on the uri-review list and the designated
>>>>>>> expert was happy. That review was IMO the time for such comments
>>>>>>> and second-guessing the designated expert at this stage seems
>>>>>>> contrary to the registration requirements. So process-wise I
>>>>>>> think your main comment is late.
>>>>>>
>>>>>> First, if IETF Last Call is too late to make serious technical
>>>>>> comments
>>>>>> on drafts, then I think we have to rename it to IETF Too-Late Call.
>>>>>>
>>>>>> Second, designated experts are there to check for minimum requirements
>>>>>> for a registration, and to give advice as they see fit (and have
>>>>>> time).
>>>>>> I'm myself a designated expert on "Character Sets", and I have
>>>>>> definitely in the past approved, and would again in the future
>>>>>> approve,
>>>>>> registrations for stuff on which I would complain strongly if the
>>>>>> question was "is this a good technical solution".
>>>>>>
>>>>>> Graham Klyne, the designated expert for URI scheme registrations, has
>>>>>> confirmed offline that he does not see his role as "expert
>>>>>> reviewer" as
>>>>>> judging the technical merit of a URI scheme proposal.
>>>>>
>>>>> While that's fair enough. Its also fair to note that there was
>>>>> discussion of the this document on the uri-review list but this
>>>>> aspect was not raised at all. That list is called "uri-review"
>>>>> and from its archives it does seem to frequently do more than
>>>>> just check the paperwork (including quite a few mails from you:-).
>>>>
>>>> Oh well. I'm not sure how familiar you are with the IETF :-), but it's
>>>> basically all a volunteer organization. So even more than in an
>>>> organization where people are getting paid, some things happen to get a
>>>> lot of attention and other things happen to get less attention than
>>>> maybe they would deserve. And most people have their day jobs, and
>>>> occasionally miss a mail or two, or even a few more. And many people are
>>>> on many lists and just skim them until something catches their eye, and
>>>> ignore many threads. If you don't do anything like this and survive, I'd
>>>> like to know how :-).
>>>>
>>>> So the uri-review list, like any other IETF (or other) list, can get
>>>> excited about stuff, sometimes for good reasons, or can just ignore some
>>>> aspects of some proposal. It's unfortunate, but it's something we have
>>>> to live with. You can't ask everybody on that list to take the same
>>>> amount of time to look at all the proposals that e.g. a Security
>>>> Directorate or Apps Area Directorate reviewer is using.
>>>>
>>>>
>>>>>>> But in any case, I also think you're wrong technically in this>>
>>>>>>> case.
>>>>>>
>>>>>> Let's see. I hope we agree that we should come to a conclusion on this
>>>>>> issue on technical merits, rather than on process details.
>>>>>
>>>>> Sure.
>>>>
>>>> Good.
>>>>
>>>>>>> nih *is* intended for a corner case,
>>>>>
>>>>> Let me emphasise the above. nih is not intended to be used
>>>>> broadly, nor often. If you want a hash-based URI scheme for
>>>>> users to speak that is for broad frequent use then I think
>>>>> you are free to try design one. But nih is not that and is
>>>>> not intended to be that.
>>>>
>>>> Then, at the barest minimum, don't sell it as that. The only thing the
>>>> draft essentially says is "use this if you want to read/speak it". Now
>>>> you are saying "don't use that for users to speak, unless in specific
>>>> corner cases", but you still haven't told me or the readers of the draft
>>>> what these corner cases are, and why the SHOULD/MUST not use it
>>>> otherwise even if they might think it makes sense.
>>>>
>>>> The second, more general advice is of course to not design URIs for
>>>> corner cases, because URIs work best if they are used widely. (There may
>>>> be a very tiny chance that your case is different, but even after
>>>> reading all your mail, I haven't understood that.)
>>>>
>>>>
>>>>> (And I'm not sure such a beast
>>>>> could really be done well.)
>>>>
>>>> Speaking 256 or so bits of random data aloud is in no way going to be
>>>> terribly easy :-).
>>>>
>>>>
>>>>>>> where humans need to speak these
>>>>>>> URIs and was added as a direct result of requirements from the core
>>>>>>> WG and not as an afterthought. ni URIs are not intended for that
>>>>>>> and so there really are IMO different requirements, (esp. e.g.
>>>>>>> checkdigit) that are best met with different schemes.
>>>>>>
>>>>>> I agree that the value of a checkdigit is very limited for
>>>>>> communication
>>>>>
>>>>> s/very limited/useless/
>>>>>
>>>>>> among machines (and for communication among humans with the help of
>>>>>> machines, such as in the case of email).
>>>>>>
>>>>>> On the other hand, I can't understand why (even assuming we needed a
>>>>>> separate scheme) there is no authority and no query part on nih.
>>>>>
>>>>> The main intent of nih is to allow entry of something that
>>>>> confirms something else (e.g. a public key) that is already
>>>>> present.
>>>>
>>>> At least a little bit of information about the "use case", but this just
>>>> leads to more questions:
>>>>
>>>> Do you need an URI for that? (Isn't that what people are supposed to do
>>>> with fingerprints these days?)
>>>>
>>>> How/where would a user input that URI e.g. in a browser?
>>>>
>>>> Would copy/paste from an email or a Web page be fine?
>>>>
>>>> Would entry be needed, or could it just be checked? (I understand that
>>>> forcing a user to enter the data is way safer than believing her that a
>>>> check was made, but then it's also way more tedious, and many users will
>>>> just switch to different software.)
>>>>
>>>> Can ni: URIs also be used for the same purpose? If not, why not (they
>>>> essentially contain the same information)?
>>>>
>>>> What about other URIs, starting e.g. with http:?
>>>>
>>>> I won't claim that this list of questions is exhaustive, but I hope it's
>>>> a good start.
>>>>
>>>>
>>>>> There is no need for an authority for that, for
>>>>> the use-cases we have. We could speculate about other potential
>>>>> use-cases but we'd rather not speculate like that when there's
>>>>> no need to.
>>>>
>>>> There was a lot of stuff that we take for granted today that Tim
>>>> Berners-Lee didn't speculate when he designed the first URI schemes. But
>>>> if he had designed these schemes with only corner cases in mind, he
>>>> wouldn't have invented the Web :-). (sorry about an analogy again)
>>>>
>>>>
>>>>>> For the authority, I'd assume that it would be as useful when the
>>>>>> URI is
>>>>>> transmitted e.g. over the phone as when it is transmitted e.g. over
>>>>>> email.
>>>>>
>>>>> We don't have a use for that that I know about.
>>>>
>>>> Do you mean the "over the phone" part or the authority part? (assuming
>>>> the later below)
>>>>
>>>>> I agree
>>>>> it could be done, but then I think it'd also impact on
>>>>> usability, which will be pretty crap no matter what's
>>>>> done.
>>>>
>>>> Reading "example.com" or some equivalent domain name in addition to a
>>>> long hex string shouldn't really make matters much worse.
>>>>
>>>>> But making usability worse also seems wrong.
>>>>
>>>> My understanding is that there are some cases where things will be found
>>>> with authority, but not without. If that's right, then I'm sure users
>>>> will prefer to find what they are looking for, after aurally
>>>> transmitting 256 or thereabout bits, even at the cost of an additional
>>>> domain name (and a few slashes), which are the easiest parts to get
>>>> across the line quickly and correctly.
>>>>
>>>>
>>>>> Not
>>>>> having an authority also seems to work fine for PGP keys
>>>>
>>>> That the lack of authority works in some cases is perfectly okay. But
>>>> it's not an argument for not allowing authority for cases (even those
>>>> that maybe you're not seeing yet) where it is or will be useful.
>>>>
>>>>
>>>>> and the lack of an authority does get rid of some threats,
>>>>> if the nih URI is used for something security-sensitive.
>>>>
>>>> Which would mean that ni: has these threats, yes? Where are they
>>>> described? I don't remember seeing them in the security section.
>>>>
>>>>
>>>>>> For the query part, there are already various ideas and proposals
>>>>>> floating around,
>>>>>
>>>>> Where? If you mean draft-hallambaker-decade-params
>>>>
>>>> Correct.
>>>>
>>>>> then
>>>>> we (the authors of that) don't think those are useful for
>>>>> nih names.
>>>>
>>>> Why not? And what if others think they would be useful?
>>>>
>>>>
>>>>>> and at least some of them would be of interest for when
>>>>>> the URI is transmitted e.g. over the phone. Also, even if we currently
>>>>>> didn't have any actual proposals for query parameters, I think it
>>>>>> would
>>>>>> be a very bad idea to exclude them a priori for transmission e.g. over
>>>>>> the phone.
>>>>>
>>>>> I disagree that there is any "very bad idea" here.
>>>>>
>>>>>>> Merging ni/nih would also add more complexity for no benefit,
>>>>>>> which would be a bad idea.
>>>>>>
>>>>>> Can you please explain what kind of complexity would have to be added?
>>>>>
>>>>> I think its obvious actually. In your table above you highlighted
>>>>> 5 ways in which ni and nih differ. Merging all those yields loads
>>>>> of combinations, which makes for complexity.
>>>>
>>>> Well, if your implementation is a big switch with 32 cases, one for each
>>>> combination, with no code sharing, then indeed you get complexity. But I
>>>> hope we agree that that's very bad design, and totally unnecessary. It's
>>>> very straightforward to go through the components one-by-one and deal
>>>> with them (hint: I'd start with the check digit).
>>>>
>>>> On the other hand, the complexity you get from query parameters is
>>>> potentially huge, because, contrary to the basic syntax, we don't know
>>>> for sure what combinations of parameters people will dream up, and how
>>>> these will interact.
>>>>
>>>>
>>>>>> In terms of specification, merging the two schemes doesn't seem to be
>>>>>> difficult or complex at all. Also, in terms of implementation, the
>>>>>> only
>>>>>> additions to the ni: scheme that become necessary are the check digit
>>>>>> and the expression of the "suite id" as a decimal. It's very difficult
>>>>>> for me to imagine that this would add significant complexity to an
>>>>>> implementation; if code for nih: exists, that can mostly just be moved
>>>>>> over.
>>>>>
>>>>> Feel free to look at our code. (With the caveat that I'm a crap
>>>>> programmer so close your eyes a bit when you look at the 'C' code:-)
>>>>>
>>>>>>> Your analogy about httpm/h may appear reasonable, but it is always
>>>>>>> unreasonable to draw conclusions from analogies. It is also unwise
>>>>>>> to reason from counterfactuals, which we'd also be doing if we
>>>>>>> accepted your argument. So I find that speculation utterly useless
>>>>>>> to be honest.
>>>>>>
>>>>>> It is definitely unreasonable to draw conclusions from analogies
>>>>>> *only*.
>>>>>
>>>>> I only saw the analogy. What in your httpm/h argument is not
>>>>> couterfactual analogy?
>>>>
>>>> Do you claim that it's not true that URIs are often transferred
>>>> electronically, often transferred on paper, and often spoken, and that
>>>> these sets for which these activities happen overlap? If you think that
>>>> has to be different for ni:/nih:, you have to convince me, not the other
>>>> way round.
>>>>
>>>>
>>>>>> But if you think that the httpm/h analogy is wrong, and that ni/nih is
>>>>>> different, could you please explain *what* is different?
>>>>>
>>>>> We have real use cases for ni and nih and we think they differ.
>>>>> I'd be repeating myself to say why again.
>>>>
>>>> You're still very vague on these "real use cases". Confirmation of PGP
>>>> keys by speaking the URI aloud seems to be your main/only use case for
>>>> nih:. But I'm only guessing, because you haven't really explained
>>>> this yet.
>>>>
>>>>>>> In this case, we are dealing with different requirements so this
>>>>>>> should stay as-is.
>>>>>>
>>>>>> If "different requirements" is your main (or only) real argument,
>>>>>
>>>>> That would be a valid argument.
>>>>
>>>> It would only be a valid argument if these are requirements that can't
>>>> be consolidated.
>>>>
>>>>
>>>>>> could
>>>>>> you at least explain exactly how they are different?
>>>>>
>>>>> I did that above. Asking for an "exact" explanation seems
>>>>> like asking the same thing again.
>>>>
>>>> Here are the pieces of text from above that I can at least in some way
>>>> link to actual requirements:
>>>> "nih is not intended to be used broadly, nor often."
>>>> "The main intent of nih is to allow entry of something that
>>>> confirms something else (e.g. a public key) that is already
>>>> present."
>>>>
>>>> Is that all there is? Or did I miss something? Maybe it would help this
>>>> discussion if you wrote a few paragraphs of free-standing text
>>>> explaining the use cases (and restrictions, and reasons for these) for
>>>> both schemes. It may turn out to be a valid addition to the document at
>>>> the very minimum. (I'm not asking for an independent "use cases and
>>>> requirements" draft :-)
>>>>
>>>>
>>>>>> Just that one
>>>>>> requirement came from the core WG and others from other WGs or other
>>>>>> parties doesn't help me to understand how the actual requirements
>>>>>> differ. (Please note that even if the requirements differ, that
>>>>>> doesn't
>>>>>> mean that we need different technology to address them.)
>>>>>
>>>>> Perhaps not. But that was the design choice we made and its
>>>>> a valid one.
>>>>
>>>> Given the more than 20 years of experience we have of how URIs are
>>>> handled on the Web and around it, I have very good reasons to strongly
>>>> doubt that this is a good design choice.
>>>>
>>>>
>>>>>> Why do you say that ni: URIs are not intended for humans to speak?
>>>>>
>>>>> So phone me up and say this:
>>>>>
>>>>>      ni:///sha-256;UyaQV-Ev4rdLoHyJJWCi11OHfrYv9E1aGQAlMO2X_-Q
>>>>
>>>> So apart from the upper/lower problem, would the equivalent nih: URI be
>>>> any better?
>>>>
>>>>>> What
>>>>>> am I supposed to do if I got an ni: URI in a mail message and call you
>>>>>> on the phone to tell you about that?
>>>>>
>>>>> Not my problem actually, but I guess most people might
>>>>> say "remember that mail you sent me with all that gobbledygook
>>>>> nonsense - what the hell was that about?" :-)
>>>>
>>>> I think "tell you about it" should have been "speak it out to you".
>>>>
>>>>
>>>>>>     If I want to send somebody the
>>>>>> information in an ni: URI by mail, should I use only the ni:
>>>>>> version or
>>>>>> only the nih: version, or both, if I can't exclude that the recipient
>>>>>> may want to relay this information via voice?
>>>>>
>>>>> You can try either and let me know what works. This seems like
>>>>> a very artificial use-case for ni.
>>>>
>>>> Why artificial? Long URIs get spoken over the phone once in a while. And
>>>> I really don't understand why this is "very artificial" for ni:, but
>>>> "indispensable" for nih:.
>>>>
>>>>
>>>>>>> Finally, we have (some, early,) running code that matches the
>>>>>>> current draft and that ought also count for something
>>>>>>
>>>>>> How much?
>>>>>
>>>>> Feel free to go look and see. [1] I've not counted lines of
>>>>> code, but we have c, python, ruby and clojure library
>>>>> implementations and some apps and other bits and pieces.
>>>>>
>>>>>       [1] http://sourceforge.net/projects/netinf/
>>>>>
>>>>>> The boiler plate on every ID is pretty clear that they are not
>>>>>> set in stone. Also, the changes needed to merge the two schemes are
>>>>>> not
>>>>>> rocket science, quite to the contrary. (I herewith volunteer to fix
>>>>>> the
>>>>>> Ruby version, just to show)
>>>>>
>>>>> I didn't say our code is set in stone. I said that running code
>>>>> counts.
>>>>>
>>>>> I didn't say a merge would require rocket science.
>>>>
>>>> It somehow sounded like this.
>>>>
>>>>> I said it'd be
>>>>> a bad idea and would produce a worse result.
>>>>
>>>> Can you substantiate that? The discussion on use cases is still open,
>>>> and the argument with all the 32 combinations also didn't fly.
>>>>
>>>>>>> when compared
>>>>>>> to a change that would be a gratuitous dis-improvement
>>>>>>
>>>>>> In what sense would merging the two schemes be a dis-improvement? Can
>>>>>> you please explain?
>>>>>
>>>>> I believe I did that above.
>>>>
>>>> Very marginally, perhaps. More information would definitely help.
>>>>
>>>>>>> based it
>>>>>>> seems upon dubious argument
>>>>>>
>>>>>> If you think that my arguments are dubious, please explain exactly
>>>>>> why.
>>>>>
>>>>> I believe I did that above. (To be clear: not all your argument is
>>>>> dubious
>>>>
>>>> Thanks for some encouragement :-).
>>>>
>>>>
>>>>> but the httph/m part is IMO.)
>>>>
>>>> I'm sorry that I started out with that analogy, but I thought it would
>>>> be easy to understand. You seem to be caught in the specific use/corner
>>>> cases, but I'm trying to look at the long term big picture.
>>>>
>>>>
>>>>>>> that is also offered at the wrong
>>>>>>> point in the process.
>>>>>>
>>>>>> See above. If there's something wrong with IETF Last Call, or with the
>>>>>> fact that the Apps Area Directorate does reviews (which I don't
>>>>>> think),
>>>>>> then that should be addressed separately. For this discussion, I
>>>>>> hope we
>>>>>> can concentrate on technical issues.
>>>>>
>>>>> Right. But let's not ignore the fact that the uri-review
>>>>> list had sight of this at the end of April.
>>>>
>>>> [If you keep insisting, why don't you check your MUA and look at all the
>>>> messages I sent on the draft. You may be surprised, but I seriously hope
>>>> you will stop bringing up "uri-review" again.]
>>>>
>>>>
>>>>> Bottom line - we have use-cases and a valid design and running
>>>>> code that as far as we know works and I see no reason to make
>>>>> the change you'd like, which would make thing worse IMO.
>>>>
>>>> It may look like some more work in the short time, but it will make
>>>> things more general and create more potential for the future.
>>>>
>>>>
>>>> Regards,    Martin.
>>>>
>>>>
>>>
>>
>

From abdussalambaryun@gmail.com  Mon Jun 18 06:18:03 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C68721F85A2 for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 06:18:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 agh0ZTjkjWsi for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 06:18:03 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id DB1C621F8595 for <ietf@ietf.org>; Mon, 18 Jun 2012 06:18:02 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2995094vcq.31 for <ietf@ietf.org>; Mon, 18 Jun 2012 06:18:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=vlULzs853aLD93J2MpQwNqC9rhyy8tHN5mK49AzCUHo=; b=oKBqz6bthpmxYN9NnrWv1m4/ZwsKc6QXB9MVFpuAfKv3E1qz8dr3bFphyVKT2pvMl7 1RBhGra33Sq6zHp52OlFdldJPidBo+vxJ3lSoXERzFWNUk5aT0334nL+vE6WsWBB/UF9 ME933KddCJuHaq+8vEtDkXHmGhOyxCrhzl1TO5M9nmsEXwIf+yBX409QtM7I2zfELH3C 5CSx7gOAjMVx7KptfHy6yqmgRzr43LKXxHFta2iLZ9jzanEbrlWywgzaCtT1A5TDYgJZ KDcx/aJof5OI1RCO2w30KnBc4tb85KnXPxHdxwnbnHyTpDXC3Ats5CguxNn/7XlM2yi9 Y8YA==
MIME-Version: 1.0
Received: by 10.220.149.148 with SMTP id t20mr7801422vcv.12.1340025482367; Mon, 18 Jun 2012 06:18:02 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Mon, 18 Jun 2012 06:18:02 -0700 (PDT)
Date: Mon, 18 Jun 2012 15:18:02 +0200
Message-ID: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com>
Subject: Re: Protocol Definition
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: vesely@tana.it
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 13:18:03 -0000

IMO the important issue in any definition is to include how the IETF
defines protocol,
this may be find in some RFCs :)

The IP is the main protocol, and all protocols in IETF are based on IP
and Internet.

AB
++++

On 5 Jan 2012, todd glassey <tglassey at earthlink.net> wrote
> On 1/5/2012 6:48 AM, Dave CROCKER wrote:
>>
>> (One can quibble about the difference between algorithm and
>> program. An algorithm is a component of a program.
>
> The program is the code-based implementation of the alg?
>
>> The distinction is relevant here because a protocol is typically
>> a complete mechanism rather than being a component of the
>> mechanisms.
>
> I.e. "A complete method of doing something"...

I noticed no disagreement between "method" and "mechanism", at the
time.  In retrospect, those two terms might seem to allude to a
different depth of semantic explanations.  Rereading that thread, I
find that the same ambiguity holds for algorithm descriptions:  one
can give a full description (or coding) of, say, sqrt, without
actually saying that the square of the result will match its argument
up to some rounding error.  The specification does not have to relate
the underlying mathematical abstraction.

Protocol specifications, especially when dealing with policies, do not
have to describe the exact meaning of the relevant tokens.  To do that
would often look like mandating a state or a reaction, neither of
which is needed to ensure interoperability.  In fact, the protocol
just has to ensure that a policy can be transmitted correctly.  Many
would rather leave a policy token underspecified than get involved in
its details.

In that respect, a protocol is not a complete method.  The "upper
layer", where policies and politics are dealt with, seems to be too
fuzzy to be specified.  I think this limitation is consistent with the
etymological meaning of the term, that refers to forms of conduct that
don't betray intentions.  Is that right?

From melinda.shore@gmail.com  Mon Jun 18 07:48:51 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B036A21F86B3 for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 07:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 xGWPG1ujDnIO for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 07:48:51 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2498621F86B6 for <ietf@ietf.org>; Mon, 18 Jun 2012 07:48:51 -0700 (PDT)
Received: by dacx6 with SMTP id x6so7093984dac.31 for <ietf@ietf.org>; Mon, 18 Jun 2012 07:48:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=VKKKoqwoHS850TSToS6AT73O4MOS9j1U7SqTMFsB1dI=; b=wQiSK2VYv+WUwCgO44YFaqarhKyzNmBVHZ9muyLmq0o+K+Jlx/0cdxgKz6G2Uipd+w 1YxMpcJLqoRBHpK+rXKnCg9e3tepmCMfsN10L+Kendb3OcRl7WWogLwLdZ7SxH4MQxvm RXdVO6Ce31GBHPT7ljvd980L7d76MPm/26YDoM2VepmebbOn6tuVBaMa0UNESQxB6yha /iy8N687VfYUmuVroiiQ7Oj/KjZkydTf0jhImUCqH1/ddKMTBTinWxdwwI7wuzrjX9Sb GzinW1S+1gv7IsaAdJjCmekiWeQqU8gr10w7Lk5pZcPCTbIFO+G09vRa6j3ECABzvUYv 8SXw==
Received: by 10.68.239.164 with SMTP id vt4mr51550627pbc.166.1340030929753; Mon, 18 Jun 2012 07:48:49 -0700 (PDT)
Received: from spandex.local (66-230-88-51-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.88.51]) by mx.google.com with ESMTPS id tq4sm1891585pbc.11.2012.06.18.07.48.48 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Jun 2012 07:48:48 -0700 (PDT)
Message-ID: <4FDF3FCE.4030406@gmail.com>
Date: Mon, 18 Jun 2012 06:48:46 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CALaySJ+t2sYzFgeN_32E8u+Rw5kNPtwrNoxf0M-ZU63GYW_zDw@mail.gmail.com> <CADnDZ88=yj+-zNXpJy92YfBg+8xq8=fumCJ061YGDRjUMS8yoQ@mail.gmail.com>
In-Reply-To: <CADnDZ88=yj+-zNXpJy92YfBg+8xq8=fumCJ061YGDRjUMS8yoQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 14:48:51 -0000

On 6/18/12 3:11 AM, Abdussalam Baryun wrote:
> It is clear from the draft if you read it, that the decision *is not*
> for the internet-community in two issues: a) editor decision of
> accepting a propose change, b) editor decision of change-updates to
> submit to IESG. The discussion in the I-D is mentioned as just for
> information not as decision making of submission.

This is consistent with how individual, non-WG documents are
progressed in the IETF.  I don't see a conflict or discontinuity.

Melinda


From chair@ietf.org  Mon Jun 18 09:25:22 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCEF921F86DA for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 09:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 vpWnoWP-XN4u for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 09:25:21 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id F290E21F86D5 for <ietf@ietf.org>; Mon, 18 Jun 2012 09:25:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id EE67A12BF0F; Mon, 18 Jun 2012 09:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6Cs3+Qs2Bqq; Mon, 18 Jun 2012 09:25:20 -0700 (PDT)
Received: from [192.168.2.110] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) by c8a.amsl.com (Postfix) with ESMTPSA id 7779012BBAC; Mon, 18 Jun 2012 09:25:20 -0700 (PDT)
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com>
Date: Mon, 18 Jun 2012 12:25:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E80B3213-396E-4092-936B-367C4EB305C8@ietf.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org> <F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com>
To: Eric Burger <eburger-l@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 16:25:22 -0000

Some SDOs have gone to great lengths to specify this in detail.  I am =
hoping that we can avoid that path.  Instead, as Ed already pointed out, =
each person already provides an organizational affiliation when they =
register.  Consistency would be helpful.

Russ


On Jun 15, 2012, at 5:37 PM, Eric Burger wrote:

> Do we have guidelines as to what is an "organization affiliation"?
>=20
> On Jun 14, 2012, at 5:26 PM, IETF Chair wrote:
>=20
>> Two things have occurred since the message below as sent to the IETF =
mail list.  First, we got a lawyer in Europe to do some investigation, =
and the inclusion of the email address on the blue sheet will lead to =
trouble with the European privacy laws.  Second, Ted Hardie suggested =
that we could require a password to access the scanned blue sheet.
>>=20
>> Based on the European privacy law information, the use of email will =
result in a major burden.  If the email address is used, then we must =
provide a way for people to ask for their email address to be remove at =
any time in the future, even if we got prior approval to include it.  =
Therefore, I suggest that we collect organization affiliation to =
discriminate between multiple people with the same name instead of email =
address.
>>=20
>> Based on Ted's suggestion, I checked with the Secretariat about using =
a datatracker login to download the scanned blue sheet.  This is fairly =
easy to do, once the community tracking tools are deployed.  However, =
with the removal of the email addresses from the blue sheets, it is =
unclear that there is any further need for password protection of these =
images.  Therefore, I suggest that we proceed without password =
protection for the blue sheet images.
>>=20
>> Here is a summary of the suggested way forward:
>>=20
>> - Stop collecting email addresses on blue sheets;
>>=20
>> - Collect organization affiliation to discriminate between multiple =
people with the same name;
>>=20
>> - Scan the blue sheets and include the images in the proceedings for =
the WG session;
>>=20
>> - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and
>>=20
>> - Discard paper blue sheets after scanning.
>>=20
>> Russ
>>=20
>>=20
>> On May 6, 2012, at 12:46 PM, IETF Chair wrote:
>>=20
>>> We have heard from many community participants, and consensus is =
quite rough on this topic.  The IESG discussed this thread and reached =
two conclusions:
>>>=20
>>> (1) Rough consensus: an open and transparent standards process is =
more important to the IETF than privacy of blue sheet information.
>>>=20
>>> (2) Rough consensus: inclusion of email addresses is a good way to =
distinguish participants with the same or similar names.
>>>=20
>>>=20
>>> Based on these conclusions, the plan is to handle blue sheets as =
follows:
>>>=20
>>> - Continue to collect email addresses on blue sheets;
>>>=20
>>> - Scan the blue sheet and include the image in the proceedings for =
the WG session;
>>>=20
>>> - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and
>>>=20
>>> - Discard paper blue sheets after scanning.
>>>=20
>>>=20
>>> On behalf of the IESG,
>>> Russ
>>>=20
>>=20
>=20


From touch@isi.edu  Mon Jun 18 11:51:25 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2162421F86F7 for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 11:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ZHscKlFfIOhk for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 11:51:24 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 9913621F86F3 for <ietf@ietf.org>; Mon, 18 Jun 2012 11:51:24 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q5IInZgB023272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 Jun 2012 11:49:36 -0700 (PDT)
Message-ID: <4FDF783F.2030104@isi.edu>
Date: Mon, 18 Jun 2012 11:49:35 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu> <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp> <4FDBEACA.4030701@isi.edu> <4FDC1F9C.2060808@necom830.hpcl.titech.ac.jp> <79E3C9F8-3A0F-4BD7-B018-A508D439ED57@isi.edu> <4FDF219D.5020201@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4FDF219D.5020201@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 18:51:25 -0000

I will include a response to the rest of this in my summary of the last
call concerns. Regarding your last point:

On 6/18/2012 5:39 AM, Masataka Ohta wrote:
...
> PS
> 
> While your draft is rather harmful than useless, I'm fine
> if the following point of the draft:
> 
>     >>  Originating sources MAY set the IPv4 ID field of atomic
>     datagrams to any value.
> 
> is changed to:
> 
>     >>  Originating sources MUST set the IPv4 ID field of atomic
>     datagrams to values as unique as possible.
> 
> which is what the current BSD implementations do.

There are implementations that set DF=1 and ID=0 (cellphones).

BSD does not make IDs as unique as possible; it selects them according
to a pseudorandom algorithm that does not take into account the
datagram's source IP, destination IP, or protocol. I.e., BSD code
repeats the IDs more frequently than necessary when a host concurrently
sources datagrams with different (srcIP, dstIP, proto) tuples.

So it would already be in violation of your proposed wording, as would
most ID generation mechanisms.

Joe

From touch@isi.edu  Mon Jun 18 11:58:45 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9716A21F8657 for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 11:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.099
X-Spam-Level: 
X-Spam-Status: No, score=-104.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 04BWdhuyLB8J for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 11:58:45 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 2239C21F85B5 for <ietf@ietf.org>; Mon, 18 Jun 2012 11:58:45 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q5IIw2VP026235 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 Jun 2012 11:58:03 -0700 (PDT)
Message-ID: <4FDF7A3A.7020900@isi.edu>
Date: Mon, 18 Jun 2012 11:58:02 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu> <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp> <4FDBEACA.4030701@isi.edu> <4FDC2CCB.70904@necom830.hpcl.titech.ac.jp> <603619C7-D09E-4779-8C0A-3EC29C7972A9@isi.edu> <4FDF1A93.2060304@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4FDF1A93.2060304@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 18:58:45 -0000

On 6/18/2012 5:09 AM, Masataka Ohta wrote:
> Joe Touch wrote:
> 
>>> 	draft-generic-v6ops-tunmtu-03.txt
>>>
>>> to fragment IPv6 packets by intermediate routers should be
>>> very interesting to you.
>>
>> It is aware of our IPv4-ID doc, and consistent with it.
> 
> What?

I looked more closely, and the doc is deeply flawed, even though it
appears to intend to be consistent with our IPv4-update doc through rate
limiting.  I'll post a summary to the v6-ops mailing list of those
issues. To summarize:

- it fragments inner packets at the ingress but does not reassemble them
	this means its choice of unique IDs isn't unique; other
	paths that don't use the tunnel might have IDs that
	are set by the source that collide with those assigned
	by the ingress, causing reassembly errors

- it creates inner fragments that interfere with arriving fragments
	i.e., it claims the IDs are unique, but this is true only
	for those it assigns; it does not attempt to monitor or
	drop collisions due to fragments that arrive with
	recently assigned IDs

>> When the DF is "ignored", the ID field is rewritten - i.e.,
> 
> If the ID field could be rewritten by intermediate entities,
> it is fine for intermediate routers to clear DF.

The counterexample is, as above:

	- when source-generated fragments can go around the rewriter

	- when other rewriters exist on other paths

Any time this sort of rewriting occurs, it might be safe if contained
inside a tunnel that "cleans up its mess", i.e., when it knows that only
its ingrees can generate fragments, and that the egress reassembles the
fragments and sets the DF=1.

Since that's not the case here, it's not safe.

Joe

From touch@isi.edu  Mon Jun 18 14:04:34 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5F0511E80CA for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 14:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.799
X-Spam-Level: 
X-Spam-Status: No, score=-103.799 tagged_above=-999 required=5 tests=[AWL=-1.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 AdNClM1YFe6e for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 14:04:34 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 11D9511E80BD for <ietf@ietf.org>; Mon, 18 Jun 2012 14:04:34 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q5IL3SFE009992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 Jun 2012 14:03:30 -0700 (PDT)
Message-ID: <4FDF97A0.5030701@isi.edu>
Date: Mon, 18 Jun 2012 14:03:28 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: gathering experience running WIFI
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 21:04:35 -0000

Hi, all,

There had been some talk of gathering experience at IETF meetings 
running WIFI, and I'm not sure it went anywhere.

Although this might not be appropriate for an RFC, I'm hoping to gather 
some relevant advice to put on a webpage that could be useful for future 
IETF meetings, as well as for meetings of other organizations (e.g., 
ACM, IEEE, etc.).

If anyone is interested in participating, please contact me directly. 
I'm presuming this list is NOT the best place to have this discussion, 
so please do not "reply all" here.

Thanks,

Joe

From touch@isi.edu  Mon Jun 18 15:44:44 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC2A911E80A0 for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 15:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 3+vD-UmMhmTB for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 15:44:43 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id D471E11E808F for <ietf@ietf.org>; Mon, 18 Jun 2012 15:44:43 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q5IMiPR0012655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 Jun 2012 15:44:25 -0700 (PDT)
Message-ID: <4FDFAF49.7070708@isi.edu>
Date: Mon, 18 Jun 2012 15:44:25 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: Protocol Definition
References: <4FDF0362.3050101@tana.it>
In-Reply-To: <4FDF0362.3050101@tana.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 22:44:44 -0000

On 6/18/2012 3:30 AM, Alessandro Vesely wrote:
...
> I noticed no disagreement between "method" and "mechanism", at the
> time.  In retrospect, those two terms might seem to allude to a
> different depth of semantic explanations.  Rereading that thread, I
> find that the same ambiguity holds for algorithm descriptions:  one
> can give a full description (or coding) of, say, sqrt, without
> actually saying that the square of the result will match its argument
> up to some rounding error.  The specification does not have to relate
> the underlying mathematical abstraction.

This is the difference between a behavioral description and a procedural 
description.

Behavioral treats a system as a "black box", and defines the system as a 
function and how it transforms its input into its output.

Procedural specifies the particular steps taken inside the box.

Procedural is more specific than behavioral:

	behavioral = any of a number of ways of calculating SQRT
	procedural = one specific algorithm for calculating SQRT

Semantics is a completely different thing - the assignment of "meaning" 
to symbols. Neither procedural nor behavioral descriptions need to 
include semantic descriptions.

> Protocol specifications, especially when dealing with policies, do not
> have to describe the exact meaning of the relevant tokens.  To do that
> would often look like mandating a state or a reaction, neither of
> which is needed to ensure interoperability.

In a protocol, state transitions and response messages are specified. 
Protocols are typically described procedurally, FWIW.

> In fact, the protocol
> just has to ensure that a policy can be transmitted correctly.  Many
> would rather leave a policy token underspecified than get involved in
> its details.

This is like claiming that a protocol is just "bits on the wire", and it 
is not accurate.

> In that respect, a protocol is not a complete method.  The "upper
> layer", where policies and politics are dealt with, seems to be too
> fuzzy to be specified.  I think this limitation is consistent with the
> etymological meaning of the term, that refers to forms of conduct that
> don't betray intentions.  Is that right?

Conduct, intention, and semantics refer to human interpretations of 
events. Unless a human is part of your protocol stack, they're not relevant.

I agree with AB - these issues aren't relevant to IETF descriptions of 
protocols.

Joe

From mohta@necom830.hpcl.titech.ac.jp  Mon Jun 18 17:59:09 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C15CB21F86BE for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 17:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.016
X-Spam-Level: 
X-Spam-Status: No, score=0.016 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 SiI2gz2BNmJ1 for <ietf@ietfa.amsl.com>; Mon, 18 Jun 2012 17:59:09 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id E63BB21F86B8 for <ietf@ietf.org>; Mon, 18 Jun 2012 17:59:08 -0700 (PDT)
Received: (qmail 23297 invoked from network); 19 Jun 2012 01:04:23 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 19 Jun 2012 01:04:23 -0000
Message-ID: <4FDFCE8D.8090403@necom830.hpcl.titech.ac.jp>
Date: Tue, 19 Jun 2012 09:57:49 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>, ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FC96ACA.9040800@isi.edu> <4FC97E57.6070505@necom830.hpcl.titech.ac.jp> <4FCEAB53.2020504@isi.edu> <4FDB12F2.6030808@necom830.hpcl.titech.ac.jp> <4FDB6843.6090107@isi.edu> <4FDBE75A.8090100@necom830.hpcl.titech.ac.jp> <4FDBEACA.4030701@isi.edu> <4FDC1F9C.2060808@necom830.hpcl.titech.ac.jp> <79E3C9F8-3A0F-4BD7-B018-A508D439ED57@isi.edu> <4FDF219D.5020201@necom830.hpcl.titech.ac.jp> <4FDF783F.2030104@isi.edu>
In-Reply-To: <4FDF783F.2030104@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 00:59:09 -0000

Joe Touch wrote:

>> While your draft is rather harmful than useless, I'm fine
>> if the following point of the draft:
>>
>>      >>   Originating sources MAY set the IPv4 ID field of atomic
>>      datagrams to any value.
>>
>> is changed to:
>>
>>      >>   Originating sources MUST set the IPv4 ID field of atomic
>>      datagrams to values as unique as possible.
>>
>> which is what the current BSD implementations do.
> 
> There are implementations that set DF=1 and ID=0 (cellphones).

They are broken implementations violating RFC791.

To quote from RFC1122:

   1.2  General Considerations

      There are two important lessons that vendors of Internet host
      software have learned and which a new vendor should consider
      seriously.


      1.2.2  Robustness Principle

         At every layer of the protocols, there is a general rule whose
         application can lead to enormous benefits in robustness and
         interoperability [IP:1]:

                "Be liberal in what you accept, and
                 conservative in what you send"


         The second part of the principle is almost as important:
         software on other hosts may contain deficiencies that make it
         unwise to exploit legal but obscure protocol features.  It is
         unwise to stray far from the obvious and simple, lest untoward
         effects result elsewhere.  A corollary of this is "watch out
         for misbehaving hosts"; host software should be prepared, not
         just to survive other misbehaving hosts, but also to cooperate
         to limit the amount of disruption such hosts can cause to the
         shared communication facility.

it is obvious that your draft violates the robustness principle.

> BSD does not make IDs as unique as possible; it selects them according
> to a pseudorandom algorithm that does not take into account the
> datagram's source IP, destination IP, or protocol. I.e., BSD code
> repeats the IDs more frequently than necessary when a host concurrently
> sources datagrams with different (srcIP, dstIP, proto) tuples.

You merely mean BSD code does not try to make ID unique for
the longest possible MSL and the fastest possible packet rate,
which is not my point.

As the uniqueness is broken at some MSL and rate anyway, the
current code is enough to be "as unique as possible".

						Masataka Ohta

From ajs@anvilwalrusden.com  Mon Jun 18 19:12:24 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB70C11E80EF; Mon, 18 Jun 2012 19:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 zVJyys1TpQ9T; Mon, 18 Jun 2012 19:12:24 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id D897C11E80D7; Mon, 18 Jun 2012 19:12:23 -0700 (PDT)
Received: from crankycanuck.ca (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 53BE91ECB41D; Tue, 19 Jun 2012 02:12:13 +0000 (UTC)
Date: Mon, 18 Jun 2012 22:12:11 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>, dnsext@ietf.org
Subject: Re: Gen-ART review of draft-ietf-dnsext-dnssec-bis-updates-18
Message-ID: <20120619021211.GI32683@crankycanuck.ca>
References: <EBFB2D2E-78FF-46D6-B4FF-1F57FB8D769B@bbn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EBFB2D2E-78FF-46D6-B4FF-1F57FB8D769B@bbn.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: draft-ietf-dnsext-dnssec-bis-updates@tools.ietf.org, IESG <iesg@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 02:12:24 -0000

Hi,

I'm the shepherd for this draft.  Thanks for the review.  Some
follow-up inline.

On Fri, May 25, 2012 at 05:02:28PM -0400, Richard L. Barnes wrote:
> 
> MAJOR:
> 
> 4.1.  
> It's not clear what the threat model is that this section is
> designed to address.  If the zone operator is malicious, then it can
> simulate the necessary zone cut and still prove the non-existence of
> records in the child zone.

The problem here is not a malicious parent operator, but "an NSEC or
NSEC3 RR from an ancestor zone".  In the original specification, an
attacker could use such an RR to prove the non-existence of some name
in a subordinate zone.  That was the problem.  (Remember, in DNS there
is a good chance that you are not talking to an authoritative server.)
If you have suggestions on ways to make that clearer, it'd be welcome.
The editors tried to come up with compact examples that would be
anything other than mystifying, and were unsuccessful.  

> 5.10.  
> I find the recommendation of the "Accept Any Success" policy
> troubling.  It deals very poorly with compromise (and other
> roll-over scenarios): Suppose there are two trust anchors, one for
> example.com and one for child.example.com.  If the private key
> corresponding to the TA for child.example.com is compromised, but
> the validator continues to trust it, this negates the benefit
> provided by the parent (example.com) facilitating a rollover.
> Suggest an alternative policy, "Highest Signer": Out of the set of
> keys configured as TAs, the validator only uses a key as a TA (for
> purposes of validation) if there does not exist a DNSSEC path from
> it to any other TA.  This policy seems like more work to enforce
> (because you have to do more backward chaining), but ISTM that the
> validator should have the necessary DNSSEC records anyway, so it's
> just a matter a couple of quick checks.

First, the Working Group debated this matter at considerable length,
several times.  The Accept Any Success policy provides greater
robustness in the face of configuration errors, and is more likely to
lead to continued resolution.  We believe, based on experience so far,
that such configuration errors are vastly more likely than key
compromise.  If we are to reopen this, we will need to go back to the
WG again.  

Note that Appendix C does discuss other options and 5.10 explicitly
suggests that this be configurable; but, because the biggest problem
we have is resolution failure in the face of mucked up configurations,
the consensus was that Accept Any Success was the best default.  That
could, of course, change in future, at which time an update to the
document would be advisable.

The suggestion for "Highest Signer" is interesting but has never to my
knowledge been previously mooted in relation to this draft.  I
therefore think that including it in particular would require some
review.  I don't know of any implementation that currently uses that
approach, either (but since there are vast gaps in my knowledge even
of what's on my desk, it wouldn't surprise me to learn that there were
some).  Do you know of any?  If not, it seems to me that it would be a
good idea to have some fielded experience with the approach before
recommending it as default.  It's an intriguing idea, however, and
seems to me to be worth pursuing.  I'm just not sure it should be in
this draft.  I personally think it would be premature to recommend it
as default, but if you take your position very firmly I am prepared to
take the question up with the Working Group.

Thanks again for the review.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From ron.even.tlv@gmail.com  Tue Jun 19 02:19:16 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03CDD21F8618; Tue, 19 Jun 2012 02:19:16 -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 IGQ-RRkv8ry0; Tue, 19 Jun 2012 02:19:11 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id D027421F860F; Tue, 19 Jun 2012 02:19:10 -0700 (PDT)
Received: by wibhn6 with SMTP id hn6so2235993wib.13 for <multiple recipients>; Tue, 19 Jun 2012 02:19:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=g0EcFfQrBnG3uPD774u0vmT2+lvD4+Ub2zDnXbZEWyk=; b=iltcSzC0ZYmpgYPjctDBqhtmvi+bvhCuU5eOlJPDEd8/+TQg7F5SwXAdcV6Mte0D7U FVN19SQdvjkbCXzyfGquOY122IShx42yO23NvLZgZCs4W3XCmUpgBSZFWQ2JrBtVCm2K HGLJHjK/HXJYa6o8KKSURBewhaQxlwyAT3b7foh9aIiX0yU8swHNumgg9BpisGWtepKx tDnMHDxpxiKZ5jo1jAryFZxQIs7nCPZOXLLbxx/ycKDy+LVgbr2o4jw5sLCiDUbHIZwt HPkUU4bW245HwqhGgu36mtgUN6SPGznwD4htBZ8rUUmT3JIKKgNVCHeC16ExZX4OAd5i Z7WQ==
Received: by 10.180.86.194 with SMTP id r2mr1643274wiz.15.1340097549696; Tue, 19 Jun 2012 02:19:09 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-177-104-121.red.bezeqint.net. [79.177.104.121]) by mx.google.com with ESMTPS id bn9sm31214527wib.5.2012.06.19.02.19.03 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Jun 2012 02:19:07 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Paul Sangster'" <Paul_Sangster@symantec.com>, <draft-ietf-nea-pt-tls.all@tools.ietf.org>
References: <4fcd272e.2968b40a.55d4.ffff9de3@mx.google.com> <6E79D623502C70419A9EAB18E4D274252B8B06102F@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
In-Reply-To: <6E79D623502C70419A9EAB18E4D274252B8B06102F@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
Subject: RE: GenART LC review of draft-ietf-nea-pt-tls-05
Date: Tue, 19 Jun 2012 12:16:19 +0300
Message-ID: <4fe0440b.6959b40a.7a49.6095@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0223_01CD4E15.57B56D80"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1Cl9xExNAkih6WSYeHA9SkXDOg7gG388dgASA4xdA=
Content-Language: en-us
Cc: gen-art@ietf.org, nea@ietf.org, 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 09:19:16 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0223_01CD4E15.57B56D80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

I am OK with your responses. The only thing I am not sure is about using PEN
0 defined in the registry.

 

Decimal

| Organization

| | Contact

| | | Email

| | | |

0

  Reserved

    Internet Assigned Numbers Authority

      iana&iana.org

 

I was wondering how this enterprise number should be specified since it
appears as "Reserved" in the registry. I have no specific suggestion

Roni

 

 

From: Paul Sangster [mailto:Paul_Sangster@symantec.com] 
Sent: Wednesday, June 13, 2012 7:56 PM
To: Roni Even; draft-ietf-nea-pt-tls.all@tools.ietf.org
Cc: 'IETF'; gen-art@ietf.org; nea@ietf.org
Subject: RE: GenART LC review of draft-ietf-nea-pt-tls-05

 

Thanks for the detailed review, comments are in-lined.

 

From: Roni Even [mailto:ron.even.tlv@gmail.com] 
Sent: Monday, June 04, 2012 2:20 PM
To: draft-ietf-nea-pt-tls.all@tools.ietf.org
Cc: 'IETF'; gen-art@ietf.org
Subject: GenART LC review of draft-ietf-nea-pt-tls-05

 

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-ietf-nea-pt-tls-05

Reviewer: Roni Even

Review Date:2012-6-4

IETF LC End Date: 2012-6-13

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

Major issues:

 

Minor issues:

1.       In section 3.2 "Therefore, this specification requests the IANA
reserve a TCP port number for use with the PT-TLS protocol upon publication
of this specification as an Internet standard RFC." I think it will  be
better to have here the assigned port number and instruct the RFC editor to
put the correct value.

 

[PS:] Ok, we can reword this in hopes of getting a particular value (race
condition with other upcoming RFCs).

 

2.       In section 3.4.2.2 last paragraph you summarize the text from
section 3.8 while in the paragraph above you provide the reference. Why do
you need the last paragraph if 3.8 is referenced.

 

[PS:] The goal of this section is to introduce and summarize the different
phases of PT-TLS.  We felt a brief discussion of the general message flow
was helpful to the reader to understand what occurs during this phase
(similar to what we did in the other sub-sections).  Your correct that this
information is covered later in more detail.

 

3.       In various places you refer to SMI 0 as IETF SMI number while
according to the table it is IANA SMI number.

 

[PS:] I presume this is about the PEN 0 being for the IETF.  Correct, it's
the IETF's name space that administered by the IANA.  What text would you
like to see to make this more clear?  Can we do it in one place, for example
stating that the IETF name space is administered by the IANA?

 

4.       I assume that all implementations MUST support message type vendor
ID 0. Is this mentioned?

 

[PS:] The purpose of this section was just to summarize and enumerate the
message types for vendor id 0.   I don't think it's a general rule that any
message type defined in the IETF (IANA J) name space must (or should be)
supported by all implementations.  It will vary depending on the purpose of
the message so that normative language is included in the descriptions of
the message.

 

5.       In section 3.5 and 6.1 you propose a policy of "Expert Review with
Specification Required ". I think that according to RFC5226 expert review is
implied if you select a specification required policy.

 

[PS:] I agree, it says "Specification Required also implies use of a
Designated Expert".  The policy is just "Specification Required" so we could
remove the "Expert Review with" and make it clear it's the Specification
Required IANA policy. 

 

6.       In section 3.6 on 9+ "Recipients of messages   of type 9 or higher
that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message
Type of a received PT-TLS message MUST respond with a Type Not Supported
PT-TLS error code in a PT-TLS Error message." I think this is true only for
Message Type Vendor ID 0.

 

[PS:] Thanks will reword this section to make it more clear.

 

7.       In 3.7.1 for Max vers and prefs ver you say that they MUST be set
to 1. I think it will be more correct here to say SHOULD since you explain
afterwards that they may have other values.

 

[PS:] I think this is a MUST.  The next sentence just points out that this
normative text might change in a future revision (which is not currently
planned).

 

8.       In section 3.7.2 "the recipient SHOULD send". Why not make it a
MUST here.

 

[PS:] I ok with making this change, let's see what others think .

 

9.       In section 3.7.2 "The version selected MUST be within the Min Vers
to Max Vers inclusive range sent in the Version Request   Message" I was
expecting to see pref ver here.

 

[PS:] Perf is just an informational (hint) preference.

 

10.   In section 3.8.3 " The SASL client authentication starts when the NEA
Server  enters the PT-TLS Negotiation phase and its policy indicates  that
an authentication of the NEA Client is necessary but was not performed
during the TLS handshake protocol " my read of  section 3.8 second paragraph
is that it can be done even if was done in the TLS handshake so the last
part of the sentence is not correct, if there is a policy you do it anyhow.
This comment is also for the third paragraph.

 

[PS:] Thanks, this was supposed to be an example.  Will fix these.

 

11.   In section 3.9 I noticed that you propose to send the entire original
message. Isn't it enough to send only the message identifier. This is based
on the last sentence of this section.

 

[PS:] Not "the entire original message" as its at most the first 1024 bytes
of the offending message.  This allows the recipient to either caches
recently sent messages and/or message identifiers when determining what
caused the error.  We thought this flexibility was useful and had very
little cost.

 

12.   Most of the text in section 6.1 repeats RFC5226 but in your words. Are
you trying to change some of RFC5226 text if not why write it in different
words?

 

[PS:] We were hoping to emphasize the aspects of 5226 that are most
important to this specification.  We weren't trying to change how the IANA
policy was interpreted.  Did you think we did so?  Is there a portion of
this text that is most troubling or was this just a question?

 

 

 

 

Nits/editorial comments:

 


------=_NextPart_000_0223_01CD4E15.57B56D80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2023900102;
	mso-list-type:hybrid;
	mso-list-template-ids:-625979886 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I am OK with your =
responses. The only thing I am not sure is about using PEN 0 defined in =
the registry.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Decimal<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>| =
Organization<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>| | =
Contact<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>| | | =
Email<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>| | | =
|<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New"'>0<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp; =
Reserved<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp; Internet Assigned Numbers =
Authority<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
iana&amp;iana.org<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I was wondering how this =
enterprise number should be specified since it appears as =
&quot;Reserved&quot; in the registry. I have no specific =
suggestion<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Paul Sangster [mailto:Paul_Sangster@symantec.com] <br><b>Sent:</b> =
Wednesday, June 13, 2012 7:56 PM<br><b>To:</b> Roni Even; =
draft-ietf-nea-pt-tls.all@tools.ietf.org<br><b>Cc:</b> 'IETF'; =
gen-art@ietf.org; nea@ietf.org<br><b>Subject:</b> RE: GenART LC review =
of draft-ietf-nea-pt-tls-05<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks for the detailed review, comments are =
in-lined&#8230;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Roni Even [<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Sent:</b> Monday, June 04, 2012 2:20 PM<br><b>To:</b> <a =
href=3D"mailto:draft-ietf-nea-pt-tls.all@tools.ietf.org">draft-ietf-nea-p=
t-tls.all@tools.ietf.org</a><br><b>Cc:</b> 'IETF'; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
GenART LC review of =
draft-ietf-nea-pt-tls-05<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
draft-ietf-nea-pt-tls-05<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;6&#8211;4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;6&#8211;13<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as a standard track =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.2 &#8220;Therefore, this specification requests the IANA reserve a TCP =
port number for use with the PT-TLS protocol upon publication of this =
specification as an Internet standard RFC.&#8221; I think it will&nbsp; =
be better to have here the assigned port number and instruct the RFC =
editor to put the correct value.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] Ok, we can reword this in hopes of getting a particular value =
(race condition with other upcoming =
RFCs).<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.4.2.2 last paragraph you summarize the text from section 3.8 while in =
the paragraph above you provide the reference. Why do you need the last =
paragraph if 3.8 is referenced.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] The goal of this section is to introduce and summarize the =
different phases of PT-TLS.&nbsp; We felt a brief discussion of the =
general message flow was helpful to the reader to understand what occurs =
during this phase (similar to what we did in the other =
sub-sections).&nbsp; Your correct that this information is covered later =
in more detail.<o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In various =
places you refer to SMI 0 as IETF SMI number while according to the =
table it is IANA SMI number.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] I presume this is about the PEN 0 being for the IETF.&nbsp; =
Correct, it&#8217;s the IETF&#8217;s name space that administered by the =
IANA. &nbsp;What text would you like to see to make this more =
clear?&nbsp; Can we do it in one place, for example stating that the =
IETF name space is administered by the =
IANA?<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I assume =
that all implementations MUST support message type vendor ID 0. Is this =
mentioned?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] The purpose of this section was just to summarize and enumerate =
the message types for vendor id 0.&nbsp; &nbsp;I don&#8217;t think =
it&#8217;s a general rule that any message type defined in the IETF =
(IANA </span></i></b><b><i><span =
style=3D'font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span></=
i></b><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>) name space must (or should be) supported by all =
implementations.&nbsp; It will vary depending on the purpose of the =
message so that normative language is included in the descriptions of =
the message.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.5 and 6.1 you propose a policy of &#8220;Expert Review with =
Specification Required &#8220;. I think that according to RFC5226 expert =
review is implied if you select a specification required =
policy.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] I agree, it says &#8220;Specification Required also implies use =
of a Designated Expert&#8221;.&nbsp; The policy is just =
&#8220;Specification Required&#8221; so we could remove the =
&#8220;Expert Review with&#8221; and make it clear it&#8217;s the =
Specification Required IANA policy. <o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText style=3D'margin-left:10.5pt'><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></i></b></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.6 on 9+ &#8220;Recipients of messages&nbsp;&nbsp; of type 9 or higher =
that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message =
Type of a received PT-TLS message MUST respond with a Type Not Supported =
PT-TLS error code in a PT-TLS Error message.&#8221; I think this is true =
only for Message Type Vendor ID 0.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] Thanks will reword this section to make it more =
clear.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In 3.7.1 =
for Max vers and prefs ver you say that they MUST be set to 1. I think =
it will be more correct here to say SHOULD since you explain afterwards =
that they may have other values.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] I think this is a MUST.&nbsp; The next sentence just points out =
that this normative text might change in a future revision (which is not =
currently planned).<o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.7.2 &#8220;the recipient SHOULD send&#8221;. Why not make it a MUST =
here.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] I ok with making this change, let&#8217;s see what others think =
&#8230;<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.7.2 &#8220;The version selected MUST be within the Min Vers to Max =
Vers inclusive range sent in the Version Request&nbsp;&nbsp; =
Message&#8221; I was expecting to see pref ver =
here.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] Perf is just an informational (hint) =
preference.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>10.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.8.3 &#8220; The SASL client authentication starts when the NEA =
Server&nbsp; enters the PT-TLS Negotiation phase and its policy =
indicates&nbsp; that an authentication of the NEA Client is necessary =
but was not performed during the TLS handshake protocol &#8220; my read =
of&nbsp; section 3.8 second paragraph is that it can be done even if was =
done in the TLS handshake so the last part of the sentence is not =
correct, if there is a policy you do it anyhow. This comment is also for =
the third paragraph.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] Thanks, this was supposed to be an example.&nbsp; Will fix =
these.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>11.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.9 I noticed that you propose to send the entire original message. =
Isn&#8217;t it enough to send only the message identifier. This is based =
on the last sentence of this section.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] Not &#8220;the entire original message&#8221; as its at most =
the first 1024 bytes of the offending message.&nbsp; This allows the =
recipient to either caches recently sent messages and/or message =
identifiers when determining what caused the error. &nbsp;We thought =
this flexibility was useful and had very little =
cost.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>12.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Most of =
the text in section 6.1 repeats RFC5226 but in your words. Are you =
trying to change some of RFC5226 text if not why write it in different =
words?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] We were hoping to emphasize the aspects of 5226 that are most =
important to this specification.&nbsp; We weren&#8217;t trying to change =
how the IANA policy was interpreted.&nbsp; Did you think we did =
so?&nbsp; Is there a portion of this text that is most troubling or was =
this just a question?<o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_0223_01CD4E15.57B56D80--


From abdussalambaryun@gmail.com  Tue Jun 19 03:39:47 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9C7F21F85F3 for <ietf@ietfa.amsl.com>; Tue, 19 Jun 2012 03:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 1j9WAZrEnKI8 for <ietf@ietfa.amsl.com>; Tue, 19 Jun 2012 03:39:46 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id BB78B21F85F2 for <ietf@ietf.org>; Tue, 19 Jun 2012 03:39:45 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so3679688vbb.31 for <ietf@ietf.org>; Tue, 19 Jun 2012 03:39:45 -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 :content-type; bh=SKVHYNvXeOivwFZ/CnsjG0hEfTjJ3b0gy84BeCxNP8w=; b=T1b7Gri2+PXcfdF3+A3xtI6MkRUBRk98WClJLwyj9tltWOy4sn7awoMwCtAwWVRXVf b21zjOoE5k+HddcPMr/iezldKECNPDwzTGiBM8FbcTRDCetQDGqO1ZWiiOy2rrUkTd/a Nk8xAyifNyrcXPFJAufn4sGoiFHrjt7h0jnhtYTt5Z1t2gbYspjUD3rTDdjr2VZqiexJ dKaP1MNshr1X2t+V7Gg4EJhFwc8T8d8uDD15WqSgylERW0atf8MOI9wBKcJjQAIgUDBd pu8eoeT40IClUTwAzquCKnvG3j2tm7bWLb9XzNCoSSKCxYjz5CJxUvzBV0f5T6cZ6sSn 7RrA==
MIME-Version: 1.0
Received: by 10.220.149.15 with SMTP id r15mr9445353vcv.1.1340102384947; Tue, 19 Jun 2012 03:39:44 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Tue, 19 Jun 2012 03:39:44 -0700 (PDT)
In-Reply-To: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com>
Date: Tue, 19 Jun 2012 12:39:44 +0200
Message-ID: <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org, melinda.shore@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 10:39:47 -0000

Hi Melinda, and All,

>This is consistent with how individual, non-WG documents are
>progressed in the IETF.  I don't see a conflict or discontinuity.

Conflict process if we consider the I-D process as a IETF process. It
is not consistent with the IETF procedures. It can be consistent if
the IESG amend the I-D submission-process or take my suggestions.

Yes I agree that non-WGs documents take different submission stream
than IETF-WGs documents. One is named non-IETF submission and the
other IETF submission streams (two only streams so far). In the I-D we
are discussing of [publishing the Tao of the IETF], the submission
stream was not refered to which of two submission streams. It is most
likely understood as a new second IETF submission stream (I may name
it IETF-Tao stream), because this I-D affect the community (it must be
a group production not an individual production).

Please note that:
1) The subject I-D obsoletes RFC4677 if approved. The RFC4677 is a
IETF WG's procedure overview.

2) RFC4677 is not a formal IETF process document but instead an
informational overview.

The IETF procedures are only done in the IETF WGs or IETF community,
how can an individual decide for the community!!! That is why we are
discussing it in a IETF-list, not in a non-WG-list.

AB
====================
On 6/17/12, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> The abstract mentions 'many people',  because many people may mean 4 to 10
> people. The annonced I-D lacks the method of discussion in the community
> (discussing such change), the draft mentions the input from any community
> individual to be accepted by editor and then approved by IESG, but does not
> mention the methodology of discussion between community members nor between
> editor and members, also no announcements of such updates mentioned in
> draft.
>
> suggest> amend in abstract the word 'many' to the word  'some', or mention
> like in the introduction the desire of community.
>
> suggest> to add> to the draft that a discussion group to discuss
> inputs/suggestions before the editors undertakes changes. The draft to
> specify the discussion ( may be either on-List or during the IETF
> meetings). I prefer to mention; the face-to-face IETF meeting discussion in
> this procedure issue.
>
> suggest> to add>  the announcement for last call of Tao changes by the
> IESG,
>
> suggest> replace in section2> line 7> The editor of the Tao decides which
> proposed changes should be submitted to the IESG for the next version of
> the Tao.
>
>      replace with> The editor of the Tao decides which proposed changes
> should be
>                           submitted to the IESG for the next version of the
> Tao after
>                           the community discussed the changes.
>
> suggest> A time period of updates to be made, and input from the community
> to be collected, and editor to submit to IESG. It will be helpful also to
>
>
> AB
> ==============
>
> On Fri, Jun 15, 2012 at 9:29 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Publishing the "Tao of the IETF" as a Web Page'
>>  <draft-hoffman-tao-as-web-page-02.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2012-07-13. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>   Discussion of the "Tao of the IETF" during 2012 made it clear that
>>   many people want the document published only as a web page, not as an
>>   RFC that needs to be periodically updated.  This document specifies
>>   how the Tao will be published as a web page.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>>
>

From vesely@tana.it  Tue Jun 19 04:20:02 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC5B21F85E5 for <ietf@ietfa.amsl.com>; Tue, 19 Jun 2012 04:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.418
X-Spam-Level: 
X-Spam-Status: No, score=-4.418 tagged_above=-999 required=5 tests=[AWL=0.301,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 0ja2Bx7j3uLa for <ietf@ietfa.amsl.com>; Tue, 19 Jun 2012 04:20:01 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 6C07C21F85C9 for <ietf@ietf.org>; Tue, 19 Jun 2012 04:20:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1340104798; bh=vy59P97R1EhWcCX+PEZoW91AKKdr1emHrMw8UmbfP6c=; l=3388; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=lDU1r02vb4FpILlEGUzabffDdCXBZFyVGPAmkWDl0ag5qHxkSVYN54asHhP3AJyr0 pHnkp2nPIbHa7DAegvCK8YFr61IxSJSKKIQYXDzNnk3oRgnycCHlDqWOF2iuX03Cjh RgdQZbBVIFyNqqiVHZ9RPa6UqeDAMO1G+opuyLLQ=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 19 Jun 2012 13:19:58 +0200 id 00000000005DC035.000000004FE0605E.00001E40
Message-ID: <4FE0605E.50004@tana.it>
Date: Tue, 19 Jun 2012 13:19:58 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Protocol Definition
References: <4FDF0362.3050101@tana.it> <4FDFAF49.7070708@isi.edu>
In-Reply-To: <4FDFAF49.7070708@isi.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 11:20:02 -0000

On Tue 19/Jun/2012 00:44:25 +0200 Joe Touch wrote:
> On 6/18/2012 3:30 AM, Alessandro Vesely wrote:
> ...
>> one can give a full description (or coding) of, say, sqrt, without
>> actually saying that the square of the result will match its argument
>> up to some rounding error.  The specification does not have to relate
>> the underlying mathematical abstraction.
> 
> This is the difference between a behavioral description and a
> procedural description.
> 
> Behavioral treats a system as a "black box", and defines the system as
> a function and how it transforms its input into its output.
> 
> Procedural specifies the particular steps taken inside the box.
> 
> Procedural is more specific than behavioral:
> 
>     behavioral = any of a number of ways of calculating SQRT
>     procedural = one specific algorithm for calculating SQRT
> 
> Semantics is a completely different thing - the assignment of
> "meaning" to symbols. Neither procedural nor behavioral descriptions
> need to include semantic descriptions.

We agree that including semantic descriptions is optional.  But what
is better?  For SQRT, I'd hold that a short, crispy reference to the
theoretical background may be useful and wouldn't harm.  For the
general case, I'm not sure.

>> Protocol specifications, especially when dealing with policies, do not
>> have to describe the exact meaning of the relevant tokens.  To do that
>> would often look like mandating a state or a reaction, neither of
>> which is needed to ensure interoperability.
> 
> In a protocol, state transitions and response messages are specified.

When they're part of the protocol proper, they are specified indeed.
Policy tweaks, however, live in some limbo.  For example, recursion
for DNS, access restrictions for HTTP, ADSP for SMTP.  Specifications
can hardly discuss such topics.  If they do, they get criticized for
interfering with deployment.  In addition, as policies typically
involve subjective considerations, it is quite rare to gather rough
consensus on any specific advice about them.

> Protocols are typically described procedurally, FWIW.

Yes.  And quite often a procedural description is the most accurate
way to reverse engineer the actual meaning of a message.  Policies
don't enjoy such practice.

>> In fact, the protocol just has to ensure that a policy can be
>> transmitted correctly.  Many would rather leave a policy token
>> underspecified than get involved in its details.
> 
> This is like claiming that a protocol is just "bits on the wire",
> and it is not accurate.

Well, it is not accurate to assume full knowledge about the policies
and their consequences.  Let me try and express that better below.

> Conduct, intention, and semantics refer to human interpretations of
> events. Unless a human is part of your protocol stack, they're not
> relevant.
> 
> I agree with AB - these issues aren't relevant to IETF descriptions of
> protocols.

Besides development, humans typically configure some implementations
of one or more protocols.  That is what makes protocols run, so it has
to be relevant to us.  Hostmasters who carry out that task are skilled
staff.  However, they have to infer the exact meaning of a policy
token by the wording of its definition and/or by trial and error,
neither of which seems to be formally adequate to me.  What am I missing?

From jason_livingood@cable.comcast.com  Tue Jun 19 07:28:46 2012
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED5721F852C for <ietf@ietfa.amsl.com>; Tue, 19 Jun 2012 07:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.631
X-Spam-Level: 
X-Spam-Status: No, score=-102.631 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4,  USER_IN_WHITELIST=-100]
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 8En+5phfU5xc for <ietf@ietfa.amsl.com>; Tue, 19 Jun 2012 07:28:45 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 93EDC21F84F0 for <ietf@ietf.org>; Tue, 19 Jun 2012 07:28:45 -0700 (PDT)
Received: from ([24.40.56.116]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.21786047; Tue, 19 Jun 2012 08:11:23 -0600
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.155]) by pacdcexhub03.cable.comcast.com ([fe80::5527:6d6b:29a7:f414%15]) with mapi id 14.02.0283.003; Tue, 19 Jun 2012 10:28:36 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: 2012 ISOC Board of Trustees Election Results (IETF List)
Thread-Topic: 2012 ISOC Board of Trustees Election Results (IETF List)
Thread-Index: AQHNTifSrvsSW1LNVkOC5spQYD6rsQ==
Date: Tue, 19 Jun 2012 14:28:35 +0000
Message-ID: <CC06040F.6576D%jason_livingood@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [24.40.56.165]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B28F8320415F8142B3E23B9812180998@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 14:28:46 -0000

On behalf of the Internet Society=B9s Election Committee, I wish to extend
our appreciation and thanks to all of the nominees and final candidates
for the Board of Trustees. We are quite honoured to have such
well-qualified people so interested in serving the Internet Society!

The election results were certified on 24 May 2012 and the challenge
period concluded 10 June 2012. The process ran smoothly and the Election
Committee does not have any issues or concerns to report. The new Trustees
will be seated at the Internet Society Board Meeting in Vancouver, Canada,
on 4 August 2012.

CHAPTERS
In the Chapter membership election, we had three candidates:
1. Gihan Dias
2. Sala Tamanikaiwaimaro
3. Rudi Vansnick

55 out of the 86 Chapters voted, which is a vote participation rate of
63.95%. In the previous election, the vote participation was 79.49%.

Rudy Vansnick received the highest number of the votes and has been
elected for a three-year term.

ORGANISATIONS
In the Organisation membership election, we had six candidates:
1. Keith Davidson
2. Marshall Eubanks
3. David Farber
4. Demi Getschko
5. Byron Holland
6. Bevil Wooding

52 of the 109 Organisation Members, or 47.71%, voted. They had the
opportunity to vote for up to two candidates, with votes weighted by the
class of membership. In the previous election the vote participation was
50.47%, on a group size of 107 organizations.

Keith Davidson and David Farber, receiving the largest weighted vote
counts, have been elected for three-year terms.

INTERNET ENGINEERING TASK FORCE (IETF)
Using the process documented in RFC 3677, the IAB has re-appointed Eric
Burger as the IETF appointee to the ISOC Board.

We congratulate all of the new and returning trustees and look forward to
working with them soon on the Board of Trustees. We also thank all
nominees and final candidates for their participation, as well as ISOC
staff for their support of this critical process.

Respectfully submitted,

Jason Livingood, Chair
Alain Aina and Theresa Swinehart, Election Committee Members








From rbarnes@bbn.com  Tue Jun 19 08:31:46 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F04821F8522; Tue, 19 Jun 2012 08:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 309x36VYmpwj; Tue, 19 Jun 2012 08:31:45 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 1558B21F8508; Tue, 19 Jun 2012 08:31:44 -0700 (PDT)
Received: from ros-dhcp192-1-51-6.bbn.com ([192.1.51.6]:54956) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Sh0OW-0004gM-WF; Tue, 19 Jun 2012 11:31:05 -0400
From: Richard L. Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11
Date: Tue, 19 Jun 2012 11:31:42 -0400
Message-Id: <D48790C9-D5B0-407E-A917-DC6D5BC42D9D@bbn.com>
To: ietf@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org, gen-art@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 15:31:46 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-nfsv4-federated-fs-admin-11
Reviewer: Richard Barnes
Review Date: Jun-19-2012
IETF LC End Date: Not known
IESG Telechat date: Jun-28-2012

Summary: Almost ready, couple of issues

MAJOR:=20

4. / 7.
This protocol allows for the provisioning of security information as =
part of the FedFsNsdbParams, in the form of a certificate to be used in =
verifying a TLS server certificate.  There are two notable issues with =
how the document does this now:
1. Section 4 does not adequately specify how the certificate in the =
FedFsNsdbParams should be used in the verification process.  Is it to be =
used as a trust anchor, so that any subordinate certificate is =
considered valid?  Or perhaps it is to be matched against the end-entity =
certificate.  In either case, it seems like it would be sufficient to =
provision a certificate fingerprint (or even a public key fingerprint) =
instead of the whole certificate.
2. In the security considerations, the document should discuss the =
implications of provisioning trust information in this way (depending on =
how it is used), and any requirements for security mechanisms to be used =
in these cases.


MINOR:

2.=20
It's not clear what the difference is between utf8string_cs and =
utf8string_cis.  Should you mention at some point that these MUST be =
UTF-8, even though the XDR won't enforce that?  (Say, at the beginning =
of Section 4?)

3.
It's not clear to me how FEDFS_ERR_PERM differs from FEDFS_ERR_ACCESS.  =
I don't see it called out for use anywhere in the procedure calls.  =
Perhaps this is a legacy of prior versions that should be deleted?


EDITORIAL:=20

3.=20
The definition of FEDFS_ERR_LOOP isn't actually related to looping.  It =
seems like this should either detect a loop (e.g., via a repeated name), =
or be renamed something like FEDFS_ERR_TOOMANYREFERS.

4. "The port is the NSDB transport port for the LDAP interface"
Suggest rewording to clarify that this is an LDAP/TCP port (I initially =
wondered if other transports could be used), e.g.:
"The port value in the FedFsNsdbName indicates the LDAP port on the =
NSDB"


From Paul_Sangster@symantec.com  Tue Jun 19 08:24:21 2012
Return-Path: <Paul_Sangster@symantec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD3211E808F; Tue, 19 Jun 2012 08:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 AoiOk4cvj95A; Tue, 19 Jun 2012 08:24:15 -0700 (PDT)
Received: from tus1smtoutpex02.symantec.com (tus1smtoutpex02.symantec.com [216.10.195.242]) by ietfa.amsl.com (Postfix) with ESMTP id D267021F8566; Tue, 19 Jun 2012 08:24:04 -0700 (PDT)
X-AuditID: d80ac3f2-b7f806d0000068dc-a0-4fe099945643
Received: from tus1opsmtapin02.ges.symantec.com (tus1opsmtapin02.ges.symantec.com [192.168.214.44]) by tus1smtoutpex02.symantec.com (Symantec Brightmail Gateway out) with SMTP id 55.26.26844.49990EF4; Tue, 19 Jun 2012 15:24:04 +0000 (GMT)
Received: from [155.64.220.138] (helo=TUS1XCHHUBPIN02.SYMC.SYMANTEC.COM) by tus1opsmtapin02.ges.symantec.com with esmtp (Exim 4.76) (envelope-from <Paul_Sangster@symantec.com>) id 1Sh0Hk-0001GD-0W; Tue, 19 Jun 2012 15:24:04 +0000
Received: from TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM ([155.64.220.150]) by TUS1XCHHUBPIN02.SYMC.SYMANTEC.COM ([172.24.185.246]) with mapi; Tue, 19 Jun 2012 08:24:04 -0700
From: Paul Sangster <Paul_Sangster@symantec.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-nea-pt-tls.all@tools.ietf.org" <draft-ietf-nea-pt-tls.all@tools.ietf.org>
Date: Tue, 19 Jun 2012 08:25:43 -0700
Subject: RE: GenART LC review of draft-ietf-nea-pt-tls-05
Thread-Topic: GenART LC review of draft-ietf-nea-pt-tls-05
Thread-Index: Ac1Cl9xExNAkih6WSYeHA9SkXDOg7gG388dgASA4xdAADb42MA==
Message-ID: <6E79D623502C70419A9EAB18E4D274252B8B2C397F@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
References: <4fcd272e.2968b40a.55d4.ffff9de3@mx.google.com> <6E79D623502C70419A9EAB18E4D274252B8B06102F@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM> <4fe0440b.6959b40a.7a49.6095@mx.google.com>
In-Reply-To: <4fe0440b.6959b40a.7a49.6095@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_6E79D623502C70419A9EAB18E4D274252B8B2C397FTUS1XCHEVSPIN_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNIsWRmVeSWpSXmKPExsVyYMU1Hd0pMx/4G2y+zm4x9+IEdourrz6z WDzbOJ/F4vPbCou/7cwOrB47Z91l91iy5CeTx5fLn9kCmKO4bFJSczLLUov07RK4Mp5Mvsxe sH4uU8WE6YsZGxi//mbsYuTkkBAwkbh8dx4bhC0mceHeeiCbi0NI4AOjxJ3dh9khnNeMEl2r mpkhnFWMEr/fLgRrZxMwkNh55BRYlYhAI6PE1yVzmEESzAJJEsdnbGABsVkEVCXW35zCDmIL C1hKTPk+CSwuImAlsfTDRCYI20niyrnjYDavQJTE3Om7oFbvYpRY8/QpWDOngIXExg23WEFs RqBjv59awwSxTFzi1pP5TBBPCEgs2XOeGcIWlXj5+B9UvajEnfb1jBD1+RIP1pxih1gmKHFy 5hOWCYxis5CMmoWkbBaSMoi4jsSC3Z/YIGxtiWULXzPD2GcOPGZCFl/AyL6KUaaktNiwOLck v7SkILXCwEivuDI3ERjByXrJ+bmbGIFRfIPr8KcdjDeWKh5iFOBgVOLh3TDpgb8Qa2IZUOUh RgkOZiUR3roZQCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8H3Zv9RcSSE8sSc1OTS1ILYLJMnFw SjUwTvO/mqp7O39hgQfrf+aqiQt1Qu0NZRetP2zSfOsJU3XDpjcHZ9kei3OJ7T/B/Lp2XdrV dSdXOP5/xXf55sPca523a9SKnKdUbWleKGJZrLBRZz1r1UTpx/P3CrWkdVwWF9vJFvDY4lyB uuxL4faQHFHH8Fe7FQzMg8L59j9+kME0w3jJW1EjJZbijERDLeai4kQAludT5d4CAAA=
X-Mailman-Approved-At: Tue, 19 Jun 2012 08:57:07 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "nea@ietf.org" <nea@ietf.org>, 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 15:24:21 -0000

--_000_6E79D623502C70419A9EAB18E4D274252B8B2C397FTUS1XCHEVSPIN_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

NEA has 2 existing RFCs (PA and PB protocols) that use the PEN of 0 in exac=
tly the same way as PT-TLS.  One option might be to change "Reserved" to "R=
eserved for IETF Use".
From: Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: Tuesday, June 19, 2012 2:16 AM
To: Paul Sangster; draft-ietf-nea-pt-tls.all@tools.ietf.org
Cc: 'IETF'; gen-art@ietf.org; nea@ietf.org
Subject: RE: GenART LC review of draft-ietf-nea-pt-tls-05

Hi,
I am OK with your responses. The only thing I am not sure is about using PE=
N 0 defined in the registry.

Decimal
| Organization
| | Contact
| | | Email
| | | |
0
  Reserved
    Internet Assigned Numbers Authority
      iana&iana.org

I was wondering how this enterprise number should be specified since it app=
ears as "Reserved" in the registry. I have no specific suggestion
Roni


From: Paul Sangster [mailto:Paul_Sangster@symantec.com]
Sent: Wednesday, June 13, 2012 7:56 PM
To: Roni Even; draft-ietf-nea-pt-tls.all@tools.ietf.org
Cc: 'IETF'; gen-art@ietf.org; nea@ietf.org
Subject: RE: GenART LC review of draft-ietf-nea-pt-tls-05

Thanks for the detailed review, comments are in-lined...

From: Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: Monday, June 04, 2012 2:20 PM
To: draft-ietf-nea-pt-tls.all@tools.ietf.org<mailto:draft-ietf-nea-pt-tls.a=
ll@tools.ietf.org>
Cc: 'IETF'; gen-art@ietf.org<mailto:gen-art@ietf.org>
Subject: GenART LC review of draft-ietf-nea-pt-tls-05

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.



Document: draft-ietf-nea-pt-tls-05

Reviewer: Roni Even

Review Date:2012-6-4

IETF LC End Date: 2012-6-13

IESG Telechat date:



Summary: This draft is almost ready for publication as a standard track RFC=
.



Major issues:



Minor issues:

1.       In section 3.2 "Therefore, this specification requests the IANA re=
serve a TCP port number for use with the PT-TLS protocol upon publication o=
f this specification as an Internet standard RFC." I think it will  be bett=
er to have here the assigned port number and instruct the RFC editor to put=
 the correct value.



[PS:] Ok, we can reword this in hopes of getting a particular value (race c=
ondition with other upcoming RFCs).



2.       In section 3.4.2.2 last paragraph you summarize the text from sect=
ion 3.8 while in the paragraph above you provide the reference. Why do you =
need the last paragraph if 3.8 is referenced.



[PS:] The goal of this section is to introduce and summarize the different =
phases of PT-TLS.  We felt a brief discussion of the general message flow w=
as helpful to the reader to understand what occurs during this phase (simil=
ar to what we did in the other sub-sections).  Your correct that this infor=
mation is covered later in more detail.



3.       In various places you refer to SMI 0 as IETF SMI number while acco=
rding to the table it is IANA SMI number.



[PS:] I presume this is about the PEN 0 being for the IETF.  Correct, it's =
the IETF's name space that administered by the IANA.  What text would you l=
ike to see to make this more clear?  Can we do it in one place, for example=
 stating that the IETF name space is administered by the IANA?



4.       I assume that all implementations MUST support message type vendor=
 ID 0. Is this mentioned?



[PS:] The purpose of this section was just to summarize and enumerate the m=
essage types for vendor id 0.   I don't think it's a general rule that any =
message type defined in the IETF (IANA :)) name space must (or should be) s=
upported by all implementations.  It will vary depending on the purpose of =
the message so that normative language is included in the descriptions of t=
he message.



5.       In section 3.5 and 6.1 you propose a policy of "Expert Review with=
 Specification Required ". I think that according to RFC5226 expert review =
is implied if you select a specification required policy.



[PS:] I agree, it says "Specification Required also implies use of a Design=
ated Expert".  The policy is just "Specification Required" so we could remo=
ve the "Expert Review with" and make it clear it's the Specification Requir=
ed IANA policy.



6.       In section 3.6 on 9+ "Recipients of messages   of type 9 or higher=
 that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message T=
ype of a received PT-TLS message MUST respond with a Type Not Supported PT-=
TLS error code in a PT-TLS Error message." I think this is true only for Me=
ssage Type Vendor ID 0.



[PS:] Thanks will reword this section to make it more clear.



7.       In 3.7.1 for Max vers and prefs ver you say that they MUST be set =
to 1. I think it will be more correct here to say SHOULD since you explain =
afterwards that they may have other values.



[PS:] I think this is a MUST.  The next sentence just points out that this =
normative text might change in a future revision (which is not currently pl=
anned).



8.       In section 3.7.2 "the recipient SHOULD send". Why not make it a MU=
ST here.



[PS:] I ok with making this change, let's see what others think ...



9.       In section 3.7.2 "The version selected MUST be within the Min Vers=
 to Max Vers inclusive range sent in the Version Request   Message" I was e=
xpecting to see pref ver here.



[PS:] Perf is just an informational (hint) preference.



10.   In section 3.8.3 " The SASL client authentication starts when the NEA=
 Server  enters the PT-TLS Negotiation phase and its policy indicates  that=
 an authentication of the NEA Client is necessary but was not performed dur=
ing the TLS handshake protocol " my read of  section 3.8 second paragraph i=
s that it can be done even if was done in the TLS handshake so the last par=
t of the sentence is not correct, if there is a policy you do it anyhow. Th=
is comment is also for the third paragraph.



[PS:] Thanks, this was supposed to be an example.  Will fix these.



11.   In section 3.9 I noticed that you propose to send the entire original=
 message. Isn't it enough to send only the message identifier. This is base=
d on the last sentence of this section.



[PS:] Not "the entire original message" as its at most the first 1024 bytes=
 of the offending message.  This allows the recipient to either caches rece=
ntly sent messages and/or message identifiers when determining what caused =
the error.  We thought this flexibility was useful and had very little cost=
.



12.   Most of the text in section 6.1 repeats RFC5226 but in your words. Ar=
e you trying to change some of RFC5226 text if not why write it in differen=
t words?



[PS:] We were hoping to emphasize the aspects of 5226 that are most importa=
nt to this specification.  We weren't trying to change how the IANA policy =
was interpreted.  Did you think we did so?  Is there a portion of this text=
 that is most troubling or was this just a question?









Nits/editorial comments:


--_000_6E79D623502C70419A9EAB18E4D274252B8B2C397FTUS1XCHEVSPIN_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2023900102;
	mso-list-type:hybrid;
	mso-list-template-ids:-625979886 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>NEA has 2 existing RFCs (PA and PB protocols) that use the PE=
N of 0 in exactly the same way as PT-TLS.&nbsp; One option might be to chan=
ge &#8220;Reserved&#8221; to &#8220;Reserved for IETF Use&#8221;.<o:p></o:p=
></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;padding:=
0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'margin-botto=
m:0in;margin-bottom:.0001pt;line-height:normal'><b><span style=3D'font-size=
:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even [mailto:ron.e=
ven.tlv@gmail.com] <br><b>Sent:</b> Tuesday, June 19, 2012 2:16 AM<br><b>To=
:</b> Paul Sangster; draft-ietf-nea-pt-tls.all@tools.ietf.org<br><b>Cc:</b>=
 'IETF'; gen-art@ietf.org; nea@ietf.org<br><b>Subject:</b> RE: GenART LC re=
view of draft-ietf-nea-pt-tls-05<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'color=
:#1F497D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'colo=
r:#1F497D'>I am OK with your responses. The only thing I am not sure is abo=
ut using PEN 0 defined in the registry.<o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:n=
ormal'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>Decimal<o=
:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:0in;margin-=
bottom:.0001pt;line-height:normal'><span style=3D'font-size:10.0pt;font-fam=
ily:"Courier New"'>| Organization<o:p></o:p></span></p><p class=3DMsoNormal=
 style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span=
 style=3D'font-size:10.0pt;font-family:"Courier New"'>| | Contact<o:p></o:p=
></span></p><p class=3DMsoNormal style=3D'margin-bottom:0in;margin-bottom:.=
0001pt;line-height:normal'><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New"'>| | | Email<o:p></o:p></span></p><p class=3DMsoNormal style=3D'm=
argin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New"'>| | | |<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-hei=
ght:normal'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>0<o:=
p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:0in;margin-b=
ottom:.0001pt;line-height:normal'><span style=3D'font-size:10.0pt;font-fami=
ly:"Courier New"'>&nbsp; Reserved<o:p></o:p></span></p><p class=3DMsoNormal=
 style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span=
 style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;&nbsp; In=
ternet Assigned Numbers Authority<o:p></o:p></span></p><p class=3DMsoNormal=
 style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span=
 style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; iana&amp;iana.org<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><=
span style=3D'color:#1F497D'>I was wondering how this enterprise number sho=
uld be specified since it appears as &quot;Reserved&quot; in the registry. =
I have no specific suggestion<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorm=
al><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'=
border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><d=
iv style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0i=
n 0in'><p class=3DMsoNormal style=3D'margin-bottom:0in;margin-bottom:.0001p=
t;line-height:normal'><b><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-famil=
y:"Tahoma","sans-serif"'> Paul Sangster [mailto:Paul_Sangster@symantec.com]=
 <br><b>Sent:</b> Wednesday, June 13, 2012 7:56 PM<br><b>To:</b> Roni Even;=
 draft-ietf-nea-pt-tls.all@tools.ietf.org<br><b>Cc:</b> 'IETF'; gen-art@iet=
f.org; nea@ietf.org<br><b>Subject:</b> RE: GenART LC review of draft-ietf-n=
ea-pt-tls-05<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>Thanks for =
the detailed review, comments are in-lined&#8230;<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>=
<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;paddin=
g:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'margin-bottom:0in;margin=
-bottom:.0001pt;line-height:normal'><b><span style=3D'font-size:10.0pt;font=
-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.=
0pt;font-family:"Tahoma","sans-serif"'> Roni Even [<a href=3D"mailto:ron.ev=
en.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>] <br><b>Sent:</b> Monda=
y, June 04, 2012 2:20 PM<br><b>To:</b> <a href=3D"mailto:draft-ietf-nea-pt-=
tls.all@tools.ietf.org">draft-ietf-nea-pt-tls.all@tools.ietf.org</a><br><b>=
Cc:</b> 'IETF'; <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br=
><b>Subject:</b> GenART LC review of draft-ietf-nea-pt-tls-05<o:p></o:p></s=
pan></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMs=
oNormal>I am the assigned Gen-ART reviewer for this draft. For background o=
n Gen-ART, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p><p class=3DMsoNormal>Please resolve these comments along=
 with any other Last Call comments you may receive.<o:p></o:p></p><p class=
=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: draft-ietf-=
nea-pt-tls-05<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: Roni Even<o:p=
></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif"'>Review Date:2012&#8211;6&#8211;4<o:p></o=
:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif"'>IETF LC End Date: 2012&#8211;6&#8211;13<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif"'>IESG Telechat date:<o:p></o:p></span></p>=
<p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: This=
 draft is almost ready for publication as a standard track RFC.<o:p></o:p><=
/span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainT=
ext><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Maj=
or issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif"'>Minor issues:<o:p></o:p></span></p><p class=3DMsoPlainTe=
xt style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><!=
[if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif"'><span style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Ti=
mes New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><=
![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"=
'>In section 3.2 &#8220;Therefore, this specification requests the IANA res=
erve a TCP port number for use with the PT-TLS protocol upon publication of=
 this specification as an Internet standard RFC.&#8221; I think it will&nbs=
p; be better to have here the assigned port number and instruct the RFC edi=
tor to put the correct value.<o:p></o:p></span></p><p class=3DMsoPlainText>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS=
:] Ok, we can reword this in hopes of getting a particular value (race cond=
ition with other upcoming RFCs).<o:p></o:p></span></i></b></p><p class=3DMs=
oPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=
=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !sup=
portLists]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f"'><span style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In sec=
tion 3.4.2.2 last paragraph you summarize the text from section 3.8 while i=
n the paragraph above you provide the reference. Why do you need the last p=
aragraph if 3.8 is referenced.<o:p></o:p></span></p><p class=3DMsoPlainText=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[P=
S:] The goal of this section is to introduce and summarize the different ph=
ases of PT-TLS.&nbsp; We felt a brief discussion of the general message flo=
w was helpful to the reader to understand what occurs during this phase (si=
milar to what we did in the other sub-sections).&nbsp; Your correct that th=
is information is covered later in more detail.<o:p></o:p></span></i></b></=
p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
PlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 l=
fo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif"'><span style=3D'mso-list:Ignore'>3.<span style=3D'font:7.=
0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><=
/span><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif"'>In various places you refer to SMI 0 as IETF SMI number while acco=
rding to the table it is IANA SMI number.<o:p></o:p></span></p><p class=3DM=
soPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-ser=
if";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><=
i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'>[PS:] I presume this is about the PEN 0 being for the IETF.&nbsp; =
Correct, it&#8217;s the IETF&#8217;s name space that administered by the IA=
NA. &nbsp;What text would you like to see to make this more clear?&nbsp; Ca=
n we do it in one place, for example stating that the IETF name space is ad=
ministered by the IANA?<o:p></o:p></span></i></b></p><p class=3DMsoPlainTex=
t><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=3D'margi=
n-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists=
]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span=
 style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New Roman"'>&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I assume that a=
ll implementations MUST support message type vendor ID 0. Is this mentioned=
?<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.=
0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></sp=
an></p><p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>[PS:] The purpose of this secti=
on was just to summarize and enumerate the message types for vendor id 0.&n=
bsp; &nbsp;I don&#8217;t think it&#8217;s a general rule that any message t=
ype defined in the IETF (IANA </span></i></b><b><i><span style=3D'font-size=
:11.0pt;font-family:Wingdings;color:#1F497D'>J</span></i></b><b><i><span st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>)=
 name space must (or should be) supported by all implementations.&nbsp; It =
will vary depending on the purpose of the message so that normative languag=
e is included in the descriptions of the message.<o:p></o:p></span></i></b>=
</p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DM=
soPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1=
 lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif"'><span style=3D'mso-list:Ignore'>5.<span style=3D'font:=
7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span=
></span><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif"'>In section 3.5 and 6.1 you propose a policy of &#8220;Expert Rev=
iew with Specification Required &#8220;. I think that according to RFC5226 =
expert review is implied if you select a specification required policy.<o:p=
></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></=
p><p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-family=
:"Calibri","sans-serif";color:#1F497D'>[PS:] I agree, it says &#8220;Specif=
ication Required also implies use of a Designated Expert&#8221;.&nbsp; The =
policy is just &#8220;Specification Required&#8221; so we could remove the =
&#8220;Expert Review with&#8221; and make it clear it&#8217;s the Specifica=
tion Required IANA policy. <o:p></o:p></span></i></b></p><p class=3DMsoPlai=
nText style=3D'margin-left:10.5pt'><b><i><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></i=
></b></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25=
in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>6=
.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; </span></span></span><![endif]><span style=3D'font-size:11.0pt;font=
-family:"Calibri","sans-serif"'>In section 3.6 on 9+ &#8220;Recipients of m=
essages&nbsp;&nbsp; of type 9 or higher that do not support the PT-TLS Mess=
age Type Vendor ID and PT-TLS Message Type of a received PT-TLS message MUS=
T respond with a Type Not Supported PT-TLS error code in a PT-TLS Error mes=
sage.&#8221; I think this is true only for Message Type Vendor ID 0.<o:p></=
o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font=
-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><=
p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-family:"C=
alibri","sans-serif";color:#1F497D'>[PS:] Thanks will reword this section t=
o make it more clear.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=3D'margin-=
left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span s=
tyle=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times New Roman"'>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In 3.7.1 for Max =
vers and prefs ver you say that they MUST be set to 1. I think it will be m=
ore correct here to say SHOULD since you explain afterwards that they may h=
ave other values.<o:p></o:p></span></p><p class=3DMsoPlainText><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'font-s=
ize:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] I think =
this is a MUST.&nbsp; The next sentence just points out that this normative=
 text might change in a future revision (which is not currently planned).<o=
:p></o:p></span></i></b></p><p class=3DMsoPlainText><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-=
.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore=
'>8.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; </span></span></span><![endif]><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif"'>In section 3.7.2 &#8220;the recipient SH=
OULD send&#8221;. Why not make it a MUST here.<o:p></o:p></span></p><p clas=
s=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText=
><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#1F497D'>[PS:] I ok with making this change, let&#8217;s see what othe=
rs think &#8230;<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=3D'margin-left:=
.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style=
=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 3.7.2 &#82=
20;The version selected MUST be within the Min Vers to Max Vers inclusive r=
ange sent in the Version Request&nbsp;&nbsp; Message&#8221; I was expecting=
 to see pref ver here.<o:p></o:p></span></p><p class=3DMsoPlainText><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] Perf=
 is just an informational (hint) preference.<o:p></o:p></span></i></b></p><=
p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPla=
inText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2=
'><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif"'><span style=3D'mso-list:Ignore'>10.<span style=3D'font:7.0p=
t "Times New Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 3.8.3 =
&#8220; The SASL client authentication starts when the NEA Server&nbsp; ent=
ers the PT-TLS Negotiation phase and its policy indicates&nbsp; that an aut=
hentication of the NEA Client is necessary but was not performed during the=
 TLS handshake protocol &#8220; my read of&nbsp; section 3.8 second paragra=
ph is that it can be done even if was done in the TLS handshake so the last=
 part of the sentence is not correct, if there is a policy you do it anyhow=
. This comment is also for the third paragraph.<o:p></o:p></span></p><p cla=
ss=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainTex=
t><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'>[PS:] Thanks, this was supposed to be an example.&nbsp; Will=
 fix these.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:=
p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;=
text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'ms=
o-list:Ignore'>11.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;=
 </span></span></span><![endif]><span style=3D'font-size:11.0pt;font-family=
:"Calibri","sans-serif"'>In section 3.9 I noticed that you propose to send =
the entire original message. Isn&#8217;t it enough to send only the message=
 identifier. This is based on the last sentence of this section.<o:p></o:p>=
</span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p cl=
ass=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'>[PS:] Not &#8220;the entire original messag=
e&#8221; as its at most the first 1024 bytes of the offending message.&nbsp=
; This allows the recipient to either caches recently sent messages and/or =
message identifiers when determining what caused the error. &nbsp;We though=
t this flexibility was useful and had very little cost.<o:p></o:p></span></=
i></b></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p cla=
ss=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>12.<span style=
=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span></span><![endi=
f]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Most=
 of the text in section 6.1 repeats RFC5226 but in your words. Are you tryi=
ng to change some of RFC5226 text if not why write it in different words?<o=
:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>[PS:] We were hoping to emphasize =
the aspects of 5226 that are most important to this specification.&nbsp; We=
 weren&#8217;t trying to change how the IANA policy was interpreted.&nbsp; =
Did you think we did so?&nbsp; Is there a portion of this text that is most=
 troubling or was this just a question?<o:p></o:p></span></i></b></p><p cla=
ss=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainTex=
t><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>=
&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.=
0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p clas=
s=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editorial com=
ments:<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
></div></div></div></body></html>=

--_000_6E79D623502C70419A9EAB18E4D274252B8B2C397FTUS1XCHEVSPIN_--

From abdussalambaryun@gmail.com  Wed Jun 20 03:51:38 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0E4721F8738; Wed, 20 Jun 2012 03:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 8vjhZpwM9Ycu; Wed, 20 Jun 2012 03:51:38 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9955421F861C; Wed, 20 Jun 2012 03:51:37 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so4263769vcq.31 for <multiple recipients>; Wed, 20 Jun 2012 03:51:37 -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=wpPSoaOiu4cIZDZbRgBku7E2hiTQEJlg+cs/x/ewn7U=; b=WCToj5D4uN+OhVhJjYZMjY9fd9JJY2sYWUH58Pjx+Cuvm3DeZf6FnRq0HpEWNIpER1 lmG2UOBPAhBXD0EaYypn+fNNXmM0EgZxzox20FNOFI5caovyyqdHZ7yx1Gsbw3FD5sN1 0J+DQ5f01iD63lxRYdbFNS+kWH3U5aTo/7i+13JkL//ofs+ngtG95x9b9OElfpcyM2uJ JXlmGfXnq5QWx1wlRDBEB3YWz7xVdrOcoq71/qqmMEGXZ+iIAFsytlpZnQYnysR2mxLv fIk8+0rvKfVNlOpKCbD5LMPVz8GCbk1iT9ec2alcZVThstbAL9IxU/zABjR0yBzPqhHu hjkg==
MIME-Version: 1.0
Received: by 10.52.100.4 with SMTP id eu4mr9220262vdb.66.1340189496993; Wed, 20 Jun 2012 03:51:36 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Wed, 20 Jun 2012 03:51:36 -0700 (PDT)
In-Reply-To: <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com>
Date: Wed, 20 Jun 2012 12:51:36 +0200
Message-ID: <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org, melinda.shore@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 10:51:38 -0000

I got a request to clarify (language and reference) my message:

> Conflict process if we consider the I-D process as a IETF process. It
> is not consistent with the IETF procedures. It can be consistent if
> the IESG amend the I-D submission-process or take my suggestions.

 I refere to the IETF process of: preparing the I-D by WG,
Community-accepting, Submitting, and IESG-approval. The new
Tao-update-process of the draft is not including the community. The
IETF process in draft is as : individual preparing, individual submit
to Editor, Editor decides and accepts, Editor submitting, and
IESG-approval.

The above are two different IETF submission streams, which may be
consistent if we include *the community* in accepting submission to
IESG.

====================

RFC4844>section 4.1.3>

4.1.3. Process Change
>From time to time, it may be necessary to change the approval
processes for any given stream, or even add or remove streams. This
may occur when the RFC Editor, the IAB, the body responsible for a
given stream of documents, or the community determines that there are
issues to be resolved in general for RFC approval or for per-stream
approval processes.
In this framework, the general approach is that the IAB will work
with the RFC Editor and other parties to get community input and it
will verify that any changes appropriately account for community
requirements.

RFC4844>section 5>
The subsections below identify the streams that exist today. There
is no immediate expectation of new streams being created and it is
preferable that new streams NOT be created. Creation of streams and
all policies surrounding general changes to the RFC Series are
discussed above in Section 4.

5.1. RFC Approval Processes
5.1.1. IETF Document Stream
5.1.2. IAB Document Stream
5.1.3. IRTF Document Stream
5.1.4. Independent Submission Stream

===========================

To understand IETF procedures of processes and document-streams I
refer you to sections 4 and 5 in [RFC4844], and section 4 in [RFC5378]
, may read also RFC5741, RFC5742, and FC2418.

However, if you still don't understand my language or if I
misunderstood, please advise/comment :)

Regards
AB

+++++++++++++++++++++++++++++++++++

On 6/19/12, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> Hi Melinda, and All,
>
>>This is consistent with how individual, non-WG documents are
>>progressed in the IETF.  I don't see a conflict or discontinuity.
>
> Conflict process if we consider the I-D process as a IETF process. It
> is not consistent with the IETF procedures. It can be consistent if
> the IESG amend the I-D submission-process or take my suggestions.
>
> Yes I agree that non-WGs documents take different submission stream
> than IETF-WGs documents. One is named non-IETF submission and the
> other IETF submission streams (two only streams so far). In the I-D we
> are discussing of [publishing the Tao of the IETF], the submission
> stream was not refered to which of two submission streams. It is most
> likely understood as a new second IETF submission stream (I may name
> it IETF-Tao stream), because this I-D affect the community (it must be
> a group production not an individual production).
>
> Please note that:
> 1) The subject I-D obsoletes RFC4677 if approved. The RFC4677 is a
> IETF WG's procedure overview.
>
> 2) RFC4677 is not a formal IETF process document but instead an
> informational overview.
>
> The IETF procedures are only done in the IETF WGs or IETF community,
> how can an individual decide for the community!!! That is why we are
> discussing it in a IETF-list, not in a non-WG-list.
>
> AB
> ====================
> On 6/17/12, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
>> The abstract mentions 'many people',  because many people may mean 4 to
>> 10
>> people. The annonced I-D lacks the method of discussion in the community
>> (discussing such change), the draft mentions the input from any community
>> individual to be accepted by editor and then approved by IESG, but does
>> not
>> mention the methodology of discussion between community members nor
>> between
>> editor and members, also no announcements of such updates mentioned in
>> draft.
>>
>> suggest> amend in abstract the word 'many' to the word  'some', or
>> mention
>> like in the introduction the desire of community.
>>
>> suggest> to add> to the draft that a discussion group to discuss
>> inputs/suggestions before the editors undertakes changes. The draft to
>> specify the discussion ( may be either on-List or during the IETF
>> meetings). I prefer to mention; the face-to-face IETF meeting discussion
>> in
>> this procedure issue.
>>
>> suggest> to add>  the announcement for last call of Tao changes by the
>> IESG,
>>
>> suggest> replace in section2> line 7> The editor of the Tao decides which
>> proposed changes should be submitted to the IESG for the next version of
>> the Tao.
>>
>>      replace with> The editor of the Tao decides which proposed changes
>> should be
>>                           submitted to the IESG for the next version of
>> the
>> Tao after
>>                           the community discussed the changes.
>>
>> suggest> A time period of updates to be made, and input from the
>> community
>> to be collected, and editor to submit to IESG. It will be helpful also to
>>
>>
>> AB
>> ==============
>>
>> On Fri, Jun 15, 2012 at 9:29 PM, The IESG <iesg-secretary@ietf.org>
>> wrote:
>>
>>>
>>> The IESG has received a request from an individual submitter to consider
>>> the following document:
>>> - 'Publishing the "Tao of the IETF" as a Web Page'
>>>  <draft-hoffman-tao-as-web-page-02.txt> as Informational RFC
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2012-07-13. Exceptionally, comments may
>>> be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>   Discussion of the "Tao of the IETF" during 2012 made it clear that
>>>   many people want the document published only as a web page, not as an
>>>   RFC that needs to be periodically updated.  This document specifies
>>>   how the Tao will be published as a web page.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page/ballot/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>>
>>>
>>
>

From sm@resistor.net  Wed Jun 20 08:45:20 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1589A21F86B6 for <ietf@ietfa.amsl.com>; Wed, 20 Jun 2012 08:45:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 wCgjGxbTF1RU for <ietf@ietfa.amsl.com>; Wed, 20 Jun 2012 08:45:17 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8851221F86B4 for <ietf@ietf.org>; Wed, 20 Jun 2012 08:45:17 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5KFj8iw004001; Wed, 20 Jun 2012 08:45:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1340207112; i=@resistor.net; bh=03pTrfOU3+4wIWeMonjBVmAlMf5svVQtmnSjE2GjmBU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=peIG8obTbCwKRcN6iAnndRF8y2Yl0n0jajh9mfChhoRXHL+mOnT9UncfDXEMlJUzQ wqdgWIDPCI95wsycxCUAWtvXNinUeZay5FRjl8I8DrEQmfzKAHbddGybX/TnN/bUwd 8upRvYy81MwRQ03MFaUUkQhMH+scUK3vLx5mRCno=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1340207112; i=@resistor.net; bh=03pTrfOU3+4wIWeMonjBVmAlMf5svVQtmnSjE2GjmBU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PNquEG8weiSFmojekO18/sdOzL2WJtLzCuCs9+z3bKfErg0XSR4cJns/Xg+Rs8inJ FNDnadQEcHlEc3lpAKMMMpkyXwkUOXQgGaaWkHo6RSIf9IWr12vDPBOMD0qeMDGz3A as1URn8JqspbyXTnElb6xHtTTnIt9lVL4TbUSdoM=
Message-Id: <6.2.5.6.2.20120620072437.0ad66a00@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 20 Jun 2012 08:39:56 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
In-Reply-To: <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.g mail.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 15:45:20 -0000

Hi Abdussalam,
At 03:51 20-06-2012, Abdussalam Baryun wrote:
>  I refere to the IETF process of: preparing the I-D by WG,
>Community-accepting, Submitting, and IESG-approval. The new
>Tao-update-process of the draft is not including the community. The
>IETF process in draft is as : individual preparing, individual submit
>to Editor, Editor decides and accepts, Editor submitting, and
>IESG-approval.
>
>The above are two different IETF submission streams, which may be
>consistent if we include *the community* in accepting submission to
>IESG.

RFC 4844 discusses about RFC Series and the streams used by the 
various communities to publish a RFC.  One of those streams is for 
IETF Documents.  In the I-D being discussed, the document will be 
published on a web page.  The IESG will choose Paul Hoffman as the 
editor.  I gather that those details are not a problem.

draft-hoffman-tao-as-web-page-02 mentions that the changes will be 
discussed on an open, Tao-specific mailing list.  The second 
paragraph of Section 2 and the third paragraph are not so clear about 
changes, i.e. the editor accepts proposed changes and the IESG 
accepts proposed changes.  Are you suggesting that the changes should 
be discussed in a Working Group or something else?

BTW, RFC 4677 should be moved to Historic instead of Obsolete.

Regards,
-sm 


From paul.hoffman@vpnc.org  Wed Jun 20 09:25:36 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A1521F86EC for <ietf@ietfa.amsl.com>; Wed, 20 Jun 2012 09:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 iXdAdfwPkw7Z for <ietf@ietfa.amsl.com>; Wed, 20 Jun 2012 09:25:35 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 558AF21F86E4 for <ietf@ietf.org>; Wed, 20 Jun 2012 09:25:35 -0700 (PDT)
Received: from [10.20.30.101] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q5KGPUrr041672 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 20 Jun 2012 09:25:31 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <6.2.5.6.2.20120620072437.0ad66a00@resistor.net>
Date: Wed, 20 Jun 2012 09:25:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F4E6FDD-33F9-4383-9DB0-9F6B17D9A5D9@vpnc.org>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1278)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 16:25:36 -0000

On Jun 20, 2012, at 8:39 AM, SM wrote:

> RFC 4844 discusses about RFC Series and the streams used by the =
various communities to publish a RFC.  One of those streams is for IETF =
Documents.  In the I-D being discussed, the document will be published =
on a web page.  The IESG will choose Paul Hoffman as the editor.  I =
gather that those details are not a problem.

Errr, maybe. The IESG could easily choose someone else; many individuals =
in this community would be fine at being the Tao editor. Remember, I was =
the third editor of the document.

> draft-hoffman-tao-as-web-page-02 mentions that the changes will be =
discussed on an open, Tao-specific mailing list.  The second paragraph =
of Section 2 and the third paragraph are not so clear about changes, =
i.e. the editor accepts proposed changes and the IESG accepts proposed =
changes. =20

Can you say what was "not so clear"? I absolutely want that bit to be =
clear. Proposed text is appreciated here.

> BTW, RFC 4677 should be moved to Historic instead of Obsolete.


Earlier versions of the Tao were made obsolete, not moved to Historic, =
so I thought it was most appropriate to do that here as well. FWIW, the =
definition of "Historic" in RFC 2026 is for specifications, not =
descriptive documents like the Tao.

--Paul Hoffman


From sm@resistor.net  Wed Jun 20 12:12:28 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3894821F8644 for <ietf@ietfa.amsl.com>; Wed, 20 Jun 2012 12:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level: 
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 KE-WVUZwVBfn for <ietf@ietfa.amsl.com>; Wed, 20 Jun 2012 12:12:24 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 284C421F8643 for <ietf@ietf.org>; Wed, 20 Jun 2012 12:12:24 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5KJBaT1003603; Wed, 20 Jun 2012 12:11:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1340219542; i=@resistor.net; bh=ri4fAXsXaW8cWfPgZubDig1TSr/nOndI0Cspozb8OcE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UYOLrkV6ZTgVN2fjNAz3NGvA1dLr6jhAkbtxDQdYU/cEOL9YF+zWXpxmZZ+PqyDFT GBHlqDm6GuXDEe7U90wGrwej7WhuMtx3nrfXJyt3WD09nK1w2Obs2sxsquwvyA8Nct sM2OR3d6JE09O6NDuXj7qhSKkNSoZEREMKKIWqF4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1340219542; i=@resistor.net; bh=ri4fAXsXaW8cWfPgZubDig1TSr/nOndI0Cspozb8OcE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=DfsxSXuqtMlrbiFqgqbCY2kefsmHyVX0rEOWtJ1+0MbJOM8Qb4yDmRpxridz2mwi9 1+HTD0BsLXeqJ2FkLuh/kslXeBWo4h7kxKsPzLGnPUSWilK9FJQXqZYtAtVH0Er3si a84PrkSbyW0SNZpo5cgTDOUUR5CYoE30qL+57uzY=
Message-Id: <6.2.5.6.2.20120620104822.0a7158c8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 20 Jun 2012 12:02:08 -0700
To: Paul Hoffman <paul.hoffman@vpnc.org>
From: SM <sm@resistor.net>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
In-Reply-To: <8F4E6FDD-33F9-4383-9DB0-9F6B17D9A5D9@vpnc.org>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <8F4E6FDD-33F9-4383-9DB0-9F6B17D9A5D9@vpnc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 19:12:28 -0000

Hi Paul,
At 09:25 20-06-2012, Paul Hoffman wrote:
>Errr, maybe. The IESG could easily choose someone else; many 
>individuals in this community would be fine at being the Tao editor. 
>Remember, I was the third editor of the document.

Yes. :-)

>Can you say what was "not so clear"? I absolutely want that bit to 
>be clear. Proposed text is appreciated here.

I would not put too many administrative details in a RFC as it will 
be read literally.  Here's  some suggested text which I'll leave to 
author discretion:

    The Tao will be edited by one person who is chosen by the IESG.
    The changes can be discussed on the tao-discuss@ietf.org mailing list.
    The editor submits the revised version of the Tao to the IESG for approval.
    The revised version is published by the IETF Secretariat at
    <http://www.ietf.org/tao.html>.

What was not clear is the how changes make it into the 
document.  Instead of using two steps, you could keep the URL above 
as the stable one and use your discretion for the editing part.  I 
removed the tao-possible-revision.html as "we" do not want to see a 
RFP where the IETF gets billed for such work. :-)   The editor can 
work out some details such as automatically picking changes from SVN 
and pushing it to some work-in-progress web page with the IETF 
Secretariat.  I did not mention "community" in the above.  Feel free 
to add that.  There is some overhead in the above.  As people will 
probably get bored after a while, it should be less work.

>Earlier versions of the Tao were made obsolete, not moved to 
>Historic, so I thought it was most appropriate to do that here as 
>well. FWIW, the definition of "Historic" in RFC 2026 is for 
>specifications, not descriptive documents like the Tao.

RFC 2026 is the alternate reality of the IETF.  It's convenient to 
cite it every now and then.  If the IESG asks, you could tell it that 
the information in FYI 17 is simply and obviously obsolete and fits 
its published "statement" for Historic.  I take it that nobody would 
refer anyone to RFC 4677 except for historical reasons.

I'll +0 the draft to avoid changing the state of consensus.

Regards,
-sm 


From mohta@necom830.hpcl.titech.ac.jp  Wed Jun 20 17:58:07 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B213211E80A0 for <ietf@ietfa.amsl.com>; Wed, 20 Jun 2012 17:58:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level: 
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 rHkbpBvamI7w for <ietf@ietfa.amsl.com>; Wed, 20 Jun 2012 17:58:07 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id C94CE11E8079 for <ietf@ietf.org>; Wed, 20 Jun 2012 17:58:06 -0700 (PDT)
Received: (qmail 71234 invoked from network); 21 Jun 2012 01:04:07 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 21 Jun 2012 01:04:07 -0000
Message-ID: <4FE2715C.2090601@necom830.hpcl.titech.ac.jp>
Date: Thu, 21 Jun 2012 09:57:00 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4FC9585E.6010205@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 00:58:07 -0000

Though the ID states:

   This
   document underscores the point that not only is reassembly (and
   possibly subsequent fragmentation) required for translation, it can
   be used to avoid issues with IPv4 ID uniqueness.

according to RFC2765, which does not need port numbers for
address mapping:

   If the IPv6 packet contains a Fragment header the header fields are
   set as above with the following exceptions:

         Identification:
                 Copied from the low-order 16-bits in the
                 Identification field in the Fragment header.

         Flags:
                 The More Fragments flag is copied from the M flag in
                 the Fragment header.  The Don't Fragments flag is set
                 to zero allowing this packet to be fragmented by IPv4
                 routers.

the translated IPv4 packets are not atomic with 16bit IDs.

Note that the RFC is referred by NAT646 etc.

Then, aren't IPv6 nodes are required to rate limit packets
they generate with fragment headers assuming 16bit IDs?

Or, are 6 to 4 translators are required to rate limit and
drop rate-violating packets to make the "stateless"
translators full of states.

Or?

						Masataka Ohta

PS

As the RFC specifies ID=0 when DF is set 0, it should also
be updated to conform to the robustness principle.

From abdussalambaryun@gmail.com  Thu Jun 21 02:17:02 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1552021F8532 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 02:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 WHPb10qM38zF for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 02:17:01 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 19DCA21F852E for <ietf@ietf.org>; Thu, 21 Jun 2012 02:17:00 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so229068vcq.31 for <ietf@ietf.org>; Thu, 21 Jun 2012 02:17:00 -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=gkCl7eBt91VTrTTX2/t4FhzZ9aL+lUwCbtNppUz7Dqg=; b=AIgt4G7KuJRsQ9XFnL/ZQMp7LJ1B36CCSG3RQ/BxBenfdSMaOtTVxQOoo4ONKkAhcM L0xOUptPqmc/alrt4CmkdNj7ZcIS/KDE6FSXUEAiZLuHWlg3xH1WrIRpWLmpy8riOnMY S3f4YY/EpHXXQYPgNtLNDoE1KjNgGwbUJr4NdMksZdF0zTpyoIFYVP5/0FN8+ZTMFbC2 nGfctfW52W3RBxVmrghXs5a2vd9vIdDRv6iE73C7sHWVIdT9sNZMZLMSsyU2vlt6Wjzb w3Q7hqbIlzx7olPvr3GHlFsuLhqU7pKxYRZXsxCitt1nqkDVV5/EN5d5o7n/9m+dLWLy 4p/A==
MIME-Version: 1.0
Received: by 10.52.100.4 with SMTP id eu4mr10727813vdb.66.1340270220430; Thu, 21 Jun 2012 02:17:00 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Thu, 21 Jun 2012 02:16:59 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120620072437.0ad66a00@resistor.net>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net>
Date: Thu, 21 Jun 2012 11:16:59 +0200
Message-ID: <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 09:17:02 -0000

Hi SM,

I thank you for your comments and input,

The I-D being discussed (draft-hoffman-tao-as-web-page-02), does
mention the discussion on a list, but it does not mention the
community or consensus. The point of this I-D is to make the process
easier and valuable for users and memebrs, so I don't suggest to make
such discussion on the list mandatory for this webpage process.

> RFC 4844 discusses about RFC Series and the streams used by the
> various communities to publish a RFC.  One of those streams is for
> IETF Documents.

Please note that the milestone/aim of the I-D and the webpage is to
produce a RFC in the end of its progress. I think the webpage is a
IETF document published and edited differently than IETF-drafts. So
RFC4844 should be considered. Furthermore the I-D avoids to reference
or mention IETF procedure documents (mentions obslete documents), I
don't know why?

>  In the I-D being discussed, the document will be
> published on a web page.  The IESG will choose Paul Hoffman as the
> editor.  I gather that those details are not a problem.

The problem is not choosing editor, but the webpage process. The Tao
webpage is a document but the question was is this document an IETF
document or a non-IETF document. Under the procedure IETF-documents
have a process. The <draft-hoffman-tao-as-web-page-02> draft has a
different process even though it is an IETF-document. The draft if
approved will Obsletes RFC4677 (this document went through IETF
process, and will be replaced by webpage with different process) so
the only reference is the webpage and its progress is through new
stream of Tao-process.

>  Are you suggesting that the changes should
> be discussed in a Working Group or something else?

I suggested the below message:

http://www.ietf.org/mail-archive/web/ietf/current/msg73750.html

I think that discussions should be limited times (in hours or few
days) which I prefer to take place in the IETF meetings and getting a
community consesus on the updates of the webpage. Because if we have
all individual-submissions with discussions and consensus of working
group then it will be disaster not making things easier. That is why I
suggest Editor acceptance with community consesus, and limited
discussions to solve the purpose of this I-D.

> BTW, RFC 4677 should be moved to Historic instead of Obsolete.

I agree with this suggestions.

Regards,
AB

++++++++++++++++++++++++++++++++++++++++++++++++++++++
On 6/20/12, SM <sm@resistor.net> wrote:
> Hi Abdussalam,
> At 03:51 20-06-2012, Abdussalam Baryun wrote:
>>  I refere to the IETF process of: preparing the I-D by WG,
>>Community-accepting, Submitting, and IESG-approval. The new
>>Tao-update-process of the draft is not including the community. The
>>IETF process in draft is as : individual preparing, individual submit
>>to Editor, Editor decides and accepts, Editor submitting, and
>>IESG-approval.
>>
>>The above are two different IETF submission streams, which may be
>>consistent if we include *the community* in accepting submission to
>>IESG.
>
> RFC 4844 discusses about RFC Series and the streams used by the
> various communities to publish a RFC.  One of those streams is for
> IETF Documents.  In the I-D being discussed, the document will be
> published on a web page.  The IESG will choose Paul Hoffman as the
> editor.  I gather that those details are not a problem.
>
> draft-hoffman-tao-as-web-page-02 mentions that the changes will be
> discussed on an open, Tao-specific mailing list.  The second
> paragraph of Section 2 and the third paragraph are not so clear about
> changes, i.e. the editor accepts proposed changes and the IESG
> accepts proposed changes.  Are you suggesting that the changes should
> be discussed in a Working Group or something else?
>
> BTW, RFC 4677 should be moved to Historic instead of Obsolete.
>
> Regards,
> -sm
>
>

From abdussalambaryun@gmail.com  Thu Jun 21 03:34:54 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0A5621F859B for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 03:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 RNhCryr6nHmm for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 03:34:54 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6130121F8599 for <ietf@ietf.org>; Thu, 21 Jun 2012 03:34:54 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so266297vbb.31 for <ietf@ietf.org>; Thu, 21 Jun 2012 03:34:53 -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=FZ/Y5W9qYQFQQwWfnapdnsDNe3DEjiVBByIWwmPDudg=; b=AQG5VugRebKLem+TepK3EwKlfhNPpO3IyscO2uP/fO0U576nOzErj6qYLefD8zff/P cjV0mknwel88BjnQCrkPp2gepQumd56t0n6ZlqpP7A3o0uk+0A14URY/JIVd845rNQRg YPIofhGxX1cUnux38ajAtjp3CYm2/B5P5o3rqCjJnbO5SmI1/2tu+9c8lNG6vb37itQt vgcriy3GhTPOHrAd8ylYbhdsBqS81lxTpkwLQwQlTxbPFMrVa3IMo7MthU395/1RgTNe Ks3yfspmaMgPLSwi3RF8xx5FRVgXjDdzYMvVnlYmJboY6LNrES1YAIxd8+H4FwLu7RrI 7u2w==
MIME-Version: 1.0
Received: by 10.220.149.15 with SMTP id r15mr13416031vcv.1.1340274893561; Thu, 21 Jun 2012 03:34:53 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Thu, 21 Jun 2012 03:34:53 -0700 (PDT)
In-Reply-To: <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com>
Date: Thu, 21 Jun 2012 12:34:53 +0200
Message-ID: <CADnDZ8-01L10ywMfW=2N90AnQRv2U3Vhp=qgJtpRL5KAgC=8XQ@mail.gmail.com>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: SM <sm@resistor.net>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 10:34:55 -0000

Hi All

Discussing the draft <draft-hoffman-tao-as-web-page-02>

>Can you say what was "not so clear"? I absolutely want that bit to be clear. Proposed text is appreciated here.

-Why the document/draft does not mention/reference other descriptive
related works?

-Why the document/draft obsoletes RFC4677, is there a big reason?

-Why is the document/draft not clear of its aim, objectives,
sub-process-periods, and update-announcement-procedure?

In the introduction>
[This document contains the procedure agreed to by the IESG. The Tao
has traditionally been an IETF consensus document,..]
-Why the document/draft in section 2 does not mention consesus while
mentioned in introduction.

-Why the document/draft does not include section about the Tao-list
and this discussion method and purposes.

-Why the document/draft has one section after the introduction,
avoiding important sections like in RFC2418 (WG procedures) or as:
       a) Roles of Tao-webpage update.
       b) Roles of Individual submission to Editor.
       c) The community input to the webpage.
       d) What is the Editor criteria of accepting and refusing such updates.

>Earlier versions of the Tao were made obsolete, not moved to Historic, so I thought it was most appropriate to do that here as well. FWIW, the definition of "Historic" in RFC 2026 is for specifications, not descriptive documents like the Tao.

Yes the early versions were obsoleted by a new RFC, not obsoleted by
RFC-that-references-webpage. I am not against the webpage, but against
to obsolete RFC4677. There should be a way to make one Tao RFC alive
while having the webpage. Maybe this I-D can update RFC4677 to add the
possibility of both RFC and webpage.

>I'll +0 the draft to avoid changing the state of consensus.

I agree and want the *consesus* and *community* input to be clear in the draft

I hope my message language is good/ok to understand, if not please
advise and I will send another clarification,

Regards
AB
==================================================

From abdussalambaryun@gmail.com  Thu Jun 21 13:00:17 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB2321F8742 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 13:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 SvmM4+jBZCWP for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 13:00:16 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6306121F862F for <ietf@ietf.org>; Thu, 21 Jun 2012 13:00:16 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so602148vcq.31 for <ietf@ietf.org>; Thu, 21 Jun 2012 13:00:15 -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 :content-type; bh=T7JghJFBp3ElVtD6GzevNmJoqGpEzFjS3XkKnP49r3g=; b=d/KlGIwswr9vpQjb7Mi+ZeooxgqgguuJ28AsROYmevypCXmj+m3M00BONe7sPqQ0Du VTUXHMgUmYPirOjJ/0X0OD0XtNPGzCmK+Gk6MIVOAX3aZqwpt8/J40V7ZbU9oLmgsNII qlMIg5/xA62VqA+0hzrdHNMXlCNWuV9wEhvaB6doRBY9BaiDlyBPeM6cwGpYzs3lVdZJ D15A3aLWTPORKCfh67isRd6Gf8GaqvLk7yNqMdHgdIAnJApDumL7JWJsC4cxHCZPM78o AO7iXpkTzMM18iCp0zMw/rtKz2yeHM08nbaq828T5AewMxF1JfGR4PBf3FYlfiEQCy96 WRHw==
MIME-Version: 1.0
Received: by 10.220.140.193 with SMTP id j1mr14410099vcu.4.1340308815648; Thu, 21 Jun 2012 13:00:15 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Thu, 21 Jun 2012 13:00:15 -0700 (PDT)
In-Reply-To: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com>
References: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com>
Date: Thu, 21 Jun 2012 22:00:15 +0200
Message-ID: <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com>
Subject: Re: Protocol Definition
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 20:00:17 -0000

I got help from a friend, to amend the definition statement to:

All protocols in IETF are based on the Internet or/and the IP.

AB
++++
<Defining any protocol has to consider somehow it's networks>


On 6/18/12, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> IMO the important issue in any definition is to include how the IETF
> defines protocol,
> this may be find in some RFCs :)
>
> The IP is the main protocol, and all protocols in IETF are based on IP
> and Internet.
>
> AB

From melinda.shore@gmail.com  Thu Jun 21 13:03:01 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B18F121F8503 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 13:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.339
X-Spam-Level: 
X-Spam-Status: No, score=-3.339 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, 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 jwyBy+jgKwCe for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 13:03:00 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id BF9D421F84FB for <ietf@ietf.org>; Thu, 21 Jun 2012 13:02:59 -0700 (PDT)
Received: by dacx6 with SMTP id x6so1384639dac.31 for <ietf@ietf.org>; Thu, 21 Jun 2012 13:02:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bSGzQYUBzulMb4fC7VrGYq9X6urjJryohZoA7BmfcTQ=; b=yFii9hrqHRl7//teqnfXh/aUfzAL0juwK9caPZ6LYGJ7cLQfQilKZHJJWnfi4wGcnW Ht7e45Smk6UsjMLDuubuDdgzBHGbaOt1xwIx2vsW18wcae4R7em5yqOMNkby2u2IuMkQ l2Z8XhY+afHI/ohPLtPgsSmWgXnlRHVbaDFZRVEgPwp3mBHnzvNb/TVoXcdPBqB2H81S a8SacbNVfkCrXHbEigq0P3KQNO6TX43GSVHqA4ankoWLBz9YOR4prAJ7fddRUe5byrEe cDmUfRKjVnbPh5LGB+c5DEilOm1fXy7FbEDPqgEb4mSg7l+TOt12Ha4EifaGImMBDFe5 Wd8g==
Received: by 10.68.226.226 with SMTP id rv2mr1778176pbc.101.1340308979559; Thu, 21 Jun 2012 13:02:59 -0700 (PDT)
Received: from spandex.local (216-67-47-144-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.47.144]) by mx.google.com with ESMTPS id of1sm36570227pbb.15.2012.06.21.13.02.58 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Jun 2012 13:02:58 -0700 (PDT)
Message-ID: <4FE37DF1.2080407@gmail.com>
Date: Thu, 21 Jun 2012 12:02:57 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com>
In-Reply-To: <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 20:03:02 -0000

On 6/21/12 1:16 AM, Abdussalam Baryun wrote:
> I think that discussions should be limited times (in hours or few
> days) which I prefer to take place in the IETF meetings and getting a
> community consesus on the updates of the webpage.

Hi: if you're concerned about and familiar with community process
then surely you're aware that work is progressed and decisions made
on mailing lists - right?

Melinda

From housley@vigilsec.com  Thu Jun 21 14:08:43 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0699821F867B for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 14:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.538
X-Spam-Level: 
X-Spam-Status: No, score=-102.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 e8u+XfkJ3q1H for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 14:08:42 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 6670421F8679 for <ietf@ietf.org>; Thu, 21 Jun 2012 14:08:42 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 2040FF2403B for <ietf@ietf.org>; Thu, 21 Jun 2012 17:09:09 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id QRZp4ENmxfh5 for <ietf@ietf.org>; Thu, 21 Jun 2012 17:08:30 -0400 (EDT)
Received: from [192.168.2.110] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 982EDF2403A for <ietf@ietf.org>; Thu, 21 Jun 2012 17:09:07 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4FE37DF1.2080407@gmail.com>
Date: Thu, 21 Jun 2012 17:08:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F96B6701-F6FF-41C1-BF81-81A00C76C450@vigilsec.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com> <4FE37DF1.2080407@gmail.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 21:08:43 -0000

This URL <http://www.ietf.org/tao> will bring up the current document.  =
It works exactly the same as <http://www.ietf.org/tao.html>.

This means that <http://www.ietf.org/tao/archive> cannot be used as =
suggested on this thread.

I propose the following URLs for the Tao:

   - current Tao: <http://www.ietf.org/tao.html>

   - draft Tao: <http://www.ietf.org/tao-possible-revision.html>

   - archive entries: =
<http://www.ietf.org/tao-archive/tao-YYYYMMDD.html>

Russ=

From chair@ietf.org  Thu Jun 21 15:10:13 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74E9021F854F; Thu, 21 Jun 2012 15:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 K-KwzCxtsm7N; Thu, 21 Jun 2012 15:10:13 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 8C81821F854A; Thu, 21 Jun 2012 15:10:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 8A89512C97A; Thu, 21 Jun 2012 15:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6dPSUbZCu672; Thu, 21 Jun 2012 15:10:12 -0700 (PDT)
Received: from [192.168.2.110] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) by c8a.amsl.com (Postfix) with ESMTPSA id 18C9412C970; Thu, 21 Jun 2012 15:10:12 -0700 (PDT)
Subject: Proposed Update to Note Well
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com>
Date: Thu, 21 Jun 2012 18:10:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org>
References: <4FCF5B92.3070703@qualcomm.com> <4FCF5F99.3060807@cisco.com> <4FCF6BD5.7080503@qualcomm.com> <4FCF8471.2050701@cisco.com> <AEF1278E-68D1-47D3-932A-8B4940E864A0@harvard.edu> <4FD0679D.60304@cisco.com> <4FD068BC.5050405@cs.tcd.ie> <CAP0PwYZb87zRv0HpTES1twLnnTWUk9ft80bupUoB5f62P3eL=A@mail.gmail.com> <4FD0A53A.6010406@innovationslab.net> <4FD0AAA5.3060400@cisco.com> <C07B527F-37D1-4340-BF7D-F1B6BD263726@gmail.com> <4FD0B3A1.7090001@qualcomm.com> <4FD0B3FA.90704@qualcomm.com> <CAP0PwYYjbaHqkk7z5dXBB4kcH=NhT5_MofHFpwpgXnXvBG_tKQ@mail.gmail.com> <4FD0B86E.8020008@qualcomm.com> <CALaySJKSzsgpmxaiTsHMAEBJNTyPGScMnsfTM=rbMiMEUREb6w@mail.gmail.com> <BD3F594E-0ED1-4079-836F-5D7F5D63AD91@harvard.edu> <CAP0PwYam-arXn1vYebn16d7b_paD7P9ZwKhG1aYgCo2yxuUWaQ@mail.gmail.com> <4FD0F8C5.8000100@qualcomm.com> <4FD10927.8020906@qualcomm.com> <CALaySJ+cMTbcsQQXTa4xhxS+0jBHah4XBXuHEeo4+i2iv1cRVg@mail.gmail.com> <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com>
To: IETF <ietf@ietf.org>, IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 22:10:13 -0000

The IESG has heard many complaints that the Note Well is too complex.  =
After some discussion with counsel, we propose the following updated =
Note Well for your comment and review.  The below summary would be =
followed with a pointer to or text of more details, which will depend =
upon whether it's a meeting slide, on the web site, on the registration =
page, or on a mailing-list greeting.

On behalf of the IESG,
  Russ Housley
  IETF Chair

--------------------------------------

NOTE WELL

In summary:

   By participating with the IETF, you agree to follow IETF processes.

   If you write, say, or discuss anything in the IETF, formally or =
informally,
   (all of which we call "a contribution") that you know is covered by a =
patent
   or patent application you or your employer own, one of you must =
disclose
   that.

   You understand that meetings might be recorded and broadcast.

This would be followed with a pointer to or text of more details,
which will depend upon whether it's a meeting slide, on the web site,
on the registration page, or on a mailing-list greeting.


From sm@resistor.net  Thu Jun 21 15:21:03 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71B3011E809A for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 15:21:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 vwYy7Of63Tuk for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 15:21:02 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F61111E808E for <ietf@ietf.org>; Thu, 21 Jun 2012 15:21:02 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5LMKorQ007725; Thu, 21 Jun 2012 15:20:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1340317255; i=@resistor.net; bh=ppDPE17DPE+uXkWQZk22vUBZwwr4RftSKvBwFDN3Sys=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=v+mKe/lGYnViB6M9aqI2zGO6KBaj4UHB/D7Swf/Q5CTQH5w0urFeplGrcy4vlYt6v XjZYKXdhoAXD0X5KLZALwKnUe7gKOEBET8Ux6mGNFYO1uOW3gZhmYIlwu9VXCQUG5X Qq+T3d8IkdyGXPIXCdWAyX/+apEmscVbhsi3zY6w=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1340317255; i=@resistor.net; bh=ppDPE17DPE+uXkWQZk22vUBZwwr4RftSKvBwFDN3Sys=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=oP7yxT/poST4uDXnlphGILT7Y/94z5+Qo/3+nAT4CsvNd4NncumWGiTQYRJnHj0my uW7t6Unk0tJD8gK9JDL9z99s7AkecxdpHgCHmEQ7ZcZk3/SyKg1fQY9X6+CB7Q0nFX 8s4cIlx5cqBBLSF94kd2u1NU9NtqwBGvAoU5v+DU=
Message-Id: <6.2.5.6.2.20120621085050.0a2e1a60@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 21 Jun 2012 14:50:01 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
In-Reply-To: <CADnDZ8-01L10ywMfW=2N90AnQRv2U3Vhp=qgJtpRL5KAgC=8XQ@mail.g mail.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com> <CADnDZ8-01L10ywMfW=2N90AnQRv2U3Vhp=qgJtpRL5KAgC=8XQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 22:21:03 -0000

Hi Abdussalam,
At 03:34 21-06-2012, Abdussalam Baryun wrote:
>-Why is the document/draft not clear of its aim, objectives,

Paul Hoffman actually asked what was not clear to me.  It does not 
mean that the draft is not clear.

>I agree and want the *consesus* and *community* input to be clear in the draft

The last comment in the message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg73779.html meant 
that I neither support nor oppose publication.  I was interested in 
seeing your arguments about the draft.

Regards,
-sm


From stewe@stewe.org  Thu Jun 21 16:01:37 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E97E211E80B6 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 16:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 eezTaLtaf35x for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 16:01:37 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe002.messaging.microsoft.com [213.199.154.205]) by ietfa.amsl.com (Postfix) with ESMTP id 990D511E80AA for <ietf@ietf.org>; Thu, 21 Jun 2012 16:01:36 -0700 (PDT)
Received: from mail51-am1-R.bigfish.com (10.3.201.245) by AM1EHSOBE005.bigfish.com (10.3.204.25) with Microsoft SMTP Server id 14.1.225.23; Thu, 21 Jun 2012 23:00:07 +0000
Received: from mail51-am1 (localhost [127.0.0.1])	by mail51-am1-R.bigfish.com (Postfix) with ESMTP id 53244805BD	for <ietf@ietf.org>; Thu, 21 Jun 2012 23:00:07 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT002.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: PS-19(zz98dI1432Izz1202h1082kzz1033IL8275dhz2fh2a8h668h839h944he5bhf0ah)
Received-SPF: pass (mail51-am1: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT002.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail51-am1 (localhost.localdomain [127.0.0.1]) by mail51-am1 (MessageSwitch) id 1340319605173885_21460; Thu, 21 Jun 2012 23:00:05 +0000 (UTC)
Received: from AM1EHSMHS006.bigfish.com (unknown [10.3.201.241])	by mail51-am1.bigfish.com (Postfix) with ESMTP id 1E9B92A0046	for <ietf@ietf.org>; Thu, 21 Jun 2012 23:00:05 +0000 (UTC)
Received: from BL2PRD0710HT002.namprd07.prod.outlook.com (157.56.240.133) by AM1EHSMHS006.bigfish.com (10.3.207.106) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 21 Jun 2012 23:00:04 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.88]) by BL2PRD0710HT002.namprd07.prod.outlook.com ([10.255.102.37]) with mapi id 14.16.0164.004; Thu, 21 Jun 2012 23:01:27 +0000
From: Stephan Wenger <stewe@stewe.org>
To: IETF <ietf@ietf.org>
Subject: Re: Proposed Update to Note Well
Thread-Topic: Proposed Update to Note Well
Thread-Index: AQHNT/qtF8urOkUi9ECLOMdvpukpJJcE7kCA
Date: Thu, 21 Jun 2012 23:01:26 +0000
Message-ID: <CC08F195.88447%stewe@stewe.org>
In-Reply-To: <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4C5F941A07C76F448B88435C6B15AF26@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 23:01:38 -0000

Hi Russ, policy-folks,

I support the simplification of the Note Well.

Two concerns, one substantial and one nit, with respect to the language
proposed.

The use of the work "know" in the context of requiring a disclosure is IMO
substantially wrong.  It should be "believe".  Two reasons.  The pragmatic
one: Positive "knowledge" of a patent covering a technology is not
something the IETF can expect from a layman.  The net result of this
language could well be that legal departments advise participants to never
make disclosures, as they are not patent lawyers (let alone courts of law)
that can reasonably make a determination of infringement.  Second, the
procedural reason:  Knowledge is not what BCP79 requires.  BCP79 requires
(in section 6) knowledge of IPR of which the contributor "believes" that
it covers, or may cover, the contribution.   According to my parsing of
English (and note that I'm not a native speaker), in the sentence
proposed, the "know" is attached to "covered" and not to the existence of
a patent. =20

The nit: "you or your employer own".  I believe that "own" is a close
enough (and practical enough) approximation of "right to assert", which is
required in BCP79.  However, there are scenarios where one does not "own"
IPR (in the sense of an assignment), but has the right to assert.  One
example would be an exclusive license.  In the light of recent legal
maneuvering (i.e. HTC asserting patents that they have borrowed from
Google--at least that is my understanding), language closer to BCP79's
language may be preferable.  Then again, the motivation of this exercise
appears to be to make the Note Well more accessible, and the language as
provided is not in contradiction with BCP79; it just leaves out one exotic
class of cases.  So I call this a nit.  Still, thinking about a
replacement for "own" that is more layman-friendly than "right to assert"
would be a worthwhile exercise.

Regards,
Stephan


On 6.21.2012 15:10 , "IETF Chair" <chair@ietf.org> wrote:

>The IESG has heard many complaints that the Note Well is too complex.
>After some discussion with counsel, we propose the following updated Note
>Well for your comment and review.  The below summary would be followed
>with a pointer to or text of more details, which will depend upon whether
>it's a meeting slide, on the web site, on the registration page, or on a
>mailing-list greeting.
>
>On behalf of the IESG,
>  Russ Housley
>  IETF Chair
>
>--------------------------------------
>
>NOTE WELL
>
>In summary:
>
>   By participating with the IETF, you agree to follow IETF processes.
>
>   If you write, say, or discuss anything in the IETF, formally or
>informally,
>   (all of which we call "a contribution") that you know is covered by a
>patent
>   or patent application you or your employer own, one of you must
>disclose
>   that.
>
>   You understand that meetings might be recorded and broadcast.
>
>This would be followed with a pointer to or text of more details,
>which will depend upon whether it's a meeting slide, on the web site,
>on the registration page, or on a mailing-list greeting.
>
>



From barryleiba.mailing.lists@gmail.com  Thu Jun 21 17:04:28 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2989021F855E for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 17:04:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.939
X-Spam-Level: 
X-Spam-Status: No, score=-102.939 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 JKGUt-gfVj5Q for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 17:04:27 -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 C8FE121F855B for <ietf@ietf.org>; Thu, 21 Jun 2012 17:04:26 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so3092063lbb.31 for <ietf@ietf.org>; Thu, 21 Jun 2012 17:04:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=z7yNF03Bxwa574g8u0r5rGUNMr4sJSit70zVFPiIwXw=; b=OrFSVvp3eD8ww/K48wXLV3sR/r/lDmAYN82FINuQfUP3wnJ6S7yTep45aghnKfuf7f x65j8/14E/9khO+3xWjBGc39rNK8Wti+AioSLysYhkRmMS+KifIKnYFj85hOlNE4O1yi eo24pEDeVhtF2cwU490wKpKFM3dZaSe9+gu3NKjZc8SdkBbZzUY0Z9WJ3N6YeQ6fHq/H dfZDtrTghLsmnoP0dZUQKZLjw1yJOqVWc2IrwLtjdeS+NU5Z/Ix6xZXwbdmGObcSZDkY /7x0zFuY3L/EpmxrP2zbefEVnb5IR6U1EXcSjkkQSEq/S3jNLoReAsk46N916uL4qNad BaMQ==
MIME-Version: 1.0
Received: by 10.152.112.233 with SMTP id it9mr29250lab.40.1340323465761; Thu, 21 Jun 2012 17:04:25 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.48.104 with HTTP; Thu, 21 Jun 2012 17:04:25 -0700 (PDT)
In-Reply-To: <CC08F195.88447%stewe@stewe.org>
References: <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org> <CC08F195.88447%stewe@stewe.org>
Date: Fri, 22 Jun 2012 02:04:25 +0200
X-Google-Sender-Auth: VYsgYjza4k9FggaAYYmjjcjWW1A
Message-ID: <CAC4RtVCyKmCeCLzqai287-GExcNqJBhUSwnu5UCiXDphjvOLhQ@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
From: Barry Leiba <barryleiba@computer.org>
To: Stephan Wenger <stewe@stewe.org>
Content-Type: multipart/alternative; boundary=f46d040838d30f94d004c30460ca
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 00:04:28 -0000

--f46d040838d30f94d004c30460ca
Content-Type: text/plain; charset=ISO-8859-1

Stephan, you're right about the first point.  We were focused on "knowing"
about the IPR, but it's "believe" is covered, indeed.  For the purpose of
this briefest of brief summaries -- the point here is to make something
that could actually be shown *and read out* by the chairs in IETF sessions
-- I think replacing "know" with "believe" is the best answer.

For the second point, "own", you're also right, but for this purpose I
think we have to say that it has to yield to simplicity.  The more detailed
reference will have to be the place to go for the proper legal info.  We
did think about this, and "own" was the closest we could get in "sound
bite" form.

Barry, Applications AD

On Thursday, June 21, 2012, Stephan Wenger wrote:

> Hi Russ, policy-folks,
>
> I support the simplification of the Note Well.
>
> Two concerns, one substantial and one nit, with respect to the language
> proposed.
>
> The use of the work "know" in the context of requiring a disclosure is IMO
> substantially wrong.  It should be "believe".  Two reasons.  The pragmatic
> one: Positive "knowledge" of a patent covering a technology is not
> something the IETF can expect from a layman.  The net result of this
> language could well be that legal departments advise participants to never
> make disclosures, as they are not patent lawyers (let alone courts of law)
> that can reasonably make a determination of infringement.  Second, the
> procedural reason:  Knowledge is not what BCP79 requires.  BCP79 requires
> (in section 6) knowledge of IPR of which the contributor "believes" that
> it covers, or may cover, the contribution.   According to my parsing of
> English (and note that I'm not a native speaker), in the sentence
> proposed, the "know" is attached to "covered" and not to the existence of
> a patent.
>
> The nit: "you or your employer own".  I believe that "own" is a close
> enough (and practical enough) approximation of "right to assert", which is
> required in BCP79.  However, there are scenarios where one does not "own"
> IPR (in the sense of an assignment), but has the right to assert.  One
> example would be an exclusive license.  In the light of recent legal
> maneuvering (i.e. HTC asserting patents that they have borrowed from
> Google--at least that is my understanding), language closer to BCP79's
> language may be preferable.  Then again, the motivation of this exercise
> appears to be to make the Note Well more accessible, and the language as
> provided is not in contradiction with BCP79; it just leaves out one exotic
> class of cases.  So I call this a nit.  Still, thinking about a
> replacement for "own" that is more layman-friendly than "right to assert"
> would be a worthwhile exercise.
>
> Regards,
> Stephan
>
>
> On 6.21.2012 15:10 , "IETF Chair" <chair@ietf.org <javascript:;>> wrote:
>
> >The IESG has heard many complaints that the Note Well is too complex.
> >After some discussion with counsel, we propose the following updated Note
> >Well for your comment and review.  The below summary would be followed
> >with a pointer to or text of more details, which will depend upon whether
> >it's a meeting slide, on the web site, on the registration page, or on a
> >mailing-list greeting.
> >
> >On behalf of the IESG,
> >  Russ Housley
> >  IETF Chair
> >
> >--------------------------------------
> >
> >NOTE WELL
> >
> >In summary:
> >
> >   By participating with the IETF, you agree to follow IETF processes.
> >
> >   If you write, say, or discuss anything in the IETF, formally or
> >informally,
> >   (all of which we call "a contribution") that you know is covered by a
> >patent
> >   or patent application you or your employer own, one of you must
> >disclose
> >   that.
> >
> >   You understand that meetings might be recorded and broadcast.
> >
> >This would be followed with a pointer to or text of more details,
> >which will depend upon whether it's a meeting slide, on the web site,
> >on the registration page, or on a mailing-list greeting.
> >
> >
>
>
>

--f46d040838d30f94d004c30460ca
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Stephan, you&#39;re right about the first point. =A0We were focused on &quo=
t;knowing&quot; about the IPR, but it&#39;s &quot;believe&quot; is covered,=
 indeed. =A0For the purpose of this briefest of brief summaries -- the poin=
t here is to make something that could actually be shown *and read out* by =
the chairs in IETF sessions -- I think replacing &quot;know&quot; with &quo=
t;believe&quot; is the best answer.<div>
<br></div><div>For the second point, &quot;own&quot;, you&#39;re also right=
, but for this purpose I think we have to say that it has to yield to simpl=
icity. =A0The more detailed reference will have to be the place to go for t=
he proper legal info. =A0We did think about this, and &quot;own&quot; was t=
he closest we could get in &quot;sound bite&quot; form.</div>
<div><br></div><div>Barry, Applications AD<span></span><br><div><br>On Thur=
sday, June 21, 2012, Stephan Wenger  wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
Hi Russ, policy-folks,<br>
<br>
I support the simplification of the Note Well.<br>
<br>
Two concerns, one substantial and one nit, with respect to the language<br>
proposed.<br>
<br>
The use of the work &quot;know&quot; in the context of requiring a disclosu=
re is IMO<br>
substantially wrong. =A0It should be &quot;believe&quot;. =A0Two reasons. =
=A0The pragmatic<br>
one: Positive &quot;knowledge&quot; of a patent covering a technology is no=
t<br>
something the IETF can expect from a layman. =A0The net result of this<br>
language could well be that legal departments advise participants to never<=
br>
make disclosures, as they are not patent lawyers (let alone courts of law)<=
br>
that can reasonably make a determination of infringement. =A0Second, the<br=
>
procedural reason: =A0Knowledge is not what BCP79 requires. =A0BCP79 requir=
es<br>
(in section 6) knowledge of IPR of which the contributor &quot;believes&quo=
t; that<br>
it covers, or may cover, the contribution. =A0 According to my parsing of<b=
r>
English (and note that I&#39;m not a native speaker), in the sentence<br>
proposed, the &quot;know&quot; is attached to &quot;covered&quot; and not t=
o the existence of<br>
a patent.<br>
<br>
The nit: &quot;you or your employer own&quot;. =A0I believe that &quot;own&=
quot; is a close<br>
enough (and practical enough) approximation of &quot;right to assert&quot;,=
 which is<br>
required in BCP79. =A0However, there are scenarios where one does not &quot=
;own&quot;<br>
IPR (in the sense of an assignment), but has the right to assert. =A0One<br=
>
example would be an exclusive license. =A0In the light of recent legal<br>
maneuvering (i.e. HTC asserting patents that they have borrowed from<br>
Google--at least that is my understanding), language closer to BCP79&#39;s<=
br>
language may be preferable. =A0Then again, the motivation of this exercise<=
br>
appears to be to make the Note Well more accessible, and the language as<br=
>
provided is not in contradiction with BCP79; it just leaves out one exotic<=
br>
class of cases. =A0So I call this a nit. =A0Still, thinking about a<br>
replacement for &quot;own&quot; that is more layman-friendly than &quot;rig=
ht to assert&quot;<br>
would be a worthwhile exercise.<br>
<br>
Regards,<br>
Stephan<br>
<br>
<br>
On 6.21.2012 15:10 , &quot;IETF Chair&quot; &lt;<a href=3D"javascript:;" on=
click=3D"_e(event, &#39;cvml&#39;, &#39;chair@ietf.org&#39;)">chair@ietf.or=
g</a>&gt; wrote:<br>
<br>
&gt;The IESG has heard many complaints that the Note Well is too complex.<b=
r>
&gt;After some discussion with counsel, we propose the following updated No=
te<br>
&gt;Well for your comment and review. =A0The below summary would be followe=
d<br>
&gt;with a pointer to or text of more details, which will depend upon wheth=
er<br>
&gt;it&#39;s a meeting slide, on the web site, on the registration page, or=
 on a<br>
&gt;mailing-list greeting.<br>
&gt;<br>
&gt;On behalf of the IESG,<br>
&gt; =A0Russ Housley<br>
&gt; =A0IETF Chair<br>
&gt;<br>
&gt;--------------------------------------<br>
&gt;<br>
&gt;NOTE WELL<br>
&gt;<br>
&gt;In summary:<br>
&gt;<br>
&gt; =A0 By participating with the IETF, you agree to follow IETF processes=
.<br>
&gt;<br>
&gt; =A0 If you write, say, or discuss anything in the IETF, formally or<br=
>
&gt;informally,<br>
&gt; =A0 (all of which we call &quot;a contribution&quot;) that you know is=
 covered by a<br>
&gt;patent<br>
&gt; =A0 or patent application you or your employer own, one of you must<br=
>
&gt;disclose<br>
&gt; =A0 that.<br>
&gt;<br>
&gt; =A0 You understand that meetings might be recorded and broadcast.<br>
&gt;<br>
&gt;This would be followed with a pointer to or text of more details,<br>
&gt;which will depend upon whether it&#39;s a meeting slide, on the web sit=
e,<br>
&gt;on the registration page, or on a mailing-list greeting.<br>
&gt;<br>
&gt;<br>
<br>
<br>
</blockquote></div></div>

--f46d040838d30f94d004c30460ca--

From scott.brim@gmail.com  Thu Jun 21 18:02:20 2012
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D500B11E8083; Thu, 21 Jun 2012 18:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 2ml9YfxY2v66; Thu, 21 Jun 2012 18:02:20 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 54D7F11E8072; Thu, 21 Jun 2012 18:02:20 -0700 (PDT)
Received: by dacx6 with SMTP id x6so1650872dac.31 for <multiple recipients>; Thu, 21 Jun 2012 18:02:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xTgmiz3nmm5lxNeyAd7KzSaQX6Yp9RzjrtAbO2esZg8=; b=pxqCP5QgTo1rd3C4VnNN9NORC6M804ije3zeQ2djDEBsBbcU2XdYJFx0J5V/yhjZ+R ioGHzVRwvqNvqBSS/z4eEeiRLrOX+PeOKoxzVDZYKBj+a8MkY8mhrIkM8agBK16B+mc3 x6egobC4mK2puv5Z/jkFdHehyPUw9A9odvpmD/xL1M9obOP3xEFWvR1Mj4BisqaetHuu RlGwna4rDnBhw8n6caiI/75vEweZdDCjA+lICS3cgKUgZzIg84GjJrxlyk51vFV45PiD rsxozHj/KIMSNbDsHqxPyImfA7MqlhihaHXVFVwA70Pq0L2y1qHp1KwPrzW0WWONHHIF g14g==
Received: by 10.68.238.68 with SMTP id vi4mr3839489pbc.123.1340326940103; Thu, 21 Jun 2012 18:02:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.220.132 with HTTP; Thu, 21 Jun 2012 18:01:59 -0700 (PDT)
In-Reply-To: <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org>
References: <4FCF5B92.3070703@qualcomm.com> <4FCF5F99.3060807@cisco.com> <4FCF6BD5.7080503@qualcomm.com> <4FCF8471.2050701@cisco.com> <AEF1278E-68D1-47D3-932A-8B4940E864A0@harvard.edu> <4FD0679D.60304@cisco.com> <4FD068BC.5050405@cs.tcd.ie> <CAP0PwYZb87zRv0HpTES1twLnnTWUk9ft80bupUoB5f62P3eL=A@mail.gmail.com> <4FD0A53A.6010406@innovationslab.net> <4FD0AAA5.3060400@cisco.com> <C07B527F-37D1-4340-BF7D-F1B6BD263726@gmail.com> <4FD0B3A1.7090001@qualcomm.com> <4FD0B3FA.90704@qualcomm.com> <CAP0PwYYjbaHqkk7z5dXBB4kcH=NhT5_MofHFpwpgXnXvBG_tKQ@mail.gmail.com> <4FD0B86E.8020008@qualcomm.com> <CALaySJKSzsgpmxaiTsHMAEBJNTyPGScMnsfTM=rbMiMEUREb6w@mail.gmail.com> <BD3F594E-0ED1-4079-836F-5D7F5D63AD91@harvard.edu> <CAP0PwYam-arXn1vYebn16d7b_paD7P9ZwKhG1aYgCo2yxuUWaQ@mail.gmail.com> <4FD0F8C5.8000100@qualcomm.com> <4FD10927.8020906@qualcomm.com> <CALaySJ+cMTbcsQQXTa4xhxS+0jBHah4XBXuHEeo4+i2iv1cRVg@mail.gmail.com> <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com> <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 21 Jun 2012 21:01:59 -0400
Message-ID: <CAPv4CP9FqeZ5UdtR-O0uy0tKxOHaZEsrRz-friF22nkKL-y=RA@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
To: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b33960125d56804c3052f4c
Cc: IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 01:02:21 -0000

--047d7b33960125d56804c3052f4c
Content-Type: text/plain; charset=ISO-8859-1

Nice job.  One comment:

On Thu, Jun 21, 2012 at 6:10 PM, IETF Chair <chair@ietf.org> allegedly
wrote:

>   If you write, say, or discuss anything in the IETF, formally or
> informally,
>

Can you fit "even between meetings" at the end of this line?  Some people
will think "in the IETF" refers to physical meetings, and may not get
through the detailed info that comes later.


>   (all of which we call "a contribution") that you know is covered by a
> patent
>   or patent application you or your employer own, one of you must disclose
>   that.


I also like know -> believe.

Thanks ... Scott

--047d7b33960125d56804c3052f4c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">Nice job. =A0One comment:</div><div class=3D"gma=
il_quote"><br></div><div class=3D"gmail_quote">On Thu, Jun 21, 2012 at 6:10=
 PM, IETF Chair <span dir=3D"ltr">&lt;<a href=3D"mailto:chair@ietf.org" tar=
get=3D"_blank">chair@ietf.org</a>&gt;</span>=A0allegedly wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">=A0 If you write, say, or discuss anything i=
n the IETF, formally or informally,<br></blockquote><div><br></div><div>Can=
 you fit &quot;even between meetings&quot; at the end of this line? =A0Some=
 people will think &quot;in the IETF&quot; refers to physical meetings, and=
 may not get through the detailed info that comes later.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
 =A0 (all of which we call &quot;a contribution&quot;) that you know is cov=
ered by a patent<br>
 =A0 or patent application you or your employer own, one of you must disclo=
se<br>
 =A0 that.</blockquote><div><br></div><div>I also like know -&gt; believe.<=
/div><div><br></div><div>Thanks ... Scott</div></div>

--047d7b33960125d56804c3052f4c--

From abdussalambaryun@gmail.com  Thu Jun 21 18:12:33 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9AD121F85EF for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 18:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 IkgYA2q0R0pR for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 18:12:32 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B5FCE21F8546 for <ietf@ietf.org>; Thu, 21 Jun 2012 18:12:32 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so721232vbb.31 for <ietf@ietf.org>; Thu, 21 Jun 2012 18:12:32 -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=pjd900O/vuxUYh9t60Gs0umqEqobrjsIQWBIGsfLqqg=; b=M/FJBhkPX0toKAQMQfPc2D0gWnxjIt7OLb692XQY+/1ogh1+ubE9mcG/LJQMfPX3mh Y+WG31q14Xv8NvUF9FxVe7vEtV3N9hCRorAJf6PEsR+i/ODXbeM9WM8eAw6iHSG9WOiF C69uziSjZ9W/WqxB3iBtVKc6yNv2OpPR2WR3wUpFfQTEmnCMmvIGOK9u0MxTqEbSPqOW erdb0vzGPSWF95+RLs4eWkVBM8HBySktwTi3Fjq8B9CBdJlcYRv5GYVXCiGV+wnTl+s5 cCuB2VSIBXZcsiNQ0MKJSxDpvTd/4FioxDxUMjhi9hkfhsJ1PQIPux+lzwy2dMjpo1my VG/Q==
MIME-Version: 1.0
Received: by 10.52.90.196 with SMTP id by4mr68297vdb.103.1340327551952; Thu, 21 Jun 2012 18:12:31 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Thu, 21 Jun 2012 18:12:31 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120621085050.0a2e1a60@resistor.net>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com> <CADnDZ8-01L10ywMfW=2N90AnQRv2U3Vhp=qgJtpRL5KAgC=8XQ@mail.gmail.com> <6.2.5.6.2.20120621085050.0a2e1a60@resistor.net>
Date: Fri, 22 Jun 2012 03:12:31 +0200
Message-ID: <CADnDZ881q6ztP+cDsnF5pajjFQg+Pd6k+iPQyW2pnVpiWNdpCA@mail.gmail.com>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: housley@vigilsec.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 01:12:33 -0000

Hi Russ,

I agree with the proposal totally, but my confusions are: a) if we are
having the current document RFC4677 on the Tao-web, could we not
obsolete the RFC4677 until we get a final updated agreed RFC other
than the submitted I-D, Or the first web-document approved to obsolete
the RFC4677.
b) If we are making a new IETF web-document process, could we have the
I-D submited to include how the community will decide and how the
editor will decide.

sorry for any disturb,

Abdussalam
++++++++++++++++++++++++++++++++++++++++++++++++
From: Russ Housley <housley at vigilsec.com>
To: IETF <ietf at ietf.org>
Date: Thu, 21 Jun 2012 17:08:40 -0400

This URL <http://www.ietf.org/tao> will bring up the current document.
 It works exactly the same as <http://www.ietf.org/tao.html>.

This means that <http://www.ietf.org/tao/archive> cannot be used as
suggested on this thread.

I propose the following URLs for the Tao:

   - current Tao: <http://www.ietf.org/tao.html>

   - draft Tao: <http://www.ietf.org/tao-possible-revision.html>

   - archive entries: <http://www.ietf.org/tao-archive/tao-YYYYMMDD.html>

Russ

From stpeter@stpeter.im  Thu Jun 21 18:18:21 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C60A911E8083; Thu, 21 Jun 2012 18:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2DPU-fSle772; Thu, 21 Jun 2012 18:18:21 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 359D311E80A1; Thu, 21 Jun 2012 18:18:21 -0700 (PDT)
Received: from [192.168.0.9] (unknown [216.17.179.227]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7DF1540092; Thu, 21 Jun 2012 19:35:59 -0600 (MDT)
Message-ID: <4FE3C7DC.9050607@stpeter.im>
Date: Thu, 21 Jun 2012 19:18:20 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: Proposed Update to Note Well
References: <4FCF5B92.3070703@qualcomm.com> <4FCF6BD5.7080503@qualcomm.com> <4FCF8471.2050701@cisco.com> <AEF1278E-68D1-47D3-932A-8B4940E864A0@harvard.edu> <4FD0679D.60304@cisco.com> <4FD068BC.5050405@cs.tcd.ie> <CAP0PwYZb87zRv0HpTES1twLnnTWUk9ft80bupUoB5f62P3eL=A@mail.gmail.com> <4FD0A53A.6010406@innovationslab.net> <4FD0AAA5.3060400@cisco.com> <C07B527F-37D1-4340-BF7D-F1B6BD263726@gmail.com> <4FD0B3A1.7090001@qualcomm.com> <4FD0B3FA.90704@qualcomm.com> <CAP0PwYYjbaHqkk7z5dXBB4kcH=NhT5_MofHFpwpgXnXvBG_tKQ@mail.gmail.com> <4FD0B86E.8020008@qualcomm.com> <CALaySJKSzsgpmxaiTsHMAEBJNTyPGScMnsfTM=rbMiMEUREb6w@mail.gmail.com> <BD3F594E-0ED1-4079-836F-5D7F5D63AD91@harvard.edu> <CAP0PwYam-arXn1vYebn16d7b_paD7P9ZwKhG1aYgCo2yxuUWaQ@mail.gmail.com> <4FD0F8C5.8000100@qualcomm.com> <4FD10927.8020906@qualcomm.com> <CALaySJ+cMTbcsQQXTa4xhxS+0jBHah4XBXuHEeo4+i2iv1cRVg@mail.gmail.com> <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com> <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org>
In-Reply-To: <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 01:18:21 -0000

I like the idea of a brief summary that can be shown on one readable
slide at the beginning of each session, read aloud by a meeting chair,
etc. Wordsmithing below.

On 6/21/12 4:10 PM, IETF Chair wrote:

>    If you write, say, or discuss anything in the IETF, formally or informally,
>    (all of which we call "a contribution") that you know is covered by a patent
>    or patent application you or your employer own, one of you must disclose
>    that.

With all due respect, that sentence could be improved. I suggest:

   Anything that you write, say, or discuss in the IETF, formally or
informally,
   at an IETF meeting or in another IETF venue such as a mailing list,
is an
   IETF contribution. If you believe that a contribution of yours is
covered by
   a patent or a patent application made by you or your employer, you must
   disclose it.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/





From dan-ietf@danyork.org  Thu Jun 21 19:31:59 2012
Return-Path: <dan-ietf@danyork.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 955E621F844A for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 19:31:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.998
X-Spam-Level: 
X-Spam-Status: No, score=-2.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_57=0.6, 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 rJCQPVxsEHh5 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 19:31:58 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 529EA21F8446 for <ietf@ietf.org>; Thu, 21 Jun 2012 19:31:58 -0700 (PDT)
Received: by qadz3 with SMTP id z3so102291qad.10 for <ietf@ietf.org>; Thu, 21 Jun 2012 19:31:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:mime-version:content-type:subject:date:references:cc:to :message-id:x-mailer:x-gm-message-state; bh=d9KTnUz3YvXRMtfUHOzMjW5+KuN0/TNAj0AAbz9YyTE=; b=fb8IyAABbv1XQ1oFuYwxPHj5DtcEhNbNRfRcEm2d8nGQnWuFC8XLpg/6leAirOaIVH E8cGNvdHUy7HvEdaiu2nxKOzxlvLvxSlxxhcehVdoxjYXXfpwkw2se4ME+RCHqjx2+WD TnX3SjguDAeb+nMBtDHXZdQWbCFjNn1dbrYz1t5cF+YhshHHi5Ihg/rwNXLaQi6RtZmh S5VKem5/eCeFbbF9BMaw3ncRKevnN7wrUe5nNkk32AldJphZHyIyOXkk2ZKk+2J0vYIJ TMhfUHK9i78wxHrlMPbZNfDYm79B2Pzm5uJJB/DfK29oQ4eFTw2rPhQ0qNjuV5zVMuci kA8g==
Received: by 10.224.58.201 with SMTP id i9mr3523736qah.39.1340332317659; Thu, 21 Jun 2012 19:31:57 -0700 (PDT)
Received: from [172.20.12.152] (cpe-74-75-92-114.maine.res.rr.com. [74.75.92.114]) by mx.google.com with ESMTPS id j12sm46518074qak.15.2012.06.21.19.31.56 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Jun 2012 19:31:57 -0700 (PDT)
From: Dan York <dan-ietf@danyork.org>
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_1FC4C94A-3510-4F1A-9B2F-CDFE747C2C5E"
Subject: Re: [CDNi] Last Call: <draft-ietf-cdni-use-cases-08.txt> (Use Cases for Content	Delivery Network Interconnection) to Informational RFC
Date: Thu, 21 Jun 2012 22:31:50 -0400
References: <3A900E99-5226-4023-BB23-F06DF648A0B2@danyork.org>
To: IETF-Discussion list <ietf@ietf.org>
Message-Id: <4D8B1F16-20F2-4C55-834B-65DE1DA2BA58@danyork.org>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQmmqO1kqP2O242MUCztgd8+f/+uL11B11iiLJCo+q9XoH3L38WCu75v/RBvCNBOFbjoyh8j
Cc: cdni@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 02:31:59 -0000

--Apple-Mail=_1FC4C94A-3510-4F1A-9B2F-CDFE747C2C5E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Responding to the Last Call for comments, I think the draft is well done =
and will be very useful in helping people understand what the CDNI =
effort is all about.

My only substantive comment is that there is another use case related to =
IPv6 that could be spelled out under section 4.1, "Device and Network =
Technology Extension":

http://tools.ietf.org/html/draft-ietf-cdni-use-cases-08#section-4.1

The text for the additional use case could be:
----
3. CDN-A only supports IPv4 within its infrastructure but wants to =
deliver content over IPv6.  CDN-B supports both IPv4 and IPv6 within its =
infrastructure. CDN-A interconnects with CDN-B to serve out its content =
over native IPv6 connections.
----

In truth this could be seen as a variation of use case #1 in this =
section, "CDN-A cannot support a specific delivery protocol," and is =
similar to the reference to HTTPS in use case #1.  However, when I read =
that use case I find myself thinking about higher level delivery =
protocols and not something as fundamental as IP. =20

Plus, given that we'll be in the IPv4/IPv6 transition for some time, it =
may be useful to specifically highlight how CDNI could assist in the =
transition to IPv6.

Again, I think it's a good document that should be published.

My 2 cents,
Dan

P.S. Well, I will also admit that the comma in the first sentence of the =
abstract bothers me: "Content Delivery Networks (CDNs) are commonly used =
for improving the End User experience of a content delivery service, at =
a reasonable cost." I think that comma could be removed... but I'll =
leave that for the grammarians to duke it out... :-)

On Jun 20, 2012, at 9:14 AM, The IESG wrote:

>=20
> The IESG has received a request from the Content Delivery Networks
> Interconnection WG (cdni) to consider the following document:
> - 'Use Cases for Content Delivery Network Interconnection'
>  <draft-ietf-cdni-use-cases-08.txt> as Informational RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-07-04. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   Content Delivery Networks (CDNs) are commonly used for improving the
>   End User experience of a content delivery service, at a reasonable
>   cost.  This document focuses on use cases that correspond to
>   identified industry needs and that are expected to be realized once
>   open interfaces and protocols supporting interconnection of CDNs are
>   specified and implemented.  The document can be used to guide the
>   definition of the requirements to be supported by CDN =
Interconnection
>   (CDNI) interfaces.  It obsoletes RFC 3570.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/ballot/
>=20
>=20
> The following IPR Declarations may be related to this I-D:
>=20
>   http://datatracker.ietf.org/ipr/1764/
>=20
>=20
>=20
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org
> https://www.ietf.org/mailman/listinfo/cdni

--=20
Dan York  dyork@lodestar2.com
http://danyork.me/   skype:danyork
Phone: +1-802-735-1624
Twitter - http://twitter.com/danyork
--------------------------------------------------------
All comments and opinions are entirely my own and have no connection =
whatsoever to any employer, past or present. Indeed, by tomorrow even I =
might be disavowing these comments.
--------------------------------------------------------

--=20
Dan York  dyork@lodestar2.com
http://www.danyork.com/   skype:danyork
Phone: +1-802-735-1624
Twitter - http://twitter.com/danyork
--------------------------------------------------------
All comments and opinions are entirely my own and have no connection =
whatsoever to any employer, past or present. Indeed, by tomorrow even I =
might be disavowing these comments.
--------------------------------------------------------


--Apple-Mail=_1FC4C94A-3510-4F1A-9B2F-CDFE747C2C5E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;">Responding to the Last Call for comments, I =
think the draft is well done and will be very useful in helping people =
understand what the CDNI effort is all about.</div><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><br></div><div>My only =
substantive comment is that there is another use case related to IPv6 =
that could be spelled out under section 4.1, "Device and Network =
Technology Extension":</div><div><br></div><div><a =
href=3D"http://tools.ietf.org/html/draft-ietf-cdni-use-cases-08#section-4.=
1">http://tools.ietf.org/html/draft-ietf-cdni-use-cases-08#section-4.1</a>=
</div><div><br></div><div>The text for the additional use case could =
be:</div><div>----</div><div>3. CDN-A only supports IPv4 within its =
infrastructure but wants to deliver content over IPv6. &nbsp;CDN-B =
supports both IPv4 and IPv6 within its infrastructure. CDN-A =
interconnects with CDN-B to serve out its content over native IPv6 =
connections.</div><div>----</div><div><br></div><div>In truth this could =
be seen as a variation of use case #1 in this section, "CDN-A cannot =
support a specific delivery protocol," and is similar to the reference =
to HTTPS in use case #1. &nbsp;However, when I read that use case I find =
myself thinking about higher level delivery protocols and not something =
as fundamental as IP. &nbsp;</div><div><br></div><div>Plus, given that =
we'll be in the IPv4/IPv6 transition for some time, it may be useful to =
specifically highlight how CDNI could assist in the transition to =
IPv6.</div><div><br></div><div>Again, I think it's a good document that =
should be published.</div><div><br></div><div>My 2 =
cents,</div><div>Dan</div><div><br></div><div>P.S. Well, I will also =
admit that the comma in the first sentence of the abstract bothers me: =
"Content Delivery Networks (CDNs) are commonly used for improving =
the&nbsp;End User experience of a content delivery service, at a =
reasonable&nbsp;cost." I think that comma could be removed... but I'll =
leave that for the grammarians to duke it out... =
:-)</div><div><br><div><div>On Jun 20, 2012, at 9:14 AM, The IESG =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><br>The IESG has received a request from the Content =
Delivery Networks<br>Interconnection WG (cdni) to consider the following =
document:<br>- 'Use Cases for Content Delivery Network =
Interconnection'<br> &nbsp;&lt;draft-ietf-cdni-use-cases-08.txt&gt; as =
Informational RFC<br><br>The IESG plans to make a decision in the next =
few weeks, and solicits<br>final comments on this action. Please send =
substantive comments to the<br><a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by =
2012-07-04. Exceptionally, comments may be<br>sent to <a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, =
please retain the<br>beginning of the Subject line to allow automated =
sorting.<br><br>Abstract<br><br><br> &nbsp;&nbsp;Content Delivery =
Networks (CDNs) are commonly used for improving the<br> &nbsp;&nbsp;End =
User experience of a content delivery service, at a reasonable<br> =
&nbsp;&nbsp;cost. &nbsp;This document focuses on use cases that =
correspond to<br> &nbsp;&nbsp;identified industry needs and that are =
expected to be realized once<br> &nbsp;&nbsp;open interfaces and =
protocols supporting interconnection of CDNs are<br> =
&nbsp;&nbsp;specified and implemented. &nbsp;The document can be used to =
guide the<br> &nbsp;&nbsp;definition of the requirements to be supported =
by CDN Interconnection<br> &nbsp;&nbsp;(CDNI) interfaces. &nbsp;It =
obsoletes RFC 3570.<br><br><br><br><br>The file can be obtained =
via<br><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/">http:/=
/datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/</a><br><br>IESG =
discussion can be tracked via<br><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/ballot/"=
>http://datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/ballot/</a><br>=
<br><br>The following IPR Declarations may be related to this =
I-D:<br><br> =
&nbsp;&nbsp;http://datatracker.ietf.org/ipr/1764/<br><br><br><br>_________=
______________________________________<br>CDNi mailing =
list<br>CDNi@ietf.org<br>https://www.ietf.org/mailman/listinfo/cdni<br></d=
iv></blockquote></div><br><div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">--&nbsp;<br>Dan York &nbsp;<a =
href=3D"mailto:dyork@lodestar2.com">dyork@lodestar2.com</a><br><a =
href=3D"http://danyork.me/">http://danyork.me/</a>&nbsp;&nbsp;&nbsp;<a =
href=3D"skype:danyork">skype:danyork</a><br>Phone: =
+1-802-735-1624<br>Twitter -&nbsp;<a =
href=3D"http://twitter.com/danyork">http://twitter.com/danyork</a></div><d=
iv style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
">--------------------------------------------------------</div></div><div=
 style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">All comments and opinions are =
entirely my own and have no connection whatsoever to any employer, past =
or present. Indeed, by tomorrow even I might be disavowing these =
comments.</div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
">--------------------------------------------------------</div></div>
</div>
</div></div></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">--&nbsp;<br>Dan York &nbsp;<a =
href=3D"mailto:dyork@lodestar2.com">dyork@lodestar2.com</a><br><a =
href=3D"http://www.danyork.com/">http://www.danyork.com/</a>&nbsp;&nbsp;&n=
bsp;<a href=3D"skype:danyork">skype:danyork</a><br>Phone: =
+1-802-735-1624<br>Twitter -&nbsp;<a =
href=3D"http://twitter.com/danyork">http://twitter.com/danyork</a></div><d=
iv style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
">--------------------------------------------------------</div></div><div=
 style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">All comments and opinions are =
entirely my own and have no connection whatsoever to any employer, past =
or present. Indeed, by tomorrow even I might be disavowing these =
comments.</div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
">--------------------------------------------------------</div></div></sp=
an></span>
</div>
<br></body></html>=

--Apple-Mail=_1FC4C94A-3510-4F1A-9B2F-CDFE747C2C5E--

From randy@psg.com  Thu Jun 21 19:42:45 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F15C21F8494 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 19:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599]
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 tkQ2e26k-B8S for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 19:42:44 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id D024621F8491 for <ietf@ietf.org>; Thu, 21 Jun 2012 19:42:44 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Shtpb-000F1q-O5; Fri, 22 Jun 2012 02:42:44 +0000
Date: Thu, 21 Jun 2012 16:42:42 -1000
Message-ID: <m2y5ng6p99.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Protocol Definition
In-Reply-To: <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com>
References: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com> <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 02:42:45 -0000

> All protocols in IETF are based on the Internet or/and the IP.

what a laugh.  try, for example,

   RFC 826

randy

From hartmans@mit.edu  Thu Jun 21 19:45:52 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 202B121F8491; Thu, 21 Jun 2012 19:45:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.432
X-Spam-Level: 
X-Spam-Status: No, score=-104.432 tagged_above=-999 required=5 tests=[AWL=-2.167, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 M1cjA5pBV5gS; Thu, 21 Jun 2012 19:45:51 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 1883F21F8496; Thu, 21 Jun 2012 19:45:44 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 3E14A20439; Thu, 21 Jun 2012 22:45:16 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 4DAD841EF; Thu, 21 Jun 2012 22:45:40 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Proposed Update to Note Well
References: <4FCF5B92.3070703@qualcomm.com> <AEF1278E-68D1-47D3-932A-8B4940E864A0@harvard.edu> <4FD0679D.60304@cisco.com> <4FD068BC.5050405@cs.tcd.ie> <CAP0PwYZb87zRv0HpTES1twLnnTWUk9ft80bupUoB5f62P3eL=A@mail.gmail.com> <4FD0A53A.6010406@innovationslab.net> <4FD0AAA5.3060400@cisco.com> <C07B527F-37D1-4340-BF7D-F1B6BD263726@gmail.com> <4FD0B3A1.7090001@qualcomm.com> <4FD0B3FA.90704@qualcomm.com> <CAP0PwYYjbaHqkk7z5dXBB4kcH=NhT5_MofHFpwpgXnXvBG_tKQ@mail.gmail.com> <4FD0B86E.8020008@qualcomm.com> <CALaySJKSzsgpmxaiTsHMAEBJNTyPGScMnsfTM=rbMiMEUREb6w@mail.gmail.com> <BD3F594E-0ED1-4079-836F-5D7F5D63AD91@harvard.edu> <CAP0PwYam-arXn1vYebn16d7b_paD7P9ZwKhG1aYgCo2yxuUWaQ@mail.gmail.com> <4FD0F8C5.8000100@qualcomm.com> <4FD10927.8020906@qualcomm.com> <CALaySJ+cMTbcsQQXTa4xhxS+0jBHah4XBXuHEeo4+i2iv1cRVg@mail.gmail.com> <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com> <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org> <4FE3C7DC.9050607@stpeter.im>
Date: Thu, 21 Jun 2012 22:45:40 -0400
In-Reply-To: <4FE3C7DC.9050607@stpeter.im> (Peter Saint-Andre's message of "Thu, 21 Jun 2012 19:18:20 -0600")
Message-ID: <tslzk7wdpyj.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 02:45:52 -0000

I like Peter's rephrasing  for a number of reasons.

1) Clearly states who is responsible for making the disclosure happen
(the IETf contributor)

2) Defines IETf contribution in its own sentence which makes it easier
to reference later.

3) Makes it clear that things like mailing list conversations are
covered.

From cntreras@gmail.com  Thu Jun 21 19:49:12 2012
Return-Path: <cntreras@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ED5021F8548 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 19:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 IJa9puh+IztA for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 19:49:11 -0700 (PDT)
Received: from mail-qa0-f52.google.com (mail-qa0-f52.google.com [209.85.216.52]) by ietfa.amsl.com (Postfix) with ESMTP id 8DF0621F8491 for <ietf@ietf.org>; Thu, 21 Jun 2012 19:49:11 -0700 (PDT)
Received: by qabj34 with SMTP id j34so139633qab.4 for <ietf@ietf.org>; Thu, 21 Jun 2012 19:49:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=FrSdSPPSM8kMJRcRswz300QSSYmALcokgb6lURuE0Mg=; b=scrcfXMOxZhQhNdv6enejhDGLCtyCfqGNWOavni0H91yNq61ma1K5W11O9SF+AQywq krJVgDoR8jndzS29G1LQ2bhNlMjUSIGhcz1Rvz/vMff/Z4DW1v3YYS2wW1FGlS3cTOgJ 750/kkLvopklE+S2rOqXigZk34cuVoZCCQo0sdXE9AHrMlLH1GCYJUbYNoS/5xMz0Pn2 TnJvtTfkEkal+nMW01/3/yMmtn/czzQ6CENlCviOd8jimVpL6gKWJNbzscge/+GZtIpb xcvEQoQYGaN1nSiJlHDEarOG6i5r59NjCKLBdmySMNiVZf2S84+/UJe7Puf2VDdQNQFD BCng==
Received: by 10.224.186.143 with SMTP id cs15mr3328906qab.94.1340333351105; Thu, 21 Jun 2012 19:49:11 -0700 (PDT)
Received: from [10.171.121.45] (mobile-198-228-196-036.mycingular.net. [198.228.196.36]) by mx.google.com with ESMTPS id n2sm66644068qap.10.2012.06.21.19.49.09 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Jun 2012 19:49:10 -0700 (PDT)
References: <CC08F195.88447%stewe@stewe.org>
In-Reply-To: <CC08F195.88447%stewe@stewe.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Message-Id: <AFB6264C-0EA2-4E7E-A98D-5EEFEF514958@gmail.com>
X-Mailer: iPhone Mail (9B206)
From: Jorge Contreras <cntreras@gmail.com>
Subject: Re: Proposed Update to Note Well
Date: Thu, 21 Jun 2012 22:49:00 -0400
To: Stephan Wenger <stewe@stewe.org>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 02:49:12 -0000

Sent from my iPhone

On Jun 21, 2012, at 7:01 PM, Stephan Wenger <stewe@stewe.org> wrote:

> Hi Russ, policy-folks,
> 
> I support the simplification of the Note Well.
> 
> Two concerns, one substantial and one nit, with respect to the language
> proposed.
> 
> The use of the work "know" in the context of requiring a disclosure is IMO
> substantially wrong.  It should be "believe".  Two reasons.  The pragmatic
> one: Positive "knowledge" of a patent covering a technology is not
> something the IETF can expect from a layman.  The net result of this
> language could well be that legal departments advise participants to never
> make disclosures, as they are not patent lawyers (let alone courts of law)
> that can reasonably make a determination of infringement.  Second, the
> procedural reason:  Knowledge is not what BCP79 requires.  BCP79 requires
> (in section 6) knowledge of IPR of which the contributor "believes" that
> it covers, or may cover, the contribution.   According to my parsing of
> English (and note that I'm not a native speaker), in the sentence
> proposed, the "know" is attached to "covered" and not to the existence of
> a patent.  
> 
> The nit: "you or your employer own".  I believe that "own" is a close
> enough (and practical enough) approximation of "right to assert", which is
> required in BCP79.  However, there are scenarios where one does not "own"
> IPR (in the sense of an assignment), but has the right to assert.  One
> example would be an exclusive license.  In the light of recent legal
> maneuvering (i.e. HTC asserting patents that they have borrowed from
> Google--at least that is my understanding), language closer to BCP79's
> language may be preferable.  Then again, the motivation of this exercise
> appears to be to make the Note Well more accessible, and the language as
> provided is not in contradiction with BCP79; it just leaves out one exotic
> class of cases.  So I call this a nit.  Still, thinking about a
> replacement for "own" that is more layman-friendly than "right to assert"
> would be a worthwhile exercise

The word would be "control". 

> 
> Regards,
> Stephan
> 
> 
> On 6.21.2012 15:10 , "IETF Chair" <chair@ietf.org> wrote:
> 
>> The IESG has heard many complaints that the Note Well is too complex.
>> After some discussion with counsel, we propose the following updated Note
>> Well for your comment and review.  The below summary would be followed
>> with a pointer to or text of more details, which will depend upon whether
>> it's a meeting slide, on the web site, on the registration page, or on a
>> mailing-list greeting.
>> 
>> On behalf of the IESG,
>> Russ Housley
>> IETF Chair
>> 
>> --------------------------------------
>> 
>> NOTE WELL
>> 
>> In summary:
>> 
>>  By participating with the IETF, you agree to follow IETF processes.
>> 
>>  If you write, say, or discuss anything in the IETF, formally or
>> informally,
>>  (all of which we call "a contribution") that you know is covered by a
>> patent
>>  or patent application you or your employer own, one of you must
>> disclose
>>  that.
>> 
>>  You understand that meetings might be recorded and broadcast.
>> 
>> This would be followed with a pointer to or text of more details,
>> which will depend upon whether it's a meeting slide, on the web site,
>> on the registration page, or on a mailing-list greeting.
>> 
>> 
> 
> 

From stewe@stewe.org  Thu Jun 21 19:59:51 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1AB621F85E0 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 19:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 nmYnS-DWTKoF for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 19:59:51 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe001.messaging.microsoft.com [213.199.154.204]) by ietfa.amsl.com (Postfix) with ESMTP id AF4E121F85DF for <ietf@ietf.org>; Thu, 21 Jun 2012 19:59:50 -0700 (PDT)
Received: from mail109-am1-R.bigfish.com (10.3.201.250) by AM1EHSOBE003.bigfish.com (10.3.204.23) with Microsoft SMTP Server id 14.1.225.23; Fri, 22 Jun 2012 02:58:21 +0000
Received: from mail109-am1 (localhost [127.0.0.1])	by mail109-am1-R.bigfish.com (Postfix) with ESMTP id 850EB3A0553; Fri, 22 Jun 2012 02:58:21 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT002.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -20
X-BigFish: PS-20(zz98dI9371I1432Izz1202h1082kzz1033IL8275bh8275dhz2fh2a8h668h839h944he5bhf0ah)
Received-SPF: pass (mail109-am1: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT002.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail109-am1 (localhost.localdomain [127.0.0.1]) by mail109-am1 (MessageSwitch) id 1340333898921029_20599; Fri, 22 Jun 2012 02:58:18 +0000 (UTC)
Received: from AM1EHSMHS005.bigfish.com (unknown [10.3.201.237])	by mail109-am1.bigfish.com (Postfix) with ESMTP id DF35640004E; Fri, 22 Jun 2012 02:58:18 +0000 (UTC)
Received: from BL2PRD0710HT002.namprd07.prod.outlook.com (157.56.240.133) by AM1EHSMHS005.bigfish.com (10.3.207.105) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 22 Jun 2012 02:58:18 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.88]) by BL2PRD0710HT002.namprd07.prod.outlook.com ([10.255.102.37]) with mapi id 14.16.0164.004; Fri, 22 Jun 2012 02:59:45 +0000
From: Stephan Wenger <stewe@stewe.org>
To: IETF <ietf@ietf.org>
Subject: Re: Proposed Update to Note Well
Thread-Topic: Proposed Update to Note Well
Thread-Index: AQHNT/qtF8urOkUi9ECLOMdvpukpJJcE7kCAgAC08QD//42kAA==
Date: Fri, 22 Jun 2012 02:59:44 +0000
Message-ID: <CC092D26.884B8%stewe@stewe.org>
In-Reply-To: <AFB6264C-0EA2-4E7E-A98D-5EEFEF514958@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <ECD377403C9F9448B70F7C3B0B49949E@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 02:59:51 -0000

On 6.21.2012 19:49 , "Jorge Contreras" <cntreras@gmail.com> wrote:
>> So I call this a nit.  Still, thinking about a replacement for "own"
>>that=20
>> is more layman-friendly than "right to assert" would be a worthwhile
>>exercise

> The word would be "control".

Agreed.  And "control" sounds reasonably straightforward to me.
Stephan



>
>
>Sent from my iPhone
>
>On Jun 21, 2012, at 7:01 PM, Stephan Wenger <stewe@stewe.org> wrote:
>
>> Hi Russ, policy-folks,
>>=20
>> I support the simplification of the Note Well.
>>=20
>> Two concerns, one substantial and one nit, with respect to the language
>> proposed.
>>=20
>> The use of the work "know" in the context of requiring a disclosure is
>>IMO
>> substantially wrong.  It should be "believe".  Two reasons.  The
>>pragmatic
>> one: Positive "knowledge" of a patent covering a technology is not
>> something the IETF can expect from a layman.  The net result of this
>> language could well be that legal departments advise participants to
>>never
>> make disclosures, as they are not patent lawyers (let alone courts of
>>law)
>> that can reasonably make a determination of infringement.  Second, the
>> procedural reason:  Knowledge is not what BCP79 requires.  BCP79
>>requires
>> (in section 6) knowledge of IPR of which the contributor "believes" that
>> it covers, or may cover, the contribution.   According to my parsing of
>> English (and note that I'm not a native speaker), in the sentence
>> proposed, the "know" is attached to "covered" and not to the existence
>>of
>> a patent. =20
>>=20
>> The nit: "you or your employer own".  I believe that "own" is a close
>> enough (and practical enough) approximation of "right to assert", which
>>is
>> required in BCP79.  However, there are scenarios where one does not
>>"own"
>> IPR (in the sense of an assignment), but has the right to assert.  One
>> example would be an exclusive license.  In the light of recent legal
>> maneuvering (i.e. HTC asserting patents that they have borrowed from
>> Google--at least that is my understanding), language closer to BCP79's
>> language may be preferable.  Then again, the motivation of this exercise
>> appears to be to make the Note Well more accessible, and the language as
>> provided is not in contradiction with BCP79; it just leaves out one
>>exotic
>> class of cases.  So I call this a nit.  Still, thinking about a
>> replacement for "own" that is more layman-friendly than "right to
>>assert"
>> would be a worthwhile exercise
>
>The word would be "control".
>
>>=20
>> Regards,
>> Stephan
>>=20
>>=20
>> On 6.21.2012 15:10 , "IETF Chair" <chair@ietf.org> wrote:
>>=20
>>> The IESG has heard many complaints that the Note Well is too complex.
>>> After some discussion with counsel, we propose the following updated
>>>Note
>>> Well for your comment and review.  The below summary would be followed
>>> with a pointer to or text of more details, which will depend upon
>>>whether
>>> it's a meeting slide, on the web site, on the registration page, or on
>>>a
>>> mailing-list greeting.
>>>=20
>>> On behalf of the IESG,
>>> Russ Housley
>>> IETF Chair
>>>=20
>>> --------------------------------------
>>>=20
>>> NOTE WELL
>>>=20
>>> In summary:
>>>=20
>>>  By participating with the IETF, you agree to follow IETF processes.
>>>=20
>>>  If you write, say, or discuss anything in the IETF, formally or
>>> informally,
>>>  (all of which we call "a contribution") that you know is covered by a
>>> patent
>>>  or patent application you or your employer own, one of you must
>>> disclose
>>>  that.
>>>=20
>>>  You understand that meetings might be recorded and broadcast.
>>>=20
>>> This would be followed with a pointer to or text of more details,
>>> which will depend upon whether it's a meeting slide, on the web site,
>>> on the registration page, or on a mailing-list greeting.
>>>=20
>>>=20
>>=20
>>=20
>



From dwm@xpasc.com  Thu Jun 21 20:32:04 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CFE611E80BF for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 20:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=-3.900, BAYES_00=-2.599]
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 JH5THtRAKTGF for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 20:32:04 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id F40B411E8083 for <ietf@ietf.org>; Thu, 21 Jun 2012 20:32:03 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id F27A240537 for <ietf@ietf.org>; Fri, 22 Jun 2012 03:32:02 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id q5M3W2Q0019119 for <ietf@ietf.org>; Thu, 21 Jun 2012 20:32:02 -0700
Date: Thu, 21 Jun 2012 20:32:02 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: IETF <ietf@ietf.org>
Subject: Re: Proposed Update to Note Well
In-Reply-To: <tslzk7wdpyj.fsf@mit.edu>
Message-ID: <alpine.LRH.2.01.1206212030560.13613@egate.xpasc.com>
References: <4FCF5B92.3070703@qualcomm.com> <4FD0679D.60304@cisco.com> <4FD068BC.5050405@cs.tcd.ie> <CAP0PwYZb87zRv0HpTES1twLnnTWUk9ft80bupUoB5f62P3eL=A@mail.gmail.com> <4FD0A53A.6010406@innovationslab.net> <4FD0AAA5.3060400@cisco.com> <C07B527F-37D1-4340-BF7D-F1B6BD263726@gmail.com> <4FD0B3A1.7090001@qualcomm.com> <4FD0B3FA.90704@qualcomm.com> <CAP0PwYYjbaHqkk7z5dXBB4kcH=NhT5_MofHFpwpgXnXvBG_tKQ@mail.gmail.com> <4FD0B86E.8020008@qualcomm.com> <CALaySJKSzsgpmxaiTsHMAEBJNTyPGScMnsfTM=rbMiMEUREb6w@mail.gmail.com> <BD3F594E-0ED1-4079-836F-5D7F5D63AD91@harvard.edu> <CAP0PwYam-arXn1vYebn16d7b_paD7P9ZwKhG1aYgCo2yxuUWaQ@mail.gmail.com> <4FD0F8C5.8000100@qualcomm.com> <4FD10927.8020906@qualcomm.com> <CALaySJ+cMTbcsQQXTa4xhxS+0jBHah4XBXuHEeo4+i2iv1cRVg@mail.gmail.com> <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com> <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org> <4FE3C7DC.9050607@stpeter.im> <tslzk7wdpyj.fsf@mit.edu>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.24-gef8a08a
X-CLX-ID: a110AD3GD7Hu1vr-5L20323
X-CLX-Spam: false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 03:32:04 -0000

I agree .. Peter's version is clear and concise.

On Thu, 21 Jun 2012, Sam Hartman wrote:

> I like Peter's rephrasing  for a number of reasons.
> 
> 1) Clearly states who is responsible for making the disclosure happen
> (the IETf contributor)
> 
> 2) Defines IETf contribution in its own sentence which makes it easier
> to reference later.
> 
> 3) Makes it clear that things like mailing list conversations are
> covered.
> 

From jnc@mercury.lcs.mit.edu  Thu Jun 21 20:50:45 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0557811E80D0; Thu, 21 Jun 2012 20:50:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 SHCVRYFocZyq; Thu, 21 Jun 2012 20:50:44 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 71A5F11E80CD; Thu, 21 Jun 2012 20:50:42 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 7264D18C0F5; Thu, 21 Jun 2012 23:50:41 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Proposed Update to Note Well
Message-Id: <20120622035041.7264D18C0F5@mercury.lcs.mit.edu>
Date: Thu, 21 Jun 2012 23:50:41 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: iesg@ietf.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 03:50:45 -0000

    > From: Peter Saint-Andre <stpeter@stpeter.im>

    > With all due respect, that sentence could be improved.

Agree with others; splitting it up into two simpler sentences is an
improvement.

A tweak, though (you lost something in the second sentence):

   Anything that you write, say, or discuss in the IETF, formally or informally,
   either at an IETF meeting, or in another IETF venue, such as a mailing
   list, is an IETF contribution. If any contribution of yours is covered by
   a patent or patent application made by you or your employer, you or they
   must disclose that.

The original allowed the employer to make the disclosure (since, after all,
the employee may not know of all patent filings), and also had a positive
requirement to make such a disclosure; this revised one brings all that back.

	Noel

From abdussalambaryun@gmail.com  Thu Jun 21 20:57:50 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB73911E80CA for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 20:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 f-TFNBMDIGWo for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 20:57:50 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3E74111E8083 for <ietf@ietf.org>; Thu, 21 Jun 2012 20:57:50 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so766434vcq.31 for <ietf@ietf.org>; Thu, 21 Jun 2012 20:57:49 -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=OGotr9SpuOJJKjlpQKId8hy07hNSiPfvfRcvEzAHGnE=; b=Arbq7q+4AeSJudDPFtsaM+k+8i++RQBhEXiVtrwBCFPlN+FWpkyw5+8uaAIUJd6oTR foENDIV8Jcz6U9DzaRwkbELTqEfaBLPb2JDz6l34OJ7uQ4xO/KR65j2OXPTVXlFfX11R IL9J26imaDz9Y660aCWS+3bMRGFqFCJwqkl34CzW74+kKk/cSJJhQEo7afZoCztPnUwP VU9Cn9wZMuRK0boY3uMfVMfixZeEgV4I/ims4BW+UixB3Eb18aKFwZwl7zon4zVpbIfs bxRRKOb5jOP0eK8baXKa4F76ZWZC4Xpi5TNPLgl6T8ZKw75mnQEJdSlB9epbSvUmTcCS jFTQ==
MIME-Version: 1.0
Received: by 10.52.33.37 with SMTP id o5mr220741vdi.86.1340337469764; Thu, 21 Jun 2012 20:57:49 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Thu, 21 Jun 2012 20:57:49 -0700 (PDT)
In-Reply-To: <m2y5ng6p99.wl%randy@psg.com>
References: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com> <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com> <m2y5ng6p99.wl%randy@psg.com>
Date: Fri, 22 Jun 2012 05:57:49 +0200
Message-ID: <CADnDZ8-6VcRU-ZYWU01VqRSW9K--_QUAJtn5-4w+sPk-FhVWYQ@mail.gmail.com>
Subject: Re: Protocol Definition
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 03:57:50 -0000

On 6/22/12, Randy Bush <randy@psg.com> wrote:
>> All protocols in IETF are based on the Internet or/and the IP.
>
>
>    RFC 826

read in first page

[The purpose of this RFC is to present a method of Converting
Protocol Addresses (e.g., IP addresses) to Local Network
Addresses (e.g., Ethernet addresses). This is a issue of general
concern in the ARPA Internet community at this time. The
method proposed here is presented for your consideration and
comment. This is not the specification of a Internet Standard.]


>
> randy
>

From narten@us.ibm.com  Thu Jun 21 21:53:56 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8B8721F85A1 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 21:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 xEbjoLnqqCnQ for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 21:53:55 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 60E2C21F8599 for <ietf@ietf.org>; Thu, 21 Jun 2012 21:53:54 -0700 (PDT)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 21 Jun 2012 22:53:53 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 21 Jun 2012 22:53:50 -0600
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 151F43E40049 for <ietf@ietf.org>; Fri, 22 Jun 2012 04:53:49 +0000 (WET)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q5M4rJuV227544 for <ietf@ietf.org>; Thu, 21 Jun 2012 22:53:34 -0600
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q5M4s0B2008895 for <ietf@ietf.org>; Thu, 21 Jun 2012 22:54:00 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q5M4rxZn008884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 21 Jun 2012 22:54:00 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q5M4r2dU018871 for <ietf@ietf.org>; Fri, 22 Jun 2012 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q5M4r2qX018839 for ietf@ietf.org; Fri, 22 Jun 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201206220453.q5M4r2qX018839@rotala.raleigh.ibm.com>
Date: Fri, 22 Jun 2012 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12062204-4242-0000-0000-00000213DCC5
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 04:53:56 -0000

Total of 90 messages in the last 7 days.
 
script run at: Fri Jun 22 00:53:01 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 13.33% |   12 | 12.25% |   100292 | abdussalambaryun@gmail.com
 10.00% |    9 |  7.70% |    63054 | touch@isi.edu
 10.00% |    9 |  7.40% |    60622 | mohta@necom830.hpcl.titech.ac.jp
  3.33% |    3 |  8.63% |    70669 | gk@ninebynine.org
  2.22% |    2 |  5.04% |    41277 | stephen.farrell@cs.tcd.ie
  3.33% |    3 |  3.65% |    29879 | barryleiba@computer.org
  1.11% |    1 |  5.17% |    42315 | paul_sangster@symantec.com
  1.11% |    1 |  4.88% |    40005 | ron.even.tlv@gmail.com
  3.33% |    3 |  2.54% |    20818 | sm@resistor.net
  3.33% |    3 |  2.23% |    18225 | john-ietf@jck.com
  3.33% |    3 |  2.09% |    17131 | stpeter@stpeter.im
  2.22% |    2 |  2.75% |    22524 | tjc@ecs.soton.ac.uk
  2.22% |    2 |  2.53% |    20699 | duerst@it.aoyama.ac.jp
  2.22% |    2 |  2.36% |    19294 | stewe@stewe.org
  2.22% |    2 |  2.02% |    16530 | ynir@checkpoint.com
  2.22% |    2 |  1.87% |    15274 | chair@ietf.org
  2.22% |    2 |  1.82% |    14909 | vesely@tana.it
  2.22% |    2 |  1.51% |    12370 | melinda.shore@gmail.com
  2.22% |    2 |  1.51% |    12346 | johnl@iecc.com
  2.22% |    2 |  1.51% |    12329 | harald@alvestrand.no
  2.22% |    2 |  1.43% |    11721 | paul.hoffman@vpnc.org
  1.11% |    1 |  2.24% |    18382 | dan-ietf@danyork.org
  2.22% |    2 |  1.13% |     9264 | jnc@mercury.lcs.mit.edu
  1.11% |    1 |  1.11% |     9064 | edj.etc@gmail.com
  1.11% |    1 |  1.09% |     8930 | narten@us.ibm.com
  1.11% |    1 |  1.09% |     8923 | adrian@olddog.co.uk
  1.11% |    1 |  1.07% |     8744 | cntreras@gmail.com
  1.11% |    1 |  1.06% |     8644 | joelja@bogus.com
  1.11% |    1 |  1.00% |     8190 | ajs@anvilwalrusden.com
  1.11% |    1 |  0.99% |     8119 | scott.brim@gmail.com
  1.11% |    1 |  0.97% |     7926 | eburger-l@standardstrack.com
  1.11% |    1 |  0.86% |     7065 | jason_livingood@cable.comcast.com
  1.11% |    1 |  0.84% |     6872 | dcrocker@bbiw.net
  1.11% |    1 |  0.83% |     6830 | rbarnes@bbn.com
  1.11% |    1 |  0.74% |     6047 | jmpolk@cisco.com
  1.11% |    1 |  0.74% |     6045 | dwm@xpasc.com
  1.11% |    1 |  0.73% |     6014 | hartmans-ietf@mit.edu
  1.11% |    1 |  0.72% |     5924 | housley@vigilsec.com
  1.11% |    1 |  0.68% |     5599 | smb@cs.columbia.edu
  1.11% |    1 |  0.66% |     5397 | dhc@dcrocker.net
  1.11% |    1 |  0.57% |     4698 | randy@psg.com
--------+------+--------+----------+------------------------
100.00% |   90 |100.00% |   818960 | Total


From joelja@bogus.com  Thu Jun 21 22:16:32 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8543F21F8672 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 22:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 9c8iwNliSv2p for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 22:16:32 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id EDD2421F8671 for <ietf@ietf.org>; Thu, 21 Jun 2012 22:16:31 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q5M5GST2004358 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 22 Jun 2012 05:16:29 GMT (envelope-from joelja@bogus.com)
Message-ID: <4FE3FFAC.9010906@bogus.com>
Date: Thu, 21 Jun 2012 22:16:28 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Protocol Definition
References: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com> <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com> <m2y5ng6p99.wl%randy@psg.com> <CADnDZ8-6VcRU-ZYWU01VqRSW9K--_QUAJtn5-4w+sPk-FhVWYQ@mail.gmail.com>
In-Reply-To: <CADnDZ8-6VcRU-ZYWU01VqRSW9K--_QUAJtn5-4w+sPk-FhVWYQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 22 Jun 2012 05:16:30 +0000 (UTC)
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 05:16:32 -0000

On 6/21/12 20:57 , Abdussalam Baryun wrote:
> On 6/22/12, Randy Bush <randy@psg.com> wrote:
>>> All protocols in IETF are based on the Internet or/and the IP.
>>
>>
>>    RFC 826
> 
> read in first page
> 
> [The purpose of this RFC is to present a method of Converting
> Protocol Addresses (e.g., IP addresses) to Local Network
> Addresses (e.g., Ethernet addresses). This is a issue of general
> concern in the ARPA Internet community at this time. The
> method proposed here is presented for your consideration and
> comment. This is not the specification of a Internet Standard.]

http://tools.ietf.org/html/rfc5921

   This document specifies an architectural framework for the
   application of Multiprotocol Label Switching (MPLS) to the
   construction of packet-switched transport networks.  It describes a
   common set of protocol functions -- the MPLS Transport Profile (MPLS-
   TP) -- that supports the operational models and capabilities typical
   of such networks, including signaled or explicitly provisioned
   bidirectional connection-oriented paths, protection and restoration
   mechanisms, comprehensive Operations, Administration, and Maintenance
   (OAM) functions, and network operation in the absence of a dynamic
   control plane or IP forwarding support.
> 
>>
>> randy
>>
> 



From melinda.shore@gmail.com  Thu Jun 21 22:24:33 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D746B21F866B for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 22:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.481
X-Spam-Level: 
X-Spam-Status: No, score=-3.481 tagged_above=-999 required=5 tests=[AWL=0.118,  BAYES_00=-2.599, 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 sGpbSQ9bROAl for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 22:24:33 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC3C21F84FD for <ietf@ietf.org>; Thu, 21 Jun 2012 22:24:33 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so3138568pbc.31 for <ietf@ietf.org>; Thu, 21 Jun 2012 22:24:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=e15GZUZVIB0BSaTs+1Zl+yV3N6YCsa9jMI5aNjyDIAA=; b=K/hTIEb7/ZJFrASH+kxtRvseGNEr96k4nrmVVUbjNqInl29tI7XBXhf5091BYITC+L o4uQ513Dqq2u9JV3H9vKNJ+kXU7HeNXvN8FyaZ8XuA9MngQ3meHu5C1FdUwEVQ8hHd7d If4P0ANt14NtcIh14aDS7t3nd8Egp6Lp119/YFqzRlvHrB+X+zu6cV6IChCReisfwsDz E6vPmsRmxFxNETbqgkmXs/QMd3X/nrKad2ADGwUtUisqlQeJS0DqInHiQd0AJ0fd6Sh0 8uVpUWptk2gSVnP+doVSoHv30+xKNgLqvQfFUso1bhWqyFaZNFHj7qfY3+dZLHWaNgAV Bdow==
Received: by 10.68.194.201 with SMTP id hy9mr6331884pbc.69.1340342673016; Thu, 21 Jun 2012 22:24:33 -0700 (PDT)
Received: from spandex.local (216-67-47-144-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.47.144]) by mx.google.com with ESMTPS id ny10sm37859191pbb.38.2012.06.21.22.24.31 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Jun 2012 22:24:32 -0700 (PDT)
Message-ID: <4FE4018D.7040509@gmail.com>
Date: Thu, 21 Jun 2012 21:24:29 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Protocol Definition
References: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com> <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com> <m2y5ng6p99.wl%randy@psg.com> <CADnDZ8-6VcRU-ZYWU01VqRSW9K--_QUAJtn5-4w+sPk-FhVWYQ@mail.gmail.com> <4FE3FFAC.9010906@bogus.com>
In-Reply-To: <4FE3FFAC.9010906@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 05:24:34 -0000

On 6/21/12 9:16 PM, Joel jaeggli wrote:
> On 6/21/12 20:57 , Abdussalam Baryun wrote:
>> On 6/22/12, Randy Bush<randy@psg.com>  wrote:
>>>> All protocols in IETF are based on the Internet or/and the IP.

[ ... ]

> http://tools.ietf.org/html/rfc5921

I dunno - once you throw "based on the Internet" in there pretty
much anything goes.  Which is not to say that I think his definition
of "protocol" is helpful, since it does not appear to actually *be*
a definition.

But anyway, I was surprised by some of things for which I haven't
been able to find a definition in IETF documents - for example,
"state," although that's an extremely difficult term for which to do
an exhaustive search and it's very likely out there but hard to find.

Melinda


From salvatore.loreto@ericsson.com  Fri Jun 22 02:55:02 2012
Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA38A21F8606 for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 02:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 K-9+m4digHHg for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 02:55:02 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id A170F21F8600 for <ietf@ietf.org>; Fri, 22 Jun 2012 02:55:01 -0700 (PDT)
X-AuditID: c1b4fb25-b7fbf6d000002e5d-74-4fe440f25344
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 06.A1.11869.2F044EF4; Fri, 22 Jun 2012 11:54:58 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.264.0; Fri, 22 Jun 2012 11:54:58 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 367F02326	for <ietf@ietf.org>; Fri, 22 Jun 2012 12:54:58 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 4169853205	for <ietf@ietf.org>; Fri, 22 Jun 2012 12:54:58 +0300 (EEST)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id EF59F51624	for <ietf@ietf.org>; Fri, 22 Jun 2012 12:54:57 +0300 (EEST)
Message-ID: <4FE440F1.9060508@ericsson.com>
Date: Fri, 22 Jun 2012 12:54:57 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed Update to Note Well
References: <20120622035041.7264D18C0F5@mercury.lcs.mit.edu>
In-Reply-To: <20120622035041.7264D18C0F5@mercury.lcs.mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUyM+Jvre4nhyf+Bgf7zCyebZzP4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujPtTXApWclbcu/GOpYGxl72LkZNDQsBE4uf9dUwQtpjEhXvr 2UBsIYFTjBLX3kd3MXIB2RsYJWb9bmCFcM4zSnRtO8AC4RxilGj+8YMJwjnNKNFyaQszSD+v gLZE9/45YHNZBFQlVk8/C7aPTcBM4vlDiBpRgWSJ3vMNUPWCEidnPgGaysEhAmQffGwJEhYW 0JT4uew2E0hYSMBG4uT7eJAwp4CtRNPhdywgNjOQfWHOdShbXmL72znMEN+oSVw9t4kZ4hst id6znUwTGEVmIVk2C0n7LCTtCxiZVzEK5yZm5qSXG+mlFmUmFxfn5+kVp25iBIb3wS2/VXcw 3jkncohRmoNFSZzXeusefyGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2M8nN2FLJqi3ULxxZ+ cl1YGqj4pefcYdUsfdVpCxTl/ZwYL672kctgm+W+O2Ma861/y3/1NG7Weq74yqnSpLPsmunE Dx+Sj3cvLP77+deR5CdsljuE52n/qFU8l3V9Vdac4ifG3p1179p5XTVD1m9Lmapy/8DHmq0H D3HMjDJf/NyG7bXgxc7pSizFGYmGWsxFxYkAaXzAoD0CAAA=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 09:55:03 -0000

I like and support the idea of a brief summary that fits in one readable 
slide

+1 for the Peter's version as it clarifies what is an IETF contribution, 
and to the Noel tweak of the second sentence.


-- 
Salvatore Loreto, PhD
www.sloreto.com



On 6/22/12 6:50 AM, Noel Chiappa wrote:
>      >  From: Peter Saint-Andre<stpeter@stpeter.im>
>
>      >  With all due respect, that sentence could be improved.
>
> Agree with others; splitting it up into two simpler sentences is an
> improvement.
>
> A tweak, though (you lost something in the second sentence):
>
>     Anything that you write, say, or discuss in the IETF, formally or informally,
>     either at an IETF meeting, or in another IETF venue, such as a mailing
>     list, is an IETF contribution. If any contribution of yours is covered by
>     a patent or patent application made by you or your employer, you or they
>     must disclose that.
>
> The original allowed the employer to make the disclosure (since, after all,
> the employee may not know of all patent filings), and also had a positive
> requirement to make such a disclosure; this revised one brings all that back.
>
> 	Noel



From dan-ietf@danyork.org  Fri Jun 22 05:19:13 2012
Return-Path: <dan-ietf@danyork.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E35321F8674 for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 05:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.998
X-Spam-Level: 
X-Spam-Status: No, score=-2.998 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_57=0.6, 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 Tih7WL7Xdq7x for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 05:19:11 -0700 (PDT)
Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by ietfa.amsl.com (Postfix) with ESMTP id 436B521F85F3 for <ietf@ietf.org>; Fri, 22 Jun 2012 05:19:11 -0700 (PDT)
Received: by qcsg15 with SMTP id g15so1343975qcs.27 for <ietf@ietf.org>; Fri, 22 Jun 2012 05:19:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=+KzD+aBYTKTJKJzv5bnGfakH+uxoiLSCeHbR/vuf9zs=; b=bYnLPwxBndI2trkzDcmv6RxZUw4ZgiTwQpU4pGHhSb8akrkq7cuEXe2LnGZtwlEID4 oiDyA7w6lDfv5p62Dq4pcUYZHGtvpPih6QiR6RHwNkWFLAU4pziJ8tAXJYWBufPwilYS iG8hMA/QbvXB8cf1SLARt8ODkABQ2lemCPBlkpL4cjDnWk7BRv0JpHtU1J/L7kbzFoDc vGJf2pNJHpUW+oEXYzMmWq9tsxc++3NL5MysMLFgnJG/VvdIdp6powP7mjrplDRPm1VB IOfp/atLMeEqtVuqaigu/Gvq8XqURh/OAYbD5wetywj4MoCrfiYsf0sVgrSkeLwekMDf 9J9w==
Received: by 10.224.209.193 with SMTP id gh1mr5918929qab.21.1340367550516; Fri, 22 Jun 2012 05:19:10 -0700 (PDT)
Received: from [172.20.12.152] (cpe-74-75-92-114.maine.res.rr.com. [74.75.92.114]) by mx.google.com with ESMTPS id gb7sm69099069qab.12.2012.06.22.05.19.09 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 22 Jun 2012 05:19:10 -0700 (PDT)
Subject: Re: Proposed Update to Note Well
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_3043CB19-0D86-4DF9-A838-680FCD9D8C09"
From: Dan York <dan-ietf@danyork.org>
In-Reply-To: <4FE3C7DC.9050607@stpeter.im>
Date: Fri, 22 Jun 2012 08:19:07 -0400
Message-Id: <B5EDFFD5-2D3F-463D-BE1C-25678FF4ACE2@danyork.org>
References: <4FCF5B92.3070703@qualcomm.com> <4FCF6BD5.7080503@qualcomm.com> <4FCF8471.2050701@cisco.com> <AEF1278E-68D1-47D3-932A-8B4940E864A0@harvard.edu> <4FD0679D.60304@cisco.com> <4FD068BC.5050405@cs.tcd.ie> <CAP0PwYZb87zRv0HpTES1twLnnTWUk9ft80bupUoB5f62P3eL=A@mail.gmail.com> <4FD0A53A.6010406@innovationslab.net> <4FD0AAA5.3060400@cisco.com> <C07B527F-37D1-4340-BF7D-F1B6BD263726@gmail.com> <4FD0B3A1.7090001@qualcomm.com> <4FD0B3FA.90704@qualcomm.com> <CAP0PwYYjbaHqkk7z5dXBB4kcH=NhT5_MofHFpwpgXnXvBG_tKQ@mail.gmail.com> <4FD0B86E.8020008@qualcomm.com> <CALaySJKSzsgpmxaiTsHMAEBJNTyPGScMnsfTM=rbMiMEUREb6w@mail.gmail.com> <BD3F594E-0ED1-4079-836F-5D7F5D63AD91@harvard.edu> <CAP0PwYam-arXn1vYebn16d7b_paD7P9ZwKhG1aYgCo2yxuUWaQ@mail.gmail.com> <4FD0F8C5.8000100@qualcomm.com> <4FD10927.8020906@qualcomm.com> <CALaySJ+cMTbcsQQXTa4xhxS+0jBHah4XBXuHEeo4+i2iv1cRVg@mail.gmail.com> <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com> <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org> <4FE3C7D C.9050607@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQk58js+NlQ/Cgru7sV3hOF2qWQWa3SF8Ezb/Euazd5iJLpnjiRKqJj+2dTXeiaE/dZ5TXhK
Cc: IETF <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 12:19:13 -0000

--Apple-Mail=_3043CB19-0D86-4DF9-A838-680FCD9D8C09
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

+1 for Peter's version.  Very concise and clear.  Thanks for doing that, =
Peter.

Dan

On Jun 21, 2012, at 9:18 PM, Peter Saint-Andre wrote:

> I like the idea of a brief summary that can be shown on one readable
> slide at the beginning of each session, read aloud by a meeting chair,
> etc. Wordsmithing below.
>=20
> On 6/21/12 4:10 PM, IETF Chair wrote:
>=20
>>   If you write, say, or discuss anything in the IETF, formally or =
informally,
>>   (all of which we call "a contribution") that you know is covered by =
a patent
>>   or patent application you or your employer own, one of you must =
disclose
>>   that.
>=20
> With all due respect, that sentence could be improved. I suggest:
>=20
>   Anything that you write, say, or discuss in the IETF, formally or
> informally,
>   at an IETF meeting or in another IETF venue such as a mailing list,
> is an
>   IETF contribution. If you believe that a contribution of yours is
> covered by
>   a patent or a patent application made by you or your employer, you =
must
>   disclose it.
>=20
> Peter
>=20
> --=20
> Peter Saint-Andre
> https://stpeter.im/
>=20
>=20
>=20
>=20

--=20
Dan York  dyork@lodestar2.com
http://www.danyork.com/   skype:danyork
Phone: +1-802-735-1624
Twitter - http://twitter.com/danyork
--------------------------------------------------------
All comments and opinions are entirely my own and have no connection =
whatsoever to any employer, past or present. Indeed, by tomorrow even I =
might be disavowing these comments.
--------------------------------------------------------


--Apple-Mail=_3043CB19-0D86-4DF9-A838-680FCD9D8C09
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">+1 =
for Peter's version. &nbsp;Very concise and clear. &nbsp;Thanks for =
doing that, Peter.<div><br></div><div>Dan</div><div><br><div><div>On Jun =
21, 2012, at 9:18 PM, Peter Saint-Andre wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>I =
like the idea of a brief summary that can be shown on one =
readable<br>slide at the beginning of each session, read aloud by a =
meeting chair,<br>etc. Wordsmithing below.<br><br>On 6/21/12 4:10 PM, =
IETF Chair wrote:<br><br><blockquote type=3D"cite"> &nbsp;&nbsp;If you =
write, say, or discuss anything in the IETF, formally or =
informally,<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;(all =
of which we call "a contribution") that you know is covered by a =
patent<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;or patent =
application you or your employer own, one of you must =
disclose<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;that.<br></blockquote><br>With all due respect, that =
sentence could be improved. I suggest:<br><br> &nbsp;&nbsp;Anything that =
you write, say, or discuss in the IETF, formally or<br>informally,<br> =
&nbsp;&nbsp;at an IETF meeting or in another IETF venue such as a =
mailing list,<br>is an<br> &nbsp;&nbsp;IETF contribution. If you believe =
that a contribution of yours is<br>covered by<br> &nbsp;&nbsp;a patent =
or a patent application made by you or your employer, you must<br> =
&nbsp;&nbsp;disclose it.<br><br>Peter<br><br>-- <br>Peter =
Saint-Andre<br><a =
href=3D"https://stpeter.im/">https://stpeter.im/</a><br><br><br><br><br></=
div></blockquote></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">--&nbsp;<br>Dan York &nbsp;<a =
href=3D"mailto:dyork@lodestar2.com">dyork@lodestar2.com</a><br><a =
href=3D"http://www.danyork.com/">http://www.danyork.com/</a>&nbsp;&nbsp;&n=
bsp;<a href=3D"skype:danyork">skype:danyork</a><br>Phone: =
+1-802-735-1624<br>Twitter -&nbsp;<a =
href=3D"http://twitter.com/danyork">http://twitter.com/danyork</a></div><d=
iv style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
">--------------------------------------------------------</div></div><div=
 style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">All comments and opinions are =
entirely my own and have no connection whatsoever to any employer, past =
or present. Indeed, by tomorrow even I might be disavowing these =
comments.</div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
">--------------------------------------------------------</div></div></sp=
an></span>
</div>
<br></div></body></html>=

--Apple-Mail=_3043CB19-0D86-4DF9-A838-680FCD9D8C09--

From stpeter@stpeter.im  Fri Jun 22 07:36:45 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3B3D21F86D7; Fri, 22 Jun 2012 07:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.444
X-Spam-Level: 
X-Spam-Status: No, score=-102.444 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 cCgC3qB3UKBt; Fri, 22 Jun 2012 07:36:44 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id DE90121F8595; Fri, 22 Jun 2012 07:36:44 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E9F7D40092; Fri, 22 Jun 2012 08:54:24 -0600 (MDT)
Message-ID: <4FE47DB1.2080207@stpeter.im>
Date: Fri, 22 Jun 2012 08:14:09 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Proposed Update to Note Well
References: <20120622035041.7264D18C0F5@mercury.lcs.mit.edu>
In-Reply-To: <20120622035041.7264D18C0F5@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 14:36:45 -0000

On 6/21/12 9:50 PM, Noel Chiappa wrote:
>     > From: Peter Saint-Andre <stpeter@stpeter.im>
> 
>     > With all due respect, that sentence could be improved.
> 
> Agree with others; splitting it up into two simpler sentences is an
> improvement.
> 
> A tweak, though (you lost something in the second sentence):
> 
>    Anything that you write, say, or discuss in the IETF, formally or informally,
>    either at an IETF meeting, or in another IETF venue, such as a mailing
>    list, is an IETF contribution. If any contribution of yours is covered by
>    a patent or patent application made by you or your employer, you or they
>    must disclose that.
> 
> The original allowed the employer to make the disclosure (since, after all,
> the employee may not know of all patent filings), and also had a positive
> requirement to make such a disclosure; this revised one brings all that back.

At the risk of starting a long thread about "we all contribute as
individuals", I'll note that traditionally the IPR rules have applied to
real people, not corporations. It's not the employee's responsibility to
know of all patent filings, and our IPR rules don't make that
assumption; we say only that if you have such knowledge and you make a
contribution that is based on such knowledge, you need to disclose the
IPR. If you don't want to disclose, you don't need to make a
contribution. I suppose it is fine to say "you or they need to disclose
it", but leaving it up to the faceless "they" might give individuals the
idea that this is all about corporations and not about each of us as
individual participants at the IETF. And somehow we also lost the point
about "you know" or "you believe" along the way. Thus I'd be more
happier with something like this:

   Anything that you write, say, or discuss in the IETF, formally or
   informally, either at an IETF meeting or in another IETF venue
   such as a mailing list, is an IETF contribution.  If you believe that
   any contribution of yours is covered by a patent or patent
   application made by you or your employer, you must disclose
   that fact or arrange for your employer to disclose it on your behalf.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/





From stewe@stewe.org  Fri Jun 22 07:45:38 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6F9821F8620; Fri, 22 Jun 2012 07:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 GVf7Z1l7sesn; Fri, 22 Jun 2012 07:45:37 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe004.messaging.microsoft.com [216.32.180.14]) by ietfa.amsl.com (Postfix) with ESMTP id BEF7021F861A; Fri, 22 Jun 2012 07:45:36 -0700 (PDT)
Received: from mail46-va3-R.bigfish.com (10.7.14.244) by VA3EHSOBE001.bigfish.com (10.7.40.21) with Microsoft SMTP Server id 14.1.225.23; Fri, 22 Jun 2012 14:43:51 +0000
Received: from mail46-va3 (localhost [127.0.0.1])	by mail46-va3-R.bigfish.com (Postfix) with ESMTP id 39FCE3002FC; Fri, 22 Jun 2012 14:43:51 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT002.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -1
X-BigFish: PS-1(zzbb2dI98dI9371I1432Izz1202h1082kzzz2fh2a8h668h839h944he5bhf0ah)
Received-SPF: pass (mail46-va3: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT002.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail46-va3 (localhost.localdomain [127.0.0.1]) by mail46-va3 (MessageSwitch) id 1340376228847560_21870; Fri, 22 Jun 2012 14:43:48 +0000 (UTC)
Received: from VA3EHSMHS015.bigfish.com (unknown [10.7.14.247])	by mail46-va3.bigfish.com (Postfix) with ESMTP id C18382A0055; Fri, 22 Jun 2012 14:43:48 +0000 (UTC)
Received: from BL2PRD0710HT002.namprd07.prod.outlook.com (157.56.240.133) by VA3EHSMHS015.bigfish.com (10.7.99.25) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 22 Jun 2012 14:43:46 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.88]) by BL2PRD0710HT002.namprd07.prod.outlook.com ([10.255.102.37]) with mapi id 14.16.0164.004; Fri, 22 Jun 2012 14:45:15 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Peter Saint-Andre <stpeter@stpeter.im>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Proposed Update to Note Well
Thread-Topic: Proposed Update to Note Well
Thread-Index: AQHNUCoxF8urOkUi9ECLOMdvpukpJJcGYkCA//+TVYA=
Date: Fri, 22 Jun 2012 14:45:14 +0000
Message-ID: <CC09D19A.884F1%stewe@stewe.org>
In-Reply-To: <4FE47DB1.2080207@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B26583079ADF7E41AD43F35BC14A7887@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 14:45:39 -0000

On 6.22.2012 07:14 , "Peter Saint-Andre" <stpeter@stpeter.im> wrote:



   Anything that you write, say, or discuss in the IETF, formally or
   informally, either at an IETF meeting or in another IETF venue
   such as a mailing list, is an IETF contribution.  If you believe that
   any contribution of yours is covered by a patent or patent
   application made by you or your employer, you must disclose
   that fact or arrange for your employer to disclose it on your behalf.


s/made by you or your employer/controlled by you or your employer/

And I would remove "on your behalf", as it a) adds to the word count, and
b) could be viewed as a requirement to fill in the section III of the
disclosure form--something that is neither common practice nor, IMO, overly
useful.

Stephan

>On 6/21/12 9:50 PM, Noel Chiappa wrote:
>>     > From: Peter Saint-Andre <stpeter@stpeter.im>
>>=20
>>     > With all due respect, that sentence could be improved.
>>=20
>> Agree with others; splitting it up into two simpler sentences is an
>> improvement.
>>=20
>> A tweak, though (you lost something in the second sentence):
>>=20
>>    Anything that you write, say, or discuss in the IETF, formally or
>>informally,
>>    either at an IETF meeting, or in another IETF venue, such as a
>>mailing
>>    list, is an IETF contribution. If any contribution of yours is
>>covered by
>>    a patent or patent application made by you or your employer, you or
>>they
>>    must disclose that.
>>=20
>> The original allowed the employer to make the disclosure (since, after
>>all,
>> the employee may not know of all patent filings), and also had a
>>positive
>> requirement to make such a disclosure; this revised one brings all that
>>back.
>
>At the risk of starting a long thread about "we all contribute as
>individuals", I'll note that traditionally the IPR rules have applied to
>real people, not corporations. It's not the employee's responsibility to
>know of all patent filings, and our IPR rules don't make that
>assumption; we say only that if you have such knowledge and you make a
>contribution that is based on such knowledge, you need to disclose the
>IPR. If you don't want to disclose, you don't need to make a
>contribution. I suppose it is fine to say "you or they need to disclose
>it", but leaving it up to the faceless "they" might give individuals the
>idea that this is all about corporations and not about each of us as
>individual participants at the IETF. And somehow we also lost the point
>about "you know" or "you believe" along the way. Thus I'd be more
>happier with something like this:
>
>   Anything that you write, say, or discuss in the IETF, formally or
>   informally, either at an IETF meeting or in another IETF venue
>   such as a mailing list, is an IETF contribution.  If you believe that
>   any contribution of yours is covered by a patent or patent
>   application made by you or your employer, you must disclose
>   that fact or arrange for your employer to disclose it on your behalf.
>
>Peter
>
>--=20
>Peter Saint-Andre
>https://stpeter.im/
>
>
>
>
>



From stpeter@stpeter.im  Fri Jun 22 08:12:20 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0C7521F86FE; Fri, 22 Jun 2012 08:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.451
X-Spam-Level: 
X-Spam-Status: No, score=-102.451 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4nDJ5zGBmUAl; Fri, 22 Jun 2012 08:12:19 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C7A3D21F86F8; Fri, 22 Jun 2012 08:12:19 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 1A9FE40092; Fri, 22 Jun 2012 09:30:00 -0600 (MDT)
Message-ID: <4FE48B52.3080900@stpeter.im>
Date: Fri, 22 Jun 2012 09:12:18 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Proposed Update to Note Well
References: <CC09D19A.884F1%stewe@stewe.org>
In-Reply-To: <CC09D19A.884F1%stewe@stewe.org>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org" <iesg@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:12:21 -0000

On 6/22/12 8:45 AM, Stephan Wenger wrote:
> On 6.22.2012 07:14 , "Peter Saint-Andre" <stpeter@stpeter.im> wrote:
> 
> 
> 
>    Anything that you write, say, or discuss in the IETF, formally or
>    informally, either at an IETF meeting or in another IETF venue
>    such as a mailing list, is an IETF contribution.  If you believe that
>    any contribution of yours is covered by a patent or patent
>    application made by you or your employer, you must disclose
>    that fact or arrange for your employer to disclose it on your behalf.
> 
> 
> s/made by you or your employer/controlled by you or your employer/
> 
> And I would remove "on your behalf", as it a) adds to the word count, and
> b) could be viewed as a requirement to fill in the section III of the
> disclosure form--something that is neither common practice nor, IMO, overly
> useful.

You're right on both counts. So (and addressing Randy's concern):

   Anything that you write, say, or discuss in the IETF, formally or
   informally, either at an IETF meeting or in another IETF venue
   such as a mailing list, is an IETF contribution.  If you believe
   that any contribution of yours is covered by a patent or patent
   application controlled by you or an organization with which you
   are affiliated, you must disclose it or arrange for that
   organization to disclose it.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/





From barryleiba@gmail.com  Fri Jun 22 08:27:15 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE5021F86B2; Fri, 22 Jun 2012 08:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.944
X-Spam-Level: 
X-Spam-Status: No, score=-102.944 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ZfrQgHPoUyUH; Fri, 22 Jun 2012 08:27:13 -0700 (PDT)
Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by ietfa.amsl.com (Postfix) with ESMTP id 8F34221F8687; Fri, 22 Jun 2012 08:27:13 -0700 (PDT)
Received: by qcsg15 with SMTP id g15so1513052qcs.27 for <multiple recipients>; Fri, 22 Jun 2012 08:27:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=wsmQavpekCA3PbRjHOfP5IR+J1UVY6R9tNw8zIptlwA=; b=zxNYqLwmEkz8URmjrZRA41ATNMqZ7uwLUp+Df+i2+Nmr9//DUS/HjUe5w+BRgC0DN/ qZYWMn01EpuGRtoS5VONuv9ZHjArD7lKNA7g7cO1wBjOHtrxxHqT3Ir0wb10jwzHLCLZ 08XKfizn9/JMBAemo0T2+rwsZOAXzPH2X0ejuwieiscU73vdA3n5ePEhiyq0W8pcZbdB iUT7IppdjfD9AksTYUhU2M1R1p1BnTW2XrjAdZgYpqaN7WHi0Q0IV/tdgV4BtmWq2kVh JM9wAkehmpj8higQQbiUqdoEILwK88hIZHY0RcPi5bqBife//J3HUjmdaSjGvLTblIHX kBmA==
MIME-Version: 1.0
Received: by 10.224.200.194 with SMTP id ex2mr6942311qab.58.1340378833012; Fri, 22 Jun 2012 08:27:13 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.229.245.85 with HTTP; Fri, 22 Jun 2012 08:27:12 -0700 (PDT)
In-Reply-To: <4FE48B52.3080900@stpeter.im>
References: <CC09D19A.884F1%stewe@stewe.org> <4FE48B52.3080900@stpeter.im>
Date: Fri, 22 Jun 2012 11:27:12 -0400
X-Google-Sender-Auth: PnaLMaaUGxPbboTMiH92dD48xjc
Message-ID: <CALaySJ+1a13uKSLRbdUzadZLBVzrer5tkWAwoyNX-DyNLC5FTQ@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
From: Barry Leiba <barryleiba@computer.org>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:27:15 -0000

> You're right on both counts. So (and addressing Randy's concern):
>
> =A0 Anything that you write, say, or discuss in the IETF, formally or
> =A0 informally, either at an IETF meeting or in another IETF venue
> =A0 such as a mailing list, is an IETF contribution. =A0If you believe
> =A0 that any contribution of yours is covered by a patent or patent
> =A0 application controlled by you or an organization with which you
> =A0 are affiliated, you must disclose it or arrange for that
> =A0 organization to disclose it.

While I like the words, I'll note that we have now about doubled the
length from the version we started this thread with.  Remember that
the point was to have it be *very* brief, something that we can
reasonable expect people to read on the screen, and chairs to read
aloud in meetings without its sounding like the disclaimer on a
pharmaceutical advert.  And remember that it's not meant to tell you
everything you need to know, ever -- only to remind you of the
significant point, and to refer you elsewhere for details.

Given that, does the community really want this version?  Does the
community think it will meet those needs, and that it will really work
to be read aloud in roughly 40 sessions a day for five days?

Barry

From jnc@mercury.lcs.mit.edu  Fri Jun 22 08:45:44 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D49DF21F86C4; Fri, 22 Jun 2012 08:45:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 vCZd1vxG8SXL; Fri, 22 Jun 2012 08:45:44 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 3C68721F86C1; Fri, 22 Jun 2012 08:45:44 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 5949218C119; Fri, 22 Jun 2012 11:45:43 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Proposed Update to Note Well
Message-Id: <20120622154543.5949218C119@mercury.lcs.mit.edu>
Date: Fri, 22 Jun 2012 11:45:43 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: iesg@ietf.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:45:45 -0000

    > From: Peter Saint-Andre <stpeter@stpeter.im>

    > traditionally the IPR rules have applied to real people

Well, like you, I don't want to get into a rathole on this. Yes, nothing we
do can absolutely stop patents going unknown about (e.g. patents from
entities which don't participate), but I would prefer to be as expansive as
possible, and try and drag parent organizations in too, to the degree we can
(we have already, IIRC, had cases where an organization knew of a patent, but
a particular individual did not). IANAL, of course, but I assume since the
original attorney-generated text did include this concept, there was some
valid legal foundation for doing so.

    > And somehow we also lost the point about "you know" or "you believe"
    > along the way.

That was deliberate. To me, "believe" is a loophole big enough to drive a
truck through. Things either are, or are not, covered by a patent. (Yes, yes,
I know: legally speaking, that's not so until a finder of fact makes that
determination.) But leaving out the 'believe' means you can't say 'well, _I_
didn't think it applied' - leaving it out implies a duty to take in a wider
circle of assessment of whether it applies than simply one's personal guess.
Plus it also makes the text shorter.. :-)

	Noel

From stpeter@stpeter.im  Fri Jun 22 08:46:05 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6497821F870A; Fri, 22 Jun 2012 08:46:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.462
X-Spam-Level: 
X-Spam-Status: No, score=-102.462 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 AWJBXpBAp+9B; Fri, 22 Jun 2012 08:46:04 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id EDA9221F8713; Fri, 22 Jun 2012 08:46:03 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 93F7F40092; Fri, 22 Jun 2012 10:03:40 -0600 (MDT)
Message-ID: <4FE49336.4000203@stpeter.im>
Date: Fri, 22 Jun 2012 09:45:58 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Proposed Update to Note Well
References: <CC09D19A.884F1%stewe@stewe.org> <4FE48B52.3080900@stpeter.im> <CALaySJ+1a13uKSLRbdUzadZLBVzrer5tkWAwoyNX-DyNLC5FTQ@mail.gmail.com>
In-Reply-To: <CALaySJ+1a13uKSLRbdUzadZLBVzrer5tkWAwoyNX-DyNLC5FTQ@mail.gmail.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:46:05 -0000

On 6/22/12 9:27 AM, Barry Leiba wrote:
>> You're right on both counts. So (and addressing Randy's concern):
>>
>>   Anything that you write, say, or discuss in the IETF, formally or
>>   informally, either at an IETF meeting or in another IETF venue
>>   such as a mailing list, is an IETF contribution.  If you believe
>>   that any contribution of yours is covered by a patent or patent
>>   application controlled by you or an organization with which you
>>   are affiliated, you must disclose it or arrange for that
>>   organization to disclose it.
> 
> While I like the words, I'll note that we have now about doubled the
> length from the version we started this thread with.  Remember that
> the point was to have it be *very* brief, something that we can
> reasonable expect people to read on the screen, and chairs to read
> aloud in meetings without its sounding like the disclaimer on a
> pharmaceutical advert.  And remember that it's not meant to tell you
> everything you need to know, ever -- only to remind you of the
> significant point, and to refer you elsewhere for details.
> 
> Given that, does the community really want this version?  Does the
> community think it will meet those needs, and that it will really work
> to be read aloud in roughly 40 sessions a day for five days?

Lawyers and spec writers are not known for brevity. :)

Here's something really short:

   By participating here, you agree to follow IETF processes.

   If you actively contribute and you believe that what you
   contribute is controlled by patents, you need to disclose that.

   You understand that meetings might be recorded and broadcast.

Then just point to a longer version for everything else.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From ajs@anvilwalrusden.com  Fri Jun 22 08:46:32 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55FE921F86FD; Fri, 22 Jun 2012 08:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 zGDqO+Xpk9bk; Fri, 22 Jun 2012 08:46:31 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB9D21F8759; Fri, 22 Jun 2012 08:46:31 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id AA6651ECB41D; Fri, 22 Jun 2012 15:46:17 +0000 (UTC)
Date: Fri, 22 Jun 2012 11:46:16 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Proposed Update to Note Well
Message-ID: <20120622154616.GF44040@mail.yitter.info>
References: <CC09D19A.884F1%stewe@stewe.org> <4FE48B52.3080900@stpeter.im> <CALaySJ+1a13uKSLRbdUzadZLBVzrer5tkWAwoyNX-DyNLC5FTQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALaySJ+1a13uKSLRbdUzadZLBVzrer5tkWAwoyNX-DyNLC5FTQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:46:32 -0000

Hi,

On Fri, Jun 22, 2012 at 11:27:12AM -0400, Barry Leiba wrote:

> reasonable expect people to read on the screen, and chairs to read
> aloud in meetings without its sounding like the disclaimer on a
> pharmaceutical advert. 

If the chairs are going to read boilerplate in meetings all week long,
it's going to sound like such a disclaimer anyway.  I'm happy about
the "short", but I don't understand the reason that the notice will
need to be read out loud.  Is such a requirement the plan?  If so,
why?

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From barryleiba@gmail.com  Fri Jun 22 08:49:45 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B09B21F8713; Fri, 22 Jun 2012 08:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.945
X-Spam-Level: 
X-Spam-Status: No, score=-102.945 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 nU2Q4ZQdpYiS; Fri, 22 Jun 2012 08:49:45 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id DBA8B21F86FE; Fri, 22 Jun 2012 08:49:44 -0700 (PDT)
Received: by qadz3 with SMTP id z3so435397qad.10 for <multiple recipients>; Fri, 22 Jun 2012 08:49:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=+LD9vkcYo9LHDqINVuU069sxzY0stf/PKav306Y3Cw0=; b=YlrwVEmOSwabYnHk2/KTCp6HdEkddUqi52huUPrMW6vKqMZZFQY0p0IMbjEjtDR5px AM+reUU47qLiZkThcLEeZSgLAQcA3qTKDUTihxY5QRpqZOCuDsHtRVL8SNBNyRcqt6pa PN3vnPHZV8gCXC0cU8X3rDI4EYiphfSaCRBQLueHrcdKOlg/4L9WyrsIQdtGTPVKHxmj s7ekB4bCkEJrS2JdvUqrbm3dUp2uxnhsEunwhW5DZ25G3kWwmwUrz42d1TJ60JIZ+VyC Paodo7JheJzzOgDbobz/LDp/4TCNl5hp7TWwqS4NdEItzXGoPWmUZKGERuOboyMYEpp6 N5Fg==
MIME-Version: 1.0
Received: by 10.229.135.196 with SMTP id o4mr1310639qct.154.1340380184260; Fri, 22 Jun 2012 08:49:44 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.229.245.85 with HTTP; Fri, 22 Jun 2012 08:49:43 -0700 (PDT)
In-Reply-To: <20120622154616.GF44040@mail.yitter.info>
References: <CC09D19A.884F1%stewe@stewe.org> <4FE48B52.3080900@stpeter.im> <CALaySJ+1a13uKSLRbdUzadZLBVzrer5tkWAwoyNX-DyNLC5FTQ@mail.gmail.com> <20120622154616.GF44040@mail.yitter.info>
Date: Fri, 22 Jun 2012 11:49:43 -0400
X-Google-Sender-Auth: mw-c_Ncd8a7Ed87IZPoSt6s-uH0
Message-ID: <CALaySJ+b=DvAxEJGoo2yBMBar+1XQ0+3NhXSCd9hcLCqbT3xHQ@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
From: Barry Leiba <barryleiba@computer.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:49:45 -0000

> If the chairs are going to read boilerplate in meetings all week long,
> it's going to sound like such a disclaimer anyway. =A0I'm happy about
> the "short", but I don't understand the reason that the notice will
> need to be read out loud. =A0Is such a requirement the plan? =A0If so,
> why?

No, no... no *requirement*.  We just want it to be concise enough so
that it *can* reasonably be done.  It's kind of the test: if it's too
long for that, then it's probably too long.  The current Note Well
says what needs to be said, but makes everyone's eyes glaze over.

Barry

From stpeter@stpeter.im  Fri Jun 22 08:51:24 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B2C221F8741; Fri, 22 Jun 2012 08:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.468
X-Spam-Level: 
X-Spam-Status: No, score=-102.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 u4jZX08WLnoZ; Fri, 22 Jun 2012 08:51:23 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id D0CD921F86FE; Fri, 22 Jun 2012 08:51:23 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4B1E2400F9; Fri, 22 Jun 2012 10:09:04 -0600 (MDT)
Message-ID: <4FE4947A.7040905@stpeter.im>
Date: Fri, 22 Jun 2012 09:51:22 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Proposed Update to Note Well
References: <20120622154543.5949218C119@mercury.lcs.mit.edu>
In-Reply-To: <20120622154543.5949218C119@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:51:24 -0000

On 6/22/12 9:45 AM, Noel Chiappa wrote:
>     > From: Peter Saint-Andre <stpeter@stpeter.im>>
>
>     > And somehow we also lost the point about "you know" or "you believe"
>     > along the way.
> 
> That was deliberate. To me, "believe" is a loophole big enough to drive a
> truck through. 

You're right. I was just trying to incorporate consensus. ;-)

So:

   By participating here, you agree to follow IETF processes.

   If you actively contribute and you know that your contribution
   is controlled by patents, you need to disclose that.

   You understand that meetings might be recorded and broadcast.

   Refer to <foo> for details.

/psa


From stewe@stewe.org  Fri Jun 22 08:51:58 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4437621F8589; Fri, 22 Jun 2012 08:51:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 H1h2Gk+Krxyg; Fri, 22 Jun 2012 08:51:57 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe004.messaging.microsoft.com [216.32.181.184]) by ietfa.amsl.com (Postfix) with ESMTP id 26F4821F858E; Fri, 22 Jun 2012 08:51:57 -0700 (PDT)
Received: from mail128-ch1-R.bigfish.com (10.43.68.235) by CH1EHSOBE008.bigfish.com (10.43.70.58) with Microsoft SMTP Server id 14.1.225.23; Fri, 22 Jun 2012 15:50:26 +0000
Received: from mail128-ch1 (localhost [127.0.0.1])	by mail128-ch1-R.bigfish.com (Postfix) with ESMTP id 9828C3604BA; Fri, 22 Jun 2012 15:50:26 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT005.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -1
X-BigFish: PS-1(zzbb2dI98dI9371I1432Izz1202h1082kzzz2fh2a8h668h839h944he5bhf0ah)
Received-SPF: pass (mail128-ch1: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT005.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail128-ch1 (localhost.localdomain [127.0.0.1]) by mail128-ch1 (MessageSwitch) id 1340380224721649_6207; Fri, 22 Jun 2012 15:50:24 +0000 (UTC)
Received: from CH1EHSMHS022.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.250])	by mail128-ch1.bigfish.com (Postfix) with ESMTP id A275F240045;	Fri, 22 Jun 2012 15:50:24 +0000 (UTC)
Received: from BL2PRD0710HT005.namprd07.prod.outlook.com (157.56.240.133) by CH1EHSMHS022.bigfish.com (10.43.70.22) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 22 Jun 2012 15:50:24 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.88]) by BL2PRD0710HT005.namprd07.prod.outlook.com ([10.255.102.40]) with mapi id 14.16.0164.004; Fri, 22 Jun 2012 15:51:53 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Peter Saint-Andre <stpeter@stpeter.im>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Proposed Update to Note Well
Thread-Topic: Proposed Update to Note Well
Thread-Index: AQHNUCoxF8urOkUi9ECLOMdvpukpJJcGYkCA//+TVYCAAHzqAP//la+A
Date: Fri, 22 Jun 2012 15:51:52 +0000
Message-ID: <CC09DC18.88502%stewe@stewe.org>
In-Reply-To: <4FE48B52.3080900@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8CCC1B043969D9488C173C32E88F8AB3@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:51:58 -0000

Hi Noel,

"Affiliate" is overly broad, and undefined and therefore not
supported by BCP79.  It cannot be reasonably expected of an IETF
participant to have an objective view of with whom he/she is affiliated.

One (the most?) common definition of "affiliate" used in contracts
results in a sweep in of any corporate entity that is controlled,
or controls, another entity, including individuals.  Recursively.
As there is no definition of "affiliate" in BCP79, we have to assume
such a common definition.

Now, I'm affiliated with IEEE, and so is John Doe, who controls a
patent of which I believe it may be necessary to practice a draft.
I happen to be aware of John Doe's patent because John Doe is a former
colleague of mine, but other than that, and our IEEE memberships, there
Is no other connection between John Doe and myself.  I surely
do not have an disclosure obligation based on our joint affiliation
with IEEE?

Using affiliate would IMO be a policy change through the back door.

I would rather strongly suggest to stick with vocabulary available in
BCP79.
The formulation used in BCP79 is "employer or sponsor".  Wordcount +=3D2  :=
-(

Stephan

On 6.22.2012 08:12 , "Peter Saint-Andre" <stpeter@stpeter.im> wrote:

>On 6/22/12 8:45 AM, Stephan Wenger wrote:
>> On 6.22.2012 07:14 , "Peter Saint-Andre" <stpeter@stpeter.im> wrote:
>>=20
>>=20
>>=20
>>    Anything that you write, say, or discuss in the IETF, formally or
>>    informally, either at an IETF meeting or in another IETF venue
>>    such as a mailing list, is an IETF contribution.  If you believe that
>>    any contribution of yours is covered by a patent or patent
>>    application made by you or your employer, you must disclose
>>    that fact or arrange for your employer to disclose it on your behalf.
>>=20
>>=20
>> s/made by you or your employer/controlled by you or your employer/
>>=20
>> And I would remove "on your behalf", as it a) adds to the word count,
>>and
>> b) could be viewed as a requirement to fill in the section III of the
>> disclosure form--something that is neither common practice nor, IMO,
>>overly
>> useful.
>
>You're right on both counts. So (and addressing Randy's concern):
>
>   Anything that you write, say, or discuss in the IETF, formally or
>   informally, either at an IETF meeting or in another IETF venue
>   such as a mailing list, is an IETF contribution.  If you believe
>   that any contribution of yours is covered by a patent or patent
>   application controlled by you or an organization with which you
>   are affiliated, you must disclose it or arrange for that
>   organization to disclose it.
>
>Peter
>
>--=20
>Peter Saint-Andre
>https://stpeter.im/
>
>
>
>
>



From jnc@mercury.lcs.mit.edu  Fri Jun 22 08:56:01 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E282821F8789 for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 08:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 RJJHRtKCmm-5 for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 08:56:01 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 635B421F8779 for <ietf@ietf.org>; Fri, 22 Jun 2012 08:56:01 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1C9B518C119; Fri, 22 Jun 2012 11:56:01 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Proposed Update to Note Well
Message-Id: <20120622155601.1C9B518C119@mercury.lcs.mit.edu>
Date: Fri, 22 Jun 2012 11:56:01 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:56:02 -0000

    > From: Stephan Wenger <stewe@stewe.org>

    > Hi Noel,
    > "Affiliate" is overly broad, and undefined and therefore not supported
    > by BCP79. 

??? My suggested text did not include "affiliate"? Maybe you're looking at
someone else's text?

	Noel

From stewe@stewe.org  Fri Jun 22 09:03:47 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A216321F870A; Fri, 22 Jun 2012 09:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 LPRhwbrhwAXT; Fri, 22 Jun 2012 09:03:47 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe002.messaging.microsoft.com [213.199.154.205]) by ietfa.amsl.com (Postfix) with ESMTP id 89D5321F874F; Fri, 22 Jun 2012 09:03:46 -0700 (PDT)
Received: from mail13-am1-R.bigfish.com (10.3.201.238) by AM1EHSOBE005.bigfish.com (10.3.204.25) with Microsoft SMTP Server id 14.1.225.23; Fri, 22 Jun 2012 16:02:15 +0000
Received: from mail13-am1 (localhost [127.0.0.1])	by mail13-am1-R.bigfish.com (Postfix) with ESMTP id 2A1CB20256; Fri, 22 Jun 2012 16:02:15 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT004.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -1
X-BigFish: PS-1(zzbb2dI98dI9371I1432Izz1202h1082kzzz2fh2a8h668h839h944he5bhf0ah)
Received-SPF: pass (mail13-am1: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT004.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail13-am1 (localhost.localdomain [127.0.0.1]) by mail13-am1 (MessageSwitch) id 1340380932611852_17977; Fri, 22 Jun 2012 16:02:12 +0000 (UTC)
Received: from AM1EHSMHS006.bigfish.com (unknown [10.3.201.235])	by mail13-am1.bigfish.com (Postfix) with ESMTP id 8F41B160049; Fri, 22 Jun 2012 16:02:12 +0000 (UTC)
Received: from BL2PRD0710HT004.namprd07.prod.outlook.com (157.56.240.133) by AM1EHSMHS006.bigfish.com (10.3.207.106) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 22 Jun 2012 16:02:10 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.88]) by BL2PRD0710HT004.namprd07.prod.outlook.com ([10.255.102.39]) with mapi id 14.16.0164.004; Fri, 22 Jun 2012 16:03:33 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Peter Saint-Andre <stpeter@stpeter.im>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Proposed Update to Note Well
Thread-Topic: Proposed Update to Note Well
Thread-Index: AQHNUI4UF8urOkUi9ECLOMdvpukpJJcGfKEA//+OCQA=
Date: Fri, 22 Jun 2012 16:03:32 +0000
Message-ID: <CC09E33B.88542%stewe@stewe.org>
In-Reply-To: <4FE4947A.7040905@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8D5C019B411B844EBCF09A8432328FA2@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 16:03:47 -0000

Strike "actively".  It's a loophole and adds no value.

I don't know how a "contribution" can be "controlled" by
a patent. =20

Using "related" as the broadest possible term that IMO
may just be supported by BCP79:

   "If you believe  that a patent controlled by your employer
   or sponsor is related to your contribution, then you must
   disclose that patent."

I'm quite sure that the term "believe" is appropriate.  It's not
the Note Well that allows trucks go through, it's BCP79.  However,
ignoring my own advice (stick to terminology used in BCP79) I may
settle for "aware of":
  =20
   "If you are aware of a patent controlled by your employer
   or sponsor that is related to your contribution, then you must
   disclose that patent."


Stephan


On 6.22.2012 08:51 , "Peter Saint-Andre" <stpeter@stpeter.im> wrote:

>On 6/22/12 9:45 AM, Noel Chiappa wrote:
>>     > From: Peter Saint-Andre <stpeter@stpeter.im>>
>>
>>     > And somehow we also lost the point about "you know" or "you
>>believe"
>>     > along the way.
>>=20
>> That was deliberate. To me, "believe" is a loophole big enough to drive
>>a
>> truck through.=20
>
>You're right. I was just trying to incorporate consensus. ;-)
>
>So:
>
>   By participating here, you agree to follow IETF processes.
>
>   If you actively contribute and you know that your contribution
>   is controlled by patents, you need to disclose that.
>
>   You understand that meetings might be recorded and broadcast.
>
>   Refer to <foo> for details.
>
>/psa
>
>



From stewe@stewe.org  Fri Jun 22 09:04:39 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F2721F87AD for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 09:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Sj8DiN1qEPWu for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 09:04:36 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id 6C98621F87B1 for <ietf@ietf.org>; Fri, 22 Jun 2012 09:04:34 -0700 (PDT)
Received: from mail28-tx2-R.bigfish.com (10.9.14.238) by TX2EHSOBE014.bigfish.com (10.9.40.34) with Microsoft SMTP Server id 14.1.225.23; Fri, 22 Jun 2012 16:03:04 +0000
Received: from mail28-tx2 (localhost [127.0.0.1])	by mail28-tx2-R.bigfish.com (Postfix) with ESMTP id 0F23AA02B5; Fri, 22 Jun 2012 16:03:04 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT002.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 1
X-BigFish: PS1(zz98dI1432Izz1202h1082kzz8275dhz2fh2a8h668h839h944he5bhf0ah)
Received-SPF: pass (mail28-tx2: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT002.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail28-tx2 (localhost.localdomain [127.0.0.1]) by mail28-tx2 (MessageSwitch) id 1340380981541156_16305; Fri, 22 Jun 2012 16:03:01 +0000 (UTC)
Received: from TX2EHSMHS009.bigfish.com (unknown [10.9.14.241])	by mail28-tx2.bigfish.com (Postfix) with ESMTP id 748E920058; Fri, 22 Jun 2012 16:03:01 +0000 (UTC)
Received: from BL2PRD0710HT002.namprd07.prod.outlook.com (157.56.240.133) by TX2EHSMHS009.bigfish.com (10.9.99.109) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 22 Jun 2012 16:03:00 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.88]) by BL2PRD0710HT002.namprd07.prod.outlook.com ([10.255.102.37]) with mapi id 14.16.0164.004; Fri, 22 Jun 2012 16:04:26 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Proposed Update to Note Well
Thread-Topic: Proposed Update to Note Well
Thread-Index: AQHNUI+FF8urOkUi9ECLOMdvpukpJJcGCumA
Date: Fri, 22 Jun 2012 16:04:26 +0000
Message-ID: <CC09E582.88557%stewe@stewe.org>
In-Reply-To: <20120622155601.1C9B518C119@mercury.lcs.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4EB063D4E5870D40AD12AADAD14364BF@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 16:04:39 -0000

Oh, sorry.  Incorrect citing.  Too many messages in too short a time.
Stephan

On 6.22.2012 08:56 , "Noel Chiappa" <jnc@mercury.lcs.mit.edu> wrote:

>    > From: Stephan Wenger <stewe@stewe.org>
>
>    > Hi Noel,
>    > "Affiliate" is overly broad, and undefined and therefore not
>supported
>    > by BCP79.=20
>
>??? My suggested text did not include "affiliate"? Maybe you're looking at
>someone else's text?
>
>	Noel
>



From stpeter@stpeter.im  Fri Jun 22 09:31:32 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3DE21F8781; Fri, 22 Jun 2012 09:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.473
X-Spam-Level: 
X-Spam-Status: No, score=-102.473 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 I42764q67GLq; Fri, 22 Jun 2012 09:31:32 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E2DC121F8743; Fri, 22 Jun 2012 09:31:31 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4CF8A40092; Fri, 22 Jun 2012 10:49:12 -0600 (MDT)
Message-ID: <4FE49DE2.1000207@stpeter.im>
Date: Fri, 22 Jun 2012 10:31:30 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Proposed Update to Note Well
References: <CC09E33B.88542%stewe@stewe.org>
In-Reply-To: <CC09E33B.88542%stewe@stewe.org>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org" <iesg@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 16:31:32 -0000

On 6/22/12 10:03 AM, Stephan Wenger wrote:
> Strike "actively".  It's a loophole and adds no value.

Sure.

> I don't know how a "contribution" can be "controlled" by
> a patent.  

Sure. I misread your earlier note.

> Using "related" as the broadest possible term that IMO
> may just be supported by BCP79:

BCP79 says "covered".

>    "If you believe  that a patent controlled by your employer
>    or sponsor is related to your contribution, then you must
>    disclose that patent."
> 
> I'm quite sure that the term "believe" is appropriate.  It's not
> the Note Well that allows trucks go through, it's BCP79.  However,
> ignoring my own advice (stick to terminology used in BCP79) I may
> settle for "aware of":
>    
>    "If you are aware of a patent controlled by your employer
>    or sponsor that is related to your contribution, then you must
>    disclose that patent."

Why is it limited to employers and sponsors? I might control it myself
directly, or just know that a patent covers it (BCP79, Section 6.1.1).

Keeping it as short as possible, I suggest:

   If you are aware that a contribution of yours is covered by
   patents, you need to disclose that fact.

OK, enough wordsmithing from me today...

/psa

From marshall.eubanks@gmail.com  Fri Jun 22 10:04:38 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59E8421F8746; Fri, 22 Jun 2012 10:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 yZ2RQdLsGevW; Fri, 22 Jun 2012 10:04:37 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5C221F8740; Fri, 22 Jun 2012 10:04:37 -0700 (PDT)
Received: by bkty8 with SMTP id y8so1958075bkt.31 for <multiple recipients>; Fri, 22 Jun 2012 10:04:36 -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:content-transfer-encoding; bh=e0GCDFf0W2okCL0wyhsY8400dnF7riDKMXIFsUdXWRg=; b=UuCz1iTWSTmFALRbcXfbAzMEjMJdeuafnpD+009f6lz59EGkUDFkFnHYmd+89ienMe 8dC6nSen+wyzHdt9suI0v7HVR5EyrL6MuBpon/q1pjC/2Dn2VOy4xwPKhl26MO/rL0yh uBBUUkPtxqjq9g2svcFpGpx7SQHLQIQ2OXKgwVWSFDgboDdzhtS2yrznz+mJINZ2giQi uYUY5ZEf5y3sf5hmhy3CO23IEgvh8dHwHVk0fTJDuW2j1YUq0BJ6/eTchZrEAISsJkRR fKs8B7DcDdk7S3+XjWxbMYFKLx3XpwfCGfXQj1K9NU6rcp74I/dyeK5MFEe5EckxcJA7 0vJg==
MIME-Version: 1.0
Received: by 10.152.46.232 with SMTP id y8mr2852221lam.18.1340384676337; Fri, 22 Jun 2012 10:04:36 -0700 (PDT)
Received: by 10.112.30.167 with HTTP; Fri, 22 Jun 2012 10:04:36 -0700 (PDT)
In-Reply-To: <4FE49DE2.1000207@stpeter.im>
References: <CC09E33B.88542%stewe@stewe.org> <4FE49DE2.1000207@stpeter.im>
Date: Fri, 22 Jun 2012 13:04:36 -0400
Message-ID: <CAJNg7VKp_aguk+mgBYoSNTFw97__Dk6dr_f+_WNU=vVy8coubA@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 17:04:38 -0000

On Fri, Jun 22, 2012 at 12:31 PM, Peter Saint-Andre <stpeter@stpeter.im> wr=
ote:
> On 6/22/12 10:03 AM, Stephan Wenger wrote:
>> Strike "actively". =A0It's a loophole and adds no value.
>
> Sure.
>
>> I don't know how a "contribution" can be "controlled" by
>> a patent.
>
> Sure. I misread your earlier note.
>
>> Using "related" as the broadest possible term that IMO
>> may just be supported by BCP79:
>
> BCP79 says "covered".
>
>> =A0 =A0"If you believe =A0that a patent controlled by your employer
>> =A0 =A0or sponsor is related to your contribution, then you must
>> =A0 =A0disclose that patent."
>>
>> I'm quite sure that the term "believe" is appropriate. =A0It's not
>> the Note Well that allows trucks go through, it's BCP79. =A0However,
>> ignoring my own advice (stick to terminology used in BCP79) I may
>> settle for "aware of":
>>
>> =A0 =A0"If you are aware of a patent controlled by your employer
>> =A0 =A0or sponsor that is related to your contribution, then you must
>> =A0 =A0disclose that patent."
>
> Why is it limited to employers and sponsors? I might control it myself
> directly, or just know that a patent covers it (BCP79, Section 6.1.1).
>
> Keeping it as short as possible, I suggest:
>
> =A0 If you are aware that a contribution of yours is covered by
> =A0 patents, you need to disclose that fact.

Shouldn't that be

s/patents/patents or patent applications/

?

Regards
Marshall

>
> OK, enough wordsmithing from me today...
>
> /psa

From stewe@stewe.org  Fri Jun 22 10:07:17 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64E1621F8773; Fri, 22 Jun 2012 10:07:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.849
X-Spam-Level: 
X-Spam-Status: No, score=-3.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, 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 i4-qhrfi73tt; Fri, 22 Jun 2012 10:07:15 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe002.messaging.microsoft.com [213.199.154.140]) by ietfa.amsl.com (Postfix) with ESMTP id 9869721F858F; Fri, 22 Jun 2012 10:07:10 -0700 (PDT)
Received: from mail98-db3-R.bigfish.com (10.3.81.242) by DB3EHSOBE005.bigfish.com (10.3.84.25) with Microsoft SMTP Server id 14.1.225.23; Fri, 22 Jun 2012 17:05:38 +0000
Received: from mail98-db3 (localhost [127.0.0.1])	by mail98-db3-R.bigfish.com (Postfix) with ESMTP id DA67E4803EA; Fri, 22 Jun 2012 17:05:37 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT002.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -1
X-BigFish: PS-1(zzbb2dI98dI9371I1432Izz1202h1082kzzz2fh2a8h668h839h944he5bhf0ah)
Received-SPF: pass (mail98-db3: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT002.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail98-db3 (localhost.localdomain [127.0.0.1]) by mail98-db3 (MessageSwitch) id 1340384735407997_26373; Fri, 22 Jun 2012 17:05:35 +0000 (UTC)
Received: from DB3EHSMHS012.bigfish.com (unknown [10.3.81.237])	by mail98-db3.bigfish.com (Postfix) with ESMTP id 5F87F600A8; Fri, 22 Jun 2012 17:05:35 +0000 (UTC)
Received: from BL2PRD0710HT002.namprd07.prod.outlook.com (157.56.240.133) by DB3EHSMHS012.bigfish.com (10.3.87.112) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 22 Jun 2012 17:05:35 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.88]) by BL2PRD0710HT002.namprd07.prod.outlook.com ([10.255.102.37]) with mapi id 14.16.0164.004; Fri, 22 Jun 2012 17:07:04 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Proposed Update to Note Well
Thread-Topic: Proposed Update to Note Well
Thread-Index: AQHNUI4UF8urOkUi9ECLOMdvpukpJJcGfKEA//+OCQCAAH0uAP//lI+A
Date: Fri, 22 Jun 2012 17:07:04 +0000
Message-ID: <CC09F337.8855E%stewe@stewe.org>
In-Reply-To: <4FE49DE2.1000207@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A509A18D276E43469F744F1E3B27C1C8@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "iesg@ietf.org" <iesg@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 17:07:17 -0000

Hi Peter,

On 6.22.2012 09:31 , "Peter Saint-Andre" <stpeter@stpeter.im> wrote:

>On 6/22/12 10:03 AM, Stephan Wenger wrote:
>>   =20
>>    "If you are aware of a patent controlled by your employer
>>    or sponsor that is related to your contribution, then you must
>>    disclose that patent."
>
>Why is it limited to employers and sponsors? I might control it myself
>directly, or just know that a patent covers it (BCP79, Section 6.1.1).

Section 6.1.1 requires the IPR being controlled by employer or sponsor.
The part you are referring to is gated by section 6.6, which is where
The employer or sponsor control is required.

That leaves us with

   If you are aware of a patent controlled by your employer
   or sponsor that is related to your contribution, then you must
   disclose that patent."


"Disclose that *patent*" instead of "disclose that *fact*", because we
Do not want to see disclosures suing "I'm aware of IPR covering my
Contribution".

My final word for today as well; see you all tomorrow on this fine list :-)

Stephan



From stpeter@stpeter.im  Fri Jun 22 10:07:38 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCD211E80AE; Fri, 22 Jun 2012 10:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.477
X-Spam-Level: 
X-Spam-Status: No, score=-102.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hgszMyuYOQpY; Fri, 22 Jun 2012 10:07:35 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 47D1311E8099; Fri, 22 Jun 2012 10:07:30 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 207E4400EE; Fri, 22 Jun 2012 11:25:06 -0600 (MDT)
Message-ID: <4FE4A64C.3060403@stpeter.im>
Date: Fri, 22 Jun 2012 11:07:24 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Subject: Re: Proposed Update to Note Well
References: <CC09E33B.88542%stewe@stewe.org> <4FE49DE2.1000207@stpeter.im> <CAJNg7VKp_aguk+mgBYoSNTFw97__Dk6dr_f+_WNU=vVy8coubA@mail.gmail.com>
In-Reply-To: <CAJNg7VKp_aguk+mgBYoSNTFw97__Dk6dr_f+_WNU=vVy8coubA@mail.gmail.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 17:07:38 -0000

On 6/22/12 11:04 AM, Marshall Eubanks wrote:
> On Fri, Jun 22, 2012 at 12:31 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:

>> Keeping it as short as possible, I suggest:
>>
>>   If you are aware that a contribution of yours is covered by
>>   patents, you need to disclose that fact.
> 
> Shouldn't that be
> 
> s/patents/patents or patent applications/

Yes.

From barryleiba@gmail.com  Fri Jun 22 10:15:43 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 124C321F8609; Fri, 22 Jun 2012 10:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.945
X-Spam-Level: 
X-Spam-Status: No, score=-102.945 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 YpIhyvbeAAXu; Fri, 22 Jun 2012 10:15:42 -0700 (PDT)
Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by ietfa.amsl.com (Postfix) with ESMTP id 6254521F851E; Fri, 22 Jun 2012 10:15:42 -0700 (PDT)
Received: by qcsg15 with SMTP id g15so1604015qcs.27 for <multiple recipients>; Fri, 22 Jun 2012 10:15:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=kPXqTc1w50RbXsGMvNCy/ds5mvOTAWjJQnjEw2iWDLI=; b=l5i/C5qH6HO2U9q8+fcw0nN7GWsodAYSc8EroEbF33QV5zLopBg8UkBM647XTFJZ2r EdssfNVc9qpo17WRQtbg0WEDTerGIxL9MeuzuUXWVuYWCq2JH7gQWVbIhzm1YMzbmQhG eOk2ep/3po6p5Dxjc+0b8Rp2yMnhwlOqvKiVRGxPVppvrJp1DDg5ne3axESE3NdEBZ16 y9/yA8RXJEX3DxB2fwmkjZbl1pBkqotoYPBzS6ngO7iiG8TrcoRS+lUB1VWCkVYdMZLa R74OPkGinuXIBH8VTJ4gndqQI6HhheoA/7ecoedp1tSbnvntrCffX5mswO2Pbxr9NsVI I1CA==
MIME-Version: 1.0
Received: by 10.229.136.10 with SMTP id p10mr1461852qct.131.1340385341853; Fri, 22 Jun 2012 10:15:41 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.229.245.85 with HTTP; Fri, 22 Jun 2012 10:15:41 -0700 (PDT)
In-Reply-To: <CC09F337.8855E%stewe@stewe.org>
References: <4FE49DE2.1000207@stpeter.im> <CC09F337.8855E%stewe@stewe.org>
Date: Fri, 22 Jun 2012 13:15:41 -0400
X-Google-Sender-Auth: epevXe5ICNmpA2wN_7O_U_Tly8A
Message-ID: <CALaySJKbjEwS-auY-j0Xg2HsY2qqhhuq027K2tEh4tBboa=nxQ@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
From: Barry Leiba <barryleiba@computer.org>
To: Stephan Wenger <stewe@stewe.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 17:15:43 -0000

>>> =A0 =A0"If you are aware of a patent controlled by your employer
>>> =A0 =A0or sponsor that is related to your contribution, then you must
>>> =A0 =A0disclose that patent."
>>
>>Why is it limited to employers and sponsors? I might control it myself
>>directly, or just know that a patent covers it (BCP79, Section 6.1.1).
>
> Section 6.1.1 requires the IPR being controlled by employer or sponsor.
> The part you are referring to is gated by section 6.6, which is where
> The employer or sponsor control is required.

No, I think PSA's point was that it should be "YOU or your employer or
sponsor."  It's possible that you, yourself, have unassigned patents.

Barry

From stpeter@stpeter.im  Fri Jun 22 10:16:22 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C59221F86BD; Fri, 22 Jun 2012 10:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.485
X-Spam-Level: 
X-Spam-Status: No, score=-102.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 S8ClhsGUoMI0; Fri, 22 Jun 2012 10:16:21 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id ADA8121F8611; Fri, 22 Jun 2012 10:16:21 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 53318400EE; Fri, 22 Jun 2012 11:34:02 -0600 (MDT)
Message-ID: <4FE4A864.6000207@stpeter.im>
Date: Fri, 22 Jun 2012 11:16:20 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Proposed Update to Note Well
References: <CC09F337.8855E%stewe@stewe.org>
In-Reply-To: <CC09F337.8855E%stewe@stewe.org>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org" <iesg@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 17:16:22 -0000

On 6/22/12 11:07 AM, Stephan Wenger wrote:
> Hi Peter,
> 
> On 6.22.2012 09:31 , "Peter Saint-Andre" <stpeter@stpeter.im> wrote:
> 
>> On 6/22/12 10:03 AM, Stephan Wenger wrote:
>>>    
>>>    "If you are aware of a patent controlled by your employer
>>>    or sponsor that is related to your contribution, then you must
>>>    disclose that patent."
>>
>> Why is it limited to employers and sponsors? I might control it myself
>> directly, or just know that a patent covers it (BCP79, Section 6.1.1).
> 
> Section 6.1.1 requires the IPR being controlled by employer or sponsor.

That's not how I read 6.1.1.

   Any Contributor who reasonably and personally knows of IPR meeting
   the conditions of Section 6.6 which the Contributor believes Covers
   or may ultimately Cover his or her Contribution....

Nothing there about employers or sponsors.

   ...or which the
   Contributor reasonably and personally knows his or her employer or
   sponsor may assert against Implementing Technologies based on such
   Contribution, ....

That's one branch in the decision tree, but not the only one.

   ...must make a disclosure in accordance with this Section
   6.

> The part you are referring to is gated by section 6.6, which is where
> The employer or sponsor control is required.

Not as I see it ("by the individual"):

   IPR disclosures under Sections 6.1.1. and 6.1.2 are required with
   respect to IPR that is owned directly or indirectly, by the
   individual or his/her employer or sponsor (if any) or that such
   persons otherwise have the right to license or assert.

> That leaves us with
> 
>    If you are aware of a patent controlled by your employer
>    or sponsor that is related to your contribution, then you must
>    disclose that patent."

It needs to say "you or..."

> "Disclose that *patent*" instead of "disclose that *fact*", because we
> Do not want to see disclosures suing "I'm aware of IPR covering my
> Contribution".

Right. :)

> My final word for today as well; see you all tomorrow on this fine list :-)

Mine too. I hope. :)

/psa


From fanf2@hermes.cam.ac.uk  Fri Jun 22 10:17:35 2012
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F5411E80CD for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 10:17:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.062
X-Spam-Level: 
X-Spam-Status: No, score=-6.062 tagged_above=-999 required=5 tests=[AWL=0.537,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 PbLiM3cQQv4j for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 10:17:34 -0700 (PDT)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5FEEC11E80C8 for <ietf@ietf.org>; Fri, 22 Jun 2012 10:17:34 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:43961) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1Si7UC-000216-Qc (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 22 Jun 2012 18:17:32 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1Si7UC-0005II-4I (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 22 Jun 2012 18:17:32 +0100
Date: Fri, 22 Jun 2012 18:17:32 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Randy Bush <randy@psg.com>
Subject: Re: Protocol Definition
In-Reply-To: <m2y5ng6p99.wl%randy@psg.com>
Message-ID: <alpine.LSU.2.00.1206221815380.18854@hermes-2.csi.cam.ac.uk>
References: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com> <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com> <m2y5ng6p99.wl%randy@psg.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 17:17:35 -0000

Randy Bush <randy@psg.com> wrote:

> > All protocols in IETF are based on the Internet or/and the IP.
>
> what a laugh.  try, for example, RFC 826

Perhaps a better example is RFC 6325.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Cromarty: Northeasterly backing westerly, 5 or 6. Moderate or rough.
Occasional rain. Moderate or poor.

From d3e3e3@gmail.com  Fri Jun 22 10:52:02 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78AFD21F856C for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 10:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.518
X-Spam-Level: 
X-Spam-Status: No, score=-103.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 REwz94nx4Kfv for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 10:52:01 -0700 (PDT)
Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com [209.85.213.53]) by ietfa.amsl.com (Postfix) with ESMTP id 27E8121F855F for <ietf@ietf.org>; Fri, 22 Jun 2012 10:52:01 -0700 (PDT)
Received: by yhp26 with SMTP id 26so2922524yhp.26 for <ietf@ietf.org>; Fri, 22 Jun 2012 10:51:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=HV3nuz/gvRodPWgbmz6S0mgGmyjmjxqRBtPWRS8Cc7U=; b=rwpZVrddZEqyTosmg/w8L/icmxMP9zp2bAPy+b3YOvQT6PRXeyWvnteE3FSs1FUiox lVH3N74YKhx+254wGak5d4vm3LKYd9AhJXJcsQyfgGt5IXZ4hcsXhEpmYgNO8rBJesrU 0cFOWzxvtFi9AcaBCSnmeDS3Uwwm35K0r5ntLG8Lqwi314P42E+yXy4u6e9rJKL8UflP KVTwWzmFpofbuUOc5BE0nLk6zqe/h0LK1jXh7lA5YITCm3g3eAM07+1XaVFuEIFSTT/M pI2OlI2oBx+kt7ubShdBDT4Ptqzu4RIafBkvrgWKNRWtErw29XlEgKn8JKqojh73wg0p sd+g==
Received: by 10.43.106.1 with SMTP id ds1mr775033icc.24.1340387519282; Fri, 22 Jun 2012 10:51:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.16.227 with HTTP; Fri, 22 Jun 2012 10:51:38 -0700 (PDT)
In-Reply-To: <alpine.LSU.2.00.1206221815380.18854@hermes-2.csi.cam.ac.uk>
References: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com> <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com> <m2y5ng6p99.wl%randy@psg.com> <alpine.LSU.2.00.1206221815380.18854@hermes-2.csi.cam.ac.uk>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 22 Jun 2012 13:51:38 -0400
Message-ID: <CAF4+nEE0UWq4UeYYsZ_khsZxD5P7APpd2CoV=4g0wV9N13evdQ@mail.gmail.com>
Subject: Re: Protocol Definition
To: Tony Finch <dot@dotat.at>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 17:52:02 -0000

How about RFC 1661.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

On Fri, Jun 22, 2012 at 1:17 PM, Tony Finch <dot@dotat.at> wrote:
> Randy Bush <randy@psg.com> wrote:
>
>> > All protocols in IETF are based on the Internet or/and the IP.
>>
>> what a laugh. =A0try, for example, RFC 826
>
> Perhaps a better example is RFC 6325.
>
> Tony.
> --
> f.anthony.n.finch =A0<dot@dotat.at> =A0http://dotat.at/
> Cromarty: Northeasterly backing westerly, 5 or 6. Moderate or rough.
> Occasional rain. Moderate or poor.

From bob.hinden@gmail.com  Fri Jun 22 11:13:52 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9169C21F871D; Fri, 22 Jun 2012 11:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.51
X-Spam-Level: 
X-Spam-Status: No, score=-103.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 tsKvcYUK6U1g; Fri, 22 Jun 2012 11:13:52 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id D451221F8717; Fri, 22 Jun 2012 11:13:51 -0700 (PDT)
Received: by qadz3 with SMTP id z3so517116qad.10 for <multiple recipients>; Fri, 22 Jun 2012 11:13:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=3hT6Si+R/u6/JGy08GvUhyYtoGLCXsyzi9u1QfjJDWU=; b=TcvY+zVd/YvIfGjFih2+F6+ol9w7SkE/p45oecwOqBPAWr/NWMsw7JJX2UshN5mo+I NxcsWHG2X60CZuvEazMKOrKy89ZPi1yuFtiHzKC55zjr0c4/WsrI6NDbnrzuOFY99r2a u22fz21A0vsxPj2AFxx+nqt7ux1MESsgmhwAUFgXfIDLl/ziBRNoHtivNDDT241xxbfy Q922PbSBujkH4s76gWijwKLQ0avq/Pq8AnPV8usu/clJ885DFdDoH3WLyPCH9FxH6WcG 2JgF6VnsO1n5a8lP+HUoLDHKmBrHDUlmdeUI/TG5pswvcxJDubhGkT4toSFSquMERq/e 01RA==
Received: by 10.224.116.203 with SMTP id n11mr7943797qaq.61.1340388831332; Fri, 22 Jun 2012 11:13:51 -0700 (PDT)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id gb7sm70820112qab.12.2012.06.22.11.13.49 (version=SSLv3 cipher=OTHER); Fri, 22 Jun 2012 11:13:50 -0700 (PDT)
Subject: Re: Proposed Update to Note Well
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <8B7419F5-0C5C-473A-8EC0-1B8A483171D8@ietf.org>
Date: Fri, 22 Jun 2012 11:13:47 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C248F169-CCB5-4B88-9950-02714CCC89AE@gmail.com>
References: <4FCF5B92.3070703@qualcomm.com> <4FCF5F99.3060807@cisco.com> <4FCF6BD5.7080503@qualcomm.com> <4FCF8471.2050701@cisco.com> <AEF1278E-68D1-47D3-932A-8B4940E864A0@harvard.edu> <4FD0679D.60304@cisco.com> <4FD068BC.5050405@cs.tcd.ie> <CAP0PwYZb87zRv0HpTES1twLnnTWUk9ft80bupUoB5f62P3eL=A@mail.gmail.com> <4FD0A53A.6010406@innovationslab.net> <4FD0AAA5.3060400@cisco.com> <C07B527F-37D1-4340-BF7D-F1B6BD263726@gmail.com> <4FD0B3A1.7090001@qualcomm.com> <4FD0B3FA.90704@qualcomm.com> <CAP0PwYYjbaHqkk7z5dXBB4kcH=NhT5_MofHFpwpgXnXvBG_tKQ@mail.gmail.com> <4FD0B86E.8020008@qualcomm.com> <CALaySJKSzsgpmxaiTsHMAEBJNTyPGScMnsfTM=rbMiMEUREb6w@mail.gmail.com> <BD3F594E-0ED1-4079-836F-5D7F5D63AD91@harvard.edu> <CAP0PwYam-arXn1vYebn16d7b_paD7P9ZwKhG1aYgCo2yxuUWaQ@mail.gmail.com> <4FD0F8C5.8000100@qualcomm.com> <4FD10927.8020906@qualcomm.com> <CALaySJ+cMTbcsQQXTa4xhxS+0jBHah4XBXuHEeo4+i2iv1cRVg@mail.gmail.com> <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com> <8B7419F5-0C5C-473A-8EC0-1B 8A483171D8@ietf.org>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 18:13:52 -0000

Russ,

I like that it is shorter, but I think it might be a little too short.  =
That is, I think it needs to be clearer what is a contribution and then =
mention patents.  For example:

  If you write, say, or discuss anything in the IETF, formally or =
informally,
  that is considered "a contribution" to the IETF.  If you believe this =
is covered by a patent
  or patent application you or your employer own, one of you must =
disclose
  that.

Thanks,
Bob


On Jun 21, 2012, at 3:10 PM, IETF Chair wrote:

> The IESG has heard many complaints that the Note Well is too complex.  =
After some discussion with counsel, we propose the following updated =
Note Well for your comment and review.  The below summary would be =
followed with a pointer to or text of more details, which will depend =
upon whether it's a meeting slide, on the web site, on the registration =
page, or on a mailing-list greeting.
>=20
> On behalf of the IESG,
>  Russ Housley
>  IETF Chair
>=20
> --------------------------------------
>=20
> NOTE WELL
>=20
> In summary:
>=20
>   By participating with the IETF, you agree to follow IETF processes.
>=20
>   If you write, say, or discuss anything in the IETF, formally or =
informally,
>   (all of which we call "a contribution") that you know is covered by =
a patent
>   or patent application you or your employer own, one of you must =
disclose
>   that.
>=20
>   You understand that meetings might be recorded and broadcast.
>=20
> This would be followed with a pointer to or text of more details,
> which will depend upon whether it's a meeting slide, on the web site,
> on the registration page, or on a mailing-list greeting.
>=20


From acooper@cdt.org  Fri Jun 22 12:59:40 2012
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 429C521F8602; Fri, 22 Jun 2012 12:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 rDsD+5+0OpS7; Fri, 22 Jun 2012 12:59:39 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 0180821F8601; Fri, 22 Jun 2012 12:59:38 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Fri, 22 Jun 2012 15:59:36 -0400
Subject: Re: Last Call: <draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt> (Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI)) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <ADE21D06-F6A4-4018-A999-6B50EC94F3C7@fugue.com>
Date: Fri, 22 Jun 2012 15:59:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AE0A5BB-E5B7-46A3-A3D6-3F7C8FB84016@cdt.org>
References: <20120531184851.30358.8816.idtracker@ietfa.amsl.com> <ADE21D06-F6A4-4018-A999-6B50EC94F3C7@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Cc: GEOPRIV WG <geopriv@ietf.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 19:59:40 -0000

Hi Ted,

Some responses inline.

On May 31, 2012, at 4:43 PM, Ted Lemon wrote:

> There are still a few problems with this draft.   The first is that it =
uses a nonstandard and somewhat odd encoding to deliver the URI and =
Lifetime values.   These should simply be delivered as separate options, =
leaving out the whole Luritype complication.    The argument might be =
raised that the Luritype field provides some sort of future-proofing, =
but this future-proofing can as easily be attained with another DHCP =
option code, so it's unnecessary.

My understanding is that the option is encoded this way both for =
extensibility and because the Valid-For parameter is solely a property =
of the URI. Surely this is not the only instance of a DHCP option with a =
sub-option?=20

It may have been before I was paying attention, but I get the impression =
that related ground has already been trod in DHC, given that it also =
came up in GEOPRIV. =
http://www.ietf.org/mail-archive/web/geopriv/current/msg08451.html

>=20
> Secondly, this text ought to be expanded:
>=20
>> The choice of the Valid-For value is a policy decision for the=20
>> operator of the DHCP server.  Like location URIs themselves, it can=20=

>> be statically configured on the DHCP server or provisioned=20
>> dynamically (via an out-of-band exchange with a Location Information
>> Server) as requests for location URIs are received.
>=20
> To:
>=20
>> The choice of the Valid-For value is a policy decision for the=20
>> operator of the DHCP server.  Like location URIs themselves, it can=20=

>> be statically configured on the DHCP server or provisioned=20
>> dynamically (via an out-of-band exchange with a Location Information
>> Server) as requests for location URIs are received.   DHCP server
>> operators are advised not to configure a valid-for lifetime that is
>> greater than half the minimum configured lifetime for DHCP leases,
>> since this could result in stale configuration information on the
>> DHCP client and potential loss of service.
>=20

I'm not sure the additional text is necessary given that there is an =
entire paragraph explaining considerations for servers in setting the =
Valid-For value. Furthermore, I don't see how "potential loss of =
service" is possible. We're talking about a URI with an expiration. When =
it expires, location recipients will no longer have access to the =
client's location, but it otherwise doesn't affect recipients' ability =
to use any "service" whatsoever.

>=20
> Thirdly, this text is simply wrong, and indeed specifically =
contradicted by RFC3396:
>=20
>>   Per [RFC2131], subsequent LocationURI Options, which are=20
>>   non-concatenated, overwrite the previous value.
>=20
> I don't think this is a huge problem, but I think the text should say =
this:
>=20
>> It is not meaningful to configure multiple LocationURI options.   =
DHCPv4 servers and clients conforming to RFC3396 will not permit this; =
DHCPv6 servers and clients can be configured this way, but the behavior =
when so configured is undefined.   Therefore, DHCPv6 server operators =
are cautioned not to configure more than one such option.

Works for me.

>=20
> Section 3.2 suggests that options shouldn't contain certain =
potentially harmful values, but this is a toothless restriction, since =
an attacker can simply ignore it.   In order for it to be effective, =
Section 3.2 should insist that DHCP clients reject forbidden URI =
formats.   Of course, this too is somewhat toothless, since any list of =
forbidden URI formats will necessarily fail to mention any future =
potentially harmful URIs that could arise.   It would be better to list =
which URIs _are_ permitted, and require the client to reject any URI =
that is not permitted.   The document is already set up to do this, but =
doesn't _actually_ do it, so fixing this should be quite easy.

In 3.3, I suggest replacing the following:

"This section specifies which URI types are acceptable as a location
   URI scheme (or type) for this DHCP Option:"

with

"URIs carried by this DHCP Option MUST have one of the following URI =
schemes:"

Thanks,
Alissa

>=20
> Sorry for not catching all of this sooner=97the previous review of the =
document was rudely interrupted by the Paris IETF meeting... :)
>=20
> Aside from these objections, which I think are easy to address, I have =
no problem with the document proceeding.



From uyeshiro@ifa.hawaii.edu  Fri Jun 22 13:37:35 2012
Return-Path: <uyeshiro@ifa.hawaii.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B48DE11E8087; Fri, 22 Jun 2012 13:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 MCVv9J6t8Fc7; Fri, 22 Jun 2012 13:37:34 -0700 (PDT)
Received: from hale.ifa.hawaii.edu (hale.ifa.hawaii.edu [128.171.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 670EE11E807F; Fri, 22 Jun 2012 13:37:32 -0700 (PDT)
Received: from XeonAL (xeonal [128.171.163.193]) by hale.ifa.hawaii.edu (8.13.8/8.13.8) with ESMTP id q5MKbRX6019643; Fri, 22 Jun 2012 10:37:27 -1000 (HST)
From: "Robin Uyeshiro" <uyeshiro@IfA.Hawaii.Edu>
To: "'Bob Hinden'" <bob.hinden@gmail.com>, "'IETF'" <ietf@ietf.org>
Subject: RE: Proposed Update to Note Well
Date: Fri, 22 Jun 2012 10:37:52 -1000
Message-ID: <BA22D211CA854D1B92CC0303D873B8B1@XeonAL>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6863
In-Reply-To: <C248F169-CCB5-4B88-9950-02714CCC89AE@gmail.com>
Thread-Index: Ac1Qou8aRojES9IySoizqTEjI4ZMjQAEj5wg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Importance: Normal
Cc: 'IETF Announce' <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 20:37:35 -0000

I'd like to comment a bit on patent ownership/control/etc.  Patents are
"assigned" by the (US) patent office, usually, these days, to the =
company
for whom the inventor works.  "Ownership" is not a term used.  "Control" =
can
be problematic, if the inventor changes employment.  If you invent =
something
for which a patent is issued and assigned to your company, then you =
change
employment, then neither you nor the company you currently work for
"control" that patent.  But you should probably still disclose the =
patent.

I'd vote for

>>   If you are aware that a contribution of yours is covered by
>>   patents, you need to disclose that fact.

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Bob
Hinden
Sent: Friday, June 22, 2012 8:14 AM
To: IETF
Cc: Bob Hinden; IETF Announce
Subject: Re: Proposed Update to Note Well


Russ,

I like that it is shorter, but I think it might be a little too short.  =
That
is, I think it needs to be clearer what is a contribution and then =
mention
patents.  For example:

  If you write, say, or discuss anything in the IETF, formally or
informally,
  that is considered "a contribution" to the IETF.  If you believe this =
is
covered by a patent
  or patent application you or your employer own, one of you must =
disclose
  that.

Thanks,
Bob


On Jun 21, 2012, at 3:10 PM, IETF Chair wrote:

> The IESG has heard many complaints that the Note Well is too complex.
After some discussion with counsel, we propose the following updated =
Note
Well for your comment and review.  The below summary would be followed =
with
a pointer to or text of more details, which will depend upon whether =
it's a
meeting slide, on the web site, on the registration page, or on a
mailing-list greeting.
>=20
> On behalf of the IESG,
>  Russ Housley
>  IETF Chair
>=20
> --------------------------------------
>=20
> NOTE WELL
>=20
> In summary:
>=20
>   By participating with the IETF, you agree to follow IETF processes.
>=20
>   If you write, say, or discuss anything in the IETF, formally or
informally,
>   (all of which we call "a contribution") that you know is covered by =
a
patent
>   or patent application you or your employer own, one of you must =
disclose
>   that.
>=20
>   You understand that meetings might be recorded and broadcast.
>=20
> This would be followed with a pointer to or text of more details,
> which will depend upon whether it's a meeting slide, on the web site,
> on the registration page, or on a mailing-list greeting.
>=20


From cntreras@gmail.com  Fri Jun 22 13:43:16 2012
Return-Path: <cntreras@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4BF21F862A; Fri, 22 Jun 2012 13:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 JRwayTwIXH0V; Fri, 22 Jun 2012 13:43:15 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id A287921F8621; Fri, 22 Jun 2012 13:43:15 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so2831504obb.31 for <multiple recipients>; Fri, 22 Jun 2012 13:43:15 -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=JlvfI9jFLJUvMu7O4gMltXwNQssdumHJ/KjHnKUNJbc=; b=oF1Vhw9cn5Xj+Zs1yBknxYd94lSRnlRcejjUlEPW/wtGD7aDEaGgagYELVMZgyEzs5 zyOdrqKXdDD5H8cm4ScslM8Fylim2eAcdcF+TiLEiDPCBJYT9X74ZcAENZjbtA7r1CxR noadVSUirkjFq7S1DIcBkUbFsPJDHeQbLXo8ezh6Lj6aATRj938hNlkFGRixGaSAvV+G BubX3bKHJ4/5LnbfUdhHa03B7eKGL4DIJ2EAEpXjOzb6O9Axq4lIVg3VXTPiCSJwBD5W lE8jYPJJu27YeouxWNrE8O+puIWP0FNOwn+q8Ihjt2aC3+4ck411cuq3FYy4XmC8gvJe GRNw==
MIME-Version: 1.0
Received: by 10.60.4.165 with SMTP id l5mr3385058oel.41.1340397795283; Fri, 22 Jun 2012 13:43:15 -0700 (PDT)
Received: by 10.182.44.197 with HTTP; Fri, 22 Jun 2012 13:43:15 -0700 (PDT)
In-Reply-To: <BA22D211CA854D1B92CC0303D873B8B1@XeonAL>
References: <C248F169-CCB5-4B88-9950-02714CCC89AE@gmail.com> <BA22D211CA854D1B92CC0303D873B8B1@XeonAL>
Date: Fri, 22 Jun 2012 16:43:15 -0400
Message-ID: <CAP0PwYYfBtgGifZVi287JmAWxMm2Rr3jAUg8-BKOKMjskRo47w@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
From: Jorge Contreras <cntreras@gmail.com>
To: Robin Uyeshiro <uyeshiro@ifa.hawaii.edu>
Content-Type: multipart/alternative; boundary=e89a8ff1c2e872143004c315ae41
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>, IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 20:43:16 -0000

--e89a8ff1c2e872143004c315ae41
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jun 22, 2012 at 4:37 PM, Robin Uyeshiro <uyeshiro@ifa.hawaii.edu>wrote:

> I'd like to comment a bit on patent ownership/control/etc.  Patents are
> "assigned" by the (US) patent office, usually, these days, to the company
> for whom the inventor works.


No, the patent is assigned by the inventor to the company.  The PTO just
records the assignment.


>  "Ownership" is not a term used.  "Control" can
> be problematic, if the inventor changes employment.  If you invent
> something
> for which a patent is issued and assigned to your company, then you change
> employment, then neither you nor the company you currently work for
> "control" that patent.


This is just not correct.  If the patent is assigned to the company, and
the inventor leaves the company, the company still owns and controls the
patent.



> But you should probably still disclose the patent.
>

Yes.

--e89a8ff1c2e872143004c315ae41
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Fri, Jun 22, 2012 at 4:37 PM, Robin U=
yeshiro <span dir=3D"ltr">&lt;<a href=3D"mailto:uyeshiro@ifa.hawaii.edu" ta=
rget=3D"_blank">uyeshiro@ifa.hawaii.edu</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
I&#39;d like to comment a bit on patent ownership/control/etc. =A0Patents a=
re<br>
&quot;assigned&quot; by the (US) patent office, usually, these days, to the=
 company<br>
for whom the inventor works. </blockquote><div><br>No, the patent is assign=
ed by the inventor to the company.=A0 The PTO just records the assignment.<=
br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
=A0&quot;Ownership&quot; is not a term used. =A0&quot;Control&quot; can<br>
be problematic, if the inventor changes employment. =A0If you invent someth=
ing<br>
for which a patent is issued and assigned to your company, then you change<=
br>
employment, then neither you nor the company you currently work for<br>
&quot;control&quot; that patent. =A0</blockquote><div><br>This is just not =
correct.=A0 If the patent is assigned to the company, and the inventor leav=
es the company, the company still owns and controls the patent.<br><br>=A0<=
/div>
<blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">But you should probably s=
till disclose the patent.<br></blockquote><div class=3D"h5"><br>Yes. <br>
</div></div><br>

--e89a8ff1c2e872143004c315ae41--

From uyeshiro@ifa.hawaii.edu  Fri Jun 22 13:49:11 2012
Return-Path: <uyeshiro@ifa.hawaii.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2195D21F8621 for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 13:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 mpM-vlMRt+4M for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 13:49:10 -0700 (PDT)
Received: from hale.ifa.hawaii.edu (hale.ifa.hawaii.edu [128.171.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8343021F85D3 for <ietf@ietf.org>; Fri, 22 Jun 2012 13:49:10 -0700 (PDT)
Received: from XeonAL (xeonal [128.171.163.193]) by hale.ifa.hawaii.edu (8.13.8/8.13.8) with ESMTP id q5MKn8Wt020171; Fri, 22 Jun 2012 10:49:08 -1000 (HST)
From: "Robin Uyeshiro" <uyeshiro@IfA.Hawaii.Edu>
To: "'Jorge Contreras'" <cntreras@gmail.com>
Subject: RE: Proposed Update to Note Well
Date: Fri, 22 Jun 2012 10:49:42 -1000
Message-ID: <1CC7E58691B04ECDB9D4CE5340072A03@XeonAL>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0043_01CD5064.BDF4C860"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6863
In-Reply-To: <CAP0PwYYfBtgGifZVi287JmAWxMm2Rr3jAUg8-BKOKMjskRo47w@mail.gmail.com>
Thread-Index: Ac1Qt6iCp3SSXciYQHGQIqJ3X5KQuAAAIVIg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Importance: Normal
Cc: 'Bob Hinden' <bob.hinden@gmail.com>, 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 20:49:11 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0043_01CD5064.BDF4C860
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

 "Ownership" is not a term used.  "Control" can
be problematic, if the inventor changes employment.  If you invent =
something
for which a patent is issued and assigned to your company, then you =
change
employment, then neither you nor the company you currently work for
"control" that patent. =20


This is just not correct.  If the patent is assigned to the company, and =
the
inventor leaves the company, the company still owns and controls the =
patent.

 [RU]  Your new (current) company does not "own" the patent and neither =
do
you, if you have signed away your rights, which you are required to do =
for
most companies in the US.  But you should still disclose the patent.=20


------=_NextPart_000_0043_01CD5064.BDF4C860
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19258"></HEAD>
<BODY>
<DIV>&nbsp;"Ownership" is not a term used. &nbsp;"Control" can<BR>be=20
problematic, if the inventor changes employment. &nbsp;If you invent=20
something<BR>for which a patent is issued and assigned to your company, =
then you=20
change<BR>employment, then neither you nor the company you currently =
work=20
for<BR>"control" that patent. &nbsp;</DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3Dgmail_quote>
  <DIV><BR>This is just not correct.&nbsp; If the patent is assigned to =
the=20
  company, and the inventor leaves the company, the company still owns =
and=20
  controls the patent.<BR><BR>&nbsp;<SPAN =
class=3D640034720-22062012><FONT=20
  color=3D#0000ff size=3D2 face=3DArial>[RU]&nbsp;&nbsp;Your new =
(current) company=20
  does not "own" the patent and neither do you, if you have signed away =
your=20
  rights, which you are required to do for most companies in the =
US.&nbsp; But=20
  you should still disclose the=20
patent.&nbsp;</FONT></SPAN></DIV></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0043_01CD5064.BDF4C860--


From cntreras@gmail.com  Fri Jun 22 13:52:52 2012
Return-Path: <cntreras@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3353821F852E for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 13:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 QcYWadNZkKH6 for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 13:52:51 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9CDA621F852D for <ietf@ietf.org>; Fri, 22 Jun 2012 13:52:51 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so2841316obb.31 for <ietf@ietf.org>; Fri, 22 Jun 2012 13:52:51 -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=fnPwxXG9aMK7IXYdwAdoGmUj7HhQRKeSPNHeuu30GwA=; b=AZ8VpDIU5SiqKwc4bjsZpk24qxm+9mD2+BF5NYlLiBW4SclvUB6COHt6kUSgz7WMEB UMPng2YCa1I2HebSjZGmNolQuJ6P7mb+q31rnEckM14oD4TUSzPMKZENBaMmwyy1g5Ic uLWN46nERX7RmeGyiapoM5dX08aWZH+eoBQ7t2pAIrdIGXrj+FFKHnIa6UrgKG+Cxxy1 jAPzvZtUIVacJY1mxccFwQ0g5/q3huYm1/o8YR/1o0OvWs1GwAxnAAsbwFyLoLZCVcui u2GLVuSYd080f5ZKu7JSt0XWLNRb4KSI1XX52IJk5Do8o1harNopteZLtEfFgRBcUb6y uukw==
MIME-Version: 1.0
Received: by 10.60.172.143 with SMTP id bc15mr3399197oec.73.1340398371224; Fri, 22 Jun 2012 13:52:51 -0700 (PDT)
Received: by 10.182.44.197 with HTTP; Fri, 22 Jun 2012 13:52:51 -0700 (PDT)
In-Reply-To: <1CC7E58691B04ECDB9D4CE5340072A03@XeonAL>
References: <CAP0PwYYfBtgGifZVi287JmAWxMm2Rr3jAUg8-BKOKMjskRo47w@mail.gmail.com> <1CC7E58691B04ECDB9D4CE5340072A03@XeonAL>
Date: Fri, 22 Jun 2012 16:52:51 -0400
Message-ID: <CAP0PwYa+7F2Y5xotdFTZ4LRGtKWku_DPfdhZWE_RP6REDQEu=A@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
From: Jorge Contreras <cntreras@gmail.com>
To: Robin Uyeshiro <uyeshiro@ifa.hawaii.edu>
Content-Type: multipart/alternative; boundary=bcaec54c527cc63cbe04c315d095
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 20:52:52 -0000

--bcaec54c527cc63cbe04c315d095
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jun 22, 2012 at 4:49 PM, Robin Uyeshiro <uyeshiro@ifa.hawaii.edu>wrote:

> **
>  "Ownership" is not a term used.  "Control" can
> be problematic, if the inventor changes employment.  If you invent
> something
> for which a patent is issued and assigned to your company, then you change
> employment, then neither you nor the company you currently work for
> "control" that patent.
>
>
> This is just not correct.  If the patent is assigned to the company, and
> the inventor leaves the company, the company still owns and controls the
> patent.
>
>  [RU]  Your new (current) company does not "own" the patent and neither
> do you, if you have signed away your rights, which you are required to do
> for most companies in the US.  But you should still disclose the patent.
>
> Ah, I see your point now.  You are right about ownership, but this would
become a "third party disclosure".  It's not required, but is recommended
under BCP 79.  It's the same as if you knew about a patent held by another,
unrelated company.  Once you leave the first employer, you don't know what
the fate of the patent is (e.g., it could be sold, abandoned, etc.) so you
aren't required to disclose it (just encouraged to).

--bcaec54c527cc63cbe04c315d095
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Fri, Jun 22, 2012 at 4:49 PM, Robin U=
yeshiro <span dir=3D"ltr">&lt;<a href=3D"mailto:uyeshiro@ifa.hawaii.edu" ta=
rget=3D"_blank">uyeshiro@ifa.hawaii.edu</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
<u></u>





<div><div class=3D"im">
<div>=A0&quot;Ownership&quot; is not a term used. =A0&quot;Control&quot; ca=
n<br>be=20
problematic, if the inventor changes employment. =A0If you invent=20
something<br>for which a patent is issued and assigned to your company, the=
n you=20
change<br>employment, then neither you nor the company you currently work=
=20
for<br>&quot;control&quot; that patent. =A0</div>
</div><blockquote style=3D"MARGIN-RIGHT:0px">
  <div class=3D"gmail_quote">
  <div><div class=3D"im"><br>This is just not correct.=A0 If the patent is =
assigned to the=20
  company, and the inventor leaves the company, the company still owns and=
=20
  controls the patent.<br><br></div>=A0<span><font color=3D"#0000ff" face=
=3D"Arial">[RU]=A0=A0Your new (current) company=20
  does not &quot;own&quot; the patent and neither do you, if you have signe=
d away your=20
  rights, which you are required to do for most companies in the US.=A0 But=
=20
  you should still disclose the=20
patent.=A0</font></span></div></div></blockquote></div></blockquote><div>Ah=
, I see your point now.=A0 You are right about ownership, but this would be=
come a &quot;third party disclosure&quot;.=A0 It&#39;s not required, but is=
 recommended under BCP 79.=A0 It&#39;s the same as if you knew about a pate=
nt held by another, unrelated company.=A0 Once you leave the first employer=
, you don&#39;t know what the fate of the patent is (e.g., it could be sold=
, abandoned, etc.) so you aren&#39;t required to disclose it (just encourag=
ed to).<br>
=A0</div></div><br>

--bcaec54c527cc63cbe04c315d095--

From john-ietf@jck.com  Fri Jun 22 14:12:03 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E5B11E80D0 for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 14:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 RdbrsfdZ02-N for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 14:12:02 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E4ED411E80DC for <ietf@ietf.org>; Fri, 22 Jun 2012 14:12:01 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SiB2a-000Hpb-9B; Fri, 22 Jun 2012 17:05:16 -0400
Date: Fri, 22 Jun 2012 17:11:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jorge Contreras <cntreras@gmail.com>, Robin Uyeshiro <uyeshiro@ifa.hawaii.edu>
Subject: Re: Proposed Update to Note Well
Message-ID: <50404A860941E07881DF8EEA@JcK-HP8200.jck.com>
In-Reply-To: <CAP0PwYa+7F2Y5xotdFTZ4LRGtKWku_DPfdhZWE_RP6REDQEu=A@mail.gmail.com>
References: <CAP0PwYYfBtgGifZVi287JmAWxMm2Rr3jAUg8-BKOKMjskRo47w@mail.gmail.com> <1CC7E58691B04ECDB9D4CE5340072A03@XeonAL> <CAP0PwYa+7F2Y5xotdFTZ4LRGtKWku_DPfdhZWE_RP6REDQEu=A@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 21:12:03 -0000

--On Friday, June 22, 2012 16:52 -0400 Jorge Contreras
<cntreras@gmail.com> wrote:

>>  [RU]  Your new (current) company does not "own" the patent
>>  and neither do you, if you have signed away your rights,
>> which you are required to do for most companies in the US.
>> But you should still disclose the patent.
>> 
>> Ah, I see your point now.  You are right about ownership, but
>> this would
> become a "third party disclosure".  It's not required, but is
> recommended under BCP 79.  It's the same as if you knew about
> a patent held by another, unrelated company.  Once you leave
> the first employer, you don't know what the fate of the patent
> is (e.g., it could be sold, abandoned, etc.) so you aren't
> required to disclose it (just encouraged to).

Jorge, while I understand your reasoning, it seems to me that
you are creating a loophole here that we don't want (and that
isn't justified by the BCP).   Consider the following scenario: 

While working for company X, I invent something and a patent
application is filed with my name as the inventor.  According to
company policy, I assign all rights to the patent (if awarded)
to the company.   I then leave company X and join company Y.
Just to make this a little easier by avoiding some of the
complex issues associated with disclosing patent applications),
assume that there are no survivable NDAs with company X that
prevent my disclosing the patent application to company Y or to
the IETF.  As another simplification, assume that I became
active in the IETF only when I joined company Y (that avoids any
question about my obligation or lack thereof to disclose while I
was still working for company X).

Now, I find myself in a WG that is considering a technology that
I reasonable believe interacts with the patent application in
question.  There is no basis on which I can claim that I didn't
know about that application... after all, I signed it.   So I
think I'm _obligated_ to disclose.  Whether that disclosure is
1st party (I'm the inventor) or third party (the thing belongs
to company X) seems like uninteresting hair-splitting.  And my
disclosure might say "I know about this application but you need
to check with the patent owner, which was Company X when last I
had first-hand knowledge, as to what its current status is".
But asserting that such a disclosure is not required puts the
notion of what I might reasonably be expected know into a rather
different light, one that, IMO, might be very damaging to the
process.

And, no, I don't think the Note Well needs to go nearly into
that level of detail.  For it, it seems to me that it is
sufficient to say that one is obligated to disclose if one has
first-hand, direct, knowledge of the patent (or application) and
that disclosure under other circumstances is encouraged and
might, in some cases, be required.

     john


From stephen.farrell@cs.tcd.ie  Fri Jun 22 14:20:37 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E03811E80C9 for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 14:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.266
X-Spam-Level: 
X-Spam-Status: No, score=-102.266 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 SvoWN4sJj9Pa for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 14:20:36 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 0A2A911E80BC for <ietf@ietf.org>; Fri, 22 Jun 2012 14:20:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 7207D1715B4 for <ietf@ietf.org>; Fri, 22 Jun 2012 22:20:33 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1340400032; bh=1ml2GZGJQBaZO1 5HVqcd9mH8wOrP1aeQ485GRWOckOU=; b=nyMg3wYjSOBOU58bCRa8eI6UOcmZTL BBM8WypRjmVdypHpdi4qKgNM+FxXZvZ67XwW57gtgIat5hqYt/7/C2IGkE5KrVbp a7ImzA9IYB0Tj7/UBUD6oEDYRjtmjcmTMeeHE0xRVRrWq1LHoYMhb4in6wojMPmL EKBZbEQqRSeK+30237LI392wkG2YJf3c6VWT7wpMO3Q0Cf12DZYBv0tHgzr489rn wFwtJQmtaEgwweWlk30f0f4qOOflhr1/Fa0qxUT0STnvTrHKxeVb9AlthBlS3IV3 MhKIRgrZSpZ06Hq1cp+UnRnD+9Te/3KpVmJFlMweLNPDRFonKtOqEY+w==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id aEgiPeqWX6pw for <ietf@ietf.org>; Fri, 22 Jun 2012 22:20:32 +0100 (IST)
Received: from [10.87.48.10] (unknown [86.46.25.252]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 153E0171477 for <ietf@ietf.org>; Fri, 22 Jun 2012 22:20:32 +0100 (IST)
Message-ID: <4FE4E19F.2050400@cs.tcd.ie>
Date: Fri, 22 Jun 2012 22:20:31 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com>
In-Reply-To: <20120604141804.23098.42455.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 21:20:37 -0000

Hi All,

I went back through the IETF LC comments and think that we've
resolved them all on the list and have the changes in this
version [1] of the draft, with the possible exception of those
below.

The issues raised but not so far obviously resolved on the
list were I think:

1) inclusion of content type
2) nih as a URI scheme or not

For (1) this version includes ct= in draft-farrell-decade-ni
(the only changes to draft-hallambaker-decade-ni-params [2]
made so far are those that flow from moving that text), so
I'd hope that this version resolves that but would welcome
feedback on the new text from folks who commented. I'd hope
it should be ok, modulo some text tweaks.

For (2) we've left nih in as a URI scheme in this version.
We're still in favour of keeping it that way and have added
some language about why its there and is done like that. I'm
guessing that Martin at least won't be happy (but who knows;-),
so again comments are welcome as to whether the new text helps
or not. But in the end we'll go with Barry's consensus call
on this if he judges that we're in the rough, rather than the
folks who've commented on this topic. In that case I'll put
out a version with no nih scheme and the "human speakable"
format as just a textual convention (with a check-digit,
which'd be plain odd IMO, the uri scheme is the right idea
really:-)

Please let me know if I've missed addressing anything else
or if you have any other comments.

Cheers,
S.

[1] http://tools.ietf.org/html/draft-farrell-decade-ni
[2] http://tools.ietf.org/html/draft-hallambaker-decade-ni-params

(Note: only [1] is in IETF LC...just in case someone's
confused about that:-)

On 06/04/2012 03:18 PM, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Naming Things with Hashes'
>   <draft-farrell-decade-ni-07.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-07-02. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document defines a set of ways to identify a thing using the
>    output from a hash function, specifying URI, URL, binary and human
>    "speakable" formats for these names.  The various formats are
>    designed to support, but not require, a strong link to the referenced
>    object such that the referenced object may be authenticated to the
>    same degree as the reference to it.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-farrell-decade-ni/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-farrell-decade-ni/ballot/
> 
> 
> The following IPR Declarations may be related to this I-D:
> 
>    http://datatracker.ietf.org/ipr/1773/
>    http://datatracker.ietf.org/ipr/1775/
> 
> 
> 
> 
> 


From abdussalambaryun@gmail.com  Fri Jun 22 14:23:05 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FFF521F850C for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 14:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 ilN3tFi5gcOR for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 14:23:04 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 53C0521F850B for <ietf@ietf.org>; Fri, 22 Jun 2012 14:23:02 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1236929vbb.31 for <ietf@ietf.org>; Fri, 22 Jun 2012 14:23:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=pctuyfiAkmC/VUg2VeAsSn0J5pRhi5N4y1fm651z9NQ=; b=HIQDamBe9timEmXDOhRtKXsQPYvKbLb7FJaY/WMLxFC+HJiPXfwEgmn6vSNPvflE+e NilguGt7hybLijc2iwLexBRyF7Kqb96YkF2vcbFRYUZM6X3nfq/y+/6tvfFKTaKj8DjP hgERinFszZAn2x4J8/ITNIYFRyOFypV7GXLtI5CPIlaEcWRj1tO8e0P2A7dcXc0fjk6b vUy5VFvvE5Mx5dk99N3A1GFvbFWJ0nL+vkBAXZhUYsvW1vQBJvzG8+iTd9Tf/xvaLiGB zo/6JvIJiY0R0OAhq8jmrXD09/KiFUQabqX3K3Oq6zho94yC42EciTrUeijtr2WGd46z S9BA==
MIME-Version: 1.0
Received: by 10.52.90.144 with SMTP id bw16mr1466503vdb.129.1340400181709; Fri, 22 Jun 2012 14:23:01 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Fri, 22 Jun 2012 14:23:01 -0700 (PDT)
Date: Fri, 22 Jun 2012 23:23:01 +0200
Message-ID: <CADnDZ88UU6Oh8=uy_aaFSDkFtMR5tAiyti=OO1_c0EbNh6va-Q@mail.gmail.com>
Subject: How IETF Protocols are Definition?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 21:23:05 -0000

Hi All,
+++++++++++++++++++++++++++++++++++++++++++++++++
Previos subject: Protocol Definition
Change the subject so we can focus on the reality of IETF purpose>
+++++++++++++++++++++++++++++++++++++++++++++++++
The thing is that the definition has been discussed on the list and
they were very good overall. However, the first question is not
defining but how our IETF-WGs define protocols. If you cannot find a
definition then write a RFC about the definition and you will notice
that it will not pass through until you define it in the limits that I
tried to define.

There are RFC that were/are in IETF that didn't mention there
applicability statement or use cases, which I think is very important
is designing any protocol as:
1- what was it designed for? and  2- how will it be used?
But thoes RFCs/protocols are for the Internet network, so that is why
IETF is involved. I don't think that IETF is standardizing protocols
that are/can not used in Internet network.

Therefore, all protocols/RFCs in IETF SHOULD be produced in consistent
with IETF purpose, and RECOMMENDED to define its
use-case/applicability. However, it will be nice to think to write a
draft of defining *IETF protocols and technologies*, which I may do in
future interested, because this thread is going long :)

Thanks, Donald and Tony for your points/comments, but we may see the
RFCs that update your pointed-RFCs and in the future it may be updated
as well to invision IETF purpose.

AB
===========================================

On 6/22/12, Donald Eastlake <d3e3e3@gmail.com> wrote:
> How about RFC 1661.
>
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
> On Fri, Jun 22, 2012 at 1:17 PM, Tony Finch <dot@dotat.at> wrote:
>> Randy Bush <randy@psg.com> wrote:
>>
>>> > All protocols in IETF are based on the Internet or/and the IP.
>>>
>>> what a laugh.  try, for example, RFC 826
>>
>> Perhaps a better example is RFC 6325.
>>
>> Tony.
>> --
>> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
>> Cromarty: Northeasterly backing westerly, 5 or 6. Moderate or rough.
>> Occasional rain. Moderate or poor.
>

From barryleiba.mailing.lists@gmail.com  Fri Jun 22 15:09:29 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E95A121F8599 for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 15:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.88
X-Spam-Level: 
X-Spam-Status: No, score=-102.88 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_UNSUB18=0.131, USER_IN_WHITELIST=-100]
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 46e-STskHaQC for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 15:09:29 -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 9533621F8596 for <ietf@ietf.org>; Fri, 22 Jun 2012 15:09:28 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so4523612lbb.31 for <ietf@ietf.org>; Fri, 22 Jun 2012 15:09:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=eM3taNEwum6cmW/QePMabV/TI47wMJmJnIXw1LJMKo8=; b=hQAcNB3u+KABI5cd1UEKDplR9WhPtS+PBs0allm/Wdg9QZ3e3IE+1+/+Xs8dCDB0/V K+Jkcm8RwiVDo0j+5rFFP0SHVDKn9EDF+rqik3Ut+/nO9suB16clbProBQKNd9XPTuAG 2vUs4TXwQKhpC0WGIUNAHqc8Xmt0tIdbR8N3wrFGlPw6qzIoTTztmtHjZC5aoh7vHKOU K6LtwwyKE1XVMuUUA5P+dj0WyXelwXNFdZp2k1Nh40XnmXIWhuSxAtdVQNVY+YqntQlY FRSrGEdINzF3g+84MYItouI+UFo921cmMKDFr2NIcZ8u/vuZEuDAZwJHIhEBe1wsECB4 U5ow==
MIME-Version: 1.0
Received: by 10.112.26.131 with SMTP id l3mr2132469lbg.80.1340402962631; Fri, 22 Jun 2012 15:09:22 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.48.104 with HTTP; Fri, 22 Jun 2012 15:09:22 -0700 (PDT)
In-Reply-To: <50404A860941E07881DF8EEA@JcK-HP8200.jck.com>
References: <CAP0PwYYfBtgGifZVi287JmAWxMm2Rr3jAUg8-BKOKMjskRo47w@mail.gmail.com> <1CC7E58691B04ECDB9D4CE5340072A03@XeonAL> <CAP0PwYa+7F2Y5xotdFTZ4LRGtKWku_DPfdhZWE_RP6REDQEu=A@mail.gmail.com> <50404A860941E07881DF8EEA@JcK-HP8200.jck.com>
Date: Sat, 23 Jun 2012 00:09:22 +0200
X-Google-Sender-Auth: PzGFb0qYHqc1fAzz4xDcggkUUko
Message-ID: <CAC4RtVAedCTLOgL+d9WG45ykR2_zmi9x-aZycc8OmPnebDfExw@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=bcaec55555a4718e8604c316e266
Cc: Robin Uyeshiro <uyeshiro@ifa.hawaii.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 22:09:30 -0000

--bcaec55555a4718e8604c316e266
Content-Type: text/plain; charset=ISO-8859-1

I do jot agree with what John says below.  Look at Section 6.6 of RFC 3979,
where it talks abou who owns the IPR.  In the case given below, the
participant no longer owns the IPR, directly or indirectly.  It's owned by
company X.  The participant is, thus, encouraged to file a third-party
disclosure, but nothing is required.

That said, I, as John, think none of that matters for this brief "sound
bite".  I think this should say nothing more than that if you know about
relevant IPR you or your employer have to disclose.  The "ifs, ands, and
buts," and any other qualifications should be left for the details part.

Barry

On Friday, June 22, 2012, John C Klensin wrote:

>
>
> --On Friday, June 22, 2012 16:52 -0400 Jorge Contreras
> <cntreras@gmail.com <javascript:;>> wrote:
>
> >>  [RU]  Your new (current) company does not "own" the patent
> >>  and neither do you, if you have signed away your rights,
> >> which you are required to do for most companies in the US.
> >> But you should still disclose the patent.
> >>
> >> Ah, I see your point now.  You are right about ownership, but
> >> this would
> > become a "third party disclosure".  It's not required, but is
> > recommended under BCP 79.  It's the same as if you knew about
> > a patent held by another, unrelated company.  Once you leave
> > the first employer, you don't know what the fate of the patent
> > is (e.g., it could be sold, abandoned, etc.) so you aren't
> > required to disclose it (just encouraged to).
>
> Jorge, while I understand your reasoning, it seems to me that
> you are creating a loophole here that we don't want (and that
> isn't justified by the BCP).   Consider the following scenario:
>
> While working for company X, I invent something and a patent
> application is filed with my name as the inventor.  According to
> company policy, I assign all rights to the patent (if awarded)
> to the company.   I then leave company X and join company Y.
> Just to make this a little easier by avoiding some of the
> complex issues associated with disclosing patent applications),
> assume that there are no survivable NDAs with company X that
> prevent my disclosing the patent application to company Y or to
> the IETF.  As another simplification, assume that I became
> active in the IETF only when I joined company Y (that avoids any
> question about my obligation or lack thereof to disclose while I
> was still working for company X).
>
> Now, I find myself in a WG that is considering a technology that
> I reasonable believe interacts with the patent application in
> question.  There is no basis on which I can claim that I didn't
> know about that application... after all, I signed it.   So I
> think I'm _obligated_ to disclose.  Whether that disclosure is
> 1st party (I'm the inventor) or third party (the thing belongs
> to company X) seems like uninteresting hair-splitting.  And my
> disclosure might say "I know about this application but you need
> to check with the patent owner, which was Company X when last I
> had first-hand knowledge, as to what its current status is".
> But asserting that such a disclosure is not required puts the
> notion of what I might reasonably be expected know into a rather
> different light, one that, IMO, might be very damaging to the
> process.
>
> And, no, I don't think the Note Well needs to go nearly into
> that level of detail.  For it, it seems to me that it is
> sufficient to say that one is obligated to disclose if one has
> first-hand, direct, knowledge of the patent (or application) and
> that disclosure under other circumstances is encouraged and
> might, in some cases, be required.
>
>     john
>
>

--bcaec55555a4718e8604c316e266
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I do jot agree with what John says below. =A0Look at Section 6.6 of RFC 397=
9, where it talks abou who owns the IPR. =A0In the case given below, the pa=
rticipant no longer owns the IPR, directly or indirectly. =A0It&#39;s owned=
 by company X. =A0The participant is, thus, encouraged to file a third-part=
y disclosure, but nothing is required.<div>
<br></div><div>That said, I, as John, think none of that matters for this b=
rief &quot;sound bite&quot;. =A0I think this should say nothing more than t=
hat if you know about relevant IPR you or your employer have to disclose. =
=A0The &quot;ifs, ands, and buts,&quot; and any other qualifications should=
 be left for the details part.</div>
<div><br></div><div>Barry<span></span><br><br>On Friday, June 22, 2012, Joh=
n C Klensin  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
--On Friday, June 22, 2012 16:52 -0400 Jorge Contreras<br>
&lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;cntr=
eras@gmail.com&#39;)">cntreras@gmail.com</a>&gt; wrote:<br>
<br>
&gt;&gt; =A0[RU] =A0Your new (current) company does not &quot;own&quot; the=
 patent<br>
&gt;&gt; =A0and neither do you, if you have signed away your rights,<br>
&gt;&gt; which you are required to do for most companies in the US.<br>
&gt;&gt; But you should still disclose the patent.<br>
&gt;&gt;<br>
&gt;&gt; Ah, I see your point now. =A0You are right about ownership, but<br=
>
&gt;&gt; this would<br>
&gt; become a &quot;third party disclosure&quot;. =A0It&#39;s not required,=
 but is<br>
&gt; recommended under BCP 79. =A0It&#39;s the same as if you knew about<br=
>
&gt; a patent held by another, unrelated company. =A0Once you leave<br>
&gt; the first employer, you don&#39;t know what the fate of the patent<br>
&gt; is (e.g., it could be sold, abandoned, etc.) so you aren&#39;t<br>
&gt; required to disclose it (just encouraged to).<br>
<br>
Jorge, while I understand your reasoning, it seems to me that<br>
you are creating a loophole here that we don&#39;t want (and that<br>
isn&#39;t justified by the BCP). =A0 Consider the following scenario:<br>
<br>
While working for company X, I invent something and a patent<br>
application is filed with my name as the inventor. =A0According to<br>
company policy, I assign all rights to the patent (if awarded)<br>
to the company. =A0 I then leave company X and join company Y.<br>
Just to make this a little easier by avoiding some of the<br>
complex issues associated with disclosing patent applications),<br>
assume that there are no survivable NDAs with company X that<br>
prevent my disclosing the patent application to company Y or to<br>
the IETF. =A0As another simplification, assume that I became<br>
active in the IETF only when I joined company Y (that avoids any<br>
question about my obligation or lack thereof to disclose while I<br>
was still working for company X).<br>
<br>
Now, I find myself in a WG that is considering a technology that<br>
I reasonable believe interacts with the patent application in<br>
question. =A0There is no basis on which I can claim that I didn&#39;t<br>
know about that application... after all, I signed it. =A0 So I<br>
think I&#39;m _obligated_ to disclose. =A0Whether that disclosure is<br>
1st party (I&#39;m the inventor) or third party (the thing belongs<br>
to company X) seems like uninteresting hair-splitting. =A0And my<br>
disclosure might say &quot;I know about this application but you need<br>
to check with the patent owner, which was Company X when last I<br>
had first-hand knowledge, as to what its current status is&quot;.<br>
But asserting that such a disclosure is not required puts the<br>
notion of what I might reasonably be expected know into a rather<br>
different light, one that, IMO, might be very damaging to the<br>
process.<br>
<br>
And, no, I don&#39;t think the Note Well needs to go nearly into<br>
that level of detail. =A0For it, it seems to me that it is<br>
sufficient to say that one is obligated to disclose if one has<br>
first-hand, direct, knowledge of the patent (or application) and<br>
that disclosure under other circumstances is encouraged and<br>
might, in some cases, be required.<br>
<br>
 =A0 =A0 john<br>
<br>
</blockquote></div>

--bcaec55555a4718e8604c316e266--

From john-ietf@jck.com  Fri Jun 22 15:45:18 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8780F21F8593 for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 15:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level: 
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 9lDZqnk0GLrD for <ietf@ietfa.amsl.com>; Fri, 22 Jun 2012 15:45:18 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 01CFC21F858F for <ietf@ietf.org>; Fri, 22 Jun 2012 15:45:17 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SiCUr-000HwE-QP; Fri, 22 Jun 2012 18:38:33 -0400
Date: Fri, 22 Jun 2012 18:45:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: When is disclosure required (was: Re: Proposed Update to Note Well)
Message-ID: <33E84E0F92B159A542ECE3DD@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVAedCTLOgL+d9WG45ykR2_zmi9x-aZycc8OmPnebDfExw@mail.gmail.com>
References: <CAP0PwYYfBtgGifZVi287JmAWxMm2Rr3jAUg8-BKOKMjskRo47w@mail.gmail.com> <1CC7E58691B04ECDB9D4CE5340072A03@XeonAL> <CAP0PwYa+7F2Y5xotdFTZ4LRGtKWku_DPfdhZWE_RP6REDQEu=A@mail.gmail.com> <50404A860941E07881DF8EEA@JcK-HP8200.jck.com> <CAC4RtVAedCTLOgL+d9WG45ykR2_zmi9x-aZycc8OmPnebDfExw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Robin Uyeshiro <uyeshiro@ifa.hawaii.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 22:45:18 -0000

(subject changed, since we seem to be in agreement about the
Note Well issues)

--On Saturday, June 23, 2012 00:09 +0200 Barry Leiba
<barryleiba@computer.org> wrote:

> I do jot agree with what John says below.  Look at Section 6.6
> of RFC 3979, where it talks abou who owns the IPR.  In the
> case given below, the participant no longer owns the IPR,
> directly or indirectly.  It's owned by company X.  The
> participant is, thus, encouraged to file a third-party
> disclosure, but nothing is required.

Ok.  Not how I remembered the intent, but that is clearly what
it says.   I do think it creates a gaping loophole for a
company/organization that wanted to subvert the rules, but so it
goes. 

> That said, I, as John, think none of that matters for this
> brief "sound bite".  I think this should say nothing more than
> that if you know about relevant IPR you or your employer have
> to disclose.  The "ifs, ands, and buts," and any other
> qualifications should be left for the details part.

yes.

    john


From lars@netapp.com  Sat Jun 23 01:06:41 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C55B21F854B for <ietf@ietfa.amsl.com>; Sat, 23 Jun 2012 01:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.346
X-Spam-Level: 
X-Spam-Status: No, score=-10.346 tagged_above=-999 required=5 tests=[AWL=0.253, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 Ge27ssdXbKBm for <ietf@ietfa.amsl.com>; Sat, 23 Jun 2012 01:06:41 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0F30B21F854D for <ietf@ietf.org>; Sat, 23 Jun 2012 01:06:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,462,1336374000";  d="p7s'?scan'208";a="657404088"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 23 Jun 2012 01:06:34 -0700
Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q5N86Yjn012117 for <ietf@ietf.org>; Sat, 23 Jun 2012 01:06:34 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.193]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0298.004; Sat, 23 Jun 2012 01:06:34 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: IETF <ietf@ietf.org>
Subject: Re: Proposed Update to Note Well
Thread-Topic: Proposed Update to Note Well
Thread-Index: AQHNT/qkH0OL2Ixd6069A7hzCMzAQZcHGuuAgADoqIA=
Date: Sat, 23 Jun 2012 08:06:32 +0000
Message-ID: <BC155647-7F8A-4053-9B69-760114E85988@netapp.com>
References: <4FCF5B92.3070703@qualcomm.com> <4FCF5F99.3060807@cisco.com> <4FCF6BD5.7080503@qualcomm.com> <4FCF8471.2050701@cisco.com> <AEF1278E-68D1-47D3-932A-8B4940E864A0@harvard.edu> <4FD0679D.60304@cisco.com> <4FD068BC.5050405@cs.tcd.ie> <CAP0PwYZb87zRv0HpTES1twLnnTWUk9ft80bupUoB5f62P3eL=A@mail.gmail.com> <4FD0A53A.6010406@innovationslab.net> <4FD0AAA5.3060400@cisco.com> <C07B527F-37D1-4340-BF7D-F1B6BD263726@gmail.com> <4FD0B3A1.7090001@qualcomm.com> <4FD0B3FA.90704@qualcomm.com> <CAP0PwYYjbaHqkk7z5dXBB4kcH=NhT5_MofHFpwpgXnXvBG_tKQ@mail.gmail.com> <4FD0B86E.8020008@qualcomm.com> <CALaySJKSzsgpmxaiTsHMAEBJNTyPGScMnsfTM=rbMiMEUREb6w@mail.gmail.com> <BD3F594E-0ED1-4079-836F-5D7F5D63AD91@harvard.edu> <CAP0PwYam-arXn1vYebn16d7b_paD7P9ZwKhG1aYgCo2yxuUWaQ@mail.gmail.com> <4FD0F8C5.8000100@qualcomm.com> <4FD10927.8020906@qualcomm.com> <CALaySJ+cMTbcsQQXTa4xhxS+0jBHah4XBXuHEeo4+i2iv1cRVg@mail.gmail.com> <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com> <8B7419F5-0C5C-473A-8EC0-1B 8A483171D8@ietf.org> <C248F169-CCB5-4B88-9950-02714CCC89AE@gmail.com>
In-Reply-To: <C248F169-CCB5-4B88-9950-02714CCC89AE@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_B08244D9-3CA1-4723-8FB2-B5C848BA760B"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jun 2012 08:06:41 -0000

--Apple-Mail=_B08244D9-3CA1-4723-8FB2-B5C848BA760B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,

having just gone through a similar exercise over on the IRTF side of =
things (see http://irtf.org/ipr), I wonder if what we came up with as a =
text couldn't be adapted to also work for the IETF:

> The IRTF follows the IETF Intellectual Property Rights (IPR) =
disclosure rules. This is a summary of these rules as they relate to =
IRTF research group discussions, mailing lists and Internet Drafts:
>=20
> 	=95 If you include your own or your employer=92s IPR in a =
contribution to an IRTF research group, then you must file an IPR =
disclosure with the IETF.
> 	=95 If you recognize your own or your employer=92s IPR in =
someone else=92s contribution and you are participating in the =
discussions in the research group relating to that contribution, then =
you must file an IPR disclosure with the IETF. Even if you are not =
participating in the discussion, the IRTFstill requests that you file an =
IPR disclosure with the IETF.
> 	=95 Finally, the IRTF requests that you file an IPR disclosure =
with the IETF if you recognize IPR owned by others in any IRTF =
contribution.
> You may file an IPR disclosure here: =
http://www.ietf.org/ipr/file-disclosure
>=20
> See RFC 3979 (BCP 79) for definitions of =93IPR=94 and =93contribution=94=
 and for the detailed rules (substituting =93IRTF=94 for =93IETF=94).


Lars=

--Apple-Mail=_B08244D9-3CA1-4723-8FB2-B5C848BA760B
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDYyMzA4MDYyOVowIwYJKoZIhvcNAQkEMRYEFPwv
twLNNSwsLJFRTak0g3bj/ExkMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAA9n7fTB
diad8sn97yMM01ic/8yLd7NuYUKpDUiJ7D2JGLJ4F5sNH5oYAWZ2HrQ7jPd/ZZt+HZ3WhnM4iVGq
00Iik2N0oIQNC/t0AM1J0d33sWbqKyij7pUpN8WSweTPCN+DEXTkXzZ8H7xPlNRzrWoz8yKx0O4r
h802x+dCu3KGmuDBNgRENM7oVkjOauEr+TAmBLimHIAO5UdWgyFtiuujGiVVMOO5lrSvzxnSSyQI
c0ykCLj3fUL4Ir4O5R7+21meHZdAJwxjG9AXW7mhgTabUYu2ax2xpdU4j9v39dkJkv09VmZ82/pf
vkZLqCrWzD4jsC+y5lMd4jId1UTeKcwAAAAAAAA=

--Apple-Mail=_B08244D9-3CA1-4723-8FB2-B5C848BA760B--

From barryleiba.mailing.lists@gmail.com  Sat Jun 23 04:47:56 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E93BB21F84FA for <ietf@ietfa.amsl.com>; Sat, 23 Jun 2012 04:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.946
X-Spam-Level: 
X-Spam-Status: No, score=-102.946 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 t3LZVby5k6Nt for <ietf@ietfa.amsl.com>; Sat, 23 Jun 2012 04:47:56 -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 2968F21F84F0 for <ietf@ietf.org>; Sat, 23 Jun 2012 04:47:55 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so5025718lbb.31 for <ietf@ietf.org>; Sat, 23 Jun 2012 04:47:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=aDOsEgru8zAud9TMbte1QyTG0FHeCzWZsutgyEyfPkA=; b=ksRWyehr2Ryc2mm/Ym9OuuVhUwwhOJY42g6+FKGHxXwDEja2TiRXVIEgM56iODhtMc oo5c7/K8Q/HUpHDEGmnEXVygJgnoSn+BNWPWU1PiKF+mVpytHDbc/7FrAMUz129QjxR6 UqD09eLnmt5zt3+4gUlgYDjOzimaKD7F4VMRTiARtM0GvLfCQnFBIvv4lXBd+4BeAHdT 8Ax2rKorCVFrj+Nerxo0oNV6LYIGYCG53SRtunku8xcisVBW1kNORZ1+24o6TPWQ5qiU zcsc5/kpXqSh5CZFalHedaYh5zOUr1XVmdYWu0pwdnlCRVrEwZUD0oeOsy2tD9mq7vKw C5KQ==
MIME-Version: 1.0
Received: by 10.152.108.144 with SMTP id hk16mr5400747lab.2.1340452074999; Sat, 23 Jun 2012 04:47:54 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.48.104 with HTTP; Sat, 23 Jun 2012 04:47:54 -0700 (PDT)
In-Reply-To: <BC155647-7F8A-4053-9B69-760114E85988@netapp.com>
References: <4FCF5B92.3070703@qualcomm.com> <4FCF5F99.3060807@cisco.com> <4FCF6BD5.7080503@qualcomm.com> <4FCF8471.2050701@cisco.com> <AEF1278E-68D1-47D3-932A-8B4940E864A0@harvard.edu> <4FD0679D.60304@cisco.com> <4FD068BC.5050405@cs.tcd.ie> <CAP0PwYZb87zRv0HpTES1twLnnTWUk9ft80bupUoB5f62P3eL=A@mail.gmail.com> <4FD0A53A.6010406@innovationslab.net> <4FD0AAA5.3060400@cisco.com> <C07B527F-37D1-4340-BF7D-F1B6BD263726@gmail.com> <4FD0B3A1.7090001@qualcomm.com> <4FD0B3FA.90704@qualcomm.com> <CAP0PwYYjbaHqkk7z5dXBB4kcH=NhT5_MofHFpwpgXnXvBG_tKQ@mail.gmail.com> <4FD0B86E.8020008@qualcomm.com> <CALaySJKSzsgpmxaiTsHMAEBJNTyPGScMnsfTM=rbMiMEUREb6w@mail.gmail.com> <BD3F594E-0ED1-4079-836F-5D7F5D63AD91@harvard.edu> <CAP0PwYam-arXn1vYebn16d7b_paD7P9ZwKhG1aYgCo2yxuUWaQ@mail.gmail.com> <4FD0F8C5.8000100@qualcomm.com> <4FD10927.8020906@qualcomm.com> <CALaySJ+cMTbcsQQXTa4xhxS+0jBHah4XBXuHEeo4+i2iv1cRVg@mail.gmail.com> <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com> <C248F169-CCB5-4B88-9950-02714CCC89AE@gmail.com> <BC155647-7F8A-4053-9B69-760114E85988@netapp.com>
Date: Sat, 23 Jun 2012 13:47:54 +0200
X-Google-Sender-Auth: fmTMbgaE08gvaMl6M4SQ2TKiG6s
Message-ID: <CAC4RtVBF3Xh5Cb3huvANQTRe6zQPNkAwoZJn12-6z+HsYR8gsg@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
From: Barry Leiba <barryleiba@computer.org>
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: multipart/alternative; boundary=bcaec54d4dd6c4d01304c322519a
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jun 2012 11:47:57 -0000

--bcaec54d4dd6c4d01304c322519a
Content-Type: text/plain; charset=ISO-8859-1

> having just gone through a similar exercise over on the IRTF side of
things
> (see http://irtf.org/ipr), I wonder if what we came up with as a text
couldn't
> be adapted to also work for the IETF

It's too long.  We're looking for something *very* short, just a "sound
bite", which gets the main point across and sends anyone who needs more
details to the right place.  That's why we're trying to resist all the
"Yes, but that's not quite it, and you have to add this" modifications.  I
think even the initial one we posted is a bit too long, and PSA has
distilled it, in a couple of his messages, to what I think is the real
essence.

Barry

--bcaec54d4dd6c4d01304c322519a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<span class=3D"Apple-style-span" style>&gt; having just gone through a simi=
lar exercise over on the IRTF side of things</span><div><span class=3D"Appl=
e-style-span" style>&gt; (see=A0<a href=3D"http://irtf.org/ipr" target=3D"_=
blank">http://irtf.org/ipr</a>), I wonder if what we came up with as a text=
 couldn&#39;t</span></div>
<div><span class=3D"Apple-style-span" style>&gt; be adapted to also work fo=
r the IETF</span><br dir=3D"ltr"></div><div><span class=3D"Apple-style-span=
" style><br></span></div><div><span class=3D"Apple-style-span" style>It&#39=
;s too long. =A0We&#39;re looking for something *very* short, just a &quot;=
sound bite&quot;, which gets the main point across and sends anyone who nee=
ds more details to the right place. =A0That&#39;s why we&#39;re trying to r=
esist all the &quot;Yes, but that&#39;s not quite it, and you have to add t=
his&quot; modifications. =A0I think even the initial one we posted is a bit=
 too long, and PSA has distilled it, in a couple of his messages, to what I=
 think is the real essence.</span></div>
<div><span class=3D"Apple-style-span" style><br></span></div><div><span cla=
ss=3D"Apple-style-span" style>Barry<span></span></span></div>

--bcaec54d4dd6c4d01304c322519a--

From abdussalambaryun@gmail.com  Sun Jun 24 02:09:28 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D1FA21F859F; Sun, 24 Jun 2012 02:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, 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 5+NWEG4ggUrK; Sun, 24 Jun 2012 02:09:27 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id AD47B21F854D; Sun, 24 Jun 2012 02:09:23 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1712959vbb.31 for <multiple recipients>; Sun, 24 Jun 2012 02:09:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=4O9JGHEmaJUz98z80UI1t9lOhzZLN1uktn8mFQln0wY=; b=CiGJXvM71VLrk+KtEOMjGa7+HB9EvjbvxPxqVBwXK1KKQQiOdTqKaqlxDzn4iUC9Sq AJVBk8yBP2bomo7gteNmCMTkirBDkKNEUVIx95tLJN1zvIMWkknJJcODH3LMyp1tdZZ1 UZrzRChRR80wpBHmHJgavwMyUV93rfFkUOPe35LkegtvVa2SzogDPQ2ApFscuJU4CqLc TGib7gLc3su7JUwRvx0veSiEmDcpoEOeyIcbl85a51AegskRRsVQeWgh1PjJMx40bnF7 fulQADd4WDcu11S9RBMFF6QyG3G4ePN/gZUNY9Vnl3gSOFu/8MTxmBGwY1ivIvHohW7L d8Yg==
MIME-Version: 1.0
Received: by 10.220.153.80 with SMTP id j16mr4909329vcw.55.1340528963111; Sun, 24 Jun 2012 02:09:23 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Sun, 24 Jun 2012 02:09:22 -0700 (PDT)
Date: Sun, 24 Jun 2012 11:09:22 +0200
Message-ID: <CADnDZ89VAZP8LSD2u090S9R3LGUJubFPmW8sCmBB2GEQWKBY4Q@mail.gmail.com>
Subject: Proposing to create an IETF WG in the general area
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: datatracker-rqmts@ietf.org, charter-tool@ietf.org, "iesg@ietf.org" <iesg@ietf.org>, ietf-action@ietf.org, Gen-Art@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jun 2012 09:09:28 -0000

Hi All,

I think there is a need to have at least one WG in the General Area
(GA). The question is: why we have a GA without focused work or
community representation? I understand from the IETF procedures that
this organisation works through WGs, so it can make progresses through
WGs. The GA has no WG, therefore, Does that mean the area is not
progressing or there is no work done in the area? Furthermore, the
general area related RFCs cannot be found under such IETF-tool-trac
like in other areas.

Proposed WG: will look into RFCs related to the area and to find out
what is missing, or how to direct/organise the GA's input decisions or
I-D submitted by the IETF community.

Overall, IMHO there are work done for the GA purposes but it is not
directed/organised by a IETF-WG, therefore, I propose to create a WG
for GA with a trac.tool to make progress efficient and easy to follow
up :)

Regards,

Abdussalam Baryun,
University of Glamorgan, UK
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
<In discussions one may be wrong, or may be right, but it does not matter
  if we work together as a team to progress and resolve all open issues.
  IETF WGs are always right, and they represent the IETF community. >

From abdussalambaryun@gmail.com  Sun Jun 24 02:21:56 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E4E21F84FA; Sun, 24 Jun 2012 02:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.589
X-Spam-Level: 
X-Spam-Status: No, score=-3.589 tagged_above=-999 required=5 tests=[AWL=0.010,  BAYES_00=-2.599, 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 VdgFAoR9JcMl; Sun, 24 Jun 2012 02:21:55 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 98E4E21F84E6; Sun, 24 Jun 2012 02:21:55 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so1710634vcq.31 for <multiple recipients>; Sun, 24 Jun 2012 02:21:55 -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=koMJF3qGmYeBYGQlgiwuAcMRsBxY7u+bnVDkRoQppNo=; b=Kx3RX2Ec0AO/x6dv58CPtn96b7AAFmNym1lZKomwdU2Fezl/etWPu1bWyDwww0l54K OuzpeqHxT+w97U9JlrZa2GyZ0nvlDBd+ccxtNPNbjlNm6zztMHL3gBdjxBD2blQ3tXIw y4yCHAVZ4zwigv/XmnwBOkjAyxdI25icV73mUXExkJXoJTXWl45ddjT2iqWArEaywle3 RFR0G3ZxFnZCd4igjjFQK5eTbR8QdTonXphy2oQQval9dMOIKZAC0VPl0ZPy/WkHptPV RNo8/AjIGKpXQg6q7x3j1wTG2lslQ0T3/fJ4ZcEmEqi41INMbDO4OGXJ5Bc/J3ffI+U8 Xtzw==
MIME-Version: 1.0
Received: by 10.220.153.80 with SMTP id j16mr4925719vcw.55.1340529715108; Sun, 24 Jun 2012 02:21:55 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Sun, 24 Jun 2012 02:21:55 -0700 (PDT)
In-Reply-To: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com>
Date: Sun, 24 Jun 2012 11:21:55 +0200
Message-ID: <CADnDZ89c9VsvBydkTKv2u+rCTWmcbRyd5Wy12OEbXsgYWPrO2w@mail.gmail.com>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iesg@ietf.org" <iesg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jun 2012 09:21:56 -0000

Propose to include in the I-D <draft-hoffman-tao-as-web-page-02.txt>
an IETF-WG that is created in the IETF General Area to discuss Tao
document/webpage issues,

AB
===

From tglassey@earthlink.net  Sun Jun 24 06:20:33 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D184521F860B for <ietf@ietfa.amsl.com>; Sun, 24 Jun 2012 06:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
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 r+rCLrrBoF4B for <ietf@ietfa.amsl.com>; Sun, 24 Jun 2012 06:20:33 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 596F921F8633 for <ietf@ietf.org>; Sun, 24 Jun 2012 06:20:33 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=GxAjioNK7sSNCcqikhA3/XnWQRNgN9zdgklkLBzyMAq9DLdXWR36bT1pniYzFBeO; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1Simjw-0008AS-Ph; Sun, 24 Jun 2012 09:20:32 -0400
Message-ID: <4FE71418.7060600@earthlink.net>
Date: Sun, 24 Jun 2012 06:20:24 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>, ietf <ietf@ietf.org>
Subject: Re: Protocol Definition
References: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com> <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com> <m2y5ng6p99.wl%randy@psg.com> <alpine.LSU.2.00.1206221815380.18854@hermes-2.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1206221815380.18854@hermes-2.csi.cam.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79754bb59eb2d551a848e27f74a711dc45350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jun 2012 13:20:33 -0000

On 6/22/2012 10:17 AM, Tony Finch wrote:
> Randy Bush <randy@psg.com> wrote:
>
>>> All protocols in IETF are based on the Internet or/and the IP.
>> what a laugh.  try, for example, RFC 826
> Perhaps a better example is RFC 6325.
>
> Tony.
Try this

"The IETFis and open and fair framework  produces standards for use in 
both networking and internetworking services for global communication" 
and the reasoning is that when ITU and other orgs like it were formed 
there was not Internetworking or Local Area Networks and so the IETF was 
formed to emerge the need to facilitate standards in these two key areas 
which other groups like ITU and IEEE with the underlying 802 work were 
not providing.

-- 
//Confidential Mailing - Please destroy this if you are not the intended recipient.


From tglassey@earthlink.net  Sun Jun 24 06:23:06 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31E9021F861A for <ietf@ietfa.amsl.com>; Sun, 24 Jun 2012 06:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.092
X-Spam-Level: 
X-Spam-Status: No, score=-1.092 tagged_above=-999 required=5 tests=[AWL=0.907,  BAYES_00=-2.599, J_CHICKENPOX_44=0.6]
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 6aY+SJIZmL+q for <ietf@ietfa.amsl.com>; Sun, 24 Jun 2012 06:23:05 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 5DBFA21F860B for <ietf@ietf.org>; Sun, 24 Jun 2012 06:23:05 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=lTxavvy07cxf6WBlDG+pex6gkS5q2E/G75/8uFAvZN7niYJYWf2oTRJjxB0cbMXl; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1SimmL-0004yj-Un for ietf@ietf.org; Sun, 24 Jun 2012 09:23:02 -0400
Message-ID: <4FE714AD.4070905@earthlink.net>
Date: Sun, 24 Jun 2012 06:22:53 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposing to create an IETF WG in the general area
References: <CADnDZ89VAZP8LSD2u090S9R3LGUJubFPmW8sCmBB2GEQWKBY4Q@mail.gmail.com>
In-Reply-To: <CADnDZ89VAZP8LSD2u090S9R3LGUJubFPmW8sCmBB2GEQWKBY4Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec797aeda6796cbec53ae0f89ab6f094e202350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jun 2012 13:23:06 -0000

On 6/24/2012 2:09 AM, Abdussalam Baryun wrote:
> Hi All,
>
> I think there is a need to have at least one WG in the General Area
> (GA). The question is: why we have a GA without focused work or
> community representation? I understand from the IETF procedures that
> this organisation works through WGs, so it can make progresses through
> WGs. The GA has no WG, therefore, Does that mean the area is not
> progressing or there is no work done in the area? Furthermore, the
> general area related RFCs cannot be found under such IETF-tool-trac
> like in other areas.
>
> Proposed WG: will look into RFCs related to the area and to find out
> what is missing, or how to direct/organise the GA's input decisions or
> I-D submitted by the IETF community.
>
> Overall, IMHO there are work done for the GA purposes but it is not
> directed/organised by a IETF-WG, therefore, I propose to create a WG
> for GA with a trac.tool to make progress efficient and easy to follow
> up :)

Gen Area groups also functioned  as reception gateways for projects too 
meaning that the WG Manager in this group would be a lobbyist as well in 
passing new projects to other WG's once set up.

So then would this WG also be an incubator for projects?

Todd
> Regards,
>
> Abdussalam Baryun,
> University of Glamorgan, UK
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> <In discussions one may be wrong, or may be right, but it does not matter
>    if we work together as a team to progress and resolve all open issues.
>    IETF WGs are always right, and they represent the IETF community. >
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2180 / Virus Database: 2437/5089 - Release Date: 06/23/12
>
>


-- 
//Confidential Mailing - Please destroy this if you are not the intended recipient.


From duerst@it.aoyama.ac.jp  Mon Jun 25 03:36:01 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 396DB21F84D5 for <ietf@ietfa.amsl.com>; Mon, 25 Jun 2012 03:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.449
X-Spam-Level: 
X-Spam-Status: No, score=-99.449 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
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 9ZykapaTx-ZN for <ietf@ietfa.amsl.com>; Mon, 25 Jun 2012 03:35:57 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 29C9821F842B for <ietf@ietf.org>; Mon, 25 Jun 2012 03:35:56 -0700 (PDT)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5PAZiSC030005 for <ietf@ietf.org>; Mon, 25 Jun 2012 19:35:45 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 2e70_bb6e_8511b916_beb1_11e1_8b5b_001d096c566a; Mon, 25 Jun 2012 19:35:44 +0900
Received: from [IPv6:::1] ([133.2.210.1]:35766) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D737D> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 25 Jun 2012 19:35:45 +0900
Message-ID: <4FE83EF5.1050000@it.aoyama.ac.jp>
Date: Mon, 25 Jun 2012 19:35:33 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> <4FE4E19F.2050400@cs.tcd.ie>
In-Reply-To: <4FE4E19F.2050400@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jun 2012 10:36:01 -0000

Hello Stephen, others,

On 2012/06/23 6:20, Stephen Farrell wrote:
>
> Hi All,
>
> I went back through the IETF LC comments and think that we've
> resolved them all on the list and have the changes in this
> version [1] of the draft, with the possible exception of those
> below.
>
> The issues raised but not so far obviously resolved on the
> list were I think:
>
> 1) inclusion of content type
> 2) nih as a URI scheme or not
>
> For (1) this version includes ct= in draft-farrell-decade-ni
> (the only changes to draft-hallambaker-decade-ni-params [2]
> made so far are those that flow from moving that text), so
> I'd hope that this version resolves that but would welcome
> feedback on the new text from folks who commented. I'd hope
> it should be ok, modulo some text tweaks.
>
> For (2) we've left nih in as a URI scheme in this version.
> We're still in favour of keeping it that way and have added
> some language about why its there and is done like that. I'm
> guessing that Martin at least won't be happy (but who knows;-),
> so again comments are welcome as to whether the new text helps
> or not.

When reading your explanations, I had hoped that there would be some 
text along the lines of "different use case" that would really explain 
why two separate schemes are necessary. For example something similar to 
what Graham was mentioning at
http://www.ietf.org/mail-archive/web/ietf/current/msg73760.html, which I 
understand is similar to what I mentioned as fingerprints in our discussion.

Unfortunately, what I find is the following:

 > The justification for using a URI scheme for this is that that might
 > help a user agent for the speaker to better display the value, or
 > perhaps if there was some use-case for a machine to speak the value.

So we are creating a new URI scheme because *perhaps* there is a use 
case? Or because it *might* help? In the whole discussion, I was always 
ready to accept that there are different use cases, assuming that they 
could be clearly explained. I'm really wondering why this is so 
difficult. If these use cases really exist, it shouldn't be that 
difficult, and it shouldn't sound so vague, or should it? I'm not 
necessarily blaming you, but between you, your coauthors, and the WG 
that apparently proposed this, it shouldn't be that hard to come up with 
a better and more definite explanation than the sentence above.


 > We do not include the query string since there is no way to ensure
 > that its value might be spoken unambiguously, and similarly for the
 > authority, where e.g. internationalised forms of domain name could
 > not be usefully spoken.  This leaves the hash value as the only part
 > of the ni URI that we feel can be usefully included.  But since
 > speakers or listeners (or speech recognition) may err, we also
 > include a check-digit to catch common errors.

It is really strange to assume that text-to-speech software would work 
for English (or ASCII in general), but not for other scripts or 
languages. Sure, the level of text-to-speech software may not be exactly 
the same for each script and each language, but that's no reason to 
prohibit a domain name. There are definitely millions of domain names in 
e.g. Chinese or Japanese or Russian,... that can be spoken and re-typed 
quite unambiguously, and that users would have much less problems with 
than a long string of hex digits. (And we would still have the check 
digit, anyway.) On the other hand, it is quite possible to create domain 
names with ASCII/English that neither humans nor text-to-speech engines 
will be able to pronounce right.


Regards,   Martin.


> But in the end we'll go with Barry's consensus call
> on this if he judges that we're in the rough, rather than the
> folks who've commented on this topic. In that case I'll put
> out a version with no nih scheme and the "human speakable"
> format as just a textual convention (with a check-digit,
> which'd be plain odd IMO, the uri scheme is the right idea
> really:-)
>
> Please let me know if I've missed addressing anything else
> or if you have any other comments.
>
> Cheers,
> S.
>
> [1] http://tools.ietf.org/html/draft-farrell-decade-ni
> [2] http://tools.ietf.org/html/draft-hallambaker-decade-ni-params
>
> (Note: only [1] is in IETF LC...just in case someone's
> confused about that:-)
>
> On 06/04/2012 03:18 PM, The IESG wrote:
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Naming Things with Hashes'
>>    <draft-farrell-decade-ni-07.txt>  as Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2012-07-02. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     This document defines a set of ways to identify a thing using the
>>     output from a hash function, specifying URI, URL, binary and human
>>     "speakable" formats for these names.  The various formats are
>>     designed to support, but not require, a strong link to the referenced
>>     object such that the referenced object may be authenticated to the
>>     same degree as the reference to it.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-farrell-decade-ni/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-farrell-decade-ni/ballot/
>>
>>
>> The following IPR Declarations may be related to this I-D:
>>
>>     http://datatracker.ietf.org/ipr/1773/
>>     http://datatracker.ietf.org/ipr/1775/
>>
>>
>>
>>
>>
>
>

From stephen.farrell@cs.tcd.ie  Mon Jun 25 05:06:13 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77BB721F8532 for <ietf@ietfa.amsl.com>; Mon, 25 Jun 2012 05:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.292
X-Spam-Level: 
X-Spam-Status: No, score=-102.292 tagged_above=-999 required=5 tests=[AWL=-0.308, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
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 F-mzWdxabYF3 for <ietf@ietfa.amsl.com>; Mon, 25 Jun 2012 05:06:09 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 3912621F851C for <ietf@ietf.org>; Mon, 25 Jun 2012 05:06:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id DC896171474; Mon, 25 Jun 2012 13:06:04 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1340625960; bh=A0pBbjysOz/5hj FcvbiDNzwKqBTqcb5N/N22H8W+asY=; b=TXQxqwJ74UNwvBnJx7DK0OZL2s6ibF QhBfxy5A6Cm2qyj6g+uR5Mx+CrXaEewNpi3+Zd4ICZZYxe3Iv43EGy2BtNpbUD0w q81m+zv1lu613qfK+LvMKYAxnh5Amfnn/kqo2V7OYGlpeHEE1/z510c0hrWaz328 sPWAKhTMlduyXw89qH17gUQK3ekJikqF0pwqPQzeDgNparbSnl4PK0nHo8UmjWRL G2zqfqjhlGsVTf7F6wocAgeKO68MVDHaqi/E3oyBMmGyCKEq7P7Q12/jQy7lL8Zc 0n7YX4rM9U3TemrhNngmOL7/Us7ZWhOI3OlMvbZUmSi81eT0y1f/L6cw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id GzHW-UrgpvEY; Mon, 25 Jun 2012 13:06:00 +0100 (IST)
Received: from [IPv6:2001:770:10:203:d86f:8845:f318:4fa9] (unknown [IPv6:2001:770:10:203:d86f:8845:f318:4fa9]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 2C4E1171523; Mon, 25 Jun 2012 13:05:55 +0100 (IST)
Message-ID: <4FE85424.9000409@cs.tcd.ie>
Date: Mon, 25 Jun 2012 13:05:56 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> <4FE4E19F.2050400@cs.tcd.ie> <4FE83EF5.1050000@it.aoyama.ac.jp>
In-Reply-To: <4FE83EF5.1050000@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jun 2012 12:06:13 -0000

Hi Martin,

On 06/25/2012 11:35 AM, "Martin J. Dürst" wrote:
> Hello Stephen, others,
> 
> On 2012/06/23 6:20, Stephen Farrell wrote:
>>
>> Hi All,
>>
>> I went back through the IETF LC comments and think that we've
>> resolved them all on the list and have the changes in this
>> version [1] of the draft, with the possible exception of those
>> below.
>>
>> The issues raised but not so far obviously resolved on the
>> list were I think:
>>
>> 1) inclusion of content type
>> 2) nih as a URI scheme or not
>>
>> For (1) this version includes ct= in draft-farrell-decade-ni
>> (the only changes to draft-hallambaker-decade-ni-params [2]
>> made so far are those that flow from moving that text), so
>> I'd hope that this version resolves that but would welcome
>> feedback on the new text from folks who commented. I'd hope
>> it should be ok, modulo some text tweaks.
>>
>> For (2) we've left nih in as a URI scheme in this version.
>> We're still in favour of keeping it that way and have added
>> some language about why its there and is done like that. I'm
>> guessing that Martin at least won't be happy (but who knows;-),
>> so again comments are welcome as to whether the new text helps
>> or not.
> 
> When reading your explanations, I had hoped that there would be some
> text along the lines of "different use case" that would really explain
> why two separate schemes are necessary. For example something similar to
> what Graham was mentioning at
> http://www.ietf.org/mail-archive/web/ietf/current/msg73760.html, which I
> understand is similar to what I mentioned as fingerprints in our
> discussion.
> 
> Unfortunately, what I find is the following:
> 
>> The justification for using a URI scheme for this is that that might
>> help a user agent for the speaker to better display the value, or
>> perhaps if there was some use-case for a machine to speak the value.
> 
> So we are creating a new URI scheme because *perhaps* there is a use
> case? Or because it *might* help? In the whole discussion, I was always
> ready to accept that there are different use cases, assuming that they
> could be clearly explained. I'm really wondering why this is so
> difficult. If these use cases really exist, it shouldn't be that
> difficult, and it shouldn't sound so vague, or should it? I'm not
> necessarily blaming you, but between you, your coauthors, and the WG
> that apparently proposed this, it shouldn't be that hard to come up with
> a better and more definite explanation than the sentence above.

IMO the use-case is clear, and is stated in the first sentence
of section 7.

I believe that Graham got the use-case, and accepted that its
different from ni URIs, but was questioning the need for nih to
be a uri scheme. He can confirm or refute that himself I guess,
but quoting his mail [1] (just before the one you reference):

"I can see that there are distinct use-cases here, and I
think you have reasonable grounds for not wanting to combine
them."

   [1] http://www.ietf.org/mail-archive/web/ietf/current/msg73758.html

Maybe the language I added for why we want nih as a uri
scheme is not sufficiently clear, or isn't convincing, but
that's a different argument.

>> We do not include the query string since there is no way to ensure
>> that its value might be spoken unambiguously, and similarly for the
>> authority, where e.g. internationalised forms of domain name could
>> not be usefully spoken.  This leaves the hash value as the only part
>> of the ni URI that we feel can be usefully included.  But since
>> speakers or listeners (or speech recognition) may err, we also
>> include a check-digit to catch common errors.
> 
> It is really strange to assume that text-to-speech software would work
> for English (or ASCII in general), but not for other scripts or
> languages. Sure, the level of text-to-speech software may not be exactly
> the same for each script and each language, but that's no reason to
> prohibit a domain name. There are definitely millions of domain names in
> e.g. Chinese or Japanese or Russian,... that can be spoken and re-typed
> quite unambiguously, and that users would have much less problems with
> than a long string of hex digits. (And we would still have the check
> digit, anyway.) On the other hand, it is quite possible to create domain
> names with ASCII/English that neither humans nor text-to-speech engines
> will be able to pronounce right.

The point is that we only leave in the ascii-hex. The
goal being to reduce this to something that can be
unambiguously spoken, and I think ascii-hex is about
as close as one can get to that. Anything else brings
additional ambiguity and hence is left out.

Its true that the machine-reading/recognition bit is
speculative though, but I don't think its much of a leap,
nor is it really crucial to the argument.

Cheers,
S.


> 
> 
> Regards,   Martin.
> 
> 
>> But in the end we'll go with Barry's consensus call
>> on this if he judges that we're in the rough, rather than the
>> folks who've commented on this topic. In that case I'll put
>> out a version with no nih scheme and the "human speakable"
>> format as just a textual convention (with a check-digit,
>> which'd be plain odd IMO, the uri scheme is the right idea
>> really:-)
>>
>> Please let me know if I've missed addressing anything else
>> or if you have any other comments.
>>
>> Cheers,
>> S.
>>
>> [1] http://tools.ietf.org/html/draft-farrell-decade-ni
>> [2] http://tools.ietf.org/html/draft-hallambaker-decade-ni-params
>>
>> (Note: only [1] is in IETF LC...just in case someone's
>> confused about that:-)
>>
>> On 06/04/2012 03:18 PM, The IESG wrote:
>>>
>>> The IESG has received a request from an individual submitter to consider
>>> the following document:
>>> - 'Naming Things with Hashes'
>>>    <draft-farrell-decade-ni-07.txt>  as Proposed Standard
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2012-07-02. Exceptionally, comments
>>> may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>     This document defines a set of ways to identify a thing using the
>>>     output from a hash function, specifying URI, URL, binary and human
>>>     "speakable" formats for these names.  The various formats are
>>>     designed to support, but not require, a strong link to the
>>> referenced
>>>     object such that the referenced object may be authenticated to the
>>>     same degree as the reference to it.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-farrell-decade-ni/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-farrell-decade-ni/ballot/
>>>
>>>
>>> The following IPR Declarations may be related to this I-D:
>>>
>>>     http://datatracker.ietf.org/ipr/1773/
>>>     http://datatracker.ietf.org/ipr/1775/
>>>
>>>
>>>
>>>
>>>
>>
>>


From Tom.Haynes@netapp.com  Fri Jun 22 08:06:16 2012
Return-Path: <Tom.Haynes@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D81C821F86F7; Fri, 22 Jun 2012 08:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 8fEOXcta-sQ4; Fri, 22 Jun 2012 08:06:16 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id DF36021F86E5; Fri, 22 Jun 2012 08:06:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,458,1336374000"; d="scan'208";a="657232717"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 22 Jun 2012 08:06:15 -0700
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q5MF6FDB015259; Fri, 22 Jun 2012 08:06:15 -0700 (PDT)
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.92]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0298.004; Fri, 22 Jun 2012 08:05:23 -0700
From: "Haynes, Tom" <Tom.Haynes@netapp.com>
To: "rbarnes@bbn.com" <rbarnes@bbn.com>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org" <draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [nfsv4] Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11 (fwd)
Thread-Topic: [nfsv4] Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11 (fwd)
Thread-Index: AQHNUIiR3/6yfq+JwEWuYsxcwIlj9Q==
Date: Fri, 22 Jun 2012 15:06:14 +0000
Message-ID: <CC08E06F.1AFEC%tom.haynes@netapp.com>
In-Reply-To: <alpine.LFD.2.02.1206201253010.38625@jlentini-linux.nane.netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A3AB0AC6EF04794EB4191E199A92143B@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 25 Jun 2012 07:15:31 -0700
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:06:17 -0000

<comments inline>

On 6/20/12 11:53 AM, "James Lentini" <jlentini@netapp.com> wrote:

>
>Below is the Gen-ART review comments for the FedFS admin protocol.
>
>-james
>
>---------- Forwarded message ----------
>Date: Tue, 19 Jun 2012 11:31:42 -0400
>From: Richard L. Barnes <rbarnes@bbn.com>
>To: ietf@ietf.org, The IESG <iesg@ietf.org>,
>    draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org, gen-art@ietf.org
>Subject: Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11
>
>I am the assigned Gen-ART reviewer for this draft. For background on
>Gen-ART, please see the FAQ at
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>Please resolve these comments along with any other Last Call comments
>you may receive.
>
>Document: draft-ietf-nfsv4-federated-fs-admin-11
>Reviewer: Richard Barnes
>Review Date: Jun-19-2012
>IETF LC End Date: Not known
>IESG Telechat date: Jun-28-2012
>
>Summary: Almost ready, couple of issues
>
>MAJOR:=20
>
>4. / 7.
>This protocol allows for the provisioning of security information as part
>of the FedFsNsdbParams, in the form of a certificate to be used in
>verifying a TLS server certificate.  There are two notable issues with
>how the document does this now:
>1. Section 4 does not adequately specify how the certificate in the
>FedFsNsdbParams should be used in the verification process.  Is it to be
>used as a trust anchor, so that any subordinate certificate is considered
>valid?  Or perhaps it is to be matched against the end-entity
>certificate.  In either case, it seems like it would be sufficient to
>provision a certificate fingerprint (or even a public key fingerprint)
>instead of the whole certificate.
>2. In the security considerations, the document should discuss the
>implications of provisioning trust information in this way (depending on
>how it is used), and any requirements for security mechanisms to be used
>in these cases.
>


I'm going to have to work with the rest of the group to answer this one.


>
>MINOR:
>
>2.=20
>It's not clear what the difference is between utf8string_cs and
>utf8string_cis.  Should you mention at some point that these MUST be
>UTF-8, even though the XDR won't enforce that?  (Say, at the beginning of
>Section 4?)


Argh, we did away with utf8string_cs and utf8string_cis in 3530bis.


utf8string_cis should be utf8val_REQUIRED4
utf8string_cs should be ascii_REQUIRED4

In 3530bis, these are defined as:

typedef :opaque  :utf8string<>:UTF-8 encoding for strings.
typedef :utf8string:utf8_expected:String expected to be UTF-8 but no
validation
typedef :utf8string:utf8val_RECOMMENDED4:String SHOULD be sent UTF-8 and
SHOULD be validated
typedef :utf8string:utf8val_REQUIRED4:String MUST be sent UTF-8 and MUST
be validated
typedef :utf8string:ascii_REQUIRED4:String MUST be sent as ASCII and thus
is automatically UTF-8


I'll change the types and there is already some text pointing the reader
to Chapter 12 of 3530bis.


>
>3.
>It's not clear to me how FEDFS_ERR_PERM differs from FEDFS_ERR_ACCESS.  I
>don't see it called out for use anywhere in the procedure calls.  Perhaps
>this is a legacy of prior versions that should be deleted?


This is inherited from the base NFSv4.0 documentation and also NFSv3. It
is also the difference between EPERM and EACCES. (see
http://www.wlug.org.nz/EACCES)


13.1.6.1.  NFS4ERR_ACCESS (Error Code 13)

   Indicates permission denied.  The caller does not have the correct
   permission to perform the requested operation.  Contrast this with
   NFS4ERR_PERM (Section 13.1.6.2), which restricts itself to owner or
   privileged user permission failures.

13.1.6.2.  NFS4ERR_PERM (Error Code 1)

   Indicates requester is not the owner.  The operation was not allowed
   because the caller is neither a privileged user (root) nor the owner
   of the target of the operation.






>
>
>EDITORIAL:=20
>
>3.=20
>The definition of FEDFS_ERR_LOOP isn't actually related to looping.  It
>seems like this should either detect a loop (e.g., via a repeated name),
>or be renamed something like FEDFS_ERR_TOOMANYREFERS.


This has its roots in a Linux error code:

>> As I recall this error is supposed to be returned when fedfsd is passed
>>a pathname that contains too many symlinks.  The equivalent errno on
>>Linux is called ELOOP.

We are striving to maintain parity.





>
>4. "The port is the NSDB transport port for the LDAP interface"
>Suggest rewording to clarify that this is an LDAP/TCP port (I initially
>wondered if other transports could be used), e.g.:
>"The port value in the FedFsNsdbName indicates the LDAP port on the NSDB"


Thanks, we've been struggling with this issue, I'll take your suggested
change here.

>
>_______________________________________________
>nfsv4 mailing list
>nfsv4@ietf.org
>https://www.ietf.org/mailman/listinfo/nfsv4


From mellon@fugue.com  Fri Jun 22 13:11:33 2012
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F4EA21F8627; Fri, 22 Jun 2012 13:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 kdwpohG7zGLT; Fri, 22 Jun 2012 13:11:32 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id D843521F8625; Fri, 22 Jun 2012 13:11:32 -0700 (PDT)
Received: from [10.1.10.17] (173-162-214-218-NewEngland.hfc.comcastbusiness.net [173.162.214.218]) by toccata.fugue.com (Postfix) with ESMTPSA id CFD3E2381565; Fri, 22 Jun 2012 16:11:30 -0400 (EDT)
Subject: Re: [dhcwg] Last Call:	<draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt> (Dynamic	Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a	Location Uniform Resource Identifier (URI)) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <3AE0A5BB-E5B7-46A3-A3D6-3F7C8FB84016@cdt.org>
Date: Fri, 22 Jun 2012 16:11:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <33AFBD35-FDCA-4424-9EB1-1903976085B0@fugue.com>
References: <20120531184851.30358.8816.idtracker@ietfa.amsl.com> <ADE21D06-F6A4-4018-A999-6B50EC94F3C7@fugue.com> <3AE0A5BB-E5B7-46A3-A3D6-3F7C8FB84016@cdt.org>
To: Alissa Cooper <acooper@cdt.org>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Mon, 25 Jun 2012 07:15:31 -0700
Cc: GEOPRIV WG <geopriv@ietf.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 20:11:33 -0000

On Jun 22, 2012, at 3:59 PM, Alissa Cooper wrote:
> My understanding is that the option is encoded this way both for =
extensibility and because the Valid-For parameter is solely a property =
of the URI. Surely this is not the only instance of a DHCP option with a =
sub-option?=20

What's in the draft is not suboptions=97it's a whole special format =
requiring new code on all servers that implement it.   Suboptions don't =
exist in DHCPv6=97just encapsulations of regular options, which I don't =
think make sense here either.

> It may have been before I was paying attention, but I get the =
impression that related ground has already been trod in DHC, given that =
it also came up in GEOPRIV. =
http://www.ietf.org/mail-archive/web/geopriv/current/msg08451.html

When the topic of suboptions first came up, it was because I proposed =
them as an alternative to a complicated internal option structure with =
lots of special code required in the server to implement.   But given =
that only one Location URI option is allowed, there's no need for =
suboptions.

> I'm not sure the additional text is necessary given that there is an =
entire paragraph explaining considerations for servers in setting the =
Valid-For value. Furthermore, I don't see how "potential loss of =
service" is possible. We're talking about a URI with an expiration. When =
it expires, location recipients will no longer have access to the =
client's location, but it otherwise doesn't affect recipients' ability =
to use any "service" whatsoever.

You're right=97don't know how I missed that.

>> Section 3.2 suggests that options shouldn't contain certain =
potentially harmful values, but this is a toothless restriction, since =
an attacker can simply ignore it.   In order for it to be effective, =
Section 3.2 should insist that DHCP clients reject forbidden URI =
formats.   Of course, this too is somewhat toothless, since any list of =
forbidden URI formats will necessarily fail to mention any future =
potentially harmful URIs that could arise.   It would be better to list =
which URIs _are_ permitted, and require the client to reject any URI =
that is not permitted.   The document is already set up to do this, but =
doesn't _actually_ do it, so fixing this should be quite easy.
>=20
> In 3.3, I suggest replacing the following:
>=20
> "This section specifies which URI types are acceptable as a location
>   URI scheme (or type) for this DHCP Option:"
>=20
> with
>=20
> "URIs carried by this DHCP Option MUST have one of the following URI =
schemes:"

That's just as toothless.   Unless the client MUST reject these options, =
it MAY accept them.


From abdussalambaryun@gmail.com  Mon Jun 25 08:07:45 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5906B21F8454 for <ietf@ietfa.amsl.com>; Mon, 25 Jun 2012 08:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.59
X-Spam-Level: 
X-Spam-Status: No, score=-3.59 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, 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 aJ4E+SWzjE1F for <ietf@ietfa.amsl.com>; Mon, 25 Jun 2012 08:07:44 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id CFB8821F8452 for <ietf@ietf.org>; Mon, 25 Jun 2012 08:07:34 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2302905vcq.31 for <ietf@ietf.org>; Mon, 25 Jun 2012 08:07:34 -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=YcEBboihGL4quN4uiTvVyzKClA98pB+SvlG7gUYsPlQ=; b=jxijwTApita6yFPb5LN8yHdzGEsKxk0hS4V8pfq7PB21mCOy9J1yxvBNwxz1x/0yrk lcT+XHJQnwN1pCIn0ffpLukTKyIEIAZ8rC0w6IIwuSUL10+7uGoByl2sUstm90+7MQ1l OuyD4zA2NPpG6SOEM/lZdpKVCEQO37tvu+uBKVZxTouiY/XgcNfKz3yD9GdJDKj3yqNi ZaUhH1MZ3yKjSz5KXSGMzULAiAP5oQo0tSlzr5gpWQGOk/Z8bkGTdLnPgFQdE3icKlJC vtkS9s+Ub00X+xQZVcIn9wn17u8IhyRB3lUsGau7mopNL+jXfxtSUOW1iLPuZgKLvbgJ qlNg==
MIME-Version: 1.0
Received: by 10.220.149.15 with SMTP id r15mr8233882vcv.1.1340636854072; Mon, 25 Jun 2012 08:07:34 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Mon, 25 Jun 2012 08:07:33 -0700 (PDT)
In-Reply-To: <CADnDZ8-jwmdQ3q1UBmYSkPaZhk6dSc5tRhq5OwkzYAu=Wa1=BQ@mail.gmail.com>
References: <CADnDZ89VAZP8LSD2u090S9R3LGUJubFPmW8sCmBB2GEQWKBY4Q@mail.gmail.com> <4FE73B4A.1010904@joelhalpern.com> <CADnDZ8-jwmdQ3q1UBmYSkPaZhk6dSc5tRhq5OwkzYAu=Wa1=BQ@mail.gmail.com>
Date: Mon, 25 Jun 2012 17:07:33 +0200
Message-ID: <CADnDZ8-XqFO0Oywzkn1Mncd7cC3NqDu6_2BDKYLymcFjRFpguw@mail.gmail.com>
Subject: Re: Proposing to create an IETF WG in the general area
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: tglassey@earthlink.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jun 2012 15:07:45 -0000

Hi Tidd and All,

The General Area WGs focus on IETF processes and policies, I don't
think projects are done there,

>So then would this WG also be an incubator for projects?

The IETF-WG I propose is only to do with IETF processes and policies
(procedures, and best practices), not incubator projects,

All organisations in the world have defined Business Information
System (BIS) that organises its procedure-policy, information and
processes. In IETF we have the BIS as well, but I don't see a clear
focused group (like in other organisation) on that updates/follow-ups
on the BIS for the future. Other organisation have a management
committee for this issue of procedure-updates. Therefore, a WG for
this purpose is necessary for two things 1) The WG job is only to
follow up with policy issues and if there is a need for update 2) so
that when a memebr wants to submit a I-D for to update/replace a
policy I can submit to IETF and a focused WG.

Please advise or provide your comments,

AB
=======

From: tglassey <tglassey at earthlink.net>
To: ietf at ietf.org
Date: Sun, 24 Jun 2012 06:22:53 -0700

Gen Area groups also functioned as reception gateways for projects too
meaning that the WG Manager in this group would be a lobbyist as well
in passing new projects to other WG's once set up.
So then would this WG also be an incubator for projects?

Todd

From duerst@it.aoyama.ac.jp  Tue Jun 26 04:12:06 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F6F121F857D for <ietf@ietfa.amsl.com>; Tue, 26 Jun 2012 04:12:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.608
X-Spam-Level: 
X-Spam-Status: No, score=-99.608 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 A3UMRYMinchu for <ietf@ietfa.amsl.com>; Tue, 26 Jun 2012 04:12:05 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9774321F8568 for <ietf@ietf.org>; Tue, 26 Jun 2012 04:12:01 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5QBBoDO013850 for <ietf@ietf.org>; Tue, 26 Jun 2012 20:11:50 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 5ac2_00be_ba2e64a4_bf7f_11e1_8a73_001d096c5782; Tue, 26 Jun 2012 20:11:49 +0900
Received: from [IPv6:::1] ([133.2.210.1]:42582) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D7C9E> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 26 Jun 2012 20:11:54 +0900
Message-ID: <4FE998E9.9010809@it.aoyama.ac.jp>
Date: Tue, 26 Jun 2012 20:11:37 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> <4FE4E19F.2050400@cs.tcd.ie> <4FE83EF5.1050000@it.aoyama.ac.jp> <4FE85424.9000409@cs.tcd.ie>
In-Reply-To: <4FE85424.9000409@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Graham Klyne <GK@ninebynine.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2012 11:12:06 -0000

Hello Stephen,

On 2012/06/25 21:05, Stephen Farrell wrote:

> On 06/25/2012 11:35 AM, "Martin J. DÃ¼rst" wrote:

>> Unfortunately, what I find is the following:
>>
>>> The justification for using a URI scheme for this is that that might
>>> help a user agent for the speaker to better display the value, or
>>> perhaps if there was some use-case for a machine to speak the value.
>>
>> So we are creating a new URI scheme because *perhaps* there is a use
>> case? Or because it *might* help? In the whole discussion, I was always
>> ready to accept that there are different use cases, assuming that they
>> could be clearly explained. I'm really wondering why this is so
>> difficult. If these use cases really exist, it shouldn't be that
>> difficult, and it shouldn't sound so vague, or should it? I'm not
>> necessarily blaming you, but between you, your coauthors, and the WG
>> that apparently proposed this, it shouldn't be that hard to come up with
>> a better and more definite explanation than the sentence above.
>
> IMO the use-case is clear, and is stated in the first sentence
> of section 7.

That sentence reads:

   "Sometimes a name may need to be referred to in a format that is easy
    or unambiguous for humans to read out, for example, over the phone."

I continue to be convinced that this is not a separate use case. URIs 
are not a priori separable into those that are written down on napkins 
(or copy-pasted into emails,...) and those that are spoken over the phone.

If I send you an URI with a hash, I don't know whether you read your 
mail with your eyes (for which ni: seems appropriate) or whether you 
have a screen reader that does a text-to-speech conversion (for which 
nih: seems to be appropriate).


> I believe that Graham got the use-case, and accepted that its
> different from ni URIs, but was questioning the need for nih to
> be a uri scheme. He can confirm or refute that himself I guess,
> but quoting his mail [1] (just before the one you reference):
>
> "I can see that there are distinct use-cases here, and I
> think you have reasonable grounds for not wanting to combine
> them."
>
>     [1] http://www.ietf.org/mail-archive/web/ietf/current/msg73758.html

I think what Graham refers to as the "distinct use-cases" is identified 
in the second-to-last sentence of his mail:

     "I think you said somewhere in this exchange, nih: is intended to
      be used to confirm some information that you already have."

For all that I know about URIs, that would be consistent with Graham's 
questioning of the need for an URI scheme (because a resource is only 
confirmed, not identified). It would also be supported by the fact that 
the examples for "nih:" show only shortened hashes (which, as far as I 
understand, are okay for confirmation but not for search).

[One of my editorial comments was to streamline the examples so that the 
examples for ni: and nih: would appear with the same truncation lengths, 
in pairs. When I wrote that comment, I didn't realize that there might 
be a deeper reason for having different truncation lengths for ni: and 
nih:, mostly because that wasn't really very much explained in the draft.]

So the question is really, what's the use case, and what's just a 
consequence of that use case. If confirmation of already available 
resources (e.g. like a fingerprint) is the (main?) use case, and the 
greater weight on "speakability" just a design consequence, then it 
makes sense to have two separate things. If identification is the main 
purpose in both cases, then two separate schemes don't make sense.


> Maybe the language I added for why we want nih as a uri
> scheme is not sufficiently clear, or isn't convincing, but
> that's a different argument.

Let's for a moment concentrate on what is use case, and what are the 
design properties that follow from that. We can go back to language once 
we have made some progress on substance.


Regards,    Martin.

From stephen.farrell@cs.tcd.ie  Tue Jun 26 04:26:49 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E3DA21F860B for <ietf@ietfa.amsl.com>; Tue, 26 Jun 2012 04:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 KcjGGmmubuwy for <ietf@ietfa.amsl.com>; Tue, 26 Jun 2012 04:26:48 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 510CB21F8609 for <ietf@ietf.org>; Tue, 26 Jun 2012 04:26:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id BA83D1715B2; Tue, 26 Jun 2012 12:26:47 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1340710007; bh=Cx6KDQGAJspu5E Vk9QZe9KSjyBCzoijSRggLeKXsECg=; b=QxEqzFrXTXHBt5hWsg8sCGH1TUPPJe FFzRCFIJvN5zcaf2SlBFGywNkDWuSV3/o3GAAE6bG7jxGL9JXnXnNrCWepPb/k2H nIjL2gyC1EbEJnCLHpOzVcdtP6r+1jrO7ltClpnNhZ3wxPmLjkZl0XtQVL8DsWEq K48gFBUIiTJia53jAnUGAUA7MlxY4/aEgJLRt8sbJ2PekmqIuLLhPjXmoVfJvOIV /kUOl4hK8EghMq5CYAwqn9cJ03Ud79mNaQwEUuyOUigg6YuCjTjDP05WGMh1ajsb FFfnkAy33FD4zVvxX4IrbSJToWIm1JiBNGRItgscIA2PytiaPxzkkw+Q==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 6ysaPInghEu8; Tue, 26 Jun 2012 12:26:47 +0100 (IST)
Received: from [IPv6:2001:770:10:203:8cee:98bb:ac1:26b] (unknown [IPv6:2001:770:10:203:8cee:98bb:ac1:26b]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 9301F17151B; Tue, 26 Jun 2012 12:26:45 +0100 (IST)
Message-ID: <4FE99C75.9010309@cs.tcd.ie>
Date: Tue, 26 Jun 2012 12:26:45 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> <4FE4E19F.2050400@cs.tcd.ie> <4FE83EF5.1050000@it.aoyama.ac.jp> <4FE85424.9000409@cs.tcd.ie> <4FE998E9.9010809@it.aoyama.ac.jp>
In-Reply-To: <4FE998E9.9010809@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Graham Klyne <GK@ninebynine.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2012 11:26:49 -0000

Hi again Martin,

On 06/26/2012 12:11 PM, "Martin J. Dürst" wrote:
> So the question is really, what's the use case, and what's just a
> consequence of that use case. If confirmation of already available
> resources (e.g. like a fingerprint) is the (main?) use case, and the
> greater weight on "speakability" just a design consequence, then it
> makes sense to have two separate things.

Yes, confirmation is the main current use-case for nih as I understand
it and have said previously. (Of course the resource might not yet
be present, so "already available" isn't quite right, but that's a
nit.)

Have we beaten this to death sufficiently now? I hope so;-)

If you want to suggest a sentence that says that, feel free.

Stephen.




From hartmans@mit.edu  Tue Jun 26 12:14:51 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4B4611E809F; Tue, 26 Jun 2012 12:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.161
X-Spam-Level: 
X-Spam-Status: No, score=-104.161 tagged_above=-999 required=5 tests=[AWL=-1.896, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 03BizKd24iQn; Tue, 26 Jun 2012 12:14:51 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 5419811E809C; Tue, 26 Jun 2012 12:14:51 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id AC551202D8; Tue, 26 Jun 2012 15:14:16 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id C78ED41EF; Tue, 26 Jun 2012 15:14:35 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: ietf@ietf.org
Subject: Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-08.txt> (A GSS-API Mechanism for the Extensible Authentication Protocol) to Proposed Standard
References: <20120626165832.6142.66386.idtracker@ietfa.amsl.com>
Date: Tue, 26 Jun 2012 15:14:35 -0400
In-Reply-To: <20120626165832.6142.66386.idtracker@ietfa.amsl.com> (The IESG's message of "Tue, 26 Jun 2012 09:58:32 -0700")
Message-ID: <tslk3yt6g2s.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: abfab@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2012 19:14:52 -0000

EAP (RFC 3748) has a applicability statement  scoped very strictly to
network access.
This document  provides a mechanism that falls well outside that
applicability statement and permits the use of EAP for general
application authentication.

When ABFAB was chartered, there was a charter item to update the EAP
applicability statement. I think A number of people in the room at the
BOF, including myself, would have objected to the work being chartered
had that charter item not been present.

I think that work is important because I believe there are a number of
important concerns that apply to the use of EAP for authentication
beyond network access that need to be documented.

Unfortunately, the technical specification has gotten ahead of the
applicability statement update.
I'm OK with that provided that we're still firmly committed to an
applicability statement update. As part of approving this document now,
I want to confirm that we have consensus at least within the ABFAB
working group and the IESG to do that update.
If there is any doubt I'd far prefer that this document be held until
the applicability statement catches up.

--Sam

From sm@resistor.net  Tue Jun 26 13:15:29 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6540811E80CD for <ietf@ietfa.amsl.com>; Tue, 26 Jun 2012 13:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 FiqoHvqNzR49 for <ietf@ietfa.amsl.com>; Tue, 26 Jun 2012 13:15:25 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D3AC111E809C for <ietf@ietf.org>; Tue, 26 Jun 2012 13:15:25 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5QKFFF8008857; Tue, 26 Jun 2012 13:15:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1340741720; bh=xxPscKJjJYouwL8X1j0oBd1DdyyIN073JnEBovjLOq8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JoyOJReXGMgOne87Bf4CdrF7GUhMQaHnBTdJWGlmFni1abI3aNa2d7VCX8opUk32/ MZKj1JCkWO+qVuESgrA677S5Rztotk1zfHVVmK6o2ne2q9PtkTt9sN8ZiN55tcMfxQ Zd5jxegoDSpEMD50+SFG80lsMFZaEyZOZPFEVFRk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1340741720; i=@resistor.net; bh=xxPscKJjJYouwL8X1j0oBd1DdyyIN073JnEBovjLOq8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aBDmxE22HRM1qO7uf9CLQDQ0xl8H1iTbjIEsETOwC2GORO4cWI+JjuRtNS/fvoyUy AMGdt5wpziiV8w6dJGObZtbklWN8kz/j9nyOoPYzG0vqkUSare3li6XP97vausyQfX pFIUnoTNQFvS/rzvGIJBRGZVbE7pDNXvJ/gXHiLo=
Message-Id: <6.2.5.6.2.20120626121535.09fac360@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 26 Jun 2012 13:06:11 -0700
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
In-Reply-To: <4FE4E19F.2050400@cs.tcd.ie>
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> <4FE4E19F.2050400@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2012 20:15:29 -0000

Hi Stephen,
At 14:20 22-06-2012, Stephen Farrell wrote:
>The issues raised but not so far obviously resolved on the
>list were I think:
>
>1) inclusion of content type
>2) nih as a URI scheme or not

[snip]

>For (2) we've left nih in as a URI scheme in this version.
>We're still in favour of keeping it that way and have added
>some language about why its there and is done like that. I'm
>guessing that Martin at least won't be happy (but who knows;-),
>so again comments are welcome as to whether the new text helps
>or not. But in the end we'll go with Barry's consensus call
>on this if he judges that we're in the rough, rather than the
>folks who've commented on this topic. In that case I'll put
>out a version with no nih scheme and the "human speakable"
>format as just a textual convention (with a check-digit,
>which'd be plain odd IMO, the uri scheme is the right idea
>really:-)

I read Section 7 of draft-farrell-decade-ni-08.  The justification 
for a nih URI scheme elicits a smile.  The idea is futuristic. :-)  I 
suggest having a version without the nih scheme.

Regards,
-sm 


From hartmans@mit.edu  Wed Jun 27 12:00:51 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8C1511E8171; Wed, 27 Jun 2012 12:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.038
X-Spam-Level: 
X-Spam-Status: No, score=-104.038 tagged_above=-999 required=5 tests=[AWL=-1.773, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 eJ3U5sLdRJ3s; Wed, 27 Jun 2012 12:00:51 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id A23A211E8172; Wed, 27 Jun 2012 12:00:48 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id DE31A201CC; Wed, 27 Jun 2012 15:00:10 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 9A05A41EF; Wed, 27 Jun 2012 15:00:29 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "t.p." <daedulus@btconnect.com>
Subject: Re: [secdir] secdir review of draft-sakane-dhc-dhcpv6-kdc-option
References: <21762_1337814743_q4NNCMPh008981_alpine.BSF.2.00.1205231837020.9762@fledge.watson.org> <1337881837.3279.45.camel@destiny.pc.cs.cmu.edu> <004a01cd4562$b7b338e0$4001a8c0@gateway.2wire.net>
Date: Wed, 27 Jun 2012 15:00:29 -0400
In-Reply-To: <004a01cd4562$b7b338e0$4001a8c0@gateway.2wire.net> (t. p.'s message of "Fri, 8 Jun 2012 11:37:27 +0100")
Message-ID: <tsl7gus37hu.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: , draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org, ietf <ietf@ietf.org>, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2012 19:00:52 -0000

>>>>> "t" == t p <daedulus@btconnect.com> writes:

    t> Just to make public what I have hinted at privately, I think that steps
    t> in section 4.1 may be somewhat underspecified.

    t> A related issue is that section 4.1 prefers DNS to DHCP for Kerberos
    t> information but the Security Considerations stress the weakness of
    t> DHCP and recommend authenticating DHCP.  What if DHCP is secure
    t> and DNS is not?  Should DNS still be preferred?

Yes probably.
DNS has been and will continue to be the dominant way to discover KDCs.
I see this as a specialized DHCP option for certain deployments, not
something you'll see in the enterprise for desktops or laptops as an
example.
I mean some people may deploy it, but I suspect that you won't see it in
most situations where DNS works well today.
So, basically in all cases, including preconfigured DNS servers, I'd
expect DNS to be preferred.

Note that choosing the right KDC does impact availability--if you have
the wrong KDC it won't work.
In general though, choosing the wrong KDC does not compromise
authentication. It's a bit more complex than that, but KDC location has
not generally been considered  security sensitive.

From sm@elandsys.com  Wed Jun 27 02:54:17 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECEA21F85F2 for <ietf@ietfa.amsl.com>; Wed, 27 Jun 2012 02:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 LT7MF-FZx+My for <ietf@ietfa.amsl.com>; Wed, 27 Jun 2012 02:54:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D540121F85EA for <ietf@ietf.org>; Wed, 27 Jun 2012 02:54:06 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.239.8]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5R9rno1002552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jun 2012 02:53:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1340790841; bh=Szh9IMwMRK6i/aj2difdUaVVBLK9v8cQ0MDlldCsgVU=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=VXOo4gn+AzLyiy2ttZ+CWuFhwN2+ZPE8K5wmfy+zMWgEmoqLXjy/lGBLz0J3BQWvr rRngYhFeGUmiNYiSfTBP4Vz/hqp1gzeHSuPVj0gEWu6/GrO1PpX/rY8yETBAD0OmWl FDRRVYxEGHn8G5h8glz+wMein4eNzmXum15UjpEI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1340790841; i=@elandsys.com; bh=Szh9IMwMRK6i/aj2difdUaVVBLK9v8cQ0MDlldCsgVU=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=DxvFjsnVPIYK2D08ju2ruAvz5huGc2j3biFO0J67vkSMZskQBbbg2ad3g+MpTnEGD ys5vcsoTDtJNoLXmvall18fHL+DtB4Zi/pG/Oy4wFlRkk5ZNePuITeYR8ZKRVzzLvJ QsEhaEJ+MQKfSCsf60Vtn4QWkivBDYSdgHziOa2M=
Message-Id: <6.2.5.6.2.20120627020651.0ae005b0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 27 Jun 2012 02:51:17 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: getting pre-5378 signover?
In-Reply-To: <20120606133434.GA5859@crankycanuck.ca>
References: <20120606133434.GA5859@crankycanuck.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Wed, 27 Jun 2012 12:28:58 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2012 09:54:17 -0000

Hello,

A message requesting guidance about getting pre-5378 signover was 
sent to trustees@ietf.org on June 6.  There hasn't been any response 
from the IETF Trust.

Regards,
S. Moonesamy


From randy@psg.com  Wed Jun 27 13:53:41 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 461FE21F86B5; Wed, 27 Jun 2012 13:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level: 
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599]
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 UzORTusXpG+l; Wed, 27 Jun 2012 13:53:40 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id C096321F86B1; Wed, 27 Jun 2012 13:53:40 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SjzF5-00074c-Ly; Wed, 27 Jun 2012 20:53:40 +0000
Date: Wed, 27 Jun 2012 10:53:38 -1000
Message-ID: <m2r4t0jx2l.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: The IESG <iesg-secretary@ietf.org>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6204bis-09.txt> (Basic	Requirements for	IPv6 Customer Edge Routers) to Informational RFC
In-Reply-To: <20120627174957.18647.15377.idtracker@ietfa.amsl.com>
References: <20120627174957.18647.15377.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF v6ops list <v6ops@ietf.org>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2012 20:53:41 -0000

> - 'Basic Requirements for IPv6 Customer Edge Routers'
>   <draft-ietf-v6ops-6204bis-09.txt> as Informational RFC

this document persists in confusing routing and forwarding.

there are no routing protocols, a la 1812, here.  there is confused text
such as

4.1.  General Requirements

   The IPv6 CE router is responsible for implementing IPv6 routing; that
   is, the IPv6 CE router must look up the IPv6 destination address in
   its routing table to decide to which interface it should send the
   packet.

which i thought was forwarding, not routing.

RA/RD doeth not a router make.

randy

From acooper@cdt.org  Wed Jun 27 14:27:43 2012
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 692C121F8661; Wed, 27 Jun 2012 14:27:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.262
X-Spam-Level: 
X-Spam-Status: No, score=-102.262 tagged_above=-999 required=5 tests=[AWL=0.337, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 cvNjXYsCfwSC; Wed, 27 Jun 2012 14:27:42 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 2E38121F865D; Wed, 27 Jun 2012 14:27:42 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Wed, 27 Jun 2012 17:27:39 -0400
Subject: Re: [dhcwg] Last Call:	<draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt> (Dynamic	Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a	Location Uniform Resource Identifier (URI)) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <33AFBD35-FDCA-4424-9EB1-1903976085B0@fugue.com>
Date: Wed, 27 Jun 2012 17:27:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C9D555E-C18A-47D3-BB6A-B822B7957ABE@cdt.org>
References: <20120531184851.30358.8816.idtracker@ietfa.amsl.com> <ADE21D06-F6A4-4018-A999-6B50EC94F3C7@fugue.com> <3AE0A5BB-E5B7-46A3-A3D6-3F7C8FB84016@cdt.org> <33AFBD35-FDCA-4424-9EB1-1903976085B0@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Cc: GEOPRIV WG <geopriv@ietf.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2012 21:27:43 -0000

Hi Ted,

On Jun 22, 2012, at 4:11 PM, Ted Lemon wrote:

> On Jun 22, 2012, at 3:59 PM, Alissa Cooper wrote:
>> My understanding is that the option is encoded this way both for =
extensibility and because the Valid-For parameter is solely a property =
of the URI. Surely this is not the only instance of a DHCP option with a =
sub-option?=20
>=20
> What's in the draft is not suboptions=97it's a whole special format =
requiring new code on all servers that implement it.   Suboptions don't =
exist in DHCPv6=97just encapsulations of regular options, which I don't =
think make sense here either.
>=20
>> It may have been before I was paying attention, but I get the =
impression that related ground has already been trod in DHC, given that =
it also came up in GEOPRIV. =
http://www.ietf.org/mail-archive/web/geopriv/current/msg08451.html
>=20
> When the topic of suboptions first came up, it was because I proposed =
them as an alternative to a complicated internal option structure with =
lots of special code required in the server to implement.   But given =
that only one Location URI option is allowed, there's no need for =
suboptions.


If we split it into two options, that eliminates the future possibility =
of supporting multiple URIs per client. So we will need to take this =
back to the GEOPRIV WG to make sure folks are okay with foreclosing =
that.


>=20
>=20
>>> Section 3.2 suggests that options shouldn't contain certain =
potentially harmful values, but this is a toothless restriction, since =
an attacker can simply ignore it.   In order for it to be effective, =
Section 3.2 should insist that DHCP clients reject forbidden URI =
formats.   Of course, this too is somewhat toothless, since any list of =
forbidden URI formats will necessarily fail to mention any future =
potentially harmful URIs that could arise.   It would be better to list =
which URIs _are_ permitted, and require the client to reject any URI =
that is not permitted.   The document is already set up to do this, but =
doesn't _actually_ do it, so fixing this should be quite easy.
>>=20
>> In 3.3, I suggest replacing the following:
>>=20
>> "This section specifies which URI types are acceptable as a location
>>  URI scheme (or type) for this DHCP Option:"
>>=20
>> with
>>=20
>> "URIs carried by this DHCP Option MUST have one of the following URI =
schemes:"
>=20
> That's just as toothless.   Unless the client MUST reject these =
options, it MAY accept them.

Okay, will add MUST reject language.

Alissa



From marka@isc.org  Wed Jun 27 17:31:14 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E1F11E8134; Wed, 27 Jun 2012 17:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.766
X-Spam-Level: 
X-Spam-Status: No, score=-1.766 tagged_above=-999 required=5 tests=[AWL=0.233,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 O66l0iSB4-To; Wed, 27 Jun 2012 17:31:13 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 544AD11E8133; Wed, 27 Jun 2012 17:31:10 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 71B2A5F99B2; Thu, 28 Jun 2012 00:30:55 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:7471:6721:a784:9471]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 78635216C33; Thu, 28 Jun 2012 00:30:53 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 49AF52208913; Thu, 28 Jun 2012 10:30:51 +1000 (EST)
To: Randy Bush <randy@psg.com>
From: Mark Andrews <marka@isc.org>
References: <20120627174957.18647.15377.idtracker@ietfa.amsl.com> <m2r4t0jx2l.wl%randy@psg.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6204bis-09.txt> (Basic Requirements for IPv6 Customer Edge Routers) to Informational RFC
In-reply-to: Your message of "Wed, 27 Jun 2012 10:53:38 -1000." <m2r4t0jx2l.wl%randy@psg.com>
Date: Thu, 28 Jun 2012 10:30:51 +1000
Message-Id: <20120628003051.49AF52208913@drugs.dv.isc.org>
Cc: IETF v6ops list <v6ops@ietf.org>, The IESG <iesg-secretary@ietf.org>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 00:31:14 -0000

In message <m2r4t0jx2l.wl%randy@psg.com>, Randy Bush writes:
> > - 'Basic Requirements for IPv6 Customer Edge Routers'
> >   <draft-ietf-v6ops-6204bis-09.txt> as Informational RFC
> 
> this document persists in confusing routing and forwarding.
> 
> there are no routing protocols, a la 1812, here.  there is confused text
> such as
> 
> 4.1.  General Requirements
> 
>    The IPv6 CE router is responsible for implementing IPv6 routing; that
>    is, the IPv6 CE router must look up the IPv6 destination address in
>    its routing table to decide to which interface it should send the
>    packet.
> 
> which i thought was forwarding, not routing.

It's static routing.  And if there is down stream PD there will be
next hop routers as well as interfaces in the table.

> RA/RD doeth not a router make.
> 
> randy
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From ron.even.tlv@gmail.com  Thu Jun 28 07:28:52 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0A1221F84F8; Thu, 28 Jun 2012 07:28:52 -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=[AWL=-0.000, 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 oMgnGTDe4hAf; Thu, 28 Jun 2012 07:28:51 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 405A621F84F6; Thu, 28 Jun 2012 07:28:51 -0700 (PDT)
Received: by bkty8 with SMTP id y8so2230979bkt.31 for <multiple recipients>; Thu, 28 Jun 2012 07:28:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=DA5MEXEu0DpBbcPJiet+yV+uluj4H3or/q+v3N+rorg=; b=sW6OyIQgN3y5A/WX0P/rG6dFtVyIu42jUky6kloUlPky7J/aRN18zUWOL4JXlUeBg/ k7uditZEPF8vrHDR1yj0VNJ3pETDWCWdQfbUDGP8EcmYObipVvSBKKeuRaFsWeK+A3FF Srs492IVpAZqXkOMwrgoZ2UlMI2mJgy3Ixjf/zcXvdoPFP8OlgBTJrD0uxe9mkk5gfF4 2GIp2RkAIw+E28wYeVR0piqbMG/bkCWdRa7nYwszTe6g3p98Mfar0bVMPnj2SZvI9utz bTelcWz8KiqZ5X4pYhdBFg5CEmXPZMUklsYUwkKDvFiKmnCi2tGUPi9h7NCxn0zGpVC0 tg3g==
Received: by 10.204.132.80 with SMTP id a16mr1384739bkt.82.1340893730281; Thu, 28 Jun 2012 07:28:50 -0700 (PDT)
Received: from RoniE ([109.64.198.75]) by mx.google.com with ESMTPS id iq16sm59240722bkc.6.2012.06.28.07.28.48 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Jun 2012 07:28:49 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-hoffman-tao-as-web-page.all@tools.ietf.org>, <ietf@ietf.org>, <gen-art@ietf.org>
Subject: GenART LC review of draft-hoffman-tao-as-web-page-02
Date: Thu, 28 Jun 2012 17:28:29 +0200
Message-ID: <00b701cd5542$acb50780$061f1680$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B8_01CD5553.703EC1E0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1VQqs+3AMkTzdBSOCThHrnWYVdSA==
Content-Language: en-us
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 14:28:53 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00B8_01CD5553.703EC1E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-hoffman-tao-as-web-page-02

Reviewer: Roni Even

Review Date:2012-6-28

IETF LC End Date: 2012-7-13

IESG Telechat date:

 

Summary: This draft is ready for publication as an Informational RFC.

 

Major issues:

 

Minor issues:

In the section 2 the second sentence is "The initial content for the Tao web
page will come from the last Internet-Draft that was meant to replace RFC
4677.". I was wondering if this information is important to this document
when published. If it is maybe rephrase it to "The initial content for the
Tao web page is based on the last Internet-Draft that was meant to replace
RFC 4677". 

I also suggest that maybe it will be good to have an informative reference
to it.

 

 

Nits/editorial comments:

 

1.       Section 1 second paragraph "led" instead of "lead" 

2.       Section 2 third paragraph "proposed" instead of "propsed"

 


------=_NextPart_000_00B8_01CD5553.703EC1E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1239562432;
	mso-list-type:hybrid;
	mso-list-template-ids:1795562620 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
draft-hoffman-tao-as-web-page-02<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;6&#8211;28<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;7&#8211;13<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In the =
section 2 the second sentence is &#8220;The initial content for the Tao =
web page will come from the last Internet-Draft that was meant to =
replace RFC 4677.&#8221;. I was wondering if this information is =
important to this document when published. If it is maybe rephrase it to =
&#8220;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The =
initial content for the Tao web page is based on the last Internet-Draft =
that was meant to replace RFC 4677&#8221;. <o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I also =
suggest that maybe it will be good to have an informative reference to =
it.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section 1 =
second paragraph &#8220;led&#8221; instead of &#8220;lead&#8221; =
<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section 2 =
third paragraph &#8220;proposed&#8221; instead of =
&#8220;propsed&#8221;<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00B8_01CD5553.703EC1E0--


From tnadeau@lucidvision.com  Thu Jun 28 11:23:35 2012
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38F9621F851C for <ietf@ietfa.amsl.com>; Thu, 28 Jun 2012 11:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 f4Ya-A2+iK4X for <ietf@ietfa.amsl.com>; Thu, 28 Jun 2012 11:23:33 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 5CBDC21F8512 for <ietf@ietf.org>; Thu, 28 Jun 2012 11:23:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by lucidvision.com (Postfix) with ESMTP id CA0A2218A827 for <ietf@ietf.org>; Thu, 28 Jun 2012 14:23:31 -0400 (EDT)
X-Virus-Scanned: amavisd-new at www.lucidvision.com
Received: from lucidvision.com ([127.0.0.1]) by localhost (static-72-71-250-34.cncdnh.fios.verizon.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SxWr-imZ4l0L for <ietf@ietf.org>; Thu, 28 Jun 2012 14:23:31 -0400 (EDT)
Received: from sa-nc-mfg-98.static.jnpr.net (natint3.juniper.net [66.129.224.36]) by lucidvision.com (Postfix) with ESMTP id D041E218A81B for <ietf@ietf.org>; Thu, 28 Jun 2012 14:23:30 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: bits-n-bites: Exhibitors and product vendors hawking wares at an IETF meeting?
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <8F4E6FDD-33F9-4383-9DB0-9F6B17D9A5D9@vpnc.org>
Date: Thu, 28 Jun 2012 14:23:29 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <199FFAA6-FEC9-4454-901A-7DDFE78ED72A@lucidvision.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <8F4E6FDD-33F9-4383-9DB0-9F6B17D9A5D9@vpnc.org>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 18:23:35 -0000

	Has the IETF morphed into a conference/convention?

http://www.ietf.org/meeting/84/bits-n-bites.html



From housley@vigilsec.com  Thu Jun 28 11:40:37 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91A8221F85D8 for <ietf@ietfa.amsl.com>; Thu, 28 Jun 2012 11:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 b1aw8zMndC+j for <ietf@ietfa.amsl.com>; Thu, 28 Jun 2012 11:40:37 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id E304821F85D2 for <ietf@ietf.org>; Thu, 28 Jun 2012 11:40:36 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 5D563F2403B; Thu, 28 Jun 2012 14:40:46 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id TKrqRVkSUGex; Thu, 28 Jun 2012 14:40:30 -0400 (EDT)
Received: from [192.168.2.100] (pool-108-28-60-116.washdc.fios.verizon.net [108.28.60.116]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 6399EF2403A; Thu, 28 Jun 2012 14:40:45 -0400 (EDT)
Subject: Re: bits-n-bites: Exhibitors and product vendors hawking wares at an IETF meeting?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <199FFAA6-FEC9-4454-901A-7DDFE78ED72A@lucidvision.com>
Date: Thu, 28 Jun 2012 14:40:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BEB839C7-3189-4F40-9EBD-D414E0E378F7@vigilsec.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <8F4E6FDD-33F9-4383-9DB0-9F6B17D9A5D9@vpnc.org> <199FFAA6-FEC9-4454-901A-7DDFE78ED72A@lucidvision.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 18:40:37 -0000

There was a long discussion about this event prior to it being =
scheduled.  Sorry you missed that discussion.

We will have a discussion after the event to determine if we should do =
it again.

Russ


On Jun 28, 2012, at 2:23 PM, Thomas Nadeau wrote:

>=20
> 	Has the IETF morphed into a conference/convention?
>=20
> http://www.ietf.org/meeting/84/bits-n-bites.html
>=20
>=20


From david.black@emc.com  Thu Jun 28 13:51:44 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCC5421F8526; Thu, 28 Jun 2012 13:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 vg1LkAWUb-E4; Thu, 28 Jun 2012 13:51:42 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 47F6A21F8593; Thu, 28 Jun 2012 13:51:41 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5SKpcOB030462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jun 2012 16:51:39 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 28 Jun 2012 16:51:16 -0400
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5SKpEHi013407; Thu, 28 Jun 2012 16:51:14 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub26.corp.emc.com ([10.254.110.182]) with mapi; Thu, 28 Jun 2012 16:51:14 -0400
From: <david.black@emc.com>
To: <alan.b.johnston@gmail.com>, <mohsen.soroush@sylantro.com>, <vvenkatar@gmail.com>, <gen-art@ietf.org>
Date: Thu, 28 Jun 2012 16:51:13 -0400
Subject: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Index: Ac1Vb8Dn5IHpqMlJQDmiZm9plrtFJQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 28 Jun 2012 14:45:17 -0700
Cc: bliss@ietf.org, david.black@emc.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 20:51:45 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-bliss-shared-appearances-11
Reviewer: David L. Black
Review Date: June 28, 2012
IETF LC End Date: June 28, 2012
IESG Telechat date: (if known)

Summary:

This draft is on the right track but has open issues, described in the revi=
ew.

This draft describes support for shared appearances in support of multi-lin=
e
and shared-line telephone often found in businesses.  All of the open issue=
s
are minor.  The draft is well-written and reasonably clear for the most par=
t,
although significant SIP expertise is required to completely understand it.

Major issues:  None.

Minor issues:

4.1 - REQ-16:

   in this case, seizing the line is the same thing as dialing.

That seems wrong - I would have thought it was a "prerequisite" as
opposed to "the same thing" because seizing the line is immediately
followed by a dialing request.

5.3.

   A user may select an appearance number but then abandon placing a
   call (go back on hook).  In this case, the UA MUST free up the
   appearance number by removing the event state with a PUBLISH as
   described in [RFC3903].

What happens when that can't be done due to UA or network failure?

5.4.

   A 400 response is returned if the chosen appearance number is invalid,

Is that always a 400 (Bad Request) or is any 4xx response allowed?  If
it's always 400, add the words "Bad Request" after "400".

   If the Appearance Agent policy does not allow this, a 400 response
   is returned.

Same question.  In addition, is 403 Forbidden allowed here?

   If an INVITE is sent by a member of the group to the shared AOR (i.e.
   they call their own AOR), the Appearance Agent MUST assign two
   appearance numbers.  The first appearance number will be the one
   selected or assigned to the outgoing INVITE.  The second appearance
   number will be another one assigned by the Appearance Agent for the
   INVITE as it is forked back to the members of the group.

How does that interact with the single appearance UAs in 8.1.1 that won't
understand the second appearance number?  A warning that such a UA can't
pick up its call to its own AOR would suffice, either here or in 8.1.1.

9.1=20

   A UA that has no knowledge of appearances must will only have
   appearance numbers for outgoing calls if assigned by the Appearance
   Agent.  If the non-shared appearance UA does not support Join or
   Replaces, all dialogs could be marked "exclusive" to indicate that
   these options are not available.

Should that "could be marked" be changed to "SHOULD be marked" ?
Also, analogous questions for "could" in 9.2 and "can" in 9.3.

All three of these affect interoperability.

12. Security Considerations

In general, this section is weak on rationale - the second, third and
fourth paragraphs should all explain more about the purpose of and/or
rationale for their security requirements (e.g., what does the security
mechanism protect against and when/why might that protection be desired
and/or required?).

   NOTIFY or PUBLISH message bodies that provide the dialog state
   information and the dialog identifiers MAY be encrypted end-to-end
   using the standard mechanisms.

What are "the standard mechanisms"?  List them, and provide references,
please.

Please ensure that the section 6 XML and Section 7 ABNF are
syntax-checked with actual tools.

Nits/editorial comments:

p.10:

   The next section discusses the operations used to implement parts of
   the shared appearance feature.

"The following list describes the operations ..." would be better.

5.3.1.

   A UA wanting to place a call but not have an appearance number
   assigned publishes before sending the INVITE without an 'appearance'
   element but with the 'shared' event package parameter present.

I think I understand what was intended here, but this would be clearer
if "publishes" was replaced with language about sending a PUBLISH.
It's also not completely clear whether "without" applies to the
INVITE or the PUBLISH, so this sentence probably needs to be reworded.

5.4. - Expand B2BUA acronym on first use.

idnits 2.12.13 ran clean.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From mellon@fugue.com  Wed Jun 27 15:02:20 2012
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F60B21F861D; Wed, 27 Jun 2012 15:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 YtKpY4l9p5jS; Wed, 27 Jun 2012 15:02:19 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 46B8F21F861C; Wed, 27 Jun 2012 15:02:19 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by toccata.fugue.com (Postfix) with ESMTPSA id 5B5092381615; Wed, 27 Jun 2012 18:02:16 -0400 (EDT)
Subject: Re: [dhcwg] Last Call:	<draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt> (Dynamic	Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a	Location Uniform Resource Identifier (URI)) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_687B87F2-BB1D-4C83-AB94-CE46AF5A00F2"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <2C9D555E-C18A-47D3-BB6A-B822B7957ABE@cdt.org>
Date: Thu, 28 Jun 2012 00:02:14 +0200
Message-Id: <829DAD0D-D6CC-4BDB-A5D9-0B36FE7379BD@fugue.com>
References: <20120531184851.30358.8816.idtracker@ietfa.amsl.com> <ADE21D06-F6A4-4018-A999-6B50EC94F3C7@fugue.com> <3AE0A5BB-E5B7-46A3-A3D6-3F7C8FB84016@cdt.org> <33AFBD35-FDCA-4424-9EB1-1903976085B0@fugue.com> <2C9D555E-C18A-47D3-BB6A-B822B7957ABE@cdt.org>
To: Alissa Cooper <acooper@cdt.org>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Thu, 28 Jun 2012 14:45:25 -0700
Cc: GEOPRIV WG <geopriv@ietf.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2012 22:02:20 -0000

--Apple-Mail=_687B87F2-BB1D-4C83-AB94-CE46AF5A00F2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On Jun 27, 2012, at 11:27 PM, Alissa Cooper wrote:
> If we split it into two options, that eliminates the future =
possibility of supporting multiple URIs per client. So we will need to =
take this back to the GEOPRIV WG to make sure folks are okay with =
foreclosing that.

The document already says that multiple URIs aren't valid, doesn't it?


--Apple-Mail=_687B87F2-BB1D-4C83-AB94-CE46AF5A00F2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 27, 2012, at 11:27 PM, Alissa Cooper =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">If we split =
it into two options, that eliminates the future possibility of =
supporting multiple URIs per client. So we will need to take this back =
to the GEOPRIV WG to make sure folks are okay with foreclosing =
that.<br></span></blockquote></div><br><div>The document already says =
that multiple URIs aren't valid, doesn't =
it?</div><div><br></div></body></html>=

--Apple-Mail=_687B87F2-BB1D-4C83-AB94-CE46AF5A00F2--

From alan.b.johnston@gmail.com  Thu Jun 28 18:05:29 2012
Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0575F11E80FA; Thu, 28 Jun 2012 18:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 kKLshi9zm47k; Thu, 28 Jun 2012 18:05:28 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id B5D1911E80A2; Thu, 28 Jun 2012 18:05:27 -0700 (PDT)
Received: by yenq13 with SMTP id q13so2595199yen.31 for <multiple recipients>; Thu, 28 Jun 2012 18:05:27 -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:content-transfer-encoding; bh=UKpmvQQl3KGBpTU+DKE/cWv4M90OECLV/6XPcxRaL1c=; b=E38N3onfj44+nigxSdK83N5XPWeq7LzXqseQFUvQqRV3GkxRBRTJLJYP4iB464muEB in7FIuOHip+PfogC81slJRE9TY6nNmfiiu2du5W57RsET6aSVyzWqn2ZY1bvA7xcy3EV YzzRn4V3AQQ7MzXeea7/kjK4EY0rvRgGB74qZRcFPBk8XC3XbQyTOrMjBqE4xf+dHMIj 9iMrwBqYUwpMRINa/KyXw7SVynnFzGnsMxWdjQzOKu3C9ykjGkaF9+pH8/PHtSVZ7pd8 xOnD4U80B2ownVoT3l/JLkKMJ2Xh0opHhkrxG6jUPDFnDXey5Q0K5PXUb28HH8MUHpbV Ru3Q==
MIME-Version: 1.0
Received: by 10.42.130.68 with SMTP id u4mr1429708ics.17.1340931925588; Thu, 28 Jun 2012 18:05:25 -0700 (PDT)
Received: by 10.231.228.135 with HTTP; Thu, 28 Jun 2012 18:05:25 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com>
Date: Thu, 28 Jun 2012 20:05:25 -0500
Message-ID: <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
From: Alan Johnston <alan.b.johnston@gmail.com>
To: david.black@emc.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mohsen.soroush@sylantro.com, ietf@ietf.org, gen-art@ietf.org, bliss@ietf.org, vvenkatar@gmail.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 01:05:29 -0000

David,

Thank you for your review of the document. =A0See below for how I
propose to resolve the issues you have raised.  Let me know if you
have any other issues or concerns.

- Alan -

On Thu, Jun 28, 2012 at 3:51 PM, <david.black@emc.com> wrote:
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-bliss-shared-appearances-11
> Reviewer: David L. Black
> Review Date: June 28, 2012
> IETF LC End Date: June 28, 2012
> IESG Telechat date: (if known)
>
> Summary:
>
> This draft is on the right track but has open issues, described in the re=
view.
>
> This draft describes support for shared appearances in support of multi-l=
ine
> and shared-line telephone often found in businesses. =A0All of the open i=
ssues
> are minor. =A0The draft is well-written and reasonably clear for the most=
 part,
> although significant SIP expertise is required to completely understand i=
t.
>
> Major issues: =A0None.
>
> Minor issues:
>
> 4.1 - REQ-16:
>
> =A0 in this case, seizing the line is the same thing as dialing.
>
> That seems wrong - I would have thought it was a "prerequisite" as
> opposed to "the same thing" because seizing the line is immediately
> followed by a dialing request.


This requirement is about sending one request that causes both actions
to occur. =A0In a PSTN ringdown circuit (a very specialized circuit,
used for "hotlines"), the two operations are the same thing. =A0Besides
this statement, is REQ-16 itself not clear? =A0Perhaps I should just
remove this statement if it adds confusion rather than clarity to the
requirement.

>
>
> 5.3.
>
> =A0 A user may select an appearance number but then abandon placing a
> =A0 call (go back on hook). =A0In this case, the UA MUST free up the
> =A0 appearance number by removing the event state with a PUBLISH as
> =A0 described in [RFC3903].
>
> What happens when that can't be done due to UA or network failure?


A little further down in this section says:

"=A0 This publication state is refreshed as described in [RFC3903] during
=A0 =A0the early dialog state or the Appearance Agent may reassign the
=A0 =A0appearance number."

So if the removal publish is lost, it will eventually timeout since it
is not refreshed.  This is standard PUBLISH behavior described in RFC
3903.

>
>
> 5.4.
>
> =A0 A 400 response is returned if the chosen appearance number is invalid=
,
>
> Is that always a 400 (Bad Request) or is any 4xx response allowed? =A0If
> it's always 400, add the words "Bad Request" after "400".

We chose 400 in particular, although any 4xx response would have the
same result.  "Bad Request" is the reason phrase, and the practice of
putting it in () is a convention commonly used in SIP documents.  The
actual reason phrase can be different, customized ("Invalid
Appearance") if desired, or in a different language.

So in this case we are specifying the 400 response.

>
> =A0 If the Appearance Agent policy does not allow this, a 400 response
> =A0 is returned.
>
> Same question. =A0In addition, is 403 Forbidden allowed here?

403 is usually used in SIP to indicate that the request has failed due
to an authorization policy, and the request can be retried with
different credentials.  That doesn't quite fit here.

>
> =A0 If an INVITE is sent by a member of the group to the shared AOR (i.e.
> =A0 they call their own AOR), the Appearance Agent MUST assign two
> =A0 appearance numbers. =A0The first appearance number will be the one
> =A0 selected or assigned to the outgoing INVITE. =A0The second appearance
> =A0 number will be another one assigned by the Appearance Agent for the
> =A0 INVITE as it is forked back to the members of the group.
>
> How does that interact with the single appearance UAs in 8.1.1 that won't
> understand the second appearance number? =A0A warning that such a UA can'=
t
> pick up its call to its own AOR would suffice, either here or in 8.1.1.

I will put text in 8.1.1 that makes this point clear.

>
> 9.1
>
> =A0 A UA that has no knowledge of appearances must will only have
> =A0 appearance numbers for outgoing calls if assigned by the Appearance
> =A0 Agent. =A0If the non-shared appearance UA does not support Join or
> =A0 Replaces, all dialogs could be marked "exclusive" to indicate that
> =A0 these options are not available.
>
> Should that "could be marked" be changed to "SHOULD be marked" ?
> Also, analogous questions for "could" in 9.2 and "can" in 9.3.
>
> All three of these affect interoperability.

I can change this to SHOULD.  Actually, it doesn't affect
interoperability, as "exclusive" is just a hint, for user experience
and interface purposes and to reduce failed requests.  If a Join or
Replace is inadvertently sent, the operation will fail, which is the
same result as not allowing it, although a worse user experience.

>
> 12. Security Considerations
>
> In general, this section is weak on rationale - the second, third and
> fourth paragraphs should all explain more about the purpose of and/or
> rationale for their security requirements (e.g., what does the security
> mechanism protect against and when/why might that protection be desired
> and/or required?).

Right, the mechanisms are to provide privacy and to prevent
hijacking/spoofing.  I can add text to make this clear.

>
> =A0 NOTIFY or PUBLISH message bodies that provide the dialog state
> =A0 information and the dialog identifiers MAY be encrypted end-to-end
> =A0 using the standard mechanisms.
>
> What are "the standard mechanisms"? =A0List them, and provide references,
> please.

That would be S/MIME as described in RFC 3261.  I can add this.

>
> Please ensure that the section 6 XML and Section 7 ABNF are
> syntax-checked with actual tools.

I will double check them.

>
> Nits/editorial comments:
>
> p.10:
>
> =A0 The next section discusses the operations used to implement parts of
> =A0 the shared appearance feature.
>
> "The following list describes the operations ..." would be better.
>
> 5.3.1.
>
> =A0 A UA wanting to place a call but not have an appearance number
> =A0 assigned publishes before sending the INVITE without an 'appearance'
> =A0 element but with the 'shared' event package parameter present.
>
> I think I understand what was intended here, but this would be clearer
> if "publishes" was replaced with language about sending a PUBLISH.
> It's also not completely clear whether "without" applies to the
> INVITE or the PUBLISH, so this sentence probably needs to be reworded.

OK, it is the PUBLISH that doesn't have the parameter - I'll make this clea=
r.

>
> 5.4. - Expand B2BUA acronym on first use.
>
> idnits 2.12.13 ran clean.
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>

From narten@us.ibm.com  Thu Jun 28 21:53:06 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A22021F8650 for <ietf@ietfa.amsl.com>; Thu, 28 Jun 2012 21:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 cVoQAYaEE4Tu for <ietf@ietfa.amsl.com>; Thu, 28 Jun 2012 21:53:05 -0700 (PDT)
Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9FA1421F864F for <ietf@ietf.org>; Thu, 28 Jun 2012 21:53:05 -0700 (PDT)
Received: from /spool/local by e1.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 29 Jun 2012 00:53:05 -0400
Received: from d01relay07.pok.ibm.com (9.56.227.147) by e1.ny.us.ibm.com (192.168.1.101) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 29 Jun 2012 00:53:04 -0400
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q5T4r3dF64946308 for <ietf@ietf.org>; Fri, 29 Jun 2012 00:53:03 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q5T4r3Af028197 for <ietf@ietf.org>; Fri, 29 Jun 2012 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q5T4r3ks028180 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 29 Jun 2012 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q5T4r234012871 for <ietf@ietf.org>; Fri, 29 Jun 2012 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q5T4r2XX012832 for ietf@ietf.org; Fri, 29 Jun 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201206290453.q5T4r2XX012832@rotala.raleigh.ibm.com>
Date: Fri, 29 Jun 2012 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
x-cbid: 12062904-6078-0000-0000-00000CAB37F6
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 04:53:06 -0000

Total of 63 messages in the last 7 days.
 
script run at: Fri Jun 29 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 11.11% |    7 |  8.79% |    41754 | stpeter@stpeter.im
  7.94% |    5 |  8.63% |    41009 | barryleiba@computer.org
  7.94% |    5 |  8.35% |    39674 | stewe@stewe.org
  6.35% |    4 |  5.36% |    25484 | abdussalambaryun@gmail.com
  4.76% |    3 |  5.96% |    28300 | stephen.farrell@cs.tcd.ie
  3.17% |    2 |  4.25% |    20199 | duerst@it.aoyama.ac.jp
  3.17% |    2 |  3.49% |    16603 | cntreras@gmail.com
  3.17% |    2 |  3.49% |    16578 | acooper@cdt.org
  3.17% |    2 |  3.01% |    14300 | mellon@fugue.com
  3.17% |    2 |  2.97% |    14087 | uyeshiro@ifa.hawaii.edu
  3.17% |    2 |  2.84% |    13516 | john-ietf@jck.com
  3.17% |    2 |  2.75% |    13077 | tglassey@earthlink.net
  3.17% |    2 |  2.57% |    12205 | hartmans-ietf@mit.edu
  3.17% |    2 |  2.03% |     9641 | jnc@mercury.lcs.mit.edu
  1.59% |    1 |  3.10% |    14728 | ron.even.tlv@gmail.com
  1.59% |    1 |  2.90% |    13770 | lars@netapp.com
  1.59% |    1 |  2.65% |    12579 | dan-ietf@danyork.org
  1.59% |    1 |  2.63% |    12472 | alan.b.johnston@gmail.com
  1.59% |    1 |  2.18% |    10352 | tom.haynes@netapp.com
  1.59% |    1 |  2.11% |    10007 | david.black@emc.com
  1.59% |    1 |  1.79% |     8524 | narten@us.ibm.com
  1.59% |    1 |  1.69% |     8052 | bob.hinden@gmail.com
  1.59% |    1 |  1.55% |     7368 | salvatore.loreto@ericsson.com
  1.59% |    1 |  1.43% |     6803 | marshall.eubanks@gmail.com
  1.59% |    1 |  1.36% |     6439 | sm@resistor.net
  1.59% |    1 |  1.34% |     6385 | melinda.shore@gmail.com
  1.59% |    1 |  1.34% |     6346 | joelja@bogus.com
  1.59% |    1 |  1.30% |     6195 | d3e3e3@gmail.com
  1.59% |    1 |  1.30% |     6192 | marka@isc.org
  1.59% |    1 |  1.23% |     5855 | housley@vigilsec.com
  1.59% |    1 |  1.16% |     5493 | sm+ietf@elandsys.com
  1.59% |    1 |  1.14% |     5402 | dot@dotat.at
  1.59% |    1 |  1.13% |     5363 | tnadeau@lucidvision.com
  1.59% |    1 |  1.09% |     5197 | ajs@anvilwalrusden.com
  1.59% |    1 |  1.09% |     5158 | randy@psg.com
--------+------+--------+----------+------------------------
100.00% |   63 |100.00% |   475107 | Total


From alan.b.johnston@gmail.com  Fri Jun 29 07:17:34 2012
Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2B321F86AA; Fri, 29 Jun 2012 07:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 x0AvZ4aVtn+E; Fri, 29 Jun 2012 07:17:30 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7065A21F86FD; Fri, 29 Jun 2012 07:17:30 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so3073815ggn.31 for <multiple recipients>; Fri, 29 Jun 2012 07:17:29 -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:content-transfer-encoding; bh=dk6H41O8IvIbdLLnP6a+MzMcMIdN1t9ODZg1cOjbDKE=; b=wZDaqviHB5hTcIhpHo1c7UkLyVe1ocVISo/6LELVU5hnz8qzUBKfLpFeC9KuEgAO/n HPMbTfr4InlK0o/9v3kX7RUfPmzVzx4Lpx9YBP34tD7RkOXE9zRdFTgxo5NjT6c9tpBa Gd+TvmbZ/ZgEAUeSTMpHShrmu+HSWETScJFq+yrYIq9+hWqC3ibjgd6UiuZRZ5PPPci1 sR/M6c1DgGxlKWeyDcrz7mbJijNWcCB4+3g9PiOiL3wjY/bqU/WJK//qbRDB+iDXDPSE 1MmtuSZIVmVGrUemaSXg7gwS7qd2vUPBHh8iAnRJ3s4ZTyk/4dfIXQa38JseB0OwL0Ss 5MOQ==
MIME-Version: 1.0
Received: by 10.50.193.196 with SMTP id hq4mr1555160igc.57.1340979449458; Fri, 29 Jun 2012 07:17:29 -0700 (PDT)
Received: by 10.231.228.135 with HTTP; Fri, 29 Jun 2012 07:17:29 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208D3A89C@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com> <8D3D17ACE214DC429325B2B98F3AE71208D3A89C@MX15A.corp.emc.com>
Date: Fri, 29 Jun 2012 09:17:29 -0500
Message-ID: <CAKhHsXEeKYSaM92dhs=mYfyx8ncsCvxW-9A9KGdUbfY3r=EVMw@mail.gmail.com>
Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
From: Alan Johnston <alan.b.johnston@gmail.com>
To: david.black@emc.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mohsen.soroush@sylantro.com, ietf@ietf.org, gen-art@ietf.org, bliss@ietf.org, vvenkatar@gmail.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 14:17:35 -0000

David,

I will make those changes.  Thanks for the feedback.

- Alan -

On Fri, Jun 29, 2012 at 8:43 AM,  <david.black@emc.com> wrote:
> Alan,
>
> Thank you for the quick response. =A0I have a few comments on the propose=
d
> resolutions. =A0Absence of a comment implies that I agree with the propos=
ed
> resolution.
>
> REQ-16 - I understand what's going on here (automatic ringdown), but the
> language is just slightly off because there is actually a dialing request=
.
> Here's all of REQ-16:
>
> =A0 REQ-16 The mechanism should support a way for a UA to seize a
> =A0 particular appearance number and also send the request at the same
> =A0 time. =A0This is needed when an automatic ringdown feature (a telepho=
ne
> =A0 configured to immediately dial a phone number when it goes off hook)
> =A0 is combined with shared appearances - in this case, seizing the line
> =A0 is the same thing as dialing.
>
> The language problem is that the line seizing includes a dialing request,
> so "is the same thing as" isn't quite correct when applied solely to
> "seizing the line". =A0As you suggest, the simplest fix would be to just
> remove "- in this case ... dialing", or it could be changed to:
>
> =A0 =A0 =A0 =A0- in this case, seizing the line is part of dialing.
>
> 5.3 - Doing nothing is fine. =A0I'm not a SIP expert, so I assume that
> the standard PUBLISH behavior (soft-state times out if not refreshed)
> is well-known to anyone who is, and hence no change is needed.
>
> 5.4 - please add "(Bad Request)" after each of the two instances of "400"=
.
>
> 9.1/2/3 - please change to using "SHOULD" in each of these sections
> and explain that the "SHOULD" is motivated by user experience concerns.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: Alan Johnston [mailto:alan.b.johnston@gmail.com]
>> Sent: Thursday, June 28, 2012 9:05 PM
>> To: Black, David
>> Cc: mohsen.soroush@sylantro.com; vvenkatar@gmail.com; gen-art@ietf.org;
>> shida@ntt-at.com; bliss@ietf.org; ietf@ietf.org; rjsparks@nostrum.com
>> Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
>>
>> David,
>>
>> Thank you for your review of the document. =A0See below for how I
>> propose to resolve the issues you have raised. =A0Let me know if you
>> have any other issues or concerns.
>>
>> - Alan -
>>
>> On Thu, Jun 28, 2012 at 3:51 PM, <david.black@emc.com> wrote:
>> >
>> > I am the assigned Gen-ART reviewer for this draft. For background on
>> > Gen-ART, please see the FAQ at
>> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>> >
>> > Please resolve these comments along with any other Last Call comments
>> > you may receive.
>> >
>> > Document: draft-ietf-bliss-shared-appearances-11
>> > Reviewer: David L. Black
>> > Review Date: June 28, 2012
>> > IETF LC End Date: June 28, 2012
>> > IESG Telechat date: (if known)
>> >
>> > Summary:
>> >
>> > This draft is on the right track but has open issues, described in the
>> review.
>> >
>> > This draft describes support for shared appearances in support of mult=
i-line
>> > and shared-line telephone often found in businesses. =A0All of the ope=
n issues
>> > are minor. =A0The draft is well-written and reasonably clear for the m=
ost
>> part,
>> > although significant SIP expertise is required to completely understan=
d it.
>> >
>> > Major issues: =A0None.
>> >
>> > Minor issues:
>> >
>> > 4.1 - REQ-16:
>> >
>> > =A0 in this case, seizing the line is the same thing as dialing.
>> >
>> > That seems wrong - I would have thought it was a "prerequisite" as
>> > opposed to "the same thing" because seizing the line is immediately
>> > followed by a dialing request.
>>
>>
>> This requirement is about sending one request that causes both actions
>> to occur. =A0In a PSTN ringdown circuit (a very specialized circuit,
>> used for "hotlines"), the two operations are the same thing. =A0Besides
>> this statement, is REQ-16 itself not clear? =A0Perhaps I should just
>> remove this statement if it adds confusion rather than clarity to the
>> requirement.
>>
>> >
>> >
>> > 5.3.
>> >
>> > =A0 A user may select an appearance number but then abandon placing a
>> > =A0 call (go back on hook). =A0In this case, the UA MUST free up the
>> > =A0 appearance number by removing the event state with a PUBLISH as
>> > =A0 described in [RFC3903].
>> >
>> > What happens when that can't be done due to UA or network failure?
>>
>>
>> A little further down in this section says:
>>
>> "=A0 This publication state is refreshed as described in [RFC3903] durin=
g
>> =A0 =A0the early dialog state or the Appearance Agent may reassign the
>> =A0 =A0appearance number."
>>
>> So if the removal publish is lost, it will eventually timeout since it
>> is not refreshed. =A0This is standard PUBLISH behavior described in RFC
>> 3903.
>>
>> >
>> >
>> > 5.4.
>> >
>> > =A0 A 400 response is returned if the chosen appearance number is inva=
lid,
>> >
>> > Is that always a 400 (Bad Request) or is any 4xx response allowed? =A0=
If
>> > it's always 400, add the words "Bad Request" after "400".
>>
>> We chose 400 in particular, although any 4xx response would have the
>> same result. =A0"Bad Request" is the reason phrase, and the practice of
>> putting it in () is a convention commonly used in SIP documents. =A0The
>> actual reason phrase can be different, customized ("Invalid
>> Appearance") if desired, or in a different language.
>>
>> So in this case we are specifying the 400 response.
>>
>> >
>> > =A0 If the Appearance Agent policy does not allow this, a 400 response
>> > =A0 is returned.
>> >
>> > Same question. =A0In addition, is 403 Forbidden allowed here?
>>
>> 403 is usually used in SIP to indicate that the request has failed due
>> to an authorization policy, and the request can be retried with
>> different credentials. =A0That doesn't quite fit here.
>>
>> >
>> > =A0 If an INVITE is sent by a member of the group to the shared AOR (i=
.e.
>> > =A0 they call their own AOR), the Appearance Agent MUST assign two
>> > =A0 appearance numbers. =A0The first appearance number will be the one
>> > =A0 selected or assigned to the outgoing INVITE. =A0The second appeara=
nce
>> > =A0 number will be another one assigned by the Appearance Agent for th=
e
>> > =A0 INVITE as it is forked back to the members of the group.
>> >
>> > How does that interact with the single appearance UAs in 8.1.1 that wo=
n't
>> > understand the second appearance number? =A0A warning that such a UA c=
an't
>> > pick up its call to its own AOR would suffice, either here or in 8.1.1=
.
>>
>> I will put text in 8.1.1 that makes this point clear.
>>
>> >
>> > 9.1
>> >
>> > =A0 A UA that has no knowledge of appearances must will only have
>> > =A0 appearance numbers for outgoing calls if assigned by the Appearanc=
e
>> > =A0 Agent. =A0If the non-shared appearance UA does not support Join or
>> > =A0 Replaces, all dialogs could be marked "exclusive" to indicate that
>> > =A0 these options are not available.
>> >
>> > Should that "could be marked" be changed to "SHOULD be marked" ?
>> > Also, analogous questions for "could" in 9.2 and "can" in 9.3.
>> >
>> > All three of these affect interoperability.
>>
>> I can change this to SHOULD. =A0Actually, it doesn't affect
>> interoperability, as "exclusive" is just a hint, for user experience
>> and interface purposes and to reduce failed requests. =A0If a Join or
>> Replace is inadvertently sent, the operation will fail, which is the
>> same result as not allowing it, although a worse user experience.
>>
>> >
>> > 12. Security Considerations
>> >
>> > In general, this section is weak on rationale - the second, third and
>> > fourth paragraphs should all explain more about the purpose of and/or
>> > rationale for their security requirements (e.g., what does the securit=
y
>> > mechanism protect against and when/why might that protection be desire=
d
>> > and/or required?).
>>
>> Right, the mechanisms are to provide privacy and to prevent
>> hijacking/spoofing. =A0I can add text to make this clear.
>>
>> >
>> > =A0 NOTIFY or PUBLISH message bodies that provide the dialog state
>> > =A0 information and the dialog identifiers MAY be encrypted end-to-end
>> > =A0 using the standard mechanisms.
>> >
>> > What are "the standard mechanisms"? =A0List them, and provide referenc=
es,
>> > please.
>>
>> That would be S/MIME as described in RFC 3261. =A0I can add this.
>>
>> >
>> > Please ensure that the section 6 XML and Section 7 ABNF are
>> > syntax-checked with actual tools.
>>
>> I will double check them.
>>
>> >
>> > Nits/editorial comments:
>> >
>> > p.10:
>> >
>> > =A0 The next section discusses the operations used to implement parts =
of
>> > =A0 the shared appearance feature.
>> >
>> > "The following list describes the operations ..." would be better.
>> >
>> > 5.3.1.
>> >
>> > =A0 A UA wanting to place a call but not have an appearance number
>> > =A0 assigned publishes before sending the INVITE without an 'appearanc=
e'
>> > =A0 element but with the 'shared' event package parameter present.
>> >
>> > I think I understand what was intended here, but this would be clearer
>> > if "publishes" was replaced with language about sending a PUBLISH.
>> > It's also not completely clear whether "without" applies to the
>> > INVITE or the PUBLISH, so this sentence probably needs to be reworded.
>>
>> OK, it is the PUBLISH that doesn't have the parameter - I'll make this c=
lear.
>>
>> >
>> > 5.4. - Expand B2BUA acronym on first use.
>> >
>> > idnits 2.12.13 ran clean.
>> >
>> > Thanks,
>> > --David
>> > ----------------------------------------------------
>> > David L. Black, Distinguished Engineer
>> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
>> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 29=
3-7786
>> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
>> > ----------------------------------------------------
>> >
>

From abdussalambaryun@gmail.com  Fri Jun 29 08:34:41 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23AE721F877E for <ietf@ietfa.amsl.com>; Fri, 29 Jun 2012 08:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.192
X-Spam-Level: 
X-Spam-Status: No, score=-3.192 tagged_above=-999 required=5 tests=[AWL=-0.193, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, 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 PlEY2g+69zE9 for <ietf@ietfa.amsl.com>; Fri, 29 Jun 2012 08:34:39 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 53DB621F8776 for <ietf@ietf.org>; Fri, 29 Jun 2012 08:34:39 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2618414vcq.31 for <ietf@ietf.org>; Fri, 29 Jun 2012 08:34:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=sYznqgZKvVyErzn35Ub/C60gf9k4/mQ7PfuFw1hIXdI=; b=Edt+z5DHHlsooMPVVFz2ohzv1srmq9PwsYH0aiDR/adrQMv5ps+UgApXIdfJTrd4cK I4qZzrqf+lMwILNuxRk0SX2FI4H2YSUX5vWCgHlMb8+ePYlVdtnW2U8uqwYxa5PF8ICM dRBEKoVCXdsI0oRxGfjPbTXHZATKlJjVCQTVRVP5w8xZLVnYHWbOCYGurSDmHUmyCMhS jynh5rNpi8gRjrVxyFVfZj4XiGRD1g2/woMZO3wAw/xflJxbqQ+oFULrJZibQvtyFph+ 9wRkfu7NY4duUGrGTSgV0ufWzuMmD4QwnrERkIQyCrgsBacLmq94RK4xjnc+Gm1Jpprd gZ/w==
MIME-Version: 1.0
Received: by 10.52.24.179 with SMTP id v19mr1079205vdf.127.1340984078782; Fri, 29 Jun 2012 08:34:38 -0700 (PDT)
Received: by 10.220.145.9 with HTTP; Fri, 29 Jun 2012 08:34:38 -0700 (PDT)
Date: Fri, 29 Jun 2012 17:34:38 +0200
Message-ID: <CADnDZ8_Vq4fvJzdFJUXYfrfVgtRv6E452ws+jjxs+h75qgA_iA@mail.gmail.com>
Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: david.black@emc.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 15:34:41 -0000

Hi David,

I was not aware of this wiki and review team. does this team review
IETF procedure and policies, please advise,

AB
===========================
I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-bliss-shared-appearances-11
Reviewer: David L. Black
Review Date: June 28, 2012
IETF LC End Date: June 28, 2012
IESG Telechat date: (if known)

Summary:

This draft is on the right track but has open issues, described in the review.

This draft describes support for shared appearances in support of multi-line
and shared-line telephone often found in businesses.  All of the open issues
are minor.  The draft is well-written and reasonably clear for the most part,
although significant SIP expertise is required to completely understand it.

Major issues:  None.

Minor issues:

4.1 - REQ-16:

   in this case, seizing the line is the same thing as dialing.

That seems wrong - I would have thought it was a "prerequisite" as
opposed to "the same thing" because seizing the line is immediately
followed by a dialing request.

5.3.

   A user may select an appearance number but then abandon placing a
   call (go back on hook).  In this case, the UA MUST free up the
   appearance number by removing the event state with a PUBLISH as
   described in [RFC3903].

What happens when that can't be done due to UA or network failure?

5.4.

   A 400 response is returned if the chosen appearance number is invalid,

Is that always a 400 (Bad Request) or is any 4xx response allowed?  If
it's always 400, add the words "Bad Request" after "400".

   If the Appearance Agent policy does not allow this, a 400 response
   is returned.

Same question.  In addition, is 403 Forbidden allowed here?

   If an INVITE is sent by a member of the group to the shared AOR (i.e.
   they call their own AOR), the Appearance Agent MUST assign two
   appearance numbers.  The first appearance number will be the one
   selected or assigned to the outgoing INVITE.  The second appearance
   number will be another one assigned by the Appearance Agent for the
   INVITE as it is forked back to the members of the group.

How does that interact with the single appearance UAs in 8.1.1 that won't
understand the second appearance number?  A warning that such a UA can't
pick up its call to its own AOR would suffice, either here or in 8.1.1.

9.1

   A UA that has no knowledge of appearances must will only have
   appearance numbers for outgoing calls if assigned by the Appearance
   Agent.  If the non-shared appearance UA does not support Join or
   Replaces, all dialogs could be marked "exclusive" to indicate that
   these options are not available.

Should that "could be marked" be changed to "SHOULD be marked" ?
Also, analogous questions for "could" in 9.2 and "can" in 9.3.

All three of these affect interoperability.

12. Security Considerations

In general, this section is weak on rationale - the second, third and
fourth paragraphs should all explain more about the purpose of and/or
rationale for their security requirements (e.g., what does the security
mechanism protect against and when/why might that protection be desired
and/or required?).

   NOTIFY or PUBLISH message bodies that provide the dialog state
   information and the dialog identifiers MAY be encrypted end-to-end
   using the standard mechanisms.

What are "the standard mechanisms"?  List them, and provide references,
please.

Please ensure that the section 6 XML and Section 7 ABNF are
syntax-checked with actual tools.

Nits/editorial comments:

p.10:

   The next section discusses the operations used to implement parts of
   the shared appearance feature.

"The following list describes the operations ..." would be better.

5.3.1.

   A UA wanting to place a call but not have an appearance number
   assigned publishes before sending the INVITE without an 'appearance'
   element but with the 'shared' event package parameter present.

I think I understand what was intended here, but this would be clearer
if "publishes" was replaced with language about sending a PUBLISH.
It's also not completely clear whether "without" applies to the
INVITE or the PUBLISH, so this sentence probably needs to be reworded.

5.4. - Expand B2BUA acronym on first use.

idnits 2.12.13 ran clean.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black at emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------

From adrian@olddog.co.uk  Fri Jun 29 10:13:36 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F306A21F86C2 for <ietf@ietfa.amsl.com>; Fri, 29 Jun 2012 10:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.154
X-Spam-Level: 
X-Spam-Status: No, score=-2.154 tagged_above=-999 required=5 tests=[AWL=-0.155, BAYES_00=-2.599, J_CHICKENPOX_55=0.6]
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 tzGD2RnonXKk for <ietf@ietfa.amsl.com>; Fri, 29 Jun 2012 10:13:35 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD8C21F85E4 for <ietf@ietf.org>; Fri, 29 Jun 2012 10:13:34 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q5THDV2m001578;  Fri, 29 Jun 2012 18:13:31 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q5THDUNI001564 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Jun 2012 18:13:30 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>, <david.black@emc.com>
References: <CADnDZ8_Vq4fvJzdFJUXYfrfVgtRv6E452ws+jjxs+h75qgA_iA@mail.gmail.com>
In-Reply-To: <CADnDZ8_Vq4fvJzdFJUXYfrfVgtRv6E452ws+jjxs+h75qgA_iA@mail.gmail.com>
Subject: RE: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Date: Fri, 29 Jun 2012 18:13:30 +0100
Message-ID: <0c1101cd561a$81e48cf0$85ada6d0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGrVsAUJ8cU2nqJ0H4+em4dc7ailZdVh2+A
Content-Language: en-gb
Cc: 'ietf' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 17:13:36 -0000

Please read the FAQ at http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq
Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Abdussalam Baryun
> Sent: 29 June 2012 16:35
> To: david.black@emc.com
> Cc: ietf
> Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
> 
> Hi David,
> 
> I was not aware of this wiki and review team. does this team review
> IETF procedure and policies, please advise,
> 
> AB
> ===========================
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please resolve these comments along with any other Last Call comments
> you may receive.
> 
> Document: draft-ietf-bliss-shared-appearances-11
> Reviewer: David L. Black
> Review Date: June 28, 2012
> IETF LC End Date: June 28, 2012
> IESG Telechat date: (if known)
> 
> Summary:
> 
> This draft is on the right track but has open issues, described in the review.
> 
> This draft describes support for shared appearances in support of multi-line
> and shared-line telephone often found in businesses.  All of the open issues
> are minor.  The draft is well-written and reasonably clear for the most part,
> although significant SIP expertise is required to completely understand it.
> 
> Major issues:  None.
> 
> Minor issues:
> 
> 4.1 - REQ-16:
> 
>    in this case, seizing the line is the same thing as dialing.
> 
> That seems wrong - I would have thought it was a "prerequisite" as
> opposed to "the same thing" because seizing the line is immediately
> followed by a dialing request.
> 
> 5.3.
> 
>    A user may select an appearance number but then abandon placing a
>    call (go back on hook).  In this case, the UA MUST free up the
>    appearance number by removing the event state with a PUBLISH as
>    described in [RFC3903].
> 
> What happens when that can't be done due to UA or network failure?
> 
> 5.4.
> 
>    A 400 response is returned if the chosen appearance number is invalid,
> 
> Is that always a 400 (Bad Request) or is any 4xx response allowed?  If
> it's always 400, add the words "Bad Request" after "400".
> 
>    If the Appearance Agent policy does not allow this, a 400 response
>    is returned.
> 
> Same question.  In addition, is 403 Forbidden allowed here?
> 
>    If an INVITE is sent by a member of the group to the shared AOR (i.e.
>    they call their own AOR), the Appearance Agent MUST assign two
>    appearance numbers.  The first appearance number will be the one
>    selected or assigned to the outgoing INVITE.  The second appearance
>    number will be another one assigned by the Appearance Agent for the
>    INVITE as it is forked back to the members of the group.
> 
> How does that interact with the single appearance UAs in 8.1.1 that won't
> understand the second appearance number?  A warning that such a UA can't
> pick up its call to its own AOR would suffice, either here or in 8.1.1.
> 
> 9.1
> 
>    A UA that has no knowledge of appearances must will only have
>    appearance numbers for outgoing calls if assigned by the Appearance
>    Agent.  If the non-shared appearance UA does not support Join or
>    Replaces, all dialogs could be marked "exclusive" to indicate that
>    these options are not available.
> 
> Should that "could be marked" be changed to "SHOULD be marked" ?
> Also, analogous questions for "could" in 9.2 and "can" in 9.3.
> 
> All three of these affect interoperability.
> 
> 12. Security Considerations
> 
> In general, this section is weak on rationale - the second, third and
> fourth paragraphs should all explain more about the purpose of and/or
> rationale for their security requirements (e.g., what does the security
> mechanism protect against and when/why might that protection be desired
> and/or required?).
> 
>    NOTIFY or PUBLISH message bodies that provide the dialog state
>    information and the dialog identifiers MAY be encrypted end-to-end
>    using the standard mechanisms.
> 
> What are "the standard mechanisms"?  List them, and provide references,
> please.
> 
> Please ensure that the section 6 XML and Section 7 ABNF are
> syntax-checked with actual tools.
> 
> Nits/editorial comments:
> 
> p.10:
> 
>    The next section discusses the operations used to implement parts of
>    the shared appearance feature.
> 
> "The following list describes the operations ..." would be better.
> 
> 5.3.1.
> 
>    A UA wanting to place a call but not have an appearance number
>    assigned publishes before sending the INVITE without an 'appearance'
>    element but with the 'shared' event package parameter present.
> 
> I think I understand what was intended here, but this would be clearer
> if "publishes" was replaced with language about sending a PUBLISH.
> It's also not completely clear whether "without" applies to the
> INVITE or the PUBLISH, so this sentence probably needs to be reworded.
> 
> 5.4. - Expand B2BUA acronym on first use.
> 
> idnits 2.12.13 ran clean.
> 
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black at emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From peter@akayla.com  Thu Jun 28 21:55:14 2012
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7235111E8120 for <ietf@ietfa.amsl.com>; Thu, 28 Jun 2012 21:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 IFv3cEhVrofk for <ietf@ietfa.amsl.com>; Thu, 28 Jun 2012 21:55:13 -0700 (PDT)
Received: from p3plsmtpa01-03.prod.phx3.secureserver.net (p3plsmtpa01-03.prod.phx3.secureserver.net [72.167.82.83]) by ietfa.amsl.com (Postfix) with SMTP id 329D811E8109 for <ietf@ietf.org>; Thu, 28 Jun 2012 21:55:13 -0700 (PDT)
Received: (qmail 25222 invoked from network); 29 Jun 2012 04:55:12 -0000
Received: from unknown (173.8.184.78) by p3plsmtpa01-03.prod.phx3.secureserver.net (72.167.82.83) with ESMTP; 29 Jun 2012 04:55:08 -0000
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-ippm-twamp-value-added-octets.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-ippm-twamp-value-added-octets-03
Date: Thu, 28 Jun 2012 21:55:10 -0700
Message-ID: <029601cd55b3$5d387360$17a95a20$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1Vst90fvRgMPNAQLeI1Kicrd8uCw==
Content-Language: en-us
X-Mailman-Approved-At: Fri, 29 Jun 2012 11:58:25 -0700
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 04:55:14 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-ippm-twamp-value-added-octets-03
Reviewer: Peter Yee
Review Date: 28-June-2012
IETF LC End Date: 28-June-2012
IESG Telechat date: Pending

Summary: This draft describes an extension to the TWAMP protocol for
handling
packet "trains" which are used to quantify network capacity metrics. 
The document is ready for publication as an informational RFC. 

Major Issues: None

Minor Issues: None

Nits/editorial comments:

Section 2, in the paragraph right after the two bullets: "measurements" ->
"measurement".

Section 3, 5th paragraph, 4th sentence ("The method to measuring the UDP
delivery rate may also
require the packet loss.") left me confused.  Did you mean something like
"The method for
measuring the UDP delivery rate may also require the rate of packet loss."?
Percentage?
Count?

Next paragraph, 2nd sentence: "rate" -> "rates".

Next paragraph, same change.

Section 4, 2nd paragraph, 2nd sentence: "require" -> "requires".

Section 5, 2nd paragraph, 1st sentence: "of first" -> "of the first".

Section 5, 3rd diagram, it's not utterly clear that the Reserved field
includes the two bits
from the last octet on the previous line.  (Yes, I do understand that it's
really hard to
indicate the connection in an ASCII diagram!)  The text implies that must be
the case,
but only owing to the size of the field.

Section 5.1, second to last paragraph, last sentence: "If I bit" -> "If the
I bit".

Section 5.2, 2nd bullet, 2nd sub-bullet, 2nd sentence: "the another" ->
"another".

Section 5.:, "to estimate or calculate" -> "to estimating or calculating"?

Section 5.3, second sentence: "to identify" -> "of identifying".

Section 6, 1st paragraph: "direction" -> "directions".

Section 6, 2nd paragraph, 2nd sentence: "the whole trains" -> "whole
trains".

Section 6, 2nd paragraph, last sentence: "of new field" -> "of a new field".



From david.black@emc.com  Fri Jun 29 06:44:21 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C061721F86FD; Fri, 29 Jun 2012 06:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.398
X-Spam-Level: 
X-Spam-Status: No, score=-102.398 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 qImnSoaOKl70; Fri, 29 Jun 2012 06:44:20 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id C57C321F86C2; Fri, 29 Jun 2012 06:44:19 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5TDi7fv003111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2012 09:44:16 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 29 Jun 2012 09:43:57 -0400
Received: from mxhub15.corp.emc.com (mxhub15.corp.emc.com [128.222.70.236]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5TDht9Y008133; Fri, 29 Jun 2012 09:43:56 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub15.corp.emc.com ([128.222.70.236]) with mapi; Fri, 29 Jun 2012 09:43:55 -0400
From: <david.black@emc.com>
To: <alan.b.johnston@gmail.com>
Date: Fri, 29 Jun 2012 09:43:54 -0400
Subject: RE: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Index: Ac1Vk1H5siVBJynsTLy55SYGzR+w1QAZ0lZQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208D3A89C@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
In-Reply-To: <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 29 Jun 2012 11:58:25 -0700
Cc: mohsen.soroush@sylantro.com, ietf@ietf.org, gen-art@ietf.org, bliss@ietf.org, vvenkatar@gmail.com, david.black@emc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 13:44:22 -0000

Alan,

Thank you for the quick response.  I have a few comments on the proposed
resolutions.  Absence of a comment implies that I agree with the proposed
resolution.

REQ-16 - I understand what's going on here (automatic ringdown), but the
language is just slightly off because there is actually a dialing request.
Here's all of REQ-16:

   REQ-16 The mechanism should support a way for a UA to seize a
   particular appearance number and also send the request at the same
   time.  This is needed when an automatic ringdown feature (a telephone
   configured to immediately dial a phone number when it goes off hook)
   is combined with shared appearances - in this case, seizing the line
   is the same thing as dialing.

The language problem is that the line seizing includes a dialing request,
so "is the same thing as" isn't quite correct when applied solely to
"seizing the line".  As you suggest, the simplest fix would be to just
remove "- in this case ... dialing", or it could be changed to:

	- in this case, seizing the line is part of dialing.

5.3 - Doing nothing is fine.  I'm not a SIP expert, so I assume that
the standard PUBLISH behavior (soft-state times out if not refreshed)
is well-known to anyone who is, and hence no change is needed.

5.4 - please add "(Bad Request)" after each of the two instances of "400".

9.1/2/3 - please change to using "SHOULD" in each of these sections
and explain that the "SHOULD" is motivated by user experience concerns.

Thanks,
--David

> -----Original Message-----
> From: Alan Johnston [mailto:alan.b.johnston@gmail.com]
> Sent: Thursday, June 28, 2012 9:05 PM
> To: Black, David
> Cc: mohsen.soroush@sylantro.com; vvenkatar@gmail.com; gen-art@ietf.org;
> shida@ntt-at.com; bliss@ietf.org; ietf@ietf.org; rjsparks@nostrum.com
> Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
>=20
> David,
>=20
> Thank you for your review of the document. =A0See below for how I
> propose to resolve the issues you have raised.  Let me know if you
> have any other issues or concerns.
>=20
> - Alan -
>=20
> On Thu, Jun 28, 2012 at 3:51 PM, <david.black@emc.com> wrote:
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-bliss-shared-appearances-11
> > Reviewer: David L. Black
> > Review Date: June 28, 2012
> > IETF LC End Date: June 28, 2012
> > IESG Telechat date: (if known)
> >
> > Summary:
> >
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > This draft describes support for shared appearances in support of multi=
-line
> > and shared-line telephone often found in businesses. =A0All of the open=
 issues
> > are minor. =A0The draft is well-written and reasonably clear for the mo=
st
> part,
> > although significant SIP expertise is required to completely understand=
 it.
> >
> > Major issues: =A0None.
> >
> > Minor issues:
> >
> > 4.1 - REQ-16:
> >
> > =A0 in this case, seizing the line is the same thing as dialing.
> >
> > That seems wrong - I would have thought it was a "prerequisite" as
> > opposed to "the same thing" because seizing the line is immediately
> > followed by a dialing request.
>=20
>=20
> This requirement is about sending one request that causes both actions
> to occur. =A0In a PSTN ringdown circuit (a very specialized circuit,
> used for "hotlines"), the two operations are the same thing. =A0Besides
> this statement, is REQ-16 itself not clear? =A0Perhaps I should just
> remove this statement if it adds confusion rather than clarity to the
> requirement.
>=20
> >
> >
> > 5.3.
> >
> > =A0 A user may select an appearance number but then abandon placing a
> > =A0 call (go back on hook). =A0In this case, the UA MUST free up the
> > =A0 appearance number by removing the event state with a PUBLISH as
> > =A0 described in [RFC3903].
> >
> > What happens when that can't be done due to UA or network failure?
>=20
>=20
> A little further down in this section says:
>=20
> "=A0 This publication state is refreshed as described in [RFC3903] during
> =A0 =A0the early dialog state or the Appearance Agent may reassign the
> =A0 =A0appearance number."
>=20
> So if the removal publish is lost, it will eventually timeout since it
> is not refreshed.  This is standard PUBLISH behavior described in RFC
> 3903.
>=20
> >
> >
> > 5.4.
> >
> > =A0 A 400 response is returned if the chosen appearance number is inval=
id,
> >
> > Is that always a 400 (Bad Request) or is any 4xx response allowed? =A0I=
f
> > it's always 400, add the words "Bad Request" after "400".
>=20
> We chose 400 in particular, although any 4xx response would have the
> same result.  "Bad Request" is the reason phrase, and the practice of
> putting it in () is a convention commonly used in SIP documents.  The
> actual reason phrase can be different, customized ("Invalid
> Appearance") if desired, or in a different language.
>=20
> So in this case we are specifying the 400 response.
>=20
> >
> > =A0 If the Appearance Agent policy does not allow this, a 400 response
> > =A0 is returned.
> >
> > Same question. =A0In addition, is 403 Forbidden allowed here?
>=20
> 403 is usually used in SIP to indicate that the request has failed due
> to an authorization policy, and the request can be retried with
> different credentials.  That doesn't quite fit here.
>=20
> >
> > =A0 If an INVITE is sent by a member of the group to the shared AOR (i.=
e.
> > =A0 they call their own AOR), the Appearance Agent MUST assign two
> > =A0 appearance numbers. =A0The first appearance number will be the one
> > =A0 selected or assigned to the outgoing INVITE. =A0The second appearan=
ce
> > =A0 number will be another one assigned by the Appearance Agent for the
> > =A0 INVITE as it is forked back to the members of the group.
> >
> > How does that interact with the single appearance UAs in 8.1.1 that won=
't
> > understand the second appearance number? =A0A warning that such a UA ca=
n't
> > pick up its call to its own AOR would suffice, either here or in 8.1.1.
>=20
> I will put text in 8.1.1 that makes this point clear.
>=20
> >
> > 9.1
> >
> > =A0 A UA that has no knowledge of appearances must will only have
> > =A0 appearance numbers for outgoing calls if assigned by the Appearance
> > =A0 Agent. =A0If the non-shared appearance UA does not support Join or
> > =A0 Replaces, all dialogs could be marked "exclusive" to indicate that
> > =A0 these options are not available.
> >
> > Should that "could be marked" be changed to "SHOULD be marked" ?
> > Also, analogous questions for "could" in 9.2 and "can" in 9.3.
> >
> > All three of these affect interoperability.
>=20
> I can change this to SHOULD.  Actually, it doesn't affect
> interoperability, as "exclusive" is just a hint, for user experience
> and interface purposes and to reduce failed requests.  If a Join or
> Replace is inadvertently sent, the operation will fail, which is the
> same result as not allowing it, although a worse user experience.
>=20
> >
> > 12. Security Considerations
> >
> > In general, this section is weak on rationale - the second, third and
> > fourth paragraphs should all explain more about the purpose of and/or
> > rationale for their security requirements (e.g., what does the security
> > mechanism protect against and when/why might that protection be desired
> > and/or required?).
>=20
> Right, the mechanisms are to provide privacy and to prevent
> hijacking/spoofing.  I can add text to make this clear.
>=20
> >
> > =A0 NOTIFY or PUBLISH message bodies that provide the dialog state
> > =A0 information and the dialog identifiers MAY be encrypted end-to-end
> > =A0 using the standard mechanisms.
> >
> > What are "the standard mechanisms"? =A0List them, and provide reference=
s,
> > please.
>=20
> That would be S/MIME as described in RFC 3261.  I can add this.
>=20
> >
> > Please ensure that the section 6 XML and Section 7 ABNF are
> > syntax-checked with actual tools.
>=20
> I will double check them.
>=20
> >
> > Nits/editorial comments:
> >
> > p.10:
> >
> > =A0 The next section discusses the operations used to implement parts o=
f
> > =A0 the shared appearance feature.
> >
> > "The following list describes the operations ..." would be better.
> >
> > 5.3.1.
> >
> > =A0 A UA wanting to place a call but not have an appearance number
> > =A0 assigned publishes before sending the INVITE without an 'appearance=
'
> > =A0 element but with the 'shared' event package parameter present.
> >
> > I think I understand what was intended here, but this would be clearer
> > if "publishes" was replaced with language about sending a PUBLISH.
> > It's also not completely clear whether "without" applies to the
> > INVITE or the PUBLISH, so this sentence probably needs to be reworded.
>=20
> OK, it is the PUBLISH that doesn't have the parameter - I'll make this cl=
ear.
>=20
> >
> > 5.4. - Expand B2BUA acronym on first use.
> >
> > idnits 2.12.13 ran clean.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >


From david.black@emc.com  Fri Jun 29 08:44:58 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A23821F87AD for <ietf@ietfa.amsl.com>; Fri, 29 Jun 2012 08:44:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.111
X-Spam-Level: 
X-Spam-Status: No, score=-102.111 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, USER_IN_WHITELIST=-100]
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 vcO4TELxYAiT for <ietf@ietfa.amsl.com>; Fri, 29 Jun 2012 08:44:55 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id A064521F85D8 for <ietf@ietf.org>; Fri, 29 Jun 2012 08:44:54 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5TFii30013354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2012 11:44:51 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 29 Jun 2012 11:44:26 -0400
Received: from mxhub08.corp.emc.com (mxhub08.corp.emc.com [128.222.70.205]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5TFiPs2007346; Fri, 29 Jun 2012 11:44:25 -0400
Received: from mxhub38.corp.emc.com (128.222.70.105) by mxhub08.corp.emc.com (128.222.70.205) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 29 Jun 2012 11:44:25 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub38.corp.emc.com ([128.222.70.105]) with mapi; Fri, 29 Jun 2012 11:44:24 -0400
From: <david.black@emc.com>
To: <abdussalambaryun@gmail.com>
Date: Fri, 29 Jun 2012 11:44:23 -0400
Subject: RE: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Index: Ac1WDL0dQ5SynxyIStyuOn/DS/o3owAARjqA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208D3A914@MX15A.corp.emc.com>
References: <CADnDZ8_Vq4fvJzdFJUXYfrfVgtRv6E452ws+jjxs+h75qgA_iA@mail.gmail.com>
In-Reply-To: <CADnDZ8_Vq4fvJzdFJUXYfrfVgtRv6E452ws+jjxs+h75qgA_iA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 29 Jun 2012 11:58:25 -0700
Cc: david.black@emc.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 15:44:59 -0000

> I was not aware of this wiki and review team. does this team review
> IETF procedure and policies, please advise,

Only when those procedures and policies are in documents that are being con=
sidered
for [RFC] publication, as indicated in the first Q&A in the FAQ:

Q: What is Gen-ART?

A: The General Area Review Team. They provide generalist reviews for the Ge=
neral Area director (currently the IETF Chair), providing an additional set=
 of eyes for documents as they are being considered for publication.

Thanks,
--David

> -----Original Message-----
> From: Abdussalam Baryun [mailto:abdussalambaryun@gmail.com]
> Sent: Friday, June 29, 2012 11:35 AM
> To: Black, David
> Cc: ietf
> Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
>=20
> Hi David,
>=20
> I was not aware of this wiki and review team. does this team review
> IETF procedure and policies, please advise,
>=20
> AB
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-bliss-shared-appearances-11
> Reviewer: David L. Black
> Review Date: June 28, 2012
> IETF LC End Date: June 28, 2012
> IESG Telechat date: (if known)
>=20
> Summary:
>=20
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> This draft describes support for shared appearances in support of multi-l=
ine
> and shared-line telephone often found in businesses.  All of the open iss=
ues
> are minor.  The draft is well-written and reasonably clear for the most p=
art,
> although significant SIP expertise is required to completely understand i=
t.
>=20
> Major issues:  None.
>=20
> Minor issues:
>=20
> 4.1 - REQ-16:
>=20
>    in this case, seizing the line is the same thing as dialing.
>=20
> That seems wrong - I would have thought it was a "prerequisite" as
> opposed to "the same thing" because seizing the line is immediately
> followed by a dialing request.
>=20
> 5.3.
>=20
>    A user may select an appearance number but then abandon placing a
>    call (go back on hook).  In this case, the UA MUST free up the
>    appearance number by removing the event state with a PUBLISH as
>    described in [RFC3903].
>=20
> What happens when that can't be done due to UA or network failure?
>=20
> 5.4.
>=20
>    A 400 response is returned if the chosen appearance number is invalid,
>=20
> Is that always a 400 (Bad Request) or is any 4xx response allowed?  If
> it's always 400, add the words "Bad Request" after "400".
>=20
>    If the Appearance Agent policy does not allow this, a 400 response
>    is returned.
>=20
> Same question.  In addition, is 403 Forbidden allowed here?
>=20
>    If an INVITE is sent by a member of the group to the shared AOR (i.e.
>    they call their own AOR), the Appearance Agent MUST assign two
>    appearance numbers.  The first appearance number will be the one
>    selected or assigned to the outgoing INVITE.  The second appearance
>    number will be another one assigned by the Appearance Agent for the
>    INVITE as it is forked back to the members of the group.
>=20
> How does that interact with the single appearance UAs in 8.1.1 that won't
> understand the second appearance number?  A warning that such a UA can't
> pick up its call to its own AOR would suffice, either here or in 8.1.1.
>=20
> 9.1
>=20
>    A UA that has no knowledge of appearances must will only have
>    appearance numbers for outgoing calls if assigned by the Appearance
>    Agent.  If the non-shared appearance UA does not support Join or
>    Replaces, all dialogs could be marked "exclusive" to indicate that
>    these options are not available.
>=20
> Should that "could be marked" be changed to "SHOULD be marked" ?
> Also, analogous questions for "could" in 9.2 and "can" in 9.3.
>=20
> All three of these affect interoperability.
>=20
> 12. Security Considerations
>=20
> In general, this section is weak on rationale - the second, third and
> fourth paragraphs should all explain more about the purpose of and/or
> rationale for their security requirements (e.g., what does the security
> mechanism protect against and when/why might that protection be desired
> and/or required?).
>=20
>    NOTIFY or PUBLISH message bodies that provide the dialog state
>    information and the dialog identifiers MAY be encrypted end-to-end
>    using the standard mechanisms.
>=20
> What are "the standard mechanisms"?  List them, and provide references,
> please.
>=20
> Please ensure that the section 6 XML and Section 7 ABNF are
> syntax-checked with actual tools.
>=20
> Nits/editorial comments:
>=20
> p.10:
>=20
>    The next section discusses the operations used to implement parts of
>    the shared appearance feature.
>=20
> "The following list describes the operations ..." would be better.
>=20
> 5.3.1.
>=20
>    A UA wanting to place a call but not have an appearance number
>    assigned publishes before sending the INVITE without an 'appearance'
>    element but with the 'shared' event package parameter present.
>=20
> I think I understand what was intended here, but this would be clearer
> if "publishes" was replaced with language about sending a PUBLISH.
> It's also not completely clear whether "without" applies to the
> INVITE or the PUBLISH, so this sentence probably needs to be reworded.
>=20
> 5.4. - Expand B2BUA acronym on first use.
>=20
> idnits 2.12.13 ran clean.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black at emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From dworley@avaya.com  Fri Jun 29 12:18:33 2012
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54B0C21F8865; Fri, 29 Jun 2012 12:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.952
X-Spam-Level: 
X-Spam-Status: No, score=-102.952 tagged_above=-999 required=5 tests=[AWL=0.647, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 D2sT0e2dOwwG; Fri, 29 Jun 2012 12:18:32 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id D1EF821F87EC; Fri, 29 Jun 2012 12:18:31 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAIj+7U+HCzI1/2dsb2JhbABFhVqvXoEegQeCGAEBAQEDEhERRRACAQgNCwICJgICAjAVEAEBBA4NGodpnnqKHpMggSCPDzJgA5sriguCew
X-IronPort-AV: E=Sophos;i="4.77,499,1336363200"; d="scan'208";a="313255578"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 29 Jun 2012 15:15:55 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 29 Jun 2012 14:59:49 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 29 Jun 2012 15:18:28 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "alan.b.johnston@gmail.com" <alan.b.johnston@gmail.com>
Date: Fri, 29 Jun 2012 15:18:24 -0400
Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Index: Ac1WK/SS5AOXm0ZpSfqMaQa/q754dw==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
In-Reply-To: <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "mohsen.soroush@sylantro.com" <mohsen.soroush@sylantro.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "bliss@ietf.org" <bliss@ietf.org>, "vvenkatar@gmail.com" <vvenkatar@gmail.com>, "david.black@emc.com" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 19:18:33 -0000

T24gVGh1LCAyMDEyLTA2LTI4IGF0IDIwOjA1IC0wNTAwLCBBbGFuIEpvaG5zdG9uIHdyb3RlOgo+
ID4KPiA+IDQuMSAtIFJFUS0xNjoKPiA+Cj4gPiAgIGluIHRoaXMgY2FzZSwgc2VpemluZyB0aGUg
bGluZSBpcyB0aGUgc2FtZSB0aGluZyBhcyBkaWFsaW5nLgo+ID4KPiA+IFRoYXQgc2VlbXMgd3Jv
bmcgLSBJIHdvdWxkIGhhdmUgdGhvdWdodCBpdCB3YXMgYSAicHJlcmVxdWlzaXRlIiBhcwo+ID4g
b3Bwb3NlZCB0byAidGhlIHNhbWUgdGhpbmciIGJlY2F1c2Ugc2VpemluZyB0aGUgbGluZSBpcyBp
bW1lZGlhdGVseQo+ID4gZm9sbG93ZWQgYnkgYSBkaWFsaW5nIHJlcXVlc3QuCj4gCj4gCj4gVGhp
cyByZXF1aXJlbWVudCBpcyBhYm91dCBzZW5kaW5nIG9uZSByZXF1ZXN0IHRoYXQgY2F1c2VzIGJv
dGggYWN0aW9ucwo+IHRvIG9jY3VyLiAgSW4gYSBQU1ROIHJpbmdkb3duIGNpcmN1aXQgKGEgdmVy
eSBzcGVjaWFsaXplZCBjaXJjdWl0LAo+IHVzZWQgZm9yICJob3RsaW5lcyIpLCB0aGUgdHdvIG9w
ZXJhdGlvbnMgYXJlIHRoZSBzYW1lIHRoaW5nLiAgQmVzaWRlcwo+IHRoaXMgc3RhdGVtZW50LCBp
cyBSRVEtMTYgaXRzZWxmIG5vdCBjbGVhcj8gIFBlcmhhcHMgSSBzaG91bGQganVzdAo+IHJlbW92
ZSB0aGlzIHN0YXRlbWVudCBpZiBpdCBhZGRzIGNvbmZ1c2lvbiByYXRoZXIgdGhhbiBjbGFyaXR5
IHRvIHRoZQo+IHJlcXVpcmVtZW50LgoKSU1ITywgYSBnb29kIGZpeCBpczoKCiAgIFJFUS0xNiBU
aGUgbWVjaGFuaXNtIHNob3VsZCBzdXBwb3J0IGEgd2F5IGZvciBhIFVBIHRvIHNlaXplIGEKICAg
cGFydGljdWxhciBhcHBlYXJhbmNlIG51bWJlciBhbmQgYWxzbyBzZW5kIHRoZSByZXF1ZXN0IGF0
IHRoZSBzYW1lCiAgIHRpbWUuICBUaGlzIGlzIG5lZWRlZCB3aGVuIGFuIGF1dG9tYXRpYyByaW5n
ZG93biBmZWF0dXJlIChhIHRlbGVwaG9uZQogICBjb25maWd1cmVkIHRvIGltbWVkaWF0ZWx5IGRp
YWwgYSBwaG9uZSBudW1iZXIgd2hlbiBpdCBnb2VzIG9mZiBob29rKQogICBpcyBjb21iaW5lZCB3
aXRoIHNoYXJlZCBhcHBlYXJhbmNlcyAtIGluIHRoaXMgY2FzZSwgc2VpemluZyB0aGUgbGluZQog
ICBpcyA+Pj5pbnRlZ3JhdGVkIHdpdGg8PDwgZGlhbGluZy4KCkRhbGUKCg==

From alan.b.johnston@gmail.com  Fri Jun 29 17:43:05 2012
Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94E2721F849A; Fri, 29 Jun 2012 17:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.203
X-Spam-Level: 
X-Spam-Status: No, score=-102.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1,  USER_IN_WHITELIST=-100]
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 hTu8so4Rqnni; Fri, 29 Jun 2012 17:43:05 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id E510E21F844B; Fri, 29 Jun 2012 17:43:04 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so4968301obb.31 for <multiple recipients>; Fri, 29 Jun 2012 17:43:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:x-mailer:from:subject:date:to; bh=eF5yYxdrm0swAjP9jGXQF5kDnPRhZ5N4RqNg9kmEaAg=; b=lmI3kN/oGVrNVHkFcngn92r1j6nz79rYUHZ9LmTrY6z+izKqaavsbSu4mkkSS9p7Lh UFbT681uPb65ttObCQhOgHSOPHhBicGul30lCpfNhOcwO2sv1mFA7el3R6KSD5SBBQeh 82KbdsDeR/2Sf+IO6c62aNkRpmKS5j/0BX/DsrQxL1yqFjFztzw7SP+e974xFg1EDaEC 3M7AAlmzkCLX+Z/P0zDMfmaBE7D1X1dw1Bk1Wb11ii2J5K9BWv2rXwhUjr9yLb7vfIsS 9yqKFUzTnlqxfbdsm3NoH3OLstuFflkXYa3sdoAiXuAsuLzaabi84CtDU0eYnx2wpE20 Vesw==
Received: by 10.60.21.198 with SMTP id x6mr2034683oee.24.1341016898396; Fri, 29 Jun 2012 17:41:38 -0700 (PDT)
Received: from [10.4.153.20] (mobile-166-147-069-169.mycingular.net. [166.147.69.169]) by mx.google.com with ESMTPS id n10sm4159930oeb.6.2012.06.29.17.41.36 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Jun 2012 17:41:37 -0700 (PDT)
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.com>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain; charset=us-ascii
Message-Id: <8CC36564-7A02-47AC-9BCA-4DE0C9BECADE@gmail.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (9B206)
From: Alan Johnston <alan.b.johnston@gmail.com>
Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Date: Fri, 29 Jun 2012 19:41:28 -0500
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Cc: "mohsen.soroush@sylantro.com" <mohsen.soroush@sylantro.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "bliss@ietf.org" <bliss@ietf.org>, "vvenkatar@gmail.com" <vvenkatar@gmail.com>, "david.black@emc.com" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jun 2012 00:43:05 -0000

We will use this language. Thanks, Dale.=20

 - Alan -



On Jun 29, 2012, at 2:18 PM, "Worley, Dale R (Dale)" <dworley@avaya.com> wro=
te:

> On Thu, 2012-06-28 at 20:05 -0500, Alan Johnston wrote:
>>>=20
>>> 4.1 - REQ-16:
>>>=20
>>>  in this case, seizing the line is the same thing as dialing.
>>>=20
>>> That seems wrong - I would have thought it was a "prerequisite" as
>>> opposed to "the same thing" because seizing the line is immediately
>>> followed by a dialing request.
>>=20
>>=20
>> This requirement is about sending one request that causes both actions
>> to occur.  In a PSTN ringdown circuit (a very specialized circuit,
>> used for "hotlines"), the two operations are the same thing.  Besides
>> this statement, is REQ-16 itself not clear?  Perhaps I should just
>> remove this statement if it adds confusion rather than clarity to the
>> requirement.
>=20
> IMHO, a good fix is:
>=20
>   REQ-16 The mechanism should support a way for a UA to seize a
>   particular appearance number and also send the request at the same
>   time.  This is needed when an automatic ringdown feature (a telephone
>   configured to immediately dial a phone number when it goes off hook)
>   is combined with shared appearances - in this case, seizing the line
>   is >>>integrated with<<< dialing.
>=20
> Dale
>=20
